91501321 00482837 alarms and performance events reference v100r007 08

OptiX BWS 1600G Backbone DWDM Optical Transmission System

V100R007

Alarms and Performance Events Reference

Issue 08

Date 2011-10-30

Part Number 00482837

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Overview......................................................................................................................................1-11.1 Alarm Level.....................................................................................................................................................1-21.2 Alarm Category...............................................................................................................................................1-21.3 Performance Event Category..........................................................................................................................1-31.4 Alarm Signal Flow..........................................................................................................................................1-4

1.4.1 Overview................................................................................................................................................1-41.4.2 Non-Convergent OTU Processing Standard SDH Signals....................................................................1-61.4.3 Non-Convergent OTU Processing Standard OTN Signals....................................................................1-91.4.4 Convergent OTU Processing Standard SDH Signals...........................................................................1-121.4.5 Convergent OTU Processing Standard OTN Signals..........................................................................1-151.4.6 Regenerating OTU...............................................................................................................................1-181.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function.............................................1-201.4.8 Convergence OTU Processing the GE Standard Signals.....................................................................1-221.4.9 Non-Convergence OTU Board Processing the 10GE Standard Signals..............................................1-26

1.5 Suppression Relation of Alarms....................................................................................................................1-291.5.1 Suppression Relation of OTU Service Alarms on WDM Side............................................................1-291.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-12.1 Product Alarm List..........................................................................................................................................2-2

2.1.1 Alarm List A...........................................................................................................................................2-22.1.2 Alarm List B...........................................................................................................................................2-22.1.3 Alarm List C...........................................................................................................................................2-32.1.4 Alarm List D...........................................................................................................................................2-32.1.5 Alarm List E...........................................................................................................................................2-32.1.6 Alarm List F...........................................................................................................................................2-42.1.7 Alarm List H...........................................................................................................................................2-42.1.8 Alarm List I............................................................................................................................................2-42.1.9 Alarm List J............................................................................................................................................2-52.1.10 Alarm List K.........................................................................................................................................2-52.1.11 Alarm List L.........................................................................................................................................2-5

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference Contents

Issue 08 (2011-10-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

2.1.12 Alarm List M........................................................................................................................................2-52.1.13 Alarm List N.........................................................................................................................................2-62.1.14 Alarm List O.........................................................................................................................................2-62.1.15 Alarm List P.........................................................................................................................................2-92.1.16 Alarm List R.......................................................................................................................................2-102.1.17 Alarm List S.......................................................................................................................................2-112.1.18 Alarm List T.......................................................................................................................................2-122.1.19 Alarm List V.......................................................................................................................................2-132.1.20 Alarm List W......................................................................................................................................2-13

2.2 Board Alarm List...........................................................................................................................................2-132.2.1 D40 Board Alarm List..........................................................................................................................2-132.2.2 DCP Board Alarm List.........................................................................................................................2-142.2.3 ELOG/ELOGS Board Alarm List........................................................................................................2-142.2.4 ETMX/ETMXS Board Alarm List.......................................................................................................2-152.2.5 FDG Board Alarm List.........................................................................................................................2-162.2.6 FIU Board Alarm List..........................................................................................................................2-172.2.7 FMU Board Alarm List........................................................................................................................2-182.2.8 HBA Board Alarm List........................................................................................................................2-182.2.9 ITL Board Alarm List..........................................................................................................................2-182.2.10 LBE/LBES Board Alarm List............................................................................................................2-182.2.11 LBF/LBFS Board Alarm List.............................................................................................................2-192.2.12 LOG/LOGS Board Alarm List...........................................................................................................2-212.2.13 LQM Board Alarm List......................................................................................................................2-222.2.14 LU40 Board Alarm List.....................................................................................................................2-232.2.15 LU40S Board Alarm List...................................................................................................................2-242.2.16 LUR40/LUR40S Board Alarm List...................................................................................................2-262.2.17 LWC1 Board Alarm List....................................................................................................................2-262.2.18 LWF/LWFS Board Alarm List..........................................................................................................2-272.2.19 LWX Board Alarm List......................................................................................................................2-292.2.20 M40 Board Alarm List.......................................................................................................................2-292.2.21 MCA Board Alarm List......................................................................................................................2-302.2.22 MR2 Board Alarm List......................................................................................................................2-302.2.23 MWA Board Alarm List....................................................................................................................2-302.2.24 MWF Board Alarm List.....................................................................................................................2-302.2.25 OAU Board Alarm List......................................................................................................................2-302.2.26 OBU Board Alarm List......................................................................................................................2-312.2.27 OLP Board Alarm List.......................................................................................................................2-312.2.28 OPU Board Alarm List.......................................................................................................................2-312.2.29 PMU Board Alarm List......................................................................................................................2-312.2.30 RMU9 Board Alarm List....................................................................................................................2-322.2.31 RPC Board Alarm List.......................................................................................................................2-322.2.32 SC1/SC2 Board Alarm List................................................................................................................2-32

Contents

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystem


ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

2.2.33 SCC Board Alarm List.......................................................................................................................2-332.2.34 TMR/TMRS Board Alarm List..........................................................................................................2-342.2.35 TMX/TMXS Board Alarm List..........................................................................................................2-342.2.36 TMX40/TMX40S Board Alarm List..................................................................................................2-352.2.37 TRC1 Board Alarm List.....................................................................................................................2-372.2.38 V40 Board Alarm List........................................................................................................................2-372.2.39 VA4 Board Alarm List.......................................................................................................................2-382.2.40 VOA Board Alarm List......................................................................................................................2-382.2.41 WMU Board Alarm List....................................................................................................................2-382.2.42 WSD9 Board Alarm List....................................................................................................................2-382.2.43 WSM9 Board Alarm List...................................................................................................................2-382.2.44 WSMD2 Board Alarm List................................................................................................................2-392.2.45 WSMD4 Board Alarm List................................................................................................................2-39

3 Alarm Processing........................................................................................................................3-13.1 Common Alarm Processing............................................................................................................................3-2

3.1.1 ALM_DATA_RLOS..............................................................................................................................3-23.1.2 ALM_DATA_TLOS..............................................................................................................................3-43.1.3 B1_EXC.................................................................................................................................................3-53.1.4 BEFFEC_EXC.......................................................................................................................................3-73.1.5 CHAN_LOS...........................................................................................................................................3-93.1.6 FCSERRORS_OVER..........................................................................................................................3-113.1.7 IN_PWR_HIGH...................................................................................................................................3-133.1.8 IN_PWR_LOW....................................................................................................................................3-153.1.9 LINK_ERR...........................................................................................................................................3-183.1.10 LINK_STATUS.................................................................................................................................3-203.1.11 LOOP_ALM.......................................................................................................................................3-223.1.12 LSR_WILL_DIE................................................................................................................................3-233.1.13 MS_AIS..............................................................................................................................................3-253.1.14 MS_RDI.............................................................................................................................................3-263.1.15 MUT_LOS.........................................................................................................................................3-293.1.16 NEBD_XC_DIF.................................................................................................................................3-303.1.17 OA_LOW_GAIN...............................................................................................................................3-323.1.18 ODU_AIS...........................................................................................................................................3-343.1.19 OMS_FDI...........................................................................................................................................3-363.1.20 OPS_PS_INDI....................................................................................................................................3-373.1.21 OSC_LOS...........................................................................................................................................3-393.1.22 OTU_LOF..........................................................................................................................................3-403.1.23 OUT_PWR_HIGH.............................................................................................................................3-433.1.24 PM_BDI.............................................................................................................................................3-453.1.25 PM_BEI..............................................................................................................................................3-483.1.26 PM_BIP8_OVER...............................................................................................................................3-513.1.27 PORT_MODULE_OFFLINE............................................................................................................3-53



iii

3.1.28 POWERALM.....................................................................................................................................3-543.1.29 POWER_DIFF_DEFECT..................................................................................................................3-563.1.30 POWER_FAIL...................................................................................................................................3-573.1.31 PS.......................................................................................................................................................3-593.1.32 PUMP_COOL_EXC..........................................................................................................................3-613.1.33 R_DATA_LOST................................................................................................................................3-623.1.34 R_LOF................................................................................................................................................3-643.1.35 R_LOS................................................................................................................................................3-663.1.36 R_OOF...............................................................................................................................................3-693.1.37 R_SLIP...............................................................................................................................................3-723.1.38 REM_SF.............................................................................................................................................3-733.1.39 SECU_ALM.......................................................................................................................................3-753.1.40 SM_BEI..............................................................................................................................................3-753.1.41 SM_BIP8_OVER...............................................................................................................................3-793.1.42 SM_TIM.............................................................................................................................................3-803.1.43 SUM_INPWR_LOW.........................................................................................................................3-823.1.44 SUM_OUTPWR_LOW.....................................................................................................................3-833.1.45 T_DATA_LOST................................................................................................................................3-853.1.46 TD.......................................................................................................................................................3-863.1.47 TF.......................................................................................................................................................3-883.1.48 WRG_BD_TYPE...............................................................................................................................3-89

3.2 Alarm Processing..........................................................................................................................................3-903.2.1 AD_CHECK_FAIL..............................................................................................................................3-913.2.2 ALM_PIUA_OFFLINE.......................................................................................................................3-923.2.3 ALM_PIUB_OFFLINE.......................................................................................................................3-933.2.4 AU_AIS................................................................................................................................................3-943.2.5 AU_LOP...............................................................................................................................................3-963.2.6 B1_SD..................................................................................................................................................3-973.2.7 B2_EXC...............................................................................................................................................3-993.2.8 B2_SD................................................................................................................................................3-1013.2.9 BD_STATUS.....................................................................................................................................3-1023.2.10 BD_VER_NMAT.............................................................................................................................3-1033.2.11 BEFFEC_SD....................................................................................................................................3-1053.2.12 BOOTROM_BAD...........................................................................................................................3-1063.2.13 CFG_VERIFY..................................................................................................................................3-1073.2.14 CFGBD_FAIL..................................................................................................................................3-1083.2.15 CFGDATA_OUTRANGE...............................................................................................................3-1093.2.16 CHAN_ADD....................................................................................................................................3-1113.2.17 CLT_MM.........................................................................................................................................3-1123.2.18 COMMUN_FAIL.............................................................................................................................3-1133.2.19 DBMS_ERROR...............................................................................................................................3-1143.2.20 DBMS_PROTECT_MODE.............................................................................................................3-116

Contents



iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

3.2.21 DCM_INSUFF.................................................................................................................................3-1173.2.22 DSP_LOAD_FAIL...........................................................................................................................3-1183.2.23 EDFA_TEMP_OVER......................................................................................................................3-1193.2.24 FAN_FAIL.......................................................................................................................................3-1203.2.25 FEC_LOF.........................................................................................................................................3-1213.2.26 FEC_OOF.........................................................................................................................................3-1223.2.27 FIBER_CRITICAL..........................................................................................................................3-1233.2.28 FIBER_MAJOR...............................................................................................................................3-1253.2.29 FIBER_MINOR...............................................................................................................................3-1263.2.30 FPGA_ABN.....................................................................................................................................3-1283.2.31 GAINDATA_MIS............................................................................................................................3-1293.2.32 HARD_BAD....................................................................................................................................3-1303.2.33 HARD_FAIL....................................................................................................................................3-1313.2.34 INPWR_FAIL..................................................................................................................................3-1323.2.35 J0_MM.............................................................................................................................................3-1333.2.36 K1_K2_M.........................................................................................................................................3-1343.2.37 K2_M...............................................................................................................................................3-1353.2.38 L_SYNC...........................................................................................................................................3-1353.2.39 LAN_LOC........................................................................................................................................3-1373.2.40 LASER_HAZARD_WARNING.....................................................................................................3-1383.2.41 LOCK_CUR_FAIL..........................................................................................................................3-1393.2.42 LSR_COOL_ALM...........................................................................................................................3-1403.2.43 LTEMP_OVER................................................................................................................................3-1413.2.44 LTI....................................................................................................................................................3-1423.2.45 MAIL_ERR......................................................................................................................................3-1443.2.46 MOD_COM_FAIL...........................................................................................................................3-1453.2.47 MODULE_COOLCUR_OVER.......................................................................................................3-1463.2.48 MODULE_TEMP_OVER...............................................................................................................3-1473.2.49 MS_REI............................................................................................................................................3-1483.2.50 MUT_TLOS.....................................................................................................................................3-1503.2.51 NESTATE_INSTALL.....................................................................................................................3-1523.2.52 NESOFT_MM..................................................................................................................................3-1533.2.53 NO_BD_PARA................................................................................................................................3-1543.2.54 NO_BD_SOFT.................................................................................................................................3-1553.2.55 OCH_FDI.........................................................................................................................................3-1563.2.56 OCH_FDI-O.....................................................................................................................................3-1573.2.57 OCH_FDI-P.....................................................................................................................................3-1583.2.58 OCH_LOS-P....................................................................................................................................3-1603.2.59 OCH_OCI.........................................................................................................................................3-1613.2.60 OCH_SSF.........................................................................................................................................3-1623.2.61 OCH_SSF-O.....................................................................................................................................3-1633.2.62 OCH_SSF-P.....................................................................................................................................3-165



v

3.2.63 ODU_LCK.......................................................................................................................................3-1663.2.64 ODU_OCI........................................................................................................................................3-1683.2.65 ODU_TCMn_AIS............................................................................................................................3-1703.2.66 ODU_TCMn_BDI............................................................................................................................3-1713.2.67 ODU_TCMn_BEI............................................................................................................................3-1723.2.68 ODU_TCMn_DEG..........................................................................................................................3-1753.2.69 ODU_TCMn_EXC...........................................................................................................................3-1773.2.70 ODU_TCMn_LCK...........................................................................................................................3-1783.2.71 ODU_TCMn_LTC...........................................................................................................................3-1793.2.72 ODU_TCMn_OCI............................................................................................................................3-1803.2.73 ODU_TCMn_SSF............................................................................................................................3-1813.2.74 ODU_TCMn_SD.............................................................................................................................3-1833.2.75 ODU_TCMn_TIM...........................................................................................................................3-1843.2.76 OMS_BDI........................................................................................................................................3-1863.2.77 OMS_BDI-O....................................................................................................................................3-1873.2.78 OMS_BDI-P.....................................................................................................................................3-1883.2.79 OMS_FDI-O.....................................................................................................................................3-1893.2.80 OMS_FDI-P.....................................................................................................................................3-1903.2.81 OMS_LOS-P....................................................................................................................................3-1913.2.82 OMS_SSF.........................................................................................................................................3-1933.2.83 OMS_SSF-O....................................................................................................................................3-1943.2.84 OMS_SSF-P.....................................................................................................................................3-1953.2.85 OOS_LOST......................................................................................................................................3-1963.2.86 OPS_MAIN_BAK_ATTR_DIFF....................................................................................................3-1973.2.87 OPS_PS_FAIL.................................................................................................................................3-1993.2.88 OPS_PS_FIXED..............................................................................................................................3-2003.2.89 OPUk_PLM......................................................................................................................................3-2013.2.90 OSC_RDI.........................................................................................................................................3-2023.2.91 OTU_AIS.........................................................................................................................................3-2033.2.92 OTU_LOM.......................................................................................................................................3-2053.2.93 OUT_PWR_LOW............................................................................................................................3-2063.2.94 OUTPWR_FAIL..............................................................................................................................3-2073.2.95 PATCH_ACT_TIMEOUT...............................................................................................................3-2083.2.96 PATCH_DEACT_TIMEOUT.........................................................................................................3-2093.2.97 PATCH_ERR ..................................................................................................................................3-2103.2.98 PATCH_NOT_CONFIRM .............................................................................................................3-2113.2.99 PATCHFILE_NOTEXIST ..............................................................................................................3-2113.2.100 PATH_VERIFY_ALM..................................................................................................................3-2123.2.101 PDU_OFF_ALM............................................................................................................................3-2133.2.102 PM_BIP8_SD.................................................................................................................................3-2153.2.103 PM_TIM.........................................................................................................................................3-2163.2.104 PORTSWITCH_FAIL...................................................................................................................3-217

Contents



vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

3.2.105 POWER_DIFF_OVER..................................................................................................................3-2193.2.106 PRIORITY_VERIFY_ALM..........................................................................................................3-2203.2.107 PRBS_LSS.....................................................................................................................................3-2213.2.108 PUM_BCM_ALM.........................................................................................................................3-2223.2.109 PUM_TEM_ALM..........................................................................................................................3-2243.2.110 PW_SWITCH_EX.........................................................................................................................3-2253.2.111 PWR_MAJ_ALM..........................................................................................................................3-2263.2.112 PWR_MIN_ALM...........................................................................................................................3-2273.2.113 PWR_TEMP_OVERTH................................................................................................................3-2283.2.114 R_LOC...........................................................................................................................................3-2293.2.115 REAR_BD_OFFLINE...................................................................................................................3-2313.2.116 RELAY_ALARM..........................................................................................................................3-2323.2.117 REM_SD........................................................................................................................................3-2333.2.118 RL_CRITICAL_HI........................................................................................................................3-2343.2.119 RL_CRITICAL_LOW...................................................................................................................3-2353.2.120 RMON_ALM_ALIGNMENT_OVER..........................................................................................3-2363.2.121 RMON_ALM_DROPEVENT_OVER..........................................................................................3-2383.2.122 RMON_ALM_FCSERROR_OVER..............................................................................................3-2393.2.123 RMON_ALM_INBADOCTS_OVER...........................................................................................3-2403.2.124 RMON_ALM_OUTBADOCTS_OVER.......................................................................................3-2423.2.125 S1_SYN_CHANGE.......................................................................................................................3-2433.2.126 SCC_LOC......................................................................................................................................3-2443.2.127 SM_BDI.........................................................................................................................................3-2453.2.128 SM_BIP8_SD.................................................................................................................................3-2483.2.129 SM_IAE.........................................................................................................................................3-2493.2.130 SPEED_OVER...............................................................................................................................3-2513.2.131 SUM_INPWR_HI..........................................................................................................................3-2533.2.132 SUM_OUTPWR_HI......................................................................................................................3-2543.2.133 SWDL_ACTIVATED_TIMEOUT................................................................................................3-2553.2.134 SWDL_AUTOMATCH_INH........................................................................................................3-2563.2.135 SWDL_CHGMNG_NOMATCH...................................................................................................3-2573.2.136 SWDL_COMMIT_FAIL...............................................................................................................3-2583.2.137 SWDL_INPROCESS.....................................................................................................................3-2593.2.138 SWDL_NEPKGCHECK................................................................................................................3-2593.2.139 SWDL_PKG_NOBDSOFT...........................................................................................................3-2603.2.140 SWDL_PKGVER_MM.................................................................................................................3-2613.2.141 SWDL_ROLLBACK_FAIL..........................................................................................................3-2623.2.142 SYNC_C_LOS...............................................................................................................................3-2633.2.143 SYSLOG_COMM_FAIL...............................................................................................................3-2643.2.144 T_LOC...........................................................................................................................................3-2653.2.145 T_SLIP...........................................................................................................................................3-2663.2.146 TEM_HA........................................................................................................................................3-267



vii

3.2.147 TEM_LA........................................................................................................................................3-2683.2.148 TEMP_ALARM.............................................................................................................................3-2693.2.149 TEMP_OVER................................................................................................................................3-2703.2.150 THUNDERALM............................................................................................................................3-2713.2.151 TP_LOC.........................................................................................................................................3-2723.2.152 VCXO_LOC...................................................................................................................................3-2733.2.153 W_R_FAILURE.............................................................................................................................3-2743.2.154 WAVE_LEN_LOCK_FAIL..........................................................................................................3-275

4 Performance Event List.............................................................................................................4-14.1 Product Performance Event List.....................................................................................................................4-2

4.1.1 Performance Event List of Check and Error Correction........................................................................4-24.1.2 Performance Event List of Equipment Function....................................................................................4-44.1.3 Performance Event list of Multiplex Section Bit Error..........................................................................4-84.1.4 Performance Event List of Regenerator Section Bit Error.....................................................................4-84.1.5 Performance Event List of Ethernet.......................................................................................................4-9

4.2 Board Performance Event List......................................................................................................................4-124.2.1 D40 Board Performance Event List.....................................................................................................4-124.2.2 DCP Board Performance Event List....................................................................................................4-134.2.3 ELOG/ELOGS Board Performance Event List...................................................................................4-134.2.4 ETMX/ETMXS Board Performance Event List..................................................................................4-144.2.5 FDG Board Performance Event List....................................................................................................4-164.2.6 FIU Board Performance Event List......................................................................................................4-174.2.7 FMU Board Performance Event List...................................................................................................4-174.2.8 HBA Board Performance Event List....................................................................................................4-174.2.9 ITL Board Performance Event List......................................................................................................4-184.2.10 LBE/LBES Board Performance Event List........................................................................................4-184.2.11 LBF/LBFS Board Performance Event List........................................................................................4-204.2.12 LOG/LOGS Board Performance Event List......................................................................................4-234.2.13 LQM Board Performance Event List.................................................................................................4-244.2.14 LU40 Board Performance Event List.................................................................................................4-254.2.15 LU40S Board Performance Event List...............................................................................................4-274.2.16 LUR40/LUR40S Board Performance Event List...............................................................................4-294.2.17 LWC1 Board Performance Event List...............................................................................................4-294.2.18 LWF/LWFS Board Performance Event List......................................................................................4-304.2.19 LWX Board Performance Event List.................................................................................................4-324.2.20 M40 Board Performance Event List...................................................................................................4-334.2.21 MCA Board Performance Event List.................................................................................................4-334.2.22 MR2 Board Performance Event List..................................................................................................4-334.2.23 MR8 Board Performance Event List..................................................................................................4-334.2.24 MWA Board Performance Event List................................................................................................4-344.2.25 MWF Board Performance Event List.................................................................................................4-344.2.26 OAU Board Performance Event List.................................................................................................4-34

Contents



viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

4.2.27 OBU Board Performance Event List..................................................................................................4-344.2.28 OLP Board Performance Event List...................................................................................................4-354.2.29 OPU Board Performance Event List..................................................................................................4-354.2.30 PMU Board Performance Event List.................................................................................................4-354.2.31 RMU9 Board Performance Event List...............................................................................................4-354.2.32 RPC Board Performance Event List...................................................................................................4-354.2.33 SC1/SC2 Board Performance Event List...........................................................................................4-364.2.34 TMR/TMRS Board Performance Event List.....................................................................................4-364.2.35 TMX/TMXS Board Performance Event List.....................................................................................4-374.2.36 TMX40/TMX40S Board Performance Event List.............................................................................4-394.2.37 TRC1 Board Performance Event List................................................................................................4-414.2.38 V40 Board Performance Event List...................................................................................................4-424.2.39 VA4 Board Performance Event List..................................................................................................4-424.2.40 VOA Board Performance Event List.................................................................................................4-424.2.41 WMU Board Performance Event List................................................................................................4-424.2.42 WSD9 Board Performance Event List...............................................................................................4-434.2.43 WSM9 Board Performance Event List...............................................................................................4-434.2.44 WSMD2 Board Performance Event List............................................................................................4-434.2.45 WSMD4 Board Performance Event List............................................................................................4-43

5 Performance Event Processing.................................................................................................5-15.1 BCV.................................................................................................................................................................5-55.2 CCV.................................................................................................................................................................5-55.3 CRC4BBE.......................................................................................................................................................5-65.4 CRC4CSES..................................................................................................................................................... 5-75.5 CRC4ES..........................................................................................................................................................5-75.6 CRC4FEBBE.................................................................................................................................................. 5-85.7 CRC4FECSES.................................................................................................................................................5-95.8 CRC4FEES......................................................................................................................................................5-95.9 CRC4FESES.................................................................................................................................................5-105.10 CRC4SES....................................................................................................................................................5-115.11 CRC4UAS...................................................................................................................................................5-115.12 EDF_BOX_TMP.........................................................................................................................................5-125.13 ENV_TMP..................................................................................................................................................5-135.14 FEC_AFT_COR_ER...................................................................................................................................5-145.15 FEC_AFT_COR_ERAVR..........................................................................................................................5-145.16 FEC_AFT_CORER_FLOAT......................................................................................................................5-155.17 FEC_BEF_COR_ER...................................................................................................................................5-165.18 FEC_BEF_COR_ERAVR..........................................................................................................................5-175.19 FEC_BEF_CORER_FLOAT......................................................................................................................5-175.20 FEC_COR_0BIT_CNT...............................................................................................................................5-185.21 FEC_COR_1BIT_CNT...............................................................................................................................5-195.22 FEC_COR_BYTE_CNT.............................................................................................................................5-19



ix

5.23 FEC_UNCOR_BLOCK_CNT....................................................................................................................5-205.24 ICCLC.........................................................................................................................................................5-215.25 ICTMP.........................................................................................................................................................5-225.26 LINE_OUT_POWER..................................................................................................................................5-225.27 LSBIAS.......................................................................................................................................................5-245.28 LSCLC........................................................................................................................................................5-245.29 LSIOP..........................................................................................................................................................5-255.30 LSOOP........................................................................................................................................................5-265.31 LSTMP........................................................................................................................................................5-275.32 MSBBE.......................................................................................................................................................5-285.33 MSCSES......................................................................................................................................................5-295.34 MSES..........................................................................................................................................................5-305.35 MSFEBBE...................................................................................................................................................5-315.36 MSFECSES.................................................................................................................................................5-325.37 MSFEES......................................................................................................................................................5-335.38 MSFESES....................................................................................................................................................5-345.39 MSSES........................................................................................................................................................5-355.40 MSUAS.......................................................................................................................................................5-365.41 ODU_PM_BBE...........................................................................................................................................5-375.42 ODU_PM_BBER........................................................................................................................................5-385.43 ODU_PM_BIP8..........................................................................................................................................5-395.44 ODU_PM_ES..............................................................................................................................................5-395.45 ODU_PM_FEBBE......................................................................................................................................5-405.46 ODU_PM_FEBBER...................................................................................................................................5-415.47 ODU_PM_FEES.........................................................................................................................................5-425.48 ODU_PM_FESES.......................................................................................................................................5-435.49 ODU_PM_FESESR....................................................................................................................................5-445.50 ODU_PM_FEUAS......................................................................................................................................5-455.51 ODU_PM_SES............................................................................................................................................5-465.52 ODU_PM_SESR.........................................................................................................................................5-465.53 ODU_PM_UAS..........................................................................................................................................5-475.54 ODU_TCMn_BBE......................................................................................................................................5-485.55 ODU_TCMn_BBER...................................................................................................................................5-495.56 ODU_TCMn_BIAES..................................................................................................................................5-505.57 ODU_TCMn_ES.........................................................................................................................................5-515.58 ODU_TCMn_FEBBE.................................................................................................................................5-525.59 ODU_TCMn_FEBBER..............................................................................................................................5-525.60 ODU_TCMn_FEES....................................................................................................................................5-535.61 ODU_TCMn_FESES..................................................................................................................................5-545.62 ODU_TCMn_FESESR...............................................................................................................................5-545.63 ODU_TCMn_FEUAS.................................................................................................................................5-555.64 ODU_TCMn_IAES.....................................................................................................................................5-56

Contents



x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

5.65 ODU_TCMn_SES.......................................................................................................................................5-565.66 ODU_TCMn_SESR....................................................................................................................................5-575.67 ODU_TCMn_UAS......................................................................................................................................5-585.68 OOPRL........................................................................................................................................................5-595.69 OTU_BBE...................................................................................................................................................5-605.70 OTU_BBER................................................................................................................................................5-605.71 OTU_ES......................................................................................................................................................5-615.72 OTU_FEBBE..............................................................................................................................................5-625.73 OTU_FEBBER............................................................................................................................................5-635.74 OTU_FEES.................................................................................................................................................5-645.75 OTU_FESES...............................................................................................................................................5-655.76 OTU_FESESR............................................................................................................................................5-665.77 OTU_FEUAS..............................................................................................................................................5-675.78 OTU_SES....................................................................................................................................................5-685.79 OTU_SESR.................................................................................................................................................5-685.80 OTU_SM_BIP8...........................................................................................................................................5-695.81 OTU_UAS...................................................................................................................................................5-705.82 OTU_IAES..................................................................................................................................................5-715.83 OTU_BIAES...............................................................................................................................................5-725.84 PCLSOP......................................................................................................................................................5-725.85 PCLSSN......................................................................................................................................................5-735.86 PCLSWL.....................................................................................................................................................5-745.87 PCLSWLO..................................................................................................................................................5-745.88 PMUTMP....................................................................................................................................................5-755.89 PUMPOOP..................................................................................................................................................5-765.90 PUMPTMP..................................................................................................................................................5-775.91 RSBBE........................................................................................................................................................5-785.92 RSCSES......................................................................................................................................................5-785.93 RSES...........................................................................................................................................................5-795.94 RSOFS.........................................................................................................................................................5-805.95 RSSES.........................................................................................................................................................5-815.96 RSUAS........................................................................................................................................................5-825.97 SUMIOP......................................................................................................................................................5-835.98 SUMOOP....................................................................................................................................................5-845.99 WCV............................................................................................................................................................5-86

A Glossary.....................................................................................................................................A-1

B Acronyms and Abbreviations.................................................................................................B-1



xi

About This Document

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX BWS 1600G V100R007

OptiX iManager T2000 V200R008C00

Intended AudienceThe intended audiences of this document are:

l Network Monitoring Engineerl System Maintenance Engineer

Symbol ConventionsThe following symbols may be found in this document. They are defined as follows:

Symbol Description

DANGERIndicates a hazard with a high level of risk which, if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which,if not avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if notavoided, could cause equipment damage, data loss, andperformance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or saveyou time.

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference About This Document


1

Symbol Description

NOTE Provides additional information to emphasize orsupplement important points of the main text.

GUI ConventionsConvention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles are inboldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. Forexample, choose File > Create > Folder.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

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

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 havebeen added.

The performance processing of OOPRL has been added.

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



The alarms and performances of the LV40 and LV40S boards have been added.


About This Document



2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)









Chapter Update Description

Chapter 2 Alarm List 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 havebeen deleted.

Chapter 4 PerformanceEvent List

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 havebeen deleted.






3




Chapter 2 Alarm List The alarms of the SCC and SCU boards have been added.The alarm of SUBRACK_ID_CONFLICT,SUB_RACK_NUM_OUTRANGE, SUB_RACK_OFFLINEand OPU3_PLM has been added.

Chapter 3 AlarmProcessing

The alarm processing of SUBRACK_ID_CONFLICT,SUB_RACK_NUM_OUTRANGE, SUB_RACK_OFFLINEand OPU3_PLM has been added.




Chapter 2 Alarm List The alarms of the LUR40, LUR40S, CP40 and EOLP boardshave 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.


The alarm processing of LWFD and LRFD boards have beendeleted.The alarm processing of TCM layer have been added.The alarm processing of LASER_HAZARD_WARNING hasbeen added.


The performances of the LUR40, LUR40S, CP40 and EOLPboards have been added.The performance of the LWFD and LRFD boards have beendeleted.The performances of TCM layer have been added.

About This Document




Issue 08 (2011-10-30)




Chapter 1 Overview Convergent OTU Processing GE Standard Signals have beenadded.Non-Convergent OTU Processing 10GE Standard Signals havebeen 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 andRS_CROSSTR have been deleted.The alarm of L_SYNC have been added.Power monitoring and optical power monitoring alarm of theFIU, MR2, MR8, MB2 and ITL have been deleted.The alarms of the LRF, and LRFS boards have been deleted.


The section of common alarm processing have been added.The alarm processing of CRC4_CROSSTR, MS_CROSSTRand 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 beendeleted.




Chapter 2 Alarm List The alarms of the VA2, LOM and LOMS boards have beenadded.The LAN_LOC alarm of SCC board have been added.



5



The alarm processing of PWR_TEMP_OVERTH has beenadded.The alarm processing of THUNDERALM,SWDL_ACTIVATED_TIMEOUT, SWDL_NEPKGCHECK,SWDL_CHGMNG_NOMATCH, SWDL_PKG_NOBD-SOFT, SWDL_ROLLBACK_FAIL,SWDL_COMMIT_FAIL, SWDL_INPROCESS,SWDL_PKGVER_MM, SWDLAUTOMATCH_INH has beenmodified.


The performance events of the VA2, LOM and LOMS boardshave been added.




Chapter 2 Alarm List The alarms of the LW40, LR40, IMX4, IMX4S, ELOG, ELOGSand 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 alarmsof SCC board have been added.


The OLS of alarms processing have been added.The alarm processing of the OTU4000 and OTU4010 boardshave 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.



About This Document




Issue 08 (2011-10-30)


Chapter 1 Overview A new chapter.

Chapter 2 Alarm List The BD_STATUS, HARD_BAD andFPGA_ABN have been added to WMU, theTF_CHECK_FAIL have been deleted.The VA2 has been deleted, and the LRF(S)has been added.The description of ALM_PIUA_OFFLINEand ALM_PIUB_OFFLINE was updated.The RMON alarms of ST1 and ST2 have beenadded.

4 Performance Event List The LSIOPCUR, LSIOPMIN andLSIOPMAX have been deleted from WMU,and the PCLSOPCUR, PCLSOPMIN,PCLSOPMAX have been added to.The MSFEES, MSFESES, MSFEBBE andMSFECSES have been deleted.The Fragments and Jabbers have been addedto LOG and LOGS.

The alarm list and performance event list of LRF(S) are added.

Add the chapter of Chapter 1 Overview.





7


Chapter 1 Alarm andPerformance EventLists

The ADDITION_C_AIS, ADDITION_C_BPV,ADDITION_C_CRC, ADDITION_C_LOF andADDITION_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 andRMON_ALM_OUTBADOCTS_UNDER have been deleted.The alarms and performance events of the LRF, LRFS, M08 andD08 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 havebeen added.


ADDITION_C_AIS, ADDITION_C_BPV,ADDITION_C_CRC, ADDITION_C_LOF andADDITION_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 andRMON_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 ofALM_DATA_TLOS, AU_AIS, AU_LOP, MAIL_ERR andNEBD_XC_DIF.



About This Document




Issue 08 (2011-10-30)


Chapter 1 Alarm andPerformance EventLists

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 performanceevent 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 havebeen added.


Modify the possible causes and troubleshooting ofBOOTROM_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 PerformanceEvent Processing

Some bugs in former version are fixed.



The description of alarms and performance events relevant to the 40GOTU is added on the basisof 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.


Some bugs in version 1.32 are fixed in this version. The alarms and performance events of theFCE, DCP, M08, D08 and V48 have been added.





9

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 first commercial release.



The first field trial release.

About This Document




Issue 08 (2011-10-30)

1 Overview

About This Chapter

This chapter describes the meaning, indicator status, category, range, and impact of the alarmsof four levels. It also describes the meaning and category of performance events, and providesthe suppression relation of alarms and performance event suppression by alarms.

1.1 Alarm LevelThis section respectively describes the meaning, impact, and indicator status of the alarms offour levels.

1.2 Alarm CategoryThis section describes the meaning and range of alarms in different categories.

1.3 Performance Event CategoryThe performance events can be classified into seven categories according to the functionsmonitored by the performance events.

1.4 Alarm Signal FlowThis 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 AlarmsThis section describes the rules of alarm suppression and provides the suppression relation figureof common alarms. The efficiency for handling the alarms can be enhanced due to the alarmsuppression.

1.6 Performance Event Suppression by AlarmsAn optical interface can report several alarms and performance events. Some performance eventsare not important for the maintenance engineer.

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference 1 Overview


1-1

1.1 Alarm LevelThis section respectively describes the meaning, impact, and indicator status of the alarms offour levels.

The alarm level is used to identify the severity, importance, and urgency of the alarms. Thealarms can be classified into the following four levels in the sequence of decreasing severity:critical alarm, major alarm, minor alarm, and warning alarm.

l Critical alarm: The alarm needs to be handled immediately; otherwise, the system will bedown.

l Major alarm: The alarm needs to be handled in time; otherwise, some important functionswill not be performed.

l Minor alarm: The alarm is used to inform the maintenance personnel of locating the alarmcauses and removing the incipient fault.

l Warning alarm: The alarm need not be handled. The maintenance personnel only need toknow the running status of the equipment.

For the meaning and corresponding indicator status on the board of the alarms of the four levels,see Table 1-1.

Table 1-1 Alarm levels

Alarm Level Definition Indicator Status

Critical alarm Global fault alarms and event alarms thatcause system down

The alarm indicator (red) ofthe board flashes three timesevery other second.

Major alarm Faulty alarms and event alarms of certainboards or lines

The alarm indicator (red) ofthe board flashes twice everyother second.

Minor alarm General fault alarms and event alarms that areused to indicate whether the board or line isnormally working such as board reset andfailure or timeout of occupation of commonresources.

The alarm indicator (red) ofthe board flashes once everyother second.

Warningalarm

Fault alarms and event alarms for warning The alarm indicator (red) ofthe 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 CategoryThis 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 Overview



1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

Table 1-2 Alarm category

AlarmCategory

Definition Example

Communicationalarm

Alarms related to the NEcommunication, ECCcommunication, andcommunication with opticalsignals

The alarm is generated when theNE communication is interruptedor the optical signal is lost.

Process alarm Alarms related to the softwareprocessing and anomalies

The alarm is generated when thedatabase is in error or the NE is inthe installing state.

Equipment alarm Alarms related to the hardware ofthe equipment

The alarm is generated when thelaser is faulty or the opticalinterface is looped back.

Service alarm Alarms related to the service statusand network service quality

The alarm is generated when thesignals at the line layer aredegraded.

Environmentalarm

Alarms related to the power supplysystem and environment of theequipment room

The alarm is generated when thetemperature of the power module isexcessively high.

Security alarm Alarms related to the networkmanagement and the NE security

The alarm is generated when theNE user is not logged in.

1.3 Performance Event CategoryThe performance events can be classified into seven categories according to the functionsmonitored by the performance events.

The performance events are important parameters that reflect the working performance of theequipment. Knowledge of the generation principle, related boards, and alarms of theperformance events is helpful to find incipient faults in routine maintenance and analyze thefault. 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 exceedsthe pre-set threshold, the related alarm is triggered. Hence, when a performance event isgenerated, check whether the related alarm is generated and handle the performance eventaccording to the handling procedure of the related alarm.

The OptiX BWS 1600G provides the remote monitoring function through which the networkcan monitor the transmission of data in different network segments. Remote monitoring(RMON) provides flexible detection modes and control mechanisms to cater for the needs ofdifferent types of networks. The RMON defines a serial of statistic formats and functions torealize the data exchange among the control stations and detection stations in compliance withthe RMON standard. The RMON also provides error diagnosis, planning, and informationreceiving of the performance events of the entire network.



1-3

Table 1-3 Performance event categories

Performance EventCategory

Definition

Administrative unit pointerjustification

The performance event related to the positive or negativejustification count of the AU pointer in the SDH frame of theWDM-side signals.

Performance event related tothe bit errors of theregenerator section

The performance event generated when bit errors occur to theregenerator section in the SDH frames of the signals on theWDM side or the client side of the board.

Performance event related tothe bit errors of the multiplexsection

The performance event generated when bit errors occur to themultiplex section in the SDH frames of the signals on theWDM side or the client side of the board.

Performance event related tothe check and errorcorrection

The performance event generated when the board performsservice check or bit error correction.

Performance event related tothe equipment function

The performance event generated when the optical power, theworking current of the laser or other factors about the runningenvironment exceed the threshold.

RMON performance event The performance event related to the mode in which the boardtransmits or receives the data packets, the number and qualityof packets in different lengths transmitted or received.

Performance Event of FC The performance event generated when parameter changes inFC.

1.4 Alarm Signal FlowThis 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 OverviewThis section describes the eight types of scenarios of the alarm signal flow, SF, SD, and basicconcepts in the alarm signal flow diagram.

Classification

For a WDM product, the detection and transmission of alarms vary according to the type of thesignals that are accessed into the OTU. The OTU is classified into the following types:

l Non-convergent OTUIt refers to an OTU that converts one channel of client service signals.

l Convergent OTUIt refers to an OTU that converges and converts multiple channels of client service signals.

1 Overview




Issue 08 (2011-10-30)

l Regenerating OTUIt refers to an OTU that regenerates the corresponding service signals at an intermediatestation.

According to the type of the OTU and the type of the signals accessed by the OTU, the followingeight situations are defined in this section:

l Non-convergent OTU processing standard SDH signalsThis section describes the alarm signal flow when the non-convergent OTU processesstandard SDH signals.

l Non-convergent OTU processing standard OTN signalsThis section describes the alarm signal flow when the non-convergent OTU processesstandard OTN signals.

l Convergent OTU processing standard SDH signalsThis section describes the alarm signal flow when the convergent OTU processes standardSDH signals.

l Convergent OTU processing standard OTN signalsThis section describes the alarm signal flow when the convergent OTU processes standardOTN signals.

l Regenerating OTUThis section describes the alarm signal flow of the regenerating OTU.

l OTU with the cross-connect functionThis section describes the alarm signal flow of the OTU with the cross-connect function.

l Convergent OTU processing GE standard signalsThis section describes the alarm signal flow when the convergent OTU processes GEstandard signals.

l Non-convergent OTU processing 10GE standard signalsThis section describes the alarm signal flow when the non-convergent OTU processes 10GEstandard signals.

SF and SD

SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are triggerconditions 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 eventsare 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 notdetected or reported.

Concepts

The following concepts are used in the diagrams in this section:

l WDM side: It is the WDM side of the OTU.l Client side: it is the client side of the OTU. On the client side, the services from a client

device are accessed.



1-5

l Middle part: It is the middle part between the WDM side and the client side. It is a virtualconcept, and thus is not displayed on the T2000. This concept is introduced to describe thealarm detection mechanism.

l N#1: It indicates channel 1 at optical interface N on the OTU. For example, the client-sideoptical interfaces of the ELOG unit are numbered 3, 4, 5, and 6, and the WDM-side opticalinterface of the ETMXELOG unit is numbered 1. Then, 3#1 indicates channel 1 at client-side optical interface 3.

l 1#N: It indicates channel N at WDM-side optical interface 1 on the OTU. For example,1#3 indicates channel 3 at WDM-side optical interface 1.

1.4.2 Non-Convergent OTU Processing Standard SDH SignalsThis section describes the alarm signal flow when the non-convergent OTU processes standardSDH signals.

Figure 1-1 and Figure 1-2 show the alarm signal flows when the non-convergent OTU processesstandard 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

R_LOSR_LOS

R_LOFR_LOFR_LOF

MS_AISMS_AISMS_AIS

B1_SD/B1_EXC

BI errors

PM_BEI

PM BIP8 errorsErrorsPM_BIP8_SD/

PM_BIP8_OVER

SM_BEI

SM BIP8 errors Errors

R_LOF

R_LOF

MS_AIS

B1 errors

SM_BIP8_SD/SM_BIP8_OVER

B1_SD/B1_EXC

Station B Client device

Client-side WDM-side WDM-side Client-side Client-device

SF

SD

SD

SF:SF event detecting SD:SD event detecting

SD

xxx Detects and reports the xxx alarm.

Station A

Alarm processing

R_LOF

SF

1 Overview




Issue 08 (2011-10-30)

This section describes the alarm signal flow by analyzing how the OTU processes the R_LOSalarm and PM BIP8 errors. The alarm signal flows of other alarms are similar.

l R_LOSThe client side of the OTU at station A receives R_LOS signals. The R_LOS signals areprocessed on the WDM side of the OTU and then are sent to station B. The WDM side ofthe OTU at station B detects the R_LOF alarm, and then an SF event is generated. Theevent triggers a protection switching. The alarm is then sent to the downstream client deviceof station B, and the OTU reports the R_LOF alarm to the client device.

l PM BIP8 errorsThe OTU at station B detects PM BIP 8 errors on the WDM side. Then, the PM_BIP8_SDor PM_BIP8_OVER alarm is generated. The number of errors determines which alarm isgenerated. 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 thedownstream station except that the PM BIP 8 errors are from the data inside). The alarmsrelated 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 protectionswitching is triggered.



1-7

Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals

OTU_LOM

PM_TIM

SM_TIM

PM_BEI

OTU_LOFOTU_LOF

PM_BDI&SM_BDI

PM_BDI

ODU_AIS/ODU_OCI/ODU_LCK

R_LOF

R_LOSR_LOF


R_LOS

MFAS frame discontinuous

PM TTI byte mismatch

SM TTI byte mismatch

PM_BEI

PM_BDIPM_BDI

SM_BEISM_BEI

SM_BDISM_BDI

BEFFEC_EXCExcessive bit errors before FEC

R_LOF

PM_BDI&SM_BDI

Station A Station B Client device


SF

SF

SF

xxx

SF : SF event detecting Alarm processing

Detects and reports the xxx alarm.

This section describes the alarm signal flow by analyzing how the OTU processes the SM_BEIand 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 upstreamstation 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 sendsthe PM_BDI and SM_BDI alarms to the WDM side of upstream station A. In addition, the

1 Overview




Issue 08 (2011-10-30)

alarm is then sent to the client side of station B. After the alarm is processed on the clientside, 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 protectionswitching is triggered.

1.4.3 Non-Convergent OTU Processing Standard OTN SignalsThis section describes the alarm signal flow when the non-convergent OTU unit processesstandard OTN signals.

Figure 1-3 and Figure 1-4 show the alarm signal flows when the non-convergent OTU processesstandard OTN signals.

NOTE


The non-intrusive monitoring of the board shown in the figures in this section is enabled.



1-9

Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals

R_LOS


SM_BEI

ODU_AISODU_AISR_LOS

PM BIP8 errorsPM BIP8 errorsPM_BIP8_SD/

PM_BIP8_OVERPM_BIP8_SD/

PM_BIP8_OVER

SM BIP8 errors

PM BIP8 errors


PM_BIP8_SD/PM_BIP8_OVER

SM_BEI

SM BIP8 errors SM_BIP8_SD/SM_BIP8_OVER

SM_BDI

OTU_LOFODU_AIS

OTU_LOF/OTU_AIS OTU_LOF/

OTU_AIS ODU_AIS

OTU_LOF ODU_AIS

OTU_AISODU_AISOTU_AIS ODU_AIS


SF

SD

SD

SD

SF

SF

SF

xxx

SF:SF event detecting SD:SD event detecting Alarm processing


PM BIP8 errors

SM_BDI

SM_BDI

SM_BDI

This section describes the alarm signal flow by analyzing how the OTU unit processes theR_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 theSM_BDI alarm to the upstream client equipment of station A. The R_LOS signals areprocessed on the WDM side of the OTU and then are sent to station B. The WDM side of

1 Overview




Issue 08 (2011-10-30)

the OTU at station B detects the ODU_AIS alarm, and then an SF event is generated. Theevent triggers a protection switching. The alarm is then sent to the downstream clientequipment 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 theSM_BDI alarm to the upstream client equipment of station A. In addition, the LOF alarmis processed on the WDM side of the OTU and then is sent to station B. The WDM side ofthe OTU at station B detects the ODU_AIS alarm, and then an SF event is generated. Theevent triggers a protection switching. The alarm is then sent to the downstream clientequipment 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 theSM_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then sentto 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 protectionswitching is triggered.

Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals

SM_BEI/SM_BDI SM_BEI/

SM_BDI

SM_TIM

SM_TIM

SM_BEI/SM_BDI SM_BEI/

SM_BDI

ODU_AIS/ODU_LCK/ODU_OCI ODU_AIS/

ODU_LCK/ODU_OCI

ODU_AIS/ODU_LCK/ODU_OCI


R_LOSR_LOS ODU_AIS

PM_BDI&SM_BDI



SF

xxx


Transparent transmission of all PM signals

SM TTI bytemismatch





1-11

l SM_TIM

When the OTU receives the SM_TIM alarm on the client side or on the WDM side. Thisalarm is not sent to the downstream station.

l SM_BEI/SM_BDIThe OTU detects the SM_BEI/SM_BDI alarm that is sent from the upstream station. Thisalarm is not sent to the downstream station.

l PM_TIM/ PM_BEI/PM_BDIThe OTU transparently transmits all PM alarms.

l ODU_AIS/ODU_LCK/ODU_OCIThe client side of the OTU at station A receives ODU_AIS, ODU_LCK, or ODU_OCIsignals. The signals are not processed and reported at the local station. After the signals aresent 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 protectionswitching. The alarm is then sent to the downstream client equipment of station B, and theOTU reports the ODU_AIS, ODU_LCK, or ODU_OCI alarm to the client equipment.

l R_LOSThe WDM side of the OTU at station B detects the R_LOS alarm. The OTU sends PM_BDIand SM_BDI alarms to the WDM side of upstream station A. In addition, the alarm is thensent to the client side of station B. After the alarm is processed on the client side, theODU_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 protectionswitching is triggered.

1.4.4 Convergent OTU Processing Standard SDH SignalsThis section describes the alarm signal flow when the convergent OTU processes standard SDHsignals.

Figure 1-5 and Figure 1-6 show the alarm signal flows when the convergent OTU processesstandard SDH signals.

NOTE

l In Figure 1-5, N#1 indicates channel 1 at optical interface N of the OTU. For example, the client-sideoptical interfaces of the ETMX are numbered 3, 4, 5, and 6, and the WDM-side optical interface of theETMX is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical interface 3. 1#N indicateschannel N at WDM-side optical interface 1 on the OTU. For example, 1#3 indicates channel 3 atWDM-side optical interface 1.

l Middle part is the middle part between the WDM side and the client side. It is a virtual concept, andthus is not displayed on the T2000. This concept is introduced to describe the alarm detectionmechanism. In the middle part of the convergent OTU, the optical interface numbers and channelnumbers of signals are reallocated.

NOTE



1 Overview




Issue 08 (2011-10-30)

Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals

N#1 R_LOS N#1 REM_SF

N#1 REM_SF

N#1 REM_SF

R_LOS

N#1 R_LOS

N#1 R_LOS

N#1 R_LOS

1#N R_LOF

1#N R_LOF

1#N R_LOF

1#N R_LOF

R_LOF

R_LOF

R_LOF

R_LOF

N#1 AA

N#1 B

N#1 C

N#1 D

B

D

C

A、B、C、D are the others of the SDH alarms

1#N A

1#N B

1#N C

1#N D

A

B

C

D

Middle Client-side Client-deviceClient-side WDM-side WDM-side Middle

Client deviceStation BStation A

SF:SF event detecting

SF

SF

SF

SF

SF

Alarm processing

N#1 R_LOS N#1 REM_SF

N#1 REM_SF

N#1 REM_SF

R_LOS

N#1 R_LOF

N#1 R_LOC

N#1 errors

R_LOF

R_LOC

Errors

1#N R_LOF

1#N R_LOF

1#N R_LOF

1#N BIT errors

R_LOF

R_LOF

R_LOF

Errors

SF

SF

SF

R_LOS

R_LOS

R_LOS N#1 REM_SF

xxx

SD:SD event detecting


SD

This section describes the alarm signal flow through an example in which four client-sideservices 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. Afterbeing processed in the middle part of the OTU at station A, the alarm signals are then sentto station B. The R_LOF alarm of the corresponding channel is generated in the middlepart of station B, and the REM_SF alarm is generated on the client side. The R_LOF alarmis 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, forexample, channel 1 at optical interface 3. After being processed in the middle part and onthe WDM side of the OTU at station A and the WDM side of station B, the alarm signalsare then sent to the downstream station. The R_LOF alarm of channel 3 at optical interface1 is generated in the middle part of station B, and the REM_SF alarm of channel 1 at opticalinterface 3 is generated on the client side. The R_LOF alarm is detected in the clientequipment.



1-13

An SF event is generated in the corresponding channel in the middle part of the OTU atstation B, and a protection switching is triggered.

l Non-R_LOS signals are accessed on the client side.The signal flow of the R_LOF or the LOC is similar to that of the R_LOS.When any other alarms are accessed, the same alarm is reported at each detection point inthe system.

Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals

R_LOF

R_LOF

R_LOF

R_LOF

R_LOS

PM_BDI&SM_BDI

R_LOS

R_LOF

R_LOF

R_LOF

R_LOFPM_BDI&SM_BDI

OTU_LOF

R_LOF

R_LOF

R_LOF

R_LOF


PM_BDI


Errors

Errors

Errors

ErrorsPM_BEI

PM BIP8 errors

Errors

Errors

Errors

ErrorsSM_BEI



SM BIP8 errors

OTU_LOF

Middle Client-side Client-deviceClient-side WDM-side WDM-side MiddleClient deviceStation BStation A

SF

SF

SF

SD

SD

xxx




1 Overview




Issue 08 (2011-10-30)

l There is R_LOS, OTU_LOF, OTUk_LOM, ODU_AIS, ODU_OCI, or ODU_LCK on theWDM side.The WDM side of the OTU at station B accesses and processes the alarm signals. The OTUsends 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 theclient 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 protectionswitching 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. In this case, the biterror alarm is detected in the client equipment.An SD event is generated on the WDM side of the OTU at station B, and a protectionswitching is triggered.

1.4.5 Convergent OTU Processing Standard OTN SignalsThis section describes the alarm signal flow when the convergent OTU processes standard OTNsignals.

Figure 1-7 and Figure 1-8 show the alarm signal flows when the convergent OTU processesstandard OTN signals.

NOTE

In Figure 1-7, N#1 indicates channel 1 at optical interface N of the OTU. For example, the client-sideoptical interfaces of the ETMX unit are numbered 3, 4, 5, and 6, and the WDM-side optical interface ofthe ETMX unit is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical interface 3. 1#Nindicates channel N at WDM-side optical interface 1 on the OTU. For example, 1#3 indicates channel 3at 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 thusis not displayed on the T2000. This concept is introduced to describe the alarm detection mechanism. Inthe middle part of the convergent OTU, the optical interface number and channel number of signals are re-allocated.

NOTE





1-15

Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals

Middle Client-side Client-device

R_LOS

Client-side WDM-side WDM-side Middle

A

B

C


N#1 R_LOS

N#1 R_LOS

N#1 R_LOS

N#1 R_LOS

N#1 REM_SF

N#1 REM_SF

N#1 REM_SF

N#1 REM_SF

1#N ODU_AIS

1#N ODU_AIS

1#N ODU_AIS

1#N ODU_AIS

ODU_AIS

ODU_AIS

ODU_AIS

ODU_AIS

N#1 A

N#1 B

N#1 C

N#1 ODU_AIS

1#N A

1#N B

1#N C

1#N ODU_AIS

A

B

C

ODU_AIS

SD

SF

SF

SF

R_LOS

ODU_AIS

N#1 R_LOS

N#1 R_LOS

N#1 OTU_LOF

N#1 BIT errors

OTU_LOF

N#1REM_SF

N#1 REM_SF

N#1REM_SF

BIT errors

1#N ODU_AIS

1#N ODU_AIS

1#N ODU_AIS

1#N BIT errors

ODU_AIS

ODU_AIS

ODU_AIS

SD

SF

SF

SF

R_LOS

R_LOS

R_LOS

xxx

Inserts SM_BDI back

Inserts SM_BDI back

Inserts SM_BDI back

Inserts SM_BDI back

Inserts SM_BDI back

Inserts SM_BDI back

Inserts SM_BDI back

BIT errors


Detects and reports the xxx alarm. A, B, C are the others of the OTN alarms

R_LOS

SF


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 sendsthe SM_BDI alarm to the upstream client equipment of station A. After being processedin the middle part and on the WDM side of the OTU at station A, the alarm signals are thensent to station B. The ODU_AIS alarm of the corresponding channel is generated in themiddle part of station B, and the REM_SF alarm is generated on the client side. TheODU_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 switchingis 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 theclient side, for example, channel 1 at optical interface 3. The OTU sends the SM_BDI alarmto the upstream client equipment of station A. After being processed in the middle part andon the WDM side of the OTU at station A and the WDM side of station B, the alarm signalsare then sent to the downstream station. The ODU_AIS alarm of channel 3 at optical

1 Overview




Issue 08 (2011-10-30)

interface 1 is generated in the middle part of station B, and the REM_SF alarm of channel1 at optical interface 3 is generated on the client side. The ODU_AIS alarm is detected inthe client device.

An SF event is generated in the corresponding channel in the middle part of the OTU atstation B, and a protection switching is triggered.

l The alarm signals except for the signals of the R_LOS and OTU_LOF alarms are accessedon the client side.

When any of other alarm signals is accessed, the corresponding alarm is reported at eachdetection point in the system.

Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals

ODU_AIS

ODU_AIS

ODU_AIS

ODU_AIS

R_LOS

PM_BDI&SM_BDI

R_LOS

ODU_AIS

ODU_AIS

ODU_AIS

ODU_AIS

OTU_LOF

ODU_AIS

ODU_AIS

ODU_AIS

ODU_AIS


PM_BDI


Errors

Errors

Errors

ErrorsPM_BEI

PM BIP8 errors

Errors

Errors

Errors

ErrorsSM_BEI



SM BIP8 errors

OTU_LOF/

Middle Client-side Client-deviceClient-side WDM-side WDM-side Middle


SF

SD

SF

SF

SD

xxx



PM_BDI&SM_BDI



1-17


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 OTUsends 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 theclient 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 protectionswitching 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-dependentalarm is detected in the client device.An SD event is generated on the WDM side of the OTU at station B, and a protectionswitching is triggered.

1.4.6 Regenerating OTUThis 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 Overview




Issue 08 (2011-10-30)

Figure 1-9 Alarm signal flow of the regenerating OTU

OTU_LOM

PM_TIM

Station A Station B(REG) Station C

SM_TIM

PM_BEI

OTU_LOF


R_LOS ODU_AIS


R_LOS

PM_BEI

PM_BDIPM_BDI

SM_BEISM_BEI

SM_BDISM_BDI

BEFFEC_EXC

PM_TIM

PM_BEI

PM_BDI

SM_IAESM_IAE



PM BIP8 errors PM_BIP8_SD/PM_BIP8_OVER

SM BIP8 errors SM_BIP8_SD/SM_BIP8_OVER

OTU_LOF

WDM-side WDM-side1 WDM-side2 WDM-side

xxx

MFAS frame discontinuous

PM TTI byte mismatch


Excessive bit errors before FEC


ODU_AIS

In the case of the regenerating OTU, all alarms in the SM section are terminated at the localstation and are not sent to the downstream station. Other alarms are then sent to the downstream



1-19

station, and are reported on the WDM side of the OTU (except that the R_LOS alarm is insertedwith an ODU_AIS alarm to the downstream station).

1.4.7 Alarm Signal Processing of the OTU with the Cross-ConnectFunction

The OTU with the cross-connect function supports the service transmission in the straight-through mode or the cross-connect mode. The processing of alarm signals in one mode isdifferent 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 displayedon the T2000.

Figure 1-10 OTU with the cross-connect function in the straight-through mode

3#1(RX1)4#1(RX2)5#1(RX3)6#1(RX4)

1#31#41#51#6

1(OUT)

3#1(TX1)4#1(TX2)5#1(TX3)6#1(TX4)

1#31#41#51#6

1(IN)

A B

As shown in Figure 1-10, the four channels of optical signals accessed from RX1-RX4 on unitA at the upstream station are sent to channels 3-6 that correspond to the OUT port in the straight-through mode. One channel of optical signals that are input from the IN port on unit B at thedownstream station is demultiplexed into four channels of optical signals, which are then directlysent to TX1-TX4.

Hence, in the straight-through mode, the REM_SF and REM_SD alarms at the downstreamstation indicate that the signals at the corresponding port on the client side at the upstream stationfail or bit errors at this port exceed the threshold. For example, when the services in channel 1at optical interface 3 on unit A at the upstream station fail, channel 1 at optical interface 3 onunit B at the downstream station reports the REM_SF alarm.

Cross-Connect Mode

The cross-connect mode is classified into intra-unit cross-connection and inter-unit cross-connection.

l Intra-unit cross-connectionIn Figure 1-11, the cross-connection from RX3 (channel 1 at optical interface 5) on unitA to OUT (channel 3 at optical interface 1) on unit A is defined as the intra-unit cross-connection.

l Inter-unit cross-connection

1 Overview




Issue 08 (2011-10-30)

In Figure 1-11, the cross-connection from RX1 (channel 1 at optical interface 3) on unitC to OUT (channel 6 at optical interface 1) on unit A is defined as the inter-unit cross-connection. The inter-unit cross-connection is realized by using the backplane.

Figure 1-11 shows the unidirectional signal flow in the cross-connect mode.

Figure 1-11 OTU with the cross-connect function in the cross-connect mode

C

3#1(RX1)4#1(RX2)5#1(RX3)6#1(RX4)

1#31#41#51#6

1(OUT)

3#1(TX1)4#1(TX2)5#1(TX3)6#1(TX4)

1#31#41#51#6

1(IN)

A B

3#1(RX1)4#1(RX2)5#1(RX3)6#1(RX4)

1#31#41#51#6

In Figure 1-11, the following cross-connections are created:

l Intra-unit cross-connection from RX3 (channel 1 at optical interface 5) on unit A to OUT(channel 3 at optical interface 1) on unit A

l Inter-unit cross-connection from RX1 (channel 1 at optical interface 3) on unit C to OUT(channel 6 at optical interface 1) on unit A

The signals that are received from RX3 (channel 1 at optical interface 5) on unit A at the upstreamstation are sent to IN (channel 3 at optical interface 1) on unit B at the downstream station. Thesignals received from RX1 (channel 1 at optical interface 3) on unit C at the upstream stationare sent to IN (channel 6 at optical interface 1) on unit B at the downstream station.

The meaning of optical channels regarding the REM_SF and REM_SD alarms in the cross-connect mode is different from that in the straight-through mode. For example, when the servicesin channel 1 at optical interface 4 on unit A at the upstream station fail, unit B at the downstreamstation reports the REM_SF alarm in channel 1 at optical interface 3; when the services in channel1 at optical interface 3 on unit C at the upstream station fail, unit B at the downstream stationreports 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 theunit at the upstream station to locate the alarm signal source. Then, check whether the clientsignal status such as the optical power, fibers and optical modules in the channel at thecorresponding optical interface is normal. If not, take the corresponding maintenance measures.

CAUTIONIn any mode, proper configuration must be made on the T2000.



1-21

1.4.8 Convergence OTU Processing the GE Standard SignalsThis topic describes the alarm signal flow when the convergence OTU board processes the GEstandard signals.

Figure 1-12 and Figure 1-13 show the alarm signal flows when the convergence OTU boardprocesses 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 opticalinterfaces on the client side of the ETMX board are numbered 3, 4, 5, and 6; the optical interface on theWDM side is numbered 1. Then, 3#1 represents channel 1 of optical interface 3.


1 Overview




Issue 08 (2011-10-30)

Figure 1-12 Alarm signal flow when the convergence OTU board processes the GE standardsignals - 1

R_LOS

Client-side Client deviceClient-side WDM-side WDM-side

Client device

B站

Station A

R_LOS

R_LOS...

N#1REM_SF

...N#1REM_SF

N#1REM_SF

LINK_ERR

...LINK_ERR

LINK_ERR

N#1R_LOS

N#1R_LOS

N#1R_LOS

No Packet

... ...

No Packet

...No Packet

No Packet

PM_BEI

PM BIP8 biterrors PM_BIP8_SD/

PM_BIP8_OVER

SDBit errors

...

SM_BEI

SM BIP8bit errors

SD

...


SF: SF event detecting SD: SD event detecting

XXX Detects and reports the XXX alarm

No Packet

No Packet

N#1ALM_DATA_RLOS

N#1ALM_DATA_RLOS

N#1ALM_DATA_RLOS

N#1ALM_DATA_TLOS

N#1ALM_DATA_TLOS

N#1ALM_DATA_TLOS

LINK_ERR

...

LINK_ERR

LINK_ERR...

LINK_ERR

...LINK_ERR

LINK_ERR

N#1LINK_ERR

N#1LINK_ERR

N#1LINK_ERR

N#1LINK_ERR

N#1LINK_ERR

N#1LINK_ERR

LINK_ERR

...

LINK_ERR

LINK_ERR...

No Packet

...No Packet

No Packet

N#1LINK_ERR

N#1LINK_ERR

N#1LINK_ERR

N#1ALM_DATA_TLOS

N#1ALM_DATA_TLOS

N#1ALM_DATA_TLOS

LPT=Disable

LPT=Enable

Bit errors

Bit errors

Bit errors

Bit errors

Bit errors

Alarm processing

Station B

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_LOSalarm is reported on the client side and is then processed on the WDM side. The alarm issent to station B and is processed on the WDM side. The client side of station B reports theREM_SF alarm, which is then sent to the downstream client device. The client devicedetects the LINK_ERR alarm.

The SF event is generated on the WDM side of the OTU board at station B, which triggersa service channel switching.



1-23

l LINK_ERR on the client sideAuto-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 tostation B. The client side of station B reports the ALM_DATA_TLOS alarm, which isthen 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 ofthe OTU at station A, the LINK_ERR alarm is reported on the client side and is sent tostation B. The client side of station B reports the LINK_ERR alarm, which is then sentto 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 isdisabled.

l No Packet on the client sidethe No Packet signal is detected on the client side of the OTU at station A, theALM_DATA_RLOS alarm is reported on the client side and is sent to station B. Theclient side of station B reports the ALM_DATA_TLOS alarm, which is then sent to thedownstream client device. The client device detects the No Packet alarm.

l PM_BIP8_SD/PM_BIP8_OVER/SM_BIP8_SD/SM_BIP8_OVER on the WDM sideThe OTU board at station B receives and processes the alarm signal on the WDM side andsends the PM_BEI or SM_BEI alarm back to the WDM side of the upstream station A. Inaddition, the alarm signal is further sent to the downstream client device. The client devicedetects bit errors.The SD event is generated on the WDM side of the OTU at station B. Whether this eventtriggers a service channel switching is set by users.

1 Overview




Issue 08 (2011-10-30)

Figure 1-13 Alarm signal flow when the convergence OTU board processes the GE standardsignals - 2

OTU_LOM

PM_TIM

SM_TIM

PM_BEI

DiscontinuousMFAS framesPM TTI byte

mismatch

SM TTI bytemismatch

PM_BEI

PM_BDIPM_BDI

SM_BEISM_BEI

SM_BDISM_BDI

BEFFEC_EXCExcessive bit

errors before FEC


Client-side WDM-side WDM-side Client-side Client device

SF: SF event detecting Alarm processing


OTU_LOFOTU_LOF

PM_BDI&SM_BDI

PM_BDI



SF

SF

No Packet

...No Packet

No Packet

No Packet

...No Packet

No Packet

OTU_LOFOTU_LOF

PM_BDI&SM_BDI

PM_BDI


R_LOS


R_LOS

PM_BDI&SM_BDI

SF

SF

SF

LINK_ERR

...LINK_ERR

LINK_ERR

LINK_ERR

...LINK_ERR

LINK_ERR

LINK_ERR

LINK_ERR

...

LINK_ERR

R_LOS R_LOS

PM_BDI&SM_BDI

SFNo Packet

No Packet

...

No Packet

LPT=Disable

LPT=Disable

LPT=Disable

LPT=Enable

LPT=Enable

LPT=Enable



1-25

This section describes how the OTU board processes the OTU_LOM alarm and the OTU_LOFalarm. This is considered as an example to describe the alarm signal flow. The alarm signal flowof other alarms is similar.

l OTU_LOM on the WDM sideThe OTU board at station B receives the OTU_LOM alarm on the WDM side. This alarmis not further sent to the downstream.

l OTU_LOF on the WDM sideAuto-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_BDIand SM_BDI alarms back to the WDM side of the upstream station A. In addition, theOTU_LOF alarm is sent to the client side of station B and is processed on the clientside. Then, the OTU_LOF alarm is sent to the downstream client device. The clientdevice detects the No Packet signal.

– When the LPT is enabled and the OTU_LOF is detected on the WDM side of the OTUboard at station B, the WDM side reports the OTU_LOF alarm and sends the PM_BDIand SM_BDI alarms back to the WDM side of the upstream station A. In addition, theOTU_LOF alarm is sent to the client side of station B and is processed on the clientside. Then, the OTU_LOF alarm is sent to the downstream client device. The clientdevice detects the LINK_ERR alarm.

The alarm signal flow is the same as that in the auto-negotiation mode when the LPT isdisabled.The SF event is generated on the WDM side of the OTU board at station B, which triggersa service channel switching.

1.4.9 Non-Convergence OTU Board Processing the 10GE StandardSignals

This topic describes the alarm signal flow when the non-convergence OTU board processes the10GE standard signals.

Figure 1-14 and Figure 1-15 show the alarm signal flows when the non-convergence OTUboard processes the 10GE standard signals.

NOTE


1 Overview




Issue 08 (2011-10-30)

Figure 1-14 Alarm signal flow when the non-convergence OTU board processes the 10GEstandard signals - 1

LINK_ERRR_LOSR_LOS

LINK_ERR

ALM_DATA_RLOSNo Packet

PM_BEI

PM BIP8bit errors Bit errorsPM_BIP8_SD/

PM_BIP8_OVER

SM_BEI

SM BIP8 biterrors

No Packet




SD

SF: SF event detecting SD: SD event detecting

SD

Alarm processing


LINK_ERR

LINK_ERR LINK_ERR LINK_ERR

ALM_DATA_TLOS

Bit errors

REM_SF

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 exampleto 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_LOSalarm is reported on the client side and is then processed on the WDM side. The alarm issent to station B and is processed on the WDM side. The client side of station B reports theLINK_ERR alarm and the REM_SF alarm, which is then sent to the downstream clientdevice. 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, theLINK_ERR alarm is reported on the client side and is sent to station B. The client side ofstation 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, theALM_DATA_RLOS alarm is reported on the client side and is sent to station B. The



1-27

client side of station B reports the ALM_DATA_TLOS alarm, which is then sent to thedownstream 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 OTUboard at station B, the PM_BEI is returned back to the upstream station A and thePM_BIP8_SD or PM_BIP8_OVER is sent to the downstream client device. The clientdevice detects bit errors.

The SD event is generated on the WDM side of the OTU at station B. Whether this eventtriggers a service channel switching is set by users.

Figure 1-15 Alarm signal flow when the non-convergence OTU board processes the 10GEstandard signals - 2

OTU_LOM

PM_TIM

SM_TIM

PM_BEI

OTU_LOFOTU_LOF

PM_BDI&SM_BDI

PM_BDI


R_LOS


R_LOS

DiscontinuousMFAS framesPM TTI byte

mismatch

SM TTIbytemismatch

PM_BEI

PM_BDIPM_BDI

SM_BEISM_BEI

SM_BDISM_BDI

BEFFEC_EXC

Excessive biterrors before FEC

LINK_ERR

PM_BDI&SM_BDI



SF

SF

SF

SF: SF event detecting Alarm processing


LINK_ERR

LINK_ERR

1 Overview




Issue 08 (2011-10-30)

This section describes how the OTU board processes the OTU_LOM alarm and the OTU_LOFalarm. This is considered as an example to describe the alarm signal flow. The alarm signal flowof other alarms is similar.

l OTU_LOM on the WDM sideWhen the discontinuous MFAS frames are detected on the WDM side of the OTU boardat station B, the WDM side reports the OTU_LOM alarm, which is not sent to thedownstream.

l OTU_LOF on the WDM sideWhen the OTU_LOF is detected on the WDM side of the OTU board at station B, theWDM side reports the OTU_LOF alarm and sends the PM_BDI and SM_BDI alarms backto the WDM side of the upstream station A. In addition, the OTU_LOF alarm is sent to theclient side of station B and is processed on the client side. Then, the OTU_LOF alarm issent 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 triggersa service channel switching.

1.5 Suppression Relation of AlarmsThis section describes the rules of alarm suppression and provides the suppression relation figureof common alarms. The efficiency for handling the alarms can be enhanced due to the alarmsuppression.

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 thesignal is lost, the optical interface generates the R_LOS alarm accompanied with the alarmindicating that the B1/B2 bit errors cross the threshold. However, the alarm indicating that theB1/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 thresholdthrough the R_LOS alarm. Only the R_LOS alarm is reported by the optical interface.

The rules of alarm suppression are as follows:l The client-side alarms and the WDM-side alarms are relatively independent. There are no

alarm suppression relation between the client-side alarms and the WDM-side alarms.l There is no alarm suppression relation between the detection alarms related to the board

hardware and the service alarms.

NOTE

Some alarms for the optical module are exceptional. For example, the R_LOS alarm suppresses theIN_PWR_LOW alarm.

l There is no alarm suppression relation for the alarms that cannot be generated at the sametime.

1.5.1 Suppression Relation of OTU Service Alarms on WDM SideThe 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 lossoccurs to one optical interface on the WDM side, the optical interface only reports the R_LOSalarm but not the R_LOC , SM_BIP8_OVER, OTU_AIS and the below alarms.



1-29

Figure 1-16 Suppression relation of OTU service alarms on WDM side

SM_BIP8_OVER

R_LOS

PM_TIM

PM_BEI

BEFFEC_EXC

R_LOF


PM_BDI

PM_BIP8_OVER

SM_BIP8_SD

SM_IAESM_TIM

PM_BIP8_SD

R_LOC

OTU_LOM

FEC_OOF

OTU_LOF

OTU_AIS

R_OOF

B2_EXC

B2_SD

B1_EXC

B1_SD

MS_RDI

MS_REI

J0_MMMS_AIS

AU_AIS AU_LOP

SM_BDI

SM_BEI

1.5.2 Suppression Relation of OTU Service Alarms on client SideThe 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 lossoccurs to one optical interface on the client side, the optical interface only reports the R_LOSalarm but not the R_LOC and R_LOF alarms.

1 Overview




Issue 08 (2011-10-30)

Figure 1-17 Suppression relation of OTU service alarms on client side

R_LOC

J0_MM

R_OOF

R_LOF

R_LOS

B2_EXCMS_AIS

B1_SDMS_REI B2_SD

B1_EXC MS_RDI

1.6 Performance Event Suppression by AlarmsAn optical interface can report several alarms and performance events. Some performance eventsare not important for the maintenance engineer.

When the equipment is faulty, several alarms and performance events may be generated by thesame optical interface. However, some alarms and performance events are not important for themaintenance engineer. For example, when the signal is lost, the optical interface generates theR_LOS alarm accompanied with the B1/B2 bit error performance event. However, the B1/B2bit error performance event is not important for the maintenance engineer. In this case, theequipment suppresses the B1/B2 bit error performance event through the R_LOS alarm. Onlythe R_LOS alarm is reported by the optical interface.

Table 1-4 lists the performance events suppressed by the R_LOS alarm.

Table 1-4 Performance events suppressed by the R_LOS alarm

MSBBE MSFEBBE RSCSES

MSES MSFECSES RSOFS

MSSES MSFEUAS FEC_AFT_COR_ER

MSCSES RSBBE FEC_BEF_COR_ER

MSFEES RSES

MSFESES RSSES

Table 1-5 lists the performance events suppressed by the NO_BD_PARA alarm.



1-31

Table 1-5 Performance events suppressed by the NO_BD_PARA alarm

LSBIASCUR LSCLCCUR LSTMPCUR

LSBIASMAX LSCLCMAX LSTMPMAX

LSBIASMIN LSCLCMIN LSTMPMIN

1 Overview




Issue 08 (2011-10-30)

2 Alarm List

About This Chapter

This chapter describes the alphabetical lists of alarms and lists alarms of every board.

2.1 Product Alarm ListThis section lists the alarms supported by the product in alphabetical order.

2.2 Board Alarm ListLists the alarms of every board.

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference 2 Alarm List


2-1

2.1 Product Alarm ListThis section lists the alarms supported by the product in alphabetical order.

2.1.1 Alarm List AThis section used a table to list the alarms starting with A.

Name Description Level

AD_CHECK_FAIL AD (analog to digital converter) selfcheck failure

Major

ALM_DATA_RLOS Receiving data lost on the Ethernetport

Minor

ALM_DATA_TLOS Transmitting data lost on the Ethernetport

Minor

ALM_PIUA_OFFLINE Power interface unit A offline Major

ALM_PIUB_OFFLINE Power interface unit B offline Major

AU_AIS AU alarm indication signal Major

AU_LOP AU loss of pointer Major

2.1.2 Alarm List BThis section used a table to list the alarms starting with B.


B1_EXC Regenerator section (B1) excessiveerrors

Minor

B1_SD Regenerator section(B1) signaldegraded

Minor

B2_EXC Multiplex section (B2) excessiveerrors

Major

B2_SD Multiplex section (B2) signaldegraded

Minor

BD_VER_NMAT Board version mismatch Major

BD_STATUS Board is not in position Major

BEFFEC_EXC Signal excessive errors before FECalarm

Minor

2 Alarm List




Issue 08 (2011-10-30)


BEFFEC_SD Signal degraded alarm before FECalarm

Minor

BOOTROM_BAD BOOTROM checksum alarm Major

2.1.3 Alarm List CThis section used a table to list the alarms starting with C.


CFGBD_FAIL Board configuration is mismatched Major

CFG_VERIFY Configuration is not verified Major

CFGDATA_OUTRANGE Board configuration data out of rangealarm

Major

CHAN_ADD Channel of single wave signal addition Major

CHAN_LOS Channel of single wave signal loss Critical

CLT_MM Service type on the client is not match Major

COMMUN_FAIL Board serial port communicationfailure

Major

2.1.4 Alarm List DThis section used a table to list the alarms starting with D.


DBMS_ERROR Database error Major

DBMS_PROTECT_MODE Database in protect mode Critical

DCM_INSUFF Insufficient dispersion compensationmargin

Minor

DSP_LOAD_FAIL DSP software loading failure Critical

2.1.5 Alarm List EThis section used a table to list the alarms starting with E.



2-3


EDFA_TEMP_OVER EDFA temperature exceeds thethreshold

Critical

2.1.6 Alarm List FThis section used a table to list the alarms starting with F.


FAN_FAIL Fan failed Major

FCSERRORS_OVER CRC errors cross the upper threshold Minor

FEC_LOF Loss of FEC frame Critical

FEC_OOF Out of FEC frame Critical

FIBER_CRITICAL OTDR testing fiber critical alarm Critical

FIBER_MAJOR OTDR testing fiber major alarm Major

FIBER_MINOR OTDR testing fiber minor alarm Minor

FPGA_ABN FPGA status is abnormal Major

2.1.7 Alarm List HThis section used a table to list the alarms starting with H.


HARD_BAD Hardware failed Critical

HARD_FAIL Board hardware failed Critical

2.1.8 Alarm List IThis section used a table to list the alarms starting with I.


INPWR_FAIL Input power failed Major

IN_PWR_HIGH Input power is too high Critical

IN_PWR_LOW Input power is too low Critical

2 Alarm List




Issue 08 (2011-10-30)

2.1.9 Alarm List JThis section used a table to list the alarms starting with J.


J0_MM J0 byte/trace indicator mismatch Minor

2.1.10 Alarm List KThis section used a table to list the alarms starting with K.


K1_K2_M K1, K2 mismatch Minor

K2_M K2 mismatch Minor

2.1.11 Alarm List LThis section used a table to list the alarms starting with L.


LAN_LOC Ethernet communication failure Major

LASER_HAZARD_WARNING Laser level hazard warning Critical

LINK_ERR Link error Critical

LINK_STATUS Link status abnormality Critical

LOCK_CUR_FAIL Pump driving current is out of lock Critical

LOOP_ALM Indication of loop operating Minor

LSR_COOL_ALM Cooling current of the laser overthreshold

Major

LSR_WILL_DIE Laser will be out of work Critical

LTEMP_OVER Laser temperature exceeds thethreshold

Major

LTI All clock sources are lost Major

L_SYNC Loss of synchronization alarm Critical

2.1.12 Alarm List MThis section used a table to list the alarms starting with M.



2-5


MAIL_ERR Mail communication error Major

MOD_COM_FAIL Module communication failure Major

MODULE_COOLCUR_OVER Module cooling current exceeds thethreshold

Major

MODULE_TEMP_OVER Module temperature exceeds thethreshold

Major

MS_AIS Multiplex section alarm indication Major

MS_RDI Multiplex section remote defectindication

Minor

MS_REI Multiplex section remote errorindication

Warning

MUT_LOS Loss of multiplexed signals Critical

MUT_TLOS Loss of the output multiplexed signals Critical

2.1.13 Alarm List NThis section used a table to list the alarms starting with N.


NESOFT_MM Software difference between workingand protection boards

Critical

NESTATE_INSTALL NE is in install state Critical

NEBD_XC_DIF Crossing data of NE and boarddifferent

Major

NO_BD_SOFT No board software Critical

NO_BD_PARA No board parameter Critical

2.1.14 Alarm List OThis section used a table to list the alarms starting with O.


OA_LOW_GAIN Optical amplification gain low Critical

OCH_FDI Forward defect indication at OCHlayer

Major

2 Alarm List




Issue 08 (2011-10-30)


OCH_FDI-O Forward defect indication (overhead)at OCH layer

Minor

OCH_FDI-P Forward defect indication (payload) atOCH layer

Major

OCH_LOS-P Loss of signal (payload) at OCH layer Critical

OCH_OCI Open connection indication at OCHlayer

Minor

OCH_SSF Server signal fail at OCH layer Major

OCH_SSF-O Server signal fail (overhead) at OCHlayer

Minor

OCH_SSF-P Server signal fail (payload) at OCHlayer

Major

ODU_AIS ODU (optical channel data unit) alarmindication signal

Major

ODU_LCK ODU locked Major

ODU_OCI ODU (Optical channel data unit) openconnection indication

Major

ODU_TCMn_AIS ODU1 TCMn alarm indication signal Major

ODU_TCMn_BDI ODU1 TCMn backward defectindication

Minor

ODU_TCMn_BEI ODU1 TCMn backward errorindication

Major

ODU_TCMn_DEG ODU1 TCMn signal degraded Minor

ODU_TCMn_EXC ODU1 TCMn section BIP8 excessiveerror defect

Major

ODU_TCMn_LCK ODU1 TCMn signal locked Minor

ODU_TCMn_LTC Loss of ODU1 TCMn serialconnection

Minor

ODU_TCMn_OCI ODU1 TCMn open connectionindication

Minor

ODU_TCMn_SD ODU1 TCMn signal degrade Major

ODU_TCMn_SSF ODU1 TCMn Server signal fail Critical

ODU_TCMn_TIM ODU1 TCMn TTI mismatch Minor

OMS_BDI Backward defect indication at OMSlayer

Minor



2-7


OMS_BDI-O Backward defect indication(overhead) at OMS layer

Minor

OMS_BDI-P Backward defect indication (payload)at OMS layer

Minor

OMS_FDI Forward defect indication at OMSlayer

Major

OMS_FDI-O Forward defect indication (overhead)at OMS layer

Minor

OMS_FDI-P Forward defect indication (payload) atOMS layer

Major

OMS_LOS-P Loss of signal (payload) at OMS layer Critical

OMS_SSF Server signal fail at OMS layer Major

OMS_SSF-O Server signal fail (overhead) at OMSlayer

Minor

OMS_SSF-P Server signal fail (payload) at OMSlayer

Major

OOS_LOST Loss of OTM overhead signal Minor

OPS_MAIN_BAK_ATTR_DIFF Attribute difference between workingand protection channel

Critical

OPS_PS_FAIL Failure of optical channel protectionswitching

Major

OPS_PS_FIXED Alarm of optical channel protectionswitching

Major

OPS_PS_INDI Indication of optical channelprotection switching

Major

OPU2_PLM OPU2 payload mismatch Major

OPU3_PLM OPU3 payload mismatch Major

OTU_AIS OTU (optical transponder unit) alarmindication signal

Major

OTU_LOF Loss of FAS frame Critical

OTU_LOM MFAS multi-frame alignment signalis discontinuous.

Major

OSC_LOS Loss of OSC signal Critical

OSC_RDI Remote defect indication Minor

OUTPWR_FAIL Output power failed Major

2 Alarm List




Issue 08 (2011-10-30)


OUT_PWR_HIGH Output power is too high Major

OUT_PWR_LOW Output power is too low Major

2.1.15 Alarm List PThis section used a table to list the alarms starting with P.


PATCH_ERR Patch error Major

PATCH_NOT_CONFIRM The patch file does not exist Major

PATCHFILE_NOTEXIST Actived patch has not been confirmedovertime

Major

PATH_VERIFY_ALM Failure in checking dual-endconfiguration consistency of thephysical and logical channels

Major

PATCH_ACT_TIMEOUT Duration of patch package inactivation state too long

Minor

PATCH_DEACT_TIMEOUT Duration of patch package indeactivation state too long

Minor

PATCH_PKGERR Patch package file error Major

PDU_OFF_ALM PDU unit is offline Critical

PM_BDI ODU layer PM section backwarddefect indication

Major

PM_BEI ODU layer PM section backward errorindication

Major

PM_BIP8_OVER ODU layer PM section BIP-8excessive error defect

Major

PM_BIP8_SD ODU layer PM section BIP-8degraded signal defect

Major

PM_TIM ODU layer PM section trail traceidentifier (TTI) mismatch

Major

PORT_MODULE_OFFLINE Client port module offline Major

PORTSWITCH_FAIL Optical switch switching failure Major

POWER_DIFF_DEFECT Power difference between monitoredworking and protection channels

Minor



2-9


POWER_DIFF_OVER Power difference between monitoredworking and protection channelscrosses the upper threshold

Major

POWER_FAIL Board's power failure Major

POWERALM Power status alarm Critical

PRBS_LSS Loss of PRBS (Pseudo-RandomBinary Sequence) signal

Minor

PRIORITY_VERIFY_ALM Path priority configurations at bothends are not consistent

Major

PS PS (protection switching) indication Major

PUM_BCM_ALM Working current of pump laser overthreshold

Major

PUM_COOL_EXC Cool current of pump laser overthreshold

Critical

PUM_TEM_ALM Working temperature of the pumplaser over threshold

Major

PWR_MIN_ALM Abnormal power supply (commonoverload or shortage)

Major

PWR_MAJ_ALM Abnormal power supply (severeoverload or shortage)

Critical

PWR_TEMP_OVERTH The power interface unit temperatureoverhigh alarm

Major

PW_SWITCH_EX Offline of DPFU boardBackup poweruse alarm

Critical

2.1.16 Alarm List RThis section used a table to list the alarms starting with R.


REAR_BD_OFFLINE Offline of DPFU board Major

RELAY_ALARM PMU relay alarm Critical

REM_SD Remote signal degrade Minor

REM_SF Remote signal failure alarm indication Minor

RL_CRITICAL_HI Critical high return loss alarm Critical

RL_CRITICAL_LOW Critical low return loss alarm Critical

2 Alarm List




Issue 08 (2011-10-30)


R_DATA_LOST Ethernet port receiving data lost Minor

R_LOC Loss of clock on receiving line Critical

R_LOF Loss of frame Critical

R_LOS Loss of signal Critical

R_OOF Out of frame Critical

RMON_ALM_ALIGNMENT_OVER

Alignment errors is over the upperthreshold

Minor

RMON_ALM_DROPEVENT_OVER

Statistics of drop packets events isover the upper threshold

Minor

RMON_ALM_FCSERROR_OVER

Statistics of check errors is over theupper threshold

Minor

RMON_ALM_INBADOCTS_OVER

Statistics of receiving bad packets isover the upper threshold

Minor

RMON_ALM_OUTBADOCTS_OVER

Statistics of transmitting bad packetsis over the upper threshold

Minor

R_SLIP Receiving side frame slipping Major

2.1.17 Alarm List SThis section used a table to list the alarms starting with S.


SCC_LOC Loss of SCC clock Critical

SECU_ALM Security alarm Major

SM_BDI OTU layer SM section backwarddefect indication

Major

SM_BEI OTU layer SM section backward errorindication

Major

SM_BIP8_OVER OTU layer SM section BIP-8excessive error defect

Major

SM_BIP8_SD OTU layer SM section BIP-8degraded signal defect

Major

SM_IAE OTU layer, SM section incomingalignment error

Major

SM_TIM OTU layer SM section trail traceidentifier (TTI) is mismatched

Major



2-11


SPEED_OVER The data rate exceeds the set limits Minor

SUBRACK_ID_CONFLICT Conflict of subrack ID. Critical

SUB_RACK_NUM_OUTRANGE Number of online slave subracks overthreshold

Critical

SUB_RACK_OFFLINE Slave subrack offline Critical

SUM_INPWR_HI Input optical power is too high Major

SUM_INPWR_LOW Input optical power is too low Major

SUM_OUTPWR_HI Output optical power is too high Major

SUM_OUTPWR_LOW Output optical power is too low Major

SWDL_ACTIVATED_TIMEOUT Activation time out Critical

SWDL_AUTOMATCH_INH Automatic match inhibited Minor

SWDL_CHGMNG_NOMATCH SCC board changed alarm Critical

SWDL_COMMIT_FAIL Commit failure alarm Minor

SWDL_INPROCESS NE is loading package Warning

SWDL_NEPKGCHECK Loss of file Critical

SWDL_PKG_NOBDSOFT Board software cancelled during theloading of package

Minor

SWDL_PKGVER_MM Package version conformance checkfailed

Minor

SWDL_ROLLBACK_FAIL NE rollback failed Minor

SYSLOG_COMM_FAIL NE and syslog server communicationfailed

Major

2.1.18 Alarm List TThis section used a table to list the alarms starting with T.


T_DATA_LOST Client-side transmitting data lost Minor

T_LOC Loss of transmit clock Major

T_SLIP Transmitted side frame slipping Major

TD Transmitter degrade Critical

TEM_HA Laser temperature is too high Major

2 Alarm List




Issue 08 (2011-10-30)


TEM_LA Laser temperature is too low Major

TEMP_ALARM The ambient temperature of the boardexceeds the threshold.

Minor

TF Transmission failure Critical

THUNDERALM Thunder protection circuit failure Minor

TP_LOC Transmission phase lock ring loss ofclock

Major

2.1.19 Alarm List VThis section used a table to list the alarms starting with V.


VCXO_LOC Local oscillator loss of clock Major

2.1.20 Alarm List WThis section used a table to list the alarms starting with W.


WAVE_LEN_LOCK_FAIL Wavelength locking failure alarm Critical

W_R_FAILURE Writing or reading chip register failed Major

WRG_BD_TYPE Physical board is mismatched withconfigured board

Major

2.2 Board Alarm ListLists the alarms of every board.

2.2.1 D40 Board Alarm List

AD_CHECK_FAIL NO_BD_PARA OMS_SSF-P

BD_STATUS OMS_FDI POWER_FAIL

FPGA_ABN OMS_FDI-O SUM_INPWR_HI



2-13

MODULE_COOLCUR_OVER

OMS_FDI-P SUM_INPWR_LOW

MODULE_TEMP_OVER OMS_LOS-P TEMP_ALARM

MUT_LOS OMS_SSF W_R_FAILURE

NO_BD_SOFT OMS_SSF-O

2.2.2 DCP Board Alarm List

BD_STATUS NO_BD_SOFT PS

FPGA_ABN POWER_DIFF_DEFECT R_LOS

MUT_LOS POWER_DIFF_OVER TEMP_ALARM

NO_BD_PARA POWER_FAIL W_R_FAILURE

2.2.3 ELOG/ELOGS Board Alarm List

AD_CHECK_FAIL OCH_FDI-O PORT_MODULE_OFFLINE

ALM_DATA_RLOS OCH_FDI-P POWER_FAIL

ALM_DATA_TLOS OCH_LOS-P PRBS_LSS

BD_STATUS OCH_OCI PW_SWITCH_EX

BEFFEC_EXC OCH_SSF R_LOC

REM_SF OCH_SSF-O R_LOS

CLT_MM OCH_SSF-P RMON_ALM_FCSERROR_OVER

COMMUN_FAIL ODU_AIS RMON_ALM_INBADOCTS_OVER

FPGA_ABN ODU_LCK RMON_ALM_OUTBADOCTS_OVER

IN_PWR_HIGH ODU_OCI SM_BDI

IN_PWR_LOW OPU2_PLM SM_BEI

LINK_ERR OTU_AIS SM_BIP8_OVER

LOOP_ALM OTU_LOF SM_BIP8_SD

LSR_COOL_ALM OTU_LOM SM_IAE

LSR_WILL_DIE OUT_PWR_HIGH SM_TIM

2 Alarm List




Issue 08 (2011-10-30)

LTEMP_OVER OUT_PWR_LOW TD

MODULE_TEMP_OVER PM_BDI TEMP_ALARM

NO_BD_PARA PM_BEI TF

NO_BD_SOFT PM_BIP8_OVER W_R_FAILURE

OCH_FDI PM_BIP8_SD WAVE_LEN_LOCK_FAIL

L_SYNC PM_TIM

2.2.4 ETMX/ETMXS Board Alarm ListAD_CHECK_FAIL NO_BD_SOFT PM_TIM

B1_EXC OCH_FDI PORT_MODULE_OFFLINE

B1_SD OCH_FDI-O POWER_FAIL

B2_EXC OCH_FDI-P PRBS_LSS

B2_SD OCH_LOS-P PW_SWITCH_EX

BD_STATUS OCH_OCI R_LOC

BEFFEC_EXC OCH_SSF R_LOF

REM_SD OCH_SSF-O R_LOS

REM_SF OCH_SSF-P R_OOF

COMMUN_FAIL ODU_AIS SM_BDI

FEC_LOF ODU_LCK SM_BEI

MS_AIS ODU_OCI SM_BIP8_OVER

FPGA_ABN OPU2_PLM SM_BIP8_SD

IN_PWR_HIGH OTU_AIS SM_IAE

IN_PWR_LOW OTU_LOF SM_TIM

J0_MM OTU_LOM TD

LOOP_ALM OUT_PWR_HIGH TEMP_ALARM

LSR_COOL_ALM OUT_PWR_LOW TF

LSR_WILL_DIE PM_BDI W_R_FAILURE

LTEMP_OVER PM_BEI WAVE_LEN_LOCK_FAIL

MODULE_TEMP_OVER PM_BIP8_OVER ODU_TCM1_BEI

NO_BD_PARA PM_BIP8_SD ODU_TCM1_LCK



2-15

ODU_TCM1_AIS ODU_TCM1_BDI ODU_TCM1_SD

ODU_TCM1_DEG ODU_TCM1_EXC ODU_TCM2_AIS

ODU_TCM1_LTC ODU_TCM1_OCI ODU_TCM2_DEG

ODU_TCM1_SSF ODU_TCM1_TIM ODU_TCM2_LTC

ODU_TCM2_BDI ODU_TCM2_BEI ODU_TCM2_SSF

ODU_TCM2_EXC ODU_TCM2_LCK ODU_TCM3_BDI

ODU_TCM2_OCI ODU_TCM2_SD ODU_TCM3_EXC

ODU_TCM2_TIM ODU_TCM3_AIS ODU_TCM3_OCI

ODU_TCM3_BEI ODU_TCM3_DEG ODU_TCM3_TIM

ODU_TCM3_LCK ODU_TCM3_LTC ODU_TCM4_BEI

ODU_TCM3_SD ODU_TCM3_SSF ODU_TCM4_LCK










ODU_TCM6_LCK ODU_TCM6_LTC

ODU_TCM6_SD ODU_TCM6_SSF

2.2.5 FDG Board Alarm ListAD_CHECK_FAIL NO_BD_PARA POWER_FAIL

AU_AIS NO_BD_SOFT PS

AU_LOP OCH_FDI PW_SWITCH_EX

B1_EXC OCH_FDI-O R_LOF

B1_SD OCH_FDI-P R_LOS

B2_EXC OCH_LOS-P R_DATA_LOST

2 Alarm List




Issue 08 (2011-10-30)

B2_SD OCH_OCI R_LOC

BD_STATUS OCH_SSF R_OOF

BEFFEC_EXC OCH_SSF-O RMON_ALM_FCSERROR_OVER

REM_SF OCH_SSF-P RMON_ALM_INBADOCTS_OVER

FEC_LOF ODU_AIS RMON_ALM_OUTBADOCTS_OVER

FEC_OOF ODU_LCK SM_BDI

FPGA_ABN ODU_OCI SM_BEI

IN_PWR_HIGH OTU_AIS SM_BIP8_OVER

IN_PWR_LOW OTU_LOF SM_BIP8_SD

J0_MM OTU_LOM SM_IAE

LINK_STATUS OUT_PWR_HIGH SM_TIM

LOOP_ALM OUT_PWR_LOW T_DATA_LOST

LSR_COOL_ALM PM_BDI T_LOC

LSR_WILL_DIE PM_BEI TD

LTEMP_OVER PM_BIP8_OVER TEMP_ALARM

MS_AIS PM_BIP8_SD TF

MS_RDI PM_TIM VCXO_LOC

MS_REI PORT_MODULE_OFFLINE

W_R_FAILURE

2.2.6 FIU Board Alarm ListE3FIU

AD_CHECK_FAIL NO_BD_PARA TEMP_ALARM

BD_STATUS NO_BD_SOFT W_R_FAILURE

FPGA_ABN OOS_LOST

E2FIU

AD_CHECK_FAIL NO_BD_SOFT TEMP_ALARM



2-17

BD_STATUS POWER_FAIL W_R_FAILURE

MUT_LOS SUM_INPWR_HI

NO_BD_PARA SUM_INPWR_LOW

2.2.7 FMU Board Alarm List

BD_STATUS FPGA_ABN TEMP_ALARM

FIBER_CRITICAL MOD_COM_FAIL W_R_FAILURE

FIBER_MAJOR NO_BD_PARA

FIBER_MINOR NO_BD_SOFT

2.2.8 HBA Board Alarm List

BD_STATUS MODULE_TEMP_OVER PUMP_COOL_EXC

FPGA_ABN MUT_LOS PUM_BCM_ALM

IN_PWR_HIGH NO_BD_SOFT PUM_TEM_ALM

IN_PWR_LOW OA_LOW_GAIN TEMP_ALARM

LSR_WILL_DIE OUT_PWR_HIGH W_R_FAILURE

MOD_COM_FAIL POWER_FAIL LASER_HAZARD_WARNING

2.2.9 ITL Board Alarm List

BD_STATUS FPGA_ABN NO_BD_SOFT

TEMP_ALARM

2.2.10 LBE/LBES Board Alarm List

AD_CHECK_FAIL NO_BD_PARA PM_BIP8_SD

ALM_DATA_RLOS OCH_FDI PM_TIM

ALM_DATA_TLOS OCH_FDI-O PORT_MODULE_OFFLINE

2 Alarm List




Issue 08 (2011-10-30)

BD_STATUS OCH_FDI-P POWER_FAIL

BEFFEC_EXC OCH_LOS-P PW_SWITCH_EX

REM_SF OCH_OCI R_LOC

REM_SD OCH_SSF R_LOS

COMMUN_FAIL OCH_SSF-O RMON_ALM_FCSERROR_OVER

FEC_LOF OCH_SSF-P SM_BDI

FEC_OOF ODU_AIS SM_BEI

FPGA_ABN ODU_LCK SM_BIP8_OVER

IN_PWR_HIGH ODU_OCI SM_BIP8_SD

IN_PWR_LOW OTU_AIS SM_IAE

LINK_ERR OTU_LOF SM_TIM

LOOP_ALM OTU_LOM TD

LSR_COOL_ALM OUT_PWR_HIGH TEMP_ALARM

LSR_WILL_DIE OUT_PWR_LOW TF

LTEMP_OVER PM_BDI W_R_FAILURE

MODULE_TEMP_OVER

PM_BEI WAVE_LEN_LOCK_FAIL

NO_BD_SOFT PM_BIP8_OVER L_SYNC

2.2.11 LBF/LBFS Board Alarm ListAD_CHECK_FAIL NO_BD_SOFT PORT_MODULE_OFFLINE

ALM_DATA_RLOS NO_BD_PARA POWER_FAIL

ALM_DATA_TLOS OCH_FDI PRBS_LSS

B1_EXC OCH_FDI-O PW_SWITCH_EX

B1_SD OCH_FDI-P R_LOC

B2_EXC OCH_LOS-P R_LOF

B2_SD OCH_OCI R_LOS

BD_STATUS OCH_SSF R_OOF

BEFFEC_EXC OCH_SSF-O RMON_ALM_ALIGNMENT_OVER



2-19

REM_SD OCH_SSF-P RMON_ALM_DROPEVENT_OVER

REM_SF ODU_AIS RMON_ALM_FCSERROR_OVER

COMMUN_FAIL ODU_LCK SM_BDI

FEC_LOF ODU_OCI SM_BEI

FEC_OOF OPU2_PLM SM_BIP8_OVER

FPGA_ABN OTU_AIS SM_BIP8_SD

IN_PWR_HIGH OTU_LOF SM_IAE

IN_PWR_LOW OTU_LOM SM_TIM

J0_MM OUT_PWR_HIGH TD

LINK_ERR OUT_PWR_LOW TEMP_ALARM

LOOP_ALM PM_BDI TF

LSR_COOL_ALM PM_BEI W_R_FAILURE

LSR_WILL_DIE PM_BIP8_OVER WAVE_LEN_LOCK_FAIL

LTEMP_OVER PM_BIP8_SD ODU_TCM1_BEI

MS_AIS PM_TIM ODU_TCM1_LCK










ODU_TCM3_LCK ODU_TCM3_LTC ODU_TCM4_BEI

ODU_TCM3_SD ODU_TCM3_SSF ODU_TCM4_LCK





2 Alarm List




Issue 08 (2011-10-30)






ODU_TCM6_LCK ODU_TCM6_LTC MODULE_TEMP_OVER

ODU_TCM6_SD ODU_TCM6_SSF L_SYNC

2.2.12 LOG/LOGS Board Alarm List

AD_CHECK_FAIL OCH_FDI-O PORT_MODULE_OFFLINE

ALM_DATA_RLOS OCH_FDI-P POWER_FAIL

ALM_DATA_TLOS OCH_LOS-P PRBS_LSS

BD_STATUS OCH_OCI PW_SWITCH_EX

BEFFEC_EXC OCH_SSF R_LOC

REM_SF OCH_SSF-O R_LOS

CLT_MM OCH_SSF-P RMON_ALM_FCSERROR_OVER

COMMUN_FAIL ODU_AIS RMON_ALM_INBADOCTS_OVER

FPGA_ABN ODU_LCK RMON_ALM_OUTBADOCTS_OVER

IN_PWR_HIGH ODU_OCI SM_BDI

IN_PWR_LOW OTU_AIS SM_BEI

LINK_ERR OTU_LOF SM_BIP8_OVER

LOOP_ALM OTU_LOM SM_BIP8_SD

LSR_COOL_ALM OUT_PWR_HIGH SM_IAE

LSR_WILL_DIE OUT_PWR_LOW SM_TIM

LTEMP_OVER PM_BDI TD

MODULE_TEMP_OVER

PM_BEI TEMP_ALARM

NO_BD_PARA PM_BIP8_OVER TF

NO_BD_SOFT PM_BIP8_SD W_R_FAILURE



2-21

OCH_FDI PM_TIM WAVE_LEN_LOCK_FAIL

L_SYNC REM_SD

2.2.13 LQM Board Alarm ListAD_CHECK_FAIL OCH_FDI POWER_FAIL

B1_SD OCH_FDI-O PW_SWITCH_EX

B1_EXC OCH_FDI-P R_DATA_LOST

BD_STATUS OCH_LOS-P R_LOC

BEFFEC_EXC OCH_OCI R_LOF

REM_SD OCH_SSF R_LOS

REM_SF OCH_SSF-O R_OOF

DSP_LOAD_FAIL OCH_SSF-P RMON_ALM_FCSERROR_OVER

ESCON_CODE_ERROR ODU_AIS RMON_ALM_FCSERROR_UNDER

FPGA_ABN ODU_LCK SM_BDI

IN_PWR_HIGH ODU_OCI SM_BEI

IN_PWR_LOW OTU_AIS SM_BIP8_OVER

J0_MM OTU_LOF SM_BIP8_SD

L_SYNC OTU_LOM SM_IAE

LINK_STATUS OUT_PWR_HIGH SM_TIM

LOOP_ALM OUT_PWR_LOW T_DATA_LOST

LSR_COOL_ALM PM_BDI TD

LSR_WILL_DIE PM_BEI TEMP_ALARM

LTEMP_OVER PM_BIP8_OVER TF

MS_AIS PM_BIP8_SD VCXO_LOC

NO_BD_PARA PM_TIM W_R_FAILURE

NO_BD_SOFT PORT_MODULE_OFF-LINE

2 Alarm List




Issue 08 (2011-10-30)

2.2.14 LU40 Board Alarm ListAD_CHECK_FAIL B1_SD BD_STATUS

B1_EXC BEFFEC_SD CLT_MM

BEFFEC_EXC DCM_INSUFF FPGA_ABN

COMMUN_FAIL IN_PWR_HIGH IN_PWR_LOW

HARD_FAIL LINK_ERR LOOP_ALM

J0_MM LSR_WILL_DIE LTEMP_OVER

LSR_COOL_ALM NO_BD_PARA NO_BD_SOFT

MODULE_TEMP_OVER OCH_FDI-O OCH_FDI-P

OCH_FDI OCH_OCI OCH_SSF

OCH_LOS-P OCH_SSF-P ODU_AIS

OCH_SSF-O ODU_OCI OPU3_PLM

ODU_LCK OTU_LOF OTU_LOM

OTU_AIS OUT_PWR_LOW PM_BDI

OUT_PWR_HIGH PM_BIP8_OVER PM_BIP8_SD

PM_BEI PORT_MODULE_OFF-LINE

POWER_FAIL

PM_TIM REM_SD REM_SF

PRBS_LSS RMON_ALM_DROPEVENT_OVER



R_LOF R_LOS

R_LOC SM_BEI SM_BIP8_OVER

SM_BDI SM_IAE SM_TIM

SM_BIP8_SD TF WAVE_LEN_LOCK_FAIL

TEMP_ALARM W_R_FAILURE ODU_TCM1_BEI

ODU_TCM1_AIS ODU_TCM1_BDI ODU_TCM1_LCK

ODU_TCM1_DEG ODU_TCM1_EXC ODU_TCM1_SD

ODU_TCM1_LTC ODU_TCM1_OCI ODU_TCM2_AIS

ODU_TCM1_SSF ODU_TCM1_TIM ODU_TCM2_DEG

ODU_TCM2_BDI ODU_TCM2_BEI ODU_TCM2_LTC



2-23

ODU_TCM2_EXC ODU_TCM2_LCK ODU_TCM2_SSF

ODU_TCM2_OCI ODU_TCM2_SD ODU_TCM3_BDI

ODU_TCM2_TIM ODU_TCM3_AIS ODU_TCM3_EXC

ODU_TCM3_BEI ODU_TCM3_DEG ODU_TCM3_OCI

ODU_TCM3_LCK ODU_TCM3_LTC ODU_TCM3_TIM

ODU_TCM3_SD ODU_TCM3_SSF ODU_TCM4_BEI












2.2.15 LU40S Board Alarm ListAD_CHECK_FAIL B1_SD BD_STATUS

B1_EXC BEFFEC_SD CLT_MM

BEFFEC_EXC DCM_INSUFF FPGA_ABN

COMMUN_FAIL IN_PWR_HIGH IN_PWR_LOW

HARD_FAIL LINK_ERR LOOP_ALM

J0_MM LSR_WILL_DIE LTEMP_OVER

LSR_COOL_ALM NO_BD_PARA NO_BD_SOFT

MODULE_TEMP_OVER OCH_FDI-O OCH_FDI-P

OCH_FDI OCH_OCI OCH_SSF

OCH_LOS-P OCH_SSF-P ODU_AIS

OCH_SSF-O ODU_OCI OPU3_PLM

2 Alarm List




Issue 08 (2011-10-30)

ODU_LCK OTU_LOF OTU_LOM

OTU_AIS OUT_PWR_LOW PM_BDI

OUT_PWR_HIGH PM_BIP8_OVER PM_BIP8_SD

PM_BEI PORT_MODULE_OFF-LINE

POWER_FAIL

PM_TIM REM_SD REM_SF

PRBS_LSS RMON_ALM_DROPEVENT_OVER



R_LOF R_LOS

R_LOC SM_BEI SM_BIP8_OVER

SM_BDI SM_IAE SM_TIM

SM_BIP8_SD TF WAVE_LEN_LOCK_FAIL

TEMP_ALARM W_R_FAILURE ODU_TCM1_BEI





















2-25





2.2.16 LUR40/LUR40S Board Alarm List

AD_CHECK_FAIL BD_STATUS BEFFEC_EXC

BEFFEC_SD COMMUN_FAIL DCM_INSUFF

FPGA_ABN HARD_FAIL IN_PWR_HIGH

IN_PWR_LOW 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

OPU3_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 R_LOC R_LOS

SM_BDI SM_BEI SM_BIP8_OVER

SM_BIP8_SD SM_IAE SM_TIM

TEMP_ALARM TF W_R_FAILURE

2.2.17 LWC1 Board Alarm List

AD_CHECK_FAIL NO_BD_PARA PORT_MODULE_OFFLINE

B1_EXC NO_BD_SOFT POWER_FAIL

B1_SD OCH_FDI PS

B2_EXC OCH_FDI-O PW_SWITCH_EX

2 Alarm List




Issue 08 (2011-10-30)

B2_SD OCH_FDI-P R_LOC

BD_STATUS OCH_LOS-P R_LOF

BEFFEC_EXC OCH_OCI R_LOS

REM_SD OCH_SSF R_OOF

REM_SF OCH_SSF-O SM_BDI

COMMUN_FAIL OCH_SSF-P SM_BEI

FEC_LOF ODU_AIS SM_BIP8_OVER

FEC_OOF ODU_LCK SM_BIP8_SD

FPGA_ABN ODU_OCI SM_IAE

IN_PWR_HIGH OTU_AIS SM_TIM

IN_PWR_LOW OTU_LOF TD

J0_MM OTU_LOM TEMP_ALARM

LOOP_ALM OUT_PWR_HIGH TF

LSR_COOL_ALM OUT_PWR_LOW VCXO_LOC



MODULE_TEMP_OVER PM_BIP8_OVER PM_TIM

MS_AIS PM_BIP8_SD

2.2.18 LWF/LWFS Board Alarm ListAD_CHECK_FAIL NO_BD_PARA PM_TIM

B1_EXC OCH_FDI PORT_MODULE_OFFLINE


B2_EXC OCH_FDI-P PS

B2_SD OCH_LOS-P PW_SWITCH_EX

BD_STATUS OCH_OCI R_LOC

BEFFEC_EXC OCH_SSF R_LOF

REM_SD OCH_SSF-O R_LOS

REM_SF OCH_SSF-P R_OOF

COMMUN_FAIL ODU_AIS SM_BDI



2-27

FEC_LOF ODU_LCK SM_BEI

FEC_OOF ODU_OCI SM_BIP8_OVER

FPGA_ABN OPU2_PLM SM_BIP8_SD

IN_PWR_HIGH OTU_AIS SM_IAE

IN_PWR_LOW OTU_LOF SM_TIM

J0_MM OTU_LOM TD

LOOP_ALM OUT_PWR_HIGH TEMP_ALARM

LSR_COOL_ALM OUT_PWR_LOW TF



MODULE_TEMP_OVER PM_BIP8_OVER MS_AIS

NO_BD_SOFT PM_BIP8_SD ODU_TCM1_BEI




















2 Alarm List




Issue 08 (2011-10-30)




2.2.19 LWX Board Alarm ListB1_EXC OCH_FDI R_LOC

B1_SD OCH_FDI-O R_LOF

BD_STATUS OCH_FDI-P R_LOS

CFGBD_FAIL OCH_LOS-P SPEED_OVER

FCSERRORS_OVER OCH_OCI TD

FPGA_ABN OCH_SSF TEM_HA

IN_PWR_HIGH OCH_SSF-O TEM_LA

IN_PWR_LOW OCH_SSF-P TEMP_ALARM

J0_MM OUT_PWR_HIGH TF

LOOP_ALM OUT_PWR_LOW TP_LOC

LSR_COOL_ALM PORT_MODULE_OFF-LINE

W_R_FAILURE

LSR_WILL_DIE POWER_FAIL PW_SWITCH_EX

NO_BD_SOFT PRBS_LSS NO_BD_PARA

2.2.20 M40 Board Alarm ListAD_CHECK_FAIL NO_BD_SOFT SUM_OUTPWR_HI

BD_STATUS NO_BD_PARA SUM_OUTPWR_LOW

FPGA_ABN OMS_BDI TEMP_ALARM

MODULE_COOLCUR_OVER

OMS_BDI-O W_R_FAILURE

MODULE_TEMP_OVER OMS_BDI-P

MUT_LOS POWER_FAIL



2-29

2.2.21 MCA Board Alarm List

BD_STATUS FPGA_ABN PORTSWITCH_FAIL

CHAN_ADD NO_BD_PARA TEMP_ALARM

CHAN_LOS NO_BD_SOFT W_R_FAILURE

2.2.22 MR2 Board Alarm List

BD_STATUS FPGA_ABN NO_BD_SOFT

TEMP_ALARM

2.2.23 MWA Board Alarm List

BD_STATUS TEMP_ALARM NO_BD_SOFT

FPGA_ABN

2.2.24 MWF Board Alarm List

BD_STATUS TEMP_ALARM NO_BD_SOFT

FPGA_ABN

2.2.25 OAU Board Alarm List

AD_CHECK_FAIL IN_PWR_LOW POWER_FAIL

BD_STATUS LSR_WILL_DIE PUM_BCM_ALM

DSP_LOAD_FAIL MUT_LOS PUMP_COOL_EXC

EDFA_TEMP_OVER NO_BD_SOFT PUM_TEM_ALM

FPGA_ABN NO_BD_PARA TEMP_ALARM

IN_PWR_HIGH OA_LOW_GAIN W_R_FAILURE

LASER_HAZARD_WARNING

2 Alarm List




Issue 08 (2011-10-30)

2.2.26 OBU Board Alarm List







LASER_HAZARD_WARNING

2.2.27 OLP Board Alarm List

AD_CHECK_FAIL NO_BD_SOFT POWER_FAIL

BD_STATUS IN_PWR_HIGH PS

FPGA_ABN IN_PWR_LOW R_LOS

MUT_LOS POWER_DIFF_DEFECT TEMP_ALARM

NO_BD_PARA POWER_DIFF_OVER W_R_FAILURE

2.2.28 OPU Board Alarm List







2.2.29 PMU Board Alarm List

BD_STATUS PWR_MIN_ALM TEMP_ALARM

PDU_OFF_ALM POWERALM THUNDERALM



2-31

POWER_FAIL REAR_BD_OFFLINE

PWR_MAJ_ALM RELAY_ALARM

2.2.30 RMU9 Board Alarm List

AD_CHECK_FAIL OMS_BDI-O PORT_MODULE_OFF-LINE

BD_STATUS OMS_BDI-P POWER_FAIL

FPGA_ABN OMS_FDI SUM_INPWR_HI

MODULE_TEMP_OVER

OMS_FDI-O SUM_INPWR_LOW

MUT_LOS OMS_FDI-P SUM_OUTPWR_HI

MUT_TLOS OMS_LOS-P SUM_OUTPWR_LOW

NO_BD_PARA OMS_SSF TEMP_ALARM

NO_BD_SOFT OMS_SSF-O

OMS_BDI OMS_SSF-P

2.2.31 RPC Board Alarm List

AD_CHECK_FAIL NO_BD_PARA PUMP_COOL_EXC

BD_STATUS NO_BD_SOFT RL_CRITICAL_HI

FPGA_ABN OUT_PWR_HIGH RL_CRITICAL_LOW

GAINDATA_MIS OUT_PWR_LOW TEMP_ALARM

LOCK_CUR_FAIL POWER_FAIL W_R_FAILURE

LSR_WILL_DIE PUM_BCM_ALM LASER_HAZARD_WARNING

2.2.32 SC1/SC2 Board Alarm List

BD_STATUS NO_BD_SOFT SCC_LOC

FPGA_ABN NO_BD_PARA T_SLIP

IN_PWR_HIGH OSC_LOS TD

2 Alarm List




Issue 08 (2011-10-30)

IN_PWR_LOW OSC_RDI TEMP_ALARM

LOOP_ALM OUT_PWR_HIGH TF

LSR_COOL_ALM OUT_PWR_LOW VCXO_LOC

LSR_WILL_DIE R_LOF W_R_FAILURE

LTI R_LOS

R_SLIP

2.2.33 SCC Board Alarm ListALM_PIUA_OFFLINE ALM_PIUB_OFFLINE BD_STATUS

BD_VER_NMAT BOOTROM_BAD CFGDATA_OUTRANGE

CFG_VERIFY DBMS_ERROR DBMS_PROTECT_MODE

FAN_FAIL FUSE_ALARM INPWR_FAIL

K1_K2_M K2_M LAN_LOC

MAIL_ERR MDL_ALARM NEBD_XC_DIF

NESOFT_MM NESTATE_INSTALL NO_BD_SOFT

OPS_MAIN_BAK_ATTR_DIFF

OPS_PS_FAIL OPS_PS_INDI

OUTPWR_FAIL OPS_PS_FIXED PATCH_ERR

PATCHFILE_NOTEXIST PATH_VERIFY_ALM PBU_BD_OFFLINE

PATCH_NOT_CONFIRM PRIORITY_VERIFY_ALM PWR_MAJ_ALM

PATCH_DEACT_TIME-OUT

PATCH_ACT_TIMEOUT PATCH_PKGERR

POWER_FAIL REAR_BD_OFFLINE RELAY_ALARM

PWR_TEMP_OVERTH SWDL_ACTIVATED_TIMEOUT

SWDL_AUTOMATCH_INH

SECU_ALM SWDL_COMMIT_FAIL SWDL_INPROCESS

SWDL_NEPKGCHECK SWDL_CHGMNG_NO-MATCH

SWDL_PKG_NOBD-SOFT

SWDL_PKGVER_MM SYSLOG_COMM_FAIL TEMP_ALARM

SWDL_ROLLBACK_FAIL W_R_FAILURE WRG_BD_TYPE



2-33

2.2.34 TMR/TMRS Board Alarm ListAD_CHECK_FAIL OCH_LOS-P PORT_MODULE_OFF-

LINE

BD_STATUS OCH_OCI POWER_FAIL

BEFFEC_EXC OCH_SSF PW_SWITCH_EX

COMMUN_FAIL OCH_SSF-O R_LOC

FEC_LOF OCH_SSF-P R_LOS

FEC_OOF ODU_AIS SM_BDI

FPGA_ABN ODU_LCK SM_BEI

IN_PWR_HIGH ODU_OCI SM_BIP8_OVER

IN_PWR_LOW OTU_AIS SM_BIP8_SD

LSR_COOL_ALM OTU_LOF SM_IAE

LSR_WILL_DIE OTU_LOM SM_TIM

LTEMP_OVER OUT_PWR_HIGH TD

MODULE_TEMP_OVER OUT_PWR_LOW TEMP_ALARM

NO_BD_SOFT PM_BDI TF

NO_BD_PARA PM_BEI W_R_FAILURE

OCH_FDI PM_BIP8_OVER WAVE_LEN_LOCK_FAIL

OCH_FDI-O PM_BIP8_SD

OCH_FDI-P PM_TIM

2.2.35 TMX/TMXS Board Alarm ListAD_CHECK_FAIL MS_RDI PM_BIP8_SD

B1_EXC MS_REI PM_TIM

B1_SD NO_BD_PARA POWER_FAIL

B2_EXC NO_BD_SOFT PW_SWITCH_EX

B2_SD OCH_FDI PORT_MODULE_OFFLINE

BD_STATUS OCH_FDI-O PRBS_LSS

BEFFEC_EXC OCH_FDI-P R_LOC

REM_SD OCH_LOS-P R_LOF

2 Alarm List




Issue 08 (2011-10-30)

REM_SF OCH_OCI R_LOS

COMMUN_FAIL OCH_SSF R_OOF

FEC_LOF OCH_SSF-O SM_BDI

FEC_OOF OCH_SSF-P SM_BEI

FPGA_ABN ODU_AIS SM_BIP8_OVER

IN_PWR_HIGH ODU_LCK SM_BIP8_SD

IN_PWR_LOW ODU_OCI SM_IAE

J0_MM OTU_AIS SM_TIM

LOOP_ALM OTU_LOF T_LOC

LSR_COOL_ALM OTU_LOM TD

LSR_WILL_DIE OUT_PWR_HIGH TEMP_ALARM

LTEMP_OVER OUT_PWR_LOW TF

MODULE_TEMP_OVER PM_BDI W_R_FAILURE

MS_AIS PM_BEI WAVE_LEN_LOCK_FAIL

PM_BIP8_OVER

2.2.36 TMX40/TMX40S Board Alarm ListAD_CHECK_FAIL ALM_DATA_RLOS ALM_DATA_TLOS

B1_EXC B1_SD BD_STATUS

BEFFEC_EXC CLT_MM COMMUN_FAIL

DCM_INSUFF FPGA_ABN HARD_FAIL

IN_PWR_HIGH IN_PWR_LOW J0_MM

LINK_ERR 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 OPU3_PLM OTU_AIS

OTU_LOF OTU_LOM OUT_PWR_HIGH



2-35

OUT_PWR_LOW PM_BDI PM_BEI

PM_BIP8_OVER PM_BIP8_SD PM_TIM

PORT_MODULE_OFF-LINE

POWER_FAIL PRBS_LSS

REM_SD REM_SF R_LOC

R_LOF R_LOS SM_BDI

SM_BEI SM_BIP8_OVER SM_BIP8_SD

SM_IAE SM_TIM TEMP_ALARM

ODU_TCM1_AIS ODU_TCM1_BDI ODU_TCM1_BEI

ODU_TCM1_DEG ODU_TCM1_EXC ODU_TCM1_LCK

ODU_TCM1_LTC ODU_TCM1_OCI ODU_TCM1_SD

ODU_TCM1_SSF ODU_TCM1_TIM ODU_TCM2_AIS

ODU_TCM2_BDI ODU_TCM2_BEI ODU_TCM2_DEG

ODU_TCM2_EXC ODU_TCM2_LCK ODU_TCM2_LTC

ODU_TCM2_OCI ODU_TCM2_SD ODU_TCM2_SSF

ODU_TCM2_TIM ODU_TCM3_AIS ODU_TCM3_BDI

ODU_TCM3_BEI ODU_TCM3_DEG ODU_TCM3_EXC

ODU_TCM3_LCK ODU_TCM3_LTC ODU_TCM3_OCI

ODU_TCM3_SD ODU_TCM3_SSF ODU_TCM3_TIM

ODU_TCM4_AIS ODU_TCM4_BDI ODU_TCM4_BEI

ODU_TCM4_DEG ODU_TCM4_EXC ODU_TCM4_LCK

ODU_TCM4_LTC ODU_TCM4_OCI ODU_TCM4_SD

ODU_TCM4_SSF ODU_TCM4_TIM ODU_TCM5_AIS

ODU_TCM5_BDI ODU_TCM5_BEI ODU_TCM5_DEG

ODU_TCM5_EXC ODU_TCM5_LCK ODU_TCM5_LTC

ODU_TCM5_OCI ODU_TCM5_SD ODU_TCM5_SSF

ODU_TCM5_TIM ODU_TCM6_AIS ODU_TCM6_BDI

ODU_TCM6_BEI ODU_TCM6_DEG ODU_TCM6_EXC

ODU_TCM6_LCK ODU_TCM6_LTC ODU_TCM6_OCI

ODU_TCM6_SD ODU_TCM6_SSF ODU_TCM6_TIM

TF W_R_FAILURE

2 Alarm List




Issue 08 (2011-10-30)

2.2.37 TRC1 Board Alarm ListAD_CHECK_FAIL NO_BD_PARA PM_BIP8_SD

B1_EXC OCH_FDI PM_TIM


B2_EXC OCH_FDI-P PW_SWITCH_EX

B2_SD OCH_LOS-P R_LOC

BD_STATUS OCH_OCI R_LOF

BEFFEC_EXC OCH_SSF R_LOS

COMMUN_FAIL OCH_SSF-O R_OOF

FEC_LOF OCH_SSF-P SM_BDI

FEC_OOF ODU_AIS SM_BEI

FPGA_ABN ODU_LCK SM_BIP8_OVER

IN_PWR_HIGH ODU_OCI SM_BIP8_SD

IN_PWR_LOW OTU_AIS SM_IAE

J0_MM OTU_LOF SM_TIM

LSR_COOL_ALM OTU_LOM TD

LSR_WILL_DIE OUT_PWR_HIGH TEMP_ALARM

LTEMP_OVER OUT_PWR_LOW TF

MODULE_TEMP_OVER PM_BDI W_R_FAILURE

PM_BIP8_OVER PM_BEI WAVE_LEN_LOCK_FAIL

NO_BD_SOFT

2.2.38 V40 Board Alarm ListAD_CHECK_FAIL NO_BD_SOFT POWER_FAIL

BD_STATUS NO_BD_PARA SUM_OUTPWR_HI

FPGA_ABN OMS_BDI SUM_OUTPWR_LOW

MODULE_TEMP_OVER OMS_BDI-O TEMP_ALARM

MUT_LOS OMS_BDI-P W_R_FAILURE



2-37

2.2.39 VA4 Board Alarm List

AD_CHECK_FAIL NO_BD_PARA POWER_FAIL

BD_STATUS NO_BD_SOFT R_LOS

IN_PWR_HIGH OUT_PWR_HIGH TEMP_ALARM

IN_PWR_LOW OUT_PWR_LOW 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 MODULE_TEMP_OVER POWER_FAIL

BD_STATUS NO_BD_PARA TEMP_ALARM

FPGA_ABN NO_BD_SOFT CHAN_LOS

HARD_BAD PORT_MODULE_OFFLINE

2.2.42 WSD9 Board Alarm List

AD_CHECK_FAIL OMS_BDI OMS_SSF-O

BD_STATUS OMS_BDI_O OMS_SSF-P

FPGA_ABN OMS_BDI_P POWER_FAIL

MOD_COM_FAIL OMS_FDI SUM_INPWR_HI

MODULE_TEMP_OVER OMS_FDI-O SUM_INPWR_LOW

MUT_LOS OMS_FDI-P TEMP_ALARM

NO_BD_PARA OMS_LOS-P W_R_FAILURE

NO_BD_SOFT OMS_SSF

2.2.43 WSM9 Board Alarm List

AD_CHECK_FAIL NO_BD_SOFT OMS_SSF

2 Alarm List




Issue 08 (2011-10-30)

BD_STATUS OMS_BDI OMS_SSF-O

FPGA_ABN OMS_BDI_O OMS_SSF-P

MOD_COM_FAIL OMS_BDI_P POWER_FAIL

MODULE_TEMP_OVER OMS_FDI SUM_INPWR_HI

MUT_LOS OMS_FDI-O SUM_INPWR_LOW

MUT_TLOS OMS_FDI-P TEMP_ALARM


2.2.44 WSMD2 Board Alarm ListAD_CHECK_FAIL BD_STATUS FPGA_ABN

MODULE_TEMP_OVER MOD_COM_FAIL 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

2.2.45 WSMD4 Board Alarm ListAD_CHECK_FAIL NO_BD_SOFT OMS_SSF

BD_STATUS OMS_BDI OMS_SSF-O

FPGA_ABN OMS_BDI-O OMS_SSF-P

MOD_COM_FAIL OMS_BDI-P POWER_FAIL

MODULE_TEMP_OVER OMS_FDI SUM_INPWR_HI

MUT_LOS OMS_FDI-O SUM_INPWR_LOW

MUT_TLOS OMS_FDI-P TEMP_ALARM




2-39

3 Alarm Processing

About This Chapter

3.1 Common Alarm ProcessingThis chapter describes common information relevant to alarm handling, including alarmdescriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarmhandling procedures.

3.2 Alarm ProcessingThis chapter describes information relevant to alarm handling, including alarm descriptions,alarm parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference 3 Alarm Processing


3-1

3.1 Common Alarm ProcessingThis chapter describes common information relevant to alarm handling, including alarmdescriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarmhandling procedures.

NOTE

In the case of an alarm, see its handling procedure to clear it; if this alarm persists, contact Huawei engineersfor troubleshooting.

The alarm handling involves board reset, either of software or hardware. Software reset andhardware 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 hardwarereset of the SCC will result in reconfiguration of the key hardware, such as FPGA reloading;the upper-layer software need be restarted.

l Reset of other boards: a reset of software on other boards does not affect running serviceswhile a reset of hardware on other boards does. A mis-reset of such a board affects thecommunication 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 thereceived bytes and compares the number with the number of last time. The alarm is generatedwhen 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 Alarm Type

Minor Communication alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1 Indicates the Ethernet port where the alarm is generated. For example,0x01 indicates Ethernet port 1.

3 Alarm Processing




Issue 08 (2011-10-30)

Name Meaning

Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. It consistsof 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 havedata packet. As a result, the services may be interrupted.

Possible Causesl Cause 1: The data equipment on the client side stops sending data.

l Cause 2: The data configuration is incorrect.

l Cause 3: The Ethernet port of the board is faulty, which cannot receive data.

Procedure

l Query the alarm on the T2000 and record the IDs of the port and channel where the alarmis generated.

l 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) stopssending data. If yes, start to send data again.

l Cause 2: The data configuration is incorrect.

1. Check whether the receive wavelength on the client side of the board that reports thealarm is consistent with the transmit wavelength at the port of the data equipment. Ifnot, replace the module at the port of the data equipment.

2. Check whether the port where the alarm is generated is configured with logical servicebut does not access any real service. If yes, delete the logical service or suppress thisalarm.


1. Check whether the LINK_ERR alarm is generated at the Ethernet port. If yes,troubleshoot the LINK_ERR alarm.

2. If the alarm persists, check whether there are other alarms on the board that reportsthe alarm. If there are other alarms, troubleshoot these alarms.

3. If the alarm persists, the board may be faulty. Replace the board. For details, seeReplacing a Board of the Supporting Tasks.

----End

Related Information

The alarm is a warning alarm used as an auxiliary warning for fault judgement. Generally, thealarm 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.



3-3

3.1.2 ALM_DATA_TLOS

DescriptionTransmitting data lost on the Ethernet port. The board regularly checks the total number of thetransmitted bytes and compares the number with the number of last time. The alarm is generatedwhen 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



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning



Impact on the SystemThe connection status of the Ethernet port is normal; however, the optical signals do not havedata packet. As a result, the services may be interrupted.

Possible Causesl Cause 1: The WDM side at the local station does not receive data and thus no data is sent

from the client side.l Cause 2: The WDM side at the local station receives data but the client side does not send

data because the board is faulty.

Procedurel Query the alarm on the T2000 and record the IDs of the port and channel where the alarm

is generated.l Cause 1: The WDM side at the local station receives no data and thus no data is sent from

the client side.

3 Alarm Processing




Issue 08 (2011-10-30)

1. Check whether the board at the opposite station reports an ALM_DATA_RLOS alarm.2. 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.l 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 thefaulty board. For details, see the Troubleshooting.

2. If the alarm persists, replace the board that reports the alarm. For details, see Replacinga Board of the Supporting Tasks.

----End

Related Information

None

3.1.3 B1_EXC

Description

Regenerator section (B1) excessive errors. The alarm is generated when the received SDHsignals 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 The alarm is generated on the WDM side when the B1 bit errors in the SDH signals receivedon the WDM side exceed the B1 bit error threshold.

l The alarm is generated on the client side when the B1 bit errors in the SDH signals receivedon the client side exceed the B1 bit error threshold.

Attribute


Minor Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the optical interface where the alarm is generated. For example,0x01 indicates optical interface 1.



3-5

Name Meaning



The B1 bit errors in the service signals received by the board exceed the threshold of the B1 biterrors set for the board. The alarm affects the QoS of the service signals.

Possible Causes

l Cause 1 for the alarm generated on the client side: The input signals on the client sidecontain the bit errors.

l Cause 1 for the alarm generated on the WDM side: The receive side of the local station isfaulty.

l Cause 2 for the alarm generated on the WDM side: The attenuation of the received signalsis excessively high; the fiber or connector is not clean.

l Cause 3 for the alarm generated on the WDM side: The transmit side of the oppositestation is faulty.

Procedure


l Cause 1 for the alarm generated on the client side: The input signals on the client sidecontain 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 themanual of the client equipment.

l Cause 1 for the alarm generated on the WDM side: The receive side of the local station isfaulty.

Clientside

WDMside

Station A

OADM

FIU

Client sideWDM side

OTU2

Station B

OADM

FIU

OTU1Out-loop

Detects and reportsthe B1_EXC alarm

Detects and reportsthe B1_EXC alarm

1. Configure outloop at the transmit and receive optical interfaces on the WDM side ofthe OTU2. If there are no bit error alarms on the OTU1, it indicates that the board atthe local station is faulty. Replace the faulty board. For details, see Replacing a Boardof the Supporting Tasks.

l Cause 2 for the alarm generated on the WDM side: The attenuation of the received signalsis excessively high; the fiber or connector is not clean.

3 Alarm Processing




Issue 08 (2011-10-30)

1. If there are bit errors, check whether the transmit optical power at the correspondingoptical interfaces on the opposite OTU1 on the T2000. For the optical powerspecification of the specific board, see Technical Specifications of the ProductDescription .

2. If the optical power is normal, check the fiber and clean the fiber connector.

l Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite stationis faulty.

1. If the optical power is abnormal, check whether the B1_EXC alarm is generated onthe client side of the opposite OTU1. If yes, eliminate the B1_EXC alarm on theclient side. If not, it indicates that the opposite OTU1 is faulty. Replace the oppositeOTU1. For the optical power specification of the specific board, see TechnicalSpecifications 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 havethe FEC function. As a result, before performing signal FEC in the receive direction of WDMside of the local-end OTU, the local-end OTU counts the bit error rate. This alarm is generatedwhen the counted bit error rate exceeds the threshold.

Reported from the WDM or client side: WDM side.

Attribute


Minor Service alarm

Parameters


Name Meaning




3-7

Name Meaning



The error tolerance of the system decreases, which affects the quality of signals if the decreaseis sufficient.

Possible Causesl 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 excessivelylow, or dispersion or non-linearity occurs.

l Cause 2: The board at the opposite station is faulty.

l Cause 3: The board that reports the alarm is faulty.

Procedure


l Cause 1: The OTU board input optical power is excessively high or low. The systemperformance declines. For example, the optical signal to noise ratio (OSNR) is excessivelylow, 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 Specificationsof the Product Description .

2. If the input optical power is abnormal, see the methods for handling theIN_PWR_HIGH and IN_PWR_LOW.

3. If the optical power is normal, it is possible that the system performance degrades,For the alarm handling, see Troubleshooting Bit Errorsof the Troubleshooting.

l Cause 2 and cause 3: The board at the opposite station may be faulty; the board at the localstation may be faulty.

1. If the alarm persists, the OTU board that reports the alarm may be faulty. Replace theOTU board, For details, see Replacing a Board of the Supporting Tasks.

2. If the alarm persists, the board at the opposite station may be faulty. Replace the faultyboard, For details, see Replacing a Board of the Supporting Tasks.

----End

Related Information

Related Cases:

l MD-A13 Bit Error Alarm Is Generated When Optical Power Gets Close to the Threshold

l MC-A55 Improper DCM Distribution Causes Abnormal Service of the OptiX BWS 1600GEquipment after the Upgrade

3 Alarm Processing




Issue 08 (2011-10-30)

3.1.5 CHAN_LOS

Description

Channel of single wave signal loss alarm. The alarm is generated when the MCA (opticalspectrum analyzing) board detects that the original channel is lost after it scans the opticalspectrum.

Reported from the WDM side or client side: NA.

Attribute


Critical Equipment alarm

Parameters


Name Meaning

Parameter 1 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, theID of the wavelength at which the alarm is reported. For example, 0x000x01 denotes that the alarm is reported in channel (or at wavelength) 1.

Parameters 4 and 5 The value is 0xff of every parameter.

Impact on the Systeml The services of the related wavelength are unavailable.

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

Possible Causesl 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 λ1wavelength is not accessed. The possible cause is that the fiber to the client or WDM sideof the OTU1 is connected.



3-9

OTU1

MCA

FIU

FIUOTU2

OTU3

OTU4

OA

MUX/DMUX

OA

OAOA

MUX/DMUX

Station A Station B

Client side WDM side Client sideWDM side

λ1

λ2

λ1

λ2

l Cause 2: The laser of the board at the opposite station is shut down. For example, the laserof OTU1 in the preceding figure is shut down.

l Cause 3: The attenuation of the multiplexer or OA unit upstream of the MCA is excessivelyhigh.

l Cause 4: The OTU board located before the MCA is faulty. For example, OTU1 in thepreceding figure is faulty.

l Cause 5: The MCA that reports the alarm is faulty.


is generated. Parameter 2 and parameter 3 indicate the number of wavelengths in whichthe alarm is generated.

l 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 thatthe monitoring of the wavelength is disabled.

2. If the wavelength needs to be accessed in the actual network, check the fiberconnection in the upstream stations along the signal flow so that the fiber connectionis established properly.

l Cause 2: The laser of the board at the opposite station is shut down.1. Check whether the laser of the OTU that transmits the wavelength is shut down. If the

laser is shut down, opening the Laser.l Cause 3: The attenuation of the multiplexer or OA unit 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 upstreamOTU board is within the normal range.

2. Query the alarms reported by the MCA input optical power of the optical interface,and then calculate the output optical power of the upstream multiplexer or OA unit todetermine whether it is within the normal range. For the optical power specificationof the specific board, see Technical Specifications of the Product Description . If theoptical power is excessively low or there is no light, check the attenuation that is setfor the input optical power on the multiplexer or OA unit. If the attenuation isexcessively high, decrease the attenuation for the multiplexer or OA unit.

NOTE

Output optical power of the multiplexer or OA unit (dBm) = Input optical power at the IN porton the MCA (dBm) - 10lg("MON"/"OUT") (dBm). "MON"/"OUT" represents the split ratioof the MON port on the multiplexer or OA unit.

l Cause 4: The OTU upstream of the MCA is faulty.

3 Alarm Processing




Issue 08 (2011-10-30)

1. Query the input optical power at the optical interface where the alarm is generated onthe MCA. If the data is abnormal, replace the OTU that transmits the wavelength tothe MCA. For details, see Replacing a Board of the Supporting Tasks.

l Cause 5: The MCA that reports the alarm is faulty.

1. Use an optical spectrum analyzer to analyze the optical spectrum data of thecorresponding optical interface on the MCA. If the data is normal, perform a cold reseton the MCA.

2. If the alarm persists, replace the MCA that reports the alarm. For details, see Replacinga Board of the Supporting Tasks.

----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 packetevents detected by the Ethernet port of the board crosses the upper threshold.

Reported from the WDM or client side: WDM side.

Attribute


Minor Service alarm

Parameters


Name Meaning


Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm isgenerated. For example, 0x00 0x01 indicates channel 1 of the portindicated by parameter 1.



3-11

Impact on the SystemThe Ethernet QoS is degraded.

Possible Causesl Cause 1: The client data equipment is faulty. As a result, the data sent contains a large

number of CRC error packets.l Cause 2: CRC error packets are generated at the receive end because the input optical power

is excessively high or low.l Cause 3: The optical interface modes (and the fiber modes) of the two connected Ethernet

ports are inconsistent.l Cause 4: The fiber is damaged or the fiber connector is dirty.l Cause 5: The board that reports the alarm is faulty.


is generated.l 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 theclient equipment.

l Cause 2 and cause 4: CRC error packets are generated at the receive end because the inputoptical power is excessively high or low. The fiber is damaged or the fiber connector isdirty.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 ofthe Product Description . If the optical power is abnormal, troubleshoot the alarmaccording to the handling procedure for the IN_PWR_HIGH or IN_PWR_LOWalarm.

2. If the optical power is normal, proceed with the next step.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 ofthe board, see Hardware Description. If they are not consistent, replace the fiber orboard to ensure that the optical interface mode and the fiber type of the two Ethernetports are consistent.

l Cause 5: The board that reports the alarm is faulty.1. If the alarm persists, replace the board that reports the alarm. For details, see Replacing

a Board of the Supporting Tasks.

----End

Related InformationNone.

3 Alarm Processing




Issue 08 (2011-10-30)

3.1.7 IN_PWR_HIGH

DescriptionInput optical power is excessively high. The alarm is generated when the input optical power ishigher than the upper threshold of the input optical power.

Reported from the WDM side or client side: WDM side, client side.

Attribute




Name Meaning


Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm isgenerated. For example, 0x00 0x01 indicates channel 1 of the opticalinterface indicated by parameter 1.

Impact on the SystemWhen the input optical power is excessively high, bit errors and LOF alarms may be generatedin the received signals, and the optical module on the board can be damaged. As a result, theservices are affected.

Possible Causesl Cause 1 for the alarm generated on the client side: The input optical power is excessively

high, and the attenuation configured is insufficient.l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The output optical power of the board

in the upstream station is excessively high.l Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is

faulty.l Cause 1 for the alarm generated in multiple wavelengths: The input optical power is

excessively high, and the attenuation configured is insufficient.



3-13

l Cause 2 for the alarm generated in multiple wavelengths: The output optical power of theboard in the upstream station is excessively high.

l Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarmis faulty.


is generated.l 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 withinthe normal range. For the optical power specifications of the specific board, see theProduct Description. If the input power is abnormal as shown on the T2000, use aoptical power meter to measure the input optical power of the board that reports thealarm to check whether the input optical power is within the normal range. If the inputoptical power is abnormal, increase the attenuation to a proper extent so that the inputoptical power is within the normal range.

l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.1. If the input optical power of the board that reports the alarm is normal, the board may

be faulty. In this case, replace the board. For details, see Replacing a Board of theSupporting Tasks.

l Cause 1 for the alarm generated on the WDM side: The output optical power of the boardin 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 withinthe normal range. For the optical power specifications of the specific board, see theProduct Description. If the input optical power is abnormal, query the input and outputoptical power of the boards upstream of the OTU in a reversed sequence of the signalflow on the T2000. Locate the board with very low optical power, and then adjust theinput optical power of the board to a proper value.

l Cause 2 for the alarm generated on the WDM side: The board that reports the alarm isfaulty.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 theSupporting Tasks.

l Cause 1 for the alarm generated in multiple wavelengths: The input optical power isexcessively 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 opticalpower, and then adjust the input optical power of the board to a proper value.

l Cause 2 for the alarm generated in multiple wavelengths: The upstream board outputs veryhigh optical power.1. Test the input and output optical power of the board in the opposite station in the

reversed sequence of signal flow on the T2000.2. If the optical power is excessively high, check the input and output optical power of

the upstream boards in turn to determine whether they are within a normal range. Ifboth the input and output optical power of the upstream boards are abnormal, adjust

3 Alarm Processing




Issue 08 (2011-10-30)

the input optical power to a proper value. For the optical power specifications of thespecific board, see Product Description.

3. If the input optical power of the upstream board is within a normal range, whereas theoutput optical power is abnormal, the upstream board may be faulty. Replace theboard. For details, see Replacing a Board of the Supporting Tasks.

l Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarmis 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. Forthe optical power specifications of the specific board, see Product Description. If theinput 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 InformationThe optical attenuator is marked with attenuation values expressed in dB.

3.1.8 IN_PWR_LOW

DescriptionInput optical power is excessively low. The alarm is generated when the input optical power issmaller than the lower threshold of the input optical power.


Attribute




Name Meaning





3-15


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 Causesl 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.l Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attached

to the optical interface on the board that reports the alarm is excessively high.l Cause 3 for the alarm generated on the client side: The channel use status setting of the

board that reports the alarm is incorrect.l Cause 4 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and the

fiber jumper is over-bent, damaged or aged.l Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuator

attached to the optical interface on the board that reports the alarm is excessively high.l Cause 3 for the alarm generated on the WDM side: The attenuation attached to the transmit

optical interface on the board at the opposite station is excessively high, or the transmitoptical module is faulty.

l Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission ofthe optical signals is excessively high and the compensation is insufficient.

l Cause 5 for the alarm generated on the WDM side: The board that reports the alarm isfaulty.

Procedure


l Cause 1 for the alarm generated on the client side: The fiber connector is dirty, and the fiberjumper 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 opticalpower specifications of the specific board, see the Product Description.

2. If the detected power is excessively low, check the fiber connection. If the fiberconnector is dirty, clean or replace the fiber connector. For details, see theTroubleshooting.

3. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damagedor aged, adjust the fiber jumper or replace the fiber jumper.

l Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attachedto 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 asuitable attenuator.


3 Alarm Processing




Issue 08 (2011-10-30)

l Cause 3 for the alarm generated on the client side: The channel use status setting of theboard that reports the alarm is incorrect.

1. Check whether the channel use status setting on the T2000 is the same as that of theactual channel use status setting of the board. If not, resetting the channel use status.

l Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and thefiber jumper is over-bent, damaged or aged.

1. Use an optical power meter to measure the input optical power of the local board todetermine whether the input optical power is within the normal range. For the opticalpower specifications of the specific board, see the Product Description.

2. If the detected power is excessively low, check the fiber connection. If the fiberconnector is dirty, clean or replace the fiber connector. For details, see theTroubleshooting.

3. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damagedor aged, adjust the fiber jumper or replace the fiber jumper.

l Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuatorattached 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 thereceive 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 asuitable attenuator.

l Cause 3 for the alarm generated on the WDM side: The attenuation attached to the transmitoptical interface on the board at the opposite station is excessively high, or the transmitoptical module is faulty.

1. Check the board at the opposite station. If the laser on the board is shut down, of theattenuation of the attenuator attached to the transmit optical interface on the board isexcessively high, open the laser or decrease the attenuation value of the attenuator toa proper value, or replace the attenuator with a suitable attenuator to ensure that theoutput optical power of the board is within the normal range.

2. If the alarm persists, query the performance value and alarms related to the outputoptical power of the board at the opposite station. If the performance value shown inthe query result does not meet the specification requirement and, for example, the TFalarm is generated, it indicates that the optical module is faulty. Replace the board atthe opposite station. For details, see Replacing a Board of the Supporting Tasks.

l Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission ofthe optical signals is excessively high and the compensation is insufficient. Cause 5 for thealarm 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 thelocal station in the reversed sequence of signal flow on the T2000. Locate the boardwith the very low optical power, and then adjust the input optical power of the boardto a proper value.

2. Check the input and output optical power of the upstream stations one by one in thereversed sequence of signal flow on the T2000 and locate the faulty section where theoptical power is excessively low.

3. If the output optical power of the upstream station is normal, check the cables, fiberjumpers, fiber connectors, and attenuators; if the attenuation of the cables is higherthan the attenuation in the engineering design, adjust the attenuator, rectify or changethe cables; if the fiber jumper, fiber connector or the attenuator is dirty, clean or replacethe fiber jumper, fiber connector or attenuator. For details, see the Troubleshooting;



3-17

4. If the output optical power of the upstream station is abnormal, troubleshoot the faultsat the upstream station so that the output optical power is normal.

5. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.For details, see Replacing a Board of the Supporting Tasks.

l If the alarm is generated in multiple wavelengths, the alarm handling method is similar tothe 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 MC-A19 Use Power Monitoring To Process Problems On Wavelength Division

l MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm

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


Critical Communication alarm

Parameters


Parameter Description



3 Alarm Processing




Issue 08 (2011-10-30)


When the link status of the Ethernet ports is down, a valid link cannot be created between thetwo data ports and the data services are interrupted.

Possible Causesl Cause 1: The service type of the client equipment mismatches the service type of the

interconnected OTU.l Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports

are inconsistent. For example, one port is in the auto-negotiation mode but the other is non-negotiation.

l Cause 3: The input optical power of the two interconnected Ethernet ports is excessivelyhigh or very low.

l Cause 4: The optical interface modes (and the fiber modes) of the two interconnectedEthernet ports are inconsistent.

l Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails.l Cause 6: The data equipment on the client side is faulty.l Cause 7: The board that reports the alarm is faulty.

Procedure


l Cause 1: The service type of the client equipment mismatches the service type of theinterconnected 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 typeof the board or replace the OTU with a proper service type. For details, see Replacinga Board of the Supporting Tasks.

l Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports areinconsistent.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 areinconsistent, modify the setting to ensure the consistency.

l Cause 3: The input optical power of the two interconnected Ethernet ports is excessivelyhigh 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 thespecific board, see the Product Description.

2. If the input optical power is abnormal, see the handling procedures for theIN_PWR_HIGH or IN_PWR_LOW alarms.

l Cause 4: The optical module types of the two interconnected Ethernet boards areinconsistent. Hence, the types of fibers that the two optical modules can be connected toare 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 thetype of the two optical modules match the fiber type.



3-19

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 areproperly connected. If they are not properly connected, reconnect or replace the fiberor cable.

l Cause 6: The data equipment on the client side is faulty.

1. Check whether the data equipment on the client side is faulty. If the equipment isfaulty, troubleshoot the fault of the data equipment on the client side.



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


Name Meaning



3 Alarm Processing




Issue 08 (2011-10-30)


When the link status of the Ethernet ports is down, the available link cannot be created betweenthe two data ports and the data services are interrupted.

Possible Causesl Cause 1: The service type of the client equipment mismatches the service type of the

interconnected OTU.l Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports

are not consistent. For example, The auto-negotiation is enabled for one port but disabledfor the other.

l Cause 3: The input optical power of the two interconnected Ethernet ports is excessivelyhigh or very low.

l Cause 4: The optical interface modes (and the fiber modes) of the two interconnectedEthernet ports are inconsistent.

l Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails.l Cause 6: The data equipment on the client side is faulty.l Cause 7: The board that reports the alarm is faulty.

Procedure


l Cause 1: The service type of the client equipment mismatches the service type of theinterconnected 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 OTUat the local station does not match the type of the services transmitted from the clientdata equipment, first check if the configuration of the service type is correct, thenconsider to replace the board with a board of a proper service type. For details, seeReplacing a Board of the Supporting Tasks.

l Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports arenot 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 areinconsistent, modify the setting to ensure the consistency.

l Cause 3: The input optical power of the two interconnected Ethernet ports is excessivelyhigh 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.

2. If the input optical power is abnormal, see the handling procedures for theIN_PWR_HIGH or IN_PWR_LOW alarms.

l Cause 4: The optical interface modes (and the fiber modes) of the two interconnectedEthernet 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



3-21

ensure that the optical interface mode and the fiber type of the two Ethernet ports areconsistent.

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 areproperly connected. If they are not properly connected, reconnect or replace the fiberor cable.

l Cause 6: The data equipment on the client side is faulty.

1. Check whether the data equipment on the client side is faulty. If the equipment isfaulty, troubleshoot the fault of the data equipment on the client side.



----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 isin the loopback status.


Attribute


Minor Equipment alarm

Parameters


Name Meaning


3 Alarm Processing




Issue 08 (2011-10-30)

Name Meaning

Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm isgenerated. 0x00 0x01 indicates optical interface loopback of the opticalport indicated by parameter 1.

Parameter 4 Indicates the loopback type. For example,l 0x01: Inloop.l 0x02: Outloop.


Services are interrupted.

Possible Causesl Cause 1: The loopback command is issued during testing or maintenance.


Procedure


l Cause 1: The loopback command is issued during testing or maintenance.

1. Check whether the loopback is set on the optical interface during testing ormaintenance. After the test or maintenance is complete, release the loopbackconfigured for the specific optical interface.

l Cause 2: The board is faulty.

1. If the alarm persists, perform a cold reset on the faulty board on the T2000.

2. If the alarm persists, replace the faulty board. For details, see Replacing a Board ofthe Supporting Tasks.

----End

Related Information

None.

3.1.12 LSR_WILL_DIE

Description

Laser will be out of work.




3-23

Attribute



Parameters


Name Meaning




The laser is seriously aged, and thus the quality of the output optical signals and the receivedsignals is decreased (for example, the optical power is lower or not stable). The impact dependson 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. Fordetails, 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 Alarm Processing




Issue 08 (2011-10-30)

3.1.13 MS_AIS

Description

Multiplex section alarm indication. The alarm is generated when the opposite station transmitsthe MS_AIS signals or the receive side of the local station is faulty.

Reported from the WDM or client side: WDM side, client side.

l WDM side: In this case, the type of the service received on the WDM side is SDH.

l client side: In this case, the type of the service accessed on the client side is SDH.

Attribute


Major Communication alarm

Parameters


Name Meaning



Impact on the Systeml If the alarm is reported from the WDM side, the services is interrupted.

l If the alarm is reported from the client side, the services are faulty.

Possible Causesl 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 theMS_AIS signal, as shown in the following figure.



3-25

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theMS_AIS alarm

The client signals containthe MS_AIS signal

WDMside

Clientside

Detects and reports theMS_AIS alarm

l Cause 1 for the alarm generated on the WDM side: The input signals from the clientequipment at the opposite station contain MS_AIS signals, which are transmitted to thedownstream station. At the same time, the MS_AIS alarm is detected on the WDM side ofthe OTU at the local station and it is reported to the T2000. See the preceding figure.



is generated.l Cause 1 for the alarm generated on the client side: In the case of the OTU board of which

the client side supports the SDH services, the input signals from the client side contain theMS_AIS signal, as shown in the following figure.1. When the MS_AIS alarm is reported from the client side, troubleshoot the fault of the

equipment on the client side.l Cause 1 for the alarm generated on the WDM side: The input signals from the client side

of the OTU at the opposite station contain MS_AIS signals.1. Check whether the MS_AIS 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 handlingmethod for the alarm generated on the client side of the OTU.

l Cause 2 for the alarm generated on the WDM side: The board that reports the alarm isfaulty.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 Boardof the Supporting Tasks.

----End


3.1.14 MS_RDI

DescriptionMultiplex section remote defect indication alarm. The alarm is generated at the local station ifthe opposite station back transmits the information through overhead when the WDM-side

3 Alarm Processing




Issue 08 (2011-10-30)

receive part of the opposite station is faulty (for example, the R_LOS, R_LOF, FEC_LOF orMS_AIS alarm is generated).

Reported from the WDM or client side: WDM side, client side

l WDM side: In this case, the type of the service received on the WDM side is SDH.l Client side: In this case, the type of the service accessed on the client side is SDH.

Attribute




Name Meaning



Impact on the Systeml If the alarm is reported from the WDM side, the services may be interrupted.l If the alarm is reported from the client side, the client-side services are faulty.

Possible Causesl 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 boardat the local station A contain the MS_RDI signals. The OTU of the station A reports theMS_RDI alarm on the client side after it detects the MS_RDI signals.



3-27

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theMS_RDI alarm

The client signals containthe MS_RDI signal

WDMside

Clientside

l Cause 1 for the alarm generated on the WDM side: The receive part on the WDM side ofthe opposite station detects the signal failure (for example, the R_LOS, R_LOF, FEC_LOFor the MS_AIS alarm is generated.). As shown in the following figure, the WDM side ofthe OTU board in station B (the opposite station) sends the MS_RDI signals back to stationA (the local station) after it detects and reports the R_LOS, R_LOF, FEC_LOF or theMS_AIS alarm. The WDM side of the OTU board in station A reports the MS_RDI alarmafter it detects the MS_RDI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports the R_LOS,R_LOF, FEC_LOF, MS_AIS alarm

WDMside

Clientside

Sends the MS_RDIsignal back

Detects and reports theMS_RDI alarm


Procedure


l Cause 1 for the alarm generated on the client side: In the case of the OTU board of whichthe client side supports the SDH service, the input signals from the client side contain theMS_RDI signal.

1. When the MS_RDI alarm is reported from the client side, remove the fault of theequipment connected to the client side of the OTU board first.

l Cause 1 for the alarm generate on the WDM side: The receiver on the WDM side of theopposite station detects a signal failure (for example, the R_LOS, R_LOF, FEC_LOF orthe MS_AIS alarm is generated).

3 Alarm Processing




Issue 08 (2011-10-30)

1. Query the alarm of the board in the opposition station by using the T2000. If theR_LOS, R_LOF, FEC_LOF or MS_AIS alarm exists, see the handling procedureof the R_LOS, R_LOF, FEC_LOF or MS_AIS alarm for troubleshooting.

l Cause 2 for the alarm generated on the WDM side: The board that reports the alarm isfaulty.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


3.1.15 MUT_LOS

DescriptionLoss of multiplexed signals alarm. The alarm is generated when the input multiplexed signalsof the board is lost.

Reported from the WDM side or client side: NA

Attribute




Name Meaning



Impact on the SystemThe services that travel through the optical interface that generates this alarm are interrupted.



3-29

Possible Causesl Cause 1: Certain optical interfaces on the board that reports the alarm are not connected to

a fibers or the fibers are damaged.l Cause 2: The attenuation of signals in line transmission is excessively high.l Cause 3: The board that reports the alarm is faulty.


is generated.l 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 signalsto the specific optical interface, or replace the damaged fiber.

l Cause 2: The attenuation of signals in line transmission is excessively high.1. Use an optical power meter to measure the actual receive optical power of the board

that reports the alarm. Check whether the receive optical power is within the normalrange. For the optical power specification of the specific board, see TechnicalSpecifications of the Product Description .

2. If the receive optical power is excessively low, see the handling procedure of theSUM_INPWR_LOW alarm for troubleshooting.

l Cause 3: The board that reports the alarm is faulty.1. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.

For details, see Replacing a Board of the Supporting Tasks.

----End

Related InformationRelated 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 Cross-Connections

l MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS

3.1.16 NEBD_XC_DIF

DescriptionCrossing data of NE and board different. For the board supporting service cross-connection, thealarm is generated when the cross-connection data stored on the SCC is not consistent with thatstored on the board.

3 Alarm Processing




Issue 08 (2011-10-30)

Attribute


Major Process alarm

Parameters


Name Meaning

Parameter 1 The slot ID of the board where the cross-connection data is not consistentwith that on the SCC. For example, 0x01 stands for the slot 1.

Parameter 2 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.


Services are interrupted during service grooming or perform a warm reset on of the board.

Possible Causesl Cause 1: The cross-connection data of the board is incorrect.l Cause 2: The cross-connection data stored on the board is different from that in the SCC

board.

Procedure

l Query the alarm on the T2000. Record the slot ID of the board that reports the alarm.l Cause 1: The cross-connection data of the board is incorrect.

1. Re-configure the cross-connection data on the T2000.For details, see theConfiguration Guide.

l Cause 2: The cross-connection data stored on the board is different from that in the SCCboard.



3-31

1. If the alarm persists, perform a warm reset on the board related to service cross-connections on the T2000.

2. If the alarm persists, perform a warm reset on the SCC board.

----End


3.1.17 OA_LOW_GAIN

DescriptionOptical amplifier signal gain low. The alarm is generated when the actual gain of the opticalamplifier board is lower than the standard gain 3 dB.


Attribute




Name Meaning

Parameter 1 indicates the optical interface where this alarm is generated. Since theoptical amplifiers are different, the value of the parameter varies. Thevalue 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.

Impact on the SystemThe alarm caused by different factors has different influences on the system:

l If the alarm is generated because the input optical power is excessively high, the redundancyof the system decreases, which influences the succeeding capacity expansion.

l If the alarm is caused by other factors (for the OAU board, including the excessive insertionloss caused by the TDC and RDC), the input optical power of the downstream signals and

3 Alarm Processing




Issue 08 (2011-10-30)

the redundancy of the system decrease. The services would have bit errors or even beinterrupted.

Possible Causesl Cause 1: The input optical power of the board is excessively high.l Cause 2: For the OAU board, the alarm might be generated because the insertion loss

between the TDC and RDC optical interfaces is excessively high.l Cause 3: The board that reports the alarm is faulty.

Procedurel 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 onthe T2000. For the optical power specification of the specific board, see TechnicalSpecifications of the Product Description .

2. If the input optical power is not within the normal range, adjust the optical attenuatorattached to the input optical interface so that the input optical power meets thespecification requirement.

3. If no optical attenuator is attached to the input optical interface, add a VOA to ensurethat the input optical power meet the specification requirement.

l Cause 2: The insertion loss between the TDC and RDC optical interfaces is excessivelyhigh. (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 opticalinterfaces.

NOTE

Insertion loss = Optical power at the TDC optical interface - Optical power at the RDC opticalinterface. On the T2000, the difference between the optical power at optical interface 3 and theoptical power at optical interface 5 represents the insertion loss.

2. If the insertion loss is excessive, clean the fiber jumper and fiber connector betweenthe TDC and RDC optical interfaces. For the insertion loss specification, see For theoptical power specification of the specific board, see Technical Specifications of theProduct Description . of the Product Description.

3. If the alarm persists, replace the DCM module between the TDC and RDC opticalinterfaces.

l Cause 3: 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




3-33

3.1.18 ODU_AIS

Description

ODU (optical channel data unit) alarm indication signal. The alarm occurs when the OTU detectsthat all signals are "1" and the STAT information is "111" at the entire ODU layer of the inputsignals. 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


Name Meaning

Parameter 1 Indicates the optical interface where the alarm occurs. For example, 0x01indicates 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 interfaceindicated by parameter 1.


Carried services at this board are interrupted.

Possible Causesl 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 theODU_AIS signal;

as shown in the following figure.

The client-side input signals of the OTU in station A (local station) contains ODU_AISsignals. The OTU in station A reports the ODU_AIS alarm on the client side after detectingthe ODU_AIS signals. At the same time the OTU transparently transmits the ODU_AISsignals to the station B (opposite station).

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theODU_AIS alarm

The client signals containthe ODU_AIS signal

WDMside

Clientside

l Cause 1 for the alarm generated on the WDM side: The ODU_AIS signals are manuallyinserted 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 stationA (opposite station). The WDM side of the OTU in the station B (local station) reports theODU_AIS alarm after detecting the ODU_AIS signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects and reports theODU_AIS alarm

Manually insert theODU_AIS signal

Procedure


l Cause 1 for the alarm generated on the client side: The input signals from the client sidecontain the ODU_AIS signal.

1. 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.

l Cause 1 for the alarm generated on the WDM side: The ODU_AIS signals are manuallyinserted to the OTU at the opposite station.

1. If the alarm persists, on the T2000 query whether the ODU_AIS signals are manuallyinserted to the OTU at the opposite station. If yes, disable the ODU_AIS signalsmanually inserted.

----End



3-35

Related Information

None

3.1.19 OMS_FDI

Description

Forward defect indication at OMS layer. When the OMS_FDI-P and OMS_FDI-O alarmscoexist, this alarm is generated. At the same time, the OMS_FDI-P and OMS_FDI-O alarms aresuppressed. When the board at the OTS layer detects a loss of signal alarm but cannot forwardthe alarm to the downstream station, it inserts the OMS_FDI signal. When the downstreamstation receives the OMS_FDI signal, it reports the OMS_FDI alarm.


Attribute



Parameters


Name Meaning




If the logical fiber connection is established improperly, there is no impact on services. Otherwisethere might be impact on the services.

Possible Causesl Cause 1: The logical fiber connection is not consistent with the physical fiber connection.l Cause 2: In the upstream path, fiber cut occurs, the optical power is excessively low, or

dispersion degrades. Thus, the loss of signal alarm is detected in the downstream path, andthe OMS_FDI is inserted to the downstream path.

3 Alarm Processing




Issue 08 (2011-10-30)


is generated.l Cause 1: The logical fiber connection is not consistent with the physical fiber connection.

1. Check whether the logical fiber connection configured for the optical interface wherethe alarm is generated is consistent with its physical fiber connection. If not, modifythe configuration of the logical fiber connection so that the logical fiber connection isconsistent with the physical fiber connection.

l Cause 2: In the upstream path, fiber cut occurs, the optical power is excessively low, ordispersion degrades. Thus, the loss of signal alarm is detected in the downstream path, andthe 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 accordingto the corresponding alarm handling procedure.

----End


3.1.20 OPS_PS_INDI

DescriptionIndication of optical channel protection switching. The alarm is generated when the opticalchannel protection switching of the services succeeds.

Attribute






3-37

Name Meaning

Parameter 1 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 channeland are not interrupted. You need to locate the cause for protection switching and clear the relatedfault. Otherwise the services might be interrupted.

Possible Causesl Cause 1: The external switching command (such as forced switching or manual switching)

is performed and the switching is successful.

l Cause 2: The services in the working channel are abnormal. The services are automaticallyswitched from the working channel to the protection channel.

Procedure

l Query the alarm on the T2000 and record the type and ID of the protection group wherethe alarm is generated.

l 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 statusis in the forced switching or manual switching status, check whether the externalswitching is the need for normal working.If the external switching is the need fornormal working, there is no need to handle the alarm.

2. If the external switching is not the need for normal working, clear the externalswitching by issuing the clear switching command.

l Cause 2: The services in the working channel are abnormal. The services are automaticallyswitched 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 theswitching state, check whether the alarms with higher priority exist on the related

3 Alarm Processing




Issue 08 (2011-10-30)

boards at the local station such asR_LOS, R_LOF or B1_EXC. If yes, handle thealarms that trigger the protection switching by priority.

2. If the alarm persists, you need to solve the BER-related problem. For the alarmhandling, see Troubleshooting Bit Errorsof the Troubleshooting.

3. If the alarm persists, you need to solve the fiber-related problem. For how totroubleshoot the specific fault, see Troubleshooting Optical Power Anomalies of theTroubleshooting.

----End

Related Information

For the principles of protection and the trigger conditions of the alarm, see the FeatureDescription.

3.1.21 OSC_LOS

Description

Loss of signal on receiving line. This alarm is generated when the receive side receives no signals.


Attribute



Parameters


Name Meaning




There is fiber break in the receive direction and will cause carried service break of this port.



3-39

Possible Causesl Cause 1: A certain optical interface on the board that reports the alarm is not connected to

a fiber.

l Cause 2: The laser of the board at the opposite station is shut down.

l Cause 3: The attenuation of the transmission line is excessively high, and a fiber breakoccurs on the transmission line.

l Cause 4: The transmit side of the opposite station is faulty.

Procedure

l Query the alarm on the T2000 and record the IDs of the optical interface and channel wherethe alarm is generated.

l Cause 1: A certain optical interface on the board that reports the alarm is not connected toa fiber.

1. Check whether the fiber jumper is connected to the optical interface of the board atthe local station. If not, connect the fiber jumper.

l Cause 2: The laser of the board at the opposite station is shut down.

1. Use the T2000 to check whether the laser of the specific board at the opposite stationis open. If not, open the laser of the board.

l Cause 3: The attenuation of the transmission line is excessively high, and a fiber breakoccurs on the transmission line.

1. On the T2000 check whether the receive optical power at the optical interface wherethe alarm is generated is within the normal range. For the optical power specificationof the specific board, see Technical Specifications of the Product Description .

2. If the receive optical power is not within the normal range, troubleshoot the alarmaccording to the handling procedure for the IN_PWR_LOW or IN_PWR_HIGH.

3. If the receive optical power is normal, check the fiber connector. If the fiber connectoris dirty or damaged, clean or replace the fiber connector.

l Cause 4: The transmit side of the opposite station is faulty.


----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 opticalsignals are out of synchronization for more than 3 ms.

Reported from the WDM side or client side: WDM side, client side

3 Alarm Processing




Issue 08 (2011-10-30)

Attribute




Name Meaning

Parameter 1 Indicates the optical interface where the alarm occurs. For example, 0x01indicates 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 interfaceindicated by parameter 1.

Impact on the SystemServices carried on this board are interrupted.


the client side supports the OTN services, the input signals from the client side contain theOTU_LOF signal,as shown in the following figure.The input signals on the client side of the OTU at station A (local station) contain theOTU_LOF signals. The OTU at station A reports the OTU_LOF alarm on the client sideafter detecting the OTU_LOF signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theOTU_LOF alarm

The client signals containthe OTU_LOF signal

WDMside

Clientside

l Cause 2 for the alarm generated on the client side: The received optical power or OSNRof the board is abnormal, or the OTU board at the local station is faulty.



3-41

l Cause 3 for the alarm generated on the client side: In the case of the OTU board of whichthe client side supports the OTN services, the service type set on the client side isinconsistent with the actual service type.

l Cause 1 for the alarm generated on the WDM side: The frame structure of the transmittedsignals of the OTU at the opposite station mismatches frame structure of the OTU at thelocal station, or there is no frame structure in the signals transmitted by the OTU at theopposite station.

l Cause 2 for the alarm generated on the WDM side: The received optical power or OSNRof the board is abnormal, or the OTU board at the local station is faulty.

l Cause 3 for the alarm generated on the WDM side: The OTU board at the opposite stationis faulty.

Procedurel Query the alarm on the T2000 and record the IDs of the optical interface and channel where

the alarm is generated.l Cause 1 for the alarm generated on the client side: The input signals from the client side

contain the OTU_LOF signals.1. 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.l 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 specificboard, see Technical Specifications of the Product Description . If the optical poweris abnormal, troubleshoot the alarm according to the handling procedure for theIN_PWR_HIGH or IN_PWR_LOW alarm.

2. If the OTU_LOF alarm is generated transiently, it may be caused by the burst bit errorsin the transmission line. For the alarm handling, see Troubleshooting TransientService Interruption of the Troubleshooting.


4. If the alarm persists, on the T2000 perform a cold reset on the board that reports thealarm.


l Cause 3 for the alarm generated on the client side: the service type set on the client side isinconsistent 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 thecorresponding optical interface on the board properly. For details, refer to "Queryingand Setting the Service Type on the Client Side on the Board" of the SupportingTasks.

l Cause 1 for the alarm generated on the WDM side: The frame structure of the transmittedsignals of the OTU at the opposite station mismatches the frame structure of the OTU atthe local station, or there is no frame structure in the signals transmitted by the OTU at theopposite 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 Alarm Processing




Issue 08 (2011-10-30)

to receive the signals from the WDM side of the opposite OTU. Then, check the framestructure of the received signals to see whether the frame structure matches the framestructure at the local OTU or whether the signals are framed. If not, replace the OTUat the opposite station.

l Cause 2 for the alarm generated on the WDM side: The received optical power or OSNRof 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 thespecific board, refer to the Product Description.If the optical power is abnormal,troubleshoot the fault according to the handling procedure for the IN_PWR_HIGHor IN_PWR_LOW alarm.

2. If the OTU_LOF alarm is generated transiently, it may be caused by the burst bit errorsin the transmission line. For the alarm handling, see Troubleshooting TransientService Interruption of the Troubleshooting.


4. If the alarm persists, on the T2000 perform a cold reset on the board that reports thealarm.


l Cause 3 for the alarm generated on the WDM side: The OTU board at the opposite stationis faulty.1. If the alarm persists, perform a cold reset on the faulty board at the opposite station.2. 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 InformationRelated Cases: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 Stationl MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with

the SSE1TMRl 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.l MC-A56 LWF Board Reports OTU_LOF Alarml MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After

Correction

3.1.23 OUT_PWR_HIGH

DescriptionOutput optical power too high alarm. This alarm is generated when the laser output optical powercrosses the upper threshold.

Reported from the WDM or client side: WDM side, client side.



3-43

Attribute


Major Equipment alarm


Name Meaning



Impact on the Systeml When the output optical power is excessively high, the input optical power at the receive

end will be very high if no proper optical attenuator is used at the receive end. As a result,the module at the receive end may be damaged.

l If the alarm is caused by the faulty module of the laser or the faulty board, the board isworking abnormally, which will affect the transmitting and receiving of the services.

Possible Causesl The optical module of laser is faulty or the board is faulty.

Procedurel 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 specificpluggable optical module. For details, see Replacing Pluggable Optical Modules ofthe Parts Replacement.

2. If the board does not supports pluggable optical modules, replace the board. Fordetails, see Replacing a Board of the Supporting Tasks.

----End


3 Alarm Processing




Issue 08 (2011-10-30)

3.1.24 PM_BDI

DescriptionODU PM section backward defect indication. The alarm is transferred in the upstream directionof the services, indicating the detected signal failure.


Attribute







Impact on the SystemServices carried on this board are interrupted.

Possible Causesl 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 thePM_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 thePM_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 afterdetecting the PM_BDI signals.



3-45

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports thePM_BDI alarm

The client signals containthe PM_BDI signal

WDMside

Clientside


l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The ODU_AIS/ODU_OCI/ODU_LCK

alarm is generated when the WDM side of the OTU at the opposite station receives thesignals 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 backto station A (local station) after detecting the ODU_AIS/ODU_OCI/ODU_LCK alarm. TheWDM side of the OTU at station A reports the PM_BDI alarm after detecting the PM_BDIsignals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects and reports theODU_AIS, ODU_OCI or

ODU_LCK alarm


Insert the PM_BDIsignal back


l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty. 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 (oppositestation) inserts the PM_BDI signals back to the station A (local station) by mistake. TheWDM side of the OTU in the station A reports the PM_BDI alarm after detecting thePM_BDI signals.

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside


Insert the PM_BDIsignal by mistake

Procedure


l Cause 1 for the alarm generated on the client side: In the case of the OTU of which theclient side supports the OTN services, the input signals on the client side contain thePM_BDI signals.

1. If the client side reports the PM_BDI alarm, check whether the client-side equipmentconnected to the OTU is faulty according to the related manuals. If yes, troubleshootthe fault generated on the client-side equipment by referring to the related manuals.

2. If the alarm persists, perform a cold reset on the faulty board at the local station onthe T2000.

3. If the alarm persists, replace the faulty board.For details, see Replacing a Board of theSupporting Tasks.

l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.


2. If the alarm persists, replace the faulty board.

l Cause 1 for the alarm generated on the WDM side: The ODU_AIS/ODU_OCI/ODU_LCKalarm is generated when the WDM side of the OTU at the opposite station receives thesignals 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 stationreceives the signals at the local station. If yes, handle the alarm by referring to thecorresponding handling procedure.



2. If the alarm persists, the OTU at the local station may be faulty. Replace the faultyboard.

l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty. 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 stationon the T2000.



3-47

2. If the alarm persists, the OTU at the opposite station may be faulty. Replace the faultyboard.

----End


3.1.25 PM_BEI

DescriptionODU PM section backward error indication. If the board detects that the input signals containthe PM-BIP8 bit errors, it inserts the PM_BEI alarm back to the upstream board. The alarmoccurs when the upstream station detects that the BEI flag in the OCH-OH of the PM section ofthe received signals is true.


Attribute







Impact on the SystemThe bit errors occur to the service signals, which influences the system quality.


client side supports the OTN services, the input signals on the client side contain thePM_BEI signals, as shown in the following figure.

3 Alarm Processing




Issue 08 (2011-10-30)

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 thePM_BEI signals and transparently sends the PM_BEI signals to the station B (oppositestation) at the same time. The WDM side of the OTU in the station B reports the PM_BEIalarm after detecting the PM_BEI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports thePM_BEI alarm

The client signals containthe PM_BEI signal

WDMside

Clientside


l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The PM_BIP8 bit errors occur when

the OTU in the opposite station receives the signals in the local station, as shown in thefollowing figure.The WDM side of the OTU in the station B (opposite station) inserts the PM_BEI signalsback to the station A (local station) after detecting the PM-BIP8 bit errors. The WDM sideof the OTU in the station A reports the PM_BEI alarm after detecting the PM_BEI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects the PM-BIP8 biterrors


Insert the PM_BEIsignal back


l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty. 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 (oppositestation) inserts the PM_BEI signals back to the station A (local station) by mistake. TheWDM side of the OTU in the station A reports the PM_BEI alarm after detecting thePM_BEI signals.



3-49

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside


Insert the PM_BEIsignal by mistake

Procedure


l Cause 1 for the alarm generated on the client side: In the case of the OTU of which theclient side supports the OTN services, the input signals on the client side contain thePM_BEI signals.

1. If the client side reports the PM_BEI alarm, check whether the client-side equipmentconnected to the OTU is faulty according to the related manuals. If yes, clear the faultof the client-side equipment by referring to the related manuals.

2. If the alarm persists, perform a cold reset on the faulty board in the local station.



1. If the alarm persists, perform a cold reset on the faulty board in the local station throughthe T2000.

2. If the alarm persists, the OTU in the local station may be faulty. Replace the faultyboard.

l Cause 1 for the alarm generated on the WDM side: The PM_BIP8 bit errors occur whenthe 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 thecorresponding optical interface to check whether the PM_BIP8 bit error occurs whenthe OTU in the upstream station receives the signals at the local station. If yes, handlethe alarm by referring to the handling procedure of the PM_BIP8_OVER alarm.


1. If the alarm persists, perform a cold reset on the faulty board in the local station throughthe T2000.

2. If the alarm persists, the OTU in the local station may be faulty. Replace the faultyboard.

l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty. 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 stationthrough the T2000.

3 Alarm Processing




Issue 08 (2011-10-30)

2. If the alarm persists, the OTU in the opposite station may be faulty. Replace the faultyboard.

----End

Related Information

None.

3.1.26 PM_BIP8_OVER

Description

ODU layer, PM section BIP (Bit Interleaved Parity) exceed the upper threshold. The alarmoccurs when the number of BIP8 bit errors of the PM section in the optical channel data unitlayer crosses the upper threshold.


Attribute


Major Service alarm

Parameters






The bit errors are generated in the service signals of the system, which influences the systemquality.



3-51


client side supports the OTN services, the input signals on the client side has a great amountof BIP8 bit errors of the PM section.


l Cause 1 for the alarm generated on the WDM side: The input optical power is extremelyhigh or extremely low.

l Cause 2 for the alarm generated on the WDM side: The system performance declines. Forexample, the optical signal to noise ratio (OSNR) is extremely low, or dispersion or non-linearity occurs.

l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty.


Procedure


l Cause 1 for the alarm generated on the client side: In the case of the OTU of which theclient side supports the OTN services, the input signals on the client side has a great amountof BIP8 bit errors of the PM section.

1. In the case of the OTU board of which the client side supports the OTN services, querythe current performance of the corresponding optical interface on the T2000 to checkwhether the input signals on the client side has a great amount of BIP8 bit errors ofthe PM section. If yes, clear the fault on the client-side equipment.



l Cause 1 for the alarm generated on the WDM side: The input optical power is extremelyhigh or extremely low.

1. Check whether the input optical power of the interface is within the normal range byusing the T2000, For the optical power specification of the specific board, seeTechnical 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.

l Cause 2 for the alarm generated on the WDM side: The system performance declines. Forexample, the optical signal to noise ratio (OSNR) is extremely low, or dispersion or non-linearity occurs.

1. If the alarm persists, For the alarm handling, see Troubleshooting Bit Errorsof theTroubleshooting.

l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty.

1. If the alarm persists, the board in the opposite station may be faulty. Replace the faultyboard.


3 Alarm Processing




Issue 08 (2011-10-30)

1. If the alarm persists, the board that reports the alarm may be faulty. Replace the board.

----End

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 isoffline.


Attribute



Parameters






Absence of the optical module would lead to the interruption of services borne by thecorresponding optical interface.

Possible Causesl Cause 1: The optical module does not exist or is not correctly inserted in the slot.

l Cause 2: The optical module or the board is faulty.



3-53


is generated.l Cause 1: The optical module does not exist or is not correctly inserted in the slot.

1. Install the optical module properly.l Cause 2: The optical module or the board is faulty.

1. If the alarm persists, If the board uses pluggable optical modules, replace the specificpluggable optical module. For details, see Replacing Pluggable Optical Modules ofthe Parts Replacement.

2. If the optical module is not pluggable, replace the faulty board. For details, seeReplacing a Board of the Supporting Tasks.

----End


3.1.28 POWERALM

DescriptionPower status alarm. That is, the alarm indicates the alarm status of the eight tributary powersupplies on the cabinet. The alarm occurs when a power-off is detected in any one of the tributarypower supplies.

Attribute


Critical Environment alarm


3 Alarm Processing




Issue 08 (2011-10-30)


Parameter 1 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.

Impact on the SystemThe reliability of system power supplying decreases.

Possible Causesl Cause 1: There is a power-off in a tributary power supply or the input power of the

equipment.l Cause 2: The PDU is faulty.l Cause 3: The PMU is faulty.

Procedurel Cause 1: There is a power-off in a tributary power supply or the input power of the

equipment.1. 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.2. 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 tributarypower supplies that correspond to the power supply. (When the power supply isrequired in the future, set the status of the alarm to Not Suppressed.) Otherwise,ensure that the PDU is powered on normally.

3. Check whether the alarm is raised because the tributary power supply switch thatcorresponds to the empty subrack is turned off or not. If yes, suppress thePOWERALM alarm in the unused tributary power supply. (When a subrack is addedin the future, set the status of the alarm to Not Suppressed.)

l Cause 2: The PDU is faulty.1. 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. Replacethe PDU. For details, see Replacing the PDU of the Parts Replacement.

l Cause 3: The PMU is faulty.1. If the alarm persists, replace the faulty PMU. For details, see Replacing the PMU of

the Parts Replacement.

----End



3-55

Related Information

None.

3.1.29 POWER_DIFF_DEFECT

Description

Power difference between optical monitoring active and standby channels. The alarm isgenerated when the power difference between the active and standby optical monitoring signalsexceeds the degraded threshold.


Attribute



Parameters



Parameter 1 The optical power of this optical interface is lower than that of anotheroptical interface and the difference exceeds the threshold.

Parameters 2 and 3 The value is always 0x00 0x01.


None.

Possible Causesl Cause 1: The power difference between the active and standby optical signals transmitted

by the board at the opposite station is rather large.

l Cause 2: The optical power attenuation of the optical signals in transmission is very largeor the optical attenuator that enables very large attenuation is added to the board at theopposite station. As a result, the power difference of the optical signals at the receive endis rather large.


3 Alarm Processing




Issue 08 (2011-10-30)


is generated.l Cause 1: The power difference between the active and standby optical signals transmitted

by the board in the opposite station is rather large.1. 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.l 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 theopposite station.1. Adjust the optical power of the active and standby channels at the receive end until

the alarm clears.l Cause 3: The board that reports the alarm is faulty.


----End


3.1.30 POWER_FAIL

DescriptionPower failure. This alarm is generated if the power supply of a board becomes abnormal. Forexample, there is overvoltage or undervoltage of the power supply, or the battery on the SCChas no charge.


Attribute





3-57

Parameters

Name Meaning

Parameter 1 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.

NOTEFor E8LWF, E8LWFS, E8LBF, E8LBFS, E8ELOG, E8ELOGS, E8ETMX,E8ETMXS, E8TMR, E8TMRS,

l 0x03 denotes 1.2 V.





l 0x08 denotes -5.2 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.

Impact on the Systeml If this alarm is reported by the SCC board, the system time is lost if the system is powered

off.l 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 performedbetween the active power supply and standby power supply but there is no impact on theservices.

l 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 Alarm Processing




Issue 08 (2011-10-30)

Possible Causesl Cause 1: If this alarm is reported by the SCC board, it indicates the battery on the SCC has

no charge.l Cause 2: If this alarm is reported by other boards, it indicates the power supply of the board

is faulty or aged.l 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 isfaulty.

Procedurel 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 powersupply of the board is faulty or aged.1. Replace the faulty board, For details, see Replacing a Board of the Supporting

Tasks.l 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 isfaulty.1. If the alarm is reported by the PMU board, replace the faulty power supply module.

For details, see the Parts Replacement.

----End

Related InformationRelated Cases:l MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER

Alarms

3.1.31 PS

DescriptionPS (protection switching) indication. The alarm occurs when the protection switching of theservices succeeds. When the alarm is generated, the services are working on the protectionchannel.

Attribute






3-59


Parameters 1 Indicates the ID of the protection group in which the alarm is generated.For example, 0x01 indicates protection group 1, 0x02 indicates protectiongroup 2, and 0xff indicates an invalid value.

Parameters 2 and 3 Indicates the optical port where the alarm is generated. It consists of twobytes. For example, 0x00 0x01 indicates optical port 1, 0x00 0x02indicates optical port 2, 0x00 0x03 indicates optical port 3, 0x00 0x04indicates optical port 4, and 0x00 0xff indicates the invalid value.

Parameters 4 This parameter is reserved. It consists of one byte and the value is 0xff.

Parameters 5 This parameter consists of one byte and indicates whether the definitionof an optical port is valid. If the value is 0xA5, the definition of the opticalport 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 protectionchannel and are not interrupted. You need to locate the cause for protection switching and clearthe related fault. Otherwise the services might be interrupted.

Possible Causesl Cause 1: The external switching command (forced switching or manual switching) is

performed and the switching succeeds.l Cause 2: The services in the working channel are abnormal. The services switches from

the working channel to the protection channel.

Procedure


l Cause 1: The external switching command (forced switching or manual switching) isperformed 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 externalswitching is the need for normal working.

2. If the external switching is the need for normal working, there is no need to handlethe alarm.


l Cause 2: The services in the working channel are abnormal. The services switches fromthe 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 localstation have alarms that can trigger a protection switching, such as R_LOS,

3 Alarm Processing




Issue 08 (2011-10-30)

R_LOF or B1_EXC. If yes, handle the alarms that trigger the protection switchingby priority.

2. If the alarm persists, clear the bit errors. For the alarm handling, see TroubleshootingBit Errorsof the Troubleshooting.

3. If the alarm persists, clear the fiber faulty. For how to troubleshoot the specific fault,see Troubleshooting Optical Power Anomalies of the Troubleshooting.

4. If there is no other alarm as confirmed, perform a manual switching to switch theservices from the protection channel to the working channel. After the manualswitching 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 currentcrosses the upper threshold.


Attribute



Parameters




Parameters 2 and 3 Indicate the pump laser where the alarm is generated. For example, 0x000x01 indicates pump laser 1.



3-61


Parameter 4 Indicates the threshold crossing type. For example, 0x01 indicates theupper threshold is exceeded and 0x02 indicates the lower threshold isexceeded.

Impact on the SystemWhen this alarm is reported, the optical components sharply age and the performance of outputsignals degrades.

Possible Causesl Cause 1: The ambient temperature is too high or low.l Cause 2: The pump laser temperature is too high or low.l Cause 3: The board that reports the alarm is faulty.

Procedurel Cause 1: The ambient temperature is too high or low.

1. Check whether the ambient temperature is normal. If the ambient temperature isexcessively high or very low, adjust the temperature to ensure that the temperature iswithin the normal range.

l Cause 2 and cause 3: The pump laser temperature is too high or low; the board that reportsthe alarm is faulty.1. If the alarm persists, replace the faulty board, For details, see Replacing a Board of


----End


3.1.33 R_DATA_LOST

DescriptionClient-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 alarmoccurs when the two numbers are the same, which indicating that the board does not receive anydata.


Attribute



3 Alarm Processing




Issue 08 (2011-10-30)

Parameters






The connection status of the Ethernet port is normal; however, the received optical signals donot have data packet.

Possible Causesl Cause 1: The data equipment on the client side stops to send data.


Procedure

l Query the alarm on the T2000 and record the IDs of the Ethernet port and channel wherethe alarm is generated.

l 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) stopssending data. If yes, clear the fault on the data equipment on the client side (includingtest meters) to make it send data again.


1. Confirm that the connection status of the Ethernet port is normal and no other alarmexists on the board. If other alarms exist, clear other alarms first.

2. If the alarm persists, the board might be faulty. Replace the faulty board in the localstation, For details, see Replacing a Board of the Supporting Tasks.

----End

Related Information

The alarm is a warning alarm used as an auxiliary warning for fault judgement. Generally, thealarm occurs when the test meter or client-side data equipment stops to send data packet. Thepossibility that the alarm is generated due to the faulty board is slim.



3-63

3.1.34 R_LOF

Description

Loss of frame on receiving line. This alarm is generated when the frame alignment processingis out of frame (OOF) in consecutive 3ms.


Attribute



Parameters





Impact on the Systeml The board fails in locating the data frame of the received SDH signals; the client services

fail.

l The board detects this alarm, boards supporting protection switching perform protectionswitching.

Possible Causesl Cause 1 for the alarm generated on the client side: The input signals from the client side

contain the R_LOF signal.

l Cause 2 for the alarm generated on the client side: The service type of the client equipmentmismatches the service type of the interconnected OTU.


l Cause 1 for the alarm generated on the WDM side: The receive optical power or the OSNRof the local board is abnormal.

3 Alarm Processing




Issue 08 (2011-10-30)

l Cause 2 for the alarm generated on the WDM side: The signals transmitted by theupstream OTU have no SDH frame structure.


l Cause 4 for the alarm generated on the WDM side: The input signals from the upstreamstation contain the R_LOS or R_LOF signal.

l Cause 5 for the alarm generated on the WDM side: The dispersion compensation is verylarge or very low.

Procedure


l Cause 1 for the alarm generated on the client side: The input signals from the client sidecontain the R_LOF alarm signal.

1. If the alarm is reported on the client side, apply a hardware loopback between thetransmit and receive optical interfaces on the client side of the board. If this alarm onthe board persists, it indicates that the board is faulty. In this case, see the alarmhandling procedure for cause 3 of this alarm generated on the client side.

CAUTIONConfiguring a loopback on the board interrupts the services on the board.

2. If this alarm is cleared, it indicates that the input signals on the client side contain anR_LOF signal. In this case, rectify the fault on the client equipment.

l Cause 2 for the alarm generated on the client side: The service type of the client equipmentmismatches the service type of the interconnected OTU.

1. Check whether the service type of the OTU at the local station matches the type ofthe services transmitted from the client data equipment. If not, change the service typeof the corresponding port on the board or replace the board with another board thatmatches the service type. For details, see Replacing a Board of the SupportingTasks.

NOTE

Before changing the service type of the port, make sure that the optical cross-connectionsconfigured on the board are in deactivation state.

2. Check whether the alarm is cleared. If the alarm persists, see the alarm handlingprocedure for cause 3 of this alarm generated on the client side.


1. If the alarm persists, the board may be faulty. Replace the faulty board that reports thealarm. For details, see Replacing a Board of the Supporting Tasks.

2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.

l Cause 1 for the alarm generated on the WDM side/cause 2 for the alarm generated on theWDM side: The receive optical power or the OSNR of the local board is abnormal; thesignals transmitted by the upstream OTU have no SDH frame structure.



3-65

1. If the WDM side reports this alarm, use the T2000 to check whether client side of theboard in the opposite station reports R_LOF alarm. If it does, deal the fault with thesolution for client-side R_LOF.

2. If the alarm remains, use the T2000 to check whether the receive optical power of theWDM-side interface of the alarm-reporting board is in normal range. For the opticalpower specification of the specific board, see Technical Specifications of the ProductDescription .

3. If the receive optical power is abnormal, take the alarm as the IN_PWR_LOW orIN_PWR_HIGH alarm for troubleshooting.

4. If the receive optical power is normal, use the SDH meter to receive signals transmittedby the WDM side of the board in opposite station. Check whether the signal is whitespectrum or has no SDH format. If it does not comply with the requirement, replacethe faulty board. For details, see Replacing a Board of the Supporting Tasks.


1. If the alarm persists, the board may be faulty. Replace the faulty board at the localstation. For details, see Replacing a Board of the Supporting Tasks.

l Cause 4 for the alarm generated on the WDM side: The input signals from the upstreamstation contain the R_LOS or R_LOF signal.

1. If the alarm persists, clear the alarm of the equipment on the upstream station.

l Cause 5 for the alarm generated on the WDM side: The dispersion compensation is verylarge or very low.

1. If the alarm persists, replace the DCM module.

2. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.

----End

Related Information

Related Cases:

l MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber LossIs Very Large

l MC-A21 Inconsistent Wavelength Range Causes an Interconnection Failure between theWDM and SDH Equipment

l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarmon the Board

l 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.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute



Parameters






There is fiber break in the receive direction and will cause carried service break of this port.

Possible Causesl Cause 1 for the alarm generated on the client side: The fiber jumper is not connected at the

optical port of the board.

l Cause 2 for the alarm generated on the client side: The line loss is excessively large or thereis a fiber cut.

l Cause 3 for the alarm generated on the client side: The board at the local station receivescolorless light on the client side.

l Cause 4 for the alarm generated on the client side: The board that reports the alarm ismalfunctioning.

l Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected atthe optical port of the board.

l Cause 2 for the alarm generated on the WDM side: The line loss is excessively large orthere is a fiber cut; The optical module sends white light.

l Cause 3 for the alarm generated on the WDM side: The laser of the board at the oppositestation is shut down.

l Cause 4 for the alarm generated on the WDM side: The transmit module of the oppositestation is faulty.



3-67

Procedure


l Cause 1 for the alarm generated on the client side: The fiber jumper is not connected at theoptical port 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.l Cause 2 for the alarm generated on the client side: The line loss is excessively large or there

is a fiber cut.1. Check whether the receive optical power of the interface of the board at the local

station is within the normal range by using the T2000, For the optical powerspecification of the specific board, see Technical Specifications of the ProductDescription .– 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.l 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 arenot colorless light, the board that transmits the signals may be malfunctioning. In thiscase, replace the malfunctioning board.

l Cause 4 for the alarm generated on the client 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.l 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.l 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 powerspecification of the specific board, see Technical Specifications of the ProductDescription .– 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 whetherthe signal is white light. If the result does not comply with the requirement, replacethe faulty board. For details, see Replacing a Board of the Supporting Tasks.

l Cause 3 for the alarm generated on the WDM side: The laser of the board at the oppositestation is shut down.

3 Alarm Processing




Issue 08 (2011-10-30)

1. Use the T2000 the check whether the board laser of the opposite station is open. If notso, open the laser.

l Cause 4 for the alarm generated on the WDM side: The transmit module of the oppositestation 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 MC-A1 The TF Alarm on the OTU at the Upstream Station Results in the OTU_LOF Alarmon the OTU at the Downstream Station

l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.

l MC-A14 The LWF Board Reports R_LOS Because the Incorrect Fiber Type Leads toDispersion Over-Compensation

l MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS When theService Between the Upstream Optical Amplifier Board and the FIU Board Is Interrupted

l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarmon the Board

l MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified by Using AnOptical Power Meter

3.1.36 R_OOF

Description

Out of frame on receiving line. This alarm is generated when the heads of consecutive five framesfail to be detected.


Attribute



Parameters




3-69





There is a fiber break in the receive direction and will cause carried service break of this port.

Possible Causesl Cause 1 for the alarm generated on the client side: The received signals have excessive

attenuation or optical power.l Cause 2 for the alarm generated on the client side: The bit errors in the transmission are

too large.l Cause 3 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 4 for the alarm generated on the client side: The clock configuration of the data

equipment at the two ends is incorrect.l Cause 1 for the alarm generated on the WDM side: The received signals have excessive

attenuation or optical power.l Cause 2 for the alarm generated on the WDM side: The bit errors in the transmission are

too large.l Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station

is faulty.l Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is

faulty.

Procedure


l Cause 1 for the alarm generated on the client side: The received signals have excessiveattenuation 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 powerspecification of the specific board, see Technical Specifications of the ProductDescription .

2. If the receive optical power is not in the normal range, deal it with the solution forIN_PWR_LOW or IN_PWR_HIGH.

l Cause 2 for the alarm generated on the client side: The bit errors in the transmission aretoo 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 Alarm Processing




Issue 08 (2011-10-30)

2. If there is no bit error alarm and the receive optical power is normal, check the fiberconnector. If the fiber connector is dirty or damaged, inspecting and cleaning the fiberconnector.

l Cause 3 for the alarm generated on the client 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.l Cause 4 for the alarm generated on the client side: The clock configuration of the data

equipment at the two ends is incorrect.1. Check whether Clock Configuration of the data equipment at the two ends is set to

Trace the Link Clock. If yes, set the clock configuration of the data equipment atone end to Trace the Internal Clock.

l Cause 1 for the alarm generated on the WDM side: The received signals have excessiveattenuation 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 powerspecification of the specific board, see Technical Specifications of the ProductDescription .

2. If the receive optical power is not in the normal range, deal it with the solution forIN_PWR_LOW or IN_PWR_HIGH.

l Cause 2 for the alarm generated on the WDM side: The bit errors in the transmission aretoo large.1. Check whether there are bit error alarms. If there are bit error alarms, clear the alarms

first according to the proper handling procedure.2. If there is no bit error alarm and the receive optical power is normal, check the fiber

connector. If the fiber connector is dirty or damaged, inspecting and cleaning the fiberconnector.

l Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite stationis 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 thesolution for client-side R_OOF.

l Cause 4 for the alarm generated on the WDM side: The board that reports the alarm isfaulty.1. If the alarm persists, replace the faulty board, For details, see Replacing a Board of


----End

Related InformationRelated Cases:l MC-A16 LOF/OOF Is Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss

Is Very Large



3-71

3.1.37 R_SLIP

DescriptionReceiving side frame slipping. The alarm is generated when the phase deviation occurs to thereceived service frames of the OSC or OTC board.


Attribute







Impact on the SystemThis has impact on services carried by the OSC or the OTC, such as degrading in opticalsupervisory signals or clock signals. This can cause NE disconnection off the NM system.

Possible Causesl Cause 1: The clock configuration is wrong or the clock signals are not synchronous.l Cause 2: The attenuation in the optical line is excessively large, or the receive optical power

is too high.l Cause 3: The fibers at the eastward and the westward interfaces of the OSC or the OTC are

reversely connected.l Cause 4: The board that reports the alarm is faulty.

Procedurel Cause 1: The clock configuration is incorrect or the clock signals are not synchronous.

3 Alarm Processing




Issue 08 (2011-10-30)

1. Check whether the clock configuration is correct, if not, reconfigure it, ensure that theclocks of the total network are synchronous. For details see the ConfigurationGuide.

l Cause 2: The attenuation in the optical line is excessively large, or the receive optical poweris too high.

1. Check whether the receive optical power of the interface is within the normal rangeby using the T2000. For the optical power specification of the specific board, seeTechnical Specifications of the Product Description .

– If the receive optical power is excessively low, check the fiber jumper or the fiberconnector. If the fiber jumper or fiber connector is dirty, replace the fiber jumperor clean the fiber connector.

– If the receive-side optical power is to high, adjust the optical attenuator to makethe receive optical power in the normal range.

l Cause 3: The fibers at the eastward and the westward interfaces of the OSC or the OTC arereversely connected. For example, The fibers at the westward of the TM1 interface and theeastward 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 thefibers at the eastward and the westward interfaces of the OSC or the OTC are reverselyconnected. If the fiber connection is incorrect, correct it according to the figure.

FIU

FIU

OA

OA

SC2RM1

TM1 RM2

TM2


1. If the alarm persists, perform a cold reset on the faulty board through the T2000.


----End

Related Information

Related Cases:

l MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on theOSC Board

3.1.38 REM_SF

Description

Remote signal failure alarm. This alarm is generated when the remote end received signals fail.




3-73

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the optical port where the alarm is generated. For example, 0x01indicates optical port 1.

Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm isgenerated. For example, 0x00 0x01 indicates channel 1 of the optical portindicated by parameter 1.


Services borne by client sides of the board are interrupted.

Possible Causesl Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the

opposite end.

l Cause 2: The client side of the OTU board at the opposite end is faulty.

Procedure

l Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at theopposite end.

1. Check whether there is an R_LOS or R_LOF alarm on the client side of the OTUboard at the opposite station on the T2000. If there is an R_LOS or R_LOF alarm, seeR_LOS or R_LOF to clear the alarm.

l Cause 2: The client side of the OTU board at the opposite end is faulty.

1. Replace the OTU board at the opposite station.For details, see Replacing a Board ofthe Supporting Tasks.

----End

Related Information

None.

3 Alarm Processing




Issue 08 (2011-10-30)

3.1.39 SECU_ALM

DescriptionSecurity alarm. The alarm is generated when the login fails after five consecutive login failureperformed by the same user.


Attribute



ParametersNone.

Impact on the SystemThe alarm automatically ends with no impact on the system.

Possible Causesl Cause 1: This alarm can be caused by illegal login, such as login with a incorrect password

or a user not exist.l Cause 2: The board that reports the alarm is faulty.

Procedurel Cause 1: This alarm can be caused by illegal login, such as login with a incorrect password

or a user not exist.1. Check whether there are users illegally logging in to the NE. If yes, clear the user that

is illegally logged in to.l Cause 2: The board that reports the alarm is faulty.

1. If the alarm persists when there is no user who logged in to the NE illegally, replacethe board. For details, see Replacing a Board of the Supporting Tasks.

----End


3.1.40 SM_BEI

DescriptionOTU layer, SM section backward error indication. If the board detects that the input signalscontain the SM-BIP8 bit errors, it inserts the SM_BEI alarm back to the upstream board. The



3-75

alarm occurs when the upstream station detects that the BEI flag in the OCH-OH of the SMsection of the received signals is true.


Attribute







Impact on the SystemThe bit errors occur to the service signals, which influence the system quality.


the client side supports the OTN services (For example, ETMX, LBF), the input signalsfrom 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 theSM_BEI signals and transparently sends the SM_BEI signals to the station B (oppositestation) at the same time.

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theSM_BEI alarm

The client signals containthe SM_BEI signal

WDMside

Clientside

l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The SM_BIP8 bit errors occur when

the OTU at the opposite station receives the signals of the local station, as shown in thefollowing figure.The WDM side of the OTU in the station B (opposite station) inserts the SM_BEI signalsback to the station A (local station) after detecting the SM-BIP8 bit errors. The WDM sideof the OTU in the station A reports the SM_BEI alarm after detecting the SM_BEI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects the SM-BIP8 biterrors


Insert the SM_BEIsignal back


l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty. It inserts the SM_BEI signals back to the local station improperly. See the followingfigure.The WDM side of the OTU in the station B (opposite station) inserts the SM_BEI signalsback to the station A (local station) by mistake. The WDM side of the OTU in the stationA reports the SM_BEI alarm after detecting the SM_BEI signals.



3-77

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside


Insert the SM_BEIsignal by mistake


is generated.l 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_BEIsignal.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 faultof the client-side equipment by referring to the related manuals.

l Cause 2 for the alarm generated on the client 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,

For details, see Replacing a Board of the Supporting Tasks.l 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 theSM_BIP8_OVER alarm.

2. If the alarm persists, perform a cold reset on the faulty board through the T2000.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.

l 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


3 Alarm Processing




Issue 08 (2011-10-30)

3.1.41 SM_BIP8_OVER

DescriptionOTU layer, SM section bit interleaved parity exceeds threshold. The alarm is generated whenthe number of BIP8 bit errors of the SM section in the optical channel data unit layer exceedsthe threshold.


Attribute


Major Service alarm





Impact on the SystemThe service signals borne by the wavelength generate a great amount of bit errors. The signalsare degraded.


client side supports the OTN services (For example, ETMX, LBF), the input signals fromthe client side contain a great amount of BIP8 bit errors of the SM section.

l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The input optical power is excessively

high or low.l 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 non-linearity occurs.



3-79

l Cause 3 for the alarm generated on the WDM side: The board at opposite station is faulty.l Cause 4 for the alarm generated on the WDM side: The board that reports the alarm is

faulty.


is generated.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 fromthe 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 BIP8bit errors of the PM section. If yes, remove the fault on the client-side equipment.

l Cause 2 for the alarm generated on the client 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, For details, see Replacing a Board of the Supporting Tasks.l 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 specificboard, see Technical Specifications of the Product Description .. If the optical poweris abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm fortroubleshooting.

l Cause 2 for the alarm generated on the WDM side: The system performance declines.1. If the alarm persists, For the alarm handling, see Troubleshooting Bit Errorsof the

Troubleshooting.l 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.l 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


3.1.42 SM_TIM

DescriptionOTU layer, SM Trail Trace Identifier (TTI) is mismatched . The alarm occurs when the receivedTTI value of the SM section is not consistent with the TTI value to receive.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute



Parameters






The specific impact depends on the cause of the alarm.

l If the TTI byte is incorrectly configured, the alarm has no impact on the services and thesystem.

l If the fiber is incorrectly connected, the services are interrupted.

Possible Causesl 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.

l Cause 2: The fiber is incorrectly connected.

Procedure


l Cause 1: The TTI bytes of the SM section to receive by the board in the local station or theopposite 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. Ifnot, set the TTI byte of the SM section to receive or to be transmitted on the T2000to ensure the consistency. For detailed operations, refer to section "Configuring OTUOverheads" in the Configuration Guide.

l Cause 2: The fiber is incorrectly connected.



3-81

1. If the alarm persists, check whether the fiber is correctly connected according to theengineering fiber connection diagram. If not, connect the fiber again according to thefiber connection diagram.

----End

Related Information

The alarm is used for monitoring the SM section of the optical transport network (OTN). Set onthe T2000 the TTI byte of the section monitoring (SM) section to receive, and then compare thevalue with the received TTI byte of the section. The alarm occurs when the two values are notthe consistent.

3.1.43 SUM_INPWR_LOW

Description

Sum input optical power is excessively low. The alarm is generated when the input optical powerof 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 evenare interrupted.

3 Alarm Processing




Issue 08 (2011-10-30)

Possible Causesl Cause 1: The attenuation of the fiber increases, the fiber jumper, fiber connector or the

optical attenuator is dirty.

l Cause 2: The board in the upstream station is faulty, and thus the output optical power isdecreased.


Procedure


l Cause 1: The attenuation of the fiber increases, the fiber jumper, fiber connector or theoptical attenuator is dirty.

1. Check the cables, fiber jumpers, fiber connectors and attenuators.

2. If the attenuation of the cables is larger than that in engineering design, adjust theattenuator, rectify the cables.

3. If the fiber jumper, fiber connector, or fiber attenuator is dirty or damaged, replacethe fiber jumper or check and clean the fiber connector.

l Cause 2: The board in the upstream station is faulty, and thus the output optical power isdecreased.

1. Query the input and output optical power of the upstream boards in the reversedsequence of signal flow by using the T2000 and find out the faulty area where theoptical power is excessively low. Check the output optical power of the upstreamstations. If it is abnormal, the board in the upstream station might be faulty. Replacethe 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 powerof the board is lower than the lower threshold.

Attribute





3-83





Impact on the SystemThe input optical power of the downstream receive board is excessively low, which leads to thatthe services generate the bit errors or even are interrupted.

Possible Causesl Cause 1: The internal attenuation of the board (only for the V40) is excessive.l Cause 2: The fiber is incorrectly connected.l Cause 3: The input optical power of the signals of the board is excessively low.l Cause 4: The board that reports the alarm is faulty.


is generated.l 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 thecorresponding channel to the suitable value on the T2000.

l Cause 2: The fiber is incorrectly connected.1. If the alarm persists, check whether the fiber connection is correct according to the

engineering fiber connection diagram. The input optical signals of differentwavelengths should be accessed from the corresponding input optical interfaces of theboard. If the fiber connection is not correct, correctly connect the fiber according tothe fiber connection diagram.

l Cause 3: The input optical power of the signals of the board is excessively low.1. 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 powerperformance reported by the board at the local station to check the consistency, Forthe optical power specification of the specific board, see Technical Specifications ofthe Product Description .. If they are not consistent, test the input power of the input

3 Alarm Processing




Issue 08 (2011-10-30)

interface of the board and the output power of the board in the opposite station byusing an optical power meter.

– If the input power of the board at the local station but the output power of the boardin the opposite station is within the normal range, check the fiber jumper and fiberconnector. 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 boardin the opposite station reports the related alarms. Check the related alarms on theT2000, and handle the alarms by referring to the corresponding handlingprocedure.


1. 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.

----End

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 alarmis generated when the two numbers are the same, which indicating that the board does nottransmit any data.


Attribute



Parameters






3-85




The connection status of the Ethernet port is normal; however, the transmitted optical signalsdo not have data packet.

Possible Causesl 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.

l Cause 2: The WDM side of the board at the local station can receive data, but the clientside has no data to transmit due to the faulty board.

Procedure


l Cause 1: The WDM side of the board at the local station does not receive any data, whichleads 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. Ifyes, handle the R_DATA_LOST alarm according to the corresponding handlingprocedure.

l Cause 2: The WDM side of the board at the local station can receive data, but the clientside has no data to transmit due to the faulty board.

1. If the alarm persists, the board at the local station might be faulty. Perform a cold reseton the faulty board on the T2000.

2. 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 theR_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 exceedsthe degrade threshold.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute







Impact on the SystemPossibly the board laser cannot work normally, or the output light of the laser is of low qualityor with bit errors and further cause service break.

Possible Causesl Cause 1: The laser is aging.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.

Procedurel Cause 1: The laser is aging.

1. On the T2000, perform a warm reset on the board where the alarm is generated andthen check whether the alarm is cleared.

2. If the alarm persists, check whether the board supports pluggable laser module. If theboard uses pluggable optical modules, replace the specific pluggable optical module.For details, see Replacing Pluggable Optical Modules of the Parts Replacement.

3. If the board is not pluggable, replace the faulty board, For details, see Replacing aBoard of the Supporting Tasks.

l Cause 2: The air conditioner (A/C) does not work for a certain cause and thus thetemperature is high, which causes the TD alarm.1. Start the air conditioner (A/C) and then the alarm is cleared automatically.2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.

----End



3-87

Related InformationIn a cooled optical module that adopts automatic level control (ALC), the laser ages after long-term operation and thus the laser emitting efficiency decreases. To ensure constant output opticalpower, the laser bias current, an index that reflects the laser aging degree, needs to be increased.

3.1.47 TF

DescriptionTransmission failure. The alarm is generated when the launched optical power of the laserexceeds the threshold of the output optical power of the laser.


Attribute





Parameter 1 Indicates the optical interface where the alarm is generated. For example, 0x01indicates optical interface 1.

Impact on the SystemThe laser transmission becomes faulty, which causes service interruption.

Possible CausesCause 1: The laser module is damaged, or the laser is aging.

Procedurel Cause 1: The laser module is damaged, or the laser is aging.

1. On the T2000, perform a warm reset on the board where the alarm is generated andthen check whether the alarm is cleared.

2. If the alarm persists, check whether the board supports pluggable laser module. If theboard uses pluggable optical modules, replace the specific pluggable optical module.For details, see Replacing Pluggable Optical Modules of the Parts Replacement.

3 Alarm Processing




Issue 08 (2011-10-30)

3. If the board does not support pluggable laser module, replace the faulty board. Fordetails, see Replacing a Board of the Supporting Tasks.

----End

Related Information

In a cooled optical module that adopts automatic level control (ALC), the laser ages after long-term operation and thus the laser emitting efficiency decreases. To ensure constant output opticalpower, the laser bias current needs to be increased. Hence, the bias current is an index that reflectsthe aging degree of the laser.

Related Cases:

l MC-A12 Certain Boards Report the TF Alarm Transiently Because the Fan Speed Is Lowand 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 arenot consistent.


Attribute



Parameters



Parameter 1 Indicates the slot where the installed board is mismatched with the configuredboard. For example, 0x01 indicates that the physical board installed in slot 1 isnot the same as the configured logical board.


The type of the logical board is inconsistent with the type of the physical board. The board cannotwork normally.



3-89

Possible Causesl 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.l Cause 2: The board software is incorrect.l Cause 3: The board that reports the alarm is faulty.

Procedurel 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 logicalboard 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. If the alarm persists when the type of the logical board is consistent with the type ofthe physical board, check whether the board software matches the hardware.

l Cause 3: The board that reports the alarm is faulty.1. 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


3.2 Alarm ProcessingThis 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 engineersfor troubleshooting.

The alarm handling involves board reset, either of software or hardware. Software reset andhardware 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 hardwarereset of the SCC might result in reconfiguration of the key hardware, such as FPGAreloading; the upper-layer software need be restarted.

l Reset of other boards: a reset of software on other boards does not affect running serviceswhile a reset of hardware on other boards does. A mis-reset of such a board affects thecommunication between this board and the SCC and even interrupts services.

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.1 AD_CHECK_FAIL

Description

AD (analog to digital converter) self check failure alarm. This alarm is generated when the ADchip on the board is faulty.


Attribute



Parameters



Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicateschip 1.

Parameters 2 and 3 The value is always 0x00 0x01. There is no concept of channels.

Impact on the Systeml This alarm might affect services.

l Parameters relevant to the AD chip on the board, such as board input/output optical power,back facet current and cooling current, fail to be queried on the T2000. As a result,maintenance engineers can neither obtain the current operation performance data of thenetwork nor find in time any dormant problems of the network operation. The alarm mightinterrupt 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-91

Related Information

None

3.2.2 ALM_PIUA_OFFLINE

Description

The power interface unit A (PIUA) offline alarm. This alarm is generated when the systemdetects that PIUA in the subrack is offline.

Attribute



Parameters



Parameter 1 There is no concept of optical interfaces, it is always 0x01.



The subrack lacks one backup input power supply (PIUA), which affects the reliability of thesubrack power supplies.

Possible Causesl The power interface unit A is offline.l 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. Replacethe faulty PIUA. For details, see the Parts Replacement.

----End

3 Alarm Processing




Issue 08 (2011-10-30)

Related InformationNone

3.2.3 ALM_PIUB_OFFLINE

DescriptionThe power interface unit B (PIUB) offline alarm. This alarm is generated when the system detectsthat PIUB in the subrack is offline.


Attribute





Parameter 1 There is no concept of optical interfaces, it is always 0x01.


Impact on the SystemThe subrack lacks one backup input power supply (PIUB), which affects the reliability of thesubrack power supplies.

Possible Causesl The power interface unit B is offline.l 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. Replacethe faulty PIUA. For details, see the Parts Replacement.

----End



3-93


3.2.4 AU_AIS

DescriptionAU alarm indication signal. The alarm is generated when the AU (including pointers) of theSDH frame are all "1" signals. The client side sends the AU_AIS signals to the WDM side afterthe higher order path signal failure of the receive end on the client side.

Reported from the WDM side or client side: WDM side.

Attribute





Parameter 1 The path number of the VC4 in SDH frames. The different SDH framehas a different value range. For example, The value range of the STM-Nframe is from 0x01 to 0x0n.


Impact on the SystemServices are interrupted.

Possible Causesl As shown in the following figure, the client side of the opposite station sends AU_AIS.

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theAU_AIS alarm

The client side sendsAU_AIS signal

WDMside

Clientside

l 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.

Station B

OTU

OTU

WDMside

Station A

Detects and reports theAU_AIS alarm

WDMside

Clientside

Outloop on the client side/Inloop on the WDM side

l The receive optical module of the board at the local station or the transmit part of the client-side equipment is faulty.

Procedure

Step 1 Check whether client-side outloop or the WDM-side inloop occurs to the board in the oppositestation. 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_AISsignal. 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 clientside of the opposite station is normal. If the power is abnormal, remove the fault of the equipmenton the client side.

Step 4 If the alarm persists, check whether the input optical power of the WDM side of the board at thelocal station is within the normal range by using the T2000. For the optical power specificationsof the specific board, see the Product Description. If the optical power is abnormal, add properattenuation by adding a fixed attenuator or VOA.

Step 5 If the alarm persists and the faulty board supports the pluggable optical module, replace thepluggable 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-95

Related InformationIf 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, thereis no need to handle the alarm.

3.2.5 AU_LOP

DescriptionAU loss of pointer. The alarm is generated when the AU_PTR values in consecutive eight framesare invalid (the value is out of the range from 0 to 782).


Attribute





Parameter 1 The path number of the VC4 in SDH frames. The different SDH framehas a different value range. For example, The value range of the STM-Nframe is from 0x01 to 0x0n.



Possible Causesl As shown in the following figure, the client side of the opposite station sends AU_LOP.

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theAU_LOP alarm

The client side sendsAU_LOP signal

WDMside

Clientside

l The service timeslots configured at the local station and in the opposite station are notconsistent.

l The board hardware is faulty.

Procedure

Step 1 Check whether the opposite station have the AU_LOP alarm or not.

l If yes, the board in the opposite station is faulty. Replace the faulty board in the oppositestation.

l If not, check whether the service configuration at the local station and in the opposite stationare 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 PartsReplacement.

----End

Related Information

None

3.2.6 B1_SD

Description

Regenerator section (B1) excessive errors. The alarm is generated when the received signals inSDH frame degrades and the B1 bit errors in the multiplex section exceeds the signal degrade(SD) threshold.


l The alarm is generated on the WDM side when the B1 bit errors in the SDH signals receivedon the WDM side exceed the signal degrade (SD) threshold.

l The alarm is generated on the client side when the B1 bit errors in the SDH signals receivedon the client side exceed the signal degrade (SD) threshold.



3-97

Attribute


Minor Service alarm

Parameters






The B1 bit errors in the service signals received by the board exceeds the degrade threshold ofsignals set on the board. The generation of the alarm has an influence on the QoS of the servicesignals.

Possible Causesl The attenuation of the received signals is overlarge; the fiber or connector is dirty.l The transmit part of the opposite station is faulty.l The receive part of the local station is faulty.

Procedure

Step 1 Check whether the receive optical power of the interface is within the normal range by usingthe T2000. For the optical power specifications of the specific board, see the ProductDescription. If the receive optical power of the board at the local station is excessively low, clearthe 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 interfaceon the upstream board is within the normal range by using the T2000. For the optical powerspecifications of the specific board, see the Product Description. If the launched optical powerof the board in the upstream station is excessively low, clear the alarm according to the handlingprocedure of the OUT_PWR_LOW alarm.

Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using theT2000 and loop back the transmit optical interface and receive optical interface on the WDM

3 Alarm Processing




Issue 08 (2011-10-30)

side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault ofthe upstream station.

Step 4 If the alarm persists and the faulty board supports the pluggable optical module, replace thepluggable optical module. 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 noisesources. 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 inthe multiplex section exceeds the threshold.


l The alarm is generated on the WDM side when the B2 bit errors in the SDH signals receivedon the WDM side exceed the B2 bit error threshold.

l The alarm is generated on the client side when the B2 bit errors in the SDH signals receivedon the client side exceed the B2 bit error threshold.

Attribute


Major Service alarm

Parameters






3-99




The B2 bit errors in the service signals received by the board exceeds the threshold of the B2bit errors set on the board. The generation of the alarm has an influence on the QoS of the servicesignals.

Possible Causesl The attenuation of the received signals is overlarge; the fiber or connector is dirty.

l The transmit part of the opposite station is faulty.

l The receive part of the local station is faulty.

Procedure



Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using theT2000 and loop back the transmit optical interface and receive optical interface on the WDMside of the OTU board on the upstream station. If the bit error exists, clear the bit error fault ofthe upstream station.




----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.8 B2_SD

Description

Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors inthe multiplex section exceeds the signal degrade (SD) threshold.


l The alarm is generated on the WDM side when the B2 bit errors in the SDH signals receivedon the WDM side exceed the signal degrade (SD) threshold.

l The alarm is generated on the client side when the B2 bit errors in the SDH signals receivedon the client side exceed the signal degrade (SD) threshold.

Attribute


Minor Service alarm

Parameters






The B2 bit errors in the service signals received by the board exceeds the degrade threshold ofsignals set on the board. The generation of the alarm has an influence on the QoS of the servicesignals.

Possible Causesl The attenuation of the received signals is overlarge; the fiber or connector is dirty.

l The transmit part of the opposite station is faulty.

l The receive part of the local station is faulty.



3-101

Procedure



Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using theT2000 and loop back the transmit optical interface and receive optical interface on the WDMside of the OTU board on the upstream station. If the bit error exists, clear the bit error fault ofthe upstream station.




----End


3.2.9 BD_STATUS

DescriptionBoard out of position alarm. The alarm is generated when the physical board is not inserted inthe slot.

Attribute



ParametersNone

Impact on the SystemThe board is not in service. Hence, the functions related to the board are unavailable.

3 Alarm Processing




Issue 08 (2011-10-30)

Possible Causesl 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 switchon the PMU is improperly set.

l In the case of the ROP board of the OptiX BWS 1600G, it is possible that communicationbetween the board and the subrack fails.

l The logic board is configured but the physical board has not been inserted in the properslot.

l The connection between the plug of the board and the socket of the mother board is loose.l The board is faulty.

Procedure

Step 1 If the PMU board in the power supply box reports the alarm, check whether the serial cable andalarm 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 dipswitch, see the Hardware Description. If the dip switch is set improperly, re-set the dip switchproperly (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 ROPboard 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 If no corresponding board is inserted, insert the board.l If the corresponding board is inserted, check whether the insertion is firm. If not, reset the

board.


----End


3.2.10 BD_VER_NMAT

DescriptionThe 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 versionmapping table.


Attribute


Major Process alarm



3-103



Parameter 1 Indicates the slot where the alarm is generated. For example, 0x01 denotes slot1.

Parameter 2 Indicates a board software type that does not comply with the version mappingtable, For example,

l 0x01 denotes that the extended BIOS version does not comply with theversion mapping table.

l 0x02 denotes that the board software version does not comply with the versionmapping table.

l 0x03 denotes that the FPGA version does not comply with the versionmapping table.

l 0x04 denotes that the BIOS version does not comply with the version mappingtable.

Parameter 3 Indicates a reserved parameter whose value is always 0xff.



Impact on the SystemMismatch of any board software version with the NE software version in the version mappingtable fails some intended functions.

Possible Causesl The board software version does not comply with the version mapping table.l The board FPGA version does not comply with the version mapping table.l The extended BIOS version does not comply with the version mapping table.l 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 boardsoftware 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 boardFPGA according to the Version Upgrade Guide and version mapping table.

3 Alarm Processing




Issue 08 (2011-10-30)

Step 3 If the extended BIOS version does not comply with the version mapping table, update theextended 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. Fordetails, 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-endOTU have the FEC function. As a result, before performing signal FEC in the receive directionof WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm isgenerated when the counted bit error rate exceeds the threshold.

Reported from the WDM side or client side: WDM side

Attribute


Minor Service alarm

Parameters


Name Meaning




The system redundancy decreases, which affects the quality of signals if the decrease is serious.



3-105

Possible Causesl The board input optical power is excessively high or low.l The system performance declines. For example, the optical signal to noise ratio (OSNR)

is excessively low, or dispersion or non-linearity occurs.l The opposite-end board is faulty.l The local-end board is faulty.

ProcedureStep 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 inputoptical power is abnormal, see the methods for handling the IN_PWR_HIGH andIN_PWR_LOW alarms.

Step 2 If the alarm persists, the performance of the system may be degraded, for example, the opticalsignal 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. Fordetails, 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


3.2.12 BOOTROM_BAD

DescriptionBOOTROM data check failed alarm. This alarm is generated when the basic or extended BIOSsoftware of the board is damaged.


Attribute




3 Alarm Processing




Issue 08 (2011-10-30)


Parameter 1 The value is always 0x03.

Parameters 2 and 3 Indicates the BIOS type. For example, 0x01 indicates the basic BIOSsoftware. 0x02 indicates the extended BIOS software.

Parameter 4 The value is always 0x01.

Impact on the SystemWhen repowered on or reset after a power supply failure, the SCC board cannot be normallystarted.

Possible Causesl The extended BIOS software of the board is damaged.l The basic BIOS software of the board is damaged.l The SCC board is faulty.

Procedure

Step 1 Determine upon the alarm parameter (0x01 denotes the basic BIOS while 0x02 the extendedBIOS) 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 PartsReplacement.

Step 3 If the extended BIOS software is damaged, reload the extended BIOS of the SCC board. Fordetails, see the Version Upgrade Guide.

Step 4 If the alarm persists, the SCC board might be faulty. Replace the faulty board. For details, seethe Parts Replacement.

----End


3.2.13 CFG_VERIFY

DescriptionConfiguration is not verified.

Attribute


Major Security alarm



3-107


None

Impact on the SystemThe configuration data is not taken into effect.

Possible CausesThe alarm is generated when the verification is not performed 15 minutes after the lastconfiguration command is issued.

Procedure

Step 1 Download the configuration data on the T2000 to issue the configuration information again andverify it.

----End


3.2.14 CFGBD_FAIL

DescriptionBoard configuration is mismatched. The alarm is generated when the configuration issued andthe protection type are not consistent in the case of that the protection type of the single fed andsingle receiving board is configured to intra-board channel protection.


Attribute



ParametersNone

Impact on the SystemThe intra-board protection configured cannot realize the protection function.

3 Alarm Processing




Issue 08 (2011-10-30)

Possible Causes

The configuration is error. The protection type of the single fed and single receiving board isconfigured to intra-board channel protection.

Procedure

Step 1 The single fed and single receiving board does not support intra-board protection. Delete theprotection attribute of the board on the T2000 after confirming that the board configured is thesingle fed and single receiving board.

Step 2 Replace the board with a dual fed selective receiving board. For details, see the PartsReplacement.

----End

Related Information

None

3.2.15 CFGDATA_OUTRANGE

DescriptionBoard configuration data out of range alarm.

Attribute



Parameters


Parameter 1 Indicates the type of the configured data that exceeds the threshold or doesnot 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 exceedsthe threshold.



3-109




Impact on the SystemAs for the cross-connect capacity, this alarm results in the logical cross-connect capacityconfigured 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 theconfigured mapping trail of the service and the mapping trail mode that is actually supported bythe board. As a result, services at the optical layer are not available.

Possible Causesl As for the operating wavelength of the OTU, the configured logic wavelength differs with

the actual wavelength or falls beyond the tuning range.l 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 dataon the board.

l In the case of the type of the services to be transmitted, if the board does not support theconfigured service type, the configuration data on the SCC is inconsistent with the data onthe board.

l As for the cross-connect capacity, the cross-connect capacity configured exceeds the cross-connect capacity supported by the equipment.

l In the case of the mapping trail mode, if the configured mapping trail of the service is notsupported by the board, configuration data is inconsistent between the SCC and the board.

Procedure

Step 1 View on the T2000 the parameters of the alarm and confirm the configuration data type and theIDs of the slot, optical interface and channel that correspond to the configuration data threshold-crossing 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 thesame as the fixed wavelength of the optical module on the board; or replace the board oroptical module with another one whose wavelength is the same as that stored in the NEsoftware.

l In the case of the working mode of the optical interface, check whether the configuredworking mode is the same as the actual mode of the board by using the T2000. If theconfigured working mode is not the same as the actual mode, re-configure the workingmode of the optical interface.

3 Alarm Processing




Issue 08 (2011-10-30)

l In the case of the type of the services to be transmitted, check whether the service type isthe same as the actual type of the services accessed by the board by using the T2000. If theconfigured service type is not the same as the actual service type, re-configure the servicetype.

l As for the cross-connect capacity, check whether the logical cross-connect capacityconfigured for the subrack exceeds the capacity supported by the equipment. If yes, re-configure the cross-connect.

l In the case of the mapping trail mode for the service, check whether the mapping trail isthe same as the mode that is actually supported by the board. If the configured mode is notsupported by the board, re-configure a valid the mode of the board.

----End


3.2.16 CHAN_ADD

DescriptionChannel of single wave signal add. The alarm is generated when the MCA (optical spectrumanalyzing) board detects that new channels are added after it scans the optical spectrum.


Attribute





Parameter 1 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.



3-111


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

Possible Causesl The configuration for wavelength monitoring is incorrect. The accessed wavelength is not

set to be the monitored wavelength.

l The MCA board is faulty.

Procedure

Step 1 Check whether the configuration for wavelength monitoring of the MCA board is incorrect byusing the T2000. If the configuration is incorrect, modify the configuration to ensure that themonitored wavelength and the number of the monitored wavelengths are consistent with theaccessed 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 opticalspectrum 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 thecorresponding optical interface of the board at the local station is not consistent with that in theopposite station.


Attribute



Parameters


3 Alarm Processing




Issue 08 (2011-10-30)


Parameter 1 Indicates the optical port where the alarm is generated. For example, 0x03indicates optical port 3.


Impact on the SystemThe services borne by the optical interface on the client side would be interrupted.

Possible Causesl The service type of the corresponding optical interface of the board at the local station is

not consistent with the opposite station.l 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 localstation is consistent with that in the opposite station by using the T2000. If not, configure theservice type again.

Step 2 If the alarm persists, check whether the cross-connection of corresponding optical interface ofthe board at the local station is configured correctly; if it is not consistent with the engineeringdesign, configure it again.

Step 3 If the alarm persists, maybe the board at the local station is faulty. Replace the faulty board. Fordetails, see the Parts Replacement.

----End


3.2.18 COMMUN_FAIL

DescriptionInternal communication failure on the board.


Attribute





3-113




Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. Forexample,

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.

Impact on the SystemThe board that reports the alarm cannot be reconfigured or cannot actuate external commands.

Possible CausesThe board is faulty.

Procedure


----End


3.2.19 DBMS_ERROR

DescriptionDatabase error alarm. The alarm is generated when the database is in error.

3 Alarm Processing




Issue 08 (2011-10-30)

Attribute


Major Process alarm



Parameter 1 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.

Impact on the SystemThe configured data cannot be saved successfully. As a result, the data is lost.

Possible Causesl Operation to database fails.l Data in the database is damaged.l The board is faulty.

ProcedureStep 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.


----End



3-115

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 protectionmode.


Attribute


Critical Process alarm

Parameters

None


In the protection mode, the NE database cannot be backed up.

Possible Causesl The reset times of the SCC in five minutes exceeds the threshold value of the protection

mode.

l The SCC issues a command to test the protection mode.

Procedure

Step 1 Check whether the NE database entering in the protection mode is caused by human factor. Ifthat is the case,

l Perform a warm or cold reset on the SCC through the T2000. Release the protection mode.For details, see the Troubleshooting.

l Wait for 15 minutes. Release the protection mode after automatic reset.


----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.21 DCM_INSUFF

DescriptionInsufficient dispersion compensation margin. The alarm is generated when the dispersioncompensation value gets close to the limits of the dispersion compensation margin.

Attribute







Parameter 4 Indicates the dispersion compensation margin. The board is ps/nm.

Parameter 5 Indicates positive or negative dispersion compensation margin. The value0x00 indicates positive dispersion compensation margin, and the value0x01 indicates negative dispersion compensation margin.

Impact on the SystemThe alarm does not affect the existing services. The alarm indicates that the system cannot meetthe higher dispersion compensation requirements.

Possible CausesThe 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, clearthe alarms according to the proper procedure.



3-117

Step 2 If there are no other alarms, query the dispersion compensation value of the board on theT2000.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 dispersioncompensation capabilities.

l If the dispersion compensation value is small and close to the lower limit of the dispersioncompensation margin, replace the DCM module with a DCM module with higher dispersioncompensation capabilities.

----End


3.2.22 DSP_LOAD_FAIL

DescriptionDSP software loading failure. The alarm is generated when loading the DSP programme fails.


Attribute


Major Process alarm




Impact on the SystemLoading the DSP program to the board fails. As a result, the board cannot work normally, whichhas an influence on the services of users.

Possible CausesThe board hardware is faulty.

3 Alarm Processing




Issue 08 (2011-10-30)

Procedure

Step 1 Perform a warm reset on the faulty board through the T2000. For details, see theTroubleshooting.


----End

Related Information

None

3.2.23 EDFA_TEMP_OVER

Description

EDFA temperature exceeds the threshold. The alarm is generated when the actual temperatureof the EDFA box exceeds the normal working temperature range by more than 5°C.

Attribute



Parameters



Parameter 1 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 theupper threshold is exceeded and 0x02 indicates the lower threshold isexceeded.


The output optical power of the board decreases, the gain flatness is degraded and the systemredundancy decreases. In a serious situation, the services have bit errors or even are interrupted.

Possible Causes




3-119

Procedure


----End

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 damagesthe boards.

Possible Causesl The speed level of fan is stop.

l 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




Issue 08 (2011-10-30)

3.2.25 FEC_LOF

DescriptionReceived FEC is loss of frame. The alarm is generated when the FEC frame is lost.


Attribute





Parameter 1 Indicates the port on the WDM side where the alarm is generated. Thevalue is always 0x01.


Impact on the SystemThe generation of the alarm affects the receiving of the services.

Possible Causesl The received signals have excessive attenuation.l The signals transmitted by the WDM side of the opposite station do not have FEC frame

structure.l The board in the opposite station is faulty.l 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 withinthe 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 theIN_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 theopposite station reports the alarm, remove the fault in the opposite station.



3-121

1. Check whether the board is forced to emit light. If yes, release the setting.2. 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 PartsReplacement.

Step 3 If the opposite station does not report the alarm, the board at the local station is faulty. Replacethe faulty board. For details, see the Parts Replacement.

----End


3.2.26 FEC_OOF

DescriptionReceived FEC is out of frame.


Attribute





Parameter 1 Indicates the port on the WDM side where the alarm is generated. Thevalue is always 0x01.


Impact on the SystemThe generation of the alarm affects the receiving of the services.

Possible Causesl The received signals have excessive attenuation.l The local station has the WDM-side inloop.

3 Alarm Processing




Issue 08 (2011-10-30)

l The board in the opposite station is faulty.

l 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 withinthe 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 theIN_PWR_LOW alarm for troubleshooting.

Step 2 Perform the hardware self-loop on the WDM side of the board in the opposite station. If theopposite station reports the alarm, remove the fault in the opposite station.

1. Check whether the board is forced to emit light. If yes, release the setting.

2. 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 PartsReplacement.

Step 3 If the opposite station does not report the alarm, the board at the local station is faulty. Replacethe 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 fibermonitored by the OTDR is excessive and thus crosses the critical alarm threshold.

Reporting to the WDM or client side: NA

Attribute



Parameters




3-123


Parameter 1 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 interfaceindicated 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 Causesl The monitored fiber section is damaged.

l The monitored fiber section is cut.

l The board is faulty.

Procedure

Step 1 Compare the optical power of the board at the downstream station that the monitored fiberconnects to with the history data. If the optical power decreases, a fault that the alarm indicatesoccurs in the fiber; proceed with step 2. If the optical power does not decrease, proceed withstep 3.

Step 2 Locate the fiber fault upon the fiber fault location displayed on OAMS. Eliminate influence offactors such as temperature, external force, and aging (if the fiber is permanently damagedphysically, splice it; if the fiber is seriously aged, replace it) to ensure that the optical power ofthe board at the downstream station to which the monitored fiber connects is restored to thehistory normal value.

Step 3 Retest the monitored fiber with the "roll call test" method in "by reference curve" mode (afterthe fiber fault is cleared, the monitored fiber must be retested in "by reference curve" mode toclear 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 theParts Replacement.

----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.28 FIBER_MAJOR

Description

The OTDR-tested fiber major alarm. This alarm is generated in the tested fiber when any of thefollowing conditions is met:

l The difference between the fiber channel omnidistance transmission loss tested by theOTDR and that measured in the final acceptance test (or the raw data value) is a minimumof the omnidistance transmission loss threshold of the fiber major alarm.

l The loss in a newly added event crosses the loss threshold in a newly added event of fibermajor alarm.

l The loss increase in an existing event crosses the loss threshold in an existing event of fibermajor alarm.


Attribute



Parameters







Multiplexed signals in the main optical path might be interrupted.




3-125


Procedure

Step 1 Determine whether the fault that the alarm indicates exists according to the optical power changeof the board at the downstream station to which the monitored fiber is connected. Compare theoptical power with the history data. If the optical power decreases, the fiber is faulty; proceedwith 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 offactors such as temperature, external force, and aging to ensure that the optical power of theboard at the downstream station to which the monitored fiber connects is restored to the historynormal value.


Step 4 If the alarm persists, the alarm might be misreported. Perform a perform a warm reset on on theboard.



----End


3.2.29 FIBER_MINOR

DescriptionThe OTDR-tested fiber minor alarm. This alarm is generated in the tested fiber when any of thefollowing conditions is met:

l The difference between the fiber channel omnidistance transmission loss tested by theOTDR and that measured in the final acceptance test (or the raw data value) is a minimumof the omnidistance transmission loss threshold of the fiber minor alarm.

l The loss in a newly added event crosses the loss threshold in a newly added event of fiberminor alarm.

l The loss increase in an existing event crosses the loss threshold in an existing event of fiberminor alarm.


3 Alarm Processing




Issue 08 (2011-10-30)

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 interfaceindicated by parameter 1.



Multiplexed signals in the main optical path might degrade.



Procedure

Step 1 Determine whether the fault that the alarm indicates exists according to the optical power changeof the board at the downstream station to which the monitored fiber is connected. Compare theoptical power with the history data. If the optical power decreases, the fiber is faulty; proceedwith 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 offactors such as temperature, external force, and aging to ensure that the optical power of theboard at the downstream station to which the monitored fiber connects is restored to the historynormal value.




3-127

Step 4 If the alarm persists, the alarm might be misreported. Perform a perform a warm reset on on theboard.



----End


3.2.30 FPGA_ABN

DescriptionFPGA status is abnormal. The alarm is generated when the standby FPGA is currently used bythe board.

Attribute



ParametersNone

Impact on the SystemThe active FPGA file of the board is abnormal and the standby FPGA file is enabled. If thestandby FGPA file is abnormal, the board cannot work, which has an influence on the servicesof users. The case needs to be handled in time.

Possible Causesl The active FPGA file is not existed when the board boots.l Loading of the active FPGA file fails when the board boots.

Procedure

Step 1 Reload the FPGA file to the board.


----End


3 Alarm Processing




Issue 08 (2011-10-30)

3.2.31 GAINDATA_MIS

Description

The GAINDATA_MIS is an alarm indicating mismatch of gain attribute. When the nominalgain value issued by the NE software falls beyond the tuning range of the nominal gain, thealarm is reported.

Attribute



Parameters





Parameter 4 Indicates that the gain is excessively high or low. The value 0x01 indicatesthat the gain is excessively low; the value 0x02 indicates that the gain isexcessively high.


The service quality may be affected.

Possible Causesl The Raman board gain that is set is out of the permitted range.

l The insertion loss of the line changes.

l The optical power of the Raman board is manually locked.

l The laser on the Raman board is disabled.



3-129

Procedure

Step 1 Query the threshold of the current actual nominal gain on the T2000. Reconfigure a valid nominalgain value for the optical interface channel of the unit based on the queried threshold.

----End


3.2.32 HARD_BAD

DescriptionHardware failure alarm. When the system detects a hardware failure, this alarm is reported.


Attribute



Parameters


Parameter 1 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 denotedifferent components.

Impact on the SystemThe alarm affects the normal operating of the board and affects services.

Possible Causesl A clock relevant to services is faulty.l The power supply is faulty.l The board hardware is faulty.

3 Alarm Processing




Issue 08 (2011-10-30)

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. Fordetails, see the Parts Replacement.

----End


3.2.33 HARD_FAIL

DescriptionBoard failed alarm. The alarm is generated when the board failed.

Attribute




None

Impact on the SystemThe alarm affects the normal operating of the board and affects services.

Possible CausesThe board hardware is faulty.

Procedure

Step 1 Replace the faulty board. For details see Parts Replacement.

----End




3-131

3.2.34 INPWR_FAIL

Description

Input power failed. The alarm is generated when the power input is fault.

Attribute



Parameters



Parameter 1 The power supply module number, For example, 0x01 denotes the power supply1.


The power input of the system is affected, which leads to the function failure of the system.

Possible Causesl The input power is faulty.

l 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 PartsReplacement.

----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.35 J0_MM

Description

Trace indicator mismatch. The alarm is generated when the J0 byte received is not consistentwith the J0 byte to receive.


Attribute



Parameters






The services are not affected.

Possible Causesl The J0 byte is mismatched.l 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 consistentwith that to receive by the board at the local station. If they are inconsistent, set the two to beconsistent with each other.

Step 2 If the alarm persists, bit errors may exist in the line. Refer to the handling procedure of the B1_SDor B2_SD alarm for troubleshooting.



3-133

Step 3 If the alarm persists, consider whether to replace the board or not according to the actual situationbecause that only the J0_MM alarm does not affect the services. For details, see theTroubleshooting.

----End


3.2.36 K1_K2_M

DescriptionThe K1 and K2 bytes mismatch alarm. This alarm is generated when K1 transmitted by an 1:N(N≤8) optical channel protection group mismatches K2 received.


Attribute



ParametersNone

Impact on the System1:N (N≤8) optical channel protection might fails. As a result, services fail to be protected.

Possible Causesl The configuration of 1:N (N≤8) optical channel protection at the local or opposite station

is incorrect.l The board at the local or opposite station is faulty.

Procedure

Step 1 Check the the configurations of 1:N (N≤8) optical channel protection at the local and oppositestations. 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 K2received 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


3 Alarm Processing




Issue 08 (2011-10-30)

3.2.37 K2_M

Description

The K2 bytes mismatch alarm. This alarm is generated when K2 transmitted by an 1:N (N≤8)optical channel protection group mismatches K2 received.


Attribute



Parameters

None


1:N (N≤8) optical channel protection might fails. As a result, services fail to be protected.

Possible Causesl The configuration of 1:N (N≤8) optical channel protection at the local or opposite station

is incorrect.l The board at the local or opposite station is faulty.

Procedure

Step 1 Check the the configurations of 1:N (N≤8) optical channel protection at the local and oppositestations. 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 K2received 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 inthe physical coding sublayer (PCS) of a receiving port.



3-135

Attribute


Critical Service quality alarm





Impact on the SystemWhen 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 Causesl Configuration of signal type or rate of the equipment at the local station and the opposite

station are not consistent.l Link failure.l The equipment in the opposite station is faulty.l The receive optical power of the local board is abnormal.l The board at the local station is faulty.

Procedure

Step 1 Check whether the configuration of signal type or rate of the equipment at the local station andthe opposite station are consistent. If they are not consistent, modify the setting to ensure theconsistency.

Step 2 If the alarm persists, check whether the fiber or cable that is used to connect between theequipments at the local station and the opposite station are well connected. If they are not wellconnected, 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 thatis the case, remove the fault of the data equipment in the opposite station.

3 Alarm Processing




Issue 08 (2011-10-30)

Step 4 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 optical power specificationsof boards, see the Product Description. If the optical power is abnormal, take the alarm as theIN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.


----End

Related Information

None

3.2.39 LAN_LOC

Description

Ethernet communication failure. The alarm is generated when the external Ethernetcommunication and the network port fail.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the network port ID. For example, 0x01 indicates network port1 and 0x02 indicates network port 2.

Parameters 2 and 3 Indicates the number of the channel in which the alarm is generated. Thevalue 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 thisnetwork port fails. In this case, the communication between the NE and the T2000 stops.



3-137

Possible Causesl 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.

l The network port is not required but is enabled on the T2000.

l The network cable is faulty.

l The SCC board is faulty.

Procedure

Step 1 Query the alarm parameters on the T2000. Check whether the corresponding network port isrequired 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 cableis properly connected to the network port.

Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cableand re-connect it.

Step 3 If the alarm persists, the SCC board may be faulty. In this case, replace the faulty board. Fordetailed 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 thatit might cause personal injury if the IPA protection is not configured. The alarm is reported toprompt the user to configure the IPA protection.

Attribute



Parameters


3 Alarm Processing




Issue 08 (2011-10-30)



Parameters 2 and 3 Indicates the channel where the alarm is generated, the value is always0x00 0x01.


This alarm does not affect services; however, it might cause personal injury.

Possible Causesl 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 isabnormal.

Attribute



Parameters




3-139




Impact on the SystemThe locking of the output optical power of the board fails, which influences the services on theentire optical line.


Procedure



----End


3.2.42 LSR_COOL_ALM

DescriptionCooling current of the laser over threshold alarm. The alarm is generated when the refrigerationcurrent of the laser on the WDM side exceeds the threshold.


Attribute



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,

3 Alarm Processing




Issue 08 (2011-10-30)

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.




Impact on the SystemWhen the refrigeration current of the laser exceeds the threshold, the optical module of the boardworks abnormally. As a result, services cannot be transmitted or received normally.


Procedure


----End


3.2.43 LTEMP_OVER

DescriptionLaser temperature exceeds the threshold. The alarm is generated when the laser temperature ofthe board exceeds the threshold.


Attribute






3-141






Impact on the SystemThe transmit function of the laser is influenced, which leads to the abnormal transmitted opticalsignals. As a result, the signals received by the downstream station are degraded or the signalsare interrupted.

Possible Causesl The ambient temperature of the board is too high or too low.l The board hardware is faulty.

Procedure

Step 1 Check the ambient temperature of the board. For ambient temperature specifications of thespecific board, see the Product Description. If the ambient temperature is too high, handle thealarm 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 If the optical module is unpluggable, replace the faulty board. For details, see the Parts

Replacement.l If the optical module is pluggable, replace the faulty optical module or board. For details,

see the Parts Replacement.

----End


3.2.44 LTI

DescriptionAll clock sources are lost. The alarm is generated when external clock source exists in the prioritytable but the board works in holdover or free running status.

3 Alarm Processing




Issue 08 (2011-10-30)


Attribute



Parameters






The services are not affected and no bit errors are generated.

Possible Causesl The board is faulty.

l 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_LOSalarm.

Step 2 If the clock issued by the SCC is lost, check whether the SCC is faulty or the communicationbetween the SCC and the board is normal.

Step 3 If the local oscillator clock is lost, replace the faulty board. For details, see the PartsReplacement.

----End

Related Information

None



3-143

3.2.45 MAIL_ERR

DescriptionMail communication error. The alarm is generated when the communication between the boardmailbox and the SCC is abnormal due to the hardware or software fault.

Attribute





Parameter 1 The slot ID of the board of which the mailbox is faulty. For example, 0x01 standsfor slot 1.

Impact on the Systeml If the SCC is abnormal, it cannot issue commands to all boards of the NE, which might

affect the services.l If the board indicated by the alarm is abnormal, the SCC cannot issue commands to the

board, which might affect the services.

Possible Causesl The communication between the SCC and the mailbox on the backplane is abnormal.l 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. Fordetails, 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.


3 Alarm Processing




Issue 08 (2011-10-30)

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


3.2.46 MOD_COM_FAIL

DescriptionModule communicates abnormally. The alarm is generated when the communication of the CPUand other internal modules of the board is abnormal.


Attribute






Parameters 2 and 3 Indicates the ID of the protection group in which the alarm is generated.

Impact on the SystemBecause the communication between the CPU and other internal modules is interrupted, therelated operations cannot be performed by using the T2000 and the performance information ofeach module cannot be queried.

Possible Causesl The contact between the board and the connector of the optical module is poor.l The software processing of the related modules of the board is faulty.l The board hardware is faulty.



3-145

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 insertit again. For details, see the Troubleshooting.


----End

Related Information

None

3.2.47 MODULE_COOLCUR_OVER

Description

Module cooling current exceeds the threshold. The alarm is generated when the refrigerationcurrent of the module is higher than the upper threshold or lower than the lower threshold.

Attribute



Parameters






3 Alarm Processing




Issue 08 (2011-10-30)


The working performance and the reliability of the module is affected. Generally the QoS is notaffected. However, the QoS is affected if the alarm exists for a long time. The alarm should behandled in time.

Possible Causesl The temperature of the optical module is too high.


Procedure

Step 1 Check the ambient temperature of the board. For ambient temperature specifications of thespecific board, see the Product Description. If the ambient temperature is too high, handle thealarm by referring to the handling procedure of the TEMP_OVER alarm.


----End

Related Information

None

3.2.48 MODULE_TEMP_OVER

Description

Module temperature exceeds the threshold. The alarm is generated when the temperature of themodule is higher than the upper threshold or lower than the lower threshold.


Attribute



Parameters




3-147






The working performance and the reliability of the module is affected. Generally the QoS is notaffected. However, the QoS is affected if the alarm exists for a long time. The alarm should behandled in time.

Possible Causesl The ambient temperature of the board is too high or too low.


Procedure

Step 1 Check the ambient temperature of the board. For ambient temperature specifications of thespecific 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.


----End

Related Information

None

3.2.49 MS_REI

Description

Multiplex section remote error indication. The alarm is generated when the remote end detectsthe bit error block.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute


Warning Service alarm





Impact on the SystemBit errors occur in transmission.

Possible Causesl 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 boardin station A (the local station) contain the MS_REI signals. The OTU of the station A reportsthe MS_REI alarm on the client side after it detects the MS_REI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theMS_REI alarm

The client signals containthe MS_REI signal

WDMside

Clientside

l The too low receive optical power in the opposite station due to the too low transmit opticalpower at the local station or faulty transmission line would lead to that the opposite stationreceives bit error blocks.



3-149

As shown in the following figure:

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theMS_REI alarm

WDMside

Clientside

Insert the MS_REIsignal

Detects the B2 bit errors

Procedure

Step 1 Query which side reports the MS_REI alarm,l If the client side reports the MS_REI alarm, remove the fault on the client-side equipment

first.l 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 opticalpower specifications of the specific board, see the Production Description. If the transmittingoptical power at the local station is excessively low, replace the optical module or the faultyboard.

Step 3 If the alarm persists and the transmit optical power at the local station is normal, check whetherthe receive optical power in the opposite station is excessively low. If the receive optical powerin the opposite station is excessively low, the transmission line might be faulty. Check the inputand output optical power of the optical amplifier stations are normal according to the lineconnection.l If the optical power is normal but bit errors still exist in the opposite station, replace the

board in the opposite station.l If the optical power is abnormal, locate the specific position and cause of the fault and then

remove the fault.

----End


3.2.50 MUT_TLOS

DescriptionLoss of the output multiplexed signals alarm. The alarm is generated when the output multiplexedsignals of the board is lost.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute







Impact on the SystemAll services that pass through the board are interrupted.

Possible Causesl The optical power is excessively low of the output port, maybe the input optical power of

the add wavelength is excessively low.l The attenuation of signals in line transmission is overlarge.l The board is faulty.

Procedure

Step 1 Check whether the fiber connection is correct according to the engineering fiber connectiondiagram. The input optical signals in different wavelengths should be accessed to correspondinginput optical interfaces of the board. If the fiber connection is incorrect, correct it according tothe diagram.

Step 2 If the alarm persists, measure the actual receive optical power of the board at the local stationby using an optical power meter. Check whether the receive optical power or transmit opticalpower is within the normal range. For the optical power specifications of the specific board, seethe Product Description.

Step 3 If the receive optical power or transmit optical power of the board at the local station isexcessively low, check whether there have MUT_LOS alarm at the local station,see the handlingprocedure of the SUM_INPWR_LOW or SUM_OUTPR_LOW alarm for troubleshooting.l If yes, see the handling procedure of the MUT_LOS alarm for troubleshooting.



3-151

l 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. Fordetails, 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 installingstate.

Attribute



Parameters

None

Impact on the Systeml The NM cannot query all configuration information about the NE.

l If the alarm is generated by the NE that is in normal running state, the data of the NM isinitialized. You need to issue the correct configuration in time.

Possible Causesl The NE is in the initial installing state.

l 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.


----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.52 NESOFT_MM

Description

Software difference between working and protection boards alarm. The two file systems of theSCC board are backup for each other. Each file is saved in the two file systems. The alarm isgenerated when the software versions in the two file systems are not consistent or the versionsof the files with the same name are not consistent.

Attribute


Major Process alarm

Parameters



Parameter 1 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 asingle SCC differ.

0x08 denotes that file versions of the active and standby SCCs differ, orthere is no file with the same name under the corresponding directory ofthe opposite board.

0x0c denotes that the file versions in the active and standby areas of asingle SCC differ; and the file versions of the active and standby SCCsalso 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-153

Possible Causesl The software version currently running on the active SCC board is not consistent with that

on the standby SCC board.l The version of the software set file in the active area of the active or standby SCC is not

consistent with that of the file that has the same name in the SCC board.l The software set file in the active area of the active or standby SCC does not have the file

that has the same name and same type in the standby or active board.

Procedure

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 tomake 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 activearea of the other SCC board that does not have the file.

----End


3.2.53 NO_BD_PARA

DescriptionNo board parameter alarm. The alarm is generated when the board does not have the parametertable.


Attribute






3 Alarm Processing




Issue 08 (2011-10-30)



Impact on the SystemThe parameter table file of the board is lost, which may influence the services of users.

Possible Causesl The correct parameter table is not loaded before delivery.l The incorrect parameter table file is loaded on site, which overlaps the original file.l The parameter table file is abnormally missing in running process.

Procedure

Step 1 Perform a warm reset on the faulty board through the T2000. For details, see the Troubleshooting.


----End


3.2.54 NO_BD_SOFT

DescriptionNo board software alarm. The alarm is generated when the board does not have the necessaryfiles, for example, loading software, manufacturer information and logic software.


Attribute






3-155


Parameter 1 It is always 0x01.

Parameters 2 and 3 Indicates the ID of the lost file. For example, 0x00 0x01 denotes that theactive 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 thatthe manufacturer information is lost.


The board does not have the desired files. The running file cannot be found when the board isreset. As a result, the normal function cannot be realized. The alarm must be cleared in time.

Possible Causesl Parts of software are not loaded to the board.l The software on the board is abnormally missing in the running process.l The inside detection of the board is abnormal.

Procedure

Step 1 Reload the corresponding software through the T2000.



----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 aresuppressed.


Attribute



3 Alarm Processing




Issue 08 (2011-10-30)

Parameters


Name Meaning




If the logical fiber connection is wrong, there is no impact on services. Otherwise there mightbe 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 orOMS_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 thedownstream station when the board at OTS layer detects the OTS_LOS-O signal and the alarmis generated when the downstream station receives the signals



3-157

Attribute



Parameters

Name Meaning



Impact on the SystemIf the logical fiber connection is wrong, there is no impact on services. Otherwise there mightbe impact on the system monitoring and management.

Possible Causesl The logical fiber connection is not consistent with the actual fiber connection.l The OCh layer receives the FDI-O overhead signal from the OCH layer, when the OMS

lost overhead signals because of a fiber cut, low optical power, or dispersion. This alarmis generated.

Procedure


Step 2 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station andall upstream stations. If yes, clear the OTS_LOS-O alarm by following the proper handlingprocedures.

----End


3.2.57 OCH_FDI-P

DescriptionForward defect indication (payload) at OCh layer. The OCH_FDI-P signal is inserted to thedownstream station when the board at OMS layer detects payload LOS signals and the alarm isgenerated when the downstream station receives the signals.

3 Alarm Processing




Issue 08 (2011-10-30)

Attribute



Parameters


Name Meaning





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 lostpayload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.

Procedure


Step 2 If the alarm persists, check whether there are the OTS_LOS-P or OMS_LOS-P alarms at theopposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarmsby following the proper handling procedures.

----End

Related Information

None



3-159

3.2.58 OCH_LOS-P

DescriptionLoss of signal (payload) at OCh layer. The OTU detects LOS alarms and there is no OTS_LOS-P, OMS_LOS-P or OMS_SSF-P alarm in the superstratum.

Attribute







Impact on the SystemIf the logical fiber connection is wrong, there is no impact on services. Otherwise there mightbe impact on the services.

Possible Causesl The logical fiber connection is not consistent with the actual fiber connection.l The board detects no payload signals because of there is a fiber cut, low optical power, or

dispersion.

Procedure


Step 2 Confirm that the fiber connection between the OTU board that reports this alarm and theDEMUX board is correct.

Step 3 If the alarm persists, check whether the output optical power at the OUT interface of the OTUboard in the opposite or upstream station is normal or not. If not, clear the alarm according to

3 Alarm Processing




Issue 08 (2011-10-30)

the procedure to handle the IN_PWR_HIGH or IN_PWR_LOW alarm to make the output opticalpower normal.

Step 4 If the alarm persists, check whether the fiber at the OUT interface of the OTU board in theopposite or upstream station is disconnected from the MUX board or not. If yes, correctly connectthe fiber between the two boards.

Step 5 If the alarm persists,check whether the dispersion of the fiber is complied with the requirementor not. For the specifications of the dispersion, see the Product Description. If not, connect asuitable dispersion compensation module by referring to the Troubleshooting

Step 6 Check whether there is R_LOS alarm,

l If yes, clear the alarm according to the procedure to handle R_LOS.

l 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 theupstream service link, or no logical fiber connection is configured from the OTU board to themultiplex board. In this case, the OCI signal is inserted in the downstream service link. Afterreceiving the OCI signal, the optical terminating node in the downstream reports the OCH_OCIalarm.

Attribute



Parameters






3-161




Possible Causesl The logical fiber connection is not consistent with the actual fiber connection.l No optical cross-connection for services to the local station is configured at the upstream

station.

Procedure


Step 2 Check whether the services of the optical cross-connections at the upstream station areconfigured. If no, re-configure the optical cross-connections to ensure the normal transmissionof the services.

----End


3.2.60 OCH_SSF

DescriptionServer signal fail at OCh layer. When the OCH_SSF-P and OCH_SSF-O alarms coexist, thisalarm is generated. At the same time, the OCH_SSF-P and OCH_SSF-O alarms are suppressed.


Attribute




3 Alarm Processing




Issue 08 (2011-10-30)






Possible Causesthe 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 2 Check whether there are OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-Palarms 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 handlingprocedures.

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 byfollowing the proper handling procedures.

----End


3.2.61 OCH_SSF-O

DescriptionServer signal fail (overhead) at OCh layer. When the OMS layer detects the lost of the overheadsignals, this alarm is generated.




3-163

Attribute



Parameters






If the logical fiber connection is wrong, there is no impact on services. Otherwise there mightbe impact on the system monitoring and management.

Possible Causesl 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 alarmis generated.

Procedure


Step 2 Check whether there is OTS_LOS-O alarm on the FIU connected to the local board, If yes, clearthe 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 andall upstream stations. If yes, clear the OTS_LOS-O alarm by following the proper handlingprocedure.

----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

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 lostpayload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.

Procedure


Step 2 Check whether there are OTS_LOS-P or OMS_LOS-P alarms on the FIU connected to the localboard, If yes, clear the OTS_LOS-P or OMS_LOS-P alarms by following the proper handlingprocedures.



3-165

Step 3 If the alarm persists, check whether there are the OTS_LOS-P or OMS_LOS-P alarms at theopposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarmsby following the proper handling procedures.

----End


3.2.63 ODU_LCK

DescriptionODU locked. The alarm is generated when all signal values of the optical data unit (ODU) inthe received optical transport network (OTN) services are 0x55. The alarm indicates that theupstream signal connection is locked and no signals passes.


Attribute







Impact on the SystemCarried services at this board are interrupted.

Possible Causesl 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 Alarm Processing




Issue 08 (2011-10-30)

The client-side input signals of the OTU in station A (local station) contains ODU_LCKsignals. The OTU in station A reports the ODU_LCK alarm on the client side after detectingthe ODU_LCK signals. At the same time the OTU transparently transmits the ODU_LCKsignals to the station B (opposite station). The WDM side of the OTU in the station B reportsthe ODU_LCK alarm after detecting the ODU_LCK signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theODU_LCK alarm

The client signals containthe ODU_LCK signal

WDMside

Clientside


l 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 stationA (opposite station). The WDM side of the OTU in the station B (local station) reports theODU_LCK alarm after detecting the ODU_LCK signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside


Manually insert theODU_LCK signal

ProcedureStep 1 Query which side reports the ODU_LCK alarm,

l If the client side reports the ODU_LCK alarm, remove the fault on the client equipmentfirst. For details, see the related manuals.

l 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 stationhas the ODU_LCK alarm. If yes, remove the fault on the client equipment in the opposite stationfirst.

Step 3 Query on the T2000 whether the ODU_LCK signals are manually inserted to the OTU in theopposite station. If yes, release the ODU_LCK signals manually inserted. For details, see theTroubleshooting.

----End



3-167


3.2.64 ODU_OCI

DescriptionODU (Optical channel data unit) open connection indication. The alarm is generated when allsignal 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 inputinterface of the upstream station.


Attribute







Impact on the SystemCarried services at this board are interrupted.


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_OCIsignals. The OTU in station A reports the ODU_OCI alarm on the client side after detectingthe ODU_OCI signals. At the same time the OTU transparently transmits the ODU_OCIsignals to the station B (opposite station). The WDM side of the OTU in the station B reportsthe ODU_OCI alarm after detecting the ODU_OCI signals.

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theODU_OCI alarm

The client signals containthe ODU_OCI signal

WDMside

Clientside


l 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 stationA (opposite station). The WDM side of the OTU in the station B (local station) reports theODU_OCI alarm after detecting the ODU_OCI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside


Manually insert theODU_OCI signal

Procedure

Step 1 Query which side reports the ODU_OCI alarm,l If the client side reports the ODU_OCI alarm, remove the fault on the client equipment

first. For details, see the related manuals.l 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 stationhas the ODU_OCI alarm. If yes, remove the fault on the client equipment in the opposite stationfirst.

Step 3 Query on the T2000 whether the ODU_OCI signals are manually inserted to the OTU in theopposite station. If yes, release the ODU_OCI signals manually inserted. For details, see theTroubleshooting.

----End

Related Information

None



3-169

3.2.65 ODU_TCMn_AIS

DescriptionODU TCMn alarm indication signal. An AIS signal travels downstream, which indicates that asignal failure is detected in the upstream.

n indicates the level of TCM and its value ranges from 1 to 6.

Attribute







Impact on the SystemThe services borne by the optical interface would be unavailable.

Possible Causesl Signals input from the client side contain ODU_TCMn_AIS signal.l The corresponding board at the opposite end transmits the ODU_TCMn_AIS signals.l 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 equipmenton the client side.

3 Alarm Processing




Issue 08 (2011-10-30)

Step 3 Query whether the ODU_PM_AIS, R_LOS or R_LOF alarm exists on the client side of the OTUboard at the opposite end by using the T2000. If the alarm exists, check the equipment at theopposite 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 FECtype. If the configuration is incorrect, modify the configuration.

----End

Related InformationITU-T G.709

3.2.66 ODU_TCMn_BDI

DescriptionODU TCMn backward defect indication. The alarm is generated when five consecutive BDIbytes in the TCMn overhead field are "1".


Attribute







Impact on the SystemBit errors occur in the downstream station.



3-171

Possible Causesl Signals input from the client side contain ODU_TCMn_BDI signal.

l 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 2 Query whether the alarm is reported from the client side or the WDM side,

l If the alarm is reported from the client side, check the equipment on the client side.

l If the alarm is reported from the WDM side, check whether the corresponding OTU boardin the downstream station receives the LOF, LOM, ODU_TCMn_AIS,ODU_TCMn_LCK, ODU_TCMn_LTC, ODU_TCMn_OCI, ODU_TCMn_SSF alarmsby 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 containthe BIP8 bit errors, it inserts the ODU_TCMn_BEI alarm back to the upstream board. The alarmis generated when the upstream station detects that the BEI flag in the OCH-OH of the TCMnsection of the received signals is true.


Attribute



Parameters


3 Alarm Processing




Issue 08 (2011-10-30)




Impact on the SystemThe bit errors occur to the service signals, which influences the system quality.


client side supports the OTN services, the input signals on the client side contain theODU_TCMn_BEI signals, as shown in the following figure. The input signals on theclient side of the OTU in the station A contain the ODU_TCMn_BEI signals. The OTU inthe station A reports the ODU_TCMn_BEI alarm on the client side after detecting theODU_TCMn_BEI signals and transparently sends the ODU_TCMn_BEI signals to thestation B (opposite station) at the same time. The WDM side of the OTU in the station Breports the ODU_TCMn_BEI alarm after detecting the ODU_TCMn_BEI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detectsandreports theODU_TCMn_BEI alarm

The client signals containthe ODU_TCMn_BEI signal

WDMside

Clientside

Detects and reports the alarmODU_TCMn_BEI

l Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.l Cause 1 for the alarm generated on the WDM side: The ODU-TCMn-BIP8 bit errors occur

when the OTU in the opposite station receives the signals at the local station, as shown inthe following figure. The WDM side of the OTU in the station B (opposite station) insertsthe ODU_TCMn_BEI signals back to the station A (local station) after detecting the ODU-TCMn-BIP8 bit errors. The WDM side of the OTU in the station A reports theODU_TCMn_BEI alarm after detecting the ODU_TCMn_BEI signals.



3-173

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects the ODU_TCMn_BEI biterrors

Detects and reports theODU_TCMn_BEI alarm

Insert the ODU_TCMn_BEIsignal back


l Cause 3 for the alarm generated on the WDM side: The board at the opposite station isfaulty. It inserts the ODU_TCMn_BEI signals back to the local station improperly. Asshown 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. TheWDM side of the OTU in the station A reports the ODU_TCMn_BEI alarm after detectingthe ODU_TCMn_BEI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects and reports theODU_TCMn_BEI alarm

Insert the ODU_TCMn_BEIsignal by mistake

Procedure


l Cause 1 for the alarm generated on the client side: In the case of the OTU of which theclient side supports the OTN services, the input signals on the client side contain theODU_TCMn_BEI signals.

1. If the client side reports the ODU_TCMn_BEI alarm, check whether the client-sideequipment 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.

2. If the alarm persists, perform a cold reset on the faulty board at the local station.



3 Alarm Processing




Issue 08 (2011-10-30)

1. If the alarm persists, perform a cold reset on the faulty board at the local station throughthe T2000.

2. If the alarm persists, the OTU at the local station may be faulty. Replace the faultyboard.

l Cause 1 for the alarm generated on the WDM side: The PM_BIP8 bit errors occur whenthe 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 localstation. If yes, handle the alarm by referring to the handling procedure of theODU_TCMn_EXC alarm.

l Cause 2 for the alarm generated on the WDM side: The board that reports the alarm isfaulty.1. If the alarm persists, perform a cold reset on the faulty board at the local station through

the T2000.2. If the alarm persists, the OTU at the local station may be faulty. Replace the faulty

board.l 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. If the alarm persists, perform a cold reset on the faulty board in the opposite station

through the T2000.2. If the alarm persists, the OTU in the opposite station may be faulty. Replace the faulty

board.

----End


3.2.68 ODU_TCMn_DEG

DescriptionODU TCMn signal degraded. This alarm is generated when the BIP8 detection mode is burstymode and the signal degradation or bit error count exceeds the threshold.


Attribute






3-175






If the alarm is generated, the services borne by the optical interface would generate bit errors,which makes the service signals unavailable.

Possible Causesl The optical interface at the local end is faulty.l The optical interface at the opposite end is faulty.l 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, andchannel 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 withinthe 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 andIN_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 theTroubleshooting.

----End

Related Information

ITU-T G.709

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.69 ODU_TCMn_EXC

DescriptionODU TCMn section BIP8 error cross the threshold. When the BIP8 detection mode is Poissonmode and the signal degradation or bit error count exceeds the threshold.


Attribute







Impact on the SystemThe alarm has an influence on the QoS of the service signals.

Possible Causesl The attenuation of the received signals is rather large, and the fiber of the transmission line

is abnormal.l The transmit part of the opposite station is faulty.l The receive part of the local station is faulty.

Procedure




3-177


Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using theT2000. Loop back the transmit optical interface and receive optical interface on the WDM sideof the OTU board on the upstream station. If the bit error exists, clear the bit error fault of theupstream station.

Step 4 If the alarm persists, replace the faulty board on the local station. For details, see theTroubleshooting.

----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 tolock the access point signal of users during testing. It can be generated when the service layeradapts the source and sink. The alarm is generated when the STAT byte value is "101" duringlocking.


Attribute



Parameters




3 Alarm Processing




Issue 08 (2011-10-30)



Impact on the SystemThe services borne by the optical interface would be unavailable.

Possible CausesThe 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 generatesthis alarm.

Step 2 Set the LCK type to be Disabled if it is Enabled.

----End


3.2.71 ODU_TCMn_LTC

DescriptionLoss of ODU TCMn serial connection. The TCM provides the connection monitoring functionof the ODU to cater for the different applications. For example, the TCM from optical NNI tooptical NNI monitors the connection through the carrier network of the ODU. The alarm isgenerated when the serial connection is lost and the STAT byte value is "000".


Attribute






3-179




Impact on the SystemThe tandem connection monitoring (TCM) is not available.

Possible CausesThe 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


3.2.72 ODU_TCMn_OCI

DescriptionODU TCMn open connection indication. The alarm is generated when the output interface isnot connected to the input interface and the STAT byte value is "110".


Attribute




3 Alarm Processing




Issue 08 (2011-10-30)






The services borne by the optical interface would be unavailable.

Possible Causesl The corresponding board in the upstream station has ODU_TCMn_OCI alarm.l There is loopback in the corresponding board in the opposite station.l The corresponding board in the opposite station has no or incorrect cross-connection

configuration.

Procedure


Step 2 If the alarm persists, check whether the upstream station has this alarm. If so, locate the stationthat 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 isconfigured with incorrect or no cross-connection configuration. If so, configure the correct cross-connection.

----End

Related Information

ITU-T G.709

3.2.73 ODU_TCMn_SSF

Description

The ODU TCMn server signal failure alarm.




3-181

Attribute








Possible Causesl The ODU_TCMn_AIS or ODU_LOFLOM alarm is generated to the line.l The OTUk_TIM alarm is generated to the line and the OTUk_TIM follow-up response is

set to be enabled.l The OTUk_SSF alarm is generated.

Procedure

Step 1 Check along the service signal flow to locate the station that first generates the SSF alarm.1. Check whether the 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.2. 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


3 Alarm Processing




Issue 08 (2011-10-30)

3.2.74 ODU_TCMn_SD

Description

Optical channel data unit (ODU) layer TCMn section bit error degrade alarm. This alarm isgenerated when the detection board detects that the number of BIP8 check bit errors on sectionTCMn at the ODU layer exceeds the degrade threshold.


Attribute


Major Service

Parameters






The bit errors occur in the service signals, which influences the system quality.

Possible Causesl 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.

l The input optical power is excessively high or low.

l 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.

l The upstream board is faulty.

l The local board is faulty.



3-183

Procedure

Step 1 In the case of the OTU board that supports the OTN service type, query on the T2000 whetherthe client input signals contain excessive BIP8 bit errors on section TCM1. If yes, remove thefault of the client equipment.

Step 2 If the alarm persists, query on the T2000 the input optical power at each optical interface of theboard. 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 opticalpower at any optical interface is beyond the normal range, handle the alarm according to themethod 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 faultyboard, see the Parts Replacement.

Step 5 If the alarm persists, the upstream board might be faulty. For details on how to replace the faultyboard, 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 traceidentifier 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 expectedAPI.

For the set TIM detection mode, the network architecture can be classified into the followingthree types.

l For the point-to-point topology, only the source access point identifiers (SAPI) is comparedfor the sink of trail termination.

l For the point-to-multipoint topology, only the SAPI is compared for the sink of trailtermination.

l For the multipoint-to-multipoint topology, only the destination access point identifiers(DAPI) is compared for the sink of trail termination.


Attribute



3 Alarm Processing




Issue 08 (2011-10-30)

Parameters






If the alarm is generated, the signal quality of the services borne by the optical interface wouldbe degraded. Hence, the service signals may be unavailable.

Possible Causesl The networking architecture and the TIM detection mode to configure are not consistent.

l The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI toreceive at the local end.

l The fiber connection is incorrect.

l 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 forthe local end on the T2000 interface according to networking architecture. If the topology is apoint-to-point one or point-to-multipoint one, only the SAPI is compared for the sink of trailtermination. If the topology is multipoint-to-multipoint topology, only the DAPI is comparedfor the sink of trail termination.

Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that toreceive at the local end through the T2000. If they are not consistent, query the TTI received onthe T2000. Set the SAPI and the DAPI of the TTI to receive at the local end to be the same asthese of the TTI received.

Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstreamport 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 thecross-connection.

----End



3-185

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 alarmscoexist, this alarm is generated. At the same time, the OMS_BDI-P and OMS_BDI-O alarmsare suppressed.

Attribute



Parameters






The incorrect logical fiber connection does not affect services; however, other errors interruptthe 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 fiberconnection to make it consistent with the actual fiber connection.

3 Alarm Processing




Issue 08 (2011-10-30)

Step 2 Check whether there are the OTS_LOS, OTS_LOS-O, OTS_TIM or OMS_LOS-P alarms at theopposite 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 backto the upstream station when the downstream station receives no overhead signals from theupstream station and the OTS_LOS_O alarm is generated from the downstream station.

Attribute



Parameters







Possible Causesl 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



3-187

cut, low optical power, or dispersion. This alarm is generated when the local station receivesthe BDI-O overhead signal.

l The local station sends no overhead signals.

Procedure


Step 2 Check whether there are the OTS_LOS-O alarm at the opposite station and all downstreamstations. 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 backto the upstream station when the downstream station receives no payload signals from theupstream station.

Attribute



Parameters





3 Alarm Processing




Issue 08 (2011-10-30)



Possible Causes

The downstream station inserts the BDI-P overhead signal back to the OMS layer of the localstation, when the downstream station detects no payload signals because of a fiber cut, lowoptical power, or dispersion. This alarm is generated when the local station receives the BDI-Poverhead signal.

Procedure


Step 2 Check whether there are the OTS_LOS-P or OMS_LOS-P alarms at the opposite station and alldownstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarms alarms by followingthe 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 thedownstream station when the board at OTS layer detects no overhead signals and can not sendoverhead signals to the downstream station.

Attribute



Parameters




3-189






Possible Causesl The logical fiber connection is not consistent with the actual fiber connection.

l The FDI-O overhead signal is inserted to the OMS layer of the downstream station, whenthe local station detects no overhead signals because of a fiber cut, low optical power, ordispersion. This alarm is generated when the downstream station receives the FDI-Ooverhead signal.

Procedure


Step 2 Check whether there is the OTS_LOS-O alarm at all upstream stations. If yes, clear theOTS_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 thedownstream station when the board at OTS layer detects no payload signals and can not sendpayload signals to the downstream station.

Attribute



3 Alarm Processing




Issue 08 (2011-10-30)

Parameters






Services are interrupted.

Possible Causes

The FDI-P signal is inserted to the OMS layer of the downstream station, when the local stationdetects no payload signals because of a fiber cut, low optical power, or dispersion. This alarmis generated when the downstream station receives the FDI-P signal.

Procedure


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.



3-191

Attribute



Parameters







l The OMS layer detects no payload signals because of there is a fiber cut, low optical power,or dispersion.

Procedure


Step 2 Confirm that the actual fiber connection between the board that reports this alarm and the FIUboard is correct.

Step 3 Check whether there is OTS_LOS alarm on the FIU, if yes, clear the alarm according to theprocedure to handle OTS_LOS.

Step 4 Check whether there is MUT_LOS alarm,

l If yes, clear the alarm according to the procedure to handle MUT_LOS.

l If not, replace the faulty board by referring to the Troubleshooting.

----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.82 OMS_SSF

Description

Server signal fail at OMS layer. When the OMS_SSF-P and OMS_SSF-O alarms coexist, thisalarm 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 2 Check whether there is OTS_LOS, OTS_TIM, OTS_LOS-P or OTS_LOS-O alarms on the FIUconnected to the local board, If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P or OTS_LOS-O alarms by following the proper handling procedure.



3-193

Step 3 If the alarm persists, check whether there are the OTS_LOS, OTS_TIM, OTS_LOS-P orOTS_LOS-O alarms at all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P or OTS_LOS-O alarms by following the proper handling procedures.

----End


3.2.83 OMS_SSF-O

DescriptionServer signal fail (overhead) at OMS layer. When the OTS layer detects the failure of theoverhead signals or receives the OMS_FDI-O signal from the upstream station, this alarm isgenerated.

Attribute







Impact on the SystemIf the logical fiber connection is wrong, there is no impact on services. Otherwise there mightbe impact on the system monitoring and management.

Possible Causesl The logical fiber connection is not consistent with the actual fiber connection.l Because of a fiber cut, low optical power, dispersion, or failure in overhead signals on the

upstream OTS layer, the FDI-O and SSF-O of the OMS layer are inserted into the

3 Alarm Processing




Issue 08 (2011-10-30)

downstream station; or the overhead signals on the local OTS layer fail, and thus the OMSlayer reports this alarm.

Procedure


Step 2 Check whether there is OTS_LOS-O or OOS_LOST alarm on the FIU connected to the localboard, If yes, clear the OTS_LOS-O or OOS_LOST alarm by following the proper handlingprocedure.

Step 3 If the alarm persists, check whether there is the OTS_LOS-O or OOS_LOST alarm at theopposite station and all upstream stations. If yes, clear the OTS_LOS-O or OOS_LOST alarmby 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 payloadsignals or receives the OMS_FDI-P signal from the upstream station, this alarm is generated.

Attribute



Parameters







3-195



Possible Causes

The OMS layer receives the SSF-P overhead signal from the OTS layer, when the OTS can notdetect any signals because of a fiber cut, low optical power, or dispersion. This alarm isgenerated.

Procedure


Step 2 Check whether there is OTS_LOS-P alarm on the FIU connected to the local board, If yes, clearthe 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 andall upstream stations. If yes, clear the OTS_LOS-P alarms by following the proper handlingprocedures.

----End

Related Information

None

3.2.85 OOS_LOST

Description

Loss of OOS (OTM overhead signal). When the local station receives no overhead signals inconsecutive 10s and there is not OTS_LOS-O alarm, this alarm is generated.

Attribute



Parameters


3 Alarm Processing




Issue 08 (2011-10-30)





If the logical fiber connection is wrong, there is no impact on services. Otherwise there mightbe impact on the optical layer overhead.


l The local station receives no overhead signals in consecutive 10s because of the oppositestation sends no overhead signals.

Procedure


Step 2 Check whether the opposite station supports the OLS function,

l If not, it is not needed to handle this alarm.

l 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 theport attribute configuration of the working and protection channels of the protection group isnot consistent.

Attribute





3-197

Parameters



Parameter 1 The protection type. For example,




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 groupis not consistent.

Procedure

Step 1 Check whether the port attribute configuration of the working and protection channels at thelocal station is consistent. If not, configure the port attribute of the working and protectionchannels again to ensure the consistency.

Step 2 Check whether the port attribute configuration of the working and protection channels in theopposite 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 theconsistency.

----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.87 OPS_PS_FAIL

DescriptionFailure of optical channel protection switching. The alarm is generated when the optical channelprotection switching of the services fails.

Attribute





Parameter 1 The protection type. For example,



Parameter 2 The ID of the protection group in which the alarm is generated. For example,0x01 denotes protection group 1.


0x00 stands for the protection unit.

0x01 stands for the working unit.

Impact on the SystemServices cannot be switched from the working channel to the protection channel, which leadsto the service interruption.

Possible CausesThe OTU board is faulty.

ProcedureStep 1 Replace the faulty OTU board. For details, see the Parts Replacement.

----End



3-199

Related Information

None

3.2.88 OPS_PS_FIXED

Description

Alarm of optical channel protection switching. The alarm is generated when the protectionswitching state is changed to locked or forced switching whose priority is higher than auto-switching.

Attribute



Parameters


Name Meaning

Parameter 1 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.



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




Issue 08 (2011-10-30)


The protection group does not initiate auto-switching in case of the SF or SD alarm, and thusthe services are interrupted.

Possible Causesl Cause 1: The protection switching state is changed to locked or forced switching.

Procedure

l Query the alarm on the T2000 and record the type and ID of the protection group wherethe alarm is generated.

l 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 externalswitching is the need for normal working. If the external switching is the need fornormal working, there is no need to handle the alarm.


----End

Related Information


3.2.89 OPUk_PLM

Description

OPUk payload mismatch. The type of received payload mismatches the expected payload typedefined in the adaption function.

k indicates the level of rate and its value is 2 and 3.

Attribute



Parameters




3-201




Impact on the SystemPossibly the services are not available.

Possible CausesThe setting of PT bytes to be received at the OPU layer of the local NE is different from thereceive 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 theopposite station. For the load type of the board, see the Hardware Description. If the load typesof the boards do not match, replace one of them with the matched board. For details, see theParts Replacement.

Step 2 If the alarm persists, use the T2000 to query whether the PT byte value to be received at theOPU 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 transmittedby the opposite NE..

----End


3.2.90 OSC_RDI

DescriptionRemote defect indication. The alarm is generated when the opposite station call back the localstation after receiving an R_LOF alarm.


Attribute



3 Alarm Processing




Issue 08 (2011-10-30)





Impact on the SystemThe communication between the two stations is abnormal.

Possible Causesl The opposite station receives the R_LOF signals.l The optical fiber is damaged.l 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_LOFalarm for troubleshooting.

Step 2 If the alarm persists, check whether the fiber between the two stations is damaged. If that is thecase, repair the fiber.


----End


3.2.91 OTU_AIS

DescriptionOTU (optical transponder unit) alarm indication signal. The alarm is generated when the OTUboard detects that all signals at the OTU layer of the input signals are abnormal. The alarmindicates that the signals at the OTU layer are faulty and the data borne is unavailable.




3-203

Attribute



Parameters






Carried services at this board are interrupted.


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 theOTU_AIS signals. The OTU in the station A reports the OTU_AIS alarm on the client sideafter detecting the OTU_AIS signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theOTU_AIS alarm

The client signals containthe OTU_AIS signal

WDMside

Clientside

l The upstream signal source sends the OTU_AIS signals.

3 Alarm Processing




Issue 08 (2011-10-30)

Procedure

Step 1 If the client side reports the OTU_AIS alarm, remove the fault on the client equipment first. Fordetails, see the related manuals.

Step 2 If the WDM side reports the OTU_AIS alarm, remove the fault on the upstream signal source.

----End


3.2.92 OTU_LOM

DescriptionLoss of Multi-frame. The alarm is generated when the MFAS values of the received signal framesare not successive.


Attribute







Impact on the SystemThe services carried by this board may be unavailable.

Possible Causesl The signals received by the OTU at the local station have excessive bit errors.



3-205

l The board in the upstream station does not send the correct number of successive frames.l The board at the local station is faulty.l 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 boardat the local station. If the BIP8 bit errors are excessive, handle the alarm by referring to thehandling 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 thecorrect number of successive frames. If not, cold reset the board in the upstream station. Fordetails, see the Troubleshooting.

Step 3 If the alarm persists, cold reset the faulty board at the local station through the T2000 or removethe faulty board and then insert it. For details, see the Troubleshooting.


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 InformationThe value of the multi-frame alignment signal (MFAS) byte of the OTN frames sequentlychanges from "0000 0000" to "1111 1111" in all together 256 frames. The value of the MFASbyte in each OTUk/ODUk frame is larger than that of the preceding frame by one. Hence, 256frames of multi-frame signals can be provided. The value of the MFAS byte must be compliantwith the rule of increase by degrees.

3.2.93 OUT_PWR_LOW

DescriptionOutput optical power too low alarm. The laser output optical power is excessively low.


Attribute




3 Alarm Processing




Issue 08 (2011-10-30)






The output optical power of the laser is excessively low, which influences the normaltransmission of services.

Possible Causesl The input optical power is excessively low.

l The laser is aged.


Procedure

Step 1 Check whether the input optical power of the interface of the board at the local station is withinthe normal range by using the T2000. For the optical power specifications of the specific board,see the Product Description.

l If it is not within the normal range, add a suitable attenuation to adjust the input opticalpower in the normal range.

l If it is within the normal range, replace the faulty optical module. For details, see the PartsReplacement.


----End

Related Information

None

3.2.94 OUTPWR_FAIL

Description

Output power failed. The board regularly reads the AD value and calculates the voltage valueby using a formula. An overvoltage or undervoltage alarm is generated when the board comparesthe calculated voltage with the threshold.



3-207

Attribute





Parameter 1 Indicates the input power supply number. For example, 0x01 indicates powerinput 1 and 0x02 indicates power input 2.

Impact on the SystemThe power input of other modules are affected, which leads to the functional faults of relatedmodules.

Possible CausesThe power supply module is faulty.

Procedure

Step 1 Replace the faulty power module. For details, see the Parts Replacement.

----End


3.2.95 PATCH_ACT_TIMEOUT

DescriptionDuration of patch package in activation state too long. The alarm is generated when the durationthat the patch package is in the activation state exceeds the threshold.

Attribute



3 Alarm Processing




Issue 08 (2011-10-30)

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 ofthe observation.

Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using theT2000.

----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 theduration 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-209

Procedure

Step 1 If the patch file is confirmed to be correct, activate the patch file through 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 thesystem.

Possible Causes

If the patch is in the running status before NE reboots, the patch file is detected to be incorrectafter 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




Issue 08 (2011-10-30)

3.2.98 PATCH_NOT_CONFIRM

DescriptionActivated patch has not been confirmed overtime. The alarm is generated when the patch file isnot confirmed five minutes after it is activated.

Attribute



ParametersNone

Impact on the SystemThe activated status of the patch is the intermediate status for you observe the effect of the patchfile. The status is used to remain the user to confirm the patch file, which has no influence onthe normal running of the system.

Possible CausesThe 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 ofthe observation.


----End

Related InformationThe 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 afterthe patch file is confirmed to be qualified. The alarm disappears if the activated status of thepatch file is changed upon a command.

3.2.99 PATCHFILE_NOTEXIST

DescriptionPatch file not exist. The alarm is generated when the equipment detects that the patch file doesnot exist when it runs the patch file again.



3-211

Attribute



ParametersNone

Impact on the SystemThe loaded patch cannot work normally. The problem to be solved by the patch remains in thesystem.

Possible CausesIf 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


3.2.100 PATH_VERIFY_ALM

DescriptionConsistency verification failure between the logical path dual-end configuration and the physicalpath fiber connection. That is, the 1:N optical path protection group checks the consistencybetween the logical path configuration and the physical path fiber connection. The alarm isgenerated when inconsistency is detected.

Attribute


Major Process alarm

3 Alarm Processing




Issue 08 (2011-10-30)

Parameters


Parameter 1 Indicates the protection group ID. For example, 0x01 indicates the protectiongroup 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 (N≤8) 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 twoends of the 1:N (N≤8) optical path protection are inconsistent.

Procedure

Step 1 Check the configuration of the 1:N (N≤8) optical path protection at the local end and theopposite 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 (N≤8) optical path protection. Ensure thatthe 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 surethat 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 boarddetects that PDU1 or PDU2 is offline.




3-213

Attribute



Parameters



Parameter 1 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 Causesl A PDU is offline.l The PMU board detection is incorrect.l A PDU is faulty.

Procedure

Step 1 Check whether the PDU that the alarm indicates is correctly installed or not. If not, see the PowerBox 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 If the status of the PDU indicators is abnormal, the PDU might be faulty. Replace the faulty

PDU. For details, see the Troubleshooting.l 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) staysoff.

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.102 PM_BIP8_SD

Description

BIP in the PM section of the ODU layer degrades. The alarm is generated when the number ofBIP8 bit errors of the PM section on the optical channel data unit layer exceeds the degradethreshold.


Attribute


Major Service alarm

Parameters






The bit errors are generated in the service signals of the system, which influences the systemquality.

Possible Causesl 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.


l The system performance declines. For example, the optical signal to noise ratio (OSNR)is excessively low, or dispersion or non-linearity occurs.





3-215

Procedure

Step 1 For the OTU board whose WDM side supports the OTN services, check on the T2000 whetherthe input signals on the WDM side have a great amount of BIP8 bit errors of the PM section. Ifyes, 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 theT2000. 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 alarmfor 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. Fordetails, 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 ofthe PM section is not consistent with the TTI value to receive.


Attribute



Parameters




3 Alarm Processing




Issue 08 (2011-10-30)



Impact on the SystemThe alarm has no impact on the system.

Possible Causesl The TTI bytes of the PM section to receive by the board at the local station is incorrectly

configured.l The TTI bytes of the PM section to be transmitted by the board in the upstream station is

incorrectly configured.l The fiber is incorrectly connected.l 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 localstation is consistent with that to be transmitted by the OTU in the opposite station. If not, set theTTI 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 engineeringfiber connection diagram. If not, connect the fiber again according to the fiber connectiondiagram.

Step 3 If the alarm persists, bit errors may be generated in transmission. Clear it as the PM_BIP8_SDalarm for troubleshooting.

----End

Related InformationThe alarm is used for monitoring the PM section of the OTN.

3.2.104 PORTSWITCH_FAIL

DescriptionOptical switch switching failure. This alarm is generated when the board detects that the opticalswitch inside the board fails to switch.




3-217

Attribute



Parameters






When the MCA board reports this alarm, the spectrum analysis data at optical ports cannot bequeried.

Possible Causes


Procedure

Step 1 Perform a cold reset on the faulty board by using the T2000 or remove the faulty board and insertit 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.


----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.105 POWER_DIFF_OVER

Description

Power difference between optical monitoring active and standby crossed the threshold. Thisalarm is generated when the optical power difference of signals in the active and standbysupervisory channels exceeds the threshold.

Attribute



Parameters



Parameter 1 The optical power of one optical port is lower than that of the other opticalport in the same group, and the difference between the optical power ofboth 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 thanthat of optical port 2.


Optical ports 3 and 4 are in the same group.



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 thereceived services would be affected.



3-219

Possible Causesl 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.

l The optical power difference of signals in the active and standby channels when the boardat the opposite end transmits signals is too large.

l 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 standbychannels 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 thefaulty 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. Thatis, the 1:N optical path protection group checks the consistency of the path priority configurationbetween the two ends. The alarm is generated when inconsistency is detected.

Attribute


Major Process alarm

Parameters


Parameter 1 Indicates the protection group ID. For example, 0x01 indicates the protectiongroup 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 Alarm Processing




Issue 08 (2011-10-30)


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.

Impact on the SystemThe 1:N (N≤8) optical path protection may fail, and thus the services are not protected, or evenare interrupted.

Possible CausesThe path priority configuration of the stations at the two ends of the 1:N optical path protectionis 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 surethat the check succeeds and the configuration at the two ends is consistent.

----End


3.2.107 PRBS_LSS

DescriptionLoss of PRBS (Pseudo-Random Binary Sequence) signal. The alarm is generated when theboard, on which the PRBS bit error test is started, does not receive the PRBS signals from thelocal board.

Attribute






3-221






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 notreceive 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 thelocal board.

l If the alarm is cleared, the board is normal. Refer to Step 2 to check the link.

l If the alarm persists, the board is faulty. Replace the board. For details, see the PartsReplacement.

Step 2 Check the link and make sure that the link under PRBS test is a loop. If the alarm persists, performa loopback on each point of the link. Find out the abnormal point in the link, and remove thefault.

----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 biascurrent of the optical amplifier unit exceeds the threshold.

3 Alarm Processing




Issue 08 (2011-10-30)

Attribute



Parameters







The pump laser may be aged. Report of this alarm has no impact on the services. However, ifno measure is taken, the output optical power of the board will be affected in a period of time.This affects services.

Possible Causesl The too high or too low ambient temperature affects the laser.


Procedure

Step 1 Check whether the ambient temperature is normal. If not so, adjust the ambient temperature ofthe 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 theTroubleshooting.

Step 3 If the alarm persists, you can remove and reinsert the faulty board if it does not affect services.


----End



3-223

Related Information

None

3.2.109 PUM_TEM_ALM

Description

Working temperature of the pump laser exceeds the threshold. This alarm is generated when thepump laser operating temperature of the optical amplifier unit exceeds the threshold.

Attribute



Parameters







The pump laser may be aged. Report of this alarm has no impact on the services. However, ifno measure is taken, the output optical power of the board will be affected in a period of time.This affects services.

Possible Causesl The ambient temperature is too high or too low.

l The cooling system of the pump laser is damaged.

l The pump laser has excessive current.

3 Alarm Processing




Issue 08 (2011-10-30)

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.


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


Attribute



Parameters



Parameter 1 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.




3-225


The power supply reliability of the system decreases. The active power supply of the board failsand the power supply of the standby power supply board (PBU) is used. Clear the fault of thepower 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.


----End

Related Information

None

3.2.111 PWR_MAJ_ALM

Description

Abnormal power supply (severe overload or shortage). The alarm is generated when the voltageof the input power supply is excessively low or too high.

Attribute



Parameters


Parameter 1 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 Alarm Processing




Issue 08 (2011-10-30)


The NE might be abnormally running, which leads to the service interruption.

Possible Causesl The voltage of the input power supply is excessively low.

l The voltage of the input power supply is too high.

l There is no input voltage in the subrack.

l The PGND of the subrack and BGND of the power supply are not co-ground.

l The SCC is faulty.

Procedure

Step 1 Check whether the input power supply is correctly connected to the cabinet and subrack. If theinput power supply is not correctly connected to the equipment, rectify the fault. For details, seethe Installation Guide.

Step 2 If the alarm persists, check whether the voltage of the input power supply is normal. If not, rectifythe 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 theT2000. If the voltage of the two power supplies are 79.6 V, it indicates that the PGND of thesubrack and BGND of the power supply may be not co-ground. Make sure the PGND and BGNDare 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 theinput power supply voltage is insufficient or excessive.


Attribute


Minor Environment alarm



3-227

Parameters



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, adjustor 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 boarddetects that the power module temperature crosses the upper threshold.

3 Alarm Processing




Issue 08 (2011-10-30)

Attribute


Critical Equipment

Parameters

Parameters Description

Parameter 1 Indicates the input power supply ID. For example, 0x01 denotes power supply1.


The board in the subrack might report an alarm against temperature and unstably operates.

Possible Causesl The power module is faulty.

l The fan is faulty.

l 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 isoverhigh, condition it to a proper degree.


----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 extractedfrom received signals.




3-229

Attribute



Parameters






Carried service at this port is interrupted.

Possible Causesl The link is abnormal and the board cannot normally extract clock signals.

l The setting of board clock tracing is incorrect.


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 entirenetwork 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




Issue 08 (2011-10-30)

3.2.115 REAR_BD_OFFLINE

Description

Offline of DPFU board. The alarm is generated when the rear board is offline.

Attribute



Parameters



Parameter 1 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 The value is always 0xff 0xff. These two parameters are reserved.

Parameters 4 and 5 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 If no corresponding board exists, insert the corresponding board.l If the corresponding board exists, check whether the board is well inserted. If not, remove

and then insert the board again.



3-231


----End

Related Information

None

3.2.116 RELAY_ALARM

Description

PMU relay alarm. The alarm is generated when the equipment for external alarm input has anyalarm.

Attribute



Parameters



Parameter 1 The housekeeping number where the alarm is generated. For example, 0x01–0x0f respectively stand for the 1–16 alarm inputs.


The equipment for external alarm input might be running abnormally.

Possible Causesl The trigger condition for housekeeping is incorrectly configured.

l 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 alarminput is correctly configured.

3 Alarm Processing




Issue 08 (2011-10-30)

Step 2 Check whether the housekeeping setting of the client-side equipment is the same as that of theequipment at the local station. If not, modify the housekeeping setting of the client-sideequipment or the equipment at the local station.

Step 3 Check whether the external equipment for alarm input is normally running. If not, remove thefault 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 signalsdegrade.


Attribute



Parameters






The QoS of the service signals is affected. In a serious situation, the services are interrupted.



3-233

Possible Causesl The client side of the OTU at the opposite end has alarm such as B1_EXC.l 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 procedureof handling B1_EXC to handle the alarm.

Step 2 If the alarm persists, check whether demultiplexed client signals on the WDM side of the OTUat the local end have the B1_EXC alarm. If yes, see the procedure of handling B1_EXC to handlethe 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 theupper threshold of the return loss alarm.

Attribute



Parameters





3 Alarm Processing




Issue 08 (2011-10-30)


This alarm is generated in case of a fiber connection error. When this alarm is generated, servicesmay be interrupted.

Possible Causesl The fiber near the Raman board is broken.l The fiber near the Raman board is over-bent or pressed.l The connector of the fiber near the Raman board is unclean.l 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 whetherthe 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. Ifyes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it bymeans 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 thelower threshold of the return loss alarm.

Attribute



Parameters




3-235





This alarm is generated in case of a fiber connection error. When this alarm is generated, servicesmay be interrupted.

Possible Causesl The fiber near the Raman board is broken.

l The fiber near the Raman board is over-bent or pressed.

l The connector of the fiber near the Raman board is unclean.

l 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 whetherthe 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. Ifyes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it bymeans 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 ofalignment error packets detected by the Ethernet port crosses the upper threshold.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute


Minor Service alarm

Parameters






The Ethernet QoS is degraded.

Possible Causesl The data equipment on the client side is faulty. As a result, the data sent includes a great

amount of alignment error packets.

l The too high or too low input optical power leads to the generation of alignment errorpackets at the receive end.

l The optical interface modes (and the fiber modes) of the two connected Ethernet ports arenot consistent.

l The fiber is damaged or the fiber connector is dirty.


Procedure

Step 1 Check whether the input optical power of the Ethernet port is within the normal range by usingthe T2000. For the optical power specifications of the specific board, see the ProductDescription. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH orIN_PWR_LOW alarm for troubleshooting.

Step 2 If the alarm persists, check whether the optical interface mode (and the fiber mode) of the twoconnected Ethernet ports are consistent. If they are not consistent, replace the fiber or board toensure that the optical interface mode and the fiber type of the two Ethernet ports are consistent.



3-237

Step 3 If the alarm persists, check whether the data equipment on the client side is normal. If it isabnormal, 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 thecorresponding optical interface of the OTU. If it is dirty, clean or replace the fiber connector.For details, see the Troubleshooting.


----End


3.2.121 RMON_ALM_DROPEVENT_OVER

DescriptionStatistics of drop packet events is over the upper threshold. The alarm is generated when thenumber of the drop packets crosses the upper threshold due to the cache memory overflow ofthe Ethernet port.


Attribute


Minor Service alarm





Impact on the SystemThe Ethernet QoS is degraded.

3 Alarm Processing




Issue 08 (2011-10-30)

Possible Causes

The board is faulty.

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 numberof CRC error packets detected by the Ethernet port crosses the upper threshold.


Attribute


Minor Service alarm

Parameters









3-239

Possible Causesl The data equipment on the client side is faulty. As a result, the data sent includes a great

amount of CRC error packets.l The too high or too low input optical power leads to the generation of CRC error packets

at the receive end.l The optical interface modes (and the fiber modes) of the two connected Ethernet ports are

not consistent.l The fiber is damaged or the fiber connector is dirty.l 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 usingthe T2000. For the optical power specifications of the specific board, see the ProductDescription. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH orIN_PWR_LOW alarm for troubleshooting.

Step 2 If the alarm persists, check whether the optical interface mode (and the fiber mode) of the twoconnected Ethernet ports are consistent. If they are not consistent, replace the fiber or board toensure 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 isabnormal, 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 thecorresponding optical interface of the OTU. If it is dirty, clean or replace the fiber connector.For details, see the Troubleshooting.


----End

Related InformationThe abnormal data packets include:

l ethunder, the excessively short packet that is less than 64 octets.l ethover, excessively long packet whose length exceeds the set maximum length.l ethfrg, fragment that is less than 64 octets and with the CRC error packets.l ethjab, ambiguous packet that is excessively long and with CRC error packets.l ethfcs, CRC error packets.

3.2.123 RMON_ALM_INBADOCTS_OVER

DescriptionStatistics of receiving bad packets is over the upper threshold. The alarm is generated when theoctet number of bad packets detected by the Ethernet port of the board crosses the upperthreshold.


3 Alarm Processing




Issue 08 (2011-10-30)

Attribute


Minor Service alarm

Parameters







Possible Causesl The data equipment on the client side sends the abnormal data packets.

l The abnormal link between the client side and the Ethernet port on the board leads to theerror of the data packets in transmission.

l 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 thefault 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 theboard is normal.

1. Check whether the optical interface mode (and the fiber mode) of the two connectedEthernet ports are consistent. If they are not consistent, replace the fiber or board to ensurethat the optical interface mode and the fiber type of the two Ethernet ports are consistent.

2. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,see the Troubleshooting.

3. Check whether the transmitting/receive optical power of the two connected Ethernet portsis within the normal range. For the optical power specifications of the specific board, see



3-241

the Product Description. If the optical power is abnormal, take the alarm as theIN_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

The abnormal data packets include:

l ethunder, the excessively short packet that is less than 64 octets.

l ethover, excessively long packet whose length exceeds the set maximum length.

l ethfrg, fragment that is less than 64 octets and with the CRC error packets.

l ethjab, ambiguous packet that is excessively long and with CRC error packets.

l ethfcs, CRC error packets.

3.2.124 RMON_ALM_OUTBADOCTS_OVER

Description

Statistics of receiving bad packets is over the upper threshold. The alarm is generated when thenumber of bad packets detected by the Ethernet port of the board crosses the upper threshold.


Attribute


Minor Service alarm

Parameters





3 Alarm Processing




Issue 08 (2011-10-30)



Possible Causesl The signals received on the WDM side of the board have the B1 or B2 bit errors.

l 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, handlethe alarm by referring to the handling procedure of the B1_EXC or B2_EXC alarm.


----End

Related Information

The abnormal data packets include:

l ethunder, the excessively short packet that is less than 64 octets.

l ethover, excessively long packet whose length exceeds the set maximum length.

l ethfrg, fragment that is less than 64 octets and with the CRC error packets.

l ethjab, ambiguous packet that is excessively long and with CRC error packets.

l ethfcs, CRC error packets.

3.2.125 S1_SYN_CHANGE

Description

Synchronous source changed in S1 mode.


Attribute



Parameters




3-243




Impact on the SystemThe switching performs to the working clock source of the board, which influence the userservices.

Possible Causesl The fiber connection is faulty.l 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 onthe upstream station.

Step 2 Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details, see theTroubleshooting.


----End


3.2.126 SCC_LOC

DescriptionSCC loss of clock. The alarm is generated when the OSC board detects that the clock sourcesent by the SCC board is missing.

Attribute




3 Alarm Processing




Issue 08 (2011-10-30)






The NE is out of control and the optical supervisory channel is interrupted.

Possible Causesl The board is faulty.

l The SCC board is faulty.

l The alarm is generated during the cold reset of the SCC board. The alarm automaticallydisappears after the cold reset is complete.

Procedure

Step 1 Query the reset record of the SCC board.

l If the time when the alarm disappears is consistent with the time that the SCC is reset, thealarm might be caused by resetting the SCC. There is no need to handle the alarm.

l 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 PartsReplacement.

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 directionof the services, indicating the detected signal failure.




3-245

Attribute







Impact on the SystemService carried by the board is interrupted.

Possible Causesl 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 theSM_BDI signals and transparently sends the SM_BDI signals to the station B (oppositestation) at the same time. The WDM side of the OTU in the station B reports the SM_BDIalarm after detecting the SM_BDI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theSM_BDI alarm

The client signals containthe SM_BDI signal

WDMside

Clientside


l The R_LOS, OTU_LOF or OTU_AIS alarm is generated when the WDM side of the OTUin the opposite station receives the signals at the local station.

3 Alarm Processing




Issue 08 (2011-10-30)

As shown in the following figure: The WDM side of the OTU in the station B (oppositestation) detects and reports the R_LOS, OTU_LOF or OTU_AIS alarm, it inserts theSM_BDI signals back to the local station. The WDM side of the OTU in the station Areports the SM_BDI alarm after detecting the SM_BDI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects and reports theR_LOS, OTU_LOF,

OTU_AIS alarm


Insert the SM_BDIsignal back

l The board at the local station is faulty.l 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 thestation 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 afterdetecting the SM_BDI signals.

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside


Insert the SM_BDIsignal by mistake

Procedure

Step 1 If the client side reports the SM_BDI alarm, check whether the client-side equipment connectedto the OTU is faulty according to the related manuals. If yes, remove the fault of the client-sideequipment 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 thefaulty 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.



3-247

Step 4 If the WDM side reports the SM_BDI alarm, check whether the R_LOS, OTU_LOF orOTU_AIS alarm is generated when the OTU in the opposite station receives the signals at thelocal station. If yes, handle the alarm by referring to the corresponding handling procedure.


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 thenumber of BIP8 bit errors of the SM section in the optical channel data unit layer exceeds thedegraded threshold.


Attribute


Major Service alarm

Parameters





3 Alarm Processing




Issue 08 (2011-10-30)


The service signals borne by the wavelength generate a great amount of bit errors. The signalsare degraded.

Possible Causesl 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 theSM section.


l The system performance declines. For example, the optical signal to noise ratio (OSNR)is excessively low, or dispersion or non-linearity occurs.



Procedure

Step 1 For the OTU board whose client side supports the OTN services, check on the T2000 whetherthe input signals on the client side has a great amount of BIP8 bit errors of the PM section. Ifyes, 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 normalrange by using the T2000. For the optical power specifications of the specific board, see theProduct Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH orIN_PWR_LOW alarm for troubleshooting.

Step 3 If the alarm persists, see the description on bit error fault handling in the Troubleshooting.


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, itinserts the SM_IAE flag to the downstream board. The alarm is generated when the downstreamboard detects that OTN frames received contains the IAE flag.




3-249

Attribute







Impact on the SystemGenerally the services are not affected. If the slip frame problem is severe, the bit errors mightoccur to the services.

Possible Causesl 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 thefollowing figure.The client-side input signals of the OTU in station A (local station) contains SM_IAEsignals. The OTU in station A reports the SM_IAE alarm on the client side after detectingthe SM_IAE signals.

OTU

OTU

Clientside

WDMside

Station A Station B

Detects and reports theSM_IAE alarm

The client signals containthe SM_IAE signal

WDMside

Clientside

l The slip frame occurs to the client-side signals of the OTU in the opposite station, insertSM_IAE signals to the local station, as shown in the following figure.

3 Alarm Processing




Issue 08 (2011-10-30)

OTU

OTU

Clientside

WDMside

Station A Station B

WDMside

Clientside

Detects and reports theSM_IAE alarm

Insert the SM_IAEsignal

The client signals havethe slip frame

l The board at the local station is faulty.l The board in the upstream station is faulty.

ProcedureStep 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 therelated manuals.


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 signalssent by client-side equipment connected to the OTU. If yes, remove the fault of the client-sideequipment 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 theT2000 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 theT2000 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


3.2.130 SPEED_OVER

DescriptionData rate exceeding the set limits. The alarm is generated when the service rate of the boardexceeds the set threshold value.



3-251


Attribute



Parameters






The services are not available.

Possible Causesl The carried service type is incorrect.


Procedure

Step 1 On the T2000, readjust the client service bearer rate to a value that is greater than the currentservice rate.


----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.131 SUM_INPWR_HI

DescriptionInput optical power is too high. The alarm is generated when the input optical power of themultiplexed signals exceeds the threshold.


Attribute







Impact on the SystemThe 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 Causesl 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 properattenuation is not added.

l The output optical power of the board in the upstream station or opposite station is too high.l The board at the local station is faulty.

Procedure

Step 1 Check whether the input optical power of the input interface of the board at the local station iswithin the normal range by using an optical power meter. For the optical power indexed of the



3-253

specific board, see the Product Description. If the power is not within the normal range, addproper 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 stationsis within the normal range by using the T2000. For the optical power specifications of the specificboard, see the Product Description. If the input optical power of the board at the local station istoo 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 checkwhether the corresponding input and output optical power of each upstream station are withinthe normal range.

l If the input and output optical power of the board in the upstream station are not within thenormal range, adjust the input optical power to be within the normal range. For the opticalpower indexed of the specific board, see the Product Description.

l If the input optical power of the board in the upstream station is within the normal rangebut 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.


----End

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 ofmultiplexer unit is higher than the upper threshold.

Attribute



Parameters




3 Alarm Processing




Issue 08 (2011-10-30)



Impact on the SystemThe alarm has an effect on the system services. The input optical power of the board in thedownstream station might be too high, which leads to that the bit errors occur to the services orthe services might be interrupted. The receive module of the OTU in the downstream stationmight be damaged.

Possible Causesl The optical power of the accessed signals are too high and no proper attenuation is added.l The internal attenuation of the board is incorrectly adjusted.l The board hardware is faulty.

Procedure

Step 1 Check whether the input optical power of the input interface of the board is within the normalrange by using an optical power meter. For the optical power indexed of the specific board, seethe Product Description. If the power is not within the normal range, add proper attenuation byplacing 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 thecorresponding channel to a proper value on the T2000.


----End


3.2.133 SWDL_ACTIVATED_TIMEOUT

DescriptionActivation time out. During loading of the software packet, the alarm is generated when theoperation is not committed in thirty minutes after activation operation.

Attribute





3-255

Parameters

None


The services are not affected.

Possible Causes

The operation is not committed in thirty minutes after activation operation during loading of thesoftware packet.

Procedure

Step 1 Query on the T2000 whether the activation operation is complete. If yes, proceed with the commitoperation.

----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 checkswhether the board software matches the NE software or not. If not, the SCC unit upgrades the board softwareof the new board.

Attribute


Minor Process alarm

Parameters

None


The SCC unit cannot automatically update the software of the board that is newly inserted. Ifthe software of the new board mismatches the NE software, some functions of the NE mayoperate abnormally. .

3 Alarm Processing




Issue 08 (2011-10-30)

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 boardsoftware of each board matches the NE software after the NE starts up upon a power failure, theSCC unit is replaced, or a cold reset is performed on the SCC unit. The alarm is generated whenthe board software of a board mismatches the NE software. It indicates that the board softwaremismatches the NE software.

Attribute



Parameters

None

Impact on the Systeml When the alarm is generated, the automatic match function for packet loading is disabled

l The software version of the unit is inconsistent with that of the SCC unit. Some functionsof the NE may operate abnormally.

Possible Causesl 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.

l The SCC unit is replaced, and the software package of the new SCC is inconsistent withthe software version of units.



3-257

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


3.2.136 SWDL_COMMIT_FAIL

DescriptionCommit failure alarm. During loading of the software packet, the alarm is generated when thecommitment operation is failure.

Attribute


Minor Process alarm

ParametersNone

Impact on the SystemThe packet loading would fail and the upgrade of the software version fails.

Possible CausesDuring the packet loading, the dual-partition board fails in copying the new software from onepartition to the other.

NOTE

The dual-partition board has two file systems. The two partitions are of mutual backup. In normal status, everyfile is saved in both two partitions.

Procedure


----End


3 Alarm Processing




Issue 08 (2011-10-30)

3.2.137 SWDL_INPROCESS

Description

NE is loading package. This alarm is generated when the NE is performing packet loading.

Attribute


Minor Process alarm

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


----End

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 thata file in a partition of the SCC software package is lost and the file cannot be restored from therelated file in another partition. Next time when the SCC checks the software package and findsthe 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.



3-259

Attribute



ParametersNone

Impact on the SystemBecause a file in the SCC software package is lost, there might be impact on the normal operationof some functions of the NE.

Possible CausesThe file is lost and irrecoverable.

Procedure


----End


3.2.139 SWDL_PKG_NOBDSOFT

DescriptionNo 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 softwarepackage. 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 actualrequirements.

Attribute


Minor Process alarm

ParametersNone

3 Alarm Processing




Issue 08 (2011-10-30)


The software version of the unit is inconsistent with that of the SCC unit. Some functions of theNE may operate abnormally.

Possible Causes

The user uses the customized software package, in which no software for the normal board isfound.

Procedure


----End

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 softwareversion information.

Attribute


Minor Process alarm

Parameters

None


The software versions on the NE are inconsistent. Some functions of the NE may operateabnormally.

Possible Causes

The file of the software packet is faulty, and the software version information about the softwarepacket is not consistent with the actual software version information.



3-261

Procedure


----End

Related Information

None

3.2.141 SWDL_ROLLBACK_FAIL

Description

NE rollback failed. Some board rollback fails when the NE performs rollback, the alarm isgenerated.

Attribute


Minor Process alarm

Parameters

None


The NE rollback fails. The board software cannot recover to the version before the packetloading. and the board software version and the NE software version may mismatch. Somefunctions of the NE may operate abnormally.

Possible Causes

Some board rollback fails when the NE performs rollback.

Procedure


----End

Related Information

None

3 Alarm Processing




Issue 08 (2011-10-30)

3.2.142 SYNC_C_LOS

Description

Loss of clock source. This alarm is generated when the board detect inexistence ofsynchronization source with higher priority than the current synchronization source.

Attribute


Warning Equipment alarm

Parameters



Parameter 1 Indicates the clock source type. For example, 0xf0 denotes the external clocksource; 0xf1 denotes the internal clock source.

Parameter 2 Indicates the clock source ID. For example, when parameter 1 is 0xf0, 0x01denotes external clock source 1; when parameter 1 is 0xf1, 0x01 denotes internalclock source 1.


This alarm does not interrupt services or cause bit errors.

Possible Causesl 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.



3-263

Procedure

Step 1 Check whether the fiber connection is correct according to the engineering fiber connectiondiagram. The input optical signals in different wavelengths should be accessed to correspondinginput optical interfaces of the board. If the fiber connection is incorrect, correct it according tothe diagram.

Step 2 Check whether the external clock source is normal. If not, remove the clock source fault first.


----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 whenthe session or the connection between an NE and the syslog server is abnormal.

Attribute



Parameters


Name Meaning

Parameters 1 to 4 Indicates the address of the syslog server.

Parameter 5 Indicates the type of the fault that causes the alarm. 0x0a indicates that theconnection 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 syslogserver.

3 Alarm Processing




Issue 08 (2011-10-30)

Possible CausesIn the TCP mode, the connection between an NE and the syslog server or the session betweenservers 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


3.2.144 T_LOC

DescriptionTransmit loss of clock. The alarm is generated when the clock signals cannot be extracted onthe line side at the transmit end.


Attribute







Impact on the SystemCarried service at this port is interrupted.



3-265

Possible Causesl The client side does not access services and the laser on the WDM side is forced to emit

light.l 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, seethe Troubleshooting.


----End


3.2.145 T_SLIP

DescriptionTransmitted side frame slipping. The alarm is generated when the phase deviation occurs to thetransmitted service frames of the board.

Attribute







3 Alarm Processing




Issue 08 (2011-10-30)

Impact on the SystemBit errors occur in the client services, which can cause service break when it gets severe.

Possible CausesThe clock signals are not synchronous.

Procedure

Step 1 Perform a cold reset on the faulty board through the T2000 or remove the faulty board. Fordetails, see the Troubleshooting.


----End


3.2.146 TEM_HA

DescriptionLaser temperature is too high. This alarm is generated when the laser temperature is higher thanthe laser temperature maximum.


Attribute



Parameters



Impact on the SystemThis has impact on the working wavelengths of the optical module and affects the client services.

Possible Causesl Working temperature of the board is too high.l The laser is faulty.



3-267

l The module performance detection circuit is faulty.

Procedure

Step 1 Check the board ambient temperature and ventilation of the equipment room. If the boardambient temperature is too high, cool the equipment room with cooling devices, such as the airconditioner.


----End

Related Information

None

3.2.147 TEM_LA

Description

Laser temperature is excessively low. his alarm is generated when the laser temperature is lowerthan the laser temperature minimum.


Attribute



Parameters




This has impact on the working wavelengths of the optical module and affects the client services.

Possible Causesl Working temperature of the board is excessively low.

l The laser is faulty.

l The module performance detection circuit is faulty.

3 Alarm Processing




Issue 08 (2011-10-30)

Procedure

Step 1 Check the board ambient temperature. If it is excessively low, increase it.


----End


3.2.148 TEMP_ALARM

DescriptionThe temperature threshold crossing alarm. This alarm is generated when the board ambienttemperature crosses the board temperature threshold.


Attribute



Parameters


Parameter 1 Indicates whether the temperature crosses the upper or lower threshold. Forexample,

l 0x01 denotes that the temperature crosses the upper threshold.l 0x02 denotes that the temperature crosses the lower threshold.

Impact on the SystemServices borne on the board might be affected.

Possible Causesl The board ambient temperature is overhigh.l The board ambient temperature is overlow.l The board is faulty.

Procedure

Step 1 Check whether the fan runs normally and whether the air duct is blocked because the dust filterof the fan is not cleaned in a long period.



3-269


----End

Related Information

None

3.2.149 TEMP_OVER

Description

Working temperature over threshold. This alarm is generated when the board workingtemperature exceeds the threshold.


Attribute



Parameters



Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upperthreshold is exceeded and 0x02 indicates the lower threshold is exceeded.

Impact on the Systeml This alarm affects the system heat dissipation.

l In corresponding service boards, this alarm affects normal working of service chips andcauses bit errors.

Possible Causesl The ambient temperature is too high.

l The cooling devices are abnormal.


3 Alarm Processing




Issue 08 (2011-10-30)

Procedure

Step 1 Check the board ambient temperature in the NM system and check the ambient temperature ofthe equipment room. If the equipment is too hot, check the cooling device and make it worknormally.

Step 2 If the alarm persists, check whether the subrack fan is normal. If it stops working, replace it. Fordetails, 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 failureof the PFU or DPFU module.

Attribute



Parameters



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 orDPFU.



3-271


The lightning protection performance of the system is degraded. If the equipment is attacked bythe strong current (for example, strong lightning stroke), the board on the subrack may beunavailable. As a result, the services are interrupted.

Possible Causesl 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, thelightning protection component on the PFU or DPFU board is unavailable and the circuitis broke due to the automatic protection of the fuse, the PMU detects the failure and reportsthis alarm.


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 theequipment 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 clockof the board is lost.


Attribute



Parameters


3 Alarm Processing




Issue 08 (2011-10-30)





Carried service at this port is interrupted.

Possible Causesl The client side does not access services and the laser on the WDM side is forced to emit

light.l The client side normally accesses services but the transmitted signals do not have clock

signals.l 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, seethe Troubleshooting.


----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 isabnormal.


Attribute





3-273

Parameters



Parameter 1 The value is always 0x01. There is no concept of optical ports.



The abnormal crystal oscillator of the board leads to that the board cannot work normally, whichinfluences the user services.

Possible Causes

The board is faulty.

Procedure

Step 1 Perform a cold reset on the faulty board through the T2000. For details, see theTroubleshooting.

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 thewritten value of the register are not consistent.

Attribute



3 Alarm Processing




Issue 08 (2011-10-30)



Parameter 1 Indicates the IDs of the board register. For example, 0x01-0x09 indicates the IDsof the faulty chips that are of different types.

Impact on the SystemThe board cannot work normally. In this case, the services may not be received or transmittedproperly. In addition, the board may fail to query the current performance value.


ProcedureStep 1 Perform a warm reset on the faulty board on the T2000. For details, see the Troubleshooting.


----End


3.2.154 WAVE_LEN_LOCK_FAIL

DescriptionWavelength locking failure alarm. The alarm is generated when the wavelength locker cannotlock the wavelength due to the severe wavelength wander.


Attribute



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in the



3-275

following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.


Parameter 1 The optical port where the alarm is generated. The value is always 0x01.

Impact on the SystemThe services borne by the wavelength are degraded or interrupted, which might influence theservices borne by the adjacent wavelengths.


Procedure

Step 1 Perform a cold reset on the faulty board through the T2000 or reseat the faulty board. For details,see the Troubleshooting.


----End


3 Alarm Processing




Issue 08 (2011-10-30)

4 Performance Event List

About This Chapter

This chapter lists the names, description and relevant boards of the performance event inalphabetical order and lists the performance event of every board.

4.1 Product Performance Event ListLists the different types of performance event.

4.2 Board Performance Event ListThis section list the performance event of every board.

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference 4 Performance Event List


4-1

4.1 Product Performance Event ListLists the different types of performance event.

4.1.1 Performance Event List of Check and Error CorrectionName Description

CRC4BBE CRC4 Background Block Error

CRC4CSES CRC4 Consecutive Severely Errored Second

CRC4ES CRC4 Errored Second

CRC4FEBBE CRC4 Far End Background Block Error

CRC4FECSES CRC4 Far End Consecutive Severely ErroredSecond

CRC4FEES CRC4 Far End Errored Second

CRC4FESES CRC4 Far End Severely Errored Second

CRC4SES CRC4 Severely Errored Second

CRC4UAS CRC4 Unavailable Second

FEC_AFT_COR_ER After FEC Correct Errored Rate

FEC_BEF_COR_ER Before FEC Correct Errored Rate

FEC_COR_0BIT_CNT Forward Error Correction - Corrected 0 Bit Count

FEC_COR_1BIT_CNT Forward Error Correction - Corrected 1 Bit Count

FEC_COR_BYTE_CNT Forward Error Correction - Corrected Byte Count

FEC_UNCOR_BLOCK_CNT

Forward Error Correction - Uncorrected BlockCount

FEC_AFT_COR_ERAVR

After FEC Correct Average Errored Rate inmonitor period

FEC_BEF_COR_ERAVR

Before FEC Correct Average Errored Rate inmonitor period

ODU_PM_BBE ODU PM Section Background Block Error

ODU_PM_BBER ODU PM Section Ratio of Background BlockError

ODU_PM_BIP8 ODU PM Section BIP8

ODU_PM_FEBBE ODU PM Section Far End Background BlockError





Issue 08 (2011-10-30)

Name Description

ODU_PM_FEBBER ODU PM Section Ratio of Far End BackgroundBlock Error

ODU_PM_FEES ODU PM Section Far End Errored Second

ODU_PM_FESES ODU PM Section Far End Severely ErroredSecond

ODU_PM_FESESR ODU PM Section Ratio of Far End SeverelyErrored Second

ODU_PM_FEUAS ODU PM Section Unavailable Second

ODU_PM_ES ODU PM Section Errored Second

ODU_PM_SES ODU PM Section Severely Errored Second

ODU_PM_SESR ODU PM Section Ratio of Severely ErroredSecond

ODU_PM_UAS ODU PM Section Unavailable Second

OTU_BBE OTU Background Block Error

OTU_BBER OTU Ratio of Background Block Error

OTU_BIAES OTU SM Section Backward Incoming AlignmentErrored Second

OTU_SM_BIP8 OTU SM Section BIP8

OTU_ES OTU Errored Second

OTU_FEBBE OTU SM Section Far End Background Block Error

OTU_FEBBER OTU SM Section Ratio of Far End BackgroundBlock Error

OTU_FEES OTU SM Section Far End Errored Second

OTU_FESES OTU SM Section Far End Severely ErroredSecond

OTU_FESESR OTU SM Section Ratio of Far End SeverelyErrored Second

OTU_FEUAS OTU SM Section Unavailable Second

OTU_IAES OTU SM Section Incoming Alignment ErroredSecond.

OTU_SES OTU Severely Errored Second

OTU_SESR OTU Ratio of Severely Errored Second

OTU_UAS OTU Unavailable Second

ODU_TCMn_BBE ODU TCMn Section Background Block Error



4-3

Name Description

ODU_TCMn_BBER ODU TCMn Section Ratio of Background BlockError

ODU_TCMn_BIAES ODU TCMn Section Backward IncomingAlignment Errored Second

ODU_TCMn_ES ODU TCMn Section Errored Second

ODU_TCMn_FEBBE ODU TCMn Section Far End Background BlockError

ODU_TCMn_FEBBER ODU TCMn Section Ratio of Far End BackgroundBlock Error

ODU_TCMn_FEES ODU TCMn Section Far End Errored Second

ODU_TCMn_FESES ODU TCMn Section Far End Severely ErroredSecond

ODU_TCMn_FESESR ODU TCMn Section Ratio of Far End SeverelyErrored Second

ODU_TCMn_FEUAS ODU TCMn Section Unavailable Second

ODU_TCMn_IAES ODU TCMn Section Incoming Alignment ErroredSecond

ODU_TCMn_SES ODU TCMn Section Severely Errored Second

ODU_TCMn_SESR ODU TCMn Section Ratio of Severely ErroredSecond

ODU_TCMn_UAS ODU TCMn Section Unavailable Second

4.1.2 Performance Event List of Equipment FunctionName Description

BCVCUR Current Pump Laser BackfacetCurrent Value

BCVMAX Maximum Pump Laser BackfacetCurrent Value

BCVMIN Minimum Pump Laser BackfacetCurrent Value

CCVCUR Current Pump Laser CoolingCurrent Value

CCVMAX Maximum Pump Laser CoolingCurrent Value





Issue 08 (2011-10-30)

Name Description

CCVMIN Minimum Pump Laser CoolingCurrent Value

EDF_BOX_TMPCUR Current EDFA Fiber BoxTemperature Value

EDF_BOX_TMPMAX Maximum EDFA Fiber BoxTemperature Value

EDF_BOX_TMPMIN EDFA Fiber Box TemperatureValue

ENVTMPMAX Maximum Board EnvironmentalTemperature Value

ENVTMPMIN Minimum Board EnvironmentalTemperature Value

ENVTMPCUR Current Board EnvironmentalTemperature Value

ICCLCCUR Current Module Cooling CurrentValue

ICCLCMAX Maximum Module Cooling CurrentValue

ICCLCMIN Minimum Module Cooling CurrentValue

ICTMPCUR Current Module Temperature Value

ICTMPMAX Maximum Module TemperatureValue

ICTMPMIN Minimum Module TemperatureValue

LINE_OUT_POWERCUR Current Line Out Optical PowerValue

LINE_OUT_POWERMAX Maximum Line Out Optical PowerValue

LINE_OUT_POWERMIN Minimum Line Out Optical PowerValue

LSOOPCUR Current Output Optical Power Value

LSOOPMAX Maximum Output Optical PowerValue

LSOOPMIN Minimum Output Optical PowerValue

LSIOPCUR Current Input Optical Power Value



4-5

Name Description

LSIOPMAX Maximum Input Optical PowerValue

LSIOPMIN Minimum Input Optical PowerValue

LSTMPCUR Current Laser Temperature Value

LSTMPMAX Maximum Laser Temperature Value

LSTMPMIN Minimum Laser Temperature Value

LSBIASCUR Current Laser Bias Current Value

LSBIASMAX Maximum Laser Bias Current Value

LSBIASMIN Minimum Laser Bias Current Value

LSCLCCUR Current Laser Cooling CurrentValue

LSCLCMAX Maximum Laser Cooling CurrentValue

LSCLCMIN Minimum Laser Cooling CurrentValue

OOPRLCUR Current value of the optical outputpower return loss

OOPRLMAX Maximum value of the optical outputpower return loss within a timeperiod

OOPRLMIN Minimum value of the optical outputpower return loss within a timeperiod

PCLSOPCUR Current Per-channel Laser OutputPower Value

PCLSOPMAX Maximum Per-channel Laser OutputPower Value

PCLSOPMIN Minimum Per-channel Laser OutputPower Value

PCLSSNCUR Current Per-channel OSNR Value

PCLSWLCUR Current Per-channel CentralWavelength Value

PCLSWLMAX Maximum Per-channel CentralWavelength Value

PCLSWLMIN Minimum Per-channel CentralWavelength Value





Issue 08 (2011-10-30)

Name Description

PCLSWLOCUR Current Per-channel CentralWavelength Deviation Value

PCLSWLOMAX Maximum Per-channel CentralWavelength Deviation Value

PCLSWLOMIN Minimum Per-channel CentralWavelength Deviation Value

PMUTMPCUR Current PMU board EnvironmentTemperature Value

PMUTMPMAX Maximum PMU board EnvironmentTemperature Value

PMUTMPMIN Minimum PMU board EnvironmentTemperature Value

PUMPOOPCUR Current Pump Output Optical PowerValue

PUMPOOPMAX Maximum Pump Output OpticalPower Value

PUMPOOPMIN Minimum Pump Output OpticalPower Value

PUMPTMPCUR Current Pump Laser TemperatureValue

PUMPTMPMAX Maximum Pump Laser TemperatureValue

PUMPTMPMIN Minimum Pump Laser TemperatureValue

SUMIOPCUR Current Input Optical Power Value

SUMIOPMAX Maximum Input Optical PowerValue

SUMIOPMIN Minimum Input Optical PowerValue

SUMOOPCUR Current Output Optical Power Value

SUMOOPMAX Maximum Output Optical PowerValue

SUMOOPMIN Minimum Output Optical PowerValue

WCVCUR Current Pump Laser WorkingCurrent Value



4-7

Name Description

WCVMAX Maximum Pump Laser WorkingCurrent Value

WCVMIN Minimum Pump Laser WorkingCurrent Value

4.1.3 Performance Event list of Multiplex Section Bit ErrorName Description

MSBBE MS Background Block Error

MSES MS Errored Second

MSSES MS Severely Errored Second

MSUAS MS Unavailable Second

MSCSES MS Consecutive Severely Errored Second

MSFEES MS Far End Errored Second

MSFESES MS Far End Severely Errored Second

MSFEBBE MS Far End Background Block Error

MSFECSES MS Far End Consecutive Severely Errored Second

4.1.4 Performance Event List of Regenerator Section Bit ErrorName Description

RSBBE RS Background Block Error

RSES RS Errored Second

RSSES RS Severely Errored Second

RSCSES RS Consecutive Severely Errored Second

RSUAS RS Unavailable Second

RSOFS RS Out-of-Frame Second





Issue 08 (2011-10-30)

4.1.5 Performance Event List of Ethernet

Table 4-1 Statistics of Packets with Different Lengths

Name Description

Packets Received (64 Octets inLength)

The total number of packets (including badpackets) received per second that are 64 octetsin length (excluding framing bits but includingFCS octets).

Packets Received (65~127 Octetsin Length)

The total number of packets (including badpackets) received per second that are between 65and 127 octets in length inclusive (excludingframing bits but including FCS octets).

Packets Received (128~255Octets in Length)

The total number of packets (including badpackets) received per second that are between128 and 255 octets in length inclusive(excluding framing bits but including FCSoctets).







Packets Transmitted (64 Octets inLength)

The total number of packets (including badpackets) transmitted per second that are 64octets in length (excluding framing bits butincluding FCS octets).

Packets Transmitted (65~127Octets in Length)

The total number of packets (including badpackets) transmitted per second that are between65 and 127 octets in length inclusive (excludingframing bits but including FCS octets).


The total number of packets (including badpackets) transmitted per second that are between128 and 255 octets in length inclusive(excluding framing bits but including FCSoctets).



4-9

Name Description







Table 4-2 Statistics of Overall Performance

Name Description

Unicast Packets Received The total number of good packets received persecond that are directed to a unicast address.

Multicast Packets Received The total number of good packets received persecond that are directed to a multicast address.Note that this number does not include packetsdirected to the broadcast address.

Broadcast Packets Received The total number of good packets received persecond that are directed to the broadcast address.Note that this does not include multicast packets.

Unicast Packets Transmitted The total number of packets that higher-levelprotocols request to transmit per second, andwhich are not addressed to a multicast orbroadcast address at this sub-layer, includingthose that are discarded or not sent.

Multicast Packets Transmitted The total number of packets that higher-levelprotocols request to transmit per second, andwhich are addressed to a multicast address at thissub-layer, including those that are discarded ornot sent. For a MAC layer protocol, this includesboth Group and Functional addresses.





Issue 08 (2011-10-30)

Name Description

Broadcast Packets Transmitted The total number of packets that higher-levelprotocols request to transmit per second, andwhich are addressed to a broadcast address atthis sub-layer, including those that are discardedor not sent.

Pause Frames Received A count of MAC control frames received persecond on this interface with an opcodeindicating the PAUSE operation.

Pause Frames Transmitted A count of MAC control frames transmitted persecond on this interface with an opcodeindicating the PAUSE operation.

Undersize Packets Received The total number of packets received per secondthat are less than 64 octets in length (excludingframing bits, but including FCS octets) and areotherwise well formed.

Oversize Packets Received The total number of packets received per secondthat are longer than 1518 octets in length(excluding framing bits, but including FCSoctets) and are otherwise well formed.

Fragments The total number of packets received per secondthat are less than 64 octets in length (excludingframing bits but including FCS octets) and hadeither a bad frame check sequence (FCS) withan integral number of octets (FCS Error) or a badFCS with a non-integral number of octets(Alignment Error).

Jabbers The total number of packets received per secondthat are longer than 1518 octets (excludingframing bits, but including FCS octets), and hadeither a bad frame check sequence (FCS) withan integral number of octets (FCS Error) or a badFCS with a non-integral number of octets(Alignment Error).

Good Octets Received The total number of octets of good packetsreceived per second on the network (excludingframing bits but including FCS octets).

Good Octets Transmitted The total number of octets of good packetstransmitted per second on the network(excluding framing bits but including FCSoctets).

Bad Octets Received The total number of octets of bad packetsreceived per second on the network (excludingframing bits but including FCS octets).



4-11

Name Description

Bad Octets Transmitted The total number of octets of bad packetstransmitted per second on the network(excluding framing bits but including FCSoctets).

Table 4-3 Error and Collision

Name Description

Alignment Errors The number of received frames that havealignment errors. An alignment errored framecannot pass the FCS check because the framecontains a non-integer number of bytes.

FCS Errors The count of frames received per second on aparticular interface that are of an integralnumber of octets in length but do not pass theFCS check. This count does not include framesreceived with frame-too-long or frame-too-shorterror.

Packets Received (1519~MTUOctets in Length)

The total number of packets received per secondthat are between 1519 octets and MTU octets inlength.

Packets Transmitted (1519~MTUOctets in Length)

The total number of packets transmitted persecond that are between 1519 octets and MTUoctets in length.

4.2 Board Performance Event ListThis section list the performance event of every board.

4.2.1 D40 Board Performance Event ListENVTMPMAX ICCLCMAX ICTMPMIN

ENVTMPMIN ICCLCMIN SUMIOPCUR

ENVTMPCUR ICTMPCUR SUMIOPMAX

ICCLCCUR ICTMPMAX SUMIOPMIN





Issue 08 (2011-10-30)

4.2.2 DCP Board Performance Event ListENVTMPMAX ENVTMPCUR SUMIOPMAX

ENVTMPMIN SUMIOPCUR SUMIOPMIN

4.2.3 ELOG/ELOGS Board Performance Event ListENVTMPCUR LSTMPMAX OTU_SM_BIP8

ENVTMPMAX LSTMPMIN OTU_UAS

ENVTMPMIN ODU_PM_BBE Packets Received (64 Octets inLength)

FEC_AFT_COR_ER ODU_PM_BBER Packets Received (65~127Octets in Length)

FEC_BEF_COR_ER ODU_PM_BIP8 Packets Received (128~255Octets in Length)

FEC_COR_0BIT_CNT ODU_PM_ES Packets Received (256~511Octets in Length)

FEC_COR_1BIT_CNT ODU_PM_FEBBE Packets Received (512~1023Octets in Length)

FEC_COR_BYTE_CNT ODU_PM_FEBBER Packets Received (1024~1518Octets in Length)

FEC_UNCOR_BLOCK_CNT

ODU_PM_FEES Packets Received (1519~MTUOctets in Length)

ICTMPCUR ODU_PM_FESES Packets Transmitted (64 Octetsin Length)

ICTMPMAX ODU_PM_FESESR Packets Transmitted (65~127Octets in Length)

ICTMPMIN ODU_PM_FEUAS Packets Transmitted (128~255Octets in Length)

LINE_OUT_POWERCUR ODU_PM_SES Packets Transmitted (256~511Octets in Length)

LINE_OUT_POWERMAX ODU_PM_SESR Packets Transmitted(512~1023 Octets in Length)

LINE_OUT_POWERMIN ODU_PM_UAS Packets Transmitted(1024~1518 Octets in Length)

LSBIASCUR OTU_BBE Unicast Packets Received

LSBIASMAX OTU_BBER Multicast Packets Received



4-13

LSBIASMIN OTU_BIAES Broadcast Packets Received

LSCLCCUR OTU_ES Unicast Packets Transmitted

LSCLCMAX OTU_FEBBE Multicast Packets Transmitted

LSCLCMIN OTU_FEBBER Broadcast Packets Transmitted

LSIOPCUR OTU_FEES Undersize Packets Received

LSIOPMAX OTU_FESES Oversize Packets Received

LSIOPMIN OTU_FESESR Fragments

LSOOPCUR OTU_FEUAS Jabbers

LSOOPMAX OTU_IAES Bad Octets Received

LSOOPMIN OTU_SES Bad Octets Transmitted

LSTMPCUR OTU_SESR FCS Errors

FEC_AFT_COR_ERAVR FEC_BEF_COR_ERAVR

4.2.4 ETMX/ETMXS Board Performance Event ListENVTMPCUR LSIOPMIN ODU_PM_SESR

ENVTMPMAX LSOOPCUR ODU_PM_UAS

ENVTMPMIN LSOOPMAX OTU_BBE

FEC_AFT_COR_ER LSOOPMIN OTU_BBER

FEC_BEF_COR_ER LSTMPCUR OTU_BIAES

FEC_COR_0BIT_CNT LSTMPMAX OTU_ES

FEC_COR_1BIT_CNT LSTMPMIN OTU_FEBBE

FEC_COR_BYTE_CNT MSBBE OTU_FEBBER

FEC_UNCOR_BLOCK_CNT

MSCSES OTU_FEES

ICTMPCUR MSES OTU_FESES

ICTMPMAX MSSES OTU_FESESR

ICTMPMIN MSUAS OTU_FEUAS

LINE_OUT_POWERCUR ODU_PM_BBE OTU_IAES

LINE_OUT_POWERMAX ODU_PM_BBER OTU_SES

LINE_OUT_POWERMIN ODU_PM_BIP8 OTU_SESR





Issue 08 (2011-10-30)

LSBIASCUR ODU_PM_ES OTU_SM_BIP8

LSBIASMAX ODU_PM_FEBBE OTU_UAS

LSBIASMIN ODU_PM_FEBBER RSES

LSCLCCUR ODU_PM_FEES RSOFS

LSCLCMAX ODU_PM_FESES RSSES

LSCLCMIN ODU_PM_FESESR RSUAS

LSIOPCUR ODU_PM_FEUAS FEC_AFT_COR_ERAVR

LSIOPMAX ODU_PM_SES FEC_BEF_COR_ERAVR

ODU_TCM1_BBE ODU_TCM1_BBER ODU_TCM1_BIAES

ODU_TCM1_ES ODU_TCM1_FEBBE ODU_TCM1_FEBBER

ODU_TCM1_FEES ODU_TCM1_FESES ODU_TCM1_FESESR

ODU_TCM1_FEUAS ODU_TCM1_IAES ODU_TCM1_SES

ODU_TCM1_SESR ODU_TCM1_UAS ODU_TCM2_BBE

ODU_TCM2_BBER ODU_TCM2_BIAES ODU_TCM2_ES

ODU_TCM2_FEBBE ODU_TCM2_FEBBER ODU_TCM2_FEES

ODU_TCM2_FESES ODU_TCM2_FESESR ODU_TCM2_FEUAS

ODU_TCM2_IAES ODU_TCM2_SES ODU_TCM2_SESR

ODU_TCM2_UAS ODU_TCM3_BBE ODU_TCM3_BBER

ODU_TCM3_BIAES ODU_TCM3_ES ODU_TCM3_FEBBE

ODU_TCM3_FEBBER ODU_TCM3_FEES ODU_TCM3_FESES

ODU_TCM3_FESESR ODU_TCM3_FEUAS ODU_TCM3_IAES

ODU_TCM3_SES ODU_TCM3_SESR ODU_TCM3_UAS












4-15






4.2.5 FDG Board Performance Event List

ENVTMPCUR ODU_PM_BBE Packets Transmitted (65~127 Octets inLength)

ENVTMPMAX ODU_PM_BBER Packets Transmitted (128~255 Octetsin Length)

ENVTMPMIN ODU_PM_BIP8 Packets Transmitted (256~511 Octetsin Length)

FEC_AFT_COR_ER

ODU_PM_ES Packets Transmitted (512~1023 Octetsin Length)

FEC_BEF_COR_ER

ODU_PM_FEBBE Packets Received (64 Octets in Length)

FEC_COR_0BIT_CNT

ODU_PM_FEBBER Packets Received (65~127 Octets inLength)

FEC_COR_1BIT_CNT

ODU_PM_FEES Packets Received (128~255 Octets inLength)

FEC_COR_BYTE_CNT

ODU_PM_FESES Packets Received (256~511 Octets inLength)

FEC_UNCOR_BLOCK_CNT

ODU_PM_FESESR Packets Received (512~1023 Octets inLength)

LSBIASCUR ODU_PM_FEUAS Packets Received (1024~1518 Octetsin Length)

LSBIASMAX ODU_PM_SES Packets Received (1519~MTU Octetsin Length)

LSBIASMIN ODU_PM_SESR Packets Transmitted (64 Octets inLength)

LSCLCCUR ODU_PM_UAS Packets Transmitted (1024~1518Octets in Length)

LSCLCMAX OTU_BBE Packets Transmitted (1519~MTUOctets in Length)

LSCLCMIN OTU_BBER Unicast Packets Received





Issue 08 (2011-10-30)

LSIOPCUR OTU_BIAES Multicast Packets Received

LSIOPMAX OTU_ES Broadcast Packets Received

LSIOPMIN OTU_FEBBE Unicast Packets Transmitted

LSOOPCUR OTU_FEBBER Multicast Packets Transmitted

LSOOPMAX OTU_FEES Broadcast Packets Transmitted

LSOOPMIN OTU_FESES Pause Frames Received

LSTMPCUR OTU_FESESR Pause Frames Transmitted

LSTMPMAX OTU_FEUAS Undersize Packets Received

LSTMPMIN OTU_IAES Oversize Packets Received

MSBBE OTU_SES Fragments

MSCSES OTU_SESR Jabbers

MSES OTU_SM_BIP8 Good Octets Received

MSFEBBE OTU_UAS Good Octets Transmitted

MSFECSES RSBBE Bad Octets Received

MSFEES RSCSES Bad Octets Transmitted

MSFESES RSES FCS Errors

MSSES RSSES

MSUAS RSUAS

4.2.6 FIU Board Performance Event List

ENVTMPMAX ENVTMPCUR ENVTMPMIN

SUMIOPMAX SUMIOPMIN SUMIOPCUR

4.2.7 FMU Board Performance Event List

ENVTMPMAX ENVTMPMIN ENVTMPCUR

4.2.8 HBA Board Performance Event List

BCVCUR ENVTMPCUR SUMIOPMAX



4-17

BCVMAX ICTMPCUR SUMIOPMIN

BCVMIN ICTMPMAX SUMOOPCUR

CCVCUR ICTMPMIN SUMOOPMAX

CCVMAX PUMPTMPCUR SUMOOPMIN

CCVMIN PUMPTMPMAX WCVCUR

ENVTMPMAX PUMPTMPMIN WCVMAX

ENVTMPMIN SUMIOPCUR WCVMIN

4.2.9 ITL Board Performance Event List

ICCLCCUR ICTMPCUR ENVTMPMAX

ICCLCMAX ICTMPMAX ENVTMPMIN

ICCLCMIN ICTMPMIN ENVTMPCUR

4.2.10 LBE/LBES Board Performance Event List

ENVTMPMAX LSOOPMIN Packets Received (64 Octets in Length)

ENVTMPMIN ODU_PM_BBE Packets Received (65~127 Octets inLength)

ENVTMPCUR ODU_PM_BBER Packets Received (128~255 Octets inLength)

FEC_AFT_COR_ER ODU_PM_BIP8 Packets Received (256~511 Octets inLength)

FEC_BEF_COR_ER ODU_PM_ES Packets Received (512~1023 Octets inLength)

FEC_COR_0BIT_CNT ODU_PM_FEBBE Packets Received (1024~1518 Octets inLength)

FEC_COR_1BIT_CNT ODU_PM_FEBBER Packets Transmitted (64 Octets inLength)

FEC_COR_BYTE_CNT

ODU_PM_FEES Packets Transmitted (65~127 Octets inLength)

FEC_UNCOR_BLOCK_CNT

ODU_PM_FESES Packets Transmitted (128~255 Octets inLength)

ICTMPCUR ODU_PM_FESESR Packets Transmitted (256~511 Octets inLength)





Issue 08 (2011-10-30)

ICTMPMAX ODU_PM_FEUAS Packets Transmitted (512~1023 Octetsin Length)

ICTMPMIN ODU_PM_SES Packets Transmitted (1024~1518Octets in Length)

LINE_OUT_POWER-CUR

ODU_PM_SESR Unicast Packets Received

LINE_OUT_POWER-MAX

ODU_PM_UAS Multicast Packets Received

LINE_OUT_POWER-MIN

OTU_BBE Broadcast Packets Received

LSBIASCUR OTU_BBER Unicast Packets Transmitted

LSBIASMAX OTU_BIAES Multicast Packets Transmitted

LSBIASMIN OTU_ES Broadcast Packets Transmitted

LSCLCCUR OTU_FEBBE Pause Frames Received

LSCLCMAX OTU_FEBBER Pause Frames Transmitted

LSCLCMIN OTU_FEES Undersize Packets Received

LSIOPCUR OTU_FESES Oversize Packets Received

LSIOPMAX OTU_FESESR Fragments

LSIOPMIN OTU_FEUAS Jabbers

LSTMPCUR OTU_IAES Good Octets Received

LSTMPMAX OTU_SES Good Octets Transmitted

LSTMPMIN OTU_SESR FCS Errors

LSOOPCUR OTU_SM_BIP8 FEC_AFT_COR_ERAVR

LSOOPMAX OTU_UAS FEC_BEF_COR_ERAVR







ODU_TCM2_FEBBE ODU_TCM2_FEBBER

ODU_TCM2_FEES

ODU_TCM2_FESES ODU_TCM2_FESESR

ODU_TCM2_FEUAS



4-19













ODU_TCM5_FEBBE ODU_TCM5_FEBBER

ODU_TCM5_FEES

ODU_TCM5_FESES ODU_TCM5_FESESR

ODU_TCM5_FEUAS







4.2.11 LBF/LBFS Board Performance Event ListENVTMPCUR MSSES RSCSES

ENVTMPMAX MSUAS RSES

ENVTMPMIN ODU_PM_BBE RSOFS

FEC_AFT_COR_ER ODU_PM_BBER RSSES

FEC_BEF_COR_ER ODU_PM_BIP8 RSUAS

FEC_COR_0BIT_CNT ODU_PM_ES Packets Received (64 Octetsin Length)





Issue 08 (2011-10-30)



FEC_UNCOR_BLOCK_CNT

ODU_PM_FEES Packets Received (256~511Octets in Length)

ICTMPCUR ODU_PM_FESES Packets Received (512~1023Octets in Length)

ICTMPMAX ODU_PM_FESESR Packets Received(1024~1518 Octets in Length)

ICTMPMIN ODU_PM_FEUAS Packets Transmitted (64Octets in Length)

LINE_OUT_POWER-CUR

ODU_PM_SES Packets Transmitted (65~127Octets in Length)

LINE_OUT_POWER-MAX

ODU_PM_SESR Packets Transmitted(128~255 Octets in Length)


LSBIASCUR OTU_BBE Packets Transmitted(512~1023 Octets in Length)

LSBIASMAX OTU_BBER Packets Transmitted(1024~1518 Octets in Length)

LSBIASMIN OTU_BIAES Unicast Packets Received

LSCLCCUR OTU_ES Multicast Packets Received

LSCLCMAX OTU_FEBBE Broadcast Packets Received

LSCLCMIN OTU_FEBBER Unicast Packets Transmitted

LSIOPCUR OTU_FEES Multicast PacketsTransmitted

LSIOPMAX OTU_FESES Broadcast PacketsTransmitted

LSIOPMIN OTU_FESESR Pause Frames Received

LSOOPCUR OTU_FEUAS Pause Frames Transmitted

LSOOPMAX OTU_IAES Undersize Packets Received

LSOOPMIN OTU_SES Oversize Packets Received

LSTMPCUR OTU_SESR Fragments

LSTMPMAX OTU_SM_BIP8 Jabbers



4-21

LSTMPMIN OTU_UAS Good Octets Received

MSBBE FEC_BEF_COR_ERAVR Good Octets Transmitted

MSCSES FEC_AFT_COR_ERAVR FCS Errors

MSES RSBBE ODU_TCM1_BIAES

ODU_TCM1_BBE ODU_TCM1_BBER ODU_TCM1_FEBBER

ODU_TCM1_ES ODU_TCM1_FEBBE ODU_TCM1_FESESR

ODU_TCM1_FEES ODU_TCM1_FESES ODU_TCM1_SES

ODU_TCM1_FEUAS ODU_TCM1_IAES ODU_TCM2_BBE

ODU_TCM1_SESR ODU_TCM1_UAS ODU_TCM2_ES

ODU_TCM2_BBER ODU_TCM2_BIAES ODU_TCM2_FEES

ODU_TCM2_FEBBE ODU_TCM2_FEBBER ODU_TCM2_FEUAS

ODU_TCM2_FESES ODU_TCM2_FESESR ODU_TCM2_SESR

ODU_TCM2_IAES ODU_TCM2_SES ODU_TCM3_BBER

ODU_TCM2_UAS ODU_TCM3_BBE ODU_TCM3_FEBBE

ODU_TCM3_BIAES ODU_TCM3_ES ODU_TCM3_FESES

ODU_TCM3_FEBBER ODU_TCM3_FEES ODU_TCM3_IAES

ODU_TCM3_FESESR ODU_TCM3_FEUAS ODU_TCM3_UAS

ODU_TCM3_SES ODU_TCM3_SESR ODU_TCM4_BIAES

ODU_TCM4_BBE ODU_TCM4_BBER ODU_TCM4_FEBBER

ODU_TCM4_ES ODU_TCM4_FEBBE ODU_TCM4_FESESR

ODU_TCM4_FEES ODU_TCM4_FESES ODU_TCM4_SES

ODU_TCM4_FEUAS ODU_TCM4_IAES ODU_TCM5_BBE

ODU_TCM4_SESR ODU_TCM4_UAS ODU_TCM5_ES

ODU_TCM5_BBER ODU_TCM5_BIAES ODU_TCM5_FEES

ODU_TCM5_FEBBE ODU_TCM5_FEBBER ODU_TCM5_FEUAS

ODU_TCM5_FESES ODU_TCM5_FESESR ODU_TCM5_SESR

ODU_TCM5_IAES ODU_TCM5_SES ODU_TCM6_BBER

ODU_TCM5_UAS ODU_TCM6_BBE ODU_TCM6_FEBBE

ODU_TCM6_BIAES ODU_TCM6_ES ODU_TCM6_FESES

ODU_TCM6_FEBBER ODU_TCM6_FEES ODU_TCM6_IAES

ODU_TCM6_FESESR ODU_TCM6_FEUAS ODU_TCM6_UAS





Issue 08 (2011-10-30)

ODU_TCM6_SES ODU_TCM6_SESR

4.2.12 LOG/LOGS Board Performance Event ListENVTMPCUR LSTMPMAX OTU_SM_BIP8

ENVTMPMAX LSTMPMIN OTU_UAS

ENVTMPMIN ODU_PM_BBE Packets Received (64 Octets inLength)

FEC_AFT_COR_ER ODU_PM_BBER Packets Received (65~127Octets in Length)

FEC_BEF_COR_ER ODU_PM_BIP8 Packets Received (128~255Octets in Length)

FEC_COR_0BIT_CNT ODU_PM_ES Packets Received (256~511Octets in Length)



FEC_UNCOR_BLOCK_CNT

ODU_PM_FEES Packets Received (1519~MTUOctets in Length)

ICTMPCUR ODU_PM_FESES Packets Transmitted (64 Octetsin Length)

ICTMPMAX ODU_PM_FESESR Packets Transmitted (65~127Octets in Length)

ICTMPMIN ODU_PM_FEUAS Packets Transmitted (128~255Octets in Length)

LINE_OUT_POWERCUR ODU_PM_SES Packets Transmitted (256~511Octets in Length)

LINE_OUT_POWERMAX ODU_PM_SESR Packets Transmitted(512~1023 Octets in Length)


LSBIASCUR OTU_BBE Unicast Packets Received

LSBIASMAX OTU_BBER Multicast Packets Received

LSBIASMIN OTU_BIAES Broadcast Packets Received

LSCLCCUR OTU_ES Unicast Packets Transmitted



4-23

LSCLCMAX OTU_FEBBE Multicast Packets Transmitted

LSCLCMIN OTU_FEBBER Broadcast Packets Transmitted

LSIOPCUR OTU_FEES Undersize Packets Received

LSIOPMAX OTU_FESES Oversize Packets Received

LSIOPMIN OTU_FESESR Fragments

LSOOPCUR OTU_FEUAS Jabbers

LSOOPMAX OTU_IAES Bad Octets Received

LSOOPMIN OTU_SES Bad Octets Transmitted

LSTMPCUR OTU_SESR FCS Errors


4.2.13 LQM Board Performance Event ListENVTMPCUR ODU_PM_FEBBER Packets Received (65~127

Octets in Length)

ENVTMPMAX ODU_PM_FEES Packets Received (128~255Octets in Length)

ENVTMPMIN ODU_PM_FESES Packets Received (256~511Octets in Length)

FEC_AFT_COR_ER ODU_PM_FESESR Packets Received (512~1023Octets in Length)

FEC_BEF_COR_ER ODU_PM_FEUAS Packets Received (1024~1518Octets in Length)

FEC_COR_0BIT_CNT ODU_PM_SES Packets Received (1519~MTUOctets in Length)

FEC_COR_1BIT_CNT ODU_PM_SESR Packets Transmitted (65~127Octets in Length)

FEC_COR_BYTE_CNT ODU_PM_UAS Packets Transmitted (128~255Octets in Length)

FEC_UNCOR_BLOCK_CNT

OTU_BBE Packets Transmitted (256~511Octets in Length)

LSBIASCUR OTU_BBER Packets Transmitted(512~1023 Octets in Length)

LSBIASMAX OTU_BIAES Packets Transmitted(1024~1518 Octets in Length)





Issue 08 (2011-10-30)

LSBIASMIN OTU_ES Packets Transmitted(1519~MTU Octets in Length)

LSCLCCUR OTU_FEBBE Unicast Packets Received

LSCLCMAX OTU_FEBBER Multicast Packets Received

LSCLCMIN OTU_FEES Broadcast Packets Received

LSIOPCUR OTU_FESES Unicast Packets Transmitted

LSIOPMAX OTU_FESESR Multicast Packets Transmitted

LSIOPMIN OTU_FEUAS Broadcast PacketsTransmitted

LSOOPCUR OTU_IAES Pause Frames Received

LSOOPMAX OTU_SES Pause Frames Transmitted

LSOOPMIN OTU_SESR Undersize Packets Received

LSTMPCUR OTU_SM_BIP8 Oversize Packets Received

LSTMPMAX OTU_UAS Fragments

LSTMPMIN RSBBE Jabbers

ODU_PM_BBE RSCSES Good Octets Received

ODU_PM_BBER RSES Good Octets Transmitted

ODU_PM_BIP8 RSSES Bad Octets Received

ODU_PM_ES RSUAS Bad Octets Transmitted

ODU_PM_FEBBE Packets Received (64 Octets inLength)

FCS Errors

FEC_AFT_COR_ERAVR

FEC_BEF_COR_ERAVR

4.2.14 LU40 Board Performance Event ListENVTMPCUR ENVTMPMAX ENVTMPMIN

FEC_AFT_CORER_FLOAT

FEC_AFT_COR_ER FEC_BEF_CORER_FLOAT

FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT

FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT

LINE_OUT_POWERCUR

LINE_OUT_POWERMAX LINE_OUT_POWERMIN LSBIASCUR



4-25

LSBIASMAX 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 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 OTU_UAS

RSBBE RSCSES RSES

RSOFS RSSES RSUAS




















Issue 08 (2011-10-30)














4.2.15 LU40S Board Performance Event ListENVTMPCUR ENVTMPMAX ENVTMPMIN

FEC_AFT_CORER_FLOAT




LINE_OUT_POWERCUR













4-27






RSBBE RSCSES RSES

RSOFS RSSES RSUAS





























Issue 08 (2011-10-30)





4.2.16 LUR40/LUR40S Board Performance Event List

ENVTMPCUR ENVTMPMAX ENVTMPMIN

FEC_AFT_CORER_FLOAT




LINE_OUT_POWERCUR
















4.2.17 LWC1 Board Performance Event List

ENVTMPMAX LSIOPMIN ODU_PM_SESR



4-29

ENVTMPMIN LSOOPCUR ODU_PM_UAS

ENVTMPCUR LSOOPMAX OTU_BBE






FEC_UNCOR_BLOCK_CNT

MSES OTU_FEES

ICTMPCUR MSSES OTU_FESES

ICTMPMAX MSUAS OTU_FESESR

ICTMPMIN MSCSES OTU_FEUAS






LSBIASMIN ODU_PM_FEBBER RSBBE

LSCLCCUR ODU_PM_FEES RSES


LSCLCMIN ODU_PM_FESESR RSCSES

LSIOPCUR ODU_PM_FEUAS RSUAS

LSIOPMAX ODU_PM_SES RSOFS


4.2.18 LWF/LWFS Board Performance Event ListENVTMPMAX LSIOPMIN ODU_PM_SESR








Issue 08 (2011-10-30)





FEC_UNCOR_BLOCK_CNT

MSES OTU_FEES




























4-31



















4.2.19 LWX Board Performance Event ListENVTMPMAX LSCLCMIN Packets Received (64 Octets in Length)

ENVTMPMIN LSBIASCUR Packets Received (65~127 Octets inLength)

ENVTMPCUR LSBIASMAX Packets Received (128~255 Octets inLength)

LSOOPCUR LSBIASMIN Packets Received (256~511 Octets inLength)

LSOOPMAX LSCLCCUR Packets Received (512~1023 Octets inLength)

LSOOPMIN LSCLCMAX Packets Received (1024~1518 Octets inLength)





Issue 08 (2011-10-30)

LSIOPCUR RSBBE Packets Received (1519~MTU Octets inLength)

LSIOPMAX RSES Undersize Packets Received

LSIOPMIN RSSES Oversize Packets Received

LSTMPCUR RSCSES Good Octets Received

LSTMPMAX RSUAS Bad Octets Received

LSTMPMIN RSOFS FCS Errors

4.2.20 M40 Board Performance Event ListENVTMPMAX ICCLCMAX ICTMPMIN

ENVTMPMIN ICCLCMIN SUMOOPCUR

ENVTMPCUR ICTMPCUR SUMOOPMAX

ICCLCCUR ICTMPMAX SUMOOPMIN

4.2.21 MCA Board Performance Event ListENVTMPMAX PCLSOPCUR PCLSWLOCUR

ENVTMPMIN PCLSSNCUR

ENVTMPCUR PCLSWLCUR

4.2.22 MR2 Board Performance Event ListENVTMPMAX ENVTMPMIN ENVTMPCUR

4.2.23 MR8 Board Performance Event ListENVTMPCUR ENVTMPMAX ENVTMPMIN



4-33

4.2.24 MWA Board Performance Event ListENVTMPMAX ENVTMPMIN ENVTMPCUR

4.2.25 MWF Board Performance Event ListENVTMPMAX ENVTMPMIN ENVTMPCUR

4.2.26 OAU Board Performance Event ListBCVCUR EDF_BOX_TMPMIN SUMIOPMAX

BCVMAX ENVTMPMAX SUMIOPMIN

BCVMIN ENVTMPMIN SUMOOPCUR

CCVCUR ENVTMPCUR SUMOOPMAX



EDF_BOX_TMPCUR PUMPTMPMIN WCVMAX

EDF_BOX_TMPMAX SUMIOPCUR WCVMIN

4.2.27 OBU Board Performance Event ListBCVCUR EDF_BOX_TMPMIN SUMIOPMAX












Issue 08 (2011-10-30)

4.2.28 OLP Board Performance Event List

ENVTMPMAX ENVTMPCUR SUMIOPMAX

ENVTMPMIN SUMIOPCUR SUMIOPMIN

4.2.29 OPU Board Performance Event List

BCVCUR EDF_BOX_TMPMIN SUMIOPMAX








4.2.30 PMU Board Performance Event List

PMUTMPCUR PMUTMPMAX PMUTMPMIN

4.2.31 RMU9 Board Performance Event List

ENVTMPCUR ICTMPMAX SUMIOPMIN

ENVTMPMAX ICTMPMIN SUMOOPCUR

ENVTMPMIN SUMIOPCUR SUMOOPMAX

ICTMPCUR SUMIOPMAX SUMOOPMIN

4.2.32 RPC Board Performance Event List

BCVCUR ENVTMPMAX PUMPTMPCUR

BCVMAX ENVTMPMIN PUMPTMPMAX

BCVMIN ENVTMPCUR PUMPTMPMIN



4-35

CCVCUR OOPRLMAX WCVCUR

CCVMAX OOPRLMIN WCVMAX

CCVMIN OOPRLCUR WCVMIN

4.2.33 SC1/SC2 Board Performance Event List

CRC4BBE ENVTMPMAX LSTMPCUR

CRC4CSES ENVTMPMIN LSTMPMAX

CRC4ES ENVTMPCUR LSTMPMIN

CRC4FEBBE LSOOPCUR LSBIASCUR

CRC4FECSES LSOOPMAX LSBIASMAX

CRC4FEES LSOOPMIN LSBIASMIN

CRC4FESES LSIOPCUR LSCLCCUR

CRC4SES LSIOPMAX LSCLCMAX

CRC4UAS LSIOPMIN LSCLCMIN

4.2.34 TMR/TMRS Board Performance Event List

ENVTMPMAX LSCLCMIN ODU_PM_SES

ENVTMPMIN LSIOPCUR ODU_PM_SESR

ENVTMPCUR LSIOPMAX ODU_PM_UAS

FEC_AFT_COR_ER LSIOPMIN OTU_BBE

FEC_BEF_COR_ER LSOOPCUR OTU_BBER

FEC_COR_0BIT_CNT LSOOPMAX OTU_BIAES

FEC_COR_1BIT_CNT LSOOPMIN OTU_ES

FEC_COR_BYTE_CNT LSTMPCUR OTU_FEBBE

FEC_UNCOR_BLOCK_CNT LSTMPMAX OTU_FEBBER

ICTMPCUR LSTMPMIN OTU_FEES

ICTMPMAX ODU_PM_BBE OTU_FESES

ICTMPMIN ODU_PM_BBER OTU_FESESR

LINE_OUT_POWERCUR ODU_PM_BIP8 OTU_FEUAS





Issue 08 (2011-10-30)

LINE_OUT_POWERMAX ODU_PM_ES OTU_IAES

LINE_OUT_POWERMIN ODU_PM_FEBBE OTU_SES

LSBIASCUR ODU_PM_FEBBER OTU_SESR

LSBIASMAX ODU_PM_FEES OTU_SM_BIP8

LSBIASMIN ODU_PM_FESES OTU_UAS

LSCLCCUR ODU_PM_FESESR

LSCLCMAX ODU_PM_FEUAS

4.2.35 TMX/TMXS Board Performance Event ListENVTMPMAX LSOOPMAX ODU_PM_SESR

ENVTMPCUR LSOOPMIN ODU_PM_UAS

ENVTMPMIN LSTMPCUR OTU_BBE

FEC_AFT_COR_ER LSTMPMAX OTU_BBER

FEC_BEF_COR_ER LSTMPMIN OTU_BIAES

FEC_COR_0BIT_CNT MSBBE OTU_ES

FEC_COR_1BIT_CNT MSCSES OTU_FEBBE

FEC_COR_BYTE_CNT MSES OTU_FEBBER

FEC_UNCOR_BLOCK_CNT MSFEBBE OTU_FEES

ICTMPCUR MSFECSES OTU_FESES

ICTMPMAX MSFEES OTU_FESESR

ICTMPMIN MSFESES OTU_FEUAS

LINE_OUT_POWERCUR MSSES OTU_IAES

LINE_OUT_POWERMAX MSUAS OTU_SES

LINE_OUT_POWERMIN ODU_PM_BBE OTU_SESR

LSBIASCUR ODU_PM_BBER OTU_SM_BIP8

LSBIASMAX ODU_PM_BIP8 OTU_UAS

LSBIASMIN ODU_PM_ES RSBBE

LSCLCCUR ODU_PM_FEBBE RSCSES

LSCLCMAX ODU_PM_FEBBER RSES

LSCLCMIN ODU_PM_FEES RSOFS



4-37

LSIOPCUR ODU_PM_FESES RSSES

LSIOPMAX ODU_PM_FESESR RSUAS

LSIOPMIN ODU_PM_FEUAS FEC_AFT_COR_ERAVR

LSOOPCUR ODU_PM_SES FEC_BEF_COR_ERAVR
































Issue 08 (2011-10-30)


4.2.36 TMX40/TMX40S Board Performance Event ListENVTMPCUR ENVTMPMAX ENVTMPMIN

FEC_AFT_CORER_FLOAT




LSBIASCUR















RSBBE RSCSES RSES

RSSES RSUAS RSOFS









4-39























RMON Performance Event

Packets Received (64 Octetsin Length)

Packets Transmitted(512~1023 Octets in Length)

Undersize Packets Received


Packets Transmitted(1024~1518 Octets inLength)

Oversize Packets Received


Unicast Packets Received Fragments





Issue 08 (2011-10-30)


Multicast Packets Received Jabbers


Broadcast Packets Received Good Octets Received

Packets Received(1024~1518 Octets inLength)

Unicast Packets Transmitted Bad Octets Received

Packets Transmitted (64Octets in Length)

Multicast PacketsTransmitted

Good Octets Transmitted


Broadcast PacketsTransmitted

Bad Octets Transmitted


Pause Frames Received Alignment Errors


Pause Frames Transmitted FCS Errors

4.2.37 TRC1 Board Performance Event ListENVTMPMAX LSIOPMIN ODU_PM_SESR








FEC_UNCOR_BLOCK_CNT MSES OTU_FEES










4-41








4.2.38 V40 Board Performance Event List

ENVTMPMAX ICTMPCUR SUMOOPCUR

ENVTMPMIN ICTMPMAX SUMOOPMAX

ENVTMPCUR ICTMPMIN SUMOOPMIN

4.2.39 VA4 Board Performance Event List

ENVTMPMAX LSOOPCUR LSIOPCUR

ENVTMPMIN LSOOPMAX LSIOPMAX

ENVTMPCUR LSOOPMIN LSIOPMIN

4.2.40 VOA Board Performance Event List

LSOOPCUR LSOOPMIN LSIOPMAX

LSOOPMAX LSIOPCUR LSIOPMIN

4.2.41 WMU Board Performance Event List

ENVTMPCUR ICTMPMIN PCLSWLMAX

ENVTMPMAX PCLSOPCUR PCLSWLMIN

ENVTMPMIN PCLSOPMAX PCLSWLOCUR

ICTMPCUR PCLSOPMIN PCLSWLOMAX





Issue 08 (2011-10-30)

ICTMPMAX PCLSWLCUR PCLSWLOMIN

4.2.42 WSD9 Board Performance Event ListENVTMPCUR ICTMPMAX SUMIOPMIN




4.2.43 WSM9 Board Performance Event ListENVTMPCUR ICTMPMAX SUMIOPMIN




4.2.44 WSMD2 Board Performance Event ListENVTMPCUR ENVTMPMAX ENVTMPMIN

ICTMPCUR ICTMPMAX ICTMPMIN

SUMIOPCUR SUMIOPMAX SUMIOPMIN

SUMOOPCUR SUMOOPMAX SUMOOPMIN

4.2.45 WSMD4 Board Performance Event ListENVTMPCUR ICTMPMAX SUMIOPMIN






4-43

5 Performance Event Processing

About This Chapter

The performance event is an important parameter to evaluate the working performance ofDWDM equipment. Being acquainted with the generation principle, related boards and relatedalarms help you discover hidden trouble in routine maintenance and locate fault introubleshooting.

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 eventaccordingly.

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

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference 5 Performance Event Processing


5-1

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





Issue 08 (2011-10-30)

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-3

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





Issue 08 (2011-10-30)

5.1 BCV

Description

Pump Laser Back Facet Current

It includes:

l BCVMAX: stands for the maximum value during a period of time.

l BCVMIN: stands for the minimum value during a period of time.

l BCVCUR: stands for the current value.

Impact on System

None

Generation Principle and Possible Causes

Back facet current is current O/E converted from part of light reflected from the resonant cavityof a laser. The back facet current reflects the laser output optical power value. If the BCVCURis 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 CCVMAX: stands for the maximum value during a period of time.

l CCVMIN: stands for the minimum value during a period of time.

l CCVCUR: stands for the current value.



5-5

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 coolingcircuit in a certain laser.

Related Alarms

Alarm Name Correlation

PUMP_COOL_EXC It is generated when the cooling current oflaser 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 causeand solve the problem in a timely manner to avoid any alarm, thus to ensure the signaltransmission quality.


CRC error is detected by checking the received parity bit. The background block error meansthere are one or more data blocks containing error bits during transmission.

Related Alarms

None





Issue 08 (2011-10-30)

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 severelyerrored second means the severely errored second appears consecutively, it might indicate theinterruption 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



5-7

Impact on SystemThere 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 ensurethe signal transmission quality.

Generation Principle and Possible CausesCRC error is detected by checking the received parity bit. An errored second contains more thanone error block.

Related AlarmsNone

Procedure

Step 1 None

----End


5.6 CRC4FEBBE

DescriptionCRC4 Far End Background Block Error

Impact on SystemThere are bit errors in the services. If the number of bit errors is small, there is no impact on theservices. If the number of bit errors is large, determine the cause and solve the problem in atimely manner to avoid any alarm, thus to ensure the signal transmission quality.

Generation Principle and Possible CausesCRC error is detected by checking the received parity bit. The background block error meansthere are one or more data blocks containing error bit during transmission. And the far endbackground block error refers to the background block error detected at the opposite end.

Related AlarmsNone

Procedure

Step 1 None

----End





Issue 08 (2011-10-30)

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 severelyerrored second means the severely errored second appears consecutively, it might indicate theservice interruption on the fiber link. The far end consecutive severely errored second refers tothe 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 ensurethe signal transmission quality.



5-9


CRC error is detected by checking the received parity bit. An errored second contains more thanone error block. And the far end errored second refers to the errored second detected at theopposite 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 mannerto 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 severelyerrored second refers to the severely errored second detected at the opposite end.

Related Alarms

None

Procedure

Step 1 None

----End

Related Information

None





Issue 08 (2011-10-30)

5.10 CRC4SES

DescriptionCRC4 Severely Errored Second

Impact on SystemThere are bit errors in the services. Determine the cause and solve the problem in a timely mannerbecause the bit errors have affected the signal transmission quality.

Generation Principle and Possible CausesCRC 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 AlarmsNone

Procedure

Step 1 None

----End


5.11 CRC4UAS

DescriptionCRC4 Unavailable Second


Generation Principle and Possible CausesCRC error is detected by checking the received parity bit. If the severely errored seconds lastfor 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 erroredsecond disappears for more than 10 seconds, the available time starts from the beginning of the11th second, and the former 10 seconds are counted as available.



5-11

Related AlarmsNone


CRC4_CROSSTR CRC4 multi-frame error code count exceedsthe threshold. The alarm is generated whenthe number of the bit errors in the CRC4multiframe exceeds the threshold.

Procedure

Step 1 None

----End


5.12 EDF_BOX_TMP

DescriptionEDFA Fiber Box Temperature

It includes:

l EDF_BOX_TMPMAX: stand for the maximum value during a period of time.l EDF_BOX_TMPMIN: stand for the minimum value during a period of time.l EDF_BOX_TMPCUR: stand for the current value.

Impact on SystemThe 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.

Generation Principle and Possible CausesUse an A/D converter to sample the voltage corresponding to the working temperature of EDFAfiber box, and convert the voltage into temperature. The performance value shows the workingtemperature of EDFA fiber box.

Related AlarmsAlarm Name Correlation

EDFA_TMP_OVER It is generated when the temperature of EDFAfiber box exceeds the normal range.





Issue 08 (2011-10-30)

Procedure

Step 1 Check the ambient temperature of the board. For ambient temperature specifications of thespecific board, refer to the Product Description.

Step 2 Check whether the fan runs normally and whether the air duct is blocked because the dust filterof 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


5.13 ENV_TMP

DescriptionBoard Environmental Temperature

It includes:

l ENV_TMPMAX: stands for the maximum value during a period of time.l ENV_TMPMIN: stands for the minimum value during a period of time.l ENV_TMPCUR: stands for the current value.

Impact on SystemNone

Generation Principle and Possible CausesThis performance event is generated by hardware detecting, to show the ambient temperatureof board.


TEMP_ALARM It is generated when the ambient temperatureexceeds the threshold.

Procedure

Step 1 If the TEMP_ALARM alarm is generated, see the proper handling procedures.

----End



5-13

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 thatthe bit errors in the services bring impact on the transmission quality. In this case, determine thecause in a timely manner.


This performance event shows there are still errors at the receiver after FEC. This performanceevent 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 powerto 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






Issue 08 (2011-10-30)



In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the opticalpower 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




In this case, there must be FEC_BEF_CORER_FLOAT accompanied. You can adjust the opticalpower to increase the OSNR.

Related Alarms

None

Procedure

Step 1 None

----End



5-15

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 solvethe problem in a timely manner to avoid any alarm, and thus to ensure the signal transmissionquality.


The cause for the BER before the FEC is that the receiver detects bit errors, which are causedby dispersion, unstable performance of the optical interface, and/or very high attenuation.

Related Alarms


BEFFEC_EXC Signal degraded before FEC alarm. Signals sent from WDM sides ofthe opposite-end OTU have the FEC function. As a result, beforeperforming signal FEC in the receive direction of WDM side of thelocal-end OTU, the local-end OTU counts the bit error rate. This alarmis generated when the counted bit error rate exceeds the threshold.

BEFFEC_SD Signal degraded alarm before FEC alarm. Signals sent from WDMsides of the opposite-end OTU have the FEC function. As a result,before performing signal FEC in the receive direction of WDM sideof the local-end OTU, the local-end OTU counts the bit error rate.This alarm is generated when the counted bit error rate exceeds thethreshold.

Procedure

Step 1 Refer to the method of handling the BEFFEC_EXC.

----End

Related Information

None





Issue 08 (2011-10-30)

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 solvethe 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 OSNRat the receiving end. Normally, it should be zero.

Related Alarms


BEFFEC_EXC Signal degraded before FEC alarm. Signals sent from WDM side ofthe local-end OTU, the local-end OTU counts the bit error rate. Thisalarm is generated when the counted bit error rate exceeds thethreshold.

BEFFEC_SD Signal degraded alarm before FEC alarm. Signals sent from WDMside 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 thethreshold.

Procedure


----End

Related Information

None

5.19 FEC_BEF_CORER_FLOAT

Description

Before FEC Correct Errored Rate(floating point values)



5-17

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 solvethe 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 OSNRat the receiving end.

Related Alarms




Procedure


----End

Related Information

None


Description

Forward Error Correction - Corrected 0 Bit Count

Impact on System

None


This performance event shows the number of 0bit corrected by FEC function of the board, andindicates the FEC capability to signals of low OSNR.





Issue 08 (2011-10-30)

Related Alarms

None

Procedure

Step 1 None

----End

Related Information

None


Description

Forward Error Correction - Corrected 1 Bit Count

Impact on System

None


This performance event shows the number of 1bit corrected by FEC function of the board, andindicates 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



5-19


Generation Principle and Possible CausesThis performance event shows the number of byte corrected by FEC function of the board, andindicates the FEC capability to signals of low OSNR. Normally, it should be zero.

Related AlarmsNone

Procedure

Step 1 None

----End


5.23 FEC_UNCOR_BLOCK_CNT

DescriptionForward Error Correction - uncorrected Block Count

Impact on SystemThere are bit errors in the services and the signal transmission quality is affected.

Generation Principle and Possible CausesThis performance event shows the number of received error frames that cannot be corrected byFEC, and indicates that bit errors are beyond the correction capability of FEC. Normally, theperformance value should be zero.








Issue 08 (2011-10-30)

Procedure


----End

Related Information

None

5.24 ICCLC

Description

Module Cooling Current

It includes:

l ICCLCMAX: stands for the maximum value during a period of time.

l ICCLCMIN: stands for the minimum value during a period of time.

l ICCLCCUR: stands for the current value.

Impact on System

None


This performance event is generated by software checking with the cooling current detectingcircuit on board, to show the working status of module cooling current.

Related Alarms


MODULE_COOLCUR_OVER It is generated when the cooling or warmingcurrent of module exceeds the alarmthreshold.

Procedure

Step 1 If the MODULE_COOLCUR_OVER alarm is generated, see the handling procedure of thealarm.

----End



5-21


5.25 ICTMP

DescriptionModule Temperature

It includes:

l ICTMPMAX: stands for the maximum value during a period of time.l ICTMPMIN: stands for the minimum value during a period of time.l ICTMPCUR: stands for the current value.


Generation Principle and Possible CausesThis performance event is generated by checking the current working temperature of module,to show the working temperature of a module.


MODULE_TEMP_OVER It is generated when the working temperatureof module exceeds the threshold.

Procedure

Step 1 If the MODULE_TEMP_OVER alarm is generated, see the handling procedure of the alarm.

----End


5.26 LINE_OUT_POWER

DescriptionThe Line Output Optical Power

It includes:





Issue 08 (2011-10-30)

l LINE_OUT_POWER_MAX: stands for the maximum value during a period of time.

l LINE_OUT_POWER_MIN: stands for the minimum value during a period of time.

l 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 ofoptical 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

laser VOA and other units

Monitoringpoint A

Monitoringpoint A

Optical transmitting module

WARNINGOUT_PWR_HIGH and OUT_PWR_LOW alarms are generated by monitoring LSOOP, theyare independent from LINE_OUT_POWER.

Related Alarms

None

Procedure

Step 1 None

----End

Related Information

None



5-23

5.27 LSBIAS

DescriptionLaser Bias Current

It includes:

l LSBIASMAX: stands for the maximum value during a period of time.l LSBIASMIN: stands for the minimum value during a period of time.l LSBIASCUR: stands for the current value.


Generation Principle and Possible CausesThe LSBIAS performance value is obtained by hardware check and software conversion.


TD It is generated when the working current oflaser exceeds the threshold or the multiple ofthreshold.

LSR_WILL_DIE It is generated when the working current oflaser exceeds the threshold or the multiple ofthreshold.

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


5.28 LSCLC

DescriptionLaser Cooling Current





Issue 08 (2011-10-30)

It includes:

l LSCLCMAX: stands for the maximum value during a period of time.l LSCLCMIN: stands for the minimum value during a period of time.l LSCLCCUR: stands for the current value.

Impact on SystemWhen the cooling current of a laser exceeds the threshold, the optical module of the board worksabnormally. As a result, services cannot be transmitted or received normally.

Generation Principle and Possible CausesExternal cooling or warming equipment should be provided to keep the temperature stable fora laser to work. The laser cooling current shows the working status of cooling equipment orcircuit.


LSR_COOL_ALM It is generated when the laser cooling currentexceeds the pre-set threshold.

Procedure

Step 1 If the LSR_COOL_ALM alarm is generated, see the handling procedure of the alarm.

----End


5.29 LSIOP

DescriptionInput Optical Power

It includes:

l LSIOPMAX: stand for the maximum value during a period of time.l LSIOPMIN: stand for the minimum value during a period of time.l LSIOPCUR: stand for the current value.

Impact on SystemWhen the input optical power is very high or very low, bit errors and the LOF alarm may begenerated in the received signals, which brings impact on the services.



5-25


The hardware checks the optical module and then the software converts the check result intoLSIOP to show the input optical power performance of a board.

Related Alarms


IN_PWR_HIGH It is generated when the optical power input by board is higher thanthe upper threshold.

IN_PWR_LOW It is generated when the optical power input by board is lower thanthe lower threshold.

Procedure

Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than thehistory 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 thehistory 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 LSOOPMAX: stands for the maximum value during a period of time.

l LSOOPMIN: stands for the minimum value during a period of time.

l LSOOPCUR: stands for the current value.

Impact on System

If the output optical power of the laser is abnormal, there is impact on the normal transmissionof services.





Issue 08 (2011-10-30)

Generation Principle and Possible CausesThe hardware checks the optical module and then the software converts the check result intoLSOOP value to show the output optical power performance of the laser in a board.


OUT_PWR_HIGH It is generated when the optical power output by board is higher thanthe upper threshold.

OUT_PWR_LOW It is generated when the optical power output by board is lower thanthe lower threshold.

TF It is generated when the optical power output by board is 1dB lowerthan the lower threshold.

Procedure

Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than thehistory 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 thehistory 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


5.31 LSTMP

DescriptionLaser Temperature

It includes:

l LSTMPMAX: stands for the maximum value during a period of time.l LSTMPMIN: stands for the minimum value during a period of time.l LSTMPCUR: stands for the current value.




5-27


Normally, the laser temperature is a stable value obtained by software through calculating theresult outputted by the temperature detecting circuit in the laser.

Related Alarms


LTEMP_OVER It is generated when the laser temperature exceeds the pre-setthreshold.

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 andsolve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmissionquality.


The multiplex section errors are detected by checking the B2 byte. The background block errormeans there are one or more data blocks containing error bits during transmission.

Related Alarms


B2_EXC Multiplex section (B2) excessive errors alarm. The alarm is generatedwhen the B2 bit errors in the multiplex section exceeds the threshold.

B2_SD Multiplex section (B2) signal degraded alarm. The alarm is generatedwhen the B2 bit errors in the multiplex section exceeds the signaldegrade (SD) threshold.





Issue 08 (2011-10-30)


MS_AIS Multiplex section alarm indication. The alarm is generated when theopposite station transmits the MS_AIS signals or the receive part ofthe local station is faulty.

R_OOF Out of frame on receiving line. This alarm is generated when the headsof consecutive five frames fail to be detected.

R_LOF Loss of frame on receiving line. This alarm is generated when theframe alignment processing is out of frame (OOF) in consecutive 3ms.

Procedure

Step 1 Refer to the method of handling the B2_EXC.

----End

Related Information

None

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 problemin 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 erroredsecond, there is at least one defect or 30% of data blocks are error blocks. While the consecutiveseverely errored second means the severely errored second appears consecutively, accompaniedby the B2_EXC alarm. It might result in service interruption.

Related Alarms





5-29






Procedure


----End

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, determinethe cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signaltransmission quality.


The multiplex section errors are detected by checking the B2 byte. The MS errored second meansthere are more than one error block transmitted in this second.

Related Alarms







Issue 08 (2011-10-30)






Procedure


----End


5.35 MSFEBBE

DescriptionMS Far End Background Block Error

Impact on SystemIf bit errors are generated in the services on a far-end NE but no related alarm is reported on theopposite NE, there is no impact on the system. You, however, need to determine the cause andsolve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmissionquality.

Generation Principle and Possible CausesThe multiplex section errors are detected by checking the B2 byte. The background block errormeans there are one or more data blocks containing error bit during transmission. And the farend background block error refers to the background block error detected at the opposite end.



5-31


MS_RDI Multiplex section remote defect indication alarm. The alarm isgenerated at the local station if the opposite station back transmits theinformation through overhead when the WDM-side receive part ofthe opposite station is faulty.

MS_REI Multiplex section remote error indication. The alarm is generatedwhen the remote end detects the bit error block.

Procedure

Step 1 Refer to the method of handling the MS_RDI.

----End


5.36 MSFECSES

DescriptionMS Far End Consecutive Severely Errored Second


Generation Principle and Possible CausesThe multiplex section errors are detected by checking the B2 byte. During a severely erroredsecond, there is at least one defect or 30% of data blocks are error blocks. The consecutiveseverely errored second means the severely errored second appears consecutively, and it isaccompanied by the B2_EXE alarm. It might result in service interruption. The far endconsecutive severely errored second refers to the consecutive severely errored second detectedat the opposite end.





Issue 08 (2011-10-30)

Related Alarms




Procedure


----End

Related Information

None

5.37 MSFEES

Description

MS Far End Errored Second

Impact on System

If bit errors are generated in the services on a far-end NE but no related alarm is reported on theopposite NE, there is no impact on the system. You, however, need to determine the cause andsolve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmissionquality.


The multiplex section errors are detected by checking the B2 byte. An errored second containsmore than one error block. And the far end errored second refers to the errored second detectedat the opposite end.

Related Alarms





5-33



Procedure


----End

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 erroredsecond, there is at least one defect or 30% of data blocks are error blocks. And the far end severelyerrored second refers to the severely errored second detected at the opposite end.

Related Alarms








Issue 08 (2011-10-30)

Procedure


----End


5.39 MSSES

DescriptionMS Severely Errored Second

Impact on SystemThere are bit errors in the services. If the number of bit errors increases, determine the cause andsolve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmissionquality.

Generation Principle and Possible CausesThe multiplex section errors are detected by checking the B2 byte. During a severely erroredsecond, there is at least one defect or 30% of data blocks are error blocks.









5-35

Procedure


----End

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 mannerto ensure the signal transmission quality.


The multiplex section errors are detected by checking the B2 byte. If the severely errored secondslast for more than 10 seconds, the unavailable second starts from the beginning of the 11thsecond, and the former 10 severely errored seconds are counted as unavailable. If the severelyerrored second disappears for more than 10 seconds, the available time starts from the beginningof the 11th second, and the former 10 seconds are counted as available.

Related Alarms





R_LOS Loss of signal on receiving line. This alarm is generated when thereceive side receives no signals.






Issue 08 (2011-10-30)



Procedure


----End

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 blockerror means there are one or more data blocks containing error bits during transmission.

Related Alarms


PM_BIP8_OVER Bit interleaved parity (BIP) in the PM section of the ODU layerexceeds the upper threshold. The alarm is generated when the numberof BIP8 bit errors of the PM section on the optical channel data unitlayer exceeds the upper threshold.

PM_BIP8_SD BIP in the PM section of the ODU layer degrades. The alarm isgenerated when the number of BIP8 bit errors of the PM section onthe optical channel data unit layer exceeds the degrade threshold.



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 islarge, determine the cause and solve the problem in a timely manner to avoid any alarm, thus toensure the signal transmission quality.


ODU PM section background block errors are detected by checking the received parity bits. Thebackground block error refers to a data block where at least one bit error is generated during thetransmission. Background block error ratio of the ODU PM section refers to the ratio of thenumber of background block errors of the ODU PM section to the number of all blocks minusthe number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].

Related Alarms




Procedure


----End





Issue 08 (2011-10-30)


5.43 ODU_PM_BIP8

DescriptionODU PM Section BIP8


Generation Principle and Possible CausesThis performance event shows the number of errors that a board with an OTN interface detectsin path monitoring through the BIP8 check. Normally, the performance value should be zero.




Procedure


----End


5.44 ODU_PM_ES

DescriptionODU PM Section Errored Second



5-39

Impact on System



ODU PM Section error is detected by checking the received parity bit. An errored secondcontains more than one error block.

Related Alarms




Procedure


----End

Related Information

None

5.45 ODU_PM_FEBBE

Description

ODU PM Section Far End Background Block Error

Impact on System






Issue 08 (2011-10-30)

Generation Principle and Possible CausesODU PM Section error is detected by checking the received parity bit. The background blockerror means there are one or more data blocks containing error bit during transmission. And thefar end background block error refers to the background block error detected at the opposite end.


PM_BDI ODU PM section backward defect indication. The alarm is transferredin the upstream direction of the services, indicating the detected signalfailure.

PM_BEI ODU PM section backward error indication. If the board detects thatthe input signals contain the PM-BIP8 bit errors, it inserts the PM_BEIalarm back to the upstream board. The alarm is generated when theupstream station detects that the BEI flag in the OCH-OH of the PMsection of the received signals is true.

Procedure

Step 1 Refer to the method of handling the PM_BEI.

----End


5.46 ODU_PM_FEBBER

DescriptionODU PM Section Ratio of Far End Background Block Error

Impact on SystemWhen the value is not 0, it indicates that there are bit errors in the services. When the value islarge, determine the cause and solve the problem in a timely manner to avoid any alarm, thus toensure the signal transmission quality.

Generation Principle and Possible CausesODU PM section background block errors are detected by checking the received parity bits. Thebackground block error refers to a data block where at least one bit error is generated during thetransmission. Background block error ratio of the ODU PM section refers to the ratio of thenumber of background block errors of the ODU PM section to the number of all blocks minusthe number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second]. And the ratio of far end background block error refers to the ratioof background block error detected at the opposite end.



5-41




Procedure


----End


5.47 ODU_PM_FEES

DescriptionODU PM Section Far End Errored Second


Generation Principle and Possible CausesODU PM Section error is detected by checking the received parity bit. An errored secondcontains more than one error block. And the far end errored second refers to the errored seconddetected at the opposite end.







Issue 08 (2011-10-30)



Procedure


----End


5.48 ODU_PM_FESES

DescriptionODU PM Section Far End Severely Errored Second

Impact on SystemThere 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 ensurethe signal transmission quality.

Generation Principle and Possible CausesError is detected by checking the received parity bit. During a severely errored second, there isat least one defect or 30% of data blocks are error blocks. And the far end severely errored secondrefers to the severely errored second detected at the opposite end.






5-43

Procedure


----End

Related Information

None

5.49 ODU_PM_FESESR

Description

ODU PM Section Ratio of Far End Severely Errored Second

Impact on System

There are bit errors in the services on a far-end NE. If the number of block errors increases,determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensurethe signal transmission quality.


Bit errors are detected by checking the received parity bits. Severely errored second (SES) refersto the second where the checked signals contain a minimum of 30% block errors or at least onedefect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certainperiod of time to the total available time. Far end severely errored second ratio refers to the ratioof errored seconds that are detected at the far end.

Related Alarms




Procedure


----End





Issue 08 (2011-10-30)

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 problemin 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 fromthe beginning of the 11th second, and the former 10 severely errored seconds are counted asunavailable. If the severely errored second disappears for more than 10 seconds, the availabletime starts from the beginning of the 11th second, and the former 10 seconds are counted asavailable.And the far end unavailable second refers to the unavailable second detected at theopposite end.

Related Alarms




Procedure


----End

Related Information

None



5-45

5.51 ODU_PM_SES

Description

ODU PM Section Severely Errored Second

Impact on System

There are bit errors in the services. Determine the cause and solve the problem in a timely mannerbecause the bit errors have affected the signal transmission quality.


ODU PM Section error is detected by checking the received parity bit. During a severely erroredsecond, there is at least one defect or 30% of data blocks are error blocks.

Related Alarms




Procedure


----End

Related Information

None

5.52 ODU_PM_SESR

Description

ODU PM Section Ratio of Severely Errored Second





Issue 08 (2011-10-30)


Generation Principle and Possible CausesBit errors are detected by checking the received parity bits. Severely errored second (SES) refersto the second where the checked signals contain a minimum of 30% block errors or at least onedefect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certainperiod of time to the total available time.




Procedure


----End


5.53 ODU_PM_UAS

DescriptionODU PM Section Unavailable Second


Generation Principle and Possible CausesIf the severely errored seconds last for more than 10 seconds, the unavailable second starts fromthe beginning of the 10 seconds. If the severely errored second disappears for more than 10seconds, the available time starts from the beginning of the 10 seconds.



5-47

Related Alarms




Procedure


----End

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 causeand resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus toensure the signal transmission quality.


ODU TCMn Section errors are detected by checking the received parity bits. The backgroundblock error means there are one or more data blocks containing error bits during transmission.

Related Alarms


ODU_TCMn_DEG ODU TCMn burst-mode signal degradation. The unit reports thisalarm when bit errors are of burst distribution and the signaldegradation or bit error count crosses the threshold.





Issue 08 (2011-10-30)


ODU_TCMn_EXC ODU TCMn Poisson-mode excessive bit errors. The unit reports thisalarm when bit errors are of Poisson distribution and the signaldegradation 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 inthe 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 theODU_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 islarge, determine the cause and resolve the problem in a timely manner to avoid the occurrenceof 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 duringthe transmission. Background block error ratio of the ODU TCMn section refers to the ratio ofthe number of background block errors of the ODU TCMn section to the number of all blocksminus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].

Related Alarms





5-49



Procedure



----End

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 timelymanner to ensure the signal transmission quality.


ODU TCMn section backward incoming alignment errored second are detected by checking thebackward input frame alignment bits. Backward incoming alignment errored second refers tothe 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 normalrange. For the optical power specifications of the board, refer to the Product Description. If theinput optical power is abnormal, refer to the methods for handling the IN_PWR_HIGH andIN_PWR_LOW alarms.





Issue 08 (2011-10-30)

Step 2 If the performance event persists, refer to the description on bit error fault handling in theTroubleshooting.

----End


5.57 ODU_TCMn_ES

DescriptionODU TCMn Section Errored Second

Impact on SystemThere are bit errors in the services. If the number of block errors increases, determine the causeand resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus toensure the signal transmission quality.

Generation Principle and Possible CausesODU TCMn Section error is detected by checking the received parity bit. An errored secondcontains more than one error block.




Procedure



----End




5-51

5.58 ODU_TCMn_FEBBE

DescriptionODU TCMn Section Far End Background Block Error

Impact on SystemIf bit errors are generated in the services on a far-end NE but no related alarms are reported onthe opposite NE, there is no impact on the system. You, however, need to determine the causeand resolve the problem in a timely manner to avoid the occurrence of any alarm, and thus toensure the signal transmission quality.

Generation Principle and Possible CausesODU TCMn Section error is detected by checking the received parity bit. The background blockerror means there are one or more data blocks containing error bit during transmission. And thefar end background block error refers to the background block error detected in the opposite end.

Related AlarmsNone

Procedure



----End


5.59 ODU_TCMn_FEBBER

DescriptionODU TCMn Section Ratio of Far End Background Block Error

Impact on SystemWhen the value is not 0, it indicates that there are bit errors in the services. When the value islarge, determine the cause and resolve the problem in a timely manner to avoid the occurrenceof any alarm, and thus to ensure the signal transmission quality.





Issue 08 (2011-10-30)

Generation Principle and Possible CausesODU 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 duringthe transmission. Far end background block error ratio of the ODU TCMn section refers to theratio of the number of far end background block errors of the ODU TCMn section to the numberof all blocks minus the number of blocks during the unavailable time and SES period. BBER =cBBE/[(P-UAS-cSES) x blocks per second].

Related AlarmsNone

Procedure



----End

5.60 ODU_TCMn_FEES

DescriptionODU TCMn Section Far End Errored Second

Impact on SystemThere 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 anyalarm, and thus to ensure the signal transmission quality.

Generation Principle and Possible CausesODU Backward error indication of the TCMn section is determined by the BEI that is insertedat the far end. Far end errored second refers to the second where the checked signals contain atleast one block error at the far end.

Related AlarmsNone

Procedure

Step 1 Refer to the method of handling the ODU_TCMn_SES.

----End



5-53

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 anyalarm, and thus to ensure the signal transmission quality.


ODU Far end severely errored second of the TCMn section is determined by the BEI that isinserted at the far end. Far end severely errored second refers to the second where the checkedsignals contain a minimum of 30% block errors or at least one defect occurs. The fiber line maybe faulty.

Related Alarms

None

Procedure



----End

Related Information

None

5.62 ODU_TCMn_FESESR

Description

ODU TCMn Section Ratio of Far End Severely Errored Second





Issue 08 (2011-10-30)

Impact on System

There are bit errors in the services on a far-end NE. Determine the cause and resolve the problemin 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 aminimum of 30% block errors or at least one defect occurs. FESESR refers to the ratio of theFESES 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


ODU_TCMn_BDI ODU TCMn backward defect indication. The unit reports this alarmwhen the BDI bit of a TCMn overhead stays "1" for five consecutiveframes. The alarm travels upstream, which indicates the detectedsignal failure.



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


OTU_LOF OTU frame loss. The upstream station detects the LOF alarm and theninserts 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





Issue 08 (2011-10-30)

Impact on System

There are bit errors in the services. Determine the cause and resolve the problem in a timelymanner 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 atleast one defect occurs. The fiber line may be faulty.

Related Alarms




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

There are bit errors in the services. Determine the cause and resolve the problem in a timelymanner because the bit errors have affected the signal transmission quality.


It is obtained by calculating the BIP-8 of ODU TCMn section.



5-57




ProcedureStep 1 Refer to the method of handling the ODU_TCMn_DEG or ODU_TCMn_EXC.

----End


5.67 ODU_TCMn_UAS

DescriptionODU TCMn Section Unavailable Second

Impact on SystemThere are bit errors in the services. Determine the cause and resolve the problem in a timelymanner because the bit errors have affected the signal transmission quality.









Issue 08 (2011-10-30)

Procedure

Step 1 Refer to the method of handling the ODU_TCMn_DEG or ODU_TCMn_EXC alarm.

----End


5.68 OOPRL

DescriptionOptical Output Power Return Loss

It includes:

l OOPRLMAX: maximum value of the optical output power return loss within a time periodl OOPRLMIN: minimum value of the optical output power return loss within a time periodl OOPRLCUR: current value of the optical output power return loss

Impact on SystemServices may be interrupted.

Generation Principle and Possible CausesThe fiber near the board is cut, improperly bent, or squeezed, or the fiber connector is improperlyconnected to the board interface.


RL_CRITICAL_HI This alarm is generated when the return loss is higher than the upperthreshold of the return loss alarm.

RL_CRITICAL_LOW

This alarm is generated when the return loss is lower than the lowerthreshold of the return loss alarm.

Procedure

Step 1 Refer to the method of handling the RL_CRITICAL_HI or RL_CRITICAL_LOW.

----End




5-59

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 meansthere are one or more data blocks containing error bits during transmission.

Related Alarms


SM_BIP8_OVER OTU SM section bit interleaved parity exceeds threshold. The alarmis generated when the number of BIP8 bit errors of the SM section inthe optical channel data unit layer exceeds the threshold.

SM_BIP8_SD OTU SM section bit interleaved parity deterioration. The alarm isgenerated when the number of BIP8 bit errors of the SM section inthe optical channel data unit layer exceeds the degraded threshold.

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





Issue 08 (2011-10-30)

Impact on System

When the value is not 0, it indicates that there are bit errors in the services. When the value islarge, determine the cause and solve the problem in a timely manner to avoid any alarm, thus toensure the signal transmission quality.


OTU section background block errors are detected by checking the received parity bits. Thebackground block error refers to a data block where at least one bit error is generated during thetransmission. Background block error ratio of the OTU section refers to the ratio of the numberof background block errors of the OTU section to the number of all blocks minus the numberof blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocksper second].

Related Alarms




Procedure


----End

Related Information

None

5.71 OTU_ES

Description

OTU Errored Second

Impact on System




5-61

Generation Principle and Possible CausesOTU error is detected by checking the received parity bit. An errored second contains more thanone error block.




Procedure


----End


5.72 OTU_FEBBE

DescriptionOTU SM Section Far End Background Block Error


Generation Principle and Possible CausesOTU SM Section error is detected by checking the received parity bit. The background blockerror means there are one or more data blocks containing error bit during transmission. And thefar end background block error refers to the background block error detected at the opposite end.





Issue 08 (2011-10-30)


SM_BDI OTU SM section backward defect indication. The alarm is transferredin the upstream direction of the services, indicating the detected signalfailure.

SM_BEI OTU SM section backward error indication. If the board detects thatthe input signals contain the SM-BIP8 bit errors, it inserts the SM_BEIalarm back to the upstream board. The alarm is generated when theupstream station detects that the BEI flag in the OCH-OH of the SMsection of the received signals is true.

Procedure

Step 1 Refer to the method of handling the SM_BEI.

----End


5.73 OTU_FEBBER

DescriptionOTU SM Section Ratio of Far End Background Block Error

Impact on SystemWhen the value is not 0, it indicates that there are bit errors in the services. When the value islarge, determine the cause and solve the problem in a timely manner to avoid any alarm, thus toensure the signal transmission quality.

Generation Principle and Possible CausesOTU SM section background block errors are detected by checking the received parity bits. Thebackground block error refers to a data block where at least one bit error is generated during thetransmission. Background block error ratio of the OTU SM section refers to the ratio of thenumber of background block errors of the OTU SM section to the number of all blocks minusthe number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second]. And the ratio of far end background block error refers to the ratioof background block error detected at the opposite end.



5-63

Related Alarms




Procedure


----End

Related Information

None

5.74 OTU_FEES

Description

OTU SM Section Far End Errored Second

Impact on System

There are bit errors in the services on a far-end NE. If the number of block errors increases,determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensurethe signal transmission quality.


OTU SM Section error is detected by checking the received parity bit. An errored second containsmore than one error block. And the far end errored second refers to the errored second detectedat the opposite end.

Related Alarms







Issue 08 (2011-10-30)



Procedure


----End


5.75 OTU_FESES

DescriptionOTU SM Section Far End Severely Errored Second

Impact on SystemThere are bit errors in the services on a far-end NE. Determine the cause and solve the problemin a timely manner because the bit errors have affected the signal transmission quality.

Generation Principle and Possible CausesOTU SM Section error is detected by checking the received parity bit. During a severely erroredsecond, there is at least one defect or 30% of data blocks are error blocks. And the far end severelyerrored second refers to the severely errored second detected at the opposite end.






5-65

Procedure


----End

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) refersto the second where the checked signals contain a minimum of 30% block errors or at least onedefect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certainperiod of time to the total available time. Far end severely errored second ratio refers to the ratioof errored seconds that are detected at the far end.

Related Alarms




Procedure


----End





Issue 08 (2011-10-30)

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 fromthe beginning of the 11th second, and the former 10 severely errored seconds are counted asunavailable. If the severely errored second disappears for more than 10 seconds, the availabletime starts from the beginning of the 11th second, and the former 10 seconds are counted asavailable.And the far end unavailable second refers to the unavailable second detected at theopposite end.

Related Alarms




Procedure


----End

Related Information

None



5-67

5.78 OTU_SES

DescriptionOTU Severely Errored Second

Impact on SystemThere are severely errored second in the services. Determine the cause and solve the problemin a timely manner because the bit errors have affected the signal transmission quality.

Generation Principle and Possible CausesError is detected by checking the received parity bit. During a severely errored second, there isat least one defect or 30% of data blocks are error blocks.




Procedure


----End


5.79 OTU_SESR

DescriptionOTU Ratio of Severely Errored Second

Impact on SystemThere are severely errored second in the services. Determine the cause and solve the problemin a timely manner because the bit errors have affected the signal transmission quality.





Issue 08 (2011-10-30)

Generation Principle and Possible CausesBit errors are detected by checking the received parity bits. Severely errored second (SES) refersto the second where the checked signals contain a minimum of 30% block errors or at least onedefect occurs. Severely errored second (SES) ratio refers to the ratio of SES count in a certainperiod of time to the total available time.




Procedure


----End


5.80 OTU_SM_BIP8

DescriptionOTU SM Section BIP8


Generation Principle and Possible CausesThis performance event shows the number of errors that a board with an OTN interface detectsin section monitoring through the BIP8 check. Normally, it should be zero.



5-69




ProcedureStep 1 Refer to the method of handling the SM_BIP8_SD.

----End


5.81 OTU_UAS

DescriptionOTU Unavailable Second










Issue 08 (2011-10-30)

Procedure


----End

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 occurin the services.


IAE is defined to allow the S-CMEP ingress point to inform its peer S-CMEP egress point thatan alignment error in the incoming signal has been detected.

Related Alarms


SM_IAE The optical channel transport unit (OTU) layer SM section introducedalignment errors alarm. When the board detects the slip frame, itinserts the SM_IAE flag to the downstream board. The SM_IAEalarm is reported when the downstream board detects that the receivedOTN frames contains the IAE flag.

Procedure

Step 1 Refer to the method of handling the SM_IAE.

----End

Related Information

None



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 occurin the services.


It is used to convey in the upstream direction an incoming alignment error (IAE) condition thatis 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 monitoredby the spectrum analyzer unit.

It includes:

l PCLSOPMAX: stands for the maximum value during a period of time.

l PCLSOPMIN: stands for the minimum value during a period of time.

l PCLSOPCUR: stands for the current value.

Impact on System

None





Issue 08 (2011-10-30)


The MCA board analyzes the multiplexed optical signals, selects a channel of signal to checkits 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 analyzerunit.

It includes:

l PCLSSNMAX: stands for the maximum value during a period of time.l PCLSSNMIN: stands for the minimum value during a period of time.l PCLSSNCUR: stands for the current value.

Impact on System

None


The MCA board analyzes the multiplexed optical signals, checks and calculates the OSNR of achannel of signal.

Related Alarms

None

Procedure

Step 1 None

----End



5-73


5.86 PCLSWL

DescriptionPer-channel Central Wavelength, indicating the central wavelength of a channel among opticalsignals monitored by the spectrum analyzer unit.

It includes:

l PCLSWLMAX: stands for the maximum value during a period of time.l PCLSWLMIN: stands for the minimum value during a period of time.l PCLSWLCUR: stands for the current value.


Generation Principle and Possible CausesThe MCA board analyzes the multiplexed optical signals, selects a channel of signal to checkits central wavelength.

Related AlarmsNone

Procedure

Step 1 None

----End


5.87 PCLSWLO

DescriptionPer-channel Central Wavelength Deviation, indicating the deviation between the ITU-T standardwavelength and the wavelength of a channel among optical signals monitored by the spectrumanalyzer unit.

It includes:

l PCLSWLOMAX: stands for the maximum value during a period of time.





Issue 08 (2011-10-30)

l PCLSWLOMIN: stands for the minimum value during a period of time.

l PCLSWLOCUR: stands for the current value.

Impact on System

None


The MCA board analyzes the multiplexed optical signals, checks and calculates the centralwavelength 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 PMUTMPMAX: stands for the maximum value during a period of time.

l PMUTMPMIN: stands for the minimum value during a period of time.

l PMUTMPCUR: stands for the current value.

Impact on System

Services on the board may be affected when the ambient temperature of the board exceeds thethreshold.


It is generated by the temperature check circuit of the PMU board to show the working ambienttemperature of PMU.



5-75

Related Alarms


TEMP_ALARM The temperature threshold crossing alarm. This alarm is generatedwhen the board ambient temperature crosses the board temperaturethreshold.

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 PUMPOOPMAX: stands for the maximum value during a period of time.

l PUMPOOPMIN: stands for the minimum value during a period of time.

l 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 checkresult into PUMPOOP to show the pump optical power of Raman amplifier board.

Related Alarms


OUT_PWR_HIGH Output optical power too high alarm. This alarm is generated whenthe laser output optical power crosses the upper threshold.





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 PUMPTMPMAX: denotes the maximum value during a period of time.l PUMPTMPMIN: denotes the minimum value during a period of time.l PUMPTMPCUR: denotes the current value.

Impact on System

Services on the board may be affected when the ambient temperature of the board exceeds thethreshold.


To obtain this performance event, perform a check by the check circuit. Then calculate the resultwith software for conversion.


PUM_TEM_ALM Working temperature of the pump laser exceeds the threshold. Thisalarm is generated when the pump laser operating temperature of theoptical amplifier unit exceeds the threshold.

Procedure

Step 1 Refer to the method of handling the PUM_TEM_ALM.

----End

Related Information

None



5-77

5.91 RSBBE

DescriptionRS Background Block Error

Impact on SystemThere are bit errors in the services. If the number of block errors increases, determine the causeand solve the problem in a timely manner to avoid any alarm, thus to ensure the signaltransmission quality.

Generation Principle and Possible CausesThe regenerator section errors are detected by checking the B1 byte. The background block errormeans there are one or more data blocks containing error bits during transmission.


B1_EXC Regenerator section (B1) excessive errors.The alarm is generated when the receivedsignals in SDH frame degrades and the B1 biterrors in the multiplex section exceeds thethreshold.

B1_SD Regenerator section (B1) excessive errors.The alarm is generated when the receivedsignals in SDH frame degrades and the B1 biterrors in the multiplex section exceeds thesignal degrade (SD) threshold.

Procedure


----End


5.92 RSCSES

DescriptionRS Consecutive Severely Errored Second





Issue 08 (2011-10-30)


Generation Principle and Possible CausesThe regenerator section errors are detected by checking the B1 byte. During a severely erroredsecond, there is at least one defect or 30% of data blocks are error blocks. While the consecutiveseverely errored second means the severely errored second appears consecutively, accompaniedby the B1_EXC alarm. It might result in service interruption.




Procedure


----End


5.93 RSES

DescriptionRS Errored Second




5-79

Generation Principle and Possible CausesThe regenerator section errors are detected by checking the B1 byte. The RS errored secondmeans there are more than one error block transmitted in this second.




Procedure


----End


5.94 RSOFS

DescriptionRS Out-of-Frame Second

Impact on SystemThis alarm indicates that the frame headers cannot be identified in five or more consecutiveframes in the received signals of the line board. The board enters the out-of-frame state. As aresult, the services are unavailable. If the out-of-frame state lasts for 3 ms, the board enters theloss-of-frame state. The R_LOF alarm is generated.

Generation Principle and Possible CausesOut-Of-Frame (OOF) refers to the loss of framing bytes and the OOF second contains at leastone OOF.

OOF turns to be LOF (Loss Of Frame) if it lasts more than 3ms.





Issue 08 (2011-10-30)


R_OOF Out of frame on receiving line. This alarm isgenerated when the headers of consecutivefive frames fail to be detected.

R_LOF Loss of frame on receiving line. This alarm isgenerated when the frame alignmentprocessing is out of frame (OOF) inconsecutive 3ms.

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 normalrange 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 attenuationby adding a fix attenuator or a variable optical attenuator (VOA).


----End


5.95 RSSES

DescriptionRS Severely Errored Second


Generation Principle and Possible CausesThe regenerator section errors are detected by checking the B1 byte. During a severely erroredsecond, there is at least one defect or 30% of blocks are error blocks.



5-81




Procedure


----End


5.96 RSUAS

DescriptionRS Unavailable Second


Generation Principle and Possible CausesThe regenerator section errors are detected by checking the B1 byte. If the severely erroredseconds last for more than 10 seconds, the unavailable second starts from the beginning of the11th second, and the former 10 severely errored seconds are counted as unavailable. If theseverely errored second disappears for more than 10 seconds, the available time starts from thebeginning of the 11th second, and the former 10 seconds are counted as available.





Issue 08 (2011-10-30)




Procedure


----End


5.97 SUMIOP

DescriptionInput Optical Power

It includes:

l SUMIOPMAX: stands for the maximum value during a period of time.l SUMIOPMIN: stands for the minimum value during a period of time.l SUMIOPCUR: stands for the current value.

Impact on SystemIf the total input optical power is excessively high, the optical modules of the local board andthe downstream board may be damaged. As a result, bit errors are generated in the services oreven the services are interrupted. If the total input optical power is excessively low, the single-wavelength optical signals that are output by the board may be lost. As a result, bit errors aregenerated in the services or even the services are interrupted.

Generation Principle and Possible CausesTo obtain this performance event, perform a check using the check circuit, and then calculatethe result with software for conversion.



5-83

SUMIOP is the total input optical power of demultiplexer and the optical amplifier board.

Related Alarms


IN_PWR_HIGH It is generated when the optical power input by board is higher thanthe upper threshold.

IN_PWR_LOW It is generated when the optical power input by board is lower thanthe lower threshold.

SUM_INPWR_HI It is generated when the detected total input optical power is higherthan the upper threshold.

SUM_INPWR_LOW

It is generated when the detected total input optical power is lowerthan the lower threshold.

Procedure

Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than thehistory 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 orSUM_INPWR_HI alarm.

Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than thehistory 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 orSUM_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 typesthat are supported by the total input power alarm.

5.98 SUMOOP

Description

Output Optical Power

It includes:

l SUMOOPMAX: stands for the maximum value during a period of time.

l SUMOOPMIN: stands for the minimum value during a period of time.

l SUMOOPCUR: stands for the current value.





Issue 08 (2011-10-30)

Impact on SystemThe total output power brings impact on the services. If the total output power is excessivelyhigh, the input optical power of the downstream board may be very high. As a result, bit errorsare generated in the services or even the services are interrupted. In addition, the receiver moduleof the OTU at the downstream station may be damaged. If the total output power is excessivelylow, the input optical power of the downstream board may be very low. As a result, bit errorsare generated in the services or even the services are interrupted.

Generation Principle and Possible CausesTo obtain this performance event, perform a check using the check circuit, and then calculatethe 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 opticalpower through the "OUT" port, while in an amplifier board, the input signals pass the amplifierand then output the total optical power through the "OUT" port.


OUT_PWR_HIGH It is generated when the optical power output by board is higher thanthe upper threshold.

OUT_PWR_LOW It is generated when the optical power output by board is lower thanthe lower threshold.

SUM_OUTPWR_HI

It is generated when the detected total input optical power is higherthan the upper threshold.

SUM_OUTPWR_LOW

It is generated when the optical power output by board is 1dB lowerthan the lower threshold.

Procedure

Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than thehistory 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 orSUM_OUTPWR_HI alarm.

Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than thehistory 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 orSUM_OUTPWR_LOW alarm.

Step 3 If an alarm is generated, refer to the proper handling procedure.

----End



5-85

Related InformationThe board types that are supported by the output power alarm are different from the board typesthat are supported by the total output power alarm.

5.99 WCV

DescriptionPump Laser Working Current, also called Pump Laser Driver Current or Pump Laser BiasCurrent.

It includes:

l WCVMAX: stands for the maximum value during a period of time (in 1mA).l WCVMIN: stands for the minimum value during a period of time (in 1mA).l WCVCUR: stands for the current value (in 1mA).

Impact on SystemWhen the pump laser works normally, there is no impact on the services. If an alarm is generated,determine the cause.

Generation Principle and Possible CausesWCV indicates the pump laser driver current of an optical amplifier board. The optical amplifierboard amplifies the input signal using the pump laser driven by pump laser working current.


PUM_BCM_ALM The board reports this alarm when the detected pump laser drivercurrent is higher than the threshold due to laser exceptions caused bylaser aging, or over-high/low ambient temperature.

LSR_WILL_DIE The board reports this alarm when the pump laser driver current ishigher than the termination threshold due to laser aging.

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






Issue 08 (2011-10-30)

A Glossary

A

Auto negotiation The negotiation mode that is set on the communication equipment. When the autonegotiation mode is enabled, the equipment sets its working mode and rate throughnegotiation based on the mode and rate of the opposite equipment.

B

Bandwidth Information-carrying capacity of a communication channel. Analog bandwidth is therange of signal frequencies that can be transmitted by a communication channel ornetwork.

Bit Error Rate The ratio of the errored bit count to the transmitted bit count in a certain period of time.In the digital communication system, bit error rate is the ratio of the errored bit count tothe transmitted bit count in a typical period of time.

Broadcast The act of sending a frame addressed to all stations on the network.

C

Channel The trail on the channel layer.

Client Server A terminal device (computer or workstation) that sends instructions to the server anddisplays the results through the user interface.

Clock tracing The method to keep the time on each node being synchronized with a clock source in anetwork.

Concatenate A combination process. The process combines multiple virtual containers (VCs). Then,the capacity of the combined VCs can used as the capacity of a single VC and the bitsequence is complete.

Connection A "transport entity" which consists of an associated pair of "unidirectional connections"capable of simultaneously transferring information in opposite directions between theirrespective inputs and outputs.

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference A Glossary


A-1

D

DCM Dispersion Compensation Module. A module, which contains dispersion compensationfibers 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 ofoptical fiber doped with the rare-earth element Erbium and the energey level jump ofErbium ions activated by pump sources. When the amplifier passes the external lightsource pump, it amplifies the optical signals in a specific wavelength range.

Ethernet A data link level protocol comprising the OSI model's bottom two layers. It is a broadcastnetworking technology that can use several different physical media, including twistedpair cable and coaxial cable. Ethernet usually uses CSMA/CD. TCP/IP is commonlyused with Ethernet networks.

F

Fiber jumper The fiber which is used to connect the subrack with the ODF, subrack or connect theboard interfaces.

Forward ErrorCorrection

A data encoding technology. It is a method to control errors in communication. In thismethod, extra (redundant) bits are inserted into the data stream towards other equipmentto control errors. The equipment at the receive end can use these redundant bits to detecterrors and correct errors if possible.

Frame A cyclic set of consecutive time slots in which the relative position of each time slot canbe identified.

Full duplex Pertaining to both parties that can send and receive data at the same time on thecommunication link.

G

Gain The ratio between the optical power from the input optical interface of the opticalamplifier and the optical power from the output optical interface of the jumper fiber,which expressed in dB.

Grooming A process that multiplexes multiple channels of low-rate signals into one or severalchannels of required signals.

L

Label A mark on a cable, a subrack, or a cabinet for identification.

Laser The device that generates the directional light covering a narrow range of wavelengths.Laser light is more coherent than ordinary light. Semiconductor diode lasers are the usedlight source in fiber-optic system.

A Glossary



A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

M

Main Topology The default T2000 client interface, a basic component of the human-machine interactiveinterface. The topology clearly shows the structure of the network, the alarms of differentNEs, subnets in the network, the communication status as well as the basic networkoperation status. All topology management functions are accessed here.

Multiplexing A procedure by which multiple lower order path layer signals are adapted into a higherorder path or the multiple higher order path layer signals are adapted into a multiplexsection.

O

Opposite station/opposite station board

The opposite station is a service-specific concept. As shown in Figure A-1, if station Ais the local station, station C is the opposite station for service λ1 and station B is theopposite station for service λ2. The opposite station board is specific to the transmittingor 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 oppositeto OTU1 is OTU3.

Figure A-1 Service flow

Station B

Clinetside

OTU1

WDMside

OTU2

Station A

Clientside

WDMside

OTU3

OTU4

Station C

FIU

FIU

OADM

OADM

OADM

OADM

FIU

FIU

OTU5

OTU6

λ1

λ2 λ3

λ1

λ2 λ3

Optical spectrumanalyzer

An instrument that scans the spectrum to record power, measures the value of lossinsertion and tests the performance of the wavelength and optical signal noise ratio(OSNR) of each channel.

Optical switch A passive component possessing two or more ports which selectively transmits, redirects,or blocks optical power in an optical fiber transmission line.

OSNR Optical Signal-to-Noise Ratio. Ratio of the optical power of the transmitted optical signalto the noise on the received signal.

Overhead A message that is transmitted on the optical network layer and does not need to associatewith a specific connection. For example, such an auxiliary channel can be used as adigital communication channel between management entities to transmit managementdata.

Pointer An indicator whose value defines the frame offset of a virtual container with respect tothe frame reference of the transport entity on which it is supported.



A-3

R

Regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,waveforms and timing of its signal elements are constrained within specified limits.

Route The path a trail takes.

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 thetelecommunication management network structure. That is, the T2000 is a subnetworkmanagement system. The T2000 provides all management functions at the NE layer andsome of the management functions at the network layer.

Timeslot Single timeslot on a E1 digital interface—that is, a 64-kbps, synchronous, full-duplexdata channel, typically used for a single voice connection.

Trail A type of transport entity, mainly engaged in transferring signal from the input of thetrail source to the output of the trail sink, and monitoring the integrality of the transferredsignal.

U

Upstream station/downstream station

For the station where signals are received, the station where signals are transmitted andthe station where signals just pass through are upstream stations. As shown in FigureA-2, service λ1 traverses from station A, to station B, and finally to station C. Station Aand station B are upstream stations of station C. The service signals can be ECC signals,GE signals, or orderwire signals.

Conversely, station B and station C are downstream stations for station A.

Figure A-2 Service flow

Station B

Clinetside

OTU1

WDMside

OTU2

Station A

Clientside

WDMside

OTU3

OTU4

Station C

FIU

FIU

OADM

OADM

OADM

OADM

FIU

FIU

OTU5

OTU6

λ1

λ2 λ3

λ1

λ2 λ3

A Glossary



A-4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

User The user of the T2000 client, and the user and password define the correspondingauthority of operation and management of the T2000.

W

Wander In telecommunication, wander are long-term random variations of the significant instantsof a digital signal from their ideal positions.



A-5

B Acronyms and Abbreviations

A

AIS Alarm Indication Signal

API Access Point Identifiers

B

BDI Backward Defect Indication

BEI Backward Error Indication

BIP Bit Interleaved Parity

BITS Building Integrated Timing Supply System

C

CRC Cyclical Redundancy Check

D

DAPI Destination Access Point Identifier

DSP Digital Signal Processing

E

EDFA Erbium-Doped Fiber Amplifier

F

FEC Forward Error Correction

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference B Acronyms and Abbreviations


B-1

FPGA Field Programmable Gate Array

G

GE Gigabit Ethernet

H

HP Higher Order Path

HDB High Density Bipolar Code

HPI Higher Order Path Interface

I

IAE Incoming Alignment Error

L

LACP Link Aggregation Control Protocol

LOF Loss Of Frame

LOS Loss Of Signal

M

MFAS MultiFrame Alignment Signal

MS Multiplex Section

O

OCI Open Connection Indication

ODU Optical Channel Data Unit

OOF Out Of Frame

OPU Optical Channel Payload Unit

OTN Optical Transmission Network

P

PIN Positive Intrinsic Negative

B Acronyms and Abbreviations



B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 08 (2011-10-30)

PM Path Monitoring

PT Payload Type

R

RDI Remote Defect Indication

REI Remote Error Indication

S

SAPI Source Access Point Identifiers

SD Signal Degrade

SDH Synchronous Digital Hierarchy

SES Severely Errored Second

SF Signal Fail

SM Section Monitoring

T

TCM Tandem Connection Monitoring

TIM Trace Identifier Mismatch

TTI Trail Trace Identifier

U

UAS Unavailable Second

OptiX BWS 1600G Backbone DWDM Optical TransmissionSystemAlarms and Performance Events Reference B Acronyms and Abbreviations


B-3

91501321 00482837 alarms and performance events reference v100r007 08

Documents