00482837-Alarms and Performance Events Reference (V100R007 - 08)

OptiX BWS 1600G Backbone DWDM Optical Transmission System V100R007
Alarms and Performance Events Reference
Issue Date Part Number
08 2011-10-30 00482837
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property 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.
OptiX BWS 1600G Backbone DWDM Optical Transmission System Alarms and Performance Events Reference
Contents
Contents
About This Document.....................................................................................................................1 1 Overview......................................................................................................................................1-1
1.1 Alarm Level.....................................................................................................................................................1-2 1.2 Alarm Category...............................................................................................................................................1-2 1.3 Performance Event Category..........................................................................................................................1-3 1.4 Alarm Signal Flow..........................................................................................................................................1-4 1.4.1 Overview................................................................................................................................................1-4 1.4.2 Non-Convergent OTU Processing Standard SDH Signals....................................................................1-6 1.4.3 Non-Convergent OTU Processing Standard OTN Signals....................................................................1-9 1.4.4 Convergent OTU Processing Standard SDH Signals...........................................................................1-12 1.4.5 Convergent OTU Processing Standard OTN Signals..........................................................................1-15 1.4.6 Regenerating OTU...............................................................................................................................1-18 1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function.............................................1-20 1.4.8 Convergence OTU Processing the GE Standard Signals.....................................................................1-22 1.4.9 Non-Convergence OTU Board Processing the 10GE Standard Signals..............................................1-26 1.5 Suppression Relation of Alarms....................................................................................................................1-29 1.5.1 Suppression Relation of OTU Service Alarms on WDM Side............................................................1-29 1.5.2 Suppression Relation of OTU Service Alarms on client Side.............................................................1-30 1.6 Performance Event Suppression by Alarms..................................................................................................1-31
2 Alarm List....................................................................................................................................2-1
2.1 Product Alarm List..........................................................................................................................................2-2 2.1.1 Alarm List A...........................................................................................................................................2-2 2.1.2 Alarm List B...........................................................................................................................................2-2 2.1.3 Alarm List C...........................................................................................................................................2-3 2.1.4 Alarm List D...........................................................................................................................................2-3 2.1.5 Alarm List E...........................................................................................................................................2-3 2.1.6 Alarm List F...........................................................................................................................................2-4 2.1.7 Alarm List H...........................................................................................................................................2-4 2.1.8 Alarm List I............................................................................................................................................2-4 2.1.9 Alarm List J............................................................................................................................................2-5 2.1.10 Alarm List K.........................................................................................................................................2-5 2.1.11 Alarm List L.........................................................................................................................................2-5 Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
OptiX BWS 1600G Backbone DWDM Optical Transmission System Alarms and Performance Events Reference 2.1.12 Alarm List M........................................................................................................................................2-5 2.1.13 Alarm List N.........................................................................................................................................2-6 2.1.14 Alarm List O.........................................................................................................................................2-6 2.1.15 Alarm List P.........................................................................................................................................2-9 2.1.16 Alarm List R.......................................................................................................................................2-10 2.1.17 Alarm List S.......................................................................................................................................2-11 2.1.18 Alarm List T.......................................................................................................................................2-12 2.1.19 Alarm List V.......................................................................................................................................2-13 2.1.20 Alarm List W......................................................................................................................................2-13
2.2 Board Alarm List...........................................................................................................................................2-13 2.2.1 D40 Board Alarm List..........................................................................................................................2-13 2.2.2 DCP Board Alarm List.........................................................................................................................2-14 2.2.3 ELOG/ELOGS Board Alarm List........................................................................................................2-14 2.2.4 ETMX/ETMXS Board Alarm List.......................................................................................................2-15 2.2.5 FDG Board Alarm List.........................................................................................................................2-16 2.2.6 FIU Board Alarm List..........................................................................................................................2-17 2.2.7 FMU Board Alarm List........................................................................................................................2-18 2.2.8 HBA Board Alarm List........................................................................................................................2-18 2.2.9 ITL Board Alarm List..........................................................................................................................2-18 2.2.10 LBE/LBES Board Alarm List............................................................................................................2-18 2.2.11 LBF/LBFS Board Alarm List.............................................................................................................2-19 2.2.12 LOG/LOGS Board Alarm List...........................................................................................................2-21 2.2.13 LQM Board Alarm List......................................................................................................................2-22 2.2.14 LU40 Board Alarm List.....................................................................................................................2-23 2.2.15 LU40S Board Alarm List...................................................................................................................2-24 2.2.16 LUR40/LUR40S Board Alarm List...................................................................................................2-26 2.2.17 LWC1 Board Alarm List....................................................................................................................2-26 2.2.18 LWF/LWFS Board Alarm List..........................................................................................................2-27 2.2.19 LWX Board Alarm List......................................................................................................................2-29 2.2.20 M40 Board Alarm List.......................................................................................................................2-29 2.2.21 MCA Board Alarm List......................................................................................................................2-30 2.2.22 MR2 Board Alarm List......................................................................................................................2-30 2.2.23 MWA Board Alarm List....................................................................................................................2-30 2.2.24 MWF Board Alarm List.....................................................................................................................2-30 2.2.25 OAU Board Alarm List......................................................................................................................2-30 2.2.26 OBU Board Alarm List......................................................................................................................2-31 2.2.27 OLP Board Alarm List.......................................................................................................................2-31 2.2.28 OPU Board Alarm List.......................................................................................................................2-31 2.2.29 PMU Board Alarm List......................................................................................................................2-31 2.2.30 RMU9 Board Alarm List....................................................................................................................2-32 2.2.31 RPC Board Alarm List.......................................................................................................................2-32 2.2.32 SC1/SC2 Board Alarm List................................................................................................................2-32 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
Contents
2.2.33 SCC Board Alarm List.......................................................................................................................2-33 2.2.34 TMR/TMRS Board Alarm List..........................................................................................................2-34 2.2.35 TMX/TMXS Board Alarm List..........................................................................................................2-34 2.2.36 TMX40/TMX40S Board Alarm List..................................................................................................2-35 2.2.37 TRC1 Board Alarm List.....................................................................................................................2-37 2.2.38 V40 Board Alarm List........................................................................................................................2-37 2.2.39 VA4 Board Alarm List.......................................................................................................................2-38 2.2.40 VOA Board Alarm List......................................................................................................................2-38 2.2.41 WMU Board Alarm List....................................................................................................................2-38 2.2.42 WSD9 Board Alarm List....................................................................................................................2-38 2.2.43 WSM9 Board Alarm List...................................................................................................................2-38 2.2.44 WSMD2 Board Alarm List................................................................................................................2-39 2.2.45 WSMD4 Board Alarm List................................................................................................................2-39
3 Alarm Processing........................................................................................................................3-1
3.1 Common Alarm Processing............................................................................................................................3-2 3.1.1 ALM_DATA_RLOS..............................................................................................................................3-2 3.1.2 ALM_DATA_TLOS..............................................................................................................................3-4 3.1.3 B1_EXC.................................................................................................................................................3-5 3.1.4 BEFFEC_EXC.......................................................................................................................................3-7 3.1.5 CHAN_LOS...........................................................................................................................................3-9 3.1.6 FCSERRORS_OVER..........................................................................................................................3-11 3.1.7 IN_PWR_HIGH...................................................................................................................................3-13 3.1.8 IN_PWR_LOW....................................................................................................................................3-15 3.1.9 LINK_ERR...........................................................................................................................................3-18 3.1.10 LINK_STATUS.................................................................................................................................3-20 3.1.11 LOOP_ALM.......................................................................................................................................3-22 3.1.12 LSR_WILL_DIE................................................................................................................................3-23 3.1.13 MS_AIS..............................................................................................................................................3-25 3.1.14 MS_RDI.............................................................................................................................................3-26 3.1.15 MUT_LOS.........................................................................................................................................3-29 3.1.16 NEBD_XC_DIF.................................................................................................................................3-30 3.1.17 OA_LOW_GAIN...............................................................................................................................3-32 3.1.18 ODU_AIS...........................................................................................................................................3-34 3.1.19 OMS_FDI...........................................................................................................................................3-36 3.1.20 OPS_PS_INDI....................................................................................................................................3-37 3.1.21 OSC_LOS...........................................................................................................................................3-39 3.1.22 OTU_LOF..........................................................................................................................................3-40 3.1.23 OUT_PWR_HIGH.............................................................................................................................3-43 3.1.24 PM_BDI.............................................................................................................................................3-45 3.1.25 PM_BEI..............................................................................................................................................3-48 3.1.26 PM_BIP8_OVER...............................................................................................................................3-51 3.1.27 PORT_MODULE_OFFLINE............................................................................................................3-53 Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
OptiX BWS 1600G Backbone DWDM Optical Transmission System Alarms and Performance Events Reference 3.1.28 POWERALM.....................................................................................................................................3-54 3.1.29 POWER_DIFF_DEFECT..................................................................................................................3-56 3.1.30 POWER_FAIL...................................................................................................................................3-57 3.1.31 PS.......................................................................................................................................................3-59 3.1.32 PUMP_COOL_EXC..........................................................................................................................3-61 3.1.33 R_DATA_LOST................................................................................................................................3-62 3.1.34 R_LOF................................................................................................................................................3-64 3.1.35 R_LOS................................................................................................................................................3-66 3.1.36 R_OOF...............................................................................................................................................3-69 3.1.37 R_SLIP...............................................................................................................................................3-72 3.1.38 REM_SF.............................................................................................................................................3-73 3.1.39 SECU_ALM.......................................................................................................................................3-75 3.1.40 SM_BEI..............................................................................................................................................3-75 3.1.41 SM_BIP8_OVER...............................................................................................................................3-79 3.1.42 SM_TIM.............................................................................................................................................3-80 3.1.43 SUM_INPWR_LOW.........................................................................................................................3-82 3.1.44 SUM_OUTPWR_LOW.....................................................................................................................3-83 3.1.45 T_DATA_LOST................................................................................................................................3-85 3.1.46 TD.......................................................................................................................................................3-86 3.1.47 TF.......................................................................................................................................................3-88 3.1.48 WRG_BD_TYPE...............................................................................................................................3-89
3.2 Alarm Processing..........................................................................................................................................3-90 3.2.1 AD_CHECK_FAIL..............................................................................................................................3-91 3.2.2 ALM_PIUA_OFFLINE.......................................................................................................................3-92 3.2.3 ALM_PIUB_OFFLINE.......................................................................................................................3-93 3.2.4 AU_AIS................................................................................................................................................3-94 3.2.5 AU_LOP...............................................................................................................................................3-96 3.2.6 B1_SD..................................................................................................................................................3-97 3.2.7 B2_EXC...............................................................................................................................................3-99 3.2.8 B2_SD................................................................................................................................................3-101 3.2.9 BD_STATUS.....................................................................................................................................3-102 3.2.10 BD_VER_NMAT.............................................................................................................................3-103 3.2.11 BEFFEC_SD....................................................................................................................................3-105 3.2.12 BOOTROM_BAD...........................................................................................................................3-106 3.2.13 CFG_VERIFY..................................................................................................................................3-107 3.2.14 CFGBD_FAIL..................................................................................................................................3-108 3.2.15 CFGDATA_OUTRANGE...............................................................................................................3-109 3.2.16 CHAN_ADD....................................................................................................................................3-111 3.2.17 CLT_MM.........................................................................................................................................3-112 3.2.18 COMMUN_FAIL.............................................................................................................................3-113 3.2.19 DBMS_ERROR...............................................................................................................................3-114 3.2.20 DBMS_PROTECT_MODE.............................................................................................................3-116 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
Contents
3.2.21 DCM_INSUFF.................................................................................................................................3-117 3.2.22 DSP_LOAD_FAIL...........................................................................................................................3-118 3.2.23 EDFA_TEMP_OVER......................................................................................................................3-119 3.2.24 FAN_FAIL.......................................................................................................................................3-120 3.2.25 FEC_LOF.........................................................................................................................................3-121 3.2.26 FEC_OOF.........................................................................................................................................3-122 3.2.27 FIBER_CRITICAL..........................................................................................................................3-123 3.2.28 FIBER_MAJOR...............................................................................................................................3-125 3.2.29 FIBER_MINOR...............................................................................................................................3-126 3.2.30 FPGA_ABN.....................................................................................................................................3-128 3.2.31 GAINDATA_MIS............................................................................................................................3-129 3.2.32 HARD_BAD....................................................................................................................................3-130 3.2.33 HARD_FAIL....................................................................................................................................3-131 3.2.34 INPWR_FAIL..................................................................................................................................3-132 3.2.35 J0_MM.............................................................................................................................................3-133 3.2.36 K1_K2_M.........................................................................................................................................3-134 3.2.37 K2_M...............................................................................................................................................3-135 3.2.38 L_SYNC...........................................................................................................................................3-135 3.2.39 LAN_LOC........................................................................................................................................3-137 3.2.40 LASER_HAZARD_WARNING.....................................................................................................3-138 3.2.41 LOCK_CUR_FAIL..........................................................................................................................3-139 3.2.42 LSR_COOL_ALM...........................................................................................................................3-140 3.2.43 LTEMP_OVER................................................................................................................................3-141 3.2.44 LTI....................................................................................................................................................3-142 3.2.45 MAIL_ERR......................................................................................................................................3-144 3.2.46 MOD_COM_FAIL...........................................................................................................................3-145 3.2.47 MODULE_COOLCUR_OVER.......................................................................................................3-146 3.2.48 MODULE_TEMP_OVER...............................................................................................................3-147 3.2.49 MS_REI............................................................................................................................................3-148 3.2.50 MUT_TLOS.....................................................................................................................................3-150 3.2.51 NESTATE_INSTALL.....................................................................................................................3-152 3.2.52 NESOFT_MM..................................................................................................................................3-153 3.2.53 NO_BD_PARA................................................................................................................................3-154 3.2.54 NO_BD_SOFT.................................................................................................................................3-155 3.2.55 OCH_FDI.........................................................................................................................................3-156 3.2.56 OCH_FDI-O.....................................................................................................................................3-157 3.2.57 OCH_FDI-P.....................................................................................................................................3-158 3.2.58 OCH_LOS-P....................................................................................................................................3-160 3.2.59 OCH_OCI.........................................................................................................................................3-161 3.2.60 OCH_SSF.........................................................................................................................................3-162 3.2.61 OCH_SSF-O.....................................................................................................................................3-163 3.2.62 OCH_SSF-P.....................................................................................................................................3-165 Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Contents
OptiX BWS 1600G Backbone DWDM Optical Transmission System Alarms and Performance Events Reference 3.2.63 ODU_LCK.......................................................................................................................................3-166 3.2.64 ODU_OCI........................................................................................................................................3-168 3.2.65 ODU_TCMn_AIS............................................................................................................................3-170 3.2.66 ODU_TCMn_BDI............................................................................................................................3-171 3.2.67 ODU_TCMn_BEI............................................................................................................................3-172 3.2.68 ODU_TCMn_DEG..........................................................................................................................3-175 3.2.69 ODU_TCMn_EXC...........................................................................................................................3-177 3.2.70 ODU_TCMn_LCK...........................................................................................................................3-178 3.2.71 ODU_TCMn_LTC...........................................................................................................................3-179 3.2.72 ODU_TCMn_OCI............................................................................................................................3-180 3.2.73 ODU_TCMn_SSF............................................................................................................................3-181 3.2.74 ODU_TCMn_SD.............................................................................................................................3-183 3.2.75 ODU_TCMn_TIM...........................................................................................................................3-184 3.2.76 OMS_BDI........................................................................................................................................3-186 3.2.77 OMS_BDI-O....................................................................................................................................3-187 3.2.78 OMS_BDI-P.....................................................................................................................................3-188 3.2.79 OMS_FDI-O.....................................................................................................................................3-189 3.2.80 OMS_FDI-P.....................................................................................................................................3-190 3.2.81 OMS_LOS-P....................................................................................................................................3-191 3.2.82 OMS_SSF.........................................................................................................................................3-193 3.2.83 OMS_SSF-O....................................................................................................................................3-194 3.2.84 OMS_SSF-P.....................................................................................................................................3-195 3.2.85 OOS_LOST......................................................................................................................................3-196 3.2.86 OPS_MAIN_BAK_ATTR_DIFF....................................................................................................3-197 3.2.87 OPS_PS_FAIL.................................................................................................................................3-199 3.2.88 OPS_PS_FIXED..............................................................................................................................3-200 3.2.89 OPUk_PLM......................................................................................................................................3-201 3.2.90 OSC_RDI.........................................................................................................................................3-202 3.2.91 OTU_AIS.........................................................................................................................................3-203 3.2.92 OTU_LOM.......................................................................................................................................3-205 3.2.93 OUT_PWR_LOW............................................................................................................................3-206 3.2.94 OUTPWR_FAIL..............................................................................................................................3-207 3.2.95 PATCH_ACT_TIMEOUT...............................................................................................................3-208 3.2.96 PATCH_DEACT_TIMEOUT.........................................................................................................3-209 3.2.97 PATCH_ERR ..................................................................................................................................3-210 3.2.98 PATCH_NOT_CONFIRM .............................................................................................................3-211 3.2.99 PATCHFILE_NOTEXIST ..............................................................................................................3-211 3.2.100 PATH_VERIFY_ALM..................................................................................................................3-212 3.2.101 PDU_OFF_ALM............................................................................................................................3-213 3.2.102 PM_BIP8_SD.................................................................................................................................3-215 3.2.103 PM_TIM.........................................................................................................................................3-216 3.2.104 PORTSWITCH_FAIL...................................................................................................................3-217
vi
Issue 08 (2011-10-30)
Contents
3.2.105 POWER_DIFF_OVER..................................................................................................................3-219 3.2.106 PRIORITY_VERIFY_ALM..........................................................................................................3-220 3.2.107 PRBS_LSS.....................................................................................................................................3-221 3.2.108 PUM_BCM_ALM.........................................................................................................................3-222 3.2.109 PUM_TEM_ALM..........................................................................................................................3-224 3.2.110 PW_SWITCH_EX.........................................................................................................................3-225 3.2.111 PWR_MAJ_ALM..........................................................................................................................3-226 3.2.112 PWR_MIN_ALM...........................................................................................................................3-227 3.2.113 PWR_TEMP_OVERTH................................................................................................................3-228 3.2.114 R_LOC...........................................................................................................................................3-229 3.2.115 REAR_BD_OFFLINE...................................................................................................................3-231 3.2.116 RELAY_ALARM..........................................................................................................................3-232 3.2.117 REM_SD........................................................................................................................................3-233 3.2.118 RL_CRITICAL_HI........................................................................................................................3-234 3.2.119 RL_CRITICAL_LOW...................................................................................................................3-235 3.2.120 RMON_ALM_ALIGNMENT_OVER..........................................................................................3-236 3.2.121 RMON_ALM_DROPEVENT_OVER..........................................................................................3-238 3.2.122 RMON_ALM_FCSERROR_OVER..............................................................................................3-239 3.2.123 RMON_ALM_INBADOCTS_OVER...........................................................................................3-240 3.2.124 RMON_ALM_OUTBADOCTS_OVER.......................................................................................3-242 3.2.125 S1_SYN_CHANGE.......................................................................................................................3-243 3.2.126 SCC_LOC......................................................................................................................................3-244 3.2.127 SM_BDI.........................................................................................................................................3-245 3.2.128 SM_BIP8_SD.................................................................................................................................3-248 3.2.129 SM_IAE.........................................................................................................................................3-249 3.2.130 SPEED_OVER...............................................................................................................................3-251 3.2.131 SUM_INPWR_HI..........................................................................................................................3-253 3.2.132 SUM_OUTPWR_HI......................................................................................................................3-254 3.2.133 SWDL_ACTIVATED_TIMEOUT................................................................................................3-255 3.2.134 SWDL_AUTOMATCH_INH........................................................................................................3-256 3.2.135 SWDL_CHGMNG_NOMATCH...................................................................................................3-257 3.2.136 SWDL_COMMIT_FAIL...............................................................................................................3-258 3.2.137 SWDL_INPROCESS.....................................................................................................................3-259 3.2.138 SWDL_NEPKGCHECK................................................................................................................3-259 3.2.139 SWDL_PKG_NOBDSOFT...........................................................................................................3-260 3.2.140 SWDL_PKGVER_MM.................................................................................................................3-261 3.2.141 SWDL_ROLLBACK_FAIL..........................................................................................................3-262 3.2.142 SYNC_C_LOS...............................................................................................................................3-263 3.2.143 SYSLOG_COMM_FAIL...............................................................................................................3-264 3.2.144 T_LOC...........................................................................................................................................3-265 3.2.145 T_SLIP...........................................................................................................................................3-266 3.2.146 TEM_HA........................................................................................................................................3-267 Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
OptiX BWS 1600G Backbone DWDM Optical Transmission System Alarms and Performance Events Reference 3.2.147 TEM_LA........................................................................................................................................3-268 3.2.148 TEMP_ALARM.............................................................................................................................3-269 3.2.149 TEMP_OVER................................................................................................................................3-270 3.2.150 THUNDERALM............................................................................................................................3-271 3.2.151 TP_LOC.........................................................................................................................................3-272 3.2.152 VCXO_LOC...................................................................................................................................3-273 3.2.153 W_R_FAILURE.............................................................................................................................3-274 3.2.154 WAVE_LEN_LOCK_FAIL..........................................................................................................3-275
4 Performance Event List.............................................................................................................4-1

4.1 Product Performance Event List.....................................................................................................................4-2 4.1.1 Performance Event List of Check and Error Correction........................................................................4-2 4.1.2 Performance Event List of Equipment Function....................................................................................4-4 4.1.3 Performance Event list of Multiplex Section Bit Error..........................................................................4-8 4.1.4 Performance Event List of Regenerator Section Bit Error.....................................................................4-8 4.1.5 Performance Event List of Ethernet.......................................................................................................4-9 4.2 Board Performance Event List......................................................................................................................4-12 4.2.1 D40 Board Performance Event List.....................................................................................................4-12 4.2.2 DCP Board Performance Event List....................................................................................................4-13 4.2.3 ELOG/ELOGS Board Performance Event List...................................................................................4-13 4.2.4 ETMX/ETMXS Board Performance Event List..................................................................................4-14 4.2.5 FDG Board Performance Event List....................................................................................................4-16 4.2.6 FIU Board Performance Event List......................................................................................................4-17 4.2.7 FMU Board Performance Event List...................................................................................................4-17 4.2.8 HBA Board Performance Event List....................................................................................................4-17 4.2.9 ITL Board Performance Event List......................................................................................................4-18 4.2.10 LBE/LBES Board Performance Event List........................................................................................4-18 4.2.11 LBF/LBFS Board Performance Event List........................................................................................4-20 4.2.12 LOG/LOGS Board Performance Event List......................................................................................4-23 4.2.13 LQM Board Performance Event List.................................................................................................4-24 4.2.14 LU40 Board Performance Event List.................................................................................................4-25 4.2.15 LU40S Board Performance Event List...............................................................................................4-27 4.2.16 LUR40/LUR40S Board Performance Event List...............................................................................4-29 4.2.17 LWC1 Board Performance Event List...............................................................................................4-29 4.2.18 LWF/LWFS Board Performance Event List......................................................................................4-30 4.2.19 LWX Board Performance Event List.................................................................................................4-32 4.2.20 M40 Board Performance Event List...................................................................................................4-33 4.2.21 MCA Board Performance Event List.................................................................................................4-33 4.2.22 MR2 Board Performance Event List..................................................................................................4-33 4.2.23 MR8 Board Performance Event List..................................................................................................4-33 4.2.24 MWA Board Performance Event List................................................................................................4-34 4.2.25 MWF Board Performance Event List.................................................................................................4-34 4.2.26 OAU Board Performance Event List.................................................................................................4-34 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
Contents
4.2.27 OBU Board Performance Event List..................................................................................................4-34 4.2.28 OLP Board Performance Event List...................................................................................................4-35 4.2.29 OPU Board Performance Event List..................................................................................................4-35 4.2.30 PMU Board Performance Event List.................................................................................................4-35 4.2.31 RMU9 Board Performance Event List...............................................................................................4-35 4.2.32 RPC Board Performance Event List...................................................................................................4-35 4.2.33 SC1/SC2 Board Performance Event List...........................................................................................4-36 4.2.34 TMR/TMRS Board Performance Event List.....................................................................................4-36 4.2.35 TMX/TMXS Board Performance Event List.....................................................................................4-37 4.2.36 TMX40/TMX40S Board Performance Event List.............................................................................4-39 4.2.37 TRC1 Board Performance Event List................................................................................................4-41 4.2.38 V40 Board Performance Event List...................................................................................................4-42 4.2.39 VA4 Board Performance Event List..................................................................................................4-42 4.2.40 VOA Board Performance Event List.................................................................................................4-42 4.2.41 WMU Board Performance Event List................................................................................................4-42 4.2.42 WSD9 Board Performance Event List...............................................................................................4-43 4.2.43 WSM9 Board Performance Event List...............................................................................................4-43 4.2.44 WSMD2 Board Performance Event List............................................................................................4-43 4.2.45 WSMD4 Board Performance Event List............................................................................................4-43
5 Performance Event Processing.................................................................................................5-1

5.1 BCV.................................................................................................................................................................5-5 5.2 CCV.................................................................................................................................................................5-5 5.3 CRC4BBE.......................................................................................................................................................5-6 5.4 CRC4CSES..................................................................................................................................................... 5-7 5.5 CRC4ES..........................................................................................................................................................5-7 5.6 CRC4FEBBE.................................................................................................................................................. 5-8 5.7 CRC4FECSES.................................................................................................................................................5-9 5.8 CRC4FEES......................................................................................................................................................5-9 5.9 CRC4FESES.................................................................................................................................................5-10 5.10 CRC4SES....................................................................................................................................................5-11 5.11 CRC4UAS...................................................................................................................................................5-11 5.12 EDF_BOX_TMP.........................................................................................................................................5-12 5.13 ENV_TMP..................................................................................................................................................5-13 5.14 FEC_AFT_COR_ER...................................................................................................................................5-14 5.15 FEC_AFT_COR_ERAVR..........................................................................................................................5-14 5.16 FEC_AFT_CORER_FLOAT......................................................................................................................5-15 5.17 FEC_BEF_COR_ER...................................................................................................................................5-16 5.18 FEC_BEF_COR_ERAVR..........................................................................................................................5-17 5.19 FEC_BEF_CORER_FLOAT......................................................................................................................5-17 5.20 FEC_COR_0BIT_CNT...............................................................................................................................5-18 5.21 FEC_COR_1BIT_CNT...............................................................................................................................5-19 5.22 FEC_COR_BYTE_CNT.............................................................................................................................5-19 Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
5.23 FEC_UNCOR_BLOCK_CNT....................................................................................................................5-20 5.24 ICCLC.........................................................................................................................................................5-21 5.25 ICTMP.........................................................................................................................................................5-22 5.26 LINE_OUT_POWER..................................................................................................................................5-22 5.27 LSBIAS.......................................................................................................................................................5-24 5.28 LSCLC........................................................................................................................................................5-24 5.29 LSIOP..........................................................................................................................................................5-25 5.30 LSOOP........................................................................................................................................................5-26 5.31 LSTMP........................................................................................................................................................5-27 5.32 MSBBE.......................................................................................................................................................5-28 5.33 MSCSES......................................................................................................................................................5-29 5.34 MSES..........................................................................................................................................................5-30 5.35 MSFEBBE...................................................................................................................................................5-31 5.36 MSFECSES.................................................................................................................................................5-32 5.37 MSFEES......................................................................................................................................................5-33 5.38 MSFESES....................................................................................................................................................5-34 5.39 MSSES........................................................................................................................................................5-35 5.40 MSUAS.......................................................................................................................................................5-36 5.41 ODU_PM_BBE...........................................................................................................................................5-37 5.42 ODU_PM_BBER........................................................................................................................................5-38 5.43 ODU_PM_BIP8..........................................................................................................................................5-39 5.44 ODU_PM_ES..............................................................................................................................................5-39 5.45 ODU_PM_FEBBE......................................................................................................................................5-40 5.46 ODU_PM_FEBBER...................................................................................................................................5-41 5.47 ODU_PM_FEES.........................................................................................................................................5-42 5.48 ODU_PM_FESES.......................................................................................................................................5-43 5.49 ODU_PM_FESESR....................................................................................................................................5-44 5.50 ODU_PM_FEUAS......................................................................................................................................5-45 5.51 ODU_PM_SES............................................................................................................................................5-46 5.52 ODU_PM_SESR.........................................................................................................................................5-46 5.53 ODU_PM_UAS..........................................................................................................................................5-47 5.54 ODU_TCMn_BBE......................................................................................................................................5-48 5.55 ODU_TCMn_BBER...................................................................................................................................5-49 5.56 ODU_TCMn_BIAES..................................................................................................................................5-50 5.57 ODU_TCMn_ES.........................................................................................................................................5-51 5.58 ODU_TCMn_FEBBE.................................................................................................................................5-52 5.59 ODU_TCMn_FEBBER..............................................................................................................................5-52 5.60 ODU_TCMn_FEES....................................................................................................................................5-53 5.61 ODU_TCMn_FESES..................................................................................................................................5-54 5.62 ODU_TCMn_FESESR...............................................................................................................................5-54 5.63 ODU_TCMn_FEUAS.................................................................................................................................5-55 5.64 ODU_TCMn_IAES.....................................................................................................................................5-56 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
Contents
5.65 ODU_TCMn_SES.......................................................................................................................................5-56 5.66 ODU_TCMn_SESR....................................................................................................................................5-57 5.67 ODU_TCMn_UAS......................................................................................................................................5-58 5.68 OOPRL........................................................................................................................................................5-59 5.69 OTU_BBE...................................................................................................................................................5-60 5.70 OTU_BBER................................................................................................................................................5-60 5.71 OTU_ES......................................................................................................................................................5-61 5.72 OTU_FEBBE..............................................................................................................................................5-62 5.73 OTU_FEBBER............................................................................................................................................5-63 5.74 OTU_FEES.................................................................................................................................................5-64 5.75 OTU_FESES...............................................................................................................................................5-65 5.76 OTU_FESESR............................................................................................................................................5-66 5.77 OTU_FEUAS..............................................................................................................................................5-67 5.78 OTU_SES....................................................................................................................................................5-68 5.79 OTU_SESR.................................................................................................................................................5-68 5.80 OTU_SM_BIP8...........................................................................................................................................5-69 5.81 OTU_UAS...................................................................................................................................................5-70 5.82 OTU_IAES..................................................................................................................................................5-71 5.83 OTU_BIAES...............................................................................................................................................5-72 5.84 PCLSOP......................................................................................................................................................5-72 5.85 PCLSSN......................................................................................................................................................5-73 5.86 PCLSWL.....................................................................................................................................................5-74 5.87 PCLSWLO..................................................................................................................................................5-74 5.88 PMUTMP....................................................................................................................................................5-75 5.89 PUMPOOP..................................................................................................................................................5-76 5.90 PUMPTMP..................................................................................................................................................5-77 5.91 RSBBE........................................................................................................................................................5-78 5.92 RSCSES......................................................................................................................................................5-78 5.93 RSES...........................................................................................................................................................5-79 5.94 RSOFS.........................................................................................................................................................5-80 5.95 RSSES.........................................................................................................................................................5-81 5.96 RSUAS........................................................................................................................................................5-82 5.97 SUMIOP......................................................................................................................................................5-83 5.98 SUMOOP....................................................................................................................................................5-84 5.99 WCV............................................................................................................................................................5-86
A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1
Issue 08 (2011-10-30)
xi
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name OptiX BWS 1600G OptiX iManager T2000 Version V100R007 V200R008C00
Intended Audience
The intended audiences of this document are: l l Network Monitoring Engineer System Maintenance Engineer
Symbol Conventions
The following symbols may be found in this document. They are defined as follows: Symbol Description
DANGER
Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save you time.
WARNING
CAUTION
TIP
Issue 08 (2011-10-30)
About This Document
Symbol
NOTE
Description Provides additional information to emphasize or supplement important points of the main text.
GUI Conventions
Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Issue 08 (2011-10-30) Based on Product Version V100R007

The updated contents are as follows. The alarms and performances of the LQM board has been added. The alarm processing of GAINDATA_MIS, RL_CRITICAL_HI, RL_CRITICAL_LOW have been added. The performance processing of OOPRL has been added. Some bugs in the manual of the previous version are fixed.

The updated contents are as follows. The alarms and performances of the LV40 and LV40S boards have been added. Some bugs in the manual of the previous version are fixed.
2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
About This Document

The updated contents are as follows. Some bugs in the manual of the previous version are fixed.


The updated contents are as follows. Chapter Chapter 2 Alarm List Update Description The alarms of the IMX4, IMX4S, LW40, LR40, FCE, LDG, LOM, LOMS, LQM, TRC2, LWM, LWMR, LWXR, M48, D48, V48, DWC, EDWC, WSM5, WSD5, RPA, ST1, ST2, OCP, SCS, CP40, PBU, VA2, DGE, DSE and GFU boards have been deleted. The performances of the IMX4, IMX4S, LW40, LR40, FCE, LDG, LOM, LOMS, LQM, TRC2, LWM, LWMR, LWXR, M48, D48, V48, DWC, EDWC, WSM5, WSD5, RPA, ST1, ST2, OCP, SCS, CP40, VA2, DGE, DSE and GFU boards have been deleted.
Chapter 4 Performance Event List

Issue 08 (2011-10-30)
About This Document

The updated contents are as follows. Chapter Chapter 2 Alarm List Update Description The alarms of the SCC and SCU boards have been added. The alarm of SUBRACK_ID_CONFLICT, SUB_RACK_NUM_OUTRANGE, SUB_RACK_OFFLINE and OPU3_PLM has been added. Chapter 3 Alarm Processing The alarm processing of SUBRACK_ID_CONFLICT, SUB_RACK_NUM_OUTRANGE, SUB_RACK_OFFLINE and OPU3_PLM has been added.

The updated contents are as follows. Chapter Chapter 2 Alarm List Update Description The alarms of the LUR40, LUR40S, CP40 and EOLP boards have been added. The alarms of the LWFD and LRFD boards have been deleted. The alarms of TCM layer have been added. The alarm of LASER_HAZARD_WARNING has been added. Chapter 3 Alarm Processing The alarm processing of LWFD and LRFD boards have been deleted. The alarm processing of TCM layer have been added. The alarm processing of LASER_HAZARD_WARNING has been added. Chapter 4 Performance Event List The performances of the LUR40, LUR40S, CP40 and EOLP boards have been added. The performance of the LWFD and LRFD boards have been deleted. The performances of TCM layer have been added.
Issue 08 (2011-10-30)
About This Document

The updated contents are as follows. Chapter Chapter 1 Overview Update Description Convergent OTU Processing GE Standard Signals have been added. Non-Convergent OTU Processing 10GE Standard Signals have been added. Chapter 2 Alarm List The alarms of the LU40, LU40S, TMX40, TMX40S, MR8, WSMD2, LRFD, and LWFD boards have been added. The alarm of CRC4_CROSSTR, MS_CROSSTR and RS_CROSSTR have been deleted. The alarm of L_SYNC have been added. Power monitoring and optical power monitoring alarm of the FIU, MR2, MR8, MB2 and ITL have been deleted. The alarms of the LRF, and LRFS boards have been deleted. Chapter 3 Alarm Processing The section of common alarm processing have been added. The alarm processing of CRC4_CROSSTR, MS_CROSSTR and RS_CROSSTR have been deleted. The alarm processing of L_SYNC have been added. 4 Performance Event List The performances of the LU40, LU40S, TMX40, TMX40S, MR8, WSMD2, LRFD, and LWFD boards have been added. The performance of the LRF, and LRFS boards have been deleted.

The updated contents are as follows. Chapter Chapter 2 Alarm List Update Description The alarms of the VA2, LOM and LOMS boards have been added. The LAN_LOC alarm of SCC board have been added.
Issue 08 (2011-10-30)
About This Document
Chapter Chapter 3 Alarm Processing
Update Description The alarm processing of PWR_TEMP_OVERTH has been added. The alarm processing of THUNDERALM, SWDL_ACTIVATED_TIMEOUT, SWDL_NEPKGCHECK, SWDL_CHGMNG_NOMATCH, SWDL_PKG_NOBDSOFT, SWDL_ROLLBACK_FAIL, SWDL_COMMIT_FAIL, SWDL_INPROCESS, SWDL_PKGVER_MM, SWDLAUTOMATCH_INH has been modified.
The performance events of the VA2, LOM and LOMS boards have been added.

The updated contents are as follows. Chapter Chapter 2 Alarm List Update Description The alarms of the LW40, LR40, IMX4, IMX4S, ELOG, ELOGS and WSMD4 boards have been added. The OLS alarms have been added. Modify the name of OTU_OOM to be OTU_LOM. The boards of OTU4000 and OTU4010 have been deleted. The SYSLOG_COMM_FAIL, REAR_BD_OFFLINE alarms of SCC board have been added. Chapter 3 Alarm Processing The OLS of alarms processing have been added. The alarm processing of the OTU4000 and OTU4010 boards have been deleted. The performance events of the LW40, LR40, IMX4, IMX4S, ELOG, ELOGS and WSMD4 boards have been added. The OTN performances of the boards have been added. The boards of OTU4000 and OTU4010 have been deleted.

The updated contents are as follows.
6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
About This Document
Chapter Chapter 1 Overview Chapter 2 Alarm List
Update Description A new chapter. The BD_STATUS, HARD_BAD and FPGA_ABN have been added to WMU, the TF_CHECK_FAIL have been deleted. The VA2 has been deleted, and the LRF(S) has been added. The description of ALM_PIUA_OFFLINE and ALM_PIUB_OFFLINE was updated. The RMON alarms of ST1 and ST2 have been added.
4 Performance Event List
The LSIOPCUR, LSIOPMIN and LSIOPMAX have been deleted from WMU, and the PCLSOPCUR, PCLSOPMIN, PCLSOPMAX have been added to. The MSFEES, MSFESES, MSFEBBE and MSFECSES have been deleted. The Fragments and Jabbers have been added to LOG and LOGS.
The alarm list and performance event list of LRF(S) are added. Add the chapter of Chapter 1 Overview.

Issue 08 (2011-10-30)
About This Document
Chapter Chapter 1 Alarm and Performance Event Lists
Update Description The ADDITION_C_AIS, ADDITION_C_BPV, ADDITION_C_CRC, ADDITION_C_LOF and ADDITION_LOC have been added. FEC_LOF, DROPEVENT_UNDER, FCSERRORS_UNDER, INBADOCTS_UNDER, OUTBADOCTS_UNDER, RMON_ALM_DROPEVENT_UNDER, RMON_ALM_FCSERRORS_UNDER, RMON_ALM_INBADOCTS_UNDER and RMON_ALM_OUTBADOCTS_UNDER have been deleted. The alarms and performance events of the LRF, LRFS, M08 and D08 have been deleted. The alarms and performance events of the RMU9, ST1, ST2, TRC2, VA2 and WMU have been added. Modify the name of REM_SD_AIS_EX to be CLIENT_SD; modify the name of REMS_UNEQ_EX to be CLIENT_SF. The PS reported by OTUs has been added. The RMON performance events of the LDG, LOG, LOGS, FCE, FDG, LBE, LBES, LBF, LBFS, LQM, LWX and LWXR have been added.
Chapter 2 Alarm Processing
ADDITION_C_AIS, ADDITION_C_BPV, ADDITION_C_CRC, ADDITION_C_LOF and ADDITION_LOC have been added. FEC_LOF, DROPEVENT_UNDER, FCSERRORS_UNDER, INBADOCTS_UNDER, OUTBADOCTS_UNDER, RMON_ALM_DROPEVENT_UNDER, RMON_ALM_FCSERRORS_UNDER, RMON_ALM_INBADOCTS_UNDER and RMON_ALM_OUTBADOCTS_UNDER have been deleted. Modify the name of REM_SD_AIS_EX to be CLIENT_SD; modify the name of REMS_UNEQ_EX to be CLIENT_SF. Modify the possible causes and troubleshooting of ALM_DATA_TLOS, AU_AIS, AU_LOP, MAIL_ERR and NEBD_XC_DIF.

Issue 08 (2011-10-30)
About This Document
Chapter Chapter 1 Alarm and Performance Event Lists
Update Description The heading of section 1.1 is changed from "Alarm List" to "Product Alarm List"; the heading of section 1.3 is changed from "Performance Event List" to "Product Performance Event List". The board alarm lists in section 1.2 and the board performance event lists in section 1.4 ared arranged in alphabetical order. The alarms and performance events of the ETMX, ETMXS, LBF, LBFS, LQM, M48, D48, WSD5, WSD9, WSM5 and WSM9 have been added.
Chapter 2 Alarm Processing
Modify the possible causes and troubleshooting of BOOTROM_BAD, CHAN_ADD, CHAN_LOS, COMMUN_FAIL, PM_BDI, PM_BEI, R_LOC and TP_LOC. Modify the name of PW_SWITCH to be PW_SWITCH_EX. Modify the name of PWR_STA_ALM to be POWERALM; modify the possible causes and troubleshooting.
Chapter 3 Performance Event Processing
Some bugs in former version are fixed.

The updated contents are as follows. The description of alarms and performance events relevant to the 40GOTU is added on the basis of the previous version. Modify document template in this version. Fix several bugs in the manual of the previous version.

The former manual version is T2-040302-20060530-C-1.40. The updated contents are as follows. Some bugs in version 1.32 are fixed in this version. The alarms and performance events of the FCE, DCP, M08, D08 and V48 have been added.

The former manual version is T2-040338-20060630-C-1.32.
Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9
About This Document
Fixed some bugs in version 1.31. The alarms and performances events of following board have been deleted: AP8, AS8, OCU, OCUS, LQS and RPL.

The former manual version is T2-040338-20060115-C-1.31. The first commercial release.

The former manual version is T2-040338-20051210-C-1.30. The first field trial release.
10
Issue 08 (2011-10-30)
1 Overview
1
About This Chapter
Overview
This chapter describes the meaning, indicator status, category, range, and impact of the alarms of four levels. It also describes the meaning and category of performance events, and provides the suppression relation of alarms and performance event suppression by alarms. 1.1 Alarm Level This section respectively describes the meaning, impact, and indicator status of the alarms of four levels. 1.2 Alarm Category This section describes the meaning and range of alarms in different categories. 1.3 Performance Event Category The performance events can be classified into seven categories according to the functions monitored by the performance events. 1.4 Alarm Signal Flow This section describes the alarm signal flow of the OTU. It describes the generation, detection, and transmission of alarms when the OTU accesses different types of signals. 1.5 Suppression Relation of Alarms This section describes the rules of alarm suppression and provides the suppression relation figure of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm suppression. 1.6 Performance Event Suppression by Alarms An optical interface can report several alarms and performance events. Some performance events are not important for the maintenance engineer.
Issue 08 (2011-10-30)
1-1
1 Overview
1.1 Alarm Level

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

This section describes the meaning and range of alarms in different categories. The alarms can be classified into the following six categories. For details, see Table 1-2.
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
1 Overview
Table 1-2 Alarm category Alarm Category Communication alarm Definition Alarms related to the NE communication, ECC communication, and communication with optical signals Alarms related to the software processing and anomalies Alarms related to the hardware of the equipment Alarms related to the service status and network service quality Alarms related to the power supply system and environment of the equipment room Alarms related to the network management and the NE security Example The alarm is generated when the NE communication is interrupted or the optical signal is lost.
Process alarm
The alarm is generated when the database is in error or the NE is in the installing state. The alarm is generated when the laser is faulty or the optical interface is looped back. The alarm is generated when the signals at the line layer are degraded. The alarm is generated when the temperature of the power module is excessively high. The alarm is generated when the NE user is not logged in.
Equipment alarm
Service alarm
Environment alarm Security alarm
1.3 Performance Event Category

The performance events can be classified into seven categories according to the functions monitored by the performance events. The performance events are important parameters that reflect the working performance of the equipment. Knowledge of the generation principle, related boards, and alarms of the performance events is helpful to find incipient faults in routine maintenance and analyze the fault. The categories of the performance events are listed in Table 1-3. The performance events and alarms are related. When the number of performance events exceeds the pre-set threshold, the related alarm is triggered. Hence, when a performance event is generated, check whether the related alarm is generated and handle the performance event according to the handling procedure of the related alarm. The OptiX BWS 1600G provides the remote monitoring function through which the network can monitor the transmission of data in different network segments. Remote monitoring (RMON) provides flexible detection modes and control mechanisms to cater for the needs of different types of networks. The RMON defines a serial of statistic formats and functions to realize the data exchange among the control stations and detection stations in compliance with the RMON standard. The RMON also provides error diagnosis, planning, and information receiving of the performance events of the entire network.
Issue 08 (2011-10-30)
1-3
1 Overview
Table 1-3 Performance event categories Performance Event Category Administrative unit pointer justification Performance event related to the bit errors of the regenerator section Performance event related to the bit errors of the multiplex section Performance event related to the check and error correction Performance event related to the equipment function RMON performance event Definition The performance event related to the positive or negative justification count of the AU pointer in the SDH frame of the WDM-side signals. The performance event generated when bit errors occur to the regenerator section in the SDH frames of the signals on the WDM side or the client side of the board. The performance event generated when bit errors occur to the multiplex section in the SDH frames of the signals on the WDM side or the client side of the board. The performance event generated when the board performs service check or bit error correction. The performance event generated when the optical power, the working current of the laser or other factors about the running environment exceed the threshold. 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. The performance event generated when parameter changes in FC.
Performance Event of FC
1.4 Alarm Signal Flow

This section describes the alarm signal flow of the OTU. It describes the generation, detection, and transmission of alarms when the OTU accesses different types of signals.
1.4.1 Overview
This section describes the eight 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 l Non-convergent OTU It refers to an OTU that converts one channel of client service signals. Convergent OTU It refers to an OTU that converges and converts multiple channels of client service signals.
1 Overview
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 eight situations are defined in this section: l Non-convergent OTU processing standard SDH signals This section describes the alarm signal flow when the non-convergent OTU processes standard SDH signals. l Non-convergent OTU processing standard OTN signals This section describes the alarm signal flow when the non-convergent OTU processes standard OTN signals. l Convergent OTU processing standard SDH signals This section describes the alarm signal flow when the convergent OTU processes standard SDH signals. l Convergent OTU processing standard OTN signals This section describes the alarm signal flow when the convergent OTU processes standard OTN signals. l l l Regenerating OTU This section describes the alarm signal flow of the regenerating OTU. OTU with the cross-connect function This section describes the alarm signal flow of the OTU with the cross-connect function. Convergent OTU processing GE standard signals This section describes the alarm signal flow when the convergent OTU processes GE standard signals. l Non-convergent OTU processing 10GE standard signals This section describes the alarm signal flow when the non-convergent OTU processes 10GE standard signals.
SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are trigger conditions of a protection switching. Whether the SD event is used as a trigger condition, however, it can be set by the user. The SF and SD events are marked in the alarm signal flow diagrams in this section. These events are generated when the equipment configured with network protection detects a certain alarm. If the equipment is not configured with the network protection, The SF and SD events are not detected or reported.
Concepts
The following concepts are used in the diagrams in this section: l l WDM side: It is the WDM side of the OTU. Client side: it is the client side of the OTU. On the client side, the services from a client device are accessed.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-5
Issue 08 (2011-10-30)
1 Overview
Middle part: It is the middle part between the WDM side and the client side. It is a virtual concept, and thus is not displayed on the T2000. This concept is introduced to describe the alarm detection mechanism. N#1: It indicates channel 1 at optical interface N on the OTU. For example, the client-side optical interfaces of the ELOG unit are numbered 3, 4, 5, and 6, and the WDM-side optical interface of the ETMXELOG unit is numbered 1. Then, 3#1 indicates channel 1 at clientside optical interface 3. 1#N: It indicates channel N at WDM-side optical interface 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical interface 1.
1.4.2 Non-Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the non-convergent OTU processes standard SDH signals. Figure 1-1 and Figure 1-2 show the alarm signal flows when the non-convergent OTU processes standard SDH signals.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals
Station A Client-side WDM-side Station B WDM-side SF R_LOS R_LOF SF R_LOF R_LOF R_LOF R_LOF Client-side Client device Client-device
R_LOS
R_LOF
MS_AIS
MS_AIS
MS_AIS SD
MS_AIS
BI errors
B1_SD/ B1_EXC
B1_SD/ B1_EXC SD PM BIP8 errors PM_BIP8_SD/ PM_BIP8_OVER
B1 errors
Errors
PM_BEI SM BIP8 errors SD SM_BIP8_SD/ SM_BIP8_OVER
Errors
SM_BEI SF:SF event detecting xxx SD:SD event detecting Alarm processing
Detects and reports the xxx alarm.
1-6
Issue 08 (2011-10-30)
1 Overview
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 WDM side of the OTU at station B detects the R_LOF alarm, and then an SF event is generated. The event triggers a protection switching. 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. Then, the PM_BIP8_SD or PM_BIP8_OVER alarm is generated. The number of errors determines which alarm is generated. In addition, the PM_BEI alarm is 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. An SD event is generated on the WDM side of the OTU at station B, and a protection switching is triggered.
Issue 08 (2011-10-30)
1-7
1 Overview
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals
Station A Client-side WDM-side MFAS frame discontinuous PM TTI byte mismatch SM TTI byte mismatch PM_BEI PM_BDI SM_BEI SM_BDI Excessive bit errors before FEC Station B WDM-side OTU_LOM PM_TIM SM_TIM PM_BEI PM_BDI SM_BEI SM_BDI BEFFEC_EXC SF OTU_LOF Client-side Client device Client-device
OTU_LOF
R_LOF
PM_BDI&SM_BDI
ODU_AIS/ ODU_OCI/ ODU_LCK
SF ODU_AIS/ ODU_OCI/ ODU_LCK R_LOF
PM_BDI R_LOS SF R_LOS
R_LOF
PM_BDI&SM_BDI SF : SF event detecting xxx Alarm processing
This section describes the alarm signal flow by analyzing how the OTU processes the SM_BEI and OTU_LOF alarms. The alarm signal flows of other alarms are similar. l SM_BEI The WDM side of the OTU at station B detects the SM_BEI alarm that is from upstream station A. The alarm is not sent to the downstream station. l OTU_LOF The WDM side of the OTU at station B detects the OTU_LOF alarm. Then, the OTU sends the PM_BDI and SM_BDI alarms to the WDM side of upstream station A. In addition, the
1 Overview
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. An SF event is generated on the WDM side of the OTU at station B, and a protection switching is triggered.
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. Figure 1-3 and Figure 1-4 show the alarm signal flows when the non-convergent OTU processes standard OTN signals.
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.
Issue 08 (2011-10-30)
1-9
1 Overview
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals
Station A Client-side WDM-side Station B WDM-side SF R_LOS ODU_AIS SD PM_BIP8_SD/ PM_BIP8_OVER ODU_AIS Client-side Client device Client-device
R_LOS SM_BDI PM BIP8 errors
PM_BIP8_SD/ PM_BIP8_OVER
PM BIP8 errors
SM BIP8 errors
SM_BIP8_SD/ SM_BIP8_OVER
SM_BEI
SD PM BIP8 errors PM_BIP8_SD/ PM_BIP8_OVER SD SM_BIP8_SD/ SM_BIP8_OVER PM BIP8 errors
SM BIP8 errors
SM_BEI SF ODU_AIS
OTU_LOF
OTU_LOF
ODU_AIS
SM_BDI SF ODU_AIS
OTU_AIS
OTU_AIS
ODU_AIS
SM_BDI
OTU_LOF/ OTU_AIS
SF OTU_LOF/ OTU_AIS
ODU_AIS
SM_BDI
SF:SF event detecting xxx
SD:SD event detecting
Alarm processing
This section describes the alarm signal flow by analyzing how the OTU unit processes the R_LOS and OTU_LOF alarms. 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 OTU sends the SM_BDI alarm to the upstream client equipment of station A. The R_LOS signals are processed on the WDM side of the OTU and then are sent to station B. The WDM side of
1 Overview
the OTU at station B detects the ODU_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 ODU_AIS alarm to the client equipment. l The OTU_LOF signals are accessed on the client side. The client side of the OTU at station A receives OTU_LOF signals. The OTU sends the SM_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 ODU_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 ODU_AIS alarm to the client equipment. l The OTU_LOF signals are accessed on the WDM side. The WDM side of the OTU at station B detects the OTU_LOF alarm. The OTU sends the SM_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then sent to the downstream client side of station B. After the alarm is processed on the client side, the ODU_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. Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals
Station A Client-side WDM-side Station B WDM-side Client-side Client device Client-device
SM TTI byte mismatch
SM_TIM
SM TTI byte mismatch
SM_TIM
SM_BEI/ SM_BDI
SM_BEI/ SM_BDI
SM_BEI/ SM_BDI
SM_BEI/ SM_BDI
Transparent transmission of all PM signals ODU_AIS/ ODU_LCK/ ODU_OCI
ODU_AIS/ ODU_LCK/ ODU_OCI
R_LOS
SF R_LOS ODU_AIS
PM_BDI&SM_BDI
SD:SD event detecting
Alarm processing
Issue 08 (2011-10-30)
1-11
1 Overview
SM_TIM When the OTU receives the SM_TIM alarm on the client side or on the WDM side. This alarm is not sent to the downstream station.
SM_BEI/SM_BDI The OTU detects the SM_BEI/SM_BDI alarm that is sent from the upstream station. This alarm is not sent to the downstream station.
l l
PM_TIM/ PM_BEI/PM_BDI The OTU transparently transmits all PM alarms. ODU_AIS/ODU_LCK/ODU_OCI The client side of the OTU at station A receives ODU_AIS, ODU_LCK, or ODU_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 ODU_AIS, ODU_LCK, or ODU_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 ODU_AIS, ODU_LCK, or ODU_OCI alarm to the client equipment.
R_LOS The WDM side of the OTU at station B detects the R_LOS alarm. The OTU sends PM_BDI and SM_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 ODU_AIS alarm is detected in the client equipment. An SF event is generated on the WDM side of the OTU at station B, and a protection switching is triggered.
1.4.4 Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the convergent OTU processes standard SDH signals. Figure 1-5 and Figure 1-6 show the alarm signal flows when the convergent OTU processes standard SDH signals.
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 ETMX are numbered 3, 4, 5, and 6, and the WDM-side optical interface of the ETMX 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 T2000. 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
1-12
Issue 08 (2011-10-30)
1 Overview
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Station A Client-side R_LOS R_LOS R_LOS R_LOS Middle WDM-side WDM-side Station B Middle SF N#1 R_LOS N#1 R_LOS SF N#1 R_LOS N#1 R_LOS 1#N R_LOF SF 1#N R_LOF SF 1#N R_LOF SF 1#N R_LOF SF N#1 R_LOS N#1 R_LOF N#1 R_LOC N#1 errors 1#N R_LOF SF 1#N R_LOF SF 1#N R_LOF SD 1#N BIT errors N#1 REM_SF R_LOF Errors N#1 REM_SF N#1 REM_SF R_LOF R_LOF N#1 REM_SF N#1 REM_SF N#1 REM_SF N#1 REM_SF R_LOF R_LOF R_LOF R_LOF Client-side Client device Client-device
R_LOS R_LOF R_LOC Errors
A B C D
N#1 A N#1 B N#1 C N#1 D
1#N A 1#N B 1#N C 1#N D
A B C D
ABCD are the others of the SDH alarms SF:SF event detecting xxx SD:SD event detecting Alarm processing
This section describes the alarm signal flow through an example in which four client-side services are accessed on the convergent OTU. l Four channels of R_LOS signals are accessed on the client side. The OTU at station A accesses four channels of R_LOS signals on the client side. After being processed in the middle part of the OTU at station A, the alarm signals are then sent to station B. The R_LOF alarm of the corresponding channel is generated in the middle part of station B, and the REM_SF alarm is generated on the client side. The R_LOF alarm is detected in the client equipment. An SF event is generated in each channel and on the WDM side of the OTU at station B, and a protection switching is triggered. l One channel of R_LOS signals are accessed on the client side. The OTU at station A accesses one channel of R_LOS signals on the client side, for example, channel 1 at optical interface 3. After being processed in the middle part and on the WDM side of the OTU at station A and the WDM side of station B, the alarm signals are then sent to the downstream station. The R_LOF alarm of channel 3 at optical interface 1 is generated in the middle part of station B, and the REM_SF alarm of channel 1 at optical interface 3 is generated on the client side. The R_LOF alarm is detected in the client equipment.
Issue 08 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-13
1 Overview
An SF event is generated in the corresponding channel in the middle part of the OTU at station B, and a protection switching is triggered. Non-R_LOS signals are accessed on the client side. The signal flow of the R_LOF or the LOC is similar to that of the R_LOS. When any other alarms are accessed, the same alarm is reported at each detection point in the system.
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
Station A Client-side Middle WDM-side WDM-side Station B Middle Client-side Client device Client-device R_LOF SF R_LOS R_LOF PM_BDI&SM_BDI R_LOF R_LOF SF OTU_LOF R_LOF PM_BDI&SM_BDI R_LOF R_LOF ODU_AIS/ ODU_LCK/ ODU_OCI SF ODU_AIS/ ODU_LCK/ ODU_OCI R_LOF R_LOF R_LOF Errors SD PM BIP8 errors PM_BIP8_SD/ PM_BIP8_OVER Errors Errors PM_BEI Errors Errors SD SM BIP8 errors SM_BIP8_SD/ SM_BIP8_OVER Errors Errors Errors SD:SD event detecting Alarm processing R_LOF R_LOF
R_LOS
OTU_LOF
PM_BDI
SM_BEI SF:SF event detecting xxx
This section describes the alarm signal flow through an example in which four client-side services are accessed on the convergent OTU.
1 Overview
There is R_LOS, OTU_LOF, OTUk_LOM, ODU_AIS, ODU_OCI, or ODU_LCK on the WDM side. The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU sends the PM_BDI or SM_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.
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 PM_BEI or SM_BEI alarm to the WDM side of upstream station A. The alarm is then sent to the client side of the downstream station B. In this case, 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, and a protection switching is triggered.
1.4.5 Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the convergent OTU processes standard OTN signals. Figure 1-7 and Figure 1-8 show the alarm signal flows when the convergent OTU processes standard OTN signals.
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 ETMX unit are numbered 3, 4, 5, and 6, and the WDM-side optical interface of the ETMX 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 T2000. 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 reallocated.
NOTE
Issue 08 (2011-10-30)
1-15
1 Overview
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
Station A Client-side R_LOS Inserts SM_BDI back R_LOS Inserts SM_BDI back R_LOS Inserts SM_BDI back R_LOS Inserts SM_BDI back R_LOS Inserts SM_BDI back R_LOS Inserts SM_BDI back OTU_LOF Inserts SM_BDI back N#1 OTU_LOF N#1 R_LOS N#1 R_LOS N#1 R_LOS N#1 R_LOS N#1 R_LOS N#1 R_LOS Middle WDM-side WDM-side Station B Middle SF 1#N ODU_AIS SF 1#N ODU_AIS SF 1#N ODU_AIS SF 1#N ODU_AIS SF 1#N ODU_AIS SF 1#N ODU_AIS SF 1#N ODU_AIS SD N#1 ODU_AIS 1#N ODU_AIS ODU_AIS N#1REM_SF ODU_AIS N#1 REM_SF ODU_AIS N#1REM_SF ODU_AIS N#1 REM_SF ODU_AIS N#1 REM_SF ODU_AIS N#1 REM_SF ODU_AIS N#1 REM_SF ODU_AIS Client-side Client device Client-device
ODU_AIS
A B C BIT errors
N#1 A N#1 B N#1 C
1#N A 1#N B 1#N C SD
A B C
N#1 BIT errors SD:SD event detecting
1#N BIT errors Alarm processing A, B, C are the others of the OTN alarms
BIT errors
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, and sends the SM_BDI alarm to the upstream client equipment of station A. 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 ODU_AIS alarm of the corresponding channel is generated in the middle part of station B, and the REM_SF alarm is generated on the client side. The ODU_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 or OTU_LOF signals are accessed on the client side. The OTU at station A accesses one channel of R_LOS or OTU_LOF signals on the client side, for example, channel 1 at optical interface 3. The OTU sends the SM_BDI alarm to the upstream client equipment of station A. 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 ODU_AIS alarm of channel 3 at optical
1 Overview
interface 1 is generated in the middle part of station B, and the REM_SF alarm of channel 1 at optical interface 3 is generated on the client side. The ODU_AIS alarm is detected in the client device. An SF event is generated in the corresponding channel in the middle part of the OTU at station B, and a protection switching is triggered. l The alarm signals except for the signals of the R_LOS and OTU_LOF alarms are accessed on the client side. When any of other alarm signals is accessed, the corresponding alarm is reported at each detection point in the system. Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
Station A Client-side Middle WDM-side WDM-side Station B Middle Client-side Client device Client-device
ODU_AIS R_LOS SF R_LOS ODU_AIS PM_BDI&SM_BDI ODU_AIS ODU_AIS SF OTU_LOF OTU_LOF/ ODU_AIS ODU_AIS PM_BDI&SM_BDI ODU_AIS ODU_AIS ODU_AIS/ SF ODU_LCK/ ODU_AIS/ ODU_OCI ODU_LCK/ ODU_OCI PM_BDI ODU_AIS ODU_AIS ODU_AIS Errors SD PM BIP8 errors PM_BIP8_SD/ PM_BIP8_OVER Errors Errors PM_BEI Errors Errors SD SM BIP8 errors SM_BIP8_SD/ SM_BIP8_OVER Errors Errors Errors SD:SD event detecting Alarm processing ODU_AIS
SM_BEI SF:SF event detecting xxx
Issue 08 (2011-10-30)
1-17
1 Overview
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, OTU_LOF,ODU_AIS, ODU_OCI, or ODU_LCK on the WDM side. The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU sends the PM_BDI or SM_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 ODU_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 PM_BEI or SM_BEI alarm 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.
1.4.6 Regenerating OTU

This section describes the alarm signal flow of the regenerating OTU. Figure 1-9 shows the alarm signal flow of the regenerating OTU.
NOTE
The ALS function of the OTU shown in the figure in this section is not enabled. The non-intrusive monitoring of the board shown in the figure in this section is enabled.
1-18
Issue 08 (2011-10-30)
1 Overview
Figure 1-9 Alarm signal flow of the regenerating OTU

Station A WDM-side Station B(REG) WDM-side1 WDM-side2 Station C WDM-side
MFAS frame discontinuous PM TTI byte mismatch
OTU_LOM PM_TIM SM_TIM PM_BEI PM_BDI SM_BEI PM_BEI PM_BDI PM_TIM
SM TTI byte mismatch PM_BEI PM_BDI SM_BEI
SM_BDI
SM_BDI
SM_IAE
SM_IAE
OTU_LOF ODU_AIS/ ODU_OCI/ ODU_LCK
OTU_LOF
ODU_AIS
PM BIP8 errors
SM BIP8 errors
SM_BIP8_SD/ SM_BIP8_OVER
Excessive bit errors before FEC
BEFFEC_EXC
R_LOS
R_LOS
ODU_AIS
xxx
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. Other alarms are then sent to the downstream
Issue 08 (2011-10-30)
1-19
1 Overview
station, and are reported on the WDM side of the OTU (except that the R_LOS alarm is inserted with an ODU_AIS alarm to the downstream station).
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function
The OTU with the cross-connect function supports the service transmission in the straightthrough mode or the cross-connect mode. The processing of alarm signals in one mode is different from that in the other mode.
Straight-Through Mode
Figure 1-10 shows the unidirectional signal flow in the straight-through mode.
NOTE
The optical interface number and channel number shown in Figure 1-10 are the numbers that are displayed on the T2000.
Figure 1-10 OTU with the cross-connect function in the straight-through mode
A 3#1(RX1) 4#1(RX2) 5#1(RX3) 6#1(RX4) 1#3 1#4 1(OUT) 1#5 1#6 1#3 1(IN) 1#4 1#5 1#6 B 3#1(TX1) 4#1(TX2) 5#1(TX3) 6#1(TX4)
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 straightthrough 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 crossconnection. 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 crossconnection. l
1-20
Inter-unit cross-connection
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 08 (2011-10-30)
1 Overview
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 crossconnection. 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 3#1(RX1) 4#1(RX2) 5#1(RX3) 6#1(RX4) 1#3 1#4 1(OUT) 1#5 1#6 1#3 1(IN) 1#4 1#5 1#6 B 3#1(TX1) 4#1(TX2) 5#1(TX3) 6#1(TX4)
3#1(RX1) 4#1(RX2) 5#1(RX3) 6#1(RX4) C
1#3 1#4 1#5 1#6
In Figure 1-11, the following cross-connections are created: l l Intra-unit cross-connection from RX3 (channel 1 at optical interface 5) on unit A to OUT (channel 3 at optical interface 1) on unit A Inter-unit cross-connection from RX1 (channel 1 at optical interface 3) on unit C to OUT (channel 6 at optical interface 1) on unit A
The signals that are received from RX3 (channel 1 at optical interface 5) on unit A at the upstream station are sent to IN (channel 3 at optical interface 1) on unit B at the downstream station. The signals received from RX1 (channel 1 at optical interface 3) on unit C at the upstream station are sent to IN (channel 6 at optical interface 1) on unit B at the downstream station. The meaning of optical channels regarding the REM_SF and REM_SD alarms in the crossconnect mode is different from that in the straight-through mode. For example, when the services in channel 1 at optical interface 4 on unit A at the upstream station fail, unit B at the downstream station reports the REM_SF alarm in channel 1 at optical interface 3; when the services in channel 1 at optical interface 3 on unit C at the upstream station fail, unit B at the downstream station reports the REM_SF alarm in channel 1 at optical interface 6. Hence, when a unit reports the REM_SF or REM_SD alarm, query the cross-connections of the unit at the upstream station to locate the alarm signal source. Then, check whether the client signal status such as the optical power, fibers and optical modules in the channel at the corresponding optical interface is normal. If not, take the corresponding maintenance measures.
CAUTION
In any mode, proper configuration must be made on the T2000.
Issue 08 (2011-10-30)
1-21
1 Overview
1.4.8 Convergence OTU Processing the GE Standard Signals

This topic describes the alarm signal flow when the convergence OTU board processes the GE standard signals. Figure 1-12 and Figure 1-13 show the alarm signal flows when the convergence OTU board processes the GE standard signals.
NOTE
N#1 in Figure 1-12 represents channel 1 of optical interface N of the OTU board. For example, the optical interfaces on the client side of the ETMX board are numbered 3, 4, 5, and 6; the optical interface on the WDM side is numbered 1. Then, 3#1 represents channel 1 of optical interface 3. The ALS function of the OTU shown in the figure in this section is not enabled.
1-22
Issue 08 (2011-10-30)
1 Overview
Figure 1-12 Alarm signal flow when the convergence OTU board processes the GE standard signals - 1
Station A Client-side R_LOS R_LOS R_LOS LINK_ERR LINK_ERR LINK_ERR LINK_ERR LINK_ERR LINK_ERR No Packet No Packet N#1R_LOS N#1R_LOS ... N#1R_LOS N#1LINK_ERR N#1LINK_ERR ... N#1LINK_ERR N#1LINK_ERR N#1LINK_ERR ... N#1LINK_ERR N#1ALM_DATA_RLOS N#1ALM_DATA_RLOS ... N#1ALM_DATA_RLOS SD PM BIP8 bit errors PM_BIP8_SD/ PM_BIP8_OVER LPT=Disable LPT=Enable WDM-side WDM-side Station B Client-side Client device Client device LINK_ERR LINK_ERR ... LINK_ERR B LINK_ERR LINK_ERR ... LINK_ERR No Packet No Packet ... No Packet No Packet No Packet ... No Packet Bit errors Bit errors ... Bit errors SD SM_BIP8_SD/ SM_BIP8_OVER Bit errors Bit errors ... Bit errors
N#1REM_SF N#1REM_SF ... N#1REM_SF N#1LINK_ERR N#1LINK_ERR ... N#1LINK_ERR N#1ALM_DATA_TLOS N#1ALM_DATA_TLOS ... N#1ALM_DATA_TLOS N#1ALM_DATA_TLOS N#1ALM_DATA_TLOS ... N#1ALM_DATA_TLOS
No Packet
PM_BEI SM BIP8 bit errors
SM_BEI SF: SF event detecting SD: SD event detecting Alarm processing
XXX Detects and reports the XXX alarm
R_LOS on the client side When the R_LOS signal is detected on the client side of the OTU at station A, the R_LOS alarm is reported on the client side and is then processed on the WDM side. The alarm is sent to station B and is processed on the WDM side. The client side of station B reports the REM_SF alarm, which is then sent to the downstream client device. The client device detects the LINK_ERR alarm. The SF event is generated on the WDM side of the OTU board at station B, which triggers a service channel switching.
Issue 08 (2011-10-30)
1-23
1 Overview
LINK_ERR on the client side Auto-negotiation Mode When the LPT is disabled and the LINK_ERR signal is detected on the client side of the OTU at station A, the LINK_ERR alarm is reported on the client side and is sent to station B. The client side of station B reports the ALM_DATA_TLOS alarm, which is then sent to the downstream client device. The client device detects the No Packet signal. When the LPT is enabled and the LINK_ERR signal is detected on the client side of the OTU at station A, the LINK_ERR alarm is reported on the client side and is sent to station B. The client side of station B reports the LINK_ERR alarm, which is then sent to the downstream client device. The client device detects the LINK_ERR alarm. The alarm signal flow is the same as that in the auto-negotiation mode when the LPT is disabled.
No Packet on the client side the No Packet signal is detected on the client side of the OTU at station A, the ALM_DATA_RLOS alarm is reported on the client side and is sent to station B. The client side of station B reports the ALM_DATA_TLOS alarm, which is then sent to the downstream client device. The client device detects the No Packet alarm.
PM_BIP8_SD/PM_BIP8_OVER/SM_BIP8_SD/SM_BIP8_OVER on the WDM side The OTU board at station B receives and processes the alarm signal on the WDM side and sends the PM_BEI or SM_BEI alarm back to the WDM side of the upstream station A. In addition, the alarm signal is further sent to the downstream client device. The client device detects bit errors. The SD event is generated on the WDM side of the OTU at station B. Whether this event triggers a service channel switching is set by users.
1-24
Issue 08 (2011-10-30)
1 Overview
Figure 1-13 Alarm signal flow when the convergence OTU board processes the GE standard signals - 2
Station A Client-side WDM-side Station B WDM-side Discontinuous MFAS frames OTU_LOM PM TTI byte mismatch PM_TIM SM TTI byte mismatch SM_TIM PM_BEI PM_BDI SM_BEI SM_BDI PM_BEI PM_BDI SM_BEI Client-side Client device Client device
SM_BDI Excessive bit errors before FEC BEFFEC_EXC OTU_LOF SF LPT=Disable OTU_LOF
No Packet No Packet
...
No Packet
PM_BDI&SM_BDI ODU_AIS/ ODU_OCI/ ODU_LCK SF ODU_AIS/ LPT=Disable ODU_OCI/ ODU_LCK
No Packet No Packet
...
No Packet No Packet
PM_BDI SF R_LOS
R_LOS
LPT=Disable
No Packet
...
No Packet
LINK_ERR
PM_BDI&SM_BDI SF LPT=Enable OTU_LOF
OTU_LOF
LINK_ERR
...
LINK_ERR
PM_BDI&SM_BDI ODU_AIS/ ODU_OCI/ ODU_LCK SF ODU_AIS/ LPT=Enable ODU_OCI/ ODU_LCK
LINK_ERR LINK_ERR
...
LINK_ERR LINK_ERR
PM_BDI SF R_LOS
LPT=Enable
R_LOS
LINK_ERR
...
LINK_ERR
PM_BDI&SM_BDI SF: SF event detecting Alarm processing
Issue 08 (2011-10-30)
1-25
1 Overview
This section describes how the OTU board processes the OTU_LOM alarm and the OTU_LOF alarm. This is considered as an example to describe the alarm signal flow. The alarm signal flow of other alarms is similar. l OTU_LOM on the WDM side The OTU board at station B receives the OTU_LOM alarm on the WDM side. This alarm is not further sent to the downstream. l OTU_LOF on the WDM side Auto-negotiation Mode When the LPT is disabled and the OTU_LOF is detected on the WDM side of the OTU board at station B, the WDM side reports the OTU_LOF alarm and sends the PM_BDI and SM_BDI alarms back to the WDM side of the upstream station A. In addition, the OTU_LOF alarm is sent to the client side of station B and is processed on the client side. Then, the OTU_LOF alarm is sent to the downstream client device. The client device detects the No Packet signal. When the LPT is enabled and the OTU_LOF is detected on the WDM side of the OTU board at station B, the WDM side reports the OTU_LOF alarm and sends the PM_BDI and SM_BDI alarms back to the WDM side of the upstream station A. In addition, the OTU_LOF alarm is sent to the client side of station B and is processed on the client side. Then, the OTU_LOF alarm is sent to the downstream client device. The client device detects the LINK_ERR alarm. The alarm signal flow is the same as that in the auto-negotiation mode when the LPT is disabled. The SF event is generated on the WDM side of the OTU board at station B, which triggers a service channel switching.
1.4.9 Non-Convergence OTU Board Processing the 10GE Standard Signals

This topic describes the alarm signal flow when the non-convergence OTU board processes the 10GE standard signals. Figure 1-14 and Figure 1-15 show the alarm signal flows when the non-convergence OTU board processes the 10GE standard signals.
NOTE
The ALS function of the OTU shown in the figure in this section is not enabled.
1-26
Issue 08 (2011-10-30)
1 Overview
Figure 1-14 Alarm signal flow when the non-convergence OTU board processes the 10GE standard signals - 1
Station A Client-side WDM-side Station B WDM-side Client-side Client device Client device
R_LOS LINK_ERR No Packet
R_LOS LINK_ERR
REM_SF LINK_ERR LINK_ERR ALM_DATA_TLOS
LINK_ERR LINK_ERR No Packet
ALM_DATA_RLOS
PM BIP8 bit errors
SD PM_BIP8_SD/ PM_BIP8_OVER
Bit errors
PM_BEI SM BIP8 bit errors SD SM_BIP8_SD/ SM_BIP8_OVER Bit errors
SM_BEI SF: SF event detecting SD: SD event detecting Alarm processing
This section describes how the OTU board processes the R_LOS alarm, the LINK_ERR alarm, the ALM_DATA_RLOS alarm, and the PM_BIP8 bit errors. This is considered as an example to describe the alarm signal flow. The alarm signal flow of other alarms is similar. l R_LOS on the client side When the R_LOS signal is detected on the client side of the OTU at station A, the R_LOS alarm is reported on the client side and is then processed on the WDM side. The alarm is sent to station B and is processed on the WDM side. The client side of station B reports the LINK_ERR alarm and the REM_SF alarm, which is then sent to the downstream client device. The client device detects the LINK_ERR alarm. l LINK_ERR on the client side When the LINK_ERR signal is detected on the client side of the OTU at station A, the LINK_ERR alarm is reported on the client side and is sent to station B. The client side of station B reports the LINK_ERR alarm, which is then sent to the downstream client device. The client device detects the LINK_ERR alarm. l No Packet on the client side When the No Packet signal is detected on the client side of the OTU at station A, the ALM_DATA_RLOS alarm is reported on the client side and is sent to station B. The
Issue 08 (2011-10-30)
1-27
1 Overview
client side of station B reports the ALM_DATA_TLOS alarm, which is then sent to the downstream client device. The client device detects the No Packet signal. l PM_BIP8 bit errors on the WDM side When the PM_BIP8_SD or PM_BIP8_OVER is detected on the WDM side of the OTU board at station B, the PM_BEI is returned back to the upstream station A and the PM_BIP8_SD or PM_BIP8_OVER is sent to the downstream client device. The client device detects bit errors. The SD event is generated on the WDM side of the OTU at station B. Whether this event triggers a service channel switching is set by users. Figure 1-15 Alarm signal flow when the non-convergence OTU board processes the 10GE standard signals - 2
Station A Client-side WDM-side Discontinuous MFAS frames PM TTI byte mismatch SM TTIbyte mismatch PM_BEI PM_BDI SM_BEI SM_BDI
Excessive bit errors before FEC
Station B WDM-side OTU_LOM PM_TIM SM_TIM PM_BEI PM_BDI SM_BEI SM_BDI BEFFEC_EXC SF OTU_LOF Client-side
Client device Client device
OTU_LOF
LINK_ERR
PM_BDI&SM_BDI ODU_AIS/ ODU_OCI/ ODU_LCK SF ODU_AIS/ ODU_OCI/ ODU_LCK
LINK_ERR
PM_BDI R_LOS SF R_LOS
LINK_ERR
PM_BDI&SM_BDI SF: SF event detecting

XXX
Alarm processing
Detects and reports the XXX alarm
1-28
Issue 08 (2011-10-30)
1 Overview
This section describes how the OTU board processes the OTU_LOM alarm and the OTU_LOF alarm. This is considered as an example to describe the alarm signal flow. The alarm signal flow of other alarms is similar. l OTU_LOM on the WDM side When the discontinuous MFAS frames are detected on the WDM side of the OTU board at station B, the WDM side reports the OTU_LOM alarm, which is not sent to the downstream. l OTU_LOF on the WDM side When the OTU_LOF is detected on the WDM side of the OTU board at station B, the WDM side reports the OTU_LOF alarm and sends the PM_BDI and SM_BDI alarms back to the WDM side of the upstream station A. In addition, the OTU_LOF alarm is sent to the client side of station B and is processed on the client side. Then, the OTU_LOF alarm is sent to the downstream client device. The client device detects the LIN_ERR alarm. The SF event is generated on the WDM side of the OTU board at station B, which triggers a service channel switching.
1.5 Suppression Relation of Alarms

This section describes the rules of alarm suppression and provides the suppression relation figure of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm suppression. When the equipment is faulty, several alarms may be generated by the same optical interface. However, some alarms are not important for the maintenance engineer. For example, when the signal is lost, the optical interface generates the R_LOS alarm accompanied with the alarm indicating that the B1/B2 bit errors cross the threshold. However, the alarm indicating that the B1/B2 bit errors cross the threshold is not important for the maintenance engineer. In this case, the equipment suppresses the alarm indicating that the B1/B2 bit errors cross the threshold through the R_LOS alarm. Only the R_LOS alarm is reported by the optical interface. The rules of alarm suppression are as follows: l l The client-side alarms and the WDM-side alarms are relatively independent. There are no alarm suppression relation between the client-side alarms and the WDM-side alarms. There is no alarm suppression relation between the detection alarms related to the board hardware and the service alarms.
NOTE
Some alarms for the optical module are exceptional. For example, the R_LOS alarm suppresses the IN_PWR_LOW alarm.
There is no alarm suppression relation for the alarms that cannot be generated at the same time.
1.5.1 Suppression Relation of OTU Service Alarms on WDM Side

The suppression relation of OTU service alarms on WDM side is shown in the Figure 1-16. The alarm above the arrow suppresses the alarm below the arrow. For example: If the signal loss occurs to one optical interface on the WDM side, the optical interface only reports the R_LOS alarm but not the R_LOC , SM_BIP8_OVER, OTU_AIS and the below alarms.
1 Overview
Figure 1-16 Suppression relation of OTU service alarms on WDM side

R_LOS
OTU_AIS
R_LOC
OTU_LOF
FEC_OOF
OTU_LOM
SM_TIM
ODU_AIS/ ODU_OCI/ ODU_LCK SM_BIP8_OVER
SM_IAE
SM_BDI
SM_BIP8_SD
PM_TIM PM_BDI PM_BIP8_OVER R_LOF
SM_BEI
PM_BEI PM_BIP8_SD R_OOF
BEFFEC_EXC
MS_AIS
J0_MM
MS_RDI
B1_EXC
B2_EXC
AU_AIS
AU_LOP
MS_REI
B1_SD
B2_SD
1.5.2 Suppression Relation of OTU Service Alarms on client Side

The suppression relation of OTU service alarms on client side is shown in the Figure 1-17. The alarm above the arrow suppresses the alarm below the arrow. For example: If the signal loss occurs to one optical interface on the client side, the optical interface only reports the R_LOS alarm but not the R_LOC and R_LOF alarms.
1 Overview
Figure 1-17 Suppression relation of OTU service alarms on client side

R_LOS
R_LOF
R_LOC
R_OOF
J0_MM
MS_AIS
B1_EXC
B2_EXC
MS_RDI
MS_REI
B1_SD
B2_SD
1.6 Performance Event Suppression by Alarms

An optical interface can report several alarms and performance events. Some performance events are not important for the maintenance engineer. When the equipment is faulty, several alarms and performance events may be generated by the same optical interface. However, some alarms and performance events are not important for the maintenance engineer. For example, when the signal is lost, the optical interface generates the R_LOS alarm accompanied with the B1/B2 bit error performance event. However, the B1/B2 bit error performance event is not important for the maintenance engineer. In this case, the equipment suppresses the B1/B2 bit error performance event through the R_LOS alarm. Only the R_LOS alarm is reported by the optical interface. Table 1-4 lists the performance events suppressed by the R_LOS alarm. Table 1-4 Performance events suppressed by the R_LOS alarm MSBBE MSES MSSES MSCSES MSFEES MSFESES MSFEBBE MSFECSES MSFEUAS RSBBE RSES RSSES RSCSES RSOFS FEC_AFT_COR_ER FEC_BEF_COR_ER
Table 1-5 lists the performance events suppressed by the NO_BD_PARA alarm.
1 Overview
Table 1-5 Performance events suppressed by the NO_BD_PARA alarm LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSTMPCUR LSTMPMAX LSTMPMIN
1-32
Issue 08 (2011-10-30)
2 Alarm List
2
About This Chapter
2.2 Board Alarm List Lists the alarms of every board.
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.
Issue 08 (2011-10-30)
2-1
2 Alarm List
2.1 Product Alarm List

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

This section used a table to list the alarms starting with A. Name AD_CHECK_FAIL ALM_DATA_RLOS ALM_DATA_TLOS ALM_PIUA_OFFLINE ALM_PIUB_OFFLINE AU_AIS AU_LOP Description AD (analog to digital converter) self check failure Receiving data lost on the Ethernet port Transmitting data lost on the Ethernet port Power interface unit A offline Power interface unit B offline AU alarm indication signal AU loss of pointer Level Major Minor Minor Major Major Major Major
2.1.2 Alarm List B

This section used a table to list the alarms starting with B. Name B1_EXC B1_SD B2_EXC B2_SD BD_VER_NMAT BD_STATUS BEFFEC_EXC Description Regenerator section (B1) excessive errors Regenerator section(B1) signal degraded Multiplex section (B2) excessive errors Multiplex section (B2) signal degraded Board version mismatch Board is not in position Signal excessive errors before FEC alarm Level Minor Minor Major Minor Major Major Minor
2-2
Issue 08 (2011-10-30)
2 Alarm List
Name BEFFEC_SD BOOTROM_BAD
Description Signal degraded alarm before FEC alarm BOOTROM checksum alarm
Level Minor Major
2.1.3 Alarm List C

This section used a table to list the alarms starting with C. Name CFGBD_FAIL CFG_VERIFY CFGDATA_OUTRANGE CHAN_ADD CHAN_LOS CLT_MM COMMUN_FAIL Description Board configuration is mismatched Configuration is not verified Board configuration data out of range alarm Channel of single wave signal addition Channel of single wave signal loss Service type on the client is not match Board serial port communication failure Level Major Major Major Major Critical Major Major
2.1.4 Alarm List D

This section used a table to list the alarms starting with D. Name DBMS_ERROR DBMS_PROTECT_MODE DCM_INSUFF DSP_LOAD_FAIL Description Database error Database in protect mode Insufficient dispersion compensation margin DSP software loading failure Level Major Critical Minor Critical
2.1.5 Alarm List E

This section used a table to list the alarms starting with E.
Issue 08 (2011-10-30)
2-3
2 Alarm List
Name EDFA_TEMP_OVER
Description EDFA temperature exceeds the threshold
Level Critical
2.1.6 Alarm List F

This section used a table to list the alarms starting with F. Name FAN_FAIL FCSERRORS_OVER FEC_LOF FEC_OOF FIBER_CRITICAL FIBER_MAJOR FIBER_MINOR FPGA_ABN Description Fan failed CRC errors cross the upper threshold Loss of FEC frame Out of FEC frame OTDR testing fiber critical alarm OTDR testing fiber major alarm OTDR testing fiber minor alarm FPGA status is abnormal Level Major Minor Critical Critical Critical Major Minor Major
2.1.7 Alarm List H

This section used a table to list the alarms starting with H. Name HARD_BAD HARD_FAIL Description Hardware failed Board hardware failed Level Critical Critical
2.1.8 Alarm List I

This section used a table to list the alarms starting with I. Name INPWR_FAIL IN_PWR_HIGH IN_PWR_LOW Description Input power failed Input power is too high Input power is too low Level Major Critical Critical
2-4
Issue 08 (2011-10-30)
2 Alarm List
2.1.9 Alarm List J

This section used a table to list the alarms starting with J. Name J0_MM Description J0 byte/trace indicator mismatch Level Minor
2.1.10 Alarm List K

This section used a table to list the alarms starting with K. Name K1_K2_M K2_M Description K1, K2 mismatch K2 mismatch Level Minor Minor
2.1.11 Alarm List L

This section used a table to list the alarms starting with L. Name LAN_LOC LASER_HAZARD_WARNING LINK_ERR LINK_STATUS LOCK_CUR_FAIL LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER LTI L_SYNC Description Ethernet communication failure Laser level hazard warning Link error Link status abnormality Pump driving current is out of lock Indication of loop operating Cooling current of the laser over threshold Laser will be out of work Laser temperature exceeds the threshold All clock sources are lost Loss of synchronization alarm Level Major Critical Critical Critical Critical Minor Major Critical Major Major Critical
2.1.12 Alarm List M

This section used a table to list the alarms starting with M.
2 Alarm List
Name MAIL_ERR MOD_COM_FAIL MODULE_COOLCUR_OVER MODULE_TEMP_OVER MS_AIS MS_RDI MS_REI MUT_LOS MUT_TLOS
Description Mail communication error Module communication failure Module cooling current exceeds the threshold Module temperature exceeds the threshold Multiplex section alarm indication Multiplex section remote defect indication Multiplex section remote error indication Loss of multiplexed signals Loss of the output multiplexed signals
Level Major Major Major Major Major Minor Warning Critical Critical
2.1.13 Alarm List N

This section used a table to list the alarms starting with N. Name NESOFT_MM NESTATE_INSTALL NEBD_XC_DIF NO_BD_SOFT NO_BD_PARA Description Software difference between working and protection boards NE is in install state Crossing data of NE and board different No board software No board parameter Level Critical Critical Major Critical Critical
2.1.14 Alarm List O

This section used a table to list the alarms starting with O. Name OA_LOW_GAIN OCH_FDI Description Optical amplification gain low Forward defect indication at OCH layer
Level Critical Major
2-6
Issue 08 (2011-10-30)
2 Alarm List
Name OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI ODU_TCMn_AIS ODU_TCMn_BDI ODU_TCMn_BEI ODU_TCMn_DEG ODU_TCMn_EXC ODU_TCMn_LCK ODU_TCMn_LTC ODU_TCMn_OCI ODU_TCMn_SD ODU_TCMn_SSF ODU_TCMn_TIM OMS_BDI
Description Forward defect indication (overhead) at OCH layer Forward defect indication (payload) at OCH layer Loss of signal (payload) at OCH layer Open connection indication at OCH layer Server signal fail at OCH layer Server signal fail (overhead) at OCH layer Server signal fail (payload) at OCH layer ODU (optical channel data unit) alarm indication signal ODU locked ODU (Optical channel data unit) open connection indication ODU1 TCMn alarm indication signal ODU1 TCMn backward defect indication ODU1 TCMn backward error indication ODU1 TCMn signal degraded ODU1 TCMn section BIP8 excessive error defect ODU1 TCMn signal locked Loss of ODU1 TCMn serial connection ODU1 TCMn open connection indication ODU1 TCMn signal degrade ODU1 TCMn Server signal fail ODU1 TCMn TTI mismatch Backward defect indication at OMS layer
Level Minor Major Critical Minor Major Minor Major Major Major Major Major Minor Major Minor Major Minor Minor Minor Major Critical Minor Minor
Issue 08 (2011-10-30)
2-7
2 Alarm List
Name OMS_BDI-O OMS_BDI-P OMS_FDI OMS_FDI-O OMS_FDI-P OMS_LOS-P OMS_SSF OMS_SSF-O OMS_SSF-P OOS_LOST OPS_MAIN_BAK_ATTR_DIFF OPS_PS_FAIL OPS_PS_FIXED OPS_PS_INDI OPU2_PLM OPU3_PLM OTU_AIS OTU_LOF OTU_LOM OSC_LOS OSC_RDI OUTPWR_FAIL
Description Backward defect indication (overhead) at OMS layer Backward defect indication (payload) at OMS layer Forward defect indication at OMS layer Forward defect indication (overhead) at OMS layer Forward defect indication (payload) at OMS layer Loss of signal (payload) at OMS layer Server signal fail at OMS layer Server signal fail (overhead) at OMS layer Server signal fail (payload) at OMS layer Loss of OTM overhead signal Attribute difference between working and protection channel Failure of optical channel protection switching Alarm of optical channel protection switching Indication of optical channel protection switching OPU2 payload mismatch OPU3 payload mismatch OTU (optical transponder unit) alarm indication signal Loss of FAS frame MFAS multi-frame alignment signal is discontinuous. Loss of OSC signal Remote defect indication Output power failed
Level Minor Minor Major Minor Major Critical Major Minor Major Minor Critical Major Major Major Major Major Major Critical Major Critical Minor Major
2-8
Issue 08 (2011-10-30)
2 Alarm List
Name OUT_PWR_HIGH OUT_PWR_LOW
Description Output power is too high Output power is too low
Level Major Major
2.1.15 Alarm List P

This section used a table to list the alarms starting with P. Name PATCH_ERR PATCH_NOT_CONFIRM PATCHFILE_NOTEXIST PATH_VERIFY_ALM Description Patch error The patch file does not exist Actived patch has not been confirmed overtime Failure in checking dual-end configuration consistency of the physical and logical channels Duration of patch package in activation state too long Duration of patch package in deactivation state too long Patch package file error PDU unit is offline ODU layer PM section backward defect indication ODU layer PM section backward error indication ODU layer PM section BIP-8 excessive error defect ODU layer PM section BIP-8 degraded signal defect ODU layer PM section trail trace identifier (TTI) mismatch Client port module offline Optical switch switching failure Power difference between monitored working and protection channels Level Major Major Major Major
PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR PDU_OFF_ALM PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE PORTSWITCH_FAIL POWER_DIFF_DEFECT
Minor Minor Major Critical Major Major Major Major Major Major Major Minor
Issue 08 (2011-10-30)
2-9
2 Alarm List
Name POWER_DIFF_OVER
Description Power difference between monitored working and protection channels crosses the upper threshold Board's power failure Power status alarm Loss of PRBS (Pseudo-Random Binary Sequence) signal Path priority configurations at both ends are not consistent PS (protection switching) indication Working current of pump laser over threshold Cool current of pump laser over threshold Working temperature of the pump laser over threshold Abnormal power supply (common overload or shortage) Abnormal power supply (severe overload or shortage) The power interface unit temperature overhigh alarm Offline of DPFU boardBackup power use alarm
Level Major
POWER_FAIL POWERALM PRBS_LSS PRIORITY_VERIFY_ALM PS PUM_BCM_ALM PUM_COOL_EXC PUM_TEM_ALM PWR_MIN_ALM PWR_MAJ_ALM PWR_TEMP_OVERTH PW_SWITCH_EX
Major Critical Minor Major Major Major Critical Major Major Critical Major Critical
2.1.16 Alarm List R

This section used a table to list the alarms starting with R. Name REAR_BD_OFFLINE RELAY_ALARM REM_SD REM_SF RL_CRITICAL_HI RL_CRITICAL_LOW
2-10
Description Offline of DPFU board PMU relay alarm Remote signal degrade Remote signal failure alarm indication Critical high return loss alarm Critical low return loss alarm
Level Major Critical Minor Minor Critical Critical

Issue 08 (2011-10-30)
2 Alarm List
Name R_DATA_LOST R_LOC R_LOF R_LOS R_OOF RMON_ALM_ALIGNMENT_OV ER RMON_ALM_DROPEVENT_OV ER RMON_ALM_FCSERROR_OVE R RMON_ALM_INBADOCTS_OV ER RMON_ALM_OUTBADOCTS_O VER R_SLIP
Description Ethernet port receiving data lost Loss of clock on receiving line Loss of frame Loss of signal Out of frame Alignment errors is over the upper threshold Statistics of drop packets events is over the upper threshold Statistics of check errors is over the upper threshold Statistics of receiving bad packets is over the upper threshold Statistics of transmitting bad packets is over the upper threshold Receiving side frame slipping
Level Minor Critical Critical Critical Critical Minor Minor Minor Minor Minor Major
2.1.17 Alarm List S

This section used a table to list the alarms starting with S. Name SCC_LOC SECU_ALM SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM Description Loss of SCC clock Security alarm OTU layer SM section backward defect indication OTU layer SM section backward error indication OTU layer SM section BIP-8 excessive error defect OTU layer SM section BIP-8 degraded signal defect OTU layer, SM section incoming alignment error OTU layer SM section trail trace identifier (TTI) is mismatched
Level Critical Major Major Major Major Major Major Major
Issue 08 (2011-10-30)
2-11
2 Alarm List
Name SPEED_OVER SUBRACK_ID_CONFLICT SUB_RACK_NUM_OUTRANGE SUB_RACK_OFFLINE SUM_INPWR_HI SUM_INPWR_LOW SUM_OUTPWR_HI SUM_OUTPWR_LOW SWDL_ACTIVATED_TIMEOUT SWDL_AUTOMATCH_INH SWDL_CHGMNG_NOMATCH SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKG_NOBDSOFT SWDL_PKGVER_MM SWDL_ROLLBACK_FAIL SYSLOG_COMM_FAIL
Description The data rate exceeds the set limits Conflict of subrack ID. Number of online slave subracks over threshold Slave subrack offline Input optical power is too high Input optical power is too low Output optical power is too high Output optical power is too low Activation time out Automatic match inhibited SCC board changed alarm Commit failure alarm NE is loading package Loss of file Board software cancelled during the loading of package Package version conformance check failed NE rollback failed NE and syslog server communication failed
Level Minor Critical Critical Critical Major Major Major Major Critical Minor Critical Minor Warning Critical Minor Minor Minor Major
2.1.18 Alarm List T

This section used a table to list the alarms starting with T. Name T_DATA_LOST T_LOC T_SLIP TD TEM_HA
2-12
Description Client-side transmitting data lost Loss of transmit clock Transmitted side frame slipping Transmitter degrade Laser temperature is too high
Level Minor Major Major Critical Major

Issue 08 (2011-10-30)
2 Alarm List
Name TEM_LA TEMP_ALARM TF THUNDERALM TP_LOC
Description Laser temperature is too low The ambient temperature of the board exceeds the threshold. Transmission failure Thunder protection circuit failure Transmission phase lock ring loss of clock
Level Major Minor Critical Minor Major
2.1.19 Alarm List V

This section used a table to list the alarms starting with V. Name VCXO_LOC Description Local oscillator loss of clock Level Major
2.1.20 Alarm List W

This section used a table to list the alarms starting with W. Name WAVE_LEN_LOCK_FAIL W_R_FAILURE WRG_BD_TYPE Description Wavelength locking failure alarm Writing or reading chip register failed Physical board is mismatched with configured board Level Critical Major Major
2.2 Board Alarm List

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

AD_CHECK_FAIL BD_STATUS FPGA_ABN NO_BD_PARA OMS_FDI OMS_FDI-O OMS_SSF-P POWER_FAIL SUM_INPWR_HI
Issue 08 (2011-10-30)
2-13
2 Alarm List
MODULE_COOLCUR_O VER MODULE_TEMP_OVER MUT_LOS NO_BD_SOFT
OMS_FDI-P OMS_LOS-P OMS_SSF OMS_SSF-O
SUM_INPWR_LOW TEMP_ALARM W_R_FAILURE
2.2.2 DCP Board Alarm List

BD_STATUS FPGA_ABN MUT_LOS NO_BD_PARA NO_BD_SOFT POWER_DIFF_DEFECT POWER_DIFF_OVER POWER_FAIL PS R_LOS TEMP_ALARM W_R_FAILURE
2.2.3 ELOG/ELOGS Board Alarm List

AD_CHECK_FAIL ALM_DATA_RLOS ALM_DATA_TLOS BD_STATUS BEFFEC_EXC REM_SF CLT_MM COMMUN_FAIL FPGA_ABN IN_PWR_HIGH IN_PWR_LOW LINK_ERR LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE
2-14
OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OPU2_PLM OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH
PORT_MODULE_OFFLINE POWER_FAIL PRBS_LSS PW_SWITCH_EX R_LOC R_LOS RMON_ALM_FCSERROR_O VER RMON_ALM_INBADOCTS_ OVER RMON_ALM_OUTBADOCT S_OVER SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM
Issue 08 (2011-10-30)
2 Alarm List
LTEMP_OVER MODULE_TEMP_OVER NO_BD_PARA NO_BD_SOFT OCH_FDI L_SYNC
OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM
TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL
2.2.4 ETMX/ETMXS Board Alarm List

AD_CHECK_FAIL B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC REM_SD REM_SF COMMUN_FAIL FEC_LOF MS_AIS FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVER NO_BD_PARA NO_BD_SOFT OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OPU2_PLM OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE POWER_FAIL PRBS_LSS PW_SWITCH_EX R_LOC R_LOF R_LOS R_OOF SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL ODU_TCM1_BEI ODU_TCM1_LCK
Issue 08 (2011-10-30)
2-15
2 Alarm List
ODU_TCM1_AIS ODU_TCM1_DEG ODU_TCM1_LTC ODU_TCM1_SSF ODU_TCM2_BDI ODU_TCM2_EXC ODU_TCM2_OCI ODU_TCM2_TIM ODU_TCM3_BEI ODU_TCM3_LCK ODU_TCM3_SD ODU_TCM4_AIS ODU_TCM4_DEG ODU_TCM4_LTC ODU_TCM4_SSF ODU_TCM5_BDI ODU_TCM5_EXC ODU_TCM5_OCI ODU_TCM5_TIM ODU_TCM6_BEI ODU_TCM6_LCK ODU_TCM6_SD
ODU_TCM1_BDI ODU_TCM1_EXC ODU_TCM1_OCI ODU_TCM1_TIM ODU_TCM2_BEI ODU_TCM2_LCK ODU_TCM2_SD ODU_TCM3_AIS ODU_TCM3_DEG ODU_TCM3_LTC ODU_TCM3_SSF ODU_TCM4_BDI ODU_TCM4_EXC ODU_TCM4_OCI ODU_TCM4_TIM ODU_TCM5_BEI ODU_TCM5_LCK ODU_TCM5_SD ODU_TCM6_AIS ODU_TCM6_DEG ODU_TCM6_LTC ODU_TCM6_SSF
ODU_TCM1_SD ODU_TCM2_AIS ODU_TCM2_DEG ODU_TCM2_LTC ODU_TCM2_SSF ODU_TCM3_BDI ODU_TCM3_EXC ODU_TCM3_OCI ODU_TCM3_TIM ODU_TCM4_BEI ODU_TCM4_LCK ODU_TCM4_SD ODU_TCM5_AIS ODU_TCM5_DEG ODU_TCM5_LTC ODU_TCM5_SSF ODU_TCM6_BDI ODU_TCM6_EXC ODU_TCM6_OCI ODU_TCM6_TIM
2.2.5 FDG Board Alarm List

AD_CHECK_FAIL AU_AIS AU_LOP B1_EXC B1_SD B2_EXC NO_BD_PARA NO_BD_SOFT OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P POWER_FAIL PS PW_SWITCH_EX R_LOF R_LOS R_DATA_LOST
2-16
Issue 08 (2011-10-30)
2 Alarm List
B2_SD BD_STATUS BEFFEC_EXC REM_SF FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LINK_STATUS LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MS_AIS MS_RDI MS_REI
OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFF LINE
R_LOC R_OOF RMON_ALM_FCSERROR_OVE R RMON_ALM_INBADOCTS_OV ER RMON_ALM_OUTBADOCTS_ OVER SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM T_DATA_LOST T_LOC TD TEMP_ALARM TF VCXO_LOC W_R_FAILURE
2.2.6 FIU Board Alarm List

E3FIU AD_CHECK_FAIL BD_STATUS FPGA_ABN NO_BD_PARA NO_BD_SOFT OOS_LOST TEMP_ALARM W_R_FAILURE
E2FIU AD_CHECK_FAIL NO_BD_SOFT TEMP_ALARM
Issue 08 (2011-10-30)
2-17
2 Alarm List
BD_STATUS MUT_LOS NO_BD_PARA
POWER_FAIL SUM_INPWR_HI SUM_INPWR_LOW
W_R_FAILURE
2.2.7 FMU Board Alarm List

BD_STATUS FIBER_CRITICAL FIBER_MAJOR FIBER_MINOR FPGA_ABN MOD_COM_FAIL NO_BD_PARA NO_BD_SOFT TEMP_ALARM W_R_FAILURE
2.2.8 HBA Board Alarm List

BD_STATUS FPGA_ABN IN_PWR_HIGH IN_PWR_LOW LSR_WILL_DIE MOD_COM_FAIL MODULE_TEMP_OVER MUT_LOS NO_BD_SOFT OA_LOW_GAIN OUT_PWR_HIGH POWER_FAIL PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM TEMP_ALARM W_R_FAILURE LASER_HAZARD_WAR NING
2.2.9 ITL Board Alarm List

BD_STATUS TEMP_ALARM FPGA_ABN NO_BD_SOFT
2.2.10 LBE/LBES Board Alarm List

AD_CHECK_FAIL ALM_DATA_RLOS ALM_DATA_TLOS NO_BD_PARA OCH_FDI OCH_FDI-O PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE
2-18
Issue 08 (2011-10-30)
2 Alarm List
BD_STATUS BEFFEC_EXC REM_SF REM_SD COMMUN_FAIL FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW LINK_ERR LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVE R NO_BD_SOFT
OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER
POWER_FAIL PW_SWITCH_EX R_LOC R_LOS RMON_ALM_FCSERROR_O VER SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL L_SYNC
2.2.11 LBF/LBFS Board Alarm List

AD_CHECK_FAIL ALM_DATA_RLOS ALM_DATA_TLOS B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC NO_BD_SOFT NO_BD_PARA OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O PORT_MODULE_OFFLINE POWER_FAIL PRBS_LSS PW_SWITCH_EX R_LOC R_LOF R_LOS R_OOF RMON_ALM_ALIGNMENT_ OVER
Issue 08 (2011-10-30)
2-19
2 Alarm List
REM_SD REM_SF COMMUN_FAIL FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LINK_ERR LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MS_AIS ODU_TCM1_AIS ODU_TCM1_DEG ODU_TCM1_LTC ODU_TCM1_SSF ODU_TCM2_BDI ODU_TCM2_EXC ODU_TCM2_OCI ODU_TCM2_TIM ODU_TCM3_BEI ODU_TCM3_LCK ODU_TCM3_SD ODU_TCM4_AIS ODU_TCM4_DEG ODU_TCM4_LTC ODU_TCM4_SSF
OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OPU2_PLM OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM ODU_TCM1_BDI ODU_TCM1_EXC ODU_TCM1_OCI ODU_TCM1_TIM ODU_TCM2_BEI ODU_TCM2_LCK ODU_TCM2_SD ODU_TCM3_AIS ODU_TCM3_DEG ODU_TCM3_LTC ODU_TCM3_SSF ODU_TCM4_BDI ODU_TCM4_EXC ODU_TCM4_OCI ODU_TCM4_TIM
RMON_ALM_DROPEVENT_ OVER RMON_ALM_FCSERROR_OV ER SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL ODU_TCM1_BEI ODU_TCM1_LCK ODU_TCM1_SD ODU_TCM2_AIS ODU_TCM2_DEG ODU_TCM2_LTC ODU_TCM2_SSF ODU_TCM3_BDI ODU_TCM3_EXC ODU_TCM3_OCI ODU_TCM3_TIM ODU_TCM4_BEI ODU_TCM4_LCK ODU_TCM4_SD ODU_TCM5_AIS ODU_TCM5_DEG ODU_TCM5_LTC
2-20
Issue 08 (2011-10-30)
2 Alarm List
ODU_TCM5_BDI ODU_TCM5_EXC ODU_TCM5_OCI ODU_TCM5_TIM ODU_TCM6_BEI ODU_TCM6_LCK ODU_TCM6_SD
ODU_TCM5_BEI ODU_TCM5_LCK ODU_TCM5_SD ODU_TCM6_AIS ODU_TCM6_DEG ODU_TCM6_LTC ODU_TCM6_SSF
ODU_TCM5_SSF ODU_TCM6_BDI ODU_TCM6_EXC ODU_TCM6_OCI ODU_TCM6_TIM MODULE_TEMP_OVER L_SYNC
2.2.12 LOG/LOGS Board Alarm List

AD_CHECK_FAIL ALM_DATA_RLOS ALM_DATA_TLOS BD_STATUS BEFFEC_EXC REM_SF CLT_MM COMMUN_FAIL FPGA_ABN IN_PWR_HIGH IN_PWR_LOW LINK_ERR LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVE R NO_BD_PARA NO_BD_SOFT
Issue 08 (2011-10-30)
OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD
PORT_MODULE_OFFLINE POWER_FAIL PRBS_LSS PW_SWITCH_EX R_LOC R_LOS RMON_ALM_FCSERROR_OVE R RMON_ALM_INBADOCTS_OV ER RMON_ALM_OUTBADOCTS_ OVER SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE
2-21
2 Alarm List
OCH_FDI L_SYNC
PM_TIM REM_SD
WAVE_LEN_LOCK_FAIL
2.2.13 LQM Board Alarm List

AD_CHECK_FAIL B1_SD B1_EXC BD_STATUS BEFFEC_EXC REM_SD REM_SF DSP_LOAD_FAIL ESCON_CODE_ERROR FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM L_SYNC LINK_STATUS LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MS_AIS NO_BD_PARA NO_BD_SOFT OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE POWER_FAIL PW_SWITCH_EX R_DATA_LOST R_LOC R_LOF R_LOS R_OOF RMON_ALM_FCSERROR_OV ER RMON_ALM_FCSERROR_UN DER SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM T_DATA_LOST TD TEMP_ALARM TF VCXO_LOC W_R_FAILURE
2-22
Issue 08 (2011-10-30)
2 Alarm List
2.2.14 LU40 Board Alarm List

AD_CHECK_FAIL B1_EXC BEFFEC_EXC COMMUN_FAIL HARD_FAIL J0_MM LSR_COOL_ALM MODULE_TEMP_OVER OCH_FDI OCH_LOS-P OCH_SSF-O ODU_LCK OTU_AIS OUT_PWR_HIGH PM_BEI PM_TIM PRBS_LSS RMON_ALM_ALIGNMEN T_OVER R_LOC SM_BDI SM_BIP8_SD TEMP_ALARM ODU_TCM1_AIS ODU_TCM1_DEG ODU_TCM1_LTC ODU_TCM1_SSF ODU_TCM2_BDI B1_SD BEFFEC_SD DCM_INSUFF IN_PWR_HIGH LINK_ERR LSR_WILL_DIE NO_BD_PARA OCH_FDI-O OCH_OCI OCH_SSF-P ODU_OCI OTU_LOF OUT_PWR_LOW PM_BIP8_OVER PORT_MODULE_OFFLINE REM_SD RMON_ALM_DROPEVEN T_OVER R_LOF SM_BEI SM_IAE TF W_R_FAILURE ODU_TCM1_BDI ODU_TCM1_EXC ODU_TCM1_OCI ODU_TCM1_TIM ODU_TCM2_BEI BD_STATUS CLT_MM FPGA_ABN IN_PWR_LOW LOOP_ALM LTEMP_OVER NO_BD_SOFT OCH_FDI-P OCH_SSF ODU_AIS OPU3_PLM OTU_LOM PM_BDI PM_BIP8_SD POWER_FAIL REM_SF RMON_ALM_FCSERRO R_OVER R_LOS SM_BIP8_OVER SM_TIM WAVE_LEN_LOCK_FAI L ODU_TCM1_BEI ODU_TCM1_LCK ODU_TCM1_SD ODU_TCM2_AIS ODU_TCM2_DEG ODU_TCM2_LTC
Issue 08 (2011-10-30)
2-23
2 Alarm List
ODU_TCM2_EXC ODU_TCM2_OCI ODU_TCM2_TIM ODU_TCM3_BEI ODU_TCM3_LCK ODU_TCM3_SD ODU_TCM4_AIS ODU_TCM4_DEG ODU_TCM4_LTC ODU_TCM4_SSF ODU_TCM5_BDI ODU_TCM5_EXC ODU_TCM5_OCI ODU_TCM5_TIM ODU_TCM6_BEI ODU_TCM6_LCK ODU_TCM6_SD
ODU_TCM2_LCK ODU_TCM2_SD ODU_TCM3_AIS ODU_TCM3_DEG ODU_TCM3_LTC ODU_TCM3_SSF ODU_TCM4_BDI ODU_TCM4_EXC ODU_TCM4_OCI ODU_TCM4_TIM ODU_TCM5_BEI ODU_TCM5_LCK ODU_TCM5_SD ODU_TCM6_AIS ODU_TCM6_DEG ODU_TCM6_LTC ODU_TCM6_SSF
ODU_TCM2_SSF ODU_TCM3_BDI ODU_TCM3_EXC ODU_TCM3_OCI ODU_TCM3_TIM ODU_TCM4_BEI ODU_TCM4_LCK ODU_TCM4_SD ODU_TCM5_AIS ODU_TCM5_DEG ODU_TCM5_LTC ODU_TCM5_SSF ODU_TCM6_BDI ODU_TCM6_EXC ODU_TCM6_OCI ODU_TCM6_TIM
2.2.15 LU40S Board Alarm List

AD_CHECK_FAIL B1_EXC BEFFEC_EXC COMMUN_FAIL HARD_FAIL J0_MM LSR_COOL_ALM MODULE_TEMP_OVER OCH_FDI OCH_LOS-P OCH_SSF-O B1_SD BEFFEC_SD DCM_INSUFF IN_PWR_HIGH LINK_ERR LSR_WILL_DIE NO_BD_PARA OCH_FDI-O OCH_OCI OCH_SSF-P ODU_OCI BD_STATUS CLT_MM FPGA_ABN IN_PWR_LOW LOOP_ALM LTEMP_OVER NO_BD_SOFT OCH_FDI-P OCH_SSF ODU_AIS OPU3_PLM
2-24
Issue 08 (2011-10-30)
2 Alarm List
ODU_LCK OTU_AIS OUT_PWR_HIGH PM_BEI PM_TIM PRBS_LSS RMON_ALM_ALIGNMEN T_OVER R_LOC SM_BDI SM_BIP8_SD TEMP_ALARM ODU_TCM1_AIS ODU_TCM1_DEG ODU_TCM1_LTC ODU_TCM1_SSF ODU_TCM2_BDI ODU_TCM2_EXC ODU_TCM2_OCI ODU_TCM2_TIM ODU_TCM3_BEI ODU_TCM3_LCK ODU_TCM3_SD ODU_TCM4_AIS ODU_TCM4_DEG ODU_TCM4_LTC ODU_TCM4_SSF ODU_TCM5_BDI ODU_TCM5_EXC ODU_TCM5_OCI
Issue 08 (2011-10-30)
OTU_LOF OUT_PWR_LOW PM_BIP8_OVER PORT_MODULE_OFFLINE REM_SD RMON_ALM_DROPEVEN T_OVER R_LOF SM_BEI SM_IAE TF W_R_FAILURE ODU_TCM1_BDI ODU_TCM1_EXC ODU_TCM1_OCI ODU_TCM1_TIM ODU_TCM2_BEI ODU_TCM2_LCK ODU_TCM2_SD ODU_TCM3_AIS ODU_TCM3_DEG ODU_TCM3_LTC ODU_TCM3_SSF ODU_TCM4_BDI ODU_TCM4_EXC ODU_TCM4_OCI ODU_TCM4_TIM ODU_TCM5_BEI ODU_TCM5_LCK ODU_TCM5_SD
OTU_LOM PM_BDI PM_BIP8_SD POWER_FAIL REM_SF RMON_ALM_FCSERRO R_OVER R_LOS SM_BIP8_OVER SM_TIM WAVE_LEN_LOCK_FAI L ODU_TCM1_BEI ODU_TCM1_LCK ODU_TCM1_SD ODU_TCM2_AIS ODU_TCM2_DEG ODU_TCM2_LTC ODU_TCM2_SSF ODU_TCM3_BDI ODU_TCM3_EXC ODU_TCM3_OCI ODU_TCM3_TIM ODU_TCM4_BEI ODU_TCM4_LCK ODU_TCM4_SD ODU_TCM5_AIS ODU_TCM5_DEG ODU_TCM5_LTC ODU_TCM5_SSF ODU_TCM6_BDI
2-25
2 Alarm List
ODU_TCM5_TIM ODU_TCM6_BEI ODU_TCM6_LCK ODU_TCM6_SD
ODU_TCM6_AIS ODU_TCM6_DEG ODU_TCM6_LTC ODU_TCM6_SSF
ODU_TCM6_EXC ODU_TCM6_OCI ODU_TCM6_TIM
2.2.16 LUR40/LUR40S Board Alarm List

AD_CHECK_FAIL BEFFEC_SD FPGA_ABN IN_PWR_LOW LTEMP_OVER NO_BD_SOFT OCH_FDI-P OCH_SSF ODU_AIS OPU3_PLM OTU_LOM PM_BDI PM_BIP8_SD POWER_FAIL SM_BDI SM_BIP8_SD TEMP_ALARM BD_STATUS COMMUN_FAIL HARD_FAIL LSR_COOL_ALM MODULE_TEMP_OVER OCH_FDI OCH_LOS-P OCH_SSF-O ODU_LCK OTU_AIS OUT_PWR_HIGH PM_BEI PM_TIM R_LOC SM_BEI SM_IAE TF BEFFEC_EXC DCM_INSUFF IN_PWR_HIGH LSR_WILL_DIE NO_BD_PARA OCH_FDI-O OCH_OCI OCH_SSF-P ODU_OCI OTU_LOF OUT_PWR_LOW PM_BIP8_OVER PORT_MODULE_OFFLINE R_LOS SM_BIP8_OVER SM_TIM W_R_FAILURE
2.2.17 LWC1 Board Alarm List

AD_CHECK_FAIL B1_EXC B1_SD B2_EXC NO_BD_PARA NO_BD_SOFT OCH_FDI OCH_FDI-O PORT_MODULE_OFFLINE POWER_FAIL PS PW_SWITCH_EX
2-26
Issue 08 (2011-10-30)
2 Alarm List
B2_SD BD_STATUS BEFFEC_EXC REM_SD REM_SF COMMUN_FAIL FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVER MS_AIS
OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD
R_LOC R_LOF R_LOS R_OOF SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF VCXO_LOC W_R_FAILURE WAVE_LEN_LOCK_FAIL PM_TIM
2.2.18 LWF/LWFS Board Alarm List

AD_CHECK_FAIL B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC REM_SD REM_SF COMMUN_FAIL NO_BD_PARA OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS PM_TIM PORT_MODULE_OFFLINE POWER_FAIL PS PW_SWITCH_EX R_LOC R_LOF R_LOS R_OOF SM_BDI
Issue 08 (2011-10-30)
2-27
2 Alarm List
FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVER NO_BD_SOFT ODU_TCM1_AIS ODU_TCM1_DEG ODU_TCM1_LTC ODU_TCM1_SSF ODU_TCM2_BDI ODU_TCM2_EXC ODU_TCM2_OCI ODU_TCM2_TIM ODU_TCM3_BEI ODU_TCM3_LCK ODU_TCM3_SD ODU_TCM4_AIS ODU_TCM4_DEG ODU_TCM4_LTC ODU_TCM4_SSF ODU_TCM5_BDI ODU_TCM5_EXC ODU_TCM5_OCI ODU_TCM5_TIM
ODU_LCK ODU_OCI OPU2_PLM OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD ODU_TCM1_BDI ODU_TCM1_EXC ODU_TCM1_OCI ODU_TCM1_TIM ODU_TCM2_BEI ODU_TCM2_LCK ODU_TCM2_SD ODU_TCM3_AIS ODU_TCM3_DEG ODU_TCM3_LTC ODU_TCM3_SSF ODU_TCM4_BDI ODU_TCM4_EXC ODU_TCM4_OCI ODU_TCM4_TIM ODU_TCM5_BEI ODU_TCM5_LCK ODU_TCM5_SD ODU_TCM6_AIS
SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL MS_AIS ODU_TCM1_BEI ODU_TCM1_LCK ODU_TCM1_SD ODU_TCM2_AIS ODU_TCM2_DEG ODU_TCM2_LTC ODU_TCM2_SSF ODU_TCM3_BDI ODU_TCM3_EXC ODU_TCM3_OCI ODU_TCM3_TIM ODU_TCM4_BEI ODU_TCM4_LCK ODU_TCM4_SD ODU_TCM5_AIS ODU_TCM5_DEG ODU_TCM5_LTC ODU_TCM5_SSF ODU_TCM6_BDI ODU_TCM6_EXC
2-28
Issue 08 (2011-10-30)
2 Alarm List
ODU_TCM6_BEI ODU_TCM6_LCK ODU_TCM6_SD
ODU_TCM6_DEG ODU_TCM6_LTC ODU_TCM6_SSF
ODU_TCM6_OCI ODU_TCM6_TIM
2.2.19 LWX Board Alarm List

B1_EXC B1_SD BD_STATUS CFGBD_FAIL FCSERRORS_OVER FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE NO_BD_SOFT OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE POWER_FAIL PRBS_LSS R_LOC R_LOF R_LOS SPEED_OVER TD TEM_HA TEM_LA TEMP_ALARM TF TP_LOC W_R_FAILURE PW_SWITCH_EX NO_BD_PARA
2.2.20 M40 Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN MODULE_COOLCUR_O VER MODULE_TEMP_OVER MUT_LOS NO_BD_SOFT NO_BD_PARA OMS_BDI OMS_BDI-O OMS_BDI-P POWER_FAIL SUM_OUTPWR_HI SUM_OUTPWR_LOW TEMP_ALARM W_R_FAILURE
Issue 08 (2011-10-30)
2-29
2 Alarm List
2.2.21 MCA Board Alarm List

BD_STATUS CHAN_ADD CHAN_LOS FPGA_ABN NO_BD_PARA NO_BD_SOFT PORTSWITCH_FAIL TEMP_ALARM W_R_FAILURE
2.2.22 MR2 Board Alarm List

BD_STATUS TEMP_ALARM FPGA_ABN NO_BD_SOFT
2.2.23 MWA Board Alarm List

BD_STATUS FPGA_ABN TEMP_ALARM NO_BD_SOFT
2.2.24 MWF Board Alarm List

BD_STATUS FPGA_ABN TEMP_ALARM NO_BD_SOFT
2.2.25 OAU Board Alarm List

AD_CHECK_FAIL BD_STATUS DSP_LOAD_FAIL EDFA_TEMP_OVER FPGA_ABN IN_PWR_HIGH LASER_HAZARD_WARN ING IN_PWR_LOW LSR_WILL_DIE MUT_LOS NO_BD_SOFT NO_BD_PARA OA_LOW_GAIN POWER_FAIL PUM_BCM_ALM PUMP_COOL_EXC PUM_TEM_ALM TEMP_ALARM W_R_FAILURE
2-30
Issue 08 (2011-10-30)
2 Alarm List
2.2.26 OBU Board Alarm List

AD_CHECK_FAIL BD_STATUS DSP_LOAD_FAIL EDFA_TEMP_OVER FPGA_ABN IN_PWR_HIGH LASER_HAZARD_WARN ING IN_PWR_LOW LSR_WILL_DIE MUT_LOS NO_BD_SOFT NO_BD_PARA OA_LOW_GAIN POWER_FAIL PUM_BCM_ALM PUMP_COOL_EXC PUM_TEM_ALM TEMP_ALARM W_R_FAILURE
2.2.27 OLP Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN MUT_LOS NO_BD_PARA NO_BD_SOFT IN_PWR_HIGH IN_PWR_LOW POWER_DIFF_DEFECT POWER_DIFF_OVER POWER_FAIL PS R_LOS TEMP_ALARM W_R_FAILURE
2.2.28 OPU Board Alarm List

AD_CHECK_FAIL BD_STATUS DSP_LOAD_FAIL EDFA_TEMP_OVER FPGA_ABN IN_PWR_HIGH IN_PWR_LOW LSR_WILL_DIE MUT_LOS NO_BD_SOFT NO_BD_PARA OA_LOW_GAIN POWER_FAIL PUM_BCM_ALM PUMP_COOL_EXC PUM_TEM_ALM TEMP_ALARM W_R_FAILURE
2.2.29 PMU Board Alarm List

BD_STATUS PDU_OFF_ALM
Issue 08 (2011-10-30)
PWR_MIN_ALM POWERALM
TEMP_ALARM THUNDERALM
2-31
2 Alarm List
POWER_FAIL PWR_MAJ_ALM
REAR_BD_OFFLINE RELAY_ALARM
2.2.30 RMU9 Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN MODULE_TEMP_OVE R MUT_LOS MUT_TLOS NO_BD_PARA NO_BD_SOFT OMS_BDI OMS_BDI-O OMS_BDI-P OMS_FDI OMS_FDI-O OMS_FDI-P OMS_LOS-P OMS_SSF OMS_SSF-O OMS_SSF-P PORT_MODULE_OFFLINE POWER_FAIL SUM_INPWR_HI SUM_INPWR_LOW SUM_OUTPWR_HI SUM_OUTPWR_LOW TEMP_ALARM
2.2.31 RPC Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN GAINDATA_MIS LOCK_CUR_FAIL LSR_WILL_DIE NO_BD_PARA NO_BD_SOFT OUT_PWR_HIGH OUT_PWR_LOW POWER_FAIL PUM_BCM_ALM PUMP_COOL_EXC RL_CRITICAL_HI RL_CRITICAL_LOW TEMP_ALARM W_R_FAILURE LASER_HAZARD_WA RNING
2.2.32 SC1/SC2 Board Alarm List

BD_STATUS FPGA_ABN IN_PWR_HIGH NO_BD_SOFT NO_BD_PARA OSC_LOS SCC_LOC T_SLIP TD
2-32
Issue 08 (2011-10-30)
2 Alarm List
IN_PWR_LOW LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTI R_SLIP
OSC_RDI OUT_PWR_HIGH OUT_PWR_LOW R_LOF R_LOS
TEMP_ALARM TF VCXO_LOC W_R_FAILURE
2.2.33 SCC Board Alarm List

ALM_PIUA_OFFLINE BD_VER_NMAT CFG_VERIFY FAN_FAIL K1_K2_M MAIL_ERR NESOFT_MM OPS_MAIN_BAK_ATTR_ DIFF OUTPWR_FAIL PATCHFILE_NOTEXIST PATCH_NOT_CONFIRM PATCH_DEACT_TIMEOUT POWER_FAIL PWR_TEMP_OVERTH SECU_ALM SWDL_NEPKGCHECK SWDL_PKGVER_MM SWDL_ROLLBACK_FAIL ALM_PIUB_OFFLINE BOOTROM_BAD DBMS_ERROR FUSE_ALARM K2_M MDL_ALARM NESTATE_INSTALL OPS_PS_FAIL OPS_PS_FIXED PATH_VERIFY_ALM PRIORITY_VERIFY_ALM PATCH_ACT_TIMEOUT REAR_BD_OFFLINE SWDL_ACTIVATED_TIME OUT SWDL_COMMIT_FAIL SWDL_CHGMNG_NOMATCH SYSLOG_COMM_FAIL W_R_FAILURE BD_STATUS CFGDATA_OUTRANGE DBMS_PROTECT_MOD E INPWR_FAIL LAN_LOC NEBD_XC_DIF NO_BD_SOFT OPS_PS_INDI PATCH_ERR PBU_BD_OFFLINE PWR_MAJ_ALM PATCH_PKGERR RELAY_ALARM SWDL_AUTOMATCH_I NH SWDL_INPROCESS SWDL_PKG_NOBDSOFT TEMP_ALARM WRG_BD_TYPE
Issue 08 (2011-10-30)
2-33
2 Alarm List
2.2.34 TMR/TMRS Board Alarm List

AD_CHECK_FAIL BD_STATUS BEFFEC_EXC COMMUN_FAIL FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVER NO_BD_SOFT NO_BD_PARA OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE POWER_FAIL PW_SWITCH_EX R_LOC R_LOS SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL
2.2.35 TMX/TMXS Board Alarm List

AD_CHECK_FAIL B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC REM_SD MS_RDI MS_REI NO_BD_PARA NO_BD_SOFT OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P PM_BIP8_SD PM_TIM POWER_FAIL PW_SWITCH_EX PORT_MODULE_OFFLINE PRBS_LSS R_LOC R_LOF
2-34
Issue 08 (2011-10-30)
2 Alarm List
REM_SF COMMUN_FAIL FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVER MS_AIS PM_BIP8_OVER
OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI
R_LOS R_OOF SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM T_LOC TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL
2.2.36 TMX40/TMX40S Board Alarm List

AD_CHECK_FAIL B1_EXC BEFFEC_EXC DCM_INSUFF IN_PWR_HIGH LINK_ERR LSR_WILL_DIE NO_BD_PARA OCH_FDI-O OCH_OCI OCH_SSF-P ODU_OCI OTU_LOF ALM_DATA_RLOS B1_SD CLT_MM FPGA_ABN IN_PWR_LOW LOOP_ALM LTEMP_OVER NO_BD_SOFT OCH_FDI-P OCH_SSF ODU_AIS OPU3_PLM OTU_LOM ALM_DATA_TLOS BD_STATUS COMMUN_FAIL HARD_FAIL J0_MM LSR_COOL_ALM MODULE_TEMP_OVER OCH_FDI OCH_LOS-P OCH_SSF-O ODU_LCK OTU_AIS OUT_PWR_HIGH
Issue 08 (2011-10-30)
2-35
2 Alarm List
OUT_PWR_LOW PM_BIP8_OVER PORT_MODULE_OFFLINE REM_SD R_LOF SM_BEI SM_IAE ODU_TCM1_AIS ODU_TCM1_DEG ODU_TCM1_LTC ODU_TCM1_SSF ODU_TCM2_BDI ODU_TCM2_EXC ODU_TCM2_OCI ODU_TCM2_TIM ODU_TCM3_BEI ODU_TCM3_LCK ODU_TCM3_SD ODU_TCM4_AIS ODU_TCM4_DEG ODU_TCM4_LTC ODU_TCM4_SSF ODU_TCM5_BDI ODU_TCM5_EXC ODU_TCM5_OCI ODU_TCM5_TIM ODU_TCM6_BEI ODU_TCM6_LCK ODU_TCM6_SD TF
PM_BDI PM_BIP8_SD POWER_FAIL REM_SF R_LOS SM_BIP8_OVER SM_TIM ODU_TCM1_BDI ODU_TCM1_EXC ODU_TCM1_OCI ODU_TCM1_TIM ODU_TCM2_BEI ODU_TCM2_LCK ODU_TCM2_SD ODU_TCM3_AIS ODU_TCM3_DEG ODU_TCM3_LTC ODU_TCM3_SSF ODU_TCM4_BDI ODU_TCM4_EXC ODU_TCM4_OCI ODU_TCM4_TIM ODU_TCM5_BEI ODU_TCM5_LCK ODU_TCM5_SD ODU_TCM6_AIS ODU_TCM6_DEG ODU_TCM6_LTC ODU_TCM6_SSF W_R_FAILURE
PM_BEI PM_TIM PRBS_LSS R_LOC SM_BDI SM_BIP8_SD TEMP_ALARM ODU_TCM1_BEI ODU_TCM1_LCK ODU_TCM1_SD ODU_TCM2_AIS ODU_TCM2_DEG ODU_TCM2_LTC ODU_TCM2_SSF ODU_TCM3_BDI ODU_TCM3_EXC ODU_TCM3_OCI ODU_TCM3_TIM ODU_TCM4_BEI ODU_TCM4_LCK ODU_TCM4_SD ODU_TCM5_AIS ODU_TCM5_DEG ODU_TCM5_LTC ODU_TCM5_SSF ODU_TCM6_BDI ODU_TCM6_EXC ODU_TCM6_OCI ODU_TCM6_TIM
2-36
Issue 08 (2011-10-30)
2 Alarm List
2.2.37 TRC1 Board Alarm List

AD_CHECK_FAIL B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC COMMUN_FAIL FEC_LOF FEC_OOF FPGA_ABN IN_PWR_HIGH IN_PWR_LOW J0_MM LSR_COOL_ALM LSR_WILL_DIE LTEMP_OVER MODULE_TEMP_OVER PM_BIP8_OVER NO_BD_SOFT NO_BD_PARA OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS ODU_LCK ODU_OCI OTU_AIS OTU_LOF OTU_LOM OUT_PWR_HIGH OUT_PWR_LOW PM_BDI PM_BEI PM_BIP8_SD PM_TIM POWER_FAIL PW_SWITCH_EX R_LOC R_LOF R_LOS R_OOF SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TD TEMP_ALARM TF W_R_FAILURE WAVE_LEN_LOCK_FAIL
2.2.38 V40 Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN MODULE_TEMP_OVER MUT_LOS NO_BD_SOFT NO_BD_PARA OMS_BDI OMS_BDI-O OMS_BDI-P POWER_FAIL SUM_OUTPWR_HI SUM_OUTPWR_LOW TEMP_ALARM W_R_FAILURE
Issue 08 (2011-10-30)
2-37
2 Alarm List
2.2.39 VA4 Board Alarm List

AD_CHECK_FAIL BD_STATUS IN_PWR_HIGH IN_PWR_LOW NO_BD_PARA NO_BD_SOFT OUT_PWR_HIGH OUT_PWR_LOW POWER_FAIL R_LOS TEMP_ALARM W_R_FAILURE
2.2.40 VOA Board Alarm List

BD_STATUS NO_BD_PARA NO_BD_SOFT
2.2.41 WMU Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN HARD_BAD MODULE_TEMP_OVER NO_BD_PARA NO_BD_SOFT PORT_MODULE_OFFLINE POWER_FAIL TEMP_ALARM CHAN_LOS
2.2.42 WSD9 Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN MOD_COM_FAIL MODULE_TEMP_OVER MUT_LOS NO_BD_PARA NO_BD_SOFT OMS_BDI OMS_BDI_O OMS_BDI_P OMS_FDI OMS_FDI-O OMS_FDI-P OMS_LOS-P OMS_SSF OMS_SSF-O OMS_SSF-P POWER_FAIL SUM_INPWR_HI SUM_INPWR_LOW TEMP_ALARM W_R_FAILURE
2.2.43 WSM9 Board Alarm List

AD_CHECK_FAIL
2-38
NO_BD_SOFT
OMS_SSF
Issue 08 (2011-10-30)
2 Alarm List
BD_STATUS FPGA_ABN MOD_COM_FAIL MODULE_TEMP_OVER MUT_LOS MUT_TLOS NO_BD_PARA
OMS_BDI OMS_BDI_O OMS_BDI_P OMS_FDI OMS_FDI-O OMS_FDI-P OMS_LOS-P
OMS_SSF-O OMS_SSF-P POWER_FAIL SUM_INPWR_HI SUM_INPWR_LOW TEMP_ALARM W_R_FAILURE
2.2.44 WSMD2 Board Alarm List

AD_CHECK_FAIL MODULE_TEMP_OVER MUT_TLOS OMS_BDI OMS_FDI OMS_LOS-P OMS_SSF-P SUM_INPWR_LOW BD_STATUS MOD_COM_FAIL NO_BD_PARA OMS_BDI-O OMS_FDI-O OMS_SSF POWER_FAIL TEMP_ALARM FPGA_ABN MUT_LOS NO_BD_SOFT OMS_BDI-P OMS_FDI-P OMS_SSF-O SUM_INPWR_HI W_R_FAILURE
2.2.45 WSMD4 Board Alarm List

AD_CHECK_FAIL BD_STATUS FPGA_ABN MOD_COM_FAIL MODULE_TEMP_OVER MUT_LOS MUT_TLOS NO_BD_PARA NO_BD_SOFT OMS_BDI OMS_BDI-O OMS_BDI-P OMS_FDI OMS_FDI-O OMS_FDI-P OMS_LOS-P OMS_SSF OMS_SSF-O OMS_SSF-P POWER_FAIL SUM_INPWR_HI SUM_INPWR_LOW TEMP_ALARM W_R_FAILURE
Issue 08 (2011-10-30)
2-39
3 Alarm Processing
3
About This Chapter
Alarm Processing
3.1 Common Alarm Processing 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. 3.2 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.
Issue 08 (2011-10-30)
3-1
3 Alarm Processing
3.1 Common Alarm Processing

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 this alarm persists, contact Huawei engineers for troubleshooting.
The alarm handling involves board reset, either of software or hardware. Software reset and hardware reset have different impacts on services. l Reset of the SCC board: A software reset of the SCC is a restart of the upper-layer software, which neither updates the FPGA file or hardware data nor interrupts services. A hardware reset of the SCC will result in reconfiguration of the key hardware, such as FPGA reloading; the upper-layer software need be restarted. 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.
3.1.1 ALM_DATA_RLOS
Description
Receiving data lost on the Ethernet port. The board regularly checks the total number of the received bytes and compares the number with the number of last time. The alarm is generated when the two numbers are the same, which indicating that the board does not receive any data. Reported from the WDM side or client side: client side.
Attribute
Alarm Severity Minor Alarm Type 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 Parameter 1 Meaning Indicates the Ethernet port where the alarm is generated. For example, 0x01 indicates Ethernet port 1.
3-2
Issue 08 (2011-10-30)
3 Alarm Processing
Name
Meaning
Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. It consists of two bytes. The value of these two parameters is always 0x00 0x01, which indicates channel 1.
Impact on the System

The connection status of the Ethernet port is normal; however, the optical signals do not have data packet. As a result, the services may be interrupted.
Possible Causes
l l l Cause 1: The data equipment on the client side stops sending data. Cause 2: The data configuration is incorrect. Cause 3: The Ethernet port of the board is faulty, which cannot receive data.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The data equipment on the client side stops sending data. 1. l Check whether the data equipment on the client side (including test meters) stops sending data. If yes, start to send data again. Check whether the receive wavelength on the client side of the board that reports the alarm is consistent with the transmit wavelength at the port of the data equipment. If not, replace the module at the port of the data equipment. Check whether the port where the alarm is generated is configured with logical service but does not access any real service. If yes, delete the logical service or suppress this alarm. Check whether the LINK_ERR alarm is generated at the Ethernet port. If yes, troubleshoot the LINK_ERR alarm. If the alarm persists, check whether there are other alarms on the board that reports the alarm. If there are other alarms, troubleshoot these alarms. If the alarm persists, the board may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 2: The data configuration is incorrect. 1.
2.
Cause 3: The Ethernet port of the board is faulty, which cannot receive data. 1. 2. 3.
----End
Related Information
The alarm is a warning alarm used as an auxiliary warning for fault judgement. Generally, the alarm is generated when the test meter or client-side data equipment stops sending data packet. The possibility that the alarm is generated due to the faulty board is low.
Issue 08 (2011-10-30)
3-3
3 Alarm Processing
3.1.2 ALM_DATA_TLOS
Description
Transmitting data lost on the Ethernet port. The board regularly checks the total number of the transmitted bytes and compares the number with the number of last time. The alarm is generated when the two numbers are the same, which indicates that the board does not transmit any data. Reported from the WDM side or client side: client side.
Attribute
Parameters

The connection status of the Ethernet port is normal; however, the optical signals do not have data packet. As a result, the services may be interrupted.
Possible Causes
l l Cause 1: The WDM side at the local station does not receive data and thus no data is sent from the client side. Cause 2: The WDM side at the local station receives data but the client side does not send data because the board is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The WDM side at the local station receives no data and thus no data is sent from the client side.
3-4
3 Alarm Processing
1. 2. l
Check whether the board at the opposite station reports an ALM_DATA_RLOS alarm. If the ALM_DATA_RLOS is detected on the OTU board at the opposite station, see ALM_DATA_RLOS for how to troubleshoot the alarm at the opposite station.
Cause 2: The WDM side at the local station receives data but the client side does not send data because the board is faulty. 1. If the board at the opposite station does not report an ALM_DATA_RLOS alarm, perform a cold reset on the faulty board at the local station on the T2000 or reset the faulty board. For details, see the Troubleshooting. If the alarm persists, replace the board that reports the alarm. For details, see Replacing a Board of the Supporting Tasks.
2. ----End
Related Information
None
3.1.3 B1_EXC
Description
Regenerator section (B1) excessive errors. The alarm is generated when the received SDH signals degrade and the B1 bit errors in the multiplex section exceed the threshold. Reported from the WDM side or client side: WDM side client side. l l The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received on the WDM side exceed the B1 bit error threshold. The alarm is generated on the client side when the B1 bit errors in the SDH signals received on the client side exceed the B1 bit error threshold.
Attribute
Alarm Severity Minor Alarm Type Service 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 Parameter 1 Meaning Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.
Issue 08 (2011-10-30)
3-5
3 Alarm Processing
Name
Meaning

The B1 bit errors in the service signals received by the board exceed the threshold of the B1 bit errors set for the board. The alarm affects the QoS of the service signals.
Possible Causes
l l l l Cause 1 for the alarm generated on the client side: The input signals on the client side contain the bit errors. Cause 1 for the alarm generated on the WDM side: The receive side of the local station is faulty. Cause 2 for the alarm generated on the WDM side: The attenuation of the received signals is excessively high; the fiber or connector is not clean. Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The input signals on the client side contain the bit errors. 1. If the alarm is reported from the client side, it indicates that the input signals on the client side contain bit errors. In this case, eliminate the bit errors according to the manual of the client equipment.
Cause 1 for the alarm generated on the WDM side: The receive side of the local station is faulty.
Detects and reports the B1_EXC alarm OTU1 Client side WDM side
O A D M F I U F I U O A D M
Detects and reports the B1_EXC alarm
OTU2
Out-loop
WDM side Client side
Station A
Station B
1.
Configure outloop at the transmit and receive optical interfaces on the WDM side of the OTU2. If there are no bit error alarms on the OTU1, it indicates that the board at the local station is faulty. Replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
Cause 2 for the alarm generated on the WDM side: The attenuation of the received signals is excessively high; the fiber or connector is not clean.
3-6
3 Alarm Processing
1.
If there are bit errors, check whether the transmit optical power at the corresponding optical interfaces on the opposite OTU1 on the T2000. For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the optical power is normal, check the fiber and clean the fiber connector.
2. l
Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station is faulty. 1. If the optical power is abnormal, check whether the B1_EXC alarm is generated on the client side of the opposite OTU1. If yes, eliminate the B1_EXC alarm on the client side. If not, it indicates that the opposite OTU1 is faulty. Replace the opposite OTU1. For the optical power specification of the specific board, see Technical Specifications of the Product Description .
----End
Related Information
None.
3.1.4 BEFFEC_EXC
Description
Signal degraded before FEC alarm. 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 is generated when the counted bit error rate exceeds the threshold. Reported from the WDM or client side: WDM side.
Attribute
Parameters
Issue 08 (2011-10-30)
3-7
3 Alarm Processing
Name
Meaning

The error tolerance of the system decreases, which affects the quality of signals if the decrease is sufficient.
Possible Causes
l Cause 1: The OTU board input optical power is excessively high or low. The system performance declines. For example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or non-linearity occurs. Cause 2: The board at the opposite station is faulty. Cause 3: The board that reports the alarm is faulty.
l l
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The OTU board input optical power is excessively high or low. The system performance declines. For example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or non-linearity occurs. 1. Check whether the receive optical power on the T2000 is within the normal range, For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the input optical power is abnormal, see the methods for handling the IN_PWR_HIGH and IN_PWR_LOW. If the optical power is normal, it is possible that the system performance degrades, For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting.
2. 3. l
Cause 2 and cause 3: The board at the opposite station may be faulty; the board at the local station may be faulty. 1. 2. If the alarm persists, the OTU board that reports the alarm may be faulty. Replace the OTU board, For details, see Replacing a Board of the Supporting Tasks. If the alarm persists, the board at the opposite station may be faulty. Replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
Related Cases: l l MD-A13 Bit Error Alarm Is Generated When Optical Power Gets Close to the Threshold MC-A55 Improper DCM Distribution Causes Abnormal Service of the OptiX BWS 1600G Equipment after the Upgrade
3-8
3 Alarm Processing
3.1.5 CHAN_LOS
Description
Channel of single wave signal loss alarm. The alarm is generated when the MCA (optical spectrum analyzing) board detects that the original channel is lost after it scans the optical spectrum. Reported from the WDM side or client side: NA.
Attribute
Alarm Severity Critical Alarm Type 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. Name Parameter 1 Meaning Indicates the ID of the optical interface where the alarm is generated, namely, the ID of the optical interface the MCA detects. For example, 0x01 denotes that the MCA detects optical interface 1.
Parameters 2 and 3 Indicates the ID of the channel where the alarm is generated, namely, the ID of the wavelength at which the alarm is reported. For example, 0x00 0x01 denotes that the alarm is reported in channel (or at wavelength) 1. Parameters 4 and 5 The value is 0xff of every parameter.

l l The services of the related wavelength are unavailable. The MCA cannot monitor the optical spectrum performance of the wavelength related to the alarm.
Possible Causes
l Cause 1: The wavelength that needs to be monitored is not accessed. For example, in the following figure, 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.
Issue 08 (2011-10-30)
3 Alarm Processing
MCA M U X / D M U X
1 OTU1 2 OTU2 Client side WDM side
OA
OA
F I U
F I U
OA
OA
M U X / D M U X
1 OTU3 2 OTU4 WDM side Client side
Station A
Station B
l l l 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. Cause 3: The attenuation of the multiplexer or OA unit upstream of the MCA is excessively high. Cause 4: The OTU board located before the MCA is faulty. For example, OTU1 in the preceding figure is faulty. Cause 5: The MCA that reports the alarm is faulty.
Procedure
l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Parameter 2 and parameter 3 indicate the number of wavelengths in which the alarm is generated. Cause 1: The wavelengths needs to be monitored is not accessed. 1. Check whether the wavelength where the alarm is generated is required in the actual network. If not, modify the wavelength monitoring configuration of the MCA so that the monitoring of the wavelength is disabled. 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. Check whether the laser of the OTU that transmits the wavelength is shut down. If the laser is shut down, opening the Laser.
2.
Cause 2: The laser of the board at the opposite station is shut down. 1.
Cause 3: The attenuation of the multiplexer or OA unit upstream of the MCA is excessively high. 1. Query the output optical power of the upstream OTU board connected to the multiplexer unit. Check whether the queried output optical power of the upstream OTU board is within the normal range. 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, see Technical Specifications of the Product Description . If the optical power is excessively low or there is no light, check the attenuation that is set for the input optical power on the multiplexer or OA unit. If the attenuation is excessively high, decrease the attenuation for the multiplexer or OA unit.
NOTE
2.
Output optical power of the multiplexer or OA unit (dBm) = Input optical power at the IN port on the MCA (dBm) - 10lg("MON"/"OUT") (dBm). "MON"/"OUT" represents the split ratio of the MON port on the multiplexer or OA unit.
l
3-10
Cause 4: The OTU upstream of the MCA is faulty.

3 Alarm Processing
1.
Query the input optical power at the optical interface where the alarm is generated on the MCA. If the data is abnormal, replace the OTU that transmits the wavelength to the MCA. For details, see Replacing a Board of the Supporting Tasks. 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. If the alarm persists, replace the MCA that reports the alarm. For details, see Replacing a Board of the Supporting Tasks.
Cause 5: The MCA that reports the alarm is faulty. 1.
2. ----End
Related Information
None.
3.1.6 FCSERRORS_OVER
Description
CRC errors cross the upper threshold. The alarm is generated when the number of bad packet events detected by the Ethernet port of the board crosses the upper threshold. Reported from the WDM or client side: WDM side.
Attribute
Parameters
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is generated. For example, 0x00 0x01 indicates channel 1 of the port indicated by parameter 1.
Issue 08 (2011-10-30)
3-11
3 Alarm Processing

The Ethernet QoS is degraded.
Possible Causes
l l l l l Cause 1: The client data equipment is faulty. As a result, the data sent contains a large number of CRC error packets. Cause 2: CRC error packets are generated at the receive end because the input optical power is excessively high or low. Cause 3: The optical interface modes (and the fiber modes) of the two connected Ethernet ports are inconsistent. Cause 4: The fiber is damaged or the fiber connector is dirty. Cause 5: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The client data equipment is faulty. As a result, the data sent contains a large number of CRC error packets. 1. Use a BER detector to check whether the data transmitted from the client equipment contains bit errors. If there are bit errors in the data, troubleshoot the faults on the client equipment.
Cause 2 and cause 4: CRC error packets are generated at the receive end because the input optical power is excessively high or low. The fiber is damaged or the fiber connector is dirty. 1. Check whether the input optical power of the Ethernet port is within the normal. For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the optical power is abnormal, troubleshoot the alarm according to the handling procedure for the IN_PWR_HIGH or IN_PWR_LOW alarm. If the optical power is normal, proceed with the next step.
2. l
Cause 3: The optical interface modes (and the fiber modes) of the two connected Ethernet ports are not consistent. 1. If the alarm persists, check whether the optical interface mode (and the fiber mode) of the two connected Ethernet ports are consistent. For the optical interface mode of the board, see Hardware Description. If they are not consistent, replace the fiber or board to ensure that the optical interface mode and the fiber type of the two Ethernet ports are consistent. If the alarm persists, replace the board that reports the alarm. For details, see Replacing a Board of the Supporting Tasks.
Cause 5: The board that reports the alarm is faulty. 1.
----End
Related Information
None.
3 Alarm Processing
3.1.7 IN_PWR_HIGH
Description
Input optical power is excessively high. The alarm is generated when the input optical power is higher than the upper threshold of the input optical power. Reported from the WDM side or client side: WDM side, client side.
Attribute
Parameters
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is generated. For example, 0x00 0x01 indicates channel 1 of the optical interface indicated by parameter 1.

When the input optical power is excessively high, bit errors and LOF alarms may be generated in the received signals, and the optical module on the board can be damaged. As a result, the services are affected.
Possible Causes
l l l l l Cause 1 for the alarm generated on the client side: The input optical power is excessively high, and the attenuation configured is insufficient. Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The output optical power of the board in the upstream station is excessively high. Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. Cause 1 for the alarm generated in multiple wavelengths: The input optical power is excessively high, and the attenuation configured is insufficient.
Issue 08 (2011-10-30)
3 Alarm Processing
l l
Cause 2 for the alarm generated in multiple wavelengths: The output optical power of the board in the upstream station is excessively high. Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the 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 T2000 to check whether the input optical power is within the normal range. For the optical power specifications of the specific board, see the Product Description. If the input power is abnormal as shown on the T2000, use a optical 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. If the input optical power of the board that reports the alarm is normal, the board may be faulty. In this case, replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. 1.
Cause 1 for the alarm generated on the WDM side: The output optical power of the board in the upstream station is excessively high. 1. If the alarm is generated on the WDM side, query the input optical power of the board that reports the alarm on the T2000 to check whether the input optical power is within the normal range. For the optical power specifications of the specific board, see the Product Description. If the input optical power is abnormal, query the input and output optical power of the boards upstream of the OTU in a reversed sequence of the signal flow on the T2000. Locate the board with very low optical power, and then adjust the input optical power of the board to a proper value.
Cause 2 for the 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. For details, see Replacing a Board of the Supporting Tasks.
Cause 1 for the alarm generated in multiple wavelengths: The input optical power is excessively high, and the attenuation configured is insufficient. 1. Test the input and output optical power of the board in the opposite station in the reversed sequence of signal flow on the T2000. Locate the board with very high optical power, and then adjust the input optical power of the board to a proper value.
Cause 2 for the alarm generated in multiple wavelengths: The upstream board outputs very high optical power. 1. 2. Test the input and output optical power of the board in the opposite station in the reversed sequence of signal flow on the T2000. If the optical power is excessively high, check the input and output optical power of the upstream boards in turn to determine whether they are within a normal range. If both the input and output optical power of the upstream boards are abnormal, adjust
3-14
3 Alarm Processing
the input optical power to a proper value. For the optical power specifications of the specific board, see Product Description. 3. If the input optical power of the upstream board is within a normal range, whereas the output optical power is abnormal, the upstream board may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarm is faulty. 1. If the alarm persists, query the input optical power of the board that reports the alarm on the T2000 to check whether the input optical power is within a normal range. For the optical power specifications of the specific board, see Product Description. If the input optical power is abnormal as shown on the T2000, the board may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
3.1.8 IN_PWR_LOW
Description
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
Parameters
Issue 08 (2011-10-30)
3-15
3 Alarm Processing

If the input optical power is excessively low, bit errors may be generated in the received signals, which affect the normal receiving of the services.
Possible Causes
l l l l l l l Cause 1 for the alarm generated on the client side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attached to the optical interface on the board that reports the alarm is excessively high. Cause 3 for the alarm generated on the client side: The channel use status setting of the board that reports the alarm is incorrect. Cause 4 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuator attached to the optical interface on the board that reports the alarm is excessively high. Cause 3 for the alarm generated on the WDM side: The attenuation attached to the transmit optical interface on the board at the opposite station is excessively high, or the transmit optical module is faulty. Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission of the optical signals is excessively high and the compensation is insufficient. Cause 5 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
l l
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. 1. Use an optical power meter to measure the input optical power of the local board to determine whether the input optical power is within the normal range. For the optical power specifications of the specific board, see the Product Description. If the detected power is excessively low, check the fiber connection. If the fiber connector is dirty, clean or replace the fiber connector. For details, see the Troubleshooting. 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.
2.
3. l
Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attached to the optical interface on the board that reports the alarm is excessively high. 1. If the alarm persists, check whether the attenuation of the attenuator attached to the receive optical interface is excessively high. If the attenuation is excessively high, decrease the attenuation value of the attenuator to a proper value or replace it with a suitable attenuator. If the alarm persists, replace the board that reports the alarm. For details, see Replacing a Board of the Supporting Tasks.
2.
3-16
3 Alarm Processing
Cause 3 for the alarm generated on the client side: The channel use status setting of the board that reports the alarm is incorrect. 1. Check whether the channel use status setting on the T2000 is the same as that of the actual channel use status setting of the board. If not, resetting the channel use status.
Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. 1. Use an optical power meter to measure the input optical power of the local board to determine whether the input optical power is within the normal range. For the optical power specifications of the specific board, see the Product Description. If the detected power is excessively low, check the fiber connection. If the fiber connector is dirty, clean or replace the fiber connector. For details, see the Troubleshooting. 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.
2.
3. l
Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuator attached to the optical interface on the board that reports the alarm is excessively high. 1. If the alarm persists, check whether the attenuation of the attenuator attached to the receive optical interface is excessively high. If the attenuation is excessively high, decrease the attenuation value of the attenuator to a proper value or replace it with a suitable attenuator.
Cause 3 for the alarm generated on the WDM side: The attenuation attached to the transmit optical interface on the board at the opposite station is excessively high, or the transmit optical module is faulty. 1. Check the board at the opposite station. If the laser on the board is shut down, of the attenuation of the attenuator attached to the transmit optical interface on the board is excessively high, open the laser or decrease the attenuation value of the attenuator to a proper value, or replace the attenuator with a suitable attenuator to ensure that the output optical power of the board is within the normal range. If the alarm persists, query the performance value and alarms related to the output optical power of the board at the opposite station. If the performance value shown in the query result does not meet the specification requirement and, for example, the TF alarm is generated, it indicates that the optical module is faulty. Replace the board at the opposite station. For details, see Replacing a Board of the Supporting Tasks.
2.
Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission of the optical signals is excessively high and the compensation is insufficient. Cause 5 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. Query the input and output optical power of the boards upstream of the OTU at the local station in the reversed sequence of signal flow on the T2000. Locate the board with the very low optical power, and then adjust the input optical power of the board to a proper value. Check the input and output optical power of the upstream stations one by one in the reversed sequence of signal flow on the T2000 and locate the faulty section where the optical power is excessively low. 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 Troubleshooting;
2.
3.
Issue 08 (2011-10-30)
3 Alarm Processing
4. 5. l
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. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
If the alarm is generated in multiple wavelengths, the alarm handling method is similar to the handling method for the alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB. Related Cases: l l MC-A19 Use Power Monitoring To Process Problems On Wavelength Division MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
3.1.9 LINK_ERR
Description
Link error alarm. The 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 Critical Alarm Type 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. Parameter Parameter 1 Description Indicates the Ethernet port where the alarm is generated. For example, 0x01 indicates Ethernet port 1.
3-18
Issue 08 (2011-10-30)
3 Alarm Processing

When the link status of the Ethernet ports is down, a valid link cannot be created between the two data ports and the data services are interrupted.
Possible Causes
l l Cause 1: The service type of the client equipment mismatches the service type of the interconnected OTU. 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 nonnegotiation. Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or very low. Cause 4: The optical interface modes (and the fiber modes) of the two interconnected Ethernet ports are inconsistent. Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails. Cause 6: The data equipment on the client side is faulty. Cause 7: The board that reports the alarm is faulty.
l l l l l
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. 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, setting the service type of the board or replace the OTU with a proper service type. For details, see Replacing a Board of the Supporting Tasks.
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.
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or very low. 1. Check whether the input optical power of the Ethernet port on the two ports that are interconnected is within the normal range. For the optical power specifications of the specific board, see the Product Description. If the input optical power is abnormal, see the handling procedures for the IN_PWR_HIGH or IN_PWR_LOW alarms.
2. l
Cause 4: The optical module types of the two interconnected Ethernet boards are inconsistent. Hence, the types of fibers that the two optical modules 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.
Issue 08 (2011-10-30)
3 Alarm Processing
Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails. 1. Check whether the fiber or cable that is used to connect the two Ethernet ports are properly connected. If they are not properly connected, reconnect or replace the fiber or cable. Check whether the data equipment on the client side is faulty. If the equipment is faulty, troubleshoot the fault of the data equipment on the client side. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 6: The data equipment on the client side is faulty. 1.
----End
Related Information
Related Cases: l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
3.1.10 LINK_STATUS
Description
LINK status abnormality. The alarm is generated when the link status of the data port is down. Reported from the WDM or client side: client side.
Attribute
Parameters
3-20
Issue 08 (2011-10-30)
3 Alarm Processing

When the link status of the Ethernet ports is down, the available link cannot be created between the two data ports and the data services are interrupted.
Possible Causes
l l Cause 1: The service type of the client equipment mismatches the service type of the interconnected OTU. Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports are not consistent. For example, The auto-negotiation is enabled for one port but disabled for the other. Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or very low. Cause 4: The optical interface modes (and the fiber modes) of the two interconnected Ethernet ports are inconsistent. Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails. Cause 6: The data equipment on the client side is faulty. Cause 7: The board that reports the alarm is faulty.
l l l l l
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. 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 the service type of the OTU at the local station does not match the type of the services transmitted from the client data equipment, first check if the configuration of the service type is correct, then consider to replace the board with a board of a proper service type. For details, see Replacing a Board of the Supporting Tasks.
Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports are not consistent. 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.
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or very low. 1. Check whether the input optical power of the two interconnected Ethernet ports is within the normal range. For the optical power specifications of the specific board, see the Product Description. If the input optical power is abnormal, see the handling procedures for the IN_PWR_HIGH or IN_PWR_LOW alarms.
2. l
Cause 4: The optical interface modes (and the fiber modes) of the two interconnected Ethernet ports are inconsistent. 1. Check whether the optical interface mode (and the fiber mode) of the two connected Ethernet ports are consistent. If they are not consistent, replace the fiber or board to
Issue 08 (2011-10-30)
3 Alarm Processing
ensure that the optical interface mode and the fiber type of the two Ethernet ports are consistent. l Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails. 1. Check whether the fiber or cable that is used to connect the two Ethernet ports are properly connected. If they are not properly connected, reconnect or replace the fiber or cable. Check whether the data equipment on the client side is faulty. If the equipment is faulty, troubleshoot the fault of the data equipment on the client side. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 6: The data equipment on the client side is faulty. 1.
----End
Related Information
None.
3.1.11 LOOP_ALM
Description
Indication of loop operating. The alarm is generated when the optical interface of the board is in the loopback status. Reported from the WDM side or client side: WDM side, client side.
Attribute
Alarm Severity Minor Alarm Type Equipment alarm
Parameters
3-22
Issue 08 (2011-10-30)
3 Alarm Processing
Name
Meaning
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is generated. 0x00 0x01 indicates optical interface loopback of the optical port indicated by parameter 1. Parameter 4 Indicates the loopback type. For example, l 0x01: Inloop. l 0x02: Outloop.

Services are interrupted.
Possible Causes
l l Cause 1: The loopback command is issued during testing or maintenance. Cause 2: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. 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. If the alarm persists, perform a cold reset on the faulty board on the T2000. If the alarm persists, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
Cause 2: The board is faulty. 1. 2.
----End
Related Information
None.
3.1.12 LSR_WILL_DIE
Description
Laser will be out of work. Reported from the WDM side or client side: WDM side, client side.
Issue 08 (2011-10-30)
3-23
3 Alarm Processing
Attribute
Parameters

The laser is seriously aged, and thus the quality of the output optical signals and the received signals is decreased (for example, the optical power is lower or not stable). The impact depends on the aging level of the laser.
Possible Causes
The laser is aged. The service life of the laser would be terminated.
Procedure
Step 1 If the board uses pluggable optical modules, replace the specific pluggable optical module. For details, see Replacing Pluggable Optical Modules of the Parts Replacement. Step 2 If the faulty board dose not supports pluggable optical modules, replace the board. For details, see Replacing a Board of the Supporting Tasks. ----End
Related Information
None.
3-24
Issue 08 (2011-10-30)
3 Alarm Processing
3.1.13 MS_AIS
Description
Multiplex section alarm indication. The alarm is generated when the opposite station transmits the MS_AIS signals or the receive side of the local station is faulty. Reported from the WDM or client side: WDM side, client side. l l WDM side: In this case, the type of the service received on the WDM side is SDH. client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Alarm Severity Major Alarm Type Communication alarm
Parameters

l l If the alarm is reported from the WDM side, the services is interrupted. If the alarm is reported from the client side, the services are faulty.
Possible Causes
l Cause 1 for the alarm generated on the client side: For the OTU board of which the client side supports the SDH services, and the input signals from the client side contain the MS_AIS signal, as shown in the following figure.
Issue 08 (2011-10-30)
3-25
3 Alarm Processing
Detects and reports the MS_AIS alarm
Detects and reports the MS_AIS alarm
The client signals contain the MS_AIS signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
Cause 1 for the alarm generated on the WDM side: The input signals from the client equipment at the opposite station contain MS_AIS signals, which are transmitted to the downstream station. At the same time, the MS_AIS alarm is detected on the WDM side of the OTU at the local station and it is reported to the T2000. See the preceding figure. Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU board of which the client side supports the SDH services, the input signals from the client side contain the MS_AIS signal, as shown in the following figure. 1. l When the MS_AIS alarm is reported from the client side, troubleshoot the fault of the equipment on the client side.
Cause 1 for the alarm generated on the WDM side: The input signals from the client side of the OTU at the opposite station contain MS_AIS signals. 1. Check whether the MS_AIS is generated on the client side of the OTU at the opposite station on the T2000. If yes, troubleshoot the MS_AIS alarm according to the handling method for the alarm generated on the client side of the OTU.
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. If the alarm persists and the MS_AIS is not inserted at the opposite station, the board that reports the alarm is faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.1.14 MS_RDI
Description
Multiplex section remote defect indication alarm. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDM-side
3 Alarm Processing
receive part of the opposite station is faulty (for example, the R_LOS, R_LOF, FEC_LOF or MS_AIS alarm is generated). Reported from the WDM or client side: WDM side, client side l l WDM side: In this case, the type of the service received on the WDM side is SDH. Client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Parameters

l l If the alarm is reported from the WDM side, the services may be interrupted. If the alarm is reported from the client side, the client-side services are faulty.
Possible Causes
l Cause 1 for the alarm generated on the client side: For the OTU board whose client side supports the SDH services, the input signals from the client side contain the MS_RDI signal. As shown in the following figure, the input signals from the client side of the OTU board 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.
Issue 08 (2011-10-30)
3-27
3 Alarm Processing
Detects and reports the MS_RDI alarm
The client signals contain the MS_RDI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
Cause 1 for the alarm generated on the WDM side: The receive part on the WDM side of the opposite station detects the signal failure (for example, the R_LOS, R_LOF, FEC_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, FEC_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, FEC_LOF, MS_AIS alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the MS_RDI alarm
Station B Sends the MS_RDI signal back
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU board of which the client side supports the SDH service, the input signals from the client side contain the MS_RDI signal. 1. l When the MS_RDI alarm is reported from the client side, remove the fault of the equipment connected to the client side of the OTU board first.
Cause 1 for the alarm generate on the WDM side: The receiver on the WDM side of the opposite station detects a signal failure (for example, the R_LOS, R_LOF, FEC_LOF or the MS_AIS alarm is generated).
3-28
3 Alarm Processing
1.
Query the alarm of the board in the opposition station by using the T2000. If the R_LOS, R_LOF, FEC_LOF or MS_AIS alarm exists, see the handling procedure of the R_LOS, R_LOF, FEC_LOF or MS_AIS alarm for troubleshooting.
Cause 2 for the 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 or not according to the actual situation (whether affects the services). For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.1.15 MUT_LOS
Description
Loss of multiplexed signals alarm. The alarm is generated when the input multiplexed signals of the board is lost. Reported from the WDM side or client side: NA
Attribute
Parameters

The services that travel through the optical interface that generates this alarm are interrupted.
3 Alarm Processing
Possible Causes
l l l Cause 1: Certain optical interfaces on the board that reports the alarm are not connected to a fibers or the fibers are damaged. Cause 2: The attenuation of signals in line transmission is excessively high. Cause 3: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: Certain optical interfaces on the board that reports the alarm are not connected to a fibers or the fibers are damaged. 1. Check whether there are certain optical interfaces that reports the alarm are not connected to fibers or the fibers are damaged. If yes, connect the input optical signals to the specific optical interface, or replace the damaged fiber. 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, see Technical Specifications of the Product Description . If the receive optical power is excessively low, see the handling procedure of the SUM_INPWR_LOW alarm for troubleshooting. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 2: The attenuation of signals in line transmission is excessively high. 1.
2. l
----End
Related Information
Related Cases: l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm After Auto Optical Power Adjustment Is Started During the Creation of Single-Station Optical CrossConnections MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
3.1.16 NEBD_XC_DIF
Description
Crossing data of NE and board different. For the board supporting service cross-connection, the alarm is generated when the cross-connection data stored on the SCC is not consistent with that stored on the board.
3-30
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Alarm Severity Major Alarm Type 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. Name Parameter 1 Meaning The slot ID of the board where the cross-connection data is not consistent with that on the SCC. For example, 0x01 stands for the slot 1. The type of the service with inconsistent data. For example, 0x03 stands for the inconsistent space division cross-connect services. Parameter 3 The clip number. For example, 0x01-0x10 stand for the clip numbers; 0xff stands for the unclassified clip by numbering. Parameters 4 and 5 The two parameters are reserved. The value is always 0xff 0xff.
Parameter 2

Services are interrupted during service grooming or perform a warm reset on of the board.
Possible Causes
l l Cause 1: The cross-connection data of the board is incorrect. Cause 2: The cross-connection data stored on the board is different from that in the SCC board.
Procedure
l l Query the alarm on the T2000. Record the slot ID of the board that reports the alarm. Cause 1: The cross-connection data of the board is incorrect. 1. l Re-configure the cross-connection data on the T2000.For details, see the Configuration Guide.
Cause 2: The cross-connection data stored on the board is different from that in the SCC board.
Issue 08 (2011-10-30)
3 Alarm Processing
1. 2. ----End
If the alarm persists, perform a warm reset on the board related to service crossconnections on the T2000. If the alarm persists, perform a warm reset on the SCC board.
Related Information
None.
3.1.17 OA_LOW_GAIN
Description
Optical amplifier signal gain low. The alarm is generated when the actual gain of the optical amplifier board is lower than the standard gain 3 dB. Reported from the WDM side or client 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. Name Parameter 1 Meaning indicates the optical interface where this alarm is generated. Since the optical amplifiers are different, the value of the parameter varies. The value is 0x02 or 0x04.
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. The value is always 0x00 0x01.

The alarm caused by different factors has different influences on the system: l l If the alarm is generated because the input optical power is excessively high, the redundancy of the system decreases, which influences the succeeding capacity expansion. If the alarm is caused by other factors (for the OAU board, including the excessive insertion loss caused by the TDC and RDC), the input optical power of the downstream signals and
3-32
3 Alarm Processing
the redundancy of the system decrease. The services would have bit errors or even be interrupted.
Possible Causes
l l l Cause 1: The input optical power of the board is excessively high. Cause 2: For the OAU board, the alarm might be generated because the insertion loss between the TDC and RDC optical interfaces is excessively high. Cause 3: The board that reports the alarm is faulty.
Procedure
l Cause 1: The input optical power of the board is excessively high. 1. Check whether the receive optical power of the board is within the normal range on the T2000. For the optical power specification of the specific board, see Technical Specifications of the Product Description . 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. If no optical attenuator is attached to the input optical interface, add a VOA to ensure that the input optical power meet the specification requirement.
2.
3. l
Cause 2: The insertion loss between the TDC and RDC optical interfaces is excessively high. (in the case of the OAU board) 1. On the T2000 query the optical power at the TDC and RDC optical interfaces on the OAU, and then calculate the insertion loss between the TDC and RDC optical interfaces.
NOTE
Insertion loss = Optical power at the TDC optical interface - Optical power at the RDC optical interface. On the T2000, 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 the insertion loss specification, see For the optical power specification of the specific board, see Technical Specifications of the Product Description . of the Product Description. If the alarm persists, replace the DCM module between the TDC and RDC optical interfaces. If the alarm persists, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
3. l
----End
Related Information
None.
Issue 08 (2011-10-30)
3-33
3 Alarm Processing
3.1.18 ODU_AIS
Description
ODU (optical channel data unit) alarm indication signal. The alarm occurs when the OTU detects that all signals are "1" and the STAT information is "111" at the entire ODU layer of the input signals. The generation of the alarm indicates that the signals at the ODU layer are faulty. Reported from the WDM or client side: WDM side, client side
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 Parameter 1 Meaning Indicates the optical interface where the alarm occurs. For example, 0x01 indicates optical interface 1.
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm occurs. For example, 0x00 0x01 indicates channel 1 of the optical interface indicated by parameter 1.

Carried services at this board are interrupted.
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU board of which the client side supports the OTN services, the input signals from the client side contain the ODU_AIS signal; as shown in the following figure. The client-side input signals of the OTU in station A (local station) contains ODU_AIS signals. The OTU in station A reports the ODU_AIS alarm on the client side after detecting the ODU_AIS signals. At the same time the OTU transparently transmits the ODU_AIS signals to the station B (opposite station).
3-34
Issue 08 (2011-10-30)
3 Alarm Processing
Detects and reports the ODU_AIS alarm
The client signals contain the ODU_AIS signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
Cause 1 for the alarm generated on the WDM side: The ODU_AIS signals are manually inserted to the OTU at the opposite station, as shown in the following figure: The ODU_AIS signals are manually inserted on the WDM side of the OTU in the station A (opposite station). The WDM side of the OTU in the station B (local station) reports the ODU_AIS alarm after detecting the ODU_AIS signals.
Manually insert the ODU_AIS signal Detects and reports the ODU_AIS alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A
Station B
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The input signals from the client side contain the ODU_AIS signal. 1. l If the client side reports the ODU_AIS alarm, clear the fault on the client equipment. For details, refer to the related manuals of the client equipment.
Cause 1 for the alarm generated on the WDM side: The ODU_AIS signals are manually inserted to the OTU at the opposite station. 1. If the alarm persists, on the T2000 query whether the ODU_AIS signals are manually inserted to the OTU at the opposite station. If yes, disable the ODU_AIS signals manually inserted.
----End
Issue 08 (2011-10-30)
3-35
3 Alarm Processing
Related Information
None
3.1.19 OMS_FDI
Description
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
Parameters

If the logical fiber connection is established improperly, there is no impact on services. Otherwise there might be impact on the services.
Possible Causes
l l Cause 1: The logical fiber connection is not consistent with the physical fiber connection. Cause 2: In the upstream path, fiber cut occurs, the optical power is excessively low, or dispersion degrades. Thus, the loss of signal alarm is detected in the downstream path, and the OMS_FDI is inserted to the downstream path.
3-36
3 Alarm Processing
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The logical fiber connection is not consistent with the physical fiber connection. 1. Check whether the logical fiber connection configured for the optical interface where the alarm is generated is consistent with its physical fiber connection. If not, modify the configuration of the logical fiber connection so that the logical fiber connection is consistent with the physical fiber connection.
Cause 2: In the upstream path, fiber cut occurs, the optical power is excessively low, or dispersion degrades. Thus, the loss of signal alarm is detected in the downstream path, and the OMS_FDI is inserted to the downstream path. 1. Check whether there are OTS_LOS or OTS_TIM at the opposite station and all upstream stations. If yes, troubleshoot the OTS_LOS or OTS_TIM alarm according to the corresponding alarm handling procedure.
----End
Related Information
None.
3.1.20 OPS_PS_INDI
Description
Indication of optical channel protection switching. The alarm is generated when the optical channel protection switching of the services succeeds.
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.
Issue 08 (2011-10-30)
3-37
3 Alarm Processing
Name Parameter 1
Meaning The protection group type. For example, 0x01 stands for the 1:N optical channel protection. 0x02 stands for the clock protection. 0x03 stands for the 1+1 optical channel protection. 0x04 stands for the WXCP protection.
Parameters 2 and 3 Indicates the ID of the protection group in which the alarm is generated. For example, 0x00 0x01 denotes protection group 1. Parameter 4 The unit ID of the protection group. For example, 0x00 stands for the protection unit. 0x01 stands for the working unit.

The protection switching is performed to the system. The services work in the protection channel and are not interrupted. You need to locate the cause for protection switching and clear the related fault. Otherwise the services might be interrupted.
Possible Causes
l l Cause 1: The external switching command (such as forced switching or manual switching) is performed and the switching is successful. Cause 2: The services in the working channel are abnormal. The services are automatically switched from the working channel to the protection channel.
Procedure
l l Query the alarm on the T2000 and record the type and ID of the protection group where the alarm is generated. Cause 1: The external switching command (such as forced switching or manual switching) is performed and the switching is successful. 1. On the T2000 query the switching status of the protection group. If the switching status is in the forced switching or manual switching status, check whether the external switching is the need for normal working.If the external switching is the need for normal working, there is no need to handle the alarm. If the external switching is not the need for normal working, clear the external switching by issuing the clear switching command.
2. l
Cause 2: The services in the working channel are abnormal. The services are automatically switched from the working channel to the protection channel. 1. On the T2000 query the status of the working channel.If the working channel is in the switching state, check whether the alarms with higher priority exist on the related
3-38
3 Alarm Processing
boards at the local station such asR_LOS, R_LOF or B1_EXC. If yes, handle the alarms that trigger the protection switching by priority. 2. 3. If the alarm persists, you need to solve the BER-related problem. For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting. If the alarm persists, you need to solve the fiber-related problem. For how to troubleshoot the specific fault, see Troubleshooting Optical Power Anomalies of the Troubleshooting.
----End
Related Information
For the principles of protection and the trigger conditions of the alarm, see the Feature Description.
3.1.21 OSC_LOS
Description
Loss of signal on receiving line. This alarm is generated when the receive side receives no signals. Reported from the WDM side or client side: NA
Attribute
Parameters

There is fiber break in the receive direction and will cause carried service break of this port.
3 Alarm Processing
Possible Causes
l l l l Cause 1: A certain optical interface on the board that reports the alarm is not connected to a fiber. Cause 2: The laser of the board at the opposite station is shut down. Cause 3: The attenuation of the transmission line is excessively high, and a fiber break occurs on the transmission line. Cause 4: The transmit side of the opposite station is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the optical interface and channel where the alarm is generated. Cause 1: A certain optical interface on the board that reports the alarm is not connected to a fiber. 1. l Check whether the fiber jumper is connected to the optical interface of the board at the local station. If not, connect the fiber jumper. Use the T2000 to check whether the laser of the specific board at the opposite station is open. If not, open the laser of the board.
Cause 2: The laser of the board at the opposite station is shut down. 1.
Cause 3: The attenuation of the transmission line is excessively high, and a fiber break occurs on the transmission line. 1. On the T2000 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, see Technical Specifications of the Product Description . If the receive optical power is not within the normal range, troubleshoot the alarm according to the handling procedure for the IN_PWR_LOW or IN_PWR_HIGH. If the receive optical power is normal, check the fiber connector. If the fiber connector is dirty or damaged, clean or replace the fiber connector. If the alarm persists, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
2. 3. l
Cause 4: The transmit side of the opposite station is faulty. 1.
----End
Related Information
None.
3.1.22 OTU_LOF
Description
Loss of OTU frame. The alarm occurs when the FAS frames in the OTU layer of the optical signals are out of synchronization for more than 3 ms. Reported from the WDM side or client side: WDM side, client side
3 Alarm Processing
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 Parameter 1 Meaning Indicates the optical interface where the alarm occurs. For example, 0x01 indicates optical interface 1.
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm occurs. For example, 0x00 0x01 indicates channel 1 of the optical interface indicated by parameter 1.

Services carried on this board are interrupted.
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU board of which the client side supports the OTN services, the input signals from the client side contain the OTU_LOF signal, as shown in the following figure. The input signals on the client side of the OTU at station A (local station) contain the OTU_LOF signals. The OTU at station A reports the OTU_LOF alarm on the client side after detecting the OTU_LOF signals.
Detects and reports the OTU_LOF alarm
The client signals contain the OTU_LOF signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
Cause 2 for the alarm generated on the client side: The received optical power or OSNR of the board is abnormal, or the OTU board at the local station is faulty.
Issue 08 (2011-10-30)
3 Alarm Processing
Cause 3 for the alarm generated on the client side: In the case of the OTU board of which the client side supports the OTN services, the service type set on the client side is inconsistent with the actual service type. Cause 1 for the alarm generated on the WDM side: The frame structure of the transmitted signals of the OTU at the opposite station mismatches frame structure of the OTU at the local station, or there is no frame structure in the signals transmitted by the OTU at the opposite station. Cause 2 for the alarm generated on the WDM side: The received optical power or OSNR of the board is abnormal, or the OTU board at the local station is faulty. Cause 3 for the alarm generated on the WDM side: The OTU board at the opposite station is faulty.
l l
Procedure
l l Query the alarm on the T2000 and record the IDs of the optical interface and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The input signals from the client side contain the OTU_LOF signals. 1. l If the alarm is generated on the client side, troubleshoot the fault on the client equipment. For details, refer to the related manuals of the client equipment.
Cause 2 for the alarm generated on the client side: The received optical power or OSNR of the board is abnormal, or the OTU board at the local station is faulty. 1. On the T2000 query the input optical power of the OTU at the local station to check whether it is within the normal range. For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the optical power is abnormal, troubleshoot the alarm according to the handling procedure for the IN_PWR_HIGH or IN_PWR_LOW alarm. If the OTU_LOF alarm is generated transiently, it may be caused by the burst bit errors in the transmission line. For the alarm handling, see Troubleshooting Transient Service Interruption of the Troubleshooting. If the alarm persists, you need to solve the BER-related problem. For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting. If the alarm persists, on the T2000 perform a cold reset on the board that reports the alarm. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
2.
3. 4. 5. l
Cause 3 for the alarm generated on the client side: the service type set on the client side is inconsistent with the actual service type. 1. Check whether the service type set on the client side of the OTU is consistent with the service type of the client equipment. If not, change the service type of the corresponding optical interface on the board properly. For details, refer to "Querying and Setting the Service Type on the Client Side on the Board" of the Supporting Tasks.
Cause 1 for the alarm generated on the WDM side: The frame structure of the transmitted signals of the OTU at the opposite station mismatches the frame structure of the OTU at the local station, or there is no frame structure in the signals transmitted by the OTU at the opposite station. 1. On the T2000 query the type of the OTU at the opposite station to check whether the board can be connected to the OTU at the local station. Use the OTN test instrument
3-42
3 Alarm Processing
to receive the signals from the WDM side of the opposite OTU. Then, check the frame structure of the received signals to see whether the frame structure matches the frame structure at the local OTU or whether the signals are framed. If not, replace the OTU at the opposite station. l Cause 2 for the alarm generated on the WDM side: The received optical power or OSNR of the board is abnormal, or the OTU board at the local station is faulty. 1. On the T2000 query the input optical power of the OTU at the local station to check whether it is within the normal range. For the optical power specifications of the specific board, refer to the Product Description.If the optical power is abnormal, troubleshoot the fault according to the handling procedure for the IN_PWR_HIGH or IN_PWR_LOW alarm. If the OTU_LOF alarm is generated transiently, it may be caused by the burst bit errors in the transmission line. For the alarm handling, see Troubleshooting Transient Service Interruption of the Troubleshooting. If the alarm persists, you need to solve the BER-related problem. For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting. If the alarm persists, on the T2000 perform a cold reset on the board that reports the alarm. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
2.
3. 4. 5. l
Cause 3 for the alarm generated on the WDM side: The OTU board at the opposite station is faulty. 1. 2. If the alarm persists, perform a cold reset on the faulty board at the opposite station. If the alarm persists, the board at the opposite station may be faulty. Replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
Related Cases: l l l l l MC-A1 The TF Alarm on the OTU at the Upstream Station Results in the OTU_LOF Alarm on the OTU at the Downstream Station MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with the SSE1TMR MC-A28 When Accessing 10GE LAN Services, the LSX Board Reports the OTUk_LOF Alarm Because of the Inconsistency in the Settings of WDM-side Rate. MC-A56 LWF Board Reports OTU_LOF Alarm MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After Correction
3.1.23 OUT_PWR_HIGH
Description
Output optical power too high alarm. This alarm is generated when the laser output optical power crosses the upper threshold. Reported from the WDM or client side: WDM side, client side.
3 Alarm Processing
Attribute
Alarm Severity Major Alarm Type Equipment alarm
Parameters

l When the output optical power is excessively high, the input optical power at the receive end will be very high if no proper optical attenuator is used at the receive end. As a result, the module at the receive end may be damaged. If the alarm is caused by the faulty module of the laser or the faulty board, the board is working abnormally, which will affect the transmitting and receiving of the services.
Possible Causes
l The optical module of laser is faulty or the board is faulty.
Procedure
l Query the alarm on the T2000 and record the IDs of the optical interface and channel where the alarm is generated. 1. If the input optical power is within the normal range, the optical module of the laser of the board is faulty. If the board uses pluggable optical modules, replace the specific pluggable optical module. For details, see Replacing Pluggable Optical Modules of the Parts Replacement. If the board does not supports pluggable optical modules, replace the board. For details, see Replacing a Board of the Supporting Tasks.
2. ----End
Related Information
None.
3 Alarm Processing
3.1.24 PM_BDI
Description
ODU PM section backward defect indication. The alarm is transferred in the upstream direction of the services, indicating the detected signal failure. Reported from the WDM side or client side: WDM side, client side
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 Parameter 1 Description Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

Services carried on this board are interrupted.
Possible Causes
l Cause 2 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side contain the PM_BDI signal, as shown in the following figure. The input signals on the client side of the OTU at station A contain the PM_BDI signals. The OTU at station A reports the PM_BDI alarm on the client side after detecting the PM_BDI signals and transparently sends the PM_BDI signals to station B (opposite station) at the same time. The WDM side of the OTU at station B reports the PM_BDI alarm after detecting the PM_BDI signals.
Issue 08 (2011-10-30)
3-45
3 Alarm Processing
Detects and reports the PM_BDI alarm
Detects and reports the PM_BDI alarm
The client signals contain the PM_BDI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
l l
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The ODU_AIS/ODU_OCI/ODU_LCK alarm is generated when the WDM side of the OTU at the opposite station receives the signals from the local station, as shown in the following figure. The WDM side of the OTU at station B (opposite station) inserts the PM_BDI signals back to station A (local station) after detecting the ODU_AIS/ODU_OCI/ODU_LCK alarm. The WDM side of the OTU at station A reports the PM_BDI alarm after detecting the PM_BDI signals.
Detects and reports the ODU_AIS, ODU_OCI or ODU_LCK alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the PM_BDI alarm
Station B Insert the PM_BDI signal back
l l
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the PM_BDI signals back to the local station improperly. As shown in the following figure: The WDM side of the OTU in the station B (opposite station) inserts the PM_BDI signals back to the station A (local station) by mistake. The WDM side of the OTU in the station A reports the PM_BDI alarm after detecting the PM_BDI signals.
3-46
Issue 08 (2011-10-30)
3 Alarm Processing
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the PM_BDI alarm
Station B Insert the PM_BDI signal by mistake
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side contain the PM_BDI signals. 1. If the client side reports the PM_BDI alarm, check whether the client-side equipment connected to the OTU is faulty according to the related manuals. If yes, troubleshoot the fault generated on the client-side equipment by referring to the related manuals. If the alarm persists, perform a cold reset on the faulty board at the local station on the T2000. If the alarm persists, replace the faulty board.For details, see Replacing a Board of the Supporting Tasks. If the alarm persists, perform a cold reset on the faulty board at the local station on the T2000. If the alarm persists, replace the faulty board.
2. 3. l
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. 1. 2.
Cause 1 for the alarm generated on the WDM side: The ODU_AIS/ODU_OCI/ODU_LCK alarm is generated when the WDM side of the OTU at the opposite station receives the signals from the local station. 1. If the WDM side reports the PM_BDI alarm, check whether the ODU_AIS, ODU_OCI or ODU_LCK alarm is generated when the OTU in the opposite station receives the signals at the local station. If yes, handle the alarm by referring to the corresponding handling procedure.
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. 2. If the alarm persists, perform a cold reset on the faulty board at the local station on the T2000. If the alarm persists, the OTU at the local station may be faulty. Replace the faulty board.
Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the PM_BDI signals back to the local station improperly. 1. If the alarm persists, perform a cold reset on the faulty board at the opposite station on the T2000.
Issue 08 (2011-10-30)
3 Alarm Processing
2. ----End
If the alarm persists, the OTU at the opposite station may be faulty. Replace the faulty board.
Related Information
None.
3.1.25 PM_BEI
Description
ODU PM section backward error indication. If the board detects that the input signals contain the PM-BIP8 bit errors, it inserts the PM_BEI alarm back to the upstream board. The alarm occurs when the upstream station detects that the BEI flag in the OCH-OH of the PM section of the received signals is true. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

The bit errors occur to the service signals, which influences the system quality.
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side contain the PM_BEI signals, as shown in the following figure.
3-48
3 Alarm Processing
The input signals on the client side of the OTU in the station A contain the PM_BEI signals. The OTU in the station A reports the PM_BEI alarm on the client side after detecting the PM_BEI signals and transparently sends the PM_BEI signals to the station B (opposite station) at the same time. The WDM side of the OTU in the station B reports the PM_BEI alarm after detecting the PM_BEI signals.
Detects and reports the PM_BEI alarm Detects and reports the PM_BEI alarm
The client signals contain the PM_BEI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
l l
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The PM_BIP8 bit errors occur when the OTU in the opposite station receives the signals in the local station, as shown in the following figure. The WDM side of the OTU in the station B (opposite station) inserts the PM_BEI signals back to the station A (local station) after detecting the PM-BIP8 bit errors. The WDM side of the OTU in the station A reports the PM_BEI alarm after detecting the PM_BEI signals.
Detects the PM-BIP8 bit errors
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the PM_BEI alarm
Station B Insert the PM_BEI signal back
l l
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the PM_BEI signals back to the local station improperly. As shown in the following figure, the WDM side of the OTU in the station B (opposite station) inserts the PM_BEI signals back to the station A (local station) by mistake. The WDM side of the OTU in the station A reports the PM_BEI alarm after detecting the PM_BEI signals.
Issue 08 (2011-10-30)
3-49
3 Alarm Processing
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the PM_BEI alarm
Station B Insert the PM_BEI signal by mistake
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side contain the PM_BEI signals. 1. If the client side reports the PM_BEI alarm, check whether the client-side equipment connected to the OTU is faulty according to the related manuals. If yes, clear the fault of the client-side equipment by referring to the related manuals. If the alarm persists, perform a cold reset on the faulty board in the local station. If the alarm persists, replace the board that reports the alarm. For details, see Replacing a Board of the Supporting Tasks. If the alarm persists, perform a cold reset on the faulty board in the local station through the T2000. If the alarm persists, the OTU in the local station may be faulty. Replace the faulty board.
2. 3. l
Cause 1 for the alarm generated on the WDM side: The PM_BIP8 bit errors occur when the OTU in the opposite station receives the signals in the local station. 1. If the WDM side reports the PM_BEI alarm, query the current performance of the corresponding optical interface to check whether the PM_BIP8 bit error occurs when the OTU in the upstream station receives the signals at the local station. If yes, handle the alarm by referring to the handling procedure of the PM_BIP8_OVER alarm.
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. 2. If the alarm persists, perform a cold reset on the faulty board in the local station through the T2000. If the alarm persists, the OTU in the local station may be faulty. Replace the faulty board.
Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the PM_BEI signals back to the local station improperly. 1. If the alarm persists, perform a cold reset on the faulty board in the opposite station through the T2000.
3-50
Issue 08 (2011-10-30)
3 Alarm Processing
2. ----End
If the alarm persists, the OTU in the opposite station may be faulty. Replace the faulty board.
Related Information
None.
3.1.26 PM_BIP8_OVER
Description
ODU layer, PM section BIP (Bit Interleaved Parity) exceed the upper threshold. The alarm occurs when the number of BIP8 bit errors of the PM section in the optical channel data unit layer crosses the upper threshold. Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Major Alarm Type Service alarm
Parameters

The bit errors are generated in the service signals of the system, which influences the system quality.
Issue 08 (2011-10-30)
3-51
3 Alarm Processing
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side has a great amount of BIP8 bit errors of the PM section. Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The input optical power is extremely high or extremely low. Cause 2 for the alarm generated on the WDM side: The system performance declines. For example, the optical signal to noise ratio (OSNR) is extremely low, or dispersion or nonlinearity occurs. Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
l l l
l l
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side has a great amount of BIP8 bit errors of the PM section. 1. In the case of the OTU board of which the client side supports the OTN services, query the current performance of the corresponding optical interface on the T2000 to check whether the input signals on the client side has a great amount of BIP8 bit errors of the PM section. If yes, clear the fault on the client-side equipment. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
Cause 1 for the alarm generated on the WDM side: The input optical power is extremely high or extremely low. 1. Check whether the input optical power of the interface is within the normal range by using the T2000, For the optical power specification of the specific board, see Technical Specifications of the Product Description .. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.
Cause 2 for the alarm generated on the WDM side: The system performance declines. For example, the optical signal to noise ratio (OSNR) is extremely low, or dispersion or nonlinearity occurs. 1. If the alarm persists, For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting.
Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. 1. If the alarm persists, the board in the opposite station may be faulty. Replace the faulty board.
Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
3-52
3 Alarm Processing
1. ----End
If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
Related Information
None.
3.1.27 PORT_MODULE_OFFLINE
Description
Port module offline. The alarm is generated when the board detects that the optical module is offline. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

Absence of the optical module would lead to the interruption of services borne by the corresponding optical interface.
Possible Causes
l l
Issue 08 (2011-10-30)
Cause 1: The optical module does not exist or is not correctly inserted in the slot. Cause 2: The optical module or the board is faulty.
3 Alarm Processing
Procedure
l l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The optical module does not exist or is not correctly inserted in the slot. 1. 1. Install the optical module properly. If the alarm persists, If the board uses pluggable optical modules, replace the specific pluggable optical module. For details, see Replacing Pluggable Optical Modules of the Parts Replacement. If the optical module is not pluggable, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks. Cause 2: The optical module or the board is faulty.
2. ----End
Related Information
None.
3.1.28 POWERALM
Description
Power status alarm. That is, the alarm indicates the alarm status of the eight tributary power supplies on the cabinet. The alarm occurs when a power-off is detected in any one of the tributary power supplies.
Attribute
Alarm Severity Critical Alarm Type Environment alarm
Parameters
3-54
Issue 08 (2011-10-30)
3 Alarm Processing
Parameter Parameter 1
Description Indicates the number of the tributary power supply. For example: l 0x01: Indicates the subrack power supply 1 of the PDU1. l 0x02: Indicates the subrack power supply 2 of the PDU1. l 0x03: Indicates the subrack power supply 3 of the PDU1. l 0x04: Indicates the auxiliary power supply of the PDU1. l 0x05: Indicates the subrack power supply 1 of the PDU2. l 0x06: Indicates the subrack power supply 2 of the PDU2. l 0x07: Indicates the subrack power supply 3 of the PDU2. l 0x08: Indicates the auxiliary power supply of the PDU2.

The reliability of system power supplying decreases.
Possible Causes
l l l Cause 1: There is a power-off in a tributary power supply or the input power of the equipment. Cause 2: The PDU is faulty. Cause 3: The PMU is faulty.
Procedure
l Cause 1: There is a power-off in a tributary power supply or the input power of the equipment. 1. 2. Check whether the other three tributary power supplies that are located on the same PDU report the POWERALAM alarm or not. If yes, the PDU is powered off. Check whether the dual power supplies are not accessed on purpose because of a certain reason or not. If yes, suppress the POWERALM alarms in the four tributary power supplies that correspond to the power supply. (When the power supply is required in the future, set the status of the alarm to Not Suppressed.) Otherwise, ensure that the PDU is powered on normally. Check whether the alarm is raised because the tributary power supply switch that corresponds to the empty subrack is turned off or not. If yes, suppress the POWERALM alarm in the unused tributary power supply. (When a subrack is added in the future, set the status of the alarm to Not Suppressed.) Check whether the other three tributary power supplies that are located on the same PDU report the POWERALAM alarm or not. If yes, the PDU is powered off. Replace the PDU. For details, see Replacing the PDU of the Parts Replacement. If the alarm persists, replace the faulty PMU. For details, see Replacing the PMU of the Parts Replacement.
3.
Cause 2: The PDU is faulty. 1.
Cause 3: The PMU is faulty. 1.
----End
3 Alarm Processing
Related Information
None.
3.1.29 POWER_DIFF_DEFECT
Description
Power difference between optical monitoring active and standby channels. The alarm is generated when the power difference between the active and standby optical monitoring signals exceeds the degraded threshold. Reported from the WDM side or client 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 Parameter 1 Description The optical power of this optical interface is lower than that of another optical interface and the difference exceeds the threshold.
Parameters 2 and 3 The value is always 0x00 0x01.

None.
Possible Causes
l l Cause 1: The power difference between the active and standby optical signals transmitted by the board at the opposite station is rather large. Cause 2: The optical power attenuation of the optical signals in transmission is very large or the optical attenuator that enables very large attenuation is added to the board at the opposite station. As a result, the power difference of the optical signals at the receive end is rather large. Cause 3: The board that reports the alarm is faulty.
l
3-56
3 Alarm Processing
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The power difference between the active and standby optical signals transmitted by the board in the opposite station is rather large. 1. l If the alarm persists, adjust the optical power of the active and standby channels at the transmit end to obtain a difference within 3 dB.
Cause 2: The optical power attenuation of the optical signals in transmission is very large or the optical attenuator that enables very large attenuation is added to the board at the opposite station. 1. Adjust the optical power of the active and standby channels at the receive end until the alarm clears. If the alarm persists, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.1.30 POWER_FAIL
Description
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. Reported from the WDM side or client side: NA
Attribute
Issue 08 (2011-10-30)
3-57
3 Alarm Processing
Parameters
Name Parameter 1 Meaning Indicates the power supply number. For example, l 0x01 denotes 3.3 V. l 0x02 denotes 5.0 V. l 0x03 denotes -5.2 V. l 0x05 denotes the battery on the SCC has no power.
NOTE For E8LWF, E8LWFS, E8LBF, E8LBFS, E8ELOG, E8ELOGS, E8ETMX, E8ETMXS, E8TMR, E8TMRS, l 0x03 denotes 1.2 V. l 0x04 denotes 1.5 V. l 0x05 denotes 1.8 V. l 0x06 denotes 2.5 V. l 0x07 denotes 3.3 V. l 0x08 denotes -5.2 V. l 0x09 denotes 5.0 V.
Parameter 2
Indicates the faulty power supply. For example, l 0x01 indicates that the active power supply fails. l 0x02 indicates that the standby power supply fails.
Parameter 3
Indicates the power supply status. For example, l 0x01 indicates overvoltage of the power supply. l 0x02 indicates undervoltage of the power supply.
Parameters 4 and 5 The value is 0xff of every parameter.

l l If this alarm is reported by the SCC board, the system time is lost if the system is powered off. If this alarm is reported by the PMU boards, it indicates that the the input voltage of the power supply on the subrack is abnormal. In this case, protection switching is performed between the active power supply and standby power supply but there is no impact on the services. If this alarm is reported by other boards, If the active power supply fails, and the standby power supply is normal, which can cause the switching of the power supply, there is no impact on the services. If the active power supply fails, and the standby power supply fails too, the services may be interrupted.
3-58
Issue 08 (2011-10-30)
3 Alarm Processing
Possible Causes
l l l Cause 1: If this alarm is reported by the SCC board, it indicates the battery on the SCC has no charge. Cause 2: If this alarm is reported by other boards, it indicates the power supply of the board is faulty or aged. Cause 3: If this alarm is reported by the PMU board, it indicates that the input voltage of the power supply on the subrack is abnormal, prompting that the power supply module is faulty.
Procedure
l Cause 1 and cause 2: If this alarm is reported by the SCC board, it indicates the battery on the SCC has no charge; If this alarm is reported by other boards, it indicates the power supply of the board is faulty or aged. 1. l Replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
Cause 3: If this alarm is reported by the PMU board, it indicates that the input voltage of the power supply on the subrack is abnormal, prompting that the power supply module is faulty. 1. If the alarm is reported by the PMU board, replace the faulty power supply module. For details, see the Parts Replacement.
----End
Related Information
Related Cases: l MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER Alarms
3.1.31 PS
Description
PS (protection switching) indication. The alarm occurs when the protection switching of the services succeeds. When the alarm is generated, the services are working on the protection channel.
Attribute
Parameters
3 Alarm Processing
Parameter Parameters 1
Description Indicates the ID of the protection group in which the alarm is generated. For example, 0x01 indicates protection group 1, 0x02 indicates protection group 2, and 0xff indicates an invalid value.
Parameters 2 and 3 Indicates the optical port where the alarm is generated. It consists of two bytes. For example, 0x00 0x01 indicates optical port 1, 0x00 0x02 indicates optical port 2, 0x00 0x03 indicates optical port 3, 0x00 0x04 indicates optical port 4, and 0x00 0xff indicates the invalid value. Parameters 4 Parameters 5 This parameter is reserved. It consists of one byte and the value is 0xff. This parameter consists of one byte and indicates whether the definition of an optical port is valid. If the value is 0xA5, the definition of the optical port is valid; if the value is 0xff, the definition of the optical port is invalid.

The protection switching is performed to the system. The services works on the protection channel and are not interrupted. You need to locate the cause for protection switching and clear the related fault. Otherwise the services might be interrupted.
Possible Causes
l l Cause 1: The external switching command (forced switching or manual switching) is performed and the switching succeeds. Cause 2: The services in the working channel are abnormal. The services switches from the working channel to the protection channel.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The external switching command (forced switching or manual switching) is performed and the switching succeeds. 1. On the T2000 query the switching status of the protection group. If the switching status is in the forced switching or manual switching status, check whether the external switching is the need for normal working. If the external switching is the need for normal working, there is no need to handle the alarm. If the external switching is not the need for normal working, clear the external switching by issuing the clear switching command.
2. 3. l
Cause 2: The services in the working channel are abnormal. The services switches from the working channel to the protection channel. 1. If the alarm persists, query the status of the working channel on the T2000. If the working channel is in the switching status, check whether related boards at the local station have alarms that can trigger a protection switching, such as R_LOS,
3-60
3 Alarm Processing
R_LOF or B1_EXC. If yes, handle the alarms that trigger the protection switching by priority. 2. 3. 4. If the alarm persists, clear the bit errors. For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting. If the alarm persists, clear the fiber faulty. For how to troubleshoot the specific fault, see Troubleshooting Optical Power Anomalies of the Troubleshooting. If there is no other alarm as confirmed, perform a manual switching to switch the services from the protection channel to the working channel. After the manual switching is performed, the PS alarm is cleared.
----End
Related Information
3.1.32 PUMP_COOL_EXC
Description
Cool current of pump laser over threshold. This alarm is generated when the laser cooling current crosses the upper threshold. Reported from the WDM side or client side: NA
Attribute
Parameters
Parameters 2 and 3 Indicate the pump laser where the alarm is generated. For example, 0x00 0x01 indicates pump laser 1.
Issue 08 (2011-10-30)
3-61
3 Alarm Processing
Description Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

When this alarm is reported, the optical components sharply age and the performance of output signals degrades.
Possible Causes
l l l Cause 1: The ambient temperature is too high or low. Cause 2: The pump laser temperature is too high or low. Cause 3: The board that reports the alarm is faulty.
Procedure
l Cause 1: The ambient temperature is too high or low. 1. Check whether the ambient temperature is normal. If the ambient temperature is excessively high or very low, adjust the temperature to ensure that the temperature is within the normal range.
Cause 2 and cause 3: The pump laser temperature is too high or low; the board that reports the alarm is faulty. 1. If the alarm persists, replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.1.33 R_DATA_LOST
Description
Client-side receiving data lost. The board regularly checks the Ethernet performance event "Good Octets Received" and compares the number with the number of last time. The alarm occurs when the two numbers are the same, which indicating that the board does not receive any data. Reported from the WDM side or client side: client side
Attribute
Alarm Severity Minor
3-62
Alarm Type Communication alarm
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters

The connection status of the Ethernet port is normal; however, the received optical signals do not have data packet.
Possible Causes
l l Cause 1: The data equipment on the client side stops to send data. Cause 2: The Ethernet port of the board is faulty, which cannot receive data.
Procedure
l l Query the alarm on the T2000 and record the IDs of the Ethernet port and channel where the alarm is generated. Cause 1: The data equipment on the client side stops sending data. 1. Check whether the data equipment on the client side (including test meters) stops sending data. If yes, clear the fault on the data equipment on the client side (including test meters) to make it send data again. Confirm that the connection status of the Ethernet port is normal and no other alarm exists on the board. If other alarms exist, clear other alarms first. If the alarm persists, the board might be faulty. Replace the faulty board in the local station, For details, see Replacing a Board of the Supporting Tasks.
Cause 2: The Ethernet port of the board is faulty, which cannot receive data. 1. 2.
----End
Related Information
The alarm is a warning alarm used as an auxiliary warning for fault judgement. Generally, the alarm occurs when the test meter or client-side data equipment stops to send data packet. The possibility that the alarm is generated due to the faulty board is slim.
3 Alarm Processing
3.1.34 R_LOF
Description
Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3ms. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

l l The board fails in locating the data frame of the received SDH signals; the client services fail. The board detects this alarm, boards supporting protection switching perform protection switching.
Possible Causes
l l l l Cause 1 for the alarm generated on the client side: The input signals from the client side contain the R_LOF signal. Cause 2 for the alarm generated on the client side: The service type of the client equipment mismatches the service type of the interconnected OTU. Cause 3 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The receive optical power or the OSNR of the local board is abnormal.
3-64
3 Alarm Processing
l l l l
Cause 2 for the alarm generated on the WDM side: The signals transmitted by the upstream OTU have no SDH frame structure. Cause 3 for the alarm generated on the WDM side: The board that reports the alarm is faulty. Cause 4 for the alarm generated on the WDM side: The input signals from the upstream station contain the R_LOS or R_LOF signal. Cause 5 for the alarm generated on the WDM side: The dispersion compensation is very large or very low.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The input signals from the client side contain the R_LOF alarm signal. 1. If the alarm is reported on the client side, 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 3 of this alarm generated on the client side.
CAUTION
Configuring a loopback on the board interrupts the services on the board. 2. l 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.
Cause 2 for the alarm generated on the client side: 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, see 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. l
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. If the alarm persists, the board may be faulty. Replace the faulty board that reports the alarm. For details, see Replacing a Board of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 1 for the alarm generated on the WDM side/cause 2 for the alarm generated on the WDM side: The receive optical power or the OSNR of the local board is abnormal; the signals transmitted by the upstream OTU have no SDH frame structure.
Issue 08 (2011-10-30)
3 Alarm Processing
1.
If the WDM side reports this alarm, use the T2000 to check whether client side of the board in the opposite station reports R_LOF alarm. If it does, deal the fault with the solution for client-side R_LOF. If the alarm remains, use the T2000 to check whether the receive optical power of the WDM-side interface of the alarm-reporting board is in normal range. For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the receive optical power is abnormal, take the alarm as the IN_PWR_LOW or IN_PWR_HIGH alarm for troubleshooting. If the receive optical power is normal, use the SDH meter to receive signals transmitted by the WDM side of the board in opposite station. Check whether the signal is white spectrum or has no SDH format. If it does not comply with the requirement, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
2.
3. 4.
Cause 3 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. If the alarm persists, the board may be faulty. Replace the faulty board at the local station. For details, see Replacing a Board of the Supporting Tasks.
Cause 4 for the alarm generated on the WDM side: The input signals from the upstream station contain the R_LOS or R_LOF signal. 1. If the alarm persists, clear the alarm of the equipment on the upstream station. Cause 5 for the alarm generated on the WDM side: The dispersion compensation is very large or very low. 1. 2. If the alarm persists, replace the DCM module. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases: l l l l MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss Is Very Large MC-A21 Inconsistent Wavelength Range Causes an Interconnection Failure between the WDM and SDH Equipment MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm on the Board MC-A31 Wrong Calculation for Dispersion in One DWDM Project
3.1.35 R_LOS
Description
Loss of signal on receiving line. This alarm is generated when the receive side receives no signal. Reported from the WDM side or client side: WDM side, client side
3-66
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Parameters

There is fiber break in the receive direction and will cause carried service break of this port.
Possible Causes
l l l l l l l l Cause 1 for the alarm generated on the client side: The fiber jumper is not connected at the optical port of the board. Cause 2 for the alarm generated on the client side: The line loss is excessively large or there is a fiber cut. Cause 3 for the alarm generated on the client side: The board at the local station receives colorless light on the client side. Cause 4 for the alarm generated on the client side: The board that reports the alarm is malfunctioning. Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected at the optical port of the board. Cause 2 for the alarm generated on the WDM side: The line loss is excessively large or there is a fiber cut; The optical module sends white light. Cause 3 for the alarm generated on the WDM side: The laser of the board at the opposite station is shut down. Cause 4 for the alarm generated on the WDM side: The transmit module of the opposite station is faulty.
Issue 08 (2011-10-30)
3-67
3 Alarm Processing
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The fiber jumper is not connected at the optical port of the board. 1. l Check whether the fiber jumper is connected at the optical interface of the board at the local station. If not so, connect the fiber jumper.
Cause 2 for the alarm generated on the client side: The line loss is excessively large or there is a fiber cut. 1. Check whether the receive optical power of the interface of the board at the local station is within the normal range by using the T2000, For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the receive optical power is abnormal, take the alarm as the IN_PWR_LOW or IN_PWR_HIGH alarm for troubleshooting. If the receive optical power is normal, check the fiber connector. If there is any dirt or damage, clean the fiber connector. For details, see the Troubleshooting.
Cause 3 for the alarm generated on the client side: The board at the local station receives colorless light. 1. If the receive optical power and the fiber are normal, use a meter to check whether the signals received on the client side of the board are colorless light. If the signals are not colorless light, the board that transmits the signals may be malfunctioning. In this case, replace the malfunctioning board. If the alarm persists, replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected at the optical interface of the board. 1. Check whether the fiber jumper is connected at the optical interface of the board at the local station. If not so, connect the fiber jumper.
Cause 2 for the alarm generated on the WDM side: The line loss is excessively large or there is a fiber cut; The optical module sends white light. 1. Check whether the receive optical power of the interface of the board at the local station is within the normal range by using the T2000. For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the receive optical power is abnormal, take the alarm as the IN_PWR_LOW or IN_PWR_HIGH alarm for troubleshooting. If the receive optical power is normal, check the fiber connector. If there is any dirt or damage, clean the fiber connector. For details, see the Troubleshooting. If the receive optical power and the fiber are normal, use the SDH meter to receive the signals from the WDM side of the board at the opposite station. Check whether the signal is white light. If the result does not comply with the requirement, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
Cause 3 for the alarm generated on the WDM side: The laser of the board at the opposite station is shut down.
3-68
3 Alarm Processing
1. l
Use the T2000 the check whether the board laser of the opposite station is open. If not so, open the laser.
Cause 4 for the alarm generated on the WDM side: The transmit module of the opposite station is faulty. 1. If the alarm persists, the board at the opposite station may be faulty. Replace the board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
Related Cases: l l l l l l MC-A1 The TF Alarm on the OTU at the Upstream Station Results in the OTU_LOF Alarm on the OTU at the Downstream Station MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides. MC-A14 The LWF Board Reports R_LOS Because the Incorrect Fiber Type Leads to Dispersion Over-Compensation MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS When the Service Between the Upstream Optical Amplifier Board and the FIU Board Is Interrupted MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm on the Board MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified by Using An Optical Power Meter
3.1.36 R_OOF
Description
Out of frame on receiving line. 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
Issue 08 (2011-10-30)
3-69
3 Alarm Processing
Description Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

There is a fiber break in the receive direction and will cause carried service break of this port.
Possible Causes
l l l l l l l l Cause 1 for the alarm generated on the client side: The received signals have excessive attenuation or optical power. Cause 2 for the alarm generated on the client side: The bit errors in the transmission are too large. Cause 3 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 4 for the alarm generated on the client side: The clock configuration of the data equipment at the two ends is incorrect. Cause 1 for the alarm generated on the WDM side: The received signals have excessive attenuation or optical power. Cause 2 for the alarm generated on the WDM side: The bit errors in the transmission are too large. Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station is faulty. Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: The received signals have excessive attenuation or optical power. 1. If the client side reports this alarm, check whether the receive optical power of the interface is within the normal range by using the T2000, For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the receive optical power is not in the normal range, deal it with the solution for IN_PWR_LOW or IN_PWR_HIGH.
2. l
Cause 2 for the alarm generated on the client side: The bit errors in the transmission are too large. 1. Check whether there are bit error alarms. If there are bit error alarms, clear the alarms first according to the proper handling procedure.
3-70
3 Alarm Processing
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, inspecting and cleaning the fiber connector. If the alarm persists, replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
Cause 4 for the alarm generated on the client side: The clock configuration of the data equipment at the two ends is incorrect. 1. Check whether Clock Configuration of the data equipment at the two ends is set to Trace the Link Clock. If yes, set the clock configuration of the data equipment at one end to Trace the Internal Clock.
Cause 1 for the alarm generated on the WDM side: The received signals have excessive attenuation or optical power. 1. If the client side reports this alarm, check whether the receive optical power of the interface is within the normal range by using the T2000, For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the receive optical power is not in the normal range, deal it with the solution for IN_PWR_LOW or IN_PWR_HIGH.
2. l
Cause 2 for the alarm generated on the WDM side: The bit errors in the transmission are too large. 1. 2. Check whether there are bit error alarms. If there are bit error alarms, clear the alarms first according to the proper handling procedure. 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, inspecting and cleaning the fiber connector.
Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station is faulty. 1. If the WDM side reports this alarm, use the T2000 to check whether client side of the board in the opposite station reports R_OOF alarm. If it does, deal the fault with the solution for client-side R_OOF.
Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. If the alarm persists, replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
----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
Issue 08 (2011-10-30)
3-71
3 Alarm Processing
3.1.37 R_SLIP
Description
Receiving side frame slipping. The alarm is generated when the phase deviation occurs to the received service frames of the OSC or OTC board. Reported from the WDM side or client side: NA
Attribute
Parameters

This has impact on services carried by the OSC or the OTC, such as degrading in optical supervisory signals or clock signals. This can cause NE disconnection off the NM system.
Possible Causes
l l l l Cause 1: The clock configuration is wrong or the clock signals are not synchronous. Cause 2: The attenuation in the optical line is excessively large, or the receive optical power is too high. Cause 3: The fibers at the eastward and the westward interfaces of the OSC or the OTC are reversely connected. Cause 4: The board that reports the alarm is faulty.
Procedure
l
3-72
Cause 1: The clock configuration is incorrect or the clock signals are not synchronous.
3 Alarm Processing
1.
Check whether the clock configuration is correct, if not, reconfigure it, ensure that the clocks of the total network are synchronous. For details see the Configuration Guide.
Cause 2: The attenuation in the optical line is excessively large, or the receive optical power is too high. 1. Check whether the receive optical power of the interface is within the normal range by using the T2000. For the optical power specification of the specific board, see Technical Specifications of the Product Description . If the receive optical power is excessively low, check the fiber jumper or the fiber connector. If the fiber jumper or fiber connector is dirty, replace the fiber jumper or clean the fiber connector. If the receive-side optical power is to high, adjust the optical attenuator to make the receive optical power in the normal range.
Cause 3: The fibers at the eastward and the westward interfaces of the OSC or the OTC are reversely connected. For example, The fibers at the westward of the TM1 interface and the eastward of the TM2 interface are reversely connected, as shown in the following figure. 1. If the alarm remains, check the engineering fiber connection figure to see whether the fibers at the eastward and the westward interfaces of the OSC or the OTC are reversely connected. If the fiber connection is incorrect, correct it according to the figure.
OA
F I U RM1 TM2 TM1 RM2 F I U
SC2
OA
Cause 4: The board that reports the alarm is faulty. 1. 2. If the alarm persists, perform a cold reset on the faulty board through the T2000. If the alarm persists, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
Related Cases: l MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the OSC Board
3.1.38 REM_SF
Description
Remote signal failure alarm. This alarm is generated when the remote end received signals fail. Reported from the WDM side or client side: client side
3 Alarm Processing
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 Parameter 1 Meaning Indicates the optical port where the alarm is generated. For example, 0x01 indicates optical port 1.
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is generated. For example, 0x00 0x01 indicates channel 1 of the optical port indicated by parameter 1.

Services borne by client sides of the board are interrupted.
Possible Causes
l l Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the opposite end. Cause 2: The client side of the OTU board at the opposite end is faulty.
Procedure
l Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the opposite end. 1. Check whether there is an R_LOS or R_LOF alarm on the client side of the OTU board at the opposite station on the T2000. If there is an R_LOS or R_LOF alarm, see R_LOS or R_LOF to clear the alarm. Replace the OTU board at the opposite station.For details, see Replacing a Board of the Supporting Tasks.
Cause 2: The client side of the OTU board at the opposite end is faulty. 1.
----End
Related Information
None.
3 Alarm Processing
3.1.39 SECU_ALM
Description
Security alarm. The alarm is generated when the login fails after five consecutive login failure performed by the same user. Reported from the WDM side or client side: NA
Attribute
Parameters
None.

The alarm automatically ends with no impact on the system.
Possible Causes
l l Cause 1: This alarm can be caused by illegal login, such as login with a incorrect password or a user not exist. Cause 2: The board that reports the alarm is faulty.
Procedure
l Cause 1: This alarm can be caused by illegal login, such as login with a incorrect password or a user not exist. 1. l Check whether there are users illegally logging in to the NE. If yes, clear the user that is illegally logged in to. If the alarm persists when there is no user who logged in to the NE illegally, replace the board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.1.40 SM_BEI
Description
OTU layer, SM section backward error indication. If the board detects that the input signals contain the SM-BIP8 bit errors, it inserts the SM_BEI alarm back to the upstream board. The
3 Alarm Processing
alarm occurs when the upstream station detects that the BEI flag in the OCH-OH of the SM section of the received signals is true. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

The bit errors occur to the service signals, which influence the system quality.
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU board of which the client side supports the OTN services (For example, ETMX, LBF), the input signals from the client side contain the SM_BEI signal, as shown in the following figure. The input signals on the client side of the OTU in the station A contain the SM_BEI signals. The OTU in the station A reports the SM_BEI alarm on the client side after detecting the SM_BEI signals and transparently sends the SM_BEI signals to the station B (opposite station) at the same time.
3-76
Issue 08 (2011-10-30)
3 Alarm Processing
Detects and reports the SM_BEI alarm
The client signals contain the SM_BEI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
l l
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The SM_BIP8 bit errors occur when the OTU at the opposite station receives the signals of the local station, as shown in the following figure. The WDM side of the OTU in the station B (opposite station) inserts the SM_BEI signals back to the station A (local station) after detecting the SM-BIP8 bit errors. The WDM side of the OTU in the station A reports the SM_BEI alarm after detecting the SM_BEI signals.
Detects the SM-BIP8 bit errors
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the SM_BEI alarm
Station B Insert the SM_BEI signal back
l l
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the SM_BEI signals back to the local station improperly. See the following figure. The WDM side of the OTU in the station B (opposite station) inserts the SM_BEI signals back to the station A (local station) by mistake. The WDM side of the OTU in the station A reports the SM_BEI alarm after detecting the SM_BEI signals.
Issue 08 (2011-10-30)
3-77
3 Alarm Processing
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the SM_BEI alarm
Station B Insert the SM_BEI signal by mistake
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports OTN services, the input signals from the client side contain the SM_BEI signal. 1. If the client side reports the SM_BEI alarm, check whether the client-side equipment connected to the OTU is faulty according to the related manuals. If yes, clear the fault of the client-side equipment by referring to the related manuals. If the alarm persists, the OTU in the local station is faulty. Replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
Cause 1 for the alarm generated on the WDM side: The SM_BIP8 bit errors occur when the OTU at the opposite station receives the signals of the local station. 1. If the WDM side reports the SM_BEI alarm, check whether the SM_BIP8 bit error occurs when the OTU in the upstream station receives the signals in the local station. If yes, handle the alarm by referring to the handling procedure of the SM_BIP8_OVER alarm. If the alarm persists, perform a cold reset on the faulty board through the T2000.
2. l
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. If the alarm persists, the OTU in the local station is faulty. Replace the faulty board. Cause 3 for the alarm generated on the WDM side: The board at opposite station is faulty. It inserts the SM_BEI signals back to the local station improperly. 1. If the alarm persists, the OTU in the opposite station may be faulty. Replace the faulty board.
----End
Related Information
None.
3-78
Issue 08 (2011-10-30)
3 Alarm Processing
3.1.41 SM_BIP8_OVER
Description
OTU layer, 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. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

The service signals borne by the wavelength generate a great amount of bit errors. The signals are degraded.
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services (For example, ETMX, LBF), the input signals from the client side contain a great amount of BIP8 bit errors of the SM section. Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The input optical power is excessively high or low. Cause 2 for the alarm generated on the WDM side: The system performance declines. For example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or nonlinearity occurs.
l l l
Issue 08 (2011-10-30)
3 Alarm Processing
l l
Cause 3 for the alarm generated on the WDM side: The board at opposite station is faulty. Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services (For example, ETMX, LBF), the input signals from the client side contain a great amount of BIP8 bit errors of the SM section. 1. In the case of the OTU board of which the client side supports the OTN services, check on the T2000 whether the input signals on the client side has a great amount of BIP8 bit errors of the PM section. If yes, remove the fault on the client-side equipment. If the alarm persists, the board at the local station may be faulty. Replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
Cause 1 for the alarm generated on the WDM side: The input optical power is excessively high or low. 1. If the alarm persists, Check whether the input optical power of the interface is within the normal range by using the T2000, For the optical power specification of the specific board, see Technical Specifications of the Product Description .. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. If the alarm persists, For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting.
Cause 2 for the alarm generated on the WDM side: The system performance declines. 1.
Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. 1. If the alarm persists, the board in the opposite station may be faulty. Replace the faulty board.
Cause 4 for the 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 may be faulty. Replace the faulty board.
----End
Related Information
None.
3.1.42 SM_TIM
Description
OTU layer, SM Trail Trace Identifier (TTI) is mismatched . The alarm occurs when the received TTI value of the SM section is not consistent with the TTI value to receive. Reported from the WDM side or client side: WDM side, client side
3 Alarm Processing
Attribute
Parameters

The specific impact depends on the cause of the alarm. l l If the TTI byte is incorrectly configured, the alarm has no impact on the services and the system. If the fiber is incorrectly connected, the services are interrupted.
Possible Causes
l l Cause 1: The TTI bytes of the SM section to receive by the board in the local station or the opposite station is incorrectly configured. Cause 2: The fiber is incorrectly connected.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The TTI bytes of the SM section to receive by the board in the local station or the opposite station is incorrectly configured. 1. Check on the T2000 whether the TTI bytes of the SM section to receive by the OTU in the local station is consistent with that to be transmitted by the opposite station. If not, set the TTI byte of the SM section to receive or to be transmitted on the T2000 to ensure the consistency. For detailed operations, refer to section "Configuring OTU Overheads" in the Configuration Guide.
l
Issue 08 (2011-10-30)
Cause 2: The fiber is incorrectly connected.

3 Alarm Processing
1.
If the alarm persists, check whether the fiber is correctly connected according to the engineering fiber connection diagram. If not, connect the fiber again according to the fiber connection diagram.
----End
Related Information
The alarm is used for monitoring the SM section of the optical transport network (OTN). Set on the T2000 the TTI byte of the section monitoring (SM) section to receive, and then compare the value with the received TTI byte of the section. The alarm occurs when the two values are not the consistent.
3.1.43 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.
Attribute
Parameters

The single optical signal output by the board might be lost. The services have bit errors or even are interrupted.
3-82
Issue 08 (2011-10-30)
3 Alarm Processing
Possible Causes
l l l Cause 1: The attenuation of the fiber increases, the fiber jumper, fiber connector or the optical attenuator is dirty. Cause 2: The board in the upstream station is faulty, and thus the output optical power is decreased. Cause 3: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The attenuation of the fiber increases, the fiber jumper, fiber connector or the optical attenuator is dirty. 1. 2. 3. l Check the cables, fiber jumpers, fiber connectors and attenuators. If the attenuation of the cables is larger than that in engineering design, adjust the attenuator, rectify the cables. If the fiber jumper, fiber connector, or fiber attenuator is dirty or damaged, replace the fiber jumper or check and clean the fiber connector.
Cause 2: The board in the upstream station is faulty, and thus the output optical power is decreased. 1. Query the input and output optical power of the upstream boards in the reversed sequence of signal flow by using the T2000 and find out the faulty area where the optical power is excessively low. Check the output optical power of the upstream stations. If it is abnormal, the board in the upstream station might be faulty. Replace the faulty board. For details, see Replacing a Board of the Supporting Tasks. If the alarm persists, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.1.44 SUM_OUTPWR_LOW
Description
Output optical power is excessively low. The alarm is generated when the output optical power of the board is lower than the lower threshold.
Attribute
Alarm Severity Major
Issue 08 (2011-10-30)
Alarm Type Equipment alarm
3-83
3 Alarm Processing
Parameters

The input optical power of the downstream receive board is excessively low, which leads to that the services generate the bit errors or even are interrupted.
Possible Causes
l l l l Cause 1: The internal attenuation of the board (only for the V40) is excessive. Cause 2: The fiber is incorrectly connected. Cause 3: The input optical power of the signals of the board is excessively low. Cause 4: The board that reports the alarm is faulty.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The internal attenuation of the board (only for the V40) is excessive. 1. Query on the T2000 the attenuation of each channel of the board (only for the V40) to check whether the attenuation is excessive. If yes, adjust the attenuation of the corresponding channel to the suitable value on the T2000. If the alarm persists, check whether the fiber connection is correct according to the engineering fiber connection diagram. The input optical signals of different wavelengths should be accessed from the corresponding input optical interfaces of the board. If the fiber connection is not correct, correctly connect the fiber according to the fiber connection diagram. If the alarm persists, test the output optical power of the board at the local station by using an optical power meter. Compare the test value with the optical power performance reported by the board at the local station to check the consistency, For the optical power specification of the specific board, see Technical Specifications of the Product Description .. If they are not consistent, test the input power of the input
Cause 2: The fiber is incorrectly connected. 1.
Cause 3: The input optical power of the signals of the board is excessively low. 1.
3-84
3 Alarm Processing
interface of the board and the output power of the board in the opposite station by using an optical power meter. If the input power of the board at the local station but the output power of the board in the opposite station is within the normal range, check the fiber jumper and fiber connector. If it is dirty, replace the fiber jumper or clean the fiber connector. If the output power of the board in the opposite station is excessively low, the board in the opposite station reports the related alarms. Check the related alarms on the T2000, and handle the alarms by referring to the corresponding handling procedure. l Cause 4: The board that reports the alarm is faulty. 1. ----End If the alarm persists, the board at the local station is faulty. Replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
Related Information
None.
3.1.45 T_DATA_LOST
Description
Client-side transmitting data lost. The board regularly checks the Ethernet performance event "Good Octets Transmitted" and compares the number with the number of last time. The alarm is generated when the two numbers are the same, which indicating that the board does not transmit any data. Reported from the WDM side or client side: client side
Attribute
Parameters
Issue 08 (2011-10-30)
3-85
3 Alarm Processing
Parameter
Description

The connection status of the Ethernet port is normal; however, the transmitted optical signals do not have data packet.
Possible Causes
l l Cause 1: The WDM side of the board at the local station does not receive any data, which leads to that the client side has no data to transmit. Cause 2: The WDM side of the board at the local station can receive data, but the client side has no data to transmit due to the faulty board.
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The WDM side of the board at the local station does not receive any data, which leads to that the client side has no data to transmit. 1. Check whether the board in the opposite station has the R_DATA_LOST alarm. If yes, handle the R_DATA_LOST alarm according to the corresponding handling procedure.
Cause 2: The WDM side of the board at the local station can receive data, but the client side has no data to transmit due to the faulty board. 1. 2. If the alarm persists, the board at the local station might be faulty. Perform a cold reset on the faulty board on the T2000. If the alarm persists, replace the faulty board at the local station.
----End
Related Information
Generally the T_DATA_LOST alarm of the board at the local station is caused by the R_DATA_LOST alarm of the board in the upstream station.
3.1.46 TD
Description
Transmitter degrade alarm. The alarm is generated when the bias current of the laser exceeds the degrade threshold. Reported from the WDM side or client side: WDM side, client side
3 Alarm Processing
Attribute
Parameters

Possibly the board laser cannot work normally, or the output light of the laser is of low quality or with bit errors and further cause service break.
Possible Causes
l l Cause 1: The laser is aging. Cause 2: The air conditioner (A/C) does not work for a certain cause and thus the temperature is high, which causes the TD alarm.
Procedure
l Cause 1: The laser is aging. 1. 2. On the T2000, perform a warm reset on the board where the alarm is generated and then check whether the alarm is cleared. If the alarm persists, check whether the board supports pluggable laser module. If the board uses pluggable optical modules, replace the specific pluggable optical module. For details, see Replacing Pluggable Optical Modules of the Parts Replacement. If the board is not pluggable, replace the faulty board, For details, see Replacing a Board of the Supporting Tasks.
3. l
Cause 2: The air conditioner (A/C) does not work for a certain cause and thus the temperature is high, which causes the TD alarm. 1. 2. Start the air conditioner (A/C) and then the alarm is cleared automatically. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
3 Alarm Processing
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after longterm 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.1.47 TF
Description
Transmission failure. The alarm is generated when the launched 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
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 optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

The laser transmission becomes faulty, which causes service interruption.
Possible Causes
Cause 1: The laser module is damaged, or the laser is aging.
Procedure
l Cause 1: The laser module is damaged, or the laser is aging. 1. 2. On the T2000, perform a warm reset on the board where the alarm is generated and then check whether the alarm is cleared. If the alarm persists, check whether the board supports pluggable laser module. If the board uses pluggable optical modules, replace the specific pluggable optical module. For details, see Replacing Pluggable Optical Modules of the Parts Replacement.
3-88
3 Alarm Processing
3. ----End
If the board does not support pluggable laser module, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after longterm 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 Because the Fan Speed Is Low and the Board Temperature Reaches 60 Degrees Centigrade
3.1.48 WRG_BD_TYPE
Description
incorrect board type. The alarm is generated when the logic board and the physical board are not consistent. Reported from the WDM side or client 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 Parameter 1 Indicates the slot where the installed board is mismatched with the configured board. For example, 0x01 indicates that the physical board installed in slot 1 is not the same as the configured logical board.

The type of the logical board is inconsistent with the type of the physical board. The board cannot work normally.
3 Alarm Processing
Possible Causes
l l l Cause 1: The type of the logical board configured on the T2000 is inconsistent with the type of the physical board installed in the slot. Cause 2: The board software is incorrect. Cause 3: The board that reports the alarm is faulty.
Procedure
l Cause 1: The type of the logical board configured on the T2000 is inconsistent with the type of the physical board installed in the slot. 1. Check whether the logical board configured on the T2000 has accordant board type with the physical board in the slot. If not, check whether the fault lies in the logical board or the physical board according to the engineering configuration requirements. If the logical board configuration is faulty, reconfigure the logical board in the T2000. If the physical board configuration is faulty, insert a physical board of the correct type. l Cause 2: The board software is incorrect. 1. l If the alarm persists when the type of the logical board is consistent with the type of the physical board, check whether the board software matches the hardware. If the alarm persists when the board software matches the hardware, replace the faulty board. For details, see Replacing a Board of the Supporting Tasks.
----End
Related Information
None.
3.2 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
In the case of an alarm, see its handling procedure to clear it; if this alarm persists, contact Huawei engineers for troubleshooting.
The alarm handling involves board reset, either of software or hardware. Software reset and hardware reset have different impacts on services. l Reset of the SCC board: A software reset of the SCC is a restart of the upper-layer software, which neither updates the FPGA file or hardware data nor interrupts services. A hardware reset of the SCC might result in reconfiguration of the key hardware, such as FPGA reloading; the upper-layer software need be restarted. 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.
3-90
3 Alarm Processing
3.2.1 AD_CHECK_FAIL
Description
AD (analog to digital converter) self check failure alarm. This alarm is generated when the AD chip on the board is faulty. Reported from the WDM side or client 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 Parameter 1 Description Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.
Parameters 2 and 3 The value is always 0x00 0x01. There is no concept of channels.

l l This alarm might affect services. Parameters relevant to the AD chip on the board, such as board input/output optical power, back facet current and cooling current, fail to be queried on the T2000. As a result, maintenance engineers can neither obtain the current operation performance data of the network nor find in time any dormant problems of the network operation. The alarm might interrupt or even fail the system, which should be handled at once.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Replace the faulty board. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
None
3.2.2 ALM_PIUA_OFFLINE
Description
The power interface unit A (PIUA) offline alarm. This alarm is generated when the system detects that PIUA in the subrack is offline.
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 Parameter 1 Parameters 2 and 3 Description There is no concept of optical interfaces, it is always 0x01. The value is always 0x00 0x01. There is no concept of channels.

The subrack lacks one backup input power supply (PIUA), which affects the reliability of the subrack power supplies.
Possible Causes
l l The power interface unit A is offline. The power interface unit A is faulty.
Procedure
Step 1 Check whether PIUA of the subrack is correctly connected or not. If not, reconnect it correctly. Step 2 If PIUA of the subrack is correctly connected while the alarm persists, PIUA is faulty. Replace the faulty PIUA. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
None
3.2.3 ALM_PIUB_OFFLINE
Description
The power interface unit B (PIUB) offline alarm. This alarm is generated when the system detects that PIUB in the subrack is offline. Reported from the WDM side or client 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 Parameter 1 Parameters 2 and 3 Description There is no concept of optical interfaces, it is always 0x01. The value is always 0x00 0x01. There is no concept of channels.

The subrack lacks one backup input power supply (PIUB), which affects the reliability of the subrack power supplies.
Possible Causes
l l The power interface unit B is offline. The power interface unit B is faulty.
Procedure
Step 1 Check whether PIUB of the subrack is correctly connected or not. If not, reconnect it correctly. Step 2 If PIUB of the subrack is correctly connected while the alarm persists, PIUB is faulty. Replace the faulty PIUA. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
None
3.2.4 AU_AIS
Description
AU alarm indication signal. The alarm is generated when the AU (including pointers) of the SDH frame are all "1" signals. The client side sends the AU_AIS signals to the WDM side after the higher order path signal failure of the receive end on the client side. Reported from the WDM side or client side: WDM side.
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 Parameter 1 Description The path number of the VC4 in SDH frames. The different SDH frame has a different value range. For example, The value range of the STM-N frame is from 0x01 to 0x0n.

Possible Causes
l As shown in the following figure, the client side of the opposite station sends AU_AIS.
3-94
Issue 08 (2011-10-30)
3 Alarm Processing
Detects and reports the AU_AIS alarm
The client side sends AU_AIS signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The client-side outloop or the WDM-side inloop occurs to the board in the opposite station, and the downstream station detects the AU_AIS alarm, as shown in the following figure.
Detects and reports the AU_AIS alarm
Outloop on the client side/ Inloop on the WDM side
O T U
WDM side
WDM side
O T U
Client side
Station A
Station B
The receive optical module of the board at the local station or the transmit part of the clientside equipment is faulty.
Procedure
Step 1 Check whether client-side outloop or the WDM-side inloop occurs to the board in the opposite station. If yes, there is no need to handle the alarm. Step 2 If the alarm persists, check whether the client side of the opposite station transmits AU_AIS signal. If yes, remove the fault of the equipment on the client side. Step 3 If the alarm persists, check whether the launched optical power of the equipment on the client side of the opposite station is normal. If the power is abnormal, remove the fault of the equipment on the client side. Step 4 If the alarm persists, check whether the input optical power of the WDM side of the board at the local station is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, add proper attenuation by adding a fixed attenuator or VOA. Step 5 If the alarm persists and the faulty board supports the pluggable optical module, replace the pluggable optical module. For details, see Parts Replacement. Step 6 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
If the client-side outloop or the WDM-side inloop occurs to the board in the upstream station, the AU_AIS alarm is normal. The alarm disappears when the loopback is released. Hence, there is no need to handle the alarm.
3.2.5 AU_LOP
Description
AU loss of pointer. The alarm is generated when the AU_PTR values in consecutive eight frames are invalid (the value is out of the range from 0 to 782). Reported from the WDM side or client side: WDM side.
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 Parameter 1 Description The path number of the VC4 in SDH frames. The different SDH frame has a different value range. For example, The value range of the STM-N frame is from 0x01 to 0x0n.

Possible Causes
l As shown in the following figure, the client side of the opposite station sends AU_LOP.
3-96
Issue 08 (2011-10-30)
3 Alarm Processing
Detects and reports the AU_LOP alarm
The client side sends AU_LOP signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
l l
The service timeslots configured at the local station and in the opposite station are not consistent. The board hardware is faulty.
Procedure
Step 1 Check whether the opposite station have the AU_LOP alarm or not. l l If yes, the board in the opposite station is faulty. Replace the faulty board in the opposite station. If not, check whether the service configuration at the local station and in the opposite station are consistent. If they are different, configure the services again.
Step 2 If the alarm persists, replace the faulty board at the local station. For details, see the Parts Replacement. ----End
Related Information
None
3.2.6 B1_SD
Description
Regenerator section (B1) excessive errors. The alarm is generated when the received signals in SDH frame degrades and the B1 bit errors in the multiplex section exceeds the signal degrade (SD) threshold. Reported from the WDM side or client side: WDM side, client side l 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 (SD) threshold. 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 (SD) threshold.
Issue 08 (2011-10-30)
3-97
3 Alarm Processing
Attribute
Parameters

The B1 bit errors in the service signals received by the board exceeds the degrade threshold of signals set on the board. The generation of the alarm has an influence on the QoS of the service signals.
Possible Causes
l l l The attenuation of the received signals is overlarge; the fiber or connector is dirty. The transmit part of the opposite station is faulty. The receive part of the local station is faulty.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the receive optical power of the board at the local station is excessively low, clear the alarm according to the handling procedure of the IN_PWR_LOW alarm. Step 2 If the alarm persists, check whether the launched optical power of the corresponding interface on the upstream board is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the launched optical power of the board in the upstream station is excessively low, clear the alarm according to the handling procedure of the OUT_PWR_LOW alarm. Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using the T2000 and loop back the transmit optical interface and receive optical interface on the WDM
3 Alarm Processing
side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault of the upstream station. Step 4 If the alarm persists and the faulty board supports the pluggable optical module, replace the pluggable optical module. For details, see the Parts Replacement. Step 5 If the alarm persists, replace the faulty board at the local station. For details, see the Parts Replacement. Step 6 If the alarm bursts, it may be caused by that the transmission line is influenced by various noise sources. Search the jam source that may cause the burst bit error and remove the interference. ----End
Related Information
None
3.2.7 B2_EXC
Description
Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the threshold. Reported from the WDM side or client side: WDM side, client side l l The alarm is generated on the WDM side when the B2 bit errors in the SDH signals received on the WDM side exceed the B2 bit error threshold. The alarm is generated on the client side when the B2 bit errors in the SDH signals received on the client side exceed the B2 bit error threshold.
Attribute
Parameters
Issue 08 (2011-10-30)
3-99
3 Alarm Processing
Parameter
Description

The B2 bit errors in the service signals received by the board exceeds the threshold of the B2 bit errors set on the board. The generation of the alarm has an influence on the QoS of the service signals.
Possible Causes
l l l The attenuation of the received signals is overlarge; the fiber or connector is dirty. The transmit part of the opposite station is faulty. The receive part of the local station is faulty.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the receive optical power of the board at the local station is excessively low, clear the alarm according to the handling procedure of the IN_PWR_LOW alarm. Step 2 If the alarm persists, check whether the launched optical power of the corresponding interface on the upstream board is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the launched optical power of the board in the upstream station is excessively low, clear the alarm according to the handling procedure of the OUT_PWR_LOW alarm. Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using the T2000 and loop back the transmit optical interface and receive optical interface on the WDM side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault of the upstream station. Step 4 If the alarm persists and the faulty board supports the pluggable optical module, replace the pluggable optical module. For details, see the Parts Replacement. Step 5 If the alarm persists, replace the faulty board at the local station. For details, see the Parts Replacement. Step 6 If the alarm bursts, it may be caused by that the transmission line is influenced by various noise sources. Search the jam source that may cause the burst bit error and remove the interference. ----End
Related Information
None
3-100
Issue 08 (2011-10-30)
3 Alarm Processing
3.2.8 B2_SD
Description
Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the signal degrade (SD) threshold. Reported from the WDM side or client side: WDM side, client side l l The alarm is generated on the WDM side when the B2 bit errors in the SDH signals received on the WDM side exceed the signal degrade (SD) threshold. The alarm is generated on the client side when the B2 bit errors in the SDH signals received on the client side exceed the signal degrade (SD) threshold.
Attribute
Parameters

The B2 bit errors in the service signals received by the board exceeds the degrade threshold of signals set on the board. The generation of the alarm has an influence on the QoS of the service signals.
Possible Causes
l l l
Issue 08 (2011-10-30)
The attenuation of the received signals is overlarge; the fiber or connector is dirty. The transmit part of the opposite station is faulty. The receive part of the local station is faulty.
3 Alarm Processing
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the receive optical power of the board at the local station is excessively low, clear the alarm according to the handling procedure of the IN_PWR_LOW alarm. Step 2 If the alarm persists, check whether the launched optical power of the corresponding interface on the upstream board is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the launched optical power of the board in the upstream station is excessively low, clear the alarm according to the handling procedure of the OUT_PWR_LOW alarm. Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using the T2000 and loop back the transmit optical interface and receive optical interface on the WDM side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault of the upstream station. Step 4 If the alarm persists and the faulty board supports the pluggable optical module, replace the pluggable optical module. For details, see the Parts Replacement. Step 5 If the alarm persists, replace the faulty board at the local station. For details, see the Parts Replacement. Step 6 If the alarm bursts, it may be caused by that the transmission line is influenced by various noise sources. Search the jam source that may cause the burst bit error and remove the interference. ----End
Related Information
None
3.2.9 BD_STATUS
Description
Board out of position alarm. The alarm is generated when the physical board is not inserted in the slot.
Attribute
Parameters
None

The board is not in service. Hence, the functions related to the board are unavailable.
3 Alarm Processing
Possible Causes
l In the case of the PMU board in the power supply box of the OptiX BWS 1600G, it is possible that the serial cable and alarm cable is improperly connected, or the DIP switch on the PMU is improperly set. In the case of the ROP board of the OptiX BWS 1600G, it is possible that communication between the board and the subrack fails. The logic board is configured but the physical board has not been inserted in the proper slot. The connection between the plug of the board and the socket of the mother board is loose. The board is faulty.
l l l l
Procedure
Step 1 If the PMU board in the power supply box reports the alarm, check whether the serial cable and alarm cable on the PMU are properly connected. If not, reconnect them properly. Step 2 If the alarm persists, check the dip switch on the PMU board. For the configuration of the dip switch, see the Hardware Description. If the dip switch is set improperly, re-set the dip switch properly (switch up or switch down according to actual situation). Step 3 If the ROP board reports the alarm, check whether the network cable for connecting the ROP board to the subrack is loose or damaged. If yes, reconnect or replace the network cable. Step 4 Check whether the corresponding board is inserted in the physical slot. l l If no corresponding board is inserted, insert the board. If the corresponding board is inserted, check whether the insertion is firm. If not, reset the board.
Step 5 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.10 BD_VER_NMAT
Description
The board version mismatch alarm. This alarm is generated when the board software version, FPGA version, BIOS version or extended BIOS version does not comply with the version mapping table. Reported from the WDM side or client side: NA
Attribute
Issue 08 (2011-10-30)
3-103
3 Alarm Processing
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 slot where the alarm is generated. For example, 0x01 denotes slot 1. Parameter 2 Indicates a board software type that does not comply with the version mapping table, For example, l 0x01 denotes that the extended BIOS version does not comply with the version mapping table. l 0x02 denotes that the board software version does not comply with the version mapping table. l 0x03 denotes that the FPGA version does not comply with the version mapping table. l 0x04 denotes that the BIOS version does not comply with the version mapping table. Parameter 3 Indicates a reserved parameter whose value is always 0xff. Parameter 4 Indicates a reserved parameter whose value is always 0xff. Parameter 5 Indicates a reserved parameter whose value is always 0xff.

Mismatch of any board software version with the NE software version in the version mapping table fails some intended functions.
Possible Causes
l l l l The board software version does not comply with the version mapping table. The board FPGA version does not comply with the version mapping table. The extended BIOS version does not comply with the version mapping table. The BIOS version does not comply with the version mapping table.
Procedure
Step 1 If the board software version does not comply with the version mapping table, update the board software according to the Version Upgrade Guide and version mapping table. Step 2 If the board FPGA version does not comply with the version mapping table, update the board FPGA according to the Version Upgrade Guide and version mapping table.
3 Alarm Processing
Step 3 If the extended BIOS version does not comply with the version mapping table, update the extended BIOS software according to the Version Upgrade Guide and version mapping table. Step 4 If the BIOS version does not comply with the version mapping table, replace the board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.11 BEFFEC_SD
Description
Signal degraded alarm before FEC alarm. 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 is generated when the counted bit error rate exceeds the threshold. Reported from the WDM side or client side: WDM side
Attribute
Parameters

The system redundancy decreases, which affects the quality of signals if the decrease is serious.
3 Alarm Processing
Possible Causes
l l l l The board input optical power is excessively high or low. The system performance declines. For example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or non-linearity occurs. The opposite-end board is faulty. The local-end board is faulty.
Procedure
Step 1 On the T2000, 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. Step 2 If the alarm persists, the performance of the system may be degraded, for example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or non-linearity occurs. For details, see "Rectifying Bit Errors" in the Troubleshooting. Step 3 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For details, see the Parts Replacement. Step 4 If the alarm persists, the board in the opposite station might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.12 BOOTROM_BAD
Description
BOOTROM data check failed alarm. This alarm is generated when the basic or extended BIOS software of the board is damaged. Reported from the WDM side or client side: NA
Attribute
Parameters
3 Alarm Processing
Description The value is always 0x03.
Parameters 2 and 3 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software. 0x02 indicates the extended BIOS software. Parameter 4 The value is always 0x01.

When repowered on or reset after a power supply failure, the SCC board cannot be normally started.
Possible Causes
l l l The extended BIOS software of the board is damaged. The basic BIOS software of the board is damaged. The SCC board is faulty.
Procedure
Step 1 Determine upon the alarm parameter (0x01 denotes the basic BIOS while 0x02 the extended BIOS) whether the basic or extended BIOS software of the board is damaged. Step 2 If the basic BIOS software is faulty, replace the faulty SCC board. For details, see the Parts Replacement. Step 3 If the extended BIOS software is damaged, reload the extended BIOS of the SCC board. For details, see the Version Upgrade Guide. Step 4 If the alarm persists, the SCC board might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.13 CFG_VERIFY
Description
Configuration is not verified.
Attribute
Issue 08 (2011-10-30)
Alarm Type Security alarm
3-107
3 Alarm Processing
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. None

The configuration data is not taken into effect.
Possible Causes
The alarm is generated when the verification is not performed 15 minutes after the last configuration command is issued.
Procedure
Step 1 Download the configuration data on the T2000 to issue the configuration information again and verify it. ----End
Related Information
None
3.2.14 CFGBD_FAIL
Description
Board configuration is mismatched. The alarm is generated when the configuration issued and the protection type are not consistent in the case of that the protection type of the single fed and single receiving board is configured to intra-board channel protection. Reported from the WDM side or client side: NA
Attribute
Parameters
None

The intra-board protection configured cannot realize the protection function.
3 Alarm Processing
Possible Causes
The configuration is error. The protection type of the single fed and single receiving board is configured to intra-board channel protection.
Procedure
Step 1 The single fed and single receiving board does not support intra-board protection. Delete the protection attribute of the board on the T2000 after confirming that the board configured is the single fed and single receiving board. Step 2 Replace the board with a dual fed selective receiving board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.15 CFGDATA_OUTRANGE
Description
Board configuration data out of range alarm.
Attribute
Parameters
Parameter Parameter 1 Description Indicates the type of the configured data that exceeds the threshold or does not comply with the SCC board. 0x01 denotes the OTU board operating wavelength. 0x08 denotes the working mode of the optical interface. 0x09 denotes the type of the services to be transmitted. 0x0b denotes the cross-connect capacity. 0x0c denotes mapping trail of the service. Parameter 2 Indicates the slot ID of the physical board whose configuration exceeds the threshold.
Issue 08 (2011-10-30)
3-109
3 Alarm Processing

As for the cross-connect capacity, this alarm results in the logical cross-connect capacity configured for the subrack exceeds the capacity supported by the equipment. As for the mapping trail mode for the service, this alarm results in the difference between the configured mapping trail of the service and the mapping trail mode that is actually supported by the board. As a result, services at the optical layer are not available.
Possible Causes
l l As for the operating wavelength of the OTU, the configured logic wavelength differs with the actual wavelength or falls beyond the tuning range. In the case of the working mode of the optical interface, if the board does not support the configured working mode, the configuration data on the SCC is inconsistent with the data on the board. In the case of the type of the services to be transmitted, if the board does not support the configured service type, the configuration data on the SCC is inconsistent with the data on the board. As for the cross-connect capacity, the cross-connect capacity configured exceeds the crossconnect capacity supported by the equipment. In the case of the mapping trail mode, if the configured mapping trail of the service is not supported by the board, configuration data is inconsistent between the SCC and the board.
l l
Procedure
Step 1 View on the T2000 the parameters of the alarm and confirm the configuration data type and the IDs of the slot, optical interface and channel that correspond to the configuration data thresholdcrossing alarm. Step 2 Take the relevant handling measures according to the configuration data type. l As for the operating wavelength of the OTU, query the actual wavelength of the board and the logic wavelength stored on the NE software side. 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; or replace the board or optical module with another one whose wavelength is the same as that stored in the NE software. In the case of the working mode of the optical interface, check whether the configured working mode is the same as the actual mode of the board by using the T2000. If the configured working mode is not the same as the actual mode, re-configure the working mode of the optical interface.
3-110
3 Alarm Processing
In the case of the type of the services to be transmitted, check whether the service type is the same as the actual type of the services accessed by the board by using the T2000. If the configured service type is not the same as the actual service type, re-configure the service type. As for the cross-connect capacity, check whether the logical cross-connect capacity configured for the subrack exceeds the capacity supported by the equipment. If yes, reconfigure the cross-connect. In the case of the mapping trail mode for the service, check whether the mapping trail is the same as the mode that is actually supported by the board. If the configured mode is not supported by the board, re-configure a valid the mode of the board.
----End
Related Information
None
3.2.16 CHAN_ADD
Description
Channel of single wave signal add. The alarm is generated when the MCA (optical spectrum analyzing) board detects that new channels are added after it scans the optical spectrum. Reported from the WDM side or client 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 Parameter 1 Description Indicates the ID of the optical interface where the alarm is generated, namely, the ID of the optical interface the MCA detects. For example, 0x01 denotes that the MCA detects optical interface 1.
Parameters 2 and 3 Indicates the ID of the channel in where the alarm is generated, namely, the ID of the wavelength at which the alarm is reported. For example, 0x00 0x01 denotes that the alarm is reported in channel (or at wavelength) 1.
Issue 08 (2011-10-30)
3-111
3 Alarm Processing

The MCA cannot monitor the optical spectrum performance of the wavelength related to the alarm.
Possible Causes
l l The configuration for wavelength monitoring is incorrect. The accessed wavelength is not set to be the monitored wavelength. The MCA board is faulty.
Procedure
Step 1 Check whether the configuration for wavelength monitoring of the MCA board is incorrect by using the T2000. If the configuration is incorrect, modify the configuration to ensure that the monitored wavelength and the number of the monitored wavelengths are consistent with the accessed wavelength and the number of accessed wavelengths. Step 2 If the alarm persists, test the optical spectrum data of the input optical signals by using the optical spectrum analyzer. If the data is normal, the optical spectrum analyzing module may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.17 CLT_MM
Description
Service type on client is not match. The alarm is generated when the service type of the corresponding optical interface of the board at the local station is not consistent with that in the opposite station. Reported from the WDM side or client side: client side
Attribute
Parameters
3 Alarm Processing
Description Indicates the optical port where the alarm is generated. For example, 0x03 indicates optical port 3.

The services borne by the optical interface on the client side would be interrupted.
Possible Causes
l l The service type of the corresponding optical interface of the board at the local station is not consistent with the opposite station. The board at the local station is faulty.
Procedure
Step 1 Check whether the service type of the corresponding optical interface of the board at the local station is consistent with that in the opposite station by using the T2000. If not, configure the service type again. Step 2 If the alarm persists, check whether the cross-connection of corresponding optical interface of the board at the local station is configured correctly; if it is not consistent with the engineering design, configure it again. Step 3 If the alarm persists, maybe the board at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.18 COMMUN_FAIL
Description
Internal communication failure on the board. Reported from the WDM side or client side: NA.
Attribute
Issue 08 (2011-10-30)
3-113
3 Alarm Processing
Parameters
Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. For example, 0x00 0x01 denotes channel 1 of RS485; 0x00 0x02 denotes channel 2 of RS485; 0x00 0x03 denotes the channel between boards; 0x00 0x04 denotes the Ethernet emergency channel between subracks.

The board that reports the alarm cannot be reconfigured or cannot actuate external commands.
Possible Causes
The board is faulty.
Procedure
Related Information
None
3.2.19 DBMS_ERROR
Description
Database error alarm. The alarm is generated when the database is in error.
3-114
Issue 08 (2011-10-30)
3 Alarm Processing
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 Parameter 1 Description Indicates the fault type of the alarm. For example: 0x05 denotes checking the head of standby areas in database have errors. 0x07 denotes checking the database of standby areas have errors. Parameter 2 Indicates the memory areas in database: 0x00 denotes FDB0; 0x01 denotes FDB1; 0x02 denotes DRDB. Parameter 3 Indicates the database ID: 0x00 denotes the whole memory made a mistake. 0x01-0xff denotes the database which made a mistake.

The configured data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l l l Operation to database fails. Data in the database is damaged. The board is faulty.
Procedure
Step 1 Fix the problem by periodically backing up the database. Check and test the database in backup area to ensure that the data in database is complete. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
None
3.2.20 DBMS_PROTECT_MODE
Description
Database in protect mode. The alarm is generated when the NE database is in the protection mode. Reported from the WDM side or client side: NA.
Attribute
Alarm Severity Critical Alarm Type Process alarm
Parameters
None

In the protection mode, the NE database cannot be backed up.
Possible Causes
l l The reset times of the SCC in five minutes exceeds the threshold value of the protection mode. The SCC issues a command to test the protection mode.
Procedure
Step 1 Check whether the NE database entering in the protection mode is caused by human factor. If that is the case, l l Perform a warm or cold reset on the SCC through the T2000. Release the protection mode. For details, see the Troubleshooting. Wait for 15 minutes. Release the protection mode after automatic reset.
Related Information
None
3 Alarm Processing
3.2.21 DCM_INSUFF
Description
Insufficient dispersion compensation margin. The alarm is generated when the dispersion compensation value gets close to the limits of the dispersion compensation margin.
Attribute
Parameters
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is generated. For example, 0x00 0x01 indicates channel 1 of the optical interface indicated by parameter 1. Parameter 4 Parameter 5 Indicates the dispersion compensation margin. The board is ps/nm. Indicates positive or negative dispersion compensation margin. The value 0x00 indicates positive dispersion compensation margin, and the value 0x01 indicates negative dispersion compensation margin.

The alarm does not affect the existing services. The alarm indicates that the system cannot meet the higher dispersion compensation requirements.
Possible Causes
The configuration of the DCM module is not correct or the DCM module is faulty.
Procedure
Step 1 Check whether there are OTU_LOF alarms on the T2000. If there are OTU_LOF alarms, clear the alarms according to the proper procedure.
3 Alarm Processing
Step 2 If there are no other alarms, query the dispersion compensation value of the board on the T2000. 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. 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
3.2.22 DSP_LOAD_FAIL
Description
DSP software loading failure. The alarm is generated when loading the DSP programme fails. Reported from the WDM side or client 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 Parameter 1 Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

Loading the DSP program to the board fails. As a result, the board cannot work normally, which has an influence on the services of users.
Possible Causes
3 Alarm Processing
Procedure
Step 1 Perform a warm reset on the faulty board through the T2000. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.23 EDFA_TEMP_OVER
Description
EDFA temperature exceeds the threshold. The alarm is generated when the actual temperature of the EDFA box exceeds the normal working temperature range by more than 5C.
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 Parameter 1 Description The value is always 0x01. There is no concept of optical interfaces.
Parameters 2 and 3 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The output optical power of the board decreases, the gain flatness is degraded and the system redundancy decreases. In a serious situation, the services have bit errors or even are interrupted.
Possible Causes
3 Alarm Processing
Procedure
Related Information
None
3.2.24 FAN_FAIL
Description
Fan failed alarm.
Attribute
Parameters
None

The fan is faulty. As a result, the temperature of the running boards are over high, which damages the boards.
Possible Causes
l l The speed level of fan is stop. The fan is unavailable.
Procedure
Step 1 Check whether the FAN Speed Level is configured to Stop or Low Speed through the T2000. If that is the case, set the FAN Speed Level to High Speed. Step 2 If the alarm persists, replace the faulty fan. For details, see the Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.25 FEC_LOF
Description
Received FEC is loss of frame. The alarm is generated when the FEC frame is lost. Reported from the WDM side or client side: WDM side.
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 Parameter 1 Description Indicates the port on the WDM side where the alarm is generated. The value is always 0x01.

The generation of the alarm affects the receiving of the services.
Possible Causes
l l l l The received signals have excessive attenuation. The signals transmitted by the WDM side of the opposite station do not have FEC frame structure. The board in the opposite station is faulty. The board at the local station is faulty.
Procedure
Step 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 T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_LOW alarm and the IN_PWR_HIGH alarm for troubleshooting. Step 2 Perform the hardware self-loop on the WDM side of the board in the opposite station. If the opposite station reports the alarm, remove the fault in the opposite station.
3 Alarm Processing
1. 2.
Check whether the board is forced to emit light. If yes, release the setting. Check whether the opposite station has the WDM-side inloop. If yes, release the loopback. If not, the board may be faulty. Replace the faulty board. For details, see Parts Replacement.
Step 3 If the opposite station does not report the alarm, the board at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.26 FEC_OOF
Description
Received FEC is out of frame. Reported from the WDM side or client side: WDM side.
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 Parameter 1 Description Indicates the port on the WDM side where the alarm is generated. The value is always 0x01.

The generation of the alarm affects the receiving of the services.
Possible Causes
l l
3-122
The received signals have excessive attenuation. The local station has the WDM-side inloop.
3 Alarm Processing
l l
The board in the opposite station is faulty. The board at the local station is faulty.
Procedure
Step 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 T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_LOW alarm for troubleshooting. Step 2 Perform the hardware self-loop on the WDM side of the board in the opposite station. If the opposite station reports the alarm, remove the fault in the opposite station. 1. 2. Check whether the board is forced to emit light. If yes, release the setting. Check whether the opposite station has the WDM-side inloop. If yes, release the loopback. If not, the board may be faulty. Replace the faulty board. For details, see Parts Replacement.
Step 3 If the opposite station does not report the alarm, the board at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
3.2.27 FIBER_CRITICAL
Description
The OTDR-tested fiber critical alarm. This alarm is generated when the attenuation of the fiber monitored by the OTDR is excessive and thus crosses the critical alarm threshold. Reporting to the WDM or client side: NA
Attribute
Parameters
Issue 08 (2011-10-30)
3-123
3 Alarm Processing
Description Indicates the optical interface where the alarm is generated. For example, 0x01 denotes optical interface 1.
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. For example, 0x00 0x01 denotes channel 1 of the optical interface indicated by parameter 1. Parameter 4 and 5 Indicates the distance when a fault is generated (unit: 10m)

Multiplexed signals in the main optical path might be interrupted.
Possible Causes
l l l The monitored fiber section is damaged. The monitored fiber section is cut. The board is faulty.
Procedure
Step 1 Compare the optical power of the board at the downstream station that the monitored fiber connects to with the history data. If the optical power decreases, a fault that the alarm indicates occurs in the fiber; proceed with step 2. If the optical power does not decrease, proceed with step 3. Step 2 Locate the fiber fault upon the fiber fault location displayed on OAMS. Eliminate influence of factors such as temperature, external force, and aging (if the fiber is permanently damaged physically, splice it; if the fiber is seriously aged, replace it) to ensure that the optical power of the board at the downstream station to which the monitored fiber connects is restored to the history normal value. Step 3 Retest the monitored fiber with the "roll call test" method in "by reference curve" mode (after the fiber fault is cleared, the monitored fiber must be retested in "by reference curve" mode to clear the alarm). Step 4 If the alarm persists, the alarm might be misreported. Perform a warm reset on the board. Step 5 If the alarm persists, perform a cold reset on the board. Step 6 If the alarm persists, the board might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.28 FIBER_MAJOR
Description
The OTDR-tested fiber major alarm. This alarm is generated in the tested fiber when any of the following conditions is met: l The difference between the fiber channel omnidistance transmission loss tested by the OTDR and that measured in the final acceptance test (or the raw data value) is a minimum of the omnidistance transmission loss threshold of the fiber major alarm. The loss in a newly added event crosses the loss threshold in a newly added event of fiber major alarm. The loss increase in an existing event crosses the loss threshold in an existing event of fiber major alarm.
l l
Reporting to the WDM or client 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 Parameter 1 Description Indicates the optical interface where the alarm is generated. For example, 0x01 denotes optical interface 1.
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. For example, 0x00 0x01 denotes channel 1 of the optical interface indicated by parameter 1. Parameter 4 and 5 Indicates the distance when a fault is generated (unit: 10m)

Multiplexed signals in the main optical path might be interrupted.
Possible Causes
l
Issue 08 (2011-10-30)
The monitored fiber section is damaged.

3 Alarm Processing
Procedure
Step 1 Determine whether the fault that the alarm indicates exists according to the optical power change of the board at the downstream station to which the monitored fiber is connected. Compare the optical power with the history data. If the optical power decreases, the fiber is faulty; proceed with step 2. If the optical power does not decrease, proceed with step 3. Step 2 Locate the fiber fault upon the fiber fault location displayed on OAMS. Eliminate influence of factors such as temperature, external force, and aging to ensure that the optical power of the board at the downstream station to which the monitored fiber connects is restored to the history normal value. Step 3 Retest the monitored fiber with the "roll call test" method in "by reference curve" mode (after the fiber fault is cleared, the monitored fiber must be retested in "by reference curve" mode to clear the alarm). Step 4 If the alarm persists, the alarm might be misreported. Perform a perform a warm reset on on the board. Step 5 If the alarm persists, perform a cold reset on the board. Step 6 If the alarm persists, the board might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.29 FIBER_MINOR
Description
The OTDR-tested fiber minor alarm. This alarm is generated in the tested fiber when any of the following conditions is met: l The difference between the fiber channel omnidistance transmission loss tested by the OTDR and that measured in the final acceptance test (or the raw data value) is a minimum of the omnidistance transmission loss threshold of the fiber minor alarm. The loss in a newly added event crosses the loss threshold in a newly added event of fiber minor alarm. The loss increase in an existing event crosses the loss threshold in an existing event of fiber minor alarm.
l l
Reporting to the WDM or client side: NA
3-126
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Parameters
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. For example, 0x00 0x01 indicates channel 1 of the optical interface indicated by parameter 1. Parameter 4 and 5 Indicates the distance when a fault is generated (unit: 10m)

Multiplexed signals in the main optical path might degrade.
Possible Causes
l l The monitored fiber section is damaged. The board is faulty.
Procedure
Step 1 Determine whether the fault that the alarm indicates exists according to the optical power change of the board at the downstream station to which the monitored fiber is connected. Compare the optical power with the history data. If the optical power decreases, the fiber is faulty; proceed with step 2. If the optical power does not decrease, proceed with step 3. Step 2 Locate the fiber fault upon the fiber fault location displayed on OAMS. Eliminate influence of factors such as temperature, external force, and aging to ensure that the optical power of the board at the downstream station to which the monitored fiber connects is restored to the history normal value. Step 3 Retest the monitored fiber with the "roll call test" method in "by reference curve" mode (after the fiber fault is cleared, the monitored fiber must be retested in "by reference curve" mode to clear the alarm).
3 Alarm Processing
Step 4 If the alarm persists, the alarm might be misreported. Perform a perform a warm reset on on the board. Step 5 If the alarm persists, perform a cold reset on the board. Step 6 If the alarm persists, the board might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.30 FPGA_ABN
Description
FPGA status is abnormal. The alarm is generated when the standby FPGA is currently used by the board.
Attribute
Parameters
None

The active FPGA file of the board is abnormal and the standby FPGA file is enabled. If the standby FGPA file is abnormal, the board cannot work, which has an influence on the services of users. The case needs to be handled in time.
Possible Causes
l l The active FPGA file is not existed when the board boots. Loading of the active FPGA file fails when the board boots.
Procedure
Step 1 Reload the FPGA file to the board. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.31 GAINDATA_MIS
Description
The GAINDATA_MIS is an alarm indicating mismatch of gain attribute. When the nominal gain value issued by the NE software falls beyond the tuning range of the nominal gain, the alarm is reported.
Attribute
Parameters
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. For example, 0x00 0x01 denotes channel 1 of the optical interface indicated by parameter 1. Parameter 4 Indicates that the gain is excessively high or low. The value 0x01 indicates that the gain is excessively low; the value 0x02 indicates that the gain is excessively high.

The service quality may be affected.
Possible Causes
l l l l The Raman board gain that is set is out of the permitted range. The insertion loss of the line changes. The optical power of the Raman board is manually locked. The laser on the Raman board is disabled.
Issue 08 (2011-10-30)
3-129
3 Alarm Processing
Procedure
Step 1 Query the threshold of the current actual nominal gain on the T2000. Reconfigure a valid nominal gain value for the optical interface channel of the unit based on the queried threshold. ----End
Related Information
None
3.2.32 HARD_BAD
Description
Hardware failure alarm. When the system detects a hardware failure, this alarm is reported. Reported from the WDM side or client side: NA
Attribute
Parameters
Parameter Parameter 1 Description Indicates the fault type of the alarm. For example, 0x06 denotes that the digital phase-locked loop is faulty. 0x0f denotes that the chip is faulty. 0x12 denotes that the clock components are faulty. 0x14 denotes that the power supply components are faulty. 0x15 denotes that other type of equipment is faulty. Parameters 2 and 3 Indicates the name of the faulty component. Different values denote different components.

The alarm affects the normal operating of the board and affects services.
Possible Causes
l l l
3-130
A clock relevant to services is faulty. The power supply is faulty. The board hardware is faulty.
3 Alarm Processing
Procedure
Step 1 Check whether the board is well seated. Step 2 If the alarm persists while the board is correctly and securely seated, replace the board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.33 HARD_FAIL
Description
Board failed alarm. The alarm is generated when the board failed.
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. None

The alarm affects the normal operating of the board and affects services.
Possible Causes
Procedure
Step 1 Replace the faulty board. For details see Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.34 INPWR_FAIL
Description
Input power failed. The alarm is generated when the power input is fault.
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 The power supply module number, For example, 0x01 denotes the power supply 1.

The power input of the system is affected, which leads to the function failure of the system.
Possible Causes
l l The input power is faulty. The PMU board for detection is faulty.
Procedure
Step 1 Replace the input power. For details, see the Parts Replacement. Step 2 If the alarm persists, the PMU might be fault. Replace the PMU. For details, see the Parts Replacement. ----End
Related Information
None
3-132
Issue 08 (2011-10-30)
3 Alarm Processing
3.2.35 J0_MM
Description
Trace indicator mismatch. The alarm is generated when the J0 byte received is not consistent with the J0 byte to receive. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

The services are not affected.
Possible Causes
l l The J0 byte is mismatched. The service connection is incorrect.
Procedure
Step 1 Check whether the J0 byte to transmit by the board in the opposite station is set to be consistent with that to receive by the board at the local station. If they are inconsistent, set the two to be consistent with each other. Step 2 If the alarm persists, bit errors may exist in the line. Refer to the handling procedure of the B1_SD or B2_SD alarm for troubleshooting.
3 Alarm Processing
Step 3 If the alarm persists, consider whether to replace the board or not according to the actual situation because that only the J0_MM alarm does not affect the services. For details, see the Troubleshooting. ----End
Related Information
None
3.2.36 K1_K2_M
Description
The K1 and K2 bytes mismatch alarm. This alarm is generated when K1 transmitted by an 1:N (N8) optical channel protection group mismatches K2 received. Reported from the WDM side or client side: NA.
Attribute
Parameters
None

1:N (N8) optical channel protection might fails. As a result, services fail to be protected.
Possible Causes
l l The configuration of 1:N (N8) optical channel protection at the local or opposite station is incorrect. The board at the local or opposite station is faulty.
Procedure
Step 1 Check the the configurations of 1:N (N8) optical channel protection at the local and opposite stations. Make sure that the two configurations are correct and consistent. Step 2 If the alarm persists, use a proper meter to test whether K1 transmitted by the board matches K2 received or not. If they mismatch each other, the board at the local or opposite station is faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.37 K2_M
Description
The K2 bytes mismatch alarm. This alarm is generated when K2 transmitted by an 1:N (N8) optical channel protection group mismatches K2 received. Reported from the WDM side or client side: NA.
Attribute
Parameters
None

1:N (N8) optical channel protection might fails. As a result, services fail to be protected.
Possible Causes
l l The configuration of 1:N (N8) optical channel protection at the local or opposite station is incorrect. The board at the local or opposite station is faulty.
Procedure
Step 1 Check the the configurations of 1:N (N8) optical channel protection at the local and opposite stations. Make sure that the two configurations are correct and consistent. Step 2 If the alarm persists, use a proper meter to test whether K2 transmitted by the board matches K2 received or not. If they mismatch each other, the board at the local or opposite station is faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.38 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.
3 Alarm Processing
Attribute
Alarm Severity Critical Alarm Type Service quality alarm
Parameters

When loss of synchronization occurs in the physical coding sublayer (PCS) of a receiving port, the port stops receiving data. Thus, the loss of synchronization alarm affects the quality of service (QoS). In this case, the service is interrupted.
Possible Causes
l l l l l Configuration of signal type or rate of the equipment at the local station and the opposite station are not consistent. Link failure. The equipment in the opposite station is faulty. The receive optical power of the local board is abnormal. The board at the local station is faulty.
Procedure
Step 1 Check whether the configuration of signal type or rate of the equipment at the local station and the opposite station are consistent. If they are not consistent, modify the setting to ensure the consistency. Step 2 If the alarm persists, check whether the fiber or cable that is used to connect between the 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. Step 3 If the alarm persists, check whether the data equipment in the opposite station is faulty. If that is the case, remove the fault of the data equipment in the opposite station.
3 Alarm Processing
Step 4 If the alarm remains, use the T2000 to check whether the receive optical power of the WDMside interface of the alarm-reporting board is in normal range. For optical power specifications of boards, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 5 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.39 LAN_LOC
Description
Ethernet communication failure. The alarm is generated when the external Ethernet communication and the network port fail.
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 Parameter 1 Meaning Indicates the network port ID. For example, 0x01 indicates network port 1 and 0x02 indicates network port 2.
Parameters 2 and 3 Indicates the number of the channel in which the alarm is generated. The value consists of two bytes and is always 0x00 0x01.

When the network port is faulty or there is a cut in the network cable, the communication at this network port fails. In this case, the communication between the NE and the T2000 stops.
Issue 08 (2011-10-30)
3-137
3 Alarm Processing
Possible Causes
l l l l The network port is required and is enabled on the T2000. However, the network cable is not connected to the network port or is inappropriately connected. The network port is not required but is enabled on the T2000. The network cable is faulty. The SCC board is faulty.
Procedure
Step 1 Query the alarm parameters on the T2000. Check whether the corresponding network port is required according to the alarm parameters. l IF the corresponding network port is not required, then disable the port on the T2000. l IF the corresponding network port is required, then check and ensure that the network cable is properly connected to the network port. Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable and re-connect it. Step 3 If the alarm persists, the SCC board may be faulty. In this case, replace the faulty board. For detailed operations, see Parts Replacement. ----End
Related Information
None
3.2.40 LASER_HAZARD_WARNING
Description
The Laser hazard warning alarm. This alarm is generated when the laser power is so high that it might cause personal injury if the IPA protection is not configured. The alarm is reported to prompt the user to configure the IPA protection.
Attribute
Parameters
3 Alarm Processing
Parameters 2 and 3 Indicates the channel where the alarm is generated, the value is always 0x00 0x01.

This alarm does not affect services; however, it might cause personal injury.
Possible Causes
l The laser power is high and the IPA protection is not configured.
Procedure
l Configure the IPA protection.
----End
Related Information
None
3.2.41 LOCK_CUR_FAIL
Description
Pump drive current unlocked alarm. The alarm is generated when the working current is abnormal.
Attribute
Parameters
Issue 08 (2011-10-30)
3-139
3 Alarm Processing
Parameters 2 and 3 Indicate the pump laser where the alarm is generated. For example, 0x00 0x01 indicates pump laser 1.

The locking of the output optical power of the board fails, which influences the services on the entire optical line.
Possible Causes
Procedure
Related Information
None
3.2.42 LSR_COOL_ALM
Description
Cooling current of the laser over threshold alarm. The alarm is generated when the refrigeration current of the laser on the WDM side exceeds the threshold. Reported from the WDM side or client side: WDM side
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,
3 Alarm Processing
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

When the refrigeration current of the laser exceeds the threshold, the optical module of the board works abnormally. As a result, services cannot be transmitted or received normally.
Possible Causes
Procedure
Related Information
None
3.2.43 LTEMP_OVER
Description
Laser temperature exceeds the threshold. The alarm is generated when the laser temperature of the board exceeds the threshold. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3 Alarm Processing
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is generated. For example, 0x00 0x01 indicates channel 1 of the optical interface indicated by parameter 1. Parameter 4 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The transmit function of the laser is influenced, which leads to the abnormal transmitted optical signals. As a result, the signals received by the downstream station are degraded or the signals are interrupted.
Possible Causes
l l The ambient temperature of the board is too high or too low. The board hardware is faulty.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of the specific board, see the Product Description. If the ambient temperature is too high, handle the alarm by referring to the handling procedure of the TEMP_ALARM alarm. Step 2 If the alarm persists, the board at the local station may be faulty. l l If the optical module is unpluggable, replace the faulty board. For details, see the Parts Replacement. If the optical module is pluggable, replace the faulty optical module or board. For details, see the Parts Replacement.
----End
Related Information
None
3.2.44 LTI
Description
All clock sources are lost. The alarm is generated when external clock source exists in the priority table but the board works in holdover or free running status.
3 Alarm Processing
Reported from the WDM side or client 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 Parameter 1 Parameters 2 and 3 Description The value is always 0x01. There is no concept of optical interfaces. The value is always 0x00 0x01. There is no concept of channels.

The services are not affected and no bit errors are generated.
Possible Causes
l l The board is faulty. The external clock, clock issued by the SCC and the local oscillator clock are lost.
Procedure
Step 1 If the external clock is lost, handle the alarm by referring to the handling procedure of the R_LOS alarm. Step 2 If the clock issued by the SCC is lost, check whether the SCC is faulty or the communication between the SCC and the board is normal. Step 3 If the local oscillator clock is lost, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
Issue 08 (2011-10-30)
3-143
3 Alarm Processing
3.2.45 MAIL_ERR
Description
Mail communication error. The alarm is generated when the communication between the board mailbox and the SCC is abnormal due to the hardware or software fault.
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 The slot ID of the board of which the mailbox is faulty. For example, 0x01 stands for slot 1.

l l If the SCC is abnormal, it cannot issue commands to all boards of the NE, which might affect the services. If the board indicated by the alarm is abnormal, the SCC cannot issue commands to the board, which might affect the services.
Possible Causes
l l The communication between the SCC and the mailbox on the backplane is abnormal. The communication between the board in the slot that the alarm information indicates and the mailbox on the backplane is abnormal.
Procedure
Step 1 Perform a warm reset on the SCC on the T2000. For details, see the Troubleshooting. Step 2 If the alarm persists, perform a warm reset on the board in the slot indicated by the alarm. For details, see the Troubleshooting. Step 3 If the alarm persists, reseat the board in the slot that the alarm information indicates. For details, see the Troubleshooting. Step 4 If the alarm persists, reseat the SCC board. For details, see the Troubleshooting. Step 5 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
3 Alarm Processing
Step 6 If the alarm persists, replace the SCC board. For details, see the Parts Replacement. Step 7 If the alarm persists, replace the subrack. ----End
Related Information
None
3.2.46 MOD_COM_FAIL
Description
Module communicates abnormally. 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
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 Parameter 1 Description The value is always 0x01. There is no concept of optical interfaces.
Parameters 2 and 3 Indicates the ID of the protection group in which the alarm is generated.

Because the communication between the CPU and other internal modules is interrupted, the related operations cannot be performed by using the T2000 and the performance information of each module cannot be queried.
Possible Causes
l l l
Issue 08 (2011-10-30)
The contact between the board and the connector of the optical module is poor. The software processing of the related modules of the board is faulty. The board hardware is faulty.
3 Alarm Processing
Procedure
Step 1 Check and ensure that the board and the optical module are connected properly. Step 2 Perform a cold reset on the faulty board by using the T2000 or remove the faulty board and insert it again. For details, see the Troubleshooting. Step 3 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
3.2.47 MODULE_COOLCUR_OVER
Description
Module cooling current exceeds the threshold. The alarm is generated when the refrigeration current of the module is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
3-146
Issue 08 (2011-10-30)
3 Alarm Processing

The working performance and the reliability of the module is affected. Generally the QoS is not affected. However, the QoS is affected if the alarm exists for a long time. The alarm should be handled in time.
Possible Causes
l l The temperature of the optical module is too high. The board hardware is faulty.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of the specific board, see the Product Description. If the ambient temperature is too high, handle the alarm by referring to the handling procedure of the TEMP_OVER alarm. Step 2 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
3.2.48 MODULE_TEMP_OVER
Description
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. Reported from the WDM side or client side: WDM side
Attribute
Parameters
Issue 08 (2011-10-30)
3-147
3 Alarm Processing

The working performance and the reliability of the module is affected. Generally the QoS is not affected. However, the QoS is affected if the alarm exists for a long time. The alarm should be handled in time.
Possible Causes
l l The ambient temperature of the board is too high or too low. The board hardware is faulty.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of the specific board, see the Product Description. If the ambient temperature is too high or too low, handle the alarm by referring to the handling procedure of the TEMP_OVER alarm. Step 2 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
3.2.49 MS_REI
Description
Multiplex section remote error indication. The alarm is generated when the remote end detects the bit error block. Reported from the WDM side or client side: WDM side, client side
3-148
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Alarm Severity Warning Alarm Type Service alarm
Parameters

Bit errors occur in transmission.
Possible Causes
l For the OTU board whose client side supports the SDH services, the input signals from the client side contain the MS_REI signal. As shown in the following figure, the input signals from the client side of the OTU board in station A (the local station) contain the MS_REI signals. The OTU of the station A reports the MS_REI alarm on the client side after it detects the MS_REI signals.
Detects and reports the MS_REI alarm
The client signals contain the MS_REI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The too low receive optical power in the opposite station due to the too low transmit optical power at the local station or faulty transmission line would lead to that the opposite station receives bit error blocks.
Issue 08 (2011-10-30)
3 Alarm Processing
As shown in the following figure:

Detects the B2 bit errors
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the MS_REI alarm
Station B Insert the MS_REI signal
Procedure
Step 1 Query which side reports the MS_REI alarm, l l If the client side reports the MS_REI alarm, remove the fault on the client-side equipment first. If the WDM side reports the MS_REI alarm, see step 2 to step 3.
Step 2 Check whether the transmit optical power at the local station is excessively low. For the optical power specifications of the specific board, see the Production Description. If the transmitting optical power at the local station is excessively low, replace the optical module or the faulty board. Step 3 If the alarm persists and the transmit optical power at the local station is normal, check whether the receive optical power in the opposite station is excessively low. If the receive optical power in the opposite station is excessively low, the transmission line might be faulty. Check the input and output optical power of the optical amplifier stations are normal according to the line connection. l l If the optical power is normal but bit errors still exist in the opposite station, replace the board in the opposite station. If the optical power is abnormal, locate the specific position and cause of the fault and then remove the fault.
----End
Related Information
None
3.2.50 MUT_TLOS
Description
Loss of the output multiplexed signals alarm. The alarm is generated when the output multiplexed signals of the board is lost. Reported from the WDM side or client side: NA
3 Alarm Processing
Attribute
Parameters

All services that pass through the board are interrupted.
Possible Causes
l l l The optical power is excessively low of the output port, maybe the input optical power of the add wavelength is excessively low. The attenuation of signals in line transmission is overlarge. The board is faulty.
Procedure
Step 1 Check whether the fiber connection is correct according to the engineering fiber connection diagram. The input optical signals in different wavelengths should be accessed to corresponding input optical interfaces of the board. If the fiber connection is incorrect, correct it according to the diagram. Step 2 If the alarm persists, measure the actual receive optical power of the board at the local station by using an optical power meter. Check whether the receive optical power or transmit optical power is within the normal range. For the optical power specifications of the specific board, see the Product Description. Step 3 If the receive optical power or transmit optical power of the board at the local station is excessively low, check whether there have MUT_LOS alarm at the local station,see the handling procedure of the SUM_INPWR_LOW or SUM_OUTPR_LOW alarm for troubleshooting. l
Issue 08 (2011-10-30)
If yes, see the handling procedure of the MUT_LOS alarm for troubleshooting.
3 Alarm Processing
If not, make sure that the input power of the added wavelength is normal.
Step 4 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
3.2.51 NESTATE_INSTALL
Description
NE is in install state, not configured. The alarm is generated when the NE is in the initial installing state.
Attribute
Parameters
None

l l The NM cannot query all configuration information about the NE. If the alarm is generated by the NE that is in normal running state, the data of the NM is initialized. You need to issue the correct configuration in time.
Possible Causes
l l The NE is in the initial installing state. The normal configuration is not performed to the NE after the NE is initialized.
Procedure
Step 1 Issue the configuration information to the NE by using the T2000. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.52 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 Parameter 1 Description 0x01 denotes the file in the flash memory. 0x02 denotes the current running software. Parameters 2 and 3 Indicates the ID of the file that does not comply with the SCC. Parameter 4 Indicates the alarm cause. 0x04 denotes that the file versions in the active and standby areas of a single SCC differ. 0x08 denotes that file versions of the active and standby SCCs differ, or there is no file with the same name under the corresponding directory of the opposite board. 0x0c denotes that the file versions in the active and standby areas of a single SCC differ; and the file versions of the active and standby SCCs also differ. Parameter 5 Indicates a value 0xff, which is not used at present.

The NE software cannot run or cannot perform the protection switching.
3 Alarm Processing
Possible Causes
l l l The software version currently running on the active SCC board is not consistent with that on the standby SCC board. 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. 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
Step 1 Update the NE software on the active or standby SCC board to ensure the version consistency. Step 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. Step 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
3.2.53 NO_BD_PARA
Description
No board parameter alarm. The alarm is generated when the board does not have the parameter table. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3-154
Issue 08 (2011-10-30)
3 Alarm Processing
Parameter
Description

The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l l l The correct parameter table is not loaded before delivery. The incorrect parameter table file is loaded on site, which overlaps the original file. The parameter table file is abnormally missing in running process.
Procedure
Related Information
None
3.2.54 NO_BD_SOFT
Description
No board software alarm. The alarm is generated when the board does not have the necessary files, for example, loading software, manufacturer information and logic software. Reported from the WDM side or client side: NA.
Attribute
Parameters
3 Alarm Processing
Description It is always 0x01.
Parameters 2 and 3 Indicates the ID of the lost file. For example, 0x00 0x01 denotes that the active board software is lost; 0x00 0x03 denotes that the FPGA file is lost; 0x00 0x05 denotes that the active ini file is lost; 0x00 0x07 denotes that the manufacturer information is lost.

The board does not have the desired files. The running file cannot be found when the board is reset. As a result, the normal function cannot be realized. The alarm must be cleared in time.
Possible Causes
l l l Parts of software are not loaded to the board. The software on the board is abnormally missing in the running process. The inside detection of the board is abnormal.
Procedure
Step 1 Reload the corresponding software through the T2000. Step 2 Perform a warm reset on the faulty board through the T2000. For details, see the Troubleshooting. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.55 OCH_FDI
Description
Forward defect indication at 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. Reported from the WDM side or client side: WDM side
Attribute
3-156
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters

If the logical fiber connection is wrong, there is no impact on services. Otherwise there might be impact on the services.
Possible Causes
The OCH_FDI-P and OCH_FDI-O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check whether there are the OTS_LOS, OTS_TIM, OTS_LOS-O or OMS_LOS-P alarms at the opposite station and all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-O or OMS_LOS-P alarms by following the proper handling procedures. ----End
Related Information
None
3.2.56 OCH_FDI-O
Description
Forward defect indication (overhead) at OCh layer. The OCH_FDI-O signal is inserted to the downstream station when the board at OTS layer detects the OTS_LOS-O signal and the alarm is generated when the downstream station receives the signals
Issue 08 (2011-10-30)
3-157
3 Alarm Processing
Attribute
Parameters
Name Parameter 1 Meaning Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

If the logical fiber connection is wrong, there is no impact on services. Otherwise there might be impact on the system monitoring and management.
Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The OCh layer receives the FDI-O overhead signal from the OCH layer, when the OMS lost overhead signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS-O alarm by following the proper handling procedures. ----End
Related Information
None
3.2.57 OCH_FDI-P
Description
Forward defect indication (payload) at OCh layer. The OCH_FDI-P signal is inserted to the downstream station when the board at OMS layer detects payload LOS signals and the alarm is generated when the downstream station receives the signals.
3 Alarm Processing
Attribute
Parameters

Possible Causes
the logical fiber connection is not consistent with the actual fiber connection. The OCh layer receives the FDI-O overhead signal from the OCh layer, when the OMS lost payload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check whether there are the OTS_LOS-P or OMS_LOS-P alarms at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarms by following the proper handling procedures. ----End
Related Information
None
3 Alarm Processing
3.2.58 OCH_LOS-P
Description
Loss of signal (payload) at OCh layer. The OTU detects LOS alarms and there is no OTS_LOSP, OMS_LOS-P or OMS_SSF-P alarm in the superstratum.
Attribute
Parameters

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The board detects no payload signals because of there is a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Confirm that the fiber connection between the OTU board that reports this alarm and the DEMUX board is correct. Step 3 If the alarm persists, check whether the output optical power at the OUT interface of the OTU board in the opposite or upstream station is normal or not. If not, clear the alarm according to
3 Alarm Processing
the procedure to handle the IN_PWR_HIGH or IN_PWR_LOW alarm to make the output optical power normal. Step 4 If the alarm persists, check whether the fiber at the OUT interface of the OTU board in the opposite or upstream station is disconnected from the MUX board or not. If yes, correctly connect the fiber between the two boards. Step 5 If the alarm persists,check whether the dispersion of the fiber is complied with the requirement or not. For the specifications of the dispersion, see the Product Description. If not, connect a suitable dispersion compensation module by referring to the Troubleshooting Step 6 Check whether there is R_LOS alarm, l l If yes, clear the alarm according to the procedure to handle R_LOS. If not, replace the faulty board by referring to the Troubleshooting.
----End
Related Information
None
3.2.59 OCH_OCI
Description
Open connection indication at OCh layer. No optical cross-connections are configured in the upstream service link, or no logical fiber connection is configured from the OTU board to the multiplex board. In this case, the OCI signal is inserted in the downstream service link. After receiving the OCI signal, the optical terminating node in the downstream reports the OCH_OCI alarm.
Attribute
Parameters
Issue 08 (2011-10-30)
3-161
3 Alarm Processing
Parameter
Description

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. No optical cross-connection for services to the local station is configured at the upstream station.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether the services of the optical cross-connections at the upstream station are configured. If no, re-configure the optical cross-connections to ensure the normal transmission of the services. ----End
Related Information
None
3.2.60 OCH_SSF
Description
Server signal fail at 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. Reported from the WDM side or client side: WDM side
Attribute
Parameters
3 Alarm Processing

Possible Causes
the logical fiber connection is not consistent with the actual fiber connection. The OTS-LOS alarm in the superstratum or The OMS-LOS alarm at OMS layer is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there are OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarms on the FIU connected to the local board, If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarms by following the proper handling procedures. Step 3 If the alarm persists, check whether there are the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarms 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 alarms by following the proper handling procedures. ----End
Related Information
None
3.2.61 OCH_SSF-O
Description
Server signal fail (overhead) at 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
3 Alarm Processing
Attribute
Parameters

Possible Causes
l The OCh layer receives the SSF-O overhead signal from the OMS layer, when the OTS lost overhead signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is OTS_LOS-O alarm on the FIU connected to the local board, If yes, clear the OTS_LOS-O alarm by following the proper handling procedure. Step 3 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS-O alarm by following the proper handling procedure. ----End
Related Information
None
3 Alarm Processing
3.2.62 OCH_SSF-P
Description
Server signal fail (payload) at OCh layer.
Attribute
Parameters

Possible Causes
The OCh layer receives the SSF-P overhead signal from the OMS layer, when the OMS lost payload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there are OTS_LOS-P or OMS_LOS-P alarms on the FIU connected to the local board, If yes, clear the OTS_LOS-P or OMS_LOS-P alarms by following the proper handling procedures.
Issue 08 (2011-10-30)
3-165
3 Alarm Processing
Step 3 If the alarm persists, check whether there are the OTS_LOS-P or OMS_LOS-P alarms at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarms by following the proper handling procedures. ----End
Related Information
None
3.2.63 ODU_LCK
Description
ODU locked. The alarm is generated when all signal values of the optical data unit (ODU) in the received optical transport network (OTN) services are 0x55. The alarm indicates that the upstream signal connection is locked and no signals passes. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

Possible Causes
l For the OTU board whose client side supports the OTN services, the input signals from the client side contain the ODU_LCK signal, as shown in the following figure.
3-166
3 Alarm Processing
The client-side input signals of the OTU in station A (local station) contains ODU_LCK signals. The OTU in station A reports the ODU_LCK alarm on the client side after detecting the ODU_LCK signals. At the same time the OTU transparently transmits the ODU_LCK signals to the station B (opposite station). The WDM side of the OTU in the station B reports the ODU_LCK alarm after detecting the ODU_LCK signals.
Detects and reports the ODU_LCK alarm Detects and reports the ODU_LCK alarm
The client signals contain the ODU_LCK signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The ODU_LCK signals are manually inserted to the OTU in the opposite station. As shown in the following figure: The ODU_LCK signals are manually inserted on the WDM side of the OTU in the station A (opposite station). The WDM side of the OTU in the station B (local station) reports the ODU_LCK alarm after detecting the ODU_LCK signals.
Manually insert the ODU_LCK signal Detects and reports the ODU_LCK alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A
Station B
Procedure
Step 1 Query which side reports the ODU_LCK alarm, l l If the client side reports the ODU_LCK alarm, remove the fault on the client equipment first. For details, see the related manuals. If the WDM side reports the ODU_LCK alarm, see step 2 to step 3.
Step 2 Query on the T2000 whether the corresponding client side of the OTU in the opposite station has the ODU_LCK alarm. If yes, remove the fault on the client equipment in the opposite station first. Step 3 Query on the T2000 whether the ODU_LCK signals are manually inserted to the OTU in the opposite station. If yes, release the ODU_LCK signals manually inserted. For details, see the Troubleshooting. ----End
3 Alarm Processing
Related Information
None
3.2.64 ODU_OCI
Description
ODU (Optical channel data unit) open connection indication. The alarm is generated when all signal values of the optical data unit (ODU) in the received optical transport network (OTN) services are 0x66. The alarm indicates that the output interface is not connected to the input interface of the upstream station. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

Possible Causes
l For the OTU board whose client side supports the OTN services, the input signals from the client side contain the ODU_OCI signal, as shown in the following figure. The client-side input signals of the OTU in station A (local station) contains ODU_OCI signals. The OTU in station A reports the ODU_OCI alarm on the client side after detecting the ODU_OCI signals. At the same time the OTU transparently transmits the ODU_OCI signals to the station B (opposite station). The WDM side of the OTU in the station B reports the ODU_OCI alarm after detecting the ODU_OCI signals.
Detects and reports the ODU_OCI alarm
3 Alarm Processing
Detects and reports the ODU_OCI alarm
The client signals contain the ODU_OCI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The ODU_OCI signals are manually inserted to the OTU in the opposite station. As shown in the following figure: The ODU_OCI signals are manually inserted on the WDM side of the OTU in the station A (opposite station). The WDM side of the OTU in the station B (local station) reports the ODU_OCI alarm after detecting the ODU_OCI signals.
Manually insert the ODU_OCI signal Detects and reports the ODU_OCI alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A
Station B
Procedure
Step 1 Query which side reports the ODU_OCI alarm, l l If the client side reports the ODU_OCI alarm, remove the fault on the client equipment first. For details, see the related manuals. If the WDM side reports the ODU_OCI alarm, see step 2 to step 3.
Step 2 Query on the T2000 whether the corresponding client side of the OTU in the opposite station has the ODU_OCI alarm. If yes, remove the fault on the client equipment in the opposite station first. Step 3 Query on the T2000 whether the ODU_OCI signals are manually inserted to the OTU in the opposite station. If yes, release the ODU_OCI signals manually inserted. For details, see the Troubleshooting. ----End
Related Information
None
3 Alarm Processing
3.2.65 ODU_TCMn_AIS
Description
ODU TCMn alarm indication signal. An AIS signal travels downstream, which indicates that a signal failure is detected in the upstream. n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters

The services borne by the optical interface would be unavailable.
Possible Causes
l l l Signals input from the client side contain ODU_TCMn_AIS signal. The corresponding board at the opposite end transmits the ODU_TCMn_AIS signals. The loopback or cross-connection is set on the upstream station; the FEC type is incorrectly configured.
Procedure
Step 1 Query whether there is alarm with higher severity on the board by using the T2000. If there is, handle the alarm with higher severity. Step 2 Query whether the alarm is reported from the client side. If that is the case, check the equipment on the client side.
3 Alarm Processing
Step 3 Query whether the ODU_PM_AIS, R_LOS or R_LOF alarm exists on the client side of the OTU board at the opposite end by using the T2000. If the alarm exists, check the equipment at the opposite end. Step 4 Query whether the loopback is set on the upstream station by using the T2000. If that is the case, release the loopback of the upstream station. Step 5 Check whether the upstream station has correct configuration of cross-connection and of FEC type. If the configuration is incorrect, modify the configuration. ----End
Related Information
ITU-T G.709
3.2.66 ODU_TCMn_BDI
Description
ODU TCMn backward defect indication. The alarm is generated when five consecutive BDI bytes in the TCMn overhead field are "1". n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters

Bit errors occur in the downstream station.
3 Alarm Processing
Possible Causes
l l Signals input from the client side contain ODU_TCMn_BDI signal. The corresponding OTU board in the downstream station receives the LOF, LOM, ODU_TCMn_AIS, ODU_TCMn_LCK, ODU_TCMn_LTC, ODU_TCMn_OCI, ODU_TCMn_SSF alarms.
Procedure
Step 1 Query whether there is alarm with higher severity on the board by using the T2000. If there is, handle the alarm with higher severity. Step 2 Query whether the alarm is reported from the client side or the WDM side, l l If the alarm is reported from the client side, check the equipment on the client side. If the alarm is reported from the WDM side, check whether the corresponding OTU board in the downstream station receives the LOF, LOM, ODU_TCMn_AIS, ODU_TCMn_LCK, ODU_TCMn_LTC, ODU_TCMn_OCI, ODU_TCMn_SSF alarms by using the T2000. If yes, handle the corresponding alarms in the downstream station.
----End
Related Information
ITU-T G.709
3.2.67 ODU_TCMn_BEI
Description
ODU TCMn section backward error indication. If the board detects that the input signals contain the BIP8 bit errors, it inserts the ODU_TCMn_BEI alarm back to the upstream board. The alarm is generated when the upstream station detects that the BEI flag in the OCH-OH of the TCMn section of the received signals is true. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3 Alarm Processing

The bit errors occur to the service signals, which influences the system quality.
Possible Causes
l Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side contain the ODU_TCMn_BEI signals, as shown in the following figure. The input signals on the client side of the OTU in the station A contain the ODU_TCMn_BEI signals. The OTU in the station A reports the ODU_TCMn_BEI alarm on the client side after detecting the ODU_TCMn_BEI signals and transparently sends the ODU_TCMn_BEI signals to the station B (opposite station) at the same time. The WDM side of the OTU in the station B reports the ODU_TCMn_BEI alarm after detecting the ODU_TCMn_BEI signals.
Detectsandreports the ODU_TCMn_BEI alarm Detects and reports the ODU_TCMn_BEI alarm
The client signals contain the ODU_TCMn_BEI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
l l
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for the alarm generated on the WDM side: The ODU-TCMn-BIP8 bit errors occur when the OTU in the opposite station receives the signals at the local station, as shown in the following figure. The WDM side of the OTU in the station B (opposite station) inserts the ODU_TCMn_BEI signals back to the station A (local station) after detecting the ODUTCMn-BIP8 bit errors. The WDM side of the OTU in the station A reports the ODU_TCMn_BEI alarm after detecting the ODU_TCMn_BEI signals.
Issue 08 (2011-10-30)
3-173
3 Alarm Processing
Detects the ODU_TCMn_BEI bit errors
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the ODU_TCMn_BEI alarm
Station B Insert the ODU_TCMn_BEI signal back
l l
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the ODU_TCMn_BEI signals back to the local station improperly. As shown in the following figure, the WDM side of the OTU in the station B (opposite station) inserts the ODU_TCMn_BEI signals back to the station A (local station) by mistake. The WDM side of the OTU in the station A reports the ODU_TCMn_BEI alarm after detecting the ODU_TCMn_BEI signals.
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the ODU_TCMn_BEI alarm
Station B Insert the ODU_TCMn_BEI signal by mistake
Procedure
l l Query the alarm on the T2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for the alarm generated on the client side: In the case of the OTU of which the client side supports the OTN services, the input signals on the client side contain the ODU_TCMn_BEI signals. 1. If the client side reports the ODU_TCMn_BEI alarm, check whether the client-side equipment connected to the OTU is faulty according to the related manuals. If yes, remove the fault of the client-side equipment by referring to the related manuals. If the alarm persists, perform a cold reset on the faulty board at the local station. If the alarm persists, replace the board that reports the alarm. For details, see Replacing a Board of the Supporting Tasks.
2. 3. l
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.
3-174
Issue 08 (2011-10-30)
3 Alarm Processing
1. 2. l
If the alarm persists, perform a cold reset on the faulty board at the local station through the T2000. If the alarm persists, the OTU at the local station may be faulty. Replace the faulty board.
Cause 1 for the alarm generated on the WDM side: The PM_BIP8 bit errors occur when the OTU in the opposite station receives the signals at the local station. 1. If the WDM side reports the PM_BEI alarm, check whether the ODU_TCMn_BEI bit error occurs when the OTU in the upstream station receives the signals at the local station. If yes, handle the alarm by referring to the handling procedure of the ODU_TCMn_EXC alarm.
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is faulty. 1. 2. If the alarm persists, perform a cold reset on the faulty board at the local station through the T2000. If the alarm persists, the OTU at the local station may be faulty. Replace the faulty board.
Cause 3 for the alarm generated on the WDM side: The board at the opposite station is faulty. It inserts the ODU_TCMn_BEI signals back to the local station improperly. 1. 2. If the alarm persists, perform a cold reset on the faulty board in the opposite station through the T2000. If the alarm persists, the OTU in the opposite station may be faulty. Replace the faulty board.
----End
Related Information
None.
3.2.68 ODU_TCMn_DEG
Description
ODU TCMn signal degraded. This alarm is generated when the BIP8 detection mode is bursty mode and the signal degradation or bit error count exceeds the threshold. n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
3 Alarm Processing

If the alarm is generated, the services borne by the optical interface would generate bit errors, which makes the service signals unavailable.
Possible Causes
l l l The optical interface at the local end is faulty. The optical interface at the opposite end is faulty. The fiber of the transmission line is abnormal.
Procedure
Step 1 Use the T2000 to browse alarm of the entire network to confirm the slot ID, interface ID, and channel ID of the board that generates this alarm. Step 2 Locate the point that first generates the ODUk_TCMn_DEG according to the service route. 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 T2000. For the optical power specifications of the specific board, see the Product Description. If not so, process it with the solution for IN_PWR_HIGH and IN_PWR_LOW. Step 4 If the alarm persists, check whether the fiber meets the following requirements: l The radius of the bending 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 requirement is not met, clean the fiber connector or replace the fiber. Step 5 If the alarm persists, the board might be faulty. Replace the faulty board. For details, see the Troubleshooting. ----End
Related Information
ITU-T G.709
3 Alarm Processing
3.2.69 ODU_TCMn_EXC
Description
ODU TCMn section BIP8 error cross the threshold. When the BIP8 detection mode is Poisson mode and the signal degradation or bit error count exceeds the threshold. n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters

The alarm has an influence on the QoS of the service signals.
Possible Causes
l l l The attenuation of the received signals is rather large, and the fiber of the transmission line is abnormal. The transmit part of the opposite station is faulty. The receive part of the local station is faulty.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using the T2000. For the optical power specifications of the specific board, 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.
3 Alarm Processing
Step 2 If the alarm persists, check whether the launched optical power of the corresponding interface on the upstream board is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the launched optical power of the board in the upstream station is excessively low, clear the alarm according to the handling procedure of the OUT_PWR_LOW alarm. Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using the T2000. Loop back the transmit optical interface and receive optical interface on the WDM side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault of the upstream station. Step 4 If the alarm persists, replace the faulty board on the local station. For details, see the Troubleshooting. ----End
Related Information
ITU-T G.709
3.2.70 ODU_TCMn_LCK
Description
ODU TCMn signal 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. n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
3-178
Issue 08 (2011-10-30)
3 Alarm Processing
Parameter
Description

Possible Causes
The signals are locked for the test of current line signals.
Procedure
Step 1 Use T2000 to query and locate the slot ID, interface ID, and channel ID of the board that generates this alarm. Step 2 Set the LCK type to be Disabled if it is Enabled. ----End
Related Information
ITU-T G.709
3.2.71 ODU_TCMn_LTC
Description
Loss of ODU TCMn serial connection. The TCM provides the connection monitoring function of the ODU to cater for the different applications. For example, the TCM from optical NNI to optical NNI monitors the connection through the carrier network of the ODU. The alarm is generated when the serial connection is lost and the STAT byte value is "000". n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
3 Alarm Processing

The tandem connection monitoring (TCM) is not available.
Possible Causes
The opposite end is not configured with TCM enabled, so there is no TCM source.
Procedure
Step 1 In the T2000, find the locate that generates this alarm first by the network figure. Step 2 Query whether this location and its opposite location are different in TCM source configuration. If so, modify the configuration. ----End
Related Information
ITU-T G.709
3.2.72 ODU_TCMn_OCI
Description
ODU TCMn open connection indication. The alarm is generated when the output interface is not connected to the input interface and the STAT byte value is "110". n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
3 Alarm Processing

Possible Causes
l l l The corresponding board in the upstream station has ODU_TCMn_OCI alarm. There is loopback in the corresponding board in the opposite station. The corresponding board in the opposite station has no or incorrect cross-connection configuration.
Procedure
Step 1 Query whether there is alarm with higher severity on the board by using the T2000. If there is, handle the alarm with higher severity. Step 2 If the alarm persists, check whether the upstream station has this alarm. If so, locate the station that triggers this alarm according to the service route. Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback. If so, cancel the loopback. Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is configured with incorrect or no cross-connection configuration. If so, configure the correct crossconnection. ----End
Related Information
ITU-T G.709
3.2.73 ODU_TCMn_SSF
Description
The ODU TCMn server signal failure alarm. n indicates the level of TCM and its value ranges from 1 to 6.
3 Alarm Processing
Attribute
Parameters

Possible Causes
l l l The ODU_TCMn_AIS or ODU_LOFLOM alarm is generated to the line. The OTUk_TIM alarm is generated to the line and the OTUk_TIM follow-up response is set to be enabled. The OTUk_SSF alarm is generated.
Procedure
Step 1 Check along the service signal flow to locate the station that first generates the SSF alarm. 1. 2. Check whether the ODU_PM_AIS or ODU_LOFLOM alarm has occurred in the station or not. If yes, clear the the alarm according to the corresponding handling procedure. Check whether the OTUk_TIM alarm has occurred in the station or not. If yes, clear the alarm according to the alarm handling procedure.
Step 2 If the alarm persists, check whether the OTUk_SSF alarm has occurred to the line or not. If yes, clear the alarm according to the alarm handling procedure. ----End
Related Information
None
3 Alarm Processing
3.2.74 ODU_TCMn_SD
Description
Optical channel data unit (ODU) layer TCMn section bit error degrade alarm. This alarm is generated when the detection board detects that the number of BIP8 check bit errors on section TCMn at the ODU layer exceeds the degrade threshold. Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Major Alarm Type Service
Parameters

The bit errors occur in the service signals, which influences the system quality.
Possible Causes
l l l l l In the case of the OTU board that supports the OTN service type, the client input signals contain excessive BIP8 bit errors on section TCM1. The input optical power is excessively high or low. The system performance degrades. For example, the optical signal-to-noise ratio (OSNR) is excessively low, or problems such as dispersion and nonlinearity occur in the system. The upstream board is faulty. The local board is faulty.
Issue 08 (2011-10-30)
3-183
3 Alarm Processing
Procedure
Step 1 In the case of the OTU board that supports the OTN service type, query on the T2000 whether the client input signals contain excessive BIP8 bit errors on section TCM1. If yes, remove the fault of the client equipment. Step 2 If the alarm persists, query on the T2000 the input optical power at each optical interface of the board. Check whether the input optical power at each optical interface is within the normal range. For the optical power specifications of the board, see the Product Description. If the input optical power at any optical interface is beyond the normal range, handle the alarm according to the method of handling the IN_PWR_HIGH or IN_PWR_LOW alarm. Step 3 If the alarm persists, see the description of bit error handling in the Troubleshooting. Step 4 If the alarm persists, the local board might be faulty. For details on how to replace the faulty board, see the Parts Replacement. Step 5 If the alarm persists, the upstream board might be faulty. For details on how to replace the faulty board, see the Parts Replacement. ----End
Related Information
None.
3.2.75 ODU_TCMn_TIM
Description
ODU TCMn TTI mismatch. This alarm is generated during control process when the trail trace identifier at the opposite end mismatches that at the local end while 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 l l For the point-to-point topology, only the source access point identifiers (SAPI) is compared for the sink of trail termination. For the point-to-multipoint topology, only the SAPI is compared for the sink of trail termination. For the multipoint-to-multipoint topology, only the destination access point identifiers (DAPI) is compared for the sink of trail termination.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
3-184
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters

If the alarm is generated, the signal quality of the services borne by the optical interface would be degraded. Hence, the service signals may be unavailable.
Possible Causes
l l l l The networking architecture and the TIM detection mode to configure are not consistent. The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to receive at the local end. The fiber connection is incorrect. The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the T2000. Select the suitable topology for the local end on the T2000 interface according to networking architecture. If the topology is a point-to-point one or point-to-multipoint one, only the SAPI is compared for the sink of trail termination. If the topology is multipoint-to-multipoint topology, only the DAPI is compared for the sink of trail termination. Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to receive at the local end through the T2000. If they are not consistent, query the TTI received on the T2000. Set the SAPI and the DAPI of the TTI to receive at the local end to be the same as these of the TTI received. Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber. Step 4 Check whether the cross-connection configuration is correct. If not, correctly configure the cross-connection. ----End
3 Alarm Processing
Related Information
ITU-T G.709
3.2.76 OMS_BDI
Description
Backward defect indication at 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

The incorrect logical fiber connection does not affect services; however, other errors interrupt the services of the system.
Possible Causes
The OMS_BDI-P and OMS_BDI-O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not, and query whether the fiber connection searching is right or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection.
3 Alarm Processing
Step 2 Check whether there are the OTS_LOS, OTS_LOS-O, OTS_TIM or OMS_LOS-P alarms at the opposite station and all downstream stations. If yes, clear the OTS_LOS, OTS_LOS-O, OTS_TIM or OMS_LOS-P alarms by following the proper handling procedures. ----End
Related Information
None
3.2.77 OMS_BDI-O
Description
Backward defect indication (overhead) at OMS layer. The OMS_BDI-O signal is inserted back to the upstream station when the downstream station receives no overhead signals from the upstream station and the OTS_LOS_O alarm is generated from the downstream station.
Attribute
Parameters

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
Issue 08 (2011-10-30)
3 Alarm Processing
cut, low optical power, or dispersion. This alarm is generated when the local station receives the BDI-O overhead signal. l The local station sends no overhead signals.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there are the OTS_LOS-O alarm at the opposite station and all downstream stations. If yes, clear the OTS_LOS-O alarm by following the proper handling procedures. ----End
Related Information
None
3.2.78 OMS_BDI-P
Description
Backward defect indication (payload) at 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
3-188
Issue 08 (2011-10-30)
3 Alarm Processing

Possible Causes
The downstream station inserts the BDI-P overhead signal back to the OMS layer of the local station, when the downstream station detects no payload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated when the local station receives the BDI-P overhead signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there are the OTS_LOS-P or OMS_LOS-P alarms at the opposite station and all downstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarms alarms by following the proper handling procedures. ----End
Related Information
None
3.2.79 OMS_FDI-O
Description
Forward defect indication (overhead) at OMS layer. The OMS_FDI-O signal is inserted to the downstream station when the board at OTS layer detects no overhead signals and can not send overhead signals to the downstream station.
Attribute
Parameters
Issue 08 (2011-10-30)
3-189
3 Alarm Processing

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The FDI-O overhead signal is inserted to the OMS layer of the downstream station, when the local station detects no overhead signals because of a fiber cut, low optical power, or dispersion. This alarm is generated when the downstream station receives the FDI-O overhead signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is the OTS_LOS-O alarm at all upstream stations. If yes, clear the OTS_LOS-O alarm by following the proper handling procedures. ----End
Related Information
None
3.2.80 OMS_FDI-P
Description
Forward defect indication (payload) at OMS layer. The OMS_FDI-P signal is inserted to the downstream station when the board at OTS layer detects no payload signals and can not send payload signals to the downstream station.
Attribute
3-190
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters

Possible Causes
The FDI-P signal is inserted to the OMS layer of the downstream station, when the local station detects no payload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated when the downstream station receives the FDI-P signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there are the OTS_LOS-P alarms at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P alarms by following the proper handling procedures. ----End
Related Information
None
3.2.81 OMS_LOS-P
Description
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.
Issue 08 (2011-10-30)
3-191
3 Alarm Processing
Attribute
Parameters
Parameter Parameter 1 Description Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The OMS layer detects no payload signals because of there is a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not, and query whether the fiber connection searching is right or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Confirm that the actual fiber connection between the board that reports this alarm and the FIU board is correct. Step 3 Check whether there is OTS_LOS alarm on the FIU, if yes, clear the alarm according to the procedure to handle OTS_LOS. Step 4 Check whether there is MUT_LOS alarm, l l If yes, clear the alarm according to the procedure to handle MUT_LOS. If not, replace the faulty board by referring to the Troubleshooting.
----End
Related Information
None
3 Alarm Processing
3.2.82 OMS_SSF
Description
Server signal fail at OMS layer. When the OMS_SSF-P and OMS_SSF-O alarms coexist, this alarm is generated. At the same time, the OMS_SSF-P and OMS_SSF-O alarms are suppressed.
Attribute
Parameters

Possible Causes
The OMS_SSF-P and OMS_SSF-O alarms are coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is OTS_LOS, OTS_TIM, OTS_LOS-P or OTS_LOS-O alarms on the FIU connected to the local board, If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P or OTS_LOSO alarms by following the proper handling procedure.
Issue 08 (2011-10-30)
3-193
3 Alarm Processing
Step 3 If the alarm persists, check whether there are the OTS_LOS, OTS_TIM, OTS_LOS-P or OTS_LOS-O alarms at all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOSP or OTS_LOS-O alarms by following the proper handling procedures. ----End
Related Information
None
3.2.83 OMS_SSF-O
Description
Server signal fail (overhead) at OMS layer. When the OTS layer detects the failure of the overhead signals or receives the OMS_FDI-O signal from the upstream station, this alarm is generated.
Attribute
Parameters

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. Because of a fiber cut, low optical power, dispersion, or failure in overhead signals on the upstream OTS layer, the FDI-O and SSF-O of the OMS layer are inserted into the
3-194
3 Alarm Processing
downstream station; or the overhead signals on the local OTS layer fail, and thus the OMS layer reports this alarm.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is 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 the proper handling procedure. Step 3 If the alarm persists, check whether there is the OTS_LOS-O or OOS_LOST alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS-O or OOS_LOST alarm by following the proper handling procedures. ----End
Related Information
None
3.2.84 OMS_SSF-P
Description
Server signal fail (payload) at OMS layer. When the OTS layer detects the failure of the payload signals or receives the OMS_FDI-P signal from the upstream station, this alarm is generated.
Attribute
Parameters
Issue 08 (2011-10-30)
3-195
3 Alarm Processing

Possible Causes
The OMS layer receives the SSF-P overhead signal from the OTS layer, when the OTS can not detect any signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is OTS_LOS-P alarm on the FIU connected to the local board, If yes, clear the OTS_LOS-P alarm by following the proper handling procedure. Step 3 If the alarm persists, check whether there are the OTS_LOS-P alarms at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P alarms by following the proper handling procedures. ----End
Related Information
None
3.2.85 OOS_LOST
Description
Loss of OOS (OTM overhead signal). When the local station receives no overhead signals in consecutive 10s and there is not OTS_LOS-O alarm, this alarm is generated.
Attribute
Parameters
3-196
Issue 08 (2011-10-30)
3 Alarm Processing

If the logical fiber connection is wrong, there is no impact on services. Otherwise there might be impact on the optical layer overhead.
Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The local station receives no overhead signals in consecutive 10s because of the opposite station sends no overhead signals.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection or not, and query whether the fiber connection searching is right or not. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether the opposite station supports the OLS function, l l If not, it is not needed to handle this alarm. If yes, make sure that the opposite station sends the correct overhead signals.
----End
Related Information
None
3.2.86 OPS_MAIN_BAK_ATTR_DIFF
Description
Attribute difference between working and protection channel. The alarm is generated when the port attribute configuration of the working and protection channels of the protection group is not consistent.
Attribute
Alarm Severity Critical
Issue 08 (2011-10-30)
Alarm Type Process alarm
3-197
3 Alarm Processing
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 Parameter 1 Description The protection type. For example, 0x03 stands for the 1+1 optical channel protection. 0x04 stands for the WXCP protection. Parameters 2 and 3 Indicates the ID of the protection group in which the alarm is generated. For example, 0x00 0x01 denotes protection group 1. Parameter 4 The mismatch type of the port attribute. For example, 0x00 stands for the auto-negotiation mismatch. 0x01 stands for the service type of the optical interface mismatch.

The services are unavailable after the protection switching is performed to the protection group.
Possible Causes
The port attribute configuration of the working and protection channels of the protection group is not consistent.
Procedure
Step 1 Check whether the port attribute configuration of the working and protection channels at the local station is consistent. If not, configure the port attribute of the working and protection channels again to ensure the consistency. Step 2 Check whether the port attribute configuration of the working and protection channels in the opposite station are consistent with that of the corresponding channels at the local station. If not, configure the port attribute of the working and protection channels again to ensure the consistency. ----End
Related Information
None
3-198
Issue 08 (2011-10-30)
3 Alarm Processing
3.2.87 OPS_PS_FAIL
Description
Failure of optical channel protection switching. The alarm is generated when the optical channel protection switching of the services 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 The protection type. For example, 0x03 stands for the 1+1 optical channel protection. 0x04 stands for the WXCP protection. Parameter 2 The ID of the protection group in which the alarm is generated. For example, 0x01 denotes protection group 1. Parameter 3 The unit ID of the protection group. For example, 0x00 stands for the protection unit. 0x01 stands for the working unit.

Services cannot be switched from the working channel to the protection channel, which leads to the service interruption.
Possible Causes
The OTU board is faulty.
Procedure
Step 1 Replace the faulty OTU board. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
None
3.2.88 OPS_PS_FIXED
Description
Alarm of optical channel protection switching. The alarm is generated when the protection switching state is changed to locked or forced switching whose priority is higher than autoswitching.
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 Parameter 1 Meaning The protection group type. For example, l 0x01 stands for the 1:N optical channel protection. l 0x02 stands for the clock protection. l 0x03 stands for the 1+1 optical channel protection. l 0x04 stands for the WXCP protection. l 0x07 stands for the inter-subrack 1+1 optical channel protection. l 0x11 stands for the optical line protection. Parameters 2 and 3 Indicates the ID of the protection group in which the alarm is generated. For example, 0x00 0x01 denotes protection group 1. Parameter 4 The unit ID of the protection group. For example, l 0x00 stands for the protection unit. l 0x01 stands for the working unit. Parameter 5 Indicates the current switching state of the protection group. For example, l 0x01 stands for the locked switching. l 0x02 stands for the forced switching.
3 Alarm Processing

The protection group does not initiate auto-switching in case of the SF or SD alarm, and thus the services are interrupted.
Possible Causes
l Cause 1: The protection switching state is changed to locked or forced switching.
Procedure
l l Query the alarm on the T2000 and record the type and ID of the protection group where the alarm is generated. Cause 1: The protection switching state is changed to locked or forced switching. 1. On the T2000 query the switching status of the protection group. If the switching status is in the locked switching or forced switching status, check whether the external switching is the need for normal working. If the external switching is the need for normal working, there is no need to handle the alarm. If the external switching is not the need for normal working, clear the external switching by issuing the clear switching command.
2. ----End
Related Information
3.2.89 OPUk_PLM
Description
OPUk payload mismatch. The type of received payload mismatches the expected payload type defined in the adaption function. k indicates the level of rate and its value is 2 and 3.
Attribute
Parameters
3 Alarm Processing

Possibly the services are not available.
Possible Causes
The setting of PT bytes to be received at the OPU layer of the local NE is different from the receive PT bytes at the OPU layer.
Procedure
Step 1 Check whether the payload type of the local board match that of the corresponding board of the opposite station. For the load type of the board, see the Hardware Description. If the load types of the boards do not match, replace one of them with the matched board. For details, see the Parts Replacement. Step 2 If the alarm persists, use the T2000 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 byte to be received at the OPU of the local board or the PT byte to be transmitted by the opposite NE.. ----End
Related Information
ITU-T G.709
3.2.90 OSC_RDI
Description
Remote defect indication. The alarm is generated when the opposite station call back the local station after receiving an R_LOF alarm. Reported from the WDM side or client side: NA.
Attribute
3-202
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters

The communication between the two stations is abnormal.
Possible Causes
l l l The opposite station receives the R_LOF signals. The optical fiber is damaged. The board is faulty.
Procedure
Step 1 Query whether the opposite station has the R_LOF alarm. If that is the case, take it as the R_LOF alarm for troubleshooting. Step 2 If the alarm persists, check whether the fiber between the two stations is damaged. If that is the case, repair the fiber. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.91 OTU_AIS
Description
OTU (optical transponder unit) alarm indication signal. The alarm is generated when the OTU board detects that all signals at the OTU layer of the input signals are abnormal. The alarm indicates that the signals at the OTU layer are faulty and the data borne is unavailable. Reported from the WDM side or client side: WDM side, client side
3 Alarm Processing
Attribute
Parameters

Possible Causes
l For the OTU board whose client side supports the OTN services, the input signals from the client side contain the OTU_AIS signals, as shown in the following figure. The input signals on the client side of the OTU in the station A (local station) contain the OTU_AIS signals. The OTU in the station A reports the OTU_AIS alarm on the client side after detecting the OTU_AIS signals.
Detects and reports the OTU_AIS alarm
The client signals contain the OTU_AIS signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The upstream signal source sends the OTU_AIS signals.
3-204
Issue 08 (2011-10-30)
3 Alarm Processing
Procedure
Step 1 If the client side reports the OTU_AIS alarm, remove the fault on the client equipment first. For details, see the related manuals. Step 2 If the WDM side reports the OTU_AIS alarm, remove the fault on the upstream signal source. ----End
Related Information
None
3.2.92 OTU_LOM
Description
Loss of Multi-frame. The alarm is generated when the MFAS values of the received signal frames are not successive. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

The services carried by this board may be unavailable.
Possible Causes
l
Issue 08 (2011-10-30)
The signals received by the OTU at the local station have excessive bit errors.
3 Alarm Processing
l l l
The board in the upstream station does not send the correct number of successive frames. The board at the local station is faulty. The board in the upstream station is faulty.
Procedure
Step 1 Check on the T2000 the BIP8 bit error performance value of the received signals of the board at the local station. If the BIP8 bit errors are excessive, handle the alarm by referring to the handling procedure of the SM_BIP8_OVER alarm. Step 2 If the alarm persists, check on the T2000 whether the OTU in the upstream station sends the correct number of successive frames. If not, cold reset the board in the upstream station. For details, see the Troubleshooting. Step 3 If the alarm persists, cold reset the faulty board at the local station through the T2000 or remove the faulty board and then insert it. For details, see the Troubleshooting. Step 4 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. Step 5 If the alarm persists, the board in the upstream station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
The value of the multi-frame alignment signal (MFAS) byte of the OTN frames sequently changes from "0000 0000" to "1111 1111" in all together 256 frames. The value of the MFAS byte in each OTUk/ODUk frame is larger than that of the preceding frame by one. Hence, 256 frames of multi-frame signals can be provided. The value of the MFAS byte must be compliant with the rule of increase by degrees.
3.2.93 OUT_PWR_LOW
Description
Output optical power too low alarm. The laser output optical power is excessively low. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3 Alarm Processing

The output optical power of the laser is excessively low, which influences the normal transmission of services.
Possible Causes
l l l The input optical power is excessively low. The laser is aged. The board is faulty.
Procedure
Step 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 T2000. For the optical power specifications of the specific board, see the Product Description. l l If it is not within the normal range, add a suitable attenuation to adjust the input optical power in the normal range. If it is within the normal range, replace the faulty optical module. For details, see the Parts Replacement.
Related Information
None
3.2.94 OUTPWR_FAIL
Description
Output power failed. The board regularly reads the AD value and calculates the voltage value by using a formula. An overvoltage or undervoltage alarm is generated when the board compares the calculated voltage with the threshold.
3 Alarm Processing
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 input power supply number. For example, 0x01 indicates power input 1 and 0x02 indicates power input 2.

The power input of other modules are affected, which leads to the functional faults of related modules.
Possible Causes
The power supply module is faulty.
Procedure
Step 1 Replace the faulty power module. For details, see the Parts Replacement. ----End
Related Information
None
3.2.95 PATCH_ACT_TIMEOUT
Description
Duration of patch package in activation state too long. The alarm is generated when the duration that the patch package is in the activation state exceeds the threshold.
Attribute
3-208
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters
None

There is no influence on the normal running of the system.
Possible Causes
The duration that the patch package is in the activation state exceeds the threshold.
Procedure
Step 1 If the patch file is confirmed to be correct, run the patch file through the T2000 after the end of the observation. Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the T2000. ----End
Related Information
None
3.2.96 PATCH_DEACT_TIMEOUT
Description
Duration of patch package in deactivation state too long. The alarm is generated when the duration that the patch package is in the deactivation state exceeds the threshold.
Attribute
Parameters
None

There is no influence on the normal running of the system.
Possible Causes
The patch package is in the deactivation state exceeds the threshold.
3 Alarm Processing
Procedure
Step 1 If the patch file is confirmed to be correct, activate the patch file through the T2000. Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the T2000. ----End
Related Information
None
3.2.97 PATCH_ERR
Description
Patch error alarm. The alarm is generated when the board detects the incorrect patch file.
Attribute
Parameters
None

The loaded patch cannot work normally. The problem to be solved by the patch remains in the system.
Possible Causes
If the patch is in the running status before NE reboots, the patch file is detected to be incorrect after NE reboots.
Procedure
Step 1 Obtain the correct patch file according to the Version Upgrade Guide and version mapping table, and then reload the correct patch file. ----End
Related Information
None
3 Alarm Processing
3.2.98 PATCH_NOT_CONFIRM
Description
Activated patch has not been confirmed overtime. The alarm is generated when the patch file is not confirmed five minutes after it is activated.
Attribute
Parameters
None

The activated status of the patch is the intermediate status for you observe the effect of the patch file. The status is used to remain the user to confirm the patch file, which has no influence on the normal running of the system.
Possible Causes
The patch file is not confirmed five minutes after it is activated.
Procedure
Step 1 If the patch file is confirmed to be correct, run the patch file through the T2000 after the end of the observation. Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the T2000. ----End
Related Information
The patch file is in the status for you observe the effect of the patch file after it is activated. When the alarm is generated, do not need to end the alarm immediately. Confirm the patch after the patch file is confirmed to be qualified. The alarm disappears if the activated status of the patch file is changed upon a command.
3.2.99 PATCHFILE_NOTEXIST
Description
Patch file not exist. The alarm is generated when the equipment detects that the patch file does not exist when it runs the patch file again.
3 Alarm Processing
Attribute
Parameters
None

The loaded patch cannot work normally. The problem to be solved by the patch remains in the system.
Possible Causes
If the patch is in the running status before NE reboots, the patch file is lost after the NE reboots.
Procedure
Step 1 Obtain the correct patch file according to the Version Upgrade Guide and version mapping table, and then reload the correct patch file. ----End
Related Information
None
3.2.100 PATH_VERIFY_ALM
Description
Consistency verification failure between the logical path dual-end configuration and the physical path fiber connection. That is, the 1:N optical path protection group checks the consistency between the logical path configuration and the physical path fiber connection. The alarm is generated when inconsistency is detected.
Attribute
3-212
Issue 08 (2011-10-30)
3 Alarm Processing
Parameters
Parameter Description Parameter 1 Indicates the protection group ID. For example, 0x01 indicates the protection group whose ID is 1. Parameter 2 Indicates the unit ID in the protection group at the local end. For example, l 0x00 indicates the protection path. l 0x01 to 0x08 indicates working paths. Parameter 3 Indicates the unit ID in the protection group at the opposite end. For example, l 0x00 indicates the protection path. l 0x01 to 0x08 indicates working paths.

The 1:N (N8) optical path protection may fail, and thus the services are not protected.
Possible Causes
The logical path configuration and the physical path fiber connection of the stations at the two ends of the 1:N (N8) optical path protection are inconsistent.
Procedure
Step 1 Check the configuration of the 1:N (N8) optical path protection at the local end and the opposite end. Ensure that the configuration at the two stations is correct and consistent. Step 2 Check the physical path fiber connection of the 1:N (N8) optical path protection. Ensure that the physical path fiber connection and the logical path configuration are consistent. Step 3 Perform another consistency check on the path protection parameters at the two ends. Make sure that the check succeeds and the configuration at the two ends is consistent. ----End
Related Information
None
3.2.101 PDU_OFF_ALM
Description
The power distribution unit (PDU) offline alarm. This alarm is generated when the PMU board detects that PDU1 or PDU2 is offline. Reported from the WDM side or client side: NA.
3 Alarm Processing
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 Parameter 1 Description Indicates the PDU ID. For example: l 0x01 denotes that PDU1 is offline. l 0x02 denotes that PDU2 is offline.

One power supply input is lost, which declines the reliability of the equipment power supplies.
Possible Causes
l l l A PDU is offline. The PMU board detection is incorrect. A PDU is faulty.
Procedure
Step 1 Check whether the PDU that the alarm indicates is correctly installed or not. If not, see the Power Box Guide to reinstall the PDU and correctly connect the cables and fibers. Step 2 If the alarm persists, check the status of the PDU indicators. l l If the status of the PDU indicators is abnormal, the PDU might be faulty. Replace the faulty PDU. For details, see the Troubleshooting. If the status of the PDU indicators is normal, the PDU detection might be incorrect. Perform a cold reset on the PDU. For details, see the Parts Replacement.
Step 3 If the alarm persists, replace the PMU board. For details, see the Parts Replacement. ----End
Related Information
Normally, the PDU running indicator (green) stays on and the PDU alarm indicator (red) stays off.
3 Alarm Processing
3.2.102 PM_BIP8_SD
Description
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. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters

The bit errors are generated in the service signals of the system, which influences the system quality.
Possible Causes
l l l l l
Issue 08 (2011-10-30)
For the OTU board whose WDM side supports the OTN services, the input signals on the WDM side have a great amount of BIP8 bit errors of the PM section. The input optical power is excessively high or low. The system performance declines. For example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or non-linearity occurs. The board in the opposite station is faulty. The board at the local station is faulty.
3 Alarm Processing
Procedure
Step 1 For the OTU board whose WDM side supports the OTN services, check on the T2000 whether the input signals on the WDM side have a great amount of BIP8 bit errors of the PM section. If yes, remove the fault on the WDM-side equipment. Step 2 Check whether the input optical power of the interface is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 3 If the alarm persists, see the Troubleshooting for handling the bit errors. Step 4 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see Parts Replacement. Step 5 If the alarm persists, the board in the opposite station may be faulty. Replace the faulty board. For details, see Parts Replacement. ----End
Related Information
None
3.2.103 PM_TIM
Description
ODU layer PM section TTI mismatch. The alarm is generated when the received TTI value of the PM section is not consistent with the TTI value to receive. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3-216
Issue 08 (2011-10-30)
3 Alarm Processing
Parameter
Description

The alarm has no impact on the system.
Possible Causes
l l l l The TTI bytes of the PM section to receive by the board at the local station is incorrectly configured. The TTI bytes of the PM section to be transmitted by the board in the upstream station is incorrectly configured. The fiber is incorrectly connected. Bit errors generated in transmission.
Procedure
Step 1 On the T2000, check whether the TTI bytes of the PM section to receive by the OTU at the local station is consistent with that to be transmitted by the OTU in the opposite station. If not, set the TTI byte to receive or to be transmitted again on the T2000 to ensure the consistency. Step 2 If the alarm persists, check whether the fiber is correctly connected according to the engineering fiber connection diagram. If not, connect the fiber again according to the fiber connection diagram. Step 3 If the alarm persists, bit errors may be generated in transmission. Clear it as the PM_BIP8_SD alarm for troubleshooting. ----End
Related Information
The alarm is used for monitoring the PM section of the OTN.
3.2.104 PORTSWITCH_FAIL
Description
Optical switch switching failure. This alarm is generated when the board detects that the optical switch inside the board fails to switch. Reported from the WDM side or client side: NA.
Issue 08 (2011-10-30)
3-217
3 Alarm Processing
Attribute
Parameters

When the MCA board reports this alarm, the spectrum analysis data at optical ports cannot be queried.
Possible Causes
Procedure
Step 1 Perform a cold reset on the faulty board by using the T2000 or remove the faulty board and insert it again. For details, see the Troubleshooting. Step 2 After the board is reset, re-command on the T2000 the MCA board to analyze the spectrum. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3-218
Issue 08 (2011-10-30)
3 Alarm Processing
3.2.105 POWER_DIFF_OVER
Description
Power difference between optical monitoring active and standby crossed the threshold. This alarm is generated when the optical power difference of signals in the active and standby supervisory channels exceeds the 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 Parameter 1 Description The optical power of one optical port is lower than that of the other optical port in the same group, and the difference between the optical power of both ports exceeds the alarm threshold. Example: Optical ports 1 and 2 are in the same group. l 0x01 indicates that the optical power of optical port 1 is lower than that of optical port 2. l 0x02 indicates that the optical power of optical port 2 is lower than that of optical port 1. Optical ports 3 and 4 are in the same group. l 0x03 indicates that the optical power of optical port 3 is lower than that of optical port 4. l 0x04 indicates that the optical power of optical port 4 is lower than that of optical port 3. Parameters 2 and 3 It is always 0x00 0x01.

The switching of the active and standby channels is affected. As a result, the quality of the received services would be affected.
Issue 08 (2011-10-30)
3-219
3 Alarm Processing
Possible Causes
l l 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. The optical power difference of signals in the active and standby channels when the board at the opposite end transmits signals is too large. The detection circuit of the board at the local end is faulty.
Procedure
Step 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. Step 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
3.2.106 PRIORITY_VERIFY_ALM
Description
Consistency verification failure of the path priority configuration between the two ends. That is, the 1:N optical path protection group checks the consistency of the path priority configuration between the two ends. The alarm is generated when inconsistency is detected.
Attribute
Parameters
Parameter Description Parameter 1 Indicates the protection group ID. For example, 0x01 indicates the protection group whose ID is 1. Parameter 2 Indicates the number of the path that is verified at the local end. For example, 0x01 indicates that working path 1 is verified at the local end. Parameter 3 Indicates the priority of the path that is verified at the local end. For example, 0x01 indicates that priority of the path verified at the local end is 1.
3-220
Issue 08 (2011-10-30)
3 Alarm Processing
Parameter Description Parameter 4 Indicates the number of the path that is verified at the opposite end. For example, 0x01 indicates that working path 1 is verified at the opposite end. Parameter 5 Indicates the priority of the path that is verified at the opposite end. For example, 0x01 indicates that priority of the path verified at the opposite end is 1.

The 1:N (N8) optical path protection may fail, and thus the services are not protected, or even are interrupted.
Possible Causes
The path priority configuration of the stations at the two ends of the 1:N optical path protection is not consistent.
Procedure
Step 1 Check the configuration of the 1:N optical path protection at the local end and the opposite end. Ensure that the path priority configuration at the two ends are correct and consistent. Step 2 Perform another consistency check on the path protection parameters at the two ends. Make sure that the check succeeds and the configuration at the two ends is consistent. ----End
Related Information
None
3.2.107 PRBS_LSS
Description
Loss of PRBS (Pseudo-Random Binary Sequence) signal. The alarm is generated when the board, on which the PRBS bit error test is started, does not receive the PRBS signals from the local board.
Attribute
Parameters
3 Alarm Processing

The PRBS test services on the board are interrupted.
Possible Causes
The link is abnormal. Hence, the board, on which the PRBS bit error test is started, does not receive the PRBS signals from the local board. The board is faulty, or the line is degraded.
Procedure
Step 1 Perform a selfloop by connecting the transmit end to the receive end of the PRBS signals on the local board. l l If the alarm is cleared, the board is normal. Refer to Step 2 to check the link. If the alarm persists, the board is faulty. Replace the board. For details, see the Parts Replacement.
Step 2 Check the link and make sure that the link under PRBS test is a loop. If the alarm persists, perform a loopback on each point of the link. Find out the abnormal point in the link, and remove the fault. ----End
Related Information
None
3.2.108 PUM_BCM_ALM
Description
Working current of pump laser over threshold. This alarm is generated when the pump laser bias current of the optical amplifier unit exceeds the threshold.
3-222
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Parameters
Parameters 2 and 3 Indicate the pump laser where the alarm is generated. For example, 0x00 0x01 indicates pump laser 1. Parameter 4 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The pump laser may be aged. Report of this alarm has no impact on the services. However, if no measure is taken, the output optical power of the board will be affected in a period of time. This affects services.
Possible Causes
l l The too high or too low ambient temperature affects the laser. The board is faulty.
Procedure
Step 1 Check whether the ambient temperature is normal. If not so, adjust the ambient temperature of the equipment to a proper degree. Step 2 If the alarm persists, perform a warm reset on the faulty board on the T2000. For details, see the Troubleshooting. Step 3 If the alarm persists, you can remove and reinsert the faulty board if it does not affect services. Step 4 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
3 Alarm Processing
Related Information
None
3.2.109 PUM_TEM_ALM
Description
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.
Attribute
Parameters
Parameters 2 and 3 Indicate the pump laser where the alarm is generated. For example, 0x00 0x01 indicates pump laser 1. Parameter 4 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The pump laser may be aged. Report of this alarm has no impact on the services. However, if no measure is taken, the output optical power of the board will be affected in a period of time. This affects services.
Possible Causes
l l l
3-224
The ambient temperature is too high or too low. The cooling system of the pump laser is damaged. The pump laser has excessive current.
3 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is normal. If not so, improve it. Step 2 If the alarm persists, perform a warm reset on the faulty board through the T2000. For details, see the Troubleshooting. Step 3 If the alarm persists, you can remove and reinsert the faulty board if it does not affect services. Step 4 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.110 PW_SWITCH_EX
Description
Backup power use alarm. The alarm is generated when the standby power supply is used. Reported from the WDM side or client 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 Parameter 1 Description The power supply number. For example, 0x01 indicates the 3.3 V power supply. 0x02 indicates the 5.0 V power supply. 0x03 indicates the -5.2 V power supply. Parameters 2 and 3 The value is always 0x00 0x01.
Issue 08 (2011-10-30)
3-225
3 Alarm Processing

The power supply reliability of the system decreases. The active power supply of the board fails and the power supply of the standby power supply board (PBU) is used. Clear the fault of the power supply or replace the faulty board in time.
Possible Causes
The power supply of the board is faulty.
Procedure
Step 1 On the T2000, check whether the board has the POWER_FAIL or W_R_FAIL alarm. If yes, handle the alarm by referring to the corresponding handling procedure. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.111 PWR_MAJ_ALM
Description
Abnormal power supply (severe overload or shortage). The alarm is generated when the voltage of the input power supply is excessively low or too high.
Attribute
Parameters
Parameter Parameter 1 Description Parameter 1 indicates the input power supply number. For example, 0x01 indicates the first power input. 0x02 indicates the second power input. Parameter 2 Parameter 2 indicates the power supply status. For example, 0x01 indicates undervoltage of the power supply. 0x02 indicates overvoltage of the power supply.
3-226
Issue 08 (2011-10-30)
3 Alarm Processing

The NE might be abnormally running, which leads to the service interruption.
Possible Causes
l l l l l The voltage of the input power supply is excessively low. The voltage of the input power supply is too high. There is no input voltage in the subrack. The PGND of the subrack and BGND of the power supply are not co-ground. The SCC is faulty.
Procedure
Step 1 Check whether the input power supply is correctly connected to the cabinet and subrack. If the input power supply is not correctly connected to the equipment, rectify the fault. For details, see the Installation Guide. Step 2 If the alarm persists, check whether the voltage of the input power supply is normal. If not, rectify the input voltage of the equipment power supply. Step 3 In the case of the PMU board, query the voltage of the first/second power supply on the T2000. If the voltage of the two power supplies are 79.6 V, it indicates that the PGND of the subrack and BGND of the power supply may be not co-ground. Make sure the PGND and BGND are co-ground. For details, see the Installation Guide. Step 4 If the alarm persists, replace the power supply, For details, see the Parts Replacement. Step 5 If the alarm persists, replace the SCC. For details, see the Parts Replacement. ----End
Related Information
None
3.2.112 PWR_MIN_ALM
Description
The power supply undervoltage or overvoltage minor alarm. This alarm is generated when the input power supply voltage is insufficient or excessive. Reported from the WDM side or client side: NA.
Attribute
Alarm Severity Minor Alarm Type Environment alarm
Issue 08 (2011-10-30)
3-227
3 Alarm Processing
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 input power supply ID. For example: l 0x01 denotes that power supply 1 is faulty. l 0x02 denotes that power supply 2 is faulty. Parameter 2 Indicates overvoltage or undervoltage of the power supplies. For example: l 0x01 denotes undervoltage of the power supplies. l 0x02 denotes overvoltage of the power supplies.

The NE operation might be faulty and services might be interrupted.
Possible Causes
The input power supply voltage is insufficient or excessive.
Procedure
Step 1 Check whether the equipment is correctly connected to the input power supplies or not. If not, correctly connect them. For details, see the Installation Guide. Step 2 If the alarm persists, check whether the input power supply voltage is normal or not. If not, adjust or replace the input power supplies to obtain the normal input voltage. ----End
Related Information
This alarm differs with PWR_MAJ_ALM in alarm severity; the threshold of the former is lower.
3.2.113 PWR_TEMP_OVERTH
Description
The power interface unit temperature overhigh alarm. This alarm is generated when the board detects that the power module temperature crosses the upper threshold.
3-228
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Alarm Severity Critical Alarm Type Equipment
Parameters
Parameters Description Parameter 1 Indicates the input power supply ID. For example, 0x01 denotes power supply 1.

The board in the subrack might report an alarm against temperature and unstably operates.
Possible Causes
l l l The power module is faulty. The fan is faulty. The board ambient temperature is overhigh.
Procedure
Step 1 Check the power module and fan in the subrack. If any of them is faulty, remove the fault. Step 2 If the alarm persists, check the board ambient temperature. If the board ambient temperature is overhigh, condition it to a proper degree. Step 3 If the alarm persists, the board might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.114 R_LOC
Description
Loss of clock on receiving line. This alarm occurs when the clock signal fails to be extracted from received signals. Reported from the WDM side or client side: WDM side
3 Alarm Processing
Attribute
Parameters

Carried service at this port is interrupted.
Possible Causes
l l l The link is abnormal and the board cannot normally extract clock signals. The setting of board clock tracing is incorrect. The board is faulty.
Procedure
Step 1 Check whether the physical link is normal. If there is any abnormity, such as OTU_LOF, SM_BIP8_OVER, remove the fault. Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the entire network planning. Adjust the board clock setting if it is incorrect. Step 3 If the alarm persists, replace the faulty board. For details, refer to the Parts Replacement. ----End
Related Information
None
3 Alarm Processing
3.2.115 REAR_BD_OFFLINE
Description
Offline of DPFU board. The alarm is generated when the rear board is offline.
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 Parameter 1 Description The board number generating the alarm. For example, 0x01: AUX board (interface board); 0x02: PBU board (standby power supply unit); 0x03: DPFU1 board (power filter unit 1); 0x04: DPFU2 board (power filter unit 2). Parameters 2 and 3 Parameters 4 and 5 The value is always 0xff 0xff. These two parameters are reserved. The value is always 0xff 0xff. These two parameters are reserved.

None
Possible Causes
Board offline.
Procedure
Step 1 Check whether the corresponding board is inserted. l l If no corresponding board exists, insert the corresponding board. If the corresponding board exists, check whether the board is well inserted. If not, remove and then insert the board again.
Issue 08 (2011-10-30)
3 Alarm Processing
Related Information
None
3.2.116 RELAY_ALARM
Description
PMU relay alarm. The alarm is generated when the equipment for external alarm input has any 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 Parameter 1 The housekeeping number where the alarm is generated. For example, 0x01 0x0f respectively stand for the 116 alarm inputs.

The equipment for external alarm input might be running abnormally.
Possible Causes
l l The trigger condition for housekeeping is incorrectly configured. The alarm is generated to the equipment for external alarm input.
Procedure
Step 1 When the alarm input is for external alarm input, check whether the trigger condition for alarm input is correctly configured.
3 Alarm Processing
Step 2 Check whether the housekeeping setting of the client-side equipment is the same as that of the equipment at the local station. If not, modify the housekeeping setting of the client-side equipment or the equipment at the local station. Step 3 Check whether the external equipment for alarm input is normally running. If not, remove the fault on the external equipment. ----End
Related Information
None
3.2.117 REM_SD
Description
Remote signal degraded alarm. This alarm is generated when the remote end received signals degrade. Reported from the WDM side or client side: client side
Attribute
Parameters

The QoS of the service signals is affected. In a serious situation, the services are interrupted.
3 Alarm Processing
Possible Causes
l l The client side of the OTU at the opposite end has alarm such as B1_EXC. Demultiplexed client signals on a WDM side of the OTU at the local end has alarm such as B1_EXC.
Procedure
Step 1 Check whether OTU at the opposite end have the B1_EXC alarm or not. If yes, see the procedure of handling B1_EXC to handle the alarm. Step 2 If the alarm persists, check whether demultiplexed client signals on the WDM side of the OTU at the local end have the B1_EXC alarm. If yes, see the procedure of handling B1_EXC to handle the alarm. ----End
Related Information
None
3.2.118 RL_CRITICAL_HI
Description
Critical high return loss alarm. This alarm is generated when the return loss is higher than the upper threshold of the return loss alarm.
Attribute
Parameters
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. For example, 0x00 0x01 denotes channel 1 of the optical interface indicated by parameter 1.
3-234
Issue 08 (2011-10-30)
3 Alarm Processing

This alarm is generated in case of a fiber connection error. When this alarm is generated, services may be interrupted.
Possible Causes
l l l l The fiber near the Raman board is broken. The fiber near the Raman board is over-bent or pressed. The connector of the fiber near the Raman board is unclean. The connector of the fiber near the Raman board is installed incorrectly.
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether the fiber near the Raman board is properly connected. If not, reconnect it. Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If yes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by means of splicing. Step 3 If the alarm still persists, check whether the end face of the fiber near the Raman board is clean. If not, clean it again and then connect the fiber properly. ----End
Related Information
None
3.2.119 RL_CRITICAL_LOW
Description
Critical low return loss alarm. This alarm is generated when the return loss is lower than the lower threshold of the return loss alarm.
Attribute
Parameters
3 Alarm Processing
Description Indicates the optical interface where the alarm is generated. For example, 0x01 denotes optical interface 1.
Parameters 2 and 3 Consists of two bytes, indicates the channel where this alarm is generated. For example, 0x00 0x01 denotes channel 1 of the optical interface indicated by parameter 1.

This alarm is generated in case of a fiber connection error. When this alarm is generated, services may be interrupted.
Possible Causes
l l l l The fiber near the Raman board is broken. The fiber near the Raman board is over-bent or pressed. The connector of the fiber near the Raman board is unclean. The connector of the fiber near the Raman board is installed incorrectly.
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether the fiber near the Raman board is properly connected. If not, reconnect it. Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If yes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by means of splicing. Step 3 If the alarm still persists, check whether the end face of the fiber near the Raman board is clean. If not, clean it again and then connect the fiber properly. ----End
Related Information
None
3.2.120 RMON_ALM_ALIGNMENT_OVER
Description
Alignment errors is over the upper threshold. The alarm is generated when the number of alignment error packets detected by the Ethernet port crosses the upper threshold. Reported from the WDM side or client side: client side
3-236
Issue 08 (2011-10-30)
3 Alarm Processing
Attribute
Parameters

Possible Causes
l l l l l The data equipment on the client side is faulty. As a result, the data sent includes a great amount of alignment error packets. The too high or too low input optical power leads to the generation of alignment error packets at the receive end. The optical interface modes (and the fiber modes) of the two connected Ethernet ports are not consistent. The fiber is damaged or the fiber connector is dirty. The board at the local station is faulty.
Procedure
Step 1 Check whether the input optical power of the Ethernet port is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 2 If the alarm persists, check whether the optical interface mode (and the fiber mode) of the two connected Ethernet ports are consistent. If they are not consistent, replace the fiber or board to ensure that the optical interface mode and the fiber type of the two Ethernet ports are consistent.
3 Alarm Processing
Step 3 If the alarm persists, check whether the data equipment on the client side is normal. If it is abnormal, remove the fault of the data equipment on the client side. Step 4 If the alarm persists, check the fiber connector between the client-side data equipment and the corresponding optical interface of the OTU. If it is dirty, clean or replace the fiber connector. For details, see the Troubleshooting. Step 5 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.121 RMON_ALM_DROPEVENT_OVER
Description
Statistics of drop packet events is over the upper threshold. The alarm is generated when the number of the drop packets crosses the upper threshold due to the cache memory overflow of the Ethernet port. Reported from the WDM side or client side: client side
Attribute
Parameters

3 Alarm Processing
Possible Causes
Procedure
Step 1 Replace the faulty board. For details see Parts Replacement. ----End
Related Information
None
3.2.122 RMON_ALM_FCSERROR_OVER
Description
Statistics of check errors is over the upper threshold. The alarm is generated when the number of CRC error packets detected by the Ethernet port crosses the upper threshold. Reported from the WDM side or client side: client side
Attribute
Parameters

3 Alarm Processing
Possible Causes
l l l l l The data equipment on the client side is faulty. As a result, the data sent includes a great amount of CRC error packets. The too high or too low input optical power leads to the generation of CRC error packets at the receive end. The optical interface modes (and the fiber modes) of the two connected Ethernet ports are not consistent. The fiber is damaged or the fiber connector is dirty. The board at the local station is faulty.
Procedure
Step 1 Check whether the input optical power of the Ethernet port is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 2 If the alarm persists, check whether the optical interface mode (and the fiber mode) of the two connected Ethernet ports are consistent. If they are not consistent, replace the fiber or board to ensure that the optical interface mode and the fiber type of the two Ethernet ports are consistent. Step 3 If the alarm persists, check whether the data equipment on the client side is normal. If it is abnormal, remove the fault of the data equipment on the client side. Step 4 If the alarm persists, check the fiber connector between the client-side data equipment and the corresponding optical interface of the OTU. If it is dirty, clean or replace the fiber connector. For details, see the Troubleshooting. Step 5 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
The abnormal data packets include: l l l l l ethunder, the excessively short packet that is less than 64 octets. ethover, excessively long packet whose length exceeds the set maximum length. ethfrg, fragment that is less than 64 octets and with the CRC error packets. ethjab, ambiguous packet that is excessively long and with CRC error packets. ethfcs, CRC error packets.
3.2.123 RMON_ALM_INBADOCTS_OVER
Description
Statistics of receiving bad packets is over the upper threshold. The alarm is generated when the octet number of bad packets detected by the Ethernet port of the board crosses the upper threshold. Reported from the WDM side or client side: client side
3 Alarm Processing
Attribute
Parameters

Possible Causes
l l l The data equipment on the client side sends the abnormal data packets. The abnormal link between the client side and the Ethernet port on the board leads to the error of the data packets in transmission. The faulty board leads to the regeneration of the signals or detection error.
Procedure
Step 1 Check whether the data equipment on the client side is normal. If it is abnormal, remove the fault of the data equipment on the client side. Step 2 If the alarm persists, check whether the link between the client side and the Ethernet port on the board is normal. 1. Check whether the optical interface mode (and the fiber mode) of the two connected Ethernet ports are consistent. If they are not consistent, replace the fiber or board to ensure that the optical interface mode and the fiber type of the two Ethernet ports are consistent. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details, see the Troubleshooting. Check whether the transmitting/receive optical power of the two connected Ethernet ports is within the normal range. For the optical power specifications of the specific board, see
2. 3.
Issue 08 (2011-10-30)
3 Alarm Processing
the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 3 If the alarm persists, perform a warm reset on the faulty board through the T2000. For details, see the Troubleshooting. ----End
Related Information
3.2.124 RMON_ALM_OUTBADOCTS_OVER
Description
Statistics of receiving bad packets is over the upper threshold. The alarm is generated when the number of bad packets detected by the Ethernet port of the board crosses the upper threshold. Reported from the WDM side or client side: client side
Attribute
Parameters
3-242
Issue 08 (2011-10-30)
3 Alarm Processing

Possible Causes
l l The signals received on the WDM side of the board have the B1 or B2 bit errors. Bad packets are generated during signal processing due to the faulty board.
Procedure
Step 1 Check whether the signals received on the WDM side have the B1 or B2 bit errors. If yes, handle the alarm by referring to the handling procedure of the B1_EXC or B2_EXC alarm. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
3.2.125 S1_SYN_CHANGE
Description
Synchronous source changed in S1 mode. Reported from the WDM side or client side: WDM side
Attribute
Parameters
3 Alarm Processing
Parameter Parameter 1 Parameters 2 and 3
Description The value is always 0x01. There is no concept of optical interfaces. The value is always 0x00 0x01. There is no concept of channels.

The switching performs to the working clock source of the board, which influence the user services.
Possible Causes
l l The fiber connection is faulty. The upstream station generates the alarm.
Procedure
Step 1 Check whether the WDM side of the upstream station has the alarm. If yes, clear the alarms on the upstream station. Step 2 Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details, see the Troubleshooting. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.126 SCC_LOC
Description
SCC loss of clock. The alarm is generated when the OSC board detects that the clock source sent by the SCC board is missing.
Attribute
Parameters
3 Alarm Processing
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Parameters 2 and 3 Description The value is always 0x01. There is no concept of optical interfaces. The value is always 0x00 0x01. There is no concept of channels.

The NE is out of control and the optical supervisory channel is interrupted.
Possible Causes
l l l The board is faulty. The SCC board is faulty. The alarm is generated during the cold reset of the SCC board. The alarm automatically disappears after the cold reset is complete.
Procedure
Step 1 Query the reset record of the SCC board. l l If the time when the alarm disappears is consistent with the time that the SCC is reset, the alarm might be caused by resetting the SCC. There is no need to handle the alarm. If the time when the alarm disappears is not consistent with the time that the SCC is reset, the board might be faulty. Replace the faulty board. For details, see the Parts Replacement.
Step 2 If the alarm persists, the SCC board might be faulty. Replace the faulty SCC board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.127 SM_BDI
Description
OTU SM section backward defect indication. The alarm is transferred in the upstream direction of the services, indicating the detected signal failure. Reported from the WDM side or client side: WDM side, client side
Issue 08 (2011-10-30)
3-245
3 Alarm Processing
Attribute
Parameters

Service carried by the board is interrupted.
Possible Causes
l For the OTU whose client side supports the OTN services, the input signals on the client side contain the SM_BDI signals, as shown in the following figure. The input signals on the client side of the OTU in the station A contain the SM_BDI signals. The OTU in the station A reports the SM_BDI alarm on the client side after detecting the SM_BDI signals and transparently sends the SM_BDI signals to the station B (opposite station) at the same time. The WDM side of the OTU in the station B reports the SM_BDI alarm after detecting the SM_BDI signals.
Detects and reports the SM_BDI alarm Detects and reports the SM_BDI alarm
The client signals contain the SM_BDI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The R_LOS, OTU_LOF or OTU_AIS alarm is generated when the WDM side of the OTU in the opposite station receives the signals at the local station.
3-246
3 Alarm Processing
As shown in the following figure: The WDM side of the OTU in the station B (opposite station) detects and reports the R_LOS, OTU_LOF or OTU_AIS alarm, it inserts the SM_BDI signals back to the local station. The WDM side of the OTU in the station A reports the SM_BDI alarm after detecting the SM_BDI signals.
Detects and reports the R_LOS, OTU_LOF, OTU_AIS alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the SM_BDI alarm
Station B Insert the SM_BDI signal back
l l
The board at the local station is faulty. The board in the opposite station is faulty. It inserts the SM_BDI signals back to the local station by mistake. As shown in the following figure: The WDM side of the OTU in the station B (opposite station) inserts the SM_BDI signals back to the station A (local station) by mistake. The WDM side of the OTU in the station A reports the SM_BDI alarm after detecting the SM_BDI signals.
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the SM_BDI alarm
Station B Insert the SM_BDI signal by mistake
Procedure
Step 1 If the client side reports the SM_BDI alarm, check whether the client-side equipment connected to the OTU is faulty according to the related manuals. If yes, remove the fault of the client-side equipment by referring to the related manuals. Step 2 If the alarm persists, perform a cold reset on the faulty board through the T2000 or reseat the faulty board. For details, see the Troubleshooting. Step 3 If the alarm persists, the board at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement.
Issue 08 (2011-10-30)
3-247
3 Alarm Processing
Step 4 If the WDM side reports the SM_BDI alarm, check whether the R_LOS, OTU_LOF or OTU_AIS alarm is generated when the OTU in the opposite station receives the signals at the local station. If yes, handle the alarm by referring to the corresponding handling procedure. Step 5 If the alarm persists, perform a cold reset on the faulty board through the T2000 or reseat the faulty board. For details, see the Troubleshooting. Step 6 If the alarm persists, the OTU at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement. Step 7 If the alarm persists, the OTU in the opposite station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.128 SM_BIP8_SD
Description
OTU layer, SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section in the optical channel data unit layer exceeds the degraded threshold. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3-248
Issue 08 (2011-10-30)
3 Alarm Processing

The service signals borne by the wavelength generate a great amount of bit errors. The signals are degraded.
Possible Causes
l For the OTU board whose client side supports the OTN services (For example, ETMX, LBF), the input signals from the client side contain a great amount of BIP8 bit errors of the SM section. The input optical power is excessively high or low. The system performance declines. For example, the optical signal to noise ratio (OSNR) is excessively low, or dispersion or non-linearity occurs. The board in the opposite station is faulty. The board at the local station is faulty.
l l l l
Procedure
Step 1 For the OTU board whose client side supports the OTN services, check on the T2000 whether the input signals on the client side has a great amount of BIP8 bit errors of the PM section. If yes, remove the fault on the client-side equipment. Step 2 If the alarm persists, Check whether the input optical power of the interface is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 3 If the alarm persists, see the description on bit error fault handling in the Troubleshooting. Step 4 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. Step 5 If the alarm persists, the board in the opposite station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.129 SM_IAE
Description
OTU layer, SM section incoming alignment error. When the board detects the slip frame, it inserts the SM_IAE flag to the downstream board. The alarm is generated when the downstream board detects that OTN frames received contains the IAE flag. Reported from the WDM side or client side: WDM side, client side
Issue 08 (2011-10-30)
3-249
3 Alarm Processing
Attribute
Parameters

Generally the services are not affected. If the slip frame problem is severe, the bit errors might occur to the services.
Possible Causes
l For the OTU board whose client side supports the OTN services (For example, ETMX, LBF), the input signals from the client side contain the SM_IAE signal, as shown in the following figure. The client-side input signals of the OTU in station A (local station) contains SM_IAE signals. The OTU in station A reports the SM_IAE alarm on the client side after detecting the SM_IAE signals.
Detects and reports the SM_IAE alarm
The client signals contain the SM_IAE signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
The slip frame occurs to the client-side signals of the OTU in the opposite station, insert SM_IAE signals to the local station, as shown in the following figure.
3-250
Insert the SM_IAE signal The client signals have the slip frame Client side O T U WDM side WDM side
3 Alarm Processing
Detects and reports the SM_IAE alarm
O T U
Client side
Station A
Station B
l l
The board at the local station is faulty. The board in the upstream station is faulty.
Procedure
Step 1 If the client side reports the SM_IAE alarm, check whether the client-side equipment connected to the OTU is faulty. If yes, remove the fault of the client-side equipment by referring to the related manuals. Step 2 If the alarm persists, perform a cold reset on the faulty board through the T2000 or reseat the faulty board. For details, see the Troubleshooting. Step 3 If the alarm persists, the board at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement. Step 4 If the WDM side reports the SM_IAE alarm, check whether the slip frame occurs to the signals sent by client-side equipment connected to the OTU. If yes, remove the fault of the client-side equipment by referring to the related manuals. Step 5 If the alarm persists, perform a cold reset on the OTU board at the local station through the T2000 or reseat the board. For details, see the Troubleshooting. Step 6 If the alarm persists, perform a cold reset on the OTU board in the opposite station through the T2000 or reseat the board. For details, see the Troubleshooting. Step 7 If the alarm persists, the OTU board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. Step 8 If the alarm persists, the board in the opposite station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.130 SPEED_OVER
Description
Data rate exceeding the set limits. The alarm is generated when the service rate of the board exceeds the set threshold value.
3 Alarm Processing
Reported from the WDM side or client side: client side
Attribute
Parameters

The services are not available.
Possible Causes
l l The carried service type is incorrect. The board hardware is faulty.
Procedure
Step 1 On the T2000, readjust the client service bearer rate to a value that is greater than the current service rate. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3-252
Issue 08 (2011-10-30)
3 Alarm Processing
3.2.131 SUM_INPWR_HI
Description
Input optical power is too high. The alarm is generated when the input optical power of the multiplexed signals exceeds the threshold. Reported from the WDM side or client side: NA
Attribute
Parameters

The optical modules of the boards at the local station and downstream station might be damaged. The services might have bit errors, or even be interrupted.
Possible Causes
l The output optical power of the board in the upstream station is normal and the power of the received optical signals accessed by the board at the local station is too high. The proper attenuation is not added. The output optical power of the board in the upstream station or opposite station is too high. The board at the local station is faulty.
l l
Procedure
Step 1 Check whether the input optical power of the input interface of the board at the local station is within the normal range by using an optical power meter. For the optical power indexed of the
3 Alarm Processing
specific board, see the Product Description. If the power is not within the normal range, add proper attenuation by placing a fix attenuator or a VOA. Step 2 If the alarm persists, check whether the output optical power of the board in the upstream stations is within the normal range by using the T2000. For the optical power specifications of the specific board, see the Product Description. If the input optical power of the board at the local station is too high, handle the alarm by referring to the handling procedure of the IN_PWR_HIGH alarm. If the output optical power of the boards in the upstream stations is too 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 in the upstream station are not within the normal range, adjust the input optical power to be within the normal range. For the optical power indexed of the specific board, see the Product Description. If the input optical power of the board in the upstream station is within the normal range but the output optical power is not, the board in the upstream station might be faulty. Replace the faulty board. For details, see the Parts Replacement.
Related Information
None
3.2.132 SUM_OUTPWR_HI
Description
Input optical power is too high. The alarm is generated when the output optical power of multiplexer unit is higher than the upper threshold.
Attribute
Parameters
3-254
Issue 08 (2011-10-30)
3 Alarm Processing
Parameter
Description

The alarm has an effect on the system services. The input optical power of the board in the downstream station might be too high, which leads to that the bit errors occur to the services or the services might be interrupted. The receive module of the OTU in the downstream station might be damaged.
Possible Causes
l l l The optical power of the accessed signals are too high and no proper attenuation is added. The internal attenuation of the board is incorrectly adjusted. The board hardware is faulty.
Procedure
Step 1 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 indexed of the specific board, see the Product Description. If the power is not within the normal range, add proper attenuation by placing a fix attenuator or a VOA. Step 2 If the alarm persists, query the attenuation value of each channel of the board (only for the V40) on the T2000. If the attenuation of the channel is too small, adjust the attenuation of the corresponding channel to a proper value on the T2000. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.133 SWDL_ACTIVATED_TIMEOUT
Description
Activation time out. During loading of the software packet, the alarm is generated when the operation is not committed in thirty minutes after activation operation.
Attribute
Issue 08 (2011-10-30)
3-255
3 Alarm Processing
Parameters
None

The services are not affected.
Possible Causes
The operation is not committed in thirty minutes after activation operation during loading of the software packet.
Procedure
Step 1 Query on the T2000 whether the activation operation is complete. If yes, proceed with the commit operation. ----End
Related Information
None
3.2.134 SWDL_AUTOMATCH_INH
Description
Automatic match inhibited. The alarm indicates the automatic match function is disabled.
NOTE
After the automatic match function is enabled, when a board is added in an NE, the system automatically checks whether the board software matches the NE software or not. If not, the SCC unit upgrades the board software of the new board.
Attribute
Alarm Severity Minor Alarm Type Process alarm
Parameters
None

The SCC unit cannot automatically update the software of the board that is newly inserted. If the software of the new board mismatches the NE software, some functions of the NE may operate abnormally. .
3 Alarm Processing
Possible Causes
The automatic match switch is turned off.
Procedure
Step 1 If the alarm persists, contact Huawei engineers. ----End
Related Information
None
3.2.135 SWDL_CHGMNG_NOMATCH
Description
SCC software and board software mismatch alarm. 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 a cold reset is performed on the SCC unit. The alarm is generated 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 l When the alarm is generated, the automatic match function for packet loading is disabled The software version of the unit is inconsistent with that of the SCC unit. Some functions of the NE may operate abnormally.
Possible Causes
l l After the NE is powered off, a unit is inserted and the software version of the unit is inconsistent with that of the SCC unit. The SCC unit is replaced, and the software package of the new SCC is inconsistent with the software version of units.
Issue 08 (2011-10-30)
3-257
3 Alarm Processing
Procedure
Step 1 In the T2000, use a correct software packet to perform packet loading on the board. For details, refer to the Version Upgrade Instructions. ----End
Related Information
None
3.2.136 SWDL_COMMIT_FAIL
Description
Commit failure alarm. During loading of the software packet, the alarm is generated when the commitment operation is failure.
Attribute
Parameters
None

The packet loading would fail and the upgrade of the software version fails.
Possible Causes
During the packet 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 backup. In normal status, every file is saved in both two partitions.
Procedure
Related Information
None
3 Alarm Processing
3.2.137 SWDL_INPROCESS
Description
NE is loading package. This alarm is generated when the NE is performing packet loading.
Attribute
Parameters
None

Working/Protection backing up of the SCC board are prohibited.
Possible Causes
The NE is performing the copying of the package file for loading.
Procedure
Related Information
None
3.2.138 SWDL_NEPKGCHECK
Description
Loss of file. The alarm is generated 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 clears.
NOTE
The SCC checks the software package ever time when it starts up and when the periodical check is performed. The periodical check is performed every hour by default.
Issue 08 (2011-10-30)
3-259
3 Alarm Processing
Attribute
Parameters
None

Because a file in the SCC software package is lost, there might be impact on the normal operation of some functions of the NE.
Possible Causes
The file is lost and irrecoverable.
Procedure
Related Information
None
3.2.139 SWDL_PKG_NOBDSOFT
Description
No matching board software alarm. 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 is generated.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual requirements.
Attribute
Parameters
None
3 Alarm Processing

The software version of the unit is inconsistent with that of the SCC unit. Some functions of the NE may operate abnormally.
Possible Causes
The user uses the customized software package, in which no software for the normal board is found.
Procedure
Related Information
None
3.2.140 SWDL_PKGVER_MM
Description
Package version conformance check failed. The alarm indicates the software version information (similar to the file list category) of the software packet is not consistent with the actual software version information.
Attribute
Parameters
None

The software versions on the NE are inconsistent. Some functions of the NE may operate abnormally.
Possible Causes
The file of the software packet is faulty, and the software version information about the software packet is not consistent with the actual software version information.
3 Alarm Processing
Procedure
Related Information
None
3.2.141 SWDL_ROLLBACK_FAIL
Description
NE rollback failed. Some board rollback fails when the NE performs rollback, the alarm is generated.
Attribute
Parameters
None

The NE rollback fails. The board software cannot recover to the version before the packet loading. and the board software version and the NE software version may mismatch. Some functions of the NE may operate abnormally.
Possible Causes
Some board rollback fails when the NE performs rollback.
Procedure
Related Information
None
3 Alarm Processing
3.2.142 SYNC_C_LOS
Description
Loss of clock source. This alarm is generated when the board detect inexistence of synchronization source with higher priority than the current synchronization source.
Attribute
Alarm Severity Warning Alarm Type 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 clock source type. For example, 0xf0 denotes the external clock source; 0xf1 denotes the internal clock source. Parameter 2 Indicates the clock source ID. For example, when parameter 1 is 0xf0, 0x01 denotes external clock source 1; when parameter 1 is 0xf1, 0x01 denotes internal clock source 1.

This alarm does not interrupt services or cause bit errors.
Possible Causes
l In non-S1 mode The fiber is faulty (if the system traces the line clock source) or the connection is faulty. The external clock source stops input (if the system traces the line clock source). The board is faulty. l In S1 mode The local station performs S1 byte switching. The input of external clock (BITS) changes. The board is faulty.
Issue 08 (2011-10-30)
3-263
3 Alarm Processing
Procedure
Step 1 Check whether the fiber connection is correct according to the engineering fiber connection diagram. The input optical signals in different wavelengths should be accessed to corresponding input optical interfaces of the board. If the fiber connection is incorrect, correct it according to the diagram. Step 2 Check whether the external clock source is normal. If not, remove the clock source fault first. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.143 SYSLOG_COMM_FAIL
Description
The communication between an NE and the syslog server fails. The alarm is generated when the session or the connection between an NE and the syslog server is abnormal.
Attribute
Parameters
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 to 4 Indicates the address of the syslog server. Parameter 5 Indicates the type of the fault that causes the alarm. 0x0a indicates that the connection fails. 0x02 indicates that the session is abnormal.

There is no impact on services, and no bit error is generated. But you can not find the syslog server.
3 Alarm Processing
Possible Causes
In the TCP mode, the connection between an NE and the syslog server or the session between servers is abnormal.
Procedure
Step 1 Check whether the board is returned for repair or not. If yes, there is no need to handle the alarm. Step 2 Restart Syslog service, and make sure that the server address, protocol and port match the actual. ----End
Related Information
None
3.2.144 T_LOC
Description
Transmit loss of clock. The alarm is generated when the clock signals cannot be extracted on the line side at the transmit end. Reported from the WDM side or client side: WDM side
Attribute
Parameters

3 Alarm Processing
Possible Causes
l l The client side does not access services and the laser on the WDM side is forced to emit light. If the client side normally accesses services but the transmitted signals do not have clock signals, the board hardware is faulty.
Procedure
Step 1 If the client side does not access services, access the client-side services first. Step 2 If the alarm persists, perform a cold reset on the faulty board through the T2000. For details, see the Troubleshooting. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.145 T_SLIP
Description
Transmitted side frame slipping. The alarm is generated when the phase deviation occurs to the transmitted service frames of the board.
Attribute
Parameters
3-266
Issue 08 (2011-10-30)
3 Alarm Processing

Bit errors occur in the client services, which can cause service break when it gets severe.
Possible Causes
The clock signals are not synchronous.
Procedure
Step 1 Perform a cold reset on the faulty board through the T2000 or remove the faulty board. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.146 TEM_HA
Description
Laser temperature is too high. This alarm is generated when the laser temperature is higher than the laser temperature maximum. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
Parameter Description Parameter 1 Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

This has impact on the working wavelengths of the optical module and affects the client services.
Possible Causes
l l
Issue 08 (2011-10-30)
Working temperature of the board is too high. The laser is faulty.

3 Alarm Processing
The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature and ventilation of the equipment room. If the board ambient temperature is too high, cool the equipment room with cooling devices, such as the air conditioner. Step 2 Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.147 TEM_LA
Description
Laser temperature is excessively low. his alarm is generated when the laser temperature is lower than the laser temperature minimum. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
Parameter Description Parameter 1 Indicates the optical interface where the alarm is generated. For example, 0x01 indicates optical interface 1.

This has impact on the working wavelengths of the optical module and affects the client services.
Possible Causes
l l l
3-268
Working temperature of the board is excessively low. The laser is faulty. The module performance detection circuit is faulty.
3 Alarm Processing
Procedure
Step 1 Check the board ambient temperature. If it is excessively low, increase it. Step 2 Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.148 TEMP_ALARM
Description
The temperature threshold crossing alarm. This alarm is generated when the board ambient temperature crosses the board temperature threshold. Reported from the WDM side or client side: NA.
Attribute
Parameters
Parameter Description Parameter 1 Indicates whether the temperature crosses the upper or lower threshold. For example, l 0x01 denotes that the temperature crosses the upper threshold. l 0x02 denotes that the temperature crosses the lower threshold.

Services borne on the board might be affected.
Possible Causes
l l l The board ambient temperature is overhigh. The board ambient temperature is overlow. The board is faulty.
Procedure
Step 1 Check whether the fan runs normally and whether the air duct is blocked because the dust filter of the fan is not cleaned in a long period.
3 Alarm Processing
Related Information
None
3.2.149 TEMP_OVER
Description
Working temperature over threshold. This alarm is generated when the board working temperature exceeds the threshold. Reported from the WDM side or client 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 Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

l l This alarm affects the system heat dissipation. In corresponding service boards, this alarm affects normal working of service chips and causes bit errors.
Possible Causes
l l l
3-270
The ambient temperature is too high. The cooling devices are abnormal. The board hardware is faulty.
3 Alarm Processing
Procedure
Step 1 Check the board ambient temperature in the NM system and check the ambient temperature of the equipment room. If the equipment is too hot, check the cooling device and make it work normally. Step 2 If the alarm persists, check whether the subrack fan is normal. If it stops working, replace it. For details, see the Parts Replacement. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.150 THUNDERALM
Description
Thunder protection circuit failure alarm. For the 1600g, The alarm is generated when the PMU board detects a lightning circuit failure of the PFU or DPFU module.
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, 0x11 indicates the first level lighting circuit failure of the first PFU or DPFU. 0x12 indicates the second level lighting circuit failure of the first PFU or DPFU. 0x21 indicates the first level lighting circuit failure of the second PFU or DPFU. 0x22 indicates the second level lighting circuit failure of the second PFU or DPFU.
Issue 08 (2011-10-30)
3-271
3 Alarm Processing

The lightning protection performance of the system is degraded. If the equipment is attacked by the strong current (for example, strong lightning stroke), the board on the subrack may be unavailable. As a result, the services are interrupted.
Possible Causes
l The equipment is attacked by the 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 PFU or DPFU board is unavailable and the circuit is broke due to the automatic protection of the fuse, the PMU detects the failure and reports this alarm. The board hardware is faulty.
Procedure
Step 1 Replace the faulty PFU or DPFU power module. For details, see the Parts Replacement. ----End
Related Information
In the lightning storm weather, intensive electromagnetic fields form in the air. To protect the equipment against lightning stroke, the equipment must be grounded during installation.
3.2.151 TP_LOC
Description
Transmission phase lock ring loss of clock. The alarm is generated when the transmitted clock of the board is lost. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
3-272
Issue 08 (2011-10-30)
3 Alarm Processing

Possible Causes
l l l The client side does not access services and the laser on the WDM side is forced to emit light. The client side normally accesses services but the transmitted signals do not have clock signals. The board hardware is faulty.
Procedure
Step 1 If the client side does not access services, access the client-side services first. Step 2 If the alarm persists, perform a cold reset on the faulty board through the T2000. For details, see the Troubleshooting. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.152 VCXO_LOC
Description
Local oscillator loss of clock. The alarm is generated when the crystal oscillator of the board is abnormal. Reported from the WDM side or client side: WDM side, client side
Attribute
Issue 08 (2011-10-30)
Alarm Type Equipment alarm
3-273
3 Alarm Processing
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 Parameter 1 Parameters 2 and 3 Description The value is always 0x01. There is no concept of optical ports. The value is always 0x00 0x01. There is no concept of channels.

The abnormal crystal oscillator of the board leads to that the board cannot work normally, which influences the user services.
Possible Causes
Procedure
Step 1 Perform a cold reset on the faulty board through the T2000. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. Foe details see Parts Replacement. ----End
Related Information
None
3.2.153 W_R_FAILURE
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
3-274
Issue 08 (2011-10-30)
3 Alarm Processing
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 IDs of the board register. For example, 0x01-0x09 indicates the IDs of the faulty chips that are of different types.

The board cannot work normally. In this case, the services may not be received or transmitted properly. In addition, the board may fail to query the current performance value.
Possible Causes
Procedure
Step 1 Perform a warm reset on the faulty board on the T2000. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3.2.154 WAVE_LEN_LOCK_FAIL
Description
Wavelength locking failure alarm. The alarm is generated when the wavelength locker cannot lock the wavelength due to the severe wavelength wander. Reported from the WDM side or client side: WDM side
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
3 Alarm Processing
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 Parameter 1 Description The optical port where the alarm is generated. The value is always 0x01.

The services borne by the wavelength are degraded or interrupted, which might influence the services borne by the adjacent wavelengths.
Possible Causes
Procedure
Step 1 Perform a cold reset on the faulty board through the T2000 or reseat the faulty board. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
3-276
Issue 08 (2011-10-30)
4
About This Chapter
Performance Event List
This chapter lists the names, description and relevant boards of the performance event in alphabetical order and lists the performance event of every board. 4.1 Product Performance Event List Lists the different types of performance event. 4.2 Board Performance Event List This section list the performance event of every board.
Issue 08 (2011-10-30)
4-1
4.1 Product Performance Event List

Lists the different types of performance event.
4.1.1 Performance Event List of Check and Error Correction

Name CRC4BBE CRC4CSES CRC4ES CRC4FEBBE CRC4FECSES CRC4FEES CRC4FESES CRC4SES CRC4UAS FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT FEC_AFT_COR_ERAV R FEC_BEF_COR_ERAV R ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_FEBBE Description CRC4 Background Block Error CRC4 Consecutive Severely Errored Second CRC4 Errored Second CRC4 Far End Background Block Error CRC4 Far End Consecutive Severely Errored Second CRC4 Far End Errored Second CRC4 Far End Severely Errored Second CRC4 Severely Errored Second CRC4 Unavailable Second After FEC Correct Errored Rate Before FEC Correct Errored Rate Forward Error Correction - Corrected 0 Bit Count Forward Error Correction - Corrected 1 Bit Count Forward Error Correction - Corrected Byte Count Forward Error Correction - Uncorrected Block Count After FEC Correct Average Errored Rate in monitor period Before FEC Correct Average Errored Rate in monitor period ODU PM Section Background Block Error ODU PM Section Ratio of Background Block Error ODU PM Section BIP8 ODU PM Section Far End Background Block Error
4-2
Issue 08 (2011-10-30)
Name ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_ES ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_SM_BIP8 OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_UAS ODU_TCMn_BBE
Issue 08 (2011-10-30)
Description ODU PM Section Ratio of Far End Background Block Error ODU PM Section Far End Errored Second ODU PM Section Far End Severely Errored Second ODU PM Section Ratio of Far End Severely Errored Second ODU PM Section Unavailable Second ODU PM Section Errored Second ODU PM Section Severely Errored Second ODU PM Section Ratio of Severely Errored Second ODU PM Section Unavailable Second OTU Background Block Error OTU Ratio of Background Block Error OTU SM Section Backward Incoming Alignment Errored Second OTU SM Section BIP8 OTU Errored Second OTU SM Section Far End Background Block Error OTU SM Section Ratio of Far End Background Block Error OTU SM Section Far End Errored Second OTU SM Section Far End Severely Errored Second OTU SM Section Ratio of Far End Severely Errored Second OTU SM Section Unavailable Second OTU SM Section Incoming Alignment Errored Second. OTU Severely Errored Second OTU Ratio of Severely Errored Second OTU Unavailable Second ODU TCMn Section Background Block Error
4-3
Name ODU_TCMn_BBER ODU_TCMn_BIAES ODU_TCMn_ES ODU_TCMn_FEBBE ODU_TCMn_FEBBER ODU_TCMn_FEES ODU_TCMn_FESES ODU_TCMn_FESESR ODU_TCMn_FEUAS ODU_TCMn_IAES ODU_TCMn_SES ODU_TCMn_SESR ODU_TCMn_UAS
Description ODU TCMn Section Ratio of Background Block Error ODU TCMn Section Backward Incoming Alignment Errored Second ODU TCMn Section Errored Second ODU TCMn Section Far End Background Block Error ODU TCMn Section Ratio of Far End Background Block Error ODU TCMn Section Far End Errored Second ODU TCMn Section Far End Severely Errored Second ODU TCMn Section Ratio of Far End Severely Errored Second ODU TCMn Section Unavailable Second ODU TCMn Section Incoming Alignment Errored Second ODU TCMn Section Severely Errored Second ODU TCMn Section Ratio of Severely Errored Second ODU TCMn Section Unavailable Second
4.1.2 Performance Event List of Equipment Function

Name BCVCUR BCVMAX BCVMIN CCVCUR CCVMAX Description Current Pump Laser Backfacet Current Value Maximum Pump Laser Backfacet Current Value Minimum Pump Laser Backfacet Current Value Current Pump Laser Cooling Current Value Maximum Pump Laser Cooling Current Value
4-4
Issue 08 (2011-10-30)
Name CCVMIN EDF_BOX_TMPCUR EDF_BOX_TMPMAX EDF_BOX_TMPMIN ENVTMPMAX ENVTMPMIN ENVTMPCUR ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSOOPCUR LSOOPMAX LSOOPMIN LSIOPCUR
Description Minimum Pump Laser Cooling Current Value Current EDFA Fiber Box Temperature Value Maximum EDFA Fiber Box Temperature Value EDFA Fiber Box Temperature Value Maximum Board Environmental Temperature Value Minimum Board Environmental Temperature Value Current Board Environmental Temperature Value Current Module Cooling Current Value Maximum Module Cooling Current Value Minimum Module Cooling Current Value Current Module Temperature Value Maximum Module Temperature Value Minimum Module Temperature Value Current Line Out Optical Power Value Maximum Line Out Optical Power Value Minimum Line Out Optical Power Value Current Output Optical Power Value Maximum Output Optical Power Value Minimum Output Optical Power Value Current Input Optical Power Value
Issue 08 (2011-10-30)
4-5
Name LSIOPMAX LSIOPMIN LSTMPCUR LSTMPMAX LSTMPMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN OOPRLCUR OOPRLMAX
Description Maximum Input Optical Power Value Minimum Input Optical Power Value Current Laser Temperature Value Maximum Laser Temperature Value Minimum Laser Temperature Value Current Laser Bias Current Value Maximum Laser Bias Current Value Minimum Laser Bias Current Value Current Laser Cooling Current Value Maximum Laser Cooling Current Value Minimum Laser Cooling Current Value Current value of the optical output power return loss Maximum value of the optical output power return loss within a time period Minimum value of the optical output power return loss within a time period Current Per-channel Laser Output Power Value Maximum Per-channel Laser Output Power Value Minimum Per-channel Laser Output Power Value Current Per-channel OSNR Value Current Per-channel Central Wavelength Value Maximum Per-channel Central Wavelength Value Minimum Per-channel Central Wavelength Value
Issue 08 (2011-10-30)
OOPRLMIN
PCLSOPCUR PCLSOPMAX PCLSOPMIN PCLSSNCUR PCLSWLCUR PCLSWLMAX PCLSWLMIN
4-6
Name PCLSWLOCUR PCLSWLOMAX PCLSWLOMIN PMUTMPCUR PMUTMPMAX PMUTMPMIN PUMPOOPCUR PUMPOOPMAX PUMPOOPMIN PUMPTMPCUR PUMPTMPMAX PUMPTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN WCVCUR
Description Current Per-channel Central Wavelength Deviation Value Maximum Per-channel Central Wavelength Deviation Value Minimum Per-channel Central Wavelength Deviation Value Current PMU board Environment Temperature Value Maximum PMU board Environment Temperature Value Minimum PMU board Environment Temperature Value Current Pump Output Optical Power Value Maximum Pump Output Optical Power Value Minimum Pump Output Optical Power Value Current Pump Laser Temperature Value Maximum Pump Laser Temperature Value Minimum Pump Laser Temperature Value Current Input Optical Power Value Maximum Input Optical Power Value Minimum Input Optical Power Value Current Output Optical Power Value Maximum Output Optical Power Value Minimum Output Optical Power Value Current Pump Laser Working Current Value
Issue 08 (2011-10-30)
4-7
Name WCVMAX WCVMIN
Description Maximum Pump Laser Working Current Value Minimum Pump Laser Working Current Value
4.1.3 Performance Event list of Multiplex Section Bit Error

Name MSBBE MSES MSSES MSUAS MSCSES MSFEES MSFESES MSFEBBE MSFECSES Description MS Background Block Error MS Errored Second MS Severely Errored Second MS Unavailable Second MS Consecutive Severely Errored Second MS Far End Errored Second MS Far End Severely Errored Second MS Far End Background Block Error MS Far End Consecutive Severely Errored Second
4.1.4 Performance Event List of Regenerator Section Bit Error

Name RSBBE RSES RSSES RSCSES RSUAS RSOFS Description RS Background Block Error RS Errored Second RS Severely Errored Second RS Consecutive Severely Errored Second RS Unavailable Second RS Out-of-Frame Second
4-8
Issue 08 (2011-10-30)
4.1.5 Performance Event List of Ethernet

Table 4-1 Statistics of Packets with Different Lengths Name Packets Received (64 Octets in Length) Description The total number of packets (including bad packets) received per second that are 64 octets in length (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received per second that are between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received per second that are between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received per second that are between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received per second that are between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received per second that are between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted per second that are 64 octets in length (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted per second that are between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted per second that are between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
4-9
Packets Received (65~127 Octets in Length)
Packets Transmitted (64 Octets in Length)
Packets Transmitted (65~127 Octets in Length)
Issue 08 (2011-10-30)
Name Packets Transmitted (256~511 Octets in Length)
Description The total number of packets (including bad packets) transmitted per second that are between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted per second that are between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted per second that are between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
Table 4-2 Statistics of Overall Performance Name Unicast Packets Received Multicast Packets Received Description The total number of good packets received per second that are directed to a unicast address. The total number of good packets received per second that are directed to a multicast address. Note that this number does not include packets directed to the broadcast address. The total number of good packets received per second that are directed to the broadcast address. Note that this does not include multicast packets. The total number of packets that higher-level protocols request to transmit per second, and which are not addressed to a multicast or broadcast address at this sub-layer, including those that are discarded or not sent. The total number of packets that higher-level protocols request to transmit per second, and which are addressed to a multicast address at this sub-layer, including those that are discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses.
Broadcast Packets Received
Unicast Packets Transmitted
Multicast Packets Transmitted
4-10
Issue 08 (2011-10-30)
Name Broadcast Packets Transmitted
Description The total number of packets that higher-level protocols request to transmit per second, and which are addressed to a broadcast address at this sub-layer, including those that are discarded or not sent. A count of MAC control frames received per second on this interface with an opcode indicating the PAUSE operation. A count of MAC control frames transmitted per second on this interface with an opcode indicating the PAUSE operation. The total number of packets received per second that are less than 64 octets in length (excluding framing bits, but including FCS octets) and are otherwise well formed. The total number of packets received per second that are longer than 1518 octets in length (excluding framing bits, but including FCS octets) and are otherwise well formed. The total number of packets received per second that are less than 64 octets in length (excluding framing bits but including 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). The total number of packets received per second that are longer than 1518 octets (excluding framing bits, but including 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). The total number of octets of good packets received per second on the network (excluding framing bits but including FCS octets). The total number of octets of good packets transmitted per second on the network (excluding framing bits but including FCS octets). The total number of octets of bad packets received per second on the network (excluding framing bits but including FCS octets).
Pause Frames Received
Pause Frames Transmitted
Undersize Packets Received
Oversize Packets Received
Fragments
Jabbers
Good Octets Received
Good Octets Transmitted
Bad Octets Received
Issue 08 (2011-10-30)
4-11
Name Bad Octets Transmitted
Description The total number of octets of bad packets transmitted per second on the network (excluding framing bits but including FCS octets).
Table 4-3 Error and Collision Name Alignment Errors Description The number of received frames that have alignment errors. An alignment errored frame cannot pass the FCS check because the frame contains a non-integer number of bytes. The count of frames received per second on a particular interface that are of an integral number of 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. The total number of packets received per second that are between 1519 octets and MTU octets in length.
FCS Errors
Packets Received (1519~MTU Octets in Length)
Packets Transmitted (1519~MTU The total number of packets transmitted per Octets in Length) second that are between 1519 octets and MTU octets in length.
4.2 Board Performance Event List

This section list the performance event of every board.
4.2.1 D40 Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN
4-12
Issue 08 (2011-10-30)
4.2.2 DCP Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR SUMIOPCUR SUMIOPMAX SUMIOPMIN
4.2.3 ELOG/ELOGS Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSTMPMAX LSTMPMIN ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_SM_BIP8 OTU_UAS Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Received Multicast Packets Received
Issue 08 (2011-10-30)
4-13
LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR FEC_AFT_COR_ERAVR
OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR FEC_BEF_COR_ERAVR
Broadcast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Undersize Packets Received Oversize Packets Received Fragments Jabbers Bad Octets Received Bad Octets Transmitted FCS Errors
4.2.4 ETMX/ETMXS Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSCSES MSES MSSES MSUAS ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR
4-14
Issue 08 (2011-10-30)
LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES
ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES
OTU_SM_BIP8 OTU_UAS RSES RSOFS RSSES RSUAS FEC_AFT_COR_ERAVR FEC_BEF_COR_ERAVR ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR
Issue 08 (2011-10-30)
4-15
ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR ODU_TCM6_SES
ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS ODU_TCM6_SESR
ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
4.2.5 FDG Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN FEC_AFT_COR_E R FEC_BEF_COR_E R FEC_COR_0BIT_C NT FEC_COR_1BIT_C NT FEC_COR_BYTE_ CNT FEC_UNCOR_BL OCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN
4-16
ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER
Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Unicast Packets Received
Issue 08 (2011-10-30)
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSCSES MSES MSFEBBE MSFECSES MSFEES MSFESES MSSES MSUAS
OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS RSBBE RSCSES RSES RSSES RSUAS
Multicast Packets Received Broadcast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Undersize Packets Received Oversize Packets Received Fragments Jabbers Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted FCS Errors
4.2.6 FIU Board Performance Event List

ENVTMPMAX SUMIOPMAX ENVTMPCUR SUMIOPMIN ENVTMPMIN SUMIOPCUR
4.2.7 FMU Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR
4.2.8 HBA Board Performance Event List

BCVCUR
Issue 08 (2011-10-30)
ENVTMPCUR
SUMIOPMAX
4-17
BCVMAX BCVMIN CCVCUR CCVMAX CCVMIN ENVTMPMAX ENVTMPMIN
ICTMPCUR ICTMPMAX ICTMPMIN PUMPTMPCUR PUMPTMPMAX PUMPTMPMIN SUMIOPCUR
SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN WCVCUR WCVMAX WCVMIN
4.2.9 ITL Board Performance Event List

ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN ENVTMPMAX ENVTMPMIN ENVTMPCUR
4.2.10 LBE/LBES Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CN T FEC_UNCOR_BLOCK _CNT ICTMPCUR LSOOPMIN ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length)
Issue 08 (2011-10-30)
4-18
ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSTMPCUR LSTMPMAX LSTMPMIN LSOOPCUR LSOOPMAX ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES
ODU_PM_FEUAS ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBE R ODU_TCM2_FESES R
Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Received Multicast Packets Received Broadcast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Undersize Packets Received Oversize Packets Received Fragments Jabbers Good Octets Received Good Octets Transmitted FCS Errors FEC_AFT_COR_ERAVR FEC_BEF_COR_ERAVR ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS
Issue 08 (2011-10-30)
4-19
ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR ODU_TCM6_SES
ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBE R ODU_TCM5_FESES R ODU_TCM5_SES ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS ODU_TCM6_SESR
ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
4.2.11 LBF/LBFS Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT MSSES MSUAS ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES RSCSES RSES RSOFS RSSES RSUAS Packets Received (64 Octets in Length)
4-20
Issue 08 (2011-10-30)
FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX
ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8
Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Received Multicast Packets Received Broadcast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Undersize Packets Received Oversize Packets Received Fragments Jabbers
Issue 08 (2011-10-30)
4-21
LSTMPMIN MSBBE MSCSES MSES ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR
OTU_UAS FEC_BEF_COR_ERAVR FEC_AFT_COR_ERAVR RSBBE ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS
Good Octets Received Good Octets Transmitted FCS Errors ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
4-22
Issue 08 (2011-10-30)
ODU_TCM6_SES
ODU_TCM6_SESR
4.2.12 LOG/LOGS Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSTMPMAX LSTMPMIN ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_SM_BIP8 OTU_UAS Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Received Multicast Packets Received Broadcast Packets Received Unicast Packets Transmitted
Issue 08 (2011-10-30)
4-23
LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR FEC_AFT_COR_ERAVR
OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR FEC_BEF_COR_ERAV R
Multicast Packets Transmitted Broadcast Packets Transmitted Undersize Packets Received Oversize Packets Received Fragments Jabbers Bad Octets Received Bad Octets Transmitted FCS Errors
4.2.13 LQM Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length)
4-24
Issue 08 (2011-10-30)
LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE FEC_AFT_COR_ERAV R
OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS RSBBE RSCSES RSES RSSES RSUAS Packets Received (64 Octets in Length) FEC_BEF_COR_ERAVR
Packets Transmitted (1519~MTU Octets in Length) Unicast Packets Received Multicast Packets Received Broadcast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Undersize Packets Received Oversize Packets Received Fragments Jabbers Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted FCS Errors
4.2.14 LU40 Board Performance Event List

ENVTMPCUR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_COR_BYTE_CNT LINE_OUT_POWERMAX ENVTMPMAX FEC_AFT_COR_ER FEC_COR_0BIT_CNT FEC_UNCOR_BLOCK_C NT LINE_OUT_POWERMIN ENVTMPMIN FEC_BEF_CORER_FLOA T FEC_COR_1BIT_CNT LINE_OUT_POWERCUR LSBIASCUR
Issue 08 (2011-10-30)
4-25
LSBIASMAX LSCLCMAX LSIOPMAX LSOOPMAX LSTMPMAX ODU_PM_BBER ODU_PM_FEBBE ODU_PM_FESES ODU_PM_SES OTU_BBE OTU_ES OTU_FEES OTU_FEUAS OTU_SESR RSBBE RSOFS ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE
LSBIASMIN LSCLCMIN LSIOPMIN LSOOPMIN LSTMPMIN ODU_PM_BIP8 ODU_PM_FEBBER ODU_PM_FESESR ODU_PM_SESR OTU_BBER OTU_FEBBE OTU_FESES OTU_IAES OTU_SM_BIP8 RSCSES RSSES ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER
LSCLCCUR LSIOPCUR LSOOPCUR LSTMPCUR ODU_PM_BBE ODU_PM_ES ODU_PM_FEES ODU_PM_FEUAS ODU_PM_UAS OTU_BIAES OTU_FEBBER OTU_FESESR OTU_SES OTU_UAS RSES RSUAS ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES
4-26
Issue 08 (2011-10-30)
ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR ODU_TCM6_SES
ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS ODU_TCM6_SESR
ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
4.2.15 LU40S Board Performance Event List

ENVTMPCUR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_COR_BYTE_CNT LINE_OUT_POWERMAX LSBIASMAX LSCLCMAX LSIOPMAX LSOOPMAX LSTMPMAX ODU_PM_BBER ODU_PM_FEBBE ODU_PM_FESES ODU_PM_SES ENVTMPMAX FEC_AFT_COR_ER FEC_COR_0BIT_CNT FEC_UNCOR_BLOCK_C NT LINE_OUT_POWERMIN LSBIASMIN LSCLCMIN LSIOPMIN LSOOPMIN LSTMPMIN ODU_PM_BIP8 ODU_PM_FEBBER ODU_PM_FESESR ODU_PM_SESR ENVTMPMIN FEC_BEF_CORER_FLOA T FEC_COR_1BIT_CNT LINE_OUT_POWERCUR LSBIASCUR LSCLCCUR LSIOPCUR LSOOPCUR LSTMPCUR ODU_PM_BBE ODU_PM_ES ODU_PM_FEES ODU_PM_FEUAS ODU_PM_UAS
Issue 08 (2011-10-30)
4-27
OTU_BBE OTU_ES OTU_FEES OTU_FEUAS OTU_SESR RSBBE RSOFS ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS
OTU_BBER OTU_FEBBE OTU_FESES OTU_IAES OTU_SM_BIP8 RSCSES RSSES ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES ODU_TCM6_BBE
OTU_BIAES OTU_FEBBER OTU_FESESR OTU_SES OTU_UAS RSES RSUAS ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER
4-28
Issue 08 (2011-10-30)
ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR ODU_TCM6_SES
ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS ODU_TCM6_SESR
ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
4.2.16 LUR40/LUR40S Board Performance Event List

ENVTMPCUR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_COR_BYTE_CNT LINE_OUT_POWERMAX LSBIASMAX LSCLCMAX LSIOPMAX LSOOPMAX LSTMPMAX ODU_PM_BBER ODU_PM_FEBBE ODU_PM_FESES ODU_PM_SES OTU_BBE OTU_ES OTU_FEES OTU_FEUAS OTU_SESR ENVTMPMAX FEC_AFT_COR_ER FEC_COR_0BIT_CNT FEC_UNCOR_BLOCK_C NT LINE_OUT_POWERMIN LSBIASMIN LSCLCMIN LSIOPMIN LSOOPMIN LSTMPMIN ODU_PM_BIP8 ODU_PM_FEBBER ODU_PM_FESESR ODU_PM_SESR OTU_BBER OTU_FEBBE OTU_FESES OTU_IAES OTU_SM_BIP8 ENVTMPMIN FEC_BEF_CORER_FLOA T FEC_COR_1BIT_CNT LINE_OUT_POWERCUR LSBIASCUR LSCLCCUR LSIOPCUR LSOOPCUR LSTMPCUR ODU_PM_BBE ODU_PM_ES ODU_PM_FEES ODU_PM_FEUAS ODU_PM_UAS OTU_BIAES OTU_FEBBER OTU_FESESR OTU_SES OTU_UAS
4.2.17 LWC1 Board Performance Event List

ENVTMPMAX
Issue 08 (2011-10-30)
LSIOPMIN
ODU_PM_SESR
4-29
ENVTMPMIN ENVTMPCUR FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX FEC_AFT_COR_ERAVR
LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSES MSSES MSUAS MSCSES ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES FEC_BEF_COR_ERAVR
ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS RSBBE RSES RSSES RSCSES RSUAS RSOFS
4.2.18 LWF/LWFS Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR FEC_AFT_COR_ER LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER
4-30
Issue 08 (2011-10-30)
FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES
LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSES MSSES MSUAS MSCSES ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES
OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS RSBBE RSES RSSES RSCSES RSUAS RSOFS ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE
Issue 08 (2011-10-30)
4-31
ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR ODU_TCM6_SES FEC_AFT_COR_ERAVR
ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS ODU_TCM6_SESR FEC_BEF_COR_ERAVR
ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
4.2.19 LWX Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR LSOOPCUR LSOOPMAX LSOOPMIN LSCLCMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length)
4-32
Issue 08 (2011-10-30)
LSIOPCUR LSIOPMAX LSIOPMIN LSTMPCUR LSTMPMAX LSTMPMIN
RSBBE RSES RSSES RSCSES RSUAS RSOFS
Packets Received (1519~MTU Octets in Length) Undersize Packets Received Oversize Packets Received Good Octets Received Bad Octets Received FCS Errors
4.2.20 M40 Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN
4.2.21 MCA Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR PCLSOPCUR PCLSSNCUR PCLSWLCUR PCLSWLOCUR
4.2.22 MR2 Board Performance Event List

4.2.23 MR8 Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN
Issue 08 (2011-10-30)
4-33
4.2.24 MWA Board Performance Event List

4.2.25 MWF Board Performance Event List

4.2.26 OAU Board Performance Event List

BCVCUR BCVMAX BCVMIN CCVCUR CCVMAX CCVMIN EDF_BOX_TMPCUR EDF_BOX_TMPMAX EDF_BOX_TMPMIN ENVTMPMAX ENVTMPMIN ENVTMPCUR PUMPTMPCUR PUMPTMPMAX PUMPTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN WCVCUR WCVMAX WCVMIN
4.2.27 OBU Board Performance Event List

4-34
Issue 08 (2011-10-30)
4.2.28 OLP Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR SUMIOPCUR SUMIOPMAX SUMIOPMIN
4.2.29 OPU Board Performance Event List

4.2.30 PMU Board Performance Event List

PMUTMPCUR PMUTMPMAX PMUTMPMIN
4.2.31 RMU9 Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN
4.2.32 RPC Board Performance Event List

BCVCUR BCVMAX BCVMIN
Issue 08 (2011-10-30)

PUMPTMPCUR PUMPTMPMAX PUMPTMPMIN

4-35
CCVCUR CCVMAX CCVMIN
OOPRLMAX OOPRLMIN OOPRLCUR
WCVCUR WCVMAX WCVMIN
4.2.33 SC1/SC2 Board Performance Event List

CRC4BBE CRC4CSES CRC4ES CRC4FEBBE CRC4FECSES CRC4FEES CRC4FESES CRC4SES CRC4UAS ENVTMPMAX ENVTMPMIN ENVTMPCUR LSOOPCUR LSOOPMAX LSOOPMIN LSIOPCUR LSIOPMAX LSIOPMIN LSTMPCUR LSTMPMAX LSTMPMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN
4.2.34 TMR/TMRS Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_SES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS
4-36
Issue 08 (2011-10-30)
LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX
ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS
OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS
4.2.35 TMX/TMXS Board Performance Event List

ENVTMPMAX ENVTMPCUR ENVTMPMIN FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSCSES MSES MSFEBBE MSFECSES MSFEES MSFESES MSSES MSUAS ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8 OTU_UAS RSBBE RSCSES RSES RSOFS
Issue 08 (2011-10-30)
4-37
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR
ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS
RSSES RSUAS FEC_AFT_COR_ERAVR FEC_BEF_COR_ERAVR ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES
4-38
Issue 08 (2011-10-30)
ODU_TCM6_SES
ODU_TCM6_SESR
ODU_TCM6_UAS
4.2.36 TMX40/TMX40S Board Performance Event List

ENVTMPCUR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_COR_BYTE_CNT LSBIASMAX LSCLCMAX LSIOPMAX LSOOPMAX LSTMPMAX ODU_PM_BBER ODU_PM_FEBBE ODU_PM_FESES ODU_PM_SES OTU_BBE OTU_ES OTU_FEES OTU_FEUAS OTU_SESR RSBBE RSSES ODU_TCM1_BBE ODU_TCM1_ES ODU_TCM1_FEES ODU_TCM1_FEUAS ODU_TCM1_SESR ODU_TCM2_BBER ENVTMPMAX FEC_AFT_COR_ER FEC_COR_0BIT_CNT FEC_UNCOR_BLOCK_C NT LSBIASMIN LSCLCMIN LSIOPMIN LSOOPMIN LSTMPMIN ODU_PM_BIP8 ODU_PM_FEBBER ODU_PM_FESESR ODU_PM_SESR OTU_BBER OTU_FEBBE OTU_FESES OTU_IAES OTU_SM_BIP8 RSCSES RSUAS ODU_TCM1_BBER ODU_TCM1_FEBBE ODU_TCM1_FESES ODU_TCM1_IAES ODU_TCM1_UAS ODU_TCM2_BIAES ENVTMPMIN FEC_BEF_CORER_FLOA T FEC_COR_1BIT_CNT LSBIASCUR LSCLCCUR LSIOPCUR LSOOPCUR LSTMPCUR ODU_PM_BBE ODU_PM_ES ODU_PM_FEES ODU_PM_FEUAS ODU_PM_UAS OTU_BIAES OTU_FEBBER OTU_FESESR OTU_SES OTU_UAS RSES RSOFS ODU_TCM1_BIAES ODU_TCM1_FEBBER ODU_TCM1_FESESR ODU_TCM1_SES ODU_TCM2_BBE ODU_TCM2_ES
Issue 08 (2011-10-30)
4-39
ODU_TCM2_FEBBE ODU_TCM2_FESES ODU_TCM2_IAES ODU_TCM2_UAS ODU_TCM3_BIAES ODU_TCM3_FEBBER ODU_TCM3_FESESR ODU_TCM3_SES ODU_TCM4_BBE ODU_TCM4_ES ODU_TCM4_FEES ODU_TCM4_FEUAS ODU_TCM4_SESR ODU_TCM5_BBER ODU_TCM5_FEBBE ODU_TCM5_FESES ODU_TCM5_IAES ODU_TCM5_UAS ODU_TCM6_BIAES ODU_TCM6_FEBBER ODU_TCM6_FESESR ODU_TCM6_SES
ODU_TCM2_FEBBER ODU_TCM2_FESESR ODU_TCM2_SES ODU_TCM3_BBE ODU_TCM3_ES ODU_TCM3_FEES ODU_TCM3_FEUAS ODU_TCM3_SESR ODU_TCM4_BBER ODU_TCM4_FEBBE ODU_TCM4_FESES ODU_TCM4_IAES ODU_TCM4_UAS ODU_TCM5_BIAES ODU_TCM5_FEBBER ODU_TCM5_FESESR ODU_TCM5_SES ODU_TCM6_BBE ODU_TCM6_ES ODU_TCM6_FEES ODU_TCM6_FEUAS ODU_TCM6_SESR
ODU_TCM2_FEES ODU_TCM2_FEUAS ODU_TCM2_SESR ODU_TCM3_BBER ODU_TCM3_FEBBE ODU_TCM3_FESES ODU_TCM3_IAES ODU_TCM3_UAS ODU_TCM4_BIAES ODU_TCM4_FEBBER ODU_TCM4_FESESR ODU_TCM4_SES ODU_TCM5_BBE ODU_TCM5_ES ODU_TCM5_FEES ODU_TCM5_FEUAS ODU_TCM5_SESR ODU_TCM6_BBER ODU_TCM6_FEBBE ODU_TCM6_FESES ODU_TCM6_IAES ODU_TCM6_UAS
RMON Performance Event Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Received Undersize Packets Received Oversize Packets Received
Fragments
4-40
Issue 08 (2011-10-30)
Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length)
Multicast Packets Received Broadcast Packets Received Unicast Packets Transmitted
Jabbers Good Octets Received Bad Octets Received
Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted
Good Octets Transmitted Bad Octets Transmitted Alignment Errors FCS Errors
4.2.37 TRC1 Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT ICTMPCUR ICTMPMAX ICTMPMIN LINE_OUT_POWERCUR LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSES MSSES MSUAS MSCSES ODU_PM_BBE ODU_PM_BBER ODU_PM_BIP8 ODU_PM_ES ODU_PM_SESR ODU_PM_UAS OTU_BBE OTU_BBER OTU_BIAES OTU_ES OTU_FEBBE OTU_FEBBER OTU_FEES OTU_FESES OTU_FESESR OTU_FEUAS OTU_IAES OTU_SES OTU_SESR OTU_SM_BIP8
Issue 08 (2011-10-30)
4-41
LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX
ODU_PM_FEBBE ODU_PM_FEBBER ODU_PM_FEES ODU_PM_FESES ODU_PM_FESESR ODU_PM_FEUAS ODU_PM_SES
OTU_UAS RSBBE RSES RSSES RSCSES RSUAS RSOFS
4.2.38 V40 Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR ICTMPCUR ICTMPMAX ICTMPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN
4.2.39 VA4 Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR LSOOPCUR LSOOPMAX LSOOPMIN LSIOPCUR LSIOPMAX LSIOPMIN
4.2.40 VOA Board Performance Event List

LSOOPCUR LSOOPMAX LSOOPMIN LSIOPCUR LSIOPMAX LSIOPMIN
4.2.41 WMU Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN ICTMPCUR
4-42
ICTMPMIN PCLSOPCUR PCLSOPMAX PCLSOPMIN
PCLSWLMAX PCLSWLMIN PCLSWLOCUR PCLSWLOMAX

Issue 08 (2011-10-30)
ICTMPMAX
PCLSWLCUR
PCLSWLOMIN
4.2.42 WSD9 Board Performance Event List

4.2.43 WSM9 Board Performance Event List

4.2.44 WSMD2 Board Performance Event List

ENVTMPCUR ICTMPCUR SUMIOPCUR SUMOOPCUR ENVTMPMAX ICTMPMAX SUMIOPMAX SUMOOPMAX ENVTMPMIN ICTMPMIN SUMIOPMIN SUMOOPMIN
4.2.45 WSMD4 Board Performance Event List

Issue 08 (2011-10-30)
4-43
5 Performance Event Processing
5
About This Chapter
Performance Event Processing
The performance event is an important parameter to evaluate the working performance of DWDM equipment. Being acquainted with the generation principle, related boards and related alarms help you discover hidden trouble in routine maintenance and locate fault in troubleshooting. If a performance event exceeds the pre-set threshold, the related alarm(s) are generated. Therefore, upon any performance event, check any related alarms and handle the event accordingly. 5.1 BCV 5.2 CCV 5.3 CRC4BBE 5.4 CRC4CSES 5.5 CRC4ES 5.6 CRC4FEBBE 5.7 CRC4FECSES 5.8 CRC4FEES 5.9 CRC4FESES 5.10 CRC4SES 5.11 CRC4UAS 5.12 EDF_BOX_TMP 5.13 ENV_TMP 5.14 FEC_AFT_COR_ER 5.15 FEC_AFT_COR_ERAVR 5.16 FEC_AFT_CORER_FLOAT
5.17 FEC_BEF_COR_ER 5.18 FEC_BEF_COR_ERAVR 5.19 FEC_BEF_CORER_FLOAT 5.20 FEC_COR_0BIT_CNT 5.21 FEC_COR_1BIT_CNT 5.22 FEC_COR_BYTE_CNT 5.23 FEC_UNCOR_BLOCK_CNT 5.24 ICCLC 5.25 ICTMP 5.26 LINE_OUT_POWER 5.27 LSBIAS 5.28 LSCLC 5.29 LSIOP 5.30 LSOOP 5.31 LSTMP 5.32 MSBBE 5.33 MSCSES 5.34 MSES 5.35 MSFEBBE 5.36 MSFECSES 5.37 MSFEES 5.38 MSFESES 5.39 MSSES 5.40 MSUAS 5.41 ODU_PM_BBE 5.42 ODU_PM_BBER 5.43 ODU_PM_BIP8 5.44 ODU_PM_ES 5.45 ODU_PM_FEBBE 5.46 ODU_PM_FEBBER 5.47 ODU_PM_FEES 5.48 ODU_PM_FESES 5.49 ODU_PM_FESESR
5.50 ODU_PM_FEUAS 5.51 ODU_PM_SES 5.52 ODU_PM_SESR 5.53 ODU_PM_UAS 5.54 ODU_TCMn_BBE 5.55 ODU_TCMn_BBER 5.56 ODU_TCMn_BIAES 5.57 ODU_TCMn_ES 5.58 ODU_TCMn_FEBBE 5.59 ODU_TCMn_FEBBER 5.60 ODU_TCMn_FEES 5.61 ODU_TCMn_FESES 5.62 ODU_TCMn_FESESR 5.63 ODU_TCMn_FEUAS 5.64 ODU_TCMn_IAES 5.65 ODU_TCMn_SES 5.66 ODU_TCMn_SESR 5.67 ODU_TCMn_UAS 5.68 OOPRL 5.69 OTU_BBE 5.70 OTU_BBER 5.71 OTU_ES 5.72 OTU_FEBBE 5.73 OTU_FEBBER 5.74 OTU_FEES 5.75 OTU_FESES 5.76 OTU_FESESR 5.77 OTU_FEUAS 5.78 OTU_SES 5.79 OTU_SESR 5.80 OTU_SM_BIP8 5.81 OTU_UAS 5.82 OTU_IAES
5.83 OTU_BIAES 5.84 PCLSOP 5.85 PCLSSN 5.86 PCLSWL 5.87 PCLSWLO 5.88 PMUTMP 5.89 PUMPOOP 5.90 PUMPTMP 5.91 RSBBE 5.92 RSCSES 5.93 RSES 5.94 RSOFS 5.95 RSSES 5.96 RSUAS 5.97 SUMIOP 5.98 SUMOOP 5.99 WCV
5-4
Issue 08 (2011-10-30)
5.1 BCV
Description
Pump Laser Back Facet Current It includes: l l l BCVMAX: stands for the maximum value during a period of time. BCVMIN: stands for the minimum value during a period of time. BCVCUR: stands for the current value.
Impact on System
None
Generation Principle and Possible Causes

Back facet current is current O/E converted from part of light reflected from the resonant cavity of a laser. The back facet current reflects the laser output optical power value. If the BCVCUR is 0, the laser is faulty; replace the board where this faulty laser resides in.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.2 CCV
Description
Pump Laser Cooling Current It includes: l l l
Issue 08 (2011-10-30)
CCVMAX: stands for the maximum value during a period of time. CCVMIN: stands for the minimum value during a period of time. CCVCUR: stands for the current value.
Impact on System
None

Use an A/D converter to sample the voltage corresponding to the cooling current of each laser, and convert the voltage into cooling current. This value shows the working status of the cooling circuit in a certain laser.
Related Alarms
Alarm Name PUMP_COOL_EXC Correlation It is generated when the cooling current of laser exceeds the normal range.
Procedure
Step 1 If the PUMP_COOL_EXC alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.3 CRC4BBE
Description
CRC4 Background Block Error
Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

CRC error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.4 CRC4CSES
Description
CRC4 Consecutive Severely Errored Second
Impact on System

CRC error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might indicate the interruption of service that shares a fiber link with the supervisory channel.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.5 CRC4ES
Description
CRC4 Errored Second
Impact on System
There are bit errors in the services. If the CRC4 errored seconds are generated continuously, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

CRC error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.6 CRC4FEBBE
Description
CRC4 Far End Background Block Error
Impact on System
There are bit errors in the services. If the number of bit errors is small, there is no impact on the services. If the number of bit errors is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

CRC error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.7 CRC4FECSES
Description
CRC4 Far End Consecutive Severely Errored Second
Impact on System

CRC error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might indicate the service interruption on the fiber link. The far end consecutive severely errored second refers to the consecutive severely errored second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.8 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.

CRC error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.9 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.

CRC error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.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.

CRC error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.11 CRC4UAS
Description
CRC4 Unavailable Second
Impact on System

CRC error is detected by checking the received parity bit. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
None Alarm Name CRC4_CROSSTR Correlation CRC4 multi-frame error code count exceeds the threshold. The alarm is generated when the number of the bit errors in the CRC4 multiframe exceeds the threshold.
Procedure
Step 1 None ----End
Related Information
None
5.12 EDF_BOX_TMP
Description
EDFA Fiber Box Temperature It includes: l l l EDF_BOX_TMPMAX: stand for the maximum value during a period of time. EDF_BOX_TMPMIN: stand for the minimum value during a period of time. EDF_BOX_TMPCUR: stand for the current value.
Impact on System
The EDFA fiber box can operate normally only when the temperature is in the temperature range. If the temperature is very high or very low, the system performance is affected.

Use an A/D converter to sample the voltage corresponding to the working temperature of EDFA fiber box, and convert the voltage into temperature. The performance value shows the working temperature of EDFA fiber box.
Related Alarms
Alarm Name EDFA_TMP_OVER Correlation It is generated when the temperature of EDFA fiber box exceeds the normal range.
Issue 08 (2011-10-30)
5-12
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of the specific board, refer to the Product Description. Step 2 Check whether the fan runs normally and whether the air duct is blocked because the dust filter of the fan is not cleaned in a long period. Step 3 If the alarm persists, replace the faulty board. For details, refer to the Parts Replacement. ----End
Related Information
None
5.13 ENV_TMP
Description
Board Environmental Temperature It includes: l l l ENV_TMPMAX: stands for the maximum value during a period of time. ENV_TMPMIN: stands for the minimum value during a period of time. ENV_TMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by hardware detecting, to show the ambient temperature of board.
Related Alarms
Alarm Name TEMP_ALARM Correlation It is generated when the ambient temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_ALARM alarm is generated, see the proper handling procedures. ----End
Related Information
None
5.14 FEC_AFT_COR_ER
Description
After FEC Correct Errored Rate
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that the bit errors in the services bring impact on the transmission quality. In this case, determine the cause in a timely manner.

This performance event shows there are still errors at the receiver after FEC. This performance event is caused by low OSNR at the receiving end. Normally, it should be zero. In this case, there must be FEC_BEF_COR_ER accompanied. You can adjust the optical power to increase the OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.15 FEC_AFT_COR_ERAVR
Description
After FEC Correct Average Errored Rate in monitor period.
Impact on System

This performance event shows there are still errors at the receiver after FEC. This performance event is caused by low OSNR at the receiving end. Normally, it should be zero. In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the optical power to increase the OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.16 FEC_AFT_CORER_FLOAT
Description
After FEC Correct Errored Rate(floating point values)
Impact on System

This performance event shows there are still errors at the receiver after FEC. This performance event is caused by low OSNR at the receiving end. Normally, it should be zero. In this case, there must be FEC_BEF_CORER_FLOAT accompanied. You can adjust the optical power to increase the OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.17 FEC_BEF_COR_ER
Description
BER before FEC.
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate (BER) is low, the system operates normally. If the BER is high, determine the causes and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality.

The cause for the BER before the FEC is that the receiver detects bit errors, which are caused by dispersion, unstable performance of the optical interface, and/or very high attenuation.
Related Alarms
Alarm Name BEFFEC_EXC Correlation Signal degraded before FEC alarm. 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 is generated when the counted bit error rate exceeds the threshold. Signal degraded alarm before FEC alarm. 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 is generated when the counted bit error rate exceeds the threshold.
BEFFEC_SD
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC. ----End
Related Information
None
5.18 FEC_BEF_COR_ERAVR
Description
Before FEC Correct Average Errored Rate in monitor period.
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate (BER) is low, the system operates normally. If the BER is high, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR at the receiving end. Normally, it should be zero.
Related Alarms
Alarm Name BEFFEC_EXC Correlation 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. 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.
BEFFEC_SD
Procedure
Related Information
None
5.19 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.

This performance event shows errors are detected at the receiver, which is caused by low OSNR at the receiving end.
Related Alarms
BEFFEC_SD
Procedure
Related Information
None
5.20 FEC_COR_0BIT_CNT
Description
Forward Error Correction - Corrected 0 Bit Count
Impact on System
None

This performance event shows the number of 0bit corrected by FEC function of the board, and indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.21 FEC_COR_1BIT_CNT
Description
Forward Error Correction - Corrected 1 Bit Count
Impact on System
None

This performance event shows the number of 1bit corrected by FEC function of the board, and indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.22 FEC_COR_BYTE_CNT
Description
Forward Error Correction - Corrected Byte Count
Impact on System
None

This performance event shows the number of byte corrected by FEC function of the board, and indicates the FEC capability to signals of low OSNR. Normally, it should be zero.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.23 FEC_UNCOR_BLOCK_CNT
Description
Forward Error Correction - uncorrected Block Count
Impact on System
There are bit errors in the services and the signal transmission quality is affected.

This performance event shows the number of received error frames that cannot be corrected by FEC, and indicates that bit errors are beyond the correction capability of FEC. Normally, the performance value should be zero.
Related Alarms
BEFFEC_SD
5-20
Procedure
Related Information
None
5.24 ICCLC
Description
Module Cooling Current It includes: l l l ICCLCMAX: stands for the maximum value during a period of time. ICCLCMIN: stands for the minimum value during a period of time. ICCLCCUR: stands for the current value.
Impact on System
None

This performance event is generated by software checking with the cooling current detecting circuit on board, to show the working status of module cooling current.
Related Alarms
Alarm Name MODULE_COOLCUR_OVER Correlation It is generated when the cooling or warming current of module exceeds the alarm threshold.
Procedure
Step 1 If the MODULE_COOLCUR_OVER alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.25 ICTMP
Description
Module Temperature It includes: l l l ICTMPMAX: stands for the maximum value during a period of time. ICTMPMIN: stands for the minimum value during a period of time. ICTMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by checking the current working temperature of module, to show the working temperature of a module.
Related Alarms
Alarm Name MODULE_TEMP_OVER Correlation It is generated when the working temperature of module exceeds the threshold.
Procedure
Step 1 If the MODULE_TEMP_OVER alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.26 LINE_OUT_POWER
Description
The Line Output Optical Power It includes:
l l l
LINE_OUT_POWER_MAX: stands for the maximum value during a period of time. LINE_OUT_POWER_MIN: stands for the minimum value during a period of time. LINE_OUT_POWER_CUR: stands for the current value.
Impact on System
None

The LINE_OUT_POWER performance is generated by checking the output optical power of optical transmitting module at WDM side of a board. The relation between them shows as: LSOOP LINE_OUT_POWER Figure 5-1 Monitoring point of optical power
Monitoring point A Monitoring point A
laser
VOA and other units
Optical transmitting module
WARNING
OUT_PWR_HIGH and OUT_PWR_LOW alarms are generated by monitoring LSOOP, they are independent from LINE_OUT_POWER.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
Issue 08 (2011-10-30)
5-23
5.27 LSBIAS
Description
Laser Bias Current It includes: l l l LSBIASMAX: stands for the maximum value during a period of time. LSBIASMIN: stands for the minimum value during a period of time. LSBIASCUR: stands for the current value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
Alarm Name TD Correlation It is generated when the working current of laser exceeds the threshold or the multiple of threshold. It is generated when the working current of laser exceeds the threshold or the multiple of threshold.
LSR_WILL_DIE
Procedure
Step 1 If the TD alarm is generated, see the handling procedure of the alarm. Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.28 LSCLC
Description
Laser Cooling Current
It includes: l l l LSCLCMAX: stands for the maximum value during a period of time. LSCLCMIN: stands for the minimum value during a period of time. LSCLCCUR: stands for the current value.
Impact on System
When the cooling current of a laser exceeds the threshold, the optical module of the board works abnormally. As a result, services cannot be transmitted or received normally.

External cooling or warming equipment should be provided to keep the temperature stable for a laser to work. The laser cooling current shows the working status of cooling equipment or circuit.
Related Alarms
Alarm Name LSR_COOL_ALM Correlation It is generated when the laser cooling current exceeds the pre-set threshold.
Procedure
Step 1 If the LSR_COOL_ALM alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.29 LSIOP
Description
Input Optical Power It includes: l l l LSIOPMAX: stand for the maximum value during a period of time. LSIOPMIN: stand for the minimum value during a period of time. LSIOPCUR: stand for the current value.
Impact on System
When the input optical power is very high or very low, bit errors and the LOF alarm may be generated in the received signals, which brings impact on the services.

The hardware checks the optical module and then the software converts the check result into LSIOP to show the input optical power performance of a board.
Related Alarms
Alarm Name IN_PWR_HIGH IN_PWR_LOW Correlation It is generated when the optical power input by board is higher than the upper threshold. It is generated when the optical power input by board is lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), refer to the procedure for handling the IN_PWR_HIGH alarm. Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), refer to the procedure for handling the IN_PWR_LOW alarm. Step 3 If an alarm is generated, refer to the proper handling procedure. ----End
Related Information
None
5.30 LSOOP
Description
Output Optical Power It includes: l l l LSOOPMAX: stands for the maximum value during a period of time. LSOOPMIN: stands for the minimum value during a period of time. LSOOPCUR: stands for the current value.
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal transmission of services.

The hardware checks the optical module and then the software converts the check result into LSOOP value to show the output optical power performance of the laser in a board.
Related Alarms
Alarm Name OUT_PWR_HIGH OUT_PWR_LOW TF Correlation It is generated when the optical power output by board is higher than the upper threshold. It is generated when the optical power output by board is lower than the lower threshold. It is generated when the optical power output by board is 1dB lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm. Step 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. Step 3 If an alarm is generated, see the "Related Alarms". ----End
Related Information
None
5.31 LSTMP
Description
Laser Temperature It includes: l l l LSTMPMAX: stands for the maximum value during a period of time. LSTMPMIN: stands for the minimum value during a period of time. LSTMPCUR: stands for the current value.
Impact on System
None

Normally, the laser temperature is a stable value obtained by software through calculating the result outputted by the temperature detecting circuit in the laser.
Related Alarms
Alarm Name LTEMP_OVER Correlation It is generated when the laser temperature exceeds the pre-set threshold.
Procedure
Step 1 If the LTEMP_OVER alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.32 MSBBE
Description
MS Background Block Error
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name B2_EXC B2_SD Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the threshold. Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the signal degrade (SD) threshold.
5-28
Alarm Name MS_AIS
Correlation 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. Out of frame on receiving line. This alarm is generated when the heads of consecutive five frames fail to be detected. Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3ms.
R_OOF R_LOF
Procedure
Step 1 Refer to the method of handling the B2_EXC. ----End
Related Information
None
5.33 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 rectify the problem in a timely manner because the bit errors have severely affected the signal transmission quality. In addition, the B2_EXC and B2_SD alarms may be generated.

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. While the consecutive severely errored second means the severely errored second appears consecutively, accompanied by the B2_EXC alarm. It might result in service interruption.
Related Alarms
Alarm Name B2_EXC Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the threshold.
Issue 08 (2011-10-30)
5-29
Alarm Name B2_SD
Correlation Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the signal degrade (SD) threshold. 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. Out of frame on receiving line. This alarm is generated when the heads of consecutive five frames fail to be detected. Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3ms.
MS_AIS
R_OOF R_LOF
Procedure
Related Information
None
5.34 MSES
Description
MS Errored Second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. The MS errored second means there are more than one error block transmitted in this second.
Related Alarms
Alarm Name B2_EXC Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the threshold.
5-30
Alarm Name B2_SD
Correlation Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the signal degrade (SD) threshold. 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. Out of frame on receiving line. This alarm is generated when the heads of consecutive five frames fail to be detected. Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3ms.
MS_AIS
R_OOF R_LOF
Procedure
Related Information
None
5.35 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.

The multiplex section errors are detected by checking the B2 byte. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Issue 08 (2011-10-30)
5-31
Related Alarms
Alarm Name MS_RDI Correlation Multiplex section remote defect indication alarm. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDM-side receive part of the opposite station is faulty. Multiplex section remote error indication. The alarm is generated when the remote end detects the bit error block.
MS_REI
Procedure
Step 1 Refer to the method of handling the MS_RDI. ----End
Related Information
None
5.36 MSFECSES
Description
MS Far End Consecutive Severely Errored Second
Impact on System

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, and it is accompanied by the B2_EXE alarm. It might result in service interruption. The far end consecutive severely errored second refers to the consecutive severely errored second detected at the opposite end.
5-32
Issue 08 (2011-10-30)
Related Alarms
MS_REI
Procedure
Related Information
None
5.37 MSFEES
Description
MS Far End Errored Second
Impact on System

The multiplex section errors are detected by checking the B2 byte. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
Alarm Name MS_RDI Correlation Multiplex section remote defect indication alarm. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDM-side receive part of the opposite station is faulty.
Issue 08 (2011-10-30)
Alarm Name MS_REI
Correlation Multiplex section remote error indication. The alarm is generated when the remote end detects the bit error block.
Procedure
Related Information
None
5.38 MSFESES
Description
MS Far End Severely Errored Second
Impact on System

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
MS_REI
5-34
Issue 08 (2011-10-30)
Procedure
Related Information
None
5.39 MSSES
Description
MS Severely Errored Second
Impact on System

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
Alarm Name B2_EXC B2_SD Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the threshold. Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the signal degrade (SD) threshold. 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. Out of frame on receiving line. This alarm is generated when the heads of consecutive five frames fail to be detected. Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3ms.
MS_AIS
R_OOF R_LOF
Issue 08 (2011-10-30)
5-35
Procedure
Related Information
None
5.40 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.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name B2_EXC B2_SD Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the threshold. Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceeds the signal degrade (SD) threshold. 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. Loss of signal on receiving line. This alarm is generated when the receive side receives no signals. Multiplex section remote defect indication alarm. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDM-side receive part of the opposite station is faulty.
MS_AIS
R_LOS MS_RDI
5-36
Alarm Name MS_REI
Correlation Multiplex section remote error indication. The alarm is generated when the remote end detects the bit error block.
Procedure
Related Information
None
5.41 ODU_PM_BBE
Description
ODU PM Section Background Block Error
Impact on System

ODU PM Section errors are detected by checking the received parity bits. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name PM_BIP8_OVER Correlation 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. 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.
PM_BIP8_SD
Issue 08 (2011-10-30)
5-37
Procedure
Step 1 Refer to the method of handling the PM_BIP8_SD. ----End
Related Information
None
5.42 ODU_PM_BBER
Description
ODU PM Section Ratio of Background Block Error
Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

ODU PM section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the ODU PM section refers to the ratio of the number of background block errors of the ODU PM section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second].
Related Alarms
PM_BIP8_SD
Procedure
Related Information
None
5.43 ODU_PM_BIP8
Description
ODU PM Section BIP8
Impact on System

This performance event shows the number of errors that a board with an OTN interface detects in path monitoring through the BIP8 check. Normally, the performance value should be zero.
Related Alarms
PM_BIP8_SD
Procedure
Related Information
None
5.44 ODU_PM_ES
Description
ODU PM Section Errored Second
Impact on System

ODU PM Section error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
PM_BIP8_SD
Procedure
Related Information
None
5.45 ODU_PM_FEBBE
Description
ODU PM Section Far End Background Block Error
Impact on System
5-40
Issue 08 (2011-10-30)

ODU PM Section error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name PM_BDI Correlation ODU PM section backward defect indication. The alarm is transferred in the upstream direction of the services, indicating the detected signal failure. ODU PM section backward error indication. If the board detects that the input signals contain the PM-BIP8 bit errors, it inserts the PM_BEI alarm back to the upstream board. The alarm is generated when the upstream station detects that the BEI flag in the OCH-OH of the PM section of the received signals is true.
PM_BEI
Procedure
Step 1 Refer to the method of handling the PM_BEI. ----End
Related Information
None
5.46 ODU_PM_FEBBER
Description
ODU PM Section Ratio of Far End Background Block Error
Impact on System

ODU PM section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the ODU PM section refers to the ratio of the number of background block errors of the ODU PM section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second]. And the ratio of far end background block error refers to the ratio of background block error detected at the opposite end.
Related Alarms
PM_BEI
Procedure
Related Information
None
5.47 ODU_PM_FEES
Description
ODU PM Section Far End Errored Second
Impact on System

ODU PM Section error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
Alarm Name PM_BDI Correlation ODU PM section backward defect indication. The alarm is transferred in the upstream direction of the services, indicating the detected signal failure.
5-42
Alarm Name PM_BEI
Correlation ODU PM section backward error indication. If the board detects that the input signals contain the PM-BIP8 bit errors, it inserts the PM_BEI alarm back to the upstream board. The alarm is generated when the upstream station detects that the BEI flag in the OCH-OH of the PM section of the received signals is true.
Procedure
Related Information
None
5.48 ODU_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.

Error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
PM_BEI
Issue 08 (2011-10-30)
5-43
Procedure
Related Information
None
5.49 ODU_PM_FESESR
Description
ODU PM Section Ratio of Far End Severely Errored Second
Impact on System

Bit errors are detected by checking the received parity bits. Severely errored second (SES) refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time. Far end severely errored second ratio refers to the ratio of errored seconds that are detected at the far end.
Related Alarms
PM_BEI
Procedure
Related Information
None
5.50 ODU_PM_FEUAS
Description
ODU PM Section Unavailable 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.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.And the far end unavailable second refers to the unavailable second detected at the opposite end.
Related Alarms
PM_BEI
Procedure
Related Information
None
Issue 08 (2011-10-30)
5-45
5.51 ODU_PM_SES
Description
ODU PM Section Severely Errored Second
Impact on System

ODU PM Section error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
PM_BIP8_SD
Procedure
Related Information
None
5.52 ODU_PM_SESR
Description
ODU PM Section Ratio of Severely Errored Second
5-46
Issue 08 (2011-10-30)
Impact on System

Bit errors are detected by checking the received parity bits. Severely errored second (SES) refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
PM_BIP8_SD
Procedure
Related Information
None
5.53 ODU_PM_UAS
Description
ODU PM Section Unavailable Second
Impact on System

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 10 seconds. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 10 seconds.
Related Alarms
PM_BIP8_SD
Procedure
Related Information
None
5.54 ODU_TCMn_BBE
Description
ODU 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 resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU TCMn Section errors are detected by checking the received parity bits. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name ODU_TCMn_DEG Correlation ODU TCMn burst-mode signal degradation. The unit reports this alarm when bit errors are of burst distribution and the signal degradation or bit error count crosses the threshold.
5-48
Issue 08 (2011-10-30)
Alarm Name ODU_TCMn_EXC
Correlation ODU TCMn Poisson-mode excessive bit errors. The unit reports this alarm when bit errors are of Poisson distribution and the signal degradation or bit error count crosses the threshold.
Procedure
Step 1 Check on the T2000 whether there are a great amount of BIP8 bit errors of the TCM section in the input signals on the client side or not. If yes, rectify the fault on the client-side equipment. Step 2 If the performance keeps deteriorating, refer to the handling procedure for the ODU_TCMn_DEG or ODU_TCMn_EXC alarm. ----End
Related Information
None
5.55 ODU_TCMn_BBER
Description
ODU 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 resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU TCMn section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the ODU TCMn section refers to the ratio of the number of background block errors of the ODU TCMn section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(PUAS-cSES) x blocks per second].
Related Alarms
Alarm Name ODU_TCMn_DEG Correlation ODU TCMn burst-mode signal degradation. The unit reports this alarm when bit errors are of burst distribution and the signal degradation or bit error count crosses the threshold.
5-49
Issue 08 (2011-10-30)
Alarm Name ODU_TCMn_EXC
Correlation ODU TCMn Poisson-mode excessive bit errors. The unit reports this alarm when bit errors are of Poisson distribution and the signal degradation or bit error count crosses the threshold.
Procedure
Related Information
None
5.56 ODU_TCMn_BIAES
Description
ODU TCMn Section Backward Incoming Alignment Errored Second
Impact on System
There are errors in frame alignment. Determine the cause and resolve the problem in a timely manner to ensure the signal transmission quality.

ODU TCMn section backward incoming alignment errored second are detected by checking the backward input frame alignment bits. Backward incoming alignment errored second refers to the second where more than one backward input frame alignment errors are generated.
Related Alarms
None
Procedure
Step 1 Check on the T2000 whether the input optical power of the optical interface is within the normal range. For the optical power specifications of the board, refer to the Product Description. If the input optical power is abnormal, refer to the methods for handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
Step 2 If the performance event persists, refer to the description on bit error fault handling in the Troubleshooting. ----End
Related Information
None
5.57 ODU_TCMn_ES
Description
ODU 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 resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU TCMn Section error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
Alarm Name ODU_TCMn_DEG Correlation ODU TCMn burst-mode signal degradation. The unit reports this alarm when bit errors are of burst distribution and the signal degradation or bit error count crosses the threshold. ODU TCMn Poisson-mode excessive bit errors. The unit reports this alarm when bit errors are of Poisson distribution and the signal degradation or bit error count crosses the threshold.
ODU_TCMn_EXC
Procedure
Related Information
None
5.58 ODU_TCMn_FEBBE
Description
ODU 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 alarms are reported on the opposite NE, there is no impact on the system. You, however, need to determine the cause and resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU TCMn Section error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected in the opposite end.
Related Alarms
None
Procedure
Step 1 Check on the T2000 whether the input optical power of the optical interface is within the normal range. For the optical power specifications of the board, refer to the Product Description. If the input optical power is abnormal, refer to the methods for handling the IN_PWR_HIGH and IN_PWR_LOW alarms. Step 2 If the performance event persists, refer to the description on bit error fault handling in the Troubleshooting. ----End
Related Information
None
5.59 ODU_TCMn_FEBBER
Description
ODU 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 resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU TCMn section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Far end background block error ratio of the ODU TCMn section refers to the ratio of the number of far end background block errors of the ODU TCMn section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].
Related Alarms
None
Procedure
5.60 ODU_TCMn_FEES
Description
ODU 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 resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU Backward error indication of the TCMn section is determined by the BEI that is inserted at the far end. Far end errored second refers to the second where the checked signals contain at least one block error at the far end.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODU_TCMn_SES. ----End
Related Information
None
5.61 ODU_TCMn_FESES
Description
ODU 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 resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus to ensure the signal transmission quality.

ODU Far end severely errored second of the TCMn section is determined by the BEI that is inserted at the far end. Far end severely errored second refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. The fiber line may be faulty.
Related Alarms
None
Procedure
Related Information
None
5.62 ODU_TCMn_FESESR
Description
ODU 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 resolve the problem in a timely manner because the bit errors have affected the signal transmission quality.

Far end severely errored second refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. FESESR refers to the ratio of the FESES count in a certain period to the total available time.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODU_TCMn_SESR. ----End
Related Information
None
5.63 ODU_TCMn_FEUAS
Description
ODU TCMn Section Unavailable Second
Impact on System
The far-end services are not available.

Unavailable seconds are generated when the number of bit errors at the far end is very large.
Related Alarms
Alarm Name ODU_TCMn_BDI Correlation ODU TCMn backward defect indication. The unit reports this alarm when the BDI bit of a TCMn overhead stays "1" for five consecutive frames. The alarm travels upstream, which indicates the detected signal failure.
Issue 08 (2011-10-30)
5-55
Procedure
Step 1 Refer to the method of handling the ODU_TCMn_BDI. ----End
Related Information
None
5.64 ODU_TCMn_IAES
Description
ODU TCMn Section Incoming Alignment Errored Second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.

There is the OTU_LOF alarm at the upstream station.
Related Alarms
Alarm Name OTU_LOF Correlation OTU frame loss. The upstream station detects the LOF alarm and then inserts IAE. The local station reports ODU_TCMn_IAES.
Procedure
Step 1 Refer to the method of handling the OTU_LOF. ----End
Related Information
None
5.65 ODU_TCMn_SES
Description
ODU TCMn Section Severely Errored Second
Impact on System
There are bit errors in the services. Determine the cause and resolve the problem in a timely manner because the bit errors have affected the signal transmission quality.

It is obtained by calculating the BIP-8 of ODUk TCMn section. Severely errored second (SES) refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. The fiber line may be faulty.
Related Alarms
ODU_TCMn_EXC
Procedure
Step 1 Refer to the method of handling the ODU_TCMn_DEG or ODU_TCMn_EXC. ----End
Related Information
None
5.66 ODU_TCMn_SESR
Description
ODU TCMn Section Ratio of Severely Errored Second
Impact on System

It is obtained by calculating the BIP-8 of ODU TCMn section.
Related Alarms
ODU_TCMn_EXC
Procedure
Step 1 Refer to the method of handling the ODU_TCMn_DEG or ODU_TCMn_EXC. ----End
Related Information
None
5.67 ODU_TCMn_UAS
Description
ODU TCMn Section Unavailable Second
Impact on System

Related Alarms
ODU_TCMn_EXC
5-58
Issue 08 (2011-10-30)
Procedure
Step 1 Refer to the method of handling the ODU_TCMn_DEG or ODU_TCMn_EXC alarm. ----End
Related Information
None
5.68 OOPRL
Description
Optical Output Power Return Loss It includes: l l l OOPRLMAX: maximum value of the optical output power return loss within a time period OOPRLMIN: minimum value of the optical output power return loss within a time period OOPRLCUR: current value of the optical output power return loss
Impact on System
Services may be interrupted.

The fiber near the board is cut, improperly bent, or squeezed, or the fiber connector is improperly connected to the board interface.
Related Alarms
Alarm Name RL_CRITICAL_HI RL_CRITICAL_LO W Correlation This alarm is generated when the return loss is higher than the upper threshold of the return loss alarm. This alarm is generated when the return loss is lower than the lower threshold of the return loss alarm.
Procedure
Step 1 Refer to the method of handling the RL_CRITICAL_HI or RL_CRITICAL_LOW. ----End
Related Information
None
5.69 OTU_BBE
Description
OTU Background Block Error
Impact on System

OTU errors are detected by checking the received parity bits. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name SM_BIP8_OVER Correlation 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. OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section in the optical channel data unit layer exceeds the degraded threshold.
SM_BIP8_SD
Procedure
Step 1 Refer to the method of handling the SM_BIP8_SD. ----End
Related Information
None
5.70 OTU_BBER
Description
OTU Ratio of Background Block Error
5-60
Issue 08 (2011-10-30)
Impact on System

OTU section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the OTU section refers to the ratio of the number of background block errors of the OTU section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].
Related Alarms
SM_BIP8_SD
Procedure
Related Information
None
5.71 OTU_ES
Description
OTU Errored Second
Impact on System

OTU error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
SM_BIP8_SD
Procedure
Related Information
None
5.72 OTU_FEBBE
Description
OTU SM Section Far End Background Block Error
Impact on System

OTU SM Section error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
5-62
Issue 08 (2011-10-30)
Related Alarms
Alarm Name SM_BDI Correlation OTU SM section backward defect indication. The alarm is transferred in the upstream direction of the services, indicating the detected signal failure. OTU SM section backward error indication. If the board detects that the input signals contain the SM-BIP8 bit errors, it inserts the SM_BEI alarm back to the upstream board. The alarm is generated when the upstream station detects that the BEI flag in the OCH-OH of the SM section of the received signals is true.
SM_BEI
Procedure
Step 1 Refer to the method of handling the SM_BEI. ----End
Related Information
None
5.73 OTU_FEBBER
Description
OTU SM Section Ratio of Far End Background Block Error
Impact on System

OTU SM section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the OTU SM section refers to the ratio of the number of background block errors of the OTU SM section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second]. And the ratio of far end background block error refers to the ratio of background block error detected at the opposite end.
Issue 08 (2011-10-30)
5-63
Related Alarms
SM_BEI
Procedure
Related Information
None
5.74 OTU_FEES
Description
OTU SM Section Far End Errored Second
Impact on System

OTU SM Section error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
Alarm Name SM_BDI Correlation OTU SM section backward defect indication. The alarm is transferred in the upstream direction of the services, indicating the detected signal failure.
5-64
Alarm Name SM_BEI
Correlation OTU SM section backward error indication. If the board detects that the input signals contain the SM-BIP8 bit errors, it inserts the SM_BEI alarm back to the upstream board. The alarm is generated when the upstream station detects that the BEI flag in the OCH-OH of the SM section of the received signals is true.
Procedure
Related Information
None
5.75 OTU_FESES
Description
OTU SM Section Far End Severely Errored Second
Impact on System

OTU SM Section error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
SM_BEI
Issue 08 (2011-10-30)
5-65
Procedure
Related Information
None
5.76 OTU_FESESR
Description
OTU SM Section Ratio of Far End Severely Errored Second
Impact on System

Bit errors are detected by checking the received parity bits. Severely errored second (SES) refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time. Far end severely errored second ratio refers to the ratio of errored seconds that are detected at the far end.
Related Alarms
SM_BEI
Procedure
Related Information
None
5.77 OTU_FEUAS
Description
OTU SM Section Unavailable Second
Impact on System

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.And the far end unavailable second refers to the unavailable second detected at the opposite end.
Related Alarms
SM_BEI
Procedure
Related Information
None
Issue 08 (2011-10-30)
5-67
5.78 OTU_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.

Error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
SM_BIP8_SD
Procedure
Related Information
None
5.79 OTU_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.

Bit errors are detected by checking the received parity bits. Severely errored second (SES) refers to the second where the checked signals contain a minimum of 30% block errors or at least one defect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
SM_BIP8_SD
Procedure
Related Information
None
5.80 OTU_SM_BIP8
Description
OTU SM Section BIP8
Impact on System

This performance event shows the number of errors that a board with an OTN interface detects in section monitoring through the BIP8 check. Normally, it should be zero.
Issue 08 (2011-10-30)
5-69
Related Alarms
SM_BIP8_SD
Procedure
Related Information
None
5.81 OTU_UAS
Description
OTU Unavailable Second
Impact on System

Related Alarms
SM_BIP8_SD
5-70
Issue 08 (2011-10-30)
Procedure
Related Information
None
5.82 OTU_IAES
Description
OTU SM Section Incoming Alignment Errored Second.
Impact on System
Generally, the services are not affected. If the slip frame problem is severe, bit errors might occur in the services.

IAE is defined to allow the S-CMEP ingress point to inform its peer S-CMEP egress point that an alignment error in the incoming signal has been detected.
Related Alarms
Alarm Name SM_IAE Correlation The optical channel transport unit (OTU) layer SM section introduced alignment errors alarm. When the board detects the slip frame, it inserts the SM_IAE flag to the downstream board. The SM_IAE alarm is reported when the downstream board detects that the received OTN frames contains the IAE flag.
Procedure
Step 1 Refer to the method of handling the SM_IAE. ----End
Related Information
None
Issue 08 (2011-10-30)
5-71
5.83 OTU_BIAES
Description
OTU SM Section Backward Incoming Alignment Errored Second.
Impact on System
Generally, the services are not affected. If the slip frame problem is severe, bit errors might occur in the services.

It is used to convey in the upstream direction an incoming alignment error (IAE) condition that is detected in the corresponding OTUk section monitoring sink in the IAE overhead.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.84 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 l l PCLSOPMAX: stands for the maximum value during a period of time. PCLSOPMIN: stands for the minimum value during a period of time. PCLSOPCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals, selects a channel of signal to check its optical power.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.85 PCLSSN
Description
Per-channel OSNR, indicating OSNR of a channel of signal monitored by the spectrum analyzer unit. It includes: l l l PCLSSNMAX: stands for the maximum value during a period of time. PCLSSNMIN: stands for the minimum value during a period of time. PCLSSNCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals, checks and calculates the OSNR of a channel of signal.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.86 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 l l PCLSWLMAX: stands for the maximum value during a period of time. PCLSWLMIN: stands for the minimum value during a period of time. PCLSWLCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals, selects a channel of signal to check its central wavelength.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.87 PCLSWLO
Description
Per-channel Central Wavelength Deviation, indicating 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
5-74
PCLSWLOMAX: stands for the maximum value during a period of time.

l l
PCLSWLOMIN: stands for the minimum value during a period of time. PCLSWLOCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals, checks and calculates the central wavelength deviation of a channel of signal.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
5.88 PMUTMP
Description
PMU board Environment Temperature It includes: l l l PMUTMPMAX: stands for the maximum value during a period of time. PMUTMPMIN: stands for the minimum value during a period of time. PMUTMPCUR: stands for the current value.
Impact on System
Services on the board may be affected when the ambient temperature of the board exceeds the threshold.

It is generated by the temperature check circuit of the PMU board to show the working ambient temperature of PMU.
Related Alarms
Alarm Name TEMP_ALARM Correlation The temperature threshold crossing alarm. This alarm is generated when the board ambient temperature crosses the board temperature threshold.
Procedure
Step 1 If the TEMP_ALARM alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.89 PUMPOOP
Description
Pump Output Optical Power It includes: l l l PUMPOOPMAX: stands for the maximum value during a period of time. PUMPOOPMIN: stands for the minimum value during a period of time. PUMPOOPCUR: stands for the current value.
Impact on System
None

The check circuit of the pump laser performs a check and then the software converts the check result into PUMPOOP to show the pump optical power of Raman amplifier board.
Related Alarms
Alarm Name OUT_PWR_HIGH Correlation Output optical power too high alarm. This alarm is generated when the laser output optical power crosses the upper threshold.
5-76
Issue 08 (2011-10-30)
Procedure
Step 1 If the OUT_PWR_HIGH alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
5.90 PUMPTMP
Description
Pump Laser Temperature It includes: l l l PUMPTMPMAX: denotes the maximum value during a period of time. PUMPTMPMIN: denotes the minimum value during a period of time. PUMPTMPCUR: denotes the current value.
Impact on System
Services on the board may be affected when the ambient temperature of the board exceeds the threshold.

To obtain this performance event, perform a check by the check circuit. Then calculate the result with software for conversion.
Related Alarms
Alarm Name PUM_TEM_ALM Correlation Working temperature of the pump laser exceeds the threshold. This alarm is generated when the pump laser operating temperature of the optical amplifier unit exceeds the threshold.
Procedure
Step 1 Refer to the method of handling the PUM_TEM_ALM. ----End
Related Information
None
5.91 RSBBE
Description
RS Background Block Error
Impact on System

The regenerator section errors are detected by checking the B1 byte. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name B1_EXC Correlation Regenerator section (B1) excessive errors. The alarm is generated when the received signals in SDH frame degrades and the B1 bit errors in the multiplex section exceeds the threshold. Regenerator section (B1) excessive errors. The alarm is generated when the received signals in SDH frame degrades and the B1 bit errors in the multiplex section exceeds the signal degrade (SD) threshold.
B1_SD
Procedure
Related Information
None
5.92 RSCSES
Description
RS Consecutive Severely Errored Second
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. While the consecutive severely errored second means the severely errored second appears consecutively, accompanied by the B1_EXC alarm. It might result in service interruption.
Related Alarms
B1_SD
Procedure
Related Information
None
5.93 RSES
Description
RS Errored Second
Impact on System

The regenerator section errors are detected by checking the B1 byte. The RS errored second means there are more than one error block transmitted in this second.
Related Alarms
B1_SD
Procedure
Related Information
None
5.94 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. The R_LOF alarm is generated.

Out-Of-Frame (OOF) refers to the loss of framing bytes and the OOF second contains at least one OOF. OOF turns to be LOF (Loss Of Frame) if it lasts more than 3ms.
Related Alarms
Alarm Name R_OOF Correlation Out of frame on receiving line. This alarm is generated when the headers of consecutive five frames fail to be detected. Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3ms.
R_LOF
Procedure
Step 1 Check whether the fibers and connectors are properly installed. Clean the fiber connectors. Step 2 Check whether the input optical power of the input interface of the board is within the normal range by using an optical power meter. For the optical power specifications of a certain board, see the Product Description. If the power is not within the normal range, add proper attenuation by adding a fix attenuator or a variable optical attenuator (VOA). Step 3 Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
5.95 RSSES
Description
RS Severely Errored Second
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored second, there is at least one defect or 30% of blocks are error blocks.
Issue 08 (2011-10-30)
5-81
Related Alarms
B1_SD
Procedure
Related Information
None
5.96 RSUAS
Description
RS Unavailable Second
Impact on System

The regenerator section errors are detected by checking the B1 byte. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
5-82
Issue 08 (2011-10-30)
Related Alarms
B1_SD
Procedure
Related Information
None
5.97 SUMIOP
Description
Input Optical Power It includes: l l l SUMIOPMAX: stands for the maximum value during a period of time. SUMIOPMIN: stands for the minimum value during a period of time. 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 singlewavelength optical signals that are output by the board may be lost. As a result, bit errors are generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate the result with software for conversion.
SUMIOP is the total input optical power of demultiplexer and the optical amplifier board.
Related Alarms
Alarm Name IN_PWR_HIGH IN_PWR_LOW SUM_INPWR_HI SUM_INPWR_LO W Correlation It is generated when the optical power input by board is higher than the upper threshold. It is generated when the optical power input by board is lower than the lower threshold. It is generated when the detected total input optical power is higher than the upper threshold. It is generated when the detected total input optical power is lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH or SUM_INPWR_HI alarm. Step 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. Step 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.
5.98 SUMOOP
Description
Output Optical Power It includes: l l l
5-84
SUMOOPMAX: stands for the maximum value during a period of time. SUMOOPMIN: stands for the minimum value during a period of time. 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 very 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 very low. As a result, bit errors are generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate the result with software for conversion. SUMOOP is the total optical power output by the multiplexer and the optical amplifier board. In a multiplexer unit, the input signals pass the multiplexer and then output the total optical power through the "OUT" port, while in an amplifier board, the input signals pass the amplifier and then output the total optical power through the "OUT" port.
Related Alarms
Alarm Name OUT_PWR_HIGH OUT_PWR_LOW SUM_OUTPWR_H I SUM_OUTPWR_L OW Correlation It is generated when the optical power output by board is higher than the upper threshold. It is generated when the optical power output by board is lower than the lower threshold. It is generated when the detected total input optical power is higher than the upper threshold. It is generated when the optical power output by board is 1dB lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH or SUM_OUTPWR_HI alarm. Step 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 or SUM_OUTPWR_LOW alarm. Step 3 If an alarm is generated, refer to the proper handling procedure. ----End
Issue 08 (2011-10-30)
5-85
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.
5.99 WCV
Description
Pump Laser Working Current, also called Pump Laser Driver Current or Pump Laser Bias Current. It includes: l l l WCVMAX: stands for the maximum value during a period of time (in 1mA). WCVMIN: stands for the minimum value during a period of time (in 1mA). WCVCUR: stands for the current value (in 1mA).
Impact on System
When the pump laser works normally, there is no impact on the services. If an alarm is generated, determine the cause.

WCV indicates the pump laser driver current of an optical amplifier board. The optical amplifier board amplifies the input signal using the pump laser driven by pump laser working current.
Related Alarms
Alarm Name PUM_BCM_ALM Correlation 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. The board reports this alarm when the pump laser driver current is higher than the termination threshold due to laser aging.
LSR_WILL_DIE
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the handling procedure of the alarm. Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
A Glossary
A
A
Auto negotiation
Glossary
The negotiation mode that is set on the communication equipment. When the auto negotiation mode is enabled, the equipment sets its working mode and rate through negotiation based on the mode and rate of the opposite equipment.
B
Bandwidth Information-carrying capacity of a communication channel. Analog bandwidth is the range of signal frequencies that can be transmitted by a communication channel or network. The ratio of the errored bit count to the transmitted bit count in a certain period of time. In the digital communication system, bit error rate is the ratio of the errored bit count to the transmitted bit count in a typical period of time. The act of sending a frame addressed to all stations on the network.
Bit Error Rate
Broadcast
C
Channel Client Server Clock tracing Concatenate The trail on the channel layer. A terminal device (computer or workstation) that sends instructions to the server and displays the results through the user interface. The method to keep the time on each node being synchronized with a clock source in a network. A combination process. The process combines multiple virtual containers (VCs). Then, the capacity of the combined VCs can used as the capacity of a single VC and the bit sequence is complete. A "transport entity" which consists of an associated pair of "unidirectional connections" capable of simultaneously transferring information in opposite directions between their respective inputs and outputs.
Connection
Issue 08 (2011-10-30)
A-1
A Glossary
D
DCM Dispersion Compensation Module. A module, which contains dispersion compensation fibers to compensate for the positive dispersion of transmitting fiber.
E
EDFA An optical device that amplifies the optical signals. The device uses a short length of optical fiber doped with the rare-earth element Erbium and the energey level jump of Erbium ions activated by pump sources. When the amplifier passes the external light source pump, it amplifies the optical signals in a specific wavelength range. A data link level protocol comprising the OSI model's bottom two layers. It is a broadcast networking technology that can use several different physical media, including twisted pair cable and coaxial cable. Ethernet usually uses CSMA/CD. TCP/IP is commonly used with Ethernet networks.
Ethernet
F
Fiber jumper Forward Error Correction The fiber which is used to connect the subrack with the ODF, subrack or connect the board interfaces. A data encoding technology. It is a method to control errors in communication. In this method, extra (redundant) bits are inserted into the data stream towards other equipment to control errors. The equipment at the receive end can use these redundant bits to detect errors and correct errors if possible. A cyclic set of consecutive time slots in which the relative position of each time slot can be identified. Pertaining to both parties that can send and receive data at the same time on the communication link.
Frame Full duplex
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. A process that multiplexes multiple channels of low-rate signals into one or several channels of required signals.
Grooming
L
Label Laser A mark on a cable, a subrack, or a cabinet for identification. The device that generates the directional light covering a narrow range of wavelengths. Laser light is more coherent than ordinary light. Semiconductor diode lasers are the used light source in fiber-optic system.
A-2
Issue 08 (2011-10-30)
A Glossary
M
Main Topology The default T2000 client interface, a basic component of the human-machine interactive interface. The topology clearly shows the structure of the network, the alarms of different NEs, subnets in the network, the communication status as well as the basic network operation status. All topology management functions are accessed here. A procedure by which multiple lower order path layer signals are adapted into a higher order path or the multiple higher order path layer signals are adapted into a multiplex section.
Multiplexing
O
Opposite station/ opposite station board The opposite station is a service-specific concept. As shown in Figure A-1, if station A is the local station, station C is the opposite station for service 1 and station B is the opposite station for service 2. The opposite station board is specific to the transmitting or receiving of a service. For service 2, the board opposite to OTU5 is OTU2. For service 3, the board opposite to OTU6 is OTU4. Similarly, for service 1, the board opposite to OTU1 is OTU3. Figure A-1 Service flow
1
Station A OTU1
O A D M F I U F I U
Station B
O A D M O A D M F I U O A D M
Station C OTU3
F I U
OTU2
OTU4
Clinet WDM side side
O T U 5
2
O T U 6
3
Optical spectrum analyzer Optical switch OSNR Overhead
An instrument that scans the spectrum to record power, measures the value of loss insertion and tests the performance of the wavelength and optical signal noise ratio (OSNR) of each channel. A passive component possessing two or more ports which selectively transmits, redirects, or blocks optical power in an optical fiber transmission line. Optical Signal-to-Noise Ratio. Ratio of the optical power of the transmitted optical signal to the noise on the received signal. A message that is transmitted on the optical network layer and does not need to associate with a specific connection. For example, such an auxiliary channel can be used as a digital communication channel between management entities to transmit management data. 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-3
Pointer
Issue 08 (2011-10-30)
A Glossary
R
Regeneration Route 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. The path a trail takes.
S
S1 byte The byte defined in ITU-T to transmit the network synchronization status information.
T
T2000 A network management system that Huawei provides to manage transmission networks. The T2000 is located between the NE level and the network level in the telecommunication management network structure. That is, the T2000 is a subnetwork management system. The T2000 provides all management functions at the NE layer and some of the management functions at the network layer. Single timeslot on a E1 digital interfacethat is, a 64-kbps, synchronous, full-duplex data channel, typically used for a single voice connection. A type of transport entity, mainly engaged in transferring signal from the input of the trail source to the output of the trail sink, and monitoring the integrality of the transferred signal.
Timeslot Trail
U
Upstream station/ downstream station For the station where signals are received, the station where signals are transmitted and the station where signals just pass through are upstream stations. As shown in Figure A-2, service 1 traverses from station A, to station B, and finally to station C. Station A and station B are upstream stations of station C. The service signals can be ECC signals, GE signals, or orderwire signals. Conversely, station B and station C are downstream stations for station A. Figure A-2 Service flow
1
Station A OTU1
O A D M F I U F I U
Station B
O A D M O A D M F I U O A D M
Station C OTU3
F I U
OTU2
OTU4
Clinet WDM side side
O T U 5
2
O T U 6
3
A-4
Issue 08 (2011-10-30)
A Glossary
User
The user of the T2000 client, and the user and password define the corresponding authority of operation and management of the T2000.
W
Wander In telecommunication, wander are long-term random variations of the significant instants of a digital signal from their ideal positions.
Issue 08 (2011-10-30)
A-5
B Acronyms and Abbreviations
B
A AIS API B BDI BEI BIP BITS
Acronyms and Abbreviations
Alarm Indication Signal Access Point Identifiers
Backward Defect Indication Backward Error Indication Bit Interleaved Parity Building Integrated Timing Supply System
C CRC Cyclical Redundancy Check
D DAPI DSP Destination Access Point Identifier Digital Signal Processing
E EDFA Erbium-Doped Fiber Amplifier
F FEC Forward Error Correction
Issue 08 (2011-10-30)
B-1
FPGA
Field Programmable Gate Array
G GE Gigabit Ethernet
H HP HDB HPI Higher Order Path High Density Bipolar Code Higher Order Path Interface
I IAE Incoming Alignment Error
L LACP LOF LOS Link Aggregation Control Protocol Loss Of Frame Loss Of Signal
M MFAS MS MultiFrame Alignment Signal Multiplex Section
O OCI ODU OOF OPU OTN Open Connection Indication Optical Channel Data Unit Out Of Frame Optical Channel Payload Unit Optical Transmission Network
P PIN Positive Intrinsic Negative
B-2
Issue 08 (2011-10-30)
PM PT
Path Monitoring Payload Type
R RDI REI Remote Defect Indication Remote Error Indication
S SAPI SD SDH SES SF SM Source Access Point Identifiers Signal Degrade Synchronous Digital Hierarchy Severely Errored Second Signal Fail Section Monitoring
T TCM TIM TTI Tandem Connection Monitoring Trace Identifier Mismatch Trail Trace Identifier
U UAS Unavailable Second
Issue 08 (2011-10-30)
B-3

00482837-Alarms and Performance Events Reference (V100R007 - 08)

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

00482837-Alarms and Performance Events Reference (V100R007 - 08)

Hochgeladen von

Copyright:

Verfügbare Formate

OptiX BWS 1600G Backbone DWDM Optical Transmission System V100R007

Alarms and Performance Events Reference

Issue Date Part Number

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

4 Performance Event List.............................................................................................................4-1

5 Performance Event Processing.................................................................................................5-1

A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Updates in Issue 08 (2011-10-30) Based on Product Version V100R007

Updates in Issue 07 (2011-03-15) Based on Product Version V100R007

About This Document

Updates in Issue 06 (2010-05-30) Based on Product Version V100R007

Updates in Issue 05 (2009-12-30) Based on Product Version V100R007

Updates in Issue 04 (2009-11-05) Based on Product Version V100R007

Chapter 4 Performance Event List

Updates in Issue 03 (2009-06-22) Based on Product Version V100R007

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Updates in Issue 02 (2009-04-25) Based on Product Version V100R007

Updates in Issue 01 (2008-12-18) Based on Product Version V100R007

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Updates in Issue 03 (2008-08-30) Based on Product Version V100R006

Updates in Issue 02 (2008-02-29) Based on Product Version V100R006

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Chapter Chapter 3 Alarm Processing

Chapter 4 Performance Event List

Updates in Issue 01 (2007-11-30) Based on Product Version V100R006

Chapter 4 Performance Event List

Updates in Issue 03 (2007-09-30) Based on Product Version V100R005

About This Document

Chapter Chapter 1 Overview Chapter 2 Alarm List

4 Performance Event List

Updates in Issue 02 (2007-05-30) Based on Product Version V100R005

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Chapter Chapter 1 Alarm and Performance Event Lists

Chapter 2 Alarm Processing

Updates in Issue 01 (2007-01-20) Based on Product Version V100R005

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Chapter Chapter 1 Alarm and Performance Event Lists

Chapter 2 Alarm Processing

Chapter 3 Performance Event Processing

Some bugs in former version are fixed.

Updates in Issue 02 (2006-07-30) Based on Product Version V100R004

Updates in Issue 01 (2006-05-30) Based on Product Version V100R004

Updates in Issue 03 (2006-06-30) Based on Product Version V100R003

About This Document

Updates in Issue 02 (2006-01-15) Based on Product Version V100R003

Updates in Issue 01 (2005-12-10) Based on Product Version V100R003

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.