Professional Documents
Culture Documents
V100R005C00
Issue 02
Date 2010-11-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
The following table lists the product versions related to this document.
Intended Audience
The intended audience of this document are:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Update Description
Whole manual l This manual provides descriptions according to product series OptiX
OSN 8800, OptiX OSN 6800, and OptiX OSN 3800. Any difference
between the products is described in the manual.
l The equipment name is changed from OptiX OSN 8800 I to OptiX
OSN 8800 T32 or from OptiX OSN 8800 II to OptiX OSN 8800 T64.
Update Description
Update Description
Contents
2 Alarm List....................................................................................................................................2-1
2.1 Product Alarm List..........................................................................................................................................2-2
2.1.1 Alarm List A...........................................................................................................................................2-3
2.1.2 Alarm List B...........................................................................................................................................2-4
2.1.3 Alarm List C...........................................................................................................................................2-6
2.1.4 Alarm List D...........................................................................................................................................2-7
2.1.5 Alarm List E...........................................................................................................................................2-8
2.1.6 Alarm List F...........................................................................................................................................2-9
2.1.7 Alarm List G.........................................................................................................................................2-10
2.1.8 Alarm List H.........................................................................................................................................2-10
2.1.9 Alarm List I..........................................................................................................................................2-12
2.1.10 Alarm List J........................................................................................................................................2-13
2.1.11 Alarm List K.......................................................................................................................................2-13
3.1 B1_EXC..........................................................................................................................................................3-4
3.1.1 B1_EXC (OCS)......................................................................................................................................3-4
3.1.2 B1_EXC (OTN).....................................................................................................................................3-7
3.2 BEFFEC_EXC..............................................................................................................................................3-10
3.3 BOOTROM_BAD........................................................................................................................................3-14
3.3.1 BOOTROM_BAD (OCS)....................................................................................................................3-14
3.3.2 BOOTROM_BAD (OTN)....................................................................................................................3-16
3.4 BUS_ERR.....................................................................................................................................................3-17
3.4.1 BUS_ERR (OCS).................................................................................................................................3-17
3.4.2 BUS_ERR (OTN)................................................................................................................................3-20
3.5 CHAN_LOS..................................................................................................................................................3-22
3.6 CLIENT_PORT_PS......................................................................................................................................3-25
3.7 COMMUN_FAIL..........................................................................................................................................3-27
3.7.1 COMMUN_FAIL (OCS).....................................................................................................................3-27
3.7.2 COMMUN_FAIL (OTN).....................................................................................................................3-29
3.8 ETH_8B10B_ERR........................................................................................................................................3-34
3.9 EX_ETHOAM_CC_LOS..............................................................................................................................3-36
3.9.1 EX_ETHOAM_CC_LOS (OCS).........................................................................................................3-36
3.9.2 EX_ETHOAM_CC_LOS (OTN).........................................................................................................3-37
3.10 FC_LINK_ERR...........................................................................................................................................3-39
3.11 FC_SYNC_LOS..........................................................................................................................................3-43
3.12 IN_PWR_HIGH..........................................................................................................................................3-44
3.12.1 IN_PWR_HIGH (OCS)......................................................................................................................3-44
3.12.2 IN_PWR_HIGH (OTN).....................................................................................................................3-46
3.13 IN_PWR_LOW...........................................................................................................................................3-49
3.13.1 IN_PWR_LOW (OCS)......................................................................................................................3-49
3.13.2 IN_PWR_LOW (OTN)......................................................................................................................3-52
3.14 INTRA_OTU_PS........................................................................................................................................3-56
3.15 LASER_MODULE_MISMATCH..............................................................................................................3-58
3.16 LINK_ERR..................................................................................................................................................3-59
3.16.1 LINK_ERR (OCS).............................................................................................................................3-59
3.16.2 LINK_ERR (OTN).............................................................................................................................3-60
3.17 LOOP_ALM................................................................................................................................................3-63
3.17.1 LOOP_ALM (OCS)...........................................................................................................................3-64
3.17.2 LOOP_ALM (OTN)...........................................................................................................................3-65
3.18 LPT_ACTIVE.............................................................................................................................................3-66
3.19 LSR_WILL_DIE.........................................................................................................................................3-69
3.20 MS_AIS.......................................................................................................................................................3-70
3.20.1 MS_AIS (OCS)..................................................................................................................................3-70
3.20.2 MS_AIS (OTN)..................................................................................................................................3-72
3.21 MS_RDI......................................................................................................................................................3-74
3.21.1 MS_RDI (OCS)..................................................................................................................................3-74
4 Alarm Processing........................................................................................................................4-1
4.1 AD_CHECK_FAIL.......................................................................................................................................4-11
4.2 ALC_ADJUST_FAIL...................................................................................................................................4-12
4.3 ALC_WAIT_ADJUST..................................................................................................................................4-14
4.4 ALM_ALS....................................................................................................................................................4-15
4.5 APS_MANUAL_STOP................................................................................................................................4-16
4.6 ALM_GFP_dCSF..........................................................................................................................................4-17
4.7 ALM_GFP_dLFD.........................................................................................................................................4-18
4.8 ALM_HANGUP...........................................................................................................................................4-20
4.9 ALM_TC_OEI..............................................................................................................................................4-21
4.10 ALM_TC_REI............................................................................................................................................4-23
4.11 APE_ADJUST_FAIL..................................................................................................................................4-24
4.12 APE_ADJUST_PEND................................................................................................................................4-25
4.13 APS_FAIL...................................................................................................................................................4-26
4.14 APS_INDI...................................................................................................................................................4-27
4.15 AU_AIS.......................................................................................................................................................4-29
4.16 AU_LOP......................................................................................................................................................4-31
4.17 B1_SD.........................................................................................................................................................4-33
4.17.1 B1_SD (OCS).....................................................................................................................................4-34
4.17.2 B1_SD (OTN)....................................................................................................................................4-37
4.18 B2_EXC......................................................................................................................................................4-38
4.19 B2_SD.........................................................................................................................................................4-41
4.20 B3_EXC......................................................................................................................................................4-44
4.21 B3_EXC_VC3.............................................................................................................................................4-47
4.22 B3_EXC_VC4.............................................................................................................................................4-49
4.23 B3_SD.........................................................................................................................................................4-49
4.24 B3_SD_VC3................................................................................................................................................4-52
4.25 B3_SD_VC4................................................................................................................................................4-54
4.26 BD_NOT_INSTALLED.............................................................................................................................4-55
4.27 BD_STATUS..............................................................................................................................................4-55
4.27.1 BD_STATUS (OCS)..........................................................................................................................4-56
4.27.2 BD_STATUS (OTN).........................................................................................................................4-57
4.28 BDID_ERROR............................................................................................................................................4-58
4.29 C2_VCAIS..................................................................................................................................................4-59
4.30 CHAN_ADD...............................................................................................................................................4-60
4.31 CHIP_ABN.................................................................................................................................................4-61
4.32 CLIENT_PROT_NOTSTART....................................................................................................................4-62
4.33 CLIENT_PORT_STA_INDI......................................................................................................................4-63
4.34 CLK_NO_TRACE_MODE........................................................................................................................4-64
4.35 CRC4_CROSSTR.......................................................................................................................................4-66
4.36 DB_RESTORE_FAIL.................................................................................................................................4-67
4.37 DBPS_ABNORMAL..................................................................................................................................4-68
4.38 DBMS_ERROR..........................................................................................................................................4-69
4.39 DBMS_PROTECT_MODE........................................................................................................................4-71
4.40 DCM_INSUFF............................................................................................................................................4-72
4.41 DLAG_PROTECT_FAIL...........................................................................................................................4-73
4.42 DSP_LOAD_FAIL......................................................................................................................................4-75
4.43 ETH_CFM_LOC.........................................................................................................................................4-76
4.44 ETH_CFM_MISMERGE............................................................................................................................4-77
4.45 ETH_CFM_MACSTATUS........................................................................................................................ 4-79
4.46 ETH_CFM_RDI..........................................................................................................................................4-80
4.47 ETH_CFM_UNEXPERI.............................................................................................................................4-81
4.48 ETH_SERVICE_CONFIG_FAIL...............................................................................................................4-83
4.49 ETHOAM_DISCOVER_FAIL...................................................................................................................4-84
4.50 ETHOAM_RMT_CRIT_FAULT...............................................................................................................4-86
4.51 ETHOAM_RMT_LOOP.............................................................................................................................4-87
4.52 ETHOAM_RMT_SD..................................................................................................................................4-88
4.53 ETHOAM_SELF_LOOP............................................................................................................................4-89
4.54 ETHOAM_VCG_SELF_LOOP..................................................................................................................4-91
4.55 EX_ETHOAM_CC_LOS............................................................................................................................4-92
4.56 EX_ETHOAM_MPID_CNFLCT...............................................................................................................4-94
4.57 EXT_SYNC_LOS.......................................................................................................................................4-95
4.58 EXT_TIME_LOC....................................................................................................................................... 4-96
4.59 FAN_FAIL..................................................................................................................................................4-98
4.60 FAN_FAULT..............................................................................................................................................4-99
4.61 FEATURE_WITHOUT_LICENSE..........................................................................................................4-100
4.62 FC_8B10BERR_OVER............................................................................................................................4-101
4.63 FCS_ERR..................................................................................................................................................4-101
4.64 FEC_LOF..................................................................................................................................................4-104
4.65 FEC_OOF..................................................................................................................................................4-105
4.66 FLOW_OVER...........................................................................................................................................4-106
4.67 FPGA_ABN..............................................................................................................................................4-107
4.68 FSELECT_STG........................................................................................................................................4-108
4.69 FWD_PKT_LOSS.....................................................................................................................................4-109
4.70 GAINDATA_MIS.....................................................................................................................................4-110
4.71 HARD_BAD.............................................................................................................................................4-111
4.72 HARD_ERR..............................................................................................................................................4-114
4.73 HP_LOM...................................................................................................................................................4-117
4.74 HP_RDI.....................................................................................................................................................4-118
4.75 HP_REI.....................................................................................................................................................4-119
4.76 HP_SLM....................................................................................................................................................4-121
4.77 HP_TIM....................................................................................................................................................4-122
4.78 HP_UNEQ.................................................................................................................................................4-124
4.79 HSC_UNAVAIL.......................................................................................................................................4-125
4.80 INTRA_OTU_STA_INDI........................................................................................................................4-126
4.81 J0_MM......................................................................................................................................................4-128
4.82 K1_K2_M..................................................................................................................................................4-129
4.83 K2_M........................................................................................................................................................4-130
4.84 L_SYNC....................................................................................................................................................4-131
4.85 LAN_LOC.................................................................................................................................................4-132
4.86 LAG_PORT_FAIL....................................................................................................................................4-133
4.87 LAG_VC_PORT_FAIL............................................................................................................................4-135
4.88 LASER_HAZARD_WARNING..............................................................................................................4-136
4.89 LASER_SHUT..........................................................................................................................................4-137
4.90 LCS_DAYS_OF_GRACE........................................................................................................................4-138
4.91 LCS_EXPIRED.........................................................................................................................................4-139
4.92 LCS_FILE_NOT_EXIST..........................................................................................................................4-140
4.93 LCAS_FOPR.............................................................................................................................................4-141
4.94 LCAS_FOPT.............................................................................................................................................4-142
4.95 LCAS_PLCR.............................................................................................................................................4-143
4.96 LCAS_PLCT.............................................................................................................................................4-144
4.97 LCAS_TLCR............................................................................................................................................4-146
4.98 LCAS_TLCT.............................................................................................................................................4-147
4.99 LOCAL_FAULT.......................................................................................................................................4-148
4.100 LOCK_CUR_FAIL.................................................................................................................................4-149
4.101 LOCKPOW_MIS....................................................................................................................................4-150
4.102 LP_RDI_VC3..........................................................................................................................................4-151
4.103 LP_SLM_VC3........................................................................................................................................4-152
4.104 LP_UNEQ_VC3......................................................................................................................................4-153
4.105 LPT_RFI..................................................................................................................................................4-154
4.106 LSR_COOL_ALM..................................................................................................................................4-155
4.107 LSR_FORCE_OPEN..............................................................................................................................4-156
4.108 LSR_INVALID.......................................................................................................................................4-157
4.109 LTI...........................................................................................................................................................4-158
4.110 MOD_COM_FAIL..................................................................................................................................4-160
4.111 MODULE_ADJUST_FAIL....................................................................................................................4-161
4.112 MODULE_COOLCUR_OVER..............................................................................................................4-162
4.113 MODULE_TEMP_OVER......................................................................................................................4-163
4.114 MODULEFILE_UPDATE_FAIL...........................................................................................................4-164
4.115 MS_CROSSTR.......................................................................................................................................4-165
4.116 MS_REI...................................................................................................................................................4-166
4.117 MS_SNCP_PS.........................................................................................................................................4-167
4.118 MS_SNCP_STA_INDI...........................................................................................................................4-168
4.119 MS_APS_INDI_EX................................................................................................................................4-170
4.120 MULTI_RPL_OWNER..........................................................................................................................4-171
4.121 NEBD_XC_DIF......................................................................................................................................4-172
4.122 NESF_LOST...........................................................................................................................................4-174
4.123 NESOFT_MM.........................................................................................................................................4-174
4.124 NESTATE_INSTALL............................................................................................................................4-176
4.125 NO_BD_PARA.......................................................................................................................................4-177
4.126 NO_BD_SOFT........................................................................................................................................4-178
4.127 NO_ELABEL..........................................................................................................................................4-179
4.128 NODEID_MM........................................................................................................................................4-180
4.129 NTP_SYNC_FAIL..................................................................................................................................4-181
4.130 NULL_SEND..........................................................................................................................................4-182
4.131 OCH_FDI................................................................................................................................................4-183
4.132 OCH_FDI-O............................................................................................................................................4-184
4.133 OCH_FDI-P............................................................................................................................................4-185
4.134 OCH_LOS-P...........................................................................................................................................4-186
4.135 OCH_OCI................................................................................................................................................4-187
4.136 OCH_SSF................................................................................................................................................4-188
4.137 OCH_SSF-O............................................................................................................................................4-189
4.138 OCH_SSF-P............................................................................................................................................4-190
4.139 ODU_AIS................................................................................................................................................4-190
4.140 ODU_LCK..............................................................................................................................................4-192
4.141 ODU_OCI...............................................................................................................................................4-193
4.142 ODU_SNCP_STA_INDI........................................................................................................................4-194
4.143 ODUk_LOFLOM....................................................................................................................................4-195
4.144 ODUk_PM_LCK....................................................................................................................................4-197
4.145 ODUk_PM_OCI......................................................................................................................................4-198
4.146 ODUk_PM_TIM.....................................................................................................................................4-199
4.147 ODUk_TCMn_AIS.................................................................................................................................4-200
4.148 ODUk_TCMn_BDI.................................................................................................................................4-201
4.149 ODUk_TCMn_DEG...............................................................................................................................4-202
4.150 ODUk_TCMn_EXC................................................................................................................................4-204
4.151 ODUk_TCMn_LCK................................................................................................................................4-205
4.152 ODUk_TCMn_LTC................................................................................................................................4-206
4.153 ODUk_TCMn_OCI.................................................................................................................................4-207
4.154 ODUk_TCMn_SSF.................................................................................................................................4-208
4.155 ODUk_TCMn_TIM................................................................................................................................4-209
4.156 ODUKSP_PS..........................................................................................................................................4-211
4.157 ODUKSP_STA_INDI.............................................................................................................................4-212
4.158 OH_LOOP...............................................................................................................................................4-214
4.159 OLP_PS...................................................................................................................................................4-215
4.160 OLP_STA_INDI.....................................................................................................................................4-216
4.161 OMS_BDI...............................................................................................................................................4-218
4.162 OMS_BDI-O...........................................................................................................................................4-219
4.163 OMS_BDI-P............................................................................................................................................4-220
4.164 OMS_FDI-O............................................................................................................................................4-221
4.165 OMS_FDI-P............................................................................................................................................4-222
4.166 OMS_LOS-P...........................................................................................................................................4-222
4.167 OMS_SSF................................................................................................................................................4-223
4.168 OMS_SSF-O...........................................................................................................................................4-224
4.169 OMS_SSF-P............................................................................................................................................4-225
4.170 OOL.........................................................................................................................................................4-226
4.171 OOS_LOST.............................................................................................................................................4-227
4.172 OPA_FAIL_INDI....................................................................................................................................4-228
4.173 OPU1_MSIM..........................................................................................................................................4-229
4.174 OPU1_VCAT_SQM...............................................................................................................................4-230
4.175 OPU1_VCAT_VcPLM...........................................................................................................................4-231
4.176 OPU2_MSIM..........................................................................................................................................4-232
4.177 OPU3_MSIM..........................................................................................................................................4-232
4.178 OPUk_PLM.............................................................................................................................................4-233
4.179 OSC_BDI................................................................................................................................................4-234
4.180 OSC_DEG...............................................................................................................................................4-235
4.181 OSC_RDI................................................................................................................................................4-236
4.182 OTS_BDI................................................................................................................................................4-237
4.183 OTS_BDI-O............................................................................................................................................4-238
4.184 OTS_BDI-P.............................................................................................................................................4-239
4.185 OTS_LOS-O............................................................................................................................................4-240
4.186 OTS_LOS-P............................................................................................................................................4-241
4.187 OTS_TIM................................................................................................................................................4-242
4.188 OTU_AIS................................................................................................................................................4-243
4.189 OTU_LOF...............................................................................................................................................4-244
4.190 OTU_LOM..............................................................................................................................................4-245
4.191 OTUk_AIS..............................................................................................................................................4-246
4.192 OTUk_BDI..............................................................................................................................................4-247
4.193 OTUk_DEG............................................................................................................................................4-248
4.194 OTUk_EXC.............................................................................................................................................4-249
4.195 OTUk_LOM............................................................................................................................................4-250
4.196 OTUk_TIM.............................................................................................................................................4-251
4.197 OUT_PWR_LOW...................................................................................................................................4-253
4.198 OWSP_PS...............................................................................................................................................4-254
4.199 OWSP_STA_INDI..................................................................................................................................4-255
4.200 PATCH_ACT_TIMEOUT......................................................................................................................4-257
4.201 PATCH_DEACT_TIMEOUT................................................................................................................4-258
4.202 PATCH_PKGERR..................................................................................................................................4-259
4.203 PM_BDI..................................................................................................................................................4-260
4.204 PM_BEI...................................................................................................................................................4-261
4.205 PM_BIP8_OVER....................................................................................................................................4-262
4.206 PM_BIP8_SD..........................................................................................................................................4-263
4.207 PM_TIM..................................................................................................................................................4-265
4.208 PORTSWITCH_FAIL............................................................................................................................4-266
4.209 POWER_ABNORMAL..........................................................................................................................4-266
4.210 POWER_DIFF_OVER...........................................................................................................................4-268
4.211 PRBS_LSS..............................................................................................................................................4-269
4.212 PUM_BCM_ALM..................................................................................................................................4-270
4.213 PUM_TEM_ALM...................................................................................................................................4-271
4.214 R_LOC....................................................................................................................................................4-272
4.214.1 R_LOC (OCS)................................................................................................................................4-272
4.214.2 R_LOC (OTN)...............................................................................................................................4-273
4.215 RELAY_ALARM_CRITICAL ..............................................................................................................4-274
4.216 RELAY_ALARM_IGNORE .................................................................................................................4-275
4.217 RELAY_ALARM_MAJOR ...................................................................................................................4-277
4.218 RELAY_ALARM_MINOR ...................................................................................................................4-278
4.219 REM_SD.................................................................................................................................................4-279
4.220 RS_CROSSTR........................................................................................................................................4-280
4.221 RTC_FAIL..............................................................................................................................................4-281
4.222 S1_SYN_CHANGE................................................................................................................................4-282
4.223 SCC_LOC...............................................................................................................................................4-283
4.224 SEC_RADIUS_FAIL..............................................................................................................................4-284
4.225 SERVICE_TYPE_EXCEED_LICENSE................................................................................................4-285
4.226 SERVICE_CAPACITY_EXCEED_LICENSE......................................................................................4-286
4.227 SHELF_AREA_POWER_OVER...........................................................................................................4-287
4.228 SPAN_LOSS_HIGH...............................................................................................................................4-288
4.229 SPAN_LOSS_LOW................................................................................................................................4-289
4.230 SLAVE_WORKING...............................................................................................................................4-290
4.231 SM_BDI..................................................................................................................................................4-292
4.232 SM_BEI...................................................................................................................................................4-293
4.233 SM_BIP8_OVER....................................................................................................................................4-294
4.234 SM_BIP8_SD..........................................................................................................................................4-295
4.235 SM_IAE..................................................................................................................................................4-296
4.236 SM_TIM..................................................................................................................................................4-297
4.237 SNCP_FAIL............................................................................................................................................4-298
4.238 SO_SK_MISMATCH.............................................................................................................................4-299
4.239 SPEED_OVER........................................................................................................................................4-301
4.240 STORM_CUR_QUENUM_OVER........................................................................................................4-302
4.241 SUBRACK_ID_MISMATCH................................................................................................................4-302
4.242 SUBRACK_LOOP..................................................................................................................................4-303
4.243 SUM_INPWR_HI...................................................................................................................................4-304
4.244 SW_SNCP_PS........................................................................................................................................4-306
4.245 SW_SNCP_STA_INDI...........................................................................................................................4-307
4.246 SWDL_ACTIVATED_TIMEOUT.........................................................................................................4-308
4.247 SWDL_AUTOMATCH_INH.................................................................................................................4-309
4.248 SWDL_BD_EXCLUDE.........................................................................................................................4-310
4.249 SWDL_CHGMNG_NOMATCH............................................................................................................4-311
4.250 SWDL_COMMIT_FAIL........................................................................................................................4-312
4.251 SWDL_INPROCESS..............................................................................................................................4-313
4.252 SWDL_PKG_NOBDSOFT....................................................................................................................4-314
4.253 SWDL_PKGVER_MM..........................................................................................................................4-315
4.254 SWDL_ROLLBACK_FAIL...................................................................................................................4-315
4.255 SYN_BAD..............................................................................................................................................4-316
4.256 SYNC_C_LOS........................................................................................................................................4-318
4.257 SYNC_DISABLE...................................................................................................................................4-319
4.258 SYNC_F_M_SWITCH...........................................................................................................................4-320
4.259 SYNC_LOCKOFF..................................................................................................................................4-322
4.260 SYNC_FAIL...........................................................................................................................................4-323
4.261 SYSPARA_CFDB_NOSAME................................................................................................................4-324
4.262 T_LOSEX................................................................................................................................................4-325
4.263 T_SLIP....................................................................................................................................................4-326
4.264 TEM_HA.................................................................................................................................................4-326
4.265 TEM_LA.................................................................................................................................................4-327
4.266 TEMP_OVER.........................................................................................................................................4-328
4.267 TEST_STATUS......................................................................................................................................4-331
4.268 THUNDERALM.....................................................................................................................................4-331
4.269 TIME_LOS..............................................................................................................................................4-333
4.270 TIME_NO_TRACE_MODE..................................................................................................................4-334
4.271 TR_LOC..................................................................................................................................................4-335
4.272 TU_AIS_VC3..........................................................................................................................................4-337
4.273 TU_LOP_VC3........................................................................................................................................4-338
4.274 VCAT_LOA............................................................................................................................................4-339
4.274.1 VCAT_LOA (OCS).......................................................................................................................4-339
4.274.2 VCAT_LOA (OTN).......................................................................................................................4-340
4.275 VCAT_LOM_VC3..................................................................................................................................4-341
4.276 VCAT_LOM_VC4..................................................................................................................................4-342
4.277 VLAN_SNCP_PS...................................................................................................................................4-343
4.278 VOA_ADJUST_FAIL............................................................................................................................4-344
4.279 VOADATA_MIS....................................................................................................................................4-345
4.280 W_R_FAIL..............................................................................................................................................4-346
4.281 WAVE_ADD_ABN................................................................................................................................4-347
4.282 WAVE_DROP_ABN..............................................................................................................................4-348
4.283 WAVEDATA_MIS.................................................................................................................................4-349
4.284 WAVELEN_OVER................................................................................................................................4-350
4.285 XC_UNSWITCH....................................................................................................................................4-351
6.28 HPFEBBE...................................................................................................................................................6-28
6.29 HPFECSES..................................................................................................................................................6-29
6.30 HPFEES......................................................................................................................................................6-30
6.31 HPFESES....................................................................................................................................................6-31
6.32 HPFEUAS...................................................................................................................................................6-32
6.33 HPSES.........................................................................................................................................................6-33
6.34 HPUAS........................................................................................................................................................6-34
6.35 ICCLC.........................................................................................................................................................6-35
6.36 ICTMP.........................................................................................................................................................6-36
6.37 LSBIAS.......................................................................................................................................................6-37
6.38 LSBISA.......................................................................................................................................................6-38
6.39 LSCLC........................................................................................................................................................6-39
6.40 LSIOP..........................................................................................................................................................6-40
6.41 LSOOP........................................................................................................................................................6-41
6.42 LSTMP........................................................................................................................................................6-42
6.43 MSBBE.......................................................................................................................................................6-43
6.44 MSCSES......................................................................................................................................................6-44
6.45 MSES..........................................................................................................................................................6-45
6.46 MSFEBBE...................................................................................................................................................6-46
6.47 MSFECSES.................................................................................................................................................6-46
6.48 MSFEES......................................................................................................................................................6-47
6.49 MSFESES....................................................................................................................................................6-48
6.50 MSFEUAS..................................................................................................................................................6-49
6.51 MSSES........................................................................................................................................................6-50
6.52 MSUAS.......................................................................................................................................................6-51
6.53 ODU2PMBIP8............................................................................................................................................6-52
6.54 ODUk_PM_BBE.........................................................................................................................................6-53
6.55 ODUk_PM_BBER......................................................................................................................................6-53
6.56 ODUk_PM_ES............................................................................................................................................6-54
6.57 ODUk_PM_FEBBE....................................................................................................................................6-55
6.58 ODUk_PM_FEBBER.................................................................................................................................6-56
6.59 ODUk_PM_FEES.......................................................................................................................................6-57
6.60 ODUk_PM_FESES.....................................................................................................................................6-57
6.61 ODUk_PM_FESESR..................................................................................................................................6-58
6.62 ODUk_PM_FEUAS....................................................................................................................................6-59
6.63 ODUk_PM_SES..........................................................................................................................................6-60
6.64 ODUk_PM_SESR.......................................................................................................................................6-60
6.65 ODUk_PM_UAS........................................................................................................................................6-61
6.66 ODUk_TCMn_BBE....................................................................................................................................6-62
6.67 ODUk_TCMn_BBER.................................................................................................................................6-63
6.68 ODUk_TCMn_BIAES................................................................................................................................6-64
6.69 ODUk_TCMn_ES.......................................................................................................................................6-64
6.70 ODUk_TCMn_FEBBE...............................................................................................................................6-65
6.71 ODUk_TCMn_FEBBER............................................................................................................................6-66
6.72 ODUk_TCMn_FEES..................................................................................................................................6-67
6.73 ODUk_TCMn_FESES................................................................................................................................6-67
6.74 ODUk_TCMn_FESESR.............................................................................................................................6-68
6.75 ODUk_TCMn_FEUAS...............................................................................................................................6-69
6.76 ODUk_TCMn_IAES...................................................................................................................................6-69
6.77 ODUk_TCMn_SES.....................................................................................................................................6-70
6.78 ODUk_TCMn_SESR..................................................................................................................................6-71
6.79 ODUk_TCMn_UAS....................................................................................................................................6-71
6.80 OSC_BBE...................................................................................................................................................6-72
6.81 OSC_BBER.................................................................................................................................................6-73
6.82 OSC_BIAES................................................................................................................................................6-73
6.83 OSC_ES......................................................................................................................................................6-74
6.84 OSC_FEBBE...............................................................................................................................................6-75
6.85 OSC_FEBBER............................................................................................................................................6-75
6.86 OSC_FEES..................................................................................................................................................6-76
6.87 OSC_FESES................................................................................................................................................6-77
6.88 OSC_FESESR.............................................................................................................................................6-77
6.89 OSC_FEUAS..............................................................................................................................................6-78
6.90 OSC_IAES..................................................................................................................................................6-79
6.91 OSC_SES....................................................................................................................................................6-79
6.92 OSC_SESR..................................................................................................................................................6-80
6.93 OSC_UAS...................................................................................................................................................6-80
6.94 OSPICCV....................................................................................................................................................6-81
6.95 OSPITMP....................................................................................................................................................6-82
6.96 OTU2SMBIP8.............................................................................................................................................6-83
6.97 OTUk_BBE.................................................................................................................................................6-84
6.98 OTUk_BBER..............................................................................................................................................6-84
6.99 OTUk_ES....................................................................................................................................................6-85
6.100 OTUk_FEBBE..........................................................................................................................................6-86
6.101 OTUk_FEBBER........................................................................................................................................6-87
6.102 OTUk_FEES.............................................................................................................................................6-88
6.103 OTUk_FESES...........................................................................................................................................6-88
6.104 OTUk_FESESR........................................................................................................................................6-89
6.105 OTUk_FEUAS..........................................................................................................................................6-90
6.106 OTUk_SES................................................................................................................................................6-91
6.107 OTUk_SESR.............................................................................................................................................6-91
6.108 OTUk_UAS...............................................................................................................................................6-92
6.109 PCLSOP....................................................................................................................................................6-93
6.110 PCLSSN....................................................................................................................................................6-94
6.111 PCLSWL...................................................................................................................................................6-95
6.112 PCLSWLO................................................................................................................................................6-95
6.113 RPL............................................................................................................................................................6-96
6.114 RSBBE......................................................................................................................................................6-97
6.115 RSCSES....................................................................................................................................................6-98
6.116 RSES.........................................................................................................................................................6-99
6.117 RSOFS.....................................................................................................................................................6-100
6.118 RSOOF....................................................................................................................................................6-101
6.119 RSSES.....................................................................................................................................................6-102
6.120 RSUAS....................................................................................................................................................6-103
6.121 SUMIOP..................................................................................................................................................6-104
6.122 SUMOOP................................................................................................................................................6-105
6.123 TLB.........................................................................................................................................................6-106
6.124 TPL..........................................................................................................................................................6-107
6.125 VC3BBE..................................................................................................................................................6-108
6.126 VC3CSES................................................................................................................................................6-109
6.127 VC3ES.....................................................................................................................................................6-111
6.128 VC3FEBBE.............................................................................................................................................6-113
6.129 VC3FECSES...........................................................................................................................................6-114
6.130 VC3FEES................................................................................................................................................6-115
6.131 VC3FESES..............................................................................................................................................6-116
6.132 VC3FEUAS.............................................................................................................................................6-117
6.133 VC3SES..................................................................................................................................................6-119
6.134 VC3UAS.................................................................................................................................................6-120
6.135 WCV........................................................................................................................................................6-121
6.136 XCSTMP.................................................................................................................................................6-122
7 Event List.....................................................................................................................................7-1
8 Event Processing.........................................................................................................................8-1
8.1 EAPE abnormal event notification..................................................................................................................8-2
8.2 EAPE adjustment result event notification.....................................................................................................8-3
8.3 OWSP abnormal event....................................................................................................................................8-6
8.4 ODUk SPRing abnormal event.......................................................................................................................8-9
8.5 RMON performance value is above the upper limit.....................................................................................8-11
8.6 RMON module performance value is lower than the lower threshold..........................................................8-13
8.7 1+1 Equipment Level Protection Switching Event Report...........................................................................8-15
A Glossary.....................................................................................................................................A-1
Figures
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals....................1-7
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals....................1-8
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals..................1-10
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals..................1-11
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals..........................1-13
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals..........................1-14
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals.........................1-16
Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals.........................1-17
Figure 1-9 Alarm signal flow of the regenerating OTU.....................................................................................1-19
Figure 1-10 OTU with the cross-connect function in the straight-through mode..............................................1-20
Figure 1-11 OTU with the cross-connect function in the cross-connect mode..................................................1-21
Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals ...........................................................1-23
Figure 1-13 Alarm signal flow 2: when the OTU processes GE signals............................................................1-24
Figure 1-14 Scenario I........................................................................................................................................1-25
Figure 1-15 Scenario II.......................................................................................................................................1-26
Figure 1-16 Scenario III.....................................................................................................................................1-27
Figure 1-17 Suppression of OTN alarms...........................................................................................................1-30
Figure 1-18 Suppression of alarms related to SDH services and other common equipment alarms.................1-31
Tables
1 Overview
This chapter describes the meaning and indicator status of the alarms of four levels, and the
meaning, range and severity of the alarms in different categories. Describes different types of
performance event, the alarm signal flow of the OTU unit and the suppression relation of alarms.
1.1 Alarm Level
This section respectively describes the meaning, influence 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
Performance events can be classified into ten categories according to the function monitored by
a performance event. Among these performance events, Performance Event of Higher Order
Path Bit Error, Lower Order Path Bit Error and Pointer Justification are supported only by the
OptiX OSN 8800.
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.
Critical alarm Global fault alarms and event alarms that The SRV is on (red).
would cause system down.
Major alarm Faulty alarms and event alarms of partial The SRV is on (red).
boards or lines.
Minor alarm General fault alarms and event alarms that are The SRV is on (yellow).
used to describe whether the board or line is
normally working.
Warning Fault alarms and event alarms for warning. The alarm indicator is off.
alarm
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.
Performance event related to the The performance event generated when bit errors occur to
bit errors of the regenerator the regenerator section in the SDH frames of the signals
section on the WDM side or the client side of the board.
Performance event related to the The performance event generated when bit errors occur to
bit errors of the multiplex the multiplex section in the SDH frames of the signals on
section the WDM side or the client side of the board.
Performance Event of Higher The performance event generated when bit errors occur to
Order Path Bit Error higher order path.
Performance Event of Lower The performance event generated when bit errors occur to
Order Path Bit Error lower order path.
Performance Event of Pointer The performance event generated when the board
Justification performs pointer justification
Performance event related to the The performance event generated when the board
check and error correction performs service check or bit error correction.
Performance event related to the The performance event generated when the optical power,
equipment function the working current of the laser or other factors about the
running environment exceed the threshold.
OTN performance event The performance event generated when bit errors occur to
the PM, TCM or SM segment of the OTN service.
RMON performance event The performance event related to the mode in which the
board transmits or receives the data packets, the number
and quality of packets in different lengths transmitted or
received.
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.
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.
1.4.3 Non-Convergent OTU Processing Standard OTN Signals
This section describes the alarm signal flow when the non-convergent OTU unit processes
standard OTN 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:
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:
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
SF
R_LOS
R_LOS R_LOF R_LOF
SF
R_LOF
R_LOF R_LOF R_LOF
MS_AIS
MS_AIS MS_AIS MS_AIS
SD
BI errors B1_SD/ B1_SD/
B1errors
B1_EXC B1_EXC
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
SF
OTUk_AIS
OTUk_AIS R_LOF
ODUk_PM_BDI
&OTUk_BDI
SD
OTUk_LOM
OTUk_AIS R_OOF
ODUk_PM_BDI
&OTUk_BDI
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
Station A Station B Client device
Client-side WDM-side WDM-side Client-side Client-device
ODUk_PM_BDI
SF
SM TTI byte mismatch
OTUk_TIM R_LOF
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
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
For TIM alarm: The SF event is generated when the TIM follow-up 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.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
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
Station A Station B Client device
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
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
OTUk_BDI
OTUk_BDI OTUk_BDI
OTUk_BDI OTUk_BDI
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.
NOTE
l 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.
l 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
The ALS function of the OTU shown in the figures in this section is not enabled.
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Station A Station B Client device
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_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
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
Station A Station B Client device
Client-side Middle WDM-side WDM-side Middle Client-side Client-device
R_LOF
SF R_LOF
R_LOS
R_LOS
R_LOF
ODUk_PM_BDI&
OTUk_BDI R_LOF
R_LOF
SF
OTUk_LOF/ R_LOF
OTUk_AIS OTUk_LOF/
OTUk_AIS
R_LOF
ODUk_PM_BDI&
R_LOF
OTUk_BDI
R_LOF
ODUk_PM_AIS/ SF
ODUk_PM_LCK/ ODUk_PM_AIS/ R_LOF
ODUk_PM_OCI ODUk_PM_LCK/
ODUk_PM_OCI R_LOF
ODUk_PM_BDI R_LOF
Errors
SD
PM BIP8 errors ODUk_PM_DEG/ Errors
ODUk_PM_EXC
Errors
Errors
SD
Errors
SM BIP8 errors OTUk_DEG/
OTUk_EXC
Errors
PM remote BER
performance events Errors
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
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.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
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.
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
The ALS function of the OTU shown in the figures in this section is not enabled.
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
Station A Station B Client device
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
R_LOS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS
OTUk_LOM SF
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
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
ODUk_PM_AIS
N#1 ODUk_PM_AIS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
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.
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 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
Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
Station A Station B Client device
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
performance events Errors
Errors
SD
SM BIP8 errors Errors
OTUk_DEG/
OTUk_EXC
Errors
NOTE
The value of k on the WDM-side is different from that of the client device.
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
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.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
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
switching is triggered.
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.
MFASframe discontinuous
OTUk_LOM ODUk_PM_AIS
OTUk_BDI
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
R_LOS
R_LOS ODUk_PM_AIS
OTUk_BDI
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).
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
CAUTION
In any mode, proper configuration must be made on the U2000.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals
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
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
Station A Station B Client device
SF
R_LOS
R_LOS None LINK_ERR
MS_BDI
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.
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.
OTU OTU
OTU
OM OA OA OD
OTU
Client-side equipment
Client-side equipment
Line-side ODF
Line-side ODF
OTU OTU
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 alarm 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
reports the OTS_BDI alarm.
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.
OTU OTU
OTU
Client-side equipment
Client-side equipment
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
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.
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 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 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. 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.
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 alarm and the FIU board at station B does
not report the OTS_LOS-P alarm.
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
Client-side equipment
Client-side equipment
West line-side ODF
Line-side ODF
OTU
Line-side ODF
OTU O O O OO O OO
T T T T T T T T OTU
U U U UU U UU
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.
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. Station C reports the OCh_FDI or OCh_SSF alarm (for
wavelengths between stations A and C).
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. Station C reports the OCh_FDI-P or OCh_SSF-P alarm (for
wavelengths between stations A and C).
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 alarm 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. Station C reports the OCh_FDI-O or OCh_SSF-O alarm
(for wavelengths between stations A and C).
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
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
wavelengths between stations A and C).
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).
l The OTU board at station A is faulty.
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
wavelengths between stations A and C).
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
reports the OTS_BDI alarm.
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 alarm and the FIU board at station C does
not report the OTS_LOS-P alarm.
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
reports the OTS_BDI alarm.
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).
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
1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment 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.
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
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
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 bit error performance event. However, the B1 bit error
performance event is not important for the maintenance engineer. In this case, the equipment
suppresses the B1 bit error performance event through the R_LOS alarm. Only the R_LOS alarm
is reported by the optical interface.
For OptiX OSN 8800, Table 1-4 lists the performance events suppressed by the R_LOS alarm.
For OptiX OSN 6800/3800, Table 1-5 lists the performance events suppressed by the R_LOS
alarm.
Table 1-4 Performance events suppressed by the R_LOS alarm (OptiX OSN 8800)
MSFEBBE FEC_AFT_COR_ER
MSFEUAS FEC_BEF_COR_ER
Table 1-5 Performance events suppressed by the R_LOS alarm (OptiX OSN 6800/3800)
Table 1-6 lists the performance events suppressed by the NO_BD_PARA alarm.
2 Alarm List
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.
B3_SD The higher order path Minor SF64, SF64A, SFD64, SL64,
B3 signals received SLD64, SLH41, SLO16,
on the line are SLQ16, SLQ64
degraded.
INTRA_OTU_STA_I The state of the Intra- Minor DCP, LDGD, LDM, LDMD,
NDI OTU 1+1 optical LQM, LQMD, LWXD, LWXS,
channel protection OLP, TOM
group
LASER_SHUT The laser of the board Major SF64, SF64A, SFD64, SL64,
is shut down SLD64, SLH41, SLO16,
SLQ16, SLQ64
ODU_SNCP_STA_IN The state of the ODU Minor ELQX, ENQ2, LQMS, ND2,
DI SNCP protection NPO2, NQ2, NS2, NS3, PTQX,
group TDX, TOM, TQM, TQS, TQX,
TSXL
ODU1_LOFLOM The FAS and MFAS Critica ELQX, ENQ2, LDGD, LDGS,
are abnormal l LDM, LDMD, LDMS, LQM,
LQMD, LQMS, ND2, NPO2,
ODU1_PM_AIS ODU1 PM alarm Warni NQ2, NS2, NS3, PTQX, TDG,
indication signal ng TDX, TMX, TOG, TOM, TQM,
ODU1_PM_BDI ODU1 PM backward Warni TQS
defect indication ng
ODU2_LOFLOM The FAS and MFAS Critica ELQX, LOG, ND2, NS2, NS3,
are abnormal l PTQX, TDX, TMX, TQX,
TSXL
ODUKSP_STA_INDI The state of the Minor ENQ2, ND2, NPO2, NQ2, NS2,
ODUk SPRing NS3
protection group
SPAN_LOSS_HIGH Span loss is too high Major HBA, OAU1, OBU1, OBU2,
VA1, VA4
SUM_INPWR_HI Sum input optical Major D40, D40V, FIU, HBA, OAU1,
power is too high OBU1, OBU2, RDU9, RMU9,
ROAM, VA1, WSD9, WSMD2,
SUM_INPWR_LOW Sum input optical Major WSMD4
power is excessively
low
SW_SNCP_STA_IND The state of the Sub- Minor L4G, LDGD, LDGS, LOG,
I Wavelength SNCP LOM, LQG, LQM, LQMD,
protection group. LQMS, TDG, TOM, TQM
TN22AUX
BD_STATUS HARD_ERR RELAY_ALARM_MAJOR
TN21AUX
BD_STATUS NO_BD_SOFT RELAY_ALARM_MAJOR
HARD_ERR RELAY_ALARM_IG-
NORE
TN51AUX
BD_STATUS HARD_BAD WRG_BD_TYPE
COMMUN_FAIL HARD_ERR
OMS_FDI OMS_SSF_O
OMS_FDI OMS_SSF_O
OPA_FAIL_INDI
OPA_FAIL_INDI
OPA_FAIL_INDI
LASER_HAZARD_WARN- OUT_PWR_HIGH
ING
LOCKPOW_MIS OUT_PWR_LOW
NO_BD_PARA OMS_SSF
NO_BD_SOFT OMS_SSF_O
NO_BD_SOFT OMS_SSF
NO_BD_PARA OCh_SSF_O
TN12DCP
BD_STATUS NO_BD_SOFT OPA_FAIL_INDI
INTRA_OTU_STA_INDI OCh_SSF_O
NO_BD_PARA OCh_SSF_P
OPA_FAIL_INDI OTS_LOS-O
OTS_BDI OTS_LOS-P
OPA_FAIL_INDI
IN_PWR_HIGH OUT_PWR_LOW TF
LOOP_ALM TD
LAN_LOC RELAY_ALARM_MAJOR
LAN_LOC RELAY_ALARM_MAJOR
RELAY_ALARM_CRITI- RELAY_ALARM_MINOR
CAL
BOOTROM_BAD LAG_PORT_FAIL TD
ETHOAM_RMT_CRIT_FA LCAS_PLCT TF
ULT
ETH_CFM_UNEXPERI LSR_INVALID
ODU1_TCM3_AIS ODU2_TCM2_TIM TD
ODU1_TCM3_LTC ODU2_TCM3_LCK TF
FAN_FAIL
OPA_FAIL_INDI OTS_LOS-O
OTS_BDI OTS_LOS-P
TN12FIU
BD_STATUS OTS_BDI SUM_INPWR_HI
OOS_LOST OTS_LOS-P
OPA_FAIL_INDI OTS_TIM
TN11FIU
BD_STATUS OOS_LOST OTS_TIM
NO_BD_SOFT OTS_LOS-O
NO_ELABEL OTS_LOS-P
TN21FIU
BD_STATUS OTS_BDI-O OTS_TIM
OPA_FAIL_INDI OTS_LOS-O
OTS_BDI OTS_LOS-P
COMMUN_FAIL
LASER_HAZARD_W SPAN_LOSS_LOW
ARNING
CRC4_CROSSTR NO_BD_SOFT TD
HARD_ERR OSC_LOS TF
LOOP_ALM OUT_PWR_LOW
OMS_FDI OMS_SSF-O
TN12ITL
BD_STATUS OMS_BDI-P OMS_SSF-O
OCh_SSF ODU5G_TCM4_LCK TD
ODU5G_PM_AIS ODU5G_TCM4_TIM TF
ODU5G_PM_LCK ODU5G_TCM5_EXC
OCh_OCI ODU1_TCM4_LCK TD
ODU1_LOFLOM ODU1_TCM4_TIM TF
OCh_OCI ODU1_TCM4_LCK TD
ODU1_LOFLOM ODU1_TCM4_TIM TF
ODU1_PM_DEG ODU1_TCM5_DEG
ODU1_PM_EXC ODU1_TCM5_EXC
OCh_SSF_O ODU1_TCM4_LTC TD
ODU1_PM_BDI ODU1_TCM5_AIS TF
ODU1_PM_OCI ODU1_TCM5_LCK
OCh_SSF ODU1_TCM4_LCK TD
ODU1_PM_AIS ODU1_TCM4_TIM TF
ODU1_PM_LCK ODU1_TCM5_EXC
OCh_SSF_P ODU1_TCM4_LTC TD
ODU1_PM_DEG ODU1_TCM5_AIS TF
OCh_SSF_P ODU2_TCM4_SSF TD
ODU2_PM_LCK ODU2_TCM5_DEG TF
LINK_ERR ODU2_TCM4_AIS TD
LSR_FORCE_OPEN ODU2_TCM4_LTC TF
MULTI_RPL_OWNER ODU2_TCM4_TIM
LINK_ERR ODU2_TCM4_AIS TD
LSR_FORCE_OPEN ODU2_TCM4_LTC TF
MULTI_RPL_OWNER ODU2_TCM4_TIM
OCh_SSF ODU2_TCM4_LTC TD
ODU2_PM_BDI ODU2_TCM5_AIS TF
ODU2_PM_OCI ODU2_TCM5_LCK
TN11LOG
BD_STATUS ODU2_PM_OCI ODU2_TCM5_LCK
OCh_SSF_O ODU2_TCM4_LTC TD
ODU2_PM_BDI ODU2_TCM5_AIS TF
OCh_LOS_P ODU2_TCM4_DEG TD
OCh_SSF_P ODU2_TCM4_SSF TF
OCh_SSF ODU5G_TCM4_LTC TD
ODU5G_PM_AIS ODU5G_TCM5_AIS TF
ODU5G_PM_EXC ODU5G_TCM5_EXC
ODU5G_PM_LCK ODU5G_TCM5_LCK
OCh_OCI ODU1_TCM4_LTC TD
ODU1_LOFLOM ODU1_TCM5_AIS TF
ODU1_PM_EXC ODU1_TCM5_LCK
TN11LQMD
B1_EXC ODU1_PM_LCK ODU1_TCM5_LTC
OCh_LOS_P ODU1_TCM4_LCK TD
OCh_SSF_P ODU1_TCM4_TIM TF
ODU1_PM_DEG ODU1_TCM5_EXC
ODU1_PM_EXC ODU1_TCM5_LCK
OCh_SSF_O ODU1_TCM4_SSF TD
ODU1_PM_BDI ODU1_TCM5_DEG TF
ODU1_PM_OCI ODU1_TCM5_OCI
TN11LQMS
B1_EXC ODU1_PM_OCI ODU1_TCM5_LTC
OCh_SSF ODU1_TCM4_LTC TD
ODU1_PM_AIS ODU1_TCM5_AIS TF
ODU1_PM_LCK ODU1_TCM5_LCK
OCh_OCI ODU1_TCM4_LTC TD
ODU1_LOFLOM ODU1_TCM5_AIS TF
ODU1_PM_EXC ODU1_TCM5_LCK
ODU1_PM_LCK ODU1_TCM5_LTC
ODU3_PM_LCK ODU3_TCM4_LTC TD
ODU3_TCM1_AIS ODU3_TCM5_AIS TF
ODU3_TCM1_LCK ODU3_TCM5_LCK
ODU3_TCM1_LTC ODU3_TCM5_LTC
TN12LSXLR
ODU3_PM_SSF ODU3_TCM4_SSF TD
ODU3_TCM1_AIS ODU3_TCM5_AIS TF
ODU3_TCM1_LCK ODU3_TCM5_LCK
ODU3_PM_BDI ODU3_TCM4_SSF TD
ODU3_PM_SSF ODU3_TCM5_DEG TF
ODU3_TCM1_BDI ODU3_TCM5_OCI
TN12LSXL
B1_EXC ODU3_TCM1_AIS ODU3_TCM5_LTC
ODU3_PM_DEG ODU3_TCM4_TIM TD
ODU3_PM_OCI ODU3_TCM5_BDI TF
ODU2_PM_SSF ODU2_TCM4_OCI TD
ODU2_TCM1_DEG ODU2_TCM5_BDI TF
OCh_SSF_P ODU2_TCM4_SSF TD
ODU2_PM_LCK ODU2_TCM5_DEG TF
TN12LSX
B1_EXC ODU2_PM_TIM ODU2_TCM5_SSF
OCh_SSF ODU2_TCM4_OCI TD
ODU2_PM_BDI ODU2_TCM5_BDI TF
ODU2_PM_OCI ODU2_TCM5_LTC
ODU2_PM_SSF ODU2_TCM5_OCI
TN13LSX
B1_EXC ODU2_PM_TIM ODU2_TCM5_SSF
OCh_SSF ODU2_TCM4_OCI TD
ODU2_PM_BDI ODU2_TCM5_BDI TF
ODU2_PM_OCI ODU2_TCM5_LTC
ODU2_PM_SSF ODU2_TCM5_OCI
HARD_ERR OCh_FDI_P TD
LASER_MODULE_MIS- OCh_SSF_O TF
MATCH
HARD_ERR OCh_FDI_O TD
IN_PWR_LOW OCh_SSF TF
LOOP_ALM OPA_FAIL_INDI
HARD_ERR OCh_FDI_P TD
LASER_MODULE_MIS- OCh_SSF_O TF
MATCH
TN12LWXS
HARD_BAD OCh_FDI_P TD
J0_MM OCh_SSF_O TF
LSR_COOL_ALM OUT_PWR_HIGH
HARD_ERR NO_ELABEL
MODULE_COOLCUR_OV OPA_FAIL_INDI
ER
COMMUN_FAIL NO_ELABEL
HARD_BAD PORTSWITCH_FAIL
COMMUN_FAIL NO_ELABEL
HARD_BAD PORTSWITCH_FAIL
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
OMS_FDI OMS_SSF-P
ODU1_TCM2_LCK ODU2_TCM2_LTC TD
ODU1_TCM2_TIM ODU2_TCM3_AIS TF
ODU1_TCM3_DEG ODU2_TCM3_LCK
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.
ODU1_TCM2_LTC ODU2_TCM3_DEG TD
ODU1_TCM3_AIS ODU2_TCM3_SSF TF
ODU1_TCM3_LCK ODU2_TCM4_BDI
ODU1_TCM2_DEG ODU2_TCM2_LTC TD
ODU1_TCM2_SSF ODU2_TCM3_AIS TF
ODU1_TCM3_BDI ODU2_TCM3_LCK
TN52NQ2
ODU1_TCM2_DEG ODU2_TCM2_LTC TD
ODU1_TCM2_SSF ODU2_TCM3_AIS TF
ODU1_TCM3_BDI ODU2_TCM3_LCK
TN51NQ2
BD_STATUS ODU1_TCM3_SSF ODU2_TCM3_OCI
ODU1_TCM2_SSF ODU2_TCM2_OCI TD
ODU1_TCM3_DEG ODU2_TCM3_BDI TF
ODU1_TCM3_OCI ODU2_TCM3_LTC
ODU1_TCM2_DEG ODU2_TCM2_LTC TD
ODU1_TCM2_SSF ODU2_TCM3_AIS TF
ODU1_TCM3_BDI ODU2_TCM3_LCK
ODU1_TCM3_DEG ODU2_TCM3_LTC
TN12NS2
BD_STATUS ODU1_TCM4_AIS ODU2_TCM3_TIM
ODU1_TCM2_TIM ODU2_TCM2_SSF TD
ODU1_TCM3_LCK ODU2_TCM3_DEG TF
ODU1_TCM3_SSF ODU2_TCM3_OCI
ODU1_TCM3_TIM ODU2_TCM3_SSF
TN11NS2
BD_STATUS ODU1_TCM4_AIS ODU2_TCM3_SSF
ODU1_TCM3_AIS ODU2_TCM2_SSF TD
ODU1_TCM3_LTC ODU2_TCM3_DEG TF
ODU1_TCM3_TIM ODU2_TCM3_OCI
ODU1_TCM4_TIM ODU3_PM_DEG TD
ODU1_TCM5_EXC ODU3_PM_SSF TF
ODU1_TCM5_LTC ODU3_TCM1_AIS
ODU1_TCM5_OCI ODU3_TCM1_BDI
TN52NS3
BD_STATUS ODU1_TCM5_SSF ODU3_TCM1_LCK
ODU1_TCM4_SSF ODU3_PM_EXC TD
ODU1_TCM5_DEG ODU3_PM_TIM TF
ODU1_TCM5_OCI ODU3_TCM1_DEG
TN11NS3
BD_STATUS ODU3_PM_TIM ODU3_TCM5_LCK
ODU3_PM_AIS ODU3_TCM4_OCI TD
ODU3_PM_DEG ODU3_TCM4_TIM TF
ODU3_PM_SSF ODU3_TCM5_DEG
TN11OAU1
NO_BD_PARA SPAN_LOSS_HIGH
TN11OBU1
BD_STATUS NO_BD_PARA SPAN_LOSS_HIGH
MUT_LOS PUM_TEM_ALM
NO_BD_PARA SPAN_LOSS_HIGH
TN11OBU2
BD_STATUS NO_BD_PARA SPAN_LOSS_HIGH
MUT_LOS PUM_TEM_ALM
CLIENT_PORT_STA_IN- NO_ELABEL
DI OLP_PS
TN12OLP
BD_STATUS NO_BD_PARA OLP_PS
INTRA_OTU_STA_INDI OCh_SSF_O
MUT_LOS OCh_SSF_P
POWER_FAIL
ODU1_TCM2_LTC ODU2_TCM3_DEG TD
ODU1_TCM3_AIS ODU2_TCM3_SSF TF
ODU1_TCM3_LCK ODU2_TCM4_BDI
NO_ELABEL OMS_SSF_O
NO_BD_SOFT OMS_SSF
OPA_FAIL_INDI
HARD_ERR OSC_LOS TF
HARD_ERR OSC_LOS TF
SUBRACK_ID_CON-
ALC_ADJUST_FAIL LCS_FILE_NOT_EXIST FLICT
TN51SCC
SUBRACK_ID_MIS-
ALC_ADJUST_FAIL LCS_FILE_NOT_EXIST MATCH
LCS_EXPIRED SUBRACK_ID_CONFLICT
TNK2SCC
SUBRACK_ID_CON-
ALC_ADJUST_FAIL LCS_FILE_NOT_EXIST FLICT
TN11SCC
SWDL_ACTIVATED_TI
ALC_ADJUST_FAIL NESF_LOST MEOUT
TN21SCC
SWDL_ACTIVATED_TI
ALC_ADJUST_FAIL LCS_FILE_NOT_EXIST MEOUT
TN22SCC
SWDL_AUTOMATCH_I
ALC_ADJUST_FAIL LCS_EXPIRED NH
OMS_BDI_P OMS_SSF
OMS_FDI OMS_SSF_O
OPA_FAIL_INDI OTS_LOS_O
OTS_BDI OTS_LOS_P
COMMUN_FAIL NO_ELABEL TD
HARD_ERR OSC_DEG TF
IN_PWR_LOW OUT_PWR_HIGH
LASER_MODULE_MIS- OUT_PWR_LOW
MATCH
HP_LOM OTU_LOF TF
HP_SLM PM_BEI
HP_LOM OTU_LOF TF
HP_SLM PM_BEI
HP_LOM OTU_LOF TF
HP_SLM PM_BEI
FSELECT_STG LSR_WILL_DIE TF
FSELECT_STG LSR_WILL_DIE TF
FSELECT_STG LSR_WILL_DIE TF
FSELECT_STG LSR_WILL_DIE TF
FSELECT_STG LSR_WILL_DIE TF
FSELECT_STG LSR_WILL_DIE TF
CLK_NO_TRACE_MOD SYN_BAD
E NO_BD_SOFT
HARD_ERR SYNC_F_M_SWITCH
DLAG_PROTECT_FAIL LAG_PORT_FAIL TD
ETHOAM_RMT_SD LOOP_ALM TF
ETH_CFM_MACSTATUS LSR_WILL_DIE
ETH_CFM_MISMERGE MULTI_RPL_OWNER
IN_PWR_HIGH ODU1_PM_DEG TD
LOOP_ALM ODU1_PM_SSF TF
LSR_INVALID OPU1_PLM
ODU2_PM_LCK ODU2_TCM5_AIS TD
ODU2_TCM1_AIS ODU2_TCM5_LTC TF
ODU2_TCM1_DEG ODU2_TCM5_SSF
ODU2_TCM1_LCK ODU2_TCM5_TIM
TN11TDX
B1_EXC LSR_COOL_ALM OPU1_VCAT_VcPLM
IN_PWR_HIGH ODU1_PM_EXC TD
LINK_ERR ODU1_PM_TIM TF
TN12TDX
B1_EXC LSR_COOL_ALM OPU2_PLM
IN_PWR_LOW ODU2_PM_LCK TD
LOCAL_FAULT ODU_SNCP_PS TF
ODU1_TCM2_SSF ODU2_TCM3_BDI TD
ODU1_TCM3_DEG ODU2_TCM3_OCI TF
ODU1_TCM3_OCI ODU2_TCM4_AIS
TN12TMX
ODU1_TCM2_OCI ODU2_TCM3_BDI TD
ODU1_TCM3_BDI ODU2_TCM3_OCI TF
ODU1_TCM3_LTC ODU2_TCM4_AIS
ODU1_TCM3_OCI ODU2_TCM4_BDI
IN_PWR_LOW ODU1_LOFLOM TD
LSR_INVALID ODU1_PM_LCK TF
ODU0_PM_AIS ODU1_TCM4_LTC TD
ODU0_PM_OCI ODU1_TCM5_AIS TF
ODU1_PM_AIS ODU1_TCM5_LCK
TN11TOM
B1_EXC ODU1_PM_OCI ODU1_TCM5_OCI
OCh_SSF_O ODU1_TCM4_SSF TD
ODU1_PM_BDI ODU1_TCM5_DEG TF
IN_PWR_HIGH ODU1_PM_DEG TD
LINK_ERR ODU1_PM_SSF TF
TN12TQM
B1_EXC ODU1_TCM1_LTC ODU1_TCM6_DEG
ODU1_PM_EXC ODU1_TCM5_BDI TD
ODU1_PM_TIM ODU1_TCM5_LTC TF
ODU1_TCM1_EXC ODU1_TCM6_AIS
ODU1_TCM1_LCK ODU1_TCM6_BDI
ODU1_PM_TIM ODU1_TCM5_BDI TD
ODU1_TCM1_EXC ODU1_TCM5_LTC TF
ODU1_TCM1_OCI ODU1_TCM5_TIM
ODU1_TCM1_SSF ODU1_TCM6_AIS
ODU2_PM_LCK ODU2_TCM5_AIS TD
ODU2_TCM1_AIS ODU2_TCM5_LTC TF
ODU2_TCM1_LCK ODU2_TCM5_TIM
ODU2_TCM1_LTC ODU2_TCM6_AIS
TN11TQX
B1_EXC LPT_ACTIVE OPU2_PLM
IN_PWR_HIGH ODU2_PM_LCK TD
LINK_ERR ODU_SNCP_PS TF
IN_PWR_HIGH ODU2_PM_SSF TD
LSR_COOL_ALM OPA_FAIL_INDI TF
TN53TSXL
B1_EXC ODU3_TCM2_AIS ODU3_TCM6_BDI
ODU3_TCM1_BDI ODU3_TCM5_DEG TD
ODU3_TCM1_OCI ODU3_TCM5_SSF TF
ODU3_TCM1_TIM ODU3_TCM5_EXC
ODU3_TCM1_EXC ODU3_TCM6_AIS
TN12VA1
HARD_ERR TEMP_OVER
TN12VA4
HARD_ERR TEMP_OVER
TN12WSD9/TN13WSD9
MUT_LOS OMS_SSF_O
OMS_BDI OMS_SSF_P
MODULE_ADJUST_FAI OPA_FAIL_INDI
L
TN12WSM9/TN13WSM9
MODULEFILE_UPDATE_FAI
BD_STATUS L TEMP_OVER
MUT_LOS OMS_SSF_O
OMS_BDI OMS_SSF_P
MUT_LOS OMS_SSF_O
OMS_BDI OMS_SSF_P
TN12WSMD4
TN12XCS
BD_STATUS HARD_ERR TEMP_OVER
HARD_BAD NO_ELABEL
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.
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 BOOTROM_BAD
See the alarm page according to the type of the board that reports the alarm.
3.4 BUS_ERR
See the alarm page according to the type of the board that reports the alarm.
3.5 CHAN_LOS
3.6 CLIENT_PORT_PS
3.7 COMMUN_FAIL
Refer to the alarm page according to the type of the board that reports the alarm.
3.8 ETH_8B10B_ERR
3.9 EX_ETHOAM_CC_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
3.10 FC_LINK_ERR
3.11 FC_SYNC_LOS
3.12 IN_PWR_HIGH
Refer to the alarm page according to the type of the board that reports the alarm.
3.13 IN_PWR_LOW
Refer to the alarm page according to the type of the board that reports the alarm.
3.14 INTRA_OTU_PS
3.15 LASER_MODULE_MISMATCH
3.16 LINK_ERR
Refer to the alarm page according to the type of the board that reports the alarm.
3.17 LOOP_ALM
Refer to the alarm page according to the type of the board that reports the alarm.
3.18 LPT_ACTIVE
3.19 LSR_WILL_DIE
3.20 MS_AIS
Refer to the alarm page according to the type of the board that reports the alarm.
3.21 MS_RDI
Refer to the alarm page according to the type of the board that reports the alarm.
3.22 MUT_LOS
3.23 OA_LOW_GAIN
3.24 ODU_SNCP_PS
3.25 ODUk_PM_AIS
3.26 ODUk_PM_BDI
3.27 ODUk_PM_DEG
3.28 ODUk_PM_EXC
3.29 ODUk_PM_SSF
3.30 OMS_FDI
3.31 OSC_LOS
3.32 OTS_LOS
3.33 OTUk_LOF
3.34 OTUk_SSF
3.35 OUT_PWR_HIGH
3.36 PORT_MODULE_OFFLINE
3.37 POWER_FAIL
3.38 PUMP_COOL_EXC
3.39 R_LOF
Refer to the alarm page according to the type of the board that reports the alarm.
3.40 R_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
3.41 R_OOF
Refer to the alarm page according to the type of the board that reports the alarm.
3.42 R_SLIP
3.43 REM_SF
3.44 REMOTE_FAULT
3.45 SECU_ALM
3.46 SUBRACK_ID_CONFLICT
3.47 SUM_INPWR_LOW
3.48 SWDL_NEPKGCHECK
3.49 TD
3.50 TEMP_OVER
3.51 TF
3.52 TS_CFG_MISMATCH
3.53 WRG_BD_TYPE
3.1 B1_EXC
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.1.2 B1_EXC (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
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
Parameters
None
Possible Causes
The possible causes of the B1_EXC alarm are as follows:
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 in the
Supporting Task.
l Cause 1: The line performance degrades.
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 of the Board 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,
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.
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.
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.
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.
l Cause 2: The external environment is abnormal.
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.
l Cause 3: The receive board of the local end is faulty.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: The transmit board of the opposite end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 of this alarm generated on the client side: The input signals on the client side contain
B1 bit errors.
l Cause 2 of this alarm generated on the client side: The board that reports this alarm is faulty.
l Cause 1 of this alarm generated on the WDM side: The receive side of the local station
(Station B) is faulty.
l Cause 2 of this 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 of this alarm generated on the WDM side: The transmit side of the opposite station
(Station A) is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
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
Station A Station B
l Cause 1 of this alarm generated on the client side: The input signals on the client side contain
B1 bit errors.
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 OTU1. If the
alarm on OTU1 persists, it indicates that the OTU1 hardware is faulty. In this case,
see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
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 B1 bit errors. In this case, rectify the fault on the client equipment.
l Cause 2 of 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.
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.
l Cause 1 of this alarm generated on the WDM side: The receive side of the local station
(Station B) is faulty.
1. Configure outloop at the transmit and receive optical interfaces on the WDM side of
OTU2. If there is no bit error alarm on the OTU1, it indicates that the board at the
local station (Station B) is faulty. Replace the faulty board.
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.
CAUTION
Configuring a loopback on the board interrupts the services on the board.
2. If OTU1 has bit error alarms, see the alarm handling procedure for cause 2 of this
alarm generated on the WDM side.
l Cause 2 of this 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, check the transmit optical power at the corresponding optical
interfaces on the opposite OTU1 on the U2000. For the optical power specification of
the specific board, refer to "Technical Specifications" of the Product Description.For
details, refer to "Querying Optical Power on the U2000" of the Supporting Tasks.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
2. If the transmit optical power of the corresponding optical interface on OTU1 is within
the normal range, check the attenuation of the transmission link between transmitting
module of OTU1 at the opposite station and the receiving module of OTU2 at the local
station. If the preset attenuation values are excessively large, correct them so that they
are within the normal range. For details, see "Adjusting, Replacing, Adding, and
Removing Attenuator" in the Supporting Tasks.
3. If the alarm persists, check the fiber connectors at stations A and B separately. If the
fiber connectors are dirty, clean or replace them. For details, refer to "Inspecting and
Cleaning the Fiber-Optic Connectors" of the Supporting Tasks.
4. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Supporting Tasks. If the fibers inside a station are
normal, check the optical cables between stations to rectify the fault.
5. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 of this alarm generated on the WDM side: The transmit side of the opposite station
(Station A) is faulty.
1. If the transmit optical power of the corresponding optical interface on OTU1 at the
opposite station is abnormal, it indicates that OTU1 is faulty. In this case, replace the
board.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.2 BEFFEC_EXC
Description
This alarm indicates that signals are degraded before FEC. Signals sent from WDM sides of the
opposite-end OTU 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 occurs when the counted bit error rate crosses the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-2 lists the fault symptom for the BEFFEC_EXC alarm.
The NE that reports this alarm reports a Cause 3 of this alarm in the case of multiple
temperature alarm or fan fault alarm, such as wavelengths: The external environment is
TEMP_OVER or FAN_FAIL, within a improper.
certain time.
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
The possible causes of the BEFFEC_EXC alarm are as follows:
l Cause 1 of this alarm in the case of a single wavelength: The input optical power of the
OTU board is extremely high or low.
l Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of
the interconnected OTUs are different.
l Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board
and the multiplexer/demultiplexer board is faulty.
l Cause 4 of this alarm in the case of a single wavelength: An inappropriate DCM is installed.
l Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm
is faulty.
l Cause 6 of this alarm in the case of a single wavelength: The board at the opposite station
is faulty.
l Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables
between stations or the multiplexing portions inside a station are faulty.
l Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals
during line transmission is excessively high.
l Cause 3 of this alarm in the case of multiple wavelengths: The external environment is
improper.
Procedure
1 Check the alarm information on the U2000 and record the IDs of the port and channel where the
alarm is generated.
2 Cause 1 of this alarm in the case of a single wavelength: The input optical power of the OTU
board is extremely high or low.
(1) Check whether the received optical power on the U2000 is within the normal range. For
the optical power specification of the specific board, refer to "Technical Specifications" of
the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards" of
the Hardware Description to obtain the manufacturing information of the optical module on the
board.
(2) If the input optical power is abnormal, see the methods for handling the IN_PWR_HIGH
and IN_PWR_LOW alarms.
(3) If the input optical power is normal but the alarm persists, see the alarm handling procedure
for cause 2 of this alarm in the case of a single wavelength.
3 Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of the
interconnected OTUs are different.
(1) On the U2000, check the settings of FEC mode of the two interconnected OTUs. If the
settings are different, change the settings to FEC or AFEC to ensure consistency. For details,
see "Setting the FEC Mode" in the Supporting Tasks.
(2) Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
for cause 3 of this alarm in the case of a single wavelength.
4 Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board and
the multiplexer/demultiplexer board is faulty.
(1) Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them.
For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting
Tasks.
(2) If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Supporting Tasks.
(3) Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
for cause 4 of this alarm in the case of a single wavelength.
5 Cause 4 of this alarm in the case of a single wavelength: TAn inappropriate DCM is installed.
(1) Check whether the DCM used on the existing network is appropriate. If not, replace the
DCM.
(2) Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
for cause 5 of this alarm in the case of a single wavelength.
6 Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm is
faulty.
(1) Replace the board that reports this alarm.
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 pluggable Replace the faulty board. For details, refer to
optical modules, "Replacing a Board" of the Supporting
Tasks.
(2) Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
for cause 6 of this alarm in the case of a single wavelength.
7 Cause 6 of this alarm in the case of a single wavelength: The board at the opposite station is
faulty.
(1) Replace the OTU board at the opposite station.
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 pluggable Replace the faulty board. For details, refer to
optical modules, "Replacing a Board" of the Supporting
Tasks.
(2) Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
8 Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables between
stations or the multiplexing portions inside a station are faulty.
(1) Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them.
For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting
Tasks.
(2) If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Supporting Tasks. If the fibers inside a station are normal,
check the optical cables between stations to rectify the fault.
(3) Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
for cause 2 of this alarm in the case of multiple wavelengths.
9 Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals during
line transmission is excessively high.
(1) Check the attenuation of the multiplexing portions inside a station and the line attenuation
between stations section by section. If the preset attenuation values are excessively large,
correct them so that they are within the normal range. For details, refer to "Adjusting,
Replacing, Adding and Removing Attenuator" of the Supporting Tasks.
(2) Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
for cause 3 of this alarm in the case of multiple wavelengths.
10 Cause 3 of this alarm in the case of multiple wavelengths: The external environment is improper.
(1) Check the ambient temperature inside the telecommunications room, the cleanliness of the
air filter, and the heat dissipation conditions of each fan. For details, see the procedure for
handling the TEMP_OVER alarm.
(2) Check whether the alarm is cleared. If the alarm persists, check whether external
electromagnetic interference exists. For example, whether there is external electronic
equipment, whether the power supply is instable, and whether the lightning electromagnetic
interference exists, or whether a high-voltage output cable generates electromagnetic
interference. If yes, take corresponding measures to withstand the electromagnetic
interference.
(3) Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases:
l MD-A13 Bit Error Alarm Is Generated When Optical Power Gets Close to the Threshold
l MC-A55 Improper DCM Distribution Causes Abnormal Service
l MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board
None.
3.3 BOOTROM_BAD
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.3.2 BOOTROM_BAD (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The BOOTROM_BAD (OCS) 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The possible causes of the BOOTROM_BAD alarm are as follows:
Procedure
1 View the BOOTROM_BAD alarm on the U2000 and determine the relevant board.
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
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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameters 1 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software.
0x02 indicates the extended BIOS software.
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 basic BIOS software of the board is damaged.
l Cause 2: The extended BIOS software of the board is damaged.
l Cause 3: The SCC board is faulty.
Procedure
l 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.
l Cause 1: The basic BIOS software of the board is damaged.
1. Replace the faulty SCC board. For details, refer to "Replacing the SCC Board" of the
Parts Replacement.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
l Cause 2: The extended BIOS software of the board is damaged.
1. Reload the extended BIOS of the SCC board. For details, see the Version Upgrade
Guide.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
NOTE
The BIOS detection interval is 24 hours. Therefore, the BOOTROM_BAD alarm is displayed
24 hours later if the alarm persists after you reload the extended BISO.
l Cause 3: The SCC board is faulty.
1. Replace the faulty SCC board. For details, refer to "Replacing the SCC Board" of the
Parts Replacement.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
----End
Related Information
None
3.4 BUS_ERR
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.4.2 BUS_ERR (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The BUS_ERR (OCS) is an alarm indicating the bus error. This alarm is generated when the
board detects a backplane bus error.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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 in the
Supporting Task.
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.
CAUTION
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 in the Installation Guide and Inserting Boards in the Installation Guide. Then,
check whether the alarm is cleared.
2. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
CAUTION
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.
CAUTION
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
Description
The BUS_ERR is an alarm indicating the bus error. This alarm is generated when the board
detects a backplane bus error.
Attribute
Alarm Severity Alarm Type
Critical Equipment
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 and 2 Indicates the ID of the bus in which the alarm is generated.
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: In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, 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 the Installation
Guide. In the case of the OptiX OSN 6800 equipment, see "Removing Boards" and
"Inserting Boards". In the case of the OptiX OSN 3800 equipment, see "Removing
Boards" and "Inserting Boards".In the case of the OptiX OSN 8800 equipment, see
"Removing Boards" and "Inserting Boards". .
2. Check whether the alarm is cleared. If the alarm persists, replace the board. For details,
see the Parts Replacement.
l Cause 2: In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, the cross-
connect board is inserted inappropriately or faulty.
1. Reseat the cross-connect board. For operations, see Removing Boards in the
Installation Guide and Inserting Boards in the 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.5 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
Alarm Severity Alarm Type
Parameters
None
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 wavelength that needs to be monitored is not received. For example, in the
following figure, λ1 wavelength needs to be monitored as configured, but actually λ1
wavelength is not accessed. The possible cause is that the fiber to the client or WDM side
of the OTU1 is connected.
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 optical power difference between the monitored wavelengths is excessively
large. (For example, the optical power difference between λ1 and λ2 is excessively large.)
l Cause 4: The attenuation of the multiplexer or OA unit interconnected with the MCA is
excessively high.
l Cause 5: The OTU board located before the MCA is faulty. For example, OTU1 in the
preceding figure is faulty.
l Cause 6: The MCA that reports the alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1: The wavelength that needs to be monitored is not received.
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 so that the fiber connection
is established properly.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
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.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The optical power difference between the monitored wavelengths is excessively
large.
1. Query whether the system is configured with the APE function. If yes, enable the APE
function to re-adjust the optical power of each wavelength. For detailed operations,
see "Automatic Power Equilibrium (APE)" in the Feature Description.
2. If the system is not configured with the APE function, manually enable the adjustment
of a single wavelength and adjust the optical power of the wavelength with excessively
large difference, ensuring that the optical power is flat.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The attenuation of the multiplexer or OA unit interconnected with the MCA is
excessively high.
1. Query the output optical power of the upstream OTU board connected to the
multiplexer unit. Check whether the output optical power of the upstream OTU board
is within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
2. Query the alarms reported by the MCA input optical power of the optical interface,
and then calculate the output optical power of the upstream multiplexer or OA unit to
determine whether it 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 extremely 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 very high, decrease the attenuation for 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. For details, see "MON Interface Optical Split
Ratio" in the Hardware Description.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: The OTU in the upstream direction of the MCA is faulty.
1. Replace the OTU that transmits the wavelength to the MCA.
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 the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 6.
l Cause 6: 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.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.6 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
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-5 lists the fault symptoms for the CLIENT_PORT_PS alarm.
A protection switching is performed, and the Cause 2: The services of the working channel
board on the working channel reports alarms of the client-side 1+1 protection group are
that can trigger a protection switching. For faulty. The current channel automatically
details about the alarm information, see switches to the working channel and the
Table 3-6. alarm is reported.
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: 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
l Cause 1: A user issues an external switching command such as forced switching or manual
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
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
1. Query whether the related boards for configuring the protection group have alarms
relevant to the services. If yes, handle the alarms by referring to the alarm handling
procedure. For details about the alarm information, see Table 3-6.
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.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Table 3-6 lists the alarms that can trigger a protection switching.
3.7 COMMUN_FAIL
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.7.2 COMMUN_FAIL (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
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 in the
Supporting Task.
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.
l Cause 2 of a single board reporting this alarm: The board is faulty.
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 in the Installation Guide and Inserting Boards in the
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 in the
Installation Guide and Inserting Boards in the 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
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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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 0x02 denotes RS485 path 2;
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.
0x00 0x06 denotes RS485 path 3;
0x00 0x07 denotes RS485 path 4;
Fault Symptom
Table 3-8 lists the fault symptom for the COMMUN_FAIL alarm.
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).
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 6800 and OptiX
0x00 0x03. l For OptiX OSN 6800 and OSN 3800: The AUX board
OptiX OSN 3800: The is faulty. For OptiX OSN
AUX board reports the 8800: The EFI1 or EFI2
BD_STATUS alarm. board is faulty.
l For OptiX OSN 8800:
The EFI1 or EFI2 board
reports the BD_STATUS
alarm.
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
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
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.
l Cause 3 of a single board reporting this alarm: The board is faulty.
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 6800 and OptiX OSN
3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
NOTE
When the ports on the AUX board for communicating with other boards are faulty, the services boards
report the COMMUN_FAIL alarm but the standby SCC board does not report this alarm.
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.
l Cause 3 of a single board reporting this alarm: The board is faulty.
1. Replace the board that reports the alarm. 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 6800 and OptiX OSN
3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty..
For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty.
1. Check whether the AUX board also reports alarms such as BD_STATUS, indicating
abnormal board status. Reseat the board. For the operation of reseating the board, see
the Installation Guide. In the case of the OptiX OSN 6800 equipment, see "Removing
Boards" and "Inserting Boards". In the case of the OptiX OSN 3800 equipment, see
"Removing Boards" and "Inserting Boards".
2. Check whether the alarm is cleared. If the alarm persists, replace the AUX board. For
details, refer to "Replacing the AUX 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.
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 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.
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.
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.
l Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
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 the Installation Guide. In the case of the OptiX OSN 6800
equipment, see "Removing Boards" and "Inserting Boards". In the case of the OptiX
OSN 3800 equipment, see "Removing Boards" and "Inserting Boards".In the case of
the OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting Boards".
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.8 ETH_8B10B_ERR
Description
This alarm indicates an Ethernet line signal encoding/decoding error. The alarm occurs when
signals are converted from 8bit mode to 10bit mode.
Reported from the WDM side or client side: Client side
Attribute
Alarm Severity Alarm Type
Parameters
None
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 fiber between the access equipment and the optical interface on the client side
of the board is faulty.
l Cause 2: The access equipment is faulty.
l Cause 3: The board hardware 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 input equipment and the
interface on the client side of the board is overlarge, and whether the fiber is aged or
loose. If that is the case, clean the fiber connector or replace the fiber.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The access equipment is faulty.
1. Apply a hardware loopback between the transmit and receive optical interfaces on the
client side of the board. If the alarm persists, it indicates that the board is faulty. In
this case, replace the board.
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. If the alarm is cleared, it indicates that the access equipment on the client side is faulty.
In this case, rectify the fault on the access equipment.
l Cause 3: The board hardware is faulty.
1. Replace the faulty board.
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.
Related Information
None.
3.9 EX_ETHOAM_CC_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.9.2 EX_ETHOAM_CC_LOS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The EX_ETHOAM_CC_LOS (OCS) 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
Alarm Severity Alarm Type
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
Name Meaning
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.
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
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 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.
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
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 of the time during which the CC message is transmitted from the source
maintenance point to the sink maintenance point), this alarm is generated.
Reported from the WDM side or client side: Client side
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 and 2 2 bytes, indicates the number of the Ethernet port where this alarm is
generated.
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
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
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) for the source and sink maintenance points, to locate the fault
in the services between the source maintenance point and the sink maintenance point.
4. Perform checks for the problem services, including software check, hardware check,
and traffic check. After the services restore, the alarm is automatically cleared. You
may perform LB to confirm that the alarm is cleared.
5. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.10 FC_LINK_ERR
Description
The FC_LINK_ERR alarm indicates an FC service link failure. This alarm occurs when the FC
link is faulty.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the status of the transmission link on the WDM side. It is used to identify
the link status on a transmission network.
l 0x00: means WAN_UP, indicating that the transmission link is normal.
l 0x01: means WAN_DOWN, indicating that the transmission link is faulty.
Fault Symptom
Table 3-10 lists the fault symptom for the FC_LINK_ERR alarm.
The WDM side of the opposite board may Cause 1: The WDM side of the opposite OTU
report an R_LOS, R_LOF, OTUk_LOF, reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. OTUk_LOM, or OTUk_AIS alarm. (The
value of parameter 1 is 0x01.)
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 WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
l Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow
control management mode occurs. (The value of parameter 2 is 0x01.)
l Cause 3: The type or the time sequence of the services on the board is configured
improperly.
l Cause 4: The type of the client-side optical module on the board mismatches the type of
the actual service, or the actual fiber mismatches the fiber type that the optical module
supports.
l Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).
l Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
Procedure
l Check the information of this alarm on the U2000. Record the parameters of this alarm.
l Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
1. On the U2000, check whether an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or
OTUk_AIS alarm is generated on the WDM side of the connected board. If yes, handle
the alarm properly.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow
control management mode occurs. (The value of parameter 2 is 0x01.).
1. Check the alarm parameters to see whether the ISL mode is incorrect, or the flow
control management mode mismatches. If yes, check the configuration of the client
equipment in the network.
2. Reconfigure the ISL mode and the traffic control management mode.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The type or the time sequence of the services on the board is configured
improperly.
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, change the service type
of the corresponding port on the board or replace the board with another board that
matches the service type. For details, refer to "Replacing a Board" of the Supporting
Tasks.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
2. 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.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The type of the client-side optical module on the board mismatches the type of
the actual service, or the actual fiber mismatches the fiber type that the optical module
supports.
1. Check whether the service type that the client-side optical module on the board is the
same with the actual service type. If not, replace the board or replace the optical module
if it is pluggable to ensure the optical module type matches the actual service type.
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. If the alarm persists, check whether the fiber type supported by the client-side optical
module is the same with the type of the connected fiber. If not, replace the board or
the fiber.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).
1. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
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. If the alarm persists, the OTU board at the opposite station may be faulty. In this case,
replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 6.
l Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
1. If the alarm persists, the client equipment may be faulty. In this case, rectify the fault
on the client equipment.
2. If the alarm persists, the client equipment at the opposite station may be faulty. In this
case, rectify the fault on the client equipment at the opposite station.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.11 FC_SYNC_LOS
Description
This alarm indicates a loss of the FC service synchronous word. This alarm is generated when
the FC service state fails to obtain the signal alignment word.
Attribute
Parameters
None
Fault Symptom
Table 3-11 lists the fault symptom for the FC_SYNC_LOS alarm.
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
The possible causes of the FC_SYNC_LOS alarm are as follows:
l Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
l Cause 2: The transmit optical power is abnormal.
Procedure
l Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
1. Check whether the rate that is configured on the U2000 of the services at the ports on
the local board matches the rate of the accessed services. If they are not matched, you
need to change the type of the accessed services or the type of the services on the
board according to the networking planning, to ensure that the rates of these services
are the same. The service type for an optical interface on the board can be set or queried
on the U2000. For details, refer to "Querying and Setting the Service Type on the
Client Side of a Board" of the Supporting Tasks.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The transmit optical power is abnormal.
1. On the U2000, 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 alarms to rectify the fault.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.12 IN_PWR_HIGH
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.12.2 IN_PWR_HIGH (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The IN_PWR_HIGH (OCS) 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
Alarm Severity Alarm Type
Parameters
None
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 Query current alarms on the U2000. For details, see Querying the Current Alarms 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
Information in the Supporting Task.
2. Check whether the threshold of the optical power is set properly. For the operations,
see Querying Optical Power of the Board 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 of the Board 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
of the Board 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.
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.
3. If the alarm persists, see other causes.
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
Replacement. Then, check whether the alarm is cleared.
3. If the alarm persists, replace the opposite board. For details, see Parts Replacement.
Then, check whether the alarm is cleared.
4. If the alarm persists, see other causes.
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
Information in the Supporting Task.
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.
3. If the alarm persists, see other causes.
----End
Related Information
None.
Description
This alarm indicates that the input optical power is excessively high. This 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
Alarm Severity Alarm Type
Parameters
None
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 for this alarm generated on the client side: The input optical power is excessively
high, and the attenuation configured is insufficient.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.
l Cause 2 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1 for this alarm generated on the client side: The input optical power is excessively
high, and the attenuation configured 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 specification of the specific board, refer to
"Technical Specifications" of 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 so that the input optical power is within the normal range.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
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 client side.
l Cause 2 for this alarm generated on the client side: The board that reports the alarm is 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.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
l Cause 1 for this alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.
1. If the alarm 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 specification of the specific board, refer to
"Technical Specifications" of the Product Description.. If the input optical power is
abnormal, query the input and output optical power of the board in the upstream
direction of the OTU in a reverse sequence of the signal flow on the U2000. If the
input and output optical power of the upstream board exceeds the normal range, adjust
the input optical power of the board to a proper value.
2. If the input optical power of the upstream boards is within the normal range, whereas
the output optical power is abnormal, the upstream board may be faulty. Replace the
board.
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.
3. 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 board that reports the alarm is
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.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
l If the alarm is generated in multiple wavelengths, the alarm handling method is similar to
the handling method for this alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
3.13 IN_PWR_LOW
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.13.2 IN_PWR_LOW (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The IN_PWR_LOW (OCS) 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
Alarm Severity Alarm Type
Parameters
None
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
the opposite board is faulty.
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
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
Information in the Supporting Task.
2. Check whether the threshold of the optical power is set properly. For the operations,
see Querying Optical Power of the Board 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.
3. If the alarm persists, see other causes.
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 of the Board 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
manufacturer information about the board optical module.
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
whether the alarm is cleared.
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.
Then, check whether the alarm is cleared.
6. If the alarm persists, see other causes.
l Cause of the board: The transmit power of the opposite station is excessively low because
the opposite board is faulty.
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
Replacement. Then, check whether the alarm is cleared.
3. If the alarm persists, replace the opposite board. For details, see Parts Replacement.
Then, check whether the alarm is cleared.
4. If the alarm persists, see other causes.
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
Information in the Supporting Task.
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.
3. If the alarm persists, see other causes.
----End
Related Information
None.
Description
This alarm indicates that the input optical power is excessively low. The alarm is generated when
the input optical power is smaller than the lower threshold of the input optical power.
Reported from the WDM side or client side: WDM side, client side.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
The possible causes of the IN_PWR_LOW alarm are as follows:
l Cause 1 for this alarm generated on the client side: The fiber connector is dirty, and the
fiber jumper is over-bent, damaged or aged.
l Cause 2 for this alarm generated on the client side: The attenuation of the attenuator attached
to the optical interface on the board that reports this alarm is excessively high.
l Cause 3 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this 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 this alarm generated on the WDM side: The attenuation of the attenuator
attached to the optical interface on the board that reports this alarm is excessively high.
l Cause 3 for this 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 this alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient.
l Cause 5 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1 for this 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 to
determine whether the input optical power is within the normal range. For details,
refer to "Testing Optical Power by Using an Optical Power Meter" of the Supporting
Tasks. For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks to obtain the
manufacturing information of the optical module on the board.
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, refer to "Inspecting
and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks.
3. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged
or aged, adjust the fiber jumper or replace the fiber jumper. For details, refer to
"Replacing Fiber Jumpers" in the Supporting Tasks.
4. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the client side.
l Cause 2 for this 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. For details, refer to "Adjusting, Replacing, Adding and Removing
Attenuator" of the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the client side.
l Cause 3 for this alarm generated on the client side: The board that reports the alarm is faulty.
1. If the alarm persists, replace the board that reports the alarm.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
l Cause 1 for this 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 details,
refer to "Testing Optical Power by Using an Optical Power Meter" of the Supporting
Tasks. For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks to obtain the
manufacturing information of the optical module on the board.
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, refer to "Inspecting
and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks.
3. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged
or aged, adjust the fiber jumper or replace the fiber jumper. For details, refer to
"Replacing Fiber Jumpers" in the Supporting Tasks.
4. 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 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. For details, refer to "Adjusting, Replacing, Adding and Removing
Attenuator" of the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 for this 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 closed, open it on
the U2000. For details, refer to "Opening/Closing Lasers" in the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, check whether the optical
attenuator with excessively high attenuation is attached to the transmit optical
interface on the board at the opposite station. If yes, decrease the attenuation to a
proper value or replace the optical attenuator so that the output optical power of the
opposite board is normal. For details, refer to "Adjusting, Replacing, Adding and
Removing Attenuator" of the Supporting Tasks.
3. Check whether the alarm is cleared. If the alarm persists, check the output optical
power performance values and alarms of the board. If the reported alarms or
performance values are different from the specification values, see the corresponding
handling procedure for the alarms or performance events to rectify the fault.
4. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4 of this alarm generated on the WDM side.
l Cause 4 for this alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient.
1. Query the input and output optical power of the boards in the upstream direction 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. For details, refer to "Adjusting, Replacing,
Adding and Removing Attenuator" of the Supporting Tasks.
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, troubleshoot the faults
at the upstream station so that the output optical power is normal.
5. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5 of this alarm generated on the WDM side.
l Cause 5 for this alarm generated on the WDM side: The board that reports the alarm is
faulty.
1. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
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.
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
Related Cases:
l MC-A19 Use Power Monitoring To Process Problems On Wavelength Division
l MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
l MC-A66 The Received Optical Power of Downstream Stations Is not Flat
l MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
None.
3.14 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.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-14 lists the fault symptoms for the INTRA_OTU_PS alarm.
A protection switching is performed, and the Cause 2: The services of the working channel
board on the working channel reports alarms of the intra-board 1+1 protection group are
that can trigger a protection switching. For faulty. The current channel automatically
details about the alarm information, see switches to the working channel and the
Table 3-15. alarm is reported.
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: A user issues an external switching command such as forced switching or manual
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
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
Procedure
l Cause 1: A user issues an external switching command such as forced switching or manual
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 intra-board 1+1 protection group are
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
1. Query whether the related boards for configuring the protection group have alarms
relevant to the services. If yes, handle the alarms by referring to the alarm handling
procedure. For details about the alarm information, see Table 3-15.
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.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Table 3-15 lists the alarms that can trigger a protection switching.
3.15 LASER_MODULE_MISMATCH
Description
This alarm indicates a mismatch of the optical module type and the fiber type. This alarm is
generated when the type of the optical module mismatches the type of the board.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
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
The possible cause of the LASER_MODULE_MISMATCH alarm is as follows:
l Cause 1: The optical interface type supported by the physical board does not match the type
of the optical module inserted into the optical interface.
Procedure
l Cause 1: The optical interface type supported by the physical board does not match the type
of the optical module inserted into the optical interface.
1. Check whether the optical module inserted into the optical interface matches the type
of the optical interface. For details, see "Quick Reference Table of the Units" in the
Hardware Description.
2. If not, replace the optical module with another one of the right type. For details, see
"Replacing the Pluggable Optical Module" in the Parts Replacement.
3. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.16 LINK_ERR
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.16.2 LINK_ERR (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The LINK_ERR (OCS) alarm indicates incorrect data link. This alarm is generated when the
Ethernet connection is incorrect and the port negotiation fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
1 View the LINK_ERR alarm on the U2000 to confirm the relevant board. Confirm the specific
port ID of the board.
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.
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.
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.
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
Description
This alarm indicates a link error. This alarm is generated when the link status of the Ethernet
data port is down.
Reported from the WDM side or client side: Client side
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-17 lists the fault symptom for the LINK_ERR alarm.
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 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 low.
l Cause 4: The fiber or cable that connects the two Ethernet ports fails.
l Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Hence, the types of fibers that the two optical modules can be connected to
are inconsistent.
l Cause 6: The data equipment on the client side is faulty.
l Cause 7: The board that reports this alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm 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, change the service type
of the corresponding port on the board or replace the board with another board that
matches the service type. For details, refer to "Replacing a Board" of the Supporting
Tasks.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
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. For details, see "Querying
and Setting the Working Mode of the Ethernet Board" in the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or low.
1. Check whether the input optical power of the two interconnected Ethernet ports is
within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
2. If the input optical power is abnormal, see the handling procedures for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The fiber or cable that connects the two Ethernet ports fails.
1. Check whether the fiber or cable that connects the two Ethernet ports are properly
connected. If they are not properly connected, reconnect or replace the fiber or cable.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Hence, the types of fibers that the two optical modules can be connected to
are inconsistent.
1. Check whether the types of fibers that the two optical modules can be connected to
are consistent. If they are inconsistent, replace the fiber or either board to make the
type of the two optical modules match the fiber type.
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. If the alarm persists, check whether the optical module types of the two interconnected
boards match the type of the fiber that connects the two boards. If not, replace the
board whose optical module type does not match the fiber board.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 6.
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.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
l MC-A102 The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS
Alarm
l MC-A128 EPL Service was interrupted due to a service mode mismatch of L4G boards
l MC-A165 LINK_ERR Occurs Due to an Optical Module Fault on the TQX Board
None.
3.17 LOOP_ALM
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.17.2 LOOP_ALM (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The LOOP_ALM (OCS) 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
Procedure
1 After you manually cancel the loopback configuration, the LOOP_ALM alarm is automatically
cleared.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 and 2 Indicates the optical interface where this alarm is generated. For example,
0x00 0x01 indicates optical interface 1.
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
The possible cause of the LOOP_ALM alarm is as follows:
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm 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. For details, refer to "Performing Inloop
and Outloop" of the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.18 LPT_ACTIVE
Description
This alarm indicates that the LPT switching is active. The data equipment itself has protection
scheme. 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 in 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.
Fault Symptom
Table 3-19 lists the fault symptoms for the LPT_ACTIVE alarm.
The R_LOS, LINK_ERR or L_SYNC alarm Cause 1: The input signals on the client side
may be generated on the client side of the are missing or the local board detects a
board. LINK_ERR or L_SYNC alarm.
An R_LOF alarm may be generated on the Cause 4: When the WDM equipment
WDM side. accesses data services and the SDH frames
are transmitted on the WDM side, this alarm
may be triggered by the R_LOS or R_LOF
alarm on the WDM side.
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 input signals on the client side are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
l Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
l Cause 3: When the WDM equipment accesses data services and the OTN frames are
transmitted on the WDM side, this 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 WDM side.
l Cause 4: When the WDM equipment accesses data services and the SDH frames are
transmitted on the WDM side, this alarm may be triggered by the R_LOS or R_LOF alarm
on the WDM side.
l Cause 5: Regarding to separation of the tributary board from the line board, if the cross-
connection configuration does not exist, the alarm is generated.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Check whether the service type accessed by the WDM equipment and the frame format
transmitted on the WDM side is consistent with that of the service configuration model by
using the U2000. If they are not consistent, configure them to ensure the consistency.
l Cause 1: The input signals on the client side are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
1. Check whether the R_LOS, LINK_ERR or L_SYNC alarms are generated on the
client side. If that is the case, clear the R_LOS, LINK_ERR or L_SYNCalarm.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
1. Check whether an REM_SF alarm is generated on the client side. If that is the case,
clear the REM_SF alarm.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: When the WDM equipment accesses the data services and the OTN frames are
transmitted on the WDM 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 WDM side.
1. If the frames on the WDM side are transmitted in the OTN format, check 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 alarms. If yes, clear the alarms.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: When the WDM equipment accesses the data services and the SDH frames are
transmitted on the WDM side, the alarm may be triggered by the R_LOS or R_LOF alarm
on the WDM side.
1. If the frames on the WDM side are transmitted in the SDH format, check the R_LOS
or R_LOF alarm information on the U2000 and clear the alarm.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: Regarding to separation of the tributary board from the line board, if the cross-
connection configuration does not exist, the alarm is generated.
1. Check the trails of the cross-connect services according to the board that reports the
alarm. Regarding to separation of the tributary board from the line board, check
whether the cross-connection is configured on the U2000. If not, configure the cross-
connection.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.19 LSR_WILL_DIE
Description
This alarm indicates that the laser will be out of work.
Reported from the WDM side or client side: WDM side, client side.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
The possible causes of the LSR_WILL_DIE alarm are as follows:
Cause 1: The laser is aging. 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 aging. The service life of the laser would be terminated.
1. Check whether the board that reports this alarm supports pluggable optical modules.
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 board. For details, refer to
pluggable optical modules, "Replacing a Board" of the Supporting
Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The detection circuit of the board is faulty.
1. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.20 MS_AIS
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.20.2 MS_AIS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The MS_AIS (OCS) 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the MS_AIS alarm are as follows:
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 in the
Supporting Task.
l Cause 1: The receive board at the local station is faulty.
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 in the Installation
Guide and Inserting Boards in the Installation Guide. Then, check whether the alarm
is cleared.
CAUTION
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
Replacement. Then, check whether the alarm is cleared.
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 Inserting Boards in the Installation Guide. Then, check
whether the alarm is cleared.
3. If the alarm persists, replace the cross-connect board. For details, see Parts
Replacement. Then, check whether the alarm is cleared.
4. If the alarm persists, see cause 3.
l Cause 3: The transmit board at the opposite station is faulty.
1. If the alarm persists, replace the opposite board. For details, see Parts Replacement.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 input signals from the client side contain the MS_AIS signal, as shown in
the following figure.
Detects and
reports the
MS_AIS alarm
The client signals O O
A F F A
contain the OTU1
D I I D OTU2
MS_AIS signal U U
M M
Client WDM WDM Client
side side side side
Station A Station B
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1 : The input signals from the client side contain the MS_AIS signal
1. Apply a hardware loopback between the transmit and receive optical interfaces on the
client side of OTU1. If the alarm on OTU1 persists, it indicates that OTU1 is faulty.
In this case, see the alarm handling procedure for cause 2.
2. If the alarm is cleared, it indicates that the input signals on the client side contain bit
errors. In this case, rectify the fault on the client equipment.
l Cause 2: The board that reports the alarm is faulty.
1. If the alarm persists, the board that reports the alarm is faulty. Replace the board.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.21 MS_RDI
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.21.2 MS_RDI (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The MS_RDI (OCS) 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
Alarm Severity Alarm Type
Parameters
None
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 Query current alarms on the U2000. For details, see Querying the Current Alarms in the
Supporting Task.
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 in the Installation Guide and
Inserting Boards in the Installation Guide. Then, check whether the alarm is cleared.
CAUTION
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 transmit board at the local station. For details, see
Parts Replacement. Then, check whether the alarm is cleared.
3. If the alarm persists, see cause 3.
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 in the Installation Guide
and Inserting Boards in the Installation Guide. Then, check whether the alarm is
cleared.
CAUTION
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 receive board at the opposite station. For details, see
Parts Replacement.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-22 lists the fault symptom for the MS_RDI alarm.
The board at the opposite station reports an Cause 1 for this alarm generated on the WDM
R_LOS, R_LOF, or MS_AIS alarm. side: The receiver on the WDM side at the
opposite station detects a signal failure.
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 for this 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
at the local station A contain the MS_RDI signals. The OTU of the station A reports the
MS_RDI alarm on the client side after it detects the MS_RDI signals.
Client O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
l Cause 1 for this alarm generated on the WDM side: The receiver on the WDM side at the
opposite station detects a signal failure. (For example, an R_LOS, R_LOF, or the 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 the 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
l Cause 2 for this alarm generated on the WDM side: The board that reports the alarm is
faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1 for this 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, rectify the fault on the client
equipment connected to the OTU board. For details, see the related manual of the
client equipment.
l Cause 1 for the alarm generate on the WDM side: The receiver on the WDM side at the
opposite station detects a signal failure (for example, an R_LOS, R_LOF or the MS_AIS
alarm is generated).
1. Query the alarm of the board at the opposition station by using the U2000. If and
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.
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 board that reports the alarm is
faulty.
1. If the alarm persists, the board at the local station is faulty. Consider whether to replace
the faulty board according to the actual situation (for example, whether replacing the
board affects the services).
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.22 MUT_LOS
Description
This alarm indicates a loss of multiplexed signals. This alarm is generated when the input
multiplexed signals of the board are lost.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-23 lists the fault symptom for the MUT_LOS alarm.
The optical interfaces on the board that Cause 1: Certain optical interfaces on the
reports this alarm are disconnected. board that reports this alarm are disconnected
or the fibers connected to the optical
interfaces are damaged.
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: 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 during line transmission is excessively high.
l Cause 3: The board that reports the alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l On the U2000, check whether the boards on the multiplexing link in the upstream direction
report this alarm along the reverse direction of the signal flow.
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 or incorrectly connected. If
yes, connect the input optical fibers to the specific optical interface.
2. Check whether the fibers or fiber connectors on the board that reports this alarm are
dirty. If yes, see Checking Fiber Jumpers by Using an Optical Power Meter or
Replacing Fiber Jumpers to rectify the fault.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The attenuation of signals during 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
Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
2. If the receive optical power is excessively low, check whether an optical attenuator
with excessively high attenuation is attached to the receive optical interface on the
board. If yes, decrease the attenuation of the optical attenuator to a proper value or
replace the optical attenuator with a proper one.
3. If the alarm persists, check whether the attenuation of the built-in VOA in the upstream
board is excessively high. If yes, adjust the attenuation of the VOA to a proper value.
4. Check whether the alarm is cleared. If the alarm persists, the optical cables between
stations may be faulty. In this case, rectify the fault on the optical cables.
5. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports the alarm is faulty.
1. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
l MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
l MC-A151 OWSP Protection Switching Fails Due to Incorrect Connection of Fiber Jumpers
on the DCP Boards
l MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper
None.
3.23 OA_LOW_GAIN
Description
This alarm indicates that the gain of an optical amplifier is low. The alarm is generated when
the actual gain of the optical amplifier board is 3 dB lower than the standard gain.
Attribute
Alarm Severity Alarm Type
Parameters
None
l If the alarm is generated because the input optical power is excessively high, the redundancy
of the system decreases, which affects the subsequent capacity expansion.
l If the alarm is caused by other factors (for example, excessive insertion loss between the
TDC and RDC optical interfaces on an OAU board), the input optical power of the
downstream signals and the redundancy of the system decrease. The services may have bit
errors or even be interrupted.
Fault Symptom
Table 3-24 lists the fault symptom for the OA_LOW_GAIN alarm.
The OAU board that reports this alarm also Cause 1: The input optical power of the OAU
reports a power high alarm, such as board is excessively high.
SUM_INPWR_HI.
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
The possible causes of the OA_LOW_GAIN alarm are as follows:
Procedure
l Cause 1: The input optical power of the board is excessively high.
1. On the U2000, check whether the receive optical power 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.
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. For details, refer to "Adjusting, Replacing, Adding and
Removing Attenuator" of the Supporting Tasks.
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.
For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the
Supporting Tasks.
4. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The insertion loss between the TDC and RDC optical interfaces is excessively
high. (This cause is applicable only to the OAU board.)
1. On the U2000, check 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. For details, refer to "Querying the Insertion Loss Between the TDC and
RDC Optical Interfaces on the OAU board" in the Supporting Tasks.
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 excessive, clean the fiber jumper and fiber connector between
the TDC and RDC optical interfaces. For details, refer to "Inspecting and Cleaning
the Fiber-Optic Connectors" in the Supporting Tasks. For the insertion loss
specification, see the Product Description. For the optical power specification of the
specific board, refer to "Technical Specifications" of the Product Description.
3. Check whether the alarm is cleared. If the alarm persists, replace the DCM module
between the TDC and RDC optical interfaces. For details, see "Replacing the DCM"
in the Supporting Tasks.
4. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports the alarm is faulty.
1. Replace the faulty board.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.24 ODU_SNCP_PS
Description
The ODU_SNCP_PS alarm indicates the ODU SNCP protection switching. This alarm occurs
when the ODU SNCP protection group actuates switching in which the current channel switches
to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-25 lists the fault symptoms for the ODU_SNCP_PS alarm.
A protection switching is performed, and the Cause 2: The services of the working channel
board on the working channel reports alarms of the ODU SNCP protection group are
that can trigger a protection switching. For faulty. The current channel automatically
details about the alarm information, see switches to the working channel and the
Table 3-26. alarm is reported.
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: A user issues an external switching command such as forced switching or manual
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
l Cause 1: A user issues an external switching command such as forced switching or manual
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 ODU SNCP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
1. Query whether the related boards for configuring the protection group have alarms
relevant to the services. If that is the case, handle the alarms by referring to the
corresponding handling procedure of the alarms. For details about the alarm
information, see Table 3-26.
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.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Table 3-26 lists the alarms that can trigger a protection switching.
OTUk_DEG ODUk_PM_EXC
3.25 ODUk_PM_AIS
Description
This alarm is an ODUk PM alarm indication signal. An AIS signal from the downstream station
indicates that a signal failure is detected at the upstream station.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-27 lists the fault symptoms for the ODUk_PM_AIS alarm.
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
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
The possible causes of the ODUk_PM_AIS alarm are as follows:
l Cause 1 for this alarm generated on the client side: Signals input from the client side contain
ODUk_PM_AIS signal.
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.
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.
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
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1 for this alarm generated on the client side: Signals input from the client side contain
ODUk_PM_AIS 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 OTU1. If the
alarm on OTU1 persists, it indicates that the OTU1 hardware is faulty. In this case,
see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
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.
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.
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.26 ODUk_PM_BDI
Description
This alarm is an ODUk PM backward defect indication. This alarm is generated when the PM
section at the opposite station detects a signal failure and inserts a BDI alarm to the local station.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
Fault Symptom
Table 3-28 lists the fault symptom for the ODUk_PM_BDI alarm.
The board at the opposite station reports an Cause 1 for this alarm generated on the WDM
R_LOS, OTUk_LOF, OTUk_LOM, side: The WDM side of the corresponding
ODUk_PM_LCK, ODUk_PM_OCI, board at the opposite station reports an
ODUk_PM_TIM, or ODUk_PM_SSF alarm. R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI,
ODUk_PM_TIM, or ODUk_PM_SSF alarm
and inserts an ODUk_PM_BDI back to the
local station (station A).
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 for this alarm generated on the client side: Signals input from the client side contain
an ODUk_PM_BDI signal.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding
board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and
inserts an ODUk_PM_BDI back to the local station (station A).
O WDM O
Client T WDM T Client
side side side side
U U
Station A Station B
Detects and reports the Sends the
ODUk_PM_BDI alarm ODUk_PM_BDI signal
back
Procedure
l On the U2000, check whether there is an alarm with higher severity on the board. If yes,
handle the alarm properly.
l Cause 1 for this alarm generated on the client side: Signals input from the client side contain
an ODUk_PM_BDI 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 OTU board.
If this alarm 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.
CAUTION
A loopback on the board interrupts the existing services.
2. If this 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 this alarm is
faulty.
1. Check whether the board that reports this alarm supports pluggable optical modules.
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.
l Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding
board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and
inserts an ODUk_PM_BDI back to the local station.
1. If this alarm is reported from the WDM side, check whether the corresponding OTU
board at the opposite station receives an R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm
by using the U2000. If yes, handle the corresponding alarm at the opposite station.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709
3.27 ODUk_PM_DEG
Description
This alarm indicates that the ODUk PM 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.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-29 lists the fault symptom for the ODUk_PM_DEG alarm.
The OTU board at the local station may report Cause 1: The input optical power of the OTU
an IN_PWR_LOW, IN_PWR_HIGH, or a is abnormal.
BEFFEC_EXC alarm.
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
The possible causes of the ODUk_PM_DEG alarm are as follows:
Procedure
l Cause 1: The input optical power of the OTU board is abnormal.
1. On the U2000, view the alarms of the entire network to confirm the slot ID, interface
ID, and channel ID of the board that generates this alarm.
2. Along the service signal flow, check whether the input optical power of the point that
first generates this 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. For details, refer to "Adjusting, Replacing, Adding and
Removing Attenuator" of the Supporting Tasks.
4. Check whether the alarm is cleared. If the alarm persists, troubleshoot this alarm
station by station along the service signal flow.
5. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The fiber on the transmission line is abnormal.
1. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace
them. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of
the Supporting Tasks.
2. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Supporting Tasks.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports the alarm is faulty or the corresponding board at the opposite
station is faulty.
1. If the alarm persists, replace the board that reports the alarm.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709
3.28 ODUk_PM_EXC
Description
This alarm indicates that the BIP8 error count on the ODUk PM section exceeds the threshold.
This alarm is generated when the BIP8 detection is in poisson mode and bit error count exceeds
the threshold.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
Fault Symptom
Table 3-30 lists the fault symptoms for the ODUk_PM_EXC alarm.
The OTU board at the local station may report Cause 1: The attenuation of the received
an IN_PWR_LOW alarm. signals is rather large, and the fiber
transmission line is abnormal.
The OTU board at the opposite station may Cause 1: The attenuation of the received
report an OUT_PWR_LOW alarm. signals is rather large, and the fiber
transmission line is abnormal.
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 attenuation of the received signals is rather large, and the fiber transmission
line is abnormal.
l Cause 2: The transmitter of OTU board at the opposite station is faulty.
l Cause 3: The receiver of the OTU board at local station is faulty.
Procedure
l Cause 1: The attenuation of the received signals is rather large, and the fiber transmission
line is abnormal.
1. On the U2000, check whether the receive optical power is within the normal range.
For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description.For details, refer to "Querying Optical
Power on the U2000" of the Supporting Tasks.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the OTU board.
2. If the receive optical power of the OTU 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 launched optical power at the corresponding
optical interface on the upstream 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. If the launched optical power of the OTU
board at the upstream station is excessively low, clear the alarm according to the
handling procedure of the OUT_PWR_LOW alarm.
4. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The transmitter of the OTU board at the opposite station is faulty.
1. Apply a hardware loopback between the transmit and receive optical interfaces on the
WDM side of the OTU board at the upstream station. If the alarm persists, it indicates
that the transmitter on the OTU board of the opposite station is faulty. In this case,
replace the OTU board.
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. If the alarm persists, see the alarm handling procedure for cause 3.
l Cause 3: The receiver of the OTU board at local station is faulty.
1. If the alarm persists, replace the faulty board at the local station.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709
3.29 ODUk_PM_SSF
Description
The ODUk_PM_SSF is an alarm indicating signal failure at the ODUk PM layer.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-31 lists the fault symptom for the ODUk_PM_SSF alarm.
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
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 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
the alarm is generated.
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.
The OTU2 board reports the Handle these alarms in advance. That is,
preceding alarms, clear these alarms according to the
corresponding methods.
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.
The line board at station C reports Handle these alarms in advance. That is,
the preceding alarms, clear these alarms according to the
corresponding methods.
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.
The OTU2 board at station B reports Handle these alarms in advance. That is,
the preceding alarms, clear these alarms according to the
corresponding methods.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 3.
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.
2. Check whether the alarm is cleared. If the alarm persists, see cause 4.
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.
The line board at the station reports Handle these alarms in advance. That is,
the preceding alarms, clear these alarms according to the
corresponding methods.
The line board at the station does not Contact Huawei engineers.
report the preceding alarms,
----End
Related Information
None
3.30 OMS_FDI
Description
This 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 loss of signal 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.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Fault Symptom
Table 3-32 lists the fault symptom for the OMS_FDI alarm.
The board at the opposite station reports an Cause 2: At the upstream station, a fiber cut
OTS_LOS or OTS_TIM alarm. occurs or the optical power is excessively
low. Thus, the loss of signal alarm is detected
at the downstream station, and an OMS_FDI
alarm is then inserted to the downstream
station.
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
The possible causes of the OMS_FDI alarm are as follows:
l Cause 1: The logical fiber connections are inconsistent with the physical fiber connections.
l Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low.
Thus, the loss of signal alarm is detected at the downstream station, and the OMS_FDI is
then inserted to the downstream station.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1: The logical fiber connections are inconsistent with the physical fiber connections.
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. For details, see "Checking Logical
Fibers" in the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low.
Thus, the loss of signal alarm is detected at the downstream station, and then the OMS_FDI
is inserted to the downstream station.
1. Check whether an OTS_LOS or OTS_TIM alarm is generated at the opposite station
and all upstream stations. If yes, troubleshoot the OTS_LOS or OTS_TIM alarm
according to the alarm handling procedure.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.31 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: A certain optical interface on the board that reports the alarm is not connected to
a fiber.
l Cause 2: The laser of the board at the opposite station is shut down.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs
on the transmission line.
l Cause 4: The transmit part of the opposite station is faulty.
l Cause 5: The receive part of the local station is faulty.
Procedure
l Query the alarm on the U2000 and record the IDs of the optical interface and channel where
the alarm is generated.
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.
l Cause 2: The laser of the board at the opposite station is shut down.
1. Use the U2000 to check whether the laser of the specific board at the opposite station
is on. 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.
l Cause 4: The transmit part of the opposite station is faulty.
1. If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board"
of the Supporting Tasks.
Related Information
None.
3.32 OTS_LOS
Description
The OTS_LOS alarm indicates a loss of signal at the 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.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
Procedure
l Check the alarm information on the U2000 and record the IDs of the optical interface and
channel where the alarm is generated.
l Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
1. Check whether the logical fiber connections of the FIU are consistent with the physical
fiber connections. If not, modify the configuration of the logical fiber connections so
that logical fiber connections are consistent with the physical fiber connections.
2. Check and make sure that the fiber connection between the "IN" interface on the local
FIU and the opposite station is correct and reliable.
3. If the alarm persists, check whether the attenuation of the "IN" interface on 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 optical interfaces
on the FIU are correct and reliable.
----End
Related Information
None.
3.33 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
Fault Symptom
Table 3-33 lists the fault symptom for the TEMP_OVER alarm.
Two boards at two ends of a single Cause 1: The settings of the service type or
wavelength report the OTUk_LOF alarm in FEC type are incorrect.
the deployment.
A single board at one end reports the Cause 3: The receive optical power or the
OTUk_LOF alarm in the deployment. In OSNR of the local board is abnormal.
addition, the alarm indicating abnormal
optical power is reported.
Multiple boards on the same link report the Cause 6: The dispersion compensation value
OTUk_LOF alarm in the deployment. is excessively great or small.
A single board at one end reports the Cause 2: The board that reports the alarm is
OTUk_LOF alarm in the deployment. faulty.
A board reports the OTUk_LOF alarm during Cause 2: The board that reports the alarm is
normal operation after deployment. faulty.
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 settings of the service type or FEC type are incorrect.
l Cause 2: The board that reports the alarm is faulty.
l Cause 3: The receive optical power or the OSNR of the local board is abnormal.
l Cause 4: The signals transmitted by the corresponding board at the opposite end do not
have a frame structure.
l Cause 5: The fiber of the transmission line is abnormal.
l Cause 6: The dispersion compensation value is excessively great or small.
Procedure
l Cause 1: The settings of the service type or FEC type are incorrect.
1. Query the FEC type on the U2000 to check whether the set FEC type is the same as
the FEC type supported by the board. For the specific service types and FEC types,
see the Hardware Description. If the FEC type is different from the FEC type
supported by the board, reset the FEC type to the same as the FEC type supported by
the board. For details about the operation, see Setting the FEC Type in the Supporting
Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see cause 2.
l Cause 2: The board that reports the alarm is faulty.
1. See Performing Hardware Loopback to perform the relevant operation on the optical
interface where the alarm is reported. Then check whether the alarm is cleared.
2. If the alarm persists, replace the board.
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.
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 the alarm is cleared. If the alarm persists, see cause 5.
l Cause 5: 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 inserted.
– The fiber connector is clean.
– The cable is intact.
If the preceding requirements are not met, clean the fiber connector or replace the
fiber. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of
the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see cause 6.
l Cause 6: The dispersion compensation value is excessively great or small.
1. If the alarm persists, replace the DCM module. For details about the operations, see
Replacing a DCM in the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
----End
Related Information
ITU-T G.709
3.34 OTUk_SSF
Description
The OTUk_SSF is an alarm that the signal fails at the OTUk server layer.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-34 lists the fault symptom for the OTUk_SSF alarm.
A station may report the R_LOS, Cause 1: The station reports the R_LOS alarm
ODUk_PM_SSF alarm at the same time. and the OTUk_SSF alarm at the same time.
A station may report the OTUk_AIS, Cause 2: The station reports the OTUk_AIS,
OTUk_LOF, or OTUk_LOM alarm at the OTUk_LOF, or OTUk_LOM alarm and the
same time. ODUk_PM_SSF alarm at the same time.
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 station reports the R_LOS alarm and the OTUk_SSF alarm at the same time.
As shown in the following figure, the client side (the client side accesses the OTU service)
in the receive direction of the OTU1 board at station A or the WDM side in the receive
direction of the OTU2 board at station B reports the R_LOS alarm.
M M
O U OA U
OA O
T X/ F F X/
U D I T
I D
1 M U U
U M
U OA OA 2
Client WDM U
Client
side side X X WDM
side side
Station A Station B
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
ODUk_PM_SSF alarm at the same time.
Procedure
l Cause 1: The station reports the R_LOS alarm and the OTUk_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, for example, the OTU1
board at station A or the OTU2 board at station B in the figure.
2. Check whether the R_LOS alarm is reported in the receive direction of the OTU board
at the station.
The OTU board reports the Handle the alarm in advance. That is, clear
preceding alarm, the alarm according to the corresponding
method.
l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm 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, for example, the OTU1
board at station A or the OTU2 board at station B in the figure.
2. Check whether the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm is reported in the
receive direction of the OTU board at the station.
The OTU board reports the Handle the alarm in advance. That is, clear
preceding alarm, the alarm according to the corresponding
method.
The OTU board does not report the Contact Huawei engineers.
preceding alarm,
----End
Related Information
None
3.35 OUT_PWR_HIGH
Description
This alarm indicates that the output optical power is very high. This alarm is generated when
the laser output optical power exceeds the upper threshold.
Reported from the WDM or client side: WDM side, client side.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
Cause 1: The optical module of laser is faulty or the board is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the optical interface and
channel where the alarm is generated.
l Cause 1: The optical module of laser is faulty or the board is faulty.
1. Check whether the board that reports this alarm supports pluggable optical modules.
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 supports Replace the faulty board. For details, refer
pluggable optical modules, to "Replacing a Board" of the Supporting
Tasks.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.36 PORT_MODULE_OFFLINE
Description
This alarm indicates that the optical module on an optical interface is offline. This alarm is
generated when the board detects that an optical module is offline.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
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 optical module does not exist or is not correctly inserted in the optical
interface.
l Cause 2: The optical module or the board is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1: The optical module does not exist or is not correctly inserted in the slot.
1. Check whether the optical interface where this alarm is generated has an optical
module.
The optical interface has no optical Insert an optical module into the optical
module. interface properly.
The optical interface has an optical See the alarm handling procedure for
module. cause 2.
----End
Related Information
None.
3.37 POWER_FAIL
Description
This alarm indicates a 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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.
– If the active power supply fails but the standby power supply is normal, there is no
impact on the existing services, because a switching to the standby power supply is
performed.
– If both active and standby power supply fail, the existing services are interrupted.
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: If this alarm is reported by the SCC board, it indicates that the battery on the SCC
board does not provide power or has no charge (the value of parameter 1 of this alarm is
0x05).
l Cause 2: If this alarm is reported by the PIU board, it indicates that the input voltage of the
subrack is abnormal because the power supply module is faulty (the value of parameter 1
of this alarm is 0x3d or 0x3f).
l Cause 3: If this alarm is reported by the PIU or CRPC board, it indicates that the power
supply module of the board fails or is aging (the value of parameter 1 of this alarm may be
any one but 0x05).
Procedure
l Cause 1: If this alarm is reported by the SCC board, it indicates that the battery on the SCC
board fails to provide power or has no power (the value of alarm parameter 1 is 0x05).
1. Check the jumper setting of the battery on the SCC board. If the setting disables the
battery from proving power, change the setting to ensure that the battery to provide
power to the SCC board. For details about the jumper setting of the battery on the SCC
board, see the Hardware Description.
2. If the alarm persists, replace the faulty board. For details, see the Parts
Replacement.
l Cause 2: If this alarm is reported by the PIU board, it indicates that the input voltage of the
subrack is abnormal because the power supply module is faulty (the value of parameter 1
of this alarm is 0x3d or 0x3f).
1. Check whether the switch on the DC power distribution box of the cabinet is ON. If
not, turn it to ON.
2. If the alarm persists, it indicates that the switch on the DC power distribution box is
faulty. In this case, replace the switch. For details, see "Replacing the Power Switch
on the DC Power Distribution Box" in the Parts Replacement.
l Cause 3: If this alarm is reported by the PIU or CRPC board, it indicates that the power
supply module of the board fails or is aging (the value of parameter 1 of this alarm may be
any one but 0x05).
1. Replace the faulty board. For details, see "Replacing the PIU Board" or "Replacing
the Raman Amplifier Board" in the Parts Replacement.
----End
Related Information
Related Cases:
l MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER
Alarms
l MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution
l MC-A112 The SCC Housed In the Slave Subrack Reports the POWER_FAIL Alarm
Because the Jumper on the Board Is Set Improperly
3.38 PUMP_COOL_EXC
Description
This alarm indicates that the cooling current of the pump laser exceeds the threshold. This alarm
is generated when the laser cooling current exceeds the upper threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates that the cooling current exceeds the threshold. The value is always
0x01.
Fault Symptom
Table 3-35 lists the fault symptom for the PUMP_COOL_EXC alarm.
The NE that reports this alarm reports a Cause 1: The ambient temperature of the
temperature alarm or fan fault alarm, such as board is excessively high or low.
TEMP_OVER or FAN_FAIL, within a
certain time.
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
The possible causes of the PUMP_COOL_EXC alarm are as follows:
Procedure
l Cause 1: The ambient temperature is excessively high or low.
1. Check the ambient temperature inside the telecommunications room, the cleanliness
of the air filter, and heat dissipation through fans. For details, see TEMP_OVER to
rectify the fault.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for causes 2 and 3.
l Causes 2: The pump laser temperature is excessively high or low/Cause 3: The board that
reports this alarm is faulty.
1. If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board"
of the Supporting Tasks.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.39 R_LOF
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.39.2 R_LOF (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The R_LOF (OCS) 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the R_LOF alarm are as follows:
Procedure
l Query current alarms on the U2000. For details, see Querying the Current Alarms in the
Supporting Task.
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.
3. If the alarm persists, see cause 2.
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 of the Board in the Supporting Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the
manufacturer information about the optical module.
If... Then...
The receive optical power of the local board is Proceed to the next step.
excessively low
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.
– Cleaning Optical Fiber Connectors Using Cartridge Cleaners
– Cleaning Optical Fiber Connectors Using Lens Tissue
– Cleaning Optical Adapters Using Optical Cleaning Sticks
Then, check whether the alarm is cleared.
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...
4. 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, see cause 4.
l Cause 4: The transmit optical power of the opposite station is abnormal.
1. On the U2000, check whether the transmit optical power of the opposite board 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 of the Board in the Supporting Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the
manufacturer information about the board optical module.
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.
3. If the alarm persists, see cause 5.
l Cause 5: The receive board at the local station is faulty.
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.
CAUTION
The loopback may cause service interruptions.
CAUTION
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.
If... Then...
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.
3. If the alarm persists, see cause 6.
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.
Description
This alarm indicates loss of frame in the received signals. This alarm is generated when the frame
alignment processing is out of frame (OOF) in consecutive 3 ms.
l WDM side - Check for this alarm when there are SDH frames in the services accessed on
the WDM side.
l Client side - Check for this alarm when the SDH services are accessed on the client side.
Attribute
Parameters
None
Fault Symptom
Table 3-37 lists the fault symptom for the R_LOF alarm.
The upstream board may report an R_LOS or Cause 4 for this alarm generated on the WDM
R_LOF alarm. side
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 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF signal.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The receive optical power or the OSNR
of the local board is abnormal.
l Cause 2 for this alarm generated on the WDM side: The signals transmitted by the upstream
OTU have no SDH frame structure.
l Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
l Cause 4 for this alarm generated on the WDM side: The input signals from the upstream
station contain an R_LOS or R_LOF signal.
l Cause 5 for this alarm generated on the WDM side: The dispersion is under- or over-
compensated.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm 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.
CAUTION
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.
1. Check whether board that reports this alarm supports pluggable optical modules.
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, contact Huawei for help.
l Cause 1 for this alarm generated on the WDM side/Cause 2 for this 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, on the U2000 check whether the client side of the
board at the opposite station reports an R_LOF alarm. If yes, rectify the fault according
to the procedure for handling the R_LOF alarm generated on the client side.
2. If the alarm persists, on the U2000 check whether the receive optical power at the
WDM-side optical interface of the alarm-reporting board is within normal range. For
the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
3. If the optical power is abnormal, rectify the fault according the procedure for handling
the IN_PWR_LOW or IN_PWR_HIGH alarm.
4. If the receive optical power is normal, use an SDH meter to receive signals from the
WDM side of the board in opposite station. Check whether the received signal is of
white spectrum (no signal frame) or has no SDH frame. If the received signal fails to
comply with the requirement, replace the faulty board.
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.
5. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
1. If the alarm persists, the board may be faulty. Replace the faulty board at the local
station.
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 of this alarm generated on the WDM side.
l Cause 4 for this alarm generated on the WDM side: The input signals from the upstream
station contain an R_LOS or R_LOF signal.
1. If the alarm persists, clear the alarm of the equipment at the upstream station.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5 of this alarm generated on the WDM side.
l Cause 5 for this alarm generated on the WDM side: The dispersion is under- or over-
compensated.
1. If the alarm persists, replace the DCM module. For details, see "Replacing a DCM"
in the Supporting Tasks.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss
Is Very Large
l MC-A21 An Interconnection Failure between the WDM and SDH Equipment
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
l MC-A31 Wrong Calculation for Dispersion in One DWDM Project
l MC-A104 No Optical Power Is Output on the WDM Side Due to Incorrect Configuration
l MC-A115 Determine whether the type and connections of the dispersion compensation
module (DCM) are proper according to the insertion loss between the TDC and the RDC
optical interfaces on the OAU
l MC-A128 EPL Service was interrupted due to a service mode mismatch of L4G boards
None.
3.40 R_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.40.2 R_LOS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The R_LOS (OCS) alarm indicates the loss of signal on the receive side of the line.
Attribute
Parameters
None
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 in
the Supporting Task.
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.
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
alarm persists, proceed to the next step.
2. Check whether the tail fiber is connected to the optical interface of the local board
properly.
If... Then...
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 of the Board 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.
(1) 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.
(2) 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.
(3) 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.
(4) 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.
2. Check whether the alarm is cleared. If the alarm persists, see other causes.
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.
2. Check whether the alarm is cleared. If the alarm persists, see other causes.
l Causes 1 of the board: The receive board at the local station is fault. As a result, the line
receiving fails.
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.
CAUTION
The loopback may cause service interruptions.
CAUTION
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.
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.
2. Check whether the alarm is cleared. If the alarm persists, see other causes.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Cause 1 for this alarm generated on the client side: The fiber jumper is not connected at
the optical interface of the board.
l Cause 2 for this alarm generated on the client side: The line attenuation is excessively high
or there is a fiber cut.
l Cause 3 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: No fiber jumper is connected to the
optical interface on the board of the local station, the fiber jumper connected to the optical
interface is loose, or the fiber jumper is connected improperly.
l Cause 2 for this alarm generated on the WDM side: The line attenuation is excessively high
or there is a fiber cut.
l Cause 3 for this alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
l Cause 4 for this alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
this alarm is generated.
l Cause 1 for this alarm generated on the client side: No fiber jumper is connected to the
optical interface on the board of the local station, the fiber jumper connected to the optical
interface is loose, or the fiber jumper is connected improperly.
1. Check the fiber jumper connection on the board that reports this alarm at the local
station.
2. Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers between boards according to
the actual networking environment.
3. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the client side.
l Cause 2 for this alarm generated on the client side: The line attenuation is excessively high
or there is a fiber cut.
1. Use a test instrument to test the fiber connection to determine whether a fiber break
occurs. If yes, replace the fiber.
2. Check whether this alarm is cleared. If the alarm persists, on the U2000 check whether
the receive optical power of the optical interface is within the normal range. For the
optical power specifications of the board, see the Product Description.
The receive optical power is Check the relevant fiber connectors. If the
normal, fiber connectors are dirty, clean or replace the
fiber connectors.
3. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the client side.
l Cause 3 for this alarm generated on the client side: The board that reports this alarm is
faulty.
1. Apply a hardware loopback between the transmit and receive optical interfaces on the
client side of the board that reports this alarm. If this alarm persists, it indicates that
the board is faulty. In this case, replace the board. For details, refer to "Replacing a
Board" of the Supporting Tasks. If this alarm is cleared, it indicates that the output
power of the client equipment is abnormal. In this case, check for and rectify the fault
on the client equipment.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
l Cause 1 for this alarm generated on the WDM side: No fiber jumper is connected to the
optical interface on the board of the local station, the fiber jumper connected to the optical
interface is loose, or the fiber jumper is connected improperly.
1. Check the fiber jumper connection on the board that reports this alarm at the local
station.
2. Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers between boards according to
the actual networking environment.
3. Check whether this 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 line attenuation is excessively high
or there is a fiber cut.
1. On the U2000, check whether the receive optical power at the optical interface is
within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description.
The receive optical power is Check the relevant fiber connectors. If there
normal, is any dirt or damage, clean or replace the fiber
connectors. For how to troubleshoot the
specific fault, refer to "Troubleshooting
Optical Power Anomalies" of the
Troubleshooting.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 for this alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
1. On the U2000, check whether the laser on the board at the opposite station is on. If
not, open the laser.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4 of this alarm generated on the WDM side.
l Cause 4 for this 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.
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, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
l MC-A14 The LWF Board Reports R_LOS
l MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
l MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
l MC-A125 Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case of
a fiber break
l MC-A126 VA4 board reports R_LOS when the receiver power is below -23 dBm even if
the attenuation is decreased
l MC-A141 Normal Boards Are Mistakenly Considered Faulty due to Optical Module
Characteristics
l MC-A145 The Client Equipment Interconnected with the TOM Board Reports the R_LOS
Alarm Due to a Problem with the Optical Module on the TOM Board
l MC-A153 It Is Recommended to Enable the Auto-Negotiation Working Mode at a GE Port
When the LPT Function Is Enabled
l MC-A154 The N2SLQ16 Board Interconnected with the TQS Board Reports an R_LOS
Alarm Because The TQS Board Emits White Lights When the Input Optical Power Is
Normal
l MC-A156 An SDH Board on the SDH Equipment Reports an R_LOF Alarm When the
SDH Board Is Interconnected with a Tributary Board on the OptiX OSN 6800
l MC-A159 Services Are Interrupted After the Protection Hold-Off Time Is Set to 10s During
Configuration of Client-Side 1+1 Protection on the OptiX OSN 6800
l MC-A164 Why the WDM-Side Service Rate Reaches 11.1 Gbit/s When the LSX Board
Receives 10GE-LAN Services in Bit Transparent Transmission Mode on the Client Side
l MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper
3.41 R_OOF
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.41.2 R_OOF (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The R_OOF (OCS) 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
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 3: The transmit optical power of the opposite station is abnormal.
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 Query current alarms on the U2000. For details, see Querying the Current Alarms in the
Supporting Task.
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
of the Board in the Supporting Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the
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
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.
– Cleaning Optical Fiber Connectors Using Cartridge Cleaners
– Cleaning Optical Fiber Connectors Using Lens Tissue
– Cleaning Optical Adapters Using Optical Cleaning Sticks
Then, check whether the alarm is cleared.
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...
4. 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, see cause 3.
l Cause 3: The transmit optical power of the opposite station is abnormal.
1. On the U2000, check whether the transmit optical power of the opposite board 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 of the Board in the Supporting Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the
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.
3. If the alarm persists, see cause 4.
l Cause 4: The receive board at the local station is faulty (including the fault of the cross-
connect board).
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.
CAUTION
The loopback may cause service interruptions.
CAUTION
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.
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
Replacement. Then, check whether the alarm is cleared.
4. If the alarm persists, see cause 5.
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.
Description
This alarm indicates out of frame in the receive signals. This alarm is generated when the heads
of consecutive five frames fail to be detected.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
Fault Symptom
Table 3-40 lists the fault symptoms for the R_OOF alarm.
The board that reports this alarm also report Cause 1 for this alarm generated on the WDM
an IN_PWR_LOW alarm. side
The board that reports this alarm also reports Cause 2 for this alarm generated on the WDM
bit error alarms, such as B1_EXC alarm. side
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 for this alarm generated on the client side: The input signals on the client side are
abnormal and thus an R_OOF alarm is generated.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The attenuation or optical power of the
received signals are excessively high.
l Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
l Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
l Cause 4 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1 for this alarm generated on the client side: The input signals on the client side are
abnormal and thus an R_OOF alarm is generated.
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.
CAUTION
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 contain
R_OOF signals. 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.
1. If the alarm persists, replace the faulty board.
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.
l Cause 1 for this alarm generated on the WDM side: The attenuation or optical power of the
received signals excessively high.
1. If the client side reports this alarm, check whether the receive optical power of the
interface 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.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
2. If the receive optical power is not within the normal range, see IN_PWR_LOW or
IN_PWR_HIGH to rectify the fault.
3. If the receive optical power is within the normal range, 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: A large number of bit errors are
generated during the transmission.
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.
3. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
1. On the U2000, check whether the transmit optical power at the corresponding optical
interface on the opposite OTU is within the normal range. For the optical power
specification of the specific board, refer to "Technical Specifications" of the Product
Description. For details, refer to "Querying Optical Power on the U2000" of the
Supporting Tasks.
2. If the transmit optical power exceeds the normal range, it indicates that the opposite
board is faulty. In this case, replace the faulty board.
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.
3. If the transmit optical power is within the normal range, see the alarm handling
procedure for cause 4 of this alarm generated on the WDM side.
l Cause 4 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
1. If the alarm persists, replace the faulty board.
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, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss
Is Very Large
l MC-A115 Determine whether the type and connections of the dispersion compensation
module (DCM) are proper according to the insertion loss between the TDC and the RDC
optical interfaces on the OAU
l MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
3.42 R_SLIP
Description
This alarm indicates frame slipping on the receive side. The alarm is generated when the phase
deviation occurs in the received service frames of the OSC or OTC board.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-41 lists the fault symptom for the R_SLIP alarm.
The board that reports this alarm also report Cause 2: The optical line attenuation is
an IN_PWR_HIGH or IN_PWR_LOW excessively high or the receive optical power
alarm. is excessively high.
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 clock configuration is wrong or the clock signals are not synchronous.
l Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
l Cause 3: The fibers at the eastward and westward optical interfaces on the OSC or OTC
board are connected reversely.
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 to ensure that
the clocks of the total network are synchronous. For details on how to configure the
clock information, see "Physical Clock" in the Feature Description.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
1. On the U2000, check whether the receive optical power at the optical interface is
within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description.
The receive optical power is excessively Check the fiber jumper or the fiber
low, connector. If the fiber jumper or fiber
connector is dirty, clean the fiber
connector or replace the fiber jumper.
The receive optical power is excessively adjust the optical attenuator to ensure
high, that the receive optical power is within
the normal range.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The fibers at the eastward and westward optical interfaces on the OSC or OTC
board are connected reversely. For example, the fibers for connecting to the TM1 optical
interface in the west and the TM2 optical interface in the east are connected reversely. See
the following figure.
1. If the alarm persists, check the engineering fiber connection diagram to see whether
the fibers at the eastward and the westward optical interfaces on the OSC or OTC
board are connected reversely. If the fiber connection is incorrect, correct it according
to the diagram.
OA
F RM1 TM2 F
I SC2 I
U TM1 RM2 U
OA
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The board that reports this alarm is faulty.
1. If the alarm persists, perform a cold reset on the faulty board on the U2000.
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.
3. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the
OSC Board
None.
3.43 REM_SF
Description
This alarm indicates that remote client-side services are not loaded. 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
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-42 lists the fault symptom for the REM_SF alarm.
The OTU board at the opposite station reports Cause 1: An R_LOS, R_LOF, R_LOC,
an R_LOS, R_LOF, R_LOC, MS_AIS, or a MS_AIS, or a LINK_ERR alarm is generated
LINK_ERR alarm. on the client side of the OTU at the opposite
station.
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: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on
the client side of the OTU board at the opposite station.
l Cause 2: The client side of the OTU board at the opposite end is faulty.
Procedure
l Cause 1: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on
the client side of the OTU board at the opposite station.
1. On the U2000, check whether an R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR
alarm is generated on the client side of the OTU board at the opposite station. If yes,
see R_LOS, R_LOF, R_LOC, MS_AIS, LINK_ERR 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.
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 the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.44 REMOTE_FAULT
Description
This alarm indicates a fault at the remote end.
Attribute
Parameters
None
Fault Symptom
Table 3-43 lists the fault symptom for the REMOTE_FAULT alarm.
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 opposite station receives a LOCAL_FAULT alarm.
See the following figure.
The client side of OTU board at station A detects a LOCAL_FAULT alarm, and the client
side of the OTU board at station B reports a REMOTE_FAULT alarm.
O O
Client T WDM WDM T Client
side U side side U side
Station A Station B
Procedure
l Cause 1: The opposite station receives a LOCAL_FAULT alarm.
1. Clear the LOCAL_FAULT alarm at the opposite station.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The board at the opposite station is faulty.
1. Replace the faulty board at the opposite station. For details, refer to "Replacing a
Board" of the Supporting Tasks.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.45 SECU_ALM
Description
The SECU_ALM is a security alarm. This alarm is generated when login fails after four
consecutive login failures performed by the same user.
Attribute
Alarm Severity Alarm Type
Parameters
None.
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: This alarm can be caused by illegal login. For example, the password is incorrect
or the user does exist.
Procedure
l Cause 1: This alarm can be caused by illegal login. For example, the password is incorrect
or the user does exist.
1. Check whether invalid users exist in the user list in the login window. If yes, delete
the invalid users from the user list.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.46 SUBRACK_ID_CONFLICT
Description
This alarm indicates a conflict of subrack IDs. In the case of the master-slave subrack mode,
this alarm is reported when the master subrack detects that the DIP switch settings of the slave
subracks are repeated.
Attribute
Parameters
Parameter Description
Fault Symptom
Table 3-44 lists the fault symptom for the SUBRACK_ID_CONFLICT alarm.
The board may report the BD_STATUS, l Cause 1: In the case of the master-slave
COMMUN_FAIL, and WRG_BD_TYPE subrack mode, multiple master subracks
alarms at the same time. 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.
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
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 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. 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 re-set the ID of this slave
subrack by changing the DIP switch setting on the SCC board. In this case, the IDs of
the two slave subracks are different.
2. After the subrack ID is changed, perform a warm reset on all the boards in the subrack.
For details, see "Performing a Warm Reset on the Board" in the Supporting Tasks.
3. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.47 SUM_INPWR_LOW
Description
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.
This alarm is reported from neither the WDM side nor the client side.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Fault Symptom
Table 3-45 lists the fault symptom for the SUM_INPWR_LOW alarm.
The upstream board reports an Cause 1: The output optical power of the
OUT_PWR_LOW alarm. upstream station decreases, and thus the input
optical power of the local station is
excessively low.
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 output optical power of the upstream station decreases, and thus the input
optical power of the local station is excessively low.
l Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber
connectors are dirty.
l Cause 3: The board that reports this alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
l Cause 1: The output optical power of the upstream station decreases and thus the input
optical power of the local station is excessively low.
1. On the U2000, check the output optical power of the boards at the upstream station
along the reverse direction of the signal flow. If the output optical power of a certain
board is excessively low, adjust the output optical power of the board to a value within
the normal range.
2. If the alarm persists, replace the board whose output optical power is excessively low.
For details, refer to "Replacing a Board" of the Supporting Tasks.
3. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber
connectors are dirty.
1. If the output optical power of all the boards at the upstream stations is normal, check
whether an optical attenuator with excessively high attenuation is attached to the
receive optical interface on the board that reports this alarm. If yes, decrease the
attenuation of the optical attenuator to a proper value or replace the optical attenuator
with a proper one.
2. If the alarm persists, check whether the attenuation of the built-in VOA in the upstream
boards is excessively high. If yes, adjust the attenuation of the VOA to a proper value.
3. If the alarm persists, check whether related fibers or fiber connectors are dirty. If yes,
replace the fiber jumpers or check and clean the fiber connectors.
4. If the alarm persists, the optical cables between stations may be faulty. In this case,
rectify the fault on the optical cables.
5. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports this alarm is faulty.
1. If the alarm persists, replace the faulty board.
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, contact Huawei for help.
----End
Related Information
None.
3.48 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
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-46 lists the fault symptom for the SWDL_NEPKGCHECK alarm.
The SWDL_NEPKGCHECK alarm persists. Cause 1: The same file in two partitions in the
SCC software package of the SCC board is
lost and cannot be restored.
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 same file in two partitions in the SCC software package is lost and cannot be
restored.
l Cause 2: A file in a partition of the SCC software package is lost and the file cannot be
restored from the associated file in another partition.
Procedure
l Causes 1 and 2: The same file in two partitions in the SCC software package is lost and
cannot be restored. A file in a partition of the SCC software package is lost and the file
cannot be restored from the associated file in another partition.
1. Select the software package of the same version to perform a package loading on the
NMS.
2. After successful package loading, the alarm is removed automatically. If the alarm
persists, contact Huawei engineers.
----End
Related Information
None
3.49 TD
Description
This alarm indicates that the transmitter is degraded. The TD alarm threshold of the laser is set
to a value 1.2 times of the initial value of the bias current. The TD alarm is generated when the
bias current of the laser exceeds the threshold and is smaller than the initial value by 1.5 times.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None.
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
Cause 1: The laser is aging.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser is aging.
1. Check whether board that reports this alarm supports pluggable optical modules.
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 2.
l Cause 2: The detection circuit of the board is faulty.
1. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----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.50 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.
Fault Symptom
Table 3-47 lists the fault symptom for the TEMP_OVER alarm.
On the NMS, the adjusting mode of the fan Cause 1: The set rotating speed of the fan
board is set to Adjustable Speed Mode and board is excessively low.
the rotating speed is set to Low Speed or
Medium Speed.
The fan board reports the FAN_FAIL or Cause 2: The fan board is faulty.
FAN_FAULT alarm.
The adjusting mode of the fan board is set to Cause 3: The air filter is excessively dusty.
Auto Speed Mode and the rotating speed is
set to High Speed. In addition, no other
alarms are generated.
The fan board reports the BD_STATUS Cause 5: The fan is not in position.
alarm.
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
The possible causes of the TEMP_OVER alarm are as follows:
l Cause 1: The set rotating speed of the fan board is excessively low.
l Cause 2: The fan board is faulty.
l Cause 3: The air filter is excessively dusty.
l Cause 4: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
l Cause 5: The fan is not in position.
l Cause 6: The board that reports the alarm is faulty.
Procedure
l Query the alarm parameter on the U2000. If the parameter is 0x01, handle the alarm
according to causes 1 to 6. If the parameter is 0x02, handle the alarm according to causes
4 and 6.
l Cause 1: The set rotating speed of the fan board is excessively low.
1. Check the adjusting mode and rotating speed of the fan board on the NMS. If the
adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or
Medium Speed, change the rotating speed to High Speed or the adjusting mode to
Auto Speed Mode.
2. Check whether the alarm is cleared. If the alarm persists, see cause 2.
l Cause 2: The fan board is faulty.
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.
2. Check whether the alarm is cleared. If the alarm persists, see Cause 5.
l Cause 5: 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.
2. Check whether the alarm is cleared. If the alarm persists, see Cause 6.
l Cause 6: The board that reports the alarm is faulty.
1. Replace the board that reports the alarm. For details, see the Parts Replacement.
----End
Related Information
None
3.51 TF
Description
This alarm indicates a transmission failure. This alarm is generated when the transmit optical
power of the laser exceeds the threshold of the output optical power of the laser.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
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
The possible causes of the TF alarm are as follows:
Cause 1: The laser module is damaged, or the laser is aging.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser module is damaged, or the laser is aging.
1. Check whether the board that reports this alarm supports pluggable optical modules.
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 the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The detection circuit of the board is faulty.
1. Perform a cold reset on the faulty board through the U2000.
2. If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty
board. For details, refer to "Replacing a Board" of the Supporting Tasks.
3. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----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.
Related Cases:
l MC-A12 Certain Boards Report the TF Alarm Transiently
3.52 TS_CFG_MISMATCH
Description
This alarm indicates a timeslot mistach. 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.
Reported from the WDM side or client side: WDM side
Attribute
Alarm Severity Alarm Type
Major Processing
Parameters
None
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
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 value of Timeslot Configuration Mode of the board that reports
this alarm is the same as the value of Timeslot Configuration Mode of the
corresponding board at the opposite station. If not, set them to Automatic. For details
on how to configure the service timeslots, see "Configuring Service Timeslots" in the
Configuration Guide.
2. If the mode is consistent, 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.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.53 WRG_BD_TYPE
Description
This alarm indicates that the type of the board is incorrect. This alarm is generated when the
logical board and the physical board are inconsistent.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
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.
None.
Possible Causes
The possible causes of the WRG_BD_TYPE alarm are as follows:
l Cause 1: The type of the logical board configured on the U2000 is different from 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 different from the type
of the physical board installed in the slot.
1. On the U2000, check whether the type of the logical board is the same as the type of
the physical board installed in the corresponding slot. If not, determine whether the
type of logical board or the type of the physical board is inappropriate according to
the engineering configuration requirements.
– If the type of the logical board is inappropriate, reconfigure the logical board on
the U2000.
– If the type of the physical board is appropriate, remove the existing board and then
insert another board of the correct type.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The board that reports this alarm is faulty.
1. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
CAUTION
Exercise caution when replacing the SCC board. For details on how to replace the
SCC board and the precautions, see the Parts Replacement.
2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
4 Alarm Processing
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 ALC_ADJUST_FAIL
4.3 ALC_WAIT_ADJUST
4.4 ALM_ALS
4.5 APS_MANUAL_STOP
4.6 ALM_GFP_dCSF
4.7 ALM_GFP_dLFD
4.8 ALM_HANGUP
4.9 ALM_TC_OEI
4.10 ALM_TC_REI
4.11 APE_ADJUST_FAIL
4.12 APE_ADJUST_PEND
4.13 APS_FAIL
4.14 APS_INDI
4.15 AU_AIS
4.16 AU_LOP
4.17 B1_SD
See the alarm page according to the type of the board that reports the alarm.
4.18 B2_EXC
4.19 B2_SD
4.20 B3_EXC
4.21 B3_EXC_VC3
4.22 B3_EXC_VC4
4.23 B3_SD
4.24 B3_SD_VC3
4.25 B3_SD_VC4
4.26 BD_NOT_INSTALLED
4.27 BD_STATUS
See the alarm page according to the type of the board that reports the alarm.
4.28 BDID_ERROR
4.29 C2_VCAIS
4.30 CHAN_ADD
4.31 CHIP_ABN
4.32 CLIENT_PROT_NOTSTART
4.33 CLIENT_PORT_STA_INDI
4.34 CLK_NO_TRACE_MODE
4.35 CRC4_CROSSTR
4.36 DB_RESTORE_FAIL
4.37 DBPS_ABNORMAL
4.38 DBMS_ERROR
4.39 DBMS_PROTECT_MODE
4.40 DCM_INSUFF
4.41 DLAG_PROTECT_FAIL
4.42 DSP_LOAD_FAIL
4.43 ETH_CFM_LOC
4.44 ETH_CFM_MISMERGE
4.45 ETH_CFM_MACSTATUS
4.46 ETH_CFM_RDI
4.47 ETH_CFM_UNEXPERI
4.48 ETH_SERVICE_CONFIG_FAIL
4.49 ETHOAM_DISCOVER_FAIL
4.50 ETHOAM_RMT_CRIT_FAULT
4.51 ETHOAM_RMT_LOOP
4.52 ETHOAM_RMT_SD
4.53 ETHOAM_SELF_LOOP
4.54 ETHOAM_VCG_SELF_LOOP
4.55 EX_ETHOAM_CC_LOS
4.56 EX_ETHOAM_MPID_CNFLCT
4.57 EXT_SYNC_LOS
4.58 EXT_TIME_LOC
4.59 FAN_FAIL
4.60 FAN_FAULT
4.61 FEATURE_WITHOUT_LICENSE
4.62 FC_8B10BERR_OVER
4.63 FCS_ERR
4.64 FEC_LOF
4.65 FEC_OOF
4.66 FLOW_OVER
4.67 FPGA_ABN
4.68 FSELECT_STG
4.69 FWD_PKT_LOSS
4.70 GAINDATA_MIS
4.71 HARD_BAD
4.72 HARD_ERR
4.73 HP_LOM
4.74 HP_RDI
4.75 HP_REI
4.76 HP_SLM
4.77 HP_TIM
4.78 HP_UNEQ
4.79 HSC_UNAVAIL
4.80 INTRA_OTU_STA_INDI
4.81 J0_MM
4.82 K1_K2_M
4.83 K2_M
4.84 L_SYNC
4.85 LAN_LOC
4.86 LAG_PORT_FAIL
4.87 LAG_VC_PORT_FAIL
4.88 LASER_HAZARD_WARNING
4.89 LASER_SHUT
4.90 LCS_DAYS_OF_GRACE
4.91 LCS_EXPIRED
4.92 LCS_FILE_NOT_EXIST
4.93 LCAS_FOPR
4.94 LCAS_FOPT
4.95 LCAS_PLCR
4.96 LCAS_PLCT
4.97 LCAS_TLCR
4.98 LCAS_TLCT
4.99 LOCAL_FAULT
4.100 LOCK_CUR_FAIL
4.101 LOCKPOW_MIS
4.102 LP_RDI_VC3
4.103 LP_SLM_VC3
4.104 LP_UNEQ_VC3
4.105 LPT_RFI
4.106 LSR_COOL_ALM
4.107 LSR_FORCE_OPEN
4.108 LSR_INVALID
4.109 LTI
4.110 MOD_COM_FAIL
4.111 MODULE_ADJUST_FAIL
4.112 MODULE_COOLCUR_OVER
4.113 MODULE_TEMP_OVER
4.114 MODULEFILE_UPDATE_FAIL
4.115 MS_CROSSTR
4.116 MS_REI
4.117 MS_SNCP_PS
4.118 MS_SNCP_STA_INDI
4.119 MS_APS_INDI_EX
4.120 MULTI_RPL_OWNER
4.121 NEBD_XC_DIF
4.122 NESF_LOST
4.123 NESOFT_MM
4.124 NESTATE_INSTALL
4.125 NO_BD_PARA
4.126 NO_BD_SOFT
4.127 NO_ELABEL
4.128 NODEID_MM
4.129 NTP_SYNC_FAIL
4.130 NULL_SEND
4.131 OCH_FDI
4.132 OCH_FDI-O
4.133 OCH_FDI-P
4.134 OCH_LOS-P
4.135 OCH_OCI
4.136 OCH_SSF
4.137 OCH_SSF-O
4.138 OCH_SSF-P
4.139 ODU_AIS
4.140 ODU_LCK
4.141 ODU_OCI
4.142 ODU_SNCP_STA_INDI
4.143 ODUk_LOFLOM
4.144 ODUk_PM_LCK
4.145 ODUk_PM_OCI
4.146 ODUk_PM_TIM
4.147 ODUk_TCMn_AIS
4.148 ODUk_TCMn_BDI
4.149 ODUk_TCMn_DEG
4.150 ODUk_TCMn_EXC
4.151 ODUk_TCMn_LCK
4.152 ODUk_TCMn_LTC
4.153 ODUk_TCMn_OCI
4.154 ODUk_TCMn_SSF
4.155 ODUk_TCMn_TIM
4.156 ODUKSP_PS
4.157 ODUKSP_STA_INDI
4.158 OH_LOOP
4.159 OLP_PS
4.160 OLP_STA_INDI
4.161 OMS_BDI
4.162 OMS_BDI-O
4.163 OMS_BDI-P
4.164 OMS_FDI-O
4.165 OMS_FDI-P
4.166 OMS_LOS-P
4.167 OMS_SSF
4.168 OMS_SSF-O
4.169 OMS_SSF-P
4.170 OOL
4.171 OOS_LOST
4.172 OPA_FAIL_INDI
4.173 OPU1_MSIM
4.174 OPU1_VCAT_SQM
4.175 OPU1_VCAT_VcPLM
4.176 OPU2_MSIM
4.177 OPU3_MSIM
4.178 OPUk_PLM
4.179 OSC_BDI
4.180 OSC_DEG
4.181 OSC_RDI
4.182 OTS_BDI
4.183 OTS_BDI-O
4.184 OTS_BDI-P
4.185 OTS_LOS-O
4.186 OTS_LOS-P
4.187 OTS_TIM
4.188 OTU_AIS
4.189 OTU_LOF
4.190 OTU_LOM
4.191 OTUk_AIS
4.192 OTUk_BDI
4.193 OTUk_DEG
4.194 OTUk_EXC
4.195 OTUk_LOM
4.196 OTUk_TIM
4.197 OUT_PWR_LOW
4.198 OWSP_PS
4.199 OWSP_STA_INDI
4.200 PATCH_ACT_TIMEOUT
4.201 PATCH_DEACT_TIMEOUT
4.202 PATCH_PKGERR
4.203 PM_BDI
4.204 PM_BEI
4.205 PM_BIP8_OVER
4.206 PM_BIP8_SD
4.207 PM_TIM
4.208 PORTSWITCH_FAIL
4.209 POWER_ABNORMAL
4.210 POWER_DIFF_OVER
4.211 PRBS_LSS
4.212 PUM_BCM_ALM
4.213 PUM_TEM_ALM
4.214 R_LOC
See the alarm page according to the type of the board that reports the alarm.
4.215 RELAY_ALARM_CRITICAL
4.216 RELAY_ALARM_IGNORE
4.217 RELAY_ALARM_MAJOR
4.218 RELAY_ALARM_MINOR
4.219 REM_SD
4.220 RS_CROSSTR
4.221 RTC_FAIL
4.222 S1_SYN_CHANGE
4.223 SCC_LOC
4.224 SEC_RADIUS_FAIL
4.225 SERVICE_TYPE_EXCEED_LICENSE
4.226 SERVICE_CAPACITY_EXCEED_LICENSE
4.227 SHELF_AREA_POWER_OVER
4.228 SPAN_LOSS_HIGH
4.229 SPAN_LOSS_LOW
4.230 SLAVE_WORKING
4.231 SM_BDI
4.232 SM_BEI
4.233 SM_BIP8_OVER
4.234 SM_BIP8_SD
4.235 SM_IAE
4.236 SM_TIM
4.237 SNCP_FAIL
4.238 SO_SK_MISMATCH
4.239 SPEED_OVER
4.240 STORM_CUR_QUENUM_OVER
4.241 SUBRACK_ID_MISMATCH
4.242 SUBRACK_LOOP
4.243 SUM_INPWR_HI
4.244 SW_SNCP_PS
4.245 SW_SNCP_STA_INDI
4.246 SWDL_ACTIVATED_TIMEOUT
4.247 SWDL_AUTOMATCH_INH
4.248 SWDL_BD_EXCLUDE
4.249 SWDL_CHGMNG_NOMATCH
4.250 SWDL_COMMIT_FAIL
4.251 SWDL_INPROCESS
4.252 SWDL_PKG_NOBDSOFT
4.253 SWDL_PKGVER_MM
4.254 SWDL_ROLLBACK_FAIL
4.255 SYN_BAD
4.256 SYNC_C_LOS
4.257 SYNC_DISABLE
4.258 SYNC_F_M_SWITCH
4.259 SYNC_LOCKOFF
4.260 SYNC_FAIL
4.261 SYSPARA_CFDB_NOSAME
4.262 T_LOSEX
4.263 T_SLIP
4.264 TEM_HA
4.265 TEM_LA
4.266 TEMP_OVER
4.267 TEST_STATUS
4.268 THUNDERALM
4.269 TIME_LOS
4.270 TIME_NO_TRACE_MODE
4.271 TR_LOC
4.272 TU_AIS_VC3
4.273 TU_LOP_VC3
4.274 VCAT_LOA
See the alarm page according to the type of the board that reports the alarm.
4.275 VCAT_LOM_VC3
4.276 VCAT_LOM_VC4
4.277 VLAN_SNCP_PS
4.278 VOA_ADJUST_FAIL
4.279 VOADATA_MIS
4.280 W_R_FAIL
4.281 WAVE_ADD_ABN
4.282 WAVE_DROP_ABN
4.283 WAVEDATA_MIS
4.284 WAVELEN_OVER
4.285 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.
Possible Causes
The board hardware is faulty.
Procedure
1 Perform a cold reset on the faulty board through the U2000.
2 If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty board.
For details, see the Parts Replacement.
----End
Related Information
None
4.2 ALC_ADJUST_FAIL
Description
ALC link adjustment failure. This alarm is generated when the ALC link adjustment fails.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Name Meaning
Parameter 3 and Parameter 4 l When Parameter 2 is 0x01, it indicates the no-response slot.
l When Parameter 2 is 0x02, it indicates the slot of the board
and optical interface.
l When Parameter 2 is 0x03, Parameter 3 indicates the link
number.
l When Parameter 2 is 0x04, it indicates the timeout period.
l When Parameter 2 is 0x05, it indicates the timeout period.
l When Parameter 2 is 0x06, Parameter 3 indicates the node
state.
Parameter 5 and Parameter 6 l When Parameter 2 is 0x01, it indicates the port number.
l When Parameter 2 is 0x02, it indicates the port number.
Possible Causes
l The board does not respond to a query.
l Alarms such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, and R_LOS occur on the
equipment.
l The node receives adjustment frames but no link is on the node.
l The link adjustment operation times out.
l The node adjustment operation times out.
l The node is in an incorrect node. That is, though receiving adjustment frames, the node is
not in the pre-adjustment state.
l The node does not permit adjustment and there are more than two retries of adjustment.
l The link configuration is in disorder.
Procedure
1 Check whether the ALC configuration is normal. The configuration rules are as follows:
l The sink node cannot be configured as a reference node.
l Reference equipment must be configured for the source node.
l The detection board should not be empty for a non-reference node.
l When the detection board is OBU1, the adjustment equipment should not be empty.
l When configuring the source node, make sure that the same optical interface is not configured
for the detection equipment and reference equipment.
2 Check whether the adjustment on the adjustment node is within the range.
----End
Related Information
None
4.3 ALC_WAIT_ADJUST
Description
ALC link anomaly and wait for adjustment. This alarm is generated when the ALC link in manual
mode is faulty and needs to be adjusted, this alarm is reported at the source node.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
l Currently, the ALC is in the manual mode. When the ALC link has anomaly and needs to
be adjusted, this alarm is reported.
Procedure
1 Manually start ALC adjustment.
----End
Related Information
None
4.4 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The ALS function is enabled on the U2000 or the Navigator.
Procedure
1 When the ALS function is disabled, the alarm is cleared automatically.
----End
Related Information
None
4.5 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is manually stopped.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The MSP protocol of the corresponding MSP group is manually stopped.
Procedure
1 View on the U2000 and confirm the MSP subnet where the protocol is stopped.
2 Restart the MSP protocol of the protection group, and the alarm is cleared.
----End
Related Information
None
4.6 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
Alarm Severity Alarm Type
Parameters
None
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
1 View the ALM_GFP_dCSF alarm on the U2000, and then determine the number of the
VCTRUNK where this alarm is generated.
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.
3 If the alarm persists, check whether the interface module at the source end is normal. If not,
replace the optical module.
4 If the alarm persists, replace the board that reports the alarm.
----End
Related Information
None
4.7 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
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
in the Supporting Task.
l Cause 1: There are a large number of bit errors on the link.
1. For details, see Querying the Current Alarms 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.
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.
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.
If... Then...
The HARD_BAD alarm exists The board is faulty. Proceed to the next
step.
If... Then...
The HARD_BAD alarm does not exist After eliminating other causes, proceed
to the next step if the fault persists.
----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.8 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The orderwire phone is in the off-hook state for a long time.
l The hardware is faulty.
Procedure
1 Check whether the orderwire phone is hung up. If not, hang up the phone. Then, check whether
the ALM_HANGUP alarm is cleared.
2 If the ALM_HANGUP alarm persists, the board hardware may be faulty. Replace the faulty
board. For details, see the Parts Replacement.
----End
Related Information
None
4.9 ALM_TC_OEI
Description
The ALM_TC_OEI alarm is an output error indication in the tandem connection. When the
accumulated number of output errors received at the sink of the tandem connection within one
second is greater than 0, the ALM_TC_OEI alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Some bit errors occur in the signals output from the sink of the tandem connection.
Procedure
1 Check whether any higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC,
B1_SD, B2_SD, or B3_SD alarm, is detected at the source and the sink. If yes, take priority to
clear it. Moreover, clean the fiber connector, and make sure that the fiber connector is inserted
firmly. Then check whether the ALM_TC_OEI alarm at the local station is cleared.
2 If the alarm persists, check whether the transmit board at the source is faulty. If yes, perform a
cold reset on the relevant line board, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
3 If the alarm persists, replace the relevant line board at the source, and then check whether the
alarm is cleared.
4 If the alarm persists, check whether the receive board at the sink is faulty. If yes, perform a cold
reset on the board that reports the alarm, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check
whether the alarm is cleared.
6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded.
In this case, ask the relevant carrier for solution.
----End
Related Information
None
4.10 ALM_TC_REI
Description
The ALM_TC_REI alarm is a remote error indication in the tandem connection. When the
accumulated number of remote bit errors in the tandem connection received at the sink within
one second is greater than 0, the ALM_TC_REI alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Bit errors occur in the monitored tandem connection section.
Procedure
1 Check whether any higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC,
B1_SD, B2_SD, or B3_SD alarm, is detected at the source and the sink. If yes, take priority to
clear it. Moreover, clean the fiber connector, and make sure that the fiber connector is inserted
firmly. Then, check whether the TC_REI alarm at the local station is cleared.
2 If the alarm persists, check whether the transmit board at the source is faulty. If yes, perform a
cold reset on the relevant board, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
3 If the alarm persists, replace the relevant line board at the source, and then check whether the
alarm is cleared.
4 If the alarm persists, check whether the receive board at the sink is faulty. If yes, perform a cold
reset on the line board that reports the alarm, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check
whether the alarm is cleared.
6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded.
In this case, ask the relevant carrier for solution.
----End
Related Information
None
4.11 APE_ADJUST_FAIL
Description
APE adjustment failure. This alarm is generated when the APE adjustment fails.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
l The communication fails.
Procedure
1 Check the cause of OSNR degrade and handle the alarm accordingly.
----End
Related Information
None
4.12 APE_ADJUST_PEND
Description
APE adjustment is pending for operation.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
APE detect the powers of channels are unequal, then APE adjustment is pending for operation.
Procedure
1 Manually start APE adjustment.
----End
Related Information
None
4.13 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching occurs.
l 0x01: linear MSP group
l 0x02: ring MSP group
Possible Causes
The possible causes of the APS_FAIL alarm are as follows:
Procedure
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.
2 Make sure that the networkwide APS protocol works properly. Stop the protocol, and then restart
it to check whether the alarm is cleared.
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.14 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching
occurs.
l 0x01: linear MSP group
l 0x02: ring MSP group
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
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.
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.
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.15 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
Alarm Severity Alarm Type
Parameters
None
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
to the downstream station.
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.
Identification method: Use the exclusive method.
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 in the
Supporting Task.
l Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm
to the downstream station.
If... Then...
The alarms listed in Table 4-1 exist Handle these alarms first. If the AU_AIS
alarm persists, proceed to the next step.
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.
CAUTION
The loopback may cause the service interruption.
3. Check whether the AU_AIS alarm exists at the opposite station after the loopback is
performed.
The alarm exists The AU_AIS alarm of the local station is transmitted
from the opposite station. Proceed to the next step.
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.
The alarms listed in Table 4-1 exist Handle these alarms first. If the AU_AIS
alarm is not cleared, see board cause 1.
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.
3. Check whether the alarm is cleared. If the alarm persists, see other causes.
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.
3. Check whether the alarm is cleared. If the alarm persists, see other causes.
----End
Related Information
4.16 AU_LOP
Description
The AU_LOP is an alarm indicating loss of the AU pointer. When the NDF or invalid pointer
values are received in eight consecutively frames on the receive side of the local optical interface,
the AU_LOP alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the AU_LOP alarm are as follows:
l Cause 1: Excessive receive bit errors are available at the local station.
Identification method: Query the alarms of bit errors on the U2000.
l Cause 2: The level of the service transmitted by the opposite station is inconsistent with
that of the service to be received at the local station.
Identification method: Query the service configuration on the U2000.
l Cause 3: The board (including the cross-connect and timing board) of the local end is faulty.
Identification method: Use the exclusive method.
l Cause 4: The board (including the cross-connect and timing board) of the opposite end is
faulty.
Identification method: Use the exclusive method.
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 in the
Supporting Task.
l Cause 1: Excessive bit errors are available at the local station.
1. Check whether any bit error alarms exist at the local end. Clear these alarms first.
– B1_EXC
– B1_SD
– B2_EXC
– B2_SD
2. Check whether the AU_LOP alarm is cleared. If the alarm persists, see other causes.
l Cause 2: The level of the service transmitted by the opposite station is inconsistent with
the level of the service to be received at the local station.
1. Check whether the level of the service transmitted by the opposite station is consistent
with the level of the service to be received by the local station.
If... Then...
The service levels are different Reconfigure the service levels at the two ends.
Then, check whether the alarm is cleared. If the
alarm persists, see other causes.
l Cause 3: The 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, perform cold reset on the
cross-connect board at the local station by using the U2000, or reseat the cross-connect
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 in the Installation Guide and Inserting Boards
in the Installation Guide.
CAUTION
If no protection cross-connect board works normally, do not perform the operations,
because all the services may be interrupted.
3. Check whether the alarm is cleared. If the alarm persists, replace the local cross-
connect and timing board. For details, see Parts Replacement.
l Cause 4: The transmit board (including the cross-connect and timing board) of the opposite
end is faulty.
1. Replace the faulty transmit board at the opposite station. For details, see Parts
Replacement.
2. Check whether the alarm is cleared. If the alarm persists, perform cold reset on the
cross-connect board at the opposite end, or reseat the cross-connect board at the
opposite end. For the operations that are performed by the U2000, see Performing a
Cold Reset of a Board in the Supporting Task. For the operations of reseating a board,
see Removing Boards in the Installation Guide and Inserting Boards in the Installation
Guide.
CAUTION
If no protection cross-connect board is available, the cold reset on the cross-connect
and clock board may interrupt the entire service.
3. Check whether the alarm is cleared. If the alarm persists, replace the opposite cross-
connect and timing board. For details, see Parts Replacement.
----End
Related Information
The concatenation levels of the services involve AU3, VC4, VC4-4c, VC4-8c, VC4-16c, and
VC4-64c.
NOTE
If the AU_LOP alarm is reported when the equipment runs on the existing network, you need to contact
the technical support engineers of Huawei and report the alarm even though you have cleared it by adopting
the preceding methods.
4.17 B1_SD
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.17.2 B1_SD (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The B1_SD (OCS) 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the B1_SD 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. Determine the number of the interface that reports the
alarm according to Parameter 1. For details, see Querying the Current Alarms in the
Supporting Task.
l Cause 1: The line performance degrades.
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 of the Board 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,
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.
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.
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.
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.
l Cause 2: The external environment is abnormal.
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.
l Cause 3: The receive board of the local end is faulty.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: The transmit board of the opposite end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
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.
Reported from the WDM side or client side: WDM side, 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 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
Alarm Severity Alarm Type
Parameters
None
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
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.
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
procedure of the OUT_PWR_LOW alarm.
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.
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.
5 If the alarm persists, replace the faulty board at the local station. For details, see the Parts
Replacement.
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.18 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the B2_EXC alarm are as follows:
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 in the
Supporting Task.
l Cause 1: The line performance degrades.
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 of the Board 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,
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.
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.
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.
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.
l Cause 2: The external environment is abnormal.
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.
l Cause 3: The receive board of the local end is faulty.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: The transmit board of the opposite end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
4.19 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
Parameters
None
Possible Causes
The possible causes of the B2_SD 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. Determine the number of the interface that reports the
alarm according to Parameter 1. For details, see Querying the Current Alarms in the
Supporting Task.
l Cause 1: The line performance degrades.
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 of the Board 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,
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.
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.
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.
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.
l Cause 2: The external environment is abnormal.
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.
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.
l Cause 3: The receive board of the local end is faulty.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: The transmit board of the opposite end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
4.20 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
Parameters
None
Possible Causes
The possible causes of the B3_EXC alarm are as follows:
Procedure
l Query current alarms on the U2000. Determine the number of the interface that reports the
alarm. For details, see Querying the Current Alarms in the Supporting Task.
l Cause 1: The line performance degrades.
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 of the Board 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,
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.
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.
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.
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.
l Cause 2: The external environment is abnormal.
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.
l Cause 3: The receive board of the local end is faulty.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: The transmit board of the opposite end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
4.21 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the B3_EXC_VC3 alarm are as follows:
Procedure
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.
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.
3 If the alarm persists, replace the board that generates the B3_EXC_VC3 alarm.
----End
Related Information
None
4.22 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the B3_EXC_VC4 alarm may be the same as those of the B3_EXC alarm.
Procedure
1 See the procedure for handling the B3_EXC alarm.
----End
4.23 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the B3_SD alarm are as follows:
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 in the
Supporting Task.
l Cause 1: The line performance degrades.
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 of the Board 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,
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.
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.
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.
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.
l Cause 2: The external environment is abnormal.
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.
l Cause 3: The receive board of the local end is faulty.
1. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
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.
3. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: The transmit board of the opposite end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
4.24 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
Parameters
None
Possible Causes
The possible causes of the B3_SD_VC3 alarm are as follows:
Procedure
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.
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,
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
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.
3 If the alarm persists, replace the board that generates the B3_SD_VC3 alarm.
----End
Related Information
None
4.25 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the B3_SD_VC4 alarm may be the same as those of the B3_SD alarm.
Procedure
1 See the procedure for handling the B3_SD alarm.
----End
4.26 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED alarm is an alarm indicating that the logical board is not created
in the corresponding slot. This alarm occurs when a physical board is installed but no logical
board is created on the U2000.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The logic board is not created.
Procedure
1 On the U2000, add a logic board that corresponds to the slot that reports the alarm.
----End
Related Information
None
4.27 BD_STATUS
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.27.2 BD_STATUS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The BD_STATUS (OCS) 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the BD_STATUS alarm are as follows:
Procedure
l Query current alarms on the U2000. Then find the boards that report the alarm. For details,
see Querying the Current Alarms 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.
2. If the alarm persists, see other causes.
l Cause 2: The board is not inserted in the corresponding slot or the contact part of the board
with the mother board is loose.
1. Check whether the board is inserted in the corresponding slot. If not, insert the
corresponding physical board. For details, see Inserting Boards in the 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 in the Installation Guide and Inserting Boards in the Installation
Guide. Then, check whether the alarm is cleared.
3. If the alarm persists, see other causes.
l Cause 3: The pins of the mother board are bent or the board is faulty.
1. Remove the board that reports the alarm. For details, see Removing Boards in the
Installation Guide. Check whether any pins of the mother board 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 Installation Guide. Then, check
whether the alarm is cleared.
2. If the alarm persists, replace the board that reports the alarm. For details, see the Parts
Replacement. Then, check whether the alarm is cleared.
3. If the alarm persists, see other causes.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The AUX board is faulty.
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
1 If the alarm is reported on the AUX board and all service boards but services are normal and the
SCC board operates normally, it indicates that the AUX board is faulty. Perform a warm reset
or cold reset on the faulty board through the U2000. If the alarm persists, replace the AUX board.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
4 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei
engineers.
----End
Related Information
None
4.28 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
Possible Causes
The possible causes of the BDID_ERROR alarm are as follows:
Procedure
1 View the BDID_ERROR alarm on the U2000 to determine the relevant board.
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.
----End
Related Information
None
4.29 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The value of the C2 byte to be transmitted is incorrectly configured at the remote end.
Procedure
1 View the C2_VCAIS alarm on the U2000. Determine the VC path that reports the alarm.
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.
3 If the alarm persists, replace the transmit board at the remote end. For details, see the Parts
Replacement.
----End
Related Information
None
4.30 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
Alarm Severity Alarm Type
Parameters
None
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
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.
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.31 CHIP_ABN
Description
The CHIP_ABN is an alarm indicating temperature chip failure. This alarm is generated when
the temperature chip fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The temperature chip on the board fails.
Procedure
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.
2 If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
4.32 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
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
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.
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.
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.33 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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
l Cause 1: A user issues an external switching command such as forced switching, manual
switching or locked switching.
1. On the U2000, query the switching state of the protection group. If the switching state
is forced switching, manual switching or locked 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 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.
2. If the alarm persists, check whether the attribute of the protection group is
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.
l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
1. There is no need to handle this alarm. After WTR Times (s), the alarm clears.
----End
Related Information
None
4.34 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
Alarm Severity Alarm Type
Parameters
None
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
----End
Related Information
None
4.35 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
exceeds the threshold.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
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
1 Check the clock configuration of the system on the U2000 to ensure that the configuration is
correct. For details, see the Configuration Guide.
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.
3 If the services are not influenced, check whether the fiber jumper between the FIU board and
the SC2/SC1/ST2 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.36 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Possible Causes
l The database configuration file is lost.
l Data in the database is damaged.
Procedure
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.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.37 DBPS_ABNORMAL
Description
The alarm indicates that the DBPS protection group is abnormal. When the DBPS protection
group detects anomalies, the DBPS_ABNORMAL alarm is reported.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated.
Parameter 3 The anomaly of the DBPS protection group is classified into the following
three types:
l 0x1 indicates that timeout occurs during the communication between
the active equipment and standby equipment;
l 0x2 indicates that the protection configuration of the active and
standby equipment is incorrect;
l 0x3 indicates that the snooping protocol is abnormal.
l If the protocol communication between the active equipment and the standby equipment
in the DBPS protection group cannot be established, there may be two pieces of active
equipment or standby equipment.
l If the DBPS protection status of the active equipment and standby equipment is
inconsistent, the service protection cannot function properly.
l If the snooping protocol used (VRRP or ARP) detects anomalies, the snooping function
cannot be realized, and thus the protection status of the active equipment and the protection
status of the standby equipment are incorrect.
Possible Causes
l The protocol communication between the active equipment and the standby equipment is
interrupted. In this case, communication between the protocol interfaces cannot be
established, or the protection configuration on the active equipment and the protection
configuration on the standby equipment are inconsistent.
l The VLAN configuration of the active equipment and the VLAN configuration of the
standby equipment are inconsistent, or the active equipment and standby equipment use
different snooping protocols.
l In the case of the VRRP protocol, the configuration of the DBPS protection group may be
inconsistent with the configuration of the VRRP group of the interconnected routers or the
VRRP groups of the routers interconnected to the active and standby DBPS may be
different.
Procedure
1 Query alarms on the U2000 to determine the ID of the protection group where the alarms are
generated.
2 Check whether the protocol interface of the DBPS protection group is configured properly and
the IDs of the protection groups on the active and standby equipment are consistent. If there are
errors in the configuration, modify the configuration of the protection group.
3 Check whether the VLAN configuration and the snooping protocol on DBPS protection group
are consistent. If not, modify the protection configuration.
4 If the VRRP protocol is used, check whether the configuration of the DBPS protection group is
consistent with the configuration of the VRRP protection in the two interconnected routers. Note
that the DBPS protection group must correspond to the VRRP group. In addition, the VRRP
groups of the routers interconnected to the active and standby DBPS equipment must be
consistent. Otherwise, eliminate the incorrect VRRP configuration of the router, and then re-
configure the DBPS protection group.
----End
Related Information
None.
4.38 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a database error. The alarm occurs when the database
is in error
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the alarm type. The value is the error code that causes the
DBMS_ERROR alarm.
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.
Possible Causes
l Operation to database fails.
l Data in the database is damaged.
l The board is faulty.
Procedure
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.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.39 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
Parameters
None
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
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.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.40 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
Possible Causes
The configuration of the DCM module is not correct or the DCM module is faulty.
Procedure
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.
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.41 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Name Meaning
Possible Causes
The possible causes of the DLAG_PROTECT_FAIL alarm are as follows:
Procedure
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.
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.
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.
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.
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.
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.
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.
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.42 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The board hardware is faulty.
Procedure
1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.43 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
Alarm Severity Alarm Type
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
Parameter Description
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.
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.44 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
Related Information
None
4.45 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).
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.46 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter Description
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).
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.47 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.48 ETH_SERVICE_CONFIG_FAIL
Description
Ethernet service configuration failure alarm.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 and 2 Indicates the service ID. A link conflicting with DBPS is invisible to users
and the value of this parameter for such a link is 0xff 0xff (invalid).
Parameters 3 and 4 Indicates the in port CVLAN ID. 0xff 0xff: No in port CVLAN is
available.
Parameters 5 and 6 Indicates the in port SVLAN ID. 0xff 0xff: No in port SVLAN is
available.
Parameter 7 Indicates the protection type. 0x00: LAG. 0x0a: DBPS. 0xff: No
protection is available.
Parameter 8 Indicates the protection group ID. 0xff: No protection group is available.
Possible Causes
Cause 1: The Ethernet service fails to be configured due to resource conflict.
Procedure
l Cause 1: The Ethernet service fails to be configured due to resource conflict.
1. On the U2000, view the alarm parameters. If the value of parameter 7 is 0xff, determine
the service ID based on parameters 1 and 2 and delete the service mapping. Then create
the service again by using another VLAN or port.
2. If the value of parameter 7 is 0x00 (LAG), determine the service ID based on alarm
parameters 1 and 2 and delete the service mapping the service ID, or determine the
protection group ID based on alarm parameter 8 and delete the LAG protection group
mapping the protection group ID. Then create the service again by using another port
or VLAN.
3. If the value of parameter 7 is 0x01 (DBPS), determine the protection group ID based
on alarm parameter 8 and delete the southbound port of the DBPS protection group
or delete the DBPS protection group. Then, create the southbound port of the DBPS
protection group by using another port.
----End
Related Information
None.
4.49 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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
1 View the ETHOAM_DISCOVER_FAIL alarm on the U2000 and determine the possible causes
of the alarm according to Parameter 1.
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.
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.
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.
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.
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
automatically cleared.
----End
Related Information
None
4.50 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
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
the alarm is cleared.
2 If irrecoverable problems such as a power failure occur at the opposite end, remove the fault.
The alarm is automatically cleared.
----End
Related Information
None
4.51 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
1 Disable the loopback. The ETHOAM_RMT_LOOP alarm is automatically cleared.
----End
Related Information
None
4.52 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The port with the OAM protocol enabled receives the link event message from the opposite end.
Procedure
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
automatically cleared.
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.
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.53 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
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.
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.
----End
Related Information
None
4.54 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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.
Procedure
1 Check the ETHOAM_VCG_SELF_LOOP alarm on the U2000, and determine the VCG port
number according to Parameters 1 and 2.
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.
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.
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.55 EX_ETHOAM_CC_LOS
Description
This alarm indicates a loss of the periodic continuity check message. When the sink maintenance
point receives the continuity check (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 of the time during which the CC message is transmitted from the source
maintenance point to the sink maintenance point), this alarm is generated.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 and 2 2 bytes, indicates the number of the Ethernet port where this alarm is
generated.
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
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
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) for the source and sink maintenance points, to locate the fault
in the services between the source maintenance point and the sink maintenance point.
4. Perform checks for the problem services, including software check, hardware check,
and traffic check. After the services restore, the alarm is automatically cleared. You
may perform LB to confirm that the alarm is cleared.
5. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
4.56 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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).
Possible Causes
Multiple MPs with the same MPID are created in a maintenance domain.
Procedure
1 View the EX_ETHOAM_MPID_CNFLCT alarm on the U2000 and confirm the ID of the
relevant MP according to the alarm parameters.
2 Query the information about the MP. Delete all the MPs that repeat the MPID, the alarm is
automatically cleared.
----End
Related Information
None
4.57 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
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located.
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.
l Cause 2: The input and output modes of the external clock source are inconsistent.
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.
l Cause 4: The clock board is faulty.
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.58 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located.
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.
l Cause 3: The clock board is faulty.
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.
l Cause 3: The clock board is faulty.
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.
2. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
----End
Related Information
None
4.59 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating a fan failure. This alarm is generated when one or more
fans fail.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 1 Indicates the number of failed fans. For example, 0x01 indicates that one fan
fails.
Possible Causes
l The fans stop running.
l The speed of the fans is excessively low.
l The fans fail.
Procedure
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.
2 If the alarm persists, replace the faulty fan tray assembly. For details, see the Parts
Replacement.
----End
Related Information
None
4.60 FAN_FAULT
Description
The FAN_FAULT is an alarm indicating a fan fault. This alarm is generated when one fan fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l One fan fails.
l The logical inspection fails.
Procedure
1 Replace the fan tray assembly. For details, see the Parts Replacement.
----End
Related Information
None
4.61 FEATURE_WITHOUT_LICENSE
Description
Service without license. A license-controlled feature is used but a license for the feature is not
installed.
Attribute
Parameters
None
Possible Causes
A license-controlled feature is used but a license for the feature is not installed. The possible
causes why the feature is not authorized are as follows:
Procedure
1 Load a correct license file onto the system so that the license-controlled feature is authorized,
or delete the service of unauthorized feature.
----End
Related Information
None
4.62 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
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
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.
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.63 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
Alarm Severity Alarm Type
Parameters
None
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.
l Cause 4: The board is faulty.
Procedure
l Query current alarms on the U2000. Determine the VCTRUNK number that reports the
alarm. For details, see Querying the Current Alarms 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.
2. If the alarm persists, see Cause 3.
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.
– Cleaning Optical Fiber Connectors Using Cartridge Cleaners
– Cleaning Optical Fiber Connectors Using Lens Tissue
– Cleaning Optical Adapters Using Optical Cleaning Sticks
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 of the Board in the Supporting Task.
NOTE
Related Information
None
4.64 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
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
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 The board hardware is faulty.
l Certain problems are found in the services from the opposite end.
Procedure
1 View the FEC_LOF alarm on the U2000 to determine the relevant board.
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.
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.
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.
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.
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.
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.65 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out-of-frame.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
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
1 View the FEC_OOF alarm on the U2000 to determine the relevant board.
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.
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.
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.
5 If the alarm persists, check whether the fiber is normal. If yes, replace the board that generates
the alarm.
6 If the alarm persists, replace the cross-connect and timing board at the local station.
7 If the alarm persists, replace the line board at the opposite end.
8 If the alarm persists, replace the cross-connect and timing board at the opposite end.
----End
Related Information
None
4.66 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating the inflow at the Ethernet port exceeds the threshold.
When the received traffic at the Ethernet port exceeds the expected traffic, this alarm is generated.
Attribute
Parameters
None
Possible Causes
The traffic received by the port is larger than the preset traffic of the port.
Procedure
1 View the FLOW_OVER alarm on the U2000, and confirm the relevant board and port according
to Parameter 1.
2 If the expected traffic of the port can be increased, this alarm can be cleared by increasing the
threshold traffic. For details, see "Adjusting Ethernet Path Bandwidth."
NOTE
The channel numbers to be added should have the same rate as the original channel members.
3 If the expected traffic of the port cannot be increased, service packet loss can be avoided only
by reducing the traffic transmitted by the opposite station.
----End
Related Information
None
4.67 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
Alarm Severity Alarm Type
Parameters
None
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
1 Reload the FPGA file to the board.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.68 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is forcibly selected.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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.
Possible Causes
The command of forcibly selecting the clock board is issued.
Procedure
1 After the command of forcibly selecting the clock board is cancelled, the FSELECT_STG alarm
is automatically cleared.
----End
Related Information
None
4.69 FWD_PKT_LOSS
Description
The FWD_PKT_LOSS is an alarm indicating loss of packets at a certain port
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
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.
2 If the alarm persists, check whether the packets transmitted at the opposite station are proper. If
not, transmit proper packets again.
3 If the alarm persists, check whether the QoS is configured properly. If not, re-configure the QoS.
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.70 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
Alarm Severity Alarm Type
Parameters
None
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.71 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware failure. When the system detects hardware
failure, this alarm is reported.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter Description
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 the 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 the Installation Guide. In the case of the OptiX
OSN 6800 and OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting
Boards". In the case of the OptiX OSN 3800 equipment, see "Removing Boards" and
"Inserting Boards".. 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.72 HARD_ERR
Description
The HARD_ERR is an alarm indicating a hardware error. The alarm occurs when the board
hardware has a minor fault.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter Description
Possible Causes
The board hardware is faulty.
Procedure
1 Perform warm reset or cold reset on the faulty board through the U2000. For details, see the
Troubleshooting.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.73 HP_LOM
Description
The HP_LOM is an alarm indicating higher order path loss of multiframe.
Attribute
Alarm Severity Alarm Type
Parameters
None
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:
Procedure
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.
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.
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.
4 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.
----End
Related Information
None.
4.74 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
Alarm Severity Alarm Type
Parameters
None
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.
Procedure
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.
2 View alarms on the U2000 to check whether the HP_RDI alarm is cleared.
Options Description
If this alarm is cleared The fault is removed. End the alarm handling.
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.75 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
Parameters
None
Possible Causes
The possible cause of the HP_REI alarm is as follows:
Procedure
1 View the alarms on the opposite NE, and check whether there are B1 or B2 bit errors.
Options Description
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.
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.
CAUTION
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD
4.76 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
Alarm Severity Alarm Type
Parameters
None
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.
l The services are incorrectly configured.
Procedure
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.
2 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option Description
If this alarm is cleared The fault is removed. End the alarm handling.
3 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.
4 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option Description
If this alarm is cleared The fault is removed. End the alarm handling.
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.
CAUTION
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
4.77 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
Alarm Severity Alarm Type
Parameters
None
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.
l The services are incorrectly configured.
Procedure
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.
2 View alarms on the U2000 to check whether the HP_TIM alarm is cleared.
Options Description
If this alarm is cleared The fault is removed. End the alarm handling.
3 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.
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.
Option Description
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.
CAUTION
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
4.78 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the higher order path received by the line board is
unloaded.
Attribute
Parameters
None
Possible Causes
The possible cause of the HP_UNEQ alarm is as follows:
Procedure
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.
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.
3 View alarms on the U2000 to check whether the HP_UNEQ alarm is cleared.
Options Description
If this alarm is cleared The fault is removed. End the alarm handling.
4 The board at the local station is faulty. Replace the faulty board.
----End
Related Information
None.
4.79 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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
1 Replace the standby board. For details, see the Parts Replacement.
----End
Related Information
None
4.80 INTRA_OTU_STA_INDI
Description
The INTRA_OTU_STA_INDI alarm indicates the state of the Intra-OTU 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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
1+1 protection group are faulty.
l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
l Cause 1: A user issues a command to perform the external switching.
1. On the U2000, query the switching state of the protection group. If the switching state
is forced switching, manual switching or locked 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 a command to clear the
external switching.
l Cause 2: The services of the working channel or the protection channel of the intra-board
1+1 protection group are faulty.
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.
2. If the alarm persists, check whether the attribute of the protection group is
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.
l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
1. This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
None
4.81 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.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
Possible Causes
l The J0 byte mismatches.
l The service connection is incorrect.
Procedure
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.
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.
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.82 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
Possible Causes
The possible causes of the K1_K2_M alarm are as follows:
Procedure
1 View this alarm on the U2000, and determine the ID of the MS where the alarm is reported
according to alarm parameters.
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
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.
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.
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.83 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the K2_M alarm are as follows:
Procedure
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.
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
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.84 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
Parameters
None
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
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.
2 If the alarm persists, check whether the fiber or cable that is used to connect between the
equipments at the local station and the opposite station are well connected. If they are not well
connected, reconnect or replace the fiber or cable.
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.
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.
5 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
None
4.85 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
None
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.
l The board is faulty.
Procedure
1 Query the alarm informations on the U2000. Check whether the corresponding network port is
required according to the alarm parameters,
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.
2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable
and re-connect it.
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.86 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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, 0x00 0x02
indicates port 2, 0x03 indicates port 3, etc.
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.
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
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.
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.
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.
4 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
4.87 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that the VCG port in the aggregation group
fails. When the VCTRUNK port is not available, the aggregation fails. Therefore, this alarm
occurs.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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, 0x00 0x02
indicates port 2, 0x03 indicates port 3, etc.
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.
Possible Causes
l The port is in the link down or disabled state.
l The port has not received LACP messages.
l The port is self-looped.
Procedure
1 Check whether the VCG port in the aggregation group is fail. If yes, remove VCG port faults.
2 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.
3 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
4.88 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the work band. 0x01 indicates the C-Band and 0x02 indicates the L-
Band.
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
1 Check the IPA configuration on the NE.
2 If the NE is not configured with the IPA function, follow the network plan to create the IPA
protection. For detailed operations, see Feature Description.
3 If the NE is configured with the IPA function, enable the IPA function.
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.89 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of the board is shut down.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The user uses the U2000 or Navigator to perform the operation to shut down the laser.
Procedure
1 If the user cancels the setting of laser shutdown, the LASER_SHUT alarm is automatically
cleared.
----End
Related Information
None
4.90 LCS_DAYS_OF_GRACE
Description
License in keepalive period. The LCS_DAYS_OF_GRACE is an alarm indicating the license
has expired and is within the keepalive period of 60 days.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
l The license file fails. The system is in the trial state and within the keepalive period of 60
days.
l The license file does not match ESN or V/R version. The system is in trial state and within
the keepalive period of 60 days.
l The license-controlled items exceed the expiry date but is within the keepalive period of
60 days.
Procedure
1 Load a license file to the system.
----End
Related Information
None
4.91 LCS_EXPIRED
Description
License expired. The LCS_EXPIRED is an alarm indicating the license has expired and the
keepalive period of 60 days has also elapsed.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
l The license of the system has expired and the keepalive period of 60 days has also elapsed.
l The system license file does not match the ESN or V/R version, and the keepalive period
of 60 days has elapsed.
Procedure
1 Load a license file to the system.
----End
Related Information
None
4.92 LCS_FILE_NOT_EXIST
Description
No license file. The LCS_FILE_NOT_EXIST is an alarm indicating the system is under license
control but a license file is not loaded onto the system.
Attribute
Parameters
None
Possible Causes
When starting up, the system does not find a license file, which is essential for the system to
run.
Procedure
1 Load a license file to the system.
----End
Related Information
None
4.93 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
Alarm Severity Alarm Type
Parameters
None
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
1 View the LCAS_FOPR alarm on the U2000 and determine the relevant VCTRUNK.
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.
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
whether the alarm is cleared.
4 If the alarm persists, disable and then enable the LCAS function at both ends. Check whether
the alarm is cleared.
----End
Related Information
None
4.94 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
Alarm Severity Alarm Type
Parameters
None
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
1 View the LCAS_FOPT alarm on the U2000 and determine the relevant VCTRUNK.
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.95 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
Alarm Severity Alarm Type
Parameters
None
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
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.
2 Ensure that the physical link is available. Check whether bidirectional services are configured.
If not, configure bidirectional services.
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.
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.
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
whether the alarm is cleared.
6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check
whether the alarm is cleared.
7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then,
check whether the alarm is cleared.
8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
CAUTION
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.96 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
Parameters
None
Possible Causes
The possible causes of the LCAS_PLCT alarm are as follows:
Procedure
1 View the LCAS_PLCT alarm on the U2000 and determine the relevant VCTRUNK.
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.
3 If the alarm persists, check whether bidirectional services are configured. If not, configure
bidirectional services. Then, check whether the alarm is cleared.
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.
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.
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
the alarm is cleared.
7 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check
whether the alarm is cleared.
8 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then,
check whether the alarm is cleared.
CAUTION
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.97 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
Parameters
None
Possible Causes
The possible causes of the LCAS_TLCR alarm are as follows:
Procedure
1 View the LCAS_TLCR alarm on the U2000 and determine the relevant VCTRUNK.
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.
3 Check whether bidirectional services are configured. If not, configure bidirectional services.
Then, check whether the alarm is cleared.
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.
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.
6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check
whether the alarm is cleared.
7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then,
check whether the alarm is cleared.
8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
CAUTION
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.98 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the LCAS_TLCT alarm are as follows:
Procedure
1 View the LCAS_TLCT alarm on the U2000 and determine the relevant VCTRUNK.
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.
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.
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.
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.
6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check
whether the alarm is cleared.
7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then,
check whether the alarm is cleared.
8 If the alarm persists, perform cold reset on the board.
CAUTION
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.99 LOCAL_FAULT
Description
Local fault alarm.
Attribute
Parameters
None
Possible Causes
l The input fiber on the client side is transiently cut.
l The board receives various bit errors.
l The input optical power on the client side is abnormal.
Procedure
1 Check whether the attenuation of the fiber between the input equipment and the interface on the
client side of the board is overlarge, and whether the fiber is aged or loose. If that is the case,
clean the fiber connector or replace the fiber. For details, see the Supporting Tasks.
2 Check whether the output optical power of the input equipment is within the normal range. If
the optical power is abnormal, remove the fault of the input equipment.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.100 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Possible Causes
The board is faulty.
Procedure
1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.101 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
Alarm Severity Alarm Type
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.102 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
Alarm Severity Alarm Type
Parameters
None
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
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.103 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
Alarm Severity Alarm Type
Parameters
None
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
1 View the LP_SLM_VC3 alarm on the U2000, and then determine the path number.
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.
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.
4 If the alarm persists, replace the line board at the local station.
5 If the alarm persists, replace the tributary board at the opposite station.
----End
Related Information
None
4.104 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
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
1 View the LP_UNEQ_VC3 alarm on the U2000, and then determine the path number.
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.
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
automatically cleared.
----End
Related Information
None
4.105 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
Alarm Severity Alarm Type
Parameters
None
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
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.
2 Based on the confirmed port number, check whether the opposite port is enabled. If yes, check
whether the LPT_RFI alarm is cleared.
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.
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.106 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
Possible Causes
The possible causes of the LSR_COOL_ALM alarm are as follows:
Procedure
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.
2 If the alarm persists, the laser may be faulty. Replace the board that generates the alarm. For
details, see the Parts Replacement.
----End
Related Information
None
4.107 LSR_FORCE_OPEN
Description
The LSR_FORCE_OPEN is an alarm indicating that the laser is forced to be open.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The optical interface is set to Disabled but the status of the laser is On.
NOTE
For L4G board, if the laser is On when the port on the client side is set to be disabled, the alarm is generated.
Procedure
1 Query whether the laser reporting the alarm needs to be used. If that is the case, set the status of
the laser to On on the U2000. If not, shut down the laser on the U2000.
----End
Related Information
None
4.108 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
Possible Causes
l The optical module has no license.
l A fault occurs during verifying the license of the optical module.
Procedure
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.109 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The possible causes of the LTI alarm are as follows:
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.
5. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
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.
2. 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.
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.
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.
5. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
l Cause 3: The synchronization source is set as non-revertive or locked.
Related Information
None
4.110 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.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
Parameters
None
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.
l The board hardware is faulty.
Procedure
1 Check the connection between the board and optical module, and re-connect the board and
optical module.
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.
3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
None
4.111 MODULE_ADJUST_FAIL
Description
The MODULE_ADJUST_FAIL is an alarm indicating that adjustment of the optical module
fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
Possible Causes
l The temperature of the optical module is excessively high.
l The optical module of the board is faulty.
Procedure
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
handling procedures.
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.
3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts
Replacement.
----End
Related Information
None
4.112 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
Possible Causes
l The temperature of the optical module is excessively high.
l The board hardware is faulty.
Procedure
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.
2 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
None
4.113 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the threshold crossing type. 0x01 indicates that the upper threshold is
exceeded and 0x02 indicates that the lower threshold is exceeded.
Possible Causes
l The ambient temperature of the board is excessively high or excessively low.
l The board hardware is faulty.
Procedure
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.
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
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.114 MODULEFILE_UPDATE_FAIL
Description
The MODULEFILE_UPDATE_FAIL is an alarm indicating that updating the microprogram
and laser parameter table fails. The alarm occurs when the in-service upgrade of the
microprogram of the optical module and the parameter table on the U2000 fails.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the type of the software that generates the alarm. 0x01 indicates the
microprogram and 0x02 denotes the parameter table.
Possible Causes
The upgrade of the microprogram of the optical module and the parameter table of the laser fails.
Procedure
1 Check whether the upgraded microprogram of the optical module and the parameter table of the
laser are correct.
2 Upgrade the microprogram of the optical module and the parameter table of the laser again.
3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts
Replacement.
----End
Related Information
None
4.115 MS_CROSSTR
Description
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.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The laser of the board in the opposite station is degraded.
l The input optical power of the board at the local station is too high or too low.
l The clock in the opposite station is degraded.
l The fiber is degraded.
Procedure
1 Check whether the fiber is aging or has excessive attenuation. If that is the case, remove the fault
of the fiber.
2 Query whether the board has the B1_EXC, B2_EXC, B1_SD or B2_SD alarms by using the
U2000. If that is the case, clear the alarms.
3 Check whether the input optical power of the board at the local station is within the normal range
by using the U2000. For the optical power specifications of the specific board, see the Product
Description.
l If the optical power displayed on the U2000 is normal, the board might be faulty. Replace
the faulty board. For details, see the Parts Replacement.
l If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
be within the normal range.
4 If the alarm persists, remove the fault of the board in the opposite station.
----End
Related Information
None
4.116 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The number of B2 bit errors received at the opposite station is beyond the specified range.
Procedure
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.117 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
to the protection channel from the working channel.
Reporting side: NA
Attribute
Alarm Severity Alarm Type
Parameters
None
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 MS 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 MS SNCP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
Procedure
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,
(1) If the external switching operation is necessary, ignore the alarm.
(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.
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
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
4.118 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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
1 On the U2000, query the switching state of the protection group. If the switching state is forced
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.
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.
(2) If the alarm persists, check whether the attribute of the protection group is Revertive. If
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.
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.119 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching
occurs:
l 0x01: linear MSP group
l 0x02: ring MSP group
Name Meaning
Parameter 4 Indicates the slot ID of the board where the protection switching
occurs.
Parameter 5 Indicates the number of the optical interface where the protection
switching occurs.
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.
l The board is faulty.
Procedure
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.
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.
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.120 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
Parameters
None
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
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.
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.121 NEBD_XC_DIF
Description
The NEBD_XC_DIF is an alarm indicating that the cross-connect matrix data of the NE and
board is different. For the board supporting service cross-connection, the alarm occurs when the
cross-connection data stored on the SCC is not consistent with that stored on the board.
Attribute
Alarm Severity Alarm Type
Critical Process 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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
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.
----End
Related Information
None
4.122 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The NE software is not reloaded after the NE software of the SCC board is erased.
Procedure
1 Reload the NE software of the SCC according to the Version Upgrade Guide.
2 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
None
4.123 NESOFT_MM
Description
Software difference between working and protection boards alarm. The two file systems of the
SCC board are backup for each other. Each file is saved in the two file systems. The alarm is
generated when the software versions in the two file systems are not consistent or the versions
of the files with the same name are not consistent.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameters 2 and 3 Indicates the ID of the file that does not comply with the SCC.
Possible Causes
l The software version currently running on the active SCC board is not consistent with that
on the standby SCC board.
l The version of the software set file in the active area of the active or standby SCC is not
consistent with that of the file that has the same name in the SCC board.
l The software set file in the active area of the active or standby SCC does not have the file
that has the same name and same type in the standby or active board.
Procedure
1 Update the NE software on the active or standby SCC board to ensure the version consistency.
2 Update the version of the software set file in the active area of the active or standby SCC to
make the file be consistent with the file that has the same name in the SCC board.
3 Add the file that is consistent with that of one SCC board to the corresponding area in the active
area of the other SCC board that does not have the file.
----End
Related Information
None
4.124 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
Alarm Severity Alarm Type
Parameters
None
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
1 Deliver the configuration information to the board by using the U2000.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.125 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.
Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
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
1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.126 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 3 Indicates the fault type. For example, 0x01 indicates that the file is lost
and 0x02 indicates that the file verification fails.
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
1 Reload the corresponding software through the U2000.
2 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.127 NO_ELABEL
Description
The NO_ELABEL is an alarm indicating that the electronic label is unloaded. The alarm is
generated when the electronic label of board is lost or not loaded.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the carrier type of the electronic label. For Example, 0x01
indicates the mother board, 0x02 indicates the sub-board and 0x03
indicates the optical module.
Possible Causes
The electronic label is unloaded or lost.
Procedure
1 Replace the board. For details, see the Parts Replacement.
----End
Related Information
None
4.128 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
Alarm Severity Alarm Type
Major Communication 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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 and Parameter 2 Indicates the ID of the MSP group in which the NODEID_MM
alarm is generated.
Possible Causes
The east and west node IDs configured for each node on the MSP ring do not match.
Procedure
1 View the NODEID_MM alarm on the U2000, and then determine the relevant MSP group ID.
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.
3 Restart the MSP protocol, and the alarm is cleared automatically.
----End
Related Information
None
4.129 NTP_SYNC_FAIL
Description
NTP synchronization failure. This alarm indicates that the NE is in the unsync state. The alarm
is cleared when the NTP turns into the sync state.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l The NTP server is not configured correctly.
l The NE fails to connect to the NTP server or the connection is interrupted.
l The NTP server stops unexpectedly.
Procedure
1 Check whether the NTP server is configured correctly.
2 Check whether the DCN is normal.
3 Check whether the NTP server works properly.
----End
Related Information
None
4.130 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The NULL Mapping Status parameter of the board is set to Enabled.
Procedure
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.131 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
Possible Causes
The OCH_FDI-P and OCH_FDI-O alarms coexist.
Procedure
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.
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.132 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
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
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.
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.133 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
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 payload signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
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.
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.134 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 at
the upper OMS and OTS layers, the OCH_LOS-P alarm is reported.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The board detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.
Procedure
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.
2 Confirm that the fiber connection between the OTU board that reports this alarm and the
DEMUX board is correct.
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.
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.
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.
----End
Related Information
None
4.135 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
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l No optical cross-connection for services to the local station is configured at the upstream
station.
Procedure
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.
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.136 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
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The OTS-LOS alarm at the upper OTS layer or the OMS-LOS alarm at the OMS layer is
generated.
Procedure
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.
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.137 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.
Reported from the WDM side or client side: WDM side
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.
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.138 OCH_SSF-P
Description
The OCH_SSF-P is an alarm indicating that the server signal (payload) fails at the OCh layer.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
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
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.
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.
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
by following proper handling procedures.
----End
Related Information
None
4.139 ODU_AIS
Description
The ODU_AIS is an ODU alarm indication.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
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.
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.
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.
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.140 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the ODU path are locked.
Attribute
Parameters
None
Possible Causes
The possible causes of the ODU_LCK alarm are as follows:
Procedure
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.
2 If no ODU path test is performed, cancel the lockout and then check whether the ODU_LCK
alarm is cleared.
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.141 ODU_OCI
Description
The ODU_OCI is an ODU open connection indication.
Attribute
Alarm Severity Alarm Type
Parameters
None
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.
l The upstream services are faulty.
l This board is faulty.
Procedure
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.
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.
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.142 ODU_SNCP_STA_INDI
Description
The ODU_SNCP_STA_INDI alarm indicates the state of the ODU SNCP 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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 ODU SNCP
group are faulty.
l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
l Cause 1: A user issues an external switching command.
1. On the U2000, query the switching state of the protection group. If the switching state
is forced switching, manual switching or locked 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 a command to clear the
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.
2. If the alarm persists, check whether the attribute of the protection group is
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 clear.
l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
1. This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
None
4.143 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
Alarm Severity Alarm Type
Parameters
None
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
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.
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.
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.
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.
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.144 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The services at the optical interface are interrupted.
Procedure
1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.
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.145 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".
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
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.
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.
3 Check whether the corresponding board of the station that triggers this alarm has any loopback.
If that is the case, release the loopback.
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.146 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
Alarm Severity Alarm Type
Parameters
None
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.
Procedure
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.
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.
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.
4 Check whether the cross-connection configuration is correct. If not, correctly configure the
cross-connection.
----End
Related Information
ITU-T G.709
4.147 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.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
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.
2 Query whether the alarm is reported from the client side. If that is the case, check the equipment
on the client side.
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.
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.
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.148 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
Alarm Severity Alarm Type
Parameters
None
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
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.
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.149 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.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The optical interface that reports the alarm is faulty.
l The optical interface at the opposite end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
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.
2 Locate the point that first generates the ODUk_TCMn_DEG alarm according to the service
route.
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.
4 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.
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.
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.150 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The attenuation of the received signals is excessively large, and the fiber of the transmission
line is abnormal.
l The transmit part of the opposite station is faulty.
l The receive part of the local station is faulty.
Procedure
1 Check whether the received 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.
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
procedure of the OUT_PWR_LOW alarm.
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.
4 If the alarm persists, replace the faulty board at the local station. For details, see the Parts
Replacement.
----End
Related Information
ITU-T G.709
4.151 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The signals are locked for the test of current line signals.
Procedure
1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.
2 Set the LCK type to Disabled if it is Enabled.
----End
Related Information
ITU-T G.709
4.152 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".
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The TCM at the opposite end is not set as enabled, and thus there is no TCM source.
Procedure
1 On the U2000, find the position that generates this alarm first according to the network topology.
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.153 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
Alarm Severity Alarm Type
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.
Procedure
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.
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.
3 Check whether the corresponding board of the station that triggers this alarm has any loopback.
If yes, release the loopback.
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.154 ODUk_TCMn_SSF
Description
The ODUk_TCMn_SSF is an alarm indicating that the ODUk TCMn server signal fails.
Attribute
Alarm Severity Alarm Type
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
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.
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.155 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.
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
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 fiber connection is incorrect.
l The cross-connection configuration is incorrect.
Procedure
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.
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.
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.
4 Check whether the cross-connection configuration is correct. If not, correctly configure the
cross-connection.
----End
Related Information
ITU-T G.709
4.156 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
to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 ODUk SP 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 ODUk SP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
Procedure
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,
(1) If the external switching operation is necessary, ignore the alarm.
(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.
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 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.
(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.157 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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 ODUk SP protection group are
faulty.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
1 On the U2000, query the switching state of the protection group. If the switching state is forced
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.
2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
(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.
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.158 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The overhead bus of the line board is looped back.
Procedure
1 After the loopback is released, the OH_LOOP alarm is automatically cleared.
----End
Related Information
None
4.159 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
Alarm Severity Alarm Type
Parameters
None
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 optical line 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 optical line protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
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 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,
(1) If the external switching operation is necessary, ignore the alarm.
(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.
2 If the alarm is generated due to the automatic switching of the protection group,
(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.
(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.
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.160 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
1 On the U2000, query the switching state of the protection group. If the switching state is forced
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.
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.
(2) If the alarm persists, check whether the attribute of the protection group is Revertive. If
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.
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.161 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
Possible Causes
The OMS_BDI-P and OMS_BDI-O alarms coexist.
Procedure
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.
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.162 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
Alarm Severity Alarm Type
Warning Communication alarm
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
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.
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.163 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
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
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.
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
handling procedures.
----End
Related Information
None
4.164 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 logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.165 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
Alarm Severity Alarm Type
Warning Communication alarm
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
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.
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.166 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
Possible Causes
The OMS layer detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.
Procedure
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.
2 Confirm that the actual fiber connection between the board that reports this alarm and the FIU
board is correct.
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.
----End
Related Information
None
4.167 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
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The OMS_SSF-P and OMS_SSF-O alarms coexist.
Procedure
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.
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.
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.168 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
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.
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
by following proper handling procedures.
----End
Related Information
None
4.169 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
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.
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.170 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.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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.
2. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
----End
Related Information
None
4.171 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
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The local station receives no overhead signals in ten consecutive seconds because the
opposite station sends no overhead signals.
Procedure
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.
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.172 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
Alarm Severity Alarm Type
Parameters
Parameter Description
Possible Causes
The rated optical power of the optical amplifier board is excessively high or excessively low.
Procedure
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.
2 If the alarm persists, adjust the rated optical power of the input or output optical interface.
----End
Related Information
None
4.173 OPU1_MSIM
Description
The OPU1_MSIM is an alarm indicating the OPU1 multiplex structure identifier mismatch.
Attribute
Parameters
None
Possible Causes
The board does not support the multiplex structure for service transmission of the board on the
source NE.
Procedure
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.
2 If the multiplex structures of the two boards do not match, replace one of them with a matched
board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.174 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The cross-connection configuration is incorrect.
Procedure
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.175 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
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.
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.176 OPU2_MSIM
Description
The OPU2_MSIM is an alarm indicating that mismatch of the OPU2 multiplex structure
indicator.
Attribute
Parameters
None
Possible Causes
The board does not support the multiplex structure for service transmission of the board on the
source NE.
Procedure
1 Check whether the multiplex structure of the local board mismatches with that of the
corresponding board of the source NE. For the multiplex structure of the board, see the Hardware
Description.
2 If the multiplex structures of the two boards do not match, replace one of them with a matched
board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.177 OPU3_MSIM
Description
The OPU3_MSIM is an alarm indicating mismatch of the OPU3 multiplex structure.
Attribute
Parameters
None
Possible Causes
The board does not support the multiplex structure for service transmission of the board on the
source NE.
Procedure
1 Check whether the multiplex structure of the local board mismatches with that of the
corresponding board of the source NE. For the multiplex structure of the board, see the Hardware
Description.
2 If the multiplex structures of the two boards do not match, replace one of them with a matched
board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.178 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.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The type of the payload in the data on the WDM side of the interconnected board mismatches.
Procedure
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.
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.
3 Check whether the payload types of the local board match 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.179 OSC_BDI
Description
Backward defect indication. This alarm occurs when detects a signal failure and the BDI byte
value is 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
BDI is declared if the BDI bit in the overhead field (byte 3, bit 5) is "1" for 5 consecutive frames.
Procedure
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.
2 If the alarm persists, check whether the corresponding board at the downstream station receives
the R_LOS orR_LOF alarm by using the U2000. If yes, handle the corresponding alarm at the
downstream station.
----End
Related Information
None
4.180 OSC_DEG
Description
Signal degraded alarm. This alarm occurs when bit errors are of burst distribution and the signal
degradation or bit error count crosses the threshold.
Attribute
Parameters
None
Possible Causes
l The optical interface at the local end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
1 Check whether the input optical power 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 optical power is not within the normal range, see the handing procedure of
the IN_PWR_HIGH and IN_PWR_LOW alarms for troubleshooting.
2 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.
3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, refer to
"Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
4.181 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
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.
l The board is faulty.
Procedure
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.
2 If the alarm persists, check whether the fiber between the two stations is damaged. If that is the
case, repair the fiber.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.182 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
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The upstream station reports the OTS_LOS alarm, and the downstream station inserts it
back to the local station.
Procedure
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.
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.
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.183 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
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.
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.184 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 reports this alarm.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.
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.185 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
The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.
3 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.
4 If the alarm persists, check whether the laser of the OSC at the opposite station is "On". If not,
open the laser of the OSC.
----End
Related Information
None
4.186 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
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
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
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.
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.187 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
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
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
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.
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.188 OTU_AIS
Description
The OTU_AIS an OTU alarm indication.
Attribute
Alarm Severity Alarm Type
Parameters
None
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.
l The upstream services are faulty.
l This board is faulty.
Procedure
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.
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.
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.
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.189 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame alignment signal (FAS) is abnormal.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the OTU_LOF alarm are as follows:
l The fiber or the optical power is faulty.
l The board hardware is faulty.
l The services that are transmitted from the opposite station are faulty.
Procedure
1 View the OTU_LOF alarm on the U2000 to determine the relevant board.
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 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.
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.
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.
5 If the alarm still persists, check whether the fiber works well. If yes, replace the board that
generates the alarm.
6 If the alarm persists, replace the cross-connect and timing board at the local station.
7 If the alarm persists, replace the line board at the opposite station.
8 If the alarm persists, replace the cross-connect and timing board at the opposite station.
----End
Related Information
None
4.190 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the multiframe alignment signal (MFAS) is
abnormal.
Attribute
Alarm Severity Alarm Type
Parameters
None
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.
Procedure
1 View the OTU_LOM alarm on the U2000 to determine the relevant board.
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 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.
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.
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.
5 If the alarm persists, check whether the fiber works well. If yes, replace the board that generates
the alarm.
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.191 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.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Alarm Severity Alarm Type
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
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.
2 If the alarm is reported from the client side, check the equipment on the client side.
3 Use the U2000 to query whether the upstream station has any loopback. If yes, release the
loopback.
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.192 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
Alarm Severity Alarm Type
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
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.
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.193 OTUk_DEG
Description
The OTUk_DEG is an alarm indicating that the OTUk signal is degraded. This alarm occurs
when the bit error detection mode is the burst mode, the signal is degraded, or bit error count
crosses the threshold.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 0, 1, 2, 3
l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The optical interface at the local end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
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.
2 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.
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.194 OTUk_EXC
Description
The OTUk_EXC is an alarm indicating that the OTUk bit errors cross the threshold. 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
Possible Causes
l The attenuation of the received signals is rather large, and the fiber of the transmission line
is abnormal.
l The receive part of the local station is faulty.
Procedure
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.
2 If the alarm persists, replace the faulty board at the local station. For details, see the Parts
Replacement.
----End
Related Information
ITU-T G.709
4.195 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The FEC type is incorrectly configured.
l The bit errors in the received signals of the OTU board at the local station are excessive.
l The board at the local station is faulty.
Procedure
1 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.
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.
3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.196 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.
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
Possible Causes
l The networking architecture and the TIM detection mode to be configured are not
consistent.
l The TTI sent at the opposite end is not consistent with the TTI to be received at the local
end.
l The fiber connection is incorrect.
l The cross-connection configuration is incorrect.
Procedure
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.
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.
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.
4 Check whether the cross-connection configuration is correct. If not, correctly configure the
cross-connection.
----End
Related Information
ITU-T G.709
4.197 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.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The input optical power is excessively low.
l The laser is aged.
l The board is faulty.
Procedure
1 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 specific boards, see
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.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.198 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
Alarm Severity Alarm Type
Parameters
None
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 OWSP 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 OWSP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
Procedure
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,
(1) If the external switching operation is necessary, ignore the alarm.
(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.
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 R_LOC, R_LOS. 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
4.199 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Possible Causes
l The user issues an external switching command such as the forced switching, manual
switching, or locked switching.
l The services of the working or protection channel of the OWSP protection group are faulty.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
1 On the U2000, query the switching state of the protection group. If the switching state is forced
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.
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 R_LOC, R_LOS. If yes, handle the alarms according to the corresponding alarm handling
procedures.
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.200 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
exceeds the threshold.
Attribute
Parameters
None
Possible Causes
The activated state of the patch package is excessively long.
Procedure
1 If the patch file is confirmed to be correct, run the patch file through the U2000 after the end of
the observation.
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.201 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
Possible Causes
The deactivated state of the patch package exceeds the threshold.
Procedure
1 If the patch file is confirmed to be correct, activate the patch file through the U2000.
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.202 PATCH_PKGERR
Description
The PATCH_PKGERR is an alarm indicating a patch package file error.
Attribute
Alarm Severity Alarm Type
Minor Process
Parameters
None
Possible Causes
The patch package of certain boards is lost
Procedure
1 Contact Huawei engineers to regenerate the patch package file.
----End
Related Information
None
4.203 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the PM_BDI alarm are as follows:
Procedure
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.
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.
CAUTION
The loopback causes service interruption.
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.204 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
Alarm Severity Alarm Type
Parameters
None
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:
Procedure
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.
2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the
PM_BEI alarm is generated, check and modify the configuration.
CAUTION
The loopback causes service interruption.
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.205 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the ODU PM section
exceeds the threshold.
Attribute
Parameters
None
Possible Causes
The possible causes of the PM_BIP8_OVER alarm are as follows:
Procedure
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.
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.
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. If
not, replace the line board.
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.
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
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm
is cleared.
9 Replace the line board that reports the alarm at the local station, and then check whether the
alarm is cleared.
10 Replace the cross-connect and timing board at the local station, and then check whether the alarm
is cleared.
11 Replace the line board at the opposite station, and then check whether the alarm is cleared.
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.206 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the PM BIP error signal is degraded in the ODU
PM section.
Attribute
Parameters
None
Possible Causes
The possible causes of the PM_BIP8_SD alarm are as follows:
Procedure
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_SD alarm is cleared.
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.
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. If
not, replace the line board.
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.
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
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm
is cleared.
9 Replace the line board that reports the alarm at the local station, and then check whether the
alarm is cleared.
10 Replace the cross-connect and timing board at the local station, and then check whether the alarm
is cleared.
11 Replace the line board at the opposite station, and then check whether the alarm is cleared.
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.207 PM_TIM
Description
The PM_TIM is an alarm indicating that the monitoring trail trace identifier (TTI) mismatches
in the ODU PM overhead.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible cause of the PM_TIM alarm is as follows:
Procedure
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.208 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The board hardware is faulty.
Procedure
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.
2 After the board is reset, perform the spectrum analysis on the MCA again by sing the U2000.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.209 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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.
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 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 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 in the Installation Guide and Inserting Boards in the Installation Guide.
CAUTION
If the services that pass the board are not configured with protection, the services are
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.210 POWER_DIFF_OVER
Description
The POWER_DIFF_OVER is an alarm indicating that the power difference between the active
and standby optical supervisory channels (OSCs) crosses the threshold.
Attribute
Parameters
None
Possible Causes
l During transport, the optical power of signals is excessively attenuated or the board at the
local end is added with an over-large optical attenuator. Hence, the optical power difference
between the active and standby OSCs at the receive end is excessively large.
l The optical power difference of signals in 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
1 Replace with a suitable optical attenuator. Adjust the optical power in the active and standby
channels of the board at the local station to ensure that the power difference is within 5 dB.
2 If the alarm persists, the detection circuit of the board at the local station is faulty. Replace the
faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.211 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
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
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
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.
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.212 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
Alarm Severity Alarm Type
Parameters
Parameter Description
Parameter 1 Indicates the threshold crossing type. The value is always 0x01.
Possible Causes
l Excessively high or excessively low ambient temperature affects the laser.
l The board is faulty.
Procedure
1 Check whether the ambient temperature is normal. If not, adjust the ambient temperature of the
equipment to a proper degree.
2 If the alarm persists, perform a warm reset on the faulty board on the U2000.
3 If the alarm persists, you can reseat the faulty board if it does not affect the services.
4 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.213 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
Alarm Severity Alarm Type
Parameters
Parameter Description
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.
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
1 Check whether the ambient temperature is normal. If not, improve it.
2 If the alarm persists, perform a warm reset on the faulty board through the U2000.
3 If the alarm persists, you can reseat the faulty board if it does not affect services.
4 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.214 R_LOC
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.214.2 R_LOC (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The R_LOC (OCS) 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
Possible Causes
The possible causes of the R_LOC alarm are as follows:
Procedure
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.
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.
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
Attribute
Alarm Severity Alarm Type
Parameters
None
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.
l The board is faulty.
Procedure
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.
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.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.215 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is a critical alarm of the alarm input.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
For the OptiX OSN 8800,
Procedure
1 For the OptiX OSN 8800, 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.
2 For the OptiX OSN 6800, Check whether the status of the external equipment (for example,
access control system) connected to the alarm input interface of the EFI board changes. If that
is the case, remove the fault of the external equipment.
3 For the OptiX OSN 3800, Check whether the status of the external equipment (for example,
access control system) connected to the alarm input interface of the AUX board changes. If that
is the case, remove the fault of the external equipment.
4 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.216 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is a warning alarm of the alarm input.
Attribute
Parameters
None
For the OptiX OSN 6800, the status of the external equipment connected to the alarm input
interface of the EFI board changes.
For the OptiX OSN 3800, the status of the external equipment connected to the alarm input
interface of the AUX 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.
l The status of the alarm input of the EFI board changes.
l The alarm input interface of the EFI board reports the alarm by default. The alarm is reported
in the default state.
l The status of the alarm input of the AUX board changes.
l The alarm input interface of the AUX board reports the alarm by default. The alarm is
reported in the default state.
Procedure
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.
2 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the EFI board changes. If that is the case, remove the
fault of the external equipment.
3 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the AUX board changes. If that is the case, remove the
fault of the external equipment.
4 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.217 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is a major alarm of the alarm input.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
For the OptiX OSN 6800, the status of the external equipment connected to the alarm input
interface of the EFI board changes.
For the OptiX OSN 3800, the status of the external equipment connected to the alarm input
interface of the AUX 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.
l The status of the alarm input of the EFI board changes.
l The alarm input interface of the EFI board reports the alarm by default. The alarm is reported
in the default state.
l The status of the alarm input of the AUX board changes.
l The alarm input interface of the AUX board reports the alarm by default. The alarm is
reported in the default state.
Procedure
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.
2 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the EFI board changes. If that is the case, remove the
fault of the external equipment.
3 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the AUX board changes. If that is the case, remove the
fault of the external equipment.
4 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.218 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is a minor alarm of the alarm input.
Attribute
Alarm Severity Alarm Type
Parameters
None
For the OptiX OSN 6800, the status of the external equipment connected to the alarm input
interface of the EFI board changes.
For the OptiX OSN 3800, the status of the external equipment connected to the alarm input
interface of the AUX 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.
l The status of the alarm input of the EFI board changes.
l The alarm input interface of the EFI board reports the alarm by default. The alarm is reported
in the default state.
l The status of the alarm input of the AUX board changes.
l The alarm input interface of the AUX board reports the alarm by default. The alarm is
reported in the default state.
Procedure
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.
2 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the EFI board changes. If that is the case, remove the
fault of the external equipment.
3 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the AUX board changes. If that is the case, remove the
fault of the external equipment.
4 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.219 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
Alarm Severity Alarm Type
Parameters
None
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
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.
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.220 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
Alarm Severity Alarm Type
Parameters
None
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
1 Check whether the fiber is aged or has excessive attenuation. If that is the case, remove the fault
of the fiber.
2 Query whether the board has the B1_EXC, B2_EXC, B1_SD, or B2_SD alarm by using the
U2000. If that is the case, clear the alarm.
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
the faulty board. For details, see the Parts Replacement.
l If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
a value within the normal range.
4 If the alarm persists, remove the fault of the board at the opposite station.
----End
Related Information
None
4.221 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the timing of the real time clock (RTC) fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The clip of the RTC clock is damaged.
l The temperature of the board is excessively high.
Procedure
1 Check whether the board temperature is normal. If it is abnormal, replace the fan.
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.222 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the
S1 mode.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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
Possible Causes
l Cause 1: The fiber connection is faulty.
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
automatically cleared.
----End
Related Information
None
4.223 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The board is faulty.
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
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.
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.224 SEC_RADIUS_FAIL
Description
Excessive failures in radius authentication. The SEC_RADIUS_FAIL is an alarm indicating that
a large number of authentification failures occur on the NE within a short period.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
A large number of RADIUS authentication failures occur on the NE within a short period.
Procedure
1 Check whether the user account expired.
2 Check whether the user password is changed or the user access policy is changed by the
administrator.
4 Check whether the shared key between the GNAS and the radius server is correct.
----End
Related Information
None
4.225 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
Alarm Severity Alarm Type
Major Service
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the ID of the subrack, where the service type exceeds the license limit.
Possible Causes
The service type configured in the subrack exceeds the license limit.
Procedure
1 According the alarm parameter, check whether the type of configured services in the subrack
exceeds the license limit by using the U2000.
3 If no proper license is available, purchase the license with a higher version from Huawei.
----End
Related Information
None
4.226 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the ID of the subrack, where the service capacity exceeds the license
limit.
Possible Causes
The service capacity configured in the subrack exceeds the license limit.
Procedure
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.
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.227 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
1 Remove the board from the subrack. Wait until the alarm is cleared.
----End
Related Information
None
4.228 SPAN_LOSS_HIGH
Description
Line insertion loss is excessively high. The alarm is generated when the actual line insertion loss
is higher than the reference value and the difference between the actual value and the reference
value exceeds the alarm threshold.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
l The line fiber is aged.
Procedure
1 Check whether the line fiber connections are abnormal and whether the fibers are aging. If the
line fiber connections are abnormal or the fibers are aging, reconnect the fibers or replace the
aging fibers.
2 Check whether any VOA is not configured on the line. If yes, manually adjust the attenuation
to the normal value.
3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively low,
set the alarm threshold according to the planning of the live network.
4 Check whether the insertion loss of the board is normal. If board replacement is necessary, see
the Parts Replacement.
----End
Related Information
None
4.229 SPAN_LOSS_LOW
Description
Line insertion loss is excessive low. The alarm is generated when the actual line insertion loss
is lower than the reference value and the difference between the actual value and the reference
value exceeds the alarm threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
l Aging fibers on the line are replaced with new fibers, or the line insertion loss is decreased.
l The sampled reference value of the line attenuation is inappropriate.
Procedure
1 Check whether the line fibers are aging. If the line fibers are new fibers, enable the ALC function
and then sample the reference value again.
2 Check whether any VOA is not configured on the line. If yes, manually adjust the attenuation
to the normal value.
3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively low,
set the alarm threshold according to the planning of the live network.
4 Check whether the insertion loss of the board is normal. If board replacement is necessary, see
the Parts Replacement.
----End
Related Information
None
4.230 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the SLAVE_WORKING alarm are as follows:
Procedure
l Query current alarms on the U2000. Determine the board that reports the alarm. For details,
see Querying the Current Alarms 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 Inserting Boards in the
Installation Guide. Then, check whether the alarm is cleared.
2. If the alarm persists, see Cause 2.
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
Replacement. Then, check whether the alarm is cleared.
2. If the alarm persists, see Cause 3.
l Cause 3: The service board is faulty.
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 in the Installation Guide and
Inserting Boards in the Installation Guide. Then, check whether the alarm is cleared.
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.231 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the SM_BDI alarm are as follows:
Procedure
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.
2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the
SM_BDI occurs, check and modify the configuration.
CAUTION
The loopback causes service interruption.
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.232 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the SM_BEI alarm are as follows:
Procedure
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.233 SM_BIP8_OVER
Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the OTU SM section
exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the SM_BIP8_OVER alarm are as follows:
Procedure
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 SM_BIP8_OVER alarm is cleared.
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.
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. If
not, replace the line board.
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.
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
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
8 Check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the
alarm is cleared.
9 Replace the line board that reports the alarm at the local station, and then check whether the
alarm is cleared.
10 Replace the cross-connect and timing board at the local station, and then check whether the alarm
is cleared.
11 Replace the line board at the opposite station, and then check whether the alarm is cleared.
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.234 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the SM_BIP8_SD alarm are as follows:
Procedure
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 SM_BIP8_SD alarm is cleared.
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.
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. If
not, replace the line board.
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.
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
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm
is cleared.
9 Replace the line board that reports the alarm at the local station, and then check whether the
alarm is cleared.
10 Replace the cross-connect and timing board at the local station, and then check whether the alarm
is cleared.
11 Replace the line board at the opposite station, and then check whether the alarm is cleared.
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.235 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
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
1 Adjust the frame offset on the board system side of the remote end (namely, the source of the
OTU/ODU adaptation function).
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.236 SM_TIM
Description
The SM_TIM is an alarm indicating the section monitoring TTI mismatch in the OTU SM
overhead.
Attribute
Parameters
None
Possible Causes
The possible causes of the SM_TIM alarm are as follows:
Procedure
1 According to the service network, determine the expected setting of the SM_TTI byte in the
relevant position.
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.
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.
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.237 SNCP_FAIL
Description
The SNCP_FAIL is an alarm indicating an SNCP switching failure.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
During the SNCP switching, the service grooming fails.
Procedure
1 Reset the SCC board to re-configure all the services.
----End
Related Information
None
4.238 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
CAUTION
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
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.
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.239 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The set rate of the optical interface is incorrect.
l The board hardware is faulty.
Procedure
1 Query the set rate and actual rate on the U2000, and determine whether the set rate is incorrect.
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.
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.240 STORM_CUR_QUENUM_OVER
Description
Alarm storm. Certain alarms on the SCC board may be lost when the alarm queue is full. This
alarm indicates that the alarm module is in the alarm storm state.
Attribute
Minor Service
Parameters
None
Possible Causes
The alarm queue fails to contain all the alarms when there are excessive alarms.
Procedure
1 Handle the existing alarms (except the STORM_CUR_QUENUM_OVER alarm). The
STORM_CUR_QUENUM_OVER alarm clears when the number of the current alarms is equal
to or below the STORM_CUR_QUENUM_OVER alarm threshold.
----End
Related Information
None
4.241 SUBRACK_ID_MISMATCH
Description
The SUBRACK_ID_MISMATCH is an alarm indicating mismatch of the subrack ID.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
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
2 Modify the DIP switch to "0", and thus the alarm is cleared.
----End
Related Information
None
4.242 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l In the master/slave subrack mode, the internal network interfaces are connected in a closed
loop.
l The AUX board is faulty, which leads to the abnormal communication.
Procedure
1 Check the cable connection between the subracks to ensure that the subracks are connected in
a chain manner.
2 Check whether the alarm is cleared. If the alarm persists, perform a warm reset or cold reset on
the faulty board through the U2000.
3 If the alarm persists, replace the AUX board.
----End
Related Information
None
4.243 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.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
Parameters
None
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.
l The board at the local station is faulty.
Procedure
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.
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
the faulty board. For details, see the Parts Replacement.
3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.244 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
to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 SW 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 SW SNCP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
Procedure
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,
(1) If the external switching operation is necessary, ignore the alarm.
(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.
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 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.
(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.245 SW_SNCP_STA_INDI
Description
The SW_SNCP_STA_INDI is an alarm indicating the state of the Sub-Wavelength SNCP
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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
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.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
1 On the U2000, query the switching state of the protection group. If the switching state is forced
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.
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 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.
(2) If the alarm persists, check whether the attribute of the protection group is Revertive. If
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.
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.246 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The operation is not committed 120 seconds after activation operation during loading of the
software package.
Procedure
1 In the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
4.247 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The automatic matching switch is turned off.
Procedure
1 If the alarm persists, contact Huawei engineers.
----End
Related Information
None
4.248 SWDL_BD_EXCLUDE
Description
The SWDL_BD_EXCLUDE is an alarm indicating that a board is excluded from software
download during software package downloading. This alarm occurs when some board failed
because of a failure to communicate with the SCC board or insufficient flash space.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The board is offline.
l Cause 2: The communication between the board and the SCC board is abnormal.
l Cause 3: The flash memory space on the board is insufficient.
l Cause 4: The board is repeatedle reset after activation because of a board software fault.
Procedure
1 On the DC window of the U2000, view the information about the boards that are isolated during
package loading.
2 Check whether the isolated boards are offline. If the isolated boards are offline, get them online.
3 Check whether any COMMUN_FAIL alarm is reported on the isolated boards. If the alarm is
reported, handle the problem by referring to the alarm processing mehod.
4 Check whether the flash memory space on the boards is sufficient. If the space is insufficient,
clean up the boards to get sufficient space.
5 Check whether the downloaded software matches with the isolated board version. If the software
mismathches with the board verison, download the correct software again.
6 If the preceding items are checeked and the results are normal, select the isolated boards on the
DC window, download software agagin, and then activate the software.
7 After handling all isolated boards, the SWDL_BD_EXCLUDE alarm is cleared when the board
isolation is released.
----End
Related Information
None
4.249 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm indicating that the SCC board is changed. The
system re-checks whether the board software of each board matches the NE software after the
NE starts up upon a power failure, the SCC unit is replaced, or cold reset is performed on the
SCC unit. The alarm occurs when the board software of a board mismatches the NE software.
It indicates that the board software mismatches the NE software.
Attribute
Parameters
None
l The software version of the unit is inconsistent with that of the SCC 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 SCC board.
l The SCC board is replaced, and the software package of the new SCC is inconsistent with
the software version of the board.
Procedure
1 On the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
4.250 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
Alarm Severity Alarm Type
Parameters
None
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
1 On the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
4.251 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
Parameters
None
Possible Causes
The NE is performing the package loading operation.
Procedure
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.252 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.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The user uses the customized software package, in which no software for the normal board is
found.
Procedure
1 On the U2000, choose correct software version to perform a normal package loading again.
----End
Related Information
None
4.253 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
Parameters
None
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
1 On the U2000, use a correct software package to perform package loading on the board.
----End
Related Information
None
4.254 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Certain board rollbacks fail when the NE performs the rollback.
Procedure
1 On the U2000, use the correct software package to perform package loading on the board.
----End
Related Information
None
4.255 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the synchronization source is degraded. This alarm
occurs when the clock source traced by the equipment is degraded.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located.
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.
Possible Causes
The possible causes of the SYN_BAD alarm are as follows:
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 quality of the traced clock source is degraded.
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 2: The input and output modes of the external clock source are inconsistent.
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.
----End
Related Information
None
4.256 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating the loss of synchronization source level. This alarm
is reported when the board detects that no synchronization source with a higher priority than the
current synchronization source exists.
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.
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 3: The service board is faulty.
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.
l Cause 3: The service board is faulty.
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.
2. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
l Cause 4: The clock board is faulty.
1. If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared.
2. If the alarm persists, replace the clock board.
----End
Related Information
None
4.257 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The automatic synchronization state of the system control board is changed from enabled to
disabled.
Procedure
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.258 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH is an alarm indicating the forced or manual switching state of a
clock source.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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.
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 switched 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.
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
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.259 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating that the clock source in the priority list is locked.
Attribute
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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.
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 locked 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.
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.260 SYNC_FAIL
Description
The SYNC_FAIL is an alarm indicating that the batch backup fails.
Attribute
Alarm Severity Alarm Type
Parameters
Parameter Description
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
1 Wait until the next working/protection backup succeeds and check whether the alarm is cleared.
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.261 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The SCC data and the CF card data are not consistent upon the first startup.
Procedure
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.262 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the T_LOSEX alarm are as follows:
Procedure
1 View the T_LOSEX alarm on the U2000 to determine the relevant board.
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.
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.
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.
----End
Related Information
None
4.263 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The clock signals are not synchronous.
Procedure
1 Perform cold reset on the faulty board through the U2000 or remove the faulty board. For details,
see the Supporting Tasks.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.264 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.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The working temperature of the board is excessively high.
l The laser is faulty.
l The module performance detection circuit is faulty.
Procedure
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.
2 Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.265 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.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Working temperature of the board is excessively low.
l The laser is faulty.
l The module performance detection circuit is faulty.
Procedure
1 Check the board ambient temperature. If it is excessively low, increase it.
2 Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.266 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
Alarm Severity Alarm Type
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.
Fault Symptom
Table 4-5 lists the fault symptom for the TEMP_OVER alarm.
On the NMS, the adjusting mode of the fan Cause 1: The set rotating speed of the fan
board is set to Adjustable Speed Mode and board is excessively low.
the rotating speed is set to Low Speed or
Medium Speed.
The fan board reports the FAN_FAIL or Cause 2: The fan board is faulty.
FAN_FAULT alarm.
The adjusting mode of the fan board is set to Cause 3: The air filter is excessively dusty.
Auto Speed Mode and the rotating speed is
set to High Speed. In addition, no other
alarms are generated.
The fan board reports the BD_STATUS Cause 5: The fan is not in position.
alarm.
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
The possible causes of the TEMP_OVER alarm are as follows:
l Cause 1: The set rotating speed of the fan board is excessively low.
l Cause 2: The fan board is faulty.
l Cause 3: The air filter is excessively dusty.
l Cause 4: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
l Cause 5: The fan is not in position.
Procedure
l Query the alarm parameter on the U2000. If the parameter is 0x01, handle the alarm
according to causes 1 to 6. If the parameter is 0x02, handle the alarm according to causes
4 and 6.
l Cause 1: The set rotating speed of the fan board is excessively low.
1. Check the adjusting mode and rotating speed of the fan board on the NMS. If the
adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or
Medium Speed, change the rotating speed to High Speed or the adjusting mode to
Auto Speed Mode.
2. Check whether the alarm is cleared. If the alarm persists, see cause 2.
l Cause 2: The fan board is faulty.
1. If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is
generated on the fan board. If yes, handle the alarm in advance.
2. Check whether the alarm is cleared. If the alarm persists, see cause 3.
l Cause 3: The air filter is excessively dusty.
1. 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.
2. 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 Routine Maintenance.
3. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
l Cause 4: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment 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.
2. Check whether the alarm is cleared. If the alarm persists, see Cause 5.
l Cause 5: 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.
2. Check whether the alarm is cleared. If the alarm persists, see Cause 6.
l Cause 6: The board that reports the alarm is faulty.
1. Replace the board that reports the alarm. For details, see the Parts Replacement.
----End
Related Information
None
4.267 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that the board is in the test state.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
A command is issued for the board to enter the test state.
Procedure
1 View the TEST_STATUS alarm on the U2000 to determine the relevant board.
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.268 THUNDERALM
Description
The THUNDERALM is an alarm indicating a lighting protection circuit failure.
The alarm is generated when the PIU board detects a lightning protection circuit failure of the
PIU board.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Parameter Description
Parameter 1 Indicates the number of the unit that reports the alarm. For example,
0x01 indicates the PIU1 unit.
0x02 indicates the PIU2 unit.
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
lightning 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.
l The board hardware is faulty.
Procedure
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.269 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.
Possible Causes
The possible causes of the TIME_LOS alarm are as follows:
Procedure
l Cause 1: There are fiber failures or misconnections.
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 2: The service board is faulty.
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.
2. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
l Cause 3: The clock board is faulty.
1. If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared.
2. If the alarm persists, replace the clock board.
----End
Related Information
None
4.270 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the TIME_NO_TRACE_MODE alarm are as follows:
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.
l Cause 2: There are fiber failures or misconnections.
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.
l Cause 4: The clock board is faulty.
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.
2. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
----End
Related Information
None
4.271 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
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 example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
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
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.272 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
Alarm Severity Alarm Type
Parameters
None
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
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
alarm is cleared. If the alarm persists, go to the next step.
2 Perform cold reset on the board that reports the alarm. Then check whether the TU_AIS_VC3
alarm is cleared. If the alarm persists, go to the next step.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after cold reset of the board.
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.
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.
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.273 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
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
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
alarm is cleared. If the alarm persists, go to the next step.
2 Perform cold reset on the board that reports the alarm. Then check whether the TU_LOP_VC3
alarm is cleared. If the alarm persists, go to the next step.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after cold reset of the board.
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.
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.
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.274 VCAT_LOA
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.274.2 VCAT_LOA (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
Description
The VCAT_LOA (OCS) 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows:
The configured VCTRUNK timeslots pass physical links of different distances.
Procedure
1 View the VCAT_LOA alarm on the U2000 to determine the relevant board.
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
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The fiber connection on the WDM side is incorrect.
l The board at the upstream or local station is faulty.
Procedure
1 Check whether the fiber connection on the WDM side is correct. If not, re-connect the fibers.
2 Check whether there are abnormal alarms in the WDM-side services. If yes, clear the alarms
according to the proper procedures.
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.
4 Based on the results, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.275 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the VCAT_LOM_VC3 alarm are as follows:
Procedure
1 View the VCAT_LOM_VC3 alarm on the U2000 to determine the relevant board.
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.
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.
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.276 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
Alarm Severity Alarm Type
Parameters
None
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
1 View the VCAT_LOM_VC4 alarm on the U2000 to determine the relevant board.
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.
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.
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.277 VLAN_SNCP_PS
Description
VLAN SNCP protection switching alarm. 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
Alarm Severity Alarm Type
Parameters
Parameter Description
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated.
Possible Causes
l A user issues an external switching command such as forced switching, manual switching
or locked switching.
l The services of the working channel or the protection channel of the VLAN SNCP group
are faulty.
l The switching is in WTR State. After WTR Times (s), the alarm clears.
Procedure
1 On the U2000, query the switching state of the protection group. If the switching state is forced
switching, manual switching or locked switching, check whether the external switching
operation is necessary,
(1) If the external switching operation is necessary, ignore the alarm.
(2) If the external switching operation is unnecessary, issue a clear switching command to clear
the external switching.
2 If the alarm is generated due to the fault of the working channel or the protection channel of the
protection group,
(1) Query whether the related boards for configuring the protection group have the alarms, for
example, R_LOF, R_LOS, R_OOF, OTUk_LOF, OTUk_LOM, OTUk_AIS. If yes, clear
the alarm so that the services in the working channel or the protection channel return normal.
(2) If the alarm persists, check whether the attribute of the protection group is Revertive. If
that is the case, the working channel would automatically switch to the working channel.
The alarm would disappear. If the attribute is Non-Revertive, set it to Revertive and the
alarm would disappear.
3 On the U2000, query the switching state of the protection group, if the switching is in WTR
State. This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
None
4.278 VOA_ADJUST_FAIL
Description
The VOA_ADJUST_FAIL is an alarm indicating that the VOA adjustment fails.
Attribute
Alarm Severity Alarm Type
Parameters
Parameter Description
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.
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
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.
2 If the alarm persists, check whether the laser of the OAU1 is on. If not, turn it on.
----End
Related Information
None
4.279 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.280 W_R_FAIL
Description
Writing or reading chip register failure. The alarm is generated when the read value and the
written value of the register are not consistent.
Attribute
Parameters
Parameter Description
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.
Possible Causes
The board is faulty.
Procedure
1 Perform a warm reset on the faulty board on the U2000. For details, see the Troubleshooting.
2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.281 WAVE_ADD_ABN
Description
APE detect wavelengths added.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The actually accessed wavelengths on each optical interface can be obtained through the
spectrum analysis module of the detect board. The wavelengths are then compared with the
scanned wavelengths obtained during the defining. If there is a wavelength that is not accessed,
a wavelength drop alarm is reported.
Procedure
1 The network management system prompts the user to re-define the APE standard optical power
curve.
----End
Related Information
None
4.282 WAVE_DROP_ABN
Description
APE detect wavelengths dropped.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Possible Causes
The actually accessed wavelengths on each optical interface can be obtained through the
spectrum analysis module of the detect board. The wavelengths are then compared with the
scanned wavelengths obtained during the defining. If a new wavelength is detected, a wavelength
add alarm is reported.
Procedure
1 The network management system prompts the user to re-define the APE standard optical power
curve.
----End
Related Information
None
4.283 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
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
l Cause 2: The board is faulty.
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
optical module on the board.
l Cause 2: The board is faulty.
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.284 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
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.
Procedure
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.
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
the Supporting Tasks.
3 If the alarm persists, cold reset of the OTU board is required. For details, see the Supporting
Tasks.
----End
Related Information
None
4.285 XC_UNSWITCH
Description
The XC_UNSWITCH is an alarm indicating that the cross-connect matrix of the board is not
switched.
Attribute
Parameters
None
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
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.
2 If the alarm persists, perform warm reset on the board, and check whether the XC_UNSWITCH
alarm is still generated.
3 If the alarm persists, contact Huawei engineers to re-load the board software.
4 If the alarm persists, replace the board that reports the alarm. For details, see the Parts
Replacement.
----End
Related Information
None
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.
ETHDROP (Drop Events) The total number of events in EGSH, LQMS, LQMD,
which packets were dropped LOG, LOM, TOM, TOG
by the probe due to lack of
resources. Note that this
number is not necessarily the
number of packets dropped;
it is just the number of times
this condition has been
detected.
RXOCTETS (Octets The total number of octets of LSX, TDX, TQX, EGSH,
Received) data (including those in bad LDX
packets) received on the
network (excluding framing
bits but including FCS
octets).
RXPKTS (Packets The total number of packets LSX, TDX, TQX, EGSH,
Received) (including bad packets, LDX
broadcast packets, and
multicast packets) received.
RXBRDCAST (Broadcast The total number of good LSX, LQMS, LQMD, TDX,
Packets Received) packets received that were LOG, LOM, LDMS, LDMD,
directed to the broadcast LDM, LQM, TOM, LDX,
address. Note that this does TOG, TQX, EGSH
not include multicast
packets.
RXMULCAST (Multicast The total number of good LSX, LQMS, LQMD, TDX,
Packets Received) packets received that were LOG, LOM, LDMS, LDMD,
directed to a multicast LDM, LQM, TOM, LDX,
address. Note that this TOG, TQX, EGSH
number does not include
packets directed to the
broadcast address.
ETHCRCALI (FCS and The total number of packets EGSH, LQMS, TDX
Alignment Errors) received that had a length
(excluding framing bits, but
including FCS octets) of
between 64 and 1518 octets,
inclusive, but had either a bad
Frame Check Sequence
(FCS) with an integral
number of octets (FCS Error)
or a bad FCS with a non-
integral number of octets
(Alignment Error).
ETHUNDER (Undersize The total number of packets LSX, LQMS, LQMD, TDX,
Packets Received) received that were less than LOG, LOM, LDMS, LDMD,
64 octets long (excluding LDM, LQM, TOM, TQX,
framing bits, but including LDX, TOG, EGSH
FCS octets) and were
otherwise well formed.
ETHOVER (Oversize The total number of packets LSX, LQMS, LQMD, TDX,
Packets Received) received that were longer LOG, LOM, LDMS, LDMD,
than 1518 octets (excluding LDM, LQM, TOM, TQX,
framing bits, but including LDX, TOG, EGSH
FCS octets) and were
otherwise well formed.
ETHFRG (Fragments) The total number of packets LSX, LQMS, LQMD, TDX,
received that were less than LOG, LOM, LDMS, LDMD,
64 octets in length (excluding LDM, LQM, TOM, LDX,
framing bits but including TOG, TQX, EGSH
FCS octets) and had either a
bad Frame Check Sequence
(FCS) with an integral
number of octets (FCS Error)
or a bad FCS with a non-
integral number of octets
(Alignment Error).
ETHJAB (Jabbers) The total number of packets LSX, LQMS, LQMD, TDX,
received that were longer LOG, LOM, LDMS, LDMD,
than 1518 octets (excluding LDM, LQM, TOM, LDX,
framing bits, but including TOG, TQX, EGSH
FCS octets), and had either a
bad Frame Check Sequence
(FCS) with an integral
number of octets (FCS Error)
or a bad FCS with a non-
integral number of octets
(Alignment Error).
RXPKT64 (Packets The total number of packets LSX, LQMS, LQMD, TDX,
Received, 64 Octets in (including bad packets) LOG, LOM, LDMS, LDMD,
Length) received that were 64 octets LDM, LQM, TOM, LDX,
in length (excluding framing TOG, TQX, EGSH
bits but including FCS
octets).
RXPKT1519 (Packets The total number of packets LQMS, LQMD, TDX, LOG,
Received, 1519~MTU (including bad packets) LOM, LDMS, LDMD,
Octets in Length) received that were between LDM, LQM, TOM, TOG,
1519 and MTU octets in TQX
length inclusive (excluding
framing bits but including
FCS octets).
TXPKT64 (Packets The total number of packets LSX, LQMS, LQMD, TDX,
Transmitted, 64 Octets in (including bad packets) LOG, LOM, LDMS, LDMD,
Length) transmitted that were 64 LDM, LQM, TOM, LDX,
octets in length (excluding TQX, EGSH
framing bits but including
FCS octets).
TXPKT1519 (Packets The total number of packets LQMS, LQMD, TDX, LOG,
Transmitted, 1519~MTU (including bad packets) LOM, LDMS, LDMD,
Octets in Length) transmitted that were LDM, LQM, TOM, TQX
between 1519 and MTU
octets in length inclusive
(excluding framing bits but
including FCS octets).
RXUNICAST (Unicast The total number of good LSX, LQMS, LQMD, TDX,
Packets Received) packets received that were LOG, LOM, LDMS, LDMD,
directed to a unicast address. LDM, LQM, TOM, EGSH,
LDX, TQX
TXUNICAST (Unicast The total number of packets
Packets Transmitted) that higher-level protocols
requested be transmitted, and
which were not addressed to
a multicast or broadcast
address at this sub-layer,
including those that were
discarded or not sent.
RXBGOOD (Good Octets The total number of octets of LQMS, LQMD, TDX, LOG,
Received) good packets received on the LOM, LDMS, LDMD,
network (excluding framing LDM, LQM, TOM, TOG
bits but including FCS
octets).
TXBGOOD (Good Octets The total number of octets of LQMS, LQMD, TDX, LOG,
Transmitted) good packets transmitted on LOM, LDMS, LDMD,
the network (excluding LDM, LQM, TOM
framing bits but including
FCS octets).
RXBBAD (Bad Octets The total number of octets of LQMS, LQMD, TDX, LOG,
Received) bad packets received on the LOM, LDMS, LDMD,
network (excluding framing LDM, LQM, TOM, TOG,
bits but including FCS TQX
octets).
TXBBAD (Bad Octets The total number of octets of LQMS, LQMD, TDX, LOG,
Transmitted) bad packets transmitted on LOM, LDMS, LDMD,
the network (excluding LDM, LQM, TOM, TQX
framing bits but including
FCS octets).
ETHFCS (FCS Errors) A count of frames received LSX, TDX, LOG, LOM,
on a particular interface that TQX, TOM, TOG, LDX,
are an integral number of EGSH
octets in length but do not
pass the FCS check. This
count does not include
frames received with frame-
too-long or frame-too-short
error.
TXETHDROP (Drop Events The total number of events in LQMS, LQMD, LOM,
at Transmission Direction) which packets were dropped LDMS, LDMD, LDM,
by the probe due to lack of LQM, TOM
resources at transmission
direction. Note that this
number is not necessarily the
number of packets dropped;
it is just the number of times
this condition has been
detected.
TXETHOVER (Oversize The total number of packets LQMS, LQMD, TDX, LOM,
Packets Transmitted) transmitted that were longer LDMS, LDMD, LDM,
than 1518 octets (excluding LQM, TOM, TQX
framing bits, but including
FCS octets) and were
otherwise well formed.
TXPKTS (Packets The total number of packets LSX, EGSH, LDX, TDX,
Transmitted) (including bad packets, TQX
broadcast packets, and
multicast packets)
Transmitted.
TXOCTETS (Octets The total number of octets of LSX, EGSH, LDX, TDX,
Transmitted) data (including those in bad TQX
packets) Transmitted on the
network (excluding framing
bits but including FCS
octets).
Name Board
The total number of frames with wrong CRC that the FC LOM
channel received in client side.
The total number of times that the link reseted in both client
and WAN side.
Name Board
LSBIASMAX VC3CSES
Full Frame Speed Packets Received and Transmitted Packets Transmitted(64 Octets
Received (128~255 Octets in Length) 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)
Undersize Packets
Broadcast Packets Received Multicast Packets Received Received
ODU1_PM_SES ODU2_TCMn_FEBBE
ODU1_PM_SESR ODU2_TCMn_FEBBER
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.
ODU1_PM_FESESR ODU2_TCMn_BBE
ODU1_PM_FEUAS ODU2_TCMn_BBER
CRC4SES LSIOPMIN
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.
MSFEBBE ODU1_TCMn_FEUAS
MSFECSES ODU1_TCMn_IAES
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.
MSFEBBE ODU1_TCMn_FEUAS
MSFECSES ODU1_TCMn_IAES
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.
ODU1_PM_BBE ODU1_TCMn_SESR
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.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
ODU1_PM_BBE ODU1_TCMn_SESR
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.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
ODU1_PM_BBE ODU1_TCMn_SESR
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.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
LSTMPMIN ODU2_TCMn_SESR
Packets Transmitted(128~255
Alignment Errors Oversize Packets Received Octets in Length)
ODU2_PM_BBE ODU2_TCMn_SESR
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.
ODU2_PM_BBE ODU2_TCMn_SESR
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.
LSTMPCUR ODU2_TCMn_FEUAS
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.
NOTE
In the GFP-T mode, the TN11LOG board does not support the RMON performance event.
LSTMPCUR ODU2_TCMn_FESESR
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.
Multicast Packets
Drop Events Broadcast Packets Received Received
FC_Client_RxOLSPrim_
CLIENT_CRC_ERR Cnt LINKTST_CNT
FC_Client_RxLRRPrim_Cnt FC_Client_TxOLSPrim_
Cnt
ODU1_PM_BBE ODU1_TCMn_SESR
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.
FCS and Alignment Errors Undersize Packets Received Oversize Packets Received
Oversize Packets
Transmitted
TN12LQMD
Packets Received Broadcast Packets
(1024~1518 Octets in Transmitted
Drop Events Length)
ODU1_PM_BBE ODU1_TCMn_SESR
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.
TN11LQMS
FCS and Alignment Errors Undersize Packets Received Oversize Packets Received
Oversize Packets
Transmitted
TN12LQMS
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
ODU1_PM_BBE ODU1_TCMn_SESR
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.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
LSTMPCUR ODU3_TCMn_FESESR
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.
LSTMPMIN ODU3_TCMn_SESR
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.
LSTMPMIN ODU2_TCMn_SESR
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.
LSTMPMIN ODU2_TCMn_SESR
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.
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
TN12ND2
FEC_AFT_CORER_FLOAT ODU1_PM_SES ODU2_TCMn_BIAES
ODU1_PM_FESESR ODU2_TCMn_BBE
ODU1_PM_FEUAS ODU2_TCMn_BBER
TN11ND2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
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.
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
TN52NQ2
FEC_AFT_CORER_FLOAT ODU0_PM_UAS ODU2_PM_SES
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN51NQ2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
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.
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
TN12NS2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
TN11NS2
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
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.
TN52NS3
FEC_AFT_COR_ER ODU1_PM_FESESR ODU2_TCMn_UAS
TN11NS3
ODU2_PM_ES ODU3_TCMn_FEBBE
FEC_AFT_COR_ER R
ODU2_PM_BBER ODU3_TCMn_FEBBE
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.
ODU1_PM_SES ODU2_TCMn_FEBBE
ODU1_PM_SESR ODU2_TCMn_FEBBER
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.
CRC4SES LSIOPMIN
CRC4SES LSIOPMIN
HPSES RPLMAX
HPUAS RPLMIN
LSIOPCUR OSC_FEBBE
LSIOPMAX OSC_FEBBER
ODU2_PM_BBE ODU2_TCMn_SESR
ODU2_PM_BBER ODU2_TCMn_UAS
TN11TDX
TN12TDX
LSBIASCUR LSTMPCUR ODU2_PM_SES
LSOOPMIN ODU2_PM_FEUAS
Packets Transmitted(128~255
Alignment Errors Octets Transmitted Octets in Length)
TN11TDX
Broadcast Packets Received Multicast Packets Received FCS and Alignment Errors
TN12TDX
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.
Drop Events
ODU0_PM_FEES ODU1_TCMn_FEUAS
TN11TOM
FEC_AFT_COR_ER ODU1_PM_FEBBER OTU1_BBE
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.
TN11TOM
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
Drop Events
LSTMPMAX ODU1_PM_SES
TN12TQM
FEC_AFT_COR_ER ODU1_PM_FEBBE OTU1_BBE
ODU1_PM_ES ODU1_TCMn_UAS
Oversize Packets
Transmitted
TN12TQM
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
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.
ODU2_PM_BBE ODU2_TCMn_SESR
ODU2_PM_BBER ODU2_TCMn_UAS
TN11TQX
LSBIASCUR LSTMPCUR ODU2_PM_SES
LSOOPMIN ODU2_PM_FEUAS
TN11TQX
Undersize Packets
Octets Received Received FCS Errors
TN53TSXL
FEC_AFT_CORER_FLOAT ODU3_PM_ES OTU3_BBE
ODU3_PM_BBER ODU3_TCMn_UAS
TN12VA1
TN12VA4
6.16 FEC_AFT_COR_ERAVR
6.17 FEC_AFT_CORER_FLOAT
6.18 FEC_BEF_COR_ER
6.19 FEC_BEF_COR_ERAVR
6.20 FEC_BEF_CORER_FLOAT
6.21 FEC_COR_0BIT_CNT
6.22 FEC_COR_1BIT_CNT
6.23 FEC_COR_BYTE_CNT
6.24 FEC_UNCOR_BLOCK_CNT
6.25 HPBBE
6.26 HPCSES
6.27 HPES
6.28 HPFEBBE
6.29 HPFECSES
6.30 HPFEES
6.31 HPFESES
6.32 HPFEUAS
6.33 HPSES
6.34 HPUAS
6.35 ICCLC
6.36 ICTMP
6.37 LSBIAS
6.38 LSBISA
6.39 LSCLC
6.40 LSIOP
6.41 LSOOP
6.42 LSTMP
6.43 MSBBE
6.44 MSCSES
6.45 MSES
6.46 MSFEBBE
6.47 MSFECSES
6.48 MSFEES
6.49 MSFESES
6.50 MSFEUAS
6.51 MSSES
6.52 MSUAS
6.53 ODU2PMBIP8
6.54 ODUk_PM_BBE
6.55 ODUk_PM_BBER
6.56 ODUk_PM_ES
6.57 ODUk_PM_FEBBE
6.58 ODUk_PM_FEBBER
6.59 ODUk_PM_FEES
6.60 ODUk_PM_FESES
6.61 ODUk_PM_FESESR
6.62 ODUk_PM_FEUAS
6.63 ODUk_PM_SES
6.64 ODUk_PM_SESR
6.65 ODUk_PM_UAS
6.66 ODUk_TCMn_BBE
6.67 ODUk_TCMn_BBER
6.68 ODUk_TCMn_BIAES
6.69 ODUk_TCMn_ES
6.70 ODUk_TCMn_FEBBE
6.71 ODUk_TCMn_FEBBER
6.72 ODUk_TCMn_FEES
6.73 ODUk_TCMn_FESES
6.74 ODUk_TCMn_FESESR
6.75 ODUk_TCMn_FEUAS
6.76 ODUk_TCMn_IAES
6.77 ODUk_TCMn_SES
6.78 ODUk_TCMn_SESR
6.79 ODUk_TCMn_UAS
6.80 OSC_BBE
6.81 OSC_BBER
6.82 OSC_BIAES
6.83 OSC_ES
6.84 OSC_FEBBE
6.85 OSC_FEBBER
6.86 OSC_FEES
6.87 OSC_FESES
6.88 OSC_FESESR
6.89 OSC_FEUAS
6.90 OSC_IAES
6.91 OSC_SES
6.92 OSC_SESR
6.93 OSC_UAS
6.94 OSPICCV
6.95 OSPITMP
6.96 OTU2SMBIP8
6.97 OTUk_BBE
6.98 OTUk_BBER
6.99 OTUk_ES
6.100 OTUk_FEBBE
6.101 OTUk_FEBBER
6.102 OTUk_FEES
6.103 OTUk_FESES
6.104 OTUk_FESESR
6.105 OTUk_FEUAS
6.106 OTUk_SES
6.107 OTUk_SESR
6.108 OTUk_UAS
6.109 PCLSOP
6.110 PCLSSN
6.111 PCLSWL
6.112 PCLSWLO
6.113 RPL
6.114 RSBBE
6.115 RSCSES
6.116 RSES
6.117 RSOFS
6.118 RSOOF
6.119 RSSES
6.120 RSUAS
6.121 SUMIOP
6.122 SUMOOP
6.123 TLB
6.124 TPL
6.125 VC3BBE
6.126 VC3CSES
6.127 VC3ES
6.128 VC3FEBBE
6.129 VC3FECSES
6.130 VC3FEES
6.131 VC3FESES
6.132 VC3FEUAS
6.133 VC3SES
6.134 VC3UAS
6.135 WCV
6.136 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.
Related Alarms
None
Procedure
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.
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.
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.
Related Alarms
None
Procedure
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.
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.
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.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.
Related Alarms
None
Procedure
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.
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.
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.4 BCV
Description
Pump Laser Back Facet Current
It includes:
Impact on System
None
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.5 CCV
Description
Pump Laser Cooling Current
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
1 If the PUMP_COOL_EXC alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.6 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.7 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,
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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.8 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.9 CRC4FEUAS
Description
CRC4 far end unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality. If the number of bit errors
exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.10 CRC4SES
Description
CRC4 severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality. If the number of bit errors
exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.11 CRC4UAS
Description
CRC4 unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality. If the number of bit errors
exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.12 EDTMP
Description
Laser temperature value
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the PUM_TEM_ALM.
----End
Related Information
None
6.13 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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the OUT_PWR_HIGH or OUT_PWR_LOW.
----End
Related Information
None
6.14 ENVTMP
Description
Board environmental temperature
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
1 If the TEMP_OVER alarm is generated, see the proper handling procedures.
----End
Related Information
None
6.15 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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the procedure for handling the BEFFEC_EXC.
----End
Related Information
None
6.16 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.
In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the optical
power to increase the OSNR.
Related Alarms
Alarm Name Correlation
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
1 Refer to the procedure for handling the BEFFEC_EXC.
----End
Related Information
None
6.17 FEC_AFT_CORER_FLOAT
Description
After FEC Correct Errored Rate (floating point values)
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the procedure for handling the BEFFEC_EXC.
----End
Related Information
None
6.18 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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the procedure for handling the BEFFEC_EXC.
----End
Related Information
None
6.19 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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None
6.20 FEC_BEF_CORER_FLOAT
Description
Before FEC Correct Errored Rate (floating point values)
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.
Related Alarms
Alarm Name Correlation
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.
BEFFEC_SD Signal degraded alarm 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
1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None
6.21 FEC_COR_0BIT_CNT
Description
Forward error correction - corrected 0 bit count
Impact on System
None
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.22 FEC_COR_1BIT_CNT
Description
Forward error correction - corrected 1 bit count
Impact on System
None
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.23 FEC_COR_BYTE_CNT
Description
Forward error correction - corrected byte count
Impact on System
None
Related Alarms
None
Procedure
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.
Related Alarms
Alarm Name Correlation
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
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
Background Block Error
The background block error means that one or more bit errors occur in the data block during
transmission.
6.26 HPCSES
Description
Higher order path consecutive 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
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the B3_SD and B3_EXC alarm.
----End
Related Information
None
6.27 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
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.
Related Alarms
Alarm Name Correlation
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
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.28 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.
Related Alarms
Alarm Name Correlation
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
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.29 HPFECSES
Description
Higher order path far end consecutive 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
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the HP_REI alarm.
----End
Related Information
Severely Errored Second
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.
The consecutive severely errored second (CSES) refers to the severely errored second (SES)
event that occurs consecutively.
The remote bit error refers to the bit error that is detected at the opposite station.
6.30 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
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the HP_REI alarm.
----End
Related Information
Remote Errored Second
The remote errored second refers to the errored second that is detected at the peer end.
6.31 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
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the HP_REI alarm.
----End
Related Information
Severely Errored Second
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.32 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.
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
Alarm Name Correlation
Procedure
1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None.
6.33 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
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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
Severely Errored Second
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.34 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.
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:
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
Alarm Name Correlation
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
1 Refer to the method of handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and
HP_UNEQalarms.
----End
Related Information
None
6.35 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
Related Alarms
None
Procedure
1 If the MODULE_COOLCUR_OVER alarm is generated, see the handling procedure of the
alarm.
2 None
----End
Related Information
None
6.36 ICTMP
Description
Module temperature
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
1 If the MODULE_TEMP_OVER alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.37 LSBIAS
Description
Laser bias current
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
1 If the TD alarm is generated, see the handling procedure of the alarm.
2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.38 LSBISA
Description
Laser bias current
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None
6.39 LSCLC
Description
Laser cooling current
It includes:
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.
Related Alarms
Alarm Name Correlation
Procedure
1 If the LSR_COOL_ALM alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.40 LSIOP
Description
Input optical power
It includes:
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.
Related Alarms
Alarm Name Correlation
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
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.
2 If no alarm is generated when the current performance value is at least 2 dB lower 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_LOW alarm.
----End
Related Information
None
6.41 LSOOP
Description
Output optical power
It includes:
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal transmission
of services.
Related Alarms
Alarm Name Correlation
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.
Procedure
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 of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
2 If no alarm is generated when the current performance value is at least 2 dB lower than the
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.
----End
Related Information
None
6.42 LSTMP
Description
Laser temperature
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
1 If the TEM_HA or TEM_LA alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.43 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.
Related Alarms
Alarm Name Correlation
B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed 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.
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
1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
6.44 MSCSES
Description
MS consecutive severely errored second
Impact on System
There are a large number of bit errors in the services. Determine the cause and solve the problem
in a timely manner because the bit errors severely affect the signal transmission quality. In
addition, the B2_EXC and B2_SD alarms may be generated.
Related Alarms
Alarm Name Correlation
B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed 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.
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
1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
6.45 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.
Related Alarms
Alarm Name Correlation
B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed 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.
R_LOF Loss of frame on receiving line. This alarm is generated when the
frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
6.46 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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
6.47 MSFECSES
Description
MS far end consecutive severely errored second
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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
6.48 MSFEES
Description
MS far end errored second
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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
6.49 MSFESES
Description
MS far end severely errored second
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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
6.50 MSFEUAS
Description
MS far end unavailable second
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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
6.51 MSSES
Description
MS severely errored second
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.
Related Alarms
Alarm Name Correlation
B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed 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.
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
1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
6.52 MSUAS
Description
MS unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
to ensure the signal transmission quality.
Related Alarms
Alarm Name Correlation
B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generated
when the B2 bit errors in the multiplex section exceed 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.
R_LOS Loss of signal on receiving line. This alarm is generated when the
receive side receives no signals.
Procedure
1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
6.53 ODU2PMBIP8
Description
ODU PM section BIP8
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.
Related Alarms
Alarm Name Correlation
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
1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None
6.54 ODUk_PM_BBE
Description
ODU PM section 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.
Related Alarms
Alarm Name Correlation
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
1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.55 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.
Related Alarms
Alarm Name Correlation
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.
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 degraded threshold.
Procedure
1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.56 ODUk_PM_ES
Description
ODU PM section errored second
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.
Related Alarms
Alarm Name Correlation
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.
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 degraded threshold.
Procedure
1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.57 ODUk_PM_FEBBE
Description
ODU PM section 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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.58 ODUk_PM_FEBBER
Description
ODU PM section ratio of far end 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.59 ODUk_PM_FEES
Description
ODU PM section far end errored second
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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.60 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,
determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure
the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.61 ODUk_PM_FESESR
Description
ODU PM section ratio of 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,
determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure
the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.62 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.63 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.
Related Alarms
Alarm Name Correlation
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 of
the optical channel data unit layer exceeds the upper threshold.
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
1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.64 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
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.
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 on the optical channel
data unit layer exceeds the degraded threshold.
Procedure
1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.65 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.
Related Alarms
Alarm Name Correlation
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.
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 on the optical channel
data unit layer exceeds the degraded threshold.
Procedure
1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.66 ODUk_TCMn_BBE
Description
ODUk TCMn section 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.
Related Alarms
Alarm Name Correlation
Procedure
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.
2 If the performance keeps deteriorating, see the handling procedure for the
ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.67 ODUk_TCMn_BBER
Description
ODUk TCMn 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.
Related Alarms
Alarm Name Correlation
Procedure
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.
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.68 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.
Related Alarms
None
Procedure
1 On the U2000, check whether the input optical power of the optical interface is within the normal
range. For the optical power specifications of the board, 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.
2 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
Related Information
None
6.69 ODUk_TCMn_ES
Description
ODUk TCMn section errored second
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.
Related Alarms
Alarm Name Correlation
Procedure
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.
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.70 ODUk_TCMn_FEBBE
Description
ODUk TCMn section 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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
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
1 On the U2000, check whether the input optical power of the optical interface is within the normal
range. For the optical power specifications of the board, 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.
2 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
Related Information
None
6.71 ODUk_TCMn_FEBBER
Description
ODUk TCMn section ratio of far end 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.
Related Alarms
None
Procedure
1 On the U2000, check whether the input optical power of the optical interface is within the normal
range. For the optical power specifications of the board, 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.
2 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
6.72 ODUk_TCMn_FEES
Description
ODUk TCMn section far end errored second
Impact on System
There are bit errors in the services on a far-end NE. 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.
Related Alarms
None
Procedure
1 Refer to the method of handling the ODUk_TCMn_BDI.
----End
Related Information
None
6.73 ODUk_TCMn_FESES
Description
ODUk TCMn 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,
determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure
the signal transmission quality.
Related Alarms
None
Procedure
1 On the U2000, check whether the input optical power of the optical interface is within the normal
range. For the optical power specifications of the board, 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.
2 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
Related Information
None
6.74 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.
Related Alarms
None
Procedure
1 Refer to the method of handling the ODUk_TCMn_SESR.
----End
Related Information
None
6.75 ODUk_TCMn_FEUAS
Description
ODUk TCMn section unavailable second
Impact on System
The far-end services are not available.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_TCMn_BDI.
----End
Related Information
None
6.76 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.
Related Alarms
Alarm Name Correlation
OTUk_LOF OTUk frame loss. The upstream station detects the LOF alarm and
then inserts IAE. The local station reports ODU1_TCMn_IAES.
Procedure
1 Refer to the method of handling the OTUk_LOF.
----End
Related Information
None
6.77 ODUk_TCMn_SES
Description
ODUk TCMn section severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.78 ODUk_TCMn_SESR
Description
ODUk TCMn section ratio of severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.79 ODUk_TCMn_UAS
Description
ODUk TCMn section unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC
----End
Related Information
None
6.80 OSC_BBE
Description
OSC Path Section Background Block Error.
Impact on System
There are bit errors in the OSC signals. 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.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.81 OSC_BBER
Description
OSC Path Section Ratio of Background Block Error.
Impact on System
When the value is not 0, it indicates that there are bit errors in the OSC signals. 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.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.82 OSC_BIAES
Description
OSC Path Backward Incoming 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.
Related Alarms
None
Procedure
1 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
Related Information
None
6.83 OSC_ES
Description
OSC Path Section Severely Errored Second.
Impact on System
There are bit errors in the OSC signals. 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.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.84 OSC_FEBBE
Description
OSC Path Far End Background Block Error.
Impact on System
If bit errors are generated in the signals 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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.85 OSC_FEBBER
Description
Osc Path Section Ratio of Far End Background Block Error.
Impact on System
When the value is not 0, it indicates that there are bit errors in the signalss. 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.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.86 OSC_FEES
Description
OSC Path Section Far End Background Block Error.
Impact on System
There are bit errors in the signals on a far-end NE. 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.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.87 OSC_FESES
Description
OSC Path Section Far End Severely Errored Second.
Impact on System
There are bit errors in the signals on a far-end NE. Determine the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.88 OSC_FESESR
Description
OSC Path Section Ratio of Far End Severely Errored Second.
Impact on System
There are bit errors in the signals on a far-end NE. Determine the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.
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
None
Procedure
1 None
----End
Related Information
None
6.89 OSC_FEUAS
Description
OSC Path Section Unavailable Second.
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.90 OSC_IAES
Description
OSC Path Section Errored Second.
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.91 OSC_SES
Description
OSC Path Section Severely Errored Second.
Impact on System
There are severely errored second in the OSC signals. Determine the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.92 OSC_SESR
Description
OSC Path Section Ratio of Severely Errored Second.
Impact on System
There are severely errored second in the signals. Determine the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.93 OSC_UAS
Description
OSC Path Section Unavailable Second.
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.94 OSPICCV
Description
The OSPICCV indicates the value of the cooling current of the laser.
It includes:
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.
Related Alarms
Alarm Name Correlation
LSR_COOL_ALM When the cooling current of the laser is beyond the specified
range, this alarm is generated.
Procedure
1 Refer to the method of handling the LSR_COOL_ALM alarm.
----End
Related Information
None
6.95 OSPITMP
Performance Event Meaning
The OSPITMP indicates the value of the temperature in the tube core of the laser.
It includes:
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.
Related Alarms
Alarm Name Correlation
TEM_HA When the temperature of the laser is higher than the upper
threshold, the alarm is reported.
TEM_LA When the temperature of the laser is less than the lower
threshold, the alarm is reported.
Procedure
1 Refer to the method of handling the TEM_HA and TEM_LA alarms.
----End
Related Information
None
6.96 OTU2SMBIP8
Description
OTU SM section BIP8
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.
Related Alarms
Alarm Name Correlation
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.
Procedure
1 If any alarm is generated, use the method of the relevant alarm to clear it.
----End
Related Information
None
6.97 OTUk_BBE
Description
OTU 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.
Related Alarms
Alarm Name Correlation
OTUk_EXC 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.
Procedure
1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.98 OTUk_BBER
Description
OTU 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.
Related Alarms
Alarm Name Correlation
OTUk_EXC OTU SM section bit interleaved parity exceeds threshold. The alarm
is generated when the number of BIP8 bit errors of the SM section in
the optical channel data unit layer exceeds the threshold.
Procedure
1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.99 OTUk_ES
Description
OTU errored second
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.
Related Alarms
Alarm Name Correlation
OTUk_EXC 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.
Procedure
1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.100 OTUk_FEBBE
Description
OTU SM section 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
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.101 OTUk_FEBBER
Description
OTU SM section ratio of far end 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.102 OTUk_FEES
Description
OTU SM section far end errored second
Impact on System
There are bit errors in the services on a far-end NE. 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.103 OTUk_FESES
Description
OTU SM section 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 because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.104 OTUk_FESESR
Description
OTU SM 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 because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.105 OTUk_FEUAS
Description
OTU SM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
6.106 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
in a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
OTUk_EXC 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.
Procedure
1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.107 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
in a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
OTUk_EXC 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.
Procedure
1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.108 OTUk_UAS
Description
OTU unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
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
Alarm Name Correlation
OTUk_EXC 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.
Procedure
1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.109 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
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.110 PCLSSN
Description
Per-channel OSNR, indicating OSNR of a channel of signal monitored by the spectrum analyzer
unit.
It includes:
Impact on System
None
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.111 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
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.112 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
Related Alarms
None
Procedure
1 None
----End
Related Information
None
6.113 RPL
Description
The RPL indicates the value of the input optical power.
It includes:
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.
Related Alarms
Alarm Name Correlation
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
1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None
6.114 RSBBE
Description
RS 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the B1_EXC.
----End
Related Information
None
6.115 RSCSES
Description
RS consecutive severely errored second
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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the B1_EXC.
----End
Related Information
None
6.116 RSES
Description
Regenerator section (RS) errored second
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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the B1_EXC.
----End
Related Information
None
6.117 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.
Related Alarms
Alarm Name Correlation
Procedure
1 Check whether the fibers are damaged and whether the connectors are properly installed. Clean
the fiber connectors.
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).
3 Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
6.118 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.
Related Alarms
Alarm Name Correlation
R_LOF When the R_OOF alarm lasts for 3 ms, the alarm is reported.
Procedure
1 Refer to the method of handling the R_OOF and R_LOF.
----End
Related Information
None
6.119 RSSES
Description
RS severely errored second
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.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the B1_EXC.
----End
Related Information
None
6.120 RSUAS
Description
RS unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
1 Refer to the method of handling the B1_EXC.
----End
Related Information
None
6.121 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.
Related Alarms
Alarm Name Correlation
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
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 or
SUM_INPWR_HI alarm.
2 If no alarm is generated when the current performance value is at least 2 dB lower 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_LOW or
SUM_INPWR_LOW alarm.
3 If an alarm is generated, see the handling procedure of the 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.122 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.
Related Alarms
Alarm Name Correlation
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
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 OUT_PWR_HIGH alarm.
2 If no alarm is generated when the current performance value is at least 2 dB lower 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 OUT_PWR_LOW alarm.
3 If an alarm is generated, see the handling procedure of the 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.123 TLB
Description
The TLB indicates the value of the bias current of the laser.
It includes:
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.
Related Alarms
Alarm Name Correlation
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
1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None
6.124 TPL
Description
The TPL indicates the value of the output optical power.
It includes:
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.
Related Alarms
Alarm Name Correlation
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
1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None
6.125 VC3BBE
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.
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 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
Alarm Name Correlation
Procedure
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.113 RPL performance.
Then, check whether bit errors occur on the service boards.
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.
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.126 VC3CSES
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:
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.
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 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
Alarm Name Correlation
Procedure
1 Refer to the 6.127 VC3ES.
----End
Reference
None.
6.127 VC3ES
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:
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.
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 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
Alarm Name Correlation
Procedure
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.
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.
----End
Reference
None.
6.128 VC3FEBBE
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:
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 service 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 becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
Procedure
1 Refer to the 6.125 VC3BBE to handle the NE at the opposite end.
----End
Reference
None.
6.129 VC3FECSES
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.
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 service 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 becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
Procedure
1 Refer to the 6.130 VC3FEES.
----End
Reference
None.
6.130 VC3FEES
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:
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 service 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 becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
Procedure
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.
----End
Reference
None.
6.131 VC3FESES
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:
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 service 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 becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
Procedure
1 Refer to the 6.130 VC3FEES.
----End
Reference
None.
6.132 VC3FEUAS
Possible Causes
VC3FEUAS 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 service 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 becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
Procedure
1 Refer to the 6.130 VC3FEES.
----End
Reference
None
6.133 VC3SES
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:
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.
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 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
Alarm Name Correlation
Procedure
1 Refer to the 6.127 VC3ES.
----End
Reference
None.
6.134 VC3UAS
Possible Causes
VC3UAS indicates the period of time that the unavailable time (UAT) state lasts.
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.
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 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
Alarm Name Correlation
Procedure
1 Refer to the 6.127 VC3ES.
----End
Reference
None
6.135 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.
Related Alarms
Alarm Name Correlation
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.
Procedure
1 If the PUM_BCM_ALM alarm is generated, see the handling procedure of the alarm.
2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.136 XCSTMP
Description
Board environmental temperature
It includes:
Impact on System
Excessively high or low board temperature might cause faults such as degradation of the board
working performance and bit errors.
Related Alarms
Alarm Name Correlation
Procedure
1 If the TEMP_OVER alarm is generated, see the proper handling procedures.
----End
Related Information
None
7 Event List
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.
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.
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.
8 Event Processing
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
handling procedures.
NOTE
In the case of an event, refer to its handling procedure to clear it; if this event persists, contact a customer
service technician of Huawei for troubleshooting.
When you view an event on the network management system, select the event. In the Detail
Description in the Event Details field display 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 limit
8.6 RMON module performance value is lower than the lower threshold
8.7 1+1 Equipment Level Protection Switching Event Report
Attribute
Event Severity Event Type
Major Equipment
Parameter
Parameter Description
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 cross 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, refer to the Feature
Description.
----End
Related Information
None
Attribute
Event Severity Event Type
Major Equipment
Parameter
Parameter Description
Parameter Description
Impact on System
If an adjustment success is reported, the system BER is lowered and the signal transmission
quality is 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.
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.
1. Ignore the event.
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, refer to section "Rectifying Bit Errors" 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.
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 type.
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, refer
to the Product Description.
l Cause 9: The board incorrectly responds to the command.
1. Find the board according to the NE ID and slot number indicated by event parameters
and query alarms related to the board. Handle the alarms by seeing 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, refer to 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 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 by seeing the Handling Procedure parts for
respective alarms.
----End
Related Information
None
Attribute
Event Severity Event Type
Major Communication
Parameter
Parameter Description
Parameter Description
Parameter Description
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 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.
1. Ignore the event.
----End
Related Information
None
Attribute
Event Severity Event Type
Major Communication
Parameter
Parameter Description
Parameter Description
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 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.
1. Ignore the event.
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
Attribute
Event Severity Event Type
Minor Communication
Parameter
Parameter Description
Parameter 1 Indicates the slot ID, port number and channel number,
such as 1-LOG-2(ETHER):1.
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 large 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 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 large or the receive optical power is
abnormal.
1. Check whether the received optical power of the interface is within the normal range
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, takes
handling 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 untidy.
1. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
see the Supporting Tasks.
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
Attribute
Event Severity Event Type
Minor Communication
Parameter
Parameter Description
Parameter 1 Indicates the slot ID, port number and channel number,
such as 1-LOG-2(ETHER):1.
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
Attribute
Event Severity Event Type
Critical Equipment
Parameter
Parameter Description
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, 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.
1. Ignore the event.
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
A Glossary
Numerics
1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection
SNC/trail and a permanent bridge. At the source end, the normal traffic signal is
permanently bridged to both the working and protection SNC/trail. At the sink end, the
normal traffic signal is selected from the better of the two SNCs/trails. Due to the
permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic
signal to be provided.
A
AC alternating current
ACK Acknowledgement
ACL Access Control List
Add/drop wavelength Add/drop wavelength refers to the wavelength that carries the add/drop services in the
OADM equipment.
ADM add/drop multiplexer
Administrative Unit The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
Administrator A user who has authority to access all the Management Domains of the EMLCore
product. He has access to the whole network and to all the management functionalities.
ADSL Asymmetric Digital Subscriber Line
AFEC Advanced Forward Error Correction
AGC Automatic Gain Control
AID Access Identifier
AIS See Alarm Indication Signal
alarm A message reported when a fault is detected by a device or by the network management
system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
alarm cable The cable for generation of visual or audio alarms.
alarm cascading The shunt-wound output of the alarm signals of several subracks or cabinets.
alarm cause A single disturbance or fault may lead to the detection of multiple defects. A fault cause
is the result of a correlation process which is intended to identify the defect that is
representative of the disturbance or fault that is causing the problem.
alarm indication On the cabinet of an NE, there are four indicators in different colors indicating the current
status of the NE. When the green indicator is on, it indicates that the NE is powered on.
When the red indicator is on, it indicates that a critical alarm is generated. When the
orange indicator is on, it indicates that a major alarm is generated. When the yellow
indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on
the front panel of a board indicates the current status of the board. (Metro)
Alarm Indication A code sent downstream in a digital network as an indication that an upstream failure
Signal has been detected and alarmed. It is associated with multiple transport layers.
alarm mask On the host, an alarm management method through which users can set conditions for
the system to discard (not to save, display, or query for) the alarm information meeting
the conditions.
alarm severity The significance of a change in system performance or events. According to ITU-T
recommendations, an alarm can have one of the following severities: Critical, Major,
Minor, Warning.
Alarm suppression A function used not to monitor alarms for a specific object, which may be the
networkwide equipment, a specific NE, a specific board and even a specific function
module of a specific board.
alarm type Classification of alarms with different attributes. There are six alarm types as following:
Communication: alarm indication related with information transfer. Processing: alarm
indication related with software or information processing Equipment: alarm indication
related with equipment fault Service: alarm indication related with QoS of the equipment
Environment: alarm related with the environment where the equipment resides, usually
generated by a sensor Security: alarm indication related with security
ALC Automatic Level Control
ALC link A piece of end-to-end configuration information, which exists in the equipment (single
station) as an ALC link node. Through the ALC function of each node, it fulfils optical
power control on the line that contains the link.
ALC node The ALC functional unit. It corresponds to the NE in a network. The power detect unit,
variable optical attenuator unit, and supervisory channel unit at the ALC node work
together to achieve the ALC function.
ALS See automatic laser shutdown
ANSI American National Standard Institute
APD See Avalanche Photo Diode
APE Automatic Power Equilibrium
API Access Point Identifier
B
BA Booster Amplifier
backup A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BBE Background Block Error
BBER Background Block Error Ratio
BC boundary clock
BDI Backward Defect Indication
BEI Backward Error Indication
BER See Bit Error Rate
BIAE Backward Incoming Alignment Error
BIOS Basic Input/Output System
BIP Bit-Interleaved Parity
BIP-8 Bit Interleaved Parity order 8
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
Bit Error Rate Ratio of received bits that contain errors. BER is an important index used to measure the
communications quality of a network.
BITS Building Integrated Timing Supply System
BMC Best Master Clock
BNC Bayonet-Neill-Concelman
BOM Bill of Material
bound path Binding several serial paths into a parallel path, thus improving the data throughput
capacity.
BPDU Bridge Protocol Data Unit
BPS Board-level Protection Switching
BRAS Broadband Remote Access Server
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
Broadcast service The unidirectional services from one service source to multiple service sinks are called
the broadcast service.
BWS Backbone WDM System
C
cable tie The tape used to bind the cables.
CAPEX Capital Expenditure
captive nut Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses but
are more commonly used in the hobby for engine fixing (securing engine mounts to the
firewall), wing fixings, and undercarriage fixing.
CAR Committed Access Rate
CBS Committed Burst Size
CC Continuity Check
CCI Connection Control Interface
CCM Continuity Check Message
CD Chormatic Dispersion
CDMA Code Division Multiple Access; Code Division Multiple Access; Code Division Multiple
Access
CE Customer Edge
CENELEC European Committee for Electrotechnical Standardization
Centralized alarm The system that gathers all the information about alarms into a certain terminal console.
system
CF Compact Flash
CGMP Cisco Group management Protocol
channel spacing The centre-to-centre difference in frequency or wavelength between adjacent channels
in a WDM device.
CIR Committed Information Rate
CIST Common and Internal Spanning Tree
CLEI Common Language Equipment Identification
client A device that sends requests, receives responses, and obtains services from the server.
CLNP Connectionless Network Protocol
CLNS Connectionless Network Service
clock tracing The method to keep the time on each node being synchronized with a clock source in a
network.
CM See Configuration management
CMEP Connection monitoring end point
CMI Coded Mark Inversion
concatenation A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.
Configuration 1. A network management function defined by the International Standards Organization
management (ISO). It involves installing, reinitializing & modifying hardware & software. 2.
Configuration Management (CM) is a system for collecting the configuration
information of all nodes in the network.
configure To set the basic parameters of an operation object.
congestion An extra intra-network or inter-network traffic resulting in decreasing network service
efficiency.
Connecting plate A metallic plate which is used to combine two cabinets.
connecting plate for A plate that connects two adjacent cabinet together at the cabinet top for fixing.
combining cabinets
Connection point A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
convergence 1. A process in which multiple channels of low-rate signals are multiplexed into one or
several channels of required signals. 2. It refers to the speed and capability for a group
of networking devices to run a specific routing protocol. It functions to keep the network
topology consistent.
Convergence service A service that provides enhancements to an underlying service in order to provide for
the specific requirements of the convergence service user.
CORBA Common Object Request Broker Architecture
corrugated pipe Used to protect optical fibers.
CoS Class of Service
CPLD Complex Programmable Logical Device
CPU Central Processing Unit
D
DAPI Destination Access Point Identifiers
Data backup A method that is used to copy key data to the standby storage area, to prevent data loss
in the case of the damage or failure in the original storage area.
DBPS Distribute board protect system
DC Direct Current
DCC Data Communication Channels
DCF See Dispersion Compensation Fiber
DCM Dispersion Compensation Module
DCM frame A frame which is used to hold the DCM (Dispersion Compensation Module).
DCN Data Communication Network
DDF Digital Distribution Frame
DDN Digital Data Network
Dense Wavelength Dense Wavelength Division Multiplexing. The technology utilizes the characteristics of
Division Multiplexing broad bandwidth and low attenuation of single mode optical fiber, employs multiple
wavelengths with specific frequency spacing as carriers, and allows multiple channels
to transmit simultaneously in the same fiber.
DHCP Dynamic Host Configuration Protocol
diamond-shaped nut A type of nut that is used to fasten the wiring frame to the cabinet.
Dispersion Dispersion Compensation Fiber. A kind of fiber which uses negative dispersion to
Compensation Fiber compensate for the positive dispersion of transmitting fiber to maintain the original shape
of the signal pulse.
DLAG Distribute Link Aggregation Group
DMUX demultiplexer
DNI Dual Node Interconnection
DRDB Dynamic Random Database
DRZ Differential Phase Return to Zero
E
E2E End to End
EAPE Enhanced Automatic Power Pre-Equilibrium
EBS Excess Burst Size
ECC Embedded Control Channel
EDFA See Erbium Coped Fiber Amplifier
eDQPSK Enhanced Differential Quadrature Phase Shift Keying
EFM Ethernet in the First Mile
ejector lever A lever for removing circuit boards from an electronic chassis.
Electric Supervisory A technology realizes the communication among all the nodes and transmits the
Channel monitoring data in the optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
EMC Electromagnetic Compatibility
EMI Electromagnetic Interference
EMS Element Management System
Enterprise System A path protocol which connects the host with various control units in a storage system.
Connection It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
EPL Ethernet Private Line
EPLAN Ethernet Private local area network
Erbium Coped Fiber Erbium Coped Fiber Amplifier. An optical device that amplifies the optical signals. The
Amplifier device uses a short length of optical fiber doped with the rare-earth element Erbium and
the energy level jump of Erbium ions activated by pump sources. When the amplifier
passes the external light source pump, it amplifies the optical signals in a specific
wavelength range.
ESC See Electric Supervisory Channel
F
F1 byte The user path byte, which is reserved for the user, but is typically special for network
providers. The F1 byte is mainly used to provide the temporary data or voice path for
special maintenance objectives. It belongs to the regenerator section overhead byte.
FAS Frame Alignment Signal
fault A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources and intentional settings.
FBG Fiber Bragg Grating
FC Fiber Channel
FDB Flash Database
FDDI Fiber Distributed Data Interface
FE Fast Ethernet
FEC See Forward Error Correction
Fiber Connector A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).
Fiber Management A device used to coil up extra optical fibers.
Tray
fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
fiber spool A device used in coiling up an extra length of optical fibers.
Fiber trough The trough that is used for routing fibers.
fiber/cable Fiber & Cable is the general name of optical fiber and cable. It refers to the physical
entities that connect the transmission equipment, carry transmission objects (user
information and network management information) and perform transmission function
in the transmission network. The optical fiber transmits optical signal, while the cable
transmits electrical signal. The fiber/cable between NEs represents the optical fiber
connection or cable connection between NEs. The fiber/cable between SDH NEs
represents the connection relation between NEs. At this time, the fiber/cable is of optical
fiber type.
FIFO First In First Out
Flow An aggregation of packets that have the same characteristics. On the network
management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation. At present,
two flows are supported: port flow and port+VLAN flow. Port flow is based on port ID
and port+VLAN flow is based on port ID and VLAN ID. The two flows cannot coexist
in the same port.
FMT See Fiber Management Tray
FOADM Fixed Optical add/drop Multiplexer
FOAs fixed optical attenuators
Forward Error A bit error correction technology that adds the correction information to the payload at
Correction the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
FPGA Field Programmable Gate Array
frame A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements pre-
specified by the sending and receiving parties.
FTP File Transfer Protocol
Full duplex The system that can transmit information in both directions on a communication link.
On the communication link, both parties can send and receive data at the same time.
FWM Four-Wave Mixing
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.
Gateway IP When an NE accesses a remote network management system or NE, a router can be used
to enable the TCP/IP communication. In this case, the IP address of the router is the
gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot
identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP
networks. An NE may have multiple IP addresses, for example, one IP address of the
network and one IP address of the Ethernet port.
gateway network A network element that is used for communication between the NE application layer and
element the NM application layer
GB Gigabit
GCC General Communication Channel
GCP GMPLS control plan
GE Gigabit Ethernet
GE ADM The technology can optimize GE service transport over WDM for Metro network. It
owns the capability of GE service convergence and grooming and benefits to use the
network resource more effectively.
GFF Gain Flattening Filter
GFP Generic Framing Procedure
GMPLS Generalized Multi-Protocol Label Switching
GND Ground
GNE See gateway network element
GPS Global Positioning System
GSSP General Snooping and Selection Protocol
GUI Graphic User Interface
guide rail Components to guide, position, and support plug-in boards.
H
Hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
HCS Hierarchical Cell Structure
HDB High Density Bipolar Code
HDLC High level Data Link Control
History alarm The confirmed alarms that have been saved in the memory and other external memories.
History Performance The performance data that is stored in the history register or that is automatically reported
Data and stored in the NMS.
I
IAE Incoming Alignment Error
IC Integrated Circuit
ICC ITU Carrier Code
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
Jitter transfer The physical relationship between jitter applied at the input port and the jitter appearing
at the output port.
M
MA Maintenance Associations
MAC Media Access Control
MADM Multiple Add/drop Multiplexer
main topology A interface that displays the connection relation of NEs on the NMS (screen display).
The default client interface of the NMS, 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.
MAN See Metropolitan Area Network
Management The information that is used for network management in a transport network.
information
Mapping A procedure by which tributaries are adapted into virtual containers at the boundary of
an SDH network.
Marking-off template A quadrate cardboard with four holes. It is used to mark the positions of the installation
holes for the cabinet.
MD Maintenance Domain
MDB Memory Database
MDF Main Distribution Frame
MDP Message Dispatch Process
MDS Message Distribution Service Software
ME Maintenance Entities
mean launched power The average power of a pseudo-random data sequence coupled into the fiber by the
transmitter.
MEP Maintenance End Point
Metropolitan Area A metropolitan area network (MAN) is a network that interconnects users with computer
Network resources in a geographic area or region larger than that covered by even a large local
area network (LAN) but smaller than the area covered by a wide area network (WAN).
The term is applied to the interconnection of networks in a city into a single larger
network (which may then also offer efficient connection to a wide area network). It is
also used to mean the interconnection of several local area networks by bridging them
with backbone lines. The latter usage is also sometimes referred to as a campus network.
MFAS MultiFrame Alignment Signal
N
NA No Acknowledgment
O
OA See Optical Amplifier
OADM Optical Add/Drop Multiplexer
OADM frame A frame which is used to hold the OADM boards.
OAM Operation, Administration and Maintenance
OC See Optical Coupler
OCh Optical Channel
OCI Open Connection Indication
OCP See Optical Channel Protection
OD Optical Demultiplexing
ODB Optical Duobinary
ODF Optical Distribution Frame
ODU Optical Channel Data Unit
ODUk Optical Channel Data Unit-k
OEM Original Equipment Manufacturer
OEQ Optical Equalizer
OFC Open Fiber Control
OLA See Optical Line Amplifier
OLP See Optical Line Protection
OM Optical Multiplexing
OMS Optical multiplex section
ONE See Optical NE
Online Help The capability of many programs and operating systems to display advice or instructions
for using their features when so requested by the user.
OOF Out of Frame
OPA Optical Power Adjust
OPEX OPeration EXpenditure
OPS optical physical section
Optical Amplifier Devices or subsystems in which optical signals can be amplified by means of the
stimulated emission taking place in a suitable active medium.
optical attenuator A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
Optical Channel In an optical transmission link that contains multiple wavelengths, when a certain
Protection wavelength goes faulty, the services at the wavelength can be protected if the optical
channel protection is configured.
Optical Connector A component normally attached to an optical cable or piece of apparatus for the purpose
of providing frequent optical interconnection/disconnection of optical fibers or cables.
Optical Coupler A coupler for coupling light in an optical system. Multiple discrete layers of alternating
optical materials have respective first and second indexes of refraction. The thickness of
each layer is a fraction of the light wavelength.
Optical Line Amplifier A piece of equipment that functions as an OLA to directly amplify the input optical
signals and to compensate for the line loss. Currently, the key component of the OLA is
the EDFA amplifier.
Optical Line Protection A protection mechanism that adopts dual fed and selective receiving principle and single-
ended switching mode. In this protection, two pairs of fibers are used. One pair of fibers
forms the working route. The working route transmits line signals when the line is
normal. The other pair of fibers forms the protection route. The protection route carries
line signals when the line is broken or the signal attenuation is extremely large.
Optical NE Optical Network Element (ONE) is the transport entity that implements the NE functions
(terminal multiplexing, add/drop multiplexing, cross-connection and regeneration) in a
DWDM layer network. The types of ONEs include OTM, OADM, OLA, REG and OXC.
The locating of an ONE is equivalent to that of a common NE. In a view, an ONE is
displayed with an icon, like a common NE and its alarm status can be displayed with
colors. Logically, an ONE consists of different subracks. Like a common NE, an ONE
cannot be expanded or entered like a sub-network. Similar to a common NE, an ONE
provides a list of the subracks that form the NE to display the board layout.
Optical Signal-to-Noise Optical Signal-to-Noise Ratio. The most index of measuring the performance of a
Ratio DWDM system. The ratio of signal power and noise power in a transmission link. That
is, OSNR = signal power/noise power.
Optical Spectrum A device that allows the details of a region of an optical spectrum to be resolved.
Analyzer Commonly used to diagnose DWDM systems.
Optical Supervisory Optical Supervisory Channel. A technology realizes communication among nodes in
channel optical transmission network and transmits the monitoring data in a certain channel (the
wavelength of the working channel for it is 1510 nm and that of the corresponding
protection one is 1625 nm).
Optical switch A passive component possessing two or more ports which selectively transmits, redirects,
or blocks optical power in an optical fiber transmission line.
Optical wavelength In the optical wavelength shared protection (OWSP), the service protection between
shared protection different stations can be achieved by using the same wavelength, realizing wavelength
sharing. This saves the wavelength resources and lowers the cost. The optical wavelength
shared protection is mainly applied to the ring network which is configured with
distributed services. It is achieved by using the OWSP board. In a ring network where
services are distributed at adjacent stations, each station requires one OWSP board. Then,
two wavelengths are enough for configuring the shared protection to protect one service
among stations.
OPU Optical Channel Payload Unit
OPUk Optical Channel Payload Unit-k
PE Provider Edge
Performance register Performance register is the memory space for performance event counts, including 15-
min current performance register, 24-hour current performance register, 15-min history
performance register, 24-hour history performance register, UAT register and CSES
register. The object of performance event monitoring is the board functional module, so
every board functional module has a performance register. A performance register is
used to count the performance events taking place within a period of operation time, so
as to evaluate the quality of operation from the angle of statistics.
PET Polyester
PGND Protection Ground
PHY Physical Sublayer & Physical Layer
PID Photonics Integrated Device
PIM-DM Protocol Independent Multicast-Dense Mode
PIM-SM Protocol Independent Multicast-Sparse Mode
PIN Photodiode. A semiconductor detector with an intrinsic (i) region separating the p- and
n-doped regions. It has fast linear response and is used in fiber-optic receivers.
PIR Peak Information Rate
PLL Phase-Locked Loop
PM Path Monitoring
PMD Polarization Mode Dispersion
PMI Payload Missing Indication
POH Path Overhead
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.
Polarization Dependent The maximum, peak-to-peak insertion loss (or gain) variation caused by a component
Loss when stimulated by all possible polarization states. It is specified in dB units.
POS Packet Over SDH/SONET
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
power distribution box A power box through which the power enters the cabinet and is re-distributed to various
components, at the mean time, the Power Distribution Box protects the electric devices
from current overload.
PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PRBS Pseudo Random Binary Sequence
PRC Primary Reference Clock
PRI Primary Rate Interface
protection ground A cable which connects the equipment and the protection grounding bar. Usually, one
cable half of the cable is yellow; while the other half is green.
Protection path A specific path that is part of a protection group and is labeled protection.
Protection policy In case the service route provides multiple service protections, different protection
policies can be selected as required. Protection policy refers to the protection mode given
the priority in use for the trail: protection, no protection, and extra traffic. Of the above,
the protection preference is divided into trail protection and subnet connection
protection.
Protection service A specific service that is part of a protection group and is labeled protection.
PSI Payload Structure identifier
PSN Packet Switched Network
PSTN Public Switched Telephone Network
PT Payload Type
PTN Packet Transport Network
PTP Point-To-Point
Q
QA Q Adaptation
QoS See Quality of Service
Quality of Service Quality of Service, which determines the satisfaction of a subscriber for a service. QoS
is influenced by the following factors applicable to all services: service operability,
service accessibility, service maintainability, and service integrity.
R
RAI Remote alarm indication
RAM Random Access Memory
Reflectance The ratio of the reflected optical power to the incident optical power.
REG A piece of equipment or device that regenerates electrical signals.
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.
REI Remote Error Indication
RF Radio Frequency
RFC Requirement for Comments
RFI Remote Failure indication
RIP Routing Information Protocol
RMON Remote Network Monitoring
RNC Radio Network Controller
ROADM Reconfiguration Optical Add/drop Multiplexer
RPU ROPA Pumping Unit
RS Reed-Solomon
RS232 In the asynchronous transfer mode and there is no hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RSTP Rapid Spanning Tree Protocol
RSVP Resource Reservation Protocol
RSVP-TE resource reservation setup protocol with traffic-engineering extensions;Resource
Reservation Protocol-Traffic Engineering
RZ Return to Zero code
RZ-DQPSK RZ-Enhanced Differential Quadrature Phase Shift Keying
S
S1 byte In an SDH network, each network element traces step by step to the same clock reference
source through a specific clock synchronization path, thus realizing the synchronization
of the whole network. If a clock reference source traced by the NE is lost, the clock of
this NE will trace another clock reference source of lower level. To implement protection
switching of clocks in the whole network, the NE must learn about the clock quality
information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to
transmit the network synchronization status information. It uses the lower four bits of
the multiplex section overhead S1 byte to indicate 16 types of synchronization quality
grades. The specific coding information is shown in the following table. Auto protection
switching of clocks in the synchronous network can be implemented by using S1 byte
and following the certain switching protocol.
Safe control switch The APR safe switch is set in consideration of the long-span networking requirement,
which cannot allow too low output optical power. If the safe control switch is turned off,
APR restarting optical power is the specified output power of the OAU. Otherwise, the
APR restarting optical power is restricted to less than 10 dBm.
SAN See Storage Area Network
SAP Service Access Point
SAPI Source Access Point Identifiers
SBS Stimulated Brillouin Scattering
SC Square Connector
SD Signal Degrade
SD trigger flag SD stands for signal degrade. The SD trigger flag determines whether to perform a
switching when SD occurs. The SD trigger flag can be set by using the network
management system.
SDH Synchronous Digital Hierarchy
SDI Serial Digital Interface
SDP Serious Disturbance Period
Search domain Search field refers to the range of IP addresses being searched. In the TCP/IP, the IP
addresses include: Category A address (1.0.0.0---126.255.255.255). For example,
10.*.*.*, whose search field is 10.255.255.255, all 10.*.*.* to be searched. Category B
address (128.0.0.0---191. 255. 255. 255). For example, 129.9.*.*, whose search field is
129.9.255.255, all 129.9.*.* to be searched. Category C address (192.0.0.0---223. 255.
255. 255). For example, 192.224.9.*, whose search field is 192.224.9.255, all
192.224.9.* to be searched. Category D address (224.0.0.0---230.255.255.255), which
is reserved. Category E address (240.0.0.0---247.255.255.255), which is reserved. Net-
id 127.*.*.*, in which .*.*.* can be any number. This net-ID is a local address.
Self-healing Self-healing is the establishment of a replacement connection by network without the
NMC function. When a connection failure occurs, the replacement connection is found
by the network elements and rerouted depending on network resources available at that
time.
Service protection A measure that ensures that the services can be received at the receive end.
SES Severely Errored Seconds
SETS Synchronous Equipment Timing Source
SF See Signal Fail
SFP Small Form-Factor Pluggable
SFTP Secure File Transfer Protocol
shock-proof reinforce A process by which the cabinet is fastened to the wiring frame or the top of the equipment
room so that the cabinet stands stably.
shortcut menu A menu that is displayed when right-clicking an object’s name or icon. This is also
referred to a context menu.
Side Mode Suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total
Ratio source spectrum to the second largest peak.
side trough The trough on the side of the cable rack, which is used to place nuts so as to fix the
cabinet.
signal cable Common signal cables cover the E1 cable, network cable, and other non-subscriber
signal cable.
Signal Fail Signal Fail. A signal that indicates the associated data has failed in the sense that a near-
end defect condition (non-degrade defect) is active.
SLA Service Level Agreement
SLIP Serial Line Internet Protocol
SLM Single Longitudinal Mode
SLTE Submarine Line Terminal Equipment
SM Section Monitoring
SMF Single-Mode Fiber
SMSR See Side Mode Suppression Ratio
SNCP SubNetwork Connection Protection
SNCTP Subnetwork Connection Tunnel Protection
SNMP Simple Network Management Protocol
synchronize NE time To send the system time of the server of the network management system to NEs so as
to synchronize all NEs with the server.
T
TCM Tandem Connection Monitoring
TCP Transmission Control Protocol
TDM Time Division Multiplexing
TE Traffic Engineering
TFTP Trivial File Transfer Protocol
TIM Trace Identifier Mismatch
TL1 Transaction Language 1
TLV Type/Length/Value
TM Terminal Multiplexer
TMN Telecommunication Management Network
TP traffic Policing
trail A type of transport entity, mainly engaged in transferring signals from the input of the
trail source to the output of the trail sink, and monitoring the integrality of the transferred
signals.
trTCM Two Rate Three Color Marker
TTI Trail Trace Identifier
TTL Time To Live
TU Tributary Unit
TUG Tributary Unit Group
TV Television
U
UAS Unavailable Second
UAT Unavailable time event
UDP User Datagram Protocol
underfloor cabling The cables connected cabinets and other devices are routed underfloor.
UNI User Network Interface
Unprotected Pertaining to the transmission of the services that are not protected, the services cannot
be switched to the protection channel if the working channel is faulty or the service is
interrupted, because protection mechanism is not configured.
upload An operation to report some or all configuration data of an NE to the NMS(Network
Management system). The configuration data then covers the configuration data stored
at the NMS side.
Upper subrack The subrack close to the top of the cabinet when a cabinet contains several subracks.
User A client user of the NMS. The user name and password uniquely identifies the operation
rights of a user in the NMS.
user group The group of users that share a specific service, for example, user groups of the virtual
private network (VPN) and enterprise private branch exchange (PBX). The user group
is set to aim at the special tariff, service and reward. A user can belong to none or multiple
user groups.
UTC Universal Time Coordinated
V
VB Virtual Bridge
VC Virtual Container
VCG Virtual Concatenation Group
VCI Virtual Channel Identifier
VLAN Virtual Local Area Network
VMUX Multiplexing/Demultiplexing Board with VOA
VOA Variable Optical Attenuator
VoIP Voice over IP
VPI Virtual Path Identifier
VPN Virtual Private Network
VRRP Virtual Router Redundancy Protocol
W
WAN Wide Area Network
Wavelength protection The wavelength protection group is important to describe the wavelength protection
group structure. Its function is similar to that of the protection subnet in the SDH NE. The
wavelength path protection can only work with the correct configuration of the
wavelength protection group.
WDM Wavelength Division Multiplexing
WEEE Waste Electrical and Electronic Equipment
Working path The channels allocated to transport the normal traffic.
Working service A specific service that is part of a protection group and is labeled working.
WRR Weighted Round Robin
WSS Wavelength Selective SwitchingS
WTR Wait-to-Restore
WXCP Wavelength Cross-Connection Protection
WXCP service The WXCP service is also called the GE ADM protection service. The WXCP is a type
of channel protection based on ring network. It adopts the dual fed and selective receiving
principle and uses the cross-connection function to achieve service switching between
working and protection channels.
X
XFP 10Gbit/s Small Form-Factor Pluggable
XPM Cross-Phase Modulation