Alarms and Performance Events Reference (V100R006C01 - 02)

OptiX OSN 8800/6800/3800 V100R006C01
Alarms and Performance Events Reference

Issue Date 02 2011-10-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 02 (2011-10-31)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name OptiX OSN 8800 OptiX OSN 6800 OptiX OSN 3800 iManager U2000 iManager U2000 Web LCT Version V100R006C01 V100R006C01 V100R006C01 V100R005C00 V100R005C00
Intended Audience
The intended audience of this document are: l l System maintenance engineer Network monitoring engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description
DANGER
Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
WARNING
Issue 02 (2011-10-31)
ii
About This Document
Symbol
Description
CAUTION
TIP
Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
NOTE
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Updates in Issue 02 (2011-10-31) Based on Product Version V100R006C01

Update 2 Alarm List Description l 2.2.63 NPO2 Board Alarm List is modified. l 2.2.65 NQ2 Board Alarm List is modified. l 2.2.66 NS2 Board Alarm List is modified. l 2.2.62 ND2 Board Alarm List is modified.
Issue 02 (2011-10-31)
iii
About This Document
Update 4 Alarm Processing
Description l 4.277 TIME_LOS is modified. l 4.62 EXT_TIME_LOC is modified. l 4.278 TIME_NO_TRACE_MODE is modified. l 4.177 OPA_FAIL_INDI is modified. l 4.93 LASER_HAZARD_WARNING is modified. l 4.29 CFCARD_FAILED is modified. l 3.37 POWER_FAIL is modified. l 4.63 FAN_FAIL is modified.
5 Performance Event List
l 5.2.44 NQ2 Board Performance Event List is modified. l 5.2.47 NS2 Board Performance Event List is modified. l 5.2.43 ND2 Board Performance Event List is modified.

Update 2 Alarm List Description l 2.2.3 BMD4 Board Alarm List is added. l 2.2.4 BMD8 Board Alarm List is added. l 2.2.22 ELQX Board Alarm List is added. l 2.2.74 PTQX Board Alarm List is added. l 2.2.39 LOA Board Alarm List is added. l 2.2.64 NPO2E Board Alarm List is added. l 2.2.65 NQ2 Board Alarm List is modified. l 2.2.62 ND2 Board Alarm List is modified. l 2.2.66 NS2 Board Alarm List is modified. l 2.2.101 TDX Board Alarm List is modified. l 2.2.109 TQX Board Alarm List is modified. l 2.2.68 OAU1 Board Alarm List is modified. l 2.2.55 M40 Board Alarm List is modified. l 2.2.10 D40 Board Alarm List is modified. l 2.2.54 M40V Board Alarm List is modified. l 2.2.63 NPO2 Board Alarm List is modified. l 2.2.23 ENQ2 Board Alarm List is modified. l 2.2.81 SCC Board Alarm List is modified.
Issue 02 (2011-10-31)
iv
About This Document
Description l 4.4 ALS_ACTIVE is added. l 4.115 MAINBD_SUBBD_MISMATCH is added. l 4.225 RL_CRITICAL_HI is added. l 4.226 RL_CRITICAL_LOW is added.
l 5.2.9 ELQX Board Performance Event List is added. l 5.2.54 PTQX Board Performance Event List is added. l 5.2.24 LOA Board Performance Event List is added. l 5.2.46 NPO2E Board Performance Event List is added. l 5.2.58 SCC Board Performance Event List is added.

Update 2 Alarm List Description l 2.2.3 BMD4 Board Alarm List is added. l 2.2.4 BMD8 Board Alarm List is added. l 2.2.22 ELQX Board Alarm List is added. l 2.2.74 PTQX Board Alarm List is added. l 2.2.63 NPO2 Board Alarm List is modified. 4 Alarm Processing l 4.85 IPA_SHUT is added. l 4.177 OPA_FAIL_INDI is modified. l 4.131 NO_BD_SOFT is modified. 5 Performance Event List l 5.2.9 ELQX Board Performance Event List is added. l 5.2.54 PTQX Board Performance Event List is added.
Issue 02 (2011-10-31)
About This Document

Update 2 Alarm List Description l 2.2.97 SXH Board Alarm List is added. l 2.2.102 THA Board Alarm List is added. l 2.2.104 TOA Board Alarm List is added. l 2.2.109 TQX Board Alarm List is modified. l 2.2.63 NPO2 Board Alarm List is modified. l BMD4, BMD8, ELQX, PTQX are deleted. 4 Alarm Processing 5 Performance Event List l 4.29 CFCARD_FAILED is added. l 4.60 EXT_MODULE_OFFLINE is added. l 5.2.73 SXH Board Performance Event List is added. l 5.2.78 THA Board Performance Event List is added. l 5.2.80 TOA Board Performance Event List is added. l 5.2.85 TQX Board Performance Event List is modified. l ELQX, PTQX are deleted.

Update 2 Alarm List Description l 2.2.11 DAS1 Board Alarm List is added. l 2.2.118 WSMD9 Board Alarm List is added. l 2.2.119 XCH Board Alarm List is modified. l 2.2.2 AUX Board Alarm List is modified. 4 Alarm Processing 5 Performance Event List l 4.51 ETH_MISCONNECT is added. l 4.248 SUBRACK_COMM_PS is added. l 5.2.2 DAS1 Board Performance Event List is added. l 5.2.94 WSMD9 Board Performance Event List is added.
Issue 02 (2011-10-31)
vi
About This Document

Update 2 Alarm List Description l 2.2.38 LEX4 Board Alarm List is modified. l 2.2.37 LEM24 Board Alarm List is modified. l 2.2.101 TDX Board Alarm List is modified. l 2.2.61 MR8V Board Alarm List is modified. l 2.2.19 EFI1 Board Alarm List is modified. l 2.2.20 EFI2 Board Alarm List is modified. 5 Performance Event List l 5.2.12 HSC1 Board Performance Event List is modified. l 5.2.43 ND2 Board Performance Event List is modified. l 5.2.47 NS2 Board Performance Event List is modified. l 5.2.77 TDX Board Performance Event List is modified. l 5.2.85 TQX Board Performance Event List is modified. l 5.2.28 LQMS Board Performance Event List is modified. l 5.2.27 LQMD Board Performance Event List is modified. l 5.2.29 LQM Board Performance Event List is modified. l 5.2.83 TQM Board Performance Event List is modified. l 5.2.82 TOM Board Performance Event List is modified.

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

Update 4 Alarm Processing Description l 4.52 ETH_SERVICE_CONFIG_FAIL is added. l 4.235 SPAN_LOSS_HIGH is added. l 4.236 SPAN_LOSS_LOW is added. l 4.257 SWDL_BD_EXCLUDE is added. l ALC_LINE_WASTAGE is deleted.
Issue 02 (2011-10-31)
vii
About This Document

This issue is the first official release for OptiX OSN 8800/6800/3800 V100R005C00. In this release, the manuals for OptiX OSN 8800 V100R002C02, OptiX OSN 6800 V100R004C04, and OptiX OSN 3800 V100R004C04 are combined into one manual. Update Whole manual Description l This manual provides descriptions according to product series OptiX OSN 8800, OptiX OSN 6800, and OptiX OSN 3800. Any difference between the products is described in the manual. l The equipment name is changed from OptiX OSN 8800 I to OptiX OSN 8800 T32 or from OptiX OSN 8800 II to OptiX OSN 8800 T64. 2 Alarm List l 2.2.23 ENQ2 Board Alarm List is added. l 2.2.37 LEM24 Board Alarm List is added. l 2.2.38 LEX4 Board Alarm List is added. l 2.2.63 NPO2 Board Alarm List is added. l 2.2.72 OPM8 Board Alarm List is added. l 2.2.83 SFIU Board Alarm List is added. l 2.2.84 ST2 Board Alarm List is added. 3 Common Alarm Processing l 3.3 BOOTROM_BAD is modified. l 3.4 BUS_ERR is modified. l 3.7 COMMUN_FAIL is modified. l 3.29 ODUk_PM_SSF is modified. l 3.33 OTUk_LOF is modified. l 3.34 OTUk_SSF is modified. l 3.48 SWDL_NEPKGCHECK is modified. l 3.50 TEMP_OVER is modified.
Issue 02 (2011-10-31)
viii
About This Document
Description l ALC_LINE_WASTAGE is added. l 4.2 ALC_ADJUST_FAIL is added. l 4.3 ALC_WAIT_ADJUST is added. l 4.12 APE_ADJUST_FAIL is added. l 4.13 APE_ADJUST_PEND is added. l 4.65 FEATURE_WITHOUT_LICENSE is added. l 4.73 FWD_PKT_LOSS is added. l 4.95 LCS_DAYS_OF_GRACE is added. l 4.96 LCS_EXPIRED is added. l 4.97 LCS_FILE_NOT_EXIST is added. l 4.126 MULTI_RPL_OWNER is added. l 4.134 NTP_SYNC_FAIL is added. l 4.184 OSC_BDI is added. l 4.185 OSC_DEG is added. l 4.231 SEC_RADIUS_FAIL is added. l 4.282 VCAT_LOA is added. l 4.289 WAVE_ADD_ABN is added. l 4.290 WAVE_DROP_ABN is added.
l 5.2.10 ENQ2 Board Performance Event List is added. l 5.2.22 LEM24 Board Performance Event List is added. l 5.2.23 LEX4 Board Performance Event List is added. l 5.2.45 NPO2 Board Performance Event List is added. l 5.2.53 OPM8 Board Performance Event List is added. l 5.2.70 ST2 Board Performance Event List is added.
Issue 02 (2011-10-31)
ix
About This Document
Update 6 Performance Event Processing
Description l 6.17 FEC_AFT_CORER_FLOAT is added. l 6.20 FEC_BEF_CORER_FLOAT is added. l 6.81 OSC_BBE is added. l 6.82 OSC_BBER is added. l 6.83 OSC_BIAES is added. l 6.84 OSC_ES is added. l 6.85 OSC_FEBBE is added. l 6.86 OSC_FEBBER is added. l 6.87 OSC_FEES is added. l 6.88 OSC_FESES is added. l 6.89 OSC_FESESR is added. l 6.90 OSC_FEUAS is added. l 6.91 OSC_IAES is added. l 6.92 OSC_SES is added. l 6.93 OSC_SESR is added. l 6.94 OSC_UAS is added.
Issue 02 (2011-10-31)
Contents
Contents
About This Document.....................................................................................................................ii 1 Overview.........................................................................................................................................1
1.1 Alarm Level........................................................................................................................................................2 1.2 Alarm Category..................................................................................................................................................2 1.3 Performance Event Category..............................................................................................................................3 1.4 Alarm Signal Flow..............................................................................................................................................4 1.4.1 Overview...................................................................................................................................................4 1.4.2 Non-Convergent OTU Processing Standard SDH Signals........................................................................6 1.4.3 Non-Convergent OTU Processing Standard OTN Signals........................................................................9 1.4.4 Convergent OTU Processing Standard SDH Signals..............................................................................12 1.4.5 Convergent OTU Processing Standard OTN Signals..............................................................................15 1.4.6 Regenerating OTU...................................................................................................................................18 1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function................................................20 1.4.8 OTU Processing GE Signals....................................................................................................................21 1.4.9 Optical-Layer Alarm Signal Processing on OTN....................................................................................25 1.5 Suppression Relationship of Alarms................................................................................................................29 1.5.1 Suppression of OTN Alarms...................................................................................................................29 1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment Alarms....................31 1.6 Performance Event Suppression by Alarms.....................................................................................................32
2 Alarm List......................................................................................................................................34
2.1 Product Alarm List...........................................................................................................................................35 2.1.1 Alarm List A............................................................................................................................................35 2.1.2 Alarm List B............................................................................................................................................36 2.1.3 Alarm List C............................................................................................................................................37 2.1.4 Alarm List D............................................................................................................................................37 2.1.5 Alarm List E............................................................................................................................................38 2.1.6 Alarm List F.............................................................................................................................................39 2.1.7 Alarm List G............................................................................................................................................40 2.1.8 Alarm List H............................................................................................................................................40 2.1.9 Alarm List I.............................................................................................................................................41 2.1.10 Alarm List J...........................................................................................................................................41 2.1.11 Alarm List K..........................................................................................................................................42 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
2.1.12 Alarm List L..........................................................................................................................................42 2.1.13 Alarm List M.........................................................................................................................................44 2.1.14 Alarm List N..........................................................................................................................................45 2.1.15 Alarm List O..........................................................................................................................................45 2.1.16 Alarm List P...........................................................................................................................................55 2.1.17 Alarm List R..........................................................................................................................................56 2.1.18 Alarm List S...........................................................................................................................................57 2.1.19 Alarm List T..........................................................................................................................................60 2.1.20 Alarm List V..........................................................................................................................................61 2.1.21 Alarm List W.........................................................................................................................................61 2.1.22 Alarm List X..........................................................................................................................................62 2.2 Board Alarm List..............................................................................................................................................62 2.2.1 ATE Board Alarm List............................................................................................................................62 2.2.2 AUX Board Alarm List...........................................................................................................................62 2.2.3 BMD4 Board Alarm List.........................................................................................................................63 2.2.4 BMD8 Board Alarm List.........................................................................................................................64 2.2.5 CMR1 Board Alarm List.........................................................................................................................64 2.2.6 CMR2 Board Alarm List.........................................................................................................................64 2.2.7 CMR4 Board Alarm List.........................................................................................................................64 2.2.8 CRPC Board Alarm List..........................................................................................................................64 2.2.9 D40V Board Alarm List..........................................................................................................................65 2.2.10 D40 Board Alarm List...........................................................................................................................65 2.2.11 DAS1 Board Alarm List........................................................................................................................65 2.2.12 DCU Board Alarm List..........................................................................................................................66 2.2.13 DCP Board Alarm List..........................................................................................................................66 2.2.14 DFIU Board Alarm List.........................................................................................................................67 2.2.15 DMR1 Board Alarm List.......................................................................................................................67 2.2.16 EAS2 Board Alarm List........................................................................................................................68 2.2.17 ECOM Board Alarm List......................................................................................................................69 2.2.18 EFI Board Alarm List............................................................................................................................69 2.2.19 EFI1 Board Alarm List..........................................................................................................................69 2.2.20 EFI2 Board Alarm List..........................................................................................................................70 2.2.21 EGSH Board Alarm List........................................................................................................................70 2.2.22 ELQX Board Alarm List.......................................................................................................................71 2.2.23 ENQ2 Board Alarm List........................................................................................................................73 2.2.24 FAN Board Alarm List..........................................................................................................................75 2.2.25 FIU Board Alarm List............................................................................................................................75 2.2.26 GFU Board Alarm List..........................................................................................................................76 2.2.27 HBA Board Alarm List..........................................................................................................................76 2.2.28 HSC1 Board Alarm List........................................................................................................................77 2.2.29 ITL Board Alarm List............................................................................................................................77 2.2.30 L4G Board Alarm List...........................................................................................................................78 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xii
Contents
2.2.31 LDGD Board Alarm List.......................................................................................................................79 2.2.32 LDGS Board Alarm List........................................................................................................................81 2.2.33 LDM Board Alarm List.........................................................................................................................82 2.2.34 LDMD Board Alarm List......................................................................................................................84 2.2.35 LDMS Board Alarm List.......................................................................................................................85 2.2.36 LDX Board Alarm List..........................................................................................................................87 2.2.37 LEM24 Board Alarm List......................................................................................................................88 2.2.38 LEX4 Board Alarm List........................................................................................................................90 2.2.39 LOA Board Alarm List..........................................................................................................................91 2.2.40 LOG Board Alarm List..........................................................................................................................93 2.2.41 LOM Board Alarm List.........................................................................................................................95 2.2.42 LQG Board Alarm List..........................................................................................................................97 2.2.43 LQMD Board Alarm List......................................................................................................................98 2.2.44 LQMS Board Alarm List.....................................................................................................................101 2.2.45 LQM Board Alarm List.......................................................................................................................105 2.2.46 LSQ Board Alarm List........................................................................................................................106 2.2.47 LSXLR Board Alarm List...................................................................................................................108 2.2.48 LSXL Board Alarm List......................................................................................................................110 2.2.49 LSXR Board Alarm List......................................................................................................................113 2.2.50 LSX Board Alarm List........................................................................................................................114 2.2.51 LWX2 Board Alarm List.....................................................................................................................118 2.2.52 LWXD Board Alarm List....................................................................................................................118 2.2.53 LWXS Board Alarm List.....................................................................................................................119 2.2.54 M40V Board Alarm List......................................................................................................................120 2.2.55 M40 Board Alarm List........................................................................................................................121 2.2.56 MCA4 Board Alarm List.....................................................................................................................121 2.2.57 MCA8 Board Alarm List.....................................................................................................................122 2.2.58 MR2 Board Alarm List........................................................................................................................122 2.2.59 MR4 Board Alarm List........................................................................................................................122 2.2.60 MR8 Board Alarm List........................................................................................................................123 2.2.61 MR8V Board Alarm List.....................................................................................................................123 2.2.62 ND2 Board Alarm List........................................................................................................................123 2.2.63 NPO2 Board Alarm List......................................................................................................................127 2.2.64 NPO2E Board Alarm List....................................................................................................................132 2.2.65 NQ2 Board Alarm List........................................................................................................................133 2.2.66 NS2 Board Alarm List.........................................................................................................................141 2.2.67 NS3 Board Alarm List.........................................................................................................................149 2.2.68 OAU1 Board Alarm List.....................................................................................................................156 2.2.69 OBU1 Board Alarm List......................................................................................................................157 2.2.70 OBU2 Board Alarm List......................................................................................................................158 2.2.71 OLP Board Alarm List........................................................................................................................158 2.2.72 OPM8 Board Alarm List.....................................................................................................................159 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
2.2.73 PIU Board Alarm List..........................................................................................................................160 2.2.74 PTQX Board Alarm List......................................................................................................................160 2.2.75 RDU9 Board Alarm List......................................................................................................................162 2.2.76 RMU9 Board Alarm List.....................................................................................................................162 2.2.77 ROAM Board Alarm List....................................................................................................................163 2.2.78 SBM2 Board Alarm List......................................................................................................................163 2.2.79 SC1 Board Alarm List.........................................................................................................................163 2.2.80 SC2 Board Alarm List.........................................................................................................................164 2.2.81 SCC Board Alarm List........................................................................................................................164 2.2.82 SCS Board Alarm List.........................................................................................................................171 2.2.83 SFIU Board Alarm List.......................................................................................................................171 2.2.84 ST2 Board Alarm List.........................................................................................................................171 2.2.85 SF64 Board Alarm List........................................................................................................................172 2.2.86 SF64A Board Alarm List.....................................................................................................................172 2.2.87 SFD64 Board Alarm List.....................................................................................................................173 2.2.88 SL64 Board Alarm List.......................................................................................................................174 2.2.89 SLH41 Board Alarm List....................................................................................................................175 2.2.90 SLD64 Board Alarm List....................................................................................................................175 2.2.91 SLO16 Board Alarm List....................................................................................................................176 2.2.92 SLQ16 Board Alarm List....................................................................................................................177 2.2.93 SLQ64 Board Alarm List....................................................................................................................177 2.2.94 STG Board Alarm List........................................................................................................................178 2.2.95 STI Board Alarm List..........................................................................................................................178 2.2.96 SXM Board Alarm List.......................................................................................................................179 2.2.97 SXH Board Alarm List........................................................................................................................179 2.2.98 TBE Board Alarm List........................................................................................................................179 2.2.99 TDC Board Alarm List........................................................................................................................180 2.2.100 TDG Board Alarm List......................................................................................................................180 2.2.101 TDX Board Alarm List......................................................................................................................181 2.2.102 THA Board Alarm List......................................................................................................................184 2.2.103 TMX Board Alarm List.....................................................................................................................185 2.2.104 TOA Board Alarm List......................................................................................................................189 2.2.105 TOG Board Alarm List......................................................................................................................191 2.2.106 TOM Board Alarm List.....................................................................................................................191 2.2.107 TQM Board Alarm List.....................................................................................................................194 2.2.108 TQS Board Alarm List......................................................................................................................197 2.2.109 TQX Board Alarm List......................................................................................................................198 2.2.110 TSXL Board Alarm List....................................................................................................................202 2.2.111 VA1 Board Alarm List......................................................................................................................204 2.2.112 VA4 Board Alarm List......................................................................................................................205 2.2.113 WMU Board Alarm List....................................................................................................................205 2.2.114 WSD9 Board Alarm List...................................................................................................................205 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiv
Contents
2.2.115 WSM9 Board Alarm List..................................................................................................................206 2.2.116 WSMD2 Board Alarm List................................................................................................................207 2.2.117 WSMD4 Board Alarm List................................................................................................................207 2.2.118 WSMD9 Board Alarm List................................................................................................................208 2.2.119 XCH Board Alarm List......................................................................................................................208 2.2.120 XCM Board Alarm List.....................................................................................................................210 2.2.121 XCS Board Alarm List......................................................................................................................210 2.2.122 XCT Board Alarm List......................................................................................................................210
3 Common Alarm Processing.....................................................................................................211

3.1 B1_EXC..........................................................................................................................................................214 3.1.1 B1_EXC (OCS).....................................................................................................................................214 3.1.2 B1_EXC (OTN).....................................................................................................................................217 3.2 BEFFEC_EXC................................................................................................................................................220 3.3 BOOTROM_BAD..........................................................................................................................................224 3.3.1 BOOTROM_BAD (OCS).....................................................................................................................224 3.3.2 BOOTROM_BAD (OTN).....................................................................................................................226 3.4 BUS_ERR.......................................................................................................................................................227 3.4.1 BUS_ERR (OCS)..................................................................................................................................227 3.4.2 BUS_ERR (OTN)..................................................................................................................................230 3.5 CHAN_LOS...................................................................................................................................................232 3.6 CLIENT_PORT_PS.......................................................................................................................................235 3.7 COMMUN_FAIL...........................................................................................................................................237 3.7.1 COMMUN_FAIL (OCS)......................................................................................................................237 3.7.2 COMMUN_FAIL (OTN)......................................................................................................................239 3.8 ETH_8B10B_ERR.........................................................................................................................................244 3.9 EX_ETHOAM_CC_LOS...............................................................................................................................246 3.9.1 EX_ETHOAM_CC_LOS (OCS)..........................................................................................................246 3.9.2 EX_ETHOAM_CC_LOS (OTN)..........................................................................................................247 3.10 FC_LINK_ERR............................................................................................................................................249 3.11 FC_SYNC_LOS...........................................................................................................................................253 3.12 IN_PWR_HIGH...........................................................................................................................................254 3.12.1 IN_PWR_HIGH (OCS).......................................................................................................................254 3.12.2 IN_PWR_HIGH (OTN)......................................................................................................................256 3.13 IN_PWR_LOW............................................................................................................................................259 3.13.1 IN_PWR_LOW (OCS)........................................................................................................................259 3.13.2 IN_PWR_LOW (OTN).......................................................................................................................262 3.14 INTRA_OTU_PS.........................................................................................................................................266 3.15 LASER_MODULE_MISMATCH...............................................................................................................268 3.16 LINK_ERR...................................................................................................................................................269 3.16.1 LINK_ERR (OCS)..............................................................................................................................269 3.16.2 LINK_ERR (OTN)..............................................................................................................................270 3.17 LOOP_ALM.................................................................................................................................................273 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
3.17.1 LOOP_ALM (OCS)............................................................................................................................274 3.17.2 LOOP_ALM (OTN)............................................................................................................................275 3.18 LPT_ACTIVE..............................................................................................................................................276 3.19 LSR_WILL_DIE..........................................................................................................................................279 3.20 MS_AIS........................................................................................................................................................280 3.20.1 MS_AIS (OCS)....................................................................................................................................280 3.20.2 MS_AIS (OTN)...................................................................................................................................282 3.21 MS_RDI........................................................................................................................................................284 3.21.1 MS_RDI (OCS)...................................................................................................................................284 3.21.2 MS_RDI (OTN)...................................................................................................................................286 3.22 MUT_LOS....................................................................................................................................................288 3.23 OA_LOW_GAIN.........................................................................................................................................291 3.24 ODU_SNCP_PS...........................................................................................................................................293 3.25 ODUk_PM_AIS...........................................................................................................................................295 3.26 ODUk_PM_BDI...........................................................................................................................................299 3.27 ODUk_PM_DEG..........................................................................................................................................301 3.28 ODUk_PM_EXC..........................................................................................................................................303 3.29 ODUk_PM_SSF...........................................................................................................................................306 3.30 OMS_FDI.....................................................................................................................................................309 3.31 OSC_LOS.....................................................................................................................................................311 3.32 OTS_LOS.....................................................................................................................................................312 3.33 OTUk_LOF..................................................................................................................................................313 3.34 OTUk_SSF...................................................................................................................................................316 3.35 OUT_PWR_HIGH.......................................................................................................................................318 3.36 PORT_MODULE_OFFLINE......................................................................................................................319 3.37 POWER_FAIL.............................................................................................................................................321 3.38 PUMP_COOL_EXC....................................................................................................................................323 3.39 R_LOF..........................................................................................................................................................325 3.39.1 R_LOF (OCS)......................................................................................................................................325 3.39.2 R_LOF (OTN).....................................................................................................................................328 3.40 R_LOS..........................................................................................................................................................332 3.40.1 R_LOS (OCS)......................................................................................................................................332 3.40.2 R_LOS (OTN).....................................................................................................................................336 3.41 R_OOF..........................................................................................................................................................340 3.41.1 R_OOF (OCS).....................................................................................................................................340 3.41.2 R_OOF (OTN).....................................................................................................................................343 3.42 R_SLIP.........................................................................................................................................................347 3.43 REM_SF.......................................................................................................................................................349 3.44 REMOTE_FAULT.......................................................................................................................................351 3.45 SECU_ALM.................................................................................................................................................353 3.46 SUBRACK_ID_CONFLICT........................................................................................................................354 3.47 SUM_INPWR_LOW....................................................................................................................................355 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvi
Contents
3.48 SWDL_NEPKGCHECK..............................................................................................................................357 3.49 TD.................................................................................................................................................................359 3.50 TEMP_OVER...............................................................................................................................................360 3.51 TF..................................................................................................................................................................363 3.52 TS_CFG_MISMATCH................................................................................................................................364 3.53 WRG_BD_TYPE.........................................................................................................................................366
4 Alarm Processing.......................................................................................................................368
4.1 AD_CHECK_FAIL........................................................................................................................................378 4.2 ALC_ADJUST_FAIL....................................................................................................................................379 4.3 ALC_WAIT_ADJUST...................................................................................................................................381 4.4 ALS_ACTIVE................................................................................................................................................382 4.5 ALM_ALS......................................................................................................................................................383 4.6 APS_MANUAL_STOP..................................................................................................................................383 4.7 ALM_GFP_dCSF...........................................................................................................................................384 4.8 ALM_GFP_dLFD..........................................................................................................................................385 4.9 ALM_HANGUP.............................................................................................................................................388 4.10 ALM_TC_OEI..............................................................................................................................................389 4.11 ALM_TC_REI..............................................................................................................................................390 4.12 APE_ADJUST_FAIL...................................................................................................................................392 4.13 APE_ADJUST_PEND.................................................................................................................................393 4.14 APS_FAIL....................................................................................................................................................394 4.15 APS_INDI....................................................................................................................................................395 4.16 AU_AIS........................................................................................................................................................396 4.17 AU_LOP.......................................................................................................................................................399 4.18 B1_SD..........................................................................................................................................................401 4.18.1 B1_SD (OCS)......................................................................................................................................401 4.18.2 B1_SD (OTN)......................................................................................................................................404 4.19 B2_EXC........................................................................................................................................................406 4.20 B2_SD..........................................................................................................................................................409 4.21 B3_EXC........................................................................................................................................................412 4.22 B3_EXC_VC3..............................................................................................................................................415 4.23 B3_EXC_VC4..............................................................................................................................................416 4.24 B3_SD..........................................................................................................................................................417 4.25 B3_SD_VC3.................................................................................................................................................420 4.26 B3_SD_VC4.................................................................................................................................................422 4.27 BD_NOT_INSTALLED..............................................................................................................................422 4.28 BD_STATUS................................................................................................................................................423 4.28.1 BD_STATUS (OCS)...........................................................................................................................423 4.28.2 BD_STATUS (OTN)...........................................................................................................................425 4.29 CFCARD_FAILED......................................................................................................................................426 4.30 BDID_ERROR.............................................................................................................................................427 4.31 C2_VCAIS....................................................................................................................................................428 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
4.32 CHAN_ADD................................................................................................................................................429 4.33 CHIP_ABN...................................................................................................................................................430 4.34 CLIENT_PROT_NOTSTART.....................................................................................................................430 4.35 CLIENT_PORT_STA_INDI........................................................................................................................431 4.36 CLK_NO_TRACE_MODE..........................................................................................................................433 4.37 CRC4_CROSSTR........................................................................................................................................434 4.38 DB_RESTORE_FAIL..................................................................................................................................435 4.39 DBPS_ABNORMAL...................................................................................................................................436 4.40 DBMS_ABNORMAL..................................................................................................................................438 4.41 DBMS_ERROR............................................................................................................................................439 4.42 DBMS_PROTECT_MODE.........................................................................................................................441 4.43 DCM_INSUFF.............................................................................................................................................442 4.44 DLAG_PROTECT_FAIL............................................................................................................................443 4.45 DSP_LOAD_FAIL.......................................................................................................................................445 4.46 ETH_CFM_LOC..........................................................................................................................................446 4.47 ETH_CFM_MISMERGE.............................................................................................................................447 4.48 ETH_CFM_MACSTATUS..........................................................................................................................449 4.49 ETH_CFM_RDI...........................................................................................................................................450 4.50 ETH_CFM_UNEXPERI..............................................................................................................................451 4.51 ETH_MISCONNECT..................................................................................................................................453 4.52 ETH_SERVICE_CONFIG_FAIL................................................................................................................454 4.53 ETHOAM_DISCOVER_FAIL....................................................................................................................455 4.54 ETHOAM_RMT_CRIT_FAULT................................................................................................................457 4.55 ETHOAM_RMT_LOOP..............................................................................................................................458 4.56 ETHOAM_RMT_SD...................................................................................................................................459 4.57 ETHOAM_SELF_LOOP.............................................................................................................................460 4.58 ETHOAM_VCG_SELF_LOOP...................................................................................................................462 4.59 EX_ETHOAM_MPID_CNFLCT................................................................................................................463 4.60 EXT_MODULE_OFFLINE.........................................................................................................................464 4.61 EXT_SYNC_LOS........................................................................................................................................465 4.62 EXT_TIME_LOC.........................................................................................................................................467 4.63 FAN_FAIL...................................................................................................................................................468 4.64 FAN_FAULT...............................................................................................................................................469 4.65 FEATURE_WITHOUT_LICENSE.............................................................................................................470 4.66 FC_8B10BERR_OVER...............................................................................................................................471 4.67 FCS_ERR.....................................................................................................................................................471 4.68 FEC_LOF.....................................................................................................................................................474 4.69 FEC_OOF.....................................................................................................................................................475 4.70 FLOW_OVER..............................................................................................................................................476 4.71 FPGA_ABN..................................................................................................................................................477 4.72 FSELECT_STG............................................................................................................................................478 4.73 FWD_PKT_LOSS........................................................................................................................................479 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xviii
Contents
4.74 GAINDATA_MIS........................................................................................................................................480 4.75 HARD_BAD................................................................................................................................................481 4.76 HARD_ERR.................................................................................................................................................484 4.77 HP_LOM......................................................................................................................................................487 4.78 HP_RDI........................................................................................................................................................488 4.79 HP_REI.........................................................................................................................................................490 4.80 HP_SLM.......................................................................................................................................................491 4.81 HP_TIM........................................................................................................................................................493 4.82 HP_UNEQ....................................................................................................................................................494 4.83 HSC_UNAVAIL..........................................................................................................................................495 4.84 INTRA_OTU_STA_INDI............................................................................................................................496 4.85 IPA_SHUT...................................................................................................................................................498 4.86 J0_MM..........................................................................................................................................................499 4.87 K1_K2_M.....................................................................................................................................................500 4.88 K2_M............................................................................................................................................................501 4.89 L_SYNC.......................................................................................................................................................502 4.90 LAN_LOC....................................................................................................................................................503 4.91 LAG_PORT_FAIL.......................................................................................................................................504 4.92 LAG_VC_PORT_FAIL...............................................................................................................................505 4.93 LASER_HAZARD_WARNING..................................................................................................................507 4.94 LASER_SHUT.............................................................................................................................................508 4.95 LCS_DAYS_OF_GRACE...........................................................................................................................509 4.96 LCS_EXPIRED............................................................................................................................................510 4.97 LCS_FILE_NOT_EXIST.............................................................................................................................511 4.98 LCAS_FOPR................................................................................................................................................512 4.99 LCAS_FOPT................................................................................................................................................513 4.100 LCAS_PLCR..............................................................................................................................................513 4.101 LCAS_PLCT..............................................................................................................................................515 4.102 LCAS_TLCR..............................................................................................................................................516 4.103 LCAS_TLCT..............................................................................................................................................518 4.104 LOCAL_FAULT........................................................................................................................................519 4.105 LOCK_CUR_FAIL....................................................................................................................................520 4.106 LOCKPOW_MIS.......................................................................................................................................521 4.107 LP_RDI_VC3.............................................................................................................................................522 4.108 LP_SLM_VC3............................................................................................................................................523 4.109 LP_UNEQ_VC3.........................................................................................................................................524 4.110 LPT_RFI.....................................................................................................................................................525 4.111 LSR_COOL_ALM.....................................................................................................................................526 4.112 LSR_FORCE_OPEN..................................................................................................................................527 4.113 LSR_INVALID..........................................................................................................................................528 4.114 LTI..............................................................................................................................................................529 4.115 MAINBD_SUBBD_MISMATCH.............................................................................................................531 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
4.116 MOD_COM_FAIL.....................................................................................................................................532 4.117 MODULE_ADJUST_FAIL.......................................................................................................................533 4.118 MODULE_COOLCUR_OVER.................................................................................................................534 4.119 MODULE_TEMP_OVER..........................................................................................................................535 4.120 MODULEFILE_UPDATE_FAIL..............................................................................................................536 4.121 MS_CROSSTR...........................................................................................................................................537 4.122 MS_REI......................................................................................................................................................538 4.123 MS_SNCP_PS............................................................................................................................................539 4.124 MS_SNCP_STA_INDI..............................................................................................................................540 4.125 MS_APS_INDI_EX...................................................................................................................................542 4.126 MULTI_RPL_OWNER..............................................................................................................................543 4.127 NEBD_XC_DIF.........................................................................................................................................544 4.128 NESF_LOST..............................................................................................................................................546 4.129 NESTATE_INSTALL................................................................................................................................546 4.130 NO_BD_PARA..........................................................................................................................................547 4.131 NO_BD_SOFT...........................................................................................................................................548 4.132 NO_ELABEL.............................................................................................................................................550 4.133 NODEID_MM............................................................................................................................................551 4.134 NTP_SYNC_FAIL.....................................................................................................................................552 4.135 NULL_SEND.............................................................................................................................................553 4.136 OCH_FDI...................................................................................................................................................554 4.137 OCH_FDI-O...............................................................................................................................................554 4.138 OCH_FDI-P................................................................................................................................................555 4.139 OCH_LOS-P...............................................................................................................................................556 4.140 OCH_OCI...................................................................................................................................................557 4.141 OCH_SSF...................................................................................................................................................558 4.142 OCH_SSF-O...............................................................................................................................................559 4.143 OCH_SSF-P................................................................................................................................................560 4.144 ODU_AIS...................................................................................................................................................561 4.145 ODU_LCK..................................................................................................................................................562 4.146 ODU_OCI...................................................................................................................................................563 4.147 ODU_SNCP_STA_INDI............................................................................................................................564 4.148 ODUk_LOFLOM.......................................................................................................................................566 4.149 ODUk_PM_LCK........................................................................................................................................567 4.150 ODUk_PM_OCI.........................................................................................................................................568 4.151 ODUk_PM_TIM........................................................................................................................................569 4.152 ODUk_TCMn_AIS....................................................................................................................................571 4.153 ODUk_TCMn_BDI....................................................................................................................................572 4.154 ODUk_TCMn_DEG...................................................................................................................................573 4.155 ODUk_TCMn_EXC...................................................................................................................................575 4.156 ODUk_TCMn_LCK...................................................................................................................................576 4.157 ODUk_TCMn_LTC...................................................................................................................................577 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xx
Contents
4.158 ODUk_TCMn_OCI....................................................................................................................................578 4.159 ODUk_TCMn_SSF....................................................................................................................................579 4.160 ODUk_TCMn_TIM....................................................................................................................................580 4.161 ODUKSP_PS..............................................................................................................................................582 4.162 ODUKSP_STA_INDI................................................................................................................................583 4.163 OH_LOOP..................................................................................................................................................585 4.164 OLP_PS......................................................................................................................................................586 4.165 OLP_STA_INDI.........................................................................................................................................588 4.166 OMS_BDI...................................................................................................................................................589 4.167 OMS_BDI-O..............................................................................................................................................590 4.168 OMS_BDI-P...............................................................................................................................................591 4.169 OMS_FDI-O...............................................................................................................................................592 4.170 OMS_FDI-P................................................................................................................................................593 4.171 OMS_LOS-P..............................................................................................................................................594 4.172 OMS_SSF...................................................................................................................................................595 4.173 OMS_SSF-O...............................................................................................................................................596 4.174 OMS_SSF-P...............................................................................................................................................597 4.175 OOL............................................................................................................................................................598 4.176 OOS_LOST................................................................................................................................................599 4.177 OPA_FAIL_INDI.......................................................................................................................................600 4.178 OPU1_MSIM..............................................................................................................................................601 4.179 OPU1_VCAT_SQM...................................................................................................................................602 4.180 OPU1_VCAT_VcPLM..............................................................................................................................603 4.181 OPU2_MSIM..............................................................................................................................................604 4.182 OPU3_MSIM..............................................................................................................................................604 4.183 OPUk_PLM................................................................................................................................................605 4.184 OSC_BDI....................................................................................................................................................606 4.185 OSC_DEG..................................................................................................................................................607 4.186 OSC_RDI....................................................................................................................................................608 4.187 OTS_BDI....................................................................................................................................................609 4.188 OTS_BDI-O................................................................................................................................................610 4.189 OTS_BDI-P................................................................................................................................................611 4.190 OTS_LOS-O...............................................................................................................................................612 4.191 OTS_LOS-P................................................................................................................................................613 4.192 OTS_TIM...................................................................................................................................................614 4.193 OTU_AIS....................................................................................................................................................615 4.194 OTU_LOF..................................................................................................................................................616 4.195 OTU_LOM.................................................................................................................................................617 4.196 OTUk_AIS..................................................................................................................................................618 4.197 OTUk_BDI.................................................................................................................................................619 4.198 OTUk_DEG................................................................................................................................................620 4.199 OTUk_EXC................................................................................................................................................621 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
4.200 OTUk_LOM...............................................................................................................................................622 4.201 OTUk_TIM.................................................................................................................................................623 4.202 OUT_PWR_LOW......................................................................................................................................625 4.203 OWSP_PS...................................................................................................................................................626 4.204 OWSP_STA_INDI.....................................................................................................................................627 4.205 PATCH_ACT_TIMEOUT.........................................................................................................................629 4.206 PATCH_DEACT_TIMEOUT....................................................................................................................630 4.207 PATCH_PKGERR.....................................................................................................................................631 4.208 PM_BDI......................................................................................................................................................632 4.209 PM_BEI......................................................................................................................................................633 4.210 PM_BIP8_OVER.......................................................................................................................................634 4.211 PM_BIP8_SD.............................................................................................................................................635 4.212 PM_TIM.....................................................................................................................................................637 4.213 PORTSWITCH_FAIL................................................................................................................................638 4.214 POWER_ABNORMAL.............................................................................................................................638 4.215 POWER_DIFF_OVER...............................................................................................................................640 4.216 PRBS_LSS..................................................................................................................................................641 4.217 PUM_BCM_ALM......................................................................................................................................642 4.218 PUM_TEM_ALM......................................................................................................................................643 4.219 R_LOC........................................................................................................................................................644 4.219.1 R_LOC (OCS)...................................................................................................................................644 4.219.2 R_LOC (OTN)...................................................................................................................................645 4.220 RELAY_ALARM_CRITICAL .................................................................................................................646 4.221 RELAY_ALARM_IGNORE ....................................................................................................................647 4.222 RELAY_ALARM_MAJOR ......................................................................................................................649 4.223 RELAY_ALARM_MINOR ......................................................................................................................650 4.224 REM_SD....................................................................................................................................................651 4.225 RL_CRITICAL_HI....................................................................................................................................652 4.226 RL_CRITICAL_LOW................................................................................................................................653 4.227 RS_CROSSTR............................................................................................................................................654 4.228 RTC_FAIL..................................................................................................................................................655 4.229 S1_SYN_CHANGE...................................................................................................................................656 4.230 SCC_LOC...................................................................................................................................................657 4.231 SEC_RADIUS_FAIL.................................................................................................................................658 4.232 SERVICE_TYPE_EXCEED_LICENSE...................................................................................................659 4.233 SERVICE_CAPACITY_EXCEED_LICENSE.........................................................................................660 4.234 SHELF_AREA_POWER_OVER..............................................................................................................661 4.235 SPAN_LOSS_HIGH..................................................................................................................................662 4.236 SPAN_LOSS_LOW...................................................................................................................................663 4.237 SLAVE_WORKING..................................................................................................................................664 4.238 SM_BDI......................................................................................................................................................666 4.239 SM_BEI......................................................................................................................................................667 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxii
Contents
4.240 SM_BIP8_OVER.......................................................................................................................................668 4.241 SM_BIP8_SD.............................................................................................................................................669 4.242 SM_IAE......................................................................................................................................................670 4.243 SM_TIM.....................................................................................................................................................671 4.244 SNCP_FAIL...............................................................................................................................................672 4.245 SO_SK_MISMATCH................................................................................................................................673 4.246 SPEED_OVER...........................................................................................................................................675 4.247 STORM_CUR_QUENUM_OVER............................................................................................................676 4.248 SUBRACK_COMM_PS............................................................................................................................676 4.249 SUBRACK_ID_MISMATCH....................................................................................................................677 4.250 SUBRACK_LOOP.....................................................................................................................................678 4.251 SUBRACK_TYPE_MISMATCH..............................................................................................................679 4.252 SUM_INPWR_HI......................................................................................................................................680 4.253 SW_SNCP_PS............................................................................................................................................682 4.254 SW_SNCP_STA_INDI..............................................................................................................................683 4.255 SWDL_ACTIVATED_TIMEOUT............................................................................................................684 4.256 SWDL_AUTOMATCH_INH....................................................................................................................685 4.257 SWDL_BD_EXCLUDE.............................................................................................................................686 4.258 SWDL_CHGMNG_NOMATCH...............................................................................................................687 4.259 SWDL_COMMIT_FAIL............................................................................................................................688 4.260 SWDL_INPROCESS.................................................................................................................................689 4.261 SWDL_PKG_NOBDSOFT........................................................................................................................690 4.262 SWDL_PKGVER_MM..............................................................................................................................691 4.263 SWDL_ROLLBACK_FAIL......................................................................................................................691 4.264 SYN_BAD..................................................................................................................................................692 4.265 SYNC_C_LOS...........................................................................................................................................694 4.266 SYNC_DISABLE.......................................................................................................................................695 4.267 SYNC_F_M_SWITCH..............................................................................................................................696 4.268 SYNC_LOCKOFF.....................................................................................................................................698 4.269 SYNC_FAIL...............................................................................................................................................699 4.270 SYSPARA_CFDB_NOSAME...................................................................................................................700 4.271 T_LOSEX...................................................................................................................................................701 4.272 T_SLIP........................................................................................................................................................702 4.273 TEM_HA....................................................................................................................................................702 4.274 TEM_LA....................................................................................................................................................703 4.275 TEST_STATUS..........................................................................................................................................704 4.276 THUNDERALM........................................................................................................................................705 4.277 TIME_LOS.................................................................................................................................................706 4.278 TIME_NO_TRACE_MODE......................................................................................................................707 4.279 TR_LOC.....................................................................................................................................................709 4.280 TU_AIS_VC3.............................................................................................................................................710 4.281 TU_LOP_VC3............................................................................................................................................711 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Contents
4.282 VCAT_LOA...............................................................................................................................................712 4.282.1 VCAT_LOA (OCS)...........................................................................................................................713 4.282.2 VCAT_LOA (OTN)..........................................................................................................................714 4.283 VCAT_LOM_VC3.....................................................................................................................................714 4.284 VCAT_LOM_VC4.....................................................................................................................................715 4.285 VLAN_SNCP_PS.......................................................................................................................................717 4.286 VOA_ADJUST_FAIL................................................................................................................................718 4.287 VOADATA_MIS.......................................................................................................................................719 4.288 W_R_FAIL.................................................................................................................................................720 4.289 WAVE_ADD_ABN...................................................................................................................................721 4.290 WAVE_DROP_ABN.................................................................................................................................722 4.291 WAVEDATA_MIS....................................................................................................................................723 4.292 WAVELEN_OVER....................................................................................................................................724 4.293 XC_UNSWITCH........................................................................................................................................725
5 Performance Event List.............................................................................................................727

5.1 Product Performance Event List.....................................................................................................................728 5.1.1 Performance Event of Check and Error Correction...............................................................................728 5.1.2 Performance Event of Pointer Justification...........................................................................................729 5.1.3 Performance Event of Equipment Function..........................................................................................729 5.1.4 Performance Event of Multiplex Section Bit Error...............................................................................733 5.1.5 Performance Event of Regenerator Section Bit Error...........................................................................733 5.1.6 Performance Event of Higher Order Path Bit Error..............................................................................734 5.1.7 Performance Event of Lower Order Path Bit Error...............................................................................734 5.1.8 Performance Event of OTN...................................................................................................................735 5.1.9 Performance Event List of RMON Function.........................................................................................745 5.1.10 TCM Performance Event ....................................................................................................................751 5.1.11 Performance Event of FC....................................................................................................................751 5.2 Board Performance Event List.......................................................................................................................752 5.2.1 CRPC Board Performance Event List...................................................................................................752 5.2.2 DAS1 Board Performance Event List...................................................................................................752 5.2.3 D40V Board Performance Event List....................................................................................................753 5.2.4 D40 Board Performance Event List.......................................................................................................753 5.2.5 DCP Board Performance Event List......................................................................................................754 5.2.6 EGSH Board Performance Event List...................................................................................................754 5.2.7 EAS2 Board Performance Event List....................................................................................................755 5.2.8 ECOM Board Performance Event List..................................................................................................756 5.2.9 ELQX Board Performance Event List...................................................................................................756 5.2.10 ENQ2 Board Performance Event List.................................................................................................758 5.2.11 FIU Board Performance Event List.....................................................................................................760 5.2.12 HSC1 Board Performance Event List..................................................................................................760 5.2.13 HBA Board Performance Event List...................................................................................................760 5.2.14 ITL Board Performance Event List.....................................................................................................760 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiv
Contents
5.2.15 L4G Board Performance Event List....................................................................................................761 5.2.16 LDGD Board Performance Event List................................................................................................762 5.2.17 LDGS Board Performance Event List.................................................................................................764 5.2.18 LDM Board Performance Event List...................................................................................................766 5.2.19 LDMD Board Performance Event List................................................................................................767 5.2.20 LDMS Board Performance Event List................................................................................................769 5.2.21 LDX Board Performance Event List...................................................................................................771 5.2.22 LEM24 Board Performance Event List...............................................................................................772 5.2.23 LEX4 Board Performance Event List..................................................................................................773 5.2.24 LOA Board Performance Event List...................................................................................................774 5.2.25 LOG Board Performance Event List...................................................................................................776 5.2.26 LOM Board Performance Event List...................................................................................................778 5.2.27 LQMD Board Performance Event List................................................................................................780 5.2.28 LQMS Board Performance Event List................................................................................................783 5.2.29 LQM Board Performance Event List...................................................................................................785 5.2.30 LSQ Board Performance Event List....................................................................................................787 5.2.31 LSXLR Board Performance Event List...............................................................................................788 5.2.32 LSXL Board Performance Event List.................................................................................................789 5.2.33 LSXR Board Performance Event List.................................................................................................790 5.2.34 LSX Board Performance Event List....................................................................................................791 5.2.35 LWX2 Board Performance Event List................................................................................................793 5.2.36 LWXD Board Performance Event List...............................................................................................793 5.2.37 LWXS Board Performance Event List................................................................................................793 5.2.38 M40V Board Performance Event List.................................................................................................794 5.2.39 M40 Board Performance Event List....................................................................................................794 5.2.40 MCA4 Board Performance Event List................................................................................................794 5.2.41 MCA8 Board Performance Event List................................................................................................795 5.2.42 MR8V Board Performance Event List................................................................................................795 5.2.43 ND2 Board Performance Event List....................................................................................................795 5.2.44 NQ2 Board Performance Event List....................................................................................................802 5.2.45 NPO2 Board Performance Event List.................................................................................................808 5.2.46 NPO2E Board Performance Event List...............................................................................................810 5.2.47 NS2 Board Performance Event List....................................................................................................811 5.2.48 NS3 Board Performance Event List....................................................................................................817 5.2.49 OAU1 Board Performance Event List.................................................................................................822 5.2.50 OBU1 Board Performance Event List.................................................................................................822 5.2.51 OBU2 Board Performance Event List.................................................................................................822 5.2.52 OLP Board Performance Event List....................................................................................................823 5.2.53 OPM8 Board Performance Event List.................................................................................................823 5.2.54 PTQX Board Performance Event List.................................................................................................823 5.2.55 RDU9 Board Performance Event List.................................................................................................825 5.2.56 RMU9 Board Performance Event List................................................................................................825 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Contents
5.2.57 ROAM Board Performance Event List...............................................................................................825 5.2.58 SCC Board Performance Event List....................................................................................................826 5.2.59 SC1 Board Performance Event List.....................................................................................................826 5.2.60 SC2 Board Performance Event List.....................................................................................................826 5.2.61 SFD64 Board Performance Event List................................................................................................826 5.2.62 SF64 Board Performance Event List...................................................................................................827 5.2.63 SF64A Board Performance Event List................................................................................................828 5.2.64 SL64 Board Performance Event List...................................................................................................829 5.2.65 SLD64 Board Performance Event List................................................................................................830 5.2.66 SLH41 Board Performance Event List................................................................................................830 5.2.67 SLO16 Board Performance Event List................................................................................................831 5.2.68 SLQ16 Board Performance Event List................................................................................................831 5.2.69 SLQ64 Board Performance Event List................................................................................................832 5.2.70 ST2 Board Performance Event List.....................................................................................................833 5.2.71 STG Board Performance Event List....................................................................................................833 5.2.72 SXM Board Performance Event List...................................................................................................833 5.2.73 SXH Board Performance Event List...................................................................................................833 5.2.74 TBE Board Performance Event List....................................................................................................834 5.2.75 TDC Board Performance Event List...................................................................................................835 5.2.76 TDG Board Performance Event List...................................................................................................835 5.2.77 TDX Board Performance Event List...................................................................................................836 5.2.78 THA Board Performance Event List...................................................................................................842 5.2.79 TMX Board Performance Event List...................................................................................................844 5.2.80 TOA Board Performance Event List...................................................................................................845 5.2.81 TOG Board Performance Event List...................................................................................................847 5.2.82 TOM Board Performance Event List...................................................................................................848 5.2.83 TQM Board Performance Event List...................................................................................................851 5.2.84 TQS Board Performance Event List....................................................................................................854 5.2.85 TQX Board Performance Event List...................................................................................................855 5.2.86 TSXL Board Performance Event List.................................................................................................861 5.2.87 VA1 Board Performance Event List....................................................................................................864 5.2.88 VA4 Board Performance Event List....................................................................................................864 5.2.89 WMU Board Performance Event List.................................................................................................864 5.2.90 WSD9 Board Performance Event List.................................................................................................864 5.2.91 WSM9 Board Performance Event List................................................................................................865 5.2.92 WSMD2 Board Performance Event List.............................................................................................865 5.2.93 WSMD4 Board Performance Event List.............................................................................................865 5.2.94 WSMD9 Board Performance Event List.............................................................................................865 5.2.95 XCH Board Performance Event List...................................................................................................865 5.2.96 XCM Board Performance Event List..................................................................................................866 5.2.97 XCT Board Performance Event List...................................................................................................866
6 Performance Event Processing................................................................................................867

Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvi
Contents
6.1 AUPJCHIGH..................................................................................................................................................872 6.2 AUPJCLOW...................................................................................................................................................873 6.3 AUPJCNEW...................................................................................................................................................874 6.4 BCV................................................................................................................................................................875 6.5 CCV................................................................................................................................................................875 6.6 CRC4ES..........................................................................................................................................................876 6.7 CRC4FEES.....................................................................................................................................................877 6.8 CRC4FESES...................................................................................................................................................878 6.9 CRC4FEUAS..................................................................................................................................................879 6.10 CRC4SES.....................................................................................................................................................879 6.11 CRC4UAS....................................................................................................................................................880 6.12 EDTMP.........................................................................................................................................................881 6.13 EDTPL..........................................................................................................................................................882 6.14 ENVTMP......................................................................................................................................................883 6.15 FEC_AFT_COR_ER....................................................................................................................................883 6.16 FEC_AFT_COR_ERAVR............................................................................................................................884 6.17 FEC_AFT_CORER_FLOAT.......................................................................................................................885 6.18 FEC_BEF_COR_ER....................................................................................................................................886 6.19 FEC_BEF_COR_ERAVR............................................................................................................................887 6.20 FEC_BEF_CORER_FLOAT.......................................................................................................................888 6.21 FEC_COR_0BIT_CNT................................................................................................................................888 6.22 FEC_COR_1BIT_CNT................................................................................................................................889 6.23 FEC_COR_BYTE_CNT..............................................................................................................................890 6.24 FEC_UNCOR_BLOCK_CNT.....................................................................................................................890 6.25 HPBBE.........................................................................................................................................................891 6.26 HPCSES........................................................................................................................................................892 6.27 HPES............................................................................................................................................................893 6.28 HPFEBBE.....................................................................................................................................................894 6.29 HPFECSES...................................................................................................................................................895 6.30 HPFEES........................................................................................................................................................896 6.31 HPFESES......................................................................................................................................................897 6.32 HPFEUAS....................................................................................................................................................898 6.33 HPSES..........................................................................................................................................................899 6.34 HPUAS.........................................................................................................................................................900 6.35 ICCLC..........................................................................................................................................................901 6.36 ICTMP..........................................................................................................................................................902 6.37 LSBIAS........................................................................................................................................................903 6.38 LSBISA........................................................................................................................................................904 6.39 LSCLC..........................................................................................................................................................905 6.40 LSIOP...........................................................................................................................................................906 6.41 LSOOP..........................................................................................................................................................907 6.42 LSTMP.........................................................................................................................................................908 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Contents
6.43 MSBBE.........................................................................................................................................................909 6.44 MSCSES.......................................................................................................................................................910 6.45 MSES............................................................................................................................................................911 6.46 MSFEBBE....................................................................................................................................................912 6.47 MSFECSES..................................................................................................................................................912 6.48 MSFEES.......................................................................................................................................................913 6.49 MSFESES.....................................................................................................................................................914 6.50 MSFEUAS....................................................................................................................................................915 6.51 MSSES..........................................................................................................................................................916 6.52 MSUAS........................................................................................................................................................917 6.53 ODU2PMBIP8..............................................................................................................................................918 6.54 ODUk_PM_BBE..........................................................................................................................................919 6.55 ODUk_PM_BBER.......................................................................................................................................919 6.56 ODUk_PM_ES.............................................................................................................................................920 6.57 ODUk_PM_FEBBE.....................................................................................................................................921 6.58 ODUk_PM_FEBBER...................................................................................................................................922 6.59 ODUk_PM_FEES........................................................................................................................................923 6.60 ODUk_PM_FESES......................................................................................................................................923 6.61 ODUk_PM_FESESR....................................................................................................................................924 6.62 ODUk_PM_FEUAS.....................................................................................................................................925 6.63 ODUk_PM_SES...........................................................................................................................................926 6.64 ODUk_PM_SESR........................................................................................................................................926 6.65 ODUk_PM_UAS..........................................................................................................................................927 6.66 ODUk_TCMn_BBE.....................................................................................................................................928 6.67 ODUk_TCMn_BBER..................................................................................................................................929 6.68 ODUk_TCMn_BIAES.................................................................................................................................930 6.69 ODUk_TCMn_ES........................................................................................................................................930 6.70 ODUk_TCMn_FEBBE................................................................................................................................931 6.71 ODUk_TCMn_FEBBER..............................................................................................................................932 6.72 ODUk_TCMn_FEES....................................................................................................................................933 6.73 ODUk_TCMn_FESES.................................................................................................................................933 6.74 ODUk_TCMn_FESESR...............................................................................................................................934 6.75 ODUk_TCMn_FEUAS................................................................................................................................935 6.76 ODUk_TCMn_IAES....................................................................................................................................935 6.77 ODUk_TCMn_SES......................................................................................................................................936 6.78 ODUk_TCMn_SESR...................................................................................................................................937 6.79 ODUk_TCMn_UAS.....................................................................................................................................937 6.80 OOPRL.........................................................................................................................................................938 6.81 OSC_BBE.....................................................................................................................................................939 6.82 OSC_BBER..................................................................................................................................................940 6.83 OSC_BIAES.................................................................................................................................................940 6.84 OSC_ES........................................................................................................................................................941 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxviii
Contents
6.85 OSC_FEBBE................................................................................................................................................941 6.86 OSC_FEBBER.............................................................................................................................................942 6.87 OSC_FEES...................................................................................................................................................943 6.88 OSC_FESES.................................................................................................................................................943 6.89 OSC_FESESR..............................................................................................................................................944 6.90 OSC_FEUAS................................................................................................................................................945 6.91 OSC_IAES....................................................................................................................................................945 6.92 OSC_SES......................................................................................................................................................946 6.93 OSC_SESR...................................................................................................................................................947 6.94 OSC_UAS....................................................................................................................................................947 6.95 OSPICCV.....................................................................................................................................................948 6.96 OSPITMP.....................................................................................................................................................949 6.97 OTU2SMBIP8..............................................................................................................................................950 6.98 OTUk_BBE..................................................................................................................................................950 6.99 OTUk_BBER................................................................................................................................................951 6.100 OTUk_ES...................................................................................................................................................952 6.101 OTUk_FEBBE............................................................................................................................................953 6.102 OTUk_FEBBER.........................................................................................................................................954 6.103 OTUk_FEES...............................................................................................................................................954 6.104 OTUk_FESES............................................................................................................................................955 6.105 OTUk_FESESR..........................................................................................................................................956 6.106 OTUk_FEUAS...........................................................................................................................................957 6.107 OTUk_SES.................................................................................................................................................957 6.108 OTUk_SESR..............................................................................................................................................958 6.109 OTUk_UAS................................................................................................................................................959 6.110 PCLSOP......................................................................................................................................................960 6.111 PCLSSN......................................................................................................................................................961 6.112 PCLSWL....................................................................................................................................................961 6.113 PCLSWLO..................................................................................................................................................962 6.114 RPL.............................................................................................................................................................963 6.115 RSBBE........................................................................................................................................................964 6.116 RSCSES......................................................................................................................................................964 6.117 RSES...........................................................................................................................................................965 6.118 RSOFS........................................................................................................................................................966 6.119 RSOOF.......................................................................................................................................................967 6.120 RSSES........................................................................................................................................................968 6.121 RSUAS.......................................................................................................................................................969 6.122 SUMIOP.....................................................................................................................................................970 6.123 SUMOOP....................................................................................................................................................971 6.124 TLB.............................................................................................................................................................972 6.125 TPL.............................................................................................................................................................973 6.126 VC3BBE.....................................................................................................................................................974 Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Contents
6.127 VC3CSES...................................................................................................................................................975 6.128 VC3ES........................................................................................................................................................977 6.129 VC3FEBBE................................................................................................................................................979 6.130 VC3FECSES..............................................................................................................................................980 6.131 VC3FEES...................................................................................................................................................981 6.132 VC3FESES.................................................................................................................................................982 6.133 VC3FEUAS................................................................................................................................................983 6.134 VC3SES......................................................................................................................................................985 6.135 VC3UAS.....................................................................................................................................................986 6.136 WCV...........................................................................................................................................................987 6.137 XCSTMP....................................................................................................................................................988
7 Event List.....................................................................................................................................990 8 Event Processing........................................................................................................................993

8.1 EAPE abnormal event notification.................................................................................................................994 8.2 EAPE adjustment result event notification.....................................................................................................995 8.3 OWSP abnormal event...................................................................................................................................998 8.4 ODUk SPRing abnormal event.....................................................................................................................1001 8.5 RMON performance value is above the upper limit.....................................................................................1003 8.6 RMON module performance value is lower than the lower threshold.........................................................1005 8.7 1+1 Equipment Level Protection Switching Event Report..........................................................................1007
A Glossary....................................................................................................................................1009
Issue 02 (2011-10-31)
xxx
1 Overview
1
About This Chapter
Overview
This topic describes the meaning and indicator status of the alarms of four levels, and the meaning, range and severity of the alarms in different categories. Describes different types of performance event, the alarm signal flow of the OTU unit and the suppression relationship of alarms. 1.1 Alarm Level This section respectively describes the meaning, influence and indicator status of the alarms of four levels. 1.2 Alarm Category This section describes the meaning and range of alarms in different categories. 1.3 Performance Event Category Performance events can be classified into ten categories according to the function monitored by a performance event. Among these performance events, Performance Event of Higher Order Path Bit Error, Lower Order Path Bit Error and Pointer Justification are supported only by the OptiX OSN 8800. 1.4 Alarm Signal Flow This section describes the alarm signal flow of the OTU. It describes the generation, detection, and transmission of alarms when the OTU accesses different types of signals. 1.5 Suppression Relationship of Alarms This section describes the rules of alarm suppression and provides the suppression relationship figure of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm suppression. 1.6 Performance Event Suppression by Alarms An optical interface can report several alarms and performance events. Some performance events are not important for the maintenance engineer.
Issue 02 (2011-10-31)
1 Overview
1.1 Alarm Level

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

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

Performance events can be classified into ten categories according to the function monitored by a performance event. Among these performance events, Performance Event of Higher Order Path Bit Error, Lower Order Path Bit Error and Pointer Justification are supported only by the OptiX OSN 8800. The performance event is an important parameter that reflects the working performance of the equipment. The knowledge of the generation principle, related boards and alarms of the performance event is helpful to find incipient faults in routine maintenance and analyze the fault. The categories of the performance events are shown in the Table 1-3. Performance events and alarms are related. When the number of the performance events exceeds the preset threshold, the related alarm is triggered. Hence, when a performance event is generated, check whether the related alarm is generated and handle the performance event by referring to the handling procedure of the related alarm. The OptiX OSN 8800/OptiX OSN 6800/OptiX OSN 3800 provides the remote monitoring function by which the network can monitor the transmission of data in different network segments. Remote monitoring (RMON) provides flexible detection modes and control mechanism to cater for the needs of different kinds of network. The RMON defines a serial of statistic formats and functions to realize the data exchange among the control stations and detection stations in compliance with the RMON standard. The RMON also provides error diagnosis, planning and information receiving of the performance events of the entire network.
Issue 02 (2011-10-31) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3
1 Overview
Table 1-3 Performance event category Performance event category Performance event related to the bit errors of the regenerator section Performance event related to the bit errors of the multiplex section Performance Event of Higher Order Path Bit Error Performance Event of Lower Order Path Bit Error Performance Event of Pointer Justification Performance event related to the check and error correction Performance event related to the equipment function OTN performance event RMON performance event Definition The performance event generated when bit errors occur at the regenerator section in the SDH frames of the signals on the WDM side or the client side of the board. The performance event generated when bit errors occur in the multiplex section in the SDH frames of the signals on the WDM side or the client side of the board. The performance event generated when bit errors occur on higher order path. The performance event generated when bit errors occur on lower order path. The performance event generated when the board performs pointer justification The performance event generated when the board performs service check or bit error correction. The performance event generated when the optical power, the working current of the laser or other factors about the running environment exceed the threshold. The performance event generated when bit errors occur in the PM, TCM or SM segment of the OTN service. The performance event related to the mode in which the board transmits or receives the data packets, the number and quality of packets in different lengths transmitted or received. The performance event generated when parameter changes in FC.
FC performance event
1.4 Alarm Signal Flow

This section describes the alarm signal flow of the OTU. It describes the generation, detection, and transmission of alarms when the OTU accesses different types of signals.
1.4.1 Overview
This section describes the seven types of scenarios of the alarm signal flow, SF, SD, and basic concepts in the alarm signal flow diagram.
Classification
For a WDM product, the detection and transmission of alarms vary according to the type of the signals that are accessed into the OTU. The OTU is classified into the following types:
1 Overview
l l l
Non-convergent OTU It refers to an OTU that converts one channel of client service signals. Convergent OTU It refers to an OTU that converges and converts multiple channels of client service signals. Regenerating OTU It refers to an OTU that regenerates the corresponding service signals at an intermediate station.
According to the type of the OTU and the type of the signals accessed by the OTU, the following seven situations are defined in this section: l Non-convergent OTU processing standard SDH signals This section describes the alarm signal flow when the non-convergent OTU processes standard SDH signals. l Non-convergent OTU processing standard OTN signals This section describes the alarm signal flow when the non-convergent OTU processes standard OTN signals. l Convergent OTU processing standard SDH signals This section describes the alarm signal flow when the convergent OTU processes standard SDH signals. l Convergent OTU processing standard OTN signals This section describes the alarm signal flow when the convergent OTU processes standard OTN signals. l l l Regenerating OTU This section describes the alarm signal flow of the regenerating OTU. OTU with the cross-connect function This section describes the alarm signal flow of the OTU with the cross-connect function. OTU processing GE signals This section describes the alarm signal flow when the OTU processes GE signals.
SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are trigger conditions of a protection switching. Whether the SD event is used as a trigger condition, however, it can be set by the user. The SF and SD events are marked in the alarm signal flow diagrams in this section. These events are generated when the equipment configured with network protection detects a certain alarm. If the equipment is not configured with the network protection, the SF and SD events are not detected or reported.
Concepts
The following concepts are used in the diagrams in this section: l l WDM side: It is the WDM side of the OTU. Client side: it is the client side of the OTU. On the client side, the services from a client device are accessed.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5
Issue 02 (2011-10-31)
1 Overview
Middle part: It is the middle part between the WDM side and the client side. It is a virtual concept, and therefore is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. N#1: It indicates channel 1 at optical port N on the OTU. For example, the client-side optical ports of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical port of the LQMD unit is numbered 1. Then, 3#1 indicates channel 1 at client-side optical port 3. 1#N: It indicates channel N at WDM-side optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical port 1.
1.4.2 Non-Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the non-convergent OTU processes standard SDH signals. Figure 1-1 and Figure 1-2 show the alarm signal flows when the non-convergent OTU processes standard SDH signals.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Issue 02 (2011-10-31)
1 Overview
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals
Station A Client-side WDM-side Station B WDM-side SF R_LOS R_LOS R_LOF SF R_LOF R_LOF R_LOF R_LOF Client-side Client device Client-device
R_LOF
MS_AIS
MS_AIS
MS_AIS SD
MS_AIS
BI errors
B1_SD/ B1_EXC
B1_SD/ B1_EXC SD PM BIP8 errors ODUk_PM_DEG/ ODUk_PM_EXC
B1errors
Errors
PM remote BER performance events SM BIP8 Errors
SD OTUk_DEG/ OTUk_EXC
Errors
OTUk remote BER performance events OTUk_AIS SF OTUk_AIS R_LOF
ODUk_PM_BDI &OTUk_BDI OTUk_LOM ODUk_PM_BDI &OTUk_BDI SF: SF event detecting xxx SD: SD event detecting Alarm processing SD OTUk_AIS R_OOF
Detects and reports the xxx alarm or performance event
This section describes the alarm signal flow by analyzing how the OTU processes the R_LOS alarm and PM BIP8 errors. The alarm signal flows of other alarms are similar. l R_LOS The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are processed on the WDM side of the OTU and then are sent to station B. The client side of the OTU at station B detects the REM_SF alarm. The alarm is then sent to the downstream client device of station B, and the OTU reports the R_LOF alarm to the client device. l
Issue 02 (2011-10-31)
PM BIP8 errors
1 Overview
The OTU at station B detects PM BIP 8 errors on the WDM side. When the PM BIP 8 errors exceed the threshold, the ODUk_PM_DEG or ODUk_PM_EXC alarm is generated. The number of errors determines which alarm is generated. In addition, the performance events indicting ODUk PM remote bit errors are sent to the WDM side of upstream station A. The bit errors are then sent to the client device (The bit errors cannot be sent to the downstream station except that the PM BIP 8 errors are from the data inside). The alarms related to bit errors are detected in the client device. Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals
Station A Client-side WDM-side MFAS frame discontinuous ODUk_PM_BDI &OTUk_BDI PM TTI byte mismatch SF ODUk_PM_TIM R_LOF Station B WDM-side OTUk_LOM Client-side Client device Client-device
ODUk_PM_BDI SM TTI byte mismatch OTUk_BDI ODUk_PM_BDI OTUk_BDI Excessive bit errors before FEC ODUk_PM_BDI OTUk_BDI BEFFEC_EXC SF OTUk_LOF SF OTUk_TIM R_LOF
OTUk_LOF ODUk_PM_BDI &OTUk_BDI ODUk_PM_AIS/ ODUk_PM_OCI/ ODUk_PM_LCK
R_LOF
SF ODUk_PM_AIS/ ODUk_PM_OCI/ ODUk_PM_LCK R_LOF
ODUk_PM_BDI R_LOS SF R_LOS R_LOF
ODUk_PM_BDI &OTUk_BDI SF: SF event detecting xxx Alarm processing
Detects and reports the xxx alarm
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
Issue 02 (2011-10-31)
1 Overview
This section describes the alarm signal flow by analyzing how the OTU processes the OTUk_LOF alarm. The alarm signal flows of other alarms are similar. The WDM side of the OTU at station B detects the OTUk_LOF alarm. Then, the OTU sends the ODUk_PM_BDI and OTUk_BDI alarms to the WDM side of upstream station A. In addition, the alarm is then sent to the client side of station B. After the alarm is processed on the client side, the R_LOF alarm is detected in the client device.
1.4.3 Non-Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the non-convergent OTU unit processes standard OTN signals. Figure 1-3 and Figure 1-4 show the alarm signal flows when the non-convergent OTU processes standard OTN signals.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled. The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Issue 02 (2011-10-31)
1 Overview
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals
Station A Client-side R_LOS OTUk_BDI PM BIP8 errors ODUk_PM_DEG/ ODUk_PM_EXC SM BIP8 errors OTUk_DEG/ OTUk_EXC OTUk remote BER performance events SM BIP8 errors OTUk remote BER performance events PM BIP8 errors SD ODUk_PM_DEG/ ODUk_PM_EXC SF ODUk_PM_AIS PM BIP8 errors SD OTUk_DEG/ OTUk_EXC SD ODUk_PM_DEG/ ODUk_PM_EXC PM BIP8 errors R_LOS WDM-side Station B WDM-side SF ODUk_PM_AIS Client-side Client device Client-device ODUk_PM_AIS
OTUk_LOF OTUk_BDI OTUk_LOM OTUk_BDI OTUk_AIS OTUk_BDI
OTUk_LOF
ODUk_PM_AIS
OTUk_LOM
SF ODUk_PM_AIS
ODUk_PM_AIS
OTUk_AIS OTUk_LOF/ OTUk_LOM/ OTUk_AIS
SF ODUk_PM_AIS
ODUk_PM_AIS
SF OTUk_LOF/ OTUk_LOM/ OTUk_AIS
ODUk_PM_AIS
OTUk_BDI SF: SF event detecting xxx SD: SD event detecting Alarm processing
This section describes the alarm signal flow by analyzing how the OTU unit processes the R_LOS and OTUk_LOF alarms. The alarm signal flow of other alarms is similar. l R_LOS The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are processed on the WDM side of the OTU and then are sent to station B. The WDM side of the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is generated. The event triggers a protection switching. The alarm is then sent to the downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS alarm to the client equipment. l OTUk_LOF The OTUk_LOF alarm is detected on the WDM side of the OTU board at station B, and station B sends the OTUk_BDI alarm to the WDM side of the OTU at the upstream station A. At the same time, the alarm is then sent to the downstream station of station B, where
1 Overview
it is processed on the client side of the OTU. In this case, the ODUk_PM_AIS alarm is detected in the client equipment. An SF event is generated on the WDM side of the OTU at station B, and a service channel protection switching is triggered. The client side of the OTU at station A receives OTUk_LOF signals. The OTU sends the OTUk_BDI alarm to the upstream client equipment of station A. In addition, the LOF alarm is processed on the WDM side of the OTU and then is sent to station B. The WDM side of the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is generated. The event triggers a protection switching. The alarm is then sent to the downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS alarm to the client equipment. Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals
Station A Client-side WDM-side Station B WDM-side Client-side Client device Client-device
The SF event is generated when the SF TIM follow-up response is Enabled. SM TTI byte mismatch The SF event is generated when the OTUk_TIM SF TIM follow-up response is Enabled. SM TTI byte mismatch OTUk_TIM OTUk_BDI OTUk_BDI OTUk_BDI OTUk_BDI OTUk_BDI
OTUk_BDI
Transparent transmission of all PM signals ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_OCI ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_OCI SF ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_OCI
ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_OCI
R_LOS
SF R_LOS ODUk_PM_AIS
OTUk_BDI
SF: SF event detecting xxx
SD: SD event detecting
Alarm processing
OTUk_TIM After the OTU at station A receives the OTUk_TIM alarm on the client side, it sends the OTUk_BDI alarm to the upstream station, but it does not send the OTUk_TIM alarm to the downstream station. If the TIM is enabled in the subsequent action, an SF event is generated and the WDM side of the OTU at station B reports the ODUk_PM_AIS alarm. The ODUk_PM_AIS alarm is sent to the downstream and the client device reports this alarm. After the OTU at station B receives the OTUk_TIM alarm on the WDM side, this alarm is not sent to the downstream if the TIM is not enabled in the subsequent action. If the TIM
Issue 02 (2011-10-31)
11
1 Overview
is enabled in the subsequent action, an SF event is generated. After the client side of station B processes the event, the client device reports the ODUk_PM_AIS alarm. l OTUk_BDI The OTU detects the OTUk_BDI alarm from the upstream station. This alarm is not sent to the downstream station. l l ODUk_PM_TIM/ODUk_PM_BDI The OTU transparently transmits all PM alarms. ODUk_PM_AIS/ODUk_PM_LCK/ODUk_PM_OCI The client side of the OTU at station A receives ODUk_PM_AIS, ODUk_PM_LCK, or ODUk_PM_OCI signals. The signals are not processed and reported at the local station. After the signals are sent to station B, the WDM side of the OTU at station B detects the ODUk_PM_AIS, ODUk_PM_LCK, or ODUk_PM_OCI alarm. Then, an SF event is generated. The event triggers a protection switching. The alarm is then sent to the downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS, ODUk_PM_LCK, or ODUk_PM_OCI alarm to the client equipment. l R_LOS The WDM side of the OTU at station B detects the R_LOS alarm. The OTU sends the OTUk_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then sent to the client side of station B. After the alarm is processed on the client side, the ODUk_PM_AIS alarm is detected in the client equipment. An SF event is generated on the WDM side of the OTU at station B, and a protection switching is triggered.
1.4.4 Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the convergent OTU processes standard SDH signals. Figure 1-5 and Figure 1-6 show the alarm signal flows when the convergent OTU processes standard SDH signals.
NOTE
l In Figure 1-5, N#1 indicates channel 1 at optical port N of the OTU. For example, the client-side optical ports of the LQMD are numbered 3, 4, 5, and 6, and the WDM-side optical port of the LQMD is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical port 3. 1#N indicates channel N at WDM-side optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical port 1. l Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and therefore is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In the middle part of the convergent OTU, the optical port numbers and channel numbers of signals are reallocated.
NOTE
Issue 02 (2011-10-31)
12
1 Overview
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Station A
Client-side R_LOS R_LOS R_LOS R_LOS Middle WDM-side WDM-side
Station B
Middle Client-side
Client device
Client-device
N#1 R_LOS N#1 R_LOS N#1 R_LOS N#1 R_LOS SF
N#1 REM_SF N#1 REM_SF N#1 REM_SF N#1 REM_SF
N#1 R_LOF N#1 R_LOF N#1 R_LOF N#1 R_LOF
R_LOS R_LOF R_LOC
N#1 R_LOS N#1 R_LOF N#1 R_LOC N#1 Errors SD 1#N BIT Errors
N#1 REM_SF N#1 REM_SF N#1 REM_SF
N#1 R_LOF N#1 R_LOF N#1 R_LOF
Errors
Errors
A B C D
N#1 A N#1 B N#1 C N#1 D
1#N A 1#N B 1#N C 1#N D
A B C D
A, B, C, D are the others of the SDH alarms SF:SF event detecting xxx SD:SD event detecting Alarm processing
Detects and reports the xxx alarm.
This section describes the alarm signal flow through an example in which four client-side services are accessed on the convergent OTU. l Four channels of R_LOS signals are accessed on the client side. The OTU at station A accesses four channels of R_LOS signals on the client side. After being processed in the middle part of the OTU at station A, the alarm signals are then sent to station B. The REM_SF alarm is generated on the client side of station B. The R_LOF alarm is detected in the client equipment. l One channel of R_LOS signals are accessed on the client side. The OTU at station A accesses one channel of R_LOS signals on the client side, for example, channel 1 at optical port 3. After being processed in the middle part and on the WDM side of the OTU at station A and the WDM side of station B, the alarm signals are then sent to the downstream station. The REM_SF alarm of channel 1 at optical port 3 is generated on the client side of station B. The R_LOF alarm is detected in the client equipment. l Non-R_LOS signals are accessed on the client side. The signal flow of the R_LOF or the LOC is similar to that of the R_LOS. When any other alarms are accessed, the same alarm is reported at each detection point in the system.
1 Overview
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
Station A Client-side Middle WDM-side WDM-side Station B Middle Client-side Client device Client-device R_LOF SF R_LOS R_LOF ODUk_PM_BDI& OTUk_BDI R_LOF R_LOF SF OTUk_LOF/ OTUk_AIS OTUk_LOF/ OTUk_AIS ODUk_PM_BDI& OTUk_BDI R_LOF R_LOF R_LOF R_LOF ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_OCI SF ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_OCI R_LOF R_LOF R_LOF Errors SD PM BIP8 errors ODUk_PM_DEG/ ODUk_PM_EXC Errors Errors OTUk remote BER performance events Errors Errors SD SM BIP8 errors OTUk_DEG/ OTUk_EXC Errors Errors Errors Alarm processing R_LOF
R_LOS
ODUk_PM_BDI
PM remote BER performance events SF: SF event detecting xxx SD: SD event detecting
This section describes the alarm signal flow through an example in which four client-side services are accessed on the convergent OTU. l There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, or ODUk_PM_LCK on the WDM side.
Issue 02 (2011-10-31)
1 Overview
The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU sends the ODUk_PM_BDI and OTUk_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then sent to the client side of station B. After the alarm is processed on the client side, the R_LOF alarm is detected in the client equipment. An SF event is generated on the WDM side of the OTU at station B, and a protection switching is triggered. l There are bit error alarms on the WDM side. The OTU at station B accesses and processes bit error alarm signals on the WDM side, and then sends remote bit error performance events to the WDM side of upstream station A. The bit error alarm is then sent to the client side of the downstream station B, and the bit error alarm is detected in the client equipment. An SD event is generated on the WDM side of the OTU at station B. In this case, users can determine whether the SD event triggers a service channel protection switching through proper configuration.
1.4.5 Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the convergent OTU processes standard OTN signals. Figure 1-7 and Figure 1-8 show the alarm signal flows when the convergent OTU processes standard OTN signals.
NOTE
In Figure 1-7, N#1 indicates channel 1 at optical port N of the OTU. For example, the client-side optical ports of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical port of the LQMD unit is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical port 3. 1#N indicates channel N at WDMside optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical port 1. Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and therefore is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In the middle part of the convergent OTU, the optical port number and channel number of signals are reallocated.
NOTE
Issue 02 (2011-10-31)
15
1 Overview
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
Station A Client-side R_LOS Inserts OTUk_BDI back N#1 R_LOS R_LOS Inserts OTUk_BDI back N#1 R_LOS R_LOS Inserts OTUk_BDI back N#1 R_LOS R_LOS Inserts OTUk_BDI back N#1 R_LOS R_LOS Inserts OTUk_BDI back N#1 R_LOS OTUk_LOM Inserts OTUk_BDI back N#1 OTUk_LOM OTUk_LOF Inserts OTUk_BDI back N#1 OTUk_LOF OTUk_TIM Inserts OTUk_BDI back N#1 OTUk_TIM ODUk_PM_AIS N#1 ODUk_PM_AIS Middle WDM-side WDM-side Station B Middle SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS SF N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS Client-side Client device Client-device
A B C BIT errors
N#1 A N#1 B N#1 C
1#N A 1#N B 1#N C SD
1#N A 1#N B 1#N C
N#1 BIT errors SD: SD event detecting
1#N BIT errors Alarm processing
1#N BIT errors
A, B, C are the others of the OTN alarms
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
This section describes the alarm signal flow through an example in which four client-side services are accessed on the convergent OTU. l Four channels of R_LOS signals are accessed on the client side. The OTU at station A accesses four channels of R_LOS signals on the client side. After being processed in the middle part and on the WDM side of the OTU at station A, the alarm signals are then sent to station B. The ODUk_PM_AIS alarm of the corresponding channel is generated in the middle part of station B. The ODUk_PM_AIS alarm is detected in the client device. An SF event is generated in each channel of the OTU at station B, and a protection switching is triggered. l One channel of R_LOS, OTUk_LOM or OTUk_LOF signals is accessed on the client side. The OTU at station A accesses one channel of R_LOS, OTUk_LOM or OTUk_LOF signals on the client side, for example, channel 1 at optical port 3. After being processed in the middle part and on the WDM side of the OTU at station A and the WDM side of station B, the alarm signals are then sent to the downstream station. The ODUk_PM_AIS alarm
1 Overview
of channel 3 at optical port 1 is generated in the middle part of station B. The ODUk_PM_AIS alarm is detected in the client device. An SF event is generated in each channel of the OTU at station B, and a protection switching is triggered. l The alarm signals except for the signals of the R_LOS, OTUk_LOM, and OTUk_LOF alarms are accessed on the client side. When any of other alarm signals is accessed, the corresponding alarm is reported at each detection point in the system. Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
Station A Client-side Middle WDM-side WDM-side Station B Middle Client-side Client device Client-device
ODUk_PM_AIS
R_LOS
SF R_LOS
ODUk_PM_AIS ODUk_PM_AIS
ODUk_PM_BDI &OTUk_BDI
ODUk_PM_AIS ODUk_PM_AIS
OTUk_LOF/ SF OTUk_LOM/ OTUk_LOF/ OTUk_AIS
ODUk_PM_AIS ODUk_PM_AIS ODUk_PM_AIS ODUk_PM_AIS
OTUk_LOM/ OTUk_AIS
ODUk_PM_BDI &OTUk_BDI
SF ODUk_PM_AIS/ ODUk_PM_LCK/ ODUk_PM_AIS/ ODUk_PM_OCI
ODUk_PM_AIS ODUk_PM_AIS ODUk_PM_AIS Errors
ODUk_PM_LCK/ ODUk_PM_OCI
ODUk_PM_BDI
SD PM BIP8 errors ODUk_PM_DEG/ ODUk_PM_EXC Errors Errors PM remote BER performance events Errors Errors SM BIP8 errors SD OTUk_DEG/ OTUk_EXC Errors Errors Errors Alarm processing
OTUk remote BER performance events SF: SF event detecting xxx SD: SD event detecting
Issue 02 (2011-10-31)
17

NOTE
1 Overview
The value of k on the WDM-side is different from that of the client device.
This section describes the alarm signal flow through an example in which four client-side services are accessed on the convergent OTU. l There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI or ODUk_PM_LCK on the WDM side. The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU sends the ODUk_PM_BDI or OTUk_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then sent to the client side of station B. After the alarm is processed on the client side, the ODUk_PM_AIS alarm is detected in the client device. An SF event is generated on the WDM side of the OTU at station B, and a protection switching is triggered. l There are bit error alarms on the WDM side. The WDM side of the OTU at station B accesses and processes the bit error alarm signals. The OTU sends the remote bit error performance events to the WDM side of upstream station A. The alarm is then sent to the client side of the downstream station B. The errordependent alarm is detected in the client device. An SD event is generated on the WDM side of the OTU at station B, and a protection switching is triggered.
1.4.6 Regenerating OTU

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

Station A WDM-side MFASframe discontinuous Station B(REG) WDM-side1 WDM-side2 Station C WDM-side
OTUk_LOM
ODUk_PM_AIS
OTUk_BDI PM TTI byte mismatch PM TTI byte mismatch ODUk_PM_TIM ODUk_PM_TIM TIM follow-up response is Enabled. ODUk_PM_AIS
SM TTI byte mismatch
OTUk_TIM
OTUk_BDI ODUk_PM_BDI OTUk_BDI
ODUk_PM_BDI OTUk_BDI
ODUk_PM_BDI
OTUk_LOF
OTUk_LOF
ODUk_PM_AIS
OTUk_BDI ODUk_PM_AIS/ ODUk_PM_OCI/ ODUk_PM_LCK
ODUk_PM_AIS/ ODUk_PM_OCI/ ODUk_PM_LCK
ODUk_PM_AIS/ ODUk_PM_OCI/ ODUk_PM_LCK
PM BIP8 errors
ODUk_PM_DEG/ ODUk_PM_EXC
ODUk_PM_DEG/ ODUk_PM_EXC
SM BIP8 errors
OTUk_DEG/ OTUk_EXC
Excessive bit errors before FEC BEFFEC_EXC R_LOS OTUk_BDI SF: SF event detecting SD: SD event detecting Detects and reports the xxx xxx alarm Alarm processing R_LOS ODUk_PM_AIS
In the case of the regenerating OTU, all alarms in the SM section are terminated at the local station and are not sent to the downstream station (except that the OTUk_LOF alarm is inserted with an ODUk_PM_AIS alarm to the downstream station). Other alarms are then sent to the downstream station, and are reported on the WDM side of the OTU (except that the R_LOS alarm is inserted with an ODUk_PM_AIS alarm to the downstream station).
1 Overview
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function
The OTU with the cross-connect function supports the service transmission in the straightthrough mode or the cross-connect mode. The processing of alarm signals in one mode is different from that in the other mode.
Straight-Through Mode
Figure 1-10 shows the unidirectional signal flow in the straight-through mode.
NOTE
The optical port number and channel number shown in Figure 1-10 are the numbers that are displayed on the U2000.
Figure 1-10 OTU with the cross-connect function in the straight-through mode
A 3#1(RX1) 4#1(RX2) 5#1(RX3) 6#1(RX4) 1#3 1#4 1(OUT) 1#5 1#6 1#3 1(IN) 1#4 1#5 1#6 B 3#1(TX1) 4#1(TX2) 5#1(TX3) 6#1(TX4)
As shown in Figure 1-10, the four channels of optical signals accessed from RX1-RX4 on unit A at the upstream station are sent to channels 3-6 that correspond to the OUT port in the straightthrough mode. One channel of optical signals that are input from the IN port on unit B at the downstream station is demultiplexed into four channels of optical signals, which are then directly sent to TX1-TX4. Hence, in the straight-through mode, the REM_SF and REM_SD alarms at the downstream station indicate that the signals at the corresponding port on the client side at the upstream station fail or bit errors at this port exceed the threshold. For example, when the services in channel 1 at optical port 3 on unit A at the upstream station fail, channel 1 at optical port 3 on unit B at the downstream station reports the REM_SF alarm.
Cross-Connect Mode
The cross-connect mode is classified into intra-unit cross-connection and inter-unit crossconnection. l Intra-unit cross-connection In Figure 1-11, the cross-connection from RX3 (channel 1 at optical port 5) on unit A to OUT (channel 3 at optical port 1) on unit A is defined as the intra-unit cross-connection. l Inter-unit cross-connection In Figure 1-11, the cross-connection from RX1 (channel 1 at optical port 3) on unit C to OUT (channel 6 at optical port 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.
1 Overview
Figure 1-11 OTU with the cross-connect function in the cross-connect mode
A 3#1(RX1) 4#1(RX2) 5#1(RX3) 6#1(RX4) 1#3 1#4 1(OUT) 1#5 1#6 1#3 1(IN) 1#4 1#5 1#6 B 3#1(TX1) 4#1(TX2) 5#1(TX3) 6#1(TX4)
3#1(RX1) 4#1(RX2) 5#1(RX3) 6#1(RX4) C
1#3 1#4 1#5 1#6
In Figure 1-11, the following cross-connections are created: l l Intra-unit cross-connection from RX3 (channel 1 at optical port 5) on unit A to OUT (channel 3 at optical port 1) on unit A Inter-unit cross-connection from RX1 (channel 1 at optical port 3) on unit C to OUT (channel 6 at optical port 1) on unit A
The signals that are received from RX3 (channel 1 at optical port 5) on unit A at the upstream station are sent to IN (channel 3 at optical port 1) on unit B at the downstream station. The signals received from RX1 (channel 1 at optical port 3) on unit C at the upstream station are sent to IN (channel 6 at optical port 1) on unit B at the downstream station. The meaning of optical channels regarding the REM_SF and REM_SD alarms in the crossconnect mode is different from that in the straight-through mode. For example, when the services in channel 1 at optical port 4 on unit A at the upstream station fail, unit B at the downstream station reports the REM_SF alarm in channel 1 at optical port 3; when the services in channel 1 at optical port 3 on unit C at the upstream station fail, unit B at the downstream station reports the REM_SF alarm in channel 1 at optical port 6. Hence, when a unit reports the REM_SF or REM_SD alarm, query the cross-connections of the unit at the upstream station to locate the alarm signal source. Then, check whether the client signal status such as the optical power, fibers and optical modules in the channel at the corresponding optical port is normal. If not, take the corresponding maintenance measures.
CAUTION
In any mode, proper configuration must be made on the U2000.
1.4.8 OTU Processing GE Signals

This section describes the alarm signal flow when the OTU board processes Ethernet service signals.
1 Overview
The GE services are encapsulated into OTN signals or SDH signals after they are accessed on the client side of the OTU on an Ethernet network. The alarm signal processing when the GE services are encapsulated into OTN signals differs slightly from the alarm signal processing when the GE services are encapsulated into SDH signals. Figure 1-12 and Figure 1-13 show the signal flow when the GE services are encapsulated into OTN signals and the signal flow when the GE services are encapsulated into SDH signals respectively.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Issue 02 (2011-10-31)
22
1 Overview
Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals
Station A Client-side Middle WDMside WDMside Station B Middle Client-side
Client device
Client-device
Scenario 1: The client sides are in the non-negotiation mode.

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

R_LOS R_LOS
REM_SF LINK_ERR LPT=Enable None LPT=Disable LINK_ERR None
LINK_ERR
LINK_ERR LINK_ERR Errors
LINK_ERR
Errors PM BIP8 errors

SD ODUk_PM_DEG/ ODUk_PM_EXC
Errors
Errors
PM remote BER performance events SM BIP8 errors

SD OTUk_DEG/ OTUk_EXC
Errors
OTUk remote BER performance events R_LOS OTUk_BDI& ODUk_PM_BDI
SF
R_LOS
LINK_ERR
SF OTUk_AIS/ OTUk_LOF/ OTUk_AIS/ OTUk_LOM OTUk_LOF / OTUk_LOM OTUk_BDI& ODUk_PM_BDI
LINK_ERR
ODUk_PM_AIS/ SF ODUk_PM_OCI/ ODUk_PM_LCK ODUk_PM_AIS/ ODUk_PM_OCI/ ODUk_PM_LCK ODUk_PM_BDI
LINK_ERR
SD: SD event detecting
Alarm processing
This section describes the alarm signal flow when the OTU processes the R_LOS and LINK_ERR alarms. The signal flow for processing other alarms is similar. l R_LOS
Issue 02 (2011-10-31)
23
1 Overview
The client sides of the OTUs at station A and station B work in the non-auto-negotiation mode. The R_LOS alarm signal is received on the client side of the OTU at station A. The alarm signal is sent to station B after it is processed on the WDM side of the OTU. In this case, the REM_SF alarm is generated on the client side of the OTU at station B, and the client equipment at station B reports the LINK_ERR alarm. The client sides of the OTUs at station A and station B work in the auto-negotiation mode. The R_LOS alarm signal is received on the client side of the OTU at station A. The alarm signal is sent to station B after it is processed on the WDM side of the OTU. In this case, the REM_SF and LINK_ERR alarms are generated on the client side of the OTU at station B, and the client equipment at station B reports the LINK_ERR alarm. l LINK_ERR The client sides of the OTUs at station A and station B work in the non-auto-negotiation mode. The client signals at station A contain LINK_ERR alarms, and the client signals are transmitted transparently from station A to the WDM side of the OTU at station B. The client sides of the OTUs at station A and station B work in the auto-negotiation mode. In the case of the Ethernet board that supports the LPT function, when the LPT enabling status is set to Disable, the LINK_ERR alarm is not generated on the client side of the OTU at station B; when the LPT enabling status is set to Enable, the LINK_ERR alarm is generated on the client side of the OTU at station B. Figure 1-13 Alarm signal flow 2: when the OTU processes GE signals
Station A Client-side WDM-side WDM-side Station B Client-side Client device Client-device
Scenario 1: The client sides are in the non-negotiation mode.

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

R_LOS R_LOS REM_SF LINK_ERR LPT=Enable LINK_ERR None LPT=Disable R_LOS SF R_LOS None LINK_ERR LINK_ERR None LINK_ERR
LINK_ERR
LINK_ERR
MS_BDI SF: SF event detecting xxx Alarm processing
Issue 02 (2011-10-31)
24
1 Overview
This section describes the alarm signal flow when the R_LOS alarm is received on the WDM side of the OTU at station B. The signal flow for processing other alarms is similar to Figure 1-12. After the R_LOS alarm is received on the WDM side of the OTU at station B, the SF event is generated. In addition, station B sends the MS_BDI alarm to the WDM side of the OTU at station A, and the client equipment at station B reports the LINK_ERR alarm.
1.4.9 Optical-Layer Alarm Signal Processing on OTN

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

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

OD OA
OTU
OA OM
OA
OTU OTU
Station A
Station B
Station C
1 Overview
At station A, the fiber in direction SC1-to-FIU is cut. The FIU board at station B reports the OTS_LOS-O alarm. The OD unit at station C reports the OMS_FDI-O or OMS_SSF-O alarm. The FIU board and OM unit at station A report the OTS_BDI-O alarm and OMS_BDI-O alarm respectively.
The configuration of TTI to be received at station B is inconsistent with TTI transmitted by station A. The FIU board at station B reports the OTS_TIM alarm. The OD unit at station C reports the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A report the OTS_BDI alarm and OMS_BDI alarm respectively.
The OM unit at station A is faulty. The OD unit at station C reports the OMS_LOS-P alarm and the OM unit at station A reports the OMS_BDI-P alarm.
The OTU board at station A is faulty. The OTU board at station B reports the OCh_LOS-P alarm.
Figure 1-16 Scenario III

West clientside OTU OTU
OM OA
East clientside O O OO T T T T U U U U OM O T U
OA OD
OOO T T T U U U OD
OTU
OTU OTU
In this scenario, there are three stations. Station A and station C are OTM stations, and station B is an ROADM station. In this scenario, station ROADM adds and drops certain wavelengths. That is, certain wavelengths are between stations A and B, or stations B and C, and the other wavelengths are between stations A and C. Hence, certain OCh trails are between stations A and B, or B and C, and the other OCh trails are between stations A and C. In case of the following faults, the association relations of alarms are as follows: l The fiber from station A to station B is cut. The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for wavelengths between stations A and C). l At station A, the optical amplifier unit in direction A-to-B is faulty.
Issue 02 (2011-10-31)
West line-side ODF
East line-side ODF
Line-side ODF
Line-side ODF
OTU
SC1
OA FI U OA
WSD9 SC2 RMU9
RMU9
OA FIU
FI U
FIU
SC1
OTU OTU
OD OA
WSD9
OA
OTU
OA OM
OM O T U
OD OO T T UU
OTU OTU
OTU
O O OO O T T T T T U U UU U
West clientside
East clientside
Station A
Station B
Station C
27
1 Overview
The FIU board at station B reports the OTS_LOS-P alarm and the FIU board at station A reports the OTS_BDI-P alarm. Station C reports the OCh_FDI-P or OCh_SSF-P alarm (for wavelengths between stations A and C). l At station A, the optical amplifier in direction A-to-B loses input light. The FIU board at station A inserts the OTS_PMI signal and the FIU board at station B does not report the OTS_LOS-P alarm. l At station A, the fiber in direction SC1-to-FIU is cut. The FIU board at station B reports the OTS_LOS-O alarm and the FIU board at station A reports the OTS_BDI-O alarm. Station C reports the OCh_FDI-O or OCh_SSF-O alarm (for wavelengths between stations A and C). l The configuration of TTI to be received at station B is inconsistent with TTI transmitted by station A. The FIU board at station B reports the OTS_TIM alarm and the FIU board at station A reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for wavelengths between stations A and C). l The OM unit at station A is faulty. The OD unit at station B reports the OMS_LOS-P alarm and the OM unit at station A reports the OMS_BDI-P alarm. Station C reports the OCh_FDI-P or OCh_SSF-P alarm (for wavelengths between stations A and C). l The OTU board at station A is faulty. The OTU board at station B reports the OCh_LOS-P alarm (for wavelengths between stations A and B). The OTU board at station C reports the OCh_LOS-P alarm (for wavelengths between stations A and C). l The fiber from station B to station C is cut. The FIU board at station C reports the OTS_LOS alarm and the FIU board at station B reports the OTS_BDI alarm. l At station B, the optical amplifier unit in direction B-to-C is faulty. The FIU board at station C reports the OTS_LOS-P alarm and the FIU board at station B reports the OTS_BDI-P alarm. l At station B, the optical amplifier in direction B-to-C loses input light. The FIU board at station B inserts the OTS_PMI signal and the FIU board at station C does not report the OTS_LOS-P alarm. l At station B, the fiber in direction SC1-to-FIU is cut. The FIU board at station C reports the OTS_LOS-O alarm and the FIU board at station B reports the OTS_BDI-O alarm. l The configuration of TTI to be received at station C is inconsistent with TTI transmitted by station B. The FIU board at station C reports the OTS_TIM alarm and the FIU board at station B reports the OTS_BDI alarm. l The OM unit at station B is faulty. The OD unit at station C reports the OMS_LOS-P alarm and the OM unit at station B reports the OMS_BDI-P alarm. l The OTU board at station B is faulty. The OTU board at station C reports the OCh_LOS-P alarm (for wavelengths from station B to station C).
1 Overview
1.5 Suppression Relationship of Alarms

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

There is no alarm suppression for the alarms of different TCM layers. The suppression of OTN alarms is shown in the Figure 1-17. The alarm above the arrow suppresses the alarm below the arrow. For example, the OTUk_LOM alarm suppresses the OTUk_TIM alarm.
Issue 02 (2011-10-31)
29
1 Overview
Figure 1-17 Suppression of OTN alarms

OCH_LOS
OTUk_LOF
OTUk_LOM OTUk_SSF
OTUk_TIM
Note: The TIM alarm suppresses the BDI alarm and DEG alarm of the same layer just when the TIM follow-up response is Enabled.
OTUk_BDI
ODUk_LOFLOM
OTUk_DEG
ODUk_TCMn_LTC/ ODUk_TCMn_LCK/ ODUk_TCMn_OCI
ODUk_TCMn_SSF
ODUk_TCMn_TIM
ODUk_TCMn_BDI ODUk_PM_OCI/ ODUk_PM_LCK ODUk_PM_SSF
ODUk_TCMn_DEG
ODUk_PM_TIM
ODUk_PM_BDI OPUk_PLM
ODUk_PM_DEG
OPUk_MISM
Issue 02 (2011-10-31)
30
1 Overview
1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment Alarms
The suppression of SDH service alarms and other common alarms related to equipment alarms is shown in Figure 1-18. The alarm above the arrow suppresses the alarm below the arrow. For example, when an optical port on the client side loses signals, the optical port only reports the R_LOS alarm. The R_LOC and R_LOF alarms are not reported. Figure 1-18 Suppression of alarms related to SDH services and other common equipment alarms
PORT_MODULE_OF FLINE
TEM_HA/TEM_LA
LSR_COOL_ALM
IN_PWR_HIGH/ OUT_PWR_HIGH TF LSR_WILL_DIE
OUT_PWR_LOW R_LOS
TD
R_LOC R_LOF
IN_PWR_LOW
BEFFEC_EXC J0_MM
MS_REI B1_EXC
B2_EXC
MS_AIS B1_SD
MS_RDI B2_SD
Issue 02 (2011-10-31)
31
1 Overview
1.6 Performance Event Suppression by Alarms

An optical interface can report several alarms and performance events. Some performance events are not important for the maintenance engineer. When the equipment is faulty, several alarms and performance events may be generated by the same optical interface. However, some alarms and performance events are not important for the maintenance engineer. For example, when the signal is lost, the optical interface generates the R_LOS alarm accompanied with the B1 bit error performance event. However, the B1 bit error performance event is not important for the maintenance engineer. In this case, the equipment suppresses the B1 bit error performance event through the R_LOS alarm. Only the R_LOS alarm is reported by the optical interface. For OptiX OSN 8800, Table 1-4 lists the performance events suppressed by the R_LOS alarm. For OptiX OSN 6800/3800, Table 1-5 lists the performance events suppressed by the R_LOS alarm. Table 1-4 Performance events suppressed by the R_LOS alarm (OptiX OSN 8800) MSBBE MSES MSFEES MSFESES MSFEBBE MSFEUAS RSBBE RSES RSCSES RSOFS FEC_AFT_COR_ER FEC_BEF_COR_ER LSIOPCUR LSIOPMAX LSIOPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN
Table 1-5 Performance events suppressed by the R_LOS alarm (OptiX OSN 6800/3800) MSBBE MSES MSCSES MSFEES MSFESES MSFEBBE MSFECSES MSFEUAS RSBBE RSES RSCSES RSOFS FEC_AFT_COR_ER FEC_BEF_COR_ER LSIOPCUR LSIOPMAX LSIOPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN
Table 1-6 lists the performance events suppressed by the NO_BD_PARA alarm.
Issue 02 (2011-10-31)
32
1 Overview
Table 1-6 Performance events suppressed by the NO_BD_PARA alarm LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSTMPCUR LSTMPMAX LSTMPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSIOPCUR LSIOPMAX LSIOPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN
Issue 02 (2011-10-31)
33
2 Alarm List
2
About This Chapter
2.2 Board Alarm List Lists the alarms of every board.
Alarm List
This topic describes the alphabetical lists of alarms and lists alarms of every board. 2.1 Product Alarm List This section lists the alarms supported by the product in alphabetical order.
Issue 02 (2011-10-31)
34
2 Alarm List
2.1 Product Alarm List

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

This section used a table to list the alarms starting with A. Name AD_CHECK_FAIL Description AD (analog to digital converter) self check failure Automatic laser shutdown (ALS) alarm The loss of GFP client signal The loss of GFP frame delineation ALC link adjustment failure ALC link anomaly and wait for adjustment ALS occurred The orderwire phone is in the off-hook state for a long time APE adjustment failure APE adjustment is pending for operation. The MSP protocol is manually stopped APS protection switching failure An alarm indicating the APS state AU alarm indication signal AU loss of pointer Level Major
ALM_ALS ALM_GFP_dCSF ALM_GFP_dLFD ALC_ADJUST_FAIL ALC_WAIT_ADJUST ALS_ACTIVE ALM_HANGUP
Minor Critical Major Major Major Minor Minor
APE_ADJUST_FAIL APE_ADJUST_PEND APS_MANUAL_STOP APS_FAIL APS_INDI AU_AIS AU_LOP
Major Major Minor Major Major Major Major
Issue 02 (2011-10-31)
35
2 Alarm List
2.1.2 Alarm List B

This section used a table to list the alarms starting with B. Name B1_EXC B1_SD B2_EXC B2_SD B3_EXC Description Regenerator section (B1) excessive errors Regenerator section (B1) signal degraded Multiplex section (B2) excessive errors Multiplex section (B2) signal degraded The number of higher order path B3 bit errors in the signals received on the line exceeds the threshold The number of B3 bit errors in the lower order path VC-3 exceeds the threshold. The number of B3 bit errors in the VC-4 path exceeds the threshold. The higher order path B3 signals received on the line are degraded. The number of VC-3 B3 bit errors exceeds the threshold. The number of B3 bit errors in the VC-4 path exceeds the threshold. Logic board not installed alarm Board out of position An alarm of slot verification error Signal degraded before FEC BOOTROM data check failed Level Minor Minor Major Minor Major
B3_EXC_VC3
Major
B3_EXC_VC4
Major
B3_SD
Minor
B3_SD_VC3
Minor
B3_SD_VC4
Minor
BD_NOT_INSTALLED BD_STATUS BDID_ERROR BEFFEC_EXC BOOTROM_BAD
Minor Major Major Minor Major
Issue 02 (2011-10-31)
36
2 Alarm List
Name BUS_ERR
Description Bus error
Level Critical
2.1.3 Alarm List C

This section used a table to list the alarms starting with C. Name C2_VCAIS CFCARD_FAILED CHAN_ADD CHAN_LOS CHIP_ABN CLIENT_PROT_NOTSTART CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLK_NO_TRACE_MODE CLK_LOCK_FAIL COMMUN_FAIL CPC_NODE_ID_ERR CRC4_CROSSTR Description A C2 byte alarm indication CF Card Failed Channel of single wave signal add Channel of single wave signal loss Temperature chip failure Client-side 1+1 protection group not started Client-side 1+1 protection switching The state of the client-side 1+1 optical channel protection group The clock enters into a non-tracing running mode. Clock lockout failure alarm Internal communication failure on the board Node ID Error CRC4 multi-frame error code count exceeds the threshold Level Minor Major Major Critical Minor Minor Major Minor
Minor Major Major Critical Minor
2.1.4 Alarm List D

This section used a table to list the alarms starting with D.
Issue 02 (2011-10-31)
37
2 Alarm List
Name DB_RESTORE_FAIL DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MODE DBPS_ABNORMAL DCM_INSUFF DLAG_PROTECT_FAIL DSP_LOAD_FAIL
Description Database restore fail alarm Database state is abnormal Database error alarm Database in protect mode DBPS abnormal alarm Insufficient dispersion compensation margin DLAG protect failed alarm DSP software loading failure
Level Major Major Major Critical Major Warning Major Major
2.1.5 Alarm List E

This section used a table to list the alarms starting with E. Name ETH_8B10B_ERR ETH_CFM_LOC ETH_CFM_MISMERGE ETH_CFM_MACSTATUS ETH_CFM_RDI ETH_CFM_UNEXPERI ETH_MISCONNECT ETH_SERVICE_CONFIG_ FAIL ETHOAM_DISCOVER_F AIL ETHOAM_RMT_CRIT_F AULT Description Ethernet line signal encoding/ decoding error Service connectivity loss Misconnection Remote MAC defect indication A remote CFM_OAM alarm indication Errored frame Network interface misconnection alarm Ethernet service configuration failure The point-to-point Ethernet OAM discovery failure alarm A critical fault occurs to the remote end of point-to-point Ethernet OAM Level Minor Critical Critical Major Minor Minor Major Major Minor Minor
Issue 02 (2011-10-31)
38
2 Alarm List
Name ETHOAM_RMT_LOOP
Description The remote loopback of point-to-point Ethernet OAM alarm The remote SD of point-topoint Ethernet OAM alarm Loopback of the MAC port that receives the OAM protocol packets in a point-topoint manner Loopback of the VCTRUNK port that receives the OAM protocol packets in a point-topoint manner Loss of the periodic continuity check message The maintenance point ID conflict The extended wavelength module offline The loss of external clock source The loss of the external timing source
Level Minor
ETHOAM_RMT_SD ETHOAM_SELF_LOOP
Minor Major
ETHOAM_VCG_SELF_L OOP
Major
EX_ETHOAM_CC_LOS EX_ETHOAM_MPID_CN FLCT EXT_MODULE_OFFLINE EXT_SYNC_LOS EXT_TIME_LOC
Critical Major Major Critical Major
2.1.6 Alarm List F

This section used a table to list the alarms starting with F. Name FAN_FAIL FAN_FAULT FC_8B10BERR_OVER FC_LINK_ERR FC_SYNC_LOS Description Fan failed Fan fault 8B10B bit error rate crossing alarm FC service link failure alarm FC service synchronous word loss alarm Level Major Minor Minor Critical Critical
Issue 02 (2011-10-31)
39
2 Alarm List
Name FCS_ERR FEATURE_WITHOUT_LICENSE FLOW_OVER FEC_LOF FEC_OOF FPGA_ABN FSELECT_STG FWD_PKT_LOSS
Description The frame check sequence (FCS) is incorrect Service without license The inflow at the Ethernet port exceeds the threshold Received FEC is loss of frame Received FEC is out of frame FPGA status is abnormal The clock board is forcibly selected Packets droped alarms
Level Critical Major Minor Critical Critical Major Major Minor
2.1.7 Alarm List G

This section used a table to list the alarms starting with G. Name GAINDATA_MIS Description Mismatch of gain attribute Level Major
2.1.8 Alarm List H

This section used a table to list the alarms starting with H. Name HARD_BAD HARD_ERR HP_LOM HP_RDI HP_REI Description Hardware failed Minor hardware error Loss of multiframe in the higher order path A remote defect in the higher order path A remote error indication in the higher order path Level Critical Minor Major Minor Warning
Issue 02 (2011-10-31)
40
2 Alarm List
Name HP_SLM
Description A signal label mismatch alarm in the higher order path A trace identifier mismatch alarm in the higher order path An alarm indicating that no signals are loaded in the higher order path Working/protection switching failed
Level Minor
HP_TIM
Minor
HP_UNEQ
Minor
HSC_UNAVAIL
Minor
2.1.9 Alarm List I

This section used a table to list the alarms starting with I. Name IN_PWR_HIGH IN_PWR_LOW INTRA_OTU_PS INTRA_OTU_STA_INDI Description Input optical power is too high Input optical power is excessively low Intra-OTU 1+1 protection switching The state of the Intra-OTU 1+1 optical channel protection group Laser shutdown by IPA Level Critical Critical Major Minor
IPA_SHUT
Minor
2.1.10 Alarm List J

This section used a table to list the alarms starting with J. Name J0_MM Description J0 byte or trace indicator mismatch Level Minor
Issue 02 (2011-10-31)
41
2 Alarm List
2.1.11 Alarm List K

This section used a table to list the alarms starting with K. Name K1_K2_M K2_M Description The K1 and K2 bytes mismatch alarm The K2 bytes mismatch alarm Level Minor Minor
2.1.12 Alarm List L

This section used a table to list the alarms starting with L. Name L_SYNC LAG_PORT_FAIL LAG_VC_PORT_FAIL LAN_LOC LASER_HAZARD_WARN ING LASER_MODULE_MISMATCH LASER_SHUT LCAS_FOPR Description Loss of synchronization alarm Aggregation group VCG port failure alarm Aggregation group VCG port failure alarm Ethernet communication failure Warning indication of the laser hazard level. Optical module mismatch alarm The laser of the board is shut down The failure of the LCAS protocol in the receive direction The failure of the LCAS protocol in the transmit direction Partial loss of capacity in the LCAS receive direction Partial loss of capacity in the LCAS transmit direction
Level Critical Minor Minor Major Critical Major Major Major
LCAS_FOPT
Major
LCAS_PLCR
Minor
LCAS_PLCT
Minor
Issue 02 (2011-10-31)
42
2 Alarm List
Name LCAS_TLCR
Description The total loss of capacity in the LCAS receive direction Total loss of capacity in the LCAS transmit direction License in keepalive period License expired No license file Incorrect data link Local fault Mismatch of lock-power attribute Pump drive current unlocked alarm Indication of loop operating Aremote defect indication in the VC-3 lower order path A signal label mismatch alarm in the VC-3 lower order path
Level Major
LCAS_TLCT
Major
LCS_DAYS_OF_GRACE LCS_EXPIRED LCS_FILE_NOT_EXIST LINK_ERR LOCAL_FAULT LOCKPOW_MIS LOCK_CUR_FAIL LOOP_ALM LP_RDI_VC3
Major Critical Critical Critical Minor Major Critical Minor Minor
LP_SLM_VC3
Minor
LP_UNEQ_VC3 LPT_ACTIVE LPT_RFI
No payload is equipped in Minor the VC-3 lower order path LPT switching is active A remote failure indication alarm of link state pass through Cooling current of the laser over threshold Laser forced open Invalid optical module alarm Laser will be out of work Major Critical
LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE
Major Minor Critical Critical
Issue 02 (2011-10-31)
43
2 Alarm List
Name LTI
Description The loss of synchronization source
Level Major
2.1.13 Alarm List M

This section used a table to list the alarms starting with M. Name MAINBD_SUBBD_MISMATCH MOD_COM_FAIL MODULE_ADJUST_FAIL MODULE_COOLCUR_OVE R MODULE_TEMP_OVER MODULEFILE_UPDATE_F AIL MS_AIS MS_APS_INDI_EX Description Mainboard and subboard mismatch Module communicates abnormally Adjustment of optical module failed Module cooling current exceeds the threshold Module temperature exceeds the threshold Updating the microprogram and laser parameter table failed Multiplex section alarm indication An extended indication alarm of the MSP switching state Multiplex section performance over threshold Multiplex section remote defect indication Multiplex section remote error indication MS SNCP protection switch The state of the MS SNCP protection group More than one RPL_OWNER alarm Loss of multiplexed signals
Level Major Major Major Major Major Major
Major Major
MS_CROSSTR MS_RDI MS_REI MS_SNCP_PS MS_SNCP_STA_INDI MULTI_RPL_OWNER MUT_LOS

Issue 02 (2011-10-31)
Minor Minor Warning Major Minor Minor Critical

44
2 Alarm List
2.1.14 Alarm List N

This section used a table to list the alarms starting with N. Name NEBD_XC_DIF NESF_LOST NESTATE_INSTALL NO_BD_PARA NO_BD_SOFT NO_ELABEL NODEID_MM Description Crossing data of NE and board different Lack a set of host software NE is in install state, not configured No board parameter No board software E-label unloaded The NODEID_MM is an alarm indicating the MSP node ID mismatch NTP synchronization failure The NULL signals (overhead is expressed in all "0"s) are sent out Level Critical Critical Critical Critical Critical Warning Major
NTP_SYNC_FAIL NULL_SEND
Minor Warning
2.1.15 Alarm List O

This section used a table to list the alarms starting with O. Name OA_LOW_GAIN OCH_FDI OCH_FDI-O OCH_FDI-P OCH_LOS-P Description Optical multiplexed signal gain low Forward defect indication at OCh layer Forward defect indication at OCh layer (overhead) Forward defect indication at OCh layer (payload) Loss of signal (payload) at OCh layer Level Critical Warning Warning Warning Critical
Issue 02 (2011-10-31)
45
2 Alarm List
Name OCH_OCI OCH_SSF OCH_SSF-O OCH_SSF-P ODU_AIS
Description Open connection indication at OCh layer Server signal fail at OCh layer Server signal fail (overhead) at OCh layer Server signal fail (payload) at OCh layer ODU (optical channel data unit) alarm indication signal ODU locked ODU open connection indication ODU SNCP protection switching The state of the ODU SNCP protection group OPUFLEX Payload Label Mismatch The FAS and MFAS are abnormal ODUFlex PM Alarm Indication Signal ODU0 PM Backward Defect Indication ODUFlex PM Signal Degrade Alarm ODUFlex PM Section Excessive BIP8 Errors defect ODUFlex PM Lockout Defect ODUFlex PM Open Connection Indication ODUFlex PM Server Signal Fail
Level Minor Warning Warning Warning Warning
ODU_LCK ODU_OCI ODU_SNCP_PS ODU_SNCP_STA_INDI ODUFLEX_PLM ODUFLEX_LOFLOM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_EXC
Major Major Major Minor Minor Critical Major Minor Minor Minor
ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF
Minor Minor Critical
Issue 02 (2011-10-31)
46
2 Alarm List
Name ODUFLEX_PM_TIM ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU0_PM_EXC ODU0_TCMn_AIS ODU0_TCMn_BDI ODU0_TCMn_DEG ODU0_TCMn_LCK ODU0_TCMn_LTC ODU0_TCMn_OCI ODU0_TCMn_SSF ODU0_TCMn_TIM ODU0_TCMn_EXC
Description ODUFlex PM Trace Identifier Mismatch The FAS and MFAS are abnormal ODU0 PM alarm indication signal ODU0 PM backward defect indication ODU0 PM signal degraded ODU0 PM signal locked ODU0 PM open connection indication ODU0 PM Server signal fail ODU0 PM section TTI mismatch ODU0 PM section BIP8 excessive error defect ODU0 TCMn alarm indication signal ODU0 TCMn backward defect indication ODU0 TCMn signal degraded ODU0 TCMn signal locked Loss of ODU0 TCMn serial connection ODU0 TCMn open connection indication ODU0 TCMn Server signal fail ODU0 TCMn TTI mismatch ODU0 TCMn section BIP8 excessive error defect
Level Minor Critical Warning Warning Minor Minor Minor Warning Minor Major Warning Warning Minor Minor Minor Minor Warning Minor Major
Issue 02 (2011-10-31)
47
2 Alarm List
Name ODU0_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_PM_EXC ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU1_TCMn_EXC
Description The FAS and MFAS are abnormal ODU1 PM alarm indication signal ODU1 PM backward defect indication ODU1 PM signal degraded ODU1 PM signal locked ODU1 PM open connection indication ODU1 PM Server signal fail ODU1 PM section TTI mismatch ODU1 PM section BIP8 excessive error defect ODU1 TCMn alarm indication signal ODU1 TCMn backward defect indication ODU1 TCMn signal degraded ODU1 TCMn signal locked Loss of ODU1 TCMn serial connection ODU1 TCMn open connection indication ODU1 TCMn Server signal fail ODU1 TCMn TTI mismatch ODU1 TCMn section BIP8 excessive error defect The FAS and MFAS are abnormal
Level Critical Warning Warning Minor Minor Minor Warning Minor Major Warning Warning Minor Minor Minor Minor Warning Minor Major
ODU2_LOFLOM
Critical
Issue 02 (2011-10-31)
48
2 Alarm List
Name ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_PM_EXC ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODU2_TCMn_EXC
Description ODU2 PM alarm indication signal ODU2 PM backward defect indication ODU2 PM signal degraded ODU2 PM signal locked ODU2 PM open connection indication ODU2 PM server signal fail ODU2 PM section TTI mismatch ODU2 PM section BIP8 excessive error defect ODU2 TCMn alarm indication signal ODU2 TCMn backward defect indication ODU2 TCMn signal degraded ODU2 TCMn signal locked Loss of ODU2 TCMn serial connection ODU2 TCMn open connection indication ODU2 TCMn server signal fail ODU2 TCMn TTI mismatch ODU2 TCMn section BIP8 excessive error defect ODU3 PM alarm indication signal ODU3 PM backward defect indication
Level Warning Warning Minor Minor Minor Warning Minor Major Warning Warning Minor Minor Minor Minor Warning Minor Major
ODU3_PM_AIS ODU3_PM_BDI
Warning Warning
Issue 02 (2011-10-31)
49
2 Alarm List
Name ODU3_PM_DEG ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_PM_EXC ODU3_TCMn_AIS ODU3_TCMn_BDI ODU3_TCMn_DEG ODU3_TCMn_LCK ODU3_TCMn_LTC ODU3_TCMn_OCI ODU3_TCMn_SSF ODU3_TCMn_TIM ODU3_TCMn_EXC
Description ODU3 PM signal degraded ODU3 PM signal locked ODU3 PM open connection indication ODU3 PM server signal fail ODU3 PM section TTI mismatch ODU3 PM section BIP8 excessive error defect ODU3 TCMn alarm indication signal ODU3 TCMn backward defect indication ODU3 TCMn signal degraded ODU3 TCMn signal locked Loss of ODU3 TCMn serial connection ODU3 TCMn open connection indication ODU3 TCMn server signal fail ODU3 TCMn TTI mismatch ODU3 TCMn section BIP8 excessive error defect The FAS and MFAS are abnormal ODU5G PM alarm indication signal ODU5G PM backward defect indication ODU5G PM signal degraded
Level Minor Minor Minor Warning Minor Major Warning Warning Minor Minor Minor Minor Warning Minor Major
ODU5G_LOFLOM ODU5G_PM_AIS ODU5G_PM_BDI ODU5G_PM_DEG
Critical Warning Warning Minor
Issue 02 (2011-10-31)
50
2 Alarm List
Name ODU5G_PM_EXC ODU5G_PM_LCK ODU5G_PM_OCI ODU5G_PM_SSF ODU5G_PM_TIM ODU5G_TCMn_AIS ODU5G_TCMn_BDI ODU5G_TCMn_DEG ODU5G_TCMn_EXC
Description ODU5G PM section BIP8 excessive error defect ODU5G PM signal locked ODU5G PM open connection indication ODU5G PM server signal fail ODU5G PM section TTI mismatch ODU5G TCMn alarm indication signal ODU5G TCMn backward defect indication ODU5G TCMn signal degraded ODU5G TCMn section BIP8 excessive error defect ODU5G TCMn signal locked Loss of ODU5G TCMn serial connection ODU5G TCMn open connection indication ODU5G TCMn server signal fail ODU5G TCMn TTI mismatch ODUk SP protection switch The state of the ODUk SPRing protection group Overhead bus loopback Optical line protection switching The state of the optical line protection group
Level Major Minor Minor Warning Minor Warning Warning Minor Major
ODU5G_TCMn_LCK ODU5G_TCMn_LTC ODU5G_TCMn_OCI ODU5G_TCMn_SSF ODU5G_TCMn_TIM ODUKSP_PS ODUKSP_STA_INDI OH_LOOP OLP_PS OLP_STA_INDI
Minor Minor Minor Warning Minor Major Minor Minor Major Minor
Issue 02 (2011-10-31)
51
2 Alarm List
Name OMS_BDI OMS_BDI-O
Description Backward defect indication at OMS layer Backward defect indication (overhead) at OMS layer Backward defect indication (payload) at OMS layer Forward defect indication at OMS layer Forward defect indication (overhead) at OMS layer Forward defect indication (payload) at OMS layer Loss of signal (payload) at OMS layer Server signal fail at OMS layer Server signal fail (overhead) at OMS layer Server signal fail (payload) at OMS layer The phase-locked loop is out of lock Loss of OOS Automatic adjustment of power during optical cross-connection failed OPU0 payload mismatch OPU1 payload mismatch OPU1 multiplex structure indicator mismatch OPU1 sequence indicator mismatch OPU1 virtual concatenation payload mismatch
Level Warning Warning
OMS_BDI-P
Warning
OMS_FDI OMS_FDI-O OMS_FDI-P OMS_LOS-P OMS_SSF OMS_SSF-O OMS_SSF-P OOL OOS_LOST OPA_FAIL_INDI
Warning Warning Warning Critical Warning Warning Warning Major Minor Major
OPU0_PLM OPU1_PLM OPU1_MSIM OPU1_VCAT_SQM OPU1_VCAT_VcPLM
Minor Minor Minor Major Minor
Issue 02 (2011-10-31)
52
2 Alarm List
Name OPU2_MSIM OPU2_PLM OPU3_MSIM OPU3_PLM OPU5G_PLM OSC_BDI OSC_DEG OSC_LOS OSC_RDI OTU_AIS OTU_LOF OTU_LOM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF
Description OPU2 multiplex structure indicator mismatch OPU2 payload mismatch OPU3 multiplex structure indicator mismatch OPU3 payload mismatch OPU5G payload mismatch OSC Backward defect indication OSC signal degrade Loss of OSC signal Remote defect indication OTU alarm indication signal Loss of frame Loss of Multi-frame OTU1 alarm indication signal OTU1 backward defect indication OTU1 signal degraded OTU1 BIP8 excessive error defect The FAS is abnormal The MFAS is abnormal OTU1 server signal fail OTU1 TTI mismatch OTU2 alarm indication signal OTU2 backward defect indication OTU2 signal degraded The FAS is abnormal
Level Minor Minor Minor Minor Minor Minor Minor Critical Minor Warning Critical Major Warning Warning Minor Major Critical Major Warning Minor Warning Warning Minor Critical
Issue 02 (2011-10-31)
53
2 Alarm List
Name OTU2_LOM OTU2_SSF OTU2_TIM OTU2_EXC OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OTU3_EXC OTU5G_AIS OTU5G_BDI OTU5G_DEG OTU5G_EXC OTU5G_LOF OTU5G_LOM OTU5G_SSF OTU5G_TIM OTS_BDI OTS_BDI-O
Description The MFAS is abnormal OTU2 server signal fail OTU2 TTI mismatch OTU2 BIP8 excessive error defect OTU3 alarm indication signal OTU3 backward defect indication OTU3 signal degraded The FAS is abnormal The MFAS is abnormal OTU3 server signal fail OTU3 TTI mismatch OTU3 BIP8 excessive error defect OTU5G alarm indication signal OTU5G backward defect indication OTU5G signal degraded OTU5G BIP8 excessive error defect The FAS is abnormal The MFAS is abnormal OTU5G server signal fail OTU5G TTI mismatch Backward defect indication at OTS layer Backward defect indication (overhead) at OTS layer Backward defect indication (payload) at OTS layer
Level Major Warning Minor Major Warning Warning Minor Critical Major Warning Minor Major Warning Warning Minor Major Critical Major Warning Minor Warning Warning
OTS_BDI-P
Warning
Issue 02 (2011-10-31)
54
2 Alarm List
Name OTS_LOS OTS_LOS-O OTS_LOS-P OTS_TIM OUT_PWR_HIGH OUT_PWR_LOW OWSP_PS OWSP_STA_INDI
Description Loss of signal at OTS layer Loss of signal (overhead) at OTS layer Loss of signal (payload) at OTS layer Trail trace identifier mismatch at OTS layer Output optical power is too high Output optical power is excessively low Optical wave share protection switching the state of the optical wave share protection group
Level Critical Major Critical Minor Major Major Major Minor
2.1.16 Alarm List P

This section used a table to list the alarms starting with P. Name PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR PM_BDI Description Activated patch overtime Deactivated patch overtime Patch package file error ODU PM section backward defect indication ODU PM section backward error indication ODU layer, PM section BIP exceed the upper threshold Optical channel data unit layer, path monitoring section bit interleaved parity signal degraded Level Minor Minor Minor Major
PM_BEI PM_BIP8_OVER
Major Major
PM_BIP8_SD
Major
Issue 02 (2011-10-31)
55
2 Alarm List
Name PM_TIM PORT_MODULE_OFFLINE PORTSWITCH_FAIL POWER_ABNORMAL POWER_DIFF_OVER
Description ODU layer PM section TTI mismatch Port module offline Optical switch switching failure Power supply failure Power difference between optical monitoring active and standby crossed the threshold Power failure PRBS signal lost alarm PTP time source switching alarm PTP time stamp anomaly Working temperature of the pump laser over threshold Working current of pump laser over threshold Cooling current of pump laser over threshold
Level Major Major Major Major Major
POWER_FAIL PRBS_LSS PTP_SOURCE_SWITCH PTP_TIMESTAMP_ABN PUM_TEM_ALM
Major Minor Minor Major Major
PUM_BCM_ALM PUMP_COOL_EXC
Major Critical
2.1.17 Alarm List R

This section used a table to list the alarms starting with R. Name R_LOC R_LOF R_LOS R_OOF R_SLIP RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE
Issue 02 (2011-10-31)
Description Loss of clock on receiving line Loss of frame on receiving line Loss of signal on receiving line Out of frame on receiving line Receiving side frame slipping Critical relay alarm Relay alarm warning
Level Critical Critical Critical Critical Major Critical Warning

56
2 Alarm List
Name RELAY_ALARM_MAJOR RELAY_ALARM_Minor REM_SD REM_SF REMOTE_FAULT RL_CRITICAL_HI RL_CRITICAL_LOW RS_CROSSTR RTC_FAIL
Description Major relay alarm Remote signal degraded Remote signal degraded Remote client-side service unloaded Remote fault Critical high return loss alarm Critical low return loss alarm Regenerator section performance over threshold RTC time fail alarm
Level Major Minor Minor Minor Minor Critical Critical Minor Major
2.1.18 Alarm List S

This section used a table to list the alarms starting with S. Name S1_SYN_CHANGE SCC_LOC SEC_RADIUS_FAIL SECU_ALM SERVICE_CAPACITY_E XCEED_LICENSE SERVICE_TYPE_EXCEE D_LICENSE SHELF_AREA_POWER_ OVER SLAVE_WORKING SM_BDI Description Synchronous source changed in S1 mode SCC loss of clock Excessive failures in radius authentication Security alarm The service capacity exceeds the license limit The service type exceeds the license limit Total optical power consumption of the subrack exceeds the threshold The protection board is working OTU SM section backward defect indication Level Major Critical Major Major Major Major Critical
Warning Major
Issue 02 (2011-10-31)
57
2 Alarm List
Name SM_BEI SM_BIP8_OVER
Description OTU layer, SM section backward error indication OTU layer, SM section bit interleaved parity exceeds threshold OTU layer, SM section bit interleaved parity deterioration OTU layer, SM section incoming alignment error OTU layer, SM Trail Trace Identifier (TTI) is mismatched The SNCP switching failure Span loss is excessively high Span loss is excessively low The number of timeslots bundled at the LCAS source is not consistent with the number of timeslots bundled at the LCAS sink Data rate exceeding the set limits Alarm storm The configured subrack does not match the physical subrack Inter-subrack communication protection switching alarm Conflict of subrack ID Mismatch of subrack ID Loop of subrack
Level Major Major
SM_BIP8_SD
Major
SM_IAE SM_TIM
Major Major
SNCP_FAIL SPAN_LOSS_HIGH SPAN_LOSS_LOW SO_SK_MISMATCH
Critical Major Major Critical
SPEED_OVER STORM_CUR_QUENUM_ OVER SUBRACK_TYPE_MISMATCH SUBRACK_COMM_PS
Major Minor Major
Major
SUBRACK_ID_CONFLICT SUBRACK_ID_MISMATCH SUBRACK_LOOP
Critical Major Critical
Issue 02 (2011-10-31)
58
2 Alarm List
Name SUM_INPWR_HI SUM_INPWR_LOW SW_SNCP_PS SW_SNCP_STA_INDI
Description Sum input optical power is too high Sum input optical power is excessively low SW SNCP protection switching The state of the SubWavelength SNCP protection group. Activation time out Automatic match inhibited Board excluded from software download during software package loading SCC board changed Commit failure NE is loading package Loss of file Board software cancelled during the loading of package Package version conformance check failed NE rollback failed A synchronization source degrade alarm Batch backup failed Difference between the SCC data and the CF card data The loss of synchronization source level Automatic synchronization of the system control board is disabled
Level Major Major Major Minor
SWDL_ACTIVATED_TIM EOUT SWDL_AUTOMATCH_IN H SWDL_BD_EXCLUDE
Critical Minor Major
SWDL_CHGMNG_NOMATCH SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKG_NOBDSOFT
Critical Minor Warning Critical Minor
SWDL_PKGVER_MM SWDL_ROLLBACK_FAIL SYN_BAD SYNC_FAIL SYSPARA_CFDB_NOSAME SYNC_C_LOS SYNC_DISABLE
Minor Minor Minor Minor Minor
Warning Minor
Issue 02 (2011-10-31)
59
2 Alarm List
Name SYNC_F_M_SWITCH
Description The forced or manual switching state of a clock source The clock source in the priority list is locked Difference between the SCC data and the CF card data The communication between an NE and the syslog server fails
Level Warning
SYNC_LOCKOFF SYSPARA_CFDB_NOSAME SYSLOG_COMM_FAIL
Warning Minor
Major
2.1.19 Alarm List T

This section used a table to list the alarms starting with T. Name T_LOSEX Description A board has detected the loss of signal in the service bus of the backplane Transmitted side frame slipping Transmitter degrade Laser temperature is too high Laser temperature is excessively low Working temperature over threshold The board is in the test status Transmission Failure Thunder protection circuit failure Time lock failure alarm The loss of the timing source level Level Major
T_SLIP TD TEM_HA TEM_LA TEMP_OVER TEST_STATUS TF THUNDERALM TIME_LOCK_FAIL TIME_LOS
Major Critical Major Major Major Warning Critical Minor Major Major
Issue 02 (2011-10-31)
60
2 Alarm List
Name TIME_NO_TRACE_MOD E TR_LOC TS_CFG_MISMATCH TU_AIS_VC3
Description The time enters the nontrace mode The clock of the crossconnect board is faulty The timeslot configuration mismatch alarm A TU alarm indication signal in the VC-3 lower order path An alarm indicating the loss of pointer in the VC-3 lower order path
Level Minor Major Major Major
TU_LOP_VC3
Major
2.1.20 Alarm List V

This section used a table to list the alarms starting with V. Name VCAT_LOA VCAT_LOM_VC3 Description Delay of multiframes exceeds the threshold The loss of the virtual concatenation multiframe in the VC-3 path The loss of the virtual concatenation multiframe in the VC-4 path VLAN SNCP switching Mismatch of attenuation attribute VOA adjustment failed Level Major Major
VCAT_LOM_VC4
Major
VLAN_SNCP_PS VOADATA_MIS VOA_ADJUST_FAIL
Major Major Major
2.1.21 Alarm List W

This section used a table to list the alarms starting with W. Name W_R_FAIL Description Writing or reading chip register failed
Level Major
Issue 02 (2011-10-31)
61
2 Alarm List
Name WAVE_ADD_ABN WAVE_DROP_ABN WAVEDATA_MIS WAVELEN_OVER WRG_BD_TYPE
Description APE detect wavelengths added APE detect wavelengths dropped Mismatch of wave or band attribute Wavelength over threshold Real board is mismatched with configured board
Level Warning Warning Major Major Major
2.1.22 Alarm List X

This section used a table to list the alarms starting with X. Name XC_UNSWITCH Description The cross-connect matrix of the board is not switched Level Major
2.2 Board Alarm List

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

BD_STATUS WRG_BD_TYPE
2.2.2 AUX Board Alarm List

TN11AUX BD_STATUS COMMUN_FAIL ETH_MISCONNECT HARD_BAD HARD_ERR LAN_LOC NO_BD_SOFT NO_ELABEL WRG_BD_TYPE
TN22AUX
2 Alarm List
BD_STATUS COMMUN_FAIL HARD_BAD
HARD_ERR RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE
RELAY_ALARM_MAJOR RELAY_ALARM_MINOR WRG_BD_TYPE
TN21AUX BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE RELAY_ALARM_MAJOR RELAY_ALARM_MINOR WRG_BD_TYPE
TN51AUX BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR WRG_BD_TYPE
TN16AUX BD_STATUS BOOTROM_BAD COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL POWER_FAIL SWDL_PKGVER_MM TEMP_OVER WRG_BD_TYPE
2.2.3 BMD4 Board Alarm List

BD_STATUS 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 OPA_FAIL_INDI WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
63
2 Alarm List
2.2.4 BMD8 Board Alarm List

BD_STATUS 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 OPA_FAIL_INDI WAVEDATA_MIS WRG_BD_TYPE
2.2.5 CMR1 Board Alarm List

BD_STATUS OPA_FAIL_INDI WAVEDATA_MIS WRG_BD_TYPE


2.2.8 CRPC Board Alarm List

AD_CHECK_FAIL BD_STATUS COMMUN_FAIL FAN_FAIL FPGA_ABN LASER_HAZARD_WARNING
Issue 02 (2011-10-31)
LOCK_CUR_FAIL LSR_WILL_DIE NO_BD_PARA NO_BD_SOFT OPA_FAIL_INDI OUT_PWR_HIGH
POWER_FAIL PUMP_COOL_EXC PUM_BCM_ALM RL_CRITICAL_HI RL_CRITICAL_LOW WRG_BD_TYPE
64
2 Alarm List
LOCKPOW_MIS
OUT_PWR_LOW
W_R_FAIL
2.2.9 D40V Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_TEMP_OVER MOD_COM_FAIL MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
2.2.10 D40 Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULE_COOLCUR_OV ER MODULE_TEMP_OVER MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
2.2.11 DAS1 Board Alarm List

BD_STATUS BEFFEC_EXC
Issue 02 (2011-10-31)
OA_LOW_GAIN OPA_FAIL_INDI
PUMP_COOL_EXC PUM_BCM_ALM
65
2 Alarm List
COMMUN_FAIL GAINDATA_MIS HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_HAZARD_WARNING LASER_MODULE_MISMATCH LOOP_ALM LSR_WILL_DIE MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL
OSC_BDI OSC_DEG OSC_LOS OTS_BDI OTS_BDI_O OTS_BDI_P OTS_LOS OTS_LOS_O OTS_LOS_P OTS_TIM OOS_LOST OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE
PUM_TEM_ALM R_LOF SCC_LOC SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TD TEMP_OVER TF VOADATA_MIS VOA_ADJUST_FAIL WAVEDATA_MIS WRG_BD_TYPE
2.2.12 DCU Board Alarm List

BD_STATUS OPA_FAIL_INDI WRG_BD_TYPE
2.2.13 DCP Board Alarm List

TN11DCP BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI COMMUN_FAIL HARD_BAD HARD_ERR INTRA_OTU_PS
Issue 02 (2011-10-31)
NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI
OCh_SSF_P OPA_FAIL_INDI OWSP_PS OWSP_STA_INDI POWER_DIFF_OVER R_LOS TEMP_OVER

66
2 Alarm List
INTRA_OTU_STA_INDI NO_BD_PARA
OCh_SSF OCh_SSF_O
WRG_BD_TYPE
TN12DCP BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI COMMUN_FAIL HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI 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 OPA_FAIL_INDI OWSP_PS OWSP_STA_INDI POWER_DIFF_OVER R_LOS TEMP_OVER WRG_BD_TYPE
2.2.14 DFIU Board Alarm List

BD_STATUS MUT_LOS OOS_LOST OPA_FAIL_INDI OTS_BDI OTS_BDI-O OTS_BDI-P OTS_LOS OTS_LOS-O OTS_LOS-P OTS_TIM WAVEDATA_MIS WRG_BD_TYPE
2.2.15 DMR1 Board Alarm List

Issue 02 (2011-10-31)
67
2 Alarm List
2.2.16 EAS2 Board Alarm List

ALM_GFP_dCSF ALM_GFP_dLFD AU_AIS AU_LOP B3_EXC_VC3 B3_EXC_VC4 B3_SD_VC3 B3_SD_VC4 BDID_ERROR BD_STATUS BOOTROM_BAD CHIP_ABN COMMUN_FAIL DLAG_PROTECT_FAIL ETHOAM_DISCOVER_FAIL ETHOAM_RMT_CRIT_FAULT ETHOAM_RMT_LOOP ETHOAM_RMT_SD ETHOAM_SELF_LOOP ETHOAM_VCG_SELF_LOOP ETH_CFM_LOC ETH_CFM_MACSTATUS ETH_CFM_MISMERGE ETH_CFM_RDI ETH_CFM_UNEXPERI EX_ETHOAM_CC_LOS EX_ETHOAM_MPID_C NFLCT FCS_ERR FLOW_OVER HARD_BAD HARD_ERR HP_RDI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW LAG_PORT_FAIL LAG_VC_PORT_FAIL LASER_MODULE_MIS MATCH LCAS_FOPR LCAS_FOPT LCAS_PLCR LCAS_PLCT LCAS_TLCR LCAS_TLCT LINK_ERR LOOP_ALM LPT_RFI LP_RDI_VC3 LP_SLM_VC3 LP_UNEQ_VC3 LSR_INVALID LSR_NO_FITED LSR_WILL_DIE MULTI_RPL_OWNER NO_BD_SOFT NO_ELABEL OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOS SLAVE_WORKING SO_SK_MISMATCH TD TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC TU_AIS_VC3 TU_LOP_VC3 T_LOSEX VCAT_LOA VCAT_LOM_VC3 VCAT_LOM_VC4 WRG_BD_TYPE
Issue 02 (2011-10-31)
68
2 Alarm List
2.2.17 ECOM Board Alarm List

BD_STATUS HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOS TD TEM_HA TEM_LA TEMP_OVER TF WAVEDATA_MIS WRG_BD_TYPE
2.2.18 EFI Board Alarm List

TN11EFI BD_STATUS ETH_MISCONNECT LAN_LOC RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE RELAY_ALARM_MAJOR RELAY_ALARM_MINOR WRG_BD_TYPE
TN61EFI BD_STATUS ETH_MISCONNECT LAN_LOC RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE RELAY_ALARM_MAJOR RELAY_ALARM_MINOR WRG_BD_TYPE
2.2.19 EFI1 Board Alarm List

BD_STATUS HARD_BAD LAN_LOC RELAY_ALARM_CRITICAL RELAY_ALARM_IGNORE RELAY_ALARM_MAJOR RELAY_ALARM_MINOR WRG_BD_TYPE
Issue 02 (2011-10-31)
69
2 Alarm List
2.2.20 EFI2 Board Alarm List

BD_STATUS ETH_MISCONNECT HARD_BAD WRG_BD_TYPE LAN_LOC
2.2.21 EGSH Board Alarm List

ALM_GFP_dCSF ALM_GFP_dLFD AU_AIS AU_LOP B3_EXC_VC3 B3_EXC_VC4 B3_SD_VC3 B3_SD_VC4 BDID_ERROR BD_STATUS BOOTROM_BAD CHIP_ABN COMMUN_FAIL DLAG_PROTECT_FAIL ETHOAM_DISCOVER_FA IL ETHOAM_RMT_CRIT_FA ULT ETHOAM_RMT_LOOP ETHOAM_RMT_SD ETHOAM_SELF_LOOP ETHOAM_VCG_SELF_LO OP ETH_CFM_LOC EX_ETHOAM_CC_LOS EX_ETHOAM_MPID_CNFL CT FCS_ERR HARD_BAD HARD_ERR HP_RDI HP_SLM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW LAG_PORT_FAIL LASER_MODULE_MISMATCH LCAS_FOPR LCAS_FOPT LCAS_PLCR LCAS_PLCT LCAS_TLCR LCAS_TLCT LINK_ERR LOOP_ALM LPT_RFI LSR_WILL_DIE MULTI_RPL_OWNER NO_BD_SOFT NO_ELABEL OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOS SLAVE_WORKING SO_SK_MISMATCH TD TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC TU_AIS_VC3 TU_LOP_VC3 T_LOSEX VCAT_LOA
Issue 02 (2011-10-31)
70
2 Alarm List
ETH_CFM_MACSTATUS ETH_CFM_MISMERGE ETH_CFM_RDI ETH_CFM_UNEXPERI
LP_RDI_VC3 LP_SLM_VC3 LP_UNEQ_VC3 LSR_INVALID
VCAT_LOM_VC3 VCAT_LOM_VC4 WRG_BD_TYPE
2.2.22 ELQX Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC
Issue 02 (2011-10-31)
71
2 Alarm List
NULL_SEND ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC
ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK
ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF
Issue 02 (2011-10-31)
72
2 Alarm List
ODU1_TCM3_OCI ODU1_TCM3_SSF
ODU2_TCM3_LTC ODU2_TCM3_OCI
WAVEDATA_MIS WRG_BD_TYPE
2.2.23 ENQ2 Board Alarm List

TN54ENQ2(STND) BD_STATUS BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR NO_ELABEL TEMP_OVER WRG_BD_TYPE
TN54ENQ2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR LOOP_ALM NO_BD_SOFT NO_ELABEL NULL_SEND ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS
Issue 02 (2011-10-31)
ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG
ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC
73
2 Alarm List
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF
ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS
ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM PRBS_LSS TEMP_OVER WRG_BD_TYPE
Issue 02 (2011-10-31)
74
2 Alarm List
2.2.24 FAN Board Alarm List

TN11FAN/TN21FAN/TN51FAN BD_STATUS FAN_FAIL FAN_FAULT WRG_BD_TYPE
TN16FAN BD_STATUS FAN_FAIL FAN_FAULT HARD_ERR WRG_BD_TYPE
2.2.25 FIU Board Alarm List

TN13FIU BD_STATUS MUT_LOS OOS_LOST OPA_FAIL_INDI OTS_BDI OTS_BDI-O OTS_BDI-P OTS_LOS OTS_LOS-O OTS_LOS-P OTS_TIM WAVEDATA_MIS WRG_BD_TYPE
TN12FIU BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MUT_LOS OOS_LOST OPA_FAIL_INDI OTS_BDI OTS_BDI-O OTS_BDI-P OTS_LOS OTS_LOS-O OTS_LOS-P OTS_TIM SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
TN11FIU BD_STATUS COMMUN_FAIL

Issue 02 (2011-10-31)
OOS_LOST OPA_FAIL_INDI
OTS_TIM SUM_INPWR_HI
75
2 Alarm List
HARD_BAD HARD_ERR MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL
OTS_BDI OTS_BDI-O OTS_BDI-P OTS_LOS OTS_LOS-O OTS_LOS-P
SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
TN21FIU BD_STATUS MUT_LOS OOS_LOST OPA_FAIL_INDI OTS_BDI OTS_BDI-O OTS_BDI-P OTS_LOS OTS_LOS-O OTS_LOS-P OTS_TIM WAVEDATA_MIS WRG_BD_TYPE
2.2.26 GFU Board Alarm List

BD_STATUS COMMUN_FAIL OPA_FAIL_INDI WRG_BD_TYPE
2.2.27 HBA Board Alarm List

BD_STATUS COMMUN_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_W ARNING MODULEFILE_UPDATE_FAI L MUT_LOS OA_LOW_GAIN OPA_FAIL_INDI SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
76
2 Alarm List
2.2.28 HSC1 Board Alarm List

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

TN11ITL BD_STATUS 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 OPA_FAIL_INDI WAVEDATA_MIS WRG_BD_TYPE
TN12ITL BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR 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 OPA_FAIL_INDI TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
77
2 Alarm List
2.2.30 L4G Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LAG_PORT_FAIL LAG_VC_PORT_FAIL LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MS_AIS MS_RDI MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL
Issue 02 (2011-10-31)
ODU5G_PM_OCI ODU5G_PM_SSF ODU5G_PM_TIM ODU5G_TCM1_AIS ODU5G_TCM1_BDI ODU5G_TCM1_DEG ODU5G_TCM1_EXC ODU5G_TCM1_LCK ODU5G_TCM1_LTC ODU5G_TCM1_OCI ODU5G_TCM1_SSF ODU5G_TCM1_TIM ODU5G_TCM2_AIS ODU5G_TCM2_BDI ODU5G_TCM2_DEG ODU5G_TCM2_EXC ODU5G_TCM2_LCK ODU5G_TCM2_LTC ODU5G_TCM2_OCI ODU5G_TCM2_SSF ODU5G_TCM2_TIM ODU5G_TCM3_AIS ODU5G_TCM3_BDI ODU5G_TCM3_DEG ODU5G_TCM3_EXC ODU5G_TCM3_LCK ODU5G_TCM3_LTC ODU5G_TCM3_OCI ODU5G_TCM3_SSF
ODU5G_TCM5_LCK ODU5G_TCM5_LTC ODU5G_TCM5_OCI ODU5G_TCM5_SSF ODU5G_TCM5_TIM ODU5G_TCM6_AIS ODU5G_TCM6_BDI ODU5G_TCM6_DEG ODU5G_TCM6_EXC ODU5G_TCM6_LCK ODU5G_TCM6_LTC ODU5G_TCM6_OCI ODU5G_TCM6_SSF ODU5G_TCM6_TIM OPA_FAIL_INDI OPU5G_PLM OTU5G_AIS OTU5G_BDI OTU5G_DEG OTU5G_EXC OTU5G_LOF OTU5G_LOM OTU5G_SSF OTU5G_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE REM_SD REM_SF
78
2 Alarm List
OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU5G_LOFLOM ODU5G_PM_AIS ODU5G_PM_BDI ODU5G_PM_DEG ODU5G_PM_EXC ODU5G_PM_LCK
ODU5G_TCM3_TIM ODU5G_TCM4_AIS ODU5G_TCM4_BDI ODU5G_TCM4_DEG ODU5G_TCM4_EXC ODU5G_TCM4_LCK ODU5G_TCM4_LTC ODU5G_TCM4_OCI ODU5G_TCM4_SSF ODU5G_TCM4_TIM ODU5G_TCM5_AIS ODU5G_TCM5_BDI ODU5G_TCM5_DEG ODU5G_TCM5_EXC
R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF VLAN_SNCP_PS WAVEDATA_MIS WRG_BD_TYPE
2.2.31 LDGD Board Alarm List

B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR INTRA_OTU_PS ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI
Issue 02 (2011-10-31)
79
2 Alarm List
INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MS_AIS MS_CROSSTR MS_RDI MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI
ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI
ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
80
2 Alarm List
2.2.32 LDGS Board Alarm List

B1_EXC B1_SD B2_EXC B2_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MS_AIS MS_CROSSTR MS_RDI ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE
Issue 02 (2011-10-31)
81
2 Alarm List
MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC
ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC
REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.33 LDM Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI
Issue 02 (2011-10-31)
82
2 Alarm List
INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC
ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG
ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS
Issue 02 (2011-10-31)
83
2 Alarm List
ODU1_PM_LCK ODU1_PM_OCI
ODU1_TCM5_EXC ODU1_TCM5_LCK
WRG_BD_TYPE
2.2.34 LDMD Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW
Issue 02 (2011-10-31)
84
2 Alarm List
MS_AIS NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK
ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC
PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
2.2.35 LDMS Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC
Issue 02 (2011-10-31)
85
2 Alarm List
HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG
ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS
ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD TEMP_OVER TEM_HA TEM_LA TF
Issue 02 (2011-10-31)
86
2 Alarm List
ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI
ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC
TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
2.2.36 LDX Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS
Issue 02 (2011-10-31)
87
2 Alarm List
OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF
ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC
REMOTE_FAULT REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.37 LEM24 Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL DBPS_ABNORMAL ETHOAM_DISCOVER_FAIL ETHOAM_RMT_CRIT_FAU LT ETHOAM_RMT_LOOP NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC
Issue 02 (2011-10-31)
88
2 Alarm List
ETHOAM_RMT_SD ETHOAM_SELF_LOOP ETHOAM_VCG_SELF_LOO P ETH_CFM_LOC ETH_CFM_MACSTATUS ETH_CFM_MISMERGE ETH_CFM_RDI ETH_CFM_UNEXPERI ETH_SERVICE_CONFIG_F AIL EX_ETHOAM_CC_LOS EX_ETHOAM_MPID_CNFL CT FLOW_OVER FWD_PKT_LOSS HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LAG_PORT_FAIL LAG_VC_PORT_FAIL LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE
ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF
ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF VLAN_SNCP_PS WRG_BD_TYPE
Issue 02 (2011-10-31)
89
2 Alarm List
MULTI_RPL_OWNER
ODU2_TCM4_TIM
WAVEDATA_MIS
2.2.38 LEX4 Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL DBPS_ABNORMAL ETHOAM_DISCOVER_FAIL ETHOAM_RMT_CRIT_FAU LT ETHOAM_RMT_LOOP ETHOAM_RMT_SD ETHOAM_SELF_LOOP ETHOAM_VCG_SELF_LOO P ETH_CFM_LOC ETH_CFM_MACSTATUS ETH_CFM_MISMERGE ETH_CFM_RDI ETH_CFM_UNEXPERI ETH_SERVICE_CONFIG_F AIL EX_ETHOAM_CC_LOS EX_ETHOAM_MPID_CNFL CT FLOW_OVER
Issue 02 (2011-10-31)
NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF
ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM
90
2 Alarm List
FWD_PKT_LOSS HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LAG_PORT_FAIL LAG_VC_PORT_FAIL LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MULTI_RPL_OWNER
ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM
OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF VLAN_SNCP_PS WRG_BD_TYPE WAVEDATA_MIS
2.2.39 LOA Board Alarm List

ALS_ACTIVE B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL
Issue 02 (2011-10-31)
ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM
ODUFLEX_PM_TIM OPA_FAIL_INDI OPU0_PLM OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU1_AIS OTU1_BDI

91
2 Alarm List
HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MIS MATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI
ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODUFLEX_LOFLOM ODUFLEX_PLM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_LCK ODUFLEX_PM_OCI
OTU1_DEG OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
92
2 Alarm List
ODU0_PM_SSF
ODUFLEX_PM_SSF
2.2.40 LOG Board Alarm List

TN12LOG BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS
Issue 02 (2011-10-31)
93
2 Alarm List
OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI
ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK
REM_SD REM_SF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN11LOG BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM
Issue 02 (2011-10-31)
94
2 Alarm List
LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK
ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG
OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.41 LOM Board Alarm List

BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM
Issue 02 (2011-10-31)
95
2 Alarm List
CLIENT_PROT_NOTSTART COMMUN_FAIL FC_8B10BERR_OVER FC_LINK_ERR FC_SYNC_LOS HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS
ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM
ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOC R_LOS REM_SD REM_SF TD TEMP_OVER TEM_HA TEM_LA
Issue 02 (2011-10-31)
96
2 Alarm List
ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI
ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK
TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
2.2.42 LQG Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC ODU5G_PM_OCI ODU5G_PM_SSF ODU5G_PM_TIM ODU5G_TCM1_AIS ODU5G_TCM1_BDI ODU5G_TCM1_DEG ODU5G_TCM1_EXC ODU5G_TCM1_LCK ODU5G_TCM1_LTC ODU5G_TCM1_OCI ODU5G_TCM1_SSF ODU5G_TCM1_TIM ODU5G_TCM2_AIS ODU5G_TCM2_BDI ODU5G_TCM2_DEG ODU5G_TCM2_EXC ODU5G_TCM2_LCK ODU5G_TCM2_LTC ODU5G_TCM2_OCI ODU5G_TCM2_SSF ODU5G_TCM2_TIM ODU5G_TCM3_AIS ODU5G_TCM3_BDI ODU5G_TCM5_LTC ODU5G_TCM5_OCI ODU5G_TCM5_SSF ODU5G_TCM5_TIM ODU5G_TCM6_AIS ODU5G_TCM6_BDI ODU5G_TCM6_DEG ODU5G_TCM6_EXC ODU5G_TCM6_LCK ODU5G_TCM6_LTC ODU5G_TCM6_OCI ODU5G_TCM6_SSF ODU5G_TCM6_TIM OPA_FAIL_INDI OPU5G_PLM OTU5G_AIS OTU5G_BDI OTU5G_DEG OTU5G_EXC OTU5G_LOF OTU5G_LOM OTU5G_SSF OTU5G_TIM
Issue 02 (2011-10-31)
97
2 Alarm List
MS_AIS MS_RDI MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU5G_LOFLOM ODU5G_PM_AIS ODU5G_PM_BDI ODU5G_PM_DEG ODU5G_PM_EXC ODU5G_PM_LCK
ODU5G_TCM3_DEG ODU5G_TCM3_EXC ODU5G_TCM3_LCK ODU5G_TCM3_LTC ODU5G_TCM3_OCI ODU5G_TCM3_SSF ODU5G_TCM3_TIM ODU5G_TCM4_AIS ODU5G_TCM4_BDI ODU5G_TCM4_DEG ODU5G_TCM4_EXC ODU5G_TCM4_LCK ODU5G_TCM4_LTC ODU5G_TCM4_OCI ODU5G_TCM4_SSF ODU5G_TCM4_TIM ODU5G_TCM5_AIS ODU5G_TCM5_BDI ODU5G_TCM5_DEG ODU5G_TCM5_EXC ODU5G_TCM5_LCK
OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.43 LQMD Board Alarm List

TN12LQMD B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS
Issue 02 (2011-10-31)
ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI
ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI

98
2 Alarm List
CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P
ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK
ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER SW_SNCP_PS SW_SNCP_STA_INDI
Issue 02 (2011-10-31)
99
2 Alarm List
OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC
ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK
TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
TN11LQMD B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC
Issue 02 (2011-10-31)
100
2 Alarm List
LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC
ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK
OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
2.2.44 LQMS Board Alarm List

TN12LQMS B1_EXC
Issue 02 (2011-10-31)
ODU1_PM_SSF
ODU1_TCM5_SSF
101
2 Alarm List
B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI
ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI
ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC
Issue 02 (2011-10-31)
102
2 Alarm List
OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI
ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI
R_LOF R_LOS SPEED_OVER SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
TN11LQMS B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI
Issue 02 (2011-10-31)
103
2 Alarm List
J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK
ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK
OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
104
2 Alarm List
2.2.45 LQM Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD
Issue 02 (2011-10-31)
105
2 Alarm List
MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK
ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC
REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
2.2.46 LSQ Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL DCM_INSUFF ODU3_TCM1_EXC ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_EXC ODU3_TCM6_LCK ODU3_TCM6_LTC
Issue 02 (2011-10-31)
106
2 Alarm List
HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_EXC ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG
ODU3_TCM2_EXC ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_EXC ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_EXC ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG ODU3_TCM5_EXC ODU3_TCM5_LCK ODU3_TCM5_LTC
ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM OPA_FAIL_INDI OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_EXC OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOC R_LOF R_LOS REM_SD REM_SF TD TEMP_OVER TF WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
107
2 Alarm List
2.2.47 LSXLR Board Alarm List

TN11LSXLR BD_STATUS BEFFEC_EXC COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM OPA_FAIL_INDI OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS
Issue 02 (2011-10-31)
108
2 Alarm List
ODU3_TCM1_DEG ODU3_TCM1_LCK ODU3_TCM1_LTC
ODU3_TCM5_DEG ODU3_TCM5_LCK ODU3_TCM5_LTC
WRG_BD_TYPE
TN12LSXLR BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM5_LTC ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM OPA_FAIL_INDI OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE
Issue 02 (2011-10-31)
109
2 Alarm List
ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG ODU3_TCM1_LCK
ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG ODU3_TCM5_LCK
R_LOS TD TEMP_OVER TF WAVEDATA_MIS WRG_BD_TYPE
2.2.48 LSXL Board Alarm List

TN11LSXL B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OCh_FDI
Issue 02 (2011-10-31)
ODU3_TCM1_DEG ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI
ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM OPA_FAIL_INDI OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH
110
2 Alarm List
OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_TCM1_AIS ODU3_TCM1_BDI
ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG ODU3_TCM5_LCK ODU3_TCM5_LTC ODU3_TCM5_OCI
OUT_PWR_LOW PORT_MODULE_OFFLINE REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN12LSXL B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL DCM_INSUFF HARD_BAD ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM5_LTC ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF
Issue 02 (2011-10-31)
111
2 Alarm List
HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM
ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG ODU3_TCM5_LCK
ODU3_TCM6_TIM OPA_FAIL_INDI OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF R_LOF R_LOS R_OOF TD TEMP_OVER TF WAVEDATA_MIS WRG_BD_TYPE
NOTE
In the alarms, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to TCM6.
Issue 02 (2011-10-31)
112
2 Alarm List
2.2.49 LSXR Board Alarm List

BD_STATUS BEFFEC_EXC COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS
Issue 02 (2011-10-31)
113
2 Alarm List
ODU2_TCM1_LTC
ODU2_TCM5_LCK
WRG_BD_TYPE
2.2.50 LSX Board Alarm List

TN11LSX B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT
Issue 02 (2011-10-31)
114
2 Alarm List
OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF
ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC
REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN12LSX B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG
Issue 02 (2011-10-31)
115
2 Alarm List
LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF
ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI
OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN13LSX B1_EXC B1_SD BD_STATUS BEFFEC_EXC ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI
Issue 02 (2011-10-31)
116
2 Alarm List
CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_PM_AIS
ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS
ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA
Issue 02 (2011-10-31)
117
2 Alarm List
ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF
ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI
TF WAVEDATA_MIS WRG_BD_TYPE
2.2.51 LWX2 Board Alarm List

B1_EXC B1_SD BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MODULEFILE_UPDATE_ FAIL NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P OPA_FAIL_INDI OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.52 LWXD Board Alarm List

B1_EXC B1_SD LSR_COOL_ALM LSR_FORCE_OPEN OUT_PWR_HIGH OUT_PWR_LOW
Issue 02 (2011-10-31)
118
2 Alarm List
BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM
LSR_INVALID LSR_WILL_DIE MODULEFILE_UPDATE_ FAIL NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P OPA_FAIL_INDI
PORT_MODULE_OFFLINE RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.53 LWXS Board Alarm List

TN11LWXS B1_EXC B1_SD BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MODULEFILE_UPDATE_ FAIL NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD
Issue 02 (2011-10-31)
119
2 Alarm List
IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM LSR_COOL_ALM
OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P OPA_FAIL_INDI
TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN12LWXS B1_EXC B1_SD BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM LSR_COOL_ALM LSR_FORCE_OPEN LSR_WILL_DIE MODULEFILE_UPDATE_ FAIL NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P OPA_FAIL_INDI OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.54 M40V Board Alarm List

TN12M40V BD_STATUS
Issue 02 (2011-10-31)
MODULE_TEMP_OVER
OPA_FAIL_INDI
120
2 Alarm List
COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDAT E_FAIL
MOD_COM_FAIL NO_BD_PARA NO_BD_SOFT NO_ELABEL
TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
TN11M40V BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MOD_COM_FAIL MODULE_TEMP_OVER MODULEFILE_UPDATE_F AIL NO_BD_PARA NO_BD_SOFT NO_ELABEL OPA_FAIL_INDI TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
2.2.55 M40 Board Alarm List

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

APE_ADJUST_FAIL APE_ADJUST_PEND BD_STATUS CHAN_ADD CHAN_LOS COMMUN_FAIL HARD_ERR MODULEFILE_UPDATE_FAI L MOD_COM_FAIL NO_BD_PARA NO_BD_SOFT NO_ELABEL TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE WAVE_ADD_ABN WAVE_DROP_ABN
Issue 02 (2011-10-31)
121
2 Alarm List
HARD_BAD
PORTSWITCH_FAIL
2.2.57 MCA8 Board Alarm List

APE_ADJUST_FAIL APE_ADJUST_PEND BD_STATUS CHAN_ADD CHAN_LOS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_FAI L MOD_COM_FAIL NO_BD_PARA NO_BD_SOFT NO_ELABEL PORTSWITCH_FAIL TEMP_OVER WAVE_ADD_ABN WAVE_DROP_ABN WAVEDATA_MIS WRG_BD_TYPE
2.2.58 MR2 Board Alarm List

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

Issue 02 (2011-10-31)
122
2 Alarm List

2.2.61 MR8V Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR OMS_BDI OMS_BDI_O OMS_BDI_P OMS_FDI OMS_FDI_O OMS_FDI_P OMS_SSF OMS_SSF_O OMS_SSF_P OPA_FAIL_INDI TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
2.2.62 ND2 Board Alarm List

TN53ND2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MIS MATCH LOOP_ALM LSR_WILL_DIE ODU0_TCMn_OCI ODU0_TCMn_SSF ODU0_TCMn_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF ODUFLEX_PM_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI
Issue 02 (2011-10-31)
123
2 Alarm List
NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU0_TCMn_AIS ODU0_TCMn_BDI ODU0_TCMn_DEG ODU0_TCMn_LCK ODU0_TCMn_LTC
ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODUFLEX_LOFLOM
OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN53ND2(COMP) BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU2_TCMn_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS
Issue 02 (2011-10-31)
124
2 Alarm List
HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM
ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF
ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN52ND2 BD_STATUS ODU1_TCM3_LCK ODU2_TCM3_LTC
Issue 02 (2011-10-31)
125
2 Alarm List
BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS
ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI
ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI
Issue 02 (2011-10-31)
126
2 Alarm List
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG
ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK
NOTE
2.2.63 NPO2 Board Alarm List

TN55NPO2(STND)
2 Alarm List
BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL EXT_MODULE_OFFLINE HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW IPA_SHUT LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE MAINBD_SUBBD_MISMATCH MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL NULL_SEND ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM
ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN55NPO2
2 Alarm List
BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL EXT_MODULE_OFFLINE HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW IPA_SHUT LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE MAINBD_SUBBD_MISMATCH MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI
ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF
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 OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA
Issue 02 (2011-10-31)
129
2 Alarm List
ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM
ODU2_TCMn_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI
TN54NPO2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE MAINBD_SUBBD_MISMATCH MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF
Issue 02 (2011-10-31)
130
2 Alarm List
OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI
ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM
ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI 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 OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE
Issue 02 (2011-10-31)
131
2 Alarm List
ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG
ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS
PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.64 NPO2E Board Alarm List

TN55NPO2E BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL EXT_MODULE_OFFLINE HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW IPA_SHUT LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE MAINBD_SUBBD_MISMATCH MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL
Issue 02 (2011-10-31)
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK
ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW
132
2 Alarm List
NULL_SEND ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS
ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM
PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.65 NQ2 Board Alarm List

TN53NQ2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MIS MATCH LOOP_ALM LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O
Issue 02 (2011-10-31)
ODU0_TCMn_OCI ODU0_TCMn_SSF ODU0_TCMn_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC
ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF ODUFLEX_PM_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM
133
2 Alarm List
OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU0_TCMn_AIS ODU0_TCMn_BDI ODU0_TCMn_DEG ODU0_TCMn_LCK ODU0_TCMn_LTC
ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODUFLEX_LOFLOM
OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN53NQ2(COMP) BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU2_TCMn_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM
Issue 02 (2011-10-31)
134
2 Alarm List
LOOP_ALM LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM
ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF
OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN54NQ2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG
Issue 02 (2011-10-31)
135
2 Alarm List
IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI
ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM
ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM
Issue 02 (2011-10-31)
136
2 Alarm List
ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI
ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK
TN52NQ2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK
Issue 02 (2011-10-31)
137
2 Alarm List
LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF
ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS
ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS
Issue 02 (2011-10-31)
138
2 Alarm List
ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI
ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK
OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN51NQ2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC
Issue 02 (2011-10-31)
139
2 Alarm List
LASER_MODULE_MISMATCH LOOP_ALM LSR_COOL_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI
ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC
ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF
Issue 02 (2011-10-31)
140
2 Alarm List
ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC
OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.66 NS2 Board Alarm List

TN53NS2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MIS MATCH LOOP_ALM ODU0_TCMn_OCI ODU0_TCMn_SSF ODU0_TCMn_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF ODUFLEX_PM_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS
Issue 02 (2011-10-31)
141
2 Alarm List
LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU0_TCMn_AIS ODU0_TCMn_BDI ODU0_TCMn_DEG ODU0_TCMn_LCK ODU0_TCMn_LTC
ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODUFLEX_LOFLOM
ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN53NS2(COMP) BD_STATUS BEFFEC_EXC BUS_ERR ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU2_TCMn_TIM ODUKSP_PS ODUKSP_STA_INDI
Issue 02 (2011-10-31)
142
2 Alarm List
COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM
ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF
ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN52NS2
Issue 02 (2011-10-31)
143
2 Alarm List
BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM
ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI
Issue 02 (2011-10-31)
144
2 Alarm List
ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG
ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC
TN12NS2 BD_STATUS BEFFEC_EXC ODU1_TCM4_AIS ODU1_TCM4_BDI ODU2_TCM3_TIM ODU2_TCM4_AIS
Issue 02 (2011-10-31)
145
2 Alarm List
BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG
ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI
ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_PLM OPU2_MSIM OPU2_PLM
Issue 02 (2011-10-31)
146
2 Alarm List
ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM
ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF
TN11NS2 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC
Issue 02 (2011-10-31)
147
2 Alarm List
IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM
ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI
ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_PLM OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF
Issue 02 (2011-10-31)
148
2 Alarm List
ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM
OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.67 NS3 Board Alarm List

TN54NS3 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG ODU3_TCM1_EXC ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI
Issue 02 (2011-10-31)
149
2 Alarm List
LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_EXC ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS
ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_EXC ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_EXC ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_EXC ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG
ODU3_TCM2_DEG ODU3_TCM2_EXC ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_EXC ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_EXC ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG ODU3_TCM5_EXC ODU3_TCM5_LCK ODU3_TCM5_LTC
Issue 02 (2011-10-31)
150
2 Alarm List
ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK
ODU2_TCM3_EXC ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_EXC ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_EXC ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_EXC ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI
ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_EXC ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM ODUKSP_PS ODUKSP_STA_INDI ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_EXC OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW
Issue 02 (2011-10-31)
151
2 Alarm List
ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC
ODU2_TCM6_SSF ODU2_TCM6_TIM ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_EXC ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM
PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WRG_BD_TYPE
TN52NS3 BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC
Issue 02 (2011-10-31)
152
2 Alarm List
OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI
ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF
Issue 02 (2011-10-31)
153
2 Alarm List
ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI
ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODU3_PM_AIS ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_EXC ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG
OPA_FAIL_INDI OPU1_MSIM OPU1_PLM OPU2_MSIM OPU2_PLM OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_EXC OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN11NS3
Issue 02 (2011-10-31)
154
2 Alarm List
BD_STATUS BEFFEC_EXC BUS_ERR COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU3_PM_AIS
ODU3_PM_TIM ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_LCK ODU3_TCM4_LTC ODU3_TCM4_OCI
ODU3_TCM5_LCK ODU3_TCM5_LTC ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM6_AIS ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU2_PLM OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOS TD
Issue 02 (2011-10-31)
155
2 Alarm List
ODU3_PM_BDI ODU3_PM_DEG ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF
ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG
TEMP_OVER TF WAVEDATA_MIS WRG_BD_TYPE
NOTE
2.2.68 OAU1 Board Alarm List

TN13OAU1 BD_STATUS COMMUN_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WA RNING MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOA_ADJUST_FAIL WRG_BD_TYPE
TN12OAU1 BD_STATUS COMMUN_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WARNING MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOA_ADJUST_FAIL WRG_BD_TYPE
Issue 02 (2011-10-31)
156
2 Alarm List
TN11OAU1 BD_STATUS COMMUN_FAIL DSP_LOAD_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WARNING MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOA_ADJUST_FAIL WRG_BD_TYPE
2.2.69 OBU1 Board Alarm List

TN12OBU1 BD_STATUS COMMUN_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WARNING MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WRG_BD_TYPE
TN11OBU1 BD_STATUS COMMUN_FAIL DSP_LOAD_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WARNING NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WRG_BD_TYPE
Issue 02 (2011-10-31)
157
2 Alarm List
MUT_LOS
PUM_TEM_ALM
2.2.70 OBU2 Board Alarm List

TN12OBU2 BD_STATUS COMMUN_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WARNING MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WRG_BD_TYPE
TN11OBU2 BD_STATUS COMMUN_FAIL DSP_LOAD_FAIL GAINDATA_MIS HARD_BAD HARD_ERR LASER_HAZARD_WARNING MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OA_LOW_GAIN OPA_FAIL_INDI PUMP_COOL_EXC PUM_BCM_ALM PUM_TEM_ALM SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WRG_BD_TYPE
2.2.71 OLP Board Alarm List

TN11OLP BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI NO_BD_PARA NO_BD_SOFT NO_ELABEL OLP_PS OCh_SSF_O OCh_SSF_P
Issue 02 (2011-10-31)
158
2 Alarm List
COMMUN_FAIL HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI MUT_LOS
OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF
OLP_STA_INDI OPA_FAIL_INDI POWER_DIFF_OVER R_LOS TEMP_OVER WRG_BD_TYPE
TN12OLP BD_STATUS CLIENT_PORT_PS CLIENT_PORT_STA_INDI COMMUN_FAIL HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI MUT_LOS NO_BD_PARA OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P OLP_PS OLP_STA_INDI OPA_FAIL_INDI POWER_DIFF_OVER R_LOS TEMP_OVER WRG_BD_TYPE
2.2.72 OPM8 Board Alarm List

APE_ADJUST_FAIL APE_ADJUST_PEND BD_STATUS CHAN_ADD CHAN_LOS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_FAI L MOD_COM_FAIL NO_BD_PARA NO_BD_SOFT NO_ELABEL PORTSWITCH_FAIL TEMP_OVER WRG_BD_TYPE WAVE_ADD_ABN WAVE_DROP_ABN
Issue 02 (2011-10-31)
159
2 Alarm List
2.2.73 PIU Board Alarm List

BD_STATUS POWER_FAIL THUNDERALM WRG_BD_TYPE
2.2.74 PTQX Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MUT_LOS NO_BD_PARA NO_BD_SOFT ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI
Issue 02 (2011-10-31)
160
2 Alarm List
NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK
ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI
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 OPA_FAIL_INDI OPU2_MSIM OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF R_LOC R_LOF R_LOS
Issue 02 (2011-10-31)
161
2 Alarm List
ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK
ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI
TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE MAINBD_SUBBD_MISMATCH
2.2.75 RDU9 Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
2.2.76 RMU9 Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULE_TEMP_OVE R MUT_LOS NO_BD_PARA OMS_BDI OMS_BDI_O OMS_BDI_P OMS_FDI OMS_FDI_O OMS_FDI_P OMS_LOS_P OMS_SSF_P OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS
Issue 02 (2011-10-31)
162
2 Alarm List
NO_BD_SOFT NO_ELABEL
OMS_SSF OMS_SSF_O
WRG_BD_TYPE
2.2.77 ROAM Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS NO_BD_SOFT NO_ELABEL 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER WAVEDATA_MIS WRG_BD_TYPE
2.2.78 SBM2 Board Alarm List

2.2.79 SC1 Board Alarm List

ALM_HANGUP BD_STATUS COMMUN_FAIL CRC4_CROSSTR HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LOOP_ALM LSR_WILL_DIE NO_BD_PARA NO_BD_SOFT NO_ELABEL OSC_LOS OSC_RDI OUT_PWR_HIGH OUT_PWR_LOW R_LOF R_SLIP SCC_LOC TEMP_OVER TF T_SLIP WRG_BD_TYPE
Issue 02 (2011-10-31)
163
2 Alarm List
2.2.80 SC2 Board Alarm List

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

TN51SCC LCS_EXPIRED ALC_ADJUST_FAIL ALC_WAIT_ADJUST APS_FAIL APS_INDI APS_MANUAL_STOP BD_NOT_INSTALLED BD_STATUS BOOTROM_BAD COMMUN_FAIL CPC_NODE_ID_ERR DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MOD E
Issue 02 (2011-10-31)
SUBRACK_ID_CONFLICT SUBRACK_ID_MISMATCH SUBRACK_LOOP SUBRACK_TYPE_MI SMATCH SWDL_ACTIVATED_ TIMEOUT SWDL_AUTOMATCH _INH SWDL_BD_EXCLUDE SWDL_CHGMNG_NO MATCH SWDL_COMMIT_FAI L SWDL_INPROCESS SWDL_NEPKGCHEC K SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT
164
LCS_FILE_NOT_EXIST MS_APS_INDI_EX NEBD_XC_DIF NESF_LOST NESTATE_INSTALL NODEID_MM NTP_SYNC_FAIL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL
2 Alarm List
DB_RESTORE_FAIL FEATURE_WITHOUT_ LICENSE HARD_BAD HARD_ERR HSC_UNAVAIL K1_K2_M K2_M LCS_DAYS_OF_GRAC E
SECU_ALM SEC_RADIUS_FAIL SERVICE_CAPACITY_EXCEE D_LICENSE SERVICE_TYPE_EXCEED_LICENSE SHELF_AREA_POWER_OVER SNCP_FAIL STORM_CUR_QUENUM_OVE R SUBRACK_COMM_PS
SWDL_ROLLBACK_F AIL SYNC_DISABLE SYNC_FAIL SYSLOG_COMM_FAI L SYSPARA_CFDB_NOSAME TEMP_OVER WRG_BD_TYPE XC_UNSWITCH
TN11SCC ALC_ADJUST_FAIL ALC_WAIT_ADJUST NESF_LOST BD_NOT_INSTALLED BD_STATUS BOOTROM_BAD COMMUN_FAIL DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MODE DB_RESTORE_FAIL FEATURE_WITHOUT_LICENSE HARD_BAD NESTATE_INSTALL NTP_SYNC_FAIL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL SECU_ALM SEC_RADIUS_FAIL STORM_CUR_QUENUM_ OVER
LCS_FILE_NOT_EXIST
SWDL_ACTIVATED_TI MEOUT SWDL_AUTOMATCH_I NH SWDL_BD_EXCLUDE SWDL_CHGMNG_NOMATCH SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_FAI L SYNC_DISABLE SYNC_FAIL
Issue 02 (2011-10-31)
165
2 Alarm List
HARD_ERR HSC_UNAVAIL LCS_DAYS_OF_GRACE LCS_EXPIRED
SUBRACK_ID_CONFLICT SUBRACK_ID_MISMATCH SUBRACK_LOOP SUBRACK_TYPE_MISMATCH
SYSLOG_COMM_FAIL SYSPARA_CFDB_NOSAME TEMP_OVER WRG_BD_TYPE
TN21SCC ALC_ADJUST_FAIL ALC_WAIT_ADJUST LCS_FILE_NOT_EXIST BD_NOT_INSTALLED BD_STATUS BOOTROM_BAD COMMUN_FAIL CPC_NODE_ID_ERR DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MODE DB_RESTORE_FAIL FEATURE_WITHOUT_LICENSE HARD_BAD HARD_ERR HSC_UNAVAIL LCS_DAYS_OF_GRACE NESF_LOST NESTATE_INSTALL NTP_SYNC_FAIL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL SECU_ALM SEC_RADIUS_FAIL STORM_CUR_QUENUM_ OVER SUBRACK_ID_MISMATCH SUBRACK_LOOP SUBRACK_TYPE_MISMATCH LCS_EXPIRED SWDL_ACTIVATED_TI MEOUT SWDL_AUTOMATCH_I NH SWDL_BD_EXCLUDE SWDL_CHGMNG_NOMATCH SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_FAI L SYNC_DISABLE SYNC_FAIL SYSLOG_COMM_FAIL SYSPARA_CFDB_NOSAME TEMP_OVER WRG_BD_TYPE
TN22SCC
2 Alarm List
ALC_ADJUST_FAIL ALC_WAIT_ADJUST BD_NOT_INSTALLED
LCS_DAYS_OF_GRACE LCS_EXPIRED LCS_FILE_NOT_EXIST
SWDL_AUTOMATCH_I NH SWDL_BD_EXCLUDE SWDL_CHGMNG_NOMATCH SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_FAI L SYNC_DISABLE SYNC_FAIL SYSLOG_COMM_FAIL SYSPARA_CFDB_NOSAME TEMP_OVER WRG_BD_TYPE
BD_STATUS BOOTROM_BAD COMMUN_FAIL CPC_NODE_ID_ERR DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MODE DB_RESTORE_FAIL FEATURE_WITHOUT_LICENSE HARD_BAD HARD_ERR HSC_UNAVAIL
NESF_LOST NESTATE_INSTALL NTP_SYNC_FAIL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL SECU_ALM SEC_RADIUS_FAIL STORM_CUR_QUENUM_ OVER SWDL_ACTIVATED_TIM EOUT
TN52SCC ALC_ADJUST_FAIL ALC_WAIT_ADJUST APS_FAIL APS_INDI APS_MANUAL_STOP BD_NOT_INSTALLED LCS_EXPIRED LCS_FILE_NOT_EXIST MS_APS_INDI_EX NEBD_XC_DIF NESF_LOST NESTATE_INSTALL SUBRACK_ID_MISMATCH SUBRACK_LOOP SUBRACK_TYPE_MI SMATCH SWDL_ACTIVATED_ TIMEOUT SWDL_AUTOMATCH _INH SWDL_BD_EXCLUDE
Issue 02 (2011-10-31)
167
2 Alarm List
BD_STATUS BOOTROM_BAD CFCARD_FAILED COMMUN_FAIL CPC_NODE_ID_ERR DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MOD E DB_RESTORE_FAIL FEATURE_WITHOUT_ LICENSE HARD_BAD HARD_ERR HSC_UNAVAIL K1_K2_M K2_M LCS_DAYS_OF_GRAC E
NODEID_MM NTP_SYNC_FAIL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL SECU_ALM SEC_RADIUS_FAIL SERVICE_CAPACITY_EXCEE D_LICENSE SERVICE_TYPE_EXCEED_LICENSE SHELF_AREA_POWER_OVER SNCP_FAIL STORM_CUR_QUENUM_OVE R SUBRACK_COMM_PS SUBRACK_ID_CONFLICT
SWDL_CHGMNG_NO MATCH SWDL_COMMIT_FAI L SWDL_INPROCESS SWDL_NEPKGCHEC K SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_F AIL SYNC_DISABLE SYNC_FAIL SYSLOG_COMM_FAI L SYSPARA_CFDB_NOSAME TEMP_OVER WRG_BD_TYPE XC_UNSWITCH
TNK2SCC ALC_ADJUST_FAIL ALC_WAIT_ADJUST APS_FAIL APS_INDI LCS_EXPIRED LCS_FILE_NOT_EXIST MS_APS_INDI_EX NEBD_XC_DIF SUBRACK_ID_MISMATCH SUBRACK_LOOP SUBRACK_TYPE_MI SMATCH SWDL_ACTIVATED_ TIMEOUT
Issue 02 (2011-10-31)
168
2 Alarm List
APS_MANUAL_STOP BD_NOT_INSTALLED BD_STATUS BOOTROM_BAD CFCARD_FAILED COMMUN_FAIL CPC_NODE_ID_ERR DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MOD E DB_RESTORE_FAIL FEATURE_WITHOUT_ LICENSE HARD_BAD HARD_ERR HSC_UNAVAIL K1_K2_M K2_M LCS_DAYS_OF_GRAC E
NESF_LOST NESTATE_INSTALL NODEID_MM NTP_SYNC_FAIL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL SECU_ALM SEC_RADIUS_FAIL SERVICE_CAPACITY_EXCEE D_LICENSE SERVICE_TYPE_EXCEED_LICENSE SHELF_AREA_POWER_OVER SNCP_FAIL STORM_CUR_QUENUM_OVE R SUBRACK_COMM_PS SUBRACK_ID_CONFLICT
SWDL_AUTOMATCH _INH SWDL_BD_EXCLUDE SWDL_CHGMNG_NO MATCH SWDL_COMMIT_FAI L SWDL_INPROCESS SWDL_NEPKGCHEC K SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_F AIL SYNC_DISABLE SYNC_FAIL SYSLOG_COMM_FAI L SYSPARA_CFDB_NOSAME TEMP_OVER WRG_BD_TYPE XC_UNSWITCH
TN16SCC ALC_ADJUST_FAIL ALC_WAIT_ADJUST APS_MANUAL_STOP LCS_FILE_NOT_EXIST LTI MS_APS_INDI_EX SUBRACK_ID_MISMATCH SUBRACK_LOOP SUBRACK_TYPE_MISMATCH
Issue 02 (2011-10-31)
169
2 Alarm List
APS_FAIL APS_INDI BD_NOT_INSTALLED BD_STATUS BOOTROM_BAD CFCARD_FAILED CLK_LOCK_FAIL CLK_NO_TRACE_MO DE COMMUN_FAIL CPC_NODE_ID_ERR DBMS_ABNORMAL DBMS_ERROR DBMS_PROTECT_MO DE DB_RESTORE_FAIL EXT_SYNC_LOS EXT_TIME_LOC FEATURE_WITHOUT_ LICENSE HARD_BAD HARD_ERR HSC_UNAVAIL K1_K2_M K2_M LCS_DAYS_OF_GRAC E LCS_EXPIRED
NEBD_XC_DIF NESF_LOST NESTATE_INSTALL NODEID_MM NO_BD_SOFT NO_ELABEL NTP_SYNC_FAIL OOL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL PTP_SOURCE_SWITCH PTP_TIMESTAMP_ABN RTC_FAIL S1_SYN_CHANGE SECU_ALM SEC_RADIUS_FAIL SERVICE_CAPACITY_EX CEED_LICENSE SERVICE_TYPE_EXCEED _LICENSE SHELF_AREA_POWER_O VER STORM_CUR_QUENUM_ OVER SUBRACK_COMM_PS SUBRACK_ID_CONFLICT
SWDL_ACTIVATED_TIME OUT SWDL_AUTOMATCH_INH SWDL_BD_EXCLUDE SWDL_CHGMNG_NOMATCH SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_FAIL SYNC_C_LOS SYNC_DISABLE SYNC_FAIL SYNC_F_M_SWITCH SYNC_LOCKOFF SYN_BAD SYSLOG_COMM_FAIL SYSPARA_CFDB_NOSAME TEMP_OVER TIME_LOCK_FAIL TIME_LOS TIME_NO_TRACE_MODE WRG_BD_TYPE
Issue 02 (2011-10-31)
170
2 Alarm List
2.2.82 SCS Board Alarm List

BD_STATUS 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 OPA_FAIL_INDI WRG_BD_TYPE
2.2.83 SFIU Board Alarm List

BD_STATUS MUT_LOS OOS_LOST OPA_FAIL_INDI OTS_BDI OTS_BDI_O OTS_BDI_P OTS_LOS OTS_LOS_O OTS_LOS_P OTS_TIM WAVEDATA_MIS WRG_BD_TYPE
2.2.84 ST2 Board Alarm List

ALM_HANGUP BD_STATUS BEFFEC_EXC COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OSC_BDI OSC_DEG OSC_LOS OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE R_LOF SCC_LOC TD TEMP_OVER TF WRG_BD_TYPE
Issue 02 (2011-10-31)
171
2 Alarm List
2.2.85 SF64 Board Alarm List

ALM_ALS AU_AIS AU_LOP B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BEFFEC_EXC BUS_ERR C2_VCAIS COMMUN_FAIL FEC_LOF FEC_OOF FSELECT_STG HARD_BAD HARD_ERR HP_LOM HP_RDI HP_REI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI MS_REI NO_BD_SOFT ODU_AIS ODU_LCK ODU_OCI OH_LOOP OTU_AIS OTU_LOF OTU_LOM PM_BDI PM_BEI PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WAVEDATA_MIS WRG_BD_TYPE
2.2.86 SF64A Board Alarm List

ALM_ALS AU_AIS AU_LOP
Issue 02 (2011-10-31)
HP_TIM HP_UNEQ IN_PWR_HIGH

PM_BIP8_OVER PM_BIP8_SD PM_TIM

172
2 Alarm List
B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BEFFEC_EXC BUS_ERR C2_VCAIS COMMUN_FAIL FEC_LOF FEC_OOF FSELECT_STG HARD_BAD HARD_ERR HP_LOM HP_RDI HP_REI HP_SLM
IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI MS_REI NO_BD_SOFT ODU_AIS ODU_LCK ODU_OCI OH_LOOP OTU_AIS OTU_LOF OTU_LOM PM_BDI PM_BEI
PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.87 SFD64 Board Alarm List

ALM_ALS AU_AIS AU_LOP B1_EXC B1_SD B2_EXC HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH
PM_BIP8_OVER PM_BIP8_SD PM_TIM PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC
Issue 02 (2011-10-31)
173
2 Alarm List
B2_SD B3_EXC B3_SD BD_STATUS BEFFEC_EXC BUS_ERR C2_VCAIS COMMUN_FAIL FEC_LOF FEC_OOF FSELECT_STG HARD_BAD HARD_ERR HP_LOM HP_RDI HP_REI HP_SLM
LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI MS_REI NO_BD_SOFT ODU_AIS ODU_LCK ODU_OCI OH_LOOP OTU_AIS OTU_LOF OTU_LOM PM_BDI PM_BEI
R_LOF R_LOS SLAVE_WORKING SM_BDI SM_BEI SM_BIP8_OVER SM_BIP8_SD SM_IAE SM_TIM TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WAVEDATA_MIS WRG_BD_TYPE
2.2.88 SL64 Board Alarm List

ALM_ALS AU_AIS AU_LOP B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS HP_LOM HP_RDI HP_REI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH MS_REI NO_BD_SOFT OH_LOOP PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING TEMP_OVER
Issue 02 (2011-10-31)
174
2 Alarm List
BUS_ERR C2_VCAIS COMMUN_FAIL FSELECT_STG HARD_BAD HARD_ERR
LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI
TEM_HA TEM_LA TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.89 SLH41 Board Alarm List

ALM_ALS AU_AIS AU_LOP B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BUS_ERR C2_VCAIS COMMUN_FAIL FSELECT_STG HARD_BAD HARD_ERR HP_LOM HP_RDI HP_REI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI MS_REI NO_BD_SOFT OH_LOOP PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.90 SLD64 Board Alarm List

ALM_ALS AU_AIS
Issue 02 (2011-10-31)
HP_LOM HP_RDI
MS_REI NO_BD_SOFT
175
2 Alarm List
AU_LOP B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BUS_ERR C2_VCAIS COMMUN_FAIL FSELECT_STG HARD_BAD HARD_ERR
HP_REI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI
OH_LOOP PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.91 SLO16 Board Alarm List

ALM_ALS AU_AIS AU_LOP B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BUS_ERR C2_VCAIS
Issue 02 (2011-10-31)
HP_LOM HP_RDI HP_REI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM
MS_REI NO_BD_SOFT OH_LOOP PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING TEMP_OVER TEM_HA TEM_LA
176
2 Alarm List
COMMUN_FAIL FSELECT_STG HARD_BAD HARD_ERR
LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI
TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.92 SLQ16 Board Alarm List

ALM_ALS AU_AIS AU_LOP B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BUS_ERR C2_VCAIS COMMUN_FAIL FSELECT_STG HARD_BAD HARD_ERR HP_LOM HP_RDI HP_REI HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI MS_REI NO_BD_SOFT OH_LOOP PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.93 SLQ64 Board Alarm List

ALM_ALS AU_AIS AU_LOP HP_LOM HP_RDI HP_REI MS_REI NO_BD_SOFT OH_LOOP
Issue 02 (2011-10-31)
177
2 Alarm List
B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BUS_ERR C2_VCAIS COMMUN_FAIL FSELECT_STG HARD_BAD HARD_ERR
HP_SLM HP_TIM HP_UNEQ IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LASER_SHUT LOOP_ALM LSR_COOL_ALM LSR_WILL_DIE MS_AIS MS_RDI
PORT_MODULE_OFFLINE POWER_ABNORMAL R_LOC R_LOF R_LOS SLAVE_WORKING TEMP_OVER TEM_HA TEM_LA TEST_STATUS TF TR_LOC WRG_BD_TYPE
2.2.94 STG Board Alarm List

BD_STATUS CLK_NO_TRACE_MOD E COMMUN_FAIL EXT_SYNC_LOS EXT_TIME_LOC HARD_BAD HARD_ERR LTI NO_BD_SOFT NO_ELABEL OOL S1_SYN_CHANGE SYNC_C_LOS SYNC_F_M_SWITCH TEMP_OVER TIME_LOS TIME_NO_TRACE_MODE WRG_BD_TYPE SYNC_LOCKOFF SYN_BAD
2.2.95 STI Board Alarm List

BD_STATUS WRG_BD_TYPE
Issue 02 (2011-10-31)
178
2 Alarm List
2.2.96 SXM Board Alarm List

BD_STATUS BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL TEMP_OVER WRG_BD_TYPE
2.2.97 SXH Board Alarm List

BD_STATUS BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL TEMP_OVER WRG_BD_TYPE
2.2.98 TBE Board Alarm List

B1_EXC B1_SD BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL DBPS_ABNORMAL DLAG_PROTECT_FAIL ETHOAM_DISCOVER_FA IL ETHOAM_RMT_CRIT_FA ULT ETHOAM_RMT_LOOP ETHOAM_RMT_SD ETHOAM_SELF_LOOP
Issue 02 (2011-10-31)
ETH_CFM_RDI ETH_CFM_UNEXPERI EX_ETHOAM_CC_LOS EX_ETHOAM_MPID_CNFL CT FLOW_OVER HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LAG_PORT_FAIL LAG_VC_PORT_FAIL LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM
MULTI_RPL_OWNER NO_BD_SOFT NO_ELABEL OPA_FAIL_INDI OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE RS_CROSSTR R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF
179
2 Alarm List
ETHOAM_VCG_SELF_LO OP ETH_CFM_LOC ETH_CFM_MACSTATUS ETH_CFM_MISMERGE
LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE
VLAN_SNCP_PS WAVEDATA_MIS WRG_BD_TYPE
2.2.99 TDC Board Alarm List

BD_STATUS COMMUN_FAIL DCM_INSUFF HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW NO_BD_SOFT NO_ELABEL R_LOS TEMP_OVER WRG_BD_TYPE
2.2.100 TDG Board Alarm List

BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_WILL_DIE MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM OPA_FAIL_INDI OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE REM_SD REM_SF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
180
2 Alarm List
LSR_INVALID
OPU1_PLM
2.2.101 TDX Board Alarm List

TN53TDX ALS_ACTIVE B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MIS MATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_EXC ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_EXC ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODUFLEX_LOFLOM ODUFLEX_PLM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_EXC ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODU_SNCP_STA_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA
Issue 02 (2011-10-31)
181
2 Alarm List
NULL_SEND ODU2_LOFLOM ODU2_PM_AIS
ODUFLEX_PM_SSF ODUFLEX_PM_TIM ODU_SNCP_PS
TN52TDX ALS_ACTIVE B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MIS MATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF REMOTE_FAULT R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
182
2 Alarm List
TN11TDX B1_EXC B1_SD BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL FLOW_OVER HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE MS_AIS NO_BD_SOFT NO_ELABEL ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM OPA_FAIL_INDI OPU1_PLM OPU1_VCAT_SQM OPU1_VCAT_VcPLM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF VCAT_LOA WAVEDATA_MIS WRG_BD_TYPE
TN12TDX B1_EXC B1_SD BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL ODU2_LOFLOM ODU2_PM_AIS OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF
Issue 02 (2011-10-31)
183
2 Alarm List
COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM
ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_EXC ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU2_PLM
R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.102 THA Board Alarm List

ALS_ACTIVE B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU_SNCP_PS ODU_SNCP_STA_INDI OPU0_PLM OPU1_MSIM OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW
Issue 02 (2011-10-31)
184
2 Alarm List
LASER_MODULE_MIS MATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_EXC ODU0_PM_LCK
ODU1_TCMn_EXC ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODUFLEX_LOFLOM ODUFLEX_PLM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_EXC ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF ODUFLEX_PM_TIM
PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
NOTE
2.2.103 TMX Board Alarm List

TN11TMX B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS
Issue 02 (2011-10-31)
185
2 Alarm List
HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS
ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK
ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OPU2_MSIM OPU2_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF
Issue 02 (2011-10-31)
186
2 Alarm List
ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI
ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS
OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN12TMX B1_EXC B1_SD BD_STATUS BEFFEC_EXC CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_LCK ODU1_TCM4_LTC ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS
Issue 02 (2011-10-31)
187
2 Alarm List
COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM
ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK
ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM OPA_FAIL_INDI OPU1_PLM OPU2_MSIM OPU2_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF
Issue 02 (2011-10-31)
188
2 Alarm List
ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI
ODU2_TCM1_LTC ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI
OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.104 TOA Board Alarm List

ALS_ACTIVE B1_EXC B1_SD BD_STATUS BEFFEC_EXC ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU_SNCP_PS ODU_SNCP_STA_INDI OPU0_PLM OPU1_MSIM OPU1_PLM
Issue 02 (2011-10-31)
189
2 Alarm List
BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MIS MATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_EXC ODU0_PM_LCK
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCMn_AIS ODU1_TCMn_BDI ODU1_TCMn_DEG ODU1_TCMn_EXC ODU1_TCMn_LCK ODU1_TCMn_LTC ODU1_TCMn_OCI ODU1_TCMn_SSF ODU1_TCMn_TIM ODUFLEX_LOFLOM ODUFLEX_PLM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_EXC ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF ODUFLEX_PM_TIM
OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
NOTE
Issue 02 (2011-10-31)
190
2 Alarm List
2.2.105 TOG Board Alarm List

BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM OPU0_PLM OPU1_PLM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE REM_SD REM_SF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.106 TOM Board Alarm List

TN52TOM B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART
Issue 02 (2011-10-31)
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS
ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC

191
2 Alarm List
COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P
ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC
ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU0_PLM OPU1_MSIM OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS
Issue 02 (2011-10-31)
192
2 Alarm List
ODU0_LOFLOM ODU0_PM_AIS ODU0_PM_BDI ODU0_PM_DEG ODU0_PM_LCK ODU0_PM_OCI ODU0_PM_SSF ODU0_PM_TIM ODU1_LOFLOM ODU1_PM_AIS
ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK
SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
TN11TOM B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR INTRA_OTU_PS INTRA_OTU_STA_INDI IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI
Issue 02 (2011-10-31)
193
2 Alarm List
LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL NULL_SEND OCh_FDI OCh_FDI_O OCh_FDI_P OCh_LOS_P OCh_OCI OCh_SSF OCh_SSF_O OCh_SSF_P ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK
ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC
OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
2.2.107 TQM Board Alarm List

TN11TQM
2 Alarm List
B1_EXC B1_SD BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN
LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM OPA_FAIL_INDI OPU1_PLM
OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH WAVEDATA_MIS WRG_BD_TYPE
TN12TQM B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU_SNCP_PS
Issue 02 (2011-10-31)
195
2 Alarm List
COMMUN_FAIL ETH_8B10B_ERR HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LINK_ERR LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE L_SYNC MS_AIS MS_SNCP_PS MS_SNCP_STA_INDI NO_BD_SOFT NO_ELABEL ODU1_LOFLOM ODU1_PM_AIS ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS
ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI
ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS SPEED_OVER SW_SNCP_PS SW_SNCP_STA_INDI TD TEMP_OVER TEM_HA TEM_LA TF TS_CFG_MISMATCH
Issue 02 (2011-10-31)
196
2 Alarm List
ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK
ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS ODU1_TCM6_BDI
WAVEDATA_MIS WRG_BD_TYPE
2.2.108 TQS Board Alarm List

B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOOP_ALM LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL ODU1_LOFLOM ODU1_PM_AIS ODU1_TCM1_TIM ODU1_TCM2_AIS ODU1_TCM2_BDI ODU1_TCM2_DEG ODU1_TCM2_EXC ODU1_TCM2_LCK ODU1_TCM2_LTC ODU1_TCM2_OCI ODU1_TCM2_SSF ODU1_TCM2_TIM ODU1_TCM3_AIS ODU1_TCM3_BDI ODU1_TCM3_DEG ODU1_TCM3_EXC ODU1_TCM3_LCK ODU1_TCM3_LTC ODU1_TCM3_OCI ODU1_TCM3_SSF ODU1_TCM3_TIM ODU1_TCM4_AIS ODU1_TCM4_BDI ODU1_TCM4_DEG ODU1_TCM4_EXC ODU1_TCM6_BDI ODU1_TCM6_DEG ODU1_TCM6_EXC ODU1_TCM6_LCK ODU1_TCM6_LTC ODU1_TCM6_OCI ODU1_TCM6_SSF ODU1_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU1_PLM OTU1_AIS OTU1_BDI OTU1_DEG OTU1_EXC OTU1_LOF OTU1_LOM OTU1_SSF OTU1_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE
Issue 02 (2011-10-31)
197
2 Alarm List
ODU1_PM_BDI ODU1_PM_DEG ODU1_PM_EXC ODU1_PM_LCK ODU1_PM_OCI ODU1_PM_SSF ODU1_PM_TIM ODU1_TCM1_AIS ODU1_TCM1_BDI ODU1_TCM1_DEG ODU1_TCM1_EXC ODU1_TCM1_LCK ODU1_TCM1_LTC ODU1_TCM1_OCI ODU1_TCM1_SSF
ODU1_TCM4_LCK ODU1_TCM4_LTC ODU1_TCM4_OCI ODU1_TCM4_SSF ODU1_TCM4_TIM ODU1_TCM5_AIS ODU1_TCM5_BDI ODU1_TCM5_DEG ODU1_TCM5_EXC ODU1_TCM5_LCK ODU1_TCM5_LTC ODU1_TCM5_OCI ODU1_TCM5_SSF ODU1_TCM5_TIM ODU1_TCM6_AIS
REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.109 TQX Board Alarm List

TN55TQX ALS_ACTIVE B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_EXC ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_EXC OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_EXC OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW
Issue 02 (2011-10-31)
198
2 Alarm List
HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MIS MATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_LOFLOM ODU2_PM_AIS
ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODUFLEX_LOFLOM ODUFLEX_PLM ODUFLEX_PM_AIS ODUFLEX_PM_BDI ODUFLEX_PM_DEG ODUFLEX_PM_EXC ODUFLEX_PM_LCK ODUFLEX_PM_OCI ODUFLEX_PM_SSF ODUFLEX_PM_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI
PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN53TQX B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_I NDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD NULL_SEND ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_EXC ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM OTU2_DEG OTU2_EXC OTU2_LOF OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS
Issue 02 (2011-10-31)
199
2 Alarm List
HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MIS MATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM LSR_INVALID LSR_WILL_DIE L_SYNC NO_BD_SOFT NO_ELABEL
ODU2_TCMn_AIS ODU2_TCMn_BDI ODU2_TCMn_DEG ODU2_TCMn_EXC ODU2_TCMn_LCK ODU2_TCMn_LTC ODU2_TCMn_OCI ODU2_TCMn_SSF ODU2_TCMn_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPU2_PLM OTU2_AIS OTU2_BDI
REMOTE_FAULT REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN52TQX B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM ODU2_TCM1_OCI ODU2_TCM1_SSF ODU2_TCM1_TIM ODU2_TCM2_AIS ODU2_TCM2_BDI ODU2_TCM2_DEG ODU2_TCM2_LCK ODU2_TCM2_LTC ODU2_TCM2_OCI ODU2_TCM2_SSF ODU2_TCM2_TIM ODU2_TCM3_AIS ODU2_TCM3_BDI ODU2_TCM3_DEG ODU2_TCM6_BDI ODU2_TCM6_DEG ODU2_TCM6_LCK ODU2_TCM6_LTC ODU2_TCM6_OCI ODU2_TCM6_SSF ODU2_TCM6_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPU2_PLM OTU2_AIS OTU2_BDI OTU2_DEG OTU2_LOF
Issue 02 (2011-10-31)
200
2 Alarm List
LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU2_TCM1_AIS ODU2_TCM1_BDI ODU2_TCM1_DEG ODU2_TCM1_LCK ODU2_TCM1_LTC
ODU2_TCM3_LCK ODU2_TCM3_LTC ODU2_TCM3_OCI ODU2_TCM3_SSF ODU2_TCM3_TIM ODU2_TCM4_AIS ODU2_TCM4_BDI ODU2_TCM4_DEG ODU2_TCM4_LCK ODU2_TCM4_LTC ODU2_TCM4_OCI ODU2_TCM4_SSF ODU2_TCM4_TIM ODU2_TCM5_AIS ODU2_TCM5_BDI ODU2_TCM5_DEG ODU2_TCM5_LCK ODU2_TCM5_LTC ODU2_TCM5_OCI ODU2_TCM5_SSF ODU2_TCM5_TIM ODU2_TCM6_AIS
OTU2_LOM OTU2_SSF OTU2_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD REM_SF R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
TN11TQX B1_EXC B1_SD BD_STATUS BUS_ERR CLIENT_PORT_PS LSR_FORCE_OPEN LSR_INVALID LSR_WILL_DIE NO_BD_SOFT NO_ELABEL OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REMOTE_FAULT REM_SD
Issue 02 (2011-10-31)
201
2 Alarm List
CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LASER_MODULE_MISMATCH LOCAL_FAULT LOOP_ALM LPT_ACTIVE LSR_COOL_ALM
ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU2_PLM OUT_PWR_HIGH
REM_SF R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WAVEDATA_MIS WRG_BD_TYPE
2.2.110 TSXL Board Alarm List

TN11TSXL B1_EXC B1_SD BD_STATUS BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW MS_AIS NO_BD_SOFT NO_ELABEL ODU2_LOFLOM ODU2_PM_AIS ODU2_PM_BDI ODU2_PM_DEG ODU2_PM_EXC ODU2_PM_LCK ODU2_PM_OCI ODU2_PM_SSF ODU2_PM_TIM OUT_PWR_HIGH OUT_PWR_LOW PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF RS_CROSSTR R_LOC R_LOF R_LOS TD TEMP_OVER
Issue 02 (2011-10-31)
202
2 Alarm List
J0_MM LOOP_ALM LSR_COOL_ALM LSR_FORCE_OPEN LSR_WILL_DIE
ODU_SNCP_PS ODU_SNCP_STA_INDI OPA_FAIL_INDI OPU2_MSIM OPU2_PLM
TEM_HA TEM_LA TF VCAT_LOA WRG_BD_TYPE
TN53TSXL B1_EXC B1_SD BD_STATUS BEFFEC_EXC BUS_ERR CLIENT_PORT_PS CLIENT_PORT_STA_INDI CLIENT_PROT_NOTSTART COMMUN_FAIL HARD_BAD HARD_ERR IN_PWR_HIGH IN_PWR_LOW J0_MM LOOP_ALM LSR_FORCE_OPEN LSR_WILL_DIE NO_BD_SOFT NO_ELABEL NULL_SEND ODU3_PM_AIS ODU3_PM_BDI ODU3_TCM2_AIS ODU3_TCM2_BDI ODU3_TCM2_DEG ODU3_TCM2_LCK ODU3_TCM2_LTC ODU3_TCM2_OCI ODU3_TCM2_SSF ODU3_TCM2_TIM ODU3_TCM2_EXC ODU3_TCM3_AIS ODU3_TCM3_BDI ODU3_TCM3_DEG ODU3_TCM3_LCK ODU3_TCM3_LTC ODU3_TCM3_OCI ODU3_TCM3_SSF ODU3_TCM3_TIM ODU3_TCM3_EXC ODU3_TCM4_AIS ODU3_TCM4_BDI ODU3_TCM4_DEG ODU3_TCM4_LCK ODU3_TCM6_BDI ODU3_TCM6_DEG ODU3_TCM6_LCK ODU3_TCM6_LTC ODU3_TCM6_OCI ODU3_TCM6_SSF ODU3_TCM6_TIM ODU3_TCM6_EXC ODU_SNCP_PS ODU_SNCP_STA_INDI OPU3_MSIM OPU3_PLM OTU3_AIS OTU3_BDI OTU3_DEG OTU3_LOF OTU3_LOM OTU3_SSF OTU3_TIM OTU3_EXC OUT_PWR_HIGH OUT_PWR_LOW
Issue 02 (2011-10-31)
203
2 Alarm List
ODU3_PM_DEG ODU3_PM_LCK ODU3_PM_OCI ODU3_PM_SSF ODU3_PM_TIM ODU3_PM_EXC ODU3_TCM1_AIS ODU3_TCM1_BDI ODU3_TCM1_DEG ODU3_TCM1_LCK ODU3_TCM1_LTC ODU3_TCM1_OCI ODU3_TCM1_SSF ODU3_TCM1_TIM ODU3_TCM1_EXC
ODU3_TCM4_LTC ODU3_TCM4_OCI ODU3_TCM4_SSF ODU3_TCM4_TIM ODU3_TCM4_EXC ODU3_TCM5_AIS ODU3_TCM5_BDI ODU3_TCM5_DEG ODU3_TCM5_LCK ODU3_TCM5_LTC ODU3_TCM5_OCI ODU3_TCM5_SSF ODU3_TCM5_TIM ODU3_TCM5_EXC ODU3_TCM6_AIS
PORT_MODULE_OFFLINE PRBS_LSS REM_SD REM_SF R_LOC R_LOF R_LOS TD TEMP_OVER TEM_HA TEM_LA TF WRG_BD_TYPE
2.2.111 VA1 Board Alarm List

TN11VA1 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULE_TEMP_OVE R MUT_LOS NO_BD_PARA NO_BD_SOFT NO_ELABEL OPA_FAIL_INDI SPAN_LOSS_HIGH SPAN_LOSS_LOW SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
TN12VA1 BD_STATUS COMMUN_FAIL HARD_BAD

Issue 02 (2011-10-31)
OPA_FAIL_INDI SPAN_LOSS_HIGH SPAN_LOSS_LOW

VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE

204
2 Alarm List
HARD_ERR
TEMP_OVER
2.2.112 VA4 Board Alarm List

TN11VA4 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULE_TEMP_OVE R NO_BD_PARA NO_BD_SOFT NO_ELABEL OPA_FAIL_INDI SPAN_LOSS_HIGH SPAN_LOSS_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
TN12VA4 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR OPA_FAIL_INDI SPAN_LOSS_HIGH SPAN_LOSS_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
2.2.113 WMU Board Alarm List

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

TN11WSD9 BD_STATUS COMMUN_FAIL HARD_BAD NO_BD_PARA NO_BD_SOFT NO_ELABEL OMS_LOS_P OMS_SSF OMS_SSF_O
Issue 02 (2011-10-31)
205
2 Alarm List
HARD_ERR IN_PWR_HIGH IN_PWR_LOW MODULE_ADJUST_FAI L MOD_COM_FAIL MUT_LOS
OMS_BDI OMS_BDI_O OMS_BDI_P OMS_FDI OMS_FDI_O OMS_FDI_P
OMS_SSF_P OPA_FAIL_INDI TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
TN12WSD9/TN13WSD9 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
2.2.115 WSM9 Board Alarm List

TN11WSM9 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULE_ADJUST_FAI L MOD_COM_FAIL NO_BD_PARA NO_BD_SOFT NO_ELABEL OPA_FAIL_INDI TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
TN12WSM9/TN13WSM9
Issue 02 (2011-10-31)
206
2 Alarm List
BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR
MODULEFILE_UPDATE_FAI L MODULE_ADJUST_FAIL MOD_COM_FAIL OPA_FAIL_INDI
TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
2.2.116 WSMD2 Board Alarm List

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE

TN11WSMD4 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
Issue 02 (2011-10-31)
207
2 Alarm List
TN12WSMD4 BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WRG_BD_TYPE

BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR MODULEFILE_UPDATE_F AIL MODULE_ADJUST_FAIL MOD_COM_FAIL MUT_LOS NO_BD_SOFT NO_BD_PARA NO_ELABEL 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 OPA_FAIL_INDI SUM_INPWR_HI SUM_INPWR_LOW TEMP_OVER VOADATA_MIS WAVEDATA_MIS WRG_BD_TYPE
2.2.119 XCH Board Alarm List

TN52XCH BD_STATUS BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL TEMP_OVER WRG_BD_TYPE
TN16XCH
2 Alarm List
ALC_ADJUST_FAI L ALC_WAIT_ADJUS T APS_FAIL
SUBRACK_LOOP LCS_FILE_NOT_EXIST LTI MS_APS_INDI_EX SUBRACK_TYPE_MISMATCH SWDL_ACTIVATED_TI MEOUT SWDL_AUTOMATCH_I NH SWDL_CHGMNG_NOMATCH SWDL_BD_EXCLUDE SWDL_COMMIT_FAIL SWDL_INPROCESS SWDL_NEPKGCHECK SWDL_PKGVER_MM SWDL_PKG_NOBDSOFT SWDL_ROLLBACK_FA IL SYNC_C_LOS SYNC_DISABLE SYNC_FAIL SYNC_F_M_SWITCH SYNC_LOCKOFF SYN_BAD SYSLOG_COMM_FAIL SYSPARA_CFDB_NOSAME TEMP_OVER TIME_LOS
APS_INDI NEBD_XC_DIF APS_MANUAL_ST OP BD_NOT_INSTALL ED BD_STATUS BOOTROM_BAD BUS_ERR CFCARD_FAILED CLK_NO_TRACE_ MODE COMMUN_FAIL CPC_NODE_ID_ER R DBMS_ABNORMA L DBMS_ERROR DBMS_PROTECT_ MODE DB_RESTORE_FAI L EXT_SYNC_LOS EXT_TIME_LOC FEATURE_WITHO UT_LICENSE HARD_BAD HARD_ERR NESF_LOST NESTATE_INSTALL NODEID_MM NO_BD_SOFT NO_ELABEL NTP_SYNC_FAIL OOL PATCH_ACT_TIMEOUT PATCH_DEACT_TIMEOUT PATCH_PKGERR POWER_FAIL RTC_FAIL S1_SYN_CHANGE SECU_ALM SEC_RADIUS_FAIL SERVICE_CAPACITY_EXCEED_ LICENSE SERVICE_TYPE_EXCEED_LICENSE SHELF_AREA_POWER_OVER
Issue 02 (2011-10-31)
209
2 Alarm List
HSC_UNAVAIL K1_K2_M K2_M LCS_DAYS_OF_GR ACE LCS_EXPIRED
SNCP_FAIL STORM_CUR_QUENUM_OVER SUBRACK_COMM_PS SUBRACK_ID_CONFLICT SUBRACK_ID_MISMATCH
TIME_NO_TRACE_MO DE WRG_BD_TYPE XC_UNSWITCH
2.2.120 XCM Board Alarm List

TN52XCM BD_STATUS BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL TEMP_OVER WRG_BD_TYPE
2.2.121 XCS Board Alarm List

TN11XCS BD_STATUS BUS_ERR COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL TEMP_OVER WRG_BD_TYPE
TN12XCS BD_STATUS COMMUN_FAIL HARD_BAD HARD_ERR NO_BD_SOFT NO_ELABEL TEMP_OVER WRG_BD_TYPE
2.2.122 XCT Board Alarm List

BD_STATUS BUS_ERR COMMUN_FAIL
Issue 02 (2011-10-31)
HARD_BAD HARD_ERR NO_BD_SOFT
NO_ELABEL TEMP_OVER WRG_BD_TYPE

210
3 Common Alarm Processing
3
About This Chapter
NOTE
Common Alarm Processing
This topic describes common information relevant to alarm handling, including alarm descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.
By default, optical-layer alarms (OTS, OMS, and OCH alarms) are not reported. You can enable opticallayer alarm reporting as required using the NMS. For details, see "Enabling/Disabling Supervision on the Optical Layer" in the Supporting Tasks.
NOTE
In the case of an alarm, see its handling procedure to clear it; if the alarm persists, contact Huawei engineers for troubleshooting.
The alarm handling involves board reset, either cold or warm. Cold reset and warm reset have different impacts on services. l Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software, neither the FPGA file nor hardware data is updated and so a warm reset does not interrupt services. A cold reset of the SCC might result in re-setting of the key hardware, such as FPGA reloading; the upper-layer software need be restarted. Reset of other boards: A warm reset on other boards does not affect running services while a cold reset on other boards does. If such a board is reset incorrectly, the communication between the board and the SCC is affected and even the services are interrupted.
Certain alarms listed in this topic are handled in different ways, because the board types are different. This topic describes how to handle alarms in the OCS and OTN systems separately according to the system where the board is located. 3.1 B1_EXC Refer to the alarm page according to the type of the board that reports the alarm. 3.2 BEFFEC_EXC 3.3 BOOTROM_BAD See the alarm page according to the type of the board that reports the alarm. 3.4 BUS_ERR
See the alarm page according to the type of the board that reports the alarm. 3.5 CHAN_LOS 3.6 CLIENT_PORT_PS 3.7 COMMUN_FAIL Refer to the alarm page according to the type of the board that reports the alarm. 3.8 ETH_8B10B_ERR 3.9 EX_ETHOAM_CC_LOS Refer to the alarm page according to the type of the board that reports the alarm. 3.10 FC_LINK_ERR 3.11 FC_SYNC_LOS 3.12 IN_PWR_HIGH Refer to the alarm page according to the type of the board that reports the alarm. 3.13 IN_PWR_LOW Refer to the alarm page according to the type of the board that reports the alarm. 3.14 INTRA_OTU_PS 3.15 LASER_MODULE_MISMATCH 3.16 LINK_ERR Refer to the alarm page according to the type of the board that reports the alarm. 3.17 LOOP_ALM Refer to the alarm page according to the type of the board that reports the alarm. 3.18 LPT_ACTIVE 3.19 LSR_WILL_DIE 3.20 MS_AIS Refer to the alarm page according to the type of the board that reports the alarm. 3.21 MS_RDI Refer to the alarm page according to the type of the board that reports the alarm. 3.22 MUT_LOS 3.23 OA_LOW_GAIN 3.24 ODU_SNCP_PS 3.25 ODUk_PM_AIS 3.26 ODUk_PM_BDI 3.27 ODUk_PM_DEG 3.28 ODUk_PM_EXC 3.29 ODUk_PM_SSF 3.30 OMS_FDI 3.31 OSC_LOS
3.32 OTS_LOS 3.33 OTUk_LOF 3.34 OTUk_SSF 3.35 OUT_PWR_HIGH 3.36 PORT_MODULE_OFFLINE 3.37 POWER_FAIL 3.38 PUMP_COOL_EXC 3.39 R_LOF Refer to the alarm page according to the type of the board that reports the alarm. 3.40 R_LOS Refer to the alarm page according to the type of the board that reports the alarm. 3.41 R_OOF Refer to the alarm page according to the type of the board that reports the alarm. 3.42 R_SLIP 3.43 REM_SF 3.44 REMOTE_FAULT 3.45 SECU_ALM 3.46 SUBRACK_ID_CONFLICT 3.47 SUM_INPWR_LOW 3.48 SWDL_NEPKGCHECK 3.49 TD 3.50 TEMP_OVER 3.51 TF 3.52 TS_CFG_MISMATCH 3.53 WRG_BD_TYPE
Issue 02 (2011-10-31)
213
3.1 B1_EXC
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-1 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.1.1 B1_EXC (OCS) 3.1.2 B1_EXC (OTN)
3.1.1 B1_EXC (OCS)

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

l l When the B1_EXC occurs, the quality of the transmitted services is degraded. When the B1_EXC occurs, by default, the system inserts the AU_AIS alarm in the crossconnection direction.
Possible Causes
The possible causes of the B1_EXC alarm are as follows: l l
Issue 02 (2011-10-31)
Cause 1: The line performance degrades. Cause 2: The external environment is abnormal.
l l
Cause 3: The receive board of the local end is faulty. Cause 4: The transmit board of the opposite end is faulty.
Procedure
l Query current alarms on the U2000. According to parameter 1, determine the ID of the interface that reports the alarm. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The line performance degrades. 1. Check whether the transmit power at the opposite station and the receive power at the local station meet the specifications of the interfaces. For details on optical power specification of the board, see"Technical Specifications" of the Product Description. For details, see Querying Optical Power of the Board in the Supporting Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the manufacturer information about the board optical module.
If... The transmit optical power of the opposite station is normal, but the receive optical power of the local station is almost equal to the specification (for example, within 3 dB) of the receiver sensitivity, The transmit optical power of the local board is abnormal, 2. Check whether the optical connector is normal. If... The connector is loose Then...
Then... Proceed to the next step.
See cause 4.
Tighten the optical connector. Check whether the alarm is cleared. If the alarm persists, proceed to the next step.
The interface is normal Proceed to the next step. 3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task.
Issue 02 (2011-10-31)
215
If... The connector is dirty
Then... Clean the optical connector. For details, see l Cleaning Optical Fiber Connectors Using Cartridge Cleaners l Cleaning Optical Fiber Connectors Using Lens Tissue l Cleaning Optical Adapters Using Optical Cleaning Sticks in Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step.
The connector is normal Proceed to the next step. 4. Check whether the attenuation value of the optical attenuator is proper according to the specified receive optical power. For details on optical power specifications of the board, see "Technical Specifications" of the Product Description. If... The value of optical attenuation is improper, Then ... Adjust the attenuation to the proper value. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
The value of optical attenuation is proper, 5.
Check whether the fiber is faulty. Especially, check whether the bending radius of a fiber jumper is within the normal range, and check whether the fiber from the equipment to the ODF and the fiber outside the equipment room are pressed. If the bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm persists, see cause 2. Check the ambient temperature of the equipment room. If the temperature is higher than 45C or is lower than 0C, use a cooler/heater to decrease/increase the ambient temperature. Check whether the alarm is cleared. If the alarm persists, see cause 3. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting Task.
Cause 2: The external environment is abnormal. 1.
2. l 1.
Cause 3: The receive board of the local end is faulty.
Issue 02 (2011-10-31)
216
CAUTION
The loopback may cause service interruptions. If... Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next step. No bit error alarm is reported, 2. See cause 4.
If the board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the local faulty board. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see cause 4. If the board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the faulty board at the opposite end. For details, see Parts Replacement.
3. l 1.
Cause 4: The transmit board of the opposite end is faulty.
----End
Related Information
None.
3.1.2 B1_EXC (OTN)

Description
The B1_EXC (OTN) alarm indicates the regenerator section (B1) excessive errors. The alarm is generated when the received SDH signals degrade and the B1 bit errors in the multiplex section exceed the threshold. Reported from the WDM side or client side: WDM side client side. l l The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received on the WDM side exceed the B1 bit error threshold. The alarm is generated on the client side when the B1 bit errors in the SDH signals received on the client side exceed the B1 bit error threshold.
Attribute
Parameters
None

The B1 bit errors in the service signals received by the board exceed the threshold of the B1 bit errors set for the board. The alarm affects the QoS of the service signals.
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic, handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l l l l l Cause 1 of this alarm generated on the client side: The input signals on the client side contain B1 bit errors. Cause 2 of this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 of this alarm generated on the WDM side: The receive side of the local station (Station B) is faulty. Cause 2 of this alarm generated on the WDM side: The attenuation of the received signals is excessively high; the fiber or connector is not clean. Cause 3 of this alarm generated on the WDM side: The transmit side of the opposite station (Station A) is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated.
Detects and reports the B1_EXC alarm OTU1 Client side WDM side Station A Station B
O A D M F I U F I U O A D M
Detects and reports the B1_EXC alarm
OTU2
Out-loop
WDM side Client side
Cause 1 of this alarm generated on the client side: The input signals on the client side contain B1 bit errors. 1. If this alarm is reported from the client side of the board, apply a hardware loopback between the transmit and receive optical ports on the client side of OTU1. If the alarm on OTU1 persists, it indicates that the OTU1 hardware is faulty. In this case, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
Configuring a loopback on the board interrupts the services on the board.
Issue 02 (2011-10-31)
218
2. l
If the alarm is cleared, it indicates that the input signals on the client side of the board contain B1 bit errors. In this case, rectify the fault on the client equipment. Check whether the board that reports this alarm supports pluggable optical modules. If ... Then ...
Cause 2 of this alarm generated on the client side: The board that reports the alarm is faulty. 1.
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
Cause 1 of this alarm generated on the WDM side: The receive side of the local station (Station B) is faulty. 1. Configure outloop at the transmit and receive optical ports on the WDM side of OTU2. If there is no bit error alarm on the OTU1, it indicates that the board at the local station (Station B) is faulty. Replace the faulty board. If ... Then ...
CAUTION
Configuring a loopback on the board interrupts the services on the board. 2. l If OTU1 has bit error alarms, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
Cause 2 of this alarm generated on the WDM side: The attenuation of the received signals is excessively high; the fiber or connector is not clean. 1. If there are bit errors, check the transmit optical power at the corresponding optical ports on the opposite OTU1 on the U2000. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.For details, refer to "Querying Optical Power on the U2000" of the Supporting Tasks.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards" of the Hardware Description to obtain the manufacturing information of the optical module on the board.
Issue 02 (2011-10-31)
219
2.
If the transmit optical power of the corresponding optical port on OTU1 is within the normal range, check the attenuation of the transmission link between transmitting module of OTU1 at the opposite station and the receiving module of OTU2 at the local station. If the preset attenuation values are excessively large, correct them so that they are within the normal range. For details, see "Adjusting, Replacing, Adding, and Removing Attenuator" in the Supporting Tasks. If the alarm persists, check the fiber connectors at stations A and B separately. If the fiber connectors are dirty, clean or replace them. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see "Replacing Fiber Jumpers" in the Supporting Tasks. If the fibers inside a station are normal, check the optical cables between stations to rectify the fault. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm generated on the WDM side.
3.
4.
5. l
Cause 3 of this alarm generated on the WDM side: The transmit side of the opposite station (Station A) is faulty. 1. If the transmit optical power of the corresponding optical port on OTU1 at the opposite station is abnormal, it indicates that OTU1 is faulty. In this case, replace the board. If ... Then ...
2. ----End
Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
Related Information
None.
3.2 BEFFEC_EXC
Description
This alarm indicates that signals are degraded before FEC. Signals sent from WDM sides of the opposite-end OTU have the FEC function. As a result, before performing signal FEC in the receive direction of WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm occurs when the counted bit error rate crosses the threshold. Reported from the WDM or client side: WDM side.
Issue 02 (2011-10-31)
220
Attribute
Parameters
None

The error tolerance of the system decreases, which affects the quality of signals if the decrease is sufficient.
Fault Symptom
Table 3-2 lists the fault symptom for the BEFFEC_EXC alarm. Table 3-2 Fault symptom for the BEFFEC_EXC alarm Fault Symptom The NE that reports this alarm reports a temperature alarm or fan fault alarm, such as TEMP_OVER or FAN_FAIL, within a certain time. Cause Cause 3 of this alarm in the case of multiple wavelengths: The external environment is improper.
NOTE
Possible Causes
The possible causes of the BEFFEC_EXC alarm are as follows: l l l l l l Cause 1 of this alarm in the case of a single wavelength: The input optical power of the OTU board is extremely high or low. Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of the interconnected OTUs are different. Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board and the multiplexer/demultiplexer board is faulty. Cause 4 of this alarm in the case of a single wavelength: An inappropriate DCM is installed. Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm is faulty. Cause 6 of this alarm in the case of a single wavelength: The board at the opposite station is faulty.
Issue 02 (2011-10-31)
l l l
Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables between stations or the multiplexing portions inside a station are faulty. Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals during line transmission is excessively high. Cause 3 of this alarm in the case of multiple wavelengths: The external environment is improper.
Procedure
Step 1 Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Step 2 Cause 1 of this alarm in the case of a single wavelength: The input optical power of the OTU board is extremely high or low. 1. Check whether the received optical power on the U2000 is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
2. 3.
If the input optical power is abnormal, see the methods for handling the IN_PWR_HIGH and IN_PWR_LOW alarms. If the input optical power is normal but the alarm persists, see the alarm handling procedure for cause 2 of this alarm in the case of a single wavelength.
Step 3 Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of the interconnected OTUs are different. 1. On the U2000, check the settings of FEC mode of the two interconnected OTUs. If the settings are different, change the settings to FEC or AFEC to ensure consistency. For details, see "Setting the FEC Mode" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm in the case of a single wavelength.
2.
Step 4 Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board and the multiplexer/demultiplexer board is faulty. 1. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see "Replacing Fiber Jumpers" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4 of this alarm in the case of a single wavelength. Check whether the DCM used on the existing network is appropriate. If not, replace the DCM. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5 of this alarm in the case of a single wavelength.
2.
3.
Step 5 Cause 4 of this alarm in the case of a single wavelength: An inappropriate DCM is installed. 1. 2.
Issue 02 (2011-10-31)
Step 6 Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm is faulty. 1. Replace the board that reports this alarm. If ... The board supports pluggable optical modules, Then ... Replace the specific pluggable optical module. For details, refer to "Replacing Pluggable Optical Modules" of the Parts Replacement. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
The board does not support pluggable optical modules,
2.
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 6 of this alarm in the case of a single wavelength.
Step 7 Cause 6 of this alarm in the case of a single wavelength: The board at the opposite station is faulty. 1. Replace the OTU board at the opposite station. If ... The board supports pluggable optical modules, Then ... Replace the specific pluggable optical module. For details, refer to "Replacing Pluggable Optical Modules" of the Parts Replacement. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
The board does not support pluggable optical modules,
2.
Step 8 Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables between stations or the multiplexing portions inside a station are faulty. 1. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see "Replacing Fiber Jumpers" in the Supporting Tasks. If the fibers inside a station are normal, check the optical cables between stations to rectify the fault. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm in the case of multiple wavelengths.
2.
3.
Step 9 Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals during line transmission is excessively high. 1. Check the attenuation of the multiplexing portions inside a station and the line attenuation between stations section by section. If the preset attenuation values are excessively large, correct them so that they are within the normal range. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks.
Issue 02 (2011-10-31)
2.
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm in the case of multiple wavelengths.
Step 10 Cause 3 of this alarm in the case of multiple wavelengths: The external environment is improper. 1. Check the ambient temperature inside the telecommunications room, the cleanliness of the air filter, and the heat dissipation conditions of each fan. For details, see the procedure for handling the TEMP_OVER alarm. Check whether the alarm is cleared. If the alarm persists, check whether external electromagnetic interference exists. For example, whether there is external electronic equipment, whether the power supply is instable, and whether the lightning electromagnetic interference exists, or whether a high-voltage output cable generates electromagnetic interference. If yes, take corresponding measures to withstand the electromagnetic interference. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2.
3.
----End
Related Information
Related Cases: l l l l l l MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets Close to the Threshold MC-A55 Improper DCM Distribution Causes Abnormal Service and Bit Error Alarm BEFFEC_EXC Is Detected on the Newly-added LWFS Board MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board help/wdm/com/mc/tt_wdm_mc_0237.xml#tt_wdm_mc_0237 help/wdm/com/mc/tt_wdm_mc_0238.xml#tt_wdm_mc_0238 help/wdm/com/mc/tt_wdm_mc_0239.xml#tt_wdm_mc_0239
None.
3.3 BOOTROM_BAD
See the alarm page according to the type of the board that reports the alarm. Table 3-3 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm Page Link 3.3.1 BOOTROM_BAD (OCS) 3.3.2 BOOTROM_BAD (OTN)
3.3.1 BOOTROM_BAD (OCS)

Description
The BOOTROM_BAD (OCS) is an alarm indicating the BOOTROM data check failure. During the running of board software, the system periodically checks whether the BOOTROM data is damaged. This alarm is generated when the BOOTROM data is detected damaged.
Attribute
Alarm Severity Major Alarm Type Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the type of the BIOS damage. l 0x01: basic BIOS damaged l 0x02: extended BIOS damaged

l l If the board has been started, the BOOTROM_BAD alarm does not affect the system or the services. If you perform cold reset on the board when there is the BOOTROM_BAD alarm, the board fails to load BIOS and cannot be started.
Possible Causes
The possible causes of the BOOTROM_BAD alarm are as follows: l l l The basic BIOS is damaged. The extended BIOS is damaged. The BOOTROM data area is damaged.
Procedure
Step 1 View the BOOTROM_BAD alarm on the U2000 and determine the relevant board. Step 2 Replace the board. If the board has been started, do not replace the board. Replacing the board can interrupt services, whereas the BOOTROM_BAD alarm does not affect the system or the services. ----End
Related Information
None
3.3.2 BOOTROM_BAD (OTN)

Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data check fails. This alarm occurs when the basic or extended BIOS software of the board is damaged. Reported from the WDM side or client side: NA
Attribute
Alarm Severity Major Alarm Type Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Meaning
Parameters 1 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software. 0x02 indicates the extended BIOS software.

When powered on again or reset after a power supply failure, the SCC board cannot be normally started.
Fault Symptom
None
NOTE
Possible Causes
l l l
Issue 02 (2011-10-31)
Cause 1: The basic BIOS software of the board is damaged. Cause 2: The extended BIOS software of the board is damaged. Cause 3: The SCC board is faulty.
Procedure
l l Determine upon the alarm parameter (0x01 indicates the basic BIOS while 0x02 the extended BIOS) whether the basic or extended BIOS software of the board is damaged. Cause 1: The basic BIOS software of the board is damaged. 1. 2. l 1. 2. Replace the faulty SCC board. For details, refer to "Replacing the SCC Board" of the Parts Replacement. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers. Reload the extended BIOS of the SCC board. For details, see the Version Upgrade Guide. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
NOTE
Cause 2: The extended BIOS software of the board is damaged.
The BIOS detection interval is 24 hours. Therefore, the BOOTROM_BAD alarm is displayed 24 hours later if the alarm persists after you reload the extended BISO.
Cause 3: The SCC board is faulty. 1. 2. Replace the faulty SCC board. For details, refer to "Replacing the SCC Board" of the Parts Replacement. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
----End
Related Information
None
3.4 BUS_ERR
See the alarm page according to the type of the board that reports the alarm. Table 3-4 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm Page Link 3.4.1 BUS_ERR (OCS) 3.4.2 BUS_ERR (OTN)
3.4.1 BUS_ERR (OCS)
Issue 02 (2011-10-31)
227
Description
The BUS_ERR (OCS) is an alarm indicating the bus error. This alarm is generated when the board detects a backplane bus error.
Attribute
Alarm Severity Critical Alarm Type Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Parameters 2 and 3 Meaning Indicates the ID of slot that houses the cross-connect board. Indicates the statuses of buses.

l When the BUS_ERR alarm is reported, the services that pass through the relevant bus are interrupted or have bit errors.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows: l l l Cause 1: The internal bus of the cross-connect board is faulty. Cause 2: The software version does not match the specified version. Cause 3: The backplane or the relevant board is faulty.
Procedure
l l Query current alarms on the U2000. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The internal bus of the cross-connect board is faulty. 1. Replace the cross-connect board. For details, see the Parts Replacement.
Issue 02 (2011-10-31)
228
CAUTION
If no cross-connect board that works normally can be used for protection, do not perform the operations, because all the services may be interrupted. l Cause 2: The software version does not match the specified version. 1. Check whether the version of the cross-connect board matches the version of relevant service board. For details, see Querying the Version of the Board in the Supporting Task. If the versions of the cross-connect board and relevant service board do not match, contact Huawei engineers to upgrade the relevant boards. Perform cold reset on the service board that maps the cross-connect board by using the U2000, or reseat the service board that maps the cross-connect board. For the operations that are performed on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the operations of reseating the board, see the Installation Guide. Then, check whether the alarm is cleared. If the alarm persists, replace the service board. For details, see the Parts Replacement.
2. l
Cause 3: The backplane or the relevant board is faulty. 1.
2.
CAUTION
If the services that travel through the service board are not protected, do not perform the cold reset or replace the board because services may be interrupted. 3. 4. Perform cold reset on the cross-connect board by using the U2000, or reseat the crossconnect board. Then, check whether the alarm is cleared. If the alarm persists, replace the cross-connect board. For details, see the Parts Replacement. Then, check whether the alarm is cleared.
CAUTION
If no cross-connect board that works normally can be used for protection, do not perform the operations, because all the services may be interrupted. 5. If the alarm persists, contact Huawei engineers to check whether the fault is caused by bent pins of the backplane. If the backplane is faulty, replace the backplane of the subrack.
----End
Related Information
None
3.4.2 BUS_ERR (OTN)

Description
The BUS_ERR is an alarm indicating the bus error. This alarm is generated when the board detects a backplane bus error. Reported from the WDM side or client side: NA
Attribute
Alarm Severity Critical Alarm Type Equipment
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 and 2 Description Indicates the ID of the bus in which the alarm is generated.

l In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, this alarm triggers the bus switching. For example, if the bus from cross-connect board 9 contains a BUS_ERR alarm while the bus from cross-connect board 10 does not, services are switched to the bus from cross-connect board 10. Services are unavailable or bit errors are generated. For example, ODU1 and GE services of the OptiX OSN 6800 are affected and ODU1 and ODU0 services of the OptiX OSN 8800 are affected.
Fault Symptom
None
NOTE
Possible Causes
l l Cause 1: The OTU board is inserted inappropriately or faulty. Cause 2: In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, the crossconnect board is inserted inappropriately or faulty.
Issue 02 (2011-10-31)
l l
Cause 3: When ASON services are configured, the type of the service that is actually received does not match the service type configured on the board. Cause 4: The pins are faulty or the bus is faulty on the backplane.
Procedure
l Cause 1: The OTU board is inserted inappropriately or faulty. 1. Reseat the OTU board. For the operation of reseating the board, see the Installation Guide. In the case of the OptiX OSN 6800 equipment, see "Removing Boards" and "Inserting Boards". In the case of the OptiX OSN 3800 equipment, see "Removing Boards" and "Inserting Boards".In the case of the OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting Boards". . Check whether the alarm is cleared. If the alarm persists, replace the board. For details, see the Parts Replacement.
2. l
Cause 2: In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, the crossconnect board is inserted inappropriately or faulty. 1. 2. Reseat the cross-connect board. For operations, see Removing Boards in the Installation Guide and Inserting Boards in the Installation Guide. Check whether the alarm is cleared. If the alarm persists, replace the cross-connect board. For details, see the Parts Replacement.
Cause 3: When ASON services are configured, the type of the service that is actually received does not match the service type configured on the board. 1. Check whether board that reports this alarm supports pluggable optical modules. If... Then...
2. l
Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4. Perform a cold reset on the faulty board through the U2000. If the alarm persists, replace the backplane of the subrack. For the detailed operations, contact Huawei engineers.
Cause 4: The pins are faulty or the bus is faulty on the backplane. 1. 2.
----End
Related Information
None
Issue 02 (2011-10-31)
231
3.5 CHAN_LOS
Description
The CHAN_LOS alarm indicates the single wavelength signal loss. The alarm is generated when the MCA (optical spectrum analyzer) board detects that the original channel is lost after it scans the optical spectrum. Reported from the WDM side or client side: NA.
Attribute
Parameters
None

l l The services of the related wavelength are unavailable. The MCA cannot monitor the optical spectrum performance of the wavelength related to the alarm.
Fault Symptom
None.
NOTE
Possible Causes
l Cause 1: The wavelength that needs to be monitored is not received. For example, in the following figure, 1 wavelength needs to be monitored as configured, but actually 1 wavelength is not accessed. The possible cause is that the fiber to the client or WDM side of the OTU1 is connected.
MCA M U X / D M U X M U X / D M U X
1 OTU1 2 OTU2 Client side WDM side
1 OTU3 2 OTU4 WDM side Client side
OA
OA
F I U
F I U
OA
OA
Station A
Station B
Issue 02 (2011-10-31)
232
l l l l l
Cause 2: The laser of the board at the opposite station is shut down. For example, the laser of OTU1 in the preceding figure is shut down. Cause 3: The optical power difference between the monitored wavelengths is excessively large. (For example, the optical power difference between 1 and 2 is excessively large.) Cause 4: The attenuation of the multiplexer or OA unit interconnected with the MCA is excessively high. Cause 5: The OTU board located before the MCA is faulty. For example, OTU1 in the preceding figure is faulty. Cause 6: The MCA that reports the alarm is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The wavelength that needs to be monitored is not received. 1. Check whether the wavelength where the alarm is generated is required in the actual network. If not, modify the wavelength monitoring configuration of the MCA so that the monitoring of the wavelength is disabled. If the wavelength needs to be accessed in the actual network, check the fiber connection in the upstream stations along the signal flow so that the fiber connection is established properly. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Check whether the laser of the OTU that transmits the wavelength is shut down. If the laser is shut down, opening the Laser. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
2.
3. l
Cause 2: The laser of the board at the opposite station is shut down. 1. 2.
Cause 3: The optical power difference between the monitored wavelengths is excessively large. 1. Query whether the system is configured with the APE function. If yes, enable the APE function to re-adjust the optical power of each wavelength. For detailed operations, see "Automatic Power Equilibrium (APE)" in the Feature Description. If the system is not configured with the APE function, manually enable the adjustment of a single wavelength and adjust the optical power of the wavelength with excessively large difference, ensuring that the optical power is flat. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4.
2.
3. l
Cause 4: The attenuation of the multiplexer or OA unit interconnected with the MCA is excessively high. 1. Query the output optical power of the upstream OTU board connected to the multiplexer unit. Check whether the output optical power of the upstream OTU board is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
Issue 02 (2011-10-31)
233

NOTE
2.
Query the alarms reported by the MCA input optical power of the optical interface, and then calculate the output optical power of the upstream multiplexer or OA unit to determine whether it is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.If the optical power is extremely low or there is no light, check the attenuation that is set for the input optical power on the multiplexer or OA unit. If the attenuation is very high, decrease the attenuation for the multiplexer or OA unit.
NOTE
Output optical power of the multiplexer or OA unit (dBm) = Input optical power at the IN port on the MCA (dBm) - 10lg("MON"/"OUT") (dBm). "MON"/"OUT" represents the split ratio of the MON port on the multiplexer or OA unit. For details, see "MON Interface Optical Split Ratio" in the Hardware Description.
3. l
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5. Replace the OTU that transmits the wavelength to the MCA. If ... Then ...
Cause 5: The OTU in the upstream direction of the MCA is faulty. 1.
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, 2. l Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 6. Use an optical spectrum analyzer to analyze the optical spectrum data of the corresponding optical interface on the MCA. If the data is normal, perform a cold reset on the MCA. If the alarm persists, replace the MCA that reports the alarm. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 6: The MCA that reports the alarm is faulty. 1.
2. 3. ----End
Related Information
None.
Issue 02 (2011-10-31)
234
3.6 CLIENT_PORT_PS
Description
The CLIENT_PORT_PS alarm indicates the client-side 1+1 protection switching. This alarm occurs when the client-side 1+1 protection group actuates switching in which the current channel switches to the protection channel from the working channel. Reported from the WDM side or client side: NA
Attribute
Alarm Severity Major Alarm Type Communication alarm
Parameters
None

When the client-side 1+1 protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the client-side 1+1 protection group might have faulty services that needs to be restored.
Fault Symptom
Table 3-5 lists the fault symptoms for the CLIENT_PORT_PS alarm. Table 3-5 Fault symptoms for the CLIENT_PORT_PS alarm Fault Symptom A protection switching is performed, but there is no alarm that can trigger a protection switching. A protection switching is performed, and the board on the working channel reports alarms that can trigger a protection switching. For details about the alarm information, see Table 3-6. Cause Cause 1: A user issues an external switching command such as forced switching or manual switching. Cause 2: The services of the working channel of the client-side 1+1 protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
NOTE
Issue 02 (2011-10-31)
235
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the client-side 1+1 protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the client-side 1+1 protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
Procedure
l Cause 1: A user issues an external switching command such as forced switching or manual switching. 1. On the U2000, query the switching state of the protection group. If the switching state is forced switching or manual switching, check whether the external switching operation is necessary. If the external switching operation is necessary, ignore the alarm. If the external switching operation is unnecessary, issue an external command to switch the current channel to the working channel, thus clearing the alarm.
2. 3. l
Cause 2: The services of the working channel of the client-side 1+1 protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported. 1. Query whether the related boards for configuring the protection group have alarms relevant to the services. If yes, handle the alarms by referring to the alarm handling procedure. For details about the alarm information, see Table 3-6. If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2.
3. ----End
Related Information
Table 3-6 lists the alarms that can trigger a protection switching. Table 3-6 Related Alarms R_LOF R_LOS R_LOC HARD_BAD OTUk_LOF OTUk_LOM
Issue 02 (2011-10-31)
OTUk_TIM ODUk_PM_AIS ODUk_PM_OCI ODUk_PM_LCK ODUk_PM_TIM REM_SF

IN_PWR_HIGH IN_PWR_LOW ODUk_PM_DEG ODUk_PM_EXC OTUk_DEG OTUk_EXC

236
OTUk_AIS
B1_EXC
REM_SD
For details, see "Client 1+1 Protection" in the Feature Description.
3.7 COMMUN_FAIL
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-7 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.7.1 COMMUN_FAIL (OCS) 3.7.2 COMMUN_FAIL (OTN)
3.7.1 COMMUN_FAIL (OCS)

Description
The COMMUN_FAIL (OCS) is an alarm indicating an inter-board communication failure. This alarm is reported when the communication between the SCC and other boards is interrupted.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table.
Issue 02 (2011-10-31)
237
Parameter
Description
Parameters 1 and 2 Indicates the ID of the channel in which the alarm is generated. For example, 0x00 0x01 indicates RS485 path 1. 0x00 0x02 indicates RS485 path 2. 0x00 0x03 indicates intra-board communication. 0x00 0x04 indicates the Ethernet emergency channel between subracks.

When the alarm is generated, the SCC cannot send commands or services to the board, or the board cannot work. In this case, the service cannot be configured or the protection switching becomes invalid. Thus, the new service becomes abnormal.
Possible Causes
The possible causes of the COMMUN_FAIL alarm are as follows: l l l Cause 1 of a single board reporting this alarm: The board is in the cold reset or warm reset state. Cause 2 of a single board reporting this alarm: The board is faulty. Cause 1 of multiple boards reporting this alarm: The service board AUX is faulty.
NOTE
If the communication ports between the AUX board and other boards are faulty, the service board reports the COMMUN_FAIL alarm while the standby SCC board does not report the alarm.
Cause 2 of multiple boards reporting this alarm: The SCC board or the cross-connect board is faulty.
NOTE
If the active SCC board is faulty, the active SCC board, standby SCC board, and service board report the COMMUN_FAIL alarm at the same time. If the cross-connect board is faulty, the communication in the 485 path is faulty. The cross-connect board and the service board report the COMMUN_FAIL alarm.
Procedure
l Query the alarm on the U2000. Then, determine the boards that report the alarm and corresponding alarm parameter. For details, see Querying the Current Alarms in the Supporting Task. Cause 1 of a single board reporting this alarm: The board status is cold reset or warm reset. 1. Check the board alarm indicator to see whether the status of the board that reports the alarm is cold reset or warm reset. Wait for 5 minutes if the status is cold reset or warm reset, and then check whether the alarm is cleared. For the description of the alarm indicators on the board, see Board Indicators in the Hardware Description. If the alarm persists, see Cause 2 of a single board reporting this alarm.
2. l
Issue 02 (2011-10-31)
Cause 2 of a single board reporting this alarm: The board is faulty.

1. l 1.
Replace the board that reports the alarm. For details, see the Parts Replacement. Check whether the AUX board reports the alarm that indicates a board or chip fault such as the BD_STATUS alarm. Reseat the board. For the operations of reseating a board, see the Installation Guide. Then, check whether the COMMUN_FAIL alarm is cleared. If the alarm persists, replace the board. For details, see the Parts Replacement. Then, check whether the COMMUN_FAIL alarm is cleared. If the alarm persists, see Cause 2 of multiple boards reporting alarm.
Cause 1 of multiple boards reporting this alarm: The service board AUX is faulty.
2. 3. l
Cause 2 of multiple boards reporting this alarm: The SCC board or the cross-connect board is faulty. 1. Check whether the active SCC board or the active cross-connect board reports the alarm such as the BD_STATUS or HARD_BAD alarm that indicates a board fault. Reseat the board. For the operations of reseating a board, see the Installation Guide. Then, check whether the COMMUN_FAIL alarm is cleared. If the alarm persists, replace the board. For details, see the Parts Replacement.
2. ----End
Related Information
None
3.7.2 COMMUN_FAIL (OTN)

Description
The COMMUN_FAIL is an alarm indicating an inter-board communication failure. This alarm occurs when the communication between the SCC and other boards is interrupted. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 Description Indicates the optical port number and the value is always 0x01.
Issue 02 (2011-10-31)
239
Parameter
Description
Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. For example, 0x00 0x01 denotes RS485 path 1; 0x00 0x02 denotes RS485 path 2; 0x00 0x03 denotes intra-board communication; 0x00 0x04 denotes the Ethernet emergency channel between subracks. 0x00 0x05 denotes the spi communication failure between the SCC board and AUX board. 0x00 0x06 denotes RS485 path 3; 0x00 0x07 denotes RS485 path 4;

After the alarm is generated, configuration data fails to be applied to other boards or other boards cannot function normally. The service configuration or protection switching may fail or the package loading may roll back abnormally. Thus, new services become abnormal.
Fault Symptom
Table 3-8 lists the fault symptom for the COMMUN_FAIL alarm. Table 3-8 Fault symptom for the COMMUN_FAIL alarm Fault Symptom A single board reports the COMMUN_FAIL alarm. The alarm parameter is 0x01 0x00 0x03. l The board also reports the BD_STATUS alarm (only when the board is in cold reset state). l The PROG indicator on the board blinks first at the frequency of 300 ms on and 300 ms off (green) and then at the frequency of 100 ms on and 100 ms off (green). No other symptoms occur. Cause 3 of a single board reporting this alarm: The board is faulty. Cause Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset state.
Issue 02 (2011-10-31)
240
Fault Symptom A single board reports the COMMUN_FAIL alarm. The alarm parameter is 0x01 0x00 0x01 or 0x01 0x00 0x02. The SCC board of a slave subrack reports the COMMUN_FAIL alarm. The alarm parameter is 0x01 0x00 0x04. Multiple boards report the COMMUN_FAIL alarm. The alarm parameter is 0x01 0x00 0x03. The network cables for cascading subracks are selfmade network cables rather than standard straightthrough cables with all eight cores being used. l The standby SCC board does not report the COMMUN_FAIL alarm. l For OptiX OSN 6800 and OptiX OSN 3800: The AUX board reports the BD_STATUS alarm. l For OptiX OSN 8800: The EFI1 or EFI2 board reports the BD_STATUS alarm. l The boards that report the COMMUN_FAIL alarm are housed in slave subracks. l The SUBRACK_LOOP alarm is generated on the NE, or the SUBRACK_ID_CONFLICT or SUBRACK_ID_MISMATCH alarm is generated in the housing subracks of the boards that report the COMMUN_FAIL alarm. No other symptoms occur.
Cause Cause 3 of a single board reporting this alarm: The board is faulty.
Cause 2 of a single board reporting this alarm: The network cables for cascading subracks do not meet the requirements. Cause 1 of multiple boards reporting this alarm: For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
Cause 2 of multiple boards reporting this alarm: The settings of the DIP switches of the subracks are incorrect or the subracks are cascaded inappropriately.
Issue 02 (2011-10-31)
241
Fault Symptom l The active and standby SCC boards report the COMMUN_FAIL alarm at the same time. l The active SCC board also reports alarms such as HARD_BAD and BD_STATUS, indicating abnormal equipment status. Multiple boards report the COMMUN_FAIL alarm. The alarm parameter is 0x01 0x00 0x01 or 0x01 0x00 0x02. l The cross-connect board reports the COMMUN_FAIL alarm. l The cross-connect board also reports alarms such as BD_STATUS, indicating abnormal equipment status.
Cause Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
NOTE
Possible Causes
The possible causes of a single board reporting the COMMUN_FAIL alarm are as follows: l l l Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset state. Cause 2 of a single board reporting this alarm: The network cables for cascading subracks do not meet the requirements. Cause 3 of a single board reporting this alarm: The board is faulty.
The possible causes of multiple boards reporting the COMMUN_FAIL alarm are as follows: l Cause 1 of multiple boards reporting this alarm: For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
NOTE
When the ports on the AUX board for communicating with other boards are faulty, the services boards report the COMMUN_FAIL alarm but the standby SCC board does not report this alarm.
l l
Cause 2 of multiple boards reporting this alarm: The settings of the DIP switches of the subracks are incorrect or the subracks are cascaded inappropriately. Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
Issue 02 (2011-10-31)
242

NOTE
If the active SCC board is faulty, the active SCC board, standby SCC board, and service boards report the COMMUN_FAIL alarm at the same time. If the cross-connect board is faulty, the communication on channel 485 fails. In this case, the crossconnect board and service boards report the COMMUN_FAIL alarm at the same time.
Procedure
l Query the alarm on the U2000. Then, determine the boards that report the alarm and corresponding alarm parameter. For details, refer to "Querying the Current Alarms and Performance Events of a NE on the U2000" of the Supporting Tasks. Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset state. 1. View the alarm indicators of the board to check whether the board that reports this alarm is in warm reset or cold reset state. If yes, wait for five minutes and then check whether the alarm is cleared. For the description of the alarm indicators on the board, see the Hardware Description. If the alarm persists, see cause 2 of a single board reporting this alarm.
2. l
Cause 2 of a single board reporting this alarm: The network cables for cascading subracks do not meet the requirements. 1. Replace the network cables for cascading subracks with standard straight-through network cables with all eight cores being used. Then check whether the alarm is cleared. If the alarm persists, see cause 3 of a single board reporting this alarm. Replace the board that reports the alarm. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
2. l 1. 2. l
Cause 3 of a single board reporting this alarm: The board is faulty.
Cause 1 of multiple boards reporting this alarm: For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.. For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty. 1. Check whether the AUX board also reports alarms such as BD_STATUS, indicating abnormal board status. Reseat the board. For the operation of reseating the board, see the Installation Guide. In the case of the OptiX OSN 6800 equipment, see "Removing Boards" and "Inserting Boards". In the case of the OptiX OSN 3800 equipment, see "Removing Boards" and "Inserting Boards". Check whether the alarm is cleared. If the alarm persists, replace the AUX board. For details, refer to "Replacing the AUX Board" of the Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see cause 2 of multiple boards reporting this alarm.
2. 3.
For OptiX OSN 8800: The EFI1 or EFI2 board is faulty. 1. Check whether the EFI1 or EFI2 board also reports alarms such as BD_STATUS, indicating abnormal board status. Reseat the board. For the operation of reseating the board, see "Removing Boards" and "Inserting Boards" in the Installation Guide. Check whether the alarm is cleared. If the alarm persists, replace the EFI1 or EFI2 board. For details, refer to "Replacing the EFI Board" of the Parts Replacement.
2.
Issue 02 (2011-10-31)
3. l
Check whether the alarm is cleared. If the alarm persists, see cause 2 of multiple boards reporting this alarm.
Cause 2 of multiple boards reporting this alarm: The settings of the DIP switches of the subracks are incorrect or the subracks are cascaded inappropriately. 1. Check whether the SUBRACK_LOOP, SUBRACK_ID_CONFLICT, and SUBRACK_ID_MISMATCH alarms are generated. If yes, process these alarms in advance. Check whether the alarm is cleared. If the alarm persists, see cause 3 of multiple boards reporting this alarm. Check whether the active SCC or active cross-connect board also reports the BD_STATUS and HARD_BAD alarms. Reseat the board. For the operation of reseating the board, see the Installation Guide. In the case of the OptiX OSN 6800 equipment, see "Removing Boards" and "Inserting Boards". In the case of the OptiX OSN 3800 equipment, see "Removing Boards" and "Inserting Boards".In the case of the OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting Boards". Check whether the alarm is cleared. If the alarm persists, replace the relevant board. See For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
2. l
Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty. 1.
2. 3. ----End
Related Information
None
3.8 ETH_8B10B_ERR
Description
This alarm indicates an Ethernet line signal encoding/decoding error. The alarm occurs when signals are converted from 8bit mode to 10bit mode. Reported from the WDM side or client side: Client side
Attribute
Alarm Severity Minor Alarm Type Communication alarm
Parameters
None

The coding and encoding error of the signals on the Ethernet line may lead to the bit errors. If this alarm is consecutively generated for a long time, the service may be interrupted.
Fault Symptom
None.
NOTE
Possible Causes
l l l Cause 1: The fiber between the access equipment and the optical interface on the client side of the board is faulty. Cause 2: The access equipment is faulty. Cause 3: The board hardware is faulty.
Procedure
l Cause 1: The fiber between the access equipment and the optical interface on the client side of the board is faulty. 1. Check whether the attenuation of the fiber between the input equipment and the interface on the client side of the board is overlarge, and whether the fiber is aged or loose. If that is the case, clean the fiber connector or replace the fiber. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Apply a hardware loopback between the transmit and receive optical interfaces on the client side of the board. If the alarm persists, it indicates that the board is faulty. In this case, replace the board. If ... Then ...
2. l
Cause 2: The access equipment is faulty. 1.
2. l
If the alarm is cleared, it indicates that the access equipment on the client side is faulty. In this case, rectify the fault on the access equipment. Replace the faulty board. If ... Then ...
Cause 3: The board hardware is faulty. 1.
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement.
If ... The board does not support pluggable optical modules, 2. ----End
Then ... Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
If the alarm persists, contact Huawei for help.
Related Information
None.
3.9 EX_ETHOAM_CC_LOS
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-9 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.9.1 EX_ETHOAM_CC_LOS (OCS) 3.9.2 EX_ETHOAM_CC_LOS (OTN)
3.9.1 EX_ETHOAM_CC_LOS (OCS)

Description
The EX_ETHOAM_CC_LOS (OCS) alarm indicates the loss of the periodic continuity check (CC) message. When the sink maintenance point receives the CC message from the source maintenance point, the timer is started to periodically check the link between the source and sink maintenance points. If the sink maintenance point does not receive the CC message from the source maintenance point in one period (3.5 times the time the CC message is transmitted from the source maintenance point to the sink maintenance point), this alarm is generated.
Attribute
Alarm Severity Critical Alarm Type Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Meaning
Parameters 1 and 2 Indicates the VLAN ID, consisting of two bytes. Parameter 3 Parameters 4 to 7 Indicates the level of the maintenance domain, consisting of one byte. Indicates the ID of the local maintenance point, consisting of four bytes.
Parameters 8 to 12 Indicates the ID of the remote maintenance point, consisting of five bytes.

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

Description
This alarm indicates a loss of the periodic continuity check message. When the sink maintenance point receives the continuity check (CC) message from the source maintenance point, the timer
is started to periodically check the link between the source and sink maintenance points. If the sink maintenance point does not receive the CC message from the source maintenance point in one period (3.5 times of the time during which the CC message is transmitted from the source maintenance point to the sink maintenance point), this alarm is generated. Reported from the WDM side or client side: Client side
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description
Parameters 1 and 2 2 bytes, indicates the number of the Ethernet port where this alarm is generated. Parameters 3 and 4 2 bytes, indicates the VLAN ID. Parameter 5 Parameters 6 to 9 Indicates the level of the maintenance domain. 4 bytes, indicates the ID of the locate maintenance point.
Parameters 10 to 14 5 bytes, indicates the ID of the remote maintenance point.

When the EX_ETHOAM_CC_LOS alarm is generated, it indicates that a unidirectional connectivity failure is detected on the link between the source and the sink maintenance points.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
l l
Cause 1: A software or hardware failure occurs in the services from the source maintenance point to the sink maintenance point. Cause 2: Service congestion or service interruption occurs between the source maintenance point and the sink maintenance point.
Procedure
l Cause 1 and Cause 2: A software or hardware failure, service congestion or service interruption occurs between the source maintenance point and the sink maintenance point. 1. 2. 3. 4. View the EX_ETHOAM_CC_LOS alarm on the U2000 and confirm the ID of the relevant maintenance point according to the alarm parameters. Query the information about the maintenance point. Perform loopback (LB) for the source and sink maintenance points, to locate the fault in the services between the source maintenance point and the sink maintenance point. Perform checks for the problem services, including software check, hardware check, and traffic check. After the services restore, the alarm is automatically cleared. You may perform LB to confirm that the alarm is cleared. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
5. ----End
Related Information
None.
3.10 FC_LINK_ERR
Description
The FC_LINK_ERR alarm indicates an FC service link failure. This alarm occurs when the FC link is faulty. Reported from the WDM side or client side: Client side
Attribute
Parameters
Parameter Description Parameter 1 Indicates the status of the transmission link on the WDM side. It is used to identify the link status on a transmission network. l 0x00: means WAN_UP, indicating that the transmission link is normal. l 0x01: means WAN_DOWN, indicating that the transmission link is faulty. Parameter 2 Indicates the FCBB network status. When Parameter 1 is 0x01, it is a fixed value of 0xff; When Parameter 1 is 0x00, it indicates the FCBB link status, include, 0x01: Indicates that the protocol parameter ISL mode is incorrect, and the flow control management mode at the transmit end mismatches that at receive end. 0x02: Indicates that LEM state machine is not successfully closed. The LEM state machine can distinguish between Client and WAN. 0x03: Indicates that the GFPT_Link Init state is not completed. 0x04: Indicates that the ping/ping_Ack result and the configured Buffer water line do not match.

The services may be interrupted.
Fault Symptom
Table 3-10 lists the fault symptom for the FC_LINK_ERR alarm. Table 3-10 Fault symptom for the FC_LINK_ERR alarm Fault Symptom The WDM side of the opposite board may report an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or OTUk_AIS alarm. Cause Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
NOTE
Possible Causes
l Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
Issue 02 (2011-10-31)
l l l
Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow control management mode occurs. (The value of parameter 2 is 0x01.) Cause 3: The type or the time sequence of the services on the board is configured improperly. Cause 4: The type of the client-side optical module on the board mismatches the type of the actual service, or the actual fiber mismatches the fiber type that the optical module supports. Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04). Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
l l
Procedure
l l Check the information of this alarm on the U2000. Record the parameters of this alarm. Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.) 1. On the U2000, check whether an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or OTUk_AIS alarm is generated on the WDM side of the connected board. If yes, handle the alarm properly. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
2. l
Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow control management mode occurs. (The value of parameter 2 is 0x01.). 1. Check the alarm parameters to see whether the ISL mode is incorrect, or the flow control management mode mismatches. If yes, check the configuration of the client equipment in the network. Reconfigure the ISL mode and the traffic control management mode. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
2. 3. l
Cause 3: The type or the time sequence of the services on the board is configured improperly. 1. Check whether the service type of the OTU at the local station matches the type of the services transmitted from the client data equipment. If not, change the service type of the corresponding port on the board or replace the board with another board that matches the service type. For details, refer to "Replacing a Board" of the Supporting Tasks.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections configured on the board are in deactivation state.
2.
Check whether the rate that is configured for the services ports on the board where the alarm is generated matches the rate of the actually received services. If they do not match, you need to change the type of the accessed services or the type of the services configured on the board according to the networking planning, thus to ensure that the rates of these services are consistent. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4.
3. l
Cause 4: The type of the client-side optical module on the board mismatches the type of the actual service, or the actual fiber mismatches the fiber type that the optical module supports.
Issue 02 (2011-10-31)
1.
Check whether the service type that the client-side optical module on the board is the same with the actual service type. If not, replace the board or replace the optical module if it is pluggable to ensure the optical module type matches the actual service type. If ... Then ...
2.
If the alarm persists, check whether the fiber type supported by the client-side optical module is the same with the type of the connected fiber. If not, replace the board or the fiber. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. If ... Then ...
3. l
Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04). 1.
2. 3. l
If the alarm persists, the OTU board at the opposite station may be faulty. In this case, replace the faulty board. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 6. If the alarm persists, the client equipment may be faulty. In this case, rectify the fault on the client equipment. If the alarm persists, the client equipment at the opposite station may be faulty. In this case, rectify the fault on the client equipment at the opposite station. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02). 1. 2. 3.
----End
Related Information
None.
Issue 02 (2011-10-31)
252
3.11 FC_SYNC_LOS
Description
This alarm indicates a loss of the FC service synchronous word. This alarm is generated when the FC service state fails to obtain the signal alignment word. Reported from the WDM side or client side: Client side
Attribute
Parameters
None

Fault Symptom
Table 3-11 lists the fault symptom for the FC_SYNC_LOS alarm. Table 3-11 Fault symptom for the FC_SYNC_LOS alarm Fault Symptom The board reports an OUT_PWR_HIGH or OUT_PWR_LOW alarm. Cause Cause 2: The transmit optical power is abnormal.
NOTE
Possible Causes
The possible causes of the FC_SYNC_LOS alarm are as follows: l l
Issue 02 (2011-10-31)
Cause 1: The rate of the services receivable mismatches the rate of the services that are actually received. Cause 2: The transmit optical power is abnormal.
Procedure
l Cause 1: The rate of the services receivable mismatches the rate of the services that are actually received. 1. Check whether the rate that is configured on the U2000 of the services at the ports on the local board matches the rate of the accessed services. If they are not matched, you need to change the type of the accessed services or the type of the services on the board according to the networking planning, to ensure that the rates of these services are the same. The service type for an optical interface on the board can be set or queried on the U2000. For details, refer to "Querying and Setting the Service Type on the Client Side of a Board" of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. On the U2000, check whether the output optical power at the transmit end of the board is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the output optical power is abnormal, see the handling procedures for the OUT_PWR_HIGH and OUT_PWR_LOW alarms to rectify the fault. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2. l
Cause 2: The transmit optical power is abnormal. 1.
2. ----End
Related Information
None.
3.12 IN_PWR_HIGH
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-12 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.12.1 IN_PWR_HIGH (OCS) 3.12.2 IN_PWR_HIGH (OTN)
3.12.1 IN_PWR_HIGH (OCS)

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

After the IN_PWR_HIGH alarm is generated, the services at the optical interface may contain bit errors. Too high input power also causes damages to the laser.
Possible Causes
The possible causes of the IN_PWR_HIGH alarm are as follows: l l l l Cause of the threshold setting: The reference value or threshold of optical power is improper. Cause of the external line: The attenuation value of the optical attenuator is improper. Cause of the board: The board at the opposite station is faulty. As a result, the transmitting power of the opposite station is too high. Cause of the optical module: The type of the optical module is not correct.
Procedure
l l Query current alarms on the U2000. For details, see Querying the Current Alarms in the Supporting Task. Cause of the threshold setting: The reference value or threshold of optical power is not correct. 1. Check the type of the optical module on the board. You can obtain the manufacturer information about the optical module on the board through Querying Optical Module Information in the Supporting Task. Check whether the threshold of the optical power is set properly. For the operations, see Querying Optical Power of the Board in the Supporting Task. If the configured threshold is improper, re-set the input upper threshold according to the overload optical power of the board. For details on the optical power specifications of the board, see "Technical Specifications" of the Product Description. Then, check whether the alarm is cleared. If the alarm persists, see other causes.
2.
3. l
Cause of the external line: The configured attenuation value of the optical attenuator is improper. 1. On the U2000, check whether the receive optical power of the local end is within the normal range. For details, see Querying Optical Power of the Board in the Supporting Task. For details on optical power specification of the board, see "Technical Specifications" of the Product Description. For details, see Querying Optical Power of the Board in the Supporting Task.
Issue 02 (2011-10-31)

NOTE
2.
Check whether the attenuation value of the optical attenuator is correct if the receive optical power is excessively high. If the attenuation value is not correct, change the value according to the receive optical power specified for the board. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, see other causes.
3. l
Cause of the board: The transmit power of the opposite station is excessively high because the opposite board is faulty. 1. 2. Check whether the OUT_PWR_HIGH alarm exists at the opposite station. If the alarm exists, it indicates that the optical power transmitted by the opposite station is not standard. Replace the optical module on the board or the board at the opposite station. For details, see Replacing the Pluggable Optical Module in the Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, replace the opposite board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see other causes. Check whether the type of the optical module on the board is proper according to the transmission distance. For details on the mapping relationship between the optical module type and the transmission distance, see "Technical Specifications" of the Product Description. For details on the operation, see Querying Optical Module Information in the Supporting Task. If the type is not proper, replace the optical module or board with a proper optical module or board. For details, see Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace with the proper board. If the board supports pluggable optical modules, replace the board with a proper board. For details, see Parts Replacement. If the alarm persists, see other causes.
3. 4. l 1.
Cause of the optical module: The type of the optical module is not proper.
2.
3. ----End
Related Information
None.
3.12.2 IN_PWR_HIGH (OTN)

Description
This alarm indicates that the input optical power is excessively high. This alarm is generated when the input optical power is higher than the upper threshold of the input optical power. Reported from the WDM side or client side: WDM side, client side.
Issue 02 (2011-10-31)
256
Attribute
Parameters
None

When the input optical power is excessively high, bit errors and LOF alarms may be generated in the received signals, and the optical module on the board can be damaged. As a result, the services are affected.
Fault Symptom
None.
NOTE
Possible Causes
l l l l Cause 1 for this alarm generated on the client side: The input optical power is excessively high, and the attenuation configured is insufficient. Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 for this alarm generated on the WDM side: The output optical power of the board in the upstream station is excessively high. Cause 2 for this alarm generated on the WDM side: The board that reports this alarm is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for this alarm generated on the client side: The input optical power is excessively high, and the attenuation configured is insufficient. 1. If the alarm is generated on the client side, query the input optical power of the board that reports the alarm on the U2000 to check whether the input optical power is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the input power is abnormal as shown on the U2000, use a power meter to measure the input optical power of the board that reports the alarm to check whether the input optical power is within the normal range. If the input optical power is abnormal, increase the attenuation to a proper extent so that the input optical power is within the normal range.
Issue 02 (2011-10-31)

NOTE
2. l
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the client side. 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. If ... Then ...
Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty. 1.
2. l
Cause 1 for this alarm generated on the WDM side: The output optical power of the board in the upstream station is excessively high. 1. If the alarm is generated on the WDM side, query the input optical power of the board that reports the alarm on the U2000 to check whether the input optical power is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.. If the input optical power is abnormal, query the input and output optical power of the board in the upstream direction of the OTU in a reverse sequence of the signal flow on the U2000. If the input and output optical power of the upstream board exceeds the normal range, adjust the input optical power of the board to a proper value. If the input optical power of the upstream boards is within the normal range, whereas the output optical power is abnormal, the upstream board may be faulty. Replace the board. If ... Then ...
2.
3. l
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
Cause 2 for this alarm generated on the WDM side: The board that reports the alarm is faulty.
Issue 02 (2011-10-31)
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. If ... Then ...
If the alarm is generated in multiple wavelengths, the alarm handling method is similar to the handling method for this alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
3.13 IN_PWR_LOW
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-13 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.13.1 IN_PWR_LOW (OCS) 3.13.2 IN_PWR_LOW (OTN)
3.13.1 IN_PWR_LOW (OCS)

Description
The IN_PWR_LOW (OCS) alarm indicates excessively low input optical power. This alarm is generated when a board detects that the actual input power is lower than the lower threshold of the input power reference value.
Issue 02 (2011-10-31)
259
Attribute
Parameters
None

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

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

Description
This alarm indicates that the input optical power is excessively low. The alarm is generated when the input optical power is smaller than the lower threshold of the input optical power. Reported from the WDM side or client side: WDM side, client side.
Attribute
Parameters
None

If the input optical power is excessively low, bit errors may be generated in the received signals, which affect the normal receiving of the services.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the IN_PWR_LOW alarm are as follows: l l l l l l Cause 1 for this alarm generated on the client side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. Cause 2 for this alarm generated on the client side: The attenuation of the attenuator attached to the optical port on the board that reports this alarm is excessively high. Cause 3 for this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 for this alarm generated on the WDM side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. Cause 2 for this alarm generated on the WDM side: The attenuation of the attenuator attached to the optical port on the board that reports this alarm is excessively high. Cause 3 for this alarm generated on the WDM side: The attenuation attached to the transmit optical port on the board at the opposite station is excessively high, or the transmit optical module is faulty.
Issue 02 (2011-10-31)
l l
Cause 4 for this alarm generated on the WDM side: The attenuation in the transmission of the optical signals is excessively high and the compensation is insufficient. Cause 5 for this alarm generated on the WDM side: The board that reports this alarm is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for this alarm generated on the client side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. 1. Use an optical power meter to measure the input optical power of the local board to determine whether the input optical power is within the normal range. For details, refer to "Testing Optical Power by Using an Optical Power Meter" of the Supporting Tasks. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks to obtain the manufacturing information of the optical module on the board.
2.
If the detected power is excessively low, check the fiber connection. If the fiber connector is dirty, clean or replace the fiber connector. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged or aged, adjust the fiber jumper or replace the fiber jumper. For details, refer to "Replacing Fiber Jumpers" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
3.
4. l
Cause 2 for this alarm generated on the client side: The attenuation of the attenuator attached to the optical port 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 port is excessively high. If the attenuation is excessively high, decrease the attenuation value of the attenuator to a proper value or replace it with a suitable attenuator. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm generated on the client side. If the alarm persists, replace the board that reports the alarm. If ... Then ...
2. l
Issue 02 (2011-10-31)
263
2. l
Cause 1 for this alarm generated on the WDM side: The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged. 1. Use an optical power meter to measure the input optical power of the local board to determine whether the input optical power is within the normal range. For details, refer to "Testing Optical Power by Using an Optical Power Meter" of the Supporting Tasks. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks to obtain the manufacturing information of the optical module on the board.
2.
If the detected power is excessively low, check the fiber connection. If the fiber connector is dirty, clean or replace the fiber connector. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged or aged, adjust the fiber jumper or replace the fiber jumper. For details, refer to "Replacing Fiber Jumpers" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
3.
4. l
Cause 2 for this alarm generated on the WDM side: The attenuation of the attenuator attached to the optical port 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 port is excessively high. If the attenuation is excessively high, decrease the attenuation value of the attenuator to a proper value or replace it with a suitable attenuator. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm generated on the WDM side.
2. l
Cause 3 for this alarm generated on the WDM side: The attenuation attached to the transmit optical port on the board at the opposite station is excessively high, or the transmit optical module is faulty. 1. 2. Check the board at the opposite station. If the laser on the board is closed, open it on the U2000. For details, refer to "Opening/Closing Lasers" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, check whether the optical attenuator with excessively high attenuation is attached to the transmit optical port on the board at the opposite station. If yes, decrease the attenuation to a proper value or replace the optical attenuator so that the output optical power of the opposite board is normal. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, check the output optical power performance values and alarms of the board. If the reported alarms or performance values are different from the specification values, see the corresponding handling procedure for the alarms or performance events to rectify the fault. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4 of this alarm generated on the WDM side.
3.
4. l
Cause 4 for this alarm generated on the WDM side: The attenuation in the transmission of the optical signals is excessively high and the compensation is insufficient. 1. Query the input and output optical power of the boards in the upstream direction of the OTU at the local station in the reversed sequence of signal flow on the U2000.
Issue 02 (2011-10-31)
Locate the board with the very low optical power, and then adjust the input optical power of the board to a proper value. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. 2. Check the input and output optical power of the upstream stations one by one in the reversed sequence of signal flow on the U2000 and locate the faulty section where the optical power is excessively low. If the output optical power of the upstream station is normal, check the cables, fiber jumpers, fiber connectors, and attenuators; if the attenuation of the cables is higher than the attenuation in the engineering design, adjust the attenuator, rectify or change the cables; if the fiber jumper, fiber connector or the attenuator is dirty, clean or replace the fiber jumper, fiber connector or attenuator. For details, see the Supporting Tasks. If the output optical power of the upstream station is abnormal, troubleshoot the faults at the upstream station so that the output optical power is normal. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5 of this alarm generated on the WDM side.
3.
4. 5. l
Cause 5 for this alarm generated on the WDM side: The board that reports the alarm is faulty. 1. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. If ... Then ...
If the alarm persists, contact Huawei for help.
If the alarm is generated in multiple wavelengths, the alarm handling method is similar to the handling method for the alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB. Related Cases: l l l l l l MC-A19 Use Power Monitoring To Process Problems on IN_PWR_LOW Alarm MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm MC-A66 The Received Optical Power of Downstream Stations Is not Flat and Some Wavelengths Report the IN_PWR_LOW Alarm MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander MC-A201 Frequent Fiber Cut Results in High Line Attenuation and the IN_PWR_LOW Alarm Reported by the OTU Board MC-A217 An IN_PWR_LOW Alarm Is Reported After an Optical-Layer ASON Service Is Configured on the ASON OptiX OSN 6800 NE
Issue 02 (2011-10-31)
None.
3.14 INTRA_OTU_PS
Description
The INTRA_OTU_PS alarm indicates the intra-board 1+1 protection switching. This alarm occurs when the intra-board 1+1 protection group actuates switching in which the current channel switches to the protection channel from the working channel. Reported from the WDM side or client side: WDM side
Attribute
Parameters
None

When the intra-board 1+1 protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the intra-board 1+1 protection group might have faulty services that needs to be restored.
Fault Symptom
Table 3-14 lists the fault symptoms for the INTRA_OTU_PS alarm. Table 3-14 Fault symptoms for the INTRA_OTU_PS alarm Fault Symptom A protection switching is performed, but there is no alarm that can trigger a protection switching. A protection switching is performed, and the board on the working channel reports alarms that can trigger a protection switching. For details about the alarm information, see Table 3-15. Cause Cause 1: A user issues an external switching command such as forced switching or manual switching. Cause 2: The services of the working channel of the intra-board 1+1 protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
NOTE
Issue 02 (2011-10-31)
266
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the intra-board 1+1 protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the intra-board 1+1 protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
Procedure
2. 3. l
Cause 2: The services of the working channel of the intra-board 1+1 protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported. 1. Query whether the related boards for configuring the protection group have alarms relevant to the services. If yes, handle the alarms by referring to the alarm handling procedure. For details about the alarm information, see Table 3-15. If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2.
3. ----End
Related Information
Table 3-15 lists the alarms that can trigger a protection switching. Table 3-15 Related Alarms R_LOF R_LOS POWER_DIFF_OVER R_LOC OTUk_LOF OTUk_LOM OTUk_AIS ODUk_PM_AIS ODUk_PM_OCI ODUk_PM_LCK ODUk_LOFLOM B1_EXC IN_PWR_HIGH IN_PWR_LOW ODUk_PM_DEG ODUk_PM_EXC OTUk_DEG OTUk_EXC
Issue 02 (2011-10-31)
267
For details, see "Intra-Board 1+1 Protection" in the Feature Description.
3.15 LASER_MODULE_MISMATCH
Description
This alarm indicates a mismatch of the optical module type and the fiber type. This alarm is generated when the type of the optical module mismatches the type of the board. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

The LASER_MODULE_MISMATCH alarm results in that services cannot be normally received or transmitted. It can even cause service interruption.
Fault Symptom
None.
NOTE
Possible Causes
The possible cause of the LASER_MODULE_MISMATCH alarm is as follows: l Cause 1: The optical port type supported by the physical board does not match the type of the optical module inserted into the optical port.
Procedure
l Cause 1: The optical port type supported by the physical board does not match the type of the optical module inserted into the optical port. 1. Check whether the optical module inserted into the optical port matches the type of the optical port. For details, see "Quick Reference Table of the Units" in the Hardware Description. If not, replace the optical module with another one of the right type. For details, see "Replacing the Pluggable Optical Module" in the Parts Replacement.
2.
Issue 02 (2011-10-31)
3. ----End
Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Related Information
None.
3.16 LINK_ERR
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-16 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.16.1 LINK_ERR (OCS) 3.16.2 LINK_ERR (OTN)
3.16.1 LINK_ERR (OCS)

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

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

Description
This alarm indicates a link error. This alarm is generated when the link status of the Ethernet data port is down. Reported from the WDM side or client side: Client side
Attribute
Parameters
None

When the link status of the Ethernet ports is down, a valid link cannot be created between the two data ports and the data services are interrupted.
Fault Symptom
Table 3-17 lists the fault symptom for the LINK_ERR alarm. Table 3-17 Fault symptom for the LINK_ERR alarm Fault Symptom An IN_PWR_HIGH or IN_PWR_LOW alarm may be generated on both of the two interconnected boards. Cause Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or low.
NOTE
Possible Causes
l l Cause 1: The service type of the client equipment mismatches the service type of the interconnected OTU. Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports are inconsistent. For example, one port is in the auto-negotiation mode but the other is nonnegotiation. Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or low. Cause 4: The fiber or cable that connects the two Ethernet ports fails. Cause 5: The optical module types of the two interconnected Ethernet boards are inconsistent. Hence, the types of fibers that the two optical modules can be connected to are inconsistent. Cause 6: The data equipment on the client side is faulty. Cause 7: The board that reports this alarm is faulty.
l l l
l l
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The service type of the client equipment mismatches the service type of the interconnected OTU. 1. Check whether the service type of the OTU at the local station matches the type of the services transmitted from the client data equipment. If not, change the service type of the corresponding port on the board or replace the board with another board that matches the service type. For details, refer to "Replacing a Board" of the Supporting Tasks.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections configured on the board are in deactivation state.
2.
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
Issue 02 (2011-10-31)
Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports are inconsistent. 1. Check whether the auto-negotiation mode of the optical port on the board that reports the alarm is consistent with that of the client data equipment. If they are inconsistent, modify the setting to ensure the consistency. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
2. l
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively high or low. 1. Check whether the input optical power of the two interconnected Ethernet ports is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
2. 3. l
If the input optical power is abnormal, see the handling procedures for the IN_PWR_HIGH or IN_PWR_LOW alarm. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4. Check whether the fiber or cable that connects the two Ethernet ports are properly connected. If they are not properly connected, reconnect or replace the fiber or cable. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5.
Cause 4: The fiber or cable that connects the two Ethernet ports fails. 1. 2.
Cause 5: The optical module types of the two interconnected Ethernet boards are inconsistent. Hence, the types of fibers that the two optical modules can be connected to are inconsistent. 1. Check whether the types of fibers that the two optical modules can be connected to are consistent. If they are inconsistent, replace the fiber or either board to make the type of the two optical modules match the fiber type. If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, 2. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
If the alarm persists, check whether the optical module types of the two interconnected boards match the type of the fiber that connects the two boards. If not, replace the board whose optical module type does not match the fiber board. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 6.
3. l
Issue 02 (2011-10-31)
Cause 6: The data equipment on the client side is faulty.

1.
Apply a hardware loopback between the transmit and receive optical ports on the client side of the board. If the alarm persists, it indicates that the OTU at the local station is faulty. For details, see the alarm handling procedure for cause 7. If the alarm is cleared, it indicates that the data equipment on the client side is faulty. In this case, rectify the fault on the data equipment. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 7. Perform a cold reset on the faulty board through the U2000. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. If ... Then ...
2. 3. l
Cause 7: The board that reports the alarm is faulty. 1. 2.
3. ----End
Related Information
Related Cases: l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides. The LOG board reports the R_LOS alarm on the client side. The FDG board reports the LINK_STATUS alarm. MC-A102 The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS Alarm MC-A128 EPL Service Was Interrupted Due To a Service Mode Mismatch of L4G Boards and Nodes Report R_LOF, ODU5G_PS_AIS, OTU5G_LOF, LINK_ERR Alarm
l l
None.
3.17 LOOP_ALM
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-18 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH
Issue 02 (2011-10-31)
Alarm page link 3.17.1 LOOP_ALM (OCS)
273
Board Type Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH
Alarm page link 3.17.2 LOOP_ALM (OTN)
3.17.1 LOOP_ALM (OCS)

Description
The LOOP_ALM (OCS) alarm indicates a loopback. Loopback is classified into optical interface loopback and VC-4 channel loopback. This alarm is generated when service loopback is set.
Attribute
Alarm Severity Minor Alarm Type Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the status of loopback. The values are as follows: l 0x00: Non-Loopback. l 0x01: Inloop. l 0x02: Outloop.

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

Description
This alarm indicates that a loop is generated. The alarm is generated when the optical port of the board is in the loopback status. Reported from the WDM side or client side: WDM side, client side.
Attribute
Parameters
Parameters 1 and 2 Indicates the optical port where this alarm is generated. For example, 0x00 0x01 indicates optical port 1. Parameter 3 Indicates the loopback type. l 0x00: Inloop l 0x01: Outloop

Services are interrupted.
Fault Symptom
None.

NOTE
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows: l Cause 1: The loopback command is issued during testing or maintenance.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The loopback command is issued during testing or maintenance. 1. Check whether the loopback is set on the optical port during testing or maintenance. After the test or maintenance is complete, release the loopback configured for the specific optical port. For details, refer to "Performing Inloop and Outloop" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2. ----End
Related Information
None.
3.18 LPT_ACTIVE
Description
This alarm indicates that the LPT switching is active. The data equipment itself has protection scheme. Hence, the protection provided by the WDM equipment is not needed. However, the WDM equipment is needed for informing the data equipment about the faults in the transmission layer. In this way, the switching would be triggered for the data equipment. The alarm is generated when switching is triggered. Reported from the WDM side or client side: Client side
Attribute
Parameters
None.

When the alarm is generated, services will be interrupted if no protection route exists. If there is alternative route, the services would automatically search the protection route for automatic restoration. And a prompt would be generated to remind user to remove the fault.
Fault Symptom
Table 3-19 lists the fault symptoms for the LPT_ACTIVE alarm. Table 3-19 Fault symptoms for the LPT_ACTIVE alarm Fault Symptom The R_LOS, LINK_ERR or L_SYNC alarm may be generated on the client side of the board. An REM_SF alarm may be generated on the client side of the board. Cause Cause 1: The input signals on the client side are missing or the local board detects a LINK_ERR or L_SYNC alarm. Cause 2: An REM_SF alarm is generated on the client side of the local board because equipment at the opposite station malfunctions. Cause 3: When the WDM equipment accesses data services and the OTN frames are transmitted on the WDM side, this alarm may be triggered by the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI, or ODUk_TCMn_LCK alarm on the WDM side. Cause 4: When the WDM equipment accesses data services and the SDH frames are transmitted on the WDM side, this alarm may be triggered by the R_LOS or R_LOF alarm on the WDM side. Cause 3 or cause 4
The OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI, or ODUk_TCMn_LCK may be generated on the WDM side of the board.
An R_LOF alarm may be generated on the WDM side.
An R_LOS alarm may be generated on the WDM side.
NOTE
Possible Causes
l l Cause 1: The input signals on the client side are missing or the local board detects a LINK_ERR or L_SYNC alarm. Cause 2: An REM_SF alarm is generated on the client side of the local board because equipment at the opposite station malfunctions.
Issue 02 (2011-10-31)
Cause 3: When the WDM equipment accesses data services and the OTN frames are transmitted on the WDM side, this alarm may be triggered by the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI, or ODUk_TCMn_LCK alarm on the WDM side. Cause 4: When the WDM equipment accesses data services and the SDH frames are transmitted on the WDM side, this alarm may be triggered by the R_LOS or R_LOF alarm on the WDM side. Cause 5: Regarding to separation of the tributary board from the line board, if the crossconnection configuration does not exist, the alarm is generated.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Check whether the service type accessed by the WDM equipment and the frame format transmitted on the WDM side is consistent with that of the service configuration model by using the U2000. If they are not consistent, configure them to ensure the consistency. Cause 1: The input signals on the client side are missing or the local board detects a LINK_ERR or L_SYNC alarm. 1. 2. l Check whether the R_LOS, LINK_ERR or L_SYNC alarms are generated on the client side. If that is the case, clear the R_LOS, LINK_ERR or L_SYNCalarm. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
Cause 2: An REM_SF alarm is generated on the client side of the local board because equipment at the opposite station malfunctions. 1. 2. Check whether an REM_SF alarm is generated on the client side. If that is the case, clear the REM_SF alarm. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
Cause 3: When the WDM equipment accesses the data services and the OTN frames are transmitted on the WDM side, the alarm may be triggered by the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI or ODUk_TCMn_LCK alarm on the WDM side. 1. If the frames on the WDM side are transmitted in the OTN format, check whether there are R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI or ODUk_TCMn_LCK alarms. If yes, clear the alarms. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4.
2. l
Cause 4: When the WDM equipment accesses the data services and the SDH frames are transmitted on the WDM side, the alarm may be triggered by the R_LOS or R_LOF alarm on the WDM side. 1. 2. If the frames on the WDM side are transmitted in the SDH format, check the R_LOS or R_LOF alarm information on the U2000 and clear the alarm. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5.
Cause 5: Regarding to separation of the tributary board from the line board, if the crossconnection configuration does not exist, the alarm is generated.
Issue 02 (2011-10-31)
1.
Check the trails of the cross-connect services according to the board that reports the alarm. Regarding to separation of the tributary board from the line board, check whether the cross-connection is configured on the U2000. If not, configure the crossconnection. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2. ----End
Related Information
As a link-based protection scheme, link pass through (LPT) provides the required network-level protection for point-to-point private line services by means of point-to-point link pass through.For details, see "LPT(OTN)" in the Feature Description.
3.19 LSR_WILL_DIE
Description
This alarm indicates that the laser will be out of work. Reported from the WDM side or client side: WDM side, client side.
Attribute
Parameters
None

The laser is aging, and therefore the quality of the output optical signals and the received signals is decreased (for example, the optical power is lower or is unstable). The impact depends on the aging level of the laser.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the LSR_WILL_DIE alarm are as follows: Cause 1: The laser is aging. The service life of the laser would be terminated.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser is aging. The service life of the laser would be terminated. 1. Check whether the board that reports this alarm supports pluggable optical modules. If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, Replace the board. For details, refer to "Replacing a Board" of the Supporting Tasks.
2. l
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 2: The detection circuit of the board is faulty. 1. 2.
----End
Related Information
None.
3.20 MS_AIS
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-20 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.20.1 MS_AIS (OCS) 3.20.2 MS_AIS (OTN)
3.20.1 MS_AIS (OCS)

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

l l When the MS_AIS alarm is generated, the services are interrupted. After the MS_AIS alarm is generated, the board automatically returns the MS_RDI alarm to the opposite station. Consequently, the opposite station reports the MS_RDI alarm.
Possible Causes
The possible causes of the MS_AIS alarm are as follows: l l l Cause 1: The receive board at the local station is faulty. Cause 2: The working and protection cross-connect boards at the opposite station are not in position or are faulty. Cause 3: The transmit board at the opposite station is faulty.
Procedure
l Query current alarms on the U2000. Determine the ID of the interface that reports the alarm according to alarm parameter 1. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The receive board at the local station is faulty. 1. Perform a cold reset on the receive board at the local station. For the operations that are performed on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the operations of reseating a board, see the Installation Guide. Then, check whether the alarm is cleared.
CAUTION
If the services that pass the board are not configured with protection, the services are interrupted after you perform a cold reset on the board.
Issue 02 (2011-10-31)
281
2. 3. l
If the alarm persists, replace the board that reports the alarm. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see cause 2.
Cause 2: The working and protection cross-connect boards at the opposite station are not in position or are faulty. 1. Check the board alarm indicator to see whether the status of the cross-connect board status is cold reset or warm reset. Wait for 5 minutes, and then check whether the alarm is cleared. For the description of the alarm indicators on the board, see Board Indicators in the Hardware Description. If the alarm persists, check whether the working and protection cross-connect boards at the opposite station are loose. If yes, tighten the working and protection crossconnect boards. For details, see the Installation Guide. Then, check whether the alarm is cleared. If the alarm persists, replace the cross-connect board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see cause 3. If the alarm persists, replace the opposite board. For details, see Parts Replacement.
2.
3. 4. l 1. ----End
Cause 3: The transmit board at the opposite station is faulty.
Related Information
None.
3.20.2 MS_AIS (OTN)

Description
This alarm is a multiplex section alarm indication. The alarm is generated when the input signals from the client side contain the MS_AIS signal or the receive side of the local station is faulty. Reported from the WDM or client side: client side. l client side: In this case, the type of the service received on the client side is SDH.
Attribute
Parameters
None

The services are faulty.
Fault Symptom
None.
NOTE
Possible Causes
l Cause 1 : The input signals from the client side contain the MS_AIS signal, as shown in the following figure.
Detects and reports the MS_AIS alarm
The client signals contain the MS_AIS signal

Client side
OTU1
WDM side
O A D M
F I U
F I U
O A D M
OTU2
WDM side Client side
Station A
Station B
Cause 2 : The board that reports the alarm is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 : The input signals from the client side contain the MS_AIS signal 1. Apply a hardware loopback between the transmit and receive optical ports on the client side of OTU1. If the alarm on OTU1 persists, it indicates that OTU1 is faulty. In this case, see the alarm handling procedure for cause 2. If the alarm is cleared, it indicates that the input signals on the client side contain bit errors. In this case, rectify the fault on the client equipment. If the alarm persists, the board that reports the alarm is faulty. Replace the board. If ... Then ...
2. l
Cause 2: The board that reports the alarm is faulty. 1.
2. ----End
Issue 02 (2011-10-31)
283
Related Information
None.
3.21 MS_RDI
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-21 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.21.1 MS_RDI (OCS) 3.21.2 MS_RDI (OTN)
3.21.1 MS_RDI (OCS)

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

When the MS_RDI alarm is generated, the local station is not affected. This alarm just shows that the services at the opposite station are interrupted.
Possible Causes
The possible causes of the MS_RDI alarm are as follows: l
Issue 02 (2011-10-31)
Cause 1: The opposite station receives the R_LOS and MS_AIS alarms.
l l
Cause 2: The transmit board at the local station is faulty. Cause 3: The receive board at the opposite station is faulty.
Procedure
l l Query current alarms on the U2000. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The opposite station receives the R_LOS and MS_AIS alarms. 1. On the U2000, check whether the service interruptions or bit error alarms, such as R_LOS, R_LOF, MS_AIS, B2_EXC, and B2_SD exist at the opposite station. If yes, clear these alarms first. Then, check whether the MS_RDI alarm is cleared. If the alarm persists, see cause 2. Perform a cold reset on the transmit board at the local station. For the operations on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the operations of reseating a board, see the Installation Guide. Then, check whether the alarm is cleared.
2. l 1.
Cause 2: The transmit board at the local station is faulty.
CAUTION
If the services that pass the board are not configured with protection, the services are interrupted after you perform a cold reset on the board. 2. 3. l 1. If the alarm persists, replace the transmit board at the local station. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see cause 3. Perform a cold reset on the receive board at the opposite station. For the operations on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the operations of reseating a board, see the Installation Guide. Then, check whether the alarm is cleared.
Cause 3: The receive board at the opposite station is faulty.
CAUTION
If the services that pass the board are not configured with protection, the services are interrupted after you perform a cold reset on the board. 2. ----End If the alarm persists, replace the receive board at the opposite station. For details, see Parts Replacement.
Related Information
None.
3.21.2 MS_RDI (OTN)

Description
This alarm is a multiplex section remote defect indication. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDMside receive part of the opposite station is faulty (for example, the R_LOS, R_LOF or MS_AIS alarm is generated). Reported from the WDM or client side: WDM side, client side l l WDM side: In this case, the type of the service received on the WDM side is SDH. Client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Parameters
None

l l If the alarm is reported from the WDM side, the services may be interrupted. If the alarm is reported from the client side, the client-side services are faulty.
Fault Symptom
Table 3-22 lists the fault symptom for the MS_RDI alarm. Table 3-22 Fault symptom for the MS_RDI alarm Fault Symptom The board at the opposite station reports an R_LOS, R_LOF, or MS_AIS alarm. Cause Cause 1 for this alarm generated on the WDM side: The receiver on the WDM side at the opposite station detects a signal failure.
NOTE
Possible Causes
l Cause 1 for this alarm generated on the client side: For the OTU board whose client side supports the SDH services, the input signals from the client side contain the MS_RDI signal. As shown in the following figure, the input signals from the client side of the OTU board
Issue 02 (2011-10-31)
at the local station A contain the MS_RDI signals. The OTU of the station A reports the MS_RDI alarm on the client side after it detects the MS_RDI signals.
Detects and reports the MS_RDI alarm
The client signals contain the MS_RDI signal Client side O T U WDM side WDM side O T U Client side
Station A
Station B
Cause 1 for this alarm generated on the WDM side: The receiver on the WDM side at the opposite station detects a signal failure. (For example, an R_LOS, R_LOF, or the MS_AIS alarm is generated.) As shown in the following figure, the WDM side of the OTU board in station B (the opposite station) sends the MS_RDI signals back to station A (the local station) after it detects and reports the R_LOS, R_LOF or the MS_AIS alarm. The WDM side of the OTU board in station A reports the MS_RDI alarm after it detects the MS_RDI signals.
Detects and reports the R_LOS, R_LOF, MS_AIS alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the MS_RDI alarm
Station B Sends the MS_RDI signal back
Cause 2 for this alarm generated on the WDM side: The board that reports the alarm is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for this alarm generated on the client side: In the case of the OTU board of which the client side supports the SDH service, the input signals from the client side contain the MS_RDI signal. 1. When the MS_RDI alarm is reported from the client side, rectify the fault on the client equipment connected to the OTU board. For details, see the related manual of the client equipment.
Issue 02 (2011-10-31)
287
Cause 1 for the alarm generate on the WDM side: The receiver on the WDM side at the opposite station detects a signal failure (for example, an R_LOS, R_LOF or the MS_AIS alarm is generated). 1. Query the alarm of the board at the opposition station by using the U2000. If and R_LOS, R_LOF or MS_AIS alarm exists, see the handling procedure of the R_LOS, R_LOF, or MS_AIS alarm for troubleshooting. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
2. l
Cause 2 for this alarm generated on the WDM side: The board that reports the alarm is faulty. 1. If the alarm persists, the board at the local station is faulty. Consider whether to replace the faulty board according to the actual situation (for example, whether replacing the board affects the services). If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, 2. ----End Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
Related Information
None.
3.22 MUT_LOS
Description
This alarm indicates a loss of multiplexed signals. This alarm is generated when the input multiplexed signals of the board are lost. Reported from the WDM side or client side: NA
Attribute
Parameters
None

The services through the optical port where this alarm is generated are interrupted.
Fault Symptom
Table 3-23 lists the fault symptom for the MUT_LOS alarm. Table 3-23 Fault symptom for the MUT_LOS alarm Fault Symptom The optical ports on the board that reports this alarm are disconnected. Cause Cause 1: Certain optical ports on the board that reports this alarm are disconnected or the fibers connected to the optical ports are damaged.
NOTE
Possible Causes
l l l Cause 1: Fibers connected to certain optical ports at the receive end of the board that reports the alarm are not connected, incorrectly connected, or damaged. Cause 2: The attenuation of signals during line transmission is excessively high. Cause 3: The board that reports the alarm is faulty.
Procedure
l l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. On the U2000, check whether the boards on the multiplexing link in the upstream direction report this alarm along the reverse direction of the signal flow. Cause 1: Fibers connected to certain optical ports at the receive end of the board that reports the alarm are not connected, incorrectly connected, or damaged. 1. Check whether there are fibers connected to certain optical ports at the receive end of the board that reports the alarm are not connected or incorrectly connected. If yes, connect the input optical fibers to the specific optical port. Check whether the fibers or fiber connectors on the board that reports this alarm are dirty. If yes, see Checking Fiber Jumpers by Using an Optical Power Meter or Replacing Fiber Jumpers to rectify the fault. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Use an optical power meter to measure the actual receive optical power of the board that reports the alarm. Check whether the receive optical power is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
2.
3. l
Cause 2: The attenuation of signals during line transmission is excessively high. 1.
Issue 02 (2011-10-31)

NOTE
2.
If the receive optical power is excessively low, check whether an optical attenuator with excessively high attenuation is attached to the receive optical port on the board. If yes, decrease the attenuation of the optical attenuator to a proper value or replace the optical attenuator with a proper one. If the alarm persists, check whether the attenuation of the built-in VOA in the upstream board is excessively high. If yes, adjust the attenuation of the VOA to a proper value. Check whether the alarm is cleared. If the alarm persists, the optical cables between stations may be faulty. In this case, rectify the fault on the optical cables. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3. If the alarm persists, the board that reports the alarm may be faulty. Replace the board. If ... Then ...
3. 4. 5. l
2. ----End
Related Information
Related Cases: l l l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS MC-A151 OWSP Protection Switching Fails Due to Incorrect Connection of Fiber Jumpers On The DCP Boards, DCP Boards Report The MUT_LOS Alarms And TDG Board Reports The OPU1_PLM Alarm MC-A182 Receive Optical Power Is Excessively Low Because of The End Face Problem of the Fiber Jumper, The OAU Board Reports The MUT_LOS And R_LOS Alarms MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board Causes Low Receive Optical Power, The Connected OAU Board At The Downstream Station Reports MUT_LOS And R_LOS Alarms help/wdm/com/mc/tt_wdm_mc_0245.xml#tt_wdm_mc_0245
l l
None.
Issue 02 (2011-10-31)
290
3.23 OA_LOW_GAIN
Description
This alarm indicates that the gain of an optical amplifier is low. The alarm is generated when the actual gain of the optical amplifier board is 3 dB lower than the standard gain. Reported from the WDM side or client side: NA
Attribute
Alarm Severity Critical Alarm Type Service alarm
Parameters
None

The alarm caused by different factors has different impacts on the system: l l If the alarm is generated because the input optical power is excessively high, the redundancy of the system decreases, which affects the subsequent capacity expansion. If the alarm is caused by other factors (for example, excessive insertion loss between the TDC and RDC optical ports on an OAU board), the input optical power of the downstream signals and the redundancy of the system decrease. The services may have bit errors or even be interrupted.
Fault Symptom
Table 3-24 lists the fault symptom for the OA_LOW_GAIN alarm. Table 3-24 Fault symptom for the OA_LOW_GAIN alarm Fault Symptom The OAU board that reports this alarm also reports a power high alarm, such as SUM_INPWR_HI. Cause Cause 1: The input optical power of the OAU board is excessively high.
NOTE
Issue 02 (2011-10-31)
291
Possible Causes
The possible causes of the OA_LOW_GAIN alarm are as follows: l l l Cause 1: The input optical power of the board is excessively high. Cause 2: This alarm may be generated because the insertion loss between the TDC and RDC optical ports is excessively high. (This cause is applicable only to the OAU board.) Cause 3: The board that reports the alarm is faulty.
Procedure
l Cause 1: The input optical power of the board is excessively high. 1. On the U2000, check whether the receive optical power of the board is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the input optical power is not within the normal range, adjust the optical attenuator attached to the input optical port so that the input optical power meets the specification requirement. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. If no optical attenuator is attached to the input optical port, add an optical attenuator to ensure that the input optical power meet the specification requirement. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
2.
3.
4. l
Cause 2: The insertion loss between the TDC and RDC optical ports is excessively high. (This cause is applicable only to the OAU board.) 1. On the U2000, check the optical power at the TDC and RDC optical ports on the OAU, and then calculate the insertion loss between the TDC and RDC optical ports. For details, refer to "Querying the Insertion Loss Between the TDC and RDC optical ports on the OAU board" in the Supporting Tasks.
NOTE
Insertion loss = Optical power at the TDC optical port - Optical power at the RDC optical port. On the U2000, the difference between the optical power at optical port 3 and the optical power at optical port 5 represents the insertion loss.
2.
If the insertion loss is excessive, clean the fiber jumper and fiber connector between the TDC and RDC optical ports. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" in the Supporting Tasks. For the insertion loss specification, see the Product Description. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. Check whether the alarm is cleared. If the alarm persists, replace the DCM module between the TDC and RDC optical ports. For details, see "Replacing the DCM" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3. Replace the faulty board.
3.
4. l
Issue 02 (2011-10-31)
If ...
Then ...
2. ----End
Related Information
None.
3.24 ODU_SNCP_PS
Description
The ODU_SNCP_PS alarm indicates the ODU SNCP protection switching. This alarm occurs when the ODU SNCP protection group actuates switching in which the current channel switches to the protection channel from the working channel.
Attribute
Parameters
None

When the ODU SNCP protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the ODU SNCP protection group might have faulty services that needs to be restored.
Fault Symptom
Table 3-25 lists the fault symptoms for the ODU_SNCP_PS alarm.
Issue 02 (2011-10-31)
293
Table 3-25 Fault symptoms for the ODU_SNCP_PS alarm Fault Symptom A protection switching is performed, but there is no alarm that can trigger a protection switching. A protection switching is performed, and the board on the working channel reports alarms that can trigger a protection switching. For details about the alarm information, see Table 3-26. Cause Cause 1: A user issues an external switching command such as forced switching or manual switching. Cause 2: The services of the working channel of the ODU SNCP protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
NOTE
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the ODU SNCP protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the ODU SNCP protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
Procedure
2. 3. l
Cause 2: The services of the working channel of the ODU SNCP protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported. 1. Query whether the related boards for configuring the protection group have alarms relevant to the services. If that is the case, handle the alarms by referring to the corresponding handling procedure of the alarms. For details about the alarm information, see Table 3-26. If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
2.
Issue 02 (2011-10-31)
3. ----End
Related Information
Table 3-26 lists the alarms that can trigger a protection switching. Table 3-26 Related Alarms R_LOF R_LOS R_LOC HARD_BAD OTUk_LOF OTUk_LOM ODUk_TCMn_TIM OTUk_DEG OTUk_AIS OTUk_TIM OTUk_EXC ODUk_PM_AIS ODUk_PM_LCK ODUk_PM_OCI ODUk_PM_DEG ODUk_PM_EXC ODUk_PM_TIM ODUk_TCMn_AIS ODUk_TCMn_LCK ODUk_TCMn_OCI ODUk_TCMn_LTC ODUk_TCMn_EXC ODUk_TCMn_DEG
For details, see "ODUk SNCP Protection" in the Feature Description.
3.25 ODUk_PM_AIS
Description
This alarm is an ODUk PM alarm indication signal. An AIS signal from the downstream station indicates that a signal failure is detected at the upstream station. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity Warning Alarm Type Communication alarm
Parameters
None

The services through the optical port are interrupted.
Fault Symptom
Table 3-27 lists the fault symptoms for the ODUk_PM_AIS alarm. Table 3-27 Fault symptoms for the ODUk_PM_AIS alarm Fault Symptom The client side of the corresponding OTU board at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm. Cause Cause 1 for this alarm generated on the WDM side: The client side of the corresponding OTU board at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm and then inserts an AIS signal to the local station. Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and therefore the board at the local station also reports an ODUk_PM_AIS alarm.
The WDM side of the OTU board at the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm.
NOTE
Possible Causes
The possible causes of the ODUk_PM_AIS alarm are as follows: l Cause 1 for this alarm generated on the client side: Signals input from the client side contain ODUk_PM_AIS signal. See the following figure. The input signals on the client side of the OTU at station A contain ODUk_PM_AIS signals. The OTU at station A reports an ODUk_PM_AIS alarm on the client side after detecting the ODUk_PM_AIS signals.
Issue 02 (2011-10-31)
296
Detects and reports the ODUk_PM_AIS alarm The client signals contain the ODUk_PM_AIS signal
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A
Station B
l l
Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty. Cause 1 for this alarm generated on the WDM side: The client side of the corresponding board at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and then inserts an AIS signal to the local station. See the following figure. The client side of the OTU at station A automatically inserts an ODUk_PM_AIS signal into the WDM-side signals after detecting an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm. The WDM side of the OTU at station B reports an ODUk_PM_AIS alarm after detecting an ODUk_PM_AIS signal.
Detects and reports the ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, OTUk_TIM alarm Insert the ODUk_PM_AIS signal Detects and reports the ODUk_PM_AIS alarm
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A
Station B
Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and therefore the OTU board at the local station also reports an ODUk_PM_AIS alarm.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for this alarm generated on the client side: Signals input from the client side contain ODUk_PM_AIS signal.
Issue 02 (2011-10-31)
1.
If this alarm is reported from the client side of the board, apply a hardware loopback between the transmit and receive optical ports on the client side of OTU1. If the alarm on OTU1 persists, it indicates that the OTU1 hardware is faulty. In this case, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
Configuring a loopback on the board interrupts the services on the board. 2. l If the alarm is cleared, it indicates that the input signals on the client side of the board contain bit errors. In this case, rectify the fault on the client equipment. Check whether the board that reports this alarm supports pluggable optical modules. If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, l Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
The client side of the corresponding OTU board at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm and then inserts an AIS signal to the local station 1. On the U2000, check whether an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM or OTUk_TIM alarm exists on the client side of the OTU board at the opposite end. If the alarm exists, check the equipment at the opposite station. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
2. l
Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and therefore the OTU board at the local station also reports an ODUk_PM_AIS alarm. 1. On the U2000, check whether an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm exists on the WDM side of the OTU at the local station. If yes, rectify the fault at the local station to clear the alarm. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2. ----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)
298
3.26 ODUk_PM_BDI
Description
This alarm is an ODUk PM backward defect indication. This alarm is generated when the PM section at the opposite station detects a signal failure and inserts a BDI alarm to the local station. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None

The services through the optical port are interrutped.
Fault Symptom
Table 3-28 lists the fault symptom for the ODUk_PM_BDI alarm. Table 3-28 Fault symptom for the ODUk_PM_BDI alarm Fault Symptom The board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm. Cause Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm and inserts an ODUk_PM_BDI back to the local station (station A).
Issue 02 (2011-10-31)
299

NOTE
Possible Causes
l l l Cause 1 for this alarm generated on the client side: Signals input from the client side contain an ODUk_PM_BDI signal. Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and inserts an ODUk_PM_BDI back to the local station (station A).
Detects and reports R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_PM_SSF alarms
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the ODUk_PM_BDI alarm
Station B Sends the ODUk_PM_BDI signal back
Procedure
l l On the U2000, check whether there is an alarm with higher severity on the board. If yes, handle the alarm properly. Cause 1 for this alarm generated on the client side: Signals input from the client side contain an ODUk_PM_BDI signal. 1. If this alarm is reported from the client side of the board, apply a hardware loopback between the transmit and receive optical ports on the client side of OTU board. If this alarm persists, it indicates that the board is faulty. In this case, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
A loopback on the board interrupts the existing services. 2. l If this alarm is cleared, it indicates that the input signals on the client side of the board contain bit errors. In this case, rectify the fault on the client equipment.
Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty.
Issue 02 (2011-10-31)
1.
Check whether the board that reports this alarm supports pluggable optical modules. If ... Then ...
Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and inserts an ODUk_PM_BDI back to the local station. 1. If this alarm is reported from the WDM side, check whether the corresponding OTU board at the opposite station receives an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm by using the U2000. If yes, handle the corresponding alarm at the opposite station. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
2. ----End
Related Information
ITU-T G.709
3.27 ODUk_PM_DEG
Description
This alarm indicates that the ODUk PM signal is degraded. When the BIP8 detection is in burst mode, this alarm is generated if the signal degradation or bit error count exceeds the threshold. In addition, when the BIP8 detection in poisson mode, this alarm is generated if the signal degradation exceeds the threshold. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Issue 02 (2011-10-31)
301
Parameters
None

If this alarm is generated, bit errors are generated in the services through the optical port, which makes the service signals unavailable.
Fault Symptom
Table 3-29 lists the fault symptom for the ODUk_PM_DEG alarm. Table 3-29 Fault symptom for the ODUk_PM_DEG alarm Fault Symptom The OTU board at the local station may report an IN_PWR_LOW or a BEFFEC_EXC alarm. Cause Cause 1: The attenuation of received signals is excessively large. As a result, the input optical power of the board is abnormal.
NOTE
Possible Causes
The possible causes of the ODUk_PM_DEG alarm are as follows: l l l Cause 1: The input optical power of the OTU board is abnormal. Cause 2: The fiber on the transmission line is abnormal. Cause 3: The board that reports the alarm is faulty or the corresponding board at the opposite station is faulty.
Procedure
l Cause 1: The input optical power of the OTU board is abnormal. 1. 2. On the U2000, view the alarms of the entire network to confirm the slot ID, interface ID, and channel ID of the board that generates this alarm. Along the service signal flow, check whether the input optical power of the point that first generates this alarm is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the optical power is not within the normal range, adjust the input optical power of the board to a proper value. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, troubleshoot this alarm station by station along the service signal flow. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
3.
4. 5.
Issue 02 (2011-10-31)
Cause 2: The fiber on the transmission line is abnormal. 1. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see "Replacing Fiber Jumpers" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
2.
3. l
Cause 3: The board that reports the alarm is faulty or the corresponding board at the opposite station is faulty. 1. If the alarm persists, replace the board that reports the alarm. If ... Then ...
Related Information
ITU-T G.709
3.28 ODUk_PM_EXC
Description
This alarm indicates that the BIP8 error count on the ODUk PM section exceeds the threshold. This alarm is generated when the BIP8 detection is in poisson mode and bit error count exceeds the threshold. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Issue 02 (2011-10-31)
303
Attribute
Parameters
None

The alarm has impacts on the QoS of the service signals.
Fault Symptom
Table 3-30 lists the fault symptoms for the ODUk_PM_EXC alarm. Table 3-30 Fault symptoms for the ODUk_PM_EXC alarm Fault Symptom The OTU board at the local station may report an IN_PWR_LOW alarm. Cause Cause 1: The attenuation of the received signals is rather large, and the fiber transmission line is abnormal.
NOTE
Possible Causes
l l l Cause 1: The attenuation of the received signals is rather large, and the fiber transmission line is abnormal. Cause 2: The transmitter of OTU board at the opposite station is faulty. Cause 3: The receiver of the OTU board at local station is faulty.
Procedure
l Cause 1: The attenuation of the received signals is rather large, and the fiber transmission line is abnormal. 1. On the U2000, check whether the receive optical power is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.For details, refer to "Querying Optical Power on the U2000" of the Supporting Tasks.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards" of the Hardware Description to obtain the manufacturing information of the optical module on the OTU board.
Issue 02 (2011-10-31)
304
2. 3.
If the receive optical power of the OTU board at the local station is excessively low, clear the alarm according to the handling procedure of the IN_PWR_LOW alarm. If the alarm persists, check whether the launched optical power at the corresponding optical port on the upstream board is within the normal range on the U2000. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the launched optical power of the OTU board at the upstream station is excessively low, clear the alarm according to the handling procedure of the OUT_PWR_LOW alarm. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Apply a hardware loopback between the transmit and receive optical ports on the WDM side of the OTU board at the upstream station. If the alarm persists, it indicates that the transmitter on the OTU board of the opposite station is faulty. In this case, replace the OTU board. If ... Then ...
4. l
Cause 2: The transmitter of the OTU board at the opposite station is faulty. 1.
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not support pluggable optical modules, 2. l 1. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
If the alarm persists, see the alarm handling procedure for cause 3. If the alarm persists, replace the faulty board at the local station. If ... Then ...
Cause 3: The receiver of the OTU board at local station is faulty.
Related Information
ITU-T G.709
Issue 02 (2011-10-31)
305
3.29 ODUk_PM_SSF
Description
The ODUk_PM_SSF is an alarm indicating signal failure at the ODUk PM layer. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None

Fault Symptom
Table 3-31 lists the fault symptom for the ODUk_PM_SSF alarm. Table 3-31 Fault symptom for the ODUk_PM_SSF alarm Fault Symptom A station may report the R_LOS, OTUk_SSF alarm at the same time. Cause Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration boards. Cause 4: In the case of a station configured with tributary boards and line boards, the line boards report the ODUk_PM_SSF alarm when the line is abnormal. A station may report the ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, or ODUk_TCMn_TIM alarm at the same time. A station may report the OTUk_TIM alarm at the same time. Cause 2: The station reports an alarm of the ODUk_TCMn type and the ODUk_PM_SSF alarm at the same time. Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the same time.
306
Issue 02 (2011-10-31)
NOTE
Possible Causes
l Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration boards. As shown in the following figure, when the line in the span from the OTU1 board at station A to the OTU2 board at station B or in the span from the OTU3 board at station B to the OTU4 board at station C is abnormal, the OTU4 board at station C reports the ODUk_PM_SSF alarm.
O T U 1 Client WDM side side M U X/ D M U X OA OA M U X/ D M U X O T U 2 O T U 3 M U X/ D M U X OA OA M U O X/ T D U M 4 U X WDM Client side side Station C
OA
F I U
F I U
OA
F I U
OA
F I U
OA
Station A
Station B
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
Cause 2: When Sink Enable Status is Enabled and Source Mode is Operation Mode for the TCM overheads of the station, the station reports the ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, or ODUk_TCMn_TIM alarm and the ODUk_PM_SSF alarm at the same time. The ODUk_TCMn_LTC alarm is reported only when Enable LTC Response is set to Enabled. The ODUk_TCMn_TIM alarm is reported only when Enable TIM Response is set to Enabled. Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the same time. The OTUk_TIM alarm is reported only when Enable TIM Response is set to Enabled. Cause 4: In the case of a station configured with tributary boards and line boards, the line boards report the ODUk_PM_SSF alarm when the line is abnormal.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration boards. 1. According to the service flow, find the first station where the SSF alarm is reported and then the OTU board that reports the alarm at the station, for example, the OTU4 board at station C in the figure. If the OTU4 board is a tributary-line board, check whether the OTU2 board at station B reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms.
2.
Issue 02 (2011-10-31)
307
If ... The OTU2 board reports the preceding alarms,
Then ... Handle these alarms in advance. That is, clear these alarms according to the corresponding methods.
The OTU2 board does not report the See cause 2. preceding alarms, 3. If the OTU4 board consists of a tributary board and a line board, check whether the line board at station C reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms. If ... The line board at station C reports the preceding alarms, Then ... Handle these alarms in advance. That is, clear these alarms according to the corresponding methods.
The line board at station C does not See the next step. report the preceding alarms, 4. Check whether the OTU2 board at station B reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms. If ... Then ...
The OTU2 board at station B reports Handle these alarms in advance. That is, the preceding alarms, clear these alarms according to the corresponding methods. The OTU2 board at station B does not report the preceding alarms, l See cause 2.
Cause 2: The station reports an alarm of the ODUk_TCMn type and the ODUk_PM_SSF alarm at the same time. 1. 2. According to the service flow, find the first station where the SSF alarm is reported and then the OTU board that reports the alarm at the station. Check whether the ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, or the ODUk_TCMn_TIM alarm is reported at the station. If yes, handle the alarm in advance. That is, clear the alarm according to the corresponding method. Check whether the alarm is cleared. If the alarm persists, see cause 3.
3. l
Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the same time. 1. 2. Check whether the OTUk_TIM alarm is reported at the station. If yes, handle the alarm in advance. That is, clear the alarm according to the corresponding method. Check whether the alarm is cleared. If the alarm persists, see cause 4.
Cause 4: In the case of a station configured with tributary boards and line boards, the line boards report the ODUk_PM_SSF alarm when the line is abnormal.
Issue 02 (2011-10-31)
1.
Check whether the R_LOS, OTUk_SSF, and OTUk_LOF alarms are reported on the WDM side of the line board at the station. If yes, handle the alarms in advance. That is, clear the alarms according to the corresponding methods. If ... Then ...
The line board at the station reports Handle these alarms in advance. That is, the preceding alarms, clear these alarms according to the corresponding methods. The line board at the station does not Contact Huawei engineers. report the preceding alarms, ----End
Related Information
None
3.30 OMS_FDI
Description
This alarm is a forward defect indication at OMS layer. When the OMS_FDI-P and OMS_FDIO alarms coexist, this alarm is generated. At the same time, the OMS_FDI-P and OMS_FDI-O alarms are suppressed. When the board at the OTS layer detects a loss of signal alarm but cannot forward the alarm to the downstream station, it inserts the OMS_FDI signal. When the downstream station receives the OMS_FDI signal, it reports the OMS_FDI alarm. Reported from the WDM side or client side: NA
Attribute
Parameters
None

The existing services may be interrupted.
Fault Symptom
Table 3-32 lists the fault symptom for the OMS_FDI alarm.
Table 3-32 Fault symptom for the OMS_FDI alarm Fault Symptom The board at the opposite station reports an OTS_LOS or OTS_TIM alarm. Cause Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low. Thus, the loss of signal alarm is detected at the downstream station, and an OMS_FDI alarm is then inserted to the downstream station.
NOTE
Possible Causes
The possible causes of the OMS_FDI alarm are as follows: l l Cause 1: The logical fiber connections are inconsistent with the physical fiber connections. Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low. Thus, the loss of signal alarm is detected at the downstream station, and the OMS_FDI is then inserted to the downstream station.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The logical fiber connections are inconsistent with the physical fiber connections. 1. Check whether the logical fiber connection configured for the optical interface where the alarm is generated is consistent with its physical fiber connection. If not, modify the configuration of the logical fiber connection so that the logical fiber connection is consistent with the physical fiber connection. For details, see "Checking Logical Fibers" in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
2. l
Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low. Thus, the loss of signal alarm is detected at the downstream station, and then the OMS_FDI is inserted to the downstream station. 1. Check whether an OTS_LOS or OTS_TIM alarm is generated at the opposite station and all upstream stations. If yes, troubleshoot the OTS_LOS or OTS_TIM alarm according to the alarm handling procedure. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2. ----End
Related Information
None.
3.31 OSC_LOS
Description
The OSC_LOS alarm indicates the loss of input optical power on receiving line. This alarm is generated when the input optical power of the OSC board exceeds the LOS threshold. Reported from the WDM side or client side: NA
Attribute
Parameters
None

There is a fiber break in the receive direction and this can cause loss of the monitoring signals.
Possible Causes
l l l l l Cause 1: A certain optical port on the board that reports the alarm is not connected to a fiber. Cause 2: The laser of the board at the opposite station is shut down. Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs on the transmission line. Cause 4: The transmit part of the opposite station is faulty. Cause 5: The receive part of the local station is faulty.
Procedure
l l Query the alarm on the U2000 and record the IDs of the optical port and channel where the alarm is generated. Cause 1: A certain optical port on the board that reports the alarm is not connected to a fiber. 1. l Check whether the fiber jumper is connected to the optical port of the board at the local station. If not, connect the fiber jumper. Use the U2000 to check whether the laser of the specific board at the opposite station is on. If not, open the laser of the board.
Cause 2: The laser of the board at the opposite station is shut down. 1.
Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs on the transmission line.
Issue 02 (2011-10-31)
1.
On the U2000 check whether the receive optical power at the optical port where the alarm is generated is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the receive optical power is not within the normal range, clear the alarm according to the handling procedure for the IN_PWR_LOW or IN_PWR_HIGH. If the receive optical power is normal, check the fiber connector. If the fiber connector is dirty or damaged, clean or replace the fiber connector. If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks. If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
2. 3. l
Cause 4: The transmit part of the opposite station is faulty. 1.
Cause 5: The receive part of the local station is faulty. 1.
----End
Related Information
None.
3.32 OTS_LOS
Description
The OTS_LOS alarm indicates a loss of signal at the OTS layer. When the OTS_LOS-P and OTS_LOS-O alarms coexist, this alarm is generated. At the same time, the OTS_LOS-P and OTS_LOS-O alarms are suppressed. Reported from the WDM side or client side: NA
Attribute
Parameters
None

Possible Causes
Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the optical interface and channel where the alarm is generated. Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station. 1. Check whether the logical fiber connections of the FIU are consistent with the physical fiber connections. If not, modify the configuration of the logical fiber connections so that logical fiber connections are consistent with the physical fiber connections. Check and make sure that the fiber connection between the "IN" interface on the local FIU and the opposite station is correct and reliable. If the alarm persists, check whether the attenuation of the "IN" interface on the FIU is excessively high. If yes, adjust the attenuation to a proper value. If the alarm persists, check and make sure that fibers connected to the optical interfaces on the FIU are correct and reliable.
2. 3. 4. ----End
Related Information
None.
3.33 OTUk_LOF
Description
The OTUk_LOF is an alarm indicating that the frame alignment signal (FAS) is abnormal. This alarm occurs when the frame alignment processing is out of frame (OOF) in three consecutive milliseconds. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Parameters
None

Services on the board are interrupted.
Fault Symptom
Table 3-33 lists the fault symptom for the TEMP_OVER alarm. Table 3-33 Fault symptom for the OTUk_LOF alarm Fault Symptom Two boards at two ends of a single wavelength report the OTUk_LOF alarm in the deployment. A single board at one end reports the OTUk_LOF alarm in the deployment. In addition, the alarm indicating abnormal optical power is reported. Multiple boards on the same link report the OTUk_LOF alarm in the deployment. A single board at one end reports the OTUk_LOF alarm in the deployment. A board reports the OTUk_LOF alarm during normal operation after deployment. Cause Cause 1: The settings of the service type or FEC type are incorrect. Cause 3: The receive optical power or the OSNR of the local board is abnormal.
Cause 6: The dispersion compensation value is excessively great or small. Cause 2: The board that reports the alarm is faulty. Cause 2: The board that reports the alarm is faulty.
NOTE
Possible Causes
l l l l l l Cause 1: The settings of the service type or FEC type are incorrect. Cause 2: The board that reports the alarm is faulty. Cause 3: The receive optical power or the OSNR of the local board is abnormal. Cause 4: The signals transmitted by the corresponding board at the opposite end do not have a frame structure. Cause 5: The fiber of the transmission line is abnormal. Cause 6: The dispersion compensation value is excessively great or small.
Procedure
l Cause 1: The settings of the service type or FEC type are incorrect. 1. Query the FEC type on the U2000 to check whether the set FEC type is the same as the FEC type supported by the board. For the specific service types and FEC types, see the Hardware Description. If the FEC type is different from the FEC type supported by the board, reset the FEC type to the same as the FEC type supported by the board. For details about the operation, see Setting the FEC Type in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see cause 2.
2.
Issue 02 (2011-10-31)
Cause 2: The board that reports the alarm is faulty. 1. 2. See Performing Hardware Loopback to perform the relevant operation on the optical port where the alarm is reported. Then check whether the alarm is cleared. If the alarm persists, replace the board. If ... Then ...
3. l 1.
If the alarm disappears, see cause 3. Check whether the input optical power of the position where the alarm is first generated is within the normal range. For the optical power specifications of specific boards, see the Product Description. If the optical power is abnormal, see the handling methods of the IN_PWR_HIGH and IN_PWR_LOW alarms to clear the alarms. Check whether the alarm is cleared. If the alarm persists, see cause 4.
Cause 3: The receive optical power or the OSNR of the local board is abnormal.
2. l
Cause 4: The signals transmitted by the corresponding board at the opposite end do not have a frame structure. 1. Test the signal sent from the WDM side on the board at the opposite station by using a meter. Check whether the signal is the white light without signal frame or does not have the OTN frame format. If the light does not comply with the requirement, replace the faulty board. If ... Then ...
2. l 1.
Check whether the alarm is cleared. If the alarm persists, see cause 5. If the alarm persists, check whether the fiber meets the following requirements: The bending radius is not less than 40 mm. The optical port connector is well inserted. The fiber connector is clean. The cable is intact.
Cause 5: The fiber of the transmission line is abnormal.
Issue 02 (2011-10-31)
315
If the preceding requirements are not met, clean the fiber connector or replace the fiber. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks. 2. l 1. 2. ----End Check whether the alarm is cleared. If the alarm persists, see cause 6. If the alarm persists, replace the DCM module. For details about the operations, see Replacing a DCM in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers. Cause 6: The dispersion compensation value is excessively great or small.
Related Information
ITU-T G.709
3.34 OTUk_SSF
Description
The OTUk_SSF is an alarm that the signal fails at the OTUk server layer. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Parameters
None

Fault Symptom
Table 3-34 lists the fault symptom for the OTUk_SSF alarm.
Issue 02 (2011-10-31)
316
Table 3-34 Fault symptom for the OTUk_SSF alarm Fault Symptom A station may report the R_LOS, ODUk_PM_SSF alarm at the same time. A station may report the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm at the same time. Cause Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same time. Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the ODUk_PM_SSF alarm at the same time.
NOTE
Possible Causes
l Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same time. As shown in the following figure, the client side (the client side accesses the OTU service) in the receive direction of the OTU1 board at station A or the WDM side in the receive direction of the OTU2 board at station B reports the R_LOS alarm.
M U X/ D M U X M U O X/ T D U M 2 U Client WDM X side side Station B
O T U 1 Client WDM side side
OA
OA
F I U
F I U
OA
OA
Station A
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the ODUk_PM_SSF alarm at the same time.
Procedure
l Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same time. 1. According to the service flow, find the first station where the SSF alarm is reported and then the OTU board that reports the alarm at the station, for example, the OTU1 board at station A or the OTU2 board at station B in the figure. Check whether the R_LOS alarm is reported in the receive direction of the OTU board at the station.
2.
Issue 02 (2011-10-31)
317
If ... The OTU board reports the preceding alarm,
Then ... Handle the alarm in advance. That is, clear the alarm according to the corresponding method.
The OTU board does not report the See cause 2. preceding alarm, l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the ODUk_PM_SSF alarm at the same time. 1. According to the service flow, find the first station where the SSF alarm is reported and then the OTU board that reports the alarm at the station, for example, the OTU1 board at station A or the OTU2 board at station B in the figure. Check whether the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm is reported in the receive direction of the OTU board at the station. If ... The OTU board reports the preceding alarm, Then ... Handle the alarm in advance. That is, clear the alarm according to the corresponding method.
2.
The OTU board does not report the Contact Huawei engineers. preceding alarm, ----End
Related Information
None
3.35 OUT_PWR_HIGH
Description
This alarm indicates that the output optical power is very high. This alarm is generated when the laser output optical power exceeds the upper threshold. Reported from the WDM or client side: WDM side, client side.
Attribute
Parameters
None

l When the output optical power is excessively high, the input optical power at the receive end will be very high if no proper optical attenuator is used at the receive end. As a result, the module at the receive end may be damaged. If the board works abnormally, the existing services are affected.
Fault Symptom
None.
NOTE
Possible Causes
Cause 1: The optical module of laser is faulty or the board is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the optical port and channel where the alarm is generated. Cause 1: The optical module of laser is faulty or the board is faulty. 1. Check whether the board that reports this alarm supports pluggable optical modules. If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module. For details, refer to "Replacing modules, Pluggable Optical Modules" of the Parts Replacement. The board does not supports pluggable optical modules, 2. ----End Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
Related Information
None.
3.36 PORT_MODULE_OFFLINE
Description
This alarm indicates that the optical module on an optical port is offline. This alarm is generated when the board detects that an optical module is offline. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

Absence of the optical module leads to an interruption of services through by the corresponding optical port.
Fault Symptom
None.
NOTE
Possible Causes
l l Cause 1: The optical module does not exist or is not correctly inserted in the optical port. Cause 2: The optical module or the board is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The optical module does not exist or is not correctly inserted in the slot. 1. Check whether the optical port where this alarm is generated has an optical module. If ... The optical port has no optical module. The optical port has an optical module. l Then ... Insert an optical module into the optical port properly. See the alarm handling procedure for cause 2.
Cause 2: The optical module or the board is faulty. 1. 2. Perform a cold reset on the faulty board through the U2000. If the alarm persists, the board that reports the alarm may be faulty.If the board uses pluggable optical modules, replace the specific pluggable optical module. For details, refer to "Replacing Pluggable Optical Modules" of the Parts Replacement. If the optical module is not pluggable, replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
3.
Issue 02 (2011-10-31)
4. ----End
Related Information
None.
3.37 POWER_FAIL
Description
This alarm indicates a power failure. This alarm is generated if the power supply of a board becomes abnormal. For example, there is overvoltage or undervoltage of the power supply, or the battery on the SCC has no charge. Reported from the WDM side or client side: NA
Attribute
Parameters
Parameter 1 Indicates the state of the power supply in which the alarm is generated. For example: 0x3d indicates the undervoltage of the -48 V power supply. 0x3f indicates the undervoltage of the -60 V power supply. 0x3e indicates the overvoltage of the -48 V power supply. 0x40 indicates the overvoltage of the -60 V power supply. 0x05 indicates that the voltage of the battery is excessively low or the battery fails. 0x53 indicates the undervoltage of the -48 V fan power supply. 0x54 indicates the overvoltage of the -48 V fan power supply.
Issue 02 (2011-10-31)
321

l l If this alarm is reported by the SCC board, the system time is lost when the system is powered off. If this alarm is reported by other boards, If the active power supply fails but the standby power supply is normal, there is no impact on the existing services, because a switching to the standby power supply is performed. If both active and standby power supply fail, the existing services are interrupted.
Fault Symptom
None.
NOTE
Possible Causes
l l Cause 1: If this alarm is reported by the SCC board, it indicates that the battery of the SCC board is abnormal (the value of parameter 1 of this alarm is 0x05). Cause 2: If this alarm is reported by the PIU board, it indicates that the input voltage of the subrack is abnormal because the power supply module is faulty (the value of parameter 1 of this alarm is 0x3d or 0x3f). Cause 3: If this alarm is reported by the PIU or CRPC board, it indicates that the power supply module of the board fails or is aging (the value of parameter 1 of this alarm may be any one but 0x05).
Procedure
l Cause 1: If this alarm is reported by the SCC board, it indicates that the battery of the SCC board is abnormal (the value of alarm parameter 1 is 0x05). 1. check whether the jumper cap is correctly placed over the battery jumper. If yes, check the jumper setting of the battery on the SCC board. If the setting disables the battery from proving power, change the setting to ensure that the battery to provide power to the SCC board. For details about the jumper setting of the battery on the SCC board, see the Hardware Description. If the alarm persists, use a multimeter to measure the battery voltage. If the voltage is lower than 3 V, the battery is out of work. The board must be replaced. Replace the faulty board. For details, see the Parts Replacement.
2.
Cause 2: If this alarm is reported by the PIU board, it indicates that the input voltage of the subrack is abnormal because the power supply module is faulty (the value of parameter 1 of this alarm is 0x3d or 0x3f). 1. 2. Check whether the switch on the DC power distribution box of the cabinet is ON. If not, turn it to ON. If the alarm persists, it indicates that the switch on the DC power distribution box is faulty. In this case, replace the switch. For details, see "Replacing the Power Switch on the DC Power Distribution Box" in the Parts Replacement.
Issue 02 (2011-10-31)
Cause 3: If this alarm is reported by the PIU or CRPC board, it indicates that the power supply module of the board fails or is aging (the value of parameter 1 of this alarm may be any one but 0x05). 1. Replace the faulty board. For details, see "Replacing the PIU Board" or "Replacing the Raman Amplifier Board" in the Parts Replacement.
----End
Related Information
Related Cases: l l l l MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER Alarms MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution MC-A112 The SCC Housed In the Slave Subrack Reports the POWER_FAIL Alarm Because the Jumper on the Board Is Set Improperly MC-A204 Power Modules on Multiple Boards Report the POWER_FAIL Alarms Due to Excessively High Temperature
3.38 PUMP_COOL_EXC
Description
This alarm indicates that the cooling current of the pump laser exceeds the threshold. This alarm is generated when the laser cooling current exceeds the upper threshold. Reported from the WDM side or client side: NA
Attribute
Parameters
Parameter 1 Indicates that the cooling current exceeds the threshold. The value is always 0x01.
Issue 02 (2011-10-31)
323

When this alarm is reported, the laser ages sharply and the performance of output signals degrades.
Fault Symptom
Table 3-35 lists the fault symptom for the PUMP_COOL_EXC alarm. Table 3-35 Fault symptom for the PUMP_COOL_EXC alarm Fault Symptom The NE that reports this alarm reports a temperature alarm or fan fault alarm, such as TEMP_OVER or FAN_FAIL, within a certain time. Cause Cause 1: The ambient temperature of the board is excessively high or low.
NOTE
Possible Causes
The possible causes of the PUMP_COOL_EXC alarm are as follows: l l l Cause 1: The ambient temperature is excessively high or low. Cause 2: The pump laser temperature is excessively high or low. Cause 3: The board that reports this alarm is faulty.
Procedure
l Cause 1: The ambient temperature is excessively high or low. 1. Check the ambient temperature inside the telecommunications room, the cleanliness of the air filter, and heat dissipation through fans. For details, see TEMP_OVER to rectify the fault. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for causes 2 and 3.
2. l
Causes 2: The pump laser temperature is excessively high or low/Cause 3: The board that reports this alarm is faulty. 1. 2. If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.39 R_LOF
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-36 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.39.1 R_LOF (OCS) 3.39.2 R_LOF (OTN)
3.39.1 R_LOF (OCS)

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

l l When the R_LOF alarm is generated, the services are interrupted, and the AIS signal is inserted in the downstream station. When the R_LOF occurs, the system automatically returns the MS_RDI alarm to the upstream station. Consequently, the upstream station reports the MS_RDI alarm.
Possible Causes
The possible causes of the R_LOF alarm are as follows: l l
Issue 02 (2011-10-31)
Cause 1: Two boards at different rates are connected to each other. Cause 2: The receive optical power is excessively low.
l l l l
Cause 3: The receive optical power is excessively high. Cause 4: The transmit optical power of the opposite station is abnormal. Cause 5: The receive board at the local station is faulty. Cause 6: The transmitted signals do not have the frame structure because of the fault of the opposite board.
Procedure
l l Query current alarms on the U2000. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: Two boards at different rates are connected to each other. 1. The improper fiber connection may cause that two boards at different rates are connected to each other. This affects the service configuration. Correct the fiber connection and then check whether the alarm is cleared. If the alarm persists, check whether the types of the two boards are the same. If the board that supports the FEC function is connected to the board that does not support the FEC function, two boards at different rates may be connected to each other. Enable or disable the FEC function of the two boards according to the actual condition. For details, see Enabling the FEC Function in the Supporting Task. For details on the boards that support the FEC function, see the "Function and Feature" of each board in the Hardware Description. Then, check whether the alarm is cleared. If the alarm persists, see cause 2. On the U2000, check whether the receive optical power of the local station is within the normal range. For details on optical power specification of the board, see"Technical Specifications" of the Product Description. For details of the operations, see Querying Optical Power of the Board in the Supporting Task.
NOTE
2.
3. l 1.
Cause 2 and cause 3: The receive optical power is excessively low.
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the manufacturer information about the optical module.
If... The receive optical power of the local board is excessively low The receive optical power of the local board is excessively high 2.
Go to step 3.
Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task to check whether the connectors are dirty. If the fiber connector is dirty, clean immediately. For the operations, see Supporting Task. Cleaning Optical Fiber Connectors Using Cartridge Cleaners Cleaning Optical Fiber Connectors Using Lens Tissue Cleaning Optical Adapters Using Optical Cleaning Sticks Then, check whether the alarm is cleared.
3.
If the alarm persists, check whether the attenuation of the optical attenuator is correct. If the attenuation is not correct, change the value. The attenuation of the optical
Issue 02 (2011-10-31)
attenuator depends on the receive optical power of the board. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. If... The optical attenuation is excessively low Then... Decrease the optical attenuation and check whether the alarm is cleared. If the alarm persists, proceed to the next step. Increase the optical attenuation and check whether the alarm is cleared. If the alarm persists, see cause 4.
The optical attenuation is excessively high
4. 5. l 1.
Check whether the fiber is damaged or oppressed. If yes, replace the fiber. Then, check whether the alarm is cleared. If the alarm persists, see cause 4. On the U2000, check whether the transmit optical power of the opposite board is within the normal range. For details on optical power specification of the board, see "Technical Specifications" of the Product Description. For details of the operations, see Querying Optical Power of the Board in the Supporting Task.
NOTE
Cause 4: The transmit optical power of the opposite station is abnormal.
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the manufacturer information about the board optical module.
2.
If the transmit optical power of the opposite board is abnormal, see the OUT_PWR_HIGH or OUT_PWR_LOW alarm to rectify the fault. Then, check whether the R_LOF alarm is cleared. If the alarm persists, see cause 5. Perform a selfloop (hardware inloop) on the receive and transmit interfaces of the board. For details, see Performing Hardware Loopback in the Supporting Task.
3. l 1.
Cause 5: The receive board at the local station is faulty.
CAUTION
The loopback may cause service interruptions.
CAUTION
The overload of optical power should be avoided when the hardware inloop is performed. According to the optical power specifications of the board, add an optical attenuator on the receive optical interface. For the operations of adding an attenuator, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
Issue 02 (2011-10-31)
327
If... The alarm is reported No alarm is reported 2.
Then... The local board is faulty. Proceed to the next step. See cause 6.
Replace the optical module or board at the local station. For details, see Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace the faulty board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see cause 6. Replace the optical module or board at the opposite station. For details, see Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace the board. For details, see Parts Replacement.
3. l 1.
Cause 6: The transmitted signals at the opposite station do not have the frame structure.
----End
Related Information
None.
3.39.2 R_LOF (OTN)

Description
This alarm indicates loss of frame in the received signals. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3 ms. Reported from the WDM side or client side: l l WDM side - Check for this alarm when there are SDH frames in the services accessed on the WDM side. Client side - Check for this alarm when the SDH services are accessed on the client side.
Attribute
Parameters
None

l l The board fails to locate the data frame of the received SDH signals, and therefore the client services fail. After this alarm is detected, a protection switching is performed if the board supports protection switching.
Issue 02 (2011-10-31)
Fault Symptom
Table 3-37 lists the fault symptom for the R_LOF alarm. Table 3-37 Fault symptom for the R_LOF alarm Fault Symptom The upstream board may report an R_LOS or R_LOF alarm. Cause Cause 4 for this alarm generated on the WDM side
NOTE
Possible Causes
l l l l l l l Cause 1 for this alarm generated on the client side: The input signals from the client side contain an R_LOF signal. Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 for this alarm generated on the WDM side: The receive optical power or the OSNR of the local board is abnormal. Cause 2 for this alarm generated on the WDM side: The signals transmitted by the upstream OTU have no SDH frame structure. Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is faulty. Cause 4 for this alarm generated on the WDM side: The input signals from the upstream station contain an R_LOS or R_LOF signal. Cause 5 for this alarm generated on the WDM side: The dispersion is under- or overcompensated.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for this alarm generated on the client side: The input signals from the client side contain an R_LOF alarm signal. 1. If this alarm is reported from the client side of the board, apply a hardware loopback between the transmit and receive optical ports on the client side of the board. If this alarm on the board persists, it indicates that the board is faulty. In this case, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
Configuring a loopback on the board interrupts the services on the board.
Issue 02 (2011-10-31)
329
2. l
If this alarm is cleared, it indicates that the input signals on the client side contain an R_LOF signal. In this case, rectify the fault on the client equipment.
Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty. 1. Check whether board that reports this alarm supports pluggable optical modules. If ... Then ...
Cause 1 for this alarm generated on the WDM side/Cause 2 for this alarm generated on the WDM side: The receive optical power or the OSNR of the local board is abnormal; the signals transmitted by the upstream OTU have no SDH frame structure. 1. If the WDM side reports this alarm, on the U2000 check whether the client side of the board at the opposite station reports an R_LOF alarm. If yes, rectify the fault according to the procedure for handling the R_LOF alarm generated on the client side. If the alarm persists, on the U2000 check whether the receive optical power at the WDM-side optical port of the alarm-reporting board is within normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
2.
3. 4.
If the optical power is abnormal, rectify the fault according the procedure for handling the IN_PWR_LOW or IN_PWR_HIGH alarm. If the receive optical power is normal, use an SDH meter to receive signals from the WDM side of the board in opposite station. Check whether the received signal is of white spectrum (no signal frame) or has no SDH frame. If the received signal fails to comply with the requirement, replace the faulty board. If ... Then ...
Issue 02 (2011-10-31)
330
5. l
Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm generated on the WDM side.
Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is faulty. 1. If the alarm persists, the board may be faulty. Replace the faulty board at the local station. If ... Then ...
Cause 4 for this alarm generated on the WDM side: The input signals from the upstream station contain an R_LOS or R_LOF signal. 1. 2. If the alarm persists, clear the alarm of the equipment at the upstream station. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 5 of this alarm generated on the WDM side.
Cause 5 for this alarm generated on the WDM side: The dispersion is under- or overcompensated. 1. 2. If the alarm persists, replace the DCM module. For details, see "Replacing a DCM" in the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases: l l l l l l MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss Is Very Large MC-A21 An Interconnection Failure between the WDM and SDH Equipment MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm on the Board MC-A31 Wrong Calculation for Dispersion in One DWDM Project MC-A104 No Optical Power Is Output on the WDM Side Due to Incorrect Configuration,the Board Reports the R_LOF, R_LOC, TP_LOC Alarms MC-A115 Determine Whether the Type and Connections Of the Dispersion Compensation Module (DCM) Are Proper When the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD Alarms Are Reported on the WDM Side of LWF Board MC-A128 EPL Service Was Interrupted Due To a Service Mode Mismatch of L4G Boards and Nodes Report R_LOF, ODU5G_PS_AIS, OTU5G_LOF, LINK_ERR Alarm
Issue 02 (2011-10-31)
None.
3.40 R_LOS
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-38 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.40.1 R_LOS (OCS) 3.40.2 R_LOS (OTN)
3.40.1 R_LOS (OCS)

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

l l When the R_LOS alarm is generated, the services are interrupted, and the AIS signal is inserted at the downstream station. When the R_LOS occurs, the system automatically returns the MS_RDI alarm to the upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes
The possible causes of the R_LOS alarm are as follows: l Cause 1 of the fiber: There is a fiber cut (if the alarm is reported by an SDH optical interface board). Identification method: Use instruments to test the fiber.
Cause 2 of the fiber: The optical interface of the local board is not connected to the fiber jumper or is connected to an incorrect fiber jumper (if the alarm is reported by an SDH optical interface board). Identification method: Check the connection of the fiber jumper. Cause 3 of the fiber: The line attenuation is excessively high. As a result, the optical power is excessively low (if the alarm is reported by an SDH optical interface board). Identification method: Query the optical power of the two stations. Cause 1 of the laser: The local optical interface is not used. Identification method: Check whether the optical interface is in use (if the alarm is reported by an SDH optical interface board).
Cause 2 of the laser: The opposite laser is inactive, and as a result, no signal is input. Identification method: Check whether the laser is in use (if the alarm is reported by an SDH optical interface board).
Cause 1 of the board: The receive board at the local station is faulty. As a result, the line receiving fails. Identification method: Perform a loopback. Cause 2 of the board: The transmit board at the opposite station is faulty. As a result, the line transmitting fails. Identification method: Locate the fault with the exclusive method.
Procedure
l Query current alarms on the U2000. Determine the ID of the optical interface that reports the alarm according to alarm parameter 1. For details, see Querying the Current Alarms in the Supporting Task. Cause 1 of the fiber: There is a fiber cut (if the alarm is reported by an SDH optical interface board). 1. Use the optical time-domain reflectometer (OTDR) to test the fiber, and check whether there is a fiber cut and determine the location of the fiber cut according to the attenuation curve of the line shown on the OTDR.
NOTE
The OTDR has a dead zone when it is very close to the fiber.
If... A fiber cut occurs on the line
Then... Replace the fiber and check whether the alarm is cleared. If the alarm persists, see other causes.
No fiber cut occurs on the line See other causes. l Cause 2 of the fiber: The optical interface of the local board is loose, is not connected to the fiber jumper, or is connected to an incorrect fiber jumper (if the alarm is reported by an SDH optical interface board). 1. Check the fiber jumper connected to the optical interface of the local board.
Issue 02 (2011-10-31)
333
If... The connection between the fiber jumper and the interface is loose
Then... Tighten the fiber jumper and check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
The connection between the fiber jumper and the interface is secure 2.
Check whether the tail fiber is connected to the optical interface of the local board properly. If... The fiber jumper is connected improperly Then... According to the networking environment, connect the fiber jumper between optical boards in the subrack properly and check whether the alarm is cleared. If the alarm persists, see other causes. See other causes.
The fiber jumper is connected properly l
Cause 3 of the fiber: The line attenuation is excessively high. As a result, the optical power is excessively low (if the alarm is reported by an SDH optical interface board). 1. Measure the transmit optical power of the opposite board and the receive optical power of the local board. For details, see Querying Optical Power of the Board in the Supporting Task. If... Then...
The transmit optical power of the opposite station is See cause 2 of the board. abnormal The receive optical power of the local station is abnormal 2. Proceed to the next step.
The difference between the transmit optical power of the opposite station and the receive optical power of the local station is the actual optical power attenuation of the line. Compare the result with the line attenuation in the engineering design. If the actual attenuation is excessively high, perform the following steps to find the fault and rectify it. (1) Check whether there are too many optical connectors on the fiber line and whether they are connected to the optical modules securely. If the connectors are loose, insert the connectors into the optical modules securely. (2) Check whether there are aerial optical fiber cable on the fiber line that may be damaged because of bad weather. If yes, provide a protection for the aerial optical fiber cable.
Issue 02 (2011-10-31)
334
(3) Check whether the type of the fiber and the attenuation factor on the fiber line meet the requirements specified in the engineering design document. If not, replace the fiber. (4) Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task to check whether the optical connector in the fiber line is dirty. If the fiber connector is dirty, clean it immediately. For the operations, see the Supporting Task. 3. l Check whether the alarm is cleared. If the alarm persists, see other causes. Cause 1 of the laser: The local optical interface is not used (if the alarm is reported by an SDH optical interface board). 1. Check whether an unused fiber is connected to the optical interface of the board. If yes, perform the self-loop on the receive and transmit optical interfaces by using the unused fiber. Check whether the alarm is cleared. If the alarm persists, see other causes.
2. l
Cause 2 of the laser: The laser at the opposite station is inactive. As a result, no signal is input (if the alarm is reported by an SDH optical interface board). 1. Check whether the laser of the corresponding opposite board is shut down. If yes, switch on the laser on the optical interface. For details, see Opening/Closing Lasers in the Supporting Task. Check whether the alarm is cleared. If the alarm persists, see other causes.
2. l
Causes 1 of the board: The receive board at the local station is fault. As a result, the line receiving fails. 1. Perform a selfloop (hardware inloop) on the receive and transmit interfaces of the board. For details, see Performing Hardware Loopback in the Supporting Task.
CAUTION
CAUTION
The overload of optical power should be avoided when the hardware inloop is performed. According to the optical power specifications of the board, add an optical attenuator on the receive optical interface. For the operations of adding an attenuator, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. If... The alarm is reported No alarm is reported Then... The local board is faulty. Proceed to the next step. See other causes.
Issue 02 (2011-10-31)
335
2.
Replace the optical module or board at the local station. If the board supports pluggable optical module, replace the specific pluggable optical module. Otherwise, replace the faulty board. For details, see Parts Replacement.
Cause 2 of the board: The transmit board (including the cross-connect and timing board) at the opposite station is faulty. As a result, the line transmitting fails. 1. If the opposite board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the opposite faulty board. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see other causes.
2. ----End
Related Information
None.
3.40.2 R_LOS (OTN)

Description
This alarm indicates a loss of signal. This alarm is generated when the receive side receives no signal. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None.

Services through optical port where this alarm is generated are interrupted.
Possible Causes
l l l l Cause 1 for this alarm generated on the client side: The fiber jumper is not connected at the optical port of the board. Cause 2 for this alarm generated on the client side: The line attenuation is excessively high or there is a fiber cut. Cause 3 for this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 for this alarm generated on the WDM side: No fiber jumper is connected to the optical port on the board of the local station, the fiber jumper connected to the optical port is loose, or the fiber jumper is connected incorrectly.
Issue 02 (2011-10-31)
l l l
Cause 2 for this alarm generated on the WDM side: The line attenuation is excessively high or there is a fiber cut. Cause 3 for this alarm generated on the WDM side: The laser of the board at the opposite station is shut down. Cause 4 for this alarm generated on the WDM side: The transmit module of the opposite station or receive module of the local station is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where this alarm is generated. Cause 1 for this alarm generated on the client side: No fiber jumper is connected to the optical port on the board of the local station, the fiber jumper connected to the optical port is loose, or the fiber jumper is connected incorrectly. 1. Check the fiber jumper connection on the board that reports this alarm at the local station. If ... No fiber jumper is connected to the optical port, Then ... Connect the fiber jumper that is connected to the upstream board to the optical port. Check whether the fiber jumper is connected tightly to the optical port. If not, secure the fiber jumper to the optical port.
A fiber jumper is connected to the optical port,
2.
Check whether this alarm is cleared. If the alarm persists, check whether the fiber jumper is connected properly. Reconnect fiber jumpers between boards according to the actual networking environment. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
3. l
Cause 2 for this alarm generated on the client side: The line attenuation is excessively high or there is a fiber cut. 1. 2. Use a test instrument to test the fiber connection to determine whether a fiber break occurs. If yes, replace the fiber. Check whether this alarm is cleared. If the alarm persists, on the U2000 check whether the receive optical power of the optical port is within the normal range. For the optical power specifications of the board, see the Product Description. If ... Then ...
The receive optical power exceeds See IN_PWR_LOW or IN_PWR_HIGH to the normal range, rectify the fault. The receive optical power is normal, Check the relevant fiber connectors. If the fiber connectors are dirty, clean or replace the fiber connectors.
Issue 02 (2011-10-31)
337
3. l
Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm generated on the client side.
Cause 3 for this alarm generated on the client side: The board that reports this alarm is faulty. 1. Apply a hardware loopback between the transmit and receive optical ports on the client side of the board that reports this alarm. If this alarm persists, it indicates that the board is faulty. In this case, replace the board. For details, refer to "Replacing a Board" of the Supporting Tasks. If this alarm is cleared, it indicates that the output power of the client equipment is abnormal. In this case, check for and rectify the fault on the client equipment. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
2. l
Cause 1 for this alarm generated on the WDM side: No fiber jumper is connected to the optical port on the board of the local station, the fiber jumper connected to the optical port is loose, or the fiber jumper is connected incorrectly. 1. Check the fiber jumper connection on the board that reports this alarm at the local station. If ... No fiber jumper is connected to the optical port, A fiber jumper is connected to the optical port, Then ... Connect the optical port properly.
Check whether the fiber jumper is connected tightly to the optical port. If not, secure the fiber jumper to the optical port.
2.
Check whether this alarm is cleared. If the alarm persists, check whether the fiber jumper is connected properly. Reconnect fiber jumpers between boards according to the actual networking environment. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
3. l
Cause 2 for this alarm generated on the WDM side: The line attenuation is excessively high or there is a fiber cut. 1. On the U2000, check whether the receive optical power at the optical port is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If ... Then ...
The receive optical power exceeds See IN_PWR_LOW or IN_PWR_HIGH to the normal range, rectify the fault. The receive optical power is normal, Check the relevant fiber connectors. If there is any dirt or damage, clean or replace the fiber connectors. For how to troubleshoot the specific fault, refer to "Troubleshooting Optical Power Anomalies" of the Troubleshooting.
Issue 02 (2011-10-31)
338
2. l
Cause 3 for this alarm generated on the WDM side: The laser of the board at the opposite station is shut down. 1. 2. On the U2000, check whether the laser on the board at the opposite station is on. If not, open the laser. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4 of this alarm generated on the WDM side.
Cause 4 for this alarm generated on the WDM side: The transmit module of the opposite station or receive module of the local station is faulty. 1. If the alarm persists, check whether the board at the opposite station or the board at the local station supports pluggable optical modules. If ... Then ...
2. ----End
Related Information
Related Cases: l l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides. The LOG board reports the R_LOS alarm on the client side. The FDG board reports the LINK_STATUS alarm. MC-A14 The LWF Board Reports R_LOS MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm on the Board MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified MC-A125 Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case of a fiber break MC-A126 VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm Even If the Attenuation Is Decreased MC-A141 Normal Boards Are Mistakenly Considered Faulty due to Optical Module Characteristics MC-A145 The Client Equipment Interconnected with the TOM Board Reports the R_LOS Alarm Due to a Problem with the Optical Module on the TOM Board
l l l l l l l l
Issue 02 (2011-10-31)
MC-A153 It Is Recommended to Enable the Auto-Negotiation Working Mode at a GE Port When the LPT Function Is Enabled, Or The Services Are Interrupted And The System Reports The R_LOS Alarms MC-A154 The N2SLQ16 Board Interconnected with the TQS Board Reports an R_LOS Alarm Because The TQS Board Emits White Lights When the Input Optical Power Is Normal MC-A156 An SDH Board on the SDH Equipment Reports an R_LOF Alarm When the SDH Board Is Interconnected with a Tributary Board on the OptiX OSN 6800 MC-A159 Services Are Interrupted After the Protection Hold-Off Time Is Set to 10s During Configuration of Client-Side 1+1 Protection on the OptiX OSN 6800, The System Reports The R_LOS Alarm MC-A164 Why the WDM-Side Service Rate Reaches 11.1 Gbit/s When the LSX Board Receives 10GE-LAN Services in Bit Transparent Transmission Mode on the Client Side MC-A182 Receive Optical Power Is Excessively Low Because of The End Face Problem of the Fiber Jumper, The OAU Board Reports The MUT_LOS And R_LOS Alarms MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board Causes Low Receive Optical Power, The Connected OAU Board At The Downstream Station Reports MUT_LOS And R_LOS Alarms help/wdm/com/mc/tt_wdm_mc_0243.xml#tt_wdm_mc_0243 help/wdm/com/mc/tt_wdm_mc_0252.xml#tt_wdm_mc_0252
l l
l l l
l l
3.41 R_OOF
Refer to the alarm page according to the type of the board that reports the alarm. Table 3-39 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm page link 3.41.1 R_OOF (OCS) 3.41.2 R_OOF (OTN)
3.41.1 R_OOF (OCS)

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

l l When the R_OOF alarm is generated, the services are interrupted, and the AIS signal is inserted at the downstream station. When the R_OOF alarm is generated, the system automatically returns the MS_RDI alarm to the upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes
The possible causes of the R_OOF alarm are as follows: l l l l l Cause 1: The receive optical power is excessively low. Cause 2: The receive optical power is excessively high. Cause 3: The transmit optical power of the opposite station is abnormal. Cause 4: The receive board at the local station is faulty (including the fault of the crossconnect board). Cause 5: The transmit board at the opposite station is faulty (including the fault of the crossconnect board).
Procedure
l l Query current alarms on the U2000. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The receive optical power is excessively low. Cause 2: The receive optical power is excessively high. 1. On the U2000, check whether the optical power of the local station is within the normal range. For details on optical power specification of the board, see "Technical Specifications" of the Product Description. For details, see Querying Optical Power of the Board in the Supporting Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the manufacturer information about the optical module on the board.
If... The receive optical power of the local board is excessively low
Issue 02 (2011-10-31)
341
If... The receive optical power of the local board is excessively high 2.
Then... Proceed to step 3.
Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task to check whether the connectors are dirty. If the fiber connector is dirty, clean it immediately. For the operations, see Supporting Task. Cleaning Optical Fiber Connectors Using Cartridge Cleaners Cleaning Optical Fiber Connectors Using Lens Tissue Cleaning Optical Adapters Using Optical Cleaning Sticks Then, check whether the alarm is cleared.
3.
If the alarm persists, check whether the attenuation of the optical attenuator is correct. If the attenuation is not correct, change the value. The value of the optical attenuator depends on the receive optical power of the board. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. If... The optical attenuation is excessively low Then... Decrease the optical attenuation. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Increase the optical attenuation. Then, check whether the alarm is cleared. If the alarm persists, see cause 3.
The optical attenuation is excessively high
4. 5. l 1.
Check whether the fiber is damaged or oppressed. If yes, replace the fiber. Then, check whether the alarm is cleared. If the alarm persists, see cause 3. On the U2000, check whether the transmit optical power of the opposite board is within the normal range. For details on optical power specification of the board, see "Technical Specifications" of the Product Description. For details, see Querying Optical Power of the Board in the Supporting Task.
NOTE
Cause 3: The transmit optical power of the opposite station is abnormal.
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the manufacturer information about the optical module on the board.
2.
If the transmit optical power of the opposite board is abnormal, see the OUT_PWR_HIGH or OUT_PWR_LOW alarm to rectify the fault. Then, check whether the R_OOF alarm is cleared. If the alarm persists, see cause 4.
3. l
Cause 4: The receive board at the local station is faulty (including the fault of the crossconnect board). 1. Perform a selfloop (hardware inloop) on the receive and transmit interfaces of the board. For details, see Performing Hardware Loopback in the Supporting Task.
Issue 02 (2011-10-31)
342
CAUTION
CAUTION
The overload of optical power should be avoided when the hardware inloop is performed. According to the optical power specifications of the board, add an optical attenuator on the receive optical interface. For the operations of adding an attenuator, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. If... The alarm is reported No alarm is reported 2. Then... The local board is faulty. Proceed to the next step. See cause 5.
Replace the optical module or board at the local station. If the board supports the pluggable optical module, replace the pluggable optical module. For details, see Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace the faulty board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, replace the local cross-connect board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see cause 5.
3. 4. l
Cause 5: The transmit board at the opposite station is faulty (including the fault of the crossconnect board). 1. Replace the optical module or board at the opposite station. If the board supports the pluggable optical module, replace the pluggable optical module. For details, see Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace the faulty board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, replace the cross-connect board at the opposite station. For details, see Parts Replacement.
2. ----End
Related Information
None.
3.41.2 R_OOF (OTN)

Description
This alarm indicates out of frame in the receive signals. This alarm is generated when the heads of consecutive five frames fail to be detected.
Attribute
Parameters
None

Services through the optical interface where this alarm is generated are interrupted.
Fault Symptom
Table 3-40 lists the fault symptoms for the R_OOF alarm. Table 3-40 Fault alarms for the R_OOF alarm Fault Symptom The board that reports this alarm also report an IN_PWR_LOW alarm. The board that reports this alarm also reports bit error alarms, such as B1_EXC alarm. Cause Cause 1 for this alarm generated on the WDM side Cause 2 for this alarm generated on the WDM side
NOTE
Possible Causes
l l l l l l Cause 1 for this alarm generated on the client side: The input signals on the client side are abnormal and thus an R_OOF alarm is generated. Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty. Cause 1 for this alarm generated on the WDM side: The attenuation or optical power of the received signals are excessively high. Cause 2 for this alarm generated on the WDM side: A large number of bit errors are generated during the transmission. Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station is faulty. Cause 4 for this alarm generated on the WDM side: The board that reports this alarm is faulty.
Issue 02 (2011-10-31)
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1 for this alarm generated on the client side: The input signals on the client side are abnormal and thus an R_OOF alarm is generated. 1. If this alarm is reported from the client side of the board, apply a hardware loopback between the transmit and receive optical interfaces on the client side of the board. If this alarm on the board persists, it indicates that the board is faulty. In this case, see the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
Configuring a loopback on the board interrupts the services on the board. 2. l If the alarm is cleared, it indicates that the input signals on the client side contain R_OOF signals. In this case, rectify the fault on the client equipment.
Cause 2 for this alarm generated on the client side: The board that reports this alarm is faulty. 1. If the alarm persists, replace the faulty board. If ... Then ...
Cause 1 for this alarm generated on the WDM side: The attenuation or optical power of the received signals excessively high. 1. If the client side reports this alarm, check whether the receive optical power of the interface is within the normal range on the U2000. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
2. 3. l
If the receive optical power is not within the normal range, see IN_PWR_LOW or IN_PWR_HIGH to rectify the fault. If the receive optical power is within the normal range, see the alarm handling procedure for cause 2 of this alarm generated on the WDM side.
Cause 2 for this alarm generated on the WDM side: A large number of bit errors are generated during the transmission.
Issue 02 (2011-10-31)
1. 2.
Check whether there are bit error alarms. If there are bit error alarms, clear the alarms first according to the proper handling procedure. If there is no bit error alarm and the receive optical power is normal, check the fiber connector. If the fiber connector is dirty or damaged, clean or replace the fiber connector. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3 of this alarm generated on the WDM side.
3. l
Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station is faulty. 1. On the U2000, check whether the transmit optical power at the corresponding optical interface on the opposite OTU is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. For details, refer to "Querying Optical Power on the U2000" of the Supporting Tasks. If the transmit optical power exceeds the normal range, it indicates that the opposite board is faulty. In this case, replace the faulty board. If ... Then ...
2.
3. l
If the transmit optical power is within the normal range, see the alarm handling procedure for cause 4 of this alarm generated on the WDM side.
Cause 4 for this alarm generated on the WDM side: The board that reports this alarm is faulty. 1. If the alarm persists, replace the faulty board. If ... Then ...
2. ----End
Related Information
Related Cases:
l l
MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test Because the Line Fiber Loss Is Very Large MC-A115 Determine Whether the Type and Connections Of the Dispersion Compensation Module (DCM) Are Proper When the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD Alarms Are Reported on the WDM Side of LWF Board MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party Equipment
3.42 R_SLIP
Description
This alarm indicates frame slipping on the receive side. The alarm is generated when the phase deviation occurs in the received service frames of the OSC or OTC board. Reported from the WDM side or client side: NA
Attribute
Parameters
None

This alarm has impact on services carried by the OSC. For example, the optical supervisory signals or clock signals are degraded. As a result, the NE is disconnected from the U2000 system.
Fault Symptom
Table 3-41 lists the fault symptom for the R_SLIP alarm. Table 3-41 Fault symptom for the R_SLIP alarm Fault Symptom The board that reports this alarm also report an IN_PWR_HIGH or IN_PWR_LOW alarm. Cause Cause 2: The optical line attenuation is excessively high or the receive optical power is excessively high.
NOTE
Issue 02 (2011-10-31)
347
Possible Causes
l l l l Cause 1: The clock configuration is wrong or the clock signals are not synchronous. Cause 2: The optical line attenuation is excessively high or the receive optical power is excessively high. Cause 3: The fibers at the eastward and westward optical interfaces on the OSC or OTC board are connected reversely. Cause 4: The board that reports this alarm is faulty.
Procedure
l Cause 1: The clock configuration is incorrect or the clock signals are not synchronous. 1. Check whether the clock configuration is correct. If not, reconfigure it to ensure that the clocks of the total network are synchronous. For details on how to configure the clock information, see "Physical Clock" in the Feature Description. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
2. l
Cause 2: The optical line attenuation is excessively high or the receive optical power is excessively high. 1. On the U2000, check whether the receive optical power at the optical interface is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If ... Then ...
The receive optical power is excessively Check the fiber jumper or the fiber low, connector. If the fiber jumper or fiber connector is dirty, clean the fiber connector or replace the fiber jumper. The receive optical power is excessively adjust the optical attenuator to ensure high, that the receive optical power is within the normal range. 2. l Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3.
Cause 3: The fibers at the eastward and westward optical interfaces on the OSC or OTC board are connected reversely. For example, the fibers for connecting to the TM1 optical interface in the west and the TM2 optical interface in the east are connected reversely. See the following figure. 1. If the alarm persists, check the engineering fiber connection diagram to see whether the fibers at the eastward and the westward optical interfaces on the OSC or OTC board are connected reversely. If the fiber connection is incorrect, correct it according to the diagram.
Issue 02 (2011-10-31)
348
OA
F I U RM1 TM2 TM1 RM2 F I U
SC2
OA
2. l
Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 4. If the alarm persists, perform a cold reset on the faulty board on the U2000. If the alarm persists, replace the faulty board. If ... Then ...
Cause 4: The board that reports this alarm is faulty. 1. 2.
Related Information
Related Cases: l MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the OSC Board
None.
3.43 REM_SF
Description
This alarm indicates that remote client-side services are not loaded. This alarm is generated when the client side of the board at the opposite end fails to receive signals (for example, when there is an R_LOS alarm). Reported from the WDM or client side: client side.
Issue 02 (2011-10-31)
349
Attribute
Parameters
None

Services borne by client sides of the board are interrupted.
Fault Symptom
Table 3-42 lists the fault symptom for the REM_SF alarm. Table 3-42 Fault symptom for the REM_SF alarm Fault Symptom The OTU board at the opposite station reports an R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm. Cause Cause 1: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on the client side of the OTU at the opposite station.
NOTE
Possible Causes
l l Cause 1: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on the client side of the OTU board at the opposite station. Cause 2: The client side of the OTU board at the opposite end is faulty.
Procedure
l Cause 1: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on the client side of the OTU board at the opposite station. 1. On the U2000, check whether an R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on the client side of the OTU board at the opposite station. If yes, see R_LOS, R_LOF, R_LOC, MS_AIS, LINK_ERR to clear the alarm. Replace the OTU board at the opposite station.
Cause 2: The client side of the OTU board at the opposite end is faulty. 1.
Issue 02 (2011-10-31)
If ...
Then ...
Related Information
None.
3.44 REMOTE_FAULT
Description
This alarm indicates a fault at the remote end. Reported from the WDM side or client side: Client side
Attribute
Parameters
None

If the board receives the REMOTE_FAULT alarm, the services may be interrupted.
Fault Symptom
Table 3-43 lists the fault symptom for the REMOTE_FAULT alarm. Table 3-43 Fault symptom for the REMOTE_FAULT alarm Fault Symptom A LOCAL_FAULT alarm is reported from the client side of the board at the opposite end.
Issue 02 (2011-10-31)
Cause Cause 1: The opposite station receives a LOCAL_FAULT alarm.

351
NOTE
Possible Causes
l Cause 1: The opposite station receives a LOCAL_FAULT alarm. See the following figure. The client side of OTU board at station A detects a LOCAL_FAULT alarm, and the client side of the OTU board at station B reports a REMOTE_FAULT alarm.
Client side
O T U
WDM side
WDM side
O T U
Client side
Station A Detects and reports the LOCAL_FAULT alarm
Station B Detects and reports the REMOTE_FAULT alarm
Cause 2: The board at the opposite station is faulty.
Procedure
l Cause 1: The opposite station receives a LOCAL_FAULT alarm. 1. 2. l Clear the LOCAL_FAULT alarm at the opposite station. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Replace the faulty board at the opposite station. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 2: The board at the opposite station is faulty. 1. 2.
----End
Related Information
None.
Issue 02 (2011-10-31)
352
3.45 SECU_ALM
Description
The SECU_ALM is a security alarm. This alarm is generated when login fails after four consecutive login failures performed by the same user. Reported from the WDM side or client side: NA
Attribute
Alarm Severity Major Alarm Type Security alarm
Parameters
None.

The alarm automatically ends with no impact on the system.
Fault Symptom
None.
NOTE
Possible Causes
l Cause 1: This alarm can be caused by illegal login. For example, the password is incorrect or the user does not exist.
Procedure
l Cause 1: This alarm can be caused by illegal login. For example, the password is incorrect or the user does not exist. 1. 2. ----End Check whether invalid users exist in the user list in the login window. If yes, delete the invalid users from the user list. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Related Information
None.
3.46 SUBRACK_ID_CONFLICT
Description
This alarm indicates a conflict of subrack IDs. In the case of the master-slave subrack mode, this alarm is reported when the master subrack detects that the DIP switch settings of the slave subracks are repeated.
Attribute
Parameters
Parameter Parameter 1 Description Indicates the conflict subrack ID.

The inter-subrack communication is abnormal. As a result, the master subrack cannot manage the slave subrack.
Fault Symptom
Table 3-44 lists the fault symptom for the SUBRACK_ID_CONFLICT alarm. Table 3-44 Fault symptom for the SUBRACK_ID_CONFLICT alarm Fault Symptom The board may report the BD_STATUS, COMMUN_FAIL, and WRG_BD_TYPE alarms at the same time. Cause l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in the system. l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave subracks are repeated.
NOTE
Issue 02 (2011-10-31)
354
Possible Causes
The possible causes of the SUBRACK_ID_CONFLICT alarm are as follows: l l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in the system. Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave subracks are repeated.
Procedure
l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in the system. 1. 2. 3. 4. l There should be only one master subrack in the system. Check which master subrack is redundant according to the actual networking and then remove it. Perform a warm reset on the SCC board in the master subrack. Perform a warm reset on all boards on the NE. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave subracks are repeated. 1. Disconnect one slave subrack from the master subrack, and re-set the ID of this slave subrack by changing the DIP switch setting on the SCC board. In this case, the IDs of the two slave subracks are different. Perform a warm reset on the SCC board in the master subrack on the NE. For details, see "Performing a Warm Reset on the Board" in the Supporting Tasks. After the subrack ID is changed, perform a warm reset on all the boards in the subrack. For details, see "Performing a Warm Reset on the Board" in the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
2. 3. 4. ----End
Related Information
For details, see "Master-Slave Subrack" in the Feature Description.
3.47 SUM_INPWR_LOW
Description
Sum input optical power is excessively low. The alarm is generated when the input optical power of the multiplexed signals is lower than the threshold. This alarm is reported from neither the WDM side nor the client side.
Issue 02 (2011-10-31)
355
Attribute
Parameters
None.

The output optical signals of a single channel of the board may be lost; the services in use may have bit errors or even are interrupted.
Fault Symptom
Table 3-45 lists the fault symptom for the SUM_INPWR_LOW alarm. Table 3-45 Fault symptom for the SUM_INPWR_LOW alarm Fault Symptom The upstream board reports an OUT_PWR_LOW alarm. Cause Cause 1: The output optical power of the upstream station decreases, and thus the input optical power of the local station is excessively low.
NOTE
Possible Causes
l l l Cause 1: The output optical power of the upstream station decreases, and thus the input optical power of the local station is excessively low. Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber connectors are dirty. Cause 3: The board that reports this alarm is faulty.
Procedure
l l Check the alarm information on the U2000 and record the IDs of the port and channel where the alarm is generated. Cause 1: The output optical power of the upstream station decreases and thus the input optical power of the local station is excessively low. 1. On the U2000, check the output optical power of the boards at the upstream station along the reverse direction of the signal flow. If the output optical power of a certain
Issue 02 (2011-10-31)
board is excessively low, adjust the output optical power of the board to a value within the normal range. 2. 3. l If the alarm persists, replace the board whose output optical power is excessively low. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2.
Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber connectors are dirty. 1. If the output optical power of all the boards at the upstream stations is normal, check whether an optical attenuator with excessively high attenuation is attached to the receive optical interface on the board that reports this alarm. If yes, decrease the attenuation of the optical attenuator to a proper value or replace the optical attenuator with a proper one. If the alarm persists, check whether the attenuation of the built-in VOA in the upstream boards is excessively high. If yes, adjust the attenuation of the VOA to a proper value. If the alarm persists, check whether related fibers or fiber connectors are dirty. If yes, replace the fiber jumpers or check and clean the fiber connectors. If the alarm persists, the optical cables between stations may be faulty. In this case, rectify the fault on the optical cables. Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 3. If the alarm persists, replace the faulty board. If ... Then ...
2. 3. 4. 5. l
Cause 3: The board that reports this alarm is faulty. 1.
2. ----End
Related Information
None.
3.48 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that the file is lost. The alarm occurs when the SCC checks the software package and finds that a file in a partition of the SCC software
package is lost and the file cannot be restored from the related file in another partition. Next time when the SCC checks the software package and finds the file, the alarm is cleared.
NOTE
The SCC checks the software package every time when it starts up and when the periodical check is performed. The periodical check is performed every hour by default.
Attribute
Alarm Severity Critical Alarm Type Process alarm
Parameters
None

Because a file in the SCC software package is lost, there may be an impact on the normal operation of certain functions of the NE.
Fault Symptom
Table 3-46 lists the fault symptom for the SWDL_NEPKGCHECK alarm. Table 3-46 Fault symptom for the SWDL_NEPKGCHECK alarm Fault Symptom The SWDL_NEPKGCHECK alarm persists. Cause Cause 1: The same file in two partitions in the SCC software package of the SCC board is lost and cannot be restored. Cause 2: A file in a partition of the SCC software package is lost and the file cannot be restored from the associated file in another partition.
The SWDL_NEPKGCHECK alarm disappears after being reported for a certain period and is reported again.
NOTE
Possible Causes
l l Cause 1: The same file in two partitions in the SCC software package is lost and cannot be restored. Cause 2: A file in a partition of the SCC software package is lost and the file cannot be restored from the associated file in another partition.
Issue 02 (2011-10-31)
Procedure
l Causes 1 and 2: The same file in two partitions in the SCC software package is lost and cannot be restored. A file in a partition of the SCC software package is lost and the file cannot be restored from the associated file in another partition. 1. 2. ----End Select the software package of the same version to perform a package loading on the NMS. After successful package loading, the alarm is removed automatically. If the alarm persists, contact Huawei engineers.
Related Information
None
3.49 TD
Description
This alarm indicates that the transmitter is degraded. The TD alarm threshold of the laser is set to a value 1.2 times of the initial value of the bias current. The TD alarm is generated when the bias current of the laser exceeds the threshold and is smaller than the initial value by 1.5 times. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None.

Possibly the board laser cannot work normally, or the output light of the laser is of low quality or with bit errors and further cause service break.
Fault Symptom
None.
NOTE
Issue 02 (2011-10-31)
359
Possible Causes
Cause 1: The laser is aging. Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser is aging. 1. Check whether board that reports this alarm supports pluggable optical modules. If ... Then ...
Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 2: The detection circuit of the board is faulty. 1. 2.
----End
Related Information
In a cooling optical module that adopts the automatic level control (ALC) function, the laser is aged after long-term operation and thus the laser emitting efficiency decreases. To ensure constant output optical power, the laser bias current, an index that reflects the laser aging degree, needs to be increased.
3.50 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature crosses the threshold. This alarm occurs, when the system detects that the board working temperature is higher than the upper threshold or lower than the lower threshold. Reported from the WDM side or client side: NA
Issue 02 (2011-10-31)
360
Attribute
Parameters
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The excessively high or low temperature puts the system in a highly dangerous state. If the system runs in this state for a long time, bit errors may be generated and services may be interrupted. Hence, the TEMP_OVER alarm must be handled in time.
Fault Symptom
Table 3-47 lists the fault symptom for the TEMP_OVER alarm. Table 3-47 Fault symptom for the TEMP_OVER alarm Fault Symptom On the NMS, the adjusting mode of the fan board is set to Adjustable Speed Mode and the rotating speed is set to Low Speed or Medium Speed. The fan board reports the FAN_FAIL or FAN_FAULT alarm. The adjusting mode of the fan board is set to Auto Speed Mode and the rotating speed is set to High Speed. In addition, no other alarms are generated. The fan board reports the BD_STATUS alarm. Cause Cause 1: The set rotating speed of the fan board is excessively low.
Cause 2: The fan board is faulty. Cause 3: The air filter is excessively dusty.
Cause 5: The fan is not in position.
Issue 02 (2011-10-31)
361

NOTE
Possible Causes
The possible causes of the TEMP_OVER alarm are as follows: l l l l l l Cause 1: The set rotating speed of the fan board is excessively low. Cause 2: The fan board is faulty. Cause 3: The ambient temperature is excessively high or excessively low due to a cooler or heater equipment fault. Cause 4: The fan is not in position. Cause 5: The board that reports the alarm is faulty. Cause 6: The air filter is excessively dusty.
Procedure
l Query the alarm parameter on the U2000. If the parameter is 0x01, handle the alarm according to causes 1 to 6. If the parameter is 0x02, handle the alarm according to causes 3 and 5. Cause 1: The set rotating speed of the fan board is excessively low. 1. Check the adjusting mode and rotating speed of the fan board on the NMS. If the adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or Medium Speed, change the rotating speed to High Speed or the adjusting mode to Auto Speed Mode. Check whether the alarm is cleared. If the alarm persists, see cause 2. If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is generated on the fan board. If yes, handle the alarm in advance. Check whether the alarm is cleared. If the alarm persists, see cause 3.
2. l 1. 2. l
Cause 2: The fan board is faulty.
Cause 3: The ambient temperature is excessively high or excessively low due to a cooler or heater equipment fault. 1. Check whether the ambient temperature of the equipment room is higher than 45C or lower than 0C. If the temperature is higher than 45C or lower than 0C, use a cooler or heater to decrease or increase the ambient temperature.
NOTE
The TEMP_OVER alarm is cleared when the board temperature is 5C lower than the upper threshold or 5C higher than the lower threshold so that intermittent TEMP_OVER alarms can be prevented.
2. l 1. 2. l
Issue 02 (2011-10-31)
Check whether the alarm is cleared. If the alarm persists, see Cause 5. Check whether the NE reports the BD_STATUS alarm or check whether the fan is in position on the U2000. If the fan is not in position, place it firmly. Check whether the alarm is cleared. If the alarm persists, see Cause 6.
Cause 4: The fan is not in position.
Cause 5: The board that reports the alarm is faulty.

1. l 1.
Replace the board that reports the alarm. For details, see the Parts Replacement. If the alarm persists, check whether the air filter is excessively dusty, causing the problem of heat dissipation. You can feel the wind and the temperature of the wind at the air exhaust vent. If the problem is caused by dusty the air filter, remove the air filter and clean it. For details, see Cleaning the Air Filter in the Supporting Tasks. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
Cause 6: The air filter is excessively dusty.
2. 3. ----End
Related Information
None
3.51 TF
Description
This alarm indicates a transmission failure. This alarm is generated when the transmit optical power of the laser exceeds the threshold of the output optical power of the laser. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

The laser transmission becomes faulty, and a service interruption occurs.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the TF alarm are as follows: Cause 1: The laser module is damaged, or the laser is aging.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser module is damaged, or the laser is aging. 1. Check whether the board that reports this alarm supports pluggable optical modules. If ... Then ...
2. l
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Perform a cold reset on the faulty board through the U2000. If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 2: The detection circuit of the board is faulty. 1. 2. 3.
----End
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after longterm operation and therefore the laser emitting efficiency decreases. To ensure constant output optical power, the laser bias current needs to be increased. Hence, the bias current is an index that reflects the aging degree of the laser. Related Cases: l l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station MC-A12 Certain Boards Report the TF Alarm Transiently
3.52 TS_CFG_MISMATCH
Description
This alarm indicates a timeslot mistach. This alarm is generated when the configured timeslot of one board at the local station is inconsistent with the timeslot transmitted from the opposite station. Reported from the WDM side or client side: WDM side
Issue 02 (2011-10-31)
364
Attribute
Alarm Severity Major Alarm Type Processing
Parameters
None

If a timeslot mismatch occurs, the service cannot be received properly.
Fault Symptom
None.
NOTE
Possible Causes
Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with the received timeslot.
Procedure
l Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with the received timeslot. 1. Check whether the value of Timeslot Configuration Mode of the board that reports this alarm is the same as the value of Timeslot Configuration Mode of the corresponding board at the opposite station. If not, set them to Automatic. For details on how to configure the service timeslots, see "Configuring Service Timeslots" in the Configuration Guide. If the mode is consistent, check whether the timeslot configuration at the transmit end of the opposite board is consistent with the timeslot configuration at the receive end of the local board. If not, modify the timeslot configuration of the opposite board or the local board according to the actual service. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
2.
3. ----End
Related Information
None.
Issue 02 (2011-10-31)
365
3.53 WRG_BD_TYPE
Description
This alarm indicates that the type of the board is incorrect. This alarm is generated when the logical board and the physical board are inconsistent.
Attribute
Parameters
None

The type of the logical board is different from the type of the physical board. The board cannot work normally.
Fault Symptom
NOTE
None.
Possible Causes
The possible causes of the WRG_BD_TYPE alarm are as follows: l l Cause 1: The type of the logical board configured on the U2000 is different from the type of the physical board installed in the slot. Cause 2: The board that reports this alarm is faulty.
Procedure
l Cause 1: The type of the logical board configured on the U2000 is different from the type of the physical board installed in the slot. 1. On the U2000, check whether the type of the logical board is the same as the type of the physical board installed in the corresponding slot. If not, determine whether the type of logical board or the type of the physical board is inappropriate according to the engineering configuration requirements. If the type of the logical board is inappropriate, reconfigure the logical board on the U2000.
If the type of the physical board is appropriate, remove the existing board and then insert another board of the correct type. 2. l Check whether this alarm is cleared. If the alarm persists, see the alarm handling procedure for cause 2. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks.
CAUTION
Exercise caution when replacing the SCC board. For details on how to replace the SCC board and the precautions, see the Parts Replacement. 2. ----End Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Related Information
None.
Issue 02 (2011-10-31)
367
4 Alarm Processing
4
About This Chapter
NOTE NOTE
Alarm Processing
This topic describes information relevant to alarm handling, including alarm descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.
By default, optical-layer alarms (OTS, OMS, and OCH alarms) are not reported. You can enable opticallayer alarm reporting as required using the NMS. For details, see "Enabling/Disabling Supervision on the Optical Layer" in the Supporting Tasks.
If the fault of an alarm cannot be located, contact Huawei engineers for troubleshooting.
The alarm handling involves board reset, either of cold or warm. Warm reset and cold reset have different impacts on services. l Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software, which neither updates the FPGA or hardware data nor interrupts services. A cold reset of the SCC may result in reconfiguration of the key hardware, such as FPGA reloading; the upper-layer software need be restarted. Reset of other boards: a reset of software on other boards does not affect running services while a reset of hardware on other boards does. A mis-reset of such a board affects the communication between this board and the SCC and even interrupts services.
The handling measures of certain alarms in this topic vary according to the boards that report these alarms, and therefore the handling measures of these alarms are described according to the systems (OCS and OTN systems) that the boards belong to. 4.1 AD_CHECK_FAIL 4.2 ALC_ADJUST_FAIL 4.3 ALC_WAIT_ADJUST 4.4 ALS_ACTIVE 4.5 ALM_ALS 4.6 APS_MANUAL_STOP
4 Alarm Processing
4.7 ALM_GFP_dCSF 4.8 ALM_GFP_dLFD 4.9 ALM_HANGUP 4.10 ALM_TC_OEI 4.11 ALM_TC_REI 4.12 APE_ADJUST_FAIL 4.13 APE_ADJUST_PEND 4.14 APS_FAIL 4.15 APS_INDI 4.16 AU_AIS 4.17 AU_LOP 4.18 B1_SD See the alarm page according to the type of the board that reports the alarm. 4.19 B2_EXC 4.20 B2_SD 4.21 B3_EXC 4.22 B3_EXC_VC3 4.23 B3_EXC_VC4 4.24 B3_SD 4.25 B3_SD_VC3 4.26 B3_SD_VC4 4.27 BD_NOT_INSTALLED 4.28 BD_STATUS See the alarm page according to the type of the board that reports the alarm. 4.29 CFCARD_FAILED 4.30 BDID_ERROR 4.31 C2_VCAIS 4.32 CHAN_ADD 4.33 CHIP_ABN 4.34 CLIENT_PROT_NOTSTART 4.35 CLIENT_PORT_STA_INDI 4.36 CLK_NO_TRACE_MODE 4.37 CRC4_CROSSTR 4.38 DB_RESTORE_FAIL
4 Alarm Processing
4.39 DBPS_ABNORMAL 4.40 DBMS_ABNORMAL 4.41 DBMS_ERROR 4.42 DBMS_PROTECT_MODE 4.43 DCM_INSUFF 4.44 DLAG_PROTECT_FAIL 4.45 DSP_LOAD_FAIL 4.46 ETH_CFM_LOC 4.47 ETH_CFM_MISMERGE 4.48 ETH_CFM_MACSTATUS 4.49 ETH_CFM_RDI 4.50 ETH_CFM_UNEXPERI 4.51 ETH_MISCONNECT 4.52 ETH_SERVICE_CONFIG_FAIL 4.53 ETHOAM_DISCOVER_FAIL 4.54 ETHOAM_RMT_CRIT_FAULT 4.55 ETHOAM_RMT_LOOP 4.56 ETHOAM_RMT_SD 4.57 ETHOAM_SELF_LOOP 4.58 ETHOAM_VCG_SELF_LOOP 4.59 EX_ETHOAM_MPID_CNFLCT 4.60 EXT_MODULE_OFFLINE 4.61 EXT_SYNC_LOS 4.62 EXT_TIME_LOC 4.63 FAN_FAIL 4.64 FAN_FAULT 4.65 FEATURE_WITHOUT_LICENSE 4.66 FC_8B10BERR_OVER 4.67 FCS_ERR 4.68 FEC_LOF 4.69 FEC_OOF 4.70 FLOW_OVER 4.71 FPGA_ABN
4 Alarm Processing
4.72 FSELECT_STG 4.73 FWD_PKT_LOSS 4.74 GAINDATA_MIS 4.75 HARD_BAD 4.76 HARD_ERR 4.77 HP_LOM 4.78 HP_RDI 4.79 HP_REI 4.80 HP_SLM 4.81 HP_TIM 4.82 HP_UNEQ 4.83 HSC_UNAVAIL 4.84 INTRA_OTU_STA_INDI 4.85 IPA_SHUT 4.86 J0_MM 4.87 K1_K2_M 4.88 K2_M 4.89 L_SYNC 4.90 LAN_LOC 4.91 LAG_PORT_FAIL 4.92 LAG_VC_PORT_FAIL 4.93 LASER_HAZARD_WARNING 4.94 LASER_SHUT 4.95 LCS_DAYS_OF_GRACE 4.96 LCS_EXPIRED 4.97 LCS_FILE_NOT_EXIST 4.98 LCAS_FOPR 4.99 LCAS_FOPT 4.100 LCAS_PLCR 4.101 LCAS_PLCT 4.102 LCAS_TLCR 4.103 LCAS_TLCT 4.104 LOCAL_FAULT
4 Alarm Processing
4.105 LOCK_CUR_FAIL 4.106 LOCKPOW_MIS 4.107 LP_RDI_VC3 4.108 LP_SLM_VC3 4.109 LP_UNEQ_VC3 4.110 LPT_RFI 4.111 LSR_COOL_ALM 4.112 LSR_FORCE_OPEN 4.113 LSR_INVALID 4.114 LTI 4.115 MAINBD_SUBBD_MISMATCH 4.116 MOD_COM_FAIL 4.117 MODULE_ADJUST_FAIL 4.118 MODULE_COOLCUR_OVER 4.119 MODULE_TEMP_OVER 4.120 MODULEFILE_UPDATE_FAIL 4.121 MS_CROSSTR 4.122 MS_REI 4.123 MS_SNCP_PS 4.124 MS_SNCP_STA_INDI 4.125 MS_APS_INDI_EX 4.126 MULTI_RPL_OWNER 4.127 NEBD_XC_DIF 4.128 NESF_LOST 4.129 NESTATE_INSTALL 4.130 NO_BD_PARA 4.131 NO_BD_SOFT 4.132 NO_ELABEL 4.133 NODEID_MM 4.134 NTP_SYNC_FAIL 4.135 NULL_SEND 4.136 OCH_FDI 4.137 OCH_FDI-O
4 Alarm Processing
4.138 OCH_FDI-P 4.139 OCH_LOS-P 4.140 OCH_OCI 4.141 OCH_SSF 4.142 OCH_SSF-O 4.143 OCH_SSF-P 4.144 ODU_AIS 4.145 ODU_LCK 4.146 ODU_OCI 4.147 ODU_SNCP_STA_INDI 4.148 ODUk_LOFLOM 4.149 ODUk_PM_LCK 4.150 ODUk_PM_OCI 4.151 ODUk_PM_TIM 4.152 ODUk_TCMn_AIS 4.153 ODUk_TCMn_BDI 4.154 ODUk_TCMn_DEG 4.155 ODUk_TCMn_EXC 4.156 ODUk_TCMn_LCK 4.157 ODUk_TCMn_LTC 4.158 ODUk_TCMn_OCI 4.159 ODUk_TCMn_SSF 4.160 ODUk_TCMn_TIM 4.161 ODUKSP_PS 4.162 ODUKSP_STA_INDI 4.163 OH_LOOP 4.164 OLP_PS 4.165 OLP_STA_INDI 4.166 OMS_BDI 4.167 OMS_BDI-O 4.168 OMS_BDI-P 4.169 OMS_FDI-O 4.170 OMS_FDI-P
4 Alarm Processing
4.171 OMS_LOS-P 4.172 OMS_SSF 4.173 OMS_SSF-O 4.174 OMS_SSF-P 4.175 OOL 4.176 OOS_LOST 4.177 OPA_FAIL_INDI 4.178 OPU1_MSIM 4.179 OPU1_VCAT_SQM 4.180 OPU1_VCAT_VcPLM 4.181 OPU2_MSIM 4.182 OPU3_MSIM 4.183 OPUk_PLM 4.184 OSC_BDI 4.185 OSC_DEG 4.186 OSC_RDI 4.187 OTS_BDI 4.188 OTS_BDI-O 4.189 OTS_BDI-P 4.190 OTS_LOS-O 4.191 OTS_LOS-P 4.192 OTS_TIM 4.193 OTU_AIS 4.194 OTU_LOF 4.195 OTU_LOM 4.196 OTUk_AIS 4.197 OTUk_BDI 4.198 OTUk_DEG 4.199 OTUk_EXC 4.200 OTUk_LOM 4.201 OTUk_TIM 4.202 OUT_PWR_LOW 4.203 OWSP_PS
4 Alarm Processing
4.204 OWSP_STA_INDI 4.205 PATCH_ACT_TIMEOUT 4.206 PATCH_DEACT_TIMEOUT 4.207 PATCH_PKGERR 4.208 PM_BDI 4.209 PM_BEI 4.210 PM_BIP8_OVER 4.211 PM_BIP8_SD 4.212 PM_TIM 4.213 PORTSWITCH_FAIL 4.214 POWER_ABNORMAL 4.215 POWER_DIFF_OVER 4.216 PRBS_LSS 4.217 PUM_BCM_ALM 4.218 PUM_TEM_ALM 4.219 R_LOC See the alarm page according to the type of the board that reports the alarm. 4.220 RELAY_ALARM_CRITICAL 4.221 RELAY_ALARM_IGNORE 4.222 RELAY_ALARM_MAJOR 4.223 RELAY_ALARM_MINOR 4.224 REM_SD 4.225 RL_CRITICAL_HI 4.226 RL_CRITICAL_LOW 4.227 RS_CROSSTR 4.228 RTC_FAIL 4.229 S1_SYN_CHANGE 4.230 SCC_LOC 4.231 SEC_RADIUS_FAIL 4.232 SERVICE_TYPE_EXCEED_LICENSE 4.233 SERVICE_CAPACITY_EXCEED_LICENSE 4.234 SHELF_AREA_POWER_OVER 4.235 SPAN_LOSS_HIGH
4 Alarm Processing
4.236 SPAN_LOSS_LOW 4.237 SLAVE_WORKING 4.238 SM_BDI 4.239 SM_BEI 4.240 SM_BIP8_OVER 4.241 SM_BIP8_SD 4.242 SM_IAE 4.243 SM_TIM 4.244 SNCP_FAIL 4.245 SO_SK_MISMATCH 4.246 SPEED_OVER 4.247 STORM_CUR_QUENUM_OVER 4.248 SUBRACK_COMM_PS 4.249 SUBRACK_ID_MISMATCH 4.250 SUBRACK_LOOP 4.251 SUBRACK_TYPE_MISMATCH 4.252 SUM_INPWR_HI 4.253 SW_SNCP_PS 4.254 SW_SNCP_STA_INDI 4.255 SWDL_ACTIVATED_TIMEOUT 4.256 SWDL_AUTOMATCH_INH 4.257 SWDL_BD_EXCLUDE 4.258 SWDL_CHGMNG_NOMATCH 4.259 SWDL_COMMIT_FAIL 4.260 SWDL_INPROCESS 4.261 SWDL_PKG_NOBDSOFT 4.262 SWDL_PKGVER_MM 4.263 SWDL_ROLLBACK_FAIL 4.264 SYN_BAD 4.265 SYNC_C_LOS 4.266 SYNC_DISABLE 4.267 SYNC_F_M_SWITCH 4.268 SYNC_LOCKOFF
4 Alarm Processing
4.269 SYNC_FAIL 4.270 SYSPARA_CFDB_NOSAME 4.271 T_LOSEX 4.272 T_SLIP 4.273 TEM_HA 4.274 TEM_LA 4.275 TEST_STATUS 4.276 THUNDERALM 4.277 TIME_LOS 4.278 TIME_NO_TRACE_MODE 4.279 TR_LOC 4.280 TU_AIS_VC3 4.281 TU_LOP_VC3 4.282 VCAT_LOA See the alarm page according to the type of the board that reports the alarm. 4.283 VCAT_LOM_VC3 4.284 VCAT_LOM_VC4 4.285 VLAN_SNCP_PS 4.286 VOA_ADJUST_FAIL 4.287 VOADATA_MIS 4.288 W_R_FAIL 4.289 WAVE_ADD_ABN 4.290 WAVE_DROP_ABN 4.291 WAVEDATA_MIS 4.292 WAVELEN_OVER 4.293 XC_UNSWITCH
Issue 02 (2011-10-31)
377
4 Alarm Processing
4.1 AD_CHECK_FAIL
Description
The AD_CHECK_FAIL alarm is an alarm indicating AD (analog to digital converter) self check failure. This alarm is reported when the AD chip on the board is faulty. Reported from the WDM side or client side: NA.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.

l l This alarm may affect services. Parameters relevant to the AD chip on the board, such as board input/output optical power, back facet current and cooling current, fail to be queried on the U2000. As a result, maintenance engineers can neither obtain the current operation performance data of the network nor find in time any dormant problems of the network operation. The alarm may interrupt the service in the system or even make the system down. Hence, this alarm should be handled immediately.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Perform a cold reset on the faulty board through the U2000. Step 2 If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
4 Alarm Processing
Related Information
None
4.2 ALC_ADJUST_FAIL
Description
ALC link adjustment failure. This alarm is generated when the ALC link adjustment fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Meaning Indicates the ALC link number. Indicates the adjustment failure cause. l 0x01: The board does not respond. l 0x02: There is an equipment alarm. l 0x03: Adjustment frames are received but the link is absent from the link. l 0x04: The link operation times out. l 0x05: The node operation times out. l 0x06: The node status is incorrect. l 0x07: The node does not allow adjustment. l 0x08: The link configuration is in disorder.
Issue 02 (2011-10-31)
379
4 Alarm Processing
Name
Meaning
Parameter 3 and Parameter 4 l When Parameter 2 is 0x01, it indicates the no-response slot. l When Parameter 2 is 0x02, it indicates the slot of the board and optical interface. l When Parameter 2 is 0x03, Parameter 3 indicates the link number. l When Parameter 2 is 0x04, it indicates the timeout period. l When Parameter 2 is 0x05, it indicates the timeout period. l When Parameter 2 is 0x06, Parameter 3 indicates the node state. Parameter 5 and Parameter 6 l When Parameter 2 is 0x01, it indicates the port number. l When Parameter 2 is 0x02, it indicates the port number. Parameter 7 and Parameter 8 When Parameter 2 is 0x01, it indicates the command.

The line attenuation is excessive and cannot be compensated by adjusting the intra-NE attenuation or gain. In this case, the service signals may be instable and the BER may increase.
Possible Causes
l l l l l l l l The board does not respond to a query. Alarms such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, and R_LOS occur on the equipment. The node receives adjustment frames but no link is on the node. The link adjustment operation times out. The node adjustment operation times out. The node is in an incorrect node. That is, though receiving adjustment frames, the node is not in the pre-adjustment state. The node does not permit adjustment and there are more than two retries of adjustment. The link configuration is in disorder.
Procedure
Step 1 Check whether the ALC configuration is normal. The configuration rules are as follows: l The sink node cannot be configured as a reference node. l Reference equipment must be configured for the source node. l The detection board should not be empty for a non-reference node. l When the detection board is OBU1, the adjustment equipment should not be empty. l When configuring the source node, make sure that the same optical interface is not configured for the detection equipment and reference equipment. Step 2 Check whether the adjustment on the adjustment node is within the range.
4 Alarm Processing
Step 3 Check whether other alarms, such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, or R_LOS, exist on the current equipment on the U2000. If an alarm occurs on the equipment, first rectify the alarm. Step 4 If the adjustment times out, re-start adjustment. ----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.3 ALC_WAIT_ADJUST
Description
ALC link anomaly and wait for adjustment. This alarm is generated when the ALC link in manual mode is faulty and needs to be adjusted, this alarm is reported at the source node.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Meaning Indicates the ALC link number. Indicates the node ID of the faulty node.
Parameter 3, Parameter 4, Parameter 5, Parameter 6 Indicates the NE ID of the faulty node.

The line attenuation is excessive and may affect signal quality.
Possible Causes
l Currently, the ALC is in the manual mode. When the ALC link has anomaly and needs to be adjusted, this alarm is reported.
Issue 02 (2011-10-31)
4 Alarm Processing
Procedure
Step 1 Manually start ALC adjustment. Step 2 Change the current ALC to automatic adjustment mode. ----End
Related Information
4.4 ALS_ACTIVE
Description
ALS (automatic laser shutdown function) occurred alarm. When the laser is disabled based on the ALS protocol, an ALS_ACTIVE alarm is reported.
Attribute
Parameters
None

When the alarm is generated, the related boards laser is shut down automatically.
Possible Causes
l l The input signals on the client side is missing at the local station. The WDM-side of the related boards is faulty.
Procedure
Step 1 On the U2000, query whether the client-side of the related boards has the R_LOS alarm. If that is the case, handle the alarms according to the corresponding handling procedure. Step 2 On the U2000, query whether the WDM-side of the related boards have the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI or ODUk_TCMn_LCK alarms. If that is the case, handle the alarms according to the corresponding handling procedure. ----End
4 Alarm Processing
Related Information
The OTU board and tributary board of the system provide the automatic laser shutdown (ALS) function. For details, see "ALS" in the Feature Description.
4.5 ALM_ALS
Description
The ALM_ALS alarm in an alarm related to the automatic laser shutdown (ALS) function. When a board enables the ALS function and the R_LOS alarm is generated at the optical interface, the laser is shut down automatically. In this case, the board reports the ALM_ALS alarm.
Attribute
Parameters
None

When the ALM_ALS alarm is generated, the system is not affected. This alarm just indicates that the ALS function of the laser is enabled.
Possible Causes
The ALS function is enabled on the U2000 or the Navigator.
Procedure
Step 1 When the ALS function is disabled, the alarm is cleared automatically. ----End
Related Information
None
4.6 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is manually stopped.
4 Alarm Processing
Attribute
Alarm Severity Minor Alarm Type Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the MSP group type. l 0x01: linear MSP group l 0x02: ring MSP group Parameter 2, Parameter 3 Indicates the MSP group ID.

The MSP switching protocol of the corresponding MSP group fails to function. Accordingly, the MSP fails.
Possible Causes
The MSP protocol of the corresponding MSP group is manually stopped.
Procedure
Step 1 View on the U2000 and confirm the MSP subnet where the protocol is stopped. Step 2 Restart the MSP protocol of the protection group, and the alarm is cleared. ----End
Related Information
None
4.7 ALM_GFP_dCSF
Issue 02 (2011-10-31)
384
4 Alarm Processing
Description
The ALM_GFP_dCSF is an alarm indicating the loss of the GFP client signal. When the source end cannot receive the client signal, it sends the management frame to the sink end. When the sink end receives the management frame, this alarm is reported.
Attribute
Parameters
None

During data transmission, the source end cannot receive the client signal. The services lose packets or are interrupted.
Possible Causes
l l The interface module at the source end is faulty. For example, the optical module is absent or does not match, or the optical/electrical signal is lost. The physical link at the source end fails, and it cannot normally receive the physical signal.
Procedure
Step 1 View the ALM_GFP_dCSF alarm on the U2000, and then determine the number of the VCTRUNK where this alarm is generated. Step 2 Check whether the physical link at the source end of the VCTRUNK where the uplink service is configured is normal. For example, check whether the physical link is invalid because the fiber is damaged. If the fiber is damaged, replace the fiber and then check whether the alarm is cleared. Step 3 If the alarm persists, check whether the interface module at the source end is normal. If not, replace the optical module. Step 4 If the alarm persists, replace the board that reports the alarm. ----End
Related Information
None
4.8 ALM_GFP_dLFD
4 Alarm Processing
Description
The ALM_GFP_dLFD is an alarm indicating the loss of generic framing procedure (GFP) frame delineation. If the alarm is reported when the delimitation state machine of the GFP leaves the SYNC state of the delimitation processing; the alarm is cleared when the state is SYNC again.
Attribute
Parameters
None

During the data transmission, failure in the GFP framing causes service interruption.
Possible Causes
l l Cause 1: There are a large number of bit errors on the link. Identification method: Query the alarms on the U2000. Cause 2: The number of timeslots bound with the VCTRUNK at the local station and the number of timeslots bound with the VCTRUUNK at the opposite station are not the same or the number of timeslots bound with the path is not the same as the number of timeslots configured in the cross-connection. Identification method: Query the service configuration on the U2000. l Cause 3: The board is faulty. Identification method: Use the exclusive method or determine based on experience.
Procedure
l View the ALM_GFP_dLFD alarm on the U2000, and then determine the number of the VCTRUNK where this alarm is generated. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: There are a large number of bit errors on the link. 1. Check whether any bit error alarm exists on the link. If... Then...
Any bit error alarm exists Handle the bit error alarms first. The bit error alarms are as follows: l B3_EXC l B3_SD Check whether the ALM_GFP_dLFD alarm is cleared. If the alarm persists, see other causes.
Issue 02 (2011-10-31)
386
4 Alarm Processing
If... No bit error alarm exists l
Then... See other causes.
Cause 2: The number of timeslots bound with the VCTRUNK at the local station and the number of timeslots bound with the VCTRUUNK at the opposite station are not the same or the number of timeslots bound with the path is not the same as the number of timeslots configured in the cross-connection. 1. Check whether the number of upstream or downstream timeslots bound with the VCTRUNK at the local station is consistent with the number of downstream or upstream timeslots configured at the opposite station. If ... Then ...
The counts of timeslots are different Increase or decrease the number of bound paths to ensure consistency of timeslots at both stations. For details, see the Configuration Guide. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. The counts of timeslots are the same Proceed to the next step. 2. Select the corresponding NE from the Main Topology. Check whether the number of timeslots bound with the path is the same as the number of timeslots configured in the cross-connection. If... Then...
The counts are different Reconfigure the bound timeslots or the crossconnection. Then, check whether the alarm is cleared. If the alarm persists, see other causes. The counts are the same See other causes. l Cause 3: The board is faulty. 1. Check whether the board reports the HARD_BAD alarm. If... The HARD_BAD alarm exists Then... The board is faulty. Proceed to the next step.
The HARD_BAD alarm does not exist After eliminating other causes, proceed to the next step if the fault persists. 2. ----End Replace the board. For details, see the Parts Replacement.
Related Information
Cell Delimitation State Machine
4 Alarm Processing
The cell delimitation state machine has three states: HUNT, PRESYNC, and SYNC. In the HUNT state, the state machine searches the position of delimiting cells in the BYTE BY BYTE manner. After finding a correct HCS, the state machine changes to the PRESYNC state. In the PRESYNC state, the state machines locks the position of delimiting cells. After consecutively receiving DELTA correct HCS cells, the state machine changes to the SYNC state. In this case, the cell boundary is found. In the PRESYNC state, after receiving an incorrect HCS cell, the state machine returns to the HUNT state. In the SYNC state, after consecutively receiving ALPHA incorrect HCS cells, the state machine changes to the HUNT state. Otherwise, it keeps in the SYNC state, as shown in the following figure.
4.9 ALM_HANGUP
Description
The ALM_HANGUP is an alarm indicating that the orderwire phone is in the off-hook state for a long time. This alarm is generated when the orderwire phone is in the off-hook state for a long time.
Attribute
Parameters
None
Issue 02 (2011-10-31)
388
4 Alarm Processing

l l The ALM_HANGUP alarm does not affect the services or communication of the NE. The ALM_HANGUP alarm indicates that the orderwire phone of the NE is in the off-hook state for a long time. When the alarm is generated, hang up.
Possible Causes
l l The orderwire phone is in the off-hook state for a long time. The hardware is faulty.
Procedure
Step 1 Check whether the orderwire phone is hung up. If not, hang up the phone. Then, check whether the ALM_HANGUP alarm is cleared. Step 2 If the ALM_HANGUP alarm persists, the board hardware may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.10 ALM_TC_OEI
Description
The ALM_TC_OEI alarm is an output error indication in the tandem connection. When the accumulated number of output errors received at the sink of the tandem connection within one second is greater than 0, the ALM_TC_OEI alarm is reported.
Attribute
Parameters
None

When the ALM_TC_OEI alarm is generated, the services at the local station are not affected. This alarm just indicates that some bit errors occur in the signals output from the sink of the tandem connection.
4 Alarm Processing
Possible Causes
Some bit errors occur in the signals output from the sink of the tandem connection.
Procedure
Step 1 Check whether any higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC, B1_SD, B2_SD, or B3_SD alarm, is detected at the source and the sink. If yes, take priority to clear it. Moreover, clean the fiber connector, and make sure that the fiber connector is inserted firmly. Then check whether the ALM_TC_OEI alarm at the local station is cleared. Step 2 If the alarm persists, check whether the transmit board at the source is faulty. If yes, perform a cold reset on the relevant line board, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after the cold reset of the board. Step 3 If the alarm persists, replace the relevant line board at the source, and then check whether the alarm is cleared. Step 4 If the alarm persists, check whether the receive board at the sink is faulty. If yes, perform a cold reset on the board that reports the alarm, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after the cold reset of the board. Step 5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check whether the alarm is cleared. Step 6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded. In this case, ask the relevant carrier for solution. ----End
Related Information
None
4.11 ALM_TC_REI
Description
The ALM_TC_REI alarm is a remote error indication in the tandem connection. When the accumulated number of remote bit errors in the tandem connection received at the sink within one second is greater than 0, the ALM_TC_REI alarm is reported.
4 Alarm Processing
Attribute
Parameters
None

When the ALM_TC_REI alarm is generated, the services at the local station are not affected. This alarm just indicates that bit errors occur in the monitored tandem connection section. Consequently, the transmission service quality is degraded.
Possible Causes
Bit errors occur in the monitored tandem connection section.
Procedure
Step 1 Check whether any higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC, B1_SD, B2_SD, or B3_SD alarm, is detected at the source and the sink. If yes, take priority to clear it. Moreover, clean the fiber connector, and make sure that the fiber connector is inserted firmly. Then, check whether the TC_REI alarm at the local station is cleared. Step 2 If the alarm persists, check whether the transmit board at the source is faulty. If yes, perform a cold reset on the relevant board, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after the cold reset of the board. Step 3 If the alarm persists, replace the relevant line board at the source, and then check whether the alarm is cleared. Step 4 If the alarm persists, check whether the receive board at the sink is faulty. If yes, perform a cold reset on the line board that reports the alarm, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after the cold reset of the board. Step 5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check whether the alarm is cleared.
4 Alarm Processing
Step 6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded. In this case, ask the relevant carrier for solution. ----End
Related Information
None
4.12 APE_ADJUST_FAIL
Description
APE adjustment failure. This alarm is generated when the APE adjustment fails.
Attribute
Alarm Severity Major Alarm Type Process alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the index of APE.

OSNR of receive signal degrades.
Possible Causes
l l l l l l l
Issue 02 (2011-10-31)
The communication fails. The board is offline. An error is responded from a board. The equilibrium cannot be reached after adjustment. The board type error. The VMUX attenuation adjusting fails. The adjustment is stopped by the user.
4 Alarm Processing
Procedure
Step 1 Check the cause of OSNR degrade and handle the alarm accordingly. ----End
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.13 APE_ADJUST_PEND
Description
APE adjustment is pending for operation.
Attribute
Parameters

SNR of receive signal degrade.
Possible Causes
APE detect the powers of channels are unequal, then APE adjustment is pending for operation.
Procedure
Step 1 Manually start APE adjustment. ----End
4 Alarm Processing
Related Information
4.14 APS_FAIL
Description
The APS_FAIL is an alarm indicating the APS protection switching failure. This alarm is generated when the MSP switching fails.
Attribute
Parameters
Parameter 1 Indicates the type of the MSP group in which protection switching occurs. l 0x01: linear MSP group l 0x02: ring MSP group Parameter 2 Indicates the MSP group ID.

When the APS_FAIL alarm is generated, the MSP switching fails. For a linear MSP or a twofiber ring MSP, if a fiber cut or another fault occurs at this time, the services are interrupted.
Possible Causes
The possible causes of the APS_FAIL alarm are as follows: l l l
Issue 02 (2011-10-31)
The MSP configuration parameters are incorrect. The MSP configuration is lost. The board that reports the alarm is faulty.
4 Alarm Processing
Procedure
Step 1 Make sure that the networkwide MSP configuration is correct. For a ring MSP, check the fiber connections in the east and west directions. For a linear MSP, check the working and protection fiber connections, or check the MSP switching modes at the two ends. After modifying the incorrect configuration, check whether the alarm is cleared. Step 2 Make sure that the networkwide APS protocol works properly. Stop the protocol, and then restart it to check whether the alarm is cleared. Step 3 If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For details, refer to "Replacing a Board" of the Supporting Tasks. ----End
Related Information
None
4.15 APS_INDI
Description
The APS_INDI is an alarm indicating the APS state. This alarm is generated when the MSP is in the switching state.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the type of the MSP group in which protection switching occurs. l 0x01: linear MSP group l 0x02: ring MSP group Parameter 2, Parameter 3 Indicates the MSP group ID.
Issue 02 (2011-10-31)
395
4 Alarm Processing

l l The APS_INDI alarm indicates the occurrence of a fiber cut or a terminal node failure, which triggers the MSP switching. For a two-fiber ring MSP or a linear MSP, if a fiber cut or another fault occurs after the occurrence of this alarm, the services are interrupted.
Possible Causes
The possible causes of the APS_INDI alarm are as follows: l l l l An external command, including manual switching, forced switching, and exercise switching, is issued. After the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm is generated, the MSP group changes to the switching state. The service board is faulty. The cross-connect board is faulty.
Procedure
Step 1 View the APS_INDI alarm on the U2000, and then confirm the type and ID of the protection group in which this alarm is generated. Step 2 Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked switching. If yes, clear the switching and then observe whether the alarm is cleared. Step 3 To check whether the MSP is in the automatic switching state, do as follows: 1. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm reported by the equipment. When these alarms are cleared, wait for the MSP switching to be automatically restored to the normal state, and then check whether the APS_INDI alarm is cleared. Make sure that the service board of the MSP is not faulty. Replace the relevant service board and then check whether the alarm is cleared. Make sure that the cross-connect board of the MSP is not faulty. Replace the relevant crossconnect board and then check whether the alarm is cleared.
2. 3.
----End
Related Information
For the 1+1 single-ended non-revertive linear MSP, the APS_INDI alarm is generated when the protection switching occurs. When the optical path recovers to normal, the service is not automatically switched back to the working path, and the APS_INDI alarm persists. In this case, manually switch the service from the protection path to the working path. After successful manual switching, the APS_INDI alarm is cleared.
4.16 AU_AIS
Description
The AU_AIS is an administrative unit (AU) alarm indication. When the pointer value received on the receive side of the local optical port is all "1"s, the AU_AIS alarm is reported.
4 Alarm Processing
Attribute
Parameters
None

l l When the AU_AIS alarm is reported, the VC-4 level services are interrupted if the network is not protected. In this case, the AU-AIS alarm is reported at the downstream station.
Possible Causes
The possible causes of the AU_AIS alarm are as follows: l Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm to the downstream station. Identification method: Query the alarms and the loopback on the U2000. l Board cause 1: The receive board (including the cross-connect and timing board) at the local end is faulty. Identification method: Use the exclusive method. l Board cause 2: The transmit board (including the cross-connect and timing board) at the opposite end is faulty. Identification method: Use the exclusive method.
Procedure
l Query current alarms on the U2000. Determine the number of the interface that reports the alarm according to Parameter 1. For details, see Querying the Current Alarms in the Supporting Task. Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm to the downstream station. 1. Check whether any higher-level alarm exists at the upstream station. If... The alarms listed in Table 4-1 exist Then... Handle these alarms first. If the AU_AIS alarm persists, proceed to the next step.
The alarms listed in Table 4-1 do not Proceed to the next step. exist 2. Perform a loopback at the upstream station to locate the station that reports the AU_AIS alarm originally. Perform an inloop at the receive and transmit ports at the opposite board. See the Supporting Task.
Issue 02 (2011-10-31)
4 Alarm Processing
CAUTION
The loopback may cause the service interruption. 3. Check whether the AU_AIS alarm exists at the opposite station after the loopback is performed. If ... The alarm exists Then ... The AU_AIS alarm of the local station is transmitted from the opposite station. Proceed to the next step.
The alarm does not exist See board cause 1. 4. Perform the loopback again to locate the station where the AU_AIS alarm is reported originally at the opposite upstream station. Check whether any higher-level alarm exists on board at the service source end corresponding to the station. If ... The alarms listed in Table 4-1 exist Then ... Handle these alarms first. If the AU_AIS alarm is not cleared, see board cause 1.
The alarms listed in Table 4-1 do not See board cause 2. exist l Board cause 1: The receive board (including the cross-connect and timing board) of the local end is faulty. 1. 2. 3. l Replace the receive board of the local station. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, replace the local crossconnect and timing board. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see other causes.
Board cause 2: The transmit board (including the cross-connect and timing board) of the opposite end is faulty. 1. 2. 3. Replace the corresponding transmit board of the station where the AU_AIS alarm is originally reported. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, replace the cross-connect and timing board. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see other causes.
----End
Related Information
Table 4-1 Alarms that may cause the AU_AIS alarm R_LOS MS_AIS
Issue 02 (2011-10-31)
R_LOF B1_EXC
R_OOF B1_SD
398
4 Alarm Processing
B2_EXC B3_EXC HP_LOM
B2_SD B3_SD HP_SLM
AU_LOP HP_TIM HP_UNEQ
4.17 AU_LOP
Description
The AU_LOP is an alarm indicating loss of the AU pointer. When the NDF or invalid pointer values are received in eight consecutively frames on the receive side of the local optical port, the AU_LOP alarm is reported.
Attribute
Parameters
None

l l When the AU_LOP alarm is reported, the VC-4 level services are interrupted if the network is not protected. When the AU_LOP alarm is reported, the system returns the G1 byte to the opposite end, indicating the HP_RDI alarm. Consequently, the opposite station reports the HP_RDI alarm.
Possible Causes
The possible causes of the AU_LOP alarm are as follows: l l Cause 1: Excessive receive bit errors are available at the local station. Identification method: Query the alarms of bit errors on the U2000. Cause 2: The level of the service transmitted by the opposite station is inconsistent with that of the service to be received at the local station. Identification method: Query the service configuration on the U2000. l l Cause 3: The board (including the cross-connect and timing board) of the local end is faulty. Identification method: Use the exclusive method. Cause 4: The board (including the cross-connect and timing board) of the opposite end is faulty. Identification method: Use the exclusive method.
4 Alarm Processing
Procedure
l Query current alarms on the U2000. Determine the number of the interface that reports the alarm according to Parameter 1. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: Excessive bit errors are available at the local station. 1. Check whether any bit error alarms exist at the local end. Clear these alarms first. B1_EXC B1_SD B2_EXC B2_SD 2. l Check whether the AU_LOP alarm is cleared. If the alarm persists, see other causes. Cause 2: The level of the service transmitted by the opposite station is inconsistent with the level of the service to be received at the local station. 1. Check whether the level of the service transmitted by the opposite station is consistent with the level of the service to be received by the local station. If... Then...
The service levels are different Reconfigure the service levels at the two ends. Then, check whether the alarm is cleared. If the alarm persists, see other causes. The service levels are the same See other causes. l Cause 3: The board (including the cross-connect and timing board) of the local end is faulty. 1. 2. Replace the receive board of the local station. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, perform cold reset on the cross-connect board at the local station by using the U2000, or reseat the cross-connect board at the local station. For the operations that are performed on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the operations of reseating a board, see the Installation Guide.
CAUTION
If no protection cross-connect board works normally, do not perform the operations, because all the services may be interrupted. 3. l Check whether the alarm is cleared. If the alarm persists, replace the local crossconnect and timing board. For details, see Parts Replacement.
Cause 4: The transmit board (including the cross-connect and timing board) of the opposite end is faulty. 1. 2. Replace the faulty transmit board at the opposite station. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, perform cold reset on the cross-connect board at the opposite end, or reseat the cross-connect board at the opposite end. For the operations that are performed by the U2000, see Performing a
Issue 02 (2011-10-31)
4 Alarm Processing
Cold Reset of a Board in the Supporting Task. For the operations of reseating a board, see the Installation Guide.
CAUTION
If no protection cross-connect board is available, the cold reset on the cross-connect and clock board may interrupt the entire service. 3. ----End Check whether the alarm is cleared. If the alarm persists, replace the opposite crossconnect and timing board. For details, see Parts Replacement.
Related Information
The concatenation levels of the services involve AU3, VC4, VC4-4c, VC4-8c, VC4-16c, and VC4-64c.
NOTE
If the AU_LOP alarm is reported when the equipment runs on the existing network, you need to contact the technical support engineers of Huawei and report the alarm even though you have cleared it by adopting the preceding methods.
4.18 B1_SD
See the alarm page according to the type of the board that reports the alarm. Table 4-2 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm Page Link 4.18.1 B1_SD (OCS) 4.18.2 B1_SD (OTN)
4.18.1 B1_SD (OCS)

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

When the B1_SD alarm is reported, the quality of the transmitted services is degraded.
Possible Causes
The possible causes of the B1_SD alarm are as follows: l l l l Cause 1: The line performance degrades. Cause 2: The external environment is abnormal. Cause 3: The receive board of the local end is faulty. Cause 4: The transmit board of the opposite end is faulty.
Procedure
l Query current alarms on the U2000. Determine the number of the interface that reports the alarm according to Parameter 1. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The line performance degrades. 1. Check whether the transmit power at the opposite station and the receive power at the local station meet the specifications of the interfaces. For details on optical power specification of the board, see"Technical Specifications" of the Product Description. For details, see Querying Optical Power of the Board in the Supporting Task.
NOTE
If... The transmit optical power of the opposite station is normal, but the receive optical power of the local station is almost equal to the specification (for example, within 3 dB) of the receiver sensitivity, The transmit optical power of the local board is abnormal, 2.
Issue 02 (2011-10-31)
See cause 4.
Check whether the optical connector is normal.

4 Alarm Processing
If... The connector is loose
Then... Tighten the optical connector. Check whether the alarm is cleared. If the alarm persists, proceed to the next step.
The interface is normal Proceed to the next step. 3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task. If... The connector is dirty Then... Clean the optical connector. For details, see l Cleaning Optical Fiber Connectors Using Cartridge Cleaners l Cleaning Optical Fiber Connectors Using Lens Tissue l Cleaning Optical Adapters Using Optical Cleaning Sticks in Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. The connector is normal Proceed to the next step. 4. Check whether the attenuation value of the optical attenuator is proper according to the specified receive optical power. For details on optical power specifications of the board, see "Technical Specifications" of the Product Description. If... The value of optical attenuation is improper, Then ... Adjust the attenuation to the proper value. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
Check whether the fiber is faulty. Especially, check whether the bending radius of a fiber jumper is within the normal range, and check whether the fiber from the equipment to the ODF and the fiber outside the equipment room are pressed. If the bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm persists, see cause 2.
Cause 2: The external environment is abnormal.
Issue 02 (2011-10-31)
403
4 Alarm Processing
1.
Check the ambient temperature of the equipment room. If the temperature is higher than 45C or is lower than 0C, use a cooler/heater to decrease/increase the ambient temperature. Check whether the alarm is cleared. If the alarm persists, see cause 3. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting Task.
2. l 1.
CAUTION
3. l 1.
----End
Related Information
None.
4.18.2 B1_SD (OTN)

Description
The B1_SD(OTN) alarm is an alarm indicating that the regenerator section signals are degraded. The alarm occurs when the received signals in SDH frame degrade and the B1 bit errors in the multiplex section exceed the signal degrade (SD) threshold. Reported from the WDM side or client side: WDM side, client side l l The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received on the WDM side exceed the signal degrade threshold. The alarm is generated on the client side when the B1 bit errors in the SDH signals received on the client side exceed the signal degrade threshold.
Issue 02 (2011-10-31)
4 Alarm Processing
Attribute
Parameters
None

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

l l When the B2_EXC alarm is generated, the quality of the transmitted services is degraded. When the B2_EXC alarm is reported, the system returns the M1 byte to the opposite end, indicating the MS_REI alarm. Consequently, the opposite station reports the MS_REI alarm.
Possible Causes
The possible causes of the B2_EXC alarm are as follows: l l l l Cause 1: The line performance degrades. Cause 2: The external environment is abnormal. Cause 3: The receive board of the local end is faulty. Cause 4: The transmit board of the opposite end is faulty.
Procedure
Issue 02 (2011-10-31)

NOTE
4 Alarm Processing
See cause 4.
The interface is normal Proceed to the next step. 3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task. If... The connector is dirty Then... Clean the optical connector. For details, see l Cleaning Optical Fiber Connectors Using Cartridge Cleaners l Cleaning Optical Fiber Connectors Using Lens Tissue l Cleaning Optical Adapters Using Optical Cleaning Sticks in Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. The connector is normal Proceed to the next step. 4. Check whether the attenuation value of the optical attenuator is proper according to the specified receive optical power. For details on optical power specifications of the board, see "Technical Specifications" of the Product Description.
Issue 02 (2011-10-31)
407
4 Alarm Processing
If... The value of optical attenuation is improper,
Then ... Adjust the attenuation to the proper value. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
2. l 1.
CAUTION
3. l 1.
----End
4 Alarm Processing
Related Information
None.
4.20 B2_SD
Description
The B2_SD is an alarm indicating that multiplex section B2 signals received on the line are degraded. When a line board detects that the bit errors of the multiplex section signals exceed the B2_SD alarm threshold but are lower than the B2_EXC alarm threshold, the B2_SD alarm is reported.
Attribute
Parameters
None

l l When the B2_SD alarm is reported, the quality of the transmitted services is degraded. When the B2_SD alarm is reported, the system may return the M1 byte to the opposite end, indicating the MS_REI alarm. Consequently, the remote station may report the MS_REI alarm.
Possible Causes
Procedure
l Query current alarms on the U2000. Determine the number of the interface that reports the alarm according to Parameter 1. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The line performance degrades. 1. Check whether the transmit power at the opposite station and the receive power at the local station meet the specifications of the interfaces. For details on optical power specification of the board, see"Technical Specifications" of the Product
Issue 02 (2011-10-31)
4 Alarm Processing
Description. For details, see Querying Optical Power of the Board in the Supporting Task.
NOTE
See cause 4.
The interface is normal Proceed to the next step. 3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task. If... The connector is dirty Then... Clean the optical connector. For details, see l Cleaning Optical Fiber Connectors Using Cartridge Cleaners l Cleaning Optical Fiber Connectors Using Lens Tissue l Cleaning Optical Adapters Using Optical Cleaning Sticks in Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. The connector is normal Proceed to the next step. 4. Check whether the attenuation value of the optical attenuator is proper according to the specified receive optical power. For details on optical power specifications of the board, see "Technical Specifications" of the Product Description.
Issue 02 (2011-10-31)
410
4 Alarm Processing
If... The value of optical attenuation is improper,
Then ... Adjust the attenuation to the proper value. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
Check whether the fiber is faulty. Especially, check whether the bending radius of a fiber jumper is within the normal range, and check whether the fiber from the equipment to the ODF and the fiber outside the equipment room are pressed. If the bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm persists, see cause 2. Check the ambient temperature of the equipment room. If the temperature is higher than 45C or is lower than 0C, use a cooler/heater to decrease/increase the ambient temperature. Check whether the alarm is cleared. If the alarm persists, see cause 3. Query the bit error threshold of the board that reports the alarm. According to the situation, increase the B2 error threshold. For operations, see the Supporting Task. Check whether the alarm is cleared. If the alarm persists, see Cause 4. Perform an inloop on the receive and transmit ports of the board. Refer to Supporting Task.
2. l 1. 2. l 1.
Cause 3: The setting of the bit error threshold is improper.
CAUTION
If the board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the local faulty board. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see cause 4.
3.
Issue 02 (2011-10-31)
4 Alarm Processing
Cause 4: The transmit board of the opposite end is faulty. 1. If the board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the faulty board at the opposite end. For details, see Parts Replacement.
----End
Related Information
None.
4.21 B3_EXC
Description
The B3_EXC is an alarm indicating that the number of higher order path B3 bit errors in the signals received on the line exceeds the threshold. When a line board detects that the bit errors of the higher order path signals exceed the specified threshold by detecting the B3 byte, the B3_EXC alarm is reported.
Attribute
Parameters
None

l l When the B3_EXC alarm is reported, bit errors occur in the path-level services. When the B3_EXC alarm is reported, the system returns the G1 byte to the opposite end, indicating the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm. If the AU_AIS alarm is inserted when the B3_EXC alarm is reported, the system returns the G1 byte to the opposite end, indicating the HP_RDI alarm. Consequently, the remote station generates the HP_RDI alarm.
Possible Causes
The possible causes of the B3_EXC alarm are as follows: l l l l
Issue 02 (2011-10-31)
Cause 1: The line performance degrades. Cause 2: The external environment is abnormal. Cause 3: The receive board of the local end is faulty. Cause 4: The transmit board of the opposite end is faulty.
4 Alarm Processing
Procedure
l l Query current alarms on the U2000. Determine the number of the interface that reports the alarm. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The line performance degrades. 1. Check whether the transmit power at the opposite station and the receive power at the local station meet the specifications of the interfaces. For details on optical power specification of the board, see"Technical Specifications" of the Product Description. For details, see Querying Optical Power of the Board in the Supporting Task.
NOTE
See cause 4.
The interface is normal Proceed to the next step. 3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task. If... The connector is dirty Then... Clean the optical connector. For details, see l Cleaning Optical Fiber Connectors Using Cartridge Cleaners l Cleaning Optical Fiber Connectors Using Lens Tissue l Cleaning Optical Adapters Using Optical Cleaning Sticks in Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. The connector is normal Proceed to the next step.
Issue 02 (2011-10-31)
413
4 Alarm Processing
4.
Check whether the attenuation value of the optical attenuator is proper according to the specified receive optical power. For details on optical power specifications of the board, see "Technical Specifications" of the Product Description. If... The value of optical attenuation is improper, Then ... Adjust the attenuation to the proper value. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
2. l 1.
CAUTION
If the board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the local faulty board. For details, see Parts Replacement. Check whether the alarm is cleared. If the alarm persists, see cause 4.
3. l
Issue 02 (2011-10-31)

4 Alarm Processing
1.
If the board supports the pluggable optical module, replace the pluggable optical module. Otherwise, replace the faulty board at the opposite end. For details, see Parts Replacement.
----End
Related Information
None.
4.22 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the number of B3 bit errors in the lower order path VC-3 exceeds the threshold. If a board has detected that the number of B3 bit errors exceeds the specified threshold value, the B3_EXC_VC3 alarm is reported.
Attribute
Parameters
None

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

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

l l When the B3_SD alarm is reported, bit errors occur in the path-level services. When the B3_SD alarm is reported, the system returns the G1 byte to the opposite end, indicating the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm. If the AU_AIS alarm is inserted when the B3_SD alarm is reported, the system returns the
Issue 02 (2011-10-31)
4 Alarm Processing
G1 byte to the opposite station, indicating the HP_RDI alarm. Consequently, the opposite station generates the HP_RDI alarm.
Possible Causes
Procedure
NOTE
See cause 4.
The interface is normal Proceed to the next step. 3. Check whether the connector is dirty. For details, see Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task.
Issue 02 (2011-10-31)
418
4 Alarm Processing
If... The connector is dirty
Then... Clean the optical connector. For details, see l Cleaning Optical Fiber Connectors Using Cartridge Cleaners l Cleaning Optical Fiber Connectors Using Lens Tissue l Cleaning Optical Adapters Using Optical Cleaning Sticks in Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step.
The connector is normal Proceed to the next step. 4. Check whether the attenuation value of the optical attenuator is proper according to the specified receive optical power. For details on optical power specifications of the board, see "Technical Specifications" of the Product Description. If... The value of optical attenuation is improper, Then ... Adjust the attenuation to the proper value. For details, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. Then, check whether the alarm is cleared. If the alarm persists, proceed to the next step. Proceed to the next step.
2. l 1.
Issue 02 (2011-10-31)
419
4 Alarm Processing
CAUTION
3. l 1.
----End
Related Information
None.
4.25 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the number of VC-3 B3 bit errors exceeds the threshold. If a board has detected that the number of VC-3 B3 bit errors exceeds the specified B3_SD alarm threshold value, the B3_SD_VC3 alarm is reported.
Attribute
Parameters
None

When the B3_SD_VC3 alarm is generated, the service transmission quality in the VC-3 service channel is degraded.
4 Alarm Processing
Possible Causes
The possible causes of the B3_SD_VC3 alarm are as follows: l l l l l l Higher-level bit alarms occur in the system. The received signals are heavily attenuated. The fiber connector is dirty. The fiber connector is loose. The receive unit at the opposite station is faulty. The transmit unit at the local station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or B3_SD alarm, is detected at the local station or at the upstream station. If yes, take priority to clear it, and then check whether the B3_SD_VC3 alarm is cleared. Step 2 If the alarm persists, check whether the receive optical power of the board that report the alarm is within the normal range. l l 1. 2. 3. 4. If yes, go to Step 3. If not, take the following steps: Insert the fiber connector firmly, and then check whether the alarm is cleared. Check whether the attenuation value specified in the fiber attenuator is proper. If not, adjust it to a proper value, and then check whether the alarm is cleared. Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared. Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Check whether the transmit optical power at the opposite station is within the normal range. If the transmit optical power is beyond the specified range, replace the optical module, and then check whether the alarm is cleared. If not, replace the line board at the opposite end, and then check whether the alarm is cleared. If the transmit optical power is within the normal range, clean the fiber connector at the opposite station, and then check whether the alarm is cleared. Check whether the flange is correctly connected to the optical attenuator at the opposite station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared.
5. 6.
7. 8.
Step 3 If the alarm persists, replace the board that generates the B3_SD_VC3 alarm. ----End
Related Information
None
4 Alarm Processing
4.26 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that the number of B3 bit errors in the VC-4 path exceeds the threshold. If a board has detected that the number of B3 bit errors in the VC-4 path exceeds the specified threshold value, the B3_SD_VC4 alarm is reported.
Attribute
Parameters
None

When the B3_SD_VC4 alarm is generated, bit errors occur in the path-level services.
Possible Causes
The possible causes of the B3_SD_VC4 alarm may be the same as those of the B3_SD alarm.
Procedure
Step 1 See the procedure for handling the B3_SD alarm. ----End
4.27 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED alarm is an alarm indicating that the logical board is not created in the corresponding slot. This alarm occurs when a physical board is installed but no logical board is created on the U2000.
Attribute
Issue 02 (2011-10-31)
422
4 Alarm Processing
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ID of the slot where the alarm is generated.

When the BD_NOT_INSTALLED alarm occurs, the corresponding slot cannot be configured with services. This alarm, however, does not affect the operation of the system.
Possible Causes
The logic board is not created.
Procedure
Step 1 On the U2000, add a logic board that corresponds to the slot that reports the alarm. ----End
Related Information
None
4.28 BD_STATUS
See the alarm page according to the type of the board that reports the alarm. Table 4-3 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm Page Link 4.28.1 BD_STATUS (OCS) 4.28.2 BD_STATUS (OTN)
4.28.1 BD_STATUS (OCS)

4 Alarm Processing
Description
The BD_STATUS (OCS) is an alarm indicating that the physical board is offline. This alarm is reported when the logical board is created on the U2000 but the physical board is not inserted in the subrack.
Attribute
Parameters
None

Because the physical board is not inserted in the equipment, the data that is configured on the NE cannot be delivered to this board. Hence, configuration of services fails.
Possible Causes
The possible causes of the BD_STATUS alarm are as follows: l l l Cause 1: The board is in the cold reset or warm reset state. Cause 2: The board is not inserted in the corresponding slot or the board does not contact the mother board firmly. Cause 3: The pins of the mother board are bent or the board is faulty.
Procedure
l l Query current alarms on the U2000. Then find the boards that report the alarm. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The board status is cold reset or warm reset. 1. Check the board alarm indicator to see whether the status of the board that reports the alarm is cold reset or warm reset. Wait for five minutes if the board is in the cold reset or warm reset state, and then check whether the alarm is cleared. For the description of the alarm indicators on the board, see Board Indicators in the Hardware Description. If the alarm persists, see other causes.
2. l
Cause 2: The board is not inserted in the corresponding slot or the contact part of the board with the mother board is loose. 1. 2. Check whether the board is inserted in the corresponding slot. If not, insert the corresponding physical board. For details, see the Installation Guide. Check whether the board is connected to the backplane properly and whether the board is connected properly. If the board is loose, reseat the board. For operations, see the Installation Guide. Then, check whether the alarm is cleared. If the alarm persists, see other causes.
3.
Issue 02 (2011-10-31)
4 Alarm Processing
Cause 3: The pins of the mother board are bent or the board is faulty. 1. Remove the board that reports the alarm. For details, see the Installation Guide. Check whether any pins of the mother board are bent. If any bins are bent, contact Huawei engineers for fixing the pins. After the pins are fixed, insert the board. For details, see the Installation Guide. Then, check whether the alarm is cleared. If the alarm persists, replace the board that reports the alarm. For details, see the Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see other causes.
2. 3. ----End
Related Information
None.
4.28.2 BD_STATUS (OTN)

Description
The BD_STATUS is an alarm indicating that the board is out of position. This alarm is reported when the logical board is created on the U2000 but the physical board is not inserted in the slot.
Attribute
Parameters
None

The board is not in position. Hence, the functions related to the board are unavailable.
Possible Causes
l l l l l The AUX board is faulty. The logic board is configured but the physical board has not been inserted in the proper slot. The connection between the plug of the board and the socket of the backplane is loose. The board is faulty. The backplane is faulty.
Issue 02 (2011-10-31)
425
4 Alarm Processing
Procedure
Step 1 If the alarm is reported on the AUX board and all service boards but services are normal and the SCC board operates normally, it indicates that the AUX board is faulty. Perform a warm reset or cold reset on the faulty board through the U2000. If the alarm persists, replace the AUX board. Step 2 Check whether the corresponding board is inserted in the physical slot. l l If no corresponding board is inserted, insert the board. If the corresponding board is inserted, check whether the insertion is firm. If not, reset the board.
Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. Step 4 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei engineers. ----End
Related Information
None
4.29 CFCARD_FAILED
Description
CF Card Failed.
Attribute
Parameters
None

When the CFCARD_FAILED alarm occurs, the system is not affected. The alarm indicates that the operations related to the CF card fail.
Possible Causes
The CF card is faulty and needs to be replaced.
Issue 02 (2011-10-31)
426
4 Alarm Processing
Procedure
Step 1 Replace the CF card and then check whether the CFCARD_FAILED alarm is cleared. If the alarm persists, replace the SCC board. For details, see the Parts Replacement. ----End
Related Information
None
4.30 BDID_ERROR
Description
The BDID_ERROR is an alarm indicating slot verification error. This alarm is generated when the board parity check fails or when the board is not properly secured in its slot.
Attribute
Parameters
None

l l When the BDID_ERROR alarm is generated, the board may fail to get online and as a result the services are interrupted. In this case, you cannot configure and monitor the services for the board.
Possible Causes
The possible causes of the BDID_ERROR alarm are as follows: l l l The board is not properly secured in the slot. The board hardware fails. Pins on the backplane are bent.
Procedure
Step 1 View the BDID_ERROR alarm on the U2000 to determine the relevant board. Step 2 Remove the board to check whether there are any bent pins on the backplane. If any pins are bent, fix them and then insert the board. Check whether the alarm is cleared.
4 Alarm Processing
Step 3 If the alarm persists, replace the board. ----End
Related Information
None
4.31 C2_VCAIS
Description
The C2_VCAIS is a C2 byte alarm indication. If a board has detected that the value of the received C2 byte is all "1"s, the C2_VCAIS alarm is reported.
Attribute
Parameters
None

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

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

When the CHIP_ABN alarm is generated, the board temperature cannot be correctly detected.
Possible Causes
The temperature chip on the board fails.
Procedure
Step 1 Check whether the equipment has another cross-connect board that is functioning properly. If yes, perform cold reset on the board that reports the CHIP_ABN alarm. After successful cold reset, check whether the alarm is cleared. Step 2 If the alarm persists, replace the board. For details, see the Parts Replacement. ----End
Related Information
None
4.34 CLIENT_PROT_NOTSTART
Description
The CLIENT_PROT_NOTSTART is an alarm indicating that the client-side 1+1 protection group is not started. This alarm occurs when the client-side 1+1 protection group is disabled because the configurations on the both sides of the active and standby channels of the protection group do not meet the requirements of enabling the protection group.
4 Alarm Processing
Attribute
Parameters
None

The client-side 1+1 protection group does not perform the switching in case of a service fault. In this case, the protection fails.
Possible Causes
l l l The active or standby channel is configured with an incorrect electrical-layer crossconnection. The active or standby channel is not configured with complete electrical-layer services between WDM-side ports and client-side ports. The active or standby channel is configured with an EVPL link that converges at a clientside optical interface.
Procedure
Step 1 Query on the U2000 whether the active or standby channel is configured with an incorrect electrical-layer cross-connection such as a cross-connection with an IP port as the source and another IP port as the sink. If yes, delete the incorrect electrical-layer cross-connection. Step 2 If the alarm persists, check the OTU that can be configured with electrical-layer crossconnections. If the active or standby channel of this OTU is not configured with complete electrical-layer services between WDM-side ports and client-side ports, configure the complete electrical-layer services. Step 3 If the alarm persists, check whether the active or standby channel is configured with an EVPL link that converges in the downlink. If yes, change this EVPL link to an EPL link or an EVPL link that broadcasts in the downstream. ----End
Related Information
4.35 CLIENT_PORT_STA_INDI
Description
The CLIENT_PORT_STA_INDI alarm indicates the state of the client side 1+1 optical channel protection group. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
4 Alarm Processing
Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 Description Indicate the switch request status. For example: l 0x0F: Lockout l 0x0E: Forced Switch l 0x0C: SF Switch l 0x09: SD Switch l 0x07: Manual Switch l 0x05: WTR

l l When switching of the client 1+1 protection group occurs, services are transiently interrupted. When this alarm is reported, the working channel or the protection channel of the client 1 +1 protection group might have faulty services that need to be restored.
Possible Causes
l l l Cause 1: A user issues an external switching command such as forced switching, manual switching or locked switching. Cause 2: The services of the working channel or the protection channel of the client 1+1 protection group are faulty. Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
l Cause 1: A user issues an external switching command such as forced switching, manual switching or locked switching. 1. On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching or locked switching, check whether the external switching operation is necessary.
Issue 02 (2011-10-31)
4 Alarm Processing
2. 3. l
If the external switching operation is necessary, ignore the alarm. If the external switching operation is unnecessary, issue a command to clear the external switching.
Cause 2: The services of the working channel or protection channel of the client 1+1 protection group are faulty. 1. Query whether the boards that are configured with the working channel or protection channel of the protection group have the alarms, such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_TIM, REM_SF, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC or REM_SD. If yes, handle the alarms by referring to the corresponding alarm handling procedures. If the alarm persists, check whether the attribute of the protection group is Revertive or not. If the attribute is Revertive, the working channel of the current service automatically switches to the working channel and then the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears. There is no need to handle this alarm. After WTR Times (s), the alarm clears.
2.
Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears. 1.
----End
Related Information
4.36 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE is an alarm indicating that the clock enters the non-tracing mode. This alarm is generated when the current clock does not trace any line clock source, tributary clock source, or external clock source. Reported from the WDM side or client side: NA
Attribute
Parameters
None

When the CLK_NO_TRACE_MODE alarm is generated, the clock is in the non-tracing mode. In this case, the system clock is of a low quality. When the low quality clock results in the outof-synchronization status among NEs, the bit error rate of services increases.
4 Alarm Processing
Possible Causes
The possible causes of the CLK_NO_TRACE_MODE alarm are as follows: l l Cause 1: A priority table is not manually set for the system, and NEs use their own default priority tables. Cause 2: A priority table is set, but only the internal clock source in the priority table can be traced.
Procedure
l Cause 1: A priority table is not manually set for the system, and NEs use their own default priority tables. 1. Query the current priority table of the system. If there is only the internal clock source in the priority table, set the clock source priority table to include other available clock sources. After the setting, the alarm is automatically cleared. For details, see Configuring the System Clock Source Priority Table in the Feature Description.
Cause 2: A priority table is set, but only the internal clock source in the priority table can be traced. 1. In the current priority table, if the internal clock source is not the only available source, find out why other clock sources cannot be traced. Common causes are as follows: The existence status of the clock source is lost. In this case, the system generates the SYNC_C_LOS alarm. After the SYNC_C_LOS alarm is cleared, the system clock traces any clock source other than the internal clock source, and then check whether the CLK_NO_TRACE_MODE alarm is cleared. The synchronous source is degraded. In this case, the system generates the SYN_BAD alarm. After the SYN_BAD alarm is cleared, the system clock traces any clock source other than the internal clock source, and then check whether the CLK_NO_TRACE_MODE alarm is cleared. The local station enables the SSM protocol, while the upstream station does not enable the SSM protocol. In this case, enable the SSM protocol at the upstream station. When the system clock traces any clock source other than the internal clock source, the CLK_NO_TRACE_MODE alarm is automatically cleared. For details, see Configuring the Clock Source Protection in the Feature Description.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.37 CRC4_CROSSTR
Description
The CRC4_CROSSTR is an alarm indicating that the count of CRC4 multi-frame errors crosses the threshold. The alarm occurs when the number of the bit errors in the CRC4 multiframe exceeds the threshold. Reported from the WDM side or client side: WDM side, client side
4 Alarm Processing
Attribute
Parameters
None

The alarm has an influence on the services (supervisory channel such as the orderwire signal).
Possible Causes
l l l The configuration of the system clock is incorrect. The attenuation of the transmission line is overlarge. The receive optical power is overloaded.
Procedure
Step 1 Check the clock configuration of the system on the U2000 to ensure that the configuration is correct. For details, see the Configuration Guide. Step 2 Check whether the input optical power of the interface of the board at the local station is within the normal range by using the U2000. For optical power specifications of the specific boards, see the Product Description. If the optical power is abnormal, take the processing methods of alarms such as IN_PWR_HIGH or IN_PWR_LOW for troubleshooting. Step 3 If the services are not influenced, check whether the fiber jumper between the FIU board and the SC2/SC1/ST2 board is extruded. If the fiber jumper is extruded, clean up the routed fiber jumper. If the fiber jumper is transformed due to the extrusion, replace the fiber jumper. ----End
Related Information
None
4.38 DB_RESTORE_FAIL
Description
The DB_RESTORE_FAIL is an alarm indicating a database restore failure. This alarm occurs when the database recovery fails.
Issue 02 (2011-10-31)
435
4 Alarm Processing
Attribute
Alarm Severity Major Alarm Type Process Alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 Description 0x01, indicating that the OCP database fails to recover

The configured data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l l The database configuration file is lost. Data in the database is damaged.
Procedure
Step 1 Back up the database regularly at a fixed time to solve this problem. Check and test the database in the backup area to ensure that the data in database is complete. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.39 DBPS_ABNORMAL
Description
The alarm indicates that the DBPS protection group is abnormal. When the DBPS protection group detects anomalies, the DBPS_ABNORMAL alarm is reported.
Issue 02 (2011-10-31)
436
4 Alarm Processing
Attribute
Parameters
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated. Parameter 3 The anomaly of the DBPS protection group is classified into the following three types: l 0x1 indicates that timeout occurs during the communication between the active equipment and standby equipment; l 0x2 indicates that the protection configuration of the active and standby equipment is incorrect; l 0x3 indicates that the snooping protocol is abnormal.

The following exceptions may result in service disruption. l If the protocol communication between the active equipment and the standby equipment in the DBPS protection group cannot be established, there may be two pieces of active equipment or standby equipment. If the DBPS protection status of the active equipment and standby equipment is inconsistent, the service protection cannot function properly. If the snooping protocol used (VRRP or ARP) detects anomalies, the snooping function cannot be realized, and therefore the protection status of the active equipment and the protection status of the standby equipment are incorrect.
l l
Possible Causes
l The protocol communication between the active equipment and the standby equipment is interrupted. In this case, communication between the protocol interfaces cannot be established, or the protection configuration on the active equipment and the protection configuration on the standby equipment are inconsistent. The VLAN configuration of the active equipment and the VLAN configuration of the standby equipment are inconsistent, or the active equipment and standby equipment use different snooping protocols. In the case of the VRRP protocol, the configuration of the DBPS protection group may be inconsistent with the configuration of the VRRP group of the interconnected routers or the
Issue 02 (2011-10-31)
4 Alarm Processing
VRRP groups of the routers interconnected to the active and standby DBPS may be different.
Procedure
Step 1 Query alarms on the U2000 to determine the ID of the protection group where the alarms are generated. Step 2 Check whether the protocol interface of the DBPS protection group is configured properly and the IDs of the protection groups on the active and standby equipment are consistent. If there are errors in the configuration, modify the configuration of the protection group. Step 3 Check whether the VLAN configuration and the snooping protocol on DBPS protection group are consistent. If not, modify the protection configuration. Step 4 If the VRRP protocol is used, check whether the configuration of the DBPS protection group is consistent with the configuration of the VRRP protection in the two interconnected routers. Note that the DBPS protection group must correspond to the VRRP group. In addition, the VRRP groups of the routers interconnected to the active and standby DBPS equipment must be consistent. Otherwise, eliminate the incorrect VRRP configuration of the router, and then reconfigure the DBPS protection group. ----End
Related Information
For details, see "DBPS Protection" in the Feature Description.
4.40 DBMS_ABNORMAL
Description
The alarm indicates that the database state is abnormal. When an exception occurs during the running of the database, a DBMS_ABNORMAL alarm is reported.
Attribute
Issue 02 (2011-10-31)
438
4 Alarm Processing
Parameters
Parameter Parameter 1 Description Indicates the alarm cause. 0x01 indicates that nvram device is bad. 0x02 indicates that there is no enough flash space. 0x03 indicates that submitting transactions times out. 0x04 indicates that the database is deleted without restarting the system.

Service configurations may be lost.
Possible Causes
l l Cause 1: The nvram device is damaged, the flash memory is insufficient, or submitting transactions times out. Cause 2: The database is deleted.
Procedure
l Cause 1: The nvram device is damaged, the flash memory is insufficient, or submitting transactions times out. 1. 2. 3. l 1. 2. ----End Check whether configurations are changed after the alarm is reported. If configurations are changed, manually back up services and reset the board. If no configurations are changed, reset the board directly. If the alarm persists, replace the board. Reset the NE. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
Cause 2: The database is deleted.
Related Information
None
4.41 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a database error. The alarm occurs when the database is in error
4 Alarm Processing
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the alarm type. The value is the error code that causes the DBMS_ERROR alarm. Parameter 2 Indicates the memory areas in the database: 0x00 indicates FDB0. 0x01 indicates FDB1. 0x02 indicates DRDB. Parameter 3 Indicates the ID of the database that has errors. Currently, the value can only be 0-255 (0x00-0xFF). 0x00 indicates that the entire storage area mistakes in error. 0x01-0xff indicates that the database is in error.

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

In the protection mode, the NE database cannot be backed up.
Possible Causes
l l The reset times of the SCC in five minutes cross the threshold value of the protection mode. The SCC issues a command to test the protection mode.
Procedure
Step 1 Check whether the NE database in the protection mode is caused by human factors. If that is the case, l l Perform warm or cold reset on the SCC through the U2000. Release the protection mode. For details, see the Supporting Tasks. Wait for 15 minutes. Release the protection mode after the automatic reset.
Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4 Alarm Processing
4.43 DCM_INSUFF
Description
The DCM_INSUFF is an alarm indicating the insufficient dispersion compensation margin. The alarm is generated when the dispersion compensation value gets close to the limit of the dispersion compensation margin
Attribute
Alarm Severity Warning Alarm Type Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 The value is always 0xff. Parameter 2 Indicates the positive or negative dispersion compensation margin. The value 0x00 indicates the positive dispersion compensation margin, and the value 0x01 indicates the negative dispersion compensation margin.

The alarm does not affect the existing services. The alarm indicates that the system cannot meet the higher dispersion compensation requirements.
Possible Causes
The configuration of the DCM module is not correct or the DCM module is faulty.
Procedure
Step 1 Check whether there is the OTUk_LOF alarm on the U2000. If there is the OTUk_LOF alarm, clear the alarm according to the proper procedure. Step 2 If there are no other alarms, query the dispersion compensation value of the board on the U2000.
4 Alarm Processing
If the dispersion compensation value is large and close to the upper limit of the dispersion compensation margin, replace the DCM module with a DCM module with lower dispersion compensation capabilities. If the dispersion compensation value is small and close to the lower limit of the dispersion compensation margin, replace the DCM module with a DCM module with higher dispersion compensation capabilities.
----End
Related Information
None
4.44 DLAG_PROTECT_FAIL
Description
The DLAG_PROTECT_FAIL is an alarm indicating that the DLAG protection fails. If negotiation fails or any anomaly occurs during the DLAG protection, the DLAG_PROTECT_FAIL alarm is reported.
Attribute
Alarm Severity Major Alarm Type Processing alarm
Parameters
Parameters 1 and 2 Indicates the ID of the aggregation group.
Issue 02 (2011-10-31)
443
4 Alarm Processing
Name Parameter 3
Meaning Indicates the cause of the DLAG protection failure. l 0x01: Both the active and the standby links fail. l 0x02: The active and standby ports fail to receive the LACP packets. l 0x03: The opposite equipment does not enter the LACP synchronization status. l 0x04: The active or standby port detects the self-loop. Alternatively, the active or standby port may form a loop with other ports on the board. l 0x05: The communication between the active and standby boards times out. l 0x06: The communication between the board and the cross-connect board times out. l 0x07: The active port selected by LACP is inconsistent with the one selected by cross-connect board.

When all the DLAG ports fail, or when the board fails to normally communicate with other boards, the DLAG_PROTECT_FAIL alarm is reported. In the case of the DLAG_PROTECT_FAIL alarm, services cannot be received or transmitted in the LAG, or the user cannot check whether services are in the normal state.
Possible Causes
The possible causes of the DLAG_PROTECT_FAIL alarm are as follows: l l l l l l l Both the active and standby links fail. The active and standby ports fail to receive the LACP packets. The opposite equipment does not enter the LACP synchronization status. The active or standby port detects the self-loop. Alternatively, the active or standby port may form a loop with other ports on the board. The communication between the active and standby boards times out. The communication between the board and the cross-connect board or SCC board times out. The active port selected by LACP is inconsistent with the one selected by cross-connect board.
Procedure
Step 1 View the DLAG_PROTECT_FAIL alarm on the U2000, and determine the board where the DLAG_PROTECT_FAIL alarm is generated. Determine the ID of the LAG where the DLAG_PROTECT_FAIL alarm is generated according to Parameters 1 and 2, and determine the cause of the DLAG_PROTECT_FAIL alarm at the port according to Parameter 3. Step 2 If the value of Parameter 3 is 0x01, it indicates that the link becomes faulty or fails.
4 Alarm Processing
1. 2.
On the U2000, check whether the port in the LAG is enabled. If not, enable the port and then check whether the DLAG_PROTECT_FAIL alarm is cleared. If the DLAG_PROTECT_FAIL alarm persists, check the link state of all the ports. Rectify the fault of the port link, and then check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 3 If the value of Parameter 3 is 0x02, it indicates that the port fails to receive the LACP packets. 1. On the U2000, check whether the LAG is configured at the opposite end, and check whether the port connected to the faulty port is added to the LAG at the opposite end. Make sure that the LAG is correctly configured, and then check whether the DLAG_PROTECT_FAIL alarm is cleared. If the DLAG_PROTECT_FAIL alarm persists, check whether the local port transmits packets. If both ends can normally transmit and receive packets, check whether the DLAG_PROTECT_FAIL alarm is cleared.
2.
Step 4 If the value of Parameter 3 is 0x03, it indicates that the opposite equipment fails to enter the LACP protocol synchronization status. Check the connection of the port, and LAG configuration at the opposite equipment, and then check whether the DLAG_PROTECT_FAIL alarm is cleared. Step 5 If the value of Parameter 3 is 0x04, it indicates the port is in the self-loop state. Release the loop and then check whether the DLAG_PROTECT_FAIL alarm is cleared. Step 6 If the value of Parameter 3 is 0x05, it indicates that the communication between the active and standby boards times out. Make sure the active and standby boards are in position, and the communication between them is normal. Then check whether the DLAG_PROTECT_FAIL alarm is cleared. Step 7 If the value of Parameter 3 is 0x06, it indicates that the communication between the board and the cross-connect board and SCC board times out. Make sure that the software of the crossconnect board and the SCC is normal. If the board normally communicates with the crossconnect board or SCC board, check whether the DLAG_PROTECT_FAIL alarm is cleared. Step 8 If the value of Parameter 3 is 0x07, it indicates that the active port selected by LACP is inconsistent with the one selected by cross-connect board. Make sure that the active port selected by LACP is consistent with the one selected by cross-connect board, and then check whether the DLAG_PROTECT_FAIL alarm is cleared. ----End
Related Information
None
4.45 DSP_LOAD_FAIL
Description
The DSP_LOAD_FAIL is an alarm indicating DSP software loading failure. The alarm occurs when loading the DSP program fails. Reported from the WDM side or client side: NA
4 Alarm Processing
Attribute
Parameters
None

Loading the DSP program to the board fails. As a result, the board cannot work normally, which has an influence on the services of users.
Possible Causes
Procedure
Step 1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting Tasks. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.46 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating service connectivity loss. This alarm is generated when the continuity check message (CCM) packets transmitted by the maintenance end point (MEP) of the opposite end are not received within 3.5 times of the continuity check (CC) period.
Attribute
Parameters
4 Alarm Processing
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 to 4 Parameters 5 and 6 Parameter 7 Parameter 8 Description Indicates the Ethernet port. Indicates the VLAN ID. Indicates the direction of the maintenance point. Indicates the level of the maintenance domain.
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote maintenance point ID is the ID of the CC source maintenance point.

Possible Causes
Cause 1: There is a failure in the service connectivity.
Procedure
l Cause 1: There is a failure in the service connectivity. 1. 2. Check whether the related alarms, such as LINK_ERR, are reported. If the related alarms are reported, clear the alarms first. If the ETH_CFM_LOC alarm persists, check whether the attributes and crossconnection status of the service are correctly configured on the U2000. If any error is found, modify the configuration.
----End
Related Information
None
4.47 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating a misconnection. This alarm indicates that there are misconnections between different maintenance domains (MDs).
Issue 02 (2011-10-31)
447
4 Alarm Processing
Attribute
Alarm Severity Critical Alarm Type Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 to 4 Parameters 5 and 6 Parameter 7 Parameter 8 Description Indicates the Ethernet port. Indicates the VLAN ID. Indicates the direction of the maintenance point. Indicates the level of the MD.

The CFM_OAM fails to test the service connectivity. The alarm does not affect services.
Possible Causes
l l l Cause 1: The level of the MD to which the maintenance end point (MEP) belongs is incorrectly configured. Cause 2: The MDs and MAs respectively configured at the source and sink ends of the same service are inconsistent. Cause 3: Certain physical links are incorrectly connected.
Procedure
l Cause 1: The level of the MD to which the MEP belongs is incorrectly configured. 1. Check whether the level of the maintenance point on the service is correctly configured. If the level is incorrectly configured, change the level so that the level is correct.
Cause 2: The MDs and MAs respectively configured at the source and sink ends of the same service are inconsistent. 1. If the alarm persists, check whether the MD/MA names configured at the source and sink ends are consistent. If not, modify them to the same, and then check whether the alarm is cleared.
l
Issue 02 (2011-10-31)
Cause 3: Certain physical links are incorrectly connected.

4 Alarm Processing
1. ----End
If the alarm persists, check whether physical links are misconnected. If yes, reconnect the fiber or line, and then check whether the alarm is cleared.
Related Information
None
4.48 ETH_CFM_MACSTATUS
Description
The ETH_CFM_MACSTATUS is a remote MAC defect indication. This alarm indicates that a continuity check packet carrying a port tlv or an interface tlv is received from a given remote MEP.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 to 4 Parameters 5 and 6 Parameter 7 Parameter 8 Description Indicates the Ethernet port ID. Indicates the VLAN ID. Indicates the direction of the maintenance point. Indicates the level of the maintenance domain.
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote maintenance point ID is the ID of the source maintenance point of the continuity check (CC).

The MAC status of remote mep's port is linkdown or discard.
4 Alarm Processing
Possible Causes
Cause 1: The port status of remote mep occur defection.
Procedure
l Cause 1: The port status of remote mep occur defection. 1. ----End Check whether the port of remote mep is linkdown or discarding. Rectify the fault.
Related Information
None
4.49 ETH_CFM_RDI
Description
The ETH_CFM_RDI is a remote CFM_OAM alarm indication. This alarm is generated at the local end when the CFM_OAM fault is generated at the remote end. This alarm indicates that at least one continuity check message (CCM) packet with the RDI indication is received.
Attribute
Alarm Severity Minor Alarm Type Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 to 4 Parameters 5 and 6 Parameter 7 Parameter 8 Description Indicates the Ethernet port ID. Indicates the VLAN ID. Indicates the direction of the maintenance point. Indicates the level of the maintenance domain.
Issue 02 (2011-10-31)
450
4 Alarm Processing
Parameter
Description
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote maintenance point ID is the ID of the source maintenance point of the continuity check (CC).

When the ETH_CFM_RDI alarm is generated, the services on the transmit side of the local equipment may be interrupted.
Possible Causes
Cause 1: The opposite equipment detects a fault.
Procedure
l Cause 1: The opposite equipment detects a fault. 1. ----End Check whether ETH alarms exist on the opposite equipment, and then rectify the fault according to the alarms.
Related Information
None
4.50 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating error frames. This alarm indicates that there are error continuity check message (CCM) packets in the same maintenance association (MA).
Attribute
Parameters
4 Alarm Processing
Parameter Parameters 1 to 4 Parameters 5 and 6 Parameter 7 Parameter 8
Description Indicates the Ethernet port ID. Indicates the VLAN ID. Indicates the direction of the maintenance point. Indicates the level of the maintenance domain.

The CFM_OAM fails to test the service connectivity. The alarm does not affect services.
Possible Causes
l l l Cause 1: The periods of the MDs to which the MEPs of the stations of the service belong are inconsistent. Cause 2: The MEP IDs in the MDs to which the MEPs of the stations of the service belong are the same or illegal MEP ID is used. Cause 3: There are service loops in the MDs to which the MEPs of the service belong.
Procedure
l Cause 1: The periods of the MDs to which the MEPs of the stations of the service belong are inconsistent. 1. Check whether the CCM periods that are configured on the equipment at the stations of the service are consistent. If the CCM periods are inconsistent, change the configuration so that the CCM periods are consistent.
Cause 2: The MEP IDs in the MDs to which the MEPs of the stations of the service belong are the same or illegal MEP IDs are used. 1. If the alarm persists, check whether the same MEP IDs are used in the MD to which the MEPs of the stations of the service belong. If the same MEP IDs are used, delete the repeated MEP ID and create another MEP ID so that no MEP ID conflict exists in the MD. If the alarm persists, check whether there are service loops in the MDs to which the MEPs of the service belong. If there are service loops, release the service loops.
Cause 3: There are service loops in the MDs to which the MEPs of the service belong. 1.
----End
Related Information
None
Issue 02 (2011-10-31)
452
4 Alarm Processing
4.51 ETH_MISCONNECT
Description
ETH_MISCONNECT is an alarm indicating an incorrect connection between network interfaces. This alarm indicates that the LAN cable for connecting subracks is incorrectly connected.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameters 1 Description Indicates the network interface number.

None
Possible Causes
l Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is connected to a subrack.
Procedure
l Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is connected to a subrack. 1. Check whether the ETH3 interface is connected to a subrack. If the ETH3 interface is connected to a subrack, modify the network condition and disconnect the ETH3 interface from the subrack.
----End
Related Information
None.
4 Alarm Processing
4.52 ETH_SERVICE_CONFIG_FAIL
Description
Ethernet service configuration failure alarm.
Attribute
Parameters
Parameters 1 and 2 Indicates the service ID. A link conflicting with DBPS is invisible to users and the value of this parameter for such a link is 0xff 0xff (invalid). Parameters 3 and 4 Indicates the in port CVLAN ID. 0xff 0xff: No in port CVLAN is available. Parameters 5 and 6 Indicates the in port SVLAN ID. 0xff 0xff: No in port SVLAN is available. Parameter 7 Indicates the protection type. 0x00: LAG. 0x0a: DBPS. 0xff: No protection is available. Indicates the protection group ID. 0xff: No protection group is available.
Parameter 8

The Ethernet service for which the alarm is reported fails to be created and other services are not affected.
Possible Causes
Cause 1: The Ethernet service fails to be configured due to resource conflict.
Issue 02 (2011-10-31)
454
4 Alarm Processing
Procedure
l Cause 1: The Ethernet service fails to be configured due to resource conflict. 1. On the U2000, view the alarm parameters. If the value of parameter 7 is 0xff, determine the service ID based on parameters 1 and 2 and delete the service mapping. Then create the service again by using another VLAN or port. If the value of parameter 7 is 0x00 (LAG), determine the service ID based on alarm parameters 1 and 2 and delete the service mapping the service ID, or determine the protection group ID based on alarm parameter 8 and delete the LAG protection group mapping the protection group ID. Then create the service again by using another port or VLAN. If the value of parameter 7 is 0x01 (DBPS), determine the protection group ID based on alarm parameter 8 and delete the southbound port of the DBPS protection group or delete the DBPS protection group. Then, create the southbound port of the DBPS protection group by using another port.
2.
3.
----End
Related Information
None.
4.53 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating the point-to-point Ethernet OAM discovery failure. When the OAM protocol is enabled at the port of a board and the negotiation with the opposite equipment fails, this alarm is generated.
Attribute
Parameters
Issue 02 (2011-10-31)
455
4 Alarm Processing
Parameter Description Parameter 1 Indicates the reason why the negotiation fails. l 0x01: A link fault occurs at the local end. l 0x02: The local end fails to transmit the OAM message. l 0x03: The local end fails to receive the OAM message. l 0x04: The OAM configurations of the opposite end do not meet the requirements of the local end. l 0x05: The OAM configurations of the local end do not meet the requirements of the opposite end.

The ETHOAM_DISCOVER_FAIL alarm is generated when the system runs the IEEE 802.3ah OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to services.
Possible Causes
l l l l l A link fault occurs at the local end. The local end fails to transmit the OAM message. The local end fails to receive the OAM message in a specified time. The OAM configurations of the opposite end do not meet the requirements of the local end. The OAM configurations of the local end do not meet the requirements of the opposite end.
Procedure
Step 1 View the ETHOAM_DISCOVER_FAIL alarm on the U2000 and determine the possible causes of the alarm according to Parameter 1. Step 2 When Parameter 1 is 0x01, it indicates that a link fault occurs at the local end. Query the boardlevel alarms on the U2000. Then remove the fault according to the specific link alarms such as LINK_ERR and L_SYNC. Step 3 When Parameter 1 is 0x02, it indicates that the local end fails to transmit the OAM message. View the printed information about the serial port. The DSSP, drive, and microcode components are involved in the problem. The fault location needs the assistance of engineers on related project teams. Step 4 When Parameter 1 is 0x03, it indicates that the local end fails to receive the 3ahOAM message from the opposite end in a user-defined time. 1. Check whether the MAC addresses of the interconnected ports are the same. If yes, set different MAC addresses for the interconnected ports. Then check whether the alarm is cleared. Check whether the 3ahOAM protocol is enabled at the opposite end. If not, enable the protocol at the opposite end. Then check whether the alarm is cleared. If the alarm persists, the local end fails to receive the OAM message. Replace the board. For details, see the Parts Replacement.
2. 3.
Step 5 When Parameter 1 is 0x04, it indicates that the OAM configurations of the opposite end, including link event reporting capability and unidirectional operation capability, do not meet the
4 Alarm Processing
requirements of the local end. Query and modify the configurations of the opposite port on the U2000. When the configurations meet the requirements of the local end, the alarm is automatically cleared. Step 6 When Parameter 1 is 0x05, it indicates that the OAM configurations of the local end do not meet the requirements of the opposite end. Query and modify the configurations of the local port on the U2000. When the configurations meet the requirements of the opposite end, the alarm is automatically cleared. ----End
Related Information
None
4.54 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs on the remote end of point-to-point Ethernet OAM. When the port with the OAM protocol enabled receives the OAM message that contains critical fault information from the opposite end, this alarm is generated.
Attribute
Parameters
Parameter 1 Indicates the type of the fault. l 0x01: A link fault occurs at the opposite port. l 0x02: Irrecoverable problems such as a power failure occur at the opposite end. l 0x03-0xFF: Other unknown faults occur.

The ETHOAM_RMT_CRIT_FAULT alarm is generated when the system runs the IEEE 802.3ah OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to
4 Alarm Processing
services. This alarm indicates that the signal loss alarm is generated at the receive end of the opposite port.
Possible Causes
The port with the OAM protocol enabled receives the OAM message that contains critical fault information from the opposite end, such as a link fault or power failure.
Procedure
Step 1 If a link fault occurs at the opposite port, query board-level alarms on the U2000. Remove the fault according to the specific link alarms such as L_SYNC and LINK_ERR. Check whether the alarm is cleared. Step 2 If irrecoverable problems such as a power failure occur at the opposite end, remove the fault. The alarm is automatically cleared. Step 3 If other unknown faults occur, contact Huawei engineers. ----End
Related Information
None
4.55 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating the remote loopback of the point-to-point Ethernet OAM. This alarm only occurs at the port with the point-to-point OAM protocol enabled. If the port is able to respond to loopback, it enters the loopback response state and reports the loopback response alarm after it receives the remote loopback enabling command sent by the opposite OAM port. The loopback initiation end reports the loopback initiation alarm. If the port receives the loopback disabling command, it exits the loopback response state and ends the loopback response alarm. The loopback initiation end also ends the loopback initiation alarm.
Attribute
Parameters
4 Alarm Processing
Name Parameter 1
Meaning l 0x01: The loopback is initiated. l 0x02: The loopback is responded.

The ETHOAM_RMT_LOOP alarm is generated when the system runs the IEEE 802.3ah OAM protocol. When this alarm is generated, it indicates that the services are looped back from the loopback initiation end to the loopback response end. The services and other packets are all interrupted.
Possible Causes
l l A command is issued to enable the loopback at the local port, and the opposite end is the loopback response end. A command is issued to enable the loopback at the opposite port, and the local end is the loopback response end.
Procedure
Step 1 Disable the loopback. The ETHOAM_RMT_LOOP alarm is automatically cleared. ----End
Related Information
None
4.56 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating the remote SD of the point-to-point Ethernet OAM. When the port with the OAM protocol enabled receives the link event message from the opposite end which indicates that the remote Ethernet performance is degraded, this alarm occurs.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
4 Alarm Processing
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the type of the received link event: l 0x01: error frame event l 0x02: error frame period event l 0x03: error frame second event

The ETHOAM_RMT_SD alarm is generated when the system runs the IEEE 802.3ah OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to services. When this alarm is generated, it indicates that the alarm indicating that the error frame crosses the threshold occurs at the receive end of the local port. The service performance degrades.
Possible Causes
The port with the OAM protocol enabled receives the link event message from the opposite end.
Procedure
Step 1 Improve the link performance at the opposite end until the opposite end does not send link event message to the local end, and therefore the ETHOAM_RMT_SD alarm at the local end is automatically cleared. Step 2 Modify the value of the link performance monitoring threshold at the opposite end. Then the ETHOAM_RMT_SD alarm at the local end is automatically cleared. Step 3 Disable the link event reporting at the opposite end. Then the ETHOAM_RMT_SD alarm at the local end is automatically cleared. ----End
Related Information
None
4.57 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating loopback of the MAC port that receives the OAM protocol packets in a point-to-point manner. If the MAC port of a board receives the OAM protocol packets sent by itself or the board after detection of the loop is enabled, the ETHOAM_SELF_LOOP alarm is reported.
Issue 02 (2011-10-31)
460
4 Alarm Processing
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the loopback type. l 0x01: self-loop of the port l 0x02: self-loop of the board l 0x03-0xff: other reasons

In the case of the ETHOAM_SELF_LOOP alarm, the port is in the self-loop state. The U2000 provides a function of automatically shutting down the port in the case of the ETHOAM_SELF_LOOP alarm. If the user enables this function in advance, services of this port are interrupted. Otherwise, a broadcast storm may occur.
Possible Causes
l l l Self-loop is performed for the port with a fiber. Loopback is set among ports of the board. The PHY/MAC loopback of the port is manually set.
Procedure
Step 1 Check whether the transmit and receive ends of the port are connected with a fiber. If yes, connect the fiber correctly, and then check whether the ETHOAM_SELF_LOOP alarm is cleared. Step 2 If the ETHOAM_SELF_LOOP alarm persists, check whether the transmit and receive ends of the port are connected to those of other ports with fibers. If yes, connect the fibers correctly, and then check whether the ETHOAM_SELF_LOOP alarm is cleared. Step 3 If the ETHOAM_SELF_LOOP alarm persists, check whether any PHY/MAC-layer loopback is set for the port. If yes, release the loopback, or wait for five minutes when the U2000 automatically releases the loopback. Then check whether the ETHOAM_SELF_LOOP alarm is cleared. ----End
4 Alarm Processing
Related Information
None
4.58 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP is an alarm indicating the loopback of the VCTRUNK port that receives the OAM protocol packets in a point-to-point manner. If the VCTRUNK port of a board receives the OAM protocol packets sent by itself or the board after detection of the loop is enabled, the ETHOAM_VCG_SELF_LOOP alarm is reported.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameters 1 and 2 Parameter 3 Meaning Indicate the VCG port number. Indicates the loopback type. l 0x01: The link of the VCG port is configured with a self-loop. l 0x02: The link between VCG ports is configured with a loop. l 0x03-0xff: There are other reasons.

In the case of the ETHOAM_VCG_SELF_LOOP alarm, the link of the VCG port is configured with a self-loop. The U2000 provides a function of automatically shutting down the port in the case of the ETHOAM_VCG_SELF_LOOP alarm. If the user enables this function in advance, services of this port are interrupted. If the user does not enable this function, a broadcast storm may occur.
Possible Causes
l l
Issue 02 (2011-10-31)
The links of the VCG port is configured with a self-loop. The links between VCG ports of the board is configured with a loop.
4 Alarm Processing
The port is configured with a loopback at the PHY/MAC layer manually.
Procedure
Step 1 Check the ETHOAM_VCG_SELF_LOOP alarm on the U2000, and determine the VCG port number according to Parameters 1 and 2. Step 2 Check the link configuration of the VCG port to see whether the transmit and receive directions of the port are connected. Make sure the link configuration is correct, and then check if the ETHOAM_VCG_SELF_LOOP alarm is cleared. Step 3 If the ETHOAM_VCG_SELF_LOOP alarm persists, check the link configuration of the VCG port to see whether this VCG port is connected to another VCG port on the board in the transmit and receive directions. Make sure that the link configuration is correct. Then, the ETHOAM_VCG_SELF_LOOP alarm is cleared. Step 4 If the alarm persists, check whether the port is configured with a loopback at the PHY/MAC layer. If the loopback exists, release it manually. ----End
Related Information
None
4.59 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the maintenance point (MP) ID conflict. When an MP receives the message sent by another MP with the same MP ID in a maintenance domain, this alarm occurs.
Attribute
Parameters
Parameters 1 and 2 Indicates the number of the Ethernet port where the alarm is generated.
Issue 02 (2011-10-31)
463
4 Alarm Processing
Parameter
Description
Parameters 3 and 4 Indicates the VLAN ID. Parameter 5 Parameters 6 to 9 Indicates the level of the maintenance domain. Indicates the ID of the MP where the alarm occurs. The highest byte indicates the network ID. The second highest byte indicates the node ID of the network. The lower two bytes indicate the identifier of the MP on the network node. The MP should be unique networkwide. Each node supports a maximum of 1024 MPs (each data board supports a maximum of 128 MPs).

The MP should be unique networkwide. The MP conflict can affect the protocol and cause the LB and LT tests to become abnormal. The services may be incorrectly received.
Possible Causes
Multiple MPs with the same MPID are created in a maintenance domain.
Procedure
Step 1 View the EX_ETHOAM_MPID_CNFLCT alarm on the U2000 and confirm the ID of the relevant MP according to the alarm parameters. Step 2 Query the information about the MP. Delete all the MPs that repeat the MPID, the alarm is automatically cleared. ----End
Related Information
None
4.60 EXT_MODULE_OFFLINE
Description
Extended wavelengh module offline. This alarm is generated when a user has configured services on the channel corresponding to an extended module, but the physical extended module is offline.
Attribute
Issue 02 (2011-10-31)
464
4 Alarm Processing
Parameters
None

All services on the channel corresponding to the extended module are unavailable.
Possible Causes
A user has configured services on the channel corresponding to the extended module, but the physical extended module is offline.
Procedure
Step 1 Check whether services on the channel corresponding to the extended module are necessary. Step 2 If the services are necessary, check whether an extended module is properly installed. If the extended module is properly installed, replace it with a new one. Step 3 If services are not necessary, delete the services. ----End
Related Information
None
4.61 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm is generated when the system detects the loss of the external clock source traced by the equipment. Reported from the WDM side or client side: NA
Attribute
Parameters
Name Parameter 1 Parameter 2 Meaning Indicates the number of the subrack where the clock board is located. The value is always 0xf0.
Issue 02 (2011-10-31)
465
4 Alarm Processing
Name Parameter 3 Parameter 4
Meaning Indicates the reserved byte, whose value is always 0x00. Indicates which external clock source is lost. l 0x01: The first external clock source is lost. l 0x02: The second external clock source is lost.

When the EXT_SYNC_LOS alarm is generated, the external clock source of the system is lost and cannot be traced by the equipment. This is because the clock quality may be lowered, the service quality may be affected, and pointer justifications and even bit errors may be generated.
Possible Causes
The possible causes of the EXT_SYNC_LOS alarm are as follows: l l l l Cause 1: The physical interface for the external clock source loses signals. Cause 2: The input and output modes of the external clock source are inconsistent. Cause 3: The clock input cable is incorrectly connected. Cause 4: The clock board is faulty.
Procedure
l l Query alarms on the U2000. Determine the number of the subrack where the clock loss occurs and which clock is lost according to the alarm parameters. Cause 1: The physical interface for the external clock source loses signals. 1. Check whether the output signals of the external clock equipment are normal. If not, replace the faulty external clock equipment, and then check whether the alarm is cleared. If the alarm persists, check whether the input and output modes of the external clock source are consistent. After the input and output of the external clock source are set to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared. For details, see Configuring Physical Clock in the Feature Description. If the alarm persists, check whether the clock input cable is correctly connected. If not, ensure the correct connection of the clock input cable, and then check whether the alarm is cleared. For details, see the Installation Guide. If the alarm persists, perform cold reset on the timing board, and then check whether the alarm is cleared. For details, see Performing a Cold Reset of a Board in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
Cause 2: The input and output modes of the external clock source are inconsistent. 1.
Cause 3: The clock input cable is incorrectly connected. 1.
Cause 4: The clock board is faulty. 1.
2. ----End
Issue 02 (2011-10-31)
466
4 Alarm Processing
Related Information
4.62 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm indicating the loss of the external timing source. This alarm is generated when the board does not detect the external timing signal after the external timing port is enabled. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Parameter 3 Parameter 4 Meaning Indicates the number of the subrack where the clock board is located. The value is always 0xf0. Indicates the reserved byte, whose value is always 0x00. Indicates which external timing source is lost. l 0x02: The first external timing source is lost. l 0x04: The second external timing source is lost.

The time of the local NE cannot be synchronous with the time of the external timing equipment to which the enabled external timing port is connected.
Possible Causes
The possible causes of the EXT_TIME_LOC alarm are as follows:
4 Alarm Processing
l l l
Cause 1: The physical interface for the external timing source loses signals. Cause 2: The timing input cable is incorrectly connected. Cause 3: The clock board is faulty.
Procedure
l l Query alarms on the U2000. Determine the number of the subrack where the external timing loss occurs and which external timing source is lost according to the alarm parameters. Cause 1: The physical interface for the external timing source loses signals. 1. Check whether the output signals of the external timing equipment are normal. If not, replace the faulty external timing equipment, and then check whether the alarm is cleared. If the alarm persists, check whether the timing input cable is correctly connected. If not, ensure the correct connection of the timing input cable, and then check whether the alarm is cleared. For details, see "Installing and Routing Clock Cables" in the Quick Installation Guide. If the alarm persists, perform cold reset for the clock board, and then check whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board" in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see "Replacing the Clock Board" in the Parts Replacement.
Cause 2: The timing input cable is incorrectly connected. 1.
2. ----End
Related Information
For details, see "IEEE 1588v2" in the Feature Description.
4.63 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating a fan failure. This alarm is generated when one or more fans fail.
Attribute
Parameters
None
4 Alarm Processing

The failure of one or more fans leads to the increase on the board temperature and even the damage to the board.
Possible Causes
l l l The fans stop running. The speed of the fans is excessively low. The fans fail.
Procedure
Step 1 Check whether the FAN Speed Level is set to Stop or Low Speed through the U2000. If that is the case, set FAN Speed Level to High Speed. Step 2 If the alarm persists, replace the faulty fan tray assembly. For details, see the Parts Replacement. ----End
Related Information
None
4.64 FAN_FAULT
Description
The FAN_FAULT is an alarm indicating a fan fault. This alarm is generated when one fan fails.
Attribute
Parameters
None

The failure of one fan may lead to the increase on the board temperature and even the damage to the board.
Possible Causes
l l
Issue 02 (2011-10-31)
One fan fails. The logical inspection fails.

4 Alarm Processing
Procedure
Step 1 Replace the fan tray assembly. For details, see the Parts Replacement. ----End
Related Information
None
4.65 FEATURE_WITHOUT_LICENSE
Description
Service without license. A license-controlled feature is used but a license for the feature is not installed.
Attribute
Parameters
None

A user cannot create, enable, or modify the license-controlled service or feature, but can query, delete, or deactivate the service or feature. The available services are not affected and are still available, but the alarm is reported.
Possible Causes
A license-controlled feature is used but a license for the feature is not installed. The possible causes why the feature is not authorized are as follows: l l l A license for this feature is not purchased. The license file does not match ESN or V/R version, and the system has been operating for 60 consecutive days. The trial period of the license-controlled feature has expired, and the keepalive period of 60 days has also elapsed since the expiry.
Procedure
Step 1 Load a correct license file onto the system so that the license-controlled feature is authorized, or delete the service of unauthorized feature. ----End
4 Alarm Processing
Related Information
None
4.66 FC_8B10BERR_OVER
Description
The FC_8B10BERR_OVER is an alarm indicating that the 8B10B bit errors in the FC services cross the threshold. When the 8B10B bit errors in the FC services cross the threshold, this alarm is generated.
Attribute
Parameters
None

The quality of services is affected.
Possible Causes
There are bit errors on the link, which causes the 8B10B bit errors on the ports of the FC link layer after decoding cross the threshold.
Procedure
Step 1 Check whether there is dust on the optical fiber connector or the fiber is aged. If that is the case, clean the optical fiber connector or replace the fiber. For details, see the Supporting Tasks. Step 2 Step 2 Check whether the input optical power of the board is within the normal range. For optical power specifications, see the corresponding Product Description. If the optical power is abnormal, see the handing procedures for the IN_PWR_HIGH and IN_PWR_LOW alarms, to clear the alarm. ----End
Related Information
None
4.67 FCS_ERR
4 Alarm Processing
Description
The FCS_ERR is an alarm indicating that the frame check sequence (FCS) is incorrect. At the local station, perform an FCS check for the received frames encapsulated in the GFP format. If any error occurs in the check, the alarm is reported.
NOTE
The alarm is generated only when the received service of the local station is the GFP service. This is because the IDLE frame lacks the FCS field, if the IDLE frame is encapsulated in the GFP format, the FCS check errors may occur.
Attribute
Parameters
None

l l If the FCS_ERR alarm is generated due to inconsistent encapsulation protocols, the services are interrupted. If the FCS_ERR alarm is generated due to bit errors in the system, packets are lost or services are interrupted.
Possible Causes
The possible causes of the FCS_ERR alarm are as follows: l Cause 1: Mapping protocols of the local station and opposite station are inconsistent. For example, the local station uses the GFP encapsulation protocol whereas the opposite station uses the LAPS encapsulation protocol. Or the parameter settings of the protocol are inconsistent. For example, both stations use the GFP encapsulation but Extension Header Option of the local station is set to Yes whereas Extension Header Option of the opposite station is set to No. Cause 2: There are bit errors on the link. Cause 3: The optical connector of the Ethernet board at the optical interface is loose or dirty. Cause 4: The board is faulty.
l l l
Procedure
l l Query current alarms on the U2000. Determine the VCTRUNK number that reports the alarm. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The encapsulation protocols adopted by the local station and the opposite station are inconsistent or the settings of the protocol parameters are inconsistent. 1. Check whether the encapsulation protocols of corresponding VCTRUNK ports of the local station and the opposite station are consistent and whether the parameter settings
Issue 02 (2011-10-31)
4 Alarm Processing
of the protocols are consistent. For example, check whether the parameters such as Scramble and Set Inverse Value for CRC about the protocols are set as the same. For details, see the Configuration Guide. Then, check whether the alarm is cleared. 2. l 1. If the alarm persists, see Cause 2. Check the network-wide alarms on the U2000. For operations, see the Routine Maintenance. Check whether there are bit error alarms such as B3_EXC and B3_SD on the link. If these alarms occur, clear these alarms according to corresponding procedures. Then, check whether the alarm is cleared. If the alarm persists, see Cause 3. Cause 2: There are bit errors on the link.
2. l
Cause 3: The optical connector of the Ethernet board at the optical interface is loose or dirty. 1. 2. Check whether the connector of the fiber is normal. If the connector is loose, tighten the connector. See Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task to check whether the connector is dirty. If the connector is dirty, ensure that it is cleaned immediately. For operations, see the Supporting Task. Cleaning Optical Fiber Connectors Using Cartridge Cleaners Cleaning Optical Fiber Connectors Using Lens Tissue Cleaning Optical Adapters Using Optical Cleaning Sticks 3. If the attenuation value of the optical attenuator is improper, increase or decrease it to a proper value. The value of the optical attenuator is set according to the receive optical power of the board. For optical power specifications of boards, see "Technical Specifications" of the Product Description. For operations of adjusting the optical attenuator, see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task. For operations of querying the optical power, see Querying Optical Power of the Board in the Supporting Task.
NOTE
From Querying Optical Module Information in the Supporting Task or Hardware Description, you can obtain the manufacturer information of the optical module on the board.
4. l 1.
Check whether the alarm is cleared. If the alarm persists, see Cause 4. After the preceding causes are excluded, if the alarm persists, the board where the alarm is reported is faulty. In the case of the Ethernet board with an interface board, replace the interface board first. In the case of the board without an interface board, replace the faulty board. For details, see Parts Replacement.
Cause 4: The board is faulty.
----End
Related Information
None
Issue 02 (2011-10-31)
473
4 Alarm Processing
4.68 FEC_LOF
Description
The FEC_LOF is an alarm indicating that lost of the FEC frame. The alarm occurs when the FEC frame is lost.
Attribute
Parameters
None

When the FEC_LOF alarm is generated, the FEC function is disabled. Consequently, the services are interrupted.
Possible Causes
l l l l l The cable is faulty, or the optical power is improper. The service rate is incorrect. The clocks on the NEs are out of synchronization. The board hardware is faulty. Certain problems are found in the services from the opposite end.
Procedure
Step 1 View the FEC_LOF alarm on the U2000 to determine the relevant board. Step 2 View the receive optical power of the board on the U2000. If the receive optical power is excessively low, clean the fiber header and connector. If the receive optical power is excessively high, provide more optical attenuators. After making sure that the receive optical power is proper, check whether the FEC_LOF alarm is cleared. Step 3 If the alarm persists, check whether the upstream service is the FEC service at the same rate. If not, configure the FEC service at a correct rate, and then check whether the FEC_LOF alarm is cleared. Step 4 If the alarm persists, check whether the upstream service is supported by the board. If not, configure a correct service, and then check whether the FEC_LOF alarm is cleared. Step 5 If the alarm persists, check whether the clocks on the local NE and the opposite NE are synchronous with those on the network. If not, set the clock tracing function, and then check whether the FEC_LOF alarm is cleared.
4 Alarm Processing
Step 6 If the alarm persists, the board hardware may be faulty. In this case, replace the board that reports the alarm at the local station. Step 7 If the alarm persists, the board at the opposite station may be faulty. In this case, replace the board. ----End
Related Information
None
4.69 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out-of-frame.
Attribute
Parameters
None

When the FEC_OOF alarm is generated, the FEC function is disabled. Consequently, the services are interrupted.
Possible Causes
l l l l The fiber is faulty, or the optical power is improper. Excessive bit errors occur during transmission. The clocks on the NEs are out of synchronization. The transmit unit at the opposite end is faulty.
Procedure
Step 1 View the FEC_OOF alarm on the U2000 to determine the relevant board. Step 2 View the received optical power of the board on the U2000. If the received optical power is excessively low, clean the fiber header and the connector. If the received optical power is excessively high, provide more optical attenuators. After making sure that the received optical power is proper, check whether the FEC_OOF alarm is cleared. Step 3 If the alarm persists, check the transmit optical power at the opposite end. If the transmit optical power is excessively low, replace the board at the opposite end.
4 Alarm Processing
Step 4 If the alarm persists, check whether the clocks on the local NE and the opposite NE are synchronous with those on the network. If not, set the clock tracing function, and then check whether the FEC_OOF alarm is cleared. Step 5 If the alarm persists, check whether the fiber is normal. If yes, replace the board that generates the alarm. Step 6 If the alarm persists, replace the cross-connect and timing board at the local station. Step 7 If the alarm persists, replace the line board at the opposite end. Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite end. ----End
Related Information
None
4.70 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the input flow at the Ethernet port exceeds the threshold. When the received traffic at the Ethernet port exceeds the expected traffic, this alarm is generated.
Attribute
Parameters
Parameters 1 and 2 Indicates the extra traffic (Mbit/s) of the actual traffic that exceeds the expected traffic.

l During data transmission, when the configured bandwidth is lower than the actual traffic at the port and there is the FLOW_OVER alarm, service packets are lost.
Issue 02 (2011-10-31)
4 Alarm Processing
During data transmission, when the configured bandwidth is higher than or equal to the actual traffic at the port and there is the FLOW_OVER alarm, the system and the services are not affected.
Possible Causes
The traffic received by the port is greater than the preset traffic at the port.
Procedure
Step 1 View the information about the alarm on the U2000 and identify the board and number of the port where the alarm is reported. l l If the expected traffic at the port can be increased, increase the expected traffic to a value greater than the actual traffic at the port. If the expected traffic at the port cannot be increased, service packet loss can be avoided only by reducing the traffic transmitted by the opposite station.
----End
Related Information
None
4.71 FPGA_ABN
Description
The FPGA_ABN is an alarm indicating that the FPGA status is abnormal. The alarm occurs when the standby FPGA is currently used by the board.
Attribute
Parameters
None

The active FPGA file of the board is abnormal and the standby FPGA file is enabled. If the standby FGPA file is abnormal, the board cannot work, which has an influence on the services of users. This problem needs to be handled in time.
Possible Causes
l
Issue 02 (2011-10-31)
The active FPGA file does not exist when the board starts.
4 Alarm Processing
Loading of the active FPGA file fails when the board starts.
Procedure
Step 1 Reload the FPGA file to the board. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.72 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is forcibly selected.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the slot of the clock board that is selected forcibly. l 0x01 indicates the slot with a smaller number. l 0x02 indicates the slot with a bigger number.

If the forcibly selected clock board is normal, transient interruption occurs when the services are switched. Otherwise, the services are interrupted.
Possible Causes
The command of forcibly selecting the clock board is issued.
4 Alarm Processing
Procedure
Step 1 After the command of forcibly selecting the clock board is cancelled, the FSELECT_STG alarm is automatically cleared. ----End
Related Information
None
4.73 FWD_PKT_LOSS
Description
The FWD_PKT_LOSS is an alarm indicating loss of packets at a certain port
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates why the packets are lost.

The services lose packets or are interrupted.
Possible Causes
l l l l l
Issue 02 (2011-10-31)
The packets received by the port do not match the service configuration. The packets received by the port do not match the port configuration. Packets are lost because of data congestion, such as the loss of the CAR shaping packet. The packets in a queue are lost, such as the loss of the COS packet. The MAC address of the received packets is listed on the black list.
4 Alarm Processing
Procedure
Step 1 Check whether the service configuration and the attribute configuration of the port match the received packets. If a mismatch occurs, re-configure the service and/or the attributes of the port. Step 2 If the alarm persists, check whether the packets transmitted at the opposite station are proper. If not, transmit proper packets again. Step 3 If the alarm persists, check whether the QoS is configured properly. If not, re-configure the QoS. Step 4 If the alarm persists, check whether the black list is configured properly. If not, re-configure the black list. ----End
Related Information
None
4.74 GAINDATA_MIS
Description
The GAINDATA_MIS is an alarm indicating mismatch of gain attribute. When the nominal gain value issued by the NE software falls beyond the tuning range of the nominal gain, the alarm is reported.
Attribute
Parameters
None

The service quality may be affected.
Possible Causes
Cause 1: As for the nominal gain, replacing the optical amplifier unit (OAU) or the optical module causes that the nominal gain value issued by the NE software falls beyond the new tuning range of the nominal gain.
Procedure
l Cause 1: The nominal gain value issued by the NE software falls beyond the new tuning range of the nominal gain.
Issue 02 (2011-10-31)
4 Alarm Processing
1.
Query the threshold of the current actual nominal gain on the U2000. Reconfigure a valid nominal gain value for the optical interface channel of the unit based on the queried threshold.
----End
Related Information
None
4.75 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware failure. When the system detects hardware failure, this alarm is reported. Reported from the WDM side or client side: NA
Attribute
Parameters
Issue 02 (2011-10-31)
481
4 Alarm Processing
Parameter Parameter 1
Description Indicates the fault type of the alarm. For example: 0x01 indicates that the power supply module is abnormal. 0x02 indicates that the board is not properly installed (the board is not in good contact with the backplane, that is, the board is not secured). 0x03 indicates that 38M system clock 1 is abnormal. 0x04 indicates that 38M system clock 2 is abnormal. 0x05 indicates that the 2M clock source is abnormal. 0x06 indicates the digital phase-locked loop is abnormal. 0x07 indicates that the 38M service clock is lost. 0x08 indicates that the bus is abnormal. 0x09 indicates that the standby board in TPS protection is abnormal. 0x0a indicates the active crystal oscillator of the clock stops. 0x0b indicates the frequency deviation of the crystal oscillator is excessively large. 0x0c indicates that the standby crystal oscillator of the clock stops. 0x0d indicates that the CPU/DSP/coprocessor fails. 0x0e indicates that the memory component the fails. 0x0f indicates that the component of the programmable logic device fails 0x10 indicates that the SDH component fails. 0x11 indicates that the data communication component fails. 0x12 indicates that the clock component fails. 0x13 indicates that the interface component fails. 0x14 indicates that the power component fails. 0x15 indicates that other faults occur. 0x16 indicates that the simulated phase-locked loop (PLL) is abnormal. 0x17 indicates that the 32M clock is invalid. 0x18 indicates that the 66M clock is invalid. 0x19 indicates that the 25M clock is invalid. 0x1a indicates that the loop of the cross-connect chip fails.
Issue 02 (2011-10-31)
482
4 Alarm Processing
Parameter
Description 0x1b indicates that the 8k online signal is pulled down. 0x1c indicates that the chip of the probe laser fails. 0x1d indicates that the chip of the loading laser fails. 0x1e indicates that the clock of the DSP driver chip is lost. 0x1f indicates that the output clock of the DSP is lost. 0x20 indicates that the RTM module is offline. 0x21 indicates that a chip fault. 0x22 indicates the 2M system frame header 1. 0x23 indicates the 2M system frame header 2. 0x24 indicates that the self-check fails. 0x25 indicates the self-check of the PHY chip fails. 0x26 indicates that detecting the port status of the PHY chip fails. 0x27 indicates that the 25M clock is lost. 0x28 indicates that the APD fails.
Parameters 2 and Parameters 3 When Parameter 1 is 0x08 and Parameter 2 is 0x01, it indicates that bus A is abnormal; When Parameter 1 is 0x08 and Parameter 2 is 0x02, it indicates that bus B is abnormal. Parameter 3 is 0xff. When Parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have different values, which indicate different component, module, or chip faults. When Parameter 1 is 0x15, Parameter 2 and Parameter 3 indicate other equipment faults. When Parameter 1 is of another value, Parameter 2 and Parameter 3 are always 0xff.

The alarm affects the normal operating of the board and affects services.
Possible Causes
l l Cause 1: The NE power is abnormal. Cause 2: The board is not connected to the backplane properly or the board is faulty.
Issue 02 (2011-10-31)
483
4 Alarm Processing
Procedure
l Cause 1: The NE power is abnormal. 1. l Check whether the NE power works normally. If not, feed the NE with power supply. For details, see the Installation Guide. Reseat the board. For operations, see the Installation Guide. In the case of the OptiX OSN 6800 and OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting Boards". In the case of the OptiX OSN 3800 equipment, see "Removing Boards" and "Inserting Boards".. Then, check whether the alarm is cleared. If the alarm persists, replace the board. For details, see the Parts Replacement.
Cause 2: The board is not connected to the backplane properly or the board is faulty. 1.
2. ----End
Related Information
None
4.76 HARD_ERR
Description
The HARD_ERR is an alarm indicating a hardware error. The alarm occurs when the board hardware has a minor fault. Reported from the WDM side or client side: NA
Attribute
Parameters
Issue 02 (2011-10-31)
484
4 Alarm Processing
Description Indicates the fault type of the alarm. For example: 0x01 indicates that the power supply module is abnormal. 0x02 indicates that the board is not properly installed (the board is not in good contact with the backplane, that is, the board is not secured). 0x03 indicates that 38M system clock 1 is abnormal. 0x04 indicates that 38M system clock 2 is abnormal. 0x05 indicates that the 2M clock source is abnormal. 0x06 indicates the digital phase-locked loop is abnormal. 0x07 indicates that the 38M service clock is lost. 0x08 indicates that the bus is abnormal. 0x09 indicates that the standby board in TPS protection is abnormal. 0x0a indicates the active crystal oscillator of the clock stops. 0x0b indicates the frequency deviation of the crystal oscillator is excessively large. 0x0c indicates that the standby crystal oscillator of the clock stops. 0x0d indicates that the CPU/DSP/coprocessor fails. 0x0e indicates that the memory component the fails. 0x0f indicates that the component of the programmable logic device fails 0x10 indicates that the SDH component fails. 0x11 indicates that the data communication component fails. 0x12 indicates that the clock component fails. 0x13 indicates that the interface component fails. 0x14 indicates that the power component fails. 0x15 indicates that other faults occur. 0x16 indicates that the simulated phase-locked loop (PLL) is abnormal. 0x17 indicates that the 32M clock is invalid. 0x18 indicates that the 66M clock is invalid. 0x19 indicates that the 25M clock is invalid. 0x1a indicates that the loop of the cross-connect chip fails.
Issue 02 (2011-10-31)
485
4 Alarm Processing
Parameter
Description 0x1b indicates that the 8k online signal is pulled down. 0x1c indicates that the chip of the probe laser fails. 0x1d indicates that the chip of the loading laser fails. 0x1e indicates that the clock of the DSP driver chip is lost. 0x1f indicates that the output clock of the DSP is lost. 0x20 indicates that the RTM module is offline. 0x21 indicates that a chip fault. 0x22 indicates the 2M system frame header 1. 0x23 indicates the 2M system frame header 2. 0x24 indicates that the self-check fails. 0x25 indicates the self-check of the PHY chip fails. 0x26 indicates that detecting the port status of the PHY chip fails. 0x27 indicates that the 25M clock is lost. 0x28 indicates that the APD fails.
Parameters 2 and Parameters 3 When Parameter 1 is 0x08 and Parameter 2 is 0x01, it indicates that bus A is abnormal; When Parameter 1 is 0x08 and Parameter 2 is 0x02, it indicates that bus B is abnormal. Parameter 3 is 0xff. When Parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have different values, which indicate different component, module, or chip faults. When Parameter 1 is 0x15, Parameter 2 and Parameter 3 indicate other equipment faults. When Parameter 1 is of another value, Parameter 2 and Parameter 3 are always 0xff.

The services are not affected. For specific influence, see Parameter 1.
Possible Causes
Issue 02 (2011-10-31)
486
4 Alarm Processing
Procedure
Step 1 Perform warm reset or cold reset on the faulty board through the U2000. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.77 HP_LOM
Description
The HP_LOM is an alarm indicating higher order path loss of multiframe.
Attribute
Parameters
None

When the HP_LOM alarm occurs, it indicates that the values of the H4 bytes in the payload are inconsistent with the expected values in several consecutive basic frames in the multiframe sequence. The multiframe indication of the VC-12 services is lost. As a result, the VC-12 services are unavailable. When the HP_LOM alarm occurs, the board will insert VTAIS (TU_AIS for tributary services) into the corresponding path.
Possible Causes
The possible causes of the HP_LOM alarm are as follows: l l The services are incorrectly configured. The H4 byte is lost or the H4 byte value is invalid.
Procedure
Step 1 Check whether the services at the opposite station and the local station are correctly configured. If not, modify the incorrect configuration and issue it again.
4 Alarm Processing
Step 2 View alarms on the U2000 to check whether the HP_LOM alarm is cleared. Options If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 3 Check whether the cross-connect unit and the line board are faulty. You can employ the optical path self-loop method to check whether any hardware of the opposite station is faulty. If the fault is located on the opposite station. Replace the line board first and then the SCC board of the opposite station. Step 4 View alarms on the U2000 to check whether the HP_LOM alarm is cleared. Options If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 5 Ensure the local station is faulty. Replace the faulty board. ----End
Related Information
None.
4.78 HP_RDI
Description
The HP_RDI is an alarm indicating that the local station receives the remote defect indication in the higher order path sent from the opposite station
Attribute
Parameters
None
Issue 02 (2011-10-31)
488
4 Alarm Processing

When the HP_RDI alarm occurs, it indicates that the services received by the opposite station have the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm. As a result, the HP_RDI alarm is sent to the local station.
Possible Causes
The possible causes of the HP_RDI alarm are as follows: l l l The opposite line receives the AU_AIS/AU_LOP/HP_TIM/HP_SLM alarms. The receive part at the opposite station is faulty. The transmit part at the local station is faulty.
Procedure
Step 1 View the alarms of the NE on the U2000 and check whether there are higher order alarms. Options If the AU_AIS, AU_LOP, HP_TIM, and HP_SLM alarms occur If the AU_AIS, AU_LOP, HP_TIM, and HP_SLM alarms do not occur Description Refer to the corresponding section in this document to clear the alarm. Proceed to the next step.
Step 2 View alarms on the U2000 to check whether the HP_RDI alarm is cleared. Options If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 3 Perform the loopback for the stations at two ends of the line. Locate the faulty board. Options The board at the opposite station reports the HP_RDI alarm The board at the local station reports the HP_RDI alarm Description The transmit end of the board at the opposite station is faulty. Replace the faulty board. The receive end of the board at the local station is faulty. Replace the faulty board.
----End
Related Information
AU_AIS, AU_LOP, HP_TIM, HP_SLM
4 Alarm Processing
4.79 HP_REI
Description
The HP_REI is an alarm indicating that the local station receives the remote bit error in the higher order path sent from the opposite station.
Attribute
Alarm Severity Warning Alarm Type Service quality alarm
Parameters
None

When the HP_REI alarm occurs, it indicates that the services received by the opposite station have the higher order B3 errored blocks. As a result, the HP_REI alarm is sent to the local station.
Possible Causes
The possible cause of the HP_REI alarm is as follows: The B3 bit errors are received at the opposite station.
Procedure
Step 1 View the alarms on the opposite NE, and check whether there are B1 or B2 bit errors. Options There are B1 or B2 bit errors There are B1 or B2 bit errors Description Refer to the corresponding section in this document to clear the alarm. Proceed to the next step.
Step 2 Check whether the equipment is securely grounded and whether there is intense interference source around the equipment. If few B3 bit errors occur at the remote end, the fault usually lies in the equipment instead of the optical path. Step 3 Perform the loopback for the stations at two ends of the line. Check whether the cross-connect and timing unit and the tributary board on both the opposite equipment and local equipment operate normally. Following the service direction, check upstream stations one by one. Locate the faulty board.
4 Alarm Processing
Options The board at the opposite station reports B3 bit errors The board at the local station reports B3 bit errors
Description The receive end at the opposite station is faulty. Replace the boards in an order of line board, tributary board, and SCC board. The transmit end of the board at the local station is faulty. Replace the faulty board.
CAUTION
Replacing the tributary board will interrupt services. This operation is of risk. ----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD
4.80 HP_SLM
Description
The HP_SLM is an alarm indicating the mismatch of the higher order path signal label (C2) received by the line board.
Attribute
Parameters
None

When the HP_SLM alarm occurs, it indicates that the higher order overhead C2 byte received by the local station is inconsistent with the C2 byte expected. As a result, the services in the payload are unavailable. When the HP_SLM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_SLM alarm are as follows:
4 Alarm Processing
l l
The signal label C2 byte expected to be received by the local station is inconsistent with that transmitted by the opposite station. The services are incorrectly configured.
Procedure
Step 1 Check whether the C2 byte transmitted by the corresponding higher order path at the opposite station is consistent with that expected to be received by the local station. If the configuration is different, modify them to be consistent and issue the configuration again. Step 2 View alarms on the U2000 to check whether the HP_SLM alarm is cleared. Option If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 3 Check whether the services at the opposite station and the local station are correctly configured. If not, modify the incorrect configuration and issue it again. Step 4 View alarms on the U2000 to check whether the HP_SLM alarm is cleared. Option If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 5 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and local equipment to locate the faulty board. Option The board at the opposite station reports the HP_SLM alarm The board at the local station reports HP_SLM bit errors Description The receive end at the opposite station is faulty. Replace the boards in an order of line board and SCC board. The receive end of the board at the local station is faulty. Replace the faulty board.
CAUTION
Replacing the board will interrupt services. This operation is of risk. ----End
Related Information
None.
4 Alarm Processing
4.81 HP_TIM
Description
The HP_TIM is an alarm indicating the mismatch of the higher order path trace identifier (J1) received by the line board.
Attribute
Parameters
None

When the HP_TIM alarm occurs, it indicates that the higher order overhead J1 byte received by the local station is inconsistent with the J1 byte expected. As a result, the services in the payload are unavailable. When the HP_TIM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_TIM alarm are as follows: l l The path trace identifier J1 byte expected to be received by the local station is inconsistent with that transmitted by the opposite station. The services are incorrectly configured.
Procedure
Step 1 Check whether the J1 byte transmitted by the corresponding higher order path at the opposite station is consistent with that expected to be received by the local station. If not, modify them to be consistent and issue the configuration again. Step 2 View alarms on the U2000 to check whether the HP_TIM alarm is cleared. Options If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 3 Check whether the services at the opposite station and the local station are correctly configured. If not, modify the incorrect configuration and issue it again.
4 Alarm Processing
Step 4 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and local equipment to locate the faulty board. Option The board at the opposite station reports the HP_TIM alarm The board at the local station reports HP_TIM bit errors Description The receive end at the opposite station is faulty. Replace the boards in an order of line board and SCC board. The receive end of the board at the local station is faulty. Replace the faulty board.
CAUTION
Replacing the board will interrupt services. This operation is of risk. ----End
Related Information
None.
4.82 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the higher order path received by the line board is unloaded.
Attribute
Parameters
None

When the HP_UNEQ alarm occurs, it indicates that the signal payload transmitted by the line board at the opposite station is unloaded.
Possible Causes
The possible cause of the HP_UNEQ alarm is as follows:
4 Alarm Processing
The C2 byte in five consecutive frames is all "0"s.
Procedure
Step 1 Check the C2 byte configuration of the opposite NE to see whether the C2 byte has sent UNEQ. If the configuration is incorrect, modify and re-issue the configuration. Step 2 Check whether the line board of the opposite NE is configured with services in the transmitting direction. If not, re-configure the services of the NE. Step 3 View alarms on the U2000 to check whether the HP_UNEQ alarm is cleared. Options If this alarm is cleared If this alarm persists Description The fault is removed. End the alarm handling. Proceed to the next step.
Step 4 The board at the local station is faulty. Replace the faulty board. ----End
Related Information
None.
4.83 HSC_UNAVAIL
Description
The HSC_UNAVAIL is an alarm indicating that the working/protection switching fails. This alarm occurs when the configured active and standby boards fail to perform switching
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the working/protection status of the invalid board.
Issue 02 (2011-10-31)
495
4 Alarm Processing
Description Indicates the slot ID of the invalid board.

The active-standby switching and backup functions are not available.
Possible Causes
l l l The active and standby board versions mismatch. The hardware of the standby board is faulty. Communication between the active and standby boards is abnormal.
Procedure
Step 1 Replace the standby board. For details, see the Parts Replacement. ----End
Related Information
None
4.84 INTRA_OTU_STA_INDI
Description
The INTRA_OTU_STA_INDI alarm indicates the state of the Intra-OTU 1+1 optical channel protection group. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
Attribute
Parameters
Issue 02 (2011-10-31)
496
4 Alarm Processing
Parameter Parameters 1
Description Indicate the switch request status. For example: l 0x0F: Lockout l 0x0E: Forced Switch l 0x0C: SF Switch l 0x09: SD Switch l 0x07: Manual Switch l 0x05: WTR

l l When the intra-board 1+1 protection group actuates switching, services are transiently interrupted. When the alarm is reported, the working channel or the protection channel of the board might have faulty services that need to be restored.
Possible Causes
l l l Cause 1: A user issues a command to perform the external switching such as forced switching, manual switching or locked switching. Cause 2: The services of the working channel or the protection channel of the intra-board 1+1 protection group are faulty. Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
l Cause 1: A user issues a command to perform the external switching. 1. On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching or locked switching, check whether the external switching operation is necessary. If the external switching operation is necessary, ignore the alarm. If the external switching operation is unnecessary, issue a command to clear the external switching.
2. 3. l
Cause 2: The services of the working channel or the protection channel of the intra-board 1+1 protection group are faulty. 1. Query whether the relevant boards for configuring the protection group have the alarms, such as R_LOF, R_LOS, POWER_DIFF_OVER, R_LOC, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC. If yes, handle the alarms by referring to the corresponding alarm handling procedure to restore the services of the working channel or the protection channel. If the alarm persists, check whether the attribute of the protection group is Revertive or not. If yes, the protection channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive.
2.
Issue 02 (2011-10-31)
4 Alarm Processing
Then the protection channel automatically switches to the working channel and the alarm clears. l Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears. 1. ----End This alarm requires no handling. After WTR Times (s), the alarm clears.
Related Information
For details, see "Intra-Board 1+1 Protection" in the Feature Description.
4.85 IPA_SHUT
Description
Laser shutdown by IPA. When the IPA function detects a LOS alarm for an input port of a board, it automatically shuts down the laser for the corresponding output port of the board.
Attribute
Parameters
None

The laser on the corresponding output port of the board is shut down and therefore cannot launch optical power to the downstream board.
Possible Causes
l l l The line fiber is damaged. As a result, the board reports a MUT_LOS alarm. The line loss is excessive. As a result, the input optical power is lower than the LOS threshold of the board. The board is faulty. As a result, it reports a MUT_LOS alarm.
Procedure
Step 1 On the U2000, check whether a MUT_LOS alarm is reported on the boards in an IPA pair. If the alarm is reported, clear the alarm by referring to MUT_LOS. After the fault on the line is rectified, the laser on the board that reports the IPA_SHUT alarm is enabled again and the IPA_SHUT alarm is automatically cleared. ----End
4 Alarm Processing
Related Information
The system provides the intelligent power adjustment (IPA) function for PID boards. For details, see "Introduction to PID IPA" in the Feature Description.
4.86 J0_MM
Description
The J0_MM is an alarm indicating trace indicator mismatch. The alarm occurs when the received J0 byte is not consistent with the J0 byte to be received. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

The services are not affected.
Possible Causes
l l The J0 byte mismatches. The service connection is incorrect.
Procedure
Step 1 Check whether the J0 byte to be transmitted by the board at the opposite station is set the same as the J0 byte to be received by the board at the local station. If they are inconsistent, set the two as the same. Step 2 If the alarm persists, bit errors may exist in the line. Refer to the handling procedure of the B1_SD or B2_SD alarm for troubleshooting. Step 3 If the alarm persists, consider whether to replace the board according to the actual situation because only the J0_MM alarm does not affect the services. For details, see the Parts Replacement. ----End
Related Information
None
4 Alarm Processing
4.87 K1_K2_M
Description
The K1_K2_M is an alarm indicating K1 and K2 byte mismatch. This alarm occurs when the path numbers indicated in the transmitted K1 byte and the received K2 byte are inconsistent and the inconsistency lasts for a time period (160 ms by default).
Attribute
Parameters
None

The MS protection fails. As a result, services are interrupted if a fiber cut or another fault occurs.
Possible Causes
The possible causes of the K1_K2_M alarm are as follows: l l l l The fiber connection is incorrect. The protection group types configured at the two ends of the protection group are inconsistent. The board is faulty. The cross-connect board is faulty.
Procedure
Step 1 View this alarm on the U2000, and determine the ID of the MS where the alarm is reported according to alarm parameters. Step 2 Check whether the fiber connection that this MS travels through is normal, and whether the logical configuration of the fiber is consistent with the physical configuration. After confirming that the fiber connection is correct, check whether the alarm is cleared Step 3 If the alarm persists, check whether the protection group types configured at the two ends of the protection group are consistent. If not, re-configure the protection type and check whether the alarm is cleared. Step 4 If the alarm persists, check the boards configured with the MS at the local and opposite ends are faulty. If yes, replace the faulty board. For details, see the Parts Replacement.
4 Alarm Processing
Step 5 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are faulty. If yes, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.88 K2_M
Description
The K2_M is an alarm indicating K2 byte mismatch. This alarm occurs when the protection group type configured at the opposite end indicated by the fifth bit (counted from the highest bit to the lowest bit) of the K2 byte is inconsistent with that of the local end, and the inconsistency lasts for a time period (2s by default).
Attribute
Parameters
None

The MS protection fails. As a result, services are interrupted if a fiber cut or another fault occurs.
Possible Causes
The possible causes of the K2_M alarm are as follows: l l l The MS configuration is incorrect. The board is faulty. The cross-connect board is faulty.
Procedure
Step 1 Check whether the MS configuration on the local NE is consistent with that on the opposite NE. If not, re-configure the MS and check whether the alarm is cleared. Step 2 If the alarm persists, check whether the boards configured with MSs at the local and opposite ends are faulty. If yes, replace the faulty board and check whether the alarm is cleared
4 Alarm Processing
Step 3 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are faulty. If yes, replace the faulty board and check whether the alarm is cleared ----End
Related Information
None
4.89 L_SYNC
Description
Loss of synchronization alarm. This alarm is generated when loss of synchronization occurs in the physical coding sublayer (PCS) of a receiving port.
Attribute
Alarm Severity Critical Alarm Type Service quality alarm
Parameters
None

When loss of synchronization occurs in the physical coding sublayer (PCS) of a receiving port, the port stops receiving data. therefore, the loss of synchronization alarm affects the quality of service (QoS). In this case, the service is interrupted.
Possible Causes
l l l l l Configuration of working mode, signal type or rate of the equipment at the local station and the opposite station are not consistent. Link failure. The equipment in the opposite station is faulty. The receive optical power of the local board is abnormal. The board at the local station is faulty.
Procedure
Step 1 Check whether the configuration of working mode, signal type or rate of the equipment at the local station and the opposite station are consistent. If they are not consistent, modify the setting to ensure the consistency.
4 Alarm Processing
Step 2 If the alarm persists, check whether the fiber or cable that is used to connect between the equipment at the local station and the opposite station are well connected. If they are not well connected, reconnect or replace the fiber or cable. Step 3 If the alarm persists, check whether the data equipment in the opposite station is faulty. If that is the case, remove the fault of the data equipment in the opposite station. Step 4 If the alarm remains, use the U2000 to check whether the receive optical power of the WDMside interface of the alarm-reporting board is in normal range. For optical power specifications of boards, see the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting. Step 5 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.90 LAN_LOC
Description
Ethernet communication failure. In the case of NE cascading, this alarm is generated when the Ethernet communication between NEs fails.
Attribute
Parameters
None

When the network port is faulty or there is a cut in the network cable, the communication at this network port fails. In this case, the communication between the NE and the U2000 stops.
Possible Causes
l l l l
Issue 02 (2011-10-31)
The network port is required and is enabled on the U2000. However, the network cable is not connected to the network port or is inappropriately connected. The network port is not required but is enabled on the U2000. The network cable is faulty. The board is faulty.
4 Alarm Processing
Procedure
Step 1 Query the alarm informations on the U2000. Check whether the corresponding network port is required according to the alarm parameters, If ... The corresponding network port is not required. Then ... Disable the port on the U2000. For details, see "Disable the Unused Auxiliary Interfaces" in the Commissioning Guide. Check and ensure that the network cable is properly connected to the network port.
The corresponding network port is required.
Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable and re-connect it. Step 3 If the alarm persists, the auxiliary interface board (such as the AUX, EFI, EFI1, and EFI2 board) may be faulty. In this case, replace the faulty board. For detailed operations, see Parts Replacement. ----End
Related Information
None
4.91 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that the port in the aggregation group is invalid. When the GE port is not available, the aggregation fails. Therefore, this alarm occurs.
Attribute
Alarm Severity Minor Alarm Type Process alarm
Parameters
Issue 02 (2011-10-31)
504
4 Alarm Processing
Name
Meaning
Parameters 1 and 2 Indicates the number of the port where the alarm is generated, consisting of two bytes. For example, 0x00 0x01 indicates port 1, 0x00 0x02 indicates port 2, 0x03 indicates port 3, and so on. Parameter 3 Indicates the cause of the invalid port in the aggregate group. For example, 0x01 indicates that the port is in the link down or disabled state. 0x02 indicates that the port is in the half-duplex mode. 0x03 indicates that port fails to receive LACP messages. 0x04 indicates that the port is selflooped.

The port in the aggregation group fails to share the service load. In this case, the port cannot receive or transmit services.
Possible Causes
l l l l The port is in the link down or disabled state. The port is in the half-duplex mode. The port has not received LACP messages. The port is self-looped.
Procedure
Step 1 Check the link and enabling status of all ports on the U2000. Remove link faults, and then set the port to Enable on the U2000. Step 2 On the U2000, check whether the operation mode of the port is set to Half-Duplex. If yes, reset it to Full-Duplex. Step 3 Check whether the corresponding link aggregation group is configured at the opposite station. If yes, check whether the MAC address of the opposite aggregation group that provides links to the local aggregation group is invalid. If yes, re-configure it. Step 4 Check whether the port is configured as self-looped. If yes, cancel the configuration. ----End
Related Information
None
4.92 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that the VCG port in the aggregation group fails. When the VCTRUNK port is not available, the aggregation fails. Therefore, this alarm occurs.
4 Alarm Processing
Attribute
Parameters
Parameters 1 and 2 Indicates the number of the port where the alarm is generated, consisting of two bytes. For example, 0x00 0x01 indicates port 1, 0x00 0x02 indicates port 2, 0x03 indicates port 3, etc. Parameter 3 Indicates the cause of the invalid port in the aggregate group. For example, 0x01 indicates that the port is in the link down or disabled state. 0x02 indicates that the port is in the half-duplex mode. 0x03 indicates that port fails to receive LACP messages. 0x04 indicates that the port is selflooped.

The port in the aggregation group fails to share the service load. In this case, the port cannot receive or transmit services.
Possible Causes
l l l The port is in the link down or disabled state. The port has not received LACP messages. The port is self-looped.
Procedure
Step 1 Check whether the VCG port in the aggregation group fails. If yes, remove VCG port faults. Step 2 Check whether the corresponding link aggregation group is configured at the opposite station. If yes, check whether the MAC address of the opposite aggregation group that provides links to the local aggregation group is invalid. If yes, re-configure it. Step 3 Check whether the port is configured as self-looped. If yes, cancel the configuration. ----End
Related Information
None
4 Alarm Processing
4.93 LASER_HAZARD_WARNING
Description
The laser hazard warning alarm. When a high-power laser is used in the optical transmission system, the system may cause personal injury. In this case, if the IPA function is not configured, this alarm is reported prompting the user to configure the IPA function.
Attribute
Alarm Severity Critical Alarm Type Environment alarm
Parameters
Parameter 1 Indicates the work band. 0x01 indicates the C-Band and 0x02 indicates the LBand.

This alarm does not affect services; however, it might cause personal injury.
Possible Causes
l l The laser power is high and the IPA protection is not configured. The laser power is high; although the IPA function has been configured, it is disabled.
Procedure
Step 1 Check the IPA configuration on the NE. For details, see "Creating IPA" in the Feature Description. Check the IPA configuration for a Raman system, see "Creating IPA for a Raman System" in the Feature Description. Step 2 If the NE is not configured with the IPA function, follow the network plan to create the IPA protection. For details, see "Creating IPA" in the Feature Description. To create IPA protection for a Raman system, see "Creating IPA for a Raman System" in the Feature Description. Step 3 If the NE is configured with the IPA function, enable the IPA function. For details, see "Enabling IPA" in the Feature Description. To enable the IPA function for a Raman system, see " Enabling the IPA in a Raman System" in the Feature Description.
4 Alarm Processing
Step 4 After the IPA function is configured and enabled, the alarm is cleared automatically. If the alarm persists, contact Huawei for help. ----End
Related Information
The system provides the intelligent power adjustment (IPA) function. For details, see "Intelligent Power Adjustment (IPA)" in the Feature Description. The power of the pump light from Raman amplifiers is very high. For details, see "Intelligent Power Adjustment (IPA) of Raman System" in the Feature Description.
4.94 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of the board is shut down.
Attribute
Parameters
None

When the LASER_SHUT alarm is generated, the services are interrupted.
Possible Causes
The user uses the U2000 or Navigator to perform the operation to shut down the laser.
Procedure
Step 1 If the user cancels the setting of laser shutdown, the LASER_SHUT alarm is automatically cleared. ----End
Related Information
None
4 Alarm Processing
4.95 LCS_DAYS_OF_GRACE
Description
License in keepalive period. The LCS_DAYS_OF_GRACE is an alarm indicating the license has expired and is within the keepalive period of 60 days.
Attribute
Parameters
Parameters 1 and 2 l 0x00 0x00 indicate file level alarm. l Other values indicate control-item ID. Parameters 3 and 4 Indicate days. Parameter 5 l 0x00 indicates that the license or control-item expire naturally. l 0x01 indicates that the license has been revoked. l 0x02 indicates ESN mismatching. l 0x03 indicates V/R mismatching. l 0x04 indicates ESN and V/R mismatching. When Parameter 1 and Parameter 2 are of other values, the value of Parameter 5 is 0x00.

When the license has expired but is still within the keepalive period of 60 days, the system functions are not affected, but this alarm is reported every day, reminding the user of updating the license.
Possible Causes
l The license file fails. The system is in the trial state and within the keepalive period of 60 days.
Issue 02 (2011-10-31)
4 Alarm Processing
l l
The license file does not match ESN or V/R version. The system is in trial state and within the keepalive period of 60 days. The license-controlled items exceed the expiry date but is within the keepalive period of 60 days.
Procedure
Step 1 Load a license file to the system. ----End
Related Information
None
4.96 LCS_EXPIRED
Description
License expired. The LCS_EXPIRED is an alarm indicating the license has expired and the keepalive period of 60 days has also elapsed.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameters 1 and 2 Parameter 3 Meaning Indicate days. l 0x01 indicate license having been revoked. l 0x02 indicate ESN mismatching. l 0x03 indicate V/R mismatching. l 0x04 indicate ESN and V/R mismatching.

When the license has expired and the keepalive period of 60 days has also elapsed, only the default functions of the system are available.
4 Alarm Processing
Possible Causes
l l The license of the system has expired and the keepalive period of 60 days has also elapsed. The system license file does not match the ESN or V/R version, and the keepalive period of 60 days has elapsed.
Procedure
Related Information
None
4.97 LCS_FILE_NOT_EXIST
Description
No license file. The LCS_FILE_NOT_EXIST is an alarm indicating the system is under license control but a license file is not loaded onto the system.
Attribute
Parameters
None

If a license file is not installed, only the default functions of the system are available.
Possible Causes
When starting up, the system does not find a license file, which is essential for the system to run.
Procedure
Related Information
None
4 Alarm Processing
4.98 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction. When the sink end of the LCAS module detects anomalies, the LCAS negotiation is unavailable or incorrect and this alarm is generated.
Attribute
Parameters
None

When the LCAS_FOPR alarm is generated, it indicates that the protocol state machine in the receive direction is in confusion. The negotiation may be abnormal.
Possible Causes
The possible causes of the LCAS_FOPR alarm are as follows: l l l l The downstream VCG receives repeated sequence numbers due to incorrect configurations or link bit errors. The LCAS function of the opposite VCG is disabled. The downstream VCG simultaneously receives the FIXED and other LCAS control bytes due to incorrect configurations or link bit errors. The cross-connection is incorrectly bound.
Procedure
Step 1 View the LCAS_FOPR alarm on the U2000 and determine the relevant VCTRUNK. Step 2 Check whether the LCAS protocol is enabled at the opposite end. If not, enable the LCAS protocol at the opposite end. Check whether the alarm is cleared. Step 3 If the alarm persists, check whether the configurations are correct. Especially, check whether the cross-connection is bound correctly. If not, modify the incorrect configurations. Check whether the alarm is cleared. Step 4 If the alarm persists, disable and then enable the LCAS function at both ends. Check whether the alarm is cleared. ----End
4 Alarm Processing
Related Information
None
4.99 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the failure of the LCAS protocol in the transmit direction. When the source end of the LCAS module detects anomalies, the LCAS negotiation is unavailable or incorrect and this alarm is generated.
Attribute
Parameters
None

When the LCAS_FOPT alarm is generated, it indicates that the protocol state machine in the transmit direction is in confusion. The negotiation may be abnormal.
Possible Causes
There is the persistent and unexpected MST due to incorrect configurations or link bit errors. For example, the member that transmits IDLE always receives MST=OK.
Procedure
Step 1 View the LCAS_FOPT alarm on the U2000 and determine the relevant VCTRUNK. Step 2 Check whether the service cross-connection of the VCTRUNK is bound correctly. If not, modify the incorrect configurations. Check whether the alarm is cleared. ----End
Related Information
None
4.100 LCAS_PLCR
4 Alarm Processing
Description
The LCAS_PLCR is an alarm indicating partial unavailability of the bandwidth in the LCAS receive direction. When the LCAS function of the VCTRUNK is enabled, in the receive direction, the number of paths that carry load is less than the number of paths configured and is not zero.
Attribute
Parameters
None

When the LCAS_PLCR alarm is generated, it indicates that the available bandwidth in the receive direction is reduced. The services are not interrupted.
Possible Causes
The possible causes of the LCAS_PLCR alarm are as follows: l l l Bidirectional services are not configured. The number of members in the upstream of the opposite end is less than that in the downstream of the local end. The path communication fails because the cross-connection is incorrect or the physical link is improperly connected.
Procedure
Step 1 Check whether there are other alarms such as AIS, LOP, UNEQ, and LOM. If yes, clear these alarms first. Then, check whether the alarm is cleared. Step 2 Ensure that the physical link is available. Check whether bidirectional services are configured. If not, configure bidirectional services. Step 3 If the alarm persists, check on the U2000 whether the number of downstream timeslots bound with the VCTRUNK at the local end is consistent with that of upstream timeslots bound with the VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number of the timeslots at both ends consistent. Check whether the alarm is cleared. Step 4 Check whether the cross-connection is bound from the transmit direction to the opposite end. If not, re-bind the cross-connection. Then, check whether the alarm is cleared. Step 5 If the alarm persists, the wait-to-restore (WTR) time may be excessively long and thus the members are still not restored. Then, check the WTR time. Wait for a period, and then check whether the alarm is cleared.
4 Alarm Processing
Step 6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check whether the alarm is cleared. Step 7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then, check whether the alarm is cleared. Step 8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after cold reset of the board. ----End
Related Information
None
4.101 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating partial loss of unavailability of the bandwidth in the LCAS transmit direction. When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the number of paths that carry load is less than the number of paths configured and is not zero.
Attribute
Parameters
None

When the LCAS_PLCT alarm is generated, it indicates that the available bandwidth in the transmit direction is reduced. The services will lose packets when the actual service traffic is larger than the available bandwidth in the transmit direction.
Possible Causes
The possible causes of the LCAS_PLCT alarm are as follows:
4 Alarm Processing
l l l
Bidirectional services are not configured. The number of members in the downstream of the opposite end is less than that in the upstream of the local end. The path communication fails because the cross-connection is incorrect or the physical link is improperly connected.
Procedure
Step 1 View the LCAS_PLCT alarm on the U2000 and determine the relevant VCTRUNK. Step 2 Check whether the LCAS_PLCR alarm is present at the opposite station. If yes, clear the LCAS_PLCR alarm first. Then, check whether the alarm is cleared. Step 3 If the alarm persists, check whether bidirectional services are configured. If not, configure bidirectional services. Then, check whether the alarm is cleared. Step 4 If the alarm persists, check on the U2000 whether the number of upstream timeslots bound with the VCTRUNK at the local end is consistent with that of downstream timeslots bound with the VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number of the timeslots at both ends consistent. Check whether the alarm is cleared. Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the opposite end. Re-bind the cross-connection. The alarm is automatically cleared. Step 6 If the alarm persists, the wait-to-restore (WTR) time may be excessively long and thus the members are still not restored. Check the WTR time. Wait for a period, and then check whether the alarm is cleared. Step 7 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check whether the alarm is cleared. Step 8 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then, check whether the alarm is cleared. Step 9 If the alarm persists, perform cold reset on the board.
CAUTION
Related Information
None
4.102 LCAS_TLCR
4 Alarm Processing
Description
The LCAS_TLCR is an alarm indicating the total loss of bandwidth in the LCAS receive direction. When the LCAS function of the VCTRUNK is enabled, in the receive direction, the number of paths that carry load is zero, whereas the number of paths configured is not zero.
Attribute
Parameters
None

When the LCAS_TLCR alarm is generated, it indicates that the available bandwidth in the receive direction is reduced to zero. The services in the receive direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCR alarm are as follows: l l l Bidirectional services are not configured. The upstream of the opposite end is not bound with members. The path communication fails because the cross-connection is incorrect or other alarms are present.
Procedure
Step 1 View the LCAS_TLCR alarm on the U2000 and determine the relevant VCTRUNK. Step 2 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear these alarms first. Then, check whether the alarm is cleared. Step 3 Check whether bidirectional services are configured. If not, configure bidirectional services. Then, check whether the alarm is cleared. Step 4 If the alarm persists, check whether the upstream of the opposite end is bound with timeslots. If not, bind the timeslots in the corresponding direction. Then, check whether the alarm is cleared. Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the local end. Re-bind the cross-connection. The alarm is automatically cleared. Step 6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check whether the alarm is cleared. Step 7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then, check whether the alarm is cleared. Step 8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
4 Alarm Processing
CAUTION
Related Information
None
4.103 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating total loss of bandwidth in the LCAS transmit direction. When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the number of paths that carry load is zero, whereas the number of paths configured is not zero.
Attribute
Parameters
None

When the LCAS_TLCT alarm is generated, it indicates that the available bandwidth in the transmit direction is reduced to zero. The services in the transmit direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCT alarm are as follows: l l The downstream of the opposite end is not bound with members. The path communication fails because the cross-connection is correct or other alarms are present.
Procedure
Step 1 View the LCAS_TLCT alarm on the U2000 and determine the relevant VCTRUNK. Step 2 Check whether the LCAS_TLCR alarm is present at the opposite station. If yes, clear the LCAS_TLCR alarm first. Then, check whether the alarm is cleared.
4 Alarm Processing
Step 3 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear these alarms first. Then, check whether the alarm is cleared. Step 4 If the alarm persists, check whether the downstream of the opposite end is bound with timeslots. If not, bind the timeslots in the corresponding direction. Then, check whether the alarm is cleared. Step 5 If the alarm persists, check whether the cross-connection is correctly bound from the transmit direction to the opposite end. If not, re-bind the cross-connection. Then, check whether the alarm is cleared. Step 6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check whether the alarm is cleared. Step 7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then, check whether the alarm is cleared. Step 8 If the alarm persists, perform cold reset on the board.
CAUTION
Related Information
None
4.104 LOCAL_FAULT
Description
Local fault alarm.
Attribute
Parameters
None

The 10GE services in the flow control mode are configured on the client side of the board (TN11LSX). If the board receives the LOCAL_FAULT alarm, the received services may be interrupted.
4 Alarm Processing
Possible Causes
l l l The input fiber on the client side is transiently cut. The board receives various bit errors. The input optical power on the client side is abnormal.
Procedure
Step 1 Check whether the attenuation of the fiber between the input equipment and the interface on the client side of the board is overlarge, and whether the fiber is aged or loose. If that is the case, clean the fiber connector or replace the fiber. For details, see the Supporting Tasks. Step 2 Check whether the output optical power of the input equipment is within the normal range. If the optical power is abnormal, remove the fault of the input equipment. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.105 LOCK_CUR_FAIL
Description
The LOCK_CUR_FAIL is an alarm indicating that the pump drive currently unlocked. The alarm occurs when the working current is abnormal. Reporting side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the number of pump laser.
Issue 02 (2011-10-31)
520
4 Alarm Processing

The locking of the output optical power of the board fails, which influences the services on the entire optical line.
Possible Causes
The board is faulty.
Procedure
Related Information
None
4.106 LOCKPOW_MIS
Description
The LOCKPOW_MIS is an alarm indicating mismatch of locked pump optical power. When the locked pump optical power falls beyond the range of the locked pump optical power, the alarm is reported.
Attribute
Parameters
None

Possible Causes
Cause 1: As for the locked pump optical power of the Raman board, a value that falls beyond the range of the locked pump optical power is set.
4 Alarm Processing
Procedure
l Cause 1: A value that falls beyond the range of the locked pump optical power is set. 1. ----End Query the locked pump optical power of the corresponding optical interface channel and reconfigure a valid value on the U2000.
Related Information
None
4.107 LP_RDI_VC3
Description
The LP_RDI_VC3 is a remote defect indication in the VC-3 lower order path. If a board has detected that bit 5 of the G1 byte in the VC-3 lower order path is 1, the LP_RDI_VC3 alarm is reported.
Attribute
Parameters
None

When the LP_RDI_VC3 alarm is generated, the services at the local station are not affected. This alarm just indicates that the services at the opposite end are interrupted.
Possible Causes
The LP_RDI_VC3 alarm is an accompanying alarm. When the relevant path of a tributary board at the opposite station reports the TU_AIS_VC3 or TU_LOP_VC3 alarm, it returns the LP_RDI_VC3 alarm to the local station, indicating that the TU_AIS_VC3 or TU_LOP_VC3 alarm is received at the opposite station.
Procedure
Step 1 After you clear the TU_AIS_VC3 or TU_LOP_VC3 alarm reported from the relevant path of a tributary board at the opposite station, the LP_RDI_VC3 alarm is automatically cleared. ----End
4 Alarm Processing
Related Information
None
4.108 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating a signal label mismatch in the VC-3 lower order path. If a board has detected that the signal label mismatch event occurs in the C2 byte, the LP_SLM_VC3 alarm is reported.
Attribute
Parameters
None

The system is not affected.
Possible Causes
The possible causes of the LP_SLM_VC3 alarm are as follows: l l The type of the received signals does not match that of the signals to be received. That is, the signal label byte C2 in the lower order path is inconsistent with the received C2 byte. The service type is incorrectly configured.
Procedure
Step 1 View the LP_SLM_VC3 alarm on the U2000, and then determine the path number. Step 2 Check whether the signal label byte in the lower order path of the tributary board at the opposite station is consistent with that in the lower order path of the line board at the local station. If not, modify it, and then check whether the LP_SLM_VC3 alarm is cleared. Step 3 If the alarm persists, check whether the service configuration of the path is correct. After modifying the incorrect configuration, check whether the LP_SLM_VC3 alarm is cleared. Step 4 If the alarm persists, replace the line board at the local station. Step 5 If the alarm persists, replace the tributary board at the opposite station. ----End
4 Alarm Processing
Related Information
None
4.109 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that no payload is equipped in the VC-3 lower order path. If a board has detected that the signal label in the C2 byte is 0, the LP_UNEQ_VC3 alarm is reported.
Attribute
Parameters
None

The LP_UNEQ_VC3 alarm indicates that no path services are loaded. If the service configuration is incorrect, and if the services on the PDH side are not accessed, the services may be interrupted.
Possible Causes
The possible causes of the LP_UNEQ_VC3 alarm are as follows: l l The service type is incorrectly configured. The services on the PDH side are not accessed.
Procedure
Step 1 View the LP_UNEQ_VC3 alarm on the U2000, and then determine the path number. Step 2 Check whether the service type configuration is correct. After modifying the incorrect configuration and making sure that the services are correctly accessed on the PDH side, check whether the LP_UNEQ_VC3 alarm is cleared. Step 3 If the alarm persists, check whether the property configuration of the relevant tributary board is correct. After you modify the incorrect configuration, the LP_UNEQ_VC3 alarm is automatically cleared. ----End
4 Alarm Processing
Related Information
None
4.110 LPT_RFI
Description
The LPT_RFI is a remote failure indication alarm of link pass through (LPT). This alarm occurs when the link pass through detects the failure of the remote port or the LPT service network.
Attribute
Parameters
None

During the data transmission, when the LPT detects the failure of the remote port or the service network, the link is unavailable and the services are interrupted. Moreover, the link backup is triggered.
Possible Causes
The possible causes of the LPT_RFI alarm are as follows: l l The remote port fails. For example, there is the LINK_ERR alarm, or the remote port is disabled. The LPT service network is faulty, including the following cases: There is a fiber cut. There are bit error threshold-crossing alarms such as B3_EXC. There are alarms such as VCAT_LOA, VCAT_LOM_VC3, VCAT_LOM_VC4, and LP_UNEQ_VC3.
Procedure
Step 1 View the LPT_RFI alarm on the U2000 to determine the number of the port on the board that reports the alarm according to Parameter 1. Step 2 Based on the confirmed port number, check whether the opposite port is enabled. If yes, check whether the LPT_RFI alarm is cleared. Step 3 If the alarm persists, check whether there is the LINK_ERR alarm. If yes, after the LINK_ERR alarm is cleared, check whether the LPT_RFI alarm is cleared.
4 Alarm Processing
Step 4 If the LPT_RFI alarm still persists, check whether the service network fails. l If a fiber cut occurs, replace the fiber. l If the bit error threshold-crossing alarms such as BIP_EXC and B3_EXC are detected, first clear these alarms and then check whether the LPT_RFI alarm is cleared. l Check whether there are alarms such as VCAT_LOA, VCATA_LOM_VC3, VCAT_LOM_VC4, and LP_UNEQ_VC3. If yes, first clear these alarms and then check whether the LPT_RFI alarm is cleared. ----End
Related Information
None
4.111 LSR_COOL_ALM
Description
The LSR_COOL_ALM is an alarm indicating that the cooling current of the laser crosses the threshold. The alarm is generated when the cooling current of the laser on the WDM side exceeds the threshold. Reported from the WDM side or client side: WDM side
Attribute
Parameters
None

When the cooling current of the laser exceeds the threshold, the optical module of the board works abnormally. As a result, services cannot be transmitted or received normally.
Possible Causes
The possible causes of the LSR_COOL_ALM alarm are as follows: l l The ambient temperature is excessively high. The laser is faulty.
Issue 02 (2011-10-31)
526
4 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is excessively high. If yes, decrease it to a proper value for the equipment to work well, and then check whether the LSR_COOL_ALM alarm is cleared. Step 2 If the alarm persists, the laser may be faulty. Replace the board that generates the alarm. For details, see the Parts Replacement. ----End
Related Information
None
4.112 LSR_FORCE_OPEN
Description
The LSR_FORCE_OPEN is an alarm indicating that the laser is forced to be open.
Attribute
Parameters
None

The inconsistent operations may occur.
Possible Causes
The optical interface is set to Disabled but the status of the laser is On.
NOTE
For L4G board, if the laser is On when the port on the client side is set to be disabled, the alarm is generated.
Procedure
Step 1 Query whether the laser reporting the alarm needs to be used. If that is the case, set the status of the laser to On on the U2000. If not, shut down the laser on the U2000. ----End
Related Information
None
4 Alarm Processing
4.113 LSR_INVALID
Description
The LSR_INVALID is an alarm indicating an invalid optical module. It is generated when the optical module cannot pass an authentication.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the reason why the optical is invalid. 0x01 indicates that the optical module has no license. 0x02 indicates that the license verification of the optical module is incorrect.

The optical interface of the board cannot receive and transmit services. Services are interrupted.
Possible Causes
l l The optical module has no license. A fault occurs during verifying the license of the optical module.
Procedure
Step 1 Replace the optical module with another one with a correct license, and then re-verify the license. After successful verification, the alarm is cleared. ----End
Related Information
None
4 Alarm Processing
4.114 LTI
Description
The LTI is an alarm indicating the loss of synchronization source. This alarm is generated when there are clock sources other than internal clock sources listed in the priority table but the board operates in the holdover or free-run mode.
Attribute
Parameters
Parameter 1 Indicates which synchronization sources are lost. l 0x01: All synchronization sources for the system clock are lost. l 0x02: All synchronization sources for the first 2M phase-locked source are lost. l 0x03: All synchronization sources for the second 2M phase-locked source are lost.

When the LTI alarm is generated, the NE clock is in an abnormal state. If the NE clock remains in this abnormal state for a long time, the bit error rate and the pointer justifications may increase due to the decreased clock quality.
Possible Causes
The possible causes of the LTI alarm are as follows: l l l l
Issue 02 (2011-10-31)
Cause 1: There is a fiber cut or a cable cut. Cause 2: There is no input from the external clock source. Cause 3: The synchronization source is set as non-revertive or is locked. Cause 4: The board is faulty.
4 Alarm Processing
Procedure
l l On the U2000, view the clock sources traced by the NE that reports the LTI alarm. The clock sources include external clock sources, line clock sources, and tributary clock sources. Cause 1: There is a fiber cut or a cable cut. Cause 4: The board is faulty. 1. On the U2000, check whether the R_LOS, R_LOC, or R_LOF alarm occurs on the relevant line board or tributary board. If yes, take priority to clear the alarm, and then check whether the LTI alarm is cleared. If the alarm persists, perform cold reset on the relevant line board or tributary board. After successful cold reset, check whether the LTI alarm is cleared. For details, see Performing Cold Reset on a Board in the Supporting Tasks. If the alarm persists, replace the relevant line board or tributary board, and then check whether the LTI alarm is cleared. For details, see Parts Replacement. If the alarm persists, perform cold reset on the clock board, and then check whether the alarm is cleared. For details, see Performing Cold Reset on a Board in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see the Parts Replacement. Make sure that the external clock equipment properly transmits signals. Replace the external clock equipment with a normal one, and then check whether the LTI alarm is cleared. If the alarm persists, check whether the input and output modes of the external clock source are consistent. After the input and output of the external clock source are set to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared. For details, see Configuring Physical Clock in the Feature Description. If the alarm persists, check whether the clock input cable is correctly connected. After ensuring the correct connection of the clock input cable, check whether the alarm is cleared. If the alarm persists, perform cold reset on the clock board, and then check whether the alarm is cleared. For details, see Performing Cold Reset on a Board in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see the Parts Replacement. On the U2000, check whether the synchronization source is set as non-revertive. If yes, set the source as revertive. Then, check whether the alarm is cleared. On the U2000, check whether the synchronization source is set as locked. If yes, set the source as unlocked. Then, check whether the alarm is cleared.
2.
3. 4.
5. l 1.
Cause 2: There is no input from the external clock source. Cause 4: The board is faulty.
2.
3.
4.
5. l 1. 2. ----End
Cause 3: The synchronization source is set as non-revertive or locked.
Related Information
Issue 02 (2011-10-31)
530
4 Alarm Processing
4.115 MAINBD_SUBBD_MISMATCH
Description
This alarm is generated when the board where services are processed mismatches the board where services are output in a PID group.
Attribute
Parameters
None

The board where services are output does not support the board where services are processed, and therefore the board where services are processed is unavailable.
Possible Causes
The board where services are output does not support the board where services are processed. However, the board where services are processed is housed in the corresponding slot.
Procedure
Step 1 Determine whether the board where the services are processed is required. Step 2 If the board where the services are processed is required, replace the board where services are output with a board that supports the board where services are processed. Step 3 If the board where services are processed is not required, remove it from the corresponding slot. ----End
Related Information
For OptiX OSN 6800, see "PID" in the Feature Description. For OptiX OSN 8800, see "PID" in the Feature Description.
Issue 02 (2011-10-31)
531
4 Alarm Processing
4.116 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that the module communication is abnormal. The alarm is generated when the communication of the CPU and other internal modules of the board is abnormal. Reported from the WDM side or client side: NA
Attribute
Parameters
None

Because the communication between the CPU and the optical module is abnormal, the optical module cannot be managed by the U2000 and the information about the optical module cannot be queried.
Possible Causes
l l l The board is in poor contact with the connector of the optical module. The software processing of the related modules of the board is faulty. The board hardware is faulty.
Procedure
Step 1 Check the connection between the board and optical module, and re-connect the board and optical module. Step 2 Perform cold reset on the faulty board by using the U2000 or remove the faulty board and insert it again. For details, see the Supporting Tasks. Step 3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4 Alarm Processing
4.117 MODULE_ADJUST_FAIL
Description
The MODULE_ADJUST_FAIL is an alarm indicating that adjustment of the optical module fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the type of the component in which the alarm is generated. For example, 0x01 indicates that the VOA adjustment fails. 0x02 indicates that the optical switch adjustment fails.

The adjustment of the VOA or optical switch of the optical module fails, which leads to the failure of issuing a command.
Possible Causes
l l The temperature of the optical module is excessively high. The optical module of the board is faulty.
Procedure
Step 1 Check whether the board temperature exceeds the threshold, and whether the TEM_HA and TEMP_OVER alarm exist. If that is the case, handle the alarms according to the corresponding handling procedures. Step 2 Deliver the configuration again. If the alarm persists, the adjusted range of the optical module exceeds the threshold. Perform warm reset on the board. For details, see the Supporting Tasks. Step 3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts Replacement. ----End
4 Alarm Processing
Related Information
None
4.118 MODULE_COOLCUR_OVER
Description
The MODULE_COOLCUR_OVER is an alarm indicating that the module cooling current exceeds the threshold. The alarm occurs when the cooling current of the module is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates that the upper threshold is exceeded and 0x02 indicates that the lower threshold is exceeded.

The working performance and the reliability of the module are affected. Generally the QoS is not affected. However, the QoS is affected if the alarm exists for a long time. The alarm should be handled in time.
Possible Causes
l l The temperature of the optical module is excessively high. The board hardware is faulty.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of specific boards, see the Product Description. If the ambient temperature is excessively high, handle the alarm according to the handling procedure of the TEMP_OVER alarm.
4 Alarm Processing
Step 2 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.119 MODULE_TEMP_OVER
Description
The MODULE_TEMP_OVER is an alarm indicating that the module temperature exceeds the threshold. The alarm is generated when the temperature of the module is higher than the upper threshold or lower than the lower threshold. Reported from the WDM side or client side: WDM side
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the threshold crossing type. 0x01 indicates that the upper threshold is exceeded and 0x02 indicates that the lower threshold is exceeded.

Because the temperature of the optical module exceeds the threshold, the working performance and reliability of the optical module are affected. As a result, services are affected. The alarm should be handled in time.
Possible Causes
l l
Issue 02 (2011-10-31)
The ambient temperature of the board is excessively high or excessively low. The board hardware is faulty.
4 Alarm Processing
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of specific boards, see the Product Description. If the ambient temperature is excessively high or excessively low, handle the alarm according to the handling procedure of the TEMP_OVER alarm. Step 2 If the alarm persists, the board at the local station may be faulty. Perform a cold reset on the faulty board through the U2000 Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.120 MODULEFILE_UPDATE_FAIL
Description
The MODULEFILE_UPDATE_FAIL is an alarm indicating that updating the microprogram and laser parameter table fails. The alarm occurs when the in-service upgrade of the microprogram of the optical module and the parameter table on the U2000 fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the type of the software that generates the alarm. 0x01 indicates the microprogram and 0x02 denotes the parameter table.

l l
Issue 02 (2011-10-31)
The upgrade of the microprogram of the optical module fails. The new microprogram of the optical module is unavailable and the old one is still used. The upgrade of the parameter table of the laser fails.
4 Alarm Processing
Possible Causes
The upgrade of the microprogram of the optical module and the parameter table of the laser fails.
Procedure
Step 1 Check whether the upgraded microprogram of the optical module and the parameter table of the laser are correct. Step 2 Upgrade the microprogram of the optical module and the parameter table of the laser again. Step 3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts Replacement. ----End
Related Information
None
4.121 MS_CROSSTR
Description
Multiplex section performance exceeds the threshold. The alarm is generated when the performance module reports the threshold crossing of the performance events in the multiplex section.
Attribute
Parameters
None

The line has bit errors, which decreases the QoS.
Possible Causes
l l l l
Issue 02 (2011-10-31)
The laser of the board in the opposite station is degraded. The input optical power of the board at the local station is too high or too low. The clock in the opposite station is degraded. The fiber is degraded.
4 Alarm Processing
Procedure
Step 1 Check whether the fiber is aging or has excessive attenuation. If that is the case, remove the fault of the fiber. Step 2 Query whether the board has the B1_EXC, B2_EXC, B1_SD or B2_SD alarms by using the U2000. If that is the case, clear the alarms. Step 3 Check whether the input optical power of the board at the local station is within the normal range by using the U2000. For the optical power specifications of the specific board, see the Product Description. l l If the optical power displayed on the U2000 is normal, the board might be faulty. Replace the faulty board. For details, see the Parts Replacement. If the optical power displayed on the U2000 is abnormal, adjust the input optical power to be within the normal range.
Step 4 If the alarm persists, remove the fault of the board in the opposite station. ----End
Related Information
None
4.122 MS_REI
Description
The MS_REI is an alarm that indicates that bit errors occur at the remote end of the multiplex section (MS). When the receive side of the local optical station receives the M1 byte, which indicates that the number of block bit errors detected by BIP-Nx24 (B2) at the opposite station, the MS_REI alarm is reported.
Attribute
Parameters
None

When the MS_REI alarm is generated, the number of B2 bit errors received at the opposite station is beyond the specified range. The services at the local station are not affected, but the service quality at the opposite station is degraded.
4 Alarm Processing
Possible Causes
The number of B2 bit errors received at the opposite station is beyond the specified range.
Procedure
Step 1 After you clear the B2_EXC or B2_SD alarm that occurs at the opposite station, the MS_REI alarm is automatically cleared. ----End
Related Information
None
4.123 MS_SNCP_PS
Description
The MS_SNCP_PS is an alarm indicating the MS SNCP protection switching. This alarm occurs when the MS SNCP protection group actuates switching in which the current channel switches to the protection channel from the working channel. Reporting side: NA
Attribute
Parameters
None

When the MS SNCP protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the MS SNCP protection group might have faulty services that need to be restored.
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the MS SNCP protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the MS SNCP protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
Issue 02 (2011-10-31)
4 Alarm Processing
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced switching or manual switching, check whether the external switching operation is necessary, 1. 2. If the external switching operation is necessary, ignore the alarm. If the external switching operation is unnecessary, issue an external command to switch the current channel to the working channel, thus clearing the alarm.
Step 2 If the alarm is generated due to the automatic switching of the protection group, 1. Query whether the related boards for configuring the protection group have alarms relevant to the services, such as B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC, REM_SF, and REM_SD. If yes, handle the alarms by referring to the corresponding alarm handling procedures. If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
2.
----End
Related Information
For details, see "MS SNCP Protection" in the Feature Description.
4.124 MS_SNCP_STA_INDI
Description
The MS_SNCP_STA_INDI is an alarm indicating the MS SNCP protection switching. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command. Reporting side: NA
Attribute
Parameters
4 Alarm Processing
Description Indicate the switch request status. For example: l 0x0F: Lockout l 0x0E: Forced Switch l 0x0C: SF Switch l 0x09: SD Switch l 0x07: Manual Switch l 0x05: WTR

l l When switching is performed in the MS SNCP group, the services may be transiently interrupted. When the alarm is reported, the working or protection channel of the MS SNCP group may have faulty services that need to be restored.
Possible Causes
l l l The user issues an external switching command such as forced switching, manual switching, or locked switching. The services of the working or protection channel of the MS SNCP group are faulty. The switching is set to WTR State. After the WTR time, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching or locked switching, check whether the external switching is necessary, 1. 2. If the external switching is necessary, ignore the alarm. If the external switching is unnecessary, issue a switching clearing command to clear the external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection group, do as follows: 1. Query whether the related boards for configuring the protection group have alarms such as B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC, REM_SF, and REM_SD. If that is the case, handle the alarms according to the corresponding handling procedure of the alarms to restore the services of the working or protection channel. If the alarm persists, check whether the attribute of the protection group is Revertive. If that is the case, the services in the working channel automatically switch to the working channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the alarm is cleared.
2.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in the WTR state. This alarm requires no handling. After the WTR time, the alarm is cleared. ----End
4 Alarm Processing
Related Information
For details, see "MS SNCP Protection" in the Feature Description.
4.125 MS_APS_INDI_EX
Description
The MS_APS_INDI_EX is an extended indication alarm of the MSP switching state. The alarm occurs when the multiplex section switching causes the switching of services.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the type of the MSP group in which protection switching occurs: l 0x01: linear MSP group l 0x02: ring MSP group Parameter 2, Parameter 3 Indicates the MSP group ID. l Linear MSP: The parameter value ranges from 0x01 to 0xFF (1-255). l Ring MSP: The parameter value ranges from 0x01 to 0x90 (1-144). Parameter 4 Indicates the slot ID of the board where the protection switching occurs. Indicates the number of the optical interface where the protection switching occurs.
Parameter 5
Issue 02 (2011-10-31)
542
4 Alarm Processing

If a fiber cut or another fault occurs after the MS_APS_INDI_EX alarm is generated, the services are interrupted.
Possible Causes
The possible causes of the MS_APS_INDI_EX alarm are as follows: l l l An external switching command is issued. There is a fiber cut. The board is faulty.
Procedure
Step 1 View the MS_APS_INDI_EX alarm on the U2000. According to the alarm parameters, determine the slot ID and optical interface number related to the board where the protection switching occurs. Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked switching. If yes, clear the switching, and then the alarm is automatically cleared. Step 3 If the MSP is in the automatic switching state, do as follows: 1. 2. 3. Make sure that the fibers connected to the service board configured with the MSP are not cut. Fix the broken fibers and then check whether the alarm is cleared. Make sure that the service board configured with the MSP is not faulty. Replace the relevant service board and then check whether the alarm is cleared. Make sure that the cross-connect board configured with the MSP is not faulty. Replace the relevant cross-connect board and then check whether the alarm is cleared.
----End
Related Information
After the services are switched in the 1+1 single-ended non-revertive linear multiplex section, the services are not automatically switched back to the working channel if the optical channel is recovered, and the MS_APS_INDI_EX alarm persists. In this case, the services need to be manually switched from the protection channel to the working channel. The MS_APS_INDI_EX alarm can be cleared only after successful switching.
4.126 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that there is more than one RPL OWNER node on the ring.
Issue 02 (2011-10-31)
543
4 Alarm Processing
Attribute
Parameters
None

There is no connection between all the nodes on the ring. If certain services are configured, the services may be interrupted.
Possible Causes
The ERPS protocol requires that the configuration of every node on a ring should be managed and one RPL OWNER should exist on each ring. Therefore, the alarm is generated when more than one RPL OWNER node is configured in a ring.
Procedure
Step 1 Check whether the node ID in all the received NR and RB packets is consistent with the ID of the local node. If yes, proceed with the next step. Step 2 Start the timer whose time is three times of the transmitting period (15s) of the packets. The aging of the timer indicates the end of the alarm. ----End
Related Information
None
4.127 NEBD_XC_DIF
Description
The NEBD_XC_DIF is an alarm indicating that the cross-connect matrix data of the NE and board is different. For the board supporting service cross-connection, the alarm occurs when the cross-connection data stored on the SCC is not consistent with that stored on the board.
Attribute
Issue 02 (2011-10-31)
544
4 Alarm Processing
Parameters
Parameter 1 and Parameters 2 Indicates the slot ID. Parameters 3 Indicates the cross-connect type. For example: 0x3 indicates inconsistent space division cross-connections.

Services are interrupted during service grooming or perform warm reset on the board.
Possible Causes
l l Cause 1: The cross-connection data of the board is incorrect. Cause 2: The cross-connection data stored on the board is different from that on the SCC board.
Procedure
l l Query the alarm on the U2000. Record the slot ID of the board that reports the alarm. Cause 1: The cross-connection data of the board is incorrect. 1. l Re-configure the cross-connection data on the U2000. For details, refer to the Configuration Guide.
Cause 2: The cross-connection data stored on the board is different from that on the SCC board. 1. 2. If the alarm persists, perform a warm reset on the board related to service crossconnections on the U2000. If the alarm persists, perform warm reset on the SCC on the U2000. For details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
Issue 02 (2011-10-31)
545
4 Alarm Processing
4.128 NESF_LOST
Description
The NESF_LOST is an alarm indicating absence of NE software. The alarm occurs when the NE software on the SCC board does not exist.
Attribute
Parameters
None

If the two sets of NE software do not exist, and thus the board cannot work normally and the U2000 cannot monitor the NE after the reset or power-off restart of the SCC.
Possible Causes
The NE software is not reloaded after the NE software of the SCC board is erased.
Procedure
Step 1 Reload the NE software of the SCC according to the Version Upgrade Guide. Step 2 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.129 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in installation state and is not configured. The alarm occurs when the NE is in the initial installation state.
4 Alarm Processing
Attribute
Parameters
None

l l The U2000 cannot query all configuration information about the NE. If the alarm is generated by the NE that is in the normal running state, the data of the U2000 is initialized. You need to deliver the correct configuration in time.
Possible Causes
l l The NE is in the initial installation state. The normal configuration is not delivered to the NE after the NE is initialized.
Procedure
Step 1 Deliver the configuration information to the board by using the U2000. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.130 NO_BD_PARA
Description
The NO_BD_PARR is an alarm indicating absence of the board parameter table. The alarm occurs when the board does not have the parameter table. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None
4 Alarm Processing

The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l l l The correct parameter table is not loaded before delivery. The incorrect parameter table file is loaded on site, which overlaps the original file. The parameter table file is abnormally lost in the running process.
Procedure
Related Information
None
4.131 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating absence of board software. The alarm occurs when the board does not have the necessary files, such as loading software and logic software. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the fault type. For example, 0x01 indicates that the file is lost and 0x02 indicates that the file verification fails.
Issue 02 (2011-10-31)
548
4 Alarm Processing
Parameter
Description
Parameters 2 and 3 Indicates the ID of the lost file. For example, l 0x00 0x01 indicates that the software of the working board is lost. l 0x00 0x02 indicates that the software of the protection board is lost. l 0x00 0x03 indicates that the active FPGA file is lost. l 0x00 0x04 indicates that the standby FPGA file is lost. l 0x00 0x05 indicates that the active ini file is lost. l 0x00 0x06 indicates that the standby ini file is lost. l 0x00 0x07 indicates that the active large logic file is lost. l 0x00 0x08 indicates that the standby large logic file is lost. l 0x00 0x0b indicates that the oa.cfg file is lost. l 0x00 0x0d indicates that the oxudsp.par file is lost.

The alarm affects the system as follows: l l If the board that reports the alarm is not reset, the services and functions of the board are not affected. If the board that reports the alarm is reset, the board may fail to start.
Possible Causes
l l l Parts of the software are not loaded to the board. The software on the board is abnormally lost in the running process. The internal detection of the board is abnormal.
Procedure
Step 1 Reload the corresponding software through the U2000. Step 2 Perform warm reset on the faulty board through the U2000. For details, see the Supporting Tasks. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
Issue 02 (2011-10-31)
549
4 Alarm Processing
4.132 NO_ELABEL
Description
The NO_ELABEL is an alarm indicating that the electronic label is unloaded. The alarm is generated when the electronic label of board is lost or not loaded.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the carrier type of the electronic label. For Example, 0x01 indicates the mother board, 0x02 indicates the sub-board and 0x03 indicates the optical module.
Parameters 2 and 3 Indicates the carrier ID.

None
Possible Causes
The electronic label is unloaded or lost.
Procedure
Step 1 Replace the board. For details, see the Parts Replacement. ----End
Related Information
None
4 Alarm Processing
4.133 NODEID_MM
Description
The NODEID_MM is an alarm indicating a mismatch of the MSP node ID. This alarm is generated when the configured ID of an MSP node on the MS ring mismatches the actual node ID.
Attribute
Parameters
Parameter 1 and Parameter 2 Indicates the ID of the MSP group in which the NODEID_MM alarm is generated.

When the NODEID_MM alarm is generated, the MSP switching fails. If the squelching is enabled, the squelching function fails.
Possible Causes
The east and west node IDs configured for each node on the MSP ring do not match.
Procedure
Step 1 View the NODEID_MM alarm on the U2000, and then determine the relevant MSP group ID. Step 2 Check whether the configuration of the MSP data meets the following requirements. If not, reconfigure the MSP according to the following requirements: l The node IDs configured for any two NEs are not repeated. l If node A is in the west of its adjacent node B, the local node ID of node A must be the same as the west node ID of node B, and the local node ID of node B must be the same as the east node ID of node A. Step 3 Restart the MSP protocol, and the alarm is cleared automatically. ----End
4 Alarm Processing
Related Information
None
4.134 NTP_SYNC_FAIL
Description
NTP synchronization failure. This alarm indicates that the NE is in the unsync state. The alarm is cleared when the NTP turns into the sync state.
Attribute
Parameters
None

The NTP synchronization failure leads to unsynchronous NE time. As a result, the time of NE performance events, alarms, and operation records is incorrect.
Possible Causes
l l l The NTP server is not configured correctly. The NE fails to connect to the NTP server or the connection is interrupted. The NTP server stops unexpectedly.
Procedure
Step 1 Check whether the NTP server is configured correctly. Step 2 Check whether the DCN is normal. Step 3 Check whether the NTP server works properly. ----End
Related Information
None
Issue 02 (2011-10-31)
552
4 Alarm Processing
4.135 NULL_SEND
Description
The NULL_SEND is an alarm indicating that the NULL signals (the payload is all "0"s) are sent out. When the NULL mapping status of the board is enabled, the NULL_SEND alarm is generated, prompting the users that the NULL signals are being sent out.
Attribute
Parameters
None

When this alarm is generated, it indicates that the board that reports the alarm is sending out the NULL signals and the opposite station receives the NULL signals. Hence, services are interrupted.
Possible Causes
The NULL Mapping Status parameter of the board is set to Enabled.
Procedure
Step 1 Check the NULL mapping status of the board that reports the alarm. If the NULL mapping status is enabled, change the value from Enabled to Disabled.
NOTE
If the NULL mapping status needs to be enabled in the actual situation, suppress the alarm and then disable the NULL mapping status. After that, configure the NULL_SEND alarm to be monitored.
----End
Related Information
None
Issue 02 (2011-10-31)
553
4 Alarm Processing
4.136 OCH_FDI
Description
The OCH_FDI is an alarm indicating a forward defect at the OCh layer. When the OCH_FDIP and OCH_FDI-O alarms coexist, this alarm is generated. At the same time, the OCH_FDI-P and OCH_FDI-O alarms are suppressed. Reported from the WDM side or client side: WDM side
Attribute
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise the services may be interrupted.
Possible Causes
The OCH_FDI-P and OCH_FDI-O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-O, or OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-O, or OMS_LOS-P alarm by following proper handling procedures. ----End
Related Information
None
4.137 OCH_FDI-O
Description
The OCH_FDI-O is an alarm indicating a forward defect (overhead) at the OCh layer. The OCH_FDI-O signal is inserted to the downstream station when the board at the OTS layer detects
4 Alarm Processing
the OTS_LOS-O signal and the alarm is generated when the downstream station receives the signal.
Attribute
Parameters
None

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

If the logical fiber connection is incorrect, there is no impact on services. Otherwise the services are interrupted.
Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The OCh layer receives the FDI-O overhead signal from the OCh layer, when the OMS layer loses payload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm by following proper handling procedures. ----End
Related Information
None
4.139 OCH_LOS-P
Description
The OCH_LOS-P is an alarm indicating loss of signal (payload) at the OCh layer. When the OTU detects LOS alarms and there is no OTS_LOS-P, OMS_LOS-P, or OMS_SSF-P alarm at the upper OMS and OTS layers, the OCH_LOS-P alarm is reported.
Attribute
Alarm Severity Critical
Issue 02 (2011-10-31)
Alarm Type Communication alarm
556
4 Alarm Processing
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise, the services are interrupted.
Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The board detects no payload signals because of there is a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Confirm that the fiber connection between the OTU board that reports this alarm and the DEMUX board is correct. Step 3 If the alarm persists, check whether the output optical power at the OUT interface of the OTU board at the opposite or upstream station is normal. If not, clear the alarm according to the procedure to handle the IN_PWR_HIGH or IN_PWR_LOW alarm to make the output optical power normal. Step 4 If the alarm persists, check whether the fiber at the OUT interface of the OTU board at the opposite or upstream station is disconnected from the MUX board. If yes, correctly connect the fiber between the two boards. Step 5 If the alarm persists, check whether the dispersion of the fiber is compliant with the requirement. For specifications of the dispersion, see the Product Description. If not, connect a suitable dispersion compensation module according to the Troubleshooting. Step 6 Check whether there is the R_LOS alarm. l l If yes, clear the alarm according to the handling procedure of R_LOS. If not, replace the faulty board according to the Parts Replacement.
----End
Related Information
None
4.140 OCH_OCI
Description
The OCH_OCI is an alarm indicating an open connection at the OCh layer. No optical crossconnections are configured on the upstream service link, or no logical fiber connection is configured from the OTU board to the MUX board. In this case, the OCI signal is inserted to
4 Alarm Processing
the downstream service link. After receiving the OCI signal, the optical termination node in the downstream reports the OCH_OCI alarm.
Attribute
Parameters
None

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. No optical cross-connection for services to the local station is configured at the upstream station.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether the services of the optical cross-connections at the upstream station are configured. If not, re-configure the optical cross-connections to ensure the normal transmission of the services. ----End
Related Information
None
4.141 OCH_SSF
Description
The OCH_SSF is an alarm indicating that the server signal fails at the OCh layer. When the OCH_SSF-P and OCH_SSF-O alarms coexist, this alarm is generated. At the same time, the OCH_SSF-P and OCH_SSF-O alarms are suppressed. Reported from the WDM side or client side: WDM side
Issue 02 (2011-10-31)
558
4 Alarm Processing
Attribute
Parameters
None

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The OTS-LOS alarm at the upper OTS layer or the OMS-LOS alarm at the OMS layer is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOSP alarm on the FIU connected to the local board, If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarm by following the proper handling procedures. Step 3 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOSO, or OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarm by following the proper handling procedures. ----End
Related Information
None
4.142 OCH_SSF-O
Description
The OCH_SSF-O is an alarm indicating that server signal (overhead) fails at the OCh layer. When the OMS layer detects the lost of the overhead signals, this alarm is generated. Reported from the WDM side or client side: WDM side
4 Alarm Processing
Attribute
Parameters
None

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

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

When the ODU_AIS alarm is generated, the entire ODU path is unavailable.
Possible Causes
The possible causes of the ODU_AIS alarm are as follows: l l l Alarms of higher levels exist at the local station, such as R_LOS, FEC_LOF, OTU_LOF, and OTU_AIS. The upstream services are faulty. This board is faulty.
Procedure
Step 1 Check on the U2000 whether the alarms of higher levels such as R_LOS, FEC_LOF, OTU_LOF. and OTU_AIS exist at the local station. If yes, clear these alarms and then check whether the ODU_AIS alarm is cleared. Step 2 If the ODU_AIS alarm persists, locate the fault in the upstream direction. Determine the station (FR station) that is the first to receive the ODU_AIS alarm. Then follow Step 1 to troubleshoot the FR station. Step 3 If the ODU_AIS alarm still persists, troubleshoot the upstream station (PR station) of the FR station. Check whether any alarms of higher levels exist in the receive part of the PR station. If yes, clear the alarms. Step 4 If the ODU_AIS alarm still persists, perform a loopback for the service output optical interfaces of the upstream stations from the FR station. Determine the station (FL station) where the ODU_AIS or alarms of higher levels occur for the first time after the loopback. Troubleshoot the FL station as follows: 1. 2. 3. Check the configuration at the FL station. If any fault exists, correct the connection and configuration. If the ODU_AIS alarm persists, replace the line boards at the FL station. If the ODU_AIS alarm still persists, replace the cross-connect and timing board at the FL station.
----End
Related Information
None
4.145 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the ODU path are locked.
4 Alarm Processing
Attribute
Parameters
None

When the ODU_LCK alarm is generated, the entire ODU path is locked and thus cannot be configured with services of customers.
Possible Causes
The possible causes of the ODU_LCK alarm are as follows: l l The ODU path test is performed. This board is faulty.
Procedure
Step 1 Check whether the ODU path test is performed. If yes, wait until the ODU path test is complete. Cancel the lockout. Then, check whether the ODU_LCK alarm is cleared. Step 2 If no ODU path test is performed, cancel the lockout and then check whether the ODU_LCK alarm is cleared. Step 3 If the alarm persists, the board hardware may be faulty. In this case, replace the board that reports the alarm. ----End
Related Information
None
4.146 ODU_OCI
Description
The ODU_OCI is an ODU open connection indication.
Issue 02 (2011-10-31)
563
4 Alarm Processing
Attribute
Parameters
None

When the ODU_OCI alarm is generated, no connection source exists for the entire ODU path. At this time, the service is unavailable.
Possible Causes
The possible causes of the ODU_OCI alarm are as follows: l l l Alarms of higher levels exist at the local station, such as R_LOS, FEC_LOF, OTU_LOF, and OTU_AIS. The upstream services are faulty. This board is faulty.
Procedure
Step 1 On the U2000, check whether the alarms of higher levels such as R_LOS, FEC_LOF, OTU_LOF, and OTU_AIS exist at the local station. If yes, clear these alarms and then check whether the ODU_OCI alarm is cleared. Step 2 If the alarm persists, the upstream services may be faulty. Check the upstream equipment. If it is the OptiX OSN equipment, replace the line boards. If it is another type of equipment, add a cross-connection to the downstream ODU path that receives the ODU_OCI alarm according to the corresponding alarm troubleshooting measures. Step 3 If the alarm still persists, the board at the local station may be faulty. In this case, replace the board at the local station. ----End
Related Information
None
4.147 ODU_SNCP_STA_INDI
Description
The ODU_SNCP_STA_INDI alarm indicates the state of the ODU SNCP protection group. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
4 Alarm Processing
Attribute
Parameters

l l When switching is performed to the ODU SNCP group, the services would be transiently interrupted. When the alarm is reported, the working or protection channel of the ODU SNCP group might have faulty services that need to be restored.
Possible Causes
l l l Cause 1: A user issues an external switching command such as forced switching, manual switching or locked switching. Cause 2: The services of the working channel or the protection channel of the ODU SNCP group are faulty. Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
l Cause 1: A user issues an external switching command. 1. On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching or locked switching, check whether the external switching operation is necessary. If the external switching operation is necessary, ignore the alarm.
2.
Issue 02 (2011-10-31)
4 Alarm Processing
3. l
If the external switching operation is unnecessary, issue a command to clear the external switching.
Cause 2: The services of the working channel or the protection channel of the ODU SNCP group are faulty. 1. Query whether the related boards for configuring the protection group have the alarms, for example, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_LTC, ODUk_TCMn_TIM, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC, ODUk_TCMn_DEG, ODUk_TCMn_EXC. If these boards have these alarms, handle the alarms by referring to the corresponding handling procedure of the alarms to restore the services of the working channel or the protection channel. If the alarm persists, check whether the attribute of the protection group is Revertive. If the attribute is Revertive, the working channel would automatically switch to the working channel. The alarm would clear. If the attribute is NonRevertive, set it to Revertive and the alarm would clear. This alarm requires no handling. After WTR Times (s), the alarm clears.
2.
Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears. 1.
----End
Related Information
For details, see "ODUk SNCP Protection" in the Feature Description.
4.148 ODUk_LOFLOM
Description
The ODUk_LOFLOM is an alarm indicating that the frame alignment signal (FAS) and multiframe alignment signal (MFAS) are abnormal. The alarm occurs when the information about the upstream frame header and the downstream frame header does not match k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1 or 2. For OptiX OSN 6800, its value is FLEX, 0, 1, 2 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None
4 Alarm Processing

The services on the board are interrupted.
Possible Causes
l l l l l The signals transmitted by the corresponding board at the opposite end do not have a frame structure. The input optical power is abnormal. The FEC type is incorrectly configured. Bit errors in the received signals of the OTU board at the local station are excessive. The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If that is the case, locate the position where the alarm is first generated according to the service route. If no alarm exists at the opposite end, the local end is the place where the alarm is first generated. Step 2 Check whether the input optical power of the place where the alarm is first generated is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. If the optical power is abnormal, handle the alarm according to the handling procedure of the IN_PWR_HIGH or IN_PWR_LOW alarm. Step 3 Query the FEC type of the board set on the U2000 to check whether it is consistent with the FEC type of the board. For specific error correction types, see the Hardware Description. If they are not consistent, modify the setting on the U2000 to ensure the consistency. Step 4 Query the performance value of the BIP8 bit errors in the received signals of the board at the local station by using the U2000. If the BIP8 bit errors are excessive, handle the alarm according to the handling procedure of the OTUk_DEG or OTUk_EXC alarm. Step 5 If the alarm persists, check whether the fiber meets the following requirements: l The bending radius is not less than 40 mm. l The optical interface connector is well inserted. l The fiber connector is clean. l The cable is intact. If the preceding requirements are not met, clean the fiber connector or replace the fiber. For details, see the Supporting Tasks. ----End
Related Information
ITU-T G.709
4.149 ODUk_PM_LCK
Description
The ODUk_PM_LCK is an alarm indicating that the ODUk PM signal is locked. The maintenance signal LCK byte required by the carrier is used to lock the access point signal of
4 Alarm Processing
users during testing. It can be generated when the service layer adapts the source and sink. The alarm is generated when the STAT byte value is "101" during locking. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None

The services borne by the optical port would be interrupted.
Possible Causes
The services at the optical port are interrupted.
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that generates this alarm. Step 2 Query the board information and set LCK Insertion to Disabled if it is Enabled, and the local station does not insert an LCK signal to the downstream. ----End
Related Information
ITU-T G.709
4.150 ODUk_PM_OCI
Description
The ODUk_PM_OCI is an alarm indicating an ODUk PM open connection. The alarm is generated when the output interface is not connected to the input interface and the STAT byte value is "110". k indicates the level of rate. l
Issue 02 (2011-10-31)
For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3.

4 Alarm Processing
l l
For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None

The services at the optical port are interrupted.
Possible Causes
l l l The corresponding board at the upstream station has the ODUk_PM_OCI alarm. There is loopback on the corresponding board at the opposite station. The corresponding board at the opposite station has no or incorrect cross-connection configuration.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 If the alarm persists, query whether the upstream stations generate the alarm. If that is the case, locate the station where the alarm is triggered according to the service route. Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback. If that is the case, release the loopback. Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is configured with incorrect cross-connection or has no cross-connection configuration. If that is the case, correctly configure the cross-connection. ----End
Related Information
ITU-T G.709
4.151 ODUk_PM_TIM
Description
The ODUk_PM_TIM is an alarm indicating mismatch of the ODUk PM trace identifier. The alarm occurs during control process when the trace identifier at the opposite end mismatches
4 Alarm Processing
that at the local end when the TIM detection is enabled. The system compares the access point identifiers (API) in the input signals and the expected API. For the set TIM detection mode, the network architecture can be classified into the following three types. l l l For the point-to-point topology, only the source access point identifiers (SAPI) is compared for the sink of trail termination. For the point-to-multipoint topology, only the SAPI is compared for the sink of trail termination. For the multipoint-to-multipoint topology, only the destination access point identifiers (DAPI) is compared for the sink of trail termination.
k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None

If the alarm is generated, the signal quality of the services at the optical port is degraded. Hence, the service signals may be unavailable.
Possible Causes
l l l l The networking architecture and the TIM detection mode to be configured are not consistent. The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be received at the local end. The fiber connection is incorrect. The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for the local end on the U2000 interface according to networking architecture. If the topology is a point-to-point topology or point-to-multipoint topology, only the SAPI is compared for the sink of trail termination. If the topology is multipoint-to-multipoint topology, only the DAPI is compared for the sink of trail termination.
4 Alarm Processing
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be received at the local end through the U2000. If they are not consistent, query the received TTI on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to the same as these of the received TTI. Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber. Step 4 Check whether the cross-connection configuration is correct. If not, correctly configure the cross-connection. ----End
Related Information
ITU-T G.709
4.152 ODUk_TCMn_AIS
Description
The ODUk_TCMn_AIS is an ODUk TCMn alarm signal indication. An AIS signal travels downstream, which indicates that a signal failure is detected in the upstream. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
None

The services at the optical interface are unavailable.
Possible Causes
l l
Issue 02 (2011-10-31)
Signals input from the client side contain the ODUk_TCMn_AIS signal. The corresponding board at the opposite end transmits the ODUk_TCMn_AIS signals.
4 Alarm Processing
The loopback or cross-connection is set at the upstream station, and the FEC type is incorrectly configured.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 Query whether the alarm is reported from the client side. If that is the case, check the equipment on the client side. Step 3 Query whether the ODUk_PM_AIS, R_LOS, or R_LOF alarm exists on the client side of the OTU board at the opposite end by using the U2000. If the alarm exists, check the equipment at the opposite end. Step 4 Query whether the loopback is set on the upstream station by using the U2000. If that is the case, release the loopback of the upstream station. Step 5 Check whether the configuration of the cross-connection and FEC type at the upstream station is correct. If the configuration is incorrect, modify the configuration. ----End
Related Information
ITU-T G.709
4.153 ODUk_TCMn_BDI
Description
The ODUk_TCMn_BDI is an ODUk TCMn backward defect indication. The alarm occurs when five consecutive BDI bytes in the TCMn overhead field are "1". k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Parameters
None
4 Alarm Processing

Bit errors occur at the downstream station.
Possible Causes
l l Signals input from the client side contain the ODUk_TCMn_BDI signal. The corresponding OTU board at the downstream station receives the LOF, LOM, ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or ODUk_TCMn_SSF alarm.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 Query whether the alarm is reported from the client side or the WDM side. l l If the alarm is reported from the client side, check the equipment on the client side. If the alarm is reported from the WDM side, check whether the corresponding OTU board at the downstream station receives the LOF, LOM, ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or ODUk_TCMn_SSF alarm by using the U2000. If yes, handle the corresponding alarm at the downstream station.
----End
Related Information
ITU-T G.709
4.154 ODUk_TCMn_DEG
Description
The ODUk_TCMn_DEG is an alarm indicating that the ODUk TCMn signal is degraded. This alarm occurs when the signal is degraded or bit errors cross the threshold if the error detection is in the burst mode. This alarm occurs when the signal is degraded or bit errors cross the threshold if the error detection is in the Poisson mode. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Issue 02 (2011-10-31)
573
4 Alarm Processing
Parameters
None

If the alarm is generated, the services at the optical interface generate bit errors, which make the service signals unavailable.
Possible Causes
l l l The optical interface that reports the alarm is faulty. The optical interface at the opposite end is faulty. The fiber of the transmission line is abnormal.
Procedure
Step 1 Use the U2000 to browse alarms of the entire network to determine the slot ID, interface ID, and channel ID of the board that generates this alarm. Step 2 Locate the point that first generates the ODUk_TCMn_DEG alarm according to the service route. Step 3 Step 3 Check whether the input optical power of the place where the alarm is first generated is within the normal range by using the U2000. If not, handle it according to the handling procedures of the IN_PWR_HIGH and IN_PWR_LOW alarms. For optical power specifications of specific boards, see the Product Description. Step 4 If the alarm persists, check whether the fiber meets the following requirements: l The bending radius is not less than 40 mm. l The optical interface connector is well inserted. l The fiber connector is clean. l The cable is intact. If the preceding requirements are not met, clean the fiber connector or replace the fiber. For details, see the Supporting Tasks. Step 5 If the alarm persists, the optical interface on the board at the local end may be faulty. Replace the faulty board. For details, see the Parts Replacement. Step 6 If the alarm persists, the optical interface on the OTU board at the opposite end may be faulty. Replace the faulty OTU board. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)
574
4 Alarm Processing
4.155 ODUk_TCMn_EXC
Description
The ODUk_TCMn_EXC is an alarm indicating that the ODUk TCMn section BIP8 errors cross the threshold. This alarm occurs when the bit errors cross the threshold if the error detection is in the Poisson mode. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3 For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Parameters
None

The alarm has an influence on the QoS of the service signals.
Possible Causes
l l l The attenuation of the received signals is excessively large, and the fiber of the transmission line is abnormal. The transmit part of the opposite station is faulty. The receive part of the local station is faulty.
Procedure
Step 1 Check whether the received optical power of the interface is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. If the receive optical power of the board at the local station is excessively low, clear the alarm according to the handling procedure of the IN_PWR_LOW alarm. Step 2 If the alarm persists, check whether the transmit optical power of the corresponding interface on the upstream board is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. If the transmit optical power of the board at the upstream station is excessively low, clear the alarm according to the handling procedure of the OUT_PWR_LOW alarm.
4 Alarm Processing
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station by using the U2000. Loop back the transmit optical interface and receive optical interface on the WDM side of the OTU board at the upstream station. If the bit errors exist, clear the bit error fault of the upstream station. Step 4 If the alarm persists, replace the faulty board at the local station. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.156 ODUk_TCMn_LCK
Description
The ODUk_TCMn_LCK is an alarm indicating that the ODUk TCMn signal is locked. The maintenance signal LCK byte required by the carrier is used to lock the access point signal of users during testing. It can be generated when the service layer adapts the source and sink. The alarm is generated when the STAT byte value is "101" during locking. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Parameters
None

Possible Causes
The signals are locked for the test of current line signals.
4 Alarm Processing
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that generates this alarm. Step 2 Set the LCK type to Disabled if it is Enabled. ----End
Related Information
ITU-T G.709
4.157 ODUk_TCMn_LTC
Description
The ODUk_TCMn_LTC is an alarm indicating loss of ODUk TCMn serial connection. The TCM provides the connection monitoring function of the ODUk to cater for different application scenarios. For example, the TCM from optical NNI to optical NNI monitors the connection of the ODUk through the carrier network. The alarm occurs when the serial connection is lost and the STAT byte is "000". k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3 For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Parameters
None

The TCM is not available.
Possible Causes
The TCM at the opposite end is not set as enabled, and thus there is no TCM source.
4 Alarm Processing
Procedure
Step 1 On the U2000, find the position that generates this alarm first according to the network topology. Step 2 Query whether the source configuration of this position and its opposite position is correct. If not, modify the configuration ----End
Related Information
ITU-T G.709
4.158 ODUk_TCMn_OCI
Description
The ODUk_TCMn_OCI is an ODUk TCMn open connection indication. The alarm occurs when the output interface is not connected to the input interface and the STAT byte is "110". k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Parameters
None

Possible Causes
l l l The corresponding board at the upstream station has the ODUk_TCMn_OCI alarm. There is loopback on the corresponding board at the opposite station. The corresponding board at the opposite station has no or incorrect cross-connection configuration.
Issue 02 (2011-10-31)
4 Alarm Processing
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 If the alarm persists, check whether the upstream station has this alarm. If yes, locate the station that triggers this alarm according to the service route. Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback. If yes, release the loopback. Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is configured with incorrect or no cross-connection. If yes, configure the correct cross-connection. ----End
Related Information
ITU-T G.709
4.159 ODUk_TCMn_SSF
Description
The ODUk_TCMn_SSF is an alarm indicating that the ODUk TCMn server signal fails. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
Parameters
None

Possible Causes
l
Issue 02 (2011-10-31)
The ODUk_TCMn_AIS or ODUk_LOFLOM alarm is generated on the line.

4 Alarm Processing
l l
The OTUk_TIM alarm is generated on the line and the OTUk_TIM follow-up response is set to be enabled. The OTUk_SSF alarm is generated.
Procedure
Step 1 Check along the service signal flow to locate the station that first generates the SSF alarm. 1. 2. Check whether the ODUk_PM_AIS or ODUk_LOFLOM alarm occurs at the station. If yes, clear the alarm according to the corresponding handling procedure. Check whether the OTUk_TIM alarm occurs at the station. If yes, clear the alarm according to the alarm handling procedure.
Step 2 If the alarm persists, check whether the OTUk_SSF alarm occurs on the line or not. If yes, clear the alarm according to the alarm handling procedure. ----End
Related Information
None
4.160 ODUk_TCMn_TIM
Description
The ODUk_TCMn_TIM is an alarm indicating ODUk TCMn trace identifier mismatch. This alarm occurs during control process when the trail trace identifier at the opposite end mismatches that at the local end when the TIM detection is enabled. The system compares the access point identifiers (API) in the input signals and the expected API. For the set TIM detection mode, the network architecture can be classified into the following three types: l l l For the point-to-point topology, only the source access point identifiers (SAPI) is compared for the sink of trail termination. For the point-to-multipoint topology, only the SAPI is compared for the sink of trail termination. For the multipoint-to-multipoint topology, only the destination access point identifiers (DAPI) is compared for the sink of trail termination.
k indicates the level of rate. l l l For OptiX OSN 8800, its value is 0, 1, 2, 3. For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Issue 02 (2011-10-31)
580
4 Alarm Processing
Attribute
Parameters
None

If the alarm is generated, the quality of the signals at the optical interface is degraded. Hence, the service signals may be unavailable.
Possible Causes
l l l l The networking architecture and the TIM detection mode to be configured are not consistent. The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be received at the local end. The fiber connection is incorrect. The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for the local end on the U2000 interface according to the networking architecture. If the topology is point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the sink of trail termination. Step 2 Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be received at the local end through the U2000. If they are not consistent, query the received TTI on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to the same as these of the received TTI. Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber. Step 4 Check whether the cross-connection configuration is correct. If not, correctly configure the cross-connection. ----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)
581
4 Alarm Processing
4.161 ODUKSP_PS
Description
The ODUKSP_PS is an alarm indicating the ODUk SP protection switching. This alarm occurs when the ODUk SP protection group actuates switching in which the current channel switches to the protection channel from the working channel.
Attribute
Parameters
None

When the ODUk SP protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the ODUk SP protection group might have faulty services that need to be restored.
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the ODUk SP protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the ODUk SP protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
Procedure
Step 2 If the alarm is generated due to the automatic switching of the protection group, 1. Query whether the related boards for configuring the protection group have alarms relevant to the services, such as R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI, ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG and ODUk_TCMn_EXC. If yes, handle the alarms by referring to the corresponding alarm handling procedures.
Issue 02 (2011-10-31)
4 Alarm Processing
2.
If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
----End
Related Information
The ODUk SPRing protection mainly applies to the ring network with distributed services. This protection uses two different ODUk channels to achieve the protection of multiple distributed services between all stations. For details, see "ODUk SPRing Protection" in the Feature Description.
4.162 ODUKSP_STA_INDI
Description
The ODUKSP_STA_INDI is an alarm indicating the state of the ODUk SPRing protection group. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
Attribute
Parameters
Issue 02 (2011-10-31)
583
4 Alarm Processing
Description Indicate the west switching request. For example: l 0x16: LP l 0X15: SF_P l 0x13: SF_R l 0x12: SF_RP l 0x11: SF_RW l 0x10: SF_W l 0x0E: FS_R l 0x0D: SD_P l 0x0B: SD_R l 0x0A: SD_W l 0x08: MS_R l 0x06: WTR_R l 0x03: EXER_R l 0x00: NR
Parameters 1
Indicate the east switching request. For example: l 0x16: LP l 0X15: SF_P l 0x13: SF_R l 0x12: SF_RP l 0x11: SF_RW l 0x10: SF_W l 0x0E: FS_R l 0x0D: SD_P l 0x0B: SD_R l 0x0A: SD_W l 0x08: MS_R l 0x06: WTR_R l 0x03: EXER_R l 0x00: NR

l l When the ODUk SP protection switching is performed, the services are transiently interrupted. When the alarm is reported, the working or protection channel in the ODUk SP protection group may contain faulty services. In this case, you need to remove the fault to restore the services.
Issue 02 (2011-10-31)
584
4 Alarm Processing
Possible Causes
l l l The user issues an external switching command such as forced switching, manual switching, or locked switching. The services of the working or protection channel of the ODUk SP protection group are faulty. The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching, or locked switching, check whether the external switching is necessary. 1. 2. If the external switching is necessary, ignore the alarm. If the external switching is unnecessary, issue a switching clearing command to clear the external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection group, do as follows: 1. Check whether service related alarms such as R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI, ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG or ODUk_TCMn_EXC occur on the corresponding boards in the protection group. If yes, clear the alarm according to the corresponding alarm handling procedures to restore the services of the working channel or protection channel.
Related Information
The ODUk SPRing protection mainly applies to the ring network with distributed services. This protection uses two different ODUk channels to achieve the protection of multiple distributed services between all stations. For details, see "ODUk SPRing Protection" in the Feature Description.
4.163 OH_LOOP
Description
The OH_LOOP is an alarm of overhead bus loopback. This alarm occurs when the overhead bus of a line board is looped back.
Attribute
Alarm Severity Minor Alarm Type Security alarm
Issue 02 (2011-10-31)
585
4 Alarm Processing
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning l 0x01: indicates a loopback on the line board. l 0x02: indicates a loopback on the opposite board. l 0x03: indicates a loopback on the SCC board.

When the OH_LOOP alarm occurs, the overhead signal is looped back. The services are not affected but the ECC communication is interrupted.
Possible Causes
The overhead bus of the line board is looped back.
Procedure
Step 1 After the loopback is released, the OH_LOOP alarm is automatically cleared. ----End
Related Information
None
4.164 OLP_PS
Description
The OLP_PS is an alarm indicating the optical line protection switching. This alarm occurs when the optical line protection group actuates switching in which the current channel switches to the protection channel from the working channel.
Attribute
Parameters
None
4 Alarm Processing

When the optical line protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the optical line protection group might have faulty services that need to be restored.
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the optical line protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the optical line protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported. Cause 3: The difference between the optical power on the working channel and that on the protection channel exceeds the threshold.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced switching or manual switching, check whether the external switching operation is necessary, 1. 2. If the external switching operation is necessary, ignore the alarm. If the external switching operation is unnecessary, issue an external command to switch the current channel to the working channel, thus clearing the alarm. Query whether the input optical power of the working channel is within the normal range on the U2000. For optical power specifications of specific boards, see the Product Description. If the optical power is not within the normal range, handle the alarm according to the handling procedure of the IN_PWR_LOW alarm to make the input optical power of the working or protection channel be within the normal range. If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
Step 2 If the alarm is generated due to the automatic switching of the protection group, 1.
2.
Step 3 If the alarm persists, check whether the POWER_DIFF_OVER alarm exist. If that is the case, handle the alarms according to the corresponding handling procedures. ----End
Related Information
Optical line protection (OLP) protects line fibers between adjacent stations by using the dual fed and selective receiving function of OLP boards. For details, see "Optical Line Protection" in the Feature Description.
Issue 02 (2011-10-31)
587
4 Alarm Processing
4.165 OLP_STA_INDI
Description
The OLP_STA_INDI is an alarm indicating the optical line protection switching. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
Attribute
Parameters

l l When protection switching is performed on the optical line, the services are transiently interrupted. When the alarm is reported, the working or protection channel of the optical line protection group may have faulty services that need to be restored.
Possible Causes
l l l
Issue 02 (2011-10-31)
The user issues an external switching command such as forced switching, manual switching or locked switching. The services of the working channel or protection channel of the optical line protection group are faulty. The switching is in the WTR state. After the WTR time, the alarm is cleared.
4 Alarm Processing
Procedure
Step 2 If the alarm is generated due to the fault of the working channel or protection channel of the protection group, do as follows: 1. Query whether the input optical power of the working or protection channel is within the normal range on the U2000. For optical power specifications of specific boards, see the Product Description. If the optical power is not within the normal range, handle the alarm according to the handling procedure of the IN_PWR_LOW alarm to make the input optical power of the working or protection channel be within the normal range. If the alarm persists, check whether the attribute of the protection group is Revertive. If that is the case, the services in the working channel automatically switch to the working channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the alarm is cleared.
2.
Related Information
Optical line protection (OLP) protects line fibers between adjacent stations by using the dual fed and selective receiving function of OLP boards. For details, see "Optical Line Protection" in the Feature Description.
4.166 OMS_BDI
Description
The OMS_BDI is the backward defect indication at the OMS layer. When the OMS_BDI-P and OMS_BDI-O alarms coexist, this alarm is generated. At the same time, the OMS_BDI-P and OMS_BDI-O alarms are suppressed.
Attribute
Parameters
None
4 Alarm Processing

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

Possible Causes
l The downstream station inserts the BDI-O overhead signal back to the OMS layer of the local station, when the downstream station detects no overhead signals because of a fiber
Issue 02 (2011-10-31)
4 Alarm Processing
cut, low optical power, or dispersion. This alarm is generated when the local station receives the BDI-O overhead signal. l The local station sends no overhead signals.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is the OTS_LOS-O alarm at the opposite station and all downstream stations. If yes, clear the OTS_LOS-O alarm by following proper handling procedures. ----End
Related Information
None
4.168 OMS_BDI-P
Description
The OMS_BDI-P is a backward defect indication (payload) at the OMS layer. The OMS_BDIP signal is inserted back to the upstream station when the downstream station receives no payload signals from the upstream station.
Attribute
Parameters
None

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

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

Possible Causes
The FDI-P signal is inserted to the OMS layer of the downstream station, when the local station detects no payload signals because of a fiber cut, low optical power, or dispersion. This alarm is generated when the downstream station receives the FDI-P signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is the OTS_LOS-P alarms at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P alarm by following proper handling procedures. ----End
Related Information
None
4 Alarm Processing
4.171 OMS_LOS-P
Description
The OMS_LOS-P is an alarm indicating loss of signal (payload) at the OMS layer. If there is no OTS_LOS-P alarm at the OTS layer, the OMS_LOS-P alarm is reported when the OTU board detects the LOS alarm.
Attribute
Parameters
None

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

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

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. Because of a fiber cut, low optical power, dispersion, or failure in overhead signals at the upstream OTS layer, the OTS layer of the board loses the overhead signals and the overhead signals received by the OMS layer from the OTS layer are invalid. Hence, this alarm is reported.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is the OTS_LOS-O or OOS_LOST alarm on the FIU connected to the local board. If yes, clear the OTS_LOS-O, or OOS_LOST alarm by following proper handling procedures. Step 3 If the alarm persists, check whether there is the OTS_LOS-O, or OOS_LOST alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS-O, or OOS_LOST alarm by following proper handling procedures. ----End
Related Information
None
4 Alarm Processing
4.174 OMS_SSF-P
Description
The OMS_SSF-P is an alarm indicating that the server signal fails (payload) at the OMS layer. When the OTS layer detects the failure of the payload signals or receives the OMS_FDI-P signal from the upstream station, this alarm is generated.
Attribute
Parameters
None

Possible Causes
The logical fiber connection is not consistent with the actual fiber connection. When the service-layer payload signals received by the OMS layer are invalid and the OTS layer can not detect any signals because of a fiber cut, low optical power, or dispersion, this alarm is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is OTS_LOS-P alarm on the FIU connected to the local board. If yes, clear the OTS_LOS-P alarm by following proper handling procedures. Step 3 If the alarm persists, check whether there is the OTS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS-P alarms by following proper handling procedures. ----End
Related Information
None
4 Alarm Processing
4.175 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm occurs when the phase-locked loop on the clock board becomes faulty. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the failed phase-locked loop. l 0x01: first 2M phase-locked loop l 0x02: second 2M phase-locked loop l 0x03: 155M system phase-locked loop

When the OOL alarm is generated, the phase-locked loop cannot lock on the input signals, and as a result the output clock signals are affected. This alarm may lower the quality of services or interrupt the services.
Possible Causes
Cause 1: The board hardware of the phase-locked loop is damaged.
Procedure
l Cause 1: The board hardware of the phase-locked loop is damaged. 1. 2. ----End
Perform cold reset on the board. Then, check whether the alarm is cleared. For details, see Performing Cold Reset of a Board in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
4 Alarm Processing
Related Information
4.176 OOS_LOST
Description
The OOS_LOST is an alarm indicating loss of OTM overhead signal (OOS). When the local station receives no overhead signals in ten consecutive seconds and there is no OTS_LOS-O alarm, this alarm is generated.
Attribute
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise, there may be an impact on the optical-layer overhead.
Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The local station receives no overhead signals in ten consecutive seconds because the opposite station sends no overhead signals.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether the opposite station supports the OLS function. l l If not, this alarm does not need to be handled. If yes, make sure that the opposite station sends the correct overhead signals.
----End
Related Information
None
Issue 02 (2011-10-31)
599
4 Alarm Processing
4.177 OPA_FAIL_INDI
Description
The OPA_FAIL_INDI alarm is an alarm indicating that the automatic power adjustment (OPA) of the optical cross-connection fails. The alarm occurs if the calculated attenuation exceeds the settable range of the board when the optical power is automatically adjusted.
Attribute
Parameters
Parameter Parameter 1 Description Indicates the ID of the wavelength of the optical cross-connection.

l l When the alarm is reported, the attenuation of the board is not adjusted. For new services, the services may be unavailable. For existing services, the QoS cannot be improved. This alarm indicates an operation failure instead of a fault being detected. In other words, this alarm persists even after you manually adjust the attenuation and services are restored.
Possible Causes
l l l Cause 1: The optical power budget is insufficient. Cause 2: The attenuation of the VA1 or VA4 board is manually modified if the VA1 or VA4 board is used. Cause 3: When there are adjustment points of multiplexed wavelengths and each single wavelength in OPA scenarios, the attenuation of the VOAs at the multiplexed wavelength adjustment points is not adjusted to the minimum value. For example, in the OPA application scenario, the built-in VOAs on multiplexer or demultiplexer boards or optical add/drop multiplexer (OADM) boards adjust single wavelengths, and the VA1 or VA4 boards on the line side or the built-in VOAs adjust multiplexed wavelengths.
Procedure
l Cause 1: The optical power budget is insufficient. 1. Use OA boards with larger optical power, and modify the rated input and output optical power of the OA boards. For details, see "Setting the Rated Optical Power of the OA Board" in the Commissioning Guide.
Cause 2: The attenuation of the VA1 or VA4 board is manually modified if the VA1 or VA4 board is used.
Issue 02 (2011-10-31)
4 Alarm Processing
1.
Change the optical cross-connection mode from automatic to manual and change the mode to automatic again. The OPA will be triggered after the mode is changed from manual to automatic. Therefore, check whether services are configured on the trail where the OPA applies before you change the mode.
Cause 3: When there are adjustment points of multiplexed wavelengths and each single wavelength in the automatic optical power adjustment scenario, the attenuation of the VOAs at the multiplexed wavelength adjustment points is not adjusted to the minimum value. 1. On the U2000, adjust the attenuation of the VOAs on the VA1 or VA4 board or an OA board to the minimum value, change the mode of all optical cross-connections on the trail from automatic to manual, and then change the mode to automatic again. The OPA will be triggered after the mode is changed from manual to automatic. Therefore, check whether services are configured on the trail where the OPA applies before you change the mode.
----End
Related Information
The optical power adjustment (OPA) technology is available in the commissioning phase. For details, see "Optical Power Adjust (OPA)" in the Feature Description.
4.178 OPU1_MSIM
Description
The OPU1_MSIM is an alarm indicating the OPU1 multiplex structure identifier mismatch.
Attribute
Parameters
None

The services may be unavailable.
Possible Causes
The board does not support the multiplex structure for service transmission of the board on the source NE.
Issue 02 (2011-10-31)
601
4 Alarm Processing
Procedure
Step 1 Check whether the multiplex structure of the local board mismatches with that of the corresponding board on the source NE. For the multiplex structure of the board, see the Hardware Description. Step 2 If the multiplex structures of the two boards do not match, replace one of them with a matched board. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.179 OPU1_VCAT_SQM
Description
The OPU1_VCAT_SQM is an alarm indicating the OPU1 sequence indicator mismatch. The alarm is generated when the received OPU1 sequence indicator (SQ) value is not consistent with the expected value. For example, the SQ values of channels 1-4 on the system side are 0-3 respectively. When the services from channel 1 are connected to channel 2 on the system side of the opposite TDX, the received SQ value is 0 and the SQ value to be received is 1. The values mismatch, and then the alarm is generated.
Attribute
Parameters
None

When an OPU1_VCAT_SQM is detected, the value of received SQ is not consistent with the value of SQ to be received. Then, the services are interrupted.
Possible Causes
The cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the cross-connection sequence of the virtual cascading OPU1 at the local end mismatches that at the opposite end. If not, re-configure the virtual cascading OPU1s at the local end. ----End
4 Alarm Processing
Related Information
Each channel on the WDM side has an SQ value. The SQ values of optical interfaces are in an ascending order. Compare the SQ value of the frame in each WDM-side optical interface with that of its previous frame. If mismatch is found, the SQ mismatch alarm of the optical interface is reported. If the SQ values of two optical interfaces are the same, the board also reports the SQ mismatch alarm.
4.180 OPU1_VCAT_VcPLM
Description
The OPU1_VCAT_VcPLM is an alarm indicating mismatch of the OPU1 virtual concatenation payload. The alarm is generated when the type of the OPU1 virtual concatenation payload received mismatches the expected type. Each service type corresponds to a VcPt value. For 10GE LAN, the value is 5. For STM-64, the value is 3. When two TDXs interconnected with each other, the alarm is generated if the service types at the two ends mismatch.
Attribute
Parameters
None

Possible Causes
l l Service type configuration is incorrect. Cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the VcPt value to be received at the local end is consistent with the received VcPt value. If not, check whether the service type at the opposite end is consistent with that at the local end. Re-configure the cross-connect service of the interconnected TDX board. Step 2 If the alarm persists, check whether the VcPt value of the services transmitted from the opposite end is consistent with the VcPt value to be received at the local end. If not, re-configure the cross-connect service at the opposite end. ----End
4 Alarm Processing
Related Information
ITU-T G.709
4.181 OPU2_MSIM
Description
The OPU2_MSIM is an alarm indicating that mismatch of the OPU2 multiplex structure indicator.
Attribute
Parameters
None

Possibly the services are not available.
Possible Causes
Procedure
Step 1 Check whether the multiplex structure of the local board mismatches with that of the corresponding board of the source NE. For the multiplex structure of the board, see the Hardware Description. Step 2 If the multiplex structures of the two boards do not match, replace one of them with a matched board. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.182 OPU3_MSIM
Description
The OPU3_MSIM is an alarm indicating mismatch of the OPU3 multiplex structure.
4 Alarm Processing
Attribute
Parameters
None

Possible Causes
Procedure
Step 1 Check whether the multiplex structure of the local board mismatches with that of the corresponding board of the source NE. For the multiplex structure of the board, see the Hardware Description. Step 2 If the multiplex structures of the two boards do not match, replace one of them with a matched board. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.183 OPUk_PLM
Description
The OPUk_PLM is an alarm indicating OPUk payload mismatch. The type of received payload mismatches the expected payload type defined in the adaptation function. k indicates the level of rate. l l l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3. For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G. For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Issue 02 (2011-10-31)
605
4 Alarm Processing
Attribute
Parameters
None

Possible Causes
The type of the payload in the data on the WDM side of the interconnected board mismatches.
Procedure
Step 1 Use the U2000 to query whether the PT byte value to be received at the OPU of the local board is consistent with that of the received PT bytes. If they are not consistent, modify the PT of the local NE to be consistent. Step 2 Check whether the WDM-side fiber connection is correct according to the engineering fiber connection diagram. If the fiber connection is incorrect, correctly connect the fiber according to the engineering fiber connection diagram. Step 3 Check whether the service type on the client side of the local board is the same as that of the peer board. If the service types on the local board and peer board are not the same, set the service types again based on the network plan to ensure that they are the same. Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei for help. ----End
Related Information
ITU-T G.709
4.184 OSC_BDI
Description
Backward defect indication. This alarm occurs when detects a signal failure and the BDI byte value is 1.
Issue 02 (2011-10-31)
606
4 Alarm Processing
Attribute
Parameters
None

The OSC signals borne by the optical interface would be unavailable.
Possible Causes
BDI is declared if the BDI bit in the overhead field (byte 3, bit 5) is "1" for 5 consecutive frames.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 If the alarm persists, check whether the corresponding board at the downstream station receives the R_LOS orR_LOF alarm by using the U2000. If yes, handle the corresponding alarm at the downstream station. ----End
Related Information
None
4.185 OSC_DEG
Description
Signal degraded alarm. This alarm occurs when bit errors are of burst distribution and the signal degradation or bit error count crosses the threshold.
Attribute
Parameters
None
4 Alarm Processing

If the alarm is generated, the OSC signals borne by the optical interface would generate bit errors, which makes the OSC signals unavailable.
Possible Causes
l l The optical interface at the local end is faulty. The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. For the optical power specification of the specific board, refer to "Technical Specifications" of the Product Description. If the optical power is not within the normal range, see the handing procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms for troubleshooting. Step 2 If the alarm persists, check whether the fiber meets the following requirements: l The bending radius is not less than 40 mm. l The optical interface connector is well inserted. l The fiber connector is clean. l The cable is intact. If the preceding requirements are not met, clean the fiber connector or replace the fiber. For details, see the Supporting Tasks. Step 3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting Tasks. ----End
Related Information
None
4.186 OSC_RDI
Description
The OSC_RDI is an alarm indicating a remote defect. The alarm occurs when the opposite station returns the RDI alarm to the local station after receiving an R_LOF alarm. Reported from the WDM side or client side: NA
Attribute
Issue 02 (2011-10-31)
608
4 Alarm Processing
Parameters
None

The communication between the two stations is abnormal.
Possible Causes
l l l The opposite station returns the RDI alarm to the local station after receiving the R_LOF signals. The optical fiber is damaged. The board is faulty.
Procedure
Step 1 Query whether the opposite station has the R_LOF alarm. If that is the case, take it as the R_LOF alarm for troubleshooting. Step 2 If the alarm persists, check whether the fiber between the two stations is damaged. If that is the case, repair the fiber. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.187 OTS_BDI
Description
The OTS_BDI is an alarm indicating a backward defect at the OTS layer. When the OTS_BDIP and OTS_BDI-O alarms coexist, this alarm is generated. At the same time, the OTS_BDI-P and OTS_BDI-O alarms are suppressed.
Attribute
Parameters
None
4 Alarm Processing

Possible Causes
l l The logical fiber connection is not consistent with the actual fiber connection. The upstream station reports the OTS_LOS alarm, and the downstream station inserts it back to the local station.
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 Check whether there is the OTS_TIM or OTS_LOS alarm at the opposite station. If yes, clear the OTS_TIM or OTS_LOS alarm by following proper handling procedures. Step 3 If the alarm persists, check and make sure that fibers connected to the receive interfaces on the local FIU are correct and there is no fiber disconnection. ----End
Related Information
None
4.188 OTS_BDI-O
Description
The OTS_BDI-O is an alarm indicating a backward defect (overhead) at the OTS layer. After receiving the OTS_BDI-O signal inserted by the upstream station to the downstream, the local station reports the OTS_BDI-O alarm.
Attribute
Parameters
None

4 Alarm Processing
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection. The opposite station inserts the BDI-O signal back to the local station, when detecting no overhead signals because of a fiber cut, low optical power, or dispersion. This alarm is generated when the local station receives the BDI-O overhead signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check and make sure that the fiber connection of the "RM" interface on the local FIU is correct and there is no fiber disconnection. Step 3 Check whether the opposite FIU reports the OTS_LOS-O alarm. If yes, handle the alarm by following proper handling procedures. ----End
Related Information
None
4.189 OTS_BDI-P
Description
The OTS_BDI-P is an alarm indicating a backward defect (payload) at the OTS layer. After receiving the OTS_BDI-P signal inserted back to the local station by the downstream station, the local station reports this alarm.
Attribute
Parameters
None

Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
4 Alarm Processing
The opposite station inserts the BDI-P signal back to the local station, when detecting no payload signal because of a fiber cut, low optical power, or dispersion. This alarm is generated when the local station receives the BDI-P signal.
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check and make sure that fibers connected to the receive interfaces of the local PIU are correct and there is no fiber disconnection. Step 3 Check whether there is the OTS_LOS-P alarm at the opposite station of the FIU. If yes, clear the OTS_LOS-P alarm by following proper handling procedures. ----End
Related Information
None
4.190 OTS_LOS-O
Description
The OTS_LOS-O is an alarm indicating loss of signals (overhead) at the OTS layer. When the OSC board connected to the "TM" interface of the FIU detects the LOS signals, this alarm is generated.
Attribute
Parameters
None

Possible Causes
The logical fiber connection is not consistent with the actual fiber connection. This alarm is generated when the OTS layer of the receive end detects no overhead signal because of a fiber cut, low optical power, or dispersion.
4 Alarm Processing
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check and make sure that the fiber connection between the "TM" interface of the local FIU and the OSC board is correct and there is no fiber disconnection. Step 3 If the alarm persists, check and make sure that the fiber connection between the "TM" interface of the local FIU and the OSC board is correct and there is no fiber disconnection. Step 4 If the alarm persists, check whether the laser of the OSC at the opposite station is "On". If not, open the laser of the OSC. ----End
Related Information
None
4.191 OTS_LOS-P
Description
The OTS_LOS-P is an alarm indicating loss of signal (payload) at the OTS layer. This alarm is generated when the amplifier or other boards connected to the transmit interface of the FIU detects the LOS signals.
Attribute
Parameters
None

Possible Causes
The logical fiber connection is not consistent with the actual fiber connection. This alarm is generated when the OTS layer of the receive end detects no payload signal because of a fiber cut, low optical power, or dispersion.
4 Alarm Processing
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber connection. If not, modify the logical fiber connection to make it consistent with the actual fiber connection. Step 2 If the alarm persists, check and make sure that fibers connected to the interfaces of the local station are correct and there is no fiber disconnection. ----End
Related Information
None
4.192 OTS_TIM
Description
The OTS_TIM is an alarm indicating mismatch of the trail trace identifier at the OTS layer. When the API of the received TTI at the OTS layer is not consistent with the API to be received, this alarm is generated.
Attribute
Parameters
None

If the configuration of the TTI is incorrect, there has no influence to the services. If the fiber connection is incorrect, the services may be interrupted.
Possible Causes
l l The TTI transmitted at the upstream station is not consistent with the TTI to be received at the local station. The fiber actual connection is incorrect.
Procedure
Step 1 Check whether the TTI transmitted at the transmit end (upstream station) is consistent with the TTI to be received at the local end. If not, configure the TTI at the upstream station again. Step 2 Check whether the fiber connection between the OSC and the "RM" or "TM" interface of the FIU is compliant with the network regulation. If not, connect the fibers again. ----End
4 Alarm Processing
Related Information
For details of the API and TTI, see ITU-T G.709.
4.193 OTU_AIS
Description
The OTU_AIS an OTU alarm indication.
Attribute
Parameters
None

When the OTU-AIS alarm is generated, no connection source exists for the entire ODU path. At this time, the service is unavailable.
Possible Causes
The possible causes of the OTU_AIS alarm are as follows: l l l Alarms of higher levels such as R_LOS and FEC_LOF exist at the local station. The upstream services are faulty. This board is faulty.
Procedure
Step 1 On the U2000, check whether the alarms of higher levels such as R_LOS and FEC_LOF exist at the local station. If yes, clear these alarms and then check whether the OTU_AIS alarm is cleared. Step 2 If the OTU_AIS alarm persists, locate the fault in the upstream direction. Determine the station (marked as an FR station) which is the first to receive the OTU_AIS alarm. Then follow Step 1 to troubleshoot the FR station. Step 3 If the OTU_AIS alarm still persists, troubleshoot the upstream station (marked as a PR station) of the FR station. Check whether any alarms of higher levels exist in the receive part of the PR station. If yes, clear the alarms. Step 4 If the OTU_AIS alarm persists, use fibers to perform loopbacks for the service output parts of the upstream stations from the FR station. Determine the station (marked as an FL station) where the OTU_AIS alarm is generated for the first time after the fiber loopbacks. Perform the following steps to troubleshoot the FL station. Skip this step if the services cannot be interrupted.
4 Alarm Processing
In this case, directly replace the boards in the receive part of the FR station and the boards in the service output part of the PR station. 1. 2. 3. Check the configuration at the FL station. If any fault exists, correct the connection and configuration. If the OTU_AIS alarm persists, replace the line boards at the FL station. If the OTU_AIS alarm still persists, replace the cross-connect and timing board at the FL station.
----End
Related Information
None
4.194 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame alignment signal (FAS) is abnormal.
Attribute
Parameters
None

When the OTU_LOF alarm is generated, the FEC function is disabled. At the same time, the services are interrupted.
Possible Causes
The possible causes of the OTU_LOF alarm are as follows: l l l The fiber or the optical power is faulty. The board hardware is faulty. The services that are transmitted from the opposite station are faulty.
Procedure
Step 1 View the OTU_LOF alarm on the U2000 to determine the relevant board. Step 2 View the receive optical power of the board on the U2000. If the receive optical power is excessively low, clean the fiber header and the connector. If the receive optical power is
4 Alarm Processing
excessively high, provide more optical attenuators. After making sure that the receive optical power is proper, check whether the OTU_LOF alarm is cleared. Step 3 If the OTU_LOF alarm persists, check the transmit optical power at the opposite station. If the transmit optical power is excessively low, replace the board at the opposite station. Step 4 If the alarm persists, check whether the clocks on the local NE and opposite NE are synchronous with those on the network. If not, set the clock tracing function, and then check whether the OTU_LOF alarm is cleared. Step 5 If the alarm still persists, check whether the fiber works well. If yes, replace the board that generates the alarm. Step 6 If the alarm persists, replace the cross-connect and timing board at the local station. Step 7 If the alarm persists, replace the line board at the opposite station. Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite station. ----End
Related Information
None
4.195 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the multiframe alignment signal (MFAS) is abnormal.
Attribute
Parameters
None

When the OTU_LOM alarm is generated, the multiframe is lost and the services are interrupted.
Possible Causes
The possible causes of the OTU_LOM alarm are as follows: l l
Issue 02 (2011-10-31)
The expected consecutive frames are not received. Too many bit errors exist during the transmission.
4 Alarm Processing
l l
The transmit part of the opposite station is faulty. The receive direction of this board is faulty.
Procedure
Step 1 View the OTU_LOM alarm on the U2000 to determine the relevant board. Step 2 View the receive optical power of the board on the U2000. If the receive optical power is excessively low, clean the fiber header and the connector. If the receive optical power is excessively high, provide more optical attenuators. After making sure that the receive optical power is proper, check whether the OTU_LOM alarm is cleared. Step 3 If the alarm persists, check the transmit optical power at the opposite station. If the transmit optical power is excessively low, replace the board at the opposite station. Step 4 If the alarm persists, check whether the clocks on the local NE and opposite NE are synchronous with those on the network. If not, set the clock tracing function, and then check whether the OTU_LOM alarm is cleared. Step 5 If the alarm persists, check whether the fiber works well. If yes, replace the board that generates the alarm. Step 6 If the OTU_LOM alarm still persists, replace the source board of the OUT path (excluding the stations that transparently transmit the ODU path). ----End
Related Information
None
4.196 OTUk_AIS
Description
The OTUk_AIS is an OTUk alarm indication. An AIS signal travels downstream, which indicates that a signal failure is detected in the upstream. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Parameters
None
4 Alarm Processing

The services at the optical port are unavailable.
Possible Causes
l l Signals input from the client side contain the ODUk_PM_AIS or OTUk_AIS signals. The upstream station has loopback or cross-connection or the FEC type configuration is incorrect.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 If the alarm is reported from the client side, check the equipment on the client side. Step 3 Use the U2000 to query whether the upstream station has any loopback. If yes, release the loopback. Step 4 Check whether the configuration of the cross-connection and FEC type is correct at the upstream station. If not so, correct the configuration. ----End
Related Information
ITU-T G.709
4.197 OTUk_BDI
Description
The OTUk_BDI indicates an OTUk backward defect. This alarm occurs when the SM section detects a signal failure and the value of the BDI byte is 1. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Parameters
None
4 Alarm Processing

The services at the optical port are unavailable.
Possible Causes
l l Signals input from the client side contain the OTUk_BDI alarm. The corresponding OTU board at the downstream station receives the LOF, LOM, OTUk_AIS, or OTUk_TIM, OTUk_SSF alarm.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there is, handle the alarm with higher severity. Step 2 Query whether the alarm is reported from the client side or the WDM side. l l If the alarm is reported from the client side, check the equipment on the client side. If the alarm is reported from the WDM side, check whether the corresponding OTU board at the downstream station receives the LOF, LOM, OTUk_AIS, OTUk_TIM, or OTUk_SSF alarm by using the U2000. If yes, handle the corresponding alarm at the downstream station.
----End
Related Information
ITU-T G.709
4.198 OTUk_DEG
Description
The OTUk_DEG is an alarm indicating that the OTUk signal is degraded. When the BIP8 detection is in burst mode, this alarm is generated if the signal degradation or bit error count exceeds the threshold. In addition, when the BIP8 detection in poisson mode, this alarm is generated if the signal degradation exceeds the threshold. k indicates the level of rate. l l l For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Issue 02 (2011-10-31)
620
4 Alarm Processing
Parameters
None

If the alarm is generated, the services at the optical port have bit errors, which make the service signals invalid or even unusable.
Possible Causes
l l The optical port at the local end is faulty. The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. For optical power specifications of specific boards, see the Product Description. If the optical power is not within the normal range, see the handing procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms for troubleshooting. Step 2 If the alarm persists, check whether the fiber meets the following requirements: l The bending radius is not less than 40 mm. l The optical interface connector is well inserted. l The fiber connector is clean. l The cable is intact. If the preceding requirements are not met, clean the fiber connector or replace the fiber. For details, see the Supporting Tasks. Step 3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, see the Supporting Tasks. ----End
Related Information
ITU-T G.709
4.199 OTUk_EXC
Description
The OTUk_EXC is an alarm indicating that the OTUk bit errors cross the threshold. This alarm is generated when the BIP8 detection is in poisson mode and bit error count exceeds the threshold. k indicates the level of rate. l l l
Issue 02 (2011-10-31)
For OptiX OSN 8800, its value is 1, 2, 3 For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
4 Alarm Processing
Attribute
Parameters
None

Possible Causes
l l The attenuation of the received signals is rather large, and the fiber of the transmission line is abnormal. The receive part of the local station is faulty.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. If the receive optical power of the board at the local station is excessively low, clear the alarm according to the handling procedure of the IN_PWR_LOW alarm. Step 2 If the alarm persists, replace the faulty board at the local station. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.200 OTUk_LOM
Description
The OTUk_LOM is an alarm indicating that the multiframe alignment signal (MFAS) is abnormal. This alarm occurs when the multiframe locating is out of multiframe (OOM) in three consecutive milliseconds. k indicates the level of rate. l l l
Issue 02 (2011-10-31)
For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
4 Alarm Processing
Attribute
Parameters
None

Possible Causes
l l l The FEC type is incorrectly configured. The bit errors in the received signals of the OTU board at the local station are excessive. The board at the local station is faulty.
Procedure
Step 1 Query the FEC type of the board set on the U2000 to check whether it is consistent with the FEC type of the board. For specific error correction types, see the Hardware Description. If they are not consistent, modify the setting on the U2000 to ensure the consistency. Step 2 Query the performance value of the BIP8 bit errors in the received signals of the board at the local station through the U2000. If the BIP8 bit errors are excessive, see the handling procedure of the OTUk_EXC or OTUk_DEG for troubleshooting. Step 3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.201 OTUk_TIM
Description
The OTUk_TIM is an alarm indicating OTUk trail trace identifier (TTI) mismatch. This alarm occurs during the control process when the TTI at the opposite end mismatches that at the local end when the TIM detection is enabled. The system compares the access point identifiers (API) in the input signals and the expected API. For the set TIM detection mode, the network architecture can be classified into the following three types:
4 Alarm Processing
l l l
For the point-to-point topology, only the source access point identifiers (SAPI) is compared for the sink of trail termination. For the point-to-multipoint topology, only the SAPI is compared for the sink of trail termination. For the multipoint-to-multipoint topology, only the destination access point identifiers (DAPI) is compared for the sink of trail termination.
k indicates the level of rate. l l l For OptiX OSN 8800, its value is 1, 2, 3. For OptiX OSN 6800, its value is 1, 2, 3 or 5G. For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Parameters
None

If the alarm is generated, the signal quality of the services at the optical port is degraded. Hence, the service signals may be unavailable.
Possible Causes
l l l l The networking architecture and the TIM detection mode to be configured are not consistent. The TTI sent at the opposite end is not consistent with the TTI to be received at the local end. The fiber connection is incorrect. The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the NMU2000. Select the suitable topology for the local end on the U2000 interface according to networking architecture. If the topology is point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the sink of trail termination. Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be received at the local end through the U2000. If they are not consistent, query the received TTI on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to be the same as these of the received TTI.
4 Alarm Processing
Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber. Step 4 Check whether the cross-connection configuration is correct. If not, correctly configure the cross-connection. ----End
Related Information
ITU-T G.709
4.202 OUT_PWR_LOW
Description
The OUT_PWR_LOW is an alarm indicating that the output optical power is excessively low. The output optical power of the laser is excessively low. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

The output optical power of the laser is excessively low, which influences the normal transmission of services.
Possible Causes
l l l The input optical power is excessively low. The laser is aged. The board is faulty.
Procedure
Step 1 Check whether the input optical power of the interface of the board at the local station is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. l If it is not within the normal range, add a suitable attenuation to adjust the input optical power in the normal range.
Issue 02 (2011-10-31)
4 Alarm Processing
If it is within the normal range, replace the faulty optical module. For details, see the Parts Replacement.
Related Information
None
4.203 OWSP_PS
Description
The OWSP_PS is an alarm indicating the OWSP protection switching. This alarm occurs when the OWSP protection group actuates switching in which the current channel switches to the protection channel from the working channel.
Attribute
Alarm Severity Major Alarm Type Communication Alarm
Parameters
None

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

4 Alarm Processing
2.
If the external switching operation is unnecessary, issue an external command to switch the current channel to the working channel, thus clearing the alarm. Query whether the related boards for configuring the protection group have alarms relevant to the services, such as R_LOC, R_LOS. If yes, handle the alarms by referring to the corresponding alarm handling procedures. If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
Step 2 If the alarm is generated due to the automatic switching of the protection group, 1.
2.
----End
Related Information
The optical wavelength shared protection applies to ring networks with distributed services. It occupies two wavelengths to provide protection for one channel of distributed services among all stations. For details, see "Optical Wavelength Shared Protection (DCP board)" in the Feature Description.
4.204 OWSP_STA_INDI
Description
The OWSP_STA_INDI is an alarm indicating the state of the optical wave share protection group. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
Attribute
Alarm Severity Minor Alarm Type Communication Alarm
Parameters
Issue 02 (2011-10-31)
627
4 Alarm Processing
Description Indicate the west switching request. For example: l 0x16: LP l 0X15: SF_P l 0x13: SF_R l 0x12: SF_RP l 0x11: SF_RW l 0x10: SF_W l 0x0E: FS_R l 0x0D: SD_P l 0x0B: SD_R l 0x0A: SD_W l 0x08: MS_R l 0x06: WTR_R l 0x03: EXER_R l 0x00: NR
Parameters 2
Indicate the east switching request. For example: l 0x16: LP l 0X15: SF_P l 0x13: SF_R l 0x12: SF_RP l 0x11: SF_RW l 0x10: SF_W l 0x0E: FS_R l 0x0D: SD_P l 0x0B: SD_R l 0x0A: SD_W l 0x08: MS_R l 0x06: WTR_R l 0x03: EXER_R l 0x00: NR

l l When the OWSP group performs switching, services are transiently interrupted. When this alarm is reported, the working or protection channel of the OWSP protection group may have faulty services that need to be restored.
Issue 02 (2011-10-31)
628
4 Alarm Processing
Possible Causes
l l l The user issues an external switching command such as the forced switching, manual switching, or locked switching. The services of the working or protection channel of the OWSP protection group are faulty. The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching, or locked switching, check whether the external switching is necessary, 1. 2. If the external switching is necessary, ignore the alarm. If the external switching is unnecessary, issue a switching clearing command to clear the external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection group, do as follows: 1. Query whether the related boards for configuring the protection group have alarms, such as R_LOC, R_LOS. If yes, handle the alarms according to the corresponding alarm handling procedures.
Related Information
The optical wavelength shared protection applies to ring networks with distributed services. It occupies two wavelengths to provide protection for one channel of distributed services among all stations. For details, see "Optical Wavelength Shared Protection (DCP board)" in the Feature Description.
4.205 PATCH_ACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating that the activated state of the patch package is excessively long. The alarm is generated when the activated state of the patch package exceeds the threshold.
Attribute
Parameters
None
4 Alarm Processing

The activation of the patch is not in the stable state. If the board is reset in this case, the patch does not take effect after the system restarts, and the patch is automatically restored to the deactivated state. The functions of the patch are not available or the bug corrected by the patch appears again.
Possible Causes
The activated state of the patch package is excessively long.
Procedure
Step 1 If the patch file is confirmed to be correct, run the patch file through the U2000 after the end of the observation. Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the U2000. ----End
Related Information
None
4.206 PATCH_DEACT_TIMEOUT
Description
The PATCH_DEACT_TIMEOUT is an alarm indicating that the deactivated state of the patch package is excessively long. The alarm is generated when the deactivated state of the patch package exceeds the threshold.
Attribute
Parameters
None

The deactivated state indicates that the patch is loaded but the patch is not running. If the board is reset in this case, the patch is automatically restored to the idle state after the system restarts. The functions of the patch are not available or the bug corrected by the patch appears again.
4 Alarm Processing
Possible Causes
The deactivated state of the patch package exceeds the threshold.
Procedure
Step 1 If the patch file is confirmed to be correct, activate the patch file through the U2000. Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the U2000. ----End
Related Information
None
4.207 PATCH_PKGERR
Description
The PATCH_PKGERR is an alarm indicating a patch package file error.
Attribute
Alarm Severity Minor Alarm Type Process
Parameters
None

Package loading management of certain boards may be unavailable if this alarm is generated.
Possible Causes
The patch package of certain boards is lost
Procedure
Step 1 Contact Huawei engineers to regenerate the patch package file. ----End
Related Information
None
4 Alarm Processing
4.208 PM_BDI
Description
The PM_BDI is an alarm indicating PM back defect in the PM overhead at the optical demultiplexer unit (ODU) layer. This alarm indicates that ODUs are provided at the remote end or severe alarms occur at an upper layer.
Attribute
Parameters
None

The PM_BDI alarm is generated at the ODU termination station mapping the services in the transmit direction. The services in the receive direction are not affected.
Possible Causes
The possible causes of the PM_BDI alarm are as follows: l l l Certain alarms occur at the remote ODU termination station. The transmit unit at the local end is faulty. The receive unit at the remote end is faulty.
Procedure
Step 1 Check whether any other higher-level ODU alarm is generated at the remote ODU termination station. If yes, take priority to clear it, and then check whether the PM_BDI alarm is cleared. Step 2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the PM_BDI alarm is generated, check and modify the configuration.
CAUTION
The loopback causes service interruption. Step 3 If the alarm persists, replace the board at the local station.
4 Alarm Processing
Step 4 If the alarm at the remote end persists and the inloop is normally performed at the local optical station, replace the board at the remote end. ----End
Related Information
None
4.209 PM_BEI
Description
The PM_BEI is an alarm indicating a PM back error in the PM overhead at the optical demultiplexer unit (ODU) layer. This alarm indicates that PM-BIP check bit errors occur at the remote end.
Attribute
Parameters
None

performance When the PM_BEI alarm is generated, PM-BIP bit errors occur at the ODU termination station, but the FEC function and are not affected at the local station.
Possible Causes
The possible causes of the PM_BEI alarm are as follows: l l l Certain bit errors occur at the remote ODU termination station. The transmit unit at the local end is faulty. The receive unit at the remote end is faulty.
Procedure
Step 1 Check whether any bit error occurs at the ODU termination station. After clearing the bit error, check whether the PM_BEI alarm is cleared. Step 2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the PM_BEI alarm is generated, check and modify the configuration.
4 Alarm Processing
CAUTION
The loopback causes service interruption. Step 3 If the alarm persists, replace the board at the local station. Step 4 If the alarm at the remote end persists and the inloop is normally performed at the local optical station, replace the board at the remote end. ----End
Related Information
None
4.210 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the ODU PM section exceeds the threshold.
Attribute
Parameters
None

When the PM_BIP8_OVER alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the PM_BIP8_OVER alarm are as follows: l l l l l
Issue 02 (2011-10-31)
The received signals are heavily attenuated. The fiber connector is dirty. The connector is incorrectly connected. The receive unit at the local station is faulty. The transmit unit at the opposite station is faulty.
4 Alarm Processing
Procedure
Step 1 Check whether any higher-level alarm, such as R_LOS or R_LOF, is detected on the U2000. If yes, take priority to clear it, and then check whether the PM_BIP8_OVER alarm is cleared. Step 2 Check whether the receive optical power of the board that reports the alarm is within the normal range. If yes, go to Step 9. Step 3 Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared. Step 4 Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 5 Check whether the transmit optical power at the opposite station is within the normal range. If not, replace the line board. Step 6 If the transmit optical power is within the normal range, clean the fiber connector at the opposite station, and then check whether the alarm is cleared. Step 7 Check whether the flange is correctly connected to the optical attenuator at the opposite station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm is cleared. Step 9 Replace the line board that reports the alarm at the local station, and then check whether the alarm is cleared. Step 10 Replace the cross-connect and timing board at the local station, and then check whether the alarm is cleared. Step 11 Replace the line board at the opposite station, and then check whether the alarm is cleared. Step 12 Replace the cross-connect and timing board at the opposite station, and then check whether the alarm is cleared. ----End
Related Information
None
4.211 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the PM BIP error signal is degraded in the ODU PM section.
Issue 02 (2011-10-31)
635
4 Alarm Processing
Attribute
Parameters
None

When the PM_BIP8_SD alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the PM_BIP8_SD alarm are as follows: l l l l l The received signals are heavily attenuated. The fiber connector is dirty. The connector is incorrectly connected. The receive unit at the local station is faulty. The transmit unit at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as R_LOS or R_LOF, is detected on the U2000. If yes, take priority to clear it, and then check whether the PM_BIP8_SD alarm is cleared. Step 2 Check whether the receive optical power of the board that reports the alarm is within the normal range. If yes, go to Step 9. Step 3 Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared. Step 4 Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 5 Check whether the transmit optical power at the opposite station is within the normal range. If not, replace the line board. Step 6 If the transmit optical power is within the normal range, clean the fiber connector at the opposite station, and then check whether the alarm is cleared. Step 7 Check whether the flange is correctly connected to the optical attenuator at the opposite station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm is cleared.
4 Alarm Processing
Step 9 Replace the line board that reports the alarm at the local station, and then check whether the alarm is cleared. Step 10 Replace the cross-connect and timing board at the local station, and then check whether the alarm is cleared. Step 11 Replace the line board at the opposite station, and then check whether the alarm is cleared. Step 12 Replace the cross-connect and timing board at the opposite station, and then check whether the alarm is cleared. ----End
Related Information
None
4.212 PM_TIM
Description
The PM_TIM is an alarm indicating that the monitoring trail trace identifier (TTI) mismatches in the ODU PM overhead.
Attribute
Parameters
None

When the PM_TIM alarm is generated, the FEC function and services are not affected.
Possible Causes
The possible cause of the PM_TIM alarm is as follows: The PM_TTI byte to be received at the local station is incorrectly set.
Procedure
Step 1 Check whether the SM-TTI byte to be received at the board is consistent with the received SMTTI byte. If not, modify it and make sure it is consistent with the received SM-TTI byte. ----End
4 Alarm Processing
Related Information
None
4.213 PORTSWITCH_FAIL
Description
The PORTSWITCH_FAIL is an alarm indicating an optical switch switching failure. This alarm occurs when the board detects that the optical switch inside the board fails to switch. Reported from the WDM side or client side: NA
Attribute
Parameters
None

When the MCA board reports this alarm, the spectrum analysis data at optical ports cannot be queried.
Possible Causes
Procedure
Step 1 Perform cold reset on the faulty board by using the U2000 or remove the faulty board and insert it again. For details, see the Supporting Tasks. Step 2 After the board is reset, perform the spectrum analysis on the MCA again by sing the U2000. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.214 POWER_ABNORMAL
4 Alarm Processing
Description
The POWER_ABNORMAL is an alarm indicating a power supply failure. This alarm occurs when the power supply of a board becomes abnormal.
Attribute
Parameters
Parameter 1 and Parameter 2 Each bit indicates whether the alarm is generated in the corresponding voltage. Bit 1 indicates that the alarm is generated, and bit 0 indicates that no alarm is generated.

When the POWER_ABNORMAL alarm is generated, the power supply functions abnormally, and the board may not be able to function normally.
Possible Causes
l l l Cause 1: The input power of the PIU is abnormal. Cause 2: The jumper cap of the SCC is not configured. Cause 3: The power module on the board is faulty.
Procedure
l l Query current alarms on the U2000. Then, determine the board that reports the alarm. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The input power of the PIU is abnormal. 1. 2. l Check the board alarm indicator to see whether the power input is normal. For the description of the alarm indicators on the board, see the Hardware Description. If not, feed the NE power again or replace the DC PDU. For operations of accessing the power supply, see the Installation Guide.
NOTE
Cause 2: The jumper cap of the SCC is not configured.

The POWER_ABNORMAL alarm is reported when the jumper used to set the used input voltage of the SCC is configured incorrectly.
Issue 02 (2011-10-31)
639
4 Alarm Processing
1.
Contact the local representative office of Huawei, and then check whether the jumper of the SCC is correct. If not, adjust the jumper. For details on the jumper setting of each SCC, see the Hardware Description. Check whether the alarm is cleared after you perform cold reset on the board. For the operations that are performed by using the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For operations of reseating a board, see the Installation Guide.
Cause 3: The power module on the board is faulty. 1.
CAUTION
If the services that pass the board are not configured with protection, the services are interrupted after you perform cold reset on the board. 2. ----End If the alarm persists, replace the board that reports the alarm. For details, see the Parts Replacement.
Related Information
None
4.215 POWER_DIFF_OVER
Description
The POWER_DIFF_OVER is an alarm indicating that the power difference between the active and standby optical supervisory channels (OSCs) crosses the threshold.
Attribute
Parameters
None

The switching of the active and standby channels is affected. As a result, the quality of the received services is affected.
Issue 02 (2011-10-31)
640
4 Alarm Processing
Possible Causes
l During transport, the optical power of signals is excessively attenuated or the board at the local end is added with an over-large optical attenuator. Hence, the optical power difference between the active and standby OSCs at the receive end is excessively large. The optical power difference of signals in the active and standby channels when the board at the opposite end transmits signals is excessively large. The detection circuit of the board at the local end is faulty.
l l
Procedure
Step 1 Replace with a suitable optical attenuator. Adjust the optical power in the active and standby channels of the board at the local station to ensure that the power difference is within 5 dB. Step 2 If the alarm persists, the detection circuit of the board at the local station is faulty. Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.216 PRBS_LSS
Description
The PRBS_LSS is an alarm indicating loss of the pseudo-random binary sequence (PRBS) signal. The alarm is generated when the board, on which the PRBS bit error test is performed, does not receive the PRBS signals from the local board.
Attribute
Parameters
None

The PRBS test services on the board are interrupted.
Possible Causes
l l
Issue 02 (2011-10-31)
Cause 1: The link is abnormal. Hence, the board, on which the PRBS bit error test is performed, does not receive the PRBS signals from the local board. Cause 2: The board is faulty, or the line is degraded.
4 Alarm Processing
Procedure
Step 1 Perform a self-loop by connecting the transmit end to the receive end of the PRBS signals on the local board. l l If the alarm is cleared, it indicates that the board is normal. See Step 2 to check the link. If the alarm persists, it indicates that the board is faulty. Replace the board. For details, see the Parts Replacement.
Step 2 Check the link and make sure that the link under the PRBS test is a loop. If the alarm persists, perform a loopback on each point of the link. Find out the abnormal point on the link, and repair or replace the link. ----End
Related Information
None
4.217 PUM_BCM_ALM
Description
The PUM_BCM_ALM is an alarm indicating that the bias current of the pump laser crosses the threshold. This alarm occurs when the pump laser bias current of the optical amplifier unit crosses the threshold.
Attribute
Parameters
Parameter Parameter 1 Description Indicates the threshold crossing type. The value is always 0x01.

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure is taken, however, the output optical power of the board is affected in a period of time. This affects the services
Possible Causes
l l
Issue 02 (2011-10-31)
Excessively high or excessively low ambient temperature affects the laser. The board is faulty.
4 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is normal. If not, adjust the ambient temperature of the equipment to a proper degree. Step 2 If the alarm persists, perform a warm reset on the faulty board on the U2000. Step 3 If the alarm persists, you can reseat the faulty board if it does not affect the services. Step 4 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.218 PUM_TEM_ALM
Description
The PUM_TEM_ALM is an alarm indicating that the working temperature of the pump laser exceeds the threshold. This alarm occurs when the operating temperature of the pump laser on the optical amplifier unit crosses the threshold.
Attribute
Parameters
Parameter Description Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure is taken, however, the output optical power of the board is affected in a period of time. This affects the services.
Possible Causes
l l l
Issue 02 (2011-10-31)
The ambient temperature is excessively high or excessively low. The cooling system of the pump laser is damaged. The pump laser has excessive current.
4 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is normal. If not, improve it. Step 2 If the alarm persists, perform a warm reset on the faulty board through the U2000. Step 3 If the alarm persists, you can reseat the faulty board if it does not affect services. Step 4 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.219 R_LOC
See the alarm page according to the type of the board that reports the alarm. Table 4-4 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm Page Link 4.219.1 R_LOC (OCS) 4.219.2 R_LOC (OTN)
4.219.1 R_LOC (OCS)

Description
The R_LOC (OCS) is an alarm indicating loss of the clock. This alarm is reported if the line board fails to extract clock signal from the line signal.
Attribute
Parameters
None
4 Alarm Processing

When the R_LOC alarm is generated, the line board fails to extract the clock from the received optical signals. Consequently, the services are interrupted.
Possible Causes
The possible causes of the R_LOC alarm are as follows: l l The clock extraction module on the line board is faulty. The cross-connect and timing board at the opposite station is faulty or is out of position.
Procedure
Step 1 Perform cold reset on the line board that generates the alarm at the local station. Then check whether the R_LOC alarm is cleared. Step 2 If the alarm persists, the clock extraction module on the line board may be faulty. In this case, replace the line board, and then check whether the R_LOC alarm is cleared. Step 3 If the alarm persists, check whether the cross-connect and timing board at the opposite station is faulty. If yes, replace the cross-connect and timing board, and then check whether the R_LOC alarm is cleared. ----End
Related Information
None
4.219.2 R_LOC (OTN)

Description
The R_LOC is an alarm indicating loss of the clock on the receive line. This alarm occurs when the clock signal fails to be extracted from the received signals. Reported from the WDM side or client side: WDM side, client side
Attribute
Parameters
None

Services at this port are interrupted.
4 Alarm Processing
Possible Causes
l l l The link is abnormal and the board cannot normally extract clock signals. The setting of the board clock tracing is incorrect. The board is faulty.
Procedure
Step 1 Perform a self-loop on the board. Then, check whether the physical link is normal. If there is any abnormity, such as OTUk_LOF, remove the fault. Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the entire network planning. Adjust the board clock setting if it is incorrect. Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.220 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is a critical alarm of the alarm input.
Attribute
Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input interface of the EFI1 board changes. For the OptiX OSN 6800, the status of the external equipment connected to the alarm input interface of the EFI board changes. For the OptiX OSN 3800, the status of the external equipment connected to the alarm input interface of the AUX board changes.
Possible Causes
For the OptiX OSN 8800,
4 Alarm Processing
l l
The status of the alarm input of the EFI1 board changes. The alarm input interface of the EFI1 board reports the alarm by default. The alarm is reported in the default state.
For the OptiX OSN 6800, l l The status of the alarm input of the EFI board changes. The alarm input interface of the EFI board reports the alarm by default. The alarm is reported in the default state.
For the OptiX OSN 3800, l l The status of the alarm input of the AUX board changes. The alarm input interface of the AUX board reports the alarm by default. The alarm is reported in the default state.
Procedure
Step 1 For the OptiX OSN 8800, Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI1 board changes. If that is the case, remove the fault of the external equipment. Step 2 For the OptiX OSN 6800, Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI board changes. If that is the case, remove the fault of the external equipment. Step 3 For the OptiX OSN 3800, Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the AUX board changes. If that is the case, remove the fault of the external equipment. Step 4 If no external equipment is connected to the alarm input interface, set the input interface to Unused and the alarm is cleared. ----End
Related Information
None
4.221 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is a warning alarm of the alarm input.
Attribute
Issue 02 (2011-10-31)
647
4 Alarm Processing
Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input interface of the EFI1/EFI2 board changes For the OptiX OSN 6800, the status of the external equipment connected to the alarm input interface of the EFI board changes. For the OptiX OSN 3800, the status of the external equipment connected to the alarm input interface of the AUX board changes.
Possible Causes
l l l l l l The status of the alarm input of the EFI1 board changes. The alarm input interface of the EFI1 board reports the alarm by default. The alarm is reported in the default state. The status of the alarm input of the EFI board changes. The alarm input interface of the EFI board reports the alarm by default. The alarm is reported in the default state. The status of the alarm input of the AUX board changes. The alarm input interface of the AUX board reports the alarm by default. The alarm is reported in the default state.
Procedure
Step 1 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI1 board changes. If that is the case, remove the fault of the external equipment. Step 2 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI board changes. If that is the case, remove the fault of the external equipment. Step 3 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the AUX board changes. If that is the case, remove the fault of the external equipment. Step 4 If no external equipment is connected to the alarm input interface, set the input interface to Unused and the alarm is cleared. ----End
Related Information
None
Issue 02 (2011-10-31)
648
4 Alarm Processing
4.222 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is a major alarm of the alarm input.
Attribute
Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input interface of the EFI1 board changes. For the OptiX OSN 6800, the status of the external equipment connected to the alarm input interface of the EFI board changes. For the OptiX OSN 3800, the status of the external equipment connected to the alarm input interface of the AUX board changes.
Possible Causes
l l l l l l The status of the alarm input of the EFI1 board changes. The alarm input interface of the EFI1 board reports the alarm by default. The alarm is reported in the default state. The status of the alarm input of the EFI board changes. The alarm input interface of the EFI board reports the alarm by default. The alarm is reported in the default state. The status of the alarm input of the AUX board changes. The alarm input interface of the AUX board reports the alarm by default. The alarm is reported in the default state.
Procedure
Step 1 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI1 board changes. If that is the case, remove the fault of the external equipment. Step 2 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI board changes. If that is the case, remove the fault of the external equipment.
4 Alarm Processing
Step 3 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the AUX board changes. If that is the case, remove the fault of the external equipment. Step 4 If no external equipment is connected to the alarm input interface, set the input interface to Unused and the alarm is cleared. ----End
Related Information
None
4.223 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is a minor alarm of the alarm input.
Attribute
Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input interface of the EFI1board changes. For the OptiX OSN 6800, the status of the external equipment connected to the alarm input interface of the EFI board changes. For the OptiX OSN 3800, the status of the external equipment connected to the alarm input interface of the AUX board changes.
Possible Causes
l l l l l
Issue 02 (2011-10-31)
The status of the alarm input of the EFI1 board changes. The alarm input interface of the EFI1 board reports the alarm by default. The alarm is reported in the default state. The status of the alarm input of the EFI board changes. The alarm input interface of the EFI board reports the alarm by default. The alarm is reported in the default state. The status of the alarm input of the AUX board changes.
4 Alarm Processing
The alarm input interface of the AUX board reports the alarm by default. The alarm is reported in the default state.
Procedure
Step 1 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI1 board changes. If that is the case, remove the fault of the external equipment. Step 2 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the EFI board changes. If that is the case, remove the fault of the external equipment. Step 3 Check whether the status of the external equipment (for example, access control system) connected to the alarm input interface of the AUX board changes. If that is the case, remove the fault of the external equipment. Step 4 If no external equipment is connected to the alarm input interface, set the input interface to Unused and the alarm is cleared. ----End
Related Information
None
4.224 REM_SD
Description
The REM_SD is an alarm indicating that the remote signal is degraded. When the received signals on the client side of the board at the opposite station is degraded, the alarm signal is inserted. The alarm is generated when the client side of the board at the local station detects the signals. Reported from the WDM side or client side: Client side
Attribute
Parameters
None

The QoS of the service signals is affected. In a serious situation, the services are interrupted.
4 Alarm Processing
Possible Causes
l l The client side of the OTU at the opposite end has the B1_EXC alarm. The demultiplexed client signals on the WDM side of the OTU at the local end have the B1_EXC alarm.
Procedure
Step 1 Check whether the OTU at the opposite end has the B1_EXC alarm. If yes, see the procedure of handling B1_EXC to handle the alarm. Step 2 If the alarm persists, check whether demultiplexed client signals on the WDM side of the OTU at the local end have the B1_EXC alarm. If yes, see the procedure of handling B1_EXC to handle the alarm. ----End
Related Information
None
4.225 RL_CRITICAL_HI
Description
Critical high return loss alarm. This alarm is generated when the return loss is higher than the upper threshold of the return loss alarm.
Attribute
Parameters
None

This alarm is generated in case of a fiber connection error. When this alarm is generated, services may be interrupted.
Possible Causes
l l l l
Issue 02 (2011-10-31)
The fiber near the Raman board is broken. The fiber near the Raman board is over-bent or pressed. The connector of the fiber near the Raman board is unclean. The connector of the fiber near the Raman board is installed incorrectly.
4 Alarm Processing
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether the fiber near the Raman board is properly connected. If not, reconnect it. Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If yes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by means of splicing. Step 3 If the alarm still persists, check whether the end face of the fiber near the Raman board is clean. If not, clean it again and then connect the fiber properly. ----End
Related Information
None
4.226 RL_CRITICAL_LOW
Description
Critical low return loss alarm. This alarm is generated when the return loss is lower than the lower threshold of the return loss alarm.
Attribute
Parameters
None

This alarm is generated in case of a fiber connection error. When this alarm is generated, services may be interrupted.
Possible Causes
l l l l The fiber near the Raman board is broken. The fiber near the Raman board is over-bent or pressed. The connector of the fiber near the Raman board is unclean. The connector of the fiber near the Raman board is installed incorrectly.
Issue 02 (2011-10-31)
653
4 Alarm Processing
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether the fiber near the Raman board is properly connected. If not, reconnect it. Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If yes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by means of splicing. Step 3 If the alarm still persists, check whether the end face of the fiber near the Raman board is clean. If not, clean it again and then connect the fiber properly. ----End
Related Information
None
4.227 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that the regenerator section performance events cross the threshold. The alarm occurs when the performance module reports the threshold crossing of the performance events in the regenerator section
Attribute
Parameters
None

The line has bit errors, which decreases the QoS.
Possible Causes
l l l l
Issue 02 (2011-10-31)
The laser of the board at the opposite station is degraded. The input optical power of the board at the local station is excessively high or excessively low. The clock at the opposite station is degraded. The fiber is degraded.
4 Alarm Processing
Procedure
Step 1 Check whether the fiber is aged or has excessive attenuation. If that is the case, remove the fault of the fiber. Step 2 Query whether the board has the B1_EXC, B2_EXC, B1_SD, or B2_SD alarm by using the U2000. If that is the case, clear the alarm. Step 3 Check whether the input optical power of the board at the local station is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. l l If the optical power displayed on the U2000 is normal, the board may be faulty. Replace the faulty board. For details, see the Parts Replacement. If the optical power displayed on the U2000 is abnormal, adjust the input optical power to a value within the normal range.
Step 4 If the alarm persists, remove the fault of the board at the opposite station. ----End
Related Information
None
4.228 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the timing of the real time clock (RTC) fails.
Attribute
Parameters
None

When the alarm is reported, the system employs the soft timing. Hence, the timestamp precision of the system decreases.
Possible Causes
l l
Issue 02 (2011-10-31)
The clip of the RTC clock is damaged. The temperature of the board is excessively high.
4 Alarm Processing
Procedure
Step 1 Check whether the board temperature is normal. If it is abnormal, replace the fan. Step 2 If the alarm persists, replace the faulty SCC. For details, see the Parts Replacement. ----End
Related Information
RTC is also called NE timing.
4.229 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the S1 mode. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the ID of the priority table. Valid values are as follows: l 0x01: priority table of the system clock l 0x02: priority table of the first channel 2M phase-locked source l 0x03: priority table of the second channel 2M phase-locked source

The switching performs on the working clock source of the board, which influence the user services.
Possible Causes
l
Issue 02 (2011-10-31)
Cause 1: The fiber connection is faulty.

4 Alarm Processing
Cause 2: The upstream station generates the alarm.
Procedure
l Cause 1: The fiber connection is faulty. 1. 2. l Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details, see the Supporting Tasks. If the alarm persists, replace the faulty board. For details, see the Parts Replacement. If the alarm persists, check whether the S1_SYN_CHANGE alarm is generated at the upstream station. If yes, repeat steps to clear the S1_SYN_CHANGE alarm at the upstream station. The S1_SYN_CHANGE alarm at the local station is then automatically cleared.
Cause 2: The upstream station generates the alarm. 1.
----End
Related Information
4.230 SCC_LOC
Description
The SCC_LOC is an alarm indicating that the SCC losses the clock. The alarm occurs when the OSC board detects that the clock source sent by the SCC board is lost.
Attribute
Parameters
None

The NE is out of control and the OSC is interrupted.
Possible Causes
l l l The board is faulty. The SCC board is faulty. The alarm is generated during the cold reset of the SCC board. The alarm is automatically cleared after the cold reset is complete.
Issue 02 (2011-10-31)
4 Alarm Processing
Procedure
Step 1 Query the reset record of the SCC board. l l If the time when the alarm is cleared is consistent with the time that the SCC is reset, the alarm may be caused by resetting the SCC. There is no need to handle the alarm. If the time when the alarm is cleared is not consistent with the time that the SCC is reset, the board may be faulty. Replace the faulty board. For details, see the Parts Replacement.
Step 2 If the alarm persists, the SCC board may be faulty. Replace the faulty SCC board. For details, see the Parts Replacement. ----End
Related Information
None
4.231 SEC_RADIUS_FAIL
Description
Excessive failures in radius authentication. The SEC_RADIUS_FAIL is an alarm indicating that a large number of authentification failures occur on the NE within a short period.
Attribute
Parameters
None

User login fails.
Possible Causes
A large number of RADIUS authentication failures occur on the NE within a short period.
Procedure
Step 1 Check whether the user account expired. Step 2 Check whether the user password is changed or the user access policy is changed by the administrator. Step 3 Check whether an unauthorized user attempts to log in to the network device.
4 Alarm Processing
Step 4 Check whether the shared key between the GNAS and the radius server is correct. ----End
Related Information
None
4.232 SERVICE_TYPE_EXCEED_LICENSE
Description
The SERVICE_TYPE_EXCEED_LICENSE is an alarm indicating that the service type exceeds the license limit. The alarm indicates that the type of configured services exceeds the license limit.
Attribute
Alarm Severity Major Alarm Type Service
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the ID of the subrack, where the service type exceeds the license limit.

When the SERVICE_TYPE_EXCEED_LICENSE alarm is generated, neither the existing services nor the operation of the system is affected. The subrack where the alarm is generated, however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service type configured in the subrack exceeds the license limit.
Procedure
Step 1 According the alarm parameter, check whether the type of configured services in the subrack exceeds the license limit by using the U2000.
4 Alarm Processing
Step 2 If yes, assign a proper license. Step 3 If no proper license is available, purchase the license with a higher version from Huawei. ----End
Related Information
None
4.233 SERVICE_CAPACITY_EXCEED_LICENSE
Description
The SERVICE_CAPACITY_EXCEED_LICENSE is an alarm indicating that the service capacity exceeds the license limit. This alarm indicates that the service capacity configured in the subrack exceeds the license limit.
Attribute
Alarm Severity Major Alarm Type Service
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Description Parameter 1 Indicates the ID of the subrack, where the service capacity exceeds the license limit.

When the SERVICE_CAPACITY_EXCEED_LICENSE alarm is generated, neither the existing services nor the operation of the system is affected. The subrack where the alarm is generated, however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service capacity configured in the subrack exceeds the license limit.
Issue 02 (2011-10-31)
660
4 Alarm Processing
Procedure
Step 1 According to the alarm parameters, query the license capacity for the subrack where the alarm is generated. Then, select a proper license capacity to meet the service requirements of the subrack. Step 2 If no license with a proper capacity can be used, purchase the license with a proper capacity from Huawei. ----End
Related Information
None
4.234 SHELF_AREA_POWER_OVER
Description
The SHELF_AREA_POWER_OVER is an alarm indicating that the total optical power consumption of the subrack exceeds the threshold. This alarm is generated when the total power consumption of the boards in each partition of the subrack is higher than or equal to the power consumption threshold for each partition.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Parameter 2 Meaning Indicates the subrack ID. Indicates the number of the partition.

The total power consumption of the boards in each partition of the subrack exceeds the threshold. This puts the system in a very dangerous state. If the system runs in this state for a long time, the power supply unit of the subrack may work abnormally and a power failure may occur in the subrack.
4 Alarm Processing
Possible Causes
The total power consumption of the boards in each partition of the subrack is higher than or equal to the power consumption threshold for each partition.
Procedure
Step 1 Remove the board from the subrack. Wait until the alarm is cleared. ----End
Related Information
None
4.235 SPAN_LOSS_HIGH
Description
Line insertion loss is excessively high. The alarm is generated when the actual line insertion loss is higher than the reference value and the difference between the actual value and the reference value exceeds the alarm threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates the ALC link number.

If the line insertion loss is excessively high, service signals may be instable and BER may increase. Then, the alarm indicating excessively low path optical power may occur and the performance may be abnormal.
Possible Causes
l
Issue 02 (2011-10-31)
The line fiber is aged.

4 Alarm Processing
l l l l
The line insertion loss is increased. The alarm threshold is incorrect. The insertion loss of a board on the line is abnormal. The sampled reference value of the line attenuation is inappropriate.
Procedure
Step 1 Check whether the line fiber connections are abnormal and whether the fibers are aging. If the line fiber connections are abnormal or the fibers are aging, reconnect the fibers or replace the aging fibers. Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the attenuation to the normal value. Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively low, set the alarm threshold according to the planning of the live network. Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary, see the Parts Replacement. Step 5 If none of preceding problems occur, re-sample the reference value. ----End
Related Information
4.236 SPAN_LOSS_LOW
Description
Line insertion loss is excessive low. The alarm is generated when the actual line insertion loss is lower than the reference value and the difference between the actual value and the reference value exceeds the alarm threshold.
Attribute
Parameters
4 Alarm Processing
Name Parameter 1
Meaning Indicates the ALC link number.

When the line insertion loss is excessively low, an alarm indicating that the optical power of the channel is excessively high may be generated and the performance may be abnormal.
Possible Causes
l l Aging fibers on the line are replaced with new fibers, or the line insertion loss is decreased. The sampled reference value of the line attenuation is inappropriate.
Procedure
Step 1 Check whether the line fibers are aging. If the line fibers are new fibers, enable the ALC function and then sample the reference value again. Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the attenuation to the normal value. Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively low, set the alarm threshold according to the planning of the live network. Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary, see the Parts Replacement. Step 5 If none of preceding problems occur, re-sample the reference value. ----End
Related Information
4.237 SLAVE_WORKING
Description
The SLAVE_WORKING is an alarm indicating the working state of the protection board. If the protection cross-connect board is selected for the service bus of the service board, and if the slave clock is selected as the system clock, the SLAVE_WORKING alarm is reported.
Attribute
Issue 02 (2011-10-31)
664
4 Alarm Processing
Parameters
None

When the SLAVE_WORKING alarm is generated, the system is not affected. This alarm just indicates that the protection cross-connect board is selected for the service bus of the service board, and the slave clock is selected as the system clock.
Possible Causes
The possible causes of the SLAVE_WORKING alarm are as follows: l l l Cause 1: The active cross-connect and timing board is not in position. Cause 2: The active cross-connect and timing board is faulty. Cause 3: The service board is faulty.
Procedure
l l Query current alarms on the U2000. Determine the board that reports the alarm. For details, see Querying the Current Alarms in the Supporting Task. Cause 1: The active cross-connect and timing board is not in position. 1. Check whether the active cross-connect and timing board is loose. If yes, tighten the active cross-connect and timing board. For details, see the Installation Guide. Then, check whether the alarm is cleared. If the alarm persists, see Cause 2. Replace the active cross-connect and timing board. For details, see Parts Replacement. Then, check whether the alarm is cleared. If the alarm persists, see Cause 3. Perform cold reset on the service board that reports the alarm by using the U2000, or reseat the service board that reports the alarm. For the operations that are performed on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For operations of reseating a board, see the Installation Guide. Then, check whether the alarm is cleared. If the alarm persists, replace the board that reports the alarm. For details, see Parts Replacement.
2. l 1. 2. l 1.
Cause 2: The active cross-connect and timing board is faulty.
Cause 3: The service board is faulty.
2. ----End
Related Information
The working cross-connect board refers to the cross-connect board inserted in the slot of a smaller ID. The protection cross-connect board refers to the cross-connect board inserted in the slot of a larger ID.
4 Alarm Processing
4.238 SM_BDI
Description
The SM_BDI is an SM back defect indication at the optical transponder unit (OTU) layer. This alarm indicates that OTUs are provided at the remote end or severe alarms occur at an upper layer.
Attribute
Parameters
None

The SM_BDI alarm just indicates that certain alarms occur at the OTU termination station mapping the services in the transmit direction. The services in the receive direction are not affected.
Possible Causes
The possible causes of the SM_BDI alarm are as follows: l l l Certain alarms occur at the remote OTU termination station. The transmit unit at the local end is faulty. The receive unit at the remote end is faulty.
Procedure
Step 1 Check whether any other higher-level OTU alarm is generated at the remote OTU termination station. If yes, take priority to clear it, and then check whether the SM_BDI alarm is cleared. Step 2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the SM_BDI occurs, check and modify the configuration.
CAUTION
The loopback causes service interruption. Step 3 If the alarm persists, replace the board at the local station.
4 Alarm Processing
Step 4 If the alarm at the remote end persists and the inloop is normally performed at the local optical station, replace the board at the remote end. ----End
Related Information
None
4.239 SM_BEI
Description
The SM_BEI is an SM back error indication at the optical transponder unit (OTU) layer. This alarm indicates that SM-BIP errors occur at the remote end.
Attribute
Parameters
None

When the SM_BEI alarm is generated, SM_BIP errors occur at the remote OTU termination station, but the FEC function and performance are not affected at the local station.
Possible Causes
The possible causes of the SM_BEI alarm are as follows: l l l Certain bit errors occur at the remote OTU termination station. The transmit unit at the local end is faulty. The receive unit at the remote end is faulty.
Procedure
Step 1 Query the performance of the board at the remote OTU termination station, and clear the bit errors at the remote end. ----End
Related Information
None
4 Alarm Processing
4.240 SM_BIP8_OVER
Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the OTU SM section exceeds the threshold.
Attribute
Parameters
None

When the SM_BIP8_OVER alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the SM_BIP8_OVER alarm are as follows: l l l l l The received signals are heavily attenuated. The fiber connector is dirty. The connector is incorrectly connected. The receive unit at the local station is faulty. The transmit unit at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as R_LOS or R_LOF, is detected on the U2000. If yes, take priority to clear it, and then check whether the SM_BIP8_OVER alarm is cleared. Step 2 Check whether the receive optical power of the board that reports the alarm is within the normal range. If yes, go to Step 9. Step 3 Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared. Step 4 Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 5 Check whether the transmit optical power at the opposite station is within the normal range. If not, replace the line board.
4 Alarm Processing
Step 6 If the transmit optical power is within the normal range, clean the fiber connector at the opposite station, and then check whether the alarm is cleared. Step 7 Check whether the flange is correctly connected to the optical attenuator at the opposite station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 8 Check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the alarm is cleared. Step 9 Replace the line board that reports the alarm at the local station, and then check whether the alarm is cleared. Step 10 Replace the cross-connect and timing board at the local station, and then check whether the alarm is cleared. Step 11 Replace the line board at the opposite station, and then check whether the alarm is cleared. Step 12 Replace the cross-connect and timing board at the opposite station, and then check whether the alarm is cleared. ----End
Related Information
None
4.241 SM_BIP8_SD
Description
The SM_BIP8_SD is an alarm indicating that the SM BIP error signal is degraded in the OTU SM section.
Attribute
Parameters
None

When the SM_BIP8_SD alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the SM_BIP8_SD alarm are as follows:
4 Alarm Processing
l l l l l
The received signals are heavily attenuated. The fiber connector is dirty. The connector is incorrectly connected. The receive unit at the local station is faulty. The transmit unit at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as R_LOS or R_LOF, is detected on the U2000. If yes, take priority to clear it, and then check whether the SM_BIP8_SD alarm is cleared. Step 2 Check whether the receive optical power of the board that reports the alarm is within the normal range. If yes, go to Step 9. Step 3 Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared. Step 4 Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 5 Check whether the transmit optical power at the opposite station is within the normal range. If not, replace the line board. Step 6 If the transmit optical power is within the normal range, clean the fiber connector at the opposite station, and then check whether the alarm is cleared. Step 7 Check whether the flange is correctly connected to the optical attenuator at the opposite station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared. Step 8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm is cleared. Step 9 Replace the line board that reports the alarm at the local station, and then check whether the alarm is cleared. Step 10 Replace the cross-connect and timing board at the local station, and then check whether the alarm is cleared. Step 11 Replace the line board at the opposite station, and then check whether the alarm is cleared. Step 12 Replace the cross-connect and timing board at the opposite station, and then check whether the alarm is cleared. ----End
Related Information
None
4.242 SM_IAE
4 Alarm Processing
Description
The SM_IAE is alarm indicating an SM incoming alignment error (IAE) in the OTU SM section. When the ODU frame is synchronously mapped into the OTU frame, the IAE flag is set to true if the frame alignment errors occur. When the IAE errors are detected at the sink, the sub-frame alignment bit errors occur in the received services.
Attribute
Parameters
None

When the SM_IAE alarm is generated, the service availability is affected.
Possible Causes
The possible causes of the SM_IAE alarm are as follows: l l l The clock jitter event occurs in the transmit unit at the remote end (namely, the source of the OTU/ODU adaptation function). The frame offset on the board termination side of the remote end (namely, the source of the OTU/ODU adaptation function) is inaccurate. The board FEC processing chip at the remote end (namely, the source of the OTU/ODU adaptation function) is faulty.
Procedure
Step 1 Adjust the frame offset on the board system side of the remote end (namely, the source of the OTU/ODU adaptation function). Step 2 If the alarm persists, replace the board at the remote end (namely, the source of the OTU/ODU adaptation function). ----End
Related Information
None
4.243 SM_TIM
4 Alarm Processing
Description
The SM_TIM is an alarm indicating the section monitoring TTI mismatch in the OTU SM overhead.
Attribute
Parameters
None

When the SM_TIM alarm is generated, the FEC function and the services are not affected.
Possible Causes
The possible causes of the SM_TIM alarm are as follows: l l l The expected SM_TIM byte at the local end is incorrectly set. The value of the SM_TTI byte transmitted at the remote end is incorrectly configured. The fiber is incorrectly connected.
Procedure
Step 1 According to the service network, determine the expected setting of the SM_TTI byte in the relevant position. Step 2 Check whether the SM-TTI byte to be received at the board is consistent with the received SMTTI byte. If not, modify the incorrect SM-TTI byte to be received. Step 3 If the received SM-TTI byte is incorrect, check whether the fiber connection at the next local station is correct. If not, modify the connection. Step 4 Check whether the setting of the transmitted SM-TTI byte in the upstream services is correct. If not, modify the transmitted SM-TTI byte in the upstream services. ----End
Related Information
None
4.244 SNCP_FAIL
4 Alarm Processing
Description
The SNCP_FAIL is an alarm indicating an SNCP switching failure.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 and Parameter 2 Meaning Indicates the protection group ID.

When the SNCP switching fails, the services configured with SNCP are not protected, and the services in this SNCP group are interrupted.
Possible Causes
During the SNCP switching, the service grooming fails.
Procedure
Step 1 Reset the SCC board to re-configure all the services. ----End
Related Information
None
4.245 SO_SK_MISMATCH
Description
The SO_SK_MISMATCH is an alarm indicating that the number of timeslots bundled at the LCAS source is not consistent with the number of timeslots bundled at the LCAS sink. When the number of upstream (or downstream) timeslots is not consistent with the number of downstream (or upstream) timeslots for a VCTRUNK, the SO_SK_MISMATCH alarm is reported.
4 Alarm Processing
Attribute
Parameters
None

In the case of the SO_SK_MISMATCH alarm, services are not affected.
CAUTION
If the timeslots at the sink are added to other VCTRUNKs after the SO_SK_MISMATCH alarm is reported, services in the VCTRUNK are interrupted. Do not proceed with other operations before making sure that source and sink have the same number of timeslots.
Possible Causes
The possible cause of the SO_SK_MISMATCH is as follows: The LCAS source and LCAS sink have different number of configured timeslots.
NOTE
If timeslots except the last timeslot are deleted at the sink instead of at the source, the SO_SK_MISMATCH alarm is generated. If the last timeslot is deleted at the sink instead of at the source, the SO_SK_MISMATCH alarm is not generated.
Procedure
Step 1 View the SO_SK_MISMATCH alarm on the U2000, and then determine the number of the VCTRUNK where the SO_SK_MISMATCH alarm is generated. Step 2 On the U2000, check whether the number of upstream (or downstream) timeslots is consistent with the number of downstream (or upstream) timeslots bundled in the VCTRUNK. If not, make them consistent by adding or deleting some timeslots, and then check whether the SO_SK_MISMATCH alarm is cleared. ----End
Related Information
None
4 Alarm Processing
4.246 SPEED_OVER
Description
The SPEED_OVER is an alarm indicating that the data rate exceeds the set limit. The SPEED_OVER is an alarm indicating the mismatch between the rate of the monitored optical interface and the preset one. This alarm is generated when a board detects that the received rate mismatches the preset one. Reported from the WDM side or client side: Client side
Attribute
Parameters
None

When the SPEED_OVER alarm is generated, the received service rate mismatches the preset one. The board cannot carry the service and the service is interrupted.
Possible Causes
l l The set rate of the optical interface is incorrect. The board hardware is faulty.
Procedure
Step 1 Query the set rate and actual rate on the U2000, and determine whether the set rate is incorrect. Step 2 If the set rate is incorrect, set a correct one on the U2000. Step 3 If the alarm persists, check whether the input optical power is normal. If the input optical power is excessively high or excessively low, adjust it. Step 4 If the alarm persists, check whether the board chip is faulty, that is, whether there is a HARD_BAD or a HARD_ERR alarm at the local station. If yes, replace the relevant board. For details, see the Parts Replacement ----End
Related Information
None
4 Alarm Processing
4.247 STORM_CUR_QUENUM_OVER
Description
Alarm storm. Certain alarms on the SCC board may be lost when the alarm queue is full. This alarm indicates that the alarm module is in the alarm storm state.
Attribute
Alarm Severity Minor Alarm Type Service
Parameters
None

Certain alarms may be overwritten when there are excessive alarms. In this case, the alarm status of the NE is inappropriate.
Possible Causes
The alarm queue fails to contain all the alarms when there are excessive alarms.
Procedure
Step 1 Handle the existing alarms (except the STORM_CUR_QUENUM_OVER alarm). The STORM_CUR_QUENUM_OVER alarm clears when the number of the current alarms is equal to or below the STORM_CUR_QUENUM_OVER alarm threshold. ----End
Related Information
None
4.248 SUBRACK_COMM_PS
Description
SUBRACK_COMM_PS is an alarm indicating ETH2 interface status. This alarm indicates that the ETH2 interface on the master subrack is in working state when the master subrack is under inter-subrack communication protection.
4 Alarm Processing
Attribute
Parameters
None

An NE detects that the link between subracks is broken, but communication between subracks is protected.
Possible Causes
l Cause 1: The ETH2 interface on the master subrack is in working state when the master subrack is under inter-subrack communication protection.
Procedure
l Cause 1: The ETH2 interface on the master subrack is in working state when the master subrack is under inter-subrack communication protection. 1. If the ETH2 interface on the master subrack is in working state when the master subrack is under inter-subrack communication protection, the original working channel where the ETH1 interface is located is malfunctioning. Check for any LAN_LOC alarm on the NE. If the alarm is reported, restore the subrack connection according to the alarm processing method. After the connection is restored, intersubrack communication protection automatically switches the current working channel to the original working channel. In this manner, the ETH2 interface stops working and then the SUBRACK_COMM_PS alarm is cleared.
----End
Related Information
4.249 SUBRACK_ID_MISMATCH
Description
The SUBRACK_ID_MISMATCH is an alarm indicating mismatch of the subrack ID.
Issue 02 (2011-10-31)
677
4 Alarm Processing
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning Indicates mismatch of the logical subrack ID.

The DIP switch of the subrack ID mismatches with the subrack ID saved by the software, which leads to the abnormal communication between the boards.
Possible Causes
The DIP switch of the subrack ID is changed. The subrack ID detected by the NE software and board software is mismatched with the actual subrack ID.
Procedure
Step 1 Modify the DIP switch of the AUX to the subrack ID displayed in the statistics diode of the SCC or power off the subrack Step 2 Modify the DIP switch to "0", and thus the alarm is cleared. ----End
Related Information
4.250 SUBRACK_LOOP
Description
The SUBRACK_LOOP is an alarm indicating the loop of the subrack. The alarm occurs when the cascaded subracks form a closed loop.
4 Alarm Processing
Attribute
Parameters
None

The network storm occurs to the intra-subrack communication, which leads to unavailability of the intra-subrack communication.
Possible Causes
l l In the master/slave subrack mode, the internal network interfaces are connected in a closed loop. The AUX board is faulty, which leads to the abnormal communication.
Procedure
Step 1 Check the cable connection between the subracks to ensure that the subracks are connected in a chain manner. Step 2 Check whether the alarm is cleared. If the alarm persists, perform a warm reset or cold reset on the faulty board through the U2000. Step 3 If the alarm persists, replace the AUX board. ----End
Related Information
4.251 SUBRACK_TYPE_MISMATCH
Description
The alarm indicating that the subrack configured does not match the type of the physical subrack.
Attribute
Issue 02 (2011-10-31)
679
4 Alarm Processing
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Parameter 1 Meaning The ID of the subrack.

The alarm does not affect the existing services and the operation of the system. The subrack that generates this alarm, however, cannot be configured with services.
Possible Causes
l Cause 1: The subrack configured for the SCC does not match the type of the physical subrack.
Procedure
l Cause 1: The subrack configured for the SCC does not match the type of the physical subrack. 1. 2. 3. Determine whether the logical subrack or the physical subrack is incorrect according to the actual network. If the logical subrack is incorrect, delete the incorrect subrack from the U2000 and then configure a correct logical subrack that is consistent with the physical subrack. If the physical subrack is incorrect, replace the subrack with a correct one and then configure a correct subrack ID. For details on the operations, see Feature Description. If the alarm persists, contact Huawei for help.
4. ----End
Related Information
4.252 SUM_INPWR_HI
Description
The SUM_INPWR_HI is an alarm indicating that the input optical power is excessively high. The alarm occurs when the input optical power of the multiplexed signals exceeds the threshold. Reported from the WDM side or client side: NA
4 Alarm Processing
Attribute
Parameters
None

The optical modules of the boards at the local station and downstream station may be damaged. The services have bit errors, or are even interrupted.
Possible Causes
l The output optical power of the board at the upstream station is normal and the power of the received optical signals accessed by the board at the local station is excessively high. The proper attenuation is not added. The output optical power of the board at the upstream station or opposite station is excessively high. The board at the local station is faulty.
l l
Procedure
Step 1 Check whether the input optical power of the input interface of the board at the local station is within the normal range by using an optical power meter. For optical power specifications of specific boards, see the Product Description. If the power is not within the normal range, add proper attenuation by placing a fixed attenuator or a VOA. Step 2 If the alarm persists, check whether the output optical power of the board at the upstream stations is within the normal range by using the U2000. For optical power specifications of specific boards, see the Product Description. If the input optical power of the board at the local station is excessively high, handle the alarm according to the handling procedure of the IN_PWR_HIGH alarm. If the output optical power of the boards at the upstream stations is excessively high, respectively check whether the corresponding input and output optical power of each upstream station are within the normal range. l If the input and output optical power of the board at the upstream station are not within the normal range, adjust the input optical power to a value within the normal range. For optical power specifications of specific boards, see the Product Description. If the input optical power of the board at the upstream station is within the normal range but the output optical power is not, the board at the upstream station may be faulty. Replace the faulty board. For details, see the Parts Replacement.
Related Information
None
4 Alarm Processing
4.253 SW_SNCP_PS
Description
The SW_SNCP_PS is an alarm indicating the SW SNCP protection switching. This alarm occurs when the SW SNCP protection group actuates switching in which the current channel switches to the protection channel from the working channel.
Attribute
Parameters
None

When the SW SNCP protection group actuates switching, services are transiently interrupted. When this alarm is reported, the working channel of the SW SNCP protection group might have faulty services that need to be restored.
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or manual switching. Such a command makes the current channel of the SW SNCP protection group switch to the protection channel from the working channel. Hence, the alarm is reported. Cause 2: The services of the working channel of the SW SNCP protection group are faulty. The current channel automatically switches to the working channel and the alarm is reported.
Procedure
Step 2 If the alarm is generated due to the automatic switching of the protection group, 1. Query whether the related boards for configuring the protection group have alarms relevant to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, REM_SF, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC, or REM_SD. If yes, handle the alarms by referring to the corresponding alarm handling procedures.
Issue 02 (2011-10-31)
4 Alarm Processing
2.
If the alarm persists, check whether the attribute of the protection group is Revertive. If yes, the current channel automatically switches to the working channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
----End
Related Information
For details, see "SW SNCP Protection" in the Feature Description.
4.254 SW_SNCP_STA_INDI
Description
The SW_SNCP_STA_INDI is an alarm indicating the state of the Sub-Wavelength SNCP protection group. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
Attribute
Parameters

l When switching is performed in the SW SNCP group, the services are transiently interrupted.
Issue 02 (2011-10-31)
4 Alarm Processing
When the alarm is reported, the working or protection channel of the SW SNCP group may have faulty services that need to be restored.
Possible Causes
l l l The user issues an external switching command such as forced switching, manual switching or locked switching. The services of the working or protection channel of the SW SNCP group are faulty. The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection group, do as follows: 1. Query whether the related boards for configuring the protection group have the alarm such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, REM_SF, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC, or REM_SD. If that is the case, handle the alarms according to the corresponding handling procedure of the alarm to restore the services of the working or protection channel. If the alarm persists, check whether the attribute of the protection group is Revertive. If that is the case, the services are automatically switched to the working channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the alarm is cleared.
2.
Related Information
For details, see "SW SNCP Protection" in the Feature Description.
4.255 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the activation times out. During loading of the software package, the alarm occurs when the operation is not committed 120 seconds after activation operation.
Issue 02 (2011-10-31)
684
4 Alarm Processing
Attribute
Parameters
None

The services are not affected.
Possible Causes
The operation is not committed 120 seconds after activation operation during loading of the software package.
Procedure
Step 1 Commit the activation operation again. If the alarm persists, check whether the software version is correct. If the software version is incorrect, roll back the NE to the version before package loading, and select the required software package on the NMS to load the package again. ----End
Related Information
None
4.256 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic matching function is disabled.
NOTE
After the automatic matching function is enabled, when a board is added to an NE, the system automatically checks whether the board software matches the NE software. If not, the SCC board upgrades the board software of the new board.
Attribute
Issue 02 (2011-10-31)
685
4 Alarm Processing
Parameters
None

The SCC board cannot automatically update the software of the board that is newly inserted. If the software of the new board mismatches the NE software, certain functions of the NE may operate abnormally.
Possible Causes
The automatic matching switch is turned off.
Procedure
Step 1 If the alarm persists, contact Huawei engineers. ----End
Related Information
None
4.257 SWDL_BD_EXCLUDE
Description
The SWDL_BD_EXCLUDE is an alarm indicating that a board is excluded from software download during software package downloading. This alarm occurs when some board failed because of a failure to communicate with the SCC board or insufficient flash space.
Attribute
Parameters
None

After package loading, the software of the board excluded from software download mismatches with the NE software. This may result in damage to services. Hence, handle this alarm in time.
Possible Causes
l
Issue 02 (2011-10-31)
Cause 1: The board is offline.

4 Alarm Processing
l l l
Cause 2: The communication between the board and the SCC board is abnormal. Cause 3: The flash memory space on the board is insufficient. Cause 4: The board is repeatedle reset after activation because of a board software fault.
Procedure
Step 1 On the DC window of the U2000, view the information about the boards that are isolated during package loading. Step 2 Check whether the isolated boards are offline. If the isolated boards are offline, get them online. Step 3 Check whether any COMMUN_FAIL alarm is reported on the isolated boards. If the alarm is reported, handle the problem by referring to the alarm processing mehod. Step 4 Check whether the flash memory space on the boards is sufficient. If the space is insufficient, clean up the boards to get sufficient space. Step 5 Check whether the downloaded software matches with the isolated board version. If the software mismathches with the board verison, download the correct software again. Step 6 If the preceding items are checeked and the results are normal, select the isolated boards on the DC window, download software agagin, and then activate the software. Step 7 After handling all isolated boards, the SWDL_BD_EXCLUDE alarm is cleared when the board isolation is released. ----End
Related Information
None
4.258 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm indicating that the SCC board is changed. The system re-checks whether the board software of each board matches the NE software after the NE starts up upon a power failure, the SCC unit is replaced, or cold reset is performed on the SCC unit. The alarm occurs when the board software of a board mismatches the NE software. It indicates that the board software mismatches the NE software.
Attribute
Parameters
None
4 Alarm Processing

l l When the alarm occurs, the automatic matching function for package loading is disabled. The software version of the unit is inconsistent with that of the SCC board. Certain functions of the NE may operate abnormally.
Possible Causes
l l After the NE is powered off, a board is inserted and the software version of the board is inconsistent with that of the SCC board. The SCC board is replaced, and the software package of the new SCC is inconsistent with the software version of the board.
Procedure
Step 1 On the U2000, use a correct software package to perform the package loading on the board. ----End
Related Information
None
4.259 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating a commitment failure. During loading of the software package, the alarm occurs when the commitment operation fails.
Attribute
Parameters
None

The package loading fails and the upgrade of the software version fails.
Possible Causes
During the package loading, the dual-partition board fails in copying the new software from one partition to the other.

NOTE
4 Alarm Processing
The dual-partition board has two file systems. The two partitions are of mutual backups. In normal states, every file is saved in both partitions.
Procedure
Step 1 On the U2000, use a correct software package to perform the package loading on the board. ----End
Related Information
None
4.260 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the package loading is performed on the NE. This alarm occurs when the NE is performing the package loading. After the NE finishes the commitment operation, the alarm is cleared.
Attribute
Alarm Severity Warning Alarm Type Process alarm
Parameters
None

The working/protection backup function of the SCC board is disabled.
Possible Causes
The NE is performing the package loading operation.
Procedure
Step 1 The software package loading is still in process. Wait until the package loading is complete. Then, the alarm is cleared. ----End
Related Information
None
4 Alarm Processing
4.261 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that no matching board software is available. After an NE is loaded with a customized software package, when a board is inserted, the software for the board is not found in the customized software package. In this case, the board cannot be matched automatically and therefore the alarm occurs.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual requirement.
Attribute
Parameters
None

The software version of the unit is inconsistent with that of the SCC board. Certain functions of the NE may operate abnormally.
Possible Causes
The user uses the customized software package, in which no software for the normal board is found.
Procedure
Step 1 On the U2000, choose correct software version to perform a normal package loading again. ----End
Related Information
None
Issue 02 (2011-10-31)
690
4 Alarm Processing
4.262 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the package version consistency check fails. The alarm indicates that the software version information (similar to the file list category) of the software package is not consistent with the actual software version information.
Attribute
Parameters
None

The software versions on the NE are inconsistent. Certain functions of the NE may operate abnormally.
Possible Causes
The file of the software package is faulty, and the software version information of the software package is not consistent with the actual software version information.
Procedure
Step 1 On the U2000, use a correct software package to perform package loading on the board. ----End
Related Information
None
4.263 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that the NE rollback fails. If certain board rollbacks fail when the NE performs the rollback, the alarm occurs.
Issue 02 (2011-10-31)
691
4 Alarm Processing
Attribute
Parameters
None

The NE rollback fails. The board software cannot be recovered to the version before the package loading. In this case, the board software version and the NE software version may mismatch. Certain functions of the NE may operate abnormally.
Possible Causes
Certain board rollbacks fail when the NE performs the rollback.
Procedure
Step 1 On the U2000, use the correct software package to perform package loading on the board. ----End
Related Information
None
4.264 SYN_BAD
Description
SYN_BAD is an alarm indicating that the frequency deviation of the synchronization source exceeds the permitted range. This alarm is generated when the frequency deviation of the synchronization source exceeds the permitted range so that quality of the physical-layer synchronization source deteriorates. Reported from the WDM side or client side: NA
Attribute
Parameters
4 Alarm Processing
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located. Parameter 2 Indicates the number of the slot in the subrack where the clock source of the service board is located. If the external clock source is used, the value is always 0xf0. Parameter 3 Indicates the reserved byte, whose value is always 0x00. Parameter 4 In the case of the clock source of the service board, it indicates the number of the port in the subrack where the clock source is located. In the case of the external clock source, it indicates the number of the external clock. l 0x01 indicates the first external clock. l 0x02 indicates the second external clock.

When the SYN_BAD alarm is generated, tracing the relevant clock source may cause service bit errors.
Possible Causes
The possible causes of the SYN_BAD alarm are as follows: l l l Cause 1: The frequency deviation of the synchronization source exceeds the permitted range. Cause 2: The input and output modes of the external clock source are inconsistent. Cause 3: The clock board that reports the alarm is faulty.
Procedure
l Check whether any higher-level alarm (such as B1_EXC, B1_SD, B2_EXC, B2_SD or MS_CROSSTR) or performance event is detected on the U2000. If yes, take priority to handle the higher-level alarm or performance event, and then check whether the SYN_BAD alarm is cleared. Cause 1: The frequency deviation of the synchronization source exceeds the permitted range. 1. If an external clock source is traced, check whether the clock signals are normal. If not, replace the external clock source. For details, see Configuring Physical Clock in the Feature Description. If the alarm persists, check whether the input and output modes of the external clock source are consistent. After the input and output of the external clock source are set
Cause 2: The input and output modes of the external clock source are inconsistent. 1.
Issue 02 (2011-10-31)
4 Alarm Processing
to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared. For details, see Configuring Physical Clock in the Feature Description. l Cause 3: The clock board that reports the alarm is faulty. 1. 1. If the alarm persists, perform cold reset on the clock board, and then check whether the alarm is cleared. For details, see Performing Cold Reset of a Board in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see the Parts Replacement.
2. ----End
Related Information
4.265 SYNC_C_LOS
Description
SYNC_C_LOS is an alarm indicating a synchronization source priority loss. This alarm is generated when the clock source on a service board is lost in the priority table. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. The parameter of the alarm is displayed in the brackets in the Details area. The parameter is in the hexadecimal format and is described as follows: l When the parameter contains six numbers, it indicates that the time source of the service board is in subrack 0. The first and second numbers indicate the ID of the slot where the time source of the service board is located in the subrack. The third to sixth numbers indicate the number of port where the time source of the service board is located in the subrack. For example, if the parameter value is 120001, the time source of the service board is located at port 1 of the board in slot 18 in subrack 0. When the parameter contains seven numbers, the first number indicates the ID of the subrack where the time source of the service board is located. The second and third numbers indicate the ID of the slot where the time source of the service board is located in the subrack. The fourth to seventh numbers indicate the number of port where the time source of the service board is located in the subrack. For example, if the parameter value is 1120001, the time source of the service board is located at port 1 of the board in slot 18 in subrack 1.
Issue 02 (2011-10-31)
694
4 Alarm Processing

If this alarm is generated, it indicates that the external clock is lost. The equipment cannot trace this lost external clock. In this case, if only the internal clock source can be used, bit error occurs in the services later.
Possible Causes
The possible causes of the SYNC_C_LOS alarm are as follows: l l l l Cause 1: Input signals are lost at the optical or electrical port that is connected to the clock source. Cause 2: There is a fiber cut (when a line clock source is traced). Cause 3: The service board is faulty. Cause 4: The timing board is faulty.
Procedure
l Cause 1: Input signals are lost at the optical or electrical port that is connected to the clock source. Cause 2: There is a fiber cut (when a line clock source is traced). 1. On the U2000, check whether the R_LOS alarm is generated on the relevant service board. If yes, take priority to clear the R_LOS alarm, and then check whether the SYNC_C_LOS alarm is cleared. If the alarm persists, perform cold reset on the relevant service board, and then check whether the alarm is cleared. For details, see Performing Cold Reset of a Board in the Supporting Tasks. If the alarm persists, replace the service board. For details, see the Parts Replacement. If the alarm persists, perform cold reset on the clock board, and then check whether the alarm is cleared. If the alarm persists, replace the clock board.
Cause 3: The service board is faulty. 1.
2. l
Cause 4: The clock board is faulty. 1. 2.
----End
Related Information
4.266 SYNC_DISABLE
Description
The SYNC_DISABLE is an alarm indicating that the automatic synchronization of the system control board is disabled. When the automatic synchronization of the system control board is disabled, backup in batches is not supported and this alarm is generated.
4 Alarm Processing
Attribute
Parameters
None

The data of the active and standby system control boards may be inconsistent.
Possible Causes
The automatic synchronization state of the system control board is changed from enabled to disabled.
Procedure
Step 1 Change the automatic synchronization state of the system control board to disabled, and then the alarm is cleared automatically. ----End
Related Information
None
4.267 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH is an alarm indicating the forced or manual switching state of a clock source. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
4 Alarm Processing
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Name Meaning
Parameter 1 Indicates the number of the subrack where the switched clock source is located. Parameter 2 Indicates the number of the slot in the subrack where the switched clock source is located. If the external clock source is used, the value is always 0xf0. Parameter 3 Indicates the reserved byte, whose value is always 0x00. Parameter 4 In the case of the clock source of the service board, it indicates the number of the port in the subrack where the switched clock source is located. In the case of the external clock source, it indicates the number of the external clock. l 0x01 indicates the first external clock. l 0x02 indicates the second external clock. Parameter 5 Indicates the ID of the priority table. Valid values are as follows: l 0x01: priority table of the system clock l 0x02: priority table of the first channel 2M phase-locked source l 0x03: priority table of the second channel 2M phase-locked source

When the SYNC_F_M_SWITCH alarm is generated, the NE clock works in the forced or manual switching state. This alarm does not affect services.
Possible Causes
Cause 1: A manual or forced switching command is issued for the clock source.
Procedure
l l View the SYNC_F_M_SWITCH alarm on the U2000, and then determine the relevant clock source according to the alarm parameters. Cause 1: A manual or forced switching command is issued for the clock source. 1. Clear the manual or forced switching for the relevant clock source, and the alarm is automatically cleared. For details, see Configuring Physical Clock in the Feature Description.
----End
Related Information
4 Alarm Processing
4.268 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating that the clock source in the priority list is locked. Reported from the WDM side or client side: NA
Attribute
Parameters
Parameter 1 Indicates the number of the subrack where the locked clock source is located. Parameter 2 Indicates the number of the slot in the subrack where the locked clock source is located. If the external clock source is used, the value is always 0xf0. Parameter 3 Indicates the reserved byte, whose value is always 0x00. Parameter 4 In the case of the clock source of the service board, it indicates the number of the port in the subrack where the locked clock source is located. In the case of the external clock source, it indicates the number of the external clock. l 0x01 indicates the first external clock. l 0x02 indicates the second external clock.

When the SYNC_LOCKOFF alarm is generated, the relevant clock source is locked and cannot be traced by the NE. This alarm itself does not affect services.
Possible Causes
Cause 1: The NE software issues a command to lock the clock source.
4 Alarm Processing
Procedure
l l View the SYNC_LOCKOFF alarm on the U2000, and then determine the locked clock source according to the alarm parameters. Cause 1: The NE software issues a command to lock the clock source. 1. After the lockout of the clock source is released on the U2000, the SYNC_LOCKOFF alarm is automatically cleared. For details, see Configuring Physical Clock in the Feature Description.
----End
Related Information
4.269 SYNC_FAIL
Description
The SYNC_FAIL is an alarm indicating that the batch backup fails.
Attribute
Parameters
Parameter Description
Parameter 1 Indicates the alarm cause. 0x31 indicates that backing up the database fails. 0x32 indicates that verifying the active and standby SCC file versions fails. 0x33 indicates that the active and standby SCCs fails to communicate.

The patch backup fails, and the working/protection switching is unavailable.
Possible Causes
l l l
Issue 02 (2011-10-31)
The database backup fails. Software versions of the working board and the protection board are not consistent. Protection board communication is not stable or available.
4 Alarm Processing
Procedure
Step 1 Wait until the next working/protection backup succeeds and check whether the alarm is cleared. Step 2 If the alarm persists, check whether the software versions of the working board and the protection board are consistent. If not, upgrade the software for consistency. ----End
Related Information
None
4.270 SYSPARA_CFDB_NOSAME
Description
The SYSPARA_CFDB_NOSAME is an alarm indicating the difference between the SCC data and the CF card data. Back up the data from the SCC to the CF card: In the first startup, the SCC performs the consistency check between the SCC data and the CF card data. If not consistent, the SCC does not perform the timing backup before reporting this alarm. If consistent, the SCC starts the timing backup.
Attribute
Parameters
None

The data in the system parameter area are not consistent with that saved in the CF card. The data cannot be recovered from the CF card.
Possible Causes
The SCC data and the CF card data are not consistent upon the first startup.
Procedure
Step 1 Wait for the next backup period so that the NE database automatically backs up data to the CF card and the alarm is cleared. ----End
Related Information
None
4 Alarm Processing
4.271 T_LOSEX
Description
The T_LOSEX is an alarm indicating that a board has detected the loss of signals in the service bus of the backplane. If the board has detected that the service bus of the backplane is in the LOS state, the T_LOSEX alarm is reported.
Attribute
Parameters
None

When the T_LOSEX alarm is generated, the services of a board are interrupted. Consequently, the board fails to work normally.
Possible Causes
The possible causes of the T_LOSEX alarm are as follows: l l l The service board is improperly inserted. The cross-connect board is improperly inserted. The clock source of the working and protection cross-connect boards fails to work or is of poor quality.
Procedure
Step 1 View the T_LOSEX alarm on the U2000 to determine the relevant board. Step 2 Make sure that the board is firmly inserted and properly installed, and then check whether the T_LOSEX alarm is cleared. If the alarm persists, go to the next step. Step 3 Make sure that the cross-connect board is firmly inserted and properly installed, and then check whether the T_LOSEX alarm is cleared. If the alarm persists, go to the next step. Step 4 Replace the cross-connect board that reports the alarm, and then check whether the T_LOSEX alarm is cleared. If the alarm persists, go to the next step. Step 5 Replace the board that reports the T_LOSEX alarm. ----End
4 Alarm Processing
Related Information
None
4.272 T_SLIP
Description
The T_SLIP is an alarm indicating that slip frames occur on the transmitted side. The alarm occurs when the phase deviation occurs on the transmitted service frames of the board.
Attribute
Parameters
None

Bit errors occur in the client services, which can cause a service break when it gets severe.
Possible Causes
The clock signals are not synchronous.
Procedure
Step 1 Perform cold reset on the faulty board through the U2000 or remove the faulty board. For details, see the Supporting Tasks. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.273 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is excessively high. This alarm occurs when the laser temperature is higher than the upper laser temperature threshold. Reported from the WDM side or client side: WDM side, client side
4 Alarm Processing
Attribute
Parameters
None

When the temperature of the tube core of the optical module is excessively high, the working wavelengths of the optical module and the client services are affected.
Possible Causes
l l l The working temperature of the board is excessively high. The laser is faulty. The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature and ventilation of the equipment room. If the board ambient temperature is excessively high, cool the equipment room with cooling devices, such as an air conditioner. Step 2 Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.274 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is excessively low. This alarm occurs when the laser temperature is lower than the lower threshold of the laser temperature. Reported from the WDM side or client side: WDM side, client side
Attribute
Issue 02 (2011-10-31)
703
4 Alarm Processing
Parameters
None

This has impact on the working wavelengths of the optical module and affects the client services.
Possible Causes
l l l Working temperature of the board is excessively low. The laser is faulty. The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature. If it is excessively low, increase it. Step 2 Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4.275 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that the board is in the test state.
Attribute
Alarm Severity Warning Alarm Type Processing alarm
Parameters
None

The test commands, which can be issued only when the board is in the test status, may have an impact on the system.
Possible Causes
A command is issued for the board to enter the test state.
4 Alarm Processing
Procedure
Step 1 View the TEST_STATUS alarm on the U2000 to determine the relevant board. Step 2 When a command is issued to end the test state, the TEST_STATUS alarm is automatically cleared. However, this does not eliminate the system impact that arose during the test state of the board. To ensure that the commands issued during the test state no longer affect the system, perform cold reset on the board. ----End
Related Information
None
4.276 THUNDERALM
Description
The THUNDERALM is an alarm indicating a lighting protection circuit failure. The alarm is generated when the PIU board detects a lightning protection circuit failure of the PIU board.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table. Parameter Parameter 1 Description Indicates the number of the unit that reports the alarm. For example, 0x01 indicates the PIU1 unit. 0x02 indicates the PIU2 unit.

The lightning protection performance of the system is degraded. If the equipment is attacked by a strong current (for example, a strong lightning stroke), the board in the subrack may be unavailable. As a result, the services are interrupted.
4 Alarm Processing
Possible Causes
l The equipment is attacked by a strong lighting stroke (the common mode current is larger than 5000 A and the differential mode current is larger than 3000 A). As a result, the lightning protection component on the PIU board is unavailable and the circuit is broke due to the automatic protection of the fuse. Hence, the PIU detects the failure and reports this alarm. The board hardware is faulty.
Procedure
Step 1 Replace the faulty PIU board. For details, see the Parts Replacement. ----End
Related Information
In the stormy weather, intensive electromagnetic fields form in the air. To protect the equipment against the lightning stroke, the equipment must be grounded during installation.
4.277 TIME_LOS
Description
The TIME_LOS is an alarm indicating the loss of the time source level. This alarm is generated when the time source state does not exist after the precision time function is enabled. Reported from the WDM side or client side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. The parameter of the alarm is displayed in the brackets in the Details area. The parameter is in the hexadecimal format and is described as follows: l When the parameter contains six numbers, it indicates that the time source of the service board is in subrack 0. The first and second numbers indicate the ID of the slot where the time source of the service board is located in the subrack. The third to sixth numbers indicate the number of port where the time source of the service board is located in the subrack. For example, if the parameter value is 120001, the time source of the service board is located at port 1 of the board in slot 18 in subrack 0. When the parameter contains seven numbers, the first number indicates the ID of the subrack where the time source of the service board is located. The second and third numbers indicate the ID of the slot where the time source of the service board is located in the subrack. The fourth to seventh numbers indicate the number of port where the time source of the
Issue 02 (2011-10-31)
4 Alarm Processing
service board is located in the subrack. For example, if the parameter value is 1120001, the time source of the service board is located at port 1 of the board in slot 18 in subrack 1.

When the alarm is reported, the time between the upstream and downstream NEs cannot be synchronous, which may affect the quality of the service.
Possible Causes
The possible causes of the TIME_LOS alarm are as follows: l l l Cause 1: There are fiber failures or misconnections. Cause 2: The service board is faulty. Cause 3: The clock board is faulty.
Procedure
l Cause 1: There are fiber failures or misconnections. 1. l Check the fiber connections. Check whether there are optical interface alarms, such as R_LOS and R_LOF. If there are optical interface alarms, clear the alarms first. If the alarm persists, perform cold reset on the relevant service board, and then check whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board" in the Supporting Tasks. If the alarm persists, replace the service board. For details, see the Parts Replacement. If the alarm persists, perform cold reset on the clock board, and then check whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board" in the Supporting Tasks. If the alarm persists, replace the clock board.For details, see "Replacing the Clock Board" in the Parts Replacement.
Cause 2: The service board is faulty. 1.
2. l
2. ----End
Related Information
4.278 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the time enters the non-trace mode. The precision time of the board is in the non-trace mode. This alarm is generated when the board traces the internal source after the precision time function is enabled.
4 Alarm Processing
Attribute
Parameters
None

When the alarm is reported, the time between the upstream and downstream NEs cannot be synchronous, which may affect the quality of the service.
Possible Causes
The possible causes of the TIME_NO_TRACE_MODE alarm are as follows: l l l l Cause 1: The priority table is not configured. Cause 2: There are fiber failures or misconnections. Cause 3: The attributes of the packets at the upstream NE are configured incorrectly. Cause 4: The clock board is faulty.
Procedure
l Cause 1: The priority table is not configured. 1. Query the current priority table of the system. If there is only the internal clock source in the priority table, set the clock source priority table to include other available clock sources. After the setting, the alarm is automatically cleared. For details, see "Configuring a IEEE 1588v2 Clock" in the Feature Description. Check the fiber connections. Check whether there are optical interface alarms, such as R_LOS and R_LOF. If there are optical interface alarms, clear the alarms first. If the alarm persists, check whether the attributes of the packets at the upstream NE are configured correctly on the U2000. If any error is found, modify the configuration. For details, see "Configuring a IEEE 1588v2 Clock" in the Feature Description. If the alarm persists, perform cold reset on the clock board, and then check whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board" in the Supporting Tasks. If the alarm persists, replace the clock board. For details, see "Replacing the Clock Board" in the Parts Replacement.
Cause 2: There are fiber failures or misconnections. 1.
Cause 3: The attributes of the packets at the upstream NE are configured incorrectly. 1.
2. ----End
Related Information
4 Alarm Processing
4.279 TR_LOC
Description
The TR_LOC is an alarm indicating that the clock of the cross-connect board is faulty. If a board has detected loss of the clock signal of the cross-connect board, loss of the frame header, or damage to the cross-connect board, the TR_LOC alarm is reported.
Attribute
Parameters
Parameter 1 Indicates the detailed fault information. l Bit 0 indicates that the clock of the cross-connect board in the slot with a smaller number is lost. l Bit 1 indicates that the frame header of the cross-connect board in the slot with a smaller number is lost. l Bit 2 indicates that the bus indicating the status of the cross-connect board in the slot with a smaller number is faulty. l Bit 4 indicates that the clock of the cross-connect board in the slot with a bigger number is lost. l Bit 5 indicates that the frame header of the cross-connect board in the slot with a bigger number is lost. l Bit 6 indicates that the bus indicating the status of the cross-connect board in the slot with a bigger number is faulty.

When the TR_LOC occurs, the board fails to work normally. If the protection cross-connect board is faulty, the services are not affected. If the working cross-connect board is faulty, the services are switched. Consequently, transient service interruption occurs.
Issue 02 (2011-10-31)
709
4 Alarm Processing
Possible Causes
The possible causes of the TR_LOC alarm are as follows: l l The clock line of the cross-connect board is faulty. The hardware of the local board is faulty.
Procedure
Step 1 View the TR_LOC alarm at the local station, and check whether the alarm is generated on the service boards. l l If the TR_LOC alarm is generated on most service boards, the cross-connect board is faulty. In this case, replace the faulty cross-connect board. If only the local board reports the alarm, replace the board.
----End
Related Information
None
4.280 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU alarm indication in the VC-3 lower order path. TU alarm indication is the AIS at the level of the VC-3 lower order path. If a board has detected that the TU path is all "1"s, the TU_AIS_VC3 alarm is reported.
Attribute
Parameters
None

When the TU_AIS_VC3 alarm is generated, the VC-3 path services are interrupted.
Possible Causes
The possible causes of the TU_AIS_VC3 alarm are as follows: l Certain higher-level alarms, such as the R_LOS, R_LOF, HP_SLM, or AU_AIS, occur in the system.
Issue 02 (2011-10-31)
4 Alarm Processing
l l
The cross-connect and timing board is faulty. The relevant path at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is detected on the U2000. If yes, take priority to clear it, and then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step. Step 2 Perform cold reset on the board that reports the alarm. Then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after cold reset of the board. Step 3 Replace the board that reports the alarm, and then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step. Step 4 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check whether the TU_AIS_VC3 alarm is cleared. Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether the TU_AIS_VC3 alarm is cleared. ----End
Related Information
None
4.281 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating the loss of pointer in the VC-3 lower order path. If a board has detected that the TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames, the TU_LOP_VC3 alarm is reported.
Attribute
Parameters
None
4 Alarm Processing

When the TU_LOP_VC3 alarm is generated, the VC-3 path services are interrupted.
Possible Causes
The possible causes of the TU_LOP_VC3 alarm are as follows: l l l Certain higher-level alarms, such as the R_LOS, R_LOF, HP_SLM, or AU_AIS, occur in the system. The cross-connect and timing board is faulty. The relevant path at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is detected on the U2000. If yes, take priority to clear it, and then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step. Step 2 Perform cold reset on the board that reports the alarm. Then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step.
CAUTION
If the services that travel through the board are not configured with protection, the services are interrupted after cold reset of the board. Step 3 Replace the board that reports the alarm, and then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step. Step 4 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check whether the TU_LOP_VC3 alarm is cleared. Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether the TU_LOP_VC3 alarm is cleared. ----End
Related Information
None
4.282 VCAT_LOA
See the alarm page according to the type of the board that reports the alarm.
Issue 02 (2011-10-31)
712
4 Alarm Processing
Table 4-5 Alarm page link Board Type SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Boards other than the SF64, SF64A, SFD64, SL64, SLD64, SLQ16, SLQ64, SLH41, SLO16, or EGSH Alarm Page Link 4.282.1 VCAT_LOA (OCS) 4.282.2 VCAT_LOA (OTN)
4.282.1 VCAT_LOA (OCS)

Description
The VCAT_LOA (OCS) is an alarm indicating that the delay of the virtual concatenation is excessively long. This alarm occurs when the delay time of the timeslots bound to a VCTRUNK exceeds the time allowed by the virtual concatenation delay. The time allowed by the virtual concatenation delay varies according to different board types.
Attribute
Alarm Severity Critical Alarm Type Processing alarm
Parameters
None

During the service data transmission, when the alignment time of the virtual concatenation delay is excessively long, the timeslots cannot form a data frame. Accordingly, it causes the packet loss.
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows: The configured VCTRUNK timeslots pass physical links of different distances.
Procedure
Step 1 View the VCAT_LOA alarm on the U2000 to determine the relevant board. Step 2 Configure the timeslots of the VCTRUNK again, so that they pass the same fiber. If they need to pass different fibers, make sure that the distance difference of the fibers is the shortest. ----End
4 Alarm Processing
Related Information
None
4.282.2 VCAT_LOA (OTN)

Description
The VCAT_LOA is an alarm indicating that the delay of multiframes exceeds the threshold. The alarm is generated when the MFAS value in OTN signals received on the WDM side is not consistent.
Attribute
Parameters
None

The board is unable to converge the WDM-side services into the client-side 40 Gbit/s services, which causes that the client-side services are abnormal.
Possible Causes
l l The fiber connection on the WDM side is incorrect. The board at the upstream or local station is faulty.
Procedure
Step 1 Check whether the fiber connection on the WDM side is correct. If not, re-connect the fibers. Step 2 Check whether there are abnormal alarms in the WDM-side services. If yes, clear the alarms according to the proper procedures. Step 3 If the alarm persists, perform a WDM-side inloop on the upstream board and then on the local board, to determine which board is faulty. Step 4 Based on the results, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
ITU-T G.709
4.283 VCAT_LOM_VC3
4 Alarm Processing
Description
The VCAT_LOM_VC3 is an alarm indicating the loss of the virtual concatenation multiframe in the VC-3 path. This alarm is generated when the system detects that the multiframe indicator (MFI) field in the H4 byte of the VC-3 timeslot is illegal.
Attribute
Parameters
None

l During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC3 alarm are as follows: l l The virtual concatenation delay is excessively long. The MFI field in the K4 byte transmitted from the opposite end is incorrect.
Procedure
Step 1 View the VCAT_LOM_VC3 alarm on the U2000 to determine the relevant board. Step 2 On the U2000, check whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual concatenation delay is excessively long. See the procedure for handling the VCAT_LOA alarm to clear it. After that, check whether the VCAT_LOM_VC3 alarm is cleared. Step 3 If the alarm persists, check whether the board that reports the VCAT_LOM_VC3 alarm at the local end is faulty. Replace the board that reports the alarm at the local station, and then check whether the VCAT_LOM_VC3 alarm is cleared. Step 4 If the alarm persists, it indicates that the MFI domain transmitted from the SDH opposite end is incorrect. Replace the corresponding board at the opposite station, and then check whether the VCAT_LOM_VC3 alarm is cleared. ----End
Related Information
None
4.284 VCAT_LOM_VC4
4 Alarm Processing
Description
The VCAT_LOM_VC4 is an alarm indicating the loss of the virtual concatenation multiframe in the VC-4 path. This alarm is generated when the system detects that the multiframe indicator (MFI) field in the H4 byte of the VC-4 timeslot is illegal.
Attribute
Parameters
None

l During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC4 alarm are as follows: l l The virtual concatenation delay is excessively long. The MFI field in the K4 byte transmitted from the opposite end is incorrect.
Procedure
Step 1 View the VCAT_LOM_VC4 alarm on the U2000 to determine the relevant board. Step 2 On the U2000, check whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual concatenation delay is excessively long. See the procedure for handling the VCAT_LOA alarm to clear it. After that, check whether the VCAT_LOM_VC4 alarm is cleared. Step 3 If the alarm persists, check whether the board that reports the VCAT_LOM_VC4 alarm at the local end is faulty. Replace the board that reports the alarm at the local station, and then check whether the VCAT_LOM_VC4 alarm is cleared. Step 4 If the alarm persists, it indicates that the MFI domain transmitted from the SDH opposite end is incorrect. Replace the corresponding board at the opposite station, and then check whether the VCAT_LOM_VC4 alarm is cleared. ----End
Related Information
None
Issue 02 (2011-10-31)
716
4 Alarm Processing
4.285 VLAN_SNCP_PS
Description
VLAN SNCP protection switching alarm. This alarm is reported when the working or protection channel of the protection group is faulty or the user runs an external switching command.
Attribute
Parameters
Parameter Description
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated.

l l When switching is performed to the VLAN SNCP group, the services would be transiently interrupted. When the alarm is reported, the working channel or the protection channel of the VLAN SNCP group might have faulty services that need to be restored.
Possible Causes
l l l A user issues an external switching command such as forced switching, manual switching or locked switching. The services of the working channel or the protection channel of the VLAN SNCP group are faulty. The switching is in WTR State. After WTR Times (s), the alarm clears.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced switching, manual switching or locked switching, check whether the external switching operation is necessary, 1. 2. If the external switching operation is necessary, ignore the alarm. If the external switching operation is unnecessary, issue a clear switching command to clear the external switching.
Step 2 If the alarm is generated due to the fault of the working channel or the protection channel of the protection group,
4 Alarm Processing
1.
Query whether the related boards for configuring the protection group have the alarms, for example, R_LOF, R_LOS, R_OOF, OTUk_LOF, OTUk_LOM, OTUk_AIS. If yes, clear the alarm so that the services in the working channel or the protection channel return normal. If the alarm persists, check whether the attribute of the protection group is Revertive. If that is the case, the working channel would automatically switch to the working channel. The alarm would disappear. If the attribute is Non-Revertive, set it to Revertive and the alarm would disappear.
2.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in WTR State. This alarm requires no handling. After WTR Times (s), the alarm clears. ----End
Related Information
VLAN SNCP protection utilizes the dual fed and selective receiving function of the L2 module to protect the upstream convergence services. The service granularity of protection switching is services at client-side ports, which are identified as VLAN. For details, see "VLAN SNCP Protection" in the Feature Description.
4.286 VOA_ADJUST_FAIL
Description
The VOA_ADJUST_FAIL is an alarm indicating that the VOA adjustment fails.
Attribute
Parameters
Parameter Description Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The gain adjustment of the OAU1 fails, which results in failure of command issuing.
Possible Causes
l l
Issue 02 (2011-10-31)
The external DCM of the OAU1 has excessive attenuation between the input and output interfaces. The OAU1 laser is off.
4 Alarm Processing
The gain set for OAU1 exceeds the maximum permitted actual gain. As a result, the VOA adjustment fails.
Procedure
Step 1 Check whether the external DCM of the OAU1 has excessive attenuation between the input and output interfaces. If yes, adjust it to keep the input and output in a normal range. Step 2 If the alarm persists, check whether the laser of the OAU1 is on. If not, turn it on. Step 3 Query the permitted actual gain range of OAU1 on the U2000 and set the gain again to ensure that the gain is within the permitted range. ----End
Related Information
None
4.287 VOADATA_MIS
Description
The VOADATA_MIS is an alarm indicating mismatch of the attenuation attribute. When the set attenuation value falls beyond the adjustable attenuation range of the board, the alarm is reported.
Attribute
Parameters
None

Possible Causes
Cause 1: As for the attenuation, replacing the board or the optical module causes that the stored attenuation value issued by the NE software falls beyond the new adjustable attenuation range of the board.
Procedure
l Cause 1: The stored attenuation value issued by the NE software falls beyond the new adjustable attenuation range of the board.
Issue 02 (2011-10-31)
4 Alarm Processing
1.
Query the adjustable range of the current actual attenuation. Re-set a valid attenuation value for the optical interface channel of the board based on the queried adjustable range.
----End
Related Information
None
4.288 W_R_FAIL
Description
Writing or reading chip register failure. The alarm is generated when the read value and the written value of the register are not consistent.
Attribute
Parameters
Parameter Description Parameter 1 Indicates the IDs of the board register. For example, 0x01-0x09 indicates the IDs of the faulty chips that are of different types.

The board cannot work normally. In this case, the services may not be received or transmitted properly. In addition, the board may fail to query the current performance value.
Possible Causes
The board is faulty.
Procedure
Step 1 Perform a warm reset on the faulty board on the U2000. For details, see the Troubleshooting. Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
4 Alarm Processing
4.289 WAVE_ADD_ABN
Description
APE detect wavelengths added.
Attribute
Parameters

APE detect wavelengths added.
Possible Causes
The actually accessed wavelengths on each optical interface can be obtained through the spectrum analysis module of the detect board. The wavelengths are then compared with the scanned wavelengths obtained during the defining. If a new wavelength is detected, a wavelength add alarm is reported.
Procedure
Step 1 The network management system prompts the user to re-define the APE standard optical power curve. ----End
Related Information
4 Alarm Processing
4.290 WAVE_DROP_ABN
Description
APE detect wavelengths dropped.
Attribute
Parameters

APE detect wavelengths dropped.
Possible Causes
The actually accessed wavelengths on each optical interface can be obtained through the spectrum analysis module of the detect board. The wavelengths are then compared with the scanned wavelengths obtained during the defining. If there is a wavelength that is not accessed, a wavelength drop alarm is reported.
Procedure
Step 1 The network management system prompts the user to re-define the APE standard optical power curve. ----End
Related Information
4 Alarm Processing
4.291 WAVEDATA_MIS
Description
The WAVEDATA_MIS is an alarm indicating mismatch of the wavelength or band attribute. When the configured logic wavelength or band differs with the actual wavelength or band, the alarm is reported.
Attribute
Parameters
None

The service may be interrupted.
Possible Causes
l l Cause 1: The configured logic wavelength or band differs with the actual wavelength or band. Cause 2: The board is faulty.
Procedure
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or band. 1. Query the actual wavelength of the unit and the logic wavelength stored on the U2000. If these two wavelengths differ, reconfigure the operating wavelength of the corresponding optical port to make it the same as the fixed wavelength of the optical module on the board. If the alarm persists, replace the board or optical module with another one whose wavelength is the same as that stored in the NE software. For details, see the Parts Replacement.
Cause 2: The board is faulty. 1.
----End
Related Information
None
4 Alarm Processing
4.292 WAVELEN_OVER
Description
The WAVELEN_OVER is an alarm indicating that the wavelength crosses the threshold. When the wavelength drift of the OTU board exceeds the threshold, this alarm occurs.
Attribute
Parameters
None

The services carried by the wavelength is degraded or interrupted, and the services carried by the adjacent wavelengths may be affected.
Possible Causes
l l l The wavelength drift of the corresponding channel of the OTU board exceeds the upper or lower threshold. The wavelength locking is mis-adjusted because the logical fiber connection is inconsistent with the physical fiber connection. The wavelength locking module on the WMU board or a module on the OTU board is malfunctioning.
Procedure
Step 1 Check whether the wavelength of the optical interface connecting to the wavelength monitoring board on the OTU board is within the normal range. If not, the OTU board enables the wavelength locking function to adjust the monitored wavelength. When the monitored wavelength restores to a value within the normal range, this alarm is cleared. Step 2 If the alarm persists, check whether the logical fiber connections are consistent with the physical fiber connections. If not, modify the logical fiber connections so that the logical fiber connections are consistent with the physical fiber connections. For details, see "Checking Logical Fibers" in the Supporting Tasks. Step 3 If the alarm persists, cold reset of the OTU board is required. For details, see the Supporting Tasks. Step 4 If the alarm persists, contact Huawei engineers. ----End
4 Alarm Processing
Related Information
None
4.293 XC_UNSWITCH
Description
The XC_UNSWITCH is an alarm indicating that the cross-connect matrix of the board is not switched.
Attribute
Parameters
Parameter 1 Indicates the subrack ID of the board whose cross-connect matrix is not switched. Parameter 2 Indicates the slot ID of the board whose cross-connect matrix is not switched.

The services related to the board that reports the alarm are interrupted.
Possible Causes
The possible causes of the XC_UNSWITCH alarm are as follows: l The cross-connect board or the line board fails to respond to the cross-connect matrix switching command issued by the NE software, and as a result is not updated with the crossconnect matrix configured by the NE software. The board is in the BIOS state, and as a result cannot be updated with the cross-connect matrix configured by the NE software.
Issue 02 (2011-10-31)
725
4 Alarm Processing
Procedure
Step 1 Check whether the board that reports the alarm has communication alarms. If yes, clear the communication alarms, and then check whether the XC_UNSWITCH alarm is cleared. Step 2 If the alarm persists, perform warm reset on the board, and check whether the XC_UNSWITCH alarm is still generated. Step 3 If the alarm persists, contact Huawei engineers to re-load the board software. Step 4 If the alarm persists, replace the board that reports the alarm. For details, see the Parts Replacement. ----End
Related Information
None
Issue 02 (2011-10-31)
726
5
About This Chapter
Performance Event List
This topic lists the names, description and relevant boards of the performance event in alphabetical order and lists the performance event of every board. 5.1 Product Performance Event List Lists the different types of performance event. 5.2 Board Performance Event List This section list the performance event of every board.
Issue 02 (2011-10-31)
727
5.1 Product Performance Event List

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

Lists of the performance event of check and error correction. Table 5-1 Performance Event List of Check and Error Correction Name CRC4ES CRC4FEES CRC4FESES CRC4FEUAS CRC4SES CRC4UAS FEC_AFT_COR_ERAVR FEC_BEF_COR_ERAVR FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT FEC_BEF_CORER_FLOAT FEC_AFT_CORER_FLOAT OSC_BBE OSC_BBER OSC_BIAES Description CRC4 Errored Second CRC4 Far End Errored Second CRC4 Far End Severely Errored Second CRC4 Far End Unavailable Second CRC4 Severely Errored Second CRC4 Unavailable Second After FEC Correct Average Errored Rate in monitor period Before FEC Correct Average Errored Rate in monitor period After FEC Correct Errored Rate Before FEC Correct Errored Rate Forward Error Correction - Corrected 0 Bit Count Forward Error Correction - Corrected 1 Bit Count Forward Error Correction - Corrected Byte Count Forward Error Correction - Uncorrected Block Count Before FEC Correct Errored Rate (FLOAT) After FEC Correct Errored Rate (FLOAT) OSC Path Background Block Error OSC Path Background Block Error Ratio OSC Path Backward Incoming Alignment Errored Second
Issue 02 (2011-10-31)
Name OSC_ES OSC_FEBBE OSC_FEBBER OSC_FEES OSC_FESES OSC_FESESR OSC_FEUAS OSC_IAES OSC_SES OSC_SESR OSC_UAS
Description OSC Path Errored Second OSC Path Far End Background Block Error OSC Path Far End Background Block Error Ratio OSC Path Far End Errored Second OSC Path Far End Severely Errored Second OSC Path Unavailable Seconds OSC Path Far End Unavailable Seconds OSC Path Incoming Alignment Errored Second OSC Path Severely Errored Second OSC Path Unavailable Seconds OSC Path Unavailable Seconds
5.1.2 Performance Event of Pointer Justification

This topic lists the performance events for pointer justifications. Table 5-2 Pointer justification performance event list Name AUPJCHIGH AUPJCLOW AUPJCNEW Description Count of positive AU pointer justifications Count of negative AU pointer justifications Count of new AU pointer justifications
5.1.3 Performance Event of Equipment Function

Lists the performance event of equipment function. Table 5-3 Performance Event List of Equipment Function Name BCVCUR BCVMAX Description Average Pump Laser Backfacet Current Value Maximum Pump Laser Backfacet Current Value
Issue 02 (2011-10-31)
Name BCVMIN CCVCUR CCVMAX CCVMIN EDTMPCUR EDTMPMAX EDTMPMIN EDTPLCUR EDTPLMAX EDTPLMIN ENVTMPCUR ENVTMPMAX ENVTMPMIN ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX
Description Minimum Pump Laser Backfacet Current Value Average Pump Laser Cooling Current Value Maximum Pump Laser Cooling Current Value Minimum Pump Laser Cooling Current Value Current Laser Temperature Value Maximum Laser Temperature Value Minimum Laser Temperature Value Current Laser Output Optical Power Value Maximum Laser Output Optical Power Value Minimum Laser Output Optical Power Value Current Environmental Temperature Value Maximum Environmental Temperature Value Minimum Environmental Temperature Value Current Module Cooling Current Value Maximum Module Cooling Current Value Minimum Module Cooling Current Value Current Module Temperature Value Maximum Module Temperature Value Minimum Module Temperature Value Current Laser Bias Current Value Maximum Laser Bias Current Value Minimum Laser Bias Current Value Current Laser Cooling Current Value Maximum Laser Cooling Current Value Minimum Laser Cooling Current Value Current Input Optical Power Value Maximum Input Optical Power Value
Issue 02 (2011-10-31)
730
Name LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN OOPRLCUR OOPRLMAX OOPRLMIN OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR OSPITMPMAX OSPITMPMIN RPLCUR RPLMAX RPLMIN PCLSOPCUR PCLSOPMAX PCLSOPMIN PCLSSNCUR PCLSSNMAX PCLSSNMIN
Description Minimum Input Optical Power Value Current Output Optical Power Value Maximum Output Optical Power Value Minimum Output Optical Power Value Current Laser Temperature Value Maximum Laser Temperature Value Minimum Laser Temperature Value Current value of the optical output power return loss Maximum value of the optical output power return loss within a time period Minimum value of the optical output power return loss within a time period Average value of laser cooling current Maximum value of laser cooling current Minimum value of laser cooling current Current value of laser working temperature Maximum value of laser working temperature Minimum value of laser working temperature Current value of input optical power Maximum value of input optical power Minimum value of input optical power Current Per-Channel Laser Output Power Value Maximum Per-Channel Laser Output Power Value Minimum Per-Channel Laser Output Power Value Current Per-Channel OSNR Value Maximum Per-Channel OSNR Value Minimum Per-Channel OSNR Value
Issue 02 (2011-10-31)
731
Name PCLSWLCUR PCLSWLMAX PCLSWLMIN PCLSWLOCUR PCLSWLOMAX PCLSWLOMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN TLBCUR TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN WCVCUR WCVMAX WCVMIN AVGFREQDEV MAXFREQDEV MINFREQDEV AVGMEANPATHDELAY MAXMEANPATHDELAY MINMEANPATHDELAY
Description Current Per-Channel Central Wavelength Value Maximum Per-Channel Central Wavelength Value Minimum Per-Channel Central Wavelength Value Current Per-Channel Central Wavelength Maximum Per-Channel Central Wavelength Minimum Per-Channel Central Wavelength Current Total Input Optical Power Value Maximum Total Input Optical Power Value Minimum Total Input Optical Power Value Current Output Optical Power Value Maximum Total Output Optical Power Value Minimum Total Output Optical Power Value Current value of laser bias current Maximum value of laser bias current Minimum value of laser bias current Current value of output optical power Maximum value of output optical power Minimum value of output optical power Current value of pump laser working current Maximum value of pump laser working current Minimum value of pump laser working current Average frequency deviation Maximum frequency deviation Minimum frequency deviation Average path delay Maximum path delay Minimum path delay
Issue 02 (2011-10-31)
732
Name AVGPHASEOFFSET MAXPHASEOFFSET MINPHASEOFFSET XCSTMPCUR XCSTMPMAX XCSTMPMIN
Description Average phase offset Maximum phase offset Minimum phase offset Current Environmental Temperature Value Maximum Environmental Temperature Value Minimum Environmental Temperature Value
5.1.4 Performance Event of Multiplex Section Bit Error

Lists performance event of multiplex section bit error. Table 5-4 Performance Event list of Multiplex Section Bit Error Name MSBBE MSES MSFEBBE MSFEES MSFESES MSFEUAS MSSES MSUAS Description MS Background Block Error MS Errored Second MS Far End Background Block Error MS Far End Errored Second MS Far End Severely Errored Second MS Far End Unavailable Second MS Severely Errored Second MS Unavailable Second
5.1.5 Performance Event of Regenerator Section Bit Error

Lists the performance event of Regenerator Section Bit Error. Table 5-5 Performance Event List of Regenerator Section Bit Error Name RSBBE RSCSES Description RS Background Block Error RS Consecutive Severely Errored Second
Issue 02 (2011-10-31)
733
Name RSES RSOFS RSOOF RSSES RSUAS
Description RS Errored Second RS Out-of-Frame Second Regenerator section of OOF preferance seconds RS Severely Errored Second RS Unavailable Second
5.1.6 Performance Event of Higher Order Path Bit Error

This topic lists the performance events for the bit errors in the higher order paths. Table 5-6 Higher order path performance event list Name HPBBE HPES HPSES HPUAS HPFEBBE HPFEES HPFESES HPFEUAS Description Higher order path block of background error Higher order path errored second Higher order path severely errored second Higher order path far end unavailable second Higher order path far end block of background error Higher order path far end errored second Higher order path far end severely errored second Higher order path far end consecutive severely errored second
5.1.7 Performance Event of Lower Order Path Bit Error

This topic lists the performance events for the bit errors in the lower order paths. Table 5-7 Lower order path performance event list Name VC3BBE VC3ES VC3SES
Issue 02 (2011-10-31)
Description VC3 block of background error VC3 errored second VC3 severely errored second
Name VC3UAS VC3CSES VC3FEBBE VC3FEES VC3FESES VC3FECSES VC3FEUAS
Description VC3 unavailable second VC3 consecutive severely errored second VC3 far end block of background error VC3 far end errored second VC3 far end severely errored second VC3 far end consecutive severely errored second VC3 far end unavailable second
5.1.8 Performance Event of OTN

List the three sections performance Event of OTN. It include: Path Monitoring (PM) section, Tandem Connection Monitoring (TCM) section and Section Monitoring (SM).
Performance Event of PM Section

Table 5-8 Performance Event of PM Section Name ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES Description ODU0 PM Section Background Block Error ODU0 PM Section Ratio of Background Block Error ODU0 PM Section Errored Second ODU0 PM Section Far End Background Block Error ODU0 PM Section Ratio of Far End Background Block Error ODU0 PM Section Far End Errored Second ODU0 PM Section Far End Severely Errored Second ODU0 PM Section Ratio of Far End Severely Errored Second ODU0 PM Section Far End Unavailable Second ODU0 PM Section Severely Errored Second
Issue 02 (2011-10-31)
735
Name ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR
Description ODU0 PM Section Ratio of Severely Errored Second ODU0 PM Section Unavailable Second ODU1 PM Section Background Block Error ODU1 PM Section Ratio of Background Block Error ODU1 PM Section Errored Second ODU1 PM Section Far End Background Block Error ODU1 PM Section Ratio of Far End Background Block Error ODU1 PM Section Far End Errored Second ODU1 PM Section Far End Severely Errored Second ODU1 PM Section Ratio of Far End Severely Errored Second ODU1 PM Section Far End Unavailable Second ODU1 PM Section Severely Errored Second ODU1 PM Section Ratio of Severely Errored Second ODU1 PM Section Unavailable Second ODU2 PM Section Background Block Error ODU2 PM Section Ratio of Background Block Error ODU2 PM Section Errored Second ODU2 PM Section Far End Background Block Error ODU2 PM Section Ratio of Far End Background Block Error ODU2 PM Section Far End Errored Second ODU2 PM Section Far End Severely Errored Second ODU2 PM Section Ratio of Far End Severely Errored Second
Issue 02 (2011-10-31)
736
Name ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU5G_PM_BBE ODU5G_PM_BBER ODU5G_PM_ES ODU5G_PM_FEBBE ODU5G_PM_FEBBER ODU5G_PM_FEES
Description ODU2 PM Section Far End Unavailable Second ODU2 PM Section Severely Errored Second ODU2 PM Section Ratio of Severely Errored Second ODU2 PM Section Unavailable Second ODU3 PM Section Background Block Error ODU3 PM Section Ratio of Background Block Error ODU3 PM Section Errored Second ODU3 PM Section Far End Background Block Error ODU3 PM Section Ratio of Far End Background Block Error ODU3 PM Section Far End Errored Second ODU3 PM Section Far End Severely Errored Second ODU3 PM Section Ratio of Far End Severely Errored Second ODU3 PM Section Far End Unavailable Second ODU3 PM Section Severely Errored Second ODU3 PM Section Ratio of Severely Errored Second ODU3 PM Section Unavailable Second ODU5G PM Section Background Block Error ODU5G PM Section Ratio of Background Block Error ODU5G PM Section Errored Second ODU5G PM Section Far End Background Block Error ODU5G PM Section Ratio of Far End Background Block Error ODU5G PM Section Far End Errored Second
Issue 02 (2011-10-31)
737
Name ODU5G_PM_FESES ODU5G_PM_FESESR ODU5G_PM_FEUAS ODU5G_PM_SES ODU5G_PM_SESR ODU5G_PM_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS
Description ODU5G PM Section Far End Severely Errored Second ODU5G PM Section Ratio of Far End Severely Errored Second ODU5G PM Section Far End Unavailable Second ODU5G PM Section Severely Errored Second ODU5G PM Section Ratio of Severely Errored Second ODU5G PM Section Unavailable Second ODUFLEX PM Section Background Block Error ODUFLEX PM Section Ratio of Background Block Error ODUFLEX PM Section Errored Second ODUFLEX PM Section Far End Background Block Error ODUFLEX PM Section Ratio of Far End Background Block Error ODUFLEX PM Section Far End Errored Second ODUFLEX PM Section Far End Severely Errored Second ODUFLEX PM Section Ratio of Far End Severely Errored Second ODUFLEX PM Section Far End Unavailable Second ODUFLEX PM Section Severely Errored Second ODUFLEX PM Section Ratio of Severely Errored Second ODUFLEX PM Section Unavailable Second
Issue 02 (2011-10-31)
738
Performance Event of TCM Section

Table 5-9 Performance Event of TCM Section Name ODU0_TCMn_BBE ODU0_TCMn_BBER ODU0_TCMn_BIAES ODU0_TCMn_ES ODU0_TCMn_FEBBE ODU0_TCMn_FEBBER ODU0_TCMn_FEES ODU0_TCMn_FESES ODU0_TCMn_FESESR ODU0_TCMn_FEUAS ODU0_TCMn_IAES ODU0_TCMn_SES ODU0_TCMn_SESR ODU0_TCMn_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES Description ODU0 TCMn Section Background Block Error ODU0 TCMn Section Ratio of Background Block Error ODU0 TCMn Section Background Introduced Alignment Errored Second ODU0 TCMn Section Errored Second ODU0 TCMn Section Far End Background Block Error ODU0 TCMn Section Ratio of Far End Background Block Error ODU0 TCMn Section Far End Errored Second ODU0 TCMn Section Far End Severely Errored Second ODU0 TCMn Section Ratio of Far End Severely Errored Second ODU0 TCMn Section Far End Unavailable Second ODU0 TCMn Section Introduced Alignment Errored Second ODU0 TCMn Section Severely Errored Second ODU0 TCMn Section Ratio of Severely Errored Second ODU0 TCMn Section Unavailable Second ODU1 TCMn Section Background Block Error ODU1 TCMn Section Ratio of Background Block Error ODU1 TCMn Section Background Introduced Alignment Errored Second ODU1 TCMn Section Errored Second
Issue 02 (2011-10-31)
739
Name ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR
Description ODU1 TCMn Section Far End Background Block Error ODU1 TCMn Section Ratio of Far End Background Block Error ODU1 TCMn Section Far End Errored Second ODU1 TCMn Section Far End Severely Errored Second ODU1 TCMn Section Ratio of Far End Severely Errored Second ODU1 TCMn Section Far End Unavailable Second ODU1 TCMn Section Introduced Alignment Errored Second ODU1 TCMn Section Severely Errored Second ODU1 TCMn Section Ratio of Severely Errored Second ODU1 TCMn Section Unavailable Second ODU2 TCMn Section Background Block Error ODU2 TCMn Section Ratio of Background Block Error ODU2 TCMn Section Background Introduced Alignment Errored Second ODU2 TCMn Section Errored Second ODU2 TCMn Section Far End Background Block Error ODU2 TCMn Section Ratio of Far End Background Block Error ODU2 TCMn Section Far End Errored Second ODU2 TCMn Section Far End Severely Errored Second ODU2 TCMn Section Ratio of Far End Severely Errored Second
Issue 02 (2011-10-31)
740
Name ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODU2PMBIP8 ODU3_TCMn_BBE ODU3_TCMn_BBER ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE ODU3_TCMn_FEBBER ODU3_TCMn_FEES ODU3_TCMn_FESES ODU3_TCMn_FESESR ODU3_TCMn_FEUAS ODU3_TCMn_IAES ODU3_TCMn_SES ODU3_TCMn_SESR ODU3_TCMn_UAS
Description ODU2 TCMn Section Far End Unavailable Second ODU2 TCMn Section Introduced Alignment Errored Second ODU2 TCMn Section Severely Errored Second ODU2 TCMn Section Ratio of Severely Errored Second ODU2 TCMn Section Unavailable Second Number of bit errors in the optical channel data unit ODU3 TCMn Section Background Block Error ODU3 TCMn Section Ratio of Background Block Error ODU3 TCMn Section Background Introduced Alignment Errored Second ODU3 TCMn Section Errored Second ODU3 TCMn Section Far End Background Block Error ODU3 TCMn Section Ratio of Far End Background Block Error ODU3 TCMn Section Far End Errored Second ODU3 TCMn Section Far End Severely Errored Second ODU3 TCMn Section Ratio of Far End Severely Errored Second ODU3 TCMn Section Far End Unavailable Second ODU3 TCMn Section Introduced Alignment Errored Second ODU3 TCMn Section Severely Errored Second ODU3 TCMn Section Ratio of Severely Errored Second ODU3 TCMn Section Unavailable Second
Issue 02 (2011-10-31)
741
Name ODU5G_TCMn_BBE ODU5G_TCMn_BBER ODU5G_TCMn_BIAES ODU5G_TCMn_ES ODU5G_TCMn_FEBBE ODU5G_TCMn_FEBBER ODU5G_TCMn_FEES ODU5G_TCMn_FESES ODU5G_TCMn_FESESR ODU5G_TCMn_FEUAS ODU5G_TCMn_IAES ODU5G_TCMn_SES ODU5G_TCMn_SESR ODU5G_TCMn_UAS
Description ODU5G TCMn Section Background Block Error ODU5G TCMn Section Ratio of Background Block Error ODU5G TCMn Section Background Introduced Alignment Errored Second ODU5G TCMn Section Errored Second ODU5G TCMn Section Far End Background Block Error ODU5G TCMn Section Ratio of Far End Background Block Error ODU5G TCMn Section Far End Errored Second ODU5G TCMn Section Far End Severely Errored Second ODU5G TCMn Section Ratio of Far End Severely Errored Second ODU5G TCMn Section Far End Unavailable Second ODU5G TCMn Section Introduced Alignment Errored Second ODU5G TCMn Section Severely Errored Second ODU5G TCMn Section Ratio of Severely Errored Second ODU5G TCMn Section Unavailable Second
Performance Event of SM Section

Table 5-10 Performance Event of SM Section Name OTU1_BBE OTU1_BBER OTU1_BIAES Description OTU1 SM Section Background Block Error OTU1 SM Section Ratio of Background Block Error OTU1 SM Section Background Introduced Alignment Errored Second
742
Issue 02 (2011-10-31)
Name OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS
Description OTU1 SM Section Errored Second OTU1 SM Section Far End Background Block Error OTU1 SM Section Ratio of Far End Background Block Error OTU1 SM Section Far End Errored Second OTU1 SM Section Far End Severely Errored Second OTU1 SM Section Ratio of Far End Severely Errored Second OTU1 SM Section Far End Unavailable Second OTU1 SM Section Introduced Alignment Errored Second OTU1 SM Section Severely Errored Second OTU1 SM Section Ratio of Severely Errored Second OTU1 SM Section Unavailable Second OTU2 SM Section Background Block Error OTU2 SM Section Ratio of Background Block Error OTU2 SM Section Background Introduced Alignment Errored Second OTU2 SM Section Errored Second OTU2 SM Section Far End Background Block Error OTU2 SM Section Ratio of Far End Background Block Error OTU2 SM Section Far End Errored Second OTU2 SM Section Far End Severely Errored Second OTU2 SM Section Ratio of Far End Severely Errored Second OTU2 SM Section Far End Unavailable Second
Issue 02 (2011-10-31)
743
Name OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS OTU2SMBIP8 OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS OTU5G_BBE OTU5G_BBER
Description OTU2 SM Section Introduced Alignment Errored Second OTU2 SM Section Severely Errored Second OTU2 SM Section Ratio of Severely Errored Second OTU2 SM Section Unavailable Second Number of bit errors in the optical channel transport unit OTU3 SM Section Background Block Error OTU3 SM Section Ratio of Background Block Error OTU3 SM Section Background Introduced Alignment Errored Second OTU3 SM Section Errored Second OTU3 SM Section Far End Background Block Error OTU3 SM Section Ratio of Far End Background Block Error OTU3 SM Section Far End Errored Second OTU3 SM Section Far End Severely Errored Second OTU3 SM Section Ratio of Far End Severely Errored Second OTU3 SM Section Far End Unavailable Second OTU3 SM Section Introduced Alignment Errored Second OTU3 SM Section Severely Errored Second OTU3 SM Section Ratio of Severely Errored Second OTU3 SM Section Unavailable Second OTU5G SM Section Background Block Error OTU5G SM Section Ratio of Background Block Error
Issue 02 (2011-10-31)
744
Name OTU5G_BIAES OTU5G_ES OTU5G_FEBBE OTU5G_FEBBER OTU5G_FEES OTU5G_FESES OTU5G_FESESR OTU5G_FEUAS OTU5G_IAES OTU5G_SES OTU5G_SESR OTU5G_UAS
Description OTU5G SM Section Background Introduced Alignment Errored Second OTU5G SM Section Errored Second OTU5G SM Section Far End Background Block Error OTU5G SM Section Ratio of Far End Background Block Error OTU5G SM Section Far End Errored Second OTU5G SM Section Far End Severely Errored Second OTU5G SM Section Ratio of Far End Severely Errored Second OTU5G SM Section Far End Unavailable Second OTU5G SM Section Introduced Alignment Errored Second OTU5G SM Section Severely Errored Second OTU5G SM Section Ratio of Severely Errored Second OTU5G SM Section Unavailable Second
5.1.9 Performance Event List of RMON Function

Lists the performance event of RMON function. Table 5-11 RMON Performance Event List Name ETHDROP (Drop Events) Description The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
745
RXOCTETS (Octets Received)
Issue 02 (2011-10-31)
Name RXPKTS (Packets Received)
Description The total number of packets (including bad packets, broadcast packets, and multicast packets) received. The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets. The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address. The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed. The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
RXBRDCAST (Broadcast Packets Received)
RXMULCAST (Multicast Packets Received)
ETHCRCALI (FCS and Alignment Errors)
ETHUNDER (Undersize Packets Received)
ETHOVER (Oversize Packets Received)
ETHFRG (Fragments)
ETHJAB (Jabbers)
RXPKT64 (Packets Received, 64 Octets in Length)
Issue 02 (2011-10-31)
746
Name RXPKT65 (Packets Received, 65~127 Octets in Length)
Description The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received that were between 1519 and MTU octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received and transmitted that were 64 octets in length (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received and transmitted that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received and transmitted that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received and transmitted that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
RXPKT128 (Packets Received, 128~255 Octets in Length)
RXPKT1519 (Packets Received, 1519~MTU Octets in Length)
PKT64 (Packets Received and Transmitted, 64 Octets in Length)
PKT65 (Packets Received and Transmitted, 65~127 Octets in Length)
Issue 02 (2011-10-31)
747
Name PKT512 (Packets Received and Transmitted, 512~1023 Octets in Length)
Description The total number of packets (including bad packets) received and transmitted that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) received and transmitted that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). The total number of transmitted octets of good packets (including framing bits and FCS octets). The total number of received octets of good packets (including framing bits and FCS octets). The rate of transmitted octets of good packets (including framing bits and FCS octets). The rate of received octets of good packets (including framing bits and FCS octets). The total number of transmitted octets of good packets. The total number of received octets of good packets. The rate of octets of data (including those in bad packets) transmitted on the network (excluding framing bits but including FCS octets). The rate of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted that were 64 octets in length (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
TXFULLBGOOD (Good Full Frame Octets Transmitted) RXFULLBGOOD (Good Full Frame Octets Received) TXGOODFULLFRAMESPEED (Good Full Frame Speed Transmitted) RXGOODFULLFRAMESPEED (Good Full Frame Speed Received) VCG_TXGOODPACKETS (Good Packets Transmitted) VCG_RXGOODPACKETS (Good Packets Received) VCG_TXSPEED (Full Frame Speed Transmitted)
VCG_RXSPEED (Full Frame Speed Received)
TXPKT64 (Packets Transmitted, 64 Octets in Length)
TXPKT65 (Packets Transmitted, 65~127 Octets in Length)
Issue 02 (2011-10-31)
748
Name TXPKT128 (Packets Transmitted, 128~255 Octets in Length)
Description The total number of packets (including bad packets) transmitted that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). The total number of packets (including bad packets) transmitted that were between 1519 and MTU octets in length inclusive (excluding framing bits but including FCS octets). The total number of good packets received that were directed to a unicast address. The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.
TXPKT1519 (Packets Transmitted, 1519~MTU Octets in Length)
RXUNICAST (Unicast Packets Received) TXUNICAST (Unicast Packets Transmitted)
TXMULCAST (Multicast Packets Transmitted)
TXBRDCAST (Broadcast Packets Transmitted)
RXPAUSE (Pause Frames Received)
Issue 02 (2011-10-31)
749
Name TXPAUSE (Pause Frames Transmitted)
Description A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. The total number of octets of good packets received on the network (excluding framing bits but including FCS octets). The total number of octets of good packets transmitted on the network (excluding framing bits but including FCS octets). The total number of octets of bad packets received on the network (excluding framing bits but including FCS octets). The total number of octets of bad packets transmitted on the network (excluding framing bits but including FCS octets). A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error. A count of MAC Control frames received on this interface with an opcode indicating the special operation. A count of MAC Control frames transmitted on this interface with an opcode indicating the special operation. The total number of events in which packets were dropped by the probe due to lack of resources at transmission direction. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. The total number of packets transmitted that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. The total number of packets (including bad packets, broadcast packets, and multicast packets) Transmitted.
RXBGOOD (Good Octets Received)
TXBGOOD (Good Octets Transmitted)
RXBBAD (Bad Octets Received)
TXBBAD (Bad Octets Transmitted)
ETHALI (Alignment Errors)
ETHFCS (FCS Errors)
RXCTLPKTS (Control Frames Received)
TXCTLPKTS (Control Frames Transmitted)
TXETHDROP (Drop Events at Transmission Direction)
TXETHOVER (Oversize Packets Transmitted)
TXPKTS (Packets Transmitted)
Issue 02 (2011-10-31)
750
Name TXOCTETS (Octets Transmitted)
Description The total number of octets of data (including those in bad packets) Transmitted on the network (excluding framing bits but including FCS octets).
5.1.10 TCM Performance Event

TCM performance events are used to monitor the transmission performance in the tandem connection. Table 5-12 TCM performance event list Name TCBBE TCFEBBE TCOBBE Description Tandem Connection Background Block Error Tandem Connection Far End Background Block Error Tandem Connection Outgoing Background Block Error
5.1.11 Performance Event of FC

Lists of the performance event of FC service. Name The total number of frames with wrong CRC that the FC channel received in client side. The total number of times that the link reseted in both client and WAN side. The total number of frames, with the type of Class1, that the FC channel received in client side. The total number of frames, with the type of Class2, that the FC channel received in client side. The total number of frames, with the type of Class3, that the FC channel received in client side. The total number of frames, with the type of Class4, that the FC channel received in client side. The total number of frames, with the type of Classf, that the FC channel received in client side.
Issue 02 (2011-10-31)
751
Name The total number of frames that the FC channel received in client side. The total number of frames, with the type of Class1, that the FC channel transmitted in client side. The total number of frames, with the type of Class2, that the FC channel transmitted in client side. The total number of frames, with the type of Class3, that the FC channel transmitted in client side. The total number of frames, with the type of Class4, that the FC channel transmitted in client side. The total number of frames, with the type of Classf, that the FC channel transmitted in client side. The total number of frames that the FC channel transmitted in client side. The total number of bytes that the FC channel received in client side. The total number of bytes that the FC channel transmitted in client side. The count of OS that the FC channel can't support.
5.2 Board Performance Event List

This section list the performance event of every board.
5.2.1 CRPC Board Performance Event List

BCVCUR BCVMAX BCVMIN CCVCUR CCVMAX CCVMIN EDTPLCUR EDTPLMAX EDTPLMIN ENVTMPCUR ENVTMPMAX ENVTMPMIN LSIOPMAX LSIOPMIN LSIOPCUR WCVCUR WCVMAX WCVMIN OOPRLMAX OOPRLMIN OOPRLCUR
5.2.2 DAS1 Board Performance Event List

BCVCUR BCVMAX
Issue 02 (2011-10-31)
LSBIASMIN LSIOPCUR
OSC_FEUAS OSC_IAES
752
BCVMIN CCVCUR CCVMAX CCVMIN EDTMPCUR EDTMPMAX EDTMPMIN FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX
LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN OSC_BBE OSC_BBER OSC_BIAES OSC_ES OSC_FEBBE OSC_FEBBER OSC_FEES OSC_FESES OSC_FESESR
OSC_SES OSC_SESR OSC_UAS SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN WCVCUR WCVMAX WCVMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
5.2.3 D40V Board Performance Event List

ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.4 D40 Board Performance Event List

TN12D40 ICCLCCUR ICCLCMAX
Issue 02 (2011-10-31)
ICTMPMIN SUMIOPCUR
SUMOOPMAX SUMOOPMIN
753
ICCLCMIN ICTMPCUR ICTMPMAX
SUMIOPMAX SUMIOPMIN SUMOOPCUR
XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN11D40 ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.5 DCP Board Performance Event List

LSIOPCUR LSIOPMAX LSIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.6 EGSH Board Performance Event List

HPBBE HPES HPCSES HPFEBBE HPFEES HPFECSES HPFESES HPFEUAS HPSES HPUAS LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN VC3BBE VC3CSES VC3ES VC3FEBBE VC3FECSES VC3FEES VC3FESES VC3FEUAS VC3SES VC3UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
RMON Performance Event List

Broadcast Packets Transmitted Broadcast Packets Received Control Frames Received Control Frames Transmitted Drop Events FCS Errors Fragments Full Frame Speed Received Full Frame Speed Transmitted Good Full Frame Octets Received Good Full Frame Octets Transmitted Good Full Frame Speed Received Good Full Frame Speed Transmitted Good Packets Received Good Packets Transmitted Jabbers
Multicast Packets Received Multicast Packets Transmitted Octets Received Octets Transmitted Oversize Packets Received Packets Received Packets Received and Transmitted (1024~1518 Octets in Length) Packets Received and Transmitted (128~255 Octets in Length) Packets Received and Transmitted (256~511 Octets in Length) Packets Received and Transmitted (512~1023 Octets in Length) Packets Received and Transmitted (64 Octets in Length) Packets Received and Transmitted (65~127 Octets in Length) Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length)
Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted(128~255 Octets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
5.2.7 EAS2 Board Performance Event List

HPBBE HPCSES HPES
Issue 02 (2011-10-31)
HPUAS LSBISACUR LSBISAMAX

LSOOPMIN LSTMPCUR LSTMPMAX

755
HPFEBBE HPFECSES HPFEES HPFESES HPFEUAS HPSES
LSBISAMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX
LSTMPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.8 ECOM Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
RMON Performance Event List Undersize Packets Received Unicast Packets Received Broadcast Packets Transmitted Good Octets Received FCS Errors
Broadcast Packets Received Fragments Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted Oversize Packets Transmitted
Multicast Packets Received Jabbers Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received
5.2.9 ELQX Board Performance Event List

FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS
Issue 02 (2011-10-31)
756
FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR
ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER
ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
Issue 02 (2011-10-31)
757

NOTE
NOTE
RMON Performance Event List Octets Received Packets Received Broadcast Packets Received Multicast Packets Received Undersize Packets Received Oversize Packets Received Fragments Jabbers Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Alignment Errors FCS Errors Packets Transmitted Octets Transmitted
5.2.10 ENQ2 Board Performance Event List

TN54ENQ2(STND) XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN54ENQ2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR

Issue 02 (2011-10-31)
ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS
ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE

758
FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS
ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER
ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
Issue 02 (2011-10-31)
759
5.2.11 FIU Board Performance Event List

SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.12 HSC1 Board Performance Event List

CRC4BBE CRC4ES CRC4FEBBE CRC4FEES CRC4FESES CRC4FEUAS CRC4SES CRC4UAS LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.13 HBA Board Performance Event List

BCVCUR BCVMAX BCVMIN CCVCUR CCVMAX CCVMIN EDTMPCUR EDTMPMAX EDTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN WCVCUR WCVMAX WCVMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.14 ITL Board Performance Event List

Issue 02 (2011-10-31)
760
5.2.15 L4G Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU5G_PM_BBE ODU5G_PM_BBER ODU5G_PM_ES ODU5G_PM_FEBBE ODU5G_PM_FEBBER ODU5G_PM_FEES ODU5G_PM_FESES ODU5G_PM_FESESR ODU5G_PM_FEUAS ODU5G_PM_SES ODU5G_PM_SESR ODU5G_PM_UAS ODU5G_TCMn_BBE ODU5G_TCMn_BBER ODU5G_TCMn_BIAES ODU5G_TCMn_ES ODU5G_TCMn_FEBBE ODU5G_TCMn_FEBBER ODU5G_TCMn_FEES ODU5G_TCMn_FESES ODU5G_TCMn_FESESR ODU5G_TCMn_FEUAS ODU5G_TCMn_IAES ODU5G_TCMn_SES ODU5G_TCMn_SESR ODU5G_TCMn_UAS OTU5G_BBE OTU5G_BBER OTU5G_BIAES OTU5G_ES OTU5G_FEBBE OTU5G_FEBBER OTU5G_FEES OTU5G_FESES OTU5G_FESESR OTU5G_FEUAS OTU5G_IAES OTU5G_SES OTU5G_SESR OTU5G_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE

Octets Received Multicast Packets Received Fragments
Packets Received Undersize Packets Received Jabbers
Broadcast Packets Received Oversize Packets Received Packets Received and Transmitted (64 Octets in Length) Packets Received and Transmitted (256~511 Octets in Length) Unicast Packets Received
Packets Received and Transmitted (65~127 Octets in Length) Packets Received and Transmitted (512~1023 Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Control Frames Received Packets Transmitted
Packets Received and Transmitted (128~255 Octets in Length) Packets Received and Transmitted (1024~1518 Octets in Length) Broadcast Packets Transmitted Alignment Errors Control Frames Transmitted Octets Transmitted
Pause Frames Received FCS Errors Oversize Packets Transmitted
5.2.16 LDGD Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX MSFEES MSFESES MSFEUAS MSSES MSUAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS
Issue 02 (2011-10-31)
762
LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSCSES MSES MSFEBBE MSFECSES
ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES
OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Drop Events Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length)
Issue 02 (2011-10-31)
763
Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted
Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted FCS Errors
Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received
5.2.17 LDGS Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN MSFEES MSFESES MSFEUAS MSSES MSUAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES
Issue 02 (2011-10-31)
764
LSTMPCUR LSTMPMAX LSTMPMIN MSBBE MSCSES MSES MSFEBBE MSFECSES
ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES
RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Drop Events Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted FCS Errors Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received
Issue 02 (2011-10-31)
765
5.2.18 LDM Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE

Broadcast Packets Received Multicast Packets Received
Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Unicast Packets Transmitted
Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Undersize Packets Received Oversize Packets Received Fragments Jabbers Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length)
Alignment Errors
Drop Events at Transmission Direction Oversize Packets Transmitted
5.2.19 LDMD Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES
Issue 02 (2011-10-31)
767
LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE
ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR
OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted
Undersize Packets Received Oversize Packets Received
Issue 02 (2011-10-31)
768
Fragments Jabbers Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length)
Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Unicast Packets Transmitted
Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Alignment Errors
5.2.20 LDMS Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX
Issue 02 (2011-10-31)
ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE
ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE
769
LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE
ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR
RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length)
Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Undersize Packets Received Oversize Packets Received Fragments Jabbers Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Received(128~255 Octets in Length)
Alignment Errors
Issue 02 (2011-10-31)
770
Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length)
Unicast Packets Received Unicast Packets Transmitted
5.2.21 LDX Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
Issue 02 (2011-10-31)
771

NOTE
RMON Performance Event List Alignment Errors Broadcast Packets Transmitted Broadcast Packets Received FCS Errors Fragments Jabbers Multicast Packets Received Multicast Packets Transmitted Octets Received Octets Transmitted Oversize Packets Received Packets Received Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted Packets Transmitted(1024~1518 Octets in Length) Packets Transmitted(128~255 Octets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
5.2.22 LEM24 Board Performance Event List

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_CN T LSBIASCUR LSBIASMAX
Issue 02 (2011-10-31)
ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR
ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR
772
LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE
ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
5.2.23 LEX4 Board Performance Event List

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_CN T LSBIASCUR LSBIASMAX
Issue 02 (2011-10-31)
773
LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE
ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
NOTE
NOTE
5.2.24 LOA Board Performance Event List

FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT
Issue 02 (2011-10-31)
ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE
ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR

774
FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE
ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR
ODUFLEX_PM_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE
Issue 02 (2011-10-31)
775
ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS
ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES
RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
5.2.25 LOG Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSTMPMAX LSTMPMIN ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODU3_PM_BBE OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES
Issue 02 (2011-10-31)
776
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR
ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS
OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Drop Events Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted FCS Errors Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received
Issue 02 (2011-10-31)
777

NOTE
In the GFP-T mode, the TN11LOG board does not support the RMON performance event.
5.2.26 LOM Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBISACUR LSBISAMAX LSBISAMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
Issue 02 (2011-10-31)
778
RMON Performance Event List Drop Events Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted Oversize Packets Transmitted Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted FCS Errors Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received Drop Events at Transmission Direction
FC Performance Event List CLIENT_CRC_ERR FC_Client_CreditZero_Cnt FC_Client_Invld_10BCode_ Cnt CLIENT_RXBYTECNT_S UM CLIENT_RXFRMCNT_C1 FC_Client_RxOLSPrim_ Cnt FC_Client_Truncated FrmCnt_sum FC_Client_Tx_NOS_Cnt FC_Client_Tx_Utilization CLIENT_TXBYTECNT_ SUM LINKTST_CNT FC_Wsys_Crc_Err_Cnt FC_Wsys_LinkDown_Cnt FC_Wsys_OverLongFrm_Su m FC_Wsys_Rx_PausePrim_Cn t
Issue 02 (2011-10-31)
779
CLIENT_RXFRMCNT_C2 CLIENT_RXFRMCNT_C3 CLIENT_RXFRMCNT_C4 CLIENT_RXFRMCNT_CF CLIENT_RXFRMCNT_SU M FC_Client_Rx_NOS_Cnt FC_Client_Rx_Utilization FC_Client_OverLongFrm_S um FC_Client_RxLRPrim_Cnt FC_Client_RxLRRPrim_Cnt
CLIENT_TXFRMCNT_C 1 CLIENT_TXFRMCNT_C 2 CLIENT_TXFRMCNT_C 3 CLIENT_TXFRMCNT_C 4 CLIENT_TXFRMCNT_C F CLIENT_TXFRMCNT_S UM CLIENT_UNSUPOS_CN T FC_Client_TxLRPrim_Cn t FC_Client_TxLRRPrim_ Cnt FC_Client_TxOLSPrim_ Cnt
FC_Wsys_Rx_PingAckPrim_ Cnt FC_Wsys_Rx_PingPrim_Cnt FC_Wsys_Rx_ResumePrim_ Cnt FC_Wsys_Truncated FrmCnt_sum FC_Wsys_Tx_PausePrim_Cn t FC_Wsys_Tx_PingAckPrim_ Cnt FC_Wsys_Tx_PingPrim_Cnt FC_Wsys_Tx_ResumePrim_ Cnt FC_Wsys_unsupos_cnt
5.2.27 LQMD Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS
Issue 02 (2011-10-31)
780
LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE SEFS_S
ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR RSOFS
OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List TN11LQMD Drop Events FCS and Alignment Errors Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Broadcast Packets Received Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Multicast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length)
Issue 02 (2011-10-31)
781
Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received Oversize Packets Transmitted
Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received
Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted
Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted
Pause Frames Received Good Octets Transmitted Drop Events at Transmission Direction
TN12LQMD Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Broadcast Packets Transmitted Pause Frames Received
Drop Events
Broadcast Packets Received Multicast Packets Received Undersize Packets Received Oversize Packets Received Fragments Jabbers Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Received(128~255 Octets in Length)
Pause Frames Transmitted Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted Alignment Errors
Issue 02 (2011-10-31)
782
Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length)
Unicast Packets Transmitted Multicast Packets Transmitted
5.2.28 LQMS Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
Issue 02 (2011-10-31)
783
SEFS_S
RSOFS
NOTE
NOTE
RMON Performance Event List TN11LQMS Drop Events FCS and Alignment Errors Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received Oversize Packets Transmitted Broadcast Packets Received Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Multicast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted
Multicast Packets Broadcast Good Octets Received Bad Octets Transmitted
Pause Frames Received Good Octets Transmitted Drop Events at Transmission Direction
TN12LQMS Packets Received (1024~1518 Octets in Length) Multicast Packets Transmitted

784
Broadcast Packets Received

Issue 02 (2011-10-31)
Multicast Packets Received
Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Unicast Packets Transmitted
Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Alignment Errors
5.2.29 LQM Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX
Issue 02 (2011-10-31)
785
LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE SEFS_S
ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR RSOFS
NOTE
NOTE
RMON Performance Event List Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Good Octets Received
Undersize Packets Received Oversize Packets Received Fragments
Issue 02 (2011-10-31)
786
Jabbers Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length)
Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Unicast Packets Transmitted
Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Alignment Errors
5.2.30 LSQ Board Performance Event List

FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR
Issue 02 (2011-10-31)
ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE
ODU3_TCMn_UAS OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS RSBBE RSCSES
787
LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN
RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.31 LSXLR Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOA T FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN
Issue 02 (2011-10-31)
LSTMPMAX LSTMPMIN ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER
ODU3_TCMn_FEUAS ODU3_TCMn_IAES ODU3_TCMn_SES ODU3_TCMn_SESR ODU3_TCMn_UAS OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES
788
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR
ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE ODU3_TCMn_FEBBER ODU3_TCMn_FEES ODU3_TCMn_FESES ODU3_TCMn_FESESR
OTU3_SES OTU3_SESR OTU3_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.32 LSXL Board Performance Event List

TN11LSXL/TN12LSXL FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE ODU3_TCMn_UAS OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS RSBBE RSCSES
Issue 02 (2011-10-31)
789
LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN
RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.33 LSXR Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOA T FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN
Issue 02 (2011-10-31)
ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES
ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE
790
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN
ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
NOTE
NOTE
5.2.34 LSX Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOA T FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOA T FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES
Issue 02 (2011-10-31)
791
LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN
ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Octets Received Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Transmitted Packets Received Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Multicast Packets Transmitted Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Unicast Packets Received
Broadcast Packets Transmitted

792
Issue 02 (2011-10-31)
Pause Frames Received FCS Errors
Pause Frames Transmitted Packets Transmitted
Alignment Errors Octets Transmitted
5.2.35 LWX2 Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.36 LWXD Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.37 LWXS Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR
Issue 02 (2011-10-31)
LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN

RSCSES RSES RSOFS RSSES

793
LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX
LSTMPCUR LSTMPMAX LSTMPMIN RSBBE
RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.38 M40V Board Performance Event List

ICTMPCUR ICTMPMAX ICTMPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.39 M40 Board Performance Event List

TN12M40 ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN11M40 ICCLCCUR ICCLCMAX ICCLCMIN ICTMPCUR ICTMPMAX ICTMPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.40 MCA4 Board Performance Event List

PCLSOPCUR PCLSOPMAX PCLSOPMIN
Issue 02 (2011-10-31)
PCLSSNMIN PCLSWLCUR PCLSWLMAX

PCLSWLOMAX PCLSWLOMIN XCSTMPCUR

794
PCLSSNCUR PCLSSNMAX
PCLSWLMIN PCLSWLOCUR
XCSTMPMAX XCSTMPMIN
5.2.41 MCA8 Board Performance Event List

PCLSOPCUR PCLSOPMAX PCLSOPMIN PCLSSNCUR PCLSSNMAX PCLSSNMIN PCLSWLCUR PCLSWLMAX PCLSWLMIN PCLSWLOCUR PCLSWLOMAX PCLSWLOMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.42 MR8V Board Performance Event List

5.2.43 ND2 Board Performance Event List

TN53ND2 FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT ODU0_TCMn_FESES ODU0_TCMn_FESESR ODU0_TCMn_FEUAS ODU0_TCMn_IAES ODU0_TCMn_SES ODU0_TCMn_SESR ODU0_TCMn_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR
Issue 02 (2011-10-31)
795
LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU0_TCMn_BBE ODU0_TCMn_BBER ODU0_TCMn_BIAES ODU0_TCMn_ES
ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR
ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS
Issue 02 (2011-10-31)
796
ODU0_TCMn_FEBBE ODU0_TCMn_FEBBER ODU0_TCMn_FEES
ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR
TN53ND2 (COMP) FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES
Issue 02 (2011-10-31)
797
ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR
ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN52ND2 FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX
Issue 02 (2011-10-31)
ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER
ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES
798
LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR
ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN12ND2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR
Issue 02 (2011-10-31)
799
FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS
ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER
ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN11ND2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE
Issue 02 (2011-10-31)
800
FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES
ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE
Issue 02 (2011-10-31)
801

NOTE
NOTE
5.2.44 NQ2 Board Performance Event List

TN54NQ2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES
Issue 02 (2011-10-31)
ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS
ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR
802
ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE
ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES
OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN53NQ2 FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN
Issue 02 (2011-10-31)
ODU0_TCMn_FESES ODU0_TCMn_FESESR ODU0_TCMn_FEUAS ODU0_TCMn_IAES ODU0_TCMn_SES ODU0_TCMn_SESR ODU0_TCMn_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS
ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODUFLEX_PM_BBE
803
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU0_TCMn_BBE ODU0_TCMn_BBER ODU0_TCMn_BIAES ODU0_TCMn_ES ODU0_TCMn_FEBBE ODU0_TCMn_FEBBER ODU0_TCMn_FEES
ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR
ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN53NQ2 (COMP)
Issue 02 (2011-10-31)
804
FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES
ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE
ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS
Issue 02 (2011-10-31)
805
ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR
ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
TN52NQ2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER
Issue 02 (2011-10-31)
806
LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR
ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN51NQ2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER
Issue 02 (2011-10-31)
807
LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES
ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE
OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
5.2.45 NPO2 Board Performance Event List

FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE
Issue 02 (2011-10-31)
808
FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE
ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES
NOTE
Issue 02 (2011-10-31)
809
5.2.46 NPO2E Board Performance Event List

TN55NPO2E FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR
Issue 02 (2011-10-31)
810
ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE
ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES
OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.47 NS2 Board Performance Event List

TN53NS2 FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR
Issue 02 (2011-10-31)
ODU0_TCMn_FESES ODU0_TCMn_FESESR ODU0_TCMn_FEUAS ODU0_TCMn_IAES ODU0_TCMn_SES ODU0_TCMn_SESR ODU0_TCMn_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES
ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER
811
LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU0_TCMn_BBE ODU0_TCMn_BBER ODU0_TCMn_BIAES ODU0_TCMn_ES ODU0_TCMn_FEBBE ODU0_TCMn_FEBBER ODU0_TCMn_FEES
ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR
ODUFLEX_PM_ES ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN53NS2 (COMP) FEC_AFT_CORER_FLOAT ODU0_PM_UAS ODU2_PM_SES
Issue 02 (2011-10-31)
812
FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES
ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER
ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR
Issue 02 (2011-10-31)
813
ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR
ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
XCSTMPMAX XCSTMPMIN
TN52NS2 FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN
Issue 02 (2011-10-31)
ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR
ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE
814
LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR
ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN12NS2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE
Issue 02 (2011-10-31)
815
LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES
ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE
OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN11NS2 FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES
Issue 02 (2011-10-31)
816
LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES
ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE
ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
5.2.48 NS3 Board Performance Event List

TN54NS3 FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_UAS
Issue 02 (2011-10-31)
817
FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES
ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS
ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE ODU3_TCMn_FEBBER ODU3_TCMn_FEES ODU3_TCMn_FESES ODU3_TCMn_FESESR ODU3_TCMn_FEUAS ODU3_TCMn_IAES ODU3_TCMn_SES ODU3_TCMn_SESR ODU3_TCMn_UAS OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES
Issue 02 (2011-10-31)
818
ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES
ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN52NS3 FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU2_TCMn_UAS ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER
Issue 02 (2011-10-31)
819
LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES
ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE ODU3_TCMn_FEBBER ODU3_TCMn_FEES ODU3_TCMn_FESES ODU3_TCMn_FESESR ODU3_TCMn_FEUAS ODU3_TCMn_IAES ODU3_TCMn_SES ODU3_TCMn_SESR ODU3_TCMn_UAS OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN11NS3
ODU2_PM_ES FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU3_PM_BBE ODU3_PM_BBER ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE
ODU3_TCMn_FEBBE R ODU3_TCMn_FEES ODU3_TCMn_FESES ODU3_TCMn_FESES R ODU3_TCMn_FEUAS ODU3_TCMn_IAES ODU3_TCMn_SES ODU3_TCMn_SESR ODU3_TCMn_UAS OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
Issue 02 (2011-10-31)
821
5.2.49 OAU1 Board Performance Event List

5.2.50 OBU1 Board Performance Event List

5.2.51 OBU2 Board Performance Event List

Issue 02 (2011-10-31)
822
5.2.52 OLP Board Performance Event List

LSIOPCUR LSIOPMAX LSIOPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.53 OPM8 Board Performance Event List

PCLSOPCUR PCLSOPMAX PCLSOPMIN PCLSWLCUR PCLSWLMAX PCLSWLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.54 PTQX Board Performance Event List

FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR
Issue 02 (2011-10-31)
823
LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR
ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER
OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
RMON Performance Event List Octets Received Packets Received Broadcast Packets Received Multicast Packets Received Undersize Packets Received Packets Received (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (64 Octets in Length) Unicast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received
Issue 02 (2011-10-31)
824
Oversize Packets Received Fragments Jabbers Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length)
Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length)
Pause Frames Transmitted Alignment Errors FCS Errors Packets Transmitted Octets Transmitted
5.2.55 RDU9 Board Performance Event List

SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.56 RMU9 Board Performance Event List

ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.57 ROAM Board Performance Event List

ICTMPCUR ICTMPMAX ICTMPMIN LSOOPCUR LSOOPMAX LSOOPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
Issue 02 (2011-10-31)
825
5.2.58 SCC Board Performance Event List

TN16SCC AVGFREQDEV AVGMEANPATHDELA Y AVGPHASEOFFSET MAXFREQDEV MAXMEANPATHDELAY MAXPHASEOFFSET MINFREQDEV MINMEANPATHDELAY MINPHASEOFFSET XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.59 SC1 Board Performance Event List

CRC4BBE CRC4FEBBE CRC4ES CRC4FEES CRC4FESES CRC4FEUAS CRC4SES CRC4UAS LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.60 SC2 Board Performance Event List

CRC4BBE CRC4FEBBE CRC4ES CRC4FEES CRC4FESES CRC4FEUAS CRC4SES CRC4UAS LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.61 SFD64 Board Performance Event List

AUPJCHIGH HPFEUAS OTU2SMBIP8
Issue 02 (2011-10-31)
826
AUPJCLOW AUPJCNEW FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T HPBBE HPES HPCSES HPFEBBE HPFEES HPFECSES HPFESES
HPSES HPUAS MSBBE MSES MSCSES MSFEBBE MSFEES MSFECSES MSFESES MSFEUAS MSSES MSUAS ODU2PMBIP8 OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR OSPITMPMAX OSPITMPMIN
RPLCUR RPLMAX RPLMIN RSBBE RSCSES RSES RSOFS RSOOF RSSES RSUAS TLBCUR TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.62 SF64 Board Performance Event List

AUPJCHIGH AUPJCLOW AUPJCNEW FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER
Issue 02 (2011-10-31)
HPSES HPUAS MSBBE MSES MSCSES MSFEBBE MSFEES
RPLMAX RPLMIN RSBBE RSES RSOFS RSOOF RSSES

827
FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T HPBBE HPES HPCSES HPFEBBE HPFEES HPFESES HPFECSES HPFEUAS
MSFESES MSFECSES MSFEUAS MSSES MSUAS ODU2PMBIP8 OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR OSPITMPMAX OSPITMPMIN OTU2SMBIP8 RPLCUR
RSCSES RSUAS TCBBE TCFEBBE TCOBBE TLBCUR TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.63 SF64A Board Performance Event List

AUPJCHIGH AUPJCLOW AUPJCNEW FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T MSBBE MSES MSCSES MSFEBBE MSFEES MSFECSES MSFESES MSFEUAS MSSES MSUAS ODU2PMBIP8 RSBBE RSES RSCSES RSOFS RSOOF RSSES RSUAS TCBBE TCFEBBE TCOBBE TLBCUR
Issue 02 (2011-10-31)
828
HPBBE HPES HPFEBBE HPFEES HPFESES HPFECSES HPFEUAS HPCSES HPSES HPUAS
OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR OSPITMPMAX OSPITMPMIN OTU2SMBIP8 RPLCUR RPLMAX RPLMIN
TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.64 SL64 Board Performance Event List

AUPJCHIGH AUPJCLOW AUPJCNEW HPBBE HPES HPCSES HPFEBBE HPFEES HPFECSES HPFESES HPFEUAS HPSES HPUAS MSBBE MSCSES MSES MSFEBBE MSFEES MSFECSES MSFESES MSFEUAS MSSES MSUAS OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR OSPITMPMAX OSPITMPMIN RPLCUR RPLMAX RPLMIN RSBBE RSCSES RSES RSOFS RSOOF RSSES RSUAS TLBCUR TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
Issue 02 (2011-10-31)
829
5.2.65 SLD64 Board Performance Event List

5.2.66 SLH41 Board Performance Event List

AUPJCHIGH AUPJCLOW AUPJCNEW HPBBE HPES HPCSES HPFEBBE HPFEES HPFECSES HPFESES HPFEUAS
Issue 02 (2011-10-31)
MSFEBBE MSFEES MSFECSES MSFESES MSFEUAS MSSES MSUAS OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR
RSBBE RSCSES RSES RSOFS RSOOF RSSES RSUAS TLBCUR TLBMAX TLBMIN TPLCUR
830
HPSES HPUAS MSBBE MSCSES MSES
OSPITMPMAX OSPITMPMIN RPLCUR RPLMAX RPLMIN
TPLMAX TPLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.67 SLO16 Board Performance Event List

5.2.68 SLQ16 Board Performance Event List

AUPJCHIGH AUPJCLOW AUPJCNEW HPBBE MSFEBBE MSFEES MSFECSES MSFESES RSBBE RSCSES RSES RSOFS
Issue 02 (2011-10-31)
831
HPES HPCSES HPFEBBE HPFEES HPFECSES HPFESES HPFEUAS HPSES HPUAS MSBBE MSCSES MSES
MSFEUAS MSSES MSUAS OSPICCVCUR OSPICCVMAX OSPICCVMIN OSPITMPCUR OSPITMPMAX OSPITMPMIN RPLCUR RPLMAX RPLMIN
RSOOF RSSES RSUAS TLBCUR TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.69 SLQ64 Board Performance Event List

Issue 02 (2011-10-31)
832
5.2.70 ST2 Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN OSC_BBE OSC_BBER OSC_BIAES OSC_ES OSC_FEBBE OSC_FEBBER OSC_FEES OSC_FESES OSC_FESESR OSC_FEUAS OSC_IAES OSC_SES OSC_SESR OSC_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
5.2.71 STG Board Performance Event List

5.2.72 SXM Board Performance Event List

5.2.73 SXH Board Performance Event List

Issue 02 (2011-10-31)
833
5.2.74 TBE Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
RMON Performance Event List Drop Events Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Received and Transmitted (64 Octets in Length) Packets Received and Transmitted (256~511 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Octets Received Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Received and Transmitted (65~127 Octets in Length) Packets Received and Transmitted (512~1023 Octets in Length) Unicast Packets Transmitted Pause Frames Received Packets Received Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Received and Transmitted (128~255 Octets in Length) Packets Received and Transmitted (1024~1518 Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted
Issue 02 (2011-10-31)
834
FCS Errors Oversize Packets Transmitted
Control Frames Received Packets Transmitted
Control Frames Transmitted Octets Transmitted
5.2.75 TDC Board Performance Event List

LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.76 TDG Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
RMON Performance Event List Drop Events Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Broadcast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Multicast Packets Received Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length)
Issue 02 (2011-10-31)
835
Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted
Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted FCS Errors
Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received
5.2.77 TDX Board Performance Event List

TN53TDX FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS
Issue 02 (2011-10-31)
836
LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE
ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES
OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN52TDX FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT FEC_BEF_CORER_FL OAT FEC_AFT_CORER_FL OAT LSBIASCUR LSBIASMAX
Issue 02 (2011-10-31)
ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER
OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES
837
LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER
ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS
OTU2_SESR OTU2_UAS RSBBE RSES RSCSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN SEFS_S RSOFS
TN11TDX LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN12TDX LSBIASCUR LSBIASMAX LSTMPCUR LSTMPMAX ODU2_PM_SES ODU2_PM_SESR
Issue 02 (2011-10-31)
838
LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN SEFS_S
LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS RSOFS
ODU2_PM_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
RMON Performance Event List TN53TDX Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length)
Alignment Errors
Octets Transmitted Oversize Packets Received Oversize Packets Transmitted
Bad Octets Received
Bad Octets Transmitted
Broadcast Packets Received
Packets Received Packets Received (1024~1518 Octets in Length) Packets Received (128~255 Octets in Length) Packets Received (1519~MTU Octets in Length)
Broadcast Packets Transmitted
Control Frames Received
Control Frames Transmitted

Issue 02 (2011-10-31)
Pause Frames Received

839
FCS Errors
Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Transmitted Packets Transmitted (1024~1518 Octets in Length)
Pause Frames Transmitted Undersize Packets Received Unicast Packets Received Unicast Packets Transmitted
Fragments Jabbers Multicast Packets Received Multicast Packets Transmitted
Octets Received
TN52TDX Alignment Errors Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Control Frames Received Control Frames Transmitted FCS Errors Fragments Jabbers Multicast Packets Received Octets Transmitted Oversize Packets Received Oversize Packets Transmitted Packets Received Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted(128~255 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
Issue 02 (2011-10-31)
840
Multicast Packets Transmitted Octets Received
Packets Transmitted Packets Transmitted(1024~1518 Octets in Length)
TN11TDX Broadcast Packets Received Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted Control Frames Transmitted Multicast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted FCS Errors Oversize Packets Transmitted FCS and Alignment Errors Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received Control Frames Received
TN12TDX Octets Received Packets Received Undersize Packets Received Oversize Packets Received FCS Errors
Issue 02 (2011-10-31)
841
5.2.78 THA Board Performance Event List

FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS
Issue 02 (2011-10-31)
842
ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES
ODU1_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE
NOTE
RMON Performance Event List Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Drop Events Drop Events at Transmission Direction FCS Errors Fragments Good Octets Received Good Octets Transmitted Jabbers Multicast Packets Received Multicast Packets Transmitted Oversize Packets Received Oversize Packets Transmitted Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted(1024~1518 Octets in Length) Packets Transmitted(128~255 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted
Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
Issue 02 (2011-10-31)
843
5.2.79 TMX Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE
Issue 02 (2011-10-31)
844
ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE
NOTE
NOTE
5.2.80 TOA Board Performance Event List

FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE
Issue 02 (2011-10-31)
845
LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES
ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE
OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
RMON Performance Event List Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Multicast Packets Transmitted Oversize Packets Received Oversize Packets Transmitted Packets Received(1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length)
Issue 02 (2011-10-31)
846
Drop Events Drop Events at Transmission Direction FCS Errors Fragments Good Octets Received Good Octets Transmitted Jabbers Multicast Packets Received
Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted(1024~1518 Octets in Length) Packets Transmitted(128~255 Octets in Length)
Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted
5.2.81 TOG Board Performance Event List

LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS XCSTMPCUR XCSTMPMAX XCSTMPMIN

Bad Octets Received Multicast Packets Received Broadcast Packets Received FCS Errors Fragments Good Octets Received Jabbers Drop Events Oversize Packets Received Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length)
Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Pause Frames Received Undersize Packets Received Unicast Packets Received
5.2.82 TOM Board Performance Event List

TN52TOM FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_AFT_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN ODU0_PM_FESES ODU0_PM_FESESR ODU0_PM_FEUAS ODU0_PM_SES ODU0_PM_SESR ODU0_PM_UAS ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS OTU1_IAES OTU1_BIAES OTU1_BBE OTU1_ES OTU1_SES OTU1_UAS OTU1_SESR OTU1_BBER OTU1_FEBBE OTU1_FEES OTU1_FESES OTU1_FEUAS
Issue 02 (2011-10-31)
848
LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU0_PM_BBE ODU0_PM_BBER ODU0_PM_ES ODU0_PM_FEBBE ODU0_PM_FEBBER ODU0_PM_FEES
ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS
OTU1_FESESR OTU1_FEBBER RSBBE RSES RSOFS RSCSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN11TOM FEC_AFT_COR_ER FEC_BEF_COR_ER FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CNT LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES
Issue 02 (2011-10-31)
849
LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE SEFS_S
ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS RSOFS
RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
RMON Performance Event List TN52TOM Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Drop Events Drop Events at Transmission Direction FCS Errors Fragments Good Octets Transmitted Good Octets Received Jabbers Multicast Packets Transmitted Oversize Packets Received Oversize Packets Transmitted Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted
Issue 02 (2011-10-31)
850
Multicast Packets Received
Packets Transmitted(128~255 Octets in Length)
TN11TOM Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Undersize Packets Received Oversize Packets Received Fragments Jabbers Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Drop Events
FCS Errors
5.2.83 TQM Board Performance Event List

TN11TQM LSBIASCUR LSBIASMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_SESR ODU1_PM_UAS
Issue 02 (2011-10-31)
851
LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX
ODU1_PM_BBER ODU1_PM_ES ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES
RSBBE RSCSES RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN12TQM FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSSES RSUAS
Issue 02 (2011-10-31)
852
LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES SEFS_S
ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS RSOFS
NOTE
RMON Performance Event List TN11TQM Drop Events FCS Errors Fragments Packets Received (65~127 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Transmitted (64 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Multicast Packets Transmitted Pause Frames Transmitted Bad Octets Received Oversize Packets Transmitted Broadcast Packets Received Undersize Packets Received Jabbers Packets Received (128~255 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Unicast Packets Received Multicast Packets Received Oversize Packets Received Packets Received (64 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Unicast Packets Transmitted Pause Frames Received Good Octets Transmitted Drop Events at Transmission Direction
Broadcast Packets Transmitted Good Octets Received Bad Octets Transmitted
Issue 02 (2011-10-31)
853
TN12TQM Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Unicast Packets Received Unicast Packets Transmitted Multicast Packets Transmitted Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted Good Octets Received Good Octets Transmitted Bad Octets Received Bad Octets Transmitted
Alignment Errors
5.2.84 TQS Board Performance Event List

FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT ODU1_PM_FEBBE ODU1_PM_FEBBER ODU1_PM_FEES ODU1_PM_FESES ODU1_PM_FESESR ODU1_PM_FEUAS ODU1_PM_SES OTU1_BBE OTU1_BBER OTU1_BIAES OTU1_ES OTU1_FEBBE OTU1_FEBBER OTU1_FEES
Issue 02 (2011-10-31)
854
FEC_UNCOR_BLOCK_C NT LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU1_PM_BBE ODU1_PM_BBER ODU1_PM_ES
ODU1_PM_SESR ODU1_PM_UAS ODU1_TCMn_BBE ODU1_TCMn_BBER ODU1_TCMn_BIAES ODU1_TCMn_ES ODU1_TCMn_FEBBE ODU1_TCMn_FEBBER ODU1_TCMn_FEES ODU1_TCMn_FESES ODU1_TCMn_FESESR ODU1_TCMn_FEUAS ODU1_TCMn_IAES ODU1_TCMn_SES ODU1_TCMn_SESR ODU1_TCMn_UAS
OTU1_FESES OTU1_FESESR OTU1_FEUAS OTU1_IAES OTU1_SES OTU1_SESR OTU1_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
NOTE
5.2.85 TQX Board Performance Event List

TN55TQX FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODUFLEX_PM_FESESR ODUFLEX_PM_FEUAS ODUFLEX_PM_SES ODUFLEX_PM_SESR ODUFLEX_PM_UAS
Issue 02 (2011-10-31)
855
FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE
ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS ODUFLEX_PM_BBE ODUFLEX_PM_BBER ODUFLEX_PM_ES ODUFLEX_PM_FEBBE ODUFLEX_PM_FEBBER ODUFLEX_PM_FEES ODUFLEX_PM_FESES
OTU2_BBE OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN53TQX FEC_AFT_CORER_FLO AT FEC_AFT_COR_ER ODU2_PM_BBE ODU2_PM_BBER ODU2_TCMn_UAS OTU2_BBE
Issue 02 (2011-10-31)
856
FEC_AFT_COR_ERAV R FEC_BEF_CORER_FLO AT FEC_BEF_COR_ER FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN
ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR
OTU2_BBER OTU2_BIAES OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN52TQX FEC_AFT_COR_ER FEC_AFT_COR_ERAV R FEC_BEF_COR_ER

Issue 02 (2011-10-31)
ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER
OTU2_BBE OTU2_BBER OTU2_BIAES

857
FEC_BEF_COR_ERAV R FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_ CNT FEC_BEF_CORER_FL OAT FEC_AFT_CORER_FL OAT LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER
ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS ODU2_TCMn_BBE ODU2_TCMn_BBER ODU2_TCMn_BIAES ODU2_TCMn_ES ODU2_TCMn_FEBBE ODU2_TCMn_FEBBER ODU2_TCMn_FEES ODU2_TCMn_FESES ODU2_TCMn_FESESR ODU2_TCMn_FEUAS ODU2_TCMn_IAES ODU2_TCMn_SES ODU2_TCMn_SESR ODU2_TCMn_UAS
OTU2_ES OTU2_FEBBE OTU2_FEBBER OTU2_FEES OTU2_FESES OTU2_FESESR OTU2_FEUAS OTU2_IAES OTU2_SES OTU2_SESR OTU2_UAS RSBBE RSES RSCSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN SEFS_S RSOFS
TN11TQX LSBIASCUR LSBIASMAX LSBIASMIN LSCLCCUR LSCLCMAX LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS RSBBE RSCSES
Issue 02 (2011-10-31)
858
LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN SEFS_S
ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS RSOFS
RSES RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
RMON Performance Event List TN55TQX Alignment Errors Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Control Frames Received Control Frames Transmitted FCS Errors Fragments Jabbers Multicast Packets Received Octets Transmitted Oversize Packets Received Oversize Packets Transmitted Packets Received Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted(128~255 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
Issue 02 (2011-10-31)
859
Multicast Packets Transmitted Octets Received
Packets Transmitted Packets Transmitted(1024~1518 Octets in Length)
TN53TQX Alignment Errors Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Control Frames Received Control Frames Transmitted FCS Errors Fragments Jabbers Multicast Packets Received Multicast Packets Transmitted Octets Received Octets Transmitted Oversize Packets Received Oversize Packets Transmitted Packets Received Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted Packets Transmitted(1024~1518 Octets in Length) Packets Transmitted(128~255 Octets in Length) Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
TN52TQX Alignment Errors Octets Transmitted Packets Transmitted(128~255 Octets in Length)
Issue 02 (2011-10-31)
860
Bad Octets Received Bad Octets Transmitted Broadcast Packets Transmitted Broadcast Packets Received Control Frames Received Control Frames Transmitted FCS Errors Fragments Jabbers Multicast Packets Received Multicast Packets Transmitted Octets Received
Oversize Packets Received Oversize Packets Transmitted Packets Received Packets Received(1024~1518 Octets in Length) Packets Received(128~255 Octets in Length) Packets Received(1519~MTU Octets in Length) Packets Received(256~511 Octets in Length) Packets Received(512~1023 Octets in Length) Packets Received(64 Octets in Length) Packets Received(65~127 Octets in Length) Packets Transmitted Packets Transmitted(1024~1518 Octets in Length)
Packets Transmitted (1519~MTUOctets in Length) Packets Transmitted(256~511 Octets in Length) Packets Transmitted(512~1023 Octets in Length) Packets Transmitted(64 Octets in Length) Packets Transmitted(65~127 Octets in Length) Pause Frames Transmitted Pause Frames Received Undersize Packets Received Unicast Packets Transmitted Unicast Packets Received
TN11TQX Octets Received Packets Received Undersize Packets Received Oversize Packets Received FCS Errors
5.2.86 TSXL Board Performance Event List

TN11TSXL LSBIASCUR LSBIASMAX LSBIASMIN LSTMPCUR LSTMPMAX LSTMPMIN ODU2_PM_SES ODU2_PM_SESR ODU2_PM_UAS
Issue 02 (2011-10-31)
861
LSCLCCUR LSCLCMAX LSCLCMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN
ODU2_PM_BBE ODU2_PM_BBER ODU2_PM_ES ODU2_PM_FEBBE ODU2_PM_FEBBER ODU2_PM_FEES ODU2_PM_FESES ODU2_PM_FESESR ODU2_PM_FEUAS
RSBBE RSCSES RSES RSOFS RSSES RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN53TSXL FEC_AFT_CORER_FLOAT FEC_AFT_COR_ER FEC_AFT_COR_ERAVR FEC_BEF_CORER_FLOAT FEC_BEF_COR_ER FEC_BEF_COR_ERAVR FEC_COR_0BIT_CNT FEC_COR_1BIT_CNT FEC_COR_BYTE_CNT FEC_UNCOR_BLOCK_CN T LSBIASCUR LSBIASMAX LSBIASMIN LSIOPCUR LSIOPMAX LSIOPMIN LSOOPCUR LSOOPMAX LSOOPMIN ODU3_PM_ES ODU3_PM_FEBBE ODU3_PM_FEBBER ODU3_PM_FEES ODU3_PM_FESES ODU3_PM_FESESR ODU3_PM_FEUAS ODU3_PM_SES ODU3_PM_SESR ODU3_PM_UAS ODU3_TCMn_BBE ODU3_TCMn_BBER ODU3_TCMn_BIAES ODU3_TCMn_ES ODU3_TCMn_FEBBE ODU3_TCMn_FEBBER ODU3_TCMn_FEES ODU3_TCMn_FESES ODU3_TCMn_FESESR OTU3_BBE OTU3_BBER OTU3_BIAES OTU3_ES OTU3_FEBBE OTU3_FEBBER OTU3_FEES OTU3_FESES OTU3_FESESR OTU3_FEUAS OTU3_IAES OTU3_SES OTU3_SESR OTU3_UAS RSBBE RSCSES RSES RSOFS RSSES
Issue 02 (2011-10-31)
862
LSTMPCUR LSTMPMAX LSTMPMIN ODU3_PM_BBE ODU3_PM_BBER
ODU3_TCMn_FEUAS ODU3_TCMn_IAES ODU3_TCMn_SES ODU3_TCMn_SESR ODU3_TCMn_UAS
RSUAS XCSTMPCUR XCSTMPMAX XCSTMPMIN
NOTE
RMON Performance Event List FCS Errors Pause Frames Transmitted Packets Transmitted (64 Octets in Length) Packets Transmitted (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Transmitted (256~511 Octets in Length) Packets Transmitted (512~1023 Octets in Length) Packets Transmitted (1024~1518 Octets in Length) Packets Transmitted (1519~MTU Octets in Length) Unicast Packets Transmitted Bad Octets Transmitted Good Octets Transmitted Broadcast Packets Transmitted Multicast Packets Transmitted Pause Frames Received Packets Received (64 Octets in Length) Packets Received (65~127 Octets in Length) Packets Transmitted (128~255 Octets in Length) Packets Received (256~511 Octets in Length) Packets Received (512~1023 Octets in Length) Packets Received (1024~1518 Octets in Length) Packets Received (1519~MTU Octets in Length) Unicast Packets Received Good Octets Transmitted Bad Octets Transmitted Broadcast Packets Received Fragments Multicast Packets Received Undersize Packets Received Oversize Packets Received
Jabbers
Issue 02 (2011-10-31)
863
5.2.87 VA1 Board Performance Event List

TN11VA1 ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN12VA1 XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.88 VA4 Board Performance Event List

TN11VA4 ICTMPCUR ICTMPMAX ICTMPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
TN12VA4 XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.89 WMU Board Performance Event List

PCLSWLCUR PCLSWLOCUR PCLSOPCUR XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.90 WSD9 Board Performance Event List

ICTMPCUR ICTMPMAX ICTMPMIN SUMIOPCUR SUMIOPMAX SUMIOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
Issue 02 (2011-10-31)
864
5.2.91 WSM9 Board Performance Event List

ICTMPCUR ICTMPMAX ICTMPMIN SUMOOPCUR SUMOOPMAX SUMOOPMIN XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.92 WSMD2 Board Performance Event List



5.2.95 XCH Board Performance Event List

TN16XCH XCSTMPCUR MAXFREQDEV
Issue 02 (2011-10-31)
XCSTMPMAX MINFREQDEV
XCSTMPMIN AVGFREQDEV
865
MAXPHASEOFFSET MAXMEANPATHDELAY
MINPHASEOFFSET MINMEANPATHDELAY
AVGPHASEOFFSET AVGMEANPATHDELAY
TN52XCH XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.96 XCM Board Performance Event List

TN52XCM XCSTMPCUR XCSTMPMAX XCSTMPMIN
5.2.97 XCT Board Performance Event List

Issue 02 (2011-10-31)
866
6 Performance Event Processing
6
About This Chapter
Performance Event Processing
The performance event is an important parameter to evaluate the working performance of equipment. Being acquainted with the generation principle, related boards and related alarms helps you discover hidden trouble in routine maintenance and locate faults in troubleshooting. If a performance event exceeds the threshold, the related alarms are generated. Therefore, upon any performance event, check any related alarms and handle the event accordingly. The meaning of the n and k in this topic as follows: l l k indicates the level of rate and its value is 1, 2, 3 and 5G. n indicates the level of TCM and its value ranges from 1 to 6.
6.1 AUPJCHIGH 6.2 AUPJCLOW 6.3 AUPJCNEW 6.4 BCV 6.5 CCV 6.6 CRC4ES 6.7 CRC4FEES 6.8 CRC4FESES 6.9 CRC4FEUAS 6.10 CRC4SES 6.11 CRC4UAS 6.12 EDTMP 6.13 EDTPL 6.14 ENVTMP 6.15 FEC_AFT_COR_ER
6.16 FEC_AFT_COR_ERAVR 6.17 FEC_AFT_CORER_FLOAT 6.18 FEC_BEF_COR_ER 6.19 FEC_BEF_COR_ERAVR 6.20 FEC_BEF_CORER_FLOAT 6.21 FEC_COR_0BIT_CNT 6.22 FEC_COR_1BIT_CNT 6.23 FEC_COR_BYTE_CNT 6.24 FEC_UNCOR_BLOCK_CNT 6.25 HPBBE 6.26 HPCSES 6.27 HPES 6.28 HPFEBBE 6.29 HPFECSES 6.30 HPFEES 6.31 HPFESES 6.32 HPFEUAS 6.33 HPSES 6.34 HPUAS 6.35 ICCLC 6.36 ICTMP 6.37 LSBIAS 6.38 LSBISA 6.39 LSCLC 6.40 LSIOP 6.41 LSOOP 6.42 LSTMP 6.43 MSBBE 6.44 MSCSES 6.45 MSES 6.46 MSFEBBE 6.47 MSFECSES 6.48 MSFEES
6.49 MSFESES 6.50 MSFEUAS 6.51 MSSES 6.52 MSUAS 6.53 ODU2PMBIP8 6.54 ODUk_PM_BBE 6.55 ODUk_PM_BBER 6.56 ODUk_PM_ES 6.57 ODUk_PM_FEBBE 6.58 ODUk_PM_FEBBER 6.59 ODUk_PM_FEES 6.60 ODUk_PM_FESES 6.61 ODUk_PM_FESESR 6.62 ODUk_PM_FEUAS 6.63 ODUk_PM_SES 6.64 ODUk_PM_SESR 6.65 ODUk_PM_UAS 6.66 ODUk_TCMn_BBE 6.67 ODUk_TCMn_BBER 6.68 ODUk_TCMn_BIAES 6.69 ODUk_TCMn_ES 6.70 ODUk_TCMn_FEBBE 6.71 ODUk_TCMn_FEBBER 6.72 ODUk_TCMn_FEES 6.73 ODUk_TCMn_FESES 6.74 ODUk_TCMn_FESESR 6.75 ODUk_TCMn_FEUAS 6.76 ODUk_TCMn_IAES 6.77 ODUk_TCMn_SES 6.78 ODUk_TCMn_SESR 6.79 ODUk_TCMn_UAS 6.80 OOPRL 6.81 OSC_BBE
6.82 OSC_BBER 6.83 OSC_BIAES 6.84 OSC_ES 6.85 OSC_FEBBE 6.86 OSC_FEBBER 6.87 OSC_FEES 6.88 OSC_FESES 6.89 OSC_FESESR 6.90 OSC_FEUAS 6.91 OSC_IAES 6.92 OSC_SES 6.93 OSC_SESR 6.94 OSC_UAS 6.95 OSPICCV 6.96 OSPITMP 6.97 OTU2SMBIP8 6.98 OTUk_BBE 6.99 OTUk_BBER 6.100 OTUk_ES 6.101 OTUk_FEBBE 6.102 OTUk_FEBBER 6.103 OTUk_FEES 6.104 OTUk_FESES 6.105 OTUk_FESESR 6.106 OTUk_FEUAS 6.107 OTUk_SES 6.108 OTUk_SESR 6.109 OTUk_UAS 6.110 PCLSOP 6.111 PCLSSN 6.112 PCLSWL 6.113 PCLSWLO 6.114 RPL
6.115 RSBBE 6.116 RSCSES 6.117 RSES 6.118 RSOFS 6.119 RSOOF 6.120 RSSES 6.121 RSUAS 6.122 SUMIOP 6.123 SUMOOP 6.124 TLB 6.125 TPL 6.126 VC3BBE 6.127 VC3CSES 6.128 VC3ES 6.129 VC3FEBBE 6.130 VC3FECSES 6.131 VC3FEES 6.132 VC3FESES 6.133 VC3FEUAS 6.134 VC3SES 6.135 VC3UAS 6.136 WCV 6.137 XCSTMP
Issue 02 (2011-10-31)
871
6.1 AUPJCHIGH
Description
Administrative unit pointer justification count high It indicates the positive justification count of the AU pointer when the rate of VC frame is adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number of pointer justification counts, however, cause bit errors in the services. In this case, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.
Generation Principle and Possible Causes

The root cause of the AU pointer justification is that the clocks of NEs on the SDH network are not synchronous. The possible causes of the event are as follows: l l l l The performance of the external clock is degraded. The clocks in two NEs trace each other because the optical fibers are connected incorrectly. The equipment performance is degraded due to high temperature. The clocks are configured incorrectly. If the SSM protocol is enabled but the clock IDs are not set, the loss of the primary clock source causes the network-wide pointer justification event. The clock quality is degraded because the SSM clock protection is disabled. The performance of the line board is degraded. The performance of the clock board is degraded.
l l l
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the SYN_BAD, LTI, S1_SYN_CHANGE and EXT_SYNC_LOS, are generated in the whole network. If yes, take priority to clear them. Step 2 For the network-wide pointer justification, check whether the clock configurations are consistent with those specified in the plan, including clock ID, SSM protocol, and clock tracing level. Step 3 For the non-network-wide pointer justification, check whether the optical fibers are connected correctly, and whether the ambient temperature of the equipment is within the normal range. If the AU pointer justification event occurs continuously, contact the technical support engineers of Huawei. ----End
Related Information
None
6.2 AUPJCLOW
Description
Administrative unit pointer justification count low It indicates the negative justification count of the AU pointer when the rate of VC frame is adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number of pointer justification counts, however, cause bit errors in the services. In this case, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are not synchronous. The possible causes are as follows: l l l l The performance of the external clock is degraded. The clocks in two NEs trace each other because the optical fibers are connected incorrectly. The equipment performance is degraded due to high temperature. The clocks are configured incorrectly. If the SSM protocol is enabled but the clock IDs are not set, the loss of the primary clock source causes the network-wide pointer justification event. The clock quality is degraded because the SSM clock protection is disabled. The performance of the line board is degraded. The performance of the clock board is degraded.
l l l
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the SYN_BAD, LTI, S1_SYN_CHANGE and EXT_SYNC_LOS, are generated in the whole network. If yes, take priority to clear them. Step 2 For the network-wide pointer justification, check whether the clock configurations are consistent with those specified in the plan, including clock ID, SSM protocol, and clock tracing level. Step 3 For the non-network-wide pointer justification, check whether the optical fibers are connected correctly, and whether the ambient temperature of the equipment is within the normal range. If
the AU pointer justification event occurs continuously, contact the technical support engineers of Huawei. ----End
Related Information
None
6.3 AUPJCNEW
Description
New count of administrative unit pointer
Impact on System
A little pointer justification does not affect the services. A large pointer justification can cause bit errors in the services and in this case, you need to find out the causes and take proper measures to ensure the transmission quality and prevent alarms.

The root cause of generating new data flag (pointer) for the AU pointer justification event is that the clocks of NEs in the SDH network are not synchronous. As a result, the new AU data flag (pointer) event is generated. The possible causes are as follows: l l l l The performance of the external clock is degraded. The clocks in two NEs trace each other because the optical fibers are connected incorrectly. The equipment performance is degraded due to high temperature. The clocks are configured incorrectly. If the SSM protocol is enabled but the clock IDs are not set, the loss of the primary clock source causes the network-wide pointer justification event. The clock quality is degraded because the SSM clock protection is disabled. The performance of the line board is degraded. The performance of the clock board is degraded.
l l l
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the SYN_BAD, LTI, S1_SYN_CHANGE and EXT_SYNC_LOS, are generated in the whole network. If yes, take priority to clear them. Step 2 For the network-wide pointer justification, check whether the clock configurations are consistent with those specified in the plan, including clock ID, SSM protocol, and clock tracing level. Step 3 For the non-network-wide pointer justification, check whether the optical fibers are connected correctly, and whether the ambient temperature of the equipment is within the normal range. If
the AU pointer justification event occurs continuously, contact the technical support engineers of Huawei. ----End
Related Information
None
6.4 BCV
Description
Pump Laser Back Facet Current It includes: l l l BCVMAX: stands for the maximum value during a period of time. BCVMIN: stands for the minimum value during a period of time. BCVCUR: stands for the current value.
Impact on System
None

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

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

CRC error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
Alarm Name CRC4_CROSSTR Correlation CRC4 multi-frame error code exceeds the threshold. The alarm is generated when the number of the bit errors in the CRC4 multiframe exceeds the threshold.
Procedure
Step 1 Refer to the method of handling the CRC4_CROSSTR. ----End
Related Information
None
6.7 CRC4FEES
Description
CRC4 far end errored second
Impact on System
There are bit errors in the services. If the far-end errored seconds are generated continuously, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality. If the number of bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
Alarm Name CRC4_CROSSTR Correlation CRC4 multi-frame error code counter exceeds the threshold. The alarm is generated when the number of the bit errors in the CRC4 multiframe exceeds the threshold.
Issue 02 (2011-10-31)
877
Procedure
Related Information
None
6.8 CRC4FESES
Description
CRC4 far end severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality. If the number of bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. During a severely errored second, there is at least one defect. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
Alarm Name CRC4_CROSSTR Correlation CRC4 multi-frame error code count exceeds the threshold. The alarm is generated when the number of the bit errors in the CRC4 multiframe exceeds the threshold.
Procedure
Related Information
None
Issue 02 (2011-10-31)
878
6.9 CRC4FEUAS
Description
CRC4 far end unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner because the bit errors have affected the signal transmission quality. If the number of bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Procedure
Related Information
None
6.10 CRC4SES
Description
CRC4 severely errored second
Issue 02 (2011-10-31)
879
Impact on System

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

CRC error is detected by checking the received parity bit. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Procedure
Related Information
None
6.12 EDTMP
Description
Laser temperature value It includes: l l l EDTMPMAX: stands for the maximum value during a period of time. EDTMPMIN: stands for the minimum value during a period of time. EDTMPCUR: stands for the current value.
Impact on System
None

This performance event is detected by hardware detecting circuit and then the result is calculated by the software for conversion. If the performance is not in the normal range, the EDFA module might be faulty.
Related Alarms
Alarm Name PUM_TEM_ALM Correlation Working temperature of the pump laser exceeds the threshold. This alarm is generated when the pump laser operating temperature of the optical amplifier unit exceeds the threshold.
Issue 02 (2011-10-31)
881
Procedure
Step 1 Refer to the method of handling the PUM_TEM_ALM. ----End
Related Information
None
6.13 EDTPL
Description
Pump output optical power It includes: l l l EDTPLMAX: stands for the maximum value during a period of time. EDTPLMIN: stands for the minimum value during a period of time. EDTPLCUR: stands for the current value.
Impact on System
Bit errors may be generated in the services and the services may be interrupted.

This performance event is detected by hardware detecting circuit and then the result is calculated by the software for conversion. If the performance is not in the normal range, the EDFA module might be faulty.
Related Alarms
Alarm Name OUT_PWR_HIGH OUT_PWR_LOW Correlation It is generated when the optical power output by the pump laser is higher than the upper threshold. It is generated when the optical power output by the pump laser is lower than the lower threshold.
Procedure
Step 1 Refer to the method of handling the OUT_PWR_HIGH or OUT_PWR_LOW. ----End
Related Information
None
6.14 ENVTMP
Description
Board environmental temperature It includes: l l l ENVTMPMAX: stands for the maximum value during a period of time. ENVTMPMIN: stands for the minimum value during a period of time. ENVTMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by hardware detecting to show the ambient temperature of the board.
Related Alarms
Alarm Name TEMP_OVER Correlation It is generated when the board working temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the proper handling procedures. ----End
Related Information
None
6.15 FEC_AFT_COR_ER
Description
After FEC correct errored rate
Issue 02 (2011-10-31)
883
Impact on System
After the error correction, in normal cases, the value should be 0. If the value is not 0, it indicates that the bit errors in the services bring impact on the transmission quality. In this case, determine the cause timely.

This performance event shows that there are still errors at the receiver after FEC. This performance event is caused by low OSNR at the receive end. In normal cases, it should be 0. In this case, there must be FEC_BEF_COR_ER accompanied and you should check the alarm timely.
Related Alarms
Alarm Name BEFFEC_EXC Correlation Signal degraded before FEC alarm. Signals sent from WDM sides of the opposite-end OTUs have the FEC function. As a result, before performing signal FEC in the receive direction of WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm is generated when the counted bit error rate exceeds the threshold.
Procedure
Step 1 Refer to the procedure for handling the BEFFEC_EXC. ----End
Related Information
None
6.16 FEC_AFT_COR_ERAVR
Description
After FEC Correct Average Errored Rate in monitor period.
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that the bit errors in the services bring impact on the transmission quality. In this case, determine the cause timely.

This performance event shows there are still errors at the receiver after FEC. This performance event is caused by low OSNR at the receive end. Normally, it should be zero.
In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the optical power to increase the OSNR.
Related Alarms
Procedure
Related Information
None
6.17 FEC_AFT_CORER_FLOAT
Description
After FEC Correct Errored Rate (floating point values)
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that the bit errors in the services bring impact on the transmission quality. In this case, determine the cause in a timely manner.

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

The cause for the BER before the FEC is that the receiver detects bit errors, which are caused by dispersion, unstable performance of the optical port, and/or excessively high attenuation.
Related Alarms
Issue 02 (2011-10-31)
886
Procedure
Related Information
None
6.19 FEC_BEF_COR_ERAVR
Description
Before FEC Correct Average Errored Rate in monitor period.
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate (BER) is low, the system operates normally. If the BER is high, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR at the receive end. Normally, it should be zero.
Related Alarms
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC. ----End
Related Information
None
Issue 02 (2011-10-31)
887
6.20 FEC_BEF_CORER_FLOAT
Description
Before FEC Correct Errored Rate (floating point values)
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate (BER) is low, the system operates normally. If the BER is high, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR at the receiving end.
Related Alarms
Alarm Name BEFFEC_EXC Correlation Signal degraded before FEC alarm. Signals sent from WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm is generated when the counted bit error rate exceeds the threshold. Signal degraded alarm before FEC alarm. Signals sent from WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm is generated when the counted bit error rate exceeds the threshold.
BEFFEC_SD
Procedure
Related Information
None
6.21 FEC_COR_0BIT_CNT
Description
Forward error correction - corrected 0 bit count
Impact on System
None

This performance event shows the number of 0bit corrected by FEC function of the board, and indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.22 FEC_COR_1BIT_CNT
Description
Forward error correction - corrected 1 bit count
Impact on System
None

This performance event shows the number of 1bit corrected by FEC function of the board, and indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.23 FEC_COR_BYTE_CNT
Description
Forward error correction - corrected byte count
Impact on System
None

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

This performance event shows the number of received error frames that cannot be corrected by FEC, and indicates that signals of low OSNR are beyond the correction capability of FEC. Normally, the performance value should be 0.
Issue 02 (2011-10-31)
890
Related Alarms
Alarm Name BEFFEC_EXC Correlation Signal degraded before FEC alarm. Signals sent from WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm is generated when the counted bit error rate exceeds the threshold.
Procedure
Related Information
None
6.25 HPBBE
Description
Higher order path background block error
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

The HPBBEs are detected by means of detecting the B3 byte. The possible causes of the event are as follows: l l l l l l There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty. The cross-connection unit is faulty. The clock unit is faulty.
Issue 02 (2011-10-31)
891
Related Alarms
Alarm Name B3_SD Correlation When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_SD but lower than the threshold of the B3_EXC, the alarm is reported. When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_EXC, the alarm is reported.
B3_EXC
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms. ----End
Related Information
Background Block Error The background block error means that one or more bit errors occur in the data block during transmission.
6.26 HPCSES
Description
Higher order path consecutive severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The severely errored second (SES) refers to the second in which more than 30% errored blocks occur or at least one serious disturbance period (SDP) occurs. Generally, the consecutive severely errored second (CSES) is accompanied by the B3_EXC alarm. Consequently, the services are interrupted. The possible causes of the event are as follows: l l l l
Issue 02 (2011-10-31)
There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty.
l l
The cross-connection unit is faulty. The clock unit is faulty.
Related Alarms
Alarm Name B3_SD Correlation When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_SD but lower than the threshold of the B3_EXC, the alarm is reported. When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_EXC, the alarm is reported.
B3_EXC
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm. ----End
Related Information
None
6.27 HPES
Description
Higher order path errored second
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible causes of the event are as follows: l l l l l l
Issue 02 (2011-10-31)
There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty. The cross-connection unit is faulty. The clock unit is faulty.
Related Alarms
Alarm Name B3_SD Correlation When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_SD but lower than the threshold of the B3_EXC, the alarm is reported. When the count of B3 bit errors in the alarm path exceeds the threshold, the alarm is reported.
B3_EXC
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm. ----End
Related Information
The errored second (ES) refers to the second in which one or more errored blocks are detected.
6.28 HPFEBBE
Description
Higher order path far end background block error
Impact on System
A small number of bit errors occur at the far end of the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

The HPFEBBE refers to the higher order path block error that is detected at the opposite station. The possible causes of the event are as follows: l l l l l l There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty. The cross-connection unit is faulty. The clock unit is faulty.
Issue 02 (2011-10-31)
894
Related Alarms
Alarm Name HP_REI Correlation If the board has detected that the value is 1-8 for bits 1-4 of the G1 byte in the higher order path, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the HP_REI alarm. ----End
Related Information
The background block error means that one or more bit errors occur in the data block during transmission.
6.29 HPFECSES
Description
Higher order path far end consecutive severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

The consecutive severely errored bits at the far end of the higher order path are detected by means of detecting the G1 byte. The possible causes of the event are as follows: l l l l l l There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty. The cross-connection unit is faulty. The clock unit is faulty.
Issue 02 (2011-10-31)
895
Related Alarms
Procedure
Related Information
Severely Errored Second The severely errored second (SES) refers to the second in which more than 30% errored blocks occur or at least one serious disturbance period (SDP) occurs. Consecutive Severely Errored Second The consecutive severely errored second (CSES) refers to the severely errored second (SES) event that occurs consecutively. Remote Bit Error The remote bit error refers to the bit error that is detected at the opposite station.
6.30 HPFEES
Description
Higher order path far end errored second
Impact on System
A small number of bit errors occur at the far end of the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible causes of the event are as follows: l l l
Issue 02 (2011-10-31)
There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty.
l l
The line board is faulty. The cross-connection clock unit is faulty.
Related Alarms
Procedure
Related Information
Remote Errored Second The remote errored second refers to the errored second that is detected at the peer end.
6.31 HPFESES
Description
Higher order path far end severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible causes of the event are as follows: l l l l l l
Issue 02 (2011-10-31)
There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty. The cross-connect unit is faulty. The clock unit is faulty.
Related Alarms
Procedure
Related Information
Severely Errored Second The severely errored second (SES) refers to the second in which more than 30% errored blocks occur or at least one serious disturbance period (SDP) occurs.
6.32 HPFEUAS
Description
Higher order path far end unavailable second
Impact on System
If bit errors occur in the services on a remote NE, detect the causes and troubleshoot the problem in a timely manner. Otherwise, alarms will be generated and the signal transmission quality will be affected.

HPFEUAS indicates the period of time that the unavailable time (UAT) state lasts. External causes: l l l l l The fiber performance degrades and the attenuation is excessively high at the opposite station. The fiber connector is dirty or incorrect at the opposite station. The equipment is improperly grounded at the opposite station. There is a strong interference source around the equipment at the opposite station. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems:
The signal attenuation at the receive side of the line board at the opposite station is excessively high, the transmitting circuit of the opposite station is faulty, or the receiving circuit of the local station is faulty. The synchronization performance of the clock is poor at the opposite station. The cross-connect unit and the service board do not work with each other properly at the opposite station. The fan of the opposite equipment is faulty. The board fails or the board performance degrades at the opposite station.
l l l l
Related Alarms
Alarm Name HP_REI HP_RDI Correlation Higher order path remote error indication Remote defect indication in higher order paths
Procedure
Step 1 If any alarm is generated, use the method of the related alarm to clear it. ----End
Related Information
None.
6.33 HPSES
Description
Higher order path severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible causes of the event are as follows: l l l
Issue 02 (2011-10-31)
There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty.
l l l
The line board is faulty. The cross-connection unit is faulty. The clock unit is faulty.
Related Alarms
Alarm Name B3_SD Correlation When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_SD but lower than the threshold of the B3_EXC, the alarm is reported. When the count of B3 bit errors in the alarm path exceeds the threshold, the alarm is reported.
B3_EXC
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms. ----End
Related Information
Severely Errored Second The severely errored second (SES) refers to the second in more than 30% errored blocks occur or at least one serious disturbance period (SDP) occurs.
6.34 HPUAS
Description
Higher order path unavailable second
Impact on System
l A great number of bit errors occur in the higher order path. If no related alarm is generated, the system is not affected. You need to, however, find out the causes and take proper measures in time to avoid any alarm, which affects the quality of the signals transmitted in the higher order path. If the performance event is generated, check whether the AU_AIS, B3_EXC and HP_UNEQ alarms are generated. If yes, the services may be interrupted.

Bit errors in the higher order path are detected by means of detecting the B3 byte. When signals are consecutively received for 10 seconds, and if the bit error ratio per second is more than 10-3, the period from the first second is called the period of UAS (unavailable second). When signals are consecutively received for 10 seconds, and if the bit error ratio per second is less than
10-3, the period from the first second is called the period of available second. The errored second (ES) refers to the second in which one or more errored blocks occur. The possible causes of the event are as follows: l l l l l l There is interference from the external environment. A fault occurs in the switch that interworks with the SDH equipment. The signal cable is faulty. The line board is faulty. The cross-connection unit is faulty. The clock unit is faulty.
Related Alarms
Alarm Name B3_SD Correlation When the count of B3 bit errors in the alarm path exceeds the threshold of the B3_SD but lower than the threshold of the B3_EXC, the alarm is reported. When the count of B3 bit errors in the alarm path exceeds the threshold, the alarm is reported. When the alarm is generated, the HPUAS value is increased. When the alarm is generated, the HPUAS value is increased. When the alarm is generated, the HPUAS value is increased.
B3_EXC AU_AIS HP_TIM HP_UNEQ
Procedure
Step 1 Refer to the method of handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and HP_UNEQalarms. ----End
Related Information
None
6.35 ICCLC
Description
Module cooling current It includes: l l l
Issue 02 (2011-10-31)
ICCLCMAX: stands for the maximum value during a period of time. ICCLCMIN: stands for the minimum value during a period of time. ICCLCCUR: stands for the current value.
Impact on System
None

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

This performance event is generated by checking the current working temperature of module to show the working temperature of a module.
Related Alarms
Alarm Name MODULE_TEMP_OVER Correlation It is generated when the working temperature of a module exceeds the threshold.
Procedure
Step 1 If the MODULE_TEMP_OVER alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
6.37 LSBIAS
Description
Laser bias current It includes: l l l LSBIASMAX: stands for the maximum value during a period of time. LSBIASMIN: stands for the minimum value during a period of time. LSBIASCUR: stands for the current value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
Alarm Name TD Correlation It is generated when the working current of a laser exceeds the threshold or a multiple of the threshold.
Issue 02 (2011-10-31)
Alarm Name LSR_WILL_DIE
Correlation It is generated when the working current of a laser exceeds the threshold or a multiple of the threshold.
Procedure
Step 1 If the TD alarm is generated, see the handling procedure of the alarm. Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
6.38 LSBISA
Description
Laser bias current It includes: l l l LSBIASMAX: stands for the maximum value during a period of time. LSBIASMIN: stands for the minimum value during a period of time. LSBIASCUR: stands for the current value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
Alarm Name TD LSR_WILL_DIE Correlation It is generated when the working current of a laser exceeds the threshold or a multiple of the threshold. It is generated when the working current of a laser exceeds the threshold or a multiple of the threshold.
Issue 02 (2011-10-31)
904
Procedure
Related Information
None
6.39 LSCLC
Description
Laser cooling current It includes: l l l LSCLCMAX: stands for the maximum value during a period of time. LSCLCMIN: stands for the minimum value during a period of time. LSCLCCUR: stands for the current value.
Impact on System
When the cooling current of a laser exceeds the threshold, the optical module of the board works abnormally. As a result, services cannot be transmitted or received normally.

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

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

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

Normally, the laser temperature is a stable value obtained by software through calculating the result output by the temperature detecting circuit in the laser.
Related Alarms
Alarm Name TEM_HA Correlation Laser temperature is excessively high. This alarm is generated when the laser temperature is higher than the upper threshold of the laser temperature. Laser temperature is excessively low. This alarm is generated when the laser temperature is lower than the upper threshold of the laser temperature.
TEM_LA
Procedure
Step 1 If the TEM_HA or TEM_LA alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
Issue 02 (2011-10-31)
908
6.43 MSBBE
Description
MS background block error
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name B2_EXC B2_SD Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceed the threshold. Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceed the signal degrade (SD) threshold. Multiplex section alarm indication. The alarm is generated when the opposite station transmits the MS_AIS signals or the receive part of the local station is faulty. Multiplex section performance exceeds the threshold. The alarm is generated when the performance module reports the threshold crossing of the performance events in the multiplex section. Loss of frame on receiving line. This alarm is generated when the frame alignment processing is out of frame (OOF) in consecutive 3 ms.
MS_AIS
MS_CROSSTR
R_LOF
Procedure
Step 1 Refer to the method of handling the B2_EXC. ----End
Related Information
None
6.44 MSCSES
Description
MS consecutive severely errored second
Impact on System
There are a large number of bit errors in the services. Determine the cause and solve the problem timely because the bit errors severely affect the signal transmission quality. In addition, the B2_EXC and B2_SD alarms may be generated.

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, and it is accompanied by the B2_EXC alarm. It might result in service interruption.
Related Alarms
MS_AIS
MS_CROSSTR
R_LOF
Procedure
Related Information
None
6.45 MSES
Description
MS errored second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. The MS errored second means there are more than one error block transmitted in this second.
Related Alarms
MS_AIS
MS_CROSSTR
R_LOF
Procedure
Related Information
None
6.46 MSFEBBE
Description
MS far end background block error
Impact on System
If bit errors are generated in the services on a far-end NE but no related alarm is reported on the opposite NE, there is no impact on the system. You, however, need to determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name MS_RDI Correlation Multiplex section remote defect indication alarm. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDM-side receive part of the opposite station is faulty.
Procedure
Step 1 Refer to the method of handling the MS_RDI. ----End
Related Information
None
6.47 MSFECSES
Description
MS far end consecutive severely errored second
Impact on System

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, and it is accompanied by the B2_EXE alarm. It might result in service interruption. The far end consecutive severely errored second refers to the consecutive severely errored second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
6.48 MSFEES
Description
MS far end errored second
Impact on System

The multiplex section errors are detected by checking the B2 byte. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Issue 02 (2011-10-31)
913
Related Alarms
Procedure
Related Information
None
6.49 MSFESES
Description
MS far end severely errored second
Impact on System

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
Issue 02 (2011-10-31)
914
Procedure
Related Information
None
6.50 MSFEUAS
Description
MS far end unavailable second
Impact on System
If bit errors are generated in the services on a far-end NE but no related alarm is reported on the opposite NE, there is no impact on the system. You, however, need to determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Procedure
Related Information
None
6.51 MSSES
Description
MS severely errored second
Impact on System

The multiplex section errors are detected by checking the B2 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
MS_AIS
MS_CROSSTR
R_LOF
Procedure
Related Information
None
6.52 MSUAS
Description
MS unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem timely to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the eleventh second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name B2_EXC B2_SD Correlation Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in the multiplex section exceed the threshold. Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in the multiplex section exceed the signal degrade (SD) threshold. Multiplex section alarm indication. The alarm is generated when the opposite station transmits the MS_AIS signals or the receive part of the local station is faulty. Multiplex section performance exceeds the threshold. The alarm is generated when the performance module reports the threshold crossing of the performance events in the multiplex section. Loss of signal on receiving line. This alarm is generated when the receive side receives no signals. Multiplex section remote defect indication alarm. The alarm is generated at the local station if the opposite station back transmits the information through overhead when the WDM-side receive part of the opposite station is faulty. Multiplex section remote error indication. The alarm is generated when the remote end detects the bit error block.
MS_AIS
MS_CROSSTR
R_LOS MS_RDI
MS_REI
Issue 02 (2011-10-31)
917
Procedure
Related Information
None
6.53 ODU2PMBIP8
Description
ODU PM section BIP8
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows the number of errors that a board with an OTN interface detects in path monitoring through the BIP8 check. Normally, the performance value should be zero.
Related Alarms
Alarm Name PM_BIP8_OVER Correlation Bit interleaved parity (BIP) in the PM section of the ODU layer exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the upper threshold. BIP in the PM section of the ODU layer degrades. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the degrade threshold.
PM_BIP8_SD
Procedure
Related Information
None
6.54 ODUk_PM_BBE
Description
ODU PM section background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

ODU PM section errors are detected by checking the received parity bits. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name ODUk_PM_EXC Correlation Bit interleaved parity (BIP) in the PM section of the ODU layer exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the upper threshold. Bit interleaved parity signal in the PM section of the ODU layer degrades. The alarm is generated when the number of BIP8 bit errors of the PM section of the ODU layer exceeds the degrade threshold.
ODUk_PM_DEG
Procedure
Step 1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG. ----End
Related Information
None
6.55 ODUk_PM_BBER
Description
ODU PM section ratio of background block error
Issue 02 (2011-10-31)
919
Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is large, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

ODU PM section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the ODU PM section refers to the ratio of the number of background block errors of the ODU PM section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second].
Related Alarms
Alarm Name ODUk_PM_EXC Correlation ODU layer PM section BIP exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the upper threshold. Bit interleaved parity signal in the PM section of the ODU layer degrades. The alarm is generated when the number of BIP8 bit errors of the PM section of the ODU layer exceeds the degraded threshold.
ODUk_PM_DEG
Procedure
Related Information
None
6.56 ODUk_PM_ES
Description
ODU PM section errored second
Impact on System
Issue 02 (2011-10-31)
920

ODU PM section errors are detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
Alarm Name ODUk_PM_EXC Correlation ODU layer PM section BIP exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the upper threshold. Bit interleaved parity signal in the PM section of the ODU layer degrades. The alarm is generated when the number of BIP8 bit errors of the PM section of the ODU layer exceeds the degraded threshold.
ODUk_PM_DEG
Procedure
Related Information
None
6.57 ODUk_PM_FEBBE
Description
ODU PM section far end background block error
Impact on System

ODU PM section errors are detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name ODUk_PM_BDI
Issue 02 (2011-10-31)
Correlation ODU PM section backward defect indication.

921
Procedure
Step 1 Refer to the method of handling the ODUk_PM_BDI. ----End
Related Information
None
6.58 ODUk_PM_FEBBER
Description
ODU PM section ratio of far end background block error
Impact on System

ODU PM section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the ODU PM section refers to the ratio of the number of background block errors of the ODU PM section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second]. And the ratio of far end background block error refers to the ratio of background block error detected at the opposite end.
Related Alarms
Alarm Name ODUk_PM_BDI Correlation ODU PM section backward defect indication.
Procedure
Related Information
None
6.59 ODUk_PM_FEES
Description
ODU PM section far end errored second
Impact on System

ODU PM section error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
6.60 ODUk_PM_FESES
Description
ODU PM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases, determine the cause and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

Errors are detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively. It might result in the interruption of the service that shares a fiber link with the supervisory channel. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
6.61 ODUk_PM_FESESR
Description
ODU PM section ratio of far end severely errored second
Impact on System

Bit errors are detected by checking the received parity bits. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time. Far end severely errored second ratio refers to the ratio of errored seconds that are detected at the opposite end.
Related Alarms
Issue 02 (2011-10-31)
924
Procedure
Related Information
None
6.62 ODUk_PM_FEUAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services on a far-end NE. The services may be affected.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the eleventh second, and the former 10 seconds are counted as available. And the far end unavailable second refers to the unavailable second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
Issue 02 (2011-10-31)
925
6.63 ODUk_PM_SES
Description
ODU PM section severely errored second
Impact on System
There are bit errors in services. Determine the cause and solve the problem timely because the bit errors have affected the signal transmission quality.

ODU PM Section error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might result in the interruption of the service that shares a fiber link with the supervisory channel.
Related Alarms
Alarm Name ODUk_PM_EXC Correlation ODU layer PM section BIP exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section of the optical channel data unit layer exceeds the upper threshold. Optical channel data unit layer, path monitoring section bit interleaved parity signal degraded. The alarm is generated when the number of BIP8 bit errors of the PM section of the optical channel data unit layer exceeds the degraded threshold.
ODUk_PM_DEG
Procedure
Related Information
None
6.64 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem timely because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bits. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
Alarm Name ODUk_PM_EXC Correlation ODU layer PM section BIP exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the upper threshold. Optical channel data unit layer, path monitoring section bit interleaved parity signal degraded. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the degraded threshold.
ODUk_PM_DEG
Procedure
Related Information
None
6.65 ODUk_PM_UAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the eleventh second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name ODUk_PM_EXC Correlation ODU layer PM section BIP exceeds the upper threshold. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the upper threshold. Optical channel data unit layer, path monitoring section bit interleaved parity signal degraded. The alarm is generated when the number of BIP8 bit errors of the PM section on the optical channel data unit layer exceeds the degraded threshold.
ODUk_PM_DEG
Procedure
Related Information
None
6.66 ODUk_TCMn_BBE
Description
ODUk TCMn section background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

ODUk TCMn section errors are detected by checking the received parity bits. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name ODUk_TCMn_DEG ODUk_TCMn_EXC Correlation ODU TCMn burst-mode signal degradation. ODU TCMn Poisson-mode excessive bit errors.
Issue 02 (2011-10-31)
928
Procedure
Step 1 On the U2000, check whether there are a great amount of BIP8 bit errors of the TCM section in the input signals on the client side. If yes, rectify the fault on the client-side equipment. Step 2 If the performance keeps deteriorating, see the handling procedure for the ODUk_TCMn_DEG or ODUk_TCMn_EXC. ----End
Related Information
None
6.67 ODUk_TCMn_BBER
Description
ODUk TCMn section ratio of background block error
Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

ODUk TCMn section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the ODUk TCMn section refers to the ratio of the number of background block errors of the ODUk TCMn section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(PUAS-cSES) x blocks per second].
Related Alarms
Procedure
Step 1 On the U2000, check whether there are a great amount of BIP8 bit errors of the TCM section in the input signals on the client side. If yes, rectify the fault on the client-side equipment. Step 2 If the performance event persists, see the handling procedure for the ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm. ----End
Related Information
None
6.68 ODUk_TCMn_BIAES
Description
ODU TCMn section backward introducing alignment errored second
Impact on System
There are errors in frame alignment. Determine the cause and solve the problem in a timely manner to ensure the signal transmission quality.

ODU TCMn section backward introducing alignment errored seconds are detected by checking the backward input frame alignment bits. Backward incoming alignment errored second refers to the second where more than one backward input frame alignment errors are generated.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical interface is within the normal range. For the optical power specifications of the board, see the Product Description. If the input optical power is abnormal, see the methods for handling the IN_PWR_HIGH and IN_PWR_LOW alarms. Step 2 If the performance event persists, see the description on bit error fault handling in the Troubleshooting. ----End
Related Information
None
6.69 ODUk_TCMn_ES
Description
ODUk TCMn section errored second
Issue 02 (2011-10-31)
930
Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

ODUk TCMn section error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
Procedure
Step 1 On the U2000, check whether there are a great amount of BIP8 bit errors of the TCM section in the input signals on the client side. If yes, rectify the fault on the client-side equipment. Step 2 If the performance event persists, see the handling procedure for the ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm. ----End
Related Information
None
6.70 ODUk_TCMn_FEBBE
Description
ODUk TCMn section far end background block error
Impact on System
If bit errors are generated in the services on a far-end NE but no related alarm is reported on the opposite NE, there is no impact on the system. You, however, need to determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

Far end background block of the ODUk TCMn section is detected by checking the received backward error bits. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the
background block error detected at the opposite end. The backward error bit means the inserted indication to the local end after the background block error is detected at the opposite end.
Related Alarms
None
Procedure
Related Information
None
6.71 ODUk_TCMn_FEBBER
Description
ODUk TCMn section ratio of far end background block error
Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

Background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Far end background block error ratio of the ODUk TCMn section refers to the ratio of the number of far end background block errors of the ODUk TCMn section to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second].
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical interface is within the normal range. For the optical power specifications of the board, see the Product Description. If the input
optical power is abnormal, see the methods for handling the IN_PWR_HIGH and IN_PWR_LOW alarms. Step 2 If the performance event persists, see the description on bit error fault handling in the Troubleshooting. ----End
6.72 ODUk_TCMn_FEES
Description
ODUk TCMn section far end errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

ODUk backward error indication of the TCMn section is determined by the BEI that is inserted at the far end. Far end errored second refers to the second where the checked signals contain at least one block error at the far end.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_BDI. ----End
Related Information
None
6.73 ODUk_TCMn_FESES
Description
ODUk TCMn section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

ODUk far end severely errored second of the TCMn section is determined by the BEI that is inserted at the far end. During a far end severely errored second, there is at least one defect or 30% of data blocks are error blocks. The fiber line may be faulty.
Related Alarms
None
Procedure
Related Information
None
6.74 ODUk_TCMn_FESESR
Description
ODUk TCMn section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Determine the cause and solve the problem in a timely manner, thus to ensure the signal transmission quality.

During a far end severely errored second, there is at least one defect or 30% of data blocks are error blocks. FESESR refers to the ratio of the FESES count in a certain period to the total available time.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_SESR. ----End
Related Information
None
6.75 ODUk_TCMn_FEUAS
Description
ODUk TCMn section unavailable second
Impact on System
The far-end services are not available.

Unavailable seconds are generated when the number of bit errors at the far end is large.
Related Alarms
Alarm Name ODUk_TCMn_BDI Correlation ODU TCMn backward defect indication.
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_BDI. ----End
Related Information
None
6.76 ODUk_TCMn_IAES
Description
ODUk TCMn section introducing alignment errored second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.

There is the OTUk_OOF or OTUk_LOF alarm at the upstream station.
Related Alarms
Alarm Name OTUk_LOF Correlation OTUk frame loss. The upstream station detects the LOF alarm and then inserts IAE. The local station reports ODU1_TCMn_IAES.
Procedure
Step 1 Refer to the method of handling the OTUk_LOF. ----End
Related Information
None
6.77 ODUk_TCMn_SES
Description
ODUk TCMn section severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner because the bit errors have affected the signal transmission quality.

It is obtained by calculating the BIP-8 of ODUk TCMn section. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The fiber line may be faulty.
Related Alarms
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC. ----End
Related Information
None
6.78 ODUk_TCMn_SESR
Description
ODUk TCMn section ratio of severely errored second
Impact on System

It is obtained by calculating the BIP-8 of ODU1 TCMn section. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively. SESR refers to the ratio of the SES count in a specified period to the total available time.
Related Alarms
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC. ----End
Related Information
None
6.79 ODUk_TCMn_UAS
Description
ODUk TCMn section unavailable second
Impact on System

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC ----End
Related Information
None
6.80 OOPRL
Description
Optical Output Power Return Loss It includes: l l l OOPRLMAX: maximum value of the optical output power return loss within a time period OOPRLMIN: minimum value of the optical output power return loss within a time period OOPRLCUR: current value of the optical output power return loss
Impact on System
Services may be interrupted.

The fiber near the Raman board is broken, over-bent, or pressed, or the fiber connector is unclean or installed incorrectly.
Issue 02 (2011-10-31)
938
Related Alarms
Alarm Name RL_CRITICAL_HI RL_CRITICAL_LO W Correlation This alarm is generated when the return loss is higher than the upper threshold of the return loss alarm. This alarm is generated when the return loss is lower than the lower threshold of the return loss alarm.
Procedure
Step 1 Refer to the method of handling the RL_CRITICAL_HI or RL_CRITICAL_LOW. ----End
Related Information
None
6.81 OSC_BBE
Description
OSC Path Section Background Block Error.
Impact on System
There are bit errors in the OSC signals. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.82 OSC_BBER
Description
OSC Path Section Ratio of Background Block Error.
Impact on System
When the value is not 0, it indicates that there are bit errors in the OSC signals. When the value is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

The background block error means there are one or more data blocks containing error bits during transmission. Background block error ratio refers to the ratio of the number of background block errors to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.83 OSC_BIAES
Description
OSC Path Backward Incoming Alignment Errored Second.
Impact on System
There are errors in frame alignment. Determine the cause and solve the problem in a timely manner to ensure the signal transmission quality.

Backward incoming alignment errored second refers to the second where more than one backward input frame alignment errors are generated.
Related Alarms
None
Procedure
Step 1 If the performance event persists, see the description on bit error fault handling in the Troubleshooting. ----End
Related Information
None
6.84 OSC_ES
Description
OSC Path Section Severely Errored Second.
Impact on System
There are bit errors in the OSC signals. If the number of bit errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

An errored second contains more than one error block.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.85 OSC_FEBBE
Description
OSC Path Far End Background Block Error.
Impact on System
If bit errors are generated in the signals on a far-end NE but no related alarm is reported on the opposite NE, there is no impact on the system. You, however, need to determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

OSC Path error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.86 OSC_FEBBER
Description
Osc Path Section Ratio of Far End Background Block Error.
Impact on System
When the value is not 0, it indicates that there are bit errors in the signalss. When the value is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio refers to the ratio of the number of background block errors to the number of all blocks minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second]. And the ratio of far end background block error refers to the ratio of background block error detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.87 OSC_FEES
Description
OSC Path Section Far End Background Block Error.
Impact on System
There are bit errors in the signals on a far-end NE. If the number of block errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

OSC path section error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.88 OSC_FESES
Description
OSC Path Section Far End Severely Errored Second.
Impact on System
There are bit errors in the signals on a far-end NE. Determine the cause and solve the problem in a timely manner because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.89 OSC_FESESR
Description
OSC Path Section Ratio of Far End Severely Errored Second.
Impact on System
There are bit errors in the signals on a far-end NE. Determine the cause and solve the problem in a timely manner because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bits. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time. Far end severely errored second ratio refers to the ratio of errored seconds that are detected at the far end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.90 OSC_FEUAS
Description
OSC Path Section Unavailable Second.
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission quality.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the 11th second, and the former 10 seconds are counted as available. And the far end unavailable second refers to the unavailable second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.91 OSC_IAES
Description
OSC Path Section Errored Second.
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.

None
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.92 OSC_SES
Description
OSC Path Section Severely Errored Second.
Impact on System
There are severely errored second in the OSC signals. Determine the cause and solve the problem in a timely manner because the bit errors have affected the signal transmission quality.

Error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.93 OSC_SESR
Description
OSC Path Section Ratio of Severely Errored Second.
Impact on System
There are severely errored second in the signals. Determine the cause and solve the problem in a timely manner because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bits. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might result in the interruption of the service that shares a fiber link with the supervisory channel. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.94 OSC_UAS
Description
OSC Path Section Unavailable Second.
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission quality.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the 11th second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available
time starts from the beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.95 OSPICCV
Description
The OSPICCV indicates the value of the cooling current of the laser. It includes: l l l OSPICCVMAX: stands for the maximum value during a period of time. OSPICCVMIN: stands for the minimum value during a period of time. OSPICCVCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the cooling current of the laser is excessively high or low, however, the laser may work abnormally. If the cooling current is within the normal range, you do not need to take any action.

l l The performance event records the current value of the cooling current. The cooling current is applied to control the temperature of the optical module. In the case of excessively low temperature, the cooling current is increased to make the temperature higher. In the case of excessively high temperature, the cooling current is decreased to make the temperature lower.
Related Alarms
Alarm Name LSR_COOL_ALM Correlation When the cooling current of the laser is beyond the specified range, this alarm is generated.
Issue 02 (2011-10-31)
948
Procedure
Step 1 Refer to the method of handling the LSR_COOL_ALM alarm. ----End
Related Information
None
6.96 OSPITMP
Performance Event Meaning
The OSPITMP indicates the value of the temperature in the tube core of the laser. It includes: l l l OSPITMPMAX: stands for the maximum value during a period of time. OSPITMPMIN: stands for the minimum value during a period of time. OSPITMPCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the temperature in the tube core of the laser is excessively high or low; however, the laser may work abnormally. As a result, the services may be interrupted. If the temperature is within the normal range, you do not need to take any action.

The performance event is adopted to monitor the current temperature in the tube core of the laser, and to know the current temperature of the laser.
Related Alarms
Alarm Name TEM_HA TEM_LA Correlation When the temperature of the laser is higher than the upper threshold, the alarm is reported. When the temperature of the laser is less than the lower threshold, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the TEM_HA and TEM_LA alarms. ----End
Related Information
None
6.97 OTU2SMBIP8
Description
OTU SM section BIP8
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows the number of errors that a board with an OTN interface detects in section monitoring through the BIP8 check. In normal cases, it should be 0.
Related Alarms
Alarm Name SM_BIP8_OVER Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the threshold. OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the degraded threshold.
SM_BIP8_SD
Procedure
Step 1 If any alarm is generated, use the method of the relevant alarm to clear it. ----End
Related Information
None
6.98 OTUk_BBE
Description
OTU background block error
Impact on System

OTU errors are detected by checking the received parity bits. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name OTUk_EXC Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the threshold. OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section in the optical channel data unit layer exceeds the degraded threshold.
OTUk_DEG
Procedure
Step 1 Refer to the method of handling the OTUk_EXC or OTUk_DEG. ----End
Related Information
None
6.99 OTUk_BBER
Description
OTU ratio of background block error
Impact on System

OTU section background block errors are detected by checking the received parity bits. The background block error refers to a data block where at least one bit error is generated during the transmission. Background block error ratio of the OTU section refers to the ratio of the number of background block errors of the OTU section to the number of all blocks minus the number
of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].
Related Alarms
Alarm Name OTUk_EXC Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section in the optical channel data unit layer exceeds the threshold. OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the degraded threshold.
OTUk_DEG
Procedure
Related Information
None
6.100 OTUk_ES
Description
OTU errored second
Impact on System

OTU error is detected by checking the received parity bit. An errored second contains more than one error block.
Related Alarms
Alarm Name OTUk_EXC Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the threshold.
Issue 02 (2011-10-31)
Alarm Name OTUk_DEG
Correlation OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the degraded threshold.
Procedure
Related Information
None
6.101 OTUk_FEBBE
Description
OTU SM section far end background block error
Impact on System

OTU SM section error is detected by checking the received parity bit. The background block error means there are one or more data blocks containing error bit during transmission. And the far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name OTUk_BDI Correlation OTU SM section backward defect indication.
Procedure
Step 1 Refer to the method of handling the OTUk_BDI. ----End
Related Information
None
6.102 OTUk_FEBBER
Description
OTU SM section ratio of far end background block error
Impact on System

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

OTU SM section error is detected by checking the received parity bit. An errored second contains more than one error block. And the far end errored second refers to the errored second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
6.104 OTUk_FESES
Description
OTU SM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Determine the cause and solve the problem timely because the bit errors have affected the signal transmission quality.

OTU SM Section error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might result in the interruption of the service that shares a fiber link with the supervisory channel. And the far end severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
6.105 OTUk_FESESR
Description
OTU SM section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Determine the cause and solve the problem timely because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bits. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time. Far end severely errored second ratio refers to the ratio of errored seconds that are detected at the far end.
Related Alarms
Procedure
Related Information
None
6.106 OTUk_FEUAS
Description
OTU SM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the eleventh second, and the former 10 seconds are counted as available. And the far end unavailable second refers to the unavailable second detected at the opposite end.
Related Alarms
Procedure
Related Information
None
6.107 OTUk_SES
Description
OTU severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem timely because the bit errors have affected the signal transmission quality.

Error is detected by checking the received parity bit. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might result in the interruption of the service that shares a fiber link with the supervisory channel.
Related Alarms
Alarm Name OTUk_EXC Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the threshold. OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the degraded threshold.
OTUk_DEG
Procedure
Related Information
None
6.108 OTUk_SESR
Description
OTU ratio of severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem timely because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bits. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored second means the severely errored second appears consecutively, it might result in the interruption of the service that shares a fiber link with the supervisory channel. Severely errored second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
Alarm Name OTUk_EXC Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the threshold. OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the degraded threshold.
OTUk_DEG
Procedure
Related Information
None
6.109 OTUk_UAS
Description
OTU unavailable second
Impact on System

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the eleventh second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name OTUk_EXC Correlation OTU SM section bit interleaved parity exceeds threshold. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the threshold.
Issue 02 (2011-10-31)
Alarm Name OTUk_DEG
Correlation OTU SM section bit interleaved parity deterioration. The alarm is generated when the number of BIP8 bit errors of the SM section on the optical channel data unit layer exceeds the degraded threshold.
Procedure
Related Information
None
6.110 PCLSOP
Description
Per-channel laser output power, indicating the optical power of a channel of signal monitored by the spectrum analyzer unit. It includes: l l l PCLSOPMAX: stands for the maximum value during a period of time. PCLSOPMIN: stands for the minimum value during a period of time. PCLSOPCUR: stands for the current value.
Impact on System
None

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

The MCA board analyzes the multiplexed optical signals and checks and calculates the OSNR of a channel of signal.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.112 PCLSWL
Description
Per-channel central wavelength, indicating the central wavelength of a channel among optical signals monitored by the spectrum analyzer unit. It includes: l l
Issue 02 (2011-10-31)
PCLSWLMAX: stands for the maximum value during a period of time. PCLSWLMIN: stands for the minimum value during a period of time.
PCLSWLCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signal to check its central wavelength.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.113 PCLSWLO
Description
Per-channel central wavelength deviation indicates the deviation between the ITU-T standard wavelength and the wavelength of a channel among optical signals monitored by the spectrum analyzer unit. It includes: l l l PCLSWLOMAX: stands for the maximum value during a period of time. PCLSWLOMIN: stands for the minimum value during a period of time. PCLSWLOCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and checks and calculates the central wavelength deviation of a channel of signal.
Related Alarms
None
Procedure
Step 1 None ----End
Related Information
None
6.114 RPL
Description
The RPL indicates the value of the input optical power. It includes: l l l RPLMAX: stands for the maximum value during a period of time. RPLMIN: stands for the minimum value during a period of time. RPLCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the input optical power is excessively high, the laser may be damaged. If the input optical power is excessively low, the laser may fail to detect the signals. You can know the normal range of the input optical power by querying the specifications for related optical interfaces.

The performance event is adopted to monitor the value of the input optical power of the laser, and to know the value of the input optical power.
Related Alarms
Alarm Name IN_PWR_LOW IN_PWR_HIGH Correlation The alarm is generated when the input optical power is lower than the lower threshold of the input optical power. The alarm is generated when the input optical power is higher than the upper threshold of the input optical power.
Procedure
Related Information
None
6.115 RSBBE
Description
RS background block error
Impact on System

The regenerator section errors are detected by checking the B1 byte. The background block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name B1_EXC Correlation Regenerator section (B1) excessive errors. The alarm is generated when the received signals in SDH frame degrade and the B1 bit errors in the multiplex section exceed the threshold.
Procedure
Related Information
None
6.116 RSCSES
Description
RS consecutive severely errored second
Issue 02 (2011-10-31)
964
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored second, there is at least one defect or 30% of data blocks are error blocks. Consecutive severely errored seconds (CSES) mean the severely errored seconds appear consecutively, and the CSES is generally accompanied by the B1_EXC alarm. It might result in service interruption.
Related Alarms
Procedure
Related Information
None
6.117 RSES
Description
Regenerator section (RS) errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. The RS errored second means that there are more than one error block transmitted in this second.
Related Alarms
Procedure
Related Information
None
6.118 RSOFS
Description
RS out-of-frame second
Impact on System
This alarm indicates that the frame headers cannot be identified in five or more consecutive frames in the received signals of the line board. The board enters the out-of-frame state. As a result, the services are unavailable. If the out-of-frame state lasts for 3 ms, the board enters the loss-of-frame state and the R_LOF alarm is generated.

Out-of-frame (OOF) refers to the loss of framing bytes and the OOF second contains at least one OOF. OOF turns to be loss of frame (LOF) if it lasts more than 3 ms.
Related Alarms
Alarm Name R_OOF Correlation Out of frame on receiving line. This alarm is generated when the headers of consecutive five frames fail to be detected.
Issue 02 (2011-10-31)
966
Alarm Name R_LOF
Correlation Loss of frame on receiving line. This alarm is generated when the frame alignment processing is in the OOF state in consecutive 3 ms.
Procedure
Step 1 Check whether the fibers are damaged and whether the connectors are properly installed. Clean the fiber connectors. Step 2 Check whether the input optical power of the input interface of the board is within the normal range by using an optical power meter. For the optical power specifications of a certain board, see the Product Description. If the power is not within the normal range, add proper attenuation by adding a fix attenuator or a variable optical attenuator (VOA). Step 3 Replace the faulty board. For details, see the Parts Replacement. ----End
Related Information
None
6.119 RSOOF
Description
The RSOOF indicates the count of out-of-frame events in the regenerator section.
Impact on System
When the performance event occurs, the frame alignment bytes are lost. As a result, the services are interrupted.

The out-of-frame event means that the frame alignment bytes are lost. The RSOOF means that one or more out-of-frame events occur during transmission. The possible causes of the event are as follows: l l l l
Issue 02 (2011-10-31)
There is interference from the external environment. The performance of the optical fiber is degraded. The line board is faulty. The clock unit is faulty.
Related Alarms
Alarm Name R_OOF R_LOF Correlation If more than five consecutive frames cannot be correctly aligned with the SDH frame header, the alarm is reported. When the R_OOF alarm lasts for 3 ms, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the R_OOF and R_LOF. ----End
Related Information
None
6.120 RSSES
Description
RS severely errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored second, there is at least one defect or 30% of blocks are error blocks.
Related Alarms
Issue 02 (2011-10-31)
968
Procedure
Related Information
None
6.121 RSUAS
Description
RS unavailable second
Impact on System

The regenerator section errors are detected by checking the B1 byte. If the severely errored seconds last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the severely errored second disappears for more than 10 seconds, the available time starts from the beginning of the eleventh second, and the former 10 seconds are counted as available.
Related Alarms
Procedure
Related Information
None
6.122 SUMIOP
Description
Total input optical power It includes: l l l SUMIOPMAX: stands for the maximum value during a period of time. SUMIOPMIN: stands for the minimum value during a period of time. SUMIOPCUR: stands for the current value.
Impact on System
If the total input optical power is excessively high, the optical modules of the local board and the downstream board may be damaged. As a result, bit errors are generated in the services or even the services are interrupted. If the total input optical power is excessively low, the singlewavelength optical signals that are output by the board may be lost. As a result, bit errors are generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate the result with software for conversion. SUMIOP is the total input optical power of demultiplexer and the optical amplifier board.
Related Alarms
Alarm Name IN_PWR_HIGH Correlation It is generated when the input optical power is higher than the upper threshold. Inaccurate optical power detection or faulty optical module can cause the input optical power higher than the upper threshold. It is generated when the optical power input by board is lower than the lower threshold. Inaccurate optical power detection or faulty optical module can cause the input optical power lower than the lower threshold. It is generated when the detected total input optical power is higher than the upper threshold. It is generated when the detected total input optical power is lower than the lower threshold.
IN_PWR_LOW
SUM_INPWR_HI SUM_INPWR_LO W
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the history performance value and the change in optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH or SUM_INPWR_HI alarm. Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW or SUM_INPWR_LOW alarm. Step 3 If an alarm is generated, see the handling procedure of the alarm. ----End
Related Information
The board types that are supported by the input power alarm are different from the board types that are supported by the total input power alarm.
6.123 SUMOOP
Description
Total output optical power It includes: l l l SUMOOPMAX: stands for the maximum value during a period of time. SUMOOPMIN: stands for the minimum value during a period of time. SUMOOPCUR: stands for the current value.
Impact on System
The total output power brings impact on the services. If the total output power is excessively high, the input optical power of the downstream board may be excessively high. As a result, bit errors are generated in the services or even the services are interrupted. In addition, the receiver module of the OTU at the downstream station may be damaged. If the total output power is excessively low, the input optical power of the downstream board may be excessively low. As a result, bit errors are generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate the result with software for conversion. SUMOOP is the total optical power output by the multiplexer and the optical amplifier board. In a multiplexer unit, the input signals pass the multiplexer and then output the total optical power through the "OUT" port, while on an amplifier board, the input signals pass the amplifier and then output the total optical power through the "OUT" port.
Issue 02 (2011-10-31)
971
Related Alarms
Alarm Name OUT_PWR_HIGH Correlation It is generated when the optical power output by board is higher than the upper threshold. Inaccurate optical power detection or faulty optical module can cause the input optical power higher than the upper threshold. It is generated when the optical power output by board is lower than the lower threshold. Inaccurate optical power detection or faulty optical module can cause the input optical power lower than the lower threshold.
OUT_PWR_LOW
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm. Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the history performance value and the change in optical power is not caused by normal operations (such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm. Step 3 If an alarm is generated, see the handling procedure of the alarm. ----End
Related Information
The board types that are supported by the output power alarm are different from the board types that are supported by the total output power alarm.
6.124 TLB
Description
The TLB indicates the value of the bias current of the laser. It includes: l l l TLBMAX: stands for the maximum value during a period of time. TLBMIN: stands for the minimum value during a period of time. TLBCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the bias current of the laser is beyond the normal range, however, the laser fails to work or is going to the end of its life. As a result, the services are interrupted. If the bias current is within the normal range, you do not need to take any action.

The performance event is adopted to monitor the bias of the laser, and to know the value of the bias current of the laser.
Related Alarms
Alarm Name TF Correlation When the bias current of the laser is beyond the normal range, the alarm is reported, showing transmission failure of the laser. When the bias current of the laser is less than the TF value, the alarm is reported, indicating that the life of the laser is going to the end.
LSR_WILL_DIE
Procedure
Related Information
None
6.125 TPL
Description
The TPL indicates the value of the output optical power. It includes: l l l TPLMAX: stands for the maximum value during a period of time. TPLMIN: stands for the minimum value during a period of time. TPLCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the output optical power of the laser is beyond the normal range, however, the laser fails to work or is going to the end of its life. As a result, the services are interrupted. If the output optical power is within the normal range, you do not need to take any action.

The performance event is adopted to monitor the value of the output optical power of the laser, and to know the current value of the output optical power.
Related Alarms
Alarm Name TF Correlation When the output optical power is beyond the normal range and this causes transmission failure of the laser, the alarm is reported. When the output optical power is greatly beyond the normal range, the alarm is reported, indicating that the life of the laser is going to the end.
LSR_WILL_DIE
Procedure
Related Information
None
6.126 VC3BBE
The VC3BBE is a performance event indicating the VC-3 background block error.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the B3 bit error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
VC3BBE indicates bit errors detected in a verification and excluding the higher order path unavailable time and higher order path severely errored second. External causes: l l l l l The fiber performance is degraded, and the attenuation of the fiber is excessively high. The fiber connector is dirty or incorrect. The equipment is improperly grounded. There is a strong interference source around the equipment. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems:
The signal attenuation at the receive side of the service board is excessively high, the transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end is faulty. The synchronization performance of the clock is poor. The cross-connect unit and the service board do not work with each other properly. The board becomes faulty, or the performance of the board is degraded.
l l l
Relevant Alarms
Alarm Name B3_EXC_VC3 B3_SD_VC3 Correlation B3 bit errors exceeds the threshold Signals degraded (B3)
Procedure
Step 1 Eliminate external causes. For example, the grounding is improper or the operating temperature is high. The receive optical power of the service board is excessively low or high. In this case, ground the equipment properly or provide a proper operating environment for the equipment. For more information about solving the optical power problem, see the 6.114 RPL performance. Then, check whether bit errors occur on the service boards. Step 2 If all the service boards of an NE have bit errors, the clock unit might be faulty. In this case, replace the clock unit. Step 3 If only a service board reports that bit errors exist, it indicates that the local service board might be faulty or that the opposite NE or fibers are faulty. Locate the faulty board by using the loopback method. Then, replace the faulty board. ----End
Reference
None.
6.127 VC3CSES
The VC3CSES is a performance event indicating the VC-3 continuous severely errored second.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
When a consecutive VC3CSES sequence is detected, the VC3CSES performance event occurs. When unavailable time comes or VC3CSES is absent in one second, the VC3CSES sequence ends. External causes: l l l l l The fiber performance is degraded, and the attenuation of the fiber is excessively high. The fiber connector is dirty or incorrect. The equipment is improperly grounded. There is a strong interference source around the equipment. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems: l The signal attenuation at the receive side of the service board is excessively high, the transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end is faulty. The synchronization performance of the clock is poor. The cross-connect unit and the service board do not work with each other properly. The board becomes faulty, or the performance of the board is degraded.
l l l
Relevant Alarms
Alarm Name B3_EXC_VC3 B3_SD_VC3 R_LOS R_LOF MS_AIS AU_AIS AU_LOP LP_UNEQ_VC3 Correlation B3 bit errors exceed the threshold. Signals degraded (B3). The signal on the receive line side is lost. The out-of-frame fault occurs on the receiver line side. Multiplex section alarm indication. AU alarm indication. AU pointer loss. VC-3 path unequipped.
Procedure
Step 1 Refer to the 6.128 VC3ES. ----End
Reference
None.
6.128 VC3ES
The VC3ES is a performance event indicating VC-3 errored second.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
The VC3ES performance event occurs when one or multiple bit error blocks are detected in one second or, when the R_LOS, R_LOF, and MS_AIS alarms are detected on the optical interface, or when the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected over the path. External causes: l l l l l The fiber performance is degraded, and the attenuation of the fiber is excessively high. The fiber connector is dirty or incorrect. The equipment is improperly grounded. There is a strong interference source around the equipment. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
l l l
Relevant Alarms
Alarm Name B3_EXC_VC3 B3_SD_VC3 R_LOS R_LOF MS_AIS
Issue 02 (2011-10-31)
Correlation B3 bit errors exceed the threshold. Signals degraded (B3). The signal on the receiver line side is lost. The out-of-frame fault occurs on the receive line side. Multiplex section alarm indication.
977
Alarm Name AU_AIS AU_LOP LP_UNEQ_VC3
Correlation AU alarm indication. AU pointer loss. VC-3 path unequipped.
Procedure
Step 1 If the R_LOS/R_LOF alarm is generated, a fiber cut, high attenuation, received overload or faulty board might exist. 1. 2. 3. If the receive optical power is overloaded, add an attenuator. Check whether the optical fiber cables are intact and whether the connectors are clean and properly connected. Replace the fibers or clean the fiber connectors, if necessary. If the board is faulty, replace the board.
Step 2 If the MS_AIS alarm is generated: 1. 2. 3. Check whether the service board at the opposite station is configured with insertion of the MS_AIS alarm. If yes, cancel the configuration. Check whether the transmit unit of the service board at the opposite station is faulty. Check whether the service board reports the MS_AIS alarm by performing self-loop on the fibers. Check the service board of the local station. Reset or replace the board. Then, check whether the MS_AIS alarm is cleared.
Step 3 If the AU_AIS alarm is generated: 1. 2. For the AU_AIS alarm caused by MS_AIS, R_LOS, and R_LOF, analyze the MS_AIS, R_LOS, and R_LOF alarms to locate the fault. Check whether the transmit unit of the service board at the opposite station is faulty. Check whether the service board reports the AU_AIS alarm by performing self-loop on the fibers. If the service board is faulty, reset or replace the board. Then, check whether the AU_AIS alarm is cleared. If the service unit of the local station is faulty, replace the SCC board at the local station.
3.
Step 4 If the AU_LOP alarm is generated: 1. 2. Check whether the service configuration is correct at the local and opposite stations. If not, reconfigure the service. Check whether the opposite clock board works normally and whether the cross-connect unit detects the clock. If the clock board works abnormally, modify the clock configuration and issue it again. Check whether the transmit unit of the service board at the opposite station is faulty. Check whether the service board reports the AS_AIS alarm by performing self-loop on the fibers. If the service board is faulty, reset or replace the board. Then, check whether the AU_AIS alarm is cleared. If the service unit of the local station is faulty, replace the SCC board at the local station.
3.
4.
Step 5 If the LP_UNEQ_VC3 alarm is generated:

1.
Check whether the C2 byte is correctly configured. If not, modify the configuration and issue it again. If yes, the board is judged as faulty. In this case, replace the faulty board.
Step 6 Refer to the 6.126 VC3BBE. ----End
Reference
None.
6.129 VC3FEBBE
The VC3FEBBE is a performance event indicating the VC-3 far end background block error.

If bit errors occur in the services on a remote NE, determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality.
Possible Causes
VC3FEBBE indicates the returned bit errors excluding the bit errors occurring in the VC3 far end unavailable time and VC3 far end severely errored seconds. External causes: l l l l l The fiber performance degrades and the attenuation is excessively high at the opposite station. The fiber connector is dirty or incorrect at the opposite station. The equipment is improperly grounded at the opposite station. There is a strong interference source around the equipment at the opposite station. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems: l The signal attenuation at the receive side of the service board at the opposite station is excessively high, the transmitting circuit of the opposite station is faulty, or the receiving circuit of the local station is faulty. The synchronization performance of the clock is poor at the opposite station. The cross-connect unit and the service board do not work with each other properly at the opposite station. The fan of the opposite equipment becomes faulty. The board fails or the board performance degrades at the opposite station.
l l l l
Issue 02 (2011-10-31)
Relevant Alarms
Alarm Name LP_RDI_VC3 Correlation VC-3 path remote defect indication
Procedure
Step 1 Refer to the 6.126 VC3BBE to handle the NE at the opposite end. ----End
Reference
None.
6.130 VC3FECSES
The VC3FECSES is a performance event indicating the VC-3 far end consecutive severely errored second.

Possible Causes
When a consecutive VC3FECSES sequence is detected, the VC3FECSES performance event occurs. When unavailable time comes or VC3FECSES is absent in one second, the VC3FECSES sequence ends. External causes: l l l l l The fiber performance degrades and the attenuation is excessive at the opposite station. The fiber connector is dirty or incorrect at the opposite station. The equipment is improperly grounded at the opposite station. There is a strong interference source around the equipment at the opposite station. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems: l The signal attenuation at the receive side of the service board at the opposite station is excessively high, the transmitting circuit of the opposite station is faulty, or the receiving circuit of the local station is faulty. The synchronization performance of the clock is poor at the opposite station.
l
Issue 02 (2011-10-31)
l l l
The cross-connect unit and the service board do not work with each other properly at the opposite station. The fan of the opposite equipment becomes faulty. The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Procedure
Step 1 Refer to the 6.131 VC3FEES. ----End
Reference
None.
6.131 VC3FEES
The VC3FEES is a performance event indicating the VC-3 far end errored second.

Possible Causes
The VC3FEES performance event occurs when one or multiple bit errors are returned by the G1 byte in one second or when the LP_RDI_VC3 alarm is detected on the path. External causes: l l l l l The fiber performance degrades and the attenuation is excessively high at the opposite station. The fiber connector is dirty or incorrect at the opposite station. The equipment is improperly grounded at the opposite station. There is a strong interference source around the equipment at the opposite station. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems:
The signal attenuation at the receive side of the service board at the opposite station is excessively high, the transmitting circuit of the opposite station is faulty, or the receiving circuit of the local station is faulty. The synchronization performance of the clock is poor at the opposite station. The cross-connect unit and the service board do not work with each other properly at the opposite station. The fan of the opposite equipment becomes faulty. The board fails or the board performance degrades at the opposite station.
l l l l
Relevant Alarms
Procedure
Step 1 If the LP_RDI_VC3 alarm is generated: 1. 2. Check whether the service board of the opposite station receives an alarm such as TU_AIS_VC3, TU_LOP_VC3 and LP_UNEQ_VC3. If yes, first clear the alarm. If the service board of the opposite station does not receive an alarm such as TU_AIS_VC3, TU_LOP_VC3 and LP_UNEQ_VC3, or if the local station still reports the LP_RDI_VC3 alarm after the opposite station ends this kind of alarm, check whether the opposite station or the local station is faulty by looping back the fibers. If the receive unit of the opposite station is faulty, replace the relevant board. If the transmit part of the local station is faulty, replace the SCC board.
3. 4.
Step 2 Refer to the 6.129 VC3FEBBE. ----End
Reference
None.
6.132 VC3FESES
The VC3FESES is a performance event indicating the VC-3 far end severely errored second.

Possible Causes
The VC3FESES performance event occurs when not less than 30% bit errors are contained in the message returned in one second or at least one severely disturbed period (SDP) occurs. SDP occurs when the BER of all the continuous blocks in a period of at least four continuous blocks or 1 ms (select the longer period) is lower than 10-2, or when the LP_RDI_VC3 alarm is generated. External causes: l l l l l The fiber performance degrades and the attenuation is excessively high at the opposite station. The fiber connector is dirty or incorrect at the opposite station. The equipment is improperly grounded at the opposite station. There is a strong interference source around the equipment at the opposite station. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
l l l l
Relevant Alarms
Procedure
Reference
None.
6.133 VC3FEUAS

The VC3FEUAS is a performance event indicating the VC-3 far end unavailable second.

Possible Causes
VC3FEUAS indicates the period of time that the unavailable time (UAT) state lasts. External causes: l l l l l The fiber performance degrades and the attenuation is excessively high at the opposite station. The fiber connector is dirty or incorrect at the opposite station. The equipment is improperly grounded at the opposite station. There is a strong interference source around the equipment at the opposite station. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
l l l l
Relevant Alarms
Procedure
Reference
None
6.134 VC3SES
The VC3SES is a performance event indicating the VC-3 far end severely errored second.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the B3 bit error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
The VC3SES performance event occurs when not less than 30% bit errors are detected in one second or at least one severely disturbed period (SDP) occurs. The SDP indicates that the BER of all the consecutive blocks is not lower than 10-2 or the R_LOS, R_LOF and MS_AIS alarms are generated in a period of at least four consecutive blocks or i ms (the longer one is selected), or the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected on the path. External causes: l l l l l The fiber performance is degraded, and the attenuation of the fiber is excessively high. The fiber connector is dirty or incorrect. The equipment is improperly grounded. There is a strong interference source around the equipment. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
l l l
Relevant Alarms
Alarm Name B3_EXC_VC3 B3_SD_VC3 R_LOS R_LOF
Issue 02 (2011-10-31)
Correlation B3 bit errors exceed the threshold. Signals degraded (B3). The signal on the receiver line side is lost. The out-of-frame fault occurs on the receiver line side.
985
Alarm Name MS_AIS AU_AIS AU_LOP LP_UNEQ_VC3
Correlation Multiplex section alarm indication. AU alarm indication. AU pointer loss. VC-3 path unequipped.
Procedure
Reference
None.
6.135 VC3UAS
The VC3UAS is a performance event indicating the VC-3 unavailable second.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the B3 bit error threshold and degrade threshold, the B3_EXC_VC3 and B3_SD_VC3 alarms will be generated.
Possible Causes
VC3UAS indicates the period of time that the unavailable time (UAT) state lasts. External causes: l l l l l The fiber performance is degraded, and the attenuation of the fiber is excessively high. The fiber connector is dirty or incorrect. The equipment is improperly grounded. There is a strong interference source around the equipment. The working temperature is excessively high or low, and the opposite equipment cannot tolerate such temperature.
Equipment problems:
The signal attenuation at the receive side of the service board is excessively high, the transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end is faulty. The synchronization performance of the clock is poor. The cross-connect unit and the service board do not work with each other properly. The board becomes faulty, or the performance of the board is degraded.
l l l
Relevant Alarms
Alarm Name B3_EXC_VC3 B3_SD_VC3 R_LOS R_LOF MS_AIS AU_AIS AU_LOP LP_UNEQ_VC3 Correlation B3 bit errors exceed the threshold. Signals degraded (B3). The signal on the receiver line side is lost. The out-of-frame fault occurs on the receiver line side. Multiplex section alarm indication. AU alarm indication. AU pointer loss. VC-3 path unequipped.
Procedure
Reference
None
6.136 WCV
Description
Pump laser working current, also called pump laser driver current or pump laser bias current. It includes: l l l WCVMAX: stands for the maximum value during a period of time (in 1 mA). WCVMIN: stands for the minimum value during a period of time (in 1 mA). WCVCUR: stands for the current value (in 1 mA).
Issue 02 (2011-10-31)
987
Impact on System
When the pump laser works normally, there is no impact on the services. If an alarm is generated, determine the cause.

WCV indicates the pump laser driver current of an optical amplifier board. The optical amplifier board amplifies the input signal using the pump laser driven by pump laser working current.
Related Alarms
Alarm Name PUM_BCM_ALM Correlation The board reports this alarm when the detected pump laser driver current is higher than the threshold due to laser exceptions caused by laser aging, or over-high/low ambient temperature. The board reports this alarm when the pump laser driver current is higher than the termination threshold due to laser aging. Transmitter degrade alarm. The alarm is generated when the bias current of the laser exceeds the degrade threshold.
LSR_WILL_DIE TD
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the handling procedure of the alarm. Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm. Step 3 If the TD alarm is generated, see the handling procedure of the alarm. ----End
Related Information
None
6.137 XCSTMP
Description
Board environmental temperature It includes: l l l
Issue 02 (2011-10-31)
XCSTMPMAX: stands for the maximum value during a period of time. XCSTMPMIN: stands for the minimum value during a period of time. XCSTMPCUR: stands for the current value.
Impact on System
Excessively high or low board temperature might cause faults such as degradation of the board working performance and bit errors.

This performance event is generated by hardware detecting to show the ambient temperature of the board. When the ambient temperature is abnormal, or when the heat-sinking and ventilation measures are improper, the XCSTEMP event occurs.
Related Alarms
Alarm Name TEMP_OVER Correlation It is generated when the ambient temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the proper handling procedures. ----End
Related Information
None
Issue 02 (2011-10-31)
989
7 Event List
7
This section list the common events. Table 7-1 Events regarding APE and EAPE Name APE adjust finished Level Warning Description APE adjust failed Critical
Event List
APE adjustment starts upon an APE adjustment start command. When the adjustment is complete, an APE adjust finished is reported. When APE adjustment is terminated upon an APE adjustment stop command issued by the user or due to other causes, an APE adjust failed event is reported. When EAPE adjustment is complete, an EAPE adjustment result notification event is reported to indicate whether the adjustment is successful. When EAPE adjustment becomes abnormal, an EAPE abnormal notification event is reported.
EAPE adjustment result notification event
Major
EAPE abnormal notification event
Major
Table 7-2 Events regarding IPA Name IPA abnormal event Level Major Description When IPA adjustment is terminated due to a fault of the laser, an IPA abnormal event is reported.
Issue 02 (2011-10-31)
990
7 Event List
Table 7-3 Events regarding ROADM Name ROADM wave conflict event Level Critical Description If a passthrough wavelength conflicts with an add wavelength of the OTU after a wavelength resource consistency check is started, an ROADM wavelength conflict event is reported. When the system starts a wavelength resource consistency check, an ROADM wave check event is reported. When actions such as setting wavelength blocking and deleting intra-board optical cross-connections are performed, an ROADM wave reconfig event is reported. When the optical power equalization adjustment at an ROADM node is started, an ROADM power adjust event is reported. After a wavelength resource consistency check at an ROADM node is started, the logic wavelength group of the node is in an idle or abnormal state. That is, if the node passes the check, the group returns the idle state; if the node fails the check, the group enters into the abnormal state. If the status of the logic wavelength group changes, an ROADM wave state change event is reported.
ROADM wave check event
Critical
ROADM wave reconfig event
Critical
ROADM power adjust event
Critical
ROADM wave state change event
Critical
Table 7-4 Events regarding protection Name OWSP abnormal event Level Major Description This event is reported when the optical wavelength shared protection switching occurs. This event is reported when an ODUk SPRing protection switching occurs. This event is reported when a protection switching occurs on a cross-connect board or on the system control and communication (SCC) board.
ODUk SPRing abnormal event 1+1 equipment-level protection switching event
Major Critical
Issue 02 (2011-10-31)
991
7 Event List
Table 7-5 Other events Name RMON performance value is above the upper limit RMON module performance value is lower than the lower threshold Level Minor Description This event is automatically reported when the performance value in the sampling period is higher than the upper threshold. In the sampling period, an event indicating upper threshold crossing occurs. In a new sampling period, when the sampling value is less than or is equal to the lower threshold value, this event is reported.
Minor
Issue 02 (2011-10-31)
992
8 Event Processing
8
About This Chapter
NOTE
Event Processing
This chapter describes information relevant to event handling, including event descriptions, event attribute, event parameters, impacts of events on the system, event causes, and event handling procedures.
In the case of an event, refer to its handling procedure to clear it; if this event persists, contact a customer service technician of Huawei for troubleshooting.
When you view an event on the network management system, select the event. In the Detail Description in the Event Details field display the related parameters of the event. 8.1 EAPE abnormal event notification 8.2 EAPE adjustment result event notification 8.3 OWSP abnormal event 8.4 ODUk SPRing abnormal event 8.5 RMON performance value is above the upper limit 8.6 RMON module performance value is lower than the lower threshold 8.7 1+1 Equipment Level Protection Switching Event Report
Issue 02 (2011-10-31)
993
8 Event Processing
8.1 EAPE abnormal event notification

Description
An event indicating that the EAPE meets the conditions for adjustment. This event indicates that the current status of the system allows for EAPE adjustment.
Attribute
Event Severity Major Event Type Equipment
Parameter
Parameter Parameter 1 Parameter 2 Parameter 3 Parameter 4 Description Indicates the configuration index number for the EAPE pair, such as 1. Indicates the current pre-correction BER of the sink OTU. Indicates the current input optical power of the sink OTU (in the unit of 0.1 dBm). Indicates the BIP8 bit error status in the SM section for the sink OTU. When this event is reported, only the Normal status is present, indicating that the current bit error is zero.
Impact on System
When this event occurs, the EAPE pair of the system meets the conditions for adjustment. In this case, starting the adjustment does not affect the services.
Possible Causes
Cause 1: The system is configured with an EAPE pair and the EAPE pair meets the conditions for adjustment. That is, the input optical power does not cross the threshold, the BIP8 bit error in the SM section is zero, or the pre-correction BER degrades.
Procedure
l Cause 1: The system is configured with an EAPE pair and the EAPE pair meets the conditions for adjustment.
Issue 02 (2011-10-31)
8 Event Processing
1. ----End
On the U2000, start the EAPE automatic adjustment. For details, refer to the Feature Description.
Related Information
None
8.2 EAPE adjustment result event notification

Description
An event indicating the end of the EAPE adjustment. When the EAPE adjustment is complete, the adjustment result event is reported, indicating whether the adjustment is successful or not.
Attribute
Event Severity Major Event Type Equipment
Parameter
Parameter Parameter 1 Description Indicates the configuration index number for the EAPE pair, such as 1.
Issue 02 (2011-10-31)
995
8 Event Processing
Description Indicates the cause for the end of the adjustment. The values of the parameter are as follows: succeed manual adjust no balance after adjusting communication failed board uninstalled board type error board offline vmux carry error board response error system error adjust ne not found choice ne not found condition not meet choice board not found no reason
Parameter 3 Parameter 4 Parameter 5 Parameter 6
Indicates the ID of the NE where the adjustment is successful or fails. Indicates the slot number of the board where the adjustment is successful or fails. Indicates the number of the optical interface where the adjustment is successful or fails. Indicates the number of the channel where the adjustment is successful or fails.
Impact on System
If an adjustment success is reported, the system BER is lowered and the signal transmission quality is improved. If an adjustment failure is reported, the signal transmission quality needs to be improved.
Possible Causes
l l l l
Issue 02 (2011-10-31)
Cause 1: The adjustment is successful. Cause 2: The user manually issues a command to stop the adjustment. Cause 3: After the adjustment is performed for six times, the pre-correction BER of the sink OTU does not reach the expected value. Cause 4: The inter-NE communication fails.
8 Event Processing
l l l l l l l l l
Cause 5: The logical board is not installed. Cause 6: The board type is incorrect. Cause 7: The board is not in position. Cause 8: The attenuation of the board with attenuator is adjusted to the extreme. Cause 9: The board incorrectly responds to the command. Cause 10: The system has an error, for example, operation to database fails. Cause 11: The address of the NE where the adjustment is to be performed cannot be found. Cause 12: The address of the NE where signals are selectively received cannot be found. Cause 13: The EAPE pair does not meet the conditions for starting the adjustment. The start-up conditions are as follows: The input optical power does not cross the threshold. The BIP8 value in the SM section is zero. The pre-correction BER degrades.
l l
Cause 14: The board that selectively receives signals is in an incorrect state. Cause 15: Other causes.
Procedure
l l l Cause 1: The adjustment is successful. 1. 1. Ignore the event. Ignore the event. Cause 2: The user manually issues a command to stop the adjustment. Cause 3: After the adjustment is performed for six times, the pre-correction BER of the sink OTU does not reach the expected value. 1. 2. 3. Check whether the pre-correction BER of the sink OTU is lowered. If yes, proceed with the adjustment. If the BER is not lowered, the EAPE function does not meet the requirements of the system. In this case, refer to section "Rectifying Bit Errors" in the Troubleshooting to handle the BER. On the U2000, check whether NEs involved in the EAPE pair normally communicate with each other.
Cause 4: The inter-NE communication fails. 1.
Causes 57: The logical board is not installed, or the board type is incorrect, the board is not in position. 1. Find the board according to the NE ID and slot number indicated by event parameters and then install the board or replace the board with one of the correct type. Check whether the attenuation of the board is adjusted to the extreme according to the NE ID, slot number, optical interface number, and channel number indicated by the event parameters. If yes, the system cannot continue the EAPE adjustment. In this case, check whether the optical power of signals is normal. For specifications, refer to the Product Description.
Cause 8: The attenuation of the board with attenuator is adjusted to the extreme. 1.
l
Issue 02 (2011-10-31)
Cause 9: The board incorrectly responds to the command.

8 Event Processing
1.
Find the board according to the NE ID and slot number indicated by event parameters and query alarms related to the board. Handle the alarms by seeing the Handling Procedure parts for respective alarms. Reconfigure the EAPE and start another EAPE adjustment. For details, refer to the Feature Description.
Cause 10 or Cause 15: The system has an error, or other causes. 1.
Cause 11 or Cause 12: The address of the NE where the adjustment is to be performed cannot be found, or the address of the NE where signals are selectively received cannot be found. 1. 2. Check the network connection between the NEs, and ensure the connection between the NEs is correct. On the U2000, check for the configuration information about the EAPE pair. If there is no configuration information about the EAPE pair, reconfigure the EAPE pair. Check the parameters such as the input optical power and performance of the sink board meet the conditions for adjustment. If not, the system cannot perform the EAPE adjustment. Check whether the board that selectively receiving signals is normal. Query alarms related to this board and handle the alarms by seeing the Handling Procedure parts for respective alarms.
Cause 13: The EAPE pair does not meet the conditions for starting the adjustment. 1.
Cause 14: The board that selectively receives signals is in an incorrect state. 1.
----End
Related Information
None
8.3 OWSP abnormal event

Description
An event indicating the optical wavelength shared protection. When the optical wavelength shared protection switching occurs, this event is reported.
Attribute
Event Severity Major Event Type Communication
Parameter
Parameter Parameter 1 Description Indicates the ID of the protection group where the protection switching occurs.
Issue 02 (2011-10-31)
8 Event Processing
Description Indicates the status of the westbound working channel. The values of the parameter are as follows: SF, SD, normal, unknown, unmonitored
Parameter 3
Indicates the status of the westbound protection channel. The values of the parameter are as follows: SF, SD, normal, unknown, unmonitored
Parameter 4
Indicates the status of the eastbound working channel. The values of the parameter are as follows: SF, SD, normal, unknown, unmonitored
Parameter 5
Indicates the status of the eastbound protection channel. The values of the parameter are as follows: SF, SD, normal, unknown, unmonitored
Parameter 6
Indicates the switching request of the westbound channel. The values of the parameter are as follows: no request response request exercise switching - ring WTR - ring switching manual switching - ring SD ring switching - working SD protection OK SD ring switching - working SD protection SD protection SD forced switching - ring SF ring switching - working SF protection OK SF ring switching - working SF protection SD SF ring switching - working SD protection SF SF ring switching - working SF protection SF protection SF locked
Parameter 7
Indicates the switching request of the eastbound channel. The values of the parameter are the same as those of Parameter 6.
Issue 02 (2011-10-31)
999
8 Event Processing
Description Indicates current page status. The values of the parameter are as follows: stopped starting idle east switching west switching full pass-through APS pass-through
Parameter 9
Indicates the indication of westbound remote and local ends. The values of the parameter are as follows: remote-end, near-end
Parameter 10
Indicates the indication of eastbound remote and local ends. The values of the parameter are as follows: remote-end, near-end
Impact on System
When the switching occurs in the wavelength shared protection group, the services in the system are transiently interrupted. When this event is reported, it indicates that the service in the current working channel of the protection group may be abnormal. In this case, find and rectify the fault.
Possible Causes
l l Cause 1: The current working channel is abnormal. Cause 2: An external switching command is issued.
Procedure
l Cause 1: The current working channel is abnormal. 1. Find out the cause and rectify the fault according to the alarm information reported in the current working channel. For details on the operation, see Alarm Processing parts for respective alarms. Ignore the event.
Cause 2: An external switching command is issued. 1.
----End
Related Information
None
Issue 02 (2011-10-31)
1000
8 Event Processing
8.4 ODUk SPRing abnormal event

Description
An event indicating the ODUk protection. When the switching occurs in the ODUk SPRing protection group, the working channel is switched to the protection channel, or the protection channel is switched to the working channel. In this case, this event, indicating that the switching occurs in the protection group, is reported.
Attribute
Event Severity Major Event Type Communication
Parameter
Parameter Parameter 1 Parameter 2 Description Indicates the ID of the protection group where this event occurs. Indicates the current status of the westbound working channel. The values of the parameter are as follows: SF, SD, normal, unknown, unmonitored Parameter 3 Indicates the current status of the westbound protection channel. The values of the parameter are the same as those of Parameter 2. Indicates the current status of the eastbound working channel. The values of the parameter are the same as those of Parameter 2. Indicates the current status of the eastbound protection channel. The values of the parameter are the same as those of Parameter 2. Indicates the current page of the protection group. The values of the parameter are as follows: stopped starting idle east switching west switching full pass-through APS pass-through
Parameter 4
Parameter 5
Parameter 6
8 Event Processing
Description Indicates the switching request of the westbound channel of the protection group. The values of the parameter are as follows: no req exercise sw WTR - ring sw manual sw SD sw - work SD pro OK SD sw - work SD pro SD pro SD forced sw SF sw - work SF pro OK SF sw - work SF pro SD SF sw - work SD pro SF SF sw - work SF pro SF pro SF locked
Parameter 8
Indicates the switching request of eastbound channel of the protection group. The values of the parameter are the same as those of Parameter 7. Indicates the westbound remote and local indication, and indicates whether the local station is the initiating end of the switching. The values of the parameter are as follows: remote local station as the responding end near local station as the initiating end
Parameter 9
Parameter 10
Indicates the eastbound remote and local indication, and indicates whether the local station is the initiating end of the switching. The values of the parameter are as those of Parameter 9.
Impact on System
When the switching occurs in the ODUk SPRing protection group, the service is transiently interrupted. After this event is reported, if the ODUk SPRing protection group is currently in the switching page, it indicates that the service in the westbound working channel or eastbound working channel in the ODUk SPRing protection group is abnormal. In this case, find and rectify the fault.
Issue 02 (2011-10-31)
1002
8 Event Processing
Possible Causes
l Cause 1: The user issues an external switching command, such as forced switching or manual switching. Hence, in the ODUk SPRing protection group, the working channel in a direction is switched to the protection channel in another direction, or the protection channel in a direction is switched to the working channel in another direction. In this case, this event is reported. Cause 2: When the service in the working channel of the ODUk SPRing protection group is abnormal, the service is automatically switched to the protection channel. When the service in the protection channel is abnormal, the service is automatically switched to the working channel. Hence, this event is reported. Cause 3: If the service in the working channel of the ODUk SPRing is restored, after the WTR time elapses, the service in the protection channel is automatically switched to the working channel. Hence, this event is reported.
Procedure
l Cause 1 or Cause 3: The user issues an external switching command, or after the WTR time elapses, the service in the protection channel is automatically switched to the working channel. 1. l 1. ----End Ignore the event. On the U2000, query the related switching alarms. For details, see Handling Procedure parts for respective alarms. Cause 2: The service is automatically switched to the protection channel
Related Information
None
8.5 RMON performance value is above the upper limit

Description
An event indicating that the performance value of the RMON module exceeds the upper threshold. When the performance value in the sampling period is higher than the upper threshold, this event is automatically reported. For example, when the performance value of collisions exceeds the upper threshold, the event is reported.
Attribute
Event Severity Minor Event Type Communication
Issue 02 (2011-10-31)
1003
8 Event Processing
Parameter
Parameter Parameter 1 Parameter 2 Description Indicates the slot ID, port number and channel number, such as 1-LOG-2(ETHER):1. Indicates the performance event of threshold crossing. The values of the parameter are as follows: Drop Events FCS and Alignment Errors Undersize Packets Received Oversize Packets Received Fragments Jabbers Collisions Bad Octets Received Bad Octets Transmitted Alignment Errors FCS Errors Late Collisions Excessive Collisions Deferred Transmissions Carrier Sense Errors Drop Events at Transmission Direction Parameter 3 Parameter 4 Indicates the performance value. Indicates the higher threshold value.
Impact on System
The quality of the Ethernet service is degraded, or even the services in the system are interrupted.
Possible Causes
l l l l l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits the data packets. Cause 2: The working modes of the ports at the local and opposite ends mismatch. Cause 3: The optical line attenuation is excessively large or the receive optical power is abnormal. Cause 4: The optical fiber is damaged or the fiber connector is untidy. Cause 5: The board that reports this alarm is faulty.
Issue 02 (2011-10-31)
1004
8 Event Processing
Procedure
l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits the data packets. 1. Use the smartbits equipment to check whether bit errors occur in the data transmitted at the client side. If bit errors occur, find and rectify the fault of the client-side equipment. On the U2000, query whether the working modes of the ports at the two ends of the equipment match. If the working modes mismatch, adjust the working modes of the ports according to the actual situation.
Cause 2: The working modes of the ports at the local and opposite ends mismatch. 1.
Cause 3: The optical line attenuation is excessively large or the receive optical power is abnormal. 1. Check whether the received optical power of the interface is within the normal range by using the U2000. For the optical power specifications of a specific board, see the Product Description. If the optical power is not within the normal range, takes handling measures according to the handling method of the IN_PWR_HIGH or IN_PWR_LOW alarm. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details, see the Supporting Tasks. If this event persists, replace the faulty board. For details on operations, see the Parts Replacement.
Cause 4: The optical fiber is damaged or the fiber connector is untidy. 1.
----End
Related Information
None
8.6 RMON module performance value is lower than the lower threshold
Description
An event indicating that the RMON module performance value is lower than the lower threshold. In the sampling period, an event indicating upper threshold crossing occurs. In a new sampling period, when the sampling value is less than or is equal to the lower threshold value, and the reporting mode is that this event is reported when the performance value is lower than the lower threshold value, or that this event is reported when the performance value is higher than the upper threshold value or lower than the lower threshold value, this event is reported.
Attribute
Event Severity Minor Event Type Communication
Issue 02 (2011-10-31)
1005
8 Event Processing
Parameter
Parameter Parameter 1 Parameter 2 Description Indicates the slot ID, port number and channel number, such as 1-LOG-2(ETHER):1. Indicates the performance event of threshold crossing. The values of the parameter are as follows: Drop Events FCS and Alignment Errors Undersize Packets Received Oversize Packets Received Fragments Jabbers Collisions Bad Octets Received Bad Octets Transmitted Alignment Errors FCS Errors Late Collisions Excessive Collisions Deferred Transmissions Carrier Sense Errors Drop Events at Transmission Direction Parameter 3 Parameter 4 Indicates the performance value. Indicates the lower threshold value.
Impact on System
When this event is reported, it indicates that the related Ethernet performance values are recovered. The quality of the Ethernet service in the system is improved.
Possible Causes
The fault of the system is rectified, and the performance value is recovered.
Procedure
l Ignore the event. ----End
Related Information
None
8 Event Processing
8.7 1+1 Equipment Level Protection Switching Event Report

Description
1+1 Equipment Level Protection Switching Event Report, when the board protection switching occurs, this event is reported.
Attribute
Event Severity Critical Event Type Equipment
Parameter
Parameter Parameter 1 Description Indicates the ID of the protection group where this event occurs, The values of the parameter are as follows: The value is 1, indicates the SCC board protection switching occurs. The value is 1, indicates the cross-connect board protection switching occurs. The value is 2, indicates the SCC board protection switching occurs. Parameter 2 Parameter 3 Indicates the slot ID of the current working board, such as "9". Indicates the slot ID of the current protection board, such as "10".
Impact on System
When the cross-connect board protection switching occurs in the protection group, the service may be transiently interrupted.
Possible Causes
l Cause 1: The user issues an external switching command, such as forced switching or clearing. In this case, the working unit of the protection group is switched to the protection unit, or the protection unit is switched to the working unit, this event is reported. Cause 2: When one unit in the protection group is abnormal, the protection group is switched to another unit. In this case, this event is reported.
Issue 02 (2011-10-31)
8 Event Processing
Procedure
l l Cause 1: The user issues an external switching command. 1. Ignore the event. Cause 2: When one unit in the protection group is abnormal, the protection group is switched to another unit. In this case, this event is reported. 1. ----End If this event persists, replace the faulty board. For details on operations, see Parts Replacement.
Related Information
None
Issue 02 (2011-10-31)
1008
A Glossary
A
A
AC access control list ACK acknowledgement See alternating current See acknowledgement
Glossary
A list of entities, together with their access rights, which are authorized to have access to a resource. A response sent by a receiver to indicate successful reception of information. Acknowledgements may be implemented at any level including the physical level (using voltage on one or more wires to coordinate transfer), at the link level (to indicate successful transmission across a single hardware link), or at higher levels. See access control list Network elements that provide access to all or some subset of the constituent signals contained within an STM-N signal. The constituent signals are added to (inserted), and/ or dropped from (extracted) the STM-N signal as it passed through the ADM. Add/drop wavelength refers to the wavelength that carries the add/drop services in the OADM equipment. Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and routers to determine the link layer addresses through ARP requests and ARP responses. The address resolution is a process in which the host converts the target IP address into a target MAC address before transmitting a frame. The basic function of the ARP is to query the MAC address of the target equipment through its IP address. See add/drop multiplexer The information structure which provides adaptation between the higher order path layer and the multiplex section layer. It consists of an information payload (the higher order VC) and an AU pointer which indicates the offset of the payload frame start relative to the multiplex section frame start. A user who has authority to access all the Management Domains of the EMLCore product. He has access to the whole network and to all the management functionalities. See asymmetric digital subscriber line See automatic gain control
ACL add/drop multiplexer
Add/drop wavelength Address Resolution Protocol
ADM administrative unit
Administrator ADSL AGC
Issue 02 (2011-10-31)
1009
A Glossary
AID AIS alarm
access identifier See alarm indication signal A message reported when a fault is detected by a device or by the network management system during the process of polling devices. Each alarm corresponds to a recovery alarm. After a recovery alarm is received, the status of the corresponding alarm changes to cleared. The cable for generation of visual or audio alarms. The shunt-wound output of the alarm signals of several subracks or cabinets. A single disturbance or fault may lead to the detection of multiple defects. A fault cause is the result of a correlation process which is intended to identify the defect that is representative of the disturbance or fault that is causing the problem. On the cabinet of an NE, there are four indicators in different colors indicating the current status of the NE. When the green indicator is on, it indicates that the NE is powered on. When the red indicator is on, it indicates that a critical alarm is generated. When the orange indicator is on, it indicates that a major alarm is generated. When the yellow indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on the front panel of a board indicates the current status of the board.
alarm cable alarm cascading alarm cause
alarm indication
alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multiple transport layers. alarm mask On the host, an alarm management method through which users can set conditions for the system to discard (not to save, display, or query for) the alarm information meeting the conditions. The significance of a change in system performance or events. According to ITU-T recommendations, an alarm can have one of the following severities: Critical, Major, Minor, Warning. A function used not to monitor alarms for a specific object, which may be the networkwide equipment, a specific NE, a specific board and even a specific function module of a specific board. Classification of alarms with different attributes. There are six alarm types as following: Communication: alarm indication related with information transfer. Processing: alarm indication related with software or information processing Equipment: alarm indication related with equipment fault Service: alarm indication related with QoS of the equipment Environment: alarm related with the environment where the equipment resides, usually generated by a sensor Security: alarm indication related with security See automatic level control A piece of end-to-end configuration information, which exists in the equipment (single station) as an ALC link node. Through the ALC function of each node, it fulfils optical power control on the line that contains the link. The ALC functional unit. It corresponds to the NE in a network. The power detect unit, variable optical attenuator unit, and supervisory channel unit at the ALC node work together to achieve the ALC function. See automatic laser shutdown Electric current that reverses its direction of flow (polarity) periodically according to a frequency measured in hertz, or cycles per second.
alarm severity
alarm suppression
alarm type
ALC ALC link
ALC node
ALS alternating current
Issue 02 (2011-10-31)
1010
A Glossary
American National Standard Institute American Standard Code for Information Interchange ANSI antistatic floor APD APE APID application-specific integrated circuit
An organization that defines U.S standards for the information processing industry. American National Standard Institute (ANSI) participates in defining network protocol standards. American Standard Code for Information Interchange - the standard system for representing letters and symbols. Each letter or symbol is assigned a unique number between 0 and 127. See American National Standard Institute A floor that can quickly release the static electricity of the object contacting it to prevent accumulated static electricity See avalanche photodiode automatic power equilibrium access point identifier A special type of chip that starts out as a nonspecific collection of logic gates. Late in the manufacturing process, a layer is added to connect the gates for a specific function. By changing the pattern of connections, the manufacturer can make the chip suitable for many needs. See automatic protection switching See Address Resolution Protocol A device, built with silicon planar lightwave circuits (PLC), that allows multiple wavelengths to be combined and separated in a dense wavelength-division multiplexing (DWDM) system. See American Standard Code for Information Interchange amplified spontaneous emission See application-specific integrated circuit See automatically switched optical network A technology for transmitting digital information at a high bandwidth on existing phone lines to homes and businesses. Unlike regular dialup phone service, ADSL provides continuously-available, "always on" connection. ADSL is asymmetric in that it uses most of the channel to transmit downstream to the user and only a small part to receive information from the user. ADSL simultaneously accommodates analog (voice) information on the same line. ADSL is generally offered at downstream data rates from 512 Kbps to about 6 Mbps. A protocol for the transmission of a variety of digital signals using uniform 53 byte cells. A transfer mode in which the information is organized into cells; it is asynchronous in the sense that the recurrence of cells depends on the required or instantaneous bit rate. Statistical and deterministic values may also be used to qualify the transfer mode. autonomously generated correlation tag See Asynchronous Transfer Mode See administrative unit An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to automatically exchange information over a link about speed and duplex abilities.
APS ARP arrayed waveguide grating ASCII ASE ASIC ASON asymmetric digital subscriber line
Asynchronous Transfer Mode
ATAG ATM AU auto-negotiation
Issue 02 (2011-10-31)
1011
A Glossary
automatic gain control A process or means by which gain is automatically adjusted in a specified manner as a function of a specified parameter, such as received signal level. automatic laser shutdown A technique (procedure) to automatically shutdown the output power of laser transmitters and optical amplifiers to avoid exposure to hazardous levels.
automatic level control A well-known application in communication systems with a given input signal conditioned to produce an output signal as possible, while supporting a wide gain range and controlled gain-reduction and gain recovery characteristics. automatic protection switching Capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic.
automatically switched A network which is based on technology enabling the automatic delivery of transport optical network services. Specifically, an ASON can deliver not only leased-line connections but also other transport services such as soft-permanent and switched optical connections. avalanche photodiode A semiconductor photodetector with integral detection and amplification stages. Electrons generated at a p/n junction are accelerated in a region where they free an avalanche of other electrons. APDs can detect faint signals but require higher voltages than other semiconductor electronics. See arrayed waveguide grating
AWG
B
background block error ratio backup The ratio of background block errors (BBE) to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs. A periodic operation performed on the data stored in the database for the purposes of database recovery in case that the database is faulty. The backup also refers to data synchronization between active and standby boards. A range of transmission frequencies that a transmission line or channel can carry in a network. In fact, it is the difference between the highest and lowest frequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate. See broadband access server A firmware stored in the computer mainboard. It contains basic input/output control programs, power-on self test (POST) programs, bootstraps, and system setting information. The BIOS provides hardware setting and control functions for the computer. A connector used for connecting two coaxial cables. background block error See background block error ratio See boundary clock Backward Defect Indication backward error indication See bit error rate backward incoming alignment error
bandwidth
BAS basic input/output system bayonet-neillconcelman BBE BBER BC BDI BEI BER BIAE
Issue 02 (2011-10-31)
1012
A Glossary
bill of material
Listing of all the subassemblies, parts and raw materials that go into the parent assembly. It shows the quantity of each raw material required to make the assembly. There are a variety of display formats for BOMS, including single level, indented, modular/ planning, transient, matrix and costed BOMs [APICs, CMSG]. See basic input/output system See bit-interleaved parity See bit interleaved parity order 8 An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal. Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network. A frame is divided into several blocks with 8 bits (one byte)in a parity unit. Then arrange the blocks in matrix. Compute the number of "1" over each column. Then fill a 1 in the corresponding bit for the result if the number is odd, otherwise fill a 0. A method of error monitoring. With even parity an X-bit code is generated by the transmitting equipment over a specified portion of the signal in such a manner that the first bit of the code provides even parity over the first bit of all X-bit sequences in the covered portion of the signal, the second bit provides even parity over the second bit of all X-bit sequences within the specified portion, etc. Even parity is generated by setting the BIP-X bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits which are in the same bit position within the X-bit sequences in the covered portion of the signal. The covered portion includes the BIP-X. See building integrated timing supply best master clock See bayonet-neill-concelman See bill of material A clock with a clock port for each of two or more distinct PTP communication paths. See bridge protocol data unit board-level protection switching The data messages that are exchanged across the switches within an extended LAN that uses a spanning tree protocol (STP) topology. BPDU packets contain information on ports, addresses, priorities and costs and ensure that the data ends up where it was intended to go. BPDU messages are exchanged across bridges to detect loops in a network topology. The loops are then removed by shutting down selected bridges interfaces and placing redundant switch ports in a backup, or blocked, state. The action of transmitting identical traffic on the working and protection channels simultaneously. A server providing features as user access, connection management, address allocation and authentication, authorization and accounting. It also works as a router featuring effective route management, high forwarding performance and abundant services. A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address.
BIOS BIP BIP-8 bit error bit error rate bit interleaved parity order 8 bit-interleaved parity
BITS BMC BNC BOM boundary clock BPDU BPS bridge protocol data unit
bridging broadband access server broadcast
Issue 02 (2011-10-31)
1013
A Glossary
broadcast service building integrated timing supply
The unidirectional services from one service source to multiple service sinks. In the situation of multiple synchronous nodes or communication devices, one can use a device to set up a clock system on the hinge of telecom network to connect the synchronous network as a whole, and provide satisfactory synchronous base signals to the building integrated device. This device is called BITS. Backbone WDM System
BWS
C
cable tie capex capital expenditure The tape used to bind the cables. See capital expenditure Capital expenditures (CAPEX or capex) are expenditures creating future benefits. A capital expenditure is incurred when a business spends money either to buy fixed assets or to add to the value of an existing fixed asset with a useful life that extends beyond the taxable year. Capex are used by a company to acquire or upgrade physical assets such as equipment, property, or industrial buildings. See committed access rate See committed burst size See connectivity check connection control interface See continuity check message chromatic dispersion See Code Division Multiple Access See customer edge See European Committee for Electrotechnical Standardization
CAR CBS CC CCI CCM CD CDMA CE CENELEC
central processing unit The computational and control unit of a computer. The CPU is the device that interprets and executes instructions. The CPU has the ability to fetch, decode, and execute instructions and to transfer information to and from other resources over the computer's main data-transfer path, the bus. centralized alarm system CF CGMP channel The system that gathers all the information about alarms into a certain terminal console. See compact flash Cisco Group Management Protocol A telecommunication path of a specific capacity and/or at a specific speed between two or more locations in a network. The channel can be established through wire, radio (microwave), fiber or a combination of the three. The amount of information transmitted per second in a channel is the information transmission speed, expressed in bits per second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s (1012 bit/s). The center-to-center difference in frequency or wavelength between adjacent channels in a WDM device. See committed information rate
channel spacing CIR
Issue 02 (2011-10-31)
1014
A Glossary
CIST CLEI CLNP CLNS clock synchronization
Common and Internal Spanning Tree common language equipment identification connectionless network protocol connectionless network service Also called frequency synchronization, clock synchronization means that the signal frequency traces the reference frequency, but the start point need not be consistent.
clock synchronization A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588 compliant with V2 standard specifies the precision time protocol (PTP) in a measurement and control precision time protocol system. The PTP protocol ensures clock synchronization precise to sub-microseconds. clock tracing CM CMEP CMI coarse wavelength division multiplexing The method to keep the time on each node being synchronized with a clock source in a network. See configuration management connection monitoring end point coded mark inversion A signal transmission technology that multiplexes widely-spaced optical channels into the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM does not support optical amplifiers and is applied in short-distance chain networking.
Code Division Multiple A communication scheme that forms different code sequences by using the frequency Access expansion technology. In this case, subscribers of different addresses can use different code sequences for multi-address connection. committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface. CAR is a configurable method by which incoming and outgoing packets can be classified into QoS (Quality of Service) groups, and by which the input or output transmission rate can be defined. committed burst size. A parameter used to define the capacity of token bucket C, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.
committed burst size
committed information The rate at which a frame relay network agrees to transfer information in normal rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to the leaky bucket. Common Object Request Broker Architecture A specification developed by the Object Management Group in 1992 in which pieces of programs (objects) communicate with other objects in other programs, even if the two programs are written in different programming languages and are running on different platforms. A program makes its request for objects through an object request broker, or ORB, and thus does not need to know the structure of the program from which the object comes. CORBA is designed to work in object-oriented environments. See also IIOP, object (definition 2), Object Management Group, object-oriented. Compact flash (CF) was originally developed as a type of data storage device used in portable electronic devices. For storage, CompactFlash typically uses flash memory in a standardized enclosure. A process that combines multiple virtual containers. The combined capacities can be used a single capacity. The concatenation also keeps the integrity of bit sequence.
compact flash
concatenation
Issue 02 (2011-10-31)
1015
A Glossary
Configuration Data
A command file defining hardware configurations of an NE. With this file, an NE can collaborate with other Nes in an entire network. Thus, configuration data is the key factor for normal running of an entire network. 1. A network management function defined by the International Standards Organization (ISO). It involves installing, reinitializing & modifying hardware & software. 2. Configuration Management (CM) is a system for collecting the configuration information of all nodes in the network.
configuration management
configure congestion connecting plate connection point
To set the basic parameters of an operation object. An extra intra-network or inter-network traffic resulting in decreasing network service efficiency. A metallic plate which is used to combine two cabinets. A reference point where the output of a trail termination source or a connection is bound to the input of another connection, or where the output of a connection is bound to the input of a trail termination sink or another connection. The connection point is characterized by the information which passes across it. A bidirectional connection point is formed by the association of a contradirectional pair. Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically. CCM is used to detect the link status. 1. A process in which multiple channels of low-rate signals are multiplexed into one or several channels of required signals. 2. It refers to the speed and capability for a group of networking devices to run a specific routing protocol. It functions to keep the network topology consistent.
connectivity check continuity check message convergence
convergence service CORBA corrugated pipe CPLD CPU CRC CSA CSES CSMA CST current alarm current performance data
A service that provides enhancements to an underlying service in order to provide for the specific requirements of the convergence service user. See Common Object Request Broker Architecture Used to protect optical fibers. Complex Programmable Logical Device See central processing unit See cyclic redundancy check Canadian Standards Association consecutive severely errored second carrier sense multiple access Common Spanning Tree An alarm not handled or not acknowledged after being handled. Performance data stored currently in a register. An NE provides two types of registers, namely, 15-minute register and 24-hour register, to store performance parameters of a performance monitoring entity. The two types of registers stores performance data only in the specified monitoring period.
Issue 02 (2011-10-31)
1016
A Glossary
customer edge CWDM cyclic redundancy check
A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the Service Provider (SP) network. A CE can be a router, switch, or host. See coarse wavelength division multiplexing A procedure used in checking for errors in data transmission. CRC error checking uses a complex calculation to generate a number based on the data transmitted. The sending device performs the calculation before transmission and includes it in the packet that it sends to the receiving device. The receiving device repeats the same calculation after transmission. If both devices obtain the same result, it is assumed that the transmission was error free. The procedure is known as a redundancy check because each transmission includes not only data but extra (redundant) error-checking values.
D
DAPI Data backup data communication network data communications channel destination access point identifiers A method that is used to copy key data to the standby storage area, to prevent data loss in the case of the damage or failure in the original storage area. A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF). The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to transmit information on operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-M channel. distribute board protect system See data communications channel See dispersion compensation fiber See dispersion compensation module A frame which is used to hold the DCM (Dispersion Compensation Module). See data communication network See digital distribution frame See digital data network A device that separates signals that have been combined by a multiplexer for transmission over a communications channel as a single signal. Technology that utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, employs multiple wavelengths with specific frequency spacing as carriers, and allows multiple channels to transmit simultaneously in the same fiber. A collection of multiple managed devices. By dividing managed devices into different device sets, users can manage the devices by using the U2000 in an easier way. If an operation authority over one device set is assigned to a user (user group), the authority over all the devices in the device set is assigned to the user (user group), thus making it unnecessary to set the operation authority over all the devices in a device set separately. It is recommended to configure device set by geographical region, network level, device type, or another criterion. See Dynamic Host Configuration Protocol
DBPS DCC DCF DCM DCM frame DCN DDF DDN demultiplexer dense wavelength division multiplexing device set
DHCP
Issue 02 (2011-10-31)
A Glossary
diamond-shaped nut digital data network
A type of nut that is used to fasten the wiring frame to the cabinet. A high-quality data transport tunnel that combines the digital channel (such as fiber channel, digital microwave channel, or satellite channel) and the cross multiplex technology. A type of equipment used between the transmission equipment and the exchange with transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection, cable patching, and test of loops that transmitting digital signals. A network device, usually situated in the main office of a telephone company that receives signals from multiple customer Digital Subscriber Line (DSL) connections and puts the signals on a high-speed backbone line using multiplexing techniques. A kind of fiber which uses negative dispersion to compensate for the positive dispersion of transmitting fiber to maintain the original shape of the signal pulse. A module, which contains dispersion compensation fibers to compensate for the dispersion of transmitting fiber. An Internet gateway protocol mainly based on the RIP. The protocol implements a typical dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing datagrams with its neighbors. The distributed link aggregation group (DLAG) is a board-level port protection technology used to detect unidirectional fiber cuts and to negotiate with the opposite end. In the case of a link down failure on a port or a hardware failure on a board, the services can automatically be switched to the slave board, thus realizing 1+1 protection for the inter-board ports. See distributed link aggregation group See demultiplexer Dual Node Interconnection A logical subscriber group based on which the subscriber rights are controlled. differential quadrature phase shift keying dynamic random database differential phase return to zero Differentiated Services Code Point dispersion slope compensation rate See digital subscriber line access multiplexer Digital Signal Processing Data Terminal Equipment See dual tone multiple frequency data terminal ready In telephone systems, multifrequency signaling in which standard set combinations of two specific voice band frequencies, one from a group of four low frequencies and the other from a group of four higher frequencies, are used. A protection operation method which takes switching action at both ends of the protected entity (e.g. "connection", "path"), even in the case of a unidirectional failure.
digital distribution frame digital subscriber line access multiplexer dispersion compensation fiber dispersion compensation module Distance Vector Multicast Routing Protocol distributed link aggregation group
DLAG DMUX; DEMUX DNI domain DQPSK DRDB DRZ DSCP DSCR DSLAM DSP DTE DTMF DTR dual tone multiple frequency dual-ended switching
Issue 02 (2011-10-31)
1018
A Glossary
DVB DVMRP DWDM
Digital Video Broadcasting See Distance Vector Multicast Routing Protocol See dense wavelength division multiplexing
Dynamic Host Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol. Configuration Protocol A DHCP server provides configuration parameters specific to the DHCP client host requesting, generally, information required by the host to participate on the Internet network. DHCP also provides a mechanism for allocation of IP addresses to hosts.
E
E2E EAPE EBS ECC EDFA eDQPSK EFM ejector lever electric supervisory channel electromagnetic compatibility End to End enhanced automatic power pre-equilibrium See excess burst size See embedded control channel See erbium doped fiber amplifier enhanced differential quadrature phase shift keying See Ethernet in the first mile A lever for removing circuit boards from an electronic chassis. A technology realizes the communication among all the nodes and transmits the monitoring data in the optical transmission network. The monitoring data of ESC is introduced into DCC service overhead and is transmitted with service signals. Electromagnetic compatibility is the condition which prevails when telecommunications equipment is performing its individually designed function in a common electromagnetic environment without causing or suffering unacceptable degradation due to unintentional electromagnetic interference to or from other equipment in the same environment. Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment. The sudden and momentary electric current that flows between two objects at different electrical potentials caused by direct contact or induced by an electrostatic field. An element management system (EMS) manages one or more of a specific type of network elements (NEs). An EMS allows the user to manage all the features of each NE individually, but not the communication between NEs - this is done by the network management system (NMS). A logical channel that uses a data communications channel (DCC) as its physical layer, to enable transmission of operation, administration, and maintenance (OAM) information between NEs. See electromagnetic compatibility See electromagnetic interference See element management system A path protocol which connects the host with various control units in a storage system. It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s. See Ethernet private line
electromagnetic interference electrostatic discharge element management system
embedded control channel EMC EMI EMS enterprise system connection EPL
Issue 02 (2011-10-31)
A Glossary
EPLAN erbium doped fiber amplifier
See Ethernet private LAN service An optical device that amplifies the optical signals. The device uses a short length of optical fiber doped with the rare-earth element Erbium and the energy level jump of Erbium ions activated by pump sources. When the amplifier passes the external light source pump, it amplifies the optical signals in a specific wavelength range. See electric supervisory channel See enterprise system connection See electrostatic discharge Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or cabinet to the insertion of ESD wrist strap. enhanced small form-factor pluggable A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/ s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining.. Last mile access from the broadband device to the user community. The EFM takes the advantages of the SHDSL.b is technology and the Ethernet technology. The EFM provides both the traditional voice service and internet access service of high speed. In addition, it meets the users' requirements on high definition television system (HDTV) and Video On Demand (VOD). An Ethernet service type, which carries Ethernet characteristic information over a dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks. A type of Ethernet service that is provided with dedicated bandwidth and point-to-point connections on an SDH, PDH, ATM, or MPLS server layer network. An Ethernet service type, which carries Ethernet characteristic information over a shared bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks. An Ethernet service type, which carries Ethernet characteristic information over shared bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server layer networks. European Telecommunication Standards European Telecommunications Standards Institute A cabinet which is 600mm in width and 300mm in depth, compliant with the standards of the ETSI. The European Committee for Electrotechnical Standardization was established in 1976 in Brussels. It is the result of the incorporation of two former organizations. It aims to reduce internal frontiers and trade barriers for electrotechnical products, systems and services. electrical variable optical attenuator See Ethernet virtual private line See Ethernet virtual private LAN service
ESC ESCON ESD ESD jack eSFP Ethernet
Ethernet in the first mile
Ethernet private LAN service Ethernet private line Ethernet virtual private LAN service Ethernet virtual private line ETS ETSI ETSI 300mm cabinet European Committee for Electrotechnical Standardization EVOA EVPL EVPLAN
Issue 02 (2011-10-31)
1020
A Glossary
excess burst size
A parameter related to traffic. In the single rate three color marker (srTCM) mode, the traffic control is achieved by the token buckets C and E. Excess burst size is a parameter used to define the capacity of token bucket E, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded. The number of the subnet that an NE belongs to, for identifying different network segments in a WAN. The extended ID and ID form the physical ID of the NE. The cables and optical fibers which are used for connecting electrical interfaces and optical interfaces of one cabinet to interfaces of other cabinets or peripherals. An oscilloscope display of synchronized pseudo-random digital data (signal amplitude versus time), showing the superposition of accumulated output waveforms.
Extended ID External cable eye pattern
F
F1 byte The user path byte, which is reserved for the user, but is typically special for network providers. The F1 byte is mainly used to provide the temporary data or voice path for special maintenance objectives. It belongs to the regenerator section overhead byte. Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables), 100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical fibers). A failure to implement the function while the specified operations are performed. A fault does not involve the failure caused by preventive maintenance, insufficiency of external resources and intentional settings. fiber Bragg grating See fiber channel flash database See fiber distributed data interface See fast Ethernet See forward error correction A high-speed transport technology used to build storage area networks (SANs). Fiber channel can be on the networks carrying ATM and IP traffic. It is primarily used for transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair copper wires and coaxial cables. Fiber channel provides both connection-oriented and connectionless services. A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for transmission rates of 100 megabits (100 million bits) per second on networks based on the token ring network.
fast Ethernet
fault
FBG FC FDB FDDI FE FEC fiber channel
fiber distributed data interface
fiber management tray A device used to coil up extra optical fibers.
Issue 02 (2011-10-31)
1021
A Glossary
fiber patch cord fiber spool Fiber trough fiber/cable
A kind of fiber used for connections between the subrack and the ODF, and for connections between subracks or inside a subrack. A device used in coiling up an extra length of optical fibers. The trough that is used for routing fibers. Fiber & Cable is the general name of optical fiber and cable. It refers to the physical entities that connect the transmission equipment, carry transmission objects (user information and network management information) and perform transmission function in the transmission network. The optical fiber transmits optical signal, while the cable transmits electrical signal. The fiber/cable between NEs represents the optical fiber connection or cable connection between NEs. The fiber/cable between SDH NEs represents the connection relation between NEs. At this time, the fiber/cable is of optical fiber type. A type of semi-customized circuit used in the Application Specific Integrated Circuit (ASIC) field. It is developed on the basis of the programmable components, such as the PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also overcomes the disadvantage of the original programmable components in terms of the limited number of gate arrays. See First in First out A member of the TCP/IP suite of protocols, used to copy files between two computers on the Internet. Both computers must support their respective FTP roles: one must be an FTP client and the other an FTP server. A stack management mechanism. The first saved data is first read and invoked. An aggregation of packets that have the same characteristics. On the network management system or NE software, flow is a group of classification rules. On boards, it is a group of packets that have the same quality of service (QoS) operation. At present, two flows are supported: port flow and port+VLAN flow. Port flow is based on port ID and port+VLAN flow is based on port ID and VLAN ID. The two flows cannot coexist in the same port. See fiber management tray fixed optical add/drop multiplexer fixed optical attenuator For normal traffic signals, switches normal traffic signal to the protection section, unless an equal or higher priority switch command is in effect or SF condition exists on the protection section, by issuing a forced switch request for that traffic signal. A bit error correction technology that adds the correction information to the payload at the transmit end. Based on the correction information, the bit errors generated during transmission are corrected at the receive end. Four-Wave Mixing (FWM), also called four-photon mixing, occurs when the interaction of two or three optical waves at different wavelengths generates new optical waves, called mixing products or sidebands, at other wavelengths. See field programmable gate array
field programmable gate array
FIFO File Transfer Protocol
First in First out Flow
FMT FOADM FOAs Forced switch
forward error correction four-wave mixing
FPGA
Issue 02 (2011-10-31)
1022
A Glossary
frame
A frame, starting with a header, is a string of bytes with a specified length. Frame length is represented by the sampling circle or the total number of bytes sampled during a circle. A header comprises one or a number of bytes with pre-specified values. In other words, a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties.
frame alignment signal A distinctive signal inserted in every frame or once in every n frames, always occupying the same relative position within the frame, and used to establish and maintain frame alignment. FTP full-duplex See File Transfer Protocol A full-duplex, or sometimes double-duplex system, allows communication in both directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line telephone networks are full-duplex, since they allow both callers to speak and be heard at the same time. A good analogy for a full-duplex system would be a two-lane road with one lane for each direction.
G
gain The ratio between the optical power from the input optical interface of the optical amplifier and the optical power from the output optical interface of the jumper fiber, which expressed in dB. Gain Flattening Filter (GFFs), also known as gain equalizing filters, are used to flatten or smooth out unequal signal intensities over a specified wavelength range. This unequal signal intensity usually occurs after an amplification stage (for example, EDFA and/or Raman). Typically, GFFs are used in conjunction with gain amplifiers to ensure that the amplified channels all have the same gain. A static spectral device that flattens the output spectrum of an erbium-doped fiber amplifier. When an NE accesses a remote network management system or NE, a router can be used to enable the TCP/IP communication. In this case, the IP address of the router is the gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP networks. An NE may have multiple IP addresses, for example, one IP address of the network and one IP address of the Ethernet port. A network element that is used for communication between the NE application layer and the NM application layer See gigabit general communication channel See GMPLS control plan See gigabit Ethernet The technology can optimize GE service transport over WDM for Metro network. It owns the capability of GE service convergence and grooming and benefits to use the network resource more effectively. A framing and encapsulated method which can be applied to any data type. It has been standardized by ITU-T SG15. See gain flattening filter See generic framing procedure
gain flattening filter
Gateway IP
gateway network element Gb GCC GCP GE GE ADM
generic framing procedure GFF GFP

Issue 02 (2011-10-31)
A Glossary
gigabit
In data communications, a gigabit is one billion bits, or 1,000,000,000 (that is, 10^9) bits. It's commonly used for measuring the amount of data that is transferred in a second between two telecommunication points. GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support coaxial cables or other cables. It also supports the channels in the bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge (switch) or a router as the center, it gives full play to the performance and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that are private, causing the length of the links to be sufficient for backbone applications in a building and campus. A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users. generalized multiprotocol label switching The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei. The OptiX GCP applies to the OptiX OSN product series. By using this software, the traditional network can evolve into the ASON network. The OptiX OSN product series support the ASON features. See gateway network element See Global Positioning System
gigabit Ethernet
Global Positioning System GMPLS GMPLS control plan
GNE GPS
graphical user interface A visual computer environment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen. grounding GSSP GUI The connection of sections of an electrical circuit to a common conductor, called the ground, which serves as the reference for the other voltages in the circuit. General Snooping and Selection Protocol See graphical user interface
H
Hardware loopback HCS HDB HDLC hierarchical cell structure high level data link control History alarm History Performance Data A connection mode in which a fiber jumper is used to connect the input optical interface to the output optical interface of a board to achieve signal loopback. See hierarchical cell structure high density bipolar code See high level data link control This is a term typically used to describe the priority of cells within a mixed environment. That is when Macro, Micro, and Pico cells may be viewed as candidates for cell reselection the priority described by the HCS will be used in the associated calculations. The HDLC protocol is a general purpose protocol which operates at the data link layer of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by adding a trailer and a header. The confirmed alarms that have been saved in the memory and other external memories. The performance data that is stored in the history register or that is automatically reported and stored in the NMS.
Issue 02 (2011-10-31)
1024
A Glossary
I
IAE IC ICC ICMP ID identity Idle resource optical NE incoming alignment error See integrated circuit ITU carrier code See Internet Control Message Protocol See identity The collective aspect of the set of characteristics by which a thing is definitively recognizable or known. When the U2000 is started successfully, an NE icon called "Idle ONE" will be displayed on the topological view. In this NE, the subracks and boards that are not divided to other optical NEs (such as OTM, OADM and other NEs) are retained. In this NE, idle DWDM subracks and boards are reserved, which can be distributed to other ONEs. Double-click the NE icon to view all the currently idle DWDM subracks or boards in the network. See Internet Explorer See International Electrotechnical Commission See Institute of Electrical and Electronics Engineers See Internet Engineering Task Force See Internet Group Management Protocol The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when modulating the signal at an equipment input port, results in no more than two errored seconds cumulative, where these errored seconds are integrated over successive 30 second measurement intervals. A society of engineering and electronics professionals based in the United States but boasting membership from numerous other countries. The IEEE focuses on electrical, electronics, computer engineering, and science-related matters. A combination of inseparable associated circuit elements that are formed in place and interconnected on or within a single base material to perform a microcircuit function. A network defined in CCITT, providing comprehensive transmission service for the voice, video, and data. The ISDN enables the voice, video, and data transmission on a small number of data channels simultaneously, thus implementing a comprehensive transmission service. A technology that the system reduces the optical power of all the amplifiers in an adjacent regeneration section in the upstream to a safety level if the system detects the loss of optical signals on the link. The loss of optical signals may due to the fiber is broken, the performance of equipments trend to be inferior or the connector is not plugged well. Thus, the maintenance engineers are not hurt by the laser being sent out from the slice of broken fiber. The cables and optical fibers which are used for interconnecting electrical interfaces and optical interfaces within the cabinet. A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.
IE IEC IEEE IETF IGMP Input jitter tolerance
Institute of Electrical and Electronics Engineers integrated circuit integrated services digital network
intelligent power adjustment
Internal cable internal spanning tree
Issue 02 (2011-10-31)
1025
A Glossary
International Electrotechnical Commission International Organization for Standardization International Telecommunication Union International Telecommunication UnionTelecommunication Standardization Sector Internet Control Message Protocol
The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards. An international association that works to establish global standards for communications and information exchange. Primary among its accomplishments is the widely accepted ISO/OSI reference model, which defines standards for the interaction of computers connected by communications networks. A United Nations agency, one of the most important and influential recommendation bodies, responsible for recommending standards for telecommunication (ITU-T) and radio networks (ITU-R). An international body that develops worldwide standards for telecommunications technologies. These standards are grouped together in series which are prefixed with a letter indicating the general subject and a number specifying the particular standard. For example, X.25 comes from the "X" series which deals with data networks and open system communications and number "25" deals with packet switched networks. A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and other information relevant to IP packet processing. For example, it can let the IP software on one machine inform another machine about an unreachable destination. See also communications protocol, IP, ISO/OSI reference model, packet (definition 1). A worldwide organization of individuals interested in networking and the Internet. Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with studying technical problems facing the Internet and proposing solutions to the Internet Architecture Board (IAB). The work of the IETF is carried out by various working groups that concentrate on specific topics, such as routing and security. The IETF is the publisher of the specifications that led to the TCP/IP protocol standard. Microsoft's Web browsing software. Introduced in October 1995, the latest versions of Internet Explorer include many features that allow you to customize your experience on the Web. Internet Explorer is also available for the Macintosh and UNIX platforms. The protocol for managing the membership of Internet Protocol multicast groups among the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships. The TCP/IP standard protocol that defines the IP packet as the unit of information sent across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part. The entire protocol suite is often referred to as TCP/IP because TCP and IP are the two fundamental protocols. IP is standardized in RFC 791. See Internet Protocol A 32-bit (4-byte) binary number that uniquely identifies a host (computer) connected to the Internet for communication with other hosts in the Internet by transferring packets. An IP address is expressed in dotted decimal notation, consisting of the decimal values of its 4 bytes, separated with periods; for example, 127.0.0.1. The first three bytes of the IP address identify the network to which the host is connected, and the last byte identify the host itself. The IP Over DCC follows TCP/IP telecommunications standards and controls the remote NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead DCC byte (the default is D1-D3) for communication. See intelligent power adjustment
Internet Engineering Task Force
Internet Explorer
Internet Group Management Protocol Internet Protocol
IP IP address
IP over DCC
IPA
Issue 02 (2011-10-31)
A Glossary
IPG ISDN ISO IST ITU ITU-T
inter-packet gap See integrated services digital network See International Organization for Standardization See internal spanning tree See International Telecommunication Union See International Telecommunication Union-Telecommunication Standardization Sector
J
Jitter Jitter transfer Short waveform variations caused by vibration, voltage fluctuations, and control system instability. The physical relationship between jitter applied at the input port and the jitter appearing at the output port.
L
label switched path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label switching mechanisms. A label-switched path can be chosen dynamically, based on normal routing mechanisms, or through configuration. See Link Aggregation Control Protocol See link aggregation group See local area network link access procedure on the D channel link access protocol-SDH A component that generates directional optical waves of narrow wavelengths. The laser light has better coherence than ordinary light. The fiber system takes the semi-conductor laser as the light source. A concept used to allow the transport network functionality to be described hierarchically as successive levels; each layer being solely concerned with the generation and transfer of its characteristic information. See loopback See link capacity adjustment scheme See liquid crystal display local communication network local craft terminal See light emitting diode long hop
LACP LAG LAN LAPD LAPS Laser
layer
LB LCAS LCD LCN LCT LED LHP
Issue 02 (2011-10-31)
1027
A Glossary
light emitting diode
A display and lighting technology used in almost every electrical and electronic product on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and perimeter lighting. LEDs are also used as the light source in multimode fibers, optical mice and laser-class printers. A method of bundling a group of physical interfaces together as a logical interface to increase bandwidth and reliability. For related protocols and standards, refer to IEEE 802.3ad.
Link Aggregation Control Protocol
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link aggregation group so that a MAC client can treat the link aggregation group as if it were a single link. link capacity adjustment scheme LCAS in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitlessly increase or decrease the capacity of a link to meet the bandwidth needs of the application. It also provides a means of removing member links that have experienced failure. The LCAS assumes that in cases of capacity initiation, increases or decreases, the construction or destruction of the end-to-end path is the responsibility of the Network and Element Management Systems. In the Point-to-Point Protocol (PPP), the Link Control Protocol (LCP) establishes, configures, and tests data-link Internet connections. The link in LSA is any type of connection between OSPF routers, while the state is the condition of the link. The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP is called Linktrace Message(LTM). LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2. For 802.1ag MAC Trace, the destination MEP replies with a response message to the source MEP after the destination MEP receives the LTM, and the response message is called Linktrace Reply (LTR). LTR also includes the TTL that equals the result of the TTL of LTM minus 1. A type of display that uses a liquid compound having a polar molecular structure, sandwiched between two transparent electrodes. See logical link control link management protocol loss of clock A network formed by the computers and workstations within the coverage of a few square kilometers or within a single building. It features high speed and low error rate. Ethernet, FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/ s (that is, 1 Gbit/s). When the switching condition is satisfied, this function disables the service from being switched from the working channel to the protection channel. When the service has been switched, the function enables the service to be restored from the protection channel to the working channel. According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper sublayer of the OSI data link layer. The LLC is the same for the various physical media (such as Ethernet, token ring, WLAN). A logical port is a logical number assigned to every application.
Link Control Protocol link state advertisement linktrace message
linktrace reply
liquid crystal display LLC LMP LOC local area network
Locked switching
logical link control
logical port
Issue 02 (2011-10-31)
1028
A Glossary
loopback LOP LOS loss of pointer
A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors. See loss of pointer See Loss Of Signal Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost the pointer to the start of cell in the payload. This is used to monitor the performance of the PHY layer. Loss of signal (LOS) indicates that there are no transitions occurring in the received signal. The subrack close to the bottom of the cabinet when a cabinet contains several subracks. See logical port link-state pass through See link state advertisement See label switched path linktrace See linktrace message See linktrace reply
Loss Of Signal Lower subrack LP LPT LSA LSP LT LTM LTR
M
MA MAC MADM main distribution frame main path interface at the transmitter main topology Maintenance Associations See media access control multiple add/drop multiplexer A device at a central office, on which all local loops are terminated. A reference point on the optical fiber just after the OM/OA output optical connector. A interface that displays the connection relation of NEs on the NMS (screen display). The default client interface of the NMS, a basic component of the human-machine interactive interface. The topology clearly shows the structure of the network, the alarms of different NEs, subnets in the network, the communication status as well as the basic network operation status. All topology management functions are accessed here. The network or the part of the network for which connectivity is managed by CFM. The devices in an MD are managed by a single ISP. Maintenance Point (MP) is one of either a MEP or a MIP. See metropolitan area network The management view of a resource within the telecommunication environment that may be managed via the agent. Examples of SDH managed objects are: equipment, receive port, transmit port, power supply, plug-in card, virtual container, multiplex section, and regenerator section.
maintenance domain maintenance point MAN managed object
Issue 02 (2011-10-31)
1029
A Glossary
Management information management information base manual switch
The information that is used for network management in a transport network. A type of database used for managing the devices in a communications network. It comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network. Switches normal traffic signal to the protection section, unless a failure condition exists on other sections (including the protection section) or an equal or higher priority switch command is in effect, by issuing a manual switch request for that normal traffic signal. A procedure by which tributaries are adapted into virtual containers at the boundary of an SDH network. A quadrate cardboard with four holes. It is used to mark the positions of the installation holes for the cabinet. See maintenance domain Memory Database See main distribution frame message dispatch process message distribution service software maintenance entities The average power of a pseudo-random data sequence coupled into the fiber by the transmitter. The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system. A protocol at the media access control sublayer. The protocol is at the lower part of the data link layer in the OSI model and is mainly responsible for controlling and connecting the physical media at the physical layer. When transmitting data, the MAC protocol checks whether to be able to transmit data. If the data can be transmitted, certain control information is added to the data, and then the data and the control information are transmitted in a specified format to the physical layer. When receiving data, the MAC protocol checks whether the information is correct and whether the data is transmitted correctly. If the information is correct and the data is transmitted correctly, the control information is removed from the data and then the data is transmitted to the LLC layer. maintenance end point A metropolitan area network (MAN) is a network that interconnects users with computer resources in a geographic area or region larger than that covered by even a large local area network (LAN) but smaller than the area covered by a wide area network (WAN). The term is applied to the interconnection of networks in a city into a single larger network (which may then also offer efficient connection to a wide area network). It is also used to mean the interconnection of several local area networks by bridging them with backbone lines. The latter usage is also sometimes referred to as a campus network. See multiframe alignment signal See management information base maintenance intermediate point See multicast listener discovery
Mapping marking-off template MD MDB MDF MDP MDS ME mean launched power Mean Time Between Failures media access control
MEP metropolitan area network
MFAS MIB MIP MLD
Issue 02 (2011-10-31)
1030
A Glossary
MLM laser MO mother board mounting ear MP MPI MPI-R MPI-S MPLS MS MSA MSI MSOH MSP MSPP MST MSTI MSTP MTA MTBF MTU multi-longitudinal mode laser multicast listener discovery
See multi-longitudinal mode laser See managed object A printed board assembly that is used for interconnecting arrays of plug-in electronic modules. A piece of angle plate with holes in it on a rack. It is used to fix network elements or components. See maintenance point main path interface main path interface at the receiver See main path interface at the transmitter See Multiprotocol Label Switching Multiplex Section Multiplex Section Adaptation multi-frame structure identifier See multiplex section overhead See multiplex section protection multi-service provisioning platform See multiplex section termination See multiple spanning tree instance See Multiple Spanning Tree Protocol Mail Transfer Agent See Mean Time Between Failures Maximum Transmission Unit An injection laser diode which has a number of longitudinal modes. The MLD is used by the IPv6 router to discover the multicast listeners on their directly connected network segments, and set up and maintain member relationships. On IPv6 networks, after MLD is configured on the receiver hosts and the multicast router to which the hosts are directly connected, the hosts can dynamically join related groups and the multicast router can manage members on the local network. A distinctive signal inserted in every multiframe or once in every n multiframes, always occupying the same relative position within the multiframe, and used to establish and maintain multiframe alignment.
multiframe alignment signal
multiple spanning tree Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP instance within an MST Region, to provide a simply and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to multiple MSTIs.
Issue 02 (2011-10-31)
1031
A Glossary
Multiple Spanning Tree Protocol
Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In this case, the proliferation and endless cycling of packets is avoided in the loop network. The protocol that introduces the mapping between VLANs and multiple spanning trees. This solves the problem that data cannot be normally forwarded in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs. The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH definition. A function, which is performed to provide capability for switching a signal between and including two multiplex section termination (MST) functions, from a "working" to a "protection" channel. The function performed to generate the MSOH in the process of forming an SDH frame signal and terminates the MSOH in the reverse direction. Equipment which combines a number of tributary channels onto a fewer number of aggregate bearer channels, the relationship between the tributary and aggregate channels being fixed. A procedure by which multiple lower order path layer signals are adapted into a higher order path or the multiple higher order path layer signals are adapted into a multiplex section. A technology that uses short tags of fixed length to encapsulate packets in different link layers, and provides connection-oriented switching for the network layer on the basis of IP routing and control protocols. It improves the cost performance and expandability of networks, and is beneficial to routing. See multiplexer mechanical variable optical attenuator
multiplex section overhead multiplex section protection multiplex section termination multiplexer
Multiplexing
Multiprotocol Label Switching
MUX MVOA
N
NA NCP NE NE database No Acknowledgment See Network Control Protocol See network element There are three types of database on NE SCC board as following: (1) DRDB: a dynamic database in a dynamic RAM, powered by battery; (2) SDB: a static database in a power-down RAM; (3) FDB0, FDB0: permanently saved databases in a Flash ROM. In efficient operation, the NE configuration data is saved in DRDB and SDB at the same time. Backing up an NE database means backing up the NE configuration data from SDB to FDB0 and FDB1. When an NE is restarted after power-down, the NE database is restored in the following procedures: As the SDB data is lost due to power-down, the main control restores the data first from DRDB. If the data in DRDB is also lost due to the exhaustion of the battery, the data is restored from FDB0 or FDB1.
Issue 02 (2011-10-31)
1032
A Glossary
NE Explorer
The main operation interface, of the NMS, which is used to manage the telecommunication equipment. In the NE Explorer, the user can query, manage and maintain the NE, boards, and ports on a per-NE basis. An ID that indicates a managed device in the network. In the network, each NE has a unique NE ID. A graphical user interface, of the network management system, which displays subracks, boards, and ports on an NE. In the NE Panel, the user can complete most of the configuration, management and maintenance functions for an NE. The NE configuration data that is stored on the SCC board of the equipment. The NEside data can be uploaded to the network management system(NMS) and thus is stored on the NMS side. Network Equipment Building System See network element function This is the program that switches the virtual circuit connections into place, implements path control, and operates the Synchronous Data Link Control (SDLC) link. A network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control and communication(SCC) board which manages and monitors the entire network element. The NE software runs on the SCC board. A function block which represents the telecommunication functions and communicates with the TMN OSF function block for the purpose of being monitored and/or controlled. The process of controlling a network so as to maximize its efficiency and productivity. ISO's model divides network management into five categories: fault management, accounting management, configuration management, security management and performance management.
NE ID NE Panel
NE-side data
NEBS NEF Network Control Protocol network element
network element function network management
Network Management A system in charge of the operation, administration, and maintenance of a network. System network node interface The interface at a network node which is used to interconnect with another network node. network segment A part of an Ethernet or other network, on which all message traffic is common to all nodes, that is, it is broadcast from one node on the segment and received by all others.
network service access A network address defined by ISO, through which entities on the network layer can point access OSI network services. Network Time Protocol The Network Time Protocol (NTP) defines the time synchronization mechanism. It synchronizes the time between the distributed time server and the client. NM NMS NNI NOC Noise figure NSAP NTP See network management See Network Management System See network node interface network operation center An index that represents the degrade extent of optical signals after the signals passing a system. See network service access point See Network Time Protocol
Issue 02 (2011-10-31)
1033
A Glossary
O
OA OADM OADM frame OAM OC OCI OCP OD ODB ODF ODUk OEQ OFC OLA OLP OM OMS ONE Online Help OOF OPA See optical amplifier See optical add/drop multiplexer A frame which is used to hold the OADM boards. See operation, administration and maintenance See optical coupler open connection indication See optical channel protection optical demultiplexing optical duobinary See optical distribution frame optical channel data unit-k optical equalizer open fiber control See optical line amplifier See optical line protection optical multiplexing optical multiplexing section See optical network element The capability of many programs and operating systems to display advice or instructions for using their features when so requested by the user. See out of frame optical power adjust
open shortest path first A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A link state database is constructed of the network topology which is identical on all routers in the area. Open Systems Interconnection A framework of ISO standards for communication between different systems made by different vendors, in which the communications process is organized into seven different categories that are placed in a layered sequence based on their relationship to the user. Each layer uses the layer immediately below it and provides a service to the layer above. Layers 7 through 4 deal with end-to-end communication between the message source and destination, and layers 3 through 1 deal with network functions. A group of network support functions that monitor and sustain segment operation, activities that are concerned with, but not limited to, failure detection, notification, location, and repairs that are intended to eliminate faults and keep a segment in an operational state and support activities required to provide the services of a subscriber access network to users/subscribers. operation expenditure optical physical section
operation, administration and maintenance
OpEx; OPEX OPS

Issue 02 (2011-10-31)
A Glossary
optic fiber connector
A device installed at the end of a fiber, optical source or receive unit. It is used to couple the optical wave to the fiber when connected to another device of the same type. A connector can either connect two fiber ends or connect a fiber end and a optical source (or a detector).+ A device that can be used to add the optical signals of various wavelengths to one channel and drop the optical signals of various wavelengths from one channel. Devices or subsystems in which optical signals can be amplified by means of the stimulated emission taking place in a suitable active medium. A passive device that increases the attenuation in a fiber link. It is used to ensure that the optical power of the signals received at the receive end is not extremely high. It is available in two types: fixed attenuator and variable attenuator. A signal transmitted at one wavelength in a fiber-optic system. In an optical transmission link that contains multiple wavelengths, when a certain wavelength goes faulty, the services at the wavelength can be protected if the optical channel protection is configured. A coupler for coupling light in an optical system. Multiple discrete layers of alternating optical materials have respective first and second indexes of refraction. The thickness of each layer is a fraction of the light wavelength. A frame which is used to transfer and spool fibers. A piece of equipment that functions as an OLA to directly amplify the input optical signals and to compensate for the line loss. Currently, the key component of the OLA is the EDFA amplifier. A protection mechanism that adopts dual fed and selective receiving principle and singleended switching mode. In this protection, two pairs of fibers are used. One pair of fibers forms the working route. The working route transmits line signals when the line is normal. The other pair of fibers forms the protection route. The protection route carries line signals when the line is broken or the signal attenuation is extremely large. A transport entity that implements the NE functions (terminal multiplexing, add/drop multiplexing, cross-connection and regeneration) in a DWDM layer network. The types of ONEs include OTM, OADM, OLA, REG and OXC. The locating of an ONE is equivalent to that of a common NE. In a view, an ONE is displayed with an icon, like a common NE and its alarm status can be displayed with colors. Logically, an ONE consists of different subracks. Like a common NE, an ONE cannot be expanded or entered like a sub-network. Similar to a common NE, an ONE provides a list of the subracks that form the NE to display the board layout. The most important index of measuring the performance of a DWDM system. The ratio of signal power and noise power in a transmission link. That is, OSNR = signal power/ noise power. A device that allows the details of a region of an optical spectrum to be resolved. Commonly used to diagnose DWDM systems. A technology that realizes communication among nodes in optical transmission network and transmits the monitoring data in a certain channel (the wavelength of the working channel for it is 1510 nm and that of the corresponding protection one is 1625 nm). A passive component possessing two or more ports which selectively transmits, redirects, or blocks optical power in an optical fiber transmission line.
optical add/drop multiplexer optical amplifier optical attenuator
optical channel optical channel protection optical coupler
optical distribution frame optical line amplifier
optical line protection
optical network element
optical signal-to-noise ratio optical spectrum analyzer optical supervisory channel Optical switch
Issue 02 (2011-10-31)
A Glossary
optical time domain reflectometer optical transmission section optical transponder unit optical transport network optical wavelength shared protection
A device that sends a very short pulse of light down a fiber optic communication system and measures the time history of the pulse reflection to measure the fiber length, the light loss and locate the fiber fault. Optical transmission section allows the network operator to perform monitoring and maintenance tasks between NEs. A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength. A network that uses the optical signal to transmit data In the optical wavelength shared protection (OWSP), the service protection between different stations can be achieved by using the same wavelength, realizing wavelength sharing. This saves the wavelength resources and lowers the cost. The optical wavelength shared protection is mainly applied to the ring network which is configured with distributed services. It is achieved by using the OWSP board. In a ring network where services are distributed at adjacent stations, each station requires one OWSP board. Then, two wavelengths are enough for configuring the shared protection to protect one service among stations. optical channel payload unit optical channel payload unit-k A channel that provides voice communication between operation engineers or maintenance engineers of different stations. An original equipment manufacturer, or OEM is typically a company that uses a component made by a second company in its own product, or sells the product of the second company under its own brand. See optical spectrum analyzer See optical supervisory channel See Open Systems Interconnection optical switch node See optical signal-to-noise ratio See open shortest path first See optical time domain reflectometer optical terminal multiplexer See optical transport network See optical transmission section See optical transponder unit optical channel transport unit-k An NE transmits an OOF downstream when it receives framing errors in a specified number of consecutive frame bit positions. The ranger of optical energy level of output signals. Cables or fibers connect the cabinet with other equipment from the top of the cabinet. See optical wavelength shared protection
OPU OPUk orderwire original equipment manufacturer OSA OSC OSI OSN OSNR OSPF OTDR OTM OTN OTS OTU OTUk out of frame Output optical power overhead cabling OWSP
Issue 02 (2011-10-31)
1036
A Glossary
P
PA packet over SDH/ SONET packet switched network Packing case Paired slots pass-through PBS PCB PCC PCC PCS PDH PDL PDU PE peak burst size pre-amplifier A MAN and WAN technology that provides point-to-point data connections. The POS interface uses SDH/SONET as the physical layer protocol, and supports the transport of packet data (such as IP packets) in MAN and WAN. A telecommunication network which works in packet switching mode. A case which is used for packing the board or subrack. Two slots of which the overheads can be passed through by using the bus on the backplane. The action of transmitting the same information that is being received for any given direction of transmission. See peak burst size See printed circuit board protection communication channel See policy and charging control See physical coding sublayer See plesiochronous digital hierarchy See polarization dependent loss Protocol Data Unit Provider Edge A parameter used to define the capacity of token bucket P, that is, the maximum burst IP packet size when the information is transferred at the peak information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded. Peak Information Rate. A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate. Performance register is the memory space for performance event counts, including 15min current performance register, 24-hour current performance register, 15-min history performance register, 24-hour history performance register, UAT register and CSES register. The object of performance event monitoring is the board functional module, so every board functional module has a performance register. A performance register is used to count the performance events taking place within a period of operation time, so as to evaluate the quality of operation from the angle of statistics. protection ground A circuit that consists essentially of a phase detector which compares the frequency of a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with the incoming or reference frequency. See physical sublayer & physical layer
peak information rate Performance register
PGND phase-locked loop
PHY
Issue 02 (2011-10-31)
1037
A Glossary
physical coding sublayer physical sublayer & physical layer PID PIM-DM PIM-SM PIN PIR plesiochronous digital hierarchy PLL PMD PMI POH point to multipoint
The PCS further helps to define physical layer specifications for 10 gigabit Ethernet after having been broken down into their Physical Media Dependent Sublayer or PMD. Each sublayer places the 10GBASE standards into either LAN or WAN specifications. 1. physical sublayer: One of two sublayers of the FDDI physical layer. 2. physical layer: In ATM, the physical layer provides the transmission of cells over a physical medium that connects two ATM devices. The PHY is comprised of two sublayers: PMD and TC photonics integrated device protocol independent multicast-dense mode See protocol independent multicast sparse mode See Positive Intrinsic Negative See peak information rate A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates. See phase-locked loop polarization mode dispersion payload missing indication path overhead A communications network that provides a path from one location to multiple locations (from one to many).
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. It is located in layer 2 of the IP protocol stack. Point-to-Point Protocol PPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating over Ethernet PPP frames in Ethernet frames. It is used mainly with DSL services. It offers standard PPP features such as authentication, encryption, and compression. Pointer An indicator whose value defines the frame offset of a virtual container with respect to the frame reference of the transport entity on which it is supported.
polarization dependent The maximum, peak-to-peak insertion loss (or gain) variation caused by a component loss when stimulated by all possible polarization states. It is specified in dB units. policy and charging control POS Positive Intrinsic Negative Power box Short for Policy and Charging Control, the PCC is defined in 3GPP R7. The PCC provides the QoS control and service-based charging functions in the wireless bearer network. See packet over SDH/SONET Photodiode. A semiconductor detector with an intrinsic (i) region separating the p- and n-doped regions. It has fast linear response and is used in fiber-optic receivers. A direct current power distribution box at the upper part of a cabinet, which supplies power for the subracks in the cabinet.
power distribution box A power box through which the power enters the cabinet and is re-distributed to various components, at the mean time, the Power Distribution Box protects the electric devices from current overload. PPP PPPoE See Point-to-Point Protocol See Point-to-Point Protocol over Ethernet
Issue 02 (2011-10-31)
1038
A Glossary
PRBS PRC PRI primary rate interface printed circuit board
See pseudo random binary sequence primary reference clock See primary rate interface An interface consisting of 23 channel Bs and a 64 kbit/s channel D that uses the T1 line, or consisting of 30 channel Bs and a channel D that uses the E1 line. A board used to mechanically support and electrically connect electronic components using conductive pathways, tracks, or traces, etched from copper sheets laminated onto a non-conductive substrate. A cable which connects the equipment and the protection grounding bar. Usually, one half of the cable is yellow; while the other half is green. A specific path that is part of a protection group and is labeled protection. In case the service route provides multiple service protections, different protection policies can be selected as required. Protection policy refers to the protection mode given the priority in use for the trail: protection, no protection, and extra traffic. Of the above, the protection preference is divided into trail protection and subnet connection protection. A specific service that is part of a protection group and is labeled protection. It is applicable to large-scale multicast networks with scattered members.
protection ground cable Protection path Protection policy
Protection service protocol independent multicast sparse mode
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the sequence values of any of the other elements, similar to real random sequences. PSI PSN PSTN PT PTMP PTN PTP public switched telephone network payload structure identifier See packet switched network See public switched telephone network payload type See point to multipoint packet transport network Point-To-Point A telecommunications network established to perform telephone services for the public subscribers. Sometimes called POTS.
Q
QA QoS quality of service Q adaptation See quality of service A commonly-used performance indicator of a telecommunication system or channel. Depending on the specific system and service, it may relate to jitter, delay, packet loss ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the transmission system and the effectiveness of the services, as well as the capability of a service provider to meet the demands of users.
Issue 02 (2011-10-31)
1039
A Glossary
R
radio network controller RAI RAM An equipment in the RNS which is in charge of controlling the use and the integrity of the radio resources. remote alarm indication See random access memory
random access memory Semiconductor-based memory that can be read and written by the central processing unit (CPU) or other hardware devices. The storage locations can be accessed in any order. Note that the various types of ROM memory are capable of random access but cannot be written to. The term RAM, however, is generally understood to refer to volatile memory that can be written to as well as read. Rapid Spanning Tree Protocol Receiver Sensitivity An evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change. The RSTP protocol is backward compatible with the STP protocol. Receiver sensitivity is defined as the minimum acceptable value of average received power at point R to achieve a 10-12 (The FEC is open).
reconfiguration optical The WDM equipment supports the ROADM. It flexibly and dynamically adjusts add/ add/drop multiplexer drop wavelengths of sites on the network by adjusting the pass-through or block status of any wavelength without affecting the service transmission in the main optical channel. This implements wavelength allocation among sites on the network. After the ROADM is used, the existing services are not affected during upgrade. The wavelength can be modified quickly and efficiently during network maintenance, which reduces maintenance cost. In addition, the ROADM supports the equalization for optical power, which equalizes the optical power at the channel level. Reed Solomon Code reference clock Reflectance REG Regeneration REI Resource Reservation Protocol A type of forward error correcting codes invented in 1960 by Irving Reed and Gustave Solomon, which has become commonplace in modern digital communications. A kind of stable and high-precision autonous clock providing frequencies for other clocks for reference. The ratio of the reflected optical power to the incident optical power. A piece of equipment or device that regenerates electrical signals. 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. Remote Error Indication The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data. RSVP is a network control protocol like Internet Control Message Protocol (ICMP). Radio Frequency Requirement for Comments remote failure indication A type of network topology in which each node connects to exactly two other nodes, forming a circular pathway for signals. See Routing Information Protocol
RF RFC RFI ring network RIP
Issue 02 (2011-10-31)
1040
A Glossary
RMON RNC ROADM route Routing Information Protocol
remote network monitoring See radio network controller See reconfiguration optical add/drop multiplexer A route is the path that network traffic takes from its source to its destination. In a TCP/ IP network, each IP packet is routed independently. Routes can change dynamically. A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route based on the smallest hop count between source and destination. RIP is a distance vector protocol that routinely broadcasts routing information to its neighboring routers and is known to waste bandwidth. See Reed Solomon Code In the asynchronous transfer mode and there is no hand-shaking signal. It can communicate with RS232 and RS422 of other stations in point-to-point mode and the transmission is transparent. Its highest speed is 19.2kbit/s. See Rapid Spanning Tree Protocol See Resource Reservation Protocol return to zero code
RS Code RS232
RSTP RSVP RZ
S
S1 byte In an SDH network, each network element traces step by step to the same clock reference source through a specific clock synchronization path, thus realizing the synchronization of the whole network. If a clock reference source traced by the NE is missing, this NE will trace another clock reference source of a lower level. To implement protection switching of clocks in the whole network, the NE must learn about clock quality information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to transmit network synchronization status information. It uses the lower four bits of the multiplex section overhead S1 byte to indicate 16 types of synchronization quality grades. Auto protection switching of clocks in a synchronous network can be implemented using S1 byte and a proper switching protocol. The IPA safe switch is set in consideration of the long-span networking requirement, which cannot allow too low output optical power. If the safe control switch is turned off, IPA restarting optical power is the specified output power of the OAU. Otherwise, the IPA restarting optical power is restricted to less than 10 dBm. See storage area network service access point source access point identifiers stimulated Brillouin scattering See square connector See signal degrade SD stands for signal degrade. The SD trigger flag determines whether to perform a switching when SD occurs. The SD trigger flag can be set by using the network management system. See synchronous digital hierarchy
Safe control switch
SAN SAP SAPI SBS SC SD SD trigger flag
SDH
Issue 02 (2011-10-31)
A Glossary
SDI SDP Search domain
See Serial Digital Interface serious disturbance period Search field refers to the range of IP addresses being searched. In the TCP/IP, the IP addresses include: Category A address (1.0.0.0---126.255.255.255). For example, 10.*.*.*, whose search field is 10.255.255.255, all 10.*.*.* to be searched. Category B address (128.0.0.0---191. 255. 255. 255). For example, 129.9.*.*, whose search field is 129.9.255.255, all 129.9.*.* to be searched. Category C address (192.0.0.0---223. 255. 255. 255). For example, 192.224.9.*, whose search field is 192.224.9.255, all 192.224.9.* to be searched. Category D address (224.0.0.0---230.255.255.255), which is reserved. Category E address (240.0.0.0---247.255.255.255), which is reserved. Netid 127.*.*.*, in which .*.*.* can be any number. This net-ID is a local address. A network protocol designed to provide secure file transfer over SSH. Self-healing is the establishment of a replacement connection by network without the NMC function. When a connection failure occurs, the replacement connection is found by the network elements and rerouted depending on network resources available at that time. Serial Line Interface Protocol, defines the framing mode over the serial line to implement transmission of messages over the serial line and provide the remote host interconnection function with a known IP address.
Secure File Transfer Protocol Self-healing
Serial Digital Interface An interface for transmitting digital signals. Serial Line Interface Protocol
service level agreement A service contract between a customer and a service provider that specifies the forwarding service a customer should receive. A customer may be a user organization (source domain) or another differentiated services domain (upstream domain). A SLA may include traffic conditioning rules which constitute a traffic conditioning agreement as a whole or partially. Service protection SES SETS settings A measure that ensures that the services can be received at the receive end. See severely errored second See synchronous equipment timing source Parameters of a system or operation that can be selected by the user.
severely errored second A one-second period which has a bit error ratio >= 10-3 or at least one defect. Time interval of one second during which a given digital signal is received with an error ratio greater than 10-3 (Rec. ITU R F. 592 needs correction) . SF SFP SFTP shock-proof reinforce shortcut menu side door See signal fail See small form-factor pluggable See Secure File Transfer Protocol A process by which the cabinet is fastened to the wiring frame or the top of the equipment room so that the cabinet stands stably. A menu that is displayed when right-clicking an object's name or icon. This is also referred to a context menu. The side door of a cabinet is used to protect the equipment inside the cabinet against unexpected touch and environment impact.
Issue 02 (2011-10-31)
1042
A Glossary
side mode suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total ratio source spectrum to the second largest peak. side trough signal cable signal degrade signal fail signal to noise ratio The trough on the side of the cable rack, which is used to place nuts so as to fix the cabinet. Common signal cables cover the E1 cable, network cable, and other non-subscriber signal cable. A signal indicating the associated data has degraded in the sense that a degraded defect (e.g., dDEG) condition is active. A signal that indicates the associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active. The ratio of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel). A network management protocol of TCP/IP. It enables remote users to view and modify the management information of a network element. This protocol ensures the transmission of management information between any two points. The polling mechanism is adopted to provide basic function sets. According to SNMP, agents, which can be hardware as well as software, can monitor the activities of various devices on the network and report these activities to the network console workstation. Control information about each device is maintained by a management information block.
Simple Network Management Protocol
single-ended switching A protection operation method which takes switching action only at the affected end of the protected entity (e.g. "trail", "subnetwork connection"), in the case of a unidirectional failure. single-mode fiber A type of fiber optic cable through which only one type of light signal with a fixed wave length can travel at a time. The inner diameter of the single-mode fiber is less than 10 microns. This type of fiber is used to transmit data in long distance. See service level agreement See Serial Line Interface Protocol single longitudinal mode section monitoring A specification for a new generation of optical modular transceivers. See single-mode fiber See side mode suppression ratio See subnetwork connection protection See subnetwork connection tunnel protection See Simple Network Management Protocol See signal to noise ratio An ASON connection which features flexible and dynamic adjustment of routes. SPC includes different classes of services (CoS). See synchronous optical network
SLA SLIP SLM SM small form-factor pluggable SMF SMSR SNCP SNCTP SNMP SNR soft permanent connections SONET
Issue 02 (2011-10-31)
1043
A Glossary
span
The physical reach between two pieces of WDM equipment. The number of spans determines the signal transmission distance supported by a piece of equipment and varies according to transmission system type.
Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant network to block some undesirable redundant paths through certain algorithms and prune a loop network into a loop-free tree network. SPC SPM SQL square connector SRLG SRS SSM SSMB SSU STM STM-1 STM-4 storage area network See soft permanent connections self phase modulation See structured query language Cables may use two styles of connectors: "square" and "D-style". Shared Risk Link Group stimulated Raman scattering See Synchronization Status Message synchronization status message byte synchronization supply unit Synchronous Transfer Mode See synchronous transport mode 1 Synchronous Transport Module of order 4 An architecture to attach remote computer storage devices such as disk array controllers, tape libraries and CD arrays to servers in such a way that to the operating system the devices appear as locally attached devices. See Spanning Tree Protocol A database query and programming language widely used for accessing, querying, updating, and managing data in relational database systems. Sub-network is the logical entity in the transmission network and comprises a group of network management objects. The network that consists of a group of interconnected or correlated NEs, according to different functions. For example, protection subnet, clock subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a sub-network is used to contain the equipments which are located in adjacent regions and closely related with one another, and it is indicated with a sub-network icon on a topological view. The U2000 supports multilevels of sub-networks. A sub-network planning can better the organization of a network view. On the one hand, the view space can be saved, on the other hand, it helps the network management personnel focus on the equipments under their management. A number used to differentiate network sections in a sub-network conference. A subnetwork ID consists of the first several digits (one or two) of a user phone number. An oderwire phone number consists of the sub-network ID and the user number. The technique used by the IP protocol to determine which network segment packets are destined for. The subnet mask is a binary pattern that is stored in the client machine, server or router and is matched with the IP address.
STP structured query language sub-network
sub-network number
subnet mask
subnetwork connection A function, which allows a working subnetwork connection to be replaced by a protection protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level.
A Glossary
subnetwork connection SNCTP provides a VC-4 level channel protection. When the working channel is faulty, tunnel protection the services of the entire VC-4 path can be switched over to the protection channel. support A part used to support and fix a cabinet on the antistatic floor, it is made of welded steel plates and is used to block the cabinets up, thus facilitating floor paving and cabling. Before the whole set of equipment is grounded, insulation plates must be installed under the supports, and insulating coverings must be added to the expansion bolts to satisfy the insulation requirements. An attribute set to determine whether an NE monitors the alarm. Under suppression status, NE will not monitor the corresponding alarm conditions and the alarm will not occur even when the alarm conditions are met. There may be the case that several protected boards need to be switched; thus the tributary board switching priority should be set. If the switching priority of each board is set the same, the tributary board that fails later cannot be switched. The board with higher priority can preempt the switching of that with lower priority.
Suppression state
Switching priority
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link. Message Nodes on an SDH network and a synchronization network acquire upstream clock information through this message. Then the nodes can perform proper operations on their clocks, such as tracing, switching, or converting to holdoff, and forward the synchronization information to downstream nodes. synchronize NE time synchronous digital hierarchy To send the system time of the server of the network management system to NEs so as to synchronize all NEs with the server. A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as frame structure, multiplexing mode, transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed counterparts, and the line coding of scrambling is only used only for signals. SDH is suitable for the fiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure. The SETS function provides timing reference to the relevant component parts of multiplexing equipment and represents the SDH network clement clock. A high-speed network that provides a standard interface for communications carriers to connect networks based on fiberoptic cable. SONET is designed to handle multiple data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbps, but multiples of this base rate go as high as 2.488 Gbps (gigabits per second).
synchronous equipment timing source synchronous optical network
synchronous transport Synchronous Transfer Mode at 155 Mbit/s. mode 1
T
TCM TCP TDM TE Tandem Connection Monitoring See Transmission Control Protocol See time division multiplexing See traffic engineering
Issue 02 (2011-10-31)
1045
A Glossary
Telecommunication A protocol model defined by ITU-T for managing open systems in a communications Management Network network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services. terminal multiplexer A device used at a network terminal to multiplex multiple channels of low rate signals into one channel of high rate signals, or to demultiplex one channel of high rate signals into multiple channels of low rate signals. See Trivial File Transfer Protocol trace identifier mismatch A multiplexing technology. TDM divides the sampling cycle of a channel into time slots (TSn, n=0, 1, 2, 3 and so on), and the sampling value codes of multiple signals engross time slots in a certain order, forming multiple multiplexing digital signals to be transmitted over one channel. Continuously repeating interval of time or a time period in which two devices are able to interconnect. Also called the moment synchronization, time synchronization means that the synchronization of the absolute time, which requires that the starting time of the signals keeps consistent with the UTC time. A technique used in best-effort delivery systems to prevent packets that loop endlessly. The TTL is set by the sender to the maximum time the packet is allowed to be in the network. Each router in the network decrements the TTL field when the packet arrives, and discards any packet if the TTL counter reaches zero. See Transaction Language 1 Type/Length/Value See terminal multiplexer See Telecommunication Management Network traffic Policing A technology that is used to dynamically monitor the traffic of the network and the load of the network elements, to adjust in real time the parameters such as traffic management parameters, route parameters and resource restriction parameters, and to optimize the utilization of network resources. The purpose is to prevent the congestion caused by unbalanced loads.
TFTP TIM time division multiplexing
Time Slot Time Synchronization
time to live
TL1 TLV TM TMN TP traffic engineering
Transaction Language Transaction Language One is a widely used telecommunications management protocol. 1 TL1 is a vendor-independent and technology-independent man-machine language. TL1 facilities can be provided as part of an OSS for interacting with either underlying management systems or NEs. One popular application is for a management system (or NE) to package its trap/notification data in TL1 format and forward it to an OSS component. ...(from authors.phptr.com/morris/glossary.html) Transaction Language 1 (TL1) is a widely used, "legacy", management protocol in telecommunications. It is a cross-vendor, cross-technology man-machine language, and is widely used to manage optical (SONET) and broadband access infrastructure in North America. It is defined in GR-831 by Bellcore (now Telcordia). (from en.wikipedia.org/wiki/TL1)
Issue 02 (2011-10-31)
1046
A Glossary
Transmission Control Protocol
The protocol within TCP/IP that governs the breakup of data messages into packets to be sent via IP (Internet Protocol), and the reassembly and verification of the complete messages from packets received by IP. A connection-oriented, reliable protocol (reliable in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in the ISO/OSI reference model. A component that can be installed in the cabinet for holding chassis or other devices. One or more Tributary Units, occupying fixed, defined positions in a higher order VCn payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that mixed capacity payloads made up of different size Tributary Units can be constructed to increase flexibility of the transport network A small and simple alternative to FTP for transferring files. TFTP is intended for applications that do not need complex interactions between the client and server. TFTP restricts operations to simple file transfers and does not provide authentication. TFTP is small enough to be contained in ROM to be used for bootstrapping diskless machines. Two Rate Three Color Marker trail trace identifier See time to live tributary unit See tributary unit group
tray tributary unit group
Trivial File Transfer Protocol
trTCM TTI TTL TU TUG
U
UAS UAT UDP unavailable second See unavailable time event See User Datagram Protocol
unavailable time event A UAT event is reported when the monitored object generates 10 consecutive severely errored seconds (SES) and the SESs begin to be included in the unavailable time. The event will end when the bit error ratio per second is better than within 10 consecutive seconds. UNI universal time coordinated Unprotected See user network interface The world-wide scientific standard of timekeeping. It is based upon carefully maintained atomic clocks and is kept accurate to within microseconds worldwide. Pertaining to the transmission of the services that are not protected, the services cannot be switched to the protection channel if the working channel is faulty or the service is interrupted, because protection mechanism is not configured. An operation to report some or all configuration data of an NE to the NMS(Network Management system). The configuration data then covers the configuration data stored at the NMS side. The subrack close to the top of the cabinet when a cabinet contains several subracks. A client user of the NMS. The user name and password uniquely identifies the operation rights of a user in the NMS.
upload
Upper subrack User
Issue 02 (2011-10-31)
1047
A Glossary
User Datagram Protocol
A TCP/IP standard protocol that allows an application program on one device to send a datagram to an application program on another. User Datagram Protocol (UDP) uses IP to deliver datagrams. UDP provides application programs with the unreliable connectionless packet delivery service. Thus, UDP messages can be lost, duplicated, delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is, the destination device does not actively confirm whether the correct data packet is received.
user network interface The interface between user equipment and private or public network equipment (for example, ATM switches). UTC See universal time coordinated
V
VB VC VCG VCI virtual channel identifier virtual concatenation group virtual container virtual bridge See virtual container See virtual concatenation group See virtual channel identifier A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. A group of co-located member trail termination functions that are connected to the same virtual concatenation link The information structure used to support path layer connections in the SDH. It consists of information payload and path Overhead (POH) information fields organized in a block frame structure which repeats every 125 s or 500 s. A logical grouping of two or more nodes which are not necessarily on the same physical network segment but which share the same IP network number. This is often associated with switched Ethernet. The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs.
virtual local area network virtual path identifier
virtual private network A system configuration, where the subscriber is able to build a private network via connections to different network switches that may include private network capabilities. VLAN VOA voice over IP See virtual local area network Variable Optical Attenuator An IP telephony term for a set of facilities used to manage the delivery of voice information over the Internet. VoIP involves sending voice information in a digital form in discrete packets rather than by using the traditional circuit-committed protocols of the public switched telephone network (PSTN). See voice over IP See virtual path identifier See virtual private network Virtual Router Redundancy Protocol
VoIP VPI VPN VRRP
Issue 02 (2011-10-31)
1048
A Glossary
W
WAN wavelength division multiplexing See wide area network A technology that utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple channels to transmit simultaneously in a single fiber.
Wavelength protection The wavelength protection group is important to describe the wavelength protection group structure. Its function is similar to that of the protection subnet in the SDH NE. The wavelength path protection can only work with the correct configuration of the wavelength protection group. WDM WEEE wide area network See wavelength division multiplexing waste electrical and electronic equipment A network composed of computers which are far away from each other which are physically connected through specific protocols. WAN covers a broad area, such as a province, a state or even a country. The channels allocated to transport the normal traffic. A specific service that is part of a protection group and is labeled working. weighted round Robin wavelength selective switching Wait To Restore wavelength cross-connection protection The WXCP service is also called the GE ADM protection service. The WXCP is a type of channel protection based on ring network. It adopts the dual fed and selective receiving principle and uses the cross-connection function to achieve service switching between working and protection channels.
Working path Working service WRR WSS WTR WXCP WXCP service
X
XFP XPM 10Gbit/s Small Form-Factor Pluggable cross-phase modulation
Issue 02 (2011-10-31)
1049

Alarms and Performance Events Reference (V100R006C01 - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarms and Performance Events Reference (V100R006C01 - 02)

Uploaded by

Copyright:

Available Formats

OptiX OSN 8800/6800/3800 V100R006C01

Alarms and Performance Events Reference

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

About This Document

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Updates in Issue 02 (2011-10-31) Based on Product Version V100R006C01

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Update 4 Alarm Processing

5 Performance Event List

Updates in Issue 01 (2011-07-30) Based on Product Version V100R006C01

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Update 4 Alarm Processing

5 Performance Event List

Updates in Issue 03 (2011-09-15) Based on Product Version V100R006C00

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Updates in Issue 02 (2011-04-15) Based on Product Version V100R006C00

Updates in Issue 01 (2010-12-31) Based on Product Version V100R006C00

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Updates in Issue 04 (2011-08-30) Based on Product Version V100R005C00

Updates in Issue 03 (2011-05-25) Based on Product Version V100R005C00

Updates in Issue 02 (2010-11-20) Based on Product Version V100R005C00

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Updates in Issue 01 (2010-07-30) Based on Product Version V100R005C00

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Update 4 Alarm Processing

5 Performance Event List

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

About This Document

Update 6 Performance Event Processing

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

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

3 Common Alarm Processing.....................................................................................................211

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference

OptiX OSN 8800/6800/3800 Alarms and Performance Events Reference