Alarms and Performance Events Reference (V100R002C00 - 04)

OptiX OSN 1800 Compact Multi-Service Edge Optical Transport
Platform
V100R002C00
Alarms and Performance Events Reference
Issue
04
Date
2010-10-20
Huawei Proprietary and Confidential

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

OptiX OSN 1800 Compact Multi-Service Edge Optical

Transport Platform
Contents
Contents
About This Document.....................................................................................................................1
1 Overview......................................................................................................................................1-1
1.1 Alarm Level.....................................................................................................................................................1-2
1.2 Alarm Category...............................................................................................................................................1-2
1.3 Performance Event Category..........................................................................................................................1-3
1.4 Alarm Signal Flow..........................................................................................................................................1-4
1.4.1 Overview................................................................................................................................................1-5
1.4.2 Non-Convergent OTU Processing Standard SDH Signals....................................................................1-6
1.4.3 Non-Convergent OTU Processing Standard OTN Signals..................................................................1-10
1.4.4 Convergent OTU Processing Standard SDH Signals...........................................................................1-13
1.4.5 Convergent OTU Processing Standard OTN Signals..........................................................................1-15
1.4.6 Regenerating OTU...............................................................................................................................1-18
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function.............................................1-20
1.4.8 Non-Convergence OTU Board Processing the GE Signals.................................................................1-22
1.4.9 Convergence OTU Processing the GE Signals....................................................................................1-25
1.5 Suppression Relation of Alarms....................................................................................................................1-27
1.5.1 Suppression of OTN Alarms................................................................................................................1-27
1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment Alarms................1-29
2 Alarm List....................................................................................................................................2-1
2.1 Product Alarm List..........................................................................................................................................2-2
2.1.1 Alarm List A...........................................................................................................................................2-3
2.1.2 Alarm List B...........................................................................................................................................2-3
2.1.3 Alarm List C...........................................................................................................................................2-4
2.1.4 Alarm List D...........................................................................................................................................2-4
2.1.5 Alarm List E...........................................................................................................................................2-4
2.1.6 Alarm List F...........................................................................................................................................2-5
2.1.7 Alarm List G...........................................................................................................................................2-5
2.1.8 Alarm List H...........................................................................................................................................2-6
2.1.9 Alarm List I............................................................................................................................................2-6
2.1.10 Alarm List J..........................................................................................................................................2-6
2.1.11 Alarm List L.........................................................................................................................................2-7
2.1.12 Alarm List M........................................................................................................................................2-8
Issue 04 (2010-10-20)

Contents

Transport Platform
2.1.13 Alarm List N.........................................................................................................................................2-9
2.1.14 Alarm List O.........................................................................................................................................2-9
2.1.15 Alarm List P.......................................................................................................................................2-13
2.1.16 Alarm List R.......................................................................................................................................2-14
2.1.17 Alarm List S.......................................................................................................................................2-15
2.1.18 Alarm List T.......................................................................................................................................2-16
2.1.19 Alarm List U.......................................................................................................................................2-17
2.1.20 Alarm List V.......................................................................................................................................2-17
2.1.21 Alarm List W......................................................................................................................................2-17
2.2 Board Alarm List...........................................................................................................................................2-18

2.2.1 APIU Board Alarm List.......................................................................................................................2-19
2.2.2 DMD1/DMD1S Board Alarm List.......................................................................................................2-19
2.2.3 DMD2/DMD2S Board Alarm List.......................................................................................................2-19
2.2.4 FAN Board Alarm List.........................................................................................................................2-19
2.2.5 FIU Board Alarm List..........................................................................................................................2-19
2.2.6 LDE Board Alarm List.........................................................................................................................2-20
2.2.7 LDGF Board Alarm List......................................................................................................................2-20
2.2.8 LDGF2 Board Alarm List....................................................................................................................2-21
2.2.9 LOE Board Alarm List.........................................................................................................................2-22
2.2.10 LQG Board Alarm List......................................................................................................................2-22
2.2.11 LQM Board Alarm List......................................................................................................................2-23
2.2.12 LQM2 Board Alarm List....................................................................................................................2-24
2.2.13 LQPL Board Alarm List.....................................................................................................................2-24
2.2.14 LQPU Board Alarm List....................................................................................................................2-25
2.2.15 LSPL Board Alarm List.....................................................................................................................2-26
2.2.16 LSPR Board Alarm List.....................................................................................................................2-26
2.2.17 LSPU Board Alarm List.....................................................................................................................2-27
2.2.18 LSX Board Alarm List.......................................................................................................................2-28
2.2.19 LWX2 Board Alarm List....................................................................................................................2-28
2.2.20 MD8/MD8S Board Alarm List..........................................................................................................2-29
2.2.21 MR1/MR1S Board Alarm List...........................................................................................................2-29
2.2.24 MR8 Board Alarm List......................................................................................................................2-29
2.2.25 OLP Board Alarm List.......................................................................................................................2-29
2.2.26 OPU Board Alarm List.......................................................................................................................2-30
2.2.27 PIU Board Alarm List........................................................................................................................2-30
2.2.28 SBM1 Board Alarm List....................................................................................................................2-30
2.2.32 SCC Board Alarm List.......................................................................................................................2-31
ii

Issue 04 (2010-10-20)

Transport Platform
Contents
2.2.33 SCS Board Alarm List........................................................................................................................2-32

2.2.34 TSP Board Alarm List........................................................................................................................2-32
3 Alarm Processing........................................................................................................................3-1
3.1 Common Alarm Processing............................................................................................................................3-2
3.1.1 ALM_DATA_RLOS..............................................................................................................................3-3
3.1.2 ALM_DATA_TLOS..............................................................................................................................3-4
3.1.3 B1_EXC.................................................................................................................................................3-5
3.1.4 BEFFEC_EXC.......................................................................................................................................3-7
3.1.5 IN_PWR_HIGH.....................................................................................................................................3-9
3.1.6 IN_PWR_LOW....................................................................................................................................3-11
3.1.7 LASER_MODULE_MISMATCH.......................................................................................................3-13
3.1.8 LINK_ERR...........................................................................................................................................3-14
3.1.9 LOOP_ALM.........................................................................................................................................3-16
3.1.10 LSR_WILL_DIE................................................................................................................................3-17
3.1.11 MS_AIS..............................................................................................................................................3-18
3.1.12 MS_RDI.............................................................................................................................................3-20
3.1.13 MUT_LOS.........................................................................................................................................3-22
3.1.14 NEBD_XC_DIF.................................................................................................................................3-23
3.1.15 OA_LOW_GAIN...............................................................................................................................3-24
3.1.16 ODUk_PM_AIS.................................................................................................................................3-25
3.1.17 ODUk_PM_BDI.................................................................................................................................3-27
3.1.18 ODUk_PM_DEG...............................................................................................................................3-28
3.1.19 ODUk_PM_EXC...............................................................................................................................3-30
3.1.20 OPS_PS_INDI....................................................................................................................................3-31
3.1.21 OSC_LOS...........................................................................................................................................3-33
3.1.22 OUT_PWR_HIGH.............................................................................................................................3-34
3.1.23 PORT_MODULE_OFFLINE............................................................................................................3-35
3.1.24 POWER_DIFF_DEFECT..................................................................................................................3-36
3.1.25 POWER_FAIL...................................................................................................................................3-37
3.1.26 PUMP_COOL_EXC..........................................................................................................................3-39
3.1.27 R_LOF................................................................................................................................................3-40
3.1.28 R_LOS................................................................................................................................................3-42
3.1.29 REM_SF.............................................................................................................................................3-44
3.1.30 SECU_ALM.......................................................................................................................................3-45
3.1.31 SUBRACK_ID_CONFLICT.............................................................................................................3-46
3.1.32 TD.......................................................................................................................................................3-47
3.1.33 TF.......................................................................................................................................................3-48
3.1.34 WRG_BD_TYPE...............................................................................................................................3-49
3.2 Alarm Processing..........................................................................................................................................3-50
3.2.1 AD_CHECK_FAIL..............................................................................................................................3-54
3.2.2 AU_AIS................................................................................................................................................3-55
3.2.3 AU_LOP...............................................................................................................................................3-57
Issue 04 (2010-10-20)

iii
Contents

Transport Platform
3.2.4 B1_SD..................................................................................................................................................3-58
3.2.5 B2_EXC...............................................................................................................................................3-60
3.2.6 B2_SD..................................................................................................................................................3-61
3.2.7 B3_EXC...............................................................................................................................................3-62
3.2.8 B3_SD..................................................................................................................................................3-65
3.2.9 BD_STATUS.......................................................................................................................................3-68
3.2.10 BOOTROM_BAD.............................................................................................................................3-69
3.2.11 CFG_VERIFY....................................................................................................................................3-70
3.2.12 CFGDATA_OUTRANGE.................................................................................................................3-71
3.2.13 DBMS_ERROR.................................................................................................................................3-74
3.2.14 DBMS_PROTECT_MODE...............................................................................................................3-75
3.2.15 DCC_CHAN_LACK.........................................................................................................................3-76
3.2.16 DOWN_E1_AIS.................................................................................................................................3-77
3.2.17 E1_LOC.............................................................................................................................................3-78
3.2.18 ETH_LINK_DOWN..........................................................................................................................3-79
3.2.19 EXT_SYNC_LOS..............................................................................................................................3-81
3.2.20 FAN_FAIL.........................................................................................................................................3-82
3.2.21 FEC_LOF...........................................................................................................................................3-83
3.2.22 FEC_OOF...........................................................................................................................................3-84
3.2.23 FPGA_ABN.......................................................................................................................................3-85
3.2.24 FUSE_ALARM..................................................................................................................................3-86
3.2.25 GPON_DS_LOF................................................................................................................................3-87
3.2.26 GPON_RUF.......................................................................................................................................3-88
3.2.27 GPON_US_LOF................................................................................................................................3-89
3.2.28 HARD_BAD......................................................................................................................................3-90
3.2.29 HP_LOM............................................................................................................................................3-93
3.2.30 HP_RDI..............................................................................................................................................3-94
3.2.31 HP_REI..............................................................................................................................................3-95
3.2.32 HP_SLM.............................................................................................................................................3-97
3.2.33 HP_TIM.............................................................................................................................................3-98
3.2.34 HP_UNEQ........................................................................................................................................3-100
3.2.35 J0_MM.............................................................................................................................................3-101
3.2.36 LASER_MOD_ERR_EX.................................................................................................................3-102
3.2.37 LCS_DAYS_OF_GRACE...............................................................................................................3-103
3.2.38 LCS_EXPIRED................................................................................................................................3-104
3.2.39 LCS_FILE_NOT_EXIST.................................................................................................................3-105
3.2.40 L_SYNC...........................................................................................................................................3-106
3.2.41 LOCAL_FAULT..............................................................................................................................3-107
3.2.42 LP_R_FIFO......................................................................................................................................3-108
3.2.43 LP_RDI............................................................................................................................................3-109
3.2.44 LP_REI.............................................................................................................................................3-111
3.2.45 LP_RFI.............................................................................................................................................3-112
iv

Issue 04 (2010-10-20)

Transport Platform
Contents
3.2.46 LP_SLM...........................................................................................................................................3-113
3.2.47 LP_T_FIFO......................................................................................................................................3-114
3.2.48 LP_TIM............................................................................................................................................3-116
3.2.49 LP_UNEQ........................................................................................................................................3-117
3.2.50 LTI....................................................................................................................................................3-118
3.2.51 MDL_ALARM.................................................................................................................................3-120
3.2.52 MS_REI............................................................................................................................................3-122
3.2.53 MSSW_DIFFERENT.......................................................................................................................3-122
3.2.54 NESTATE_INSTALL.....................................................................................................................3-124
3.2.55 NO_BD_PARA................................................................................................................................3-125
3.2.56 NO_BD_SOFT.................................................................................................................................3-126
3.2.57 ODUk_LOFLOM.............................................................................................................................3-127
3.2.58 ODUk_PM_LCK.............................................................................................................................3-129
3.2.59 ODUk_PM_OCI...............................................................................................................................3-129
3.2.60 ODUk_PM_TIM..............................................................................................................................3-130
3.2.61 OPS_MAIN_BAK_ATTR_DIFF....................................................................................................3-132
3.2.62 OPS_STA_INDI...............................................................................................................................3-133
3.2.63 OOL..................................................................................................................................................3-134
3.2.64 OPUk_PLM......................................................................................................................................3-135
3.2.65 OTUk_AIS.......................................................................................................................................3-136
3.2.66 OTUk_BDI.......................................................................................................................................3-137
3.2.67 OTUk_DEG.....................................................................................................................................3-138
3.2.68 OTUk_EXC......................................................................................................................................3-139
3.2.69 OTUk_LOF......................................................................................................................................3-140
3.2.70 OTUk_LOM.....................................................................................................................................3-141
3.2.71 OTUk_TIM......................................................................................................................................3-142
3.2.72 OUT_PWR_LOW............................................................................................................................3-144
3.2.73 PATCH_ACT_TIMEOUT...............................................................................................................3-145
3.2.74 PATCH_DEACT_TIMEOUT.........................................................................................................3-145
3.2.75 PATCH_ERR...................................................................................................................................3-146
3.2.76 PATCH_NOT_CONFIRM .............................................................................................................3-147
3.2.77 PATCH_PKGERR...........................................................................................................................3-148
3.2.78 PATCHFILE_NOTEXIST...............................................................................................................3-149
3.2.79 POWER_DIFF_OVER....................................................................................................................3-149
3.2.80 PRBS_LSS.......................................................................................................................................3-150
3.2.81 PUM_BCM_ALM...........................................................................................................................3-151
3.2.82 PUM_TEM_ALM............................................................................................................................3-152
3.2.83 PWR_MAJ_ALM............................................................................................................................3-153
3.2.84 R_LOC.............................................................................................................................................3-155
3.2.85 RELAY_ALARM_CRITICAL .......................................................................................................3-156
3.2.86 RELAY_ALARM_IGNORE ..........................................................................................................3-156
3.2.87 RELAY_ALARM_MAJOR ............................................................................................................3-157
Issue 04 (2010-10-20)

Contents

Transport Platform
3.2.88 RELAY_ALARM_MINOR ............................................................................................................3-158
3.2.89 REM_SD..........................................................................................................................................3-159
3.2.90 REMOTE_FAULT...........................................................................................................................3-160
3.2.91 S1_SYN_CHANGE.........................................................................................................................3-161
3.2.92 SUB_RACK_OFFLINE...................................................................................................................3-162
3.2.93 STORM_CUR_QUENUM_OVER.................................................................................................3-163
3.2.94 SUBRACK_TYPE_MISMATCH...................................................................................................3-164
3.2.95 SWDL_ACTIVATED_TIMEOUT..................................................................................................3-165
3.2.96 SWDL_AUTOMATCH_INH..........................................................................................................3-166
3.2.97 SWDL_CHGMNG_NOMATCH.....................................................................................................3-166
3.2.98 SWDL_COMMIT_FAIL.................................................................................................................3-167
3.2.99 SWDL_INPROCESS.......................................................................................................................3-168
3.2.100 SWDL_NEPKGCHECK................................................................................................................3-169
3.2.101 SWDL_PKG_NOBDSOFT...........................................................................................................3-170
3.2.102 SWDL_PKGVER_MM.................................................................................................................3-171
3.2.103 SWDL_ROLLBACK_FAIL..........................................................................................................3-171
3.2.104 SYNC_C_LOS...............................................................................................................................3-172
3.2.105 SYSLOG_COMM_FAIL...............................................................................................................3-174
3.2.106 TEM_HA........................................................................................................................................3-175
3.2.107 TEM_LA........................................................................................................................................3-176
3.2.108 TEMP_ALARM.............................................................................................................................3-177
3.2.109 TEMP_OVER................................................................................................................................3-178
3.2.110 THUNDERALM............................................................................................................................3-179
3.2.111 TU_AIS..........................................................................................................................................3-180
3.2.112 TU_LOP.........................................................................................................................................3-182
3.2.113 UP_E1_AIS....................................................................................................................................3-184
3.2.114 VCXO_LOC...................................................................................................................................3-185
4 Performance Event List.............................................................................................................4-1

4.1 Product Performance Event List..................................................................................................................... 4-2
4.1.1 Performance Event List of Check and Error Correction........................................................................4-2
4.1.2 Performance Event of Pointer Justification............................................................................................4-8
4.1.3 Performance Event List of Equipment Function....................................................................................4-8
4.1.4 Performance Event of Multiplex Section Bit Error..............................................................................4-10
4.1.5 Performance Event List of Regenerator Section Bit Error...................................................................4-10
4.1.6 Performance Event of Higher Order Path Bit Error.............................................................................4-11
4.1.7 Performance Event of Lower Order Path Bit Error..............................................................................4-12
4.1.8 Performance Event List of RMON Function.......................................................................................4-12
4.2 Board Performance Event List......................................................................................................................4-14
4.2.1 LDE Board Performance Event List....................................................................................................4-15
4.2.2 LDGF Board Performance Event List..................................................................................................4-16
4.2.3 LDGF2 Board Performance Event List................................................................................................4-16
4.2.4 LOE Board Performance Event List....................................................................................................4-17
vi

Issue 04 (2010-10-20)

Transport Platform
Contents
4.2.5 LQG Board Performance Event List....................................................................................................4-18

4.2.6 LQM2 Board Performance Event List.................................................................................................4-18
4.2.7 LQM Board Performance Event List...................................................................................................4-19
4.2.8 LQPL Board Performance Event List..................................................................................................4-20
4.2.9 LQPU Board Performance Event List..................................................................................................4-21
4.2.10 LSPL Board Performance Event List.................................................................................................4-22
4.2.11 LSPR Board Performance Event List.................................................................................................4-23
4.2.12 LSPU Board Performance Event List................................................................................................4-23
4.2.13 LSX Board Performance Event List...................................................................................................4-24
4.2.14 LWX2 Board Performance Event List...............................................................................................4-24
4.2.15 OLP Board Performance Event List...................................................................................................4-25
4.2.16 OPU Board Performance Event List..................................................................................................4-25
4.2.17 TSP Board Performance Event List...................................................................................................4-25
5 Performance Event Processing.................................................................................................5-1

5.1 AUPJCHIGH...................................................................................................................................................5-4
5.2 AUPJCLOW....................................................................................................................................................5-5
5.3 CCV.................................................................................................................................................................5-6
5.4 ENVTMP........................................................................................................................................................5-7
5.5 FEC_AFT_COR_ER.......................................................................................................................................5-7
5.6 FEC_AFT_COR_ERAVR..............................................................................................................................5-8
5.7 FEC_BEF_COR_ER.......................................................................................................................................5-9
5.8 FEC_BEF_COR_ERAVR............................................................................................................................5-10
5.9 FEC_COR_0BIT_CNT.................................................................................................................................5-11
5.10 FEC_COR_1BIT_CNT...............................................................................................................................5-11
5.11 FEC_COR_BYTE_CNT.............................................................................................................................5-12
5.12 FEC_UNCOR_BLOCK_CNT....................................................................................................................5-12
5.13 GPON_DF_BIP_CNT.................................................................................................................................5-13
5.14 GPON_UF_BIP_CNT.................................................................................................................................5-14
5.15 HPBBE........................................................................................................................................................5-14
5.16 HPCSES......................................................................................................................................................5-15
5.17 HPES...........................................................................................................................................................5-16
5.18 HPFEBBE...................................................................................................................................................5-17
5.19 HPFECSES..................................................................................................................................................5-18
5.20 HPFEES......................................................................................................................................................5-19
5.21 HPFESES....................................................................................................................................................5-20
5.22 HPSES.........................................................................................................................................................5-21
5.23 HPUAS........................................................................................................................................................5-22
5.24 LSBIAS.......................................................................................................................................................5-23
5.25 LSCLC........................................................................................................................................................5-24
5.26 LSIOP..........................................................................................................................................................5-25
5.27 LSOOP........................................................................................................................................................5-26
5.28 LSTMP........................................................................................................................................................5-27
Issue 04 (2010-10-20)

vii
Contents

Transport Platform
5.29 MSBBE.......................................................................................................................................................5-28
5.30 MSCSES......................................................................................................................................................5-29
5.31 MSES..........................................................................................................................................................5-30
5.32 MSFEBBE...................................................................................................................................................5-31
5.33 MSFECSES.................................................................................................................................................5-32
5.34 MSFEES......................................................................................................................................................5-33
5.35 MSFESES....................................................................................................................................................5-34
5.36 MSSES........................................................................................................................................................5-35
5.37 MSUAS.......................................................................................................................................................5-36
5.38 ODUk_PM_BBE.........................................................................................................................................5-37
5.39 ODUk_PM_BBER......................................................................................................................................5-38
5.40 ODUk_PM_ES............................................................................................................................................5-39
5.41 ODUk_PM_FEBBE....................................................................................................................................5-39
5.42 ODUk_PM_FEBBER.................................................................................................................................5-40
5.43 ODUk_PM_FEES.......................................................................................................................................5-41
5.44 ODUk_PM_FESES.....................................................................................................................................5-42
5.45 ODUk_PM_FESESR..................................................................................................................................5-42
5.46 ODUk_PM_FEUAS....................................................................................................................................5-43
5.47 ODUk_PM_SES..........................................................................................................................................5-44
5.48 ODUk_PM_SESR.......................................................................................................................................5-45
5.49 ODUk_PM_UAS........................................................................................................................................5-46
5.50 OTUk_BBE.................................................................................................................................................5-46
5.51 OTUk_BBER..............................................................................................................................................5-47
5.52 OTUk_ES....................................................................................................................................................5-48
5.53 OTUk_FEBBE............................................................................................................................................5-49
5.54 OTUk_FEBBER..........................................................................................................................................5-50
5.55 OTUk_FEES...............................................................................................................................................5-50
5.56 OTUk_FESES.............................................................................................................................................5-51
5.57 OTUk_FESESR..........................................................................................................................................5-52
5.58 OTUk_FEUAS............................................................................................................................................5-53
5.59 OTUk_SES..................................................................................................................................................5-53
5.60 OTUk_SESR...............................................................................................................................................5-54
5.61 OTUk_UAS.................................................................................................................................................5-55
5.62 OTUk_IAES................................................................................................................................................5-56
5.63 OTUk_BIAES.............................................................................................................................................5-57
5.64 PUMPTMP..................................................................................................................................................5-57
5.65 RSBBE........................................................................................................................................................5-58
5.66 RSCSES......................................................................................................................................................5-59
5.67 RSES...........................................................................................................................................................5-60
5.68 RSOFS.........................................................................................................................................................5-61
5.69 RSOOF........................................................................................................................................................5-62
5.70 RSSES.........................................................................................................................................................5-63
viii

Issue 04 (2010-10-20)

Transport Platform
Contents
5.71 RSUAS........................................................................................................................................................5-64
5.72 SUMIOP......................................................................................................................................................5-65
5.73 SUMOOP....................................................................................................................................................5-66
5.74 TUPJCHIGH...............................................................................................................................................5-67
5.75 TUPJCLOW................................................................................................................................................5-68
5.76 WCV............................................................................................................................................................5-69
A Glossary.....................................................................................................................................A-1
B Acronyms and Abbreviations.................................................................................................B-1
Issue 04 (2010-10-20)

ix

Transport Platform
Figures
Figures
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals....................1-7
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals....................1-9
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals..................1-10
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals..................1-12
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals..........................1-14
Figure 1-6 Alarm signal flow 1: when the convergent OTU processes standard OTN signals.........................1-16
Figure 1-7 Alarm signal flow 2: when the convergent OTU processes standard OTN signals.........................1-17
Figure 1-8 Alarm signal flow of the regenerating OTU.....................................................................................1-19
Figure 1-9 OTU with the cross-connect function in the straight-through mode................................................1-20
Figure 1-10 OTU with the cross-connect function in the cross-connect mode..................................................1-21
Figure 1-11 Alarm signal flow when the non-convergence OTU board processes the GE signals - 1..............1-22
Figure 1-12 Alarm signal flow when the non-convergence OTU board processes the GE signals - 2..............1-24
Figure 1-13 Alarm signal flow when the convergence OTU board processes the GE signals .........................1-26
Figure 1-14 Suppression of OTN alarms...........................................................................................................1-28
Figure 1-15 Suppression of alarms related to SDH services and other common equipment alarms.................1-30
Figure A-1 Service flow......................................................................................................................................A-3
Figure A-2 Service flow......................................................................................................................................A-4
Issue 04 (2010-10-20)

xi

Transport Platform
Tables
Tables
Table 1-1 Alarm levels.........................................................................................................................................1-2
Table 1-2 Alarm category.....................................................................................................................................1-3
Table 1-3 Performance event categories...............................................................................................................1-4
Table 4-1 Performance Event List of Check and Error Correction......................................................................4-2
Table 4-2 Pointer justification performance event list.........................................................................................4-8
Table 4-3 Performance Event List of Equipment Function..................................................................................4-8
Table 4-4 Performance Event list of Multiplex Section Bit Error......................................................................4-10
Table 4-5 Performance Event List of Regenerator Section Bit Error.................................................................4-11
Table 4-6 Higher order path performance event list...........................................................................................4-11
Table 4-7 Lower order path performance event list...........................................................................................4-12
Table 4-8 RMON Performance Event List.........................................................................................................4-12
Issue 04 (2010-10-20)

xiii

Transport Platform
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX OSN 1800
V100R002C00
iManager U2000
V100R002C01
Intended Audience
The intended audiences of this document are:
l
Network Monitoring Engineer
System Maintenance Engineer
Symbol Conventions
The following symbols may be found in this document. They are defined as follows:
Symbol
Description
DANGER
WARNING
CAUTION
TIP
Issue 04 (2010-10-20)
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk which,
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could cause equipment damage, data loss, and
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
you time.


Transport Platform
About This Document
Symbol
Description
Provides additional information to emphasize or
supplement important points of the main text.
NOTE
GUI Conventions
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles are in

boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Issue 04 (2010-10-20) Based on Product Version

V100R002C00
The updated contents are as follows.
Added the alarm processing of LCS_FILE_NOT_EXIST, LCS_EXPIRED,
LCS_DAYS_OF_GRACE.
The PCS_CODE_ERR alarms is deleted.
Some bugs in the manual of the previous version are fixed.

V100R002C00
The X40 board is deleted.
2

Issue 04 (2010-10-20)

Transport Platform
About This Document

V100R002C00

V100R002C00
Add the sections of "Alarm Signal Flow".
Added the alarm processing of ETH_LINK_DOWN, S1_SYN_CHANGE,
SUB_RACK_OFFLINE, SUBRACK_TYPE_MISMATCH, OPS_STA_INDI.
Added the alarms and performance events of follow boards: APIU, LDE, LQPL, LQPU, TSP.
Issue 07 (2010-06-30) Based on Product Version V100R001


The LOCAL_FAULT, REMOTE_FAULT alarms have been added.

The LOE boards have been added.

Issue 04 (2010-10-20)


Transport Platform
About This Document
The OA_LOW_GAIN, PUM_BCM_ALM, PUM_TEM_ALM, PRBS_LSS,

PUMP_COOL_EXC alarms have been added.
The WCV, CCV, PUMPTMP, SUMOOP performances have been added.
The parameter of alarms have been updated.


Chapter
Update Description
Chapter 2 Alarm List
The LOSI, LOFI and ONU_OFFLINE

alarms have been added.
The LDER, LSEL, LSEU boards have been
deleted.
The NO_BD_SOFT alarm of LSPR board
have been added.
The R_LOF alarm of LQG board have been
added.
The PATCH_DEACT_TIMEOUT,
PATCH_ACT_TIMEOUT,
PWR_MAJ_ALM, TEMP_ALARM,
FUSE_ALARM, MDL_ALARM, alarms of
SCC board have been added.
The SYSTEM_DEF_RUNNING,
VERIFY_LCS_ERROR,
LICENSE_GOINGTO_EXPIRT, R_OOF,
SPEED_OVER alarms have been deleted.
The W_R_FAILURE alarm of SCC, LQM,
LQM2, LDGF, LDGF2, LQG, LWX2,
LOEL, LOEU, OLP, LSPU, LSPL, LSPR,
LDER boards have been deleted.
The LTEMP_OVER alarm of SCC, LQM,
LQM2, LDGF, LDGF2, LQG, LWX2,
LOEL, LOEU, LSPU, LSPL, LSPR, LDER
boards have been deleted.
The TEM_HA and TEM_LA alarms have
been added.

Issue 04 (2010-10-20)

Transport Platform
About This Document
Chapter
Update Description
Chapter 3 Alarm Processing
Add the description of new alarms.
Chapter 4 Performance Event List
The LDER, LSEL, LSEU boards have been

deleted.
The ETHCRCALI have been deleted.

The first release.
Issue 04 (2010-10-20)


Transport Platform
1 Overview
Overview
About This Chapter

This chapter describes the meaning, indicator status, category, range, and impact of the alarms
of four levels. It also describes the meaning and category of performance events, and provides
the suppression relation of alarms and performance event suppression by alarms.
1.1 Alarm Level
This section respectively describes the meaning, impact, and indicator status of the alarms of
four levels.
1.2 Alarm Category
This section describes the meaning and range of alarms in different categories.
1.3 Performance Event Category
The performance events can be classified into four categories according to the functions
monitored by the performance events.
1.4 Alarm Signal Flow
This section describes the alarm signal flow of the OTU. It describes the generation, detection,
and transmission of alarms when the OTU accesses different types of signals.
1.5 Suppression Relation of Alarms
This section describes the rules of alarm suppression and provides the suppression relation figure
of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm
suppression.
Issue 04 (2010-10-20)

1-1

Transport Platform
1 Overview
1.1 Alarm Level

This section respectively describes the meaning, impact, and indicator status of the alarms of
four levels.
The alarm level is used to identify the severity, importance, and urgency of the alarms. The
alarms can be classified into the following four levels in the sequence of decreasing severity:
critical alarm, major alarm, minor alarm, and warning alarm.
l
Critical alarm: The alarm needs to be handled immediately; otherwise, the system will be
down.
Major alarm: The alarm needs to be handled in time; otherwise, some important functions
will not be performed.
Minor alarm: The alarm is used to inform the maintenance personnel of locating the alarm
causes and removing the incipient fault.
Warning alarm: The alarm need not be handled. The maintenance personnel only need to
know the running status of the equipment.
For the meaning and corresponding indicator status on the board of the alarms of the four levels,
see Table 1-1.
Table 1-1 Alarm levels
Alarm Level
Definition
Indicator Status
Critical alarm
Global fault alarms and event alarms that

cause system down
The SRV indicator is on

(red).
Major alarm
Faulty alarms and event alarms of certain

boards or lines
The SRV indicator is on

(red).
Minor alarm
General fault alarms and event alarms that are

used to indicate whether the board or line is
normally working such as board reset and
failure or timeout of occupation of common
resources.
The SRV is on (yellow).
Warning
alarm
Fault alarms and event alarms for warning
The SRV is on (green).
NOTE
If the SRV is not on, it indicates that the board is not configured with services.
1.2 Alarm Category

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

Issue 04 (2010-10-20)

Transport Platform
1 Overview
Table 1-2 Alarm category

Alarm
Category
Definition
Example
Communication
alarm
Alarms related to the NE

communication, ECC
communication, and
communication with optical
signals
The alarm is generated when the

NE communication is interrupted
or the optical signal is lost.
Process alarm
Alarms related to the software

processing and anomalies

database is in error or the NE is in
the installing state.
Equipment alarm
Alarms related to the hardware of

the equipment

laser is faulty or the optical
interface is looped back.
Service alarm
Alarms related to the service status

and network service quality

signals at the line layer are
degraded.
Environment
alarm
Alarms related to the power supply

system and environment of the
equipment room

temperature of the power module is
excessively high.
Security alarm
Alarms related to the network

management and the NE security

NE user is not logged in.
1.3 Performance Event Category

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

1-3

Transport Platform
1 Overview
Table 1-3 Performance event categories

Performance Event
Category
Definition
Performance event related to

the bit errors of the
regenerator section
The performance event is generated when bit errors occur to

the regenerator section in the SDH frames of the signals on
the WDM side or the client side of the board.

bit errors of the multiplex
section
The performance event is generated when bit errors occur at

the multiplex section in the SDH frames of the signals on the
WDM side or the client side of the board.

bit errors of the higher order
path
The performance event is generated when bit errors occur in

the higher order path.

bit errors of the lower order
path
The performance event is generated when bit errors occur in

the lower order path.

the check and error
correction
The performance event generated when the board performs

service check or bit error correction.
Performance event of pointer

justification
The performance event is generated when the board performs

the pointer justification.

the equipment function
The performance event generated when the optical power, the

working current of the laser or other factors about the running
environment exceed the threshold.
RMON performance event
The performance event related to the mode in which the board

transmits or receives the data packets, the number and quality
of packets in different lengths transmitted or received.
1.4 Alarm Signal Flow

This section describes the alarm signal flow of the OTU. It describes the generation, detection,
and transmission of alarms when the OTU accesses different types of signals.
1.4.1 Overview
This section describes the eight types of scenarios of the alarm signal flow, SF, SD, and basic
concepts in the alarm signal flow diagram.
1.4.2 Non-Convergent OTU Processing Standard SDH Signals
This section describes the alarm signal flow when the non-convergent OTU processes standard
SDH signals.
1.4.3 Non-Convergent OTU Processing Standard OTN Signals
This section describes the alarm signal flow when the non-convergent OTU unit processes
standard OTN signals.
1.4.4 Convergent OTU Processing Standard SDH Signals
1-4

Issue 04 (2010-10-20)

Transport Platform
1 Overview
This section describes the alarm signal flow when the convergent OTU processes standard SDH
signals.
1.4.5 Convergent OTU Processing Standard OTN Signals
This section describes the alarm signal flow when the convergent OTU processes standard OTN
signals.
1.4.6 Regenerating OTU
This section describes the alarm signal flow of the regenerating OTU.
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.
1.4.8 Non-Convergence OTU Board Processing the GE Signals
This topic describes the alarm signal flow when the non-convergence OTU board processes the
GE signals.
1.4.9 Convergence OTU Processing the GE Signals
This topic describes the alarm signal flow when the convergence OTU board processes the GE
signals.
1.4.1 Overview
This section describes the eight types of scenarios of the alarm signal flow, SF, SD, and basic
concepts in the alarm signal flow diagram.
Classification
For a WDM product, the detection and transmission of alarms vary according to the type of the
signals that are accessed into the OTU. The OTU is classified into the following types:
l
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
eight situations are defined in this section:
l
Non-convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the non-convergent OTU processes
standard SDH signals.
Non-convergent OTU processing standard OTN signals

This section describes the alarm signal flow when the non-convergent OTU processes
Convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the convergent OTU processes standard
SDH signals.
Issue 04 (2010-10-20)

1-5

Transport Platform
1 Overview
Convergent OTU processing standard OTN signals

This section describes the alarm signal flow when the convergent OTU processes standard
OTN signals.
Regenerating OTU
OTU with the cross-connect function

This section describes the alarm signal flow of the OTU with the cross-connect function.
Convergent OTU processing GE signals

This section describes the alarm signal flow when the convergent OTU processes GE
signals.
Non-convergent OTU processing GE signals

This section describes the alarm signal flow when the non-convergent OTU processes GE
signals.
SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are trigger
conditions of a protection switching. Whether the SD event is used as a trigger condition,
however, it can be set by the user.
The SF and SD events are marked in the alarm signal flow diagrams in this section. These events
are generated when the equipment configured with network protection detects a certain alarm.
If the equipment is not configured with the network protection, The SF and SD events are not
detected or reported.
Concepts
The following concepts are used in the diagrams in this section:
l
WDM side: It is the WDM side of the OTU.
Client side: it is the client side of the OTU. On the client side, the services from a client
device are accessed.
Middle part: It is the middle part between the WDM side and the client side. It is a virtual
concept, and thus is not displayed on the U2000. This concept is introduced to describe the
alarm detection mechanism.
N#1: It indicates channel 1 at optical interface N on the OTU. For example, the client-side
optical interfaces of the LQM unit are numbered 3, 4, 5, and 6, and the WDM-side optical
interface of the LQM unit is numbered 1. Then, 3#1 indicates channel 1 at client-side optical
interface 3.
1#N: It indicates channel N at WDM-side optical interface 1 on the OTU. For example,
1#3 indicates channel 3 at WDM-side optical interface 1.
1.4.2 Non-Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the non-convergent OTU processes standard
SDH signals.
Figure 1-1 and Figure 1-2 show the alarm signal flows when the non-convergent OTU processes
standard SDH signals.
1-6

Issue 04 (2010-10-20)

Transport Platform
1 Overview
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals
Station A
Client-side
R_LOS
R_LOF
MS_AIS
B1 errors
Station B
WDM-side
WDM-side
REM_SF
R_LOS
REM_SF
R_LOF
Client equipment
Client-side
Client equipment
G_AIS/
SF
REM_SF
R_LOF
SF
REM_SF
R_LOF
MS_AIS
MS_AIS
SD
REM_SD
REM_SD
B1_SD/
B1_EXC
SF
G_AIS
OTUk_AIS
G_AIS
B1 errors
R_LOF
OTUk_BDI&
ODUk_PM_BDI
FAS mismatch
SF
OTUk_LOF
G_AIS
R_LOF
OTUk_BDI&
ODUk_PM_BDI
MFAS mismatch
OTUk_LOM
R_OOF
OTUk_BDI&
ODUk_PM_BDI
Excessive bit
errors before
BEFFEC_EXC
FEC
SM BIP8 errors
OTUk_DEG/
OTUk_EXC
SM_BDI
OTUk_BDI
SFSF event detecting
SDSD event detecting
Insertion Alarm status insertion

Alarm processing
Errors
xxx
Insertion back: Alarm status insertion back

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, OTUk_LOF alarm, SM BIP8 errors and BEFFEC_EXC alarm. The alarm signal flows
of other alarms are similar.
l
Issue 04 (2010-10-20)
R_LOS
1-7

Transport Platform
1 Overview
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 equipment of station B, and the OTU reports the R_LOF alarm to the client
equipment.
l
OTUk_LOF
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 equipment.
SM BIP8 errors
The OTU at station B detects SM BIP 8 errors on the WDM side. When the SM BIP 8
errors exceed the threshold, the OTUk_DEG or OTUk_EXC alarm is generated (the
specific alarm is determined according to the bit error threshold set by the board). The bit
errors are further sent to the downstream client equipment connected to station B. (The bit
errors cannot be sent to the downstream station except that the SM BIP 8 errors are from
the data inside). The alarms related to bit errors are detected in the client equipment.
BEFFEC_EXC
The WDM side of the OTU at station B detects the threshold-crossing of before-FEC bit
errors and generates the BEFFEC_EXC alarm. The alarm is not sent to the downstream
station.
1-8

Issue 04 (2010-10-20)

Transport Platform
1 Overview
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals
Station A
Station B
WDM-side
WDM-side
Client equipment
Client-side
SF
OTUk_TIM
G_AIS
SF
ODUk_PM_AIS
G_AIS
SF
ODUk_PM_LCK
G_AIS
SF
ODUk_PM_OCI
G_AIS
SM_TTI byte mismach
Client equipment
R_LOF
OTUk_BDI&
ODUk_PM_BDI
ODUk_PM_AIS
R_LOF
ODUk_PM_BDI
ODUk_PM_LCK
R_LOF
ODUk_PM_BDI
ODUk_PM_OCI
R_LOF
ODUk_PM_BDI
SD
PM BIP8 errors ODUk_PM_DEG/
ODUk_PM_EXC
SF
PM_TTI byte mismatch
ODUk_PM_TIM
Bit error
G_AIS
R_LOF
ODUk_PM_BDI
ODUk_PM_BDI
ODUk_PM_BDI

Alarm processing
xxx

NOTE
The insertion or insertion back operations represented by dotted lines are performed only after the TIM
follow-up response is enabled.
This section describes the alarm signal flow by analyzing how the OTU processes the
ODUk_PM_AIS and ODUk_PM_BDI alarms. The alarm signal flows of other alarms are
similar.
l
ODUk_PM_AIS
The WDM side of the OTU at station B detects the ODUk_PM_AIS alarm. Then, the OTU
sends the ODUk_PM_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.
ODUk_PM_BDI
The WDM side of the OTU at station B detects the ODUk_PM_BDI alarm. The alarm is
not sent to the downstream station.
Issue 04 (2010-10-20)

1-9

Transport Platform
1 Overview
1.4.3 Non-Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the non-convergent OTU unit processes
Figure 1-3 and Figure 1-4 show the alarm signal flows when the non-convergent OTU processes
NOTE
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals
Station A
Client-side
R_LOS
Station B
WDM-side
WDM-side
Client equipment
Client-side
ODUK_PM_AIS
SF
ODUk_PM_AIS
ODUk_PM_AIS
R_LOS
OTUk_BDI&
ODUk_PM_BDI
ODUK_PM_AIS
OTU k_LOF
OTUk_BDI&
ODUk_PM_BDI
OTU k_ LOM
OTUk_BDI&
ODUk_PM_BDI
OTUk_AIS
Client equipment
OTUk_LOF
SF
ODUk_PM_AIS
OTUk_LOM
ODUK_PM_AIS
SF
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUK_PM_AIS
SF
ODUk_PM_AIS
OTUk_AIS
OTUk_BDI&
ODUk_PM_BDI
SM_TTI byte mismatch
OTUk_TIM
ODUk_PM_AIS
ODUK_PM_AIS
SF
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
PM BIP8 errors
REM_SD
ODUk_PM_DEG/
ODUk_PM_EXC
G_AIS
OTUk_BDI&
ODUk_PM_BDI
FAS mismatch
SF
OTUk_AIS
ODUk_PM_AIS
SF
OTUk_LOF
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
Excessive bit
errors before BEFFEC_EXC
FEC
SM BIP8 errors
OTUk_DEG/
OTUK_EXC
1-10
ODUk_PM_AIS
ODUk_PM_AIS
SM BIP8 errors

Alarm processing
PM BIP8 errors
REM_SD
xxx
Insertion back : Alarm status insertion back


Issue 04 (2010-10-20)

Transport Platform
1 Overview
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 the R_LOS alarm. The OTU sends the
OTUk_BDI and ODUk_PM_BDI alarms back to the upstream client equipment connected
to station A. In addition, the R_LOS alarm is sent to station B. The WDM side of the OTU
at station B detects the ODUk_PM_AIS alarm, and then generates an SF event. The event
triggers a protection switching. The R_LOS alarm is further sent to the downstream client
equipment connected to station B. Then the client equipment detects the ODUk_PM_AIS
alarm.
OTUk_LOF
The WDM side of the OTU at station B detects the OTUk_LOF alarm, and the OTU sends
the OTUk_BDI and ODUk_PM_BDI alarms back to the WDM side of upstream station
A. In addition, the OTUk_LOF alarm is further sent to the downstream station of station
B. After it 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.
The client side of the OTU at station A receives the OTUk_LOF alarm. The OTU sends
the OTUk_BDI and ODUk_PM_BDI alarms back to the upstream client equipment
connected to station A. In addition, the OTUk_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 generates an SF event. The event triggers a protection
switching. The OTUk_LOF alarm is further sent to the downstream client equipment
connected to station B. Then the client equipment detects the ODUk_PM_AIS alarm.
Issue 04 (2010-10-20)

1-11

Transport Platform
1 Overview
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals
Station A
Client-side
Station B
WDM-side
WDM-side
OTUk_BDI
Client-side
Client equipment
Client equipment
OTUk_BDI
MFAS
mismatch
ODUk_PM_AIS
OTUk_LOM
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
SF
OTUk_TIM
SM_TTI byte
mismatch
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
ODUK_PM_AIS
SF
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_BDI
ODUK_PM_LCK
SF
ODUk_PM_LCK
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_BDI
ODUK_PM_OCI
SF
ODUk_PM_OCI
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_BDI
SD
PM BIP8 ODUk_PM_DEG/
ODUk_PM_EXC
PM_TTI
SF
byte mismatch
ODUk_PM_AIS
ODUk_PM_TIM
PM BIP8 errors
ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_BDI
ODUk_PM_BDI

Alarm processing
xxx

OTUk_TIM
After the OTU at station B receives the OTUk_TIM alarm on the WDM side, it does not
send the alarm to the downstream station if the TIM follow-up response is disabled. If the
TIM follow-up response is enabled, an SF event is generated. After the alarm is processed
on the client side of station B, the ODUk_PM_AIS alarm is reported by the client
equipment.
OTUk_BDI
The OTU detects the OTUk_BDI alarm that is sent from the upstream station. This alarm
is not further sent to the downstream station.
l
1-12
ODUk_PM_TIM/ODUk_PM_BDI
Issue 04 (2010-10-20)

Transport Platform
1 Overview
When the TIM follow-up response is disabled, the OTU transparently transmits all PM
alarms.
l
ODUk_PM_AIS/ODUk_PM_LCK/ODUk_PM_OCI
The WDM side of the OTU at station B receives the ODUk_PM_AIS, ODUk_PM_LCK,
or ODUk_PM_OCI alarm. The alarm is further sent to the downstream client equipment
connected to station B. Then the client equipment detects the ODUk_PM_AIS,
ODUk_PM_LCK, or ODUk_PM_OCI alarm.
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 shows the alarm signal flows when the convergent OTU processes standard SDH
signals.
NOTE
Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and thus
is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In
the middle part of the convergent OTU, the optical interface numbers and channel numbers of signals are
reallocated.
NOTE
Issue 04 (2010-10-20)

1-13

Transport Platform
1 Overview
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Station A
Client-side
Station B
Middle
WDM-side
WDM-side
R_LOS
REM_SF
R_LOF
R_LOC
REM_SF
REM_SF
REM_SD
Errors
Client equipment
Client-side
Client equipment
G_AIS
SF
REM_SF
R_LOF
SF
REM_SF
R_LOF
SF
REM_SF
R_LOF
SD
REM_SD
Errors
MS_AIS
MS_AIS
G_AIS
R_LOS/
OTUk_AIS/
OTUk_LOF
SF
R_LOS/
OTUk_AIS/
OTUk_LOF
R_LOF
G_AIS
R_LOF
G_AIS
R_LOF
G_AIS
OTUk_BDI&
ODUk_PM_BDI
R_LOF
G_AIS
ODUk_PM_AIS/
SF
ODUk_PM_LCK/
ODUk_PM_AIS/
ODUk_PM_OCI
ODUk_PM_LCK/
ODUk_PM_OCI
R_LOF
G_AIS
R_LOF
G_AIS
R_LOF
G_AIS
R_LOF
ODUk_PM_BDI
Errors
SD
SM BIP8 errors
Errors
OTUk_DEG/
OTUk_EXC
Errors
Errors
Errors
SD
Errors

ODUk_PM_EXC
Errors
Errors

Alarm processing
xxx

This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
l
One channel of R_LOS signals are accessed on the client side.

The OTU at station A accesses one channel of R_LOS signals on the client side, for
example, channel 1 at optical interface 3. After being processed in the middle part and on
the WDM side of the OTU at station A and the WDM side of station B, the alarm signals
1-14

Issue 04 (2010-10-20)

Transport Platform
1 Overview
are then sent to the downstream station. The REM_SF alarm of channel 1 at optical interface
3 is generated on the client side. The R_LOF alarm is detected in the client equipment.
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.
There is an R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, or

ODUk_PM_LCK alarm 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 back to the WDM side of upstream station
A. In addition, the alarm is further sent to the downstream client side connected to station
B. After the alarm is processed on the client side, the R_LOF alarm is detected in the client
equipment.
There are bit error alarms on the WDM side.

The WDM side of the OTU board at station B accesses and processes the bit error alarms.
In addition, the alarms are further sent to the downstream client side connected to station
B. The alarms can be detected in the client equipment.
An SD event is generated on the WDM side of the OTU at station B. Whether an SD event
serves as the trigger condition of a protection switching can be configured manually.
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-6 and Figure 1-7 show the alarm signal flows when the convergent OTU processes
NOTE
Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and thus
is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In
the middle part of the convergent OTU, the optical interface number and channel number of signals are reallocated.
NOTE
Issue 04 (2010-10-20)

1-15

Transport Platform
1 Overview
Figure 1-6 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
Station A
Client-side
R_LOS
Station B
Middle
WDM-side
WDM-side
R_LOS
ODUk_PM_AIS
SF
ODUk_PM_AIS
REM_SF
OTUk_TIM
SM section
regenerate
OTUk_BDI&
ODUk_PM_BDI
SM BIP8 errors
OTUk_DEG/
OTUk_EXC
OTUk_BDI
OTUk_BDI
ODUk_PM_BDI
SM section
regenerate
REM_SF
SF
ODUk_PM_TIM
ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_AIS/
ODUk_PM_OCI
ODUk_PM_LCK/
ODUk_PM_OCI
PM BIP8 errors
Client equipment
ODUk_PM_AIS
SF
REM_SF
ODUk_PM_AIS
OTUk_LOF/
OTUk_AIS
OTUk_BDI&
ODUk_PM_BDI
Client equipment
Client-side
ODUk_PM_AIS
SF
REM_SF
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
OTUk_LOF/OTUk_AIS
Middle
PM_BIP8 errors
REM_SF
SF
REM_SF
REM_SF
ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
SD
REM_SD
REM_SD
PM_BIP8 errors
ODUk_PM_BDI
ODUk_PM_BDI

Alarm processing
Note 1
xxx

NOTE
The insertion or insertion back operations represented by dotted lines are performed only after the TIM
follow-up response is enabled.
NOTE
At note 1 in the figure, the ODUk_PM_TTI mismatch is reported only when the TTI bytes received by the
equipment in the downstream direction of station B are different from the TTI bytes transmitted by the
equipment in the upstream direction of station A.
l
One channel of R_LOS or OTUk_LOF signals is accessed on the client side.

The OTU at station A accesses one channel of R_LOS or OTUk_LOF signals on the client
side, for example, channel 1 at optical interface 3. After being processed in the middle part
and on the WDM side of the OTU at station A and the WDM side of station B, the alarm
signals are then sent to the downstream station. The REM_SF alarm is generated on the
client side of station B and finally the ODUk_PM_AIS alarm is detected in the client
equipment.
An SF event is generated in the corresponding channel in the middle part of the OTU at
station B, and a protection switching is triggered.
1-16
The OTUk_DEG, OTUk_EXC, OTUk_BDI, or ODUk_PM_BDI alarm is generated on a

client-side channel.
Issue 04 (2010-10-20)

Transport Platform
1 Overview
After the OTU at station A detects the OTUk_DEG, OTUk_EXC, OTUk_BDI, or

ODUk_PM_BDI alarm on the client-side channel, for example, channel 1 at optical
interface 3, the OTU reports the OTUk_DEG, OTUk_EXC, OTUk_BDI, or
ODUk_PM_BDI alarm but does not send the alarm to the downstream station.
Figure 1-7 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
Station A
Client-side
Middle
Station B
WDM-side
WDM-side
Middle
Client equipment
Client-side
Client equipment
ODUk_PM_AIS
R_LOS/
OTUk_AIS/
OTUk_LOF
ODUk_PM_AIS
SF
R_LOS/
OTUk_AIS/
OTUk_LOF
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
ODUk_PM_AIS/
SF
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
ODUk_PM_BDI
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_AIS
SM BIP8 errros
SD
SM BIP8 errors OTUk_DEG/
OTUk_EXC
SM BIP8 errros
SM BIP8 errros
SM BIP8 errros
PM BIP8 errros
SD
PM BIP8 errros
ODUk_PM_EXC
PM BIP8 errros
PM BIP8 errros

Alarm processing
xxx

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.
Issue 04 (2010-10-20)

1-17

Transport Platform
1 Overview
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.
l

The WDM side of the OTU board at station B accesses and processes the bit error alarms.
In addition, the alarms are further sent to the downstream client side connected to station
B and detected by the client equipment.
An SD event is generated on the WDM side of the OTU at station B, and a protection
1.4.6 Regenerating OTU

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

Issue 04 (2010-10-20)

Transport Platform
1 Overview
Figure 1-8 Alarm signal flow of the regenerating OTU

Station A
Station B(REG)
WDM-IN
WDM-side
WDM-OUT
Station C
WDM-side
ODUk_PM_AIS
R_LOS
R_LOS
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
ODUk_PM_AIS
OTUk_AIS
OTUk_AIS
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
ODUk_PM_AIS
OTUk_LOF
ODUk_PM_AIS
OTUk_LOF
OTUk_BDI&
ODUk_PM_BDI
OTUk_TIM
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_BDI&
ODUk_PM_BDI
Excessive bit
errors before FEC
ODUk_PM_AIS
ODUk_PM_OCI
ODUk_PM_LCK
BEFFEC_EXC
ODUk_PM_AIS
ODUk_PM_AIS
ODUk_PM_OCI
ODUk_PM_OCI
ODUk_PM_LCK
ODUk_PM_LCK
ODUk_PM_TIM
ODUk_PM_TIM

ODUk_PM_EXC

Alarm processing
ODUk_PM_DEG/
ODUk_PM_EXC
xxx

NOTE
The insertion or insertion back operations represented by dotted lines are performed only after the TIM followup response is enabled.
In the case of the regenerating OTU, all alarms except the OTUk_LOF and OTUk_AIS alarms
in the SM section are terminated at the local station and are not sent to the downstream station.
Issue 04 (2010-10-20)

1-19

Transport Platform
1 Overview
In the case of the OTUk_LOF and OTUk_AIS alarms, the regenerating OTU inserts the
ODUk_PM_AIS alarm to the downstream station. Other alarms are then sent to the downstream
station, and are reported on the WDM side of the OTU (except that the R_LOS alarm is inserted
with an ODUk_PM_AIS alarm to the downstream station).
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect

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

Issue 04 (2010-10-20)

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

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

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

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

1-21

Transport Platform
1 Overview
1.4.8 Non-Convergence OTU Board Processing the GE Signals

This topic describes the alarm signal flow when the non-convergence OTU board processes the
GE signals.
Figure 1-11 and Figure 1-12 show the alarm signal flows when the non-convergence OTU
board processes the GE signals.
NOTE
The ALS function of the OTU shown in the figure in this section is not enabled.
Figure 1-11 Alarm signal flow when the non-convergence OTU board processes the GE signals
-1
Station A
Client-side
LINK_ERR
Station B
WDM-side
WDM-side
Client equipment
Client-side
Client equipment
NONE
LINK_ERR
LPT=Disable
LINK_ERR
Note 1
LINK_ERR
LINK_ERR
LPT=Enable
R_LOS
FCS_error
G_AIS
SF
REM_SF
R_LOS
LINK_DOWN
REM_SF
FCS_error
FCS_error
SF
G_AIS
OTUk_AIS
Note 1
LINK_DOWN
OTUk_BDI&
ODUk_PM_BDI
SF
OTUk_LOF
FAS mismatch
Note 1
LINK_DOWN
OTUk_BDI&
ODUk_PM_BDI
MFAS mismatch
OTUk_LOM
Note 1
LINK_DOWN
OTUk_BDI&
ODUk_PM_BDI
Excessive bit
BEFFEC_EXC
errors before FEC
SM BIP8 errors
OTUk_DEG/
OTUk_EXC
OTUk_BDI
OTUk_BDI

Alarm processing
FCS_error
xxx

NOTE
In the case of note 1 in the figure, when the LPT is enabled, the LOCAL_FAULT alarm is inserted in
precedence. In other situations, the G-AIS alarm is inserted.
1-22

Issue 04 (2010-10-20)

Transport Platform
1 Overview
This section describes how the OTU board processes the R_LOS alarm and the LINK_ERR
alarm. This is considered as an example to describe the alarm signal flow. The alarm signal flow
of other alarms is similar.
l
R_LOS on the client side

When the R_LOS signal is detected on the client side of the OTU at station A, the R_LOS
alarm is reported on the client side and is then processed on the WDM side. The alarm is
sent to station B and is processed on the WDM side. The client side of station B reports the
REM_SF alarm, which is then sent to the downstream client equipment. The client
equipment detects the LINK_DOWN alarm.
LINK_ERR on the client side

When the LPT is disabled on the client sides of the OTUs at stations A and B and when
the client signals at station A contain the LINK_ERR alarm, the client signals are
transmitted transparently from station A to the WDM side of the OTU at station B.
When the LPT is enabled on the client sides of the OTUs at stations A and B and when the
client signals at station A contain the LINK_ERR alarm, the LOCAL_FAULT alarm is
inserted in precedence and then the fixed mode signals such as the G_AIS alarm are inserted
to the downstream client equipment connected to station B. The client equipment then
reports the LINK_ERR alarm.
Issue 04 (2010-10-20)

1-23

Transport Platform
1 Overview
Figure 1-12 Alarm signal flow when the non-convergence OTU board processes the GE signals
-2
Station A
Client-side
Station B
WDM-side
WDM-side
Client-side
MFAS mismatch
Note 1
OTUk_LOM
OTUk_BDI&
ODUk_PM_BDI
SM_TTI mismatch
Client equipment
Client equipment
LINK_DOWN
SF
OTUk_TIM
LINK_DOWN
OTUk_BDI&
ODUk_PM_BDI
SF
ODUk_PM_AIS
ODUk_PM_AIS
LINK_DOWN
ODUk_PM_BDI
SF
ODUk_PM_LCK
ODUk_PM_LCK
LINK_DOWN
ODUk_PM_BDI
SF
ODUk_PM_OCI
ODUk_PM_OCI
LINK_DOWN
ODUk_PM_BDI
SD
PM_BIP8 ODUk_PM_DEG/
ODUk_PM_EXC
PM_TTI mismatch
SF
ODUk_PM_TIM
LINK_DOWN
ODUk_PM_BDI
ODUk_PM_BDI
ODUk_PM_BDI

Alarm processing
xxx

NOTE
In the case of note 1 in the figure, when the LPT is enabled, the LOCAL_FAULT alarm is inserted in precedence.
In other situations, the G-AIS alarm is inserted.
This section describes how the OTU board processes the OTUk_LOM alarm and the
ODUk_PM_AIS alarm. This is considered as an example to describe the alarm signal flow. The
alarm signal flow of other alarms is similar.
l
OTUk_LOM on the WDM side

After detecting mismatch of the MFAS frame, the WDM side of the OTU at station B
reports the OTUk_LOM alarm and sends the OTUk_BDI and ODUk_PM_BDI alarms back
1-24

Issue 04 (2010-10-20)

Transport Platform
1 Overview
to the WDM side of station A. In addition, the OTUk_LOM alarm is further sent to the
client side of station B. After the alarm is processed on the client side of station B, it is sent
to the downstream client equipment connected to station B. Then the LINK_DOWN alarm
is detected in the client equipment.
l
ODUk_PM_AIS on the WDM side

After detecting the ODUk_PM_AIS alarm, the WDM side of the OTU at station B reports
the ODUk_PM_AIS alarm and sends the ODUk_PM_BDI alarm back to the WDM side
of station A. In addition, the ODUk_PM_AIS alarm is further sent to the client side of
station B. After the alarm is processed on the client side of station B, it is sent to the
downstream client equipment connected to station B. Then the LINK_DOWN alarm is
detected in the client equipment.
An SF event is generated on the WDM side of the OTU board at station B, which triggers
a service channel switching.
1.4.9 Convergence OTU Processing the GE Signals

This topic describes the alarm signal flow when the convergence OTU board processes the GE
signals.
Figure 1-13 show the alarm signal flows when the convergence OTU board processes the GE
signals.
Issue 04 (2010-10-20)

1-25

Transport Platform
1 Overview
Figure 1-13 Alarm signal flow when the convergence OTU board processes the GE signals
Station A
Client-side
Middle
R_LOS
L_SYNC
Station B
WDM-side
WDM-side
REM_SF
REM_SF
Client equipment
Client-side
Client equipment
G_AIS
SF
REM_SF
LINK_DOWN
SF
REM_SF
LINK_DOWN
FCS_error
Errors
10B_error
R_LOS/
OTUk_AIS/
OTUk_LOF
SF
R_LOS/
OTUk_AIS/
OTUk_LOF
10B_error
10B_error
LINK_DOWN
LINK_DOWN
LINK_DOWN
10B_error
LINK_DOWN
OTUk_BDI&
ODUk_PM_BDI
ODUk_PM_AIS/
SF
ODUk_PM_LCK/
OTUk_PM_OCI ODUk_PM_AIS/
ODUk_PM_LCK/
OTUk_PM_OCI
10B_error
10B_error
10B_error
LINK_DOWN
LINK_DOWN
LINK_DOWN
10B_error
LINK_DOWN
ODUk_PM_BDI
SM BIP8 errors
Errors
SD
Errors
OTUk_DEG/
OTUk_EXC
Errors
Errors
Errors
SD

OTUk_PM_EXC
Errors
Errors
Errors

Alarm processing
xxx

There is an R_LOS or L_SYNC alarm on the client side.

The client side of the OTU at station A accesses and processes the alarm. The alarm is
further sent to station B. The REM_SF alarm is generated on the client side of station B.
The client equipment detects the LINK_DOWN alarm.
An SF event is generated on the client side of the OTU at station B, which triggers a service
channel switching.
There is a FCS_error alarm on the client side.

The client side of the OTU at station A accesses and processes the alarm. The alarm is
further sent to the downstream. The client equipment detects bit errors.
1-26
There is an R_LOS, OTUk_LOF, OTUk_AIS, ODUK_PM_AIS, ODUk_PM_OCI,

ODUk_PM_LCK, or ODUk_PM_AIS alarm on the WDM side.
Issue 04 (2010-10-20)

Transport Platform
1 Overview
The WDM side of the OTU at station B accesses and processes the alarm. The OTU sends
the OTUk_BDI or ODUk_PM_BDI alarm back to the WDM side of upstream station A.
In addition, the alarm is further sent to the client side of station B. After the alarm is
processed on the client side, the LINK_DOWN alarm is detected in the client equipment.
An SF event is generated on the WDM side of the OTU at station B, which triggers a service
channel switching.
l

The WDM side of the OTU at station B accesses and processes the bit error alarms. In
addition, the alarms are further sent to the downstream client side connected to station B
and detected by the client equipment.
An SD event is generated on the WDM side of the OTU at station B. Whether an SD event
serves as the trigger condition of a protection switching can be configured manually.
1.5 Suppression Relation of Alarms

This section describes the rules of alarm suppression and provides the suppression relation figure
of common alarms. The efficiency for handling the alarms can be enhanced due to the alarm
suppression.
When the equipment is faulty, several alarms may be generated by the same optical interface.
However, some alarms are not important for the maintenance engineer. For example, when the
signal is lost, the optical interface generates the R_LOS alarm accompanied with the alarm
indiating 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 interface.
The rules of alarm suppression are as follows:
l
The client-side alarms and the WDM-side alarms are relatively independent. There are no
alarm suppression relation between the client-side alarms and the WDM-side alarms.
There is no alarm suppression relation between the detection alarms related to the board
hardware and the service alarms.
NOTE
Some alarms for the optical module are exceptional. For example, the R_LOS alarm suppresses the
IN_PWR_LOW alarm.
There is no alarm suppression relation for the alarms that cannot be generated at the same
time.
1.5.1 Suppression of OTN Alarms

1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment Alarms
1.5.1 Suppression of OTN Alarms

The suppression of OTN alarms is shown in theFigure 1-14.
The alarm above the arrow suppresses the alarm below the arrow. For example, the OTUk_LOM
alarm suppresses the OTUk_TIM alarm.
Issue 04 (2010-10-20)

1-27

Transport Platform
1 Overview
Figure 1-14 Suppression of OTN alarms

OCH_LOS
OTUk_LOF
OTUk_LOM
OTUk_SSF
OTUk_TIM
OTUk_BDI
ODUk_LOFLOM
ODUk_TCMn_LTC/
ODUk_TCMn_LCK/
ODUk_TCMn_OCI
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_DEG
ODUk_TCMn_SSF
ODUk_TCMn_TIM
ODUk_TCMn_BDI
ODUk_TCMn_DEG
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_SSF
ODUk_PM_TIM
ODUk_PM_BDI
ODUk_PM_DEG
OPUk_PLM
OPUk_MISM
1-28

Issue 04 (2010-10-20)

Transport Platform
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 as shown in Figure 1-15.
The alarm above the arrow suppresses the alarm below the arrow. For example, when an optical
interface on the client side loses signals, the optical interface only reports the R_LOS alarm. The
R_LOC and R_LOF alarms are not reported.
Issue 04 (2010-10-20)

1-29

Transport Platform
1 Overview
Figure 1-15 Suppression of alarms related to SDH services and other common equipment alarms
PORT_MODULE_OF
FLINE
LSR_COOL_ALM
TEM_HA/TEM_LA
TF
OUT_PWR_HIGH
IN_PWR_HIGH/
LSR_WILL_DIE
TD
OUT_PWR_LOW
R_LOS
IN_PWR_LOW
R_LOC
R_LOF
BEFFEC_EXC
J0_MM
MS_REI
B2_EXC
B1_EXC
B1_SD
MS_RDI
MS_AIS
AU_LOP
AU_AIS
HP_RDI
HP_REI
HP_TIM
B3_EXC
HP_UNEQ
B3_SD
HP_SLM
LP_REI
BIP_SD
HP_LOM
LP_RDI
TU_LOP
LP_RFI
TU_AIS
LP_UNEQ
BIP_SD
1-30
B2_SD
BIP_EXC

LP_TIM
LP_SLM
Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
Alarm List
About This Chapter

This chapter describes the alphabetical lists of alarms and lists alarms of every board.
2.1 Product Alarm List
This section lists the alarms supported by the product in alphabetical order.
2.2 Board Alarm List
Lists the alarms of every board.
Issue 04 (2010-10-20)

2-1

Transport Platform
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.
2.1.2 Alarm List B
This section used a table to list the alarms starting with B.
2.1.3 Alarm List C
This section used a table to list the alarms starting with C.
2.1.4 Alarm List D
This section used a table to list the alarms starting with D.
2.1.5 Alarm List E
This section used a table to list the alarms starting with E.
2.1.6 Alarm List F
This section used a table to list the alarms starting with F.
2.1.7 Alarm List G
This section used a table to list the alarms starting with G.
2.1.8 Alarm List H
This section used a table to list the alarms starting with H.
2.1.9 Alarm List I
This section used a table to list the alarms starting with I.
2.1.10 Alarm List J
This section used a table to list the alarms starting with J.
2.1.11 Alarm List L
This section used a table to list the alarms starting with L.
2.1.12 Alarm List M
This section used a table to list the alarms starting with M.
2.1.13 Alarm List N
This section used a table to list the alarms starting with N.
2.1.14 Alarm List O
This section used a table to list the alarms starting with O.
2.1.15 Alarm List P
This section used a table to list the alarms starting with P.
2.1.16 Alarm List R
This section used a table to list the alarms starting with R.
2.1.17 Alarm List S
This section used a table to list the alarms starting with S.
2.1.18 Alarm List T
This section used a table to list the alarms starting with T.
2.1.19 Alarm List U
2-2

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
This section used a table to list the alarms starting with U.

2.1.20 Alarm List V
This section used a table to list the alarms starting with V.
2.1.21 Alarm List W
This section used a table to list the alarms starting with W.
2.1.1 Alarm List A

This section used a table to list the alarms starting with A.
Name
Description
Level
Board
AD_CHECK_FAIL
AD (analog to digital
converter) self check
failure
Major
OLP, OPU
ALM_DATA_RLOS
Receiving data lost on the

Ethernet port
Minor
LDE, LDGF, LDGF2,

LSX, LOE, LQG, LQM,
LQM2
ALM_DATA_TLOS
Transmitting data lost on

the Ethernet port
Minor
LDE, LDGF, LDGF2,

LSX, LOE, LQG, LQM,
LQM2
AU_AIS
AU alarm indication signal
Major
TSP
AU_LOP
AU loss of pointer
Major
TSP
2.1.2 Alarm List B

This section used a table to list the alarms starting with B.
Issue 04 (2010-10-20)
Name
Description
Level
Board
B1_EXC
Regenerator section (B1)

excessive errors
Minor
LQG, LQM, LQM2,

LQPL, LQPU, LSX,
TSP
B1_SD
Regenerator section(B1)
signal degraded
Minor
LQG, LQM, LQM2,

LQPL, LQPU, LSX,
TSP
B2_EXC
Multiplex section (B2)

excessive errors
Major
TSP
B2_SD
Multiplex section (B2)

signal degraded
Minor
TSP
B3_EXC
The number of higher

order path B3 bit errors in
the signals received on the
line exceeds the threshold
Major
TSP

2-3

Transport Platform
2 Alarm List
Name
Description
Level
Board
B3_SD
The higher order path B3

signals received on the line
are degraded.
Minor
TSP
BD_STATUS
Board is not in position
Major
All Boards
BEFFEC_EXC
Signal excessive errors

before FEC alarm
Minor
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPU, LSX
BOOTROM_BAD
BOOTROM data check

failed alarm
Major
SCC
2.1.3 Alarm List C

This section used a table to list the alarms starting with C.
Name
Description
Level
Board
CFG_VERIFY
Configuration is not
verified
Major
SCC
CFGDATA_OUTRAN
GE
Board configuration data

out of range alarm
Major
SCC
2.1.4 Alarm List D

This section used a table to list the alarms starting with D.
Name
Description
Level
Board
DBMS_ERROR
Database error
Major
SCC
DBMS_PROTECT_MO
DE
Database in protect mode
Critical
SCC
DCC_CHAN_LACK
Insufficient DCC channels

alarm
Major
SCC
DOWN_E1_AIS
E1 down signal alarm

indication
Minor
TSP
2.1.5 Alarm List E

This section used a table to list the alarms starting with E.
2-4

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
Name
Description
Level
Board
E1_LOC
Loss of clock in up signal
Major
TSP
ETH_LINK_DOWN
Failure of network
interface connection
Critical
SCC
EXT_SYNC_LOS
Loss of external
synchronous source
Critical
TSP
2.1.6 Alarm List F

This section used a table to list the alarms starting with F.
Name
Description
Level
Board
FAN_FAIL
Fan failed
Major
FAN
FEC_LOF
Loss of FEC frame
Critical
LQG
FEC_OOF
Out of FEC frame
Critical
LQG
FPGA_ABN
FPGA status is abnormal
Major
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, OLP,
OPU, TSP
FUSE_ALARM
Output offline alarm
Critical
SCC
2.1.7 Alarm List G

This section used a table to list the alarms starting with G.
Issue 04 (2010-10-20)
Name
Description
Level
Board
GPON_DS_LOF
LOF is generated in the

downlink GPON services
Critical
LQPL, LQPU, LSPL,

LSPR, LSPU
GPON_RUF
Registration of a board
fails and the distance from
the board to an OLT is not
measured.
Critical
LQPU, LSPR, LSPU
GPON_US_LOF
LOF is generated in the

uplink GPON services
Critical
LQPL

2-5

Transport Platform
2 Alarm List
2.1.8 Alarm List H

This section used a table to list the alarms starting with H.
Name
Description
Level
Board
HARD_BAD
Hardware failed
Critical
SCC
HP_LOM
Higher order path loss of

multiframe
Major
TSP
HP_RDI
Higher order path remote

defect indication
Minor
TSP
HP_SLM
Higher order path signal

identification mismatch
Minor
TSP
HP_TIM
Higher order path tracking

Minor
TSP
HP_UNEQ
No loading error in the

higher order path
Minor
TSP
2.1.9 Alarm List I

This section used a table to list the alarms starting with I.
Name
Description
Level
Board
IN_PWR_HIGH
Input power is too high
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, SCC,
OPU, TSP
IN_PWR_LOW
Input power is too low
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, SCC,
OPU, TSP
2.1.10 Alarm List J

This section used a table to list the alarms starting with J.
2-6

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
Name
Description
Level
Board
J0_MM
J0 byte/trace indicator
mismatch
Minor
LQG, LQM, LQM2,

LQPL, LQPU, LSX,
TSP
2.1.11 Alarm List L

This section used a table to list the alarms starting with L.
Issue 04 (2010-10-20)
Name
Description
Level
Board
LASER_MOD_ERR_E
X
The optical module rate is

mismatch
Major
LQM, LQM2, LDGF,

LDGF2, LWX2, LQG,
LDE, LSPU, LSPL,
LSPR, LSX, LQPU,
LQPL, TSP, LOE
LASER_MODULE_MI
SMATCH
Optical module mismatch

alarm
Major
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, SCC, TSP
LCS_DAYS_OF_GRA
CE
License in keepalive
period
Major
SCC
LCS_EXPIRED
License expired
Critical
SCC
LCS_FILE_NOT_EXIST
No license file
Critical
SCC
LINK_ERR
Link status abnormality
Critical
LDGF, LDGF2, LOE,

LQG, LQM, LQM2,
LSX
LOCAL_FAULT
Local fault alarm
Minor
LSX
LOOP_ALM
Indication of loop
operating
Minor
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSX, LWX2, TSP
LP_RDI
Lower order path remote

defect indication
Minor
TSP
LP_REI

error indication
Minor
TSP
LP_RFI

failure indication
Minor
TSP
LP_SLM
Lower order path signal

label mismatch
Minor
TSP

2-7

Transport Platform
2 Alarm List
Name
Description
Level
Board
LP_TIM
Lower order path tracking

Minor
TSP
LP_UNEQ
Lower order path

unequipped
Minor
TSP
LSR_COOL_ALM
the cooling current of the

laser crosses the threshold
Major
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, TSP
LSR_WILL_DIE
Laser will be out of work
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, SCC,
OPU, TSP
L_SYNC
Loss of synchronization
alarm
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2
2.1.12 Alarm List M

This section used a table to list the alarms starting with M.
2-8
Name
Description
Level
Board
MDL_ALARM
Power module alarm.
Major
SCC
MSSW_DIFFERENT
Working and protection

software difference
between alarm
Critical
SCC
MS_AIS
Multiplex section alarm

indication signal
Major
LQG, LQM, LQM2,

LQPL, LQPU, LSX,
TSP
MS_RDI
Multiplex section remote

defect indication
Minor
LQG, TSP
MS_REI
Bit errors occur at the

remote end of the
multiplex section
Warnin
g
TSP
MUT_LOS
Loss of multiplexed
signals
Critical
OLP, OPU

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
2.1.13 Alarm List N

This section used a table to list the alarms starting with N.
Name
Description
Level
Board
NESTATE_INSTALL
NE is in install state
Critical
SCC
NEBD_XC_DIF
Crossing data of NE and

board different
Major
SCC
NO_BD_PARA
No board parameter
Critical
OLP, OPU
NO_BD_SOFT
No board software
Critical
All Boards
2.1.14 Alarm List O

This section used a table to list the alarms starting with O.
Issue 04 (2010-10-20)
Name
Description
Leve
l
Board
OA_LOW_GAIN
Optical amplifier signal

gain low
Critic
al
OPU
ODU0_LOFLOM
The FAS and MFAS are

abnormal
Critic
al
LDE
ODU0_PM_AIS
ODU0 PM alarm
indication signal
Major
LDE
ODU0_PM_BDI
ODU0 PM backward
defect indication
Mino
r
LDE
ODU0_PM_DEG
ODU0 PM signal
degraded
Mino
r
LDE
ODU0_PM_LCK
ODU0 PM signal locked
Mino
r
LDE
ODU0_PM_OCI
ODU0 PM open
connection indication
Mino
r
LDE
ODU0_PM_TIM
ODU0 PM section TTI

mismatch
Mino
r
LDE
ODU1_PM_AIS
ODU1 PM alarm
indication signal
Major
LDE, LDGF, LDGF2, LQM,

LQM2, LQPL, LQPU, LSPL,
LSPU
ODU1_PM_BDI
ODU1 PM backward
defect indication
Mino
r

LSPU

2-9

Transport Platform
2 Alarm List
2-10
Name
Description
Leve
l
Board
ODU1_PM_DEG
ODU1 PM signal
degraded
Mino
r

LSPU
ODU1_PM_EXC
ODU1 PM section BIP8

excessive error defect
Major

LSPU
ODU1_PM_LCK
Mino
r

LSPU
ODU1_PM_OCI
ODU1 PM open
Mino
r

LSPU
ODU1_PM_TIM
ODU1 PM section TTI

mismatch
Mino
r

LSPU
ODU2_PM_AIS
ODU2 PM alarm
indication signal
Major
LOE, LQPL, LQPU, LSX
ODU2_PM_BDI
ODU2 PM backward
defect indication
Mino
r
ODU2_PM_DEG
ODU2 PM signal
degraded
Mino
r
ODU2_PM_EXC
ODU2 PM section BIP8

Mino
r
ODU2_PM_LCK
Mino
r
ODU2_PM_OCI
ODU2 PM open
Mino
r
ODU2_PM_TIM
ODU2 PM section TTI

mismatch
Mino
r
ODU5G_PM_AIS
ODU5G PM alarm
indication signal
Major
LQG
ODU5G_PM_BDI
ODU5G PM backward
defect indication
Mino
r
LQG
ODU5G_PM_DEG
ODU5G PM signal
degraded
Mino
r
LQG
ODU5G_PM_EXC
ODU5G PM section BIP8

Major
LQG

Issue 04 (2010-10-20)

Transport Platform
Issue 04 (2010-10-20)
2 Alarm List
Name
Description
Leve
l
Board
ODU5G_PM_LCK
ODU5G PM signal locked
Mino
r
LQG
ODU5G_PM_OCI
ODU5G PM open
Mino
r
LQG
ODU5G_PM_TIM
ODU5G PM section TTI

mismatch
Mino
r
LQG
ONU_OFFLINE
ONU offline alarm
Critic
al
LQPU, LSPU, LSPR
ONU_LOSI
ONU LOSI alarm
Critic
al
LQPU, LSPU, LSPR
ONU_LOFI
ONU LOFI alarm
Critic
al
LQPU, LSPU, LSPR
OOL
The phase-locked loop is

out of lock
Major
TSP
OPS_MAIN_BAK_
ATTR_DIFF
Attribute difference
between working and
protection channel
Critic
al
SCC
OPS_PS_INDI
Indication of optical
channel protection
switching
Major
SCC
OPS_STA_INDI
Optical protection status

indication
Major
LDE, LDGF, LDGF2, LOE,

LQG, LQM, LQM2, LQPL,
LQPU, LSPL, LSPU, LSX,
LWX2, OLP, TSP
OSC_LOS
Loss of signal on receiving

line.
Critic
al
SCC
OPU0_PLM
OPU0 payload mismatch
Mino
r
LDE
OPU1_PLM
Mino
r

LQM2, LSPL, LSPU
OPU2_PLM
Mino
r
OPU5G_PLM
OPU5G payload
mismatch
Mino
r
LQG
OTU1_AIS
OTU1 alarm indication

signal
Major

LSPU

2-11

Transport Platform
2 Alarm List
2-12
Name
Description
Leve
l
Board
OTU1_BDI
OTU1 backward defect

indication
Mino
r

LSPU
OTU1_DEG
OTU1 signal degraded
Mino
r

LSPU
OTU1_EXC
OTU1 section BIP8

Major

LSPU
OTU1_LOF
Loss of OTU1 frame
Critic
al

LSPU
OTU1_LOM
Loss of OTU1 multiframe
Major

LSPU
OTU1_TIM
OTU1 section TTI

mismatch
Mino
r

LSPU
OTU2_AIS
OTU2 alarm indication

signal
Major
OTU2_BDI
OTU2 backward defect

indication
Mino
r
OTU2_DEG
OTU2 signal degraded
Mino
r
OTU2_EXC
OTU2 section BIP8

Major
OTU2_LOF
Loss of OTU2 frame
Critic
al
OTU2_LOM
Loss of OTU2 multiframe
Major
OTU2_TIM
OTU2 section TTI

mismatch
Mino
r
OTU5G_AIS
OTU5G alarm indication

signal
Major
LQG
OTU5G_BDI
OTU5G backward defect

indication
Mino
r
LQG
OTU5G_DEG
OTU5G signal degraded
Mino
r
LQG

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
Name
Description
Leve
l
Board
OTU5G_EXC
OTU5G section BIP8

Major
LQG
OTU5G_LOF
Loss of OTU5G frame
Critic
al
LQG
OTU5G_LOM
Loss of OTU5G
multiframe
Major
LQG
OTU5G_TIM
OTU5G section TTI

mismatch
Mino
r
LQG
OUT_PWR_HIGH
Output power is too high
Major

LQPU, LSPL, LSPR, LSPU,
LSX, LWX2, SCC, TSP
OUT_PWR_LOW
Output power is too low
Major

LSX, LWX2, SCC, TSP
2.1.15 Alarm List P

This section used a table to list the alarms starting with P.
Issue 04 (2010-10-20)
Name
Description
Level
Board
PATCH_ERR
Patch error
Major
SCC
PATCH_NOT_CONFIRM
Actived patch has not been

confirmed overtime
Major
SCC
PATCHFILE_NOTEXIST
The patch file does not

exist
Major
SCC
PATCH_DEACT_TIME
OUT
Duration of patch package

in deactivation state too
long.
Major
SCC
PATCH_ACT_TIMEOUT
Duration of patch package

in activation state too long.
Major
SCC
PATCH_PKGERR
Patch package file error
Major
SCC
PORT_MODULE_OFFLINE
Port module offline
Major
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, OPU, LWX2,
SCC, TSP

2-13

Transport Platform
2 Alarm List
Name
Description
Level
Board
POWER_DIFF_DEFECT
Power difference between

monitored working and
protection channels
Minor
OLP
POWER_DIFF_OVER
Power difference between

monitored working and
protection channels
crosses the upper threshold
Major
OLP
POWER_FAIL
Board's power failure
Major
APIU, FAN, LDE,

LDGF, LDGF2, LOE,
LQG, LQM, LQM2,
LQPL, LQPU, LSPL,
LSPR, LSPU, LSX,
LWX2, OLP, OPU,
PIU, SCC, TSP
PRBS_LSS
Loss of PRBS (PseudoRandom Binary

Sequence) signal.
Minor
LDE, LQG, LQM2,

LQPL, LQPU, LSX,
LWX2, LOE, LSX, TSP
PUM_BCM_ALM
Working current of pump

laser over threshold
Major
OPU
PUMP_COOL_EXC
Cool current of pump laser

over threshold
Critical
OPU
PUM_TEM_ALM
Working temperature of
the pump laser exceeds the
threshold
Major
OPU
PWR_MAJ_ALM
Abnormal power supply

(severe overload or
shortage).
Critical
SCC
2.1.16 Alarm List R

This section used a table to list the alarms starting with R.
2-14
Name
Description
Level
Board
R_LOC
Loss of clock on receiving

line
Critical
LWX2
R_LOF
Loss of frame
Critical
LQM, LQM2, LQPL,

LQPU, LQG, LSX, TSP

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
Name
Description
Level
Board
R_LOS
Loss of signal
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, OLP, TSP
REALY_ALARM_CRI
TICAL
Critical relay alarm
Critical
SCC
REALY_ALARM_MAJOR
Major relay alarm
Major
SCC
REALY_ALARM_MINOR
Minor relay alarm
Minor
SCC
REALY_ALARM_IGNORE
Warning relay alarm
Warnin
g
SCC
REMOTE_FAULT
Remote fault alarm
Minor
LSX
REM_SF
Remote client-side service

unloaded alarm
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPU, LSX
REM_SD
Remote signal degraded

alarm
Critical
LQM, LQM2, LQPL,

LQPU, LSX
2.1.17 Alarm List S

This section used a table to list the alarms starting with S.
Issue 04 (2010-10-20)
Name
Description
Level
Board
S1_SYN_CHANGE
Reference source change

in S1 mode
Major
TSP
SECU_ALM
Security alarm
Major
SCC
STORM_CUR_QUENU
M_OVER
Alarm Storm
Minor
SCC
SUB_RACK_OFFLINE
Slave subrack offline

alarm
Critical
SCC
SUBRACK_ID_CONFLICT
Conflict of subrack ID
Critical
SCC
SUBRACK_TYPE_MIS
MATCH
The configured subrack

does not match the
physical subrack
Major
SCC

2-15

Transport Platform
2 Alarm List
Name
Description
Level
Board
SWDL_ACTIVATED_
TIMEOUT
Activation time out
Critical
SCC
SWDL_AUTOMATCH
_INH
Automatic match inhibited
Minor
SCC
SWDL_CHGMNG_NOMATCH
SCC software and board

software mismatch alarm
Critical
SCC
SWDL_COMMIT_FAI
L
Commit failure alarm
Minor
SCC
SWDL_INPROCESS
NE is loading package
Warnin
g
SCC
SWDL_NEPKGCHECK
Loss of file
Critical
SCC
SWDL_PKG_NOBDSOFT
No matching board
software alarm
Minor
SCC
SWDL_PKGVER_MM
Package version
conformance check failed
Minor
SCC
SWDL_ROLLBACK_F
AIL
NE rollback failed
Minor
SCC
SYNC_C_LOS
Synchronous source level

loss
Warnin
g
TSP
SYSLOG_COMM_FAI
L
NE and syslog server

communication failed
Major
SCC
2.1.18 Alarm List T

This section used a table to list the alarms starting with T.
2-16
Name
Description
Level
Board
TD
Transmitter degrade
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, OPU, TSP
TEMP_OVER
Working temperature over

threshold
Major
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, OLP,
OPU, SCC, TSP

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
Name
Description
Level
Board
TF
Transmission failure
Critical
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, LWX2, TSP
THUNDERALM
Thunder protection circuit

failure
Minor
PIU
TEM_HA
Laser temperature is too

high.
Major
TEM_LA
Laser temperature is too

low.
Major
LDE, SCC, LQM,

LQM2, LQPL, LQPU,
LDGF, LDGF2, LQG,
LWX2, LOE, LSPL,
LSPU, LSPR, LSX, TSP
TEMP_ALARM
The temperature threshold

crossing alarm.
Minor
SCC
TU_AIS
TU alarm indication
Major
TSP
TU_LOP
TU loss of pointer
Major
TSP
2.1.19 Alarm List U

This section used a table to list the alarms starting with U.
Name
Description
Level
Board
UP_E1_AIS
E1 signal alarm indication
Minor
TSP
2.1.20 Alarm List V

This section used a table to list the alarms starting with V.
Name
Description
Level
Board
VCXO_LOC
Local oscillator loss of

clock
Major
LDE, LDGF, LDGF2,

LOE, LQG, LQM,
LQM2, LQPL, LQPU,
LSPL, LSPR, LSPU,
LSX, TSP
2.1.21 Alarm List W

This section used a table to list the alarms starting with W.
Issue 04 (2010-10-20)

2-17

Transport Platform
2 Alarm List
Name
Description
Level
Board
WRG_BD_TYPE
Physical board is
mismatched with
configured board
Major
All Boards (except SCC

board)
2.2 Board Alarm List

Lists the alarms of every board.
2.2.1 APIU Board Alarm List
2.2.2 DMD1/DMD1S Board Alarm List
2.2.4 FAN Board Alarm List
2.2.5 FIU Board Alarm List
2.2.6 LDE Board Alarm List
2.2.7 LDGF Board Alarm List
2.2.8 LDGF2 Board Alarm List
2.2.9 LOE Board Alarm List
2.2.10 LQG Board Alarm List
2.2.11 LQM Board Alarm List
2.2.12 LQM2 Board Alarm List
2.2.13 LQPL Board Alarm List
2.2.14 LQPU Board Alarm List
2.2.15 LSPL Board Alarm List
2.2.16 LSPR Board Alarm List
2.2.17 LSPU Board Alarm List
2.2.18 LSX Board Alarm List
2.2.19 LWX2 Board Alarm List
2.2.20 MD8/MD8S Board Alarm List
2.2.21 MR1/MR1S Board Alarm List
2.2.24 MR8 Board Alarm List
2.2.25 OLP Board Alarm List
2.2.26 OPU Board Alarm List
2-18

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
2.2.27 PIU Board Alarm List

2.2.28 SBM1 Board Alarm List
2.2.32 SCC Board Alarm List
2.2.33 SCS Board Alarm List
2.2.34 TSP Board Alarm List
2.2.1 APIU Board Alarm List

BD_STATUS
POWER_FAIL
PWR_TEMP_OVERTH
NO_BD_SOFT
POWER_MODULE_OFFLINE
WRG_BD_TYPE

BD_STATUS
WRG_BD_TYPE
NO_BD_SOFT

BD_STATUS
WRG_BD_TYPE
NO_BD_SOFT
2.2.4 FAN Board Alarm List

BD_STATUS
FAN_FAIL
NO_BD_SOFT
2.2.5 FIU Board Alarm List

BD_STATUS
Issue 04 (2010-10-20)
WRG_BD_TYPE

NO_BD_SOFT
2-19

Transport Platform
2 Alarm List
2.2.6 LDE Board Alarm List

ALM_DATA_RLOS
ODU0_PM_LCK
OTU1_LOM
ALM_DATA_TLOS
ODU0_PM_OCI
OTU1_TIM
BD_STATUS
ODU0_PM_TIM
OUT_PWR_HIGH
BEFFEC_EXC
ODU1_PM_AIS
OUT_PWR_LOW
FPGA_ABN
ODU1_PM_BDI
PORT_MODULE_OFFLINE
IN_PWR_HIGH
ODU1_PM_DEG
POWER_FAIL
IN_PWR_LOW
ODU1_PM_EXC
PRBS_LSS
LASER_MODULE_MISMATCH
ODU1_PM_LCK
REM_SF
LASER_MOD_ERR_EX
ODU1_PM_OCI
R_LOS
LOOP_ALM
ODU1_PM_TIM
TD
LSR_COOL_ALM
OPS_STA_INDI
TEMP_OVER
LSR_WILL_DIE
OPU0_PLM
TEM_HA
L_SYNC
OPU1_PLM
TEM_LA
NO_BD_SOFT
OTU1_AIS
TF
ODU0_LOFLOM
OTU1_BDI
VCXO_LOC
ODU0_PM_AIS
OTU1_DEG
WRG_BD_TYPE
ODU0_PM_BDI
OTU1_EXC
ODU0_PM_DEG
OTU1_LOF
2.2.7 LDGF Board Alarm List
2-20
ALM_DATA_RLOS
ODU1_PM_AIS
OTU1_TIM
ALM_DATA_TLOS
ODU1_PM_BDI
OUT_PWR_HIGH
BD_STATUS
ODU1_PM_DEG
OUT_PWR_LOW
BEFFEC_EXC
ODU1_PM_EXC
PORT_MODULE_OFFLINE
FPGA_ABN
ODU1_PM_LCK
POWER_FAIL
IN_PWR_HIGH
ODU1_PM_OCI
REM_SF
IN_PWR_LOW
ODU1_PM_TIM
R_LOS

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
LASER_MOD_ERR_EX
OPS_STA_INDI
TD
OPU1_PLM
TEMP_OVER
LINK_ERR
OTU1_AIS
TEM_HA
LOOP_ALM
OTU1_BDI
TEM_LA
LSR_COOL_ALM
OTU1_DEG
TF
LSR_WILL_DIE
OTU1_EXC
VCXO_LOC
L_SYNC
OTU1_LOF
WRG_BD_TYPE
NO_BD_SOFT
OTU1_LOM
2.2.8 LDGF2 Board Alarm List
Issue 04 (2010-10-20)
ALM_DATA_RLOS
ODU1_PM_BDI
OUT_PWR_HIGH
ALM_DATA_TLOS
ODU1_PM_DEG
OUT_PWR_LOW
BD_STATUS
ODU1_PM_EXC
PORT_MODULE_OFFLINE
BEFFEC_EXC
ODU1_PM_LCK
POWER_FAIL
FPGA_ABN
ODU1_PM_OCI
REM_SF
IN_PWR_HIGH
ODU1_PM_TIM
R_LOS
IN_PWR_LOW
OPS_STA_INDI
TD
LASER_MOD_ERR_EX
OPU1_PLM
TEMP_OVER
OTU1_AIS
TEM_HA
LINK_ERR
OTU1_BDI
TEM_LA
LOOP_ALM
OTU1_DEG
TF
LSR_WILL_DIE
OTU1_EXC
VCXO_LOC
L_SYNC
OTU1_LOF
WRG_BD_TYPE
NO_BD_SOFT
OTU1_LOM
ODU1_PM_AIS
OTU1_TIM

2-21

Transport Platform
2 Alarm List
2.2.9 LOE Board Alarm List

ALM_DATA_RLOS
ODU2_PM_AIS
OTU2_TIM
ALM_DATA_TLOS
ODU2_PM_BDI
OUT_PWR_HIGH
BD_STATUS
ODU2_PM_DEG
OUT_PWR_LOW
BEFFEC_EXC
ODU2_PM_EXC
PORT_MODULE_OFFLINE
FPGA_ABN
ODU2_PM_LCK
POWER_FAIL
IN_PWR_HIGH
ODU2_PM_OCI
PRBS_LSS
IN_PWR_LOW
ODU2_PM_TIM
REM_SF
LASER_MOD_ERR_EX
OPS_STA_INDI
R_LOS
OPU2_PLM
TD
LINK_ERR
OTU2_AIS
TEMP_OVER
LOOP_ALM
OTU2_BDI
TEM_HA
LSR_COOL_ALM
OTU2_DEG
TEM_LA
LSR_WILL_DIE
OTU2_EXC
TF
L_SYNC
OTU2_LOF
VCXO_LOC
NO_BD_SOFT
OTU2_LOM
WRG_BD_TYPE
ALM_DATA_RLOS
L_SYNC
OTU5G_LOM
ALM_DATA_TLOS
MS_AIS
OTU5G_TIM
B1_EXC
MS_RDI
OUT_PWR_HIGH
B1_SD
NO_BD_SOFT
OUT_PWR_LOW
BD_STATUS
ODU5G_PM_AIS
PORT_MODULE_OFFLINE
BEFFEC_EXC
ODU5G_PM_BDI
POWER_FAIL
FEC_LOF
ODU5G_PM_DEG
REM_SF
FEC_OOF
ODU5G_PM_EXC
R_LOF
FPGA_ABN
ODU5G_PM_LCK
R_LOS
IN_PWR_HIGH
ODU5G_PM_OCI
TD
2.2.10 LQG Board Alarm List
2-22

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
IN_PWR_LOW
ODU5G_PM_TIM
TEMP_OVER
J0_MM
OPS_STA_INDI
TEM_HA
LASER_MOD_ERR_EX
OPU5G_PLM
TEM_LA
OTU5G_AIS
TF
LINK_ERR
OTU5G_BDI
VCXO_LOC
LOOP_ALM
OTU5G_DEG
WRG_BD_TYPE
LSR_COOL_ALM
OTU5G_EXC
LSR_WILL_DIE
OTU5G_LOF
2.2.11 LQM Board Alarm List
Issue 04 (2010-10-20)
ALM_DATA_RLOS
NO_BD_SOFT
OUT_PWR_HIGH
ALM_DATA_TLOS
ODU1_PM_AIS
OUT_PWR_LOW
B1_EXC
ODU1_PM_BDI
PORT_MODULE_OFFLINE
B1_SD
ODU1_PM_DEG
POWER_FAIL
BD_STATUS
ODU1_PM_EXC
REM_SD
BEFFEC_EXC
ODU1_PM_LCK
REM_SF
FPGA_ABN
ODU1_PM_OCI
R_LOF
IN_PWR_HIGH
ODU1_PM_TIM
R_LOS
IN_PWR_LOW
OPS_STA_INDI
TD
J0_MM
OPU1_PLM
TEMP_OVER
LASER_MOD_ERR_EX
OTU1_AIS
TEM_HA
OTU1_BDI
TEM_LA
LINK_ERR
OTU1_DEG
TF
LOOP_ALM
OTU1_EXC
VCXO_LOC
LSR_WILL_DIE
OTU1_LOF
WRG_BD_TYPE
L_SYNC
OTU1_LOM
MS_AIS
OTU1_TIM

2-23

Transport Platform
2 Alarm List
2.2.12 LQM2 Board Alarm List

ALM_DATA_RLOS
NO_BD_SOFT
OUT_PWR_HIGH
ALM_DATA_TLOS
ODU1_PM_AIS
OUT_PWR_LOW
B1_EXC
ODU1_PM_BDI
PORT_MODULE_OFFLINE
B1_SD
ODU1_PM_DEG
POWER_FAIL
BD_STATUS
ODU1_PM_EXC
PRBS_LSS
BEFFEC_EXC
ODU1_PM_LCK
REM_SD
FPGA_ABN
ODU1_PM_OCI
REM_SF
IN_PWR_HIGH
ODU1_PM_TIM
R_LOF
IN_PWR_LOW
OPS_STA_INDI
R_LOS
J0_MM
OPU1_PLM
TD
LASER_MOD_ERR_EX
OTU1_AIS
TEMP_OVER
OTU1_BDI
TEM_HA
LINK_ERR
OTU1_DEG
TEM_LA
LOOP_ALM
OTU1_EXC
TF
LSR_WILL_DIE
OTU1_LOF
VCXO_LOC
L_SYNC
OTU1_LOM
WRG_BD_TYPE
MS_AIS
OTU1_TIM
2.2.13 LQPL Board Alarm List
2-24
B1_EXC
ODU1_PM_LCK
OTU2_DEG
B1_SD
ODU1_PM_OCI
OTU2_EXC
BD_STATUS
ODU1_PM_TIM
OTU2_LOF
BEFFEC_EXC
ODU2_PM_AIS
OTU2_LOM
FPGA_ABN
ODU2_PM_BDI
OTU2_TIM
GPON_DS_LOF
ODU2_PM_DEG
OUT_PWR_HIGH
GPON_US_LOF
ODU2_PM_EXC
OUT_PWR_LOW
IN_PWR_HIGH
ODU2_PM_LCK
PORT_MODULE_OFFLINE

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
IN_PWR_LOW
ODU2_PM_OCI
POWER_FAIL
J0_MM
ODU2_PM_TIM
PRBS_LSS
LASER_MOD_ERR_EX
OPS_STA_INDI
REM_SD
OPU2_PLM
REM_SF
LOOP_ALM
OTU1_AIS
R_LOF
LSR_COOL_ALM
OTU1_BDI
R_LOS
LSR_WILL_DIE
OTU1_DEG
TD
MS_AIS
OTU1_EXC
TEMP_OVER
NO_BD_SOFT
OTU1_LOF
TEM_HA
ODU1_PM_AIS
OTU1_LOM
TEM_LA
ODU1_PM_BDI
OTU1_TIM
TF
ODU1_PM_DEG
OTU2_AIS
VCXO_LOC
ODU1_PM_EXC
OTU2_BDI
WRG_BD_TYPE
B1_EXC
ODU1_PM_OCI
OTU2_BDI
B1_SD
ODU1_PM_TIM
OTU2_DEG
BD_STATUS
ODU2_PM_AIS
OTU2_EXC
BEFFEC_EXC
ODU2_PM_BDI
OTU2_LOF
FPGA_ABN
ODU2_PM_DEG
OTU2_LOM
GPON_DS_LOF
ODU2_PM_EXC
OTU2_TIM
GPON_RUF
ODU2_PM_LCK
OUT_PWR_HIGH
IN_PWR_HIGH
ODU2_PM_OCI
OUT_PWR_LOW
IN_PWR_LOW
ODU2_PM_TIM
PORT_MODULE_OFFLINE
J0_MM
ONU_OFFLINE
POWER_FAIL
LASER_MOD_ERR_EX
ONU_LOFI
PRBS_LSS
ONU_LOSI
REM_SD
LOOP_ALM
OPS_STA_INDI
REM_SF
2.2.14 LQPU Board Alarm List
Issue 04 (2010-10-20)

2-25

Transport Platform
2 Alarm List
LSR_COOL_ALM
OPU2_PLM
R_LOF
LSR_WILL_DIE
OTU1_AIS
R_LOS
MS_AIS
OTU1_BDI
TD
NO_BD_SOFT
OTU1_DEG
TEMP_OVER
ODU1_PM_AIS
OTU1_EXC
TEM_HA
ODU1_PM_BDI
OTU1_LOF
TEM_LA
ODU1_PM_DEG
OTU1_LOM
TF
ODU1_PM_EXC
OTU1_TIM
VCXO_LOC
ODU1_PM_LCK
OTU2_AIS
WRG_BD_TYPE
ODU1_PM_EXC
OUT_PWR_LOW
ODU1_PM_LCK
PORT_MODULE_OFFLINE
FPGA_ABN
ODU1_PM_OCI
POWER_FAIL
IN_PWR_HIGH
ODU1_PM_TIM
REM_SF
IN_PWR_LOW
OPS_STA_INDI
R_LOS
LASER_MOD_ERR_EX
OPU1_PLM
TD
OTU1_AIS
TEMP_OVER
LSR_COOL_ALM
OTU1_BDI
TEM_HA
LSR_WILL_DIE
OTU1_DEG
TEM_LA
GPON_DS_LOF
OTU1_EXC
TF
NO_BD_SOFT
OTU1_LOF
VCXO_LOC
ODU1_PM_AIS
OTU1_LOM
WRG_BD_TYPE
ODU1_PM_BDI
OTU1_TIM
ODU1_PM_DEG
OUT_PWR_HIGH
2.2.15 LSPL Board Alarm List

BD_STATUS
BEFFEC_EXC
2.2.16 LSPR Board Alarm List

BD_STATUS
2-26
LSR_WILL_DIE
R_LOS
Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
FPGA_ABN
NO_BD_SOFT
TD
GPON_DS_LOF
ONU_OFFLINE
TEMP_OVER
GPON_RUF
ONU_LOFI
TEM_HA
IN_PWR_HIGH
ONU_LOSI
TEM_LA
IN_PWR_LOW
OUT_PWR_HIGH
TF
LASER_MOD_ERR_EX
OUT_PWR_LOW
VCXO_LOC
PORT_MODULE_OFFLINE
WRG_BD_TYPE
LSR_COOL_ALM
POWER_FAIL
2.2.17 LSPU Board Alarm List
Issue 04 (2010-10-20)
BD_STATUS
ODU1_PM_EXC
OTU1_TIM
BEFFEC_EXC
ODU1_PM_LCK
OUT_PWR_HIGH
FPGA_ABN
ODU1_PM_OCI
OUT_PWR_LOW
GPON_DS_LOF
ODU1_PM_TIM
PORT_MODULE_OFFLINE
GPON_RUF
ONU_OFFLINE
POWER_FAIL
IN_PWR_HIGH
ONU_LOFI
REM_SD
IN_PWR_LOW
ONU_LOSI
REM_SF
LASER_MOD_ERR_EX
OPS_STA_INDI
R_LOS
OPU1_PLM
TD
LSR_COOL_ALM
OTU1_AIS
TEMP_OVER
LSR_WILL_DIE
OTU1_BDI
TEM_HA
NO_BD_SOFT
OTU1_DEG
TEM_LA
ODU1_PM_AIS
OTU1_EXC
TF
ODU1_PM_BDI
OTU1_LOF
VCXO_LOC
ODU1_PM_DEG
OTU1_LOM
WRG_BD_TYPE

2-27

Transport Platform
2 Alarm List
2.2.18 LSX Board Alarm List

ALM_DATA_RLOS
NO_BD_SOFT
OUT_PWR_LOW
ALM_DATA_TLOS
ODU2_PM_AIS
PORT_MODULE_OFFLINE
B1_EXC
ODU2_PM_BDI
POWER_FAIL
B1_SD
ODU2_PM_DEG
PRBS_LSS
BD_STATUS
ODU2_PM_EXC
REMOTE_FAULT
BEFFEC_EXC
ODU2_PM_LCK
REM_SD
FPGA_ABN
ODU2_PM_OCI
REM_SF
IN_PWR_HIGH
ODU2_PM_TIM
R_LOF
IN_PWR_LOW
OPS_STA_INDI
R_LOS
J0_MM
OPU2_PLM
TD
LASER_MOD_ERR_EX
OTU2_AIS
TEMP_OVER
OTU2_BDI
TEM_HA
LINK_ERR
OTU2_DEG
TEM_LA
LOCAL_FAULT
OTU2_EXC
TF
LOOP_ALM
OTU2_LOF
VCXO_LOC
LSR_COOL_ALM
OTU2_LOM
WRG_BD_TYPE
LSR_WILL_DIE
OTU2_TIM
MS_AIS
OUT_PWR_HIGH
2.2.19 LWX2 Board Alarm List
2-28
BD_STATUS
NO_BD_SOFT
R_LOS
FPGA_ABN
OPS_STA_INDI
TD
IN_PWR_HIGH
OUT_PWR_HIGH
TEMP_OVER
IN_PWR_LOW
OUT_PWR_LOW
TEM_HA
LASER_MOD_ERR_EX
PORT_MODULE_OFFLINE
TEM_LA
POWER_FAIL
TF

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
LOOP_ALM
PRBS_LSS
LSR_WILL_DIE
R_LOC
WRG_BD_TYPE
2.2.20 MD8/MD8S Board Alarm List

WRG_BD_TYPE
BD_STATUS
NO_BD_SOFT

WRG_BD_TYPE
BD_STATUS
NO_BD_SOFT

BD_STATUS
WRG_BD_TYPE
NO_BD_SOFT

BD_STATUS
WRG_BD_TYPE
NO_BD_SOFT
WRG_BD_TYPE
NO_BD_SOFT
2.2.24 MR8 Board Alarm List

BD_STATUS
2.2.25 OLP Board Alarm List
Issue 04 (2010-10-20)
AD_CHECK_FAIL
NO_BD_SOFT
R_LOS
BD_STATUS
OPS_STA_INDI
TEMP_OVER
FPGA_ABN
POWER_DIFF_DEFECT
WRG_BD_TYPE
MUT_LOS
POWER_DIFF_OVER
NO_BD_PARA
POWER_FAIL

2-29

Transport Platform
2 Alarm List
2.2.26 OPU Board Alarm List

AD_CHECK_FAIL
BD_STATUS
FPGA_ABN
IN_PWR_HIGH
IN_PWR_LOW
LSR_WILL_DIE
MUT_LOS
NO_BD_PARA
NO_BD_SOFT
OA_LOW_GAIN
PORT_MODULE_OFFLINE
POWER_FAIL
PUM_BCM_ALM
PUMP_COOL_EXC
PUM_TEM_ALM
TD
TEMP_OVER
WRG_BD_TYPE
2.2.27 PIU Board Alarm List

NO_BD_SOFT
BD_STATUS
POWER_FAIL
THUNDERALM

BD_STATUS
WRG_BD_TYPE
NO_BD_SOFT
WRG_BD_TYPE
NO_BD_SOFT
WRG_BD_TYPE
NO_BD_SOFT
WRG_BD_TYPE
NO_BD_SOFT

BD_STATUS

BD_STATUS

BD_STATUS
2-30

Issue 04 (2010-10-20)

Transport Platform
2 Alarm List
2.2.32 SCC Board Alarm List
Issue 04 (2010-10-20)
BD_STATUS
NESTATE_INSTALL
SECU_ALM
BOOTROM_BAD
NO_BD_SOFT
STORM_CUR_QUENUM_O
VER
CFGDATA_OUTRANGE
OPS_MAIN_BAK_ATTR
_DIFF
SUBRACK_ID_CONFLICT
CFGVERIFY
OPS_PS_INDI
SUBRACK_TYPE_MISMATCH
DBMS_ERROR
OSC_LOS
SUB_RACK_OFFLINE
DBMS_PROTECT_MODE
OUT_PWR_HIGH
SWDL_ACTIVATED_TIME
OUT
DCC_CHAN_LACK
OUT_PWR_LOW
SWDL_AUTOMATCH_INH
ETH_LINK_DOWN
PATCHFILE_NOTEXIST
SWDL_CHGMNG_NOMATCH
FUSE_ALARM
PATCH_ACT_TIMEOUT
SWDL_COMMIT_FAIL
HARD_BAD
PATCH_DEACT_TIMEOUT
SWDL_INPROCESS
IN_PWR_HIGH
PATCH_ERR
SWDL_NEPKGCHECK
IN_PWR_LOW
PATCH_NOT_CONFIRM
SWDL_PKGVER_MM
PATCH_PKGERR
SWDL_PKG_NOBDSOFT
LCS_FILE_NOT_EXIST
PORT_MODULE_OFFLINE
SWDL_ROLLBACK_FAIL
LCS_EXPIRED
POWER_FAIL
SYSLOG_COMM_FAIL
LCS_DAYS_OF_GRACE
PWR_MAJ_ALM
TEMP_ALARM
LSR_WILL_DIE
RELAY_ALARM_CRITICAL
TEMP_OVER
MDL_ALARM
RELAY_ALARM_IGNORE
TEM_HA
MSSW_DIFFERENT
RELAY_ALARM_MAJOR
TEM_LA
NEBD_XC_DIF
RELAY_ALARM_MINOR

2-31

Transport Platform
2 Alarm List
2.2.33 SCS Board Alarm List

BD_STATUS
WRG_BD_TYPE
NO_BD_SOFT
2.2.34 TSP Board Alarm List
2-32
AU_AIS
IN_PWR_HIGH
OUT_PWR_LOW
AU_LOP
IN_PWR_LOW
PORT_MODULE_OFFLINE
B1_EXC
J0_MM
POWER_FAIL
B1_SD
PRBS_LSS
B2_EXC
LASER_MOD_ERR_EX
R_LOF
B2_SD
LOOP_ALM
R_LOS
B3_EXC
LP_RDI
S1_SYN_CHANGE
B3_SD
LP_REI
SYNC_C_LOS
BD_STATUS
LP_RFI
TD
BIP_EXC
LP_SLM
TEMP_OVER
BIP_SD
LP_TIM
TEM_HA
DOWN_E1_AIS
LP_UNEQ
TEM_LA
DOWN_T1_AIS
LSR_COOL_ALM
TF
E1_LOC
LSR_WILL_DIE
TU_AIS
EXT_SYNC_LOS
LTI
TU_LOP
FPGA_ABN
MS_AIS
T_ALOS
HP_LOM
MS_RDI
UP_E1_AIS
HP_RDI
MS_REI
UP_T1AIS
HP_REI
NO_BD_SOFT
VCXO_LOC
HP_SLM
OOL
WRG_BD_TYPE
HP_TIM
OPS_STA_INDI
HP_UNEQ
OUT_PWR_HIGH

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Alarm Processing
About This Chapter

This chapter is organized into two sections: "Common Alarm Processing" and "Alarm
Processing". Section "Common Alarm Processing" provides the information on the handling of
common alarms of the product, and section "Alarm Processing" provides the information on the
handling of the other alarms other than the common alarms of the product.
3.1 Common Alarm Processing
This chapter describes common information relevant to alarm handling, including alarm
descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm
handling procedures.
3.2 Alarm Processing
This chapter describes information relevant to alarm handling, including alarm descriptions,
alarm parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.
Issue 04 (2010-10-20)

3-1

Transport Platform
3 Alarm Processing
3.1 Common Alarm Processing

This chapter describes common information relevant to alarm handling, including alarm
descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm
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 improperly, the communication
between the board and the SCC is affected and even the services are interrupted.
3.1.1 ALM_DATA_RLOS
3.1.2 ALM_DATA_TLOS
3.1.3 B1_EXC
3.1.4 BEFFEC_EXC
3.1.5 IN_PWR_HIGH
3.1.6 IN_PWR_LOW
3.1.7 LASER_MODULE_MISMATCH
3.1.8 LINK_ERR
3.1.9 LOOP_ALM
3.1.10 LSR_WILL_DIE
3.1.11 MS_AIS
3.1.12 MS_RDI
3.1.13 MUT_LOS
3.1.14 NEBD_XC_DIF
3.1.15 OA_LOW_GAIN
3.1.16 ODUk_PM_AIS
3.1.17 ODUk_PM_BDI
3.1.18 ODUk_PM_DEG
3.1.19 ODUk_PM_EXC
3.1.20 OPS_PS_INDI
3-2

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.1.21 OSC_LOS
3.1.22 OUT_PWR_HIGH
3.1.23 PORT_MODULE_OFFLINE
3.1.24 POWER_DIFF_DEFECT
3.1.25 POWER_FAIL
3.1.26 PUMP_COOL_EXC
3.1.27 R_LOF
3.1.28 R_LOS
3.1.29 REM_SF
3.1.30 SECU_ALM
3.1.31 SUBRACK_ID_CONFLICT
3.1.32 TD
3.1.33 TF
3.1.34 WRG_BD_TYPE
3.1.1 ALM_DATA_RLOS
Description
Receiving data lost on the Ethernet port. The board regularly checks the total number of the
received bytes and compares the number with the number of last time. The alarm is generated
when the two numbers are the same, which indicating that the board does not receive any data.
Reported from the WDM side or client side: client side.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None
Impact on the System

The connection status of the Ethernet port is normal; however, the optical signals do not have
data packet. As a result, the services may be interrupted.
Possible Causes
l
Issue 04 (2010-10-20)
Cause 1: The data equipment on the client side stops sending data.
3-3

Transport Platform
3 Alarm Processing
Cause 2: The data configuration is incorrect.
Cause 3: The Ethernet port of the board is faulty, which cannot receive data.
Query the alarm on the U2000 and record the IDs of the port and channel where the alarm
is generated.
Cause 1: The data equipment on the client side stops sending data.
Procedure
1.
l
Check whether the data equipment on the client side (including test meters) stops
sending data. If yes, start to send data again.
Cause 2: The data configuration is incorrect.

1.
Check whether the receive wavelength on the client side of the board that reports the
alarm is consistent with the transmit wavelength at the port of the data equipment. If
not, replace the module at the port of the data equipment.
2.
Check whether the port where the alarm is generated is configured with logical service
but does not access any real service. If yes, delete the logical service or suppress this
alarm.
Cause 3: The Ethernet port of the board is faulty, which cannot receive data.
1.
Check whether the LINK_ERR alarm is generated at the Ethernet port. If yes,
troubleshoot the LINK_ERR alarm.
2.
If the alarm persists, check whether there are other alarms on the board that reports
the alarm. If there are other alarms, troubleshoot these alarms.
3.
If the alarm persists, the board may be faulty. Replace the board. For details, refer to
"Replacing a Board" of the Supporting Tasks.
----End
Related Information
The alarm is a warning alarm used as an auxiliary warning for fault judgement. Generally, the
alarm is generated when the test meter or -side data equipment stops sending data packet. The
possibility that the alarm is generated due to the faulty board is low.
3.1.2 ALM_DATA_TLOS
Description
Transmitting data lost on the Ethernet port. The board regularly checks the total number of the
transmitted bytes and compares the number with the number of last time. The alarm is generated
when the two numbers are the same, which indicates that the board does not transmit any data.
Attribute
3-4
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Parameters
None

The connection status of the Ethernet port is normal; however, the optical signals do not have
data packet. As a result, the services may be interrupted.
Possible Causes
l
Cause 1: The WDM side at the local station does not receive data and thus no data is sent
from the client side.
Cause 2: The WDM side at the local station receives data but the client side does not send
data because the board is faulty.
is generated.
Cause 1: The WDM side at the local station receives no data and thus no data is sent from
the client side.
Procedure
1.
Check whether the board at the opposite station reports an ALM_DATA_RLOS alarm.
2.
If the ALM_DATA_RLOS is detected on the OTU board at the opposite station, see
ALM_DATA_RLOS for how to troubleshoot the alarm at the opposite station.
Cause 2: The WDM side at the local station receives data but the client side does not send
data because the board is faulty.
1.
If the board at the opposite station does not report an ALM_DATA_RLOS alarm,
perform a cold reset on the faulty board at the local station on the U2000 or reset the
faulty board. For details, see the Troubleshooting.
2.
If the alarm persists, replace the board that reports the alarm. For details, refer to
----End
Related Information
None
3.1.3 B1_EXC
Description
The B1_EXC(OTN) alarm indicates the regenerator section (B1) excessive errors. The alarm is
generated when the received SDH signals degrade and the B1 bit errors in the multiplex section
exceed the threshold.
Reported from the WDM side or client side: WDM side and client side.
l
Issue 04 (2010-10-20)
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.
3-5

Transport Platform
3 Alarm Processing
The alarm is generated on the client side when the B1 bit errors in the SDH signals received
on the client side exceed the B1 bit error threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

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

the B1_EXC alarm
OTU1
O
A
D
M
F
I
U
F
I
U
O
A
D
M
WDM side Client side
Client side WDM side

Station A
3-6
OTU2
Out-loop

Station B
Issue 04 (2010-10-20)

Transport Platform
1.
3 Alarm Processing
Configure outloop at the transmit and receive optical interfaces on the WDM side of
the OTU2. If there is no bit error alarm on the OTU1, it indicates that the board at the
local station is faulty. Replace the faulty board. For details, refer to "Replacing a
Board" of the Supporting Tasks.
Cause 2 for the alarm generated on the WDM side: The attenuation of the received signals
is excessively high; the fiber or connector is not clean.
1.
If there are bit errors, on the U2000 check whether the transmit optical power at the
corresponding optical interfaces on the opposite OTU1 is within the normal range.
For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description .
2.
If the transmit optical power of the optical interface on OTU1 at the opposite station
is within the normal range, check the fibers and clean the fiber connectors between
transmiting side of OTU1 and the receive side of OTU2.
Cause 3 for the alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
1.
If the optical power of the optical interface on OTU1 at the opposite station is
abnormal, check whether the B1_EXC alarm is generated on the client side of the
opposite OTU1. If yes, clear the B1_EXC alarm on the client side. If not, it indicates
that the opposite OTU1 is faulty. Replace the opposite OTU1. For the optical power
specification of the specific board, refer to "Technical Specifications" of the Product
Description .
----End
Related Information
None.
3.1.4 BEFFEC_EXC
Description
The BEFFEC_EXC alarm indicates that bit errors before FEC alarm exceed the threshold.
Signals from the WDM side of the opposite OTUs have the FEC function. As a result, before
performing signal FEC in the receive direction on theWDM side of the local OTUs, the local
OTUs computes the bit error rate. This alarm is generated when the computed bit error rate
exceeds the threshold.
Reported from the WDM or client side: WDM side
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None
Issue 04 (2010-10-20)

3-7

Transport Platform
3 Alarm Processing

The error tolerance of the system decreases, and the quality of signals is affected if the decrease
is sufficient.
Possible Causes
l
Cause 1: The input optical power of the OTU is excessively high or low. The system
performance degrades. For example, the optical signal to noise ratio (OSNR) is excessively
low, or dispersion or non-linearity occurs.
Cause 2: An inappropriate DCM is installed.
Cause 3: The board at the opposite station is faulty.
Cause 4: The board that reports the alarm is faulty.
is generated.
Cause 1: The input optical power of the OTU is excessively high or low. The system
performance degrades. For example, the optical signal to noise ratio (OSNR) is excessively
low, or dispersion or non-linearity occurs.
Procedure
1.
Check whether the receive optical power on the U2000 is within the normal range,
For the optical power specification of the specific board, refer to "Technical
2.
If the input optical power is abnormal, see the methods for handling the
IN_PWR_HIGH and IN_PWR_LOW.
3.
If the optical power is normal, it is possible that the system performance degrades.
For the alarm handling, refer to "Troubleshooting Bit Errors" of the
Troubleshooting.
Cause 2: An inappropriate DCM is installed.

1.
Check whether the DCM used on the existing network is appropriate. If not, replace
the DCM.
Cause 3 and cause 4: The board at the opposite station may be faulty; the board at the local
station may be faulty.
1.
If the alarm persists, the OTU that reports the alarm may be faulty. Replace the OTU,
For details, refer to "Replacing a Board" of the Supporting Tasks.
2.
If the alarm persists, the board at the opposite station may be faulty. Replace the faulty
board, For details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
3-8

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.1.5 IN_PWR_HIGH
Description
The IN_PWR_HIGH(OTN) indicates that the input optical power is excessively high. The alarm
is generated when the input optical power is higher than the upper threshold of the input optical
power.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

When the input optical power is excessively high, bit errors and LOF alarms may be generated
in the received signals, and the optical module on the board can be damaged. As a result, the
services are affected.
Possible Causes
l
Cause 1 for the alarm generated on the client side: The input optical power is excessively
high, and the configured attenuation is insufficient.
Cause 2 for the alarm generated on the client side: The board that reports the alarm is faulty.
Cause 1 for the alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.
Cause 2 for the alarm generated on the WDM side: The board that reports the alarm is
faulty.
Cause 1 for the alarm generated in multiple wavelengths: The input optical power is
excessively high, and the configured attenuation is insufficient.
Cause 2 for the alarm generated in multiple wavelengths: The output optical power of the
board in the upstream station is excessively high.
Cause 3 for the alarm generated in multiple wavelengths: The board that reports the alarm
is faulty.
is generated.
Cause 1 for the alarm generated on the client side: The input optical power is excessively
high, and the configured attenuation is insufficient.
Procedure
1.
Issue 04 (2010-10-20)
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
3-9

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

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Replace the board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
The optical attenuator is marked with attenuation values in the unit of dB.
3.1.6 IN_PWR_LOW
Description
The IN_PWR_LOW(OTN) alarm indicates that input optical power is excessively low. The
alarm is generated when the input optical power is lower than the lower threshold of the input
optical power.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

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

3-11

Transport Platform
3 Alarm Processing
Cause 4 for the alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient.
faulty.
is generated.
Cause 1 for the alarm generated on the client side: The fiber connector is dirty, and the fiber
jumper is over-bent, damaged or aged.
Procedure
1.
Use an optical power meter to measure the input optical power of the local board, thus
to determine whether the input optical power is within the normal range. For the optical
power specifications of the specific board, see the Product Description.
2.
If the detected power is low, check the fiber connection. If the fiber connector is dirty,
clean or replace the fiber connector. For details, see the Supporting Tasks.
3.
If the alarm persists, check the fiber jumper. If the fiber jumper is excessively bent,
damaged or aged, adjust the fiber jumper or replace the fiber jumper.
Cause 2 for the alarm generated on the client side: The attenuation of the attenuator attached
to the optical interface on the board that reports the alarm is excessively high.
1.
If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical interface is excessively high. If the attenuation is excessively high,
decrease the attenuation value of the attenuator to a proper value or replace it with a
suitable attenuator.
2.
Cause 3 for the alarm generated on the client side: The channel use status of the board that
reports the alarm is incorrect.
1.
Cause 1 for the alarm generated on the WDM side: The fiber connector is dirty, and the
fiber jumper is over-bent, damaged or aged.
1.
Use an optical power meter to measure the input optical power of the local board to
determine whether the input optical power is within the normal range. For the optical
power specifications of the specific board, see the Product Description.
2.
If the detected power is excessively low, check the fiber connection. If the fiber
connector is dirty, clean or replace the fiber connector. For details, see the Supporting
Tasks.
3.
If the alarm persists, check the fiber jumper. If the fiber jumper is excessively bent,
damaged or aged, adjust the fiber jumper or replace the fiber jumper.
Cause 2 for the alarm generated on the WDM side: The attenuation of the attenuator
attached to the optical interface on the board that reports the alarm is excessively high.
1.
3-12
Check whether the channel use status on the U2000 is the same as that of the actual
channel use status setting of the board. If not, resetting the channel use status.
If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical interface is excessively high. If the attenuation is excessively high,
decrease the attenuation value of the attenuator to a proper value or replace it with a
suitable attenuator.
Issue 04 (2010-10-20)

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

3-13

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The LASER_MODULE_MISMATCH alarm results in that services cannot be normally
received or transmitted. It can even cause service interruption.
Possible Causes
l
Cause 1: The type of the logical optical interface is inconsistent with the type of the physical
optical module on the board.
Cause 1: The type of the logical optical interface is inconsistent with the type of the physical
optical module on the board.
Procedure
1.
Check whether the optical module type of the board is correct. For details, see "Quick
Reference Table of the Units" in the Hardware Description. If yes, re-configure the
type of the corresponding logical optical interface.
2.
If not, replace the optical module on the board with another one of the right type. For
details, see "Replacing the Pluggable Optical Module" in the Parts Replacement.
3.
Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
3.1.8 LINK_ERR
Description
The LINK_ERR(OTN) alarm indicates the link error. The alarm is generated when the link of
the Ethernet data port is down.
Reported from the WDM side or client side: Client side
3-14

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

When the link of the Ethernet ports is down, a valid link cannot be created between the two data
ports and the data services are interrupted.
Possible Causes
l
Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports
are inconsistent. For example, one port is in the auto-negotiation mode but the other is nonnegotiation.
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or very low.
Cause 4: The optical interface types (and the fiber types) of the two interconnected Ethernet
ports are inconsistent.
Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails.
Cause 6: The data equipment on the client side is faulty.
is generated.
Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
Procedure
1.
Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports are
inconsistent.
1.
Issue 04 (2010-10-20)
Check whether the service type of the OTU at the local station matches the type of
the services transmitted from the client data equipment. If not, replace the OTU with
an OTU of a proper service type. For details, refer to "Replacing a Board" of the
Supporting Tasks.
Check whether the auto-negotiation mode of the optical interface on the board that
reports the alarm is consistent with that of the client data equipment. If they are
inconsistent, modify the setting to ensure the consistency.
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or very low.
3-15

Transport Platform
3 Alarm Processing
1.
Check whether the input optical power of the Ethernet port on the two ports that are
interconnected is within the normal range. For the optical power specifications of the
specific board, see the Product Description.
2.
If the input optical power is abnormal, see the handling procedures for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
Cause 4: The optical module types of the two interconnected Ethernet boards are
inconsistent. Hence, the types of fibers that the two optical modules support are different.
1.
Cause 5: The fiber or cable that is used to connect the two Ethernet ports fails.
1.
Check whether the fiber or cable that is used to connect the two Ethernet ports are
properly connected. If they are not properly connected, reconnect or replace the fiber
or cable.
Cause 6: The data equipment on the client side is faulty.

1.
Check whether the types of fibers that the two optical modules support are consistent.
If they are inconsistent, replace either board to make the type of the two optical
modules match the fiber type.
Check whether the data equipment on the client side is faulty. If the equipment is
faulty, troubleshoot the fault of the data equipment on the client side.

1.
If the alarm persists, perform a cold reset on the faulty board through the U2000.
2.
----End
Related Information
None.
3.1.9 LOOP_ALM
Description
The LOOP_ALM(OTN) alarm indicates a loopback. The alarm is generated when the optical
interface of the board is in the loopback status.
Attribute
Alarm Severity
Alarm Type
Minor
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.
3-16

Issue 04 (2010-10-20)

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

l 0x01: Inloop.
l 0x02: Outloop.

Services are interrupted.
Possible Causes
l
Cause 1: The loopback command is issued during testing or maintenance.
is generated.
Cause 1: The loopback command is issued during testing or maintenance.
Procedure
1.
Check whether the loopback is set on the optical interface during testing or
maintenance. After the test or maintenance is complete, release the loopback
configured for the specific optical interface.
----End
Related Information
None.
3.1.10 LSR_WILL_DIE
Description
The LSR_WILL_DIE alarm indicates that the laser will be out of work.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None
Issue 04 (2010-10-20)

3-17

Transport Platform
3 Alarm Processing

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

1.
Replace the board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
None.
3.1.11 MS_AIS
Description
The MS_AIS(OTN) is an indication alarm in the multiplex section. The alarm is generated when
the opposite station transmits the MS_AIS signals or the receive side of the local station is faulty.
Reported from the WDM or client side: WDM side, client side.
l
WDM side: In this case, the type of the service received on the WDM side is SDH.
client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None
3-18

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

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

MS_AIS alarm
The client signals contain

the MS_AIS signal
Client
side
O
T
U
WDM
side
Station A
WDM
side
O
T
U
Client
side
Station B
Cause 1 for the alarm generated on the WDM side: The input signals from the client
equipment at the opposite station contain MS_AIS signals, which are transmitted to the
downstream station. At the same time, the MS_AIS alarm is detected on the WDM side of
the OTU at the local station and it is reported to the U2000. See the preceding figure.
faulty.
is generated.
Cause 1 for the alarm generated on the client side: In the case of the OTU board of which
the client side supports the SDH services, the input signals from the client side contain the
MS_AIS signal.
Procedure
1.
l
Cause 1 for the alarm generated on the WDM side: The input signals from the client side
of the OTU at the opposite station contain MS_AIS signals.
1.
When the MS_AIS alarm is reported from the client side, remove the fault of the
equipment on the client side.
Check whether the MS_AIS alarm is generated on the client side of the OTU at the
opposite station on the U2000. If yes, clear the MS_AIS alarm according to the
handling method for the alarm generated on the client side of the OTU.
faulty.
1.
If the alarm persists and the MS_AIS alarm is not inserted at the opposite station, the
board that reports the alarm is faulty. Replace the board. For details, refer to "Replacing
a Board" of the Supporting Tasks.
----End
Issue 04 (2010-10-20)

3-19

Transport Platform
3 Alarm Processing
Related Information
None.
3.1.12 MS_RDI
Description
The MS_RDI(OTN) is a remote defect indication alarm in the multiplex section. The alarm is
generated at the local station if the opposite station back transmits the information through
overhead when the WDM-side receive part of the opposite station is faulty (for example, the
R_LOS, R_LOF or MS_AIS alarm is generated).
Reported from the WDM or client side: WDM side, client side
l
WDM side: In this case, the type of the service received on the WDM side is SDH.
Client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

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

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

MS_RDI alarm
The client signals contain

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

Transport Platform
3 Alarm Processing
1.
151. Query the alarm of the board at the opposite station by using the U2000. If the
R_LOS, R_LOF or MS_AIS alarm exists, see the handling procedure of the R_LOS,
R_LOF or MS_AIS alarm for troubleshooting.
faulty.
1.
If the alarm persists, the board at the local station is faulty. Consider whether to replace
the faulty board or not according to the actual situation (whether affects the services).
----End
Related Information
None.
3.1.13 MUT_LOS
Description
Loss of multiplexed signals alarm. The alarm is generated when the input multiplexed signals
of the board is lost.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

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

Issue 04 (2010-10-20)

Transport Platform
1.
3 Alarm Processing
Check whether there are fibers connected to certain optical interfaces at the receive
end of the board that reports the alarm are not connected, incorrectly connected, or
damaged. If yes, connect the input optical fibers to the specific optical interface, or
replace the damaged fiber.
Cause 2: The attenuation of signals in line transmission is excessively high.

1.
Use an optical power meter to measure the actual receive optical power of the board
that reports the alarm. Check whether the receive optical power is within the normal
range. For the optical power specification of the specific board, refer to "Technical
2.
If the receive optical power is excessively low, see the handling procedure of the
IN_PWR_LOW alarm for troubleshooting.

1.
----End
Related Information
None
3.1.14 NEBD_XC_DIF
Description
The NEBD_XC_DIF is an alarm indicating that the cross-connect matrix data of the NE and
board is different. For the board supporting service cross-connection, the alarm occurs when the
cross-connection data stored on the SCC is not consistent with that stored on the board.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Parameter
Description
Parameter 1 and Parameters 2 Indicates the slot ID.
Issue 04 (2010-10-20)

3-23

Transport Platform
3 Alarm Processing
Parameter
Description
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
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.
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.
Procedure
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.
If the alarm persists, perform a warm reset on the board related to service crossconnections on the U2000.
2.
If the alarm persists, perform warm reset on the SCC on the U2000. For details, refer
to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
3.1.15 OA_LOW_GAIN
Description
The OA_LOW_GAIN alarm indicates low optical amplifier signal gain. The alarm is generated
when the actual gain of the optical amplifier board is 3 dB lower than the standard gain.
Attribute
3-24
Alarm Severity
Alarm Type
Critical
Service alarm

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Parameters
None

The alarm caused by different factors has different influences on the system:
l
If the alarm is generated because the input optical power is excessively high, the redundancy
of the system decreases, which influences the succeeding capacity expansion.
Possible Causes
l
Cause 1: The input optical power of the board is excessively high.
Cause 1: The input optical power of the board is excessively high.
Procedure
1.
Check whether the receive optical power of the board is within the normal range on
the U2000. For the optical power specification of the specific board, refer to
"Technical Specifications" of the Product Description .
2.
If the input optical power is not within the normal range, adjust the optical attenuator
attached to the input optical interface so that the input optical power meets the
specification requirement.
3.
If no optical attenuator is attached to the input optical interface, add an optical

attenuator to ensure that the input optical power meet the specification requirement.

1.
If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board"
of the Supporting Tasks.
----End
Related Information
None.
3.1.16 ODUk_PM_AIS
Description
The ODUk_PM_AIS is the ODUk PM alarm indication signal. An AIS signal travels
downstream, which indicates that a signal failure is detected in the upstream.
k indicates the level of rate and its value is 0, 1, 2, or 5G.
Issue 04 (2010-10-20)

3-25

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The services borne on the optical interface would be unavailable.
Possible Causes
l
Cause 1 for the alarm generated on the client side: Signals input from the client side contain
ODUk_PM_AIS signals.
See the following figure.
The input signals on the client side of the OTU at station A contain ODUk_PM_AIS signals.
The OTU at station A reports an ODUk_PM_AIS alarm on the client side after detecting
the ODUk_PM_AIS signals.
Detects and reports

the ODUk_PM_AIS alarm
The client
signals contain
the ODUk_PM_AIS
signal
Client
side
O
T
U
WDM
side
Station A
WDM
side
O
T
U
Client
side
Station B
Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty.
Cause 1 for the alarm generated on the WDM side: The client side of corresponding board
at the opposite station reports the ODUk_PM_AIS, R_LOS, OTUk_LOF, and
OTUk_LOM alarms, and then inserts AIS signals to the downstream station.
is generated.
ODUk_PM_AIS signals.
Procedure
3-26

Issue 04 (2010-10-20)

Transport Platform
1.
3 Alarm Processing
If this alarm is reported from the client side of the board, apply a hardware loopback
between the transmit and receive optical interfaces on the client side of the OTU at
station A. If the alarm persists, it indicates that the OTU hardware is faulty. In this
case, see the alarm handling procedure for cause 2 of this alarm generated on the client
side.
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.
Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty.
1.
Check whether the board that reports this alarm supports pluggable optical modules.
If ...
Then ...
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 for the alarm generated on the WDM side: The corresponding board at the opposite
station transmits the ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM alarm signals.
1.
Query whether the ODUk_PM_AIS, R_LOS, OTUk_LOF or OTUk_LOM 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 station.
----End
Related Information
ITU-T G.709
3.1.17 ODUk_PM_BDI
Description
The ODUk_PM_BDI is a ODUk PM backward defect indication. The alarm is generated when
the PM section at the opposite station detects a signal failure and sends the BDI alarm back to
the local station.
Issue 04 (2010-10-20)

3-27

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services borne by the optical interface would be unavailable.
Possible Causes
l
ODUk_PM_BDI signals.
Cause 1 for the alarm generated on the WDM side: The WDM side of corresponding board
at the opposite station reports the ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI,
ODUk_PM_TIM alarms, and then sets BDI alarm back to the local station.
Query whether there is an alarm with higher severity on the board by using the U2000. If
there is, handle the alarm with higher severity.
ODUk_PM_BDI signals.
Procedure
1.
l
If the alarm is reported from the client side, eliminate the alarm according to the
manual of the client equipment.
Cause 1 for the alarm generated on the WDM side: The WDM side of corresponding board
at the opposite station reports the ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI,
ODUk_PM_TIM alarms, and then sends the BDI alarm back to the local station.
1.
If the alarm is reported from the WDM side, check whether the corresponding OTU
board at the opposite station receives the ODUk_PM_AIS, ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_TIM alarms by using the U2000. If yes, handle the
corresponding alarms at the opposite station.
----End
Related Information
ITU-T G.709
3.1.18 ODUk_PM_DEG
Description
The ODUk_PM_DEG alarm indicates that the ODUk PM signal is degraded. This alarm is
generated when the BIP8 detection mode is bursty mode and the signal degradation or bit error
3-28

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
count exceeds the threshold. This alarm is generated when the BIP8 detection mode is poisson
mode and the signal degradation exceeds the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the services borne on the optical interface would generate bit errors,
which makes the service signals unavailable.
Possible Causes
l
Cause 1: The input optical power of the board is abnormal.
Cause 2: The fiber of the transmission line is abnormal.
Cause 1: The input optical power of the board is abnormal.
Procedure
1.
Use the U2000 to browse alarms of the entire network to confirm the slot ID, interface
ID, and channel ID of the board that generates this alarm.
2.
Check whether the input optical power of the point that first generates the alarm is
within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description .
3.
If the optical power is not within the normal range, adjust the input optical power of
the board to a proper value.
Cause 2: The fiber of the transmission line is abnormal.

1.
If the alarm persists, check whether the fiber meets the following requirements:
The bending radius is not less than 40 mm.
The optical interface connector is well installed.
The fiber connector is clean.
The cable is intact.
2.
l
Issue 04 (2010-10-20)
If the fiber does not meet the requirements, remove the fault.

3-29

Transport Platform
3 Alarm Processing
1.
----End
Related Information
ITU-T G.709
3.1.19 ODUk_PM_EXC
Description
The ODUk_PM_EXC alarm indicates that the ODUk PM section BIP8 error count exceeds the
threshold. This alarm is generated when the BIP8 detection mode is poisson mode and bit error
count exceeds the threshold.
k indicates the level of rate and its value is 1, 2, or 5G.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The alarm has an influence on the QoS of the service signals.
Possible Causes
l
Cause 1: The attenuation of the received signals is excessively high, and the fiber of the
transmission line is abnormal.
Cause 2: The transmit part of the opposite station is faulty.
Cause 3: The receive part of the local station is faulty.
Cause 1: The attenuation of the received signals is excessively high, and the fiber of the
transmission line is abnormal.
Procedure
3-30
1.
Check whether the receive optical power of the interface is within the normal range
by using the U2000. For the optical power specification of the specific board, refer to
"Technical Specifications" of the Product Description .
2.
If the receive optical power of the board at the local station is excessively low, clear
the alarm according to the handling procedure of the IN_PWR_LOW alarm.
Issue 04 (2010-10-20)

Transport Platform
3.
If the alarm persists, check whether the transmit optical power of the corresponding
interface on the upstream board is within the normal range by using the U2000. For
the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description . If the transmit optical power of the board
in the upstream station is excessively low, clear the alarm according to the handling
procedure of the OUT_PWR_LOW alarm.

1.
3 Alarm Processing
Loop back the transmit optical interface and receive optical interface on the WDM
side of the OTU board at the upstream station. If the bit error exists, clear the bit error
fault of the upstream station.
Cause 3: The receive part at the local station is faulty.

1.
If the alarm persists, replace the faulty board at the local station. For details, refer to
----End
Related Information
ITU-T G.709
3.1.20 OPS_PS_INDI
Description
Indication of optical channel protection switching. The alarm is generated when the optical
channel protection switching of the services succeeds.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
The protection group type. For example,

0x03 stands for the 1+1 optical channel protection.
0x05 stands for the SNCP protection.
Issue 04 (2010-10-20)

3-31

Transport Platform
3 Alarm Processing
Name
Meaning
Parameters 2 and 3 Indicates the ID of the protection group in which the alarm is generated.
For example, 0x00 0x01 denotes protection group 1.

The protection switching is performed to the system. The services work in the protection channel
and are not interrupted. You need to locate the cause for protection switching and clear the related
fault. Otherwise the services might be interrupted.
Possible Causes
l
Cause 1: The external switching command (such as forced switching or manual switching)
is performed and the switching is successful.
Cause 2: The services in the working channel are abnormal. The services are automatically
switched from the working channel to the protection channel.
Cause 1: The external switching command (such as forced switching or manual switching)
is performed and the switching is successful.
Procedure
1.
On the U2000 query the switching status of the protection group. If the switching
status is in the forced switching or manual switching status, check whether the external
switching is the need for normal working.If the external switching is the need for
normal working, there is no need to handle the alarm.
2.
If the external switching is not the need for normal working, clear the external
switching by issuing the clear switching command.
Cause 2: The services in the working channel are abnormal. The services are automatically
switched from the working channel to the protection channel.
1.
On the U2000 query the status of the working channel.If the working channel is in the
switching state, check whether the alarms with higher priority exist on the related
boards at the local station such asR_LOS, R_LOF or B1_EXC If yes, handle the
alarms that trigger the protection switching by priority.
2.
If the alarm persists, you need to solve the BER-related problem. For the alarm
handling, refer to "Troubleshooting Bit Errors" of the Troubleshooting.
3.
If the alarm persists, you need to solve the fiber-related problem. For how to
troubleshoot the specific fault, refer to "Troubleshooting Optical Power Anomalies"
of the Troubleshooting.
----End
Related Information
For the principles of protection and the trigger conditions of the alarm, see the Feature
Description.
3-32

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.1.21 OSC_LOS
Description
The OSC_LOS alarm indicates the loss of input optical power on receiving line. This alarm is
generated when the input optical power of the OSC board exceeds the LOS threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

There is a fiber break in the receive direction and this can cause loss of the monitoring signals.
Possible Causes
l
Cause 1: A certain optical interface on the board that reports the alarm is not connected to
a fiber.
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.
Query the alarm on the U2000 and record the IDs of the optical interface and channel where
the alarm is generated.
Cause 1: A certain optical interface on the board that reports the alarm is not connected to
a fiber.
Procedure
1.
l
Cause 2: The laser of the board at the opposite station is shut down.
1.
Use the U2000 to check whether the laser of the specific board at the opposite station
is open. If not, open the laser of the board.
Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs
on the transmission line.
1.
Issue 04 (2010-10-20)
Check whether the fiber jumper is connected to the optical interface of the board at
the local station. If not, connect the fiber jumper.
On the U2000 check whether the receive optical power at the optical interface where
the alarm is generated is within the normal range. For the optical power specification
of the specific board, refer to "Technical Specifications" of the Product
Description .
3-33

Transport Platform
3 Alarm Processing
2.
If the receive optical power is not within the normal range, clear the alarm according
to the handling procedure for the IN_PWR_LOW or IN_PWR_HIGH.
3.
If the receive optical power is normal, check the fiber connector. If the fiber connector
is dirty or damaged, clean or replace the fiber connector.

1.

1.
----End
Related Information
None.
3.1.22 OUT_PWR_HIGH
Description
The OUT_PWR_HIGH alarm indicates that the output optical power is excessively high. This
alarm is generated when the laser output optical power crosses the upper threshold.
Reported from the WDM or client side: WDM side, client side
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
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 alarm is caused by the faulty module of the laser or the faulty board, the board is
working abnormally, which affects the transmitting and receiving of the services.
Possible Causes
Cause 1: The optical module of laser is faulty or the board is faulty.
3-34

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
l
Query the alarm on the U2000 and record the IDs of the optical interface and channel where
the alarm is generated.
Cause 1: The optical module of laser is faulty or the board is faulty.

1.
If the input optical power is within the normal range, the optical module of the laser
of the board might be faulty. If the board uses pluggable optical modules, replace the
specific pluggable optical module. For details, refer to "Replacing Pluggable Optical
Modules" of the Parts Replacement.
2.
If the board does not support pluggable optical modules, replace the board. For details,
refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None.
3.1.23 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that the optical module is offline. The alarm
is generated when the board detects that the optical module is offline.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Absence of the optical module would lead to the interruption of services borne by the
corresponding optical interface.
Possible Causes
l
Cause 1: The optical module does not exist or is not correctly inserted in the slot.
Cause 2: The optical module or the board is faulty.
is generated.
Procedure
Issue 04 (2010-10-20)

3-35

Transport Platform
3 Alarm Processing
Cause 1: The optical module does not exist or is not correctly inserted in the slot.
1.
Install the optical module properly.

1.
Perform a cold reset on the faulty board through the U2000.
2.
If the alarm persists, the board that reports the alarm may be faulty. If the board uses
pluggable optical modules, replace the specific pluggable optical module. For details,
refer to "Replacing Pluggable Optical Modules" of the Parts Replacement.
3.
If the optical module is not pluggable, replace the faulty board. For details, refer to
----End
Related Information
None.
3.1.24 POWER_DIFF_DEFECT
Description
Power difference between optical monitoring active and standby channels. The alarm is
generated when the power difference between the active and standby optical monitoring signals
exceeds the degraded threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm

None.
Possible Causes
l
Cause 1: The power difference between the active and standby optical signals transmitted
by the board at the opposite station is rather large.
Cause 2: The optical power attenuation of the optical signals in transmission is very large
or the optical attenuator that enables very large attenuation is added to the board at the
opposite station. As a result, the power difference of the optical signals at the receive end
is rather large.
is generated.
Cause 1: The power difference between the active and standby optical signals transmitted
by the board in the opposite station is rather large.
Procedure
3-36

Issue 04 (2010-10-20)

Transport Platform
1.
l
If the alarm persists, adjust the optical power of the active and standby channels at the
transmit end to obtain a difference within 3 dB.
Cause 2: The optical power attenuation of the optical signals in transmission is very large
or the optical attenuator that enables very large attenuation is added to the board at the
opposite station.
1.
3 Alarm Processing
Adjust the optical power of the active and standby channels at the receive end until
the alarm clears.

1.
----End
Related Information
None.
3.1.25 POWER_FAIL
Description
The POWER_FAIL alarm indicates the power failure. This alarm is generated if the power
supply of a board becomes abnormal. For example, there is overvoltage or undervoltage of the
power supply, or the battery on the SCC has no charge.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 04 (2010-10-20)

3-37

Transport Platform
3 Alarm Processing
Name
Meaning
Parameter 1 Indicates the state of the power supply in which the alarm is generated. For
example:
0x12 indicates the overvoltage of the 12 V active power supply.
0x13 indicates the undervoltage of the 12 V active power supply.
0x14 indicates the overvoltage of the 12 V standby power supply.
0x15 indicates the undervoltage of the 12 V standby power supply.
0x41 indicates the overvoltage of the 3.3 V active power supply.
0x42 indicates the undervoltage of the 3.3 V active power supply.
0x4f indicates the overvoltage of the 48 V active power supply.
0x50 indicates the undervoltage of the 48 V active power supply.
0x51 indicates the overvoltage of the 48 V standby power supply.
0x52 indicates the undervoltage of the 48 V standby power supply.
0x55 indicates that the first input voltage of the APIU is abnormal.
0x56 indicates that the second input voltage of the APIU is abnormal.
0x57 indicates that the first output voltage of the APIU is abnormal.
0x58 indicates that the second output voltage of the APIU is abnormal.
0x59 indicates that on the APIU, the temperature of the first channel of power
supply is excessively high and the power supply performs active protection,
which causes the power supply failure.
0x5A indicates that on the APIU, the temperature of the second channel of power
supply is excessively high and the power supply performs active protection,
which causes the power supply failure.

l
When this alarm is reported by the SCC board, the system time is lost if the system is
powered off.
When this alarm is reported by other boards,

If the active power supply fails and the standby power supply is normal, which can
cause the switching of the power supply, there is no impact on the services.
If the active power supply fails and the standby power supply fails too, the services may
be interrupted.
Possible Causes
3-38
Cause 1: If this alarm is reported by the SCC board, it indicates that the battery on the SCC
has no charge.
Cause 2: If this alarm is reported by other boards, it indicates the power supply of the board
is faulty or aged.
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
l
Cause 1: If this alarm is reported by the SCC board, it indicates the battery on the SCC has
no charge.
1.
Replace the faulty SCC board, For details, refer to "Replacing a Board" of the
Supporting Tasks.
Cause 2: If this alarm is reported by other boards, it indicates the power supply of the board
is faulty or aged.
1.
Replace the faulty board, For details, refer to "Replacing a Board" of the Supporting
Tasks.
----End
Related Information
None
3.1.26 PUMP_COOL_EXC
Description
The PUMP_COOL_EXC alarm indicates that the cool current of the pump laser exceeds the
threshold. This alarm is generated when the laser cooling current crosses the upper threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

When this alarm is reported, the optical components sharply age and the performance of output
signals degrades.
Possible Causes
l
Cause 1: The ambient temperature is excessively high or low.
Cause 2: The pump laser temperature is excessively high or low.
Cause 1: The ambient temperature is excessively high or low.
Procedure
Issue 04 (2010-10-20)

3-39

Transport Platform
3 Alarm Processing
1.
Check whether the ambient temperature is normal. If the ambient temperature is

excessively high or very low, adjust the temperature to ensure that the temperature is
within the normal range.
Cause 2 and cause 3: The pump laser temperature is excessively high or low; the board that
reports the alarm is faulty.
1.
----End
Related Information
None.
3.1.27 R_LOF
Description
The R_LOF(OTN) alarm indicates the loss of frame on the receiving line. This alarm is generated
when the frame alignment processing is out of frame (OOF) in consecutive 3 ms.
Reported from the WDM side or client side:
l
WDM side: Detect for this alarm when there are SDH frames in the services accessed on
the WDM side.
Client side: Detect for this alarm when the SDH services are accessed on the client side.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

l
The board fails in locating the data frame of the received SDH signals; the client services
fail.
The board detects this alarm, and the boards supporting protection switching perform
protection switching.
Possible Causes
3-40
Cause 1 for the alarm generated on the client side: The input signals from the client side
contain the R_LOF signal.
Cause 1 for the alarm generated on the WDM side: The receive optical power or the OSNR
of the local board is abnormal.
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Cause 2 for the alarm generated on the WDM side: The signals transmitted by the
upstream OTU have no SDH frame structure.
faulty.
Cause 4 for the alarm generated on the WDM side: The input signals from the upstream
station contain the R_LOS or R_LOF signal.
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.
Procedure
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
Issue 04 (2010-10-20)
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.
Replacement.
2.
If the board does not support pluggable optical modules, Replace the faulty board.
Cause 1 and cause 2 for the alarm generated on the WDM side: The receive optical power
or the OSNR of the local board is abnormal; the signals transmitted by the upstream OTU
have no SDH frame structure.
1.
If the WDM side reports this alarm, use the U2000 to check whether client side of the
board at the opposite station reports the R_LOF alarm. If yes, remove the fault with
the solution for client-side R_LOF.
2.
If the alarm persists, use the U2000 to check whether the receive optical power of the
WDM-side interface of the alarm-reporting board is in the normal range. For the
optical power specification of the specific board, refer to "Technical Specifications"
of the Product Description .
3.
If the optical power is abnormal, clear the alarm as the IN_PWR_LOW or

IN_PWR_HIGH alarm.
4.
If the receive optical power is normal, use the SDH meter to receive signals transmitted
by the WDM side of the board at the opposite station. Check whether the signal is
white spectrum or is not in the SDH format. If it does not comply with the requirement,
3-41

Transport Platform
3 Alarm Processing
replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
l
faulty.
1.
If the alarm persists, the board may be faulty. Replace the faulty board at the local
station. For details, refer to "Replacing a Board" of the Supporting Tasks.
Cause 4 for the alarm generated on the WDM side: The input signals from the upstream
station contain the R_LOS or R_LOF signal.
1.
If the alarm persists, clear the alarm of the equipment at the upstream station.
----End
Related Information
None
3.1.28 R_LOS
Description
The R_LOS(OTN) alarm indicates the loss of signal on receiving line. This alarm is generated
when the receive side receives no signals.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

There is a fiber break in the receive direction and the services on this port are interrupted.
Possible Causes
3-42
Cause 1 for the alarm generated on the client side: The fiber jumper is not connected to the
optical interface of the board.
Cause 2 for the alarm generated on the client side: The line loss is excessively large or there
is a fiber cut.
Cause 3 for the alarm generated on the client side: Both OTUk_LOF and IN_PWR_LOW
alarms are generated on the client side.
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected to
the optical interface of the board.
Cause 2 for the alarm generated on the WDM side: The line loss is excessively large or
there is a fiber cut.
Cause 3 for the alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
Cause 4 for the alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
Cause 5 for the alarm generated on the WDM side: Both OTUk_LOF and IN_PWR_LOW
alarms are generated on the WDM side.
is generated.
Cause 1 for the alarm generated on the client side: The fiber jumper is not connected to the
optical interface of the board.
Procedure
1.
l
Cause 2 for the alarm generated on the client side: The line loss is excessively large or there
is a fiber cut.
1.
Check whether the receive optical power of the interface of the board at the local
station is within the normal range by using the U2000. For the optical power
Description .
If the optical power is abnormal, clear the alarm as IN_PWR_LOW or
IN_PWR_HIGH.
If the receive optical power is normal, check the fiber connector. If the fiber
connector is dirty or damaged, clean the fiber connector. For details, see the
Supporting Tasks.
Cause 3 for the alarm generated on the client side: Both OTUk_LOF and IN_PWR_LOW
alarms are generated on the client side.
1.
1.
Cause 2 for the alarm generated on the WDM side: The line loss is excessively large or
there is a fiber cut.
1.
Issue 04 (2010-10-20)
Cause 1 for the alarm generated on the WDM side: The fiber jumper is not connected to
the optical interface of the board.
1.
On the U2000, check whether OTUk_LOF and IN_PWR_LOW alarms are geneated
on the client side of the board. If yes, see the handling procedure of the
OTUk_LOF and IN_PWR_LOW alarm for troubleshooting.
Check whether the receive optical power of the interface of the board at the local
station is within the normal range by using the U2000. For the optical power
Description .
3-43

Transport Platform
3 Alarm Processing
If the optical power is abnormal, clear the alarm as IN_PWR_LOW or

IN_PWR_HIGH.
If the receive optical power is normal, check the fiber connector. If the fiber
connector is dirty or damaged, clean the fiber connector. For details, see the
Supporting Tasks.
l
Cause 3 for the alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
1.
Use the U2000 the check whether the board laser of the opposite station is open. If
not, open the laser.
Cause 4 for the alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
1.
If the alarm persists, check whether the board at the opposite station or the board at
the local station supports pluggable optical modules.
If ...
Then ...
modules,
Replacement.
l

Tasks.
Cause 5 for the alarm generated on the WDM side: Both OTUk_LOF and IN_PWR_LOW
alarms are generated on the WDM side.
1.
On the U2000, check whether OTUk_LOF and IN_PWR_LOW alarms are geneated
on the WDM side of the board. If yes, see the handling procedure of the
OTUk_LOF and IN_PWR_LOW alarm for troubleshooting.
----End
Related Information
None
3.1.29 REM_SF
Description
The REM_SF alarm indicates that the remote client-side service is 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
3-44

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Services borne by the client side of the board are interrupted.
Possible Causes
l
Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the
opposite end.
Cause 2: The client side of the OTU board at the opposite end is faulty.
Cause 1: There is an R_LOS or R_LOF alarm on the client side of the OTU board at the
opposite end.
Procedure
1.
Check whether there is an R_LOS or R_LOF alarm on the client side of the OTU
board at the opposite station on the U2000. If there is an R_LOS or R_LOF alarm, see
R_LOS or R_LOF to clear the alarm.
Cause 2: The client side of the OTU board at the opposite end is faulty.
1.
Replace the OTU board at the opposite station.For details, refer to "Replacing a Board"
----End
Related Information
None.
3.1.30 SECU_ALM
Description
The SECU_ALM alarm indicates an illegal login. The alarm is generated when the login fails
after four consecutive login failure performed by the same user.
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Issue 04 (2010-10-20)

3-45

Transport Platform
3 Alarm Processing
Parameters
None.

The alarm automatically ends with no impact on the system.
Possible Causes
l
Cause 1: This alarm can be caused by illegal login, such as login with an incorrect password
or a user not existing.
Cause 1: This alarm can be caused by illegal login, such as login with an incorrect password
or a user not existing.
Procedure
1.
l
Check whether there are users illegally logging in to the NE. If yes, clear the user that
is illegally logged in to.

1.
If the alarm persists when there is no user who logged in to the NE illegally, replace
the board. For details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None.
3.1.31 SUBRACK_ID_CONFLICT
Description
The SUBRACK_ID_CONFLICT is an alarm indicating conflict of the subrack ID.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
3-46
Parameter
Description
Parameter 1
Indicates the conflict subrack ID.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

The command cannot be correctly delivered to the corresponding subrack, and the board cannot
be reached by the U2000.
Possible Causes
Cause 1: The subracks are in the master/slave mode, and the NE software of the SCC board on
the master subrack detects that the subrack ID conflict.
Procedure
l
Cause 1: The subracks are in the master/slave mode, and the NE software of the SCC board
on the master subrack detects that the subrack ID conflict.
1.
Obtain the conflict subrack ID according to the alarm parameter, and then change the
ID of the slave subrack who goes online later on the U2000. After the SCC board of
the slave subrack is reset automatically, the alarm is cleared. For specific operations,
see the Feature Description.
----End
Related Information
None
3.1.32 TD
Description
The TD alarm indicates the transmitter degrade. The alarm is generated when the bias current
of the laser exceeds the degrade threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

Possibly the board laser cannot work normally, or the output light of the laser is of poor quality
or with bit errors and further cause service break.
Possible Causes
Cause 1: The laser is aged.
Issue 04 (2010-10-20)

3-47

Transport Platform
3 Alarm Processing
Cause 2: The air conditioner (A/C) does not work for a certain cause and thus the temperature
is high, which causes the TD alarm.
Procedure
l
Cause 1: The laser is aged.

1.
Replacement.
2.
If the board is not pluggable, replace the faulty board. For details, refer to "Replacing
a Board" of the Supporting Tasks.
Cause 1: The air conditioner (A/C) does not work for a certain cause and thus the
temperature is high, which causes the TD alarm.
1.
Start the air conditioner (A/C) and then the alarm is cleared automatically.
2.
Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
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.1.33 TF
Description
The TF alarm indicates a transmission failure. The alarm is generated when the transmit optical
power of the laser exceeds the threshold of the output optical power of the laser.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

The laser transmission becomes faulty, which causes service interruption.
Possible Causes
Cause 1: The laser module is damaged, or the laser is aged.
3-48

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
l
Cause 1: The laser module is damaged, or the laser is aged.

1.
Perform a cold reset on the faulty board through the U2000.
2.
If the alarm persists, check whether the board that reports this alarm supports pluggable
optical modules.
If ...
Then ...
modules,
Replacement.

Tasks.
----End
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after longterm operation and thus the laser emitting efficiency decreases. To ensure constant output optical
power, the laser bias current needs to be increased. Hence, the bias current is an index that reflects
the aging degree of the laser.
3.1.34 WRG_BD_TYPE
Description
The WRG_BD_TYPE alarm indicates the incorrect board type. The alarm is generated when
the logic board and the physical board are not consistent.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The type of the logical board is inconsistent with the type of the physical board. The board cannot
work normally.
Issue 04 (2010-10-20)

3-49

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

1.
----End
Related Information
None.
3.2 Alarm Processing

This chapter describes information relevant to alarm handling, including alarm descriptions,
alarm parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.
NOTE
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.
3.2.1 AD_CHECK_FAIL
3.2.2 AU_AIS
3.2.3 AU_LOP
3.2.4 B1_SD
3-50

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.5 B2_EXC
3.2.6 B2_SD
3.2.7 B3_EXC
3.2.8 B3_SD
3.2.9 BD_STATUS
3.2.10 BOOTROM_BAD
3.2.11 CFG_VERIFY
3.2.12 CFGDATA_OUTRANGE
3.2.13 DBMS_ERROR
3.2.14 DBMS_PROTECT_MODE
3.2.15 DCC_CHAN_LACK
3.2.16 DOWN_E1_AIS
3.2.17 E1_LOC
3.2.18 ETH_LINK_DOWN
3.2.19 EXT_SYNC_LOS
3.2.20 FAN_FAIL
3.2.21 FEC_LOF
3.2.22 FEC_OOF
3.2.23 FPGA_ABN
3.2.24 FUSE_ALARM
3.2.25 GPON_DS_LOF
3.2.26 GPON_RUF
3.2.27 GPON_US_LOF
3.2.28 HARD_BAD
3.2.29 HP_LOM
3.2.30 HP_RDI
3.2.31 HP_REI
3.2.32 HP_SLM
3.2.33 HP_TIM
3.2.34 HP_UNEQ
3.2.35 J0_MM
3.2.36 LASER_MOD_ERR_EX
3.2.37 LCS_DAYS_OF_GRACE
Issue 04 (2010-10-20)

3-51

Transport Platform
3 Alarm Processing
3.2.38 LCS_EXPIRED
3.2.39 LCS_FILE_NOT_EXIST
3.2.40 L_SYNC
3.2.41 LOCAL_FAULT
3.2.42 LP_R_FIFO
3.2.43 LP_RDI
3.2.44 LP_REI
3.2.45 LP_RFI
3.2.46 LP_SLM
3.2.47 LP_T_FIFO
3.2.48 LP_TIM
3.2.49 LP_UNEQ
3.2.50 LTI
3.2.51 MDL_ALARM
3.2.52 MS_REI
3.2.53 MSSW_DIFFERENT
3.2.54 NESTATE_INSTALL
3.2.55 NO_BD_PARA
3.2.56 NO_BD_SOFT
3.2.57 ODUk_LOFLOM
3.2.58 ODUk_PM_LCK
3.2.59 ODUk_PM_OCI
3.2.60 ODUk_PM_TIM
3.2.61 OPS_MAIN_BAK_ATTR_DIFF
3.2.62 OPS_STA_INDI
3.2.63 OOL
3.2.64 OPUk_PLM
3.2.65 OTUk_AIS
3.2.66 OTUk_BDI
3.2.67 OTUk_DEG
3.2.68 OTUk_EXC
3.2.69 OTUk_LOF
3.2.70 OTUk_LOM
3-52

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.71 OTUk_TIM
3.2.72 OUT_PWR_LOW
3.2.73 PATCH_ACT_TIMEOUT
3.2.74 PATCH_DEACT_TIMEOUT
3.2.75 PATCH_ERR
3.2.76 PATCH_NOT_CONFIRM
3.2.77 PATCH_PKGERR
3.2.78 PATCHFILE_NOTEXIST
3.2.79 POWER_DIFF_OVER
3.2.80 PRBS_LSS
3.2.81 PUM_BCM_ALM
3.2.82 PUM_TEM_ALM
3.2.83 PWR_MAJ_ALM
3.2.84 R_LOC
3.2.85 RELAY_ALARM_CRITICAL
3.2.86 RELAY_ALARM_IGNORE
3.2.87 RELAY_ALARM_MAJOR
3.2.88 RELAY_ALARM_MINOR
3.2.89 REM_SD
3.2.90 REMOTE_FAULT
3.2.91 S1_SYN_CHANGE
3.2.92 SUB_RACK_OFFLINE
3.2.93 STORM_CUR_QUENUM_OVER
3.2.94 SUBRACK_TYPE_MISMATCH
3.2.95 SWDL_ACTIVATED_TIMEOUT
3.2.96 SWDL_AUTOMATCH_INH
3.2.97 SWDL_CHGMNG_NOMATCH
3.2.98 SWDL_COMMIT_FAIL
3.2.99 SWDL_INPROCESS
3.2.100 SWDL_NEPKGCHECK
3.2.101 SWDL_PKG_NOBDSOFT
3.2.102 SWDL_PKGVER_MM
3.2.103 SWDL_ROLLBACK_FAIL
Issue 04 (2010-10-20)

3-53

Transport Platform
3 Alarm Processing
3.2.104 SYNC_C_LOS
3.2.105 SYSLOG_COMM_FAIL
3.2.106 TEM_HA
3.2.107 TEM_LA
3.2.108 TEMP_ALARM
3.2.109 TEMP_OVER
3.2.110 THUNDERALM
3.2.111 TU_AIS
3.2.112 TU_LOP
3.2.113 UP_E1_AIS
3.2.114 VCXO_LOC
3.2.1 AD_CHECK_FAIL
Description
The AD_CHECK_FAIL alarm is an alarm indicating AD (analog to digital converter) self check
failure. This alarm is reported when the AD chip on the board is faulty.
Reported from the WDM side or client side: NA.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter Description
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.
3-54
This alarm may affect services.
Parameters relevant to the AD chip on the board, such as board input/output optical power,
fail to be queried on the U2000. As a result, maintenance engineers can neither obtain the
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
current operation performance data of the network nor find in time any dormant problems
of the network operation. The alarm may interrupt the service in the system or even make
the system down. Hence, this alarm should be handled immediately.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
3.2.2 AU_AIS
Description
The AU_AIS is an alarm indicating that the AU pointer in the signal received by the line is all
"1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the AU_AIS alarm occurs, it indicates that the AU4 services are unavailable.
The system will send an HP_RDI alarm to the opposite end. If SNCP is configured, the SF
switching occurs.
Possible Causes
The possible causes of the AU_AIS alarm are as follows:
l
The higher-level alarms such as MS_AIS, R_LOS, and R_LOF cause the AU_AIS alarm
in the corresponding VC-4 channel.
The services are incorrectly configured.
The opposite station sends the AU_AIS alarm.
Issue 04 (2010-10-20)

3-55

Transport Platform
3 Alarm Processing
The transmit part at the opposite station is faulty.
The receive part of the local station is faulty.
Procedure
Step 1 Check whether section-level alarms are present on the line board of the upstream station. If VC-4
higher order pass-through services are configured on the line board, the AU_AIS alarm of the
corresponding AU4 path will be triggered.
Options
Description
There is the R_LOS, R_LOF, R_LOC, or

MS_AIS alarm on the line board of the
upstream station
Refer to the corresponding section in this

document to clear the alarm.
There is no such alarms as mentioned
Proceed to the next step.
Step 2 Check whether the line board at the opposite station is configured for the AU_AIS alarm inserted
to the transmit end.
Options
Description
The transmit end of the line board at the

opposite station is inserted with the AU_AIS
alarm
Cancel the inserted AU_AIS alarm.
The transmit end of the line board at the

opposite station is not inserted with the
AU_AIS alarm
Step 3 Check the service configuration at the local and opposite ends and issue the configurations again.
Step 4 View alarms on the U2000 to check whether the AU_AIS alarm is cleared.
Options
Description
If this alarm is cleared
The fault is removed. End the alarm handling.
If this alarm persists
Step 5 Check whether the transmitting part of the line board on the opposite station is faulty.
3-56
Options
Description
If the line board of the opposite station is

faulty
Perform a reset on the board or replace the

board to check whether the alarm is cleared.
The transmit part of the line board at the

opposite station is normal

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Step 6 Check the line board of the local station. Perform a reset to the board or replace the board. Then
check whether the alarm is cleared.
----End
Related Information
None
3.2.3 AU_LOP
Description
The AU_LOP is an alarm indicating loss of the AU pointer.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the AU_LOP alarm occurs, the AU-4 services are unavailable.
The system will send an HP_RDI alarm to the opposite end. If SNCP is configured, the SF
switching occurs.
Possible Causes
The possible causes of the AU_LOP alarm are as follows:
l
The transmitting part of the opposite station is faulty, or the cross-connect and timing board
is faulty.
The service on the opposite station is incorrectly configured.
The number of bit errors received at the local station exceeds the specified value.
Procedure
Step 1 View alarms on the U2000 and check whether other section-level bit error alarms exist on the
board that reports the AU_LOP alarm.
Issue 04 (2010-10-20)
Options
Description
If the B1_EXC, B1_SD, B2_EXC, or B2_SD

alarm exist...


3-57

Transport Platform
3 Alarm Processing
Options
Description
There are no such alarms as B1_EXC,

B1_SD, B2_EXC and B2_SD
Step 2 Check whether the service configuration is correct on the local and opposite stations. If not,
configure them to correct.
Step 3 After verifying that the service configuration is correct, view alarms on the U2000 to check
whether the AU_LOP alarm is cleared.
Options
Description
Step 4 Check whether the clock board of the opposite end is normal, whether the cross-connect unit
detects the clock. If the clock board of the opposite end or cross-connect board is faulty, replace
the SCC board of the opposite NE.
Step 5 After replacing the SCC board of the opposite end, view alarms on the U2000 to check whether
the AU_LOP alarm is cleared.
Options
Description
Step 6 Perform the loopback for the stations at both ends of the line. Locate and replace the faulty line
board.
----End
Related Information
None.
3.2.4 B1_SD
Description
The B1_SD(OTN) alarm is an alarm indicating that the regenerator section signals are degraded.
The alarm occurs when the received signals in SDH frame degrade and the B1 bit errors in the
multiplex section exceed the signal degrade (SD) threshold.
l
3-58
on the WDM side exceed the signal degrade threshold.
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
on the client side exceed the signal degrade threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

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

3-59

Transport Platform
3 Alarm Processing
Related Information
None
3.2.5 B2_EXC
Description
Multiplex section (B2) excessive errors alarm. The alarm is generated when the B2 bit errors in
the multiplex section exceeds the threshold.
l
on the WDM side exceed the B2 bit error threshold.
on the client side exceed the B2 bit error threshold.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

The B2 bit errors in the service signals received by the board exceeds the threshold of the B2
bit errors set on the board. The generation of the alarm has an influence on the QoS of the service
signals.
Possible Causes
l
Procedure
the U2000. For the optical power specifications of the specific board, see the Product
Description. If the receive optical power of the board at the local station is excessively low, clear
Step 2 If the alarm persists, check whether the launched optical power of the corresponding interface
on the upstream board is within the normal range by using the U2000. For the optical power
specifications of the specific board, see the Product Description. If the launched optical power
of the board in the upstream station is excessively low, clear the alarm according to the handling
3-60

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using the
U2000 and loop back the transmit optical interface and receive optical interface on the WDM
side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault of
the upstream station.
Replacement.
Step 6 If the alarm bursts, it may be caused by that the transmission line is influenced by various noise
sources. Search the jam source that may cause the burst bit error and remove the interference.
----End
Related Information
None
3.2.6 B2_SD
Description
Multiplex section (B2) signal degraded alarm. The alarm is generated when the B2 bit errors in
the multiplex section exceeds the signal degrade (SD) threshold.
l
on the WDM side exceed the signal degrade (SD) threshold.
on the client side exceed the signal degrade (SD) threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The B2 bit errors in the service signals received by the board exceeds the degrade threshold of
signals set on the board. The generation of the alarm has an influence on the QoS of the service
signals.
Possible Causes
l
Issue 04 (2010-10-20)

3-61

Transport Platform
3 Alarm Processing
Procedure
the U2000. For the optical power specifications of the specific board, see the Product
Description. If the receive optical power of the board at the local station is excessively low, clear
Step 2 If the alarm persists, check whether the launched optical power of the corresponding interface
on the upstream board is within the normal range by using the U2000. For the optical power
specifications of the specific board, see the Product Description. If the launched optical power
of the board in the upstream station is excessively low, clear the alarm according to the handling
Step 3 If the alarm persists, check whether bit error alarm exists on the upstream station by using the
U2000 and loop back the transmit optical interface and receive optical interface on the WDM
side of the OTU board on the upstream station. If the bit error exists, clear the bit error fault of
the upstream station.
Replacement.
Step 6 If the alarm bursts, it may be caused by that the transmission line is influenced by various noise
sources. Search the jam source that may cause the burst bit error and remove the interference.
----End
Related Information
None
3.2.7 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
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None
3-62

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

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
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.
Query current alarms on the U2000. Determine the number of the interface that reports the
alarm. For details, see Querying the Current Alarms and Performance Events of a NE on
the U2000 in the Supporting Task.
Procedure
1.
Check whether the transmit power at the opposite station and the receive power at the
local station meet the specifications of the interfaces. For details on optical power
specification of the board, see "Technical Specifications" of the Product
Description. For details, see Querying Optical Power on the U2000 in the Supporting
Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the
manufacturer information about the board optical module.
2.
Issue 04 (2010-10-20)
If...
Then...
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,
See cause 4.
Check whether the optical connector is normal.

If...
Then...
The connector is loose
Tighten the optical connector. Check whether the alarm

is cleared. If the alarm persists, proceed to the next step.

3-63

Transport Platform
3 Alarm Processing
If...
Then...
The interface is normal Proceed to the next step.

3.
Check whether the connector is dirty. For details, see Inspecting and Cleaning the
Fiber-Optic Connectors in the Supporting Task.
If...
Then...
The connector is dirty
Clean the optical connector. For details, see

l Cleaning Optical Fiber Connectors Using Cartridge
Cleaners
l Cleaning Optical Fiber Connectors Using Lens
Tissue
l Cleaning Optical Adapters Using Optical Cleaning
Sticks
in Supporting Task. Then, check whether the alarm is
cleared. If the alarm persists, proceed to the next step.
The connector is normal Proceed to the next step.

4.
5.
l
3-64
Check whether the attenuation value of the optical attenuator is proper according to
the specified receive optical power. For details on optical power specifications of the
board, see "Technical Specifications" of the Product Description.
If...
Then ...
The value of optical attenuation is

improper,
Adjust the attenuation to the proper

value. For details, see 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.

proper,
Check whether the fiber is faulty. Especially, check whether the bending radius of a
fiber jumper is within the normal range, and check whether the fiber from the
equipment to the ODF and the fiber outside the equipment room are pressed. If the
bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If
the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm
persists, see cause 2.

1.
Check the ambient temperature of the equipment room. If the temperature is higher
than 45C or is lower than 0C, use a cooler/heater to decrease/increase the ambient
temperature.
2.
Check whether the alarm is cleared. If the alarm persists, see cause 3.

Issue 04 (2010-10-20)

Transport Platform
1.
3 Alarm Processing
Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If...
Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
No bit error alarm is reported,
See cause 4.
2.
If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the local faulty board. For details, see Parts
Replacement.
3.

1.
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
3.2.8 B3_SD
Description
The B3_SD is an alarm indicating that the higher order path B3 signals received on the line are
degraded. When a line board detects that the bit errors of the higher order path signals exceed
the specified B3_SD alarm threshold but are lower than the specified B3_EXC alarm threshold
by detecting the B3 byte, the B3_SD alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None
Issue 04 (2010-10-20)

3-65

Transport Platform
3 Alarm Processing

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
G1 byte to the opposite station, indicating the HP_RDI alarm. Consequently, the opposite
station generates the HP_RDI alarm.
Possible Causes
The possible causes of the B3_SD alarm are as follows:
l
Query current alarms on the U2000. Determine the number of the interface that reports the
alarm according to Parameter 1. For details, see Querying the Current Alarms and
Performance Events of a NE on the U2000 in the Supporting Task.
Procedure
1.
Check whether the transmit power at the opposite station and the receive power at the
local station meet the specifications of the interfaces. For details on optical power
specification of the board, see "Technical Specifications" of the Product
Description. For details, see Querying Optical Power on the U2000 in the Supporting
Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the
manufacturer information about the board optical module.
2.
3-66
If...
Then...
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,
See cause 4.
Check whether the optical connector is normal.

If...
Then...
The connector is loose
Tighten the optical connector. Check whether the alarm

is cleared. If the alarm persists, proceed to the next step.

Issue 04 (2010-10-20)

Transport Platform
If...
3 Alarm Processing
Then...
The interface is normal Proceed to the next step.

3.
Check whether the connector is dirty. For details, see Inspecting and Cleaning the
Fiber-Optic Connectors in the Supporting Task.
If...
Then...
The connector is dirty
Clean the optical connector. For details, see

l Cleaning Optical Fiber Connectors Using Cartridge
Cleaners
l Cleaning Optical Fiber Connectors Using Lens
Tissue
l Cleaning Optical Adapters Using Optical Cleaning
Sticks
in Supporting Task. Then, check whether the alarm is
cleared. If the alarm persists, proceed to the next step.
The connector is normal Proceed to the next step.

4.
5.
l
Issue 04 (2010-10-20)
Check whether the attenuation value of the optical attenuator is proper according to
the specified receive optical power. For details on optical power specifications of the
board, see "Technical Specifications" of the Product Description.
If...
Then ...

improper,
Adjust the attenuation to the proper

value. For details, see 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.

proper,
Check whether the fiber is faulty. Especially, check whether the bending radius of a
fiber jumper is within the normal range, and check whether the fiber from the
equipment to the ODF and the fiber outside the equipment room are pressed. If the
bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If
the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm
persists, see cause 2.

1.
Check the ambient temperature of the equipment room. If the temperature is higher
than 45C or is lower than 0C, use a cooler/heater to decrease/increase the ambient
temperature.
2.

3-67

Transport Platform
3 Alarm Processing
1.
Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.
CAUTION
The loopback may cause service interruptions.
If...
Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
No bit error alarm is reported,
See cause 4.
2.
module. Otherwise, replace the local faulty board. For details, see Parts
Replacement.
3.

1.
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
3.2.9 BD_STATUS
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
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The board is not in position. Hence, the functions related to the board are unavailable.
3-68

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Possible Causes
l
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.
Procedure
Step 1 Check whether the corresponding board is inserted in the physical slot.
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 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
Step 3 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei
engineers.
----End
Related Information
None
3.2.10 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data check fails. This alarm
occurs when the basic or extended BIOS software of the board is damaged.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 04 (2010-10-20)

3-69

Transport Platform
3 Alarm Processing
Parameter
Description
Parameters 1 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software.
0x02 indicates the extended BIOS software.

When powered on again or reset after a power supply failure, the SCC board cannot be normally
started.
Possible Causes
l
The extended BIOS software of the board is damaged.
The basic BIOS software of the board is damaged.
The SCC board is faulty.
Procedure
Step 1 Determine upon the alarm parameter (0x01 indicates the basic BIOS while 0x02 the extended
BIOS) whether the basic or extended BIOS software of the board is damaged.
Step 2 If the basic BIOS software is faulty, replace the faulty SCC board. For details, see the Parts
Replacement.
Step 3 If the extended BIOS software is damaged, reload the extended BIOS of the SCC board. For
details, see the Upgrade Guide.
Step 4 If the alarm persists, the SCC board may be faulty. Replace the faulty board. For details, see the
Parts Replacement.
----End
Related Information
None
3.2.11 CFG_VERIFY
Description
Configuration is not verified.
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Parameters
None
3-70

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

The configuration data is not taken into effect.
Possible Causes
The alarm is generated when the verification is not performed 15 minutes after the last
configuration command is issued.
Procedure
Step 1 Load the configuration data on the U2000 to issue the configuration information again and verify
it.
----End
Related Information
None
3.2.12 CFGDATA_OUTRANGE
Description
Board configuration data out of range alarm.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 04 (2010-10-20)

3-71

Transport Platform
3 Alarm Processing
Parameter 1 Indicates the type of the configured data that exceeds the threshold or does not
comply with the SCC board.
0x01 denotes the OTU board operating wavelength.
0x02 denotes the attenuation.
0x03 denotes the nominal gain of the amplifier unit.
0x04 denotes the add/drop wavelengths.
0x05 denotes the board operating band.
0x06 denotes the locked value of the pump optical power.
0x07 denotes the inband add/drop wavelengths of the MRx/MBx board.
0x08 denotes the working mode of the optical interface.
0x09 denotes the type of the services to be transmitted.
0x0a denotes the FEC working mode.

The impact of configuration on the system varies with the data type.
l
As for the operating wavelength of the OTU board and wavelengths added to or dropped
from the MRx board, the operating band of the board, this alarm results in the difference
between the wavelengths configured for the cross-connection and the actual wavelengths
(band) of the optical module. As a result, services at the optical layer are not available.
As for attenuation, nominal gain or pump optical power locked value, this alarm indicates
that such a value stored in the NE software is not the current actual value of the physical
board. As a result, after the board is reset it cannot be restored to the configuration state
before the reset.
Possible Causes
3-72
As for the operating wavelength of the OTU, the configured logic wavelength differs with
the actual wavelength or falls beyond the tuning range.
As for the MRx board, the configured logic wavelength differs with the actual wavelength
that the board supports.
As for data of the board operating band, the configured logic wavelength differs with the
actual wavelength that the board supports.
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 nominal gain.
In the case of the working mode of the optical interface, if the board does not support the
configured working mode, the configuration data on the SCC is inconsistent with the data
on the board.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
In the case of the type of the services to be transmitted, if the board does not support the
configured service type, the configuration data on the SCC is inconsistent with the data on
the board.
In the case of the FEC working mode, if the board does not support the configured working
mode, the configuration data on the SCC is inconsistent with the data on the board.
Procedure
Step 1 View on the U2000 the parameters of the alarm and confirm the configuration data type and the
IDs of the slot, optical interface and channel that correspond to the configuration data thresholdcrossing alarm.
Step 2 Take the relevant handling measures according to the configuration data type.
l
As for the operating wavelength of the OTU, query the actual wavelength of the board and
the logic wavelength stored on the NE software side. If these two wavelengths differ,
reconfigure the operating wavelength of the corresponding optical interface to make it the
same as the fixed wavelength of the optical module on the board; or replace the board or
optical module with another one whose wavelength is the same as that stored in the NE
software.
As for wavelengths added/dropped to/from the MRx, query the wavelengths actually added/
dropped to/from the corresponding optical interface. If these two wavelengths differ,
reconfigure the add/drop wavelengths of the corresponding optical interface to make them
the same as the fixed add/drop wavelengths of the optical module on the board; or replace
the board or optical module with another one whose wavelength is the same as that stored
in the NE software.
As for the operating wavelength of the board, query the actual operating band of the
corresponding board and the logic band stored on the NE software side. If these two bands
differ, reconfigure the operating band of the corresponding board to make it the same as
the actual operating band.
As for the nominal gain, query the threshold of the current actual nominal gain. Reconfigure
a valid nominal gain value for the optical interface channel of the board based on the queried
threshold.
In the case of the working mode of the optical interface, check whether the configured
working mode is the same as the actual mode of the board by using the U2000. If the
configured working mode is not the same as the actual mode, re-configure the working
mode of the optical interface.
In the case of the type of the services to be transmitted, check whether the service type is
the same as the actual type of the services accessed by the board by using the U2000. If the
configured service type is not the same as the actual service type, re-configure the service
type.
In the case of the FEC working mode, check whether the configured FEC working mode
is the same as the mode that is actually supported by the board by using the U2000. If the
configured FEC working mode is not the same as the actual mode, re-configure the FEC
working mode of the board.
----End
Issue 04 (2010-10-20)

3-73

Transport Platform
3 Alarm Processing
Related Information
3.2.13 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a database error. The alarm occurs when the database
is in error
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
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
3-74
Operation to database fails.
Data in the database is damaged.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
Step 1 Solve the problem by periodically backing up the database. Check and test the database in the
backup area to ensure that the data in database is complete.
----End
Related Information
None
3.2.14 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the database is in the protection
mode. The alarm occurs when the NE database is in the protection mode.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

In the protection mode, the NE database cannot be backed up.
Possible Causes
l
The reset times of the SCC in five minutes cross the threshold value of the protection mode.
The SCC issues a command to test the protection mode.
Procedure
Step 1 Check whether the NE database in the protection mode is caused by human factors. If that is the
case,
l
Perform warm or cold reset on the SCC through the U2000. Release the protection mode.
For details, see the Supporting Tasks.
Wait for 15 minutes. Release the protection mode after the automatic reset.
Issue 04 (2010-10-20)

3-75

Transport Platform
3 Alarm Processing
----End
Related Information
None
3.2.15 DCC_CHAN_LACK
Description
The alarm of insufficient DCC channels, indicating that the DCC channels of the NE are
insufficient.
Reported from the WDM side or client side: NA.
Attribute
Alarm Severity
Alarm Type
Major
Communication
Parameters
Name
Meaning
Parameter 1, Parameter 2 Indicates the slot where the alarm is generated.

Parameter 3
Indicates the optical interface where the alarm is generated.
Parameter 4
l 0x1 indicates failing to obtain the 1-byte DCC channel

resources.
resources.
resources.
resources.
resources.
resources.

When the DCC channel of the required type is unavailable, the communication of the optical
interfaces of the board becomes abnormal.
3-76

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Possible Causes
l
The communication channel distribution mode does not contain the DCC channel of the
required type.
The DCC channels of the required type have been occupied by other boards.
Procedure
----End
Related Information
None.
3.2.16 DOWN_E1_AIS
Description
The DOWN_E1_AIS is an indication alarm of the downstream 2 Mbit/s signals. If a tributary
board has detected that the value of the downstream E1 signals is all "1"s, the DOWN_E1_AIS
alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Optical port ID, fixed as 0x01.
Parameter 2, parameter 3
Indicates the path number.
Parameter 4
The value is always 0xff, and this parameter is unused.
Parameter 5
Indicates the bus number. This value is always 0x01.

When the DOWN_E1_AIS alarm is generated, the E1 signals on the board path are unavailable.
Issue 04 (2010-10-20)

3-77

Transport Platform
3 Alarm Processing
Possible Causes
The possible causes of the DOWN_E1_AIS alarm are as follows:
l
The AIS is inserted in the higher-level alarm.
The UP_E1_AIS, and E1_LOS alarm occur on the opposite board.
The local board is faulty.
The cross-connect unit or timing unit is faulty.
Procedure
Step 1 View the alarms on the U2000 to check whether there is a higher-level alarm (such as R_LOS,
R_LOC, R_LOF, or MS_AIS) on the local board. Refer to the corresponding section in this
Step 2 Check whether the UP_E1_AIS, or E1_LOS alarm occurs on the remote board. Refer to the
corresponding section in this document to clear the alarm.
Step 3 View alarms on the U2000 to check whether the DOWN_E1_AIS alarm is cleared. If this alarm
persists, reset the local board.
Step 4 If this alarm persists, replace the local board.
Step 5 If this alarm persists, reset the cross-connect unit or timing unit.
Step 6 If this alarm persists, replace the faulty cross-connect or timing unit.
----End
Related Information
None
3.2.17 E1_LOC
Description
The E1_LOC is an alarm indicating the loss of clock in the upstream E1 service on the E1
tributary board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None
3-78

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

When the E1_LOC alarm occurs, the clock in the uplink E1 signal of the E1 tributary board is
lost. As a result, the E1 services are unavailable.
Possible Causes
The possible causes of the E1_LOC alarm are as follows:
The upstream equipment is faulty, which causes problems to the clock signal accessed by the
E1 interface.
Procedure
Step 1 Check whether the service transmitting of the interconnected PDH equipment is faulty.
Step 2 Remove the fault of the interconnected equipment. View alarms on the U2000 to check whether
the E1_LOC alarm is cleared.
Options
Description
Step 3 Check the board that reports the alarm at the local station. Perform a reset on the board or replace
the board to clear the alarm.
CAUTION
Performing a cold reset on the board, or replacing the board will interrupt services. This operation
is of risk.
----End
Related Information
None.
3.2.18 ETH_LINK_DOWN
Description
Failure of network interface connection.
Issue 04 (2010-10-20)

3-79

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the Ethernet port number. For example:

0x02 indicates the RM2 or TM2 port.
0x03 indicates the ETH1 port.
0x04 indicates the ETH2 port.

When the ETH_LINK_DOWN alarm is generated during data transmission, the network port
negotiation fails. The data cannot be received and the services are interrupted.
Possible Causes
l
The working modes of the transmit and receive ports are inconsistent and the negotiation
fails.
The link is faulty.
The cable or fiber is incorrectly connected or the opposite equipment is faulty.
Procedure
Step 1 View the alarm on the NMS to determine the board that reports the alarm. Then, determine the
number of the port on the board that reports the alarm.
Step 2 Check whether the working mode of the local port is consistent with that of the opposite port.
If not, modify the modes to the same, and then check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the cable or fiber connection is faulty. If yes, recover the
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 faulty
board at the opposite station, and then check whether the alarm is cleared.
3-80

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Step 5 If the alarm persists, replace the board that reports the alarm, and then ensure that the working
modes of the ports at the local station and opposite station are consistent. Then the alarm is
cleared.
----End
Related Information
None
3.2.19 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm is
generated when the system detects the loss of the external clock source traced by the equipment.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
Name
Meaning
Parameter 1
Indicates the clock source code. The value is 0xf0.
Parameter 2
Indicates the clock source number.

l External clock source 10x01
l External clock source 20x02

When the EXT_SYNC_LOS occurs, it indicates that the external clock source set in the clock
source priority table on the clock board is invalid. The signal framing is incorrect and massive
receiving bit errors and pointer justification events occur. As a result, the services are
unavailable.
Possible Causes
The possible causes of the EXT_SYNC_LOS alarm are as follows:
The possible cause of the EXT_SYNC_LOS alarm is as follows:
The signal is lost at the physical external clock source interface.
Issue 04 (2010-10-20)

3-81

Transport Platform
3 Alarm Processing
Procedure
Step 1 Check whether the cable connection for inputting the external clock is abnormal, the cable
connector is loose, and the cable break occurs.
Step 2 If yes, remove the fault of the cable. View alarms on the U2000 to check whether the
EXT_SYNC_LOS alarm is cleared.
Options
Description
Step 3 Check whether the external clock device operates normally. If not, replace it.
----End
Related Information
None
3.2.20 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating a fan failure. This alarm is generated when one or more
fans fail.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1 Indicates the number of failed fans. For example, 0x01 indicates that one fan
fails.
Parameters 2 Indicates the fan number.
3-82

Issue 04 (2010-10-20)

Transport Platform
3 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
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
3.2.21 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.
Reported from the WDM side or client side: WDM side
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

The generation of the alarm affects the receiving of the services.
Possible Causes
l
The received signals have excessive attenuation.
The laser in the opposite station is closed.
Issue 04 (2010-10-20)

3-83

Transport Platform
3 Alarm Processing
The signals transmitted by the WDM side of the opposite station do not have FEC frame
structure.
The board in the opposite station is faulty.
The board at the local station is faulty.
Procedure
Step 1 Check whether the input optical power of the interface of the board at the local station is within
the normal range by using the U2000. For the optical power specifications of the specific board,
see the Product Description. If the optical power is abnormal, take the alarm as the
Step 2 Perform the hardware self-loop on the WDM side of the board in the opposite station. If the
opposite station reports the alarm, remove the fault in the opposite station.
(1) Check whether the board is forced to emit light. If yes, release the setting.
(2) Check whether the opposite station has the WDM-side inloop. If yes, release the loopback.
If not, the board may be faulty. Replace the faulty board. For details, see Parts
Replacement.
Step 3 If the opposite station does not report the alarm, the board at the local station is faulty. Replace
the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
3.2.22 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out-of-frame.
Reported from the WDM side or client side: WDM side
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

The generation of the alarm affects the receiving of the services.
3-84

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Possible Causes
l
The received signals have excessive attenuation.
The board in the opposite station is faulty.
Procedure
the normal range by using the U2000. For the optical power specifications of the specific board,
see the Product Description. If the optical power is abnormal, take the alarm as the
Step 2 Perform the hardware self-loop on the WDM side of the board in the opposite station. If the
opposite station reports the alarm, remove the fault in the opposite station.
(1) Check whether the board is forced to emit light. If yes, release the setting.
(2) If the alarm persists, the board may be faulty. Replace the faulty board. For details, see
Parts Replacement.
Step 3 If the opposite station does not report the alarm, the board at the local station is faulty. Replace
the faulty board. For details, see the Parts Replacement.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
None
3.2.23 FPGA_ABN
Description
The FPGA_ABN is an alarm indicating that the FPGA status is abnormal. The alarm occurs
when the standby FPGA is currently used by the board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
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.
Issue 04 (2010-10-20)

3-85

Transport Platform
3 Alarm Processing
Possible Causes
l
The active FPGA file does not exist when the board starts.
Loading of the active FPGA file fails when the board starts.
Procedure
Step 1 Reload the FPGA file to the board.
----End
Related Information
None
3.2.24 FUSE_ALARM
Description
Output offline alarm. The alarm is generated when the uninterruptible power modules (UPM)
is damaged.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1
Indicates the ID of the channel where the alarm is generated. For example,
0x01 indicates channel 1.
Parameters 2 and 3 The power module number reporting the alarm, two byte. For example,
0x00 0x01 stands for fuse of the power supply.
0x00 0x02 stands for the power failure.
0x00 0x03 stands for the load fuse 1.
0x00 0x04 stands for the load fuse 2.
3-86

Issue 04 (2010-10-20)

Transport Platform
Parameter
3 Alarm Processing
Description
Parameters 4 and 5 The cause of the alarm generation. It is always 0x00 0x01, which stands
for open circuit.

The standby power supply of the equipment is working. If the standby power supply is damaged,
the NE loses the power supply. The damaged power supply module needs to be replaced in time.
Possible Causes
l
The UPM is powered off.
The fuse of the UPM is faulty.
The load fuse is faulty.
Procedure
Step 1 Check whether the UPM is powered on normally. Open the switch of the power supply to power
on the UPM.
Step 2 If the alarm persists, check whether the battery fuse and the load fuse of the UPM are faulty. If
any fuse is faulty, replace the faulty fuse.
Step 3 If the alarm still persists, replace the UPM.
----End
Related Information
None
3.2.25 GPON_DS_LOF
Description
LOF is generated in the downlink GPON services (reported by PU board and PL board).
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

This alarm indicates that frame alignment fails in the downlink GPON service.
Issue 04 (2010-10-20)

3-87

Transport Platform
3 Alarm Processing
Possible Causes
The chip on the PU or PL board may be faulty, the transmission of downlink data may be
interrupted, or a fault may have occurred on the WDM side.
Procedure
Step 1 Check whether the line optical power is normal.
Step 2 Check whether the service processing chip is normal.
Step 3 Check whether an exception occurs on the WDM side.
----End
Related Information
None
3.2.26 GPON_RUF
Description
Registration of a board fails and the distance from the board to an OLT is not measured.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

This alarm indicates that the distance between the board and an OLT is not measured. As a result,
the GPON service is interrupted.
Possible Causes
l
The optical power may be abnormal.
The configuration of the OLT may be incorrect.
The board may be faulty.
Procedure
Step 1 Check whether the optical power is within the normal range.
3-88

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Step 2 Check whether the configuration of the OLT is correct, for example, whether the measurement
distance is correct and whether the automatic discovery function is enabled.
Step 3 If the alarm persists, replace the faulty board. For details, refer to the Parts Replacement.
----End
Related Information
None
3.2.27 GPON_US_LOF
Description
LOF is generated in the uplink GPON services (reported only by PL board).
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

This alarm indicates that frame alignment fails in the uplink service of the PL board.
Possible Causes
The chip on the PL board may be faulty, the transmission of uplink data may be interrupted, or
a fault may have occurred on the WDM side.
Procedure
Step 1 Check whether the line optical power is normal.
Step 2 Check whether the service processing chip is normal.
Step 3 Check whether an exception occurs on the WDM side.
----End
Related Information
None
Issue 04 (2010-10-20)

3-89

Transport Platform
3 Alarm Processing
3.2.28 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware failure. When the system detects hardware
failure, this alarm is reported.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
3-90

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Parameter
Description
Parameter 1
Indicates the fault type of the alarm. For example:

0x01 indicates that the power supply module is abnormal.
0x02 indicates that the board is not properly installed (the
board is not in good contact with the backplane, that is, the
board is not secured).
0x03 indicates that 38M system clock 1 is abnormal.
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.
0x17 indicates that the 32M clock is invalid.
0x1a indicates that the loop of the cross-connect chip fails.
0x1b indicates that the 8k online signal is pulled down.
Issue 04 (2010-10-20)

3-91

Transport Platform
3 Alarm Processing
Parameter
Description
0x1c indicates that the chip of the probe laser fails.
0x1c indicates that the chip of the loading laser fails.
0x1e indicates that the clock of the DSP driver chip is lost.
0x1f indicates that the output clock of the DSP is lost.
0x20 indicates that the RTM module is offline.
0x21 indicates that a chip fault.
0x22 indicates the 2M system frame header 1.
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 2 is 0x02,
bus B is abnormal.
When Parameter 1 is 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14,
0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have
different values, which indicate different component, module,
or chip faults.
When Parameter 1 is of another value, Parameter 2 and
Parameter 3 are always 0xff.

The alarm affects the normal operating of the board and affects services.
Possible Causes
l
Cause 1: The NE power is abnormal.
Cause 2: The board is not connected to the backplane properly or the board is faulty.
Cause 1: The NE power is abnormal.
Procedure
1.
l
3-92
Check whether the NE power works normally. If not, feed the NE with power supply.
Cause 2: The board is not connected to the backplane properly or the board is faulty.
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
1.
Reseat the board. Then, check whether the alarm is cleared.
2.
If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
3.2.29 HP_LOM
Description
The HP_LOM is an alarm indicating higher order path loss of multiframe.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the HP_LOM alarm occurs, it indicates that the values of the H4 bytes in the payload is
inconsistent with the expected values in several consecutive basic frames in the multiframe
sequence. The multiframe indication of the VC-12 services is lost. As a result, the VC-12 services
are unavailable.
When the HP_LOM alarm occurs, the board will insert VTAIS (TU_AIS for tributary services)
into the corresponding path.
Possible Causes
The possible causes of the HP_LOM alarm are as follows:
l
The H4 byte is lost or the H4 byte value is invalid.
Procedure
Step 1 Check whether the services at the opposite station and the local station are correctly configured.
If not, modify the incorrect configuration and issue it again.
Step 2 View alarms on the U2000 to check whether the HP_LOM alarm is cleared.
Issue 04 (2010-10-20)
Options
Description

3-93

Transport Platform
3 Alarm Processing
Step 3 Check whether the cross-connect unit and the line board are faulty. You can employ the optical
path self-loop method to check whether any hardware of the opposite station is faulty. If the
fault is located on the opposite station. Replace the line board first and then the SCC board of
the opposite station.
Step 4 View alarms on the U2000 to check whether the HP_LOM alarm is cleared.
Options
Description
Step 5 Ensure the local station is faulty. Replace the faulty board.
----End
Related Information
None.
3.2.30 HP_RDI
Description
The HP_RDI is an alarm indicating that the local station receives the remote defect indication
in the higher order path sent from the opposite station
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_RDI alarm occurs, it indicates that the services received by the opposite station
have the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm. As a result, the HP_RDI alarm is
sent to the local station.
Possible Causes
The possible causes of the HP_RDI alarm are as follows:
l
3-94
The opposite line receives the AU_AIS/AU_LOP/HP_TIM/HP_SLM alarms.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
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
Description
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
Step 2 View alarms on the U2000 to check whether the HP_RDI alarm is cleared.
Options
Description
Step 3 Perform the loopback for the stations at two ends of the line. Locate the faulty board.
Options
Description
The board at the opposite station reports the

HP_RDI alarm
The transmit end of the board at the opposite

station is faulty. Replace the faulty board.
The board at the local station reports the

HP_RDI alarm
The receive end of the board at the local

----End
Related Information
AU_AIS, AU_LOP, HP_TIM, HP_SLM
3.2.31 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.
Issue 04 (2010-10-20)

3-95

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Warning
Service quality alarm
Parameters
None

When the HP_REI alarm occurs, it indicates that the services received by the opposite station
have the higher order B3 errored blocks. As a result, the HP_REI alarm is sent to the local station.
Possible Causes
The possible cause of the HP_REI alarm is as follows:
The B3 bit errors are received at the opposite station.
Procedure
Step 1 View the alarms on the opposite NE, and check whether there are B1 or B2 bit errors.
Options
Description
There are B1 or B2 bit errors

There are B1 or B2 bit errors
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.
3-96
Options
Description
The board at the opposite station reports B3

bit errors
The receive end at the opposite station is

faulty. Replace the boards in an order of line
board, tributary board, and SCC board.
The board at the local station reports B3 bit

errors
The transmit end of the board at the local


Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
CAUTION
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD
3.2.32 HP_SLM
Description
The HP_SLM is an alarm indicating the mismatch of the higher order path signal label (C2)
received by the line board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_SLM alarm occurs, it indicates that the higher order overhead C2 byte received
by the local station is inconsistent with the C2 byte expected. As a result, the services in the
payload are unavailable.
When the HP_SLM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_SLM alarm are as follows:
l
The signal label C2 byte expected to be received by the local station is inconsistent with
that transmitted by the opposite station.
Procedure
Step 1 Check whether the C2 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If the configuration
is different, modify them to be consistent and issue the configuration again.
Issue 04 (2010-10-20)

3-97

Transport Platform
3 Alarm Processing
Step 2 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option
Description
Step 4 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option
Description
Step 5 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
Option
Description

HP_SLM alarm

board and SCC board.
The board at the local station reports

HP_SLM bit errors

CAUTION
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
3.2.33 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.
3-98

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_TIM alarm occurs, it indicates that the higher order overhead J1 byte received by
the local station is inconsistent with the J1 byte expected. As a result, the services in the payload
are unavailable.
When the HP_TIM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_TIM alarm are as follows:
l
The path trace identifier J1 byte expected to be received by the local station is inconsistent
with that transmitted by the opposite station.
Procedure
Step 1 Check whether the J1 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If not, modify them
to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the HP_TIM alarm is cleared.
Options
Description
Step 4 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
Issue 04 (2010-10-20)
Option
Description

HP_TIM alarm

board and SCC board.

3-99

Transport Platform
3 Alarm Processing
Option
Description
The board at the local station reports HP_TIM

bit errors

CAUTION
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
3.2.34 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the higher order path received by the line board is
unloaded.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_UNEQ alarm occurs, it indicates that the signal payload transmitted by the line
board at the opposite station is unloaded.
Possible Causes
The possible cause of the HP_UNEQ alarm is as follows:
The C2 byte in five consecutive frames is all "0"s.
3-100

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
Step 1 Check the C2 byte configuration of the opposite NE to see whether the C2 byte has sent UNEQ.
If the configuration is incorrect, modify and re-issue the configuration.
Step 2 Check whether the line board of the opposite NE is configured with services in the transmitting
direction. If not, re-configure the services of the NE.
Step 3 View alarms on the U2000 to check whether the HP_UNEQ alarm is cleared.
Options
Description
Step 4 The board at the local station is faulty. Replace the faulty board.
----End
Related Information
None.
3.2.35 J0_MM
Description
The J0_MM is an alarm indicating trace indicator mismatch. The alarm occurs when the received
J0 byte is not consistent with the J0 byte to be received.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services are not affected.
Possible Causes
l
The J0 byte mismatches.
The service connection is incorrect.
Issue 04 (2010-10-20)

3-101

Transport Platform
3 Alarm Processing
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 on the line. See the handling procedure of the B1_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
3.2.36 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR_EX is an alarm indicating that the pluggable optical module on the
board does not match the optical port rate of the board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the LASER_MOD_ERR_EX alarm occurs, it indicates that the pluggable optical module
installed on the board does not match the optical port rate of the board. The board will transmit/
receive services abnormally.
Possible Causes
l
Cause 1: The optical module installed in the optical port of the board is of a wrong type.
Cause 1: The optical module installed in the optical port of the board is of a wrong type.
Procedure
1.
3-102
Check whether the optical module type of the board is correct. If yes, re-configure the
service type of the corresponding optical interface.
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

1.
Replace the optical module on the board with another one of the right type. For details,
refer to "Replacing Pluggable Optical Modules" of the Parts Replacement.
2.
Check whether the alarm is cleared. If the alarm persists, Replace the faulty board.
----End
Related Information
None
3.2.37 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
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Name
Meaning
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 expires 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.
Issue 04 (2010-10-20)

3-103

Transport Platform
3 Alarm Processing

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.
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
3.2.38 LCS_EXPIRED
Description
License expired. The LCS_EXPIRED is an alarm indicating the license has expired and the
keepalive period of 60 days has also elapsed.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
table.
3-104
Name
Meaning
Parameters 1 and 2
Indicate days.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Name
Meaning
Parameter 3
l 0x01 indicate licese 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.
Possible Causes
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
----End
Related Information
None
3.2.39 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
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

If a license file is not installed, only the default functions of the system are available.
Issue 04 (2010-10-20)

3-105

Transport Platform
3 Alarm Processing
Possible Causes
When starting up, the system does not find a license file, which is essential for the system to
run.
Procedure
----End
Related Information
None
3.2.40 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
Alarm Type
Critical
Parameters
None

When loss of synchronization occurs in the physical coding sublayer (PCS) of a receiving port,
the port stops receiving data. Thus, the loss of synchronization alarm affects the quality of service
(QoS). In this case, the service is interrupted.
Possible Causes
3-106
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.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
Step 1 Check whether the configuration of working mode, signal type or rate of the equipment at the
local station and the opposite station are consistent. If they are not consistent, modify the setting
to ensure the consistency.
Step 2 If the alarm persists, check whether the fiber or cable that is used to connect between the
equipments at the local station and the opposite station are well connected. If they are not well
connected, reconnect or replace the fiber or cable.
Step 3 If the alarm persists, check whether the data equipment in the opposite station is faulty. If that
is the case, remove the fault of the data equipment in the opposite station.
Step 4 If the alarm remains, use the U2000 to check whether the receive optical power of the -side
interface of the alarm-reporting board is in normal range. For optical power specifications of
boards, see the Product Description. If the optical power is abnormal, take the alarm as the
IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.
Step 5 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
None
3.2.41 LOCAL_FAULT
Description
Local fault alarm. The alarm is generated when an error such as FIFO overflow is detected on
the transmission link from the local router (RS-A) to the remote router (RS-B).
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The 10GE services in the flow control mode are configured on the client side of the board. If
the board receives the LOCAL_FAULT alarm, the received services may be interrupted.
Possible Causes
l
The input fiber on the client side is transiently cut.
The board receives various bit errors.
Issue 04 (2010-10-20)

3-107

Transport Platform
3 Alarm Processing
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.
----End
Related Information
None
3.2.42 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO on the receive side of the lower order path
of the E1 tributary board overflows.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

When the LP_R_FIFO alarm occurs, the FIFO on the receive side of the 2M tributary board
overflows. As a result, the lower order services will be interrupted.
3-108

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Possible Causes
The possible causes of the LP_R_FIFO alarm are as follows:
l
The receiving rate of the services at the PDH side is over fast, and thus the pointer
justification is abnormal. As a result, the received FIFO overflows.
Procedure
Step 1 Check the service configuration of the opposite equipment at the PDH side and modify the
incorrect configuration. Select correct transmit rate.
Options
Description
Step 2 If the alarm persists, replace the board.
CAUTION
----End
Related Information
None.
3.2.43 LP_RDI
Description
The LP_RDI is an alarm indicating a remote defect in the lower order path of the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
Issue 04 (2010-10-20)

3-109

Transport Platform
3 Alarm Processing
table.
Name
Meaning
Parameter 1
BUS number
l BUS A 0x01
l BUS B 0x02

When the LP_RDI alarm occurs, the opposite station receives the TU_AIS or TU_LOP alarm
and then returns the LP_RDI alarm (VC12: V5[b8],VC3: G1[b5]) to the local tributary board.
Possible Causes
The possible causes of the LP_RDI alarm are as follows:
l
The opposite station has received the TU_AIS or TU_LOP alarm.
The receive part at the opposite station is faulty.
The transmit part at the local station is faulty.
Procedure
Step 1 View alarms of the NE, and check whether there is the TU_AIS or TU_LOP alarm in the
corresponding path of the tributary board at the opposite station.
Options
Description
There is the TU_AIS, or TU_LOP alarm

There are no such alarms as the TU_AIS and

TU_LOP
Step 2 If there is no alarm or the corresponding alarm is cleared at the opposite station, the LP_RDI
alarm persists. The tributary board is faulty. Replace the faulty board.
CAUTION
----End
Related Information
TU_AIS, TU_LOP
3-110

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.44 LP_REI
Description
The LP_REI indicates a remote bit error in the lower order path of the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1
BUS number
l BUS A 0x01
l BUS B 0x02

When the LP_REI alarm occurs, the lower order background block error (BBE) occurs in the
received services at the opposite station and the LP_REI alarm (VC12: V5[b3], VC3: G1[b1
b4]) is returned to the local station.
Possible Causes
The possible causes of the LP_REI alarm are as follows:
Bit errors are received in the lower order path at the opposite station.
Procedure
Step 1 View alarms of the opposite NE, and check whether there is the B3 or BIP bit error alarm.
Issue 04 (2010-10-20)
Options
Description
There is the B3 or BIP bit error alarm

document to clear the B3_EXC, B3_SD,
BIP_EXC, or BIP_SD alarm.
There is no B3 or BIP bit error alarm

3-111

Transport Platform
3 Alarm Processing
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If few B3 or BIP bit errors occur in the remote, the fault usually
lies in the equipment instead of the optical path. If any interference source exists near the
equipment, change the location.
Step 3 Perform the loopback for the stations at two ends of the line. Check whether the cross-connect
unit and the tributary board on both the opposite equipment and local equipment operate
normally. Following the service direction, check upstream stations one by one. Locate the faulty
board.
Options
Description
There is the B3 or BIP bit error reported on

the opposite board

board, tributary board, and SCC board.
There is the B3 or BIP bit error reported on

the local board
The transmit end of the board at the local

CAUTION
----End
Related Information
B3_EXC, B3_SD,
3.2.45 LP_RFI
Description
The LP_RFI is an alarm indicating that the E1 tributary board receives the remote failure alarm
of the lower order path from the downstream bus.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
3-112

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
table.
Name
Meaning
Parameter 1
BUS number
l BUS A 0x01
l BUS B 0x02

When the LP_RFI alarm occurs, the local E1 tributary board receives the remote failure alarm
of the lower order path (V5[b4]=1) at the opposite station. The system is not affected.
Possible Causes
The possible cause of the LP_RFI alarm is as follows:
The remote end of the lower order path fails to receive signals.
Procedure
Step 1 It indicates the board is faulty. Replace the board that reports the alarm.
CAUTION
----End
Related Information
None.
3.2.46 LP_SLM
Description
The LP_SLM is an alarm indicating the mismatch of the lower order path signal label received
by the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 04 (2010-10-20)

3-113

Transport Platform
3 Alarm Processing
Parameters
table.
Name
Meaning
Parameter 1
BUS number
l BUS A 0x01
l BUS B 0x02

When the LP_SLM occurs, the mapping structure of the lower order services received on the
tributary board is incorrect. As a result, the services are abnormal (VC12: V5[b5b7], VC3: C2).
Possible Causes
The possible causes of the LP_SLM alarm are as follows:
l
The lower order path signal label to be received at the local station is inconsistent with that
transmitted at the opposite station.
Procedure
Step 1 Check whether the signal label byte to be transmitted by the corresponding lower order path of
the tributary board at the opposite station is configured consistent with that to be received at 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 LP_SLM alarm is cleared.
Options
Description
----End
Related Information
None.
3.2.47 LP_T_FIFO
3-114

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Description
The LP_T_FIFO is an alarm indicating the FIFO on the transmit side of the lower order path of
the E1 tributary board overflows.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

When the LP_T_FIFO alarm occurs, the FIFO on the transmit side of the tributary board
overflows. As a result, the lower order services will be interrupted.
Possible Causes
The possible causes of the LP_T_FIFO alarm are as follows:
The frequency offset of the input PDH signal is over great, and thus the pointer justification is
abnormal. As a result, the FIFO on the transmit side overflows.
Procedure
Step 1 Check the service configuration of tributary board and modify the incorrect configuration.
Options
Description
Step 2 If the alarm persists, replace the board.
Issue 04 (2010-10-20)

3-115

Transport Platform
3 Alarm Processing
CAUTION
----End
Related Information
None.
3.2.48 LP_TIM
Description
The LP_TIM is an alarm indicating the mismatch of the lower order path trace identifier received
by the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
BUS number
l BUS A 0x01
l BUS B 0x02

When the LP_TIM alarm occurs, the lower order path trace identifier byte (VC12: J2, VC3: J1)
actually received by the tributary board at the local station is inconsistent with that to be received.
As a result, the services in the payload are unavailable.
Possible Causes
The possible causes of the LP_TIM alarm are as follows:
3-116

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
The lower order path trace identifier to be received at the local station is configured
inconsistent with that transmitted at the opposite station.
Procedure
Step 1 Check whether the trace identifier transmitted at the corresponding path of the tributary board
at the opposite station is configured consistent with that to be received at 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 LP_TIM alarm is cleared.
Options
Description
----End
Related Information
None.
3.2.49 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that the lower order path received by the tributary board
on the cross-connection side is unequipped.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Issue 04 (2010-10-20)

3-117

Transport Platform
3 Alarm Processing
Name
Meaning
Parameter 1
BUS number
l BUS A 0x01
l BUS B 0x02

When the LP_UNEQ alarm occurs, no services are loaded in the payload of the lower order path
(VC12: V5 [b5b7], VC3:C2) received by the tributary board on the cross-connection side from
the opposite station.
Possible Causes
The possible causes of the LP_UNEQ alarm are as follows:
l
The lower order path at the opposite station of the SDH transmission equipment is unused.
The T_ALOS alarm is reported on the tributary board at the opposite station of the SDH
transmission equipment, and the LP_UNEQ is enabled to be inserted.
Procedure
Step 1 Check whether the lower order path at the opposite station is set unused. If the lower order path
is used, go to step 3; If the path is not used, set the path to use.
Step 2 View alarms on the U2000 to check whether the LP_UNEQ alarm is cleared.
Options
Description
Step 3 Check whether the T_ALOS alarm is reported on the tributary board at the opposite station and
whether the LP_UNEQ is enabled to be inserted. Clear the T_ALOS alarm or disable the
LP_UNEQ to be inserted.
----End
Related Information
None
3.2.50 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.
3-118

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates which synchronization sources are lost.

l 0x01: All synchronization sources for the system clock are lost.
l 0x02: All synchronization sources for the first 2M phase-locked source are
lost.
l 0x03: All synchronization sources for the second 2M phase-locked source
are lost.

When the LTI alarm is generated, the NE clock is in an abnormal state. If the NE clock remains
in this abnormal state for a long time, the bit error rate and the pointer justifications may increase
due to the decreased clock qualityk.
Possible Causes
The possible causes of the LTI alarm are as follows:
l
Cause 1: There is a fiber cut or a cable cut.
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.
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.
Procedure
1.
Issue 04 (2010-10-20)
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.
3-119

Transport Platform
3 Alarm Processing
2.
If the alarm persists, perform cold reset on the relevant line board or tributary board.
After successful cold reset, check whether the LTI alarm is cleared. For details, see
Performing Cold Reset on a Board in the Supporting Tasks.
3.
If the alarm persists, replace the relevant line board or tributary board, and then check
whether the LTI alarm is cleared. For details, see Parts Replacement.
4.
If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.
5.
If the alarm persists, replace the clock board. For details, see the Parts Replacement.
Cause 2: There is no input from the external clock source. Cause 4: The board is faulty.
1.
Make sure that the external clock equipment properly transmits signals. Replace the
external clock equipment with a normal one, and then check whether the LTI alarm
is cleared.
2.
If the alarm persists, check whether the input and output modes of the external clock
source are consistent. After the input and output of the external clock source are set
to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared. For
details, see Configuring Physical Clock in the Feature Description.
3.
If the alarm persists, check whether the clock input cable is correctly connected. After
ensuring the correct connection of the clock input cable, check whether the alarm is
cleared.
4.
If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.
5.
Cause 3: The synchronization source is set as non-revertive or locked.

1.
On the U2000, check whether the synchronization source is set as non-revertive. If

yes, set the source as revertive. Then, check whether the alarm is cleared.
2.
On the U2000, check whether the synchronization source is set as locked. If yes, set
the source as unlocked. Then, check whether the alarm is cleared.
----End
Related Information
None
3.2.51 MDL_ALARM
Description
Power module alarm. The alarm is generated when the power supply module fails to
communicate with the equipment.
Attribute
3-120
Alarm Severity
Alarm Type
Major
Equipment alarm
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Parameters
table.
Parameter
Description
Parameter 1
The power supply module number, For example,

0x01 stands for power supply module 1.
0x02 stands for power supply module 2.
Parameters 2 and 3
The cause of the alarm, For example,

0x00 0x01 stands for shutdown.
0x00 0x02 stands for faulty.
0x00 0x03 stands for protection.
0x00 0x04 stands for communication failure.

The normal working of the UPM is affected.
Possible Causes
l
The UPM is not in position.
The serial cable connecting the UPM to the equipment is faulty.
The UPM is faulty.
The standby module of the UPM is faulty.
Procedure
Step 1 Check whether the UPM is in position. If not, install the UPM. For details, see the Installation
Guide.
Step 2 If the alarm persists, check whether the switch of the UPM is pushed to ON. If not, push the
switch to ON.
Step 3 If the alarm persists, replace the serial cable connecting the UPM to the equipment.
Step 4 If the alarm persists, replace the UPM.
----End
Related Information
None
Issue 04 (2010-10-20)

3-121

Transport Platform
3 Alarm Processing
3.2.52 MS_REI
Description
The MS_REI is an alarm that indicates that bit errors occur at the remote end of the multiplex
section (MS). When the receive side of the local optical station receives the M1 byte, which
indicates that the number of block bit errors detected by BIP-Nx24 (B2) at the opposite station,
the MS_REI alarm is reported.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

When the MS_REI alarm is generated, the number of B2 bit errors received at the opposite
station is beyond the specified range. The services at the local station are not affected, but the
service quality at the opposite station is degraded.
Possible Causes
The number of B2 bit errors received at the opposite station is beyond the specified range.
Procedure
Step 1 After you clear the B2_EXC or B2_SD alarm that occurs at the opposite station, the MS_REI
alarm is automatically cleared.
----End
Related Information
None
3.2.53 MSSW_DIFFERENT
Description
The MSSW_DIFFERENT is an alarm indicating the software difference between working and
protection boards. The two file systems of the SCC board are backups for each other. Each file
is saved in the two file systems. The alarm is generated when the software versions in the two
file systems are not consistent or the versions of the files with the same name are not consistent.
3-122

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
0x01 indicates the file in the flash memory.

0x02 indicates the current running software.
0x03 indicates the special patrol object.
Parameters 2 and 3 Indicates the numbers of the inconsistent files on the SCC boards.
Parameter 4
Indicates the alarm cause.

0x04 indicates that the file versions in the active and standby areas of a
single SCC differ.
0x08 indicates that file versions of the active and standby SCCs differ, or
there is no file with the same name under the corresponding directory of
the opposite board.
0x0c indicates that the file versions in the active and standby areas of a
single SCC differ, and the file versions of the active and standby SCCs
also differ.

The NE software cannot run or cannot perform the protection switching.
Possible Causes
l
The software version currently running on the active SCC board is not consistent with that
on the standby SCC board.
The version of the software set file in the active area of the active or standby SCC is not
consistent with that of the file that has the same name on the SCC board.
The software set file in the active area of the active or standby SCC does not have the file
that has the same name and same type in the standby or active SCC board.
Issue 04 (2010-10-20)

3-123

Transport Platform
3 Alarm Processing
Procedure
Step 1 Update the NE software on the active or standby SCC board to ensure the version consistency.
Step 2 Update the version of the software set file in the active area of the active or standby SCC to
make the file consistent with the file that has the same name on the SCC board.
Step 3 Add the file that is consistent with that of one SCC board to the corresponding area in the active
area of the other SCC board that does not have the file.
----End
Related Information
None
3.2.54 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in installation state and is not
configured. The alarm occurs when the NE is in the initial installation state.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

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
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.
----End
3-124

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Related Information
None
3.2.55 NO_BD_PARA
Description
The NO_BD_PARR is an alarm indicating absence of the board parameter table. The alarm
occurs when the board does not have the parameter table.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l
The correct parameter table is not loaded before delivery.
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
Step 1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
----End
Related Information
None
Issue 04 (2010-10-20)

3-125

Transport Platform
3 Alarm Processing
3.2.56 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, manufacturing information,
and logic software.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1
The value is always 0x01.
Parameters 2 and 3 Indicates the ID of the lost file. For example,

l 0x00 0x01 indicates the OFS1/HWX/NESOFT.HWX file.
l 0x00 0x02 indicates the OFS2/HWX/NESOFT.HWX file.
l 0x00 0x03 indicates the OFS1/HWX/NE.INI file.
l 0x00 0x04 indicates the OFS2/HWX/NE.INI file.
l 0x00 0x05 indicates the OFS1/FPGA/TNF1SCC.PGA file.
l 0x00 0x06 indicates the OFS2/FPGA/TNF1SCC.PGA file.
l 0x00 0x07 indicates the board manufacture information file.
3-126

Issue 04 (2010-10-20)

Transport Platform
Parameter
Description
Parameter 4
Indicates the fault type. For example,
3 Alarm Processing
l 0x01 indicates that the file is lost.

l 0x02 indicates that the file verification fails.
l 0x04 indicates that the versions of the files in the working and backup
areas are inconsistent.
l 0x08 indicates that the versions of the files on the active and standby
boards are inconsistent.
l 0x0e indicates that the file verification fails and the version of the file
is inconsistent with the version of the file in the backup area and the
version of the file on the standby board.

The alarm affects the system as follows:
l
If the board that reports the alarm is not reset, the services and functions of the board are
not affected.
If the board that reports the alarm is reset, the board may fail to start.
Possible Causes
l
Parts of the software are not loaded to the board.
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.
----End
Related Information
None
3.2.57 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 and its value is 0.
Issue 04 (2010-10-20)

3-127

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

The services on the board are interrupted.
Possible Causes
l
The signals transmitted by the corresponding board at the opposite end do not have a frame
structure.
The input optical power is abnormal.
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 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 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.
----End
Related Information
ITU-T G.709
3-128

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.58 ODUk_PM_LCK
Description
The ODUk_PM_LCK is an alarm indicating that the ODUk PM signal is locked. The
maintenance signal LCK byte required by the carrier is used to lock the access point signal of
users during testing. It can be generated when the service layer adapts the source and sink. The
alarm is generated when the STAT byte value is "101" during locking.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services borne by the optical interface would be interrupted.
Possible Causes
The services at the optical interface are interrupted.
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.
Step 2 Query the board information and set LCK Insertion to Disabled if it is Enabled, and the local
station does not insert an LCK signal to the downstream.
----End
Related Information
ITU-T G.709
3.2.59 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".
Issue 04 (2010-10-20)

3-129

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services at the optical interface are interrupted.
Possible Causes
l
The corresponding board at the upstream station has the ODUk_PM_OCI alarm.
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
3.2.60 ODUk_PM_TIM
Description
The ODUk_PM_TIM is an alarm indicating mismatch of the ODUk PM trace identifier. The
alarm occurs during control process when the trace identifier at the opposite end mismatches
that at the local end when the TIM detection is enabled. The system compares the access point
identifiers (API) in the input signals and the expected API.
For the set TIM detection mode, the network architecture can be classified into the following
three types.
3-130

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
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.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the signal quality of the services at the optical interface is degraded.
Hence, the service signals may be unavailable.
Possible Causes
l
The networking architecture and the TIM detection mode to be configured are not
consistent.
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.
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
Issue 04 (2010-10-20)

3-131

Transport Platform
3 Alarm Processing
Related Information
ITU-T G.709
3.2.61 OPS_MAIN_BAK_ATTR_DIFF
Description
Attribute difference between working and protection channel. The alarm is generated when the
port attribute configuration of the working and protection channels of the protection group is
not consistent.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

The services are unavailable after the protection switching is performed to the protection group.
Possible Causes
The port attribute configuration of the working and protection channels of the protection group
is not consistent.
Procedure
Step 1 Check whether the port attribute configuration of the working and protection channels at the
local station is consistent. If not, configure the port attribute of the working and protection
channels again to ensure the consistency.
Step 2 Check whether the port attribute configuration of the working and protection channels in the
opposite station are consistent with that of the corresponding channels at the local station. If not,
configure the port attribute of the working and protection channels again to ensure the
consistency.
----End
Related Information
None
3-132

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.62 OPS_STA_INDI
Description
Optical Protection Status Indication. This alarm is reported when the working or protection
channel of the protection group is faulty or the user runs an external switching command.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameters 1
Indicates the OTU level.

0x01: OTU1;
0x02: OTU2;
0x03: OTU5G.

When this alarm is reported, the working channel or the protection channel of the protection
group might have faulty services that need to be restored.
Possible Causes
l
Cause 1: A user issues an external switching command such as forced switching, manual
switching or locked switching.
Cause 2: The services of the working channel or the protection channel of the protection
group are faulty.
Cause 1: A user issues an external switching command such as forced switching, manual
switching or locked switching.
Procedure
1.
Issue 04 (2010-10-20)
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.
3-133

Transport Platform
3 Alarm Processing
2.
If the external switching operation is necessary, ignore the alarm.
3.
If the external switching operation is unnecessary, issue a command to clear the

external switching.
Cause 2: The services of the working channel or the protection channel of the 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_LOS, R_LOF, R_LOC,
HARD_BAD, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_PM_TIM, ODUk_PM_DEG, ODUk_PM_EXC,
OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM, OTUk_DEG,
OTUk_EXC, REM_SF, REM_SD, B1_EXC, IN_PWR_HIGH,
IN_PWR_LOW. If yes, handle the alarms by referring to the corresponding alarm
2.
If the alarm persists, contact Huawei for help.
----End
Related Information
None
3.2.63 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm occurs
when the phase-locked loop on the clock board becomes faulty.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
3-134

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Name
Meaning
Parameter 1
Indicates the failed phase-locked loop.

l 0x01: first 2M phase-locked loop
l 0x02: second 2M phase-locked loop
l 0x03: 155M system phase-locked loop

When the OOL alarm is generated, the phase-locked loop cannot lock on the input signals, and
as a result the output clock signals are affected. This alarm may lower the quality of services or
interrupt the services.
Possible Causes
Cause 1: The board hardware of the phase-locked loop is damaged.
Procedure
l
Cause 1: The board hardware of the phase-locked loop is damaged.

1.
Perform cold reset on the board. Then, check whether the alarm is cleared. For details,
see Performing Cold Reset of a Board in the Supporting Tasks.
2.
----End
Related Information
None
3.2.64 OPUk_PLM
Description
The OPUk_PLM is an alarm indicating OPUk payload mismatch. The type of received payload
mismatches the expected payload type defined in the adaptation function.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None
Issue 04 (2010-10-20)

3-135

Transport Platform
3 Alarm Processing

Possibly the services are not available.
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 check whether the PT byte value received at the OPU of the local board is
consistent with that of the corresponding opposite board. If they are not consistent, see the next
step.
Step 2 Check whether the WDM-side fiber connection is correct according to the engineering fiber
connection diagram. If the fiber connection is incorrect, correctly connect the fiber according to
the engineering fiber connection diagram.
Step 3 Check whether the payload types of the local board matches that of the corresponding opposite
board. If not, replace the opposite board with a matching one. For details, see the Parts
Replacement.
----End
Related Information
ITU-T G.709
3.2.65 OTUk_AIS
Description
The OTUk_AIS is an OTUk alarm indication. An AIS signal travels downstream, which
indicates that a signal failure is detected in the upstream.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The services at the optical interface are unavailable.
3-136

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Possible Causes
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 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
3.2.66 OTUk_BDI
Description
The OTUk_BDI indicates an OTUk backward defect. This alarm occurs when the SM section
detects a signal failure and the value of the BDI byte is 1.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services at the optical interface are unavailable.
Possible Causes
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 alarm.
Issue 04 (2010-10-20)

3-137

Transport Platform
3 Alarm Processing
Procedure
Step 2 Query whether the alarm is reported from the client side or the WDM side.
l
If the alarm is reported from the client side, check the equipment on the client side.
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, or OTUk_TIM alarm by
using the U2000. If yes, handle the corresponding alarm at the downstream station.
----End
Related Information
ITU-T G.709
3.2.67 OTUk_DEG
Description
The OTUk_DEG is an alarm indicating that the OTUk signal is degraded. This alarm occurs
when the bit error detection mode is the burst mode, the signal is degraded, or bit error count
crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the services at the optical interface have bit errors, which make the
service signals invalid or even unusable.
Possible Causes
l
The optical interface at the local end is faulty.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. For optical power
specifications of specific boards, see the Product Description. If the optical power is not within
3-138

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
the normal range, see the handing procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms
for troubleshooting.
Step 3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, see the
Supporting Tasks.
----End
Related Information
ITU-T G.709
3.2.68 OTUk_EXC
Description
The OTUk_EXC is an alarm indicating that the OTUk bit errors cross the threshold. This alarm
occurs when the signal is degraded or bit errors cross the threshold if the error detection is in
the burst mode. This alarm occurs when the signal is degraded or bit errors cross the threshold
if the error detection is in the Poisson mode.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

Possible Causes
l
The attenuation of the received signals is rather large, and the fiber of the transmission line
is abnormal.
Issue 04 (2010-10-20)

3-139

Transport Platform
3 Alarm Processing
Procedure
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.
Replacement.
----End
Related Information
ITU-T G.709
3.2.69 OTUk_LOF
Description
The OTUk_LOF is an alarm indicating that the frame alignment signal(FAS) is abnormal. This
alarm occurs when the frame alignment processing is out of frame (OOF) in three consecutive
milliseconds.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Services on the board are interrupted.
Possible Causes
3-140
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.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If that is the case, locate
the position where the alarm is first generated according to the service route. If no alarm is
generated at the opposite end, the local end is the place where the alarm is first generated.
Step 2 Check whether the input optical power of the place where the alarm is first generated is within
the Product Description. If the optical power is abnormal, take the alarm as the IN_PWR_HIGH
or IN_PWR_LOW alarm for troubleshooting.
Step 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 5 If the alarm persists, the board may be faulty. Replace the faulty board. For details, see the
Supporting Tasks.
----End
Related Information
ITU-T G.709
3.2.70 OTUk_LOM
Description
The OTUk_LOM is an alarm indicating that the multiframe alignment signal(MFAS) is
abnormal. This alarm occurs when the multiframe locating is out of multiframe (OOM) in three
consecutive milliseconds.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None
Issue 04 (2010-10-20)

3-141

Transport Platform
3 Alarm Processing

Possible Causes
l
The FEC type is incorrectly configured.
The bit errors in the received signals of the OTU board at the local station are excessive.
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 SM_BIP8_OVER 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
3.2.71 OTUk_TIM
Description
The OTUk_TIM is an alarm indicating OTUk trail trace identifier (TTI) mismatch. This alarm
occurs during the control process when the TTI at the opposite end mismatches that at the local
end when the TIM detection is enabled. The system compares the access point identifiers (API)
in the input signals and the expected API.
For the set TIM detection mode, the network architecture can be classified into the following
three types:
l
For the point-to-point topology, only the source access point identifiers (SAPI) is compared
for the sink of trail termination.
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.
3-142

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the signal quality of the services at the optical interface is degraded.
Hence, the service signals may be unavailable.
Possible Causes
l
The networking architecture and the TIM detection mode to be configured are not
consistent.
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.
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 04 (2010-10-20)

3-143

Transport Platform
3 Alarm Processing
3.2.72 OUT_PWR_LOW
Description
The OUT_PWR_LOW is an alarm indicating that the output optical power is excessively low.
The output optical power of the laser is excessively low.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The output optical power of the laser is excessively low, which influences the normal
transmission of services.
Possible Causes
l
The input optical power is excessively low.
The laser is aged.
Procedure
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.
If it is within the normal range, replace the faulty optical module. For details, see the Parts
Replacement.
----End
Related Information
None
3-144

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.73 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
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The activation of the patch is not in the stable state. If the board is reset in this case, the patch
does not take effect after the system restarts, and the patch is automatically restored to the
deactivated state. The functions of the patch are not available or the bug corrected by the patch
appears again.
Possible Causes
The activated state of the patch package is excessively long.
Procedure
Step 1 If the patch file is confirmed to be correct, run the patch file through the U2000 after the end of
the observation.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the
U2000.
----End
Related Information
None
3.2.74 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.
Issue 04 (2010-10-20)

3-145

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The deactivated state indicates that the patch is loaded but the patch is not running. If the board
is reset in this case, the patch is automatically restored to the idle state after the system restarts.
The functions of the patch are not available or the bug corrected by the patch appears again.
Possible Causes
The deactivated state of the patch package exceeds the threshold.
Procedure
Step 1 If the patch file is confirmed to be correct, activate the patch file through the U2000.
U2000.
----End
Related Information
None
3.2.75 PATCH_ERR
Description
The PATCH_ERR is an alarm indicating a patch error. The alarm occurs when the board detects
that the patch file is available but the patch file is incorrect.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None
3-146

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

The functions of the patch are not available or the bug corrected by the patch appears again.
Possible Causes
If a patch is running before the system reboots, the NE automatically loads and runs this patch
after the reboot. If any anomaly occurs at this time and thus the loading fails, the PATCH_ERR
alarm is reported.
Procedure
Step 1 Obtain the correct patch file according to the Upgrade Guide and Product Version Matching
Table, and then reload the correct patch file.
----End
Related Information
None
3.2.76 PATCH_NOT_CONFIRM
Description
The PATCH_NOT_CONFIRM is an alarm indicating that the activated patch has not been
confirmed overtime. The alarm occurs when the patch file is not confirmed five minutes after it
is activated.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The activated state of the patch is the intermediate state for you to observe the effect of the patch
file. The state is used to prompt the user to confirm the patch file, which has no influence on the
normal running of the system.
Possible Causes
The patch file is not confirmed five minutes after it is activated.
Issue 04 (2010-10-20)

3-147

Transport Platform
3 Alarm Processing
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.
U2000.
----End
Related Information
The patch file is in the state for you to observe the effect of the patch file after it is activated.
When the alarm occurs, you do not need to end the alarm immediately. Confirm the patch after
the patch file is confirmed to be qualified. The alarm disappears if the activated state of the patch
file is changed upon a command.
3.2.77 PATCH_PKGERR
Description
The PATCH_PKGERR is an alarm indicating a patch package file error.
Attribute
Alarm Severity
Alarm Type
Major
Process
Parameters
None

Package loading management of certain boards may be unavailable if this alarm is generated.
Possible Causes
The patch package of certain boards is lost
Procedure
Step 1 Contact Huawei engineers to regenerate the patch package file.
----End
Related Information
None
3-148

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.78 PATCHFILE_NOTEXIST
Description
The PATCHFILE_NOTEXIST is an alarm indicating that the patch file does not exist. The alarm
occurs when the equipment detects that the patch file does not exist when it runs the patch file
again.
Reporting side: NA
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The loaded patch cannot work normally. The problem to be solved by the patch remains in the
system.
Possible Causes
If the patch is in the running state before the NE reboots, the patch file is lost after the NE reboots.
Procedure
Step 1 Obtain the correct patch file according to the Upgrade Guide and Product Version Matching
Table, and then reload the correct patch file.
----End
Related Information
None
3.2.79 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.
Issue 04 (2010-10-20)

3-149

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The switching of the active and standby channels is affected. As a result, the quality of the
received services is affected.
Possible Causes
l
During 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.
Procedure
Step 1 Replace with a suitable optical attenuator. Adjust the optical power in the active and standby
channels of the board at the local station to ensure that the power difference is within 5 dB.
Step 2 If the alarm persists, the detection circuit of the board at the local station is faulty. Replace the
faulty board. For details, see the Parts Replacement.
----End
Related Information
None
3.2.80 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
3-150
Alarm Severity
Alarm Type
Minor
Equipment alarm
Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Parameters
None

The PRBS test services on the board are interrupted.
Possible Causes
l
Cause 1: The link is abnormal. Hence, the board, on which the PRBS bit error test is
performed, does not receive the PRBS signals from the local board.
Cause 2: The board is faulty, or the line is degraded.
Procedure
Step 1 Perform a self-loop by connecting the transmit end to the receive end of the PRBS signals on
the local board.
l
If the alarm is cleared, it indicates that the board is normal. See Step 2 to check the link.
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
3.2.81 PUM_BCM_ALM
Description
The PUM_BCM_ALM is an alarm indicating that the bias current of the pump laser crosses the
threshold. This alarm occurs when the pump laser bias current of the optical amplifier unit crosses
the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None
Issue 04 (2010-10-20)

3-151

Transport Platform
3 Alarm Processing

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

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure
is taken, however, the output optical power of the board is affected in a period of time. This
affects the services.
Possible Causes
l
The ambient temperature is excessively high or excessively low.
The cooling system of the pump laser is damaged.
The pump laser has excessive current.
Procedure
Step 1 Check whether the ambient temperature is normal. If not, improve it.
Step 2 If the alarm persists, perform a warm reset on the faulty board through the U2000.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect services.
----End
Related Information
None
3.2.83 PWR_MAJ_ALM
Description
Abnormal power supply (severe overload or shortage). The alarm is generated when the voltage
of the input power supply is excessively low or too high.
Attribute
Alarm Severity
Alarm Type
Critical
Environment alarm
Parameters
table.
Issue 04 (2010-10-20)

3-153

Transport Platform
3 Alarm Processing
Parameter
Description
Parameter 1
Indicates the input power supply number. For example,

0x01 indicates that a voltage state alarm of power supply 1 is generated.
0x02 indicates that a voltage state alarm of power supply 2 is generated.
Parameter 2
Parameter 2 indicates the power supply status. For example,

0x01 indicates undervoltage of the power supply.
0x02 indicates overvoltage of the power supply.
Parameter 3
Indicates the input voltage. For example,

0x00 indicates the -220 V input voltage.
0x01 indicates the -48 V AC/DC output voltage.
0x02 indicates the -48 V battery voltage.
0x03 indicates the -5 V DC/DC output voltage.

The NE might be abnormally running, which leads to the service interruption.
Possible Causes
l
The voltage of the input power supply is excessively low.
The voltage of the input power supply is too high.
There is no input voltage in the subrack.
The PGND of the subrack and BGND of the power supply are not co-ground.
The SCC is faulty.
Procedure
Step 1 Check whether the input power supply is correctly connected to the cabinet and subrack. If the
input power supply is not correctly connected to the equipment, rectify the fault. For details, see
the Installation Guide.
Step 2 If the alarm persists, check whether the voltage of the input power supply is normal. If not, rectify
the input voltage of the equipment power supply.
Step 3 In the case of the PMU board, query the voltage of the first/second power supply on the
U2000. If the voltage of the two power supplies are 79.6 V, it indicates that the PGND of the
subrack and BGND of the power supply may be not co-ground. Make sure the PGND and BGND
are co-ground. For details, see the Installation Guide.
Step 4 If the alarm persists, replace the power supply, For details, see the Parts Replacement.
Step 5 If the alarm persists, replace the SCC. For details, see the Parts Replacement.
----End
3-154

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Related Information
None
3.2.84 R_LOC
Description
The R_LOC is an alarm indicating loss of the clock on the receive line. This alarm occurs when
the clock signal fails to be extracted from the received signals.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Services at this port are interrupted.
Possible Causes
l
The link is abnormal and the board cannot normally extract clock signals.
The setting of the board clock tracing is incorrect.
Procedure
Step 1 Perform a self-loop on the board. Then, check whether the physical link is normal. If there is
any abnormity, such as OTUk_LOF, remove the fault.
Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the entire
network planning. Adjust the board clock setting if it is incorrect.
----End
Related Information
None
Issue 04 (2010-10-20)

3-155

Transport Platform
3 Alarm Processing
3.2.85 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is a critical alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

For the OptiX OSN 1800, the status of the external equipment connected to the alarm input
interface of the SCC board changes.
Possible Causes
l
The status of the alarm input of the SCC board changes.
The alarm input interface of the SCC 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 SCC board changes. If that is the case, remove the
fault of the external equipment.
Step 2 If no external equipment is connected to the alarm input interface, set the input interface to
Unused and the alarm is cleared.
----End
Related Information
None
3.2.86 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is a warning alarm of the alarm input.
3-156

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
None

Possible Causes
l
Procedure
----End
Related Information
None
3.2.87 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is a major alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None
Issue 04 (2010-10-20)

3-157

Transport Platform
3 Alarm Processing

Possible Causes
l
Procedure
----End
Related Information
None
3.2.88 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is a minor alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

Possible Causes
l
3-158

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
----End
Related Information
None
3.2.89 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
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The QoS of the service signals is affected. In a serious situation, the services are interrupted.
Possible Causes
l
The client side of the OTU at the opposite end has the B1_EXC alarm.
The demultiplexed client signals on the WDM side of the OTU at the local end have the
B1_EXC alarm.
Issue 04 (2010-10-20)

3-159

Transport Platform
3 Alarm Processing
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
3.2.90 REMOTE_FAULT
Description
The REMOTE_FAULT alarm indicates a remote fault.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The 10GE services in the flow control mode are configured on the client side of the board . If
the board receives the REMOTE_FAULT alarm, the received services may be interrupted.
Possible Causes
l
Cause 1: The opposite station receives the LOCAL_FAULT alarm.
Cause 1: The opposite station receives the LOCAL_FAULT alarm.
Procedure
1.
l
Clear the LOCAL_FAULT alarm in the opposite station.

1.
Replace the faulty board in the opposite side. For details, refer to "Replacing a Board"
----End
3-160

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Related Information
None
3.2.91 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the
S1 mode.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the ID of the priority table. Valid values are as follows:

l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source

The switching performs on the working clock source of the board, which influence the user
services.
Possible Causes
l
Cause 1: The fiber connection is faulty.
Cause 2: The upstream station generates the alarm.
Cause 1: The fiber connection is faulty.
Procedure
1.
Issue 04 (2010-10-20)
Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
see the Supporting Tasks.
3-161

Transport Platform
3 Alarm Processing
2.
l
If the alarm persists, replace the faulty board. For details, see the Parts
Replacement.
Cause 2: The upstream station generates the alarm.

1.
If the alarm persists, check whether the S1_SYN_CHANGE alarm is generated at the
upstream station. If yes, repeat steps to clear the S1_SYN_CHANGE alarm at the
upstream station. The S1_SYN_CHANGE alarm at the local station is then
automatically cleared.
----End
Related Information
None
3.2.92 SUB_RACK_OFFLINE
Description
The slave subrack is offline.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the offline slave subrack.

The offline slave subrack and the boards on this slave subrack cannot be managed by the master
subrack. If the slave subrack itself is not faulty, the services on the boards of the slave subrack
are not affected.
Possible Causes
3-162
Cause 1: The SCC board of the slave subrack is in reset state.
Cause 2: The Ethernet cable or optic fiber connected to the slave subrack is loosened.
Cause 3: The slave subrack is faulty and cannot get online.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Procedure
l
Cause 1: The SCC board of the slave subrack is in reset state.

1.
The slave subrack goes offline temporarily when the SCC board of the slave subrack
is being reset. After successful reset, the alarm is automatically cleared.
Cause 2: The network cable or optic fiber connected to the slave subrack is loosened.
1.
View the alarm parameter 1 to obtain the ID of the offline slave subrack. For example,
if the value of Parameter 1 is 0x03, the slave subrack with ID 3 is offline.
2.
Check whether the network cable or optic fiber connection between the master and
slave subracks is normal, or whether the network cable or optic fiber is faulty or
loosened. After the slave subrack gets online, the alarm is automatically cleared, and
the services on the slave subrack are not affected.
Cause 3: The slave subrack is faulty and cannot get online.

1.
Check whether the SCC board of slave subrack is faulty. If the SCC is faulty, replace
the SCC board of slave subrack.
2.
If the ID of this slave subrack will no longer be used, change the ID of the offline
slave subrack to 0xff. Then, the alarm is automatically cleared, and the subracks are
unavailable.
----End
Related Information
None
3.2.93 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
Alarm Type
Minor
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.
Issue 04 (2010-10-20)

3-163

Transport Platform
3 Alarm Processing
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
3.2.94 SUBRACK_TYPE_MISMATCH
Description
The alarm indicating that the subrack configured does not match the type of the physical subrack.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
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.
Cause 1: The subrack configured for the SCC does not match the type of the physical
subrack.
Procedure
3-164

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
1.
Determine whether the logical subrack or the physical subrack is incorrect according
to the actual network.
2.
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.
3.
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.
4.
If the alarm persists, contact Huawei for help.
----End
Related Information
None
3.2.95 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the activation times out.
During loading of the software package, the alarm occurs when the operation is not committed
120 seconds after activation operation.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
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 In the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
Issue 04 (2010-10-20)

3-165

Transport Platform
3 Alarm Processing
3.2.96 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic matching function
is disabled.
NOTE
After the automatic matching function is enabled, when a board is added to an NE, the system automatically
checks whether the board software matches the NE software. If not, the SCC board upgrades the board software
of the new board.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The SCC board cannot automatically update the software of the board that is newly inserted. If
the software of the new board mismatches the NE software, certain functions of the NE may
operate abnormally.
Possible Causes
The automatic matching switch is turned off.
Procedure
Step 1 If the alarm persists, contact Huawei engineers.
----End
Related Information
None
3.2.97 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.
3-166

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

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
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
3.2.98 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating a commitment failure. During loading of
the software package, the alarm occurs when the commitment operation fails.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None
Issue 04 (2010-10-20)

3-167

Transport Platform
3 Alarm Processing

The package loading fails and the upgrade of the software version fails.
Possible Causes
During the package loading, the dual-partition board fails in copying the new software from one
partition to the other.
NOTE
The dual-partition board has two file systems. The two partitions are of mutual backups. In normal states, every
file is saved in both partitions.
Procedure
Step 1 On the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
3.2.99 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
Alarm Type
Warning
Process alarm
Parameters
None

The working/protection backup function of the SCC board is disabled.
Possible Causes
The NE is performing the package loading operation.
3-168

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
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
3.2.100 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that the file is lost. The alarm occurs when
the SCC checks the software package and finds that a file in a partition of the SCC software
package is lost and the file cannot be restored from the related file in another partition. Next
time when the SCC checks the software package and finds the file, the alarm is cleared.
NOTE
The SCC checks the software package every time when it starts up and when the periodical check is performed.
The periodical check is performed every hour by default.
Attribute
Alarm Severity
Alarm Type
Critical
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.
Possible Causes
The file is lost and irrecoverable.
Procedure
Step 1 On the U2000, use a correct software package of this version to perform the package loading on
the board.
----End
Related Information
None
Issue 04 (2010-10-20)

3-169

Transport Platform
3 Alarm Processing
3.2.101 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that no matching board software is
available. After an NE is loaded with a customized software package, when a board is inserted,
the software for the board is not found in the customized software package. In this case, the
board cannot be matched automatically and thus the alarm occurs.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual
requirement.
NOTE
If the new board is inserted when an SWDL_CHGMNG_NOMATCH alarm is present in the system, the new
board will also report this alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The software version of the unit is inconsistent with that of the SCC board. Certain functions of
the NE may operate abnormally.
Possible Causes
The user uses the customized software package, in which no software for the normal board is
found.
Procedure
Step 1 On the U2000, choose correct software version to perform a normal package loading again.
----End
Related Information
None
3-170

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
3.2.102 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
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The software versions on the NE are inconsistent. Certain functions of the NE may operate
abnormally.
Possible Causes
The file of the software package is faulty, and the software version information of the software
package is not consistent with the actual software version information.
Procedure
Step 1 On the U2000, use a correct software package to perform package loading on the board.
----End
Related Information
None
3.2.103 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 04 (2010-10-20)

3-171

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The NE rollback fails. The board software cannot be recovered to the version before the package
loading. In this case, the board software version and the NE software version may mismatch.
Certain functions of the NE may operate abnormally.
Possible Causes
Certain board rollbacks fail when the NE performs the rollback.
Procedure
Step 1 On the U2000, use the correct software package to perform package loading on the board.
----End
Related Information
None
3.2.104 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating the loss of synchronization source level. This alarm
is reported when the board detects that no synchronization source with a higher priority than the
current synchronization source exists.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
3-172

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
table.
Name
Meaning
Parameter 1

l Clock source board number...............0x04, 0x05
l External clock source...............0xf0
l Internal clock source...............0xf1
Parameter 2

Clock source interface number...............0x01/0x02.
l External clock source 1...............0x01
l External clock source 2...............0x02
l Internal clock source...............0x01

When the SYNC_C_LOS alarm occurs, the clock source of the clock board set in the clock
source priority table is lost. As a result, the clock source of higher priority is unavailable and the
clock source switching may occur.
Possible Causes
The possible causes of the SYNC_C_LOS alarm are as follows:
l
If the higher-level clock source is unavailable, the fiber cut occurs (in the case of tracing
the line clock source) or there is no input of the external clock source (in the case of tracing
the external clock source).
The hard reset is performed on the board of the access clock source, or the upstream traced
clock source board is faulty.
The clock source switching in the S1 byte mode occurs at the local station.
The input of the external clock source (BITS) changes.
Procedure
Step 1 View alarms on the U2000 to check whether there are alarms that are caused by the loss of clock
source on the local NE .
Option
Description
There is the R_LOS, R_LOC, R_LOF, or

T_ALOS alarm

There is no alarm
Go to step 3.
Step 2 View alarms on the U2000 to check whether the SYNC_C_LOS alarm is cleared.
Issue 04 (2010-10-20)

3-173

Transport Platform
3 Alarm Processing
Option
Description
Step 3 If the priority level table is not properly configured, configure the clock source priority table
again.
Step 4 View alarms on the U2000 to check whether the SYNC_C_LOS alarm is cleared.
Option
Description
Step 5 If the line clock source is traced, check whether the quality of the upstream clock source changes.
If the external clock source is traced, check whether the external clock source works normally.
Refer to S1_SYN_CHANGE.
----End
Related Information
None
3.2.105 SYSLOG_COMM_FAIL
Description
The communication between an NE and the syslog server fails. The alarm is generated when
the session or the connection between an NE and the syslog server is abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Name
Meaning
Parameters 1 to 4 Indicates the address of the syslog server.

Parameter 5
3-174
Indicates the type of the fault that causes the alarm. 0x0a indicates that the
connection fails. 0x02 indicates that the session is abnormal.

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing

There is no impact on services, and no bit error is generated. But you can not find the syslog
server.
Possible Causes
In the TCP mode, the connection between an NE and the syslog server or the session between
servers is abnormal.
Procedure
Step 1 Check whether the board is returned for repair or not. If yes, there is no need to handle the alarm.
Step 2 Select the Start Syslog Service check box.
----End
Related Information
None
3.2.106 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is excessively high. This alarm
occurs when the laser temperature is higher than the upper laser temperature threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the temperature of the tube core of the optical module is excessively high, the working
wavelengths of the optical module and the client services are affected.
Possible Causes
l
The working temperature of the board is excessively high.
The laser is faulty.
The module performance detection circuit is faulty.
Issue 04 (2010-10-20)

3-175

Transport Platform
3 Alarm Processing
Procedure
Step 1 Check the board ambient temperature and ventilation of the equipment room. If the board
ambient temperature is excessively high, cool the equipment room with cooling devices, such
as an air conditioner.
----End
Related Information
None
3.2.107 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is excessively low. This alarm
occurs when the laser temperature is lower than the lower threshold of the laser temperature.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

This has impact on the working wavelengths of the optical module and affects the client services.
Possible Causes
l
Working temperature of the board is excessively low.
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.
----End
3-176

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Related Information
None
3.2.108 TEMP_ALARM
Description
The temperature threshold crossing alarm. This alarm is generated when the board ambient
temperature crosses the board temperature threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
table.
Parameter 1 Indicates whether the temperature crosses the upper or lower threshold. For
example,
l 0x01 denotes that the temperature crosses the upper threshold.
l 0x02 denotes that the temperature crosses the lower threshold.

Services borne on the board might be affected.
Possible Causes
l
The board ambient temperature is overhigh.
The board ambient temperature is overlow.
Procedure
Step 1 Check whether the fan runs normally and whether the air duct is blocked because the dust filter
of the fan is not cleaned in a long period.
Issue 04 (2010-10-20)

3-177

Transport Platform
3 Alarm Processing
----End
Related Information
None
3.2.109 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature crosses the threshold.
This alarm occurs, when the system detects that the board working temperature is higher than
the upper threshold or lower than the lower threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
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.
Possible Causes
The possible causes of the TEMP_OVER alarm are as follows:
l
Cause 1: The fan stops working or the air filter is excessively dusty.
Identification method: Query the alarms through the U2000.
Cause 2: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
Identification method: Check the external environment.
Cause 3: The fan is not in position.

Identification method: Query the board status or alarms through the U2000.
l
3-178

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Identification method: Use the exclusive method.
Procedure
l
Cause 1: The fan stops working or the air filter is excessively dusty.
1.
See Querying Board Temperature in the Supporting Task to check the current
temperature of the board. If the temperature is abnormal, check whether the
FAN_FAIL alarm exists. If such alarm exists, clear the alarm first.
2.
Then, check whether the TEMP_OVER alarm is cleared. If the alarm persists, check
whether the air filter is excessively dusty, thus causing the problem of heat dissipation.
You can feel the wind and the temperature of the wind at the air exhaust vent.
3.
If the problem is caused by dusty the air filter, remove the air filter and clean it. For
details, see Cleaning the Air Filter in the Supporting Task.
4.
Then, check whether the alarm is cleared. If the alarm persists, see Cause 2.
Cause 2: The ambient temperature is excessively high or low because of the cooler or heater
fault.
1.
Check whether the ambient temperature of the equipment room is higher than 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
Cause 3: The fan is not in position.

1.
Check whether the NE reports the BD_STATUS alarm or check whether the fan is in
position on the U2000. If the fan is not in position, place it firmly.
2.

1.
Replace the board that reports the alarm. For details, see the Parts Replacement.
----End
Related Information
None
3.2.110 THUNDERALM
Description
The THUNDERALM is an alarm indicating a lighting protection circuit failure.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Issue 04 (2010-10-20)

3-179

Transport Platform
3 Alarm Processing
Parameters
table.
Parameter
Description
Parameter 1
Indicates the number of the unit that reports the alarm. For example,
0x01 indicates the PIU1 unit.
0x02 indicates the PIU2 unit.

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.
Possible Causes
l
The board hardware is faulty.
Procedure
----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.
3.2.111 TU_AIS
Description
The TU_AIS is an alarm indicating that the lower order path signals received on the crossconnect unit side by the tributary board are all "1"s.
Attribute
3-180
Alarm Severity
Alarm Type
Major
Communication alarm

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Parameters
table.
Name
Meaning
Parameter 1
E1 tributary board:
BUS number
l BUS A......................0x01
l BUS B......................0x02

When the TU_AIS alarm occurs, the lower order path signals received on the cross-connection
side by the tributary board are all "1"s. Consequently, the services in the lower order path are
unavailable. If the SNCP protection is configured for the tributary board in the lower order path,
the TU_AIS will trigger the switching of the SNCP protection.
When the TU_AIS alarm occurs, the system returns the LP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the TU_AIS alarm are as follows:
l
The relevant path at the opposite station is faulty.
The higher order alarms occur.
The cross-connect unit is faulty.
Procedure
Step 1 View alarms on the U2000 to check whether there is the section-level or higher-level alarm on
the local line board that is configured with the lower order services to the tributary board.
Issue 04 (2010-10-20)
Option
Description
There is the R_LOS, R_LOC, R_LOF,

MS_AIS, AU_AIS, or AU_LOP alarm

The AIS is set inserted when there is the

B1_EXC, B2_EXC, B2_SD, B3_EXC,
HP_LOM, R_OOF, B1_SD, B3_SD,
HP_TIM, HP_UNEQ, or HP_SLM alarm


3-181

Transport Platform
3 Alarm Processing
Step 2 Check whether there is the PDH alarm at the port that is configured with interconnection services
on the opposite tributary board.
Option
Description
There is the T_ALOS, E1_LOS, E1_LOC, or

UP_E1_AIS alarm
Refer tot the corresponding section in this

Step 3 Check whether the services are correctly configured. If not, modify the service configuration
and issue it again.
Step 4 View alarms on the U2000 to check whether the TU_AIS alarm is cleared.
Option
Description
Step 5 Reset the faulty boards.
CAUTION
Performing a cold reset on the board, removing and inserting the board, or replacing the board
will interrupt services. This operation is of risk.
Step 6 View alarms on the U2000 to check whether the TU_AIS alarm is cleared.
Option
Description
Step 7 Replace the faulty SCC board.

----End
Related Information
R_LOS, R_LOC, R_LOF, MS_AIS, AU_AIS, AU_LOP, B1_EXC, B2_EXC, B2_SD,
B3_EXC, HP_LOM, R_OOF, B1_SD, B3_SD, HP_TIM, HP_UNEQ, HP_SLM, E1_LOS,
E1_LOC, and UP_E1_AIS
3.2.112 TU_LOP
3-182

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Description
The TU_LOP is an alarm indicating that the TU pointer in the signals received by the tributary
board on the cross-connection side is lost.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
BUS number
l BUS A..................0x01
l BUS B.................0x02

When the TU_LOP alarm occurs, the TU pointer in the signals received by the tributary board
on the cross-connection side is lost. As a result, the services in the path are unavailable. If the
SNCP/PP protection is configured for the tributary board in the lower order path, the TU_LOP
will trigger the switching of the SNCP/PP protection.
When the TU_LOP alarm occurs, the system returns the LP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the AU_LOP alarm are as follows:
l
The fault is with the interface between the tributary board and the cross-connect unit.
Procedure
Step 1 Check whether the cross-connect and timing board or the tributary board is correctly configured.
Step 2 View alarms on the U2000 to check whether the TU_LOP alarm is cleared.
Issue 04 (2010-10-20)
Options
Description

3-183

Transport Platform
3 Alarm Processing
Options
Description
Step 3 If the tributary unit is faulty, hard reset the faulty board.
CAUTION
Performing a cold reset on the board will interrupt services. This operation is of risk.
Step 4 View alarms on the U2000 to check whether the TU_LOP alarm is cleared.
Options
Description
Step 5 The cross-connect unit is faulty. Replace the faulty board.

----End
Related Information
None.
3.2.113 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indicating that the upstream E1 signals received on the PDH side
of the E1 tributary board are all "1"s.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
3-184

Issue 04 (2010-10-20)

Transport Platform
3 Alarm Processing
Name
Meaning
Parameter 1
Indicates the optical interface number. The value is always 0x01.
Parameter 2, parameter 3 Indicates the path number.

Parameter 4
The value is always 0xff (Reserved).
Parameter 5

When the UP_E1_AIS alarm occurs, the E1 signals received on the PDH side of the tributary
board are all "1"s. As a result, the lower order services at the interface are unavailable.
Possible Causes
The possible causes of the alarm are as follows:
l
There is TU_LOP or TU_AIS alarm on the local tributary board.
The local tributary board is faulty.
Procedure
Step 1 View alarms on the U2000 and check whether there is TU_LOP or TU_AIS alarm on the local
tributary board. If yes, clear it and then check whether the UP_E1_AIS alarm disappears.
Option
Description
Step 2 Replace the faulty tributary board.

----End
Related Information
None.
3.2.114 VCXO_LOC
Description
Local oscillator loss of clock. The alarm is generated when the crystal oscillator of the board is
abnormal.
Issue 04 (2010-10-20)

3-185

Transport Platform
3 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The abnormal crystal oscillator of the board leads to that the board cannot work normally, which
influences the user services.
Possible Causes
Procedure
Step 1 Perform a cold reset on the faulty board through the U2000. For details, see the
Troubleshooting.
Step 2 If the alarm persists, replace the faulty board. Foe details see Parts Replacement.
----End
Related Information
None
3-186

Issue 04 (2010-10-20)

Transport Platform
4 Performance Event List
Performance Event List
About This Chapter

This chapter lists the names, description and relevant boards of the performance event in
alphabetical order and lists the performance event of every board.
4.1 Product Performance Event List
Lists the different types of performance event.
4.2 Board Performance Event List
This section list the performance event of every board.
Issue 04 (2010-10-20)

4-1

Transport Platform
4.1 Product Performance Event List

Lists the different types of performance event.
4.1.1 Performance Event List of Check and Error Correction
Lists the performance event of check and error correction.
4.1.2 Performance Event of Pointer Justification
This topic lists the performance events for pointer justifications.
4.1.3 Performance Event List of Equipment Function
Lists the performance event of equipment function.
4.1.4 Performance Event of Multiplex Section Bit Error
Lists performance event of multiplex section bit error.
4.1.5 Performance Event List of Regenerator Section Bit Error
Lists the performance event of regenerator section bit error.
4.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.
4.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.
4.1.8 Performance Event List of RMON Function
Lists the performance event of RMON function.
4.1.1 Performance Event List of Check and Error Correction

Lists the performance event of check and error correction.
Table 4-1 Performance Event List of Check and Error Correction
4-2
Name
Description
Board
FEC_AFT_COR_ER
After FEC Correct Errored

Rate
FEC_AFT_COR_ERA
VR
After FEC Correct Average

Errored Rate in monitor period

LQPU, LSPL, LSPU, LSX
FEC_BEF_COR_ER
Before FEC Correct Errored

Rate
FEC_BEF_COR_ERA
VR
Before FEC Correct Average

Errored Rate in monitor period
FEC_COR_0BIT_CN
T
Forward Error Correction Corrected 0 Bit Count
FEC_COR_1BIT_CN
T
Forward Error Correction Corrected 1 Bit Count
FEC_COR_BYTE_CN
T
Forward Error Correction Corrected Byte Count

Issue 04 (2010-10-20)

Transport Platform
Issue 04 (2010-10-20)
Name
Description
FEC_UNCOR_BLOC
K_CNT
Forward Error Correction Uncorrected Block Count
GPON_UF_BIP_CNT
GPON Upstream frame BIP

error
LQPL, LQPU
GPON_DF_BIP_CNT
GPON Downstream frame BIP

error
LQPL
ODU0_PM_BBE
ODU0 PM Section
Background Block Error
LDE
ODU0_PM_BBER
ODU0 PM Section Ratio of

ODU0_PM_ES
ODU0 PM Section Errored

Second
ODU0_PM_FEBBE
ODU0 PM Section Far End

ODU0_PM_FEBBER
ODU0 PM Section Ratio of Far

End Background Block Error
ODU0_PM_FEES

Errored Second
ODU0_PM_FESES

Severely Errored Second
ODU0_PM_FESESR

End Severely Errored Second
ODU0_PM_FEUAS
ODU0 PM Section Unavailable

Second
ODU0_PM_SES
ODU0 PM Section Severely

Errored Second
ODU0_PM_SESR

ODU0_PM_UAS

Second
ODU1_PM_BBE
ODU1 PM Section
ODU1_PM_BBER

ODU1_PM_ES

Second
ODU1_PM_FEBBE


Board

LSPU
4-3

Transport Platform
4-4
Name
Description
ODU1_PM_FEBBER

ODU1_PM_FEES

Errored Second
ODU1_PM_FESES

ODU1_PM_FESESR

ODU1_PM_FEUAS

Second
ODU1_PM_SES

Errored Second
ODU1_PM_SESR

ODU1_PM_UAS

Second
ODU2_PM_BBE
ODU2 PM Section
ODU2_PM_BBER

ODU2_PM_ES

Second
ODU2_PM_FEBBE

ODU2_PM_FEBBER

ODU2_PM_FEES

Errored Second
ODU2_PM_FESES

ODU2_PM_FESESR

ODU2_PM_FEUAS

Second
ODU2_PM_SES

Errored Second
ODU2_PM_SESR


Board
Issue 04 (2010-10-20)

Transport Platform
Issue 04 (2010-10-20)
Name
Description
ODU2_PM_UAS

Second
ODU5G_PM_BBE
ODU5G PM Section
ODU5G_PM_BBER
ODU5G PM Section Ratio of

ODU5G_PM_ES
ODU5G PM Section Errored

Second
ODU5G_PM_FEBBE
ODU5G PM Section Far End

ODU5G_PM_FEBBE
R

Far End Background Block
Error
ODU5G_PM_FEES

Errored Second
ODU5G_PM_FESES

ODU5G_PM_FESESR

Far End Severely Errored
Second
ODU5G_PM_FEUAS
ODU5G PM Section
Unavailable Second
ODU5G_PM_SES
ODU5G PM Section Severely

Errored Second
ODU5G_PM_SESR

ODU5G_PM_UAS
ODU5G PM Section
Unavailable Second
OTU1_BBE
OTU1 Background Block Error
OTU1_BBER
OTU1 Ratio of Background

Block Error
OTU1_BIAES
OTU1 SM Section Background

Introduced Alignment Errored
Second
OTU1_ES
OTU1 Errored Second
OTU1_FEBBE
OTU1 SM Section Far End


Board
LQG

LSPU
4-5

Transport Platform
4-6
Name
Description
OTU1_FEBBER
OTU1 SM Section Ratio of Far

OTU1_FEES

Errored Second
OTU1_FESES

OTU1_FESESR

OTU1_FEUAS
OTU1 SM Section Unavailable

Second
OTU1_IAES
OTU1 SM Section Introduced

Alignment Errored Second
OTU1_SES
OTU1 Severely Errored

Second
OTU1_SESR
OTU1 Ratio of Severely

Errored Second
OTU1_UAS
OTU1 Unavailable Second
OTU2_BBE
OTU2 Background Block Error
OTU2_BBER
OTU2 Ratio of Background

Block Error
OTU2_BIAES
OTU2 SM Section Background

Second
OTU2_ES
OTU2 Errored Second
OTU2_FEBBE

OTU2_FEBBER

OTU2_FEES

Errored Second
OTU2_FESES

OTU2_FESESR

OTU2_FEUAS
OTU2 SM Section Unavailable

Second

Board
Issue 04 (2010-10-20)

Transport Platform
Issue 04 (2010-10-20)
Name
Description
OTU2_IAES
OTU2 SM Section Introduced

OTU2_SES
OTU2 Severely Errored

Second
OTU2_SESR
OTU2 Ratio of Severely

Errored Second
OTU2_UAS
OTU2 Unavailable Second
OTU5G_BBE
OTU5G Background Block

Error
OTU5G_BBER
OTU5G Ratio of Background

Block Error
OTU5G_BIAES
OTU5G SM Section
Background Introduced
OTU5G_ES
OTU5G Errored Second
OTU5G_FEBBE
OTU5G SM Section Far End

OTU5G_FEBBER
OTU5G SM Section Ratio of

Far End Background Block
Error
OTU5G_FEES

Errored Second
OTU5G_FESES

OTU5G_FESESR
OTU5G SM Section Ratio of

Far End Severely Errored
Second
OTU5G_FEUAS
OTU5G SM Section
Unavailable Second
OTU5G_IAES
OTU5G SM Section
Second
OTU5G_SES
OTU5G Severely Errored

Second
OTU5G_SESR
OTU5G Ratio of Severely

Errored Second
OTU5G_UAS
OTU5G Unavailable Second

Board
LQG
4-7

Transport Platform
4.1.2 Performance Event of Pointer Justification

This topic lists the performance events for pointer justifications.
Table 4-2 Pointer justification performance event list
Name
Description
Board
AUPJCHIGH
Count of positive AU
pointer justifications
TSP
AUPJCLOW
Count of negative AU
TUPJCHIGH
Count of positive TU
TUPJCLOW
Count of negative TU
4.1.3 Performance Event List of Equipment Function

Lists the performance event of equipment function.
Table 4-3 Performance Event List of Equipment Function
4-8
Name
Description
Board
CCVCUR
Current Pump Laser Cooling

Current Value
OPU
CCVMAX
Maximum Pump Laser

Cooling Current Value
CCVMIN
Minimum Pump Laser

Cooling Current Value
ENVTMPMAX
Maximum Board
Environmental Temperature
Value
ENVTMPMIN
Minimum Board
Environmental Temperature
Value
ENVTMPCUR
Current Board Environmental

Temperature Value
LSBIASCUR
Current Laser Bias Current

Value
LSBIASMAX
Maximum Laser Bias Current

Value

LSX, LWX2, OLP, OPU, TSP

LSX, LWX2, TSP
Issue 04 (2010-10-20)

Transport Platform
Issue 04 (2010-10-20)
Name
Description
LSBIASMIN
Minimum Laser Bias Current

Value
LSCLCCUR
Current Laser Cooling

Current Value
LSCLCMAX
Maximum Laser Cooling

Current Value
LSCLCMIN
Minimum Laser Cooling

Current Value
LSOOPCUR
Current Output Optical Power

Value
LSOOPMAX
Maximum Output Optical

Power Value
LSOOPMIN
Minimum Output Optical

Power Value
LSIOPCUR
Current Input Optical Power

Value
LSIOPMAX
Maximum Input Optical

Power Value
LSIOPMIN
Minimum Input Optical

Power Value
LSTMPCUR
Current Laser Temperature

Value
LSTMPMAX
Maximum Laser Temperature

Value
LSTMPMIN
Minimum Laser Temperature

Value
PUMPTMPCUR
Current Pump Laser

Temperature Value
PUMPTMPMAX
Maximum Pump Laser

Temperature Value
PUMPTMPMIN
Minimum Pump Laser

Temperature Value
SUMIOPCUR
Current Total Input Optical

Power Value
SUMIOPMAX
Maximum Total Input Optical

Power Value
SUMIOPMIN
Minimum Total Input Optical

Power Value

Board

LSX, LWX2, TSP

LSX, LWX2, TSP

LSX, LWX2, OLP, TSP

LSX, LWX2, TSP
OPU
OLP, OPU
4-9

Transport Platform
Name
Description
Board
SUMOOPCUR
Current Total Output Optical

Power Value
OPU
SUMOOPMAX
Maximum Total Output

Optical Power Value
SUMOOPMIN
Minimum Total Output

Optical Power Value
WCVCUR
Current Pump Laser Working

Current Value
WCVMAX
Maximum Pump Laser

Working Current Value
WCVMIN
Minimum Pump Laser

Working Current Value
OPU
4.1.4 Performance Event of Multiplex Section Bit Error

Lists performance event of multiplex section bit error.
Table 4-4 Performance Event list of Multiplex Section Bit Error
Name
Description
Board
MSBBE
MS Background Block Error
TSP
MSCSES
MS Consecutive Severely
Errored Second
MSES
MS Errored Second
MSFEBBE
MS Far End Background

Block Error
MSFECSES
MS Far End Consecutive

MSFEES
MS Far End Errored Second
MSFESES
MS Far End Severely Errored

Second
MSSES
MS Severely Errored Second
MSUAS
MS Unavailable Second
4.1.5 Performance Event List of Regenerator Section Bit Error

Lists the performance event of regenerator section bit error.
4-10

Issue 04 (2010-10-20)

Transport Platform
Table 4-5 Performance Event List of Regenerator Section Bit Error

Name
Description
Board
RSBBE
RS Background Block Error
RSES
RS Errored Second

LQPU, LSX, TSP
RSSES
RS Severely Errored Second
RSCSES
RS Consecutive Severely
Errored Second
RSUAS
RS Unavailable Second
RSOFS
RS Out-of-Frame Second
RSOOF
Regenerator section of OOF

perferance seconds
TSP
4.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 4-6 Higher order path performance event list
Issue 04 (2010-10-20)
Name
Description
Board
HPBBE
Higher order path block of

background error
TSP
HPES
Higher order path errored

second
HPSES
Higher order path

severely errored second
HPUAS
Higher order path far end

unavailable second
HPCSES
Higher order path

consecutive severely
errored second
HPFEBBE

block of background error
HPFEES

errored second
HPFESES

HPFECSES
Higher order path

unavailable second

4-11

Transport Platform
4.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 4-7 Lower order path performance event list
Name
Description
Board
LPBBE
Lower order path block of

background error
TSP
LPFEBBE
Lower order path far end

block of background error
LPES
Lower order path errored

second
LPFEES

errored second
LPSES
Lower order path severely

errored second
LPFESES

LPCSES
Lower order path

errored second
LPFECSES

errored second
LPUAS
Lower order path

unavailable second
4.1.8 Performance Event List of RMON Function

Lists the performance event of RMON function.
Table 4-8 RMON Performance Event List
Name
Board
Drop Events
LQM, LQM2, LDE, LDGF, LDGF2, LQG,

LOE
FCS and Alignment Errors
LOE
Broadcast Packets Received

LOE, LSX
Multicast Packets Received
4-12

Issue 04 (2010-10-20)

Transport Platform
Name
Board
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)
Length)
Length)
Length)
Packets Received (1519~MTU Octets in
Length)
Packets Transmitted (64 Octets in Length)
Packets Transmitted (65~127 Octets in
Length)

LOE, LSX

Length)
Length)
Length)
Length)
Packets Transmitted (1519~MTU Octets in
Length)
Unicast Packets Received

LOE, LSX
Unicast Packets Transmitted
LOE, LDE, LQM, LQM2, LDGF, LDGF2,

LQG, LSX
Multicast Packets Transmitted

Broadcast Packets Transmitted
Issue 04 (2010-10-20)

4-13

Transport Platform
Name
Board
Pause Frames Received

LOE, LSX
Pause Frames Transmitted
LQM, LQM2, LDGF, LDGF2, LQG, LOE,

LDE, LSX
Good Octets Received

LOE, LSX
Good Octets Transmitted

LDE, LSX
Bad Octets Received

LOE, LSX
Bad Octets Transmitted

LDE, LSX
FCS Errors

LOE, LSX
Alignment Errors
LSX
Octets Received
Octets Transmitted
4.2 Board Performance Event List

This section list the performance event of every board.
4.2.1 LDE Board Performance Event List
4.2.2 LDGF Board Performance Event List
4.2.3 LDGF2 Board Performance Event List
4.2.4 LOE Board Performance Event List
4.2.5 LQG Board Performance Event List
4.2.6 LQM2 Board Performance Event List
4.2.7 LQM Board Performance Event List
4.2.8 LQPL Board Performance Event List
4.2.9 LQPU Board Performance Event List
4.2.10 LSPL Board Performance Event List
4.2.11 LSPR Board Performance Event List
4.2.12 LSPU Board Performance Event List
4.2.13 LSX Board Performance Event List
4-14

Issue 04 (2010-10-20)

Transport Platform
4.2.14 LWX2 Board Performance Event List

4.2.15 OLP Board Performance Event List
4.2.16 OPU Board Performance Event List
4.2.17 TSP Board Performance Event List
4.2.1 LDE Board Performance Event List
Issue 04 (2010-10-20)
ENVTMPCUR
LSOOPMIN
ODU1_PM_FESES
ENVTMPMAX
LSTMPCUR
ODU1_PM_FESESR
ENVTMPMIN
LSTMPMAX
ODU1_PM_FEUAS
FEC_AFT_COR_ER
LSTMPMIN
ODU1_PM_SES
FEC_AFT_COR_ERAVR
ODU0_PM_BBE
ODU1_PM_SESR
FEC_BEF_COR_ER
ODU0_PM_BBER
ODU1_PM_UAS
FEC_BEF_COR_ERAVR
ODU0_PM_ES
OTU1_BBE
FEC_COR_0BIT_CNT
ODU0_PM_FEBBE
OTU1_BBER
FEC_COR_1BIT_CNT
ODU0_PM_FEBBER
OTU1_BIAES
FEC_COR_BYTE_CNT
ODU0_PM_FEES
OTU1_ES
FEC_UNCOR_BLOCK_CN
T
ODU0_PM_FESES
OTU1_FEBBE
LSBIASCUR
ODU0_PM_FESESR
OTU1_FEBBER
LSBIASMAX
ODU0_PM_FEUAS
OTU1_FEES
LSBIASMIN
ODU0_PM_SES
OTU1_FESES
LSCLCCUR
ODU0_PM_SESR
OTU1_FESESR
LSCLCMAX
ODU0_PM_UAS
OTU1_FEUAS
LSCLCMIN
ODU1_PM_BBE
OTU1_IAES
LSIOPCUR
ODU1_PM_BBER
OTU1_SES
LSIOPMAX
ODU1_PM_ES
OTU1_SESR
LSIOPMIN
ODU1_PM_FEBBE
OTU1_UAS
LSOOPCUR
ODU1_PM_FEBBER
LSOOPMAX
ODU1_PM_FEES

4-15

Transport Platform
4.2.2 LDGF Board Performance Event List

ENVTMPCUR
LSIOPMAX
ODU1_PM_SESR
ENVTMPMAX
LSIOPMIN
ODU1_PM_UAS
ENVTMPMIN
LSOOPCUR
OTU1_BBE
FEC_AFT_COR_ER
LSOOPMAX
OTU1_BBER
FEC_AFT_COR_ERAVR
LSOOPMIN
OTU1_BIAES
FEC_BEF_COR_ER
LSTMPCUR
OTU1_ES
FEC_BEF_COR_ERAVR
LSTMPMAX
OTU1_FEBBE
FEC_COR_0BIT_CNT
LSTMPMIN
OTU1_FEBBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
OTU1_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
OTU1_FESES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_ES
OTU1_FESESR
LSBIASCUR
ODU1_PM_FEBBE
OTU1_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
OTU1_IAES
LSBIASMIN
ODU1_PM_FEES
OTU1_SES
LSCLCCUR
ODU1_PM_FESES
OTU1_SESR
LSCLCMAX
ODU1_PM_FESESR
OTU1_UAS
LSCLCMIN
ODU1_PM_FEUAS
LSIOPCUR
ODU1_PM_SES
4.2.3 LDGF2 Board Performance Event List
4-16
ENVTMPCUR
LSIOPMAX
ODU1_PM_SESR
ENVTMPMAX
LSIOPMIN
ODU1_PM_UAS
ENVTMPMIN
LSOOPCUR
OTU1_BBE
FEC_AFT_COR_ER
LSOOPMAX
OTU1_BBER
FEC_AFT_COR_ERAVR
LSOOPMIN
OTU1_BIAES
FEC_BEF_COR_ER
LSTMPCUR
OTU1_ES
FEC_BEF_COR_ERAVR
LSTMPMAX
OTU1_FEBBE
FEC_COR_0BIT_CNT
LSTMPMIN
OTU1_FEBBER

Issue 04 (2010-10-20)

Transport Platform
FEC_COR_1BIT_CNT
ODU1_PM_BBE
OTU1_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
OTU1_FESES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_ES
OTU1_FESESR
LSBIASCUR
ODU1_PM_FEBBE
OTU1_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
OTU1_IAES
LSBIASMIN
ODU1_PM_FEES
OTU1_SES
LSCLCCUR
ODU1_PM_FESES
OTU1_SESR
LSCLCMAX
ODU1_PM_FESESR
OTU1_UAS
LSCLCMIN
ODU1_PM_FEUAS
LSIOPCUR
ODU1_PM_SES
4.2.4 LOE Board Performance Event List
Issue 04 (2010-10-20)
ENVTMPCUR
LSIOPMAX
ODU2_PM_SESR
ENVTMPMAX
LSIOPMIN
ODU2_PM_UAS
ENVTMPMIN
LSOOPCUR
OTU2_BBE
FEC_AFT_COR_ER
LSOOPMAX
OTU2_BBER
FEC_AFT_COR_ERAVR
LSOOPMIN
OTU2_BIAES
FEC_BEF_COR_ER
LSTMPCUR
OTU2_ES
FEC_BEF_COR_ERAVR
LSTMPMAX
OTU2_FEBBE
FEC_COR_0BIT_CNT
LSTMPMIN
OTU2_FEBBER
FEC_COR_1BIT_CNT
ODU2_PM_BBE
OTU2_FEES
FEC_COR_BYTE_CNT
ODU2_PM_BBER
OTU2_FESES
FEC_UNCOR_BLOCK_CN
T
ODU2_PM_ES
OTU2_FESESR
LSBIASCUR
ODU2_PM_FEBBE
OTU2_FEUAS
LSBIASMAX
ODU2_PM_FEBBER
OTU2_IAES
LSBIASMIN
ODU2_PM_FEES
OTU2_SES
LSCLCCUR
ODU2_PM_FESES
OTU2_SESR
LSCLCMAX
ODU2_PM_FESESR
OTU2_UAS
LSCLCMIN
ODU2_PM_FEUAS

4-17

Transport Platform
LSIOPCUR
ODU2_PM_SES
4.2.5 LQG Board Performance Event List

ENVTMPCUR
LSIOPMIN
OTU5G_BBE
ENVTMPMAX
LSOOPCUR
OTU5G_BBER
ENVTMPMIN
LSOOPMAX
OTU5G_BIAES
FEC_AFT_COR_ER
LSOOPMIN
OTU5G_ES
FEC_AFT_COR_ERAVR
LSTMPCUR
OTU5G_FEBBE
FEC_BEF_COR_ER
LSTMPMAX
OTU5G_FEBBER
FEC_BEF_COR_ERAVR
LSTMPMIN
OTU5G_FEES
FEC_COR_0BIT_CNT
ODU5G_PM_BBE
OTU5G_FESES
FEC_COR_1BIT_CNT
ODU5G_PM_BBER
OTU5G_FESESR
FEC_COR_BYTE_CNT
ODU5G_PM_ES
OTU5G_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU5G_PM_FEBBE
OTU5G_IAES
LSBIASCUR
ODU5G_PM_FEBBER
OTU5G_SES
LSBIASMAX
ODU5G_PM_FEES
OTU5G_SESR
LSBIASMIN
ODU5G_PM_FESES
OTU5G_UAS
LSCLCCUR
ODU5G_PM_FESESR
RSBBE
LSCLCMAX
ODU5G_PM_FEUAS
RSCSES
LSCLCMIN
ODU5G_PM_SES
RSES
LSIOPCUR
ODU5G_PM_SESR
RSSES
LSIOPMAX
ODU5G_PM_UAS
RSUAS
4.2.6 LQM2 Board Performance Event List
4-18
ENVTMPCUR
LSIOPMIN
OTU1_BBE
ENVTMPMAX
LSOOPCUR
OTU1_BBER
ENVTMPMIN
LSOOPMAX
OTU1_BIAES
FEC_AFT_COR_ER
LSOOPMIN
OTU1_ES

Issue 04 (2010-10-20)

Transport Platform
FEC_AFT_COR_ERAVR
LSTMPCUR
OTU1_FEBBE
FEC_BEF_COR_ER
LSTMPMAX
OTU1_FEBBER
FEC_BEF_COR_ERAVR
LSTMPMIN
OTU1_FEES
FEC_COR_0BIT_CNT
ODU1_PM_BBE
OTU1_FESES
FEC_COR_1BIT_CNT
ODU1_PM_BBER
OTU1_FESESR
FEC_COR_BYTE_CNT
ODU1_PM_ES
OTU1_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_FEBBE
OTU1_IAES
LSBIASCUR
ODU1_PM_FEBBER
OTU1_SES
LSBIASMAX
ODU1_PM_FEES
OTU1_SESR
LSBIASMIN
ODU1_PM_FESES
OTU1_UAS
LSCLCCUR
ODU1_PM_FESESR
RSBBE
LSCLCMAX
ODU1_PM_FEUAS
RSCSES
LSCLCMIN
ODU1_PM_SES
RSES
LSIOPCUR
ODU1_PM_SESR
RSSES
LSIOPMAX
ODU1_PM_UAS
RSUAS
4.2.7 LQM Board Performance Event List
Issue 04 (2010-10-20)
ENVTMPCUR
LSIOPMIN
OTU1_BBE
ENVTMPMAX
LSOOPCUR
OTU1_BBER
ENVTMPMIN
LSOOPMAX
OTU1_BIAES
FEC_AFT_COR_ER
LSOOPMIN
OTU1_ES
FEC_AFT_COR_ERAVR
LSTMPCUR
OTU1_FEBBE
FEC_BEF_COR_ER
LSTMPMAX
OTU1_FEBBER
FEC_BEF_COR_ERAVR
LSTMPMIN
OTU1_FEES
FEC_COR_0BIT_CNT
ODU1_PM_BBE
OTU1_FESES
FEC_COR_1BIT_CNT
ODU1_PM_BBER
OTU1_FESESR
FEC_COR_BYTE_CNT
ODU1_PM_ES
OTU1_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_FEBBE
OTU1_IAES
LSBIASCUR
ODU1_PM_FEBBER
OTU1_SES

4-19

Transport Platform
LSBIASMAX
ODU1_PM_FEES
OTU1_SESR
LSBIASMIN
ODU1_PM_FESES
OTU1_UAS
LSCLCCUR
ODU1_PM_FESESR
RSBBE
LSCLCMAX
ODU1_PM_FEUAS
RSCSES
LSCLCMIN
ODU1_PM_SES
RSES
LSIOPCUR
ODU1_PM_SESR
RSSES
LSIOPMAX
ODU1_PM_UAS
RSUAS
4.2.8 LQPL Board Performance Event List
4-20
ENVTMPCUR
ODU1_PM_BBER
OTU1_FEBBER
ENVTMPMAX
ODU1_PM_ES
OTU1_FEES
ENVTMPMIN
ODU1_PM_FEBBE
OTU1_FESES
FEC_AFT_COR_ER
ODU1_PM_FEBBER
OTU1_FESESR
FEC_AFT_COR_ERAVR
ODU1_PM_FEES
OTU1_FEUAS
FEC_BEF_COR_ER
ODU1_PM_FESES
OTU1_IAES
FEC_BEF_COR_ERAVR
ODU1_PM_FESESR
OTU1_SES
FEC_COR_0BIT_CNT
ODU1_PM_FEUAS
OTU1_SESR
FEC_COR_1BIT_CNT
ODU1_PM_SES
OTU1_UAS
FEC_COR_BYTE_CNT
ODU1_PM_SESR
OTU2_BBE
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_UAS
OTU2_BBER
GPON_DF_BIP_CNT
ODU2_PM_BBE
OTU2_BIAES
LSBIASCUR
ODU2_PM_BBER
OTU2_ES
LSBIASMAX
ODU2_PM_ES
OTU2_FEBBE
LSBIASMIN
ODU2_PM_FEBBE
OTU2_FEBBER
LSCLCCUR
ODU2_PM_FEBBER
OTU2_FEES
LSCLCMAX
ODU2_PM_FEES
OTU2_FESES
LSCLCMIN
ODU2_PM_FESES
OTU2_FESESR
LSIOPCUR
ODU2_PM_FESESR
OTU2_FEUAS
LSIOPMAX
ODU2_PM_FEUAS
OTU2_IAES

Issue 04 (2010-10-20)

Transport Platform
LSIOPMIN
ODU2_PM_SES
OTU2_SES
LSOOPCUR
ODU2_PM_SESR
OTU2_SESR
LSOOPMAX
ODU2_PM_UAS
OTU2_UAS
LSOOPMIN
OTU1_BBE
RSBBE
LSTMPCUR
OTU1_BBER
RSCSES
LSTMPMAX
OTU1_BIAES
RSES
LSTMPMIN
OTU1_ES
RSSES
ODU1_PM_BBE
OTU1_FEBBE
RSUAS
4.2.9 LQPU Board Performance Event List
Issue 04 (2010-10-20)
ENVTMPCUR
ODU1_PM_BBER
OTU1_FEES
ENVTMPMAX
ODU1_PM_ES
OTU1_FESES
ENVTMPMIN
ODU1_PM_FEBBE
OTU1_FESESR
FEC_AFT_COR_ER
ODU1_PM_FEBBER
OTU1_FEUAS
FEC_AFT_COR_ERAVR
ODU1_PM_FEES
OTU1_IAES
FEC_BEF_COR_ER
ODU1_PM_FESES
OTU1_SES
FEC_BEF_COR_ERAVR
ODU1_PM_FESESR
OTU1_SESR
FEC_COR_0BIT_CNT
ODU1_PM_FEUAS
OTU1_UAS
FEC_COR_1BIT_CNT
ODU1_PM_SES
OTU2_BBE
FEC_COR_BYTE_CNT
ODU1_PM_SESR
OTU2_BBER
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_UAS
OTU2_BIAES
GPON_UF_BIP_CNT
ODU2_PM_BBE
OTU2_ES
GPON_DF_BIP_CNT
ODU2_PM_BBER
OTU2_FEBBE
LSBIASCUR
ODU2_PM_ES
OTU2_FEBBER
LSBIASMAX
ODU2_PM_FEBBE
OTU2_FEES
LSBIASMIN
ODU2_PM_FEBBER
OTU2_FESES
LSCLCCUR
ODU2_PM_FEES
OTU2_FESESR
LSCLCMAX
ODU2_PM_FESES
OTU2_FEUAS
LSCLCMIN
ODU2_PM_FESESR
OTU2_IAES

4-21

Transport Platform
LSIOPCUR
ODU2_PM_FEUAS
OTU2_SES
LSIOPMAX
ODU2_PM_SES
OTU2_SESR
LSIOPMIN
ODU2_PM_SESR
OTU2_UAS
LSOOPCUR
ODU2_PM_UAS
RSBBE
LSOOPMAX
OTU1_BBE
RSCSES
LSOOPMIN
OTU1_BBER
RSES
LSTMPCUR
OTU1_BIAES
RSSES
LSTMPMAX
OTU1_ES
RSUAS
LSTMPMIN
OTU1_FEBBE
ODU1_PM_BBE
OTU1_FEBBER
4.2.10 LSPL Board Performance Event List
4-22
ENVTMPCUR
LSIOPMAX
ODU1_PM_SESR
ENVTMPMAX
LSIOPMIN
ODU1_PM_UAS
ENVTMPMIN
LSOOPCUR
OTU1_BBE
FEC_AFT_COR_ER
LSOOPMAX
OTU1_BBER
FEC_AFT_COR_ERAVR
LSOOPMIN
OTU1_BIAES
FEC_BEF_COR_ER
LSTMPCUR
OTU1_ES
FEC_BEF_COR_ERAVR
LSTMPMAX
OTU1_FEBBE
FEC_COR_0BIT_CNT
LSTMPMIN
OTU1_FEBBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
OTU1_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
OTU1_FESES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_ES
OTU1_FESESR
LSBIASCUR
ODU1_PM_FEBBE
OTU1_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
OTU1_IAES
LSBIASMIN
ODU1_PM_FEES
OTU1_SES
LSCLCCUR
ODU1_PM_FESES
OTU1_SESR
LSCLCMAX
ODU1_PM_FESESR
OTU1_UAS
LSCLCMIN
ODU1_PM_FEUAS

Issue 04 (2010-10-20)

Transport Platform
LSIOPCUR
ODU1_PM_SES
4.2.11 LSPR Board Performance Event List

ENVTMPCUR
ENVTMPMAX
ENVTMPMIN
LSBIASCUR
LSBIASMAX
LSBIASMIN
LSIOPCUR
LSIOPMAX
LSIOPMIN
LSOOPCUR
LSOOPMAX
LSOOPMIN
LSCLCCUR
LSCLCMAX
LSCLCMIN
LSTMPCUR
LSTMPMAX
LSTMPMIN
4.2.12 LSPU Board Performance Event List
Issue 04 (2010-10-20)
ENVTMPCUR
LSIOPMAX
ODU1_PM_SESR
ENVTMPMAX
LSIOPMIN
ODU1_PM_UAS
ENVTMPMIN
LSOOPCUR
OTU1_BBE
FEC_AFT_COR_ER
LSOOPMAX
OTU1_BBER
FEC_AFT_COR_ERAVR
LSOOPMIN
OTU1_BIAES
FEC_BEF_COR_ER
LSTMPCUR
OTU1_ES
FEC_BEF_COR_ERAVR
LSTMPMAX
OTU1_FEBBE
FEC_COR_0BIT_CNT
LSTMPMIN
OTU1_FEBBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
OTU1_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
OTU1_FESES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_ES
OTU1_FESESR
LSBIASCUR
ODU1_PM_FEBBE
OTU1_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
OTU1_IAES
LSBIASMIN
ODU1_PM_FEES
OTU1_SES
LSCLCCUR
ODU1_PM_FESES
OTU1_SESR
LSCLCMAX
ODU1_PM_FESESR
OTU1_UAS
LSCLCMIN
ODU1_PM_FEUAS

4-23

Transport Platform
LSIOPCUR
ODU1_PM_SES
4.2.13 LSX Board Performance Event List

ENVTMPCUR
LSIOPMIN
OTU2_BBE
ENVTMPMAX
LSOOPCUR
OTU2_BBER
ENVTMPMIN
LSOOPMAX
OTU2_BIAES
FEC_AFT_COR_ER
LSOOPMIN
OTU2_ES
FEC_AFT_COR_ERAVR
LSTMPCUR
OTU2_FEBBE
FEC_BEF_COR_ER
LSTMPMAX
OTU2_FEBBER
FEC_BEF_COR_ERAVR
LSTMPMIN
OTU2_FEES
FEC_COR_0BIT_CNT
ODU2_PM_BBE
OTU2_FESES
FEC_COR_1BIT_CNT
ODU2_PM_BBER
OTU2_FESESR
FEC_COR_BYTE_CNT
ODU2_PM_ES
OTU2_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU2_PM_FEBBE
OTU2_IAES
LSBIASCUR
ODU2_PM_FEBBER
OTU2_SES
LSBIASMAX
ODU2_PM_FEES
OTU2_SESR
LSBIASMIN
ODU2_PM_FESES
OTU2_UAS
LSCLCCUR
ODU2_PM_FESESR
RSBBE
LSCLCMAX
ODU2_PM_FEUAS
RSCSES
LSCLCMIN
ODU2_PM_SES
RSES
LSIOPCUR
ODU2_PM_SESR
RSSES
LSIOPMAX
ODU2_PM_UAS
RSUAS
4.2.14 LWX2 Board Performance Event List
4-24
ENVTMPCUR
ENVTMPMAX
ENVTMPMIN
LSBIASCUR
LSBIASMAX
LSBIASMIN
LSCLCCUR
LSCLCMAX
LSCLCMIN
LSIOPCUR
LSIOPMAX
LSIOPMIN

Issue 04 (2010-10-20)

Transport Platform
LSOOPCUR
LSOOPMAX
LSOOPMIN
LSTMPCUR
LSTMPMAX
LSTMPMIN
4.2.15 OLP Board Performance Event List

ENVTMPCUR
ENVTMPMAX
ENVTMPMIN
LSIOPCUR
LSIOPMAX
LSIOPMIN
SUMIOPCUR
SUMIOPMAX
SUMIOPMIN
4.2.16 OPU Board Performance Event List

CCVCUR
CCVMAX
CCVMIN
ENVTMPCUR
ENVTMPMAX
ENVTMPMIN
PUMPTMPCUR
PUMPTMPMAX
PUMPTMPMIN
SUMIOPCUR
SUMIOPMAX
SUMIOPMIN
SUMOOPCUR
SUMOOPMAX
SUMOOPMIN
WCVCUR
WCVMAX
WCVMIN
4.2.17 TSP Board Performance Event List
Issue 04 (2010-10-20)
AUPJCHIGH
LPFESES
MSBBE
AUPJCLOW
LPUAS
MSCSES
ENVTMPCUR
LPCSES
MSES
ENVTMPMAX
LPFECSES
MSFEBBE
ENVTMPMIN
LSBIASCUR
MSFECSES
HPBBE
LSBIASMAX
MSFEES
HPCSES
LSBIASMIN
MSFESES
HPES
LSCLCCUR
MSSES
HPFEBBE
LSCLCMAX
MSUAS
HPFECSES
LSCLCMIN
RSBBE
HPFEES
LSIOPCUR
RSCSES

4-25

Transport Platform
4-26
HPFESES
LSIOPMAX
RSES
HPSES
LSIOPMIN
RSOFS
HPUAS
LSOOPCUR
RSOOF
LPBBE
LSOOPMAX
RSSES
LPES
LSOOPMIN
RSUAS
LPSES
LSTMPCUR
TUPJCHIGH
LPFEBBE
LSTMPMAX
TUPJCLOW
LPFEES
LSTMPMIN

Issue 04 (2010-10-20)

Transport Platform
5 Performance Event Processing
Performance Event Processing
About This Chapter

The performance event is an important parameter to evaluate the working performance of
equipment. Being acquainted with the generation principle, related boards and related alarms
helps you discover hidden trouble in routine maintenance and locate faults in troubleshooting.
If a performance event exceeds the threshold, the related alarms are generated. Therefore, upon
any performance event, check any related alarms and handle the event accordingly.
5.1 AUPJCHIGH
5.2 AUPJCLOW
5.3 CCV
5.4 ENVTMP
5.5 FEC_AFT_COR_ER
5.6 FEC_AFT_COR_ERAVR
5.7 FEC_BEF_COR_ER
5.8 FEC_BEF_COR_ERAVR
5.9 FEC_COR_0BIT_CNT
5.11 FEC_COR_BYTE_CNT
5.12 FEC_UNCOR_BLOCK_CNT
5.13 GPON_DF_BIP_CNT
5.14 GPON_UF_BIP_CNT
5.15 HPBBE
5.16 HPCSES
5.17 HPES
Issue 04 (2010-10-20)

5-1

Transport Platform
5.18 HPFEBBE
5.19 HPFECSES
5.20 HPFEES
5.21 HPFESES
5.22 HPSES
5.23 HPUAS
5.24 LSBIAS
5.25 LSCLC
5.26 LSIOP
5.27 LSOOP
5.28 LSTMP
5.29 MSBBE
5.30 MSCSES
5.31 MSES
5.32 MSFEBBE
5.33 MSFECSES
5.34 MSFEES
5.35 MSFESES
5.36 MSSES
5.37 MSUAS
5.38 ODUk_PM_BBE
5.39 ODUk_PM_BBER
5.40 ODUk_PM_ES
5.41 ODUk_PM_FEBBE
5.42 ODUk_PM_FEBBER
5.43 ODUk_PM_FEES
5.44 ODUk_PM_FESES
5.45 ODUk_PM_FESESR
5.46 ODUk_PM_FEUAS
5.47 ODUk_PM_SES
5.48 ODUk_PM_SESR
5.49 ODUk_PM_UAS
5.50 OTUk_BBE
5-2

Issue 04 (2010-10-20)

Transport Platform
5.51 OTUk_BBER
5.52 OTUk_ES
5.53 OTUk_FEBBE
5.54 OTUk_FEBBER
5.55 OTUk_FEES
5.56 OTUk_FESES
5.57 OTUk_FESESR
5.58 OTUk_FEUAS
5.59 OTUk_SES
5.60 OTUk_SESR
5.61 OTUk_UAS
5.62 OTUk_IAES
5.63 OTUk_BIAES
5.64 PUMPTMP
5.65 RSBBE
5.66 RSCSES
5.67 RSES
5.68 RSOFS
5.69 RSOOF
5.70 RSSES
5.71 RSUAS
5.72 SUMIOP
5.73 SUMOOP
5.74 TUPJCHIGH
5.75 TUPJCLOW
5.76 WCV
Issue 04 (2010-10-20)

5-3

Transport Platform
5.1 AUPJCHIGH
Description
Administrative unit pointer justification count high
It indicates the positive justification count of the AU pointer when the rate of VC frame is
adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number
of pointer justification counts, however, cause bit errors in the services. In this case, determine
the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the
signal transmission quality.
Generation Principle and Possible Causes

The root cause of the AU pointer justification is that the clocks of NEs on the SDH network are
not synchronous. The possible causes of the event are as follows:
l
The performance of the external clock is degraded.
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.
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the 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
5-4

Issue 04 (2010-10-20)

Transport Platform
Related Information
None
5.2 AUPJCLOW
Description
Administrative unit pointer justification count low
It indicates the negative justification count of the AU pointer when the rate of VC frame is
adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number
of pointer justification counts, however, cause bit errors in the services. In this case, determine
the cause and solve the problem in a timely manner to avoid any alarm, and thus to ensure the
signal transmission quality.

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
not synchronous. The possible causes are as follows:
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.
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the 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
Issue 04 (2010-10-20)

5-5

Transport Platform
the AU pointer justification event occurs continuously, contact the technical support engineers
of Huawei.
----End
Related Information
None
5.3 CCV
Description
Pump Laser Cooling Current
It includes:
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
Correlation
PUMP_COOL_EXC
It is generated when the cooling current of the

laser exceeds the normal range.
Procedure
Step 1 If the PUMP_COOL_EXC alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
5-6

Issue 04 (2010-10-20)

Transport Platform
5.4 ENVTMP
Description
Board environmental temperature
It includes:
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
None
Procedure
Step 1 None.
----End
Related Information
None
5.5 FEC_AFT_COR_ER
Description
After FEC correct errored rate
Impact on System
After the error correction, in normal cases, the value should be 0. If the value is not 0, it indicates
that the bit errors in the services bring impact on the transmission quality. In this case, determine
the cause in a timely manner.
Issue 04 (2010-10-20)

5-7

Transport Platform

This performance event shows that there are still errors at the receiver after FEC. This
performance event is caused by low OSNR at the receiving end. In normal cases, it should be
0.
In this case, there must be FEC_BEF_COR_ER accompanied and you should check the alarm
in a timely manner.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Signal degraded before FEC alarm. Signals sent from sides of the
opposite-end OTUs have the FEC function. As a result, before
performing signal FEC in the receive direction of side of the localend 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
5.6 FEC_AFT_COR_ERAVR
Description
After FEC Correct Average Errored Rate in monitor period.
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that
the bit errors in the services bring impact on the transmission quality. In this case, determine the
cause in a timely manner.

This performance event shows there are still errors at the receiver after FEC. This performance
event is caused by low OSNR at the receiving end. Normally, it should be zero.
In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the optical
power to increase the OSNR.
5-8

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Procedure
----End
Related Information
None
5.7 FEC_BEF_COR_ER
Description
BER before FEC
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate
(BER) is low, the system operates normally. If the BER is high, determine the causes and solve
the problem in a timely manner to avoid any alarm, and thus to ensure the signal transmission
quality.

The cause for the BER before the FEC is that the receiver detects bit errors, which are caused
by dispersion, unstable performance of the optical interface, and/or excessively high attenuation.
Related Alarms
Issue 04 (2010-10-20)
Alarm Name
Correlation
BEFFEC_EXC

5-9

Transport Platform
Procedure
----End
Related Information
None
5.8 FEC_BEF_COR_ERAVR
Description
Before FEC Correct Average Errored Rate in monitor period.
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate
(BER) is low, the system operates normally. If the BER is high, determine the cause and solve
the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR
at the receiving end. Normally, it should be zero.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None
5-10

Issue 04 (2010-10-20)

Transport Platform
Description
Forward error correction - corrected 0 bit count
Impact on System
None

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

This performance event shows the number of 1bit corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Issue 04 (2010-10-20)

5-11

Transport Platform
Procedure
Step 1 None
----End
Related Information
None
5.11 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
5.12 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.
5-12

Issue 04 (2010-10-20)

Transport Platform

This performance event shows the number of received error frames that cannot be corrected by
FEC, and indicates that signals of low OSNR are beyond the correction capability of FEC.
Normally, the performance value should be 0.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Signal degraded before FEC alarm. Signals sent from side of the localend OTU, the local-end OTU counts the bit error rate. This alarm is
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None
5.13 GPON_DF_BIP_CNT
Description
GPON Downstream frame BIP error.
Impact on System
None

None
Related Alarms
Issue 04 (2010-10-20)
Alarm Name
Correlation
GPON_DS_LOF
GPON Downstream frame BIP error exceed

the threshold.

5-13

Transport Platform
Procedure
Step 1 Refer to the method of handling the GPON_DS_LOF.
----End
Related Information
None
5.14 GPON_UF_BIP_CNT
Description
GPON Upstream frame BIP error.
Impact on System
None

None
Related Alarms
Alarm Name
Correlation
GPON_US_LOF
GPON Upstream frame BIP error exceed the

threshold.
Procedure
Step 1 Refer to the method of handling the GPON_US_LOF.
----End
Related Information
None
5.15 HPBBE
Description
Higher order path background block error
5-14

Issue 04 (2010-10-20)

Transport Platform
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the
system is not affected. You need to, however, find out the causes and take proper measures in
time to avoid any alarm, which affects the quality of the signals transmitted in the higher order
path.

The HPBBEs are detected by means of detecting the B3 byte. The possible causes of the event
are as follows:
l
There is interference from the external environment.
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
Correlation
B3_SD
When the count of B3 bit errors in the alarm path exceeds the threshold of
the B3_SD but lower than the threshold of the B3_EXC, the alarm is
reported.
B3_EXC
the B3_EXC, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
The background block error means that one or more bit errors occur in the data block during
transmission.
5.16 HPCSES
Description
Higher order path consecutive severely errored second
Issue 04 (2010-10-20)

5-15

Transport Platform
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The 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
Related Alarms
Alarm Name
Correlation
B3_SD
When the count of B3 bit errors in the alarm path exceeds the
threshold of the B3_SD but lower than the threshold of the
B3_EXC, the alarm is reported.
B3_EXC
threshold of the B3_EXC, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm.
----End
Related Information
None
5.17 HPES
Description
Higher order path errored second
5-16

Issue 04 (2010-10-20)

Transport Platform
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible
causes of the event are as follows:
l
Related Alarms
Alarm Name
Correlation
B3_SD
B3_EXC
threshold, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm.
----End
Related Information
The errored second (ES) refers to the second in which one or more errored blocks are detected.
5.18 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
Issue 04 (2010-10-20)

5-17

Transport Platform
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
Related Alarms
Alarm Name
Correlation
HP_REI
If the board has detected that the value is 1-8 for bits 1-4 of the G1 byte
in the higher order path, the alarm is reported.
Procedure
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.
5.19 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
higher order path.
5-18

Issue 04 (2010-10-20)

Transport Platform

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
Related Alarms
Alarm Name
Correlation
HP_REI
If the board has detected that the value is 1-8 for bits 1-4 of the G1
byte in the higher order path, the alarm is reported.
Procedure
----End
Related Information
The severely errored second (SES) refers to the second in which more than 30% errored blocks
occur or at least one serious disturbance period (SDP) occurs.
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.
5.20 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
Issue 04 (2010-10-20)

5-19

Transport Platform
higher order path.

l
The cross-connection clock unit is faulty.
Related Alarms
Alarm Name
Correlation
HP_REI
Procedure
----End
Related Information
Remote Errored Second
The remote errored second refers to the errored second that is detected at the peer end.
5.21 HPFESES
Description
Higher order path far end severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarm is
higher order path.
5-20

Issue 04 (2010-10-20)

Transport Platform

l
The cross-connect unit is faulty.
Related Alarms
Alarm Name
Correlation
HP_REI
Procedure
----End
Related Information
The severely errored second (SES) refers to the second in which more than 30% errored blocks
occur or at least one serious disturbance period (SDP) occurs.
5.22 HPSES
Description
Higher order path severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

Issue 04 (2010-10-20)

5-21

Transport Platform
Related Alarms
Alarm Name
Correlation
B3_SD
B3_EXC
threshold, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
The severely errored second (SES) refers to the second in more than 30% errored blocks occur
or at least one serious disturbance period (SDP) occurs.
5.23 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
5-22

Issue 04 (2010-10-20)

Transport Platform
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
Related Alarms
Alarm Name
Correlation
B3_SD
the B3_SD but lower than the threshold of the B3_EXC, the alarm is
reported.
B3_EXC
When the count of B3 bit errors in the alarm path exceeds the threshold,
the alarm is reported.
AU_AIS
When the alarm is generated, the HPUAS value is increased.
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
5.24 LSBIAS
Description
Laser bias current
It includes:
l
Issue 04 (2010-10-20)
LSBIASMAX: stands for the maximum value during a period of time.

5-23

Transport Platform
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
Correlation
TD
It is generated when the working current of a

laser exceeds the threshold or a multiple of
the threshold.
LSR_WILL_DIE
It is generated when the working current of a

laser exceeds the threshold or a multiple of
the threshold.
Procedure
Step 1 If the TD alarm is generated, see the handling procedure of the alarm.
Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
5.25 LSCLC
Description
Laser cooling current
It includes:
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.
5-24

Issue 04 (2010-10-20)

Transport Platform

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
Correlation
LSR_COOL_ALM
It is generated when the laser cooling current

exceeds the pre-set threshold.
Procedure
Step 1 If the LSR_COOL_ALM alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
5.26 LSIOP
Description
Input optical power
It includes:
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
Issue 04 (2010-10-20)
Alarm Name
Correlation
IN_PWR_HIGH
It is generated when the optical power input by board is higher than

the upper threshold.

5-25

Transport Platform
Alarm Name
Correlation
IN_PWR_LOW
It is generated when the optical power input by board is lower than

the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
history performance value and the change in optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW alarm.
Step 3 If an alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
5.27 LSOOP
Description
Output optical power
It includes:
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.
5-26

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
OUT_PWR_HIGH
It is generated when the optical power output by a board is higher than

OUT_PWR_LOW
It is generated when the optical power output by a board is lower than

TF
It is generated when the optical power output by a board is 1 dB lower

than the lower threshold.
Procedure
history performance value and the change of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
history performance value and the change of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm.
Step 3 If an alarm is generated, see the Related Alarms.
----End
Related Information
None
5.28 LSTMP
Description
Laser temperature
It includes:
l
LSTMPMAX: stands for the maximum value during a period of time.
LSTMPMIN: stands for the minimum value during a period of time.
LSTMPCUR: stands for the current value.
Impact on System
None

Normally, the laser temperature is a stable value obtained by software through calculating the
result outputted by the temperature detecting circuit in the laser.
Issue 04 (2010-10-20)

5-27

Transport Platform
Related Alarms
Alarm Name
Correlation
TEM_HA
Laser temperature is excessively high. This alarm is generated when

the laser temperature is higher than the upper threshold of the laser
temperature.
TEM_LA
Laser temperature is excessively low. This alarm is generated when

the laser temperature is lower than the upper threshold of the laser
temperature.
Procedure
Step 1 If the TEM_HA or TEM_LA alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
5.29 MSBBE
Description
MS background block error
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.

The multiplex section errors are detected by checking the B2 byte. The background block error
means there are one or more data blocks containing error bits during transmission.
Related Alarms
5-28
Alarm Name
Correlation
B2_EXC
Multiplex section (B2) excessive errors alarm. The alarm is generated

when the B2 bit errors in the multiplex section exceeds the threshold.
B2_SD
Multiplex section (B2) signal degraded alarm. The alarm is generated

when the B2 bit errors in the multiplex section exceeds the signal
degrade (SD) threshold.
Issue 04 (2010-10-20)

Transport Platform
Alarm Name
Correlation
MS_AIS
Multiplex section alarm indication. The alarm is generated when the

opposite station transmits the MS_AIS signals or the receive part of
the local station is faulty.
MS_CROSSTR
Multiplex section performance exceeds the threshold. The alarm is

generated when the performance module reports the threshold
crossing of the performance events in the multiplex section.
R_LOF
Loss of frame on receiving line. This alarm is generated when the

frame alignment processing is out of frame (OOF) in consecutive 3ms.
Procedure
Step 1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
5.30 MSCSES
Description
MS consecutive severely errored second
Impact on System
There are a large number of bit errors in the services. Determine the cause and solve the problem
in a timely manner because the bit errors severely affect the signal transmission quality. In
addition, the B2_EXC and B2_SD alarms may be generated.

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
Issue 04 (2010-10-20)
Alarm Name
Correlation
B2_EXC

5-29

Transport Platform
Alarm Name
Correlation
B2_SD

MS_AIS

MS_CROSSTR

R_LOF

Procedure
----End
Related Information
None
5.31 MSES
Description
MS errored second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, determine
the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal
transmission quality.

The multiplex section errors are detected by checking the B2 byte. The MS errored second means
there are more than one error block transmitted in this second.
Related Alarms
5-30
Alarm Name
Correlation
B2_EXC

Issue 04 (2010-10-20)

Transport Platform
Alarm Name
Correlation
B2_SD

MS_AIS

MS_CROSSTR

R_LOF

frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
----End
Related Information
None
5.32 MSFEBBE
Description
MS far end background block error
Impact on System
If bit errors are generated in the services on a far-end NE but no related alarm is reported on the
opposite NE, there is no impact on the system. You, however, need to determine the cause and
quality.

The multiplex section errors are detected by checking the B2 byte. The background block error
means there are one or more data blocks containing error bit during transmission. And the far
end background block error refers to the background block error detected at the opposite end.
Issue 04 (2010-10-20)

5-31

Transport Platform
Related Alarms
Alarm Name
Correlation
MS_RDI
Multiplex section remote defect indication alarm. The alarm is

generated at the local station if the opposite station back transmits the
information through overhead when the -side receive part of the
opposite station is faulty.
MS_REI
Multiplex section remote error indication. The alarm is generated

when the remote end detects the bit error block.
Procedure
Step 1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
5.33 MSFECSES
Description
MS far end consecutive severely errored second
Impact on System
quality.

severely errored second means the severely errored second appears consecutively, and it is
accompanied by the B2_EXE alarm. It might result in service interruption. The far end
consecutive severely errored second refers to the consecutive severely errored second detected
at the opposite end.
5-32

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
MS_RDI

MS_REI

Procedure
----End
Related Information
None
5.34 MSFEES
Description
MS far end errored second
Impact on System
quality.

The multiplex section errors are detected by checking the B2 byte. An errored second contains
more than one error block. And the far end errored second refers to the errored second detected
Related Alarms
Issue 04 (2010-10-20)
Alarm Name
Correlation
MS_RDI

5-33

Transport Platform
Alarm Name
Correlation
MS_REI

Procedure
----End
Related Information
None
5.35 MSFESES
Description
MS far end severely errored second
Impact on System
quality.

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
5-34
Alarm Name
Correlation
MS_RDI

MS_REI


Issue 04 (2010-10-20)

Transport Platform
Procedure
----End
Related Information
None
5.36 MSSES
Description
MS severely errored second
Impact on System
quality.

second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
Issue 04 (2010-10-20)
Alarm Name
Correlation
B2_EXC

B2_SD

MS_AIS

MS_CROSSTR

R_LOF


5-35

Transport Platform
Procedure
----End
Related Information
None
5.37 MSUAS
Description
MS unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds
last for more than 10 seconds, the unavailable second starts from the beginning of the 11th
second, and the former 10 severely errored seconds are counted as unavailable. If the severely
errored second disappears for more than 10 seconds, the available time starts from the beginning
of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
5-36
Alarm Name
Correlation
B2_EXC

B2_SD

MS_AIS

R_LOS
Loss of signal on receiving line. This alarm is generated when the

receive side receives no signals.
MS_RDI

Issue 04 (2010-10-20)

Transport Platform
Alarm Name
Correlation
MS_REI

Procedure
----End
Related Information
None
5.38 ODUk_PM_BBE
Description
ODU PM section background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause
and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal

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
Issue 04 (2010-10-20)
Alarm Name
Correlation
ODUk_PM_EXC
Bit interleaved parity (BIP) in the PM section of the ODU layer

exceeds the upper threshold. The alarm is generated when the number
of BIP8 bit errors of the PM section on the optical channel data unit
layer exceeds the upper threshold.
ODUk_PM_DEG
Bit interleaved parity signal in the PM section of the ODU layer

degrades. The alarm is generated when the number of BIP8 bit errors
of the PM section of the ODU layer exceeds the degrade threshold.

5-37

Transport Platform
Procedure
Step 1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
5.39 ODUk_PM_BBER
Description
ODU PM section ratio of background block error
Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is
large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to
ensure the signal transmission quality.

ODU PM section background block errors are detected by checking the received parity bits. The
background block error refers to a data block where at least one bit error is generated during the
transmission. Background block error ratio of the ODU PM section refers to the ratio of the
number of background block errors of the ODU PM section to the number of all blocks minus
the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second].
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODU layer PM section BIP exceeds the upper threshold. The alarm
is generated when the number of BIP8 bit errors of the PM section on
the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG

of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
5-38

Issue 04 (2010-10-20)

Transport Platform
Related Information
None
5.40 ODUk_PM_ES
Description
ODU PM section errored second
Impact on System
quality.

ODU PM section errors are detected by checking the received parity bit. An errored second
contains more than one error block.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODUk_PM_DEG

of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
5.41 ODUk_PM_FEBBE
Description
ODU PM section far end background block error
Issue 04 (2010-10-20)

5-39

Transport Platform
Impact on System
quality.

ODU PM section errors are detected by checking the received parity bit. The background block
error means there are one or more data blocks containing error bit during transmission. And the
far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
ODU PM section backward defect indication.
Procedure
Step 1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
5.42 ODUk_PM_FEBBER
Description
ODU PM section ratio of far end background block error
Impact on System

ODU PM section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the ODU PM section refers to the ratio of the
number of background block errors of the ODU PM section to the number of all blocks minus
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.
5-40

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
5.43 ODUk_PM_FEES
Description
ODU PM section far end errored second
Impact on System
quality.

ODU PM section error is detected by checking the received parity bit. An errored second contains
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Issue 04 (2010-10-20)

5-41

Transport Platform
Related Information
None
5.44 ODUk_PM_FESES
Description
ODU PM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure
the signal transmission quality.

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
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
5.45 ODUk_PM_FESESR
Description
ODU PM section ratio of far end severely errored second
5-42

Issue 04 (2010-10-20)

Transport Platform
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
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
5.46 ODUk_PM_FEUAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services on a far-end NE. The services may be affected.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from
the beginning of the 11th second, and the former 10 severely errored seconds are counted as
unavailable. If the severely errored second disappears for more than 10 seconds, the available
time starts from the beginning of the 11th second, and the former 10 seconds are counted as
available. And the far end unavailable second refers to the unavailable second detected at the
opposite end.
Issue 04 (2010-10-20)

5-43

Transport Platform
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
5.47 ODUk_PM_SES
Description
ODU PM section severely errored second
Impact on System
There are bit errors in services. Determine the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.

ODU PM Section error is detected by checking the received parity bit. During a severely errored
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
5-44
Alarm Name
Correlation
ODUk_PM_EXC
is generated when the number of BIP8 bit errors of the PM section of
ODUk_PM_DEG
Optical channel data unit layer, path monitoring section bit

interleaved parity signal degraded. The alarm is generated when the
number of BIP8 bit errors of the PM section of the optical channel
data unit layer exceeds the degraded threshold.

Issue 04 (2010-10-20)

Transport Platform
Procedure
----End
Related Information
None
5.48 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
Impact on System

ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODUk_PM_DEG

number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
Issue 04 (2010-10-20)

5-45

Transport Platform
5.49 ODUk_PM_UAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

available.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODUk_PM_DEG

number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
5.50 OTUk_BBE
Description
OTU background block error
5-46

Issue 04 (2010-10-20)

Transport Platform
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
Correlation
OTUk_EXC
OTU SM section bit interleaved parity exceeds threshold. The alarm

is generated when the number of BIP8 bit errors of the SM section on
the optical channel data unit layer exceeds the threshold.
OTUk_DEG
OTU SM section bit interleaved parity deterioration. The alarm is

generated when the number of BIP8 bit errors of the SM section in
the optical channel data unit layer exceeds the degraded threshold.
Procedure
Step 1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
5.51 OTUk_BBER
Description
OTU ratio of background block error
Impact on System

OTU section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the OTU section refers to the ratio of the number
of background block errors of the OTU section to the number of all blocks minus the number
Issue 04 (2010-10-20)

5-47

Transport Platform
of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks
per second].
Related Alarms
Alarm Name
Correlation
OTUk_EXC

is generated when the number of BIP8 bit errors of the SM section in
OTUk_DEG

generated when the number of BIP8 bit errors of the SM section on
Procedure
----End
Related Information
None
5.52 OTUk_ES
Description
OTU errored second
Impact on System
quality.

OTU error is detected by checking the received parity bit. An errored second contains more than
one error block.
Related Alarms
5-48
Alarm Name
Correlation
OTUk_EXC

Issue 04 (2010-10-20)

Transport Platform
Alarm Name
Correlation
OTUk_DEG

Procedure
----End
Related Information
None
5.53 OTUk_FEBBE
Description
OTU SM section far end background block error
Impact on System
quality.

OTU SM section error is detected by checking the received parity bit. The background block
error means there are one or more data blocks containing error bit during transmission. And the
far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name
Correlation
OTUk_BDI
OTU SM section backward defect indication.
Procedure
Step 1 Refer to the method of handling the OTUk_BDI.
----End
Issue 04 (2010-10-20)

5-49

Transport Platform
Related Information
None
5.54 OTUk_FEBBER
Description
OTU SM section ratio of far end background block error
Impact on System

OTU SM section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the OTU SM section refers to the ratio of the
number of background block errors of the OTU SM section to the number of all blocks minus
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
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
5.55 OTUk_FEES
Description
OTU SM section far end errored second
5-50

Issue 04 (2010-10-20)

Transport Platform
Impact on System

OTU SM section error is detected by checking the received parity bit. An errored second contains
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
5.56 OTUk_FESES
Description
OTU SM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Determine the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.

OTU SM Section error is detected by checking the received parity bit. During a severely errored
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.
Issue 04 (2010-10-20)

5-51

Transport Platform
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
5.57 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

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
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
5-52

Issue 04 (2010-10-20)

Transport Platform
Related Information
None
5.58 OTUk_FEUAS
Description
OTU SM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

available. And the far end unavailable second refers to the unavailable second detected at the
opposite end.
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
5.59 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
Issue 04 (2010-10-20)

5-53

Transport Platform

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

OTUk_DEG

Procedure
----End
Related Information
None
5.60 OTUk_SESR
Description
OTU ratio of severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem

there is at least one defect or 30% of data blocks are error blocks. The consecutive severely
errored second means the severely errored second appears consecutively, it might result in the
interruption of the service that shares a fiber link with the supervisory channel. Severely errored
second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available
time.
5-54

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
OTUk_EXC

OTUk_DEG

Procedure
----End
Related Information
None
5.61 OTUk_UAS
Description
OTU unavailable second
Impact on System

available.
Related Alarms
Issue 04 (2010-10-20)
Alarm Name
Correlation
OTUk_EXC

5-55

Transport Platform
Alarm Name
Correlation
OTUk_DEG

Procedure
----End
Related Information
None
5.62 OTUk_IAES
Description
OTUk SM 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_LOF alarm at the upstream station.
Related Alarms
Alarm Name
Correlation
OTUk_LOF
OTUk frame loss. The upstream station detects the LOF alarm and
then inserts IAE. The local station reports OTUk_IAES.
Procedure
Step 1 Refer to the method of handling the OTUk_LOF.
----End
Related Information
None
5-56

Issue 04 (2010-10-20)

Transport Platform
5.63 OTUk_BIAES
Description
OTUk SM 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.

OTUk SM 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
5.64 PUMPTMP
Description
Pump Laser Temperature
It includes:
l
PUMPTMPMAX: denotes the maximum value during a period of time.
PUMPTMPMIN: denotes the minimum value during a period of time.
PUMPTMPCUR: denotes the current value.
Issue 04 (2010-10-20)

5-57

Transport Platform
Impact on System
Services on the board may be affected when the pump laser temperature of the board exceeds
the threshold.

To obtain this performance event, perform a check by the check circuit. Then calculate the result
with software for conversion.
Related Alarms
Alarm Name
Correlation
PUM_TEM_ALM
Working temperature of the pump laser exceeds the threshold. This

alarm is generated when the pump laser operating temperature of the
optical amplifier unit exceeds the threshold.
Procedure
Step 1 Refer to the method of handling the PUM_TEM_ALM.
----End
Related Information
None
5.65 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.
5-58

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
B1_EXC
Regenerator section (B1) excessive errors.

The alarm is generated when the received
signals in SDH frame degrades and the B1 bit
errors in the multiplex section exceeds the
threshold.
B1_SD

signals in SDH frame degrades and the B1 bit
errors in the multiplex section exceeds the
signal degrade (SD) threshold.
Procedure
Step 1 Refer to the method of handling the B1_EXC and B1_SD.
----End
Related Information
None
5.66 RSCSES
Description
RS consecutive severely errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. Consecutive severely
errored seconds (CSES) mean the severely errored seconds appear consecutively, and the CSES
is generally accompanied by the B1_EXC alarm. It might result in service interruption.
Issue 04 (2010-10-20)

5-59

Transport Platform
Related Alarms
Alarm Name
Correlation
B1_EXC

signals in SDH frame degrade and the B1 bit
errors in the multiplex section exceed the
threshold.
B1_SD

Procedure
----End
Related Information
None
5.67 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.
5-60

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
B1_EXC

threshold.
B1_SD

Procedure
----End
Related Information
None
5.68 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.
Issue 04 (2010-10-20)

5-61

Transport Platform
Related Alarms
Alarm Name
Correlation
R_LOF
Loss of frame on receiving line. This alarm is

generated when the frame alignment
processing is in the OOF state in consecutive
3 ms.
Procedure
Step 1 Check whether the fibers are damaged and whether the connectors are properly installed. Clean
the fiber connectors.
Step 2 Check whether the input optical power of the input interface of the board is within the normal
range by using an optical power meter. For the optical power specifications of a certain board,
see the Product Description. If the power is not within the normal range, add proper attenuation
by adding a fix attenuator or a variable optical attenuator (VOA).
----End
Related Information
None
5.69 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:
5-62
The performance of the optical fiber is degraded.

Issue 04 (2010-10-20)

Transport Platform
Related Alarms
Alarm Name
Correlation
R_LOF
When the R_OOF alarm lasts for 3 ms, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the R_LOF.
----End
Related Information
None
5.70 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 04 (2010-10-20)
Alarm Name
Correlation
B1_EXC

threshold.
B1_SD


5-63

Transport Platform
Procedure
----End
Related Information
None
5.71 RSUAS
Description
RS unavailable second
Impact on System

The regenerator section errors are detected by checking the B1 byte. If the severely errored
seconds last for more than 10 seconds, the unavailable second starts from the beginning of the
11th second, and the former 10 severely errored seconds are counted as unavailable. If the
severely errored second disappears for more than 10 seconds, the available time starts from the
beginning of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name
Correlation
B1_EXC

threshold.
B1_SD

Procedure
----End
5-64

Issue 04 (2010-10-20)

Transport Platform
Related Information
None
5.72 SUMIOP
Description
Total input optical power
It includes:
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
Correlation
IN_PWR_HIGH
It is generated when the optical power input by board is higher than

IN_PWR_LOW
It is generated when the optical power input by board is lower than

Procedure
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH alarm.
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW alarm.
Issue 04 (2010-10-20)

5-65

Transport Platform

----End
Related Information
The board types that are supported by the input power alarm are different from the board types
that are supported by the total input power alarm.
5.73 SUMOOP
Description
Total output optical power
It includes:
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.
Related Alarms
5-66
Alarm Name
Correlation
OUT_PWR_HIGH
It is generated when the optical power output by board is higher than

OUT_PWR_LOW
It is generated when the optical power output by board is lower than


Issue 04 (2010-10-20)

Transport Platform
Procedure
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm.
----End
Related Information
The board types that are supported by the output power alarm are different from the board types
that are supported by the total output power alarm.
5.74 TUPJCHIGH
Performance Event Meaning
The TUPJCHIGH is a performance event indicating the count of positive TU pointer
justifications.

A small quantity of pointer justification does not affect the services, whereas a large amount of
pointer justification causes bit errors in the services. In this case, detect the causes and
troubleshoot the problem in time. Otherwise, alarms will be generated and the signal
transmission quality will be affected.
Possible Causes
External causes:
l
The fibers are incorrectly connected, resulting in the mutual clock tracing of the two NEs.
If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l
The configuration of the clock source is incorrect. There are two clock sources in one
network.
The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l
The line board is faulty. As a result, the clock is of a bad quality.
The tributary board is faulty. As a result, the clock is of poor quality.
The timing unit is faulty, providing bad timing source or being unable to lock the traced
timing source.
Issue 04 (2010-10-20)

5-67

Transport Platform
Relevant Alarms
None
Procedure
Step 1 Check whether the fibers are connected reversely. If yes, connect them correctly. On a path
protection (PP) ring, services are normal even though the fibers are connected reversely. In other
networking modes, reverse connection of fibers interrupts services.
Step 2 If the NE traces the external clock, check the quality of the external clock. If the external clock
is of poor quality, modify the tracing configuration of the external clock.
Step 3 Check whether the configuration is correct. If not, modify the incorrect configuration and issue
it again.
Step 4 Analyze the pointer justification performance events, and locate the faulty point by changing
the position of the clock source and clock tracing direction.
----End
Reference
None.
5.75 TUPJCLOW
Performance Event Meaning
The TUPJCLOW is a performance event indicating the count of negative TU pointer
justifications.

A small quantity of pointer justification does not affect the services, whereas a large amount of
pointer justification causes bit errors in the services. In this case, detect the causes and
troubleshoot the problem in time. Otherwise, alarms will be generated and the signal
transmission quality will be affected.
Possible Causes
External causes:
l
The fibers are incorrectly connected, resulting in the mutual clock tracing of the two NEs.
If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l
The configuration of the clock source is incorrect. There are two clock sources in one
network.
The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
5-68

Issue 04 (2010-10-20)

Transport Platform
The line board is faulty. As a result, the clock is of a bad quality.
The tributary board is faulty. As a result, the clock is of a bad quality.
The timing unit is faulty, providing bad timing source or being unable to lock the traced
timing source.
Relevant Alarms
None
Procedure
Step 1 Refer to the TUPJCHIGH.
----End
Reference
None.
5.76 WCV
Description
Pump laser working current.
It includes:
l
WCVMAX: stands for the maximum value during a period of time (in 1mA).
WCVMIN: stands for the minimum value during a period of time (in 1mA).
WCVCUR: stands for the current value (in 1mA).
Impact on System
When the pump laser works normally, there is no impact on the services. If an alarm is generated,
determine the cause.

WCV indicates the pump laser driver current of an optical amplifier board. The optical amplifier
board amplifies the input signal using the pump laser driven by pump laser working current.
Related Alarms
Issue 04 (2010-10-20)
Alarm Name
Correlation
PUM_BCM_ALM
The board reports this alarm when the detected pump laser driver
current is higher than the threshold due to laser exceptions caused by
laser aging, or over-high/low ambient temperature.
LSR_WILL_DIE
The board reports this alarm when the pump laser driver current is
higher than the termination threshold due to laser aging.

5-69

Transport Platform
Alarm Name
Correlation
TD
Transmitter degrade alarm. The alarm is generated when the bias

current of the laser exceeds the degrade threshold.
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the handling procedure of the alarm.
Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
Step 3 If the TD alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
5-70

Issue 04 (2010-10-20)

Transport Platform
A Glossary
Glossary
A
Auto negotiation
The negotiation mode that is set on the communication equipment. When the auto
negotiation mode is enabled, the equipment sets its working mode and rate through
negotiation based on the mode and rate of the opposite equipment.
B
Bandwidth
Information-carrying capacity of a communication channel. Analog bandwidth is the

range of signal frequencies that can be transmitted by a communication channel or
network.
Bit Error Rate
The ratio of the errored bit count to the transmitted bit count in a certain period of time.
In the digital communication system, bit error rate is the ratio of the errored bit count to
the transmitted bit count in a typical period of time.
Broadcast
The act of sending a frame addressed to all stations on the network.
C
Channel
The trail on the channel layer.
Client Server
A terminal device (computer or workstation) that sends instructions to the server and
displays the results through the user interface.
Clock tracing
The method to keep the time on each node being synchronized with a clock source in a
network.
Concatenate
A combination process. The process combines multiple virtual containers (VCs). Then,
the capacity of the combined VCs can used as the capacity of a single VC and the bit
sequence is complete.
Connection
A "transport entity" which consists of an associated pair of "unidirectional connections"

capable of simultaneously transferring information in opposite directions between their
respective inputs and outputs.
Issue 04 (2010-10-20)

A-1
A Glossary

Transport Platform
D
DCM
Dispersion Compensation Module. A module, which contains dispersion compensation

fibers to compensate for the positive dispersion of transmitting fiber.
E
EDFA
An optical device that amplifies the optical signals. The device uses a short length of
optical fiber doped with the rare-earth element Erbium and the energey level jump of
Erbium ions activated by pump sources. When the amplifier passes the external light
source pump, it amplifies the optical signals in a specific wavelength range.
Ethernet
A data link level protocol comprising the OSI model's bottom two layers. It is a broadcast
networking technology that can use several different physical media, including twisted
pair cable and coaxial cable. Ethernet usually uses CSMA/CD. TCP/IP is commonly
used with Ethernet networks.
F
Fiber jumper
The fiber which is used to connect the subrack with the ODF, subrack or connect the
board interfaces.
Forward Error
Correction
A data encoding technology. It is a method to control errors in communication. In this

method, extra (redundant) bits are inserted into the data stream towards other equipment
to control errors. The equipment at the receive end can use these redundant bits to detect
errors and correct errors if possible.
Frame
A cyclic set of consecutive time slots in which the relative position of each time slot can
be identified.
Full duplex
Pertaining to both parties that can send and receive data at the same time on the
communication link.
G
Gain
The ratio between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
Grooming
A process that multiplexes multiple channels of low-rate signals into one or several
channels of required signals.
L
Label
A mark on a cable, a subrack, or a cabinet for identification.
Laser
The device that generates the directional light covering a narrow range of wavelengths.
Laser light is more coherent than ordinary light. Semiconductor diode lasers are the used
light source in fiber-optic system.
A-2

Issue 04 (2010-10-20)

Transport Platform
A Glossary
M
Main Topology
The default U2000 client interface, a basic component of the human-machine interactive
interface. The topology clearly shows the structure of the network, the alarms of different
NEs, subnets in the network, the communication status as well as the basic network
operation status. All topology management functions are accessed here.
Multiplexing
A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
O
Opposite station/
opposite station board
The opposite station is a service-specific concept. As shown in Figure A-1, if station A

is the local station, station C is the opposite station for service 1 and station B is the
opposite station for service 2. The opposite station board is specific to the transmitting
or receiving of a service. For service 2, the board opposite to OTU5 is OTU2. For service
3, the board opposite to OTU6 is OTU4. Similarly, for service 1, the board opposite
to OTU1 is OTU3.
Figure A-1 Service flow
1
OTU1
2
Station B
Station A
OTU2
Clinet WDM
side
side
Station C
O
A
D
M
F
I
U
F
I
U
O
A
D
M
O
A
D
M
O
T
U
5
O
T
U
6
F
I
U
F
I
U
O
A
D
M
OTU3
3
OTU4
WDM
side
Client
side
Optical spectrum
analyzer
An instrument that scans the spectrum to record power, measures the value of loss
insertion and tests the performance of the wavelength and optical signal noise ratio
(OSNR) of each channel.
Optical switch
A passive component possessing two or more ports which selectively transmits, redirects,
or blocks optical power in an optical fiber transmission line.
OSNR
Optical Signal-to-Noise Ratio. Ratio of the optical power of the transmitted optical signal
to the noise on the received signal.
Overhead
A message that is transmitted on the optical network layer and does not need to associate
with a specific connection. For example, such an auxiliary channel can be used as a
digital communication channel between management entities to transmit management
data.
Pointer
An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which it is supported.
Issue 04 (2010-10-20)

A-3

Transport Platform
A Glossary
R
Regeneration
The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
Route
The path a trail takes.
S
S1 byte
The byte defined in ITU-T to transmit the network synchronization status information.
T
U2000
A network management system that Huawei provides to manage transmission networks.

The U2000 is located between the NE level and the network level in the
telecommunication management network structure. That is, the U2000 is a subnetwork
management system. The U2000 provides all management functions at the NE layer and
some of the management functions at the network layer.
Timeslot
Single timeslot on a E1 digital interfacethat is, a 64-kbps, synchronous, full-duplex

data channel, typically used for a single voice connection.
Trail
A type of transport entity, mainly engaged in transferring signal from the input of the
trail source to the output of the trail sink, and monitoring the integrality of the transferred
signal.
U
Upstream station/
downstream station
For the station where signals are received, the station where signals are transmitted and
the station where signals just pass through are upstream stations. As shown in Figure
A-2, service 1 traverses from station A, to station B, and finally to station C. Station A
and station B are upstream stations of station C. The service signals can be ECC signals,
GE signals, or orderwire signals.
Conversely, station B and station C are downstream stations for station A.
Figure A-2 Service flow
1
OTU1
2
OTU2
Clinet WDM
side
side
A-4
Station B
Station A
Station C
O
A
D
M
F
I
U
F
I
U
O
A
D
M
O
A
D
M
O
T
U
5
O
T
U
6

F
I
U
F
I
U
O
A
D
M
OTU3
3
OTU4
WDM
side
Client
side
Issue 04 (2010-10-20)

Transport Platform
User
A Glossary
The user of the U2000 client, and the user and password define the corresponding
authority of operation and management of the U2000.
W
Wander
Issue 04 (2010-10-20)
In telecommunication, wander are long-term random variations of the significant instants

of a digital signal from their ideal positions.

A-5

Transport Platform
B Acronyms and Abbreviations
Acronyms and Abbreviations
A
AIS
Alarm Indication Signal
API
Access Point Identifiers
B
BDI
Backward Defect Indication
BEI
Backward Error Indication
BIP
Bit Interleaved Parity
BITS
Building Integrated Timing Supply System
C
CRC
Cyclical Redundancy Check
D
DAPI
Destination Access Point Identifier
DSP
Digital Signal Processing
E
EDFA
Erbium-Doped Fiber Amplifier
F
FEC
Issue 04 (2010-10-20)
Forward Error Correction

B-1
FPGA

Transport Platform
Field Programmable Gate Array
G
GE
Gigabit Ethernet
H
HP
Higher Order Path
HDB
High Density Bipolar Code
HPI
Higher Order Path Interface
I
IAE
Incoming Alignment Error
L
LACP
Link Aggregation Control Protocol
LOF
Loss Of Frame
LOS
Loss Of Signal
M
MFAS
MultiFrame Alignment Signal
MS
Multiplex Section
O
OCI
Open Connection Indication
ODU
Optical Channel Data Unit
OOF
Out Of Frame
OPU
Optical Channel Payload Unit
OTN
Optical Transmission Network
P
PIN
B-2
Positive Intrinsic Negative

Issue 04 (2010-10-20)

Transport Platform
PM
Path Monitoring
PT
Payload Type
R
RDI
Remote Defect Indication
REI
Remote Error Indication
S
SAPI
Source Access Point Identifiers
SD
Signal Degrade
SDH
Synchronous Digital Hierarchy
SES
SF
Signal Fail
SM
Section Monitoring
T
TIM
Trace Identifier Mismatch
TTI
Trail Trace Identifier
U
UAS
Issue 04 (2010-10-20)
Unavailable Second

B-3

Alarms and Performance Events Reference (V100R002C00 - 04)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Alarms and Performance Events Reference (V100R002C00 - 04)

Caricato da

Copyright:

Formati disponibili

OptiX OSN 1800 Compact Multi-Service Edge Optical Transport

Alarms and Performance Events Reference

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

2.2 Board Alarm List...........................................................................................................................................2-18

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

2.2.33 SCS Board Alarm List........................................................................................................................2-32

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

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

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

4.2.5 LQG Board Performance Event List....................................................................................................4-18

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

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

About This Document

About This Document

OptiX OSN 1800

Network Monitoring Engineer

System Maintenance Engineer

Indicates a hazard with a high level of risk which, if not

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

About This Document

Buttons, menus, parameters, tabs, window, and dialog titles are in

Issue 04 (2010-10-20) Based on Product Version

Issue 03 (2010-07-20) Based on Product Version

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

About This Document

Issue 02 (2010-06-15) Based on Product Version

Issue 01 (2010-03-05) Based on Product Version

Issue 07 (2010-06-30) Based on Product Version V100R001

Issue 06 (2009-10-19) Based on Product Version V100R001

Issue 05 (2009-06-30) Based on Product Version V100R001

Issue 04 (2009-05-30) Based on Product Version V100R001

Huawei Proprietary and Confidential

OptiX OSN 1800 Compact Multi-Service Edge Optical

About This Document

The OA_LOW_GAIN, PUM_BCM_ALM, PUM_TEM_ALM, PRBS_LSS,

Issue 03 (2009-04-10) Based on Product Version V100R001

Issue 02 (2009-02-13) Based on Product Version V100R001