OptiX OSN 8800 Alarms and Performance Events Reference (V100R002)

OptiX OSN 8800 Intelligent Optical Transport
Platform
V100R002C02
Alarms and Performance Events

Reference
Issue 08
Date 2014-02-14
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Copyright © Huawei Technologies Co., Ltd.
OptiX OSN 8800 Intelligent Optical Transport Platform
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 8800 V100R002C02
OptiX iManager T2000 V200R008C00
iManager U2000 V100R001C00
NOTE
This document is prepared based on the U2000. The operations on the T2000 are similar to those on the
U2000.
Intended Audience
This document describes the alarms and performance events generated by the equipment as well
as providing ways of handling alarms and performance events to clear the faults or failures.
This document is intended for:
l System maintenance engineer

l Network monitoring 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
Issue 08 (2014-02-14) Huawei Proprietary and Confidential ii

Symbol Description
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

CAUTION avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
time.
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.
Updates in Issue 08 (2014-02-14) Based on Product Version

V100R002C02
Some bugs in the manual of the previous version are fixed.

V100R002C02
l Modify the alarm processing of LASER_HAZARD_WARNING.
Issue 08 (2014-02-14) Huawei Proprietary and Confidential iii

l Modify the parameters definition of NO_BD_SOFT.

V100R002C02
l Modify the alarm processing of WAVELEN_OVER.
l Some bugs in the manual of the previous version are fixed.

V100R002C02

V100R002C02
Added the alarm list and performance event list of the TN54NQ2 board.
Added the performance event processing of CRC4BBE and CRC4FEBBE.

V100R002C02
Added the alarm processing of CLIENT_PORT_STA_INDI, INTRA_OTU_STA_INDI,
MS_SNCP_STA_INDI, ODUKSP_STA_INDI, ODU_SNCP_STA_INDI, OLP_STA_INDI,
OWSP_STA_INDI, SW_SNCP_STA_INDI.
Modify the alarm processing of CLIENT_PORT_PS, INTRA_OTU_PS, MS_SNCP_PS,

ODUKSP_PS, ODU_SNCP_PS, OLP_PS, OWSP_PS, SW_SNCP_PS.

V100R002C02
Deleted the alarm list and performance event list of the TN12WSMD2 and TN14WSM9 boards.
Issue 08 (2014-02-14) Huawei Proprietary and Confidential iv


V100R002C02
Added the alarm list and performance event list of the TN52TOG, TN14WSM9 boards.
Added the alarm processing of OSC_LOS, LASER_HAZARD_WARNING, LAN_LOC and

L_SYNC.
Deleted the alarm processing of MSSW_DIFFERENT.
Added the performance event processing of FEC_AFT_COR_ERAVR and

FEC_BEF_COR_ERAVR.

V100R002C00
Added the alarms and performance events of follow boards: LDX, EGSH, SF64A, SLH41,
SLO16, SLQ64, XCH, XCM, WSMD2, HSC1, STG.

V100R001C02
The lists of alarms of the CMR2, CMR4, DMR1, MB2, MR2, MR4, MR8, and SBM2 is deleted.
The lists of alarms and performance events of the LDGS and LDGD is deleted.

V100R001
The first commercial release of the OptiX OSN 8800 I V100R001.
Issue 08 (2014-02-14) Huawei Proprietary and Confidential v

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

1 Overview.........................................................................................................................................1
1.1 Alarm Level....................................................................................................................................................................2
1.2 Alarm Category..............................................................................................................................................................2
1.3 Performance Event Category..........................................................................................................................................3
1.4 Alarm Signal Flow..........................................................................................................................................................4
1.4.1 Overview.....................................................................................................................................................................4
1.4.2 Non-Convergent OTU Processing Standard SDH Signals..........................................................................................6
1.4.3 Non-Convergent OTU Processing Standard OTN Signals..........................................................................................9
1.4.4 Convergent OTU Processing Standard SDH Signals................................................................................................12
1.4.5 Convergent OTU Processing Standard OTN Signals................................................................................................15
1.4.6 Regenerating OTU.....................................................................................................................................................19
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function..................................................................21
1.4.8 OTU Processing GE Signals......................................................................................................................................23
1.4.9 Optical-Layer Alarm Signal Processing on OTN......................................................................................................26
1.5 Suppression Relation of Alarms...................................................................................................................................30
1.5.1 Suppression of OTN Alarms.....................................................................................................................................30
1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment Alarms......................................32
1.6 Performance Event Suppression by Alarms.................................................................................................................33
2 Alarm List......................................................................................................................................34
2.1 Product Alarm List.......................................................................................................................................................35
2.1.1 Alarm List A..............................................................................................................................................................35
2.1.2 Alarm List B..............................................................................................................................................................35
2.1.3 Alarm List C..............................................................................................................................................................37
2.1.4 Alarm List D..............................................................................................................................................................38
2.1.5 Alarm List E..............................................................................................................................................................39
2.1.6 Alarm List F...............................................................................................................................................................40
2.1.7 Alarm List G..............................................................................................................................................................41
2.1.8 Alarm List H..............................................................................................................................................................41
2.1.9 Alarm List I...............................................................................................................................................................43
2.1.10 Alarm List J.............................................................................................................................................................44
2.1.11 Alarm List K............................................................................................................................................................44
Issue 08 (2014-02-14) Huawei Proprietary and Confidential vi

2.1.12 Alarm List L............................................................................................................................................................44

2.1.13 Alarm List M...........................................................................................................................................................47
2.1.14 Alarm List N............................................................................................................................................................48
2.1.15 Alarm List O............................................................................................................................................................49
2.1.16 Alarm List P.............................................................................................................................................................58
2.1.17 Alarm List R............................................................................................................................................................60
2.1.18 Alarm List S.............................................................................................................................................................61
2.1.19 Alarm List T............................................................................................................................................................64
2.1.20 Alarm List V............................................................................................................................................................66
2.1.21 Alarm List W...........................................................................................................................................................67
2.1.22 Alarm List X............................................................................................................................................................67
2.2 Board Alarm List..........................................................................................................................................................68
2.2.1 ATE Board Alarm List..............................................................................................................................................68
2.2.2 AUX Board Alarm List.............................................................................................................................................68
2.2.3 CMR2 Board Alarm List...........................................................................................................................................68
2.2.4 CMR4 Board Alarm List...........................................................................................................................................68
2.2.5 CRPC Board Alarm List............................................................................................................................................68
2.2.6 D40V Board Alarm List............................................................................................................................................69
2.2.7 D40 Board Alarm List...............................................................................................................................................69
2.2.8 DCU Board Alarm List..............................................................................................................................................70
2.2.9 DCP Board Alarm List..............................................................................................................................................70
2.2.10 DMR1 Board Alarm List.........................................................................................................................................71
2.2.11 EFI1 Board Alarm List............................................................................................................................................71
2.2.12 EFI2 Board Alarm List............................................................................................................................................71
2.2.13 EGSH Board Alarm List..........................................................................................................................................71
2.2.14 FAN Board Alarm List............................................................................................................................................72
2.2.15 FIU Board Alarm List..............................................................................................................................................72
2.2.16 GFU Board Alarm List............................................................................................................................................73
2.2.17 HBA Board Alarm List............................................................................................................................................73
2.2.18 HSC1 Board Alarm List..........................................................................................................................................73
2.2.19 ITL Board Alarm List..............................................................................................................................................74
2.2.20 LDM Board Alarm List...........................................................................................................................................74
2.2.21 LDMD Board Alarm List........................................................................................................................................75
2.2.22 LDMS Board Alarm List.........................................................................................................................................77
2.2.23 LDX Board Alarm List............................................................................................................................................78
2.2.24 LOG Board Alarm List............................................................................................................................................79
2.2.25 LOM Board Alarm List...........................................................................................................................................81
2.2.26 LQMD Board Alarm List........................................................................................................................................82
2.2.27 LQMS Board Alarm List.........................................................................................................................................83
2.2.28 LQM Board Alarm List...........................................................................................................................................84
2.2.29 LSXLR Board Alarm List.......................................................................................................................................85
Issue 08 (2014-02-14) Huawei Proprietary and Confidential vii

2.2.30 LSXL Board Alarm List..........................................................................................................................................86

2.2.31 LSXR Board Alarm List..........................................................................................................................................87
2.2.32 LSX Board Alarm List............................................................................................................................................88
2.2.33 LWXS Board Alarm List.........................................................................................................................................89
2.2.34 M40V Board Alarm List..........................................................................................................................................90
2.2.35 M40 Board Alarm List............................................................................................................................................90
2.2.36 MCA4 Board Alarm List.........................................................................................................................................90
2.2.37 MCA8 Board Alarm List.........................................................................................................................................90
2.2.38 MR2 Board Alarm List............................................................................................................................................91
2.2.41 MR8V Board Alarm List.........................................................................................................................................91
2.2.42 ND2 Board Alarm List............................................................................................................................................92
2.2.43 NQ2 Board Alarm List............................................................................................................................................93
2.2.44 NS2 Board Alarm List.............................................................................................................................................95
2.2.45 NS3 Board Alarm List.............................................................................................................................................96
2.2.46 OAU1 Board Alarm List.........................................................................................................................................98
2.2.47 OBU1 Board Alarm List..........................................................................................................................................99
2.2.48 OBU2 Board Alarm List..........................................................................................................................................99
2.2.49 OLP Board Alarm List..........................................................................................................................................100
2.2.50 PIU Board Alarm List............................................................................................................................................100
2.2.51 RDU9 Board Alarm List........................................................................................................................................101
2.2.52 RMU9 Board Alarm List.......................................................................................................................................101
2.2.53 ROAM Board Alarm List......................................................................................................................................101
2.2.54 SBM2 Board Alarm List........................................................................................................................................102
2.2.55 SC1 Board Alarm List...........................................................................................................................................102
2.2.56 SC2 Board Alarm List...........................................................................................................................................102
2.2.57 SCC Board Alarm List..........................................................................................................................................103
2.2.58 SCS Board Alarm List...........................................................................................................................................105
2.2.59 SF64 Board Alarm List..........................................................................................................................................105
2.2.60 SF64A Board Alarm List.......................................................................................................................................106
2.2.61 SFD64 Board Alarm List.......................................................................................................................................107
2.2.62 SL64 Board Alarm List.........................................................................................................................................108
2.2.63 SLH41 Board Alarm List......................................................................................................................................109
2.2.64 SLD64 Board Alarm List......................................................................................................................................109
2.2.65 SLO16 Board Alarm List......................................................................................................................................110
2.2.66 SLQ16 Board Alarm List......................................................................................................................................111
2.2.67 SLQ64 Board Alarm List......................................................................................................................................111
2.2.68 STG Board Alarm List..........................................................................................................................................112
2.2.69 STI Board Alarm List............................................................................................................................................113
2.2.70 SXM Board Alarm List.........................................................................................................................................113
Issue 08 (2014-02-14) Huawei Proprietary and Confidential viii

2.2.71 TDC Board Alarm List..........................................................................................................................................113

2.2.72 TDX Board Alarm List..........................................................................................................................................113
2.2.73 TMX Board Alarm List.........................................................................................................................................114
2.2.74 TOG Board Alarm List..........................................................................................................................................117
2.2.75 TOM Board Alarm List.........................................................................................................................................117
2.2.76 TQX Board Alarm List..........................................................................................................................................119
2.2.77 VA1 Board Alarm List..........................................................................................................................................120
2.2.78 VA4 Board Alarm List..........................................................................................................................................120
2.2.79 WMU Board Alarm List........................................................................................................................................120
2.2.80 WSD9 Board Alarm List.......................................................................................................................................120
2.2.81 WSM9 Board Alarm List......................................................................................................................................121
2.2.82 WSMD2 Board Alarm List....................................................................................................................................121
2.2.83 WSMD4 Board Alarm List....................................................................................................................................121
2.2.84 XCH Board Alarm List..........................................................................................................................................122
2.2.85 XCM Board Alarm List.........................................................................................................................................122
2.2.86 XCT Board Alarm List..........................................................................................................................................122
3 Common Alarm Processing.....................................................................................................123

3.1 B1_EXC......................................................................................................................................................................126
3.1.1 B1_EXC(OCS)........................................................................................................................................................126
3.1.2 B1_EXC(OTN)........................................................................................................................................................129
3.2 BEFFEC_EXC............................................................................................................................................................131
3.3 BUS_ERR...................................................................................................................................................................132
3.3.1 BUS_ERR(OCS).....................................................................................................................................................133
3.3.2 BUS_ERR(OTN).....................................................................................................................................................135
3.4 CHAN_LOS...............................................................................................................................................................137
3.5 CLIENT_PORT_PS...................................................................................................................................................139
3.6 COMMUN_FAIL.......................................................................................................................................................140
3.6.1 COMMUN_FAIL(OCS).........................................................................................................................................140
3.6.2 COMMUN_FAIL(OTN).........................................................................................................................................142
3.7 ETH_8B10B_ERR.....................................................................................................................................................147
3.8 EX_ETHOAM_CC_LOS...........................................................................................................................................148
3.8.1 EX_ETHOAM_CC_LOS(OCS).............................................................................................................................148
3.8.2 EX_ETHOAM_CC_LOS(OTN).............................................................................................................................150
3.9 FC_LINK_ERR..........................................................................................................................................................151
3.10 FC_SYNC_LOS.......................................................................................................................................................153
3.11 IN_PWR_HIGH.......................................................................................................................................................154
3.11.1 IN_PWR_HIGH(OCS)..........................................................................................................................................155
3.11.2 IN_PWR_HIGH(OTN).........................................................................................................................................157
3.12 IN_PWR_LOW........................................................................................................................................................159
3.12.1 IN_PWR_LOW(OCS)...........................................................................................................................................159
3.12.2 IN_PWR_LOW(OTN)..........................................................................................................................................162
Issue 08 (2014-02-14) Huawei Proprietary and Confidential ix

3.13 INTRA_OTU_PS.....................................................................................................................................................164
3.14 LASER_MODULE_MISMATCH...........................................................................................................................166
3.15 LINK_ERR...............................................................................................................................................................167
3.15.1 LINK_ERR(OCS).................................................................................................................................................167
3.15.2 LINK_ERR(OTN).................................................................................................................................................168
3.16 LOOP_ALM.............................................................................................................................................................170
3.16.1 LOOP_ALM(OCS)...............................................................................................................................................170
3.16.2 LOOP_ALM(OTN)...............................................................................................................................................171
3.17 LPT_ACTIVE..........................................................................................................................................................173
3.18 LSR_WILL_DIE......................................................................................................................................................174
3.19 MS_AIS....................................................................................................................................................................175
3.19.1 MS_AIS(OCS).......................................................................................................................................................176
3.19.2 MS_AIS(OTN)......................................................................................................................................................177
3.20 MS_RDI....................................................................................................................................................................179
3.20.1 MS_RDI(OCS)......................................................................................................................................................179
3.20.2 MS_RDI(OTN)......................................................................................................................................................181
3.21 MUT_LOS................................................................................................................................................................183
3.22 OA_LOW_GAIN.....................................................................................................................................................184
3.23 ODU_SNCP_PS.......................................................................................................................................................186
3.24 ODUk_PM_AIS.......................................................................................................................................................187
3.25 ODUk_PM_BDI.......................................................................................................................................................191
3.26 ODUk_PM_DEG......................................................................................................................................................192
3.27 ODUk_PM_EXC......................................................................................................................................................193
3.28 ODUk_PM_SSF.......................................................................................................................................................194
3.29 OMS_FDI.................................................................................................................................................................198
3.30 OSC_LOS.................................................................................................................................................................199
3.31 OTS_LOS.................................................................................................................................................................200
3.32 OUT_PWR_HIGH...................................................................................................................................................201
3.33 PORT_MODULE_OFFLINE..................................................................................................................................202
3.34 POWER_FAIL.........................................................................................................................................................203
3.35 PUMP_COOL_EXC................................................................................................................................................205
3.36 R_LOF......................................................................................................................................................................206
3.36.1 R_LOF(OCS).........................................................................................................................................................206
3.36.2 R_LOF(OTN)........................................................................................................................................................210
3.37 R_LOS......................................................................................................................................................................212
3.37.1 R_LOS(OCS).........................................................................................................................................................212
3.37.2 R_LOS(OTN)........................................................................................................................................................216
3.38 R_OOF......................................................................................................................................................................218
3.38.1 R_OOF(OCS)........................................................................................................................................................219
3.38.2 R_OOF(OTN)........................................................................................................................................................222
3.39 R_SLIP.....................................................................................................................................................................224
Issue 08 (2014-02-14) Huawei Proprietary and Confidential x

3.40 REM_SF...................................................................................................................................................................226
3.41 REMOTE_FAULT...................................................................................................................................................227
3.42 SECU_ALM.............................................................................................................................................................227
3.43 SUM_INPWR_LOW................................................................................................................................................228
3.44 TD.............................................................................................................................................................................230
3.45 TF..............................................................................................................................................................................231
3.46 TS_CFG_MISMATCH............................................................................................................................................232
3.47 WRG_BD_TYPE.....................................................................................................................................................233
4 Alarm Processing.......................................................................................................................235
4.1 AD_CHECK_FAIL....................................................................................................................................................245
4.2 ALM_ALS..................................................................................................................................................................246
4.3 APS_MANUAL_STOP..............................................................................................................................................246
4.4 ALM_GFP_dCSF.......................................................................................................................................................247
4.5 ALM_GFP_dLFD......................................................................................................................................................248
4.6 ALM_HANGUP.........................................................................................................................................................252
4.7 APS_FAIL..................................................................................................................................................................252
4.8 APS_INDI..................................................................................................................................................................254
4.9 AU_AIS......................................................................................................................................................................255
4.10 AU_LOP...................................................................................................................................................................258
4.11 B1_SD......................................................................................................................................................................260
4.11.1 B1_SD(OCS).........................................................................................................................................................260
4.11.2 B1_SD(OTN).........................................................................................................................................................263
4.12 B2_EXC....................................................................................................................................................................264
4.13 B2_SD......................................................................................................................................................................268
4.14 B3_EXC....................................................................................................................................................................271
4.15 B3_EXC_VC3..........................................................................................................................................................274
4.16 B3_EXC_VC4..........................................................................................................................................................276
4.17 B3_SD......................................................................................................................................................................276
4.18 B3_SD_VC3.............................................................................................................................................................280
4.19 B3_SD_VC4.............................................................................................................................................................281
4.20 BD_NOT_INSTALLED..........................................................................................................................................282
4.21 BD_STATUS............................................................................................................................................................283
4.21.1 BD_STATUS(OCS)..............................................................................................................................................283
4.21.2 BD_STATUS(OTN)..............................................................................................................................................284
4.22 BDID_ERROR.........................................................................................................................................................285
4.23 BEFFEC_SD............................................................................................................................................................286
4.24 BIOS_STATUS........................................................................................................................................................287
4.25 BOOTROM_BAD....................................................................................................................................................288
4.25.1 BOOTROM_BAD(OCS)......................................................................................................................................289
4.25.2 BOOTROM_BAD(OTN)......................................................................................................................................290
4.26 C2_VCAIS................................................................................................................................................................291
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xi

4.27 CHAN_ADD............................................................................................................................................................292
4.28 CHIP_ABN...............................................................................................................................................................293
4.29 CLIENT_PORT_STA_INDI....................................................................................................................................294
4.30 CLIENT_PROT_NOTSTART.................................................................................................................................296
4.31 CLK_NO_TRACE_MODE......................................................................................................................................297
4.32 CODE_SYNC_LOS.................................................................................................................................................298
4.33 CRC4_CROSSTR....................................................................................................................................................299
4.34 DB_RESTORE_FAIL..............................................................................................................................................300
4.35 DBMS_ERROR........................................................................................................................................................301
4.36 DBMS_PROTECT_MODE.....................................................................................................................................302
4.37 DCM_INSUFF.........................................................................................................................................................303
4.38 DLAG_PROTECT_FAIL........................................................................................................................................304
4.39 DSP_LOAD_FAIL...................................................................................................................................................307
4.40 ETH_CFM_LOC......................................................................................................................................................308
4.41 ETH_CFM_MISMERGE.........................................................................................................................................309
4.42 ETH_CFM_MACSTATUS......................................................................................................................................310
4.43 ETH_CFM_RDI.......................................................................................................................................................311
4.44 ETH_CFM_UNEXPERI..........................................................................................................................................313
4.45 ETHOAM_DISCOVER_FAIL................................................................................................................................314
4.46 ETHOAM_RMT_CRIT_FAULT............................................................................................................................316
4.47 ETHOAM_RMT_LOOP..........................................................................................................................................317
4.48 ETHOAM_RMT_SD...............................................................................................................................................318
4.49 ETHOAM_SELF_LOOP.........................................................................................................................................319
4.50 ETHOAM_VCG_SELF_LOOP...............................................................................................................................321
4.51 EX_ETHOAM_MPID_CNFLCT............................................................................................................................322
4.52 EXT_SYNC_LOS....................................................................................................................................................323
4.53 EXT_TIME_LOC.....................................................................................................................................................325
4.54 FAN_FAIL...............................................................................................................................................................327
4.55 FAN_FAULT...........................................................................................................................................................328
4.56 FC_8B10BERR_OVER...........................................................................................................................................328
4.57 FCS_ERR.................................................................................................................................................................329
4.58 FEC_LOF.................................................................................................................................................................331
4.59 FEC_OOF.................................................................................................................................................................333
4.60 FPGA_ABN..............................................................................................................................................................334
4.61 FSELECT_STG........................................................................................................................................................335
4.62 FWD_PKT_LOSS....................................................................................................................................................336
4.63 GAINDATA_MIS....................................................................................................................................................337
4.64 HARD_BAD............................................................................................................................................................338
4.65 HARD_ERR.............................................................................................................................................................341
4.66 HP_LOM..................................................................................................................................................................344
4.67 HP_RDI....................................................................................................................................................................345
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xii

4.68 HP_REI.....................................................................................................................................................................346
4.69 HP_SLM...................................................................................................................................................................348
4.70 HP_TIM....................................................................................................................................................................350
4.71 HP_UNEQ................................................................................................................................................................351
4.72 HSC_UNAVAIL......................................................................................................................................................352
4.73 INTRA_OTU_STA_INDI........................................................................................................................................353
4.74 J0_MM......................................................................................................................................................................355
4.75 K1_K2_M.................................................................................................................................................................356
4.76 K2_M........................................................................................................................................................................357
4.77 L_SYNC...................................................................................................................................................................358
4.78 LAN_LOC................................................................................................................................................................359
4.79 LAG_PORT_FAIL...................................................................................................................................................361
4.80 LASER_HAZARD_WARNING..............................................................................................................................362
4.81 LASER_SHUT.........................................................................................................................................................363
4.82 LCAS_FOPR............................................................................................................................................................364
4.83 LCAS_FOPT............................................................................................................................................................365
4.84 LCAS_PLCR............................................................................................................................................................365
4.85 LCAS_PLCT............................................................................................................................................................367
4.86 LCAS_TLCR............................................................................................................................................................368
4.87 LCAS_TLCT............................................................................................................................................................370
4.88 LOCK_CUR_FAIL..................................................................................................................................................371
4.89 LOCKPOW_MIS.....................................................................................................................................................372
4.90 LP_RDI_VC3...........................................................................................................................................................373
4.91 LP_SLM_VC3..........................................................................................................................................................374
4.92 LP_UNEQ_VC3.......................................................................................................................................................375
4.93 LPT_RFI...................................................................................................................................................................376
4.94 LSR_COOL_ALM...................................................................................................................................................377
4.95 LSR_FORCE_OPEN................................................................................................................................................378
4.96 LSR_INVALID........................................................................................................................................................379
4.97 LTI............................................................................................................................................................................380
4.98 MOD_COM_FAIL...................................................................................................................................................382
4.99 MODULE_ADJUST_FAIL.....................................................................................................................................383
4.100 MODULE_COOLCUR_OVER.............................................................................................................................384
4.101 MODULE_TEMP_OVER......................................................................................................................................385
4.102 MODULEFILE_UPDATE_FAIL..........................................................................................................................386
4.103 MS_REI..................................................................................................................................................................387
4.104 MS_SNCP_PS........................................................................................................................................................388
4.105 MS_SNCP_STA_INDI..........................................................................................................................................389
4.106 MS_APS_INDI_EX...............................................................................................................................................391
4.107 MULTI_RPL_OWNER..........................................................................................................................................392
4.108 NEBD_XC_DIF.....................................................................................................................................................393
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xiii

4.109 NESF_LOST..........................................................................................................................................................395
4.110 NESTATE_INSTALL............................................................................................................................................396
4.111 NO_BD_PARA......................................................................................................................................................397
4.112 NO_BD_SOFT.......................................................................................................................................................398
4.113 NO_ELABEL.........................................................................................................................................................399
4.114 NODEID_MM........................................................................................................................................................400
4.115 NULL_SEND.........................................................................................................................................................401
4.116 OCH_FDI...............................................................................................................................................................402
4.117 OCH_FDI-O...........................................................................................................................................................403
4.118 OCH_FDI-P............................................................................................................................................................404
4.119 OCH_LOS-P...........................................................................................................................................................405
4.120 OCH_OCI...............................................................................................................................................................406
4.121 OCH_SSF...............................................................................................................................................................407
4.122 OCH_SSF-O...........................................................................................................................................................408
4.123 OCH_SSF-P............................................................................................................................................................409
4.124 ODU_AIS...............................................................................................................................................................410
4.125 ODU_LCK..............................................................................................................................................................411
4.126 ODU_OCI...............................................................................................................................................................412
4.127 ODUk_LOFLOM...................................................................................................................................................413
4.128 ODUk_PM_LCK....................................................................................................................................................415
4.129 ODUk_PM_OCI.....................................................................................................................................................416
4.130 ODUk_PM_TIM....................................................................................................................................................417
4.131 ODUk_TCMn_AIS................................................................................................................................................418
4.132 ODUk_TCMn_BDI................................................................................................................................................419
4.133 ODUk_TCMn_DEG...............................................................................................................................................420
4.134 ODUk_TCMn_EXC...............................................................................................................................................422
4.135 ODUk_TCMn_LCK...............................................................................................................................................423
4.136 ODUk_TCMn_LTC...............................................................................................................................................424
4.137 ODUk_TCMn_OCI................................................................................................................................................425
4.138 ODUk_TCMn_SSF................................................................................................................................................426
4.139 ODUk_TCMn_TIM................................................................................................................................................427
4.140 ODU_SNCP_STA_INDI........................................................................................................................................428
4.141 ODUKSP_PS..........................................................................................................................................................430
4.142 ODUKSP_STA_INDI............................................................................................................................................431
4.143 OH_LOOP..............................................................................................................................................................433
4.144 OLP_PS..................................................................................................................................................................434
4.145 OLP_STA_INDI.....................................................................................................................................................436
4.146 OMS_BDI...............................................................................................................................................................437
4.147 OMS_BDI-O..........................................................................................................................................................438
4.148 OMS_BDI-P...........................................................................................................................................................439
4.149 OMS_FDI-O...........................................................................................................................................................440
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xiv

4.150 OMS_FDI-P............................................................................................................................................................441
4.151 OMS_LOS-P..........................................................................................................................................................442
4.152 OMS_SSF...............................................................................................................................................................443
4.153 OMS_SSF-O...........................................................................................................................................................444
4.154 OMS_SSF-P...........................................................................................................................................................445
4.155 OOL........................................................................................................................................................................446
4.156 OOS_LOST............................................................................................................................................................447
4.157 OPA_FAIL_INDI...................................................................................................................................................448
4.158 OPU1_MSIM..........................................................................................................................................................449
4.159 OPU1_VCAT_SQM...............................................................................................................................................449
4.160 OPU1_VCAT_VcPLM..........................................................................................................................................450
4.161 OPU2_MSIM..........................................................................................................................................................451
4.162 OPU3_MSIM..........................................................................................................................................................452
4.163 OPUk_PLM............................................................................................................................................................453
4.164 OSC_RDI................................................................................................................................................................454
4.165 OTS_BDI................................................................................................................................................................455
4.166 OTS_BDI-O............................................................................................................................................................456
4.167 OTS_BDI-P............................................................................................................................................................457
4.168 OTS_LOS-O...........................................................................................................................................................458
4.169 OTS_LOS-P............................................................................................................................................................459
4.170 OTS_TIM...............................................................................................................................................................460
4.171 OTU_AIS................................................................................................................................................................460
4.172 OTU_LOF..............................................................................................................................................................462
4.173 OTU_LOM.............................................................................................................................................................463
4.174 OTUk_AIS..............................................................................................................................................................464
4.175 OTUk_BDI.............................................................................................................................................................465
4.176 OTUk_DEG............................................................................................................................................................466
4.177 OTUk_EXC............................................................................................................................................................467
4.178 OTUk_LOF............................................................................................................................................................468
4.179 OTUk_LOM...........................................................................................................................................................469
4.180 OTUk_SSF.............................................................................................................................................................470
4.181 OTUk_TIM.............................................................................................................................................................471
4.182 OUT_PWR_LOW..................................................................................................................................................473
4.183 OWSP_PS...............................................................................................................................................................474
4.184 OWSP_STA_INDI.................................................................................................................................................475
4.185 PATCH_ACT_TIMEOUT.....................................................................................................................................477
4.186 PATCH_DEACT_TIMEOUT................................................................................................................................478
4.187 PATCH_PKGERR.................................................................................................................................................479
4.188 PM_BDI..................................................................................................................................................................480
4.189 PM_BEI..................................................................................................................................................................481
4.190 PM_BIP8_OVER...................................................................................................................................................482
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xv

4.191 PM_BIP8_SD.........................................................................................................................................................483
4.192 PM_TIM.................................................................................................................................................................485
4.193 PORTSWITCH_FAIL............................................................................................................................................486
4.194 POWER_ABNORMAL.........................................................................................................................................486
4.195 POWER_DIFF_OVER...........................................................................................................................................488
4.196 PRBS_LSS..............................................................................................................................................................489
4.197 PUM_BCM_ALM..................................................................................................................................................490
4.198 PUM_TEM_ALM..................................................................................................................................................491
4.199 R_LOC....................................................................................................................................................................492
4.199.1 R_LOC(OCS)......................................................................................................................................................492
4.199.2 R_LOC(OTN)......................................................................................................................................................493
4.200 RELAY_ALARM_CRITICAL .............................................................................................................................494
4.201 RELAY_ALARM_IGNORE ................................................................................................................................495
4.202 RELAY_ALARM_MAJOR ..................................................................................................................................496
4.203 RELAY_ALARM_MINOR ..................................................................................................................................497
4.204 REM_SD................................................................................................................................................................498
4.205 RS_CROSSTR........................................................................................................................................................499
4.206 RTC_FAIL..............................................................................................................................................................500
4.207 S1_SYN_CHANGE...............................................................................................................................................501
4.208 SCC_LOC...............................................................................................................................................................502
4.209 SERVICE_TYPE_EXCEED_LICENSE...............................................................................................................503
4.210 SERVICE_CAPACITY_EXCEED_LICENSE.....................................................................................................504
4.211 SHELF_AREA_POWER_OVER..........................................................................................................................505
4.212 SLAVE_WORKING..............................................................................................................................................506
4.213 SM_BDI..................................................................................................................................................................507
4.214 SM_BEI..................................................................................................................................................................509
4.215 SM_BIP8_OVER...................................................................................................................................................509
4.216 SM_BIP8_SD.........................................................................................................................................................511
4.217 SM_IAE..................................................................................................................................................................512
4.218 SM_TIM.................................................................................................................................................................513
4.219 SNCP_FAIL...........................................................................................................................................................514
4.220 SO_SK_MISMATCH............................................................................................................................................515
4.221 SPEED_OVER.......................................................................................................................................................517
4.222 SUBRACK_ID_CONFLICT..................................................................................................................................518
4.223 SUBRACK_ID_MISMATCH................................................................................................................................519
4.224 SUBRACK_LOOP.................................................................................................................................................520
4.225 SUM_INPWR_HI..................................................................................................................................................521
4.226 SW_SNCP_PS........................................................................................................................................................522
4.227 SW_SNCP_STA_INDI..........................................................................................................................................523
4.228 SWDL_ACTIVATED_TIMEOUT........................................................................................................................525
4.229 SWDL_AUTOMATCH_INH................................................................................................................................526
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xvi

4.230 SWDL_CHGMNG_NOMATCH...........................................................................................................................526
4.231 SWDL_COMMIT_FAIL........................................................................................................................................528
4.232 SWDL_INPROCESS.............................................................................................................................................528
4.233 SWDL_NEPKGCHECK........................................................................................................................................529
4.234 SWDL_PKG_NOBDSOFT....................................................................................................................................530
4.235 SWDL_PKGVER_MM..........................................................................................................................................531
4.236 SWDL_ROLLBACK_FAIL..................................................................................................................................532
4.237 SYN_BAD..............................................................................................................................................................533
4.238 SYNC_C_LOS.......................................................................................................................................................534
4.239 SYNC_DISABLE...................................................................................................................................................536
4.240 SYNC_F_M_SWITCH..........................................................................................................................................537
4.241 SYNC_LOCKOFF.................................................................................................................................................538
4.242 SYNC_FAIL...........................................................................................................................................................540
4.243 SYSPARA_CFDB_NOSAME...............................................................................................................................541
4.244 SYSLOG_COMM_FAIL.......................................................................................................................................541
4.245 T_LOSEX...............................................................................................................................................................542
4.246 T_SLIP....................................................................................................................................................................543
4.247 TEM_HA................................................................................................................................................................544
4.248 TEM_LA................................................................................................................................................................545
4.249 TEMP_OVER.........................................................................................................................................................546
4.250 TEST_STATUS......................................................................................................................................................548
4.251 THUNDERALM....................................................................................................................................................549
4.252 TIME_LOS.............................................................................................................................................................550
4.253 TIME_NO_TRACE_MODE..................................................................................................................................551
4.254 TR_LOC.................................................................................................................................................................552
4.255 TU_AIS_VC3.........................................................................................................................................................554
4.256 TU_LOP_VC3........................................................................................................................................................555
4.257 VCAT_LOA...........................................................................................................................................................556
4.257.1 VCAT_LOA(OCS)..............................................................................................................................................557
4.257.2 VCAT_LOA(OTN).............................................................................................................................................558
4.258 VCAT_LOM_VC3.................................................................................................................................................558
4.259 VCAT_LOM_VC4.................................................................................................................................................559
4.260 VOA_ADJUST_FAIL............................................................................................................................................561
4.261 VOADATA_MIS...................................................................................................................................................562
4.262 W_R_FAILURE.....................................................................................................................................................563
4.263 WAVEDATA_MIS................................................................................................................................................564
4.264 WAVELEN_OVER................................................................................................................................................565
4.265 XC_UNSWITCH....................................................................................................................................................566
5 Performance Event List.............................................................................................................568

5.1 Product Performance Event List.................................................................................................................................569
5.1.1 Performance Event of Check and Error Correction.................................................................................................569
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xvii

5.1.2 Performance Event of Pointer Justification.............................................................................................................570

5.1.3 Performance Event of Equipment Function............................................................................................................570
5.1.4 Performance Event of Multiplex Section Bit Error.................................................................................................574
5.1.5 Performance Event of Regenerator Section Bit Error.............................................................................................575
5.1.6 Performance Event of Higher Order Path Bit Error................................................................................................576
5.1.7 Performance Event of Lower Order Path Bit Error.................................................................................................576
5.1.8 Performance Event of OTN.....................................................................................................................................577
5.1.9 Performance Event List of RMON Function...........................................................................................................585
5.1.10 TCM Performance Event ......................................................................................................................................589
5.1.11 Performance Event of FC......................................................................................................................................590
5.2 Board Performance Event List...................................................................................................................................591
5.2.1 CRPC Board Performance Event List.....................................................................................................................591
5.2.2 D40V Board Performance Event List......................................................................................................................592
5.2.3 D40 Board Performance Event List.........................................................................................................................592
5.2.4 DCP Board Performance Event List........................................................................................................................592
5.2.5 EGSH Board Performance Event List.....................................................................................................................592
5.2.6 FIU Board Performance Event List.........................................................................................................................594
5.2.7 HSC1 Board Performance Event List......................................................................................................................594
5.2.8 HBA Board Performance Event List.......................................................................................................................594
5.2.9 ITL Board Performance Event List.........................................................................................................................595
5.2.10 LDM Board Performance Event List.....................................................................................................................595
5.2.11 LDMD Board Performance Event List..................................................................................................................596
5.2.12 LDMS Board Performance Event List..................................................................................................................598
5.2.13 LDX Board Performance Event List.....................................................................................................................600
5.2.14 LOG Board Performance Event List.....................................................................................................................601
5.2.15 LOM Board Performance Event List.....................................................................................................................603
5.2.16 LQMD Board Performance Event List..................................................................................................................606
5.2.17 LQMS Board Performance Event List..................................................................................................................607
5.2.18 LQM Board Performance Event List.....................................................................................................................609
5.2.19 LSXLR Board Performance Event List.................................................................................................................611
5.2.20 LSXL Board Performance Event List...................................................................................................................612
5.2.21 LSXR Board Performance Event List...................................................................................................................613
5.2.22 LSX Board Performance Event List......................................................................................................................614
5.2.23 LWXS Board Performance Event List..................................................................................................................615
5.2.24 M40V Board Performance Event List...................................................................................................................616
5.2.25 M40 Board Performance Event List......................................................................................................................616
5.2.26 MCA4 Board Performance Event List..................................................................................................................616
5.2.27 MCA8 Board Performance Event List..................................................................................................................616
5.2.28 MR8V Board Performance Event List..................................................................................................................617
5.2.29 ND2 Board Performance Event List......................................................................................................................617
5.2.30 NQ2 Board Performance Event List......................................................................................................................618
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xviii

5.2.31 NS2 Board Performance Event List......................................................................................................................621

5.2.32 NS3 Board Performance Event List......................................................................................................................622
5.2.33 OAU1 Board Performance Event List...................................................................................................................624
5.2.34 OBU1 Board Performance Event List...................................................................................................................624
5.2.35 OBU2 Board Performance Event List...................................................................................................................624
5.2.36 OLP Board Performance Event List......................................................................................................................625
5.2.37 RDU9 Board Performance Event List...................................................................................................................625
5.2.38 RDU9 Board Performance Event List...................................................................................................................625
5.2.39 RMU9 Board Performance Event List..................................................................................................................625
5.2.40 ROAM Board Performance Event List.................................................................................................................625
5.2.41 SC1 Board Performance Event List.......................................................................................................................626
5.2.42 SC2 Board Performance Event List.......................................................................................................................626
5.2.43 SFD64 Board Performance Event List..................................................................................................................626
5.2.44 SF64 Board Performance Event List.....................................................................................................................627
5.2.45 SF64A Board Performance Event List..................................................................................................................628
5.2.46 SL64 Board Performance Event List.....................................................................................................................629
5.2.47 SLD64 Board Performance Event List..................................................................................................................629
5.2.48 SLH41 Board Performance Event List..................................................................................................................630
5.2.49 SLO16 Board Performance Event List..................................................................................................................631
5.2.50 SLQ16 Board Performance Event List..................................................................................................................631
5.2.51 SLQ64 Board Performance Event List..................................................................................................................632
5.2.52 STG Board Performance Event List......................................................................................................................632
5.2.53 SXM Board Performance Event List.....................................................................................................................633
5.2.54 TDC Board Performance Event List.....................................................................................................................633
5.2.55 TDX Board Performance Event List.....................................................................................................................633
5.2.56 TMX Board Performance Event List.....................................................................................................................635
5.2.57 TOG Board Performance Event List.....................................................................................................................636
5.2.58 TOM Board Performance Event List.....................................................................................................................637
5.2.59 TQX Board Performance Event List.....................................................................................................................639
5.2.60 VA1 Board Performance Event List......................................................................................................................641
5.2.61 VA4 Board Performance Event List......................................................................................................................641
5.2.62 WMU Board Performance Event List...................................................................................................................641
5.2.63 WSD9 Board Performance Event List...................................................................................................................641
5.2.64 WSM9 Board Performance Event List..................................................................................................................641
5.2.65 WSMD2 Board Performance Event List...............................................................................................................642
5.2.66 WSMD4 Board Performance Event List...............................................................................................................642
5.2.67 XCH Board Performance Event List.....................................................................................................................642
5.2.68 XCM Board Performance Event List....................................................................................................................642
5.2.69 XCT Board Performance Event List.....................................................................................................................642
6 Performance Event Processing................................................................................................643

6.1 AUPJCHIGH..............................................................................................................................................................648
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xix

6.2 AUPJCLOW...............................................................................................................................................................649
6.3 AUPJCNEW...............................................................................................................................................................650
6.4 BCV............................................................................................................................................................................651
6.5 CCV............................................................................................................................................................................652
6.6 CRC4BBE..................................................................................................................................................................652
6.7 CRC4FEBBE..............................................................................................................................................................653
6.8 CRC4ES......................................................................................................................................................................654
6.9 CRC4FEES.................................................................................................................................................................655
6.10 CRC4FESES.............................................................................................................................................................656
6.11 CRC4FEUAS............................................................................................................................................................656
6.12 CRC4SES.................................................................................................................................................................657
6.13 CRC4UAS................................................................................................................................................................658
6.14 EDTMP.....................................................................................................................................................................659
6.15 EDTPL......................................................................................................................................................................660
6.16 ENVTMP..................................................................................................................................................................660
6.17 FEC_AFT_COR_ER................................................................................................................................................661
6.18 FEC_AFT_COR_ERAVR........................................................................................................................................662
6.19 FEC_BEF_COR_ER................................................................................................................................................663
6.20 FEC_BEF_COR_ERAVR........................................................................................................................................664
6.21 FEC_COR_0BIT_CNT............................................................................................................................................665
6.22 FEC_COR_1BIT_CNT............................................................................................................................................665
6.23 FEC_COR_BYTE_CNT..........................................................................................................................................666
6.24 FEC_UNCOR_BLOCK_CNT.................................................................................................................................666
6.25 HPBBE.....................................................................................................................................................................667
6.26 HPES........................................................................................................................................................................668
6.27 HPFEBBE.................................................................................................................................................................669
6.28 HPFEES....................................................................................................................................................................670
6.29 HPFESES..................................................................................................................................................................671
6.30 HPFEUAS................................................................................................................................................................672
6.31 HPSES......................................................................................................................................................................673
6.32 HPUAS.....................................................................................................................................................................674
6.33 ICCLC......................................................................................................................................................................675
6.34 ICTMP......................................................................................................................................................................676
6.35 LSBIAS....................................................................................................................................................................677
6.36 LSCLC......................................................................................................................................................................678
6.37 LSIOP.......................................................................................................................................................................679
6.38 LSOOP......................................................................................................................................................................680
6.39 LSTMP.....................................................................................................................................................................681
6.40 MSBBE.....................................................................................................................................................................682
6.41 MSES........................................................................................................................................................................683
6.42 MSFEBBE................................................................................................................................................................684
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xx

6.43 MSFEES...................................................................................................................................................................685
6.44 MSFESES.................................................................................................................................................................685
6.45 MSFEUAS................................................................................................................................................................686
6.46 MSSES......................................................................................................................................................................687
6.47 MSUAS....................................................................................................................................................................688
6.48 ODU2PMBIP8..........................................................................................................................................................689
6.49 ODUk_PM_BBE......................................................................................................................................................690
6.50 ODUk_PM_BBER...................................................................................................................................................691
6.51 ODUk_PM_ES.........................................................................................................................................................692
6.52 ODUk_PM_FEBBE.................................................................................................................................................693
6.53 ODUk_PM_FEBBER...............................................................................................................................................694
6.54 ODUk_PM_FEES....................................................................................................................................................694
6.55 ODUk_PM_FESES..................................................................................................................................................695
6.56 ODUk_PM_FESESR................................................................................................................................................696
6.57 ODUk_PM_FEUAS.................................................................................................................................................697
6.58 ODUk_PM_SES.......................................................................................................................................................697
6.59 ODUk_PM_SESR....................................................................................................................................................698
6.60 ODUk_PM_UAS......................................................................................................................................................699
6.61 ODUk_TCMn_BBE.................................................................................................................................................700
6.62 ODUk_TCMn_BBER..............................................................................................................................................701
6.63 ODUk_TCMn_BIAES.............................................................................................................................................702
6.64 ODUk_TCMn_ES....................................................................................................................................................703
6.65 ODUk_TCMn_FEBBE............................................................................................................................................703
6.66 ODUk_TCMn_FEBBER..........................................................................................................................................704
6.67 ODUk_TCMn_FEES................................................................................................................................................705
6.68 ODUk_TCMn_FESES.............................................................................................................................................706
6.69 ODUk_TCMn_FESESR...........................................................................................................................................706
6.70 ODUk_TCMn_FEUAS............................................................................................................................................707
6.71 ODUk_TCMn_IAES................................................................................................................................................708
6.72 ODUk_TCMn_SES..................................................................................................................................................708
6.73 ODUk_TCMn_SESR...............................................................................................................................................709
6.74 ODUk_TCMn_UAS.................................................................................................................................................710
6.75 OSPICCV.................................................................................................................................................................710
6.76 OSPITMP.................................................................................................................................................................711
6.77 OTU2SMBIP8..........................................................................................................................................................712
6.78 OTUk_BBE..............................................................................................................................................................713
6.79 OTUk_BBER............................................................................................................................................................714
6.80 OTUk_ES.................................................................................................................................................................715
6.81 OTUk_FEBBE..........................................................................................................................................................716
6.82 OTUk_FEBBER.......................................................................................................................................................716
6.83 OTUk_FEES.............................................................................................................................................................717
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xxi

6.84 OTUk_FESES..........................................................................................................................................................718
6.85 OTUk_FESESR........................................................................................................................................................719
6.86 OTUk_FEUAS.........................................................................................................................................................719
6.87 OTUk_SES...............................................................................................................................................................720
6.88 OTUk_SESR............................................................................................................................................................721
6.89 OTUk_UAS..............................................................................................................................................................722
6.90 PCLSOP....................................................................................................................................................................723
6.91 PCLSSN....................................................................................................................................................................724
6.92 PCLSWL..................................................................................................................................................................724
6.93 PCLSWLO................................................................................................................................................................725
6.94 RPL...........................................................................................................................................................................726
6.95 RSBBE......................................................................................................................................................................727
6.96 RSCSES....................................................................................................................................................................728
6.97 RSES.........................................................................................................................................................................729
6.98 RSOFS......................................................................................................................................................................730
6.99 RSOOF.....................................................................................................................................................................731
6.100 RSSES....................................................................................................................................................................731
6.101 RSUAS...................................................................................................................................................................732
6.102 SUMIOP.................................................................................................................................................................733
6.103 SUMOOP................................................................................................................................................................735
6.104 TLB.........................................................................................................................................................................736
6.105 TPL.........................................................................................................................................................................737
6.106 VC3BBE.................................................................................................................................................................738
6.107 VC3CSES...............................................................................................................................................................739
6.108 VC3ES....................................................................................................................................................................741
6.109 VC3FEBBE............................................................................................................................................................743
6.110 VC3FECSES..........................................................................................................................................................744
6.111 VC3FEES...............................................................................................................................................................745
6.112 VC3FESES.............................................................................................................................................................746
6.113 VC3FEUAS............................................................................................................................................................748
6.114 VC3SES..................................................................................................................................................................749
6.115 VC3UAS.................................................................................................................................................................750
6.116 WCV.......................................................................................................................................................................751
6.117 XCSTMP................................................................................................................................................................752
7 Event List.....................................................................................................................................754
8 Event Processing........................................................................................................................757
8.1 EAPE Abnormal Event Notification..........................................................................................................................758
8.2 EAPE Adjustment Result Event Notification.............................................................................................................759
8.3 OWSP Abnormal Event..............................................................................................................................................762
8.4 ODUk SPRing Abnormal Event.................................................................................................................................765
8.5 RMON Performance Value Is Above the Upper Threshold.......................................................................................767
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xxii

8.6 RMON Module Performance Value Is Lower than the Lower Threshold.................................................................769
8.7 1+1 Equipment Level Protection Switching Event Report........................................................................................771
A Glossary......................................................................................................................................773
B Acronyms and Abbreviations.................................................................................................778
Issue 08 (2014-02-14) Huawei Proprietary and Confidential xxiii

Alarms and Performance Events Reference 1 Overview
1 Overview
About This Chapter
This chapter describes the meaning, indicator status, category, range, and impact of the alarms
of four levels. It also describes the meaning and category of performance events, and provides
the suppression relation of alarms and performance event suppression by alarms.
1.1 Alarm Level

This section respectively describes the meaning, impact, and indicator status of the alarms of
four levels.
1.2 Alarm Category

This section describes the meaning and range of alarms in different categories.
1.3 Performance Event Category

The performance events can be classified into ten categories according to the functions
monitored by the performance events.
1.4 Alarm Signal Flow

This section describes the alarm signal flow of the OTU. It describes the generation, detection,
and transmission of alarms when the OTU accesses different types of signals.
1.5 Suppression Relation of Alarms

This section describes the rules of alarm suppression and provides the suppression relation figure
of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm
suppression.
1.6 Performance Event Suppression by Alarms

An optical interface can report several alarms and performance events. Some performance events
are not important for the maintenance engineer.
Issue 08 (2014-02-14) Huawei Proprietary and Confidential 1

1.1 Alarm Level

This section respectively describes the meaning, impact, and indicator status of the alarms of
four levels.
The alarm level is used to identify the severity, importance, and urgency of the alarms. The
alarms can be classified into the following four levels in the sequence of decreasing severity:
critical alarm, major alarm, minor alarm, and warning alarm.
l Critical alarm: The alarm needs to be handled immediately; otherwise, the system will be
down.
l Major alarm: The alarm needs to be handled in time; otherwise, some important functions
will not be performed.
l Minor alarm: The alarm is used to inform the maintenance personnel of locating the alarm
causes and removing the incipient fault.
l Warning alarm: The alarm need not be handled. The maintenance personnel only need to
know the running status of the equipment.
For the meaning and corresponding indicator status on the board of the alarms of the four levels,
see Table 1-1.
Table 1-1 Alarm levels
Alarm Level Definition Indicator Status
Critical alarm Global fault alarms and event alarms that The SRV indicator is on
cause system down (red).
Major alarm Faulty alarms and event alarms of certain The SRV indicator is on
boards or lines (red).
Minor alarm General fault alarms and event alarms that are The SRV is on (yellow).
used to indicate whether the board or line is
normally working such as board reset and
failure or timeout of occupation of common
resources.
Warning Fault alarms and event alarms for warning The alarm indicator is off.
alarm
1.2 Alarm Category

This section describes the meaning and range of alarms in different categories.
The alarms can be classified into the following six categories. For details, see Table 1-2.

Table 1-2 Alarm category
Alarm Definition Example

Category
Communication Alarms related to the NE The alarm is generated when the

alarm communication, ECC NE communication is interrupted
communication, and or the optical signal is lost.
communication with optical
signals
Process alarm Alarms related to the software The alarm is generated when the
processing and anomalies database is in error or the NE is in
the installing state.
Equipment alarm Alarms related to the hardware of The alarm is generated when the
the equipment laser is faulty or the optical
interface is looped back.
Service alarm Alarms related to the service status The alarm is generated when the
and network service quality signals at the line layer are
degraded.
Environment Alarms related to the power supply The alarm is generated when the
alarm system and environment of the temperature of the power module is
equipment room excessively high.
Security alarm Alarms related to the network The alarm is generated when the
management and the NE security NE user is not logged in.
1.3 Performance Event Category

The performance events can be classified into ten categories according to the functions
monitored by the performance events.
The performance events are important parameters that reflect the working performance of the
equipment. Knowledge of the generation principle, related boards, and alarms of the
performance events is helpful to find incipient faults in routine maintenance and analyze the
fault. The categories of the performance events are listed in Table 1-3.
The performance events and alarms are related. When the number of performance events exceeds
the pre-set threshold, the related alarm is triggered. Hence, when a performance event is
generated, check whether the related alarm is generated and handle the performance event
according to the handling procedure of the related alarm.
The OptiX OSN 8800 I provides the remote monitoring function through which the network can
monitor the transmission of data in different network segments. Remote monitoring (RMON)
provides flexible detection modes and control mechanisms to cater for the needs of different
types of networks. The RMON defines a serial of statistic formats and functions to realize the
data exchange among the control stations and detection stations in compliance with the RMON
standard. The RMON also provides error diagnosis, planning, and information receiving of the
performance events of the entire network.

Table 1-3 Performance event categories
Performance Event Definition

Category
Performance event related to bit The performance event is generated when bit errors occur
errors of the regenerator section at the regenerator section in the SDH frames of the signals
on the WDM side or the client side of the board.
errors of the multiplex section at the multiplex section in the SDH frames of the signals
on the WDM side or the client side of the board.
errors of the higher order path in the higher order path.
errors of the lower order path in the lower order path.
Performance event of pointer The performance event is generated when the board
justification performs the pointer justification
Performance event related to the The performance event is generated when the board
verification and error correction performs the service verification or bit error correction.
Performance event related to the The performance event is generated when the optical
equipment function power, working current of the laser, or other factors about
the running environment exceed the threshold.
OTN performance event The performance event is generated when bit errors occur
in the PM, TCM, or SM segment of the OTN service.
TCM Performance Event The TCM performance events are used to monitor the
transmission performance in the tandem connection.
RMON performance event The performance event is related to the mode in which the
board transmits or receives the data packets and the
number and quality of transmitted or received packets in
different lengths.
FC performance event The performance event is generated when parameter

changes in the FC.
1.4 Alarm Signal Flow

This section describes the alarm signal flow of the OTU. It describes the generation, detection,
and transmission of alarms when the OTU accesses different types of signals.
1.4.1 Overview
This section describes the seven types of scenarios of the alarm signal flow, SF, SD, and basic
concepts in the alarm signal flow diagram.

Classification
For a WDM product, the detection and transmission of alarms vary according to the type of the
signals that are accessed into the OTU. The OTU is classified into the following types:
l Non-convergent OTU
It refers to an OTU that converts one channel of client service signals.
l Convergent OTU
It refers to an OTU that converges and converts multiple channels of client service signals.
l Regenerating OTU
It refers to an OTU that regenerates the corresponding service signals at an intermediate
station.
According to the type of the OTU and the type of the signals accessed by the OTU, the following
seven situations are defined in this section:
l Non-convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the non-convergent OTU processes
standard SDH signals.
l Non-convergent OTU processing standard OTN signals
This section describes the alarm signal flow when the non-convergent OTU processes
standard OTN signals.
l Convergent OTU processing standard SDH signals
This section describes the alarm signal flow when the convergent OTU processes standard
SDH signals.
l Convergent OTU processing standard OTN signals
This section describes the alarm signal flow when the convergent OTU processes standard
OTN signals.
l Regenerating OTU
This section describes the alarm signal flow of the regenerating OTU.
l OTU with the cross-connect function
This section describes the alarm signal flow of the OTU with the cross-connect function.
l OTU processing GE signals
This section describes the alarm signal flow when the OTU processes GE signals.
SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are trigger
conditions of a protection switching. Whether the SD event is used as a trigger condition,
however, it can be set by the user.
The SF and SD events are marked in the alarm signal flow diagrams in this section. These events
are generated when the equipment configured with network protection detects a certain alarm.
If the equipment is not configured with the network protection, The SF and SD events are not
detected or reported.

Concepts
The following concepts are used in the diagrams in this section:
l WDM side: It is the WDM side of the OTU.

l Client side: it is the client side of the OTU. On the client side, the services from a client
device are accessed.
l Middle part: It is the middle part between the WDM side and the client side. It is a virtual
concept, and thus is not displayed on the U2000. This concept is introduced to describe the
alarm detection mechanism.
l N#1: It indicates channel 1 at optical interface N on the OTU. For example, the client-side
optical interfaces of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical
interface of the LQMD unit is numbered 1. Then, 3#1 indicates channel 1 at client-side
optical interface 3.
l 1#N: It indicates channel N at WDM-side optical interface 1 on the OTU. For example,
1#3 indicates channel 3 at WDM-side optical interface 1.
1.4.2 Non-Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the non-convergent OTU processes standard
SDH signals.
Figure 1-1 and Figure 1-2 show the alarm signal flows when the non-convergent OTU processes
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.

Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals
Station A Station B Client device
Client-side WDM-side WDM-side Client-side Client-device
R_LOS
R_LOS REM_SF R_LOF
R_LOF
R_LOF REM_SF R_LOF
MS_AIS
MS_AIS REM_SF MS_AIS
BI errors
B1_EXC REM_SD B1 errors
BI errors
B1_SD B1 errors
SD
PM BIP8 errors ODUk_PM_DEG/
Errors
ODUk_PM_EXC
PM remote BER
performance events
SD
SM BIP8 Errors OTUk_DEG/
Errors
OTUk_EXC
OTUk remote BER

performance events
SF
OTUk_AIS
OTUk_AIS R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF
OTUk_LOM
OTUk_LOM R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF: SF event detecting SD: SD event detecting Alarm processing

xxx Detects and reports the xxx alarm or performance event
This section describes the alarm signal flow by analyzing how the OTU processes the R_LOS
alarm and PM BIP8 errors. The alarm signal flows of other alarms are similar.
l R_LOS
The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The client side of
the OTU at station B detects the REM_SF alarm. The alarm is then sent to the downstream
client device of station B, and the OTU reports the R_LOF alarm to the client device.
l PM BIP8 errors

The OTU at station B detects PM BIP 8 errors on the WDM side. When the PM BIP 8
errors exceed the threshold, the ODUk_PM_DEG or ODUk_PM_EXC alarm is generated.
The number of errors determines which alarm is generated. In addition, the performance
events indicting ODUk PM remote bit errors are sent to the WDM side of upstream station
A. The bit errors are then sent to the client device (The bit errors cannot be sent to the
downstream station except that the PM BIP 8 errors are from the data inside). The alarms
related to bit errors are detected in the client device.
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals
SF
MFAS frame discontinuous
OTUk_LOM
ODUk_PM_BDI
&OTUk_BDI The SF event is generated when the
SFTIM follow-up response is Enabled.
PM TTI byte mismatch
ODUk_PM_TIM R_LOF
ODUk_PM_BDI
The SF event is generated when the
SF TIM follow-up response is Enabled.
SM TTI byte mismatch
OTUk_TIM R_LOF
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
Excessive bit errors before FEC

BEFFEC_EXC
SF
OTUk_LOF
OTUk_LOF R_LOF
ODUk_PM_BDI
&OTUk_BDI
ODUk_PM_AIS/ SF
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/
ODUk_PM_OCI/ R_LOF
ODUk_PM_LCK
ODUk_PM_BDI
SF
R_LOS
R_LOS R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF: SF event detecting Alarm processing
xxx Detects and reports the xxx alarm
Detects and reports the xxx alarm when the TIM follow-up
xxx
response is Enabled.

This section describes the alarm signal flow by analyzing how the OTU processes the
OTUk_LOF alarm. The alarm signal flows of other alarms are similar.
The WDM side of the OTU at station B detects the OTUk_LOF alarm. Then, the OTU sends
the ODUk_PM_BDI and OTUk_BDI alarms to the WDM side of upstream station A. In addition,
the alarm is then sent to the client side of station B. After the alarm is processed on the client
side, the R_LOF alarm is detected in the client device.
1.4.3 Non-Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the non-convergent OTU unit processes
Figure 1-3 and Figure 1-4 show the alarm signal flows when the non-convergent OTU processes
NOTE
The non-intrusive monitoring of the board shown in the figures in this section is enabled.

Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals
R_LOS SF
R_LOS ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SD
PM BIP8 errors ODUk_PM_DEG/
ODUk_PM_DEG/ PM BIP8 errors
ODUk_PM_EXC ODUk_PM_EXC
SM BIP8 errors OTUk_DEG/

OTUk_EXC
OTUk remote BER SD
performance events SM BIP8 errors
OTUk_DEG/
OTUk_EXC
OTUk remote BER
performance events
SD
PM BIP8 errors
ODUk_PM_DEG/
PM BIP8 errors
ODUk_PM_EXC
SF
OTUk_LOF
OTUk_LOF ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SF
OTUk_LOM
OTUk_LOM ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SF
OTUk_AIS
OTUk_AIS ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI OTUk_LOF/
OTUk_LOM/ SF
OTUk_AIS OTUk_LOF/
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS
OTUk_BDI

This section describes the alarm signal flow by analyzing how the OTU unit processes the
R_LOS and OTUk_LOF alarms. The alarm signal flow of other alarms is similar.
l R_LOS
The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The WDM side of
the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is generated.
The event triggers a protection switching. The alarm is then sent to the downstream client
equipment of station B, and the OTU reports the ODUk_PM_AIS alarm to the client
equipment.
l OTUk_LOF
The OTUk_LOF alarm is detected on the WDM side of the OTU board at station B, and
station B sends the OTUk_BDI alarm to the WDM side of the OTU at the upstream station

A. At the same time, the alarm is then sent to the downstream station of station B, where
it is processed on the client side of the OTU. In this case, the ODUk_PM_AIS alarm is
detected in the client equipment. An SF event is generated on the WDM side of the OTU
at station B, and a service channel protection switching is triggered.
The client side of the OTU at station A receives OTUk_LOF signals. The OTU sends the
OTUk_BDI alarm to the upstream client equipment of station A. In addition, the LOF alarm
is processed on the WDM side of the OTU and then is sent to station B. The WDM side of
the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is generated.
The event triggers a protection switching. The alarm is then sent to the downstream client
equipment of station B, and the OTU reports the ODUk_PM_AIS alarm to the client
equipment.
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals
The SF event is generated when the

OTUk_TIM The SF event is generated when the
OTUk_TIM
OTUk_BDI
OTUk_BDI
OTUk_BDI OTUk_BDI
OTUk_BDI OTUk_BDI
Transparent transmission of all PM signals
ODUk_PM_AIS/
SF
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS/ ODUk_PM_AIS/ ODUk_PM_AIS/
ODUk_PM_LCK/ ODUk_PM_LCK/ ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_OCI ODUk_PM_OCI
R_LOS SF
R_LOS ODUk_PM_AIS
OTUk_BDI

l OTUk_TIM
After the OTU at station A receives the OTUk_TIM alarm on the client side, it sends the
OTUk_BDI alarm to the upstream station, but it does not send the OTUk_TIM alarm to
the downstream station. If the TIM is enabled in the subsequent action, an SF event is
generated and the WDM side of the OTU at station B reports the ODUk_PM_AIS alarm.
The ODUk_PM_AIS alarm is sent to the downstream and the client device reports this
alarm.

After the OTU at station B receives the OTUk_TIM alarm on the WDM side, this alarm is
not sent to the downstream if the TIM is not enabled in the subsequent action. If the TIM
is enabled in the subsequent action, an SF event is generated. After the client side of station
B processes the event, the client device reports the ODUk_PM_AIS alarm.
l OTUk_BDI
The OTU detects the OTUk_BDI alarm from the upstream station. This alarm is not sent
to the downstream station.
l ODUk_PM_TIM/ODUk_PM_BDI
The OTU transparently transmits all PM alarms.
l ODUk_PM_AIS/ODUk_PM_LCK/ODUk_PM_OCI
The client side of the OTU at station A receives ODUk_PM_AIS, ODUk_PM_LCK, or
ODUk_PM_OCI signals. The signals are not processed and reported at the local station.
After the signals are sent to station B, the WDM side of the OTU at station B detects the
ODUk_PM_AIS, ODUk_PM_LCK, or ODUk_PM_OCI alarm. Then, an SF event is
generated. The event triggers a protection switching. The alarm is then sent to the
downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS,
ODUk_PM_LCK, or ODUk_PM_OCI alarm to the client equipment.
l R_LOS
The WDM side of the OTU at station B detects the R_LOS alarm. The OTU sends the
OTUk_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then
sent to the client side of station B. After the alarm is processed on the client side, the
ODUk_PM_AIS alarm is detected in the client equipment.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
1.4.4 Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the convergent OTU processes standard SDH
signals.
Figure 1-5 and Figure 1-6 show the alarm signal flows when the convergent OTU processes
NOTE
In Figure 1-5, N#1 indicates channel 1 at optical interface N of the OTU. For example, the client-side
optical interfaces of the LQMD are numbered 3, 4, 5, and 6, and the WDM-side optical interface of the
LQMD is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical interface 3. 1#N indicates
channel N at WDM-side optical interface 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-
side optical interface 1.
Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and thus
is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In
the middle part of the convergent OTU, the optical interface numbers and channel numbers of signals are
reallocated.
NOTE

Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Client-side Middle WDM-side WDM-side Middle Client-side Client-device
R_LOS
N#1 R_LOS N#1 REM_SF N#1 R_LOF
R_LOS N#1 R_LOS N#1 REM_SF N#1 R_LOF
R_LOS
N#1 R_LOS N#1 REM_SF N#1 R_LOF
R_LOF
N#1 R_LOF N#1 REM_SF N#1 R_LOF
R_LOC
N#1 R_LOC N#1 REM_SF N#1 R_LOF
SD
Errors
N#1 Errors 1#N BIT Errors Errors
A
N#1 A 1#N A A
B
N#1 B 1#N B B
C
N#1 C 1#N C C
D
N#1 D 1#N D D
A, B, C, D are the others of the SDH alarms
SF:SF event detecting SD:SD event detecting Alarm processing
xxx Detects and reports the xxx alarm.
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
l Four channels of R_LOS signals are accessed on the client side.

The OTU at station A accesses four channels of R_LOS signals on the client side. After
being processed in the middle part of the OTU at station A, the alarm signals are then sent
to station B. The REM_SF alarm is generated on the client side of station B. The R_LOF
alarm is detected in the client equipment.
l One channel of R_LOS signals are accessed on the client side.
The OTU at station A accesses one channel of R_LOS signals on the client side, for
example, channel 1 at optical interface 3. After being processed in the middle part and on
the WDM side of the OTU at station A and the WDM side of station B, the alarm signals
are then sent to the downstream station. The REM_SF alarm of channel 1 at optical interface
3 is generated on the client side of station B. The R_LOF alarm is detected in the client
equipment.
l Non-R_LOS signals are accessed on the client side.
The signal flow of the R_LOF or the LOC is similar to that of the R_LOS.

When any other alarms are accessed, the same alarm is reported at each detection point in
the system.
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
R_LOF
SF R_LOF
R_LOS
R_LOS
R_LOF
ODUk_PM_BDI&
OTUk_BDI R_LOF
OTUk_LOF/ R_LOF
OTUk_LOM/ SF
OTUk_AIS/ OTUk_LOF/ R_LOF
OTUk_TIM OTUk_LOM/
OTUk_AIS/
OTUk_TIM R_LOF
ODUk_PM_BDI&
R_LOF
OTUk_BDI
R_LOF
ODUk_PM_AIS/
ODUk_PM_LCK/ SF
ODUk_PM_OCI/ ODUk_PM_AIS/ R_LOF
ODUk_PM_TIM ODUk_PM_LCK/
ODUk_PM_OCI/
ODUk_PM_TIM R_LOF
ODUk_PM_BDI R_LOF
Errors
SD
PM BIP8 errors ODUk_PM_DEG/ Errors
ODUk_PM_EXC
Errors
OTUk remote BER

Errors
performance events
Errors
SD
Errors
OTUk_EXC
Errors
PM remote BER
performance events Errors

For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.

l There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, or

ODUk_PM_LCK on the WDM side.
The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU
sends the ODUk_PM_BDI and OTUk_BDI alarm to the WDM side of upstream station A.
In addition, the alarm is then sent to the client side of station B. After the alarm is processed
on the client side, the R_LOF alarm is detected in the client equipment.
l There are bit error alarms on the WDM side.
The OTU at station B accesses and processes bit error alarm signals on the WDM side, and
then sends remote bit error performance events to the WDM side of upstream station A.
The bit error alarm is then sent to the client side of the downstream station B, and the bit
error alarm is detected in the client equipment.
An SD event is generated on the WDM side of the OTU at station B. In this case, users can
determine whether the SD event triggers a service channel protection switching through
proper configuration.
1.4.5 Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the convergent OTU processes standard OTN
signals.
Figure 1-7 and Figure 1-8 show the alarm signal flows when the convergent OTU processes
NOTE
In Figure 1-7, N#1 indicates channel 1 at optical interface N of the OTU. For example, the client-side
optical interfaces of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical interface of
the LQMD unit is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical interface 3. 1#N
indicates channel N at WDM-side optical interface 1 on the OTU. For example, 1#3 indicates channel 3
at WDM-side optical interface 1.
Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and thus
is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In
the middle part of the convergent OTU, the optical interface number and channel number of signals are re-
allocated.
NOTE

Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
R_LOS SF
N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS
R_LOS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS
OTUk_LOM SF
Inserts OTUk_BDI back N#1 OTUk_LOM N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
OTUk_LOF SF
Inserts OTUk_BDI back N#1 OTUk_LOF N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
OTUk_TIM
SF
Inserts OTUk_BDI back N#1 OTUk_TIM
ODUk_PM_AIS
N#1 ODUk_PM_AIS SF
A 1#N A
N#1 A 1#N A
B 1#N B 1#N B
N#1 B
C 1#N C 1#N C
N#1 C
SD
BIT errors
N#1 BIT errors 1#N BIT errors 1#N BIT errors
xxx Detects and reports the xxx alarm A, B, C are the others of the OTN alarms
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
l Four channels of R_LOS signals are accessed on the client side.

The OTU at station A accesses four channels of R_LOS signals on the client side. After
being processed in the middle part and on the WDM side of the OTU at station A, the alarm
signals are then sent to station B. The ODUk_PM_AIS alarm of the corresponding channel
is generated in the middle part of station B. The ODUk_PM_AIS alarm is detected in the
client device.
An SF event is generated in each channel of the OTU at station B, and a protection switching
is triggered.
l One channel of R_LOS, OTUk_LOM or OTUk_LOF signals is accessed on the client side.
The OTU at station A accesses one channel of R_LOS, OTUk_LOM or OTUk_LOF signals
on the client side, for example, channel 1 at optical interface 3. After being processed in
the middle part and on the WDM side of the OTU at station A and the WDM side of station

B, the alarm signals are then sent to the downstream station. The ODUk_PM_AIS alarm
of channel 3 at optical interface 1 is generated in the middle part of station B. The
ODUk_PM_AIS alarm is detected in the client device.
An SF event is generated in each channel of the OTU at station B, and a protection switching
is triggered.
l The alarm signals except for the signals of the R_LOS, OTUk_LOM, and OTUk_LOF
alarms are accessed on the client side.
When any of other alarm signals is accessed, the corresponding alarm is reported at each
detection point in the system.

Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
ODUk_PM_AIS
R_LOS SF ODUk_PM_AIS
R_LOS
ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
&OTUk_BDI
ODUk_PM_AIS
OTUk_LOF/ SF
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS OTUk_LOF/
OTUk_LOM/
OTUk_AIS ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
&OTUk_BDI
ODUk_PM_AIS
ODUk_PM_AIS/ SF
ODUk_PM_LCK/ ODUk_PM_AIS/ ODUk_PM_AIS
ODUk_PM_OCI
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS
ODUk_PM_BDI ODUk_PM_AIS
Errors
SD
PM BIP8 errors Errors
ODUk_PM_DEG/
ODUk_PM_EXC
Errors
PM remote BER
Errors
SD
SM BIP8 errors Errors
OTUk_DEG/
OTUk_EXC
Errors
OTUk remote BER


NOTE
The value of k on the WDM-side is different from that of the client device.
l There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI or

ODUk_PM_LCK on the WDM side.

The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU
sends the ODUk_PM_BDI or OTUk_BDI alarm to the WDM side of upstream station A.
In addition, the alarm is then sent to the client side of station B. After the alarm is processed
on the client side, the ODUk_PM_AIS alarm is detected in the client device.
l There are bit error alarms on the WDM side.
The WDM side of the OTU at station B accesses and processes the bit error alarm signals.
The OTU sends the remote bit error performance events to the WDM side of upstream
station A. The alarm is then sent to the client side of the downstream station B. The error-
dependent alarm is detected in the client device.
An SD event is generated on the WDM side of the OTU at station B, and a protection
1.4.6 Regenerating OTU

This section describes the alarm signal flow of the regenerating OTU.
Figure 1-9 shows the alarm signal flow of the regenerating OTU.
NOTE
The ALS function of the OTU shown in the figure in this section is not enabled.
The non-intrusive monitoring of the board shown in the figure in this section is enabled.

Figure 1-9 Alarm signal flow of the regenerating OTU
Station A Station B(REG) Station C
WDM-side WDM-side1 WDM-side2 WDM-side
MFASframe discontinuous
OTUk_LOM ODUk_PM_AIS
OTUk_BDI
PM TTI byte mismatch PM TTI byte mismatch

ODUk_PM_TIM ODUk_PM_TIM
SM TTI byte mismatch TIM follow-up response is Enabled.

OTUk_TIM ODUk_PM_AIS
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
OTUk_LOF
OTUk_LOF ODUk_PM_AIS
OTUk_BDI
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/ ODUk_PM_AIS/
ODUk_PM_OCI/ ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_LCK
PM BIP8 errors ODUk_PM_DEG/ ODUk_PM_DEG/

ODUk_PM_EXC ODUk_PM_EXC

OTUk_EXC
Excessive bit errors before FEC

BEFFEC_EXC
R_LOS
R_LOS ODUk_PM_AIS
OTUk_BDI

Detects and reports the xxx
xxx
alarm
In the case of the regenerating OTU, all alarms in the SM section are terminated at the local
station and are not sent to the downstream station (except that the OTUk_LOF alarm is inserted
with an ODUk_PM_AIS alarm to the downstream station). Other alarms are then sent to the

downstream station, and are reported on the WDM side of the OTU (except that the R_LOS
alarm is inserted with an ODUk_PM_AIS alarm to the downstream station).
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect

Function
The OTU with the cross-connect function supports the service transmission in the straight-
through mode or the cross-connect mode. The processing of alarm signals in one mode is
different from that in the other mode.
Straight-Through Mode
Figure 1-10 shows the unidirectional signal flow in the straight-through mode.
NOTE
The optical interface number and channel number shown in Figure 1-10 are the numbers that are displayed
on the U2000.
Figure 1-10 OTU with the cross-connect function in the straight-through mode
A B
3#1(RX1) 3#1(TX1)
1#3 1#3
4#1(RX2) 4#1(TX2)
1#4 1(OUT) 1(IN) 1#4
5#1(RX3) 5#1(TX3)
1#5 1#5
6#1(RX4) 6#1(TX4)
1#6 1#6
As shown in Figure 1-10, the four channels of optical signals accessed from RX1-RX4 on unit
A at the upstream station are sent to channels 3-6 that correspond to the OUT port in the straight-
through mode. One channel of optical signals that are input from the IN port on unit B at the
downstream station is demultiplexed into four channels of optical signals, which are then directly
sent to TX1-TX4.
Hence, in the straight-through mode, the REM_SF and REM_SD alarms at the downstream
station indicate that the signals at the corresponding port on the client side at the upstream station
fail or bit errors at this port exceed the threshold. For example, when the services in channel 1
at optical interface 3 on unit A at the upstream station fail, channel 1 at optical interface 3 on
unit B at the downstream station reports the REM_SF alarm.
Cross-Connect Mode
The cross-connect mode is classified into intra-unit cross-connection and inter-unit cross-
connection.
l Intra-unit cross-connection
In Figure 1-11, the cross-connection from RX3 (channel 1 at optical interface 5) on unit
A to OUT (channel 3 at optical interface 1) on unit A is defined as the intra-unit cross-
connection.

l Inter-unit cross-connection
In Figure 1-11, the cross-connection from RX1 (channel 1 at optical interface 3) on unit
C to OUT (channel 6 at optical interface 1) on unit A is defined as the inter-unit cross-
connection. The inter-unit cross-connection is realized by using the backplane.
Figure 1-11 shows the unidirectional signal flow in the cross-connect mode.
Figure 1-11 OTU with the cross-connect function in the cross-connect mode
A B
3#1(RX1) 3#1(TX1)
1#3 1#3
4#1(RX2) 4#1(TX2)
1#4 1(OUT) 1(IN) 1#4
5#1(RX3) 5#1(TX3)
1#5 1#5
6#1(RX4) 6#1(TX4)
1#6 1#6
3#1(RX1)
1#3
4#1(RX2)
1#4
5#1(RX3)
1#5
6#1(RX4)
1#6
In Figure 1-11, the following cross-connections are created:
l Intra-unit cross-connection from RX3 (channel 1 at optical interface 5) on unit A to OUT

(channel 3 at optical interface 1) on unit A
l Inter-unit cross-connection from RX1 (channel 1 at optical interface 3) on unit C to OUT
(channel 6 at optical interface 1) on unit A
The signals that are received from RX3 (channel 1 at optical interface 5) on unit A at the upstream
station are sent to IN (channel 3 at optical interface 1) on unit B at the downstream station. The
signals received from RX1 (channel 1 at optical interface 3) on unit C at the upstream station
are sent to IN (channel 6 at optical interface 1) on unit B at the downstream station.
The meaning of optical channels regarding the REM_SF and REM_SD alarms in the cross-
connect mode is different from that in the straight-through mode. For example, when the services
in channel 1 at optical interface 4 on unit A at the upstream station fail, unit B at the downstream
station reports the REM_SF alarm in channel 1 at optical interface 3; when the services in channel
1 at optical interface 3 on unit C at the upstream station fail, unit B at the downstream station
reports the REM_SF alarm in channel 1 at optical interface 6.
Hence, when a unit reports the REM_SF or REM_SD alarm, query the cross-connections of the
unit at the upstream station to locate the alarm signal source. Then, check whether the client
signal status such as the optical power, fibers and optical modules in the channel at the
corresponding optical interface is normal. If not, take the corresponding maintenance measures.

NOTICE
In any mode, proper configuration must be made on the U2000.
1.4.8 OTU Processing GE Signals

This section describes the alarm signal flow when the OTU board processes Ethernet service
signals.
The GE services are encapsulated into OTN signals or SDH signals after they are accessed on
the client side of the OTU on an Ethernet network. The alarm signal processing when the GE
services are encapsulated into OTN signals differs slightly from the alarm signal processing
when the GE services are encapsulated into SDH signals.
Figure 1-12 and Figure 1-13 show the signal flow when the GE services are encapsulated into
OTN signals and the signal flow when the GE services are encapsulated into SDH signals
respectively.
NOTE

Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals

WDM- WDM-
Client-side Middle Middle Client-side Client-device
side side
Scenario 1: The client sides are in the non-negotiation mode.

R_LOS
R_LOS REM_SF LINK_ERR
LINK_ERR
LINK_ERR None REM_SF
Scenario 2: The client sides are in the auto-negotiation mode.

R_LOS REM_SF
R_LOS LINK_ERR
LINK_ERR
LPT=Enable LINK_ERR LINK_ERR

LINK_ERR
LINK_ERR None None
LPT=Disable
Errors
Errors Errors
SD
PM BIP8 errors
ODUk_PM_DEG/ Errors
ODUk_PM_EXC
PM remote BER
performance events
SD
SM BIP8 errors
OTUk_DEG/ Errors
OTUk_EXC
OTUk remote BER

performance events
SF
R_LOS
R_LOS LINK_ERR
OTUk_BDI&
ODUk_PM_BDI
OTUk_AIS/ SF
OTUk_LOF/ OTUk_AIS/
OTUk_LOM OTUk_LOF LINK_ERR
/
OTUk_BDI& OTUk_LOM
ODUk_PM_BDI
ODUk_PM_AIS/
ODUk_PM_OCI/ SF
ODUk_PM_LCK ODUk_PM_AIS/ LINK_ERR
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_BDI

This section describes the alarm signal flow when the OTU processes the R_LOS and
LINK_ERR alarms. The signal flow for processing other alarms is similar.
l R_LOS

The client sides of the OTUs at station A and station B work in the non-auto-negotiation
mode. The R_LOS alarm signal is received on the client side of the OTU at station A. The
alarm signal is sent to station B after it is processed on the WDM side of the OTU. In this
case, the REM_SF alarm is generated on the client side of the OTU at station B, and the
client equipment at station B reports the LINK_ERR alarm.
The client sides of the OTUs at station A and station B work in the auto-negotiation mode.
The R_LOS alarm signal is received on the client side of the OTU at station A. The alarm
signal is sent to station B after it is processed on the WDM side of the OTU. In this case,
the REM_SF and LINK_ERR alarms are generated on the client side of the OTU at station
B, and the client equipment at station B reports the LINK_ERR alarm.
l LINK_ERR
The client sides of the OTUs at station A and station B work in the non-auto-negotiation
mode. The client signals at station A contain LINK_ERR alarms, and the client signals are
transmitted transparently from station A to the WDM side of the OTU at station B.
The client sides of the OTUs at station A and station B work in the auto-negotiation mode.
In the case of the Ethernet board that supports the LPT function, when the LPT enabling
status is set to Disable, the LINK_ERR alarm is not generated on the client side of the OTU
at station B; when the LPT enabling status is set to Enable, the LINK_ERR alarm is
generated on the client side of the OTU at station B.
Figure 1-13 Alarm signal flow 2: when the OTU processes GE signals
Scenario 1: The client sides are in the non-negotiation mode.

R_LOS
R_LOS REM_SF LINK_ERR
LINK_ERR
LINK_ERR None None
Scenario 2: The client sides are in the auto-negotiation mode.

R_LOS REM_SF
R_LOS LINK_ERR
LINK_ERR
LPT=Enable LINK_ERR LINK_ERR

LINK_ERR
LINK_ERR None None
LPT=Disable
SF
R_LOS
R_LOS None LINK_ERR
MS_BDI
SF: SF event detecting Alarm processing


This section describes the alarm signal flow when the R_LOS alarm is received on the WDM
side of the OTU at station B. The signal flow for processing other alarms is similar to Figure
1-12.
After the R_LOS alarm is received on the WDM side of the OTU at station B, the SF event is
generated. In addition, station B sends the MS_BDI alarm to the WDM side of the OTU at station
A, and the client equipment at station B reports the LINK_ERR alarm.
1.4.9 Optical-Layer Alarm Signal Processing on OTN

This section describes how an OTU board processes optical-layer alarm signals and how the
alarm signals flow.
Certain alarms are specific to the OCh, OMS, or OTS optical layer. This section mainly describes
the association relations between the optical-layer alarms generated by each NE.
The following part describes the alarm association relations in three network scenarios, as shown
in Figure 1-14, Figure 1-15, and Figure 1-16.
Figure 1-14 Scenario I
OTU OTU
OTU
OM OA OA OD
OTU
Client-side equipment
Line-side ODF
Line-side ODF
OTU OTU
SC1 FIU FIU SC1
OTU OTU
OTU
OD OA OA OM
OTU
OTU OTU
Station A Station B
In this scenario, there are two stations. Station A and station B are OTM stations.
In this scenario, the OTS, OMS, and OCh trails are between adjacent nodes.
In case of the following faults, the association relations of alarms are as follows:
l The fiber from station A to station B is cut.
The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A
reports the OTS_BDI alarm.
l At station A, the optical amplifier unit in direction A-to-B is faulty.
The FIU board at station B reports the OTS_LOS-P alarm and the FIU board at station A
reports the OTS_BDI-P alarm.
l At station A, the optical amplifier in direction A-to-B loses input light.

The FIU board at station A inserts the OTS_PMI signal and the FIU board at station B does
not report the OTS_LOS-P alarm.
l At station A, the fiber in direction SC1-to-FIU is cut.
The FIU board at station B reports the OTS_LOS-O alarm and the FIU board at station A
reports the OTS_BDI-O alarm.
l The configuration of TTI to be received at station B is inconsistent with TTI transmitted
by station A.
The FIU board at station B reports the OTS_TIM alarm and the FIU board at station A
l The optical multiplexer (OM) unit at station A is faulty.
The optical demultiplexer (OD) unit at station B reports the OMS_LOS-P alarm and the
OM unit at station A reports the OMS_BDI-P alarm.
l The OTU board at station A is faulty.
The OTU board at station B reports the OCh_LOS-P alarm.
Figure 1-15 Scenario II
OTU OTU
OTU
OM OA OA OD
East line-side ODF
OA OTU
Line-side ODF
Line-side ODF
West line-side
OTU OTU
ODF
FI
SC1 FIU SC1
U FIU SC2 FIU
OTU OTU
OTU
OD OA OA OM
OA OTU
OTU OTU
Station A Station B Station C
In this scenario, there are three stations. Station A and station C are OTM stations, and station
B is an OLA station.
In this scenario, station OLA only amplifies signals and terminates the OTS layer. The OMS
and OCh trails are between station A and station C.
The FIU board at station B reports the OTS_LOS alarm and the OD unit at station C reports
the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A report the
OTS_BDI alarm and OMS_BDI alarm respectively.
The FIU board at station B reports the OTS_LOS-P alarm. The OD unit at station C reports
the OMS_FDI-P or OMS_SSF-P alarm. The FIU board and OM unit at station A report the
OTS_BDI-P alarm and OMS_BDI-P alarm respectively.

The FIU board at station B reports the OTS_LOS-O alarm. The OD unit at station C reports
the OMS_FDI-O or OMS_SSF-O alarm. The FIU board and OM unit at station A report
the OTS_BDI-O alarm and OMS_BDI-O alarm respectively.
by station A.
The FIU board at station B reports the OTS_TIM alarm. The OD unit at station C reports
the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A report the
OTS_BDI alarm and OMS_BDI alarm respectively.
l The OM unit at station A is faulty.
The OD unit at station C reports the OMS_LOS-P alarm and the OM unit at station A
reports the OMS_BDI-P alarm.
The OTU board at station B reports the OCh_LOS-P alarm.
Figure 1-16 Scenario III

West client- East client-
side side
OTU OOO O O OO O
T T T T T T T T OTU
U U U U U U U U
OTU
OM OA OD OM OA OD
OTU
West line-side ODF
East line-side ODF
Line-side ODF
OTU
Line-side ODF
OTU OA WSD9 RMU9 OA

FI FI
FIU FIU SC1
SC1
U U SC2
OTU RMU9 WSD9 OA OTU

OA
OTU
OD OA OA OM
OM OD
OTU
OTU O O O OO O OO
T T T T T T T T OTU
U U U UU U UU
West client- East client-

side side
In this scenario, there are three stations. Station A and station C are OTM stations, and station
B is an ROADM station.
In this scenario, station ROADM adds and drops certain wavelengths. That is, certain
wavelengths are between stations A and B, or stations B and C, and the other wavelengths are
between stations A and C. Hence, certain OCh trails are between stations A and B, or B and C,
and the other OCh trails are between stations A and C.
The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
wavelengths between stations A and C).


The FIU board at station B reports the OTS_LOS-P alarm and the FIU board at station A
reports the OTS_BDI-P alarm. Station C reports the OCh_FDI-P or OCh_SSF-P alarm (for
The FIU board at station B reports the OTS_LOS-O alarm and the FIU board at station A
reports the OTS_BDI-O alarm. Station C reports the OCh_FDI-O or OCh_SSF-O alarm
(for wavelengths between stations A and C).
by station A.
The FIU board at station B reports the OTS_TIM alarm and the FIU board at station A
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
l The OM unit at station A is faulty.
The OD unit at station B reports the OMS_LOS-P alarm and the OM unit at station A
reports the OMS_BDI-P alarm. Station C reports the OCh_FDI-P or OCh_SSF-P alarm
(for wavelengths between stations A and C).
The OTU board at station B reports the OCh_LOS-P alarm (for wavelengths between
stations A and B). The OTU board at station C reports the OCh_LOS-P alarm (for
l The fiber from station B to station C is cut.
The FIU board at station C reports the OTS_LOS alarm and the FIU board at station B
l At station B, the optical amplifier unit in direction B-to-C is faulty.
The FIU board at station C reports the OTS_LOS-P alarm and the FIU board at station B
reports the OTS_BDI-P alarm.
l At station B, the optical amplifier in direction B-to-C loses input light.
The FIU board at station B inserts the OTS_PMI signal and the FIU board at station C does
l At station B, the fiber in direction SC1-to-FIU is cut.
The FIU board at station C reports the OTS_LOS-O alarm and the FIU board at station B
reports the OTS_BDI-O alarm.
l The configuration of TTI to be received at station C is inconsistent with TTI transmitted
by station B.
The FIU board at station C reports the OTS_TIM alarm and the FIU board at station B
l The OM unit at station B is faulty.
The OD unit at station C reports the OMS_LOS-P alarm and the OM unit at station B reports
the OMS_BDI-P alarm.
l The OTU board at station B is faulty.

The OTU board at station C reports the OCh_LOS-P alarm (for wavelengths from station
B to station C).
1.5 Suppression Relation of Alarms

This section describes the rules of alarm suppression and provides the suppression relation figure
of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm
suppression.
When the equipment is faulty, several alarms may be generated by the same optical interface.
However, some alarms are not important for the maintenance engineer. For example, when the
signal is lost, the optical interface generates the R_LOS alarm accompanied with the alarm
indicating that the B1/B2 bit errors cross the threshold. However, the alarm indicating that the
B1/B2 bit errors cross the threshold is not important for the maintenance engineer. In this case,
the equipment suppresses the alarm indicating that the B1/B2 bit errors cross the threshold
through the R_LOS alarm. Only the R_LOS alarm is reported by the optical interface.
The rules of alarm suppression are as follows:

l The client-side alarms and the WDM-side alarms are relatively independent. There are no
alarm suppression relation between the client-side alarms and the WDM-side alarms.
l There is no alarm suppression relation between the detection alarms related to the board
hardware and the service alarms.
NOTE
Some alarms for the optical module are exceptional. For example, the R_LOS alarm suppresses the
IN_PWR_LOW alarm.
l There is no alarm suppression relation for the alarms that cannot be generated at the same
time.
1.5.1 Suppression of OTN Alarms

There is no alarm suppression for the alarms of different TCM layers. The R_LOS alarm can
suppress all OTN alarms.
The suppression of OTN alarms is shown in theFigure 1-17.
The alarm above the arrow suppresses the alarm below the arrow. For example, the OTUk_LOM
alarm suppresses the OTUk_TIM alarm.

Figure 1-17 Suppression of OTN alarms
OCH_LOS
OTUk_LOF
OTUk_LOM Note:
The TIM alarm suppresses the
OTUk_SSF
BDI alarm and DEG alarm of
the same layer just when the
TIM follow-up response is
OTUk_TIM Enabled.
OTUk_BDI ODUk_LOFLOM OTUk_DEG
ODUk_TCMn_LTC/
ODUk_TCMn_LCK/ ODUk_TCMn_SSF
ODUk_TCMn_OCI
ODUk_TCMn_TIM
ODUk_TCMn_BDI ODUk_TCMn_DEG
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_SSF
ODUk_PM_TIM
ODUk_PM_BDI ODUk_PM_DEG
OPUk_PLM
OPUk_MISM

1.5.2 Suppression of Alarms Related to SDH Services and Other

Common Equipment Alarms
The suppression of SDH service alarms and other common alarms related to equipment alarms
is shown in Figure 1-18.
The alarm above the arrow suppresses the alarm below the arrow. For example, when an optical
interface on the client side loses signals, the optical interface only reports the R_LOS alarm. The
R_LOC and R_LOF alarms are not reported.
Figure 1-18 Suppression of alarms related to SDH services and other common equipment alarms
PORT_MODULE_OF
FLINE
LSR_COOL_ALM
TEM_HA/TEM_LA
IN_PWR_HIGH/
OUT_PWR_HIGH
TF LSR_WILL_DIE
OUT_PWR_LOW TD
R_LOS
IN_PWR_LOW
R_LOC
R_LOF
BEFFEC_EXC
J0_MM
MS_REI
B2_EXC
B1_EXC
MS_AIS MS_RDI
B1_SD
B2_SD

1.6 Performance Event Suppression by Alarms

An optical interface can report several alarms and performance events. Some performance events
are not important for the maintenance engineer.
When the equipment is faulty, several alarms and performance events may be generated by the
same optical interface. However, some alarms and performance events are not important for the
maintenance engineer. For example, when the signal is lost, the optical interface generates the
R_LOS alarm accompanied with the B1/B2 bit error performance event. However, the B1/B2
bit error performance event is not important for the maintenance engineer. In this case, the
equipment suppresses the B1/B2 bit error performance event through the R_LOS alarm. Only
the R_LOS alarm is reported by the optical interface.
Table 1-4 lists the performance events suppressed by the R_LOS alarm.
Table 1-4 Performance events suppressed by the R_LOS alarm
MSBBE MSFEBBE RSCSES
MSES MSFEUAS RSOFS
MSSES RSBBE FEC_AFT_COR_ER
MSFEES RSES FEC_BEF_COR_ER
MSFESES RSSES
Table 1-5 lists the performance events suppressed by the NO_BD_PARA alarm.
Table 1-5 Performance events suppressed by the NO_BD_PARA alarm
LSBIASCUR LSCLCCUR LSTMPCUR
LSBIASMAX LSCLCMAX LSTMPMAX
LSBIASMIN LSCLCMIN LSTMPMIN

Alarms and Performance Events Reference 2 Alarm List
2 Alarm List
About This Chapter
This chapter describes the alphabetical lists of alarms and lists alarms of every board.
2.1 Product Alarm List

This section lists the alarms supported by the product in alphabetical order.
2.2 Board Alarm List

Lists the alarms of every board.

2.1 Product Alarm List

This section lists the alarms supported by the product in alphabetical order.
2.1.1 Alarm List A

This section used a table to list the alarms starting with A.
Name Description Level Board
AD_CHECK_FAIL AD (analog to digital Major CRPC

converter) self check
failure
ALM_ALS Automatic laser Minor SF64A, SLH41, SLO16,

shutdown (ALS) SLQ64, SF64, SFD64, SL64,
alarm LD64, SLQ16
ALM_GFP_dCSF The loss of GFP Critica EGSH

client signal l
ALM_GFP_dLFD The loss of GFP Major EGSH

frame delineation
ALM_HANGUP The orderwire phone Minor SC1, SC2

is in the off-hook
state for a long time
APS_MANUAL_STO The MSP protocol is Minor SCC

P manually stopped
APS_FAIL APS protection Major SCC

switching failure
APS_INDI An alarm indicating Major SCC

the APS state
AU_AIS AU alarm indication Major EGSH, SF64A, SLH41, SLO16,

signal SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
AU_LOP AU loss of pointer Major EGSH, SF64A, SLH41, SLO16,

SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
2.1.2 Alarm List B

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

B1_EXC Regenerator section Minor LDM, LDMD, LDMS, LDX,

(B1) excessive errors LQM, LQMD, LQMS, LSX,
LSXL, LWXS, SF64A, SLH41,
SLO16, SLQ64, TDX, TMX,
TOM, TQX, SF64, SFD64,
SL64, LD64, SLQ16
B1_SD Regenerator section Minor LDM, LDMD, LDMS, LDX,

(B1) signal degraded LQM, LQMD, LQMS, LSX,
SLO16, SLQ64, TDX, TMX,
TOM, TQX, SF64, SFD64,
SL64, LD64, SLQ16
B2_EXC Multiplex section Major SF64A, SLH41, SLO16,

(B2) excessive errors SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
B2_SD Multiplex section Minor SF64A, SLH41, SLO16,

(B2) signal degraded SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
B3_EXC The number of higher Major SF64A, SLH41, SLO16,

order path B3 bit SLQ64, SF64, SFD64, SL64,
errors in the signals LD64, SLQ16
received on the line
exceeds the threshold
B3_EXC_VC3 The number of B3 bit Major EGSH

errors in the lower
order path VC-3
exceeds the
threshold.
B3_EXC_VC4 The number of B3 bit Major EGSH

errors in the VC-4
path exceeds the
threshold.
B3_SD The higher order path Minor SF64A, SLH41, SLO16,

B3 signals received SLQ64, SF64, SFD64, SL64,
on the line are LD64, SLQ16
degraded.
B3_SD_VC3 The number of VC-3 Minor EGSH

B3 bit errors exceeds
the threshold.
B3_SD_VC4 The number of B3 bit Minor EGSH

errors in the VC-4
path exceeds the
threshold.

BD_NOT_INSTALLE Logic board not Minor SCC

D installed alarm
BD_STATUS Board out of position Major All Boards
BDID_ERROR An alarm of slot Major EGSH

verification error
BEFFEC_EXC Signal degraded Minor LDM, LDMD, LDMS, LDX,

before FEC LOG, LOM, LQM, LQMD,
LQMS, LSX, LSXL, LSXLR,
LSXR, ND2, NQ2, NS2, NS3,
SF64, SFD64, TDX, TMX,
TOM, TQX
BOOTROM_BAD BOOTROM data Major EGSH, SCC

check failed
BUS_ERR Bus error Critica LOG, LQM, LQMD, LQMS,

l LSXL, LSXLR, ND2, NQ2,
NS2, NS3, SF64A, SLH41,
SLO16, SLQ64, SF64, SFD64,
SL64, SLD64, SLQ16, SXM,
TOG, TDX, TOM, TQX, XCH,
XCM, XCT
2.1.3 Alarm List C

This section used a table to list the alarms starting with C.
C2_VCAIS A C2 byte alarm Minor SF64A, SLH41, SLO16,

indication SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
CHAN_ADD Channel of single Major MCA4, MCA8

wave signal add
CHAN_LOS Channel of single Critica MCA4, MCA8

wave signal loss l
CHIP_ABN Temperature chip Minor EGSH

failure
CLIENT_PROT_NOT Client-side 1+1 Minor LDM, LDMD, LDMS, LDX,

START protection group not LOG, LOM, LQM, LQMD,
started LQMS, LSX, LSXL, LWXS,
TDX, TMX, TOM, TQX, TOG

CLIENT_PORT_PS Client-side 1+1 Major DCP, LDM, LDMD, LDMS,

protection switching LDX, LOG, LOM, LQM,
LQMD, LQMS, LSX, LSXL,
LWXS, OLP, TDX, TMX,
TOM, TQX, TOG
CLIENT_PORT_STA The state of the Minor DCP, LDM, LDMD, LDMS,

_INDI client-side 1+1 LDX, LOG, LOM, LQM,
optical channel LQMD, LQMS, LSX, LSXL,
protection group LWXS, OLP, TDX, TMX,
TOM, TQX, TOG
CLK_NO_TRACE_M The clock enters into Minor STG

ODE a non-tracing running
mode.
COMMUN_FAIL Internal Major AUX, CRPC, D40, D40V, DCP,

communication EGSH, FIU, GFU, HBA, HSC1,
failure on the board ITL, LDM, LDMD, LDMS,
LDX, LOG, LOM, LQM,
LSXLR, LSXR, LWXS, M40,
M40V, MCA4, MCA8, ND2,
NQ2, NS2, NS3, OAU1, OBU1,
OBU2, OLP, RDU9, RMU9,
ROAM, SC1, SC2, SCC,
SF64A, SLH41, SLO16,
SLD64, SLQ16, SXM, STG,
TDC, TDX, TMX, TOG, TOM,
TQX, VA1, VA4, WMU,
WSD9, WSM9, WSMD2,
WSMD4, XCH, XCM, XCT
CPC_NODE_ID_ERR Node ID Error Critica SCC

l
CRC4_CROSSTR CRC4 multi-frame Minor HSC1, SC1, SC2

error code count
2.1.4 Alarm List D

This section used a table to list the alarms starting with D.

DB_RESTORE_FAIL Database restore fail Major SCC

alarm
DBMS_ERROR Database error alarm Major SCC
DBMS_PROTECT_M Database in protect Critica SCC

ODE mode l
DCM_INSUFF Insufficient Minor LSXL, LSXLR, NS3, TDC

dispersion
compensation
margin
DLAG_PROTECT_F DLAG protect failed Major EGSH

AIL alarm
DSP_LOAD_FAIL DSP software Major OAU1, OBU1

loading failure
2.1.5 Alarm List E

This section used a table to list the alarms starting with E.
ETH_8B10B_ERR Ethernet line signal Minor LDM, LDMD, LDMS, LQM,

encoding/decoding LQMD, LQMS, TOG, TOM
error
ETH_CFM_LOC Service connectivity Critical EGSH

loss
ETH_CFM_MISME Misconnection Critical EGSH

RGE
ETH_CFM_MACST Remote MAC defect Major EGSH

ATUS indication
ETH_CFM_RDI A remote CFM_OAM Minor EGSH

alarm indication
ETH_CFM_UNEXP Errored frame Minor EGSH

ERI
ETHOAM_DISCOV The point-to-point Minor EGSH

ER_FAIL Ethernet OAM
discovery failure
alarm

ETHOAM_RMT_C A critical fault occurs Minor EGSH

RIT_FAULT on the remote end of
point-to-point
Ethernet OAM
ETHOAM_RMT_L The remote loopback Minor EGSH

OOP of point-to-point
Ethernet OAM alarm
ETHOAM_RMT_S The remote SD of Minor EGSH

D point-to-point
Ethernet OAM alarm
ETHOAM_SELF_L Loopback of the MAC Major EGSH

OOP port that receives the
OAM protocol
packets in a point-to-
point manner
ETHOAM_VCG_SE Loopback of the Major EGSH

LF_LOOP VCTRUNK port that
receives the OAM
protocol packets in a
point-to-point manner
EX_ETHOAM_CC_ Loss of the periodic Critical EGSH

LOS continuity check
message
EX_ETHOAM_MPI The maintenance Major EGSH

D_CNFLCT point ID conflict
EXT_SYNC_LOS The loss of external Critical STG

clock source
EXT_TIME_LOC The loss of the Major STG

external timing source
2.1.6 Alarm List F

This section used a table to list the alarms starting with F.
FAN_FAIL Fan failed Major CRPC, FAN
FAN_FAULT Fan fault Minor FAN
FC_8B10BERR_OVE 8B10B bit error rate Minor LOM

R crossing alarm

FC_LINK_ERR FC service link Critica LOM

failure alarm l
FC_SYNC_LOS FC service Critica LDX, LOM

synchronous word l
loss alarm
FCS_ERR The frame check Critica EGSH

sequence (FCS) is l
incorrect
FEC_LOF Received FEC is loss Critica SF64A, SF64, SFD64

of frame l
FEC_OOF Received FEC is out Critica SF64A, SF64, SFD64

of frame l
FPGA_ABN FPGA status is Major CRPC

abnormal
FSELECT_STG The clock board is Major SF64A, SLH41, SLO16,

forcibly selected SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
FWD_PKT_LOSS Packets droped Minor EGSH

alarms
2.1.7 Alarm List G

This section used a table to list the alarms starting with G.
GAINDATA_MIS Mismatch of gain Major HBA, OAU1, OBU1, OBU2

attribute
2.1.8 Alarm List H

This section used a table to list the alarms starting with H.

HARD_BAD Hardware failed Critica AUX, D40, D40V, DCP, EGSH,

l FIU, HBA, HSC1, ITL, LDM,
LDMD, LDMS, LDX, LOG,
LOM, LQM, LQMD, LQMS,
LSX, LSXL, LSXLR, LSXR,
LWXS, M40, M40V, MCA4,
MCA8, ND2, NQ2, NS2, NS3,
OAU1, OBU1, OBU2, OLP,
RDU9, RMU9, ROAM, SC1,
SC2, SCC, SF64A, SLH41,
SLO16, SLQ64, STG, SF64,
SFD64, SL64, LD64, SLQ16,
SXM, TDC, TDX, TMX, TOG,
TOM, TQX, VA1, VA4, WMU,
WSD9, WSM9, WSMD2,
HARD_ERR Minor hardware error Minor AUX, D40, D40V, DCP, EGSH,
FIU, HBA, HSC1, ITL, LDM,
WSD9, WSM9, WSMD2,
HP_LOM Loss of multiframe in Major SF64A, SLH41, SLO16,

the higher order path SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
HP_RDI A remote defect in Minor EGSH, SF64A, SLH41, SLO16,

the higher order path SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
HP_REI A remote error Warni SF64A, SLH41, SLO16,

indication in the ng SLQ64, SF64, SFD64, SL64,
higher order path LD64, SLQ16
HP_SLM A signal label Minor EGSH, SF64A, SLH41, SLO16,

mismatch alarm in SLQ64, SF64, SFD64, SL64,
the higher order path LD64, SLQ16

HP_TIM A trace identifier Minor SF64A, SLH41, SLO16,

mismatch alarm in SLQ64, SF64, SFD64, SL64,
the higher order path LD64, SLQ16
HP_UNEQ An alarm indicating Minor EGSH, SF64A, SLH41, SLO16,

that no signals are SLQ64, SF64, SFD64, SL64,
loaded in the higher LD64, SLQ16
order path
HSC_UNAVAIL Working/protection Minor SCC

switching failed
2.1.9 Alarm List I

This section used a table to list the alarms starting with I.
IN_PWR_HIGH Input optical power is Critica EGSH, HSC1, LDM, LDMD,

too high l LDMS, LDX, LOG, LOM,
LQM, LQMD, LQMS, LSX,
LSXL, LSXLR, LSXR, LWXS,
ND2, NQ2, NS2, NS3, RDU9,
SC1, SC2, SF64A, SLH41,
SL64, LD64, SLQ16, TDC,
TDX, TMX, TOG, TOM, TQX
IN_PWR_LOW Input optical power is Critica EGSH, HSC1, LDM, LDMD,

excessively low l LDMS, LDX, LOG, LOM,
ND2, NQ2, NS2, NS3, RDU9,
SL64, LD64, SLQ16, TDC,
INTRA_OTU_PS Intra-OTU 1+1 Major DCP, LDM, LDMD, LQM,

protection switching LQMD, LWXS, OLP, TOM
INTRA_OTU_STA_I The state of the Intra- Minor DCP, LDM, LDMD, LQM,
NDI OTU 1+1 optical LQMD, LWXS, OLP, TOM
channel protection
group

2.1.10 Alarm List J

This section used a table to list the alarms starting with J.
J0_MM J0 byte or trace Minor LDM, LDMD, LDMS, LDX,

indicator mismatch LQM, LQMD, LQMS, LSX,
SL64, LD64, SLQ16, TDX,
TMX, TQX, TOM
2.1.11 Alarm List K

This section used a table to list the alarms starting with K.
K1_K2_M The K1 and K2 bytes Minor SCC

mismatch alarm
K2_M The K2 bytes Minor SCC

mismatch alarm
2.1.12 Alarm List L

This section used a table to list the alarms starting with L.
L_SYNC Loss of Critica LDM, LDMS, LDMD, LSX,

synchronization l LOG, LQG, LOM, LQMS,
alarm LQMD, TOM, TOG
LAG_PORT_FAIL Aggregation group Minor EGSH

VCG port failure
alarm
LAN_LOC Ethernet Major EFI1, EFI2

communication
failure
LASER_HAZARD_W Warning indication Critica CRPC, HBA, OAU1, OBU1,

ARNING of the laser hazard l OBU2
level.

LASER_MODULE_ Optical module Major EGSH, LDM, LDMD, LDMS,

MISMATCH mismatch alarm LDX, LOG, LOM, LQM,
LQMD, LQMS, LSX, NQ2,
ND2, SF64A, SLH41, SLO16,
LD64, SLQ16, TDX, TMX,
TOG, TOM, TQX
LASER_SHUT The laser of the board Major SF64A, SLH41, SLO16,

is shut down SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
LCAS_FOPR The failure of the Major EGSH

LCAS protocol in the
receive direction
LCAS_FOPT The failure of the Major EGSH

LCAS protocol in the
transmit direction
LCAS_PLCR Partial loss of Minor EGSH

capacity in the LCAS
receive direction
LCAS_PLCT Partial loss of Minor EGSH

transmit direction
LCAS_TLCR The total loss of Major EGSH

receive direction
LCAS_TLCT Total loss of capacity Major EGSH

in the LCAS transmit
direction
LINK_ERR Incorrect data link Critica EGSH, LDM, LDMD, LDMS,

l LOG, LOM, LQM, LQMD,
LQMS, TOM
LOCAL_FAULT Local fault Minor LDX, LSX, TDX, TQX
LOCKPOW_MIS Mismatch of lock- Major CRPC

power attribute
LOCK_CUR_FAIL Pump drive current Critica CRPC

unlocked alarm l

LOOP_ALM Indication of loop Minor EGSH, HSC1, LDM, LDMD,

operating LDMS, LDX, LOG, LOM,
LSXL, LWXS, ND2, NQ2, NS2,
NS3, SC1, SC2, SF64A, SLH41,
TMX, TOG, TOM, TQX
LP_RDI_VC3 Aremote defect Minor EGSH

indication in the
VC-3 lower order
path
LP_SLM_VC3 A signal label Minor EGSH

mismatch alarm in
the VC-3 lower order
path
LP_UNEQ_VC3 No payload is Minor EGSH

equipped in the VC-3
lower order path
LPT_ACTIVE LPT switching is Major LDM, LDMD, LDMS, LDX,

active LOG, LOM, LQM, LQMD,
LQMS, LSX, TDX, TOM, TQX
LPT_RFI A remote failure Critica EGSH

indication alarm of l
link state pass
through
LSR_COOL_ALM Cooling current of Major HSC1, LDMD, LDMS, LDX,

the laser over LOG, LOM, LQMD, LQMS,
threshold LSX, LWXS, SF64A, SLH41,
SL64, LD64, SLQ16, TMX
LSR_FORCE_OPEN Laser forced open Minor LDM, LDMD, LDMS, LDX,

LOG, LOM, LQM, LQMD,
LSXR, LWXS, ND2, NQ2, NS2,
NS3, TDX, TMX, TOG, TOM,
TQX
LSR_INVALID Invalid optical Critica EGSH, LDM, LDMD, LDMS,

module alarm l LDX, LOG, LOM, LQM,
LQMD, LQMS, LSX, TDX,
TMX, TOG, TOM, TQX

LSR_WILL_DIE Laser will be out of Critica CRPC, EGSH, HSC1, LDM,

work l LDMD, LDMS, LDX, LOG,
LWXS, ND2, NQ2, NS2, NS3,
TMX, TOG, TOM, TQX
LTI The loss of Major STG

synchronization
source
2.1.13 Alarm List M

This section used a table to list the alarms starting with M.
MOD_COM_FAIL Module Major D40V, M40V, MCA4, MCA8,

communicates RDU9, ROAM, WSD9,
abnormally WSM9, WSMD2, WSMD4
MODULE_ADJUST_ Adjustment of optical Major RDU9, ROAM, WMU,

FAIL module failed WSD9, WSM9, WSMD2,
WSMD4
MODULE_COOLCU Module cooling Major D40, M40

R_OVER current exceeds the
threshold
MODULE_TEMP_O Module temperature Major D40, D40V, M40, M40V,

VER exceeds the threshold RMU9
MODULEFILE_UPD Updating the Major D40V, HBA, LWXS, M40V,

ATE_FAIL microprogram and MCA4, MCA8, RDU9,
laser parameter table ROAM, WSD9, WSM9,
failed WSMD2, WSMD4
MS_AIS Multiplex section Major LDM, LDMD, LDMS, LQM,

alarm indication LQMD, LQMS, SF64A,
SLH41, SLO16, SLQ64,
SF64, SFD64, SL64, LD64,
SLQ16

MS_APS_INDI_EX An extended Major SCC

indication alarm of
the MSP switching
state
MS_RDI Multiplex section Minor SF64A, SLH41, SLO16,

remote defect SLQ64, SF64, SFD64, SL64,
indication LD64, SLQ16
MS_REI Multiplex section Warning SF64A, SLH41, SLO16,

remote error SLQ64, SF64, SFD64, SL64,
indication LD64, SLQ16
MS_SNCP_PS MS SNCP protection Major LOG, LQM, LQMD, LQMS,

switch TOM
MS_SNCP_STA_IND The state of the MS Minor LOG, LQM, LQMD, LQMS,

I SNCP protection TOM
group
MULTI_RPL_OWNE More than one Minor EGSH

R RPL_OWNER alarm
MUT_LOS Loss of multiplexed Critical D40, D40V, DCP, FIU, HBA,

signals OAU1, OBU1, OBU2, OLP,
RDU9, RMU9, ROAM,
WSD9, WSMD2, WSMD4
2.1.14 Alarm List N

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

and board different
NESF_LOST Lack a set of host Critical SCC

software
NESTATE_INSTAL NE is in install state, Critical SCC

L not configured
NO_BD_PARA No board parameter Critical CRPC, D40, D40V, DCP,

HSC1, M40, M40V, MCA4,
MCA8, OAU1, OBU1, OBU2,
OLP, RMU9, SC1, SC2, WMU

NO_BD_SOFT No board software Critical CRPC, D40, D40V, DCP,

HSC1, LDM, LDMD, LDMS,
LDX, LOG, LOM, LQM,
NQ2, NS2, NS3, OAU1,
OBU1, OBU2, OLP, RMU9,
ROAM, SC1, SC2, SF64A,
SLH41, SLO16, SLQ64, STG,
EGSH, SF64, SFD64, SL64,
LD64, SLQ16, SXM, TDC,
TDX, TMX, TOG, TOM, TQX,
WMU, XCH, XCM, XCT
NO_ELABEL E-label unloaded Warning D40, D40V, DCP, EGSH,

HSC1, LDM, LDMD, LDMS,
LDX, LOG, LOM, LQM,
NQ2, NS2, NS3, OAU1,
OBU1, OBU2, OLP, RMU9,
ROAM, SC1, SC2, STG,
SXM, TDC, TDX, TMX,
TOG, TOM, TQX, WMU,
XCH, XCM, XCT
NESOFT_MM Software difference Major SCC

between working
and protection
boards
NODEID_MM The NODEID_MM Major SCC

is an alarm
indicating the MSP
node ID mismatch
NULL_SEND The NULL signals Minor LDX, LOG, LOM, LSX,

(overhead is LSXL, ND2, NQ2, NS2, NS3,
expressed in all "0"s) TDX, TMX, TOM, TQX
are sent out
2.1.15 Alarm List O

This section used a table to list the alarms starting with O.

OA_LOW_GAIN Optical multiplexed Critica HBA, OAU1, OBU1, OBU2

signal gain low l
OCH_FDI Forward defect Major DCP, LDM, LDMD, LDMS,

indication at OCh LDX, LOG, LOM, LQM,
layer LQMD, LQMS, LSX, LSXL,
LSXLR, LSXR, LWXS, ND2,
OCH_FDI-O Forward defect Minor NQ2, NS2, NS3, OLP, TMX,
indication at OCh TOM
layer (overhead)
OCH_FDI-P Forward defect Minor

indication at OCh
layer (payload)
OCH_LOS-P Loss of signal Critica DCP, LDM, LDMD, LDMS,

(payload) at OCh l LDX, LOG, LOM, LQM,
NQ2, NS2, NS3, OLP, TMX,
TOM
OCH_OCI Open connection Minor DCP, LDM, LDMD, LDMS,

indication at OCh LDX, LOG, LOM, LQM,
NQ2, NS2, NS3, OLP, TMX,
TOM
OCH_SSF Server signal fail at Major DCP, LDM, LDMD, LDMS,

OCh layer LDX, LOG, LOM, LQM,
OCH_SSF-O Server signal fail Minor LSXLR, LSXR, LWXS, ND2,
(overhead) at OCh NQ2, NS2, NS3, OLP, TMX,
layer TOM
OCH_SSF-P Server signal fail Major
(payload) at OCh
layer
ODU_AIS ODU (optical Major SF64A, SF64, SFD64

channel data unit)
alarm indication
signal
ODU_LCK ODU locked Major
ODU_OCI ODU open Major

connection indication
ODU_SNCP_PS ODU SNCP Major LQMS, ND2, NQ2, NS2, NS3,

protection switching TDX, TOM, TQX

ODU_SNCP_STA_IN The state of the ODU Minor LQMS, ND2, NQ2, NS2, NS3,
DI SNCP protection TDX, TOM, TQX
group
ODU0_LOFLOM The FAS and MFAS Critica ND2, NQ2, NS2, NS3, TOG,
are abnormal l TOM
ODU0_PM_AIS ODU0 PM alarm Major

indication signal
ODU0_PM_BDI ODU0 PM backward Minor

defect indication
ODU0_PM_DEG ODU0 PM signal Minor

degraded
ODU0_PM_LCK ODU0 PM signal Minor

locked
ODU0_PM_OCI ODU0 PM open Minor

ODU0_PM_SSF ODU0 PM Server Critica

signal fail l
ODU0_PM_TIM ODU0 PM section Minor

TTI mismatch
ODU1_LOFLOM The FAS and MFAS Critica LDM, LDMD, LDMS, LQM,
are abnormal l LQMD, LQMS, ND2, NQ2,
NS2, NS3, TMX, TOG, TOM
ODU1_PM_AIS ODU1 PM alarm Major
indication signal

defect indication

degraded
ODU1_PM_EXC ODU1 PM section Major LDM, LDMD, LDMS, LQM,

BIP8 excessive error LQMD, LQMS, TOM
defect
ODU1_PM_LCK ODU1 PM signal Minor LDM, LDMD, LDMS, LQM,

locked LQMD, LQMS, ND2, NQ2,
ODU1_PM_SSF ODU1 PM Server Critica

signal fail l


TTI mismatch
ODU1_TCMn_AIS ODU1 TCMn alarm Major LDM, LDMD, LDMS, LQM,

indication signal LQMD, LQMS, ND2, NQ2,
NS2, NS3, TMX, TOM
ODU1_TCMn_BDI ODU1 TCMn Minor
backward defect
indication
ODU1_TCMn_DEG ODU1 TCMn signal Minor

degraded
ODU1_TCMn_EXC ODU1 TCMn section Major LDM, LDMD, LDMS, LQM,

BIP8 excessive error LQMD, LQMS, TOM
defect
ODU1_TCMn_LCK ODU1 TCMn signal Minor LDM, LDMD, LDMS, LQM,

locked LQMD, LQMS, ND2, NQ2,
NS2, NS3, TMX, TOM
ODU1_TCMn_LTC Loss of ODU1 TCMn Minor
serial connection
ODU1_TCMn_OCI ODU1 TCMn open Minor

ODU1_TCMn_SSF ODU1 TCMn Server Critica

signal fail l
ODU1_TCMn_TIM ODU1 TCMn TTI Minor

mismatch
ODU2_LOFLOM The FAS and MFAS Critica LOG, ND2, NS2, NS3, TDX,
are abnormal l TMX
ODU2_PM_AIS ODU2 PM alarm Major LDX, LOG, LOM, LSX, LSXR,

indication signal ND2, NQ2, NS2, NS3, TDX,
TMX, TQX
defect indication

degraded
ODU2_PM_LCK ODU2 PM signal Minor LDX, LOG, LOM, LSX, LSXR,

locked ND2, NQ2, NS2, NS3, TDX,
TMX, TQX
ODU2_PM_SSF ODU2 PM server Critica

signal fail l


TTI mismatch
ODU2_TCMn_AIS ODU2 TCMn alarm Major LDX, LOG, LOM, LSX, LSXR,
indication signal ND2, NQ2, NS2, NS3, TDX,
TMX, TQX
backward defect
indication

degraded
ODU2_TCMn_LCK ODU2 TCMn signal Minor LDX, LOG, LOM, LSX, LSXR,
locked ND2, NQ2, NS2, NS3, TDX,
TMX, TQX
serial connection

ODU2_TCMn_SSF ODU2 TCMn server Critica

signal fail l

mismatch
ODU3_PM_AIS ODU3 PM alarm Major LSXL, LSXLR, NS3

indication signal

defect indication

degraded
ODU3_PM_LCK ODU3 PM signal Minor

locked

ODU3_PM_SSF ODU3 PM section Critica

TTI mismatch l

TTI mismatch
ODU3_PM_EXC ODU3 PM section Major NS3

excessive BIP8 errors
ODU3_TCMn_AIS ODU3 TCMn alarm Major LSXL, LSXLR, NS3

indication signal


backward defect
indication

degraded
ODU3_TCMn_LCK ODU3 TCMn signal Minor

locked

serial connection

ODU3_TCMn_SSF ODU3 TCMn server Critica

signal fail l

mismatch
ODUKSP_PS ODUk SP protection Major ND2, NQ2, NS2, NS3

switch
ODUKSP_STA_INDI The state of the Minor ND2, NQ2, NS2, NS3

ODUk SPRing
protection group
OH_LOOP Overhead bus Minor SF64A, SLH41, SLO16,

loopback SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
OLP_PS Optical line Major OLP

protection switching
OLP_STA_INDI The state of the Minor OLP

optical line
protection group
OMS_BDI Backward defect Minor D40, D40V, ITL, MR2, MR4,

indication at OMS MR8, MR8V, RDU9, RMU9,
layer ROAM, SCS, WSD9, WSMD2,
WSMD4
OMS_BDI-O Backward defect Minor
indication (overhead)
at OMS layer
OMS_BDI-P Backward defect Minor

indication (payload)
at OMS layer

OMS_FDI Forward defect Major

indication at OMS
layer
OMS_FDI-O Forward defect Minor

at OMS layer
OMS_FDI-P Forward defect Major

at OMS layer
OMS_LOS-P Loss of signal Critica D40, D40V, ITL, RDU9, RMU9,

(payload) at OMS l ROAM, SCS, WSD9, WSMD2,
layer WSMD4
OMS_SSF Server signal fail at Major D40, D40V, ITL, MR2, MR4,
OMS layer MR8, MR8V, RDU9, RMU9,
ROAM, SCS, WSD9, WSMD2,
OMS_SSF-O Server signal fail Minor WSMD4
(overhead) at OMS
layer
OMS_SSF-P Server signal fail Major

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

loop is out of lock
OOS_LOST Loss of OOS Minor FIU
OPA_FAIL_INDI Automatic Major CMR2, CMR4, CRPC, D40,

adjustment of power D40V, DCP, DCU, DMR1, FIU,
during optical cross- GFU, HBA, ITL, LDM, LDX,
connection failed LOG, LOM, LQM, LQMD,
LSXR, LWXS, M40, M40V,
MB2, MR2, MR4, MR8, MR8V,
ND2, NQ2, NS2, NS3, OAU1,
OBU1, OBU2, OLP, RDU9,
RMU9, ROAM, SBM2, SCS,
TMX, TOM, TOG, VA1, VA4,
WSD9, WSM9, WSMD2,
WSMD4
OPU0_PLM OPU0 payload Minor TOM, TOG

mismatch
OPU1_PLM OPU1 payload Minor LDM, LDMD, LDMS, LQM,

mismatch LQMD, LQMS, ND2, NQ2,

OPU1_MSIM OPU1 multiplex Minor ND2, NQ2, NS2, NS3, TOM

structure indicator
mismatch
OPU2_MSIM OPU2 multiplex Minor LOM, ND2, NQ2, NS2, NS3,

structure indicator TMX
mismatch
OPU2_PLM OPU2 payload Minor LDX, LOG, LOM, LSX, ND2,

mismatch NQ2, NS2, NS3, TDX, TMX,
TQX
OPU3_MSIM OPU3 multiplex Minor LSXL, LSXLR, NS3

structure indicator
mismatch
OPU3_PLM OPU3 payload Minor LSXL, LSXLR, NS3

mismatch
OSC_LOS Loss of OSC signal Critica HSC1, SC1, SC2

l
OSC_RDI Remote defect Minor HSC1, SC1, SC2

indication
OTU_AIS OTU alarm Major SF64A, SF64, SFD64

indication signal
OTU_LOF Loss of frame Critica SF64A, SF64, SFD64

l
OTU_LOM Loss of Multi-frame Major SF64A, SF64, SFD64
OTU1_AIS OTU1 alarm Major LDM, LDMD, LDMS, LQM,

indication signal LQMD, LQMS, TMX, TOM
OTU1_BDI OTU1 backward Minor

defect indication
OTU1_DEG OTU1 signal Minor

degraded
OTU1_EXC OTU1 BIP8 Major LDM, LDMD, LDMS, LQM,

excessive error defect LQMD, LQMS, TOM
OTU1_LOF The FAS is abnormal Critica LDM, LDMD, LDMS, LQM,

l LQMD, LQMS, TMX, TOM
OTU1_LOM The FAS is abnormal Major
OTU1_SSF OTU1 server signal Critica

fail l
OTU1_TIM OTU1 TTI mismatch Minor

OTU2_AIS OTU2 alarm Major LDX, LOG, LOM, LSX, LSXR,

indication signal ND2, NQ2, NS2, TDX, TMX,
TQX
defect indication

degraded
OTU2_LOF The FAS is abnormal Critica LDX, LOG, LOM, LSX, LSXR,
l ND2, NQ2, NS2, TDX, TMX,
TQX
OTU2_LOM The MFAS is Major
abnormal

fail l
OTU3_AIS OTU3 alarm Major LSXL, LSXLR, NS3

indication signal

defect indication

degraded
OTU3_LOF The FAS is abnormal Critica

l
OTU3_LOM The MFAS is Major

abnormal

fail l
OTU3_EXC OTU3 BIP8 Major NS3

excessive error defect
OTS_BDI Backward defect Minor FIU

indication at OTS
layer
OTS_BDI-O Backward defect Minor

at OTS layer
OTS_BDI-P Backward defect Minor

at OTS layer

OTS_LOS Loss of signal at OTS Critica FIU

layer l
OTS_LOS-O Loss of signal Major

(overhead) at OTS
layer
OTS_LOS-P Loss of signal Critica

(payload) at OTS l
layer
OTS_TIM Trail trace identifier Minor FIU

mismatch at OTS
layer
OUT_PWR_HIGH Output optical power Major CRPC, EGSH, HSC1, LDM,

is too high LDMD, LDMS, LDX, LOG,
OUT_PWR_LOW Output optical power Major LSX, LSXL, LSXLR, LSXR,
is excessively low LWXS, ND2, NQ2, NS2, NS3,
SC1, SC2, TDX, TMX, TOG,
TOM, TQX
OWSP_PS Optical wave share Major DCP

protection switching
OWSP_STA_INDI the state of the optical Minor DCP

wave share
protection group
2.1.16 Alarm List P

This section used a table to list the alarms starting with P.
PATCH_ACT_TIME- Activated patch Minor SCC

OUT overtime
PATCH_DEACT_TI Deactivated patch Minor

MEOUT overtime
PATCH_PKGERR Patch package file Major SCC

error
PM_BDI ODU PM section Major SF64A, SF64, SFD64

backward defect
indication

PM_BEI ODU PM section Major

backward error
indication
PM_BIP8_OVER ODU layer, PM Major

section BIP exceed
the upper threshold
PM_BIP8_SD Optical channel data Major

unit layer, path
monitoring section
bit interleaved parity
signal degraded
PM_TIM ODU layer PM Major

section TTI
mismatch
PORT_MODULE_OF Port module offline Major EGSH, LDM, LDMD, LDMS,

FLINE LDX, LOG, LOM, LQM,
NQ2, NS2, NS3, SF64A,
SLH41, SLO16, SLQ64, SF64,
PORTSWITCH_FAIL Optical switch Major MCA4, MCA8, WMU

switching failure
POWER_ABNORMA Power supply failure Major SF64A, SLH41, SLO16,

L SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
POWER_DIFF_OVE Power difference Major DCP, OLP

R between optical
monitoring active
and standby crossed
the threshold
POWER_FAIL Power failure Major CRPC, PIU, SCC
PRBS_LSS PRBS signal lost Minor LDM, LDMD, LDMS, LDX,

alarm LOG, LOM, LQM, LQMD,
LQMS, LSX, LSXL, ND2, NQ2,
NS2, NS3, TDX, TMX, TOM,
TQX
PUM_TEM_ALM Working temperature Major OAU1, OBU1, OBU2

of the pump laser
over threshold

PUM_BCM_ALM Working current of Major CRPC, OAU1, OBU1, OBU2

pump laser over
threshold
PUMP_COOL_EXC Cooling current of Critica CRPC, OAU1, OBU1, OBU2

pump laser over l
threshold
2.1.17 Alarm List R

This section used a table to list the alarms starting with R.
R_LOC Loss of clock on Critica LDM, LDMD, LDMS, LDX,

receiving line l LOM, LQM, LQMD, LQMS,
LSX, LWXS, SF64A, SLH41,
TMX, TOM, TQX
R_LOF Loss of frame on Critica HSC1, LDM, LDMD, LDMS,

receiving line l LDX, LQM, LQMD, LQMS,
LSX, LSXL, LWXS, SC1, SC2,
TOM, TQX
R_LOS Loss of signal on Critica DCP, EGSH, LDM, LDMD,

receiving line l LDMS, LDX, LOG, LOM,
ND2, NQ2, NS2, NS3, OLP,
LD64, SLQ16, TDC, TDX,
TMX, TOG, TOM, TQX
R_OOF Out of frame on Critica LSXL

receiving line l
R_SLIP Receiving side frame Major HSC1, SC1, SC2

slipping
RELAY_ALARM_CR Critical relay alarm Critica EFI1

ITICAL l

RELAY_ALARM_IG Relay alarm warning Warni

NORE ng
RELAY_ALARM_M Major relay alarm Major

AJOR
RELAY_ALARM_Mi Remote signal Minor

nor degraded
REM_SD Remote signal Minor LDM, LDMD, LDMS, LDX,

degraded LOG, LOM, LQM, LQMD,
LQMS, LSX, LSXL, TDX,
REM_SF Remote signal Minor TMX, TOG, TOM, TQX
Failure
REMOTE_FAULT Remote fault Minor LDX, LSX, TDX, TQX
RS_CROSSTR Regenerator section Minor LDM, LDMD, LDMS, LDX,

performance over LQM, LQMD, LQMS, LSX,
threshold LWXS, TMX, TOM
RTC_FAIL RTC time fail alarm Major SCC
2.1.18 Alarm List S

This section used a table to list the alarms starting with S.
S1_SYN_CHANGE Synchronous source Major STG

changed in S1 mode
SCC_LOC SCC loss of clock Critica HSC1, SC1, SC2

l
SECU_ALM Security alarm Major SCC
SERVICE_CAPACIT The service capacity Major SCC

Y_EXCEED_LICENS exceeds the license
E limit
SERVICE_TYPE_EX The service type Major SCC

CEED_LICENSE exceeds the license
limit
SHELF_AREA_POW Total optical power Critica SCC

ER_OVER consumption of the l
subrack exceeds the
threshold

SLAVE_WORKING The protection board Warni EGSH, SF64A, SLH41, SLO16,

is working ng SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
SM_BDI OTU SM section Major SF64A, SF64, SFD64

backward defect
indication
SM_BEI OTU layer, SM Major

section backward
error indication
SM_BIP8_OVER OTU layer, SM Major

section bit interleaved
parity exceeds
threshold
SM_BIP8_SD OTU layer, SM Major

section bit interleaved
parity deterioration
SM_IAE OTU layer, SM Major

section incoming
alignment error
SM_TIM OTU layer, SM Trail Major

Trace Identifier (TTI)
is mismatched
SNCP_FAIL The SNCP switching Critica SCC

failure l
SO_SK_MISMATCH The number of Critica EGSH

timeslots bundled at l
the LCAS source is
not consistent with
the number of
timeslots bundled at
the LCAS sink
SPEED_OVER Data rate exceeding Major LDM, LDMD, LDMS, LQM,

the set limits LQMD, LQMS, LWXS
STORM_CUR_QUE Alarm storm Major SCC

NUM_OVER
SUBRACK_TYPE_M The configured Major SCC

ISMATCH subrack does not
match the physical
subrack
SUBRACK_ID_CON- Conflict of subrack Critica SCC

FLICT ID l

SUBRACK_ID_MIS- Mismatch of subrack Major SCC

MATCH ID
SUBRACK_LOOP Loop of subrack Critica SCC

l
SUM_INPWR_HI Sum input optical Major D40, D40V, FIU, HBA, OAU1,
power is too high OBU1, OBU2, RMU9, ROAM,
WSD9, WSMD2, WSMD4
SUM_INPWR_LOW Sum input optical Major
power is excessively
low
SW_SNCP_PS SW SNCP protection Major LOG, LQM, LQMD, LQMS,

switching TOM
SW_SNCP_STA_IND The state of the Sub- Minor LOG, LQM, LQMD, LQMS,
I Wavelength SNCP TOM
protection group.
SWDL_ACTIVATED Activation time out Critica SCC

_TIMEOUT l
SWDL_AUTOMATC Automatic match Minor SCC

H_INH inhibited
SWDL_CHGMNG_N SCC board changed Critica SCC

OMATCH l
SWDL_COMMIT_FA Commit failure Minor SCC

IL
SWDL_INPROCESS NE is loading Minor SCC

package
SWDL_NEPKGCHE Loss of file Critica SCC

CK l
SWDL_PKG_NOBD- Board software Minor SCC

SOFT cancelled during the
loading of package
SWDL_PKGVER_M Package version Minor SCC

M conformance check
failed
SWDL_ROLLBACK_ NE rollback failed Minor SCC

FAIL
SYN_BAD A synchronization Minor STG

source degrade alarm
SYNC_FAIL Batch backup failed Minor SCC

SYSPARA_CFDB_N Difference between Minor SCC

OSAME the SCC data and the
CF card data
SYNC_C_LOS The loss of Warni STG

synchronization ng
source level
SYNC_DISABLE Automatic Minor SCC

synchronization of
the system control
board is disabled
SYNC_F_M_SWITC The forced or manual Warni STG

H switching state of a ng
clock source
SYNC_LOCKOFF The clock source in Warni STG

the priority list is ng
locked
SYSPARA_CFDB_N Difference between Minor SCC

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

This section used a table to list the alarms starting with T.
T_LOSEX A board has detected Major EGSH

the loss of signal in
the service bus of the
backplane
T_SLIP Transmitted side Major HSC1, SC1, SC2

frame slipping
TD Transmitter degrade Critica EGSH, HSC1, LDM, LDMD,

l LDMS, LDX, LOG, LOM,
ND2, NQ2, NS2, NS3, TDX,
TMX, TOG, TOM, TQX

TEM_HA Laser temperature is Major EGSH, LDM, LDMD, LDMS,

too high LDX, LOG, LOM, LQM,
LQMD, LQMS, LSX, LSXR,
TOG, TOM, TQX
TEM_LA Laser temperature is Major EGSH, LDM, LDMD, LDMS,

excessively low LDX, LOG, LOM, LQM,
LQMD, LQMS, LSX, LSXR,
TOG, TOM, TQX
TEMP_OVER Working temperature Major D40, D40V, DCP, EGSH, FIU,

over threshold HBA, HSC1, ITL, LDM,
WSD9, WSM9, WSMD2,
TEST_STATUS The board is in the Warni EGSH, SF64A, SLH41, SLO16,

test status ng SLQ64, SF64, SFD64, SL64,
LD64, SLQ16
TF Transmission Failure Critica EGSH, HSC1, LDM, LDMD,

l LDMS, LDX, LOG, LOM,
ND2, NQ2, NS2, NS3, SC1,
SC2, SF64A, SLH41, SLO16,
TOG, TOM, TQX

THUNDERALM Thunder protection Minor PIU

circuit failure
TIME_LOS The loss of the timing Major STG

source level
TIME_NO_TRACE_ The time enters the Minor STG

MODE non-trace mode
TR_LOC The clock of the Major EGSH, SF64A, SLH41, SLO16,

cross-connect board SLQ64, SF64, SFD64, SL64,
is faulty LD64, SLQ16
TS_CFG_MISMATC The timeslot Major LDM, LDMD, LDMS, LOM,

H configuration LQM, LQMD, LQMS, TOM
mismatch alarm
TU_AIS_VC3 A TU alarm Major EGSH

indication signal in
path
TU_LOP_VC3 An alarm indicating Major EGSH

the loss of pointer in
path
2.1.20 Alarm List V

This section used a table to list the alarms starting with V.
VCAT_LOA Delay of multiframes Major EGSH

VCAT_LOM_VC3 The loss of the virtual Major EGSH

concatenation
multiframe in the
VC-3 path
VCAT_LOM_VC4 The loss of the virtual Major EGSH

concatenation
multiframe in the
VC-4 path
VOADATA_MIS Mismatch of Major D40V, M40V, MR8V, OAU1,

attenuation attribute OBU1, OBU2, RMU9, VA1,
VA4, WSD9, WSM9, WSMD2,
WSMD4

VOA_ADJUST_FAIL VOA adjustment Major OAU1

failed
2.1.21 Alarm List W

This section used a table to list the alarms starting with W.
W_R_FAIL Writing or reading Major CRPC

chip register failed
WAVEDATA_MIS Mismatch of wave or Major CMR2, CMR4, D40, D40V,

band attribute DMR1, FIU, HBA, ITL, LDM,
LWXS, M40, M40V, MB2,
MCA4, MCA8, MR2, MR4,
MR8, MR8V, ND2, NQ2, NS2,
NS3, OAU1, OBU1, OBU2,
RDU9, RMU9, ROAM, SBM2,
TMX, TOM, TOG, VA1, VA4,
WSD9, WSM9, WSMD2,
WSMD4
WAVELEN_OVER Wavelength over Critica WMU

threshold l
WRG_BD_TYPE Real board is Major All Boards

mismatched with
configured board
2.1.22 Alarm List X

This section used a table to list the alarms starting with X.
XC_UNSWITCH The cross-connect Major SCC

matrix of the board is
not switched

2.2 Board Alarm List

Lists the alarms of every board.
2.2.1 ATE Board Alarm List

BD_STATUS WRG_BD_TYPE
2.2.2 AUX Board Alarm List

TN51AUX
BD_STATUS HARD_BAD WRG_BD_TYPE
COMMUN_FAIL HARD_ERR
2.2.3 CMR2 Board Alarm List

BD_STATUS WAVEDATA_MIS WRG_BD_TYPE
OPA_FAIL_INDI
2.2.4 CMR4 Board Alarm List

OPA_FAIL_INDI
2.2.5 CRPC Board Alarm List

AD_CHECK_FAI POWER_FAIL
L NO_BD_PARA
BD_STATUS NO_BD_SOFT PUMP_COOL_EXC
COMMUN_FAIL OPA_FAIL_INDI PUM_BCM_ALM
FAN_FAIL OUT_PWR_HIGH WRG_BD_TYPE
FPGA_ABN OUT_PWR_LOW W_R_FAIL

LOCKPOW_MIS LSR_WILL_DIE LASER_HAZARD_WARNING
LOCK_CUR_FAI
L
2.2.6 D40V Board Alarm List

BD_STATUS OMS_BDI NO_ELABEL
COMMUN_FAIL OMS_BDI-O OPA_FAIL_INDI
HARD_BAD OMS_BDI-P OMS_SSF-P
HARD_ERR OMS_FDI SUM_INPWR_HI
MOD_COM_FAIL OMS_FDI-O SUM_INPWR_LOW
MODULE_TEMP_OVER OMS_FDI-P TEMP_OVER
MODULEFILE_UPDATE_ OMS_LOS-P VOADATA_MIS

FAIL
MUT_LOS OMS_SSF WAVEDATA_MIS
NO_BD_PARA OMS_SSF-O WRG_BD_TYPE
NO_BD_SOFT
2.2.7 D40 Board Alarm List

BD_STATUS NO_BD_PARA OPA_FAIL_INDI
COMMUN_FAIL NO_BD_SOFT SUM_INPWR_HI
HARD_BAD NO_ELABEL SUM_INPWR_LOW
HARD_ERR OMS_BDI TEMP_OVER
MODULE_COOLCUR_OV OMS_BDI-O WAVEDATA_MIS

ER
OMS_FDI OMS_BDI-P WRG_BD_TYPE
OMS_FDI-O OMS_LOS-P OMS_SSF-P
OMS_FDI-P OMS_SSF MUT_LOS
MODULE_TEMP_OVER OMS_SSF-O

2.2.8 DCU Board Alarm List

BD_STATUS OPA_FAIL_INDI WRG_BD_TYPE
2.2.9 DCP Board Alarm List

TN11DCP
BD_STATUS NO_BD_SOFT OPA_FAIL_INDI
CLIENT_PORT_PS NO_ELABEL OWSP_PS
CLIENT_PORT_STA_IN- OCH_FDI OWSP_STA_INDI

DI
COMMUN_FAIL OCH_FDI-O OCH_SSF
HARD_BAD OCH_FDI-P OCH_SSF-O
HARD_ERR OCH_LOS-P OCH_SSF-P
INTRA_OTU_PS OCH_OCI POWER_DIFF_OVER
INTRA_OTU_STA_INDI MUT_LOS R_LOS
WRG_BD_TYPE NO_BD_PARA TEMP_OVER
TN12DCP
BD_STATUS NO_BD_SOFT OPA_FAIL_INDI
CLIENT_PORT_PS OCH_FDI OWSP_PS
CLIENT_PORT_STA_IN- OCH_FDI-O OWSP_STA_INDI

DI
COMMUN_FAIL OCH_FDI-P POWER_DIFF_OVER
HARD_BAD OCH_LOS-P R_LOS
HARD_ERR OCH_OCI TEMP_OVER
INTRA_OTU_PS OCH_SSF WRG_BD_TYPE
INTRA_OTU_STA_INDI OCH_SSF-O
NO_BD_PARA OCH_SSF-P

2.2.10 DMR1 Board Alarm List

OPA_FAIL_INDI
2.2.11 EFI1 Board Alarm List

BD_STATUS RELAY_ALARM_IG- WRG_BD_TYPE
NORE
LAN_LOC RELAY_ALARM_MAJOR
RELAY_ALARM_CRITI- RELAY_ALARM_MINOR
CAL
2.2.12 EFI2 Board Alarm List

BD_STATUS WRG_BD_TYPE LAN_LOC
2.2.13 EGSH Board Alarm List

EX_ETHOAM_MPID_CNF
ALM_GFP_dCSF LCT MULTI_RPL_OWNER
ALM_GFP_dLFD FCS_ERR NO_ELABEL
AU_AIS FWD_PKT_LOSS NO_BD_SOFT
AU_LOP HARD_BAD OUT_PWR_HIGH
B3_EXC_VC3 HARD_ERR OUT_PWR_LOW
B3_EXC_VC4 HP_RDI ETH_CFM_UNEXPERI
B3_SD_VC3 HP_SLM ETH_CFM_MACSTATUS
B3_SD_VC4 HP_UNEQ EX_ETHOAM_CC_LOS
BDID_ERROR IN_PWR_HIGH PORT_MODULE_OFFLINE
BD_STATUS IN_PWR_LOW R_LOS
BOOTROM_BAD LAG_PORT_FAIL SLAVE_WORKING
LASER_MODULE_MIS-
CHIP_ABN MATCH SO_SK_MISMATCH

COMMUN_FAIL LCAS_FOPR TD
DLAG_PROTECT_FAIL LCAS_FOPT TEMP_OVER
ETHOAM_DISCOVER_
FAIL LCAS_PLCR TEM_HA
ETHOAM_RMT_CRIT_
FAULT LCAS_PLCT TEM_LA
ETHOAM_RMT_LOOP LCAS_TLCR TEST_STATUS
ETHOAM_RMT_SD LCAS_TLCT TF
ETHOAM_SELF_LOOP LINK_ERR TR_LOC
ETHOAM_VCG_SELF_
LOOP LOOP_ALM TU_AIS_VC3
ETH_CFM_LOC LPT_RFI TU_LOP_VC3
ETH_CFM_MISMERGE LP_RDI_VC3 T_LOSEX
ETH_CFM_RDI LP_SLM_VC3 VCAT_LOA
LSR_INVALID LP_UNEQ_VC3 VCAT_LOM_VC3
LSR_WILL_DIE WRG_BD_TYPE VCAT_LOM_VC4
2.2.14 FAN Board Alarm List

BD_STATUS FAN_FAULT WRG_BD_TYPE
FAN_FAIL
2.2.15 FIU Board Alarm List

TN13FIU
BD_STATUS OTS_BDI-O OTS_LOS-P
OOS_LOST OTS_BDI-P OTS_TIM
OPA_FAIL_INDI OTS_LOS WAVEDATA_MIS
OTS_BDI OTS_LOS-O WRG_BD_TYPE
TN12FIU

BD_STATUS OTS_BDI SUM_INPWR_HI
COMMUN_FAIL OTS_BDI-O SUM_INPWR_LOW
HARD_BAD OTS_BDI-P TEMP_OVER
HARD_ERR OTS_LOS WAVEDATA_MIS
MUT_LOS OTS_LOS-O WRG_BD_TYPE
OOS_LOST OTS_LOS-P
OPA_FAIL_INDI OTS_TIM
2.2.16 GFU Board Alarm List

BD_STATUS OPA_FAIL_INDI WRG_BD_TYPE
COMMUN_FAIL
2.2.17 HBA Board Alarm List

BD_STATUS SUM_INPWR_LOW OPA_FAIL_INDI
COMMUN_FAIL SUM_INPWR_HI TEMP_OVER
GAINDATA_MIS MODULEFILE_UPDATE_FAIL WAVEDATA_MIS
HARD_BAD MUT_LOS WRG_BD_TYPE
HARD_ERR OA_LOW_GAIN LASER_HAZARD_WARN-

ING
2.2.18 HSC1 Board Alarm List

ALM_HANGUP NO_BD_PARA
BD_STATUS NO_BD_SOFT R_LOF
COMMUN_FAIL NO_ELABEL R_SLIP
CRC4_CROSSTR OSC_RDI SCC_LOC
HARD_BAD OSC_LOS TEMP_OVER
HARD_ERR OUT_PWR_HIGH TD
IN_PWR_HIGH OUT_PWR_LOW TF

IN_PWR_LOW LSR_COOL_ALM T_SLIP
LOOP_ALM LSR_WILL_DIE WRG_BD_TYPE
2.2.19 ITL Board Alarm List

TN11ITL
BD_STATUS OMS_FDI-O OMS_SSF-P
OMS_BDI OMS_FDI-P OPA_FAIL_INDI
OMS_BDI-O OMS_LOS-P WAVEDATA_MIS
OMS_BDI-P OMS_SSF WRG_BD_TYPE
OMS_FDI OMS_SSF-O
TN12ITL
BD_STATUS OMS_BDI-P OMS_SSF-O
COMMUN_FAIL OMS_FDI OMS_SSF-P
HARD_BAD OMS_FDI-O OPA_FAIL_INDI
HARD_ERR OMS_FDI-P TEMP_OVER
OMS_BDI OMS_LOS-P WAVEDATA_MIS
OMS_BDI-O OMS_SSF WRG_BD_TYPE
2.2.20 LDM Board Alarm List

B1_EXC ODU1_PM_AIS OUT_PWR_HIGH
B1_SD ODU1_PM_DEG OUT_PWR_LOW
BD_STATUS ODU1_PM_EXC ODU1_PM_BDI
BEFFEC_EXC ODU1_PM_LCK PORT_MODULE_OFFLINE
CLIENT_PROT_NOT- ODU1_PM_OCI PRBS_LSS

START
CLIENT_PORT_PS ODU1_PM_SSF R_LOC
CLIENT_PORT_STA_ ODU1_PM_TIM R_LOF

INDI

COMMUN_FAIL ODU1_TCMn_AIS R_LOS
ETH_8B10B_ERR ODU1_TCMn_BDI REM_SD
HARD_BAD ODU1_TCMn_DEG REM_SF
HARD_ERR ODU1_TCMn_EXC RS_CROSSTR
IN_PWR_HIGH ODU1_TCMn_LCK SPEED_OVER
IN_PWR_LOW ODU1_TCMn_LTC TD
INTRA_OTU_PS ODU1_TCMn_OCI TEM_HA
INTRA_OTU_STA_IN ODU1_TCMn_SSF TEM_LA

DI
J0_MM ODU1_TCMn_TIM TEMP_OVER
L_SYNC OPA_FAIL_INDI TF
LASER_MODULE_MI OPU1_PLM TS_CFG_MISMATCH

SMATCH
LINK_ERR OTU1_AIS OCh_FDI
LOOP_ALM OTU1_BDI OCh_FDI-O
LPT_ACTIVE OTU1_DEG OCh_FDI-P
LSR_FORCE_OPEN OTU1_EXC OCh_LOS-P
LSR_INVALID OTU1_LOF OCh_OCI
LSR_WILL_DIE OTU1_LOM OCh_SSF
MS_AIS OTU1_SSF OCh_SSF-O
NO_BD_SOFT OTU1_TIM OCh_SSF-P
NO_ELABEL NULL_SEND WAVEDATA_MIS
WRG_BD_TYPE ODU1_LOFLOM
NOTE
In the alarms, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
2.2.21 LDMD Board Alarm List

B1_EXC ODU1_LOFLOM OTU1_TIM
B1_SD ODU1_PM_AIS OUT_PWR_HIGH
BD_STATUS ODU1_PM_BDI OUT_PWR_LOW

BEFFEC_EXC ODU1_PM_DEG PORT_MODULE_OFFLINE
CLIENT_PROT_NOT- ODU1_PM_EXC PRBS_LSS

START
CLIENT_PORT_PS ODU1_PM_LCK R_LOC
CLIENT_PORT_STA_ ODU1_PM_OCI R_LOF

INDI
COMMUN_FAIL ODU1_PM_SSF R_LOS
ETH_8B10B_ERR ODU1_PM_TIM REM_SD
HARD_BAD ODU1_TCMn_AIS REM_SF
HARD_ERR ODU1_TCMn_BDI RS_CROSSTR
IN_PWR_HIGH ODU1_TCMn_DEG SPEED_OVER
IN_PWR_LOW ODU1_TCMn_EXC TD
INTRA_OTU_PS ODU1_TCMn_LCK TEM_HA
INTRA_OTU_STA_IN ODU1_TCMn_LTC TEM_LA

DI
J0_MM ODU1_TCMn_OCI TEMP_OVER
L_SYNC ODU1_TCMn_SSF TF
LASER_MODULE_MI ODU1_TCMn_TIM TS_CFG_MISMATCH

SMATCH
LINK_ERR OPU1_PLM OCh_FDI
LOOP_ALM OTU1_AIS OCh_FDI-O
LPT_ACTIVE OTU1_BDI OCh_FDI-P
LSR_COOL_ALM OTU1_DEG OCh_LOS-P
LSR_FORCE_OPEN OTU1_EXC OCh_OCI
LSR_INVALID OTU1_LOF OCh_SSF
LSR_WILL_DIE OTU1_LOM OCh_SSF-O
MS_AIS OTU1_SSF OCh_SSF-P
NO_BD_SOFT NO_ELABEL WAVEDATA_MIS
WRG_BD_TYPE NULL_SEND
NOTE
TCM6.

2.2.22 LDMS Board Alarm List

B1_EXC ODU1_PM_AIS ODU1_PM_BDI
B1_SD ODU1_PM_DEG NULL_SEND
BD_STATUS ODU1_PM_EXC ODU1_LOFLOM
BEFFEC_EXC ODU1_PM_LCK PORT_MODULE_OFFLINE
CLIENT_PROT_NOT- ODU1_PM_OCI PRBS_LSS

START
CLIENT_PORT_PS ODU1_PM_SSF R_LOC
CLIENT_PORT_STA_ ODU1_PM_TIM R_LOF

INDI
COMMUN_FAIL ODU1_TCMn_AIS R_LOS
ETH_8B10B_ERR ODU1_TCMn_BDI REM_SD
HARD_BAD ODU1_TCMn_DEG REM_SF
HARD_ERR ODU1_TCMn_EXC RS_CROSSTR
IN_PWR_HIGH ODU1_TCMn_LCK SPEED_OVER
IN_PWR_LOW ODU1_TCMn_LTC TD
J0_MM ODU1_TCMn_OCI TEM_HA
L_SYNC ODU1_TCMn_SSF TEM_LA
LASER_MODULE_MI ODU1_TCMn_TIM TEMP_OVER

SMATCH
LINK_ERR OPU1_PLM TF
LOOP_ALM OTU1_AIS TS_CFG_MISMATCH
LPT_ACTIVE OTU1_BDI OCh_FDI
LSR_COOL_ALM OTU1_DEG OCh_FDI-O
LSR_FORCE_OPEN OTU1_EXC OCh_FDI-P
LSR_INVALID OTU1_LOF OCh_LOS-P
LSR_WILL_DIE OTU1_LOM OCh_OCI
MS_AIS OTU1_SSF OCh_SSF
NO_BD_SOFT OTU1_TIM OCh_SSF-O
NO_ELABEL OUT_PWR_HIGH OCh_SSF-P
WRG_BD_TYPE OUT_PWR_LOW WAVEDATA_MIS

NOTE
TCM6.
2.2.23 LDX Board Alarm List

B1_EXC OCh_FDI-O OTU2_DEG
B1_SD OCh_FDI-P OTU2_LOF
BD_STATUS OCh_LOS-P OTU2_LOM
BEFFEC_EXC OCh_OCI OTU2_SSF
CLIENT_PORT_PS OCh_SSF OTU2_TIM
CLIENT_PORT_STA_INDI OCh_SSF-O OUT_PWR_HIGH
CLIENT_PROT_NOTSTART OCh_SSF-P OUT_PWR_LOW
COMMUN_FAIL ODU2_PM_AIS OPU2_PLM
FC_SYNC_LOS ODU2_PM_BDI OTU2_AIS
HARD_BAD ODU2_PM_DEG OTU2_BDI
HARD_ERR ODU2_PM_LCK PORT_MODULE_OFF-

LINE
IN_PWR_HIGH ODU2_PM_OCI PRBS_LSS
IN_PWR_LOW ODU2_PM_SSF REM_SD
J0_MM ODU2_PM_TIM REM_SF
LASER_MODULE_MIS- ODU2_TCMn_AIS REMOTE_FAULT

MATCH
LOCAL_FAULT ODU2_TCMn_BDI RS_CROSSTR
LOOP_ALM ODU2_TCMn_DEG R_LOC
LPT_ACTIVE ODU2_TCMn_LCK R_LOF
LSR_COOL_ALM ODU2_TCMn_LTC R_LOS
LSR_FORCE_OPEN ODU2_TCMn_OCI TD
LSR_INVALID ODU2_TCMn_SSF TEMP_OVER
LSR_WILL_DIE ODU2_TCMn_TIM TEM_HA
NO_BD_SOFT OPA_FAIL_INDI TEM_LA
NO_ELABEL OCh_FDI TF
NULL_SEND WRG_BD_TYPE WAVEDATA_MIS

2.2.24 LOG Board Alarm List

TN12LOG
BD_STATUS OCH_FDI-O OTU2_DEG
BEFFEC_EXC OCH_FDI-P OTU2_LOF
BUS_ERR OCH_LOS-P OTU2_LOM
CLIENT_PROT_NOTSTART OCH_OCI OTU2_SSF
CLIENT_PORT_PS OCH_SSF OTU2_TIM
CLIENT_PORT_STA_INDI OCH_SSF-O OUT_PWR_HIGH
COMMUN_FAIL OCH_SSF-P OUT_PWR_LOW
HARD_BAD ODU2_PM_AIS OPU2_PLM
HARD_ERR ODU2_PM_BDI OTU2_AIS
IN_PWR_HIGH ODU2_PM_DEG OTU2_BDI
IN_PWR_LOW ODU2_PM_LCK PORT_MODULE_OFF-

LINE
L_SYNC ODU2_PM_OCI PRBS_LSS
LASER_MODULE_MIS- ODU2_PM_SSF R_LOS

MATCH
LINK_ERR ODU2_PM_TIM REM_SD
LOOP_ALM ODU2_TCMn_AIS REM_SF
LPT_ACTIVE ODU2_TCMn_BDI SW_SNCP_PS
LSR_COOL_ALM ODU2_TCMn_DEG SW_SNCP_STA_INDI
LSR_FORCE_OPEN ODU2_TCMn_LCK TD
LSR_INVALID ODU2_TCMn_LTC TEM_HA
LSR_WILL_DIE ODU2_TCMn_OCI TEM_LA
MS_SNCP_PS ODU2_TCMn_SSF TEMP_OVER
MS_SNCP_STA_INDI ODU2_TCMn_TIM TF
NO_BD_SOFT OPA_FAIL_INDI WAVEDATA_MIS
NO_ELABEL OCH_FDI WRG_BD_TYPE
NULL_SEND
TN11LOG

BD_STATUS OCH_FDI-O OTU2_BDI
BEFFEC_EXC OCH_FDI-P OTU2_DEG
BUS_ERR OCH_LOS-P OTU2_LOF
CLIENT_PROT_NOTSTART OCH_OCI OTU2_LOM
CLIENT_PORT_PS OCH_SSF OTU2_SSF
CLIENT_PORT_STA_INDI OCH_SSF-O OTU2_TIM
COMMUN_FAIL OCH_SSF-P OUT_PWR_HIGH
HARD_BAD ODU2_LOFLOM OUT_PWR_LOW
HARD_ERR ODU2_PM_AIS OPA_FAIL_INDI
IN_PWR_HIGH ODU2_PM_BDI OPU2_PLM
IN_PWR_LOW ODU2_PM_DEG OTU2_AIS
L_SYNC ODU2_PM_LCK PORT_MODULE_OFF-

LINE
LASER_MODULE_MIS- ODU2_PM_OCI PRBS_LSS

MATCH
LINK_ERR ODU2_PM_SSF R_LOS
LOOP_ALM ODU2_PM_TIM REM_SD
LPT_ACTIVE ODU2_TCMn_AIS REM_SF
LSR_COOL_ALM ODU2_TCMn_BDI SW_SNCP_PS
LSR_FORCE_OPEN ODU2_TCMn_DEG SW_SNCP_STA_INDI
LSR_INVALID ODU2_TCMn_LCK TD
LSR_WILL_DIE ODU2_TCMn_LTC TEM_HA
MS_SNCP_PS ODU2_TCMn_OCI TEM_LA
MS_SNCP_STA_INDI ODU2_TCMn_SSF TEMP_OVER
NO_BD_SOFT ODU2_TCMn_TIM TF
NO_ELABEL OCH_FDI WAVEDATA_MIS
NULL_SEND WRG_BD_TYPE
NOTE
TCM6.

2.2.25 LOM Board Alarm List

BD_STATUS OCH_FDI-O OTU2_BDI
BEFFEC_EXC OCH_FDI-P OTU2_DEG
CLIENT_PROT_NOTSTART OCH_LOS-P OTU2_LOF
CLIENT_PORT_PS OCH_OCI OTU2_LOM
CLIENT_PORT_STA_INDI OCH_SSF OTU2_SSF
COMMUN_FAIL OCH_SSF-O OTU2_TIM
FC_8B10BERR_OVER OCH_SSF-P OUT_PWR_HIGH
FC_LINK_ERR ODU2_PM_AIS OUT_PWR_LOW
FC_SYNC_LOS ODU2_PM_BDI NO_ELABEL
HARD_BAD ODU2_PM_DEG NULL_SEND
HARD_ERR ODU2_PM_LCK OCH_FDI
IN_PWR_HIGH ODU2_PM_OCI PORT_MODULE_OFF-

LINE
IN_PWR_LOW ODU2_PM_SSF PRBS_LSS
L_SYNC ODU2_PM_TIM R_LOC
LASER_MODULE_MIS- ODU2_TCMn_BDI R_LOS

MATCH
LINK_ERR ODU2_TCMn_AIS REM_SD
LOOP_ALM ODU2_TCMn_DEG REM_SF
LPT_ACTIVE ODU2_TCMn_LCK TD
LSR_COOL_ALM ODU2_TCMn_LTC TEM_HA
LSR_FORCE_OPEN ODU2_TCMn_OCI TEM_LA
LSR_WILL_DIE ODU2_TCMn_TIM TF
NO_BD_SOFT OPA_FAIL_INDI TS_CFG_MISMATCH
OPU2_PLM OPU2_MSIM WAVEDATA_MIS
OTU2_AIS WRG_BD_TYPE
NOTE
TCM6.

2.2.26 LQMD Board Alarm List

B1_EXC NULL_SEND OTU1_DEG
B1_SD OCH_FDI OTU1_EXC
BD_STATUS OCH_FDI-O OTU1_LOF
BEFFEC_EXC OCH_FDI-P OTU1_LOM
BUS_ERR OCH_LOS-P OTU1_SSF
CLIENT_PROT_NOT- OCH_OCI OTU1_TIM

START
CLIENT_PORT_PS OCH_SSF OUT_PWR_HIGH
CLIENT_PORT_STA_INDI OCH_SSF-O OUT_PWR_LOW
COMMUN_FAIL OCH_SSF-P MS_SNCP_STA_INDI
ETH_8B10B_ERR ODU1_LOFLOM NO_BD_SOFT
HARD_BAD ODU1_PM_AIS NO_ELABEL
HARD_ERR ODU1_PM_BDI PORT_MODULE_OFFLINE
IN_PWR_HIGH ODU1_PM_DEG PRBS_LSS
IN_PWR_LOW ODU1_PM_EXC R_LOC
INTRA_OTU_PS ODU1_PM_LCK R_LOF
INTRA_OTU_STA_INDI ODU1_PM_OCI R_LOS
J0_MM ODU1_PM_SSF REM_SD
L_SYNC ODU1_PM_TIM REM_SF
LASER_MODULE_MIS- ODU1_TCMn_AIS RS_CROSSTR

MATCH
LINK_ERR ODU1_TCMn_BDI SW_SNCP_PS
LOOP_ALM ODU1_TCMn_DEG SW_SNCP_STA_INDI
LPT_ACTIVE ODU1_TCMn_EXC SPEED_OVER
LSR_COOL_ALM ODU1_TCMn_LCK TD
LSR_FORCE_OPEN ODU1_TCMn_LTC TEM_HA
MS_AIS ODU1_TCMn_TIM TF
MS_SNCP_PS OPA_FAIL_INDI TS_CFG_MISMATCH

OTU1_AIS OPU1_PLM WAVEDATA_MIS
OTU1_BDI WRG_BD_TYPE
NOTE
TCM6.
2.2.27 LQMS Board Alarm List

B1_EXC OCH_FDI-O OTU1_DEG
B1_SD OCH_FDI-P OTU1_EXC
BD_STATUS OCH_LOS-P OTU1_LOF
BEFFEC_EXC OCH_OCI OTU1_LOM
BUS_ERR OCH_SSF OTU1_SSF
CLIENT_PROT_NOT- OCH_SSF-O OTU1_TIM

START
CLIENT_PORT_PS OCH_SSF-P OUT_PWR_HIGH
CLIENT_PORT_STA_INDI ODU_SNCP_PS OUT_PWR_LOW
COMMUN_FAIL ODU_SNCP_STA_INDI NO_ELABEL
ETH_8B10B_ERR ODU1_LOFLOM NULL_SEND
HARD_BAD ODU1_PM_AIS OCH_FDI
HARD_ERR ODU1_PM_BDI PORT_MODULE_OFF-

LINE
IN_PWR_HIGH ODU1_PM_DEG PRBS_LSS
IN_PWR_LOW ODU1_PM_EXC RS_CROSSTR
J0_MM ODU1_PM_LCK R_LOC
L_SYNC ODU1_PM_OCI R_LOF
LINK_ERR ODU1_PM_SSF R_LOS
LOOP_ALM ODU1_PM_TIM REM_SD
LPT_ACTIVE ODU1_TCMn_AIS REM_SF
LSR_COOL_ALM ODU1_TCMn_BDI SW_SNCP_PS
LSR_FORCE_OPEN ODU1_TCMn_DEG SW_SNCP_STA_INDI
LSR_WILL_DIE ODU1_TCMn_EXC SPEED_OVER

LSR_INVALID ODU1_TCMn_LCK TD
LASER_MODULE_MIS- ODU1_TCMn_LTC TEM_HA

MATCH
MS_AIS ODU1_TCMn_OCI TEM_LA
MS_SNCP_PS ODU1_TCMn_SSF TEMP_OVER
MS_SNCP_STA_INDI ODU1_TCMn_TIM TF
NO_BD_SOFT OPA_FAIL_INDI TS_CFG_MISMATCH
OTU1_AIS OPU1_PLM WAVEDATA_MIS
OTU1_BDI WRG_BD_TYPE
NOTE
TCM6.
2.2.28 LQM Board Alarm List

B1_EXC OCH_FDI OTU1_EXC
B1_SD OCH_FDI-O OTU1_LOF
BD_STATUS OCH_FDI-P OTU1_LOM
BEFFEC_EXC OCH_LOS-P OTU1_SSF
BUS_ERR OCH_OCI OTU1_TIM
CLIENT_PROT_NOT- OCH_SSF OUT_PWR_HIGH

START
CLIENT_PORT_PS OCH_SSF-O OUT_PWR_LOW
CLIENT_PORT_STA_INDI OCH_SSF-P NO_BD_SOFT
COMMUN_FAIL ODU1_LOFLOM NO_ELABEL
ETH_8B10B_ERR ODU1_PM_AIS NULL_SEND
HARD_BAD ODU1_PM_BDI PORT_MODULE_OFFLINE
HARD_ERR ODU1_PM_DEG PRBS_LSS
IN_PWR_HIGH ODU1_PM_EXC R_LOC
IN_PWR_LOW ODU1_PM_LCK R_LOF
INTRA_OTU_PS ODU1_PM_OCI R_LOS
INTRA_OTU_STA_INDI ODU1_PM_SSF REM_SD

J0_MM ODU1_PM_TIM REM_SF
L_SYNC ODU1_TCMn_AIS RS_CROSSTR
LASER_MODULE_MIS- ODU1_TCMn_BDI SW_SNCP_PS

MATCH
LINK_ERR ODU1_TCMn_DEG SW_SNCP_STA_INDI
LOOP_ALM ODU1_TCMn_EXC SPEED_OVER
LPT_ACTIVE ODU1_TCMn_LCK TD
LSR_FORCE_OPEN ODU1_TCMn_LTC TEM_HA
MS_AIS ODU1_TCMn_TIM TF
MS_SNCP_PS OPA_FAIL_INDI TS_CFG_MISMATCH
MS_SNCP_STA_INDI OPU1_PLM WAVEDATA_MIS
OTU1_BDI OTU1_AIS WRG_BD_TYPE
OTU1_DEG
NOTE
TCM6.
2.2.29 LSXLR Board Alarm List

TN12LSXLR
BD_STATUS OCH_SSF-O OPU3_PLM
BEFFEC_EXC OCH_SSF-P OTU3_AIS
BUS_ERR ODU3_PM_AIS OTU3_BDI
COMMUN_FAIL ODU3_PM_BDI OTU3_DEG
DCM_INSUFF ODU3_PM_DEG OTU3_LOF
HARD_BAD ODU3_PM_LCK OTU3_LOM
HARD_ERR ODU3_PM_OCI OTU3_SSF
IN_PWR_HIGH ODU3_PM_SSF OTU3_TIM
IN_PWR_LOW ODU3_PM_TIM OUT_PWR_HIGH
LSR_FORCE_OPEN ODU3_TCMn_AIS OUT_PWR_LOW

LSR_WILL_DIE ODU3_TCMn_BDI PORT_MODULE_OFF-

LINE
NO_BD_SOFT ODU3_TCMn_DEG R_LOS
NO_ELABEL ODU3_TCMn_LCK TD
OCH_FDI ODU3_TCMn_LTC TEMP_OVER
OCH_FDI-O ODU3_TCMn_OCI TF
OCH_FDI-P ODU3_TCMn_SSF WAVEDATA_MIS
OCH_LOS-P ODU3_TCMn_TIM WRG_BD_TYPE
OCH_OCI OPA_FAIL_INDI
OCH_SSF OPU3_MSIM
NOTE
TCM6.
2.2.30 LSXL Board Alarm List

TN12LSXL
B1_EXC OCH_FDI-P OPU3_PLM
B1_SD OCH_LOS-P OTU3_AIS
BD_STATUS OCH_OCI OTU3_BDI
BEFFEC_EXC OCH_SSF OTU3_DEG
BUS_ERR OCH_SSF-O OTU3_LOF
CLIENT_PROT_NOT- OCH_SSF-P OTU3_LOM

START
CLIENT_PORT_PS ODU3_PM_AIS OTU3_SSF
CLIENT_PORT_STA_IN- ODU3_PM_BDI OTU3_TIM

DI
COMMUN_FAIL ODU3_PM_DEG OUT_PWR_HIGH
DCM_INSUFF ODU3_PM_LCK OUT_PWR_LOW
HARD_BAD ODU3_PM_OCI PORT_MODULE_OFF-

LINE
HARD_ERR ODU3_PM_SSF PRBS_LSS
IN_PWR_HIGH ODU3_PM_TIM R_OOF

IN_PWR_LOW ODU3_TCMn_AIS R_LOF
J0_MM ODU3_TCMn_BDI R_LOS
LOOP_ALM ODU3_TCMn_DEG REM_SD
LSR_FORCE_OPEN ODU3_TCMn_LCK REM_SF
LSR_WILL_DIE ODU3_TCMn_LTC TD
NO_BD_SOFT ODU3_TCMn_OCI TEMP_OVER
NO_ELABEL ODU3_TCMn_SSF TF
NULL_SEND ODU3_TCMn_TIM WAVEDATA_MIS
OCH_FDI OPA_FAIL_INDI WRG_BD_TYPE
OCH_FDI-O OPU3_MSIM
NOTE
TCM6.
2.2.31 LSXR Board Alarm List

BD_STATUS ODU2_PM_AIS OTU2_LOF
BEFFEC_EXC ODU2_PM_BDI OTU2_LOM
COMMUN_FAIL ODU2_PM_DEG OTU2_SSF
HARD_BAD ODU2_PM_LCK OTU2_TIM
HARD_ERR ODU2_PM_OCI OUT_PWR_HIGH
IN_PWR_HIGH ODU2_PM_SSF OUT_PWR_LOW
IN_PWR_LOW ODU2_PM_TIM OCH_SSF
LSR_FORCE_OPEN ODU2_TCMn_AIS OCH_SSF-O
LSR_WILL_DIE ODU2_TCMn_BDI OCH_SSF-P
NO_BD_SOFT ODU2_TCMn_DEG PORT_MODULE_OFF-

LINE
NO_ELABEL ODU2_TCMn_LCK R_LOS
OCH_FDI ODU2_TCMn_LTC TD
OCH_FDI-O ODU2_TCMn_OCI TEM_HA
OCH_FDI-P ODU2_TCMn_SSF TEM_LA

OCH_LOS-P ODU2_TCMn_TIM TEMP_OVER
OCH_OCI OPA_FAIL_INDI TF
OTU2_BDI OTU2_AIS WAVEDATA_MIS
OTU2_DEG WRG_BD_TYPE
NOTE
TCM6.
2.2.32 LSX Board Alarm List

B1_EXC OCH_FDI-O OTU2_DEG
B1_SD OCH_FDI-P OTU2_LOF
BD_STATUS OCH_LOS-P OTU2_LOM
BEFFEC_EXC OCH_OCI OTU2_SSF
CLIENT_PROT_NOT- OCH_SSF OTU2_TIM

START
CLIENT_PORT_PS OCH_SSF-O OUT_PWR_HIGH
CLIENT_PORT_STA_INDI OCH_SSF-P OUT_PWR_LOW
COMMUN_FAIL ODU2_PM_AIS NO_ELABEL
HARD_BAD ODU2_PM_BDI NULL_SEND
HARD_ERR ODU2_PM_DEG OCH_FDI
IN_PWR_HIGH ODU2_PM_LCK PORT_MODULE_OFF-

LINE
IN_PWR_LOW ODU2_PM_OCI PRBS_LSS
J0_MM ODU2_PM_SSF R_LOC
L_SYNC ODU2_PM_TIM R_LOF
LASER_MODULE_MIS- ODU2_TCMn_AIS R_LOS

MATCH
LOCAL_FAULT ODU2_TCMn_BDI REM_SD
LOOP_ALM ODU2_TCMn_DEG REM_SF
LPT_ACTIVE ODU2_TCMn_LCK REMOTE_FAULT
LSR_COOL_ALM ODU2_TCMn_LTC RS_CROSSTR

LSR_FORCE_OPEN ODU2_TCMn_OCI TD
LSR_INVALID ODU2_TCMn_SSF TEM_HA
LSR_WILL_DIE ODU2_TCMn_TIM TEM_LA
NO_BD_SOFT OPA_FAIL_INDI TEMP_OVER
OTU2_AIS OPU2_PLM TF
OTU2_BDI WRG_BD_TYPE WAVEDATA_MIS
NOTE
TCM6.
2.2.33 LWXS Board Alarm List

B1_EXC MODULEFILE_UPDATE_F LSR_WILL_DIE
AIL
B1_SD NO_BD_SOFT PORT_MODULE_OFF-

LINE
BD_STATUS NO_ELABEL RS_CROSSTR
CLIENT_PROT_NOT- OCH_FDI R_LOC

START
CLIENT_PORT_PS OCH_FDI-O R_LOF
CLIENT_PORT_STA_IN- OCH_FDI-P R_LOS

DI
COMMUN_FAIL OCH_LOS-P SPEED_OVER
HARD_BAD OCH_OCI TD
HARD_ERR OCH_SSF TEM_HA
IN_PWR_HIGH OCH_SSF-O TEM_LA
IN_PWR_LOW OCH_SSF-P TEMP_OVER
J0_MM OPA_FAIL_INDI TF
LOOP_ALM OUT_PWR_HIGH WAVEDATA_MIS
LSR_COOL_ALM OUT_PWR_LOW WRG_BD_TYPE
LSR_FORCE_OPEN

2.2.34 M40V Board Alarm List

BD_STATUS MODULEFILE_UPDATE_F MODULE_TEMP_OVER
AIL
COMMUN_FAIL NO_BD_PARA TEMP_OVER
HARD_BAD NO_BD_SOFT VOADATA_MIS
HARD_ERR NO_ELABEL WAVEDATA_MIS
MOD_COM_FAIL OPA_FAIL_INDI WRG_BD_TYPE
2.2.35 M40 Board Alarm List

BD_STATUS NO_BD_PARA MODULE_TEMP_OVER
COMMUN_FAIL NO_BD_SOFT TEMP_OVER
HARD_BAD NO_ELABEL WAVEDATA_MIS
HARD_ERR OPA_FAIL_INDI WRG_BD_TYPE
MODULE_COOLCUR_OV
ER
2.2.36 MCA4 Board Alarm List

BD_STATUS MOD_COM_FAIL PORTSWITCH_FAIL
CHAN_ADD MODULEFILE_UPDATE_F TEMP_OVER

AIL
CHAN_LOS NO_BD_PARA WAVEDATA_MIS
COMMUN_FAIL NO_BD_SOFT WRG_BD_TYPE
HARD_BAD NO_ELABEL HARD_ERR
2.2.37 MCA8 Board Alarm List

BD_STATUS MOD_COM_FAIL HARD_ERR
CHAN_ADD MODULEFILE_UPDATE_F PORTSWITCH_FAIL

AIL
CHAN_LOS NO_BD_PARA TEMP_OVER

COMMUN_FAIL NO_BD_SOFT WAVEDATA_MIS
HARD_BAD NO_ELABEL WRG_BD_TYPE
2.2.38 MR2 Board Alarm List

BD_STATUS OMS_FDI-O OPA_FAIL_INDI
OMS_BDI OMS_FDI-P WAVEDATA_MIS
OMS_BDI-P OMS_SSF-O
OMS_FDI OMS_SSF-P

OMS_BDI-P OMS_SSF-O
OMS_FDI OMS_SSF-P

OMS_BDI-P OMS_SSF-O
OMS_FDI OMS_SSF-P
2.2.41 MR8V Board Alarm List


OMS_BDI OMS_FDI-P VOADATA_MIS
OMS_BDI-O OMS_SSF WAVEDATA_MIS
OMS_BDI-P OMS_SSF-O WRG_BD_TYPE
OMS_FDI OMS_SSF-P
2.2.42 ND2 Board Alarm List

TN52ND2
BD_STATUS ODU1_PM_AIS ODUKSP_PS
BEFFEC_EXC ODU1_PM_BDI ODUKSP_STA_INDI
BUS_ERR ODU1_PM_DEG ODU_SNCP_PS
COMMUN_FAIL ODU1_PM_LCK ODU_SNCP_STA_INDI
HARD_BAD ODU1_PM_OCI OPU1_MSIM
HARD_ERR ODU1_PM_SSF OPU1_PLM
IN_PWR_HIGH ODU1_PM_TIM OPU2_MSIM
IN_PWR_LOW ODU1_TCMn_AIS OPU2_PLM
LOOP_ALM ODU1_TCMn_BDI OPA_FAIL_INDI
LSR_FORCE_OPEN ODU1_TCMn_DEG OTU2_AIS
LSR_WILL_DIE ODU1_TCMn_LCK OTU2_BDI
NO_BD_SOFT ODU1_TCMn_LTC OTU2_DEG
NO_ELABEL ODU1_TCMn_OCI OTU2_LOF
NULL_SEND ODU1_TCMn_SSF OTU2_LOM
OCH_FDI ODU1_TCMn_TIM OTU2_SSF
OCH_FDI-O ODU2_LOFLOM OTU2_TIM
OCH_FDI-P ODU2_PM_AIS OUT_PWR_HIGH
OCH_LOS-P ODU2_PM_BDI OUT_PWR_LOW
OCH_OCI ODU2_PM_DEG ODU0_PM_SSF
OCH_SSF ODU2_PM_LCK ODU0_PM_TIM
OCH_SSF-O ODU2_PM_OCI ODU1_LOFLOM
OCH_SSF-P ODU2_PM_SSF PORT_MODULE_OFFLINE
ODU0_LOFLOM ODU2_PM_TIM PRBS_LSS

ODU0_PM_AIS ODU2_TCMn_AIS R_LOS
ODU0_PM_BDI ODU2_TCMn_BDI TD
ODU0_PM_DEG ODU2_TCMn_DEG TEMP_OVER
ODU0_PM_LCK ODU2_TCMn_LCK TEM_HA
ODU0_PM_OCI ODU2_TCMn_LTC TEM_LA
ODU2_TCMn_SSF ODU2_TCMn_OCI TF
ODU2_TCMn_TIM WRG_BD_TYPE WAVEDATA_MIS
NOTE
TCM6.
2.2.43 NQ2 Board Alarm List

TN54NQ2
BD_STATUS ODU1_PM_AIS ODU_SNCP_STA_INDI
BEFFEC_EXC ODU1_PM_BDI ODU_SNCP_PS
BUS_ERR ODU1_PM_DEG OPA_FAIL_INDI
COMMUN_FAIL ODU1_PM_LCK OPU1_MSIM
HARD_BAD ODU1_PM_OCI OPU1_PLM
HARD_ERR ODU1_PM_SSF OPU2_MSIM
IN_PWR_HIGH ODU1_PM_TIM OPU2_PLM
IN_PWR_LOW ODU1_TCMn_AIS OTU2_AIS
LASER_MODULE_MIS- ODU1_TCMn_BDI OTU2_BDI

MATCH
LOOP_ALM ODU1_TCMn_DEG OTU2_DEG
LSR_FORCE_OPEN ODU1_TCMn_LCK OTU2_LOF
LSR_WILL_DIE ODU1_TCMn_LTC OTU2_LOM
NO_BD_SOFT ODU1_TCMn_OCI OTU2_SSF
NO_ELABEL ODU1_TCMn_SSF OTU2_TIM
NULL_SEND ODU1_TCMn_TIM OUT_PWR_HIGH
OCh_FDI ODU2_PM_AIS OUT_PWR_LOW
OCh_FDI_O ODU2_PM_BDI ODU0_PM_SSF

OCh_FDI_P ODU2_PM_DEG ODU0_PM_TIM
OCh_LOS_P ODU2_PM_LCK ODU1_LOFLOM
OCh_OCI ODU2_PM_OCI PORT_MODULE_OFF-

LINE
OCh_SSF ODU2_PM_SSF PRBS_LSS
OCh_SSF_O ODU2_PM_TIM R_LOS
OCh_SSF_P ODU2_TCMn_AIS TD
ODU0_LOFLOM ODU2_TCMn_BDI TEMP_OVER
ODU0_PM_AIS ODU2_TCMn_DEG TEM_HA
ODU0_PM_BDI ODU2_TCMn_LCK TEM_LA
ODU0_PM_DEG ODU2_TCMn_LTC TF
ODU0_PM_LCK ODU2_TCMn_OCI WAVEDATA_MIS
ODU0_PM_OCI ODU2_TCMn_SSF WRG_BD_TYPE
ODUKSP_PS ODU2_TCMn_TIM
ODUKSP_STA_INDI
TN52NQ2
BD_STATUS ODU1_LOFLOM ODUKSP_PS
BEFFEC_EXC ODU1_PM_AIS ODUKSP_STA_INDI
BUS_ERR ODU1_PM_BDI ODU_SNCP_PS
COMMUN_FAIL ODU1_PM_DEG ODU_SNCP_STA_INDI
HARD_BAD ODU1_PM_LCK OPU1_MSIM
HARD_ERR ODU1_PM_OCI OPU1_PLM
IN_PWR_HIGH ODU1_PM_SSF OPU2_MSIM
IN_PWR_LOW ODU1_PM_TIM OPU2_PLM
LASER_MODULE_MIS- ODU1_TCMn_AIS OPA_FAIL_INDI

MATCH
LOOP_ALM ODU1_TCMn_BDI OTU2_AIS
LSR_FORCE_OPEN ODU1_TCMn_DEG OTU2_BDI
LSR_WILL_DIE ODU1_TCMn_LCK OTU2_DEG
NO_BD_SOFT ODU1_TCMn_LTC OTU2_LOF

NO_ELABEL ODU1_TCMn_OCI OTU2_LOM
NULL_SEND ODU1_TCMn_SSF OTU2_SSF
OCH_FDI ODU1_TCMn_TIM OTU2_TIM
OCH_FDI-O ODU2_PM_AIS OUT_PWR_HIGH
OCH_FDI-P ODU2_PM_BDI OUT_PWR_LOW
OCH_LOS-P ODU2_PM_DEG ODU0_PM_OCI
OCH_OCI ODU2_PM_LCK ODU0_PM_SSF
OCH_SSF ODU2_PM_OCI ODU0_PM_TIM
OCH_SSF-O ODU2_PM_SSF PORT_MODULE_OFF-

LINE
OCH_SSF-P ODU2_PM_TIM PRBS_LSS
ODU0_LOFLOM ODU2_TCMn_AIS R_LOS
ODU0_PM_AIS ODU2_TCMn_BDI TD
ODU0_PM_BDI ODU2_TCMn_DEG TEMP_OVER
ODU0_PM_DEG ODU2_TCMn_LCK TEM_HA
ODU0_PM_LCK ODU2_TCMn_LTC TEM_LA
ODU2_TCMn_SSF ODU2_TCMn_OCI TF
ODU2_TCMn_TIM WRG_BD_TYPE WAVEDATA_MIS
2.2.44 NS2 Board Alarm List

TN52NS2
BD_STATUS ODU1_PM_AIS ODUKSP_STA_INDI
BEFFEC_EXC ODU1_PM_BDI ODU_SNCP_PS
BUS_ERR ODU1_PM_DEG ODU_SNCP_STA_INDI
COMMUN_FAIL ODU1_PM_LCK OPU1_MSIM
HARD_BAD ODU1_PM_OCI OPU1_PLM
HARD_ERR ODU1_PM_SSF OPU2_MSIM
IN_PWR_HIGH ODU1_PM_TIM OPU2_PLM
IN_PWR_LOW ODU1_TCMn_AIS OPA_FAIL_INDI
LOOP_ALM ODU1_TCMn_BDI OTU2_AIS

LSR_FORCE_OPEN ODU1_TCMn_DEG OTU2_BDI
LSR_WILL_DIE ODU1_TCMn_LCK OTU2_DEG
NO_BD_SOFT ODU1_TCMn_LTC OTU2_LOF
NO_ELABEL ODU1_TCMn_OCI OTU2_LOM
NULL_SEND ODU1_TCMn_SSF OTU2_SSF
OCH_FDI ODU1_TCMn_TIM OTU2_TIM
OCH_FDI-O ODU2_PM_AIS OUT_PWR_HIGH
OCH_FDI-P ODU2_PM_BDI OUT_PWR_LOW
OCH_LOS-P ODU2_PM_DEG ODU0_PM_SSF
OCH_OCI ODU2_PM_LCK ODU0_PM_TIM
OCH_SSF ODU2_PM_OCI ODU1_LOFLOM
OCH_SSF-O ODU2_PM_SSF PORT_MODULE_OFFLINE
OCH_SSF-P ODU2_PM_TIM PRBS_LSS
ODU0_LOFLOM ODU2_TCMn_AIS R_LOS
ODU0_PM_AIS ODU2_TCMn_BDI TD
ODU0_PM_BDI ODU2_TCMn_DEG TEMP_OVER
ODU0_PM_DEG ODU2_TCMn_LCK TEM_HA
ODU0_PM_LCK ODU2_TCMn_LTC TEM_LA
ODU0_PM_OCI ODU2_TCMn_OCI TF
ODU2_TCMn_TIM ODU2_TCMn_SSF WAVEDATA_MIS
ODUKSP_PS WRG_BD_TYPE
NOTE
TCM6.
2.2.45 NS3 Board Alarm List

TN52NS3
BD_STATUS ODU1_PM_TIM ODU3_TCMn_OCI
BEFFEC_EXC ODU1_TCMn_AIS ODU3_TCMn_SSF
BUS_ERR ODU1_TCMn_BDI ODU3_TCMn_TIM

COMMUN_FAIL ODU1_TCMn_DEG ODUKSP_PS
DCM_INSUFF ODU1_TCMn_LCK ODUKSP_STA_INDI
HARD_BAD ODU1_TCMn_LTC ODU_SNCP_PS
HARD_ERR ODU1_TCMn_OCI ODU_SNCP_STA_INDI
IN_PWR_HIGH ODU1_TCMn_SSF OPU1_MSIM
IN_PWR_LOW ODU1_TCMn_TIM OPU1_PLM
LOOP_ALM ODU2_LOFLOM OPU2_MSIM
LSR_FORCE_OPEN ODU2_PM_AIS OPU2_PLM
LSR_WILL_DIE ODU2_PM_BDI OPU3_MSIM
NO_BD_SOFT ODU2_PM_DEG OPU3_PLM
NO_ELABEL ODU2_PM_LCK OPA_FAIL_INDI
NULL_SEND ODU2_PM_OCI OTU3_AIS
OCH_FDI ODU2_PM_SSF OTU3_BDI
OCH_FDI-O ODU2_PM_TIM OTU3_DEG
OCH_FDI-P ODU2_TCMn_AIS OTU3_EXC
OCH_LOS-P ODU2_TCMn_BDI OTU3_LOF
OCH_OCI ODU2_TCMn_DEG OTU3_LOM
OCH_SSF ODU2_TCMn_LCK OTU3_SSF
OCH_SSF-O ODU2_TCMn_LTC OTU3_TIM
OCH_SSF-P ODU2_TCMn_OCI OUT_PWR_HIGH
ODU0_LOFLOM ODU2_TCMn_SSF OUT_PWR_LOW
ODU0_PM_AIS ODU2_TCMn_TIM ODU1_PM_LCK
ODU0_PM_BDI ODU3_PM_AIS ODU1_PM_OCI
ODU0_PM_DEG ODU3_PM_BDI ODU1_PM_SSF
ODU0_PM_LCK ODU3_PM_DEG PORT_MODULE_OFFLINE
ODU0_PM_OCI ODU3_PM_LCK PRBS_LSS
ODU0_PM_SSF ODU3_PM_OCI R_LOS
ODU0_PM_TIM ODU3_PM_SSF TD
ODU1_LOFLOM ODU3_PM_TIM TEMP_OVER
ODU1_PM_AIS ODU3_PM_EXC TEM_HA

ODU1_PM_BDI ODU3_TCMn_AIS TEM_LA
ODU1_PM_DEG ODU3_TCMn_BDI TF
ODU3_TCMn_LCK ODU3_TCMn_DEG WAVEDATA_MIS
ODU3_TCMn_LTC WRG_BD_TYPE
NOTE
TCM6.
2.2.46 OAU1 Board Alarm List

TN12OAU1
LASER_HAZARD_WARN- SUM_INPWR_HI
BD_STATUS ING
COMMUN_FAIL OA_LOW_GAIN SUM_INPWR_LOW
GAINDATA_MIS OPA_FAIL_INDI TEMP_OVER
HARD_BAD PUMP_COOL_EXC VOADATA_MIS
HARD_ERR PUM_BCM_ALM VOA_ADJUST_FAIL
MUT_LOS PUM_TEM_ALM WAVEDATA_MIS
NO_BD_PARA NO_BD_SOFT WRG_BD_TYPE
NO_ELABEL
TN11OAU1
BD_STATUS NO_ELABEL SUM_INPWR_LOW
COMMUN_FAIL OA_LOW_GAIN SUM_INPWR_HI
DSP_LOAD_FAIL OPA_FAIL_INDI TEMP_OVER
GAINDATA_MIS PUM_BCM_ALM VOA_ADJUST_FAIL
HARD_BAD PUM_TEM_ALM WAVEDATA_MIS
HARD_ERR PUMP_COOL_EXC WRG_BD_TYPE
MUT_LOS NO_BD_SOFT LASER_HAZARD_W

ARNING
NO_BD_PARA

2.2.47 OBU1 Board Alarm List

TN12OBU1
BD_STATUS NO_ELABEL PUM_TEM_ALM
COMMUN_FAIL OA_LOW_GAIN SUM_INPWR_HI
GAINDATA_MIS OPA_FAIL_INDI SUM_INPWR_LOW
HARD_BAD NO_BD_PARA TEMP_OVER
HARD_ERR NO_BD_SOFT VOADATA_MIS
MUT_LOS PUMP_COOL_EXC WAVEDATA_MIS
LASER_HAZARD_WA PUM_BCM_ALM WRG_BD_TYPE

RNING
TN11OBU1
BD_STATUS NO_BD_SOFT PUM_TEM_ALM
COMMUN_FAIL NO_ELABEL PUMP_COOL_EXC
DSP_LOAD_FAIL OA_LOW_GAIN SUM_INPWR_LOW
GAINDATA_MIS OPA_FAIL_INDI SUM_INPWR_HI
HARD_BAD MUT_LOS TEMP_OVER
HARD_ERR NO_BD_PARA WAVEDATA_MIS
PUM_BCM_ALM LASER_HAZARD_WARN- WRG_BD_TYPE

ING
2.2.48 OBU2 Board Alarm List

BD_STATUS NO_ELABEL PUMP_COOL_EXC
COMMUN_FAIL OA_LOW_GAIN SUM_INPWR_LOW
GAINDATA_MIS OPA_FAIL_INDI SUM_INPWR_HI
HARD_BAD NO_BD_PARA TEMP_OVER
HARD_ERR NO_BD_SOFT VOADATA_MIS
MUT_LOS PUM_BCM_ALM WAVEDATA_MIS
LASER_HAZARD_WA PUM_TEM_ALM WRG_BD_TYPE

RNING

2.2.49 OLP Board Alarm List

TN11OLP
BD_STATUS NO_BD_SOFT OLP_PS
COMMUN_FAIL NO_ELABEL OLP_STA_INDI
CLIENT_PORT_PS OCH_FDI OPA_FAIL_INDI
CLIENT_PORT_STA_IN- OCH_FDI-O INTRA_OTU_STA_INDI

DI
HARD_BAD OCH_FDI-P MUT_LOS
HARD_ERR OCH_LOS-P NO_BD_PARA
INTRA_OTU_PS OCH_OCI POWER_DIFF_OVER
OCH_SSF-O OCH_SSF R_LOS
OCH_SSF-P WRG_BD_TYPE TEMP_OVER
TN12OLP
BD_STATUS NO_BD_PARA OLP_PS
COMMUN_FAIL OCH_FDI OLP_STA_INDI
CLIENT_PORT_PS OCH_FDI-O OPA_FAIL_INDI
CLIENT_PORT_STA_IN- OCH_FDI-P POWER_DIFF_OVER

DI
HARD_BAD OCH_LOS-P R_LOS
HARD_ERR OCH_OCI TEMP_OVER
INTRA_OTU_PS OCH_SSF WRG_BD_TYPE
INTRA_OTU_STA_INDI OCH_SSF-O
MUT_LOS OCH_SSF-P
2.2.50 PIU Board Alarm List

BD_STATUS THUNDERALM WRG_BD_TYPE
POWER_FAIL

2.2.51 RDU9 Board Alarm List

MODULEFILE_UPDATE_
BD_STATUS FAIL OMS_LOS-P
COMMUN_FAIL MUT_LOS OMS_SSF
HARD_BAD OMS_BDI OMS_SSF-O
HARD_ERR OMS_BDI-O OMS_SSF-P
IN_PWR_HIGH OMS_BDI-P OPA_FAIL_INDI
IN_PWR_LOW OMS_FDI TEMP_OVER
MOD_COM_FAIL OMS_FDI-O WAVEDATA_MIS
MODULE_ADJUST_FAIL OMS_FDI-P WRG_BD_TYPE
2.2.52 RMU9 Board Alarm List

BD_STATUS OMS_BDI-O NO_ELABEL
COMMUN_FAIL OMS_BDI-P OMS_BDI
HARD_BAD OMS_FDI OPA_FAIL_INDI
HARD_ERR OMS_FDI-O SUM_INPWR_HI
MODULE_TEMP_OVER OMS_FDI-P SUM_INPWR_LOW
MUT_LOS OMS_LOS-P TEMP_OVER
NO_BD_PARA OMS_SSF VOADATA_MIS
NO_BD_SOFT OMS_SSF-O WAVEDATA_MIS
OMS_SSF-P WRG_BD_TYPE
2.2.53 ROAM Board Alarm List

BD_STATUS OMS_BDI OPA_FAIL_INDI
COMMUN_FAIL OMS_BDI-O NO_BD_SOFT
HARD_BAD OMS_BDI-P NO_ELABEL
HARD_ERR OMS_FDI OMS_SSF-P
MOD_COM_FAIL OMS_FDI-O SUM_INPWR_LOW

MODULE_ADJUST_FAIL OMS_FDI-P SUM_INPWR_HI
MODULEFILE_UPDATE_FAI OMS_LOS-P TEMP_OVER

L
MUT_LOS OMS_SSF WAVEDATA_MIS
OMS_SSF-O WRG_BD_TYPE
2.2.54 SBM2 Board Alarm List

OPA_FAIL_INDI
2.2.55 SC1 Board Alarm List

ALM_HANGUP LSR_WILL_DIE LOOP_ALM
BD_STATUS NO_BD_PARA R_LOF
COMMUN_FAIL NO_BD_SOFT R_SLIP
CRC4_CROSSTR NO_ELABEL SCC_LOC
HARD_BAD OSC_RDI T_SLIP
HARD_ERR OUT_PWR_HIGH TF
IN_PWR_HIGH OUT_PWR_LOW TEMP_OVER
IN_PWR_LOW OSC_LOS WRG_BD_TYPE
2.2.56 SC2 Board Alarm List

ALM_HANGUP LSR_WILL_DIE LOOP_ALM
BD_STATUS NO_BD_PARA R_LOF
COMMUN_FAIL NO_BD_SOFT R_SLIP
CRC4_CROSSTR NO_ELABEL SCC_LOC
HARD_BAD OSC_RDI T_SLIP
HARD_ERR OUT_PWR_HIGH TF
IN_PWR_HIGH OUT_PWR_LOW TEMP_OVER

IN_PWR_LOW OSC_LOS WRG_BD_TYPE
2.2.57 SCC Board Alarm List

TN52SCC
APS_MANUAL_ST NESTATE_INSTALL SUBRACK_LOOP

OP
APS_FAIL NESOFT_MM SUBRACK_TYPE_MIS-

MATCH
APS_INDI NODEID_MM SWDL_ACTIVATED_TI

MEOUT
BD_NOT_INSTALL PATCH_PKGERR SWDL_AUTOMATCH_I

ED NH
BD_STATUS PATCH_ACT_TIMEOUT SWDL_CHGMNG_NO-

MATCH
BOOTROM_BAD PATCH_DEACT_TIMEOUT SWDL_COMMIT_FAIL
COMMUN_FAIL SUBRACK_ID_CONFLICT SWDL_INPROCESS
DBMS_ERROR SUBRACK_ID_MISMATCH SWDL_NEPKGCHECK
DBMS_PROTECT_ POWER_FAIL SWDL_PKGVER_MM

MODE
DB_RESTORE_FAI RTC_FAIL SWDL_PKG_NOBD-

L SOFT
HARD_BAD SECU_ALM SWDL_ROLLBACK_FA

IL
HARD_ERR SERVICE_CAPACITY_EXCEED_ SYNC_DISABLE

LICENSE
HSC_UNAVAIL SERVICE_TYPE_EXCEED_LI- SYNC_FAIL

CENSE
K1_K2_M SHELF_AREA_POWER_OVER SYSPARA_CFDB_NO-

SAME
K2_M SNCP_FAIL SYSLOG_COMM_FAIL
MS_APS_INDI_EX STORM_CUR_QUENUM_OVER TEMP_OVER
NEBD_XC_DIF XC_UNSWITCH WRG_BD_TYPE
NESF_LOST

TN51SCC
APS_MANUAL_ST NESOFT_MM SUBRACK_TYPE_MIS-

OP MATCH
NODEID_MM SWDL_ACTIVATED_TI
APS_FAIL MEOUT
PATCH_PKGERR SWDL_AUTOMATCH_I
APS_INDI NH
BD_NOT_INSTALL PATCH_ACT_TIMEOUT SWDL_CHGMNG_NO-

ED MATCH
BD_STATUS PATCH_DEACT_TIMEOUT SWDL_COMMIT_FAIL
BOOTROM_BAD POWER_FAIL SWDL_INPROCESS
COMMUN_FAIL RTC_FAIL SWDL_NEPKGCHECK
DBMS_ERROR SECU_ALM SWDL_PKGVER_MM
DBMS_PROTECT_ SERVICE_CAPACITY_EXCEED_ SWDL_PKG_NOBD-

MODE LICENSE SOFT
DB_RESTORE_FAI SERVICE_TYPE_EXCEED_LI- SWDL_ROLLBACK_FA

L CENSE IL
HARD_BAD SHELF_AREA_POWER_OVER SYNC_DISABLE
HARD_ERR STORM_CUR_QUENUM_OVER SYNC_FAIL
HSC_UNAVAIL SUBRACK_ID_CONFLICT SYSPARA_CFDB_NO-

SAME
K1_K2_M SUBRACK_ID_MISMATCH SYSLOG_COMM_FAIL
K2_M SUBRACK_LOOP TEMP_OVER
MS_APS_INDI_EX NESTATE_INSTALL WRG_BD_TYPE
NESF_LOST
TNK2SCC
APS_MANUAL_ST NODEID_MM SUBRACK_TYPE_MIS-

OP MATCH
APS_FAIL NESOFT_MM SWDL_ACTIVATED_TI

MEOUT
APS_INDI PATCH_PKGERR SWDL_AUTOMATCH_I

NH

BD_NOT_INSTALL PATCH_ACT_TIMEOUT SWDL_CHGMNG_NO-

ED MATCH
BD_STATUS PATCH_DEACT_TIMEOUT SWDL_COMMIT_FAIL
BOOTROM_BAD POWER_FAIL SWDL_INPROCESS
COMMUN_FAIL RTC_FAIL SWDL_NEPKGCHECK
DBMS_ERROR SECU_ALM SWDL_PKGVER_MM
DBMS_PROTECT_ SERVICE_CAPACITY_EXCEED_ SWDL_PKG_NOBD-

MODE LICENSE SOFT
DB_RESTORE_FAI SERVICE_TYPE_EXCEED_LI- SWDL_ROLLBACK_FA

L CENSE IL
HARD_BAD SHELF_AREA_POWER_OVER SYNC_DISABLE
HARD_ERR SNCP_FAIL SYNC_FAIL
HSC_UNAVAIL STORM_CUR_QUENUM_OVER SYSPARA_CFDB_NO-

SAME
K1_K2_M SUBRACK_ID_CONFLICT SYSLOG_COMM_FAIL
K2_M SUBRACK_ID_MISMATCH TEMP_OVER
MS_APS_INDI_EX SUBRACK_LOOP WRG_BD_TYPE
NEBD_XC_DIF NESTATE_INSTALL XC_UNSWITCH
NESF_LOST
2.2.58 SCS Board Alarm List

BD_STATUS OMS_FDI_O OMS_SSF_P
OMS_BDI OMS_FDI_P OPA_FAIL_INDI
OMS_BDI_O OMS_LOS_P WRG_BD_TYPE
OMS_BDI_P OMS_SSF
OMS_FDI OMS_SSF_O
2.2.59 SF64 Board Alarm List

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_MIS- PORT_MODULE_OFF-

MATCH LINE
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 HP_SLM TF
HP_REI HP_TIM TR_LOC
PM_BDI WRG_BD_TYPE
2.2.60 SF64A Board Alarm List

B1_EXC J0_MM PM_TIM
B1_SD LASER_MODULE_MIS- PORT_MODULE_OFFLINE

MATCH

HP_RDI HP_SLM TF
PM_BDI WRG_BD_TYPE
2.2.61 SFD64 Board Alarm List

B1_EXC J0_MM PM_TIM
B1_SD LASER_MODULE_MIS- PORT_MODULE_OFF-

MATCH LINE

HP_RDI PM_BDI TF
HP_SLM WRG_BD_TYPE
2.2.62 SL64 Board Alarm List

ALM_ALS HP_RDI OH_LOOP
AU_AIS HP_REI HARD_ERR
AU_LOP HP_SLM HP_LOM
B1_EXC HP_TIM NO_BD_SOFT
B1_SD HP_UNEQ PORT_MODULE_OFF-

LINE
B2_EXC IN_PWR_HIGH POWER_ABNORMAL
B2_SD IN_PWR_LOW R_LOC
B3_EXC J0_MM R_LOF
B3_SD LASER_MODULE_MIS- R_LOS

MATCH
BD_STATUS LASER_SHUT SLAVE_WORKING
BUS_ERR LOOP_ALM TEMP_OVER
C2_VCAIS LSR_COOL_ALM TEM_HA

COMMUN_FAIL LSR_WILL_DIE TEM_LA
FSELECT_STG MS_AIS TEST_STATUS
HARD_BAD MS_RDI TF
WRG_BD_TYPE MS_REI TR_LOC
2.2.63 SLH41 Board Alarm List

AU_AIS HP_REI HARD_BAD
AU_LOP HP_SLM HARD_ERR
B1_EXC HP_TIM HP_LOM
B1_SD HP_UNEQ PORT_MODULE_OFFLINE
B3_EXC J0_MM R_LOF
LASER_MODULE_MIS-
B3_SD MATCH R_LOS
MS_REI MS_RDI TF
NO_BD_SOFT WRG_BD_TYPE TR_LOC
2.2.64 SLD64 Board Alarm List



LINE
B3_EXC J0_MM R_LOF

MATCH
NO_BD_SOFT MS_RDI TF
WRG_BD_TYPE MS_REI TR_LOC
2.2.65 SLO16 Board Alarm List

B1_SD HP_UNEQ PORT_MODULE_OFFLINE
B3_EXC J0_MM R_LOF
LASER_MODULE_MIS-
B3_SD MATCH R_LOS

MS_REI MS_RDI TF
2.2.66 SLQ16 Board Alarm List


LINE
B3_EXC J0_MM R_LOF

MATCH
MS_REI MS_RDI TF
2.2.67 SLQ64 Board Alarm List

ALM_ALS HP_RDI HARD_BAD
AU_AIS HP_REI HARD_ERR
AU_LOP HP_SLM HP_LOM
B1_EXC HP_TIM PORT_MODULE_OFFLINE
B1_SD HP_UNEQ POWER_ABNORMAL

B2_EXC IN_PWR_HIGH R_LOC
B2_SD IN_PWR_LOW R_LOF
B3_EXC J0_MM R_LOS
LASER_MODULE_MIS-
B3_SD MATCH SLAVE_WORKING
BD_STATUS LASER_SHUT TEMP_OVER
BEFFEC_SD LOOP_ALM TEM_HA
BUS_ERR LSR_COOL_ALM TEM_LA
C2_VCAIS LSR_WILL_DIE TEST_STATUS
COMMUN_FAIL MS_AIS TF
FSELECT_STG MS_RDI TR_LOC
NO_BD_SOFT MS_REI WRG_BD_TYPE
OH_LOOP
2.2.68 STG Board Alarm List

TN52STG
BD_STATUS NO_BD_SOFT SYNC_F_M_SWITCH
CLK_NO_TRACE_MOD SYNC_LOCKOFF
E NO_ELABEL
COMMUN_FAIL OOL SYN_BAD
EXT_SYNC_LOS HARD_ERR TEMP_OVER
EXT_TIME_LOC LTI TIME_LOS
HARD_BAD S1_SYN_CHANGE TIME_NO_TRACE_MODE
WRG_BD_TYPE SYNC_C_LOS
TNK2STG
BD_STATUS NO_BD_SOFT SYNC_F_M_SWITCH
CLK_NO_TRACE_MOD NO_ELABEL SYNC_LOCKOFF

E
COMMUN_FAIL OOL SYN_BAD

EXT_SYNC_LOS S1_SYN_CHANGE TEMP_OVER
EXT_TIME_LOC SYNC_C_LOS TIME_LOS
HARD_BAD HARD_ERR TIME_NO_TRACE_MODE
WRG_BD_TYPE LTI
2.2.69 STI Board Alarm List

BD_STATUS WRG_BD_TYPE
2.2.70 SXM Board Alarm List

BD_STATUS HARD_ERR TEMP_OVER
BUS_ERR NO_BD_SOFT WRG_BD_TYPE
COMMUN_FAIL NO_ELABEL HARD_BAD
2.2.71 TDC Board Alarm List

BD_STATUS IN_PWR_HIGH HARD_ERR
COMMUN_FAIL IN_PWR_LOW R_LOS
DCM_INSUFF NO_BD_SOFT TEMP_OVER
HARD_BAD NO_ELABEL WRG_BD_TYPE
2.2.72 TDX Board Alarm List

TN52TDX
B1_EXC NULL_SEND OTU2_LOF
B1_SD ODU2_LOFLOM OTU2_LOM
BD_STATUS ODU2_PM_AIS OTU2_SSF
BEFFEC_EXC ODU2_PM_BDI OTU2_TIM
BUS_ERR ODU2_PM_DEG OUT_PWR_HIGH
CLIENT_PORT_PS ODU2_PM_LCK OUT_PWR_LOW

CLIENT_PORT_STA_INDI ODU2_PM_OCI NO_BD_SOFT
CLIENT_PROT_NOTSTART ODU2_PM_SSF NO_ELABEL
COMMUN_FAIL ODU2_PM_TIM PORT_MODULE_OFFLINE
HARD_BAD ODU2_TCMn_AIS PRBS_LSS
HARD_ERR ODU2_TCMn_BDI REMOTE_FAULT
IN_PWR_HIGH ODU2_TCMn_DEG R_LOC
IN_PWR_LOW ODU2_TCMn_LCK R_LOF
J0_MM ODU2_TCMn_LTC R_LOS
LASER_MODULE_MIS- ODU2_TCMn_OCI REM_SD

MATCH
LOCAL_FAULT ODU2_TCMn_SSF REM_SF
LOOP_ALM ODU2_TCMn_TIM TD
LPT_ACTIVE ODU_SNCP_PS TEMP_OVER
LSR_FORCE_OPEN ODU_SNCP_STA_I TEM_HA

NDI
LSR_INVALID OPU2_PLM TEM_LA
LSR_WILL_DIE OTU2_AIS TF
OTU2_DEG OTU2_BDI WRG_BD_TYPE
2.2.73 TMX Board Alarm List

TN11TMX
B1_EXC ODU1_PM_LCK OTU1_BDI
B1_SD ODU1_PM_OCI OTU1_DEG
BD_STATUS ODU1_PM_SSF OTU1_LOF
BEFFEC_EXC ODU1_PM_TIM OTU1_LOM
CLIENT_PORT_PS ODU1_TCMn_AIS OTU1_SSF
CLIENT_PORT_STA_INDI ODU1_TCMn_BDI OTU1_TIM
CLIENT_PROT_NOTSTART ODU1_TCMn_DEG OTU2_AIS
COMMUN_FAIL ODU1_TCMn_LCK OTU2_BDI
HARD_BAD ODU1_TCMn_LTC OTU2_DEG

HARD_ERR ODU1_TCMn_OCI OTU2_LOF
IN_PWR_HIGH ODU1_TCMn_SSF OTU2_LOM
IN_PWR_LOW ODU1_TCMn_TIM OTU2_SSF
J0_MM ODU2_LOFLOM OTU2_TIM
LASER_MODULE_MIS- ODU2_PM_AIS OUT_PWR_HIGH

MATCH
LOOP_ALM ODU2_PM_BDI OUT_PWR_LOW
LSR_FORCE_OPEN ODU2_PM_DEG ODU1_PM_AIS
LSR_INVALID ODU2_PM_LCK ODU1_PM_BDI
LSR_WILL_DIE ODU2_PM_OCI ODU1_PM_DEG
NO_BD_SOFT ODU2_PM_SSF PORT_MODULE_OFF-

LINE
NO_ELABEL ODU2_PM_TIM PRBS_LSS
NULL_SEND ODU2_TCMn_AIS REM_SD
OCh_FDI ODU2_TCMn_BDI REM_SF
OCh_FDI_O ODU2_TCMn_DEG RS_CROSSTR
OCh_FDI_P ODU2_TCMn_LCK R_LOC
OCh_LOS_P ODU2_TCMn_LTC R_LOF
OCh_OCI ODU2_TCMn_OCI R_LOS
OCh_SSF ODU2_TCMn_SSF TD
OCh_SSF_O ODU2_TCMn_TIM TEMP_OVER
OCh_SSF_P OPA_FAIL_INDI TEM_HA
ODU1_LOFLOM OPU1_PLM TEM_LA
OPU2_PLM OPU2_MSIM TF
OTU1_AIS WRG_BD_TYPE WAVEDATA_MIS
TN12TMX
B1_EXC ODU1_PM_DEG OTU1_BDI
B1_SD ODU1_PM_LCK OTU1_DEG
BD_STATUS ODU1_PM_OCI OTU1_LOF
BEFFEC_EXC ODU1_PM_SSF OTU1_LOM

CLIENT_PORT_PS ODU1_PM_TIM OTU1_SSF
CLIENT_PORT_STA_INDI ODU1_TCMn_AIS OTU1_TIM
CLIENT_PROT_NOTSTART ODU1_TCMn_BDI OTU2_AIS
COMMUN_FAIL ODU1_TCMn_DEG OTU2_BDI
HARD_BAD ODU1_TCMn_LCK OTU2_DEG
HARD_ERR ODU1_TCMn_LTC OTU2_LOF
IN_PWR_HIGH ODU1_TCMn_OCI OTU2_LOM
IN_PWR_LOW ODU1_TCMn_SSF OTU2_SSF
J0_MM ODU1_TCMn_TIM OTU2_TIM
LASER_MODULE_MIS- ODU2_PM_AIS OUT_PWR_HIGH

MATCH
LOOP_ALM ODU2_PM_BDI OUT_PWR_LOW
LSR_COOL_ALM ODU2_PM_DEG ODU1_LOFLOM
LSR_FORCE_OPEN ODU2_PM_LCK ODU1_PM_AIS
LSR_INVALID ODU2_PM_OCI ODU1_PM_BDI
LSR_WILL_DIE ODU2_PM_SSF PORT_MODULE_OF

FLINE
NO_BD_SOFT ODU2_PM_TIM PRBS_LSS
NO_ELABEL ODU2_TCMn_AIS REM_SD
NULL_SEND ODU2_TCMn_BDI REM_SF
OCh_FDI ODU2_TCMn_DEG RS_CROSSTR
OCh_FDI_O ODU2_TCMn_LCK R_LOC
OCh_FDI_P ODU2_TCMn_LTC R_LOF
OCh_LOS_P ODU2_TCMn_OCI R_LOS
OCh_OCI ODU2_TCMn_SSF TD
OCh_SSF ODU2_TCMn_TIM TEMP_OVER
OCh_SSF_O OPA_FAIL_INDI TEM_HA
OCh_SSF_P OPU1_PLM TEM_LA
OPU2_PLM OPU2_MSIM TF
OTU1_AIS WRG_BD_TYPE WAVEDATA_MIS

NOTE
TCM6.
2.2.74 TOG Board Alarm List

BD_STATUS NO_ELABEL OPU1_PLM
BUS_ERR ODU0_LOFLOM OUT_PWR_HIGH
CLIENT_PORT_PS ODU0_PM_AIS OUT_PWR_LOW
CLIENT_PORT_STA_INDI ODU0_PM_BDI OPA_FAIL_INDI
CLIENT_PROT_NOTSTART ODU0_PM_DEG LSR_WILL_DIE
COMMUN_FAIL ODU0_PM_LCK L_SYNC
ETH_8B10B_ERR ODU0_PM_OCI NO_BD_SOFT
HARD_BAD ODU0_PM_SSF PORT_MODULE_OFF-

LINE
HARD_ERR ODU0_PM_TIM R_LOS
IN_PWR_HIGH ODU1_LOFLOM REM_SD
IN_PWR_LOW ODU1_PM_AIS REM_SF
LASER_MODULE_MIS- ODU1_PM_BDI TD
MATCH
LOOP_ALM ODU1_PM_DEG TEMP_OVER
LSR_FORCE_OPEN ODU1_PM_LCK TEM_HA
LSR_INVALID ODU1_PM_OCI TEM_LA
ODU1_PM_TIM ODU1_PM_SSF TF
OPU0_PLM WRG_BD_TYPE WAVEDATA_MIS
2.2.75 TOM Board Alarm List

TN52TOM
B1_EXC OCH_OCI OPU1_PLM
B1_SD OCH_SSF OTU1_AIS
BD_STATUS OCH_SSF-O OTU1_BDI
BEFFEC_EXC OCH_SSF-P OTU1_DEG
BUS_ERR ODU0_LOFLOM OTU1_EXC

CLIENT_PORT_PS ODU0_PM_AIS OTU1_LOF
CLIENT_PORT_STA_INDI ODU0_PM_BDI OTU1_LOM
CLIENT_PROT_NOTSTART ODU0_PM_DEG OTU1_SSF
COMMUN_FAIL ODU0_PM_LCK OTU1_TIM
ETH_8B10B_ERR ODU0_PM_OCI OUT_PWR_HIGH
HARD_BAD ODU0_PM_SSF OUT_PWR_LOW
HARD_ERR ODU0_PM_TIM OPA_FAIL_INDI
INTRA_OTU_PS ODU1_LOFLOM OCH_FDI-O
INTRA_OTU_STA_INDI ODU1_PM_AIS OCH_FDI-P
IN_PWR_HIGH ODU1_PM_BDI OCH_LOS-P
IN_PWR_LOW ODU1_PM_DEG PORT_MODULE_OFF-

LINE
J0_MM ODU1_PM_EXC PRBS_LSS
L_SYNC ODU1_PM_LCK RS_CROSSTR
LASER_MODULE_MIS- ODU1_PM_OCI R_LOC

MATCH
LINK_ERR ODU1_PM_SSF R_LOF
LOOP_ALM ODU1_PM_TIM R_LOS
LPT_ACTIVE ODU1_TCMn_AIS REM_SD
LSR_FORCE_OPEN ODU1_TCMn_BDI REM_SF
LSR_INVALID ODU1_TCMn_DEG SW_SNCP_PS
LSR_WILL_DIE ODU1_TCMn_EXC SW_SNCP_STA_INDI
MS_SNCP_PS ODU1_TCMn_LCK TD
MS_SNCP_STA_INDI ODU1_TCMn_LTC TEMP_OVER
NO_BD_SOFT ODU1_TCMn_OCI TEM_HA
NO_ELABEL ODU1_TCMn_SSF TEM_LA
NULL_SEND ODU1_TCMn_TIM TF
OCH_FDI ODU_SNCP_PS TS_CFG_MISMATCH
OPU0_PLM ODU_SNCP_STA_INDI WAVEDATA_MIS
OPU1_MSIM WRG_BD_TYPE

NOTE
TCM6.
2.2.76 TQX Board Alarm List

TN52TQX
B1_EXC NULL_SEND OTU2_LOM
B1_SD ODU2_PM_AIS OTU2_SSF
BD_STATUS ODU2_PM_BDI OTU2_TIM
BEFFEC_EXC ODU2_PM_DEG OUT_PWR_HIGH
BUS_ERR ODU2_PM_LCK OUT_PWR_LOW
CLIENT_PORT_PS ODU2_PM_OCI LSR_WILL_DIE
CLIENT_PORT_STA_INDI ODU2_PM_SSF NO_BD_SOFT
CLIENT_PROT_NOT- ODU2_PM_TIM
START NO_ELABEL
COMMUN_FAIL ODU2_TCMn_AIS PORT_MODULE_OFFLINE
HARD_BAD ODU2_TCMn_BDI PRBS_LSS
HARD_ERR ODU2_TCMn_DEG REMOTE_FAULT
IN_PWR_HIGH ODU2_TCMn_LCK R_LOC
IN_PWR_LOW ODU2_TCMn_LTC R_LOF
J0_MM ODU2_TCMn_OCI R_LOS
LASER_MODULE_MIS- ODU2_TCMn_SSF REM_SD

MATCH
LOCAL_FAULT ODU2_TCMn_TIM REM_SF
LOOP_ALM ODU_SNCP_PS TD
LPT_ACTIVE ODU_SNCP_STA_IN- TEMP_OVER

DI
LSR_FORCE_OPEN OPU2_PLM TEM_HA
LSR_INVALID OTU2_AIS TEM_LA
OTU2_DEG OTU2_BDI TF
OTU2_LOF WRG_BD_TYPE

NOTE
TCM6.
2.2.77 VA1 Board Alarm List

TN12VA1
BD_STATUS HARD_ERR VOADATA_MIS
COMMUN_FAIL OPA_FAIL_INDI WAVEDATA_MIS
HARD_BAD TEMP_OVER WRG_BD_TYPE
2.2.78 VA4 Board Alarm List

TN12VA4
BD_STATUS HARD_ERR VOADATA_MIS
COMMUN_FAIL OPA_FAIL_INDI WAVEDATA_MIS
HARD_BAD TEMP_OVER WRG_BD_TYPE
2.2.79 WMU Board Alarm List

BD_STATUS NO_BD_PARA PORTSWITCH_FAIL
COMMUN_FAIL NO_BD_SOFT TEMP_OVER
HARD_BAD NO_ELABEL WAVELEN_OVER
HARD_ERR MODULE_ADJUST_FAIL WRG_BD_TYPE
2.2.80 WSD9 Board Alarm List

TN12WSD9/TN13WSD9
BD_STATUS OMS_BDI-O OPA_FAIL_INDI
COMMUN_FAIL OMS_BDI-P SUM_INPWR_LOW
HARD_BAD OMS_FDI SUM_INPWR_HI
HARD_ERR OMS_FDI-O TEMP_OVER
MOD_COM_FAIL OMS_FDI-P VOADATA_MIS

MODULE_ADJUST_FAI OMS_LOS-P WAVEDATA_MIS

L
MODULEFILE_UPDATE OMS_SSF WRG_BD_TYPE

_FAIL
MUT_LOS OMS_SSF-O
OMS_BDI OMS_SSF-P
2.2.81 WSM9 Board Alarm List

TN12WSM9/TN13WSM9
BD_STATUS MOD_COM_FAIL TEMP_OVER
COMMUN_FAIL MODULE_ADJUST_FAI VOADATA_MIS

L
HARD_BAD MODULEFILE_UPDATE WAVEDATA_MIS

_FAIL
HARD_ERR OPA_FAIL_INDI WRG_BD_TYPE
2.2.82 WSMD2 Board Alarm List

BD_STATUS OMS_BDI-O OPA_FAIL_INDI
COMMUN_FAIL OMS_BDI-P SUM_INPWR_HI
HARD_BAD OMS_FDI SUM_INPWR_LOW
HARD_ERR OMS_FDI-O TEMP_OVER
MODULEFILE_UPDATE_F OMS_FDI-P VOADATA_MIS

AIL
MODULE_ADJUST_FAIL OMS_LOS-P WRG_BD_TYPE
MOD_COM_FAIL OMS_SSF WAVEDATA_MIS
MUT_LOS OMS_SSF-O
OMS_BDI OMS_SSF-P
2.2.83 WSMD4 Board Alarm List

TEMP_OVER OMS_BDI OMS_SSF-P

COMMUN_FAIL OMS_BDI-O OPA_FAIL_INDI
BD_STATUS OMS_BDI-P SUM_INPWR_LOW
MUT_LOS OMS_FDI SUM_INPWR_HI
MOD_COM_FAIL OMS_FDI-O VOADATA_MIS
MODULE_ADJUST OMS_FDI-P WAVEDATA_MIS

_FAIL
MODULEFILE_UP OMS_LOS-P WRG_BD_TYPE

DATE_FAIL
HARD_BAD OMS_SSF
HARD_ERR OMS_SSF-O
2.2.84 XCH Board Alarm List

TN52XCH
BD_STATUS HARD_ERR TEMP_OVER
BUS_ERR NO_BD_SOFT WRG_BD_TYPE
COMMUN_FAIL NO_ELABEL HARD_BAD
2.2.85 XCM Board Alarm List

TN52XCM
BD_STATUS HARD_ERR HARD_BAD
BUS_ERR NO_BD_SOFT TEMP_OVER
COMMUN_FAIL NO_ELABEL WRG_BD_TYPE
2.2.86 XCT Board Alarm List

BD_STATUS HARD_ERR HARD_BAD
BUS_ERR NO_BD_SOFT TEMP_OVER
COMMUN_FAIL NO_ELABEL WRG_BD_TYPE

Alarms and Performance Events Reference 3 Common Alarm Processing
3 Common Alarm Processing
About This Chapter
This chapter describes common information relevant to alarm handling, including alarm
descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm
handling procedures.
NOTE
In the case of an alarm, see its handling procedure to clear it; if the alarm persists, contact Huawei engineers
for troubleshooting.
The alarm handling involves board reset, either cold or warm. Cold reset and warm reset have
different impacts on services.
l Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software,
neither the FPGA file nor hardware data is updated and so a warm reset does not interrupt
services. A cold reset of the SCC might result in re-setting of the key hardware, such as
FPGA reloading; the upper-layer software need be restarted.
l Reset of other boards: A warm reset on other boards does not affect running services while
a cold reset on other boards does. If such a board is reset improperly, the communication
between the board and the SCC is affected and even the services are interrupted.
Certain alarms listed in this chapter are handled in different ways, because the board types are
different. This chapter describes how to handle alarms in the OCS and OTN systems separately
according to the system where the board is located.
The meaning of the n and k in this chapter as follows:

l k indicates the level of rate and its value is 0, 1, 2, 3.
l n indicates the level of TCM and its value ranges from 1 to 6.
3.1 B1_EXC
Refer to the alarm page according to the type of the board that reports the alarm.
3.2 BEFFEC_EXC
3.3 BUS_ERR
See the alarm page according to the type of the board that reports the alarm.

3.4 CHAN_LOS
3.5 CLIENT_PORT_PS
3.6 COMMUN_FAIL
3.7 ETH_8B10B_ERR
3.8 EX_ETHOAM_CC_LOS
3.9 FC_LINK_ERR
3.10 FC_SYNC_LOS
3.11 IN_PWR_HIGH
3.12 IN_PWR_LOW
3.13 INTRA_OTU_PS
3.14 LASER_MODULE_MISMATCH
3.15 LINK_ERR
3.16 LOOP_ALM
3.17 LPT_ACTIVE
3.18 LSR_WILL_DIE
3.19 MS_AIS
3.20 MS_RDI
3.21 MUT_LOS
3.22 OA_LOW_GAIN
3.23 ODU_SNCP_PS
3.24 ODUk_PM_AIS
3.25 ODUk_PM_BDI
3.26 ODUk_PM_DEG
3.27 ODUk_PM_EXC
3.28 ODUk_PM_SSF
3.29 OMS_FDI
3.30 OSC_LOS

3.31 OTS_LOS
3.32 OUT_PWR_HIGH
3.33 PORT_MODULE_OFFLINE
3.34 POWER_FAIL
3.35 PUMP_COOL_EXC
3.36 R_LOF
3.37 R_LOS
3.38 R_OOF
3.39 R_SLIP
3.40 REM_SF
3.41 REMOTE_FAULT
3.42 SECU_ALM
3.43 SUM_INPWR_LOW
3.44 TD
3.45 TF
3.46 TS_CFG_MISMATCH
3.47 WRG_BD_TYPE

3.1 B1_EXC
Table 3-1 Alarm page link
Board Type Alarm page link
SF64, SF64A, SFD64, SL64, SLD64, 3.1.1 B1_EXC(OCS)

SLQ16, SLQ64, SLH41, SLO16, or EGSH
Boards other than the SF64, SF64A, SFD64, 3.1.2 B1_EXC(OTN)

SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
3.1.1 B1_EXC(OCS)
Description
The B1_EXC(OCS) alarm indicates that the number of regenerator section B1 bit errors in the
signals received on the line exceeds the threshold. When a line board detects the B1 bytes and
determines that the bit error ratio (BER) of the regenerator section signals exceeds the threshold
for the B1_EXC alarm, the alarm is reported.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Impact on the System

l When the B1_EXC occurs, the quality of the transmitted services is degraded.
l When the B1_EXC occurs, by default, the system inserts the AU_AIS alarm in the cross-
connection direction.
Possible Causes
The possible causes of the B1_EXC alarm are as follows:
l Cause 1: The line performance degrades.

l Cause 2: The external environment is abnormal.

l Cause 3: The receive board of the local end is faulty.
l Cause 4: The transmit board of the opposite end is faulty.
Procedure
l Query current alarms on the U2000. According to parameter 1, determine the ID of the
interface that reports the alarm. For details, see Querying the Current Alarms and
Performance Events of a NE on the U2000 in the Supporting Task.
1. Check whether the transmit power at the opposite station and the receive power at the
local station meet the specifications of the interfaces. For details on optical power
specification of the board, see "Technical Specifications" of the Product
Description. For details, see Querying Optical Power on the U2000 in the Supporting
Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the
manufacturer information about the board optical module.
If... Then...
The transmit optical power of the opposite station is Proceed to the next step.
normal, but the receive optical power of the local
station is almost equal to the specification (for
example, within ±3 dB) of the receiver sensitivity,
The transmit optical power of the local board is See cause 4.

abnormal,
2. Check whether the optical connector is normal.
If... Then...
The connector is loose Tighten the optical connector. Check whether the alarm
is cleared. If the alarm persists, proceed to the next step.
The interface is normal Proceed to the next step.
3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the
Fiber-Optic Connectors in the Supporting Task.

If... Then...
The connector is dirty Clean the optical connector. For details, see
l Cleaning Optical Fiber Connectors Using Cartridge

Cleaners
l Cleaning Optical Fiber Connectors Using Lens
Tissue
l Cleaning Optical Adapters Using Optical Cleaning
Sticks
in Supporting Task. Then, check whether the alarm is

cleared. If the alarm persists, proceed to the next step.
The connector is normal Proceed to the next step.
4. Check whether the attenuation value of the optical attenuator is proper according to
the specified receive optical power. For details on optical power specifications of the
board, see "Technical Specifications" of the Product Description.
If... Then ...
The value of optical attenuation is Adjust the attenuation to the proper

improper, value. For details, see Adjusting,
Replacing, Adding and Removing
Attenuator in the Supporting Task. Then,
check whether the alarm is cleared. If the
alarm persists, proceed to the next step.
The value of optical attenuation is Proceed to the next step.

proper,
5. Check whether the fiber is faulty. Especially, check whether the bending radius of a
fiber jumper is within the normal range, and check whether the fiber from the
equipment to the ODF and the fiber outside the equipment room are pressed. If the
bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If
the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm
persists, see cause 2.
1. Check the ambient temperature of the equipment room. If the temperature is higher
than 45°C or is lower than 0°C, use a cooler/heater to decrease/increase the ambient
temperature.
2. Check whether the alarm is cleared. If the alarm persists, see cause 3.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.

NOTICE
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
No bit error alarm is reported, See cause 4.
2. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the local faulty board. For details, see Parts
Replacement.
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
3.1.2 B1_EXC(OTN)
Description
The B1_EXC(OTN) alarm indicates the regenerator section (B1) excessive errors. The alarm is
generated when the received SDH signals degrade and the B1 bit errors in the multiplex section
exceed the threshold.
Reported from the WDM side or client side: WDM side and client side.
l The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received
on the WDM side exceed the B1 bit error threshold.
l The alarm is generated on the client side when the B1 bit errors in the SDH signals received
on the client side exceed the B1 bit error threshold.
Attribute
Minor Service alarm

Parameters
None

The B1 bit errors in the service signals received by the board exceed the threshold of the B1 bit
errors set for the board. The alarm affects the QoS of the service signals.
Possible Causes
l Cause 1 for the alarm generated on the client side: The input signals on the client side
contain bit errors.
l Cause 1 for the alarm generated on the WDM side: The receive side of the local station is
faulty.
l Cause 2 for the alarm generated on the WDM side: The attenuation of the received signals
is excessively high; the fiber or connector is not clean.
l Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite
station is faulty.
Procedure
l Query the alarm on the U2000 and record the IDs of the port and channel where the alarm
is generated.
l Cause 1 for the alarm generated on the client side: The input signals on the client side
contain bit errors.
1. If the alarm is reported from the client side, it indicates that the input signals on the
client side contain bit errors. In this case, eliminate the bit errors according to the
documents of the client equipment.
l Cause 1 for the alarm generated on the WDM side: The receive side of the local station is
faulty.
Detects and reports Detects and reports

the B1_EXC alarm the B1_EXC alarm
O O
A F F A
OTU1 I I OTU2
D D
M U U M Out-loop
Client side WDM side WDM side Client side
Station A Station B
1. Configure outloop at the transmit and receive optical interfaces on the WDM side of
the OTU2. If there is no bit error alarm on the OTU1, it indicates that the board at the
local station is faulty. Replace the faulty board. For details, refer to "Replacing a
Board" of the Supporting Tasks.
l Cause 2 for the alarm generated on the WDM side: The attenuation of the received signals
is excessively high; the fiber or connector is not clean.
1. If there are bit errors, on the U2000 check whether the transmit optical power at the
corresponding optical interfaces on the opposite OTU1 is within the normal range.

For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description .
2. If the transmit optical power of the optical interface on OTU1 at the opposite station
is within the normal range, check the fibers and clean the fiber connectors between
transmiting side of OTU1 and the receive side of OTU2.
l Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
1. If the optical power of the optical interface on OTU1 at the opposite station is
abnormal, check whether the B1_EXC alarm is generated on the client side of the
opposite OTU1. If yes, clear the B1_EXC alarm on the client side. If not, it indicates
that the opposite OTU1 is faulty. Replace the opposite OTU1. For the optical power
specification of the specific board, refer to "Technical Specifications" of the Product
Description .
----End
Related Information
None.
3.2 BEFFEC_EXC
Description
The BEFFEC_EXC alarm indicates that bit errors before FEC alarm exceed the threshold.
Signals from the WDM side of the opposite OTUs have the FEC function. As a result, before
performing signal FEC in the receive direction on theWDM side of the local OTUs, the local
OTUs computes the bit error rate. This alarm is generated when the computed bit error rate
exceeds the threshold.
Reported from the WDM or client side: WDM side
Attribute
Minor Service alarm
Parameters
None

The error tolerance of the system decreases, and the quality of signals is affected if the decrease
is sufficient.

Possible Causes
l Cause 1: The input optical power of the OTU is excessively high or low. The system
performance degrades. For example, the optical signal to noise ratio (OSNR) is excessively
low, or dispersion or non-linearity occurs.
l Cause 2: An inappropriate DCM is installed.
l Cause 3: The board at the opposite station is faulty.
l Cause 4: The board that reports the alarm is faulty.
Procedure
is generated.
l Cause 1: The input optical power of the OTU is excessively high or low. The system
performance degrades. For example, the optical signal to noise ratio (OSNR) is excessively
low, or dispersion or non-linearity occurs.
1. Check whether the receive optical power on the U2000 is within the normal range,
2. If the input optical power is abnormal, see the methods for handling the
IN_PWR_HIGH and IN_PWR_LOW.
3. If the optical power is normal, it is possible that the system performance degrades.
For the alarm handling, refer to "Troubleshooting Bit Errors" of the
Troubleshooting.
l Cause 2: An inappropriate DCM is installed.
1. Check whether the DCM used on the existing network is appropriate. If not, replace
the DCM.
l Cause 3 and cause 4: The board at the opposite station may be faulty; the board at the local
station may be faulty.
1. If the alarm persists, the OTU that reports the alarm may be faulty. Replace the OTU,
For details, refer to "Replacing a Board" of the Supporting Tasks.
2. If the alarm persists, the board at the opposite station may be faulty. Replace the faulty
board, For details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
3.3 BUS_ERR

Board Type Alarm Page Link
SF64, SF64A, SFD64, SL64, SLD64, 3.3.1 BUS_ERR(OCS)

Boards other than the SF64, SF64A, SFD64, 3.3.2 BUS_ERR(OTN)

SLO16, or EGSH
3.3.1 BUS_ERR(OCS)
Description
The BUS_ERR is an alarm indicating the bus error. This alarm is generated when the board
detects a backplane bus error.
Attribute
Critical Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of slot that houses the cross-connect board.
Parameters 2 and 3 Indicates the statuses of buses.

l When the BUS_ERR alarm is reported, the services that pass through the relevant bus are
interrupted or have bit errors.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows:
l Cause 1: The internal bus of the cross-connect board is faulty.

l Cause 2: The software version does not match the specified version.
l Cause 3: The backplane or the relevant board is faulty.
Procedure
l Query current alarms on the U2000. For details, see Querying the Current Alarms and
l Cause 1: The internal bus of the cross-connect board is faulty.
1. Replace the cross-connect board. For details, see the Parts Replacement.
NOTICE
If no cross-connect board that works normally can be used for protection, do not
perform the operations, because all the services may be interrupted.
l Cause 2: The software version does not match the specified version.
1. Check whether the version of the cross-connect board matches the version of relevant
service board. For details, see Querying the Version of the Board in the Supporting
Task.
2. If the versions of the cross-connect board and relevant service board do not match,
contact Huawei engineers to upgrade the relevant boards.
l Cause 3: The backplane or the relevant board is faulty.
1. Perform cold reset on the service board that maps the cross-connect board by using
the U2000, or reseat the service board that maps the cross-connect board. For the
operations that are performed on the U2000, see Performing a Cold Reset of a Board
in the Supporting Task. For the operations of reseating the board, see "Removing
Boards" and "Inserting Boards" in the Quick Installation Guide. Then, check whether
the alarm is cleared.
2. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
NOTICE
If the services that travel through the service board are not protected, do not perform
the cold reset or replace the board because services may be interrupted.
3. Perform cold reset on the cross-connect board by using the U2000, or reseat the cross-
connect board. Then, check whether the alarm is cleared.
4. If the alarm persists, replace the cross-connect board. For details, see the Parts
Replacement. Then, check whether the alarm is cleared.

NOTICE
If no cross-connect board that works normally can be used for protection, do not
perform the operations, because all the services may be interrupted.
5. If the alarm persists, contact Huawei engineers to check whether the fault is caused
by bent pins of the backplane. If the backplane is faulty, replace the backplane of the
subrack.
----End
Related Information
None
3.3.2 BUS_ERR(OTN)
Description
The BUS_ERR is an alarm indicating the bus error. This alarm is generated when the board
detects a backplane bus error.
Reported from the WDM side or client side: NA
Attribute
Critical Equipment
Parameters
Parameter Description
Parameters 1 and 2 Indicates the ID of the bus in which the alarm is generated.

l This alarm triggers the bus switching.
l Services are unavailable or bit errors are generated.For example, and ODU1 and ODU0
services of the OptiX OSN 8800 are affected.
Fault Symptom
None

NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic, handle
the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The OTU board is inserted inappropriately or faulty.
l Cause 2: The cross-connect board is inserted inappropriately or faulty.
l Cause 3: When ASON services are configured, the type of the service that is actually
received does not match the service type configured on the board.
l Cause 4: The pins are faulty or the bus is faulty on the backplane.
Procedure
l Cause 1: The OTU board is inserted inappropriately or faulty.
1. Reseat the OTU board. For the operation of reseating the board, see "Removing
Boards" and "Inserting Boards".in the Quick Installation Guide.
2. Check whether the alarm is cleared. If the alarm persists, replace the board. For details,
see the Parts Replacement.
l Cause 2: The cross-connect board is inserted inappropriately or faulty.
1. Reseat the cross-connect board. For operations, see "Removing Boards" and "Inserting
Boards".in the Quick Installation Guide.
2. Check whether the alarm is cleared. If the alarm persists, replace the cross-connect
board. For details, see the Parts Replacement.
l Cause 3: When ASON services are configured, the type of the service that is actually
received does not match the service type configured on the board.
1. Check whether board that reports this alarm supports pluggable optical modules.
If... Then...
The board supports pluggable optical Replace the specific pluggable optical
modules, module. For details, refer to "Replacing
Pluggable Optical Modules" of the Parts
Replacement.
The board does not support Replace the faulty board. For details, refer
pluggable optical modules, to "Replacing a Board" of the Supporting
Tasks.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The pins are faulty or the bus is faulty on the backplane.
1. Perform a cold reset on the faulty board through the U2000.
2. If the alarm persists, replace the backplane of the subrack. For the detailed operations,
contact Huawei engineers.
----End

Related Information
None
3.4 CHAN_LOS
Description
The CHAN_LOS alarm indicates the single wavelength signal loss. The alarm is generated when
the MCA (optical spectrum analyzer) board detects that the original channel is lost after it scans
the optical spectrum.
Attribute
Parameters
None

l The services of the related wavelength are unavailable.
l The MCA cannot monitor the optical spectrum performance of the wavelength related to
the alarm.
Possible Causes
l Cause 1: The wavelength that needs to be monitored is not accessed. For example, in the
following figure, wavelength λ1 needs to be monitored, but actually λ1 is not accessed. The
possible cause is that the fiber to the client or WDM side of OTU1 is disconnected.
MCA
M M
λ1 U U λ1
OTU1 X OA OA X OTU3
F F
/ /
λ2 I I λ2
D D
OTU2 U U OTU4
M OA OA M
U U
X X
Client side WDM side WDM side Client side
Station A Station B
l Cause 2: The laser of the board at the opposite station is shut down. For example, the laser
of OTU1 in the preceding figure is shut down.
l Cause 3: The attenuation of the multiplexer or OA unit in the upstream of the MCA is
excessively high.

l Cause 4: The OTU in the upstream of the MCA is faulty. For example, OTU1 in the
preceding figure is faulty.
l Cause 5: The MCA that reports the alarm is faulty.
Procedure
is generated. Parameter 2 and parameter 3 indicate the number of wavelengths in which
the alarm is generated.
l Cause 1: The wavelengths that need to be monitored are not accessed.
1. Check whether the wavelength where the alarm is generated is required in the actual
network. If not, modify the wavelength monitoring configuration of the MCA so that
the monitoring of the wavelength is disabled.
2. If the wavelength needs to be accessed in the actual network, check the fiber
connection in the upstream stations along the signal flow and make sure that the fiber
connection is established properly.
l Cause 2: The laser of the board at the opposite station is shut down.
1. Check whether the laser of the OTU that transmits the wavelength is shut down. If the
laser is shut down, opening the Laser.
l Cause 3: The attenuation of the multiplexer or OA unit in the upstream of the MCA is
excessively high.
1. Query the output optical power of the upstream OTU connected to the multiplexer
unit. Make sure that the queried output optical power of the upstream OTU is within
the normal range.
2. Query the input optical power of the optical interface (on the MCA) that reports the
alarms, and then calculate the output optical power of the upstream multiplexer or OA
unit to determine whether the output optical power is within the normal range. For the
optical power specification of the specific board, refer to "Technical Specifications"
of the Product Description . If the optical power is excessively low or there is no light,
check the attenuation that is set for the input optical power on the multiplexer or OA
unit. If the attenuation is excessively high, decrease the attenuation of the multiplexer
or OA unit.
NOTE
Output optical power of the multiplexer or OA unit (dBm) = Input optical power at the IN port
on the MCA (dBm) - 10lg(MON/OUT) (dBm). MON/OUT represents the split ratio of the
MON port on the multiplexer or OA unit.
l Cause 4: The OTU in the upstream of the MCA is faulty.
1. Query the optical spectrum data at the optical interface where the alarm is generated
on the MCA. If the data is abnormal, replace the OTU that transmits the wavelength
to the MCA. For details, refer to "Replacing a Board" of the Supporting Tasks.
l Cause 5: The MCA that reports the alarm is faulty.
1. Use an optical spectrum analyzer to analyze the optical spectrum data of the
corresponding optical interface on the MCA. If the data is normal, perform a cold reset
on the MCA.
2. If the alarm persists, replace the MCA that reports the alarm. For details, refer to
"Replacing a Board" of the Supporting Tasks.
----End

Related Information
None.
3.5 CLIENT_PORT_PS
Description
The CLIENT_PORT_PS alarm indicates the client-side 1+1 protection switching. This alarm
occurs when the client-side 1+1 protection group actuates switching in which the current channel
switches to the protection channel from the working channel.
Attribute
Major Communication alarm
Parameters
None

When the client-side 1+1 protection group actuates switching, services are transiently
interrupted. When this alarm is reported, the working channel of the client-side 1+1 protection
group might have faulty services that needs to be restored.
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual
switching. Such a command makes the current channel of the client-side 1+1 protection
group switch to the protection channel from the working channel. Hence, the alarm is
reported.
l Cause 2: The services of the working channel of the client-side 1+1 protection group are
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
Procedure
switching.
1. On the U2000, query the switching state of the protection group. If the switching state
is forced switching or manual switching, check whether the external switching
operation is necessary.
2. If the external switching operation is necessary, ignore the alarm.

3. If the external switching operation is unnecessary, issue an external command to

switch the current channel to the working channel, thus clearing the alarm.
l Cause 2: The services of the working channel of the client-side 1+1 protection group are
is reported.
1. Query whether the related boards for configuring the protection group have alarms
relevant to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_TIM, REM_SF,
ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC or REM_SD. If
yes, handle the alarms by referring to the corresponding alarm handling procedures.
2. If the alarm persists, check whether the attribute of the protection group is
Revertive. If yes, the current channel automatically switches to the working channel
and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the
alarm clears.
----End
Related Information
None
3.6 COMMUN_FAIL
SF64, SF64A, SFD64, SL64, SLD64, 3.6.1 COMMUN_FAIL(OCS)

Boards other than the SF64, SF64A, SFD64, 3.6.2 COMMUN_FAIL(OTN)

SLO16, or EGSH
3.6.1 COMMUN_FAIL(OCS)
Description
The COMMUN_FAIL(OCS) is an alarm indicating an inter-board communication failure. This
alarm is reported when the communication between the SCC and other boards is interrupted.

Attribute
Major Equipment alarm
Parameters
Parameters 1 and 2 Indicates the ID of the channel in which the alarm is generated. For
example,
0x00 0x01 indicates RS485 path 1.
0x00 0x02 indicates RS485 path 2.
0x00 0x03 indicates intra-board communication.
0x00 0x04 indicates the Ethernet emergency channel between subracks.

When the alarm is generated, the SCC cannot send commands or services to the board, or the
board cannot work. In this case, the service cannot be configured or the protection switching
becomes invalid. Thus, the new service becomes abnormal.
Possible Causes
The possible causes of the COMMUN_FAIL alarm are as follows:
l Cause 1 of a single board reporting this alarm: The board is in the cold reset or warm reset
state.
l Cause 2 of a single board reporting this alarm: The board is faulty.
l Cause 1 of multiple boards reporting this alarm: The service board AUX is faulty.
NOTE
If the communication ports between the AUX board and other boards are faulty, the service board
reports the COMMUN_FAIL alarm while the standby SCC board does not report the alarm.
l Cause 2 of multiple boards reporting this alarm: The SCC board or the cross-connect board
is faulty.

NOTE
If the active SCC board is faulty, the active SCC board, standby SCC board, and service board report
the COMMUN_FAIL alarm at the same time.
If the cross-connect board is faulty, the communication in the 485 path is faulty. The cross-connect
board and the service board report the COMMUN_FAIL alarm.
Procedure
l Query the alarm on the U2000. Then, determine the boards that report the alarm and
corresponding alarm parameter. For details, see Querying the Current Alarms and
l Cause 1 of a single board reporting this alarm: The board status is cold reset or warm reset.
1. Check the board alarm indicator to see whether the status of the board that reports the
alarm is cold reset or warm reset. Wait for 5 minutes if the status is cold reset or warm
reset, and then check whether the alarm is cleared. For the description of the alarm
indicators on the board, see Board Indicators in the Hardware Description.
2. If the alarm persists, see Cause 2 of a single board reporting this alarm.
1. Replace the board that reports the alarm. For details, see the Parts Replacement.
l Cause 1 of multiple boards reporting this alarm: The service board AUX is faulty.
1. Check whether the AUX board reports the alarm that indicates a board or chip fault
such as the BD_STATUS alarm. Reseat the board. For the operations of reseating a
board, see "Removing Boards" and "Inserting Boards" in the Quick Installation
Guide. Then, check whether the COMMUN_FAIL alarm is cleared.
2. If the alarm persists, replace the board. For details, see the Parts Replacement. Then,
check whether the COMMUN_FAIL alarm is cleared.
3. If the alarm persists, see Cause 2 of multiple boards reporting alarm.
l Cause 2 of multiple boards reporting this alarm: The SCC board or the cross-connect board
is faulty.
1. Check whether the active SCC board or the active cross-connect board reports the
alarm such as the BD_STATUS or HARD_BAD alarm that indicates a board fault.
Reseat the board. For the operations of reseating a board, see "Removing Boards" and
"Inserting Boards" in the Quick Installation Guide. Then, check whether the
COMMUN_FAIL alarm is cleared.
2. If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
3.6.2 COMMUN_FAIL(OTN)
Description
The COMMUN_FAIL is an alarm indicating an inter-board communication failure. This alarm
occurs when the communication between the SCC and other boards is interrupted.

Attribute
Parameters
Parameters 1 Indicates the optical port number and the value is always 0x01.
Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. For
example,
0x00 0x01 denotes RS485 path 1;
0x00 0x03 denotes intra-board communication;
0x00 0x04 denotes the Ethernet emergency channel between subracks.
0x00 0x05 denotes the spi communication failure between the SCC board
and AUX board.

After the alarm is generated, configuration data fails to be applied to other boards or other boards
cannot function normally. The service configuration or protection switching may fail or the
package loading may roll back abnormally. Thus, new services become abnormal.
Fault Symptom
Table 3-4 lists the fault symptom for the COMMUN_FAIL alarm.

Table 3-4 Fault symptom for the COMMUN_FAIL alarm
Fault Symptom Cause
A single board reports the l The board also reports the Cause 1 of a single board
COMMUN_FAIL alarm. BD_STATUS alarm reporting this alarm: The
The alarm parameter is 0x01 (only when the board is in board is in cold reset or warm
0x00 0x03. cold reset state). reset state.
l The PROG indicator on
the board blinks first at
the frequency of 300 ms
on and 300 ms off (green)
and then at the frequency
of 100 ms on and 100 ms
off (green).
No other symptoms occur. Cause 3 of a single board

reporting this alarm: The
board is faulty.
A single board reports the No other symptoms occur. Cause 3 of a single board
COMMUN_FAIL alarm. reporting this alarm: The
The alarm parameter is 0x01 board is faulty.
0x00 0x01 or 0x01 0x00
0x02.
The SCC board of a slave The network cables for Cause 2 of a single board
subrack reports the cascading subracks are self- reporting this alarm: The
COMMUN_FAIL alarm. made network cables rather network cables for cascading
The alarm parameter is 0x01 than standard straight- subracks do not meet the
0x00 0x04. through cables with all eight requirements.
cores being used.
Multiple boards report the l The standby SCC board Cause 1 of multiple boards
COMMUN_FAIL alarm. does not report the reporting this alarm: For
The alarm parameter is 0x01 COMMUN_FAIL alarm. OptiX OSN 8800: The EFI1
0x00 0x03. l For OptiX OSN 8800: or EFI2 board is faulty.
The EFI1 or EFI2 board
reports the BD_STATUS
alarm.

Fault Symptom Cause
l The boards that report the Cause 2 of multiple boards

COMMUN_FAIL alarm reporting this alarm: The
are housed in slave settings of the DIP switches
subracks. of the subracks are incorrect
l The SUBRACK_LOOP or the subracks are cascaded
alarm is generated on the inappropriately.
NE, or the
SUBRACK_ID_CON-
FLICT or
SUBRACK_ID_MIS-
MATCH alarm is
generated in the housing
subracks of the boards
that report the
COMMUN_FAIL alarm.
l The active and standby Cause 3 of multiple boards

SCC boards report the reporting this alarm: The
COMMUN_FAIL alarm SCC or cross-connect board
at the same time. is faulty.
l The active SCC board
also reports alarms such
as HARD_BAD and
BD_STATUS, indicating
abnormal equipment
status.
Multiple boards report the l The cross-connect board Cause 3 of multiple boards
COMMUN_FAIL alarm. reports the reporting this alarm: The
The alarm parameter is 0x01 COMMUN_FAIL alarm. SCC or cross-connect board
0x00 0x01 or 0x01 0x00 l The cross-connect board is faulty.
0x02. also reports alarms such
as BD_STATUS,
indicating abnormal
equipment status.
NOTE
Possible Causes
The possible causes of a single board reporting the COMMUN_FAIL alarm are as follows:
l Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset
state.

l Cause 2 of a single board reporting this alarm: The network cables for cascading subracks
do not meet the requirements.
The possible causes of multiple boards reporting the COMMUN_FAIL alarm are as follows:
l Cause 1 of multiple boards reporting this alarm: For OptiX OSN 8800: The EFI1 or EFI2
board is faulty.
l Cause 2 of multiple boards reporting this alarm: The settings of the DIP switches of the
subracks are incorrect or the subracks are cascaded inappropriately.
l Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
NOTE
If the active SCC board is faulty, the active SCC board, standby SCC board, and service boards report
the COMMUN_FAIL alarm at the same time.
If the cross-connect board is faulty, the communication on channel 485 fails. In this case, the cross-
connect board and service boards report the COMMUN_FAIL alarm at the same time.
Procedure
l Query the alarm on the U2000. Then, determine the boards that report the alarm and
corresponding alarm parameter. For details, refer to "Querying the Current Alarms and
Performance Events of a NE on the U2000" of the Supporting Tasks.
l Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset
state.
1. View the alarm indicators of the board to check whether the board that reports this
alarm is in warm reset or cold reset state. If yes, wait for five minutes and then check
whether the alarm is cleared. For the description of the alarm indicators on the board,
see the Hardware Description.
2. If the alarm persists, see cause 2 of a single board reporting this alarm.
l Cause 2 of a single board reporting this alarm: The network cables for cascading subracks
do not meet the requirements.
1. Replace the network cables for cascading subracks with standard straight-through
network cables with all eight cores being used. Then check whether the alarm is
cleared.
2. If the alarm persists, see cause 3 of a single board reporting this alarm.
1. Replace the board that reports the alarm. See For details, refer to "Replacing a Board"
of the Supporting Tasks..
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
l Cause 1 of multiple boards reporting this alarm: For OptiX OSN 8800: The EFI1 or EFI2
board is faulty..
1. Check whether the EFI1 or EFI2 board also reports alarms such as BD_STATUS,
indicating abnormal board status. Reseat the board. For the operation of reseating the
board, see "Removing Boards" and "Inserting Boards" in the Quick Installation
Guide.
2. Check whether the alarm is cleared. If the alarm persists, replace the EFI1 or EFI2
board.For details, refer to "Replacing the EFI Board" of the Parts Replacement..

3. Check whether the alarm is cleared. If the alarm persists, see cause 2 of multiple boards
reporting this alarm.
1. Check whether the SUBRACK_LOOP, SUBRACK_ID_CONFLICT, and
SUBRACK_ID_MISMATCH alarms are generated. If yes, process these alarms in
advance.
2. Check whether the alarm is cleared. If the alarm persists, see cause 3 of multiple boards
reporting this alarm.
1. Check whether the active SCC or active cross-connect board also reports the
BD_STATUS and HARD_BAD alarms. Reseat the board. For the operation of
reseating the board, see "Removing Boards" and "Inserting Boards".in the Quick
Installation Guide.
2. Check whether the alarm is cleared. If the alarm persists, replace the relevant board.
See For details, refer to "Replacing a Board" of the Supporting Tasks..
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
----End
Related Information
None
3.7 ETH_8B10B_ERR
Description
The ETH_8B10B_ERR alarm indicates the Ethernet line signal encoding/decoding error. The
alarm is generated when the signals is converted from 8bit mode to 10bit mode.
Reported from the WDM side or client side: Client side
Attribute
Minor Communication alarm
Parameters
None

The coding and encoding errors of the signals on the Ethernet line may lead to bit errors. If the
alarm persists consecutively generated for a long time, the service may be interrupted.

Possible Causes
l Cause 1: The fiber between the access equipment and the optical interface on the client side
of the board is faulty.
l Cause 2: The access equipment on the client side is faulty.
l Cause 3: The board where the alarm is generated is faulty.
Procedure
l Cause 1: The fiber between the access equipment and the optical interface on the client side
of the board is faulty.
1. Check whether the attenuation of the fiber between the access equipment and the
interface on the client side of the board is overlarge, and whether the fiber is aged or
loose. If yes, clean the fiber connector or replace the fiber.
l Cause 2: The access equipment on the client side is faulty.
1. Outloop the client-side transmit and receive optical interfaces, check whether the
alarm on the client side of the board is cleared.
2. If the alarm persists, locate the fault of the client-side access equipment and remove
the fault.
3. If the alarm clears, locate the fault of the board at the local station, see cause 3.
l Cause 3: The board where the alarm is generated is faulty.
1. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
None
3.8 EX_ETHOAM_CC_LOS
SF64, SF64A, SFD64, SL64, SLD64, 3.8.1 EX_ETHOAM_CC_LOS(OCS)

Boards other than the SF64, SF64A, SFD64, 3.8.2 EX_ETHOAM_CC_LOS(OTN)

SLO16, or EGSH
3.8.1 EX_ETHOAM_CC_LOS(OCS)

Description
The EX_ETHOAM_CC_LOS alarm indicates the loss of the periodic continuity check (CC)
message. When the sink maintenance point receives the CC message from the source
maintenance point, the timer is started to periodically check the link between the source and sink
maintenance points. If the sink maintenance point does not receive the CC message from the
source maintenance point in one period (3.5 times the time the CC message is transmitted from
the source maintenance point to the sink maintenance point), this alarm is generated.
Attribute
Critical Communication alarm
Parameters
Name Meaning
Parameters 1 and 2 Indicates the VLAN ID, consisting of two bytes.
Parameter 3 Indicates the level of the maintenance domain, consisting of one byte.
Parameters 4 to 7 Indicates the ID of the local maintenance point, consisting of four bytes.
Parameters 8 to 12 Indicates the ID of the remote maintenance point, consisting of five bytes.

When the EX_ETHOAM_CC_LOS alarm is generated, it indicates that a unidirectional
connectivity failure is detected on the link between the source and sink maintenance points.
Possible Causes
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
l A software or hardware failure occurs to the services from the source maintenance point
to the sink maintenance point.
l Service congestion or service interruption occurs between the source maintenance point
and the sink maintenance point.

Procedure
Step 1 View the EX_ETHOAM_CC_LOS alarm on the U2000 and confirm the ID of the relevant
maintenance point according to the alarm parameters.
Step 2 Query the information about the maintenance point.
Step 3 Perform loopback (LB) and link trace (LT) test for the source and sink maintenance points, thus
to locate the fault in the services between the source maintenance point and the sink maintenance
point.
Step 4 Check the faulty services, including software , hardware, and traffic. After the services restore,
the alarm automatically clears. You may also perform LB to confirm that the alarm clears.
----End
Related Information
None
3.8.2 EX_ETHOAM_CC_LOS(OTN)
Description
The EX_ETHOAM_CC_LOS alarm indicates the loss of the periodic continuity check (CC)
message. When the sink maintenance point receives the CC message from the source
maintenance point, the timer is started to periodically check the link between the source and sink
maintenance points. If the sink maintenance point does not receive the CC message from the
source maintenance point in one period (3.5 times the time which the CC message is transmitted
from the source maintenance point to the sink maintenance point), this alarm is generated.
Attribute
Parameters
Parameters 1 and 2 Indicates the ID of the Ethernet port where the alarm is generated,
consisting of two bytes.

Parameters 3 and 4 Indicates the VLAN ID, consisting of two bytes.
Parameter 5 Indicates the level of the maintenance domain, consisting of one byte.
Parameters 6 to 9 Indicates the ID of the locate maintenance point, consisting of four bytes.
Parameters 10 to 14 Indicates the ID of the remote maintenance point, consisting of five bytes.

When the EX_ETHOAM_CC_LOS alarm is generated, it indicates that a unidirectional
connectivity failure is detected on the link between the source and the sink maintenance points.
Possible Causes
l Cause 1: A software or hardware failure occurs in the services from the source maintenance
point to the sink maintenance point.
l Cause 2: Service congestion or service interruption occurs between the source maintenance
point and the sink maintenance point.
Procedure
l Cause 1 and Cause 2: A software or hardware failure, service congestion or service
interruption occurs between the source maintenance point and the sink maintenance point.
1. View the EX_ETHOAM_CC_LOS alarm on the U2000 and confirm the ID of the
relevant maintenance point according to the alarm parameters.
2. Query the information about the maintenance point.
3. Perform loopback (LB) and looptracing (LT) for the source and sink maintenance
points, thus to locate the fault in the services between the source maintenance point
and the sink maintenance point.
4. Check the faulty services, including software, hardware, and traffic. After the services
restore, the alarm automatically clears. You may perform LB to confirm that the alarm
clears.
----End
Related Information
None
3.9 FC_LINK_ERR
Description
FC_LINK_ERR is an alarm indicating the FC service link failure. The alarm is generated when
the FC link is faulty.

Attribute
Parameters
Parameter 1 Indicates WAN down/WAN up. 0x00 indicates WAN up; 0x01 indicates WAN
down.
Parameter 2 Indicates the FCBB network status.
When parameter 1 is 0x00, parameter 2 is a fixed value of 0xff;
When parameter 1 is 0x01, parameter 2 indicates the FCBB link status.
0x01 Indicates that the protocol parameter ISL mode is incorrect, and the traffic
control management mode at the transmit end mismatches that at the receive end.
0x02: Indicates that the LEM state machine is not successfully closed. The LEM
state machine can distinguish between Client and WAN.
0x03: Indicates that the GFPT_Link Init state is not completed.
0x04: Indicates that the ping/ping_Ack result and the configured Buffer water
line do not match.
0x11: Indicates that the online to offline protocol at the FC port fails to be
enabled.
0x12: Indicates that the link reset protocol at the FC port fails to be enabled.
0x13: Indicates that the link fail protocol at the FC port fails to be enabled.
0x14: Indicates that the link init protocol at the FC port fails to be enabled.

The services might be interrupted.
Possible Causes
l Cause 1: The LOF, OOF or BDI alarm is generated on the client side or the WDM side.

l Cause 2: The protocol parameter ISL mode is incorrect, and the traffic control management
mode at the transmit end mismatches that at the receive end.
l Cause 3: The fibers on the WDM side of the board are connected improperly.
l Cause 4: The type or the time sequence of the services on the board is configured
improperly.
Procedure
l Cause 1: The LOF, OOF or BDI alarm is generated on the client side or the WDM side.
1. Check whether the LOF, OOF or BDI alarm is generated or not on the client side or
the WDM side of the local station. If yes, clear the alarm according to the
corresponding alarm handling procedure.
l Cause 2: The protocol parameter ISL mode is incorrect, and the traffic control management
mode at the transmit end mismatches that at the receive end.
1. Check whether the alarm is caused by incorrect protocol parameter ISL mode, or the
mismatched traffic control management mode. If yes, check the configuration of the
switch in the network.
2. 47. Re-configure the ISL mode and the traffic control management mode, thus to make
the ISL mode and the traffic control management mode of the switch match those of
the board.
l Cause 3: The fibers on the WDM side of the board are connected improperly.
1. Check and ensure that the fibers on the WDM side of the board that reports the alarm
are connected properly.
l Cause 4: The type or the time sequence of the services on the board is configured
improperly.
1. If the alarm persists, check whether the rate of the board and the type and the time
sequence of the services on the board are configured correctly. If not, re-configure
them.
----End
Related Information
None
3.10 FC_SYNC_LOS
Description
The FC_SYNC_LOS alarm indicates the FC service synchronous word loss. The alarm is
generated when the clock is lost and synchronization fails.

Attribute
Parameters
None

Possible Causes
l Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
l Cause 2: The optical power at the transmit end of the board is abnormal.
Procedure
l Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
1. 50. Check whether the rate that is configured for the services ports on the board where
the alarm is generated matches the rate of the actually received services. If they do
not match, you need to change the type of the accessed services or the type of the
services configured on the board according to the networking planning, thus to ensure
that the rates of these services are consistent.
l Cause 2: The optical power at the transmit end of the board is abnormal.
1. 51. Check whether the output optical power at the transmit end of the board is within
the normal range. For the optical power specification of the specific board, refer to
"Technical Specifications" of the Product Description . If the output optical power is
abnormal, see the handling procedures for the OUT_PWR_HIGH and
OUT_PWR_LOW to clear the alarm.
----End
Related Information
None
3.11 IN_PWR_HIGH

SF64, SF64A, SFD64, SL64, SLD64, 3.11.1 IN_PWR_HIGH(OCS)

Boards other than the SF64, SF64A, SFD64, 3.11.2 IN_PWR_HIGH(OTN)

SLO16, or EGSH
3.11.1 IN_PWR_HIGH(OCS)
Description
The IN_PWR_HIGH is an alarm of too high input optical power. This alarm is generated when
a board detects that the actual input power is higher than the upper threshold of the input power
reference value.
Attribute
Parameters
None

After the IN_PWR_HIGH alarm is generated, the services at the optical interface may contain
bit errors. Too high input power also causes damages to the laser.
Possible Causes
The possible causes of the IN_PWR_HIGH alarm are as follows:
l Cause of the threshold setting: The reference value or threshold of optical power is
improper.
l Cause of the external line: The attenuation value of the optical attenuator is improper.
l Cause of the board: The board at the opposite station is faulty. As a result, the transmitting
power of the opposite station is too high.
l Cause of the optical module: The type of the optical module is not correct.

Procedure
l Cause of the threshold setting: The reference value or threshold of optical power is not
correct.
1. Check the type of the optical module on the board. You can obtain the manufacturer
information about the optical module on the board through Querying Optical Module
Information in the Supporting Task.
2. Check whether the threshold of the optical power is set properly. For the operations,
see Querying Optical Power on the U2000 in the Supporting Task. If the configured
threshold is improper, re-set the input upper threshold according to the overload
optical power of the board. For details on the optical power specifications of the board,
see "Technical Specifications" of the Product Description. Then, check whether the
alarm is cleared.
3. If the alarm persists, see other causes.
l Cause of the external line: The configured attenuation value of the optical attenuator is
improper.
1. On the U2000, check whether the receive optical power of the local end is within the
normal range. For details, see Querying Optical Power on the U2000 in the Supporting
Task. For details on optical power specification of the board, see "Technical
Specifications" of the Product Description. For details, see Querying Optical Power
on the U2000 in the Supporting Task.
NOTE
2. Check whether the attenuation value of the optical attenuator is correct if the receive
optical power is excessively high. If the attenuation value is not correct, change the
value according to the receive optical power specified for the board. For details, see
Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
Then, check whether the alarm is cleared.
l Cause of the board: The transmit power of the opposite station is excessively high because
the opposite board is faulty.
1. Check whether the OUT_PWR_HIGH alarm exists at the opposite station.
2. If the alarm exists, it indicates that the optical power transmitted by the opposite station
is not standard. Replace the optical module on the board or the board at the opposite
station. For details, see Replacing the Pluggable Optical Module in the Parts
3. If the alarm persists, replace the opposite board. For details, see Parts Replacement.
l Cause of the optical module: The type of the optical module is not proper.
1. Check whether the type of the optical module on the board is proper according to the
transmission distance. For details on the mapping relationship between the optical
module type and the transmission distance, see "Technical Specifications" of the

Product Description. For details on the operation, see Querying Optical Module
2. If the type is not proper, replace the optical module or board with a proper optical
module or board. For details, see Replacing the Pluggable Optical Module in the Parts
Replacement. Otherwise, replace with the proper board. If the board supports
pluggable optical modules, replace the board with a proper board. For details, see
Parts Replacement.
----End
Related Information
None.
3.11.2 IN_PWR_HIGH(OTN)
Description
The IN_PWR_HIGH(OTN) indicates that the input optical power is excessively high. The alarm
is generated when the input optical power is higher than the upper threshold of the input optical
power.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

When the input optical power is excessively high, bit errors and LOF alarms may be generated
in the received signals, and the optical module on the board can be damaged. As a result, the
services are affected.
Possible Causes
l Cause 1 for the alarm generated on the client side: The input optical power is excessively
high, and the configured attenuation is insufficient.
l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.
l Cause 1 for the alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.

l Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is
faulty.
l Cause 1 for the alarm generated in multiple wavelengths: The input optical power is
excessively high, and the configured attenuation is insufficient.
l Cause 2 for the alarm generated in multiple wavelengths: The output optical power of the
board in the upstream station is excessively high.
l Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarm
is faulty.
Procedure
is generated.
l Cause 1 for the alarm generated on the client side: The input optical power is excessively
high, and the configured attenuation is insufficient.
1. If the alarm is generated on the client side, query the input optical power of the board
that reports the alarm on the U2000 to check whether the input optical power is within
the normal range. For the optical power specifications of the specific board, see the
Product Description. If the input power is abnormal as shown on the U2000, use a
power meter to measure the input optical power of the board that reports the alarm to
check whether the input optical power is within the normal range. If the input optical
power is abnormal, increase the attenuation to a proper extent to make the input optical
power within the normal range.
1. If the input optical power of the board that reports the alarm is normal, the board may
be faulty. In this case, replace the board. For details, refer to "Replacing a Board" of
the Supporting Tasks.
l Cause 1 for the alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.
1. If the board is generated on the WDM side, query the input optical power of the board
that reports the alarm on the U2000 to check whether the input optical power is within
the normal range. For the optical power specifications of the specific board, see the
Product Description. If the input optical power is abnormal, query the input and output
optical power of the boards in the upstream of the OTU in a reversed sequence of the
signal flow on the U2000. Locate the board with very low optical power, and then
adjust the input optical power of the board to a proper value.
faulty.
1. If the input optical power of the board that reports the alarm is normal, the board may
be faulty. In this case, replace the board. For details, refer to "Replacing a Board" of
l Cause 1 for the alarm generated in multiple wavelengths: The input optical power is
excessively high, and the configured attenuation is insufficient.
1. Test the input and output optical power of the board in the opposite station in the
reversed sequence of signal flow on the U2000. Locate the board with very high optical
power, and then adjust the input optical power of the board to a proper value.
l Cause 2 for the alarm generated in multiple wavelengths: The upstream board outputs very
high optical power.

1. Test the input and output optical power of the board in the opposite station in the
reversed sequence of signal flow on the U2000.
2. If the optical power is excessively high, check the input and output optical power of
the upstream boards in turn to determine whether they are within a normal range. If
both the input and output optical power of the upstream boards is abnormal, adjust the
input optical power to a proper value. For the optical power specifications of the
specific board, see Product Description.
3. If the input optical power of the upstream board is within a normal range, whereas the
output optical power is abnormal, the upstream board may be faulty. Replace the
board. For details, refer to "Replacing a Board" of the Supporting Tasks.
l Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarm
is faulty.
1. If the alarm persists, query the input optical power of the board that reports the alarm
on the U2000 to check whether the input optical power is within a normal range. For
the optical power specifications of the specific board, see Product Description. If the
input optical power is abnormal as shown on the U2000, the board may be faulty.
Replace the board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
The optical attenuator is marked with attenuation values in the unit of dB.
3.12 IN_PWR_LOW
SF64, SF64A, SFD64, SL64, SLD64, 3.12.1 IN_PWR_LOW(OCS)

Boards other than the SF64, SF64A, SFD64, 3.12.2 IN_PWR_LOW(OTN)

SLO16, or EGSH
3.12.1 IN_PWR_LOW(OCS)
Description
The IN_PWR_LOW alarm indicates excessively low input optical power. This alarm is
generated when a board detects that the actual input power is lower than the lower threshold of
the input power reference value.

Attribute
Parameters
None

After the IN_PWR_LOW alarm is generated, the services at the optical interface may contain
bit errors.
Possible Causes
The possible causes of the IN_PWR_LOW alarm are as follows:
l Cause of the threshold setting: The reference value or threshold of the optical power is not
correct.
l Cause of the external line: The receive optical power is excessively low because the
performance of the fiber is degraded.
l Cause of the board: The transmit power of the opposite station is excessively low because
l Cause of the optical module: The type of the optical module is not correct.
Procedure
l Query current alarms on the U2000. Determine the number of the optical interface that
reports the alarm according to parameter 1. For details, see Querying the Current Alarms
and Performance Events of a NE on the U2000 in the Supporting Task.
l Cause of the threshold setting: The reference value or threshold of optical power is not
correct.
1. Check the type of the optical module on the board. You can obtain the manufacturer
information about the optical module on the board through Querying Optical Module
2. Check whether the threshold of the optical power is set properly. For the operations,
see Querying Optical Power on the U2000 in the Supporting Task. If the configured
threshold is not correct, re-set the input lower threshold according to the optical power
receiver sensitivity of the board. For details on the optical power specifications of the
board, see the "Technical Specifications" of the Product Description. Then, check
whether the alarm is cleared.
l Cause of the external line: The receive optical power is excessively low because the
performance of the fiber is degraded.
1. On the U2000, check whether the receive optical power of the local station is within
the normal range. For details, see Querying Optical Power on the U2000 in the

Supporting Task. For details on optical power specification of the board, see
"Technical Specifications" of the Product Description.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the
2. Check whether the attenuation value of the optical attenuator is correct if the receive
optical power is excessively low. If the attenuation value is not correct, change the
value according to the receive optical power specified for the board. Then, check
3. If the alarm persists, see Inspecting and Cleaning the Fiber-Optic Connectors in the
Supporting Task to check whether the connectors are dirty. Clean the optical
connectors if they are dirty. For the operations, see the Supporting Task.
– Cleaning Optical Fiber Connectors Using Cartridge Cleaners
– Cleaning Optical Fiber Connectors Using Lens Tissue
– Cleaning Optical Adapters Using Optical Cleaning Sticks
4. If the alarm persists, check whether the fiber is damaged or oppressed. If yes, replace
the fiber. Then, check whether the alarm is cleared.
5. If the alarm persists, add a proper optical amplifier to increase the receive optical
power at the local station according to the receive optical power specified for the board.
l Cause of the board: The transmit power of the opposite station is excessively low because
1. Check whether the OUT_PWR_LOW alarm exists at the opposite station.
2. If the alarm exists, it indicates that the optical power transmitted by the opposite station
is not standard. Replace the optical module on the board or the board at the opposite
station. For details, see Replacing the Pluggable Optical Module in the Parts
l Cause of the optical module: The type of the optical module is not proper.
1. Check whether the type of the optical module on the board is proper according to the
transmission distance. For details on the mapping relationship between the optical
module type and the transmission distance, see "Technical Specifications" of the
Product Description. For details on the operation, see Querying Optical Module
2. 88. If the type is improper, replace the optical module or board with a proper optical
module or board. If the board supports pluggable optical modules, replace the
pluggable optical module. For details, see Replacing the Pluggable Optical Module
in the Parts Replacement. Otherwise, replace the board with a proper board. For
details, see Parts Replacement.
----End

Related Information
None.
3.12.2 IN_PWR_LOW(OTN)
Description
The IN_PWR_LOW(OTN) alarm indicates that input optical power is excessively low. The
alarm is generated when the input optical power is lower than the lower threshold of the input
optical power.
Attribute
Parameters
None

If the input optical power is excessively low, bit errors may be generated in the received signals,
which affect the normal receiving of the services.
Possible Causes
l Cause 1 for the alarm generated on the client side: The fiber connector is dirty, and the fiber
jumper is excessively bent, damaged or aged.
l Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attached
to the optical interface on the board that reports the alarm is excessively high.
l Cause 3 for the alarm generated on the client side: The channel use status of the board that
reports the alarm is incorrect.
l Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and the
fiber jumper is over-bent, damaged or aged.
l Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuator
attached to the optical interface on the board that reports the alarm is excessively high.
l Cause 3 for the alarm generated on the WDM side: The attenuation attached to the transmit
optical interface on the board at the opposite station is excessively high, or the transmit
optical module is faulty.
l Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient.

faulty.
Procedure
is generated.
l Cause 1 for the alarm generated on the client side: The fiber connector is dirty, and the fiber
jumper is over-bent, damaged or aged.
1. Use an optical power meter to measure the input optical power of the local board, thus
to determine whether the input optical power is within the normal range. For the optical
power specifications of the specific board, see the Product Description.
2. If the detected power is low, check the fiber connection. If the fiber connector is dirty,
clean or replace the fiber connector. For details, see the Supporting Tasks.
3. If the alarm persists, check the fiber jumper. If the fiber jumper is excessively bent,
damaged or aged, adjust the fiber jumper or replace the fiber jumper.
l Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attached
to the optical interface on the board that reports the alarm is excessively high.
1. If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical interface is excessively high. If the attenuation is excessively high,
decrease the attenuation value of the attenuator to a proper value or replace it with a
suitable attenuator.
2. If the alarm persists, replace the board that reports the alarm. For details, refer to
l Cause 3 for the alarm generated on the client side: The channel use status of the board that
reports the alarm is incorrect.
1. Check whether the channel use status on the U2000 is the same as that of the actual
channel use status setting of the board. If not, resetting the channel use status.
l Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and the
fiber jumper is over-bent, damaged or aged.
1. Use an optical power meter to measure the input optical power of the local board to
determine whether the input optical power is within the normal range. For the optical
power specifications of the specific board, see the Product Description.
2. If the detected power is excessively low, check the fiber connection. If the fiber
connector is dirty, clean or replace the fiber connector. For details, see the Supporting
Tasks.
3. If the alarm persists, check the fiber jumper. If the fiber jumper is excessively bent,
damaged or aged, adjust the fiber jumper or replace the fiber jumper.
l Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuator
attached to the optical interface on the board that reports the alarm is excessively high.
1. If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical interface is excessively high. If the attenuation is excessively high,
decrease the attenuation value of the attenuator to a proper value or replace it with a
suitable attenuator.
l Cause 3 for the alarm generated on the WDM side: The attenuation attached to the transmit
optical interface on the board at the opposite station is excessively high, or the transmit
optical module is faulty.

1. Check the board at the opposite station. If the laser on the board is shut down, of the
attenuation of the attenuator attached to the transmit optical interface on the board is
excessively high, open the laser or decrease the attenuation value of the attenuator to
a proper value, or replace the attenuator with a suitable attenuator to ensure that the
output optical power of the board is within the normal range.
2. If the alarm persists, query the performance value and alarms related to the output
optical power of the board at the opposite station. If the performance value shown in
the query result does not meet the specification requirement, for example, the TF alarm
is generated, it indicates that the optical module is faulty. Replace the board at the
opposite station. For details, refer to "Replacing a Board" of the Supporting Tasks.
l Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient. Cause 5 for the
alarm generated on the WDM side: The board that reports the alarm is faulty.
1. Query the input and output optical power of the boards in the upstream of the OTU at
the local station in the reversed sequence of signal flow on the U2000. Locate the
board with the very low optical power, and then adjust the input optical power of the
board to a proper value.
2. Check the input and output optical power of the upstream stations one by one in the
reversed sequence of signal flow on the U2000 and locate the faulty section where the
optical power is excessively low.
3. If the output optical power of the upstream station is normal, check the cables, fiber
jumpers, fiber connectors, and attenuators. If the attenuation of the cables is higher
than the attenuation in the engineering design, adjust the attenuator, rectify or change
the cables. If the fiber jumper, fiber connector or the attenuator is dirty, clean or replace
the fiber jumper, fiber connector or attenuator. For details, see the Supporting Tasks;
4. If the output optical power of the upstream station is abnormal, handle the faults at
the upstream station so that the output optical power is normal.
5. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
l If the alarm is generated in multiple wavelengths, the alarm handling method is similar to
the handling method for the alarm generated on the WDM side.
----End
Related Information
None
3.13 INTRA_OTU_PS
Description
The INTRA_OTU_PS alarm indicates the intra-board 1+1 protection switching. This alarm
occurs when the intra-board 1+1 protection group actuates switching in which the current
channel switches to the protection channel from the working channel.
Reported from the WDM side or client side: WDM side

Attribute
Parameters
None

When the intra-board 1+1 protection group actuates switching, services are transiently
interrupted. When this alarm is reported, the working channel of the intra-board 1+1 protection
group might have faulty services that needs to be restored.
Possible Causes
switching. Such a command makes the current channel of the intra-board 1+1 protection
group switch to the protection channel from the working channel. Hence, the alarm is
reported.
l Cause 2: The services of the working channel of the intra-board 1+1 protection group are
is reported.
Procedure
switching.
l Cause 2: The services of the working channel of the intra-board 1+1 protection group are
is reported.
relevant to the services, such as R_LOF, R_LOS, POWER_DIFF_OVER, R_LOC,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH,
IN_PWR_LOW, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG,
OTUk_EXC. If yes, handle the alarms by referring to the corresponding alarm

alarm clears.
----End
Related Information
None
3.14 LASER_MODULE_MISMATCH
Description
The LASER_MODULE_MISMATCH alarm indicates the optical module mismatch. This alarm
is generated when the type of the optical module mismatches the type of the board.
Attribute
Parameters
None

The LASER_MODULE_MISMATCH alarm results in that services cannot be normally
received or transmitted. It can even cause service interruption.
Possible Causes
l Cause 1: The rate of the corresponding logical optical interface is inconsistent with the
actual rate of the physical optical module on the board.
l Cause 2: The type of the logical optical interface is inconsistent with the type of the physical
optical module on the board.
Procedure
l Cause 1: The rate of the corresponding logical optical interface is inconsistent with the
actual rate of the physical optical module on the board.
1. Check whether the rate of the logical optical interface is consistent with the rate of the
corresponding physical optical interface on the board or not. If not, re-configure the
logical rate.
l Cause 2: The type of the logical optical interface is inconsistent with the type of the physical

1. Check whether the optical module type of the board is correct. If yes, re-configure the
type of the corresponding logical optical interface.
2. If no, replace the optical module on the board with another one of the right type.
----End
Related Information
None
3.15 LINK_ERR
SF64, SF64A, SFD64, SL64, SLD64, 3.15.1 LINK_ERR(OCS)

Boards other than the SF64, SF64A, SFD64, 3.15.2 LINK_ERR(OTN)

SLO16, or EGSH
3.15.1 LINK_ERR(OCS)
Description
The LINK_ERR alarm indicates incorrect data link. This alarm is generated when the Ethernet
connection is incorrect and the port negotiation fails.
Attribute
Parameters
None

When the LINK_ERR alarm is generated during the data transmission, the network port
negotiation fails. The data cannot be received and the services are interrupted.

Possible Causes
The possible causes of the LINK_ERR alarm are as follows:
l The working modes of optical interfaces at the transmit and receive ends are inconsistent.
Hence, the negotiation fails.
l The link is faulty.
l The electrical cable, fiber connection, or opposite equipment is faulty.
Procedure
Step 1 View the LINK_ERR alarm on the U2000 to confirm the relevant board. Confirm the specific
port ID of the board.
Step 2 Check whether the working mode of the local port is consistent with that of the port at the
opposite station. If not, change it and then check whether the LINK_ERR alarm is cleared.
Step 3 If the alarm persists, check whether the electrical cable or fiber connection is faulty. If yes, fix
the electrical cable or fiber connection, and then check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the opposite equipment is faulty. If yes, replace the board
at the opposite station, and then check whether the alarm is cleared.
Step 5 If the alarm persists, replace the board that generates the alarm. After you make sure that the
working modes of the ports at the local and opposite stations are consistent, the LINK_ERR
alarm is automatically cleared.
----End
Related Information
None
3.15.2 LINK_ERR(OTN)
Description
The LINK_ERR(OTN) alarm indicates the link error. The alarm is generated when the link of
the Ethernet data port is down.
Attribute
Parameters
None


When the link of the Ethernet ports is down, a valid link cannot be created between the two data
ports and the data services are interrupted.
Possible Causes
l Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
l Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports
are inconsistent. For example, one port is in the auto-negotiation mode but the other is non-
negotiation.
l Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or very low.
l Cause 4: The optical interface types (and the fiber types) of the two interconnected Ethernet
ports are inconsistent.
l Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails.
l Cause 6: The data equipment on the client side is faulty.
Procedure
is generated.
l Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
1. Check whether the service type of the OTU at the local station matches the type of
the services transmitted from the client data equipment. If not, replace the OTU with
an OTU of a proper service type. For details, refer to "Replacing a Board" of the
Supporting Tasks.
l Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports are
inconsistent.
1. Check whether the auto-negotiation mode of the optical interface on the board that
reports the alarm is consistent with that of the client data equipment. If they are
inconsistent, modify the setting to ensure the consistency.
l Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or very low.
1. Check whether the input optical power of the Ethernet port on the two ports that are
interconnected is within the normal range. For the optical power specifications of the
specific board, see the Product Description.
2. If the input optical power is abnormal, see the handling procedures for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
l Cause 4: The optical module types of the two interconnected Ethernet boards are
inconsistent. Hence, the types of fibers that the two optical modules support are different.
1. Check whether the types of fibers that the two optical modules support are consistent.
If they are inconsistent, replace either board to make the type of the two optical
modules match the fiber type.

l Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails.
1. Check whether the fiber or cable that is used to connect the two Ethernet ports are
properly connected. If they are not properly connected, reconnect or replace the fiber
or cable.
l Cause 6: The data equipment on the client side is faulty.
1. Check whether the data equipment on the client side is faulty. If the equipment is
faulty, troubleshoot the fault of the data equipment on the client side.
1. If the alarm persists, perform a cold reset on the faulty board through the U2000.
----End
Related Information
None.
3.16 LOOP_ALM
SF64, SF64A, SFD64, SL64, SLD64, 3.16.1 LOOP_ALM(OCS)

Boards other than the SF64, SF64A, SFD64, 3.16.2 LOOP_ALM(OTN)

SLO16, or EGSH
3.16.1 LOOP_ALM(OCS)
Description
The LOOP_ALM alarm indicates a loopback. Loopback is classified into optical interface
loopback and VC-4 channel loopback. This alarm is generated when service loopback is set.
Attribute
Minor Equipment alarm

Parameters
Name Meaning
Parameter 1 Indicates the status of loopback.
The values are as follows:
l 0x00: Non-Loopback.
l 0x01: Inloop.
l 0x02: Outloop.

When the LOOP_ALM alarm is generated, it indicates that the system loopback is performed.
In this case, if services are running on the optical interface or channel, the services are interrupted.
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
The board loopback is manually configured.
Procedure
Step 1 After you manually cancel the loopback configuration, the LOOP_ALM alarm is automatically
cleared.
----End
Related Information
None.
3.16.2 LOOP_ALM(OTN)
Description
The LOOP_ALM(OTN) alarm indicates a loopback. The alarm is generated when the optical
interface of the board is in the loopback status.

Attribute
Parameters
Parameters 1 and 2 Indicate the optical interface where the alarm is generated. For example,
0x00 0x01 indicates optical interface 1.
Parameter 3 Indicates the loopback type:

l 0x00: Inloop.
l 0x01: Outloop.

Services are interrupted.
Possible Causes
l Cause 1: The loopback command is issued during testing or maintenance.
Procedure
is generated.
l Cause 1: The loopback command is issued during testing or maintenance.
1. Check whether the loopback is set on the optical interface during testing or
maintenance. After the test or maintenance is complete, release the loopback
configured for the specific optical interface.
----End
Related Information
None.

3.17 LPT_ACTIVE
Description
The LPT_ACTIVE alarm indicates that the LPT switching is active. The data equipment has
protection scheme itself. Hence, the protection provided by the WDM equipment is not needed.
However, the WDM equipment is needed for informing the data equipment about the faults on
the transmission layer. In this way, the switching would be triggered for the data equipment.
The alarm is generated when switching is triggered.
Attribute
Parameters
None

When the alarm is generated, the services would be interrupted if no protection route exists. If
there is an alternative route, the services would automatically search the protection route for
automatic restoration. And a prompt would be generated to remind user to remove the fault.
Possible Causes
l Cause 1: The input signals on the client side are missing or the link generates the
LINK_ERR alarm.
l Cause 2: When the WDM equipment accesses the data services and the OTN frames are
transmitted on the line side, the alarm may be triggered by the R_LOS, OTUk_AIS,
OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS,
ODUk_TCMn_OCI or ODUk_TCMn_LCK alarm on the line side.
l Cause 3: When the WDM equipment accesses the data services and the SDH frames are
transmitted on the line side, the alarm may be triggered by the R_LOS or R_LOF alarm on
the line side.
l Cause 4: For the model that the line unit and the tributary unit are separated, if the cross-
connection configuration does not exist, the alarm would be generated.
Procedure
is generated.

l Check whether the service type accessed by the WDM equipment and the frame format
transmitted on the line side is consistent with that of the service configuration model by
using the U2000. If they are inconsistent, configure them to ensure the consistency.
l Cause 1: The input signals on the client side are missing or the link generates the
LINK_ERR alarm.
1. Check whether the R_LOS or the LINK_ERR alarm is generated on the client side.
If yes, clear the R_LOS or LINK_ERR alarm on the client side.
l Cause 2: When the WDM equipment accesses the data services and the OTN frames are
transmitted on the line side, the alarm may be triggered by the R_LOS, OTUk_AIS,
OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS,
ODUk_TCMn_OCI or ODUk_TCMn_LCK alarm on the line side.
1. If the frames on the line side are transmitted in the OTN format, query whether there
are R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI or
ODUk_TCMn_LCK alarm. If yes, clear the alarm.
l Cause 3: When the WDM equipment accesses the data services and the SDH frames are
transmitted on the line side, the alarm may be triggered by the R_LOS or R_LOF alarm on
the line side.
1. If the frames on the line side are transmitted in the SDH format, query whether the
R_LOS or R_LOF alarm is generated on the NM. If yes, clear the alarm.
l Cause 4: For the model where the line unit and the tributary unit are separated, if the cross-
connection configuration does not exist, the alarm would be generated.
1. Check the trails of the cross-connect services according to the board that generates
the alarm. For the model where the line unit and the tributary unit are separated, query
whether the cross-connection is configured through the U2000. If not, configure the
cross-connection.
----End
Related Information
None
3.18 LSR_WILL_DIE
Description
The LSR_WILL_DIE alarm indicates that the laser will be out of work.
Attribute

Parameters
None

The laser is seriously aged, and thus the quality of the output optical signals and the received
signals is decreased (for example, the optical power is lower or not stable). The impact depends
on the aging level of the laser.
Possible Causes
Cause 1: The laser is aged. The service life of the laser would be terminated.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser is aged. The service life of the laser would be terminated.
1. If the board uses pluggable optical modules, replace the specific pluggable optical
module. For details, refer to "Replacing Pluggable Optical Modules" of the Parts
Replacement.
2. If the faulty board dose not support pluggable optical modules, replace the board. For
details, refer to "Replacing a Board" of the Supporting Tasks.
l Cause 2: The detection circuit of the board is faulty.
1. Replace the board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
None.
3.19 MS_AIS
SF64, SF64A, SFD64, SL64, SLD64, 3.19.1 MS_AIS(OCS)

Boards other than the SF64, SF64A, SFD64, 3.19.2 MS_AIS(OTN)

SLO16, or EGSH

3.19.1 MS_AIS(OCS)
Description
The MS_AIS is an indication alarm in the multiplex section. When the last three bits of the K2
byte are 111 in five frames consecutively received on the receive side of the local optical
interface, the MS_AIS alarm is reported. This alarm shows that the signals in the multiplex
section corresponding to the optical interface that reports the alarm are useless.
Attribute
Parameters
None

l When the MS_AIS alarm is generated, the services are interrupted.
l After the MS_AIS alarm is generated, the board automatically returns the MS_RDI alarm
to the opposite station. Consequently, the opposite station reports the MS_RDI alarm.
Possible Causes
The possible causes of the MS_AIS alarm are as follows:
l Cause 1: The receive board at the local station is faulty.

l Cause 2: The working and protection cross-connect boards at the opposite station are not
in position or are faulty.
l Cause 3: The transmit board at the opposite station is faulty.
Procedure
l Query current alarms on the U2000. Determine the ID of the interface that reports the alarm
according to alarm parameter 1. For details, see Querying the Current Alarms and
1. Perform a cold reset on the receive board at the local station. For the operations that
are performed on the U2000, see Performing a Cold Reset of a Board in the Supporting
Task. For the operations of reseating a board, see "Removing Boards" and "Inserting
Boards" in the Quick Installation Guide. Then, check whether the alarm is cleared.

NOTICE
If the services that pass the board are not configured with protection, the services are
interrupted after you perform a cold reset on the board.
2. If the alarm persists, replace the board that reports the alarm. For details, see Parts
3. If the alarm persists, see cause 2.
l Cause 2: The working and protection cross-connect boards at the opposite station are not
in position or are faulty.
1. Check the board alarm indicator to see whether the status of the cross-connect board
status is cold reset or warm reset. Wait for 5 minutes, and then check whether the
alarm is cleared. For the description of the alarm indicators on the board, see Board
Indicators in the Hardware Description.
2. If the alarm persists, check whether the working and protection cross-connect boards
at the opposite station are loose. If yes, tighten the working and protection cross-
connect boards. For details, see "Removing Boards" and "Inserting Boards" in the
Quick Installation Guide. Then, check whether the alarm is cleared.
3. If the alarm persists, replace the cross-connect board. For details, see "Removing
Boards" and "Inserting Boards" in the Quick Installation Guide. Then, check whether
l Cause 3: The transmit board at the opposite station is faulty.
----End
Related Information
None.
3.19.2 MS_AIS(OTN)
Description
The MS_AIS(OTN) is an indication alarm in the multiplex section. The alarm is generated when
the opposite station transmits the MS_AIS signals or the receive side of the local station is faulty.
Reported from the WDM or client side: WDM side, client side.
l WDM side: In this case, the type of the service received on the WDM side is SDH.
l client side: In this case, the type of the service accessed on the client side is SDH.

Attribute
Parameters
None

l If the alarm is reported from the WDM side, the services are interrupted.
l If the alarm is reported from the client side, the services are faulty.
Possible Causes
l Cause 1 for the alarm generated on the client side: For the OTU board of which the client
side supports the SDH services, and the input signals from the client side contain MS_AIS
signals, as shown in the following figure.
Detects and reports the Detects and reports the

MS_AIS alarm MS_AIS alarm
The client signals contain

the MS_AIS signal
Client O WDM O Client

WDM
side T side T side
side
U U
Station A Station B
l Cause 1 for the alarm generated on the WDM side: The input signals from the client
equipment at the opposite station contain MS_AIS signals, which are transmitted to the
downstream station. At the same time, the MS_AIS alarm is detected on the WDM side of
the OTU at the local station and it is reported to the U2000. See the preceding figure.
faulty.
Procedure
is generated.
l Cause 1 for the alarm generated on the client side: In the case of the OTU board of which
the client side supports the SDH services, the input signals from the client side contain the
MS_AIS signal.
1. When the MS_AIS alarm is reported from the client side, remove the fault of the
equipment on the client side.

l Cause 1 for the alarm generated on the WDM side: The input signals from the client side
of the OTU at the opposite station contain MS_AIS signals.
1. Check whether the MS_AIS alarm is generated on the client side of the OTU at the
opposite station on the U2000. If yes, clear the MS_AIS alarm according to the
handling method for the alarm generated on the client side of the OTU.
faulty.
1. If the alarm persists and the MS_AIS alarm is not inserted at the opposite station, the
board that reports the alarm is faulty. Replace the board. For details, refer to "Replacing
a Board" of the Supporting Tasks.
----End
Related Information
None.
3.20 MS_RDI
SF64, SF64A, SFD64, SL64, SLD64, 3.20.1 MS_RDI(OCS)

Boards other than the SF64, SF64A, SFD64, 3.20.2 MS_RDI(OTN)

SLO16, or EGSH
3.20.1 MS_RDI(OCS)
Description
The MS_RDI is a remote defect indication in the multiplex section. When the last three bits of
the K2 byte are 110 in five frames consecutively received on the receive side of the local optical
station, the MS_RDI alarm is reported. When receiving the R_LOS and MS_AIS alarms, the
opposite station returns the alarm to the local station.
Attribute

Parameters
None

When the MS_RDI alarm is generated, the local station is not affected. This alarm just shows
that the services at the opposite station are interrupted.
Possible Causes
The possible causes of the MS_RDI alarm are as follows:
l Cause 1: The opposite station receives the R_LOS and MS_AIS alarms.
l Cause 2: The transmit board at the local station is faulty.
l Cause 3: The receive board at the opposite station is faulty.
Procedure
l Cause 1: The opposite station receives the R_LOS and MS_AIS alarms.
1. On the U2000, check whether the service interruptions or bit error alarms, such as
R_LOS, R_LOF, MS_AIS, B2_EXC, and B2_SD exist at the opposite station. If
yes, clear these alarms first.
2. Then, check whether the MS_RDI alarm is cleared. If the alarm persists, see cause 2.
l Cause 2: The transmit board at the local station is faulty.
1. Perform a cold reset on the transmit board at the local station. For the operations on
the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the
operations of reseating a board, see "Removing Boards" and "Inserting Boards" in the
NOTICE
2. If the alarm persists, replace the transmit board at the local station. For details, see
Parts Replacement. Then, check whether the alarm is cleared.
l Cause 3: The receive board at the opposite station is faulty.
1. Perform a cold reset on the receive board at the opposite station. For the operations
on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For
the operations of reseating a board, see "Removing Boards" and "Inserting Boards"
in the Quick Installation Guide. Then, check whether the alarm is cleared.

NOTICE
2. If the alarm persists, replace the receive board at the opposite station. For details, see
Parts Replacement.
----End
Related Information
None.
3.20.2 MS_RDI(OTN)
Description
The MS_RDI(OTN) is a remote defect indication alarm in the multiplex section. The alarm is
generated at the local station if the opposite station back transmits the information through
overhead when the WDM-side receive part of the opposite station is faulty (for example, the
R_LOS, R_LOF or MS_AIS alarm is generated).
Reported from the WDM or client side: WDM side, client side
l WDM side: In this case, the type of the service received on the WDM side is SDH.
l Client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Parameters
None

l If the alarm is reported from the WDM side, the services may be interrupted.
l If the alarm is reported from the client side, the client-side services are faulty.
Possible Causes
l Cause 1 for the alarm generated on the client side: For the OTU board whose client side
supports the SDH services, the input signals from the client side contain the MS_RDI signal.
As shown in the following figure, the input signals from the client side of the OTU board
in local station A contain the MS_RDI signals. The OTU of station A reports the MS_RDI
alarm on the client side after it detects the MS_RDI signals.

Detects and reports the

MS_RDI alarm
The client signals contain

the MS_RDI signal
Client O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
l Cause 1 for the alarm generated on the WDM side: The receive part on the WDM side of
the opposite station detects the signal failure (for example, the R_LOS, R_LOF or MS_AIS
alarm is generated.). As shown in the following figure, the WDM side of the OTU board
in station B (the opposite station) sends the MS_RDI signals back to station A (the local
station) after it detects and reports the R_LOS, R_LOF or MS_AIS alarm. The WDM side
of the OTU board in station A reports the MS_RDI alarm after it detects the MS_RDI
signals.
Detects and reports the R_LOS,
R_LOF, MS_AIS alarm
Client O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
Detects and reports the Sends the MS_RDI
MS_RDI alarm signal back
faulty.
Procedure
is generated.
l Cause 1 for the alarm generated on the client side: In the case of the OTU board of which
the client side supports the SDH service, the input signals from the client side contain the
MS_RDI signal.
1. When the MS_RDI alarm is reported from the client side, remove the fault of the
equipment connected to the client side of the OTU board first.
l Cause 1 for the alarm generate on the WDM side: The receiver on the WDM side of the
opposite station detects a signal failure (for example, the R_LOS, R_LOF or MS_AIS alarm
is generated).

1. 151. Query the alarm of the board at the opposite station by using the U2000. If the
R_LOS, R_LOF or MS_AIS alarm exists, see the handling procedure of the R_LOS,
R_LOF or MS_AIS alarm for troubleshooting.
faulty.
1. If the alarm persists, the board at the local station is faulty. Consider whether to replace
the faulty board or not according to the actual situation (whether affects the services).
----End
Related Information
None.
3.21 MUT_LOS
Description
Loss of multiplexed signals alarm. The alarm is generated when the input multiplexed signals
of the board is lost.
Attribute
Parameters
None

The services that travel through the optical interface that generates this alarm are interrupted.
Possible Causes
l Cause 1: Fibers connected to certain optical interfaces at the receive end of the board that
reports the alarm are not connected, incorrectly connected, or damaged.
l Cause 2: The attenuation of signals in line transmission is excessively high.

Procedure
is generated.
l Cause 1: Fibers connected to certain optical interfaces at the receive end of the board that
reports the alarm are not connected, incorrectly connected, or damaged.
1. Check whether there are fibers connected to certain optical interfaces at the receive
end of the board that reports the alarm are not connected, incorrectly connected, or
damaged. If yes, connect the input optical fibers to the specific optical interface, or
replace the damaged fiber.
l Cause 2: The attenuation of signals in line transmission is excessively high.
1. Use an optical power meter to measure the actual receive optical power of the board
that reports the alarm. Check whether the receive optical power is within the normal
range. For the optical power specification of the specific board, refer to "Technical
2. If the receive optical power is excessively low, see the handling procedure of the
SUM_INPWR_LOW alarm for troubleshooting.
----End
Related Information
None
3.22 OA_LOW_GAIN
Description
The OA_LOW_GAIN alarm indicates low optical amplifier signal gain. The alarm is generated
when the actual gain of the optical amplifier board is 3 dB lower than the standard gain.
Attribute
Critical Service alarm
Parameters
None


The alarm caused by different factors has different influences on the system:
l If the alarm is generated because the input optical power is excessively high, the redundancy
of the system decreases, which influences the succeeding capacity expansion.
l If the alarm is caused by other factors (for the OAU board, including the excessive insertion
loss caused by the TDC/RDC), the input optical power of the downstream signals and the
redundancy of the system decrease. The services would have bit errors or even be
interrupted.
Possible Causes
l Cause 1: The input optical power of the board is excessively high.
l Cause 2: For the OAU board, the alarm might be generated because the insertion loss
between the TDC and RDC optical interfaces is excessively high.
Procedure
l Cause 1: The input optical power of the board is excessively high.
1. Check whether the receive optical power of the board is within the normal range on
the U2000. For the optical power specification of the specific board, refer to
"Technical Specifications" of the Product Description .
2. If the input optical power is not within the normal range, adjust the optical attenuator
attached to the input optical interface so that the input optical power meets the
specification requirement.
3. If no optical attenuator is attached to the input optical interface, add an optical
attenuator to ensure that the input optical power meet the specification requirement.
l Cause 2: The insertion loss between the TDC and RDC optical interfaces is excessively
high. (in the case of the OAU board)
1. On the U2000 query the optical power at the TDC and RDC optical interfaces on the
OAU, and then calculate the insertion loss between the TDC and RDC optical
interfaces.
NOTE
Insertion loss = Optical power at the TDC optical interface - Optical power at the RDC optical
interface. On the U2000, the difference between the optical power at optical interface 3 and
the optical power at optical interface 5 represents the insertion loss.
2. If the insertion loss is excessively high, clean the fiber jumper and fiber connector
between the TDC and RDC optical interfaces. For the insertion loss specification, see
3. If the alarm persists, replace the DCM module between the TDC and RDC optical
interfaces.
1. If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board"
of the Supporting Tasks.
----End

Related Information
None.
3.23 ODU_SNCP_PS
Description
ODUk SNCP protection switching. This alarm is generated on the board of working channel
when an ODU SNCP protection group actuates switching in which the current channel switches
to the protection channel from the working channel.
Attribute
Parameters
None

When the ODU SNCP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the ODU SNCP protection group might
have faulty services that needs to be restored.
Possible Causes
switching. Such a command makes the current channel of the ODU SNCP protection group
switch to the protection channel from the working channel. Hence, the alarm is reported.
l Cause 2: The services of the working channel of the ODU SNCP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
Procedure
switching.

l Cause 2: The services of the working channel of the ODU SNCP protection group are faulty.
reported.
relevant to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_LOFLOM,
ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM,
ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_OCI,
ODUk_TCMn_LTC, ODUk_TCMn_TIM, OTUk_DEG, OTUk_EXC,
ODUk_PM_DEG, ODUk_PM_EXC, ODUk_TCMn_DEG,
ODUk_TCMn_EXC. If yes, handle the alarms by referring to the corresponding
alarm handling procedures.
alarm clears.
----End
Related Information
None
3.24 ODUk_PM_AIS
Description
The ODUk_PM_AIS is the ODUk PM alarm indication signal. An AIS signal travels
downstream, which indicates that a signal failure is detected in the upstream.
k indicates the level of rate and its value is 0,1, 2, or 3.
Attribute
Parameters
None

The services borne on the optical interface would be unavailable.

Fault Symptom
Table 3-12 lists the fault symptoms for the ODUk_PM_AIS alarm.
Table 3-12 Fault symptoms for the ODUk_PM_AIS alarm
Fault Symptom Cause
The client side of the corresponding OTU Cause 1 for this alarm generated on the WDM
board at the opposite station reports an side: The client side of the corresponding
ODUk_PM_AIS, R_LOS, OTUk_LOF, OTU board at the opposite station reports an
OTUk_LOM, or OTUk_TIM alarm. ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm and then
inserts an AIS signal to the local station.
The WDM side of the OTU board at the local Cause 2 for this alarm generated on the WDM
station reports an R_LOS, OTUk_LOF, side: The WDM side of the OTU board at the
OTUk_LOM, or OTUk_TIM alarm. local station reports an R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm, and thus
the board at the local station also reports an
ODUk_PM_AIS alarm.
NOTE
Possible Causes
l Cause 1 for the alarm generated on the client side: Signals input from the client side contain
ODUk_PM_AIS signals.
See the following figure.
The input signals on the client side of the OTU at station A contain ODUk_PM_AIS signals.
The OTU at station A reports an ODUk_PM_AIS alarm on the client side after detecting
the ODUk_PM_AIS signals.

Detects and reports

the ODUk_PM_AIS alarm
The client
signals contain
the ODUk_PM_AIS
signal O O
Client T WDM WDM T Client
side U side side U side
Station A Station B
l Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty.
l Cause 1 for this alarm generated on the WDM side: The client side of the corresponding
board at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm, and then inserts an AIS signal to the local station.
See the following figure.
The client side of the OTU at station A automatically inserts an ODUk_PM_AIS signal
into the WDM-side signals after detecting an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm. The WDM side of the OTU at station B reports an
ODUk_PM_AIS alarm after detecting an ODUk_PM_AIS signal.
Detects and reports the

ODUk_PM_AIS, R_LOS, Insert the Detects and reports
OTUk_LOF, OTUk_LOM, ODUk_PM_AIS the ODUk_PM_AIS alarm
OTUk_TIM alarm signal
Client O WDM WDM O Client

side T side side T side
U U
Station A Station B
l Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at
the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and
thus the OTU board at the local station also reports an ODUk_PM_AIS alarm.
Procedure
is generated.
ODUk_PM_AIS signals.

1. If this alarm is reported from the client side of the board, apply a hardware loopback
between the transmit and receive optical interfaces on the client side of the OTU at
station A. If the alarm persists, it indicates that the OTU hardware is faulty. In this
case, see the alarm handling procedure for cause 2 of this alarm generated on the client
side.
NOTICE
Configuring a loopback on the board interrupts the services on the board.
2. If the alarm is cleared, it indicates that the input signals on the client side of the board
contain bit errors. In this case, rectify the fault on the client equipment.
l Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty.
1. Check whether the board that reports this alarm supports pluggable optical modules.
If ... Then ...
Replacement.
Tasks.
l The client side of the corresponding OTU board at the opposite station reports an
ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm and then
inserts an AIS signal to the local station
1. On the U2000, check whether an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM or OTUk_TIM alarm exists on the client side of the OTU board at the
opposite end. If the alarm exists, check the equipment at the opposite station.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the WDM side.
l Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at
the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and
thus the OTU board at the local station also reports an ODUk_PM_AIS alarm.
1. On the U2000, check whether an R_LOS, OTUk_LOF, OTUk_LOM, or
OTUk_TIM alarm exists on the WDM side of the OTU at the local station. If yes,
rectify the fault at the local station to clear the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709

3.25 ODUk_PM_BDI
Description
The ODUk_PM_BDI is a ODUk PM backward defect indication. The alarm is generated when
the PM section at the opposite station detects a signal failure and sends the BDI alarm back to
the local station.
Attribute
Parameters
None

The services borne by the optical interface would be unavailable.
Possible Causes
ODUk_PM_BDI signals.
l Cause 1 for the alarm generated on the WDM side: The WDM side of corresponding board
at the opposite station reports the ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_TIM, ODUk_PM_SSF alarms, and then sends the BDI
alarm back to the local station.
Procedure
l Query whether there is an alarm with higher severity on the board by using the U2000. If
there is, handle the alarm with higher severity.
ODUk_PM_BDI signals.
1. If the alarm is reported from the client side, eliminate the alarm according to the
manual of the client equipment.
l Cause 1 for the alarm generated on the WDM side: The WDM side of corresponding board
at the opposite station reports the ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_TIM, ODUk_PM_SSF alarms, and then sets BDI alarm
back to the local station.

1. If the alarm is reported from the WDM side, check whether the corresponding OTU
board in the opposite station receives the ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_PM_SSF alarms
by using the U2000. If yes, handle the corresponding alarms in the opposite station.
----End
Related Information
ITU-T G.709
3.26 ODUk_PM_DEG
Description
The ODUk_PM_DEG alarm indicates that the ODUk PM signal is degraded. This alarm is
generated when the BIP8 detection mode is bursty mode and the signal degradation or bit error
count exceeds the threshold. This alarm is generated when the BIP8 detection mode is poisson
mode and the signal degradation exceeds the threshold.
Attribute
Parameters
None

If the alarm is generated, the services borne on the optical interface would generate bit errors,
which makes the service signals unavailable.
Possible Causes
l Cause 1: The input optical power of the board is abnormal.
l Cause 2: The fiber of the transmission line is abnormal.
Procedure
l Cause 1: The input optical power of the board is abnormal.

1. Use the U2000 to browse alarms of the entire network to confirm the slot ID, interface
ID, and channel ID of the board that generates this alarm.
2. Check whether the input optical power of the point that first generates the alarm is
within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description .
3. If the optical power is not within the normal range, adjust the input optical power of
the board to a proper value.
l Cause 2: The fiber of the transmission line is abnormal.
1. If the alarm persists, check whether the fiber meets the following requirements:
– The bending radius is not less than 40 mm.
– The optical interface connector is well installed.
– The fiber connector is clean.
– The cable is intact.
2. If the fiber does not meet the requirements, remove the fault.
1. If the alarm persists, replace the board that reports the alarm. For details, refer to
----End
Related Information
ITU-T G.709
3.27 ODUk_PM_EXC
Description
The ODUk_PM_EXC alarm indicates that the ODUk PM section BIP8 error count exceeds the
threshold. This alarm is generated when the BIP8 detection mode is poisson mode and bit error
count exceeds the threshold.
k indicates the level of rate and its value is 1, 2, or 3.
Attribute

Parameters
None


The alarm has an influence on the QoS of the service signals.
Possible Causes
l Cause 1: The attenuation of the received signals is excessively high, and the fiber of the
transmission line is abnormal.
l Cause 2: The transmit part of the opposite station is faulty.
l Cause 3: The receive part of the local station is faulty.
Procedure
l Cause 1: The attenuation of the received signals is excessively high, and the fiber of the
transmission line is abnormal.
1. Check whether the receive optical power of the interface is within the normal range
by using the U2000. For the optical power specification of the specific board, refer to
2. If the receive optical power of the board at the local station is excessively low, clear
the alarm according to the handling procedure of the IN_PWR_LOW alarm.
3. If the alarm persists, check whether the transmit optical power of the corresponding
interface on the upstream board is within the normal range by using the U2000. For
the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description . If the transmit optical power of the board
in the upstream station is excessively low, clear the alarm according to the handling
procedure of the OUT_PWR_LOW alarm.
1. Loop back the transmit optical interface and receive optical interface on the WDM
side of the OTU board at the upstream station. If the bit error exists, clear the bit error
fault of the upstream station.
l Cause 3: The receive part at the local station is faulty.
1. If the alarm persists, replace the faulty board at the local station. For details, refer to
----End
Related Information
ITU-T G.709
3.28 ODUk_PM_SSF
Description
The ODUk_PM_SSF is an alarm indicating signal failure at the ODUk PM layer.

Attribute
Parameters
None

Fault Symptom
Table 3-13 lists the fault symptom for the ODUk_PM_SSF alarm.
Table 3-13 Fault symptom for the ODUk_PM_SSF alarm
Fault Symptom Cause
A station may report the R_LOS, OTUk_SSF Cause 1: The line in the regeneration span is
alarm at the same time. abnormal when there are electrical
regeneration boards.
Cause 4: In the case of a station configured
with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm
when the line is abnormal.
A station may report the ODUk_TCMn_SSF, Cause 2: The station reports an alarm of the
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn type and the ODUk_PM_SSF
ODUk_TCMn_AIS, ODUk_TCMn_LTC, or alarm at the same time.
ODUk_TCMn_TIM alarm at the same time.
A station may report the OTUk_TIM alarm at Cause 3: The station reports the OTUk_TIM
the same time. alarm and the ODUk_PM_SSF alarm at the
same time.
NOTE
Possible Causes
l Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration
boards. As shown in the following figure, when the line in the span from the OTU1 board
at station A to the OTU2 board at station B or in the span from the OTU3 board at station
B to the OTU4 board at station C is abnormal, the OTU4 board at station C reports the
ODUk_PM_SSF alarm.

M M M M
O U OA OA U U U
O O OA OA O
T X/ F F X/ X/ F F X/
T T T
U D I I D D I I D
U U U
1 M U U M M U U M
OA OA 2 3 4
Client WDM U U U OA OA U
side side X X X X WDM Client
side side
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
l Cause 2: When Sink Enable Status is Enabled and Source Mode is Operation Mode for
the TCM overheads of the station, the station reports the ODUk_TCMn_SSF,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, or
ODUk_TCMn_TIM alarm and the ODUk_PM_SSF alarm at the same time. The
ODUk_TCMn_LTC alarm is reported only when Enable LTC Response is set to
Enabled. The ODUk_TCMn_TIM alarm is reported only when Enable TIM Response is
set to Enabled.
l Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the
same time. The OTUk_TIM alarm is reported only when Enable TIM Response is set to
Enabled.
l Cause 4: In the case of a station configured with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm when the line is abnormal.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
l Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration
boards.
1. According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station, for example, the OTU4
board at station C in the figure.
2. If the OTU4 board is a tributary-line board, check whether the OTU2 board at station
B reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms.
If ... Then ...
The OTU2 board reports the Handle these alarms in advance. That is,
preceding alarms, clear these alarms according to the
corresponding methods.
The OTU2 board does not report the See cause 2.

preceding alarms,
3. If the OTU4 board consists of a tributary board and a line board, check whether the
line board at station C reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms.

If ... Then ...
The line board at station C reports Handle these alarms in advance. That is,
the preceding alarms, clear these alarms according to the
The line board at station C does not See the next step.
report the preceding alarms,
4. Check whether the OTU2 board at station B reports the R_LOS, OTUk_SSF, and
OTUk_LOF alarms.
If ... Then ...
The OTU2 board at station B reports Handle these alarms in advance. That is,
The OTU2 board at station B does See cause 2.

not report the preceding alarms,
l Cause 2: The station reports an alarm of the ODUk_TCMn type and the ODUk_PM_SSF
alarm at the same time.
1. According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station.
2. Check whether the ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI,
ODUk_TCMn_AIS, ODUk_TCMn_LTC, or the ODUk_TCMn_TIM alarm is
reported at the station. If yes, handle the alarm in advance. That is, clear the alarm
according to the corresponding method.
l Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the
same time.
1. Check whether the OTUk_TIM alarm is reported at the station. If yes, handle the alarm
in advance. That is, clear the alarm according to the corresponding method.
l Cause 4: In the case of a station configured with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm when the line is abnormal.
1. Check whether the R_LOS, OTUk_SSF, and OTUk_LOF alarms are reported on the
WDM side of the line board at the station. If yes, handle the alarms in advance. That
is, clear the alarms according to the corresponding methods.
If ... Then ...
The line board at the station reports Handle these alarms in advance. That is,

If ... Then ...
The line board at the station does not Contact Huawei engineers.
report the preceding alarms,
----End
Related Information
None
3.29 OMS_FDI
Description
The OMS_FDI alarm is a forward defect indication at OMS layer. When the OMS_FDI-P and
OMS_FDI-O alarms coexist, this alarm is generated. At the same time, the OMS_FDI-P and
OMS_FDI-O alarms are suppressed. When the board at the OTS layer detects a signal loss alarm
but cannot forward the alarm to the downstream station, it inserts the OMS_FDI signal. When
the downstream station receives the OMS_FDI signal, it reports the OMS_FDI alarm.
Attribute
Parameters
None

Possible Causes
l Cause 1: The logical fiber connection is not consistent with the physical fiber connection.
l Cause 2: In the upstream path, fiber cut occurs, the optical power is excessively low, or
dispersion degrades. Thus, the loss of signal is detected in the downstream path, and the
OMS_FDI signal is inserted to the downstream path.
Procedure
is generated.
l Cause 1: The logical fiber connection is not consistent with the physical fiber connection.

1. Check whether the logical fiber connection configured for the optical interface where
the alarm is generated is consistent with its physical fiber connection. If not, modify
the configuration of the logical fiber connection so that the logical fiber connection is
consistent with the physical fiber connection.
l Cause 2: In the upstream path, fiber cut occurs, the optical power is excessively low, or
dispersion degrades. Thus, the loss of signal is detected in the downstream path, and the
OMS_FDI signal is inserted to the downstream path.
1. Check whether there is OTS_LOS or OTS_TIM at the opposite station and all
upstream stations. If yes, clear the OTS_LOS or OTS_TIM alarm according to the
corresponding alarm handling procedure.
----End
Related Information
None.
3.30 OSC_LOS
Description
The OSC_LOS alarm indicates the loss of input optical power on receiving line. This alarm is
generated when the input optical power of the OSC board exceeds the LOS threshold.
Attribute
Parameters
None

There is a fiber break in the receive direction and this can cause loss of the monitoring signals.
Possible Causes
l Cause 1: A certain optical interface on the board that reports the alarm is not connected to
a fiber.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs
on the transmission line.

Procedure
l Query the alarm on the U2000 and record the IDs of the optical interface and channel where
l Cause 1: A certain optical interface on the board that reports the alarm is not connected to
a fiber.
1. Check whether the fiber jumper is connected to the optical interface of the board at
the local station. If not, connect the fiber jumper.
1. Use the U2000 to check whether the laser of the specific board at the opposite station
is open. If not, open the laser of the board.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs
on the transmission line.
1. On the U2000 check whether the receive optical power at the optical interface where
the alarm is generated is within the normal range. For the optical power specification
of the specific board, refer to "Technical Specifications" of the Product
Description .
2. If the receive optical power is not within the normal range, clear the alarm according
to the handling procedure for the IN_PWR_LOW or IN_PWR_HIGH.
3. If the receive optical power is normal, check the fiber connector. If the fiber connector
is dirty or damaged, clean or replace the fiber connector.
----End
Related Information
None.
3.31 OTS_LOS
Description
The OTS_LOS alarm indicates the loss of signal at OTS layer. When the OTS_LOS-P and
OTS_LOS-O alarms coexist, this alarm is generated. At the same time, the OTS_LOS-P and
OTS_LOS-O alarms are suppressed.

Attribute

Parameters
None

Possible Causes
Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
Procedure
l Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
1. Check whether the logical fiber connection of the FIU is consistent with the physical
fiber connection. If not, modify the configuration of the logical fiber connection so
that logical fiber connection is consistent with the physical fiber connection.
2. Check and make sure that the fiber connection between the "IN" interface of the local
FIU and the opposite station is correct and reliable.
3. If the alarm persists, check the attenuation of the "IN" interface of the FIU is
excessively high. If yes, adjust the attenuation to a proper value.
4. If the alarm persists, check and make sure that fibers connected to the interfaces of
the FIU are correct and reliable.
----End
Related Information
None.
3.32 OUT_PWR_HIGH
Description
The OUT_PWR_HIGH alarm indicates that the output optical power is excessively high. This
alarm is generated when the laser output optical power crosses the upper threshold.
Reported from the WDM or client side: WDM side, client side

Attribute
Parameters
None

l When the output optical power is excessively high, the input optical power at the receive
end will be very high if no proper optical attenuator is used at the receive end. As a result,
the module at the receive end may be damaged.
l If the alarm is caused by the faulty module of the laser or the faulty board, the board is
working abnormally, which affects the transmitting and receiving of the services.
Possible Causes
Cause 1: The optical module of laser is faulty or the board is faulty.
Procedure
l Cause 1: The optical module of laser is faulty or the board is faulty.
1. If the input optical power is within the normal range, the optical module of the laser
of the board might be faulty. If the board uses pluggable optical modules, replace the
specific pluggable optical module. For details, refer to "Replacing Pluggable Optical
Modules" of the Parts Replacement.
2. If the board does not support pluggable optical modules, replace the board. For details,
refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None.
3.33 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that the optical module is offline. The alarm
is generated when the board detects that the optical module is offline.

Attribute
Parameters
None

Absence of the optical module would lead to the interruption of services borne by the
corresponding optical interface.
Possible Causes
l Cause 1: The optical module does not exist or is not correctly inserted in the slot.
l Cause 2: The optical module or the board is faulty.
Procedure
is generated.
l Cause 1: The optical module does not exist or is not correctly inserted in the slot.
1. Install the optical module properly.
l Cause 2: The optical module or the board is faulty.
2. If the alarm persists, the board that reports the alarm may be faulty. If the board uses
pluggable optical modules, replace the specific pluggable optical module. For details,
refer to "Replacing Pluggable Optical Modules" of the Parts Replacement.
3. If the optical module is not pluggable, replace the faulty board. For details, refer to
----End
Related Information
None.
3.34 POWER_FAIL
Description
The POWER_FAIL alarm indicates the power failure. This alarm is generated if the power
supply of a board becomes abnormal. For example, there is overvoltage or undervoltage of the
power supply, or the battery on the SCC has no charge.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the state of the power supply in which the alarm is generated. For
example:
0x3d indicates the undervoltage of the -48 V power supply.
0x3f indicates the undervoltage of the -60 V power supply.
0x3e indicates the overvoltage of the -48 V power supply.
0x40 indicates the overvoltage of the -60 V power supply.
0x05 indicates that the voltage of the battery is excessively low or the battery
fails.
0x53 indicates the undervoltage of the -48 V fan power supply.
0x54 indicates the overvoltage of the -48 V fan power supply.

l When this alarm is reported by the SCC board, the system time is lost if the system is
powered off.
l When this alarm is reported by other boards,
– If the active power supply fails and the standby power supply is normal, which can
cause the switching of the power supply, there is no impact on the services.
– If the active power supply fails and the standby power supply fails too, the services may
be interrupted.
Possible Causes
l Cause 1: If this alarm is reported by the SCC board, it indicates the battery on the SCC has
no charge or does not provide power supply.
l Cause 2: If this alarm is reported by other boards, it indicates the power supply of the board
is faulty or aged.

Procedure
l Cause 1: If this alarm is reported by the SCC board, it indicates that the battery on the SCC
has no charge or does not provide power supply.
1. Check the battery jumper setting on the SCC. If the setting indicates that the battery
is not used, re-set the battery jumper so that the batter provides power supply to the
board. For details on battery jumper setting, see the Hardware Description.
2. If the alarm persists, replace the faulty SCC board, For details, refer to "Replacing a
Board" of the Supporting Tasks.
l Cause 2: If this alarm is reported by other boards, it indicates the power supply of the board
is faulty or aged.
1. Replace the faulty board, For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
None
3.35 PUMP_COOL_EXC
Description
The PUMP_COOL_EXC alarm indicates that the cool current of the pump laser exceeds the
threshold. This alarm is generated when the laser cooling current crosses the upper threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the threshold crossing type. The value is always 0x01.

When this alarm is reported, the optical components sharply age and the performance of output
signals degrades.

Possible Causes
l Cause 1: The ambient temperature is excessively high or low.
l Cause 2: The pump laser temperature is excessively high or low.
Procedure
l Cause 1: The ambient temperature is excessively high or low.
1. Check whether the ambient temperature is normal. If the ambient temperature is
excessively high or very low, adjust the temperature to ensure that the temperature is
within the normal range.
l Cause 2 and cause 3: The pump laser temperature is excessively high or low; the board that
reports the alarm is faulty.
----End
Related Information
None.
3.36 R_LOF
SF64, SF64A, SFD64, SL64, SLD64, 3.36.1 R_LOF(OCS)

Boards other than the SF64, SF64A, SFD64, 3.36.2 R_LOF(OTN)

SLO16, or EGSH
3.36.1 R_LOF(OCS)
Description
The R_LOF alarm indicates loss of frame on the receive side of the line. When the R_OOF alarm
are received in consecutive 3 ms by the optical interface on the receive side of the local optical
station, the R_LOF alarm is reported.

Attribute
Parameters
None

l When the R_LOF alarm is generated, the services are interrupted, and the AIS signal is
inserted in the downstream station.
l When the R_LOF occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station reports the MS_RDI alarm.
Possible Causes
The possible causes of the R_LOF alarm are as follows:
l Cause 1: Two boards at different rates are connected to each other.
l Cause 2: The receive optical power is excessively low.
l Cause 3: The receive optical power is excessively high.
l Cause 4: The transmit optical power of the opposite station is abnormal.
l Cause 6: The transmitted signals do not have the frame structure because of the fault of the
opposite board.
Procedure
l Cause 1: Two boards at different rates are connected to each other.
1. The improper fiber connection may cause that two boards at different rates are
connected to each other. This affects the service configuration. Correct the fiber
connection and then check whether the alarm is cleared.
2. If the alarm persists, check whether the types of the two boards are the same. If the
board that supports the FEC function is connected to the board that does not support
the FEC function, two boards at different rates may be connected to each other. Enable
or disable the FEC function of the two boards according to the actual condition. For
details, see Enabling the FEC Function in the Supporting Task. For details on the
boards that support the FEC function, see the "Function and Feature" of each board
in the Hardware Description. Then, check whether the alarm is cleared.
l Cause 2 and cause 3: The receive optical power is excessively low.
1. On the U2000, check whether the receive optical power of the local station is within
the normal range. For details on optical power specification of the board, see

"Technical Specifications" of the Product Description. For details of the operations,

see Querying Optical Power on the U2000 in the Supporting Task.
NOTE
manufacturer information about the optical module.
If... Then...
The receive optical power of the local board is Proceed to the next step.
excessively low
The receive optical power of the local board is Go to step 3.

excessively high
2. Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task
to check whether the connectors are dirty. If the fiber connector is dirty, clean
immediately. For the operations, see Supporting Task.

3. If the alarm persists, check whether the attenuation of the optical attenuator is correct.
If the attenuation is not correct, change the value. The attenuation of the optical
attenuator depends on the receive optical power of the board. For details, see
Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
If... Then...
The optical attenuation is excessively Decrease the optical attenuation and

low check whether the alarm is cleared. If the
The optical attenuation is excessively Increase the optical attenuation and

high check whether the alarm is cleared. If the
alarm persists, see cause 4.
4. Check whether the fiber is damaged or oppressed. If yes, replace the fiber. Then, check
1. On the U2000, check whether the transmit optical power of the opposite board is within
"Technical Specifications" of the Product Description. For details of the operations,
see Querying Optical Power on the U2000 in the Supporting Task.
NOTE

2. If the transmit optical power of the opposite board is abnormal, see the
OUT_PWR_HIGH or OUT_PWR_LOW alarm to rectify the fault. Then, check
whether the R_LOF alarm is cleared.
1. Perform a selfloop (hardware inloop) on the receive and transmit interfaces of the
board. For details, see Performing Hardware Loopback in the Supporting Task.
NOTICE
NOTICE
The overload of optical power should be avoided when the hardware inloop is
performed. According to the optical power specifications of the board, add an optical
attenuator on the receive optical interface. For the operations of adding an attenuator,
see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
If... Then...
The alarm is reported The local board is faulty. Proceed to the next step.
No alarm is reported See cause 6.
2. Replace the optical module or board at the local station. For details, see Replacing the
Pluggable Optical Module in the Parts Replacement. Otherwise, replace the faulty
board. For details, see Parts Replacement. Then, check whether the alarm is cleared.
l Cause 6: The transmitted signals at the opposite station do not have the frame structure.
1. Replace the optical module or board at the opposite station. For details, see Replacing
the Pluggable Optical Module in the Parts Replacement. Otherwise, replace the board.
For details, see Parts Replacement.
----End
Related Information
None.

3.36.2 R_LOF(OTN)
Description
The R_LOF(OTN) alarm indicates the loss of frame on the receiving line. This alarm is generated
when the frame alignment processing is out of frame (OOF) in consecutive 3 ms.
Reported from the WDM side or client side:
l WDM side: Detect for this alarm when there are SDH frames in the services accessed on
the WDM side.
l Client side: Detect for this alarm when the SDH services are accessed on the client side.
Attribute
Parameters
None

l The board fails in locating the data frame of the received SDH signals; the client services
fail.
l The board detects this alarm, and the boards supporting protection switching perform
protection switching.
Possible Causes
l Cause 1 for the alarm generated on the client side: The input signals from the client side
contain the R_LOF signal.
l Cause 1 for the alarm generated on the WDM side: The receive optical power or the OSNR
of the local board is abnormal.
l Cause 2 for the alarm generated on the WDM side: The signals transmitted by the
upstream OTU have no SDH frame structure.
faulty.
l Cause 4 for the alarm generated on the WDM side: The input signals from the upstream
station contain the R_LOS or R_LOF signal.
l Cause 5 for the alarm generated on the WDM side: The dispersion compensation is
excessively high or low.

Procedure
is generated.
l Cause 1 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF alarm signal.
1. If this alarm is reported from the client side of the board, apply a hardware loopback
between the transmit and receive optical interfaces on the client side of the board. If
this alarm on the board persists, it indicates that the board is faulty. In this case, see
the alarm handling procedure for cause 2 of this alarm generated on the client side.
NOTICE
Configuring a loopback on the board interrupts the services on the board.
2. If this alarm is cleared, it indicates that the input signals on the client side contain an
R_LOF signal. In this case, rectify the fault on the client equipment.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
Replacement.
2. If the board does not support pluggable optical modules, Replace the faulty board.
l Cause 1 and cause 2 for the alarm generated on the WDM side: The receive optical power
or the OSNR of the local board is abnormal; the signals transmitted by the upstream OTU
have no SDH frame structure.
1. If the WDM side reports this alarm, use the U2000 to check whether client side of the
board at the opposite station reports the R_LOF alarm. If yes, remove the fault with
the solution for client-side R_LOF.
2. If the alarm persists, use the U2000 to check whether the receive optical power of the
WDM-side interface of the alarm-reporting board is in the normal range. For the
optical power specification of the specific board, refer to "Technical Specifications"
of the Product Description .
3. If the optical power is abnormal, clear the alarm as the IN_PWR_LOW or
IN_PWR_HIGH alarm.
4. If the receive optical power is normal, use the SDH meter to receive signals transmitted
by the WDM side of the board at the opposite station. Check whether the signal is
white spectrum or is not in the SDH format. If it does not comply with the requirement,
replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
faulty.
1. If the alarm persists, the board may be faulty. Replace the faulty board at the local
station. For details, refer to "Replacing a Board" of the Supporting Tasks.

l Cause 4 for the alarm generated on the WDM side: The input signals from the upstream
station contain the R_LOS or R_LOF signal.
1. If the alarm persists, clear the alarm of the equipment at the upstream station.
l Cause 5 for the alarm generated on the WDM side: The dispersion compensation is
excessively high or low.
1. If the alarm persists, replace the DCM module.
----End
Related Information
None
3.37 R_LOS
SF64, SF64A, SFD64, SL64, SLD64, 3.37.1 R_LOS(OCS)

Boards other than the SF64, SF64A, SFD64, 3.37.2 R_LOS(OTN)

SLO16, or EGSH
3.37.1 R_LOS(OCS)
Description
The R_LOS(OCS) alarm indicates the loss of signal on the receive side of the line.
Attribute
Parameters
None


l When the R_LOS alarm is generated, the services are interrupted, and the AIS signal is
inserted at the downstream station.
l When the R_LOS occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes
The possible causes of the R_LOS alarm are as follows:
l Cause 1 of the fiber: There is a fiber cut (if the alarm is reported by an SDH optical interface
board).
Identification method: Use instruments to test the fiber.
l Cause 2 of the fiber: The optical interface of the local board is not connected to the fiber
jumper or is connected to an incorrect fiber jumper (if the alarm is reported by an SDH
optical interface board).
Identification method: Check the connection of the fiber jumper.
l Cause 3 of the fiber: The line attenuation is excessively high. As a result, the optical power
is excessively low (if the alarm is reported by an SDH optical interface board).
Identification method: Query the optical power of the two stations.
l Cause 1 of the laser: The local optical interface is not used.
Identification method: Check whether the optical interface is in use (if the alarm is reported
by an SDH optical interface board).
l Cause 2 of the laser: The opposite laser is inactive, and as a result, no signal is input.
Identification method: Check whether the laser is in use (if the alarm is reported by an SDH
optical interface board).
l Cause 1 of the board: The receive board at the local station is faulty. As a result, the line
receiving fails.
Identification method: Perform a loopback.
l Cause 2 of the board: The transmit board at the opposite station is faulty. As a result, the
line transmitting fails.
Identification method: Locate the fault with the exclusive method.
Procedure
l Query current alarms on the U2000. Determine the ID of the optical interface that reports
the alarm according to alarm parameter 1. For details, see Querying the Current Alarms
l Cause 1 of the fiber: There is a fiber cut (if the alarm is reported by an SDH optical interface
board).
1. Use the optical time-domain reflectometer (OTDR) to test the fiber, and check whether
there is a fiber cut and determine the location of the fiber cut according to the
attenuation curve of the line shown on the OTDR.
NOTE
The OTDR has a dead zone when it is very close to the fiber.

If... Then...
A fiber cut occurs on the line Replace the fiber and check whether the alarm is
cleared. If the alarm persists, see other causes.
No fiber cut occurs on the line See other causes.
l Cause 2 of the fiber: The optical interface of the local board is loose, is not connected to
the fiber jumper, or is connected to an incorrect fiber jumper (if the alarm is reported by
an SDH optical interface board).
1. Check the fiber jumper connected to the optical interface of the local board.
If... Then...
The connection between the fiber Tighten the fiber jumper and check
jumper and the interface is loose whether the alarm is cleared. If the
The connection between the fiber Proceed to the next step.

jumper and the interface is secure
2. Check whether the tail fiber is connected to the optical interface of the local board
properly.
If... Then...
The fiber jumper is connected According to the networking

improperly environment, connect the fiber jumper
between optical boards in the subrack
properly and check whether the alarm is
cleared. If the alarm persists, see other
causes.
The fiber jumper is connected See other causes.

properly
l Cause 3 of the fiber: The line attenuation is excessively high. As a result, the optical power
is excessively low (if the alarm is reported by an SDH optical interface board).
1. Measure the transmit optical power of the opposite board and the receive optical power
of the local board. For details, see Querying Optical Power on the U2000 in the
Supporting Task.
If... Then...
The transmit optical power of the opposite station is See cause 2 of the board.
abnormal
The receive optical power of the local station is Proceed to the next step.
abnormal

2. The difference between the transmit optical power of the opposite station and the
receive optical power of the local station is the actual optical power attenuation of the
line. Compare the result with the line attenuation in the engineering design. If the
actual attenuation is excessively high, perform the following steps to find the fault
and rectify it.
– Check whether there are too many optical connectors on the fiber line and
whether they are connected to the optical modules securely. If the connectors are
loose, insert the connectors into the optical modules securely.
– Check whether there are aerial optical fiber cable on the fiber line that may be
damaged because of bad weather. If yes, provide a protection for the aerial optical
fiber cable.
– Check whether the type of the fiber and the attenuation factor on the fiber line
meet the requirements specified in the engineering design document. If not,
replace the fiber.
– Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting
Task to check whether the optical connector in the fiber line is dirty. If the fiber
connector is dirty, clean it immediately. For the operations, see the Supporting
Task:
3. Check whether the alarm is cleared. If the alarm persists, see other causes.
l Cause 1 of the laser: The local optical interface is not used (if the alarm is reported by an
SDH optical interface board).
1. Check whether an unused fiber is connected to the optical interface of the board. If
yes, perform the self-loop on the receive and transmit optical interfaces by using the
unused fiber.
l Cause 2 of the laser: The laser at the opposite station is inactive. As a result, no signal is
input (if the alarm is reported by an SDH optical interface board).
1. Check whether the laser of the corresponding opposite board is shut down. If yes,
switch on the laser on the optical interface. For details, see Opening/Closing Lasers
in the Supporting Task.
l Causes 1 of the board: The receive board at the local station is fault. As a result, the line
receiving fails.
NOTICE

NOTICE
If... Then...
No alarm is reported See other causes.
2. Replace the optical module or board at the local station. If the board supports pluggable
optical module, replace the specific pluggable optical module. Otherwise, replace the
faulty board. For details, see Parts Replacement.
l Cause 2 of the board: The transmit board (including the cross-connect and timing board)
at the opposite station is faulty. As a result, the line transmitting fails.
1. If the opposite board supports the pluggable optical module, replace the pluggable
optical module. Otherwise, replace the opposite faulty board. For details, see Parts
Replacement.
----End
Related Information
None.
3.37.2 R_LOS(OTN)
Description
The R_LOS(OTN) alarm indicates the loss of signal on receiving line. This alarm is generated
when the receive side receives no signals.
Attribute
Parameters
None


There is a fiber break in the receive direction and the services on this port are interrupted.
Possible Causes
l Cause 1 for the alarm generated on the client side: The fiber jumper is not connected to the
optical interface of the board.
l Cause 2 for the alarm generated on the client side: The line loss is excessively large or there
is a fiber cut.
l Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected to
the optical interface of the board.
l Cause 2 for the alarm generated on the WDM side: The line loss is excessively large or
there is a fiber cut.
l Cause 3 for the alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
l Cause 4 for the alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
Procedure
is generated.
l Cause 1 for the alarm generated on the client side: The fiber jumper is not connected to the
optical interface of the board.
l Cause 2 for the alarm generated on the client side: The line loss is excessively large or there
is a fiber cut.
1. Check whether the receive optical power of the interface of the board at the local
station is within the normal range by using the U2000. For the optical power
Description .
– If the optical power is abnormal, clear the alarm as IN_PWR_LOW or
IN_PWR_HIGH.
– If the receive optical power is normal, check the fiber connector. If the fiber
connector is dirty or damaged, clean the fiber connector. For details, see the
Supporting Tasks.
l Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected to
the optical interface of the board.

l Cause 2 for the alarm generated on the WDM side: The line loss is excessively large or
there is a fiber cut.
1. Check whether the receive optical power of the interface of the board at the local
station is within the normal range by using the U2000. For the optical power
Description .
– If the optical power is abnormal, clear the alarm as IN_PWR_LOW or
IN_PWR_HIGH.
– If the receive optical power is normal, check the fiber connector. If the fiber
connector is dirty or damaged, clean the fiber connector. For details, see the
Supporting Tasks.
l Cause 3 for the alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
1. Use the U2000 the check whether the board laser of the opposite station is open. If
not, open the laser.
l Cause 4 for the alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
1. If the alarm persists, check whether the board at the opposite station or the board at
the local station supports pluggable optical modules.
If ... Then ...
Replacement.
Tasks.
----End
Related Information
None
3.38 R_OOF
SF64, SF64A, SFD64, SL64, SLD64, 3.38.1 R_OOF(OCS)


Boards other than the SF64, SF64A, SFD64, 3.38.2 R_OOF(OTN)

SLO16, or EGSH
3.38.1 R_OOF(OCS)
Description
The R_OOF alarm indicates that the out-of-frame event occurs on the receive side of the line.
When the correct A1, A2 bytes are not contained in five consecutive frames received on the
receive side of the local optical station, the R_OOF alarm is reported.
Attribute
Parameters
None

l When the R_OOF alarm is generated, the services are interrupted, and the AIS signal is
inserted at the downstream station.
l When the R_OOF alarm is generated, the system automatically returns the MS_RDI alarm
to the upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes
The possible causes of the R_OOF alarm are as follows:
l Cause 1: The receive optical power is excessively low.

l Cause 2: The receive optical power is excessively high.
l Cause 4: The receive board at the local station is faulty (including the fault of the cross-
connect board).
l Cause 5: The transmit board at the opposite station is faulty (including the fault of the cross-
connect board).

Procedure
l Cause 1: The receive optical power is excessively low. Cause 2: The receive optical power
is excessively high.
1. On the U2000, check whether the optical power of the local station is within the normal
range. For details on optical power specification of the board, see "Technical
Specifications" of the Product Description. For details, see Querying Optical Power
on the U2000 in the Supporting Task.
NOTE
manufacturer information about the optical module on the board.
If... Then...
The receive optical power of the local board is Proceed to the next step.
excessively low
The receive optical power of the local board is Proceed to step 3.

excessively high
2. Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task
to check whether the connectors are dirty. If the fiber connector is dirty, clean it
immediately. For the operations, see Supporting Task.

3. If the alarm persists, check whether the attenuation of the optical attenuator is correct.
If the attenuation is not correct, change the value. The value of the optical attenuator
depends on the receive optical power of the board. For details, see Adjusting,
Replacing, Adding and Removing Attenuator in the Supporting Task.
If... Then...
The optical attenuation is excessively Decrease the optical attenuation. Then,

low check whether the alarm is cleared. If the
The optical attenuation is excessively Increase the optical attenuation. Then,

high check whether the alarm is cleared. If the
alarm persists, see cause 3.
4. Check whether the fiber is damaged or oppressed. If yes, replace the fiber. Then, check


1. On the U2000, check whether the transmit optical power of the opposite board is within
"Technical Specifications" of the Product Description. For details, see Querying
Optical Power on the U2000 in the Supporting Task.
NOTE
manufacturer information about the optical module on the board.
2. If the transmit optical power of the opposite board is abnormal, see the
OUT_PWR_HIGH or OUT_PWR_LOW alarm to rectify the fault. Then, check
whether the R_OOF alarm is cleared.
l Cause 4: The receive board at the local station is faulty (including the fault of the cross-
connect board).
NOTICE
NOTICE
If... Then...
No alarm is reported See cause 5.
2. Replace the optical module or board at the local station. If the board supports the
pluggable optical module, replace the pluggable optical module. For details, see
Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace
the faulty board. For details, see Parts Replacement. Then, check whether the alarm
is cleared.
3. If the alarm persists, replace the local cross-connect board. For details, see Parts
l Cause 5: The transmit board at the opposite station is faulty (including the fault of the cross-
connect board).

1. Replace the optical module or board at the opposite station. If the board supports the
pluggable optical module, replace the pluggable optical module. For details, see
Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace
the faulty board. For details, see Parts Replacement. Then, check whether the alarm
is cleared.
2. If the alarm persists, replace the cross-connect board at the opposite station. For details,
see Parts Replacement.
----End
Related Information
None.
3.38.2 R_OOF(OTN)
Description
The R_OOF(OTN) alarm indicates the out of frame on receiving line. This alarm is generated
when the heads of consecutive five frames fail to be detected.
Attribute
Parameters
None

There is a fiber break in the receive direction and the services on this port are interrupted.
Possible Causes
l Cause 1 for the alarm generated on the client side: The received signals have excessively
high attenuation or optical power.
l Cause 2 for the alarm generated on the client side: The number bit errors in the transmission
is excessively large.
l Cause 4 for the alarm generated on the client side: The clock configuration of the data
equipment at the two ends is incorrect.
l Cause 1 for the alarm generated on the WDM side: The received signals have excessive
attenuation or optical power.

l Cause 2 for the alarm generated on the WDM side: The bit errors in the transmission are
excessively large.
is faulty.
faulty.
Procedure
is generated.
l Cause 1 for the alarm generated on the client side: The received signals have excessive
1. If the client side reports this alarm, check whether the receive optical power of the
interface is within the normal range by using the U2000, For the optical power
Description .
2. If the receive optical power is not in the normal range, clear the alarm with the solution
for IN_PWR_LOW or IN_PWR_HIGH.
l Cause 2 for the alarm generated on the client side: The number of bit errors in the
transmission is excessively large.
1. Check whether there are bit error alarms. If there are bit error alarms, clear the alarms
first according to the proper handling procedure.
2. If there is no bit error alarm and the receive optical power is normal, check the fiber
connector. If the fiber connector is dirty or damaged, clean or replace the fiber
connector.
l Cause 4 for the alarm generated on the client side: The clock configuration of the data
equipment at the two ends is incorrect.
1. Check whether Clock Configuration of the data equipment at the two ends is set to
Trace the Link Clock. If yes, set the clock configuration of the data equipment at
one end to Trace the Internal Clock.
l Cause 1 for the alarm generated on the WDM side: The received signals have excessive
1. If the client side reports this alarm, check whether the receive optical power of the
interface is within the normal range by using the U2000. For the optical power
Description .
2. If the receive optical power is not in the normal range, clear the alarm with the solution
for IN_PWR_LOW or IN_PWR_HIGH.
l Cause 2 for the alarm generated on the WDM side: The number of bit errors in the
transmission is excessively large.
1. Check whether there are bit error alarms. If there are bit error alarms, clear the alarms
first according to the proper handling procedure.

2. If there is no bit error alarm and the receive optical power is normal, check the fiber
connector. If the fiber connector is dirty or damaged, clean or replace the fiber
connector.
is faulty.
1. If the WDM side reports this alarm, use the U2000 to check whether client side of the
board in the opposite station reports the R_LOF alarm. If yes, clear the alarm with the
solution for client-side R_LOF alarm.
faulty.
1. If the alarm persists, replace the faulty board, For details, refer to "Replacing a Board"
----End
Related Information
None
3.39 R_SLIP
Description
The R_SLIP alarm indicates the receive side frame slipping. The alarm is generated when the
phase deviation occurs in the received service frames of the OSC or OTC board.
Attribute
Parameters
None

The services carried by the OSC or the OTC board are affected, such as degrading in optical
supervisory signals or clock signals. This can cause NE disconnection off the NM system.
Possible Causes
l Cause 1: The clock configuration is wrong or the clock signals are not synchronous.
l Cause 2: The attenuation in the optical line is excessively high, or the receive optical power

l Cause 3: The fibers at the eastward and the westward interfaces of the OSC or the OTC are
reversely connected.
Procedure
l Cause 1: The clock configuration is incorrect or the clock signals are not synchronous.
1. Check whether the clock configuration is correct. If not, reconfigure it and ensure that
the clocks of the total network are synchronous. For details, see the Configuration
Guide.
l Cause 2: The attenuation in the optical line is excessively high, or the receive optical power
by using the U2000. For the optical power specification of the specific board, refer to
– If the receive optical power is excessively low, check the fiber jumper or the fiber
connector. If the fiber jumper or fiber connector is dirty, clean the fiber connector
or replace the fiber jumper.
– If the receive-side optical power is to high, adjust the optical attenuator to make
the receive optical power in the normal range.
l Cause 3: The fibers at the eastward and the westward interfaces of the OSC or the OTC are
reversely connected. For example, The fibers at the westward of the TM1 interface and the
eastward of the TM2 interface are reversely connected, as shown in the following figure.
1. If the alarm persists, check the engineering fiber connection figure to see whether the
fibers at the eastward and the westward interfaces of the OSC or the OTC are reversely
connected. If the fiber connection is incorrect, correct it according to the figure.
OA
F RM1 TM2 F
I SC2 I
U TM1 RM2 U
OA

1. If the alarm persists, perform a cold reset on the faulty board through the U2000.
----End
Related Information
None

3.40 REM_SF
Description
The REM_SF alarm indicates that the remote signal failure. This alarm is generated when the
client side of the board at the opposite end fails to receive signals (for example, when there is
an R_LOS alarm).
Reported from the WDM or client side: client side
Attribute
Parameters
None

Services borne by the client side of the board are interrupted.
Possible Causes
l Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the
opposite end.
l Cause 2: The client side of the OTU board at the opposite end is faulty.
Procedure
l Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the
opposite end.
1. Check whether there is an R_LOS or R_LOF alarm on the client side of the OTU
board at the opposite station on the U2000. If there is an R_LOS or R_LOF alarm, see
R_LOS or R_LOF to clear the alarm.
l Cause 2: The client side of the OTU board at the opposite end is faulty.
1. Replace the OTU board at the opposite station.For details, refer to "Replacing a Board"
----End
Related Information
None.

3.41 REMOTE_FAULT
Description
The REMOTE_FAULT alarm indicates a remote fault.
Attribute
Parameters
None

The 10GE services in the flow control mode are configured on the client side of the board . If
the board receives the REMOTE_FAULT alarm, the received services may be interrupted.
Possible Causes
l Cause 1: The opposite station receives the LOCAL_FAULT alarm.
Procedure
l Cause 1: The opposite station receives the LOCAL_FAULT alarm.
1. Clear the LOCAL_FAULT alarm in the opposite station.
1. Replace the faulty board in the opposite side. For details, refer to "Replacing a Board"
----End
Related Information
None
3.42 SECU_ALM
Description
The SECU_ALM alarm indicates an illegal login. The alarm is generated when the login fails
after four consecutive login failure performed by the same user.

Attribute
Major Security alarm
Parameters
None.

The alarm automatically ends with no impact on the system.
Possible Causes
l Cause 1: This alarm can be caused by illegal login, such as login with an incorrect password
or a user not existing.
Procedure
l Cause 1: This alarm can be caused by illegal login, such as login with an incorrect password
or a user not existing.
1. Check whether there are users illegally logging in to the NE. If yes, clear the user that
is illegally logged in to.
1. If the alarm persists when there is no user who logged in to the NE illegally, replace
the board. For details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None.
3.43 SUM_INPWR_LOW
Description
The SUM_INPWR_LOW alarm indicates that the sum input optical power is excessively low.
The alarm is generated when the input optical power of the multiplexed signals is lower than
the threshold.

Attribute
Parameters
None

The single optical signal output by the board might be lost. The services have bit errors or even
are interrupted.
Possible Causes
l Cause 1: The attenuation of the fiber increases, the fiber jumper, fiber connector or the
optical attenuator is dirty.
l Cause 2: The board in the upstream station is faulty, and thus the output optical power is
decreased.
Procedure
is generated.
l Cause 1: The attenuation of the fiber increases, the fiber jumper, fiber connector or the
optical attenuator is dirty.
1. Check the cables, fiber jumpers, fiber connectors and attenuators.
2. If the attenuation of the cables is higher than that in engineering design, adjust the
attenuator and rectify the cables.
3. If the fiber jumper, fiber connector, or fiber attenuator is dirty or damaged, replace
the fiber jumper or check and clean the fiber connector.
l Cause 2: The board in the upstream station is faulty, and thus the output optical power is
decreased.
1. Query the input and output optical power of the upstream boards in the reversed
sequence of signal flow by using the U2000 and find out the faulty area where the
optical power is excessively low. Check the output optical power of the upstream
stations. If it is abnormal, the board at the upstream station might be faulty. Replace
the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
----End

Related Information
None.
3.44 TD
Description
The TD alarm indicates the transmitter degrade. The alarm is generated when the bias current
of the laser exceeds the degrade threshold.
Attribute
Parameters
None

Possibly the board laser cannot work normally, or the output light of the laser is of poor quality
or with bit errors and further cause service break.
Possible Causes
Cause 1: The laser is aged.
Procedure
l Cause 1: The laser is aged.
Replacement.
2. If the board is not pluggable, replace the faulty board. For details, refer to "Replacing
a Board" of the Supporting Tasks.
----End
Related Information
In a cooling optical module that adopts the automatic level control (ALC) function, the laser is
aged after long-term operation and thus the laser emitting efficiency decreases. To ensure
constant output optical power, the laser bias current, an index that reflects the laser aging degree,
needs to be increased.

3.45 TF
Description
The TF alarm indicates a transmission failure. The alarm is generated when the transmit optical
power of the laser exceeds the threshold of the output optical power of the laser.
Attribute
Parameters
None

The laser transmission becomes faulty, which causes service interruption.
Possible Causes
Cause 1: The laser module is damaged, or the laser is aged.
Procedure
l Cause 1: The laser module is damaged, or the laser is aged.
2. If the alarm persists, check whether the board that reports this alarm supports pluggable
optical modules.
If ... Then ...
Replacement.
Tasks.
----End

Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after long-
term operation and thus the laser emitting efficiency decreases. To ensure constant output optical
power, the laser bias current needs to be increased. Hence, the bias current is an index that reflects
the aging degree of the laser.
3.46 TS_CFG_MISMATCH
Description
The TS_CFG_MISMATCH alarm indicates the timeslot configuration mismatch. This alarm is
generated when the configured timeslot of one board at the local station is inconsistent with the
timeslot transmitted from the opposite station.
Attribute
Major Processing
Parameters
None

If a timeslot mismatch occurs, the service cannot be received properly.
Possible Causes
Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with the
received timeslot.
Procedure
l Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with
the received timeslot.
1. Check whether the Timeslot Configuration Mode parameter of the board that reports
this alarm is set to Manual. If not, set the parameter to Manual.
2. Check whether the timeslot configuration at the transmit end of the opposite board is
consistent with the timeslot configuration at the receive end of the local board. If not,
modify the timeslot configuration of the opposite board or the local board according
to the actual service.
----End

Related Information
None
3.47 WRG_BD_TYPE
Description
The WRG_BD_TYPE alarm indicates the incorrect board type. The alarm is generated when
the logic board and the physical board are not consistent.
Attribute
Parameters
None

The type of the logical board is inconsistent with the type of the physical board. The board cannot
work normally.
Possible Causes
l Cause 1: The type of the logical board configured on the U2000 is inconsistent with the
type of the physical board installed in the slot.
Procedure
l Cause 1: The type of the logical board configured on the U2000 is inconsistent with the
type of the physical board installed in the slot.
1. Check whether the logical board configured on the U2000 has accordant board type
with the physical board in the slot. If not, check whether the fault lies in the logical
board or the physical board according to the engineering configuration requirements.
– If the logical board configuration is faulty, reconfigure the logical board on the
U2000.
– If the physical board configuration is faulty, insert a physical board of the correct
type.

NOTICE
Exercise caution when replacing the SCC board. For details on how to replace the
SCC board and the precautions, see the Parts Replacement.
----End
Related Information
None.

Alarms and Performance Events Reference 4 Alarm Processing
4 Alarm Processing
About This Chapter
This chapter describes information relevant to alarm handling, including alarm descriptions,
alarm parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.
NOTE
If the fault of an alarm cannot be located, contact Huawei engineers for troubleshooting.
The alarm handling involves board reset, either of cold or warm. Warm reset and cold reset have
different impacts on services.
l Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software,
which neither updates the FPGA or hardware data nor interrupts services. A cold reset of
the SCC may result in reconfiguration of the key hardware, such as FPGA reloading; the
upper-layer software need be restarted.
l Reset of other boards: a reset of software on other boards does not affect running services
while a reset of hardware on other boards does. A mis-reset of such a board affects the
communication between this board and the SCC and even interrupts services.
The handling measures of certain alarms in this chapter vary according to the boards that report
these alarms, and thus the handling measures of these alarms are described according to the
systems (OCS and OTN systems) that the boards belong to.
4.1 AD_CHECK_FAIL
4.2 ALM_ALS
4.3 APS_MANUAL_STOP
4.4 ALM_GFP_dCSF
4.5 ALM_GFP_dLFD
4.6 ALM_HANGUP
4.7 APS_FAIL
4.8 APS_INDI

4.9 AU_AIS
4.10 AU_LOP
4.11 B1_SD
4.12 B2_EXC
4.13 B2_SD
4.14 B3_EXC
4.15 B3_EXC_VC3
4.16 B3_EXC_VC4
4.17 B3_SD
4.18 B3_SD_VC3
4.19 B3_SD_VC4
4.20 BD_NOT_INSTALLED
4.21 BD_STATUS
4.22 BDID_ERROR
4.23 BEFFEC_SD
4.24 BIOS_STATUS
4.25 BOOTROM_BAD
4.26 C2_VCAIS
4.27 CHAN_ADD
4.28 CHIP_ABN
4.29 CLIENT_PORT_STA_INDI
4.30 CLIENT_PROT_NOTSTART
4.31 CLK_NO_TRACE_MODE
4.32 CODE_SYNC_LOS
4.33 CRC4_CROSSTR
4.34 DB_RESTORE_FAIL
4.35 DBMS_ERROR
4.36 DBMS_PROTECT_MODE
4.37 DCM_INSUFF
4.38 DLAG_PROTECT_FAIL
4.39 DSP_LOAD_FAIL

4.40 ETH_CFM_LOC
4.41 ETH_CFM_MISMERGE
4.42 ETH_CFM_MACSTATUS
4.43 ETH_CFM_RDI
4.44 ETH_CFM_UNEXPERI
4.45 ETHOAM_DISCOVER_FAIL
4.46 ETHOAM_RMT_CRIT_FAULT
4.47 ETHOAM_RMT_LOOP
4.48 ETHOAM_RMT_SD
4.49 ETHOAM_SELF_LOOP
4.50 ETHOAM_VCG_SELF_LOOP
4.51 EX_ETHOAM_MPID_CNFLCT
4.52 EXT_SYNC_LOS
4.53 EXT_TIME_LOC
4.54 FAN_FAIL
4.55 FAN_FAULT
4.56 FC_8B10BERR_OVER
4.57 FCS_ERR
4.58 FEC_LOF
4.59 FEC_OOF
4.60 FPGA_ABN
4.61 FSELECT_STG
4.62 FWD_PKT_LOSS
4.63 GAINDATA_MIS
4.64 HARD_BAD
4.65 HARD_ERR
4.66 HP_LOM
4.67 HP_RDI
4.68 HP_REI
4.69 HP_SLM
4.70 HP_TIM
4.71 HP_UNEQ

4.72 HSC_UNAVAIL
4.73 INTRA_OTU_STA_INDI
4.74 J0_MM
4.75 K1_K2_M
4.76 K2_M
4.77 L_SYNC
4.78 LAN_LOC
4.79 LAG_PORT_FAIL
4.80 LASER_HAZARD_WARNING
4.81 LASER_SHUT
4.82 LCAS_FOPR
4.83 LCAS_FOPT
4.84 LCAS_PLCR
4.85 LCAS_PLCT
4.86 LCAS_TLCR
4.87 LCAS_TLCT
4.88 LOCK_CUR_FAIL
4.89 LOCKPOW_MIS
4.90 LP_RDI_VC3
4.91 LP_SLM_VC3
4.92 LP_UNEQ_VC3
4.93 LPT_RFI
4.94 LSR_COOL_ALM
4.95 LSR_FORCE_OPEN
4.96 LSR_INVALID
4.97 LTI
4.98 MOD_COM_FAIL
4.99 MODULE_ADJUST_FAIL
4.100 MODULE_COOLCUR_OVER
4.101 MODULE_TEMP_OVER
4.102 MODULEFILE_UPDATE_FAIL
4.103 MS_REI

4.104 MS_SNCP_PS
4.105 MS_SNCP_STA_INDI
4.106 MS_APS_INDI_EX
4.107 MULTI_RPL_OWNER
4.108 NEBD_XC_DIF
4.109 NESF_LOST
4.110 NESTATE_INSTALL
4.111 NO_BD_PARA
4.112 NO_BD_SOFT
4.113 NO_ELABEL
4.114 NODEID_MM
4.115 NULL_SEND
4.116 OCH_FDI
4.117 OCH_FDI-O
4.118 OCH_FDI-P
4.119 OCH_LOS-P
4.120 OCH_OCI
4.121 OCH_SSF
4.122 OCH_SSF-O
4.123 OCH_SSF-P
4.124 ODU_AIS
4.125 ODU_LCK
4.126 ODU_OCI
4.127 ODUk_LOFLOM
4.128 ODUk_PM_LCK
4.129 ODUk_PM_OCI
4.130 ODUk_PM_TIM
4.131 ODUk_TCMn_AIS
4.132 ODUk_TCMn_BDI
4.133 ODUk_TCMn_DEG
4.134 ODUk_TCMn_EXC
4.135 ODUk_TCMn_LCK

4.136 ODUk_TCMn_LTC
4.137 ODUk_TCMn_OCI
4.138 ODUk_TCMn_SSF
4.139 ODUk_TCMn_TIM
4.140 ODU_SNCP_STA_INDI
4.141 ODUKSP_PS
4.142 ODUKSP_STA_INDI
4.143 OH_LOOP
4.144 OLP_PS
4.145 OLP_STA_INDI
4.146 OMS_BDI
4.147 OMS_BDI-O
4.148 OMS_BDI-P
4.149 OMS_FDI-O
4.150 OMS_FDI-P
4.151 OMS_LOS-P
4.152 OMS_SSF
4.153 OMS_SSF-O
4.154 OMS_SSF-P
4.155 OOL
4.156 OOS_LOST
4.157 OPA_FAIL_INDI
4.158 OPU1_MSIM
4.159 OPU1_VCAT_SQM
4.160 OPU1_VCAT_VcPLM
4.161 OPU2_MSIM
4.162 OPU3_MSIM
4.163 OPUk_PLM
4.164 OSC_RDI
4.165 OTS_BDI
4.166 OTS_BDI-O
4.167 OTS_BDI-P

4.168 OTS_LOS-O
4.169 OTS_LOS-P
4.170 OTS_TIM
4.171 OTU_AIS
4.172 OTU_LOF
4.173 OTU_LOM
4.174 OTUk_AIS
4.175 OTUk_BDI
4.176 OTUk_DEG
4.177 OTUk_EXC
4.178 OTUk_LOF
4.179 OTUk_LOM
4.180 OTUk_SSF
4.181 OTUk_TIM
4.182 OUT_PWR_LOW
4.183 OWSP_PS
4.184 OWSP_STA_INDI
4.185 PATCH_ACT_TIMEOUT
4.186 PATCH_DEACT_TIMEOUT
4.187 PATCH_PKGERR
4.188 PM_BDI
4.189 PM_BEI
4.190 PM_BIP8_OVER
4.191 PM_BIP8_SD
4.192 PM_TIM
4.193 PORTSWITCH_FAIL
4.194 POWER_ABNORMAL
4.195 POWER_DIFF_OVER
4.196 PRBS_LSS
4.197 PUM_BCM_ALM
4.198 PUM_TEM_ALM
4.199 R_LOC

4.200 RELAY_ALARM_CRITICAL
4.201 RELAY_ALARM_IGNORE
4.202 RELAY_ALARM_MAJOR
4.203 RELAY_ALARM_MINOR
4.204 REM_SD
4.205 RS_CROSSTR
4.206 RTC_FAIL
4.207 S1_SYN_CHANGE
4.208 SCC_LOC
4.209 SERVICE_TYPE_EXCEED_LICENSE
4.210 SERVICE_CAPACITY_EXCEED_LICENSE
4.211 SHELF_AREA_POWER_OVER
4.212 SLAVE_WORKING
4.213 SM_BDI
4.214 SM_BEI
4.215 SM_BIP8_OVER
4.216 SM_BIP8_SD
4.217 SM_IAE
4.218 SM_TIM
4.219 SNCP_FAIL
4.220 SO_SK_MISMATCH
4.221 SPEED_OVER
4.222 SUBRACK_ID_CONFLICT
4.223 SUBRACK_ID_MISMATCH
4.224 SUBRACK_LOOP
4.225 SUM_INPWR_HI
4.226 SW_SNCP_PS
4.227 SW_SNCP_STA_INDI
4.228 SWDL_ACTIVATED_TIMEOUT
4.229 SWDL_AUTOMATCH_INH
4.230 SWDL_CHGMNG_NOMATCH

4.231 SWDL_COMMIT_FAIL
4.232 SWDL_INPROCESS
4.233 SWDL_NEPKGCHECK
4.234 SWDL_PKG_NOBDSOFT
4.235 SWDL_PKGVER_MM
4.236 SWDL_ROLLBACK_FAIL
4.237 SYN_BAD
4.238 SYNC_C_LOS
4.239 SYNC_DISABLE
4.240 SYNC_F_M_SWITCH
4.241 SYNC_LOCKOFF
4.242 SYNC_FAIL
4.243 SYSPARA_CFDB_NOSAME
4.244 SYSLOG_COMM_FAIL
4.245 T_LOSEX
4.246 T_SLIP
4.247 TEM_HA
4.248 TEM_LA
4.249 TEMP_OVER
4.250 TEST_STATUS
4.251 THUNDERALM
4.252 TIME_LOS
4.253 TIME_NO_TRACE_MODE
4.254 TR_LOC
4.255 TU_AIS_VC3
4.256 TU_LOP_VC3
4.257 VCAT_LOA
4.258 VCAT_LOM_VC3
4.259 VCAT_LOM_VC4
4.260 VOA_ADJUST_FAIL
4.261 VOADATA_MIS
4.262 W_R_FAILURE

4.263 WAVEDATA_MIS
4.264 WAVELEN_OVER
4.265 XC_UNSWITCH

4.1 AD_CHECK_FAIL
Description
The AD_CHECK_FAIL alarm is an alarm indicating AD (analog to digital converter) self check
failure. This alarm is reported when the AD chip on the board is faulty.
Reported from the WDM side or client side: NA.
Attribute
Parameters
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.

l This alarm may affect services.
l Parameters relevant to the AD chip on the board, such as board input/output optical power,
back facet current and cooling current, fail to be queried on the U2000. As a result,
maintenance engineers can neither obtain the current operation performance data of the
network nor find in time any dormant problems of the network operation. The alarm may
interrupt the service in the system or even make the system down. Hence, this alarm should
be handled immediately.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Replace the faulty board. For details, see the Parts Replacement.
----End

Related Information
None
4.2 ALM_ALS
Description
The ALM_ALS alarm in an alarm related to the automatic laser shutdown (ALS) function. When
a board enables the ALS function and the R_LOS alarm is generated at the optical interface, the
laser is shut down automatically. In this case, the board reports the ALM_ALS alarm.
Attribute
Parameters
None

When the ALM_ALS alarm is generated, the system is not affected. This alarm just indicates
that the ALS function of the laser is enabled.
Possible Causes
The ALS function is enabled on the U2000 or the Navigator.
Procedure
Step 1 When the ALS function is disabled, the alarm is cleared automatically.
----End
Related Information
None
4.3 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is manually stopped.

Attribute
Minor Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the MSP group type.
l 0x01: linear MSP group

l 0x02: ring MSP group
Parameter 2, Parameter 3 Indicates the MSP group ID.

The MSP switching protocol of the corresponding MSP group fails to function. Accordingly,
the MSP fails.
Possible Causes
The MSP protocol of the corresponding MSP group is manually stopped.
Procedure
Step 1 View on the U2000 and confirm the MSP subnet where the protocol is stopped.
Step 2 Restart the MSP protocol of the protection group, and the alarm is cleared.
----End
Related Information
None
4.4 ALM_GFP_dCSF

Description
The ALM_GFP_dCSF is an alarm indicating the loss of the GFP client signal. When the source
end cannot receive the client signal, it sends the management frame to the sink end. When the
sink end receives the management frame, this alarm is reported.
Attribute
Parameters
None

During data transmission, the source end cannot receive the client signal. The services lose
packets or are interrupted.
Possible Causes
l The interface module at the source end is faulty. For example, the optical module is absent
or does not match, or the optical/electrical signal is lost.
l The physical link at the source end fails, and it cannot normally receive the physical signal.
Procedure
Step 1 View the ALM_GFP_dCSF alarm on the U2000, and then determine the number of the
VCTRUNK where this alarm is generated.
Step 2 Check whether the physical link at the source end of the VCTRUNK where the uplink service
is configured is normal. For example, check whether the physical link is invalid because the
fiber is damaged. If the fiber is damaged, replace the fiber and then check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the interface module at the source end is normal. If not,
replace the optical module.
Step 4 If the alarm persists, replace the board that reports the alarm.
----End
Related Information
None
4.5 ALM_GFP_dLFD

Description
The ALM_GFP_dLFD is an alarm indicating the loss of generic framing procedure (GFP) frame
delineation. If the alarm is reported when the delimitation state machine of the GFP leaves the
SYNC state of the delimitation processing; the alarm is cleared when the state is SYNC again.
Attribute
Parameters
None

During the data transmission, failure in the GFP framing causes service interruption.
Possible Causes
l Cause 1: There are a large number of bit errors on the link.
Identification method: Query the alarms on the U2000.
l Cause 2: The number of timeslots bound with the VCTRUNK at the local station and the
number of timeslots bound with the VCTRUUNK at the opposite station are not the same
or the number of timeslots bound with the path is not the same as the number of timeslots
configured in the cross-connection.
Identification method: Query the service configuration on the U2000.
l Cause 3: The board is faulty.
Identification method: Use the exclusive method or determine based on experience.
Procedure
l View the ALM_GFP_dLFD alarm on the U2000, and then determine the number of the
VCTRUNK where this alarm is generated. For details, see Querying the Current Alarms
l Cause 1: There are a large number of bit errors on the link.
1. For details, see Querying the Current Alarms and Performance Events of a NE on the
U2000 in the Supporting Task. Check whether any bit error alarm exists on the link.

If... Then...
Any bit error alarm exists Handle the bit error alarms first. The bit error alarms
are as follows:
l B3_EXC
l B3_SD
Check whether the ALM_GFP_dLFD alarm is

cleared. If the alarm persists, see other causes.
No bit error alarm exists See other causes.
l Cause 2: The number of timeslots bound with the VCTRUNK at the local station and the
number of timeslots bound with the VCTRUUNK at the opposite station are not the same
or the number of timeslots bound with the path is not the same as the number of timeslots
configured in the cross-connection.
1. Check whether the number of upstream or downstream timeslots bound with the
VCTRUNK at the local station is consistent with the number of downstream or
upstream timeslots configured at the opposite station.
If ... Then ...
The counts of timeslots are different Increase or decrease the number of bound
paths to ensure consistency of timeslots at
both stations. For details, see the
Configuration Guide. Then, check whether
the alarm is cleared. If the alarm persists,
proceed to the next step.
The counts of timeslots are the same Proceed to the next step.
2. Select the corresponding NE from the Main Topology. Choose Configuration > SDH
Service Configuration from the Function Tree. Check whether the number of
timeslots bound with the path is the same as the number of timeslots configured in the
cross-connection.
If... Then...
The counts are different Reconfigure the bound timeslots or the cross-
connection. Then, check whether the alarm is cleared. If
the alarm persists, see other causes.
The counts are the same See other causes.

1. Check whether the board reports the HARD_BAD alarm.

If... Then...
The HARD_BAD alarm exists The board is faulty. Proceed to the next
step.
The HARD_BAD alarm does not exist After eliminating other causes, proceed
to the next step if the fault persists.
2. Replace the board. For details, see the Parts Replacement.
----End
Related Information
Cell Delimitation State Machine
The cell delimitation state machine has three states: HUNT, PRESYNC, and SYNC. In the
HUNT state, the state machine searches the position of delimiting 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 machines locks the position of delimiting 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.

4.6 ALM_HANGUP
Description
The ALM_HANGUP is an alarm indicating that the orderwire phone is in the off-hook state for
a long time. This alarm is generated when the orderwire phone is in the off-hook state for a long
time.
Attribute
Parameters
None

l The ALM_HANGUP alarm does not affect the services or communication of the NE.
l The ALM_HANGUP alarm indicates that the orderwire phone of the NE is in the off-hook
state for a long time. When the alarm is generated, hang up.
Possible Causes
l The orderwire phone is in the off-hook state for a long time.
l The hardware is faulty.
Procedure
Step 1 Check whether the orderwire phone is hung up. If not, hang up the phone. Then, check whether
the ALM_HANGUP alarm is cleared.
Step 2 If the ALM_HANGUP alarm persists, the board hardware may be faulty. Replace the faulty
----End
Related Information
None
4.7 APS_FAIL

Description
The APS_FAIL is an alarm indicating the APS protection switching failure. This alarm is
generated when the MSP switching fails.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching occurs.

Parameter 2 Indicates the MSP group ID.

When the APS_FAIL alarm is generated, the MSP switching fails. For a linear MSP or a two-
fiber ring MSP, if a fiber cut or another fault occurs at this time, the services are interrupted.
Possible Causes
The possible causes of the APS_FAIL alarm are as follows:
l The MSP configuration parameters are incorrect.

l The MSP configuration is lost.
l The board that reports the alarm is faulty.
Procedure
Step 1 Make sure that the networkwide MSP configuration is correct. For a ring MSP, check the fiber
connections in the east and west directions. For a linear MSP, check the working and protection
fiber connections, or check the MSP switching modes at the two ends. After modifying the
incorrect configuration, check whether the alarm is cleared.
Step 2 Make sure that the networkwide APS protocol works properly. Stop the protocol, and then restart
it to check whether the alarm is cleared.

Step 3 If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For
details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
4.8 APS_INDI
Description
The APS_INDI is an alarm indicating the APS state. This alarm is generated when the MSP is
in the switching state.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching
occurs.


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
The possible causes of the APS_INDI alarm are as follows:

l An external command, including manual switching, forced switching, and exercise

switching, is issued.
l After the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm is generated, the MSP
group changes to the switching state.
l The service board is faulty.
l The cross-connect board is faulty.
Procedure
Step 1 View the APS_INDI alarm on the U2000, and then confirm the type and ID of the protection
group in which this alarm is generated.
Step 2 Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked
switching. If yes, clear the switching and then observe whether the alarm is cleared.
Step 3 To check whether the MSP is in the automatic switching state, do as follows:
1. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm reported by the
equipment. When these alarms are cleared, wait for the MSP switching to be automatically
restored to the normal state, and then check whether the APS_INDI alarm is cleared.
2. Make sure that the service board of the MSP is not faulty. Replace the relevant service
board and then check whether the alarm is cleared.
3. Make sure that the cross-connect board of the MSP is not faulty. Replace the relevant cross-
connect board and then check whether the alarm is cleared.
----End
Related Information
For the 1+1 single-ended non-revertive linear MSP, the APS_INDI alarm is generated when the
protection switching occurs. When the optical path recovers to normal, the service is not
automatically switched back to the working path, and the APS_INDI alarm persists. In this case,
manually switch the service from the protection path to the working path. After successful
manual switching, the APS_INDI alarm is cleared.
4.9 AU_AIS
Description
The AU_AIS is an administrative unit (AU) alarm indication. When the pointer value received
on the receive side of the local optical interface is all "1"s, the AU_AIS alarm is reported.
Attribute

Parameters
None

l When the AU_AIS alarm is reported, the VC-4 level services are interrupted if the network
is not protected.
l In this case, the AU-AIS alarm is reported at the downstream station.
Possible Causes
The possible causes of the AU_AIS alarm are as follows:
l Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm
Identification method: Query the alarms and the loopback on the U2000.
l Board cause 1: The receive board (including the cross-connect and timing board) at the
local end is faulty.
Identification method: Use the exclusive method.
l Board cause 2: The transmit board (including the cross-connect and timing board) at the
opposite end is faulty.
Procedure
l Query current alarms on the U2000. Determine the number of the interface that reports the
alarm according to Parameter 1. For details, see Querying the Current Alarms and
l Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm
1. Check whether any higher-level alarm exists at the upstream station.
If... Then...
The alarms listed in Table 4-1 exist Handle these alarms first. If the AU_AIS
The alarms listed in Table 4-1 do not Proceed to the next step.
exist
2. Perform a loopback at the upstream station to locate the station that reports the
AU_AIS alarm originally. Perform an inloop at the receive and transmit ports at the
opposite board. See the Supporting Task.

NOTICE
The loopback may cause the service interruption.
3. Check whether the AU_AIS alarm exists at the opposite station after the loopback is
performed.
If ... Then ...
The alarm exists The AU_AIS alarm of the local station is transmitted
from the opposite station. Proceed to the next step.
The alarm does not exist See board cause 1.
4. Perform the loopback again to locate the station where the AU_AIS alarm is reported
originally at the opposite upstream station. Check whether any higher-level alarm
exists on board at the service source end corresponding to the station.
If ... Then ...
The alarms listed in Table 4-1 exist Handle these alarms first. If the AU_AIS
alarm is not cleared, see board cause 1.
The alarms listed in Table 4-1 do not See board cause 2.

exist
l Board cause 1: The receive board (including the cross-connect and timing board) of the
local end is faulty.
1. Replace the receive board of the local station. For details, see Parts Replacement.
2. Check whether the alarm is cleared. If the alarm persists, replace the local cross-
connect and timing board. For details, see Parts Replacement.
l Board cause 2: The transmit board (including the cross-connect and timing board) of the
opposite end is faulty.
1. Replace the corresponding transmit board of the station where the AU_AIS alarm is
originally reported. For details, see Parts Replacement.
2. Check whether the alarm is cleared. If the alarm persists, replace the cross-connect
and timing board. For details, see Parts Replacement.
----End
Related Information
Table 4-1 Alarms that may cause the AU_AIS alarm
R_LOS R_LOF R_OOF

MS_AIS B1_EXC B1_SD
B2_EXC B2_SD AU_LOP
B3_EXC B3_SD HP_TIM
HP_LOM HP_SLM HP_UNEQ
4.10 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 level.
l Cause 3: Boards on the local NE are faulty.
l Cause 4: Boards 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 level.
1. Check whether the services transmitted by the peer NE and received by local NE are
consistent in the service level.
If... Then...
Services transmitted by the peer NE and Reconfigure the service level on the local
received by local NE are inconsistent in and peer NEs and check whether the
the service level 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 level
Step 3 Cause 3: Boards on the local NE are faulty.

1. Cold reset the local receive board on the NMS or directly remove and insert this board.
NOTICE
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.
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: Boards on the peer NE are faulty.

1. Cold reset the peer transmit board on the NMS or directly remove and insert this board.
NOTICE
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
board.

3. 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.
4.11 B1_SD
SF64, SF64A, SFD64, SL64, SLD64, 4.11.1 B1_SD(OCS)

Boards other than the SF64, SF64A, SFD64, 4.11.2 B1_SD(OTN)

SLO16, or EGSH
4.11.1 B1_SD(OCS)
Description
The B1_SD is an alarm indicating that regenerator section B1 signals received on the line are
degraded. When a line board detects that the bit errors of the regenerator section signals exceed
the B1_SD alarm threshold but are lower than the B1_EXC alarm threshold, the B1_SD alarm
is reported.
Attribute
Minor Service alarm
Parameters
None

When the B1_SD alarm is reported, the quality of the transmitted services is degraded.

Possible Causes
The possible causes of the B1_SD alarm are as follows:

Procedure
Task.
NOTE
If... Then...

abnormal,
If... Then...

If... Then...

Cleaners
Tissue
Sticks

If... Then ...


proper,
temperature.
Task.

NOTICE
If... Then...
step.
Replacement.
Replacement.
----End
Related Information
None.
4.11.2 B1_SD(OTN)
Description
The B1_SD(OTN) alarm is an alarm indicating that the regenerator section signals are degraded.
The alarm occurs when the received signals in SDH frame degrade and the B1 bit errors in the
multiplex section exceed the signal degrade (SD) threshold.
l The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received
on the WDM side exceed the signal degrade threshold.
l The alarm is generated on the client side when the B1 bit errors in the SDH signals received
on the client side exceed the signal degrade threshold.
Attribute
Minor Service alarm

Parameters
None

The B1 bit errors in the service signals received by the board exceed the degrade threshold of
signals set on the board. The generation of the alarm has an impact on the QoS of the service
signals.
Possible Causes
l The attenuation of the received signals is overlarge; the fiber or connector is dirty.
l The transmit part of the opposite station is faulty.
l The receive part of the local station is faulty.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using
the U2000. For optical power specifications of specific boards, see the Product Description. If
the receive optical power of the board at the local station is excessively low, clear the alarm
according to the handling procedure of the IN_PWR_LOW alarm.
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding interface
on the upstream board is within the normal range by using the U2000. For theoptical power
specifications of specific boards, see the Product Description. If the transmit optical power of
the board at the upstream station is excessively low, clear the alarm according to the handling
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station by using
the U2000 and loop back the transmit optical interface and receive optical interface on the
WDM side of the OTU board at the upstream station. If bit errors exist, clear the bit error fault
of the upstream station.
Step 4 If the alarm persists and the faulty board supports the pluggable optical module, replace the
pluggable optical module. For details, see the Parts Replacement.
Step 5 If the alarm persists, replace the faulty board at the local station. For details, see the Parts
Replacement.
Step 6 If the alarm bursts, it may be caused by the transmission line influenced by various noise sources.
Search the jam source that may cause the burst bit errors and remove the interference.
----End
Related Information
None
4.12 B2_EXC

Description
The B2_EXC is an alarm indicating that the number of multiplex section B2 bit errors in the
signals received on the line exceed the specified value. When a line board detects that the bit
errors of the multiplex section signals exceed the threshold for the B2_EXC alarm by detecting
the B2 byte, the B2_EXC alarm is reported.
Attribute
Major Service alarm
Parameters
None

l When the B2_EXC alarm is generated, the quality of the transmitted services is degraded.
l When the B2_EXC alarm is reported, the system returns the M1 byte to the opposite end,
indicating the MS_REI alarm. Consequently, the opposite station reports the MS_REI
alarm.
Possible Causes

Procedure
Task.
NOTE

If... Then...

abnormal,
If... Then...
If... Then...

Cleaners
Tissue
Sticks

If... Then ...


If... Then ...

proper,
temperature.
Task.
NOTICE
If... Then...
step.
Replacement.
Replacement.
----End
Related Information
None.

4.13 B2_SD
Description
The B2_SD is an alarm indicating that multiplex section B2 signals received on the line are
degraded. When a line board detects that the bit errors of the multiplex section signals exceed
the B2_SD alarm threshold but are lower than the B2_EXC alarm threshold, the B2_SD alarm
is reported.
Attribute
Minor Service alarm
Parameters
None

l When the B2_SD alarm is reported, the quality of the transmitted services is degraded.
l When the B2_SD alarm is reported, the system may return the M1 byte to the opposite end,
indicating the MS_REI alarm. Consequently, the remote station may report the MS_REI
alarm.
Possible Causes

Procedure
Task.

NOTE
If... Then...

abnormal,
If... Then...
If... Then...

Cleaners
Tissue
Sticks


If... Then ...


proper,
temperature.
l Cause 3: The setting of the bit error threshold is improper.
1. Query the bit error threshold of the board that reports the alarm. According to the
situation, increase the B2 error threshold. For operations, see the Supporting Task.
2. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
Task.
NOTICE
If... Then...
step.
Replacement.

Replacement.
----End
Related Information
None.
4.14 B3_EXC
Description
The B3_EXC is an alarm indicating that the number of higher order path B3 bit errors in the
signals received on the line exceeds the threshold. When a line board detects that the bit errors
of the higher order path signals exceed the specified threshold by detecting the B3 byte, the
B3_EXC alarm is reported.
Attribute
Major Service alarm
Parameters
None

l When the B3_EXC alarm is reported, bit errors occur in the path-level services.
l When the B3_EXC alarm is reported, the system returns the G1 byte to the opposite end,
indicating the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm.
If the AU_AIS alarm is inserted when the B3_EXC alarm is reported, the system returns
the G1 byte to the opposite end, indicating the HP_RDI alarm. Consequently, the remote
station generates the HP_RDI alarm.
Possible Causes


Procedure
alarm. For details, see Querying the Current Alarms and Performance Events of a NE on
the U2000 in the Supporting Task.
Task.
NOTE
If... Then...

abnormal,
If... Then...

If... Then...

Cleaners
Tissue
Sticks

If... Then ...


proper,
temperature.
Task.

NOTICE
If... Then...
step.
Replacement.
Replacement.
----End
Related Information
None.
4.15 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the number of B3 bit errors in the lower order
path VC-3 exceeds the threshold. If a board has detected that the number of B3 bit errors exceeds
the specified threshold value, the B3_EXC_VC3 alarm is reported.
Attribute
Major Service alarm
Parameters
None


When the B3_EXC_VC3 alarm is generated, a great number of bit errors occur in the VC-3
service.
Possible Causes
The possible causes of the B3_EXC_VC3 alarm are as follows:
l A higher-level bit error alarm is generated in the system.
l The received signals are heavily attenuated.
l The fiber connector is dirty.
l The fiber connector is loose.
l The transmit unit at the opposite station is faulty.
l The receive unit at the local station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD, is detected at the local station or at the upstream station. If yes, take priority
to clear it, and then check whether the B3_EXC_VC3 alarm is cleared.
Step 2 If the alarm persists, check whether the receive optical power of the board that reports the alarm
is within the normal range.
l If yes, go to Step 3.
l If not, take the following steps:
1. Insert the fiber connector firmly, and then check whether the alarm is cleared.
2. Check whether the attenuation value specified in the fiber attenuator is proper. If not, adjust
it to a proper value, and then check whether the alarm is cleared.
3. Clean the fiber connector at the local station and the receive optical interface on the line
board, and then check whether the alarm is cleared.
4. Check whether the flange is correctly connected to the optical attenuator at the local station,
and whether the attenuation value specified in the optical attenuator is proper. After making
sure that the flange and optical attenuator are used properly, check whether the alarm is
cleared.
5. Check whether the transmit optical power at the opposite station is within the normal range.
6. If the transmit optical power is beyond the specified range, replace the optical module, and
then check whether the alarm is cleared. If not, replace the line board at the opposite end,
and then check whether the alarm is cleared.
7. If the transmit optical power is within the normal range, clean the fiber connector at the
remote station, and then check whether the alarm is cleared.
8. Check whether the flange is correctly connected to the optical attenuator at the opposite
station, and whether the attenuation value specified in the optical attenuator is proper. After
making sure that the flange and optical attenuator are used properly, check whether the
alarm is cleared.
Step 3 If the alarm persists, replace the board that generates the B3_EXC_VC3 alarm.
----End

Related Information
None
4.16 B3_EXC_VC4
Description
The B3_EXC_VC4 is an alarm indicating that the number of B3 bit errors in the VC-4 path
exceeds the threshold. If a board has detected that the number of B3 bit errors in the VC-4 path
exceeds the specified threshold value, the B3_EXC_VC4 alarm is reported.
Attribute
Major Service alarm
Parameters
None

When the B3_EXC_VC4 alarm occurs, bit errors occur in the path-level services.
Possible Causes
The possible causes of the B3_EXC_VC4 alarm may be the same as those of the B3_EXC alarm.
Procedure
Step 1 See the procedure for handling the B3_EXC alarm.
----End
4.17 B3_SD
Description
The B3_SD is an alarm indicating that the higher order path B3 signals received on the line are
degraded. When a line board detects that the bit errors of the higher order path signals exceed
the specified B3_SD alarm threshold but are lower than the specified B3_EXC alarm threshold
by detecting the B3 byte, the B3_SD alarm is reported.

Attribute
Minor Service alarm
Parameters
None

l When the B3_SD alarm is reported, bit errors occur in the path-level services.
l When the B3_SD alarm is reported, the system returns the G1 byte to the opposite end,
indicating the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm.
If the AU_AIS alarm is inserted when the B3_SD alarm is reported, the system returns the
G1 byte to the opposite station, indicating the HP_RDI alarm. Consequently, the opposite
station generates the HP_RDI alarm.
Possible Causes

Procedure
Task.
NOTE

If... Then...

abnormal,
If... Then...
If... Then...

Cleaners
Tissue
Sticks

If... Then ...


If... Then ...

proper,
temperature.
Task.
NOTICE
If... Then...
step.
Replacement.
Replacement.
----End
Related Information
None.

4.18 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the number of VC-3 B3 bit errors exceeds the
threshold. If a board has detected that the number of VC-3 B3 bit errors exceeds the specified
B3_SD alarm threshold value, the B3_SD_VC3 alarm is reported.
Attribute
Minor Service alarm
Parameters
None

When the B3_SD_VC3 alarm is generated, the service transmission quality in the VC-3 service
channel is degraded.
Possible Causes
The possible causes of the B3_SD_VC3 alarm are as follows:
l Higher-level bit alarms occur in the system.

l The fiber connector is loose.
l The receive unit at the opposite station is faulty.
l The transmit unit at the local station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD alarm, is detected at the local station or at the upstream station. If yes, take
priority to clear it, and then check whether the B3_SD_VC3 alarm is cleared.
Step 2 If the alarm persists, check whether the receive optical power of the board that report the alarm
is within the normal range.
l If yes, go to Step 3.
l If not, take the following steps:
1. Insert the fiber connector firmly, and then check whether the alarm is cleared.

2. Check whether the attenuation value specified in the fiber attenuator is proper. If not, adjust
it to a proper value, and then check whether the alarm is cleared.
3. Clean the fiber connector at the local station and the receive optical interface on the line
board, and then check whether the alarm is cleared.
4. Check whether the flange is correctly connected to the optical attenuator at the local station,
and whether the attenuation value specified in the optical attenuator is proper. After making
sure that the flange and optical attenuator are used properly, check whether the alarm is
cleared.
5. Check whether the transmit optical power at the opposite station is within the normal range.
6. If the transmit optical power is beyond the specified range, replace the optical module, and
then check whether the alarm is cleared. If not, replace the line board at the opposite end,
7. If the transmit optical power is within the normal range, clean the fiber connector at the
opposite station, and then check whether the alarm is cleared.
8. Check whether the flange is correctly connected to the optical attenuator at the opposite
station, and whether the attenuation value specified in the optical attenuator is proper. After
making sure that the flange and optical attenuator are used properly, check whether the
alarm is cleared.
Step 3 If the alarm persists, replace the board that generates the B3_SD_VC3 alarm.
----End
Related Information
None
4.19 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that the number of B3 bit errors in the VC-4 path exceeds
the threshold. If a board has detected that the number of B3 bit errors in the VC-4 path exceeds
the specified threshold value, the B3_SD_VC4 alarm is reported.
Attribute
Minor Service alarm
Parameters
None

When the B3_SD_VC4 alarm is generated, bit errors occur in the path-level services.

Possible Causes
The possible causes of the B3_SD_VC4 alarm may be the same as those of the B3_SD alarm.
Procedure
Step 1 See the procedure for handling the B3_SD alarm.
----End
4.20 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED alarm is an alarm indicating that the logic board is not installed.
This alarm occurs when the slot is installed with a physical board but is not configured with a
logic board.
Attribute
Parameters
None

If a board not configured is not used, this alarm can be ignored. If a board not configured is used,
services on this board are not available.
Possible Causes
The logic board is not configured.
Procedure
Step 1 On the U2000, add a logic board that corresponds to the slot that reports the alarm.
----End
Related Information
None

4.21 BD_STATUS
SF64, SF64A, SFD64, SL64, SLD64, 4.21.1 BD_STATUS(OCS)

Boards other than the SF64, SF64A, SFD64, 4.21.2 BD_STATUS(OTN)

SLO16, or EGSH
4.21.1 BD_STATUS(OCS)
Description
The BD_STATUS is an alarm indicating that the physical board is offline. This alarm is reported
when the logical board is created on the U2000 but the physical board is not inserted in the
subrack.
Attribute
Parameters
None

Because the physical board is not inserted in the equipment, the data that is configured on the
NE cannot be delivered to this board. Hence, configuration of services fails.
Possible Causes
The possible causes of the BD_STATUS alarm are as follows:
l Cause 1: The board is in the cold reset or warm reset state.

l Cause 2: The board is not inserted in the corresponding slot or the board does not contact
the backplane firmly.

l Cause 3: The pins of the backplane are bent or the board is faulty.
Procedure
l Query current alarms on the U2000. Then find the boards that report the alarm. For details,
see Querying the Current Alarms and Performance Events of a NE on the U2000 in the
Supporting Task.
l Cause 1: The board status is cold reset or warm reset.
1. Check the board alarm indicator to see whether the status of the board that reports the
alarm is cold reset or warm reset. Wait for five minutes if the board is in the cold reset
or warm reset state, and then check whether the alarm is cleared. For the description
of the alarm indicators on the board, see Board Indicators in the Hardware
Description.
l Cause 2: The board is not inserted in the corresponding slot or the contact part of the board
with the backplane is loose.
1. Check whether the board is inserted in the corresponding slot. If not, insert the
corresponding physical board. For details, see "Removing Boards" and "Inserting
Boards" in the Quick Installation Guide.
2. Check whether the board is connected to the backplane properly and whether the board
is connected properly. If the board is loose, reseat the board. For operations, see
"Removing Boards" and "Inserting Boards" in the Quick Installation Guide. Then,
check whether the alarm is cleared.
l Cause 3: The pins of the backplane are bent or the board is faulty.
1. Remove the board that reports the alarm. For details, see "Removing Boards" in the
Quick Installation Guide. Check whether any pins of the backplane are bent. If any
bins are bent, contact Huawei engineers for fixing the pins. After the pins are fixed,
insert the board. For details, see "Inserting Boards" in the Quick Installation Guide.
2. If the alarm persists, replace the board that reports the alarm. For details, see the Parts
----End
Related Information
None.
4.21.2 BD_STATUS(OTN)
Description
The BD_STATUS is an alarm indicating that the board is out of position. This alarm is reported
when the logical board is created on the U2000 but the physical board is not inserted in the slot.

Attribute
Parameters
None

The board is not in position. Hence, the functions related to the board are unavailable.
Possible Causes
l The logic board is configured but the physical board has not been inserted in the proper
slot.
l The connection between the plug of the board and the socket of the backplane is loose.
l The board is faulty.
l The backplane is faulty.
Procedure
Step 1 Check whether the corresponding board is inserted in the physical slot.
l If no corresponding board is inserted, insert the board.
l If the corresponding board is inserted, check whether the insertion is firm. If not, reset the
board.
Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
Step 3 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei
engineers.
----End
Related Information
None
4.22 BDID_ERROR
Description
The BDID_ERROR is an alarm indicating slot verification error. This alarm is generated when
the board parity check fails or when the board is not properly secured in its slot.

Attribute
Parameters
None

l When the BDID_ERROR alarm is generated, the board may fail to get online and as a result
the services are interrupted.
l In this case, you cannot configure and monitor the services for the board.
Possible Causes
The possible causes of the BDID_ERROR alarm are as follows:
l The board is not properly secured in the slot.

l The board hardware fails.
l Pins on the backplane are bent.
Procedure
Step 1 View the BDID_ERROR alarm on the U2000 to determine the relevant board.
Step 2 Remove the board to check whether there are any bent pins on the backplane. If any pins are
bent, fix them and then insert the board. Check whether the alarm is cleared.
Step 3 If the alarm persists, replace the board.
----End
Related Information
None
4.23 BEFFEC_SD
Description
The BEFFEC_SD is an alarm indicating that the signals are degraded before the FEC. Signals
from WDM side of the opposite OTU have the FEC function. As a result, before performing the
FEC in the receive direction of WDM side of the local OTU, the local OTU calculates the bit
error rate. This alarm occurs when the calculated bit error rate crosses the threshold.

Attribute
Minor Service alarm
Parameters
None

The system redundancy decreases, which affects the quality of signals if the decrease is serious.
Possible Causes
l The board input optical power is excessively high or low.
l The system performance is degraded. For example, the optical signal to noise ratio (OSNR)
is excessively low, or dispersion or non-linearity occurs.
l The opposite board is faulty.
l The local board is faulty.
Procedure
Step 1 On the U2000, check whether the input optical power of the optical interface is within the normal
range. For optical power specifications of the boards, see the Product Description. If the input
optical power is abnormal, see the methods for handling the IN_PWR_HIGH and
IN_PWR_LOW alarms.
Step 2 If the alarm persists, see the description on handling of bit error faults in the Troubleshooting.
Step 3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For
details, see the Parts Replacement.
Step 4 If the alarm persists, the board at the opposite station may be faulty. Replace the faulty board.
For details, see the Parts Replacement.
----End
Related Information
None
4.24 BIOS_STATUS
Description
The BIOS_STATUS is an alarm indicating the BIOS status. By default, if loading of the board
software fails for three consecutive times within five minutes, the board enters the BIOS status
and the BIOS_STATUS alarm is reported.

Attribute
Major Environment alarm
Parameters
None

When an anomaly occurs on the board software or hardware, the BIOS_STATUS alarm is
generated and related services are interrupted.
Possible Causes
The possible causes of the BIOS_STATUS alarm are as follows:
l The software is lost.

l Incorrect software is loaded.
l Writing or reading the software becomes abnormal.
l The board hardware is faulty.
Procedure
Step 1 View the BIOS_STATUS alarm on the U2000, and then determine the board where the
BIOS_STATUS alarm is generated.
Step 2 Perform warm reset on the board and then check whether the BIOS_STATUS alarm is cleared.
Step 3 If the BIOS_STATUS alarm persists, perform cold reset on the board. Then check whether the
BIOS_STATUS alarm is cleared.
Step 4 If the BIOS_STATUS alarm persists, contact Huawei technical support engineers and ask them
to replace the board software. After the board software is replaced, check whether the
BIOS_STATUS alarm is cleared.
Step 5 If the alarm persists, replace the board and check whether the BIOS_STATUS alarm is cleared.
----End
Related Information
None
4.25 BOOTROM_BAD

SF64, SF64A, SFD64, SL64, SLD64, 4.25.1 BOOTROM_BAD(OCS)

Boards other than the SF64, SF64A, SFD64, 4.25.2 BOOTROM_BAD(OTN)

SLO16, or EGSH
4.25.1 BOOTROM_BAD(OCS)
Description
The BOOTROM_BAD is an alarm indicating the BOOTROM data check failure. During the
running of board software, the system periodically checks whether the BOOTROM data is
damaged. This alarm is generated when the BOOTROM data is detected damaged.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the BIOS damage.
l 0x01: basic BIOS damaged

l 0x02: extended BIOS damaged

l If the board has been started, the BOOTROM_BAD alarm does not affect the system or
the services.
l If you perform cold reset on the board when there is the BOOTROM_BAD alarm, the board
fails to load BIOS and cannot be started.

Possible Causes
The possible causes of the BOOTROM_BAD alarm are as follows:
l The basic BIOS is damaged.

l The extended BIOS is damaged.
l The BOOTROM data area is damaged.
Procedure
Step 1 View the BOOTROM_BAD alarm on the U2000 and determine the relevant board.
Step 2 Replace the board. If the board has been started, do not replace the board. Replacing the board
can interrupt services, whereas the BOOTROM_BAD alarm does not affect the system or the
services.
----End
Related Information
None
4.25.2 BOOTROM_BAD(OTN)
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data check fails. This alarm
occurs when the basic or extended BIOS software of the board is damaged.
Attribute
Parameters
Parameters 1 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software.
0x02 indicates the extended BIOS software.


When powered on again or reset after a power supply failure, the SCC board cannot be normally
started.
Possible Causes
l The extended BIOS software of the board is damaged.
l The basic BIOS software of the board is damaged.
l The SCC board is faulty.
Procedure
Step 1 Determine upon the alarm parameter (0x01 indicates the basic BIOS while 0x02 the extended
BIOS) whether the basic or extended BIOS software of the board is damaged.
Step 2 If the basic BIOS software is faulty, replace the faulty SCC board. For details, see the Parts
Replacement.
Step 3 If the extended BIOS software is damaged, reload the extended BIOS of the SCC board. For
details, see the Upgrade Guide.
Step 4 If the alarm persists, the SCC board may be faulty. Replace the faulty board. For details, see the
Parts Replacement.
----End
Related Information
None
4.26 C2_VCAIS
Description
The C2_VCAIS is a C2 byte alarm indication. If a board has detected that the value of the
received C2 byte is all "1"s, the C2_VCAIS alarm is reported.
Attribute
Minor Service alarm
Parameters
None


The services are interrupted.
Possible Causes
The value of the C2 byte to be transmitted is incorrectly configured at the remote end.
Procedure
Step 1 View the C2_VCAIS alarm on the U2000. Determine the VC path that reports the alarm.
Step 2 Check whether the value of the C2 byte to be transmitted is correctly configured at the remote
end. If not, modify it, and then check whether the C2_VCAIS alarm is cleared.
Step 3 If the alarm persists, replace the transmit board at the remote end. For details, see the Parts
Replacement.
----End
Related Information
None
4.27 CHAN_ADD
Description
The CHAN_ADD is an alarm indicating that wavelengths are added to a single-wavelength
signal. The alarm occurs when the MCA (optical spectrum analyzing) board detects that new
wavelengths are added after it scans the optical spectrum.
Attribute
Parameters
None

The MCA cannot monitor the optical spectrum performance of the wavelength related to the
alarm.

Possible Causes
l The configuration for wavelength monitoring is incorrect. The accessed wavelength is not
set as the monitored wavelength.
l The MCA board is faulty.
Procedure
Step 1 Check whether the configuration for wavelength monitoring of the MCA board is incorrect by
using the U2000. If the configuration is incorrect, modify the configuration to ensure that the
monitored wavelength and the number of the monitored wavelengths are consistent with the
accessed wavelength and the number of accessed wavelengths.
Step 2 If the alarm persists, test the optical spectrum data of the input optical signals by using the optical
spectrum analyzer. If the data is normal, the optical spectrum analyzing module may be faulty.
Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.28 CHIP_ABN
Description
The CHIP_ABN is an alarm indicating temperature chip failure. This alarm is generated when
the temperature chip fails.
Attribute
Parameters
None

When the CHIP_ABN alarm is generated, the board temperature cannot be correctly detected.
Possible Causes
The temperature chip on the board fails.

Procedure
Step 1 Check whether the equipment has another cross-connect board that is functioning properly. If
yes, perform cold reset on the board that reports the CHIP_ABN alarm. After successful cold
reset, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
4.29 CLIENT_PORT_STA_INDI
Description
The CLIENT_PORT_STA_INDI alarm indicates the state of the client side 1+1 optical channel
protection group. This alarm is reported when the working or protection channel of the protection
group is faulty or the user runs an external switching command.
Attribute
Parameters
Parameters 1 Indicate the switch request status. For example:

l 0x0F: Lockout
l 0x0E: Forced Switch
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x07: Manual Switch
l 0x05: WTR


l When switching of the client-side 1+1 protection group occurs, services are transiently
interrupted.
l When this alarm is reported, the working channel or the protection channel of the client-
side 1+1 protection group might have faulty services that need to be restored.
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching, manual
switching or locked switching.
l Cause 2: The services of the working channel or the protection channel of the client-side
1+1 protection group are faulty.
l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
is forced switching, manual switching or locked switching, check whether the external
switching operation is necessary.
3. If the external switching operation is unnecessary, issue a command to clear the
external switching.
l Cause 2: The services of the working channel or protection channel of the client-side 1+1
protection group are faulty.
1. Query whether the boards that are configured with the working channel or protection
channel of the protection group have the alarms, such as R_LOF, R_LOS, R_LOC,
HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM,
ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_TIM,
REM_SF, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC or REM_SD. If
yes, handle the alarms by referring to the corresponding alarm handling procedures.
Revertive or not. If the attribute is Revertive, the working channel of the current
service automatically switches to the working channel and then the alarm clears. If
the attribute is Non-Revertive, set it to Revertive and the alarm clears.
1. There is no need to handle this alarm. After WTR Times (s), the alarm clears.
----End
Related Information
None

4.30 CLIENT_PROT_NOTSTART
Description
The CLIENT_PROT_NOTSTART is an alarm indicating that the client-side 1+1 protection
group is not started. This alarm occurs when the client-side 1+1 protection group is disabled
because the configurations on the both sides of the active and standby channels of the protection
group do not meet the requirements of enabling the protection group.
Attribute
Parameters
None

The client-side 1+1 protection group does not perform the switching in case of a service fault.
In this case, the protection fails.
Possible Causes
l The active or standby channel is configured with an incorrect electrical-layer cross-
connection.
l The active or standby channel is not configured with complete electrical-layer services
between WDM-side ports and client-side ports.
l The active or standby channel is configured with an EVPL link that converges at a client-
side optical interface.
Procedure
Step 1 Query on the U2000 whether the active or standby channel is configured with an incorrect
electrical-layer cross-connection such as a cross-connection with an IP port as the source and
another IP port as the sink. If yes, delete the incorrect electrical-layer cross-connection.
Step 2 If the alarm persists, check the OTU that can be configured with electrical-layer cross-
connections. If the active or standby channel of this OTU is not configured with complete
electrical-layer services between WDM-side ports and client-side ports, configure the complete
electrical-layer services.
Step 3 If the alarm persists, check whether the active or standby channel is configured with an EVPL
link that converges in the downlink. If yes, change this EVPL link to an EPL link or an EVPL
link that broadcasts in the downstream.
----End

Related Information
None
4.31 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE is an alarm indicating that the clock enters the non-tracing
mode. This alarm is generated when the current clock does not trace any line clock source,
tributary clock source, or external clock source.
Attribute
Parameters
None

When the CLK_NO_TRACE_MODE alarm is generated, the clock is in the non-tracing mode.
In this case, the system clock is of a low quality. When the low quality clock results in the out-
of-synchronization status among NEs, the bit error rate of services increases.
Possible Causes
The possible causes of the CLK_NO_TRACE_MODE alarm are as follows:
l Cause 1: A priority table is not manually set for the system, and NEs use their own default
priority tables.
l Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.
Procedure
l Cause 1: A priority table is not manually set for the system, and NEs use their own default
priority tables.
1. Query the current priority table of the system. If there is only the internal clock source
in the priority table, set the clock source priority table to include other available clock
sources. After the setting, the alarm is automatically cleared. For details, see
Configuring the System Clock Source Priority Table in the Feature Description.
l Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.

1. In the current priority table, if the internal clock source is not the only available source,
find out why other clock sources cannot be traced. Common causes are as follows:
– The existence status of the clock source is lost. In this case, the system generates
the SYNC_C_LOS alarm. After the SYNC_C_LOS alarm is cleared, the system
clock traces any clock source other than the internal clock source, and then check
whether the CLK_NO_TRACE_MODE alarm is cleared.
– The synchronous source is degraded. In this case, the system generates the
SYN_BAD alarm. After the SYN_BAD alarm is cleared, the system clock traces
any clock source other than the internal clock source, and then check whether the
CLK_NO_TRACE_MODE alarm is cleared.
– The local station enables the SSM protocol, while the upstream station does not
enable the SSM protocol. In this case, enable the SSM protocol at the upstream
station. When the system clock traces any clock source other than the internal clock
source, the CLK_NO_TRACE_MODE alarm is automatically cleared. For details,
see Configuring the Clock Source Protection in the Feature Description.
----End
Related Information
None
4.32 CODE_SYNC_LOS
Description
The CODE_SYNC_LOS is an alarm indicating loss of synchronization. When loss of
synchronization occurs in the received signals of the equipment during signal coding, the
equipment stops receiving data and the CODE_SYNC_LOS alarm is reported.
Attribute
Critical Service alarm
Parameters
None

Possible Causes
l The type or the rate of the signals at the opposite station is not consistent with the type or
rate of the signals at the local station.

l The link is faulty.

l The opposite equipment is faulty.
Procedure
Step 1 Check whether the type and rate of the signals at the opposite station are consistent with the type
and rate of the signals at the local station. If not, modify the service configuration at the local
station.
Step 2 If the alarm persists, check the cables and fibers between the opposite station and location station
to ensure that they are connected properly.
Step 3 If the alarm persists, it is possible that the opposite station is faulty. In this case, troubleshoot
the equipment.
----End
Related Information
None
4.33 CRC4_CROSSTR
Description
The CRC4_CROSSTR is an alarm indicating that the count of CRC4 multi-frame errors crosses
the threshold. The alarm occurs when the number of the bit errors in the CRC4 multiframe
Attribute
Minor Service alarm
Parameters
None

The alarm has an influence on the services (supervisory channel such as the orderwire signal).
Possible Causes
l The configuration of the system clock is incorrect.
l The attenuation of the transmission line is overlarge.

l The receive optical power is overloaded.
Procedure
Step 1 Check the clock configuration of the system on the U2000 to ensure that the configuration is
correct. For details, see the Configuration Guide.
Step 2 Check whether the input optical power of the interface of the board at the local station is within
the normal range by using the U2000. For optical power specifications of the specific boards,
see the Product Description. If the optical power is abnormal, take the processing methods of
alarms such as IN_PWR_HIGH or IN_PWR_LOW for troubleshooting.
Step 3 If the services are not influenced, check whether the fiber jumper between the FIU board and
the SC2/SC1 board is extruded. If the fiber jumper is extruded, clean up the routed fiber jumper.
If the fiber jumper is transformed due to the extrusion, replace the fiber jumper.
----End
Related Information
None
4.34 DB_RESTORE_FAIL
Description
The DB_RESTORE_FAIL is an alarm indicating a database restore failure. This alarm occurs
when the database recovery fails.
Attribute
Major Process Alarm
Parameters
Parameters 1 0x01, indicating that the OCP database fails to recover

The configured data cannot be saved successfully. As a result, the data is lost.

Possible Causes
l The database configuration file is lost.
l Data in the database is damaged.
Procedure
Step 1 Back up the database regularly at a fixed time to solve this problem. Check and test the database
in the backup area to ensure that the data in database is complete.
----End
Related Information
None
4.35 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a database error. The alarm occurs when the database
is in error
Attribute
Major Process alarm
Parameters
Parameter 1 Indicates the alarm type. The value is the error code that causes the
DBMS_ERROR alarm.
Parameter 2 Indicates the memory areas in the database:
0x00 indicates FDB0.
0x01 indicates FDB1.
0x02 indicates DRDB.

Parameter 3 Indicates the ID of the database that has errors. Currently, the value can only be
0-255 (0x00-0xFF).
0x00 indicates that the entire storage area mistakes in error.
0x01-0xff indicates that the database is in error.

The configured data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l Operation to database fails.
l Data in the database is damaged.
Procedure
Step 1 Solve the problem by periodically backing up the database. Check and test the database in the
backup area to ensure that the data in database is complete.
----End
Related Information
None
4.36 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the database is in the protection
mode. The alarm occurs when the NE database is in the protection mode.
Attribute
Critical Process alarm
Parameters
None


In the protection mode, the NE database cannot be backed up.
Possible Causes
l The reset times of the SCC in five minutes cross the threshold value of the protection mode.
l The SCC issues a command to test the protection mode.
Procedure
Step 1 Check whether the NE database in the protection mode is caused by human factors. If that is the
case,
l Perform warm or cold reset on the SCC through the U2000. Release the protection mode.
For details, see the Supporting Tasks.
l Wait for 15 minutes. Release the protection mode after the automatic reset.
----End
Related Information
None
4.37 DCM_INSUFF
Description
The DCM_INSUFF is an alarm indicating the insufficient dispersion compensation margin. The
alarm is generated when the dispersion compensation value gets close to the limit of the
dispersion compensation margin
Attribute
Parameters

Parameter 1 The value of Parameter 1 is always 0xff.
Parameter 2 Indicates the positive or negative dispersion compensation margin. The value
0x00 indicates the positive dispersion compensation margin, and the value 0x01
indicates the negative dispersion compensation margin.

The alarm does not affect the existing services. The alarm indicates that the system cannot meet
the higher dispersion compensation requirements.
Possible Causes
The configuration of the DCM module is not correct or the DCM module is faulty.
Procedure
Step 1 Check whether there is the OTUk_LOF alarm on the U2000. If there is the OTUk_LOF alarm,
clear the alarm according to the proper procedure.
Step 2 If there are no other alarms, query the dispersion compensation value of the board on the
U2000.
l If the dispersion compensation value is large and close to the upper limit of the dispersion
compensation margin, replace the DCM module with a DCM module with lower dispersion
compensation capabilities.
l If the dispersion compensation value is small and close to the lower limit of the dispersion
compensation margin, replace the DCM module with a DCM module with higher dispersion
compensation capabilities.
----End
Related Information
None
4.38 DLAG_PROTECT_FAIL
Description
The DLAG_PROTECT_FAIL is an alarm indicating that the DLAG protection fails. If
negotiation fails or any anomaly occurs during the DLAG protection, the
DLAG_PROTECT_FAIL alarm is reported.

Attribute
Major Processing alarm
Parameters
Name Meaning
Parameters 1 and 2 Indicates the ID of the aggregation group.
Parameter 3 Indicates the cause of the DLAG protection failure.
l 0x01: Both the active and the standby links fail.

l 0x02: The active and standby ports fail to receive the LACP packets.
l 0x03: The opposite equipment does not enter the LACP
synchronization status.
l 0x04: The active or standby port detects the self-loop. Alternatively,
the active or standby port may form a loop with other ports on the
board.
l 0x05: The communication between the active and standby boards
times out.
l 0x06: The communication between the board and the cross-connect
board times out.
l 0x07: The active port selected by LACP is inconsistent with the one
selected by cross-connect board.

When all the DLAG ports fail, or when the board fails to normally communicate with other
boards, the DLAG_PROTECT_FAIL alarm is reported. In the case of the
DLAG_PROTECT_FAIL alarm, services cannot be received or transmitted in the LAG, or the
user cannot check whether services are in the normal state.
Possible Causes
The possible causes of the DLAG_PROTECT_FAIL alarm are as follows:
l Both the active and standby links fail.

l The active and standby ports fail to receive the LACP packets.
l The opposite equipment does not enter the LACP synchronization status.

l The active or standby port detects the self-loop. Alternatively, the active or standby port
may form a loop with other ports on the board.
l The communication between the active and standby boards times out.
l The communication between the board and the cross-connect board or SCC board times
out.
l The active port selected by LACP is inconsistent with the one selected by cross-connect
board.
Procedure
Step 1 View the DLAG_PROTECT_FAIL alarm on the U2000, and determine the board where the
DLAG_PROTECT_FAIL alarm is generated. Determine the ID of the LAG where the
DLAG_PROTECT_FAIL alarm is generated according to Parameters 1 and 2, and determine
the cause of the DLAG_PROTECT_FAIL alarm at the port according to Parameter 3.
Step 2 If the value of Parameter 3 is 0x01, it indicates that the link becomes faulty or fails.
1. On the U2000, check whether the port in the LAG is enabled. If not, enable the port and
then check whether the DLAG_PROTECT_FAIL alarm is cleared.
2. If the DLAG_PROTECT_FAIL alarm persists, check the link state of all the ports. Rectify
the fault of the port link, and then check whether the DLAG_PROTECT_FAIL alarm is
cleared.
Step 3 If the value of Parameter 3 is 0x02, it indicates that the port fails to receive the LACP packets.
1. On the U2000, check whether the LAG is configured at the opposite end, and check whether
the port connected to the faulty port is added to the LAG at the opposite end. Make sure
that the LAG is correctly configured, and then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
2. If the DLAG_PROTECT_FAIL alarm persists, check whether the local port transmits
packets. If both ends can normally transmit and receive packets, check whether the
DLAG_PROTECT_FAIL alarm is cleared.
Step 4 If the value of Parameter 3 is 0x03, it indicates that the opposite equipment fails to enter the
LACP protocol synchronization status. Check the connection of the port, and LAG configuration
at the opposite equipment, and then check whether the DLAG_PROTECT_FAIL alarm is
cleared.
Step 5 If the value of Parameter 3 is 0x04, it indicates the port is in the self-loop state. Release the loop
and then check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 6 If the value of Parameter 3 is 0x05, it indicates that the communication between the active and
standby boards times out. Make sure the active and standby boards are in position, and the
communication between them is normal. Then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
Step 7 If the value of Parameter 3 is 0x06, it indicates that the communication between the board and
the cross-connect board and SCC board times out. Make sure that the software of the cross-
connect board and the SCC is normal. If the board normally communicates with the cross-
connect board or SCC board, check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 8 If the value of Parameter 3 is 0x07, it indicates that the active port selected by LACP is
inconsistent with the one selected by cross-connect board. Make sure that the active port selected

by LACP is consistent with the one selected by cross-connect board, and then check whether
the DLAG_PROTECT_FAIL alarm is cleared.
----End
Related Information
None
4.39 DSP_LOAD_FAIL
Description
The DSP_LOAD_FAIL is an alarm indicating DSP software loading failure. The alarm occurs
when loading the DSP program fails.
Attribute
Major Process alarm
Parameters
None

Loading the DSP program to the board fails. As a result, the board cannot work normally, which
has an influence on the services of users.
Possible Causes
Procedure
Step 1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
----End
Related Information
None

4.40 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating service connectivity loss. This alarm is generated
when the continuity check message (CCM) packets transmitted by the maintenance end point
(MEP) of the opposite end are not received within 3.5 times of the continuity check (CC) period.
Attribute
Parameters
Parameters 1 to 4 Indicates the Ethernet port.
Parameters 5 and 6 Indicates the VLAN ID.
Parameter 7 Indicates the direction of the maintenance point.
Parameter 8 Indicates the level of the maintenance domain.
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the CC source maintenance point.

The services may be interrupted.
Possible Causes
Cause 1: There is a failure in the service connectivity.
Procedure
l Cause 1: There is a failure in the service connectivity.

1. Check whether the related alarms, such as LINK_ERR, are reported. If the related
alarms are reported, clear the alarms first.
2. If the ETH_CFM_LOC alarm persists, check whether the attributes and cross-
connection status of the service are correctly configured on the U2000. If any error is
found, modify the configuration.
----End
Related Information
None
4.41 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating a misconnection. This alarm indicates that
there are misconnections between different maintenance domains (MDs).
Attribute
Critical Environment alarm
Parameters
Parameters 1 to 4 Indicates the Ethernet port.
Parameter 8 Indicates the level of the MD.

The CFM_OAM alarm is unable to test the service connectivity. The alarm is non-service
affecting.

Possible Causes
l Cause 1: The level of the MD to which the maintenance end point (MEP) belongs is
incorrectly configured.
l Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
l Cause 3: Certain physical links are incorrectly connected.
Procedure
l Cause 1: The level of the MD to which the MEP belongs is incorrectly configured.
1. Check whether the level of the maintenance point on the service is correctly
configured. If the level is incorrectly configured, change the level so that the level is
correct.
l Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
1. If the alarm persists, check whether the MD/MA names configured at the source and
sink ends are consistent. If not, modify them to the same, and then check whether the
alarm is cleared.
l Cause 3: Certain physical links are incorrectly connected.
1. If the alarm persists, check whether the physical links are misconnected. If yes,
reconnect the fiber or line, and then check whether the alarm is cleared.
----End
Related Information
None
4.42 ETH_CFM_MACSTATUS
Description
The ETH_CFM_MACSTATUS is a remote MAC defect indication. This alarm indicates that a
continuity check packet carrying a port tlv or an interface tlv is received from a given remote
MEP.
Attribute
Parameters


Parameters 1 to 4 Indicates the Ethernet port ID.
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).

The MAC status of remote mep's port is linkdown or discard.
Possible Causes
Cause 1: The port status of remote mep occur defection.
Procedure
l Cause 1: The port status of remote mep occur defection.
1. Check whether the port of remote mep is linkdown or discarding. Rectify the fault.
----End
Related Information
None
4.43 ETH_CFM_RDI
Description
The ETH_CFM_RDI is a remote CFM_OAM alarm indication. This alarm is generated at the
local end when the CFM_OAM fault is generated at the remote end. This alarm indicates that
at least one continuity check message (CCM) packet with the RDI indication is received.

Attribute
Minor Environment alarm
Parameters
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).

When the ETH_CFM_RDI alarm is generated, the services on the transmit side of the local
equipment may be interrupted.
Possible Causes
Cause 1: The opposite equipment detects a fault.
Procedure
l Cause 1: The opposite equipment detects a fault.
1. Check whether ETH alarms exist on the opposite equipment, and then rectify the fault
according to the alarms.
----End
Related Information
None

4.44 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating error frames. This alarm indicates that there
are error continuity check message (CCM) packets in the same maintenance association (MA).
Attribute
Parameters

The CFM_OAM alarm is unable to test the service connectivity. The alarm is non-service
affecting.
Possible Causes
l Cause 1: The periods of the MDs to which the MEPs of the stations of the service belong
are inconsistent.
l Cause 2: The MEP IDs in the MDs to which the MEPs of the stations of the service belong
are the same or illegal MEP ID is used.
l Cause 3: There are service loops in the MDs to which the MEPs of the service belong.
Procedure
l Cause 1: The periods of the MDs to which the MEPs of the stations of the service belong
are inconsistent.

1. Check whether the CCM periods that are configured on the equipment at the stations
of the service are consistent. If the CCM periods are inconsistent, change the
configuration so that the CCM periods are consistent.
l Cause 2: The MEP IDs in the MDs to which the MEPs of the stations of the service belong
are the same or illegal MEP IDs are used.
1. If the alarm persists, check whether the same MEP IDs are used in the MD to which
the MEPs of the stations of the service belong. If the same MEP IDs are used, delete
the repeated MEP ID and create another MEP ID so that no MEP ID conflict exists
in the MD.
l Cause 3: There are service loops in the MDs to which the MEPs of the service belong.
1. If the alarm persists, check whether there are service loops in the MDs to which the
MEPs of the service belong. If there are service loops, release the service loops.
----End
Related Information
None
4.45 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating the point-to-point Ethernet OAM
discovery failure. When the OAM protocol is enabled at the port of a board and the negotiation
with the opposite equipment fails, this alarm is generated.
Attribute
Parameters

Parameter 1 Indicates the reason why the negotiation fails.
l 0x01: A link fault occurs at the local end.

l 0x02: The local end fails to transmit the OAM message.
l 0x03: The local end fails to receive the OAM message.
l 0x04: The OAM configurations of the opposite end do not meet the
requirements of the local end.
l 0x05: The OAM configurations of the local end do not meet the requirements
of the opposite end.

The ETHOAM_DISCOVER_FAIL alarm is generated when the system runs the IEEE 802.3ah
OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to services.
Possible Causes
l A link fault occurs at the local end.
l The local end fails to transmit the OAM message.
l The local end fails to receive the OAM message in a specified time.
l The OAM configurations of the opposite end do not meet the requirements of the local end.
l The OAM configurations of the local end do not meet the requirements of the opposite end.
Procedure
Step 1 View the ETHOAM_DISCOVER_FAIL alarm on the U2000 and determine the possible causes
of the alarm according to Parameter 1.
Step 2 When Parameter 1 is 0x01, it indicates that a link fault occurs at the local end. Query the board-
level alarms on the U2000. Then remove the fault according to the specific link alarms such as
LINK_ERR and L_SYNC.
Step 3 When Parameter 1 is 0x02, it indicates that the local end fails to transmit the OAM message.
View the printed information about the serial port. The DSSP, drive, and microcode components
are involved in the problem. The fault location needs the assistance of engineers on related
project teams.
Step 4 When Parameter 1 is 0x03, it indicates that the local end fails to receive the 3ahOAM message
from the opposite end in a user-defined time.
1. Check whether the MAC addresses of the interconnected ports are the same. If yes, set
different MAC addresses for the interconnected ports. Then check whether the alarm is
cleared.
2. Check whether the 3ahOAM protocol is enabled at the opposite end. If not, enable the
protocol at the opposite end. Then check whether the alarm is cleared.
3. If the alarm persists, the local end fails to receive the OAM message. Replace the board.
For details, see the Parts Replacement.

Step 5 When Parameter 1 is 0x04, it indicates that the OAM configurations of the opposite end,
including link event reporting capability and unidirectional operation capability, do not meet the
requirements of the local end. Query and modify the configurations of the opposite port on the
U2000. When the configurations meet the requirements of the local end, the alarm is
automatically cleared.
Step 6 When Parameter 1 is 0x05, it indicates that the OAM configurations of the local end do not meet
the requirements of the opposite end. Query and modify the configurations of the local port on
the U2000. When the configurations meet the requirements of the opposite end, the alarm is
----End
Related Information
None
4.46 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs on the
remote end of point-to-point Ethernet OAM. When the port with the OAM protocol enabled
receives the OAM message that contains critical fault information from the opposite end, this
alarm is generated.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the fault.
l 0x01: A link fault occurs at the opposite port.

l 0x02: Irrecoverable problems such as a power failure occur at the opposite
end.
l 0x03-0xFF: Other unknown faults occur.


The ETHOAM_RMT_CRIT_FAULT alarm is generated when the system runs the IEEE
802.3ah OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to
services. This alarm indicates that the signal loss alarm is generated at the receive end of the
opposite port.
Possible Causes
The port with the OAM protocol enabled receives the OAM message that contains critical fault
information from the opposite end, such as a link fault or power failure.
Procedure
Step 1 If a link fault occurs at the opposite port, query board-level alarms on the U2000. Remove the
fault according to the specific link alarms such as L_SYNC and LINK_ERR. Check whether
Step 2 If irrecoverable problems such as a power failure occur at the opposite end, remove the fault.
The alarm is automatically cleared.
Step 3 If other unknown faults occur, contact Huawei engineers.
----End
Related Information
None
4.47 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating the remote loopback of the point-to-point
Ethernet OAM. This alarm only occurs at the port with the point-to-point OAM protocol enabled.
If the port is able to respond to loopback, it enters the loopback response state and reports the
loopback response alarm after it receives the remote loopback enabling command sent by the
opposite OAM port. The loopback initiation end reports the loopback initiation alarm. If the port
receives the loopback disabling command, it exits the loopback response state and ends the
loopback response alarm. The loopback initiation end also ends the loopback initiation alarm.
Attribute
Parameters


Name Meaning
Parameter 1 l 0x01: The loopback is initiated.

l 0x02: The loopback is responded.

The ETHOAM_RMT_LOOP alarm is generated when the system runs the IEEE 802.3ah OAM
protocol. When this alarm is generated, it indicates that the services are looped back from the
loopback initiation end to the loopback response end. The services and other packets are all
interrupted.
Possible Causes
l A command is issued to enable the loopback at the local port, and the opposite end is the
loopback response end.
l A command is issued to enable the loopback at the opposite port, and the local end is the
loopback response end.
Procedure
Step 1 Disable the loopback. The ETHOAM_RMT_LOOP alarm is automatically cleared.
----End
Related Information
None
4.48 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating the remote SD of the point-to-point Ethernet
OAM. When the port with the OAM protocol enabled receives the link event message from the
opposite end which indicates that the remote Ethernet performance is degraded, this alarm
occurs.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the type of the received link event:
l 0x01: error frame event

l 0x02: error frame period event
l 0x03: error frame second event

The ETHOAM_RMT_SD alarm is generated when the system runs the IEEE 802.3ah OAM
protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to services. When
this alarm is generated, it indicates that the alarm indicating that the error frame crosses the
threshold occurs at the receive end of the local port. The service performance degrades.
Possible Causes
The port with the OAM protocol enabled receives the link event message from the opposite end.
Procedure
Step 1 Improve the link performance at the opposite end until the opposite end does not send link event
message to the local end, and thus the ETHOAM_RMT_SD alarm at the local end is
Step 2 Modify the value of the link performance monitoring threshold at the opposite end. Then the
ETHOAM_RMT_SD alarm at the local end is automatically cleared.
Step 3 Disable the link event reporting at the opposite end. Then the ETHOAM_RMT_SD alarm at the
local end is automatically cleared.
----End
Related Information
None
4.49 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating loopback of the MAC port that receives the
OAM protocol packets in a point-to-point manner. If the MAC port of a board receives the OAM

protocol packets sent by itself or the board after detection of the loop is enabled, the
ETHOAM_SELF_LOOP alarm is reported.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the loopback type.
l 0x01: self-loop of the port

l 0x02: self-loop of the board
l 0x03-0xff: other reasons

In the case of the ETHOAM_SELF_LOOP alarm, the port is in the self-loop state. The U2000
provides a function of automatically shutting down the port in the case of the
ETHOAM_SELF_LOOP alarm. If the user enables this function in advance, services of this
port are interrupted. Otherwise, a broadcast storm may occur.
Possible Causes
l Self-loop is performed for the port with a fiber.
l Loopback is set among ports of the board.
l The PHY/MAC loopback of the port is manually set.
Procedure
Step 1 Check whether the transmit and receive ends of the port are connected with a fiber. If yes, connect
the fiber correctly, and then check whether the ETHOAM_SELF_LOOP alarm is cleared.
Step 2 If the ETHOAM_SELF_LOOP alarm persists, check whether the transmit and receive ends of
the port are connected to those of other ports with fibers. If yes, connect the fibers correctly, and
then check whether the ETHOAM_SELF_LOOP alarm is cleared.
Step 3 If the ETHOAM_SELF_LOOP alarm persists, check whether any PHY/MAC-layer loopback
is set for the port. If yes, release the loopback, or wait for five minutes when the U2000

automatically releases the loopback. Then check whether the ETHOAM_SELF_LOOP alarm is
cleared.
----End
Related Information
None
4.50 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP is an alarm indicating the loopback of the VCTRUNK port
that receives the OAM protocol packets in a point-to-point manner. If the VCTRUNK port of a
board receives the OAM protocol packets sent by itself or the board after detection of the loop
is enabled, the ETHOAM_VCG_SELF_LOOP alarm is reported.
Attribute
Parameters
Name Meaning
Parameters 1 and 2 Indicate the VCG port number.
Parameter 3 Indicates the loopback type.
l 0x01: The link of the VCG port is configured with a self-loop.

l 0x02: The link between VCG ports is configured with a loop.
l 0x03-0xff: There are other reasons.

In the case of the ETHOAM_VCG_SELF_LOOP alarm, the link of the VCG port is configured
with a self-loop. The U2000 provides a function of automatically shutting down the port in the
case of the ETHOAM_VCG_SELF_LOOP alarm. If the user enables this function in advance,
services of this port are interrupted. If the user does not enable this function, a broadcast storm
may occur.

Possible Causes
l The links of the VCG port is configured with a self-loop.
l The links between VCG ports of the board is configured with a loop.
l The port is configured with a loopback at the PHY/MAC layer manually.
Procedure
Step 1 Check the ETHOAM_VCG_SELF_LOOP alarm on the U2000, and determine the VCG port
number according to Parameters 1 and 2.
Step 2 Check the link configuration of the VCG port to see whether the transmit and receive directions
of the port are connected. Make sure the link configuration is correct, and then check if the
ETHOAM_VCG_SELF_LOOP alarm is cleared.
Step 3 If the ETHOAM_VCG_SELF_LOOP alarm persists, check the link configuration of the VCG
port to see whether this VCG port is connected to another VCG port on the board in the transmit
and receive directions. Make sure that the link configuration is correct. Then, the
ETHOAM_VCG_SELF_LOOP alarm is cleared.
Step 4 If the alarm persists, check whether the port is configured with a loopback at the PHY/MAC
layer. If the loopback exists, release it manually.
----End
Related Information
None
4.51 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the maintenance point (MP) ID
conflict. When an MP receives the message sent by another MP with the same MP ID in a
maintenance domain, this alarm occurs.
Attribute
Parameters

Parameters 1 and 2 Indicates the number of the Ethernet port where the alarm is generated.
Parameters 6 to 9 Indicates the ID of the MP where the alarm occurs. The highest byte
indicates the network ID. The second highest byte indicates the node ID
of the network. The lower two bytes indicate the identifier of the MP on
the network node.
The MP should be unique networkwide. Each node supports a maximum

of 1024 MPs (each data board supports a maximum of 128 MPs).

The MP should be unique networkwide. The MP conflict can affect the protocol and cause the
LB and LT tests to become abnormal. The services may be incorrectly received.
Possible Causes
Multiple MPs with the same MPID are created in a maintenance domain.
Procedure
Step 1 View the EX_ETHOAM_MPID_CNFLCT alarm on the U2000 and confirm the ID of the
relevant MP according to the alarm parameters.
Step 2 Query the information about the MP. Delete all the MPs that repeat the MPID, the alarm is
----End
Related Information
None
4.52 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm is
generated when the system detects the loss of the external clock source traced by the equipment.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located.
Parameter 2 l Indicates the slot ID of a board when ports are concatenated.

l The value is always 0xf0 when ports are not concatenated.
Parameter 3 Indicates the reserved byte, whose value is always 0x00.
Parameter 4 When ports are concatenated:
l 0x01: The first external clock source of the concatenated port is lost.
l 0x03: The second external clock source of the concatenated port is lost.
When ports are not concatenated:
l 0x01: The first external clock source is lost.

l 0x02: The second external clock source is lost.

When the EXT_SYNC_LOS alarm is generated, the external clock source of the system is lost
and cannot be traced by the equipment. This is because the clock quality may be lowered, the
service quality may be affected, and pointer justifications and even bit errors may be generated.
Possible Causes
The possible causes of the EXT_SYNC_LOS alarm are as follows:
l Cause 1: The physical interface for the external clock source loses signals.
l Cause 2: The input and output modes of the external clock source are inconsistent.
l Cause 3: The clock input cable is incorrectly connected.
l Cause 4: The clock board is faulty.
Procedure
l Query alarms on the U2000. Determine the number of the subrack where the clock loss
occurs and which clock is lost according to the alarm parameters.
l Cause 1: The physical interface for the external clock source loses signals.

1. Check whether the output signals of the external clock equipment are normal. If not,
replace the faulty external clock equipment, and then check whether the alarm is
cleared.
1. If the alarm persists, check whether the input and output modes of the external clock
source are consistent. After the input and output of the external clock source are set
to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared. For
details, see Configuring Physical Clock in the Feature Description.
l Cause 3: The clock input cable is incorrectly connected.
1. If the alarm persists, check whether the clock input cable is correctly connected. If
not, ensure the correct connection of the clock input cable, and then check whether
the alarm is cleared. For details, see the Installation Guide.
1. If the alarm persists, perform cold reset on the timing board, and then check whether
the alarm is cleared. For details, see Performing a Cold Reset of a Board in the
Supporting Tasks.
2. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
----End
Related Information
None
4.53 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm indicating the loss of the external timing source. This alarm
is generated when the board does not detect the external timing signal after the external timing
port is enabled.
Attribute
Parameters

Name Meaning
Parameter 2 l Indicates the slot ID of a board when ports are concatenated.

l The value is always 0xf0 when ports are not concatenated.
Parameter 4 Indicates which external clock source is lost.
l 0x02: The first external timing source is lost.

l 0x04: The second external timing source is lost.

The time of the local NE cannot be synchronous with the time of the external timing equipment
to which the enabled external timing port is connected.
Possible Causes
The possible causes of the EXT_TIME_LOC alarm are as follows:
l Cause 1: The physical interface for the external timing source loses signals.
l Cause 2: The timing input cable is incorrectly connected.
Procedure
l Query alarms on the U2000. Determine the number of the subrack where the external timing
loss occurs and which external timing source is lost according to the alarm parameters.
l Cause 1: The physical interface for the external timing source loses signals.
1. Check whether the output signals of the external timing equipment are normal. If not,
replace the faulty external timing equipment, and then check whether the alarm is
cleared.
l Cause 2: The timing input cable is incorrectly connected.
1. If the alarm persists, check whether the timing input cable is correctly connected. If
not, ensure the correct connection of the timing input cable, and then check whether
the alarm is cleared. For details, see the Installation Guide.
1. If the alarm persists, perform cold reset for the clock board, and then check whether
the alarm is cleared. For details, see Performing a Cold Reset of a Board in the
Supporting Tasks.
----End

Related Information
None
4.54 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating a fan failure. This alarm is generated when two or more
fans fail.
Attribute
Parameters
None

The failure of two or more fans leads to the increase on the board temperature and even the
damage to the board.
Possible Causes
l The fans stop running.
l The speed of the fans is excessively low.
l The fans fail.
Procedure
Step 1 Check whether the FAN Speed Level is set to Stop or Low Speed through the U2000. If that
is the case, set FAN Speed Level to High Speed.
Step 2 If the alarm persists, replace the faulty fan tray assembly. For details, see the Parts
Replacement.
----End
Related Information
None

4.55 FAN_FAULT
Description
The FAN_FAULT is an alarm indicating a fan fault. This alarm is generated when one fan fails.
Attribute
Parameters
None

The failure of one fan may lead to the increase on the board temperature and even the damage
to the board.
Possible Causes
l One fan fails.
l The logical inspection fails.
Procedure
Step 1 Replace the fan tray assembly. For details, see the Parts Replacement.
----End
Related Information
None
4.56 FC_8B10BERR_OVER
Description
The FC_8B10BERR_OVER is an alarm indicating that the 8B10B bit errors in the FC services
cross the threshold. When the 8B10B bit errors in the FC services cross the threshold, this alarm
is generated.

Attribute
Parameters
None

The quality of services is affected.
Possible Causes
There are bit errors on the link, which causes the 8B10B bit errors on the ports of the FC link
layer after decoding cross the threshold.
Procedure
Step 1 Check whether there is dust on the optical fiber connector or the fiber is aged. If that is the case,
clean the optical fiber connector or replace the fiber. For details, see the Supporting Tasks.
Step 2 Step 2 Check whether the input optical power of the board is within the normal range. For optical
power specifications, see the corresponding Product Description. If the optical power is
abnormal, see the handing procedures for the IN_PWR_HIGH and IN_PWR_LOW alarms, to
clear the alarm.
----End
Related Information
None
4.57 FCS_ERR
Description
The FCS_ERR is an alarm indicating that the frame check sequence (FCS) is incorrect. At the
local station, perform an FCS check for the received frames encapsulated in the GFP format. If
any error occurs in the check, the alarm is reported.
NOTE
The alarm is generated only when the received service of the local station is the GFP service.
This is because the IDLE frame lacks the FCS field, if the IDLE frame is encapsulated in the GFP format,
the FCS check errors may occur.

Attribute
Parameters
None

l If the FCS_ERR alarm is generated due to inconsistent encapsulation protocols, the services
are interrupted.
l If the FCS_ERR alarm is generated due to bit errors in the system, packets are lost or
services are interrupted.
Possible Causes
The possible causes of the FCS_ERR alarm are as follows:
l Cause 1: Mapping protocols of the local station and opposite station are inconsistent. For
example, the local station uses the GFP encapsulation protocol whereas the opposite station
uses the LAPS encapsulation protocol. Or the parameter settings of the protocol are
inconsistent. For example, both stations use the GFP encapsulation but Extension Header
Option of the local station is set to Yes whereas Extension Header Option of the opposite
station is set to No.
l Cause 2: There are bit errors on the link.
l Cause 3: The optical connector of the Ethernet board at the optical interface is loose or
dirty.
Procedure
l Query current alarms on the U2000. Determine the VCTRUNK number that reports the
alarm. For details, see Querying the Current Alarms and Performance Events of a NE on
the U2000 in the Supporting Task.
l Cause 1: The encapsulation protocols adopted by the local station and the opposite station
are inconsistent or the settings of the protocol parameters are inconsistent.
1. Check whether the encapsulation protocols of corresponding VCTRUNK ports of the
local station and the opposite station are consistent and whether the parameter settings
of the protocols are consistent. For example, check whether the parameters such as
Scramble and Set Inverse Value for CRC about the protocols are set as the same.
For details, see the Configuration Guide. Then, check whether the alarm is cleared.
2. If the alarm persists, see Cause 2.
l Cause 2: There are bit errors on the link.
1. Check the network-wide alarms on the U2000. For operations, see the Routine
Maintenance. Check whether there are bit error alarms such as B3_EXC and

B3_SD on the link. If these alarms occur, clear these alarms according to
corresponding procedures. Then, check whether the alarm is cleared.
l Cause 3: The optical connector of the Ethernet board at the optical interface is loose or
dirty.
1. Check whether the connector of the fiber is normal. If the connector is loose, tighten
the connector.
2. See Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task to
check whether the connector is dirty. If the connector is dirty, ensure that it is cleaned
immediately. For operations, see the Supporting Task.
3. If the attenuation value of the optical attenuator is improper, increase or decrease it to
a proper value. The value of the optical attenuator is set according to the receive optical
power of the board. For optical power specifications of boards, see Technical
Specifications of the Product Description. For operations of adjusting the optical
attenuator, see Adjusting, Replacing, Adding and Removing Attenuator in the
Supporting Task. For operations of querying the optical power, see Querying Optical
Power on the U2000 in the Supporting Task.
NOTE
From Querying Optical Module Information in the Supporting Task or Hardware

Description, you can obtain the manufacturer information of the optical module on the board.
4. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
1. After the preceding causes are excluded, if the alarm persists, the board where the
alarm is reported is faulty. In the case of the Ethernet board with an interface board,
replace the interface board first. In the case of the board without an interface board,
replace the faulty board. For details, see Parts Replacement.
----End
Related Information
None
4.58 FEC_LOF
Description
The FEC_LOF is an alarm indicating that lost of the FEC frame. The alarm occurs when the
FEC frame is lost.

Attribute

Parameters
None

When the FEC_LOF alarm is generated, the FEC function is disabled. Consequently, the services
are interrupted.
Possible Causes
l The cable is faulty, or the optical power is improper.
l The service rate is incorrect.
l The clocks on the NEs are out of synchronization.
l Certain problems are found in the services from the opposite end.
Procedure
Step 1 View the FEC_LOF alarm on the U2000 to determine the relevant board.
Step 2 View the receive optical power of the board on the U2000. If the receive optical power is
excessively low, clean the fiber header and connector. If the receive optical power is excessively
high, provide more optical attenuators. After making sure that the receive optical power is proper,
check whether the FEC_LOF alarm is cleared.
Step 3 If the alarm persists, check whether the upstream service is the FEC service at the same rate. If
not, configure the FEC service at a correct rate, and then check whether the FEC_LOF alarm is
cleared.
Step 4 If the alarm persists, check whether the upstream service is supported by the board. If not,
configure a correct service, and then check whether the FEC_LOF alarm is cleared.
Step 5 If the alarm persists, check whether the clocks on the local NE and the opposite NE are
synchronous with those on the network. If not, set the clock tracing function, and then check
whether the FEC_LOF alarm is cleared.
Step 6 If the alarm persists, the board hardware may be faulty. In this case, replace the board that reports
the alarm at the local station.
Step 7 If the alarm persists, the board at the opposite station may be faulty. In this case, replace the
board.
----End

Related Information
None
4.59 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out-of-frame.
Attribute
Parameters
None

When the FEC_OOF alarm is generated, the FEC function is disabled. Consequently, the
Possible Causes
l The fiber is faulty, or the optical power is improper.
l Excessive bit errors occur during transmission.
l The clocks on the NEs are out of synchronization.
l The transmit unit at the opposite end is faulty.
Procedure
Step 1 View the FEC_OOF alarm on the U2000 to determine the relevant board.
Step 2 View the received optical power of the board on the U2000. If the received optical power is
excessively low, clean the fiber header and the connector. If the received optical power is
excessively high, provide more optical attenuators. After making sure that the received optical
power is proper, check whether the FEC_OOF alarm is cleared.
Step 3 If the alarm persists, check the transmit optical power at the opposite end. If the transmit optical
power is excessively low, replace the board at the opposite end.
Step 4 If the alarm persists, check whether the clocks on the local NE and the opposite NE are
synchronous with those on the network. If not, set the clock tracing function, and then check
whether the FEC_OOF alarm is cleared.
Step 5 If the alarm persists, check whether the fiber is normal. If yes, replace the board that generates
the alarm.

Step 6 If the alarm persists, replace the cross-connect and timing board at the local station.
Step 7 If the alarm persists, replace the line board at the opposite end.
Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite end.
----End
Related Information
None
4.60 FPGA_ABN
Description
The FPGA_ABN is an alarm indicating that the FPGA status is abnormal. The alarm occurs
when the standby FPGA is currently used by the board.
Attribute
Parameters
None

The active FPGA file of the board is abnormal and the standby FPGA file is enabled. If the
standby FGPA file is abnormal, the board cannot work, which has an influence on the services
of users. This problem needs to be handled in time.
Possible Causes
l The active FPGA file does not exist when the board starts.
l Loading of the active FPGA file fails when the board starts.
Procedure
Step 1 Reload the FPGA file to the board.
----End
Related Information
None

4.61 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is forcibly selected.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot of the clock board that is selected forcibly.
l 0x01 indicates the slot with a smaller number.

l 0x02 indicates the slot with a bigger number.

If the forcibly selected clock board is normal, transient interruption occurs when the services
are switched. Otherwise, the services are interrupted.
Possible Causes
The command of forcibly selecting the clock board is issued.
Procedure
Step 1 After the command of forcibly selecting the clock board is cancelled, the FSELECT_STG alarm
is automatically cleared.
----End
Related Information
None

4.62 FWD_PKT_LOSS
Description
The FWD_PKT_LOSS is an alarm indicating loss of packets at a certain port
Attribute
Parameters
Name Meaning
Parameter 1 Indicates why the packets are lost.

The services lose packets or are interrupted.
Possible Causes
l The packets received by the port do not match the service configuration.
l The packets received by the port do not match the port configuration.
l Packets are lost because of data congestion, such as the loss of the CAR shaping packet.
l The packets in a queue are lost, such as the loss of the COS packet.
l The MAC address of the received packets is listed on the black list.
Procedure
Step 1 Check whether the service configuration and the attribute configuration of the port match the
received packets. If a mismatch occurs, re-configure the service and/or the attributes of the port.
Step 2 If the alarm persists, check whether the packets transmitted at the opposite station are proper. If
not, transmit proper packets again.
Step 3 If the alarm persists, check whether the QoS is configured properly. If not, re-configure the QoS.

Step 4 If the alarm persists, check whether the black list is configured properly. If not, re-configure the
black list.
----End
Related Information
None
4.63 GAINDATA_MIS
Description
The GAINDATA_MIS is an alarm indicating mismatch of gain attribute. When the nominal
gain value issued by the NE software falls beyond the tuning range of the nominal gain, the
alarm is reported.
Attribute
Parameters
None

The service quality may be affected.
Possible Causes
Cause 1: As for the nominal gain, replacing the optical amplifier unit (OAU) or the optical
module causes that the nominal gain value issued by the NE software falls beyond the new tuning
range of the nominal gain.
Procedure
l Cause 1: The nominal gain value issued by the NE software falls beyond the new tuning
range of the nominal gain.
1. Query the threshold of the current actual nominal gain on the U2000. Reconfigure a
valid nominal gain value for the optical interface channel of the unit based on the
queried threshold.
----End
Related Information
None

4.64 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware failure. When the system detects hardware
failure, this alarm is reported.
Attribute
Parameters

Parameter 1 Indicates the fault type of the alarm. For example:
0x01 indicates that the power supply module is abnormal.
0x02 indicates that the board is not properly installed (the

board is not in good contact with the backplane, that is, the
board is not secured).
0x03 indicates that 38M system clock 1 is abnormal.
0x05 indicates that the 2M clock source is abnormal.
0x06 indicates the digital phase-locked loop is abnormal.
0x07 indicates that the 38M service clock is lost.
0x08 indicates that the bus is abnormal.
0x09 indicates that the standby board in TPS protection is

abnormal.
0x0a indicates the active crystal oscillator of the clock stops.
0x0b indicates the frequency deviation of the crystal oscillator

0x0c indicates that the standby crystal oscillator of the clock

stops.
0x0d indicates that the CPU/DSP/coprocessor fails.
0x0e indicates that the memory component the fails.
0x0f indicates that the component of the programmable logic

device fails
0x10 indicates that the SDH component fails.
0x11 indicates that the data communication component fails.
0x12 indicates that the clock component fails.
0x13 indicates that the interface component fails.
0x14 indicates that the power component fails.
0x15 indicates that other faults occur.
0x17 indicates that the 32M clock is invalid.
0x1a indicates that the loop of the cross-connect chip fails.
0x1b indicates that the 8k online signal is pulled down.

0x1c indicates that the chip of the probe laser fails.
0x1c indicates that the chip of the loading laser fails.
0x1e indicates that the clock of the DSP driver chip is lost.
0x1f indicates that the output clock of the DSP is lost.
0x20 indicates that the RTM module is offline.
0x21 indicates that a chip fault.
0x22 indicates the 2M system frame header 1.
0x24 indicates that the self-check fails.
0x25 indicates the self-check of the PHY chip fails.
0x26 indicates that detecting the port status of the PHY chip
fails.
0x27 indicates that the 25M clock is lost.
0x28 indicates that the APD fails.
Parameters 2 and Parameters 3 When Parameter 1 is 0x08 and Parameter 2 is 0x01, it

indicates that bus A is abnormal. When Parameter 2 is 0x02,
bus B is abnormal.
When Parameter 1 is 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14,

0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have
different values, which indicate different component, module,
or chip faults.
When Parameter 1 is of another value, Parameter 2 and

Parameter 3 are always 0xff.

The alarm affects the normal operating of the board and affects services.
Possible Causes
l Cause 1: The NE power is abnormal.
l Cause 2: The board is not connected to the backplane properly or the board is faulty.
Procedure
l Cause 1: The NE power is abnormal.
1. Check whether the NE power works normally. If not, feed the NE with power
supply. For details, see Quick Installation Guide.

l Cause 2: The board is not connected to the backplane properly or the board is faulty.
1. Reseat the board. For operations, see "Removing Boards" and "Inserting Boards" in
the Quick Installation Guide. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
4.65 HARD_ERR
Description
The HARD_ERR is an alarm indicating a hardware error. The alarm occurs when the board
hardware has a minor fault.
Attribute
Parameters

Parameter 1 Indicates the fault type of the alarm. For example:
0x01 indicates that the power supply module is abnormal.
0x02 indicates that the board is not properly installed (the

board is not in good contact with the backplane, that is, the
board is not secured).
0x05 indicates that the 2M clock source is abnormal.
0x06 indicates the digital phase-locked loop is abnormal.
0x07 indicates that the 38M service clock is lost.
0x08 indicates that the bus is abnormal.
0x09 indicates that the standby board in TPS protection is

abnormal.
0x0a indicates the active crystal oscillator of the clock stops.
0x0b indicates the frequency deviation of the crystal oscillator

0x0c indicates that the standby crystal oscillator of the clock

stops.
0x0d indicates that the CPU/DSP/coprocessor fails.
0x0e indicates that the memory component the fails.
0x0f indicates that the component of the programmable logic

device fails
0x10 indicates that the SDH component fails.
0x11 indicates that the data communication component fails.
0x12 indicates that the clock component fails.
0x13 indicates that the interface component fails.
0x14 indicates that the power component fails.
0x15 indicates that other faults occur.
0x1a indicates that the loop of the cross-connect chip fails.
0x1b indicates that the 8k online signal is pulled down.

0x1c indicates that the chip of the probe laser fails.
0x1c indicates that the chip of the loading laser fails.
0x1e indicates that the clock of the DSP driver chip is lost.
0x1f indicates that the output clock of the DSP is lost.
0x20 indicates that the RTM module is offline.
0x21 indicates that a chip fault.
0x24 indicates that the self-check fails.
0x25 indicates the self-check of the PHY chip fails.
0x26 indicates that detecting the port status of the PHY chip
fails.
0x27 indicates that the 25M clock is lost.
0x28 indicates that the APD fails.
Parameters 2 and Parameters 3 When Parameter 1 is 0x08 and Parameter 2 is 0x01, it

indicates that bus A is abnormal. When Parameter 2 is 0x02,
bus B is abnormal.
When Parameter 1 is 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14,

0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have
different values, which indicate different component, module,
or chip faults.
When Parameter 1 is of another value, Parameter 2 and

Parameter 3 are always 0xff.

The services are not affected. For specific influence, see Parameter 1.
Possible Causes
Procedure
Step 1 Perform warm reset or cold reset on the faulty board through the U2000. For details, see the
Troubleshooting.
----End

Related Information
None
4.66 HP_LOM
Description
The HP_LOM is an alarm indicating higher order path loss of multiframe.
Attribute
Parameters
None

When the HP_LOM alarm occurs, it indicates that the values of the H4 bytes in the payload is
inconsistent with the expected values in several consecutive basic frames in the multiframe
sequence. The multiframe indication of the VC-12 services is lost. As a result, the VC-12 services
are unavailable.
When the HP_LOM alarm occurs, the board will insert VTAIS (TU_AIS for tributary services)
into the corresponding path.
Possible Causes
The possible causes of the HP_LOM alarm are as follows:
l The services are incorrectly configured.

l The H4 byte is lost or the H4 byte value is invalid.
Procedure
Step 1 Check whether the services at the opposite station and the local station are correctly configured.
If not, modify the incorrect configuration and issue it again.
Step 2 View alarms on the U2000 to check whether the HP_LOM alarm is cleared.
Options Description
If this alarm is cleared The fault is removed. End the alarm handling.
If this alarm persists Proceed to the next step.

Step 3 Check whether the cross-connect unit and the line board are faulty. You can employ the optical
path self-loop method to check whether any hardware of the opposite station is faulty. If the
fault is located on the opposite station. Replace the line board first and then the SCC board of
the opposite station.
Step 4 View alarms on the U2000 to check whether the HP_LOM alarm is cleared.
Options Description
Step 5 Ensure the local station is faulty. Replace the faulty board.
----End
Related Information
None.
4.67 HP_RDI
Description
The HP_RDI is an alarm indicating that the local station receives the remote defect indication
in the higher order path sent from the opposite station
Attribute
Parameters
None

When the HP_RDI alarm occurs, it indicates that the services received by the opposite station
have the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm. As a result, the HP_RDI alarm is
sent to the local station.
Possible Causes
The possible causes of the HP_RDI alarm are as follows:

l The opposite line receives the AU_AIS/AU_LOP/HP_TIM/HP_SLM alarms.

l The receive part at the opposite station is faulty.
l The transmit part at the local station is faulty.
Procedure
Step 1 View the alarms of the NE on the U2000 and check whether there are higher order alarms.
Options Description
If the AU_AIS, AU_LOP, HP_TIM, and Refer to the corresponding section in this
HP_SLM alarms occur document to clear the alarm.
If the AU_AIS, AU_LOP, HP_TIM, and Proceed to the next step.

HP_SLM alarms do not occur
Step 2 View alarms on the U2000 to check whether the HP_RDI alarm is cleared.
Options Description
Step 3 Perform the loopback for the stations at two ends of the line. Locate the faulty board.
Options Description
The board at the opposite station reports the The transmit end of the board at the opposite
HP_RDI alarm station is faulty. Replace the faulty board.
The board at the local station reports the The receive end of the board at the local
HP_RDI alarm station is faulty. Replace the faulty board.
----End
Related Information
AU_AIS, AU_LOP, HP_TIM, HP_SLM
4.68 HP_REI
Description
The HP_REI is an alarm indicating that the local station receives the remote bit error in the
higher order path sent from the opposite station.

Attribute
Warning Service quality alarm
Parameters
None

When the HP_REI alarm occurs, it indicates that the services received by the opposite station
have the higher order B3 errored blocks. As a result, the HP_REI alarm is sent to the local station.
Possible Causes
The possible cause of the HP_REI alarm is as follows:
The B3 bit errors are received at the opposite station.
Procedure
Step 1 View the alarms on the opposite NE, and check whether there are B1 or B2 bit errors.
Options Description
There are B1 or B2 bit errors Refer to the corresponding section in this

document to clear the alarm.
There are B1 or B2 bit errors Proceed to the next step.
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If few B3 bit errors occur at the remote end, the fault usually lies
in the equipment instead of the optical path.
Step 3 Perform the loopback for the stations at two ends of the line. Check whether the cross-connect
and timing unit and the tributary board on both the opposite equipment and local equipment
operate normally. Following the service direction, check upstream stations one by one. Locate
the faulty board.
Options Description
The board at the opposite station reports B3 The receive end at the opposite station is
bit errors faulty. Replace the boards in an order of line
board, tributary board, and SCC board.
The board at the local station reports B3 bit The transmit end of the board at the local
errors station is faulty. Replace the faulty board.

NOTICE
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD
4.69 HP_SLM
Description
The HP_SLM is an alarm indicating the mismatch of the higher order path signal label (C2)
received by the line board.
Attribute
Parameters
None

When the HP_SLM alarm occurs, it indicates that the higher order overhead C2 byte received
by the local station is inconsistent with the C2 byte expected. As a result, the services in the
payload are unavailable.
When the HP_SLM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_SLM alarm are as follows:
l The signal label C2 byte expected to be received by the local station is inconsistent with
that transmitted by the opposite station.

Procedure
Step 1 Check whether the C2 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If the configuration
is different, modify them to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option Description
Step 4 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option Description
Step 5 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
Option Description
The board at the opposite station reports the The receive end at the opposite station is
HP_SLM alarm faulty. Replace the boards in an order of line
board and SCC board.
The board at the local station reports The receive end of the board at the local
HP_SLM bit errors station is faulty. Replace the faulty board.
NOTICE
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.

4.70 HP_TIM
Description
The HP_TIM is an alarm indicating the mismatch of the higher order path trace identifier (J1)
received by the line board.
Attribute
Parameters
None

When the HP_TIM alarm occurs, it indicates that the higher order overhead J1 byte received by
the local station is inconsistent with the J1 byte expected. As a result, the services in the payload
are unavailable.
When the HP_TIM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_TIM alarm are as follows:
l The path trace identifier J1 byte expected to be received by the local station is inconsistent
with that transmitted by the opposite station.
Procedure
Step 1 Check whether the J1 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If not, modify them
to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the HP_TIM alarm is cleared.
Options Description

Step 4 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
Option Description
The board at the opposite station reports the The receive end at the opposite station is
HP_TIM alarm faulty. Replace the boards in an order of line
board and SCC board.
The board at the local station reports HP_TIM The receive end of the board at the local
bit errors station is faulty. Replace the faulty board.
NOTICE
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
4.71 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the higher order path received by the line board is
unloaded.
Attribute
Parameters
None

When the HP_UNEQ alarm occurs, it indicates that the signal payload transmitted by the line
board at the opposite station is unloaded.

Possible Causes
The possible cause of the HP_UNEQ alarm is as follows:
The C2 byte in five consecutive frames is all "0"s.
Procedure
Step 1 Check the C2 byte configuration of the opposite NE to see whether the C2 byte has sent UNEQ.
If the configuration is incorrect, modify and re-issue the configuration.
Step 2 Check whether the line board of the opposite NE is configured with services in the transmitting
direction. If not, re-configure the services of the NE.
Step 3 View alarms on the U2000 to check whether the HP_UNEQ alarm is cleared.
Options Description
Step 4 The board at the local station is faulty. Replace the faulty board.
----End
Related Information
None.
4.72 HSC_UNAVAIL
Description
The HSC_UNAVAIL is an alarm indicating that the working/protection switching fails. This
alarm occurs when the configured active and standby boards fail to perform switching
Attribute
Parameters

Parameter 1 Indicates the working/protection status of the invalid board.
Parameter 2 Indicates the slot ID of the invalid board.

The active-standby switching and backup functions are not available.
Possible Causes
l The active and standby board versions mismatch.
l The hardware of the standby board is faulty.
l Communication between the active and standby boards is abnormal.
Procedure
Step 1 Replace the standby board. For details, see the Parts Replacement.
----End
Related Information
None
4.73 INTRA_OTU_STA_INDI
Description
The INTRA_OTU_STA_INDI alarm indicates the state of the Intra-OTU 1+1 optical channel
Attribute
Parameters


l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l When the intra-board 1+1 protection group actuates switching, services are transiently
interrupted.
l When the alarm is reported, the working channel or the protection channel of the board
might have faulty services that need to be restored.
Possible Causes
l Cause 1: A user issues a command to perform the external switching such as forced
switching, manual switching or locked switching.
l Cause 2: The services of the working channel or the protection channel of the intra-board
Procedure
l Cause 1: A user issues a command to perform the external switching.
external switching.
l Cause 2: The services of the working channel or the protection channel of the intra-board
1. Query whether the relevant boards for configuring the protection group have the
alarms, such as R_LOF, R_LOS, POWER_DIFF_OVER, R_LOC, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH,
IN_PWR_LOW, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG,
OTUk_EXC. If yes, handle the alarms by referring to the corresponding alarm
handling procedure to restore the services of the working channel or the protection
channel.
Revertive or not. If yes, the protection channel automatically switches to the working

channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive.
Then the protection channel automatically switches to the working channel and the
alarm clears.
1. This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
None
4.74 J0_MM
Description
The J0_MM is an alarm indicating trace indicator mismatch. The alarm occurs when the received
J0 byte is not consistent with the J0 byte to be received.
Attribute
Parameters
None

The services are not affected.
Possible Causes
l The J0 byte mismatches.
l The service connection is incorrect.
Procedure
Step 1 Check whether the J0 byte to be transmitted by the board at the opposite station is set the same
as the J0 byte to be received by the board at the local station. If they are inconsistent, set the two
as the same.
Step 2 If the alarm persists, bit errors may exist in the line. Refer to the handling procedure of the B1_SD
or B2_SD alarm for troubleshooting.

Step 3 If the alarm persists, consider whether to replace the board according to the actual situation
because only the J0_MM alarm does not affect the services. For details, see the Parts
Replacement.
----End
Related Information
None
4.75 K1_K2_M
Description
The K1_K2_M is an alarm indicating K1 and K2 byte mismatch. This alarm occurs when the
path numbers indicated in the transmitted K1 byte and the received K2 byte are inconsistent and
the inconsistency lasts for a time period (160 ms by default).
Attribute
Parameters
None

The MS protection fails. As a result, services are interrupted if a fiber cut or another fault occurs.
Possible Causes
The possible causes of the K1_K2_M alarm are as follows:
l The fiber connection is incorrect.

l The protection group types configured at the two ends of the protection group are
inconsistent.
Procedure
Step 1 View this alarm on the U2000, and determine the ID of the MS where the alarm is reported
according to alarm parameters.

Step 2 Check whether the fiber connection that this MS travels through is normal, and whether the
logical configuration of the fiber is consistent with the physical configuration. After confirming
that the fiber connection is correct, check whether the alarm is cleared
Step 3 If the alarm persists, check whether the protection group types configured at the two ends of the
protection group are consistent. If not, re-configure the protection type and check whether the
alarm is cleared.
Step 4 If the alarm persists, check the boards configured with the MS at the local and opposite ends are
faulty. If yes, replace the faulty board. For details, see the Parts Replacement.
Step 5 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are
faulty. If yes, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.76 K2_M
Description
The K2_M is an alarm indicating K2 byte mismatch. This alarm occurs when the protection
group type configured at the opposite end indicated by the fifth bit (counted from the highest bit
to the lowest bit) of the K2 byte is inconsistent with that of the local end, and the inconsistency
lasts for a time period (2s by default).
Attribute
Parameters
None

The MS protection fails. As a result, services are interrupted if a fiber cut or another fault occurs.
Possible Causes
The possible causes of the K2_M alarm are as follows:
l The MS configuration is incorrect.


Procedure
Step 1 Check whether the MS configuration on the local NE is consistent with that on the opposite NE.
If not, re-configure the MS and check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the boards configured with MSs at the local and opposite
ends are faulty. If yes, replace the faulty board and check whether the alarm is cleared
Step 3 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are
faulty. If yes, replace the faulty board and check whether the alarm is cleared
----End
Related Information
None
4.77 L_SYNC
Description
Loss of synchronization alarm. This alarm is generated when loss of synchronization occurs in
the physical coding sublayer (PCS) of a receiving port.
Attribute
Critical Service quality alarm
Parameters
None

When loss of synchronization occurs in the physical coding sublayer (PCS) of a receiving port,
the port stops receiving data. Thus, the loss of synchronization alarm affects the quality of service
(QoS). In this case, the service is interrupted.
Possible Causes
l Configuration of working mode, signal type or rate of the equipment at the local station
and the opposite station are not consistent.
l Link failure.
l The equipment in the opposite station is faulty.
l The receive optical power of the local board is abnormal.

l The board at the local station is faulty.
Procedure
Step 1 Check whether the configuration of working mode, signal type or rate of the equipment at the
local station and the opposite station are consistent. If they are not consistent, modify the setting
to ensure the consistency.
Step 2 If the alarm persists, check whether the fiber or cable that is used to connect between the
equipment at the local station and the opposite station are well connected. If they are not well
connected, reconnect or replace the fiber or cable.
Step 3 If the alarm persists, check whether the data equipment in the opposite station is faulty. If that
is the case, remove the fault of the data equipment in the opposite station.
Step 4 If the alarm remains, use the U2000 to check whether the receive optical power of the WDM-
side interface of the alarm-reporting board is in normal range. For optical power specifications
of boards, see the Product Description. If the optical power is abnormal, take the alarm as the
IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.
Step 5 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For
----End
Related Information
None
4.78 LAN_LOC
Description
Ethernet communication failure. In the case of NE cascading, this alarm is generated when the
ethernet communication between NEs fails.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the network port ID.
For the OptiX OSN 8800,
l 0x01 indicates the ETH1 port on the EFI2 board,

l 0x04 indicates the NM_ETH1 port on the EFI2 board,
l 0X05 indicates the NM_ETH2 port on the EFI1 board.
Parameters 2 and 3 Indicates the number of the channel in which the alarm is generated. The
value consists of two bytes and is always 0x00 0x01.

When the network port is faulty or there is a cut in the network cable, the communication at this
network port fails. In this case, the communication between the NE and the U2000 stops.
Possible Causes
l The network port is required and is enabled on the U2000. However, the network cable is
not connected to the network port or is inappropriately connected.
l The network port is not required but is enabled on the U2000.
l The network cable is faulty.
Procedure
Step 1 Query the alarm parameters on the U2000. Check whether the corresponding network port is
required according to the preceding table.
If ... Then ...
The corresponding network port is not Disable the port on the U2000. For details, see
required. "Disable the Unused Auxiliary Interfaces" in
the Commissioning Guide.
The corresponding network port is Check and ensure that the network cable is
required. properly connected to the network port.
Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable
and re-connect it.
Step 3 If the alarm persists, the auxiliary interface board (such as the AUX, EFI, EFI1, and EFI2 board)
may be faulty. In this case, replace the faulty board. For detailed operations, see Parts
Replacement.
----End

Related Information
None
4.79 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that the port in the aggregation group is invalid.
When the GE port is not available, the aggregation fails. Therefore, this alarm occurs.
Attribute
Minor Process alarm
Parameters
Name Meaning
Parameters 1 and 2 Indicates the number of the port where the alarm is generated, consisting
of two bytes. For example, 0x00 0x01 indicates port 1.
Parameter 3 Indicates the cause of the invalid port in the aggregate group. For example,
0x01 indicates that the port is in the link down or disabled state. 0x02
indicates that the port is in the half-duplex mode. 0x03 indicates that port
fails to receive LACP messages. 0x04 indicates that the port is self-
looped.

The port in the aggregation group fails to share the service load. In this case, the port cannot
receive or transmit services.
Possible Causes
l The port is in the link down or disabled state.
l The port is in the half-duplex mode.
l The port has not received LACP messages.
l The port is self-looped.

Procedure
Step 1 Check the link and enabling status of all ports on the U2000. Remove link faults, and then set
the port to Enable on the U2000.
Step 2 On the U2000, check whether the operation mode of the port is set to Half-Duplex. If yes, re-
set it to Full-Duplex. Then, the alarm is cleared.
Step 3 Check whether the corresponding link aggregation group is configured at the opposite station.
If yes, check whether the MAC address of the opposite aggregation group that provides links to
the local aggregation group is invalid. If yes, re-configure it.
Step 4 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
4.80 LASER_HAZARD_WARNING
Description
The Laser hazard warning alarm. When a high-power laser is used in the optical transmission
system, the system may cause personal injury. In this case, if the IPA function is not configured,
this alarm is reported prompting the user to configure the IPA function.
Attribute
Parameters
None

This alarm does not affect services; however, it might cause personal injury.
Possible Causes
l The laser power is high and the IPA protection is not configured.
l The laser power is high; although the IPA function has been configured, it is disabled.
Procedure
Step 1 Check the IPA configuration on the NE.

Step 2 If the NE is not configured with the IPA function, follow the network plan to create the IPA
protection. For detailed operations, see the Feature Description. If the IPA function is not
required or cannot be configured on the NE, suppress this alarm. For detailed operations, see
Suppressing NE Alarms in the Supporting Tasks.
Step 3 If the NE is configured with the IPA function, enable the IPA function.
Step 4 After the IPA function is configured and enabled, the alarm is cleared automatically. If the alarm
persists, contact Huawei for help.
----End
Related Information
None
4.81 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of the board is shut down.
Attribute
Parameters
None

When the LASER_SHUT alarm is generated, the services are interrupted.
Possible Causes
The user uses the U2000 or Navigator to perform the operation to shut down the laser.
Procedure
Step 1 If the user cancels the setting of laser shutdown, the LASER_SHUT alarm is automatically
cleared.
----End
Related Information
None

4.82 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction.
When the sink end of the LCAS module detects anomalies, the LCAS negotiation is unavailable
or incorrect and this alarm is generated.
Attribute
Parameters
None

When the LCAS_FOPR alarm is generated, it indicates that the protocol state machine in the
receive direction is in confusion. The negotiation may be abnormal.
Possible Causes
The possible causes of the LCAS_FOPR alarm are as follows:
l The downstream VCG receives repeated sequence numbers due to incorrect configurations
or link bit errors.
l The LCAS function of the opposite VCG is disabled.
l The downstream VCG simultaneously receives the FIXED and other LCAS control bytes
due to incorrect configurations or link bit errors.
l The cross-connection is incorrectly bound.
Procedure
Step 1 View the LCAS_FOPR alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the LCAS protocol is enabled at the opposite end. If not, enable the LCAS
protocol at the opposite end. Check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the configurations are correct. Especially, check whether
the cross-connection is bound correctly. If not, modify the incorrect configurations. Check
Step 4 If the alarm persists, disable and then enable the LCAS function at both ends. Check whether
----End

Related Information
None
4.83 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the failure of the LCAS protocol in the transmit
direction. When the source end of the LCAS module detects anomalies, the LCAS negotiation
is unavailable or incorrect and this alarm is generated.
Attribute
Parameters
None

When the LCAS_FOPT alarm is generated, it indicates that the protocol state machine in the
transmit direction is in confusion. The negotiation may be abnormal.
Possible Causes
There is the persistent and unexpected MST due to incorrect configurations or link bit errors.
For example, the member that transmits IDLE always receives MST=OK.
Procedure
Step 1 View the LCAS_FOPT alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the service cross-connection of the VCTRUNK is bound correctly. If not, modify
the incorrect configurations. Check whether the alarm is cleared.
----End
Related Information
None
4.84 LCAS_PLCR

Description
The LCAS_PLCR is an alarm indicating partial unavailability of the bandwidth in the LCAS
receive direction. When the LCAS function of the VCTRUNK is enabled, in the receive
direction, the number of paths that carry load is less than the number of paths configured and is
not zero.
Attribute
Minor Service alarm
Parameters
None

When the LCAS_PLCR alarm is generated, it indicates that the available bandwidth in the
receive direction is reduced. The services are not interrupted.
Possible Causes
The possible causes of the LCAS_PLCR alarm are as follows:
l Bidirectional services are not configured.

l The number of members in the upstream of the opposite end is less than that in the
downstream of the local end.
l The path communication fails because the cross-connection is incorrect or the physical link
is improperly connected.
Procedure
Step 1 Check whether there are other alarms such as AIS, LOP, UNEQ, and LOM. If yes, clear these
alarms first. Then, check whether the alarm is cleared.
Step 2 Ensure that the physical link is available. Check whether bidirectional services are configured.
If not, configure bidirectional services.
Step 3 If the alarm persists, check on the U2000 whether the number of downstream timeslots bound
with the VCTRUNK at the local end is consistent with that of upstream timeslots bound with
the VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number
of the timeslots at both ends consistent. Check whether the alarm is cleared.
Step 4 Check whether the cross-connection is bound from the transmit direction to the opposite end. If
not, re-bind the cross-connection. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, the wait-to-restore (WTR) time may be excessively long and thus the
members are still not restored. Then, check the WTR time. Wait for a period, and then check

Step 6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check
Step 7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then,
Step 8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
NOTICE
If the services that travel through the board are not configured with protection, the services are
interrupted after cold reset of the board.
----End
Related Information
None
4.85 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating partial loss of unavailability of the bandwidth in the
LCAS transmit direction. When the LCAS function of the VCTRUNK is enabled, in the transmit
direction, the number of paths that carry load is less than the number of paths configured and is
not zero.
Attribute
Minor Service alarm
Parameters
None

When the LCAS_PLCT alarm is generated, it indicates that the available bandwidth in the
transmit direction is reduced. The services will lose packets when the actual service traffic is
larger than the available bandwidth in the transmit direction.
Possible Causes
The possible causes of the LCAS_PLCT alarm are as follows:


l The number of members in the downstream of the opposite end is less than that in the
upstream of the local end.
l The path communication fails because the cross-connection is incorrect or the physical link
is improperly connected.
Procedure
Step 1 View the LCAS_PLCT alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the LCAS_PLCR alarm is present at the opposite station. If yes, clear the
LCAS_PLCR alarm first. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, check whether bidirectional services are configured. If not, configure
bidirectional services. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check on the U2000 whether the number of upstream timeslots bound with
the VCTRUNK at the local end is consistent with that of downstream timeslots bound with the
VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number of
the timeslots at both ends consistent. Check whether the alarm is cleared.
Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the opposite
end. Re-bind the cross-connection. The alarm is automatically cleared.
Step 6 If the alarm persists, the wait-to-restore (WTR) time may be excessively long and thus the
members are still not restored. Check the WTR time. Wait for a period, and then check whether
Step 9 If the alarm persists, perform cold reset on the board.
NOTICE
----End
Related Information
None
4.86 LCAS_TLCR

Description
The LCAS_TLCR is an alarm indicating the total loss of bandwidth in the LCAS receive
direction. When the LCAS function of the VCTRUNK is enabled, in the receive direction, the
number of paths that carry load is zero, whereas the number of paths configured is not zero.
Attribute
Major Service alarm
Parameters
None

When the LCAS_TLCR alarm is generated, it indicates that the available bandwidth in the
receive direction is reduced to zero. The services in the receive direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCR alarm are as follows:

l The upstream of the opposite end is not bound with members.
l The path communication fails because the cross-connection is incorrect or other alarms are
present.
Procedure
Step 1 View the LCAS_TLCR alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear
these alarms first. Then, check whether the alarm is cleared.
Step 3 Check whether bidirectional services are configured. If not, configure bidirectional services.
Step 4 If the alarm persists, check whether the upstream of the opposite end is bound with timeslots. If
not, bind the timeslots in the corresponding direction. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the local
end. Re-bind the cross-connection. The alarm is automatically cleared.

Step 8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
NOTICE
----End
Related Information
None
4.87 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating total loss of bandwidth in the LCAS transmit direction.
When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the number
of paths that carry load is zero, whereas the number of paths configured is not zero.
Attribute
Major Service alarm
Parameters
None

When the LCAS_TLCT alarm is generated, it indicates that the available bandwidth in the
transmit direction is reduced to zero. The services in the transmit direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCT alarm are as follows:
l The downstream of the opposite end is not bound with members.

l The path communication fails because the cross-connection is correct or other alarms are
present.

Procedure
Step 1 View the LCAS_TLCT alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the LCAS_TLCR alarm is present at the opposite station. If yes, clear the
LCAS_TLCR alarm first. Then, check whether the alarm is cleared.
Step 3 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear
these alarms first. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the downstream of the opposite end is bound with timeslots.
If not, bind the timeslots in the corresponding direction. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, check whether the cross-connection is correctly bound from the transmit
direction to the opposite end. If not, re-bind the cross-connection. Then, check whether the alarm
is cleared.
Step 8 If the alarm persists, perform cold reset on the board.
NOTICE
----End
Related Information
None
4.88 LOCK_CUR_FAIL
Description
The LOCK_CUR_FAIL is an alarm indicating that the pump drive currently unlocked. The
alarm occurs when the working current is abnormal.
Reporting side: NA
Attribute

Parameters
Parameter 1 Indicates the number of pump laser.

The locking of the output optical power of the board fails, which influences the services on the
entire optical line.
Possible Causes
The board is faulty.
Procedure
Tasks.
----End
Related Information
None
4.89 LOCKPOW_MIS
Description
The LOCKPOW_MIS is an alarm indicating mismatch of locked pump optical power. When
the locked pump optical power falls beyond the range of the locked pump optical power, the
alarm is reported.
Attribute
Parameters
None


Possible Causes
Cause 1: As for the locked pump optical power of the Raman board, a value that falls beyond
the range of the locked pump optical power is set.
Procedure
l Cause 1: A value that falls beyond the range of the locked pump optical power is set.
1. Query the locked pump optical power of the corresponding optical interface channel
and reconfigure a valid value on the U2000.
----End
Related Information
None
4.90 LP_RDI_VC3
Description
The LP_RDI_VC3 is a remote defect indication in the VC-3 lower order path. If a board has
detected that bit 5 of the G1 byte in the VC-3 lower order path is 1, the LP_RDI_VC3 alarm is
reported.
Attribute
Parameters
None

When the LP_RDI_VC3 alarm is generated, the services at the local station are not affected.
This alarm just indicates that the services at the opposite end are interrupted.
Possible Causes
The LP_RDI_VC3 alarm is an accompanying alarm. When the relevant path of a tributary board
at the opposite station reports the TU_AIS_VC3 or TU_LOP_VC3 alarm, it returns the

LP_RDI_VC3 alarm to the local station, indicating that the TU_AIS_VC3 or TU_LOP_VC3
alarm is received at the opposite station.
Procedure
Step 1 After you clear the TU_AIS_VC3 or TU_LOP_VC3 alarm reported from the relevant path of a
tributary board at the opposite station, the LP_RDI_VC3 alarm is automatically cleared.
----End
Related Information
None
4.91 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating a signal label mismatch in the VC-3 lower order path.
If a board has detected that the signal label mismatch event occurs in the C2 byte, the
LP_SLM_VC3 alarm is reported.
Attribute
Parameters
None

The system is not affected.
Possible Causes
The possible causes of the LP_SLM_VC3 alarm are as follows:
l The type of the received signals does not match that of the signals to be received. That is,
the signal label byte C2 in the lower order path is inconsistent with the received C2 byte.
l The service type is incorrectly configured.
Procedure
Step 1 View the LP_SLM_VC3 alarm on the U2000, and then determine the path number.

Step 2 Check whether the signal label byte in the lower order path of the tributary board at the opposite
station is consistent with that in the lower order path of the line board at the local station. If not,
modify it, and then check whether the LP_SLM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the service configuration of the path is correct. After
modifying the incorrect configuration, check whether the LP_SLM_VC3 alarm is cleared.
Step 4 If the alarm persists, replace the line board at the local station.
Step 5 If the alarm persists, replace the tributary board at the opposite station.
----End
Related Information
None
4.92 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that no payload is equipped in the VC-3 lower order
path. If a board has detected that the signal label in the C2 byte is 0, the LP_UNEQ_VC3 alarm
is reported.
Attribute
Parameters
None

The LP_UNEQ_VC3 alarm indicates that no path services are loaded. If the service
configuration is incorrect, and if the services on the PDH side are not accessed, the services may
be interrupted.
Possible Causes
The possible causes of the LP_UNEQ_VC3 alarm are as follows:
l The service type is incorrectly configured.

l The services on the PDH side are not accessed.

Procedure
Step 1 View the LP_UNEQ_VC3 alarm on the U2000, and then determine the path number.
Step 2 Check whether the service type configuration is correct. After modifying the incorrect
configuration and making sure that the services are correctly accessed on the PDH side, check
whether the LP_UNEQ_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the property configuration of the relevant tributary board is
correct. After you modify the incorrect configuration, the LP_UNEQ_VC3 alarm is
----End
Related Information
None
4.93 LPT_RFI
Description
The LPT_RFI is a remote failure indication alarm of link pass through (LPT). This alarm occurs
when the link pass through detects the failure of the remote port or the LPT service network.
Attribute
Parameters
None

During the data transmission, when the LPT detects the failure of the remote port or the service
network, the link is unavailable and the services are interrupted. Moreover, the link backup is
triggered.
Possible Causes
The possible causes of the LPT_RFI alarm are as follows:
l The remote port fails. For example, there is the LINK_ERR alarm, or the remote port is
disabled.
l The LPT service network is faulty, including the following cases:
– There is a fiber cut.

– 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 LPT_RFI alarm on the U2000 to determine the number of the port on the board that
reports the alarm according to Parameter 1.
Step 2 Based on the confirmed port number, check whether the opposite port is enabled. If yes, check
whether the LPT_RFI alarm is cleared.
Step 3 If the alarm persists, check whether there is the LINK_ERR alarm. If yes, after the LINK_ERR
alarm is cleared, check whether the LPT_RFI alarm is cleared.
Step 4 If the LPT_RFI alarm still persists, check whether the service network fails.
l If a fiber cut occurs, replace the fiber.
l If the bit error threshold-crossing alarms such as BIP_EXC and B3_EXC are detected, first
clear these alarms and then check whether the LPT_RFI alarm is cleared.
l Check whether there are alarms such as VCAT_LOA, VCATA_LOM_VC3,
VCAT_LOM_VC4, and LP_UNEQ_VC3. If yes, first clear these alarms and then check
whether the LPT_RFI alarm is cleared.
----End
Related Information
None
4.94 LSR_COOL_ALM
Description
The LSR_COOL_ALM is an alarm indicating that the cooling current of the laser crosses the
threshold. The alarm is generated when the cooling current of the laser on the WDM side exceeds
the threshold.
Attribute
Parameters
None


When the cooling current of the laser exceeds the threshold, the optical module of the board
works abnormally. As a result, services cannot be transmitted or received normally.
Possible Causes
The possible causes of the LSR_COOL_ALM alarm are as follows:
l The ambient temperature is excessively high.

l The laser is faulty.
Procedure
Step 1 Check whether the ambient temperature is excessively high. If yes, decrease it to a proper value
for the equipment to work well, and then check whether the LSR_COOL_ALM alarm is cleared.
Step 2 If the alarm persists, the laser may be faulty. Replace the board that generates the alarm. For
----End
Related Information
None
4.95 LSR_FORCE_OPEN
Description
The LSR_FORCE_OPEN is an alarm indicating that the laser is forced to be open.
Attribute
Parameters
None

The inconsistent operations may occur.
Possible Causes
The optical interface is set to Disabled but the status of the laser is open.

Procedure
Step 1 Query whether the laser reporting the alarm needs to be used. If that is the case, set the status of
the laser to Enabled on the U2000. If not, shut down the laser on the U2000.
----End
Related Information
None
4.96 LSR_INVALID
Description
The LSR_INVALID is an alarm indicating an invalid optical module. It is generated when the
optical module cannot pass an authentication.
Attribute
Parameters
Parameter 1 Indicates the reason why the optical is invalid. 0x01 indicates that the optical
module has no license. 0x02 indicates that the license verification of the optical
module is incorrect.

The optical interface of the board cannot receive and transmit services. Services are interrupted.
Possible Causes
l The optical module has no license.
l A fault occurs during verifying the license of the optical module.

Procedure
Step 1 Replace the optical module with another one with a correct license, and then re-verify the license.
After successful verification, the alarm is cleared.
----End
Related Information
None
4.97 LTI
Description
The LTI is an alarm indicating the loss of synchronization source. This alarm is generated when
there are clock sources other than internal clock sources listed in the priority table but the board
operates in the holdover or free-run mode.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates which synchronization sources are lost.

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

When the LTI alarm is generated, the NE clock is in an abnormal state. If the NE clock remains
in this abnormal state for a long time, the bit error rate and the pointer justifications may increase
due to the decreased clock qualityk.

Possible Causes
The possible causes of the LTI alarm are as follows:
l Cause 1: There is a fiber cut or a cable cut.

l Cause 2: There is no input from the external clock source.
l Cause 3: The synchronization source is set as non-revertive or is locked.
Procedure
l On the U2000, view the clock sources traced by the NE that reports the LTI alarm. The
clock sources include external clock sources, line clock sources, and tributary clock sources.
l Cause 1: There is a fiber cut or a cable cut. Cause 4: The board is faulty.
1. On the U2000, check whether the R_LOS, R_LOC, or R_LOF alarm occurs on the
relevant line board or tributary board. If yes, take priority to clear the alarm, and then
check whether the LTI alarm is cleared.
2. If the alarm persists, perform cold reset on the relevant line board or tributary board.
After successful cold reset, check whether the LTI alarm is cleared. For details, see
Performing Cold Reset on a Board in the Supporting Tasks.
3. If the alarm persists, replace the relevant line board or tributary board, and then check
whether the LTI alarm is cleared. For details, see Parts Replacement.
4. If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.
l Cause 2: There is no input from the external clock source. Cause 4: The board is faulty.
1. Make sure that the external clock equipment properly transmits signals. Replace the
external clock equipment with a normal one, and then check whether the LTI alarm
is cleared.
3. If the alarm persists, check whether the clock input cable is correctly connected. After
ensuring the correct connection of the clock input cable, check whether the alarm is
cleared.
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.
l Cause 3: The synchronization source is set as non-revertive or locked.
1. On the U2000, check whether the synchronization source is set as non-revertive. If
yes, set the source as revertive. Then, check whether the alarm is cleared.

2. On the U2000, check whether the synchronization source is set as locked. If yes, set
the source as unlocked. Then, check whether the alarm is cleared.
----End
Related Information
None
4.98 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that the module communication is abnormal. The
alarm is generated when the communication of the CPU and other internal modules of the board
is abnormal.
Attribute
Parameters
None

Because the communication between the CPU and the optical module is abnormal, the optical
module cannot be managed by the U2000 and the information about the optical module cannot
be queried.
Possible Causes
l The board is in poor contact with the connector of the optical module.
l The software processing of the related modules of the board is faulty.
Procedure
Step 1 Check the connection between the board and optical module, and re-connect the board and
optical module.
Step 2 Perform cold reset on the faulty board by using the U2000 or remove the faulty board and insert
it again. For details, see the Supporting Tasks.

----End
Related Information
None
4.99 MODULE_ADJUST_FAIL
Description
The MODULE_ADJUST_FAIL is an alarm indicating that adjustment of the optical module
fails.
Attribute
Major Process alarm
Parameters
Parameter 1 Indicates the type of the component in which the alarm is generated. For example,
0x01 indicates that the VOA adjustment fails. 0x02 indicates that the optical
switch adjustment fails.

The adjustment of the VOA or optical switch of the optical module fails, which leads to the
failure of issuing a command.
Possible Causes
l The temperature of the optical module is excessively high.
l The optical module of the board is faulty.

Procedure
Step 1 Check whether the board temperature exceeds the threshold, and whether the TEM_HA and
TEMP_OVER alarm exist. If that is the case, handle the alarms according to the corresponding
Step 2 Deliver the configuration again. If the alarm persists, the adjusted range of the optical module
exceeds the threshold. Perform warm reset on the board. For details, see the Supporting Tasks.
Step 3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts
Replacement.
----End
Related Information
None
4.100 MODULE_COOLCUR_OVER
Description
The MODULE_COOLCUR_OVER is an alarm indicating that the module cooling current
exceeds the threshold. The alarm occurs when the cooling current of the module is higher than
the upper threshold or lower than the lower threshold.
Attribute
Parameters
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates that the upper
threshold is exceeded and 0x02 indicates that the lower threshold is exceeded.

The working performance and the reliability of the module are affected. Generally the QoS is
not affected. However, the QoS is affected if the alarm exists for a long time. The alarm should
be handled in time.

Possible Causes
l The temperature of the optical module is excessively high.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of specific
boards, see the Product Description. If the ambient temperature is excessively high, handle the
alarm according to the handling procedure of the TEMP_OVER alarm.
----End
Related Information
None
4.101 MODULE_TEMP_OVER
Description
The MODULE_TEMP_OVER is an alarm indicating that the module temperature exceeds the
threshold. The alarm is generated when the temperature of the module is higher than the upper
threshold or lower than the lower threshold.
Attribute
Parameters
Parameter 1 Indicates the threshold crossing type. 0x01 indicates that the upper threshold is
exceeded and 0x02 indicates that the lower threshold is exceeded.


Because the temperature of the optical module exceeds the threshold, the working performance
and reliability of the optical module are affected. As a result, services are affected. The alarm
should be handled in time.
Possible Causes
l The ambient temperature of the board is excessively high or excessively low.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of specific
boards, see the Product Description. If the ambient temperature is excessively high or
excessively low, handle the alarm according to the handling procedure of the TEMP_OVER
alarm.
Step 2 If the alarm persists, the board at the local station may be faulty. Perform a cold reset on the
faulty board through the U2000
----End
Related Information
None
4.102 MODULEFILE_UPDATE_FAIL
Description
Failure to update the microprogram and laser parameter table. This alarm is generated when the
in-service upgrade of the microprogram of the optical module and the parameter table on the
U2000 fails.
Attribute
Major Process alarm
Parameters
None


l The upgrade of the microprogram of the optical module fails. As a result, the new
microprogram of the optical module is unavailable and the old one is still used.
l The upgrade of the parameter table of the laser fails.
Possible Causes
The upgrade of the microprogram of the optical module and the parameter table of the laser fails.
Procedure
Step 1 Check whether the upgraded microprogram of the optical module and the parameter table of the
laser are correct.
Step 2 Upgrade the microprogram of the optical module and the parameter table of the laser again.
Step 3 If the alarm persists, replace the faulty optical module or board.
----End
Related Information
None
4.103 MS_REI
Description
The MS_REI is an alarm that indicates that bit errors occur at the remote end of the multiplex
section (MS). When the receive side of the local optical station receives the M1 byte, which
indicates that the number of block bit errors detected by BIP-Nx24 (B2) at the opposite station,
the MS_REI alarm is reported.
Attribute
Warning Communication alarm
Parameters
None

When the MS_REI alarm is generated, the number of B2 bit errors received at the opposite
station is beyond the specified range. The services at the local station are not affected, but the
service quality at the opposite station is degraded.

Possible Causes
The number of B2 bit errors received at the opposite station is beyond the specified range.
Procedure
Step 1 After you clear the B2_EXC or B2_SD alarm that occurs at the opposite station, the MS_REI
alarm is automatically cleared.
----End
Related Information
None
4.104 MS_SNCP_PS
Description
The MS_SNCP_PS is an alarm indicating the MS SNCP protection switching. This alarm occurs
when the MS SNCP protection group actuates switching in which the current channel switches
Reporting side: NA
Attribute
Parameters
None

When the MS SNCP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the MS SNCP protection group might have
faulty services that needs to be restored.
Possible Causes
switching. Such a command makes the current channel of the MS SNCP protection group
l Cause 2: The services of the working channel of the MS SNCP protection group are faulty.
reported.

Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced
switching or manual switching, check whether the external switching operation is necessary,
2. If the external switching operation is unnecessary, issue an external command to switch
the current channel to the working channel, thus clearing the alarm.
Step 2 If the alarm is generated due to the automatic switching of the protection group,
1. Query whether the related boards for configuring the protection group have alarms relevant
to the services, such as B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK,
ODUk_PM_OCI, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
REM_SF, and REM_SD. If yes, handle the alarms by referring to the corresponding alarm
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, the current channel automatically switches to the working channel and the alarm clears.
If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
----End
Related Information
None
4.105 MS_SNCP_STA_INDI
Description
The MS_SNCP_STA_INDI is an alarm indicating the MS SNCP protection switching. This
alarm is reported when the working or protection channel of the protection group is faulty or the
user runs an external switching command.
Reporting side: NA
Attribute
Parameters


l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l When switching is performed in the MS SNCP group, the services may be transiently
interrupted.
l When the alarm is reported, the working or protection channel of the MS SNCP group may
have faulty services that need to be restored.
Possible Causes
l The user issues an external switching command such as forced switching, manual
switching, or locked switching.
l The services of the working or protection channel of the MS SNCP group are faulty.
l The switching is set to WTR State. After the WTR time, the alarm is cleared.
Procedure
switching, manual switching or locked switching, check whether the external switching is
necessary,
1. If the external switching is necessary, ignore the alarm.
2. If the external switching is unnecessary, issue a switching clearing command to clear the
external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
1. Query whether the related boards for configuring the protection group have alarms such as
B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM,
OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI,
OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC, REM_SF, and
REM_SD. If that is the case, handle the alarms according to the corresponding handling
procedure of the alarms to restore the services of the working or protection channel.
that is the case, the services in the working channel automatically switch to the working
channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the
alarm is cleared.

Step 3 On the U2000, query the switching state of the protection group, if the switching is in the WTR
state. This alarm requires no handling. After the WTR time, the alarm is cleared.
----End
Related Information
None
4.106 MS_APS_INDI_EX
Description
The MS_APS_INDI_EX is an extended indication alarm of the MSP switching state. The alarm
occurs when the multiplex section switching causes the switching of services.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching
occurs:

l Linear MSP: The parameter value ranges from 0x01 to 0xFF

(1-255).
l Ring MSP: The parameter value ranges from 0x01 to 0x90
(1-144).
Parameter 4 Indicates the slot ID of the board where the protection switching
occurs.

Name Meaning
Parameter 5 Indicates the number of the optical interface where the protection
switching occurs.

If a fiber cut or another fault occurs after the MS_APS_INDI_EX alarm is generated, the services
are interrupted.
Possible Causes
The possible causes of the MS_APS_INDI_EX alarm are as follows:
l An external switching command is issued.

l There is a fiber cut.
Procedure
Step 1 View the MS_APS_INDI_EX alarm on the U2000. According to the alarm parameters,
determine the slot ID and optical interface number related to the board where the protection
switching occurs.
Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked
switching. If yes, clear the switching, and then the alarm is automatically cleared.
Step 3 If the MSP is in the automatic switching state, do as follows:

1. Make sure that the fibers connected to the service board configured with the MSP are not
cut. Fix the broken fibers and then check whether the alarm is cleared.
2. Make sure that the service board configured with the MSP is not faulty. Replace the relevant
service board and then check whether the alarm is cleared.
3. Make sure that the cross-connect board configured with the MSP is not faulty. Replace the
relevant cross-connect board and then check whether the alarm is cleared.
----End
Related Information
After the services are switched in the 1+1 single-ended non-revertive linear multiplex section,
the services are not automatically switched back to the working channel if the optical channel
is recovered, and the MS_APS_INDI_EX alarm persists. In this case, the services need to be
manually switched from the protection channel to the working channel. The MS_APS_INDI_EX
alarm can be cleared only after successful switching.
4.107 MULTI_RPL_OWNER

Description
The MULTI_RPL_OWNER is an alarm indicating that there is more than one RPL_OWNER
node on the ring.
Attribute
Minor Process alarm
Parameters
None

There is no connection between all the nodes on the ring. If certain services are configured, the
services may be interrupted.
Possible Causes
The ERPS protocol requires that the configuration of every node on a ring should be managed
and one RPL_OWNER should exist on each ring. Therefore, the alarm is generated when more
than one RPL_OWNER node is configured in a ring.
Procedure
Step 1 Check whether the node ID in all the received NR and RB packets is consistent with the ID of
the local node. If yes, proceed with the next step.
Step 2 Start the timer whose time is three times of the transmitting period (15s) of the packets. The
aging of the timer indicates the end of the alarm.
----End
Related Information
None
4.108 NEBD_XC_DIF
Description
Cross-connect matrix data of the NE and board being different. This alarm is generated when
the cross-connection data stored on the system control board is not consistent with that stored
on a board supporting service cross-connections. It is also generated when multiple subracks are
configured in master-slave mode and SDH boards are present in the master or slave subracks.

Attribute
Major Process alarm
Parameters
Parameters 1 Indicates the ID of the subrack where the board is located.
Parameters 2 Indicates the slot ID of the board.
Parameter 3 Indicates the cross-connect type.
Value 0x01 indicates an inconsistency of higher-order cross-connect matrix

data.
l 0x01 indicates an inconsistency of high-order cross-connect matrix data.

l 0x02 indicates an inconsistency of low-order cross-connect matrix data.
l 0x03 indicates presence of SDH boards in the master or slave subracks when
subracks are configured in master-slave mode.

When the value of alarm parameter 3 is not 0x03, services are interrupted during service
grooming or a warm reset on the board; when the value of alarm parameter 3 is 0x03, the system
functions may be abnormal, for example, service grooming may fail or protection switching may
time out.
Possible Causes
l Cause 1: The cross-connection data of the board is incorrect.
l Cause 2: The cross-connection data stored on the board is different from that on the SCC
board.
l Cause 3: Multiple subracks are configured in master-slave mode and SDH boards are
present in the master or slave subracks.
Procedure
l Query the alarm on the U2000. Record the slot ID of the board that reports the alarm.
l Cause 1: The cross-connection data of the board is incorrect.

1. Re-configure the cross-connection data on the U2000. For details, refer to the
Configuration Guide.
l Cause 2: The cross-connection data stored on the board is different from that on the SCC
board.
1. If the alarm persists, perform a warm reset on the board related to service cross-
connections on the U2000.
2. If the alarm persists, perform warm reset on the SCC on the U2000. For details, refer
to "Replacing a Board" of the Supporting Tasks.
l Cause 3: Multiple subracks are configured in master-slave mode and SDH boards are
present in the master or slave subracks.
1. Modify the board configurations in the master or slave subracks to ensure that no SDH
board is present when multiple subracks are configured in master-slave mode.
----End
Related Information
None
4.109 NESF_LOST
Description
The NESF_LOST is an alarm indicating absence of NE software. The alarm occurs when the
NE software on the SCC board does not exist.
Attribute
Parameters
None

If the two sets of NE software do not exist, and thus the board cannot work normally and the
U2000 cannot monitor the NE after the reset or power-off restart of the SCC.
Possible Causes
The NE software is not reloaded after the NE software of the SCC board is erased.

Procedure
Step 1 Reload the NE software of the SCC according to the Version Upgrade Guide.
----End
Related Information
None
4.110 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in installation state and is not
configured. The alarm occurs when the NE is in the initial installation state.
Attribute
Parameters
None

l The U2000 cannot query all configuration information about the NE.
l If the alarm is generated by the NE that is in the normal running state, the data of the
U2000 is initialized. You need to deliver the correct configuration in time.
Possible Causes
l The NE is in the initial installation state.
l The normal configuration is not delivered to the NE after the NE is initialized.
Procedure
Step 1 Deliver the configuration information to the board by using the U2000.
----End

Related Information
None
4.111 NO_BD_PARA
Description
The NO_BD_PARR is an alarm indicating absence of the board parameter table. The alarm
occurs when the board does not have the parameter table.
Attribute
Parameters
None

The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l The correct parameter table is not loaded before delivery.
l The incorrect parameter table file is loaded on site, which overlaps the original file.
l The parameter table file is abnormally lost in the running process.
Procedure
Tasks.
----End
Related Information
None

4.112 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating absence of board software. The alarm occurs when
the board does not have the necessary files, such as loading software, and logic software.
Attribute
Parameters
Parameters 1 The value is always 0x01.
Parameters 2 and 3 Indicates the ID of the lost file. For example,

l 0x00 0x01 indicates that the software of the working board is lost.
l 0x00 0x02 indicates that the software of the protection board is lost.
l 0x00 0x03 indicates that the active FPGA file is lost.
l 0x00 0x04 indicates that the standby FPGA file is lost.
l 0x00 0x05 indicates that the active ini file is lost.
l 0x00 0x06 indicates that the standby ini file is lost.
l 0x00 0x07 indicates that the active large logic file is lost.
l 0x00 0x08 indicates that the standby large logic file is lost.
l 0x00 0x0b to 0x00 0x1f indicates that the parameter table file is lost.
Parameter 4 Indicates the fault type. For example, 0x01 indicates that the file is lost
and 0x02 indicates that the file verification fails.

The alarm affects the system 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.
Possible Causes
l Parts of the software are not loaded to the board.
l The software on the board is abnormally lost in the running process.
l The internal detection of the board is abnormal.
Procedure
Step 1 Reload the corresponding software through the U2000.
Tasks.
----End
Related Information
None
4.113 NO_ELABEL
Description
Electronic label unloaded. This alarm is generated when the electronic label of a board is lost
or not loaded.
Attribute
Warning Equipment alarm
Parameters
Parameter 1 Indicates the carrier type of the electronic label. This parameter has a fixed
value of 0x01.

Parameters 2 and 3 l 0x00 0xfe: indicates that the electronic label of the backplane is lost.
l 0x00 0x01: indicates that the electronic label of the board where the
alarm is generated is lost.

None
Possible Causes
The electronic label is unloaded or lost.
Procedure
Step 1 Check the value of alarm parameters 2 and 3.
1. If the electronic label of the board where the alarm is generated is lost, replace the board.
NOTE
During board replacement, check whether there are bent pins on the backplane. If there are bent pins
on the backplane, handle the bent pins in a timely manner.
2. If the electronic label of the backplane is lost, check whether there are bent pins on the
backplane. If there are bent pins on the backplane, handle the bent pins in a timely manner.
If the problem persists after handling, replace the subrack.
Step 2 If the alarm persists after the preceding operations, contact Huawei engineers to handle the
problem.
----End
Related Information
None
4.114 NODEID_MM
Description
The NODEID_MM is an alarm indicating a mismatch of the MSP node ID. This alarm is
generated when the configured ID of an MSP node on the MS ring mismatches the actual node
ID.
Attribute

Parameters
Name Meaning
Parameter 1 and Parameter 2 Indicates the ID of the MSP group in which the NODEID_MM
alarm is generated.

When the NODEID_MM alarm is generated, the MSP switching fails. If the squelching is
enabled, the squelching function fails.
Possible Causes
The east and west node IDs configured for each node on the MSP ring do not match.
Procedure
Step 1 View the NODEID_MM alarm on the U2000, and then determine the relevant MSP group ID.
Step 2 Check whether the configuration of the MSP data meets the following requirements. If not, re-
configure the MSP according to the following requirements:
l The node IDs configured for any two NEs are not repeated.
l If node A is in the west of its adjacent node B, the local node ID of node A must be the same
as the west node ID of node B, and the local node ID of node B must be the same as the east
node ID of node A.
Step 3 Restart the MSP protocol, and the alarm is cleared automatically.
----End
Related Information
None
4.115 NULL_SEND
Description
The NULL_SEND is an alarm indicating that the NULL signals (the payload is all "0"s) are sent
out. When the NULL mapping status of the board is enabled, the NULL_SEND alarm is
generated, prompting the users that the NULL signals are being sent out.

Attribute
Parameters
None

When this alarm is generated, it indicates that the board that reports the alarm is sending out the
NULL signals and the opposite station receives the NULL signals. Hence, services are
interrupted.
Possible Causes
The NULL Mapping Status parameter of the board is set to Enabled.
Procedure
Step 1 Check the NULL mapping status of the board that reports the alarm. If the NULL mapping status
is enabled, change the value from Enabled to Disabled.
NOTE
If the NULL mapping status needs to be enabled in the actual situation, suppress the alarm and then disable
the NULL mapping status. After that, configure the NULL_SEND alarm to be monitored.
----End
Related Information
None
4.116 OCH_FDI
Description
The OCH_FDI is an alarm indicating a forward defect at the OCh layer. When the OCH_FDI-
P and OCH_FDI-O alarms coexist, this alarm is generated. At the same time, the OCH_FDI-P
and OCH_FDI-O alarms are suppressed.
Attribute

Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise the services
may be interrupted.
Possible Causes
The OCH_FDI-P and OCH_FDI-O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not,
modify the logical fiber connection to make it consistent with the actual fiber connection.
Step 2 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-O, or
OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS,
OTS_TIM, OTS_LOS-O, or OMS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
4.117 OCH_FDI-O
Description
The OCH_FDI-O is an alarm indicating a forward defect (overhead) at the OCh layer. The
OCH_FDI-O signal is inserted to the downstream station when the board at the OTS layer detects
the OTS_LOS-O signal and the alarm is generated when the downstream station receives the
signal.
Attribute
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise, there may
be an impact on the system monitoring and management.

Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The OCh layer receives the FDI-O overhead signal from the OCH layer, when the OMS
layer loses overhead signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
Step 2 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station and
all upstream stations. If yes, clear the OTS_LOS-O alarm by following proper handling
procedures.
----End
Related Information
None
4.118 OCH_FDI-P
Description
The OCH_FDI-P is an alarm indicating a forward defect indication (payload) at the OCh layer.
The OCH_FDI-P signal is inserted to the downstream station when the board at the OMS layer
detects payload LOS signals and the alarm is generated when the downstream station receives
the signals.
Attribute

Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise the services
are interrupted.
Possible Causes

l The OCh layer receives the FDI-O overhead signal from the OCh layer, when the OMS
layer loses payload signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
Step 2 If the alarm persists, check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the
opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm
by following proper handling procedures.
----End
Related Information
None
4.119 OCH_LOS-P
Description
The OCH_LOS-P is an alarm indicating loss of signal (payload) at the OCh layer. When the
OTU detects LOS alarms and there is no OTS_LOS-P, OMS_LOS-P, or OMS_SSF-P alarm in
the at the upper OMS and OTS layers, the OCH_LOS-P alarm is reported.
Attribute

Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise, the services
are interrupted.
Possible Causes
l The board detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.

Procedure
Step 2 Confirm that the fiber connection between the OTU board that reports this alarm and the
DEMUX board is correct.
Step 3 If the alarm persists, check whether the output optical power at the OUT interface of the OTU
board at the opposite or upstream station is normal. If not, clear the alarm according to the
procedure to handle the IN_PWR_HIGH or IN_PWR_LOW alarm to make the output optical
power normal.
Step 4 If the alarm persists, check whether the fiber at the OUT interface of the OTU board at the
opposite or upstream station is disconnected from the MUX board. If yes, correctly connect the
fiber between the two boards.
Step 5 If the alarm persists, check whether the dispersion of the fiber is compliant with the requirement.
For specifications of the dispersion, see the Product Description. If not, connect a suitable
dispersion compensation module according to the Troubleshooting.
Step 6 Check whether there is the R_LOS alarm.

l If yes, clear the alarm according to the handling procedure of R_LOS.
l If not, replace the faulty board according to the Parts Replacement.
----End
Related Information
None
4.120 OCH_OCI
Description
The OCH_OCI is an alarm indicating an open connection at the OCh layer. No optical cross-
connections are configured on the upstream service link, or no logical fiber connection is
configured from the OTU board to the MUX board. In this case, the OCI signal is inserted to
the downstream service link. After receiving the OCI signal, the optical termination node in the
downstream reports the OCH_OCI alarm.
Attribute

Parameters
None


are interrupted.
Possible Causes
l No optical cross-connection for services to the local station is configured at the upstream
station.
Procedure
Step 2 Check whether the services of the optical cross-connections at the upstream station are
configured. If not, re-configure the optical cross-connections to ensure the normal transmission
of the services.
----End
Related Information
None
4.121 OCH_SSF
Description
The OCH_SSF is an alarm indicating that the server signal fails at the OCh layer. When the
OCH_SSF-P and OCH_SSF-O alarms coexist, this alarm is generated. At the same time, the
OCH_SSF-P and OCH_SSF-O alarms are suppressed.
Attribute
Parameters
None

are interrupted.

Possible Causes
l The OTS-LOS alarm at the upper OTS layer or the OMS-LOS alarm at the OMS layer is
generated.
Procedure
Step 2 Check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-
P alarm on the FIU connected to the local board, If yes, clear the OTS_LOS, OTS_TIM,
OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarm by following the proper handling
procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-
O, or OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the
OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarm by following the
proper handling procedures.
----End
Related Information
None
4.122 OCH_SSF-O
Description
The OCH_SSF-O is an alarm indicating that server signal (overhead) fails at the OCh layer.
When the OMS layer detects the lost of the overhead signals, this alarm is generated.
Attribute

Parameters
None


Possible Causes
l The OCh layer receives the SSF-O overhead signal from the OMS layer, when the OTS
layer loses overhead signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
Step 2 Check whether there is the OTS_LOS-O alarm on the FIU connected to the local board. If yes,
clear the OTS_LOS-O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station and
all upstream stations. If yes, clear the OTS_LOS-O alarm by following proper handling
procedure.
----End
Related Information
None
4.123 OCH_SSF-P
Description
The OCH_SSF-P is an alarm indicating that the server signal (payload) fails at the OCh layer.
Attribute

Parameters
None

Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.

The OCh layer receives the SSF-P overhead signal from the OMS layer, when the OMS layer
loses payload signals because of a fiber cut, low optical power, or dispersion. This alarm is
generated.
Procedure
Step 2 Check whether there is the OTS_LOS-P or OMS_LOS-P alarm on the FIU connected to the
local board. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm by following proper handling
procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the
opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm
----End
Related Information
None
4.124 ODU_AIS
Description
The ODU_AIS is an ODU alarm indication.
Attribute
Parameters
None

When the ODU_AIS alarm is generated, the entire ODU path is unavailable.
Possible Causes
The possible causes of the ODU_AIS alarm are as follows:
l Alarms of higher levels exist at the local station, such as R_LOS, FEC_LOF, OTU_LOF,
and OTU_AIS.

l The upstream services are faulty.

l This board is faulty.
Procedure
Step 1 Check on the U2000 whether the alarms of higher levels such as R_LOS, FEC_LOF, OTU_LOF.
and OTU_AIS exist at the local station. If yes, clear these alarms and then check whether the
ODU_AIS alarm is cleared.
Step 2 If the ODU_AIS alarm persists, locate the fault in the upstream direction. Determine the station
(FR station) that is the first to receive the ODU_AIS alarm. Then follow Step 1 to troubleshoot
the FR station.
Step 3 If the ODU_AIS alarm still persists, troubleshoot the upstream station (PR station) of the FR
station. Check whether any alarms of higher levels exist in the receive part of the PR station. If
yes, clear the alarms.
Step 4 If the ODU_AIS alarm still persists, perform a loopback for the service output optical interfaces
of the upstream stations from the FR station. Determine the station (FL station) where the
ODU_AIS or alarms of higher levels occur for the first time after the loopback. Troubleshoot
the FL station as follows:
1. Check the configuration at the FL station. If any fault exists, correct the connection and
configuration.
2. If the ODU_AIS alarm persists, replace the line boards at the FL station.
3. If the ODU_AIS alarm still persists, replace the cross-connect and timing board at the FL
station.
----End
Related Information
None
4.125 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the ODU path are locked.
Attribute
Parameters
None


When the ODU_LCK alarm is generated, the entire ODU path is locked and thus cannot be
configured with services of customers.
Possible Causes
The possible causes of the ODU_LCK alarm are as follows:
l The ODU path test is performed.

Procedure
Step 1 Check whether the ODU path test is performed. If yes, wait until the ODU path test is complete.
Cancel the lockout. Then, check whether the ODU_LCK alarm is cleared.
Step 2 If no ODU path test is performed, cancel the lockout and then check whether the ODU_LCK
alarm is cleared.
Step 3 If the alarm persists, the board hardware may be faulty. In this case, replace the board that reports
the alarm.
----End
Related Information
None
4.126 ODU_OCI
Description
The ODU_OCI is an ODU open connection indication.
Attribute
Parameters
None

When the ODU_OCI alarm is generated, no connection source exists for the entire ODU path.
At this time, the service is unavailable.

Possible Causes
The possible causes of the ODU_OCI alarm are as follows:
l Alarms of higher levels exist at the local station, such as R_LOS, FEC_LOF, OTU_LOF,
and OTU_AIS.
Procedure
Step 1 On the U2000, check whether the alarms of higher levels such as R_LOS, FEC_LOF,
OTU_LOF. and OTU_AIS exist at the local station. If yes, clear these alarms and then check
whether the ODU_OCI alarm is cleared.
Step 2 If the alarm persists, the upstream services may be faulty. Check the upstream equipment. If it
is the OptiX OSN equipment, replace the line boards. If it is another type of equipment, add a
cross-connection to the downstream ODU path that receives the ODU_OCI alarm according to
the corresponding alarm troubleshooting measures.
Step 3 If the alarm still persists, the board at the local station may be faulty. In this case, replace the
board at the local station.
----End
Related Information
None
4.127 ODUk_LOFLOM
Description
The ODUk_LOFLOM is an alarm indicating that the frame alignment signal(FAS) and
multiframe alignment signal(MFAS) are abnormal. The alarm occurs when the information
about the upstream frame header and the downstream frame header does not match
Attribute
Parameters
None


The services on the board are interrupted.
Possible Causes
l The signals transmitted by the corresponding board at the opposite end do not have a frame
structure.
l The input optical power is abnormal.
l The FEC type is incorrectly configured.
l Bit errors in the received signals of the OTU board at the local station are excessive.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If that is the case, locate
the position where the alarm is first generated according to the service route. If no alarm exists
at the opposite end, the local end is the place where the alarm is first generated.
Step 2 Check whether the input optical power of the place where the alarm is first generated is within
the normal range by using the U2000. For optical power specifications of specific boards, see
the Product Description. If the optical power is abnormal, handle the alarm according to the
handling procedure of the IN_PWR_HIGH or IN_PWR_LOW alarm.
Step 3 Query the FEC type of the board set on the U2000 to check whether it is consistent with the FEC
type of the board. For specific error correction types, see the Hardware Description. If they are
not consistent, modify the setting on the U2000 to ensure the consistency.
Step 4 Query the performance value of the BIP8 bit errors in the received signals of the board at the
local station by using the U2000. If the BIP8 bit errors are excessive, handle the alarm according
to the handling procedure of the OTUk_DEG or OTUk_EXC alarm.
Step 5 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical interface connector is well inserted.
l The fiber connector is clean.
l The cable is intact.
If the preceding requirements are not met, clean the fiber connector or replace the fiber. For
details, see the Supporting Tasks.
----End
Related Information
ITU-T G.709

4.128 ODUk_PM_LCK
Description
The ODUk_PM_LCK is an alarm indicating that the ODUk PM signal is locked. The
maintenance signal LCK byte required by the carrier is used to lock the access point signal of
users during testing. It can be generated when the service layer adapts the source and sink. The
alarm is generated when the STAT byte value is "101" during locking.
Attribute
Parameters
None

The services borne by the optical interface would be interrupted.
Possible Causes
The services at the optical interface are interrupted.
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.
Step 2 Query the board information and set LCK Insertion to Disabled if it is Enabled, and the local
station does not insert an LCK signal to the downstream.
----End
Related Information
ITU-T G.709

4.129 ODUk_PM_OCI
Description
The ODUk_PM_OCI is an alarm indicating an ODUk PM open connection. The alarm is
generated when the output interface is not connected to the input interface and the STAT byte
value is "110".
Attribute
Parameters
None

The services at the optical interface are interrupted.
Possible Causes
l The corresponding board at the upstream station has the ODUk_PM_OCI alarm.
l There is loopback on the corresponding board at the opposite station.
l The corresponding board at the opposite station has no or incorrect cross-connection
configuration.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there
is, handle the alarm with higher severity.
Step 2 If the alarm persists, query whether the upstream stations generate the alarm. If that is the case,
locate the station where the alarm is triggered according to the service route.
Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback.
If that is the case, release the loopback.
Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is
configured with incorrect cross-connection or has no cross-connection configuration. If that is
the case, correctly configure the cross-connection.
----End

Related Information
ITU-T G.709
4.130 ODUk_PM_TIM
Description
The ODUk_PM_TIM is an alarm indicating mismatch of the ODUk PM trace identifier. The
alarm occurs during control process when the trace identifier at the opposite end mismatches
that at the local end when the TIM detection is enabled. The system compares the access point
identifiers (API) in the input signals and the expected API.
For the set TIM detection mode, the network architecture can be classified into the following
three types.
l For the point-to-point topology, only the source access point identifiers (SAPI) is compared
for the sink of trail termination.
l For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
l For the multipoint-to-multipoint topology, only the destination access point identifiers
(DAPI) is compared for the sink of trail termination.
Attribute
Parameters
None

If the alarm is generated, the signal quality of the services at the optical interface is degraded.
Hence, the service signals may be unavailable.
Possible Causes
l The networking architecture and the TIM detection mode to be configured are not
consistent.
l The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be
received at the local end.
l The cross-connection configuration is incorrect.

Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for
the local end on the U2000 interface according to networking architecture. If the topology is a
point-to-point topology or point-to-multipoint topology, only the SAPI is compared for the sink
of trail termination. If the topology is multipoint-to-multipoint topology, only the DAPI is
compared for the sink of trail termination.
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be
received at the local end through the U2000. If they are not consistent, query the received TTI
on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to the same
as these of the received TTI.
Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstream
port is correct. If the fiber connection is incorrect, correctly connect the fiber.
Step 4 Check whether the cross-connection configuration is correct. If not, correctly configure the
cross-connection.
----End
Related Information
ITU-T G.709
4.131 ODUk_TCMn_AIS
Description
The ODUk_TCMn_AIS is an ODUk TCMn alarm signal indication. An AIS signal travels
downstream, which indicates that a signal failure is detected in the upstream.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
None

The services at the optical interface are unavailable.

Possible Causes
l Signals input from the client side contain the ODUk_TCMn_AIS signal.
l The corresponding board at the opposite end transmits the ODUk_TCMn_AIS signals.
l The loopback or cross-connection is set at the upstream station, and the FEC type is
incorrectly configured.
Procedure
Step 2 Query whether the alarm is reported from the client side. If that is the case, check the equipment
on the client side.
Step 3 Query whether the ODUk_PM_AIS, R_LOS, or R_LOF alarm exists on the client side of the
OTU board at the opposite end by using the U2000. If the alarm exists, check the equipment at
the opposite end.
Step 4 Query whether the loopback is set on the upstream station by using the U2000. If that is the case,
release the loopback of the upstream station.
Step 5 Check whether the configuration of the cross-connection and FEC type at the upstream station
is correct. If the configuration is incorrect, modify the configuration.
----End
Related Information
ITU-T G.709
4.132 ODUk_TCMn_BDI
Description
The ODUk_TCMn_BDI is an ODUk TCMn backward defect indication. The alarm occurs when
five consecutive BDI bytes in the TCMn overhead field are "1".
Attribute
Parameters
None


Bit errors occur at the downstream station.
Possible Causes
l Signals input from the client side contain the ODUk_TCMn_BDI signal.
l The corresponding OTU board at the downstream station receives the LOF, LOM,
ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or
ODUk_TCMn_SSF alarm.
Procedure
Step 2 Query whether the alarm is reported from the client side or the WDM side.
l If the alarm is reported from the client side, check the equipment on the client side.
l If the alarm is reported from the WDM side, check whether the corresponding OTU board
at the downstream station receives the LOF, LOM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or ODUk_TCMn_SSF
alarm by using the U2000. If yes, handle the corresponding alarm at the downstream station.
----End
Related Information
ITU-T G.709
4.133 ODUk_TCMn_DEG
Description
The ODUk_TCMn_DEG is an alarm indicating that the ODUk TCMn signal is degraded. This
alarm occurs when the signal is degraded or bit errors cross the threshold if the error detection
is in the burst mode. This alarm occurs when the signal is degraded or bit errors cross the
threshold if the error detection is in the Poisson mode.
Attribute

Parameters
None

If the alarm is generated, the services at the optical interface generate bit errors, which make the
service signals unavailable.
Possible Causes
l The optical interface that reports the alarm is faulty.
l The optical interface at the opposite end is faulty.
Procedure
Step 1 Use the U2000 to browse alarms of the entire network to determine the slot ID, interface ID,
and channel ID of the board that generates this alarm.
Step 2 Locate the point that first generates the ODUk_TCMn_DEG alarm according to the service
route.
Step 3 Step 3 Check whether the input optical power of the place where the alarm is first generated is
within the normal range by using the U2000. If not, handle it according to the handling
procedures of the IN_PWR_HIGH and IN_PWR_LOW alarms. For optical power specifications
of specific boards, see the Product Description.
Step 5 If the alarm persists, the optical interface on the board at the local end may be faulty. Replace
the faulty board. For details, see the Parts Replacement.
Step 6 If the alarm persists, the optical interface on the OTU board at the opposite end may be faulty.
Replace the faulty OTU board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709

4.134 ODUk_TCMn_EXC
Description
The ODUk_TCMn_EXC is an alarm indicating that the ODUk TCMn section BIP8 errors cross
the threshold. This alarm occurs when the bit errors cross the threshold if the error detection is
in the Poisson mode.
Attribute
Parameters
None

Possible Causes
l The attenuation of the received signals is excessively large, and the fiber of the transmission
line is abnormal.
Procedure
Step 1 Check whether the received optical power of the interface is within the normal range by using
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding interface
on the upstream board is within the normal range by using the U2000. For optical power
specifications of specific boards, see the Product Description. If the transmit optical power of
the board at the upstream station is excessively low, clear the alarm according to the handling
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station by using
the U2000. Loop back the transmit optical interface and receive optical interface on the WDM

side of the OTU board at the upstream station. If the bit errors exist, clear the bit error fault of
the upstream station.
Replacement.
----End
Related Information
ITU-T G.709
4.135 ODUk_TCMn_LCK
Description
The ODUk_TCMn_LCK is an alarm indicating that the ODUk TCMn signal is locked. The
maintenance signal LCK byte required by the carrier is used to lock the access point signal of
users during testing. It can be generated when the service layer adapts the source and sink. The
alarm is generated when the STAT byte value is "101" during locking.
Attribute
Parameters
None

Possible Causes
The signals are locked for the test of current line signals.
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.

Step 2 Set the LCK type to Disabled if it is Enabled.
----End
Related Information
ITU-T G.709
4.136 ODUk_TCMn_LTC
Description
The ODUk_TCMn_LTC is an alarm indicating loss of ODUk TCMn serial connection. The
TCM provides the connection monitoring function of the ODUk to cater for different application
scenarios. For example, the TCM from optical NNI to optical NNI monitors the connection of
the ODUk through the carrier network. The alarm occurs when the serial connection is lost and
the STAT byte is "000".
Attribute
Parameters
None

The TCM is not available.
Possible Causes
The TCM at the opposite end is not set as enabled, and thus there is no TCM source.
Procedure
Step 1 On the U2000, find the position that generates this alarm first according to the network topology.
Step 2 Query whether the source configuration of this position and its opposite position is correct. If
not, modify the configuration
----End

Related Information
ITU-T G.709
4.137 ODUk_TCMn_OCI
Description
The ODUk_TCMn_OCI is an ODUk TCMn open connection indication. The alarm occurs when
the output interface is not connected to the input interface and the STAT byte is "110".
Attribute
Parameters
None

Possible Causes
l The corresponding board at the upstream station has the ODUk_TCMn_OCI alarm.
l There is loopback on the corresponding board at the opposite station.
l The corresponding board at the opposite station has no or incorrect cross-connection
configuration.
Procedure
Step 2 If the alarm persists, check whether the upstream station has this alarm. If yes, locate the station
that triggers this alarm according to the service route.
Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback.
If yes, release the loopback.
Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is
configured with incorrect or no cross-connection. If yes, configure the correct cross-connection.
----End

Related Information
ITU-T G.709
4.138 ODUk_TCMn_SSF
Description
The ODUk_TCMn_SSF is an alarm indicating that the ODUk TCMn server signal fails.
Attribute
Parameters
None

Possible Causes
l The ODUk_TCMn_AIS or ODUk_LOFLOM alarm is generated on the line.
l The OTUk_TIM alarm is generated on the line and the OTUk_TIM follow-up response is
set to be enabled.
l The OTUk_SSF alarm is generated.
Procedure
Step 1 Check along the service signal flow to locate the station that first generates the SSF alarm.
1. Check whether the ODUk_PM_AIS or ODUk_LOFLOM alarm occurs at the station. If
yes, clear the alarm according to the corresponding handling procedure.
2. Check whether the OTUk_TIM alarm occurs at the station. If yes, clear the alarm according
to the alarm handling procedure.
Step 2 If the alarm persists, check whether the OTUk_SSF alarm occurs on the line or not. If yes, clear
the alarm according to the alarm handling procedure.
----End

Related Information
None
4.139 ODUk_TCMn_TIM
Description
The ODUk_TCMn_TIM is an alarm indicating ODUk TCMn trace identifier mismatch. This
alarm occurs during control process when the trail trace identifier at the opposite end mismatches
that at the local end when the TIM detection is enabled. The system compares the access point
identifiers (API) in the input signals and the expected API.
three types:
termination.
Attribute
Parameters
None

If the alarm is generated, the quality of the signals at the optical interface is degraded. Hence,
the service signals may be unavailable.
Possible Causes
consistent.
l The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be
received at the local end.

Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for
the local end on the U2000 interface according to the networking architecture. If the topology
is point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail
termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the sink
of trail termination.
Step 2 Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with
that to be received at the local end through the U2000. If they are not consistent, query the
received TTI on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local
end to the same as these of the received TTI.
cross-connection.
----End
Related Information
ITU-T G.709
4.140 ODU_SNCP_STA_INDI
Description
Status indication of an ODUk SNCP protection group. This alarm is generated on the board of
working channel when the working or protection channel of the protection group is faulty or the
user runs an external switching command, or the Status is WTR State.
Attribute
Parameters


l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l When switching is performed to the ODU SNCP group, the services would be transiently
interrupted.
l When the alarm is reported, the working or protection channel of the ODU SNCP group
might have faulty services that need to be restored.
Possible Causes
l Cause 2: The services of the working channel or the protection channel of the ODU SNCP
group are faulty.
Procedure
l Cause 1: A user issues an external switching command.
external switching.
l Cause 2: The services of the working channel or the protection channel of the ODU SNCP
group are faulty.
1. Query whether the related boards for configuring the protection group have the alarms,
for example, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM,
OTUk_AIS, OTUk_TIM, ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_LTC,
ODUk_TCMn_TIM, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, ODUk_TCMn_DEG, ODUk_TCMn_EXC. If these boards
have these alarms, handle the alarms by referring to the corresponding handling
procedure of the alarms to restore the services of the working channel or the protection
channel.

Revertive. If the attribute is Revertive, the working channel would automatically
switch to the working channel. The alarm would clear. If the attribute is Non-
Revertive, set it to Revertive and the alarm would lear.
1. This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
None
4.141 ODUKSP_PS
Description
The ODUKSP_PS is an alarm indicating the ODUk SP protection switching. This alarm occurs
when the ODUk SP protection group actuates switching in which the current channel switches
Attribute
Parameters
None

When the ODUk SP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the ODUk SP protection group might have
Possible Causes
switching. Such a command makes the current channel of the ODUk SP protection group
l Cause 2: The services of the working channel of the ODUk SP protection group are faulty.
reported.

Procedure
to the services, such as R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM,
OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI, ODUk_TCMn_LCK,
ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG and ODUk_TCMn_EXC. If yes,
handle the alarms by referring to the corresponding alarm handling procedures.
----End
Related Information
None
4.142 ODUKSP_STA_INDI
Description
The ODUKSP_STA_INDI is an alarm indicating the state of the ODUk SPRing protection
group. This alarm is reported when the working or protection channel of the protection group is
faulty or the user runs an external switching command.
Attribute
Parameters

Parameters 1 Indicate the west switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR
Parameters 1 Indicate the east switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR

l When the ODUk SP protection switching is performed, the services are transiently
interrupted.
l When the alarm is reported, the working or protection channel in the ODUk SP protection
group may contain faulty services. In this case, you need to remove the fault to restore the
services.

Possible Causes
l The user issues an external switching command such as forced switching, manual
l The services of the working or protection channel of the ODUk SP protection group are
faulty.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
switching, manual switching, or locked switching, check whether the external switching is
necessary.
external switching.
1. Check whether service related alarms such as R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG or
ODUk_TCMn_EXC occur on the corresponding boards in the protection group. If yes,
clear the alarm according to the corresponding alarm handling procedures to restore the
services of the working channel or protection channel.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in the
WTR state. This alarm requires no handling. After the WTR time, the alarm is cleared.
----End
Related Information
None
4.143 OH_LOOP
Description
The OH_LOOP is an alarm of overhead bus loopback. This alarm occurs when the overhead
bus of a line board is looped back.
Attribute
Minor Security alarm

Parameters
Name Meaning
Parameter 1 l 0x01: indicates a loopback on the line board.

l 0x02: indicates a loopback on the opposite board.
l 0x03: indicates a loopback on the SCC board.

When the OH_LOOP alarm occurs, the overhead signal is looped back. The services are not
affected but the ECC communication is interrupted.
Possible Causes
The overhead bus of the line board is looped back.
Procedure
Step 1 After the loopback is released, the OH_LOOP alarm is automatically cleared.
----End
Related Information
None
4.144 OLP_PS
Description
The OLP_PS is an alarm indicating the optical line protection switching. This alarm occurs when
the optical line protection group actuates switching in which the current channel switches to the
protection channel from the working channel.
Attribute
Parameters
None


When the optical line protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the optical line protection group might have
Possible Causes
switching. Such a command makes the current channel of the optical line protection group
l Cause 2: The services of the working channel of the optical line protection group are faulty.
reported.
l Cause 3: The difference between the optical power on the working channel and that on the
protection channel exceeds the threshold.
Procedure
1. Query whether the input optical power of the working channel is within the normal range
on the U2000. For optical power specifications of specific boards, see the Product
Description. If the optical power is not within the normal range, handle the alarm according
to the handling procedure of the IN_PWR_LOW alarm to make the input optical power of
the working or protection channel be within the normal range.
Step 3 If the alarm persists, check whether the POWER_DIFF_OVER alarm exist. If that is the case,
handle the alarms according to the corresponding handling procedures.
----End
Related Information
None

4.145 OLP_STA_INDI
Description
The OLP_STA_INDI is an alarm indicating the optical line protection switching. This alarm is
reported when the working or protection channel of the protection group is faulty or the user
runs an external switching command.
Attribute
Parameters

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l When protection switching is performed on the optical line, the services are transiently
interrupted.
l When the alarm is reported, the working or protection channel of the optical line protection
group may have faulty services that need to be restored.
Possible Causes
l The user issues an external switching command such as forced switching, manual switching
or locked switching.
l The services of the working channel or protection channel of the optical line protection
group are faulty.

Procedure
necessary.
external switching.
Step 2 If the alarm is generated due to the fault of the working channel or protection channel of the
protection group, do as follows:
1. Query whether the input optical power of the working or protection channel is within the
normal range on the U2000. For optical power specifications of specific boards, see the
Product Description. If the optical power is not within the normal range, handle the alarm
according to the handling procedure of the IN_PWR_LOW alarm to make the input optical
power of the working or protection channel be within the normal range.
that is the case, the services in the working channel automatically switch to the working
channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the
alarm is cleared.
----End
Related Information
None
4.146 OMS_BDI
Description
The OMS_BDI is the backward defect indication at the OMS layer. When the OMS_BDI-P and
OMS_BDI-O alarms coexist, this alarm is generated. At the same time, the OMS_BDI-P and
OMS_BDI-O alarms are suppressed.
Attribute

Parameters
None


The incorrect logical fiber connection does not affect services. Otherwise, the services of the
system are interrupted.
Possible Causes
The OMS_BDI-P and OMS_BDI-O alarms coexist.
Procedure
Step 2 Check whether there is the OTS_LOS, OTS_LOS-O, OTS_TIM, or OMS_LOS-P alarm at the
opposite station and all downstream stations. If yes, clear the OTS_LOS, OTS_LOS-O,
OTS_TIM, or OMS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
4.147 OMS_BDI-O
Description
The OMS_BDI-O is a backward defect indication (overhead) at the OMS layer. The OMS_BDI-
O signal is inserted back to the upstream station when the downstream station receives no
overhead signals from the upstream station and the OTS_LOS_O alarm is generated from the
downstream station.
Attribute

Parameters
None


Possible Causes
l The downstream station inserts the BDI-O overhead signal back to the OMS layer of the
local station, when the downstream station detects no overhead signals because of a fiber
cut, low optical power, or dispersion. This alarm is generated when the local station receives
the BDI-O overhead signal.
l The local station sends no overhead signals.
Procedure
Step 2 Check whether there is the OTS_LOS-O alarm at the opposite station and all downstream
stations. If yes, clear the OTS_LOS-O alarm by following proper handling procedures.
----End
Related Information
None
4.148 OMS_BDI-P
Description
The OMS_BDI-P is a backward defect indication (payload) at the OMS layer. The OMS_BDI-
P signal is inserted back to the upstream station when the downstream station receives no payload
signals from the upstream station.
Attribute
Parameters
None

are interrupted.
Possible Causes
The downstream station inserts the BDI-P overhead signal back to the OMS layer of the local
station, when the downstream station detects no payload signals because of a fiber cut, low
optical power, or dispersion. This alarm is generated when the local station receives the BDI-P
overhead signal.

Procedure
Step 2 Check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the opposite station and all
downstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm by following proper
----End
Related Information
None
4.149 OMS_FDI-O
Description
The OMS_FDI-O is a forward defect indication (overhead) at the OMS layer. The OMS_FDI-
O signal is inserted to the downstream station when the board at the OTS layer detects no
overhead signals and cannot send overhead signals to the downstream station.
Attribute
Parameters
None

Possible Causes
l The FDI-O overhead signal is inserted to the OMS layer of the downstream station, when
the local station detects no overhead signals because of a fiber cut, low optical power, or
dispersion. This alarm is generated when the downstream station receives the FDI-O
overhead signal.
Procedure

Step 2 Check whether there is the OTS_LOS-O alarm at all upstream stations. If yes, clear the
OTS_LOS-O alarm by following proper handling procedures.
----End
Related Information
None
4.150 OMS_FDI-P
Description
The OMS_FDI-P is a forward defect indication (payload) at the OMS layer. The OMS_FDI-P
signal is inserted to the downstream station when the board at the OTS layer detects no payload
signals and cannot send payload signals to the downstream station.
Attribute
Parameters
None

Possible Causes
The FDI-P signal is inserted to the OMS layer of the downstream station, when the local station
detects no payload signals because of a fiber cut, low optical power, or dispersion. This alarm
is generated when the downstream station receives the FDI-P signal.
Procedure
Step 2 Check whether there is the OTS_LOS-P alarms at the opposite station and all upstream stations.
If yes, clear the OTS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None

4.151 OMS_LOS-P
Description
The OMS_LOS-P is an alarm indicating loss of signal (payload) at the OMS layer. If there is
no OTS_LOS-P alarm at the OTS layer, the OMS_LOS-P alarm is reported when the OTU board
detects the LOS alarm.
Attribute

Parameters
None

are interrupted.
Possible Causes
The OMS layer detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.
Procedure
Step 1 Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection.
If not, modify the logical fiber connection to make it consistent with the actual fiber connection.
Step 2 Confirm that the actual fiber connection between the board that reports this alarm and the FIU
board is correct.
Step 3 Check whether there is the OTS_LOS alarm on the FIU. If yes, clear the alarm according to the
procedure to handle OTS_LOS.
Step 4 Check whether there is MUT_LOS alarm.

l If yes, clear the alarm according to the procedure to handle MUT_LOS.
l If not, replace the faulty board according to the Parts Replacement.
----End
Related Information
None

4.152 OMS_SSF
Description
The OMS_SSF is an alarm indicating that the server signal fails at the OMS layer. When the
OMS_SSF-P and OMS_SSF-O alarms coexist, this alarm is generated. At the same time, the
OMS_SSF-P and OMS_SSF-O alarms are suppressed.
Attribute

Parameters
None

are interrupted.
Possible Causes
The OMS_SSF-P and OMS_SSF-O alarms coexist.
Procedure
Step 2 Check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, or OTS_LOS-O alarm on the
FIU connected to the local board. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P, or
OTS_LOS-O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, or
OTS_LOS-O alarm at all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-
P, or OTS_LOS-O alarms by following proper handling procedures.
----End
Related Information
None

4.153 OMS_SSF-O
Description
The OMS_SSF-O is an alarm indicating that the server signal (overhead) fails at the OMS layer.
When the OTS layer detects the failure of the overhead signals, or receives the OMS_FDI-O
signal from the upstream station, this alarm is generated.
Attribute
Parameters
None

Possible Causes
l Because of a fiber cut, low optical power, dispersion, or failure in overhead signals at the
upstream OTS layer, the OTS layer of the board loses the overhead signals and the overhead
signals received by the OMS layer from the OTS layer are invalid. Hence, this alarm is
reported.
Procedure
Step 2 Check whether there is the OTS_LOS-O or OOS_LOST alarm on the FIU connected to the local
board. If yes, clear the OTS_LOS-O, or OOS_LOST alarm by following proper handling
procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS-O, or OOS_LOST alarm at the
opposite station and all upstream stations. If yes, clear the OTS_LOS-O, or OOS_LOST alarm
----End
Related Information
None

4.154 OMS_SSF-P
Description
The OMS_SSF-P is an alarm indicating that the server signal fails (payload) at the OMS layer.
When the OTS layer detects the failure of the payload signals or receives the OMS_FDI-P signal
from the upstream station, this alarm is generated.
Attribute

Parameters
None

are interrupted.
Possible Causes
When the service-layer payload signals received by the OMS layer are invalid and the OTS layer
can not detect any signals because of a fiber cut, low optical power, or dispersion, this alarm is
generated.
Procedure
Step 2 Check whether there is OTS_LOS-P alarm on the FIU connected to the local board. If yes, clear
the OTS_LOS-P alarm by following proper handling procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS-P alarm at the opposite station and
all upstream stations. If yes, clear the OTS_LOS-P alarms by following proper handling
procedures.
----End
Related Information
None

4.155 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm occurs
when the phase-locked loop on the clock board becomes faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the failed phase-locked loop.
l 0x01: first 2M phase-locked loop

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

When the OOL alarm is generated, the phase-locked loop cannot lock on the input signals, and
as a result the output clock signals are affected. This alarm may lower the quality of services or
interrupt the services.
Possible Causes
Cause 1: The board hardware of the phase-locked loop is damaged.
Procedure
l Cause 1: The board hardware of the phase-locked loop is damaged.
1. Perform cold reset on the board. Then, check whether the alarm is cleared. For details,
see Performing Cold Reset of a Board in the Supporting Tasks.
----End

Related Information
None
4.156 OOS_LOST
Description
The OOS_LOST is an alarm indicating loss of OTM overhead signal (OOS). When the local
station receives no overhead signals in ten consecutive seconds and there is no OTS_LOS-O
alarm, this alarm is generated.
Attribute

Parameters
None

be an impact on the optical-layer overhead.
Possible Causes
l The local station receives no overhead signals in ten consecutive seconds because the
opposite station sends no overhead signals.
Procedure
Step 2 Check whether the opposite station supports the OLS function.
l If not, this alarm does not need to be handled.
l If yes, make sure that the opposite station sends the correct overhead signals.
----End
Related Information
None

4.157 OPA_FAIL_INDI
Description
The OPA_FAIL_INDI is an alarm indicating that the automatic power adjustment of the optical
cross-connection fails. The alarm occurs if the calculated attenuation exceeds the settable range
of the board when the optical power is automatically adjusted.
Attribute
Major Process alarm
Parameters
Parameter 1 Indicates the ID of the wavelength of the optical cross-connection.

When the alarm is reported, the attenuation of the board is not adjusted. For new services, the
services may be unavailable. For existing services, the QoS cannot be improved.
Possible Causes
The rated optical power of the optical amplifier board is excessively high or excessively low.
Procedure
Step 1 Change the power adjustment mode of the optical cross-connection to manual adjustment on the
U2000. Query whether the attenuation of the board is excessively high or excessively low. If
that is the case, manually adjust the optical power on the line.
Step 2 If the alarm persists, adjust the rated optical power of the input or output optical interface.
----End
Related Information
None

4.158 OPU1_MSIM
Description
The OPU1_MSIM is an alarm indicating the OPU1 multiplex structure identifier mismatch.
Attribute
Parameters
None

The services may be unavailable.
Possible Causes
The board does not support the multiplex structure for service transmission of the board on the
source NE.
Procedure
Step 1 Check whether the multiplex structure of the local board mismatches with that of the
corresponding board on the source NE. For the multiplex structure of the board, see the
Hardware Description.
Step 2 If the multiplex structures of the two boards do not match, replace one of them with a matched
----End
Related Information
ITU-T G.709
4.159 OPU1_VCAT_SQM
Description
The OPU1_VCAT_SQM is an alarm indicating the OPU1 sequence indicator mismatch. The
alarm is generated when the received OPU1 sequence indicator (SQ) value is not consistent with
the expected value. For example, the SQ values of channels 1-4 on the system side are 0-3

respectively. When the services from channel 1 are connected to channel 2 on the system side
of the opposite TDX, the received SQ value is 0 and the SQ value to be received is 1. The values
mismatch, and then the alarm is generated.
Attribute
Parameters
None

When an OPU1_VCAT_SQM is detected, the value of received SQ is not consistent with the
value of SQ to be received. Then, the services are interrupted.
Possible Causes
The cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the cross-connection sequence of the virtual cascading OPU1 at the local end
mismatches that at the opposite end. If not, re-configure the virtual cascading OPU1s at the local
end.
----End
Related Information
Each channel on the WDM side has an SQ value. The SQ values of optical interfaces are in an
ascending order. Compare the SQ value of the frame in each WDM-side optical interface with
that of its previous frame. If mismatch is found, the SQ mismatch alarm of the optical interface
is reported. If the SQ values of two optical interfaces are the same, the board also reports the SQ
mismatch alarm.
4.160 OPU1_VCAT_VcPLM
Description
The OPU1_VCAT_VcPLM is an alarm indicating mismatch of the OPU1 virtual concatenation
payload. The alarm is generated when the type of the OPU1 virtual concatenation payload
received mismatches the expected type. Each service type corresponds to a VcPt value. For
10GE LAN, the value is 5. For STM-64, the value is 3. When two TDXs interconnected with
each other, the alarm is generated if the service types at the two ends mismatch.

Attribute
Parameters
None

Possible Causes
l Service type configuration is incorrect.
l Cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the VcPt value to be received at the local end is consistent with the received VcPt
value. If not, check whether the service type at the opposite end is consistent with that at the
local end. Re-configure the cross-connect service of the interconnected TDX board.
Step 2 If the alarm persists, check whether the VcPt value of the services transmitted from the opposite
end is consistent with the VcPt value to be received at the local end. If not, re-configure the
cross-connect service at the opposite end.
----End
Related Information
ITU-T G.709
4.161 OPU2_MSIM
Description
The OPU2_MSIM is an alarm indicating that mismatch of the OPU2 multiplex structure
indicator.
Attribute

Parameters
None

Possibly the services are not available.
Possible Causes
source NE.
Procedure
corresponding board of the source NE. For the multiplex structure of the board, see the Hardware
Description.
----End
Related Information
ITU-T G.709
4.162 OPU3_MSIM
Description
The OPU3_MSIM is an alarm indicating mismatch of the OPU3 multiplex structure.
Attribute
Parameters
None


Possible Causes
source NE.
Procedure
corresponding board of the source NE. For the multiplex structure of the board, see the Hardware
Description.
----End
Related Information
ITU-T G.709
4.163 OPUk_PLM
Description
The OPUk_PLM is an alarm indicating OPUk payload mismatch. The type of received payload
mismatches the expected payload type defined in the adaptation function.
k indicates the level of rate and its value is 0, 1, 2, or 3.
Attribute
Parameters
None

Possible Causes
The type of the payload in the data on the WDM side of the interconnected board mismatches.

Procedure
Step 1 Use the U2000 to query whether the PT byte value to be received at the OPU of the local board
is consistent with that of the received PT bytes. If they are not consistent, modify the PT of the
local NE to be consistent.
Step 2 Check whether the WDM-side fiber connection is correct according to the engineering fiber
connection diagram. If the fiber connection is incorrect, correctly connect the fiber according to
the engineering fiber connection diagram.
Step 3 Check whether the payload types of the local board matches that of the corresponding opposite
board. If not, replace the opposite board with a matching one. For details, see the Parts
Replacement.
----End
Related Information
ITU-T G.709
4.164 OSC_RDI
Description
The OSC_RDI is an alarm indicating a remote defect. The alarm occurs when the opposite station
returns the RDI alarm to the local station after receiving an R_LOF alarm.
Attribute
Parameters
None

The communication between the two stations is abnormal.
Possible Causes
l The opposite station returns the RDI alarm to the local station after receiving the R_LOF
signals.
l The optical fiber is damaged.

Procedure
Step 1 Query whether the opposite station has the R_LOF alarm. If that is the case, take it as the R_LOF
alarm for troubleshooting.
Step 2 If the alarm persists, check whether the fiber between the two stations is damaged. If that is the
case, repair the fiber.
----End
Related Information
None
4.165 OTS_BDI
Description
The OTS_BDI is an alarm indicating a backward defect at the OTS layer. When the OTS_BDI-
P and OTS_BDI-O alarms coexist, this alarm is generated. At the same time, the OTS_BDI-P
and OTS_BDI-O alarms are suppressed.
Attribute
Parameters
None

are interrupted.
Possible Causes
l The upstream station reports the OTS_LOS alarm, and the downstream station inserts it
back to the local station.
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber
connection. If not, modify the logical fiber connection to make it consistent with the actual fiber
connection.

Step 2 Check whether there is the OTS_TIM or OTS_LOS alarm at the opposite station. If yes, clear
the OTS_TIM or OTS_LOS alarm by following proper handling procedures.
Step 3 If the alarm persists, check and make sure that fibers connected to the receive interfaces on the
local FIU are correct and there is no fiber disconnection.
----End
Related Information
None
4.166 OTS_BDI-O
Description
The OTS_BDI-O is an alarm indicating a backward defect (overhead) at the OTS layer. After
receiving the OTS_BDI-O signal inserted by the upstream station to the downstream, the local
station reports the OTS_BDI-O alarm.
Attribute
Parameters
None

Possible Causes
The opposite station inserts the BDI-O signal back to the local station, when detecting no
overhead signals because of a fiber cut, low optical power, or dispersion. This alarm is generated
when the local station receives the BDI-O overhead signal.
Procedure
Step 2 If the alarm persists, check and make sure that the fiber connection of the "RM" interface on the
local FIU is correct and there is no fiber disconnection.

Step 3 Check whether the opposite FIU reports the OTS_LOS-O alarm. If yes, handle the alarm by
following proper handling procedures.
----End
Related Information
None
4.167 OTS_BDI-P
Description
The OTS_BDI-P is an alarm indicating a backward defect (payload) at the OTS layer. After
receiving the OTS_BDI-P signal inserted back to the local station by the downstream station,
the local station repots this alarm.
Attribute

Parameters
None

are interrupted.
Possible Causes
The opposite station inserts the BDI-P signal back to the local station, when detecting no payload
signal because of a fiber cut, low optical power, or dispersion. This alarm is generated when the
local station receives the BDI-P signal.
Procedure
connection.
Step 2 If the alarm persists, check and make sure that fibers connected to the receive interfaces of the
local PIU are correct and there is no fiber disconnection.

Step 3 Check whether there is the OTS_LOS-P alarm at the opposite station of the FIU. If yes, clear
the OTS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
4.168 OTS_LOS-O
Description
The OTS_LOS-O is an alarm indicating loss of signals (overhead) at the OTS layer. When the
OSC board connected to the "TM" interface of the FIU detects the LOS signals, this alarm is
generated.
Attribute
Parameters
None

Possible Causes
This alarm is generated when the OTS layer of the receive end detects no overhead signal because
of a fiber cut, low optical power, or dispersion.
Procedure
connection.
Step 2 If the alarm persists, check and make sure that the fiber connection between the "TM" interface
of the local FIU and the OSC board is correct and there is no fiber disconnection.
Step 3 If the alarm persists, check and make sure that the fiber connection between the "RM" interface
of the opposite FIU and the OSC board is correct and there is no fiber disconnection.

Step 4 If the alarm persists, check whether the laser of the OSC at the opposite station is "Open". If not,
open the laser of the OSC.
----End
Related Information
None
4.169 OTS_LOS-P
Description
The OTS_LOS-P is an alarm indicating loss of signal (payload) at the OTS layer. This alarm is
generated when the amplifier or other boards connected to the transmit interface of the FIU
detects the LOS signals.
Attribute

Parameters
None

are interrupted.
Possible Causes
This alarm is generated when the OTS layer of the receive end detects no payload signal because
of a fiber cut, low optical power, or dispersion.
Procedure
connection.
Step 2 If the alarm persists, check and make sure that fibers connected to the interfaces of the local
station are correct and there is no fiber disconnection.
----End

Related Information
None
4.170 OTS_TIM
Description
The OTS_TIM is an alarm indicating mismatch of the trail trace identifier at the OTS layer.
When the API of the received TTI at the OTS layer is not consistent with the API to be received,
this alarm is generated.
Attribute
Parameters
None

If the configuration of the TTI is incorrect, there has no influence to the services. If the fiber
connection is incorrect, the services may be interrupted.
Possible Causes
l The TTI transmitted at the upstream station is not consistent with the TTI to be received at
the local station.
l The fiber actual connection is incorrect.
Procedure
Step 1 Check whether the TTI transmitted at the transmit end (upstream station) is consistent with the
TTI to be received at the local end. If not, configure the TTI at the upstream station again.
Step 2 Check whether the fiber connection between the OSC and the "RM" or "TM" interface of the
FIU is compliant with the network regulation. If not, connect the fibers again.
----End
Related Information
For details of the API and TTI, see ITU-T G.709.
4.171 OTU_AIS

Description
The OTU_AIS an OTU alarm indication.
Attribute
Parameters
None

When the OTU-AIS alarm is generated, no connection source exists for the entire ODU path.
At this time, the service is unavailable.
Possible Causes
The possible causes of the OTU_AIS alarm are as follows:
l Alarms of higher levels such as R_LOS and FEC_LOF exist at the local station.
Procedure
Step 1 On the U2000, check whether the alarms of higher levels such as R_LOS and FEC_LOF exist
at the local station. If yes, clear these alarms and then check whether the OTU_AIS alarm is
cleared.
Step 2 If the OTU_AIS alarm persists, locate the fault in the upstream direction. Determine the station
(marked as an FR station) which is the first to receive the OTU_AIS alarm. Then follow Step 1
to troubleshoot the FR station.
Step 3 If the OTU_AIS alarm still persists, troubleshoot the upstream station (marked as a PR station)
of the FR station. Check whether any alarms of higher levels exist in the receive part of the PR
station. If yes, clear the alarms.
Step 4 If the OTU_AIS alarm persists, use fibers to perform loopbacks for the service output parts of
the upstream stations from the FR station. Determine the station (marked as an FL station) where
the OTU_AIS alarm is generated for the first time after the fiber loopbacks. Perform the
following steps to troubleshoot the FL station. Skip this step if the services cannot be interrupted.
In this case, directly replace the boards in the receive part of the FR station and the boards in
the service output part of the PR station.
1. Check the configuration at the FL station. If any fault exists, correct the connection and
configuration.
2. If the OTU_AIS alarm persists, replace the line boards at the FL station.

3. If the OTU_AIS alarm still persists, replace the cross-connect and timing board at the FL
station.
----End
Related Information
None
4.172 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame alignment signal(FAS) is abnormal.
Attribute
Parameters
None

When the OTU_LOF alarm is generated, the FEC function is disabled. At the same time, the
Possible Causes
The possible causes of the OTU_LOF alarm are as follows:
l The fiber or the optical power is faulty.

l The services that are transmitted from the opposite station are faulty.
Procedure
Step 1 View the OTU_LOF alarm on the U2000 to determine the relevant board.
excessively low, clean the fiber header and the connector. If the receive optical power is
excessively high, provide more optical attenuators. After making sure that the receive optical
power is proper, check whether the OTU_LOF alarm is cleared.
Step 3 If the OTU_LOF alarm persists, check the transmit optical power at the opposite station. If the
transmit optical power is excessively low, replace the board at the opposite station.

Step 4 If the alarm persists, check whether the clocks on the local NE and opposite NE are synchronous
with those on the network. If not, set the clock tracing function, and then check whether the
OTU_LOF alarm is cleared.
Step 5 If the alarm still persists, check whether the fiber works well. If yes, replace the board that
generates the alarm.
Step 6 If the alarm persists, replace the cross-connect and timing board at the local station.
Step 7 If the alarm persists, replace the line board at the opposite station.
Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite station.
----End
Related Information
None
4.173 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the multiframe alignment signal(MFAS) is abnormal.
Attribute
Major Service alarm
Parameters
None

When the OTU_LOM alarm is generated, the multiframe is lost and the services are interrupted.
Possible Causes
The possible causes of the OTU_LOM alarm are as follows:
l The expected consecutive frames are not received.

l Too many bit errors exist during the transmission.
l The receive direction of this board is faulty.

Procedure
Step 1 View the OTU_LOM alarm on the U2000 to determine the relevant board.
excessively low, clean the fiber header and the connector. If the receive optical power is
excessively high, provide more optical attenuators. After making sure that the receive optical
power is proper, check whether the OTU_LOM alarm is cleared.
Step 3 If the alarm persists, check the transmit optical power at the opposite station. If the transmit
optical power is excessively low, replace the board at the opposite station.
Step 4 If the alarm persists, check whether the clocks on the local NE and opposite NE are synchronous
with those on the network. If not, set the clock tracing function, and then check whether the
OTU_LOM alarm is cleared.
Step 5 If the alarm persists, check whether the fiber works well. If yes, replace the board that generates
the alarm.
Step 6 If the OTU_LOM alarm still persists, replace the source board of the OUT path (excluding the
stations that transparently transmit the ODU path).
----End
Related Information
None
4.174 OTUk_AIS
Description
The OTUk_AIS is an OTUk alarm indication. An AIS signal travels downstream, which
indicates that a signal failure is detected in the upstream.
Attribute
Parameters
None


Possible Causes
l Signals input from the client side contain the ODUk_PM_AIS or OTUk_AIS signals.
l The upstream station has loopback or cross-connection or the FEC type configuration is
incorrect.
Procedure
Step 2 If the alarm is reported from the client side, check the equipment on the client side.
Step 3 Use the U2000 to query whether the upstream station has any loopback. If yes, release the
loopback.
Step 4 Check whether the configuration of the cross-connection and FEC type is correct at the upstream
station. If not so, correct the configuration.
----End
Related Information
ITU-T G.709
4.175 OTUk_BDI
Description
The OTUk_BDI indicates an OTUk backward defect. This alarm occurs when the SM section
detects a signal failure and the value of the BDI byte is 1.
Attribute
Parameters
None

Possible Causes
l Signals input from the client side contain the OTUk_BDI alarm.

l The corresponding OTU board at the downstream station receives the LOF, LOM,
OTUk_AIS, or OTUk_TIM, OTUk_SSF alarm.
Procedure
Step 2 Query whether the alarm is reported from the client side or the WDM side.
l If the alarm is reported from the client side, check the equipment on the client side.
l If the alarm is reported from the WDM side, check whether the corresponding OTU board
at the downstream station receives the LOF, LOM, OTUk_AIS, OTUk_TIM, or
OTUk_SSF alarm by using the U2000. If yes, handle the corresponding alarm at the
downstream station.
----End
Related Information
ITU-T G.709
4.176 OTUk_DEG
Description
The OTUk_DEG is an alarm indicating that the OTUk signal is degraded. When the BIP8
detection is in burst mode, this alarm is generated if the signal degradation or bit error count
exceeds the threshold. In addition, when the BIP8 detection in poisson mode, this alarm is
generated if the signal degradation exceeds the threshold.
Attribute
Parameters
None

If the alarm is generated, the services at the optical interface have bit errors, which make the
service signals invalid or even unusable.

Possible Causes
l The optical interface at the local end is faulty.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. For optical power
specifications of specific boards, see the Product Description. If the optical power is not within
the normal range, see the handing procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms
for troubleshooting.
Step 3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, see the
Supporting Tasks.
----End
Related Information
ITU-T G.709
4.177 OTUk_EXC
Description
The OTUk_EXC is an alarm indicating that the OTUk bit errors cross the threshold. This alarm
is generated when the BIP8 detection is in poisson mode and bit error count exceeds the
threshold.
Attribute
Parameters
None


Possible Causes
l The attenuation of the received signals is rather large, and the fiber of the transmission line
is abnormal.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using
Replacement.
----End
Related Information
ITU-T G.709
4.178 OTUk_LOF
Description
The OTUk_LOF is an alarm indicating that the frame alignment signal(FAS) is abnormal. This
alarm occurs when the frame alignment processing is out of frame (OOF) in three consecutive
milliseconds.
Attribute
Parameters
None

Services on the board are interrupted.

Possible Causes
l The signals transmitted by the corresponding board at the opposite end do not have a frame
structure.
l The input optical power is abnormal.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If that is the case, locate
the position where the alarm is first generated according to the service route. If no alarm is
generated at the opposite end, the local end is the place where the alarm is first generated.
Step 2 Check whether the input optical power of the place where the alarm is first generated is within
the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH
or IN_PWR_LOW alarm for troubleshooting.
Step 5 If the alarm persists, the board may be faulty. Replace the faulty board. For details, see the
Supporting Tasks.
----End
Related Information
ITU-T G.709
4.179 OTUk_LOM
Description
The OTUk_LOM is an alarm indicating that the multiframe alignment signal(MFAS) is
abnormal. This alarm occurs when the multiframe locating is out of multiframe (OOM) in three
consecutive milliseconds.

Attribute
Parameters
None

Possible Causes
l The bit errors in the received signals of the OTU board at the local station are excessive.
Procedure
Step 2 Query the performance value of the BIP8 bit errors in the received signals of the board at the
local station through the U2000. If the BIP8 bit errors are excessive, see the handling procedure
of the OTUk_EXC or OTUk_DEG for troubleshooting.
----End
Related Information
ITU-T G.709
4.180 OTUk_SSF
Description
The OTUk_SSF is an alarm that the signal fails at the OTUk server layer.

Attribute
Parameters
None

Possible Causes
l The input signals contain the LOS signal.
l The received signals contain the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm.
Procedure
Step 1 Check whether the LOS alarm is generated in the receive direction at the local station. If yes, it
indicates that the input signals contain the LOS signal. Clear the LOS alarm at the opposite
location according to the corresponding handling procedure.
Step 2 Check whether the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm persists on the line. If yes,
clear the alarm accordingly.
----End
Related Information
None
4.181 OTUk_TIM
Description
The OTUk_TIM is an alarm indicating OTUk trail trace identifier (TTI) mismatch. This alarm
occurs during the control process when the TTI at the opposite end mismatches that at the local
end when the TIM detection is enabled. The system compares the access point identifiers (API)
in the input signals and the expected API.
three types:
termination.

Attribute
Parameters
None

If the alarm is generated, the signal quality of the services at the optical interface is degraded.
Hence, the service signals may be unavailable.
Possible Causes
consistent.
l The TTI sent at the opposite end is not consistent with the TTI to be received at the local
end.
Procedure
Step 1 Query the TIM detection mode of the local end on the NMU2000. Select the suitable topology
for the local end on the U2000 interface according to networking architecture. If the topology
is point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail
termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the sink
of trail termination.
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be
received at the local end through the U2000. If they are not consistent, query the received TTI
on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to be the
same as these of the received TTI.
cross-connection.
----End

Related Information
ITU-T G.709
4.182 OUT_PWR_LOW
Description
The OUT_PWR_LOW is an alarm indicating that the output optical power is excessively low.
The output optical power of the laser is excessively low.
Attribute
Parameters
None

The output optical power of the laser is excessively low, which influences the normal
transmission of services.
Possible Causes
l The input optical power is excessively low.
l The laser is aged.
Procedure
Step 1 Check whether the input optical power of the interface of the board at the local station is within
the Product Description.
l If it is not within the normal range, add a suitable attenuation to adjust the input optical
power in the normal range.
l If it is within the normal range, replace the faulty optical module. For details, see the Parts
Replacement.
----End

Related Information
None
4.183 OWSP_PS
Description
The OWSP_PS is an alarm indicating the OWSP protection switching. This alarm occurs when
the OWSP protection group actuates switching in which the current channel switches to the
protection channel from the working channel.
Attribute
Major Communication Alarm
Parameters
None

When the OWSP protection group actuates switching, services are transiently interrupted. When
this alarm is reported, the working channel of the OWSP protection group might have faulty
services that needs to be restored.
Possible Causes
switching. Such a command makes the current channel of the OWSP protection group
l Cause 2: The services of the working channel of the OWSP protection group are faulty.
reported.
Procedure

to the services, such as R_LOC, R_LOS. If yes, handle the alarms by referring to the
corresponding alarm handling procedures.
----End
Related Information
None
4.184 OWSP_STA_INDI
Description
The OWSP_STA_INDI is an alarm indicating the state of the optical wave share protection
group. This alarm is reported when the working or protection channel of the protection group is
faulty or the user runs an external switching command.
Attribute
Minor Communication Alarm
Parameters

Parameters 1 Indicate the west switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR
Parameters 2 Indicate the east switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR

l When the OWSP group performs switching, services are transiently interrupted.
l When this alarm is reported, the working or protection channel of the OWSP protection
group may have faulty services that need to be restored.

Possible Causes
l The user issues an external switching command such as the forced switching, manual
l The services of the working or protection channel of the OWSP protection group are faulty.
Procedure
necessary,
external switching.
1. Query whether the related boards for configuring the protection group have alarms, such
as R_LOC, R_LOS. If yes, handle the alarms according to the corresponding alarm handling
procedures.
----End
Related Information
None
4.185 PATCH_ACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating that the activated state of the patch
package is excessively long. The alarm is generated when the activated state of the patch package
Attribute
Parameters
None


The activation of the patch is not in the stable state. If the board is reset in this case, the patch
does not take effect after the system restarts, and the patch is automatically restored to the
deactivated state. The functions of the patch are not available or the bug corrected by the patch
appears again.
Possible Causes
The activated state of the patch package is excessively long.
Procedure
Step 1 If the patch file is confirmed to be correct, run the patch file through the U2000 after the end of
the observation.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the
U2000.
----End
Related Information
None
4.186 PATCH_DEACT_TIMEOUT
Description
The PATCH_DEACT_TIMEOUT is an alarm indicating that the deactivated state of the patch
package is excessively long. The alarm is generated when the deactivated state of the patch
package exceeds the threshold.
Attribute
Parameters
None

The deactivated state indicates that the patch is loaded but the patch is not running. If the board
is reset in this case, the patch is automatically restored to the idle state after the system restarts.
The functions of the patch are not available or the bug corrected by the patch appears again.

Possible Causes
The deactivated state of the patch package exceeds the threshold.
Procedure
Step 1 If the patch file is confirmed to be correct, activate the patch file through the U2000.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the
U2000.
----End
Related Information
None
4.187 PATCH_PKGERR
Description
The PATCH_PKGERR is an alarm indicating a patch package file error.
Attribute
Major Process
Parameters
None

Package loading management of certain boards may be unavailable if this alarm is generated.
Possible Causes
The patch package of certain boards is lost
Procedure
Step 1 Contact Huawei engineers to regenerate the patch package file.
----End
Related Information
None

4.188 PM_BDI
Description
The PM_BDI is an alarm indicating PM back defect in the PM overhead at the optical
demultiplexer unit (ODU) layer. This alarm indicates that ODUs are provided at the remote end
or severe alarms occur at an upper layer.
Attribute
Parameters
None

The PM_BDI alarm is generated at the ODU termination station mapping the services in the
transmit direction. The services in the receive direction are not affected.
Possible Causes
The possible causes of the PM_BDI alarm are as follows:
l Certain alarms occur at the remote ODU termination station.

l The transmit unit at the local end is faulty.
l The receive unit at the remote end is faulty.
Procedure
Step 1 Check whether any other higher-level ODU alarm is generated at the remote ODU termination
station. If yes, take priority to clear it, and then check whether the PM_BDI alarm is cleared.
Step 2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the
PM_BDI alarm is generated, check and modify the configuration.
NOTICE
The loopback causes service interruption.
Step 3 If the alarm persists, replace the board at the local station.

Step 4 If the alarm at the remote end persists and the inloop is normally performed at the local optical
station, replace the board at the remote end.
----End
Related Information
None
4.189 PM_BEI
Description
The PM_BEI is an alarm indicating a PM back error in the PM overhead at the optical
demultiplexer unit (ODU) layer. This alarm indicates that PM-BIP check bit errors occur at the
remote end.
Attribute
Parameters
None

performance
When the PM_BEI alarm is generated, PM-BIP bit errors occur at the ODU termination station,
but the FEC function and are not affected at the local station.
Possible Causes
The possible causes of the PM_BEI alarm are as follows:
l Certain bit errors occur at the remote ODU termination station.

Procedure
Step 1 Check whether any bit error occurs at the ODU termination station. After clearing the bit error,
check whether the PM_BEI alarm is cleared.
PM_BEI alarm is generated, check and modify the configuration.

NOTICE
----End
Related Information
None
4.190 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the ODU PM section
Attribute
Major Service alarm
Parameters
None

When the PM_BIP8_OVER alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the PM_BIP8_OVER alarm are as follows:

l The connector is incorrectly connected.

Procedure
Step 1 Check whether any higher-level alarm, such as R_LOS or R_LOF, is detected on the U2000. If
yes, take priority to clear it, and then check whether the PM_BIP8_OVER alarm is cleared.
Step 2 Check whether the receive optical power of the board that reports the alarm is within the normal
range. If yes, go to Step 9.
Step 3 Clean the fiber connector at the local station and the receive optical interface on the line board,
Step 4 Check whether the flange is correctly connected to the optical attenuator at the local station, and
whether the attenuation value specified in the optical attenuator is proper. After making sure
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
Step 5 Check whether the transmit optical power at the opposite station 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 fiber connector at the opposite
station, and then check whether the alarm is cleared.
Step 7 Check whether the flange is correctly connected to the optical attenuator at the opposite station,
and whether the attenuation value specified in the optical attenuator is proper. After making sure
Step 8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm
is cleared.
Step 9 Replace the line board that reports the alarm at the local station, and then check whether the
alarm is cleared.
Step 10 Replace the cross-connect and timing board at the local station, and then check whether the alarm
is cleared.
Step 11 Replace the line board at the opposite station, and then check whether the alarm is cleared.
Step 12 Replace the cross-connect and timing board at the opposite station, and then check whether the
alarm is cleared.
----End
Related Information
None
4.191 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the PM BIP error signal is degrade in the ODU
PM section.

Attribute
Major Service alarm
Parameters
None

When the PM_BIP8_SD alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the PM_BIP8_SD alarm are as follows:

Procedure
yes, take priority to clear it, and then check whether the PM_BIP8_SD alarm is cleared.
is cleared.

alarm is cleared.
is cleared.
alarm is cleared.
----End
Related Information
None
4.192 PM_TIM
Description
The PM_TIM is an alarm indicating that the monitoring trail trace identifier (TTI) mismatches
in the ODU PM overhead.
Attribute
Parameters
None

When the PM_TIM alarm is generated, the FEC function and services are not affected.
Possible Causes
The possible cause of the PM_TIM alarm is as follows:
The PM_TTI byte to be received at the local station is incorrectly set.
Procedure
Step 1 Check whether the SM-TTI byte to be received at the board is consistent with the received SM-
TTI byte. If not, modify it and make sure it is consistent with the received SM-TTI byte.
----End

Related Information
None
4.193 PORTSWITCH_FAIL
Description
The PORTSWITCH_FAIL is an alarm indicating an optical switch switching failure. This alarm
occurs when the board detects that the optical switch inside the board fails to switch.
Attribute
Parameters
None

When the MCA board reports this alarm, the spectrum analysis data at optical ports cannot be
queried.
Possible Causes
Procedure
Step 1 Perform cold reset on the faulty board by using the U2000 or remove the faulty board and insert
it again. For details, see the Supporting Tasks.
Step 2 After the board is reset, perform the spectrum analysis on the MCA again by sing the U2000.
----End
Related Information
None
4.194 POWER_ABNORMAL

Description
The POWER_ABNORMAL is an alarm indicating a power supply failure. This alarm occurs
when the power supply of a board becomes abnormal.
Attribute
Parameters
Name Meaning
Parameter 1 and Parameter 2 Each bit indicates whether the alarm is generated in the
corresponding voltage. Bit 1 indicates that the alarm is
generated, and bit 0 indicates that no alarm is generated.

When the POWER_ABNORMAL alarm is generated, the power supply functions abnormally,
and the board may not be able to function normally.
Possible Causes
l Cause 1: The input power of the PIU is abnormal.
l Cause 2: The jumper cap of the SCC is not configured.
l Cause 3: The power module on the board is faulty.
Procedure
l Query current alarms on the U2000. Then, determine the board that reports the alarm. For
details, see Querying the Current Alarms and Performance Events of a NE on the U2000
in the Supporting Task.
l Cause 1: The input power of the PIU is abnormal.
1. Check the board alarm indicator to see whether the power input is normal. For the
description of the alarm indicators on the board, see the Hardware Description.
2. If not, feed the NE power again or replace the DC PDU. For operations of accessing
the power supply, see the Quick Installation Guide.
l Cause 2: The jumper cap of the SCC is not configured.

NOTE
The POWER_ABNORMAL alarm is reported when the jumper used to set the used input voltage of
the SCC is configured incorrectly.
1. Contact the local representative office of Huawei, and then check whether the jumper
of the SCC is correct. If not, adjust the jumper. For details on the jumper setting of
each SCC, see the Hardware Description.
l Cause 3: The power module on the board is faulty.
1. Check whether the alarm is cleared after you perform cold reset on the board. For the
operations that are performed by using the U2000, see Performing a Cold Reset of a
Board in the Supporting Task. For operations of reseating a board, see "Removing
Boards" and "Inserting Boards" in the Quick Installation Guide.
NOTICE
interrupted after you perform cold reset on the board.
2. If the alarm persists, replace the board that reports the alarm. For details, see the Parts
Replacement.
----End
Related Information
None
4.195 POWER_DIFF_OVER
Description
Optical power difference exceeding the system limit. This alarm is generated when the power
difference between the active and standby channels crosses the threshold.
Attribute
Parameters
None

The switching of the active and standby channels is affected. As a result, the quality of the
received services is affected.

Possible Causes
l During transmission, the optical power attenuation of signals is excessively large or the
board at the local end is added with an over-large optical attenuator. Therefore, the optical
power difference between the active and standby OSCs at the receive end is excessively
large.
l The optical power difference of signals on the active and standby channels when the board
at the opposite end transmits signals is excessively large.
l The detection circuit of the board at the local end is faulty.
Procedure
Step 1 Replace the existing optical attenuators with suitable ones. Adjust the optical power on the active
and standby channels of the board at the local station to ensure that the power difference is within
5 dB.
NOTE
After the POWER_DIFF_OVER alarm is reported, the alarm can be cleared only when the power difference is
with the range of the preset threshold minus 2 dB to avoid alarm jitter.
Step 2 If the alarm persists, the detection circuit of the board at the local station is faulty. Replace the
faulty board.
----End
Related Information
None
4.196 PRBS_LSS
Description
The PRBS_LSS is an alarm indicating loss of the pseudo-random binary sequence (PRBS)
signal. The alarm is generated when the board, on which the PRBS bit error test is performed,
does not receive the PRBS signals from the local board.
Attribute
Parameters
None

The PRBS test services on the board are interrupted.

Possible Causes
l Cause 1: The link is abnormal. Hence, the board, on which the PRBS bit error test is
performed, does not receive the PRBS signals from the local board.
l Cause 2: The board is faulty, or the line is degraded.
Procedure
Step 1 Perform a self-loop by connecting the transmit end to the receive end of the PRBS signals on
the local board.
l If the alarm is cleared, it indicates that the board is normal. See Step 2 to check the link.
l If the alarm persists, it indicates that the board is faulty. Replace the board. For details, see
the Parts Replacement.
Step 2 Check the link and make sure that the link under the PRBS test is a loop. If the alarm persists,
perform a loopback on each point of the link. Find out the abnormal point on the link, and repair
or replace the link.
----End
Related Information
None
4.197 PUM_BCM_ALM
Description
The PUM_BCM_ALM is an alarm indicating that the bias current of the pump laser crosses the
threshold. This alarm occurs when the pump laser bias current of the optical amplifier unit crosses
the threshold.
Attribute
Parameters
Parameter 1 Indicates the threshold crossing type. The value is always 0x01.

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure
is taken, however, the output optical power of the board is affected in a period of time. This
affects the services

Possible Causes
l Excessively high or excessively low ambient temperature affects the laser.
Procedure
Step 1 Check whether the ambient temperature is normal. If not, adjust the ambient temperature of the
equipment to a proper degree.
Step 2 If the alarm persists, perform a warm reset on the faulty board on the U2000.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect the services.
----End
Related Information
None
4.198 PUM_TEM_ALM
Description
The PUM_TEM_ALM is an alarm indicating that the working temperature of the pump laser
exceeds the threshold. This alarm occurs when the operating temperature of the pump laser on
the optical amplifier unit crosses the threshold.
Attribute
Parameters
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure
is taken, however, the output optical power of the board is affected in a period of time. This
affects the services.

Possible Causes
l The ambient temperature is excessively high or excessively low.
l The cooling system of the pump laser is damaged.
l The pump laser has excessive current.
Procedure
Step 1 Check whether the ambient temperature is normal. If not, improve it.
Step 2 If the alarm persists, perform a warm reset on the faulty board through the U2000.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect services.
----End
Related Information
None
4.199 R_LOC
SF64, SF64A, SFD64, SL64, SLD64, 4.199.1 R_LOC(OCS)

Boards other than the SF64, SF64A, SFD64, 4.199.2 R_LOC(OTN)

SLO16, or EGSH
4.199.1 R_LOC(OCS)
Description
The R_LOC is an alarm indicating loss of the clock. This alarm is reported if the line board fails
to extract clock signal from the line signal.

Attribute
Parameters
None

When the R_LOC alarm is generated, the line board fails to extract the clock from the received
optical signals. Consequently, the services are interrupted.
Possible Causes
The possible causes of the R_LOC alarm are as follows:
l The clock extraction module on the line board is faulty.

l The cross-connect and timing board at the opposite station is faulty or is out of position.
Procedure
Step 1 Perform cold reset on the line board that generates the alarm at the local station. Then check
whether the R_LOC alarm is cleared.
Step 2 If the alarm persists, the clock extraction module on the line board may be faulty. In this case,
replace the line board, and then check whether the R_LOC alarm is cleared.
Step 3 If the alarm persists, check whether the cross-connect and timing board at the opposite station
is faulty. If yes, replace the cross-connect and timing board, and then check whether the R_LOC
alarm is cleared.
----End
Related Information
None
4.199.2 R_LOC(OTN)
Description
The R_LOC is an alarm indicating loss of the clock on the receive line. This alarm occurs when
the clock signal fails to be extracted from the received signals.

Attribute
Parameters
None

Services at this port are interrupted.
Possible Causes
l The link is abnormal and the board cannot normally extract clock signals.
l The setting of the board clock tracing is incorrect.
Procedure
Step 1 Perform a self-loop on the board. Then, check whether the physical link is normal. If there is
any abnormity, such as OTUk_LOF, remove the fault.
Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the entire
network planning. Adjust the board clock setting if it is incorrect.
----End
Related Information
None
4.200 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is a critical alarm of the alarm input.
Attribute

Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input
interface of the EFI1 board changes.
Possible Causes
l The status of the alarm input of the EFI1 board changes.
l The alarm input interface of the EFI1 board reports the alarm by default. The alarm is
reported in the default state.
Procedure
Step 1 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the EFI1 board changes. If that is the case, remove the
fault of the external equipment.
Step 2 If no external equipment is connected to the alarm input interface, set the input interface to
Unused and the alarm is cleared.
----End
Related Information
None
4.201 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is a warning alarm of the alarm input.
Attribute
Parameters
None

interface of the EFI1/EFI2 board changes

Possible Causes
Procedure
----End
Related Information
None
4.202 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is a major alarm of the alarm input.
Attribute

Parameters
None

interface of the EFI1 board changes.
Possible Causes

Procedure
----End
Related Information
None
4.203 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is a minor alarm of the alarm input.
Attribute
Parameters
None

interface of the EFI1board changes.
Possible Causes
Procedure

----End
Related Information
None
4.204 REM_SD
Description
The REM_SD is an alarm indicating that the remote signal is degraded. When the received
signals on the client side of the board at the opposite station is degraded, the alarm signal is
inserted. The alarm is generated when the client side of the board at the local station detects the
signals.
Attribute
Parameters
None

The QoS of the service signals is affected. In a serious situation, the services are interrupted.
Possible Causes
l The client side of the OTU at the opposite end has the B1_EXC alarm.
l The demultiplexed client signals on the WDM side of the OTU at the local end have the
B1_EXC alarm.
Procedure
Step 1 Check whether the OTU at the opposite end has the B1_EXC alarm. If yes, see the procedure
of handling B1_EXC to handle the alarm.
Step 2 If the alarm persists, check whether demultiplexed client signals on the WDM side of the OTU
at the local end have the B1_EXC alarm. If yes, see the procedure of handling B1_EXC to handle
the alarm.
----End

Related Information
None
4.205 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that the regenerator section performance events cross
the threshold. The alarm occurs when the performance module reports the threshold crossing of
the performance events in the regenerator section
Attribute
Minor Service alarm
Parameters
None

The line has bit errors, which decreases the QoS.
Possible Causes
l The laser of the board at the opposite station is degraded.
l The input optical power of the board at the local station is excessively high or excessively
low.
l The clock at the opposite station is degraded.
l The fiber is degraded.
Procedure
Step 1 Check whether the fiber is aged or has excessive attenuation. If that is the case, remove the fault
of the fiber.
Step 2 Query whether the board has the B1_EXC, B1_SD alarm by using the U2000. If that is the case,
clear the alarm.
Step 3 Check whether the input optical power of the board at the local station is within the normal range
by using the U2000. For optical power specifications of specific boards, see the Product
Description.
l If the optical power displayed on the U2000 is normal, the board may be faulty. Replace

l If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
a value within the normal range.
Step 4 If the alarm persists, remove the fault of the board at the opposite station.
----End
Related Information
A performance monitoring period can be 15 minutes or 24 hours. A performance threshold
crossing alarm check whether the requirement of alarm clearance is met only after a new
monitoring period starts. If the alarm persists after you perform the provided procedure, query
whether the service has been restored to normal by checking the accumulated performance
values. Or wait after a new monitoring period starts and then check whether the alarm is cleared.
4.206 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the timing of the real time clock (RTC) fails.
Attribute
Parameters
None

When the alarm is reported, the system employs the soft timing. Hence, the timestamp precision
of the system decreases.
Possible Causes
l The clip of the RTC clock is damaged.
l The temperature of the board is excessively high.
Procedure
Step 1 Check whether the board temperature is normal. If it is abnormal, replace the fan.
Step 2 If the alarm persists, replace the faulty SCC. For details, see the Parts Replacement.
----End

Related Information
RTC is also called NE timing.
4.207 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the
S1 mode.
Attribute
Parameters
Parameter 1 Indicates the ID of the priority table. Valid values are as follows:
l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source

The switching performs on the working clock source of the board, which influence the user
services.
Possible Causes
l Cause 1: The fiber connection is faulty.
l Cause 2: The upstream station generates the alarm.
Procedure
l Cause 1: The fiber connection is faulty.
1. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
see the Supporting Tasks.

2. If the alarm persists, replace the faulty board. For details, see the Parts
Replacement.
l Cause 2: The upstream station generates the alarm.
1. If the alarm persists, check whether the S1_SYN_CHANGE alarm is generated at the
upstream station. If yes, repeat steps to clear the S1_SYN_CHANGE alarm at the
upstream station. The S1_SYN_CHANGE alarm at the local station is then
----End
Related Information
None
4.208 SCC_LOC
Description
The SCC_LOC is an alarm indicating that the SCC losses the clock. The alarm occurs when the
OSC board detects that the clock source sent by the SCC board is lost.
Attribute
Parameters
None

The NE is out of control and the OSC is interrupted.
Possible Causes
l The SCC board is faulty.
l The alarm is generated during the cold reset of the SCC board. The alarm is automatically
cleared after the cold reset is complete.
Procedure
Step 1 Query the reset record of the SCC board.
l If the time when the alarm is cleared is consistent with the time that the SCC is reset, the
alarm may be caused by resetting the SCC. There is no need to handle the alarm.

l If the time when the alarm is cleared is not consistent with the time that the SCC is reset,
the board may be faulty. Replace the faulty board. For details, see the Parts Replacement.
Step 2 If the alarm persists, the SCC board may be faulty. Replace the faulty SCC board. For details,
see the Parts Replacement.
----End
Related Information
None
4.209 SERVICE_TYPE_EXCEED_LICENSE
Description
The SERVICE_TYPE_EXCEED_LICENSE is an alarm indicating that the service type exceeds
the license limit. The alarm indicates that the type of configured services exceeds the license
limit.
Attribute
Major Service
Parameters
Parameter 1 Indicates the ID of the subrack, where the service type exceeds the license limit.

When the SERVICE_TYPE_EXCEED_LICENSE alarm is generated, neither the existing
services nor the operation of the system is affected. The subrack where the alarm is generated,
however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service type configured in the subrack exceeds the license limit.

Procedure
Step 1 According the alarm parameter, check whether the type of configured services in the subrack
exceeds the license limit by using the U2000.
Step 2 If yes, assign a proper license.
Step 3 If no proper license is available, purchase the license with a higher version from Huawei.
----End
Related Information
None
4.210 SERVICE_CAPACITY_EXCEED_LICENSE
Description
The SERVICE_CAPACITY_EXCEED_LICENSE is an alarm indicating that the service
capacity exceeds the license limit. This alarm indicates that the service capacity configured in
the subrack exceeds the license limit.
Attribute
Major Service
Parameters
Parameter 1 Indicates the ID of the subrack, where the service capacity exceeds the license
limit.

When the SERVICE_CAPACITY_EXCEED_LICENSE alarm is generated, neither the existing
services nor the operation of the system is affected. The subrack where the alarm is generated,
however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service capacity configured in the subrack exceeds the license limit.

Procedure
Step 1 According to the alarm parameters, query the license capacity for the subrack where the alarm
is generated. Then, select a proper license capacity to meet the service requirements of the
subrack.
Step 2 If no license with a proper capacity can be used, purchase the license with a proper capacity
from Huawei.
----End
Related Information
None
4.211 SHELF_AREA_POWER_OVER
Description
The SHELF_AREA_POWER_OVER is an alarm indicating that the total optical power
consumption of the subrack exceeds the threshold. This alarm is generated when the total power
consumption of the boards in each partition of the subrack is higher than or equal to the power
consumption threshold for each partition.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID.
Parameter 2 Indicates the number of the partition.

The total power consumption of the boards in each partition of the subrack exceeds the threshold.
This puts the system in a very dangerous state. If the system runs in this state for a long time,
the power supply unit of the subrack may work abnormally and a power failure may occur in
the subrack.

Possible Causes
The total power consumption of the boards in each partition of the subrack is higher than or
equal to the power consumption threshold for each partition.
Procedure
Step 1 Remove the board from the subrack. Wait until the alarm is cleared.
----End
Related Information
None
4.212 SLAVE_WORKING
Description
The SLAVE_WORKING is an alarm indicating the working state of the protection board. If the
protection cross-connect board is selected for the service bus of the service board, and if the
slave clock is selected as the system clock, the SLAVE_WORKING alarm is reported.
Attribute
Parameters
None

When the SLAVE_WORKING alarm is generated, the system is not affected. This alarm just
indicates that the protection cross-connect board is selected for the service bus of the service
board, and the slave clock is selected as the system clock.
Possible Causes
The possible causes of the SLAVE_WORKING alarm are as follows:
l Cause 1: The active cross-connect and timing board is not in position.

l Cause 2: The active cross-connect and timing board is faulty.
l Cause 3: The service board is faulty.

Procedure
l Query current alarms on the U2000. Determine the board that reports the alarm. For details,
see Querying the Current Alarms and Performance Events of a NE on the U2000 in the
Supporting Task.
l Cause 1: The active cross-connect and timing board is not in position.
1. Check whether the active cross-connect and timing board is loose. If yes, tighten the
active cross-connect and timing board. For details, see "Removing Boards" and
"Inserting Boards" in the Quick Installation Guide. Then, check whether the alarm is
cleared.
l Cause 2: The active cross-connect and timing board is faulty.
1. Replace the active cross-connect and timing board. For details, see Parts
1. Perform cold reset on the service board that reports the alarm by using the U2000, or
reseat the service board that reports the alarm. For the operations that are performed
on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For
operations of reseating a board, see "Removing Boards" and "Inserting Boards" in the
2. If the alarm persists, replace the board that reports the alarm. For details, see Parts
Replacement.
----End
Related Information
The working cross-connect board refers to the cross-connect board inserted in the slot of a smaller
ID.
The protection cross-connect board refers to the cross-connect board inserted in the slot of a
larger ID.
4.213 SM_BDI
Description
The SM_BDI is an SM back defect indication at the optical transponder unit (OTU) layer. This
alarm indicates that OTUs are provided at the remote end or severe alarms occur at an upper
layer.

Attribute
Parameters
None

The SM_BDI alarm just indicates that certain alarms occur at the OTU termination station
mapping the services in the transmit direction. The services in the receive direction are not
affected.
Possible Causes
The possible causes of the SM_BDI alarm are as follows:
l Certain alarms occur at the remote OTU termination station.

Procedure
Step 1 Check whether any other higher-level OTU alarm is generated at the remote OTU termination
station. If yes, take priority to clear it, and then check whether the SM_BDI alarm is cleared.
SM_BDI occurs, check and modify the configuration.
NOTICE
----End
Related Information
None

4.214 SM_BEI
Description
The SM_BEI is an SM back error indication at the optical transponder unit (OTU) layer. This
alarm indicates that SM-BIP errors occur at the remote end.
Attribute
Parameters
None

When the SM_BEI alarm is generated, SM_BIP errors occur at the remote OTU termination
station, but the FEC function and performance are not affected at the local station.
Possible Causes
The possible causes of the SM_BEI alarm are as follows:
l Certain bit errors occur at the remote OTU termination station.

Procedure
Step 1 Query the performance of the board at the remote OTU termination station, and clear the bit
errors at the remote end.
----End
Related Information
None
4.215 SM_BIP8_OVER

Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the OTU SM section
Attribute
Major Service alarm
Parameters
None

When the SM_BIP8_OVER alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the SM_BIP8_OVER alarm are as follows:

Procedure
yes, take priority to clear it, and then check whether the SM_BIP8_OVER alarm is cleared.

Step 8 Check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the
alarm is cleared.
alarm is cleared.
is cleared.
alarm is cleared.
----End
Related Information
None
4.216 SM_BIP8_SD
Description
The SM_BIP8_SD is an alarm indicating that the SM BIP error signal is degraded in the OTU
SM section.
Attribute
Major Service alarm
Parameters
None

When the SM_BIP8_SD alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the SM_BIP8_SD alarm are as follows:


Procedure
yes, take priority to clear it, and then check whether the SM_BIP8_SD alarm is cleared.
is cleared.
alarm is cleared.
is cleared.
alarm is cleared.
----End
Related Information
None
4.217 SM_IAE

Description
The SM_IAE is alarm indicating an SM incoming alignment error (IAE) in the OTU SM section.
When the ODU frame is synchronously mapped into the OTU frame, the IAE flag is set to true
if the frame alignment errors occur. When the IAE errors are detected at the sink, the sub-frame
alignment bit errors occur in the received services.
Attribute
Parameters
None

When the SM_IAE alarm is generated, the service availability is affected.
Possible Causes
The possible causes of the SM_IAE alarm are as follows:
l The clock jitter event occurs in the transmit unit at the remote end (namely, the source of
the OTU/ODU adaptation function).
l The frame offset on the board termination side of the remote end (namely, the source of
the OTU/ODU adaptation function) is inaccurate.
l The board FEC processing chip at the remote end (namely, the source of the OTU/ODU
adaptation function) is faulty.
Procedure
Step 1 Adjust the frame offset on the board system side of the remote end (namely, the source of the
OTU/ODU adaptation function).
Step 2 If the alarm persists, replace the board at the remote end (namely, the source of the OTU/ODU
adaptation function).
----End
Related Information
None
4.218 SM_TIM

Description
The SM_TIM is an alarm indicating the section monitoring TTI mismatch in the OTU SM
overhead.
Attribute
Parameters
None

When the SM_TIM alarm is generated, the FEC function and the services are not affected.
Possible Causes
The possible causes of the SM_TIM alarm are as follows:
l The expected SM_TIM byte at the local end is incorrectly set.

l The value of the SM_TTI byte transmitted at the remote end is incorrectly configured.
l The fiber is incorrectly connected.
Procedure
Step 1 According to the service network, determine the expected setting of the SM_TTI byte in the
relevant position.
Step 2 Check whether the SM-TTI byte to be received at the board is consistent with the received SM-
TTI byte. If not, modify the incorrect SM-TTI byte to be received.
Step 3 If the received SM-TTI byte is incorrect, check whether the fiber connection at the next local
station is correct. If not, modify the connection.
Step 4 Check whether the setting of the transmitted SM-TTI byte in the upstream services is correct.
If not, modify the transmitted SM-TTI byte in the upstream services.
----End
Related Information
None
4.219 SNCP_FAIL

Description
The SNCP_FAIL is an alarm indicating an SNCP switching failure.
Attribute
Parameters
Name Meaning
Parameter 1 and Parameter 2 Indicates the protection group ID.

When the SNCP switching fails, the services configured with SNCP are not protected, and the
services in this SNCP group are interrupted.
Possible Causes
During the SNCP switching, the service grooming fails.
Procedure
Step 1 Reset the SCC board to re-configure all the services.
----End
Related Information
None
4.220 SO_SK_MISMATCH
Description
The SO_SK_MISMATCH is an alarm indicating that the number of timeslots bundled at the
LCAS source is not consistent with the number of timeslots bundled at the LCAS sink. When
the number of upstream (or downstream) timeslots is not consistent with the number of
downstream (or upstream) timeslots for a VCTRUNK, the SO_SK_MISMATCH alarm is
reported.

Attribute
Parameters
None

In the case of the SO_SK_MISMATCH alarm, services are not affected.
NOTICE
If the timeslots at the sink are added to other VCTRUNKs after the SO_SK_MISMATCH alarm
is reported, services in the VCTRUNK are interrupted. Do not proceed with other operations
before making sure that source and sink have the same number of timeslots.
Possible Causes
The possible cause of the SO_SK_MISMATCH is as follows:
The LCAS source and LCAS sink have different number of configured timeslots.
NOTE
If timeslots except the last timeslot are deleted at the sink instead of at the source, the SO_SK_MISMATCH
alarm is generated.
If the last timeslot is deleted at the sink instead of at the source, the SO_SK_MISMATCH alarm is not
generated.
Procedure
Step 1 View the SO_SK_MISMATCH alarm on the U2000, and then determine the number of the
VCTRUNK where the SO_SK_MISMATCH alarm is generated.
Step 2 On the U2000, check whether the number of upstream (or downstream) timeslots is consistent
with the number of downstream (or upstream) timeslots bundled in the VCTRUNK. If not, make
them consistent by adding or deleting some timeslots, and then check whether the
SO_SK_MISMATCH alarm is cleared.
----End
Related Information
None

4.221 SPEED_OVER
Description
The SPEED_OVER is an alarm indicating that the data rate exceeds the set limit. The
SPEED_OVER is an alarm indicating the mismatch between the rate of the monitored optical
interface and the preset one. This alarm is generated when a board detects that the received rate
mismatches the preset one.
Attribute
Parameters
None

When the SPEED_OVER alarm is generated, the received service rate mismatches the preset
one. The board cannot carry the service and the service is interrupted.
Possible Causes
l The set rate of the optical interface is incorrect.
Procedure
Step 1 Query the set rate and actual rate on the U2000, and determine whether the set rate is incorrect.
Step 2 If the set rate is incorrect, set a correct one on the U2000.
Step 3 If the alarm persists, check whether the input optical power is normal. If the input optical power
is excessively high or excessively low, adjust it.
Step 4 If the alarm persists, check whether the board chip is faulty, that is, whether there is a
HARD_BAD or a HARD_ERR alarm at the local station. If yes, replace the relevant board. For
details, see the Parts Replacement
----End
Related Information
None

4.222 SUBRACK_ID_CONFLICT
Description
The SUBRACK_ID_CONFLICT is an alarm indicating conflict of the subrack ID. In the case
of the master-slave subrack mode, this alarm is generated when the master subrack detects that
the DIP switch settings of the slave subracks are repeated.
Attribute
Parameters
Parameter 1, Parameter 2, Parameter 3 These parameters have no actual meaning.
Parameter 4 Indicates the conflict subrack ID.

The inter-subrack communication is abnormal. As a result, the command cannot be correctly
delivered to the corresponding subrack, and the board cannot be reached by the U2000.
Possible Causes
The possible causes of the SUBRACK_ID_CONFLICT alarm are as follows:
l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave
subracks are repeated.
Procedure
l Perform all the following steps regardless of whether the SUBRACK_ID_CONFLICT
alarm is cleared during the operations.
l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
1. There should be only one master subrack in the system. Check which master subrack
is redundant according to the actual networking and then remove it.
2. Perform a warm reset on the system control board in the master subrack.

3. Perform a warm reset on all boards on the NE.

4. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave
subracks are repeated.
1. Disconnect one slave subrack from the master subrack and reset the ID of this slave
subrack by changing the DIP switch setting on the system control board. In this case,
the IDs of the two slave subracks are different.
2. Perform a warm reset on the system control board in the master subrack on the NE.
3. After the subrack ID is changed, perform a warm reset on all the boards in the subrack.
4. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None
4.223 SUBRACK_ID_MISMATCH
Description
The SUBRACK_ID_MISMATCH is an alarm indicating mismatch of the subrack ID.
Attribute
Parameters
None

The DIP switch of the subrack ID mismatches with the subrack ID saved by the software, which
leads to the abnormal communication between the boards.
Possible Causes
The DIP switch of the subrack ID is changed. The subrack ID detected by the NE software and
board software is mismatched with the actual subrack ID.

Procedure
Step 1 Modify the DIP switch of the AUX to the subrack ID displayed in the statistics diode of the SCC
or power off the subrack
----End
Related Information
None
4.224 SUBRACK_LOOP
Description
The SUBRACK_LOOP is an alarm indicating the loop of the subrack. The alarm occurs when
the cascaded subracks form a closed loop.
Attribute
Parameters
None

The network storm occurs in the intra-subrack communication, which leads to unavailability of
the intra-subrack communication.
Possible Causes
l In the master/slave subrack mode, the internal network interfaces are connected in a closed
loop.
Procedure
Step 1 Check the cable connection between the subracks to ensure that the subracks are connected in
a chain manner.
----End
Related Information
None

4.225 SUM_INPWR_HI
Description
The SUM_INPWR_HI is an alarm indicating that the input optical power is excessively high.
The alarm occurs when the input optical power of the multiplexed signals exceeds the threshold.
Attribute
Parameters
None

The optical modules of the boards at the local station and downstream station may be damaged.
The services have bit errors, or are even interrupted.
Possible Causes
l The output optical power of the board at the upstream station is normal and the power of
the received optical signals accessed by the board at the local station is excessively high.
The proper attenuation is not added.
l The output optical power of the board at the upstream station or opposite station is
excessively high.
Procedure
Step 1 Check whether the input optical power of the input interface of the board at the local station is
within the normal range by using an optical power meter. For optical power specifications of
specific boards, see the Product Description. If the power is not within the normal range, add
proper attenuation by placing a fixed attenuator or a VOA.
Step 2 If the alarm persists, check whether the output optical power of the board at the upstream stations
is within the normal range by using the U2000. For optical power specifications of specific
boards, see the Product Description. If the input optical power of the board at the local station
is excessively high, handle the alarm according to the handling procedure of the IN_PWR_HIGH
alarm. If the output optical power of the boards at the upstream stations is excessively high,
respectively check whether the corresponding input and output optical power of each upstream
station are within the normal range.

l If the input and output optical power of the board at the upstream station are not within the
normal range, adjust the input optical power to a value within the normal range. For optical
power specifications of specific boards, see the Product Description.
l If the input optical power of the board at the upstream station is within the normal range
but the output optical power is not, the board at the upstream station may be faulty. Replace
----End
Related Information
None
4.226 SW_SNCP_PS
Description
The SW_SNCP_PS is an alarm indicating the SW SNCP protection switching. This alarm occurs
when the SW SNCP protection group actuates switching in which the current channel switches
Attribute
Parameters
None

When the SW SNCP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the SW SNCP protection group might have
Possible Causes
switching. Such a command makes the current channel of the SW SNCP protection group
l Cause 2: The services of the working channel of the SW SNCP protection group are faulty.
reported.

Procedure
to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK,
REM_SF, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
OTUk_DEG, OTUk_EXC, or REM_SD. If yes, handle the alarms by referring to the
corresponding alarm handling procedures.
----End
Related Information
None
4.227 SW_SNCP_STA_INDI
Description
The SW_SNCP_STA_INDI is an alarm indicating the state of the Sub-Wavelength SNCP
Attribute
Parameters


l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l When switching is performed in the SW SNCP group, the services are transiently
interrupted.
l When the alarm is reported, the working or protection channel of the SW SNCP group may
have faulty services that need to be restored.
Possible Causes
l The user issues an external switching command such as forced switching, manual switching
or locked switching.
l The services of the working or protection channel of the SW SNCP group are faulty.
Procedure
necessary.
external switching.
1. Query whether the related boards for configuring the protection group have the alarm such
as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS,
ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, REM_SF, ODUk_LOFLOM,
B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC, or REM_SD.
If that is the case, handle the alarms according to the corresponding handling procedure of
the alarm to restore the services of the working or protection channel.
that is the case, the services are automatically switched to the working channel. The alarm
is cleared. If the attribute is Non-Revertive, set it to Revertive and the alarm is cleared.

Step 3 On the U2000, query the switching state of the protection group, if the switching is in the WTR
state. This alarm requires no handling. After the WTR time, the alarm is cleared.
----End
Related Information
None
4.228 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the activation times out.
During loading of the software package, the alarm occurs when the operation is not committed
120 seconds after activation operation.
Attribute
Parameters
None

The services are not affected.
Possible Causes
The operation is not committed 120 seconds after activation operation during loading of the
software package.
Procedure
Step 1 Commit the activation operation again. If the alarm persists, check whether the software version
is correct. If the software version is incorrect, roll back the NE to the version before package
loading, and select the required software package on the NMS to load the package again.
----End
Related Information
None

4.229 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic matching function
is disabled.
NOTE
After the automatic matching function is enabled, when a board is added to an NE, the system automatically
checks whether the board software matches the NE software. If not, the SCC board upgrades the board software
of the new board.
Attribute
Minor Process alarm
Parameters
None

The SCC board cannot automatically update the software of the board that is newly inserted. If
the software of the new board mismatches the NE software, certain functions of the NE may
operate abnormally.
Possible Causes
The automatic matching switch is turned off.
Procedure
Step 1 If the alarm persists, contact Huawei engineers.
----End
Related Information
None
4.230 SWDL_CHGMNG_NOMATCH
Description
Software mismatching alarm after system control board replacement. The system re-checks
whether the board software of each board matches the NE software after the NE starts up upon

a power failure or the system control board is replaced or reset (cold). This alarm is generated
when the board software of a board mismatches the NE software.
Attribute
Parameters
None

l When this alarm occurs, the automatic matching function for package loading is disabled.
l The version of the NE software is inconsistent with that of the system control board. Certain
functions of the NE may operate abnormally.
Possible Causes
l After the NE is powered off, a board is inserted and the software version of the board is
inconsistent with that of the system control board.
l The system control board is replaced and the software version of the new system control
board is inconsistent with the NE software version.
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the correct
software package to perform package loading on the board. In normal cases, this alarm is
automatically cleared after the package loading succeeds.
NOTICE
Services may be affected if an incorrect software package is used for package loading. Therefore,
perform the procedure under guidance from Huawei engineers.
----End
Related Information
None

4.231 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating a commitment failure. During loading of
the software package, the alarm occurs when the commitment operation fails.
Attribute
Minor Process alarm
Parameters
None

The package loading fails and the upgrade of the software version fails.
Possible Causes
During the package loading, the dual-partition board fails in copying the new software from one
partition to the other.
NOTE
The dual-partition board has two file systems. The two partitions are of mutual backups. In normal states, every
file is saved in both partitions.
Procedure
Step 1 On the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
4.232 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the package loading is performed on the
NE. This alarm occurs when the NE is performing the package loading. After the NE finishes
the commitment operation, the alarm is cleared.

Attribute
Warning Process alarm
Parameters
None

The working/protection backup function of the SCC board is disabled.
Possible Causes
The NE is performing the package loading operation.
Procedure
Step 1 The software package loading is still in process. Wait until the package loading is complete.
Then, the alarm is cleared.
----End
Related Information
None
4.233 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that the file is lost. The alarm occurs when
the SCC checks the software package and finds that a file in a partition of the SCC software
package is lost and the file cannot be restored from the related file in another partition. Next
time when the SCC checks the software package and finds the file, the alarm is cleared.
NOTE
The SCC checks the software package every time when it starts up and when the periodical check is performed.
The periodical check is performed every hour by default.
Attribute

Parameters
None

Because a file in the SCC software package is lost, there may be an impact on the normal
operation of certain functions of the NE.
Possible Causes
The file is lost and irrecoverable.
Procedure
Step 1 On the U2000, use a correct software package of this version to perform the package loading on
the board.
----End
Related Information
None
4.234 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that no matching board software is
available. After an NE is loaded with a customized software package, when a board is inserted,
the software for the board is not found in the customized software package. In this case, the
board cannot be matched automatically and thus the alarm occurs.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual
requirement.
NOTE
If the new board is inserted when an SWDL_CHGMNG_NOMATCH alarm is present in the system, the new
board will also report this alarm.
Attribute
Minor Process alarm
Parameters
None


The software version of the unit is inconsistent with that of the SCC board. Certain functions of
the NE may operate abnormally.
Possible Causes
The user uses the customized software package, in which no software for the normal board is
found.
Procedure
Step 1 On the U2000, choose correct software version to perform a normal package loading again.
----End
Related Information
None
4.235 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the package version consistency check
fails. The alarm indicates that the software version information (similar to the file list category)
of the software package is not consistent with the actual software version information.
Attribute
Minor Process alarm
Parameters
None

The software versions on the NE are inconsistent. Certain functions of the NE may operate
abnormally.
Possible Causes
The file of the software package is faulty, and the software version information of the software
package is not consistent with the actual software version information.

Procedure
Step 1 On the U2000, use a correct software package to perform package loading on the board.
----End
Related Information
None
4.236 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that the NE rollback fails. If certain
board rollbacks fail when the NE performs the rollback, the alarm occurs.
Attribute
Minor Process alarm
Parameters
None

The NE rollback fails. The board software cannot be recovered to the version before the package
loading. In this case, the board software version and the NE software version may mismatch.
Certain functions of the NE may operate abnormally.
Possible Causes
Certain board rollbacks fail when the NE performs the rollback.
Procedure
Step 1 On the U2000, use the correct software package to perform package loading on the board.
----End
Related Information
None

4.237 SYN_BAD
Description
SYN_BAD is an alarm indicating that the frequency deviation of the synchronization source
exceeds the permitted range. This alarm is generated when the frequency deviation of the
synchronization source exceeds the permitted range so that quality of the physical-layer
synchronization source deteriorates.
Attribute
Parameters
Name Meaning
Parameter 2 Indicates the number of the slot in the subrack where the clock source of the
service board is located. If the external clock source is used, the value is always
0xf0.
Parameter 4 In the case of the clock source of the service board, it indicates the number of
the port in the subrack where the clock source is located.
In the case of the external clock source, it indicates the number of the external
clock.
l 0x01 indicates the first external clock.

l 0x02 indicates the second external clock.

When the SYN_BAD alarm is generated, tracing the relevant clock source may cause service
bit errors.

Possible Causes
The possible causes of the SYN_BAD alarm are as follows:
l Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
l Cause 3: The clock board that reports the alarm is faulty.
Procedure
l Check whether any higher-level alarm (such as B1_EXC, B1_SD, B2_EXC, B2_SD or
MS_CROSSTR) or performance event is detected on the U2000. If yes, take priority to
handle the higher-level alarm or performance event, and then check whether the SYN_BAD
alarm is cleared.
l Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
1. If an external clock source is traced, check whether the clock signals are normal. If
not, replace the external clock source. For details, see Configuring Physical Clock in
the Feature Description.
l Cause 3: The clock board that reports the alarm is faulty.
1. 1. If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
----End
Related Information
None
4.238 SYNC_C_LOS
Description
SYNC_C_LOS is an alarm indicating a synchronization source priority loss. This alarm is
generated when the clock source on a service board is lost in the priority table.

Attribute
Parameters
When you view an alarm on the network management system, select the alarm. The parameter
of the alarm is displayed in the brackets in the Details area. The parameter is in the hexadecimal
format and is described as follows:
l When the parameter contains six numbers, it indicates that the time source of the service
board is in subrack 0. The first and second numbers indicate the ID of the slot where the
time source of the service board is located in the subrack. The third to sixth numbers indicate
the number of port where the time source of the service board is located in the subrack. For
example, if the parameter value is 120001, the time source of the service board is located
at port 1 of the board in slot 18 in subrack 0.
l When the parameter contains seven numbers, the first number indicates the ID of the
subrack where the time source of the service board is located. The second and third numbers
indicate the ID of the slot where the time source of the service board is located in the subrack.
The fourth to seventh numbers indicate the number of port where the time source of the
service board is located in the subrack. For example, if the parameter value is 1120001, the
time source of the service board is located at port 1 of the board in slot 18 in subrack 1.

If this alarm is generated, it indicates that 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 error occurs
in the services later.
Possible Causes
The possible causes of the SYNC_C_LOS alarm are as follows:
l Cause 1: Input signals are lost at the optical or electrical interface that is connected to the
clock source.
l Cause 2: There is a fiber cut (when a line clock source is traced).
l Cause 4: The timing board is faulty.
Procedure
l Cause 1: Input signals are lost at the optical or electrical interface that is connected to the
clock source. Cause 2: There is a fiber cut (when a line clock source is traced).
1. On the U2000, check whether the R_LOS alarm is generated on the relevant service
board. If yes, take priority to clear the R_LOS alarm, and then check whether the
SYNC_C_LOS alarm is cleared.

1. If the alarm persists, perform cold reset on the relevant service board, and then check
whether the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
Replacement.
2. If the alarm persists, replace the clock board.
----End
Related Information
None
4.239 SYNC_DISABLE
Description
The SYNC_DISABLE is an alarm indicating that the automatic synchronization of the system
control board is disabled. When the automatic synchronization of the system control board is
disabled, backup in batches is not supported and this alarm is generated.
Attribute
Minor Process alarm
Parameters
None

The data of the active and standby system control boards may be inconsistent.
Possible Causes
The automatic synchronization state of the system control board is changed from enabled to
disabled.
Procedure
Step 1 Change the automatic synchronization state of the system control board to disabled, and then
the alarm is cleared automatically.
----End

Related Information
None
4.240 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH is an alarm indicating the forced or manual switching state of a
clock source.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the subrack where the switched clock source is located.
Parameter 2 Indicates the number of the slot in the subrack where the switched clock source
is located. If the external clock source is used, the value is always 0xf0.
the port in the subrack where the switched clock source is located.
clock.

Name Meaning
Parameter 5 Indicates the ID of the priority table. Valid values are as follows:
l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source

When the SYNC_F_M_SWITCH alarm is generated, the NE clock works in the forced or manual
switching state. This alarm does not affect services.
Possible Causes
Cause 1: A manual or forced switching command is issued for the clock source.
Procedure
l View the SYNC_F_M_SWITCH alarm on the U2000, and then determine the relevant
clock source according to the alarm parameters.
l Cause 1: A manual or forced switching command is issued for the clock source.
1. Clear the manual or forced switching for the relevant clock source, and the alarm is
automatically cleared. For details, see Configuring Physical Clock in the Feature
Description.
----End
Related Information
None
4.241 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating that the clock source in the priority list is locked.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the number of the subrack where the locked clock source is located.
Parameter 2 Indicates the number of the slot in the subrack where the locked clock source is
located. If the external clock source is used, the value is always 0xf0.
the port in the subrack where the locked clock source is located.
clock.

When the SYNC_LOCKOFF alarm is generated, the relevant clock source is locked and cannot
be traced by the NE. This alarm itself does not affect services.
Possible Causes
Cause 1: The NE software issues a command to lock the clock source.
Procedure
l View the SYNC_LOCKOFF alarm on the U2000, and then determine the locked clock
source according to the alarm parameters.
l Cause 1: The NE software issues a command to lock the clock source.
1. After the lockout of the clock source is released on the U2000, the SYNC_LOCKOFF
alarm is automatically cleared. For details, see Configuring Physical Clock in the
Feature Description.
----End
Related Information
None

4.242 SYNC_FAIL
Description
The SYNC_FAIL is an alarm indicating that the batch backup fails.
Attribute
Minor Process alarm
Parameters
Parameter 1 Indicates the alarm cause.
0x1f indicates that backing up the database fails.
0x20 indicates that verifying the active and standby SCC file versions fails.
0x21 indicates that the active and standby SCCs fails to communicate.

The patch backup fails, and the working/protection switching is unavailable.
Possible Causes
l The database backup fails.
l Software versions of the working board and the protection board are not consistent.
l Protection board communication is not stable or available.
Procedure
Step 1 Wait until the next working/protection backup succeeds and check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the software versions of the working board and the protection
board are consistent. If not, upgrade the software for consistency.
----End
Related Information
None

4.243 SYSPARA_CFDB_NOSAME
Description
The SYSPARA_CFDB_NOSAME is an alarm indicating the difference between the SCC data
and the CF card data. Back up the data from the SCC to the CF card: In the first startup, the SCC
performs the consistency check between the SCC data and the CF card data. If not consistent,
the SCC does not perform the timing backup before reporting this alarm. If consistent, the SCC
starts the timing backup.
Attribute
Minor Process alarm
Parameters
None

The data in the system parameter area are not consistent with that saved in the CF card. The data
cannot be recovered from the CF card.
Possible Causes
The SCC data and the CF card data are not consistent upon the first startup.
Procedure
Step 1 Wait for the next backup period so that the NE database automatically backs up data to the CF
card and the alarm is cleared.
----End
Related Information
None
4.244 SYSLOG_COMM_FAIL
Description
The communication between an NE and the syslog server fails. The alarm is generated when
the session or the connection between an NE and the syslog server is abnormal.

Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicates the address of the syslog server.
Parameter 5 Indicates the type of the fault that causes the alarm. 0x0a indicates that the
connection fails. 0x02 indicates that the session is abnormal.

There is no impact on services, and no bit error is generated. But you can not find the syslog
server.
Possible Causes
In the TCP mode, the connection between an NE and the syslog server or the session between
servers is abnormal.
Procedure
Step 1 Check whether the board is returned for repair or not. If yes, there is no need to handle the alarm.
Step 2 Select the Start Syslog Service check box.
----End
Related Information
None
4.245 T_LOSEX
Description
The T_LOSEX is an alarm indicating that a board has detected the loss of signals in the service
bus of the backplane. If the board has detected that the service bus of the backplane is in the
LOS state, the T_LOSEX alarm is reported.

Attribute
Parameters
None

When the T_LOSEX alarm is generated, the services of a board are interrupted. Consequently,
the board fails to work normally.
Possible Causes
The possible causes of the T_LOSEX alarm are as follows:
l The service board is improperly inserted.
l The cross-connect board is improperly inserted.
l The clock source of the working and protection cross-connect boards fails to work or is of
poor quality.
Procedure
Step 1 View the T_LOSEX alarm on the U2000 to determine the relevant board.
Step 2 Make sure that the board is firmly inserted and properly installed, and then check whether the
T_LOSEX alarm is cleared. If the alarm persists, go to the next step.
Step 3 Make sure that the cross-connect board is firmly inserted and properly installed, and then check
whether the T_LOSEX alarm is cleared. If the alarm persists, go to the next step.
Step 4 Replace the cross-connect board that reports the alarm, and then check whether the T_LOSEX
alarm is cleared. If the alarm persists, go to the next step.
Step 5 Replace the board that reports the T_LOSEX alarm.
----End
Related Information
None
4.246 T_SLIP
Description
The T_SLIP is an alarm indicating that slip frames occur on the transmitted side.. The alarm
occurs when the phase deviation occurs on the transmitted service frames of the board.

Attribute
Parameters
None

Bit errors occur in the client services, which can cause a service break when it gets severe.
Possible Causes
The clock signals are not synchronous.
Procedure
Step 1 Perform cold reset on the faulty board through the U2000 or remove the faulty board. For details,
----End
Related Information
None
4.247 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is excessively high. This alarm
occurs when the laser temperature is higher than the upper laser temperature threshold.
Attribute
Parameters
None


When the temperature of the tube core of the optical module is excessively high, the working
wavelengths of the optical module and the client services are affected.
Possible Causes
l The working temperature of the board is excessively high.
l The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature and ventilation of the equipment room. If the board
ambient temperature is excessively high, cool the equipment room with cooling devices, such
as an air conditioner.
----End
Related Information
None
4.248 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is excessively low. This alarm
occurs when the laser temperature is lower than the lower threshold of the laser temperature.
Attribute
Parameters
None

This has impact on the working wavelengths of the optical module and affects the client services.

Possible Causes
l Working temperature of the board is excessively low.
l The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature. If it is excessively low, increase it.
----End
Related Information
None
4.249 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature crosses the threshold.
This alarm occurs, when the system detects that the board working temperature is higher than
the upper threshold or lower than the lower threshold.
Attribute
Parameters

The excessively high or low temperature puts the system in a highly dangerous state. If the
system runs in this state for a long time, bit errors may be generated and services may be
interrupted. Hence, the TEMP_OVER alarm must be handled in time.

Possible Causes
The possible causes of the TEMP_OVER alarm are as follows:
l Cause 1: The fan stops working or the air filter is excessively dusty.
Identification method: Query the alarms through the U2000.
l Cause 2: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
Identification method: Check the external environment.
l Cause 3: The fan is not in position.
Identification method: Query the board status or alarms through the U2000.
Procedure
l Cause 1: The fan stops working or the air filter is excessively dusty.
1. See Querying Board Temperature in the Supporting Task to check the current
temperature of the board. If the temperature is abnormal, check whether the
FAN_FAIL alarm exists. If such alarm exists, clear the alarm first.
2. Then, check whether the TEMP_OVER alarm is cleared. If the alarm persists, check
whether the air filter is excessively dusty, thus causing the problem of heat dissipation.
You can feel the wind and the temperature of the wind at the air exhaust vent.
3. If the problem is caused by dusty the air filter, remove the air filter and clean it. For
details, see Cleaning the Air Filter in the Supporting Task.
4. Then, check whether the alarm is cleared. If the alarm persists, see Cause 2.
l Cause 2: The ambient temperature is excessively high or low because of the cooler or heater
fault.
1. Check whether the ambient temperature of the equipment room is higher than 45°C
or lower than 0°C. 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.
NOTE
The TEMP_OVER alarm is cleared when the board temperature is 5°C lower than the upper
threshold or 5°C higher than the lower threshold so that intermittent TEMP_OVER alarms can
be prevented.
l Cause 3: The fan is not in position.
1. Check whether the NE reports the BD_STATUS alarm or check whether the fan is in
position on the U2000. If the fan is not in position, place it firmly.
1. Replace the board that reports the alarm. For details, see the Parts Replacement.
----End

Related Information
None
4.250 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that the board is in the test state.
Attribute
Warning Processing alarm
Parameters
None

The test commands, which can be issued only when the board is in the test status, may have an
impact on the system.
Possible Causes
A command is issued for the board to enter the test state.
Procedure
Step 1 View the TEST_STATUS alarm on the U2000 to determine the relevant board.
Step 2 When a command is issued to end the test state, the TEST_STATUS alarm is automatically
cleared. However, this does not eliminate the system impact that arose during the test state of
the board. To ensure that the commands issued during the test state no longer affect the system,
perform cold reset on the board.
----End
Related Information
None

4.251 THUNDERALM
Description
The THUNDERALM is an alarm indicating a lighting protection circuit failure.
The alarm is generated when the PIU board detects a surge protection circuit failure of the PIU
board.
Attribute
Parameters
Parameter 1 Indicates the number of the unit that reports the alarm. For example,
0x01 indicates the PIU1 unit.
0x02 indicates the PIU2 unit.

The surge protection performance of the system is degraded. If the equipment is attacked by a
strong current (for example, a strong lightning stroke), the board in the subrack may be
unavailable. As a result, the services are interrupted.
Possible Causes
l The equipment is attacked by a strong lighting stroke (the common mode current is larger
than 5000 A and the differential mode current is larger than 3000 A). As a result, the surge
protection component on the PIU board is unavailable and the circuit is broke due to the
automatic protection of the fuse. Hence, the PIU detects the failure and reports this alarm.
Procedure
Step 1 Replace the faulty PIU board. For details, see the Parts Replacement.
----End

Related Information
In the stormy weather, intensive electromagnetic fields form in the air. To protect the equipment
against the lightning stroke, the equipment must be grounded during installation.
4.252 TIME_LOS
Description
The TIME_LOS is an alarm indicating the loss of the time source level. This alarm is generated
when the time source state does not exist after the precision time function is enabled.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. The parameter
of the alarm is displayed in the brackets in the Details area. The parameter is in the hexadecimal
format and is described as follows:
l When the parameter contains six numbers, it indicates that the time source of the service
board is in subrack 0. The first and second numbers indicate the ID of the slot where the
time source of the service board is located in the subrack. The third to sixth numbers indicate
the number of port where the time source of the service board is located in the subrack. For
example, if the parameter value is 120001, the time source of the service board is located
at port 1 of the board in slot 18 in subrack 0.
l When the parameter contains seven numbers, the first number indicates the ID of the
subrack where the time source of the service board is located. The second and third numbers
indicate the ID of the slot where the time source of the service board is located in the subrack.
The fourth to seventh numbers indicate the number of port where the time source of the
service board is located in the subrack. For example, if the parameter value is 1120001, the
time source of the service board is located at port 1 of the board in slot 18 in subrack 1.

When the alarm is reported, the time between the upstream and downstream NEs cannot be
synchronous, which may affect the quality of the service.
Possible Causes
The possible causes of the TIME_LOS alarm are as follows:
l Cause 1: There are fiber failures or misconnections.


Procedure
1. Check the fiber connections. Check whether there are optical interface alarms, such
as R_LOS and R_LOF. If there are optical interface alarms, clear the alarms first.
1. If the alarm persists, perform cold reset on the relevant service board, and then check
whether the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
Replacement.
2. If the alarm persists, replace the clock board.
----End
Related Information
None
4.253 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the time enters the non-trace mode.
The precision time of the board is in the non-trace mode. This alarm is generated when the board
traces the internal source after the precision time function is enabled.
Attribute
Parameters
None

When the alarm is reported, the time between the upstream and downstream NEs cannot be
synchronous, which may affect the quality of the service.

Possible Causes
The possible causes of the TIME_NO_TRACE_MODE alarm are as follows:
l Cause 1: The priority table is not configured.

l Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
Procedure
l Cause 1: The priority table is not configured.
1. Query the current priority table of the system. If there is only the internal clock source
in the priority table, set the clock source priority table to include other available clock
sources. After the setting, the alarm is automatically cleared. For details, see
Configuring PTP Clock in the Feature Description.
1. Check the fiber connections. Check whether there are optical interface alarms, such
as R_LOS and R_LOF. If there are optical interface alarms, clear the alarms first.
l Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
1. If the alarm persists, check whether the attributes of the packets at the upstream NE
are configured correctly on the U2000. If any error is found, modify the configuration.
For details, see Configuring PTP Clock in the Feature Description.
the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
----End
Related Information
None
4.254 TR_LOC
Description
The TR_LOC is an alarm indicating that the clock of the cross-connect board is faulty. If a board
has detected loss of the clock signal of the cross-connect board, loss of the frame header, or
damage to the cross-connect board, the TR_LOC alarm is reported.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the detailed fault information.
l Bit 0 indicates that the clock of the cross-connect board in the slot with a
smaller number is lost.
l Bit 1 indicates that the frame header of the cross-connect board in the slot
with a smaller number is lost.
l Bit 2 indicates that the bus indicating the status of the cross-connect board in
the slot with a smaller number is faulty.
l Bit 4 indicates that the clock of the cross-connect board in the slot with a
bigger number is lost.
l Bit 5 indicates that the frame header of the cross-connect board in the slot
with a bigger number is lost.
l Bit 6 indicates that the bus indicating the status of the cross-connect board in
the slot with a bigger number is faulty.

When the TR_LOC occurs, the board fails to work normally. If the protection cross-connect
board is faulty, the services are not affected. If the working cross-connect board is faulty, the
services are switched. Consequently, transient service interruption occurs.
Possible Causes
The possible causes of the TR_LOC alarm are as follows:
l The clock line of the cross-connect board is faulty.

l The hardware of the local board is faulty.
Procedure
Step 1 View the TR_LOC alarm at the local station, and check whether the alarm is generated on the
service boards.

l If the TR_LOC alarm is generated on most service boards, the cross-connect board is faulty.
In this case, replace the faulty cross-connect board.
l If only the local board reports the alarm, replace the board.
----End
Related Information
None
4.255 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU alarm indication in the VC-3 lower order path. TU alarm indication
is the AIS at the level of the VC-3 lower order path. If a board has detected that the TU path is
all "1"s, the TU_AIS_VC3 alarm is reported.
Attribute
Parameters
None

When the TU_AIS_VC3 alarm is generated, the VC-3 path services are interrupted.
Possible Causes
The possible causes of the TU_AIS_VC3 alarm are as follows:
l Certain higher-level alarms, such as the R_LOS, R_LOF, HP_SLM, or AU_AIS, occur in
the system.
l The cross-connect and timing board is faulty.
l The relevant path at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is
detected on the U2000. If yes, take priority to clear it, and then check whether the TU_AIS_VC3
Step 2 Perform cold reset on the board that reports the alarm. Then check whether the TU_AIS_VC3

NOTICE
Step 3 Replace the board that reports the alarm, and then check whether the TU_AIS_VC3 alarm is
cleared. If the alarm persists, go to the next step.
Step 4 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check
whether the TU_AIS_VC3 alarm is cleared.
Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether
the TU_AIS_VC3 alarm is cleared.
----End
Related Information
None
4.256 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating the loss of pointer in the VC-3 lower order path. If a
board has detected that the TU-PTR value is an invalid pointer or NDF reversion in eight
consecutive frames, the TU_LOP_VC3 alarm is reported.
Attribute
Parameters
None

When the TU_LOP_VC3 alarm is generated, the VC-3 path services are interrupted.
Possible Causes
The possible causes of the TU_LOP_VC3 alarm are as follows:
l Certain higher-level alarms, such as the R_LOS, R_LOF, HP_SLM, or AU_AIS, occur in
the system.

l The cross-connect and timing board is faulty.

l The relevant path at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is
detected on the U2000. If yes, take priority to clear it, and then check whether the TU_LOP_VC3
Step 2 Perform cold reset on the board that reports the alarm. Then check whether the TU_LOP_VC3
NOTICE
Step 3 Replace the board that reports the alarm, and then check whether the TU_LOP_VC3 alarm is
cleared. If the alarm persists, go to the next step.
Step 4 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check
whether the TU_LOP_VC3 alarm is cleared.
Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether
the TU_LOP_VC3 alarm is cleared.
----End
Related Information
None
4.257 VCAT_LOA
SF64, SF64A, SFD64, SL64, SLD64, 4.257.1 VCAT_LOA(OCS)

Boards other than the SF64, SF64A, SFD64, 4.257.2 VCAT_LOA(OTN)

SLO16, or EGSH

4.257.1 VCAT_LOA(OCS)
Description
The VCAT_LOA is an alarm indicating that the delay of the virtual concatenation is excessively
long. This alarm occurs when the delay time of the timeslots bound to a VCTRUNK exceeds
the time allowed by the virtual concatenation delay. The time allowed by the virtual
concatenation delay varies according to different board types.
Attribute
Critical Processing alarm
Parameters
None

During the service data transmission, when the alignment time of the virtual concatenation delay
is excessively long, the timeslots cannot form a data frame. Accordingly, it causes the packet
loss.
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows:
The configured VCTRUNK timeslots pass physical links of different distances.
Procedure
Step 1 View the VCAT_LOA alarm on the U2000 to determine the relevant board.
Step 2 Configure the timeslots of the VCTRUNK again, so that they pass the same fiber. If they need
to pass different fibers, make sure that the distance difference of the fibers is the shortest.
----End
Related Information
None

4.257.2 VCAT_LOA(OTN)
Description
The VCAT_LOA is an alarm indicating that the delay of multiframes exceeds the threshold. The
alarm is generated when the MFAS value in OTN signals received on the WDM side is not
consistent.
Attribute
Parameters
None

The board is unable to converge the WDM-side services into the client-side 40 Gbit/s services,
which causes that the client-side services are abnormal.
Possible Causes
l The fiber connection on the WDM side is incorrect.
l The board at the upstream or local station is faulty.
Procedure
Step 1 Check whether the fiber connection on the WDM side is correct. If not, re-connect the fibers.
Step 2 Check whether there are abnormal alarms in the WDM-side services. If yes, clear the alarms
according to the proper procedures.
Step 3 If the alarm persists, perform a WDM-side inloop on the upstream board and then on the local
board, to determine which board is faulty.
Step 4 Based on the results, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.258 VCAT_LOM_VC3

Description
The VCAT_LOM_VC3 is an alarm indicating the loss of the virtual concatenation multiframe
in the VC-3 path. This alarm is generated when the system detects that the multiframe indicator
(MFI) field in the H4 byte of the VC-3 timeslot is illegal.
Attribute
Parameters
None

l During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC3 alarm are as follows:
l The virtual concatenation delay is excessively long.

l The MFI field in the K4 byte transmitted from the opposite end is incorrect.
Procedure
Step 1 View the VCAT_LOM_VC3 alarm on the U2000 to determine the relevant board.
Step 2 On the U2000, check whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual
concatenation delay is excessively long. See the procedure for handling the VCAT_LOA alarm
to clear it. After that, check whether the VCAT_LOM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the board that reports the VCAT_LOM_VC3 alarm at the
local end is faulty. Replace the board that reports the alarm at the local station, and then check
whether the VCAT_LOM_VC3 alarm is cleared.
Step 4 If the alarm persists, it indicates that the MFI domain transmitted from the SDH opposite end is
incorrect. Replace the corresponding board at the opposite station, and then check whether the
VCAT_LOM_VC3 alarm is cleared.
----End
Related Information
None
4.259 VCAT_LOM_VC4

Description
The VCAT_LOM_VC4 is an alarm indicating the loss of the virtual concatenation multiframe
in the VC-4 path. This alarm is generated when the system detects that the multiframe indicator
(MFI) field in the H4 byte of the VC-4 timeslot is illegal.
Attribute
Parameters
None

l During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC4 alarm are as follows:
l The virtual concatenation delay is excessively long.

l The MFI field in the K4 byte transmitted from the opposite end is incorrect.
Procedure
Step 1 View the VCAT_LOM_VC4 alarm on the U2000 to determine the relevant board.
Step 2 On the U2000, check whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual
concatenation delay is excessively long. See the procedure for handling the VCAT_LOA alarm
to clear it. After that, check whether the VCAT_LOM_VC4 alarm is cleared.
Step 3 If the alarm persists, check whether the board that reports the VCAT_LOM_VC4 alarm at the
local end is faulty. Replace the board that reports the alarm at the local station, and then check
whether the VCAT_LOM_VC4 alarm is cleared.
Step 4 If the alarm persists, it indicates that the MFI domain transmitted from the SDH opposite end is
incorrect. Replace the corresponding board at the opposite station, and then check whether the
VCAT_LOM_VC4 alarm is cleared.
----End
Related Information
None

4.260 VOA_ADJUST_FAIL
Description
The VOA_ADJUST_FAIL is an alarm indicating that the VOA adjustment fails.
Attribute
Major Process alarm
Parameters

The gain adjustment of the OAU1 fails, which results in failure of command issuing.
Possible Causes
l The external DCM of the OAU1 has excessive attenuation between the input and output
interfaces.
l The OAU1 laser is off.
Procedure
Step 1 Check whether the external DCM of the OAU1 has excessive attenuation between the input and
output interfaces. If yes, adjust it to keep the input and output in a normal range.
Step 2 If the alarm persists, check whether the laser of the OAU1 is on. If not, turn it on.
----End
Related Information
None

4.261 VOADATA_MIS
Description
The VOADATA_MIS is an alarm indicating mismatch of the attenuation attribute. When the
set attenuation value falls beyond the adjustable attenuation range of the board, the alarm is
reported.
Attribute
Parameters
None

Possible Causes
Cause 1: As for the attenuation, replacing the board or the optical module causes that the stored
attenuation value issued by the NE software falls beyond the new adjustable attenuation range
of the board.
Procedure
l Cause 1: The stored attenuation value issued by the NE software falls beyond the new
adjustable attenuation range of the board.
1. Query the adjustable range of the current actual attenuation. Re-set a valid attenuation
value for the optical interface channel of the board based on the queried adjustable
range.
----End
Related Information
None

4.262 W_R_FAILURE
Description
The W_R_FAILURE is an alarm indicating a writing or reading chip register failure. The alarm
occurs when the read value and the written value of the register are not consistent.
Attribute
Parameters
Parameter 1 Indicates the IDs of the board register. For example, 0x01-0x09 indicates the IDs
of the faulty chips that are of different types.

The board cannot work normally. In this case, the services may not be received or transmitted
properly. In addition, the board may fail to query the current performance value.
Possible Causes
The board is faulty.
Procedure
Step 1 Perform warm reset on the faulty board on the U2000. For details, see the Supporting Tasks.
----End
Related Information
None

4.263 WAVEDATA_MIS
Description
The WAVEDATA_MIS is an alarm indicating mismatch of the wavelength or band attribute.
When the configured logic wavelength or band differs with the actual wavelength or band, the
alarm is reported.
Attribute
Parameters
None

The service may be interrupted.
Possible Causes
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
Procedure
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
1. Query the actual wavelength of the unit and the logic wavelength stored on the
U2000. If these two wavelengths differ, reconfigure the operating wavelength of the
corresponding optical interface to make it the same as the fixed wavelength of the
1. If the alarm persists, replace the board or optical module with another one whose
wavelength is the same as that stored in the NE software. For details, see the Parts
Replacement.
----End
Related Information
None

4.264 WAVELEN_OVER
Description
The WAVELEN_OVER is an alarm indicating that the wavelength crosses the threshold. When
the wavelength drift of the OTU board exceeds the threshold, this alarm occurs.
Attribute
Parameters
None

The services carried by the wavelength is degraded or interrupted, and the services carried by
the adjacent wavelengths may be affected.
Possible Causes
l The wavelength drift of the corresponding channel of the OTU board exceeds the upper or
lower threshold.
l The wavelength locking is mis-adjusted because the logical fiber connection is inconsistent
with the physical fiber connection.
l The wavelength locking module on the WMU board or a module on the OTU board is
malfunctioning.
Procedure
Step 1 Check whether the wavelength of the optical interface connecting to the wavelength monitoring
board on the OTU board is within the normal range. If not, the OTU board enables the wavelength
locking function to adjust the monitored wavelength. When the monitored wavelength restores
to a value within the normal range, this alarm is cleared.
Step 2 If the alarm persists, check whether the logical fiber connections are consistent with the physical
fiber connections. If not, modify the logical fiber connections so that the logical fiber connections
are consistent with the physical fiber connections. For details, see Checking Logical Fibers in
Step 3 If the alarm persists, cold reset of the OTU board is required. For details, see the Supporting
Tasks.
Step 4 If the alarm persists, contact Huawei engineers.
----End

Related Information
None
4.265 XC_UNSWITCH
Description
The XC_UNSWITCH is an alarm indicating that the cross-connect matrix of the board is not
switched.
Attribute
Parameters
None

The services related to the board that reports the alarm are interrupted.
Possible Causes
The possible causes of the XC_UNSWITCH alarm are as follows:
l The cross-connect board or the line board fails to respond to the cross-connect matrix
switching command issued by the NE software, and as a result is not updated with the cross-
connect matrix configured by the NE software.
l The board is in the BIOS state, and as a result cannot be updated with the cross-connect
matrix configured by the NE software.
Procedure
Step 1 Check whether the board that reports the alarm has communication alarms. If yes, clear the
communication alarms, and then check whether the XC_UNSWITCH alarm is cleared.
Step 2 If the alarm persists, perform warm reset on the board, and check whether the XC_UNSWITCH
alarm is still generated.
Step 3 If the alarm persists, contact Huawei engineers to re-load the board software.
Step 4 If the alarm persists, replace the board that reports the alarm. For details, see the Parts
Replacement.
----End

Related Information
None

Alarms and Performance Events Reference 5 Performance Event List
5 Performance Event List
About This Chapter
This chapter lists the names, description and relevant boards of the performance event in
alphabetical order and lists the performance event of every board.
5.1 Product Performance Event List

Lists the different types of performance event.
5.2 Board Performance Event List

This section list the performance event of every board.

5.1 Product Performance Event List

Lists the different types of performance event.
5.1.1 Performance Event of Check and Error Correction

Lists of the performance event of check and error correction.
Table 5-1 Performance Event List of Check and Error Correction
Name Description Board
CRC4BBE CRC4 Background block HSC1, SC1, SC2

error
CRC4FEBBE CRC4 Far end

background block error
CRC4ES CRC4 Errored Second
CRC4FEES CRC4 Far End Errored

Second
CRC4FESES CRC4 Far End Severely

Errored Second
CRC4FEUAS CRC4 Far End

Unavailable Second
CRC4SES CRC4 Severely Errored

Second
CRC4UAS CRC4 Unavailable

Second
FEC_AFT_COR_ER After FEC Correct NS2, NS3, NQ2, LSX, LSXR, LQMS,
AVR Average Errored Rate in LQMD, LQM, LOG, LOM, LSXL,
monitor period LSXLR, TMX, LDMS, LDMD, LDM,
TOM, TDX, TQX, ND2, LDX,
FEC_BEF_COR_ER Before FEC Correct SF64A, SF64, SFD64
AVR Average Errored Rate in
monitor period
FEC_AFT_COR_ER After FEC Correct

Errored Rate
FEC_BEF_COR_ER Before FEC Correct

Errored Rate
FEC_COR_0BIT_CN Forward Error Correction

T - Corrected 0 Bit Count
FEC_COR_1BIT_CN Forward Error Correction

T - Corrected 1 Bit Count

FEC_COR_BYTE_C Forward Error Correction

NT - Corrected Byte Count
FEC_UNCOR_BLOC Forward Error Correction

K_CNT - Uncorrected Block
Count
5.1.2 Performance Event of Pointer Justification

This topic lists the performance events for pointer justifications.
Table 5-2 Pointer justification performance event list
AUPJCHIGH Count of positive AU SF64A, SLH41, SLO16, SLQ64,

pointer justifications SF64, SFD64, SL64, SLD64, SLQ16
AUPJCLOW Count of negative AU

pointer justifications
AUPJCNEW Count of new AU pointer

justifications
5.1.3 Performance Event of Equipment Function

Lists the performance event of equipment function.
Table 5-3 Performance Event List of Equipment Function
BCVCUR Average Pump Laser OAU1, OBU1, OBU2,

Backfacet Current Value CRPC, HBA
BCVMAX Maximum Pump Laser

Backfacet Current Value
BCVMIN Minimum Pump Laser

Backfacet Current Value
CCVCUR Average Pump Laser OAU1, OBU1, OBU2,

Cooling Current Value CRPC, HBA
CCVMAX Maximum Pump Laser

Cooling Current Value

CCVMIN Minimum Pump Laser

Cooling Current Value
EDTMPCUR Current Laser Temperature OAU1, OBU1, OBU2, HBA

Value
EDTMPMAX Maximum Laser

Temperature Value
EDTMPMIN Minimum Laser

Temperature Value
EDTPLCUR Current Laser Output Optical CRPC

Power Value
EDTPLMAX Maximum Laser Output

Optical Power Value
EDTPLMIN Minimum Laser Output

Optical Power Value
ENVTMPCUR Current Environmental CRPC

Temperature Value
ENVTMPMAX Maximum Environmental

Temperature Value
ENVTMPMIN Minimum Environmental

Temperature Value
ICCLCCUR Current Module Cooling M40, D40

Current Value
ICCLCMAX Maximum Module Cooling

Current Value
ICCLCMIN Minimum Module Cooling

Current Value
ICTMPCUR Current Module Temperature M40V, D40V, RMU9, VA4,

Value VA1, ROAM, WSM9,
WSD9, M40, D40, WSMD4,
ICTMPMAX Maximum Module WSMD2
Temperature Value
ICTMPMIN Minimum Module

Temperature Value
LSBIASCUR Current Laser Bias Current NS2, NS3, NQ2, LWXS,

Value LSX, LSXR, LQMS,
LQMD, LQM, LOG, LOM,
LSBIASMAX Maximum Laser Bias LSXL, LSXLR, TMX, TDX,
Current Value SC1, SC2, LDMS, LDMD,

LSBIASMIN Minimum Laser Bias Current LDM, TOM, TQX, ND2,

Value HSC1, LDX, EGSH, TOG
LSCLCCUR Current Laser Cooling LWXS, LQMS, LQMD,

Current Value LOG, LOM, LSXL, LSXLR,
TMX, LDMS, LDMD, TQX,
LSCLCMAX Maximum Laser Cooling NQ2, TDX, LDX, NS3
Current Value
LSCLCMIN Minimum Laser Cooling

Current Value
LSIOPCUR Current Input Optical Power NS2, NS3, NQ2, LWXS,

LSIOPMAX Maximum Input Optical LSXL, LSXLR, TMX, TDX,
Power Value SC1, SC2, LDMS, LDMD,
LSIOPMIN Minimum Input Optical LDM, TOM, TQX, ND2,
Power Value EGSH, HSC1, LDX, TOG,
DCP, OLP
LSOOPCUR Current Output Optical NS2, NS3, NQ2, LWXS,

Power Value LSX, LSXR, LQMS,
LQMD, LQM, ROAM,
LSOOPMAX Maximum Output Optical LOG, LOM, LSXL, LSXLR,
Power Value TMX, TDX, SC1, SC2,
LSOOPMIN Minimum Output Optical LDMS, LDMD, LDM,
Power Value TOM, TQX, ND2 , EGSH,
HSC1, LDX, TOG
LSTMPCUR Current Laser Temperature NS2, NS3, NQ2, LWXS,

LSTMPMAX Maximum Laser LSXL, LSXLR, TMX, TDX,
Temperature Value LDMS, LDMD, LDM,
LSTMPMIN Minimum Laser TOM, TQX, ND2, EGSH,
Temperature Value LDX, TOG
OSPICCVCUR Average value of laser SF64A, SLH41, SLO16,

cooling current SLQ64, SF64, SFD64, SL64,
SLD64, SLQ16
OSPICCVMAX Maximum value of laser
cooling current
OSPICCVMIN Minimum value of laser

cooling current
OSPITMPCUR Current value of laser SF64A, SLH41, SLO16,

working temperature SLQ64, SF64, SFD64, SL64,
SLD64, SLQ16
OSPITMPMAX Maximum value of laser
working temperature

OSPITMPMIN Minimum value of laser

working temperature
RPLCUR Current value of input optical SF64A, SLH41, SLO16,

power SLQ64, SF64, SFD64, SL64,
SLD64, SLQ16
RPLMAX Maximum value of input
optical power
RPLMIN Minimum value of input

optical power
PCLSOPCUR Current Per-Channel Laser MCA4, MCA8, WMU

Output Power Value
PCLSSNCUR Current Per-Channel OSNR MCA4, MCA8

Value
PCLSWLCUR Current Per-Channel Central MCA4, MCA8, WMU

Wavelength Value
PCLSWLOCUR Current Per-Channel Central MCA4, MCA8

Wavelength
SUMIOPCUR Current Total Input Optical D40V, RMU9, VA1,

Power Value ROAM, WSD9, D40, OAU1,
OBU1, OBU2, OLP, FIU,
SUMIOPMAX Maximum Total Input WSMD4, HBA, RDU9,
Optical Power Value WSMD2
SUMIOPMIN Minimum Total Input
Optical Power Value
SUMOOPCUR Current Output Optical M40, M40V, RMU9,

Power Value ROAM, WSM9, OAU1,
OBU1, OBU2, WSMD4,
SUMOOPMAX Maximum Total Output HBA, RDU9, WSMD2
Optical Power Value
SUMOOPMIN Minimum Total Output

Optical Power Value
TLBCUR Current value of laser bias SF64A, SLH41, SLO16,

current SLQ64, SF64, SFD64, SL64,
SLD64, SLQ16
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
WCVCUR Current value of pump laser OAU1, OBU1, OBU2,

working current CRPC, HBA
WCVMAX Maximum value of pump

laser working current
WCVMIN Minimum value of pump

laser working current
XCSTMPCUR Current Environmental NS2, NS3, NQ2, LWXS,

Temperature Value LSX, LSXR, LQMS,
XCSTMPMAX Maximum Environmental LSXL, LSXLR, TMX, TDX,
Temperature Value MCA4, MCA8, M40V,
XCSTMPMIN Minimum Environmental D40V, RMU9, VA4, VA1,
Temperature Value ROAM, WSM9, WSD9,
WSMD4, OAU1, M40, D40,
OBU1, OBU2, HBA, FIU,
DCP, OLP, SC1, SC2,
WMU, ITL, LDMS, LDMD,
LDM, TDC, TOM, TQX,
ND2, EGSH, HSC1, LDX,
MR8V, ND2, RDU9,
SLQ64, STG, SF64, SFD64,
SL64, SLD64, SLQ16, SXM,
TOG, WSMD2, XCH,
XCM,
5.1.4 Performance Event of Multiplex Section Bit Error

Lists performance event of multiplex section bit error.
Table 5-4 Performance Event list of Multiplex Section Bit Error
MSBBE MS Background Block Error SF64A, SLH41, SLO16,

MSCSES MS Consecutive severely SLD64, SLQ16
errored second
MSES MS Errored Second

MSFEBBE MS Far End Background

Block Error
MSFEES MS Far End Errored Second
MSFESES MS Far End Severely Errored

Second
MSFEUAS MS Far End Unavailable

Second
MSSES MS Severely Errored Second
MSUAS MS Unavailable Second
5.1.5 Performance Event of Regenerator Section Bit Error

Lists the performance event of Regenerator Section Bit Error.
Table 5-5 Performance Event List of Regenerator Section Bit Error
RSBBE RS Background Block LWXS, LSX, LQMS, LQMD, LQM,

Error LSXL, TMX, TDX, LDMS, LDMD,
LDM, TOM, TQX, LDX, SF64A,
SFD64, SL64, SLD64, SLQ16
RSCSES RS Consecutive Severely LWXS, LSX, LQMS, LQMD, LQM,

Errored Second LSXL, TMX, TDX, LDMS, LDMD,
RSES RS Errored Second LWXS, LSX, LQMS, LQMD, LQM,

LSXL, TMX, TDX, LDMS, LDMD,
RSOFS RS Out-of-Frame Second LWXS, LSX, LSXL, TMX, TDX,

TQX, LDX, SF64A, SLH41, SLO16,
SLQ64, SF64, SFD64, SL64, SLD64,
SLQ16
RSOOF Regenerator section of SF64A, SLH41, SLO16, SLQ64,

OOF perferance seconds SF64, SFD64, SL64, SLD64, SLQ16

RSSES RS Severely Errored LWXS, LSX, LQMS, LQMD, LQM,

Second LSXL, TMX, TDX, LDMS, LDMD,
RSUAS RS Unavailable Second LWXS, LSX, LQMS, LQMD, LQM,

LSXL, TMX, TDX, LDMS, LDMD,
5.1.6 Performance Event of Higher Order Path Bit Error

This topic lists the performance events for the bit errors in the higher order paths.
Table 5-6 Higher order path performance event list
HPBBE Higher order path block of EGSH, SF64A, SLH41, SLO16,

background error SLQ64, SF64, SFD64, SL64, SLD64,
SLQ16
HPES Higher order path errored
second
HPSES Higher order path

severely errored second
HPUAS Higher order path far end

unavailable second
HPFEBBE Higher order path far end

block of background error
HPFEES Higher order path far end

errored second
HPFESES Higher order path far end

HPFEUAS Higher order path far end

consecutive severely
errored second
5.1.7 Performance Event of Lower Order Path Bit Error

This topic lists the performance events for the bit errors in the lower order paths.

Table 5-7 Lower order path performance event list
VC3BBE VC3 block of background EGSH

error
VC3ES VC3 errored second
VC3SES VC3 severely errored

second
VC3UAS VC3 unavailable second
VC3CSES VC3 consecutive severely

errored second
VC3FEBBE VC3 far end block of

background error
VC3FEES VC3 far end errored

second
VC3FESES VC3 far end severely

errored second
VC3FECSES VC3 far end consecutive

VC3FEUAS VC3 far end unavailable

second
5.1.8 Performance Event of OTN

List the three sections performance Event of OTN. It include: Path Monitoring (PM) section,
Tandem Connection Monitoring (TCM) section and Section Monitoring (SM).
Performance Event of PM Section
Table 5-8 Performance Event of PM Section
ODU1_PM_BBE ODU1 PM Section NQ2, NS2, LQMS, LQMD,

Background Block Error LQM, TMX, LDMS,
LDMD, LDM, TOM, ND2,
ODU1_PM_BBER ODU1 PM Section Ratio of TOG
Background Block Error
ODU1_PM_ES ODU1 PM Section Errored

Second

ODU1_PM_FEBBE ODU1 PM Section Far End

ODU1_PM_FEBBER ODU1 PM Section Ratio of

Far End Background Block
Error
ODU1_PM_FEES ODU1 PM Section Far End

Errored Second
ODU1_PM_FESES ODU1 PM Section Far End

Severely Errored Second
ODU1_PM_FESESR ODU1 PM Section Ratio of

Far End Severely Errored
Second
ODU1_PM_FEUAS ODU1 PM Section Far End

Unavailable Second
ODU1_PM_SES ODU1 PM Section Severely

Errored Second
ODU1_PM_SESR ODU1 PM Section Ratio of

ODU1_PM_UAS ODU1 PM Section

Unavailable Second
ODU2_PM_BBE ODU2 PM Section NQ2, NS2, NS3, LSX,

Background Block Error LSXR, LOG, LOM, TMX,
TDX, TQX, ND2, LDX
ODU2_PM_BBER ODU2 PM Section Ratio of

Second
ODU2_PM_FEBBE ODU2 PM Section Far End


Error

Errored Second

ODU2_PM_FESESR ODU2 PM Section Ratio of

Second


Unavailable Second

Errored Second


Unavailable Second
ODU3_PM_BBE ODU3 PM Section LSXL, LSXLR, NS3

ODU3_PM_BBER ODU3 PM Section Ratio of


Second
ODU3_PM_FEBBE ODU3 PM Section Far End LSXL, LSXLR, NS3


Error

Errored Second

ODU3_PM_FESESR ODU3 PM Section Ratio of LSXL, LSXLR, NS3

Second

Unavailable Second

Errored Second


Unavailable Second

Performance Event of TCM Section
Table 5-9 Performance Event of TCM Section
ODU1_TCMn_BBE ODU1 TCMn Section NQ2, NS2, LQMS, LQMD,

Background Block Error LQM, TMX, LDMS, LDMD,
LDM, TOM, ND2
ODU1_TCMn_BBER ODU1 TCMn Section Ratio
of Background Block Error
ODU1_TCMn_BIAES ODU1 TCMn Section

Background Introduced
Alignment Errored Second
ODU1_TCMn_ES ODU1 TCMn Section

Errored Second
ODU1_TCMn_FEBBE ODU1 TCMn Section Far

End Background Block Error
ODU1_TCMn_FEBBER ODU1 TCMn Section Ratio

of Far End Background
Block Error
ODU1_TCMn_FEES ODU1 TCMn Section Far

End Errored Second
ODU1_TCMn_FESES ODU1 TCMn Section Far

End Severely Errored
Second
ODU1_TCMn_FESESR ODU1 TCMn Section Ratio

of Far End Severely Errored
Second
ODU1_TCMn_FEUAS ODU1 TCMn Section Far

End Unavailable Second
ODU1_TCMn_IAES ODU1 TCMn Section

Introduced Alignment
Errored Second
ODU1_TCMn_SES ODU1 TCMn Section

ODU1_TCMn_SESR ODU1 TCMn Section Ratio

of Severely Errored Second
ODU1_TCMn_UAS ODU1 TCMn Section

Unavailable Second
ODU2_TCMn_BBE ODU2 TCMn Section NQ2, NS2, LSX, LSXR,

Background Block Error LOG, LOM, TMX, ND2,
LDX, NS3, TDX, TQX



ODU2_TCMn_ES ODU2 TCMn Section

Errored Second


Block Error
ODU2_TCMn_FEES ODU2 TCMn Section Far

End Errored Second

Second

Second
ODU2_TCMn_FEUAS ODU2 TCMn Section Far


Errored Second



Unavailable Second
ODU2PMBIP8 Number of bit errors in the SF64A, SF64, SFD64

optical channel data unit
ODU3_TCMn_BBE ODU3 TCMn Section LSXL, LSXLR, NS3




ODU3_TCMn_ES ODU3 TCMn Section LSXL, LSXLR, NS3

Errored Second


Block Error
ODU3_TCMn_FEES ODU3 TCMn Section Far LSXL, LSXLR, NS3

End Errored Second

Second

Second
ODU3_TCMn_FEUAS ODU3 TCMn Section Far LSXL, LSXLR, NS3


Errored Second



Unavailable Second
Performance Event of SM Section
Table 5-10 Performance Event of SM Section
OTU1_BBE OTU1 SM Section LQMS, LQMD, LQM,

Background Block Error TMX, LDMS, LDMD,
LDM, TOM, ND2

OTU1_BBER OTU1 SM Section Ratio of

OTU1_BIAES OTU1 SM Section

OTU1_ES OTU1 SM Section Errored LQMS, LQMD, LQM,

Second TMX, , LDMS, LDMD,
LDM, TOM, ND2
OTU1_FEBBE OTU1 SM Section Far End
OTU1_FEBBER OTU1 SM Section Ratio of

Error
OTU1_FEES OTU1 SM Section Far End LQMS, LQMD, LQM,

Errored Second TMX, LDMS, LDMD,
LDM, TOM, ND2
OTU1_FESES OTU1 SM Section Far End
OTU1_FESESR OTU1 SM Section Ratio of

Second
OTU1_FEUAS OTU1 SM Section Far End LQMS, LQMD, LQM,

Unavailable Second TMX, LDMS, LDMD,
LDM, TOM, ND2
OTU1_IAES OTU1 SM Section
Errored Second
OTU1_SES OTU1 SM Section Severely

Errored Second
OTU1_SESR OTU1 SM Section Ratio of

OTU1_UAS OTU1 SM Section

Unavailable Second
OTU2_BBE OTU2 SM Section NQ2, NS2, LSX, LSXR,

Background Block Error LOG, LOM, TMX, ND2,
LDX, TDX, TQX


OTU2_ES OTU2 SM Section Errored

Second


Error
OTU2_FEES OTU2 SM Section Far End

Errored Second
OTU2_FESES OTU2 SM Section Far End


Second
OTU2_FEUAS OTU2 SM Section Far End

Unavailable Second

Errored Second
OTU2_SES OTU2 SM Section Severely

Errored Second


Unavailable Second
OTU2SMBIP8 Number of bit errors in the SF64A, SF64, SFD64

optical channel transport unit
OTU3_BBE OTU3 SM Section LSXL, LSXLR, NS3



OTU3_ES OTU3 SM Section Errored LSXL, LSXLR, NS3

Second



Error
OTU3_FEES OTU3 SM Section Far End

Errored Second
OTU3_FESES OTU3 SM Section Far End LSXL, LSXLR, NS3


Second
OTU3_FEUAS OTU3 SM Section Far End

Unavailable Second

Errored Second
OTU3_SES OTU3 SM Section Severely LSXL, LSXLR, NS3

Errored Second


Unavailable Second
5.1.9 Performance Event List of RMON Function

Lists the performance event of RMON function.
Table 5-11 RMON Performance Event List
ETHDROP Drop Events EGSH, LQMS, LQMD,

LOG, LOM, TOM, TOG
RXOCTETS Octets Received LSX, TDX, TQX, EGSH,

LDX
RXPKTS Packets Received LSX, TDX, TQX, EGSH,

LDX

RXBRDCAST Broadcast Packets Received LSX, LQMS, LQMD, TDX,

LOG, LOM, LDMS, LDMD,
LDM, LQM, TOM, EGSH,
LDX, TOG, TQX
RXMULCAST Multicast Packets Received LSX, LQMS, LQMD, TDX,

LDX, TOG, TQX
ETHCRCALI FCS and Alignment Errors EGSH, LQMS, TDX
ETHUNDER Undersize Packets Received LSX, LQMS, LQMD, TDX,

LDM, LQM, TOM, TQX,
EGSH, LDX, TOG
ETHOVER Oversize Packets Received LSX, LQMS, LQMD, TDX,

LDM, LQM, TOM, TQX,
EGSH, LDX, TOG
ETHFRG Fragments LSX, LQMS, LQMD, TDX,

LDX, TOG, TQX
ETHJAB Jabbers LSX, LQMS, LQMD, TDX,

LDX, TOG, TQX
RXPKT64 Packets Received (64 Octets LSX, LQMS, LQMD, TDX,

in Length) LOG, LOM, LDMS, LDMD,
RXPKT65 Packets Received (65~127 LDX, TOG, TQX
Octets in Length)
RXPKT128 Packets Received (128~255

Octets in Length)

Octets in Length)

Octets in Length)
RXPKT1024 Packets Received

(1024~1518 Octets in
Length)

RXPKT1519 Packets Received LQMS, LQMD, TDX, LOG,

(1519~MTU Octets in LOM, LDMS, LDMD,
Length) LDM, LQM, TOM, TOG,
TQX
PKT64 Packets Received and EGSH

Transmitted (64 Octets in
Length)
PKT65 Packets Received and

Transmitted (65~127 Octets
in Length)

in Length)

in Length)

Transmitted (512~1023
Octets in Length)

Transmitted (1024~1518
Octets in Length)
TXFULLBGOOD Good Full Frame Octets EGSH

Transmitted
RXFULLBGOOD Good Full Frame Octets

Received
TXGOODFULLFRAME- Good Full Frame Speed

SPEED Transmitted
RXGOODFULLFRAME- Good Full Frame Speed

SPEED Received
VCG_TXGOODPACKETS Good Packets Transmitted
VCG_RXGOODPACKETS Good Packets Received
VCG_TXSPEED Full Frame Speed

Transmitted
VCG_RXSPEED Full Frame Speed Received
TXPKT64 Packets Transmitted (64 LSX, LQMS, LQMD, TDX,

Octets in Length) LOG, LOM, LDMS, LDMD,
LDX, TQX

TXPKT65 Packets Transmitted (65~127

Octets in Length)
TXPKT128 Packets Transmitted

(128~255 Octets in Length)



(1024~1518 Octets in
Length)
TXPKT1519 Packets Transmitted LQMS, LQMD, TDX, LOG,

(1519~MTU Octets in LOM, LDMS, LDMD,
Length) LDM, LQM, TOM, TQX
RXUNICAST Unicast Packets Received LSX, LQMS, LQMD, TDX,

LDX, TQX, TOG
TXUNICAST Unicast Packets Transmitted LSX, LQMS, LQMD, TDX,

TXMULCAST Multicast Packets LDM, LQM, TOM, EGSH,
Transmitted LDX, TQX
TXBRDCAST Broadcast Packets
Transmitted
RXPAUSE Pause Frames Received LSX, LQMS, LQMD, TDX,

LDX, TQX, TOG
TXPAUSE Pause Frames Transmitted LSX, LQMS, LQMD, TDX,

LDX, TQX
RXBGOOD (RXBOK) Good Octets Received LQMS, LQMD, TDX, LOG,

LOM, LDMS, LDMD,
LDM, LQM, TOM, TOG
TXBGOOD (TXBOK) Good Octets Transmitted LQMS, LQMD, TDX, LOG,

LOM, LDMS, LDMD,
LDM, LQM, TOM

RXBBAD Bad Octets Received LQMS, LQMD, TDX, LOG,

LOM, LDMS, LDMD,
LDM, LQM, TOM, TOG,
TQX
TXBBAD Bad Octets Transmitted LQMS, LQMD, TDX, LOG,

LOM, LDMS, LDMD,
LDM, LQM, TOM, TQX
ETHALI Alignment Errors LSX, LQMS, LQMD,

LDMS, LDMD, LDM,
LQM, LDX, TDX, TQX
ETHFCS FCS Errors LSX, TDX, LOG, LOM,

TQX, TOM, EGSH, LDX,
TOG
RXCTLPKTS Control Frames Received EGSH, TDX, TQX
TXCTLPKTS Control Frames Transmitted EGSH, TDX, TQX
TXETHDROP Drop Events at Transmission LQMS, LQMD, LOM,

Direction LDMS, LDMD, LDM,
LQM, TOM
TXETHOVER Oversize Packets LQMS, LQMD, TDX, LOM,

Transmitted LDMS, LDMD, LDM,
LQM, TOM, TQX
TXPKTS Packets Transmitted LSX, EGSH, LDX, TDX,

TQX
TXOCTETS Octets Transmitted LSX, EGSH, LDX, TDX,

TQX
5.1.10 TCM Performance Event

TCM performance events are used to monitor the transmission performance in the tandem
connection.
Table 5-12 TCM performance event list
TCBBE Tandem Connection SF64A, SLH41, SLO16, SLQ64, SF64

TCFEBBE Tandem Connection Far

End Background Block
Error

TCOBBE Tandem Connection

Outgoing Background
Block Error
5.1.11 Performance Event of FC

Lists of the performance event of FC service.
Name Board
CLIENT_CRC_ERR LOM
FC_Client_CreditZero_Cnt
FC_Client_Invld_10BCode_Cnt
CLIENT_RXBYTECNT_SUM
CLIENT_RXFRMCNT_C1
CLIENT_RXFRMCNT_C2
CLIENT_RXFRMCNT_C3
CLIENT_RXFRMCNT_C4
CLIENT_RXFRMCNT_CF
CLIENT_RXFRMCNT_SUM
FC_Client_Rx_NOS_Cnt
FC_Client_Rx_Utilization
FC_Client_OverLongFrm_Sum
FC_Client_RxLRPrim_Cnt
FC_Client_RxLRRPrim_Cnt
FC_Client_RxOLSPrim_Cnt
FC_Client_Truncated FrmCnt_sum
FC_Client_Tx_NOS_Cnt
FC_Client_Tx_Utilization
CLIENT_TXBYTECNT_SUM
CLIENT_TXFRMCNT_C1
CLIENT_TXFRMCNT_C2

Name Board
CLIENT_TXFRMCNT_C3
CLIENT_TXFRMCNT_C4
CLIENT_TXFRMCNT_CF
CLIENT_TXFRMCNT_SUM
CLIENT_UNSUPOS_CNT
FC_Client_TxLRPrim_Cnt
FC_Client_TxLRRPrim_Cnt
FC_Client_TxOLSPrim_Cnt
LINKTST_CNT
FC_Wsys_Crc_Err_Cnt
FC_Wsys_LinkDown_Cnt
FC_Wsys_OverLongFrm_Sum
FC_Wsys_Rx_PausePrim_Cnt
FC_Wsys_Rx_PingAckPrim_Cnt
FC_Wsys_Rx_PingPrim_Cnt
FC_Wsys_Rx_ResumePrim_Cnt
FC_Wsys_Truncated FrmCnt_sum
FC_Wsys_Tx_PausePrim_Cnt
FC_Wsys_Tx_PingAckPrim_Cnt
FC_Wsys_Tx_PingPrim_Cnt
FC_Wsys_Tx_ResumePrim_Cnt
FC_Wsys_unsupos_cnt
5.2 Board Performance Event List

This section list the performance event of every board.
5.2.1 CRPC Board Performance Event List

BCVCUR CCVMIN ENVTMPMAX
BCVMAX EDTPLCUR ENVTMPMIN

BCVMIN EDTPLMAX WCVCUR
CCVCUR EDTPLMIN WCVMAX
CCVMAX ENVTMPCUR WCVMIN
5.2.2 D40V Board Performance Event List

ICTMPCUR SUMIOPCUR XCSTMPCUR
ICTMPMAX SUMIOPMAX XCSTMPMAX
ICTMPMIN SUMIOPMIN XCSTMPMIN
5.2.3 D40 Board Performance Event List

ICCLCCUR ICTMPMAX SUMIOPMIN
ICCLCMAX ICTMPMIN XCSTMPCUR
ICCLCMIN SUMIOPCUR XCSTMPMAX
ICTMPCUR SUMIOPMAX XCSTMPMIN
5.2.4 DCP Board Performance Event List

LSIOPCUR LSIOPMIN XCSTMPMAX
LSIOPMAX XCSTMPCUR XCSTMPMIN
5.2.5 EGSH Board Performance Event List

HPBBE LSBIASMIN VC3ES
HPES LSIOPCUR VC3FEBBE
HPCSES LSIOPMAX VC3FECSES
HPFEBBE LSIOPMIN VC3FEES
HPFEES LSOOPCUR VC3FESES
HPFECSES LSOOPMAX VC3FEUAS

HPFESES LSOOPMIN VC3SES
HPFEUAS LSTMPCUR VC3UAS
HPSES LSTMPMAX XCSTMPCUR
HPUAS LSTMPMIN XCSTMPMAX
LSBIASCUR VC3BBE XCSTMPMIN
LSBIASMAX VC3CSES
RMON Performance Event List
Broadcast Packets Multicast Packets Received Packets Received(64 Octets in

Transmitted Length)
Broadcast Packets Multicast Packets Transmitted Packets Received(65~127

Received Octets in Length)
Control Frames Octets Received Packets Transmitted

Received
Control Frames Octets Transmitted Packets Transmitted

Transmitted (1024~1518 Octets in Length)
Drop Events Oversize Packets Received Packets Transmitted(128~255

Octets in Length)
FCS Errors Packets Received Packets Transmitted(256~511

Octets in Length)
Fragments Packets Received and Transmitted Packets Transmitted

(1024~1518 Octets in Length) (512~1023 Octets in Length)
Full Frame Speed Packets Received and Transmitted Packets Transmitted(64 Octets
Received (128~255 Octets in Length) in Length)
Full Frame Speed Packets Received and Transmitted Packets Transmitted(65~127

Transmitted (256~511 Octets in Length) Octets in Length)
Good Full Frame Packets Received and Transmitted Pause Frames Transmitted
Octets Received (512~1023 Octets in Length)
Good Full Frame Packets Received and Transmitted Pause Frames Received
Octets Transmitted (64 Octets in Length)
Good Full Frame Packets Received and Transmitted Undersize Packets Received
Speed Received (65~127 Octets in Length)
Good Full Frame Packets Received(1024~1518 Octets Unicast Packets Transmitted

Speed Transmitted in Length)

Good Packets Packets Received(128~255 Octets in Unicast Packets Received

Received Length)
Good Packets Packets Received(256~511 Octets in

Transmitted Length)
Jabbers Packets Received(512~1023 Octets

in Length)
5.2.6 FIU Board Performance Event List

TN12FIU
SUMIOPCUR SUMIOPMIN XCSTMPMAX
SUMIOPMAX XCSTMPCUR XCSTMPMIN
5.2.7 HSC1 Board Performance Event List

CRC4BBE CRC4UAS LSOOPCUR
CRC4FEBBE LSBIASCUR LSOOPMAX
CRC4ES LSBIASMAX LSOOPMIN
CRC4FEES LSBIASMIN XCSTMPCUR
CRC4FESES LSIOPCUR XCSTMPMAX
CRC4FEUAS LSIOPMAX XCSTMPMIN
CRC4SES LSIOPMIN
5.2.8 HBA Board Performance Event List

BCVCUR EDTMPMAX SUMOOPMIN
BCVMAX EDTMPMIN WCVCUR
BCVMIN SUMIOPCUR WCVMAX
CCVCUR SUMIOPMAX WCVMIN
CCVMAX SUMIOPMIN XCSTMPCUR
CCVMIN SUMOOPCUR XCSTMPMAX
EDTMPCUR SUMOOPMAX XCSTMPMIN

5.2.9 ITL Board Performance Event List

XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.10 LDM Board Performance Event List

FEC_AFT_COR_ER ODU1_PM_BBER ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR ODU1_PM_ES OTU1_BBE
FEC_BEF_COR_ER ODU1_PM_FEBBE OTU1_BBER
FEC_BEF_COR_ERAVR ODU1_PM_FEBBER OTU1_BIAES
FEC_COR_0BIT_CNT ODU1_PM_FEES OTU1_ES
FEC_COR_1BIT_CNT ODU1_PM_FESES OTU1_FEBBE
FEC_COR_BYTE_CNT ODU1_PM_FESESR OTU1_FEBBER
FEC_UNCOR_BLOCK_CNT ODU1_PM_FEUAS OTU1_FEES
LSBIASCUR ODU1_PM_SES OTU1_FESES
LSBIASMAX ODU1_PM_SESR OTU1_FESESR
LSBIASMIN ODU1_PM_UAS OTU1_FEUAS
LSCLCCUR ODU1_TCMn_BBE OTU1_IAES
LSCLCMAX ODU1_TCMn_BBER OTU1_SES
LSCLCMIN ODU1_TCMn_BIAES OTU1_SESR
LSIOPCUR ODU1_TCMn_ES OTU1_UAS
LSIOPMAX ODU1_TCMn_FEBBE RSBBE
LSIOPMIN ODU1_TCMn_FEBBER RSCSES
LSOOPCUR ODU1_TCMn_FEES RSES
LSOOPMAX ODU1_TCMn_FESES RSSES
LSOOPMIN ODU1_TCMn_FESESR RSUAS
LSTMPCUR ODU1_TCMn_FEUAS XCSTMPCUR
LSTMPMAX ODU1_TCMn_IAES XCSTMPMAX
LSTMPMIN ODU1_TCMn_SES XCSTMPMIN
ODU1_PM_BBE ODU1_TCMn_SESR

NOTE
TCM6.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
Multicast Packets Received Packets Received Broadcast Packets

(1519~MTU Octets in Transmitted
Length)
Undersize Packets Received Packets Transmitted(64 Pause Frames Received

Octets in Length)
Oversize Packets Received Packets Transmitted Pause Frames Transmitted

Fragments Packets Transmitted Good Octets Received

Jabbers Packets Transmitted Good Octets Transmitted

Packets Received(64 Octets in Packets Transmitted Bad Octets Received

Length) (512~1023 Octets in Length)
Packets Received(65~127 Packets Transmitted Bad Octets Transmitted

Octets in Length) (1024~1518 Octets in
Length)
Packets Received(128~255 Packets Transmitted Alignment Errors

Octets in Length) (1519~MTUOctets in
Length)
Packets Received(256~511 Unicast Packets Received Drop Events at

Octets in Length) Transmission Direction
Packets Received(512~1023 Unicast Packets Transmitted Oversize Packets

Octets in Length) Transmitted
5.2.11 LDMD Board Performance Event List


NOTE
TCM6.
Packets Received

Length)


Octets in Length)





Length)

Length)


5.2.12 LDMS Board Performance Event List


NOTE
TCM6.
Packets Received

Length)

Octets in Length)






Length)

Length)


5.2.13 LDX Board Performance Event List

FEC_AFT_COR_ER ODU2_PM_ES OTU2_BBER
FEC_AFT_COR_ERAVR ODU2_PM_FEBBE OTU2_BIAES
FEC_BEF_COR_ER ODU2_PM_FEBBER OTU2_ES
FEC_BEF_COR_ERAVR ODU2_PM_FEES OTU2_FEBBE
FEC_COR_0BIT_CNT ODU2_PM_FESES OTU2_FEBBER
FEC_COR_1BIT_CNT ODU2_PM_FESESR OTU2_FEES
FEC_COR_BYTE_CNT ODU2_PM_FEUAS OTU2_FESES
FEC_UNCOR_BLOCK_CNT ODU2_PM_SES OTU2_FESESR
LSBIASCUR ODU2_PM_SESR OTU2_FEUAS
LSBIASMAX ODU2_PM_UAS OTU2_IAES
LSBIASMIN ODU2_TCMn_BBE OTU2_SES
LSCLCCUR ODU2_TCMn_BBER OTU2_SESR
LSCLCMAX ODU2_TCMn_BIAES OTU2_UAS
LSCLCMIN ODU2_TCMn_ES RSBBE
LSIOPCUR ODU2_TCMn_FEBBE RSCSES
LSIOPMAX ODU2_TCMn_FEBBER RSES
LSIOPMIN ODU2_TCMn_FEES RSOFS
LSOOPCUR ODU2_TCMn_FESES RSSES
LSOOPMAX ODU2_TCMn_FESESR RSUAS
LSOOPMIN ODU2_TCMn_FEUAS XCSTMPCUR

LSTMPCUR ODU2_TCMn_IAES XCSTMPMAX
LSTMPMAX ODU2_TCMn_SES XCSTMPMIN
LSTMPMIN ODU2_TCMn_SESR
ODU2_PM_BBE ODU2_TCMn_UAS
ODU2_PM_BBER OTU2_BBE
Packets Transmitted(128~255
Alignment Errors Oversize Packets Received Octets in Length)
Broadcast Packets Packets Received Packets Transmitted(256~511

Transmitted Octets in Length)
Broadcast Packets Packets Received(1024~1518 Packets Transmitted(512~1023

Received Octets in Length) Octets in Length)
FCS Errors Packets Received(128~255 Packets Transmitted(64 Octets in

Octets in Length) Length)
Fragments Packets Received(256~511 Packets Transmitted(65~127

Octets in Length) Octets in Length)
Jabbers Packets Received(512~1023 Pause Frames Transmitted

Octets in Length)
Multicast Packets Packets Received(64 Octets in Pause Frames Received

Received Length)
Multicast Packets Packets Received(65~127 Octets Undersize Packets Received

Transmitted in Length)
Octets Received Packets Transmitted Unicast Packets Transmitted
Octets Transmitted Packets Transmitted(1024~1518 Unicast Packets Received

Octets in Length)
5.2.14 LOG Board Performance Event List

FEC_AFT_COR_ER ODU2_PM_BBER ODU2_TCMn_SESR
FEC_AFT_COR_ERAVR ODU2_PM_ES ODU2_TCMn_UAS
FEC_BEF_COR_ER ODU2_PM_FEBBE ODU3_PM_BBE
FEC_BEF_COR_ERAVR ODU2_PM_FEBBER OTU2_BBE

FEC_COR_0BIT_CNT ODU2_PM_FEES OTU2_BBER
FEC_COR_1BIT_CNT ODU2_PM_FESES OTU2_BIAES
FEC_COR_BYTE_CNT ODU2_PM_FESESR OTU2_ES
FEC_UNCOR_BLOCK_CNT ODU2_PM_FEUAS OTU2_FEBBE
LSBIASCUR ODU2_PM_SES OTU2_FEBBER
LSBIASMAX ODU2_PM_SESR OTU2_FEES
LSBIASMIN ODU2_PM_UAS OTU2_FESES
LSCLCCUR ODU2_TCMn_BBE OTU2_FESESR
LSCLCMAX ODU2_TCMn_BBER OTU2_FEUAS
LSCLCMIN ODU2_TCMn_BIAES OTU2_IAES
LSIOPCUR ODU2_TCMn_ES OTU2_SES
LSIOPMAX ODU2_TCMn_FEBBE OTU2_SESR
LSIOPMIN ODU2_TCMn_FEBBER OTU2_UAS
LSOOPCUR ODU2_TCMn_FEES XCSTMPCUR
LSOOPMAX ODU2_TCMn_FESES XCSTMPMAX
LSOOPMIN ODU2_TCMn_FESESR XCSTMPMIN
LSTMPCUR ODU2_TCMn_FEUAS
LSTMPMAX ODU2_TCMn_IAES
LSTMPMIN ODU2_TCMn_SES
NOTE
TCM6.
Drop Events Broadcast Packets Received Multicast Packets Received
Undersize Packets Received Oversize Packets Received Fragments
Jabbers Packets Received (64 Octets Packets Received (65~127

in Length) Octets in Length)
Packets Received (128~255 Packets Received (256~511 Packets Received

Octets in Length) Octets in Length) (512~1023 Octets in
Length)

Packets Received (1024~1518 Packets Received Packets Transmitted (64

Octets in Length) (1519~MTU Octets in Octets in Length)
Length)
Packets Transmitted (65~127 Packets Transmitted Packets Transmitted

Octets in Length) (128~255 Octets in Length) (256~511 Octets in Length)
Packets Transmitted Packets Transmitted Packets Transmitted

(512~1023 Octets in Length) (1024~1518 Octets in (1519~MTU Octets in
Length) Length)
Unicast Packets Received Unicast Packets Transmitted Multicast Packets

Transmitted
Broadcast Packets Pause Frames Received Pause Frames Transmitted

Transmitted
Good Octets Received Good Octets Transmitted Bad Octets Received
Bad Octets Transmitted FCS Errors
NOTE
In the GFP-T mode, the TN11LOG board does not support the RMON performance event.
5.2.15 LOM Board Performance Event List

FEC_AFT_COR_ER LSTMPMAX ODU2_TCMn_FEUAS
FEC_AFT_COR_ERAVR LSTMPMIN ODU2_TCMn_IAES
FEC_BEF_CORER_FLOAT ODU2_PM_BBE ODU2_TCMn_SES
FEC_BEF_COR_ER ODU2_PM_BBER ODU2_TCMn_SESR
FEC_BEF_COR_ERAVR ODU2_PM_ES ODU2_TCMn_UAS
FEC_AFT_CORER_FLOAT ODU2_PM_FEBBE OTU2_BBE
FEC_COR_0BIT_CNT ODU2_PM_FEBBER OTU2_BBER
FEC_COR_1BIT_CNT ODU2_PM_FEES OTU2_BIAES
FEC_COR_BYTE_CNT ODU2_PM_FESES OTU2_ES
FEC_UNCOR_BLOCK_CNT ODU2_PM_FESESR OTU2_FEBBE
LSBISACUR ODU2_PM_FEUAS OTU2_FEBBER
LSBISAMAX ODU2_PM_SES OTU2_FEES
LSBISAMIN ODU2_PM_SESR OTU2_FESES
LSCLCCUR ODU2_PM_UAS OTU2_FESESR

LSCLCMAX ODU2_TCMn_BBE OTU2_FEUAS
LSCLCMIN ODU2_TCMn_BBER OTU2_IAES
LSIOPCUR ODU2_TCMn_BIAES OTU2_SES
LSIOPMAX ODU2_TCMn_ES OTU2_SESR
LSIOPMIN ODU2_TCMn_FEBBE OTU2_UAS
LSOOPCUR ODU2_TCMn_FEBBER XCSTMPCUR
LSOOPMAX ODU2_TCMn_FEES XCSTMPMAX
LSOOPMIN ODU2_TCMn_FESES XCSTMPMIN
LSTMPCUR ODU2_TCMn_FESESR
NOTE
TCM6.
Multicast Packets
Drop Events Broadcast Packets Received Received
Undersize Packets Received Oversize Packets Received Fragments
Jabbers Packets Received (64 Octets Packets Received (65~127

in Length) Octets in Length)
Packets Received (128~255 Packets Received (256~511 Packets Received

Octets in Length) Octets in Length) (512~1023 Octets in
Length)

Octets in Length) (1519~MTU Octets in Octets in Length)
Length)

Octets in Length) (128~255 Octets in Length) (256~511 Octets in
Length)
Packets Transmitted Packets Transmitted Packets Transmitted

(512~1023 Octets in Length) (1024~1518 Octets in (1519~MTU Octets in
Length) Length)
Unicast Packets Received Unicast Packets Transmitted Multicast Packets

Transmitted
Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted
Good Octets Received Good Octets Transmitted Bad Octets Received

Bad Octets Transmitted FCS Errors Drop Events at

Transmission Direction
Oversize Packets Transmitted
FC Performance Event List
FC_Client_RxOLSPrim_
CLIENT_CRC_ERR Cnt LINKTST_CNT
FC_Client_CreditZero_Cnt FC_Client_Truncated FC_Wsys_Crc_Err_Cnt

FrmCnt_sum
FC_Client_Invld_10BCode_ FC_Client_Tx_NOS_Cnt FC_Wsys_LinkDown_Cnt

Cnt
CLIENT_RXBYTECNT_S FC_Client_Tx_Utilization FC_Wsys_OverLongFrm_Su

UM m
CLIENT_RXFRMCNT_C1 CLIENT_TXBYTECNT_ FC_Wsys_Rx_PausePrim_Cn

SUM t
CLIENT_RXFRMCNT_C2 CLIENT_TXFRMCNT_C FC_Wsys_Rx_PingAckPrim_

1 Cnt
CLIENT_RXFRMCNT_C3 CLIENT_TXFRMCNT_C FC_Wsys_Rx_PingPrim_Cnt

2
CLIENT_RXFRMCNT_C4 CLIENT_TXFRMCNT_C FC_Wsys_Rx_ResumePrim_

3 Cnt
CLIENT_RXFRMCNT_CF CLIENT_TXFRMCNT_C FC_Wsys_Truncated

4 FrmCnt_sum
CLIENT_RXFRMCNT_SU CLIENT_TXFRMCNT_C FC_Wsys_Tx_PausePrim_Cn

M F t
FC_Client_Rx_NOS_Cnt CLIENT_TXFRMCNT_S FC_Wsys_Tx_PingAckPrim_

UM Cnt
FC_Client_Rx_Utilization CLIENT_UNSUPOS_CN FC_Wsys_Tx_PingPrim_Cnt

T
FC_Client_OverLongFrm_S FC_Client_TxLRPrim_Cn FC_Wsys_Tx_ResumePrim_

um t Cnt
FC_Client_RxLRPrim_Cnt FC_Client_TxLRRPrim_ FC_Wsys_unsupos_cnt

Cnt
FC_Client_RxLRRPrim_Cnt FC_Client_TxOLSPrim_
Cnt

5.2.16 LQMD Board Performance Event List

FEC_UNCOR_BLOCK_C ODU1_PM_FEUAS OTU1_FEES

NT
NOTE
TCM6.

TN12LQMD
Packets Received Broadcast Packets

(1024~1518 Octets in Transmitted
Drop Events Length)
Packets Received Pause Frames Received

(1519~MTU Octets in
Broadcast Packets Received Length)
Multicast Packets Received Packets Transmitted(64 Pause Frames Transmitted

Octets in Length)
Undersize Packets Received Packets Transmitted Good Octets Received

Oversize Packets Received Packets Transmitted Good Octets Transmitted

Fragments Packets Transmitted Bad Octets Received

Jabbers Packets Transmitted Bad Octets Transmitted

Packets Received(64 Octets in Packets Transmitted Alignment Errors

Length) (1024~1518 Octets in
Length)
Packets Received(65~127 Packets Transmitted Drop Events at

Octets in Length) (1519~MTUOctets in Transmission Direction
Length)
Packets Received(128~255 Unicast Packets Received Oversize Packets

Packets Received(256~511 Unicast Packets Transmitted

Octets in Length)
Packets Received(512~1023 Multicast Packets

5.2.17 LQMS Board Performance Event List



NT
NOTE
TCM6.
TN12LQMS
Packets Received

Length)


Octets in Length)





Length)

Length)


5.2.18 LQM Board Performance Event List


NT

NOTE
TCM6.
Packets Received

Length)

Octets in Length)






Length)

Length)


5.2.19 LSXLR Board Performance Event List

FEC_AFT_COR_ER ODU3_PM_BBE ODU3_TCMn_SES
FEC_AFT_COR_ERAVR ODU3_PM_BBER ODU3_TCMn_SESR
FEC_BEF_COR_ER ODU3_PM_ES ODU3_TCMn_UAS
FEC_BEF_COR_ERAVR ODU3_PM_FEBBE OTU3_BBE
FEC_UNCOR_BLOCK_C ODU3_PM_FESESR OTU3_FEBBE

NT
LSBIASCUR ODU3_PM_FEUAS OTU3_FEBBER
LSBIASMAX ODU3_PM_SES OTU3_FEES
LSBIASMIN ODU3_PM_SESR OTU3_FESES

LSTMPMAX ODU3_TCMn_FEUAS
LSTMPMIN ODU3_TCMn_IAES
NOTE
TCM6.
5.2.20 LSXL Board Performance Event List

FEC_AFT_COR_ER ODU3_PM_BBE ODU3_TCMn_SES
FEC_AFT_COR_ERAVR ODU3_PM_BBER ODU3_TCMn_SESR
FEC_BEF_COR_ER ODU3_PM_ES ODU3_TCMn_UAS
FEC_BEF_COR_ERAVR ODU3_PM_FEBBE OTU3_BBE
FEC_UNCOR_BLOCK_C ODU3_PM_FESESR OTU3_FEBBE

NT
LSBIASCUR ODU3_PM_FEUAS OTU3_FEBBER
LSBIASMAX ODU3_PM_SES OTU3_FEES
LSBIASMIN ODU3_PM_SESR OTU3_FESES

LSTMPMAX ODU3_TCMn_FEUAS
LSTMPMIN ODU3_TCMn_IAES
NOTE
TCM6.
5.2.21 LSXR Board Performance Event List

FEC_UNCOR_BLOCK_C ODU2_PM_SES OTU2_FESESR

NT

NOTE
TCM6.
5.2.22 LSX Board Performance Event List

FEC_UNCOR_BLOCK_C ODU2_PM_SES OTU2_FESESR

NT

NOTE
TCM6.
Octets Received Packets Received Broadcast Packets Received
Multicast Packets Received Undersize Packets Received Oversize Packets Received
Fragments Jabbers Packets Received (64 Octets

in Length)
Packets Received (65~127 Packets Received (128~255 Packets Received (256~511

Octets in Length) Octets in Length) Octets in Length)

Octets in Length) (1024~1518 Octets in Octets in Length)
Length)

Octets in Length) (128~255 Octets in Length) (256~511 Octets in Length)
Packets Transmitted Packets Transmitted Unicast Packets Received

(512~1023 Octets in Length) (1024~1518 Octets in
Length)
Unicast Packets Transmitted Multicast Packets Broadcast Packets

Transmitted Transmitted
Pause Frames Received Pause Frames Transmitted Alignment Errors
FCS Errors Packets Transmitted Octets Transmitted
5.2.23 LWXS Board Performance Event List

LSBIASCUR LSIOPMIN RSCSES
LSBIASMAX LSOOPCUR RSES
LSBIASMIN LSOOPMAX RSOFS

LSCLCCUR LSOOPMIN RSSES
LSCLCMAX LSTMPCUR RSUAS
LSCLCMIN LSTMPMAX XCSTMPCUR
LSIOPCUR LSTMPMIN XCSTMPMAX
LSIOPMAX RSBBE XCSTMPMIN
5.2.24 M40V Board Performance Event List

ICTMPCUR SUMOOPCUR XCSTMPCUR
ICTMPMAX SUMOOPMAX XCSTMPMAX
ICTMPMIN SUMOOPMIN XCSTMPMIN
5.2.25 M40 Board Performance Event List

ICCLCCUR ICTMPMAX SUMOOPMIN
ICCLCMAX ICTMPMIN XCSTMPCUR
ICCLCMIN SUMOOPCUR XCSTMPMAX
ICTMPCUR SUMOOPMAX XCSTMPMIN
5.2.26 MCA4 Board Performance Event List

PCLSOPCUR PCLSWLOCUR XCSTMPMIN
PCLSSNCUR XCSTMPCUR
PCLSWLCUR XCSTMPMAX
5.2.27 MCA8 Board Performance Event List

PCLSOPCUR PCLSWLOCUR XCSTMPMIN
PCLSSNCUR XCSTMPCUR
PCLSWLCUR XCSTMPMAX

5.2.28 MR8V Board Performance Event List

5.2.29 ND2 Board Performance Event List

TN52ND2
FEC_AFT_COR_ER ODU1_PM_ES ODU2_PM_SESR
FEC_AFT_COR_ERAVR ODU1_PM_FEBBE ODU2_PM_UAS
FEC_BEF_COR_ER ODU1_PM_FEBBER ODU2_TCMn_BBE
FEC_BEF_COR_ERAVR ODU1_PM_FEES ODU2_TCMn_BBER
FEC_COR_0BIT_CNT ODU1_PM_FESES ODU2_TCMn_BIAES
FEC_COR_1BIT_CNT ODU1_PM_FESESR ODU2_TCMn_ES
FEC_COR_BYTE_CNT ODU1_PM_FEUAS ODU2_TCMn_FEBBE
FEC_UNCOR_BLOCK_CN ODU1_PM_SES ODU2_TCMn_FEBBER

T
LSBIASCUR ODU1_PM_SESR ODU2_TCMn_FEES
LSBIASMAX ODU1_PM_UAS ODU2_TCMn_FESES
LSBIASMIN ODU1_TCMn_BBE ODU2_TCMn_FESESR
LSIOPCUR ODU1_TCMn_BBER ODU2_TCMn_FEUAS
LSIOPMAX ODU1_TCMn_BIAES ODU2_TCMn_IAES
LSIOPMIN ODU1_TCMn_ES ODU2_TCMn_SES
LSOOPCUR ODU1_TCMn_FEBBE ODU2_TCMn_SESR
LSOOPMAX ODU1_TCMn_FEBBER ODU2_TCMn_UAS
LSOOPMIN ODU1_TCMn_FEES OTU2_BBE
LSTMPCUR ODU1_TCMn_FESES OTU2_BBER
LSTMPMAX ODU1_TCMn_FESESR OTU2_BIAES
LSTMPMIN ODU1_TCMn_FEUAS OTU2_ES
ODU0_PM_BBE ODU1_TCMn_IAES OTU2_FEBBE
ODU0_PM_BBER ODU1_TCMn_SES OTU2_FEBBER
ODU0_PM_ES ODU1_TCMn_SESR OTU2_FEES
ODU0_PM_FEBBE ODU1_TCMn_UAS OTU2_FESES

ODU0_PM_FEBBER ODU2_PM_BBE OTU2_FESESR
ODU0_PM_FEES ODU2_PM_BBER OTU2_FEUAS
ODU0_PM_FESES ODU2_PM_ES OTU2_IAES
ODU0_PM_FESESR ODU2_PM_FEBBE OTU2_SES
ODU0_PM_FEUAS ODU2_PM_FEBBER OTU2_SESR
ODU0_PM_SES ODU2_PM_FEES OTU2_UAS
ODU0_PM_SESR ODU2_PM_FESES XCSTMPCUR
ODU0_PM_UAS ODU2_PM_FESESR XCSTMPMAX
ODU1_PM_BBE ODU2_PM_FEUAS XCSTMPMIN
ODU1_PM_BBER ODU2_PM_SES
NOTE
TCM6.
5.2.30 NQ2 Board Performance Event List

TN54NQ2
FEC_AFT_COR_ER ODU1_PM_BBER ODU2_PM_SESR
FEC_AFT_COR_ERAVR ODU1_PM_ES ODU2_PM_UAS
FEC_AFT_CORER_FLOAT ODU1_PM_FEBBE ODU2_TCMn_BBE
FEC_BEF_COR_ER ODU1_PM_FEBBER ODU2_TCMn_BBER
FEC_BEF_COR_ERAVR ODU1_PM_FEES ODU2_TCMn_BIAES
FEC_BEF_CORER_FLOAT ODU1_PM_FESES ODU2_TCMn_ES
FEC_COR_0BIT_CNT ODU1_PM_FESESR ODU2_TCMn_FEBBE
FEC_COR_1BIT_CNT ODU1_PM_FEUAS ODU2_TCMn_FEBBER
FEC_COR_BYTE_CNT ODU1_PM_SES ODU2_TCMn_FEES
FEC_UNCOR_BLOCK_CN ODU1_PM_SESR ODU2_TCMn_FESES

T
LSBIASCUR ODU1_PM_UAS ODU2_TCMn_FESESR
LSBIASMAX ODU1_TCMn_BBE ODU2_TCMn_FEUAS
LSBIASMIN ODU1_TCMn_BBER ODU2_TCMn_IAES
LSIOPCUR ODU1_TCMn_BIAES ODU2_TCMn_SES

LSIOPMAX ODU1_TCMn_ES ODU2_TCMn_SESR
LSIOPMIN ODU1_TCMn_FEBBE ODU2_TCMn_UAS
LSOOPCUR ODU1_TCMn_FEBBER OTU2_BBE
LSOOPMAX ODU1_TCMn_FEES OTU2_BBER
LSOOPMIN ODU1_TCMn_FESES OTU2_BIAES
LSTMPCUR ODU1_TCMn_FESESR OTU2_ES
LSTMPMAX ODU1_TCMn_FEUAS OTU2_FEBBE
LSTMPMIN ODU1_TCMn_IAES OTU2_FEBBER
ODU0_PM_BBE ODU1_TCMn_SES OTU2_FEES
ODU0_PM_BBER ODU1_TCMn_SESR OTU2_FESES
ODU0_PM_ES ODU1_TCMn_UAS OTU2_FESESR
ODU0_PM_FEBBE ODU2_PM_BBE OTU2_FEUAS
ODU0_PM_FEBBER ODU2_PM_BBER OTU2_IAES
ODU0_PM_FEES ODU2_PM_ES OTU2_SES
ODU0_PM_FESES ODU2_PM_FEBBE OTU2_SESR
ODU0_PM_FESESR ODU2_PM_FEBBER OTU2_UAS
ODU0_PM_FEUAS ODU2_PM_FEES XCSTMPCUR
ODU0_PM_SES ODU2_PM_FESES XCSTMPMAX
ODU0_PM_SESR ODU2_PM_FESESR XCSTMPMIN
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
TN52NQ2


T
NOTE
TCM6.

5.2.31 NS2 Board Performance Event List

TN52NS2

T

NOTE
TCM6.
5.2.32 NS3 Board Performance Event List

TN52NS3
FEC_AFT_COR_ER ODU1_PM_SES ODU3_PM_BBER
FEC_AFT_COR_ERAVR ODU1_PM_SESR ODU3_PM_ES
FEC_BEF_COR_ER ODU1_PM_UAS ODU3_PM_FEBBE
FEC_BEF_COR_ERAVR ODU1_TCMn_BBE ODU3_PM_FEBBER
FEC_COR_0BIT_CNT ODU1_TCMn_BBER ODU3_PM_FEES
FEC_COR_1BIT_CNT ODU1_TCMn_BIAES ODU3_PM_FESES
FEC_COR_BYTE_CNT ODU1_TCMn_ES ODU3_PM_FESESR
FEC_UNCOR_BLOCK_CN ODU1_TCMn_FEBBE ODU3_PM_FEUAS

T
LSBIASCUR ODU1_TCMn_FEBBER ODU3_PM_SES
LSBIASMAX ODU1_TCMn_FEES ODU3_PM_SESR
LSBIASMIN ODU1_TCMn_FESES ODU3_PM_UAS
LSCLCCUR ODU1_TCMn_FESESR ODU3_TCMn_BBE
LSCLCMAX ODU1_TCMn_FEUAS ODU3_TCMn_BBER
LSCLCMIN ODU1_TCMn_IAES ODU3_TCMn_BIAES
LSIOPCUR ODU1_TCMn_SES ODU3_TCMn_ES
LSIOPMAX ODU1_TCMn_SESR ODU3_TCMn_FEBBE
LSIOPMIN ODU1_TCMn_UAS ODU3_TCMn_FEBBER
LSOOPCUR ODU2_PM_BBE ODU3_TCMn_FEES

LSOOPMAX ODU2_PM_BBER ODU3_TCMn_FESES
LSOOPMIN ODU2_PM_ES ODU3_TCMn_FESESR
LSTMPCUR ODU2_PM_FEBBE ODU3_TCMn_FEUAS
LSTMPMAX ODU2_PM_FEBBER ODU3_TCMn_IAES
LSTMPMIN ODU2_PM_FEES ODU3_TCMn_SES
ODU0_PM_BBE ODU2_PM_FESES ODU3_TCMn_SESR
ODU0_PM_BBER ODU2_PM_FESESR ODU3_TCMn_UAS
ODU0_PM_ES ODU2_PM_FEUAS OTU3_BBE
ODU0_PM_FEBBE ODU2_PM_SES OTU3_BBER
ODU0_PM_FEBBER ODU2_PM_SESR OTU3_BIAES
ODU0_PM_FEES ODU2_PM_UAS OTU3_ES
ODU0_PM_FESES ODU2_TCMn_BBE OTU3_FEBBE
ODU0_PM_FESESR ODU2_TCMn_BBER OTU3_FEBBER
ODU0_PM_FEUAS ODU2_TCMn_BIAES OTU3_FEES
ODU0_PM_SES ODU2_TCMn_ES OTU3_FESES
ODU0_PM_SESR ODU2_TCMn_FEBBE OTU3_FESESR
ODU0_PM_UAS ODU2_TCMn_FEBBER OTU3_FEUAS
ODU1_PM_BBE ODU2_TCMn_FEES OTU3_IAES
ODU1_PM_BBER ODU2_TCMn_FESES OTU3_SES
ODU1_PM_ES ODU2_TCMn_FESESR OTU3_SESR
ODU1_PM_FEBBE ODU2_TCMn_FEUAS OTU3_UAS
ODU1_PM_FEBBER ODU2_TCMn_IAES XCSTMPCUR
ODU1_PM_FEES ODU2_TCMn_SES XCSTMPMAX
ODU1_PM_FESES ODU2_TCMn_SESR XCSTMPMIN
ODU1_PM_FESESR ODU2_TCMn_UAS
ODU1_PM_FEUAS ODU3_PM_BBE
NOTE
TCM6.

5.2.33 OAU1 Board Performance Event List

5.2.34 OBU1 Board Performance Event List

5.2.35 OBU2 Board Performance Event List


5.2.36 OLP Board Performance Event List

SUMIOPCUR SUMIOPMIN XCSTMPMAX
SUMIOPMAX XCSTMPCUR XCSTMPMIN
LSIOPCUR LSIOPMIN LSIOPMAX
5.2.37 RDU9 Board Performance Event List

SUMIOPCUR SUMOOPCUR XCSTMPCUR
SUMIOPMAX SUMOOPMAX XCSTMPMAX
SUMIOPMIN SUMOOPMIN XCSTMPMIN
5.2.38 RDU9 Board Performance Event List

SUMIOPCUR SUMOOPCUR XCSTMPCUR
SUMIOPMAX SUMOOPMAX XCSTMPMAX
SUMIOPMIN SUMOOPMIN XCSTMPMIN
5.2.39 RMU9 Board Performance Event List

ICTMPCUR SUMIOPMAX SUMOOPMIN
ICTMPMAX SUMIOPMIN XCSTMPCUR
ICTMPMIN SUMOOPCUR XCSTMPMAX
SUMIOPCUR SUMOOPMAX XCSTMPMIN
5.2.40 ROAM Board Performance Event List

ICTMPCUR LSOOPMIN SUMOOPMAX
ICTMPMAX SUMIOPCUR SUMOOPMIN
ICTMPMIN SUMIOPMAX XCSTMPCUR
LSOOPCUR SUMIOPMIN XCSTMPMAX

LSOOPMAX SUMOOPCUR XCSTMPMIN
5.2.41 SC1 Board Performance Event List

CRC4SES LSIOPMIN
5.2.42 SC2 Board Performance Event List

CRC4SES LSIOPMIN
5.2.43 SFD64 Board Performance Event List

AUPJCHIGH HPUAS RPLMAX
AUPJCLOW MSBBE RPLMIN
AUPJCNEW MSES RSBBE
FEC_AFT_COR_ER MSCSES RSCSES
FEC_AFT_COR_ERAVR MSFEBBE RSES
FEC_BEF_COR_ER MSFEES RSOFS

FEC_BEF_COR_ERAVR MSFECSES RSOOF
FEC_COR_0BIT_CNT MSFESES RSSES
FEC_COR_1BIT_CNT MSFEUAS RSUAS
FEC_COR_BYTE_CNT MSSES TLBCUR
FEC_UNCOR_BLOCK_CN MSUAS TLBMAX

T
HPBBE ODU2PMBIP8 TLBMIN
HPES OSPICCVCUR TPLCUR
HPCSES OSPICCVMAX TPLMAX
HPFEBBE OSPICCVMIN TPLMIN
HPFEES OSPITMPCUR XCSTMPCUR
HPFECSES OSPITMPMAX XCSTMPMAX
HPFESES OSPITMPMIN XCSTMPMIN
HPFEUAS OTU2SMBIP8
HPSES RPLCUR
5.2.44 SF64 Board Performance Event List

AUPJCHIGH MSBBE RSBBE
AUPJCLOW MSES RSES
AUPJCNEW MSCSES RSOFS
FEC_AFT_COR_ER MSFEBBE RSOOF
FEC_AFT_COR_ERAVR MSFEES RSSES
FEC_BEF_COR_ER MSFESES RSCSES
FEC_BEF_COR_ERAVR MSFECSES RSUAS
FEC_COR_0BIT_CNT MSFEUAS TCBBE
FEC_COR_1BIT_CNT MSSES TCFEBBE
FEC_COR_BYTE_CNT MSUAS TCOBBE
FEC_UNCOR_BLOCK_CN ODU2PMBIP8 TLBCUR

T
HPBBE OSPICCVCUR TLBMAX

HPES OSPICCVMAX TLBMIN
HPCSES OSPICCVMIN TPLCUR
HPFEBBE OSPITMPCUR TPLMAX
HPFEES OSPITMPMAX TPLMIN
HPFESES OSPITMPMIN XCSTMPCUR
HPFECSES OTU2SMBIP8 XCSTMPMAX
HPFEUAS RPLCUR XCSTMPMIN
HPSES RPLMAX
HPUAS RPLMIN
5.2.45 SF64A Board Performance Event List

AUPJCHIGH MSBBE RSBBE
AUPJCLOW MSES RSES
AUPJCNEW MSCSES RSCSES
FEC_AFT_COR_ER MSFEBBE RSOFS
FEC_AFT_COR_ERAVR MSFEES RSOOF
FEC_BEF_COR_ER MSFECSES RSSES
FEC_BEF_COR_ERAVR MSFESES RSUAS
FEC_COR_0BIT_CNT MSFEUAS TCBBE
FEC_COR_1BIT_CNT MSSES TCFEBBE
FEC_COR_BYTE_CNT MSUAS TCOBBE
FEC_UNCOR_BLOCK_CN ODU2PMBIP8 TLBCUR

T
HPBBE OSPICCVCUR TLBMAX
HPES OSPICCVMAX TLBMIN
HPFEBBE OSPICCVMIN TPLCUR
HPFEES OSPITMPCUR TPLMAX
HPFESES OSPITMPMAX TPLMIN
HPFECSES OSPITMPMIN XCSTMPCUR
HPFEUAS OTU2SMBIP8 XCSTMPMAX

HPCSES RPLCUR XCSTMPMIN
HPSES RPLMAX
HPUAS RPLMIN
5.2.46 SL64 Board Performance Event List

AUPJCHIGH MSFEBBE RSBBE
AUPJCLOW MSFEES RSCSES
AUPJCNEW MSFECSES RSES
HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
HPFEES OSPICCVCUR TLBCUR
HPFECSES OSPICCVMAX TLBMAX
HPFESES OSPICCVMIN TLBMIN
HPFEUAS OSPITMPCUR TPLCUR
HPSES OSPITMPMAX TPLMAX
HPUAS OSPITMPMIN TPLMIN
MSBBE RPLCUR XCSTMPCUR
MSCSES RPLMAX XCSTMPMAX
MSES RPLMIN XCSTMPMIN
5.2.47 SLD64 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF

HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
5.2.48 SLH41 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS

5.2.49 SLO16 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
5.2.50 SLQ16 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS

5.2.51 SLQ64 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
5.2.52 STG Board Performance Event List


5.2.53 SXM Board Performance Event List

5.2.54 TDC Board Performance Event List

5.2.55 TDX Board Performance Event List

TN52TDX
FEC_AFT_COR_ER ODU2_PM_ES OTU2_BBE
FEC_AFT_COR_ERAV ODU2_PM_FEBBE OTU2_BBER

R
FEC_BEF_COR_ER ODU2_PM_FEBBER OTU2_BIAES
FEC_BEF_COR_ERAV ODU2_PM_FEES OTU2_ES

R
FEC_COR_1BIT_CNT ODU2_PM_FESESR OTU2_FEBBER
FEC_COR_BYTE_CNT ODU2_PM_FEUAS OTU2_FEES
FEC_UNCOR_BLOCK_ ODU2_PM_SES OTU2_FESES

CNT
FEC_BEF_CORER_FL ODU2_PM_SESR OTU2_FESESR

OAT
FEC_AFT_CORER_FL ODU2_PM_UAS OTU2_FEUAS

OAT
LSBIASCUR ODU2_TCMn_BBE OTU2_IAES
LSBIASMAX ODU2_TCMn_BBER OTU2_SES
LSBIASMIN ODU2_TCMn_BIAES OTU2_SESR
LSIOPMIN ODU2_TCMn_FEBBER RSES
LSOOPCUR ODU2_TCMn_FEES RSCSES

ODU2_PM_BBER ODU2_TCMn_UAS
TN52TDX
Alignment Errors Octets Transmitted Octets in Length)
Bad Octets Oversize Packets Received Packets Transmitted

Received (1519~MTUOctets in Length)
Bad Octets Oversize Packets Transmitted Packets Transmitted(256~511


Broadcast Packets Packets Received(1024~1518 Packets Transmitted(64 Octets in

Received Octets in Length) Length)
Control Frames Packets Received(128~255 Packets Transmitted(65~127

Control Frames Packets Received(1519~MTU Pause Frames Transmitted

FCS Errors Packets Received(256~511 Pause Frames Received

Octets in Length)
Fragments Packets Received(512~1023 Undersize Packets Received

Octets in Length)
Jabbers Packets Received(64 Octets in Unicast Packets Transmitted

Length)
Multicast Packets Packets Received(65~127 Octets Unicast Packets Received

Received in Length)
Multicast Packets Packets Transmitted

Transmitted

Octets Received Packets Transmitted(1024~1518

Octets in Length)
5.2.56 TMX Board Performance Event List

FEC_AFT_COR_ER ODU1_TCMn_ES OTU1_BBER
FEC_AFT_COR_ERAVR ODU1_TCMn_FEBBE OTU1_BIAES
FEC_BEF_COR_ER ODU1_TCMn_FEBBER OTU1_ES
FEC_BEF_COR_ERAVR ODU1_TCMn_FEES OTU1_FEBBE
FEC_COR_0BIT_CNT ODU1_TCMn_FESES OTU1_FEBBER
FEC_COR_1BIT_CNT ODU1_TCMn_FESESR OTU1_FEES
FEC_COR_BYTE_CNT ODU1_TCMn_FEUAS OTU1_FESES
FEC_UNCOR_BLOCK_CNT ODU1_TCMn_IAES OTU1_FESESR
LSBIASCUR ODU1_TCMn_SES OTU1_FEUAS
LSBIASMAX ODU1_TCMn_SESR OTU1_IAES
LSBIASMIN ODU1_TCMn_UAS OTU1_SES
LSCLCCUR ODU2_PM_BBE OTU1_SESR
LSCLCMAX ODU2_PM_BBER OTU1_UAS
LSCLCMIN ODU2_PM_ES OTU2_BBE
LSIOPCUR ODU2_PM_FEBBE OTU2_BBER
LSIOPMAX ODU2_PM_FEBBER OTU2_BIAES
LSIOPMIN ODU2_PM_FEES OTU2_ES
LSOOPCUR ODU2_PM_FESES OTU2_FEBBE
LSOOPMAX ODU2_PM_FESESR OTU2_FEBBER
LSOOPMIN ODU2_PM_FEUAS OTU2_FEES
LSTMPCUR ODU2_PM_SES OTU2_FESES
LSTMPMAX ODU2_PM_SESR OTU2_FESESR
LSTMPMIN ODU2_PM_UAS OTU2_FEUAS
ODU1_PM_BBE ODU2_TCMn_BBE OTU2_IAES
ODU1_PM_BBER ODU2_TCMn_BBER OTU2_SES
ODU1_PM_ES ODU2_TCMn_BIAES OTU2_SESR

ODU1_PM_FEBBE ODU2_TCMn_ES OTU2_UAS
ODU1_PM_FEBBER ODU2_TCMn_FEBBE RSBBE
ODU1_PM_FEES ODU2_TCMn_FEBBER RSCSES
ODU1_PM_FESES ODU2_TCMn_FEES RSES
ODU1_PM_FESESR ODU2_TCMn_FESES RSOFS
ODU1_PM_FEUAS ODU2_TCMn_FESESR RSSES
ODU1_PM_SES ODU2_TCMn_FEUAS RSUAS
ODU1_PM_SESR ODU2_TCMn_IAES XCSTMPCUR
ODU1_PM_UAS ODU2_TCMn_SES XCSTMPMAX
ODU1_TCMn_BBE ODU2_TCMn_SESR XCSTMPMIN
ODU1_TCMn_BBER ODU2_TCMn_UAS
ODU1_TCMn_BIAES OTU1_BBE
NOTE
TCM6.
5.2.57 TOG Board Performance Event List

LSBIASCUR ODU0_PM_BBER ODU1_PM_ES
LSBIASMAX ODU0_PM_ES ODU1_PM_FEBBE
LSBIASMIN ODU0_PM_FEBBE ODU1_PM_FEBBER
LSIOPCUR ODU0_PM_FEBBER ODU1_PM_FEES
LSIOPMAX ODU0_PM_FEES ODU1_PM_FESES
LSIOPMIN ODU0_PM_FESES ODU1_PM_FESESR
LSOOPCUR ODU0_PM_FESESR ODU1_PM_FEUAS
LSOOPMAX ODU0_PM_FEUAS ODU1_PM_SES
LSOOPMIN ODU0_PM_SES ODU1_PM_SESR
LSTMPCUR ODU0_PM_SESR ODU1_PM_UAS
LSTMPMAX ODU0_PM_UAS XCSTMPCUR
LSTMPMIN ODU1_PM_BBE XCSTMPMAX
ODU0_PM_BBE ODU1_PM_BBER XCSTMPMIN

Bad Octets Received Packets Received(512~1023

Multicast Packets Received Octets in Length)
Broadcast Packets Packets Received(64 Octets in

Received Oversize Packets Received Length)
FCS Errors Packets Received(1024~1518 Packets Received(65~127 Octets

Octets in Length) in Length)
Fragments Packets Received(128~255 Pause Frames Received

Octets in Length)
Good Octets Received Packets Received(1519~MTU Undersize Packets Received

Octets in Length)
Jabbers Packets Received(256~511 Unicast Packets Received

Octets in Length)
Drop Events
5.2.58 TOM Board Performance Event List

TN52TOM
FEC_AFT_COR_ER ODU0_PM_FESESR ODU1_TCMn_IAES
FEC_AFT_COR_ERAVR ODU0_PM_FEUAS ODU1_TCMn_SES
FEC_BEF_COR_ER ODU0_PM_SES ODU1_TCMn_SESR
FEC_BEF_COR_ERAVR ODU0_PM_SESR ODU1_TCMn_UAS
FEC_COR_0BIT_CNT ODU0_PM_UAS OTU1_IAES
FEC_COR_1BIT_CNT ODU1_PM_BBE OTU1_BIAES
FEC_COR_BYTE_CNT ODU1_PM_BBER OTU1_BBE
FEC_UNCOR_BLOCK_CN ODU1_PM_ES OTU1_ES

T
LSBIASCUR ODU1_PM_FEBBE OTU1_SES
LSBIASMAX ODU1_PM_FEBBER OTU1_UAS
LSBIASMIN ODU1_PM_FEES OTU1_SESR
LSIOPCUR ODU1_PM_FESES OTU1_BBER
LSIOPMAX ODU1_PM_FESESR OTU1_FEBBE
LSIOPMIN ODU1_PM_FEUAS OTU1_FEES

LSOOPCUR ODU1_PM_SES OTU1_FESES
LSOOPMAX ODU1_PM_SESR OTU1_FEUAS
LSOOPMIN ODU1_PM_UAS OTU1_FESESR
LSTMPCUR ODU1_TCMn_BBE OTU1_FEBBER
LSTMPMAX ODU1_TCMn_BBER RSBBE
LSTMPMIN ODU1_TCMn_BIAES RSES
ODU0_PM_BBE ODU1_TCMn_ES RSOFS
ODU0_PM_BBER ODU1_TCMn_FEBBE RSCSES
ODU0_PM_ES ODU1_TCMn_FEBBER RSSES
ODU0_PM_FEBBE ODU1_TCMn_FEES RSUAS
ODU0_PM_FEBBER ODU1_TCMn_FESES XCSTMPCUR
ODU0_PM_FEES ODU1_TCMn_FESESR XCSTMPMAX
ODU0_PM_FESES ODU1_TCMn_FEUAS XCSTMPMIN
NOTE
TCM6.
TN52TOM
Packets Transmitted
Bad Octets Received Multicast Packets Transmitted (1519~MTUOctets in Length)
Bad Octets Oversize Packets Received Packets Transmitted(256~511

Broadcast Packets Oversize Packets Transmitted Packets Transmitted(512~1023


Drop Events Packets Received(128~255 Packets Transmitted(65~127

Octets in Length) Octets in Length)
Drop Events at Packets Received(1519~MTU Pause Frames Transmitted

Transmission Octets in Length)
Direction

Octets in Length)


Octets in Length)
Good Octets Packets Received(64 Octets in Unicast Packets Transmitted

Transmitted Length)
Good Octets Received Packets Received(65~127 Unicast Packets Received

Octets in Length)
Jabbers Packets Transmitted

Multicast Packets Packets Transmitted(128~255

Received Octets in Length)
5.2.59 TQX Board Performance Event List

TN52TQX
FEC_AFT_COR_ER ODU2_PM_ES OTU2_BBE
FEC_AFT_COR_ERAV ODU2_PM_FEBBE OTU2_BBER

R
FEC_BEF_COR_ER ODU2_PM_FEBBER OTU2_BIAES
FEC_BEF_COR_ERAV ODU2_PM_FEES OTU2_ES

R
FEC_COR_1BIT_CNT ODU2_PM_FESESR OTU2_FEBBER
FEC_COR_BYTE_CNT ODU2_PM_FEUAS OTU2_FEES
FEC_UNCOR_BLOCK_ ODU2_PM_SES OTU2_FESES

CNT
FEC_BEF_CORER_FL ODU2_PM_SESR OTU2_FESESR

OAT
FEC_AFT_CORER_FL ODU2_PM_UAS OTU2_FEUAS

OAT
LSBIASCUR ODU2_TCMn_BBE OTU2_IAES
LSBIASMAX ODU2_TCMn_BBER OTU2_SES
LSBIASMIN ODU2_TCMn_BIAES OTU2_SESR
LSIOPMIN ODU2_TCMn_FEBBER RSES

LSOOPCUR ODU2_TCMn_FEES RSCSES
ODU2_PM_BBER ODU2_TCMn_UAS
TN52TQX
Alignment Errors Octets Transmitted Octets in Length)
Bad Octets Oversize Packets Received Packets Transmitted

Received (1519~MTUOctets in Length)
Bad Octets Oversize Packets Transmitted Packets Transmitted(256~511



Control Frames Packets Received(128~255 Packets Transmitted(65~127

Control Frames Packets Received(1519~MTU Pause Frames Transmitted


Octets in Length)

Octets in Length)
Jabbers Packets Received(64 Octets in Unicast Packets Transmitted

Length)
Multicast Packets Packets Received(65~127 Octets Unicast Packets Received

Received in Length)
Multicast Packets Packets Transmitted

Transmitted

Octets Received Packets Transmitted(1024~1518

Octets in Length)
5.2.60 VA1 Board Performance Event List

TN12VA1
5.2.61 VA4 Board Performance Event List

TN12VA4
5.2.62 WMU Board Performance Event List

PCLSWLCUR PCLSOPCUR XCSTMPMAX
PCLSWLOCUR XCSTMPCUR XCSTMPMIN
5.2.63 WSD9 Board Performance Event List

ICTMPCUR SUMIOPCUR XCSTMPCUR
ICTMPMAX SUMIOPMAX XCSTMPMAX
ICTMPMIN SUMIOPMIN XCSTMPMIN
5.2.64 WSM9 Board Performance Event List

ICTMPCUR SUMOOPCUR XCSTMPCUR
ICTMPMAX SUMOOPMAX XCSTMPMAX
ICTMPMIN SUMOOPMIN XCSTMPMIN

5.2.65 WSMD2 Board Performance Event List

5.2.66 WSMD4 Board Performance Event List

5.2.67 XCH Board Performance Event List

TN52XCH
5.2.68 XCM Board Performance Event List

TN52XCM
5.2.69 XCT Board Performance Event List


Alarms and Performance Events Reference 6 Performance Event Processing
6 Performance Event Processing
About This Chapter
The performance event is an important parameter to evaluate the working performance of

equipment. Being acquainted with the generation principle, related boards and related alarms
helps you discover hidden trouble in routine maintenance and locate faults in troubleshooting.
If a performance event exceeds the threshold, the related alarms are generated. Therefore, upon
any performance event, check any related alarms and handle the event accordingly.
6.1 AUPJCHIGH
6.2 AUPJCLOW
6.3 AUPJCNEW
6.4 BCV
6.5 CCV
6.6 CRC4BBE
6.7 CRC4FEBBE
6.8 CRC4ES
6.9 CRC4FEES
6.10 CRC4FESES
6.11 CRC4FEUAS
6.12 CRC4SES
6.13 CRC4UAS
6.14 EDTMP
6.15 EDTPL
6.16 ENVTMP
6.17 FEC_AFT_COR_ER

6.18 FEC_AFT_COR_ERAVR
6.19 FEC_BEF_COR_ER
6.20 FEC_BEF_COR_ERAVR
6.21 FEC_COR_0BIT_CNT
6.23 FEC_COR_BYTE_CNT
6.24 FEC_UNCOR_BLOCK_CNT
6.25 HPBBE
6.26 HPES
6.27 HPFEBBE
6.28 HPFEES
6.29 HPFESES
6.30 HPFEUAS
6.31 HPSES
6.32 HPUAS
6.33 ICCLC
6.34 ICTMP
6.35 LSBIAS
6.36 LSCLC
6.37 LSIOP
6.38 LSOOP
6.39 LSTMP
6.40 MSBBE
6.41 MSES
6.42 MSFEBBE
6.43 MSFEES
6.44 MSFESES
6.45 MSFEUAS
6.46 MSSES
6.47 MSUAS
6.48 ODU2PMBIP8
6.49 ODUk_PM_BBE

6.50 ODUk_PM_BBER
6.51 ODUk_PM_ES
6.52 ODUk_PM_FEBBE
6.53 ODUk_PM_FEBBER
6.54 ODUk_PM_FEES
6.55 ODUk_PM_FESES
6.56 ODUk_PM_FESESR
6.57 ODUk_PM_FEUAS
6.58 ODUk_PM_SES
6.59 ODUk_PM_SESR
6.60 ODUk_PM_UAS
6.61 ODUk_TCMn_BBE
6.62 ODUk_TCMn_BBER
6.63 ODUk_TCMn_BIAES
6.64 ODUk_TCMn_ES
6.65 ODUk_TCMn_FEBBE
6.66 ODUk_TCMn_FEBBER
6.67 ODUk_TCMn_FEES
6.68 ODUk_TCMn_FESES
6.69 ODUk_TCMn_FESESR
6.70 ODUk_TCMn_FEUAS
6.71 ODUk_TCMn_IAES
6.72 ODUk_TCMn_SES
6.73 ODUk_TCMn_SESR
6.74 ODUk_TCMn_UAS
6.75 OSPICCV
6.76 OSPITMP
6.77 OTU2SMBIP8
6.78 OTUk_BBE
6.79 OTUk_BBER
6.80 OTUk_ES
6.81 OTUk_FEBBE

6.82 OTUk_FEBBER
6.83 OTUk_FEES
6.84 OTUk_FESES
6.85 OTUk_FESESR
6.86 OTUk_FEUAS
6.87 OTUk_SES
6.88 OTUk_SESR
6.89 OTUk_UAS
6.90 PCLSOP
6.91 PCLSSN
6.92 PCLSWL
6.93 PCLSWLO
6.94 RPL
6.95 RSBBE
6.96 RSCSES
6.97 RSES
6.98 RSOFS
6.99 RSOOF
6.100 RSSES
6.101 RSUAS
6.102 SUMIOP
6.103 SUMOOP
6.104 TLB
6.105 TPL
6.106 VC3BBE
6.107 VC3CSES
6.108 VC3ES
6.109 VC3FEBBE
6.110 VC3FECSES
6.111 VC3FEES
6.112 VC3FESES
6.113 VC3FEUAS

6.114 VC3SES
6.115 VC3UAS
6.116 WCV
6.117 XCSTMP

6.1 AUPJCHIGH
Description
Administrative unit pointer justification count high
It indicates the positive justification count of the AU pointer when the rate of VC frame is
adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number
of pointer justification counts, however, cause bit errors in the services. In this case, determine
the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the
signal transmission quality.
Generation Principle and Possible Causes

The root cause of the AU pointer justification is that the clocks of NEs on the SDH network are
not synchronous. The possible causes of the event are as follows:
l The performance of the external clock is degraded.

l The clocks in two NEs trace each other because the optical fibers are connected incorrectly.
l The equipment performance is degraded due to high temperature.
l The clocks are configured incorrectly. If the SSM protocol is enabled but the clock IDs are
not set, the loss of the primary clock source causes the network-wide pointer justification
event.
l The clock quality is degraded because the SSM clock protection is disabled.
l The performance of the line board is degraded.
l The performance of the clock board is degraded.
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the SYN_BAD, LTI, S1_SYN_CHANGE and
EXT_SYNC_LOS, are generated in the whole network. If yes, take priority to clear them.
Step 2 For the network-wide pointer justification, check whether the clock configurations are consistent
with those specified in the plan, including clock ID, SSM protocol, and clock tracing level.
Step 3 For the non-network-wide pointer justification, check whether the 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 the technical support engineers
of Huawei.
----End

Related Information
None
6.2 AUPJCLOW
Description
Administrative unit pointer justification count low
It indicates the negative justification count of the AU pointer when the rate of VC frame is
adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number
of pointer justification counts, however, cause bit errors in the services. In this case, determine
the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the
signal transmission quality.

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
not synchronous. The possible causes are as follows:

event.
Related Alarms
None
Procedure

of Huawei.
----End
Related Information
None
6.3 AUPJCNEW
Description
New count of administrative unit pointer
Impact on System
A little pointer justification does not affect the services. A large pointer justification can cause
bit errors in the services and in this case, you need to find out the causes and take proper measures
to ensure the transmission quality and prevent alarms.

The root cause of generating new data flag (pointer) for the AU pointer justification event is that
the clocks of NEs in the SDH network are not synchronous. As a result, the new AU data flag
(pointer) event is generated. The possible causes are as follows:

event.
Related Alarms
None
Procedure

of Huawei.
----End
Related Information
None
6.4 BCV
Description
Pump Laser Back Facet Current
It includes:
l BCVMAX: stands for the maximum value during a period of time.

l BCVMIN: stands for the minimum value during a period of time.
l BCVCUR: stands for the current value.
Impact on System
None

Back facet current is current O/E converted from part of light reflected from the resonant cavity
of a laser. The back facet current reflects the laser output optical power value. If the BCVCUR
is 0, the laser is faulty. In this case, replace the board where this faulty laser resides in.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None

6.5 CCV
Description
Pump Laser Cooling Current
It includes:
l CCVMAX: stands for the maximum value during a period of time.

l CCVMIN: stands for the minimum value during a period of time.
l CCVCUR: stands for the current value.
Impact on System
None

Use an A/D converter to sample the voltage corresponding to the cooling current of each laser,
and convert the voltage into cooling current. This value shows the working status of the cooling
circuit in a certain laser.
Related Alarms
Alarm Name Correlation
PUMP_COOL_EXC It is generated when the cooling current of the

laser exceeds the normal range.
Procedure
Step 1 If the PUMP_COOL_EXC alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.6 CRC4BBE
Description
CRC4 Background Block Error

Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause
and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal
transmission quality. If the number of bit errors exceeds the threshold, the CRC4_CROSSTR
alarm is generated.

CRC error is detected by checking the received parity bit. The background block error means
there are one or more data blocks containing error bits during transmission.
Related Alarms
CRC4_CROSSTR CRC4 multi-frame error code count exceeds

the threshold. The alarm is generated when
the number of the bit errors in the CRC4
multiframe exceeds the threshold.
Procedure
Step 1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.7 CRC4FEBBE
Description
CRC4 Far End Background Block Error
Impact on System
There are bit errors in the services. If the number of bit errors is small, there is no impact on the
services. If the number of bit errors is large, determine the cause and solve the problem in a
timely manner to avoid any alarm, thus to ensure the signal transmission quality.

CRC error is detected by checking the received parity bit. The background block error means
there are one or more data blocks containing error bit during transmission. And the far end
background block error refers to the background block error detected at the opposite end.

Related Alarms

Procedure
----End
Related Information
None
6.8 CRC4ES
Description
CRC4 errored seconds
Impact on System
There are bit errors in the services. If the CRC4 errored seconds are generated continuously,
determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure
the signal transmission quality.

CRC error is detected by checking the received parity bit. An errored second contains more than
one error block.
Related Alarms
CRC4_CROSSTR CRC4 multi-frame error code exceeds the

threshold. The alarm is generated when the
number of the bit errors in the CRC4 multi-
frame exceeds the threshold.

Procedure
----End
Related Information
None
6.9 CRC4FEES
Description
CRC4 far end errored second
Impact on System
There are bit errors in the services. If the far-end errored seconds are generated continuously,
the signal transmission quality. If the number of bit errors exceeds the threshold, the
CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. An errored second contains more than
one error block. And the far end errored second refers to the errored second detected at the
opposite end.
Related Alarms
CRC4_CROSSTR CRC4 multi-frame error code counter

exceeds the threshold. The alarm is generated
when the number of the bit errors in the CRC4
Procedure
----End
Related Information
None

6.10 CRC4FESES
Description
CRC4 far end severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
to avoid any alarm, and thus to ensure the signal transmission quality. If the number of bit errors
exceeds the threshold, the CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. During a severely errored second,
there is at least one defect. And the far end severely errored second refers to the severely errored
second detected at the opposite end.
Related Alarms

Procedure
----End
Related Information
None
6.11 CRC4FEUAS
Description
CRC4 far end unavailable second

Impact on System
because the bit errors have affected the signal transmission quality. If the number of bit errors

CRC error is detected by checking the received parity bit. If the severely errored seconds last
for more than 10 seconds, the unavailable second starts from the beginning of the 11th second,
and the former 10 severely errored seconds are counted as unavailable. If the severely errored
second disappears for more than 10 seconds, the available time starts from the beginning of the
11th second, and the former 10 seconds are counted as available.
Related Alarms

Procedure
----End
Related Information
None
6.12 CRC4SES
Description
CRC4 severely errored second
Impact on System

CRC error is detected by checking the received parity bit. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks.

Related Alarms

Procedure
----End
Related Information
None
6.13 CRC4UAS
Description
CRC4 unavailable second
Impact on System

CRC error is detected by checking the received parity bit. If the severely errored seconds last
for more than 10 seconds, the unavailable second starts from the beginning of the 11th second,
and the former 10 severely errored seconds are counted as unavailable. If the severely errored
second disappears for more than 10 seconds, the available time starts from the beginning of the
11th second, and the former 10 seconds are counted as available.
Related Alarms


Procedure
----End
Related Information
None
6.14 EDTMP
Description
Laser temperature value
It includes:
l EDTMPMAX: stands for the maximum value during a period of time.

l EDTMPMIN: stands for the minimum value during a period of time.
l EDTMPCUR: stands for the current value.
Impact on System
None

This performance event is detected by hardware detecting circuit and then the result is calculated
by the software for conversion. If the performance is not in the normal range, the EDFA module
might be faulty.
Related Alarms
PUM_TEM_ALM Working temperature of the pump laser exceeds the threshold. This
alarm is generated when the pump laser operating temperature of the
optical amplifier unit exceeds the threshold.
Procedure
Step 1 Refer to the method of handling the PUM_TEM_ALM.
----End
Related Information
None

6.15 EDTPL
Description
Pump output optical power
It includes:
l EDTPLMAX: stands for the maximum value during a period of time.

l EDTPLMIN: stands for the minimum value during a period of time.
l EDTPLCUR: stands for the current value.
Impact on System
Bit errors may be generated in the services and the services may be interrupted.

This performance event is detected by hardware detecting circuit and then the result is calculated
by the software for conversion. If the performance is not in the normal range, the EDFA module
might be faulty.
Related Alarms
OUT_PWR_HIGH It is generated when the optical power output by the pump laser is
higher than the upper threshold.
OUT_PWR_LOW It is generated when the optical power output by the pump laser is
lower than the lower threshold.
Procedure
Step 1 Refer to the method of handling the OUT_PWR_HIGH or OUT_PWR_LOW.
----End
Related Information
None
6.16 ENVTMP
Description
Board environmental temperature

It includes:
l ENVTMPMAX: stands for the maximum value during a period of time.
l ENVTMPMIN: stands for the minimum value during a period of time.
l ENVTMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by hardware detecting to show the ambient temperature of
the board.
Related Alarms
TEMP_OVER It is generated when the board working

temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the proper handling procedures.
----End
Related Information
None
6.17 FEC_AFT_COR_ER
Description
After FEC correct errored rate
Impact on System
After the error correction, in normal cases, the value should be 0. If the value is not 0, it indicates
that the bit errors in the services bring impact on the transmission quality. In this case, determine
the cause in a timely manner.

This performance event shows that there are still errors at the receiver after FEC. This
performance event is caused by low OSNR at the receiving end. In normal cases, it should be
0.

In this case, there must be FEC_BEF_COR_ER accompanied and you should check the alarm
in a timely manner.
Related Alarms
BEFFEC_EXC Signal degraded before FEC alarm. Signals sent from WDM sides of
the opposite-end OTUs have the FEC function. As a result, before
performing signal FEC in the receive direction of WDM side of the
local-end OTU, the local-end OTU counts the bit error rate. This alarm
is generated when the counted bit error rate exceeds the threshold.
Procedure
Step 1 Refer to the procedure for handling the BEFFEC_EXC.
----End
Related Information
None
6.18 FEC_AFT_COR_ERAVR
Description
After FEC Correct Average Errored Rate in monitor period.
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that
the bit errors in the services bring impact on the transmission quality. In this case, determine the
cause in a timely manner.

This performance event shows there are still errors at the receiver after FEC. This performance
event is caused by low OSNR at the receiving end. Normally, it should be zero.
In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the optical
power to increase the OSNR.

Related Alarms
Procedure
----End
Related Information
None
6.19 FEC_BEF_COR_ER
Description
BER before FEC
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate
(BER) is low, the system operates normally. If the BER is high, determine the causes and solve
the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission
quality.

The cause for the BER before the FEC is that the receiver detects bit errors, which are caused
by dispersion, unstable performance of the optical interface, and/or excessively high attenuation.
Related Alarms

Procedure
----End
Related Information
None
6.20 FEC_BEF_COR_ERAVR
Description
Before FEC Correct Average Errored Rate in monitor period.
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate
(BER) is low, the system operates normally. If the BER is high, determine the cause and solve
the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR
at the receiving end. Normally, it should be zero.
Related Alarms
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None

Description
Forward error correction - corrected 0 bit count
Impact on System
None

This performance event shows the number of 0bit corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
Description
Forward error correction - corrected 1 bit count
Impact on System
None

This performance event shows the number of 1bit corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR.
Related Alarms
None

Procedure
Step 1 None
----End
Related Information
None
6.23 FEC_COR_BYTE_CNT
Description
Forward error correction - corrected byte count
Impact on System
None

This performance event shows the number of byte corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR. Normally, it should be 0.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.24 FEC_UNCOR_BLOCK_CNT
Description
Forward error correction - uncorrected block count
Impact on System
There are bit errors in the services and the signal transmission quality is affected.


This performance event shows the number of received error frames that cannot be corrected by
FEC, and indicates that signals of low OSNR are beyond the correction capability of FEC.
Normally, the performance value should be 0.
Related Alarms
BEFFEC_EXC Signal degraded before FEC alarm. Signals sent from WDM side of
the local-end OTU, the local-end OTU counts the bit error rate. This
alarm is generated when the counted bit error rate exceeds the
threshold.
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None
6.25 HPBBE
Description
Higher order path background block error
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the
system is not affected. You need to, however, find out the causes and take proper measures in
time to avoid any alarm, which affects the quality of the signals transmitted in the higher order
path.

The HPBBEs are detected by means of detecting the B3 byte. The possible causes of the event
are as follows:
l There is interference from the external environment.

l A fault occurs in the switch that interworks with the SDH equipment.
l The signal cable is faulty.
l The line board is faulty.

l The cross-connection unit is faulty.

l The clock unit is faulty.
Related Alarms
B3_SD When the count of B3 bit errors in the alarm path exceeds the threshold of
the B3_SD but lower than the threshold of the B3_EXC, the alarm is
reported.
B3_EXC When the count of B3 bit errors in the alarm path exceeds the threshold of
the B3_EXC, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
The background block error means that one or more bit errors occur in the data block during
transmission.
6.26 HPES
Description
Higher order path errored second
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible
causes of the event are as follows:



Related Alarms
B3_SD When the count of B3 bit errors in the alarm path exceeds the
threshold of the B3_SD but lower than the threshold of the B3_EXC,
the alarm is reported.
B3_EXC When the count of B3 bit errors in the alarm path exceeds the
threshold, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm.
----End
Related Information
The errored second (ES) refers to the second in which one or more errored blocks are detected.
6.27 HPFEBBE
Description
Higher order path far end background block error
Impact on System
A small number of bit errors occur at the far end of the higher order path. If no related alarm is
generated, the system is not affected. You need to, however, find out the causes and take proper
measures in time to avoid any alarm, which affects the quality of the signals transmitted in the
higher order path.

The HPFEBBE refers to the higher order path block error that is detected at the opposite station.
The possible causes of the event are as follows:



Related Alarms
HP_REI If the board has detected that the value is 1-8 for bits 1-4 of the G1 byte
in the higher order path, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the HP_REI alarm.
----End
Related Information
The background block error means that one or more bit errors occur in the data block during
transmission.
6.28 HPFEES
Description
Higher order path far end errored second
Impact on System
A small number of bit errors occur at the far end of the higher order path. If no related alarm is
higher order path.


l The cross-connection clock unit is faulty.

Related Alarms
HP_REI If the board has detected that the value is 1-8 for bits 1-4 of the G1
byte in the higher order path, the alarm is reported.
Procedure
----End
Related Information
Remote Errored Second
The remote errored second refers to the errored second that is detected at the peer end.
6.29 HPFESES
Description
Higher order path far end severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarm is
higher order path.


l The cross-connect unit is faulty.

Related Alarms
HP_REI If the board has detected that the value is 1-8 for bits 1-4 of the G1
byte in the higher order path, the alarm is reported.
Procedure
----End
Related Information
The severely errored second (SES) refers to the second in which more than 30% errored blocks
occur or at least one serious disturbance period (SDP) occurs.
6.30 HPFEUAS
Description
Higher order path far end unavailable second
Impact on System
If bit errors occur in the services on a remote NE, detect the causes and troubleshoot the problem
in a timely manner. Otherwise, alarms will be generated and the signal transmission quality will
be affected.

HPFEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l The fiber performance degrades and the attenuation is excessively high at the opposite
station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:

l The signal attenuation at the receive side of the line board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the service board do not work with each other properly at the
opposite station.
l The fan of the opposite equipment is faulty.
l The board fails or the board performance degrades at the opposite station.
Related Alarms
HP_REI Higher order path remote error indication
HP_RDI Remote defect indication in higher order paths
Procedure
Step 1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None.
6.31 HPSES
Description
Higher order path severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the
path.




Related Alarms
B3_SD When the count of B3 bit errors in the alarm path exceeds the
threshold of the B3_SD but lower than the threshold of the B3_EXC,
B3_EXC When the count of B3 bit errors in the alarm path exceeds the
threshold, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
The severely errored second (SES) refers to the second in more than 30% errored blocks occur
or at least one serious disturbance period (SDP) occurs.
6.32 HPUAS
Description
Higher order path unavailable second
Impact on System
l A great number of bit errors occur in the higher order path. If no related alarm is generated,
the system is not affected. You need to, however, find out the causes and take proper
measures in time to avoid any alarm, which affects the quality of the signals transmitted in
the higher order path.
l If the performance event is generated, check whether the AU_AIS, B3_EXC and
HP_UNEQ alarms are generated. If yes, the services may be interrupted.

Bit errors in the higher order path are detected by means of detecting the B3 byte. When signals
are consecutively received for 10 seconds, and if the bit error ratio per second is more than

10-3, the period from the first second is called the period of UAS (unavailable second). When
signals are consecutively received for 10 seconds, and if the bit error ratio per second is less than
10-3, the period from the first second is called the period of available second. The errored second
(ES) refers to the second in which one or more errored blocks occur. The possible causes of the
event are as follows:

Related Alarms
B3_SD When the count of B3 bit errors in the alarm path exceeds the threshold of
the B3_SD but lower than the threshold of the B3_EXC, the alarm is
reported.
B3_EXC When the count of B3 bit errors in the alarm path exceeds the threshold,
AU_AIS When the alarm is generated, the HPUAS value is increased.
HP_TIM When the alarm is generated, the HPUAS value is increased.
HP_UNEQ When the alarm is generated, the HPUAS value is increased.
Procedure
Step 1 Refer to the method of handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and
HP_UNEQalarms.
----End
Related Information
None
6.33 ICCLC
Description
Module cooling current
It includes:

l ICCLCMAX: stands for the maximum value during a period of time.

l ICCLCMIN: stands for the minimum value during a period of time.
l ICCLCCUR: stands for the current value.
Impact on System
None

This performance event is generated by software checking with the cooling current detecting
circuit on the board, to show the working status of module cooling current.
Related Alarms
Procedure
Step 1 If the MODULE_COOLCUR_OVER alarm is generated, see the handling procedure of the
alarm.
----End
Related Information
None
6.34 ICTMP
Description
Module temperature
It includes:
l ICTMPMAX: stands for the maximum value during a period of time.

l ICTMPMIN: stands for the minimum value during a period of time.
l ICTMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by checking the current working temperature of module to
show the working temperature of a module.

Related Alarms
MODULE_TEMP_OVER It is generated when the working temperature

of a module exceeds the threshold.
Procedure
Step 1 If the MODULE_TEMP_OVER alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.35 LSBIAS
Description
Laser bias current
It includes:
l LSBIASMAX: stands for the maximum value during a period of time.

l LSBIASMIN: stands for the minimum value during a period of time.
l LSBIASCUR: stands for the current value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
TD It is generated when the working current of a

laser exceeds the threshold or a multiple of
the threshold.
LSR_WILL_DIE It is generated when the working current of a

laser exceeds the threshold or a multiple of
the threshold.

Procedure
Step 1 If the TD alarm is generated, see the handling procedure of the alarm.
Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.36 LSCLC
Description
Laser cooling current
It includes:
l LSCLCMAX: stands for the maximum value during a period of time.
l LSCLCMIN: stands for the minimum value during a period of time.
l LSCLCCUR: stands for the current value.
Impact on System
When the cooling current of a laser exceeds the threshold, the optical module of the board works
abnormally. As a result, services cannot be transmitted or received normally.

External cooling equipment should be provided to keep the temperature stable for a laser to
work. The laser cooling current shows the working status of cooling equipment or circuit.
Related Alarms
LSR_COOL_ALM It is generated when the laser cooling current

exceeds the pre-set threshold.
Procedure
Step 1 If the LSR_COOL_ALM alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None

6.37 LSIOP
Description
Input optical power
It includes:
l LSIOPMAX: stands for the maximum value during a period of time.

l LSIOPMIN: stands for the minimum value during a period of time.
l LSIOPCUR: stands for the current value.
Impact on System
When the input optical power is excessively high or low, bit errors and the LOF alarm may be
generated in the received signals, which brings impact on the services.

The hardware checks the optical module and then the software converts the check result into
LSIOP to show the input optical power performance of a board.
Related Alarms
IN_PWR_HIGH It is generated when the optical power input by board is higher than
the upper threshold.
IN_PWR_LOW It is generated when the optical power input by board is lower than
the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
history performance value and the change in optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW alarm.
Step 3 If an alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None

6.38 LSOOP
Description
Output optical power
It includes:
l LSOOPMAX: stands for the maximum value during a period of time.

l LSOOPMIN: stands for the minimum value during a period of time.
l LSOOPCUR: stands for the current value.
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal transmission
of services.

The hardware checks the optical module and then the software converts the check result into
LSOOP value to show the output optical power performance of the laser on a board.
Related Alarms
OUT_PWR_HIGH It is generated when the optical power output by a board is higher than
the upper threshold.
OUT_PWR_LOW It is generated when the optical power output by a board is lower than
the lower threshold.
TF It is generated when the optical power output by a board is 1 dB lower

than the lower threshold.
Procedure
history performance value and the change of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
history performance value and the change of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm.
Step 3 If an alarm is generated, see the Related Alarms.
----End

Related Information
None
6.39 LSTMP
Description
Laser temperature
It includes:
l LSTMPMAX: stands for the maximum value during a period of time.

l LSTMPMIN: stands for the minimum value during a period of time.
l LSTMPCUR: stands for the current value.
Impact on System
None

Normally, the laser temperature is a stable value obtained by software through calculating the
result outputted by the temperature detecting circuit in the laser.
Related Alarms
TEM_HA Laser temperature is excessively high. This alarm is generated when

the laser temperature is higher than the upper threshold of the laser
temperature.
TEM_LA Laser temperature is excessively low. This alarm is generated when

the laser temperature is lower than the upper threshold of the laser
temperature.
Procedure
Step 1 If the TEM_HA or TEM_LA alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None

6.40 MSBBE
Description
MS background block error
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.

The multiplex section errors are detected by checking the B2 byte. The background block error
means there are one or more data blocks containing error bits during transmission.
Related Alarms
B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceeds the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceeds the signal
degrade (SD) threshold.
MS_AIS Multiplex section alarm indication. The alarm is generated when the
opposite station transmits the MS_AIS signals or the receive part of
the local station is faulty.
MS_CROSSTR Multiplex section performance exceeds the threshold. The alarm is

generated when the performance module reports the threshold
crossing of the performance events in the multiplex section.
R_OOF Out of frame on receiving line. This alarm is generated when the heads
of consecutive five frames fail to be detected.
R_LOF Loss of frame on receiving line. This alarm is generated when the
frame alignment processing is out of frame (OOF) in consecutive 3ms.
Procedure
Step 1 Refer to the method of handling the B2_EXC.
----End

Related Information
None
6.41 MSES
Description
MS errored second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, determine
the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal
transmission quality.

The multiplex section errors are detected by checking the B2 byte. The MS errored second means
there are more than one error block transmitted in this second.
Related Alarms

frame alignment processing is out of frame (OOF) in consecutive 3
ms.

Procedure
----End
Related Information
None
6.42 MSFEBBE
Description
MS far end background block error
Impact on System
If bit errors are generated in the services on a far-end NE but no related alarm is reported on the
opposite NE, there is no impact on the system. You, however, need to determine the cause and
quality.

The multiplex section errors are detected by checking the B2 byte. The background block error
means there are one or more data blocks containing error bit during transmission. And the far
end background block error refers to the background block error detected at the opposite end.
Related Alarms
MS_RDI Multiplex section remote defect indication alarm. The alarm is

generated at the local station if the opposite station back transmits the
information through overhead when the WDM-side receive part of
the opposite station is faulty.
Procedure
Step 1 Refer to the method of handling the MS_RDI.
----End
Related Information
None

6.43 MSFEES
Description
MS far end errored second
Impact on System
quality.

The multiplex section errors are detected by checking the B2 byte. An errored second contains
more than one error block. And the far end errored second refers to the errored second detected
at the opposite end.
Related Alarms

Procedure
----End
Related Information
None
6.44 MSFESES
Description
MS far end severely errored second
Impact on System

quality.

The multiplex section errors are detected by checking the B2 byte. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely
errored second refers to the severely errored second detected at the opposite end.
Related Alarms

Procedure
----End
Related Information
None
6.45 MSFEUAS
Description
MS far end unavailable second
Impact on System
quality.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds
last for more than 10 seconds, the unavailable second starts from the beginning of the 11th
second, and the former 10 severely errored seconds are counted as unavailable. If the severely
errored second disappears for more than 10 seconds, the available time starts from the beginning
of the 11th second, and the former 10 seconds are counted as available.

Related Alarms

Procedure
----End
Related Information
None
6.46 MSSES
Description
MS severely errored second
Impact on System
quality.

The multiplex section errors are detected by checking the B2 byte. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms


frame alignment processing is out of frame (OOF) in consecutive 3ms.
Procedure
----End
Related Information
None
6.47 MSUAS
Description
MS unavailable second
Impact on System
to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds
last for more than 10 seconds, the unavailable second starts from the beginning of the 11th
second, and the former 10 severely errored seconds are counted as unavailable. If the severely
errored second disappears for more than 10 seconds, the available time starts from the beginning
of the 11th second, and the former 10 seconds are counted as available.

Related Alarms

R_LOS Loss of signal on receiving line. This alarm is generated when the
receive side receives no signals.

MS_REI Multiplex section remote error indication. The alarm is generated

when the remote end detects the bit error block.
Procedure
----End
Related Information
None
6.48 ODU2PMBIP8
Description
ODU PM section BIP8
Impact on System
quality.


This performance event shows the number of errors that a board with an OTN interface detects
in path monitoring through the BIP8 check. Normally, the performance value should be zero.
Related Alarms
PM_BIP8_OVER Bit interleaved parity (BIP) in the PM section of the ODU layer
exceeds the upper threshold. The alarm is generated when the number
of BIP8 bit errors of the PM section on the optical channel data unit
layer exceeds the upper threshold.
PM_BIP8_SD BIP in the PM section of the ODU layer degrades. The alarm is
generated when the number of BIP8 bit errors of the PM section on
the optical channel data unit layer exceeds the degrade threshold.
Procedure
----End
Related Information
None
6.49 ODUk_PM_BBE
Description
ODU PM section background block error
Impact on System

ODU PM section errors are detected by checking the received parity bits. The background block
error means there are one or more data blocks containing error bits during transmission.

Related Alarms
ODUk_PM_EXC Bit interleaved parity (BIP) in the PM section of the ODU layer
exceeds the upper threshold. The alarm is generated when the number
of BIP8 bit errors of the PM section on the optical channel data unit
layer exceeds the upper threshold.
ODUk_PM_DEG Bit interleaved parity signal in the PM section of the ODU layer
degrades. The alarm is generated when the number of BIP8 bit errors
of the PM section of the ODU layer exceeds the degrade threshold.
Procedure
Step 1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.50 ODUk_PM_BBER
Description
ODU PM section ratio of background block error
Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is
large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to
ensure the signal transmission quality.

ODU PM section background block errors are detected by checking the received parity bits. The
background block error refers to a data block where at least one bit error is generated during the
transmission. Background block error ratio of the ODU PM section refers to the ratio of the
number of background block errors of the ODU PM section to the number of all blocks minus
the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-
cSES) x blocks per second].

Related Alarms
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. The alarm
is generated when the number of BIP8 bit errors of the PM section on
the optical channel data unit layer exceeds the upper threshold.
of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.51 ODUk_PM_ES
Description
ODU PM section errored second
Impact on System
quality.

ODU PM section errors are detected by checking the received parity bit. An errored second
contains more than one error block.
Related Alarms

of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.52 ODUk_PM_FEBBE
Description
ODU PM section far end background block error
Impact on System
quality.

ODU PM section errors are detected by checking the received parity bit. The background block
error means there are one or more data blocks containing error bit during transmission. And the
far end background block error refers to the background block error detected at the opposite end.
Related Alarms
ODUk_PM_BDI ODU PM section backward defect indication.
Procedure
Step 1 Refer to the method of handling the ODUk_PM_BDI.
----End

Related Information
None
6.53 ODUk_PM_FEBBER
Description
ODU PM section ratio of far end background block error
Impact on System

ODU PM section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the ODU PM section refers to the ratio of the
number of background block errors of the ODU PM section to the number of all blocks minus
cSES) x blocks per second]. And the ratio of far end background block error refers to the ratio
of background block error detected at the opposite end.
Related Alarms
Procedure
----End
Related Information
None
6.54 ODUk_PM_FEES
Description
ODU PM section far end errored second

Impact on System
quality.

ODU PM section error is detected by checking the received parity bit. An errored second contains
Related Alarms
Procedure
----End
Related Information
None
6.55 ODUk_PM_FESES
Description
ODU PM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,

Errors are detected by checking the received parity bit. During a severely errored second, there
is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored
second means the severely errored second appears consecutively. It might result in the
interruption of the service that shares a fiber link with the supervisory channel. And the far end
severely errored second refers to the severely errored second detected at the opposite end.

Related Alarms
Procedure
----End
Related Information
None
6.56 ODUk_PM_FESESR
Description
ODU PM section ratio of far end severely errored second
Impact on System

Bit errors are detected by checking the received parity bits. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks. Severely errored second (SES)
ratio refers to the ratio of SES count in a certain period of time to the total available time. Far
end severely errored second ratio refers to the ratio of errored seconds that are detected at the
opposite end.
Related Alarms
Procedure
----End

Related Information
None
6.57 ODUk_PM_FEUAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services on a far-end NE. The services may be affected.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from
the beginning of the 11th second, and the former 10 severely errored seconds are counted as
unavailable. If the severely errored second disappears for more than 10 seconds, the available
time starts from the beginning of the 11th second, and the former 10 seconds are counted as
available. And the far end unavailable second refers to the unavailable second detected at the
opposite end.
Related Alarms
Procedure
----End
Related Information
None
6.58 ODUk_PM_SES
Description
ODU PM section severely errored second

Impact on System
There are bit errors in services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.

ODU PM Section error is detected by checking the received parity bit. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. The consecutive
severely errored second means the severely errored second appears consecutively, it might result
in the interruption of the service that shares a fiber link with the supervisory channel.
Related Alarms
is generated when the number of BIP8 bit errors of the PM section of
ODUk_PM_DEG Optical channel data unit layer, path monitoring section bit
interleaved parity signal degraded. The alarm is generated when the
number of BIP8 bit errors of the PM section of the optical channel
data unit layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.59 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
Impact on System


ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
6.60 ODUk_PM_UAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

available.

Related Alarms
number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
6.61 ODUk_TCMn_BBE
Description
ODUk TCMn section background block error
Impact on System

ODUk TCMn section errors are detected by checking the received parity bits. The background
block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
ODUk_TCMn_DEG ODU TCMn burst-mode signal degradation.
ODUk_TCMn_EXC ODU TCMn Poisson-mode excessive bit errors.

Procedure
Step 1 On the U2000, check whether there are a great amount of BIP8 bit errors of the TCM section in
the input signals on the client side. If yes, rectify the fault on the client-side equipment.
Step 2 If the performance keeps deteriorating, see the handling procedure for the
ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.62 ODUk_TCMn_BBER
Description
ODUk TCMn section ratio of background block error
Impact on System

ODUk TCMn section background block errors are detected by checking the received parity bits.
The background block error refers to a data block where at least one bit error is generated during
the transmission. Background block error ratio of the ODUk TCMn section refers to the ratio of
the number of background block errors of the ODUk TCMn section to the number of all blocks
minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-
UAS-cSES) x blocks per second].
Related Alarms
Procedure

Step 2 If the performance event persists, see the handling procedure for the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.63 ODUk_TCMn_BIAES
Description
ODU TCMn section backward introducing alignment errored second
Impact on System
There are errors in frame alignment. Determine the cause and solve the problem in a timely
manner to ensure the signal transmission quality.

ODU TCMn section backward introducing alignment errored seconds are detected by checking
the backward input frame alignment bits. Backward incoming alignment errored second refers
to the second where more than one backward input frame alignment errors are generated.
Related Alarms
None
Procedure
range. For the optical power specifications of the board, see the Product Description. If the input
IN_PWR_LOW alarms.
Step 2 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
Related Information
None

6.64 ODUk_TCMn_ES
Description
ODUk TCMn section errored second
Impact on System

ODUk TCMn section error is detected by checking the received parity bit. An errored second
contains more than one error block.
Related Alarms
Procedure
Step 2 If the performance event persists, see the handling procedure for the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.65 ODUk_TCMn_FEBBE
Description
ODUk TCMn section far end background block error
Impact on System

quality.

Far end background block of the ODUk TCMn section is detected by checking the received
backward error bits. The background block error means there are one or more data blocks
containing error bit during transmission. And the far end background block error refers to the
background block error detected at the opposite end. The backward error bit means the inserted
indication to the local end after the background block error is detected at the opposite end.
Related Alarms
None
Procedure
IN_PWR_LOW alarms.
Troubleshooting.
----End
Related Information
None
6.66 ODUk_TCMn_FEBBER
Description
ODUk TCMn section ratio of far end background block error
Impact on System

Background block errors are detected by checking the received parity bits. The background block
error refers to a data block where at least one bit error is generated during the transmission. Far
end background block error ratio of the ODUk TCMn section refers to the ratio of the number
of far end background block errors of the ODUk TCMn section to the number of all blocks minus
cSES) x blocks per second].

Related Alarms
None
Procedure
IN_PWR_LOW alarms.
Troubleshooting.
----End
6.67 ODUk_TCMn_FEES
Description
ODUk TCMn section far end errored second
Impact on System

ODUk backward error indication of the TCMn section is determined by the BEI that is inserted
at the far end. Far end errored second refers to the second where the checked signals contain at
least one block error at the far end.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_BDI.
----End
Related Information
None

6.68 ODUk_TCMn_FESES
Description
ODUk TCMn section far end severely errored second
Impact on System

ODUk far end severely errored second of the TCMn section is determined by the BEI that is
inserted at the far end. During a far end severely errored second, there is at least one defect or
30% of data blocks are error blocks. The fiber line may be faulty.
Related Alarms
None
Procedure
IN_PWR_LOW alarms.
Troubleshooting.
----End
Related Information
None
6.69 ODUk_TCMn_FESESR
Description
ODUk TCMn section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Determine the cause and solve the problem
in a timely manner, thus to ensure the signal transmission quality.


During a far end severely errored second, there is at least one defect or 30% of data blocks are
error blocks. FESESR refers to the ratio of the FESES count in a certain period to the total
available time.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_SESR.
----End
Related Information
None
6.70 ODUk_TCMn_FEUAS
Description
ODUk TCMn section unavailable second
Impact on System
The far-end services are not available.

Unavailable seconds are generated when the number of bit errors at the far end is large.
Related Alarms
ODUk_TCMn_BDI ODU TCMn backward defect indication.
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_BDI.
----End
Related Information
None

6.71 ODUk_TCMn_IAES
Description
ODUk TCMn section introducing alignment errored second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.

There is the OTUk_OOF or OTUk_LOF alarm at the upstream station.
Related Alarms
OTUk_LOF OTUk frame loss. The upstream station detects the LOF alarm and
then inserts IAE. The local station reports ODU1_TCMn_IAES.
Procedure
Step 1 Refer to the method of handling the OTUk_LOF.
----End
Related Information
None
6.72 ODUk_TCMn_SES
Description
ODUk TCMn section severely errored second
Impact on System

It is obtained by calculating the BIP-8 of ODUk TCMn section. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks. The fiber line may be faulty.

Related Alarms
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.73 ODUk_TCMn_SESR
Description
ODUk TCMn section ratio of severely errored second
Impact on System

It is obtained by calculating the BIP-8 of ODU1 TCMn section. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks. The consecutive severely
errored second means the severely errored second appears consecutively. SESR refers to the
ratio of the SES count in a specified period to the total available time.
Related Alarms
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End

Related Information
None
6.74 ODUk_TCMn_UAS
Description
ODUk TCMn section unavailable second
Impact on System

available.
Related Alarms
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC
----End
Related Information
None
6.75 OSPICCV
Description
The OSPICCV indicates the value of the cooling current of the laser.
It includes:

l OSPICCVMAX: stands for the maximum value during a period of time.

l OSPICCVMIN: stands for the minimum value during a period of time.
l OSPICCVCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the cooling current of
the laser is excessively high or low, however, the laser may work abnormally. If the cooling
current is within the normal range, you do not need to take any action.

l The performance event records the current value of the cooling current.
l The cooling current is applied to control the temperature of the optical module. In the case
of excessively low temperature, the cooling current is increased to make the temperature
higher. In the case of excessively high temperature, the cooling current is decreased to make
the temperature lower.
Related Alarms
LSR_COOL_ALM When the cooling current of the laser is beyond the specified range,
this alarm is generated.
Procedure
Step 1 Refer to the method of handling the LSR_COOL_ALM alarm.
----End
Related Information
None
6.76 OSPITMP
Performance Event Meaning
The OSPITMP indicates the value of the temperature in the tube core of the laser.
It includes:
l OSPITMPMAX: stands for the maximum value during a period of time.

l OSPITMPMIN: stands for the minimum value during a period of time.
l OSPITMPCUR: stands for the current value.

Impact on System
The performance event does not affect the equipment and the system. If the temperature in the
tube core of the laser is excessively high or low; however, the laser may work abnormally. As
a result, the services may be interrupted. If the temperature is within the normal range, you do
not need to take any action.

The performance event is adopted to monitor the current temperature in the tube core of the
laser, and to know the current temperature of the laser.
Related Alarms
TEM_HA When the temperature of the laser is higher than the upper threshold,
TEM_LA When the temperature of the laser is less than the lower threshold,
Procedure
Step 1 Refer to the method of handling the TEM_HA and TEM_LA alarms.
----End
Related Information
None
6.77 OTU2SMBIP8
Description
OTU SM section BIP8
Impact on System
quality.

This performance event shows the number of errors that a board with an OTN interface detects
in section monitoring through the BIP8 check. In normal cases, it should be 0.

Related Alarms
SM_BIP8_OVER OTU SM section bit interleaved parity exceeds threshold. The alarm
is generated when the number of BIP8 bit errors of the SM section on
the optical channel data unit layer exceeds the threshold.
SM_BIP8_SD OTU SM section bit interleaved parity deterioration. The alarm is

generated when the number of BIP8 bit errors of the SM section on
the optical channel data unit layer exceeds the degraded threshold.
Procedure
Step 1 If any alarm is generated, use the method of the relevant alarm to clear it.
----End
Related Information
None
6.78 OTUk_BBE
Description
OTU background block error
Impact on System

OTU errors are detected by checking the received parity bits. The background block error means
there are one or more data blocks containing error bits during transmission.
Related Alarms
OTUk_EXC OTU SM section bit interleaved parity exceeds threshold. The alarm

OTUk_DEG OTU SM section bit interleaved parity deterioration. The alarm is

generated when the number of BIP8 bit errors of the SM section in
Procedure
Step 1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.79 OTUk_BBER
Description
OTU ratio of background block error
Impact on System

OTU section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the OTU section refers to the ratio of the number
of background block errors of the OTU section to the number of all blocks minus the number
of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks
per second].
Related Alarms
is generated when the number of BIP8 bit errors of the SM section in


Procedure
----End
Related Information
None
6.80 OTUk_ES
Description
OTU errored second
Impact on System
quality.

OTU error is detected by checking the received parity bit. An errored second contains more than
one error block.
Related Alarms

Procedure
----End
Related Information
None

6.81 OTUk_FEBBE
Description
OTU SM section far end background block error
Impact on System
quality.

OTU SM section error is detected by checking the received parity bit. The background block
error means there are one or more data blocks containing error bit during transmission. And the
far end background block error refers to the background block error detected at the opposite end.
Related Alarms
OTUk_BDI OTU SM section backward defect indication.
Procedure
Step 1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.82 OTUk_FEBBER
Description
OTU SM section ratio of far end background block error
Impact on System


OTU SM section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the OTU SM section refers to the ratio of the
number of background block errors of the OTU SM section to the number of all blocks minus
cSES) x blocks per second]. And the ratio of far end background block error refers to the ratio
of background block error detected at the opposite end.
Related Alarms
Procedure
----End
Related Information
None
6.83 OTUk_FEES
Description
OTU SM section far end errored second
Impact on System

OTU SM section error is detected by checking the received parity bit. An errored second contains

Related Alarms
Procedure
----End
Related Information
None
6.84 OTUk_FESES
Description
OTU SM section far end severely errored second
Impact on System
in a timely manner because the bit errors have affected the signal transmission quality.

OTU SM Section error is detected by checking the received parity bit. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. The consecutive
severely errored second means the severely errored second appears consecutively, it might result
in the interruption of the service that shares a fiber link with the supervisory channel. And the
far end severely errored second refers to the severely errored second detected at the opposite
end.
Related Alarms
Procedure
----End

Related Information
None
6.85 OTUk_FESESR
Description
OTU SM section ratio of far end severely errored second
Impact on System

ratio refers to the ratio of SES count in a certain period of time to the total available time. Far
end severely errored second ratio refers to the ratio of errored seconds that are detected at the
far end.
Related Alarms
Procedure
----End
Related Information
None
6.86 OTUk_FEUAS
Description
OTU SM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.


available. And the far end unavailable second refers to the unavailable second detected at the
opposite end.
Related Alarms
Procedure
----End
Related Information
None
6.87 OTUk_SES
Description
OTU severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem

Error is detected by checking the received parity bit. During a severely errored second, there is
at least one defect or 30% of data blocks are error blocks. The consecutive severely errored
second means the severely errored second appears consecutively, it might result in the
interruption of the service that shares a fiber link with the supervisory channel.

Related Alarms

Procedure
----End
Related Information
None
6.88 OTUk_SESR
Description
OTU ratio of severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem

there is at least one defect or 30% of data blocks are error blocks. The consecutive severely
errored second means the severely errored second appears consecutively, it might result in the
interruption of the service that shares a fiber link with the supervisory channel. Severely errored
second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available
time.
Related Alarms


Procedure
----End
Related Information
None
6.89 OTUk_UAS
Description
OTU unavailable second
Impact on System

available.
Related Alarms


Procedure
----End
Related Information
None
6.90 PCLSOP
Description
Per-channel laser output power, indicating the optical power of a channel of signal monitored
by the spectrum analyzer unit.
It includes:
l PCLSOPMAX: stands for the maximum value during a period of time.

l PCLSOPMIN: stands for the minimum value during a period of time.
l PCLSOPCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signal to check
its optical power.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None

6.91 PCLSSN
Description
Per-channel OSNR, indicating OSNR of a channel of signal monitored by the spectrum analyzer
unit.
It includes:
l PCLSSNMAX: stands for the maximum value during a period of time.

l PCLSSNMIN: stands for the minimum value during a period of time.
l PCLSSNCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and checks and calculates the OSNR
of a channel of signal.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.92 PCLSWL
Description
Per-channel central wavelength, indicating the central wavelength of a channel among optical
signals monitored by the spectrum analyzer unit.
It includes:
l PCLSWLMAX: stands for the maximum value during a period of time.

l PCLSWLMIN: stands for the minimum value during a period of time.
l PCLSWLCUR: stands for the current value.

Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signal to check
its central wavelength.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.93 PCLSWLO
Description
Per-channel central wavelength deviation indicates the deviation between the ITU-T standard
wavelength and the wavelength of a channel among optical signals monitored by the spectrum
analyzer unit.
It includes:
l PCLSWLOMAX: stands for the maximum value during a period of time.

l PCLSWLOMIN: stands for the minimum value during a period of time.
l PCLSWLOCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and checks and calculates the central
wavelength deviation of a channel of signal.
Related Alarms
None

Procedure
Step 1 None
----End
Related Information
None
6.94 RPL
Description
The RPL indicates the value of the input optical power.
It includes:
l RPLMAX: stands for the maximum value during a period of time.

l RPLMIN: stands for the minimum value during a period of time.
l RPLCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the input optical power
is excessively high, the laser may be damaged. If the input optical power is excessively low, the
laser may fail to detect the signals. You can know the normal range of the input optical power
by querying the specifications for related optical interfaces.

The performance event is adopted to monitor the value of the input optical power of the laser,
and to know the value of the input optical power.
Related Alarms
IN_PWR_LOW The alarm is generated when the input optical power is lower than
the lower threshold of the input optical power.
IN_PWR_HIGH The alarm is generated when the input optical power is higher than
the upper threshold of the input optical power.
Procedure
----End

Related Information
None
6.95 RSBBE
Description
RS background block error
Impact on System

The regenerator section errors are detected by checking the B1 byte. The background block error
means there are one or more data blocks containing error bits during transmission.
Related Alarms
B1_EXC Regenerator section (B1) excessive errors.

The alarm is generated when the received
signals in SDH frame degrades and the B1 bit
errors in the multiplex section exceeds the
threshold.
B1_SD Regenerator section (B1) excessive errors.

signals in SDH frame degrades and the B1 bit
errors in the multiplex section exceeds the
signal degrade (SD) threshold.
Procedure
Step 1 Refer to the method of handling the B1_EXC and B1_SD.
----End
Related Information
None

6.96 RSCSES
Description
RS consecutive severely errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. Consecutive severely
errored seconds (CSES) mean the severely errored seconds appear consecutively, and the CSES
is generally accompanied by the B1_EXC alarm. It might result in service interruption.
Related Alarms

signals in SDH frame degrade and the B1 bit
errors in the multiplex section exceed the
threshold.

Procedure
----End
Related Information
None

6.97 RSES
Description
Regenerator section (RS) errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. The RS errored second
means that there are more than one error block transmitted in this second.
Related Alarms

threshold.

Procedure
----End
Related Information
None

6.98 RSOFS
Description
RS out-of-frame second
Impact on System
This alarm indicates that the frame headers cannot be identified in five or more consecutive
frames in the received signals of the line board. The board enters the out-of-frame state. As a
result, the services are unavailable. If the out-of-frame state lasts for 3 ms, the board enters the
loss-of-frame state and the R_LOF alarm is generated.

Out-of-frame (OOF) refers to the loss of framing bytes and the OOF second contains at least
one OOF.
OOF turns to be loss of frame (LOF) if it lasts more than 3 ms.
Related Alarms
R_OOF Out of frame on receiving line. This alarm is

generated when the headers of consecutive
five frames fail to be detected.
R_LOF Loss of frame on receiving line. This alarm is

generated when the frame alignment
processing is in the OOF state in consecutive
3 ms.
Procedure
Step 1 Check whether the fibers are damaged and whether the connectors are properly installed. Clean
the fiber connectors.
Step 2 Check whether the input optical power of the input interface of the board is within the normal
range by using an optical power meter. For the optical power specifications of a certain board,
see the Product Description. If the power is not within the normal range, add proper attenuation
by adding a fix attenuator or a variable optical attenuator (VOA).
----End
Related Information
None

6.99 RSOOF
Description
The RSOOF indicates the count of out-of-frame events in the regenerator section.
Impact on System
When the performance event occurs, the frame alignment bytes are lost. As a result, the services
are interrupted.

The out-of-frame event means that the frame alignment bytes are lost. The RSOOF means that
one or more out-of-frame events occur during transmission. The possible causes of the event are
as follows:
l The performance of the optical fiber is degraded.
Related Alarms
R_OOF If more than five consecutive frames cannot be correctly aligned with
the SDH frame header, the alarm is reported.
R_LOF When the R_OOF alarm lasts for 3 ms, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the R_OOF and R_LOF.
----End
Related Information
None
6.100 RSSES
Description
RS severely errored second

Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored
second, there is at least one defect or 30% of blocks are error blocks.
Related Alarms

threshold.

Procedure
----End
Related Information
None
6.101 RSUAS
Description
RS unavailable second
Impact on System


The regenerator section errors are detected by checking the B1 byte. If the severely errored
seconds last for more than 10 seconds, the unavailable second starts from the beginning of the
11th second, and the former 10 severely errored seconds are counted as unavailable. If the
severely errored second disappears for more than 10 seconds, the available time starts from the
beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms

threshold.

Procedure
----End
Related Information
None
6.102 SUMIOP
Description
Total input optical power
It includes:
l SUMIOPMAX: stands for the maximum value during a period of time.
l SUMIOPMIN: stands for the minimum value during a period of time.
l SUMIOPCUR: stands for the current value.
Impact on System
If the total input optical power is excessively high, the optical modules of the local board and
the downstream board may be damaged. As a result, bit errors are generated in the services or

even the services are interrupted. If the total input optical power is excessively low, the single-
wavelength optical signals that are output by the board may be lost. As a result, bit errors are
generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate
the result with software for conversion.
SUMIOP is the total input optical power of demultiplexer and the optical amplifier board.
Related Alarms
IN_PWR_HIGH It is generated when the input optical power is higher than the upper
threshold. Inaccurate optical power detection or faulty optical module
can cause the input optical power higher than the upper threshold.
IN_PWR_LOW It is generated when the optical power input by board is lower than
the lower threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power lower than the lower
threshold.
SUM_INPWR_HI It is generated when the detected total input optical power is higher
than the upper threshold.
SUM_INPWR_LO It is generated when the detected total input optical power is lower
W than the lower threshold.
Procedure
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH or
SUM_INPWR_HI alarm.
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW or
SUM_INPWR_LOW alarm.
----End
Related Information
The board types that are supported by the input power alarm are different from the board types
that are supported by the total input power alarm.

6.103 SUMOOP
Description
Total output optical power
It includes:
l SUMOOPMAX: stands for the maximum value during a period of time.

l SUMOOPMIN: stands for the minimum value during a period of time.
l SUMOOPCUR: stands for the current value.
Impact on System
The total output power brings impact on the services. If the total output power is excessively
high, the input optical power of the downstream board may be excessively high. As a result, bit
errors are generated in the services or even the services are interrupted. In addition, the receiver
module of the OTU at the downstream station may be damaged. If the total output power is
excessively low, the input optical power of the downstream board may be excessively low. As
a result, bit errors are generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate
the result with software for conversion.
SUMOOP is the total optical power output by the multiplexer and the optical amplifier board.
In a multiplexer unit, the input signals pass the multiplexer and then output the total optical
power through the "OUT" port, while on an amplifier board, the input signals pass the amplifier
and then output the total optical power through the "OUT" port.
Related Alarms
OUT_PWR_HIGH It is generated when the optical power output by board is higher than
the upper threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power higher than the upper
threshold.
OUT_PWR_LOW It is generated when the optical power output by board is lower than
the lower threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power lower than the lower
threshold.

Procedure
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm.
----End
Related Information
The board types that are supported by the output power alarm are different from the board types
that are supported by the total output power alarm.
6.104 TLB
Description
The TLB indicates the value of the bias current of the laser.
It includes:
l TLBMAX: stands for the maximum value during a period of time.

l TLBMIN: stands for the minimum value during a period of time.
l TLBCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the bias current of the
laser is beyond the normal range, however, the laser fails to work or is going to the end of its
life. As a result, the services are interrupted. If the bias current is within the normal range, you
do not need to take any action.

The performance event is adopted to monitor the bias of the laser, and to know the value of the
bias current of the laser.
Related Alarms
TF When the bias current of the laser is beyond the normal range, the
alarm is reported, showing transmission failure of the laser.

LSR_WILL_DIE When the bias current of the laser is less than the TF value, the alarm
is reported, indicating that the life of the laser is going to the end.
Procedure
----End
Related Information
None
6.105 TPL
Description
The TPL indicates the value of the output optical power.
It includes:
l TPLMAX: stands for the maximum value during a period of time.

l TPLMIN: stands for the minimum value during a period of time.
l TPLCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the output optical power
of the laser is beyond the normal range, however, the laser fails to work or is going to the end
of its life. As a result, the services are interrupted. If the output optical power is within the normal
range, you do not need to take any action.

The performance event is adopted to monitor the value of the output optical power of the laser,
and to know the current value of the output optical power.
Related Alarms
TF When the output optical power is beyond the normal range and this
causes transmission failure of the laser, the alarm is reported.

LSR_WILL_DIE When the output optical power is greatly beyond the normal range,
the alarm is reported, indicating that the life of the laser is going to
the end.
Procedure
----End
Related Information
None
6.106 VC3BBE

The VC3BBE is a performance event indicating the VC-3 background block error.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner
to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the
B3 bit error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
VC3BBE indicates bit errors detected in a verification and excluding the higher order path
unavailable time and higher order path severely errored second.
External causes:
l The fiber performance is degraded, and the attenuation of the fiber is excessively high.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
Equipment problems:
l The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end is
faulty.

l The synchronization performance of the clock is poor.

l The cross-connect unit and the service board do not work with each other properly.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
B3_EXC_VC3 B3 bit errors exceeds the threshold
B3_SD_VC3 Signals degraded (B3)
Procedure
Step 1 Eliminate external causes. For example, the grounding is improper or the operating temperature
is high. The receive optical power of the service board is excessively low or high. In this case,
ground the equipment properly or provide a proper operating environment for the equipment.
For more information about solving the optical power problem, see the 6.94 RPL performance.
Then, check whether bit errors occur on the service boards.
Step 2 If all the service boards of an NE have bit errors, the clock unit might be faulty. In this case,
replace the clock unit.
Step 3 If only a service board reports that bit errors exist, it indicates that the local service board might
be faulty or that the opposite NE or fibers are faulty. Locate the faulty board by using the loopback
method. Then, replace the faulty board.
----End
Reference
None.
6.107 VC3CSES

The VC3CSES is a performance event indicating the VC-3 continuous severely errored second.

B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD alarms
will be generated.

Possible Causes
When a consecutive VC3CSES sequence is detected, the VC3CSES performance event occurs.
When unavailable time comes or VC3CSES is absent in one second, the VC3CSES sequence
ends.
External causes:
Equipment problems:
faulty.
Relevant Alarms
B3_EXC_VC3 B3 bit errors exceed the threshold.
B3_SD_VC3 Signals degraded (B3).
R_LOS The signal on the receive line side is lost.
R_LOF The out-of-frame fault occurs on the receiver line side.
MS_AIS Multiplex section alarm indication.
AU_AIS AU alarm indication.
AU_LOP AU pointer loss.
LP_UNEQ_VC3 VC-3 path unequipped.
Procedure
Step 1 Refer to the 6.108 VC3ES.
----End

Reference
None.
6.108 VC3ES

The VC3ES is a performance event indicating VC-3 errored second.

B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD alarms
will be generated.
Possible Causes
The VC3ES performance event occurs when one or multiple bit error blocks are detected in one
second or, when the R_LOS, R_LOF, and MS_AIS alarms are detected on the optical interface,
or when the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected over the path.
External causes:
Equipment problems:
faulty.
Relevant Alarms

R_LOS The signal on the receiver line side is lost.
R_LOF The out-of-frame fault occurs on the receive line side.
Procedure
Step 1 If the R_LOS/R_LOF alarm is generated, a fiber cut, high attenuation, received overload or
faulty board might exist.
1. If the receive optical power is overloaded, add an attenuator.
2. Check whether the optical fiber cables are intact and whether the connectors are clean and
properly connected. Replace the fibers or clean the fiber connectors, if necessary.
3. If the board is faulty, replace the board.
Step 2 If the MS_AIS alarm is generated:

1. Check whether the service board at the opposite station is configured with insertion of the
MS_AIS alarm. If yes, cancel the configuration.
2. Check whether the transmit unit of the service board at the opposite station is faulty. Check
whether the service board reports the MS_AIS alarm by performing self-loop on the fibers.
3. Check the service board of the local station. Reset or replace the board. Then, check whether
the MS_AIS alarm is cleared.
Step 3 If the AU_AIS alarm is generated:

1. For the AU_AIS alarm caused by MS_AIS, R_LOS, and R_LOF, analyze the MS_AIS,
R_LOS, and R_LOF alarms to locate the fault.
whether the service board reports the AU_AIS alarm by performing self-loop on the fibers.
If the service board is faulty, reset or replace the board. Then, check whether the AU_AIS
alarm is cleared.
3. If the service unit of the local station is faulty, replace the SCC board at the local station.
Step 4 If the AU_LOP alarm is generated:

1. Check whether the service configuration is correct at the local and opposite stations. If not,
reconfigure the service.
2. Check whether the opposite clock board works normally and whether the cross-connect
unit detects the clock. If the clock board works abnormally, modify the clock configuration
and issue it again.
whether the service board reports the AS_AIS alarm by performing self-loop on the fibers.

If the service board is faulty, reset or replace the board. Then, check whether the AU_AIS
alarm is cleared.
4. If the service unit of the local station is faulty, replace the SCC board at the local station.
Step 5 If the LP_UNEQ_VC3 alarm is generated:

1. Check whether the C2 byte is correctly configured. If not, modify the configuration and
issue it again. If yes, the board is judged as faulty. In this case, replace the faulty board.
Step 6 Refer to the 6.106 VC3BBE.
----End
Reference
None.
6.109 VC3FEBBE

The VC3FEBBE is a performance event indicating the VC-3 far end background block error.

If bit errors occur in the services on a remote NE, determine the cause and solve the problem in
a timely manner to avoid any alarm, and thus to ensure the signal transmission quality.
Possible Causes
VC3FEBBE indicates the returned bit errors excluding the bit errors occurring in the VC3 far
end unavailable time and VC3 far end severely errored seconds.
External causes:
station.
Equipment problems:
l The signal attenuation at the receive side of the service board at the opposite station is

opposite station.
l The fan of the opposite equipment becomes faulty.
Relevant Alarms
LP_RDI_VC3 VC-3 path remote defect indication
Procedure
Step 1 Refer to the 6.106 VC3BBE to handle the NE at the opposite end.
----End
Reference
None.
6.110 VC3FECSES

The VC3FECSES is a performance event indicating the VC-3 far end consecutive severely
errored second.

Possible Causes
When a consecutive VC3FECSES sequence is detected, the VC3FECSES performance event
occurs. When unavailable time comes or VC3FECSES is absent in one second, the VC3FECSES
sequence ends.
External causes:
l The fiber performance degrades and the attenuation is excessive at the opposite station.

Equipment problems:
opposite station.
Relevant Alarms
Procedure
Step 1 Refer to the 6.111 VC3FEES.
----End
Reference
None.
6.111 VC3FEES

The VC3FEES is a performance event indicating the VC-3 far end errored second.

Possible Causes
The VC3FEES performance event occurs when one or multiple bit errors are returned by the G1
byte in one second or when the LP_RDI_VC3 alarm is detected on the path.
External causes:
station.


Equipment problems:
opposite station.
Relevant Alarms
Procedure
Step 1 If the LP_RDI_VC3 alarm is generated:
1. Check whether the service board of the opposite station receives an alarm such as
TU_AIS_VC3, TU_LOP_VC3 and LP_UNEQ_VC3. If yes, first clear the alarm.
2. If the service board of the opposite station does not receive an alarm such as TU_AIS_VC3,
TU_LOP_VC3 and LP_UNEQ_VC3, or if the local station still reports the LP_RDI_VC3
alarm after the opposite station ends this kind of alarm, check whether the opposite station
or the local station is faulty by looping back the fibers.
3. If the receive unit of the opposite station is faulty, replace the relevant board.
4. If the transmit part of the local station is faulty, replace the SCC board.
Step 2 Refer to the 6.109 VC3FEBBE.
----End
Reference
None.
6.112 VC3FESES


The VC3FESES is a performance event indicating the VC-3 far end severely errored second.

Possible Causes
The VC3FESES performance event occurs when not less than 30% bit errors are contained in
the message returned in one second or at least one severely disturbed period (SDP) occurs. SDP
occurs when the BER of all the continuous blocks in a period of at least four continuous blocks
or 1 ms (select the longer period) is lower than 10-2, or when the LP_RDI_VC3 alarm is
generated.
External causes:
station.
Equipment problems:
opposite station.
Relevant Alarms
Procedure
----End

Reference
None.
6.113 VC3FEUAS

The VC3FEUAS is a performance event indicating the VC-3 far end unavailable second.

Possible Causes
VC3FEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
station.
Equipment problems:
opposite station.
Relevant Alarms

Procedure
----End
Reference
None
6.114 VC3SES

The VC3SES is a performance event indicating the VC-3 far end severely errored second.

B3 bit error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
The VC3SES performance event occurs when not less than 30% bit errors are detected in one
second or at least one severely disturbed period (SDP) occurs. The SDP indicates that the BER
of all the consecutive blocks is not lower than 10-2 or the R_LOS, R_LOF and MS_AIS alarms
are generated in a period of at least four consecutive blocks or i ms (the longer one is selected),
or the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected on the path.
External causes:
Equipment problems:
faulty.

Relevant Alarms
Procedure
----End
Reference
None.
6.115 VC3UAS

The VC3UAS is a performance event indicating the VC-3 unavailable second.

B3 bit error threshold and degrade threshold, the B3_EXC_VC3 and B3_SD_VC3 alarms will
be generated.
Possible Causes
VC3UAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:


Equipment problems:
faulty.
Relevant Alarms
Procedure
----End
Reference
None
6.116 WCV
Description
Pump laser working current, also called pump laser driver current or pump laser bias current.
It includes:

l WCVMAX: stands for the maximum value during a period of time (in 1mA).
l WCVMIN: stands for the minimum value during a period of time (in 1mA).
l WCVCUR: stands for the current value (in 1mA).
Impact on System
When the pump laser works normally, there is no impact on the services. If an alarm is generated,
determine the cause.

WCV indicates the pump laser driver current of an optical amplifier board. The optical amplifier
board amplifies the input signal using the pump laser driven by pump laser working current.
Related Alarms
PUM_BCM_ALM The board reports this alarm when the detected pump laser driver
current is higher than the threshold due to laser exceptions caused by
laser aging, or over-high/low ambient temperature.
LSR_WILL_DIE The board reports this alarm when the pump laser driver current is
higher than the termination threshold due to laser aging.
TD Transmitter degrade alarm. The alarm is generated when the bias

current of the laser exceeds the degrade threshold.
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the handling procedure of the alarm.
Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
Step 3 If the TD alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.117 XCSTMP
Description
Board environmental temperature
It includes:

l XCSTMPMAX: stands for the maximum value during a period of time.

l XCSTMPMIN: stands for the minimum value during a period of time.
l XCSTMPCUR: stands for the current value.
Impact on System
Excessively high or low board temperature might cause faults such as degradation of the board
working performance and bit errors.

This performance event is generated by hardware detecting to show the ambient temperature of
the board.
When the ambient temperature is abnormal, or when the heat-sinking and ventilation measures
are improper, the XCSTEMP event occurs.
Related Alarms
TEMP_OVER It is generated when the ambient temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the proper handling procedures.
----End
Related Information
None

Alarms and Performance Events Reference 7 Event List
7 Event List
This section list the common events.
Table 7-1 Events regarding APE and EAPE
Name Level Description
APE adjust finished Warning APE adjustment starts upon an APE

adjustment start command. When the
adjustment is complete, an APE adjust
finished is reported.
APE adjust failed Critical When APE adjustment is terminated upon an

APE adjustment stop command issued by the
user or due to other causes, an APE adjust
failed event is reported.
EAPE adjustment result Major When EAPE adjustment is complete, an EAPE

notification event adjustment result notification event is reported
to indicate whether the adjustment is
successful.
EAPE abnormal notification Major When EAPE adjustment becomes abnormal,

event an EAPE abnormal notification event is
reported.
Table 7-2 Events regarding IPA
IPA abnormal event Major When IPA adjustment is terminated due to a

fault of the laser, an IPA abnormal event is
reported.

Table 7-3 Events regarding ROADM
ROADM wave conflict event Critical If a passthrough wavelength conflicts with an

add wavelength of the OTU after a wavelength
resource consistency check is started, an
ROADM wavelength conflict event is
reported.
ROADM wave check event Critical When the system starts a wavelength resource
consistency check, an ROADM wave check
event is reported.
ROADM wave reconfig event Critical When actions such as setting wavelength
blocking and deleting intra-board optical
cross-connections are performed, an ROADM
wave reconfig event is reported.
ROADM power adjust event Critical When the optical power equalization
adjustment at an ROADM node is started, an
ROADM power adjust event is reported.
ROADM wave state change Critical After a wavelength resource consistency

event check at an ROADM node is started, the logic
wavelength group of the node is in an idle or
abnormal state. That is, if the node passes the
check, the group returns the idle state; if the
node fails the check, the group enters into the
abnormal state. If the status of the logic
wavelength group changes, an ROADM wave
state change event is reported.
Table 7-4 Events regarding protection
OWSP abnormal event Major This event is reported when the optical
wavelength shared protection switching
occurs.
ODUk SPRing abnormal event Major This event is reported when an ODUk SPRing
protection switching occurs.
1+1 equipment-level Critical This event is reported when a protection

protection switching event switching occurs on a cross-connect board or
on the system control and communication
(SCC) board.

Table 7-5 Other events
RMON performance value is Minor This event is automatically reported when the
above the upper limit performance value in the sampling period is
higher than the upper threshold.
RMON module performance Minor In the sampling period, a event indicating

value is lower than the lower upper threshold crossing occurs. In a new
threshold sampling period, when the sampling value is
less than or is equal to the lower threshold
value, this event is reported.

Alarms and Performance Events Reference 8 Event Processing
8 Event Processing
About This Chapter
This chapter describes information relevant to event handling, including event descriptions,
event attribute, event parameters, impacts of events on the system, event causes, and event
NOTE
In the case of an event, see its handling procedure to clear it; if this event persists, contact a technical
engineer of Huawei for troubleshooting.
When you view an event on the network management system, select the event. The Detail
Description in the Event Details field displays the related parameters of the event.
8.1 EAPE Abnormal Event Notification
8.2 EAPE Adjustment Result Event Notification
8.3 OWSP Abnormal Event
8.4 ODUk SPRing Abnormal Event
8.5 RMON Performance Value Is Above the Upper Threshold
8.6 RMON Module Performance Value Is Lower than the Lower Threshold
8.7 1+1 Equipment Level Protection Switching Event Report

8.1 EAPE Abnormal Event Notification

Description
An event indicating that the EAPE meets the conditions for adjustment. This event indicates that
the current status of the system allows for EAPE adjustment.
Attribute
Event Severity Event Type
Major Equipment
Parameter
Parameter 1 Indicates the configuration index number for the

EAPE pair, such as 1.
Parameter 2 Indicates the current pre-correction BER of the

sink OTU.
Parameter 3 Indicates the current input optical power of the

sink OTU (in the unit of 0.1 dBm).
Parameter 4 Indicates the BIP8 bit error status in the SM

section for the sink OTU. When this event is
reported, only the Normal status is present,
indicating that the current bit error is zero.
Impact on System
When this event occurs, the EAPE pair of the system meets the conditions for adjustment. In
this case, starting the adjustment does not affect the services.
Possible Causes
Cause 1: The system is configured with an EAPE pair and the EAPE pair meets the conditions
for adjustment. That is, the input optical power does not exceed the threshold, the BIP8 bit error
in the SM section is zero, or the pre-correction BER degrades.
Procedure
l Cause 1: The system is configured with an EAPE pair and the EAPE pair meets the
conditions for adjustment.

1. On the U2000, start the EAPE automatic adjustment. For details, see the Feature
Description.
----End
Related Information
None
8.2 EAPE Adjustment Result Event Notification

Description
An event indicating the end of the EAPE adjustment. When the EAPE adjustment is complete,
the adjustment result event is reported, indicating whether the adjustment is successful.
Attribute
Major Equipment
Parameter
Parameter 1 Indicates the configuration index number for the

EAPE pair, such as 1.

Parameter 2 Indicates the cause for the end of the adjustment.

The values of the parameter are as follows:
succeed
manual adjust
no balance after adjusting
communication failed
board uninstalled
board type error
board offline
vmux carry error
board response error
system error
adjust ne not found
choice ne not found
condition not meet
choice board not found
no reason
Parameter 3 Indicates the ID of the NE where the adjustment

is successful or fails.
Parameter 4 Indicates the slot number of the board where the

adjustment is successful or fails.
Parameter 5 Indicates the number of the optical interface where

the adjustment is successful or fails.
Parameter 6 Indicates the number of the channel where the

adjustment is successful or fails.
Impact on System
If an adjustment success is reported, the system BER is lowered and the signal transmission
quality is improved.
If an adjustment failure is reported, the signal transmission quality needs to be improved.
Possible Causes
l Cause 1: The adjustment is successful.
l Cause 2: The user manually issues a command to stop the adjustment.
l Cause 3: After the adjustment is performed for six times, the pre-correction BER of the
sink OTU does not reach the expected value.

l Cause 4: The inter-NE communication fails.

l Cause 5: The logical board is not installed.
l Cause 6: The board type is incorrect.
l Cause 7: The board is not in position.
l Cause 8: The attenuation of the board with attenuator is adjusted to the extreme.
l Cause 9: The board incorrectly responds to the command.
l Cause 10: The system has an error, for example, the operation on the database fails.
l Cause 11: The address of the NE where the adjustment is to be performed cannot be found.
l Cause 12: The address of the NE where signals are selectively received cannot be found.
l Cause 13: The EAPE pair does not meet the conditions for starting the adjustment. The
start-up conditions are as follows:
– The input optical power does not exceed the threshold.
– The BIP8 value in the SM section is zero.
– The pre-correction BER degrades.
l Cause 14: The board that selectively receives signals is in an incorrect state.
l Cause 15: Other causes.
Procedure
l Cause 1: The adjustment is successful.
1. Ignore the event.
l Cause 2: The user manually issues a command to stop the adjustment.
l Cause 3: After the adjustment is performed for six times, the pre-correction BER of the
sink OTU does not reach the expected value.
1. Check whether the pre-correction BER of the sink OTU is lowered.
2. If yes, proceed with the adjustment.
3. If the BER is not lowered, the EAPE function does not meet the requirements of the
system. In this case, see section "Rectifying Bit Errorsin" in the Troubleshooting to
handle the BER.
l Cause 4: The inter-NE communication fails.
1. On the U2000, check whether NEs involved in the EAPE pair normally communicate
with each other. For specific operations, see the OptiX iManager U2000 Operation
Guide (WDM).
l Causes 5–7: The logical board is not installed, or the board type is incorrect, the board is
not in position.
1. Find the board according to the NE ID and slot number indicated by event parameters
and then install the board or replace the board with one of the correct types.
l Cause 8: The attenuation of the board with attenuator is adjusted to the extreme.
1. Check whether the attenuation of the board is adjusted to the extreme according to the
NE ID, slot number, optical interface number, and channel number indicated by the
event parameters. If yes, the system cannot continue the EAPE adjustment. In this

case, check whether the optical power of signals is normal. For specifications, see the
Product Description.
l Cause 9: The board incorrectly responds to the command.
1. Find out the board according to the NE ID and slot number indicated by event
parameters and query alarms related to the board. Handle the alarms according to the
Handling Procedure parts for respective alarms.
l Cause 10 or Cause 15: The system has an error, or other causes.
1. Reconfigure the EAPE and start another EAPE adjustment. For details, see the Feature
Description.
l Cause 11 or Cause 12: The address of the NE where the adjustment is to be performed
cannot be found, or the address of the NE where signals are selectively received cannot be
found.
1. Check the network connection between the NEs, and ensure the connection between
the NEs is correct.
2. On the U2000, check for the configuration information about the EAPE pair. If there
is no configuration information about the EAPE pair, reconfigure the EAPE pair.
l Cause 13: The EAPE pair does not meet the conditions for starting the adjustment.
1. Check whether the parameters such as the input optical power and performance of the
sink board meet the conditions for adjustment. If not, the system cannot perform the
EAPE adjustment.
l Cause 14: The board that selectively receives signals is in an incorrect state.
1. Check whether the board that selectively receiving signals is normal. Query alarms
related to this board and handle the alarms according to the Handling Procedure parts
for respective alarms.
----End
Related Information
None
8.3 OWSP Abnormal Event

Description
An event indicating the optical wavelength shared protection. When the optical wavelength
shared protection switching occurs, this event is reported.
Attribute
Major Communication

Parameter
Parameter 1 Indicates the ID of the protection group where the

Parameter 2 Indicates the status of the westbound working channel.

SF, SD, normal, unknown, unmonitored
Parameter 3 Indicates the status of the westbound protection channel.

Parameter 4 Indicates the status of the eastbound working channel. The

values of the parameter are as follows:
Parameter 5 Indicates the status of the eastbound protection channel.

Parameter 6 Indicates the switching request of the westbound channel.

no request
response request
exercise switching-ring
WTR-ring switching
manual switching-ring
SD ring switching-working SD protection OK
SD ring switching-working SD protection SD
protection SD
forced switching-ring
SF ring switching-working SF protection OK
SF ring switching-working SF protection SD
SF ring switching-working SD protection SF
SF ring switching-working SF protection SF
protection SF
locked
Parameter 7 Indicates the switching request of the eastbound channel.

The values of the parameter are the same as those of
Parameter 6.

Parameter 8 Indicates current page status. The values of the parameter

are as follows:
stopped
starting
idle
east switching
west switching
full pass-through
APS pass-through
Parameter 9 Indicates the indication of westbound remote and local

ends. The values of the parameter are as follows:
remote-end, near-end
Parameter 10 Indicates the indication of eastbound remote and local

ends. The values of the parameter are as follows:
remote-end, near-end
Impact on System
When the switching occurs in the wavelength shared protection group, the services in the system
are transiently interrupted. When this event is reported, it indicates that the service in the current
working channel of the protection group may be abnormal. In this case, find out and rectify the
fault.
Possible Causes
l Cause 1: The current working channel is abnormal.
l Cause 2: An external switching command is issued.
Procedure
l Cause 1: The current working channel is abnormal.
1. Find out the cause and rectify the fault according to the alarm information reported in
the current working channel. For details on the operation, see Alarm Processing parts
for respective alarms.
l Cause 2: An external switching command is issued.
----End
Related Information
None

8.4 ODUk SPRing Abnormal Event

Description
An event indicating the ODUk protection. When the switching occurs in the ODUk SPRing
protection group, the working channel is switched to the protection channel, or the protection
channel is switched to the working channel. In this case, this event, indicating that the switching
occurs in the protection group, is reported.
Attribute
Major Communication
Parameter
Parameter 1 Indicates the ID of the protection group where this event

occurs.
Parameter 2 Indicates the current status of the westbound working

channel. The values of the parameter are as follows:
Parameter 3 Indicates the current status of the westbound protection

channel. The values of the parameter are the same as those
of Parameter 2.
Parameter 4 Indicates the current status of the eastbound working

of Parameter 2.
Parameter 5 Indicates the current status of the eastbound protection

of Parameter 2.

Parameter 6 Indicates the current page of the protection group. The

values of the parameter are as follows:
stopped
starting
idle
east switching
west switching
full pass-through
APS pass-through
Parameter 7 Indicates the switching request of the westbound channel

of the protection group. The values of the parameter are
as follows:
no req
exercise sw
WTR-ring sw
manual sw
SD sw-work SD pro OK
SD sw-work SD pro SD
pro SD
forced sw
SF sw-work SF pro OK
SF sw-work SF pro SD
SF sw-work SD pro SF
SF sw-work SF pro SF
pro SF
locked
Parameter 8 Indicates the switching request of eastbound channel of

the protection group. The values of the parameter are the
same as those of Parameter 7.
Parameter 9 Indicates the westbound remote and local indication, and

indicates whether the local station is the initiating end of
the switching. The values of the parameter are as follows:
remote-local station as the responding end
near-local station as the initiating end
Parameter 10 Indicates the eastbound remote and local indication, and

indicates whether the local station is the initiating end of
the switching. The values of the parameter are as those of
Parameter 9.

Impact on System
When the switching occurs in the ODUk SPRing protection group, the service is transiently
interrupted.
After this event is reported, if the ODUk SPRing protection group is currently in the switching
page, it indicates that the service in the westbound working channel or eastbound working
channel in the ODUk SPRing protection group is abnormal. In this case, find out and rectify the
fault.
Possible Causes
l Cause 1: The user issues an external switching command, such as forced switching or
manual switching. Hence, in the ODUk SPRing protection group, the working channel in
a direction is switched to the protection channel in another direction, or the protection
channel in a direction is switched to the working channel in another direction. In this case,
this event is reported.
l Cause 2: When the service in the working channel of the ODUk SPRing protection group
is abnormal, the service is automatically switched to the protection channel. When the
service in the protection channel is abnormal, the service is automatically switched to the
working channel. Hence, this event is reported.
l Cause 3: If the service in the working channel of the ODUk SPRing is restored, after the
WTR time elapses, the service in the protection channel is automatically switched to the
working channel. Hence, this event is reported.
Procedure
l Cause 1 or Cause 3: The user issues an external switching command, or after the WTR time
elapses, the service in the protection channel is automatically switched to the working
channel.
l Cause 2: The service is automatically switched to the protection channel
1. On the U2000, query the related switching alarms. For details, see Handling Procedure
parts for respective alarms.
----End
Related Information
None
8.5 RMON Performance Value Is Above the Upper

Threshold
Description
An event indicating that the performance value of the RMON module exceeds the upper
threshold. When the performance value in the sampling period is higher than the upper threshold,
this event is automatically reported. For example, when the performance value of collisions
exceeds the upper threshold, the event is reported.

Attribute
Minor Communication
Parameter
Parameter 1 Indicates the slot ID, port number and channel number,
such as 1-LOG-2(ETHER):1.
Parameter 2 Indicates the performance event of threshold crossing.

Drop Events
FCS and Alignment Errors
Undersize Packets Received
Oversize Packets Received
Fragments
Jabbers
Collisions
Bad Octets Received
Bad Octets Transmitted
Alignment Errors
FCS Errors
Late Collisions
Excessive Collisions
Deferred Transmissions
Carrier Sense Errors
Drop Events at Transmission Direction
Parameter 3 Indicates the performance value.
Parameter 4 Indicates the higher threshold.
Impact on System
The quality of the Ethernet service is degraded, or even the services in the system are interrupted.
Possible Causes
l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits
the data packets.

l Cause 2: The working modes of the ports at the local and opposite ends mismatch.
l Cause 3: The optical line attenuation is excessively high or the receive optical power is
abnormal.
l Cause 4: The optical fiber is damaged or the fiber connector is untidy.
l Cause 5: The board that reports this alarm is faulty.
Procedure
l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits
the data packets.
1. Use the smartbits equipment to check whether bit errors occur in the data transmitted
at the client side. If bit errors occur, find out and rectify the fault of the client-side
equipment.
l Cause 2: The working modes of the ports at the local and opposite ends mismatch.
1. On the U2000, query whether the working modes of the ports at the two ends of the
equipment match. If the working modes mismatch, adjust the working modes of the
ports according to the actual situation.
l Cause 3: The optical line attenuation is excessively high or the receive optical power is
abnormal.
by using the U2000. For the optical power specifications of a specific board, see the
Product Description. If the optical power is not within the normal range, take measures
according to the handling method of the IN_PWR_HIGH or IN_PWR_LOW alarm.
l Cause 4: The optical fiber is damaged or the fiber connector is dirty.
1. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
l Cause 5: The board that reports this alarm is faulty.
1. If this event persists, replace the faulty board. For details on operations, see the Parts
Replacement.
----End
Related Information
None
8.6 RMON Module Performance Value Is Lower than the

Lower Threshold
Description
An event indicating that the RMON module performance value is lower than the lower threshold.
In the sampling period, an event indicating upper threshold crossing occurs. In a new sampling
period, when the sampling value is less than or equal to the lower threshold, and the reporting
mode is that this event is reported when the performance value is lower than the lower threshold
value, or that this event is reported when the performance value is higher than the upper threshold
or lower than the lower threshold, this event is reported.

Attribute
Minor Communication
Parameter
Parameter 1 Indicates the slot ID, port number and channel number,
such as 1-LOG-2(ETHER):1.
Parameter 2 Indicates the performance event of threshold crossing.

Drop Events
FCS and Alignment Errors
Undersize Packets Received
Oversize Packets Received
Fragments
Jabbers
Collisions
Bad Octets Received
Bad Octets Transmitted
Alignment Errors
FCS Errors
Late Collisions
Excessive Collisions
Deferred Transmissions
Carrier Sense Errors
Drop Events at Transmission Direction
Parameter 3 Indicates the performance value.
Parameter 4 Indicates the lower threshold.
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
l Ignore the event.
----End
Related Information
None
8.7 1+1 Equipment Level Protection Switching Event Report

Description
1+1 equipment level protection switching event report, when the board protection switching
occurs, this event is reported.
Attribute
Critical Equipment
Parameter
Parameter 1 Indicates the ID of the protection group where this

event occurs, The values of the parameter are as
follows:
The value 1 indicates that the cross-connect board
The value 2 indicates that the SCC board protection
switching occurs.
Parameter 2 Indicates the slot ID of the current working board,

such as 9.
Parameter 3 Indicates the slot ID of the current protection board,

such as 10.
Impact on System
When the cross-connect board protection switching occurs in the protection group, the service
may be transiently interrupted.

Possible Causes
l Cause 1: The user issues an external switching command, such as forced switching or
clearing. In this case, the working unit of the protection group is switched to the protection
unit, or the protection unit is switched to the working unit, and this event is reported.
l Cause 2: When one unit in the protection group is abnormal, the protection group is switched
to another unit. In this case, this event is reported.
Procedure
l Cause 1: The user issues an external switching command.
l Cause 2: When one unit in the protection group is abnormal, the protection group is switched
to another unit. In this case, this event is reported.
1. If this event persists, replace the faulty board. For details on operations, see Parts
Replacement.
----End
Related Information
None

Alarms and Performance Events Reference A Glossary
A Glossary
A
Auto negotiation The negotiation mode that is set on the communication equipment. When the auto
negotiation mode is enabled, the equipment sets its working mode and rate through
negotiation based on the mode and rate of the opposite equipment.
B
Bandwidth Information-carrying capacity of a communication channel. Analog bandwidth is the
range of signal frequencies that can be transmitted by a communication channel or
network.
Bit Error Rate The ratio of the errored bit count to the transmitted bit count in a certain period of time.
In the digital communication system, bit error rate is the ratio of the errored bit count to
the transmitted bit count in a typical period of time.
Broadcast The act of sending a frame addressed to all stations on the network.
C
Channel The trail on the channel layer.
Client Server A terminal device (computer or workstation) that sends instructions to the server and
displays the results through the user interface.
Clock tracing The method to keep the time on each node being synchronized with a clock source in a
network.
Concatenate A combination process. The process combines multiple virtual containers (VCs). Then,
the capacity of the combined VCs can used as the capacity of a single VC and the bit
sequence is complete.
Connection A "transport entity" which consists of an associated pair of "unidirectional connections"
capable of simultaneously transferring information in opposite directions between their
respective inputs and outputs.

D
DCM Dispersion Compensation Module. A module, which contains dispersion compensation
fibers to compensate for the positive dispersion of transmitting fiber.
E
EDFA An optical device that amplifies the optical signals. The device uses a short length of
optical fiber doped with the rare-earth element Erbium and the energey 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.
Ethernet A data link level protocol comprising the OSI model's bottom two layers. It is a broadcast
networking technology that can use several different physical media, including twisted
pair cable and coaxial cable. Ethernet usually uses CSMA/CD. TCP/IP is commonly
used with Ethernet networks.
F
Fiber jumper The fiber which is used to connect the subrack with the ODF, subrack or connect the
board interfaces.
Forward Error A data encoding technology. It is a method to control errors in communication. In this
Correction method, extra (redundant) bits are inserted into the data stream towards other equipment
to control errors. The equipment at the receive end can use these redundant bits to detect
errors and correct errors if possible.
Frame A cyclic set of consecutive time slots in which the relative position of each time slot can
be identified.
Full duplex Pertaining to both parties that can send and receive data at the same time on the
communication link.
G
Gain The ratio 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.
Grooming A process that multiplexes multiple channels of low-rate signals into one or several
channels of required signals.
L
Label A mark on a cable, a subrack, or a cabinet for identification.
Laser The device that generates the directional light covering a narrow range of wavelengths.
Laser light is more coherent than ordinary light. Semiconductor diode lasers are the used
light source in fiber-optic system.

M
Main Topology The default U2000 client interface, a basic component of the human-machine interactive
interface. The topology clearly shows the structure of the network, the alarms of different
NEs, subnets in the network, the communication status as well as the basic network
operation status. All topology management functions are accessed here.
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.
O
Opposite station/ The opposite station is a service-specific concept. As shown in Figure A-1, if station A
opposite station board is the local station, station C is the opposite station for service λ1 and station B is the
opposite station for service λ2. The opposite station board is specific to the transmitting
or receiving of a service. For service λ2, the board opposite to OTU5 is OTU2. For service
λ3, the board opposite to OTU6 is OTU4. Similarly, for service λ1, the board opposite
to OTU1 is OTU3.
Figure A-1 Service flow

Station B Station C
Station A
λ1 λ1
OTU1 O O O OTU3
O
A F F A A F F A
D I I D D I I D
λ2 M U U M M U U λ3
M
OTU2 OTU4
Clinet WDM WDM Client
side side side side
O O
T T
U U
5 6
λ2 λ3
Optical spectrum An instrument that scans the spectrum to record power, measures the value of loss
analyzer insertion and tests the performance of the wavelength and optical signal noise ratio
(OSNR) of each channel.
Optical switch A passive component possessing two or more ports which selectively transmits, redirects,
or blocks optical power in an optical fiber transmission line.
OSNR Optical Signal-to-Noise Ratio. Ratio of the optical power of the transmitted optical signal
to the noise on the received signal.
Overhead A message that is transmitted on the optical network layer and does not need to associate
with a specific connection. For example, such an auxiliary channel can be used as a
digital communication channel between management entities to transmit management
data.

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 it is supported.
Regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
Route The path a trail takes.
S1 byte The byte defined in ITU-T to transmit the network synchronization status information.
Timeslot Single timeslot on a E1 digital interface—that is, a 64-kbps, synchronous, full-duplex

data channel, typically used for a single voice connection.
Trail A type of transport entity, mainly engaged in transferring signal from the input of the
trail source to the output of the trail sink, and monitoring the integrality of the transferred
signal.
Upstream station/ For the station where signals are received, the station where signals are transmitted and
downstream station the station where signals just pass through are upstream stations. As shown in Figure
A-2, service λ1 traverses from station A, to station B, and finally to station C. Station A
and station B are upstream stations of station C. The service signals can be ECC signals,
GE signals, or orderwire signals.
Conversely, station B and station C are downstream stations for station A.
Figure A-2 Service flow

Station B Station C
Station A
λ1 λ1
OTU1 O O O OTU3
O
A F F A A F F A
D I I D D I I D
λ2 M U U M M U U λ3
M
OTU2 OTU4
Clinet WDM WDM Client
side side side side
O O
T T
U U
5 6
λ2 λ3

User The user of the U2000 client, and the user and password define the corresponding
authority of operation and management of the U2000.
W
Wander In telecommunication, wander are long-term random variations of the significant instants
of a digital signal from their ideal positions.

Alarms and Performance Events Reference B Acronyms and Abbreviations
B Acronyms and Abbreviations
AIS Alarm Indication Signal
API Access Point Identifiers
BDI Backward Defect Indication
BEI Backward Error Indication
BIP Bit Interleaved Parity
BITS Building Integrated Timing Supply System
CRC Cyclical Redundancy Check
DAPI Destination Access Point Identifier
DSP Digital Signal Processing
EDFA Erbium-Doped Fiber Amplifier

FEC Forward Error Correction
FPGA Field Programmable Gate Array
GE Gigabit Ethernet
HP Higher Order Path
HDB High Density Bipolar Code
HPI Higher Order Path Interface
IAE Incoming Alignment Error
LACP Link Aggregation Control Protocol
LOF Loss Of Frame
LOS Loss Of Signal
MFAS MultiFrame Alignment Signal
MS Multiplex Section
OCI Open Connection Indication
ODU Optical Channel Data Unit
OOF Out Of Frame
OPU Optical Channel Payload Unit
OTN Optical Transmission Network

PIN Positive Intrinsic Negative
PM Path Monitoring
PT Payload Type
RDI Remote Defect Indication
REI Remote Error Indication
SAPI Source Access Point Identifiers
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SES Severely Errored Second
SF Signal Fail
SM Section Monitoring
TCM Tandem Connection Monitoring
TIM Trace Identifier Mismatch
TTI Trail Trace Identifier
UAS Unavailable Second


OptiX OSN 8800 Alarms and Performance Events Reference (V100R002)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OptiX OSN 8800 Alarms and Performance Events Reference (V100R002)

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX OSN 8800 Intelligent Optical Transport

Alarms and Performance Events

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2014-02-14) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX OSN 8800 V100R002C02

OptiX iManager T2000 V200R008C00

iManager U2000 V100R001C00

This document is intended for:

l System maintenance engineer

Indicates a hazard with a high level of risk, which if not

Issue 08 (2014-02-14) Huawei Proprietary and Confidential ii

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

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

Updates in Issue 08 (2014-02-14) Based on Product Version

Updates in Issue 07 (2012-08-30) Based on Product Version

Issue 08 (2014-02-14) Huawei Proprietary and Confidential iii

l Modify the parameters definition of NO_BD_SOFT.

Updates in Issue 06 (2011-08-20) Based on Product Version

Updates in Issue 05 (2011-01-30) Based on Product Version

Updates in Issue 04 (2010-04-08) Based on Product Version

Added the performance event processing of CRC4BBE and CRC4FEBBE.

Some bugs in the manual of the previous version are fixed.

Updates in Issue 03 (2010-01-25) Based on Product Version

Modify the alarm processing of CLIENT_PORT_PS, INTRA_OTU_PS, MS_SNCP_PS,

Some bugs in the manual of the previous version are fixed.

Updates in Issue 02 (2009-12-18) Based on Product Version

Some bugs in the manual of the previous version are fixed.

Issue 08 (2014-02-14) Huawei Proprietary and Confidential iv

Updates in Issue 01 (2009-10-16) Based on Product Version

Added the alarm processing of OSC_LOS, LASER_HAZARD_WARNING, LAN_LOC and

Deleted the alarm processing of MSSW_DIFFERENT.

Added the performance event processing of FEC_AFT_COR_ERAVR and

Some bugs in the manual of the previous version are fixed.

Updates in Issue 01 (2009-08-10) Based on Product Version

Some bugs in the manual of the previous version are fixed.

Updates in Issue 01 (2009-03-25) Based on Product Version

Some bugs in the manual of the previous version are fixed.

Updates in Issue 01 (2008-12-31) Based on Product Version

Issue 08 (2014-02-14) Huawei Proprietary and Confidential v

About This Document.....................................................................................................................ii

Issue 08 (2014-02-14) Huawei Proprietary and Confidential vi

2.1.12 Alarm List L............................................................................................................................................................44

Issue 08 (2014-02-14) Huawei Proprietary and Confidential vii

2.2.30 LSXL Board Alarm List..........................................................................................................................................86

Issue 08 (2014-02-14) Huawei Proprietary and Confidential viii

2.2.71 TDC Board Alarm List..........................................................................................................................................113

3 Common Alarm Processing.....................................................................................................123

Issue 08 (2014-02-14) Huawei Proprietary and Confidential ix

Issue 08 (2014-02-14) Huawei Proprietary and Confidential x

Issue 08 (2014-02-14) Huawei Proprietary and Confidential xi

Issue 08 (2014-02-14) Huawei Proprietary and Confidential xii

Issue 08 (2014-02-14) Huawei Proprietary and Confidential xiii

Issue 08 (2014-02-14) Huawei Proprietary and Confidential xiv

Issue 08 (2014-02-14) Huawei Proprietary and Confidential xv

Issue 08 (2014-02-14) Huawei Proprietary and Confidential xvi

5 Performance Event List.............................................................................................................568