Alarms and Performance Events Reference (V100R005C00 - 01) PDF

OptiX OSN 9560 Intelligent Optical Switching
System
V100R005C00
Alarms and Performance Events

Reference
Issue 01
Date 2012-05-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

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

Copyright © Huawei Technologies Co., Ltd.
OptiX OSN 9560 Intelligent Optical Switching System
Alarms and Performance Events Reference About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 9560 V100R005C00
iManager U2000 V100R006C00
Intended Audience
This document describes the alarms and performance events of the OptiX OSN 9560 equipment
in terms of generation principles, classification list, and handling methods.
The intended audience of this document is system maintenance engineer.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

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

avoided, could result in equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
time.
Issue 01 (2012-05-30) Huawei Proprietary and Confidential ii

Alarms and Performance Events Reference About This Document
Symbol Description
NOTE Provides additional information to emphasize or supplement

important points of the main text.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

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

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 01(2012-05-30)

This is the first document issue for the V100R005C00 product version.
Issue 01 (2012-05-30) Huawei Proprietary and Confidential iii

Alarms and Performance Events Reference Contents
Contents
About This Document.....................................................................................................................ii

1 Generation of Alarms and Performance Events of SDH Services.......................................1
1.1 Overview............................................................................................................................................................2
1.1.1 Directions and Levels of Signal Flows......................................................................................................2
1.1.2 Two Common Alarms...............................................................................................................................3
1.1.3 Alarm Management...................................................................................................................................4
1.2 Generation and Detection of Alarms and Performance Events in the SDH Higher Order Signal Flow............5
1.2.1 Downstream Signal Flow..........................................................................................................................6
1.2.2 Upstream Signal Flow...............................................................................................................................9
1.3 Suppression Correlation Between SDH Alarms...............................................................................................10
1.4 Generation and Detection of SDH Performance Events...................................................................................11
1.4.1 Bit Errors.................................................................................................................................................11
1.4.2 Pointer Justification.................................................................................................................................15
2 Alarm list.......................................................................................................................................18
2.1 Alphabetically Listed Alarms...........................................................................................................................19
2.1.1 Alarm List A............................................................................................................................................19
2.1.2 Alarm List B............................................................................................................................................19
2.1.3 Alarm List C............................................................................................................................................21
2.1.4 Alarm List D............................................................................................................................................22
2.1.5 Alarm List E............................................................................................................................................22
2.1.6 Alarm List F.............................................................................................................................................23
2.1.7 Alarm List G............................................................................................................................................24
2.1.8 Alarm List H............................................................................................................................................24
2.1.9 Alarm List I.............................................................................................................................................26
2.1.10 Alarm List J...........................................................................................................................................26
2.1.11 Alarm List K..........................................................................................................................................26
2.1.12 Alarm List L..........................................................................................................................................26
2.1.13 Alarm List M.........................................................................................................................................29
2.1.14 Alarm List N..........................................................................................................................................30
2.1.15 Alarm List O..........................................................................................................................................30
2.1.16 Alarm List P...........................................................................................................................................32
2.1.17 Alarm List R..........................................................................................................................................34
Issue 01 (2012-05-30) Huawei Proprietary and Confidential iv

2.1.18 Alarm List S...........................................................................................................................................35

2.1.19 Alarm List T..........................................................................................................................................39
2.1.20 Alarm List V..........................................................................................................................................40
2.1.21 Alarm List W.........................................................................................................................................41
2.1.22 Alarm List X..........................................................................................................................................41
2.2 Alarms Classified by Board Type....................................................................................................................42
2.2.1 N1EGSH..................................................................................................................................................42
2.2.2 N1SF64A.................................................................................................................................................43
2.2.3 N3SLH41.................................................................................................................................................44
2.2.4 N4BPA.....................................................................................................................................................44
2.2.5 N4SF64....................................................................................................................................................45
2.2.6 N4SFD64.................................................................................................................................................46
2.2.7 N4SL64....................................................................................................................................................47
2.2.8 N4SLD64.................................................................................................................................................47
2.2.9 N4SLO16.................................................................................................................................................48
2.2.10 N4SLQ16...............................................................................................................................................49
2.2.11 N4SLQ64...............................................................................................................................................49
2.2.12 TN11CRPC............................................................................................................................................50
2.2.13 TN11DCU.............................................................................................................................................50
2.2.14 TN11MR2..............................................................................................................................................50
2.2.15 TN12OAU1...........................................................................................................................................51
2.2.16 TN12OBU1...........................................................................................................................................51
2.2.17 TN51ATE..............................................................................................................................................51
2.2.18 TN51AUX.............................................................................................................................................52
2.2.19 TN51FAN..............................................................................................................................................52
2.2.20 TN51PIU...............................................................................................................................................52
2.2.21 TN52SCC..............................................................................................................................................52
2.2.22 TN52STG..............................................................................................................................................53
2.2.23 TN52STI................................................................................................................................................53
2.2.24 TNL1STI...............................................................................................................................................53
2.2.25 TNL2SEI1.............................................................................................................................................54
2.2.26 TNL2SEI2.............................................................................................................................................54
2.2.27 TNL2SXCM..........................................................................................................................................54
3 Handling Common Alarms.......................................................................................................55

3.1 ALM_GFP_dLFD............................................................................................................................................58
3.2 APS_INDI........................................................................................................................................................60
3.3 AU_AIS............................................................................................................................................................64
3.4 AU_LOP...........................................................................................................................................................66
3.5 B1_EXC............................................................................................................................................................69
3.6 BD_STATUS....................................................................................................................................................72
3.7 BUS_ERR.........................................................................................................................................................74
3.8 COMMUN_FAIL.............................................................................................................................................77
Issue 01 (2012-05-30) Huawei Proprietary and Confidential v

3.9 CLK_NO_TRACE_MODE..............................................................................................................................79
3.10 EXT_SYNC_LOS..........................................................................................................................................80
3.11 FCS_ERR.......................................................................................................................................................83
3.12 HARD_BAD..................................................................................................................................................84
3.13 IN_PWR_HIGH.............................................................................................................................................87
3.14 IN_PWR_LOW..............................................................................................................................................88
3.15 LINK_ERR.....................................................................................................................................................90
3.16 LOOP_ALM...................................................................................................................................................91
3.17 LSR_WILL_DIE............................................................................................................................................93
3.18 LTI..................................................................................................................................................................94
3.19 MS_AIS..........................................................................................................................................................97
3.20 OUT_PWR_HIGH.........................................................................................................................................98
3.21 OUT_PWR_LOW..........................................................................................................................................99
3.22 POWER_ABNORMAL...............................................................................................................................100
3.23 POWER_FAIL.............................................................................................................................................103
3.24 SYN_BAD....................................................................................................................................................105
3.25 SYNC_C_LOS.............................................................................................................................................107
3.26 R_LOS..........................................................................................................................................................109
3.27 R_LOF..........................................................................................................................................................112
3.28 TEMP_OVER...............................................................................................................................................115
3.29 WRG_BD_TYPE.........................................................................................................................................116
4 Other Alarm Clearing...............................................................................................................118

4.1 AD_CHECK_FAIL........................................................................................................................................126
4.2 ALM_ALS......................................................................................................................................................127
4.3 ALM_GFP_dCSF...........................................................................................................................................127
4.4 ALM_HANGUP.............................................................................................................................................128
4.5 APS_FAIL......................................................................................................................................................129
4.6 APS_MANUAL_STOP..................................................................................................................................130
4.7 B1_SD............................................................................................................................................................131
4.8 B2_EXC..........................................................................................................................................................133
4.9 B2_SD............................................................................................................................................................135
4.10 B3_EXC........................................................................................................................................................137
4.11 B3_EXC_VC3..............................................................................................................................................138
4.12 B3_EXC_VC4..............................................................................................................................................140
4.13 B3_SD..........................................................................................................................................................142
4.14 B3_SD_VC3.................................................................................................................................................144
4.15 B3_SD_VC4.................................................................................................................................................145
4.16 BD_NOT_INSTALLED..............................................................................................................................147
4.17 BDID_ERROR.............................................................................................................................................148
4.18 BEFFEC_EXC..............................................................................................................................................149
4.19 BOOTROM_BAD........................................................................................................................................150
4.20 C2_VCAIS....................................................................................................................................................151
Issue 01 (2012-05-30) Huawei Proprietary and Confidential vi

4.21 CHIP_ABN...................................................................................................................................................152
4.22 DB_RESTORE_FAIL..................................................................................................................................153
4.23 DBMS_ERROR............................................................................................................................................154
4.24 DBMS_PROTECT_MODE.........................................................................................................................155
4.25 DLAG_PROTECT_FAIL............................................................................................................................156
4.26 DSP_LOAD_FAIL.......................................................................................................................................158
4.27 ETH_CFM_LOC..........................................................................................................................................158
4.28 ETH_CFM_MACSTATUS..........................................................................................................................160
4.29 ETH_CFM_MISMERGE.............................................................................................................................161
4.30 ETH_CFM_RDI...........................................................................................................................................163
4.31 ETH_CFM_UNEXPERI..............................................................................................................................164
4.32 ETHOAM_DISCOVER_FAIL....................................................................................................................166
4.33 ETHOAM_RMT_LOOP..............................................................................................................................168
4.34 ETHOAM_RMT_SD...................................................................................................................................169
4.35 ETHOAM_SELF_LOOP.............................................................................................................................170
4.36 ETHOAM_VCG_SELF_LOOP...................................................................................................................171
4.37 EX_ETHOAM_CC_LOS.............................................................................................................................172
4.38 EX_ETHOAM_MPID_CNFLCT................................................................................................................174
4.39 EXT_TIME_LOC.........................................................................................................................................175
4.40 FAN_FAIL...................................................................................................................................................176
4.41 FAN_FAULT...............................................................................................................................................177
4.42 FEATURE_WITHOUT_LICENSE.............................................................................................................178
4.43 FEC_LOF.....................................................................................................................................................180
4.44 FEC_OOF.....................................................................................................................................................181
4.45 FPGA_ABN..................................................................................................................................................182
4.46 FSELECT_STG............................................................................................................................................183
4.47 FWD_PKT_LO............................................................................................................................................184
4.48 GAINDATA_MIS........................................................................................................................................185
4.49 HARD_ERR.................................................................................................................................................185
4.50 HP_LOM......................................................................................................................................................188
4.51 HP_RDI........................................................................................................................................................189
4.52 HP_REI.........................................................................................................................................................190
4.53 HP_SLM.......................................................................................................................................................191
4.54 HP_TIM........................................................................................................................................................193
4.55 HP_UNEQ....................................................................................................................................................194
4.56 HSC_UNAVAIL..........................................................................................................................................196
4.57 IN_PWR_FAIL............................................................................................................................................197
4.58 J0_MM..........................................................................................................................................................199
4.59 K1_K2_M.....................................................................................................................................................199
4.60 K2_M............................................................................................................................................................200
4.61 LAG_PORT_FAIL.......................................................................................................................................201
4.62 LAN_LOC....................................................................................................................................................203
Issue 01 (2012-05-30) Huawei Proprietary and Confidential vii

4.63 LASER_HAZARD_WARNING..................................................................................................................204
4.64 LASER_MODULE_MISMATCH...............................................................................................................205
4.65 LASER_SHUT.............................................................................................................................................206
4.66 LCAS_FOPR................................................................................................................................................207
4.67 LCAS_FOPT................................................................................................................................................208
4.68 LCAS_PLCR................................................................................................................................................209
4.69 LCAS_PLCT................................................................................................................................................210
4.70 LCAS_TLCR................................................................................................................................................211
4.71 LCAS_TLCT................................................................................................................................................213
4.72 LCS_DAYS_OF_GRACE...........................................................................................................................214
4.73 LCS_EXPIRED............................................................................................................................................216
4.74 LCS_FILE_NOT_EXIST.............................................................................................................................219
4.75 LOCK_CUR_FAIL......................................................................................................................................221
4.76 LOCKPOW_MIS.........................................................................................................................................222
4.77 LP_RDI_VC3...............................................................................................................................................223
4.78 LP_SLM_VC3..............................................................................................................................................223
4.79 LP_UNEQ_VC3...........................................................................................................................................224
4.80 LPT_RFI.......................................................................................................................................................225
4.81 LSR_COOL_ALM.......................................................................................................................................226
4.82 LSR_INVALID............................................................................................................................................227
4.83 MS_APS_INDI_EX.....................................................................................................................................228
4.84 MS_RDI........................................................................................................................................................230
4.85 MS_REI........................................................................................................................................................231
4.86 MSSW_DIFFERENT...................................................................................................................................231
4.87 MULTI_RPL_OWNER................................................................................................................................233
4.88 MUT_LOS....................................................................................................................................................234
4.89 NEBD_XC_DIF...........................................................................................................................................235
4.90 NESF_LOST................................................................................................................................................236
4.91 NESTATE_INSTALL..................................................................................................................................237
4.92 NO_BD_PARA............................................................................................................................................238
4.93 NO_BD_SOFT.............................................................................................................................................239
4.94 NO_ELABEL...............................................................................................................................................240
4.95 NODEID_MM..............................................................................................................................................241
4.96 OA_LOW_GAIN.........................................................................................................................................242
4.97 ODU_AIS.....................................................................................................................................................244
4.98 ODU_LCK....................................................................................................................................................245
4.99 ODU_OCI.....................................................................................................................................................246
4.100 OH_LOOP..................................................................................................................................................247
4.101 OMS_BDI...................................................................................................................................................248
4.102 OMS_BDI_O..............................................................................................................................................248
4.103 OMS_BDI_P..............................................................................................................................................250
4.104 OMS_FDI...................................................................................................................................................251
Issue 01 (2012-05-30) Huawei Proprietary and Confidential viii

4.105 OMS_FDI_O..............................................................................................................................................252
4.106 OMS_FDI_P...............................................................................................................................................253
4.107 OMS_SSF...................................................................................................................................................255
4.108 OMS_SSF_O..............................................................................................................................................256
4.109 OMS_SSF_P...............................................................................................................................................257
4.110 OOL............................................................................................................................................................258
4.111 OPA_FAIL_INDI.......................................................................................................................................259
4.112 OTU_AIS....................................................................................................................................................260
4.113 OTU_LOF..................................................................................................................................................261
4.114 OTU_LOM.................................................................................................................................................262
4.115 OUT_PWR_ABN.......................................................................................................................................263
4.116 PATCH_ACT_TIMEOUT.........................................................................................................................264
4.117 PATCH_DEACT_TIMEOUT....................................................................................................................265
4.118 PATCH_ERR.............................................................................................................................................266
4.119 PATCH_NOT_CONFIRM.........................................................................................................................267
4.120 PATCH_PKGERR.....................................................................................................................................268
4.121 PATCHFILE_NOTEXIST.........................................................................................................................268
4.122 PORT_MODULE_OFFLINE....................................................................................................................269
4.123 PM_BDI......................................................................................................................................................270
4.124 PM_BEI......................................................................................................................................................271
4.125 PM_BIP8_OVER.......................................................................................................................................272
4.126 PM_BIP8_SD.............................................................................................................................................273
4.127 PM_TIM.....................................................................................................................................................275
4.128 PUM_BCM_ALM......................................................................................................................................275
4.129 PUM_TEM_ALM......................................................................................................................................277
4.130 PUMP_COOL_EXC..................................................................................................................................278
4.131 R_LOC........................................................................................................................................................279
4.132 RELAY_ALARM_CRITICAL..................................................................................................................280
4.133 RELAY_ALARM_IGNORE.....................................................................................................................281
4.134 RELAY_ALARM_MAJOR.......................................................................................................................281
4.135 RELAY_ALARM_MINOR.......................................................................................................................282
4.136 RTC_FAIL..................................................................................................................................................283
4.137 S1_SYN_CHANGE...................................................................................................................................284
4.138 SECU_ALM...............................................................................................................................................285
4.139 SERVICE_CAPACITY_EXCEED_LICENSE.........................................................................................286
4.140 SERVICE_TYPE_EXCEED_LICENSE...................................................................................................287
4.141 SHELF_AREA_POWER_OVER..............................................................................................................288
4.142 SLAVE_WORKING..................................................................................................................................289
4.143 SM_BDI......................................................................................................................................................290
4.144 SM_BEI......................................................................................................................................................291
4.145 SM_BIP8_OVER.......................................................................................................................................292
4.146 SM_BIP8_SD.............................................................................................................................................293
Issue 01 (2012-05-30) Huawei Proprietary and Confidential ix

4.147 SM_IAE......................................................................................................................................................294
4.148 SM_TIM.....................................................................................................................................................295
4.149 SNCP_FAIL...............................................................................................................................................296
4.150 SO_SK_MISMATCH................................................................................................................................297
4.151 STORM_CUR_QUENUM_OVER............................................................................................................298
4.152 SUBRACK_ID_CONFLICT......................................................................................................................299
4.153 SUBRACK_ID_MISMATCH....................................................................................................................300
4.154 SUBRACK_LOOP.....................................................................................................................................301
4.155 SUBRACK_TYPE_MISMATCH..............................................................................................................301
4.156 SUM_INPWR_HI......................................................................................................................................302
4.157 SUM_INPWR_LOW..................................................................................................................................303
4.158 SWDL_ACTIVATED_TIMEOUT............................................................................................................304
4.159 SWDL_AUTOMATCH_INH....................................................................................................................305
4.160 SWDL_CHGMNG_NOMATCH...............................................................................................................306
4.161 SWDL_COMMIT_FAIL............................................................................................................................307
4.162 SWDL_INPROCESS.................................................................................................................................308
4.163 SWDL_NEPKGCHECK............................................................................................................................309
4.164 SWDL_PKG_NOBDSOFT........................................................................................................................309
4.165 SWDL_PKGVER_MM..............................................................................................................................310
4.166 SWDL_ROLLBACK_FAIL......................................................................................................................311
4.167 SYNC_DISABLE.......................................................................................................................................312
4.168 SYNC_F_M_SWITCH..............................................................................................................................312
4.169 SYNC_FAIL...............................................................................................................................................314
4.170 SYN_LOCKOFF........................................................................................................................................315
4.171 SYSPARA_CFDB_NOSAME...................................................................................................................316
4.172 T_LOSEX...................................................................................................................................................317
4.173 TD...............................................................................................................................................................318
4.174 TEM_HA....................................................................................................................................................319
4.175 TEM_LA....................................................................................................................................................320
4.176 TEST_STATUS..........................................................................................................................................321
4.177 TF................................................................................................................................................................322
4.178 THUNDERALM........................................................................................................................................322
4.179 TIME_LOS.................................................................................................................................................324
4.180 TIME_NO_TRACE_MODE......................................................................................................................325
4.181 TR_LOC.....................................................................................................................................................326
4.182 TU_AIS_VC3.............................................................................................................................................328
4.183 TU_LOP_VC3............................................................................................................................................329
4.184 VCAT_LOA...............................................................................................................................................330
4.185 VCAT_LOM_VC3.....................................................................................................................................331
4.186 VCAT_LOM_VC4.....................................................................................................................................332
4.187 VOA_ADJUST_FAIL................................................................................................................................333
4.188 W_R_FAIL.................................................................................................................................................334
Issue 01 (2012-05-30) Huawei Proprietary and Confidential x

4.189 WAVEDATA_MIS....................................................................................................................................335
4.190 XC_UNSWITCH........................................................................................................................................336
5 Performance Event List.............................................................................................................338

5.1 Performance Events by Type..........................................................................................................................339
5.1.1 Pointer Justification Performance Event List........................................................................................339
5.1.2 Regenerator Section Performance Event List........................................................................................340
5.1.3 Multiplex Section Bit Error Performance Event List............................................................................340
5.1.4 Higher Order Path Bit Error Performance Event List...........................................................................341
5.1.5 Lower Order Path Bit Error Performance Event List............................................................................342
5.1.6 FEC Service Performance Event List....................................................................................................342
5.1.7 TCM Performance Event List................................................................................................................343
5.1.8 Laser Performance Event List...............................................................................................................343
5.1.9 Board Status Performance Event List....................................................................................................347
5.1.10 RMON performance entries................................................................................................................347
5.2 Board Performance Event List.......................................................................................................................352
5.2.1 N1EGSH................................................................................................................................................352
5.2.2 N1SF64A...............................................................................................................................................354
5.2.3 N3SLH41...............................................................................................................................................355
5.2.4 N4BPA...................................................................................................................................................355
5.2.5 N4SF64..................................................................................................................................................355
5.2.6 N4SFD64...............................................................................................................................................356
5.2.7 N4SL64..................................................................................................................................................357
5.2.8 N4SLD64...............................................................................................................................................358
5.2.9 N4SLO16...............................................................................................................................................358
5.2.10 N4SLQ16.............................................................................................................................................359
5.2.11 N4SLQ64.............................................................................................................................................359
5.2.12 TN11CRPC..........................................................................................................................................360
5.2.13 TN12OAU1.........................................................................................................................................360
5.2.14 TN12OBU1.........................................................................................................................................361
5.2.15 TN52STG............................................................................................................................................361
5.2.16 TNL2SXCM........................................................................................................................................361
6 Performance Event Clearing....................................................................................................362

6.1 Performance Event Clearing of SDH.............................................................................................................363
6.1.1 AUPJCHIGH.........................................................................................................................................363
6.1.2 AUPJCLOW..........................................................................................................................................364
6.1.3 AUPJCNEW..........................................................................................................................................365
6.1.4 BCV.......................................................................................................................................................366
6.1.5 CCV.......................................................................................................................................................367
6.1.6 EDTMP..................................................................................................................................................368
6.1.7 EDRPL...................................................................................................................................................369
6.1.8 EDTPL...................................................................................................................................................370
6.1.9 FEC_AFT_COR_ER.............................................................................................................................371
Issue 01 (2012-05-30) Huawei Proprietary and Confidential xi

6.1.10 FEC_AFT_COR_ERAVR...................................................................................................................372
6.1.11 FEC_BEF_COR_ER...........................................................................................................................373
6.1.12 FEC_BEF_COR_ERAVR...................................................................................................................374
6.1.13 FEC_COR_0BIT_CNT.......................................................................................................................375
6.1.14 FEC_COR_1BIT_CNT.......................................................................................................................376
6.1.15 FEC_COR_BYTE_CNT.....................................................................................................................377
6.1.16 FEC_UNCOR_BLOCK_CNT............................................................................................................377
6.1.17 HPBBE................................................................................................................................................378
6.1.18 HPES...................................................................................................................................................379
6.1.19 HPFEBBE............................................................................................................................................380
6.1.20 HPFEES...............................................................................................................................................382
6.1.21 HPFESES.............................................................................................................................................383
6.1.22 HPFEUAS...........................................................................................................................................384
6.1.23 HPSES.................................................................................................................................................385
6.1.24 HPUAS................................................................................................................................................386
6.1.25 LSBIAS...............................................................................................................................................387
6.1.26 LSIOP..................................................................................................................................................388
6.1.27 LSOOP.................................................................................................................................................390
6.1.28 LSTMP................................................................................................................................................391
6.1.29 MSBBE................................................................................................................................................392
6.1.30 MSES...................................................................................................................................................393
6.1.31 MSFEBBE...........................................................................................................................................394
6.1.32 MSFEES..............................................................................................................................................395
6.1.33 MSFESES............................................................................................................................................396
6.1.34 MSFEUAS...........................................................................................................................................397
6.1.35 MSSES.................................................................................................................................................398
6.1.36 MSUAS...............................................................................................................................................400
6.1.37 ODU2PMBIP8.....................................................................................................................................401
6.1.38 OSPITMPMIN.....................................................................................................................................402
6.1.39 OSPITMPMAX...................................................................................................................................403
6.1.40 OSPITMPCUR....................................................................................................................................404
6.1.41 OSPICCVMIN.....................................................................................................................................404
6.1.42 OSPICCVMAX...................................................................................................................................405
6.1.43 OSPICCVCUR....................................................................................................................................406
6.1.44 OTU2SMBIP8.....................................................................................................................................407
6.1.45 RSBBE.................................................................................................................................................408
6.1.46 RSES....................................................................................................................................................410
6.1.47 RSOFS.................................................................................................................................................411
6.1.48 RSOOF................................................................................................................................................412
6.1.49 RSSES.................................................................................................................................................413
6.1.50 RSUAS................................................................................................................................................414
6.1.51 RPLMIN..............................................................................................................................................415
Issue 01 (2012-05-30) Huawei Proprietary and Confidential xii

6.1.52 RPLMAX.............................................................................................................................................416
6.1.53 RPLCUR..............................................................................................................................................417
6.1.54 SUMIOP..............................................................................................................................................418
6.1.55 SUMOOP.............................................................................................................................................419
6.1.56 TPLMIN..............................................................................................................................................421
6.1.57 TPLMAX.............................................................................................................................................422
6.1.58 TPLCUR..............................................................................................................................................423
6.1.59 TLBMIN..............................................................................................................................................424
6.1.60 TLBMAX............................................................................................................................................425
6.1.61 TLBCUR.............................................................................................................................................425
6.1.62 WCV....................................................................................................................................................426
6.1.63 XCSTMP.............................................................................................................................................427
6.2 Performance Threshold-Crossing Event Clearing of RMON.........................................................................428
6.2.1 ETHDROP.............................................................................................................................................429
6.2.2 ETHUNDER..........................................................................................................................................429
6.2.3 ETHOVER.............................................................................................................................................431
6.2.4 ETHFRG................................................................................................................................................432
6.2.5 ETHJAB................................................................................................................................................433
6.2.6 ETHFCS................................................................................................................................................434
6.2.7 RXPAUSE.............................................................................................................................................435
6.2.8 TXPAUSE.............................................................................................................................................435
7 Abnormal Event List.................................................................................................................437

8 Handling Abnormal Events.....................................................................................................438
8.1 Linear Multiplex Section Protection Switching.............................................................................................439
8.2 SNCP Switching.............................................................................................................................................441
8.3 1+1 Equipment-Level Protection Switching..................................................................................................442
8.4 RMON Performance Value Above the Upper Threshold ..............................................................................444
8.5 RMON Performance Value Below the Lower Threshold..............................................................................445
A Glossary......................................................................................................................................447
Issue 01 (2012-05-30) Huawei Proprietary and Confidential xiii

OptiX OSN 9560 Intelligent Optical Switching System 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
1 Generation of Alarms and Performance

Events of SDH Services
About This Chapter
This topic describes the generation and detection of SDH higher order and lower order signal
flows, and suppression correlation between SDH alarms.
NOTE
The OptiX OSN 9560 cannot directly receive and transmit higher and lower order services. This topic
describes lower order bit errors and tributary boards related to the equipment that is interconnected with
the OptiX OSN 9560 and can receive and transmit higher and lower order services.
1.1 Overview
There are sufficient overhead bytes in SDH frames, including regenerator section overheads,
multiplex section overheads, and path overheads. These overhead bytes carry alarm and
performance information. According to the information, the SDH system can monitor alarms
and bit errors in real time. With an understanding of the alarm generation and detection
principles, you can quickly identify faults.
1.2 Generation and Detection of Alarms and Performance Events in the SDH Higher Order
Signal Flow
The principle for locating faults is "line first, then tributary; high level first, then low
level". Therefore, this section focuses only on the alarms and performance events generated
between the SDH interface and the cross-connect unit during maintenance.
1.3 Suppression Correlation Between SDH Alarms
The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This section describes the suppression relationships among SDH alarms.
1.4 Generation and Detection of SDH Performance Events
The performance events of an SDH network include bit errors and jitter. Jitter can result in
pointer justification on the equipment. Therefore, it is the key factor that influences the
transmission quality of the SDH network.
Issue 01 (2012-05-30) Huawei Proprietary and Confidential 1

1.1 Overview
There are sufficient overhead bytes in SDH frames, including regenerator section overheads,
multiplex section overheads, and path overheads. These overhead bytes carry alarm and
performance information. According to the information, the SDH system can monitor alarms
and bit errors in real time. With an understanding of the alarm generation and detection
principles, you can quickly identify faults.
Figure 1-1 shows the SDH alarm signal flow.
Figure 1-1 SDH alarm signal flow
SPI RST MST MSA HPT HPA LPT

LOS
"1"
(A1,A2) LOF
J0_MM AIS
(J0)
RS_BIP Err.
(B1)
MS_AIS "1"
(K2) AIS
MS_BIP Err.
(B2)
MS_REI
(M1)
MS_RDI
(K2)
AU_AIS "1"
(H1,H2,H3)
AU_LOP
(H1,H2)
HP_SLM, HP_UNEQ "1"
(C2)
HP_TIM
(J1) AIS
HP_BIP Err.
(B3)
HP_REI
(G1)
HP_RDI
(G1)
TU_AIS "1"
(V1,V2,V3)
TU_LOP
(V1,V2)
HP_LOM
(H4)
LP_UNEQ "1"
(V5)
LP_TIM
(J2)
LP_BIP Err. AIS
(V5)
LP_REI
(V5)
LP_RDI
(V5)
"1"
LP_SLM AIS
(V5)
Indicates that the corresponding alarm or signal is generated

Indicates that the corresponding alarm is detected
1.1.1 Directions and Levels of Signal Flows

This topic describes basic concepts, including the uplink signal flow, downlink signal flow,
higher order path, and lower order path, involved in signal analysis.

Term Description Figure
Downlink The signal flow is as follows:

signal SDH port → cross-connect unit SDH SDH
flow → lower order SDH port or port

Cross-connect
port
unit
Ethernet port.
PDH port
Downlink signal flow
Uplink The signal flow is as follows:

signal lower order SDH port or Ethernet SDH
port Cross-connect
SDH
port
Uplink
flow port → cross-connect unit → unit signal flow
higher order SDH port. PDH port
Higher The signal between the SDH port Higer order part
order and the cross-connect unit is the

signal higher order signal flow. SDH
port
Cross-connect
SDH
port
flow unit
PDH port
Lower The signal between the cross-

order connect unit and the SDH port or SDH
port
Cross-connect
SDH
port
signal Ethernet port is the lower order unit
flow signal flow. PDH port
Lower order part
1.1.2 Two Common Alarms

This section describes two common alarms: alarm indication signal (AIS) and remote defect
indication (RDI).
Alarm Description
AIS When an AIS alarm is reported, the system inserts all 1s into the
lower-level circuits to indicate that the signal is unavailable. The
MS_AIS, AU_AIS, TU_AIS, E1_AIS, and T1_AIS alarms are
common AIS alarms.
RDI When detecting the loss of signal (LOS), AIS, or trace identifier
mismatch (TIM) alarm, the opposite NE sends the RDI alarm to
the local NE.
The MS_RDI, HP_RDI, and LP_RDI alarms are common RDI
alarms.

NOTE
The generation of an alarm on an NE does not necessarily indicate that the NE is faulty. The alarm may
be generated due to a fault on the opposite NE or due to other causes.
For example, the R_LOS alarm is generated due to a fiber cut, or the HP_LOM alarm is generated on the
local NE due to the failure in the cross-connect unit on the opposite NE.
1.1.3 Alarm Management

This section describes the alarm reporting process.
Alarms are reported in the following cases:
l A board detects alarms and reports them to the NE software.

l The NE software reports alarms to the NMS server.
l A user queries alarms on the NMS server using an NMS client.
In the entire process, alarms are saved on the NMS after the following processing steps:
l Alarm masking
l Automatic alarm reporting
l Alarm filtering
In addition, alarm reversion and alarm suppression affect alarm reporting.
Alarm Masking
The alarm masking function can be enabled for all alarms on an NE or a board on an NE. When
an alarm is masked, the corresponding NE or board does not monitor this alarm.
Automatic Alarm Reporting

After automatic alarm reporting is enabled on an NE, an alarm on the NE is reported to the NMS
immediately after this alarm is generated. Then, an alarm panel is displayed on the NMS. A user
can view the alarm information in the alarm panel. A user can disable this function for certain
alarms. This reduces the impact of a large number of alarms on the NMS performance.
Alarm Filtering
Alarm filtering is implemented on the NMS, and does not affect alarms on NEs. The NMS
accepts or discards reported alarms based on the alarm filtering configuration. If alarm filtering
is enabled for an alarm on an NE, the NMS discards the alarm and does not save it into the alarm
database. If alarm filtering is disabled for an alarm on an NE, the NMS accepts the alarm and
saves it into the alarm database.
Alarm Suppression
Lower-level alarms usually derive from a root alarm that is directly triggered by an exception
or fault. These lower-level alarms make fault locating and handling difficult. Alarm correlation
can be configured to suppress non-root alarms. Then, fewer alarms are reported to the NMS,
and faults can be identified and rectified quickly.

Alarm Reversion
For ports that are not configured with services, the alarm reversion function can be used to
prevent alarms from being generated. This prevents interference from alarms.
When the alarm reversion function is enabled on a port, the alarm status of this port is opposite
to the actual status. That is, no alarm is reported when an alarm is generated and an alarm is
reported when no alarm is generated.
There are three alarm reversion modes: non-reversion, automatic reversion, and manual
reversion.
l Non-reversion
This mode indicates the normal alarm monitoring state and is the default mode. In this
mode, the alarm reversion function cannot be enabled on a port.
l Automatic reversion
In this mode, the alarm reversion function can be enabled only on a port that reports alarms.
After the alarm reversion function is enabled, the port does not report any alarms. When
the current alarms are cleared, the port automatically exits the reversion mode and the alarm
status reported by the port is restored to the actual alarm status.
l Manual reversion
In this mode, the alarm reversion function can be enabled on a port regardless of whether
any alarms are reported at this port.
– When the alarm reversion function is enabled on a port, the alarm status reported by the
port is opposite to the actual alarm status.
– When the alarm reversion function is disabled on a port, the alarm status reported by
the port is the same as the actual alarm status.
Take the following precautions when configuring the alarm reversion function:
l After alarm reversion is enabled on a port on a board, the alarm status of the board, including
the status of the alarm indicators on the board, remains unchanged and indicates the running
status of the board.
l The alarm reversion function is implemented by the NE software. The alarm data on the
NE is the same as the alarm data on the NMS. The alarm data indicates the alarm status
after alarm reversion is implemented.
1.2 Generation and Detection of Alarms and Performance

Events in the SDH Higher Order Signal Flow
The principle for locating faults is "line first, then tributary; high level first, then low
level". Therefore, this section focuses only on the alarms and performance events generated
between the SDH interface and the cross-connect unit during maintenance.
Generally, the alarms and performance events that are generated in the higher order paths cause
lower order alarms and performance events. Figure 1-2 shows the signal flow between the SDH
interface and the cross-connect unit.

Figure 1-2 Alarm signals generated between the SDH interface and the cross-connect unit
Frame synchronizer MS overhead Pointer processor and HP
and RS overhead processor overhead processor
processor
(RST) (MST) (MSA, HPT)
LOS "1" AIS "1" AIS

STM-N AU-AIS
optical MS-AIS H1,H2
A1, LOF AU-LOP
interface K2 H1,H2
A2 HP-TIM
B2-Err. J1 "1"
B2 HP-UNEQ
C2 Cross-connect
BI Err. MS-REI HP-SLM unit
B1 M1 C2
H4 HP-LOM
MS-RDI
k2 B3 Err.
B3
HP-REI
G1
HP-RDI
G1
Downlink signal flow Alarm report or return
Signal transfer point Alarm termination point

(Insert all "1"s signal) (Report to SCC unit)
Based on the positions of the various overhead bytes in the STM-1 frame, the overhead bytes
are classified into the following four modules:
l Regenerator section overheads

l Multiplex section overheads
l Higher order path overheads
In normal cases, a fault in the first two modules affects all the higher order paths. A fault in the
higher order overhead bytes, however, affects higher order paths.
The following sections describe the signal flow and the processing of overhead bytes.
1.2.1 Downstream Signal Flow

In the higher order downstream signal flow, overhead bytes are extracted and terminated.
Frame Synchronizer and Regenerator Section Overhead Processor

In the regenerator section (RS), the overhead bytes that are related to alarms and performance
events are as follows:
l Framing bytes (A1, A2)

l Regenerator section trace byte (J0)
l RS bit interleaved parity (BIP-8) code byte (B1)
The alarm signal flow is as follows:
l In the receive direction

When the STM-N optical signal from a line enters the optical receiving module of a line
board, the signal is first converted into an electrical signal through the optical/electrical
conversion (O/E conversion) module. It is then sent to a frame synchronizer and an
unscrambler for processing. During this process, the O/E conversion module continuously
checks the signal. An R_LOS alarm is reported if the following faults are detected:

– No signal is input.
– The optical power is low or high.
– The code type of the input signal does not match the original one.
The R_LOS alarm persists on the SDH equipment, until the optical receiving module of
the local station detects the correct code pattern and at the same time no new R_LOS alarm
is detected.
When an R_LOS alarm occurs, the system inserts an all "1"s signal into the lower level
circuits.
l Detecting the A1, A2 and J0 bytes
After receiving an STM-N signal from the O/E conversion module, the frame synchronizer
captures the frame alignment signal through the A1 and the A2 bytes in the signal.
Meanwhile, the frame synchronizer extracts the line reference synchronization clock source
from the signal and sends it to the clock board for locking the clock.
Normally, the A1 value is always "F6H", and the A2 value is always "28H". If incorrect
A1 or A2 values are detected in five consecutive frames, an R_OOF alarm occurs. If the
R_OOF alarm lasts for more than 3 ms, an R_LOF alarm occurs, and an all "1"s signal is
inserted. If the framing state lasts for more than 1 ms after the R_LOF alarm occurs, the
equipment returns to normal.
The J0 byte is used to verify if the two ends of the regenerator section are permanently
connected to each other. For an NE, the J0 byte received and the J0 byte to be received
must match. Otherwise, the equipment reports a trace identifier mismatch alarm (J0_MM).
An unscrambler is used to unscramble all the bytes except A1, A2, J0, and the two bytes
that follow the J0 bytes in the STM-N signals.
l Detecting the B1 byte
The regenerator section overhead (RSOH) processor extracts and processes other RSOH
bytes in the STM-N signal. Among all the bytes, the B1 byte is the most important.
If the B1 byte recovered from an STM-N signal is not consistent with the BIP-8 computing
result of the preceding STM-N frame, B1 bit errors are reported.
– If the number of B1 bit errors exceeds the threshold 10-6 (which is the default value), a
B1_SD alarm occurs.
– If the number of B1 bit errors exceeds the threshold 10-3 (which is the default value), a
B1_EXC alarm occurs.
When there are ten consecutive severely errored seconds (SES, indicating a second in which
errored blocks reach a percentage of 30%) in the regenerator section, the regenerator section
unavailable time event (RSUAT) occurs.
The F1, D1-D3, and E1 bytes, which are irrelevant to alarms and performance events, are sent
to the SCC module and the overhead module.
Multiplex Section Overhead Processor

In the multiplex section (MS), the overhead bytes that are related to the alarms and the
performance events are as follows:
l Automatic protection switching bytes (K1, K2)
l MS bit interleaved parity code byte (B2)
l MS remote error indication (M1)
The signal flow is as follows:

l Detecting the K1 and the K2 bytes

The K2 byte (bits 6-8) is used to indicate a failure at the remote end of the MS.
– If the code of the bits 6-8 of the K2 byte is "111", an MS_AIS alarm is generated and
an all "1"s signal is inserted.
– If the code of the bits 6-8 of the K2 byte is "110", an MS_RDI alarm is generated.
The bytes K1 and K2 (bits 1-5) are used to transmit the automatic protection switching
(APS) protocol. The bytes K1 and K2 (bits 1-5) can work with the system control and
communication board and the cross-connect board to realize MSP.
l Detecting the B2 byte and the M1 byte
If the B2 byte recovered from the STM-N signal is not consistent with the BIP-24 computing
result of the preceding STM-N frame (all bits expect for the RSOH), B2 bit errors occur.
The M1 byte is used to check if an MS_REI alarm is reported. The M1 byte carries the
error count of the interleaved bit blocks that the B2 byte has detected.
– If B2 bit errors exceed the threshold 10-6 (default), a B2_SD alarm is generated.
– If B2 bit errors exceed the threshold 10-3 (default), a B2_EXC alarm is generated.
In the multiplex section protection mode, the B2_EXC and the B2_SD (if enabled) alarms
can trigger the MSP switching.
If the B2 byte detects SES for 10 consecutive seconds, the multiplex section unavailable
time (MSUAT) event occurs.
Pointer Processor and Higher Order Path Overhead Processor

The bytes that are related to pointer justifications are H1, H2 and H3. The bytes that are related
to alarms and bit errors are as follows:
l Higher order path trace byte (J1)
l Signal label byte (C2)
l Higher order path bit interleaved parity code (path BIP-8) byte (B3)
l Path status byte (G1)
l Multiframe indicator byte (H4)
The alarm signal flow is as follows:
l Detecting the H1 and H2 bytes
The pointer processor interprets and justifies the pointer on the basis of the H1 and H2 bytes
in each AU-4. It achieves frequency and phase alignment. The pointer processor also locates
each VC-4 and transmits them to the corresponding higher order path overhead processor.
NOTE
H3 bytes tolerate phase jitter and wander in the network.

If the H1 and the H2 bytes of the AU pointer are detected to be all "1"s, an AU_AIS alarm
is reported and an all "1"s signal is inserted. If the pointer values of H1 and H2 are illegal
(beyond the normal range, which is from 0 to 782) and illegal pointers are received in eight
consecutive frames, an AU_LOP alarm is reported and an all "1"s signal is inserted.
If the AU pointer justification is positive, the number of PJCHIGHs of the multiplex section
adaptation (MSA) increases by one. If the AU pointer justification is negative, the number
of PJCLOWs of the MSA increases by one.
l Detecting the J1, C2, B3, G1 and H4 bytes

The higher order path overhead processor processes higher order path overhead (HPOH)
bytes in the received NxVC-4s. The mode for processing each byte is described as follows:
If the J1 byte value detected is not the same as the preset value, an HP_TIM alarm is reported
and an all "1"s signal is inserted.
If the C2 byte is detected as 00, an HP_UNEQ alarm is reported and an all "1"s signal is
inserted.
NOTE
In the case of the Huawei OSN series equipment, you can use the NMS to set whether the all "1"s
signal is inserted when the HP_TIM, HP_UNEQ alarm occurs. By default, the all "1"s signal is not
inserted.
Currently, the tributary unit group (TUG) is adopted as the payload structure in China. The
preset C2 value that corresponds to the TUG structure is "02".
If the B3 byte restored from the HPOH is not consistent with the BIP-8 computing result
of the VC-4 signal of the preceding frame, B3 bit errors are reported.
In the STM-N lower order SDH interface board, the TU-12 signal extracted from VC-4s
requires the H4 byte to indicate the frame number of the current multiframe in which the
current TU-12 is placed. If the H4 byte detected is illegal, an HP_LOM alarm is reported.
If bit 5 of the G1 byte is "1", an HP_RDI alarm is reported. The value of bits 1-4 of the G1
byte determines if an HP_REI alarm is reported. If the value of bits 1-4 of the G1 byte is
1-8, an HP_REI alarm is reported.
When B3 detects SES for 10 consecutive seconds, an HPUAT EVENT performance event
occurs.
Other overhead bytes such as the F3, K3 and N1 are reserved for future use.
Finally, the NxSTM-1 payloads are transmitted to the cross-connect unit for the cross connection
of the higher order path and the lower order path.
1.2.2 Upstream Signal Flow

The overhead bytes are extracted and then terminated in the downstream signal flow of the higher
order path. Generating overhead bytes and returning alarm signals to the opposite NE are
completed in the upstream signal flow of the higher order path.
Pointer Processor and Higher Order Path Overhead Processor

N x STM-1 payload signals from the cross-connect unit are first sent to higher order path
overhead processor.
The higher order path overhead processor generates N x higher order path overhead bytes, which
are sent to the pointer processor with the N x STM-1 payloads. The setting of higher order path
overhead bytes such as the J1, C2, B3, G1, F2, F3 and N1 can be completed along the upstream
direction.
If an AU_AIS, an AU_LOP or a HP_UNEQ alarm is detected in the downstream signal flow,

bit b5 of the G1 byte is set to "1", and an HP_RDI alarm is reported to the remote end. If B3 bit
errors are detected in the downstream signal, bits 1-4 of the G1 byte are set to a corresponding
bit error value (ranging 1-8) based on the detected error value, and an HP_REI alarm is reported
to the remote end.
The H4 byte is not processed in the upstream direction.

The pointer processor generates N x AU-4 pointers, and adapts the VC-4 into an AU-4 (H1 and
H2 bytes). The N x AU-4s are then multiplexed into an STM-N signal by using the multiplexing
processor and are sent to the MSOH processor.
Multiplex Section Overhead Processor

The multiplex section overhead processor sets the MSOH bytes such as the K1, K2, D4-D12,
S1, M1, E2 and B2 for the received STM-N signal.
If an R_LOS, an R_LOF or an MS_AIS alarm is detected in the downstream signal flow, bits
6-8 of the K2 byte are set to "110", and an MS_RDI alarm is reported to the remote end.
If B2 bit errors are detected in the downstream signal flow, an MS_REI alarm is reported to the
remote end through the M1 byte.
Frame Synchronizer and Regenerator Section Overhead Processor

The RSOH processor sets the overhead bytes, such as the A1, A2, J0, E1, F1, D1-D3 and B1,
in the regenerator section and sends a complete STM-N electrical signal to the frame
synchronizer and scrambler.
After being scrambled by the frame synchronizer and scrambler, the STM-N electrical signal is
converted into an STM-N optical signal by the E/O module and then sent out of the optical
interface.
1.3 Suppression Correlation Between SDH Alarms

The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This section describes the suppression relationships among SDH alarms.
Alarms are correlative. An alarm may trigger another alarm, especially, a higher-level alarm
may trigger a lower-level alarm.
For example, an R_LOS alarm occurs on an optical interface unit due to optical route faults. The
R_LOS alarm then inserts an AIS signal to the downstream circuit. As a result, all overhead
bytes change to all-1s, and alarms such as MS_AIS and AU_AIS are triggered. You do not need
to handle the downstream alarms that are triggered by the R_LOS alarm.
In addition, if all these alarms are reported simultaneously, the NMS and SCC board are heavily
loaded, and maintenance tasks are difficult.
To prevent the preceding situations, the OptiX OSN 9560 uses the alarm suppression function
to suppress some unnecessary alarms.
Figure 1-3 shows the suppression relationships of some major alarms.

Figure 1-3 Suppression of major alarms
R_LOS
R_LOF
MS_AIS
B1_EXC
B2_EXC AU_AIS
AU_LOP
B3_EXC HP_UNEQ HP_TIM HP_SLM
The higher-level alarms above the arrow mask the lower-level alarms below the arrow. This
mechanism allows maintenance engineers to focus only on higher-level alarms.
NOTE
There are suppression relationships between different-level alarms, but not between different-level
performance data because there is no causality between performance events. B2 bit errors will not be
triggered when B1 bit errors occur. The B2 bit error data is derived from calculating the contents in the
managed area.
1.4 Generation and Detection of SDH Performance Events

The performance events of an SDH network include bit errors and jitter. Jitter can result in
pointer justification on the equipment. Therefore, it is the key factor that influences the
transmission quality of the SDH network.
1.4.1 Bit Errors

Bit errors are detected through the parity check of B1, B2, B3 and V5 bytes.
Generation Mechanism
The SDH system adopts bit interleaved parity (BIP) to detect bit errors. The BIP is performed
on the BIP matrix of the regenerator section (RS), multiplex section (MS), higher order path,
and lower order path using the B1, B2, B3, and V5 bytes respectively.
The B1 byte is used for error monitoring in the RS. This function is performed by using a bit
interleaved parity 8 (BIP-8) code with even parity. The working mechanism of the B1 byte is
as follows:

1. At the transmit end, the BIP-8 is computed for all the scrambled bytes of the current frame
(frame N) and the result is stored in the B1 byte of the next frame (frame N+1) to be
scrambled.
2. At the receive end, the BIP-8 is computed for all bits of the current frame (frame N-1) to
be descrambled and the result is compared with the value of the B1 byte of the next
descrambled frame (frame N).
3. If the two values are different, exclusive-OR operation is conducted on them. The number
of "1"s in the result is the number of errored blocks in the frame during the transmission.
The B2 byte is used to error monitor in the MS, and the working mechanism is similar to that
of the B1 byte. The B1 byte monitors the errors that occur in the entire STM-N frame during the
transmission. One STM-N frame has only one B1 byte. The B2 byte monitors the errors that
occur in every STM-1 frame of the STM-N frame. The STM-N frame contains Nx3 B2 bytes.
Every three B2 bytes correspond to one STM-1 frame. For example, there are three B2 bytes for
one STM-1 frame. The working mechanism of the B2 byte is as follows:
1. At the transmit end, the BIP-24 is computed for all bits of the previous STM-1 frame except
the regenerator section overhead (RSOH), and the result is stored in the B2 bytes of the
current frame to be scrambled.
2. At the receive end, the BIP-24 is computed for all bits of the current descrambled STM-1
frame except the RSOH, and exclusive-OR operation is conducted between the parity result
and the B2 bytes in the next descrambled STM-1 frame.
3. The number of "1"s in the result of the exclusive-OR operation is the number of errored
blocks that occur in this STM-1 frame within the STM-N frame during the transmission.
A maximum of 24 errored blocks can be detected.
The B3 byte is used for monitoring the bit errors of the VC-4 or the 140 Mbit/s signal within the
STM-N frame during transmission. The monitoring mechanism of the B3 byte is similar to that
of the B1 and B2 bytes; however, it is used to perform the BIP-8 parity for the VC-4 frame.
The V5 byte performs the functions of error monitoring, signal labeling, and VC-12 path status
indicating. Bits 1-2 are used to perform the BIP-2 monitoring of bit errors in the VC-12 within
the STM-N frame. If the receive end detects errored blocks, the number of such blocks are
displayed in the performance events at the local end. At the same time, bit 3 of the V5 byte
reports the lower order path remote error indication (LP_REI) to the transmit end, and the
corresponding number of errored blocks are displayed in the performance events at the transmit
end.
Error Detection and Report

Figure 1-4 shows the error detection relationship and location.

Figure 1-4 Error detection relationship and location
LPT HPT MST RST RST MST HPT LPT
B1
B2
B3
V5
The modules in Figure 1-4 are defined as follows:
l RST is regenerator section termination.

l MST is multiplex section termination.
l HPT is higher order path termination.
l LPT is lower order path termination.
The B1, B2, B3 and V5 bit errors are monitored between these terminations. Figure 1-4 shows
that bit errors that occur in the lower order path cannot be detected in the higher order path, MS,
or RS. If bit errors occur in the RS, bit errors are triggered in the MS, higher order path, and
lower order path.
Generally, higher order bit errors can trigger lower order bit errors. If the B1 bit error occurs,
the B2, B3 and V5 bit errors are generated. If the V5 bit error occurs, B3, B2 and B1 bit errors
are not necessarily generated.
When the SDH system detects errors, it reports the error performance events or alarms, and
notifies the remote end of error detection through overhead bytes.
Terms
Table 1-1 lists the relevant terms.
Table 1-1 Bit error terms
Term Description
BE Block error. It indicates that one or more bits have errors.
BBE Background block error. It indicates an errored block occurring outside the period
of UAT and SES.
FEBBE Far end background block error. It indicates that a BBE event is detected at the
far end.

Term Description
ES Errored second. It indicates a certain second that is detected with one or more
errored blocks.
FEES Far end errored second. It indicates that an ES event is detected at the far end.
SES Severely errored second. It indicates a certain second, which contains more than
30% errored blocks or at least one serious disturbance period (SDP). The SDP is
a period of at least four consecutive blocks or 1 ms (taking the longer one) where
the error ratios of all the consecutive blocks are more than or equal to 10-2 or a
loss of signal occurs.
FESES Far end severely errored second. It indicates an SES event that is detected at the
far end.
CSES Consecutive severely errored second. It indicates the SES events that occur
consecutively, but last less than 10 seconds.
FECSES Far end consecutive severely errored second. It indicates a CSES event that is
detected at the far end.
UAS Unavailable second. A period of 10 consecutive seconds during which the bit
error ratio per second of the digital signal in either of the transmission directions
of a transmission system is inferior to 10-3. These 10 seconds are considered to
be part of the unavailable time.
Relationship with Alarms

Upon detecting errors, the local end of the SDH system reports an alarm or performance event,
and reports the error detection information to the remote end through overhead bytes. According
to the performance events or alarms reported from the local and remote ends, you can determine
the faulty section of the path or the signal directions where errors occur. Table 1-2 lists the
alarms and performance events related to bit errors.
Table 1-2 Alarms and performance events related to bit errors
Item Performance Event Alarm
If bit errors If bit errors If bit errors cross If bit errors exceed
cross the cross the the threshold at the threshold at the
threshold at threshold at the local end, the local end, the
the local the local end, local end reports opposite end
end, the the opposite the relevant reports the
local end end reports alarm. relevant alarm.
reports the the relevant
relevant event.
event.
Regener RSBBE - B1_SD/B1_EXC -

ator
section

Item Performance Event Alarm
If bit errors If bit errors If bit errors cross If bit errors exceed
cross the cross the the threshold at the threshold at the
threshold at threshold at the local end, the local end, the
the local the local end, local end reports opposite end
end, the the opposite the relevant reports the
local end end reports alarm. relevant alarm.
reports the the relevant
relevant event.
event.
Multiple MSBBE MSFEBBE B2_SD/B2_EXC MS_REI

x section
Higher HPBBE HPFEBBE B3_SD/B3_EXC HP_REI

order
path
If the B1 byte recovered from the STM-N signal is inconsistent with the BIP-8 computing result
of the previous STM-N frame, the B1 bit error occurs.
If the B2 byte recovered from the STM-N signal is inconsistent with the BIP-24 computing result
of the previous STM-N frame (all bits expect the RSOH), the B2 bit error occurs.
If the B3 byte recovered from the HPOH is inconsistent with BIP-8 computing result of the VC-4
signal of the previous frame, the B3 bit error occurs.
If B1, B2 and B3 bit errors cross the 10-6 threshold, alarms such as the B1_SD, B2_SD, B3_SD
occur. If B1, B2 and B3 bit errors cross the 10-3 threshold, alarms such as the B1_EXC, B2_EXC
and B3_EXC occur.
When B1 detects 10 consecutive SESs in the RS, it indicates that an RSUAT event occurs.
When B2 detects 10 consecutive SESs in the MS, it indicates that an MSUAT event occurs.
When B3 detects 10 consecutive SESs, it indicates that an HPUAT event occurs.
1.4.2 Pointer Justification

With the pointer justification, rate asynchronization and phase difference of payload signals are
allowed. The pointer justification adjusts the rate of the information payloads so that they are
synchronized with the STM-N frame.
SDH payload pointers can be classified into administrative unit pointer (AU_PTR) and tributary
board pointer (TU_PTR). Pointer justification involves administrative unit pointer justification
and tributary board pointer justification.
Generation Mechanism of AU Pointer Justification

In the AU-4 frame shown in Figure 1-5, several bytes in specific locations (the first nine bytes
in the fourth row) are used to record the starting point of data information (to represent the data
information phase). These bytes are called pointers. H1 and H2 are pointers, and three H3s are
negative pointer justification opportunities.

Figure 1-5 Location and content of AU_PTR
9 rows
VC-4
H1 YY H2 1* 1* H3 H3 H3
AU- 4 PTR 1 9
Y Byte: 1001SS11 (S Unspecified ) 10 270columns

1* Byte: 11111111
When the network is synchronous, the pointer is used to perform phase alignment among the
synchronous signals. If the NEs work under the same clock, the signals that are transmitted from
various NEs to a certain NE have the same clock frequency. Therefore, rate adaptation is
unnecessary. Transiently, the rate may be either a little higher or lower. In this case, phase
alignment is required.
When the network is not synchronous, the NEs work at different frequencies, and the pointer is
used for frequency justification. Pointer justification is also required to tolerate the frequency
jitter and wander in the network.
If the frame rate of the virtual container (VC) is different from that of the administrative unit
group (AUG), information is stuffed in the H3 bytes of the AU pointer area. The idle bytes are
stuffed with pseudo-random information and are inserted before the VC to decrease or increase
the frame rate of the VC. At the same time, the pointer value is raised or dropped to increase or
decrease the frame rate of the VC. Therefore, positive and negative pointer justifications are
performed. See Table 1-3.
Table 1-3 Pointer justification states
State Byte Numbering and Content of the Fourth Row in the STM-1 Rate
Name Frame Relatio
nship
7 8 9 10 11 12
Pointer H3 H3 H3 Informat Informat Informati Informat

zero ion ion on ion =
justificat containe
ion r
Positive H3 H3 H3 Stuffing Stuffing Stuffing Informat

pointer ion <
justificat containe
ion r
Negative Informat Informati Informat Informat Informat Informati Informat

pointer ion on ion ion ion on ion >
justificat containe
ion r

NOTE
The information rate is the VC frame rate. The container rate is the AU encapsulation rate.
All the NEs in the SDH network are generally well synchronized, and pointer justification seldom
occurs. Actual performance monitoring for pointer justification of the network proves that AU
pointer justification and TU pointer justification seldom occurs.
It is difficult to guarantee that all the NEs are well synchronized all the time during long-term
network operation. If one or several NEs are not synchronized, even for a very short time, a great
amount of pointer justifications could occur. Consecutive positive or negative pointer
justification adjusts the phase forward or backward to realize the frequency justification.
Generation Mechanism of TU Pointer Justification

Causes of TU pointer justification are as follows:
l TU pointer justification is transformed from AU pointer justification.

TU pointer justification does not occur when the E1 signal is adapted into VC-12, and
multiplexed into STM-1. If there is frequency offset between the E1 signal of the switch
and the SDH clock, the signal is adapted to realize synchronization. Therefore, TU pointer
justification that is detected on the tributary board is generally transformed from AU pointer
justification.
l TU pointer justification occurs during demultiplexing.
If the system clock is inconsistent with the received clock, TU pointer justification occurs
during demultiplexing.
l When the upstream NE that the service passes through has pointer justification, TU pointer
justification occurs at the local NE during demultiplexing.
Detection and Reporting of Pointer Justifications

There are two modes of detection and reporting of AU pointer justification: remote detection
and local detection.
l Remote detection
The information about AU pointer justification that is generated at the local NE is
transferred to the remote NE through the H1 and H2 bytes. The remote NE reports the AU
pointer justification by interpreting the H1 and H2 bytes. Therefore, if the remote NE reports
an AU pointer justification event, the local NE has pointer justification. The remote NE is
the downstream NE in the service direction.
l Local detection
AU pointer justification that is generated at the local NE is detected and reported at the
local NE. Therefore, if the local NE reports an AU pointer justification event, the local NE
has pointer justification.
In the SDH system, the AU pointer justification events on a majority of optical interface boards
are detected and reported through the detection of the H1 and H2 bytes. This is also called remote
detection.
Generally, AU pointer justification is generated at the upstream NE, but it is detected and
reported at the downstream NE.

Alarms and Performance Events Reference 2 Alarm list
2 Alarm list
About This Chapter
This topic describes all the alarms that the product supports.
2.1 Alphabetically Listed Alarms

This topic lists the alarms supported by the product alphabetically.
2.2 Alarms Classified by Board Type
This topic lists the alarms mapping the boards that the OptiX OSN 9560 supports.

2.1 Alphabetically Listed Alarms

This topic lists the alarms supported by the product alphabetically.
2.1.1 Alarm List A

This section uses a table to list the alarms starting with A.
Name Description Severity Board
AD_CHECK_F AD chip self-test Major TN11CRPC

AIL failure
ALM_ALS Automatic laser Minor N3SLH41 N4SLQ64 N4SLO16

shutdown N4SF64 N4SLQ16 N4SLD64
N4SL64 N4SFD64 N1SF64A
APS_MANUAL APS protocol Major TN52SCC

_STOP manually stopped
ALM_HANGUP Telephone not hung Minor TNL1STI

up
ALM_GFP_dCS GFP client signal Critical N1EGSH

F fail
ALM_GFP_dLF GFP loss of frame Major N1EGSH

D delimitation
APS_FAIL Automatic Major TN52SCC

protection
switching failure
indication
APS_INDI Automatic Major TN52SCC

protection
switching
indication
AU_AIS AU alarm Major N1EGSH N3SLH41 N4SLQ64

indication signal N4SLO16 N4SF64 N4SLQ16
N4SLD64 N4SL64 N4SFD64
N1SF64A
AU_LOP AU loss of pointer Major N1EGSH N3SLH41 N4SLQ64

N4SLO16 N4SF64 N4SLQ16
N1SF64A
2.1.2 Alarm List B

This section uses a table to list the alarms starting with B.

B1_EXC B1 excessive bit Minor N3SLH41 N4SLQ64

errors in regenerator N4SLO16 N4SF64 N4SLQ16
section N4SLD64 N4SL64 N4SFD64
N1SF64A
B1_SD B1 signal degrade in Minor N3SLH41 N4SLQ64

regenerator section N4SLO16 N4SF64 N4SLQ16
N1SF64A
B2_EXC B2 excessive bit Major N3SLH41 N4SLQ64

errors in multiplex N4SLO16 N4SF64 N4SLQ16
section N4SLD64 N4SL64 N4SFD64
N1SF64A

multiplex section N4SLO16 N4SF64 N4SLQ16
N1SF64A
B3_EXC B3 excessive bit Major N3SLH41 N4SLQ64

errors in higher N4SLO16 N4SF64 N4SLQ16
order path N4SLD64 N4SL64 N4SFD64
N1SF64A
B3_EXC_VC3 B3 excessive bit Major N1EGSH

errors in VC-3
B3_EXC_VC4 B3 excessive bit Major N1EGSH

errors in VC-4

higher order path N4SLO16 N4SF64 N4SLQ16
N1SF64A
B3_SD_VC3 B3 signal degrade in Minor N1EGSH

VC-3
B3_SD_VC4 B3 signal degrade in Minor N1EGSH

VC-4
BD_NOT_INSTA Logical board not Minor TN52SCC

LLED installed

BD_STATUS Board not in Major TN52STG TN52STI

position TNL2SXCM N1EGSH
TN52SCC N3SLH41
N4SLQ64 N4SLO16 N4SF64
N4SLQ16 N4SLD64 N4SL64
N4SFD64 N1SF64A
TN51AUX TNL2SEI1
TNL2SEI2 TN51FAN
TN51PIU TN51ATE
TN11MR2 TN11DCU
TN11CRPC TN12OAU1
TN12OBU1 N4BPA
TNL1STI
BDID_ERROR Slot check error Major N1EGSH N4BPA
BEFFEC_EXC Excessive bit errors Warning N4SF64 N4SFD64 N1SF64A

before FEC
BOOTROM_BAD BOOTROM data Major N1EGSH TN52SCC

check failure
BUS_ERR Bus error Critical TNL2SXCM N3SLH41

N4SLQ64 N4SLO16 N4SF64
N4SFD64 N1SF64A
2.1.3 Alarm List C

This section uses a table to list the alarms starting with C.
C2_VCAIS C2 byte alarm Minor N3SLH41 N4SLQ64

indication signal N4SLO16 N4SF64
N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
CHIP_ABN Temperature chip Minor N1EGSH

exception
CLK_NO_TRAC Clock entering into Minor TN52STG

E_MODE non-tracing running
mode

COMMUN_FAI Inter-board Major TN52STG TNL2SXCM

L communication N1EGSH TN52SCC
failure N3SLH41 N4SLQ64
N4SLO16 N4SF64
N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A TN51AUX
TN11CRPC TN12OAU1
TN12OBU1 N4BPA
2.1.4 Alarm List D

This section uses a table to list the alarms starting with D.
DB_RESTORE_FA Database restore fail Major TN52SCC

IL alarm
DBMS_ERROR Database error Major TN52SCC
DBMS_PROTECT Database in Critical TN52SCC

_MODE protection mode
DLAG_PROTECT DLAG protection Major N1EGSH

_FAIL fails
DSP_LOAD_FAIL DSP loading failure Major TN12OAU1 TN12OBU1
2.1.5 Alarm List E

This section uses a table to list the alarms starting with E.
ETH_CFM_LOC Ethernet OAM Critical N1EGSH

connectivity loss
ETH_CFM_MACST Remote MAC Major N1EGSH

ATUS defect indication
ETH_CFM_MISME Ethernet OAM Critical N1EGSH

RGE misconnection
ETH_CFM_RDI Ethernet OAM Minor N1EGSH

reception failure
ETH_CFM_UNEXP Incorrect Ethernet Minor N1EGSH

ERI OAM frames

ETHOAM_DISCOV Discovery failure of Minor N1EGSH

ER_FAIL point-to-point
Ethernet OAM
ETHOAM_RMT_L Remote loopback Minor N1EGSH

OOP of point-to-point
Ethernet OAM
ETHOAM_RMT_S Remote signal Minor N1EGSH

D degrade of point-to-
point Ethernet
OAM
ETHOAM_SELF_L Loopback of the Major N1EGSH

OOP MAC port
receiving the OAM
protocol packets in
a point-to-point
manner
ETHOAM_VCG_SE Loopback of the Major N1EGSH

LF_LOOP VCTRUNK port
receiving the OAM
protocol packets in
a point-to-point
manner
EX_ETHOAM_CC_ Loss of periodic Major N1EGSH

LOS continuity check
message
EX_ETHOAM_MPI Maintenance point Major N1EGSH

D_CNFLCT conflict
EXT_SYNC_LOS Loss of external Critical TN52STG

clock source
EXT_TIME_LOC External clock Major TN52STG

source loss
2.1.6 Alarm List F

This section uses a table to list the alarms starting with F.
FAN_FAIL Fan failure Major TN51FAN TN11CRPC
FAN_FAULT Fan fault Minor TN51FAN

FEATURE_WIT Unauthorized use of Major TN52SCC

HOUT_LICENS a service controlled
E by the feature license
FCS_ERR FCS check error Critical N1EGSH
FEC_LOF FEC loss of frame Critical N4SF64 N4SFD64 N1SF64A
FEC_OOF FEC out of frame Critical N4SF64 N4SFD64 N1SF64A
FPGA_ABN FPGA reading/ Major TN11CRPC

writing exception
FSELECT_STG Forced selection of Major N3SLH41 N4SLQ64 N4SLO16

clock unit N4SF64 N4SLQ16 N4SLD64
FWD_PKT_LO Packets dropped Minor N1EGSH
2.1.7 Alarm List G

This section uses a table to list the alarms starting with G.
GAINDATA Mismatch of gain Major TN12OAU1 TN12OBU1

_MIS attribute
2.1.8 Alarm List H

This section uses a table to list the alarms starting with H.
HARD_BAD Hardware failure Critical TN52STG TNL2SXCM

N1EGSH TN52SCC
N3SLH41 N4SLQ64
N4SLO16 N4SF64
N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A TN51AUX
TN12OAU1
TN12OBU1 N4BPA

HARD_ERR Hardware error Minor TN52STG TNL2SXCM

with slight N1EGSH TN52SCC
impact N3SLH41 N4SLQ64
N4SLO16 N4SF64
N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A TN51AUX
TN12OAU1
TN12OBU1
HP_LOM Higher order path Major N3SLH41 N4SLQ64

loss of N4SLO16 N4SF64
multiframe N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
HP_RDI Higher order path Minor N1EGSH N3SLH41

remote defect N4SLQ64 N4SLO16
indication N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
HP_REI Higher order path Warning N3SLH41 N4SLQ64

remote error N4SLO16 N4SF64
indication N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
HP_SLM Higher order path Minor N1EGSH N3SLH41

signal label N4SLQ64 N4SLO16
mismatch N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
HP_TIM Higher order path Minor N3SLH41 N4SLQ64

trace identifier N4SLO16 N4SF64
mismatch N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
HP_UNEQ Higher order path Minor N1EGSH N3SLH41

unequipped N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
HSC_UNAVAIL Active/standby Minor TN52SCC

switching
function failure

2.1.9 Alarm List I

This section uses a table to list the alarms starting with I.
IN_PWR_HIG Input power too Critical N1EGSH N3SLH41

H high N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
N4BPA
IN_PWR_LOW Input power too Critical N1EGSH N3SLH41

low N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
N4BPA
IN_PWR_FAIL Input power fail Critical N4BPA
2.1.10 Alarm List J

This section uses a table to list the alarms starting with J.
J0_MM Trace identifier Minor N3SLH41 N4SLQ64

mismatch N4SLO16 N4SF64
N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
2.1.11 Alarm List K

This section uses a table to list the alarms starting with K.
K1_K2_M K1 and K2 byte Minor TN52SCC

mismatch
K2_M K2 byte mismatch Minor TN52SCC
2.1.12 Alarm List L

This section uses a table to list the alarms starting with L.

LAG_PORT_FAIL Link Minor N1EGSH

aggregation port
failure
LAN_LOC Ethernet Major TNL2SEI1 TNL2SEI2

communication
failure
LASER_HAZARD_W Warning Critical TN11CRPC TN12OAU1

ARNING indication of the TN12OBU1
laser hazard
level
LASER_MODULE_MI Optical module Major N1EGSH N3SLH41

SMATCH mismatch N4SLQ64 N4SLO16 N4SF64
N4SFD64 N1SF64A
LASER_SHUT Laser shut down Major N3SLH41 N4SLQ64

N4SLO16 N4SF64 N4SLQ16
N1SF64A
LCAS_FOPR Failure of LCAS Major N1EGSH

protocol in the
receive direction
LCAS_FOPT Failure of LCAS Major N1EGSH

protocol in the
transmit
direction
LCAS_PLCR Bandwidth Minor N1EGSH

partially lost in
the LCAS
receive direction
LCAS_PLCT Bandwidth Minor N1EGSH

partially lost in
the LCAS
transmit
direction
LCAS_TLCR Bandwidth Major N1EGSH

totally lost in the
LCAS receive
direction
LCAS_TLCT Bandwidth Major N1EGSH

totally lost in the
LCAS transmit
direction

LCS_DAYS_OF_GRA License file in Major TN52SCC

CE the probation
period
LCS_EXPIRED License file Critical TN52SCC

expired
LCS_FILE_NOT_EX- License file not Critical TN52SCC

IST installed
LINK_ERR Data link error Critical N1EGSH
LOCK_CUR_FAIL Working current Critical TN11CRPC N4BPA

locking failure
LOCKPOW_MIS Mismatch of Major TN11CRPC

lock-power
attribute
LOOP_ALM Board path in Minor N1EGSH N3SLH41

loopback status N3SLH41 N4SLQ64
N4SLQ64 N4SLO16
N4SLO16 N4SF64 N4SF64
N4SLQ16 N4SLQ16
N4SLD64 N4SLD64 N4SL64
N4SL64 N4SFD64 N4SFD64
N1SF64A N1SF64A
LP_RDI_VC3 VC-3 lower Minor N1EGSH

order path
remote defect
indication
LP_SLM_VC3 VC-3 lower Minor N1EGSH

order path signal
label mismatch
LP_UNEQ_VC3 VC-3 lower Minor N1EGSH

order path
unequipped
LPT_RFI Remote failure Critical N1EGSH

indication of
link state pass
through
LSR_COOL_ALM Laser cooling Major N3SLH41 N4SLQ64

current crossing N4SLO16 N4SF64 N4SLQ16
the threshold N4SLD64 N4SL64 N4SFD64
N1SF64A
LSR_INVALID Invalid optical Critical N1EGSH

module alarm

LSR_WILL_DIE Laser going to Critical N1EGSH N3SLH41

expire N4SLQ64 N4SLO16 N4SF64
N4SFD64 N1SF64A
TN11CRPC
LTI Loss of timing Major TN52STG

information
2.1.13 Alarm List M

This section uses a table to list the alarms starting with M.
MS_AIS Multiplex section Major N3SLH41 N4SLQ64

alarm indication N4SLO16 N4SF64
signal N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
MS_APS_INDI_EX Extension of Major TN52SCC

automatic protection
switching indication
in multiplex section
MS_RDI Multiplex section Minor N3SLH41 N4SLQ64

remote defect N4SLO16 N4SF64
N4SL64 N4SFD64
N1SF64A
MS_REI Multiplex section Warning N3SLH41 N4SLQ64

remote error N4SLO16 N4SF64
N4SL64 N4SFD64
N1SF64A
MSSW_DIFFEREN Software Major TN52SCC

T inconsistency
between active and
standby boards
MULTI_RPL_OWN The ring network Minor N1EGSH

ER contains several
RPL_OWNER
nodes
MUT_LOS Loss of multiplex Critical TN12OAU1

signal TN12OBU1

2.1.14 Alarm List N

This section uses a table to list the alarms starting with N.
NEBD_XC_DIF Crossing data of NE Major TN52SCC

and board different
NESF_LOST NE software lost Critical TN52SCC
NESTATE_INSTA NE in installing state Critical TN52SCC

LL
NO_BD_PARA Board parameters not Critical TN11CRPC

set TN12OAU1
TN12OBU1 N4BPA
NO_BD_SOFT No board software Critical N3SLH41 N4SLQ64

N4SLO16 N4SF64
N4SLQ16 N4SLD64
N4SL64 N4SFD64
N1SF64A
TN11CRPC
TN12OAU1
TN12OBU1
N1EGSH N4BPA
NO_ELABEL Electronic label not Warning TN51AUX

loaded TN12OAU1
TN12OBU1
NODEID_MM The NODEID_MM Major TN52SCC

is an alarm indicating
the MSP node ID
mismatch
2.1.15 Alarm List O

This section uses a table to list the alarms starting with O.
OA_LOW_GA Optical amplifier Critical TN12OAU1 TN12OBU1

IN gain too low
ODU_AIS alarm indication Major N4SF64 N4SFD64 N1SF64A

signal
ODU_LCK locked Major N4SF64 N4SFD64 N1SF64A
ODU_OCI open connection Major N4SF64 N4SFD64 N1SF64A

indication

OH_LOOP Overhead loopback Minor N3SLH41 N4SLQ64 N4SLO16

N4SF64 N4SLQ16 N4SLD64
OMS_BDI Backward defect Minor TN11MR2

indication at OMS
layer
OMS_BDI_O Backward defect Minor TN11MR2

indication
(overhead) at OMS
layer
OMS_BDI_P Backward defect Minor TN11MR2

indication (payload)
at OMS layer
OMS_FDI Forward defect Major TN11MR2

indication at OMS
layer
OMS_FDI_O Forward defect Minor TN11MR2

indication
(overhead) at OMS
layer
OMS_FDI_P Forward defect Major TN11MR2

indication (payload)
at OMS layerr
OMS_SSF Server signal fail at Major TN11MR2

OMS layer
OMS_SSF_O Server signal fail Minor TN11MR2

(overhead) at OMS
layer
OMS_SSF_P Server signal fail Major TN11MR2

(payload) at OMS
layer
OOL The phase-locked Major TN52STG

loop is out of lock
OPA_FAIL_IN Automatic Major TN11MR2 TN11DCU

DI adjustment of power TN11CRPC TN12OAU1
during optical cross- TN12OBU1
connection failed
OTU_AIS OTU alarm Major N4SF64 N4SFD64 N1SF64A

indication signal
OTU_LOF OTU loss of FAS Critical N4SF64 N4SFD64 N1SF64A

frame

OTU_LOM OTU out of Major N4SF64 N4SFD64 N1SF64A

multiframe
OUT_PWR_HI Output power too Major N1EGSH TN11CRPC

GH high
OUT_PWR_L Output power too Major N1EGSH TN11CRPC

OW low
OUT_PWR_A Output power Critical N4BPA

BN abnormal
2.1.16 Alarm List P

This section uses a table to list the alarms starting with P.
PATCH_ACT_TIMEOUT Patch package Minor TN52SCC

activation timeout
PATCH_DEACT_TIME- Patch package Minor TN52SCC

OUT deactivation timeout
PATCH_ERR Patch error Major TN52STG

N1EGSH
TN52SCC
N3SLH41
N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
TN11CRPC
TN12OAU1
TN12OBU1
N4BPA

PATCH_NOT_CONFIRM Active patch not Major TN52STG

confirmed in time N1EGSH
TN52SCC
N3SLH41
N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
TN11CRPC
TN12OAU1
TN12OBU1
N4BPA
PATCH_PKGERR Patch package file error Minor TN52SCC
PATCHFILE_NOTEXIST No patch file Major TN52STG

N1EGSH
TN52SCC
N3SLH41
N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
TN11CRPC
TN12OAU1
TN12OBU1
N4BPA
PM_BDI ODU PM backward Major N4SF64

defect indication N4SFD64
N1SF64A
PM_BEI ODU PM backward Major N4SF64

error indication N4SFD64
N1SF64A
PM_BIP8_OVER ODU PM excessive bit Major N4SF64

errors N4SFD64
N1SF64A
PM_BIP8_SD ODU PM signal Major N4SF64

degrade N4SFD64
N1SF64A

PM_TIM ODU PM trace Major N4SF64

identifier mismatch N4SFD64
N1SF64A
PORT_MODULE_OFF- Optical module not in Major N1EGSH

LINE position N3SLH41
N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
POWER_ABNORMAL Power abnormal Major N3SLH41

N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
N4BPA
TNL1STI
POWER_FAIL Power failure Major TN52SCC

TN51PIU
TN11CRPC
PUM_BCM_ALM Pump laser bias current Major TN11CRPC

crossing the threshold TN12OAU1
TN12OBU1
N4BPA
PUM_TEM_ALM Pump laser working Major TN12OAU1

temperature crossing TN12OBU1
the threshold
PUMP_COOL_EXC Pump laser cooling Critical TN12OAU1

current crossing the TN12OBU1
threshold N4BPA
2.1.17 Alarm List R

This section uses a table to list the alarms starting with R.

R_LOC Receive loss of clock Critical N3SLH41

N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
R_LOF Receive loss of frame Critical N3SLH41

N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
R_LOS Receive loss of signal Critical N1EGSH

N3SLH41
N4SLQ64
N4SLO16
N4SF64
N4SLQ16
N4SLD64
N4SL64
N4SFD64
N1SF64A
RELAY_ALARM_CRIT Critical relay alarm Critical TNL2SEI1

ICAL
RELAY_ALARM_IG- Warning relay alarm Warning TNL2SEI1

NORE
RELAY_ALARM_MA- Major relay alarm Major TNL2SEI1

JOR
RELAY_ALARM_MI- Minor relay alarm Minor TNL2SEI1

NOR
RTC_FAIL Real-time clock Major TNL2SEI1

timing failure
2.1.18 Alarm List S

This section uses a table to list the alarms starting with S.

S1_SYN_CHANGE Clock source Major TN52STG

switching in
the S1 byte
mode
SECU_ALM Illegal user Major TN52SCC

login
SERVICE_CAPACITY_EXC The service Major TN52SCC

EED_LICENSE capacity
exceeds the
license limit
SERVICE_TYPE_EXCEED_ The service Major TN52SCC

LICENSE type exceeds
the license
limit
SHELF_AREA_POWER_OV Total optical Critical TN52SCC

ER power
consumption
of the subrack
exceeds the
threshold
SLAVE_WORKING Board Warning N1EGSH N3SLH41

selecting N4SLQ64 N4SLO16
services and N4SF64 N4SLQ16
clock signals N4SLD64 N4SL64
from the buses N4SFD64 N1SF64A
of the standby
cross-connect
board
SM_BDI OTU SM Major N4SF64 N4SFD64

backward N1SF64A
defect
indication
SM_BEI OTU SM Major N4SF64 N4SFD64

backward N1SF64A
error
indication
SM_BIP8_OVER OTU SM Major N4SF64 N4SFD64

excessive bit N1SF64A
errors
SM_BIP8_SD OTU SM Major N4SF64 N4SFD64

signal degrade N1SF64A

SM_IAE OTU SM Major N4SF64 N4SFD64

import N1SF64A
adjustment
error
SM_TIM OTU SM trace Major N4SF64 N4SFD64

identifier N1SF64A
mismatch
SNCP_FAIL The SNCP Critical TN52SCC

switching
failure
SO_SK_MISMATCH The number of Critical N1EGSH

timeslots
bundled at the
LCAS source
is not
consistent
with the
number of
timeslots
bundled at the
LCAS sink
STORM_CUR_QUENUM_O Storm alarm Minor TN52SCC

VER
SUBRACK_ID_CONFLICT Conflict of Critical TN52SCC

subrack ID
SUBRACK_ID_MISMATCH Mismatch of Major TN52SCC

subrack ID
SUBRACK_LOOP Loop of Critical TN52SCC

subrack
SUBRACK_TYPE_MIS- The Major TN52SCC

MATCH configured
subrack does
not match the
physical
subrack
SUM_INPWR_HI Total input Major TN12OAU1

power too high TN12OBU1
SUM_INPWR_LOW Total input Major TN12OAU1

power too low TN12OBU1
SWDL_ACTIVATED_TIME- Activation Critical TN52SCC

OUT timeout

SWDL_AUTOMATCH_INH Automatic Minor TN52SCC

match
function
inhibited
SWDL_CHGMNG_NO- Mismatch Critical TN52SCC

MATCH between CF
card software
and board
software
SWDL_COMMIT_FAIL Commit Minor TN52SCC

failure
SWDL_INPROCESS Package Minor TN52SCC

loading in
progress
SWDL_NEPKGCHECK File lost Critical TN52SCC
SWDL_PKG_NOBDSOFT Files of some Minor TN52SCC N4BPA

boards not
found in
software
package
SWDL_PKGVER_MM Package Minor TN52SCC

version
conformance
check failed
SWDL_ROLLBACK_FAIL Rollback Minor TN52SCC

failure
SYN_BAD Synchronizati Minor TN52STG

on source
degrade
SYNC_C_LOS Synchronizati Warning TN52STG

on source loss
of signal
SYNC_DISABLE Automatic Minor TN52SCC

synchronizatio
n of the system
control board
is disabled
SYNC_F_M_SWITCH Manual or Warning TN52STG

forced
switching of
clock source

SYNC_FAIL Synchronizati Minor TN52SCC

on failure
between active
and standby
databases
SYNC_LOCKOFF Clock source Warning TN52SCC

locked out
SYSPARA_CFDB_NOSAME Difference Minor TN52SCC

between the
SCC data and
the CF card
data
2.1.19 Alarm List T

This section uses a table to list the alarms starting with T.
TD Transmitter Critical N1EGSH

degrade
T_LOSEX Extended T_LOS Major N1EGSH

alarm
TEM_HA Laser temperature Major N1EGSH N3SLH41

too high N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
TEM_LA Laser temperature Major N1EGSH N3SLH41

too low N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
TEMP_OVER Working Major TN52STG TNL2SXCM

temperature over N1EGSH N3SLH41
the threshold N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
TN12OAU1 TN12OBU1
N4BPA

TEST_STATUS Board entering into Warning N1EGSH N3SLH41

the test status N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
TF Laser transmission Critical N1EGSH N3SLH41

failure N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
THUNDERALM Thunder protection Minor TN51PIU

circuit failure
TIME_LOS High-precision line Major TN52STG

time source loss
TIME_NO_TRACE High-precision Minor TN52STG

_MODE time not in trace
mode
TR_LOC Transmit loss of Major N1EGSH N3SLH41

clock N4SLQ64 N4SLO16
N4SF64 N4SLQ16
N4SLD64 N4SL64
N4SFD64 N1SF64A
TU_AIS_VC3 VC-3 TU alarm Major N1EGSH

indication signal
TU_LOP_VC3 VC-3 TU loss of Major N1EGSH

pointer
2.1.20 Alarm List V

This section uses a table to list the alarms starting with V.
VCAT_LOA Virtual concatenation Critical N1EGSH

loss of alignment
VCAT_LOM_VC3 VC-3 virtual Major N1EGSH

concatenation loss of
multiframe
VCAT_LOM_VC4 VC-4 virtual Major N1EGSH

concatenation loss of
multiframe

VOA_ADJUST_F VOA adjustment Major TN12OAU1

AIL failed
2.1.21 Alarm List W

This section uses a table to list the alarms starting with W.
W_R_FAIL Reading and writing Major TN11CRPC

single chip register
failure
WAVEDATA_MI Mismatch of wave or Major TN11MR2

S band attribute TN12OAU1
TN12OBU1
WRG_BD_TYPE Wrong type of board Major TN52STG

inserted TN52STI
TNL2SXCM
N1EGSH
TN52SCC
N3SLH41
N4SLQ64
N4SLO16 N4SF64
N4SLQ16
N4SLD64 N4SL64
N4SFD64
N1SF64A
TN51AUX
TNL2SEI1
TNL2SEI2
TN51FAN
TN51PIU
TN51ATE
TN11MR2
TN11DCU
TN11CRPC
TN12OAU1
TN12OBU1
N4BPA TNL1STI
2.1.22 Alarm List X

This section uses a table to list the alarms starting with X.

XC_UNSWITCH The cross-connect Major TN52SCC

matrix of the board is
not switched
2.2 Alarms Classified by Board Type

This topic lists the alarms mapping the boards that the OptiX OSN 9560 supports.
2.2.1 N1EGSH
ALM_GFP_dCSF EX_ETHOAM_MPID_CNFL MULTI_RPL_OWNER
CT
ALM_GFP_dLFD FCS_ERR NO_ELABEL
AU_AIS FWD_PKT_LOSS OUT_PWR_HIGH
AU_LOP HARD_BAD OUT_PWR_LOW
B3_EXC_VC3 HARD_ERR PATCHFILE_NOTEX-

IST
B3_EXC_VC4 HP_RDI PATCH_ERR
B3_SD_VC3 HP_SLM PATCH_NOT_CON-

FIRM
B3_SD_VC4 HP_UNEQ PORT_MODULE_OFF-

LINE
BDID_ERROR IN_PWR_HIGH R_LOS
BD_STATUS IN_PWR_LOW SLAVE_WORKING
BOOTROM_BAD LAG_PORT_FAIL SO_SK_MISMATCH
CHIP_ABN NO_BD_SOFT TD
COMMUN_FAIL LASER_MODULE_MIS- TEMP_OVER

MATCH
DLAG_PROTECT_FAIL LCAS_FOPR TEM_HA
ETHOAM_DISCOVER_FAI LCAS_FOPT TEM_LA

L
ETHOAM_RMT_LOOP LCAS_PLCR TEST_STATUS
ETHOAM_RMT_SD LCAS_PLCT TF
ETHOAM_SELF_LOOP LCAS_TLCR TR_LOC

ETHOAM_VCG_SELF_LO LCAS_TLCT TU_AIS_VC3

OP
ETH_CFM_LOC LINK_ERR TU_LOP_VC3
ETH_CFM_MACSTATUS LOOP_ALM T_LOSEX
ETH_CFM_MISMERGE LPT_RFI VCAT_LOA
ETH_CFM_RDI LP_RDI_VC3 VCAT_LOM_VC3
ETH_CFM_UNEXPERI LP_SLM_VC3 VCAT_LOM_VC4
EX_ETHOAM_CC_LOS LP_UNEQ_VC3 WRG_BD_TYPE
LSR_INVALID LSR_WILL_DIE
2.2.2 N1SF64A
ALM_ALS HP_UNEQ PM_BEI
AU_AIS IN_PWR_HIGH PM_BIP8_OVER
AU_LOP IN_PWR_LOW PM_BIP8_SD
B1_EXC J0_MM PM_TIM
B1_SD LASER_MODULE_MISMATCH PORT_MODULE_OFFLINE
B2_EXC LASER_SHUT POWER_ABNORMAL
B2_SD LOOP_ALM R_LOC
B3_EXC LSR_COOL_ALM R_LOF
B3_SD LSR_WILL_DIE R_LOS
BD_STATUS MS_AIS SLAVE_WORKING
BEFFEC_EXC MS_RDI SM_BDI
BUS_ERR MS_REI SM_BEI
C2_VCAIS NO_BD_SOFT SM_BIP8_OVER
COMMUN_FAIL ODU_AIS SM_BIP8_SD
FEC_LOF ODU_LCK SM_IAE
FEC_OOF ODU_OCI SM_TIM
FSELECT_STG OH_LOOP TEMP_OVER
HARD_BAD OTU_AIS TEM_HA
HARD_ERR OTU_LOF TEM_LA

HP_LOM OTU_LOM TEST_STATUS
HP_RDI PATCHFILE_NOTEXIST TF
HP_REI PATCH_ERR TR_LOC
HP_SLM PATCH_NOT_CONFIRM WRG_BD_TYPE
HP_TIM PM_BDI
2.2.3 N3SLH41
ALM_ALS HP_REI PATCHFILE_NOTEXIST
AU_AIS HP_SLM PATCH_ERR
AU_LOP HP_TIM PATCH_NOT_CONFIRM
B1_EXC HP_UNEQ PORT_MODULE_OFFLINE
B1_SD IN_PWR_HIGH POWER_ABNORMAL
B2_EXC IN_PWR_LOW R_LOC
B2_SD J0_MM R_LOF
B3_EXC LASER_MODULE_MIS- R_LOS

MATCH
B3_SD LASER_SHUT SLAVE_WORKING
BD_STATUS LOOP_ALM TEMP_OVER
BUS_ERR LSR_COOL_ALM TEM_HA
C2_VCAIS LSR_WILL_DIE TEM_LA
COMMUN_FAIL MS_AIS TEST_STATUS
FSELECT_STG MS_RDI TF
HARD_BAD MS_REI TR_LOC
HARD_ERR NO_BD_SOFT WRG_BD_TYPE
HP_LOM OH_LOOP HP_RDI
2.2.4 N4BPA
NO_BD_SOFT LOCK_CUR_FAIL OUT_PWR_ABN
TEMP_OVER IN_PWR_HIGH IN_PWR_LOW

PUM_BCM_ALM BD_STATUS NO_BD_PARA
PUMP_COOL_EXC PATCHFILE_NOTEXIST PATCH_ERR
PATCH_NOT_CONFIRM POWER_ABNORMAL IN_PWR_FAIL
HARD_BAD BDID_ERROR COMMUN_FAIL
SWDL_PKG_NOBDSOFT WRG_BD_TYPE
2.2.5 N4SF64
B1_EXC J0_MM PM_TIM
B1_SD LASER_MODULE_MIS- PORT_MODULE_OFFLINE

MATCH

HP_TIM PM_BDI
2.2.6 N4SFD64
B1_EXC J0_MM PM_TIM
B1_SD LASER_MODULE_MIS- PORT_MODULE_OFFLINE

MATCH
HP_TIM PM_BDI

2.2.7 N4SL64
B2_SD J0_MM R_LOF

MATCH
2.2.8 N4SLD64
B2_SD J0_MM R_LOF

MATCH

2.2.9 N4SLO16
B2_SD J0_MM R_LOF

MATCH

2.2.10 N4SLQ16
B2_SD J0_MM R_LOF

MATCH
2.2.11 N4SLQ64
B2_SD J0_MM R_LOF

MATCH

2.2.12 TN11CRPC
AD_CHECK_FAIL LSR_WILL_DIE PATCH_NOT_CONFIRM
BD_STATUS NO_BD_PARA POWER_FAIL
COMMUN_FAIL NO_BD_SOFT PUMP_COOL_EXC
FAN_FAIL OPA_FAIL_INDI PUM_BCM_ALM
FPGA_ABN OUT_PWR_HIGH WRG_BD_TYPE
LASER_HAZARD_WARN- OUT_PWR_LOW W_R_FAIL

ING
LOCKPOW_MIS PATCHFILE_NOTEXIST PATCH_ERR
LOCK_CUR_FAIL
2.2.13 TN11DCU
BD_STATUS OPA_FAIL_INDI WRG_BD_TYPE
2.2.14 TN11MR2
BD_STATUS OMS_FDI_O OPA_FAIL_INDI
OMS_BDI OMS_FDI_P WAVEDATA_MIS
OMS_BDI_O OMS_SSF WRG_BD_TYPE
OMS_BDI_P OMS_SSF_O OMS_SSF_P

OMS_FDI
2.2.15 TN12OAU1
BD_STATUS NO_BD_SOFT PUM_TEM_ALM
COMMUN_FAIL NO_ELABEL SUM_INPWR_HI
DSP_LOAD_FAIL OA_LOW_GAIN SUM_INPWR_LOW
GAINDATA_MIS OPA_FAIL_INDI TEMP_OVER
HARD_BAD PATCHFILE_NOTEXIST VOA_ADJUST_FAIL
HARD_ERR PATCH_ERR WAVEDATA_MIS
LASER_HAZARD_WARN- PATCH_NOT_CONFIRM WRG_BD_TYPE

ING
MUT_LOS PUMP_COOL_EXC PUM_BCM_ALM
NO_BD_PARA
2.2.16 TN12OBU1
BD_STATUS NO_BD_PARA PUMP_COOL_EXC
COMMUN_FAIL NO_BD_SOFT PUM_BCM_ALM
DSP_LOAD_FAIL NO_ELABEL PUM_TEM_ALM
GAINDATA_MIS OA_LOW_GAIN SUM_INPWR_HI
HARD_BAD OPA_FAIL_INDI SUM_INPWR_LOW
HARD_ERR PATCHFILE_NOTEXIST TEMP_OVER
LASER_HAZARD_WARN PATCH_ERR WAVEDATA_MIS

ING
MUT_LOS PATCH_NOT_CONFIRM WRG_BD_TYPE
2.2.17 TN51ATE
BD_STATUS WRG_BD_TYPE

2.2.18 TN51AUX
BD_STATUS HARD_BAD NO_ELABEL
COMMUN_FAIL HARD_ERR WRG_BD_TYPE
2.2.19 TN51FAN
BD_STATUS FAN_FAULT WRG_BD_TYPE
FAN_FAIL
2.2.20 TN51PIU
BD_STATUS THUNDERALM WRG_BD_TYPE
POWER_FAIL
2.2.21 TN52SCC
APS_MANUAL_STO MS_APS_INDI_EX SUBRACK_ID_CON-
P FLICT
RTC_FAIL NEBD_XC_DIF SUBRACK_ID_MIS-

MATCH
APS_FAIL NESF_LOST SUBRACK_LOOP
APS_INDI NESTATE_INSTALL SUBRACK_TYPE_MIS-

MATCH
BD_NOT_INSTALL NODEID_MM SWDL_ACTIVATED_TI

ED MEOUT
BD_STATUS PATCHFILE_NOTEXIST SWDL_AUTOMATCH_IN

H
BOOTROM_BAD PATCH_ACT_TIMEOUT SWDL_CHGMNG_NO-

MATCH
COMMUN_FAIL PATCH_DEACT_TIMEOUT SWDL_COMMIT_FAIL
DBMS_ERROR PATCH_ERR SWDL_INPROCESS
DBMS_PROTECT_ PATCH_NOT_CONFIRM SWDL_NEPKGCHECK

MODE
DB_RESTORE_FAIL PATCH_PKGERR SWDL_PKGVER_MM

HARD_BAD POWER_FAIL SWDL_PKG_NOBDSOFT
HARD_ERR SECU_ALM SWDL_ROLLBACK_FAI

L
HSC_UNAVAIL SERVICE_CAPACITY_EXCEED SYNC_DISABLE

_LICENSE
K1_K2_M SERVICE_TYPE_EXCEED_LI- SYNC_FAIL

CENSE
K2_M SHELF_AREA_POWER_OVER SYSPARA_CFDB_NO-

SAME
MSSW_DIFFERENT SNCP_FAIL WRG_BD_TYPE
STORM_CUR_QUE XC_UNSWITCH LCS_FILE_NOT_EXIST

NUM_OVER
LCS_EXPIRED LCS_DAYS_OF_GRACE FEATURE_WITHOUT_LI

CENSE
2.2.22 TN52STG
BD_STATUS NO_BD_SOFT SYNC_F_M_SWITCH
CLK_NO_TRACE_M NO_ELABEL SYNC_LOCKOFF

ODE
COMMUN_FAIL OOL SYN_BAD
EXT_SYNC_LOS PATCHFILE_NOTEXIST TEMP_OVER
EXT_TIME_LOC PATCH_ERR TIME_LOS
HARD_BAD PATCH_NOT_CONFIRM TIME_NO_TRACE_MODE
HARD_ERR S1_SYN_CHANGE WRG_BD_TYPE
LTI SYNC_C_LOS
2.2.23 TN52STI
BD_STATUS WRG_BD_TYPE
2.2.24 TNL1STI
WRG_BD_TYPE BD_STATUS POWER_ABNORMAL

ALM_HANGUP
2.2.25 TNL2SEI1
BD_STATUS RELAY_ALARM_IGNORE WRG_BD_TYPE
LAN_LOC RELAY_ALARM_MAJOR RELAY_ALARM_MI-

NOR
RELAY_ALARM_CRITI-
CAL
2.2.26 TNL2SEI2
BD_STATUS LAN_LOC WRG_BD_TYPE
2.2.27 TNL2SXCM
BD_STATUS HARD_ERR TEMP_OVER
BUS_ERR NO_BD_SOFT WRG_BD_TYPE
COMMUN_FAIL NO_ELABEL HARD_BAD

Alarms and Performance Events Reference 3 Handling Common Alarms
3 Handling Common Alarms
About This Chapter
This topic describes how to handle common alarms.
Common Principle
Conform to the following principles when handling alarms:
l Handle root alarms and then correlative alarms.

According to the correlation rules of common alarms, handle the root alarms caused by a
fault or abnormal event and then the correlative alarms caused by the root alarms.
l Check the NMS and then NEs; check external factors and then internal factors.
On the NMS, remotely check NE alarms, analyze performance events, and then check NE
configurations. Afterward, check inter-NE links. Finally, check NE hardware onsite.
l Identify common causes and then special causes.
According to alarm handling experience and the information about other alarms, identify
the common causes and then the special causes of an alarm.
l Check software and then hardware.
If the alarm is caused by equipment faults, reset the board to rectify software faults and
then replace the board to rectify hardware faults.
Common Cause
External factors, such as operating environment, power supply voltage, equipment grounding,
and heat dissipation, may trigger various alarms that are reported transiently, intermittently, and
even regularly. The alarms include HARD_BAD, COMMUN_FAIL, BD_STATUS, R_LOS,
power, and error alarms.
l Operating environment:
The equipment room temperature and humidity do not meet the requirements for long-time
and short-time operation. For example, the environment is not clean or the ventilation is
poor.
l Power supply voltage:

The DC voltage cannot be supplied as required. In addition, the voltage fluctuates within
a wide range and is always 20% greater than the maximum value or 20% smaller than the
minimum value.
l Equipment grounding:
Equipment grounding resistance is greater than or equal to 1 ohm. In this case, equipment
is vulnerable to lightning strikes.
l Heat dissipation:
Equipment heat is not easily dissipated due to factors, such as blocked exhaust vents, dirty
air filter, or improperly working fans.
Precautions
CAUTION
Board removal and insertion or cold reset will interrupt services. If services that traverse a board
are not protected, exercise caution when removing, inserting, or cold resetting boards.
CAUTION
If faults cannot be located by performing loopback, modify configurations or replace
components to locate the fault.
All troubleshooting methods have advantages and disadvantages. Therefore, maintenance
personnel need to combine these methods for troubleshooting purposes. For details about
common troubleshooting methods, see "Common Methods of Locating Faults" in
Troubleshooting.
NOTE
l This document lists the alarm parameters displayed on the NMS. When attempting to view an alarm,
select it and view the alarm parameters on the tab.
l If an alarm fails to be cleared by referring to methods in this document, contact Huawei technical
support engineers to handle the alarm.
3.1 ALM_GFP_dLFD
3.2 APS_INDI
3.3 AU_AIS
3.4 AU_LOP
3.5 B1_EXC
3.6 BD_STATUS
3.7 BUS_ERR
3.8 COMMUN_FAIL
3.9 CLK_NO_TRACE_MODE

3.10 EXT_SYNC_LOS
3.11 FCS_ERR
3.12 HARD_BAD
3.13 IN_PWR_HIGH
3.14 IN_PWR_LOW
3.15 LINK_ERR
3.16 LOOP_ALM
3.17 LSR_WILL_DIE
3.18 LTI
3.19 MS_AIS
3.20 OUT_PWR_HIGH
3.21 OUT_PWR_LOW
3.22 POWER_ABNORMAL
3.23 POWER_FAIL
3.24 SYN_BAD
3.25 SYNC_C_LOS
3.26 R_LOS
3.27 R_LOF
3.28 TEMP_OVER
3.29 WRG_BD_TYPE

3.1 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the generic framing procedure (GFP) frame
is out of frame. This alarm occurs when the GFP state machine escapes from the SYNC state,
and is cleared when the state machine enters the SYNC state again.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System

During data transmission, if the board fails to align the GFP frame, the services are interrupted.
Possible Causes
l Cause 1: The settings of timeslots and other parameters of the VCTRUNKs at both ends
are inconsistent.
l Cause 2: The performance of the service transmission line degrades.
l Cause 3: A certain board is faulty.
Procedure
Step 1 Cause 1: The settings of timeslots and other parameters of the VCTRUNKs at both ends are
inconsistent.
1. Check whether the number of uplink (downlink) timeslots bound with the local VCTRUNK
is consistent with the number of downlink (uplink) timeslots bound with the peer
VCTRUNK.
If... Then...
The number of timeslots is Modify Number of Bound Paths at either end to

inconsistent ensure that the number of timeslots is consistent.
For details, see Feature DescriptionConfiguring
the Internal Port on an Ethernet Board. Then,
check whether the ALM_GFP_dLFD alarm is
cleared. If the alarm persists, go to the next step.

If... Then...
The number of timeslots is Go to the next step.

consistent
2. Double-click a desired NE. In the NE Explorer, choose Configuration > SDH Service
Configuration from the navigation tree.
3. Check whether the number of timeslots bound with the VCTRUNK matches cross-
connection settings.
If... Then...
The number of timeslots bound with Reconfigure the cross-connections or the

the VCTRUNK does not match cross- timeslots to be bound to the VCTRUNK. Then,
connection settings check whether the ALM_GFP_dLFD alarm is
cleared. If the alarm persists, go to the next
step.
The number of timeslots bound with Go to the next step.

the VCTRUNK matches cross-
connection settings
4. Check whether the service level is consistent between the SDH cross-connections at both
ends. If the service level is inconsistent, for example, the service level of the SDH cross-
connections at the local end is VC4 but that at the peer end is VC4-16C, reconfigure the
service level of SDH cross-connections to keep its consistency between both ends.
5. Check whether the ALM_GFP_dLFD alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The performance of the service transmission line degrades.

1. Check the transmission link for bit error and optical power alarms and errored block
performance events, which are generated due to loose or contaminated fiber connectors,
faulty optical fiber cables, or poor contact between optical components.
If... Then...
Alarms, such as B3_EXC, B3_SD, Clear the alarms or events. Then, check
IN_PWR_HIGH, and IN_PWR_LOW, whether the ALM_GFP_dLFD alarm is
or events, such as RSBBE, MSBBE, and cleared. If the alarm persists, go to Step 3.
HPBBE exist
None of the preceding alarms or Go to Step 3.

performance events exists
Step 3 Cause 3: A certain board is faulty.

1. Replace the board that reports the alarm. For details, see Parts ReplacementReplacing an
Ethernet Board.
2. Then, check whether the alarm is cleared. If the ALM_GFP_dLFD alarm persists, contact
Huawei technical support engineers to handle this alarm.
----End

Related Information
Cell Delimitation State Machine
The cell delimitation state machine is available in three states: HUNT, PRESYNC, and SYNC.
In the HUNT state, the state machine hunts the position of delimitating cells in the BYTE BY
BYTE manner. After finding a correct HCS, the state machine changes to the PRESYNC state.
In the PRESYNC state, the state machine locks the position of delimitating cells. After
consecutively receiving DELTA correct HCS cells, the state machine changes to the SYNC state.
In this case, the cell boundary is found. In the PRESYNC state, after receiving an incorrect HCS
cell, the state machine returns to the HUNT state. In the SYNC state, after consecutively
receiving ALPHA incorrect HCS cells, the state machine changes to the HUNT state. Otherwise,
it keeps in the SYNC state, as shown in the following figure.
3.2 APS_INDI
Description
The APS_INDI is an alarm indicating the APS state. This alarm is reported when the MSP is in
the switching state.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the

following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details

about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the MSP group where the switching occurs.
l 0x01: linear MSP group
l 0x02: ring MSP group
Parameter 2, Parameter 3 Indicates the ID of the MSP group.

l The APS_INDI alarm indicates the occurrence of a fiber cut or a terminal node failure,
which triggers the MSP switching.
l For a two-fiber ring MSP or a linear MSP, if a fiber cut or another fault occurs after the
occurrence of this alarm, the services are interrupted.
Possible Causes
l Cause 1: An external command is issued to initiate a switching (such as manual switching,
forced switching, exercise switching, and lockout of switching).
l Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD
alarm) that triggers an automatic MSP switching.
l Cause 3: The service board is faulty.
l Cause 4: The SCC board is faulty.
Procedure
Step 1 View this alarm on the NMS and determine the MSP group type and ID based on alarm
parameters.
Step 2 Cause 1: An external command is issued to initiate a switching (such as manual switching, forced
switching, exercise switching, and lockout of switching).
1. Query the MSP switching state. For details, see Supporting TasksQuerying and Clearing
the Switching Status.
If... Then...
The MSP group is in the state of manual Clear the switching state and verify that the
switching, forced switching, exercise alarm is cleared. If the alarm persists, go to
switching, or locked switching Step 3.
The MSP group is in none of the Go to Step 3.

preceding switching states
Step 3 Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm)
that triggers an automatic MSP switching.
1. Check whether the MSP group is in the automatic switching state.

If... Then...
The local NE reports the R_LOS, The MSP group enters the automatic switching
R_LOF, MS_AIS, or B2_EXC alarm state and reports the APS_INDI alarm. In this
case, clear the R_LOS, R_LOF, MS_AIS, or
B2_EXC alarm and check whether the
APS_INDI alarm is cleared.
If the APS_INDI alarm persists, go to the next
step.
The local NE reports the B2_SD alarm After you enable the SD switching condition,
the SD-related alarm can trigger the MSP
NOTE
switching. You can use either of the following
Both SF and SD switching conditions can methods to clear the APS_INDI alarm:
trigger automatic MSP switching. The
B2_SD alarm cannot trigger MSP l Disable SD switching. For details, see
switching by default but can be specified
Configuration GuideModifying Protection
as the SD switching condition to trigger
MSP switching. Subnet Parameters.
l Clear the B2_SD alarm first.
Check whether the APS_INDI alarm is cleared.
If the alarm persists, go to the next step.
The MSP group is in none of the Go to the next step.

preceding switching states
2. Query the revertive mode of the MSP group.
If... Then...
Revertive Mode is set to Revertive After the working path recovers, the services
are switched automatically from the
protection path to the working path only when
the preset wait to restore (WTR) time expires.
The APS_INDI alarm is cleared after the
switching is successful.
When the MS is automatically restored from
the switching state to the normal state, check
whether the APS_INDI alarm is cleared. If the
alarm persists, go to Step 4.
Revertive Mode is set to Non-Revertive After the working path recovers, the services
are not switched automatically from the
protection path to the working path and the
APS_INDI alarm persists.
To clear the alarm, manually switch the
services from the protection path to the
working path.
3. In the NE Explorer, select the NE, and choose Configuration > Linear MS or
Configuration > Ring MS from the navigation tree. In the Slot Mapping Settings area,

right-click the working unit or the protection unit of a protection group and choose the
desired switching mode from the shortcut menu.
4. After the manual switching is successful, check whether the APS_INDI alarm is cleared.
If the alarm persists, go to Step 4.
Step 4 Cause 3: The service board is faulty.

1. Check whether the service board where the multiplex section is configured is faulty.
If... Then...
A service board reports alarms indicating Replace the service board. For details, see
hardware faults, such as the HARD_BAD Supporting TasksReplacing Boards On-
alarm Site.
Check whether the alarm is cleared. If the
A service board reports no alarm Go to Step 5.

indicating hardware faults
Step 5 Cause 4: The SCC board is faulty.

1. Check whether the SCC board that reports alarms is faulty.
If... Then...
An SCC board reports alarms indicating Warm reset the SCC board. For details, see
hardware or software faults, such as the Supporting TasksResetting Boards.
HARD_BAD and HARD_BAD alarms
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
An SCC board reports no alarm indicating Contact Huawei technical support

hardware or software faults engineers to handle the alarm.
2. Replace the faulty SCC board. For details, see Parts ReplacementReplacing an SCC
Board. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
Revertive Mode
The Revertive Mode field can be set to Revertive or Non-Revertive. Generally, it is

recommended that you set Revertive Mode to Revertive.
l If you set Revertive Mode to Revertive, the services are switched automatically from the
protection path to the working path after the working path recovers.
l If you set Revertive Mode to Non-Revertive, the services are not switched automatically
from the protection path to the working path after the working path recovers, and the
services are still transmitted over the protection path.

3.3 AU_AIS
Description
The AU_AIS is an alarm indication of the administrative unit (AU). This alarm occurs when the
optical interface on the local NE receives the AU pointer of all 1s.
Attribute

Parameters
None.

l Without the network protection, the services in the VC-4 path that reports the alarm are
interrupted.
l The AU_AIS alarm is reported on the downstream NEs.
Possible Causes
l Cause 1: The local NE inserts the AIS alarm to the lower level circuit.
l Cause 2: The upstream NE inserts the AIS alarm to the downstream NE.
l Cause 3: The transmit boards on the upstream NE are faulty.
l Cause 4: The receive boards on the local NE are faulty.
Procedure
Step 1 Cause 1: The local NE inserts the AIS alarm to the lower level circuit.
1. On the NMS, check the local NE for severer alarms.
If... Then...
Severer alarms, such as the R_LOS, Clear these alarms and then check whether
R_LOF, B1_EXC, and B2_EXC alarms, the AU_AIS alarm is cleared. If the alarm
are reported persists, go to Step 2.
No severer alarm is reported Go to Step 2.
Step 2 Cause 2: The upstream NE inserts the AIS alarm to the downstream NE.
1. Check upstream NEs for severer alarms.

If... Then...
Any of the alarms listed in Table 3-1 Clear the alarm and check whether the
occurs AU_AIS alarm is cleared. If the alarm
persists, go to the next step.
None of the alarms listed in Table 3-1 Go to the next step.

occurs
2. Perform loopback to locate the upstream NE that initially generates the AU_AIS alarm.
Perform loopback on the receive and transmit ports of the board on the peer NE. For details,
see the Supporting Tasks. To loop back all boards, perform the following steps:
CAUTION
A loopback will interrupt services.
l Setting a Loopback on an SDH Optical Interface Board

l Setting a Loopback on an Ethernet Port
3. Check whether the AU_AIS alarm occurs on the peer NE after the loopback is performed.
If... Then...
The AU_AIS alarm occurs on the peer The peer NE has transmitted the AU_AIS
NE alarm to the local NE. In this case, go to the
next step.
No AU_AIS alarm occurs on the peer Go to Step 4.

NE
4. Perform loopback to locate the upstream NE that generates the AU_AIS alarm. Check the
service source board of the NE for severer alarms.
If... Then...
Any of the alarms listed in Table 3-1 Clear the alarm and check whether the
occurs AU_AIS alarm is cleared. If the alarm
persists, go to Step 4.
None of the alarms listed in Table 3-1 Go to Step 3.

occurs
Step 3 Cause 3: The transmit boards on the upstream NE are faulty.

1. Replace the transmit board that initially reports the AU_AIS alarm on the peer NE. For
details, see Supporting TasksReplacing Boards On-Site.
2. Check whether the AU_AIS alarm is cleared. If the alarm persists, replace the cross-connect
board of the peer NE. For details, see Parts ReplacementReplacing a Cross-Connect
Board.

3. Check whether the AU_AIS alarm is cleared. If the alarm persists, contact Huawei technical
Step 4 Cause 4: The receive boards on the local NE are faulty.

1. Replace the receive board that reports the alarm on the local NE. For details, see Supporting
TasksReplacing Boards On-Site.
2. Check whether the AU_AIS alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
Table 3-1 Alarms that may cause the AU_AIS alarm
R_LOS R_LOF MS_AIS
B1_EXC B1_SD B2_EXC
B2_SD AU_LOP B3_EXC
B3_SD HP_TIM HP_SLM
HP_UNEQ
3.4 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm is reported when the
optical port of the local NE receives eight consecutive frames that contain NDFs or invalid AU
pointers.
Attribute
Parameters
None.

l When this alarm occurs, the services on the VC-4 path are interrupted without network
protection.
l When this alarm occurs, the system automatically returns the HP_RDI alarm to the peer
NE by using the G1 byte, and the peer NE reports the HP_RDI alarm.

l When this alarm occurs, the AU_AIS alarm occurs on the downstream NEs.
Possible Causes
l Cause 1: The number of bit errors received by the local NE exceeds the upper threshold.
l Cause 2: The services transmitted by the peer NE and received by local NE are inconsistent
in the service concatenation level.
l Cause 3: Boards, such as the clock board, on the local NE are faulty.
l Cause 4: Boards, such as the clock board, on the peer NE are faulty.
Procedure
Step 1 Cause 1: The number of bit errors received by the local NE exceeds the upper threshold.
1. Check whether local NE reports the following bit error alarms:
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
2. If the local NE reports any of the preceding alarms, clear it and check whether the AU_LOP
alarm is cleared. If the local NE reports no bit error alarm, or the AU_LOP alarm persists
after bit error alarms are cleared, go to Step 2.
Step 2 Cause 2: The services transmitted by the peer NE and received by local NE are inconsistent in
the service concatenation level.
1. Check whether the services transmitted by the peer NE and received by local NE are
consistent in the service concatenation level.
If... Then...
Services transmitted by the peer NE and Reconfigure the service concatenation

received by local NE are inconsistent in level on the local and peer NEs and check
the service concatenation level whether the AU_LOP alarm is cleared. If
the alarm persists, go to Step 3.
Services transmitted by the peer NE and Go to Step 3.

received by local NE are consistent in the
service concatenation level
Step 3 Cause 3: Boards, such as the clock board, on the local NE are faulty.
1. Cold reset the local receive board on the NMS or directly remove and insert this board. For
details about how to cold reset the local receive board, see Supporting TasksResetting
Boards.
CAUTION
If services traverse the board are not protected, cold resetting the board will interrupt
services.

2. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the local receive
board. For details, see Supporting TasksReplacing Boards On-Site.
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, cold reset the local
cross-connect board on the NMS or directly remove and insert this board. For details about
how to cold reset the local cross-connect board, see Supporting TasksResetting Boards.
CAUTION
If there is no standby cross-connect board, cold resetting the active cross-connect board
may interrupt services.
4. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the local cross-
connect board. For details, see Parts ReplacementReplacing a Cross-Connect Board.
5. Check whether the AU_LOP alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: Boards, such as the clock board, on the peer NE are faulty.
1. Cold reset the peer transmit board on the NMS or directly remove and insert this board.
For details about how to cold reset the peer transmit board, see Supporting TasksResetting
Boards.
CAUTION
If services traverse the board are not protected, a board cold reset will interrupt services.
2. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the peer transmit
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, cold reset the peer cross-
connect and clock boards on the NMS or directly remove and insert these boards. For details
about how to cold reset the peer cross-connect and clock boards, see Supporting
TasksResetting Boards.
CAUTION
4. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace peer cross-
connect and clock boards. For details about how to replace the peer cross-connect board,
see Parts ReplacementReplacing a Cross-Connect Board. For details about how to replace
the peer clock board, see Parts ReplacementReplacing a Clock Board.
5. Check whether the AU_LOP alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End

Related Information
None.
3.5 B1_EXC
Description
The B1_EXC is an alarm indicating that the number of B1 bit errors exceeds the specified
threshold. This alarm is reported when the line board detects that the number of regenerator
section bit errors exceeds the specified threshold (default threshold: 10-3) by monitoring the B1
byte.
Attribute
Minor Service alarm
Parameters
None.

l When this alarm occurs, the quality of transmitted services has badly deteriorated.
l When this alarm occurs, the system automatically inserts the AU_AIS alarm in the cross-
connection direction.
Possible Causes
l Cause 1: The bit error threshold is not proper.
l Cause 2: The ambient environment is abnormal.
l Cause 3: Line performance deteriorates.
l Cause 4: The equipment is not grounded properly
l Cause 5: The local receive board is faulty.
l Cause 6: The peer transmit board is faulty.
l Cause 7: The clock configuration is incorrect, or the clock unit performance deteriorates
Procedure
Step 1 Cause 1: The bit error threshold is not proper.
1. Check the bit error threshold. If it is low, raise the threshold as required. For details, see
Supporting TasksSetting the Threshold for the Bit Error Alarm.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The ambient environment is abnormal.

1. Check the ambient temperature, air filter, and heat dissipation. For details, see the methods
of handling the TEMP_OVER alarm.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, check for external
electromagnetic interference sources, such as external electronic equipment, unstable
power supply, lightning, and high-voltage wires. If any of the electromagnetic interference
sources exist, take anti-interference measures.
Step 3 Cause 3: Line performance deteriorates.
1. On the NMS, check whether the transmit optical power of the peer board is within the
specified range, which is provided in Product Description. For details about how to check
the transmit optical power of the peer board, see Supporting TasksQuerying the Optical
Power.
NOTE
For detailed manufacturing information about an optical module, see Supporting TasksQuerying the
Board Manufacturer Information Report or Hardware DescriptionBar Codes of the Boards.
If... Then...
The transmit optical power of the peer board is out of range Go to Step 6.
The transmit optical power of the peer NE is within the specified Go to the next step.
range
2. On the NMS, check whether the transmit optical power of the local board is within the
specified range.
If... Then...
The transmit optical power of the local board is out of range Go to Step 5.
The transmit optical power of the local board is within the Go to the next step.
specified range
3. On the NMS, check whether the receive optical power of the local board is within the
specified range.
If... Then...
The receive optical power of the local Check the fiber ends, fiber connector, and
board is out of range optical cable in turn.
The receive optical power of the local Go to Step 5.

board is within the specified range
4. Check whether the fiber connector is properly connected.

If... Then...
The fiber connector is loose Properly connect the fiber connector. Check
whether the B1_EXC alarm is cleared. If the
The fiber connector is properly Go to the next step.

connected
5. Check whether the fiber connector is contaminated. For details, see Supporting
TasksChecking Optical Fiber Connectors.
If... Then...
The fiber connector is contaminated Clean the fiber connector. For details, see the
Supporting Tasks.
l Using the Fiber Cleaner to Clean Optical
Fiber Connectors
l Using the Lens Tissue to Clean Optical Fiber
Connectors
l Using the Dust-Free Cotton Bar to Clean
Optical Fiber Adapters, Optical Attenuators,
and Flanges
Check whether the B1_EXC alarm is cleared. If
the alarm persists, go to the next step.
The fiber connector is clean Go to the next step.
6. Check whether the radius of the roll into which the pigtail is coiled is less than 6 cm, and
check the optical cable for damage, sheath stripping, aging, fusion, and cut. If the radius is
less than 6 cm, re-roll the pigtail. If any damage, sheath stripping, aging, fusion, or cut is
found on the optical cable, replace it and check whether the B1_EXC alarm is cleared.
7. If the alarm persists, check whether the optical cable matches the optical interface board
in model type. Mismatch in model type may result in low fiber sensitivity, large dispersion,
and signal distortion, which will cause bit errors.
If... Then...
The optical cable does not match the Replace the fiber or line board as required
optical interface board in model type and check whether the B1_EXC alarm is
cleared.
The optical cable matches the optical Go to the next step.

interface board in model type
8. If the B1_EXC alarm persists, go to Step 4.
Step 4 Cause 4: The equipment is not grounded properly

1. Ensure that the equipment is properly grounding, for example, ensure that the PGND cable
is properly connected and the cabinet and ground busbar are properly connected.

Step 5 Cause 5: The local receive board is faulty.

1. Replace the local optical module or board. If a pluggable optical module is installed on the
board, replace the optical module. For details, see Parts ReplacementReplacing a Pluggable
Optical Module. If no pluggable optical module is installed on the board, replace the board.
For details, see Supporting TasksReplacing Boards On-Site.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, replace the local clock
board by referring to Step 7.
Step 6 Cause 6: The peer transmit board is faulty.

1. Replace the peer optical module or board. If a pluggable optical module is installed on the
board, replace the optical module. For details, see Parts ReplacementReplacing a Pluggable
Optical Module. If no pluggable optical module is installed on the board, replace the board.
For details, see Supporting TasksReplacing Boards On-Site.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, replace the peer clock
board by referring to Step 7.
Step 7 Cause 7: The clock configuration is incorrect, or the clock unit performance deteriorates
1. Check the local and peer clock sources for timing loop or asynchronization. If pointer
adjustment events or alarms, such as the AUPJCHIGH event or the SYN_BAD alarm, are
reported along with the B1_EXC alarm, clear the pointer adjustment events or alarms first.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, replace the local clock
board. For details, see Parts ReplacementReplacing a Clock Board.
3. Check whether the B1_EXC alarm is cleared. If the alarm persists, replace the peer clock
board. For details, see Parts ReplacementReplacing a Clock Board.
4. Check whether the B1_EXC alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
None.
3.6 BD_STATUS
Description
The BD_STATUS is an alarm indicating an offline physical board. This alarm is reported when
a user has configured a board on the NMS but has not installed the board.
Attribute
Major Equipment alarm

Parameters
None.

When this alarm occurs, NE configuration data cannot be applied to the board. As a result, service
configuration fails.
Possible Causes
l Cause 1: The board is being reset.
l Cause 2: The board is not installed or has poor contact with the backplane.
l Cause 3: The board is faulty or the backplane has bent pins.
Procedure
Step 1 Cause 1: The board is being reset.
1. View the board indicator to determine whether the board is being reset. For details, see
Hardware DescriptionIndicators. Alternatively, query historical resets of the board. For
details, see Supporting TasksQuerying the Operation Log of the NMS.
If... Then...
The board is being reset Wait until the reset is complete (about 5 minutes) and
check whether the BD_STATUS alarm is cleared.
The board is not being reset Go to Step 2.
2. Check whether the BD_STATUS alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The board is not installed or has poor contact with the backplane.
1. On the NMS, double-click the alarm-reporting NE in the Main Topology. Then, record the
logical-board type for the alarm-reporting slot on the NE Panel.
2. Check whether the physical board is installed.
If... Then...
The physical board is not installed Properly install the physical board that matches the
logical board.
Check whether the BD_STATUS alarm is cleared.
If the alarm persists, go to Step 3.
The physical board is installed Go to the next step.
3. Check the contact between the board and backplane.

If... Then...
If the contact is poor Remove and properly re-insert the board. Then, check whether
the BD_STATUS alarm is cleared. If the alarm persists, go to
Step 3.
If the contact is fine Go to Step 3.
Step 3 Cause 3: The board is faulty or the backplane has bent pins.
1. Replace the alarm-reporting board. For details, see Supporting TasksReplacing Boards On-
Site. Then, check whether the BD_STATUS alarm is cleared.
2. If the alarm persists, check whether the backplane has bent pins.
If... Then...
The backplane has bent pins Contact Huawei technical support engineers to repair
the bent pins. Then, properly re-insert the board.
The backplane has no bent pin Contact Huawei technical support engineers to handle
the alarm.
----End
Related Information
None.
3.7 BUS_ERR
Description
The BUS_ERR is an alarm indicating an error in the cross-connect board bus. This alarm is
reported when the cross-connect board detects an exception on the bus from the service board
to the cross-connect board.
Attribute
Critical Equipment alarm
Parameters

Name Meaning
Parameter 1 Indicates the bus type.

l 0x00: bus interconnecting the service and cross-connect boards
l 0x01: bus that aggregates the lower-order services on the lower-
order daughter board to the higher-order bus
l 0x02: bus that transmits services to the lower-order bus on the
lower-order daughter board
l 0x03: bus (ingress bus to the chip) that restore higher order
services to the lower-order bus on the lower-order daughter
board
l 0x04: bus (inter-chip bus) that restore higher order services to
the lower-order bus on the lower-order daughter board
l 0x05: bus that interconnects lower-order buses on the lower-
order daughter board
Parameter 2, Parameter 3 Indicate the global logical number of a bus.

l When parameter 1 is 0x00, parameters 2 and 3 indicate the
global logical number of a higher-order bus.
l When parameter 1 is a value other than 0x00, parameters 2 and
3 indicate the logical number of a bus on the lower-order
daughter board.

l When the alarm occurs, the services that traverse over the faulty bus are interrupted or have
bit errors.
l When both the active and standby cross-connect boards have the BUS_ERR alarm but no
severer alarm, such as HARD_BAD, no active/standby switching occurs. When only the
active cross-connect board has the HARD_BAD alarm, services are switched from the
active board to the standby board.
Possible Causes
l Cause 1: The service board does not match the cross-connect board in software version.
l Cause 3: The cross-connect board is faulty.
l Cause 4: The backplane bus from the service board to the cross-connect board is faulty.
Procedure
Step 1 Cause 1: The service board does not match the cross-connect board in software version.
1. Check whether the service board matches the cross-connect board in software version. For
details, see the software version mapping table in Supporting TasksQuerying the Board
Information Report.

If... Then...
Both boards match in software version Go to Step 2.
Both boards do not match in software Upgrade either board to the version matching
version that of the other board. For details, see the
OptiX OSN 9560 software upgrade guide.
Check whether the BUS_ERR alarm is
cleared. If the alarm persists, go to Step 2.

1. Check whether the cross-connect and service boards are properly installed. If either board
is installed improperly, install it properly and check whether the BUS_ERR alarm is
cleared.
2. If the alarm persists, reset the service board. For details, see Supporting TasksResetting
Boards. Then, check whether the BUS_ERR alarm is cleared.
NOTE
You can initially warm reset the service board. If the BUS_ERR alarm persists after the warm reset,
cold reset the board.
3. If the alarm persists, replace the service board. For details, see Supporting TasksReplacing
Boards On-Site. Then, check whether the BUS_ERR alarm is cleared.
CAUTION
Cold reset or replace the board only when the services traverse the board are protected.
Otherwise, cold resetting or replacing the board may interrupt services.
4. If the alarm persists, go to Step 3.
Step 3 Cause 3: The cross-connect board is faulty.

1. Reset the alarm-reporting cross-connect board. For details, see Supporting TasksResetting
Boards. Then, check whether the BUS_ERR alarm is cleared.
NOTE
You can initially warm reset the cross-connect board. If the BUS_ERR alarm persists after the warm
reset, cold reset the board.
2. If the alarm persists, replace the alarm-reporting cross-connect board. For details, see Parts
ReplacementReplacing a Cross-Connect Board. Then, check whether the BUS_ERR alarm
is cleared.
CAUTION
Replace the cross-connect board only when at least one standby cross-connect board is
working properly. Otherwise, replacing the board may interrupt services.

3. If the alarm persists, follow the preceding operations and reset or replace the other cross-
connect board that has not reported this alarm. Then, check whether the BUS_ERR alarm
is cleared.
Step 4 Cause 4: The backplane bus from the service board to the cross-connect board is faulty.
1. Contact Huawei technical support engineers to check whether the backplane has bent pins.
Replace the backplane if it is damaged.
----End
Related Information
None.
3.8 COMMUN_FAIL
Description
The COMMUN_FAIL is an alarm indicating that inter-board communication is interrupted. This
alarm is reported when the communication is interrupted between the SCC board and a non-
SCC board.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the path in which the alarm is generated.
l 0x00 0x01: path 1 of the RS485
l 0x00 0x02: path 2 of the RS485
l 0x00 0x03: inter-board Ethernet communication
l 0x00 0x04: inter-subrack Ethernet emergency path

When this alarm occurs, the NE configurations cannot be applied to a board or the board cannot
work. This may disable service configuration and protection switching and affect new services.

Possible Causes
A single board may report the COMMUN_FAIL alarm due to the following causes:
l Cause 1: The service board is being reset.
Multiple boards may report the COMMUN_FAIL alarm due to the following causes:
l Cause 1: The AUX or SEI board is faulty.
l Cause 2: The SCC or cross-connect board is faulty.
Procedure
Step 1 Cause 1: The service board is being reset.
1. View the service board indicator to determine whether the board is being reset. For details,
see Hardware DescriptionIndicators. Alternatively, query historical resets of the board.
For details, see Supporting TasksQuerying the Operation Log of the NMS.
If... Then...
The board is being reset Wait until the reset is complete (about 5 minutes) and
check whether the COMMUN_FAIL alarm is cleared.
The board is not being reset Go to Step 2.

1. Replace the alarm-reporting service board. For details, see Supporting TasksReplacing
Boards On-Site. Then, check whether the COMMUN_FAIL alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
Step 3 Cause 1: The AUX or SEI board is faulty.
1. Remove and insert the AUX and SEI boards and check whether the COMMUN_FAIL
alarm is cleared.
2. If the alarm persists, replace the AUX or SEI board. For details about how to replace the
AUX board, see Parts ReplacementReplacing an AUX Board. For details about how to
replace the SEI board, see Parts ReplacementReplacing an SEI Board. Then, check whether
the COMMUN_FAIL alarm is cleared.
Step 4 Cause 2: The SCC or cross-connect board is faulty.
1. Remove and insert the active SCC or active cross-connect board and check whether the
COMMUN_FAIL alarm is cleared.
2. If the alarm persists, replace the active SCC or active cross-connect board. For details about
how to replace the active SCC board, see Parts ReplacementReplacing an SCC Board. For
details about how to replace the active cross-connect board, see Parts
ReplacementReplacing a Cross-Connect Board. Then, check whether the
COMMUN_FAIL alarm is cleared.
----End

Related Information
None.
3.9 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE is an alarm indicating that a clock enters the non-locked mode.
This alarm is reported when a tributary or external clock loses the tracing clock source.
Attribute
Minor Equipment alarm
Parameters
None.

When this alarm occurs, the clock enters the non-locked mode. In this case, the system clock
quality deteriorates, which may result in asynchronous status between NEs and more service bit
errors.
Possible Causes
l Cause 1: When no priority table is configured, an NE clock traces a clock source by referring
to the default priority table.
l Cause 2: When a priority table is configured, an NE clock can trace only internal clock
sources.
Procedure
Step 1 Cause 1: When no priority table is configured, an NE clock traces a clock source by referring
to the default priority table.
1. Query the current priority table. If the table contains only internal clock sources, add other
available clock sources to the table. For details, see Feature DescriptionConfiguring NE
Clock Sources.
Step 2 Cause 2: When a priority table is configured, an NE clock can trace only internal clock sources.
1. Query the current priority table. If the table contains more than internal clock sources,
identify the cause of the failure to trace a non-internal clock source by performing the
following steps:
l Check the system for the SYNC_C_LOS alarm that indicates clock source loss. If the
the SYNC_C_LOS exists, clear it and check whether the CLK_NO_TRACE_MODE
alarm is cleared.

l Check the system for the SYN_BAD alarm that indicates a deteriorated clock source.
If the SYN_BAD alarm exists, clear it and check whether the
CLK_NO_TRACE_MODE alarm is cleared.
l If the alarm persists, check the SSM protocol status on the local and upstream NEs. If
the SSM protocol is enabled on the local NE but not upstream NEs, enable it on these
NEs and check whether the CLK_NO_TRACE_MODE alarm is cleared. For details,
see Feature DescriptionConfiguring the Clock Source Protection.
----End
Related Information
None.
3.10 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating that an external clock source is lost. This alarm is
reported when the system detects that an external clock source traced by a device is lost.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for a clock source.
Parameter 2 Indicates the slot ID for a clock source. This parameter has a fixed value 0xF0
for an external clock source.
Parameter 3 This parameter is reserved with its value fixed at 0x00.
Parameter 4 Indicates the port ID for a service board clock source.

Indicates the channel of a lost external clock source.
l 0x01: External clock source in channel 1 is lost.
l 0x02: External clock source in channel 2 is lost.


When this alarm occurs, a device fails to trace an external clock source. This may deteriorate
clock quality, affect service quality, and trigger pointer justification or bit errors.
Possible Causes
Configuration
l Cause 1: The configured input and output modes of an external clock do not match the
clock signal type.
l Cause 2: An NE clock is in free-run mode because clock source IDs are improperly
allocated.
Hardware
l Cause 3: The external-clock cable is misconnected or damaged.

l Cause 4: The clock board functions improperly.
l Cause 5: External-clock equipment is faulty.
Procedure
Step 1 View the alarm on the NMS and determine the channel of the lost external clock source according
to alarm parameters.
Step 2 Cause 1: The configured input and output modes of an external clock do not match the clock
signal type.
1. Check the input mode of the external clock source.
If... Then...
The input mode of the external According to the actual type of external-clock
clock source does not match the signal, set External Clock Source Mode to 2MHz
clock signal type or 2Mbit/s. For details, see Feature
DescriptionConfiguring NE Clock Sources.
Check whether the EXT_SYNC_LOS alarm is
The input mode of the external Go to Step 3.

clock source matches the type of
clock signal
Step 3 Cause 2: An NE clock is in free-run mode because clock source IDs are improperly allocated.
1. If the extended SSM protocol is enabled network wide, allocate IDs to clock sources by
conforming to clock ID planning principles. If an external clock source is allocated no ID,
or there are duplicate clock source IDs, NE clock sources will enter the free-run mode. For
details about how to check clock source ID configurations on NEs, see Feature
DescriptionConfiguring the Clock Source Protection.
2. If an external clock source is allocated no ID, or there are duplicate clock source IDs, correct
clock source ID configurations based on site requirements. Then, check whether the
EXT_SYNC_LOS alarm is cleared. If the alarm persists, go to Step 4.

Step 4 Cause 3: The external-clock cable is misconnected or damaged.

1. Check whether the clock input cable is connected to the external-clock interface or whether
the cable and interface match in impedance.
If... Then...
The clock input cable is not connected Properly connect the clock input fiber to the
to the external-clock interface or the external-clock interface and check whether the
cable and interface do not match in EXT_SYNC_LOS alarm is cleared. If the alarm
impedance persists, go to the next step.
The clock input cable is properly Go to the next step.

connected to the external-clock
interface
2. If only one external-clock cable reports the EXT_SYNC_LOS alarm, locate the faults by
interchanging both external-clock cables. If both external-clock cables report the
EXT_SYNC_LOS alarm, go to the next step.
If... Then...
The EXT_SYNC_LOS alarm is reported only when the original Go to the next step.
cable is present
The EXT_SYNC_LOS alarm persists even when the original Go to Step 5.

cable is replaced
3. Check the alarm-reporting external-clock cable for loose connection, imprint, or damage.
If the cable is loose connected or has imprint or damage, properly connect or replace it.
Then, check whether the EXT_SYNC_LOS alarm is cleared. If the alarm persists, go to
Step 5.
Step 5 Cause 4: The clock board functions improperly.

1. Cold reset the clock board on the NMS or directly remove and insert it. For details about
how to cold reset the clock board, see Supporting TasksResetting Boards.
2. Check whether the EXT_SYNC_LOS alarm is cleared. If the alarm persists, replace the
clock board. For details, see Parts ReplacementReplacing a Clock Board.
3. Check whether the EXT_SYNC_LOS alarm is cleared. If the alarm persists, go to Step
6.
Step 6 Cause 5: External-clock equipment is faulty.

1. Check whether an external clock source has reliable quality. Specifically, contact Huawei
technical support engineers to identify the DA value of the external clock source. If the
external clock source is unreliable, replace it.
----End
Related Information
None.

3.11 FCS_ERR
Description
The FCS_ERR is an alarm indicating a frame check sequence (FCS) check error. This alarm is
reported when the local end encounters an error during the FCS check for frames encapsulated
in GFP format.
NOTE
This alarm applies only to the GFP service received by the local end.
An idle frame contains no FCS field. Therefore, errors will occur if the idle frame encapsulated in GFP
format is detected during the FCS check.
Attribute
Critical Communication alarm
Parameters
None.

l When this alarm occurs due to inconsistent encapsulation protocols, services will be
interrupted.
l When this alarm occurs due to system bit errors, services will lose packets or be interrupted.
Possible Causes
l Cause 1: Encapsulation protocol parameters are inconsistently set on the local and peer
ends.
l Cause 2: The performance of the optical path that transmits services deteriorates.
l Cause 3: The board is faulty.
Procedure
Step 1 View this alarm on the NMS and determine the ID of the VCTRUNK port that reports the alarm.
Step 2 Cause 1: Encapsulation protocol parameters are inconsistently set on the local and peer ends.
1. Check whether the Mapping Protocol is consistent between both ends. If the two ends use
different protocols (for example, the local end uses the GFP protocol, whereas the peer end
uses the LAPS protocol), configure the protocol to keep its consistency between both ends.
Then, check whether the extension option setting is consistent between both ends. If the
extension option setting is inconsistent between both ends (for example, after the GFP
protocol is configured at both ends, Extension Option is set to Yes on the local end whereas
Extension Option is set to No on the peer end), consistently set the extension option.

2. Check whether Scramble and Set Inverse Value for CRC are consistent between both
ends. If they are inconsistently set, consistently set the parameters on both ends. For details,
see Feature DescriptionConfiguring the Internal Port on an Ethernet Board.
3. Check whether the FCS_ERR alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: The performance of the optical path that transmits services deteriorates.
1. Check the transmission link for bit error and optical power alarms and errored block
performance events, which are generated due to loose or contaminated fiber connectors,
faulty optical fiber cables, or poor contact between optical components.
If... Then...
Alarms, such as B3_EXC, B3_SD, Clear them first. Then, check whether
IN_PWR_HIGH, and IN_PWR_LOW, or the FCS_ERR alarm is cleared. If the
events, such as RSBBE, MSBBE, and alarm persists, go to Step 4.
HPBBE exist
None of the preceding alarms or Go to Step 4.

performance events exists
Step 4 Cause 3: The board is faulty.

1. Replace the board that reports the FCS_ERR alarm. For details, see Parts
ReplacementReplacing an Ethernet Board.
2. Check whether the FCS_ERR alarm is cleared. If the alarm persists, contact Huawei
----End
Related Information
None.
3.12 HARD_BAD
Description
The HARD_BAD is an alarm indicating a hardware failure.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates a key-chip failure for a clock board.

Indicates the following faults for other boards:
l 0x01: The power module is working improperly.
l 0x02: The board is improperly installed or has poor contact with the
backplane. For example, the board is loose installed.
l 0x03: 38M system clock 1 encounters an exception.
l 0x05: 2M clock source encounters an exception.
l 0x06: The digital phase-locked loop encounters an exception.
l 0x07: The 38M service clock is lost.
l 0x08: The bus encounters an exception.
l 0x09: The TPS protection board encounters an exception.
l 0x0A: The primary crystal oscillator stops oscillating.
l 0x0B: The frequency offset of the primary crystal oscillator is large.
l 0x0C: The secondary crystal oscillator stops oscillating.
l 0x0D: The processor (CPU/DSP/coprocessor) is faulty.
l 0x0E: Storage components are faulty.
l 0x0F: The programmable logical device is faulty.
l 0x10: SDH components are faulty.
l 0x11: Data communication components are faulty.
l 0x12: Clock components are faulty.
l 0x13: Interface components are faulty.
l 0x14: Power components are faulty.
l 0x15: Other faults occur.
l 0x16: The analog phase-locked loop encounters an exception.
l 0x17: The 32M clock fails.
l 0x1A: The cross-connect chip loop is faulty.
l 0x1B: The 8k in-service line of the board is of low level.

Name Meaning
Parameter 2 Indicates the following faults for a clock board:

l 0x01: The local CPU crystal oscillator is lost.
l 0x02: The local daughter board loses its 2M crystal oscillator.
l 0x02: The local daughter board loses its 38M clock source.
l 0x04: The peer board loses its 38M clock source.
l 0x05: The peer board loses the 2K clock packet frame header.
l 0x06: The local daughter board loses the frame header 1 of the 2K clock
packet.
packet.
When parameter 1 is 0x08 for other boards, bus A encounters an exception if
parameter 2 is 0x01, and bus B encounters an exception if parameter 2 is 0x02.
When parameter 1 is not 0x08 for other boards, parameter 2 is 0xFF.
Parameter 3 Indicates hardware failures on the time module for a clock board.

When this alarm occurs, board and services are affected.
Possible Causes
l Cause 1: The NE power supply encounters an exception.
l Cause 2: The board is faulty or has poor contact with the backplane.
Procedure
Step 1 Cause 1: The NE power supply encounters an exception.
1. Check whether the power supply works properly by referring to the
POWER_ABNORMAL alarm. If the power supply works improperly or the voltage is
unstable, for example, the NE is immediately powered on after being powered off,
reconnect the power supply or replace it with a stable-voltage power supply. For details,
see Installation GuidePowering On Subracks.
2. Check whether the HARD_BAD alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The board is faulty or has poor contact with the backplane.
1. Check whether contact of the alarm-reporting board with the backplane. If the contact is
poor, remove and reinsert the board. Then, check whether the HARD_BAD alarm is
cleared.
2. If the alarm persists, replace the board. For details, see Supporting TasksReplacing Boards
On-Site.
3. Check whether the HARD_BAD alarm is cleared. If the alarm persists, contact Huawei
----End

Related Information
None.
3.13 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating a high receive optical power. This alarm is reported
when a board detects that the actual receive optical power exceeds the specified upper threshold.
Attribute
Parameters
None.

When this alarm occurs, bit errors occur in the services on the optical port. In addition, high
receive optical power will damage the laser.
Possible Causes
l Cause 1: The optical power threshold is not set properly.
l Cause 2: The transmit optical power is high at the peer end.
l Cause 3: The alarm-reporting board is faulty.
Procedure
Step 1 Cause 1: The optical power threshold is not set properly.
1. Query the optical-module details for the alarm-reporting board. For manufacturing details
about the optical module, see Supporting TasksQuerying the Board Manufacturer
Information Report or Hardware DescriptionBar Codes of the Boards.
2. Check whether the optical power threshold is set properly. For details, see Supporting
TasksQuerying the Optical Power.If the optical power threshold is improperly set, reset
Input Power Reference Lower Threshold and Input Power Reference Upper
Threshold based on board receiver sensitivity or optical-power overload indicators. For
details about board optical-power indicators, see Product Description.
3. Check whether the IN_PWR_HIGH alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The transmit optical power is high at the peer end.
1. On the NMS, check whether the transmit optical power of the peer board connected to the
local alarm-reporting board is above the specified upper threshold, or whether the peer
board reports the OUT_PWR_HIGH alarm. For details, see Supporting TasksQuerying
the Optical Power.

If... Then...
The transmit optical power is above the specified upper Go to the next step.
threshold
The transmit optical power is proper Go to Step 3.
2. Replace the optical module if it is pluggable on the peer board. For details, see Parts
ReplacementReplacing a Pluggable Optical Module. Replace the board if the optical
module is unpluggable. For details, see Supporting TasksReplacing Boards On-Site.
3. Check whether the IN_PWR_HIGH alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The alarm-reporting board is faulty.

1. If the receive optical power of the alarm-reporting board is proper, this board may be faulty.
In this case, replace the board. For details, see Supporting TasksReplacing Boards On-
Site.
----End
Related Information
None.
3.14 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating a low receive optical power. This alarm is reported
when a board detects that the actual receive optical power exceeds the specified lower threshold.
Attribute
Parameters
None.

When this alarm occurs, plenty of bit errors occur in the received signals, which affects service
receiving.
Possible Causes
l Cause 1: The optical power threshold is not set properly.
l Cause 2: The fiber connector is loose or contaminated.

l Cause 3: The transmit optical power is low at the peer end.

Procedure
Step 1 Cause 1: The optical power threshold is not set properly.
1. Query the optical-module details for the alarm-reporting board. For manufacturing details
about the optical module, see Supporting TasksQuerying the Board Manufacturer
Information Report or Hardware DescriptionBar Codes of the Boards.
2. Check whether the optical power threshold is set properly. For details, see Supporting
TasksQuerying the Optical Power.If the optical power threshold is improperly set, reset
Input Power Reference Lower Threshold and Input Power Reference Upper
Threshold based on board receiver sensitivity or optical-power overload indicators. For
details about board optical-power indicators, see Product Description.
3. Check whether the IN_PWR_LOW alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The fiber connector is loose or contaminated.

1. On the NMS, check whether the transmit optical power of the peer board connected to the
local alarm-reporting board is below the specified lower threshold, or whether the peer
board reports the OUT_PWR_LOW alarm. For details, see Supporting TasksQuerying the
Optical Power.
If... Then...
The transmit optical power is below the Go to Step 3.

specified lower threshold
The transmit optical power is proper Perform the following steps at the local and
peer ends:
2. Check whether the bending radius of the pigtail is within the normal range. If the bending
radius is smaller than 6 cm, re-roll the pigtail. Then, check whether the IN_PWR_LOW
alarm is cleared.
3. If the alarm persists, verify that the fiber connector is properly connected. Then, check
whether the IN_PWR_LOW alarm is cleared.
4. If the alarm persists, check whether the fiber connector is contaminated. For details, see
Supporting TasksChecking Optical Fiber Connectors. If the fiber connector is
contaminated, clean it by referring to Supporting Tasks.
l Using the Fiber Cleaner to Clean Optical Fiber Connectors
l Using the Lens Tissue to Clean Optical Fiber Connectors
l Using the Dust-Free Cotton Bar to Clean Optical Fiber Adapters, Optical Attenuators,
and Flanges
Step 3 Cause 3: The transmit optical power is low at the peer end.
1. Replace the optical module if it is pluggable on the peer board. For details, see Parts
ReplacementReplacing a Pluggable Optical Module. Replace the board if the optical
module is unpluggable. For details, see Supporting TasksReplacing Boards On-Site.


1. If the receive optical power of the alarm-reporting board is proper, this board may be faulty.
In this case, replace the board. For details, see Supporting TasksReplacing Boards On-
Site.
----End
Related Information
None.
3.15 LINK_ERR
Description
The LINK_ERR is an alarm indicating data link errors. This alarm is reported when connections
are incorrect and port negotiation fails on an Ethernet.
Attribute
Parameters
None.

When the alarm occurs during data transmission, the network port negotiation fails. The services
cannot be received and thus the services are interrupted.
Possible Causes
l Cause 1: The transmit and receive ports work in different modes.
l Cause 2: Ethernet boards at both ends have different optical modules, or the types of the
two optical modules do not match those of the fibers connected to them.
l Cause 3: The fibers or cables connected to the Ethernet ports fail.
Procedure
Step 1 View the alarm on the NMS, and determine the board that reports the alarm and the ID of the
port that reports the alarm according to alarm parameters.
Step 2 Cause 1: The transmit and receive ports work in different modes.
1. Check whether the transmit and receive ports work in the same mode. If they work in
different modes, for example, a port works in autonegotiation mode while the other port

works in non-autonegotiation mode, configure the working mode to keep its consistency
between both ports. Feature DescriptionConfiguring the External Port on an Ethernet Board
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: Ethernet boards at both ends have different optical modules, or the types of the two
optical modules do not match those of the fibers connected to them.
1. Check whether the Ethernet boards at both ends have the same optical module. If they have
different optical modules, such as single- and multi-mode optical modules, replace the
optical module on either board to keep its consistency. If the optical module on the board
is pluggable, replace the optical module. For details, see Parts ReplacementReplacing a
Pluggable Optical Module.
2. Then, check whether the LINK_ERR alarm is cleared. If the alarm persists, check whether
the types of the two optical modules match those of the fibers connected to them. If the
type of an optical module does not match that of its fiber, for example, a single-mode fiber
is connected to a multi-mode optical module, replace the optical module or fiber to keep
the type consistency between them.
Step 4 Cause 3: The fibers or cables connected to the Ethernet ports fail.
1. Check whether the fibers or cables are properly connected to the Ethernet ports. If the fibers
or cables are improperly connected or even fail, re-connect or replace them.

1. Use a network cable to loop back signals on the Ethernet port that reports the alarm. Then,
check whether the LINK_ERR alarm is cleared.
If... Then...
The alarm is cleared Replace the peer board. For details, see Supporting
The alarm persists Replace the local board. For details, see Supporting
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, contact Huawei
----End
Related Information
None.
3.16 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating the service loopback.

Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the number of a path. Parameter 2 indicates the optical-
port loopback alarm when being set to 0x01.
Parameter 3 Indicates the loopback type.

l 0x00: optical- or electrical- port inloop
l 0x01: optical- or electrical- port outloop
l 0x02: channel inloop
l 0x03: channel outloop
l 0x04:loopback on the client
l 0x05: loopback on the optical multiplexer
l 0x06: SPI inloop
l 0x07: SPI outloop
l 0x08: ATM layer inloop
l 0x09: ATM layer outloop
l 0x0A: PHY layer inloop
l 0x0B: PHY layer outloop
l 0x0C: MAC layer inloop
l 0x0D: MAC layer outloop
l 0x0E: VC-4 timeslot inloop
l 0x0F: VC-4 timeslot outloop
l 0x10: VC-3 timeslot inloop
l 0x11: VC-3 timeslot outloop
l 0x12: VC-12 timeslot inloop
l 0x13: VC-12 timeslot outloop
l 0x14: intermediate frequency (IF) outloop
l 0x15: IF inloop
l 0x16: radio frequency (RF) inloop
l 0xFF: any of the preceding loopback types


When this alarm occurs, services are interrupted.
Possible Causes
Cause 1: A loopback command is issued for the test or maintenance purpose.
Procedure
Step 1 View the alarm on the NMS and determine the port that reports the alarm.
Step 2 Cause 1: A loopback command is issued for the test or maintenance purpose.
1. Check whether the loopback is configured for the test or maintenance purpose. If the test
or maintenance is complete, eliminate the loopback on the port by referring to Supporting
Tasks.
l Setting a Loopback on an SDH Optical Interface Board
l Setting a Loopback on an Ethernet Port
----End
Related Information
None.
3.17 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the life cycle of a laser expires. This alarm is
reported when the laser can no longer be used.
Attribute
Parameters
None.

When this alarm occurs, bit errors occur in services. If the board is not replaced in a timely
manner, services will be interrupted.
Possible Causes
l Cause 1: The laser ages.

l Cause 2: The detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The laser ages.
If... Then...
The optical module is pluggable on the Replace the optical module. For details, see Parts
board ReplacementReplacing a Pluggable Optical
Module.
Check whether the LSR_WILL_DIE alarm is
The optical module is unpluggable on Go to Step 2.

the board
Step 2 Cause 2: The detection circuit of the board is faulty.

1. Replace the board whose detection circuit is faulty. For details, see Supporting
2. Check whether the LSR_WILL_DIE alarm is cleared. If the alarm persists, contact Huawei
----End
Related Information
None.
3.18 LTI
Description
The LTI is an alarm indicating that an NE clock is abnormal. This alarm is reported when the
synchronous source is lost.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the type of lost synchronous source.

l 0x01: Synchronous sources of the system clock are lost.
l 0x02: All the synchronous sources of the first 2M phase-locked source are
lost.
l 0x03: All the synchronous sources of the second 2M phase-locked source are
lost.

When this alarm occurs, the current NE clock is abnormal. Inefficient troubleshooting will result
in deteriorated clock quality, which may cause more bit errors and pointer justification events.
Possible Causes
l Cause 1: External synchronous sources are lost.
l Cause 2: Line synchronous sources are lost.
l Cause 3: Synchronous sources are set to Non-revertive or Lockout.
l Cause 4: The clock unit encounters an exception.
Procedure
Step 1 View the alarm on the NMS and determine the type of lost synchronous source.
1. Check the type of synchronous source traced by the NE clock, such as the external or line
synchronous source. For details, see Feature DescriptionConfiguring NE Clock Sources.
2. Perform the following steps according to the type of the lost synchronous source.
If... Then...
The external synchronous source is lost Go to Step 2.
The line synchronous source is lost Go to Step 3.
Step 2 Cause 1: External synchronous sources are lost.

1. Sequentially verify that the configurations, input cable, and transmit signals of the external
clock are proper. For details, see the methods of handling the EXT_SYNC_LOS alarm.
2. Check whether the LTI alarm is cleared. If the alarm persists, go to Step 4.
Step 3 Cause 2: Line synchronous sources are lost.

1. The transmit clock signals are lost when line synchronous source services are interrupted
or have a large number of bit errors. On the NMS, check whether the clock signal loss has
triggered clock source switchover. For details, see Feature DescriptionConfiguring
Switching Conditions for Clock Sources.
2. Check whether the line board where the clock source resides reports severer alarms.

If... Then...
The alarms, such as R_LOS, R_LOF, Clear these alarms and check whether the
B2_EXC, and AIS, that can trigger clock LTI alarm is cleared. If the alarm persists,
source switching exist go to the next step.
None of the preceding alarms exists Go to the next step.
3. On the NMS, cold reset or directly remove and insert the line board. For details about how
to reset a line board, see Supporting TasksResetting Boards.
CAUTION
If services traversing the board are not protected, cold resetting the board will interrupt
services.
4. Check whether the LTI alarm is cleared after about 5 minutes. If the alarm persists, replace
the line board. For details, see Parts ReplacementReplacing an SDH Board.
5. Check whether the LTI alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 3: Synchronous sources are set to Non-revertive or Lockout.

1. On the NMS, check whether the synchronous source is set to Non-revertive.
If... Then...
The synchronous source is set to Set it to Auto-revertive by referring to Feature

Non-revertive DescriptionConfiguring the Clock Source
Reversion.
Check whether the LTI alarm is cleared. If the
The synchronous source is not set to Go to the next step.

Non-revertive
2. On the NMS, check whether the synchronous source is set to Lockout.
If... Then...
The synchronous source is set to Set it to Unlock.Feature DescriptionSwitching

Lockout a Clock Source.
Check whether the LTI alarm is cleared. If the
The synchronous source is not set to Go to Step 5.

Lockout
Step 5 Cause 4: The clock unit encounters an exception.

1. On the NMS, cold reset or directly remove and insert the clock board. For details about
how to reset a clock board, see Supporting TasksResetting Boards.
2. Check whether the LTI alarm is cleared. If the alarm persists, replace the clock board. For
details, see Parts ReplacementReplacing a Clock Board.
3. Check whether the LTI alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
None.
3.19 MS_AIS
Description
The MS_AIS is an alarm indicating that multiplex section signals are unavailable on the optical
port that reports this alarm. This alarm is reported when the receive optical port of the local NE
has received five consecutive frames in which the last three bits of the K2 byte are 111.
Attribute
Parameters
None.

l When this alarm occurs, services are interrupted.
l When this alarm occurs, the system automatically returns the RDI message to the peer NE.
Then, the peer NE reports the MS_RDI alarm.
l When this alarm occurs, the AU_AIS alarm occurs on the downstream NE.
Possible Causes
l Cause 1: The local receive board is faulty.
l Cause 2: The active and standby cross-connect boards on the upstream NE are not detected.
l Cause 3: The transmit or cross-connect board on the upstream NE is faulty.
Procedure
Step 1 Cause 1: The local receive board is faulty.

1. Cold reset the local receive board on the NMS or directly remove and insert the board. For
details about how to cold reset a board, see Supporting TasksResetting Boards. Then, check
whether the alarm is cleared.
CAUTION
If services on the board are not protected, cold resetting the board interrupts services.
2. If the alarm persists, replace the local receive board. For details, see Supporting
TasksReplacing Boards On-Site. Then, check whether the alarm is cleared.
Step 2 Cause 2: The active and standby cross-connect boards on the upstream NE are not detected.
1. Check whether the active and standby cross-connect boards are loose on the upstream NE.
If yes, insert the boards firmly. Then, check whether the alarm is cleared.
2. If the alarm persists, cold reset the cross-connect boards on the NMS. For details, see
Supporting TasksResetting Boards. Then, check whether the alarm is cleared.
CAUTION
Step 3 Cause 3: The transmit or cross-connect board on the upstream NE is faulty.

1. Replace the transmit board on the upstream NE. For details, see Supporting TasksReplacing
Boards On-Site. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the cross-connect board on the upstream NE. For details, see
Parts ReplacementReplacing a Cross-Connect Board. Then, check whether the alarm is
cleared.
----End
Related Information
None.
3.20 OUT_PWR_HIGH
Description
The OUT_PWR_HIGH is an alarm indicating that the output optical power of a laser is above
the upper threshold. This alarm is reported when the board detects that the actual output optical
power of the laser exceeds the upper threshold.

Attribute
Parameters
None.

l If the output optical power is above the upper threshold, and no optical attenuator is installed
at the receive end of the laser, the input optical power will be above the upper threshold.
As a result, the receive module may be damaged.
l If the high optical power is caused by a laser module fault or board fault, the board is
functioning improperly. As a result, service receiving and transmission is affected.
Possible Causes
Cause 1: The transmit optical module of the laser is faulty, or the board is faulty.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the alarm.
Step 2 Cause 1: The transmit optical module of the laser is faulty, or the board is faulty.
1. Replace the optical module if it is pluggable on the board. For details, see Parts
ReplacementReplacing a Pluggable Optical Module. In other cases, replace the faulty
----End
Related Information
None.
3.21 OUT_PWR_LOW
Description
The OUT_PWR_LOW is an alarm indicating that the output optical power of a laser is below
the lower threshold. This alarm is reported when the board detects that the actual output optical
power of the laser is below the lower threshold.

Attribute
Parameters
None.

When this alarm occurs, the output optical power of the laser is below the lower threshold. As
a result, bit errors occur in the services.
Possible Causes
l Cause 1: The laser is deteriorating.
l Cause 2: The board has hardware faults.
Procedure
Step 1 Cause 1: The laser is deteriorating.Cause 2: The board has hardware faults.
1. Replace the optical module if it is pluggable on the board. For details, see Parts
ReplacementReplacing a Pluggable Optical Module. In other cases, replace the faulty
----End
Related Information
None.
3.22 POWER_ABNORMAL
Description
The POWER_ABNORMAL is an alarm indicating a power supply failure. This alarm is reported
when the power supply of the board encounters en exception.
Attribute
Parameters


Name Meaning
Parameter 1 Specifies whether the POWER_ABNORMAL alarm occurs. If the bit is 1, the
alarm occurs. If the bit is 0, the alarm does not occur.
l bit[0]: 3.3 V voltage
l bit[2]: 5 V voltage
l bit[5]: -5 V voltage
l bit[0]: output of the power supply module
l bit[1]: output of the standby power supply module
l bit[2]: 3.3 V channel B voltage
NOTE
bit[0] and bit[1] are effective only bit[0] of parameter 1 is 1.
l bit[3]: 2.5 V channel C voltage
l bit[4]: 2.5 V channel D voltage
l bit[5]: 2.5 V channel E voltage
l bit[7]: 3.3 V channel D voltage

Name Meaning
l bit[3]: 5 V channel B voltage
l bit[4]: 12 V channel B voltage

When this alarm occurs, the power supply is working improperly. As a result, the board may
function improperly.
Possible Causes
l Cause 1: The external power supply works improperly. For example, the power supply may
have undervoltage problem or the voltage fluctuates sharply.
l Cause 2: The power module on the local board malfunctions.
Procedure
Step 1 View the alarm on the NMS and determine the alarm-reporting board.
If... Then...
Multiple boards report the The external power supply is working

POWER_ABNORMAL alarm improperly. Go to Step 2.
A single board reports the The board may be faulty. Go to Step

POWER_ABNORMAL alarm 3.
Step 2 Cause 1: The external power supply works improperly. For example, the power supply may have
undervoltage problem or the voltage fluctuates sharply.
1. If the circuit breaker for the input power supply of the subrack is turned off, the power
cables on the subrack are incorrectly connected, or the connector of the power cables is
loose or firmly installed, the NE detects that the voltage is out of range and then reports the
POWER_ABNORMAL alarm. Check whether the circuit breaker on the subrack is turned
on, the power cables are properly connected to the external power supply device, DC power
distribution unit, power boards on the equipment, and whether the connectors of the power
cables are connected properly. For details, see Installation GuidePowering On Subracks.
2. Check whether the alarm is cleared. If not, replace the PDU and check whether the alarm
is cleared. If the alarm persists, contact Huawei technical support engineers to handle the
alarm.
Step 3 Cause 2: The power module on the local board malfunctions.
1. On the NMS, cold reset or directly remove and insert the alarm-reporting board. For details
about how to reset a board, see Supporting TasksResetting Boards.

CAUTION
2. Check whether the alarm is cleared. If not, replace the alarm-reporting board. For details,
see Parts ReplacementReplacing an SDH Board.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
3.23 POWER_FAIL
Description
The POWER_FAIL is an alarm indicating a power supply fault, for example, overvoltage,
undervoltage, or the battery on the SCC board has no charge.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the status of power supply.

l 0x05: The battery on the SCC board has no charge.
l 0x06: The active power supply fails.
l 0x07: The standby power supply fails.
l 0x12: The 12 V active power supply is over-voltage.
l 0x13: The 12 V active power supply is under-voltage.
l 0x14: The 12 V standby power supply is over-voltage.
l 0x15: The 12 V standby power supply is under-voltage.
l 0x41: The 3.3 V active power supply is over-voltage.
l 0x42: The 3.3 V active power supply is under-voltage.
l 0x4F: The 48 V active power supply is over-voltage.
l 0x50: The 48 V active power supply is under-voltage.
l 0x51: The 48 V standby power supply is over-voltage.
l 0x52: The 48 V standby power supply is under-voltage.
l 0x53: The -48 V fan power supply is under-voltage.
l 0x54: The -48 V fan power supply is over-voltage.

l When the POWER_FAIL alarm occurs on the SCC board, the system time is lost if the
system is powered off.
l When the POWER_FAIL alarm occurs on a non-SCC board:
– An active/standby power supply switchover occurs if the active power supply on the
board fails but the standby power supply works properly. The switchover does not affect
services but has a potential risk to the services.
– Services may be interrupted if both the active and standby power supply on the board
fail.
Possible Causes
l Cause 1: If the alarm occurs on the SCC board, the battery on the SCC board does not
supply power or has no charge.
l Cause 2: If the alarm occurs on a non-SCC board, the power module on the board fails or
is aged.
Procedure
Step 1 Cause 1: If the alarm occurs on the SCC board, the battery on the SCC board does not supply
power or has no charge.
1. Check whether the jumper on the SCC board is correctly set. For details about the jumper
settings, see Hardware DescriptionDIP Switches and Jumpers. An incorrect jumper setting
causes the POWER_FAIL alarm.
2. If the jumper is incorrectly set, modify the setting.

3. Check whether the alarm is cleared. If not, replace the SCC board. For details, see Parts
ReplacementReplacing an SCC Board.
Step 2 Cause 2: If the alarm occurs on a non-SCC board, the power module on the board fails or is
aged.
1. Replace the alarm-reporting board. For details, see Parts Replacement.
----End
Related Information
None.
3.24 SYN_BAD
Description
The SYN_BAD is an alarm indicating the quality deterioration of a clock synchronization
source. This alarm is reported when the quality of the clock synchronization source that is traced
by the equipment deteriorates.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for the clock source.
Parameter 2 Indicates the slot ID for the clock source. The value is permanently set to 0xF0
Parameter 3 This parameter is reserved with a fixed value of 0x00.

When this alarm occurs, the quality of the clock source deteriorates. Tracing the clock source
may cause bit errors in the services.

Possible Causes
l Cause 1: The quality of the traced external clock source deteriorates.
l Cause 2: The quality of the traced line clock source deteriorates.
l Cause 3: The clock board functions improperly.
Procedure
Step 1 Query the clock source that the equipment traces.Feature DescriptionViewing Clock
Synchronization Status
If... Then...
The external clock source reports the alarm Go to Step 2.
The line clock source reports the alarm Go to Step 3.
Step 2 Cause 1: The quality of the traced external clock source deteriorates.
1. Check whether input mode of the external clock signal matches that of the external clock
signal. For details, see the method of handling the EXT_SYNC_LOS alarm. Then, check
whether the SYN_BAD alarm is cleared. If the alarm persists, go to the next step.
2. Check whether the external clock cable is loose, pressed, or damaged. If yes, properly
connect the cable connector or replace the cable. Then, check whether the SYN_BAD alarm
is cleared. If the alarm persists, go to the next step.
3. Check whether an external clock source has reliable quality. You can contact Huawei
technical support engineers to identify the DA value of the external clock source. If the
external clock source has unreliable quality, replace it.
4. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 3 Cause 2: The quality of the traced line clock source deteriorates.
1. If the line performance of the traced clock source deteriorates, the precision of the clock
source decreases, and the quality of the output clock signal is poor. On the NMS, check
whether severer bit error alarms or performance events are reported on the board where the
clock source resides.
If... Then...
Alarms such as B1_EXC, B1_SD, See the methods of handling these alarms
B2_EXC, and B2_SD, or performance and performance events to clear the clock
events such as RSBBE are reported alarm caused by bit errors.
Check whether the SYN_BAD alarm is
cleared. If the alarm persists, go to the next
step.
None of severer bit error alarms or Go to the next step.

performance events is reported
2. On the NMS, cold reset or directly remove and insert the line board. For details about how
to reset a board, see Supporting TasksResetting Boards.

CAUTION
3. Check whether the SYNC_C_LOS alarm is cleared after about 5 minutes. If not, replace
the line board. For details, see Parts ReplacementReplacing an SDH Board.
Step 4 Cause 3: The clock board functions improperly.

how to reset a board, see Supporting TasksResetting Boards.
2. Check whether the alarm is cleared. If not, replace the timing board. For details, see Parts
ReplacementReplacing a Clock Board.
----End
Related Information
None.
3.25 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating a synchronization-source-level loss. This alarm is
reported when the clock source of the service board is lost in the priority table.
Attribute
Warning Equipment alarm
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for the clock source.

Name Meaning
Parameter 2 Indicates the slot ID for the clock source. The value is permanently set to 0xF0

When this alarm occurs, the external clock is lost. The equipment cannot trace this lost external
clock. In this case, if only the internal clock source can be used, bit errors may occur in the
services.
Possible Causes
l Cause 1: Input signals are lost on the optical or electrical interface that the clock source is
connected to.
l Cause 3: The clock board is faulty.
Procedure
Step 1 Cause 1: Input signals are lost on the optical or electrical interface that the clock source is
connected to.
1. On the NMS, check whether alarms, such as R_LOS and R_LOF, occur on the service
board. If yes, clear the alarms first. Then, check whether the SYNC_C_LOS alarm is
cleared.
2. If the SYNC_C_LOS alarm persists, go to Step 2.

1. On the NMS, cold reset or directly remove and insert the service board. For details about
CAUTION
2. Check whether the SYNC_C_LOS alarm is cleared after about 5 minutes. If not, replace
the service board. For details, see Supporting TasksReplacing Boards On-Site.
Step 3 Cause 3: The clock board is faulty.


2. Check whether the alarm is cleared. If not, replace the timing board. For details, see Parts
ReplacementReplacing a Clock Board.
----End
Related Information
None.
3.26 R_LOS
Description
The R_LOS is an alarm indicating that signals are lost on the receive side.
Attribute
Parameters
None.

When this alarm occurs, either of the following will interrupt services on the receive side of the
line:
l The system automatically inserts an AIS signal to the downstream NE.
l The system automatically sends an MS_RDI signal to the upstream NE so that the upstream
NE reports the MS_RDI alarm.
If a data board reports an R_LOS alarm, the Ethernet port enters the link-down state.
If an E-Line service is configured between the Ethernet port and the corresponding VCTRUNK
port, the VCTRUNK port may insert a management frame containing the client signal fail (CSF)
signal to the downstream NE.
Possible Causes
l Cause 1: The local optical port is unused.
l Cause 2: The peer laser is disabled so that no optical signal is input.
l Cause 3: The fiber is cut or the line performance deteriorates.
l Cause 4: The local receive board is faulty so that signals fail to be received.
l Cause 5: The peer transmit board or cross-connect board is faulty so that signals fail to be
transmitted.

Procedure
Step 1 View the alarm on the NMS and determine the ID of the alarm-reporting port.
Step 2 Cause 1: The local optical port is unused.

1. Check whether the alarm-reporting optical port is unused or the specified fiber is not
connected to the optical port. If the specified fiber is not connected to the optical port, use
a fiber to connect the receive and transmit interfaces of the optical port.
If... Then...
The optical port is unused or the No action is required. To clear the R_LOS
specified fiber is not connected to the alarm, mask the alarm or use a fiber to
optical port connect the receive and transmit interfaces
of the optical port.
NOTE
Masking the R_LOS alarm may trigger other
alarms.
CAUTION
Ensure that the receive optical power is within the
specified range when performing a hardware
loopback on the optical port.
The optical port is in use and the Go to Step 3.

specified fiber is connected to the optical
port
Step 3 Cause 2: The peer laser is disabled so that no optical signal is input.
1. Check whether the laser at the peer port is disabled.
If... Then...
The laser is disabled Enable the laser. For details, see Supporting TasksEnabling/
Disabling Lasers. Then, check whether the alarm is cleared. If the
The laser is enabled Go to Step 4.
Step 4 Cause 3: The fiber is cut or the line performance deteriorates.

1. Check whether the output optical power of the peer board is within the specified range,
which is provided in Product Description. For details about how to check the output optical
power of a board, see Supporting TasksQuerying the Optical Power.
NOTE
If... Then...
The output optical power of the peer board is out of range Go to Step 6.

If... Then...
The output optical power of the peer board is within the Go to the next step.
specified range
2. Use a fiber to connect the receive and transmit ports of the local receive board. For details,
see Supporting TasksHardware Loopback.
CAUTION
A loopback interrupts services. Ensure that the input optical power is within the specified
range when performing a hardware loopback. You can add an optical attenuator at the
receive optical interface of the optical port based on the optical power specifications for
the board.
If... Then...
The R_LOS alarm persists Go to Step 5.
The R_LOS alarm is cleared Repeat steps Step 4.3 to Step 4.6 to check the pigtails
and fiber connectors on the local and peer NEs.
3. Check whether the radius of the roll into which the pigtail is coiled is less than 6 cm. If the
radius is less than 6 cm, re-roll the pigtail. Then, check whether the alarm is cleared.
4. If the alarm persists, check whether the pigtail is correctly connected to the optical port.
If... Then...
The pigtail is connected incorrectly Correctly connect the pigtail between the optical
boards in the subrack based on site situations.
Then, check whether the alarm is cleared. If the
The pigtail is connected correctly Go to the next step.
5. Ensure that the pigtail is securely connected to the optical port. Then, check whether the
alarm is cleared.
contaminated, clean the fiber connector. For details, see the Supporting Tasks.
and Flanges
Check whether the alarm is cleared. If the alarm persists, go to the next step.
7. Use an optical time-domain reflectometer (OTDR) to check whether a fiber cut occurs on
the transmission line and to further locate the position of the fiber cut. For details about
how to use an OTDR, see the OTDR operation guide.

If... Then...
A fiber cut occurs on the transmission line Replace the optical fiber. Check whether
the alarm is cleared. If the alarm persists,
go to Step 5.
No fiber cut occurs on the transmission line Go to Step 5.
Step 5 Cause 4: The local receive board is faulty so that signals fail to be received.
1. Replace the optical module if it is pluggable on the alarm-reporting board. For details, see
Parts ReplacementReplacing a Pluggable Optical Module. Replace the alarm-reporting
board if the optical module is unpluggable. For details, see Supporting TasksReplacing
Boards On-Site.
Step 6 Cause 5: The peer transmit board or cross-connect board is faulty so that signals fail to be
transmitted.
1. IReplace the optical module if it is pluggable on the alarm-reporting board. For details, see
Parts ReplacementReplacing a Pluggable Optical Module. Replace the alarm-reporting
board if the optical module is unpluggable. For details, see Supporting TasksReplacing
Boards On-Site. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the peer cross-connect board. For details, see Parts
ReplacementReplacing a Cross-Connect Board.
----End
Related Information
None.
3.27 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost on the receive side of the line. This alarm
is reported when the local optical port receives five consecutive frames that do not contain correct
A1 and A2 bytes.
Attribute
Parameters
None.


l When this alarm occurs, services are interrupted, and the local NE inserts an AIS signal to
the downstream NE.
l When this alarm occurs, the system automatically returns an MS_RDI signal to the
upstream NE. Then, the upstream NE reports the MS_RDI alarm.
Possible Causes
l Cause 1: Two boards at different rates are interconnected.
l Cause 2: The transmit cable is faulty, and the fiber connector is loose or contaminated.
l Cause 3: The local receive board is faulty so that the frame structure is lost.
l Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is
lost.
Procedure
Step 1 View the alarm on the NMS and determine the alarm-reporting port according to alarm
parameters.
Step 2 Cause 1: Two boards at different rates are interconnected.

1. An improper fiber connection may cause an interconnection of two boards at different rates,
which triggers the R_LOF alarm. Check whether the optical fiber is properly connected. If
not, correct the optical fiber connection. For details, see Commissioning GuideChecking
Networkwide Fiber Connections. Then, check whether the alarm is cleared.
2. If the alarm persists, check whether the types of the two interconnected boards are the same.
For example, when a board that supports the FEC function is interconnected with a board
that does not support the FEC function, the R_LOF alarm will be reported if the rates of
the two boards are inconsistent.
3. Select two boards with the same rate. Then, check whether the alarm is cleared. If the alarm
Step 3 Cause 2: The transmit cable is faulty, and the fiber connector is loose or contaminated.
1. Check whether the output optical power of the peer board is within the normal range. For
details about the optical power indicators for boards, see Product Description. For details
about how to check the output optical power of a board, see Supporting TasksQuerying the
Optical Power.
NOTE
If... Then...
The output optical power of the peer board is out of range Go to Step 5.
The output optical power of the peer board is within the normal Go to the next step.
range
2. On the NMS, check whether the input optical power of the local board is within the normal
range.

If... Then...
The input optical power of the local board is below the lower Go to the next step.
threshold
The input optical power of the local board is above the upper Go to Step 4.
threshold
3. Check whether the bending radius of the pigtail is within the normal range. If the bending
radius is smaller than 6 cm, re-roll the pigtail. Then, check whether the alarm is cleared.
4. If the alarm persists, properly connect the pigtail to the optical port on the board. Then,
check whether the alarm is cleared.
contaminated, clean the fiber connector. For details, see Supporting Tasks.
and Flanges
6. Check whether the optical cable is aged, damaged, or pressed. If yes, replace the optical
cable. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is lost.
1. Perform a hardware inloop on the port that reports the alarm on the local NE. For details,
see Supporting TasksHardware Loopback.
CAUTION
A loopback interrupts services. Ensure that the optical power is within the normal range
when performing a hardware inloop. You can add an optical attenuator for the receive
optical interface according to the optical power specifications for the board.
If... Then...
The R_LOF alarm persists The local board is faulty. Go to the next step.
The R_LOF alarm is cleared Go to Step 5.
2. Replace the local alarm-reporting board. Replace the optical module if it is pluggable on
the board. For details, see Parts ReplacementReplacing a Pluggable Optical Module.
Replace the board if the optical module is unpluggable. For details, see Supporting
Step 5 Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is lost.
1. Replace the peer board. Replace the optical module if it is pluggable on the board. For
details, see Parts ReplacementReplacing a Pluggable Optical Module. Replace the board

if the optical module is unpluggable. For details, see Supporting TasksReplacing Boards
On-Site. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the peer cross-connect board. For details, see Parts
ReplacementReplacing a Cross-Connect Board.
----End
Related Information
None.
3.28 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the operating temperature of the board exceeds
the threshold. This alarm is reported when the system detects that the operating temperature of
the board is above or below the lower threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the threshold-crossing type of the board operating temperature.

l 0x01: The operating temperature of the board is above the upper threshold.
l 0x02: The operating temperature of the board is below the lower threshold.

When this alarm occurs, the system is in a high-risk state. A long-time high-risk state may cause
bit errors and service interruption. Handle this alarm in a timely manner.
Possible Causes
l Cause 1: The air filter is covered with dust.

l Cause 2: The fan has stopped working.

l Cause 3: The ambient temperature is out of range due to a fault on the cooler or heater
equipment.
Procedure
Step 1 Cause 1: The air filter is covered with dust.
1. Feel the wind and its temperature at the air exhaust vent to check whether heat dissipation
is impeded due to the dusty air filter.
2. If heat dissipation is impeded due to the dusty air filter, remove and clean the air filter. For
details, see Routine MaintenanceCleaning Air Filters.
Step 2 Cause 2: The fan has stopped working.

1. Check the operating status of the fan in the subrack. For details, see the method of handling
the FAN_FAIL.
Step 3 Cause 3: The ambient temperature is out of range due to a fault on the cooler or heater equipment.
1. If the temperature is higher than 45°C or lower than 0°C, use a cooler or heater to decrease
or increase the ambient temperature.

1. Replace the alarm-reporting board. For details, see Supporting TasksReplacing Boards On-
Site.
----End
Related Information
None.
3.29 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating an incorrect board type. This alarm is reported
when the configured logical board type is inconsistent with the physical board type.
Attribute

Parameters
None.

When this alarm occurs, the existing services and the system are not affected but the services
cannot be configured in the alarm-reporting slot.
Possible Causes
l Cause 1: The configured logical board type is inconsistent with the physical board type.
l Cause 2: The software version does not match the hardware version on the board.
Procedure
Step 1 Cause 1: The configured logical board type is inconsistent with the physical board type.
1. Check whether the logical board or physical board configurations are incorrect based on
project configuration requirements. In the Main Topology, double-click the NE icon to
enter the NE panel. On the NE Panel, check whether the interface type of the configured
logical board is consistent with that of the actual physical board.
If... Then...
The type of the physical interface On the NMS, delete the original logical
board is correct interface board and add another one. For
details, see Configuration GuideAdding
Boards.
The type of the logical interface board Replace the physical interface board. For
is correct details, see Supporting TasksReplacing
Boards On-Site.
2. check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The software version does not match the hardware version on the board.
1. Contact Huawei technical support engineers to check whether the software version matches
the hardware version on the board. If not, reload the board software or replace the board.
2. check whether the alarm is cleared. If the alarm persists, go to Step 3.

1. Replace the alarm-reporting board. For details, see the methods of replacing boards in Parts
Replacement.
----End
Related Information
None.

Alarms and Performance Events Reference 4 Other Alarm Clearing
4 Other Alarm Clearing
About This Chapter
This chapter describes the methods for handling other alarms.
Common Principle
Conform to the following principles when handling alarms:
l Handle root alarms and then correlative alarms.

According to the correlation rules of common alarms, handle the root alarms caused by a
fault or abnormal event and then the correlative alarms caused by the root alarms.
l Check the NMS and then NEs; check external factors and then internal factors.
On the NMS, remotely check NE alarms, analyze performance events, and then check NE
configurations. Afterward, check inter-NE links. Finally, check NE hardware onsite.
l Identify common causes and then special causes.
According to alarm handling experience and the information about other alarms, identify
the common causes and then the special causes of an alarm.
l Check software and then hardware.
If the alarm is caused by equipment faults, reset the board to rectify software faults and
then replace the board to rectify hardware faults.
Common Cause
External factors, such as operating environment, power supply voltage, equipment grounding,
and heat dissipation, may trigger various alarms that are reported transiently, intermittently, and
even regularly. The alarms include HARD_BAD, COMMUN_FAIL, BD_STATUS, R_LOS,
power, and error alarms.
l Operating environment:
The equipment room temperature and humidity do not meet the requirements for long-time
and short-time operation. For example, the environment is not clean or the ventilation is
poor.
l Power supply voltage:

The DC voltage cannot be supplied as required. In addition, the voltage fluctuates within
a wide range and is always 20% greater than the maximum value or 20% smaller than the
minimum value.
l Equipment grounding:
Equipment grounding resistance is greater than or equal to 1 ohm. In this case, equipment
is vulnerable to lightning strikes.
l Heat dissipation:
Equipment heat is not easily dissipated due to factors, such as blocked exhaust vents, dirty
air filter, or improperly working fans.
Precautions
CAUTION
Board removal and insertion or cold reset will interrupt services. If services that traverse a board
are not protected, exercise caution when removing, inserting, or cold resetting boards.
CAUTION
If faults cannot be located by performing loopback, modify configurations or replace
components to locate the fault.
All troubleshooting methods have advantages and disadvantages. Therefore, maintenance
personnel need to combine these methods for troubleshooting purposes. For details about
common troubleshooting methods, see "Common Methods of Locating Faults" in
Troubleshooting.
NOTE
l This document lists the alarm parameters displayed on the NMS. When attempting to view an alarm,
select it and view the alarm parameters on the tab.
l If an alarm fails to be cleared by referring to methods in this document, contact Huawei technical
4.1 AD_CHECK_FAIL
4.2 ALM_ALS
4.3 ALM_GFP_dCSF
4.4 ALM_HANGUP
4.5 APS_FAIL
4.6 APS_MANUAL_STOP
4.7 B1_SD
4.8 B2_EXC
4.9 B2_SD

4.10 B3_EXC
4.11 B3_EXC_VC3
4.12 B3_EXC_VC4
4.13 B3_SD
4.14 B3_SD_VC3
4.15 B3_SD_VC4
4.16 BD_NOT_INSTALLED
4.17 BDID_ERROR
4.18 BEFFEC_EXC
4.19 BOOTROM_BAD
4.20 C2_VCAIS
4.21 CHIP_ABN
4.22 DB_RESTORE_FAIL
4.23 DBMS_ERROR
4.24 DBMS_PROTECT_MODE
4.25 DLAG_PROTECT_FAIL
4.26 DSP_LOAD_FAIL
4.27 ETH_CFM_LOC
4.28 ETH_CFM_MACSTATUS
4.29 ETH_CFM_MISMERGE
4.30 ETH_CFM_RDI
4.31 ETH_CFM_UNEXPERI
4.32 ETHOAM_DISCOVER_FAIL
4.33 ETHOAM_RMT_LOOP
4.34 ETHOAM_RMT_SD
4.35 ETHOAM_SELF_LOOP
4.36 ETHOAM_VCG_SELF_LOOP
4.37 EX_ETHOAM_CC_LOS
4.38 EX_ETHOAM_MPID_CNFLCT
4.39 EXT_TIME_LOC
4.40 FAN_FAIL
4.41 FAN_FAULT
4.42 FEATURE_WITHOUT_LICENSE

4.43 FEC_LOF
4.44 FEC_OOF
4.45 FPGA_ABN
4.46 FSELECT_STG
4.47 FWD_PKT_LO
4.48 GAINDATA_MIS
4.49 HARD_ERR
4.50 HP_LOM
4.51 HP_RDI
4.52 HP_REI
4.53 HP_SLM
4.54 HP_TIM
4.55 HP_UNEQ
4.56 HSC_UNAVAIL
4.57 IN_PWR_FAIL
4.58 J0_MM
4.59 K1_K2_M
4.60 K2_M
4.61 LAG_PORT_FAIL
4.62 LAN_LOC
4.63 LASER_HAZARD_WARNING
4.64 LASER_MODULE_MISMATCH
4.65 LASER_SHUT
4.66 LCAS_FOPR
4.67 LCAS_FOPT
4.68 LCAS_PLCR
4.69 LCAS_PLCT
4.70 LCAS_TLCR
4.71 LCAS_TLCT
4.72 LCS_DAYS_OF_GRACE
4.73 LCS_EXPIRED
4.74 LCS_FILE_NOT_EXIST
4.75 LOCK_CUR_FAIL

4.76 LOCKPOW_MIS
4.77 LP_RDI_VC3
4.78 LP_SLM_VC3
4.79 LP_UNEQ_VC3
4.80 LPT_RFI
4.81 LSR_COOL_ALM
4.82 LSR_INVALID
4.83 MS_APS_INDI_EX
4.84 MS_RDI
4.85 MS_REI
4.86 MSSW_DIFFERENT
4.87 MULTI_RPL_OWNER
4.88 MUT_LOS
4.89 NEBD_XC_DIF
4.90 NESF_LOST
4.91 NESTATE_INSTALL
4.92 NO_BD_PARA
4.93 NO_BD_SOFT
4.94 NO_ELABEL
4.95 NODEID_MM
4.96 OA_LOW_GAIN
4.97 ODU_AIS
4.98 ODU_LCK
4.99 ODU_OCI
4.100 OH_LOOP
4.101 OMS_BDI
4.102 OMS_BDI_O
4.103 OMS_BDI_P
4.104 OMS_FDI
4.105 OMS_FDI_O
4.106 OMS_FDI_P
4.107 OMS_SSF
4.108 OMS_SSF_O

4.109 OMS_SSF_P
4.110 OOL
4.111 OPA_FAIL_INDI
4.112 OTU_AIS
4.113 OTU_LOF
4.114 OTU_LOM
4.115 OUT_PWR_ABN
4.116 PATCH_ACT_TIMEOUT
4.117 PATCH_DEACT_TIMEOUT
4.118 PATCH_ERR
4.119 PATCH_NOT_CONFIRM
4.120 PATCH_PKGERR
4.121 PATCHFILE_NOTEXIST
4.122 PORT_MODULE_OFFLINE
4.123 PM_BDI
4.124 PM_BEI
4.125 PM_BIP8_OVER
4.126 PM_BIP8_SD
4.127 PM_TIM
4.128 PUM_BCM_ALM
4.129 PUM_TEM_ALM
4.130 PUMP_COOL_EXC
4.131 R_LOC
4.132 RELAY_ALARM_CRITICAL
4.133 RELAY_ALARM_IGNORE
4.134 RELAY_ALARM_MAJOR
4.135 RELAY_ALARM_MINOR
4.136 RTC_FAIL
4.137 S1_SYN_CHANGE
4.138 SECU_ALM
4.139 SERVICE_CAPACITY_EXCEED_LICENSE
4.140 SERVICE_TYPE_EXCEED_LICENSE
4.141 SHELF_AREA_POWER_OVER

4.142 SLAVE_WORKING
4.143 SM_BDI
4.144 SM_BEI
4.145 SM_BIP8_OVER
4.146 SM_BIP8_SD
4.147 SM_IAE
4.148 SM_TIM
4.149 SNCP_FAIL
4.150 SO_SK_MISMATCH
4.151 STORM_CUR_QUENUM_OVER
4.152 SUBRACK_ID_CONFLICT
4.153 SUBRACK_ID_MISMATCH
4.154 SUBRACK_LOOP
4.155 SUBRACK_TYPE_MISMATCH
4.156 SUM_INPWR_HI
4.157 SUM_INPWR_LOW
4.158 SWDL_ACTIVATED_TIMEOUT
4.159 SWDL_AUTOMATCH_INH
4.160 SWDL_CHGMNG_NOMATCH
4.161 SWDL_COMMIT_FAIL
4.162 SWDL_INPROCESS
4.163 SWDL_NEPKGCHECK
4.164 SWDL_PKG_NOBDSOFT
4.165 SWDL_PKGVER_MM
4.166 SWDL_ROLLBACK_FAIL
4.167 SYNC_DISABLE
4.168 SYNC_F_M_SWITCH
4.169 SYNC_FAIL
4.170 SYN_LOCKOFF
4.171 SYSPARA_CFDB_NOSAME
4.172 T_LOSEX
4.173 TD
4.174 TEM_HA

4.175 TEM_LA
4.176 TEST_STATUS
4.177 TF
4.178 THUNDERALM
4.179 TIME_LOS
4.180 TIME_NO_TRACE_MODE
4.181 TR_LOC
4.182 TU_AIS_VC3
4.183 TU_LOP_VC3
4.184 VCAT_LOA
4.185 VCAT_LOM_VC3
4.186 VCAT_LOM_VC4
4.187 VOA_ADJUST_FAIL
4.188 W_R_FAIL
4.189 WAVEDATA_MIS
4.190 XC_UNSWITCH

4.1 AD_CHECK_FAIL
Description
The AD_CHECK_FAIL is an alarm indicating a self-check failure of the AD chip. This alarm
is reported when the AD chip on a board is faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the serial number of the AD chip. For example, The value 0x01
indicates the first AD chip

l When this alarm occurs, the services may be interrupted, or the system may malfunction.
l When this alarm occurs, maintenance engineers cannot query the parameters related to the
AD chip, such as the input or output optical power of a board, the back facet current, and
the cooling current. This prevents them from learning the operating performance and
potential risks of the network in real time.
Possible Causes
The board has hardware faults.
Procedure
Step 1 Replace the board that reports this alarm.
----End
Related Information
None.

4.2 ALM_ALS
Description
The ALM_ALS is an alarm indicating automatic laser shutdown. This alarm is reported when
the laser is automatically shut down due to the R_LOS alarm generated for the optical port.
Attribute
Parameters
None.

This alarm indicates that the automatic laser shutdown function is enabled, which does not affect
the system.
Possible Causes
A user has enabled the automatic laser shutdown function.
Procedure
Step 1 If the user disables the automatic laser shutdown function, this alarm will not be reported.
----End
Related Information
None.
4.3 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that GFP client signals are lost. When the source
receives no GFP client signal, it sends a management frame to the sink. This alarm is reported
when the sink receives the management frame.

Attribute
Parameters
None.

When this alarm occurs during data transmission, services will lose packets or be interrupted.
Possible Causes
l The source interface module is incorrect. For example, the optical module does not exist
or match, or the optical or electrical signal is lost.
l The source physical link fails and cannot receive physical signals.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port that reports the alarm.
Step 2 Check whether the physical link where the source VCTRUNK port resides is functioning
properly. If the physical link fails due to optical-fiber damage, replace the optical fiber and check
whether the ALM_GFP_dCSF alarm is cleared.
Step 3 If the alarm persists, check whether the source interface module runs properly. If the source
interface module runs improperly, replace it.
Step 4 If the alarm persists, replace the board that reports the alarm.
----End
Related Information
None.
4.4 ALM_HANGUP
Description
The ALM_HANGUP is an alarm indicating that an orderwire phone is long in the off-hook state.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates a phone number.

l This alarm does not affect local-NE services and communications.
l This alarm is reported to prompt a user to hang up the phone.
Possible Causes
l The orderwire phone of the local NE is long in the off-hook state.
l Hardware faults occur.
Procedure
Step 1 Check whether the orderwire phone is hung up. If it is in the off-hook state, hang it up and check
whether the ALM_HANGUP alarm is cleared.
----End
Related Information
None.
4.5 APS_FAIL
Description
The APS_FAIL is an alarm indicating a multiplex section protection (MSP) switching failure.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the type of the MSP group where the switching occurs.
Parameter 2, Parameter 3 Indicates the ID of the MSP group.

When this alarm occurs, services cannot be switched. In addition, if the existing path cannot be
used, services are interrupted.
Possible Causes
l MSP parameters are incorrectly configured.
l The MSP configuration is lost.
l The board is faulty.
Procedure
Step 1 Verify that network-wide MSP configuration is correct. For ring MSs, check the optical-fiber
connection. For linear MSs, check working and protection optical-fiber connections or MSP
switching mode. After MSP configuration is corrected, check whether the APS_FAIL alarm is
cleared.
Step 2 If the alarm persists, verify that network-wide MSP-related protocols are properly running. If
the protocols are improperly running, restart them. Then, check whether the APS_FAIL alarm
is cleared.
Step 3 If the alarm persists, replace the board that reports this alarm.
----End
Related Information
None.
4.6 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.

Attribute
Minor Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group.

Parameter 2 Indicates the ID of the MSP group.

When this alarm occurs, the MSP switching protocol does not work, which causes the MSP
failure.
Possible Causes
The MSP protocol is manually stopped.
Procedure
Step 1 Locate the MSP subnet where the MSP protocol is stopped on the NMS.
Step 2 Start the MSP protocol.
----End
Related Information
None.
4.7 B1_SD
Description
The B1_SD is an alarm indicating regenerator section signal deterioration. This alarm is reported
when the local board receives deteriorated SDH frames and the bit error rate of the regenerator
section exceeds the signal deterioration threshold (10-6).

Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the quality of transmitted services has deteriorated.
Possible Causes
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check whether the alarm-reporting board runs in an equipment room with a temperature higher
than 45°C or lower than 0°C for a long period of time. If the temperature is higher than 45°C or
lower than 0°C, adjust it into the normal range and check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the alarm-reporting board has a proper receive optical power.
If... Then...
The receive optical power is proper Go to Step 3.
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 3 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
The transmit optical power is proper Perform the following steps:

If... Then...
The transmit optical power is not proper Go to Step 6.
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber connector
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
Step 4 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 5 If the alarm persists, check whether the local receive board malfunctions. If the board has no
pluggable optical module and malfunctions, replace the board. If the board has a pluggable
optical module and malfunctions, replace the optical module.
Step 6 If the alarm persists, check whether the peer transmit board malfunctions. If the board has no
Step 7 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.8 B2_EXC
Description
The B2_EXC is an alarm indicating that the number of B2 bit errors exceeds the specified
threshold. This alarm is reported when the board detects that the number of multiplex section
bit errors exceeds the specified threshold (default threshold: 10-3) by monitoring the B2 byte.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, the quality of transmitted services has badly deteriorated.

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

----End
Related Information
None.
4.9 B2_SD
Description
The B2_SD is an alarm indicating multiplex section signal deterioration. This alarm is reported
when the local board detects that the number of multiplex section bit errors exceeds the B2_SD
alarm threshold (10-6) but remains below the B2_EXC alarm threshold (default threshold:
10-3) by monitoring the B2 byte.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the quality of transmitted services has deteriorated.
Possible Causes
Procedure

If... Then...
If... Then...
----End
Related Information
None.

4.10 B3_EXC
Description
The B3_EXC is an alarm indicating that the number of the higher order path (HP) B3 bit errors
exceeds the specified threshold. This alarm is reported when a board detects that the number of
the HP bit errors exceeds the specified threshold (default threshold: 10-3) by monitoring the B3
byte.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, path level services have bit errors.
Possible Causes
Procedure
If... Then...

If... Then...
----End
Related Information
None.
4.11 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the number of lower order path (LP) VC-3 B3
bit errors exceeds the specified threshold. This alarm is reported when a board detects that the
number of the VC-3 bit errors exceeds the B3_EXC alarm threshold by monitoring the B3 byte.

Attribute
Major Service alarm
Parameters
None.

When the B3_EXC_VC3 alarm occurs, the VC-3 service has plenty of bit errors.
Possible Causes
l Severer bit error alarms have occurred in the system.
Procedure
Step 1 Check the local and upstream NEs for the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm. If any of these alarms exists, clear it and check whether the B3_EXC_VC3 alarm
is cleared.
If... Then...

If... Then...
----End
Related Information
None.
4.12 B3_EXC_VC4
Description
The B3_EXC_VC4 is an alarm indicating that the number of the VC-4 B3 bit errors exceeds the
specified threshold. This alarm is reported when a board detects that the number of the VC-4 bit
errors exceeds the specified threshold by monitoring the B3 byte.
Attribute
Major Service alarm
Parameters
None.


Possible Causes
Procedure
is cleared.
If... Then...
If... Then...

----End
4.13 B3_SD
Description
The B3_SD is an alarm indicating higher order path (HP) B3 signal deterioration. This alarm is
reported when a board detects that the number of HP signal bit errors exceeds the B3_SD alarm
threshold (default threshold: 10-6) but remains below the B3_EXC alarm threshold (default
threshold: 10-3) by monitoring the B3 byte.
Attribute
Minor Service alarm
Parameters
None.

Possible Causes

Procedure
If... Then...
If... Then...
----End
Related Information
None.

4.14 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the number of the VC-3 B3 bit errors exceeds the
specified threshold. This alarm is reported when a board detects that the number of the VC-3 bit
errors exceeds the B3_SD alarm threshold by monitoring the B3 byte.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the service transmission quality of the VC-3 path has deteriorated.
Possible Causes
Procedure
is cleared.
If... Then...

If... Then...
If... Then...
----End
Related Information
None.
4.15 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that the number of the VC-4 B3 bit errors has exceeded
the specified threshold. This alarm is reported when a board detects that the number of the VC-4
bit errors exceeds the specified threshold by monitoring the B3 byte.

Attribute
Minor Service alarm
Parameters
None.

Possible Causes
Procedure
is cleared.
If... Then...

If... Then...
----End
4.16 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that a logical board is not installed. This
alarm is reported when a physical board is installed while its logical board is absent.
Attribute
Parameters
None.

When this alarm occurs, services cannot be configured for the slot that lacks the logical board.
However, lacking this board does not affect system running. If the logical board is not in use,
ignore this issue.

Possible Causes
The logical board is not configured.
Procedure
Step 1 Add the required logical board to the NMS. Alternatively, remove the physical board unless it
is in use.
----End
Related Information
None.
4.17 BDID_ERROR
Description
The BDID_ERROR is an alarm indicating an error in board position check. This alarm is reported
when a board parity check fails or the board is not properly installed.
Attribute
Parameters
None.

l When this alarm occurs, a board may fail to go online, which will interrupt services.
l When this alarm occurs, you cannot configure or monitor board services.
Possible Causes
l The board is not properly installed.
l The board has hardware faults.
l The backplane has bent pins.
Procedure
Step 1 View this alarm on the NMS and determine the board that reports the alarm.
Step 2 Remove the board to check the backplane for bent pins. If the backplane has bent pins, repair
them and insert the board. Then, check whether the BDID_ERROR alarm is cleared.

Step 3 If the alarm persists, replace the board.
----End
Related Information
None.
4.18 BEFFEC_EXC
Description
The BEFFEC_EXC is an alarm indicating that the number of forward error correction (FEC) bit
errors exceeds the specified threshold.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the system's error tolerance capability decreases. Insufficient error
tolerance capability affects the quality of service signals.
Possible Causes
l Severer alarms, such as R_LOS and FEC_LOF, have occurred in the system.
l The optical power is abnormal.
l The transmission optical fiber has encountered exceptions.
l The peer transmit board is faulty.
l The local receive board is faulty.
Procedure
Step 1 Check the system for severer alarms, such as R_LOS and FEC_LOF. If any of these alarms
exists, clear it and check whether the BEFFEC_EXC alarm is cleared.
Step 2 If the alarm persists, clean the fiber connector and check whether the BEFFEC_EXC alarm is
cleared.
Step 3 If the alarm persists, check the input optical power. If the input optical power is abnormal, use
the variable optical attenuator to adjust it into the normal range.

Step 4 Check whether the BEFFEC_EXC alarm is cleared. If the alarm persists, check the peer transmit
optical power. If the peer transmit optical power is low, replace the peer transmit board.
Step 5 Check whether the BEFFEC_EXC alarm is cleared. If the alarm persists, check whether the
optical fiber is damaged. If the optical fiber is damaged, replace it and check whether the
BEFFEC_EXC alarm is cleared.
Step 6 If the alarm persists, replace the local line board that reports the BEFFEC_EXC alarm.
----End
Related Information
None.
4.19 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating a failure to check the BOOTROM data. This alarm
is reported when the basic or extended BIOS software is damaged on a board.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the BIOS software type.

l 0x01: basic BIOS software
l 0x02: extended BIOS software
0xFF indicates no meaning.

l This alarm does not affect the system or services when the board is operating.
l When this alarm occurs, cold reset or restart will lead to a failure to load the BIOS software.
As a result, the board cannot be started.

Possible Causes
l The extended BIOS software is damaged.
l The basic BIOS software is damaged.
Procedure
Step 1 On the NMS, view the BOOTROM_BAD alarm and determine the type of the damaged BIOS
software based on alarm parameters.
If... Then...
The basic BIOS software is damaged Go to Step 2.
The extended BIOS software is Reload the extended BIOS software and check
damaged whether the BOOTROM_BAD alarm is cleared.
----End
Related Information
None.
4.20 C2_VCAIS
Description
The C2_VCAIS is an alarm pertaining to C2 bytes. This alarm is reported when a board detects
that all the received C2 bytes are 1.
Attribute
Minor Service alarm
Parameters
None.

Possible Causes
The remote end has transmitted C2 bytes that are incorrectly configured.

Procedure
Step 1 View the alarm information on the NMS and determine the VC path that has reported this alarm.
Step 2 Check whether the remote end has correctly configured the to-be-transmitted C2 bytes. If the
remote end has incorrectly configured the C2 bytes, reconfigure them and check whether the
C2_VCAIS alarm is cleared.
Step 3 If the alarm persists, replace the transmit board of the remote end.
----End
Related Information
None.
4.21 CHIP_ABN
Description
The CHIP_ABN is an alarm indicating an invalid temperature chip. This alarm is reported when
a temperature chip becomes invalid.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the invalid temperature chip. The value 0x01 indicates
that the temperature chip becomes invalid.

When this alarm occurs, the board temperature cannot be correctly detected.
Possible Causes
The temperature chip becomes invalid.

Procedure
Step 1 Check whether there is another cross-connect board that is working properly. If there is such a
board, cold reset the board that has reported the CHIP_ABN alarm. After the cold reset is
successful, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the alarm-reporting board.
----End
Related Information
None.
4.22 DB_RESTORE_FAIL
Description
The DB_RESTORE_FAIL is an alarm indicating a failure to restore a database. This alarm is
reported when the database fails to be restored.
Attribute
Major Processing alarm
Parameters
None.

When this alarm occurs, configuration data cannot be stored in the database, resulting in data
loss.
Possible Causes
l The database configuration file is lost.
l The data in the database is corrupted.
Procedure
Step 1 Verify that the data is complete in the backup database, and periodically back up databases for
restoration. Then, check whether the DB_RESTORE_FAIL alarm is cleared.
----End

Related Information
None.
4.23 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a failure to verify database files. This alarm is
reported when the database encounters an error.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the bit error that triggers the DBMS_ERROR alarm.
Parameter 2 Indicates the database storage area.

l 0x00: FDB0
l 0x01: FDB1
l 0x02: DRDB
Parameter 3 Indicates the database ID.

l 0x00: errors occur in the whole storage area.
l Values from 0x01 to 0xFF indicate specific databases that encounter errors.

When this alarm occurs, configuration data cannot be stored in the database, resulting in data
loss.
Possible Causes
l Database operations fail.
l The data in the database is corrupted.

Procedure
Step 1 Verify that the data is complete in the backup database, and periodically back up databases for
restoration. Then, check whether the DBMS_ERROR alarm is cleared.
----End
Related Information
None.
4.24 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the NE database enters the protection
mode. This alarm is reported when the NE database enters the protection mode.
Attribute
Critical Processing alarm
Parameters
None.

When this alarm occurs, you cannot back up the NE database.
Possible Causes
An NE is reset for N consecutive times within a specified period, where N exceeds the threshold
for triggering the NE database to enter the protection mode.
Procedure
Step 1 On the NMS, warm or cold reset the NE board. Then, check whether the
DBMS_PROTECT_MODE alarm is cleared.
----End
Related Information
None.

4.25 DLAG_PROTECT_FAIL
Description
The DLAG_PROTECT_FAIL is an alarm indicating a distributed link aggregation group
(DLAG) protection failure. This alarm is reported when the DLAG protection negotiation fails
or encounters an error.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the DLAG that encounters a protection failure.
Parameter 3 Indicates the cause of the DLAG protection failure.

l 0x01: Both the active and standby links become invalid.
l 0x02: Both the primary and secondary ports have not received
the LACP packets.
l 0x03: The peer NE has not entered the LACP synchronization
state.
l 0x04: The primary or secondary port detects a self-loop or a
loop formed with another port on the local board.
l 0x05: The communication between the active and standby
boards times out.
l 0x06: The communication between the local and cross-connect
boards times out.
l 0x07: The cross-connection status is inconsistent between the
active and standby boards.

When this alarm occurs, the DLAG cannot transmit or receive services or a user cannot learn
about the service status.

Possible Causes
l Both the active and standby links become invalid.
l Neither the primary nor secondary port has received the LACP packets.
l The peer NE has not entered the LACP synchronization state.
l The primary or secondary port detects a self-loop or a loop formed with another port on
the local board.
l The communication between the active and standby boards times out.
l The communication between the local board and the cross-connect or main control board
times out.
l The cross-connection status is inconsistent between the active and standby boards.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports this alarm. Then, determine
the ID of the DLAG that generates the alarm according to parameters 1 and 2, and identify cause
of the DLAG_PROTECT_FAIL alarm.
Step 2 If parameter 3 is 0x01, both the active and standby links become invalid.
1. Check whether the port in the DLAG is enabled on the NMS. If the port is not enabled,
enable it and check whether the DLAG_PROTECT_FAIL alarm is cleared.
2. Check the link status for all ports, rectify link faults, and check whether the
DLAG_PROTECT_FAIL alarm is cleared.
Step 3 If parameter 3 is 0x02, neither the primary nor secondary port has received the LACP packets.
1. On the NMS, verify that the DLAG is configured on the peer NE and the port connected
to the local port has joined the DLAG. If the DLAG is not configured or the port has not
joined the DLAG, correct the DLAG configuration. Then, check whether the
2. Verify that the local and peer NEs can properly transmit and receive packets. If either NE
cannot receive or transmit packets properly, locate and rectify the faults and check whether
the DLAG_PROTECT_FAIL alarm is cleared.
Step 4 If parameter 3 is 0x03, the peer NE has not entered the LACP synchronization state. In this case,
ensure that the local and peer NEs are properly interconnected and the DLAG is correctly
configured on the peer NE. Then, check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 5 If parameter 3 is 0x04, the primary or secondary port forms a self-loop or a loop formed with
another port on the local board. In this case, eliminate the loop and check whether the
Step 6 If parameter 3 is 0x05, the communication between the active and standby boards times out. In
this case, ensure that both boards are detected and their communication is proper. Then, check
whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 7 If parameter 3 is 0x06, the communication between the local board and the cross-connect or
main control board times out. In this case, ensure that the software on the cross-connect or main
control board runs properly and its communication with the local board is proper. Then, check
whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 8 If parameter 3 is 0x07, the cross-connection status is inconsistent between boards. In this case,
change their cross-connection status to keep its consistency.
----End

Related Information
None.
4.26 DSP_LOAD_FAIL
Description
The DSP_LOAD_FAIL is an alarm indicating a failure to load the DSP program. This alarm is
reported when the DSP program fails to be loaded.
Attribute
Parameters
None.

When this alarm occurs, a board fails to function properly, which will affect services.
Possible Causes
Procedure
Step 1 Warm reset the board on the NMS and check whether the DSP_LOAD_FAIL alarm is cleared.
----End
Related Information
None.
4.27 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating continuity check messages (CCMs) are lost. This
alarm is reported when the system has not received CCMs from the remote maintenance
association end point (MEP) within 3.5 times of the specified continuity check (CC) period.

Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate maintenance domain IDs.
Parameters 5 to 8 Indicate maintenance association IDs.
Parameters 9 to 10 Indicate MEP IDs.
Parameter 11, Parameter 12 Indicate VLAN IDs.
Parameter 13 Indicates the maintenance point direction.

l 0x01: ingress
l 0x02: egress
Parameter 14 Indicates the maintenance domain level.
Parameter 15, Parameter 16 Indicate remote MEP IDs.

Possible Causes
l The line that transmits the services between the local and remote standard maintenance
points (MPs) is interrupted.
l The network is heavily congested.
Procedure
Step 1 Check whether the physical line (network cable or optical fiber) that transmits services between
the local and remote standard MPs is correctly connected.

If... Then...
The line is incorrectly connected Re-connect the line.
The line is correctly connected Go to the next step.
Step 2 Check the bandwidth usage. If the bandwidth is exhausted, increase the bandwidth or eliminate
illegal transmission of large amount of data.
----End
Related Information
None.
4.28 ETH_CFM_MACSTATUS
Description
The ETH_CFM_MACSTATUS is an alarm indicating MAC-layer faults on the remote
maintenance association end point (MEP). This alarm is reported when the local NE receives a
continuity check message (CCM) containing MAC-layer fault indication from the remote ingress
maintenance association end point (MEP).
Attribute
Major Environment alarm
Parameters
Name Meaning
Parameter 9, Parameter 10 Indicate MEP IDs.

Name Meaning

l 0x01: ingress
l 0x02: egress

When this alarm occurs, the local NE detects MAC-layer faults on the remote port, which does
not affect the system.
Possible Causes
MAC-layer faults occur on the port where the remote MEP resides.
Procedure
Step 1 Check the remote port for MAC-layer faults.
l Check whether the port is in the discarding state by enabling the spanning tree protocol.
l View the indicator to determine whether the port is in the link down state.
Step 2 Check the board for service-affecting alarms. If these alarms exist, take precedence to clear them.
----End
Related Information
None.
4.29 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating a mismatch. This alarm is reported when
the system detects that a maintenance association (MA) ID mismatch or receives a lower-level
continuity check message (CCM).
Attribute
Critical Environment alarm

Parameters
Name Meaning
Parameter 9, Parameter 10 Indicate maintenance association end point (MEP) IDs.

l 0x01: ingress
l 0x02: egress.

l When this alarm occurs, the loopback (LB) and linktrace (LT) detection functions of
802.1ag ETH-OAM are unavailable.
l When this alarm occurs, services may be interrupted between standard maintenance points
or the data flow may be incorrectly routed.
Possible Causes
l The maintenance level is inconsistent between standard maintenance points.
l The maintenance domain or the maintenance association names are different for the
standard maintenance points.
l The physical connection is incorrect.
Procedure
Step 1 Check whether the maintenance level is consistent between the local and remote standard
maintenance points.
If... Then...
The maintenance level is inconsistent Reconfigure the maintenance level to keep its
consistency between the local and remote standard
maintenance points.
The maintenance level is consistent Go to the next step.

Step 2 Check whether the maintenance domain or the maintenance association names are the same for
the local and remote standard maintenance points
If... Then...
They are different Reconfigure the maintenance domain or maintenance association name
to keep its consistency between the local and remote standard
maintenance points.
They are the same Go to the next step.
Step 3 Verify the physical connection. Correct the physical connection if it is incorrect.
----End
Related Information
None.
4.30 ETH_CFM_RDI
Description
The ETH_CFM_RDI is an alarm indicating a receive failure of the peer maintenance association
end point (MEP). This alarm is reported when the system receives a continuity check message
(CCM) carrying the remote defect indication (RDI) from the remote NE.
Attribute
Minor Environment alarm
Parameters
Name Meaning
Parameter 9, Parameter 10 Indicate MEP IDs.

Name Meaning

l 0x01: ingress
l 0x02: egress

l When this alarm occurs, services may be interrupted between standard maintenance points.
Possible Causes
l Remote maintenance point equipment is reset.
l Remote maintenance point equipment is faulty. Specifically, the physical link is connected
properly, but the software malfunctions.
Procedure
Step 1 Locate the alarm-reporting port according to alarm parameters.
Step 2 Check whether the remote maintenance point equipment has been reset. If it has been reset,
identify the cause.
Step 3 Troubleshoot faults on the peer maintenance point connected to the alarm-reporting port by
paying attention to the following alarms:
l ETH_CFM_LOC
l ETH_CFM_UNEXPERI
l ETH_CFM_MACSTATUS
l ETH_CFM_MISMERGE
----End
Related Information
None.
4.31 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating errored frames. This alarm is reported when
the system receives an invalid continuity check massage (CCM).

Attribute
Parameters
Name Meaning
Parameter 9, Parameter 10 Indicate maintenance association end point (MEP) IDs.

l 0x01: ingress
l 0x02: egress
Parameter 14 Indicates the maintenance level.

l When this alarm occurs, a loop may occur and affect services.
Possible Causes
l Continuity check (CC) period is inconsistent between standard maintenance points at both
ends.
l Services have the same MEP ID in a maintenance domain, or there are illegal MEP IDs.
l A loop occurs in services and the looped packets are received.
Procedure
Step 1 Check whether the CC period is consistent between standard maintenance points at both ends.

If... Then...
The CC period is inconsistent Set the CC period to keep its consistency between standard
maintenance points at both ends.
The CC period is consistent Go to the next step.
Step 2 Check the maintenance domain for duplicate MEP IDs. If a duplicate MEP ID exists, delete the
ID and assign a unique ID to the MEP. Then, check whether the ETH_CFM_UNEXPERI alarm
is cleared.
Step 3 If the alarm persists, enable the loop detection function of the point-to-point OAM and check
services for loops. If any loop exists, eliminate it.
----End
Related Information
None.
4.32 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating a failure to detect point-to-point
Ethernet OAM. This alarm is reported when a port enables the OAM protocol but fails to perform
OAM authentication with the peer NE.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the cause of a negotiation failure.

l 0x01: The local link is faulty.
l 0x02: The local NE fails to transmit OAM packets.
l 0x03: The local NE has not received OAM packets from the peer NE.
l 0x04: The peer OAM configurations do not meet the local requirements.
l 0x05: The local OAM configurations do not meet the peer requirements.
l Values from 0x06 to 0xFF indicate other faults.

When this alarm occurs, the link-level 802.3ah OAM is performing OAM for the system, which
does not affect services.
Possible Causes
l The local link is faulty.
l The local NE fails to transmit OAM packets.
l The local NE has not received OAM packets from the peer NE within a given period of
time.
l The peer OAM configurations do not meet the local requirements.
l The local OAM configurations do not meet the peer requirements.
Procedure
Step 1 View this alarm on the NMS and identify the cause based on parameter 1.
Step 2 If parameter 1 is 0x01, the local link is faulty. In this case, check board alarms on the NMS.
Then, rectify faults based on specific link alarms, such as LINK_ERR.
Step 3 If parameter 1 is 0x02, the local NE fails to transmit OAM packets. In this case, query the serial-
port print information and check whether the system software is faulty. If it is faulty, contact
Huawei technical support engineers to handle the alarm.
Step 4 If parameter 1 is 0x03, the local NE has not received 802.3ah OAM packets from the peer NE
within a given period of time.
1. Ensure that the local and peer ports that are interconnected have different MAC addresses.
2. Ensure that the 802.3ah OAM is enabled on the peer NE.
3. If the ETHOAM_DISCOVER_FAIL alarm persists after the preceding operations, the local
NE cannot receive OAM packets. In this case, replace the board that reports the alarm.
Step 5 If parameter 1 is 0x04, the peer OAM configurations, such as OAM working mode, link event
notification capability, and uni-directional operating capability, do not meet the local
requirements. In this case, modify the peer OAM configurations based on the local requirements.
Step 6 If parameter 1 is 0x05, the local OAM configurations do not meet the peer requirements. In this
case, modify the local OAM configurations based on the peer requirements.
----End

Related Information
None.
4.33 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating that the point-to-point Ethernet OAM
detects a loopback on the peer end. This alarm applies only to ports that have enabled the point-
to-point OAM protocol.
l If the local port is capable of responding to loopback, it enters the loopback response state
and reports the loopback response alarm after receiving the command of enabling the
remote loopback control from the peer OAM-enabled port. In this case, the peer end reports
the loopback initiation alarm.
l After receiving the command of disabling the remote loopback control, the local port is
restored from the loopback response state and clears the loopback response alarm. In this
case, the peer end clears the loopback initiation alarm.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: loopback initiation

l 0x02: loopback response

When this alarm occurs, a loopback occurs between the loopback initiation and response ends,
which interrupts service and protocol-packet transmission. This alarm is generated when the
802.3ah OAM is performing OAM for the system.
Possible Causes
l The local port issues the command of enabling the remote loopback control and the peer
end responses.
l The peer port issues the command of enabling the remote loopback control and the local
end responses.

Procedure
Step 1 Stop the loopback.
----End
Related Information
None.
4.34 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating that the point-to-point Ethernet OAM detects
deteriorated peer Ethernet performance. This alarm is reported when the local OAM-enabled
port receives the link event notification packet that indicates deteriorated peer Ethernet
performance from the peer end.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the link event type.

l 0x01: errored frame event
l 0x02: errored frame period event
l 0x03: errored frame second event

When this alarm occurs, the local inbound port detects that the number of errored frames exceeds
the specified threshold, and the service performance deteriorates. This alarm is generated when
the link-level 802.3ah OAM, independent of services, is performing OAM for the system.
Possible Causes
The local OAM-enabled port receives the link event notification packet from the peer end.

Procedure
Step 1 Improve the link conditions for the peer end to stop transmitting link event notification packets.
Step 2 Adjust the performance monitoring threshold for the peer link.
Step 3 Disable the peer end to transmit link event notification packets.
----End
Related Information
None.
4.35 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating that the point-to-point Ethernet OAM
detects a local loop. This alarm is reported when the local MAC port receives the OAM packet
transmitted by itself or the local board during the loop check.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the loop type.

l 0x01: port self-loop
l 0x02: board self-loop
l Values from 0x03 to 0xFF indicate other causes.

When this alarm occurs, the MAC port is self-looped. If a user has enabled the automatic port
shutdown on the NMS, port services will be interrupted in case of a self-loop. If the user has not
enabled this function, a broadcast storm may occur in case of a self-loop.

Possible Causes
l The port optical fiber is self-looped.
l Inter-port links are configured into a loop on a board.
l A port PHY or MAC loopback is configured.
Procedure
Step 1 Check whether the inbound and outbound optical fibers connected to the MAC port are
interconnected. If both optical fibers are interconnected, correctly connect them and check
whether the ETHOAM_SELF_LOOP alarm is cleared.
Step 2 Check whether the inbound (outbound) optical fiber of the MAC port is interconnected with the
outbound (inbound) optical fiber of another port on the board. If inter-board optical fibers are
interconnected in such a manner, correctly connect the optical fibers and check whether the
ETHOAM_SELF_LOOP alarm is cleared.
Step 3 Check whether either PHY- or MAC-layer loopback is set for this port. If a PHY- or MAC-layer
loopback is set, clear it manually, or wait 5 minutes for the NMS to clear it automatically. Then,
----End
Related Information
None.
4.36 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating that the point-to-point Ethernet OAM
detects a local loop. This alarm is reported when a local VCTRUNK port receives the OAM
packet transmitted by itself or the local board during the loop check.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the loop type.

l 0x01: The port optical fiber is self-looped.
l 0x02: Inter-port links are configured into a loop on a board.
l Values from 0x03 to 0xFF indicate other causes.

When this alarm occurs, the links connected to the VCTRUNK port is self-looped. If a user has
enabled the automatic port shutdown on the NMS, port services will be interrupted in case of a
self-loop. If the user has not enabled this function, a broadcast storm may occur in case of a self-
loop.
Possible Causes
l The links connected to the VCTRUNK port are configured into a loop.
l Inter-port links are configured into a loop on a board.
l A port PHY or MAC loopback is manually configured.
Procedure
Step 1 View the alarm information on the NMS and identify the cause according to alarm parameters.
Step 2 Check whether the inbound and outbound links of the VCTRUNK port are interconnected. If
they are connected, correct the link configuration and check whether the
ETHOAM_SELF_LOOP alarm is cleared.
Step 3 If the alarm persists, check whether links between the VCTRUNK port and another VCTRUNK
port are configured into a loop on the board. If there is such a loop, correct the link configuration.
----End
Related Information
None.
4.37 EX_ETHOAM_CC_LOS
Description
The EX_ETHOAM_CC_LOS is an alarm indicating that a periodical continuity check message
(CCM) is lost. This alarm is reported when a sink maintenance point has not received a CCM
from the source maintenance point within 3.5 times of the specified continuity check (CC)
period. This period has started since the sink maintenance point enabled the timer to periodically
check the source-sink link after receiving the first CCM and.

Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the VLAN ID for the local maintenance point.
Parameter 3 Indicates the level of the local maintenance point.
Parameters 4 to 7 Indicate the ID of the remote maintenance point.
Parameters 8 to 11 Indicate the ID of the local maintenance point.

When this alarm occurs, a unidirectional continuity fault occurs on the source-sink link.
Possible Causes
l Software or hardware faults occur between the source and sink maintenance points.
l Services are blocked or interrupted between the source and sink maintenance points.
Procedure
None.
Procedure
Step 1 View this alarm on the NMS and determine the ID of the maintenance point that generates the
alarm.
Step 2 Query the information about the maintenance point.
Step 3 Perform the loopback (LB) or linktrace (LT) test on the source and sink maintenance points to
locate source-sink faults.
Step 4 Check the involved software, hardware, and traffic and restore the faulty services. Then, you
can perform a loopback test to check whether the EX_ETHOAM_CC_LOS alarm is cleared.
----End

Related Information
None.
4.38 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating duplicate maintenance point IDs.
This alarm is reported when a maintenance point receives a packet from another maintenance
point that has the duplicate ID within the same maintenance domain.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the VLAN ID for the local maintenance point.
Parameter 3 Indicates the level of the local maintenance point.
Parameters 4 to 7 Indicate the ID of the local maintenance point.

When this alarm occurs, the LB and LT tests will encounter exceptions and services will be
destined to incorrect maintenance points.
Possible Causes
At least two maintenance points in a maintenance domain have the same ID.
Procedure
Step 1 View this alarm on the NMS and determine the ID of the maintenance point that generates the
alarm.
Step 2 Query maintenance point information and delete the maintenance points that have duplicate IDs.
----End

Related Information
None.
4.39 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm indicating a lost external time source. This alarm is reported
when a board detects no incoming external time signal after it enables the input function of the
external time port.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for a time source.
Parameter 2 The value is fixed at 0xF0.
Parameter 3 The value is fixed at 0x00.
Parameter 4 Indicates the port ID for a time source.

When this alarm occurs, the time of the local NE cannot be synchronized with the external time
device that is connected to the enabled external time port.
Possible Causes
l Signals are lost at the physical external-time source interface.
l The cable that transmits incoming time signals is incorrectly connected.
l The clock board is faulty.

Procedure
Step 1 Check whether the incoming signals are proper. If they are improper, substitute a functional
external time device for the original device. Then, check whether the EXT_TIME_LOC alarm
is cleared.
Step 2 If the alarm persists, check whether the time input cable is correctly connected. If the time input
cable is incorrectly connected, connect it correctly and check whether the EXT_TIME_LOC
alarm is cleared.
Step 3 If the alarm persists, check whether the time input cable is faulty by replacing it. If the time input
cable is faulty, replace it and check whether the EXT_TIME_LOC alarm is cleared.
Step 4 If the alarm persists, cold reset the clock board and check whether the alarm is cleared.
Step 5 If the alarm persists, replace the clock board.
----End
Related Information
None.
4.40 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
Attribute
Parameters
None.

When this alarm occurs, inefficient troubleshooting will result in high board temperature, which
may damage boards and NEs and interrupt NE services.
Possible Causes
l The fan stops functioning.
l The fan functions at a low speed.
l The fan fails.

Procedure
Step 1 Check whether the fan is set to the stop or low speed mode. If the fan is set to either mode, reset
it to the high speed mode. Then, check whether the FAN_FAIL alarm is cleared.
Step 2 If the alarm persists, replace the fan.
----End
Related Information
None.
4.41 FAN_FAULT
Description
The FAN_FAULT is an alarm indicating a fan failure.
Attribute
Parameters
None.

When this alarm occurs, the board may function in high temperature and be damaged.
Possible Causes
The fan fails.
Procedure
Step 1 Replace the fan.
----End
Related Information
None.

4.42 FEATURE_WITHOUT_LICENSE
Description
The FEATURE_WITHOUT_LICENSE is an alarm indicating the unauthorized use of a license-
controlled service. This alarm is reported when a user uses a license-controlled service without
permission.
Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate the ID of a feature item.

The license-controlled services in use are still available, and users can query, delete, and disable
them but cannot create, enable, or edit them.
Possible Causes
l Cause 1: The user has not bought the license.
l Cause 2: The equipment serial number (ESN) or V/R version is inconsistent between the
currently used and actual license files and the license grace period expires.
l Cause 3: Both the trial and grace periods of a feature expire.
Procedure
Step 1 Cause 1: The user has not bought the license. Cause 2: The equipment serial number (ESN) or
V/R version is inconsistent between the currently used and actual license files and the license
grace period expires. Cause 3: Both the trial and grace periods of a feature expire.
1. Delete the service that is used in an unauthorized manner or contact Huawei technical
support engineers to install a correct license file on the NE.
----End

Related Information
State Definition
Normal state
In the normal state, the license file pass all the check items, and the equipment can properly
implement all the license-controlled features.
Trial state
In the trial state, the license file fails to be checked for correctness. However, the equipment in
the grace period can still implement all the license-controlled features.
License grace period
The license grace period refers to the number of days when the license is still valid after its life
cycle expires. By default, the license grace period lasts for 60 days.
Default state
In the default state, the license file fails the integrity check. The created services can still run
but cannot be configured. For example, a service cannot be added or modified.
State Transition
The following figure shows the transition of the basic states of a license file on an NE.
Normal
state
Default Trial
state state
LCS_EXPIRED LCS_DAYS_OF_GRACE
FEATURE_WITHOUT_LICENSE
Table 4-1 lists the events triggering the state transition of a license file.
Table 4-1 State transition of a license file

Starting Status Ending Status Triggering Event
Normal state Trial state l The ESN or V/R version of the license file does
not match the ESN or software version of the
equipment, but the license file remains in the
grace period.
l The installed license remains in the grace period
but the life cycle expires.
Default state Both the life cycle and grace period of the installed
license expire.

Trial state Normal state The license file is installed within its life cycle.
license expire.
Default state Trial state l The ESN or V/R version of the license file does
grace period.
Normal state The license file is installed within its life cycle.
4.43 FEC_LOF
Description
The FEC_LOF is an alarm indicating that forward error correction (FEC) frames are lost.
Attribute
Parameters
None.

When this alarm occurs, the FEC function fails, and services are interrupted.
Possible Causes
l The optical fiber is faulty or the optical power is abnormal.
l The local and upstream NEs do not match in service rate.
l The NE clock is not synchronized.
l Services transmitted from the peer NE are abnormal.
Procedure

Step 2 Check the receive optical power of the board on the NMS. If the receive optical power is below
the specified lower threshold, clean the fiber end and the connector. If the receive optical power
is above the specified upper threshold, add an optical attenuator to decrease the optical power.
Then, check whether the FEC_LOF alarm is cleared.
Step 3 If the alarm persists, check whether the FEC service rate is consistent between the local and
upstream NEs. If it is inconsistent, reconfigure the FEC service with the rate consistent between
both NEs. Then, check whether the FEC_LOF alarm is cleared.
Step 4 If the alarm persists, check whether the board supports the upstream services. If the board does
not support the upstream services, reconfigure upstream services and check whether the
FEC_LOF alarm is cleared.
Step 5 If the alarm persists, check whether the local and peer clocks are synchronized with the clocks
on the network. If the local or peer clock is not synchronized with the them, correctly set clock
tracing for the local or peer clock and check whether the FEC_LOF alarm is cleared.
Step 6 If the alarm persists, the local board may be faulty. In this case, replace the board that reports
the alarm.
Step 7 If the alarm persists, the peer board may be faulty. In this case, replace it.
----End
Related Information
None.
4.44 FEC_OOF
Description
The FEC_OOF is an alarm indicating forward error correction (FEC) out of frame (OOF) errors.
Attribute
Parameters
None.

Possible Causes
l The optical fiber is faulty or the optical power is abnormal.
l The number of bit errors during transmission exceeds the specified threshold.

l The NE clock is not synchronized.

Procedure
Step 2 Check the receive optical power of the board on the NMS. If the receive optical power is below
the specified lower threshold, clean the fiber end and the connector. If the receive optical power
is above the specified upper threshold, add an optical attenuator to decrease the optical power.
Then, check whether the FEC_OOF alarm is cleared.
Step 3 If the alarm persists, check the transmit optical power of the peer board. If the optical power is
below the specified lower threshold, replace the peer board.
Step 4 If the alarm still persists, check whether local and peer clocks are synchronized with the clocks
on the network. If the local or peer clock is not synchronized with them, correctly set clock
tracing for the local or peer clock. Then, check whether the FEC_OOF alarm is cleared.
Step 5 If the alarm persists, check the transmission optical fiber. If the fiber is proper, replace the board
that reports the FEC_OOF alarm.
Step 6 If the alarm persists, replace the local clock board and check whether the FEC_OOF alarm is
cleared.
Step 7 If the alarm persists, replace the peer line board and check whether the FEC_OOF alarm is
cleared.
Step 8 If the alarm persists, replace the peer clock board.
----End
Related Information
None.
4.45 FPGA_ABN
Description
The FPGA_ABN is an alarm indicating a failure to read and write the field programmable gate
array (FPGA).
Attribute
Parameters
None.


When this alarm occurs, the board functions are disabled. Resetting the board may interrupt
services.
Possible Causes
FPGA of the board is lost or damaged.
Procedure
Step 1 Reload the FPGA software on the board and check whether the FPGA_ABN alarm is cleared.
----End
Related Information
None.
4.46 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is selected forcibly.
Attribute
Major Security alarm
Parameters
Name Meaning
Parameter 1 Indicates the slot of the forcibly selected clock board.

l 0x01: slot with the smaller ID
l 0x02: slot with the larger ID

If the forcibly selected clock board runs properly, services will be interrupted transiently during
the switchover. If the board is faulty, services will be interrupted.

Possible Causes
A command is issued to forcibly select the clock board.
Procedure
Step 1 Cancel the command for forcibly selecting the clock board.
----End
Related Information
None.
4.47 FWD_PKT_LO
Description
The FWD_PKT_LO is an alarm indicating packet loss. This alarm is reported when packet loss
occurs during service forwarding.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, services lose packets or are interrupted.
Possible Causes
l Service configurations do not match the type of received packets.
l The transmission channel is congested, losing packets, such as CoS queue packets.
Procedure
Step 1 Check whether service configurations match the type of received packets. If the configurations
do not match the packet type, modify the configurations as required. Then, check whether the
FWD_PKT_LO alarm is cleared.
Step 2 If the alarm persists, check whether QoS functions, such as CAR, CoS, and shaping, are
configured on the port. If these QoS functions are configured, adjust parameters, such as service
bandwidth and priority, as required. Then, check whether the FWD_PKT_LO alarm is cleared.
----End

Related Information
None.
4.48 GAINDATA_MIS
Description
The GAINDATA_MIS is an alarm indicating a gain mismatch. This alarm is reported when the
configured nominal gain exceeds the adjustable nominal gain range of the board.
Attribute
Parameters
None.

When this alarm occurs, service quality may be affected.
Possible Causes
The optical amplifier board or optical module is replaced.
Procedure
Step 1 Reset the nominal gain for the optical channel by referring to the upper and lower thresholds of
the nominal gain for the board.
----End
Related Information
None.
4.49 HARD_ERR
Description
The HARD_ERR is an alarm indicating hardware errors. This alarm is reported when hardware
has minor faults.

Attribute
Parameters

Name Meaning
Parameter 1 Indicates a key-chip failure for a clock board.

Indicates the following faults for other boards:
l 0x01: The power module is working improperly.
l 0x02: The board is improperly installed or has poor contact with the
backplane. For example, the board is loose installed.
l 0x05: 2M clock source encounters an exception.
l 0x06: The digital phase-locked loop encounters an exception.
l 0x07: The 38M service clock is lost.
l 0x08: The bus encounters an exception.
l 0x09: The TPS protection board encounters an exception.
l 0x0A: The primary crystal oscillator stops oscillating.
l 0x0B: The frequency offset of the primary crystal oscillator is large.
l 0x0C: The secondary crystal oscillator stops oscillating.
l 0x0D: The processor (CPU/DSP/coprocessor) is faulty.
l 0x0E: Storage components are faulty.
l 0x0F: The programmable logical device is faulty.
l 0x10: SDH components are faulty.
l 0x11: Data communication components are faulty.
l 0x12: Clock components are faulty.
l 0x13: Interface components are faulty.
l 0x14: Power components are faulty.
l 0x15: Other faults occur.
l 0x16: The analog phase-locked loop encounters an exception.
l 0x1A: The cross-connect chip loop is faulty.
l 0x1B: The 8k in-service line of the board is of low level.

Name Meaning
Parameter 2 Indicates the following faults for a clock board:

l 0x01: The local CPU crystal oscillator is lost.
l 0x02: The local daughter board loses its 2M crystal oscillator.
l 0x02: The local daughter board loses its 38M clock source.
l 0x04: The peer board loses its 38M clock source.
l 0x05: The peer board loses the 2K clock packet frame header.
packet.
packet.
When parameter 1 is 0x08 for other boards, bus A encounters an exception if
parameter 2 is 0x01, and bus B encounters an exception if parameter 2 is 0x02.
When parameter 1 is not 0x08 for other boards, parameter 2 is 0xFF.
Parameter 3 Indicates hardware failures on the time module for a clock board.

When this alarm occurs, services are not affected.
Possible Causes
Procedure
Step 1 On the NMS, warm or cold reset the board that reports the alarm. Then, check whether the
HARD_ERR alarm is cleared.
----End
Related Information
None.
4.50 HP_LOM
Description
The HP_LOM is an alarm indicating that a higher order path (HP) multiframe is lost.

Attribute
Parameters
None.

When this alarm occurs, the path-level services are interrupted.
Possible Causes
l Cause 1: The level is inconsistent between source and sink services.
l Cause 2: The clock board is faulty. As a result, the H4 byte is lost or incorrect.
Procedure
Step 1 View this alarm on the NMS and determine the IDs of the port and path that report the alarm.
Step 2 Check whether the level is consistent between the peer to-be-transmitted service and the local
to-be-received service. If the service level is inconsistent, change the service level at either end
to keep its consistency. Then, check whether the HP_LOM alarm is cleared.
----End
Related Information
None.
4.51 HP_RDI
Description
The HP_RDI is an alarm indicating the remote receive failure in the higher order path (HP).
Attribute
Minor Communication alarm
Parameters
None.


When this alarm occurs, the local end is not affected. This alarm indicates only that the remote
path-level service is interrupted.
Possible Causes
This is an accompanying alarm. When reporting the AU_AIS, AU_LOP, HP_TIM, or HP_SLM
alarm, the relevant path of the peer line board sends the HP_RDI alarm to the local end.
Procedure
Step 1 Clear the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm reported by the relevant path of the
peer line board.
----End
Related Information
None.
4.52 HP_REI
Description
The HP_REI is an alarm indicating remote bit errors in the higher order path (HP).
Attribute
Warning Service alarm
Parameters
None.

When this alarm occurs, the local NE is not affected. This alarm indicates only that the higher
order services generate error bits when traversing NEs and deteriorates.
Possible Causes
This is an accompanying alarm. When a service-traversed NE reports the B3_EXC or B3_SD
alarm after detecting B3 bit errors, it sends the HP_REI alarm to the local NE.

Procedure
Step 1 Clear the B3_EXC or B3_SD alarm reported by a service-traversed NE.
----End
Related Information
None.
4.53 HP_SLM
Description
The HP_SLM is an alarm indicating signal label mismatch in the higher order path (HP). This
alarm is reported when the line board detects the inconsistency between the received and to-be-
received C2 bytes.
Attribute
Parameters
None.

If the AU-AIS alarm is inserted when the HP_SLM alarm occurs, the path services are
interrupted. In addition, the HP_RDI alarm is transmitted to the peer NE.
Possible Causes
l Cause 1: On the local NE, the received C2 byte (signal label overhead in the HP), which
is not 0x00, is inconsistent with the to-be-received C2 byte.
l Cause 2: The service type is incorrectly configured.
l Cause 3: The board on the terminating NE works improperly.
Procedure
Step 1 Determine the board that initially transmits lower order services by checking the upstream NEs
that have transmitted the services. The board that initially transmits the services is the source of
the C2 byte, while the other NEs transmit the C2 byte transparently. Then, determine the remote
NE that terminates the higher order overhead and transmits the C2 byte to the local NE, and
specify the remote NE as the terminating NE.

Step 2 Check whether the configured service type and to-be-transmitted C2 byte match on the
terminating NE. If they do not match, reconfigure the C2 byte. Then, check whether the HP_SLM
alarm is cleared.
Step 3 If the alarm persists, check whether the configured service type and to-be-received C2 byte match
on the local NE. If they do not match, reconfigure the C2 byte. Then, check whether the HP_SLM
alarm is cleared.
Step 4 If the alarm persists, check whether the configured service type is consistent between the
terminating and local NEs. If the configured service type is inconsistent, modify the service on
the required NE to keep the service consistency. Then, check whether the HP_SLM alarm is
cleared.
Step 5 If the alarm persists, cold reset the receive board of the terminating NE on the NMS or directly
remove and reinsert the board. Then, check whether the HP_SLM alarm is cleared.
Step 6 If the alarm persists, replace the receive board on the terminating NE.
----End
Related Information
C2 byte (signal label byte)
The C2 byte indicates the structures of the higher order virtual containers (VC-3, VC-4, and
VC-4-Xc) and the payload property.
Transparent transmission and termination
Transparent transmission indicates that a service board receives a higher order overhead byte
from an upstream NE and directly transmits it to a downstream NE without processing them.
The higher order overhead byte remains unchanged when it is transmitted from the cross-connect
board to the service board and then to the downstream NE. In most cases, higher order services,
such as the VC-4 service, transparently transmit higher order overhead bytes.
Termination indicates that the higher order overhead byte from the cross-connect board to the
service board is modified and transmitted through the optical port. The source of lower order
services, such as the VC-3 and VC-12 services, terminates higher order overhead bytes.
Figure 4-1 shows overhead transparent-transmission and termination.
Figure 4-1 Overhead transparent-transmission and termination

West Line unit East Line unit East
West
HP overhead HP overhead HP overhead HP overhead
Overhead Overhead
detection detection
Overhead transparent
A B Overhead termination
transmission
Indicates
termination
Indicates
regeneration

4.54 HP_TIM
Description
The HP_TIM is an alarm indicating the trace identifier mismatch (TIM) in the higher order path
(HP).
Attribute
Parameters
None.

If the AU-AIS alarm is inserted when the HP_TIM alarm occurs, the path services are interrupted.
In addition, the HP_RDI alarm is transmitted to the peer NE.
Possible Causes
l The service cross-connection is incorrectly configured.
l The J1 byte is incorrectly configured.
Procedure
Step 1 Check whether the service cross-connection is correctly configured. If the service cross-
connection is incorrectly configured, correct it. Then, check whether the HP_TIM alarm is
cleared.
Step 2 If the alarm persists, determine the board that initially transmits lower order services by checking
the upstream NEs that have transmitted the services. The board that initially transmits the
services is the source of the J1 byte, while the other NEs transmit the J1 byte transparently. Then,
determine the remote NE that terminates the higher order overhead and transmits the J1 byte to
the local NE, and specify the remote NE as the terminating NE.
Step 3 Check whether the J1 byte to be transmitted by the line board on the terminating NE consists
with the J1 byte to be received by the line board on the local NE. If both J1 bytes are different,
reconfigure the J1 byte on the required NE to keep its consistency.
----End
Related Information
J1 byte (path trace byte)
The J1 byte is used to repetitively transmit an HP access point identifier (APID), which helps
the receive end check whether the channel is correctly connected to the specified transmit end.


Transparent transmission indicates that a service board receives higher order overhead bytes
from an upstream NE and directly transmits them to a downstream NE without processing them.
The higher order overhead byte remains unchanged when it is transmitted from the cross-connect

West
Overhead Overhead
detection detection
transmission
Indicates
termination
Indicates
regeneration
4.55 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path (HP) carries no overhead. The
received C2 byte is 0x00.
Attribute
Parameters
None.

If the AU-AIS alarm is inserted when the HP_UNEQ alarm occurs, the path services are
interrupted. In addition, the HP_RDI alarm is transmitted to the peer NE.

Possible Causes
l Services are not configured at the upstream NEs.
l The received C2 byte is 0x00.
Procedure
Step 1 Check whether services are configured on the required path on the peer NE.
If... Then...
Services are not configured Correctly configure services and check whether the HP_UNEQ
alarm is cleared. If the alarm persists, go to Step 2.
Services are configured Go to Step 2.
Step 2 Check the service path passing through the upstream NE for the HP_UNEQ alarm.
If... Then...
The alarm exists The upstream NE transparently transmits services with no

overhead to the local NE. In this case, clear the HP_UNEQ alarm
on the path passing through the upstream NE. Then, check whether
the HP_UNEQ alarm is cleared on the local NE. If the alarm
The alarm does not exist Go to Step 3.
Step 3 Determine the board that initially transmits lower order services by checking the upstream NEs
that have transmitted the services. The board that initially transmits the services is the source of
the C2 byte, while the other NEs transmit the C2 byte transparently. Then, determine the remote
NE that terminates the higher order overhead and transmits the C2 byte to the local NE, and
specify the remote NE as the terminating NE.
Step 4 Check whether the C2 byte to be transmitted by the terminating NE is 0x00. If the C2 byte is
0x00, modify it based on the actual service type. Then, check whether the HP_UNEQ alarm is
cleared.
----End
Related Information
C2 byte (signal label byte)
The C2 byte indicates the structures of the higher order virtual containers (VC-3, VC-4, and
VC-4-Xc) and the payload property.
Transparent transmission indicates that a service board receives higher order overhead bytes
from an upstream NE and directly transmits them to a downstream NE without processing. The
higher order overhead byte remains unchanged when it is transmitted from the cross-connect


West
Overhead Overhead
detection detection
transmission
Indicates
termination
Indicates
regeneration
4.56 HSC_UNAVAIL
Description
The HSC_UNAVAIL is an alarm indicating a failure to perform the active/standby switchover.
This alarm is reported when a switchover fails between the active and standby boards.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x00: active or standby state of the board that reports the alarm
l 0x01: slot ID for the board that reports the alarm

When this alarm occurs, both the active/standby switchover and backup fail.

Possible Causes
l A board has been reset or an active/standby has occurred less than 5 minutes earlier.
l The active and standby boards do not match in version.
l The standby board has hardware faults.
l The communication between the active and standby boards encounters an exception.
Procedure
Step 1 If a board has been reset or an active/standby has occurred less than 5 minutes earlier, the
HSC_UNAVAIL alarm is automatically cleared after the reset or switchover is successful.
Step 2 Check whether the active and standby boards match in version. If they do not match, contact
Huawei technical support engineers to update software as required. Then, check whether the
HSC_UNAVAIL alarm is cleared.
Step 3 If the alarm persists, replace the standby board and check whether the HSC_UNAVAIL alarm
is cleared.
----End
Related Information
None.
4.57 IN_PWR_FAIL
Description
The IN_PWR_FAIL is an alarm indicating no receive optical power. This alarm is reported when
an optical amplifier board detects no receive optical power on its inbound optical port.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates a channel ID. The value is fixed at 0x01.


If the optical signal carrying services is amplified when traversing the optical port, and the
multiplex section protection (MSP) or subnetwork connection protection (SNCP) is configured
on the service channel, the MSP or SNCP is triggered.
If the optical signal carrying services is amplified when traversing the optical port, and no MSP
or SNCP is configured on the service channel, the services are interrupted.
Possible Causes
l Fiber cut occurs.
l The optical module is faulty.
Procedure
Step 1 Use the optical time domain reflectometer (OTDR) to check whether the fiber is disconnected.
If the fiber is disconnected, replace it and check whether the IN_PWR_FAIL alarm is cleared.
Step 2 If the alarm persists, check whether the local fiber connector or the fiber flange on the optical
distribution frame (ODF) is contaminated. If the fiber connector or flange is contaminated, clean
the pigtail connector and check whether the IN_PWR_FAIL alarm is cleared.
Step 3 If the alarm persists, verify that the local fiber flange is correctly connected. Then, check whether
the IN_PWR_FAIL alarm is cleared.
Step 4 If the alarm persists, check whether the peer transmit optical power is proper.
If... Then...
The transmit optical power is proper The local receive optical module may be faulty. In
this case, replace the local board if the optical
module is unpluggable, or replace the optical
module if it is pluggable.
The transmit optical power is improper Go to the next step.
Step 5 Clean the peer pigtail connector and check whether the IN_PWR_FAIL alarm is cleared.
Step 6 If the alarm persists, verify that the peer fiber flange is correctly connected. Then, check whether
the IN_PWR_FAIL alarm is cleared.
Step 7 If the alarm persists, the peer transmit optical module may be faulty. In this case, replace the
peer board if the optical module is unpluggable, or replace the optical module if it is pluggable.
----End
Related Information
None.

4.58 J0_MM
Description
The J0_MM is an alarm indicating a regenerator section trace byte mismatch. This alarm is
reported when the received J0 byte is inconsistent with the to-be-received J0 byte.
Attribute
Parameters
None.

This alarm does not affect services.
Possible Causes
The J0 byte to be transmitted by the peer board is inconsistent with that to be received by the
local board.
Procedure
Step 1 Check whether the J0 byte to be transmitted by the peer board is inconsistent with that to be
received by the local board. If the J0 byte is inconsistent between both boards, set a consistent
J0 byte between them and check whether the J0_MM alarm is cleared.
----End
Related Information
J0 byte (regenerator section trace byte)
This byte is used to repetitively transmit an access point identifier, which helps the receive end
verify its continued connection to the transmit end.
4.59 K1_K2_M
Description
The K1_K2_M is an alarm indicating a mismatch between the K1 and K2 bytes. This alarm is
reported when the K1 and K2 bytes indicates different channel numbers for a given period
(default: 160 ms).

Attribute
Parameters
None.

When this alarm occurs, the multiplex section protection (MSP) is unavailable. If the fiber cut
or another fault occurs, services may be interrupted.
Possible Causes
l The optical fiber is connected incorrectly.
l The MSP group type is inconsistent between both ends.
l The cross-connect board is faulty.
Procedure
Step 1 Verify that the optical fiber of the multiplex section (MS) is properly connected and the logic
configuration of the fiber matches its physical configuration. Then, check whether the K1_K2_M
alarm is cleared.
Step 2 If the alarm persists, check whether the MSP group type is consistent between both ends. If the
MSP group type is inconsistent, reconfigure the MSP group to keep its consistency between both
ends. Then, check whether the K1_K2_M alarm is cleared.
Step 3 If the alarm persists, check whether the local and peer MS-configured boards are faulty. If either
board is faulty, replace it and check whether the K1_K2_M alarm is cleared.
Step 4 If the alarm persists, check whether the local and peer cross-connect boards are faulty. If either
board is faulty, replace it.
----End
Related Information
None.
4.60 K2_M
Description
The K2_M is an alarm indicating a K2 byte mismatch. This alarm is reported when the fifth bit
of the received K2 byte indicates a specified period (default: 2s) of inconsistency between the
peer and local multiplex section protection (MSP) modes.

Attribute
Parameters
None.

When this alarm occurs, the MSP is unavailable. If the fiber cut or another fault occurs, services
may be interrupted.
Possible Causes
l The multiplex section (MS) configuration is incorrect.
Procedure
Step 1 Check whether the MS configuration is consistent between the local and peer NEs. If the MS
configuration is inconsistent, reconfigure the MS to keep its consistency between both NEs.
Then, check whether the K2_M alarm is cleared.
Step 2 If the alarm persists, check whether the local and peer MS-configured boards are faulty. If either
board is faulty, replace it and check whether the K2_M alarm is cleared.
Step 3 If the alarm persists, check whether the local and peer cross-connect boards are faulty. If either
board is faulty, replace it and check whether the K2_M alarm is cleared.
----End
Related Information
None.
4.61 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that a port in the link aggregation group (LAG)
fails.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the cause of the protection failure.

l 0x01: The link connected to the port is faulty or fails.
l 0x02: The port is in half-duplex mode.
l 0x03: The port receives no LACP packet.
l 0x04: The port detects a self-loop.
l 0x05: The failure occurs due to unknown causes.

The port in the LAG can neither share the service load nor transmit or receive services.
Possible Causes
l The port is not enabled.
l The link connected to the port is faulty.
l The port is in half-duplex mode.
l The port receives no LACP packet.
l The port detects a self-loop.
Procedure
Step 1 View the alarm on the NMS, determine the board that reports the alarm, and identify the cause
according to parameter 1.
Step 2 If parameter 1 is 0x01, the link connected to the port is faulty or fails.
1. On the NMS, check whether the port in the LAG is enabled. If the port is not enabled,
enable it and check whether the LAG_PORT_FAIL alarm is cleared.
2. Check the status of all links connected to the port. If any link is faulty, rectify the fault and
check whether the LAG_PORT_FAIL alarm is cleared.
Step 3 If parameter 1 is 0x02, change the port working mode to keep its consistency between
interconnected ends. Then, check whether the LAG_PORT_FAIL alarm is cleared.

Step 4 If parameter 1 is 0x03, the port receives no LACP packet.

1. On the NMS, check whether the LAG is configured on the peer end, and whether the peer
port connected to the local failing port has joined the LAG. Ensure that the peer LAG is
correctly configured. Then, check whether the LAG_PORT_FAIL alarm is cleared.
2. Check whether the local port transmits packets. Ensure that both ends can properly transmit
and receive packets. Then, check whether the LAG_PORT_FAIL alarm is cleared.
Step 5 If parameter 1 is 0x04, eliminate the self-loop on the port. Then, check whether the
LAG_PORT_FAIL alarm is cleared.
Step 6 If parameter 1 is 0x05, identify the cause based on the networking environment. Then, rectify
the fault and check whether the LAG_PORT_FAIL alarm is cleared.
----End
Related Information
None.
4.62 LAN_LOC
Description
The LAN_LOC is an alarm indicating that the Ethernet communication fails.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates an Ethernet port number. For example, the value 0x01
indicates Ethernet port 1.
Parameter 2, Parameter 3 Indicate the number of the channel that generates the LAN_LOC
alarm. Values of parameters 2 and 3 are fixed at 0x00 and 0x01.

When this alarm occurs, the communication is interrupted on the Ethernet port. This disconnects
some NEs from the NMS but does not affect services that currently traverse NEs.

Possible Causes
l The network cable is not connected to Ethernet port.
l The network cable is faulty.
l The Ethernet port is faulty.
Procedure
Step 1 View the alarm on the NMS and determine the Ethernet port that reports the alarm. Then, check
whether the Ethernet port has a network cable and whether the cable is properly connected. If
the Ethernet port has no network cable, connect a functional network cable to the Ethernet port.
If the network cable is loose connected, connect it properly. Then, check whether the LAN_LOC
alarm is cleared.
Step 2 If the alarm persists, the network cable may be faulty. Replace the network cable and check
whether the LAN_LOC alarm is cleared.
Step 3 If the alarm persists, check whether the Ethernet port is damaged. If it is damaged, replace the
SEI board and check whether the LAN_LOC alarm is cleared.
Step 4 If the alarm persists, check whether the SEI and AUX boards work properly. If either board
works improperly, replace it.
----End
Related Information
None.
4.63 LASER_HAZARD_WARNING
Description
The LASER_HAZARD_WARNING is an alarm indicating hazards posed by the laser. This
alarm is reported when the optical communication system employs a high-power laser that may
pose hazards to users or risks to the security system.
Attribute
Parameters
None.

When this alarm occurs, the laser does not affect services but may bring personal injuries.

Possible Causes
l The intelligent power adjustment (IPA) function is not configured on the high-power laser.
l The IPA function is configured but disabled on the high-power laser.
Procedure
Step 1 Check the IPA configuration on the NE.
l If the IPA function is not configured, configure it according to network design principles.
l If the IPA function is configured, enable it on the NE.
Step 2 After the IPA function is enabled, the LASER_HAZARD_WARNING alarm is cleared
automatically.
----End
Related Information
None.
4.64 LASER_MODULE_MISMATCH
Description
The LASER_MODULE_MISMATCH is an alarm indicating an optical module mismatch.
Attribute
Parameters
None.

When this alarm occurs, services are improperly transmitted and received or even interrupted.
Possible Causes
l The logical rate configured for the optical module does not match the rate of that on the
physical board.
l The type of the logical optical port does not match that of the actually inserted optical
module.

Procedure
Step 1 View and record the rate configured for the optical module on the NMS. Then, record the actual
rate of the optical module by checking the bar code on the board.
Step 2 If the logical and actual rates do not match, modify the logical rate to the actual rate as required.
Then, check whether the LASER_MODULE_MISMATCH alarm is cleared.
Step 3 If the alarm persists, check whether the correct optical module is installed.
Step 4 If yes, reconfigure the type of the logical optical port. If no, install the correct optical module.
----End
Related Information
None.
4.65 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of a board is shut down.
Attribute
Parameters
None.

Possible Causes
A user shuts down the laser on the NMS or by running commands.
Procedure
Step 1 Start up the laser and the LASER_SHUT alarm is cleared automatically.
----End
Related Information
None.

4.66 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the link capacity adjustment scheme (LCAS) protocol
fails in the receive direction. This alarm is reported when the system detects an exception on the
LCAS sink, which may result in an LCAS negotiation failure or error.
Attribute
Parameters
None.

When this alarm occurs, the protocol state machine in the receive direction is confused, which
may result in improper negotiation.
Possible Causes
l The downstream VCTRUNK port receives duplicate sequence numbers due to incorrect
configuration or link bit errors.
l The LCAS function is not enabled on the peer VCTRUNK port.
l The downstream VCTRUNK port concurrently receives the FIXED and other LCAS
control words due to incorrect configuration or link bit errors.
l The cross-connection is incorrectly bound.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port.
Step 2 Check whether the LCAS protocol is enabled at the peer end. If the protocol is not enabled at
the peer end, enable it and check whether the LCAS_FOPR alarm is cleared.
Step 3 If the alarm persists, check whether configurations, especially timeslot cross-connection binding,
are correct. If there are incorrect configurations, correct them and check whether the
LCAS_FOPR alarm is cleared.
Step 4 If the alarm persists, disable the LCAS protocol at both ends and concurrently enable it. Then,
check whether the LCAS_FOPR alarm is cleared.
----End

Related Information
None.
4.67 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the LCAS protocol fails in the transmit direction. This
alarm is reported when the system detects an exception on the LCAS source, which may result
in an LCAS negotiation failure or error.
Attribute
Parameters
None.

When this alarm occurs, the protocol state machine in the transmit direction is confused, which
may result in improper negotiation.
Possible Causes
An unexpected multiplex section termination (MST) occurs and lasts long due to incorrect
configurations and invalid links.
Procedure
Step 2 Verify that the service cross-connection is bound correctly on the VCTRUNK port. Then, check
whether the LCAS_FOPT alarm is cleared.
----End
Related Information
None.

4.68 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating loss of partial bandwidth in the LCAS receive direction.
This alarm is reported when only some of the configured channels carry load in the receive
direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the available bandwidth in the receive direction decreases, but services
still keep running.
Possible Causes
l Bidirectional services are not configured.
l The downstream channels bound at the local end outnumber the upstream channels bound
at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
improperly connected physical links.
Procedure
Step 1 Check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM. If any of them
exists, clear it first and check whether the LCAS_PLCR alarm is cleared.
Step 2 If the alarm persists, verify the connectivity of the physical link and check whether bidirectional
services are configured. If bidirectional services are not configured, correctly configure them
and check whether the LCAS_PLCR alarm is cleared.
Step 3 If the alarm persists, check whether the number of downstream timeslots configured for the local
VCTRUNK port is consistent with that of upstream timeslots configured for the peer VCTRUNK
port on the NMS. If the number of timeslots is inconsistent, add or delete timeslots as required
to make the number of timeslots consistent. Then, check whether the LCAS_PLCR alarm is
cleared.
Step 4 Check whether the cross-connections are bound from the transmit end to the receive end. If the
cross-connections are not bound, bind them and check whether the LCAS_PLCR alarm is
cleared.

Step 5 If the alarm persists, check the wait-to-restore (WTR) duration and wait until the WTR expires.
Then, check whether the LCAS_PLCR alarm is cleared.
Step 6 If the alarm persists, disable and enable the LCAS protocol on the VCTRUNK port. Then, check
whether the LCAS_PLCR alarm is cleared.
Step 7 If the alarm persists, delete and re-bind all physical channels of the VCTRUNK port and check
whether the LCAS_PLCR alarm is cleared.
Step 8 If the alarm persists, cold reset the board and check whether the LCAS_PLCR alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_PLCR alarm is cleared.
----End
Related Information
None.
4.69 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating loss of partial bandwidth in the LCAS transmit
direction. This alarm is reported when only some of the configured channels carry load in the
transmit direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the available bandwidth in the transmit direction decreases. This results
in packet loss when the actual outgoing traffic exceeds the available bandwidth.
Possible Causes
l The upstream channels bound at the local end outnumber the downstream channels bound
at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
improperly connected physical links.

Procedure
Step 2 Check the peer end for the LCAS_PLCR alarm. If the alarm exists at the peer end, clear it and
check whether the LCAS_PLCT alarm is cleared.
Step 3 If the alarm persists, check whether bidirectional services are configured on the port. If
bidirectional services are not configured, correctly configure them and check whether the
LCAS_PLCT alarm is cleared.
Step 4 If the alarm persists, check whether the number of upstream timeslots configured for the local
VCTRUNK port is consistent with that of downstream timeslots configured for the peer
VCTRUNK port on the NMS. If the number of timeslots is inconsistent, add or delete timeslots
as required to make the number of timeslots consistent. Then, check whether the LCAS_PLCT
alarm is cleared.
Step 5 If the alarm persists, verify that the cross-connections are correctly bound from the transmit end
to the receive end.
Step 6 If the alarm persists, check the wait-to-restore (WTR) duration and wait until the WTR expires.
Then, check whether the LCAS_PLCT alarm is cleared.
Step 7 If the alarm persists, disable and enable the LCAS function on the VCTRUNK port. Then, check
whether the LCAS_PLCT alarm is cleared.
whether the LCAS_PLCT alarm is cleared.
Step 9 If the alarm persists, cold reset the board and check whether the LCAS_PLCT alarm is cleared.
Step 10 If the alarm persists, replace the board and check whether the LCAS_PLCT alarm is cleared.
----End
Related Information
None.
4.70 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating loss of all bandwidth in the LCAS receive direction.
This alarm is reported when none of the configured channels carries load in the receive direction
after the LCAS function is enabled on the VCTRUNK port.
Attribute
Major Service alarm

Parameters
None.

When this alarm occurs, no bandwidth is available in the receive direction. That is, services are
interrupted in this direction.
Possible Causes
l The upstream channels are not bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or other
alarms.
Procedure
Step 2 Check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM. If any of them
exists, clear it first and check whether the LCAS_TLCR alarm is cleared.
Step 3 If the alarm persists, verify the connectivity of the physical link and check whether bidirectional
services are configured. If bidirectional services are not configured, correctly configure them
and check whether the LCAS_TLCR alarm is cleared.
Step 4 If the alarm persists, check whether timeslots are bound in the upstream direction at the peer
end. If timeslots are not bound in the upstream direction, correctly bind them and check whether
the LCAS_TLCR alarm is cleared.
Step 5 If the alarm persists, verify that the cross-connections are correctly bound from the transmit end
to the receive end. Then, check whether the LCAS_TLCR alarm is cleared.
whether the LCAS_TLCR alarm is cleared.
whether the LCAS_TLCR alarm is cleared.
Step 8 If the alarm persists, cold reset the board.
Step 9 If the alarm persists, replace the board and check whether the LCAS_TLCR alarm is cleared.
----End
Related Information
None.

4.71 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating loss of all bandwidth in the LCAS transmit direction.
This alarm is reported when none of the configured channels carries load in the transmit direction
after the LCAS function is enabled on the VCTRUNK port.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, there is no available bandwidth in the transmit direction. That is, services
are interrupted in this direction.
Possible Causes
l The downstream channels are not bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or other
alarms.
Procedure
Step 2 Check the peer end for the LCAS_TLCR alarm. If the alarm exists at the peer end, clear it and
check whether the LCAS_TLCT alarm is cleared.
Step 3 If the alarm persists, check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM.
If any of them exists, clear it first and check whether the LCAS_TLCT alarm is cleared.
Step 4 If the alarm persists, check whether timeslots are bound in the downstream direction at the peer
end. If timeslots are not bound in the downstream direction, correctly bind them and check
whether the LCAS_TLCT alarm is cleared.
Step 5 Verify that the cross-connections are correctly bound from the transmit end to the receive end.
Then, check whether the LCAS_TLCT alarm is cleared.

Step 8 If the alarm persists, cold reset the board and check whether the LCAS_TLCT alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_TLCT alarm is cleared.
----End
Related Information
None.
4.72 LCS_DAYS_OF_GRACE
Description
The LCS_DAYS_OF_GRACE is an alarm indicating a license in the grace period. This alarm
is reported when a license enters the grace period after its life cycle expires.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of a feature.
Parameter 3, Parameter 4 Indicate the number of days when the license can be reserved.
Parameter 5 Indicates the type of license invalidity.

l 0x01: The license file becomes invalid.
l 0x02: The equipment serial number (ESN) specified in the
license file does not match that of the equipment.
l 0x03: The V/R version of the license file does not match the
software version of the equipment.
l 0x04: Both the ESN and V/R version of the license file do not
match the ESN and software version of the equipment.
NOTE
If parameters 1 and 2 are not 0x00, the value of parameter 5 is fixed at 0x00.


If a license file is not updated in the grace period, the system or license-controlled feature will
enter the default state when the grace period expires.
Possible Causes
l Cause 1: The NE remains in the grace period of 60 days due to an invalid license file.
l Cause 2: The NE remains in the grace period of 60 days due to the ESN or V/R version
mismatch.
l Cause 3: The NE remains in the grace period of 60 days because the life cycle of the existing
license has expired.
Procedure
Step 1 Contact Huawei technical engineers to install a correct license file on the NE.
----End
Related Information
State Definition
Normal state
Trial state
Default state
State Transition

Normal
state
Default Trial
state state

grace period.
license expire.
license expire.
grace period.
4.73 LCS_EXPIRED
Description
The LCS_EXPIRED is an alarm indicating that a license file can no longer be used. This alarm
is reported when the grace period of the license file expires.

Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the number of days since the grace period of a license file
expires.
Parameter 3 Indicates the type of license invalidity.

l 0x01: The license file becomes invalid.
l 0x02: The equipment serial number (ESN) specified in the
license file does not match that of the equipment.
l 0x03: The V/R version of the license file does not match the
software version of the equipment.
l 0x04: Both the ESN and V/R version of the license file do not
match the ESN and software version of the equipment.

When this alarm occurs, the equipment enters the default state.
Possible Causes
l An NE with an invalid license file runs continuously even after the grace period expires.
l With a license file of incorrect equipment serial number (ESN) or V/R version, an NE runs
continuously even after the grace period expires.
Procedure
Step 1 Contact Huawei technical support engineers to install a correct license file on the equipment.
----End
Related Information
State Definition
Normal state

Trial state
Default state
State Transition
Normal
state
Default Trial
state state
grace period.
license expire.
license expire.

grace period.
4.74 LCS_FILE_NOT_EXIST
Description
The LCS_FILE_NOT_EXIST is an alarm indicating that a license file is not installed. This alarm
is reported when the required license is not installed on the license-controlled equipment.
Attribute
Parameters
None.

When this alarm occurs, the equipment enters the default state.
Possible Causes
The equipment is started up, but the required license file does not exist in the system.
Procedure
Step 1 Contact Huawei technical support engineers to install a correct license file on the equipment.
----End
Related Information
State Definition
Normal state

Trial state
Default state
State Transition
Normal
state
Default Trial
state state
grace period.
license expire.
license expire.

grace period.
4.75 LOCK_CUR_FAIL
Description
The LOCK_CUR_FAIL is an alarm indicating a failure to lock the working current.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the pump laser.

When this alarm occurs, transmit optical power fails to be locked on the board, which affects
services over the whole optical line.
Possible Causes
The board is faulty.
Procedure
Step 1 Warm reset the board on the NMS. Then, check whether the LOCK_CUR_FAIL alarm is cleared.

----End
Related Information
None.
4.76 LOCKPOW_MIS
Description
The LOCKPOW_MIS is an alarm indicating that the value configured for locking the pump
optical power exceeds the specified threshold. This alarm is reported when the value configured
for locking the pump optical power exceeds the specified threshold on a board.
Attribute
Parameters
None.

When this alarm occurs, service quality may be affected.
Possible Causes
The value configured for locking the pump optical power exceeds the specified threshold on a
board.
Procedure
Step 1 On the NMS, locate the board and view the value range for locking the pump optical power of
the required optical port channel.
Step 2 Reconfigure the value for locking the pump optical power according to the value range.
----End
Related Information
None.

4.77 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating a remote receive failure on the VC-3 path. This alarm
is reported when a board detects bit 5 of the G1 byte is 1 for the VC-3 path.
Attribute
Parameters
None.

This alarm does not affect the local services, but indicates that services fail to be received by
the remote end.
Possible Causes
The peer end receives alarms, such as TU_AIS_VC3 and TU_LOP_VC3.
Procedure
Step 1 Clear the alarms, such as TU_AIS_VC3 and TU_LOP_VC3, on the remote board. Then, the
LP_RDI_VC3 alarm is cleared automatically.
----End
Related Information
None.
4.78 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating a mismatch between C2 bytes identifying VC-3
signals.

Attribute
Parameters
None.

When this alarm occurs, the system is not affected.
Possible Causes
l The type is inconsistent between the received and to-be-received signals. That is, the
received and to-be-received C2 bytes are different.
l The service type is set incorrectly.
Procedure
Step 1 View the alarm on the NMS and determine the number of the path that reports the alarm.
Step 2 Check whether the C2 byte is consistent between the VC-3 paths at the local and peer ends. If
the C2 byte is inconsistent, modify the C2 byte on the VC-3 path at either end to keep its
consistency. Then, check whether the LP_SLM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the VC-3 services are correctly configured. If the services
are incorrectly configured, correctly configure them and check whether the LP_SLM_VC3 alarm
is cleared.
Step 4 If the alarm persists, replace the local board that reports the alarm.
Step 5 If the alarm still persists, replace the peer board as required.
----End
Related Information
None.
4.79 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that the VC-3 path carries no service. This alarm is
reported when a board detects that the C2 byte is 0.

Attribute
Parameters
None.

When this alarm occurs, the VC-3 path carries no service. If the alarm is caused by the incorrect
service configurations or no accessed service, services will be interrupted.
Possible Causes
l The service type is set incorrectly.
l No service is accessed.
Procedure
Step 1 View the alarm on the NMS and determine the number of the path that reports the alarm.
Step 2 Verify that the service type is correctly set and services are correctly accessed. Then, check
whether the LP_UNEQ_VC3 alarm is cleared.
----End
Related Information
None.
4.80 LPT_RFI
Description
The LPT_RFI is an alarm indicating that the link-state pass through (LPT) detects a remote port
failure. This alarm is reported when the LPT detects that a remote port or its LPT service network
fails.
Attribute
Parameters
None.


When this alarm occurs during data transmission, the active link is unavailable and services are
interrupted, which enables the standby link.
Possible Causes
l The remote port fails. For example, the port reports the LINK_ERR alarm or is not enabled.
l The LPT service network is faulty when:
– Fiber cut occurs.
– There are bit error threshold-crossing alarms, such as B3_EXC.
– There are alarms, such as VCAT_LOA, VCAT_LOM_VC3, VCAT_LOM_VC4, and
LP_UNEQ_VC3.
Procedure
Step 1 View the alarm on the NMS, and determine the board that reports the alarm and the ID of the
port that reports the alarm according to alarm parameters.
Step 2 Check whether the remote port is enabled. If the port is not enabled, enable it and check whether
the LPT_RFI alarm is cleared.
Step 3 If the alarm persists, check the remote end for the LINK_ERR alarm. If the alarm exists, clear
it and check whether the LPT_RFI alarm is cleared.
Step 4 If the alarm persists, check whether the remote LPT service network is faulty.
l If fiber cut occurs, replace the fiber.
l If there are bit error threshold-crossing alarms, such as B3_EXC, clear them and check
whether the LPT_RFI alarm is cleared.
l If there are alarms, such as VCAT_LOA, VCAT_LOM_VC3, VCAT_LOM_VC4, and
LP_UNEQ_VC3, clear them and check whether the LPT_RFI alarm is cleared.
----End
Related Information
None.
4.81 LSR_COOL_ALM
Description
The LSR_COOL_ALM is an alarm indicating that the cooling current of a laser exceeds the
specified threshold.
Attribute

Parameters
None.

When this alarm occurs, the optical module works improperly, which affects service receiving
and transmitting.
Possible Causes
l The environment temperature is high.
l The laser is faulty.
Procedure
Step 1 Check whether the environment temperature is high. If the temperature is high, adjust it into the
normal range. Then, check whether the LSR_COOL_ALM alarm is cleared.
Step 2 If the alarm persists, the laser may be faulty. In this case, replace the optical module if it is
pluggable on the board, or replace the board if the optical module is unpluggable.
----End
Related Information
None.
4.82 LSR_INVALID
Description
The LSR_INVALID is an alarm indicating an illegal optical module. This alarm is reported
when the optical module cannot be authenticated.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates why an optical module is illegal.

l 0x01: The optical module has no license.
l 0x02: The optical-module license fails to be verified.
0xFF: indicates no alarm parameter meaning.

Possible Causes
l The optical module has no license.
l The optical-module license fails to be verified.
Procedure
Step 1 Substitute an optical module with a correct license for the existing optical module. After the
license verification is successful, the LSR_INVALID alarm is cleared.
----End
Related Information
None.
4.83 MS_APS_INDI_EX
Description
The MS_APS_INDI_EX is an extended alarm indicating the status of a multiplex section (MS).
This alarm is reported when MS switching is performed, indicating that services are being
switched.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the type of the protection group to which the MS belongs.
l 0x01: indicates a linear MS
l 0x02: indicates a ring MS
Parameter 2, Parameter 3 Indicates the ID of the multiplex section protection (MSP) group.
Parameter 4 Indicates the ID of the slot where the switching is performed.
Parameter 5 Indicates the ID of the optical port where the switching is

performed.

When this alarm occurs, if a fiber cut or another fault occurs, services are interrupted.
Possible Causes
l The external switching command is issued.
l An alarm, such as R_LOS, R_LOF, MS_AIS, HARD_BAD, B2_EXC, and B2_SD, or a
cold reset that triggers automatic MS switching occurs.
Procedure
Step 1 On the NMS, view this alarm and determine the IDs of the slot and optical port where the
switching occurs.
Step 2 On the NMS, check whether the MS is in a state of manual, forced, or locked switching. If yes,
clear the switching state. Then, the alarm will be cleared automatically.
Step 3 Perform the following operations if the MS is in the automatic switching state:
1. Check whether an alarm, such as R_LOS, R_LOF, MS_AIS, HARD_BAD, B2_EXC, and
B2_SD, or a cold reset that triggers automatic switching occurs on the service board in the
MS. If yes, clear the alarms or cold reset operation. Then, check whether the alarm is
cleared.
2. Check whether the service board configured with the MS is faulty. If yes, replace the faulty
board. Then, check whether the alarm is cleared.
3. Check whether the SCC board is faulty. If yes, replace the faulty board.
----End
Related Information
For a linear MS in 1+1 single-ended revertive mode, services are not automatically switched to
the working channel after the optical path recovers, and the MS_APS_INDI_EX alarm persists.
In this case, manually switch the services from the protection channel to the working channel.
The alarm is cleared only when the switching is successful.

4.84 MS_RDI
Description
The MS_RDI is an alarm indicating that data reception fails at the peer end of a multiplex section
(MS). This alarm is reported when the board detects that the last three bits of the K2 byte are
110. The peer NE reports this alarm to the local NE when the MS_AIS alarm occurs.
Attribute
Parameters
None.

When this alarm occurs, services on the local NE are not affected. Services received by the peer
NE, however, are interrupted.
Possible Causes
l The local NE receives an alarm such as R_LOS and MS_AIS.
l The local transmit board is faulty.
l The peer receive board is faulty.
Procedure
Step 1 Check whether an alarm, such as R_LOS, R_LOF, MS_AIS, B2_EXC, and B2_SD, occurs on
the peer board. If yes, clear the alarm. Then, check whether the MS_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the local board is faulty. If yes, cold reset the local board.
Then, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the local board. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the peer board is faulty. If yes, cold reset the peer board.
Step 5 If the alarm persists, replace the peer board. Then, check whether the alarm is cleared.
----End
Related Information
None.

4.85 MS_REI
Description
The MS_REI is an alarm indicating that bit errors occur at the remote end of a multiplex section
(MS). This alarm is reported when the local optical port receives the M1 byte which indicates
the number of block bit errors detected by BIP-N×24 (B2) on the peer NE.
Attribute
Warning Communication alarm
Parameters
None.

This alarm indicates that the B2 bit errors received by the peer NE exceed the threshold. Services
on the local NE are not affected but service quality on the peer NE deteriorates.
Possible Causes
The B2 bit errors received by the peer NE exceed the threshold.
Procedure
Step 1 After the B2_EXC and B2_SD alarms are cleared, the MS_REI alarm is automatically cleared.
----End
Related Information
None.
4.86 MSSW_DIFFERENT
Description
The MSSW_DIFFERENT is an alarm indicating that software versions are inconsistent between
the active and standby SCC boards.

Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: indicates the files in the flash memory

l 0x02: indicates the software that is running
l 0x03: indicates a special routine inspection object
Parameter 2, Parameter 3 Indicates the IDs of the inconsistent files on the SCC board.
Parameter 4 Indicates the cause of the alarm.

l 0x04: indicates that file versions are inconsistent on the active
and standby areas of a single SCC board.
l 0x08: indicates that file versions are inconsistent on the active
and standby SCC boards, or files in the corresponding
directories of the active and standby SCC boards have different
names.
l 0x0c: indicates that file versions are inconsistent in the active
and standby areas of a single SCC board, and file versions are
inconsistent on the active and standby SCC boards.

l If software versions are inconsistent between the active and standby SCC boards, the active/
standby switchover of the system is affected.
l If no software exists in the flash memory, the system cannot restart after power-off or reset.
Possible Causes
l The version of the software that is running on the active SCC board is inconsistent with
that on the standby SCC board.
l The software versions in the active and standby areas (OFS1 and OFS2) are inconsistent.
l On the active or standby SCC board, no file with the same name exists in the directory of
the peer SCC board.

Procedure
Step 1 Contact Huawei technical support engineers to reload the related software.
----End
Related Information
None.
4.87 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network has more than one
RPL_OWNER nodes.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2, Parameter 3, Indicates the ID of a port.

Parameter 4
0xFF: indicates no alarm parameter meaning.
Parameter 5, Parameter 6 Indicates the ID of the Ethernet ring protection

switching (ERPS).

All nodes on the ring network are disconnected, and services may be interrupted.
Possible Causes
All nodes must be configured with ERPS, and only a RPL_OWNER node can be configured on
the ring network. If a user configures more than one RPL_OWNER nodes, this alarm is reported.

Procedure
Step 1 Check whether node IDs in the NR and RB packets are the same as the ID of the RPL_OWNER
node. If yes, go to the next step.
Step 2 Reconfigure the ERPS protection, and ensure that only one RPL_OWNER node is configured
on the ring network. Then, the alarm will be automatically cleared.
----End
Related Information
None.
4.88 MUT_LOS
Description
The MUT_LOS is an alarm indicating that coupled signals are lost. This alarm is reported when
the input coupled signals on a board are lost.
Attribute
Parameters
None.

All services that traverse the optical port on the alarm-reporting board are interrupted.
Possible Causes
l No fiber connects to an optical port of the alarm-reporting board or the fiber is damaged.
l Signals are attenuated greatly during transmission.
l The alarm-reporting board is faulty.
Procedure
Step 1 Check whether the fibers are properly connected according to the engineering fiber connection
design. Input optical signals with different wavelengths must be accessed to the specified input
optical ports. If not, correct the fiber connection according to the design.
Step 2 If the alarm persists, use an optical power meter to measure the receive optical power on the
local NE and check whether the receive optical power is within the normal range.

Step 3 If the receive optical power on the local NE is below the lower threshold, use the method of
handling the SUM_INPWR_LOW alarm to troubleshoot this problem.
Step 4 If the alarm persists, check whether the transmit optical power on the peer NE is normal. If no,
the peer board or its optical module is damaged. In this case, replace the peer board.
Step 5 If the alarm persists, the local board is faulty. Replace the local board.
----End
Related Information
None.
4.89 NEBD_XC_DIF
Description
The NEBD_XC_DIF is an alarm indicating that the cross-connection matrix data is inconsistent
between an NE and its boards. This alarm is reported when the cross-connection data stored on
the SCC board and a board that supports service cross-connections is inconsistent.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of a board.
Parameter 3 Indicates the cross-connection type. For example, 0x03 indicates

the space-division cross-connection.

During service scheduling and a cold reset on the board, services are interrupted.
Possible Causes
l The cross-connection data stored on the board is incorrect.
l The cross-connection data stored on the SCC board is incorrect.

Procedure
Step 1 View the alarm on the NMS and record the slot ID of the alarm-reporting board.
Step 2 Configure correct cross-connection data on the NMS. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, warm reset the board related to service cross-connections on the NMS.
Step 4 If the alarm persists, warm reset the SCC board on the NMS.
----End
Related Information
None.
4.90 NESF_LOST
Description
The NESF_LOST is an alarm indicating that software is lost. This alarm is reported when the
software is lost on the SCC board.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates that the type of the file that the board software is lost.

If software is lost on both the active and standby SCC boards, the SCC boards have been reset
or powered off. As a result, the SCC boards malfunction, and the NMS cannot monitor NEs after
the SCC boards are powered on.
Possible Causes
No software is loaded for the SCC board after the existing software is deleted.

Procedure
Step 1 Load software for the SCC board. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, the board may be faulty. Replace the faulty board.
----End
Related Information
None.
4.91 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that an NE is in the installation state. This
alarm is reported when the NE is newly delivered or a user issues a command to initiate the NE.
Attribute
Parameters
None.

When this alarm occurs, the NE is not configured. Download configurations for the NE.
Otherwise, the NE cannot be configured with services.
CAUTION
After this alarm is reported, you can only download data.
If you attempt to unload data, only blank data will be uploaded. As a result, services will be
interrupted after the blank data is applied.
Possible Causes
l A user has issued a command to initiate the NE but not performed a verification test.
l The NE is in the initial state and configured with no data.
l The database on the SCC board is faulty.
l If only an SCC board is used, replace the main control board.

Procedure
Step 1 Reapply the configuration data and perform a verification test. Then, check whether the alarm
is cleared.
Step 2 If the alarm persists, replace the faulty board.
----End
Related Information
None.
4.92 NO_BD_PARA
Description
The NO_BD_PARA is an alarm indicating that a board has no parameter table file.
Attribute
Parameters
None.

When this alarm occurs, user services may be affected.
Possible Causes
l The parameter table for the laser is not downloaded.
l Board parameters are not configured.
l The configured board parameters are lost.
Procedure
Step 2 Cold reset the faulty board. Then, check whether the alarm is cleared..
----End
Related Information
None.

4.93 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that some necessary files do not exist on a board. For
example, board software and logical software files do not exist.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the serial numbers of the lost files.

l 0x00, 0x01: indicate that software on the active board is lost.
l 0x00, 0x02: indicate that software on the standby board is lost.
l 0x00, 0x03: indicate that the active EPGA file is lost.
l 0x00, 0x04: indicate that the standby EPGA file is lost.
l 0x00, 0x05: indicate that the active INI file is lost.
l 0x00, 0x06: indicate that the standby INI file is lost.
l 0x00, 0x07: indicate that the active E1Map logic file is lost.
l 0x00, 0x08: indicate that the standby E1Map logic file is lost.
Parameter 3 Indicates the type of the fault.

l 0x01: indicates the file is lost.
l 0x02: indicates that file verification fails.
l 0x04: indicates that the versions are inconsistent between the
active and standby areas.
l 0x08: indicates the versions are inconsistent between the active
and standby boards.
l 0x0E: indicates that file verification fails. The file version is
inconsistent with that of the standby area and the standby board.

The impact of the alarm on the system is as follows:

l If the board that reports the alarm is not reset, the services and functions of the board are
not affected.
l If the board that reports the alarm is reset, the board may fail to start. If the processing
boards are not configured with protection, services are interrupted. If the processing boards
are configured with protection, services are switched.
Possible Causes
l The board software is unloaded.
l The board software is lost during running.
l Internal errors are detected on the board.
Procedure
Step 1 Load software for the board and warm reset the faulty board on the NMS. Then, check whether
----End
Related Information
None.
4.94 NO_ELABEL
Description
The NO_ELABEL is an alarm indicating that the electronic label does not exist. This alarm is
reported when a board is unloaded with an electronic label or the existing electronic label is lost.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the carrier type of the electronic label.

l 0x01: mother board
l 0x02: subboard
l 0x03: optical module
Parameter 2, Parameter 3 Indicates the serial number of the carrier.

None.
Possible Causes
The electronic label is unloaded or lost.
Procedure
Step 2 Replace the faulty board.
----End
Related Information
None.
4.95 NODEID_MM
Description
The NODEID_MM is an alarm indicating that node IDs do not match in a multiplex section
(MS). This alarm is reported when the node IDs configured for each node in the MS do not
match.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the ID of the multiplex section protection (MSP) group where the alarm
occurs.

When this alarm occurs, MSP switching fails, and the squelching function fails if it is enabled.
Possible Causes
The eastward and westward node IDs configured for each node on the MS ring do not match.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the MSP group where the alarm occurs
according to the alarm parameters.
Step 2 Check whether the eastward and westward node IDs configured for each node on the MS ring
match. If not, reconfigure node IDs for each node on the MS ring according to the configuration
rules, and the alarm will be automatically cleared.
l Each NE ID must be unique on the MS ring.
l If node A is to the west of its neighboring node B, the local node ID of node A must be the
same as the westward node ID of node B, and the local node ID of node B must be the same
as the eastward node ID of node A.
Step 3 Restart the MS protocol. Then, the alarm is automatically cleared.
----End
Related Information
None.
4.96 OA_LOW_GAIN
Description
The OA_LOW_GAIN is an alarm indicating that the gain of an optical amplifier declines. This
alarm is reported when the gain of the optical amplifier board is 3 dB lower than the nominal
value.
Attribute
Critical Service alarm
Parameters


Name Meaning
Parameter 1 Indicates the ID of the optical port where the alarm occurs. The
value varies with the type of the optical amplifier and is fixed at
0x02 or 0x04.
Parameter 2, Parameter 3 Indicates the ID of the channel where the alarm occurs. The value
consists of two bytes and is fixed at 0x00 0x01.

The impact of the alarm on the system varies with the cause of the alarm.
l If this alarm occurs due to the high input optical power, the redundancy of the system
declines. As a result, later system expansion is affected.
l If this alarm occurs due to other causes, for example, excessive insertion loss between the
TDC and RDC optical ports of the OAU board, the input power of downstream signals will
be low. As a result, the redundancy of the system declines. Bit errors may even occur in
the services, and services may be interrupted.
Possible Causes
l The input optical power of the board is above the upper threshold.
l For the OAU board, excessive insertion loss occurs between the TDC and RDC optical
ports.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range on the U2000. If
yes, perform the following operations:
1. Adjust the optical attenuator in front of the receive optical port to make the input optical
power within the normal range.
2. If no optical attenuator exists, add a fixed or adjustable attenuator to make the input optical
power within the normal range.
Step 2 Query the output optical power of the TDC optical port and input optical power of the RDC port
of the OAU board and calculate the insertion loss between the two optical ports.
NOTE
Insertion loss = Input optical power of the TDC optical port - Output optical power of the RDC optical port
1. If the insertion loss is excessive, clean the pigtail and fiber connectors that connect the TDC
and RDC ports. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the DCM module between the TDC and RDC ports. Then,
----End

Related Information
None.
4.97 ODU_AIS
Description
The ODU_AIS is an alarm indicating an optical demultiplexing unit (ODU) alarm.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is unavailable.
Possible Causes
The possible causes of the alarm are as follows:
l Severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur on the local NE.
l Upstream services are damaged.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur
on the local NE. If yes, clear these alarms first. Then, check whether the ODU_AIS alarm is
cleared.
Step 2 If the ODU_AIS alarm persists, locate the NE (FR NE) that initially reports the ODU_AIS alarm.
Then, repeat the preceding step.
Step 3 If the ODU_AIS alarm persists, check whether severer alarms occur on the upstream NE (PR
NE) of the FR NE. If yes, clear the alarms.
Step 4 If the ODU_AIS alarm persists, perform a loopback on the transmit optical ports of NEs from
the FR NE in the upward direction. Locate the NE (FL NE) that initially reports the ODU_AIS
alarm or severer alarms. Then, perform the following steps:
1. Check whether configurations on the FL NE are correct. If no, correct connection and
configurations.
2. If the ODU_AIS persists, replace the line board on the FL NE.

3. If the ODU_AIS persists, replace the cross-connect board on the FL NE.
----End
Related Information
None.
4.98 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the optical demultiplexing unit (ODU)
channel are locked.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is locked so that no customer service can be
carried.
Possible Causes
l The ODU channel is being tested.
Procedure
Step 1 Check whether the ODU channel is being tested. If yes, wait until the test is completed and
unlock the ODU channel. Then, check whether the alarm is cleared.
Step 2 If the ODU channel is not being tested, unclock it. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, the board is faulty. Replace the board.
----End
Related Information
None.

4.99 ODU_OCI
Description
The ODU_OCI is an alarm indicating no connection at the optical demultiplexing unit (ODU)
layer.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is disconnected. As a result, services are
unavailable.
Possible Causes
l Severer alarms occur on the local NE, such as the R_LOS, FEC_LOF, and OTU_AIS
alarms.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur
on the local NE. If yes, clear these alarms first. Then, check whether the ODU_OCI alarm is
cleared.
Step 2 If the alarm persists, upstream services may be faulty. If the upstream device is an OSN device,
replace the line board. If the upstream device is not an OSN device, add cross-connections for
the downstream ODU channel that has received the ODU_OCI alarm according to the related
alarm handling document.
Step 3 If the alarm persists, the local board is faulty. Then, replace the local board.
----End
Related Information
None.

4.100 OH_LOOP
Description
The OH_LOOP is an alarm indicating an overhead bus loopback on a line board.
Attribute
Minor Security alarm
Parameters
Name Meaning
Parameter 1 Indicates the loopback mode.

l 0x01: outloop
l 0x02: loopback of the clock board
l 0x03: loopback of the SCC board

When this alarm occurs, a loopback occurs on the overhead bus of the line board. Services are
not affected but ECC communications are interrupted.
Possible Causes
A loopback occurs on the overhead bus of the line board.
Procedure
Step 1 Release the loopback, and the alarm is automatically cleared.
----End
Related Information
None.

4.101 OMS_BDI
Description
The OMS_BDI is an alarm indicating a backward defect at the optical multiplex section (OMS)
layer. This alarm is reported to suppress the OMS_BDI_P and OMS_BDI_O alarms.
Attribute

Parameters
None.

If the alarm is caused by incorrect fiber connection, services are not affected. In other cases,
services are interrupted.
Possible Causes
The OMS_BDI_P and OMS_BDI_O alarms exist.
Procedure
Step 1 See the methods of handling the OMS_BDI_P and OMS_BDI_O alarms.
----End
Related Information
None.
4.102 OMS_BDI_O
Description
The OMS_BDI_O is an alarm indicating a backward defect in the overhead signals at the optical
multiplex section (OMS) layer. The downstream NE inserts a OMS_BDI_O signal to the
upstream NE after receiving no overhead signal from the upstream NE.

Attribute
Parameters
None.

monitoring management of the system is affected.
Possible Causes
l The physical fiber connection is inconsistent with the logical fiber connection.
l Due to a fiber cut, low power, or dispersion, the downstream NE detects no overhead signal.
Then, it inserts a BDI_O overhead signal to the local OMS layer. The local NE reports the
OMS_BDI_O alarm after receiving the BDI_O overhead signal.
Figure 4-4 Detection of the OMS_BDI_O alarm

NE 2 detects
that the
OMS_BDI_O NE 2 sends a NE2 inserts OMS_FDI_O
overhead
an FDI_O
BDI_O signal signal is lost.
signal to NE
to NE 1.
3.
NE 1 NE 2 NE 3
... ...
（upstream) (local) (downstream)
Uplink signal flow
Procedure
Step 1 As shown in Figure 4-4, check whether physical fiber connection and logical fiber connection
are consistent on the local and upstream boards. If they are inconsistent, adjust the connection.
Step 2 Check whether the laser on the upstream board is started. If not, start the laser. Then, check
Step 3 If the alarm persists, correctly connect the fiber between the local receive port and the upstream
transmit port. Then, check whether the alarm is cleared.

Step 4 If the alarm persists, check whether signals are excessively attenuated on the transmission line.
If yes, clean the fiber connectors and optical ports for the local receive port and the upstream
----End
Related Information
None.
4.103 OMS_BDI_P
Description
The OMS_BDI_P is an alarm indicating a backward defect in the payload signals at the optical
multiplex section (OMS) layer. The downstream NE inserts an OMS_BDI_P signal to the
upstream NE after receiving no payload signal from the upstream NE.
Attribute
Parameters
None.

Possible Causes
l Physical fiber connection is inconsistent with logical fiber connection.
l Due to a fiber cut, low power, or dispersion, the downstream NE detects no payload signal.
Then, it inserts a BDI_P overhead signal to the local OMS layer. The local NE then reports
the OMS_BDI_P alarm after receiving the BDI_P overhead signal.

Figure 4-5 Detection of the OMS_BDI_P alarm

NE 2 detects
that the
OMS_BDI_P NE 2 sends a NE 2 inserts OMS_FDI_P
payload signal
an
BDI_P signal is lot.
FDI_P signal
to NE 2.
to NE 3.
NE 1 NE 2 NE 3
... ...
(Upstream) (Local) (Downstream)
Uplink signal flow
Procedure
are consistent on the local and upstream boards. If they are inconsistent, adjust the connection.
Step 2 Check whether the laser on the upstream board is started. If not, start the laser. Then, check
Step 3 If the alarm persists, correctly connect the fiber between the local receive port and the upstream
Step 4 If the alarm persists, check whether signals are excessively attenuated on the transmission line.
If yes, clean the fiber connectors and optical ports for the local receive port and the upstream
----End
Related Information
None.
4.104 OMS_FDI
Description
The OMS_FDI is an alarm indicating a forward defect at the optical multiplex section (OMS)
layer. The local board inserts an OMS_FDI signal to the downstream NE after detecting signal
loss. The downstream NE then reports the OMS_FDI alarm after receiving the OMS_FDI signal.
This alarm is reported to suppress the OMS_FDI_P and OMS_FDI_O alarms.

Attribute
Parameters
None.

When this alarm occurs, services may be interrupted.
Possible Causes
l Physical fiber connection is inconsistent with logical fiber connection.
l Due to a fiber cut, low power, or dispersion, the local NE detects signal loss. Then, it inserts
an OMS_FDI signal to the downstream NE.
Procedure
Step 1 See the methods of handling the OMS_FDI_P and OMS_FDI_O alarms.
----End
Related Information
None.
4.105 OMS_FDI_O
Description
The OMS_FDI_O is an alarm indicating a forward defect in the overhead signals at the optical
multiplex section (OMS) layer. The local board inserts an FDI_O overhead signal to the
downstream NE after detecting overhead signal loss. The downstream NE then reports the
OMS_FDI_O alarm after receiving the FDI_O overhead signal.
Attribute
Parameters
None.


Possible Causes
l Due to a fiber cut, low power, or dispersion, the local NE detects overhead signal loss.
Then, it inserts an FDI_O overhead signal to the local OMS layer. The downstream NE
then reports the OMS_FDI_O alarm after receiving the FDI_O overhead signal.
Figure 4-6 Detection of the OMS_FDI_O alarm

NE 2 detects
that the
OMS_BDI_O NE 2 sends a NE2 inserts OMS_FDI_O
overhead
an FDI_O
BDI_O signal signal is lost.
signal to NE
to NE 1.
3.
NE 1 NE 2 NE 3
... ...
（upstream) (local) (downstream)
Uplink signal flow
Procedure
are consistent on the local board. If they are inconsistent, adjust the connection. Then, check
Step 2 Handle alarms on upstream NEs along the service flow by referring to the method of handling
the OMS_BDI_O alarm. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.106 OMS_FDI_P
Description
The OMS_FDI_P is an alarm indicating a forward defect in the payload signals at the optical
multiplex section (OMS) layer. The local optical transmission section (OTS) layer inserts an

OMS_FDI_P overhead signal to the downstream NE after detecting payload signal loss. The
downstream NE then reports the OMS_FDI_P alarm after receiving the OMS_FDI_P overhead
signal from the upstream OTS layer.
Attribute
Parameters
None.

Possible Causes
l Due to a fiber cut, low power, or dispersion, the local OTS layer detects payload signal
loss. Then, it inserts an FDI_P overhead signal to the downstream OMS layer. The
downstream NE then reports the OMS_FDI_P alarm after receiving the FDI_P overhead
signal.
Figure 4-7 Detection of the OMS_FDI_P alarm

NE 2 detects
that the
OMS_BDI_P NE 2 sends a NE 2 inserts OMS_FDI_P
payload signal
an
BDI_P signal is lot.
FDI_P signal
to NE 2.
to NE 3.
NE 1 NE 2 NE 3
... ...
(Upstream) (Local) (Downstream)
Uplink signal flow
Procedure

the OMS_BDI_P alarm. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.107 OMS_SSF
Description
The OMS_SSF is an alarm indicating a service signal failure at the optical multiplex section
(OMS) layer. This alarm is reported to suppress the OMS_SSF_P and OMS_SSF_O alarms.
Attribute
Parameters
None.

Possible Causes
The OMS_SSF_P and OMS_SSF_O alarms exist.
Procedure
Step 1 See the methods of handling the OMS_SSF_P and OMS_SSF_O alarms.
----End
Related Information
None.

4.108 OMS_SSF_O
Description
The OMS_SSF_O is an alarm indicating an overhead signal failure at the optical multiplex
section (OMS) layer. This alarm is reported when the local board detects an overhead signal
failure or receives an FDI_O signal from the upstream OMS layer.
Attribute
Parameters
None.

Possible Causes
l The local board detects overhead signal loss because the peer NE does not send an overhead
signal due to a fiber cut, low power, or dispersion.
Figure 4-8 Detection of the OMS_SSF_O alarm

NE 2 detects that
the overhead
NE 1 inserts an
signal fails.
FDI_O signal to
NE 2.
NE 1 NE 2 NE 3
... (local) ...
(upstream) (downstream)
OMS_SSF_
O
Uplink signal flow

Procedure
the OMS_BDI_O alarm. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.109 OMS_SSF_P
Description
The OMS_SSF_P is an alarm indicating a payload signal failure at the optical multiplex section
(OMS) layer. This alarm is reported when the local board detects a payload signal failure or
receives an FDI_P signal from the upstream OMS layer.
Attribute
Parameters
None.

Possible Causes
l The optical transmission section (OTS) layer detects no signal due to a fiber cut, low power,
or dispersion.

Figure 4-9 Detection of the OMS_SSF_P alarm

NE 2 detects that
the payload
NE 1 inserts an
signal fails.
FDI_P signal to
NE 2.
NE 1 NE 2 NE 3
...
(upstream) (local) (downstream) ...
OMS_SSF_
P
Uplink signal flow
Procedure
the OMS_BDI_P alarm. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.110 OOL
Description
The OOL is an alarm indicating that a phase-locked loop is out of lock. This alarm is reported
when the phase-locked loop on the clock board is faulty.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the phase-locked loop that is out of lock.

l 0x01: first 2M phase-locked loop
l 0x02: second 2M phase-locked loop
l 0x03: 155M system phase-locked loop

When this alarm occurs, the phase-locked loop cannot lock on the input signals, and therefore
the output clock signals are affected. This alarm may lower service quality or interrupt services.
Possible Causes
The hardware of the phase-locked loop on the clock board is faulty.
Procedure
Step 1 Cold reset the clock board. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the faulty clock board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.111 OPA_FAIL_INDI
Description
The OPA_FAIL_INDI is an alarm indicating an automatic adjustment failure of optical cross-
connections. This alarm is reported when the attenuation calculated by the system exceeds the
acceptable range.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the wavelength serial number of the optical cross-connections.

When this alarm occurs, board attenuation is not adjusted. As a result, existing service quality
cannot be improved, and new services may be interrupted.
Possible Causes
The rated optical power of the (optical amplifier) OA board is out of range.
Procedure
Step 1 Check whether board attenuation is within the normal range. If it is not within the normal range,
manually adjust the optical power of the line. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, adjust the rated optical power for the receive or transmit optical port of the
OA board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.112 OTU_AIS
Description
The OTU_AIS is an alarm indicating an optical transponder unit (OTU) alarm.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is disconnected. As a result, services are
unavailable.

Possible Causes
l Severer alarms occur on the local NE, such as the R_LOS, and FEC_LOF alarm.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS and FEC_LOF, occur on the local
NE. If yes, clear these alarms first. Then, check whether the OTU_AIS alarm is cleared.
Step 2 If the OTU_AIS alarm persists, locate the NE (FR NE) that initially reports the OTU_AIS alarm.
Then, repeat the preceding step.
Step 3 If the OTU_AIS persists, check whether severer alarms occur on the upstream NE (PR NE) of
the FR NE. If yes, clear the alarms.
Step 4 If the OTU_AIS alarm persists, perform a loopback on the transmit optical ports of NEs from
the FR NE in the upward direction. Locate the NE (FL NE) that initially reports the OTU_AIS
alarm or severer alarms. You can skip this step because fiber loopback interrupts services. If
fiber loopback is not allowed, replace the receive board on the FR NE and transmit board on the
PR NE.
1. Check whether configurations on the FL NE are correct. If no, correct connection and
configurations.
2. If the OTU_AIS persists, replace the line board on the FL NE.
3. If the OTU_AIS persists, replace the cross-connect board on the FL NE.
----End
Related Information
None.
4.113 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame align signal (FAS) at the optical transponder
unit (OTU) layer is lost.
Attribute
Parameters
None.


Possible Causes
l The optical fiber is faulty or the optical power is out of range.
l Services that are transmitted from the peer NE are abnormal.
Procedure
Step 2 Check the input optical power of the board on the NMS. If the input optical power is below the
lower threshold, clean the fiber end and the connector. If the input optical power is above the
upper threshold, add an optical attenuator to adjust the optical power. Then, check whether the
alarm is cleared.
Step 3 If the alarm persists, check the output optical power of the peer board. If the optical power is
below the lower threshold, replace the peer board.
Step 4 If the alarm persists, check whether clocks of the local and peer NEs are synchronized with those
on the network. If not, set clock tracing. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, check the transmission fiber. If the fiber is functioning properly, replace
the board that reports the alarm.
Step 6 If the alarm persists, replace the local cross-connect board.
Step 7 If the alarm persists, replace the peer line board.
Step 8 If the alarm persists, replace the peer cross-connect board.
----End
Related Information
None.
4.114 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the frame align signal (FAS) at the optical transponder
unit (OTU) is lost.
Attribute
Major Service alarm

Parameters
None.

When this alarm occurs, multiframes are lost, and services are interrupted.
Possible Causes
l The local NE has not received the expected consecutive number of frames.
l The bit errors during transmission are excessive.
Procedure
Step 2 Check the input optical power of the board on the NMS. If the input optical power is below the
lower threshold, clean the fiber end and the connector. If the input optical power is above the
upper threshold, add an optical attenuator to adjust the optical power. Then, check whether the
alarm is cleared.
Step 3 If the alarm persists, check the output optical power of the peer board. If the optical power is
below the lower threshold, replace the peer board.
Step 4 If the alarm persists, check whether clocks of the local and peer NEs are synchronized with those
on the network. If not, set clock tracing. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, check the transmission fiber. If the fiber is functioning properly, replace
the board that reports the alarm.
Step 6 If the alarm persists, replace the source board of the OTU channel (excluding the NEs that
transparently transmit the ODU channel).
----End
Related Information
None.
4.115 OUT_PWR_ABN
Description
The OUT_PWR_ABN is an alarm indicating that the output optical power is out of range.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates ID of an optical port.

When this alarm occurs, service transmission performance is affected, and services may be
interrupted.
Possible Causes
l The output optical power is out of range.
Procedure
Step 1 Check whether the wavelength of the input optical signals is within the normal range, or check
whether the board reports the PUM_BCM_ALM alarm. If the wavelength is out of range, adjust
the wavelength. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.116 PATCH_ACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating a patch package activation timeout. This
alarm is reported when activating the patch package times out.

Attribute
Parameters
None.

The patch package that is being activated is unstable. If the board is reset during the activation,
the patch does not take effect after the reset, and the patch is automatically restored to the
deactivated state. As a result, the functions of the patch are unavailable or the bugs that are fixed
by using the patch recur.
Possible Causes
The duration for the patch package that is in the activated state exceeds the specified value.
Procedure
Step 1 If the patch files are correct, run the patch on the NMS after the observation period.
Step 2 If the patch files are incorrect, delete them and reload correct patch files on the NMS.
----End
Related Information
None.
4.117 PATCH_DEACT_TIMEOUT
Description
The PATCH_DEACT_TIMEOUT is an alarm indicating a patch package deactivation timeout.
This alarm is reported when deactivating the patch package times out.
Attribute
Parameters
None.


The deactivated state indicates that the patch is loaded but not running. If the board is reset at
this time, the patch is automatically restored to the idle state after the NE is restarted. As a result,
the functions of the patch are unavailable or the bugs that are fixed by using the patch recur.
Possible Causes
The duration for the patch package that is in the deactivated state exceeds the specified value.
Procedure
----End
Related Information
None.
4.118 PATCH_ERR
Description
The PATCH_ERR is an alarm indicating a patch file error. This alarm is reported when the board
detects that the patch files are incorrect.
Attribute
Parameters
None.

When this alarm occurs, the functions of the patch are unavailable or the bugs that are fixed by
using the patch recur.
Possible Causes
If a patch is running before the NE restarts, the NE automatically loads and runs the patch after
the NE restarts. If abnormities occur at this time and patch loading fails, the PATCH_ERR is
reported.

Procedure
Step 1 Obtain correct patch files according to the Upgrade Guide and Version Mapping and reload the
patch files.
----End
Related Information
None.
4.119 PATCH_NOT_CONFIRM
Description
The PATCH_NOT_CONFIRM is an alarm indicating that a patch is not confirmed after it is
activated within the specified period.
Attribute
Parameters
None.

The activated state is an intermediate state of the patch for file effect observation, and the system
displays a message prompting you to confirm the patch files, which does not affect the system.
If the board is reset at this time, the patch does not take effect and changes to the deactivated
state.
Possible Causes
You have not confirmed the patch files after the patch is activated within the specified period.
Procedure
----End
Related Information
If the PATCH_NOT_CONFIRM alarm occurs, you do not need to clear the alarm immediately.
Confirm the patch and the patch files. Then, run a command to change the state of the activated
patch files and the alarm will be cleared.

4.120 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicating an error in the patch package file.
Attribute
Parameters
None.

When this alarm occurs, patch package loading management may fail on some boards.
Possible Causes
The patch package file is lost on some boards.
Procedure
Step 1 Contact Huawei technical support engineers to regenerate the patch package file.
----End
Related Information
None.
4.121 PATCHFILE_NOTEXIST
Description
The PATCHFILE_NOTEXIST is an alarm indicating that patch files do not exist. This alarm is
reported when a restarted NE detects no patch file.
Attribute

Parameters
None.

When this alarm occurs, the loaded patch cannot run properly but the system has some problems
to be resolved by using the patch.
Possible Causes
Patch files are running before the NE is restarted but lost after the NE is restarted.
Procedure
Step 1 Obtain correct patch files according to the Upgrade Guide and Version Mapping and reload the
patch files.
----End
Related Information
None.
4.122 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE is an alarm indicating that the optical module is not detected.
Attribute
Parameters
None.

When this alarm occurs, services are interrupted on the corresponding optical port.
Possible Causes
l The optical module is not or improperly installed to the slot.
l The optical module or board is faulty.

Procedure
Step 1 View the alarm on the NMS and record the slot ID of the alarm-reporting board.
Step 2 Check whether the optical module is properly installed to the slot. If not, install the optical
module properly. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the optical module. Replace the optical module if it is pluggable
on the board.
----End
Related Information
None.
4.123 PM_BDI
Description
The PM_BDI is an alarm indicating a backward defect in PM overheads at the optical
demultiplexing unit (ODU) layer. This alarm is reported when a major alarm occurs at the remote
ODU and upper layers.
Attribute
Parameters
None.

This alarm occurs only on the ODU termination NE for services in the transmit direction, which
does not affect services in the receive direction.
Possible Causes
l Alarms occur on the remote ODU termination NE.
l The local transmit unit is faulty.
l The remote receive unit is faulty.
Procedure
Step 1 Check whether severer alarms occur on the remote ODU termination NE. If yes, clear these
alarms first. Then, check whether the PM_BDI alarm is cleared.
Step 2 If the alarms at the remote end persist, perform an inloop on the local optical ports. If any alarms
occur, correct configurations according to the alarms.

CAUTION
A loopback interrupts services.
Step 3 If the PM_BDI alarm persists, replace the local board.
Step 4 If the alarms at the remote end persist and the loopback test detects no abnormities on the local
optical ports, replace the remote board.
----End
Related Information
None.
4.124 PM_BEI
Description
The PM_BEI is an alarm indicating a backward error in PM overheads at the optical
demultiplexing unit (ODU) layer. This alarm is reported when PM-BIP check bit errors occur
at the remote end.
Attribute
Parameters
None.

When this alarm occurs, PM_BIP check bit errors occur on the ODU termination NE, which
does not affect the FEC function and performance on the local NE.
Possible Causes
l Bit errors occur on the remote ODU termination NE.
Procedure
Step 1 Check whether bit errors occur on the ODU termination NE. If any bit errors occur, clear these
bit errors. Then, check whether the PM_BEI alarm is cleared.

Step 2 If the bit errors at the remote end persist, perform an inloop on the local optical ports to check
for alarms. If any alarms occur, correct configurations according to the alarms.
CAUTION
Step 3 If the PM_BEI alarm persists, replace the local board.
Step 4 If the bit errors at the remote end persist and the inloop test detects no abnormities on the local
----End
Related Information
None.
4.125 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the PM section at
the optical demultiplexing unit (ODU) layer exceeds the threshold.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, service transmission quality is affected.
Possible Causes
l The received signals are heavily attenuated.
l The connector is improperly connected.

Procedure
Step 1 On the NMS, check severer alarms, such as R_LOS and R_LOF, on the NMS. Clear these alarms
first and check whether the PM_BIP8_OVER alarm is cleared.
Step 2 Check whether the receive optical power of the alarm-reporting board is within the normal range.
If yes, go to step 9.
Step 3 Clean the local fiber connector and the receive optical port on the line board. Then, check whether
Step 4 Check whether the flange is correctly connected to the optical attenuator on the local NE, and
whether the attenuation value specified for the optical attenuator is proper. After determining
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
Step 5 Check whether the transmit optical power on the peer end is within the normal range. If not,
replace the line board.
Step 6 If the transmit optical power is within the normal range, clean the peer pigtail connector. Then,
Step 7 Check whether the flange is correctly connected to the optical attenuator on the peer NE, and
Step 8 Verify that optical fibers are properly connected. Then, check whether the alarm is cleared.
Step 9 Replace the local line board that reports the alarm. Then, check whether the alarm is cleared.
Step 10 Replace the local cross-connect board. Then, check whether the alarm is cleared.
Step 11 Replace the peer line board. Then, check whether the alarm is cleared.
Step 12 Replace the peer cross-connect board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.126 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the signals degrade in the PM section at the optical
transponder unit (OTU) layer.
Attribute
Major Service alarm

Parameters
None.

Possible Causes
Procedure
Step 1 On the NMS, check severer alarms, such as R_LOS and R_LOF, on the NMS. Clear these alarms
first and check whether the PM_BIP8_SD alarm is cleared.
Step 3 Clean the local fiber connector and the receive optical port on the line board. Then, check whether
Step 5 Check whether the transmit optical power on the peer end is within the normal range. If not,
replace the line board.
----End
Related Information
None.

4.127 PM_TIM
Description
The PM_TIM is an alarm indicating a trail trace identifier (TTI) mismatch in the PM overheads
at the optical demultiplexing unit (ODU) layer.
Attribute
Parameters
None.

When this alarm occurs, the FEC function and services are not affected.
Possible Causes
The PM_TTI byte to be received by the local NE is incorrectly set.
Procedure
Step 1 Check whether the SM_TTI byte to be received by the board is consistent with the received
SM_TTI byte. If not, modify the settings.
----End
Related Information
None.
4.128 PUM_BCM_ALM
Description
The PUM_BCM_ALM is an alarm indicating that the bias current of the pump laser exceeds
the threshold.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the serial number of a pump laser.
Parameter 2 Indicates the threshold-crossing type.

l 0x01: higher-threshold crossing
l 0x02: lower-threshold crossing

The PUM_BCM_ALM alarm may be caused by the aged pumper laser. When this alarm occurs,
services are not affected. Handle this alarm in a timely manner. Otherwise, the input optical
power of the board is affected and services are affected.
Possible Causes
l The input wavelength is incorrect.
l The input optical power is below the lower threshold.
l The ambient temperature is out of range, affecting the running of the laser.
Procedure
Step 1 Check whether the input wavelength is correct. If not, change it to the correct input wavelength.
Step 2 If the alarm persists, check whether the input optical power is within the normal range. If the
input optical power is low, adjust it so that it is within the normal range. Then, check whether
Step 3 If the alarm persists, check whether the ambient temperature is normal. If not, adjust the ambient
temperature.
Step 4 If the alarm persists, cold reset the board. Then, check whether the alarm is cleared.
CAUTION

Step 5 If the alarm still persists, replace the board.
----End
Related Information
None.
4.129 PUM_TEM_ALM
Description
The PUM_TEM_ALM is an alarm indicating that the ambient temperature of the pump laser
exceeds the threshold. This alarm is reported when the ambient temperature of the pump laser
on the optical amplifier (OA) board is below the lower threshold.
Attribute
Parameters
Name Meaning


The PUM_TEM_ALM alarm may be caused by the aged pumper laser. When this alarm occurs,
services are not affected. Handle this alarm in a timely manner. Otherwise, the input optical
power of the board is affected and services are affected.
Possible Causes
l The ambient temperature is out of range.
l The cooling system of the pump laser is damaged.
l The current of the pump laser is above the upper threshold.
Procedure
Step 1 Check whether the ambient temperature is normal. If not, adjust the ambient temperature for
equipment running. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, warm reset the alarm-reporting board on the NMS.

Step 3 If the alarm persists, remove and insert the alarm-reporting board while keeping services running.
Step 4 If the alarm still persists, replace the alarm-reporting board.
----End
Related Information
None.
4.130 PUMP_COOL_EXC
Description
The PUMP_COOL_EXC is an alarm indicating that the cooling current of a pump laser exceeds
the threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the serial number of a pump laser.


When this alarm occurs, optical components and the output signal performance deteriorate.
Possible Causes
l The ambient temperature of the board is out of range.
l The internal temperature of the pump laser is out of range.
Procedure
Step 1 Verify the ambient temperature of the equipment is within the normal range. Then, check

Step 2 If the alarm persists, replace the faulty board. Then, check whether the HP_SLM alarm is cleared.
----End
Related Information
None.
4.131 R_LOC
Description
The R_LOC is an alarm indicating no clock on the receive side of the line. This alarm is reported
when the line board cannot extract the clock from line signals.
Attribute
Parameters
None.

When this alarm occurs, services on the line port are interrupted.
Possible Causes
l The link is faulty so that the board cannot extract the clock.
l Clock tracing is incorrectly configured on the board.
Procedure
Step 1 Check whether the physical link is functioning properly. If not, rectify the link fault. Then, check
Step 2 If the alarm persists, check whether clock tracing configured on the board is the same as planned.
If not, modify the clock tracing configuration. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, cold reset the local line board that reports the alarm. Then, check whether
Step 4 If the alarm persists, the clock tracing module on the line board may be faulty. Replace the line
board and check whether the alarm is cleared.

Step 5 If the alarm still persists, check whether the clock board is faulty. If yes, replace the board. Then,
----End
Related Information
None.
4.132 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is an alarm indicating a critical alarm input.
Attribute
Parameters
None.

When this alarm occurs, the status of the external device that connects to the critical alarm input
port will change.
Possible Causes
l The status of the critical alarm input has changed.
l The RELAY_ALARM_CRITICAL alarm is a default setting for the alarm inputs on the
board. As a result, the alarm is reported by default.
Procedure
Step 1 Check whether the status of the external device has changed. If yes, rectify the external device
fault. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, check whether an external device is connecting to the alarm input port. If
not, set the port to unused, and the alarm will be cleared.
----End
Related Information
None.

4.133 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is an alarm indicating a warning alarm input.
Attribute
Parameters
None.

When this alarm occurs, the status of the external device that connects to the warning alarm
input port will change.
Possible Causes
l The status of the warning alarm input has changed.
l The RELAY_ALARM_IGNORE alarm is a default setting for the alarm inputs on the
board. As a result, the alarm is reported by default.
Procedure
Step 1 Check whether the status (for example, the door control status) of the external device has
changed. If yes, rectify the external device fault. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.134 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is an alarm indicating a major alarm input.

Attribute
Parameters
None.

When this alarm occurs, the status of the external device that connects to the major alarm input
port will change.
Possible Causes
l The status of the major alarm input has changed.
l The RELAY_ALARM_MAJOR alarm is a default setting for the alarm inputs on the board.
As a result, the alarm is reported by default.
Procedure
----End
Related Information
None.
4.135 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MAJOR is an alarm indicating a minor alarm input.
Attribute
Parameters
None.


When this alarm occurs, the status of the external device that connects to the minor alarm input
port will change.
Possible Causes
l The status of the minor alarm input has changed.
l The RELAY_ALARM_MINOR alarm is a default setting for the alarm inputs on the board.
As a result, the alarm is reported by default.
Procedure
----End
Related Information
None.
4.136 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the real time clock (RTC) fails on the SCC board.
Attribute
Parameters
None.

When this alarm occurs, the system is in soft timing mode, and the time-scale has low precision.
Possible Causes
l The RTC chip is damaged.
l The board temperature is above the upper threshold.

Procedure
Step 1 Check whether the board temperature is within the normal range. If not, replace the fan. Then,
Step 2 If the alarm persists, replace the SCC board.
----End
Related Information
The RTC records time for NEs.
4.137 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that a switchover has occurred on the clock
source in S1 byte mode.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the serial number of the priority table.

l 0x01: priority table for the system clock
l 0x02: priority table for the first 2M phase-locked source
l 0x03: priority table for the second 2M phase-locked source

When this alarm occurs, user services are affected.
Possible Causes
l The optical fiber is cut.

l The external BITS is interrupted.

l The S1_SYN_CHANG occurs on the upstream NE.
Procedure
Step 1 Check whether a fiber cut occurs or the line board reports the R_LOS alarm. If yes, properly
connect the optical fiber and clear the R_LOS alarm. Then, check whether the
S1_SYN_CHANGE alarm is cleared.
Step 2 If the fiber is properly connected, check whether the external BITS is interrupted.
1. Check whether the input cable of the external BITS is damaged. If yes, replace the faulty
cable. Then, check whether the S1_SYN_CHANGE alarm is cleared.
2. Properly connect the 2 Mbit/s cable for inputting the external clock to the subrack panel.
Then, check whether the S1_SYN_CHANGE alarm is cleared.
3. Check whether the 2 Mbit/s cable interface for inputting the external clock is faulty. If yes,
replace the related interface board. Then, check whether the S1_SYN_CHANGE alarm is
cleared.
Step 3 If the S1_SYN_CHANGE alarm persists, check whether the S1_SYN_CHANGE alarm occurs
on the upstream NE. Repeat steps 1 and 2 to check the upstream NE. After the upstream
S1_SYN_CHANGE alarm is cleared, the local S1_SYN_CHANGE alarm will be automatically
cleared.
----End
Related Information
None.
4.138 SECU_ALM
Description
The SECU_ALM is an alarm indicating an NE login failure. This alarm is reported when an
unauthorized user attempts to log in to an NE after four attempt failures.
Attribute
Parameters
None.

This alarm is automatically cleared and does not affect the system.

Possible Causes
l An unauthorized user has attempted to log in to the NE, and a message is displayed
indicating that the user name does not exist or the password is incorrect.
Procedure
Step 1 Check whether an unauthorized user has attempted to log in to the NE. If yes, lock the
unauthorized user account.
----End
Related Information
None.
4.139 SERVICE_CAPACITY_EXCEED_LICENSE
Description
The SERVICE_CAPACITY_EXCEED_LICENSE is an alarm indicating that the capacity of
the services configured for a subrack exceeds the limit defined by the license.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of the license-threshold-crossing subrack.

When this alarm occurs, the existing services and the system are not affected but the alarm-
related services cannot be configured on the alarm-reporting subrack.
Possible Causes
The capacity of the services configured for the subrack exceeds the limit defined by the license.

Procedure
Step 1 On the NMS, check whether the capacity of the services configured for the subrack exceeds the
limit defined by the license according alarm parameters. If yes, select an appropriate license to
meet service requirements of the subrack.
Step 2 If an appropriate license is unavailable, purchase one from Huawei.
----End
Related Information
None.
4.140 SERVICE_TYPE_EXCEED_LICENSE
Description
The SERVICE_TYPE_EXCEED_LICENSE is an alarm indicating that the types of the services
configured for a subrack exceed the limit defined by the license.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of the license-threshold-crossing subrack.

Possible Causes
The types of the services configured for the subrack exceeds the limit defined by the license.
Procedure
Step 1 On the NMS, check whether the services configured for the subrack exceeds the limit defined
by the license according alarm parameters. If yes, select an appropriate license.
Step 2 If an appropriate license is unavailable, purchase one from Huawei.
----End

Related Information
None.
4.141 SHELF_AREA_POWER_OVER
Description
The SHELF_AREA_POWER_OVER is an alarm indicating that the nominal power
consumption of an NE subrack section exceeds the threshold. This alarm is reported when the
total nominal power consumption of the boards in the subrack section is greater or equal to the
threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the subrack.
Parameter 2 Indicates the ID of the subrack section.

When this alarm occurs, the system is in a high-risk state. As a result, the subrack may be powered
off.
Possible Causes
The total nominal power consumption of the boards in the subrack section is greater or equal to
the threshold.
Procedure
Step 1 Remove the redundant boards from the subrack until the alarm is cleared.
----End

Related Information
None.
4.142 SLAVE_WORKING
Description
The SLAVE_WORKING is an alarm indicating that the standby board is working. This alarm
is reported when the service bus of the service board selects the standby cross-connect board
and the slave clock is selected as the system clock.
Attribute
Parameters
None.

Possible Causes
l The active cross-connect board is not detected.
l The active cross-connect board is faulty.
l The service board is faulty.
Procedure
Step 2 Properly install the active cross-connect board. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the active cross-connect board. Then, check whether the alarm is
cleared.
Step 4 Perform a cold reset on the alarm-reporting service board on the NMS, or directly remove and
insert this board. Then, check whether the alarm is cleared.
----End
Related Information
The active cross-connect board is installed in the slot with a smaller ID,

and the standby board is installed in the slot with a greater ID.
4.143 SM_BDI
Description
The SM_BDI is an alarm indicating a backward defect in SM overheads at the optical transponder
unit (ODU) layer. This alarm is reported when major alarms occur at the remote OTU and upper
layers.
Attribute
Parameters
None.

This alarm occurs only on the OTU termination NE of services in the transmit direction, which
does not affect services in the receive direction.
Possible Causes
l Alarms occur on the remote OTU termination NE.
Procedure
Step 1 Check whether severer alarms occur on the remote OTU termination NE. If yes, clear the alarms
according to the related alarm-handling methods. Then, check whether the SM_BDI alarm is
cleared.
Step 2 If alarms at the remote end persist, perform an inloop on the local optical ports to check for
alarms. If any alarms occur, correct configurations according to the alarms.
CAUTION
Step 3 If the SM_BDI alarm persists, replace the local board.

Step 4 If the alarms at the remote end persist and the inloop test detects no abnormities on the local
----End
Related Information
None.
4.144 SM_BEI
Description
The SM_BEI is an alarm indicating a backward error in PM overheads at the optical transponder
unit (OTU) layer. This alarm is reported when SM-BIP check bit errors occur at the remote end.
Attribute
Parameters
None.

When this alarm occurs, SM_BIP check bit errors occur on the remote OTU termination NE,
which does not affect the FEC function and performance on the local NE.
Possible Causes
l Bit errors occur on the remote OTU termination NE.
Procedure
Step 1 Check board performance on the remote OTU termination NE and clear the remote bit errors.
----End
Related Information
None.

4.145 SM_BIP8_OVER
Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the SM section at
the optical transponder unit (OTU) layer exceeds the threshold.
Attribute
Major Service alarm
Parameters
None.

Possible Causes
Procedure
Step 1 On the NMS, check whether severer alarms occur, for example, the R_LOS and R_LOF alarms.
Clear these alarms first and check whether the SM_BIP8_OVER alarm is cleared.
Step 3 Clean the local pigtail connector and the receive optical port on the line board. Then, check
Step 5 Check whether the peer transmit optical power is within the normal range. If not, replace the
line board.

----End
Related Information
None.
4.146 SM_BIP8_SD
Description
The SM_BIP8_SD is an alarm indicating that the signals degrade in the PM section at the optical
transponder unit (OTU) layer.
Attribute
Major Service alarm
Parameters
None.

Possible Causes

Procedure
Step 1 On the NMS, check whether severer alarms occur, for example, the R_LOS and R_LOF alarms.
Clear these alarms first and check whether the SM_BIP8_SD alarm is cleared.
Step 3 Clean the local pigtail connector and the receive optical port on the line board. Then, check
Step 5 Check whether the peer transmit optical power is within the normal range. If not, replace the
line board.
----End
Related Information
None.
4.147 SM_IAE
Description
The SM_IAE is an alarm indicating an incoming alignment error (IAE) in the SM section at the
optical transponder layer (OTU). When the ODU frame is synchronously mapped into the OTU
frame, the IAE flag is set to true if a frame alignment error occurs. This alarm is reported when
the sink NE detects the IAE which indicates subframe alignment bit errors occur in the received
services.

Attribute
Parameters
None.

When this alarm occurs, services may be unavailable.
Possible Causes
l A clock jitter event occurs in the transmit unit on the remote NE (the source of the OTU/
ODU adaption function).
l The frame offset on the termination side of the remote NE (the source of the OTU/ODU
adaption function).
l The FEC processing chip on the remote NE (the source of the OTU/ODU adaption
function).
Procedure
Step 1 Adjust the frame offset on the board system side of the remote NE (the source of the OTU/ODU
adaption function). Then, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the board on the remote NE (the source of the OTU/ODU adaption
function).
----End
Related Information
None.
4.148 SM_TIM
Description
The SM_TIM is an alarm indicating a trail trace identifier (TTI) mismatch in the PM overheads
at the optical transponder unit (ODU) layer.
Attribute

Parameters
None.

When this alarm occurs, the FEC function and services are not affected.
Possible Causes
l The SM_TTI byte expected by the local NE is incorrectly set.
l The SM_TTI byte transmitted by the remote NE is incorrectly set.
l The fiber is improperly connected.
Procedure
Step 1 Determine the expected setting of the SM_TTI byte based on actual situations.
Step 2 Check whether the SM_TTI byte expected by the board is consistent with the received SM_TTI
byte. If the settings of the expected SM_TTI byte are incorrect, modify the setting.
Step 3 If the received SM_TTI byte is incorrect, verify that the fiber connection on the local optical
port is correct.
Step 4 Verify that the setting of the SM_TTI byte transmitted in the upstream services is correct.
----End
Related Information
None.
4.149 SNCP_FAIL
Description
The SNCP_FAIL is an alarm indicating a subnetwork connection protection (SNCP) switchover
failure.
Attribute
Parameters

Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the protection group.

When this alarm occurs, the services that are configured with SNCP are unprotected and
interrupted.
Possible Causes
Service scheduling has failed during the SNCP switchover.
Procedure
Step 1 Reset the SCC board and recalculate all services.
----End
Related Information
None.
4.150 SO_SK_MISMATCH
Description
The SO_SK_MISMATCH is an alarm indicating that the number of timeslots is different on the
source and sink of the link capacity adjustment scheme (LCAS). This alarm is reported when
the number of upstream (or downstream) timeslots configured for the local VCTRUNK port is
inconsistent with that of downstream (or upstream) timeslots configured for the peer VCTRUNK
port.
Attribute
Parameters
None.

When the alarm occurs, services are not affected.

CAUTION
After this alarm occurs, the intermediate timeslots deleted from the sink are added to other
VCTRUNK ports. As a result, services on the VCTRUNK ports are interrupted. Make the
number of timeslots consistent between the source and sink before you proceed.
Possible Causes
The number of timeslots is different on the source and sink of the LCAS.
NOTE
If an intermediate timeslot is deleted from the sink but the corresponding timeslot is not deleted from the
source, this alarm is reported.
If the last timeslot is deleted from the sink, but the corresponding timeslot is not deleted from the source,
this alarm is not reported.
Procedure
Step 1 View the alarm on the NMS and determine the serial number of the VCTRUNK port.
Step 2 On the NMS, check whether the number of upstream (or downstream) timeslots configured for
the local VCTRUNK port is consistent with that of downstream (or upstream) timeslots
configured for the peer VCTRUNK port. If not, add or delete timeslots based on actual
requirements to make the number of timeslots consistent. Then, check whether the alarm is
cleared.
----End
Related Information
None.
4.151 STORM_CUR_QUENUM_OVER
Description
The STORM_CUR_QUENUM_OVER is an alarm indicating an alarm storm. This alarm is
reported when the alarm queue is congested, indicating that the alarm module is in the storm
state. As a result, some alarms on the SCC board may be lost.
Attribute
Minor Alarm
Parameters
None.


When this alarm occurs, the alarm queue is congested. As a result, some alarms may be lost so
that the alarm status of NEs cannot be obtained.
Possible Causes
The number of alarms exceeds the specified value, and the queue cannot contain all alarms.
Procedure
Step 1 Clear the alarms (excluding the STORM_CUR_QUENUM_OVER alarm) until the alarm storm
ends.
----End
Related Information
None.
4.152 SUBRACK_ID_CONFLICT
Description
The SUBRACK_ID_CONFLICT is an alarm indicating a subrack ID conflict.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the conflicting subrack ID.

When this alarm occurs, communications between subracks are abnormal. As a result,
commands cannot be correctly issued to subracks, and the board is unreachable.
Possible Causes
The subracks are set up in master/slave mode, and NE software of the SCC board in the master
subrack detects double subrack ID DIPs.

Procedure
Step 1 Re-set the DIP for subrack IDs.
Step 2 Warm reset all boards in the subrack whose ID is changed. Then, check whether the alarm is
cleared.
----End
Related Information
None.
4.153 SUBRACK_ID_MISMATCH
Description
The SUBRACK_ID_MISMATCH is an alarm indicating a subrack ID mismatch.
Attribute
Parameters
None.

When this alarm occurs, the subrack ID DIP on the hardware mismatches the subrack ID saved
on the software. As a result, communications between boards are abnormal.
Possible Causes
The subrack ID DIP on the hardware has changed so that the NE and board software detects that
the detected subrack ID mismatches the actual subrack ID.
Procedure
Step 1 Re-set the subrack ID DIP, or power off and then restart the subrack.
----End
Related Information
None.

4.154 SUBRACK_LOOP
Description
The SUBRACK_LOOP is an alarm indicating that subracks are connected in a closed-loop ring.
Attribute
Parameters
None.

When this alarm occurs, a network storm occurs. As a result, communications between subracks
are interrupted.
Possible Causes
In master/slave mode, a closed-loop occurs on the inner network ports between subracks.
Procedure
Step 1 Verify that all subracks are connected in a chain.
----End
Related Information
None.
4.155 SUBRACK_TYPE_MISMATCH
Description
The SUBRACK_TYPE_MISMATCH is an alarm indicating a subrack type mismatch.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the subrack ID that is inconsistent with the actual subrack ID.

Possible Causes
The logical subrack type is configured differently from the physical subrack type.
Procedure
Step 1 Delete the incorrectly configured subrack, or reconfigure a logical subrack which has the same
type with the physical subrack.
----End
Related Information
None.
4.156 SUM_INPWR_HI
Description
The SUM_INPWR_HI is an alarm indicating that the combined input optical power exceeds the
upper threshold.
Attribute
Parameters
None.


When this alarm occurs, the optical modules on the local and downstream boards may be
damaged. As a result, bit errors occur in the services, and the services may be interrupted.
Possible Causes
l The output optical power of the upstream board is within the normal range. The input optical
power of the local board exceeds the upper threshold, and an optical attenuator is not added
to prevent threshold-crossing.
l The output optical power of the local or upstream board is above the upper threshold.
l The local board is faulty.
Procedure
Step 1 Use an optical power meter to measure the input optical power on the local receive optical
interface and check whether the input optical power is within the normal range. If the input
optical power is above the upper threshold, add an optical attenuator to decrease the optical
power. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the output optical power of the upstream boards is within
the normal range on the NMS. If the output optical power is above the upper threshold, check
whether the input and output optical power on each upstream NE is within the normal range.
If... Then...
The input and output optical power on Adjust the input optical power of these NEs.
upstream NEs is out of range
The input optical power on upstream NEs is The upstream boards may be faulty. Replace
within the normal range the faulty boards.
Step 3 Check whether the alarm is cleared. If the alarm persists, replace the local faulty board.
----End
Related Information
None.
4.157 SUM_INPWR_LOW
Description
The SUM_INPWR_LOW is an alarm indicating that the combined input optical power is below
the lower threshold.

Attribute
Parameters
None.

When this alarm occurs, the output single-channel optical signals on the board are lost. As a
result, bit errors occur in the services, and the services may be interrupted.
Possible Causes
l The output optical power on the upstream NE decreases so that the input optical power on
the local NE is below the lower threshold.
l The signal attenuation on the line is greater than the acceptable value, or the pigtail, fiber
connector, or optical attenuator is contaminated or damaged.
Procedure
Step 1 On the NMS, check in sequence whether the output optical power of the upstream boards is
within the normal range along the service flow. If the output optical power is below the lower
threshold, adjust the output optical power. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, check the optical cable on the line. If the signal attenuation on the optical
cable is greater than the acceptable value, adjust the attenuator or replace the optical cable. Then,
----End
Related Information
None.
4.158 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating an activation timeout. This alarm
is reported when the commit operation is not performed after the board has been activated for a
certain period.

Attribute
Parameters
None.

Possible Causes
During the software package loading, the commit operation is not performed after the board has
been activated for a certain period.
Procedure
Step 1 On the NMS, select a correct software package and perform the commit operation.
----End
Related Information
None.
4.159 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic matching function
on an NE is disabled.
Attribute
Parameters
None.


When this alarm occurs, the SCC board cannot automatically upgrade the software on a newly
installed board, which may cause software version mismatch on the newly installed board and
the SCC board. As a result, the board may function improperly.
Possible Causes
The automatic matching function is disabled.
Procedure
Step 1 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
The automatic matching function allows the SCC board to automatically upgrade the software
on the newly installed board after the system detects a software version mismatch on a newly
installed board and the NE.
4.160 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm indicating a software version mismatch. After
an NE is powered off and then recovers or the SCC board is replaced or reset, the system checks
software version matching for all boards and the SCC board. This alarm is reported if the software
version of a board does not match that of the SCC board.
Attribute
Parameters
None.

l When this alarm occurs, the automatic matching function for software package loading is
disabled.
l Software version mismatch on the NE and boards may affect some functions of the NE.

Possible Causes
l After the NE is powered off, a board is installed and its software version does not match
the NE software version.
l The SCC board is replaced but its software version does not match the board software
version after the replacement.
Procedure
Step 1 On the NMS, reload the software package.
----End
Related Information
None.
4.161 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating that the commit operation on an NE fails.
This alarm is reported when the commit operation fails during software package loading on the
NE.
Attribute
Parameters
None.

When this alarm occurs, the commit operation on a board fails. As a result, software version
upgrade will fail.
Possible Causes
When the commit operation is performed during software package loading, the double-area
board fails to copy the new software from an area to another.
NOTE
A double-area board has two file systems that back up data for each other. In most cases, each file is saved
in both areas.

Procedure
Step 1 On the NMS, reload the original software package.
----End
Related Information
None.
4.162 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that software package loading is in progress
on an NE. This alarm is cleared after the commit operation on the NE is completed.
Attribute
Warning Processing alarm
Parameters
None.

When this alarm occurs, the backup function on the active and standby SCC boards will be
disabled.
Possible Causes
The NE is loading the software package.
Procedure
Step 1 Wait until software package loading is completed. The alarm will then be automatically cleared.
----End
Related Information
None.

4.163 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that a file is lost. The NE detects a file loss
on an area of the software package on the SCC board when performing a preventive maintenance.
This alarm is reported if the file cannot recover using the related file backed up in the other area.
This alarm is cleared if the NE detects no file loss during next preventive maintenance.
Attribute
Parameters
None.

When this alarm occurs, some functions of the NE are affected.
Possible Causes
A file in the software package on the SCC board is lost and cannot recover.
Procedure
----End
Related Information
A preventive maintenance is performed during board startup and periodical check. The
periodical check is performed every 1 hour by default.
4.164 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that the software on a board is not
included in the customized software package. This alarm is reported when the software on a
newly installed board is not included in the customized software package after the NE loads the
customized software package. As a result, the automatic matching function on the board is
unavailable.

Attribute
Parameters
None.

When this alarm occurs, some functions of the NE may be affected.
Possible Causes
A user has used a customized software package which does not include software information
about a non-customized board.
Procedure
Step 1 On the NMS, select a correct software package and load it.
----End
Related Information
A customized software package indicates that a user has customized the contents of a software
package based on actual requirements.
4.165 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the software
package version fails. This alarm is reported when the software version information described
in the description file (similar to a file list) in the software package is inconsistent with the actual
software version information.
Attribute
Parameters
None.


When this alarm occurs, the software versions on the NE are inconsistent with those described
in the description file. As a result, some functions of the NE may be affected.
Possible Causes
The software package contains a file error, resulting in software version information mismatch.
Procedure
Step 1 On the NMS, select a correct software package and load it.
----End
Related Information
None.
4.166 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating an NE rollback failure. This alarm is
reported when a board rollback fails during NE rollback.
Attribute
Parameters
None.

When this alarm occurs, the board software cannot be rolled back to the version before the
software package is loaded. As a result, the software version of the board may not match that of
the NE, which affects some functions of the NE.
Possible Causes
Some boards have failed to be rolled back to the original version during NE rollback.
Procedure
----End

Related Information
None.
4.167 SYNC_DISABLE
Description
The SYNC_DISABLE is an alarm indicating that the automatic synchronization function of the
SCC board is disabled. This alarm is reported when the automatic synchronization status of the
SCC board changes to disabled. As a result, data cannot be backed up in batches.
Attribute
Parameters
None.

Data is inconsistent between the active and standby SCC boards.
Possible Causes
The automatic synchronization status of the SCC board changes from enabled to disabled.
Procedure
Step 1 Enable the automatic synchronization function on the SCC board, and the alarm will be cleared.
----End
Related Information
None.
4.168 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH is an alarm indicating that a clock source is in the manual or forced
switching state.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for the clock source that is in the manual or forced
switching state.
Parameter 2 Indicates the slot ID for the clock source that is in the manual or forced switching
state. The value is permanently set to 0xF0 for an external clock source.
Parameter 4 Indicates the port ID for a service board clock source that is in the manual or
forced switching state;
indicates which external clock source is lost.
l 0x01: The channel-1 external clock source is lost.
l 0x02: The channel-2 external clock source is lost.
Parameter 5 Indicates the serial number of the priority table.

l 0x01: priority table for the system clock
l 0x02: priority table for the first 2M phase-locked source
l 0x03: priority table for the second 2M phase-locked source

When this alarm occurs, the NE clock works in the manual or forced switching state, which does
not affect services.
Possible Causes
A manual or forced switching command is issued for the clock source.
Procedure
Step 1 View the alarm on the NMS and determine the related clock source according to alarm
parameters.

Step 2 Clear the manual or forced switching state for the clock source, and the alarm will be
automatically cleared.
----End
Related Information
None.
4.169 SYNC_FAIL
Description
The SYNC_FAIL is an alarm indicating that data has failed to be backed up in batches on the
active and standby SCC boards.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the cause of the alarm.

l 0x31: Backing up the database fails.
l 0x32: Software version verification on the active and standby SCC boards
fails.
l 0x33: The communication between the active and standby SCC boards fails.

When this alarm occurs, data cannot be bulk backed up, and the active/standby switchover
function is unavailable.
Possible Causes
l Backing up the database fails.
l The software version is inconsistent between the active and standby SCC boards.
l Communications on the standby SCC board are unstable or interrupted.
Procedure
Step 1 Wait until the next backup is completed. Then, check whether the alarm is cleared.

Step 2 If the alarm persists, check whether the software version is consistent between the active and
standby SCC boards. If not, upgrade the software version on the active or standby SCC board.
----End
Related Information
None.
4.170 SYN_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating a clock source lockout.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for the locked clock source.
Parameter 2 Indicates the slot ID for the locked clock source. The value is permanently set to
0xF0 for an external clock source.
Parameter 4 Indicates the port ID for a locked service board clock source;
indicates which channel of external clock source is locked.
l 0x01: The channel-1 external clock source is locked.
l 0x02: The channel-2 external clock source is locked.

When this alarm occurs, the clock source is locked and cannot serve as the tracing source for
the NE, which does affect services.

Possible Causes
A lockout command is issued for the clock source.
Procedure
Step 1 View the alarm on the NMS and determine the related clock source according to alarm
parameters.
Step 2 Clear the lockout state for the clock source, and the alarm will be automatically cleared.
----End
Related Information
None.
4.171 SYSPARA_CFDB_NOSAME
Description
The SYSPARA_CFDB_NOSAME is an alarm indicating that data is inconsistent between the
system parameter area and the CF card. When data on the SCC board is backed up to the CF
card the first time, the system checks data consistency between the SCC board and the CF card.
l If data is inconsistent, the system does not periodically back up data and reports the
SYSPARA_CFDB_NOSAME alarm.
l If data is consistent, the system enables the periodical backup function.
Attribute
Parameters
None.

When this alarm occurs, data is inconsistent between the system parameter area and the CF card.
As a result, the data cannot be restored from the CF card.
Possible Causes
When data is backed up the first time, data is inconsistent between the SCC board and the CF
card.

Procedure
Step 1 The NE database will be automatically backed up to the CF card in the next backup period. Then,
----End
Related Information
None.
4.172 T_LOSEX
Description
The T_LOSEX is an alarm indicating a signal loss in the service bus of the backplane. This alarm
is reported when the board detects that the service bus of the backplane is in the LOS state.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the selected cross-connect board.

l 0x01: the cross-connect board with a smaller slot ID
l 0x02: the cross-connect board with a greater slot ID
Parameter 2, Parameter 3 Each bit indicates status of a backplane bus. If the value of bit[0]
is 1, the first bus is faulty.

When this alarm occurs, all services on the board are interrupted. As a result, the board cannot
work properly.
Possible Causes
l The service board is installed improperly.

l The cross-connect board is installed improperly.

l The clock source for the active and standby cross-connect boards is faulty or has poor
quality.
Procedure
Step 2 Verify that the alarm-reporting board is installed properly. Then, check whether the alarm is
Step 3 Verify that the cross-connect board is installed properly. Then, check whether the alarm is
Step 4 Replace the cross-connect board. Then, check whether the alarm is cleared. If the alarm persists,
go to the next step.
Step 5 Replace the alarm-reporting board.
----End
Related Information
None.
4.173 TD
Description
The TD is an alarm indicating that the transmission quality of a laser deteriorates. This alarm is
reported when a board detects that the output optical power or bias current of the laser exceeds
the threshold of a deterioration alarm.
Attribute
Parameters

Name Meaning
Parameters 1 and 2 Indicates the serial number of the pump laser.

l 0x01: The output optical power exceeds the threshold.
l 0x02: The bias current exceeds the threshold.
If the value is 0xFF, the parameter is meaningless.
Parameter 3 l 0x01: The operating temperature of the board is above the upper
threshold.
l 0x02: The operating temperature of the board is below the lower
threshold.

When this alarm occurs, the laser of the board may function improperly, the transmission quality
of the laser is poor, bit errors occur, and services may be interrupted.
Possible Causes
The laser is deteriorating.
Procedure
Step 1 Replace the optical module if it is pluggable on the board. Replace the board if the optical module
is unpluggable.
----End
Related Information
None.
4.174 TEM_HA
Description
The TEM_HA is an alarm indicating that the temperature of a laser exceeds the upper threshold.
Attribute
Parameters
None.


When this alarm occurs, the working wavelength of the optical module is affected. As a result,
user services are affected.
Possible Causes
l The temperature of the board is above the upper threshold.
l The module performance detection circuit is faulty.
Procedure
Step 1 Check the ambient temperature of the board and the ventilation in the equipment room. If the
ambient temperature of the board is above the upper threshold, use cooler equipment, such as
an air conditioner, to decrease the temperature.
----End
Related Information
None.
4.175 TEM_LA
Description
The TEM_LA is an alarm indicating that the temperature of a laser is below the lower threshold.
Attribute
Parameters
None.

When this alarm occurs, the working wavelength of the optical module is affected. As a result,
user services are affected.
Possible Causes
l The temperature of the board is below the lower threshold.

l The module performance detection circuit is faulty.
Procedure
Step 1 Check the ambient temperature of the board. If the temperature is below the lower threshold,
increase the temperature. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.176 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that a board is being tested.
Attribute
Warning Processing alarm
Parameters
None.

When this alarm occurs, a test command may affect the system.
Possible Causes
A user has issued a command for the board to switch to the test state.
Procedure
Step 2 The alarm is automatically cleared after a command is issued to end the test. However, the system
is affected. Cold resetting the board can prevent the impact on the system.
----End
Related Information
None.

4.177 TF
Description
The TF is an alarm indicating a laser transmission failure. This alarm is reported when the
transmit optical power of the laser exceeds the threshold.
Attribute
Parameters
None.

Possible Causes
The laser optical module is damaged or the laser is deteriorating.
Procedure
Step 1 Replace the optical module if it is pluggable on the board. Replace the board if the optical module
is unpluggable.
----End
Related Information
None.
4.178 THUNDERALM
Description
The THUNDERALM is an alarm indicating a surge protection failure. This alarm is reported
when the surge protection circuit for the power interface unit (PIU) board fails.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the power unit that is faulty.

l 0x00: all units
l 0x01: the first PIU board
l 0x02: the second PIU board

When this alarm occurs, the surge protection of the system is weakened. As a result, if the
equipment is attacked by a lightning strike, services may be interrupted due to board failure.
Possible Causes
l The equipment has been attacked by a strong lightning strike with a common-mode current
greater than 5000 A and a differential-mode current greater than 3000 A. As a result, the
surge protection components on the PIU board fail so that the fuse encounters an open
circuit for protection.
Procedure
Step 1 Replace the faulty PIU board.
----End
Related Information
The electromagnetic field generated by thunderstorms may cause damage to the electronic parts.
Properly ground the equipment to prevent lightning strikes.

4.179 TIME_LOS
Description
The TIME_LOS is an alarm indicating that the time source is unavailable. This alarm is reported
when the high-precision time function is enabled but no time source exists.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID for the service board time source.
Parameter 2 Indicates the slot ID for the service board time source.
Parameter 4 Indicates the port ID for the service board time source.

When this alarm occurs, the upstream and downstream time of an NE cannot be synchronized
with each other. As a result, the service quality is affected.
Possible Causes
l The fiber is faulty or is connected incorrectly.

l The fiber connector is dirty.
l The board is offline or faulty.

Procedure
Step 1 Check whether alarms such as R_LOS and R_LOF are generated on the optical port of the board.
If any alarms are generated, clear them first. Then, check whether the TIME_LOS alarm is
cleared.
Step 2 If the TIME_LOS alarm persists, check whether the fiber connector is dirty. If the fiber connector
is dirty, clean it. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the transmission cable is damaged or pressed. If yes, replace
the transmission cable. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the board is properly installed on the NMS.
l If the board is not installed properly, install the board properly. Then, check whether the
alarm is cleared.
l If the board is installed properly but is offline, warm reset the board. Then, check whether
the alarm is cleared. If the alarm persists, cold reset the board and check whether the alarm
is cleared.
Step 5 If the alarm persists, replace the board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.180 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the high-precision time of a board
is in the non-locked state. This alarm is reported when the high-precision time function on the
board is enabled and the current tracing source of the board is the internal time source.
Attribute
Parameters
None.

When this alarm occurs, the upstream and downstream time of an NE cannot be synchronized
with each other. As a result, the service quality is affected.

Possible Causes
l The time source priority table is not configured with the external time source.
l The corresponding time source cannot be traced because the value of the announce attribute
of the local NE is smaller than that of the upstream NE.
l The time source priority table is configured but the internal time source is still traced. It
indicates that other time sources do not meet the tracing conditions due to some faults, for
example, the fiber is improperly connected, or the board is offline.
Procedure
Step 1 Check whether the time source priority table is configured with an external clock source. If not,
configure an external clock source in the time source priority table. Then, check whether the
alarm is cleared.
Step 2 If the alarm persists, view the announce attribute of the NE on the NMS. If the value of the
announce attribute on the NE is smaller than that on the external time source, use either of the
following methods to change the value of the announce attribute on the NE:
l Change the value of the announce attribute on the local NE so that it is greater than that on
the upstream NE. Then, check whether the alarm is cleared.
l Change the value of the announce attribute of the upstream NE so that it is smaller than
that on the local NE. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, verify that the fiber connector is connected properly and is clean. Then,
Step 4 If the alarm persists, check whether the board is properly installed on the NMS.
l If the board is installed improperly, properly install the board. Then, check whether the
alarm is cleared.
l If the board is installed properly but is offline, warm reset the board. Then, check whether
the alarm is cleared. If the alarm persists, cold reset the board and check whether the alarm
is cleared.
Step 5 If the alarm persists, replace the board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.181 TR_LOC
Description
The TR_LOC is an alarm indicating a transmit reference clock loss.

Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: indicates the transmit clock fails on the clock board with a smaller slot
ID.
l 0x02: indicates that the transmit clock fails on the clock board with a greater
slot ID.
l 0x03: indicates that the transmit clock fails on the active and standby clock
boards.
If the slot ID contains two bytes, the options for parameter 1 are as follows:
l bit[0]: indicates that the clock is lost on the cross-connect board with a smaller
slot ID.
l bit[1]: indicates that the frame header is lost on the cross-connect board with
a smaller slot ID.
l bit[2]: indicates that the cross-connect board with a smaller slot ID fails.
l bit[3]: indicates that the clock is lost on the cross-connect board with a greater
slot ID.
l bit[4]: indicates that the frame header is lost on the cross-connect board with
a greater slot ID.
l bit[5]: indicates that the cross-connect board with a greater slot ID fails.
Parameter 2 l 0x01: indicates that the clock is lost on the cross-connect board with a smaller
slot ID.
l 0x02: indicates that the frame header is lost on the cross-connect board with
a smaller slot ID.
l 0x04: indicates that the bus is faulty on the cross-connect board with a smaller
slot ID.
l 0x08: indicates that the clock is lost on the cross-connect board with a greater
slot ID.
l 0x10: indicates that the frame header is lost on the cross-connect board with
a greater slot ID.
l 0x20: indicates that the bus is faulty on the cross-connect board with a greater
slot ID.


When this alarm occurs, the board functions improperly. Services will not be affected if the
standby cross-connect board is faulty. Services will be transiently interrupted during the active/
standby switchover if the active cross-connect board is faulty.
Possible Causes
l The clock bus on the cross-connect board is faulty.
l The clock board is not installed or is faulty.
l The local board has hardware faults.
Procedure
Step 1 Verify that the clock board is installed. Then, go to the next step.
Step 2 Check clock-board-related alarms and determine the working status of the clock board.
l If the clock board reports an alarm, clear the alarm first.
l If the clock board does not report an alarm, the board that reports the TR_LOC alarm is
faulty. Cold reset or replace the board.
----End
Related Information
None.
4.182 TU_AIS_VC3
Description
The TU_AIS_VC3 is an alarm indicating an alarm indication signal (AIS) for a lower order
VC-3 TU channel. This alarm is reported when the board detects signals in the TU channel are
all "1"s.
Attribute
Parameters
None.

When this alarm occurs, VC-3 path services are interrupted.

Possible Causes
l Severer alarms, such as R_LOS, R_LOF, or AU_AIS, occur in the system.
l The peer related channel is faulty.
Procedure
Step 1 On the NMS, check for severer alarms, such as R_LOS, R_LOF, HP_SLM, and AU_AIS. Clear
these alarms first and check whether the TU_AIS_VC3 alarm is cleared.
Step 2 Cold reset the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
CAUTION
Step 3 Replace the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
Step 4 Check whether the cross-connect board is faulty. If yes, replace the cross-connect board. Then,
Step 5 Check whether the peer board is faulty. If yes, replace the faulty board. Then, check whether
----End
Related Information
None.
4.183 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating a pointer loss in the lower order VC-3 TU channel.
This alarm is reported when a board detects that the TU-PTR value is invalid or NDF reverses
in eight consecutive frames.
Attribute
Parameters
None.


When this alarm occurs, VC-3 path services are interrupted.
Possible Causes
l Severer alarms, such as R_LOS, R_LOF, or AU_AIS, occur in the system.
l The peer related channel is faulty.
Procedure
Step 1 On the NMS, check for severer alarms, such as R_LOS, R_LOF, and AU_AIS. Clear these
alarms first and check whether the TU_LOP_VC3 alarm is cleared.
Step 2 Cold reset the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
CAUTION
Step 3 Replace the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
Step 4 Check whether the cross-connect board is faulty. If yes, replace the cross-connect board. Then,
Step 5 Check whether the peer board is faulty. If yes, replace the faulty board. Then, check whether
----End
Related Information
None.
4.184 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating that the delay of a multiframe times out. This alarm is
reported when the delay between the timeslots bound with a VCTRUNK port exceeds the
acceptable time of the virtual concatenation.

Attribute
Parameters
None.

When this alarm occurs, aligning the virtual concatenation delay times out during service data
transmission. As a result, the timeslots cannot form a data frame, and packet loss occur in the
services.
Possible Causes
The actual SDH network delay exceeds the limit of the virtual concatenation delay
compensation.
Procedure
Step 1 View the alarm on the NMS and determine the VCTRUNK port ID of the alarm-reporting board
according parameters 2 and 3.
Step 2 Reconfigure the timeslots of the VCTRUNK port so that they traverse the same fiber. If they
need to traverse different fibers, ensure that the distance difference of the fibers is the smallest.
----End
Related Information
ITU-T G.709
4.185 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating that a virtual concatenation multiframe loss in
the VC-3 channel. This alarm is reported when the system detects that the multiframe indicator
(MFI) field is incorrect in the H4 byte of the VC-3 timeslot.
Attribute

Parameters
None.

l When this alarm occurs during data transmission, services will be transiently interrupted
due to an automatic switchover performed by the link capacity adjustment scheme (LCAS).
l If the LCAS is disabled, the services are interrupted.
Possible Causes
l Bit error alarms, such as B3_EXC and B3_SD, occur on the line.
l The virtual concatenation delay times out.
l The MFI field in the K4 byte transmitted by the peer end is incorrect.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the VCAT_LOM_VC3 alarm.
Step 2 On the NMS, check whether bit error alarms, such as B3_EXC_VC3 and B3_SD_VC3, are
reported on the board. If yes, clear them first and check whether the VCAT_LOM_VC3 alarm
is cleared.
Step 3 On the NMS, check whether the VCAT_LOA alarm is reported on the board. If yes, the virtual
concatenation delay times out. See the method of handling the VCAT_LOA alarm to clear it.
Then, check whether the VCAT_LOM_VC3 alarm is cleared.
Step 4 If the alarm persists, check whether the board is faulty. If yes, replace the faulty board. Then,
Step 5 If the alarm persists, the MFI domain transmitted from the peer SDH NE is incorrect. Replace
the peer related board and check whether the alarm is cleared.
----End
Related Information
None.
4.186 VCAT_LOM_VC4
Description
The VCAT_LOM_VC4 is an alarm indicating that a virtual concatenation multiframe loss in
the VC-4 channel. This alarm is reported when the system detects that the multiframe indicator
(MFI) field is incorrect in the H4 byte of the VC-4 timeslot.

Attribute
Parameters
None.

l When this alarm occurs during data transmission, services will be transiently interrupted
due to an automatic switchover performed by the link capacity adjustment scheme (LCAS).
l If the LCAS is disabled, the services are interrupted.
Possible Causes
l Bit error alarms, such as BIP_EXC and BIP_SD, occur on the line.
l The virtual concatenation delay times out.
l The MFI field in the K4 byte transmitted by the peer end is incorrect.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the VCAT_LOM_VC4 alarm.
Step 2 On the NMS, check whether bit error alarms, such as BIP_EXC and BIP_SD, are reported on
the board. If yes, clear them first and check whether the VCAT_LOM_VC4 alarm is cleared.
Step 3 On the NMS, check whether the VCAT_LOA alarm is reported on the board. If yes, the virtual
concatenation delay times out. See the method of handling the VCAT_LOA alarm to clear it.
Then, check whether the VCAT_LOM_VC4 alarm is cleared.
Step 4 If the alarm persists, check whether the board is faulty. If yes, replace the faulty board. Then,
Step 5 If the alarm persists, the MFI domain transmitted from the peer SDH NE is incorrect. Replace
the peer related board and check whether the alarm is cleared.
----End
Related Information
None.
4.187 VOA_ADJUST_FAIL
Description
The VOA_ADJUST_FAIL is an alarm indicating a variable optical attenuator (VOA)
adjustment failure.

Attribute
Parameters
Name Meaning

l 0x01: upper-threshold crossing

When this alarm occurs, commands will fail to be issued.
Possible Causes
l The signal attenuation between the receive and transmit optical ports of the dispersion
compensation module (DCM) connected to the board is above the upper threshold.
l The laser is shut down.
Procedure
Step 1 Check the attenuation between the receive and transmit optical ports of the dispersion
compensation module (DCM) connected to the board. If the attenuation is above the upper
threshold, adjust the DCM so that the attenuation is within the normal range. Then, check whether
Step 2 If the alarm persists, verify that the laser of the board is enabled.
----End
Related Information
None.
4.188 W_R_FAIL
Description
The W_R_FAIL is an alarm indicating a failure to read and write a chip register, that is, the read
data is inconsistent with the written data.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the serial number of the register on the board. Parameter values 0x01
to 0x09 indicate that the chip is faulty. Each value indicates a chip of a certain
type.

When this alarm occurs, the board works improperly. As a result, service receiving and
transmission are affected, and the current performance value of the board may fail to be queried.
Possible Causes
Procedure
Step 1 Cold reset the faulty board on the NMS. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the faulty board. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the local clock board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.189 WAVEDATA_MIS
Description
The WAVEDATA_MIS is an alarm indicating a wavelength (band) mismatch. This alarm is
reported when the configured logical wavelength (band) does not match the actual wavelength
(band).

Attribute
Parameters
None.

Services may be interrupted.
Possible Causes
l The configured logical wavelength (band) does not match the actual wavelength (band).
Procedure
Step 1 On the NMS, query the actual and logical wavelength of the board. Verify that the configured
logical wavelength (band) matches the actual wavelength (band). Then, check whether the alarm
is cleared.
Step 2 If the alarm persists, replace the board or optical module.
----End
Related Information
None.
4.190 XC_UNSWITCH
Description
The XC_UNSWITCH is an alarm indicating that a cross-connect matrix is not switched.
Attribute
Parameters
None.


When this alarm occurs, the alarm-reporting board-related services are interrupted.
Possible Causes
l The NE fails to respond the command issued by the cross-connect or line board for
synchronously or asynchronously switching the cross-connect matrix. As a result, the cross-
connect or line board does not update the cross-connect matrix configured on the NE.
l The board is in the BIOS state so that the board cannot update the cross-connect matrix
configured on the NE.
Procedure
Step 1 Check whether a communication alarm occurs on the board that reports the XC_UNSWITCH
alarm. If yes, clear the communication alarm. Then, check whether the XC_UNSWITCH alarm
is cleared.
Step 2 If the alarm persists, warm reset the board. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, contact Huawei technical support engineers to reload board software. Then,
----End
Related Information
None.

Alarms and Performance Events Reference 5 Performance Event List
5 Performance Event List
About This Chapter
This topic describes all performance events that may occur on the OptiX OSN 9560.
5.1 Performance Events by Type

Performance events show the key parameters of the working performance of the equipment.
This topic lists the performance events of the equipment based on the service type.
5.2 Board Performance Event List
This topic uses a table to list the performance events of boards that are supported by the
equipment.

5.1 Performance Events by Type

Performance events show the key parameters of the working performance of the equipment.
This topic lists the performance events of the equipment based on the service type.
As shown in Table 5-1, based on the functions monitored by the performance events, the
performance events are classified into pointer justification performance events, check and error
correction performance events, equipment function performance events, and Ethernet
performance events.
Table 5-1 Classification of performance events

Type Definition
Pointer justification Indicates the performance events of positive justification count

performance events and negative justification count of the pointers in the SDH frames.
Check and error Indicates the performance events regarding service check and bit
correction performance error correction of a board, such as:
events l Bit error performance events in the multiplex section
l Bit error performance events in the regeneration section
l Bit error performance events of the higher order paths
l Bit error performance events of the lower order paths
l FEC service performance events
l TCM performance events
Equipment function Indicates the performance events such as the operating

performance events environment of the boards on the equipment, the board status,
optical power cross-threshold of the laser, working current cross-
threshold of the laser, receive signal level cross-threshold of a
board, transmit signal level cross-threshold of a board, including
the laser performance events, microwave power performance
events and board status performance events.
Ethernet performance Indicates the performance events such as the number of received
events or transmitted packets lost on a board, conflict detection, and
quality.
5.1.1 Pointer Justification Performance Event List

This topic lists the performance events for pointer justifications.

Table 5-2 Pointer justification performance event list
Abbreviation Description Related Boards
AUPJCHIGH Count of positive AU pointer N4SLO16 N4SLQ64 N3SLH41

justifications N4SF64 N4SLQ16 N4SLD64
AUPJCLOW Count of negative AU pointer
justifications
AUPJCNEW Count of new AU pointer

justifications
5.1.2 Regenerator Section Performance Event List

This topic lists the performance events for bit errors in the regeneration sections.
Table 5-3 Regenerator section bit error performance event list
RSBBE Regenerator section block of N4SLO16 N4SLQ64 N3SLH41

background error N4SF64 N4SLQ16 N4SLD64
RSES Regenerator section errored
second
RSSES Regenerator section severely

errored second
RSUAS Regenerator section unavailable

second
RSOFS Regenerator section out-of-frame

second
RSOOF Regenerator section of OOF

perferance seconds
5.1.3 Multiplex Section Bit Error Performance Event List

This topic lists the performance events for the bit errors in the multiplex sections.
Table 5-4 Multiplex section performance event list
MSBBE Multiplex section block of N4SLO16 N4SLQ64 N3SLH41

background error N4SF64 N4SLQ16 N4SLD64
MSES Multiplex section errored second

MSSES Multiplex section severely errored

second
MSUAS Multiplex section unavailable

second
MSFEES Multiplex section far end errored

second
MSFESES Multiplex section far end severely

errored second
MSFEBBE Multiplex section far end block of

background error
MSFEUAS Multiplex section far end

unavailable second
5.1.4 Higher Order Path Bit Error Performance Event List

This topic lists the performance events for the bit errors in the higher order paths.
Table 5-5 Higher order path performance event list
Abbreviatio Description Related Boards

n
HPBBE Higher order path block of N1EGSH N4SLO16 N4SLQ64

background error N3SLH41 N4SF64 N4SLQ16
HPFEBBE Higher order path far end block of N1SF64A
background error
HPES Higher order path errored second
HPFEES Higher order path far end errored

second
HPSES Higher order path severely errored

second
HPFESES Higher order path far end severely

errored second
HPFEUAS Higher order path far end

consecutive severely errored second
HPUAS Higher order path unavailable

second
HPCSES Higher order path consecutive

severely errored second


n
HPFECSES Higher order path far end

consecutive severely errored second
5.1.5 Lower Order Path Bit Error Performance Event List

This topic lists the performance events for the bit errors in the lower order paths.
Table 5-6 Lower order path performance event list
VC3BBE VC3 block of background error N1EGSH
VC3ES VC3 errored second
VC3SES VC3 severely errored second
VC3FEBBE VC3 far end block of background

error
VC3FEES VC3 far end errored second
VC3FESES VC3 far end severely errored

second
VC3UAS VC3 unavailable second
VC3CSES VC3 consecutive severely errored

second
VC3FECSES VC3 far end consecutive severely

errored second
VC3FEUAS VC3 far end unavailable second
5.1.6 FEC Service Performance Event List

This topic lists the FEC service performance events.
Table 5-7 EFC service performance event list
FEC_COR_0BIT_CNT FEC corrected 0 bit count N4SF64 N4SFD64 N1SF64A
FEC_COR_1BIT_CNT FEC corrected 1 bit count
FEC_COR_BYTE_CNT FEC corrected byte count

FEC_UNCOR_BLOCK_ FEC uncorrected frames

CNT
FEC_BEF_COR_ER Bit error rate before FEC

correction
FEC_BEF_COR_ERAV Before FEC Correct Average

R Errored Rate in monitor period
FEC_AFT_COR_ER Bit error rate after FEC

correction
FEC_AFT_COR_ERAV After FEC Correct Average

R Errored Rate in monitor period
ODU2PMBIP8 Number of bit errors in the

optical channel data unit
OTU2SMBIP8 Number of bit errors in the

optical channel transport unit
5.1.7 TCM Performance Event List

TCM performance events are used to monitor the transmission performance in the tandem
connection.
Table 5-8 TCM performance event list

n
TCBBE Tandem Connection Background N4SLO16 N4SLQ64 N3SLH41

Block Error N4SF64 N1SF64A
TCFEBBE Tandem Connection Far End

Background Block Error
TCOBBE Tandem Connection Outgoing

Background Block Error
5.1.8 Laser Performance Event List

This topic lists the performance events for a laser.

Table 5-9 Laser performance event list

Abbreviati Description Related Boards
on
BCVCUR Current value of pump laser back TN11CRPC TN12OAU1

facet current TN12OBU1 N4BPA
BCVMAX Maximum value of pump laser back

facet current
BCVMIN Minimum value of pump laser back

facet current
CCVCUR Current value of laser cooling current

of erbium-doped fibre amplifier
CCVMAX Maximum value of laser cooling

current of erbium-doped fibre
amplifier
CCVMIN Minimum value of laser cooling

current of erbium-doped fibre
amplifier
EDTMPCU Current value of environment TN12OAU1 TN12OBU1 N4BPA

R temperature of erbium-doped fibre
amplifier
EDTMPMA Maximum value of environment

X temperature of erbium-doped fibre
amplifier
EDTMPMIN Minimum value of environment

temperature of erbium-doped fibre
amplifier
EDRPLCUR Current value of input optical power TN11CRPC N4BPA

of erbium-doped fibre amplifier
EDRPLMA Maximum value of input optical

X power of erbium-doped fibre
amplifier
EDRPLMIN Minimum value of input optical

power of erbium-doped fibre
amplifier
EDTPLCUR Current value of output optical

amplifier
EDTPLMA Maximum value of output optical

X power of erbium-doped fibre
amplifier


on
EDTPLMIN Minimum value of output optical

amplifier
EDWCSCU Current value of pump laser working N4BPA

R current setting
EDWCSMA Maximum value of working current

X setting
EDWCSMI Minimum value of pump laser

N working current setting
OSPICCVM Maximum value of laser cooling N4SLO16 N4SLQ64 N3SLH41

AX current N4SF64 N4SLQ16 N4SLD64
OSPICCVM Minimum value of laser cooling
IN current
OSPICCVC Average value of laser cooling

UR current
OSPITMPM Maximum value of laser working

AX temperature
OSPITMPM Minimum value of laser working

IN temperature
OSPITMPC Current value of laser working

UR temperature
RPLCUR Current value of input optical power N4SLO16 N4SLQ64 N3SLH41

RPLMAX Maximum value of input optical N4SL64 N4SFD64 N1SF64A
power
RPLMIN Minimum value of input optical

power
TLBCUR Current value of laser bias current
TLBMAX Maximum value of laser bias current
TLBMIN Minimum value of laser bias current
TPLCUR Current value of output optical

power
TPLMAX Maximum value of output optical

power
TPLMIN Minimum value of output optical

power


on
SUMIOPMA Maximum value of the total input TN12OAU1 TN12OBU1

X optical power
SUMIOPMI Minimum value of the total input

N optical power
SUMIOPCU Current value of the total input

R optical power
SUMOOPM Maximum value of the total output

AX optical power
SUMOOPMI Minimum value of the total output

N optical power
SUMOOPC Current value of the total output

UR optical power
WCVCUR Current value of pump laser working TN11CRPC TN12OAU1

current TN12OBU1 N4BPA
WCVMAX Maximum value of pump laser

working current
WCVMIN Minimum value of pump laser

working current
LSOOPMA Maximum value of laser output N1EGSH

X optical power
LSOOPMIN Minimum value of laser output

optical power
LSOOPCUR Current value of laser output optical

power
LSIOPMAX Maximum value of laser input

optical power
LSIOPMIN Minimum value of laser input optical

power
LSIOPCUR Current value of laser input optical

power
LSTMPMA Maximum value of laser working

X temperature
LSTMPMIN Minimum value of laser working

temperature
LSTMPCUR Current value of laser working

temperature


on
LSBIASMA Maximum value of laser bias current

X
LSBIASMIN Minimum value of laser bias current
LSBIASCU Current value of laser bias current

R
5.1.9 Board Status Performance Event List

This topic lists the board status performance events.
Table 5-10 Board status performance event list
XCSTMPMAX Maximum value of a board TN52STG TNL2SXCM N1EGSH

temperature N4SLO16 N4SLQ64 N3SLH41
XCSTMPMIN Minimum value of a board N4SL64 N4SFD64 N1SF64A
temperature TN12OAU1 TN12OBU1
XCSTMPCUR Current value of a board
temperature
5.1.10 RMON performance entries

RMON events indicate the transmission quality of the Ethernet services.
Table 5-11 RMON performance entries list
The total number of events in which N1EGSH

ETHDROP packets were dropped by the probe
due to lack of resources.
The total number of octets of data

(including those in bad packets)
RXOCTETS received on the network (excluding
framing bits but including FCS
octets).
The total number of packets

(including bad packets, broadcast
RXPKTS
packets, and multicast packets)
received.

The total number of good packets

received that were directed to the
RXBRDCAST
broadcast address. Note that this does
not include multicast packets.

received that were directed to a
RXMULCAST multicast address. Note that this
number does not include packets
directed to the broadcast address.
The total number of packets received

that were less than 64 octets long
ETHUNDER (excluding framing bits, but including
FCS octets) and were otherwise well
formed.

that were longer than 1518 octets
ETHOVER (excluding framing bits, but including
FCS octets) and were otherwise well
formed.

that were less than 64 octets in length
(excluding framing bits but including
FCS octets) and had either a bad
ETHFRG
Frame Check Sequence (FCS)with an
integral number of octets (FCS Error)
or a bad FCS with a non-integral
number of octets (Alignment Error).

that were longer than 1518 octets
(excluding framing bits, but including
FCS octets), and had either a bad
ETHJAB
Frame Check Sequence (FCS) with an
integral number of octets (FCS Error)
or a bad FCS with a non-integral
number of octets (Alignment Error).

(including bad packets) received that
RXPKT64 were 64 octets in length (excluding
octets).

RXPKT65 were between 65 and 127 octets in
length inclusive (excluding framing
bits but including FCS octets).





A count of MAC Control frames

received on this interface with an
RXCTLPKTS
opcode indicating the special
operation.

TXOCTETS transmitted on the network (excluding
octets).

TXPKTS
transmitted.

transmitted on this interface with an
TXCTLPKTS
opcode indicating the special
operation.
The total number of packets that

higher-level protocols requested be
transmitted, and which were
TXBRDCAST
addressed to a broadcast address at
this sub-layer, including those that
were discarded or not sent.


transmitted, and which were
TXMULCAST
addressed to a multicast address at this
sub-layer, including those that were
discarded or not sent.

RXUNICAST received that were directed to a
unicast address.

transmitted, and which were not
TXUNICAST
addressed to a multicast or broadcast
address at this sub-layer, including
those that were discarded or not sent.

received on this interface with an
RXPAUSE
opcode indicating the PAUSE
operation.

transmitted on this interface with an
TXPAUSE
opcode indicating the PAUSE
operation.
A count of frames received on a

particular interface that are an integral
number of octets in length but do not
ETHFCS pass the FCS check. This count does
not include frames received with
frame-too-long or frame-too-short
error.

(including bad packets) received and
PKT64 transmitted that were 64 octets in
length (excluding framing bits but
including FCS octets).

(including bad packets) reveived and
transmitted that were between 65 and
PKT65
127 octets in length inclusive
FCS octets).


PKT128
FCS octets).

PKT256
FCS octets).

PKT512
FCS octets).

transmitted that were between 1024
PKT1024
and 1518 octets in length inclusive
FCS octets).
The total number of transmited octets

TXFULLBGOOD of good packets (including framing
bits and FCS octets).
The total number of received octets of

RXFULLBGOOD good packets (including framing bits
and FCS octets).
The rate of transmitted octets of good

TXGOODFULLFRA
packets(including framing bits and
MESPEED
FCS octets).
The rate of received octets of good

RXGOODFULLFRA
packets(including framing bits and
MESPEED
FCS octets).
VCG_TXGOODPAC The total number of transmitted octets

KETS of good packets on the VCG port.

VCG_TXPACKETS
transmitted on the VCG port.


VCG_TXOCTETS transmitted on the VCG port
FCS octets).
VCG_RXGOODPAC The total number of received octets of

KETS good packets on the VCG port.

VCG_RXPACKETS
received on the VCG port.

VCG_RXOCTETS received on the VCG port (excluding
octets).
The rate of octets of data (including

those in bad packets) transmitted on
VCG_TXSPEED
the VCG port (excluding framing bits
but including FCS octets).
The rate of octets of data (including

those in bad packets) received on the
VCG_RXSPEED
VCG port (excluding framing bits but
including FCS octets).
5.2 Board Performance Event List

This topic uses a table to list the performance events of boards that are supported by the
equipment.
5.2.1 N1EGSH
Table 5-12 SDH
HPBBE LSIOPCUR VC3ES
HPES LSIOPMAX VC3FEBBE
HPFEBBE LSIOPMIN VC3FECSES
HPFEES LSOOPCUR VC3FEES
HPFESES LSOOPMAX VC3FESES
HPFEUAS LSOOPMIN VC3FEUAS

HPSES LSTMPCUR VC3SES
HPUAS LSTMPMAX VC3UAS
LSBIASCUR LSTMPMIN XCSTMPCUR
LSBIASMAX VC3BBE XCSTMPMAX
LSBIASMIN VC3CSES XCSTMPMIN
HPCSES HPFECSES
Table 5-13 Statistics of RMON basic performance

ETHDROP RXOCTETS RXPKTS
RXBRDCAST RXMULCAST ETHUNDER
ETHOVER ETHFRG ETHJAB
RXPKT64 RXPKT65 RXPKT128
RXPKT256 RXPKT512 RXPKT1024
Table 5-14 Statistics of RMON extended performance

RXCTLPKTS TXOCTETS TXPKTS
TXCTLPKTS TXBRDCAST TXMULCAST
RXUNICAST TXUNICAST RXPAUSE
TXPAUSE ETHFCS PKT64
PKT65 PKT128 PKT256
PKT512 PKT1024
Table 5-15 Statistics of RMON VCG performance

VCG_TXGOODPACKETS VCG_TXPACKETS VCG_TXOCTETS
VCG_RXGOODPACKETS VCG_RXPACKETS VCG_RXOCTETS
VCG_TXSPEED VCG_RXSPEED

Table 5-16 Statistics of specific events of RMON performance

TXGOODFULLFRAME-
TXFULLBGOOD RXFULLBGOOD SPEED
RXGOODFULLFRAME-
SPEED
5.2.2 N1SF64A
AUPJCHIGH MSBBE RSBBE
AUPJCLOW MSES RSES
AUPJCNEW MSFEBBE RSOFS
FEC_AFT_COR_ER MSFEES RSOOF
FEC_AFT_COR_ERAVR MSFESES RSSES
FEC_BEF_COR_ER MSFEUAS RSUAS
FEC_BEF_COR_ERAVR MSSES TCBBE
FEC_COR_0BIT_CNT MSUAS TCFEBBE
FEC_COR_1BIT_CNT ODU2PMBIP8 TCOBBE
FEC_COR_BYTE_CNT OSPICCVCUR TLBCUR
FEC_UNCOR_BLOCK_CN
T OSPICCVMAX TLBMAX
HPBBE OSPICCVMIN TLBMIN
HPES OSPITMPCUR TPLCUR
HPFEBBE OSPITMPMAX TPLMAX
HPFEES OSPITMPMIN TPLMIN
HPFESES OTU2SMBIP8 XCSTMPCUR
HPFEUAS RPLCUR XCSTMPMAX
HPSES RPLMAX XCSTMPMIN
HPUAS RPLMIN HPCSES
HPFECSES

5.2.3 N3SLH41
AUPJCHIGH MSFEUAS RSSES
AUPJCLOW MSSES RSUAS
AUPJCNEW MSUAS TCBBE
HPBBE OSPICCVCUR TCFEBBE
HPES OSPICCVMAX TCOBBE
HPFEBBE OSPICCVMIN TLBCUR
HPFEES OSPITMPCUR TLBMAX
HPFESES OSPITMPMAX TLBMIN
HPFEUAS OSPITMPMIN TPLCUR
HPSES RPLCUR TPLMAX
HPUAS RPLMAX TPLMIN
MSBBE RPLMIN XCSTMPCUR
MSES RSBBE XCSTMPMAX
MSFEBBE RSES XCSTMPMIN
MSFEES RSOFS RSOOF
MSFESES HPCSES HPFECSES
5.2.4 N4BPA
WCVMAX WCVMIN WCVCUR
CCVMAX CCVMIN CCVCUR
BCVMAX BCVMIN BCVCUR
EDTPLMAX EDTPLMIN EDTPLCUR
EDRPLMAX EDRPLMIN EDRPLCUR
EDWCSMAX EDWCSMIN EDWCSCUR
EDTMPMAX EDTMPMIN EDTMPCUR
5.2.5 N4SF64
AUPJCHIGH MSBBE RSBBE

AUPJCLOW MSES RSES
AUPJCNEW MSFEBBE RSOFS
FEC_AFT_COR_ER MSFEES RSOOF
FEC_AFT_COR_ERAVR MSFESES RSSES
FEC_BEF_COR_ER MSFEUAS RSUAS
FEC_BEF_COR_ERAVR MSSES TCBBE
FEC_COR_0BIT_CNT MSUAS TCFEBBE
FEC_COR_1BIT_CNT ODU2PMBIP8 TCOBBE
FEC_COR_BYTE_CNT OSPICCVCUR TLBCUR
FEC_UNCOR_BLOCK_CN
T OSPICCVMAX TLBMAX
HPBBE OSPICCVMIN TLBMIN
HPES OSPITMPCUR TPLCUR
HPFEBBE OSPITMPMAX TPLMAX
HPFEES OSPITMPMIN TPLMIN
HPFESES OTU2SMBIP8 XCSTMPCUR
HPFEUAS RPLCUR XCSTMPMAX
HPSES RPLMAX XCSTMPMIN
HPUAS RPLMIN HPCSES
HPFECSES
5.2.6 N4SFD64
AUPJCHIGH HPUAS RPLMAX
AUPJCLOW MSBBE RPLMIN
AUPJCNEW MSES RSBBE
FEC_AFT_COR_ER MSFEBBE RSES
FEC_AFT_COR_ERAVR MSFEES RSOFS
FEC_BEF_COR_ER MSFESES RSOOF
FEC_BEF_COR_ERAVR MSFEUAS RSSES
FEC_COR_0BIT_CNT MSSES RSUAS

FEC_COR_1BIT_CNT MSUAS TLBCUR
FEC_COR_BYTE_CNT ODU2PMBIP8 TLBMAX
FEC_UNCOR_BLOCK_CNT OSPICCVCUR TLBMIN
HPBBE OSPICCVMAX TPLCUR
HPES OSPICCVMIN TPLMAX
HPFEBBE OSPITMPCUR TPLMIN
HPFEES OSPITMPMAX XCSTMPCUR
HPFESES OSPITMPMIN XCSTMPMAX
HPFEUAS OTU2SMBIP8 XCSTMPMIN
HPSES RPLCUR HPCSES
HPFECSES
5.2.7 N4SL64
AUPJCHIGH MSFESES RSOFS
AUPJCLOW MSFEUAS RSOOF
AUPJCNEW MSSES RSSES
HPBBE MSUAS RSUAS
HPES OSPICCVCUR TLBCUR
HPFEBBE OSPICCVMAX TLBMAX
HPFEES OSPICCVMIN TLBMIN
HPFESES OSPITMPCUR TPLCUR
HPFEUAS OSPITMPMAX TPLMAX
HPSES OSPITMPMIN TPLMIN
HPUAS RPLCUR XCSTMPCUR
MSBBE RPLMAX XCSTMPMAX
MSES RPLMIN XCSTMPMIN
MSFEBBE RSBBE RSES
MSFEES HPCSES HPFECSES

5.2.8 N4SLD64
HPBBE MSUAS RSUAS
MSFEBBE RSBBE RSES
5.2.9 N4SLO16
HPSES RPLCUR TPLMAX
HPUAS RPLMAX TPLMIN

MSFEES RSOFS RSOOF
5.2.10 N4SLQ16
HPBBE MSUAS RSUAS
MSFEBBE RSBBE RSES
5.2.11 N4SLQ64

HPSES RPLCUR TPLMAX
HPUAS RPLMAX TPLMIN
MSFEES RSOFS RSOOF
5.2.12 TN11CRPC
ENVTMPMAX ENVTMPMIN ENVTMPCUR
EDTPLMAX EDTPLMIN EDTPLCUR
5.2.13 TN12OAU1
XCSTMPMAX XCSTMPMIN XCSTMPCUR
SUMIOPMAX SUMIOPMIN SUMIOPCUR
SUMOOPMAX SUMOOPMIN SUMOOPCUR

5.2.14 TN12OBU1
SUMIOPMAX SUMIOPMIN SUMIOPCUR
SUMOOPMAX SUMOOPMIN SUMOOPCUR
5.2.15 TN52STG
XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.16 TNL2SXCM

Alarms and Performance Events Reference 6 Performance Event Clearing
6 Performance Event Clearing
About This Chapter
This chapter describes the method and steps of clearing the performance events.
NOTE
For details about how to clear bit errors, see "Troubleshooting Bit Errors" in the Troubleshooting.
6.1 Performance Event Clearing of SDH

This section describes the method and steps of clearing the performance events of SDH.
6.2 Performance Threshold-Crossing Event Clearing of RMON
This section describes the method of clearing the performance threshold-crossing events of
RMON.

6.1 Performance Event Clearing of SDH

This section describes the method and steps of clearing the performance events of SDH.
6.1.1 AUPJCHIGH
Description
AUPJCHIGH indicates the positive justification count of the administrative unit (AU) pointer.
Attribute
Performance Performance Event Type
Event ID
0x2A Pointer justification
Impact on System
A small number of positive justification events of the AU pointer occur in the data segment,
which does not affect the system. If the pointer justification event occurs frequently, you need
to check the causes and rectify the frequent adjustments so that the system runs stably.
Generation Principle and Possible Causes

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
asynchronous. The possible causes of the event are as follows:
l The performance of the external clock deteriorates.

l The clocks on two NEs trace each other because optical fibers are connected incorrectly.
l The equipment performance deteriorates due to high temperature.
l The clocks are configured incorrectly. If the extended SSM protocol is enabled but clock
IDs are not set, the loss of the primary clock source causes the network-wide pointer
justification event.
l The clock quality deteriorates because the SSM clock protection is disabled.
l The performance of the line board deteriorates.
l The performance of the clock board deteriorates.
Related Alarms
None.
Procedure
Step 1 Check whether clock alarms, such as SYN_BAD, LTI, S1_SYN_CHANGE, and
EXT_SYNC_LOS, are generated on the entire network. If yes, clear them first.

Step 2 For network-wide pointer justification, check whether clock configurations are the same as
planned. The configurations to be checked include the clock ID, SSM protocol, and clock tracing
level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are connected correctly,
and whether the ambient temperature of the equipment is within the normal range. If the AU
pointer justification event occurs continuously, contact Huawei technical support engineers for
a solution.
----End
Related Information
None.
6.1.2 AUPJCLOW
Description
AUPJCLOW indicates the negative justification count of the administrative unit (AU) pointer.
Attribute
Event ID
0x2B Pointer justification
Impact on System
A small number of negative justification events of the AU pointer occur in the data segment,
which does not affect the system. If the pointer justification event occurs frequently, you need
to check the causes and rectify the frequent adjustments so that the system runs stably.

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
asynchronous. The possible causes of the event are as follows:


Related Alarms
None.
Procedure
level.
a solution.
----End
Related Information
None.
6.1.3 AUPJCNEW
Description
AUPJCNEW indicates the new count of the administrative unit (AU) pointer.
Attribute
Event ID
0x2C Pointer justification
Impact on System
A new count of AU pointers is generated, which does not affect the system. If a new count of
AU pointers is generated frequently, you need to check the causes and rectify the frequent
adjustments so that the system runs stably.

The root cause of generating new data flag (pointer) for the AU pointer justification event is that
the clocks of NEs on the SDH network are asynchronous. As a result, the new AU data flag
(pointer) event is generated. The possible causes are as follows:



Related Alarms
None.
Procedure
level.
a solution.
----End
Related Information
None.
6.1.4 BCV
Description
BCV indicates the performance of the pump-laser back-facet current. It includes BCVMAX,
BCVMIN, and BCVCUR, which respectively indicate the maximum, minimum, and current
values.
Attribute
Event ID
BCVMAX: 0x76 Equipment function
BCVMIN: 0x77
BCVCUR: 0x78

Impact on System
None.

The back-facet current is the current that is O/E converted from part of light reflected from the
resonant cavity of a laser. The back-facet current indicates the laser output optical power value.
If the BCVCUR is 0, the laser is faulty. Replace the board where this faulty laser resides.
Related Alarms
None.
Procedure
Step 1 None.
----End
Related Information
None.
6.1.5 CCV
Description
CCV indicates the performance of the pump-laser cooling current. It includes the CCVMAX,
CCVMIN, and CCVCUR, which respectively indicate the maximum, minimum, and current
values.
Attribute
Event ID
CCVMAX: 0x73 Equipment function
CCVMIN: 0x74
CCVCUR: 0x75
Impact on System
None.

Use an A/D converter to sample the voltage corresponding to the cooling current of each laser
and convert the voltages into cooling currents. The values indicate the working status of the
cooling circuit in a specific laser.

Related Alarms
Alarm Name Correlation
PUMP_COOL_EXC This alarm is generated when the cooling current of a laser exceeds
the normal range.
Procedure
Step 1 If any alarms occur, see alarm handling methods to handle them.
----End
Related Information
None.
6.1.6 EDTMP
Description
EDTMP indicates the laser temperature. It includes the EDTMPMAX, EDTMPMIN, and
EDTMPCUR, which respectively indicate the maximum, minimum, and current values.
Attribute
Event ID
EDTMPMAX: 0x82 Equipment function
EDTMPMIN: 0x83
EDTMPCUR: 0x84
Impact on System
None.

This performance event is detected using a hardware detecting circuit, and the result is calculated
and converted using software. If the performance value is not within the normal range, the laser
may be faulty.

Related Alarms
PUM_TEM_ALM This alarm is generated when the laser temperature exceeds

the threshold.
Procedure
----End
Related Information
None.
6.1.7 EDRPL
Description
EDRPL indicates the input optical power performance of a laser. It includes the EDRPLMAX,
EDTRLMIN, and EDRPLCUR, which respectively indicate the maximum, minimum, and
current values.
Attribute
Event ID
EDRPLMAX: 0x7C Equipment function
EDRPLMIN: 0x7D
EDRPLCUR: 0x7E
Impact on System
Bit errors may occur in services or services may be interrupted.

may be faulty.

Related Alarms
IN_PWR_HIGH This alarm is generated when the input optical power of the laser
exceeds the upper threshold.
IN_PWR_LOW This alarm is generated when the input optical power of the laser
is below the lower threshold.
Procedure
----End
Related Information
None.
6.1.8 EDTPL
Description
EDTPL indicates the output optical power performance of a laser. It includes the EDTPLMAX,
EDTRLMIN, and EDTPLCUR, which respectively indicate the maximum, minimum, and
current values.
Attribute
Event ID
EDTPLMAX: 0x79 Equipment function
EDTPLMIN: 0x7A
EDTPLCUR: 0x7B
Impact on System
Bit errors may occur in services or services may be interrupted.

may be faulty.

Related Alarms
OUT_PWR_HIGH This alarm is generated when the output optical power of the
laser exceeds the upper threshold.
OUT_PWR_LOW This alarm is generated when the output optical power of the
laser is below the lower threshold.
Procedure
----End
Related Information
None.
6.1.9 FEC_AFT_COR_ER
Description
FEC_BEF_COR_ER indicates the bit error rate (BER) after forward error correction (FEC).
Attribute
Event ID
0xFD Check and correction
Impact on System
After the error correction, the BER should be 0. If the BER is not 0, the bit errors in the services
affect the transmission quality. In this case, determine the cause in a timely manner.

This performance event shows that bit errors still exist at the receiver after FEC due to low signal
to noise ratio (SNR) at the receiving end. Normally, the BER is 0.
In this case, FEC_BEF_COR_ER coexists. Determine the cause in a timely manner.

Related Alarms
BEFFEC_EXC Indicates the bit error threshold-crossing alarm before FEC. Signals
sent from the peer board have the FEC function. As a result, the local
board counts the bit error rate before signal FEC in the receive
direction. This alarm occurs when the counted bit error rate exceeds
the threshold.
Procedure
----End
Related Information
None.
6.1.10 FEC_AFT_COR_ERAVR
Description
FEC_AFT_COR_ERAVR indicates the average bit error rate (BER) during the monitoring
period after forward error correction (FEC).
Attribute
Event ID
0x3AA1 Check and correction
Impact on System
After the error correction, the average BER should be 0. If the average BER is not 0, the bit
errors in the services affect the transmission quality. In this case, determine the cause in a timely
manner.

This performance event shows that bit errors still exist at the receiver after FEC. The bit errors
are caused by low signal to noise ratio (SNR) at the receiving end. Normally, the BER is 0. In
this case, FEC_BEF_COR_ERAVR coexists. Determine the cause in a timely manner.

Related Alarms
the threshold.
Procedure
----End
Related Information
None.
6.1.11 FEC_BEF_COR_ER
Description
FEC_BEF_COR_ER indicates the bit error rate (BER) before forward error correction (FEC).
Attribute
Event ID
0xFC Check and correction
Impact on System
Bit errors occur on the line. The services, however, may not be affected. If the BER is low, the
system operates properly. If the BER is high, determine the causes and resolve the problem in
a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
deteriorates.

This performance event shows that errors are detected at the receiver due to low signal to noise
ratio (SNR) at the receiving end.

Related Alarms
the threshold.
Procedure
----End
Related Information
None.
6.1.12 FEC_BEF_COR_ERAVR
Description
FEC_BEF_COR_ERAVR indicates the average bit error rate (BER) during the monitoring
period before forward error correction (FEC).
Attribute
Event ID
0x3AA2 Check and correction
Impact on System
Bit errors occur on the line. The services, however, may not be affected. If the BER is low, the
system operates properly. If the BER is high, determine the causes and resolve the problem in
a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
deteriorates.

This performance event shows that errors are detected at the receiver due to low signal to noise
ratio (SNR) at the receiving end.

Related Alarms
the threshold.
Procedure
----End
Related Information
None.
6.1.13 FEC_COR_0BIT_CNT
Description
FEC_COR_0BIT_CNT indicates the number of 0 bits that are corrected using the forward error
correction (FEC) function.
Attribute
Event ID
0x85 Check and correction
Impact on System
None.

This performance event shows the number of 0 bits decoded and corrected using the FEC
function, indicating the FEC capability to signals of low signal to noise ratio (SNR).
Related Alarms
None.

Procedure
Step 1 None.
----End
Related Information
None.
6.1.14 FEC_COR_1BIT_CNT
Description
FEC_COR_1BIT_CNT indicates the number of 1 bits that are corrected using the forward error
Attribute
Event ID
Impact on System
None.

This performance event shows the number of 1 bits decoded and corrected using the FEC
Related Alarms
None.
Procedure
Step 1 None.
----End
Related Information
None.

6.1.15 FEC_COR_BYTE_CNT
Description
FEC_COR_BYTE_CNT indicates the number of bytes corrected using the forward error
Attribute
Event ID
Impact on System
None.

This performance event shows the number of bytes decoded and corrected using the FEC
Related Alarms
None.
Procedure
Step 1 None.
----End
Related Information
None.
6.1.16 FEC_UNCOR_BLOCK_CNT
Description
FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected using
the FEC function.
Attribute
Event ID

Impact on System
Bit errors occur in the services and affect the signal transmission quality.

This performance event shows the number of received error frames that cannot be corrected
using the FEC function, indicating that bit errors are beyond the FEC capability. Normally, the
performance value is 0.
Related Alarms
the threshold.
Procedure
Step 1 If any alarm occurs, use the method of the relevant alarm to clear it.
----End
Related Information
None.
6.1.17 HPBBE
Description
HPBBE indicates a background block error (BBE) on a higher-order path.
Attribute
Event ID
Impact on System
A small number of bit errors occur on the higher-order path. If no related alarm is generated, the
system is not affected. You need to, however, determine the causes and resolve the problem in

a timely manner. Otherwise, alarms may be generated, and the signal transmission quality of the
higher-order path deteriorates.

The HPBBEs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:
l There is interference from the external environment.
l A fault occurs on the switch that interconnects with the SDH equipment.
l The signal cable is faulty.
l The line board malfunctions.
l The cross-connection unit is faulty.
l The clock unit is faulty.
Related Alarms
B3_SD This alarm is reported when the B3 bit error rate on the alarm path
exceeds the threshold (1×10–6).
B3_EXC This alarm is reported when the B3 bit error rate on the alarm path
exceeds the threshold (1×10-3).
Procedure
Step 1 See the methods of handling the B3_SD and B3_EXC alarms.
----End
Related Information
BBE
The BBE indicates that one or more bit errors occur in the data block during transmission.
6.1.18 HPES
Description
HPES indicates an errored second (ES) on a higher-order path.
Attribute
Event ID

Impact on System
A small number of bit errors occur on the higher-order path. If no related alarm is generated, the

The HPESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:

Related Alarms
Procedure
----End
Related Information
ES
The ES indicates a second in which one or more errored blocks are detected.
6.1.19 HPFEBBE
Description
HPFEBBE indicates a background block error (BBE) on a higher-order path detected at the
remote end.

Attribute
Event ID
Impact on System
The remote end detects that a small number of bit errors occur on the higher-order path. If no
related alarm is generated, the system is not affected. You need to, however, determine the causes
and resolve the problem in a timely manner. Otherwise, alarms may be generated, and the signal
transmission quality of the higher-order path deteriorates.

HPFEBBEs indicate the block errors on the higher-order path detected at the remote end. The
possible causes of the event are as follows:

Related Alarms
HP_REI This alarm is reported when the board detects that the value is 1 to 8 for
bits 1 to 4 of the G1 byte on the higher-order path.
Procedure
Step 1 See the method of handling the HP_REI alarm.
----End
Related Information
BBE

6.1.20 HPFEES
Description
HPFEES indicates an errored second (ES) on a higher-order path detected at the remote end.
Attribute
Event ID

The remote end detects that a small number of bit errors occur on the higher-order path. If no

The HPFEESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:
Related Alarms
Procedure
----End
Related Information
Far End Errored Second

The far end errored second (FEES) indicates an errored second that is detected at the remote
end.
6.1.21 HPFESES
Description
HPFESES indicates a severely errored second (SES) on a higher-order path detected at the
remote end.
Attribute
Event ID
Impact on System
The remote end detects that a large number of bit errors occur on the higher-order path. If no

The HPFESESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:
Related Alarms
Procedure
----End

Related Information
SES
The SES indicates a certain second in which more than 30% errored blocks occur or at least a
serious disturbance period (SDP) occurs.
6.1.22 HPFEUAS
Description
HPFEUAS indicates an unavailable second (UAS) on a higher-order path detected at the remote
end.
Attribute
Event ID
0x4C Check and correction
Impact on System
If bit errors occur in the services on a remote NE, determine the causes and resolve the problem
in a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
deteriorates.

HPFEUAS indicates the period of time that the UAT state lasts.
External causes:
l The fiber performance deteriorates or the attenuation is excessive on the remote NE.
l The fiber connector is contaminated or incorrect on the remote NE.
l The remote NE is improperly grounded.
l There is a strong interference source around the remote NE.
l The peer NE runs in an environment with a temperature that exceeds the threshold.
Equipment problems:
l The signals received by the line board on the remote NE are greatly attenuated, the
transmitting circuit on the remote end is faulty, or the receive circuit on the local end is
faulty.
l The synchronization performance of the clock is poor on the remote NE.
l The cross-connection unit and the line board do not match on the remote NE.
l The fan on the remote NE is faulty.
l The board malfunctions or the board performance deteriorates on the remote NE.

Related Alarms
HP_REI Indicates a bit error on a higher-order path detected at the remote end.
HP_RDI Indicates a failure on a higher-order path detected at the remote end.
Procedure
----End
Related Information
None.
6.1.23 HPSES
Description
HPSES indicates a severely errored second on a higher-order path.
Attribute
Event ID
Impact on System
A large number of bit errors occur on the higher-order path. If no related alarm is generated, the

The HPSESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:


Related Alarms
Procedure
----End
Related Information
SES
6.1.24 HPUAS
Description
HPUAS indicates an unavailable second (UAS) on a higher-order path.
Attribute
Event ID
Impact on System
l A large number of bit errors occur on the higher-order path. If no related alarm is generated,
the system is not affected. You need to, however, determine the causes and resolve the
problem in a timely manner. Otherwise, alarms may be generated, and the signal
l When this performance event occurs, check whether alarms, such as AU_AIS, B3_EXC,
and HP_UNEQ, exist. If yes, services may be interrupted.

The HPUASs are detected by monitoring the B3 byte. When signals are consecutively received
for 10 seconds, and the bit error rate per second is more than 10-3, the period from the first second

is called a period of UAS. When signals are consecutively received for 10 seconds, and the bit
error rate per second is less than 10-3, the period from the first second is called a period of
available second. The ES indicates a second in which one or more errored blocks are detected.
The possible causes of the event are as follows:
Related Alarms
AU_AIS When this alarm occurs, the HPUAS value increases.
HP_TIM When this alarm occurs, the HPUAS value increases.
HP_UNEQ When this alarm occurs, the HPUAS value increases.
Procedure
Step 1 See the methods of handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and HP_UNEQ alarms.
----End
Related Information
None.
6.1.25 LSBIAS
Description
LSBIAS indicates the bias current of a laser. It includes LSBIASMAX, LSBIASMIN, and
LSBIASCUR, which respectively indicate the maximum, minimum, and current values.

Attribute
Event ID
LSBIASMAX: Equipment function

0xCF
LSBIASMIN: 0xD0
LSBIASCUR: 0xD1
Impact on System
None.

The LSBIAS performance value is obtained after hardware check and software conversion.
Related Alarms
TD Indicates that the laser performance deteriorates. This alarm is

generated when the working current of the laser exceeds the threshold
or the multiples of the threshold.
LSR_WILL_DIE Indicates that laser life is to end. This alarm is generated when the
working current of the laser exceeds the threshold or the multiples of
the threshold.
Procedure
----End
Related Information
None.
6.1.26 LSIOP
Description
LSIOP indicates the input optical power on a board. It includes LSIOPMAX, LSIOPMIN, and
LSIOPCUR, which respectively indicate the maximum, minimum, and current values.

Attribute
Event ID
LSIOPMAX: 0xC9 Equipment function
LSIOPMIN: 0xCA
LSIOPCUR: 0xCB
Impact on System
When the input optical power is out of range, bit errors and the LOF alarm may be generated in
the received signals. As a result, services are affected.

The hardware checks the optical module, and the software converts the check result into an
LSIOP to indicate the input-optical-power performance of the board.
Related Alarms
IN_PWR_HIGH This alarm is generated when the input optical power of the board
IN_PWR_LOW This alarm is generated when the input optical power of the board is
below the lower threshold.
Procedure
Step 1 If no alarm is reported when the current performance value is at least 2 dB higher than the
historical performance value, and the change in optical power is not caused by normal operations
such as expansion or upgrade, see the method of handling the IN_PWR_HIGH alarm.
Step 2 If no alarm is reported when the current performance value is at least 2 dB lower than the
such as expansion or upgrade, see the method of handling the IN_PWR_LOW alarm.
----End
Related Information
None.

6.1.27 LSOOP
Description
LSOOP indicates the output optical power on a board. It includes LSOOPMAX, LSOOPMIN,
and LSOOPCUR, which respectively indicate the maximum, minimum, and current values.
Attribute
Event ID
LSOOPMAX: 0xC6 Equipment function
LSOOPMIN: 0xC7
LSOOPCUR: 0xC8
Impact on System
If the output optical power of the laser is abnormal, service transmission will be affected.

The hardware checks the optical module, and the software converts the check result into an
LSOOP to indicate the output-optical-power performance of the board.
Related Alarms
OUT_PWR_HIGH This alarm is generated when the output optical power of the board
OUT_PWR_LOW This alarm is generated when the output optical power of the board is
below the lower threshold.
TF Indicates a laser transmission failure. This alarm is generated when

the output optical power of the board is 1 dB lower than the lower
threshold.
Procedure
such as expansion or upgrade, see the method of handling the OUT_PWR_HIGH alarm.
such as expansion or upgrade, see the method of handling the OUT_PWR_LOW alarm.

----End
Related Information
None.
6.1.28 LSTMP
Description
LSTMP indicates the temperature of a laser. It includes LSTMPMAX, LSTMPMIN, and
LSTMPCUR, which respectively indicate the maximum, minimum, and current values.
Attribute
Event ID
LSTMPMAX: Equipment function

0xCC
LSTMPMIN: 0xCD
LSTMPCUR: 0xCE
Impact on System
None.

Normally, the laser temperature is a stable value. This value is obtained by software through
calculating the result output by the temperature detecting circuit in the laser.
Related Alarms
TEM_HA Indicates that the laser temperature is over-high. This alarm

is reported when the laser temperature exceeds the upper
threshold.
TEM_LA Indicates that the laser temperature is over-low. This alarm

is reported when the laser temperature is below the lower
threshold.

Procedure
----End
Related Information
None.
6.1.29 MSBBE
Description
MSBBE indicates a background block error (BBE) in a multiplex section.
Attribute
Event ID
Impact on System
A small number of bit errors occur in the multiplex section. If no related alarm is generated, the
multiplex section deteriorates.

The MSBBEs are detected by monitoring the B2 byte. The possible causes of the event are as
follows:

l The performance of the optical fiber deteriorates.
Related Alarms
B2_SD This alarm is reported when the board has detected that the B2 bit error
rate exceeds the specified B2_SD alarm threshold (default value: 10–6).

B2_EXC This alarm is reported when the board has detected that the B2 bit error
rate exceeds the specified B2_EXC alarm threshold (default value: 10–
3).
Procedure
----End
Related Information
BBE
6.1.30 MSES
Description
MSES indicates an errored second (ES) in a multiplex section.
Attribute
Event ID
Impact on System
A small number of bit errors occur in the multiplex section. If no related alarm is generated, the

The MSESs are detected by monitoring the B2 byte. The possible causes of the event are as
follows:

Related Alarms
B2_SD This alarm is reported when the board has detected that the
B2 bit error rate exceeds the specified B2_SD alarm threshold
(default value: 10-6).
B2_EXC This alarm is reported when the board has detected that the
B2 bit error rate exceeds the specified B2_EXC alarm
threshold (default value: 10-3).
Procedure
----End
Related Information
ES
The ES indicates the second in which one or more errored blocks are detected.
6.1.31 MSFEBBE
Description
MSFEBBE indicates a background bit error (BBE) at the remote end of a multiplex section.
Attribute
Event ID
Impact on System
A small number of bit errors occur at the remote end of the multiplex section. If no related alarm
is generated, services at the local and remote ends are not affected. You need to, however,
determine the causes and resolve the problem in a timely manner. Otherwise, alarms may be
generated, and the signal transmission quality of the multiplex section deteriorates.

The MSFEBBE indicates that one or more bit errors occur in the data block during transmission.
The MSFEBBE indicates that the local end discovers that the remote end has detected a bit error
in the multiplex section. The possible causes of the event are as follows:


l The line board at the remote end malfunctions.
l The cross-connection unit at the remote end is faulty.
l The clock unit at the remote end is faulty.
Related Alarms
MS_REI This alarm is reported when the board has detected that the value is 1
to 24 for the M1 overhead byte in the multiplex section.
Procedure
Step 1 See the method of handling the MS_REI alarm.
----End
Related Information
None.
6.1.32 MSFEES
Description
MSFEES indicates an errored second (ES) at the remote end of a multiplex section.
Attribute
Event ID

A small number of bit errors occur at the remote end of the multiplex section. If no related alarm
is generated, the system is not affected. You need to, however, determine the causes and resolve
the problem in a timely manner. Otherwise, alarms may be generated, and the signal transmission
quality of the multiplex section deteriorates.

The MSFEESs are detected by monitoring the B2 byte. The possible causes of the event are as
follows:


Related Alarms
MS_REI If the board has detected that the value is 1 to 24 for the M1 overhead
byte in the multiplex section, this alarm is reported.
Procedure
----End
Related Information
ES
The ES indicates the second in which one or more errored blocks are detected.
6.1.33 MSFESES
Description
MSFESES indicates a severely errored second (SES) at the remote end of a multiplex section.
Attribute
Event ID
Impact on System
A large number of bit errors occur at the remote end of the multiplex section. If no related alarm
is generated, the system is not affected. You need to, however, determine the causes and resolve
quality of the multiplex section deteriorates.

The MSFESESs are detected by monitoring the B2 byte. The possible causes of the event are
as follows:


Related Alarms
MS_REI If the board has detected that the value is 1 to 24 for the M1 overhead
byte in the multiplex section, this alarm is reported.
Procedure
----End
Related Information
SES
The SES indicates a certain second in which more than 30% errored blocks (15% for STM-1
signals and 25% for STM-4 signals) occur or at least a serious disturbance period (SDP) occurs.
6.1.34 MSFEUAS
Description
MSFEUAS indicates a period of unavailable second (UAS) at the remote end of a multiplex
section.
Attribute
Event ID
Impact on System
If bit errors occur in the services on a remote NE but no related alarm is reported on the remote
NE, the system will not be affected. However, you need to determine the causes and troubleshoot
quality deteriorates.


MSFEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l The fiber performance deteriorates or the attenuation is excessive on the remote NE.
l The fiber connector is dirty or incorrect on the remote NE.
l The remote NE is improperly grounded.
l There is a strong interference source around the remote NE.
l The working temperature is extremely high or low, and the remote NE cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation at the receiving side of the line board on the remote NE is excessive,
the transmitting circuit on the remote end is faulty, or the receiving circuit on the local end
is faulty.
l The remote NE has poor clock synchronization performance.
l The cross-connection unit and the line board poorly match on the remote NE.
l The fan on the remote NE is faulty.
l The board malfunctions or the board performance deteriorates on the remote NE.
Related Alarms
MS_REI Indicates a bit error at the remote end of the multiplex section.
MS_RDI Indicates a failure at the remote end of the multiplex section.
Procedure
----End
Related Information
None.
6.1.35 MSSES
Description
MSSES indicates a severely errored second (SES) in a multiplex section.

Attribute
Event ID
Impact on System
A large number of bit errors occur in the multiplex section. If no related alarm is generated, the

The MSSESs are detected by monitoring the B2 byte. The SES indicates a certain second in
which more than 30% errored blocks (15% for STM-1 signals and 25% for STM-4 signals) occur
or at least a serious disturbance period (SDP) occurs. The possible causes of the event are as
follows:

Related Alarms
rate exceeds the specified B2_SD alarm threshold (default value: 10-6).
rate exceeds the specified B2_EXC alarm threshold (default value:
10-3).
Procedure
----End
Related Information
None.

6.1.36 MSUAS
Description
MSUAS indicates a period of unavailable second (UAS) in a multiplex section.
Attribute
Event ID
Impact on System
When this performance event occurs, services are unavailable in the multiplex section.

The MSUASs are detected by monitoring the B2 byte. When the SES event occurs for more
than 10 consecutive seconds, the unavailable time begins from the eleventh second, including
the previous 10 seconds. When the SES event does not occur for more than 10 consecutive
seconds, the available time begins from the eleventh second, including the previous 10 seconds.
The possible causes of the event are as follows:

Related Alarms
rate exceeds the specified B2_SD alarm threshold (default value: 10–6).
rate exceeds the specified B2_EXC alarm threshold (default value: 10–
3).
R_LOS When this alarm is generated, the UAS event in the multiplex section is
generated.
R_LOF When this alarm is generated, the UAS event in the multiplex section is
generated.

Procedure
Step 1 See the methods of handling the B2_SD, B2_EXC, R_LOS, and R_LOF alarms.
----End
Related Information
None.
6.1.37 ODU2PMBIP8
Description
ODU2PMBIP8 indicates the number of BIP8 bit errors in the PM section at the optical data unit
(ODU) layer.
Attribute
Event ID
0x104B Check and correction
Impact on System
Bit errors occur in the services. Determine the causes and resolve the problem in a timely manner.
Otherwise, alarms may be generated, and the signal transmission quality deteriorates.

This performance event indicates the number of bit errors that a board with an OTN interface
detects in the PM section at the ODU layer through the BIP8 check. Normally, the performance
value is 0.
Related Alarms
PM_BIP8_OVER This alarm is generated when the number of BIP8 bit

errors in the PM section of the ODU layer exceeds the
threshold.
PM_BIP8_SD This alarm is generated when the number of BIP8 bit

errors in the PM section of the ODU layer exceeds the
degrade threshold.

Procedure
----End
Related Information
None.
6.1.38 OSPITMPMIN
Description
OSPITMPMIN indicates the minimum temperature of a laser core.
Attribute
Event ID
0x6D Check and correction
Impact on System
The performance event does not affect the equipment and the system. If the temperature of the
laser core is below the lower threshold, however, the laser may work improperly. If the cooling
current is within the normal range, no action is required.

The performance event monitors the temperature of the laser core to help users know about the
historical minimum temperature of the laser.
Related Alarms
TEM_HA This alarm is reported when the laser temperature is above

the upper threshold.
TEM_LA This alarm is reported when the laser temperature is below

Procedure
Step 1 See the methods of handling the TEM_HA and TEM_LA alarms.
----End

Related Information
None.
6.1.39 OSPITMPMAX
Description
OSPITMPMAX indicates the maximum temperature of a laser core.
Attribute
Event ID
0x6C Check and correction
Impact on System
laser core is above the upper threshold, however, the laser may work improperly. If the cooling

The performance event monitors the temperature of the laser core to help users know about the
historical maximum temperature of the laser.
Related Alarms
TEM_HA This alarm is reported when the laser temperature exceeds the
upper threshold.

Procedure
----End
Related Information
None.

6.1.40 OSPITMPCUR
Description
OSPITMPCUR indicates the current temperature of a laser core.
Attribute
Event ID
0x6E Check and correction
Impact on System
laser core is out of range, however, the laser may work improperly and services may be
interrupted. If the cooling current is within the normal range, no action is required.

The performance event monitors the current temperature of the laser core to help users know
about the temperature status of the laser.
Related Alarms
TEM_HA This alarm is reported when the laser temperature is above

the upper threshold.

Procedure
----End
Related Information
None.
6.1.41 OSPICCVMIN
Description
OSPICCVMIN indicates the historical minimum value of the cooling current of a laser.

Attribute
Event ID
Impact on System
The performance event does not affect the equipment and the system. If the cooling current of
the laser is below the lower threshold, however, the laser may work improperly and services
may be interrupted. If the cooling current is within the normal range, no action is required.

l The performance event records the historical minimum value of the cooling current.
l The cooling current controls the temperature of the optical module. If the temperature of
the optical module is below the lower threshold, the cooling current increases to make the
temperature higher. If the temperature of the optical module is above the upper threshold,
the cooling current decreases to make the temperature lower.
Related Alarms
LSR_COOL_ALM This alarm is generated when the cooling current of the laser
exceeds the threshold.
Procedure
Step 1 See the method of handling the LSR_COOL_ALM alarm.
----End
Related Information
None.
6.1.42 OSPICCVMAX
Description
OSPICCVMAX indicates the historical maximum value of the cooling current of a laser.

Attribute
Event ID
Impact on System
the laser is above the upper threshold, however, the laser may work improperly. If the cooling

l The performance event records the historical maximum value of the cooling current.
Related Alarms
Procedure
----End
Related Information
None.
6.1.43 OSPICCVCUR
Description
OSPICCVCUR indicates the current value of the cooling current of a laser.

Attribute
Event ID
Impact on System
the laser is out of range, however, the laser may work improperly. If the cooling current is within
the normal range, no action is required.

l The performance event records the current value of the cooling current.
Related Alarms
Procedure
----End
Related Information
None.
6.1.44 OTU2SMBIP8
Description
OTU2SMBIP8 indicates the number of BIP8 bit errors in the SM section at the optical channel
transport unit (OTU) layer.

Attribute
Event ID
0x104A Check and correction
Impact on System
Bit errors occur in the services. Determine the causes and resolve the problem in a timely manner.
Otherwise, alarms may be generated, and the signal transmission quality deteriorates.

This performance event indicates the number of bit errors that a board with an OTN interface
detects in the SM section at the OTU layer through the BIP8 check. Normally, the performance
value is 0.
Related Alarms
SM_BIP8_OVER This alarm is generated when the number of BIP8 bit errors in the SM
section at the OTU layer exceeds the threshold.
SM_BIP8_SD This alarm is generated when the number of BIP8 bit errors in the SM
section at the OTU layer exceeds the degrade threshold.
Procedure
----End
Related Information
None.
6.1.45 RSBBE
Description
RSBBE indicates a background block error (BBE) in the regenerator section.

Attribute
Event ID
Impact on System
A small number of bit errors occur in the regenerator section of the line. If no related alarm is
generated, the system is not affected. You need to, however, determine the causes and resolve
quality of the regenerator section deteriorates.

The RSBBEs are detected by monitoring the B1 byte. The possible causes of the event are as
follows:

Related Alarms
rate exceeds the specified B1_SD alarm threshold (default value:
10-6).
10-3).
Procedure
----End
Related Information
BBE

6.1.46 RSES
Description
RSES indicates an errored second (ES) in the regenerator section.
Attribute
Event ID
Impact on System
A small number of bit errors occur in the regenerator section of the line. If no related alarm is

The RSESs are detected by monitoring the B1 byte. The possible causes of the event are as
follows:

Related Alarms
10-3).
Procedure
----End

Related Information
ES
The ES indicates a second in which one or more errored blocks are detected.
6.1.47 RSOFS
Description
RSOFS indicates an out-of-frame second (OFS) in the regenerator section.
Attribute
Event ID
Impact on System
When this performance event occurs, the frame alignment bytes are lost. As a result, services
are interrupted.

The out-of-frame (OOF) event indicates that frame alignment bytes are lost. The OOF second
refers to the second in which at least one OOF event occurs. When the OOF event lasts for 3
ms, the loss of frame (LOF) event occurs. The possible causes of the event are as follows:

Related Alarms
R_LOF This alarm is reported when the R_OOF alarm lasts for 3 ms.
Procedure
----End

Related Information
None.
6.1.48 RSOOF
Description
RSOOF indicates the out-of-frame (OOF) quantity in the regenerator section.
Attribute
Event ID
Impact on System
When this performance event occurs, the frame alignment bytes are lost. As a result, services
are interrupted.

The OOF event indicates that frame alignment bytes are lost. The RSOOF indicates that one or
more OOF events occur during transmission. The possible causes of the event are as follows:
Related Alarms
R_LOF This alarm is reported when the R_OOF alarm lasts for 3 ms.
Procedure
----End
Related Information
None.

6.1.49 RSSES
Description
RSSES indicates a severely errored second (SES) in the regenerator section.
Attribute
Event ID
Impact on System
A large number of bit errors occur in the regenerator section of the line. If no related alarm is

The RSSESs are detected by monitoring the B1 byte. The possible causes of the event are as
follows:
Related Alarms
rate exceeds the specified B1_SD alarm threshold (default value:
10-6).
10-3).
Procedure
----End

Related Information
SES
6.1.50 RSUAS
Description
RSUAS indicates a period of unavailable second (UAS) in the regenerator section. It indicates
the number of seconds in which services are interrupted.
Attribute
Event ID
Impact on System
When this performance event occurs, services are interrupted.

The RSUASs are detected by monitoring the B1 byte. The possible causes of the event are as
follows:

Related Alarms
10-3).

Procedure
----End
Related Information
US
When the severely errored second (SES) event occurs for more than 10 consecutive seconds,
the unavailable time begins from the eleventh second, including the previous 10 seconds. When
the SES event does not exist for more than 10 consecutive seconds, the available time begins
from the eleventh second, including the previous 10 seconds.
6.1.51 RPLMIN
Description
RPLMAX indicates the minimum value of the input optical power.
Attribute
Event ID
0x6A Check and correction
Impact on System
The performance event does not affect the equipment and the system. If the input optical power
is below the lower threshold, the laser may fail to detect signals.

The performance event monitors the input optical power of the laser to help users know about
the historical minimum input optical power of the laser.
Related Alarms
is above the upper threshold.

Procedure
----End
Related Information
None.
6.1.52 RPLMAX
Description
RPLMAX indicates the maximum value of the input optical power.
Attribute
Event ID
Impact on System
is above the upper threshold, the laser may be damaged.

The performance event monitors the current input optical power of the laser to help users know
about the historical maximum input optical power of the laser.
Related Alarms
Procedure
----End

Related Information
None.
6.1.53 RPLCUR
Description
RPLCUR indicates the current value of the input optical power.
Attribute
Event ID
0x6B Check and correction
Impact on System
is above the upper threshold, the laser may be damaged. If the input optical power is below the
lower threshold, the laser may fail to detect signals. Query the specifications for related optical
interfaces to determine the normal range of the input optical power.

The performance event monitors the current input optical power of the laser to help users know
about the current input optical power of the laser.
Related Alarms
Procedure
----End
Related Information
None.

6.1.54 SUMIOP
Description
SUMIOP indicates the total input optical power on a board. It includes SUMIOPMAX,
SUMIOPMIN, and SUMIOPCUR, which respectively indicate the maximum, minimum, and
current values.
Attribute
Event ID
SUMIOPMAX: Equipment function

0xD2
SUMIOPMIN:
0xD3
SUMIOPCUR:
0xD4
Impact on System
l If the total input optical power is above the upper threshold, the optical modules may be
damaged on the boards of the local and downstream NEs. As a result, services may
encounter bit errors or even be interrupted.
l If the total input optical power is below the lower threshold, the single-channel optical
signals output from the board may be lost. As a result, services may encounter bit errors or
even be interrupted.

The hardware circuit detects the total input optical power, and the board software reads the actual
optical power to be reported after AD value conversion.
Related Alarms
IN_PWR_HIGH Indicates that the input optical power is above the upper threshold.
The board reports this alarm if the input optical power detected is
above the upper threshold due to upper-threshold-crossing of the
input optical power, inaccurate detected optical power, or optical
module faults.
SUM_INPWR_HI Indicates that the input optical power is above the upper threshold.
The board reports this alarm when the actual input optical power
detected is above the upper threshold.

IN_PWR_LOW Indicates that the input optical power is below the lower threshold.
The board reports this alarm if the input optical power detected is
below the lower threshold due to upper-threshold-crossing of the
input optical power, inaccurate detected optical power, or optical
module faults.
SUM_INPWR_LOW Indicates that the total input optical power is below the lower
threshold. The board reports this alarm when the actual total input
optical power detected is below the lower threshold.
Procedure
such as expansion or upgrade, see the method of handling the IN_PWR_HIGH alarm.
such as expansion or upgrade, see the method of handling the IN_PWR_LOW alarm.
----End
Related Information
None.
6.1.55 SUMOOP
Description
SUMOOP indicates the total output optical power on a board. It includes SUMOOPMAX,
SUMOOPMIN, and SUMOOPCUR, which respectively indicate the maximum, minimum, and
current values.
Attribute
Event ID
SUMOOPMAX: Equipment function

0xD5
SUMOOPMIN:
0xD6
SUMOOPCUR:
0xD7

Impact on System
l If the total output optical power is above the upper threshold, the input optical power may
be above the upper threshold on boards of downstream NEs. As a result, services may
encounter bit errors or even be interrupted, and the receiving modules may be damaged on
boards of the downstream NEs.
l If the total output optical power is below the lower threshold, the input optical power may
be below the lower threshold on boards of downstream NEs. As a result, services may
encounter bit errors or even be interrupted.

and converted using software.
Related Alarms
OUT_PWR_HIGH Indicates that the output optical power is above the upper
threshold. The board reports this alarm if the output optical power
detected is above the upper threshold due to upper-threshold-
crossing of the output optical power, inaccurate detected optical
power, or optical module faults.
SUM_OUTPWR_HI Indicates that the total output optical power is above the upper
threshold. The board reports this alarm when the actual total
output optical power detected is above the upper threshold.
OUT_PWR_LOW Indicates that the output optical power is below the lower
threshold. The board reports this alarm if the output optical power
detected is below the lower threshold due to upper-threshold-
crossing of the output optical power, inaccurate detected optical
power, or optical module faults.
SUM_OUTPWR_LO Indicates that the total output optical power is below the lower
W threshold. The board reports this alarm when the actual total
output optical power detected is below the lower threshold.
Procedure
such as expansion or upgrade, see the method of handling the OUT_PWR_HIGH alarm.
such as expansion or upgrade, see the method of handling the OUT_PWR_LOW alarm.
----End

Related Information
None.
6.1.56 TPLMIN
Description
TPLMIN indicates the minimum output optical power.
Attribute
Event ID
Impact on System
The performance event does not affect the equipment and the system. If the output optical power
of the laser is out of range, the laser will fail or its life will end. If the output optical power is
within the normal range, no action is required.

The performance event helps users to monitor the output optical power of the laser and learn
about its historical minimum value.
Related Alarms
TF This alarm is reported when the output optical power of the laser is out
of range, indicating that the transmission of the laser fails.
LSR_WILL_DIE This alarm is reported when the output optical power of the laser is out
of range greatly, indicating that the laser's life will end.
Procedure
Step 1 See the methods of handling the TF and LSR_WILL_DIE alarms.
----End
Related Information
None.

6.1.57 TPLMAX
Description
TPLMAX indicates the maximum output optical power.
Attribute
Event ID
Impact on System
of the laser is out of range, the laser will fail or its life will end. As a result, services may be
interrupted. If the output optical power is within the normal range, no action is required.

about its historical maximum value.
Related Alarms
TF This alarm is reported when the output optical power of the

laser is out of range, indicating that the transmission of the
laser fails.
LSR_WILL_DIE This alarm is reported when the output optical power of the
laser is out of range greatly, indicating that the laser's life
will end.
Procedure
----End
Related Information
None.

6.1.58 TPLCUR
Description
TPLCUR indicates the current output optical power.
Attribute
Event ID
Impact on System
of the laser is out of range, the laser will fail or its life will end. As a result, services may be
interrupted. If the output optical power is within the normal range, no action is required.

about its current value.
Related Alarms
TF This alarm is reported when the output optical power of the

laser is out of range, indicating that the transmission of the
laser fails.
LSR_WILL_DIE This alarm is reported when the output optical power of the
laser is out of range greatly, indicating that the laser's life
will end.
Procedure
----End
Related Information
None.

6.1.59 TLBMIN
Description
TLBMIN indicates the minimum bias current of a laser.
Attribute
Event ID
Impact on System
The performance event does not affect the equipment and the system. If the bias current of the
laser is out of range, the laser will fail or its life will end. As a result, services may be interrupted.
If the bias current is within the normal range, no action is required.

The performance event helps users to monitor the bias current of the laser and learn about its
historical minimum value.
Related Alarms
TF This alarm is reported when the bias current of the laser is

out of range, indicating that the transmission of the laser
fails.
LSR_WILL_DIE This alarm is reported when the bias current of the laser is
greater than that for the TF alarm, indicating that the laser's
life will end.
Procedure
----End
Related Information
None.

6.1.60 TLBMAX
Description
TLBMAX indicates the maximum bias current of a laser.
Attribute
Event ID
Impact on System

The performance event helps users monitor the bias current of the laser and its historical
maximum value.
Related Alarms
TF This alarm is reported when the bias current of the laser is out of range,
indicating that the transmission of the laser fails.
LSR_WILL_DIE This alarm is reported when the bias current of the laser is greater than
that for the TF alarm, indicating that the laser's life will end.
Procedure
----End
Related Information
None.
6.1.61 TLBCUR
Description
TLBCUR indicates the current bias current of a laser.

Attribute
Event ID
Impact on System

The performance event helps users monitor the bias current of the laser and learn about its current
value.
Related Alarms
TF This alarm is reported when the bias current of the laser is out of range,
indicating that the transmission of the laser fails.
LSR_WILL_DIE This alarm is reported when the bias current of the laser is greater than
that for the TF alarm, indicating that the laser's life will end.
Procedure
----End
Related Information
None.
6.1.62 WCV
Description
WCV indicates the working current performance of a pump laser. It includes WCVMAX,
WCVMIN, and WCVCUR, which respectively indicate the maximum, minimum, and current
values.

Attribute
Event ID
WCVMAX: 0x70 Equipment function
WCVMIN: 0x71
WCVCUR: 0x72
Impact on System
When the pump laser works properly, services are not affected. If an alarm is generated, find
out the causes and clear the alarm in a timely manner.

WCV indicates the pump laser driver current of an optical amplifier (OA) board. The OA board
amplifies the input signal using the pump laser that is driven by its working current.
Related Alarms
PUM_BCM_ALM Indicates that the bias current of the pump laser exceeds the threshold.
The board reports this alarm when the pump laser driver current
detected is higher than the upper threshold due to laser faults that are
caused by laser aging, or excessively high or low ambient
temperature.
LSR_WILL_DIE Indicates that laser's life will end. The board reports this alarm when
the pump laser driver current is higher than the life termination
threshold due to laser aging.
Procedure
----End
Related Information
None.
6.1.63 XCSTMP
Description
XCSTMP indicates the temperature of the board. It includes XCSTMPMAX, XCSTMPMIN,
and XCSTMPCUR, which respectively indicate the maximum, minimum, and current values.

Attribute
Event ID
XCSTMPMAX: Equipment function

0xBC
XCSTMPMIN:
0xBD
XCSTMPCUR:
0xBE
Impact on System
Excessively high or low board temperature may cause board performance deterioration, bit
errors, or other faults.

The performance event occurs when the ambient temperature is out of range or the heat-sinking
and ventilation measures are improper.
Related Alarms
TEMP_OVER This alarm is reported if the board temperature exceeds the

threshold.
Procedure
----End
Related Information
None.
6.2 Performance Threshold-Crossing Event Clearing of

RMON
This section describes the method of clearing the performance threshold-crossing events of
RMON.

6.2.1 ETHDROP
Description
ETHDROP indicates the number of packet loss events due to insufficient resources.
NOTE
This count does not necessarily indicates the number of discarded packets but the number of packet loss
events.
Attribute
Event ID
0x79 Ethernet performance event
Impact on System
If packets are frequently lost, services are affected, and the system is affected seriously.
Therefore, rectify the fault in a timely manner.

This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, flow
control, or backward pressure.
Related Alarms
None.
Procedure
Step 1 Enable the traffic control function. Configure data traffic based on actual service requirements
and manually reduce port traffic.
----End
Related Information
None.
6.2.2 ETHUNDER
Description
ETHUNDER indicates the number of data packets, each of which contains less than 64 bytes,
received on the line side.

Attribute
Event ID
0x7A Ethernet performance event
Impact on System
The data frames whose lengths are out of range are discarded. As a result, the system services
are affected.

l The length of a data frame that is received by a port is less than 64 bytes.
l The board hardware is faulty.
Related Alarms
None.
Procedure
Step 1 Check whether the peer equipment transmits a packet whose length is less than 64 bytes.
If... Then...
The peer equipment transmits a data packet Rectify the fault on the peer equipment.
whose length is less than 64 bytes
The peer equipment transmits a data packet Go to the next step.

whose length is greater than 64 bytes
Step 2 Check the lengths of the packets whose labels are not stripped received by the local equipment.
If... Then...
Undersized packets are generated due to Change the service type to ensure that no
packet label stripping undersized packet is generated.
Undersized packets are not generated due to Go to the next step.

packet label stripping
Step 3 Replace the faulty board on the local equipment.
----End
Related Information
None.

6.2.3 ETHOVER
Description
ETHOVER indicates the number of data packets, each of which contains more than 1518 bytes,
received by ports.
Attribute
Event ID
0x7B Ethernet performance event
Impact on System
If the length of a data frame received by a port is greater than the preset maximum frame length,
the data frame is discarded. As a result, the system services are affected.

l The preset maximum frame length is less than the length of the frame that is received by a
port.
Related Alarms
None.
Procedure
Step 1 Check whether the peer equipment transmits a data packet whose length is greater than the
maximum frame length configured for the local equipment.
If... Then...
The peer equipment transmits a data packet Notify the peer equipment that the frame
whose length is greater than the maximum length should be changed.
frame length configured for the local
equipment
The peer equipment transmits a data packet Go to the next step.

whose length is less than the maximum
frame length configured for the local
equipment
Step 2 Replace the faulty board on the local equipment.
----End

Related Information
None.
6.2.4 ETHFRG
Description
ETHFRG indicates the total number of transmitted packets (including packets with FCS errors
or alignment errors), each of which contains less than 64 bytes (excluding the framing byte but
including the FCS byte). Due to noise conflict, the counter value increases normally.
Attribute
Event ID
0x7C Ethernet performance event
Impact on System
Data transmission is delayed or packet loss occurs.

l The local and peer ports work in different modes. For example, one port works in full-
duplex mode, and the other works in half-duplex mode.
l The transmission line has poor quality due to deteriorating optical fibers or network cables,
and bit errors occur.
Related Alarms
None.
Procedure
Step 1 Check whether the ports at both ends work in the same mode.
If... Then...
The ports at both ends work in different modes Change the working modes.
The ports at both ends work in the same mode Go to the next step.
Step 2 Check whether cables are faulty by replacing the suspected faulty cable with a functioning
network cable or optical fiber.
----End

Related Information
None.
6.2.5 ETHJAB
Description
ETHJAB indicates the total number of transmitted packets (including packets with FCS errors
or alignment errors), each of which contains more than 1518 bytes (excluding the framing byte
but including the FCS byte).
Attribute
Event ID
0x7D Ethernet performance event
Impact on System
Data transmission is delayed or packets are lost.

Related Alarms
None.
Procedure
If... Then...
----End

Related Information
None.
6.2.6 ETHFCS
Description
ETHFCS indicates the number of received Ethernet data frames (excluding oversized and
undersized frames) with FCS check errors at the local end.
Attribute
Event ID
0x84 Ethernet performance event
Impact on System
Data transmission is delayed or packets are lost.

Related Alarms
None.
Procedure
If... Then...
----End

Related Information
None.
6.2.7 RXPAUSE
Description
RXPAUSE indicates the number of the received MAC flow control frames with the PAUSE
operation code.
Attribute
Event ID
RXPAUSE: 0x77 Ethernet performance event
Impact on System
None.

l The packet transmit rate on the local end exceeds the port bandwidth on the peer end.
Related Alarms
None.
Procedure
Step 1 Reduce the packet transmit rate on the local end.
----End
Related Information
None.
6.2.8 TXPAUSE
Description
TXPAUSE indicates the number of the transmitted MAC flow control frames with the PAUSE
operation code.

Attribute
Event ID
TXPAUSE: 0x78 Ethernet performance event
Impact on System
None.

l The packet transmit rate on the peer end exceeds the port bandwidth on the local end.
Related Alarms
None.
Procedure
Step 1 Reduce the packet transmit rate on the peer end.
----End
Related Information
None.

Alarms and Performance Events Reference 7 Abnormal Event List
7 Abnormal Event List
This topic describes the abnormal events that the OptiX OSN 9560 supports.
Abnormal events do not necessarily occur due to exceptions. Some events, such as board reset
and switchover events, can indicate network running status while other events can prompt users
to perform operations in real time. Table 7-1 lists some abnormal events that the OptiX OSN
9560 supports.
Table 7-1 Abnormal events

Name Severity
Linear MSP switching Major
SNCP switching Major
1+1 equipment-level protection Critical

switching
RMON performance value above upper Minor

threshold
RMON performance value below lower Minor

threshold

Alarms and Performance Events Reference 8 Handling Abnormal Events
8 Handling Abnormal Events
About This Chapter
This topic describes how to handle abnormal events.
CAUTION
Board removal and insertion or cold reset will interrupt services. If services are not protected,
exercise caution when removing, inserting, or cold resetting boards.
8.1 Linear Multiplex Section Protection Switching

8.2 SNCP Switching
8.3 1+1 Equipment-Level Protection Switching
8.4 RMON Performance Value Above the Upper Threshold
8.5 RMON Performance Value Below the Lower Threshold

8.1 Linear Multiplex Section Protection Switching

Description
The linear Multiplex Section Protection (MSP) switching event is triggered and then reported
to the NMS when the current working path or protection path detects an alarm associated with
Signal Failed (SF) or Signal Degraded (SD).
Attribute
Abnormal Event Severity Abnormal Event Type
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of a linear MSP protection group.
Parameter 2 Indicates the current path where the linear MSP operates.
l Indicates the working path.
l Indicates the protection path.
Parameter 3 Indicates the type of linear MSP switching request.

l Locking
l Forcible switching
l SF switching
l SD switching
l Manual switching
l Wait-to-restore
l Exercise switching
l Reverse request
l Non-revertive request
l No request
Parameter 4 Indicates the current state of the linear MSP.

l Protocol not started
l Idle
l Switch
l Protocol starting

Name Meaning
Parameter 5 Indicates the remote or near end.

l No remote or near end
l Near end
l Remote end
Parameter 6 Indicates the cause of changing the switching state.

l Local request
l External switching commands
l K byte request
l Timeout
Impact on System
This event prompts users to identify the cause of MSP switching. If a link fails, you should repair
it promptly and ensure that the working path and protection path of the linear MSP are in the
idle state.
Possible Causes
The possible causes of the linear MSP switching are as follows:
l This event is automatically triggered.

NOTE
For details about the conditions that trigger linear MSP, see "Linear Multiplex Section Protection"
in Product DescriptionProtection Performance.
l An external switching command, such as a manual, forcible, or excise switching command,
is issued.
l Hardware or line faults occur.
Procedure
Step 1 View abnormal events on the NMS and query switching types and protection group IDs.
Step 2 Perform operations based on switching requests.
If... Then...
An external switching occurs Identify the cause and immediately clear the switching
event.
An automatic switching occurs Clear the relevant alarms and rectify the hardware or line
faults.
----End

Related Information
None.
8.2 SNCP Switching

Description
When working or protection channel of the sub-network connection protection (SNCP) detects
alarms, such as the Signal Failed (SF) or Signal Degraded (SD) alarms, the system switches
services between the working and protection channels within 50ms. In this case, the system
generates an SNCP switching event and reports it to the NMS.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the source of the SNCP, consisting of the slot number,
optical interface number, higher order path number, and lower order
path number.
Parameter 2 Indicates the sink of the SNCP, consisting of the slot number, optical
interface number, higher order path number, and lower order path
number.
Parameter 3 Indicates the current path where the SNCP operates.

l Indicates the working path.
l Indicates the protection path.
Parameter 4 Indicates the current state of the working path in the SNCP.
l NORMAL
l SD
l SF
Parameter 5 Indicates the current state of the protection path in the SNCP.
l NORMAL
l SD
l SF

Impact on System
This event prompts users to identify the cause of SNCP switching. If a link fails, you should
repair it promptly and ensure that the working path and protection path of the SNCP are in the
normal state.
Possible Causes
The possible causes of the SNCP switching are as follows:
l This event is automatically triggered.
NOTE
For details about the conditions that trigger SNCP switching, see "Sub-Network Connection
Protection" in Product DescriptionProtection Performance.
l An external switching command, such as a manual, forcible, or excise switching command,
is issued.
Procedure
Step 1 Query switching request types for SNCP switching events on the NMS.
Step 2 Perform operations based on switching requests.
If... Then...
An external switching occurs Identify the cause and immediately clear the switching
event.
An automatic switching occurs Rectify faults according to alarms and eliminate the
conditions that trigger the automatic switching.
----End
Related Information
None.
8.3 1+1 Equipment-Level Protection Switching

Description
The 1+1 equipment-level protection switching event is triggered and then reported when a
protection switching is performed between the working and protection cross-connect boards or
SCC boards.
Attribute

Parameters
Name Meaning
Parameter 1 l If the parameter value is "1", a protection

switching is performed between the working and
protection cross-connect boards.
l If the parameter value is "2", a protection
switching is performed between the working and
protection SCC boards.
Parameter 2 Indicates the ID of the slot where the current

working board is seated, for example, "9".
Parameter 3 Indicates the ID of the slot where the current

protection board is seated, for example, "10".

When 1+1 equipment-level protection switching is performed between the working and
protection cross-connect boards, services may be transiently interrupted.
Possible Causes
l An external switching command (for example, forced switching and clear switching) is
run. As a result, an active/standby protection switching is performed from the working unit
to the protection unit or from the protection unit to the working unit.
l The working unit or protection unit of the protection group becomes faulty and then is
automatically switched to the peer unit.
Procedure
Step 1 Query the type of the 1+1 protection switching event on the NMS.
Step 2 Rectify the fault according to the switching request type.
If... Then...
The switching is caused by an external Find the cause of the external switching, and
switching then clear manual switching immediately.
The working unit or protection unit of the Replace the board where the faulty unit is
protection group is faulty located.
----End
Related Information
None.

8.4 RMON Performance Value Above the Upper Threshold

Description
This event is reported when an RMON performance value within a sampling period is above the
upper threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot ID, port number and channel

number.
Parameter 2 Indicates threshold-crossing events, such as a

packet loss event.
Parameter 3 Indicates the current RMON performance value.
Parameter 4 Indicates the current maximum RMON

performance value.
Impact on System
The quality of the Ethernet service is degraded, or even the services in the system are interrupted.
Possible Causes
l The client-side data equipment is faulty, and the equipment incorrectly transmits the data
packets.
l The working modes of the ports at the local and opposite ends do not match.
l The optical line attenuation is excessively large or the receive optical power is abnormal.
l The optical fiber is damaged or the fiber connector is untidy.
l The board that reports this alarm is faulty.
Procedure
Step 1 Use the Smartbits to check for error codes sent by client equipment. If error codes exist,
troubleshoot faults on client equipment and check whether the event is cleared.

Step 2 If the event persists, check whether the ports at the local and peer ends work in the same mode.
If they work in different modes, adjust their working modes to be consistent and check whether
the event is cleared.
Step 3 On the NMS, check whether receive optical power of the optical port is within the normal range.
If the optical power is beyond the normal range, perform operations according to methods of
handling the IN_PWR_HIGH or IN_PWR_LOW alarms. Then, check whether the event is
cleared.
Step 4 If the event persists, check whether the optical-fiber connector is contaminated. If the optical-
fiber connector is contaminated, clean or replace it and check whether the event is cleared.
Step 5 If the event persists, replace the faulty board.
----End
Related Information
None.
8.5 RMON Performance Value Below the Lower Threshold

Description
This event is reported when an RMON performance value within a sampling period is below
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot ID, port number and channel

number.
Parameter 2 Indicates threshold-crossing events, such as a

packet loss event.
Parameter 3 Indicates the current RMON performance value.
Parameter 4 Indicates the current minimum RMON

performance value statistics.

Impact on System
When this event is reported, it indicates that the related Ethernet performance values are
recovered. The quality of the Ethernet service in the system is improved.
Possible Causes
The fault of the system is rectified, and the performance value is recovered.
Procedure
Step 1 Change the RMON performance lower threshold to 0 or ignore this event.
----End
Related Information
None.

Alarms and Performance Events Reference A Glossary
A Glossary
Numerics
1+1 backup A backup method in which two components mirror each other. If the active component
goes down, the standby component takes over services from the active component to
ensure that the system service is not interrupted.
1:N protection An architecture that has N normal service signals, N working SNCs/trails, and one
protection SNC/trail. It may have one extra service signal.
3G See 3rd generation.
3R reshaping, retiming, regenerating
3rd generation (3G) The third generation of digital wireless technology, as defined by the International
Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to
19.2 kbit/s offered by second generation technology.
A
A/D analog/digit
AAA See Authentication, Authorization and Accounting.
AAL See ATM Adaptation Layer.
AAL2 ATM Adaptation Layer Type 2
AAL5 ATM Adaptation Layer Type 5
ABR See available bit rate.
ACAP See adjacent channel alternate polarization.
ACH associated channel header
ACL See access control list.
ACL rule A rule for controlling the access of users.
ADM add/drop multiplexer
AF See assured forwarding.
AGC automatic gain control

AIO asynchronous input/output

AIS alarm indication signal
AIS insertion Insertion of AIS in a channel with excessive errors to indicate that it is unavailable. For
a line board, it can be set whether to insert AIS when there are excessive errors in the
B1, B2 and B3 bytes. For tributary board at the E1/T1 level, it can be set whether to
insert AIS when there are excessive errors in BIP-2. For tributary board at the E3 level
or higher, it can be set whether to insert AIS when there are excessive errors in the B3
byte.
ALS See automatic laser shutdown.
AM See adaptive modulation.
AMI See alternate mark inversion.
ANSI See American National Standards Institute.
APD See avalanche photodiode.
APID access point identifier
APS automatic protection switching
APS 1+1 protection A protection architecture that comprises one protection facility and one working facility
and performs switchover by using the Automatic Protection Switching (APS) protocol.
Normally, signals are sent only over the working facility. If an APS switchover event is
detected by the working facility, services are switched over to the protection facility.
ARP See Address Resolution Protocol.
AS See autonomous system.
ASCII American Standard Code for Information Interchange
ASK amplitude shift keying
ATM asynchronous transfer mode
ATM Adaptation An interface between higher-layer protocols and Asynchronous Transfer Mode (ATM).
Layer (AAL) The AAL provides a conversion function to and from ATM for various types of
information, including voice, video, and data.
ATM protection group Logically bound ATM VP network/subnetwork connections that share the same physical
transmission channel. In the VP Group (VPG), a pair of VP connections (working
connection and its protective connection) is used for monitoring the automatic protection
switching, called monitoring connections (APS VPCs). If the monitoring connections
switch over, the whole VPG will switch over to quicken the ATM protection switching
(as quick as the protection switching of the SDH layer).
ATPC See automatic transmit power control.
AU See administrative unit.
AUG See administrative unit group.
AWG arrayed waveguide grating
Address Resolution An Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and
Protocol (ARP) routers to determine the link layer addresses through ARP requests and ARP responses.

American National An organization that defines U.S standards for the information processing industry.
Standards Institute ANSI participates in defining network protocol standards.
(ANSI)
Authentication, A mechanism for configuring authentication, authorization, and accounting security
Authorization and services. Authentication refers to the verification of user identities and the related
Accounting (AAA) network services; authorization refers to the granting of network services to users
according to authentication results; and accounting refers to the tracking of the
consumption of network services by users.
access A link between the customer and the telecommunication network. Many technologies,
such as the copper wire, optical fiber, mobile, microwave and satellite, are used for
access.
access control list A list of entities, together with their access rights, which are authorized to have access
(ACL) to a resource.
access layer A layer that connects the end users (or last mile) to the ISP network. The access layer
devices are cost-effective and have high-density interfaces. In an actual network, the
access layer includes the devices and cables between the access points and the UPEs.
access point Any entity that has station functionality and provides access to the distribution services,
via the wireless medium (WM) for associated stations.
accumulation The sum of the service usage, consumption, and recharge fees of a subscriber.
active link A link in the link aggregation group, which is connected to the active interface.
active mode A working mode of EFM OAM. The discovery and remote loopback can only be initiated
by the interface in the active mode.
adaptive modulation A technology that is used to automatically adjust the modulation mode according to the
(AM) channel quality. When the channel quality is favorable, the equipment uses a high-
efficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment uses the
low-efficiency modulation mode to improve the anti-interference capability of the link
that carries high-priority services.
adjacency A portion of the local routing information which pertains to the reachability of a single
neighbor ES or IS over a single circuit. Adjacencies are used as input to the Decision
Process for forming paths through the routing domain. A separate adjacency is created
for each neighbor on a circuit, and for each level of routing (i.e. level 1 and level 2) on
a broadcast circuit.
adjacent channel A channel configuration method, which uses two adjacent channels (a horizontal
alternate polarization polarization wave and a vertical polarization wave) to transmit two signals.
(ACAP)
adjacent concatenation A situation where the virtual containers (VC) to carry concatenated services in SDH are
consecutive in terms of their service in the frame structures, so that they use the same
path overhead (POH).
administrative unit The information structure which provides adaptation between the higher order path layer
(AU) and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
administrative unit One or more administrative units occupying fixed, defined positions in an STM payload.
group (AUG) An AUG consists of AU-4s.

advanced ACL An ACL that defines ACL rules based on the source addresses, target addresses, protocol
type, such as TCP source or target port, the type of the ICMP protocol, and message
codes.
aggregated link Multiple signaling link sets between two nodes.
aging time The time to live before an object becomes invalid.
air interface The interface between the cellular phone set or wireless modem (usually portable or
mobile) and the active base station.
alarm A message reported when a fault is detected by a device or by the network management
system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
alarm box A device that reflects the status of an alarm in visual-audio mode. The alarm box notifies
you of the alarm generation and alarm severity after it is connected to the Signaling
Network Manager server or client and the related parameters are set.
alarm cascading The shunt-wound output of the alarm signals of several subracks or cabinets.
alarm correlation A process to analyze correlated alarms. For example, if alarm 2 is generated within five
analysis seconds after alarm 1 is generated, and it complies with the conditions defined in the
alarm correlation analysis rule, you can either mask the alarm or raise the level of alarm
2 according to the behavior defined in the alarm correlation rule.
alarm filtering An alarm management method. Alarms are detected and reported to the NMS system,
and whether the alarm information is displayed and saved is decided by the alarm filtering
status. An alarm with the filtering status set to "Filter" is not displayed and saved on the
NMS, but is monitored on the NE.
alarm indication A function that indicates the alarm status of an NE. On the cabinet of an NE, there are
four indicators in different colors indicating the current alarm status of the NE. When
the green indicator is on, the NE is powered on. When the red indicator is on, a critical
alarm is generated. When the orange indicator is on, a major alarm is generated. When
the yellow indicator is on, a minor alarm is generated. The ALM alarm indicator on the
front panel of a board indicates the current status of the board.
alarm inversion mode A mode for an NE that indicates whether the port is automatically restored to the normal
status after the service is accessed or the fault is removed. There are three alarm inversion
modes: normal, revertible and non-revertible.
alarm notification When an error occurs, the performance measurement system sends performance alarms
to the destination (for example, a file and/or fault management system) designated by
users.
alarm suppression An alarm management method. Alarms that are set to be suppressed are not reported
from NEs any more.
alternate mark A synchronous clock encoding technique which uses bipolar pulses to represent logical
inversion (AMI) 1 values.
analog signal A signal in which information is represented with a continuously variable physical
quantity, such as voltage. Because of this constant changing of the wave shape with
regard to its passing a given point in time or space, an analog signal might have a virtually
indefinite number of states or values. This contrasts with a digital signal that is expressed
as a square wave and therefore has a very limited number of discrete states. Analog
signals, with complicated structures and narrow bandwidth, are vulnerable to external
interference.

assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
(AF) It is suitable for certain key data services that require assured bandwidth and short delay.
For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that
exceeds the bandwidth limit, AF degrades the service class and continues to forward the
traffic instead of discarding the packets.
attack An attempt to bypass security controls in a system with the mission of using that system
or compromising it. An attack is usually accomplished by exploiting a current
vulnerability.
attenuation Reduction of signal magnitude or signal loss, usually expressed in decibels.
attenuator A device used to increase the attenuation of an Optical Fiber Link. Generally used to
ensure that the signal at the receive end is not too strong.
automatic laser A technique (procedure) to automatically shutdown the output power of laser transmitters
shutdown (ALS) and optical amplifiers to avoid exposure to hazardous levels.
automatic transmit A method of adjusting the transmit power based on fading of the transmit signal detected
power control (ATPC) at the receiver
autonomous system A network set that uses the same routing policy and is managed by the same technology
(AS) administration department. Each AS has a unique identifier that is an integer ranging
from 1 to 65535. The identifier is assigned by IANA. An AS can be divided into areas.
availability A capability of providing services at any time. The probability of this capability is called
availability.
available bit rate (ABR) A kind of service categories defined by the ATM forum. ABR only provides possible
forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
avalanche photodiode A semiconductor photodetector with integral detection and amplification stages.
(APD) Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
average delay A performance indicator indicating the average RTT of multiple ping operations or other
probe operations. It is expressed in milliseconds.
B
B-ISDN See broadband integrated services digital network.
BA booster amplifier
BBE background block error
BC boundary clock
BCD binary coded decimal
BDI See backward defect indication.
BDI packet A packet used to notify the upstream LSR of the failure event which has occurred on the
downstream LSR through the reverse LSP. The BDI packet can be used in the 1:1/N
protective switchover service.
BE See best effort.
BER bit error rate

BFD See Bidirectional Forwarding Detection.

BGP Border Gateway Protocol
BIP See bit interleaved parity.
BIP-8 See bit interleaved parity-8.
BIP-X bit interleaved parity-X
BITS See building integrated timing supply.
BMC best master clock
BNC See bayonet-neill-concelman.
BOM bill of material
BPDU See bridge protocol data unit.
BPS board protection switching
BSC See base station controller.
BSS base station subsystem
BTS base transceiver station
BWS backbone wavelength division multiplexing system
Bidirectional A simple Hello protocol, similar to the adjacent detection in the route protocol. Two
Forwarding Detection systems periodically send BFD detection messages on the channel between the two
(BFD) systems. If one system does not receive the detection message from the other system for
a long time, you can infer that the channel is faulty. Under some conditions, the TX and
RX rates between systems need to be negotiated to reduce traffic load.
backbone network A network that forms the central interconnection for a connected network. The
communication backbone for a country is WAN. The backbone network is an important
architectural element for building enterprise networks. It provides a path for the exchange
of information between different LANs or subnetworks. A backbone can tie together
diverse networks in the same building, in different buildings in a campus environment,
or over wide areas. Generally, the backbone network's capacity is greater than the
networks connected to it.
backplane An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backup A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
backward defect A function that the sink node of a LSP, when detecting a defect, uses to inform the
indication (BDI) upstream end of the LSP of a downstream defect along the return path.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
base station area An area of radio coverage consisting of cells served by one or more Base Transceiver
Stations (BTSs) in the same base station site.

base station controller A logical entity that connects the BTS with the MSC in a GSM/CDMA network. It
(BSC) interworks with the BTS through the Abis interface, the MSC through the A interface.
It provides the following functions: radio resource management, base station
management, power control, handover control, and traffic measurement. One BSC
controls and manages one or more BTSs in an actual network.
baseband A form of modulation in which the information is applied directly onto the physical
transmission medium.
bayonet-neill- A connector used for connecting two coaxial cables.
concelman (BNC)
bearer An information transmission path with defined capacity, delay and bit error rate.
bearer network A network used to carry the messages of a transport-layer protocol between physical
devices.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
best-effort service A unitary and simple service model. Without being approved, but after notifying the
network, the application can send any number of packets at any time. The network tries
its best to send the packets, but delay and reliability cannot be ensured. Best-Effort is
the default service model of the Internet. It can be applied to various networks, such as
FTP and E-Mail. It is implemented through the First In First-Out (FIFO) queue.
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
bit interleaved parity A method of error monitoring. With even parity an X-bit code is generated by equipment
(BIP) at the transmit end over a specified portion of the signal in such a manner that the first
bit of the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-bit
sequences within the specified portion, and so on. Even parity is generated by setting the
BIP-X bits so that there is an even number of 1s in each monitored partition of the signal.
A monitored partition comprises all bits which are in the same bit position within the X-
bit sequences in the covered portion of the signal. The covered portion includes the BIP-
X.
bit interleaved parity-8 Consists of a parity byte calculated bit-wise across a large number of bytes in a
(BIP-8) transmission transport frame. Divide a frame is into several blocks with 8 bits (one byte)
in a parity unit and then arrange the blocks in matrix. Compute the number of "1" or "0"
over each column. Then fill a 1 in the corresponding bit for the result if the number is
odd, otherwise fill a 0.
blacklist A method of filtering packets based on their source IP addresses. Compared with ACL,
the match condition for the black list is much simpler. Therefore, the black list can filter
packets at a higher speed and can effectively screen the packet sent from the specific IP
address.
bound path A parallel path with several serial paths bundled together. It improves the data throughput
capacity.

bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
bridge protocol data The data messages that are exchanged across the switches within an extended LAN that
unit (BPDU) uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
bridging The action of transmitting identical traffic on the working and protection channels
simultaneously.
broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as voice.
services digital network It currently uses the ATM technology to transmit data over SONNET-based circuits at
(B-ISDN) 155 to 622 Mbit/s or higher speed.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
broadcast address A network address in computer networking that allows information to be sent to all nodes
on a network, rather than to a specific network host.
broadcast domain A group of network stations that receives broadcast packets originating from any device
within the group. The broadcast domain also refers to the set of ports between which a
device forwards a multicast, broadcast, or unknown destination frame.
building integrated In the situation of multiple synchronous nodes or communication devices, one can use
timing supply (BITS) a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
built-in WDM A function which integrates some simple WDM systems into products that belong to the
OSN series. That is, the OSN products can add or drop several wavelengths directly.
burst A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast sending.
C
CAC See connection admission control.
CAR committed access rate
CAS multiframe A multiframe set up based on timeslot 16. Each CAS multiframe contains 16 E1 PCM
frames. Among the 8 bits of timeslot 16 in the first frame, the first 4 bits are used for
multiframe synchronization. The multiframe alignment signal (MFAS) for
synchronization is 0000. The last 4 bits are used as the not multiframe alignment signal
(NMFAS). The NMFAS is XYXX. For the other 15 frames, timeslot 16 is used to
transmit exchange and multiplexing (E&M) signaling corresponding to each timeslot.
CBR See constant bit rate.
CBS See committed burst size.
CC See continuity check.

CCDP See co-channel dual polarization.

CCS See Common Channel Signaling.
CDVT cell delay variation tolerance
CE See customer edge.
CES See circuit emulation service.
CFM connectivity fault management
CFR cell fill rate
CIR committed information rate
CIST See Common and Internal Spanning Tree.
CLEI common language equipment identification
CLK clock card
CLNP connectionless network protocol
CLP See cell loss priority.
CMI coded mark inversion
CO central office
CPU See central processing unit.
CR connection request
CRC See cyclic redundancy check.
CRC-4 multiframe A multiframe recommended by ITU-T G.704 and set up based on the first bit of timeslot
0. The CRC-4 multiframe is different from the CAS multiframe in principle and
implementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4
multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is a
CRC-4 check block that contains 2048 (256 x 8) bits. Bits C1 to C4 of a check block can
check the previous check block.
CSA Canadian Standards Association
CSES consecutive severely errored second
CSF Client Signal Fail
CSMA/CD See carrier sense multiple access with collision detection.
CST See common spanning tree.
CTC common transmit clock
CV connectivity verification
CV packet A type of packet that is generated at the frequency of 1/s on the source end LSR of an
LSP, and is terminated on the destination end LSR of the LSP. A CV packet is transmitted
from the source end LSR to the destination LSR along the LSP. A CV packet contains
the unique identifier (TTSI) of the LSP so that all types of abnormalities on the path can
be detected.
CW control word
CWDM See coarse wavelength division multiplexing.

Common Channel A signaling system used in telephone networks that separates signaling information from
Signaling (CCS) user data. A specified channel is exclusively designated to carry signaling information
for all other channels in the system.
Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the
bridged local area network are simply and fully connected.
Coordinated Universal The world-wide scientific standard of timekeeping. It is based upon carefully maintained
Time (UTC) atomic clocks and is kept accurate to within microseconds worldwide.
cabinet Free-standing and self-supporting enclosure for housing electrical and/or electronic
equipment. It is usually fitted with doors and/or side panels which may or may not be
removable.
cable distribution plate A component, which is used to arrange cables in order.
cable tie A tape used to bind cables.
carrier An organization that has telecom network resources and can provide communications
service.
carrier sense multiple Carrier sense multiple access with collision detection (CSMA/CD) is a computer
access with collision networking access method in which:
detection (CSMA/CD)
l A carrier sensing scheme is used.
l A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
cell loss priority (CLP) A field in the ATM cell header that determines the probability of a cell being dropped
if the network becomes congested. Cells with CLP = 0 are insured traffic, which is
unlikely to be dropped. Cells with CLP = 1 are best-effort traffic, which might be
dropped.
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
(CPU) and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
centralized alarm The alarms of all the hosts connecting to the Operation and Maintenance Unit (OMU).
channel A telecommunication path of a specific capacity and/or at a specific speed between two
or more locations in a network. Channels can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s, kb/s, Mb/s, Gb/s, and Tb/s.
channel spacing The center-to-center difference in frequency or wavelength between adjacent channels
in a WDM device.
check criteria A set of rules for checking and analyzing device echo information. The check criteria
for an alarm collection item need to be set through the configuration file.

circuit emulation A function with which the E1/T1 data can be transmitted through ATM networks. At the
service (CES) transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
clock selection An algorithm used for selecting the best clock for clock synchronization. For different
peers (multiple servers or peers configured for a client), a peer sends clock
synchronization packets to each server or passive peer. After receiving the response
packets, it uses the clock selection algorithm to select the best clock.
clock source A device that provides standard time for the NTP configuration.
clock synchronization Also called frequency synchronization. The signal frequency traces the reference
frequency, but the start point does not need to be consistent.
clock tracing The method to keep the time on each node synchronized with a clock source in a network.
co-channel dual A channel configuration method, which uses a horizontal polarization wave and a vertical
polarization (CCDP) polarization wave to transmit two signals. The Co-Channel Dual Polarization has twice
the transmission capacity of the single polarization.
coarse wavelength A signal transmission technology that multiplexes widely-spaced optical channels into
division multiplexing the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM
(CWDM) does not support optical amplifiers and is applied in short-distance chain networking.
collision A condition in which two packets are being transmitted over a medium at the same time.
Their interference makes both unintelligible.
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum burst
(CBS) IP packet size when the information is transferred at the committed information rate.
This parameter must be larger than 0. It is recommended that this parameter should be
not less than the maximum length of the IP packet that might be forwarded.
common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST region
(CST) is considered as a switch; therefore, the CST can be considered as their spanning tree
generated with STP/RSTP.
composite service An aggregation of a series of services relevant to each other.
conference An IP multimedia session that have two or more participants. Each conference has a
focus and can be identified uniquely.
congestion An extra intra-network or inter-network traffic that results in a decrease in network
service efficiency.
congestion A flow control measure to solve the problem of network resource competition. When
management the network congestion occurs, it places packets into the queue for buffer and determines
the packet forwarding order.
connection An association of transmission channels or telecommunication circuits, switching and
other functional units set up to provide for the transfer of signals between two or more
network points, to support a single communication.
connection admission A control process in which the network takes actions in the call set-up phase (or call re-
control (CAC) negotiation phase) to determine which connection request is admitted.

connection point A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
connectionless Pertaining to a method of data presentation. The data has a complete destination address
and is delivered by the network on a best-effort basis, independent of other data being
exchanged between the same pair of users.
constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
container A set of hardware or software devices. In software domain, it refers to the environment
variables and processes. In hardware domain, it refers to a type of topology node that
contains nodes, usually refers to one device with multiple frames; each node stands for
a frame.
continuity check (CC) Ethernet CFM can detect the connectivity between MEPs. The detection is achieved after
MEPs transmit Continuity Check Messages (CCMs) periodically.
control VLAN A VLAN that transmits only protocol packets.
control channel The channel used to transmit digital control information from the base station to a cell
phone or vice-versa.
convergence layer A "bridge" between the access layer and the core layer. The convergence layer provides
the convergence and forwarding functions for the access layer. It processes all the traffic
from the access layer devices, and provides the uplinks to the core layer. Compared with
the access layer, the convergence layer devices should have higher performance, fewer
interfaces and higher switching rate. In the real network, the convergence layer refers to
the network between UPEs and PE-AGGs.
cooling system The system that controls or influences climate by decreasing the air temperature only.
core layer A layer that functions as the backbone of high speed switching for networks and provides
high speed forwarding communications. It has a backbone transmission structure that
provides high reliability, high throughput, and low delay. The core layer devices must
have a good redundancy, error tolerance, manageability, adaptability, and they support
dual-system hot backup or load balancing technologies. In a real network, the core layer
includes the IP/MPLS backbone network consisting of NPEs and backbone routers.
correlation The similarities when two random processes vary with time.
corruption The alteration of the information in IMS networks for the purpose of deception. For
example, attackers corrupt the correct charging information to evade being charged.
cross-connection The connection of channels between the tributary board and the line board, or between
line boards inside the NE. Network services are realized through the cross-connections
of NEs.
crossover cable A twisted pair patch cable wired in such a way as to route the transmit signals from one
piece of equipment to the receive signals of another piece of equipment, and vice versa.
crystal oscillator An oscillator that produces electrical oscillations at a frequency determined by the
physical characteristics of a piezoelectric quartz crystal.
customer edge (CE) A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the
Service Provider (SP) network. A CE can be a router, switch, or host.

cutover To migrate the data of an application system to another application system, which then
provides services.
cyclic redundancy A procedure used in checking for errors in data transmission. CRC error checking uses
check (CRC) a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
D
D/A digital-analog converter
DB database
DC direct current
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common A power system, in which the BGND of the DC return conductor is short-circuited with
(with ground) (DC-C) the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with
ground) (DC-I) the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See data communications channel.
DCE See data circuit-terminating equipment.
DCF data communication function
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
DDN See digital data network.
DHCP See Dynamic Host Configuration Protocol.
DLAG See distributed link aggregation group.
DM See delay measurement.
DNI dual node interconnection
DRDB dynamic random database
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP differentiated services code point
DSL See digital subscriber line.
DSLAM See digital subscriber line access multiplexer.

DSP digital signal processing

DTE See data terminal equipment.
DTR data terminal ready
DVB digital video broadcasting
DVB-ASI digital video broadcast-asynchronous serial interface
DVMRP See Distance Vector Multicast Routing Protocol.
DWDM See dense wavelength division multiplexing.
Distance Vector An Internet gateway protocol mainly based on the RIP. The protocol implements a typical
Multicast Routing dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
Protocol (DVMRP) datagrams with its neighbors.
Dynamic Host A client-server networking protocol. A DHCP server provides configuration parameters
Configuration Protocol specific to the DHCP client host requesting, generally, information required by the host
(DHCP) to participate on the Internet network. DHCP also provides a mechanism for allocation
of IP addresses to hosts.
data backup A method that is used to copy key data to the standby storage area, to prevent data loss
in the case of damage or failure in the original storage area.
data circuit- The equipment that provides the signal conversion and coding between the data terminal
terminating equipment equipment (DTE) and the line. A DCE is located at a data station. The DCE may be
(DCE) separate equipment, or an integral part of the DTE or intermediate equipment. The DCE
may perform other functions that are normally performed at the network end of the line.
data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
data communications The data channel that uses the D1–D12 bytes in the overhead of an STM-N signal to
channel (DCC) transmit information about operation, management, maintenance and provision
(OAM&P) between NEs. The DCC channels that are composed of bytes D1–D3 are
referred to as the 192 kbit/s DCC-R channel. The other DCC channels that are composed
of bytes D4–D12 are referred to as the 576 kbit/s DCC-M channel.
data flow A process that involves processing the data extracted from the source system, such as
filtering, integration, calculation, and summary, finding and solving data inconsistency,
and deleting invalid data so that the processed data meets the requirements of the
destination system for the input data.
data mapping An algorithm that is used to convert the data between heterogeneous data models.
data restoration A method for retrieving data that is lost due to damage or misoperations.
data terminal A user device composing the UNI. The DTE accesses the data network through the DCE
equipment (DTE) equipment (for example, a modem) and usually uses the clock signals produced by DCE.
datagram A kind of protocol data unit (PDU) which is used in Connectionless Network Protocol
(CLNP), such as IP datagram, UDP datagram.
defect A limited interruption in the ability of an item to perform a required function.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a source
(DM) node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.

demodulation In communications, the means by which a modem converts data from modulated carrier
frequencies (waves that have been modified in such a way that variations in amplitude
and frequency represent meaningful information) over a telephone line. Data is converted
to the digital form needed by a computer to which the modem is attached, with as little
distortion as possible.
dense wavelength The technology that utilizes the characteristics of broad bandwidth and low attenuation
division multiplexing of single mode optical fiber, employs multiple wavelengths with specific frequency
(DWDM) spacing as carriers, and allows multiple channels to transmit simultaneously in the same
fiber.
designated port A port defined in the STP protocol. On each switch that runs the STP protocol, the traffic
from the root bridge is forwarded to the designated port. The subnet connected to the
STP switch receives the data traffic from the root bridge. All the ports on the root bridge
are designated ports. On each subnet, there is only one designated port. When a network
topology is stable, only the root port and the designated port forward traffic. Other non-
designated ports are in the blocking state, and they receive STP packets, but does not
forward user traffic.
destruction A process during which the information and resources in a network are changed
unexpectedly and the meanings of the information and resources are deleted or changed.
digital data network A high-quality data transport tunnel that combines the digital channel (such as fiber
(DDN) channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
digital modulation A method that controls the changes in amplitude, phase, and frequency of the carrier
based on the changes in the baseband digital signal. In this manner, the information can
be transmitted by the carrier.
digital network A telecommunication network where information is first converted into distinct
electronic pulses and then transmitted to a digital bit stream.
digital signal A signal in which information is represented by a limited number of discrete states
number of discrete states (for example, high and low voltages) rather than by fluctuating
levels in a continuous stream, as in an analog signal. In the pulse code modulation (PCM)
technology, the 8 kHz sampling frequency is used and a byte contains 8 bits in length.
Therefore, a digital signal is also referred to as a byte-based code stream. Digital signals,
with simple structures and broad bandwidth, are easy to shape or regenerate, and are not
easily affected by external interference.
digital subscriber line A technology for providing digital connections over the copper wire or the local
(DSL) telephone network. DSL performs data communication over the POTS lines without
affecting the POTS service.
digital subscriber line A network device, usually situated in the main office of a telephone company that
access multiplexer receives signals from multiple customer Digital Subscriber Line (DSL) connections and
(DSLAM) puts the signals on a high-speed backbone line using multiplexing techniques.
dispersion The dependence of refraction on the wavelength of light. Different wavelengths are
transmitted in an optical medium at different speeds. Wavelengths reach the end of the
medium at different times. As a result, the light pulse spreads and the dispersion occurs.
dispersion A module, which contains dispersion compensation fibers to compensate for the
compensation module dispersion of transmitting fiber.
(DCM)

distributed link A board-level port protection technology used to detect unidirectional fiber cuts and to
aggregation group negotiate with the opposite end. Once a link down failure occurs on a port or a hardware
(DLAG) failure occurs on a board, the services can automatically be switched to the slave board,
achieving 1+1 protection for the inter-board ports.
domain A logical subscriber group based on which the subscriber rights are controlled.
dotted decimal notation A format of IP address. IP addresses in this format are separated into four parts by a dot
"." with each part is in the decimal numeral.
download To obtain data from an upper-layer device or the server.
downstream In an access network, the direction of transmission toward the subscriber end of the link.
dual-ended switching A protection operation method which takes switching action at both ends of the protected
entity (for example, "connection", "path"), even in the case of a unidirectional failure.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-Aggr See Ethernet aggregation.
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
EA encryption algorithm
EBS See excess burst size.
ECC See embedded control channel.
EDFA See erbium-doped fiber amplifier.
EEPROM See electrically erasable programable read-only memory.
EF See expedited forwarding.
EFCI explicit forward congestion indication
EFM Ethernet in the First Mile
EFM OAM Ethernet in the first mile OAM
EIA See Electronic Industries Alliance.
EIR See excess information rate.
EMC See electromagnetic compatibility.
EMI See electromagnetic interference.
EMS element management system
EPD early packet discard
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
ERPS Ethernet ring protection switching
ESC See electric supervisory channel.
ESCON See enterprise system connection.

ESD electrostatic discharge

ESN See equipment serial number.
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVC Ethernet virtual connection
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
EXP See experimental bits.
Electronic Industries An association based in Washington, D.C., with members from various electronics
Alliance (EIA) manufacturers. It sets standards for electronic components. RS-232-C, for example, is
the EIA standard for connecting serial components.
EoD See Ethernet over dual domains.
Ethernet A LAN technology that uses Carrier Sense Multiple Access/Collision Detection. The
speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/
s. An Ethernet network features high reliability and is easy to maintain.
Ethernet aggregation A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
(E-Aggr) connection).
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
network (E-LAN) virtual connection).
Ethernet over dual A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet
domains (EoD) service transmission across PSN and TDM networks.
Ethernet private LAN A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
service (EPLAN) service is carried over a dedicated bridge and point-to-multipoint connections.
Ethernet private line A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
(EPL) connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
private LAN service service is carried over a shared bridge and point-to-multipoint connections.
(EVPLAN)
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
private line (EVPL) service is carried over a shared bridge and point-to-point connections.
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
(ETSI)
eSFP enhanced small form-factor pluggable
egress The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory A technology that implements communication among all the nodes and transmission of
channel (ESC) monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.

electrically erasable A type of EPROM that can be erased with an electrical signal. It is useful for stable
programable read-only storage for long periods without electricity while still allowing reprograming. EEPROMs
memory (EEPROM) contain less memory than RAM, take longer to reprogram, and can be reprogramed only
a limited number of times before wearing out.
electromagnetic A condition which prevails when telecommunications equipment is performing its
compatibility (EMC) individually designed function in a common electromagnetic environment without
causing or suffering unacceptable degradation due to unintentional electromagnetic
interference to or from other equipment in the same environment.
electromagnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
interference (EMI) limits the effective performance of electronics/electrical equipment.
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer,
channel (ECC) to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
emergency A type of measure taken to quickly rectify an emergency fault to recover the proper
maintenance running of the related system or device and to reduce losses.
encapsulation A technology for layered protocols, in which a lower-level protocol accepts a message
from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP inside
IP.
engineering label A mark on a cable, a subrack, or a cabinet for identification.
enterprise system A path protocol which connects the host with various control units in a storage system.
connection (ESCON) It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
entity A part, device, subsystem, functional unit, equipment, or system that can be considered
individually.
equalization A method of avoiding selective fading of frequencies. Equalization can compensate for
the changes of amplitude frequency caused by frequency selective fading.
equipment serial A string of characters that identify a piece of equipment and ensures correct allocation
number (ESN) of a license file to the specified equipment. It is also called "equipment fingerprint".
erbium-doped fiber An optical device that amplifies the optical signals. The device uses a short length of
amplifier (EDFA) optical fiber doped with the rare-earth element Erbium and the energy level jump of
Erbium ions activated by pump sources. When the amplifier passes the external light
source pump, it amplifies the optical signals in a specific wavelength range.
error tolerance The ability of a system or component to continue normal operation despite the presence
of erroneous inputs.
event Anything that takes place on the managed object. For example, the managed object is
added, deleted, or modified.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode, the
traffic control is achieved by the token buckets C and E. Excess burst size is a parameter
used to define the capacity of token bucket E, that is, the maximum burst IP packet size
when the information is transferred at the committed information rate. This parameter
must be larger than 0. It is recommended that this parameter should be not less than the
maximum length of the IP packet that might be forwarded.

excess information rate The bandwidth for excessive or burst traffic above the CIR; it equals the result of the
(EIR) actual transmission rate without the safety rate.
exercise switching An operation to check whether the protection switching protocol functions properly. The
protection switching is not really performed.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
(EF) demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
experimental bits A field in the MPLS packet header, three bits long. This field is always used to identify
(EXP) the CoS of the MPLS packet.
extended ID The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The physical ID of an NE is comprised of the NE ID and extended
ID.
external cable The cables and optical fibers which are used for connecting electrical interfaces and
optical interfaces of one cabinet to interfaces of other cabinets or peripherals.
external links The links between the current Web site and other Web sites. Generally, external links
refer to links from other Web sites to the current Web site.
extract To read the data required by the destination system from the source system.
F
F1 byte The user path byte, which is reserved for the user, but is typically special for network
providers. The F1 byte is mainly used to provide the temporary data or voice path for
special maintenance objectives. It belongs to the regenerator section overhead byte.
FAQ frequently asked question
FC See fiber channel.
FDB flash database
FDD See frequency division duplex.
FDDI See fiber distributed data interface.
FDI See forward defect indication.
FDI packet See forward defect indication packet.
FDV See frame delay variation.
FE See fast Ethernet.
FE port See fast Ethernet port.
FEC See forward error correction.
FFD fast failure detection
FFD packet A path failure detection method independent from CV. Different from a CV packet, the
frequency for generating FFD packets is configurable to satisfy different service
requirements. By default, the frequency is 20/s. An FFD packet contains information the
same as that in a CV packet. The destination end LSR processes FFD packets in the same
way for processing CV packets.
FICON See Fiber Connect.

FIFO first in first out queuing

FLR See frame loss ratio.
FPGA See field programmable gate array.
FPS See fast protection switching.
FR See frame relay.
FRU field replaceable unit
FTN FEC to NHLFE
FTP File Transfer Protocol
Fiber Connect A new generation connection protocol which connects the host to various control units.
(FICON) It carries single byte command protocol through the physical path of fiber channel, and
provides higher rate and better performance than ESCON.
fairness A feature in which for any link specified in a ring network, the source node is provided
with certain bandwidth capacities if the data packets transmitted by the source node are
constrained by the fairness algorithm.
fast Ethernet (FE) Any network that supports transmission rate of 100 Mbit/s. The Fast Ethernet is 10 times
faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so
on. Fast Ethernet is extended based on the IEEE802.3 standard, and it uses the following
three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),
100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical
fibers).
fast Ethernet port (FE The port that provides a rate of 100 Mbit/s.
port)
fast protection A type of pseudo wire automatic protection switching (PW APS). When the working
switching (FPS) PW is faulty, the source transmits services to the protection PW and the sink receives
the services from the protection PW. FPS generally works with the interworking function
(IWF) to provide end-to-end protection for services.
fault A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources or intentional settings.
fault alarm A type of alarm caused by hardware and/or software faults, for example, board failure,
or by the exception that occurs in major functions. After handling, a fault alarm can be
cleared, upon which the NE reports a recovery alarm. Fault alarms are of higher severity
than event alarms.
fault detection The process of determining that a fault has occurred.
fault notification A process wherein a fault is notified. For example, when a fault occurs on the local
interface, the local interface notifies the peer of the fault through OAMPDUs. The local
interface then records the fault in the log, and reports it to the NMS.
feeder 1. A radio frequency transmission line interconnecting an antenna and a transmitter or
receiver. 2. For an antenna comprising more than one driven element, a radio frequency
transmission Line interconnecting the antenna input and a driven element.

fiber channel (FC) A high-speed transport technology used to build storage area networks (SANs). Fiber
channel can be on the networks carrying ATM and IP traffic. It is primarily used for
transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode
and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair
copper wires and coaxial cables. Fiber channel provides both connection-oriented and
connectionless services.
fiber distributed data A standard developed by the American National Standards Institute (ANSI) for high-
interface (FDDI) speed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
fiber trough A trough that is used for routing fibers.
fiber/cable General name of optical fiber and cable. It refers to the physical entities that connect the
transmission equipment, carry transmission objects (user information and network
management information) and perform the transmission function in the transmission
network. The optical fiber transmits optical signal, while the cable transmits electrical
signal. The fiber/cable between NEs represents the optical fiber connection or cable
connection between NEs. The fiber/cable between SDH NEs represents the connection
relationship between NEs. At this time, the fiber/cable is of optical fiber type.
field programmable A type of semi-customized circuit used in the application specific integrated circuit
gate array (FPGA) (ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arrays.
firewall A combination of a series of components set between different networks or network
security domains. By monitoring, limiting, and changing the data traffic across the
firewall, it masks the interior information, structure and running state of the network as
much as possible to protect the network security.
fixed bandwidth The bandwidth that is fully reserved and is allocated periodically in a GPON system to
ensure the quality of cell transmission. If a T-CONT is provided with a fixed bandwidth
and does not transmit cells, the OLT can still allocate/assign the fixed bandwidth.
Therefore, idle cells are transmitted to the upstream OLT from the ONU/ONT.
flash memory A type of special electrically erasable programmable read-only memory (EEPROM) and
can be erased and rewritten in blocks at a time instead of only one byte. The data stored
in flash memory will not be lost if the flash memory is powered off.
flooding A type of incident, such as insertion of a large volume of data, that results in denial of
service.
flow An aggregation of packets that have the same characteristics. On the network
management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation.
flow queue The same type of services of a user is considered one service flow. HQoS performs queue
scheduling according to the services of each user. The service flows of each user are
classified into four FQs, namely, CS, EF, AF, and BE. CS is assigned a traffic shaping
percentage for Priority Queuing (PQ); EF, AF, and BE are assigned weights for Weighted
Fair Queuing (WFQ). The preceding two scheduling modes occupy a certain bandwidth
each; they can act at the same time without interfering each other.

forward defect A packet generated and traced forward to the sink node of the LSP by the node that first
indication (FDI) detects defects. It includes fields to indicate the nature of the defect and its location. Its
primary purpose is to suppress alarms being raised at affected higher level client LSPs
and (in turn) their client layers.
forward defect A packet that responds to the detected failure event. It is used to suppress alarms of the
indication packet (FDI upper layer network where failure has occurred.
packet)
forward error A bit error correction technology that adds the correction information to the payload at
correction (FEC) the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
fragmentation A process of breaking a packet into smaller units when transmitting over a network node
that does not support the original size of the packet.
frame delay variation A measurement of the variations in the frame delay between a pair of service frames,
(FDV) where the service frames belong to the same CoS instance on a point to point ETH
connection.
frame loss ratio (FLR) A ratio, is expressed as a percentage, of the number of service frames not delivered
divided by the total number of service frames during time interval T, where the number
of service frames not delivered is the difference between the number of service frames
arriving at the ingress ETH flow point and the number of service frames delivered at the
egress ETH flow point in a point-to-point ETH connection.
frame relay (FR) A packet-switching protocol used for WANs. Frame relay transmits variable-length
packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the sake
of speed.
free-run mode An operating condition of a clock, the output signal of which is strongly influenced by
the oscillating element and not controlled by servo phase-locking techniques. In this
mode the clock has never had a network reference input, or the clock has lost external
reference and has no access to stored data, that could be acquired from a previously
connected external reference. Free-run begins when the clock output no longer reflects
the influence of a connected external reference, or transition from it. Free-run terminates
when the clock output has achieved lock to an external reference.
frequency division An application in which channels are divided by frequency. In an FDD system, the uplink
duplex (FDD) and downlink use different frequencies. Downlink data is sent through bursts. Both
uplink and downlink transmission use frames with fixed time length.
full rate A type of data transmission rate. The service bandwidth can be 9.6 kbit/s, 4.8 kbit/s, or
2.4 kbit/s.
fully loaded A state that indicates that all slots of a piece of equipment are in use, that is, the equipment
has no vacant slots.
fuse A safety device that protects an electric circuit from excessive current, consisting of or
containing a metal element that melts when current exceeds a specific amperage, thereby
opening the circuit.
G
G-ACH generic associated channel header
GAL generic associated channel header label

GCC general communication channel

GCRA generic cell rate algorithm
GE See gigabit Ethernet.
GFC generic flow control
GFP See Generic Framing Procedure.
GNE See gateway network element.
GPS See Global Positioning System.
GRE See Generic Routing Encapsulation.
GSM See Global System for Mobile Communications.
GTS See generic traffic shaping.
GUI graphical user interface
Generic Framing A framing and encapsulation method which can be applied to any data type. It has been
Procedure (GFP) standardized by ITU-T SG15.
Generic Routing A mechanism for encapsulating any network layer protocol over any other network. GRE
Encapsulation (GRE) is used for encapsulating IP datagrams tunneled through the Internet. GRE serves as a
Layer 3 tunneling protocol and provides a tunnel for transparently transmitting data
packets.
Global Positioning A global navigation satellite system. It provides reliable positioning, navigation, and
System (GPS) timing services to worldwide users.
Global System for The second-generation mobile networking standard defined by European
Mobile Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for
Communications global mobile phone networks. The standard allows a subscriber to use a phone globally.
(GSM) GSM consists of three main parts: mobile switching subsystem (MSS), base station
subsystem (BSS), and mobile station (MS).
gain The difference between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
gateway A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway network A network element that is used for communication between the NE application layer and
element (GNE) the NM application layer.
general flow control A flow control that is applicable to the A interface, C/D interface, and trunks and can be
achieved by integrating multiple function modules. It is adopted when the traffic is heavy,
or location update and authentication of multiple subscribers are performed after the
system restarts. It can efficiently prevent system breakdown caused by link congestion
or CPU overload.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This is
(GTS) to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.

gigabit Ethernet (GE) A collection of technologies for transmitting Ethernet frames at a rate of a gigabit per
second, as defined by the IEEE 802.3z standard. GE is compatible with 10 Mbit/s and
100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and
it does not support coaxial cables or other cables. It also supports the channels in the
bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth
system with a bridge (switch) or a router as the center, it gives full play to the performance
and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that
are private, causing the length of the links to be sufficient for backbone applications in
a building and campus.
ground terminal A connection terminal on a communication device. It is used to connect the device with
ground cables, maintaining a tight connection between the device and the grounding
electrode.
H
HCS higher order connection supervision
HD-SDI See high definition-serial digital interface signal.
HDB3 high density bipolar of order 3 code
HDLC High-Level Data Link Control
HDTV See high definition television.
HEC See header error control.
HPA high order path adaptation
HPT higher order path termination
HQoS See hierarchical quality of service.
HSDPA See High Speed Downlink Packet Access.
HSI high-speed Internet
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
Packet Access for asymmetric uplink and downlink transmission of data services. It enables the
(HSDPA) maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
hang up A call processing mode used by an attendant to end the conversation with a user.
hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
header error control A field within the ATM frame whose purpose is to correct any single bit error in the cell
(HEC) Header and also to detect any multi-bit errors. It actually performs a CRC check in the
first four header bits and also at the receiving end.
hello packet The commonest packet which is periodically sent by a router to its neighbors. It contains
information about the DR, Backup Designated Router (BDR), known neighbors and
timer values.
hierarchical quality of A type of QoS that controls the traffic of users and performs the scheduling according
service (HQoS) to the priority of user services. HQoS has an advanced traffic statistics function, and the
administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth
can be allocated reasonably through traffic analysis.

high definition A type of TV that is capable of displaying at least 720 progressive or 1080 interlaced
television (HDTV) active scan lines. It must be capable of displaying a 16:9 image using at least 540
progressive or 810 interlaced active scan lines.
high definition-serial High definition video signal transported by serial digital interface.
digital interface signal
(HD-SDI)
historical performance The performance data that is stored in the history register or that is automatically reported
data and stored on the NMS.
hop A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.
hot patch A patch that is used to repair a deficiency in the software or add a new feature to a program
without restarting the software and interrupting the service. For the equipment using the
built-in system, a hot patch can be loaded, activated, confirmed, deactivated, deleted, or
queried.
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICC ITU carrier code
ICMP See Internet Control Message Protocol.
ICP IMA Control Protocol
IDU See indoor unit.
IEEE See Institute of Electrical and Electronics Engineers.
IETF See Internet Engineering Task Force.
IF See intermediate frequency.
IGMP See Internet Group Management Protocol.
IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented efficiently.
IGP See Interior Gateway Protocol.
ILM incoming label map
IMA See inverse multiplexing over ATM.
IMA frame A control unit in the IMA protocol. It is a logical frame defined as M consecutive cells,
numbered 0 to M-l, transmitted on each of the N links in an IMA group.
IP Internet Protocol
IP address A 32-bit (4-byte) binary digit that uniquely identifies a host (computer) connected to the
Internet for communication with other hosts in the Internet by transferring packets. An
IP address is expressed in dotted decimal notation, consisting of decimal values of its 4
bytes, separated by periods (,), for example, 127.0.0.1. The first three bytes of an IP
address identify the network to which the host is connected, and the last byte identifies
the host itself.

IPA See intelligent power adjustment.

IPTV See Internet Protocol television.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
IS-IS See Intermediate System to Intermediate System.
ISDN integrated services digital network
ISO International Organization for Standardization
ISP See Internet service provider.
IST internal spanning tree
ITC independent transmit clock
ITU See International Telecommunication Union.
ITU-T See International Telecommunication Union-Telecommunication Standardization
Sector.
IWF Interworking Function
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers (IEEE) electronics, computer engineering, and science-related matters.
Interior Gateway A routing protocol that is used within an autonomous system. The IGP runs in small-
Protocol (IGP) sized and medium-sized networks. The commonly used IGPs are the routing information
protocol (RIP), the interior gateway routing protocol (IGRP), the enhanced IGRP
(EIGRP), and the open shortest path first (OSPF).
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward
Intermediate System datagram or packets through a packet-based network.
(IS-IS)
International A United Nations agency, one of the most important and influential recommendation
Telecommunication bodies, responsible for recommending standards for telecommunication (ITU-T) and
Union (ITU) radio networks (ITU-R).
International An international body that develops worldwide standards for telecommunications
Telecommunication technologies. These standards are grouped together in series which are prefixed with a
Union- letter indicating the general subject and a number specifying the particular standard. For
Telecommunication example, X.25 comes from the "X" series which deals with data networks and open
Standardization Sector system communications and number "25" deals with packet switched networks.
(ITU-T)
Internet Assigned A department operated by the IAB. IANA delegates authority for IP address-space
Numbers Authority allocation and domain-name assignment to the NIC and other organizations. IANA also
(IANA) maintains a database of assigned protocol identifiers used in the TCP/IP suite, including
autonomous system numbers.
Internet Control A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
Message Protocol other information relevant to IP packet processing. For example, it can let the IP software
(ICMP) on one machine inform another machine about an unreachable destination. See also
communications protocol, IP, ISO/OSI reference model, packet (definition 1).

Internet Engineering A worldwide organization of individuals interested in networking and the Internet.
Task Force (IETF) Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with
studying technical problems facing the Internet and proposing solutions to the Internet
Architecture Board (IAB). The work of the IETF is carried out by various working groups
that concentrate on specific topics such as routing and security. The IETF is the publisher
of the specifications that led to the TCP/IP protocol standard.
Internet Group One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
Management Protocol groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
(IGMP) multicast group memberships.
Internet Protocol A system in which video is transmitted in IP packets. Also called "TV over IP", IPTV
television (IPTV) uses streaming video techniques to deliver scheduled TV programs or video-on-demand
(VOD). Unlike transmitting over the air or through cable to a TV set, IPTV uses the
transport protocol of the Internet for delivery and requires either a computer and software
media player or an IPTV set-top box to decode the images in real time.
Internet Protocol The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
version 4 (IPv4) assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol An update version of IPv4, which is designed by the Internet Engineering Task Force
version 6 (IPv6) (IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
Internet service An organization that offers users access to the Internet and related services.
provider (ISP)
inbound Data transmission from the external link to the router for the routers that support the
NetStream feature.
indicator Description of a performance feature collected from the managed devices by the
performance collector.
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
input jitter tolerance The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30-
second measurement intervals.
insertion loss The loss of power that results from inserting a component, such as a connector, coupler,
or splice, into a previously continuous path.
integrated circuit (IC) A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
intelligent power A mechanism used to reduce the optical power of all the amplifiers in an adjacent
adjustment (IPA) regeneration section in the upstream to a safety level if the system detects the loss of
optical signals on the link. If the fiber is broken, the device performance degrades, or the
connector is not plugged well, the loss of optical signals may occur. With IPA,
maintenance engineers will not be hurt by the laser sent out from the slice of broken
fiber.

interleaving A process of systematically changing the bit sequence of a digital signal, usually as part
of the channel coding, in order to reduce the influence of error bursts that may occur
during transmission.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF) signal.
inverse multiplexing A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a
over ATM (IMA) cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
J
jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
jumper A connection wire for connecting two pins.
K
K byte A general designation of K1 byte and K2 byte in the SDH.
L
L2 switching The switching based on the data link layer.
L2VPN Layer 2 virtual private network
LACP See Link Aggregation Control Protocol.
LACPDU Link Aggregation Control Protocol data unit
LAG See link aggregation group.
LAN See local area network.
LAPS Link Access Protocol-SDH
LB See loopback.
LBM See loopback message.
LBR See loopback reply.
LC Lucent connector
LCAS See link capacity adjustment scheme.
LCN local communications network
LCT local craft terminal
LDP Label Distribution Protocol
LED See light emitting diode.
LER See label edge router.
LIFO See last in first out.
LIU logical interface unit
LL logical link

LLC See logical link control.

LLID local loopback ID
LM See loss measurement.
LOC loss of continuity
LOM loss of multiframe
LOP loss of pointer
LOS See loss of signal.
LP lower order path
LPA low order path adaptation
LPT link-state pass through
LSP See label switched path.
LSR See label switching router.
LT linktrace
LTM See linktrace message.
LTR See linktrace reply.
LU line unit
Layer 2 switching A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch
transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switching.
Link Aggregation A method of bundling a group of physical interfaces together as a logical interface to
Control Protocol increase bandwidth and reliability. For related protocols and standards, refer to IEEE
(LACP) 802.3ad.
label A short identifier that is of fixed length and local significance. It is used to uniquely
identify the FEC to which a packet belongs. It does not contain topology information. It
is carried in the header of a packet and does not contain topology information.
label distribution Packets with the same destination address belong to an FEC. A label out of an MPLS
label resource pool is allocated to the FEC. LSRs record the relationship of the label and
the FEC. Then, LSRs sends a message and advertises to upstream LSRs about the label
and FEC relationship in message. The process is called label distribution.
label edge router (LER) A device that sits at the edge of an MPLS domain, that uses routing information to assign
labels to datagrams and then forwards them into the MPLS domain.
label space Value range of the label allocated to peers.
label switched path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label
(LSP) switching mechanisms. A label-switched path can be chosen dynamically, based on
common routing mechanisms or through configuration.
label switching router Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is
(LSR) composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.

laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
last in first out (LIFO) A play mode of the voice mails, the last voice mail is played firstly.
layer A concept used to allow the transport network functionality to be described hierarchically
as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
license A permission that the vendor provides for the user with a specific function, capacity, and
duration of a product. A license can be a file or a serial number. Usually the license
consists of encrypted codes. The operation authority granted varies with the level of the
license.
light emitting diode A display and lighting technology used in almost every electrical and electronic product
(LED) on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and
perimeter lighting. LEDs are also used as the light source in multimode fibers, optical
mice and laser-class printers.
line rate The maximum packet forwarding capacity on a cable. The value of line rate equals the
maximum transmission rate capable on a given type of media.
linear MSP linear multiplex section protection
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
(LAG) aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
adjustment scheme control mechanism to hitless increase or decrease the capacity of a link to meet the
(LCAS) bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the network and element management systems.
link monitoring A mechanism for an interface to notify the peer of the fault when the interface detects
that the number of errored frames, errored codes, or errored frame seconds reaches or
exceeds the specified threshold.
link protection Protection provided by the bypass tunnel for the link on the working tunnel. The link is
a downstream link adjacent to the point of local repair (PLR). When the PLR fails to
provide node protection, the link protection should be provided.
linktrace message The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.
(LTM) LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.
linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called LTR. LTR also includes the TTL that equals the result of the TTL of LTM minus
1.
load balancing The distribution of activity across two or more servers or components in order to avoid
overloading any one with too many requests or too much traffic.
load sharing A device running mode. Two or more hardware units can averagely share the system
load based on their processing capabilities when they are operating normally. When a
hardware unit fails, the other units fulfill the tasks of the faulty unit on the precondition
for guaranteeing system performance, for example, few call loss.

loading A process of importing information from the storage device to the memory to facilitate
processing (when the information is data) or execution (when the information is
program).
local MEP An MEP of a device on a network enabled with Ethernet CFM.
local area network A network formed by the computers and workstations within the coverage of a few square
(LAN) kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
logical interface An interface that does not exist physically and comes into being through configuration.
It can also exchange data.
logical link control According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper
(LLC) sublayer of the OSI data link layer. The LLC is the same for the various physical media
(such as Ethernet, token ring, WLAN).
loopback (LB) A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loopback message The loopback packet sent by the node that supports 802.2ag MAC Ping to the destination
(LBM) node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.2ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the LBM.
The LBR carries the sending time of LBM, the receiving time of LBM and the sending
time of LBR.
loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames
where the counters maintain a count of transmitted and received data frames between a
pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
low-pass filter A filter designed to transmit electromagnetic frequencies below a certain value, while
excluding those of a higher frequency.
lower subrack The subrack close to the bottom of the cabinet that contains several subracks.
lower threshold A lower performance limit which when exceeded by a performance event counter will
trigger a threshold-crossing event.
M
MA maintenance association
MAC See Media Access Control.
MAC address A link layer address or physical address. It is six bytes long.
MAC address aging A function that deletes MAC address entries of a device when no packets are received
from this device within a specified time period.
MADM multiple add/drop multiplexer
MAN See metropolitan area network.
MBS maximum burst size
MCF message communication function

MCR minimum cell rate

MD See maintenance domain.
MDP message dispatch process
ME See maintenance entity.
MEG maintenance entity group
MEL maintenance entity group level
MEP See maintenance entity group end point.
MFAS See multiframe alignment signal.
MIP See maintenance entity group intermediate point.
MLD See multicast listener discovery.
MP maintenance point
MPID maintenance point identification
MPLS See Multiprotocol Label Switching.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MPLS-TP See transport profile for multiprotocol label switching.
MS multiplex section
MSA multiplex section adaptation
MSB most significant bit
MSOH multiplex section overhead
MSP See multiplex section protection.
MST See multiplex section termination.
MST region See Multiple Spanning Tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTIE maximum time interval error
MTTR See mean time to repair.
MTU See maximum transmission unit.
MUX See multiplexer.

Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of the
(MAC) data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
Multicast Routing A protocol used to set up and maintain multicast routes, and to correctly and effectively
Protocol forward multicast packets. The multicast route is used to set up a loop-free transmission
path from the source to multiple receivers, that is, the multicast distribution tree.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol (MSTP) redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Multiple Spanning A region that consists of switches that support the MSTP in the LAN and links among
Tree region (MST them. Switches physically and directly connected and configured with the same MST
region) region attributes belong to the same MST region.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switching (MPLS) layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
main topology A basic component of a human-machine interface. It is the default client interface of the
NMS and intuitively displays the structure of a network, NEs on the network, subnets in
the network as well as the NE communication and running status, reflecting the overall
network running status.
maintenance domain The network or the part of the network for which connectivity is managed by connectivity
(MD) fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
maintenance entity An ME consists of a pair of maintenance entity group end points (MEPs), two ends of a
(ME) transport trail, and maintenance association intermediate points (MIPs) on the trail.
maintenance entity An end point of a MEG, which is able to initialize and stop the transmission of OAM
group end point (MEP) data packets for fault management and performance monitoring.
maintenance entity An intermediate point in a MEG, which is able to forward OAM packets and respond to
group intermediate some OAM packets, but unable to initiate the transmission of OAM packets or perform
point (MIP) any operations on network connections.
management The information that is used for network management in a transport network.
information

maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies,
unit (MTU) depending on the network—576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between The average time between consecutive failures of a piece of equipment. It is a measure
failures (MTBF) of the reliability of the system.
mean time to repair The average time that a device will take to recover from a failure.
(MTTR)
measurement period The interval for NEs to report measurement results to the Network Management System
(NMS).
medium A physical medium for storing computer information. A medium is used for data
duplication and keeping the data for some time. Original data can be obtained from a
medium.
member A basic element for forming a dimension according to the hierarchy of each level. Each
member represents a data element in a dimension. For example, January 1997 is a typical
member of the time dimension.
metropolitan area A network that interconnects users with computer resources in a geographic area or
network (MAN) region larger than that covered by even a large LAN but smaller than the area covered
by an WAN. The term is applied to the interconnection of networks in a city into a single
larger network (which may then also offer efficient connection to a wide area network).
It is also used to mean the interconnection of several local area networks by bridging
them with backbone lines. The latter usage is also sometimes referred to as a campus
network.
microwave The portion of the electromagnetic spectrum with much longer wavelengths than infrared
radiation, typically above about 1 mm.
mirroring The duplication of data for backup or to distribute network traffic among several
computers with identical data.
monitor link A port association solution developed as a supplementary to smart link.
monitoring A method that an inspector uses to inspect a service agent. By monitoring a service agent,
an inspector can check each detailed operation performed by the service agent during
the conversation and operate the GUI used by the service agent. The inspector helps the
service agent to provide better service.
mounting An auxiliary or associated condition or component of a device.
mounting ear A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
multicast A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.

multicast listener A protocol used by an IPv6 router to discover the multicast listeners on their directly
discovery (MLD) connected network segments, and to set up and maintain member relationships. On IPv6
networks, after MLD is configured on the receiver hosts and the multicast router to which
the hosts are directly connected, the hosts can dynamically join related groups and the
multicast router can manage members on the local network.
multiframe alignment A distinctive signal inserted in every multiframe or once in every n multiframes, always
signal (MFAS) occupying the same relative position within the multiframe, and used to establish and
maintain multiframe alignment.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a simply
instance (MSTI) and fully connected active topology for frames classified as belonging to a VLAN that
is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to
multiple MSTIs.
multiplex section A function, which is performed to provide capability for switching a signal between and
protection (MSP) including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplex section A function, which is performed to generate the MSOH during the process of forming an
termination (MST) SDH frame signal and terminates the MSOH in the reverse direction.
multiplexer (MUX) Equipment which combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate channels
being fixed.
multiplexing A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
multiprotocol label An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label
switching virtual switching (MPLS) technology. It applies the MPLS technology for network routers and
private network switches, simplifies the routing mode of core routers, and combines traditional routing
(MPLS VPN) technology and label switching technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NAS network access server
NC See NTP client.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NGN See next generation network.
NHLFE next hop label forwarding entry
NLP normal link pulse
NM network management
NMC network management center
NNI network-to-network interface
NP See network processor.

NPC See network parameter control.

NPE network provider edge
NRT-VBR non-real-time variable bit rate
NRZ non-return to zero
NRZ code non-return-to-zero code
NRZI non-return to zero inverted
NSAP See network service access point.
NSF non-stop forwarding
NTP Network Time Protocol
NTP client (NC) A bottom-level device in the time synchronization network. An NTP client obtains time
from its upper-level NTP server without providing the time synchronization service.
Compared with the top-level NTP server, the middle-level NTP server sometimes is
called an NTP client.
network layer Layer 3 of the seven-layer OSI model of computer networking. The network layer
provides routing and addressing so that two terminal systems are interconnected. In
addition, the network layer provides congestion control and traffic control. In the TCP/
IP protocol suite, the functions of the network layer are specified and implemented by
IP protocols. Therefore, the network layer is also called IP layer.
network parameter During communications, UPC is implemented to monitor the actual traffic on each virtual
control (NPC) circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
network processor (NP) An integrated circuit which has a feature set specifically targeted at the networking
application domain. Network Processors are typically software programmable devices
and would have generic characteristics similar to general purpose CPUs that are
commonly used in many different types of equipment and products.
network segment A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
network service A service that needs to be enabled at the network layer and maintained as a basic service.
network service access A network address defined by ISO, through which entities on the network layer can
point (NSAP) access OSI network services.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
next generation A packet-based network aimed to address requirement of various services. It adopts an
network (NGN) integrated and open network framework. In NGN, services are separated from call
control; call control is separated from bearer. In this way, services are independent of
network. NGN can provide various services, such as voice services, data services,
multimedia services or the integration of several services.

noise figure A measure of degradation of the signal-to-noise ratio (SNR), caused by components in
a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the output
noise power of a device to the portion thereof attributable to thermal noise in the input
termination at standard noise temperature T0 (usually 290 K). The noise figure is thus
the ratio of actual output noise to that which would remain if the device itself did not
introduce noise. It is a number by which the performance of a radio receiver can be
specified.
non-GNE See non-gateway network element.
non-gateway network A network element that communicates with the NM application layer through the
element (non-GNE) gateway NE application layer.
O
O&M operation and maintenance
OA optical amplifier
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
OAU See optical amplifier unit.
OC ordinary clock
OCP optical channel protection
OCS optical core switching
ODF optical distribution frame
ODU See outdoor unit.
OFS out-of-frame second
OHA overhead access
OHP overhead processing
OLT optical line terminal
ONU See optical network unit.
OPEX operating expense
OPU optical channel payload unit
OSC See optical supervisory channel.
OSI See open systems interconnection.
OSN optical switch node
OSNR See optical signal-to-noise ratio.
OSPF See Open Shortest Path First.
OTDR See optical time domain reflectometer.
OTM optical terminal multiplexer
OTN optical transport network

OTU See optical transponder unit.

OTUk optical channel transport unit-k
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
First (OSPF) algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed with the network topology which is identical on all
routers in the area.
offline Pertaining to the disconnection between a device or a service unit and the system or the
network, or no running of a device and service unit.
online A state indicating that a computer device or program is activated and is ready for
operations, and can communicate with a computer or can be controlled by the computer.
open systems A framework of ISO standards for communication between different systems made by
interconnection (OSI) different vendors, in which the communications process is organized into seven different
categories that are placed in a layered sequence based on their relationship to the user.
Each layer uses the layer immediately below it and provides a service to the layer above.
Layers 7 through 4 deal with end-to-end communication between the message source
and destination, and layers 3 through 1 deal with network functions.
operation, A group of network support functions that monitor and sustain segment operation,
administration and activities that are concerned with, but not limited to, failure detection, notification,
maintenance (OAM) location, and repairs that are intended to eliminate faults and keep a segment in an
operational state and support activities required to provide the services of a subscriber
access network to users/subscribers.
optical add/drop A device that can be used to add the optical signals of various wavelengths to one channel
multiplexer (OADM) and drop the optical signals of various wavelengths from one channel.
optical amplifier unit A board that is mainly responsible for amplifying optical signals. The OAU can be used
(OAU) in both the transmitting direction and the receiving direction.
optical attenuator A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
optical connector A component normally attached to an optical cable or a piece of apparatus to provide
frequent optical interconnection/disconnection of optical fibers or cables.
optical fiber A thin filament of glass or other transparent material, through which a signal-encoded
light beam may be transmitted using total internal reflection.
optical interface A component that connects several transmit or receive units.
optical network unit A form of Access Node that converts optical signals transmitted via fiber to electrical
(ONU) signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise The ratio of signal power and noise power in a transmission link. OSNR is the most
ratio (OSNR) important index of measuring the performance of a DWDM system. OSNR = signal
power/noise power.
optical splitter A passive component, which is used for splitting and sending optical power to multiple
ONUs connected by an optical fiber. In a GPON system that consists of the OLT, ONU,
splitter, and optical fibers, according to the split ratio, the optical signal over the optical
fiber connected to the OLT is splitted into multiple channels of optical signals and send
each channel to each ONU. Split ratio determines how many channels of optical signals
an optical fiber can be split to.

optical supervisory A technology that uses specific optical wavelengths to realize communication among
channel (OSC) nodes in optical transmission network and transmit the monitoring data in a certain
channel.
optical time domain A device that sends a very short pulse of light down a fiber optic communication system
reflectometer (OTDR) and measures the time history of the pulse reflection to measure the fiber length, the light
loss and locate the fiber fault.
optical transponder A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2-
unit (OTU) compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
outdoor unit (ODU) The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for radio frequency (RF) signals.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PA power amplifier
PADR PPPoe active discovery request
PBS See peak burst size.
PCB See printed circuit board.
PCM See pulse code modulation.
PCR See peak cell rate.
PCS physical coding sublayer
PDH See plesiochronous digital hierarchy.
PDU See power distribution unit.
PE See provider edge.
PGND cable A cable which connects the equipment and the protection grounding bar. Usually, one
half of the cable is yellow, whereas the other half is green.
PHB See per-hop behavior.
PIM-DM Protocol Independent Multicast - Dense Mode
PIM-SM Protocol Independent Multicast - Sparse Mode
PKT partition knowledge table
PLL See phase-locked loop.
PM performance monitoring
PMD polarization mode dispersion
POH path overhead
POS See packet over SDH/SONET.
PPD partial packet discard

PPI PDH physical interface

PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PPS port protection switching
PQ See priority queuing.
PRBS See pseudo random binary sequence.
PRC primary reference clock
PSD See power spectrum density.
PSN See packet switched network.
PSTN See public switched telephone network.
PSU power supply unit
PT payload type
PTI payload type indicator
PTN packet transport network
PTP Precision Time Protocol
PVC permanent virtual channel
PVID See port default VLAN ID.
PVP See permanent virtual path.
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
packet discarding A function of discarding the packets from unknown VLAN domain or broadcast packets.
Packet Discarding is used to prevent the situation where unknown packets or broadcast
packets use the bandwidth on a link, improving the reliability of service transmission.
packet forwarding An action performed by a router to forward a received datagram, where the destination
IP address does not match the IP address of the router, to another router or destination
host on the router list.
packet loss The discarding of data packets in a network when a device is overloaded and cannot
accept any incoming data at a given moment.
packet over SDH/ A MAN and WAN technology that provides point-to-point data connections. The POS
SONET (POS) interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
packet rate The number of bits or bytes passed within a specified time. It is expressed in bits/s or
bytes/s.
packet switched A telecommunications network that works in packet switching mode.
network (PSN)
packet switching A network technology in which information is transmitted by means of exchanging
packets and the bandwidth of a channel can be shared by multiple connections.
paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.

parity bit A check bit appended to an array of binary digits to make the sum of all the binary digits,
including the check bit, always odd or always even.
parity check A method for character level error detection. An extra bit is added to a string of bits,
usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or
even parity). Both ends of a data transmission must use the same parity. When the
transmitting device frames a character, it counts the numbers of 1s in the frame and
attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity error,
may ask for the data to be retransmitted.
parts replacement A maintenance operation of removing a faulty part or a part to be examined from a
running device and then installing a new part.
passive mode A working mode of EFM OAM. An interface in the passive mode cannot initiate the
discovery and remote loopback.
patch An independent software unit used for fixing the bugs in software.
peak burst size (PBS) A parameter that is used to define the capacity of token bucket P, that is, the maximum
burst IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that PBS should be not less than the
maximum length of the IP packet that might be forwarded. See also CIR, CBS, and PIR.
peak cell rate (PCR) The maximum rate at which an ATM connection can accept cells.
peer BGP speakers that exchange information with each other.
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
(PHB) behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
performance alarm An alarm generated when the actual result of a measurement entity equals the predefined
logical expression for threshold or exceeds the predefined threshold.
performance The performance parameters identify some indexes to scale the general performance of
parameters the system. The indexes include the number of managed nodes, number of supported
clients and log database capacity. The parameters are sorted into static parameters,
dynamic parameters and networking bandwidth parameters.
performance register The memory space for performance event counts, including 15-min current performance
register, 24-hour current performance register, 15-min historical performance register,
24-hour historical performance register, UAT register and CSES register. The object of
performance event monitoring is the board functional module, so every board functional
module has a performance register. A performance register is used to count the
performance events taking place within a period of operation time, so as to evaluate the
quality of operation from the angle of statistics.
performance threshold A limit for generating an alarm for a selected entity. When the measurement result
reaches or exceeds the preset alarm threshold, the performance management system
generates a performance alarm.
permanent virtual path Virtual path that consists of PVCs.
(PVP)
phase The relative position in time within a single period of a signal.

phase-locked loop A circuit that consists essentially of a phase detector which compares the frequency of
(PLL) a voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator; the output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
physical layer Layer 1 in the Open System Interconnection (OSI) architecture; the layer that provides
services to transmit bits or groups of bits over a transmission link between open systems
and which entails electrical, mechanical and handshaking.
physical link The link between two physical network elements (NEs). When the user creates NEs or
refreshes the device status, the system automatically creates the physical link according
to the topology structure information on the device. The remark information of a physical
link can be modified, but the physical link cannot be deleted.
ping A method used to test whether a device in the IP network is reachable according to the
sent ICMP Echo messages and received response messages.
ping test A test that is performed to send a data packet to the target IP address (a unique IP address
on the device on the network) to check whether the target host exists according to the
data packet of the same size returned from the target host.
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
hierarchy (PDH) rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
point-to-point service A service between two terminal users. In P2P services, senders and recipients are
(P2P) terminal users.
pointer An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which this pointer is supported.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
policy A set of rules that are applied when the conditions for triggering an event are met.
policy template A template that is used to define the calculation rules of a charging event, for example,
rating, debiting and accumulating. A policy template may contain the parameters to be
instantiated. They can be used when the attributes of the condition judgment, calculation
method, and action functions are carried out.
polling A mechanism for the NMS to query the agent status and other data on a regular basis.
port default VLAN ID A default VLAN ID of a port. It is allocated to a data frame if the data frame carries no
(PVID) VLAN tag when reaching the port.
port priority The priority that is used when a port attaches tags to Layer 2 packets. Packets received
on ports with higher priorities are forwarded preferentially.
power adjustment A method for dynamically and properly assigning power according to the real-time status
of a wireless network. When an AP runs under an AC for the first time, the AP uses its
maximum transmit power. When getting reports from its neighbors (that is, other APs
that are detected by the AP and managed by the same AC), the AP determines to increase
or decrease its power according to the report conclusion.

power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
power control A process in which the MS or BS uses certain rules to adjust and control the transmit
power according to the change in the channel condition and the power of the received
signal.
power distribution unit A unit that performs AC or DC power distribution.
(PDU)
power module A module that provides power supply to other boards or modules.
power off An operation that switches off devices during upgrade or expansion.
power on To start up a computer; to begin a cold boot procedure; to turn on the power
power spectrum The power layout of random signals in the frequency domain.
density (PSD)
printed circuit board A board used to mechanically support and electrically connect electronic components
(PCB) using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
priority queuing (PQ) A queue scheduling algorithm based on the absolute priority. According to the PQ
algorithm, services of higher priorities are ensured with greater bandwidth, lower
latency, and less jitter. Packets of lower priorities must wait to be sent till all packets of
higher priorities are sent. In this manner, services of higher priorities are processed earlier
than others.
private line A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
protection path A specific path that is part of a protection group and is labeled protection.
provider edge (PE) A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the
sequence (PRBS) values of any of the other elements, similar to real random sequences.
pseudo wire (PW) An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
edge-to-edge (PWE3) telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
public switched A telecommunications network established to perform telephone services for the public
telephone network subscribers. Sometimes it is called POTS.
(PSTN)
pulse A variation above or below a normal level and a given duration in electrical energy.

pulse code modulation A method of encoding information in a signal by changing the amplitude of pulses.
(PCM) Unlike pulse amplitude modulation (PAM), in which pulse amplitude can change
continuously, pulse code modulation limits pulse amplitudes to several predefined
values. Because the signal is discrete, or digital, rather than analog, pulse code
modulation is more immune to noise than PAM.
Q
QA Q adaptation
QAM See quadrature amplitude modulation.
QPSK See quadrature phase shift keying.
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It add a public VLAN
tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to
be transmitted over the service provider's backbone network based on the public VLAN
tag. This provides a layer 2 VPN tunnel for customers and enables transparent
transmission of packets over private VLANs.
QoS See quality of service.
quadrature amplitude Both an analog and a digital modulation scheme. It conveys two analog message signals,
modulation (QAM) or two digital bit streams, by changing (modulating) the amplitudes of two carrier waves,
using the amplitude-shift keying (ASK) digital modulation scheme or amplitude
modulation (AM) analog modulation scheme. These two waves, usually sinusoids, are
out of phase with each other by 90° and are thus called quadrature carriers or quadrature
components — hence the name of the scheme.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK) the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform two-
bit coding and display the codes in Gray code on graph with the minimum BER.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS See Remote Authentication Dial-In User Service.
RAI remote alarm indication
RDI remote defect indication
RED See random early detection.
REG See regenerator.
REI remote error indication
RF See radio frequency.
RIP See Routing Information Protocol.
RMEP remote maintenance association end point

RNC See radio network controller.

ROPA See remote optical pumping amplifier.
RP rendezvous point
RPR resilient packet ring
RS232 A asynchronous transfer mode that does not involve hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RS422 The specification that defines the electrical characteristics of balanced voltage digital
interface circuits. The interface can change to RS232 via the hardware jumper and others
are the same as RS232.
RSL See received signal level.
RSOH regenerator section overhead
RSSI See received signal strength indicator.
RST regenerator section termination
RSTP See Rapid Spanning Tree Protocol.
RTN radio transmission node
RTP See Real-Time Transport Protocol.
Rapid Spanning Tree An evolution of the Spanning Tree Protocol, providing for faster spanning tree
Protocol (RSTP) convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Real-Time Transport A type of host-to-host protocol used in real-time multimedia services such as Voice over
Protocol (RTP) IP (VoIP) and video.
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial-In User Service access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
(RADIUS) transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
RoHS restriction of the use of certain hazardous substances
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
Protocol (RIP) based on the smallest hop count between source and destination. RIP is a distance vector
protocol that routinely broadcasts routing information to its neighboring routers and is
known to waste bandwidth.
radio frequency (RF) A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network A piece of equipment in the RNS which is in charge of controlling the use and the integrity
controller (RNC) of the radio resources.
radio propagation An empirical mathematical formulation for the characterization of radio wave
model propagation as a function of frequency, distance and other conditions. A single model is
usually developed to predict the behavior of propagation for all similar links under
similar constraints.

random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED) to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulting from traditional tail drop can be prevented.
rate limiting A traffic management technology used to limit the total rate of packet sending on a
physical interface or a Tunnel interface. Rate limiting is directly enabled on the interface
to control the traffic passing the interface.
real-time variable bit A parameter intended for real-time applications, such as compressed voice over IP
rate (rt-VBR) (VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR),
sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source
device to transmit in bursts and at a rate that varies with time.
reboot To start the system again. Programs or data will be reloaded to all boards.
received signal level The signal level at a receiver input terminal.
(RSL)
received signal strength The received wide band power, including thermal noise and noise generated in the
indicator (RSSI) receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
receiver sensitivity The minimum acceptable value of average received power at point R to achieve a 1 x
10-12 BER (The FEC is open).
recognition Consumer awareness of having seen or heard an advertising message.
reference clock A kind of stable and high-precision autonous clock providing frequencies for other clocks
for reference.
reflectance The ratio of the reflected optical power to the incident optical power.
regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
regenerator (REG) A piece of equipment or device that regenerates electrical signals.
relay An electronic control device that has a control system and a system to be controlled. The
relay of the telepresence system is used to control the power of telepresence equipment
and is controlled by the telepresence host.
remote optical A remote optical amplifier subsystem designed for applications where power supply and
pumping amplifier monitoring systems are unavailable. The ROPA subsystem is a power compensation
(ROPA) solution to the ultra-long distance long hop (LHP) transmission.
reservation An action that the charging module performs to freeze a subscriber's balance amount,
free resources, credits, or quotas before the subscriber uses services. This action ensures
that the subscriber has sufficient balance to pay for services.
resistance The ability to impede (resist) the flow of electric current. With the exception of
superconductors, all substances have a greater or lesser degree of resistance. Substances
with very low resistance, such as metals, conduct electricity well and are called
conductors. Substances with very high resistance, such as glass and rubber, conduct
electricity poorly and are called nonconductors or insulators.
resource sharing A physical resource belonging to two or more protection subnetworks.
response A message that is returned to the requester to notify the requester of the status of the
request packet.
robustness The ability of a system to maintain function even with changes in internal structure or
external environment.

rollback A return to a previous condition through cancellation of a certain operation.

root alarm An alarm directly caused by anomaly events or faults in the network. Some lower-level
alarms always accompany a root alarm.
route The path that network traffic takes from its source to its destination. In a TCP/IP network,
each IP packet is routed independently. Routes can change dynamically.
router A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
routing The determination of a path that a data unit (frame, packet, message) traverses from
source to destination.
routing protocol A formula used by routers to determine the appropriate path onto which data should be
forwarded.
rt-VBR See real-time variable bit rate.
S
S1 byte A byte to transmit network synchronization status information. On an SDH network,
each NE traces hop by hop to the same clock reference source through a specific clock
synchronization path, realizing synchronization on the entire network. If a clock
reference source traced by an NE is missing, this NE will trace another clock reference
source of a lower level. To implement protection switching of clocks in the whole
network, the NE must learn about clock quality information of the clock reference source
it traces. Therefore, ITU-T defines S1 byte to transmit network synchronization status
information. It uses the lower four bits of the multiplex section overhead S1 byte to
indicate 16 types of synchronization quality grades. Auto protection switching of clocks
in a synchronous network can be implemented using S1 byte and a proper switching
protocol.
SAN storage area network
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SC square connector
SCR sustainable cell rate
SD See signal degrade.
SD trigger flag A signal degrade trigger flag that determines whether to perform a switching when SD
occurs. The SD trigger flag can be set by using the network management system.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDP serious disturbance period
SDRAM See synchronous dynamic random access memory.
SELV safety extra-low voltage
SEMF synchronous equipment management function
SES severely errored second

SETS SDH equipment timing source

SF See signal fail.
SFP small form-factor pluggable
SFTP See Secure File Transfer Protocol.
SHDSL See single-pair high-speed digital subscriber line.
SMSR side mode suppression ratio
SNC subnetwork connection
SNCMP subnetwork connection multipath protection
SNCP subnetwork connection protection
SNCTP subnetwork connection tunnel protection
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.
SOH section overhead
SONET See synchronous optical network.
SPE See superstratum provider edge.
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
SSMB synchronization status message byte
SSU synchronization supply unit
STD system target decoder
STP Spanning Tree Protocol
SVC switched virtual connection
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol (SFTP)
Secure Sockets Layer A security protocol that works at a socket level. This layer exists between the TCP layer
(SSL) and the application layer to encrypt/decode data and authenticate concerned entities.
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
(SNMP) transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message (SSM) Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.

security Protection of a computer system and its data from harm or loss. A major focus of
computer security, especially on systems accessed by many people or through
communication lines, is preventing system access by unauthorized individuals.
security service A service, provided by a layer of communicating open systems, which ensures adequate
security of the systems or of data transfer.
self-healing A function of establishing a replacement connection by network without the network
management connection function. When a connection failure occurs, the replacement
connection is found by the network elements and rerouted depending on network
resources available at that time.
serial port An input/output location (channel) that sends and receives data to and from a computer's
CPU or a communications device one bit at a time. Serial ports are used for serial data
communication and as interfaces with some peripheral devices, such as mice and printers.
service flow An MAC-layer-based unidirectional transmission service. It is used to transmit data
packets, and is characterized by a set of QoS parameters, such as latency, jitter, and
throughput.
service level The level of service quality of an evaluated party in a specified period, determined by
an evaluating party.
service protection A measure that ensures that services can be received at the receive end.
session A logical connection between two nodes on a network for the exchange of data. It
generally can apply to any link between any two data devices. A session is also used
simply to describe the connection time.
shaping A process of delaying packets within a traffic stream to cause it to conform to specific
defined traffic profile.
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded defect
condition is active.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB (Decibel).
signaling The information exchange concerning the establishment and control of a
telecommunication circuit and the management of the network.
single-ended switching A protection operation method that takes switching action only at the affected end of the
protected entity (for example, trail, subnetwork connection), in the case of a
unidirectional failure.
single-pair high-speed A symmetric digital subscriber line technology developed from HDSL, SDSL, and
digital subscriber line HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
(SHDSL) terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
single-polarized An antenna intended to radiate or receive radio waves with only one specified
antenna polarization.
slicing Dividing data into the information units proper for transmission.
smooth upgrade Process of upgrading the system files without service interruption

span The physical reach between two pieces of WDM equipment. The number of spans
determines the signal transmission distance supported by a piece of equipment and varies
according to transmission system type.
standard definition- Standard definition video signal transported by serial digital interface.
serial digital interface
signal (SD-SDI)
static ARP A protocol that binds some IP addresses to a specified gateway. The packet of these IP
addresses must be forwarded through this gateway.
static route A route that cannot adapt to the change of network topology. Operators must configure
it manually. When a network topology is simple, the network can work in the normal
state if only the static route is configured. It can improve network performance and ensure
bandwidth for important applications. Its disadvantage is as follows: When a network is
faulty or the topology changes, the static route does not change automatically. It must
be changed by the operators.
statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be
transmitted across a single physical channel. It dynamically allocates bandwidth only to
active input channels, to make better use of available bandwidth and allow more devices
to be connected than with other multiplexing techniques.
steering A protection switching mode defined in ITU-T G.8132, which is applicable to packet-
based T-MPLS ring networks and similar to SDH transoceanic multiplex section
protection (MSP). In this mode, the switching is triggered by the source and sink nodes
of a service.
stress The force, or combination of forces, which produces a strain; force exerted in any
direction or manner between contiguous bodies, or parts of bodies, and taking specific
names according to its direction, or mode of action, as thrust or pressure, pull or tension,
shear or tangential stress.
subnet A type of smaller networks that form a larger network according to a rule, for example,
according to different districts. This facilitates the management of the large network.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router matches with the IP address.
superstratum provider Core devices that are located within a VPLS full-meshed network. The UPE devices that
edge (SPE) are connected with the SPE devices are similar to the CE devices. The PWs set up
between the UPE devices and the SPE devices serve as the ACs of the SPE devices. The
SPE devices must learn the MAC addresses of all the sites on UPE side and those of the
UPE interfaces that are connected with the SPE. SPE is sometimes called NPE.
suppress To forbid the printing of the paper bill of an account that meets certain conditions during
the bill run.
suspension A specific state in the life cycle of a subscriber. A subscriber in this state can neither
make calls nor receive calls.
switching capacity The backplane bandwidth or switching bandwidth. The switching capacity is the
maximum data that can be processed by the interface processor of a switch and the data
bus. The backplane bandwidth indicates the overall data switching capability of a switch,
in Gbit/s.

switching priority A priority of a board that is defined for protection switching. When several protected
boards need to be switched, a switching priority should be set for each board. If the
switching priorities of the boards are the same, services on the board that fails later cannot
be switched. Services on the board with higher priority can preempt the switching
resources of that with lower priority.
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
hierarchy (SDH) transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is used only for signals. SDH is suitable
for the fiber communication system with high speed and a large capacity since it uses
synchronous multiplexing and flexible mapping structure.
synchronous dynamic A new type of DRAM that can run at much higher clock speeds than conventional
random access memory memory. SDRAM actually synchronizes itself with the CPU's bus and is capable of
(SDRAM) running at 100 MHz, about three times faster than conventional FPM RAM, and about
twice as fast as EDO DRAM or BEDO DRAM. SDRAM is replacing EDO DRAM in
computers.
synchronous optical A high-speed network that provides a standard interface for communications carriers to
network (SONET) connect networks based on fiber optical cable. SONET is designed to handle multiple
data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbit/s, but
multiples of this base rate go as high as 2.488 Gbit/s.
T
TCI tag control information
TCM tandem connection monitor
TCN topology change notification
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TDC tunable dispersion compensator
TDM See time division multiplexing.
TE terminal equipment
TFTP See Trivial File Transfer Protocol.
TIM trace identifier mismatch
TLV See type-length-value.
TM See terminal multiplexer.
TMN See telecommunications management network.
TOD time of day
TPID tag protocol identifier
TPS See tributary protection switching.

TPS protection The equipment level protection that uses one standby tributary board to protect N
tributary boards. When a fault occurs on the working board, the SCC issues the switching
command, and the payload of the working board can be automatically switched over to
the specified protection board and the protection board takes over as the working board.
After the fault is rectified, the service is automatically switched to the original board.
TSD trail signal degrade
TTI trail trace identifier
TTL See time to live.
TTSI See trail termination source identifier.
TU tributary unit
TU-LOP tributary unit loss of pointer
TUG tributary unit group
Tc committed rate measurement interval
Telnet A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users
to log in to remote systems and use resources as if they were connected to a local system.
Telnet is defined in RFC 854.
ToS type of service
Transmission Control The protocol within TCP/IP that governs the breakup of data messages into packets to
Protocol (TCP) be sent using Internet Protocol (IP), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
Trivial File Transfer A small and simple alternative to FTP for transferring files. TFTP is intended for
Protocol (TFTP) applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication. TFTP is
small enough to be contained in ROM to be used for bootstrapping diskless machines.
tail drop A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
tangent ring A concept borrowed from geometry. Two tangent rings have a common node between
them. The common node often leads to single-point failures.
telecommunications A protocol model defined by ITU-T for managing open systems in a communications
management network network. An architecture for management, including planning, provisioning, installation,
(TMN) maintenance, operation and administration of telecommunications equipment, networks
and services.
terminal multiplexer A device used at a network terminal to multiplex multiple channels of low rate signals
(TM) into one channel of high rate signals, or to demultiplex one channel of high rate signals
into multiple channels of low rate signals.
threshold An amount, limit or level on a scale. Changes will occur with a threshold reached.
threshold alarm The alarm occurs when the monitored value exceeds the threshold.
threshold crossing An alarm generated when a threshold is crossed.
alarm

throughput The maximum transmission rate of the tested object (system, equipment, connection,
service type) when no packet is discarded. Throughput can be measured with bandwidth.
throughput capability The data input/output capability of the data transmission interface.
time division A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
multiplexing (TDM) (TSn, n=0, 1, 2, 3…), and the sampling value codes of multiple signals engross time slots
in a certain order, forming multiple multiplexing digital signals to be transmitted over
one channel.
time to live (TTL) A technique used in best-effort delivery systems to prevent packets that loop endlessly.
The TTL is set by the sender to the maximum time the packet is allowed to be in the
network. Each router in the network decrements the TTL value when the packet arrives,
and discards any packet if the TTL counter reaches zero.
timer Symbolic representation for a timer object (for example, a timer object may have a
primitive designated as T-Start Request). Various MAC entities utilize timer entities that
provide triggers for certain MAC state transitions.
timestamp The current time of an event that is recorded by a computer. By using mechanisms such
as the Network Time Protocol (NTP), a computer maintains accurate current time,
calibrated to minute fractions of a second.
token bucket algorithm The token bucket is a container for tokens. The capacity of a token bucket is limited, and
the number of tokens determines the traffic rate of permitted packets. The token bucket
polices the traffic. Users place the tokens into the bucket regularly according to the preset
rate. If the tokens in the bucket exceed the capacity, no tokens can be put in. Packets can
be forwarded when the bucket has tokens, otherwise they cannot be transferred till there
are new tokens in the bucket. This scheme adjusts the rate of packet input.
topology The configuration or layout of a network formed by the connections between devices on
a local area network (LAN) or between two or more LANs.
topology discovery A technique to accurately determine the exact layout of a network using a few
assumptions about the network architecture and simple tools.
trTCM See two rate three color marker.
traceroute A program that prints the path to a destination. Traceroute sends a sequence of datagrams
with the time-to-live (TTL) set to 1,2, and so on, and uses ICMP time exceeded messages
that return to determine routers along the path.
traffic The product of the number of calls made and received and the average duration of each
call in a measurement period.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the entire
network. In this way, different traffic packets can be treated differently.
traffic policy A full set of QoS policies formed by association of traffic classification and QoS actions.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in the
scenario that the traffic matches network resources provided by the lower layer devices,
avoiding packet loss and congestion.

traffic statistics An activity of measuring and collecting statistics of various data on devices and
telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks. The
statistics also help the operators manage the device operating, locate problems, monitor
and maintain the networks, and plan the networks.
trail management A network level management function of the network management system. This function
function enables you to configure end-to-end services, view graphic interface and visual routes
of a trail, query detailed information of a trail, filter, search and locate a trail quickly,
manage and maintain trails in a centralized manner, manage alarms and performance
data by trail, and print a trail report.
trail termination source A TTSI uniquely identifies an LSP in the network. A TTSI is carried in the connectivity
identifier (TTSI) verification (CV) packet for checking the connectivity of a trail. If it matches the TTSI
received by the sink point, the trail has no connectivity defect.
transaction A business between a carrier and customer, such as payment and account adjustment.
transfer A process of transferring the account balance of an account to another account.
transit A packet is transmitted along an LSP consisting of a series of LSRs after the packet is
labeled. The intermediate nodes are named transits.
transit node All the nodes except the master node on an RRPP ring.
transmission delay The period from the time when a site starts to transmit a data frame to the time when the
site finishes the data frame transmission. It consists of the transmission latency and the
equipment forwarding latency.
transmit power control A technical mechanism used within some networking devices in order to prevent too
much unwanted interference between different wireless networks.
transparent A process during which the signaling protocol or data is not processed in the content but
transmission encapsulated in the format for the processing of the next phase.
transport profile for MPLS-TP is an extension to MPLS in terms of forwarding, OAM, reliability, NMS and
multiprotocol label control plane protocol standardized by IETF to provide sufficient transport functionality.
switching (MPLS-TP)
tray A component that can be installed in the cabinet for holding chassis or other devices.
tributary loopback A fault can be located for each service path by performing loopback to each path of the
tributary board. There are three kinds of loopback modes: no loopback, outloop, and
inloop.
tributary protection A function that uses a standby tributary processing board to protect N tributary
switching (TPS) processing boards.
trunk Physical communications line between two offices. It transports media signals such as
speech, data and video signals.
trunk link A link used to transport VLAN communication between two switches.
trunk port A switch port used to connect to other switches. The trunk port can connect to only the
trunk link. Only VLANs allowed to pass through a trunk port can be configured on the
trunk port.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.

tunnel ID A group of information, including the token, slot number of an outgoing interface, tunnel
type, and location method.
twisted pair cable A type of cable that consists of two independently insulated wires twisted around one
another for the purposes of canceling out electromagnetic interference which can cause
crosstalk. The number of twists per meter makes up part of the specifications for a given
type of cable. The greater the number of twists is, the more crosstalk is reduced.
two rate three color An algorithm that meters an IP packet stream and marks its packets based on two rates,
marker (trTCM) Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it
exceeds or does not exceed the CIR.
type-length-value An encoding type that features high efficiency and expansibility. It is also called Code-
(TLV) Length-Value (CLV). T indicates that different types can be defined through different
values. L indicates the total length of the value field. V indicates the actual data of the
TLV and is most important. TLV encoding features high expansibility. New TLVs can
be added to support new features, which is flexible in describing information loaded in
packets.
U
UART universal asynchronous receiver/transmitter
UAS unavailable second
UAT See unavailable time event.
UBR unspecified bit rate
UBR+ Unspecified Bit Rate Plus
UDP See User Datagram Protocol.
UNI See user-to-network interface.
UPC See usage parameter control.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
UPS uninterruptible power supply
UTC See Coordinated Universal Time.
User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol (UDP) datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagram. UDP provides application programs with the unreliable
connectionless packet delivery service. There is a possibility that UDP messages will be
lost, duplicated, delayed, or delivered out of order. The destination device does not
confirm whether a data packet is received.
unavailable time event An event that is reported when the monitored object generates 10 consecutive severely
(UAT) errored seconds (SES) and the SESs begin to be included in the unavailable time. The
event will end when the bit error ratio per second is better than 10-3 within 10 consecutive
seconds.
unicast The process of sending data from a source to a single recipient.

unknown multicast A packet for which no forwarding entry is found in the multicast forwarding table.
packet
uplink A transmission channel through which radio signals or other signals are transmitted to
the central office.
uplink tunnel GTP Tunnel from the Mobile Node to the SGSN.
upload An operation to report some or all configuration data of an NE to the NMS. The
configuration data then covers the configuration data stored at the NMS side.
upper limit The maximum consumption amount that a carrier sets for a subscriber in a bill cycle. If
the consumption amount if a subscriber exceeds the maximum consumption amount that
the carrier sets, the OCS still deducts the maximum consumption amount that the carrier
sets.
upstream In an access network, the direction that is far from the subscriber end of the link.
upstream board A board that provides the upstream transmission function. Through an upstream board,
services can be transmitted upstream to the upper-layer device.
usage parameter During communications, UPC is implemented to monitor the actual traffic on each virtual
control (UPC) circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
V-NNI virtual network-network interface
V-UNI See virtual user-network interface.
V.24 The physical layer interface specification between DTE and DCE defined by the ITU-
T. It complies with EIA/TIA-232.
VAS See value-added service.
VB virtual bridge
VBR See variable bit rate.
VC trunk See virtual container trunk.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCI virtual channel identifier
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VIP very important person
VLAN virtual local area network

VLAN mapping A technology that enables user packets to be transmitted over the public network by
translating private VLAN tags into public VLAN tags. When user packets arrive at the
destination private network, VLAN mapping translates public VLAN tags back into
private VLAN tags. In this manner, user packets are correctly transmitted to the
destination.
VLAN mapping table One of the properties of the MST region, which describes mappings between VLANs
and spanning tree instances.
VLAN stacking A technology that adds a VLAN tag to each incoming packet. The VLAN stacking
technology implements transparent transmission of C-VLANs in the ISP network to
realize the application of Layer 2 Virtual Private Network (VPN).
VP See virtual path.
VPI See virtual path identifier.
VPLS See virtual private LAN service.
VPN virtual private network
VRRP See Virtual Router Redundancy Protocol.
VSI virtual switch interface
Virtual Router A protocol used for multicast or multicast LANs such as an Ethernet. A group of routers
Redundancy Protocol (including an active router and several backup routers) in a LAN is regarded as a virtual
(VRRP) router, which is called a backup group. The virtual router has its own IP address. The
host in the network communicates with other networks through this virtual router. If the
active router in the backup group fails, one of the backup routers in this backup group
becomes active and provides routing service for the host in the network.
VoIP See voice over IP.
value-added service A service provided by carriers and service providers (SPs) together for subscribers based
(VAS) on voice, data, images, SMS messages, and so on. Communication network technologies,
computer technologies, and Internet technologies are used to provide value-added
services.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
virtual channel A VC logical trail that carries data between two end points in an ATM network. A point-
connection (VCC) to-multipoint VCC is a set of ATM virtual connections between two or multiple end
points.
virtual circuit A channel or circuit established between two points on a data communications network
with packet switching. Virtual circuits can be permanent virtual circuits (PVCs) or
switched virtual circuits (SVCs) .
virtual concatenation A group of co-located member trail termination functions that are connected to the same
group (VCG) virtual concatenation link
virtual container trunk The logical path formed by some cascaded VCs.
(VC trunk)
virtual fiber The fiber that is created between different devices. A virtual fiber represents the optical
path that bears SDH services in a WDM system.
virtual path (VP) A bundle of virtual channels, all of which are switched transparently across an ATM
network based on a common VPI.

virtual path identifier The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which
(VPI) virtual path the cell belongs.
virtual private LAN A type of point-to-multipoint L2VPN service provided over the public network. VPLS
service (VPLS) enables geographically isolated user sites to communicate with each other through the
MAN/WAN as if they are on the same LAN.
virtual user-network A virtual user-network interface, works as an action point to perform service
interface (V-UNI) classification and traffic control in HQoS.
voice over IP (VoIP) An IP telephony term for a set of facilities used to manage the delivery of voice
information over the Internet. VoIP involves sending voice information in a digital form
in discrete packets rather than by using the traditional circuit-committed protocols of the
public switched telephone network (PSTN).
voltage drop The voltage developed across a component or conductor by the flow of current through
the resistance or impedance of that component or conductor.
W
WAN See wide area network.
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WFQ See weighted fair queuing.
WLAN See wireless local area network.
WRED See weighted random early detection.
WRR weighted round robin
WTR See wait to restore.
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
Wideband Code A standard defined by the ITU-T for the third-generation wireless technology derived
Division Multiple from the Code Division Multiple Access (CDMA) technology.
Access (WCDMA)
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
wavelength The distance between successive peaks or troughs in a traveling wave, that is, the distance
over which a wave is transmitted within a vibration period.
wavelength protection Data for describing the wavelength protection structure. Its function is similar to that of
group the protection subnet for SDH NEs. The wavelength path protection can work only with
the correct configuration of the wavelength protection group.
weighted fair queuing A fair queue scheduling algorithm based on bandwidth allocation weights. This
(WFQ) scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all priority
queues can be scheduled.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
detection (WRED) synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.

wide area network A network composed of computers which are far away from each other which are
(WAN) physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
wireless local area A hybrid of the computer network and the wireless communication technology. It uses
network (WLAN) wireless multiple address channels as transmission media and carriers out data interaction
through electromagnetic wave to implement the functions of the traditional LAN.
working path A path allocated to transport the normal traffic.
working service A specific service that is part of a protection group and is labeled working.
wrapping A protection switching mode defined in ITU-T G.8132, which is applicable to packet-
based T-MPLS ring networks and similar to SDH two-fiber bidirectional multiplex
section protection (MSP). In this mode, the switching is triggered by the node that detects
a failure. For details, see ITU-T G.841.
X
X.21 ITU-T standard for serial communications over synchronous digital lines. It is mainly
used in Europe and Japan.
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
Y
Y.1731 The OAM protocol introduced by the ITU-T. Besides the contents defined by
IEEE802.1ag, ITU-T Recommendation Y.173 also defines the following combined
OAM messages: Alarm Indication Signal (AIS), Remote Defect Indication (RDI),
Locked Signal (LCK), Test Signal, Automatic Protection Switching (APS), Maintenance
Communication Channel (MCC), Experimental (EXP), and Vendor Specific (VSP) for
fault management and performance monitoring, such as frame loss measurement (LM),
and delay measurement (DM).


Alarms and Performance Events Reference (V100R005C00 - 01) PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Alarms and Performance Events Reference (V100R005C00 - 01) PDF

Caricato da

Copyright:

Formati disponibili

OptiX OSN 9560 Intelligent Optical Switching

Alarms and Performance Events

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2012-05-30) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX OSN 9560 V100R005C00

iManager U2000 V100R006C00

The intended audience of this document is system maintenance engineer.

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Issue 01 (2012-05-30) Huawei Proprietary and Confidential ii

NOTE Provides additional information to emphasize or supplement

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Changes in Issue 01(2012-05-30)

Issue 01 (2012-05-30) Huawei Proprietary and Confidential iii

About This Document.....................................................................................................................ii

Issue 01 (2012-05-30) Huawei Proprietary and Confidential iv

2.1.18 Alarm List S...........................................................................................................................................35

3 Handling Common Alarms.......................................................................................................55

Issue 01 (2012-05-30) Huawei Proprietary and Confidential v

4 Other Alarm Clearing...............................................................................................................118

Issue 01 (2012-05-30) Huawei Proprietary and Confidential vi

Issue 01 (2012-05-30) Huawei Proprietary and Confidential vii

Issue 01 (2012-05-30) Huawei Proprietary and Confidential viii

Issue 01 (2012-05-30) Huawei Proprietary and Confidential ix

Issue 01 (2012-05-30) Huawei Proprietary and Confidential x

5 Performance Event List.............................................................................................................338

6 Performance Event Clearing....................................................................................................362

Issue 01 (2012-05-30) Huawei Proprietary and Confidential xi

Issue 01 (2012-05-30) Huawei Proprietary and Confidential xii

7 Abnormal Event List.................................................................................................................437

Issue 01 (2012-05-30) Huawei Proprietary and Confidential xiii

1 Generation of Alarms and Performance

About This Chapter

Issue 01 (2012-05-30) Huawei Proprietary and Confidential 1

Figure 1-1 SDH alarm signal flow

SPI RST MST MSA HPT HPA LPT

Indicates that the corresponding alarm or signal is generated

1.1.1 Directions and Levels of Signal Flows

Issue 01 (2012-05-30) Huawei Proprietary and Confidential 2

Term Description Figure

Downlink The signal flow is as follows:

flow → lower order SDH port or port

Downlink signal flow

Uplink The signal flow is as follows:

higher order SDH port. PDH port

order and the cross-connect unit is the

Lower The signal between the cross-

signal Ethernet port is the lower order unit

flow signal flow. PDH port

Lower order part

1.1.2 Two Common Alarms

Issue 01 (2012-05-30) Huawei Proprietary and Confidential 3

1.1.3 Alarm Management

Alarms are reported in the following cases:

l A board detects alarms and reports them to the NE software.

In addition, alarm reversion and alarm suppression affect alarm reporting.

Automatic Alarm Reporting