Huwaei Optix Osn 2000

OptiX OSN 2000 Enhanced STM-1/STM-4/STM16 Multi-Service
Optical Transmission System

V100R003
Alarms and Performance Events Reference
Issue 02
Date 2008-10-15
Part Number 00438454
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. 2008. 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 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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

OptiX OSN 2000 Enhanced STM-1/STM-4/STM16 Multi-
Service Optical Transmission System
Alarms and Performance Events Reference Contents
Contents
About This Document.....................................................................................................................1

1 Generation of Alarms and Performance Events of SDH Services....................................1-1
1.1 Overview.........................................................................................................................................................1-2
1.1.1 Signal Flow Directions and Levels........................................................................................................1-3
1.1.2 Two Common Alarms............................................................................................................................1-3
1.1.3 Alarm Management................................................................................................................................1-4
1.2 Generation and Detection of Alarms and Performance Events in the SDH Higher Order Signal Flow.........1-6
1.2.1 Downlink Signal Flow...........................................................................................................................1-7
1.2.2 Uplink Signal Flow..............................................................................................................................1-10
1.3 Generation and Detection of Alarms and Performance Events in the SDH Lower Order Signal Flow.......1-11
1.3.1 Downlink Signal Flow.........................................................................................................................1-12
1.3.2 Uplink Signal Flow..............................................................................................................................1-13
1.3.3 Difference Between Alarm Signals of PDH Interfaces at Various Rates............................................1-14
1.4 Suppression Correlation Between SDH Alarms...........................................................................................1-15
1.4.1 Intra-Board Alarm Suppression...........................................................................................................1-15
1.4.2 Inter-board Alarm Suppression............................................................................................................1-16
1.5 Generation and Detection of SDH Performance Events...............................................................................1-17
1.5.1 Bit Error................................................................................................................................................1-17
1.5.2 Pointer Justification..............................................................................................................................1-21
2 Alarm and Performance Event List.........................................................................................2-1

2.1 Alarm List.......................................................................................................................................................2-2
2.2 Board Alarm List...........................................................................................................................................2-12
2.2.1 ASB Board Alarm List.........................................................................................................................2-13
2.2.2 AUX Board Alarm List........................................................................................................................2-13
2.2.3 AUX1 Board Alarm List......................................................................................................................2-14
2.2.4 CAU Board Alarm List........................................................................................................................2-14
2.2.5 COA Board Alarm List........................................................................................................................2-14
2.2.6 D34S Board Alarm List........................................................................................................................2-14
2.2.7 DSB Board Alarm List.........................................................................................................................2-15
2.2.8 EFFS8 Board Alarm List......................................................................................................................2-15
2.2.9 EFT0 Board Alarm List........................................................................................................................2-15
2.2.10 EFT8A Board Alarm List...................................................................................................................2-15
Issue 02 (2008-10-15) Huawei Proprietary and Confidential i

Contents Alarms and Performance Events Reference
2.2.11 EFT8B Board Alarm List...................................................................................................................2-16

2.2.12 EMS1 Board Alarm List....................................................................................................................2-17
2.2.13 ETFS8 Board Alarm List...................................................................................................................2-17
2.2.14 EU2S Board Alarm List.....................................................................................................................2-18
2.2.15 L12S Board Alarm List......................................................................................................................2-18
2.2.18 LA1 Board Alarm List.......................................................................................................................2-18
2.2.19 PD3 Board Alarm List........................................................................................................................2-18
2.2.20 PIU Board Alarm List........................................................................................................................2-18
2.2.21 PL1 Board Alarm List........................................................................................................................2-19
2.2.22 PL1P Board Alarm List......................................................................................................................2-19
2.2.23 PL3 Board Alarm List........................................................................................................................2-19
2.2.24 PLM Board Alarm List......................................................................................................................2-20
2.2.25 PLMP Board Alarm List....................................................................................................................2-20
2.2.26 PQ1 Board Alarm List........................................................................................................................2-20
2.2.27 PT1 Board Alarms..............................................................................................................................2-21
2.2.28 PT1P Board Alarms...........................................................................................................................2-21
2.2.29 SCC Board Alarms.............................................................................................................................2-21
2.2.30 SD1 Board Alarm List........................................................................................................................2-21
2.2.31 SD4 Board Alarm List........................................................................................................................2-22
2.2.32 SDE Board Alarm List.......................................................................................................................2-22
2.2.33 SL1A Board Alarm List.....................................................................................................................2-23
2.2.34 SL4 Board Alarm List........................................................................................................................2-23
2.2.35 SLM Board Alarm List......................................................................................................................2-23
2.2.36 SQ1 Board Alarm List........................................................................................................................2-24
2.2.37 T12S Board Alarm List......................................................................................................................2-24
2.2.38 T75S Board Alarm List......................................................................................................................2-24
2.2.39 TA1 Board Alarm List.......................................................................................................................2-24
2.2.40 XCS16 Board Alarm List...................................................................................................................2-24
2.2.41 XCS1A Board Alarm List..................................................................................................................2-24
2.2.42 XCS4A Board Alarm List..................................................................................................................2-24
2.3 Performance Event List.................................................................................................................................2-25
2.3.1 SDH Service Performance Event List..................................................................................................2-25
2.3.2 RMON Performance Events List.........................................................................................................2-29
2.3.3 TCM Performance Event List..............................................................................................................2-33
2.3.4 Equipment Function Performance Event List......................................................................................2-34
2.4 Board Performance Event List......................................................................................................................2-35
2.4.1 COA Board Performance Event List....................................................................................................2-36
2.4.2 EFT0 Board Performance Event List...................................................................................................2-36
2.4.3 EFT8A Performance Event List...........................................................................................................2-37
2.4.4 EFT8B Performance Event List...........................................................................................................2-37
ii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

2.4.5 EMS1 Board Performance Event List..................................................................................................2-37

2.4.6 PD3 Board Performance Event List.....................................................................................................2-38
2.4.7 PIU Board Performance Event List......................................................................................................2-38
2.4.8 PL1 Board Performance Event List.....................................................................................................2-38
2.4.9 PL1P Performance Event List..............................................................................................................2-39
2.4.10 PL3 Performance Event List..............................................................................................................2-39
2.4.11 PLM Performance Event List.............................................................................................................2-39
2.4.12 PLMP Performance Event List..........................................................................................................2-39
2.4.13 PQ1 Performance Event List..............................................................................................................2-39
2.4.14 PT1 Performance Event List..............................................................................................................2-39
2.4.15 PT1P Performance Event List............................................................................................................2-39
2.4.16 SD1 Board Performance Event List...................................................................................................2-39
2.4.17 SD4 Performance Event List..............................................................................................................2-40
2.4.18 SDE Board Performance Event List...................................................................................................2-40
2.4.19 SL1A Performance Event List...........................................................................................................2-41
2.4.20 SL4 Board Performance Event List...................................................................................................2-41
2.4.21 SLM Performance Event List.............................................................................................................2-41
2.4.22 SQ1 Performance Event List..............................................................................................................2-41
2.4.23 XCS16 Performance Event List.........................................................................................................2-41
2.4.24 XCS1A Performance Event List........................................................................................................2-42
2.4.25 XCS4A Performance Event List........................................................................................................2-42
3 Alarm Clearing...........................................................................................................................3-1
3.1 A_LOC............................................................................................................................................................3-7
3.2 ALM_GFP_dCSF............................................................................................................................................3-8
3.3 ALM_GFP_dLFD.........................................................................................................................................3-10
3.4 ALM_GFP_dSSF..........................................................................................................................................3-11
3.5 APS_FAIL.....................................................................................................................................................3-13
3.6 APS_INDI.....................................................................................................................................................3-14
3.7 AU_AIS.........................................................................................................................................................3-17
3.8 AU_LOP........................................................................................................................................................3-19
3.9 B1_EXC........................................................................................................................................................3-21
3.10 B1_SD.........................................................................................................................................................3-23
3.11 B2_EXC......................................................................................................................................................3-25
3.12 B2_SD.........................................................................................................................................................3-27
3.13 B3_EXC......................................................................................................................................................3-29
3.14 B3_EXC_VC3.............................................................................................................................................3-31
3.15 B3_SD.........................................................................................................................................................3-34
3.16 B3_SD_VC3................................................................................................................................................3-36
3.17 BD_STATUS..............................................................................................................................................3-39
3.18 BIP_EXC.....................................................................................................................................................3-40
3.19 BIP_SD........................................................................................................................................................3-42
3.20 BUS_ERR...................................................................................................................................................3-44
Issue 02 (2008-10-15) Huawei Proprietary and Confidential iii

3.21 BUS_LOC...................................................................................................................................................3-47
3.22 COMMUN_FAIL........................................................................................................................................3-49
3.23 DBMS_ERROR..........................................................................................................................................3-52
3.24 DN_E1AIS..................................................................................................................................................3-55
3.25 E1_LOC......................................................................................................................................................3-58
3.26 ETH_LOS....................................................................................................................................................3-60
3.27 EXER_FAIL................................................................................................................................................3-61
3.28 EXT_SYNC_LOS.......................................................................................................................................3-62
3.29 FCS_ERR....................................................................................................................................................3-63
3.30 FLOW_OVER.............................................................................................................................................3-65
3.31 FUSE_ALARM...........................................................................................................................................3-66
3.32 HARD_BAD...............................................................................................................................................3-68
3.33 HP_CROSSTR............................................................................................................................................3-70
3.34 HP_LOM.....................................................................................................................................................3-73
3.35 HP_RDI.......................................................................................................................................................3-75
3.36 HP_REI.......................................................................................................................................................3-77
3.37 HP_SLM......................................................................................................................................................3-79
3.38 HP_TIM......................................................................................................................................................3-80
3.39 HP_UNEQ...................................................................................................................................................3-82
3.40 HPAD_CROSSTR......................................................................................................................................3-83
3.41 IN_PWR_ABN............................................................................................................................................3-86
3.42 INPWR_FAIL.............................................................................................................................................3-88
3.43 J0_MM........................................................................................................................................................3-89
3.44 K1_K2_M....................................................................................................................................................3-91
3.45 K2_M..........................................................................................................................................................3-92
3.46 LASER_MOD_ERR...................................................................................................................................3-94
3.47 LCAS_FOPR...............................................................................................................................................3-96
3.48 LCAS_FOPT...............................................................................................................................................3-98
3.49 LCAS_PLCR...............................................................................................................................................3-99
3.50 LCAS_PLCT.............................................................................................................................................3-101
3.51 LCAS_TLCR............................................................................................................................................3-104
3.52 LCAS_TLCT.............................................................................................................................................3-107
3.53 LOOP_ALM..............................................................................................................................................3-109
3.54 LP_CROSSTR..........................................................................................................................................3-110
3.55 LP_R_FIFO...............................................................................................................................................3-113
3.56 LP_RDI.....................................................................................................................................................3-114
3.57 LP_RDI_VC12..........................................................................................................................................3-116
3.58 LP_RDI_VC3............................................................................................................................................3-117
3.59 LP_REI......................................................................................................................................................3-118
3.60 LP_REI_VC12..........................................................................................................................................3-120
3.61 LP_REI_VC3............................................................................................................................................3-121
3.62 LP_RFI......................................................................................................................................................3-123
iv Huawei Proprietary and Confidential Issue 02 (2008-10-15)

3.63 LP_SIZE_ERR..........................................................................................................................................3-124
3.64 LP_SLM....................................................................................................................................................3-125
3.65 LP_SLM_VC12........................................................................................................................................3-127
3.66 LP_SLM_VC3..........................................................................................................................................3-128
3.67 LP_T_FIFO...............................................................................................................................................3-130
3.68 LP_TIM.....................................................................................................................................................3-132
3.69 LP_TIM_VC12.........................................................................................................................................3-133
3.70 LP_TIM_VC3...........................................................................................................................................3-135
3.71 LP_UNEQ.................................................................................................................................................3-137
3.72 LP_UNEQ_VC12......................................................................................................................................3-138
3.73 LP_UNEQ_VC3........................................................................................................................................3-140
3.74 LPT_INEFFECT.......................................................................................................................................3-141
3.75 LPT_RFI....................................................................................................................................................3-143
3.76 LSR_NO_FITED......................................................................................................................................3-144
3.77 LSR_WILL_DIE.......................................................................................................................................3-146
3.78 LTI.............................................................................................................................................................3-147
3.79 MAINBD_SUBBD_MISMATCH............................................................................................................3-150
3.80 MDL_ALARM..........................................................................................................................................3-152
3.81 MSAD_CROSSTR....................................................................................................................................3-154
3.82 MS_AIS.....................................................................................................................................................3-156
3.83 MS_CROSSTR.........................................................................................................................................3-158
3.84 MS_RDI....................................................................................................................................................3-159
3.85 MS_REI.....................................................................................................................................................3-161
3.86 MSSW_DIFFRENT..................................................................................................................................3-164
3.87 NESTATE_INSTALL..............................................................................................................................3-165
3.88 NO_BD_SOFT..........................................................................................................................................3-166
3.89 NO_LSR_PARA_FILE.............................................................................................................................3-169
3.90 NODEID_MM..........................................................................................................................................3-170
3.91 OUT_PWR_ABN......................................................................................................................................3-172
3.92 OUTPWR_FAIL.......................................................................................................................................3-173
3.93 P_AIS........................................................................................................................................................3-174
3.94 P_LOS.......................................................................................................................................................3-176
3.95 PATCH_ERR............................................................................................................................................3-178
3.96 PATCH_NOT_CONFIRM.......................................................................................................................3-179
3.97 PATCHFILE_NOTEXIST........................................................................................................................3-180
3.98 POWER_FAIL..........................................................................................................................................3-182
3.99 PROTECT_MODE...................................................................................................................................3-183
3.100 PWR_MAJ_ALM...................................................................................................................................3-185
3.101 R_FIFO_E...............................................................................................................................................3-186
3.102 R_LOC....................................................................................................................................................3-188
3.103 R_LOF.....................................................................................................................................................3-190
3.104 R_LOS.....................................................................................................................................................3-192
Issue 02 (2008-10-15) Huawei Proprietary and Confidential v

3.105 R_OOF....................................................................................................................................................3-194
3.106 RELAY_ALARM...................................................................................................................................3-197
3.107 RINGMAPM_MM..................................................................................................................................3-198
3.108 RS_CROSSTR........................................................................................................................................3-199
3.109 S1_SYN_CHANGE................................................................................................................................3-201
3.110 SECU_ALM............................................................................................................................................3-202
3.111 SNCP_FAIL............................................................................................................................................3-203
3.112 SNCP_INDI............................................................................................................................................3-204
3.113 SQUTABM_MM....................................................................................................................................3-206
3.114 SYNC_C_LOS........................................................................................................................................3-207
3.115 SYNC_FAIL...........................................................................................................................................3-208
3.116 SYN_BAD..............................................................................................................................................3-210
3.117 T_ALOS..................................................................................................................................................3-212
3.118 T_FIFO_E...............................................................................................................................................3-214
3.119 T_LOC....................................................................................................................................................3-216
3.120 T_LOS.....................................................................................................................................................3-218
3.121 TC_DEG..................................................................................................................................................3-220
3.122 TC_EXC..................................................................................................................................................3-223
3.123 TC_INCAIS............................................................................................................................................3-225
3.124 TC_LTC..................................................................................................................................................3-227
3.125 TC_ODI...................................................................................................................................................3-229
3.126 TC_OEI...................................................................................................................................................3-231
3.127 TC_RDI...................................................................................................................................................3-233
3.128 TC_REI...................................................................................................................................................3-234
3.129 TC_TIM..................................................................................................................................................3-236
3.130 TC_UNEQ...............................................................................................................................................3-239
3.131 TEM_HA.................................................................................................................................................3-240
3.132 TEM_LA.................................................................................................................................................3-242
3.133 TEMP_ALARM......................................................................................................................................3-244
3.134 TF............................................................................................................................................................3-246
3.135 TPS_FAIL...............................................................................................................................................3-247
3.136 TPS_INDI................................................................................................................................................3-248
3.137 TU_AIS...................................................................................................................................................3-250
3.138 TU_AIS_VC12........................................................................................................................................3-253
3.139 TU_AIS_VC3..........................................................................................................................................3-255
3.140 TU_LOP..................................................................................................................................................3-257
3.141 TU_LOP_VC12......................................................................................................................................3-259
3.142 TU_LOP_VC3........................................................................................................................................3-262
3.143 UP_E1AIS...............................................................................................................................................3-264
3.144 VCAT_LOA............................................................................................................................................3-266
3.145 VCAT_LOM_VC12................................................................................................................................3-267
3.146 VCAT_LOM_VC3..................................................................................................................................3-269
vi Huawei Proprietary and Confidential Issue 02 (2008-10-15)

3.147 VCAT_SQM_VC12................................................................................................................................3-271
3.148 VCAT_SQM_VC3..................................................................................................................................3-272
3.149 WRG_BD_TYPE....................................................................................................................................3-274
3.150 W_R_FAILURE......................................................................................................................................3-275
4 Performance Event Clearing....................................................................................................4-1

4.1 AUPJCHIGH...................................................................................................................................................4-4
4.2 AUPJCLOW....................................................................................................................................................4-5
4.3 AUPJCNEW....................................................................................................................................................4-6
4.4 BDTMPCUR...................................................................................................................................................4-7
4.5 BDTMPMAX..................................................................................................................................................4-7
4.6 BDTMPMIN...................................................................................................................................................4-8
4.7 HPBBE............................................................................................................................................................4-8
4.8 HPCSES..........................................................................................................................................................4-9
4.9 HPES.............................................................................................................................................................4-10
4.10 HPFEBBE...................................................................................................................................................4-11
4.11 HPFECSES..................................................................................................................................................4-12
4.12 HPFEES......................................................................................................................................................4-13
4.13 HPFESES....................................................................................................................................................4-14
4.14 HPSES.........................................................................................................................................................4-15
4.15 HPUAS........................................................................................................................................................4-16
4.16 HPFEUAS...................................................................................................................................................4-17
4.17 LPBBE........................................................................................................................................................4-17
4.18 LPCSES.......................................................................................................................................................4-19
4.19 LPES............................................................................................................................................................4-20
4.20 LPFEBBE....................................................................................................................................................4-21
4.21 LPFECSES..................................................................................................................................................4-21
4.22 LPFEES.......................................................................................................................................................4-22
4.23 LPFESES.....................................................................................................................................................4-23
4.24 LPSES.........................................................................................................................................................4-24
4.25 LPUAS........................................................................................................................................................4-25
4.26 LPFEUAS....................................................................................................................................................4-26
4.27 MSBBE.......................................................................................................................................................4-27
4.28 MSCSES......................................................................................................................................................4-28
4.29 MSES..........................................................................................................................................................4-29
4.30 MSFEBBE...................................................................................................................................................4-30
4.31 MSFECSES.................................................................................................................................................4-31
4.32 MSFEES......................................................................................................................................................4-32
4.33 MSFESES....................................................................................................................................................4-33
4.34 MSSES........................................................................................................................................................4-34
4.35 MSUAS.......................................................................................................................................................4-35
4.36 MSFEUAS..................................................................................................................................................4-36
4.37 OSPITMPMAX...........................................................................................................................................4-36
Issue 02 (2008-10-15) Huawei Proprietary and Confidential vii

4.38 OSPITMPMIN............................................................................................................................................4-37
4.39 OSPITMPCUR............................................................................................................................................4-37
4.40 RPLCUR.....................................................................................................................................................4-38
4.41 RPLMAX....................................................................................................................................................4-38
4.42 RPLMIN......................................................................................................................................................4-39
4.43 RSBBE........................................................................................................................................................4-39
4.44 RSCSES......................................................................................................................................................4-41
4.45 RSES...........................................................................................................................................................4-41
4.46 RSOFS.........................................................................................................................................................4-42
4.47 RSSES.........................................................................................................................................................4-43
4.48 RSUAS........................................................................................................................................................4-44
4.49 TLBMAX....................................................................................................................................................4-45
4.50 TLBMIN......................................................................................................................................................4-46
4.51 TLBCUR.....................................................................................................................................................4-46
4.52 TPLMAX....................................................................................................................................................4-47
4.53 TPLMIN......................................................................................................................................................4-47
4.54 TPLCUR......................................................................................................................................................4-48
4.55 TUPJCHIGH...............................................................................................................................................4-48
4.56 TUPJCLOW................................................................................................................................................4-49
4.57 TUPJCNEW................................................................................................................................................4-50
A Glossary.....................................................................................................................................A-1
B Acronyms and Abbreviations.................................................................................................B-1
Index.................................................................................................................................................i-1
viii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Alarms and Performance Events Reference Figures
Figures
Figure 1-1 SDH alarm signal flow.......................................................................................................................1-2

Figure 1-2 Alarm signals generated between the SDH interface and the cross-connect unit.............................. 1-6
Figure 1-3 Generation of alarms between the E1 interface and the cross-connect unit.....................................1-11
Figure 1-4 Structure of the V5 byte....................................................................................................................1-12
Figure 1-5 Structure of the G1 byte....................................................................................................................1-15
Figure 1-6 Suppression relations among key alarms..........................................................................................1-16
Figure 1-7 Inter-board alarm suppression relations............................................................................................1-17
Figure 1-8 Error detection relation and location................................................................................................1-19
Figure 1-9 Location and content of AU_PTR....................................................................................................1-22
Issue 02 (2008-10-15) Huawei Proprietary and Confidential ix

Alarms and Performance Events Reference Tables
Tables
Table 1-1 Same type of alarms with different names.........................................................................................1-14

Table 1-2 Bit error terms....................................................................................................................................1-19
Table 1-3 Alarms and performance events related to bit errors.........................................................................1-20
Table 1-4 Pointer justification state....................................................................................................................1-22
Table 2-1 Alarm list..............................................................................................................................................2-2
Table 2-2 ASB board alarm list..........................................................................................................................2-13
Table 2-3 Logical board AUX alarm list............................................................................................................2-13
Table 2-4 Logical board STI alarm list .............................................................................................................2-14
Table 2-5 CAU board alarm list.........................................................................................................................2-14
Table 2-6 COA board alarm list.........................................................................................................................2-14
Table 2-7 EFT0 board alarm list.........................................................................................................................2-15
Table 2-8 EFT8A Board Alarm List...................................................................................................................2-15
Table 2-9 EFT8B board alarm list......................................................................................................................2-16
Table 2-10 EMS1 board alarm list.....................................................................................................................2-17
Table 2-11 PD3 board alarm list.........................................................................................................................2-18
Table 2-12 PIU board alarm list.........................................................................................................................2-18
Table 2-13 PL1 board alarm list.........................................................................................................................2-19
Table 2-14 PL1P board alarm list.......................................................................................................................2-19
Table 2-15 PLM board alarm list.......................................................................................................................2-20
Table 2-16 PLMP board alarm list.....................................................................................................................2-20
Table 2-17 PQ1 board alarm list.........................................................................................................................2-21
Table 2-18 SCC board alarms............................................................................................................................2-21
Table 2-19 SD1 board alarm list.........................................................................................................................2-22
Table 2-20 SDE board alarm list........................................................................................................................2-22
Table 2-21 SL4 board alarm list.........................................................................................................................2-23
Table 2-22 Logical board XCS alarm list...........................................................................................................2-24
Table 2-23 Pointer justification performance events..........................................................................................2-25
Table 2-24 Regenerator section error performance events.................................................................................2-26
Table 2-25 Multiplex section error performance events.....................................................................................2-26
Table 2-26 Line side performance events...........................................................................................................2-27
Table 2-27 Higher order path error performance events....................................................................................2-27
Table 2-28 Lower order path error performance events.....................................................................................2-28
Table 2-29 RMON alarm list..............................................................................................................................2-29
Issue 02 (2008-10-15) Huawei Proprietary and Confidential xi

Tables Alarms and Performance Events Reference
Table 2-30 RMON performance entry list.........................................................................................................2-30

Table 2-31 TCM performance events.................................................................................................................2-33
Table 2-32 Equipment function performance events..........................................................................................2-34
Table 2-33 COA board performance event list..................................................................................................2-36
Table 2-34 EFT0 board performance event list..................................................................................................2-36
Table 2-35 EFT8A performance event list.........................................................................................................2-37
Table 2-36 EMS1 board performance event list.................................................................................................2-37
Table 2-37 PD3 board performance event list....................................................................................................2-38
Table 2-38 PIU board performance event list....................................................................................................2-38
Table 2-39 PL1 board performance event list....................................................................................................2-39
Table 2-40 SD1 board performance event list....................................................................................................2-39
Table 2-41 SDE board performance event list...................................................................................................2-40
Table 2-42 SL4 board performance event list....................................................................................................2-41
xii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Alarms and Performance Events Reference About This Document
About This Document
Purpose
This document provides the methods for handling the alarms and performance events generated
by the OptiX OSN 2000.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 2000 V100R003
OptiX iManager T2000 V200R007C01
Intended Audience
The intended audiences of this document are:
l Network monitoring engineer

l System maintenance engineer
Organization
This document consists of eight chapters and is organized as follows.
Chapter Description
1 Generation of Alarms This part describes the generation principles of SDH alarms and
and Performance Events performance events and their relations.
of SDH Services
Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1

About This Document Alarms and Performance Events Reference
Chapter Description
2 Alarm and This part lists the alarms and performance events supported by
Performance Event List the OptiX OSN 2000.
3 Alarm Clearing This part provides the methods for handling various alarms on
the OptiX OSN 2000.
4 Performance Event This part provides the methods for handling various
Clearing performance events on the OptiX OSN 2000.
A Glossary Appendix A lists the terms used in this document.
B Acronyms and Appendix B lists the acronyms and abbreviations used in this
Abbreviations document.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
your time.
NOTE Provides additional information to emphasize or

supplement important points of the main text.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.
2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Alarms and Performance Events Reference About This Document
Italic Book titles are in italics.

Courier New Terminal display is in Courier New.
Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... } Alternative items are grouped in braces and separated by

vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
GUI Conventions
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.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.
Issue 02 (2008-10-15) Huawei Proprietary and Confidential 3

About This Document Alarms and Performance Events Reference
Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the pointer.
Double-click Press the primary mouse button twice continuously and quickly without
moving the pointer.
Drag Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2008-10-15)

The updated contents are as follows.
This version fixes some known defects.
Updates in Issue 01 (2008-08-30)

Initial commercial release.
4 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Service Optical Transmission System 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
1 Generation of Alarms and Performance

Events of SDH Services
About This Chapter
1.1 Overview
There are sufficient overhead bytes in the SDH frame, which are the regenerator section
overheads, multiplex section overheads, and path overheads. These overhead bytes carry alarm
and performance information. According to the information, the SDH system can perform in-
service monitoring of alarms and bit errors. With an understanding of the alarm generation and
detection principles, you can quickly locate faults.
1.2 Generation and Detection of Alarms and Performance Events in the SDH Higher Order
Signal Flow
The principle for locating fault is "line first, then tributary; higher order first, then lower
order".
1.3 Generation and Detection of Alarms and Performance Events in the SDH Lower Order Signal
Flow
PDH services include services at rates 1.5 Mbit/s, 2 Mbit/s, 34 Mbit/s, and 140 Mbit/s. PDH
services at different rates use different path overhead bytes. Thus, the alarm signal generation
modes vary accordingly. This section describes the signal flow and the procedure for handling
each overhead byte by each module.
1.4 Suppression Correlation Between SDH Alarms
The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This function involves the intra-board alarm suppression and the inter-board alarm
suppression. In terms of these two types of alarm suppressions, this section describes the
suppression relations among SDH alarms.
1.5 Generation and Detection of SDH Performance Events
The performance events of an SDH network include bit errors and jitter. Jitter can result in
pointer justification on the equipment. Thus, it is the key factor that influences the transmission
quality of the SDH network.
Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1-1

1 Generation of Alarms and Performance Events of SDH Service Optical Transmission System
Services Alarms and Performance Events Reference
1.1 Overview
There are sufficient overhead bytes in the SDH frame, which are the regenerator section
overheads, multiplex section overheads, and path overheads. These overhead bytes carry alarm
and performance information. According to the information, the SDH system can perform in-
service monitoring of alarms and bit errors. With an understanding of the alarm generation and
detection principles, you can quickly locate faults.
Figure 1-1 shows the SDH alarm signal flow.
Figure 1-1 SDH alarm signal flow
SPI RST MST MSA HPT HPA LPT

LOS
"1"
(A1,A2) LOF
J0-MM AIS
(J0)
RS-BIP Err.
(B1)
MS-AIS "1"
(K2) AIS
MS-BIP Err.
(B2)
MS-REI
(M1)
MS-RDI
(K2)
AU-AIS "1"
(H1,H2,H3)
AU-LOP
(H1,H2)
(C2) HP-SLM, HP-UNEQ "1"
HP-TIM
(J1) AIS
HP-BIP Err.
(B3)
HP-REI
(G1)
HP-RDI
(G1)
TU-AIS "1"
(V1,V2,V3)
TU-LOP
(V1,V2)
HP-LOM
(H4)
LP-UNEQ "1"
(V5)
LP-TIM
(J2)
LP-BIP Err. AIS
(V5)
LP-REI
(V5)
LP-RDI
(V5)
"1"
LP-SLM AIS
(V5)
Indicates that the corresponding alarm or signal is generated

Indicates that the corresponding alarm is detected
1.1.1 Signal Flow Directions and Levels

This section describes the basic concepts, including the upstream signal flow, downstream signal
flow, higher order path, and lower order path, which are involved in the signal analysis.
1-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

1.1.2 Two Common Alarms

This section describes two types of common alarms: AIS and RDI.
1.1.3 Alarm Management
This section describes the alarm reporting process.
1.1.1 Signal Flow Directions and Levels

This section describes the basic concepts, including the upstream signal flow, downstream signal
flow, higher order path, and lower order path, which are involved in the signal analysis.
Term Description Figure
Downlink A signal direction: SDH interface

signal → cross-connect unit → PDH SDH SDH
flow interface. interface interface
Crossconnect
unit
PDH interface
Downlink signal flow
Uplink A signal direction: PDH interface

signal → cross-connect unit → SDH SDH SDH
flow interface. interface interface
Crossconnect Uplink
unit signal flow
PDH interface
Higher The path between the SDH Higer order part
order path interface and the cross-connect

unit.
SDH SDH
interface interface
Crossconnect
unit
PDH interface
Lower The path between the cross-

order path connect unit and the PDH
SDH SDH
interface. interface interface
Crossconnect
unit
PDH interface
Lower order part
1.1.2 Two Common Alarms

This section describes two types of common alarms: AIS and RDI.

Alarm Description
Alarm Indication Signal The all "1"s signal that is inserted into the lower level circuit
(AIS) indicates that the signal is unavailable. The MS_AIS, AU_AIS,
TU_AIS and E1_AIS alarms are common AIS alarms.
Remote Defect Indication This alarm indicates that the opposite NE has detected the loss
(RDI) of signal (LOS), AIS, or trace identifier mismatch (TIM) alarm.
When the opposite NE detects these alarms, an RDI alarm is
sent to the local NE.
The MS_RDI, HP_RDI and LP_RDI alarms are common RDI
alarms.
NOTE
If an alarm is generated on an NE, it may not indicate that the NE is faulty. The alarm can be generated
due to a fault at the opposite NE or due to other factors.
For example, the R_LOS alarm is generated due to a fiber cut, or the HP_LOM alarm at the local NE is
generated due to the failure of the cross-connect board at the opposite NE.
1.1.3 Alarm Management

This section describes the alarm reporting process.
Alarms can be reported in the following cases:
l A board detects and reports the alarms to the NE software.
l The NE software reports the alarms to the T2000 server.
l The users query the alarms on the T2000 server through the T2000 client.
In the entire process, alarms are saved on the T2000 after three levels of processing.
The three levels of processing are the following:
l Alarm suppression
l Alarm auto-report
l Alarm filter
In addition, alarm reversion and alarm suppression affect alarm reporting.
Alarm Suppression
The suppression function can be enabled for all alarms on an NE or a board of the NE.
When an alarm is suppressed, the corresponding NE or board does not monitor this alarm.
Alarm Auto-Report
After this function is enabled on an NE, an alarm on the NE is reported to the OptiX iManager
T2000 subnet level management system (T2000) immediately after this alarm occurs. An alarm
panel is displayed on the T2000, where users can check the information about the alarm.
Users can also disable this function for certain alarms. This reduces the impact of a large number
of alarms on the T2000 performance.

Alarm Filter
When the alarm filter function is enabled on the T2000, it does not affect the alarms on the NE.
The T2000 accepts or discards the reported alarms based on the alarm filter function setting.
This function can only be enabled or disabled on an NE. If the function is enabled, the T2000
discards the alarms, and the alarms are not saved into the alarm database. If the function is
disabled, the T2000 saves the alarms into the alarm database.
Alarm Suppression
In normal cases, a root alarm that is directly triggered by abnormal events or faults derives certain
lower level alarms. Thus, alarms cannot be normally located or handled.
In this case, the alarm correlation needs to be set so that non-root alarms can be suppressed.
Then, the NE reports fewer alarms to the NMS, and faults can be located and handled in the
timely manner.
Alarm Reversion
In the case of a port for which services are not activated, the alarm reversion function can be
used to prevent relevant alarm information from being generated and thus to prevent
interferences from the generated alarms.
When the alarm reversion function is enabled, you can set the alarm status of this port to be
opposite to the actual status. That is, an alarm is reported when no alarm occurs and no alarm is
reported when alarms occur.
There are three modes of alarm reversion: non-revertive, auto-revertive, and manual-revertive
mode.
l Non-revertive:
This is the normal alarm monitoring state, and is the default alarm mode. In this mode, the
alarm reversion function cannot be enabled for a port.
l Auto-revertive
In this mode, the alarm reversion function can be enabled only on a port that reports alarms.
After the alarm reversion function is enabled, the port enters the alarm revertive mode, and
does not report alarms. When the current alarms are cleared, the port automatically exits
the revertive mode, and the alarm state reported by the port is restored to be the actual alarm
state.
l Manual-revertive
In this mode, the alarm reversion function can be enabled on a port, regardless of whether
any alarms exist on this port.
– When the alarm reversion function is enabled on a port, the alarm state reported by the
port is inconsistent with the actual alarm state.
– When the manual-revertive mode is disabled, the alarm reversion mode is restored to
be the non-revertive mode. The alarm state reported by the port is consistent with the
actual alarm state.
The precautions for setting the alarm reversion function are as follows:
l The alarm state of the board, including the state of the alarm indicators on the board, remains
unchanged, which indicates the running state of the equipment.

l The alarm reversion function is realized by the NE software. The alarm data on the NE and
on the NMS is the same, which indicates the alarm state after the alarms are reversed.
1.2 Generation and Detection of Alarms and Performance

Events in the SDH Higher Order Signal Flow
The principle for locating fault is "line first, then tributary; higher order first, then lower
order".
Therefore, this section focuses only on the alarms and performance events generated between
the SDH interface and the cross-connect unit during maintenance. This section describes the
signal flow and the procedure for handling each overhead byte by each module.
Figure 1-2 shows the signal flow between the SDH interface and the cross-connect unit.
Figure 1-2 Alarm signals generated between the SDH interface and the cross-connect unit
Frame synchronizer and MS overhead Pointer processor and

RS overhead processor processor HP overhead processor
(RST) (MST) (MSA, HPT)
LOS "1" AIS "1" AIS

A1, AU-AIS
LOF MS-AIS H1,H2
STM-N A2
K2 H1,H2
AU-LOP
optical B2-Err.
HP-TIM Cross-
B2
J1
HP-UNEQ "1" connect
interface BI Err. MS-REI C2
HP-SLM
B1 M1 C2
unit
HP-LOM
MS-RDI H4
K2 B3 Err.
B3
HP-REI
G1
G1 HP-RDI
Downlink signal flow Signal Alarm report or return Alarm

transfer point (Insert down all "1"s termination point
signal) (Report to SCC unit)
Based on the positions of the various overhead byte processing in the STM-N frame, the overhead
bytes are classified into four modules:
l Regenerator section overheads
l Multiplex section overheads
l Higher order path overheads
l Lower order path overheads
If a fault occurs in the first two modules, it affects all the higher order paths. If a fault occurs in
the overhead bytes of a higher order path, however, it affects only this higher order path and its
lower order paths.
The following sections describe the signal flow and the processing of each overhead byte.
1.2.1 Downlink Signal Flow
In the higher order downstream signal flow, overhead bytes are extracted and terminated.
1.2.2 Uplink Signal Flow

The overhead bytes are extracted and then terminated in the downlink signal flow of the higher
order path. Overhead bytes are generated and alarm signals are returned to the opposite NE in
the uplink signal flow of the higher order path.

In the higher order downstream signal flow, overhead bytes are extracted and terminated.
Frame Synchronizer and Regenerator Section Overhead Processor

In the regenerator section (RS), the overhead bytes that are related to the alarms and performance
events are as follows:
l Framing bytes (A1, A2)
l Regenerator section trace byte (J0)
l RS bit interleaved parity (BIP-8) code byte (B1)
The alarm signal flow is as follows:

l In the receive direction
When the STM-N optical signal from a line enters the optical receive module of a line
board, the signal is first converted into an electrical signal through the optical/electrical (O/
E) conversion module.
The signal is then transmitted to a frame synchronizer and an unscrambler for processing.
During this process, the O/E conversion module continuously checks the signal.
An R_LOS alarm is reported if the following faults are detected:
– No signal is input.
– The optical power is extremely low or high.
– The code type of the input signal does not match the original one.
After the R_LOS alarm is raised, the SDH equipment returns to the normal state, only when
the optical receiver at the local station has detected two consecutive correct code patterns
and no new R_LOS alarm is detected. When an R_LOS alarm occurs, the system inserts
an all "1"s signal into the lower level circuits.
l Detecting the A1, A2 and J0 bytes
After receiving an STM-N signal from the O/E conversion module, the frame synchronizer
captures the frame alignment signal through the A1 and the A2 bytes in the signal.
Meanwhile, the frame synchronizer extracts the line reference synchronization clock source
from the signal and sends it to the timing board for locking the clock.
In normal cases, the value of the A1 byte is "F6H", and the value of the A2 byte is "28H".
– If incorrect A1 or A2 values are detected in five consecutive frames, an R_OOF alarm
occurs.
– If the R_OOF alarm lasts for more than 3 ms, an R_LOF alarm occurs, and an all "1"s
signal is inserted.
– If the framing state lasts for more than 1 ms after an R_LOF alarm occurs, the equipment
is restored to normal.
The J0 byte is used to verify if both ends of the regenerator section are permanently
connected to each other. The J0 bytes at the receive end and the J0 bytes at the transmit
end should be the same. Otherwise, the equipment reports a trace identifier mismatch alarm

(J0_MM). An unscrambler is mainly used to unscramble all the bytes except the bytes A1,
A2, and J0, and the two bytes that follow the J0 bytes in the STM-N signals.
l Detecting the B1 byte
The regenerator section overhead (RSOH) processor extracts and processes other RSOH
bytes in the STM-N signal. Among all the bytes, the B1 byte is the most important.
If the B1 byte restored from an STM-N signal is not consistent with the BIP-8 computing
result of the preceding STM-N frame, a B1 bit error is reported.
If the number of B1 bit errors exceeds the threshold 10-3(which is the default value), a
B1_EXC alarm occurs.
If the number of B1 bit errors exceeds the threshold 10-6(which is the default value), a
B1_SD alarm occurs.
When 10 SESs appear consecutively in the RS (for example, when the errored blocks reach 30%
in one second), the RSUAT EVENT performance event occurs. At the same time, bytes such as
F1, D1–D3 and E1 that are not related to the alarms and performance events are transmitted to
the SCC module and the overhead module.
Multiplex Section Overhead Processor

In the multiplex section (MS), the overhead bytes that are related to the alarms and the
performance events are as follows:
l Automatic protection switching bytes (K1, K2)
l MS bit interleaved parity code (BIP-24) byte (B2)
l MS remote error indication (M1)
The signal flow is as follows:
l Detecting the K1 and the K2 bytes

The K2 byte (bits 6–8) is used to indicate a failure at the remote end of the MS.
If the code of the bits 6–8 of the K2 byte is "111", an MS_AIS alarm is generated and an
all "1"s signal is inserted.
The system control and communication board and the cross-connect board can realize the
multiplex section protection (MSP) function by using the K1 and the K2 bytes.
If the code of the bits 6–8 of the K2 byte is "110", an MS_RDI alarm is generated.
The bytes K1 and K2 (bits 1–5) are used to transmit the automatic protection switching
(APS) protocol. The bytes K1 and K2 (bits 1–5) can work with the system control and
communication board and the cross-connect board to realize MSP.
l Detecting the B2 byte and the M1 byte
If the B2 byte recovered from the STM-N signal is not consistent with the BIP-24 computing
result of the preceding STM-N frame (all bits expect for the RSOH), B2 bit errors occur.
The M1 byte is used to check if an MS_REI alarm is reported. The M1 byte carries the
error count of the interleaved bit blocks that the B2 byte has detected.
If B2 bit errors exceed the threshold 10-6 (default), a B2_SD alarm is generated, and if they
exceed the threshold 10-3 (default), a B2_EXC alarm is generated. In the MSP mode, the
B2_EXC and B2_SD (if enabled) alarms can trigger the MSP switching.
If the B2 byte detects 10 consecutive MSSESs, the multiplex section unavailable event
(MSUAT) occurs.

Pointer Processor and Higher Order Path Overhead Processor

The bytes that are related to pointer justifications are H1, H2 and H3.
The bytes that are related to alarms and bit errors are as follows:
l Higher order path trace byte (J1)
l Signal label byte (C2)
l Higher order path bit interleaved parity code (path BIP-8) byte (B3)
l Path status byte (G1)
l Multiframe indicator byte (H4)
The alarm signal flow is as follows:

l Detecting the H1 and H2 bytes
The pointer processor interprets and justifies the pointer on the basis of the H1 and H2 bytes
in each AU-4. It achieves frequency and phase alignment, and tolerates phase jitter and
wander in the network. The pointer processor also locates each VC-4 and transmits them
to the corresponding higher order path overhead processor. If the H1 and the H2 bytes of
the AU pointer are detected to be all "1"s, an AU_AIS alarm is reported and an all "1"s
signal is inserted. If the pointer values of H1 and H2 are illegal (beyond the normal range,
which is from 0 to 782) and illegal pointers are received in eight consecutive frames, an
AU_LOP alarm is reported and an all "1"s signal is inserted.
If the AU pointer justification is positive, the number of PJCHIGHs of the multiplex section
adaptation (MSA) increases by one. If the AU pointer justification is negative, the number
of PJCLOWs of the MSA increases by one.
l Detecting the J1, C2, B3, G1 and H4 bytes
The higher order path overhead processor processes higher order path overhead (HPOH)
bytes in the received NxVC-4s.
The mode for processing each byte is described as follows:
If the J1 byte value detected is not the same as the preset value, an HP_TIM alarm is reported
and an all "1"s signal is inserted.
If the C2 byte is detected as 00, an HP_UNEQ alarm is reported and an all "1"s signal is
inserted. If the C2 byte value that is detected is different from the preset value, an HP_SLM
alarm is reported and an all "1"s signal is inserted.
NOTE
In the case of the Huawei OptiX Metro and OSN series equipment, you can use the NMS to set
whether the all "1"s signal is inserted when the HP_TIM, HP_UNEQ, or HP_SLM alarm occurs. By
default, the all "1"s signal is not inserted.
Currently, the tributary unit group (TUG) is adopted as the payload structure in China. The
preset C2 value that corresponds to the TUG structure is "02".
If the B3 byte restored from the HPOH is not consistent with the BIP-8 computing result
of the VC-4 signal of the preceding frame, B3 bit errors are reported.
In the STM-N lower order SDH interface board, the TU-12 signal extracted from VC-4s
requires the H4 byte to indicate the frame number of the current multiframe in which the
current TU-12 is placed. If the H4 byte detected is illegal, an HP_LOM alarm is reported,
and an all "1"s signal and the normal H4 byte is inserted.
If bit 5 of the G1 byte is "1", an HP_RDI alarm is reported. The value of bits 1–4 of the G1
byte determines if an HP_REI alarm is reported. If the value of bits 1–4 of the G1 byte is
1–8, an HP_REI alarm is reported.

When B3 detects SES for 10 consecutive seconds, an HPUAT EVENT performance event
occurs.
Other overhead bytes such as the F3, K3 and N1 are reserved for future use.
Finally, the NxSTM-1 payloads are transmitted to the cross-connect unit for the cross connection
of the higher order path and the lower order path.

The overhead bytes are extracted and then terminated in the downlink signal flow of the higher
order path. Overhead bytes are generated and alarm signals are returned to the opposite NE in
the uplink signal flow of the higher order path.
Pointer Processor and Higher Order Path Overhead Processor

NxSTM-1 payload signals from the cross-connect unit are first transmitted to higher order path
overhead processor.
The higher order path overhead processor generates N higher order path overhead bytes, which
are transmitted to the pointer processor with the NxSTM-1 payloads.
The setting of higher order path overhead bytes such as the J1, C2, B3, G1, F2, F3 and N1 can
be completed along the upstream direction.
If an AU_AIS, an AU_LOP or a HP_UNEQ alarm is detected in the downstream signal flow,

bit b5 of the G1 byte is set to "1", and an HP_RDI alarm is reported to the remote end, and
returned to the transmit end. The transmit end reports an HP_RDI alarm.
If B3 bit errors are detected in the downstream signal, bits 1–4 of the G1 byte are set to the
number of the detected error blocks (ranging from 1 to 8), and an HP_REI alarm is reported to
the transmit end.
The H4 byte is not processed in the upstream direction.
The pointer processor generates NxAU-4 pointers, and adapts the VC-4 into an AU-4 (H1 and
H2 bytes). The NxAU-4s are then multiplexed into an STM-N signal by using the multiplexing
processor and are transmitted to the MSOH processor.
Multiplex Section Overhead Processor

The multiplex section overhead processor sets the MSOH bytes such as the K1, K2, D4–D12,
S1, M1, E2 and B2 for the received STM-N signal.
If an R_LOS, an R_LOF or an MS_AIS alarm is detected in the downstream signal flow, bits
6–8 of the K2 byte are set to "110". An MS_RDI alarm is reported to the transmit end through
the K2 byte.
If B2 bit errors are detected in the downstream signal flow, an MS_REI alarm is reported to the
remote end through the M1 byte.
Frame Synchronizer and Regenerator Section Overhead Processor

The RSOH processor sets the overhead bytes, such as the A1, A2, J0, E1, F1, D1–D3 and B1,
in the regenerator section and sends a complete STM-N electrical signal to the frame
synchronizer and scrambler.

After being scrambled by the frame synchronizer and scrambler, the STM-N electrical signal is
converted into an STM-N optical signal by the E/O module and then sent out of the optical
interface.
1.3 Generation and Detection of Alarms and Performance

Events in the SDH Lower Order Signal Flow
PDH services include services at rates 1.5 Mbit/s, 2 Mbit/s, 34 Mbit/s, and 140 Mbit/s. PDH
services at different rates use different path overhead bytes. Thus, the alarm signal generation
modes vary accordingly. This section describes the signal flow and the procedure for handling
each overhead byte by each module.
This section describes the processing of the signal flow (for E1 services) between PDH interfaces
and the cross-connect unit, and the generation of alarms.
Figure 1-3 shows the alarm signal flow.
Figure 1-3 Generation of alarms between the E1 interface and the cross-connect unit
HPA , LPT LPA PPI
E1AIS "1'' T-ALOS
Cross- V5
LP-SLM
connect V5
LP-UNEQ
board LP-TIM
J2
TU-LOP LP-TFIFO E1
V1, V2
V1, V2 TU-AIS interface
H4 HP-LOM
LP-RDI
V5
E1AIS
"1''
BIP-2
V5
LP-REI
V5
LP-RFIFO
Signal flow Alarm report or return

Signal transfer point Alarm termination point
(Insert all "1"s signal) (Report to the SCC unit)
As shown in Figure 1-3, the lower order part is divided into the following functional modules
based on different features of the overhead byte processing:
l Higher order path adaptation (HPA)
l Lower order path termination (LPT)
l Lower order path adaptation (LPA)
l PDH physical interface (PPI)
Through the processing of lower order overhead bytes, alarms and performance events can be
detected in the lower order downstream signal flow.


Lower order overhead bytes such as the V5 and H4 are generated in the lower order upstream
signal flow.
1.3.3 Difference Between Alarm Signals of PDH Interfaces at Various Rates
The flow of processing 34 Mbit/s or 140 Mbit/s PDH services is the same as the flow for
processing 2 Mbit/s PDH services. This section describes the differences between the processing
flows of 2 Mbit/s and 34/140 Mbit/s alarm signals.

Through the processing of lower order overhead bytes, alarms and performance events can be
detected in the lower order downstream signal flow.
HPA and LPT

The HPA and LPT modules are the core of the lower order path, because most lower order
overhead bytes are processed on the basis of these modules.
The lower order overhead bytes include the following:

l Lower order path pointer indication bytes (V1, V2 and V3)
l Path state and signal label byte (V5)
l Lower order path identifier (J2)
The VC-4 signal from the cross-connect unit is transmitted to the HPA.
The HPA demaps the VC-4 into VC-12s. The pointers of all VC-12s are decoded to provide the
frame offset information in the unit of bytes between the VC-4 and the VC-12.
When the NE clock at the TU-12 assembler differs from the local reference clock, continuous
pointer justification is required. The positive TU pointer justification (TUPJCHIGH) and the
negative TU pointer justification (TUPJCLOW) are detected in the downlink signal flow.
If wrong H4 multiframe byte sequence is detected in the downlink direction, the HP_LOM alarm
is reported.
If the lower order pointer byte V1 or V2 is all "1"s, a TU_AIS alarm is reported. If the value of
V1 or V2 is illegal, a TU_LOP alarm is reported. If either of these two alarms occur, all "1"s
signal is inserted into the next functional block.
In addition, if a TU_AIS alarm is generated, the AIS signal is inserted in the downstream data,
and at the same time an LP_RDI is reported. Set bit 8 of the V5 byte to "1" to generate an LP_RDI.
The VC-12 signal is transmitted to the LPT unit for V5 byte processing.
Figure 1-4 shows the structure of the V5 byte.
Figure 1-4 Structure of the V5 byte

V5
byte b1 b2 b3 b4 b5 b6 b7 b8
BIP-2 error check 1:LP-REI 1: LP_RFI Signal label

Inconsistent:LPBBE 000:LP-UNEQ 1:LP-RDI

If bits 5–7 of the V5 byte in the downlink signal flow are detected to be "000", the lower order
paths are not equipped (LP_UNEQ), and the AIS signal is inserted into the lower level circuit.
If a signal label mismatch occurs, an LP_SLM alarm is reported.
The path RDI information in bit 8 of the V5 byte is terminated, and an LP_RDI is reported.
Error monitoring bits 1 and 2 of the V5 byte are detected and the BIP-2 for the VC-12 is
calculated. The BIP-2 value that is calculated for the current frame is compared with bits 1 and
2 of the V5 byte recovered from the next frame.
An LPBBE is reported if they are not the same. Meanwhile, bit 3 of the V5 byte is restored. If
it is "1", BIP-2 errors occur at the remote end and an LPFEBBE is reported at the remote end.
NOTE
Bit 4 of the V5 byte is not used.
If 10 consecutive SESs occur during the BIP-2 monitoring, an LVCUATEVENT is reported.

At the same time, the lower order path identifier (J2) is recovered, and the value of the J2 byte
received is checked. If it is different from the expected value, an LP_TIM alarm is reported.
Lower Order Path Adaptation and PDH Physical Interface

The C-12 data that is processed in the previous procedure is transmitted to the LPA.
The subscriber data stream and the related clock reference signals are restored from the container
at the same time, and are transmitted to the PDH physical interface (PPI) as data and timing
reference.
After being processed by the LPA, the data and the clock signal are transmitted to the PPI, and
form a 2048 kbit/s signal.

Lower order overhead bytes such as the V5 and H4 are generated in the lower order upstream
signal flow.
Lower Order Path Adaptation and PDH Physical Interface

When the E1 electrical signal enters the PPI, the signal is transmitted to the mapping and
demapping processor after clock extraction and data regeneration. At the same time, jitter
suppression is performed.
The PPI detects and terminates the T_ALOS alarm. When it detects a T_ALOS alarm, it inserts
all "1"s signals into the upper level circuit.
The LPA completes data adaptation.
If the T_ALOS alarm is detected, an E1_AIS alarm is reported. A T_ALOS alarm causes an
E1_AIS alarm. The E1_AIS alarm can be suppressed by a T_ALOS alarm when the
corresponding alarm correlation is set.
If the deviation of the upstream data rate is too high, FIFO overflow occurs at the transmit end
of the lower order path. As a result, an LP_T_FIFO alarm is reported.
HPA and LPT

The LPT allows the POH to be inserted into the C-12 to form the VC-12.

The LPT inserts the signal label in bits 5–7 of the V5 byte, calculates the BIP-2 for the previous
multiframe data and stores the result in bits 1 and 2 of the V5 byte in the frame. If the path
terminal error is detected in the downstream signal flow, bit 3 of the V5 byte is set to "1" in the
next frame and an LP_REI alarm is generated.
The HPA adapts VC-12 into TU-12, maps it into higher order VC-4, and then sends it to the
cross-connect unit.
The frame offset in the byte between the VC-12 and the VC-4 is indicated by a TU-12 pointer.
Each frame defines one of the V1, V2, V3, and V4 bytes, and every four frames compose a
multiframe. The H4 byte that is used to determine the value of the V byte is also generated in
this functional module.
1.3.3 Difference Between Alarm Signals of PDH Interfaces at

Various Rates
The flow of processing 34 Mbit/s or 140 Mbit/s PDH services is the same as the flow for
processing 2 Mbit/s PDH services. This section describes the differences between the processing
flows of 2 Mbit/s and 34/140 Mbit/s alarm signals.
Same Type of Alarms with Different Names

The Table 1-1 lists the differences between 2 Mbit/s and 34/140 Mbit/s alarm signals.
Table 1-1 Same type of alarms with different names
Board Condition Alarm
2 Mbit/s electrical External signal loss occurs. T_ALOS

interface board
34 Mbit/s electrical P_LOS

interface board
140 Mbit/s electrical EXT_LOS

interface board
2 Mbit/s electrical Signals in the downstream signal flow UP_E1AIS and

interface board are all "1"s. DOWN_E1AIS
34 Mbit/s electrical P_AIS

interface board
140 Mbit/s electrical C4_R_LAISD

interface board
140 Mbit/s electrical Signals in the upstream signal flow are C4_T_LAISD
interface board all "1"s.
NOTE
An EXT_LOS alarm can cause a C4_T_LAISD alarm.

Different Path Overhead Bytes for Alarm and Performance Event Monitoring
The path overhead bytes that are used in the 34 Mbit/s and 140 Mbit/s interface boards are B3,
J1, C2 and G1.
The B3 byte uses the even BIP-8 code for error monitoring. The function of the B3 byte is the
same as that of bits 1–2 of the V5 byte.
The function of the J1 byte is the same as that of the J2 byte.
The C2 byte is the signal label byte and has the same function as bits 5–7 of the V5 byte. The
G1 byte is used to generate the alarm reply.
Figure 1-5 shows the structure of the G1 byte.
Figure 1-5 Structure of the G1 byte
G1 byte b1 b2 b3 b4 b5 b6 b7 b8
HP-REI 1: HP-RDI Reserved
The definition of bits 1–4 of the G1 byte is as follows:

l 0000–1000: indicates that there are 0 to 8 errors respectively.
l 1001–1111: indicates that there are no errors.
1.4 Suppression Correlation Between SDH Alarms

The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This function involves the intra-board alarm suppression and the inter-board alarm
suppression. In terms of these two types of alarm suppressions, this section describes the
suppression relations among SDH alarms.
1.4.1 Intra-Board Alarm Suppression

The intra-board alarm suppression means that, when different levels of alarms occur in a board,
a higher level alarm suppresses a lower level alarm.
1.4.2 Inter-board Alarm Suppression
The inter-board alarm suppression means that, when services are configured between two boards
on the same NE, the service alarm generated by the source board suppresses the service alarm
generated by the sink board. The equipment supports the alarm suppression between a line board
and a tributary board, and between a line board and a data board.
1.4.1 Intra-Board Alarm Suppression

The intra-board alarm suppression means that, when different levels of alarms occur in a board,
a higher level alarm suppresses a lower level alarm.
Figure 1-6 shows the suppression relations among key alarms.

Figure 1-6 Suppression relations among key alarms
R_LOS
R_LOF TU_AIS TU_LOP
J0_MM MS_AIS B1_EXC B2_EXC

BIP_EXC
AU_AIS AU_LOP B1_SD B2_SD
B3_EXC HP_TIM HP_SLM HP_LOM HP_UNEQ
B3_SD TU_AIS TU_LOP BIP_EXC
LP_UNEQ LP_TIM LP_SLM BIP_SD
For example: A B means A suppresses B
The higher level alarms above the arrow can suppress the lower level alarms below the arrow.
Thus, pay attention to higher level alarms when locating faults.
1.4.2 Inter-board Alarm Suppression

The inter-board alarm suppression means that, when services are configured between two boards
on the same NE, the service alarm generated by the source board suppresses the service alarm
generated by the sink board. The equipment supports the alarm suppression between a line board
and a tributary board, and between a line board and a data board.
Figure 1-7 shows the inter-board suppression relations among common alarms.

Figure 1-7 Inter-board alarm suppression relations

R_LOS
R_LOC
R_LOF
MS_AIS
AU_LOP
HP_LOM
AU_AIS
TU_AIS TU_AIS_VC3 TU_AIS_VC12
A B means A suppresses B
If an alarm above the arrow is generated at the service source, and the alarm below the arrow is
generated at the service sink, the alarm above the arrow suppresses the alarm below the arrow.
In this case, you can focus on the alarms at the service source during troubleshooting.
1.5 Generation and Detection of SDH Performance Events

The performance events of an SDH network include bit errors and jitter. Jitter can result in
pointer justification on the equipment. Thus, it is the key factor that influences the transmission
quality of the SDH network.
1.5.1 Bit Error

Bit errors are detected through the parity check of the B1, B2, B3 and V5 bytes.
1.5.2 Pointer Justification
Pointer justification is used to adjust pointers as required, so that rate asynchronization and phase
difference of payload signals can be tolerated. The rate of the information payloads is adjusted
through pointer justification. As a result, the payloads are synchronized with the STM-N frame.
1.5.1 Bit Error

Bit errors are detected through the parity check of the B1, B2, B3 and V5 bytes.
Generation Mechanism
The SDH system adopts bit interleaved parity (BIP) to detect bit errors. The BIP is performed
on the BIP matrix of the RS, MS, higher order path, and lower order path using the B1, B2, B3
and V5 bytes respectively.

The B1 byte is used for error monitoring in the regenerator section. This function is performed
by using a bit interleaved parity 8 (BIP-8) code with even parity. The working mechanism of
the B1 byte is as follows:
1. At the transmit end, the BIP-8 is computed for all the scrambled bytes of the current frame
(frame N) and the result is placed in the B1 byte of the next frame (frame N+1) to be
scrambled.
2. At the receive end, the BIP-8 is computed for all bits of the current frame (frame N-1) to
be descrambled and the result is compared with the value of the B1 byte of the next
descrambled frame (frame N).
3. If the two values are different, exclusive-OR operation is conducted on them. The number
of "1"s in the result is the number of errored blocks in the frame during the transmission.
The B2 byte is used for error monitoring in the multiplex section, and the working mechanism
is similar to the working mechanism of the B1 byte. The B1 byte monitors the errors that occur
in the entire STM-N frame during the transmission. One STM-N frame has only one B1 byte.
The B2 byte monitors the errors that occur in every STM-1 frame of the STM-N frame. The
STM-N frame contains Nx3 B2 bytes. Every three B2 bytes correspond to one STM-1 frame.
For example, there are three B2 bytes for one STM-1 frame. The working mechanism of the B2
bytes is as follows:
1. At the transmit end, the BIP-24 is computed for all bits of the previous STM-1 frame except
the RSOH, and the result is stored in the B2 bytes of the current frame to be scrambled.
2. At the receive end, the BIP-24 is computed for all bits of the current descrambled STM-1
frame except the RSOH, and exclusive-OR operation is conducted between the parity result
and the B2 bytes in the next descrambled STM-1 frame.
3. The number of "1"s in the result of the exclusive-OR operation is the number of errored
blocks that occur in this STM-1 frame within the STM-N frame during the transmission.
A maximum of 24 errored blocks can be detected.
The B3 byte is used to monitor the bit errors of the VC-4 or the 140 Mbit/s signal within the
STM-N frame during the transmission. The monitoring mechanism of the B3 byte is similar to
that of the B1 and B2 bytes; however, it is used to perform the BIP-8 parity for the VC-4 frame.
The V5 byte performs the functions of error monitoring, signal label and VC-12 path status. Bits
1–2 are used to perform the BIP-2 monitoring of bit errors in the VC-12 within the STM-N
frame. If the receive end detects errored blocks, the number of such blocks are displayed in the
performance events at the local end. At the same time, bit 3 of the V5 byte reports the lower
order path remote error indication (LP_REI) to the transmit end, and the corresponding number
of errored blocks are displayed in the performance events at the transmit end.
Error Detection and Report

Figure 1-8 shows the error detection relation and location.

Figure 1-8 Error detection relation and location
LPT HPT MST RST RST MST HPT LPT
B1
B2
B3
V5
As shown in Figure 1-8, the modules are defined as follows:
l RST is regenerator section termination.

l MST is multiplex section termination.
l HPT is higher order path termination.
l LPT is lower order path termination.
The B1, B2, B3 and V5 bit errors are respectively monitored between these terminations. Figure
1-8 shows that bit errors that occur in the lower order path cannot be detected in the higher order
path, MS and RS. If bit errors occur in the regenerator section, the bit errors are triggered in the
MS, higher order path and lower order path.
Generally, higher order bit errors can trigger lower order bit errors. If the B1 bit error occurs,
the B2, B3 and V5 bit errors are generated. On the contrary, if the V5 bit error occurs, B3, B2
and B1 bit errors are not necessarily generated.
When the SDH system detects errors, it reports the error performance events or alarms, and
notifies the remote end of error detection through overhead bytes.
Terms
Table 1-2 lists the relevant terms.
Table 1-2 Bit error terms
Term Description
BE Block error. It indicates that one or more bits have errors.
BBE Background block error. It indicates an errored block occurring outside the period
of UAT and SES.
FEBBE Far end background block error. It indicates that a BBE event is detected at the
far end.
ES Errored second. It indicates a certain second that is detected with one or more
errored blocks.

Term Description
FEES Far end errored second. It indicates that an ES event is detected at the far end.
SES Severely errored second. It indicates a certain second, which contains more than
30% errored blocks or at least one serious disturbance period (SDP). The SDP is
a period of at least four consecutive blocks or 1 ms (taking the longer one) where
the error ratios of all the consecutive blocks are more than or equal to 10-2 or a
loss of signal occurs.
FESES Far end severely errored second. It indicates an SES event that is detected at the
far end.
CSES Consecutive severely errored second. It indicates the SES events that occur
consecutively, but last less than 10 seconds.
FECSES Far end consecutive severely errored second. It indicates a CSES event that is
detected at the far end.
UAS Unavailable second. A period of 10 consecutive seconds during which the bit
error ratio per second of the digital signal in either of the transmission directions
of a transmission system is inferior to 10-3. These 10 seconds are considered to
be part of the unavailable time.
Relationship with Alarms

When errors are detected, the local end of the SDH system reports an alarm or performance
event, and reports the error detection information to the remote end through overhead bytes.
According to the performance events or alarms reported from the local end and remote end, you
can determine the faulty section of the path or the signal directions where errors occur. Table
1-3 lists the alarms and performance events related to bit errors.
Table 1-3 Alarms and performance events related to bit errors
Item Performance Event Alarm
If the bit If the bit If the bit errors If the bit errors
errors errors exceed exceed the exceed the
exceed the the threshold threshold at the threshold at the
threshold at at the local local station, the local station, the
the local station, the local station opposite station
station, the opposite reports the alarm. reports the alarm.
local station station
reports the reports the
relevant relevant
event. event.
Regener RSBBE - B1_SD/B1_EXC -

ator
section
Multiple MSBBE MSFEBBE B2_SD/B2_EXC MS_REI

x section

Item Performance Event Alarm
If the bit If the bit If the bit errors If the bit errors
errors errors exceed exceed the exceed the
exceed the the threshold threshold at the threshold at the
threshold at at the local local station, the local station, the
the local station, the local station opposite station
station, the opposite reports the alarm. reports the alarm.
local station station
reports the reports the
relevant relevant
event. event.
Higher HPBBE HPFEBBE B3_SD/B3_EXC HP_REI

order
path
Lower LPBBE LPFEBBE BIP_SD/BIP_EXC LP_REI

order
path
result of the previous STM-N frame, the B1 bit error occurs.
result of the previous STM-N frame (all bits expect the RSOH), the B2 bit error occurs.
If the B3 byte recovered from the HPOH is not consistent with BIP-8 computing result of the
VC-4 signal of the previous frame, the B3 bit error occurs.
If bit 1 and bit 2 of the V5 byte that is restored from the LPOH are different from the BIP-2
calculating result of the VC-12 signal in the previous frame, the BIP errors are reported.
If B1, B2 and B3 bit errors exceed the 10-6 threshold, alarms such as the B1_SD, B2_SD, B3_SD
occur. If B1, B2 and B3 bit errors exceed the 10-3 threshold, alarms such as the B1_EXC,
B2_EXC and B3_EXC occur.
When B1 detects 10 consecutive SESs in the RS, it indicates that an RSUAT event occurs.
When B2 detects 10 consecutive SESs in the MS, it indicates that an MSUAT event occurs.
When B3 detects 10 consecutive SESs, it indicates that an HPUAT event occurs.
When V5 detects 10 consecutive SESs, it indicates that an LPUAT event occurs.
1.5.2 Pointer Justification

Pointer justification is used to adjust pointers as required, so that rate asynchronization and phase
difference of payload signals can be tolerated. The rate of the information payloads is adjusted
through pointer justification. As a result, the payloads are synchronized with the STM-N frame.
Payload pointer in the SDH can be classified into administrative unit pointer (AU_PTR) and
tributary unit pointer (TU_PTR). Pointer justification thus involves administrative unit pointer
justification and tributary unit pointer justification.

Generation Mechanism of AU Pointer Justification

In the AU-4 frame shown in Figure 1-9, several bytes in specific locations (the first nine bytes
in the fourth row) are used to record the location of the starting point of data information (to
represent the data information phase). These bytes are called pointers. H1 and H2 are pointers,
and three H3s are negative pointer justification opportunities.
Figure 1-9 Location and content of AU_PTR
9 rows
VC-4
H1 YY H2 1* 1* H3 H3 H3
AU- 4 PTR 1 9
Y Byte: 1001SS11 (S Unspecified ) 10 270columns

1* Byte: 11111111
When the network is synchronous, the pointer is used to perform phase alignment among the
synchronous signals. If the NEs work under the same clock, the signals that are transmitted from
various NEs to a certain NE have the same clock frequency. Thus, rate adaptation is not
necessary. Transiently, the rate may be either a little higher or lower. In this case, phase alignment
is required.
When the network is not synchronous, the NEs work at different frequencies, and the pointer is
used for frequency justification. Pointer justification is also required to tolerate the frequency
jitter and wander in the network.
If the frame rate of the VC is different from that of the AUG, information is stuffed in the H3
bytes of the AU pointer area. The idle bytes are stuffed with pseudo-random information and
are inserted before the VC to decrease or increase the frame rate of the VC. At the same time,
the pointer value is raised or dropped to increase or decrease the frame rate of the VC. Thus,
positive and negative pointer justifications are generated. See Table 1-4.
Table 1-4 Pointer justification state

State Byte Numbering and Content of the Fourth Row in the STM-1 Rate
Name Frame Relatio
n
7 8 9 10 11 12
Pointer H3 H3 H3 Informat Informat Informati Informat

zero ion ion on ion =
justificat containe
ion r
Positive H3 H3 H3 Stuffing Stuffing Stuffing Informat

pointer ion <
justificat containe
ion r

State Byte Numbering and Content of the Fourth Row in the STM-1 Rate
Name Frame Relatio
n
7 8 9 10 11 12
Negative Informat Informati Informat Informat Informat Informati Informat

pointer ion on ion ion ion on ion >
justificat containe
ion r
All the NEs in the SDH network are generally well synchronized, and pointer justification seldom
occurs. Actual performance monitoring for pointer justification of the network proves that AU
pointer justification and TU pointer justification seldom occurs.
It is difficult to guarantee that all the NEs are well synchronized all the time during long-term
network operation. If one or several NEs are not synchronized, even for a very short time, a great
amount of pointer justifications could occur. Consecutive positive or negative pointer
justification adjusts the phase forward or backward to realize the frequency justification.
Generation Mechanism of TU Pointer Justification

The causes of TU pointer justification are as follows:
l TU pointer justification is transformed from AU pointer justification.
TU pointer justification does not occur when the E1 signal is adapted into VC-12, and
multiplexed into STM-1. If there is frequency offset between the E1 signal of the switch
and the SDH clock, adapt the signal to realize synchronization. Thus, TU pointer
justification that is detected on the tributary board is generally transformed from AU pointer
justification.
l TU pointer justification occurs during demultiplexing.
If the system clock is not consistent with the received clock, TU pointer justification occurs
during demultiplexing.
l When the upstream NE that the service passes through has pointer justification, TU pointer
justification occurs at the local NE during demultiplexing.
Detection and Reporting of Pointer Justifications

There are two modes of detection and reporting of AU pointer justification: remote detection
and local detection.
l Remote detection
The information about AU pointer justification that is generated at the local NE is
transferred to the remote NE through the H1 and H2 bytes. The remote NE realizes the
report of the AU pointer justification by interpreting the H1 and H2 bytes. Thus, if the
remote NE reports an AU pointer justification event, the local NE has pointer justification.
The remote NE refers to the downstream NE in the service direction.
l Local detection
AU pointer justification that is generated at the local NE is detected and reported at the
local NE. Therefore, if the local NE reports an AU pointer justification event, the local NE
has pointer justification.

In the SDH system, the AU pointer justification events on a majority of optical interface boards
are detected and reported through the detection of the H1 and H2 bytes. This is also called remote
detection.
As the transformation from AU pointer justification into TU pointer justification could occur at
the upstream NE instead of the local NE, the local NE does not necessarily have pointer
justification if the tributary board reports pointer justification events.
Generally, AU pointer justification is generated at the upstream NE, but it is detected and
reported at the downstream NE. TU pointer justification is generated at the NE where AU pointer
justification is transformed into TU pointer justification. It is detected and reported at the
tributary board of the NE where the service is terminated.

Alarms and Performance Events Reference 2 Alarm and Performance Event List
2 Alarm and Performance Event List
About This Chapter
This part describes the alarms supported by the product.
2.1 Alarm List

This part lists the alarms supported by the product alphabetically.
2.2 Board Alarm List
This part lists the alarms mapping the supported boards.
2.3 Performance Event List
This part describes the performance events supported by the product. The performance events
cover the SDH service and the Ethernet service.
2.4 Board Performance Event List
This part lists the performance events mapping the supported boards.

2 Alarm and Performance Event List Alarms and Performance Events Reference
2.1 Alarm List

This part lists the alarms supported by the product alphabetically.
Table 2-1 lists the alarms.
Table 2-1 Alarm list

Alarm Name Description Sever Board
ity
A_LOC Add to bus - loss of clock Major PL1, PT1, PLM, PL1P, PT1P,
PLMP, PQ1, PL3, and PD3
ALM_GFP_dCS GFP customer signal loss Critic EFT0, EFT8A, EFT8B, and
F al EMS1
ALM_GFP_dLF GFP out of frame Critic EFT0, EFT8A, EFT8B, and

D al EMS1
ALM_GFP_dSS GFP synchronous byte loss Critic EFT0, EFT8A, EFT8B, and
F al EMS1
APS_FAIL APS protection switching Major SCC

failed
APS_INDI Automatic protection Major SCC

switching indication
AU_AIS AU alarm indication Major SL4, OSB1A, OSB4A,

OSB16a, SL1A, SLM, SD1,
SD4, SQ1, and SDE
AU_LOP AU loss of pointer Major SL4, OSB1A, OSB4A,

OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
B1_EXC Regenerator section (B1) Minor SL4, OSB1A, OSB4A,

excessive errors OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
B1_SD Regenerator section (B1) Minor SL4, OSB1A, OSB4A,

signal degraded OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
B2_EXC Multiplex section (B2) Major SL4, OSB1A, OSB4A,

excessive errors OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
B2_SD Multiplex section (B2) signal Minor SL4, OSB1A, OSB4A,

degraded OSB16a, SL1A, SLM, SD1,
SD4, SQ1, and SDE


ity
B3_EXC Higher order path (B3) Major SL4, OSB1A, OSB4A,

excessive bit errors OSB16, SL1A, SLM, SD1,
SD4, SQ1, SDE, PL3, PD3,
PLM, and PLMP
B3_EXC_VC3 VC-3 path (B3) excessive Major EFT0, EFT8A, EFT8B, and
errors EMS1
B3_SD Higher order path (B3) signal Minor SL4, OSB1A, OSB4A,
degraded OSB16, SL1A, SLM, SD1,
PLM, and PLMP
B3_SD_VC3 VC-3 path (B3) signal Minor EFT0, EFT8A, EFT8B, and
degraded EMS1
BD_STATUS Board not in position alarm Major SCCb ,XCS, EFT0, EFT8A,
EFT8B, EMS1, PL1, PT1,
PLM, PQ1, SL4, PIU, LA1,
TA1, L12S, T12S, L75S,
T75S, AUX, AUX1, STI,
OSB1A, OSB4A, OSB16,
SL1A, SLM, SD1, SD4, SQ1,
SDE, PL3, PD3, L34S, D34S,
ASB, DSB, EU2S, CAU,
COA, EFFS8, ETFS8, PL1P,
PT1P, and PLMP
BIP_EXC BIP excessive errors Minor EFT0, EFT8A, EFT8B,

EMS1, PL1, PT1, PLM,
PL1P, PT1P, PLMP, and PQ1
BIP_SD BIP signal degraded Minor EFT0, EFT8A, EFT8B,

EMS1, PL1, PT1, PLM,
PL1P, PT1P, PLMP, and PQ1
BUS_ERR Bus error Critic XCSc, EFT0, EFT8A,

al EFT8B, EMS1, PL1, PT1,
PLM, PQ1, SL4, OSB1A,
OSB4A, OSB16, SL1A,
SLM, SD1, SD4, SQ1, SDE,
PL3, PD3, PL1P, PT1P, and
PLMP
BUS_LOC Bus dropping loss of clock Major PL1, PT1, PLM, PL1P, PT1P,
COMMUN_FAI Board communication failure Major SCC, XCS, and EMS1

L
DBMS_ERROR Database error Major SCC


ity
DN_E1AIS Alarm indication of the 2M Minor PL1, PT1, PLM, PL1P, PT1P,
downlink signal PLMP, and PQ1
E1_LOC Loss of 2M clock in upstream Major PL1, PT1, PLM, PL1P, PT1P,
signal PLMP, and PQ1
ETH_LOS Network interface connection Critic EFT0, EFT8A, EFT8B, and

loss alarm al EMS1
EXER_FAIL Exercise switch failed Major SCC
EXT_SYNC_LO Loss of external synchronous Critic XCS

S source al
FCS_ERR FCS check error Critic EFT0, EFT8A, EFT8B, and

al EMS1
FLOW_OVER Received flow exceeds the Major EMS1

threshold
HARD_BAD Hardware failed Critic SCC, XCS, EFT0, EFT8A,

al EFT8B, EMS1, PL1, PT1,
PLM, PQ1, SL4, PIU, LA1,
TA1, L12S, T12S, L75S,
T75S, AUX,AUX1, STId,
SDE, PL3, PD3, L34S, D34S,
ASB, DSB, EU2S, CAU,
COA, EFFS8, ETFS8, PL1P,
PT1P, and PLMP
HP_CROSSTR Higher order path performance Minor SL4, OSB1A, OSB4A,

over threshold OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
HP_LOM Loss of multi-frame in the Major PL1, PT1, PLM, PQ1, SL4,
higher order path OSB1A, OSB4A, OSB16,
SDE, PL1P, PT1P, and
PLMP
HP_RDI Higher order path remote Minor SL4, OSB1A, OSB4A,

defect indication OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
HP_REI Higher order path remote error Warni SL4, OSB1A, OSB4A,
indication ng OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
HP_SLM Higher order path signal Minor SL4, OSB1A, OSB4A,

identification mismatch OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE


ity
HP_TIM High order path trace identifier Minor SL4, OSB1A, OSB4A,
mismatch OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
HP_UNEQ No loading error in the higher Minor SL4, OSB1A, OSB4A,

order path OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
HPAD_CROSST Adaptation performance Minor PL1, PT1, PLM, PL1P, PT1P,

R threshold-crossing of the PLMP, PQ1, PL3, and PD3
lower order path
VCAT_LOM_V VC-12-Xv path multiframe Major EFT0, EFT8A, EFT8B, and

C12 identifier mismatch EMS1
VCAT_LOM_V VC-3-Xv path multiframe Major EFT0, EFT8A, EFT8B, and

C3 identifier mismatch EMS1
VCAT_SQM_V VC-12-Xv path SQ number Major EFT0, EFT8A, and EFT8B

C12 identifier mismatch
VCAT_SQM_V VC-3-Xv path SQ number Major EFT0, EFT8A, and EFT8B

C3 identifier mismatch
LPT_INEFFECT LPT function failed Major EFT0, EFT8A, and EFT8B
LPT_RFI Link status pass-through Major EFT0, EFT8A, EFT8B, and

remote end failure EMS1
INPWR_FAIL Input power failed Major PIU
J0_MM Trace identifier mismatch Minor SL4, OSB1A, OSB4A,

SD4, SQ1, and SDE
K1_K2_M K1 and K2 mismatch Minor SCC
K2_M K2 mismatch Minor SCC
LASER_CLOSE Laser closed Major SL4, OSB1A, OSB4A,

D OSB16, SL1A, SLM, SD1,
SD4, and SQ1
LCAS_PLCT Partial loss of capacity Minor EFT0, EFT8A, EFT8B, and

transmit EMS1
LCAS_TLCT Total loss of capacity transmit Major EFT0, EFT8A, EFT8B, and
EMS1
LCAS_PLCR Partial loss of capacity receive Minor EFT0, EFT8A, EFT8B, and
EMS1
LCAS_TLCR Total loss of capacity receive Major EFT0, EFT8A, EFT8B, and
EMS1


ity
LCAS_FOPT Failure of protocol transmit Major EFT0, EFT8A, EFT8B, and

EMS1
LCAS_FOPR Failure of protocol receive Major EFT0, EFT8A, EFT8B, and

EMS1
LOOP_ALM Loop alarm Minor XCS, EFT0, EFT8A, EFT8B,

EMS1, PL1, PT1, PLM, PQ1,
SL4, OSB1A, OSB4A,
PL1P, PT1P, and PLMP
LP_CROSSTR Lower order path performance Minor PL1, PT1, PLM, PL1P, PT1P,
parameter over threshold PLMP, PQ1, PL3, and PD3
LP_R_FIFO FIFO overflow at the receive Minor PL1, PT1, PLM, PL1P, PT1P,
side of lower order path PLMP, and PQ1
LP_T_FIFO FIFO overflow at the transmit Minor PL1, PT1, PLM, PL1P, PT1P,
side of lower order path PLMP, and PQ1
LP_RDI Lower order path remote Minor PL1, PT1, PLM, PL1P, PT1P,
defect indication PLMP, PQ1, PL3, and PD3
LP_RDI_VC12 VC-12 level path remote Minor EFT0, EFT8A, EFT8B, and
defect indication EMS1
LP_RDI_VC3 VC-3 level path remote defect Minor EFT0, EFT8A, EFT8B, and
indication EMS1
LP_REI Lower order path remote error Minor PL1, PT1, PLM, PL1P, PT1P,
indication PLMP, PQ1, PL3, and PD3
LP_REI_VC12 VC-12 level lower path remote Minor EFT0, EFT8A, EFT8B, and
error indication EMS1
LP_REI_VC3 VC-3 level path remote error Minor EFT0, EFT8A, EFT8B, and
indication EMS1
LP_RFI Lower order path remote Minor PL1, PT1, PLM, PL1P, PT1P,
failure indication PLMP, and PQ1
LP_SIZE_ERR TU structure error Minor PL1, PT1, PLM, PL1P, PT1P,

PLMP, and PQ1
LP_SLM Lower order path signal label Minor PL1, PT1, PLM, PL1P, PT1P,
mismatch PLMP, PQ1, PL3, and PD3
LP_SLM_VC12 VC-12 level path signal label Minor EFT0, EFT8A, EFT8B, and
mismatch EMS1
LP_SLM_VC3 VC-3 level path signal label Minor EFT0, EFT8A, EFT8B, and
mismatch EMS1


ity
LP_TIM Lower order path tracking Minor PL1, PT1, PLM, PL1P, PT1P,
identification mismatch PLMP, PQ1, PL3, and PD3
LP_TIM_VC12 VC-12 level path tracking Minor EFT0, EFT8A, EFT8B, and
identification mismatch EMS1
LP_TIM_VC3 VC-3 level path tracking Minor EFT0, EFT8A, EFT8B, and
identification mismatch EMS1
LP_UNEQ Lower order path unequipped Minor PL1, PT1, PLM, PL1P, PT1P,
LP_UNEQ_VC1 VC-12 level path unequipped Minor EFT0, EFT8A, EFT8B, and
2 EMS1
LP_UNEQ_VC3 VC-3 level path unequipped Minor EFT0, EFT8A, EFT8B, and
EMS1
LSR_NO_FITED Laser not installed Critic EFT0, EFT8B, EMS1,

al OSB1A, OSB4A, OSB16,
SL1A, SLM, SD1, SD4, and
SQ1
LTI Loss of synchronous source Major XCS
MAINBD_SUBB Main board and subboard Major EFT0, EMS1, PL1, PT1,
D_MISMATCH mismatch PLM, PL3, PD3, and SDE
MS_AIS Multiplex section alarm Major SL4, OSB1A, OSB4A,

indication OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
MS_CROSSTR Multiplex section path Minor SL4, OSB1A, OSB4A,

performance over threshold OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
MS_RDI Multiplex section remote Minor SL4, OSB1A, OSB4A,

defect indication OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
MS_REI Multiplex section remote error Warni SL4, OSB1A, OSB4A,

indication ng OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
MSAD_CROSST Multiplex section adaptation Minor SL4, OSB1A, OSB4A,

R performance over threshold OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
NESTATE_INST NE in install state Critic SCC

ALL al


ity
NO_BD_SOFT No board software Critic SCC, AUX, AUX1, EMS1,

al XCS, SL4, OSB1A, OSB4A,
OSB16, PL3, PD3, SL1A,
SD1, SD4, SQ1, SLM, and
SDE
NODEID_MM Multiplex section node ID Major SCC

mismatch
POWER_FAIL Power failure Major PIU
PROTECT_MO Database in protect mode Critic SCC

DE al
P_AIS All "1"s AIS indication at PDH Major PL3, PD3, PLM, and PLMP
interface
P_LOS Loss of analog signal at PDH Major PL3 and PD3

interface
R_LOC Receive loss of clock Critic SL4, OSB1A, OSB4A,

al OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
R_LOF Receive loss of frame Critic SL4, OSB1A, OSB4A,

SD4, SQ1, and SDE
R_LOS Receive loss of signal Critic SL4, OSB1A, OSB4A,

SD4, SQ1, and SDE
R_OOF Receive out of frame Critic SL4, OSB1A, OSB4A,

SD4, SQ1, and SDE
RELAY_ALAR Relay alarm Critic AUX and AUX1

M al
RINGMAPM_M Ring map mode mismatch Minor SCC

M
RS_CROSSTR Regenerator section Minor SL4, OSB1A, OSB4A,

performance over threshold OSB16, SL1A, SLM, SD1,
SD4, SQ1, and SDE
S1_SYN_CHAN Reference source change in S1 Major XCS

GE mode
SECU_ALM Security alarm Major SCC
SNCP_FAIL SNCP failed Critic SCC

al


ity
SNCP_INDI SNCP indication Major SCC
SQUTABM_MM Squelch table mode mismatch Minor SCC
SYN_BAD Synchronous source degraded Minor XCS
SYNC_C_LOS Synchronous source level loss Warni XCS

ng
SYNC_FAIL SCC batch backup failure Minor SCC
T_ALOS 2M interface loss of analog Major PL1, PT1, PLM, PL1P, PT1P,
signal PLMP, and PQ1
T_LOC Transmit loss of clock Major SL4, OSB1A, OSB4A,

SD4, SQ1, and SDE
T_LOS Transmit loss of signal Major SL4, OSB1A, OSB4A,

SD4, SQ1, and SDE
TC_DEG Tandem connection degraded Minor SL4

signal
TC_EXC Tandem connection excessive Major SL4

error
TC_INCAIS Tandem connection incoming Major SL4

AIS
TC_LTC Loss of tandem connection Major SL4
TC_ODI Tandem connection output Minor SL4

defect indication
TC_OEI Tandem connection output Warni SL4

error indication ng
TC_RDI Tandem connection remote Minor SL4

defect indication
TC_REI Tandem connection remote bit Warni SL4

error indication ng
TC_TIM Tandem connection trace Minor SL4

identifier mismatch
TC_UNEQ Tandem connection Minor SL4

unequipped
TEMP_ALARM Temperature alarm Minor XCS, EMS1, SL4, PIU, and

CAUe
TPS_FAIL TPS_FAIL Major SCC


ity
TPS_INDI TPS indication alarm Major SCC
TU_AIS TU alarm indication Major PL1, PT1, PLM, PL1P, PT1P,

TU_AIS_VC12 TU of VC-12 level alarm Major EFT0, EFT8A, EFT8B,

indication EMS1, SL4, OSB1A,
OSB4A, OSB16, SL1A,
SLM, SD1, SD4, SQ1 and
SDE
TU_AIS_VC3 TU of VC-3 level alarm Major EFT0, EFT8A, EFT8B,

indication EMS1, SL4, OSB1A,
OSB4A, OSB16, SL1A,
SDE
TU_LOP TU loss of pointer Major PL1, PT1, PLM, PL1P, PT1P,

PLMP, PL3, PD3, and PQ1.
TU_LOP_VC12 TU of VC-12 level loss of Major EFT0, EFT8A, EFT8B,

pointer EMS1, SL4, OSB1A,
OSB4A, OSB16, SL1A,
SDE
TU_LOP_VC3 TU of VC-3 level loss of Major EFT0, EFT8A, EFT8B,

pointer EMS1, SL4, OSB1A,
OSB4A, OSB16, SL1A,
SDE
UP_E1AIS 2M up signal alarm indication Minor PL1, PT1, PLM, PL1P, PT1P,
PLMP, and PQ1.
W_R_FAILURE Reading and writing board Major EMS1, STI, and COA
register failed
WRG_BD_TYP Wrong inserted board type Major SCC

E
TF Laser transmission failed Critic EFT0, EFT8B, EMS1, SL1A,

SD1, SD4, SQ1, and SLM
IN_PWR_ABN Abnormal input optical power Major EFT0, EFT8B, EMS1,

and COA


ity
OUT_PWR_AB Abnormal output optical Critic EFT0, EFT8B, EMS1,

N power al OSB1A, OSB4A, OSB16,
and COA
LSR_WILL_DIE Laser life to be terminated Critic EFT0, EFT8B, EMS1, SL1A,

TEM_HA Laser temperature crossing the Major EFT0, EFT8B, EMS1, SL1A,
upper threshold OSB1A, OSB4A, OSB16,
TEM_LA Laser temperature crossing the Major EFT0, EFT8B, EMS1, SL1A,
lower threshold OSB1A, OSB4A, OSB16,
NO_LSR_PARA Non-existent laser parameter Major EFT0, EFT8B, EMS1, SL1A,

_FILE file OSB1A, OSB4A, OSB16,
LASER_MOD_E Optical module wrongly Major EFT0, EFT8B, EMS1, SL1A,

RR inserted OSB1A, OSB4A, OSB16,
MDL_ALARM Power module alarm Major CAU
PWR_MAJ_AL DC power over-voltage/ Critic CAU

M under-voltage al
FUSE_ALARM Fuse cut Critic CAU

al
LOCK_CUR_FA Working current lock failed Critic COA

IL al
WORK_CUR_O Working current override Major COA

VER
COOL_CUR_O Cooling current override Major COA

VER
IN_PWR_FAIL Input power unavailable Critic COA

al
TEMP_OVER Operating temperature Major COA

override
NO_BD_PARA Board parameters not set Critic COA

al
FPGA_ABN Abnormal FPGA Major COA

NOTE
l a: The line units of the XCS1A/XCS4A/XCS16 are mapped as logical boards OSB1A/OSB4A/OSB16
is the T2000.
l b: If the equipment is configured with two SCC boards, when one SCC board is not in the proper slot,
the BD_STATUS is reported. If the equipment is configured with one SCC board, the alarm is not
reported.
l c: The cross-connect and time units of the XCS1A/XCS4A/XCS16 board are mapped as logical board
XCS in the T2000.
l d: The timing unit of the AUX/AUX1 board is mapped as the logical board STI on the T2000.
l e: On the T2000, the UPM is mapped as the logical board CAU.
2.2 Board Alarm List

This part lists the alarms mapping the supported boards.
2.2.1 ASB Board Alarm List

2.2.2 AUX Board Alarm List
2.2.3 AUX1 Board Alarm List
2.2.4 CAU Board Alarm List
2.2.5 COA Board Alarm List
2.2.6 D34S Board Alarm List
2.2.7 DSB Board Alarm List
2.2.8 EFFS8 Board Alarm List
2.2.9 EFT0 Board Alarm List
2.2.10 EFT8A Board Alarm List
2.2.11 EFT8B Board Alarm List
2.2.12 EMS1 Board Alarm List
2.2.13 ETFS8 Board Alarm List
2.2.14 EU2S Board Alarm List
2.2.15 L12S Board Alarm List
2.2.18 LA1 Board Alarm List
2.2.19 PD3 Board Alarm List
2.2.20 PIU Board Alarm List
2.2.21 PL1 Board Alarm List
2.2.22 PL1P Board Alarm List

2.2.24 PLM Board Alarm List

2.2.25 PLMP Board Alarm List
2.2.26 PQ1 Board Alarm List
2.2.27 PT1 Board Alarms
2.2.28 PT1P Board Alarms
2.2.29 SCC Board Alarms
2.2.30 SD1 Board Alarm List
2.2.32 SDE Board Alarm List
2.2.33 SL1A Board Alarm List
2.2.34 SL4 Board Alarm List
2.2.35 SLM Board Alarm List
2.2.36 SQ1 Board Alarm List
2.2.37 T12S Board Alarm List
2.2.39 TA1 Board Alarm List
2.2.40 XCS16 Board Alarm List
2.2.41 XCS1A Board Alarm List
2.2.1 ASB Board Alarm List
Table 2-2 ASB board alarm list
BD_STATUS HARD_BAD -
2.2.2 AUX Board Alarm List
Logical Board AUX Alarm List
Table 2-3 Logical board AUX alarm list
RELAY_ALARM HARD_BAD BD_STATUS
NO_BD_SOFT - -

Logical Board STI Alarm List
Table 2-4 Logical board STI alarm list
BD_STATUS HARD_BAD W_R_FAILURE
2.2.3 AUX1 Board Alarm List
Logical Board AUX Alarm List

For the logical board AUX alarm list, see Table 2-3.
Logical Board STI Alarm List

For the logical board STI alarm list, see Table 2-3.
Logical Board LA1 Alarm List

For the logical board LA1 alarm list, see Table 2-2.
2.2.4 CAU Board Alarm List
Table 2-5 CAU board alarm list
PWR_MAJ_ALM FUSE_ALARM TEMP_ALARM
MDL_ALARM BD_STATUS -
2.2.5 COA Board Alarm List
Table 2-6 COA board alarm list
LOCK_CUR_FAIL WORK_CUR_OVER COOL_CUR_OVER
IN_PWR_FAIL IN_PWR_ABN OUT_PWR_ABN
TEMP_OVER W_R_FAILURE BD_STATUS
NO_BD_PARA FPGA_ABN -
2.2.6 D34S Board Alarm List

For the D34S board alarm list, see Table 2-2.

2.2.7 DSB Board Alarm List
For the DSB board alarm list, see Table 2-2.
2.2.8 EFFS8 Board Alarm List
For the EFFS8 board alarm list, see Table 2-2.
2.2.9 EFT0 Board Alarm List
Table 2-7 EFT0 board alarm list
BD_STATUS BIP_EXC BIP_SD
HARD_BAD LOOP_ALM ETH_LOS
TU_AIS_VC3 TU_LOP_VC3 LP_UNEQ_VC3
LP_TIM_VC3 LP_SLM_VC3 LP_RDI_VC3
LP_REI_VC3 B3_EXC_VC3 B3_SD_VC3
VCAT_SQM_VC12 VCAT_SQM_VC3 VCAT_LOM_VC3
VCAT_LOM_VC12 TU_AIS_VC12 TU_LOP_VC12
LP_UNEQ_VC12 LP_TIM_VC12 LP_SLM_VC12
LP_RDI_VC12 LP_REI_VC12 FCS_ERR
VCAT_LOA BUS_ERR MAINBD_SUBBD_MISMATCH
LCAS_PLCT LCAS_TLCT LCAS_PLCR
LCAS_TLCR LCAS_FOPT LCAS_FOPR
TF IN_PWR_ABN OUT_PWR_ABN
LSR_WILL_DIE TEM_HA TEM_LA
NO_LSR_PARA_FILE LSR_NO_FITED LASER_MOD_ERR
ALM_GFP_dLFD ALM_GFP_dCSF ALM_GFP_dSSF
LPT_RFI LPT_INEFFECT -
2.2.10 EFT8A Board Alarm List
Table 2-8 EFT8A Board Alarm List

VCAT_LOA BUS_ERR LCAS_PLCT
LCAS_TLCT LCAS_PLCR LCAS_TLCR
LCAS_FOPT LCAS_FOPR ALM_GFP_dLFD
ALM_GFP_dCSF ALM_GFP_dSSF LPT_RFI
LPT_INEFFECT - -
2.2.11 EFT8B Board Alarm List
Table 2-9 EFT8B board alarm list

VCAT_LOA BUS_ERR LCAS_PLCR
LCAS_PLCT LCAS_TLCT LCAS_FOPR
LCAS_TLCR LCAS_FOPT OUT_PWR_ABN
TF IN_PWR_ABN TEM_LA

LSR_WILL_DIE TEM_HA LASER_MOD_ERR
NO_LSR_PARA_FILE LSR_NO_FITED ALM_GFP_dLFD
ALM_GFP_dCSF ALM_GFP_dSSF LPT_RFI
LPT_INEFFECT - -
2.2.12 EMS1 Board Alarm List
Table 2-10 EMS1 board alarm list
VCAT_LOM_VC3 VCAT_LOM_VC12 TU_AIS_VC12
TU_LOP_VC12 LP_UNEQ_VC12 LP_TIM_VC12
LP_SLM_VC12 LP_RDI_VC12 LP_REI_VC12
FCS_ERR VCAT_LOA BUS_ERR
MAINBD_SUBBD_MISMATCH LSR_NO_FITED NO_BD_SOFT
W_R_FAILURE TEMP_ALARM LCAS_PLCT
LCAS_TLCT LCAS_PLCR LCAS_TLCR
LCAS_FOPT LCAS_FOPR COMMUN_FAIL
TF IN_PWR_ABN OUT_PWR_ABN
LSR_WILL_DIE TEM_HA TEM_LA
NO_LSR_PARA_FILE LASER_MOD_ERR ALM_GFP_dLFD
ALM_GFP_dCSF ALM_GFP_dSSF FLOW_OVER
LPT_RFI- - -
2.2.13 ETFS8 Board Alarm List
For the ETFS8 board alarm list, see Table 2-2.

2.2.14 EU2S Board Alarm List

For the EU2S board alarm list, see Table 2-2.

For the L12S board alarm list, see Table 2-2.


2.2.18 LA1 Board Alarm List

For the LA1 board alarm list, see Table 2-2.
2.2.19 PD3 Board Alarm List
Table 2-11 PD3 board alarm list

A_LOC B3_EXC B3_SD
BUS_LOC BD_STATUS BUS_ERR
HARD_BAD HPAD_CROSSTR LOOP_ALM
LP_CROSSTR LP_RDI LP_REI
LP_SLM LP_TIM LP_UNEQ
NO_BD_SOFT P_AIS P_LOS
R_FIFO_E TU_AIS TU_LOP
MAINBD_SUBBD_MIS T_FIFO_E -
MATCH
2.2.20 PIU Board Alarm List
Table 2-12 PIU board alarm list

BD_STATUS INPWR_FAIL POWER_FAIL
TEMP_ALARM HARD_BAD OUTPWR_FAIL

Table 2-13 PL1 board alarm list
BUS_LOC A_LOC DN_E1AIS
E1_LOC HARD_BAD HPAD_CROSSTR
HP_LOM LOOP_ALM LP_CROSSTR
LP_RDI LP_REI LP_RFI
LP_SIZE_ERR LP_SLM LP_TIM
LP_UNEQ TU_AIS TU_LOP
T_ALOS UP_E1AIS BUS_ERR
LP_R_FIFO LP_T_FIFO MAINBD_SUBBD_MISMATCH
2.2.22 PL1P Board Alarm List
Table 2-14 PL1P board alarm list
LP_R_FIFO LP_T_FIFO -
For the PL3 board alarm list, see Table 2-11.

2.2.24 PLM Board Alarm List
Table 2-15 PLM board alarm list
LP_R_FIFO LP_T_FIFO MAINBD_SUBBD_MISMATCH
B3_SD B3_EXC P_AIS
2.2.25 PLMP Board Alarm List
Table 2-16 PLMP board alarm list
LP_R_FIFO LP_T_FIFO P_AIS
B3_SD B3_EXC -
2.2.26 PQ1 Board Alarm List

For the PQ1 board alarm list, see the following table.

Table 2-17 PQ1 board alarm list

LP_R_FIFO LP_T_FIFO -
2.2.27 PT1 Board Alarms

For the PT1 board alarm list, see Table 2-13.
2.2.28 PT1P Board Alarms

For the PT1P board alarms, see Table 2-14.
2.2.29 SCC Board Alarms
Table 2-18 SCC board alarms

APS_FAIL APS_INDI DBMS_ERROR
K1_K2_M K2_M NESTATE_INSTALL
NO_BD_SOFT PROTECT_MODE SECU_ALM
HARD_BAD WRG_BD_TYPE SNCP_INDI
SNCP_FAIL TPS_INDI TPS_FAIL
NODEID_MM RINGMAPM_MM SQUTABM_MM
PATCHFILE_NOTEXIST PATCH_ERR PATCH_NOT_CONFIRM
EXER_FAIL COMMUN_FAIL MSSW_DIFFERENT
SYNC_FAIL - -

Table 2-19 SD1 board alarm list
AU_AIS BD_STATUS AU_LOP
B1_EXC B1_SD B2_EXC
B2_SD B3_EXC B3_SD
HARD_BAD HP_CROSSTR HP_LOM
HP_RDI HP_REI HP_SLM
HP_TIM HP_UNEQ J0_MM
LOOP_ALM MSAD_CROSSTR MS_AIS
MS_CROSSTR MS_RDI MS_REI
RS_CROSSTR R_LOC R_LOF
R_LOS R_OOF T_LOC
T_LOS BUS_ERR LASER_CLOSED
TU_AIS_VC3 TU_LOP_VC3 TU_AIS_VC12
TU_LOP_VC12 NO_BD_SOFT TF
IN_PWR_ABN OUT_PWR_ABN LSR_WILL_DIE
TEM_HA TEM_LA NO_LSR_PARA_FILE
LASER_MOD_ERR LSR_NO_FITED -
For the SD4 board alarm list, see Table 2-19.
2.2.32 SDE Board Alarm List
Table 2-20 SDE board alarm list
B1_EXC B1_SD B2_EXC
B2_SD B3_EXC B3_SD

R_LOS R_OOF T_LOC
T_LOS BUS_ERR TU_AIS_VC3
TU_LOP_VC3 TU_AIS_VC12 TU_LOP_VC12
NO_BD_SOFT MAINBD_SUBBD_MISMATCH -
2.2.33 SL1A Board Alarm List
For the SL1A board alarm list, see Table 2-19.
2.2.34 SL4 Board Alarm List
Table 2-21 SL4 board alarm list
B1_EXC B1_SD B2_EXC
B2_SD B3_EXC B3_SD
R_LOS R_OOF T_LOC
T_LOS BUS_ERR NO_BD_SOFT
TU_AIS_VC3 TU_LOP_VC3 TU_AIS_VC12
TU_LOP_VC12 - -
2.2.35 SLM Board Alarm List
For the SLM board alarm list, see Table 2-19.

2.2.36 SQ1 Board Alarm List

For the SQ1 board alarm list, see Table 2-19.

For the T12S board alarm list, see Table 2-2.

For the T75S board alarm list, see Table 2-2.
2.2.39 TA1 Board Alarm List

For the TA1 board alarm list, see Table 2-2.
2.2.40 XCS16 Board Alarm List
Logical Board XCS Alarm List
Table 2-22 Logical board XCS alarm list
BD_STATUS HARD_BAD LTI
S1_SYN_CHANGE SYNC_C_LOS SYN_BAD
EXT_SYNC_LOS BUS_ERR TEMP_ALARM
COMMUN_FAIL NO_BD_SOFT LOOP_ALM
Logical Board OSB16 Alarm List

For the logical board OSB16 alarm list, see Table 2-19.
Logical board XCS alarm list

For the logical board XCS alarm list, see Table 2-22.
Logical board OSB1A alarm list

For the logical board OSB1A alarm list, see Table 2-19.

Logical board XCS alarm list

For the logical board XCS alarm list, see Table 2-22.
Logical Board OSB4A Alarm List

For the logical board OSB4A alarm list, see Table 2-19.
2.3 Performance Event List

This part describes the performance events supported by the product. The performance events
cover the SDH service and the Ethernet service.
2.3.1 SDH Service Performance Event List

The performance events of SDH services can be classified into three categories: Pointer
justification, bit error, and equipment function.
2.3.2 RMON Performance Events List
The RMON alarm entries and RMON performance entries supported by the Ethernet service
processing board comply with RFC2819.
2.3.3 TCM Performance Event List
The TCM performance events are for monitoring the transmission performance in the tandem
connection segment.
2.3.4 Equipment Function Performance Event List
The equipment function performance events convey the performance including the board
temperature, current, and optical power.
2.3.1 SDH Service Performance Event List

The performance events of SDH services can be classified into three categories: Pointer
justification, bit error, and equipment function.
Table 2-23 Pointer justification performance events
Abbreviation Details Supported Board
AUPJCHIGH Count of positive AU SL4, OSB1A, OSB4A, OSB16a,

pointer justifications SL1A, SLM, SD1, SD4, SQ1, and
SDE
AUPJCLOW Count of negative AU
pointer justifications
AUPJCNEW Count of new AU pointer

justifications
TUPJCHIGH Count of positive TU PL1, PT1, PLM, PL1P, PT1P, PLMP,

pointer justification PQ1, PL3, and PD3
TUPJCLOW Count of negative TU

pointer justifications

TUPJCNEW Count of new TU pointer

justifications
NOTE
a: The line units of the XCS1A/XCS4A/XCS16 are mapped as logical boards OSB1A/OSB4A/OSB16 in
the T2000.
Table 2-24 Regenerator section error performance events
RSBBE Regenerator section block SL4, OSB1A, OSB4A, OSB16a,

of background error SL1A, SLM, SD1, SD4, SQ1, and
SDE
RSES Regenerator section errored
second
RSSES Regenerator section

severely errored second
RSUAS Regenerator section

unavailable second
RSCSES RS consecutive severe error

seconds
RSOFS Regenerator section out-of-

frame second
Table 2-25 Multiplex section error performance events
MSBBE Multiplex section block of SL4, OSB1A, OSB4A, OSB16,

background error SL1A, SLM, SD1, SD4, SQ1,
and SDE
MSES Multiplex section errored
second
MSSES Multiplex section severely

errored second
MSCSES Multiplex section consecutive

MSUAS Multiplex section unavailable

second
MSFEUAS Multiplex section far end

unavailable second

MSFEES Multiplex section far end errored

second
MSFESES Multiplex section far end

MSFEBBE Multiplex section far end block

of background error
MSFECSES Multiplex section far end

consecutive severely errored
second
Table 2-26 Line side performance events

T3_LCV_SDH T3 line side code violation count PL3 and PD3
T3_LES_SDH T3 line side code violation errored second
T3_LSES_SDH T3 line side code violation severely

errored second
E3_LCV_SDH E3 line side code violation count
E3_LES_SDH E3 line side code violation errored second
E3_LSES_SDH E3 line side code violation severely

errored second
Table 2-27 Higher order path error performance events

HPBBE Higher order path block of EMS1, SL4, OSB1A, OSB4A,

background error OSB16, SL1A, SLM, SD1, SD4,
SQ1 and SDE
HPFEBBE Higher order path far end block of
background error
HPES Higher order path errored second
HPFEES Higher order path far end errored

second
HPSES Higher order path severely errored

second
HPFESES Higher order path far end severely

errored second

HPCSES Higher order path consecutive

HPFECSES Higher order path far end

second
HPUAS Higher order path unavailable

second
HPFEUAS Higher order path far end

unavailable second
Table 2-28 Lower order path error performance events

LPBBE Lower order path block of EFT0, EFT8A, EFT8B, EMS1,

background error PL1, PT1, PLM, PL1P, PT1P,
PLMP, PQ1, PL3 and PD3
LPFEBBE Lower order path far end block of
background error
LPES Lower order path errored second
LPFEES Lower order path far end errored

second
LPSES Lower order path severely errored

second
LPFESES Lower order path far end severely

errored second
LPCSES Lower order path continuous

severe bit error second
LPFECSES Lower order path far end

second
LPUAS Lower order path unavailable

second
LPFEUAS Lower order path far end

second

2.3.2 RMON Performance Events List

The RMON alarm entries and RMON performance entries supported by the Ethernet service
processing board comply with RFC2819.
Table 2-29 RMON alarm list

Alarm name Description Supported board
DROPEVENT_OVER The quantity of packet loss events is EFT0, EFT8A, EFT8B,

over the upper limit. and EMS1
DROPEVENT_UNDE The quantity of packet loss events is

R under the lower threshold.
INBADOCTS_OVER The number of received bad octets is

over the upper threshold.
INBADOCTS_UNDER The number of received bad octets is

under the lower threshold.
OUTBADOCTS_OVE The number of transmitted bad octets

R is over the upper threshold.
OUTBADOCTS_UND The number of transmitted bad octets

ER is under the lower threshold.
COLLISION_OVER The number of detected collisions is

over the upper threshold.
COLLISION_UNDER The number of detected collisions is

under the lower threshold.
ALIGNMENT_OVER The number of alignment errors is over

the upper threshold.
ALIGNMENT_UNDE The number of alignment errors is

R under the lower threshold.
FCSERROR_OVER The number of check errors is over the

upper threshold.
FCSERROR_UNDER The number of check errors is under

the lower threshold.
LATECOLLISION_O The number of collisions in the last

VER hour is over the upper threshold.
LATECOLLISION_U The number of collisions in the last

NDER hour is under the upper threshold.
EXCESCOLLISION_O The number of transmission failures

VER caused by successive collisions is over

Alarm name Description Supported board
EXCESCOLLISION_U The number of transmission failures

NDER caused by successive collisions is
under the upper threshold.
DEFFER_OVER The number of frames deferred in

transmission is over the upper
threshold.
DEFFER_UNDER The number of frames deferred in

transmission is under the lower
threshold.
CARRIER_OVER The number of carrier conflicts is over

CARRIER_UNDER The number of carrier conflicts is over

the upper threshold or under the lower
threshold.
Table 2-30 RMON performance entry list
Performance Performance Name Supported Board

Type
Basic The total number of received packets (including EFT0, EFT8A, EFT8B,
performance bad packets) that have a length of 64 bytes and EMS1
(excluding framing bits but including FCS bytes)
The total number of received packets (including

bad packets) with a length of 65–127 bytes
(excluding framing bits, but including FCS
bytes)

bad packets) that have a length between 128 to
255 bytes (excluding framing bits but including
FCS bytes)

bytes)

bytes)

bytes)


Type
The total number of received good packets

(excluding multicast packets) whose destination
address is the broadcast address

(excluding broadcast packets) whose destination
address is a multicast address
The number of undersize packets
The number of oversize packets
The number of fragments
The number of received packets, including bad

packets
Check errors and alignment errors
The number of jabbers
Times of detected events that the monitor EMS1

abandons packets
The received bytes, including bytes in the bad

packets
Extended The total number of transmitted packets EFT0, EFT8A, EFT8B,

performance (including bad packets) that have a length of 64 and EMS1
bytes (excluding framing bits but including FCS
bytes)
The total number of transmitted packets

(including bad packets) that have a length
between 65 to 127 bytes (excluding framing bits
but including FCS bytes)

(including bad packets) with a length of 128–255
bytes (excluding framing bits, but including FCS
bytes)

(including bad packets) with a length of 256–511
bytes (excluding framing bits, but including FCS
bytes)

(including bad packets) with a length of 512–
1023 bytes (excluding framing bits, but
including FCS bytes)


Type

(including bad packets) with a length of 1024–
1518 bytes (excluding framing bits, but
The total number of received and transmitted

packets in the length of 64 bytes

packets in the length of 65–127 bytes




Good-packet bytes received
Bad-packet bytes received
Good-packet bytes transmitted
Bad-packet bytes transmitted
The total number of received unicast packets
The number of unicast packets transmitted
The number of the received MAC flow control

frames with the PAUSE opcode
The number of the transmitted MAC flow control

frames with the PAUSE opcode
The total number of transmitted good packets

(excluding broadcast packets) whose destination
address is a multicast address.

(excluding multicast packets) whose destination
address is the broadcast address.
The number of received frames (excluding

oversized frames and undersized frames) that
have a length of an integer number and have FCS
errors


Type
The total number of received and transmitted EMS1

The times of detected events that the monitor

abandons packets
Collisions
Alignment errored frames
Frames correctly transmitted after only one

collision
Frames correctly transmitted after multiple

collisions
Late collisions
Frames unsuccessfully transmitted after

successive collisions
Delayed frames
Carrier sense condition failure

bad packets) whose length is between 1519 bytes
and the MTU (excluding framing bits, but

(including bad packets) whose length is between
1519 bytes and the MTU (excluding framing bits,
but including FCS bytes)
Port utilization
2.3.3 TCM Performance Event List

The TCM performance events are for monitoring the transmission performance in the tandem
connection segment.
Table 2-31 TCM performance events
TCBBE Tandem connection background SL4

block error
TCFEBBE Tandem connection far end

background block error

TCOBBE Tandem connection output

background block error
2.3.4 Equipment Function Performance Event List

The equipment function performance events convey the performance including the board
temperature, current, and optical power.
Table 2-32 Equipment function performance events

WCVMAX Maximum value of pump laser working COA

current
WCVMIN Minimum value of pump laser working

current
CCVMAX Maximum value of laser cooling current of

erbium-doped fiber amplifier
CCVMIN Minimum value of laser cooling current of

erbium-doped fiber amplifier
BCVMAX Maximum value of pump laser back facet

current
BCVMIN Minimum value of pump laser back facet

current
EDTPLMAX Maximum value of output optical power
EDTPLMIN Minimum value of output optical power
EDRPLMAX Maximum value of input optical power
EDRPLMIN Minimum value of input optical power
EDWCSMAX Maximum value of working current setting
EDWCSMIN Minimum value of pump laser working

current setting
EDTMPMAX Maximum value of environment temperature
EDTMPMIN Minimum value of environment temperature
BDTMPCUR Current board temperature EMS1, SL4, XCSa, PIU,

and COA
BDTMPMAX Maximum value of board temperature
BDTMPMIN Minimum value of board temperature

TLBMAX Maximum value of laser bias current EFT0, EFT8B, EMS1,

OSB1A, OSB4A,
TLBMIN Minimum value of laser bias current OSB16b, SL1A, SLM,
TLBCUR Current value of laser bias current SD1, SD4 and SQ1
TPLMAX Maximum value of output optical power
TPLMIN Minimum value of output optical power
TPLCUR Current value of output optical power
RPLMAX Maximum value of input optical power
RPLMIN Minimum value of input optical power
RPLCUR Current value of input optical power
OSPITMPMAX Maximum value of laser working

temperature
OSPITMPMIN Minimum value of laser working

temperature
OSPITMPCUR Current value of laser working temperature
NOTE
l a: The cross-connect and time units of the XCS1A/XCS4A/XCS16 board are mapped as logical board
XCS in the T2000.
l b: The line units of the XCS1A/XCS4A/XCS16 are mapped as logical boards OSB1A/OSB4A/OSB16
in the T2000.
2.4 Board Performance Event List

This part lists the performance events mapping the supported boards.
2.4.1 COA Board Performance Event List

2.4.2 EFT0 Board Performance Event List
2.4.3 EFT8A Performance Event List
2.4.4 EFT8B Performance Event List
2.4.5 EMS1 Board Performance Event List
2.4.6 PD3 Board Performance Event List
2.4.7 PIU Board Performance Event List
2.4.8 PL1 Board Performance Event List
2.4.9 PL1P Performance Event List
2.4.10 PL3 Performance Event List

2.4.11 PLM Performance Event List

2.4.12 PLMP Performance Event List
2.4.13 PQ1 Performance Event List
2.4.14 PT1 Performance Event List
2.4.15 PT1P Performance Event List
2.4.16 SD1 Board Performance Event List
2.4.17 SD4 Performance Event List
2.4.18 SDE Board Performance Event List
2.4.19 SL1A Performance Event List
2.4.20 SL4 Board Performance Event List
2.4.21 SLM Performance Event List
2.4.22 SQ1 Performance Event List
2.4.23 XCS16 Performance Event List
2.4.24 XCS1A Performance Event List
2.4.1 COA Board Performance Event List
Table 2-33 COA board performance event list
WCVMAX WCVMIN WCVAVG
CCVMAX CCVMIN CCVAVG
BCVMAX BCVMIN BCVAVG
EDTPLMAX EDTPLMIN EDTPLAVG
EDRPLMAX EDRPLMIN EDRPLAVG
EDWCSMAX EDWCSMIN EDWCSAVG
EDTMPMAX EDTMPMIN EDTMPCUR
BDTMPMAX BDTMPMIN BDTMPCUR
2.4.2 EFT0 Board Performance Event List
Table 2-34 EFT0 board performance event list
VC3BBE VC3ES VC3SES

VC3FEBBE VC3FEES VC3FESES
VC3UAS VC3CSES VC3FECSES
VC3FEUAS LPBBE LPES
LPSES LPUAS LPCSES
LPFEUAS LPFEBBE LPFEES
LPFESES LPFECSES TLBMAX
TLBMIN TLBCUR TPLMAX
TPLMIN TPLCUR RPLMAX
RPLMIN RPLCUR OSPITMPMAX
OSPITMPMIN OSPITMPCUR -
2.4.3 EFT8A Performance Event List
Table 2-35 EFT8A performance event list
VC3BBE VC3ES VC3SES
VC3FEBBE VC3FEES VC3FESES
VC3UAS VC3CSES VC3FECSES
VC3FEUAS LPBBE LPES
LPSES LPUAS LPCSES
LPFEUAS LPFEBBE LPFEES
LPFESES LPFECSES -
2.4.4 EFT8B Performance Event List
For the EFT8B board alarm list, see Table 2-34.
2.4.5 EMS1 Board Performance Event List
Table 2-36 EMS1 board performance event list
HPBBE HPES HPSES
HPFEBBE HPFEES HPFESES

HPUAS HPCSES HPFECSES
LPBBE LPES LPSES
LPUAS LPCSES LPFEBBE
LPFEES LPFESES LPFECSES
TLBMAX TLBMIN TLBCUR
TPLMAX TPLMIN TPLCUR
RPLMAX RPLMIN RPLCUR
OSPITMPMAX OSPITMPMIN OSPITMPCUR
2.4.6 PD3 Board Performance Event List
Table 2-37 PD3 board performance event list

LPBBE LPES LPSES
LPFEBBE LPFEES LPFESES
LPUAS LPCSES LPFECSES
LPFEUAS TUPJCLOW TUPJCHIGH
TUPJCNEW E3_LCV_SDH E3_LES_SDH
E3_LSES_SDH T3_LCV_SDH T3_LES_SDH
T3_LSES_SDH - -
2.4.7 PIU Board Performance Event List
Table 2-38 PIU board performance event list

2.4.8 PL1 Board Performance Event List

Table 2-39 PL1 board performance event list
LPBBE LPES LPSES
LPFEBBE LPFEES LPFESES
LPUAS LPCSES LPFECSES
LPFEUAS TUPJCLOW TUPJCHIGH
TUPJCNEW - -
2.4.9 PL1P Performance Event List

For the PL1P performance events, see Table 2-39.
2.4.10 PL3 Performance Event List

For the PL3 performance events, see Table 2-37.
2.4.11 PLM Performance Event List

For the PLM performance events, see Table 2-39.
2.4.12 PLMP Performance Event List

For the PLMP performance events, see Table 2-39.
2.4.13 PQ1 Performance Event List

For the PQ1 performance events, see Table 2-39.
2.4.14 PT1 Performance Event List

For the PT1 performance events, see Table 2-39.
2.4.15 PT1P Performance Event List

For the PT1P performance events, see Table 2-39.
2.4.16 SD1 Board Performance Event List
Table 2-40 SD1 board performance event list
RSBBE RSES RSSES
RSOFS RSUAS RSCSES

MSBBE MSES MSSES
MSFEBBE MSFEES MSFESES
MSUAS MSFEUAS MSCSES
MSFECSES AUPJCHIGH AUPJCLOW
AUPJCNEW HPBBE HPES
HPSES HPFEBBE HPFEES
HPFESES HPUAS HPFEUAS
HPCSES HPFECSES TLBMAX
OSPITMPMIN OSPITMPCUR -
2.4.17 SD4 Performance Event List

For the SD4 performance events, see Table 2-40.
2.4.18 SDE Board Performance Event List
Table 2-41 SDE board performance event list

RSBBE RSES RSSES
RSOFS RSUAS RSCSES
MSBBE MSES MSSES
AUPJCNEW HPBBE HPES
HPCSES HPFECSES -

2.4.19 SL1A Performance Event List

For the SL1A performance events, see Table 2-40.
2.4.20 SL4 Board Performance Event List
Table 2-42 SL4 board performance event list
RSBBE RSES RSSES
RSOFS RSUAS RSCSES
MSBBE MSES MSSES
AUPJCNEW HPBBE HPES
HPCSES HPFECSES TLBMAX
OSPITMPMIN OSPITMPCUR BDTMPMAX
BDTMPMIN BDTMPCUR -
2.4.21 SLM Performance Event List

For the SLM performance events, see Table 2-40.
2.4.22 SQ1 Performance Event List

For the SQ1 performance events, see Table 2-40.
2.4.23 XCS16 Performance Event List
Logical Board XCS Performance Event List

For the logical board XCS performance event list, see Table 2-38.

Logical Board OSB16 Performance Event List

For the logical board OSB16 performance event list, see Table 2-40.

Logical Board OSB1A Performance Event List

For the logical board OSB1A performance event list, see Table 2-40.

Logical Board OSB4A Performance Event List

For the logical board OSB4A performance event list, see Table 2-40.

Alarms and Performance Events Reference 3 Alarm Clearing
3 Alarm Clearing
About This Chapter
This part describes the procedure for handling the alarms.
CAUTION
The board removal and hard reset mentioned in the document interrupt services. If the services
that pass through the relevant board are unprotected, do not perform these operations unless
absolutely necessary.
NOTE
l This part lists the alarm parameters displayed on the T2000. When you view alarms on the T2000,
select an alarm. In the Alarm Details field, the related parameters of the alarm are displayed. The format
is "Alarm parameter (hex): Parameter 1, parameter 2…parameter N". For example, Parameter (hex):
0x01 0x08…
l If alarms persist, contact Huawei engineers for troubleshooting.
3.1 A_LOC
3.2 ALM_GFP_dCSF
3.3 ALM_GFP_dLFD
3.4 ALM_GFP_dSSF
3.5 APS_FAIL
3.6 APS_INDI
3.7 AU_AIS
3.8 AU_LOP
3.9 B1_EXC
3.10 B1_SD
3.11 B2_EXC

3 Alarm Clearing Alarms and Performance Events Reference
3.12 B2_SD
3.13 B3_EXC
3.14 B3_EXC_VC3
3.15 B3_SD
3.16 B3_SD_VC3
3.17 BD_STATUS
3.18 BIP_EXC
3.19 BIP_SD
3.20 BUS_ERR
3.21 BUS_LOC
3.22 COMMUN_FAIL
3.23 DBMS_ERROR
3.24 DN_E1AIS
3.25 E1_LOC
3.26 ETH_LOS
3.27 EXER_FAIL
3.28 EXT_SYNC_LOS
3.29 FCS_ERR
3.30 FLOW_OVER
3.31 FUSE_ALARM
3.32 HARD_BAD
3.33 HP_CROSSTR
3.34 HP_LOM
3.35 HP_RDI
3.36 HP_REI
3.37 HP_SLM
3.38 HP_TIM
3.39 HP_UNEQ
3.40 HPAD_CROSSTR
3.41 IN_PWR_ABN
3.42 INPWR_FAIL
3.43 J0_MM
3.44 K1_K2_M

3.45 K2_M
3.46 LASER_MOD_ERR
3.47 LCAS_FOPR
3.48 LCAS_FOPT
3.49 LCAS_PLCR
3.50 LCAS_PLCT
3.51 LCAS_TLCR
3.52 LCAS_TLCT
3.53 LOOP_ALM
3.54 LP_CROSSTR
3.55 LP_R_FIFO
3.56 LP_RDI
3.57 LP_RDI_VC12
3.58 LP_RDI_VC3
3.59 LP_REI
3.60 LP_REI_VC12
3.61 LP_REI_VC3
3.62 LP_RFI
3.63 LP_SIZE_ERR
3.64 LP_SLM
3.65 LP_SLM_VC12
3.66 LP_SLM_VC3
3.67 LP_T_FIFO
3.68 LP_TIM
3.69 LP_TIM_VC12
3.70 LP_TIM_VC3
3.71 LP_UNEQ
3.72 LP_UNEQ_VC12
3.73 LP_UNEQ_VC3
3.74 LPT_INEFFECT
3.75 LPT_RFI
3.76 LSR_NO_FITED
3.77 LSR_WILL_DIE

3.78 LTI
3.79 MAINBD_SUBBD_MISMATCH
3.80 MDL_ALARM
3.81 MSAD_CROSSTR
3.82 MS_AIS
3.83 MS_CROSSTR
3.84 MS_RDI
3.85 MS_REI
3.86 MSSW_DIFFRENT
3.87 NESTATE_INSTALL
3.88 NO_BD_SOFT
3.89 NO_LSR_PARA_FILE
3.90 NODEID_MM
3.91 OUT_PWR_ABN
3.92 OUTPWR_FAIL
3.93 P_AIS
3.94 P_LOS
3.95 PATCH_ERR
3.96 PATCH_NOT_CONFIRM
3.97 PATCHFILE_NOTEXIST
3.98 POWER_FAIL
3.99 PROTECT_MODE
3.100 PWR_MAJ_ALM
3.101 R_FIFO_E
3.102 R_LOC
3.103 R_LOF
3.104 R_LOS
3.105 R_OOF
3.106 RELAY_ALARM
3.107 RINGMAPM_MM
3.108 RS_CROSSTR
3.109 S1_SYN_CHANGE
3.110 SECU_ALM

3.111 SNCP_FAIL
3.112 SNCP_INDI
3.113 SQUTABM_MM
3.114 SYNC_C_LOS
3.115 SYNC_FAIL
3.116 SYN_BAD
3.117 T_ALOS
3.118 T_FIFO_E
3.119 T_LOC
3.120 T_LOS
3.121 TC_DEG
3.122 TC_EXC
3.123 TC_INCAIS
3.124 TC_LTC
3.125 TC_ODI
3.126 TC_OEI
3.127 TC_RDI
3.128 TC_REI
3.129 TC_TIM
3.130 TC_UNEQ
3.131 TEM_HA
3.132 TEM_LA
3.133 TEMP_ALARM
3.134 TF
3.135 TPS_FAIL
3.136 TPS_INDI
3.137 TU_AIS
3.138 TU_AIS_VC12
3.139 TU_AIS_VC3
3.140 TU_LOP
3.141 TU_LOP_VC12
3.142 TU_LOP_VC3
3.143 UP_E1AIS

3.144 VCAT_LOA
3.145 VCAT_LOM_VC12
3.146 VCAT_LOM_VC3
3.147 VCAT_SQM_VC12
3.148 VCAT_SQM_VC3
3.149 WRG_BD_TYPE
3.150 W_R_FAILURE

3.1 A_LOC
Description
The A_LOC is an alarm indicating that at the electrical interface of the tributary board, the
upstream BUS clock loses.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2 Indicates the path number (MSB).
Parameter 3 Indicates the path number (LSB).
Parameter 4 0xff (reserved)
Impact on System
When the A_LOC alarm occurs, it indicates that the clock of the tributary board is abnormal.
The lower order path services are unavailable.
Possible Causes
The possible causes of the A_LOC alarm are as follows:
l The clock in the transmitting signal of the interconnected equipment is lost.

l The receiving part of the board is faulty.
Handling Procedure
Step 1 Check whether the configuration of the interconnected equipment is correct. If yes, rectify the
fault of the interconnected equipment. View alarms on the T2000 to check whether the A_LOC
alarm is cleared.

If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
The alarm persists Proceed to the next step.
Step 2 The tributary board is faulty. Check whether the board is configured with the TPS protection.
If... Then...
The board is configured with the TPS Switch the services on the board to the
protection protection board. Then replace the faulty
board.
The board is not configured with the TPS Replace the faulty board.
protection
CAUTION
l Before replacing the tributary board, ensure that the new board is suitable.
l Replacing the tributary board without configuring the TPS protection will interrupt the board
services. This operation is risky.
----End
Related Information
None.
3.2 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating loss of the GFP client signal. When the source end
cannot receive the client signal, it sends the management frame to the sink end. The
ALM_GFP_dCSF is reported when the sink end receives the management frame.
Attribute
Critical Communication alarm
Parameters
table.

Name Meaning
Parameter 2 Indicates the VCTRUNK number (MSB).
Parameter 3 Indicates the VCTRUNK number (LSB).
Impact on System
During data service transmission, the source end cannot receive the client signal. As a result,
the services will lose packets or be interrupted.
Possible Causes
The possible causes of the ALM_GFP_dCSF alarm are as follows:
l The external port is disabled.

l The interface module is incorrect. For example, the optical module does not exist or match,
or the optical/electrical signal is lost.
l The physical link fails.
Handling Procedure
Step 1 View alarms on the T2000 to determine the relevant board. According to Parameter 2 and
Parameter 3, confirm the specific VCTRUNK number of the board
Step 2 Check on the T2000 whether the external port that corresponds to the VCTRUNK is set to
enabled. If not, set it to enabled. Then check whether the alarm is cleared.
If... Then...
Step 3 Check whether the TPS protection is configured.
If... Then...
The board is configured with the TPS Switch the services on the board to the
protection protection board. Then replace the faulty
board.
The board is not configured with the TPS Replace the faulty board.
protection
Step 4 If the alarm persists, check whether the optical module exists on the board.

If... Then...
The optical module does not exist Install the correct optical module. Then check whether
the alarm is cleared.
The optical module exists Check whether the optical module matches. If not,
replace the optical module with a correct one. Then check
whether the alarm is cleared.
Step 5 If the alarm persists, check whether the fiber is damaged. If yes, replace the fiber.
----End
Related Information
None.
3.3 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating GFP loss of frame delineation. When the
ALM_GFP_dLFD alarm occurs, it indicates that the GFP frame is in the out-of-frame state.
Attribute
Major Communication alarm
Parameters
table.
Name Meaning
Impact on System
During data transmission, the board failure in GFP frame alignment will interrupt the services.

Possible Causes
The possible causes of the ALM_GFP_dLFD alarm are as follows:
l The number of the uplink or downlink timeslots bound with the VCTRUNK at the local
station is inconsistent with the uplink or downlink timeslots bound with the corresponding
VCTRUNK at the opposite station.
l Bit errors occur in some timeslots bound with the VCTRUNK.
Handling Procedure
Parameter 3, confirm the specific VCTRUNK number of the board.
Step 2 Check on the T2000 whether the number of uplink or downlink timeslots bound with the
VCTRUNK at the local station is consistent with that of downlink or uplink timeslots bound
with the VCTRUNK at the opposite station. If not, increase or decrease the timeslots to make
the number of timeslots at both ends consistent. Then, check whether the alarm is cleared.
If... Then...
Step 3 Check whether there are the alarms such as BIP_EXC, BIP_SD, B3_EXC, and B3_SD in some
timeslot bound with the VCTRUNK. If yes, clear these alarms first. Then check whether the
alarm is cleared.
If... Then...
The alarm persists Contact Huawei engineers for troubleshooting.
----End
Related Information
None.
3.4 ALM_GFP_dSSF
Description
The ALM_GFP_dSSF is an alarm indicating the synchronous byte loss. The alarm indicates that
the detected GFP frame is in the out-of-frame state.
Attribute

Parameters
table.
Name Meaning
Impact on System
During the data transmission, the GFP synchronous byte loss will interrupt the services.
Possible Causes
The possible causes of the ALM_GFP_dSSF alarm are as follows:
l The number of the uplink or downlink timeslots bound with the VCTRUNK at the local
station is inconsistent with the uplink or downlink timeslots bound with the corresponding
VCTRUNK at the opposite station.
l Bit errors occur in some timeslots bound with the VCTRUNK.
Handling Procedure
Parameter 3, confirm the specific VCTRUNK number of the board.
Step 2 Check on the T2000 whether the number of uplink or downlink timeslots bound with the
VCTRUNK at the local station is consistent with that of downlink or uplink timeslots bound
with the VCTRUNK at the opposite station. If not, increase or decrease the timeslots to make
the number of timeslots at both ends consistent. Then, check whether the alarm is cleared.
If... Then...
Step 3 Check whether there are the alarms such as BIP_EXC, BIP_SD, B3_EXC, and B3_SD in some
timeslot bound with the VCTRUNK. If yes, clear these alarms first. Then check whether the
alarm is cleared.
If... Then...

If... Then...
----End
Related Information
None.
3.5 APS_FAIL
Description
The APS_FAIL is an alarm indicating APS protection switching failure.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
l 0x01: Linear MSP
l 0x02: Ring MSP
Parameter 2 Indicates the protection group ID.

Impact on System
When the APS_FAIL alarm occurs, it indicates that the MSP switching fails. Switching is
unavailable for the services under protection and the services will be interrupted.

Possible Causes
The possible causes of the APS_FAIL alarm are as follows:
l The MSP node configuration is incorrect. For example, the new/old protocol configured
on the node is inconsistent with that configured on the ring.
l The MSP node information is lost.
l The board is faulty.
Handling Procedure
Step 1 Check whether the current MSP parameters of the NEs on the ring are correct. If not, configure
them to correct. View alarms on the T2000 to check whether the APS_FAIL alarm is cleared.
If... Then...
Step 2 Replace the faulty board. After the board operates normally, view alarms on the T2000 to check
whether the APS_FAIL alarm is cleared.
If... Then...
CAUTION
l Before replacing the line board, ensure that the new board is suitable.
l Replacing the line board without configuring network protection, performing the cold reset,
or replacing the line board will interrupt the service. This operation is risky.
----End
Related Information
None.
3.6 APS_INDI
Description
The APS_INDI is an alarm indicating that the automatic MSP switching occurs.

Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
0x01: Linear MSP
0x02: Ring MSP

Impact on System
When the APS_INDI alarm occurs, the automatic protection switching or the switching triggered
by the external command occurs. The protected services are switched to the protection channel
for transmission.
The alarm does not affect the services. If the protection channel fails at this time, the services
are interrupted.
Possible Causes
The possible causes of the APS_INDI alarm are as follows:
l The alarm that triggers the MSP switching occurs.

l The external switching command is issued.
l The attributes of the MSP group are incorrectly configured.
Handling Procedure
Step 1 Check whether the alarms that cause the MSP switching occur on the local and opposite NEs.
If yes, handle these alarms first.

If... Then...
There is the R_LOS, R_LOF, MS_AIS, or See the corresponding section in this document
B2_EXC alarm to clear the alarm.
There is the B2_SD alarm Disable the SD switching if it is enabled, or see
the corresponding section in this document to
clear the B2_SD alarm.
There are no alarms mentioned above Proceed to the next step.
Step 2 Check whether the external switching command for the protection group is issued. If yes, cancel
the issued external switching command. View alarms on the T2000 to check whether the
APS_INDI alarm is cleared.
If... Then...
Step 3 Check whether the NE configuration is incorrect. Issue the MSP configuration again. View
alarms on the T2000 to check whether the APS_INDI alarm is cleared.
If... Then...
Step 4 If the service configuration is correct and the alarm persists, replace the SCC board.
CAUTION
l Before replacing the SCC board, ensure that the new board is suitable.
l When the 1+1 protection of the SCC board is configured, replacing the faulty SCC board
will not affect the services.
l When the 1+1 protection of the SCC board is not configured, in the process of replacing
boards, the communication between the T2000 and the NE is interrupted, and various
protection switching cannot be performed. As a result, the service will be interrupted.
l After replacing the SCC board, ensure that the ID and IP are consistent with that of the old
board.
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.82 MS_AIS
l 3.11 B2_EXC
l 3.12 B2_SD

3.7 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
Parameters
table.
Name Meaning
Parameter 1 Indicates the optical interface number.
Impact on System
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.
l The service is incorrectly configured.
l The opposite station sends the AU_AIS alarm.
l The transmit part at the opposite station is faulty.
l The receive part of the local station is faulty.

Handling Procedure
Step 1 Check whether section-level alarms occur 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.
If... Then...
There is the R_LOS, R_LOF, R_LOC, or See the corresponding section in this document
MS_AIS alarm on the line board of the to clear the alarm.
upstream station
There is no alarms mentioned above 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.
If... Then...
The transmit end of the line board at the opposite Cancel the inserted AU_AIS alarm.
station is inserted with the AU_AIS alarm
The transmit end of the line board at the opposite Proceed to the next step.
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 T2000 to check whether the AU_AIS alarm is cleared.
If... Then...
Step 5 Check whether the transmit part of the line board at the opposite station is faulty.
If... Then...
The line board of the opposite station is Perform a reset on the board or replace the
faulty board. Then check whether the alarm is
cleared.
The transmit part of the line board at the Proceed to the next step.
opposite station is normal
Step 6 Check the line board of the local station. Perform a reset on the board or replace the board. Then
check whether the alarm is cleared.
CAUTION
----End

Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.102 R_LOC
l 3.82 MS_AIS
3.8 AU_LOP
Description
The AU_LOP is an alarm indicating loss of the AU pointer in the signal received by the line
board.
Attribute
Parameters
table.
Name Meaning
Impact on System
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 transmit part of the opposite station is faulty, or the cross-connect and timing board is
faulty.
l The service at the opposite station is incorrectly configured.
l The bit errors received at the local station are excessive.
Handling Procedure
Step 1 View alarms on the T2000 and check whether there are other section-level bit error alarms on
the board that reports the AU_LOP alarm.
If... Then...
There is the B1_EXC, B1_SD, B2_EXC, See the corresponding section to clear the alarm.
or B2_SD alarm
There are no such alarms as B1_EXC, Proceed to the next step.
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 T2000 to check
whether the AU_LOP alarm is cleared.
If... Then...
Step 4 Check whether the cross-connect and timing board of the opposite station operates normally. If
not, replace the faulty board.
CAUTION
l Before replacing the cross-connect and timing board, ensure that the new board is suitable.
l If the cross-connect and timing board is not configured with 1+1 backup, performing a reset
on the board or replacing the board will interrupt services. The operation is risky.
l The cross-connect and timing board is integrated with the line function. Replacing the cross-
connect and timing board without configuring network-level protection will interrupt the
services .The operation is risky.
Step 5 After replacing the cross-connect and timing board of the opposite end, view alarms on the T2000
to check whether the AU_LOP alarm is cleared.
If... Then...
Step 6 Perform a loopback for the stations at both ends of the line. Locate and replace the faulty line
board.

CAUTION
----End
Related Information
None.
3.9 B1_EXC
Description
The B1_EXC is an alarm indicating that the regenerator section B1 bit errors in the signals
received by the line board crosses the threshold.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 2 Indicates the path number. The value is always 0x00.
Impact on System
When the B1_EXC occurs, it indicates that the number of the regenerator section B1 bit errors
in the signals received at the optical interface crosses the threshold. The services on the optical
interface are unavailable.

When the B1_EXC occurs, by default, the system inserts the AU_AIS alarm in the cross-
connection direction.
Possible Causes
The possible causes of the B1_EXC alarm are as follows:
l The received signals are attenuated to a great extent.
l The fiber head is not clean or the connector is incorrect.
l The transmit part of the opposite station is faulty.
Handling Procedure
Step 1 Check whether the fiber is intact and the optical connector is clean.
If... Then...
The fiber is intact and the optical connector Proceed to the next step.
is clean
The fiber is broken or the optical connector Replace the fiber or clean the fiber head with
is not clean alcohol. If the alarm persists, proceed to the
next step.
Step 2 View alarms on the T2000 and check whether the TEMP_ALARM alarm occurs on any board
of the reporting equipment.
If... Then...
There is the TEMP_ALARM alarm See the procedure in TEMP_ALARM.If the
B1_EXC alarm persists after the TEMP_ALARM
alarm is cleared, proceed to the next step.
There is not the TEMP_ALARM alarm Proceed to the next step.
Step 3 Query whether relevant alarms occur at the opposite station.
If... Then...
There are relevant alarms Clear these alarms first. If the B1_EXC alarm persists after
the TEMP_ALARM alarm is cleared, proceed to the next
step.
There are no relevant alarms Proceed to the next step.
Step 4 Perform a selfloop at the local station. If bit errors are cleared, it indicates that the line board of
the opposite station is faulty. Replace the faulty board. If bit errors persist, it indicates that the
line board of the local station is faulty. Replace the faulty board.

CAUTION
----End
Related Information
3.133 TEMP_ALARM
3.10 B1_SD
Description
The B1_EXC is an alarm indicating that the B1 signals received by the line are degraded.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the B1_SD alarm occurs, it indicates that the regenerator section B1 bit errors in the signals
received at the optical interface are excessive. The services on the optical interface are affected.

Possible Causes
The possible causes of the B1_SD alarm are as follows:
Handling Procedure
If... Then...
The fiber is broken or the optical connector Replace the fiber or clean the optical
is not clean connector with alcohol. If the alarm persists,
proceed to the next step.
is clean
Step 2 Check whether the clock source at the local station is correctly configured. If not, modify it to
correct or set the synchronous clock source again. Then view alarms on the T2000 to check
whether the B1_SD alarm is cleared.
If... Then...
If... Then...
There is the TEMP_ALARM alarm See the procedure in TEMP_ALARM.If the
Step 4 Perform a selfloop at the local station. If bit errors are cleared, it indicates that the line board of
the opposite station is faulty. Replace the faulty board. If bit errors persist, it indicates that the
line board of the local station is faulty. Replace the faulty board.
CAUTION
----End

Related Information
3.133 TEMP_ALARM
3.11 B2_EXC
Description
The B2_EXC is an alarm indicating that the multiplex section B2 bit errors in the signals received
by the line crosses the threshold.
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Impact on System
When the B2_EXC occurs, it indicates that the number of multiplex section B2 bit errors in the
signals received by the line crosses the threshold. The services of the optical interface are
unavailable. If the MSP is configured, this alarm will trigger the SF switching.
When the B2_EXC alarm occurs, the system inserts the AU_AIS alarm to the cross-connection
direction and places the number of B2 bit errors into the M1 byte. The MS_REI alarm will be
received by the opposite end.
Possible Causes
l The B2_EXC alarm is caused by B1 bit errors.


Handling Procedure
Step 1 Check whether there are B1 bit errors on the line board that reports the alarm.
If... Then...
There is the B1_EXC or B1_SD alarm See the corresponding section in this document
to clear the alarm.
There are not such alarms as the B1_EXC Proceed to the next step.
and B1_SD
If... Then...
is clean
whether the B2_EXC alarm is cleared.
If... Then...
If... Then...
There is the TEMP_ALARM alarm See the procedure in TEMP_ALARM. If the
Step 5 Perform a selfloop at the local station. If bit errors are eliminated, it indicates that the opposite
line board is faulty. Replace the faulty board. If bit errors increase, it indicates that the local line
board is faulty. Replace the faulty board.

CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
3.12 B2_SD
Description
The B2_SD is an alarm indicating that the multiplex section B2 signals received by the line are
degraded.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the B2_SD alarm occurs, it indicates that the multiplex section bit errors in the signals
received at the optical interface are excessive. The services on the optical interface are affected.

If multiplex section automatic protection switching is configured and the SD switching function
is enabled, this alarm will trigger the SD switching.
When the B2_SD alarm occurs, the system inserts the AU_AIS alarm to the cross-connect
direction and places the number of bit errors into the M1 byte. The MS_REI and MS_RDI alarms
will be received by the opposite end.
Possible Causes

l There is the B1_EXC or B1_SD alarm.
Handling Procedure
If... Then...
to clear the alarm.
and B1_SD
If... Then...
is clean
whether the B2_SD alarm is cleared.
If... Then...

If... Then...
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
3.13 B3_EXC
Description
The B3_EXC is an alarm indicating that the B3 bit errors in the signals received by the line
crosses the threshold.
Attribute

Major Service alarm
Parameters
table.

Name Meaning
Impact on System
If the alarm occurs, it indicates that the number of bit errors (high order B3 bit errors of line
boards or low order B3 bit errors of E3/T3 tributary board) is excessive and crosses the
performance threshold. If the line board is configured with higher order SNCP and the higher
order path bit error threshold-crossing switching is enabled, the B3_EXC alarm will trigger the
bit error threshold-crossing switching.
When the alarm occurs, the board will insert AIS (TU_AIS for tributary services) into the
corresponding path and send the HP_RDI alarm to the opposite end.
Possible Causes
l There are B1 or B2 bit errors.
Handling Procedure
Step 1 Check whether B1 or B2 bit errors occur on the reporting line board.
If... Then...
There is the B1_EXC, B1_SD, B2_EXC, See the corresponding section in this document
or B2_SD alarm to clear the alarm.
If... Then...
is clean

If... Then...
Step 4 Check whether the service configuration is correct. For example, for the lower order services
from the opposite end is configured as pass-through, if the service configuration is incorrect,
modify or re-issue the configuration. View alarms on the T2000 to check whether the B3_EXC
alarm is cleared.
If... Then...
Step 5 Perform a loopback for the stations at two ends of the line. Locate the faulty board.
If... Then...
The B3 bit error performance event is The transmit end of the board at the opposite
reported on the opposite board station is faulty. Replace the faulty board.
The B3 bit error performance event is The receive end of the board at the local
reported on the local board station is faulty. Replace the faulty board.
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
3.14 B3_EXC_VC3

Description
The B3_EXC_VC3 is an alarm indicating that the number of B3 bit errors in the lower order
path VC-3 crosses the threshold. If a board has detected that the number of B3 bit errors exceeds
the specified threshold value (default value: 10-3), the B3_EXC_VC3 alarm is reported.
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Parameter 2 Indicates the VC3 path number (MSB).
Parameter 3 Indicates the VC3 path number (LSB).
Impact on System
When the B3_EXC_VC3 alarm occurs, a large number of bit errors occur in the VC-3 service.
Possible Causes
The possible causes of the B3_EXC_VC3 alarm are as follows:
l Higher-level bit error alarms occur in the system.
l The fiber connector is not clean.
l The fiber connector is loose.
l The transmit part at the opposite station is faulty.
Handling Procedure
Step 1 Check whether any higher-level alarms, such as B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC,
or B3_SD, is detected at the local station and at the upstream station. If yes, clear these alarms
first. Then check whether the B3_EXC_VC3 alarm is cleared.

If... Then...
Step 2 Check whether the received optical power of the reporting board is within the specified value
range.
If... Then...
The received optical power is abnormal Do as follows:
l Insert the fiber connector firmly. Then check
l Check whether the attenuation value of the
optical attenuator is proper. If not, adjust it to a
proper value. Then check whether the alarm is
cleared.
l Clean the fiber connector at the local station
and the receive optical interface on the line
board. Then check whether the alarm is cleared.
l Check whether the flange is correctly
connected to the optical attenuator at the local
station, and whether the attenuation value of the
optical attenuator is proper. After making sure
that the flange and optical attenuator are used
properly, check whether the alarm is cleared.
l Check whether the launched optical power at
the opposite station is within the specified value
range.
l If the launched optical power is beyond the
specified value range, replace the optical
module. Then check whether the alarm is
cleared. If not, replace the line board at the
opposite end. Then check whether the alarm is
cleared.
l If the launched optical power is within the
specified value range, clean the fiber connector
at the remote station. Then check whether the
alarm is cleared.
The received optical power is normal Proceed to the next step.
Step 3 Replace the reporting board.

CAUTION
----End
Related Information
None.
3.15 B3_SD
Description
The B3_SD is an alarm indicating that the higher order path (B3) signals received by the line
are degraded.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
If the alarm occurs, it indicates that serious higher order path bit errors exist. The bit errors will
affect the service of the path. If higher order SNCP is configured and the B3SD switching
function is enabled, this alarm will trigger the B3SD switching.

When the B3_EXC alarm occurs, the board will insert AIS (TU_AIS for tributary services) into
the corresponding path and send the HP_REI alarm to the opposite end.
Possible Causes

l The higher-level alarms such as B1 and B2 occur at the local station.
Handling Procedure
Step 1 Check whether B1 or B2 bit errors occur on the reporting line board.
If... Then...
If... Then...
is clean
If... Then...
Step 4 Check whether the service configuration is correct. For example, whether the lower order
services from the opposite end is configured as pass-through, if the service configuration is
incorrect, modify or re-issue the configuration. View alarms on the T2000 to check whether the
B3_SD alarm is cleared.
If... Then...

If... Then...
If... Then...
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.133 TEMP_ALARM
3.16 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the B3 bit errors in the lower order path VC-3 are
degraded. If a board has detected that the number of B3 bit errors exceeds the specified
B3_SD_VC3 alarm threshold value (default value: 10-6), the B3_SD_VC3 alarm is reported.
Attribute
Minor Service alarm
Parameters


table.
Name Meaning
Impact on System
When the B3_SD_VC3 alarm occurs, the service transmission quality in the VC-3 service
channel is degraded.
Possible Causes
The possible causes of the B3_SD_VC3 alarm are as follows:
l Higher-level bit alarms occur in the system.
l The receive part at the opposite station is faulty.
l The transmit part at the local station is faulty.
Handling Procedure
Step 1 Check whether any higher-level alarm, such as B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC,
or B3_SD, is detected at the local station and at the upstream station. If yes, clear these alarms
first. Then check whether the B3_EXC_VC3 alarm is cleared.
If... Then...
Step 2 Check whether the received optical power of the reporting board is within the specified value
range.

If... Then...
The received optical power is abnormal Do as follows:
l Insert the fiber connector firmly. Then check
l Check whether the attenuation value of the
optical attenuator is proper. If not, adjust it to a
proper value. Then check whether the alarm is
cleared.
l Clean the fiber connector at the local station
and the receive optical interface on the line
board. Then check whether the alarm is cleared.
l Check whether the flange is correctly
connected to the optical attenuator at the local
station, and whether the attenuation value of the
optical attenuator is proper. After making sure
that the flange and optical attenuator are used
properly, check whether the alarm is cleared.
l Check whether the launched optical power at
the opposite station is within the specified value
range.
l If the launched optical power is beyond the
specified value range, replace the optical
module. Then check whether the alarm is
cleared. If not, replace the line board at the
opposite end. Then check whether the alarm is
cleared.
l If the launched optical power is within the
specified value range, clean the fiber connector
at the remote station. Then check whether the
alarm is cleared.
The received optical power is normal Proceed to the next step.
Step 3 Check whether the board hardware at the local station and the upstream station is faulty. If yes,
replace the faulty board.
CAUTION
----End
Related Information
None.

3.17 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board of which the logical board created in the
system is offline.
Attribute

Parameters
table.
Name Meaning
Impact on System
When the BD_STATUS occurs, it indicates that the corresponding physical board is offline. As
a result, the functions of the board are unavailable.
Possible Causes
The possible causes of the BD_STATUS alarm are as follows:
l The board is not physically installed.

l The board is installed but poorly connected.
l The board is reset.
l The NE subrack is faulty.

Handling Procedure
Step 1 Check the alarms reported by the NE. Check whether the board is correctly seated in the slot of
the NE.
If... Then...
The board is not physically installed Properly install the board into the corresponding slot
of the NE.
The board is improperly installed Properly reinstall the board into the corresponding
slot of the NE.
The board is correctly installed Proceed to the next step.
Step 2 View alarms on the T2000 to check whether the BD_STATUS alarm is cleared.
If... Then...
Step 3 The board is faulty. Replace the faulty board. After the board operates normally, view alarms
on the T2000 to check whether the BD_STATUS alarm is cleared.
If... Then...
Step 4 The NE subrack is faulty. Replace the NE subrack.
CAUTION
Performing a power-off reset on the NE subrack or replacing the NE subrack will interrupt all
the services on the NE. The operation is risky.
----End
Related Information
None.
3.18 BIP_EXC
Description
The BIP_EXC is an alarm indicating that the number of lower order path BIP2 bit errors on the
tributary board or Ethernet board exceeds the threshold.

Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the BIP_EXC alarm occurs, it indicates that a large number of lower order path bit errors
(BIP_EXC) occur. The services over the path will be affected. The system will send the LP_REI
alarm to the opposite end.
Possible Causes
The possible causes of the BIP_EXC alarm are as follows:
l The section-level or higher order bit errors occur.
l The bit errors in lower order services are excessive.
l The cross-connect board is faulty.
Handling Procedure
Step 1 Check whether there are section-level or higher order bit errors on the line board that accesses
the services.
If... Then...
B2_SD, B3_EXC, or B3_SD alarm to clear the alarm.
There are not B1_EXC, B1_SD, B2_EXC, Proceed to the next step.
B2_SD, B3_EXC, or B3_SD alarm.
Step 2 Check whether the equipment interconnected with the board at the remote end transmits
excessive bit errors. Perform an outloop on the electrical interface (on the corresponding access

board) of the board. Check whether the interconnected equipment reports bit errors. If yes,
remove the fault of the interconnected equipment. View alarms on the T2000 to check whether
the BIP_EXC alarm is cleared.
If... Then...
Step 3 Perform a loopback on the optical interface for the stations at both ends of the line. Locate the
faulty board.
If... Then...
The BIP bit error performance event is The transmit end of the board at the opposite
The BIP bit error performance event is The receive end of the board at the local
CAUTION
l Before replacing the board, ensure that the new board is suitable.
l Replacing the tributary board or Ethernet board without configuring the TPS protection will
interrupt the board services. This operation is risky.
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC
l 3.15 B3_SD
3.19 BIP_SD
Description
The BIP_SD is an alarm indicating that the lower order signals (BIP2) on the tributary board or
Ethernet board are degraded.

Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the BIP_SD alarm occurs, it indicates that a large number of lower order path bit errors
(BIP) occur. The services over the path will be affected. If lower order SNCP protection
switching is configured and lower order bit error threshold-crossing (BIP_SD) switching is
enabled, this alarm will trigger the lower order bit error threshold-crossing switching.
When the alarm occurs, the system will send the LP_REI alarm to the opposite end.
Possible Causes
The possible causes of the BIP_SD alarm are as follows:
l The higher order bit errors occur.
l The BIP2 bit errors in lower order services are excessive.
Handling Procedure
Step 1 Check whether there are section-level or higher order bit errors on the line board that accesses
the services.
If... Then...
There is not the B1_EXC, B1_SD, Proceed to the next step.
B2_EXC, B2_SD, B3_EXC, and B3_SD
alarm.

Step 2 Check whether the interconnected equipment of the board at the remote end transmits excessive
bit errors. Perform an outloop on the electrical interface of the board. Check whether the
interconnected equipment reports bit errors. If yes, remove the fault of the interconnected
equipment. View alarms on the T2000 to check whether the BIP_EXC alarm is cleared.
If... Then...
Step 3 Perform a loopback on the optical interface for the stations at both ends of the line. Locate the
faulty board.
If... Then...
The BIP bit error performance event is The transmit end of the board at the opposite
The BIP bit error performance event is The receive end of the board at the local
CAUTION
l Before replacing the board, ensure that the new board is suitable.
l Replacing the tributary board or Ethernet board without configuring the TPS protection will
interrupt the board services. This operation is risky.
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC
l 3.15 B3_SD
3.20 BUS_ERR
Description
The BUS_ERR is an alarm indicating that the service bus from the service board to the cross-
connect board is faulty or the service bus from the cross-connect board to the service board is
faulty.

Attribute

Critical Equipment alarm
Parameters
table.
Name Meaning
Parameter 3 In the case of the line board:
l 0x01-0x04: Indicates the downlink service bus number of the cross-connect

board in slot 7.
l 0x05-0x08: Indicates the downlink service bus number of the cross-connect
board in slot 8.
In the case of the tributary boards, the value is always 0x01.
In the case of the cross-connect board: Indicates the bus number.
Parameter 4 In the case of the tributary board:
l 1: Indicates the downlink service bus number of the cross-connect board in

slot 7.
l 2: Indicates the downlink service bus number of the cross-connect board in
slot 8.
Other boards: The value is always 0xff, and this parameter is unused.
Impact on System
When the BUS_ERR alarm occurs, it indicates that the uplink or downlink service signal is
faulty. As a result, the services are unavailable.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows:
l The service board is faulty.

l The cross-connect and timing board is faulty.

l When a service board is physically offline but logically configured, services are configured
between the board and another service board that operates normally.
Handling Procedure
Step 1 Check the service configuration. Check whether any board is physically offline among the boards
that are configured with services.
If... Then...
There is such a board Modify the service configuration. Then check whether the alarm
is cleared. If the alarm is cleared, end the alarm handling.
Otherwise, proceed to the next step.
There is not such a board. Proceed to the next step.
Step 2 The service board is faulty. Replace the faulty board. After the board operates normally, view
alarms on the T2000 to check whether the BUS_ERR alarm is cleared.
If... Then...
CAUTION
l Before replacing the service board, ensure that the new board is suitable.
l Replacing the service board without configuring the protection will interrupt all services of
the board. The operation is risky.
Step 3 If the equipment is configured with two cross-connect and timing boards, switch the services to
the standby cross-connect and timing board. If the equipment is configured with only one cross-
connect and timing board, install another cross-connect and timing board. After the installed
board operates, switch the services to the board so that it functions as the active board. View
alarms on the T2000 to check whether the alarm is cleared.
If... Then...

CAUTION
services. The operation is risky.
----End
Related Information
None.
3.21 BUS_LOC
Description
The BUS_LOC is an alarm indicating the loss of clock in the downlink bus on the tributary
board.
Attribute

Parameters
table.
Name Meaning

Impact on System
When the BUS_LOC alarm occurs, it indicates that the clock of the downlink bus on the tributary
board is lost. As a result, the services are unavailable.
Possible Causes
The possible causes of the BUS_LOC alarm are as follows:
l The tributary board is faulty.

Handling Procedure
Step 1 Perform a rest on, or remove and insert the tributary board. After the board operates normally,
view alarms on the T2000 to check whether the BUS_LOC alarm is cleared.
If... Then...
Step 2 The tributary board is faulty. Replace the faulty board. After the board operates normally, view
alarms on the T2000 to check whether the BUS_LOC alarm is cleared.
If... Then...
CAUTION
the standby cross-connect and timing board. View alarms on the T2000 to check whether the
alarm is cleared.
If... Then...
The alarm is cleared The original active cross-connect and timing board is faulty. Replace
the faulty board. The fault is rectified. End the alarm handling.
Step 4 If the equipment is configured with only one cross-connect and timing board, replace the board.
After the board operates normally, view alarms on the T2000 to check whether the BUS_LOC
alarm is cleared.

If... Then...
CAUTION
----End
Related Information
None.
3.22 COMMUN_FAIL
Description
The COMMUN_FAIL is an alarm indicating that the serial port or common mailbox
communication fails between the cross-connect and timing board and the SCC board, between
the EMS1 board and SCC board, or between the active and standby SCC boards.
Attribute
Parameters
table.

Name Meaning
Parameter 1 l 0x01: The communication between the cross-connect and timing board and
the SCC board or the communication between the EMS1 and the SCC board
fails.
l 0x0c or 0x0d: The communication between the active SCC board and the
standby SCC board fails.
Parameter 2 0x00
Parameter 3 l 0x0a: The common mailbox communication fails.
l 0x0b: The serial port communication fails.
l 0x01: The communication between the active SCC board and the standby SCC
board fails.
Impact on System
l If the serial port communication fails, the protection switching function of the system or
the board fails.
l If the common mailbox communication fails, the services cannot be configured and the
cross-connect board or the EMS1 board cannot respond to the commands from the NE
software.
l If the communication between the active SCC board and the standby SCC board fails, the
SCC boards cannot perform 1+1 backup.
Possible Causes
The possible causes of the COMMUN_FAIL alarm are as follows:
l The serial port circuit between the cross-connect and timing board and the SCC board or
between the EMS1 board and the SCC board is faulty.
l The common mailbox circuit is faulty between the cross-connect and timing board and the
SCC board or between the EMS1 board and the SCC board.
l The software of the cross-connect and timing board or the EMS1 board is faulty. The board
enters the BIOS state.
l The serial port circuit between the cross-connect and timing board or between the EMS1
board and the SCC board is faulty.
l The SCC board is faulty, which causes the anomaly of mailbox communication protocol.
l The standby SCC board already starts to work, but the board software is initializing.
l The Ethernet communication between the active SCC board and the standby SCC board is
abnormal.
l The mailbox communication between the active SCC board and the standby SCC board is
abnormal.

Handling Procedure
Step 1 Determine the fault type through the board that reports the alarm.
If... Then...
The cross-connect board reports the The communication between the cross-connect
alarm board and the SCC board fails. See steps 2-4.
The EMS1 board reports the alarm The communication between the EMS1 board and
the SCC board fails. See steps 5-6.
The SCC board reports the alarm The communication between the active SCC
board and the standby SCC board fails. See steps
7-9.
Step 2 Query the type of the cross-connect and timing board by using the T2000 command.
If... Then...
If the board type is null The cross-connect and timing board is faulty. Go to step 3.
If the board type is correct Proceed to the next step.
Step 3 If the equipment is configured with two cross-connect and timing boards and they report the
COMMUN_FAIL alarm at the same time, the SCC board is faulty. Replace the SCC board.
After the board operates normally, view alarms on the T2000 to check whether the
COMMUN_FAIL alarm is cleared. If the equipment is configured with only one cross-connect
and timing board, proceed with step 4.
If... Then...
Step 4 Replace the reporting cross-connect board. After the board operates normally, view alarms on
the T2000 to check whether the alarm is cleared.
If... Then...
CAUTION
Step 5 Query the type of the EMS1 board through the T2000 command.

If... Then...
If the board type is null The EMS1 board is faulty. Go to step 6.
If the board type is correct Proceed to the next step.
Step 6 Replace the EMS1 board reporting the alarm with a new EMS1 board. After the board operates
normally, view alarms on the T2000 to check whether the OUTPWR_FAIL alarm is cleared.
If... Then...
Step 7 Check whether the standby board operates normally through the indicator. If the board is
initializing, the alarm will end when the standby board is initialized.
If... Then...
The alarm is cleared End the alarm handling.
The standby board is working normally but the alarm persists Proceed to the next step.
Step 8 Reset the standby board. After the standby board restarts, the alarm should end. If the alarm
persists, replace the standby SCC board with another SCC board. After the replacement, if the
alarm ends, the former standby SCC board is faulty. In this case, replace the faulty SCC board.
If the alarm persists, proceed to the next step.
Step 9 If the communication between the active SCC board and other service boards is normal, check
the Ethernet communication between the active SCC board and the standby SCC board. If the
ping request between the two SCC boards times out, contact Huawei engineers for
troubleshooting.
----End
Related Information
None.
3.23 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the processing of the system
database.
Attribute

Major Processing alarm

Parameters
table.
Name Meaning
Parameter 1 The lowest byte of the alarm information:
l 0x01: The input parameters are illegal.

l 0x02: The database files do not exist.
l 0x03: The database memory area numbers are incorrect.
l 0x04: The database overwriting occurs.
l 0x05: Errors occur in the header information check in the database backup
area.
l 0x06: Errors occur in the FAT table structure check in the database memory
area.
l 0x07: Errors occur in the database check in the database backup area.
l 0x08: Recovering the database fails.
l 0x09: The database ID is invalid.
l 0x0A: The databases are different.
l 0x0B: The data is unchecked.
l 0x0E: The semaphore handle is invalid.
l 0x0F: Errors occur in memory applying.
l 0x10: Errors occur in memory releasing.
l 0x12: Transmitting the message packet fails.
l 0x13: The start/end record is incorrect.
l 0x14: The database is null.
l 0x15: The mark is incorrectly set.
l 0x16: The input command parameters are incorrect.
l 0x17: This is a not backup database.
l 0x18: The database is in the protection mode.
l 0x19: The configuration is not verified.
Parameter 2 Database memory area:
l 0x00 (fdb0)
l 0x00 (fdb1)
l 0x02 (drdb)

Name Meaning
Parameter 3 Indicates the database ID, presently the value range is 0-255.
l 0: The whole storage area errors.

l The number in 1-255 indicates the specific database that errors.

Impact on System
When the DBMS_ERROR alarm occurs, it indicates that errors occur in the system database
processing. The system configuration may be lost. As a result, the failure indication is returned
for some query and setting commands, and some system functions cannot work.
Possible Causes
The possible causes of the DBMS_ERROR alarm are as follows:
l The database operation fails.
l The data in the database is damaged.
l The SCC board is faulty.
Handling Procedure
Step 1 Turn the DIP switches 2 and 4 on the SCC board to OFF. Perform a warm reset on the NE. After
the NE enters the BIOS state, erase the original database. Then turn the DIP switches 2 and 4
back to the original state. Perform another warm reset on the NE. View alarms on the T2000 to
check whether the DBMS_ERROR alarm is cleared.
If... Then...
Step 2 If the alarm persists, replace the SCC board.

CAUTION
board.
----End
Related Information
None.
3.24 DN_E1AIS
Description
The DN_E1AIS is a 2M downlink signal alarm indication. When the 2M downlink signal is all
"1"s, the DN_E1AIS alarm is reported.
Attribute
Minor Communication alarm
Parameters
table.
Name Meaning

Impact on System
When the DN_E1AIS alarm occurs, the downlink E1 signal is all 1s. Consequently, the output
services are unavailable.
Possible Causes
The possible causes of the DN_E1AIS alarm are as follows:
l The higher-level alarms occur in the upstream services.
l There the alarms such as BUS_LOC, LP_TIM, and LP_SLM on the tributary board. In
addition, the AIS inserting function is enabled.
Handling Procedure
Step 1 Check whether the services are correctly configured.
If... Then...
The service configuration is incorrect Configure the services properly. Then check
whether the alarm is cleared. If not, proceed to the
next step.
The service configuration is correct Proceed to the next step.
Step 2 Check whether there are the alarms such as BUS_LOC, LP_TIM, and LP_SLM on the board
and whether the AIS inserting function is enabled.
If... Then...
There is the BUS_LOC, LP_TIM, or Clear these alarms first and disable the AIS
LP_SLM alarm and the AIS inserting inserting function. Then check whether the
function is enabled DN_E1AIS alarm is cleared. If not, proceed to
the next step.
There is no alarm such as BUS_LOC, Proceed to the next step.
LP_TIM, or LP_SLM
Step 3 Replace the board. Then check whether the alarm is cleared.
If... Then...
Step 4 Check whether higher-level bit error alarms such as R_LOS, R_LOC, R_LOF, MS_AIS,
AU_AIS, and AU_LOP are detected in the upstream service.

If... Then...
There is the R_LOS, R_LOC, R_LOF, First clear these alarms. Clean the fiber heads
MS_AIS, AU_AIS or AU_LOP alarm and ensure that the fiber connectors are firmly
inserted. Then check whether the alarm is
cleared. If not, proceed to the next step.
There is not the R_LOS, R_LOC, R_LOF, Go to step 6.
MS_AIS, AU_AIS, or AU_LOP alarm
Step 5 Replace the line board that reports the DN_E1AIS alarm at the source end. Check whether the
DN_E1AIS alarm is cleared.
If... Then...
alarm is cleared.
If... Then...
After the board operates normally, view alarms on the T2000 to check whether the BUS_LOC
alarm is cleared.
If... Then...

CAUTION
l In the case of the cross-connect and timing board:
l If the cross-connect and timing board is not configured with 1+1 backup, performing a
reset on the board or replacing the board will interrupt services. The operation is risky.
l The cross-connect and timing board is integrated with the line function. Replacing the
cross-connect and timing board without configuring network-level protection will
interrupt the services. The operation is risky.
l In the case of the line board:
l Replacing the line board without configuring network protection, performing the cold
reset, or replacing the line board will interrupt the service. This operation is risky.
----End
Related Information
None.
3.25 E1_LOC
Description
The E1_LOC is an alarm indicating the loss of clock in the uplink E1 service on the E1 tributary
board.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
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:
l The upstream equipment is faulty, which causes problems to the clock signal accessed by
the E1 interface.
Handling Procedure
Step 1 Check whether the service transmitting of the interconnected equipment is faulty. Perform an
outloop on the electrical interface of the board. Check whether the equipment reports bit errors.
Remove the fault of the interconnected equipment. View alarms on the T2000 to check whether
the E1_LOC alarm is cleared.
If... Then...
Step 2 Check the reporting board at the local station and reset the board.
If... Then...
Step 3 Replace the board.
CAUTION
Performing a cold reset on the board, or replacing the board will interrupt services. The operation
is risky.
----End
Related Information
None.

3.26 ETH_LOS
Description
The ETH_LOS is an alarm indicating loss of network port connection on the data board.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Port Number
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the ETH_LOS alarm occurs, it indicates that the network port of the data board is faulty.
As a result, the services are unavailable.
Possible Causes
The possible causes of the ETH_LOS alarm are as follows:
l The connecting cable or fiber is faulty.

l The interface board is faulty.
l The processing board is faulty.
Handling Procedure
Step 1 Check whether the cable or fiber connection of the network port is abnormal, whether the
connector is loose, and whether the cable or fiber break occurs. If yes, remove the fault of the
cable or fiber. View alarms on the T2000 to check whether the ETH_LOS alarm is cleared.

If... Then...
Step 2 Replace the interface board. View alarms on the T2000 to check whether the ETH_LOS alarm
is cleared.
If... Then...
CAUTION
Performing a cold reset on the board, or replacing the board will interrupt services. The operation
is risky.
----End
Related Information
None.
3.27 EXER_FAIL
Description
The EXER_FAIL is an alarm indicating that the automatic exercise switching fails in ECC check.
Attribute

Parameters
table.

Name Meaning
Parameter 1 Indicates the protection group ID. The value ranges from 1 to 10.
Parameter 2 Indicates the direction. 0x00: West 0x01: East
Impact on System
When the EXER_FAIL alarm occurs, it indicates that the multiplex section switching has failed.
Problems may exist in transmitting and receiving of the K byte. The multiplex section switching
may be abnormal.
Possible Causes
The possible cause of the EXER_FAIL alarm is as follows:
The board is faulty.
Handling Procedure
The EXER_FAIL is reported transiently. It will be cleared automatically.
----End
Related Information
None.
3.28 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating loss of the external clock source set on the clock
board.
Attribute
Parameters

table.
Name Meaning
Parameter 1 Indicates the clock source number.
Impact on System
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 aligning is incorrect and massive
receiving bit errors and pointer justification events occur. As a result, the services are
unavailable.
Possible Causes
The possible cause of the EXT_SYNC_LOS alarm is as follows:
The signal is lost at the physical interface of the external clock source.
Handling Procedure
Step 1 Check whether the cable connection for inputting the external clock is abnormal, whether the
cable connector is loose, and whether the cable break occurs. If yes, remove the fault of the
cable. View alarms on the T2000 to check whether the EXT_SYNC_LOS alarm is cleared.
If... Then...
Step 2 Check whether the external clock device operates normally. If not, replace the device.
----End
Related Information
None.
3.29 FCS_ERR
Description
The FCS_ERR is an alarm indicating the FCS check error. When the FCS_ERR alarm occurs,
it indicates that errors occur in the frame check sequence (FCS) performed for the received GFP
frames.

Attribute
Parameters
table.
Name Meaning
Parameter 1 0x01
Parameter 2 0x00
Parameter 3 Indicates the VCTRUNK number where the alarm occurs.
l 0x01-0x08 (1-8): EFT0, EFT8A, EFT8B
l EMS1: 0x01-0x18(1-24)

Impact on System
If the FCS_ERR alarm occurs due to inconsistent encapsulation protocols, the services will be
interrupted.
If the FCS_ERR alarm occurs due to bit errors in the system, the packets will be lost or the
services will be interrupted.
Possible Causes
The possible causes of the FCS_ERR alarm are as follows:
l The encapsulation protocols, or the protocol parameter settings such as "scrambling or not"
and "negation or not" are inconsistent.
l The services have bit errors.
Handling Procedure
Step 2 Check on the T2000 whether the encapsulation protocols of the VCTRUNK ports at the local
station and the opposite station are consistent. Also check whether the protocol parameters are
consistent.

If... Then...
The encapsulation protocols and the protocol Configure them to be consistent. If the alarm
parameters are inconsistent is cleared, the fault is rectified. End the alarm
handling. If the alarm persists, proceed to the
next step.
The encapsulation protocols and the protocol Proceed to the next step.
parameters are consistent
Step 3 Check whether there are bit error alarms such as BIP_EXC, BIP_SD, B3_EXC, and B3_SD over
the link. If yes, clear these alarms first. Then check whether the alarm is cleared.
If... Then...
----End
Related Information
None.
3.30 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the received flow on the Ethernet port exceeds
the threshold.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the number of the IP port.
Parameter 2 0x01: Indicates the optical interface number (the value is always 0x01).

Name Meaning
Parameter 3 0x01: Indicates the optical interface number (the value is always 0x01).
Parameter 4 Exceeds the value of the traffic, with the unit of Mbps
Parameter 5 Exceeds the value of the traffic, with the unit of Mbps
Impact on System
None.
Possible Causes
The possible causes of the FLOW_OVER alarm are as follows:
l When the received flow on the port exceeds the upper threshold of the port, the
FLOW_OVER alarm is generated.
Handling Procedure
Step 1 View the FLOW_OVER alarm on the T2000. According to Parameter 4 and Parameter 5, obtain
the amount of the flow that exceeds the threshold.
Step 2 If the flow on the port exceeds the set threshold, modify the upper threshold of the port or reduce
the actual flow on the port to clear the alarm.
----End
Related Information
None.
3.31 FUSE_ALARM
Description
The FUSE_ALARM is an alarm indicating that the fuse of the CAU board is faulty.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the path number.
l 0x01: Indicates the battery fuse.
l 0x02: Indicates the battery power-off.
l 0x03: Indicates load fuse 1.
l 0x04: Indicates load fuse 2.

Parameter 3 0x01: The fuse is blown.
Impact on System
The FUSE_ALARM alarm affects the power supply of the system. It may cause power failure
to the NE.
Possible Causes
The possible causes of the FUSE_ALARM alarm are as follows:
l The battery fuse is blown.
l The load fuse 1 is blown.
l The load fuse 2 is blown.
Handling Procedure
View the FUSE_ALARM alarm on the T2000. Confirm the type of the faulty load fuse according
to Parameter 3.
If... Then...
The battery fuse is blown Replace the battery fuse. Then check whether the alarm is cleared.
If not, replace the CAU.
The load fuse 1 is blown Replace load fuse 1. Then check whether the alarm is cleared. If
not, replace the CAU.
The load fuse 2 is blown Replace load fuse 2. Then check whether the alarm is cleared. If
not, replace the CAU.
CAUTION
Replacing the power module or the subrack of the NE requires the power off of the NE. This
will interrupt the services on the NE. The operation is risky.
----End

Related Information
None.
3.32 HARD_BAD
Description
The HARD_BAD is an alarm indicating board hardware failure.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Alarm type:
l 1: The power module operates abnormally.

l 2: The board is improperly installed (the board is poorly connected to the
backplane. For example, the board is not seated tight).
l 3: 38M system clock 1 is abnormal.
l 4: 38M system clock 2 is abnormal.
l 5: 2M clock source is abnormal.
l 6: The digital phase-locked loop is abnormal.
l 7: 38M service clock is lost.
l 8: The bus is abnormal.
l 9: The TPS protection board is abnormal.
l 10: The main oscillator is faulty.
l 11: The frequency offset of the main oscillator is excessive.
l 12: The standby oscillator stops oscillating.
l 13: The processors such as CPU, DSP, and coprocessor are faulty.
l 14: The memory device is faulty.
l 15: The programmable logic device (PLD) is faulty.
l 16: The SDH component is faulty.
l 17: The data communication device is faulty.
l 18: The clock device is faulty.
l 19: The interface device is faulty.
l 20: The power device is faulty.
l 21: Other faults.
l 22: The analog phase-locked loop is abnormal.
Parameter 2 Indicates the location of the alarm.

Parameter 3 Indicates the location of the alarm.
Impact on System
When the FPGA alarm occurs, it indicates that the chip, clock oscillator, or FPGA of the board
is faulty. As a result, all the board functions may be unavailable.
Possible Causes
The possible cause of the HARD_BAD alarm is as follows:
The board hardware is faulty.

Handling Procedure
Replace the faulty board. If the alarm persists after the board is replaced, contact Huawei
engineers for troubleshooting.
CAUTION
l For the SCC board:
l After replacing the SCC board, ensure that the ID and IP are consistent with that of the
old board.
----End
Related Information
None.
3.33 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that the performance of the higher order path crosses
the threshold.
Attribute
Minor Service alarm
Parameters


table.
Name Meaning
Parameter 4 The higher two bits indicate the performance monitoring period.
l When the value of the higher two bits is 1, the monitoring period is 15 minutes.
l When the value of the higher two bits is 2, the monitoring period is 24 hours.
The lower six bits and Parameter 5 indicate the performance event ID.
Parameter 5 Parameter 5 and the lower six bits of Parameter 4 indicate the performance event
ID.
Impact on System
When the HP_CROSSTR alarm occurs, it indicates that the bit errors in the higher order path
module are excessive and cross the performance threshold. As a result, bit errors may occur in
the services or the services may be unavailable.
Possible Causes
The possible causes of the HP_CROSSTR alarm are as follows:
l The laser performance on the line board at the opposite station is degraded.
l The receive optical power on the line board at the local station is over high or over low.
l The clock performance at the opposite station is degraded.
l The clock performance at the local station is degraded.
l The fiber performance is degraded.
Handling Procedure
the board that reports the HP_CROSSTR alarm.
If... Then...
There are not such alarms as B1_EXC, Proceed to the next step.
B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm.
Step 2 Check whether the clock tracing in the entire network is correctly set. After ensuring the clock
tracing setting of the entire network, view alarms on the T2000 to check whether the
HP_CROSSTR alarm is cleared after the specified performance monitoring period ends.

If... Then...
If... Then...
The higher order adaptation performance event is reported on Go to step 7.
the board at the local station
The higher order adaptation performance event is reported on Proceed to the next step.
the board at the opposite station
Step 4 Replace the line board at the opposite station. View alarms on the T2000 to check whether the
HP_CROSSTR alarm is cleared.
If... Then...
Step 5 Replace the cross-connect and timing board at the opposite station. View alarms on the T2000
to check whether the HP_CROSSTR alarm is cleared.
If... Then...
Step 6 Replace the line board at the local station. View alarms on the T2000 to check whether the
HP_CROSSTR alarm is cleared.
If... Then...
alarm is cleared.
If... Then...
If... Then...

If... Then...
CAUTION
----End
Related Information
None.
3.34 HP_LOM
Description
The HP_LOM is an alarm indicating loss of multiframe in the higher order path.
Attribute

Parameters
table.

Name Meaning
Impact on System
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 AIS (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.
Handling 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. View alarms on the T2000 to check
whether the HP_LOM alarm is cleared.
If... Then...
Step 2 Check whether the cross-connect and timing board 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 at the opposite station. Replace the line board first and then the cross-
connect and timing board of the opposite station. View alarms on the T2000 to check whether
the HP_LOM alarm is cleared.
If... Then...
Step 3 Perform an optical path self-loop at the local station to locate the faulty board if there is. Replace
the faulty board.

CAUTION
----End
Related Information
None.
3.35 HP_RDI
Description
The HP_RDI is an alarm indicating that the local station receives the remote defect indication
in the higher order path sent from the opposite station.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
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 The line board of the opposite station receives the AU_AIS, AU_LOP, HP_TIM/HP_SLM,
B3_EXC/B3_SD, HP_UNEQ, or HP_LOM alarm.
Handling Procedure
Step 1 View the alarms of the NE on the T2000 and check whether there are higher order alarms.
If... Then...
There are such alarms as the AU_AIS, See the corresponding section in this document
AU_LOP, HP_TIM, HP_SLM, B3_EXC, to clear the alarm.
B3_SD, HP_UNEQ, or HP_LOM alarm
There are no such alarms as the AU_AIS, Proceed to the next step.
AU_LOP, HP_TIM, HP_SLM, B3_SD,
HP_UNEQ, or HP_LOM alarm
Step 2 View alarms on the T2000 to check whether the HP_RDI alarm is cleared.
If... Then...
If... Then...
The board at the opposite station reports the The receive end of the board at the opposite
HP_RDI alarm station is faulty. Replace the faulty board.
The board at the local station reports the The transmit end of the board at the local
HP_RDI alarm station is faulty. Replace the faulty board.

CAUTION
----End
Related Information
l 3.7 AU_AIS
l 3.8 AU_LOP
l 3.38 HP_TIM
l 3.37 HP_SLM
3.36 HP_REI
Description
The HP_REI is an alarm indicating that the local station receives the remote error indication in
the higher order path sent from the opposite station.
Attribute

Warning Service alarm
Parameters
table.
Name Meaning

Impact on System
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:
l The B3 bit errors are received at the opposite station.
l The equipment is interfered with.
Handling Procedure
Step 1 View the alarms on the opposite NE, and check whether there are B1 or B2 bit errors.
If... Then...
There are B1 or B2 bit errors See the corresponding section in this document to clear
the alarm.
There are not B1 or B2 bit errors Proceed to the next step.
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If few B3 bit errors occur at the remote end, the fault usually lies
in the equipment instead of the optical path. Perform a loopback for the stations at two ends of
the line. Check whether the cross-connect and timing board and the tributary board on the
opposite equipment and local equipment operate normally. Following the service direction,
check upstream stations one by one. Locate the faulty board.
If... Then...
The board at the opposite station reports B3 The receive end at the opposite station is
bit errors faulty. Replace the boards in an order of line
board, tributary board, and cross-connect and
timing board.
The board at the local station reports B3 bit The transmit end at the local station is faulty.
errors Replace the boards in an order of line board,
tributary board, and cross-connect and timing
board.

CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
3.37 HP_SLM
Description
The HP_SLM is an alarm indicating mismatch of the higher order path signal label (C2 byte)
received by the line board.
Attribute

Parameters
table.

Name Meaning
Impact on System
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.
Handling Procedure
Step 1 Check whether the C2 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If the configuration
is different, modify them to be consistent and issue the configuration again.
Step 2 View alarms on the T2000 to check whether the HP_SLM alarm is cleared.
If... Then...
If not, modify the incorrect configuration and issue it again.
----End
Related Information
None.
3.38 HP_TIM

Description
The HP_TIM is an alarm indicating mismatch of the higher order path trace identifier (J1 byte)
Attribute
Parameters
table.
Name Meaning
Parameter 2 Indicates the higher order path number.
Parameter 3 Indicates the lower order path number.
Impact on System
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.
Handling 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 T2000 to check whether the HP_TIM alarm is cleared.

If... Then...
----End
Related Information
None.
3.39 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path received by the line board is
unloaded.
Attribute
Parameters
table.
Name Meaning
Impact on System
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 causes of the HP_UNEQ alarms are as follows:
l The service is not configured at the opposite station.
l The service is not configured at the upstream stations passed through.
l The C2 byte in five consecutive received frames is all "0"s.
Handling Procedure
Step 1 Check the C2 byte configuration of the opposite NE to check whether the C2 byte has sent
UNEQ. If the configuration is incorrect, modify the configuration and issue it again.
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 If the service is configured at the opposite station, check whether the HP_UNEQ alarm occurs
in the corresponding channels of the upstream stations. If the alarm occurs, the possible cause
is that the upstream transmits transparently the unloaded service to the local station. Clear the
HP_UNEQ alarm of the upstream first.
Step 4 View alarms on the T2000 to check whether the HP_UNEQ alarm is cleared.
If... Then...
Step 5 The board at the local station is faulty. Replace the faulty board.
CAUTION
----End
Related Information
None.
3.40 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that the performance of the higher order path
adaptation crosses the threshold.

Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1 0x01
Parameter 4 The higher two bits indicate the performance monitoring period.
l When the value of the higher two bits is 1, the monitoring period is 15 minutes.
l When the value of the higher two bits is 2, the monitoring period is 24 hours.
The lower six bits and Parameter 5 indicate the performance event ID.
ID.
Impact on System
When the HPAD_CROSSTR alarm occurs, it indicates that the TU-PTR pointer justification
events in the adaptation module of the higher order path are excessive and cross the performance
threshold. As a result, bit errors may occur in the lower order services or the lower order services
may be unavailable.
Possible Causes
The possible causes of the HPAD_CROSSTR alarm are as follows:
l The laser performance on the line board at the opposite station is degraded.
l The receive optical power on the line board at the local station is over high or over low.
l The clock performance at the local station is degraded.
l The fiber performance is degraded.

Handling Procedure
Step 1 Check whether the clock tracing at the local station or in the entire network is correctly set. After
verifying that the clock tracing settings are correct, wait until the set performance monitoring
period ends. View alarms on the T2000 to check whether the HPAD_CROSSTR alarm is cleared.
If... Then...
If... Then...
The higher order adaptation performance event is reported on Go to step 6.
the board at the local station
The higher order adaptation performance event is reported on Proceed to the next step.
the board at the opposite station
Step 3 Replace the line board at the opposite station. View alarms on the T2000 to check whether the
HPAD_CROSSTR alarm is cleared.
If... Then...
Step 4 Replace the cross-connect and timing board at the opposite station. View alarms on the T2000
to check whether the HPAD_CROSSTR alarm is cleared.
If... Then...
Step 5 Replace the line board at the local station. View alarms on the T2000 to check whether the
If... Then...
alarm is cleared.
If... Then...

After the board operates normally, view alarms on the T2000 to check whether the
If... Then...
CAUTION
----End
Related Information
None.
3.41 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power of the laser exceeds the
upper threshold or is below the lower threshold.
Attribute
Parameters


table.
Name Meaning
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the IN_PWR_ABN alarm occurs, the transmit power of the laser is abnormal. As a result,
the bit errors may occur in the transmitted services or the service signals cannot be located.
Possible Causes
The possible causes of the IN_PWR_ABN alarm are as follows:
l The fiber is bent heavily.

l The fiber head is not clean or the fiber connector type is incorrect.
l The optical module is faulty.
Handling Procedure
Step 1 Query the performance of the receive optical power on the T2000. Determine whether the fault
is caused by the over high or over low optical power based on the result.
If... Then...
The optical power is over low Proceed to the next step.
The optical power is over high Go to step 3.
If... Then...
The fiber is intact and the optical connector Go to step 4.
is clean
go to step 4.
Step 3 Connect the optical attenuator to the input optical interface to decrease the optical power of the
input signal. Then check whether the IN_PWR_ABN alarm is cleared.

If... Then...
Step 4 Check whether the transmit part of the optical module on the service board at the opposite station
is abnormal.
If... Then...
The alarm is cleared Replace the opposite optical module. If the alarm persists, proceed to
the next step.
Step 5 It indicates that the service board is faulty. Replace the faulty board.
CAUTION
----End
Related Information
None.
3.42 INPWR_FAIL
Description
The INPWR_FAIL is an alarm indicating the input failure of the -48 V power supply on the
power board.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the power supply number. The value is always 0x01.
Impact on System
If one power board reports the INPWR_FAIL alarm, the power supply protection fails to
function. If two power boards both report the INPWR_FAIL alarm, the system cannot operate
normally. As a result, the services are severely affected.
Possible Causes
The possible causes of the INPWR_FAIL alarm are as follows:
l The -48 V power supply on the power board is faulty.

l The output -48 V power supply on the cabinet is abnormal.
Handling Procedure
Step 1 Replace the faulty power board.
Step 2 After the new board starts to work, view alarms on the T2000 to check whether the
INPWR_FAIL alarm is cleared.
If... Then...
CAUTION
You need to power off the NE when replacing the power board of the NE. This will interrupt
the services on the NE. The operation is risky.
----End
Related Information
None.
3.43 J0_MM

Description
The J0_MM is an alarm indicating the mismatch of the regenerator section trace identifier (J0)
Attribute

Parameters
table.
Name Meaning
Impact on System
When the J0_MM occurs, the trace identifier byte J0 received by the line board mismatches that
to be received.
Possible Causes
The possible causes of the J0_MM alarm are as follows:
l The J0 byte transmitted at the opposite station is inconsistent with that to be received at the
local station.
l The local station is faulty.
l The transmit end is faulty.
Handling Procedure
Step 1 Check on the T2000 whether the transmitted J0 byte is consistent with that to be received at the
two stations that report the J0_MM alarm. If not, configure the J0 byte to be consistent.
Step 2 View alarms on the T2000 to check whether the J0_MM alarm is cleared.

If... Then...
Step 3 If the alarm persists, perform a selfloop with fibers for the optical interfaces on the corresponding
line boards at the two stations. Replace the board that reports the J0_MM alarm.
CAUTION
----End
Related Information
None.
3.44 K1_K2_M
Description
The K1_K2_M is an alarm indicating the mismatch between the transmitted K1 byte and
received K2 byte of a linear MSP group.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the protection group. 0x01: Linear MSP

Name Meaning
Impact on System
When the K1_K2_M alarm occurs, the mismatch between the transmitted K1 byte and received
K2 byte of a linear MSP group occurs. As a result, the automatic protection switching may fail
and the protected services may be interrupted.
Possible Causes
The possible causes of the K1_K2_M alarm are as follows:
l The received K2 byte mismatches the transmitted K1 byte.

l The fault occurs on the line board when it transmits or receives the K byte.
l The MSP protocol at the opposite station is not consistent.
l The MSP protocol at the opposite station is not started.
Handling Procedure
Step 1 Ensure that the MSP protocol at the opposite station is consistent. Then check whether the
K1_K2_M alarm is cleared.
If... Then...
Step 2 If the alarm persists, replace the line board in the protection channel.
CAUTION
----End
Related Information
None.
3.45 K2_M

Description
The K2_M is an alarm indicating that the mismatch between the received K2 byte and the
transmitted K2 byte of a linear MSP group.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the protection group. 0x01: Linear MSP
Impact on System
When the K2_M alarm occurs, the mismatch of the received and transmitted K2 byte of a linear
MSP group occurs. The MSP group types at two stations are inconsistent. As a result, the
automatic protection switching may fail and the protected services may be interrupted.
Possible Causes
The possible causes of the K2_M alarm are as follows:
l The mismatch between the transmitted K2 byte and the received K2 byte occurs.
l The types of the MSP group at two stations are not consistent
l The fault occurs on the line board when it transmits or receives the K byte.
Handling Procedure
Step 1 Check whether the MSP group types of two stations are consistent. Check whether they are both
of the 1+1 or 1:N MSP group. If not, modify them to be consistent. If the MSP protocol at two
stations is stopped, start the MSP protocol of the protection group again.
Step 2 View alarms on the T2000 to check whether the K2_M alarm is cleared.

If... Then...
Step 3 If the alarm persists, replace the line board in the protection channel.
CAUTION
----End
Related Information
None.
3.46 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module
on the board mismatches that of the optical interface.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the LASER_MOD_ERR alarm occurs, the installed pluggable optical module on the board
mismatches the rate level of the optical interface on the line board. As a result, the service
transmission and receiving will be abnormal.
Possible Causes
The possible causes of the LASER_MOD_ERR alarm are as follows:
l The optical module installed on the board mismatches the rate level of the optical interface.
Handling Procedure
Step 1 Check whether the service board matches the type of the optical module installed on it. If not,
replace the optical module with a new one that matches the rate level of the optical interface.
Step 2 View alarms on the T2000 to check whether the LASER_MOD_ERR alarm is cleared.
If... Then...
Step 3 The optical module is faulty. Replace the faulty module with a new one of the same type.
Step 4 View alarms on the T2000 to check whether the LASER_MOD_ERR alarm is cleared.
If... Then...
Step 5 The service board is faulty. Replace the faulty board. After the new board starts to work, view
alarms on the T2000 to check whether the LASER_MOD_ERR alarm is cleared.
If... Then...

CAUTION
----End
Related Information
None.
3.47 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction.
When this alarm occurs, the sink end of the LCAS module detects abnormalities. As a result,
the LCAS negotiation may be unavailable or incorrect.
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Impact on System
When the LCAS_FOPR alarm occurs, the protocol state machine in the receive direction is in
confusion. The negotiation may be abnormal.

Possible Causes
The possible causes of the LCAS_FOPR alarm are as follows:
l The downlink VCG receives repeated sequence numbers due to incorrect configuration or
bit errors in the link.
l The LCAS function of the opposite VCG is disabled.
l The downlink VCG simultaneously receives the FIXED and other LCAS control bytes due
to incorrect configuration or bit errors in the link.
l The cross-connection is incorrectly bound.
Handling Procedure
Step 1 View the LCAS_FOPR alarm on the T2000, and confirm the relevant VCTRUNK number
according to the alarm parameters.
If... Then...
Step 2 Check whether the LCAS protocol is enabled at the opposite station.
If... Then...
The protocol is not enabled Enable the LCAS protocol at the opposite station. If the alarm
is cleared, the fault is rectified. End the alarm handling. If the
alarm persists, proceed to the next step.
The protocol is enabled Proceed to the next step.
Step 3 Check whether the configuration is correct. Especially, check whether the cross-connection of
the timeslot is correctly bound.
If... Then...
The configuration is incorrect Modify the incorrect configuration. If the alarm is cleared,
the fault is rectified. End the alarm handling. If the alarm
persists, proceed to the next step.
The configuration is correct. Proceed to the next step.
Step 4 Disable the LCAS function at both stations and then enable this function at both stations at the
same time. Check whether the LCAS_FOPR alarm is cleared.
If... Then...
----End
Related Information
None.

3.48 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the failure of the LCAS protocol in the transmit
direction. When the source end of the LCAS module detects abnormalities, the LCAS negotiation
is unavailable or incorrect, the alarm is reported.
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Impact on System
When the LCAS_FOPT alarm occurs, the protocol state machine in the transmit direction is in
confusion. The negotiation may be abnormal.
Possible Causes
The possible causes of the LCAS_FOPT alarm are as follows:
There is the persistent and unexpected MST due to incorrect configuration or invalid link in the
link. For example, the member that transmits the IDLE always receives MST=OK.
Handling Procedure
The protocol failure alarm is caused by the incorrect configuration. Hence, first check whether
the configuration is correct. Especially, check whether the bound cross-connection is correct.
----End

Related Information
None.
3.49 LCAS_PLCR
Description
The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction.
This alarm occurs when the number of paths in the receive direction that carry load is less than
the number of paths configured and is not zero, if the LCAS function of the VCTRUNK is
enabled.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the LCAS_PLCR alarm occurs, the available bandwidth in the receive direction decreases.
The services are not interrupted.
Possible Causes
The possible causes of the LCAS_PLCR alarm are as follows:
l Bidirectional services are not configured.

l The number of members in the uplink at the opposite station is less than that in the downlink
at the local station.

l The path communication fails due to the incorrect cross-connection or improperly

connected physical link.
Handling Procedure
Step 1 Check whether there are other alarms, such as the AIS, LOP, UNEQ, or LOM. If yes, clear these
alarms first. Then, check whether the alarm is cleared.
If... Then...
Step 2 After ensuring that the physical link is available, check whether bidirectional services are
configured.
If... Then...
Bidirectional services are not configured. Configure the bidirectional services. If the alarm
is cleared, the fault is rectified. End the alarm
next step.
Bidirectional services are configured Proceed to the next step.
Step 3 Check on the T2000 whether the number of downlink timeslots bound with the VCTRUNK at
the local station is consistent with that of uplink timeslots bound with the VCTRUNK at the
opposite station.
If... Then...
The number is not consistent Increase or decrease the number of the timeslots so that the
number of timeslots at both stations is consistent. If the alarm
The number is consistent Proceed to the next step.
Step 4 Check whether the cross-connection is bound from the transmit direction to the opposite station.
If... Then...
The cross-connection is not bound Re-bind the cross-connection. If the alarm is cleared, the
fault is rectified. End the alarm handling. If the alarm
The cross-connection is bound Proceed to the next step.
Step 5 The wait-to-restore (WTR) time may be too long and the members are not restored. Check the
WTR time. Wait for a period. Then check whether the LCAS_PLCR alarm is cleared.
If... Then...

Step 6 Disable and then enable the LCAS function of the VCTRUNK. Check whether the LCAS_PLCR
alarm is cleared.
If... Then...
Step 7 Delete and re-bind all physical paths of the VCTRUNK. Check whether the LCAS_PLCR alarm
is cleared.
If... Then...
Step 8 Perform a cold reset on the board, or remove and insert the board.
If... Then...
Step 9 Replace the service board.
CAUTION
l Performing a cold reset will interrupt the services on the board. The operation is risky.
----End
Related Information
None.
3.50 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating partial loss of capacity in the LCAS transmit direction.
When this alarm occurs, the number of paths in the transmit direction that carry load is less than
the number of paths configured and is not zero, if the LCAS function of the VCTRUNK is
enabled.

Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the LCAS_PLCT alarm occurs, the available bandwidth in the transmit direction
decreases. Packet loss will occur when the actual service traffic is larger than the available
bandwidth in the transmit direction.
Possible Causes
The possible causes of the LCAS_PLCT alarm are as follows:
l Bidirectional services are not configured
l The number of members in the downlink at the opposite station is less than that in the uplink
at the local station.
l The path communication fails due to the incorrect cross-connection or improperly
connected physical link.
Handling Procedure
Step 1 View the LCAS_PLCT alarm on the T2000, and confirm the relevant VCTRUNK number
Step 2 Check whether the LCAS_PLCR alarm occurs at the opposite end. If yes, clear the LCAS_PLCR
alarm first. Then, check whether the alarm is cleared.
If... Then...

Step 3 Check whether bidirectional services are configured at the port.
If... Then...
next step.
Step 4 Check on the T2000 whether the number of uplink timeslots bound with the VCTRUNK at the
local station is consistent with that of downlink timeslots bound with the VCTRUNK at the
opposite station.
If... Then...
The number is not consistent Increase or decrease the number of the timeslots so that the
number of timeslots at both stations is consistent. If the alarm
Step 5 Re-bind the cross-connection. Then check whether the LCAS_PLCT alarm is cleared.
If... Then...
Step 6 The wait-to-restore (WTR) time may be too long and the members are not restored. Check the
WTR time. Wait for a period. Then check whether the LCAS_PLCR alarm is cleared.
If... Then...
Step 7 Disable and then enable the LCAS function of the VCTRUNK. Check whether the LCAS_PLCR
alarm is cleared.
If... Then...
is cleared.
If... Then...

If... Then...
CAUTION
----End
Related Information
None.
3.51 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating the total loss of capacity in the LCAS receive direction.
This alarm occurs when the number of paths in the receive direction that carry load is zero and
the number of paths configured is not zero, if the LCAS function of the VCTRUNK is enabled.
Attribute
Major Service alarm
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the LCAS_TLCR alarm occurs, the available bandwidth in the receive direction decreases
to zero. The services in this direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCR alarm are as follows:
l Bidirectional services are not configured

l The uplink of the opposite station is not bound with members.
l The path communication fails because the cross-connection is incorrect or other alarms.
Handling Procedure
Step 1 View the LCAS_TLCR alarm on the T2000, and confirm the relevant VCTRUNK number
If... Then...
Step 2 Check whether there are other alarms, such as the AIS, LOP, UNEQ, and LOM. If yes, clear
these alarms first. Then, check whether the alarm is cleared.
If... Then...
Step 3 Check whether bidirectional services are configured at the port.
If... Then...
next step.
Step 4 Check whether the uplink of the opposite station is bound with timeslots.

If... Then...
The downlink is not bound with timeslots Bind the timeslots in the corresponding
direction. If the alarm is cleared, the fault is
rectified. End the alarm handling. If the alarm
The uplink is bound with timeslots Proceed to the next step.
Step 5 Check whether the cross-connection is bound from the transmit direction to the local station.
If... Then...
The downlink is not bound with timeslots Re-bind the cross-connection. If the alarm is
cleared, the fault is rectified. End the alarm
next step.
Step 6 Disable and then enable the LCAS function of the VCTRUNK. Check whether the LCAS_TLCR
alarm is cleared.
If... Then...
is cleared.
If... Then...
If... Then...
CAUTION
----End

Related Information
None.
3.52 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating the total loss of bandwidth in the LCAS transmit
direction. This alarm occurs when the number of paths in the transmit direction that carry load
is zero and the number of paths configured is not zero, if the LCAS function of the VCTRUNK
is enabled.
Attribute

Major Service alarm
Parameters
table.
Name Meaning
Impact on System
When the LCAS_TLCT alarm occurs, it indicates that the available bandwidth in the transmit
direction is reduced to zero. The services in the transmit direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCT alarm are as follows:
l The downlink of the opposite station is not bound with members.

l The path communication fails because the cross-connection is incorrect or other alarms.

Handling Procedure
Step 1 View the LCAS_TLCT alarm on the T2000, and confirm the relevant VCTRUNK number.
If... Then...
Step 2 Check whether the LCAS_TLCR alarm occurs at the opposite station. If yes, clear the
LCAS_TLCR alarm and then check whether the alarm is cleared.
If... Then...
Step 3 Check whether there are other alarms, such as the AIS, LOP, UNEQ, and LOM. If yes, first clear
these alarms and then check whether the LCAS_TLCT alarm is cleared.
If... Then...
Step 4 Check whether the downlink of the opposite station is bound with timeslots.
If... Then...
The downlink is not bound with timeslots Bind the timeslots in the corresponding
direction. If the alarm is cleared, the fault is
rectified. End the alarm handling. If the alarm
Step 5 Check whether the cross-connection is correctly bound from the transmit direction to the local
station. After ensuring that the cross-connection is correctly bound, check whether the
LCAS_TLCT alarm is cleared.
If... Then...
The cross-connection is incorrectly bound Modify the cross-connection binding. If the
alarm is cleared, the fault is rectified. End the
alarm handling. If the alarm persists, proceed to
the next step.
The cross-connection is correctly bound Proceed to the next step.
Step 6 Disable and then enable the LCAS function of the VCTRUNK. Check whether the LCAS_TLCR
alarm is cleared.
If... Then...

If... Then...
is cleared.
If... Then...
If... Then...
CAUTION
----End
Related Information
None.
3.53 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating the loopback. When the LOOP_ALM occurs, it indicates
that the loopback exists.
Attribute

Minor Equipment alarm

Parameters
table.
Name Meaning
Parameter 2 Indicates the path number (MSB). In the case of the optical interface loopback,
the value of parameter 2 is 0 by default.
Parameter 3 Indicates the path number (LSB). In the case of the optical interface loopback,
the value of parameter 3 is 1 by default.
Parameter 4 Indicates the loopback type. 0x00: Optical interface inloop 0x01: Optical
interface outloop 0x02: Path inloop 0x03: Path outloop
Impact on System
When the LOOP_ALM alarm occurs, if there is the loopback in the system, services at the optical
interface or in the path that are in the reverse direction of the loopback are interrupted.
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
The line board loopback or the tributary board loopback is manually configured.
Handling Procedure
Manually release the loopback configuration, and the LOOP_ALM alarm is automatically
cleared.
----End
Related Information
None.
3.54 LP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that the performance of the lower order path of the
tributary crosses the threshold.

Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1 0x01
Parameter 4 The higher two bits indicate the performance monitoring period. When the value
of the higher two bits is 1, the monitoring period is 15 minutes; When the value
of the higher two bits is 2, the performance monitoring period is 24 hours; The
lower six bits and Parameter 5 indicate the performance event ID.
ID.
Impact on System
When the LP_CROSSTR alarm occurs, the bit errors in the lower order path module of the
tributary board are excessive and cross the performance threshold. This may cause the bit errors
in the services or unavailable services.
Possible Causes
The possible causes of the LP_CROSSTR alarm are as follows:
l The higher-level bit errors occur.

Handling Procedure
Step 1 View the bit errors of the NE. Check whether there are section-level or higher order bit errors
on the line board that accesses the services.
If... Then...
B2_SD, B3_EXC, B3_SD, BIP_EXC, or to clear the alarm.
BIP_SD alarm

If... Then...
There is no such alarm such as the Proceed to the next step.
B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, B3_SD, BIP_EXC, and BIP_SD
Step 2 Check whether the clock tracing in the entire network is correctly set. After ensuring the clock
tracing setting of the entire network, view alarms on the T2000 to check whether the
LP_CROSSTR alarm is cleared after the specified performance monitoring period ends.
If... Then...
If... Then...
The lower order performance event is The receive end at the opposite station is
reported on the opposite board faulty. Replace the boards in an order of line
board, tributary board, and cross-connect
and timing board.
The lower order performance event is The receive end at the local station is faulty.
reported on the local board Replace the boards in an order of line board,
tributary board, and cross-connect and
timing board.
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD

l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC
l 3.15 B3_SD
l 3.18 BIP_EXC
l 3.19 BIP_SD
3.55 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

Parameters
table.
Name Meaning
Impact on System
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 are interrupted.
Possible Causes
The possible causes of the LP_R_FIFO alarm are as follows:

l The transmission rate of the services in the lower order path is over fast, and thus the pointer
justification is abnormal. As a result, the received FIFO overflows.
Handling Procedure
Step 1 Replace the tributary board at the local station.
Step 2 After the new board starts to work, view alarms on the T2000 to check whether the alarm is
cleared.
If... Then...
CAUTION
Replacing the tributary board will interrupt services. The operation is risky.
alarm is cleared.
If... Then...
After the board operates normally, view alarms on the T2000 to check whether the SYN_BAD
alarm is cleared.
If... Then...
----End
Related Information
None.
3.56 LP_RDI

Description
The LP_RDI is an alarm indicating the remote defect in the lower order path of the tributary
board.
Attribute
Parameters
table.
Name Meaning
Impact on System
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]) 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.

Handling 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.
If... Then...
There is the TU_AIS, or TU_LOP alarm See the corresponding section in this document
to clear the alarm.

If... Then...
There is no such alarm as the TU_AIS or Proceed to the next step.
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
l 3.137 TU_AIS
l 3.140 TU_LOP
3.57 LP_RDI_VC12
Description
The LP_RDI_VC12 is a remote defect indication alarm in the lower order path. If the board has
detected that bit 8 of the V5 byte in the VC-12 lower order path is 1, the LP_RDI_VC12 alarm
is reported.
Attribute
Parameters
table.
Name Meaning
Parameter 2 Indicates the path number of VC-12.

Name Meaning
Impact on System
When the LP_RDI_VC12 alarm occurs, the system is not affected. This alarm only shows that
the opposite station fails to receive signals.
Possible Causes
The possible cause of the LP_RDI_VC12 alarm is as follows:
The LP_RDI_VC12 alarm is an accompanying alarm. When the relevant path of a tributary
board at the opposite station reports the TU_AIS_VC12 or TU_LOP_VC12 alarm, it returns the
LP_RDI_VC12 alarm to the local station.
Handling Procedure
After you clear the TU_AIS_VC12 or TU_LOP_VC12 alarm reported in the corresponding path
of the service board at the opposite station, the LP_RDI_VC3 alarm is automatically cleared.
----End
Related Information
None.
3.58 LP_RDI_VC3
Description
The LP_RDI_VC3 is a remote defect indication alarm in the VC-3 lower order path. If the board
has detected that bit 5 of the G1 byte in the VC-3 lower order path is 1, the LP_RDI_VC3 alarm
is reported.
Attribute
Parameters

table.
Name Meaning
Impact on System
When the LP_RDI_VC3 alarm occurs, the services at the local station are not affected. This
alarm only shows that the services at the opposite station are interrupted to be received.
Possible Causes
The possible cause of the LP_RDI_VC3 alarm is as follows:
The LP_RDI_VC3 alarm is an accompanying alarm. When the corresponding path of the
tributary board at the opposite station reports the TU_AIS_VC3 or TU_LOP_VC3 alarm, it
returns the LP_RDI_VC3 alarm to the local station, showing the TU_AIS or TU_LOP alarm is
received at the opposite station.
Handling Procedure
After you clear the TU_AIS_VC3 or TU_LOP_VC3 alarm reported in the corresponding path
of the service board at the opposite station, the LP_RDI_VC3 alarm is automatically cleared.
----End
Related Information
None.
3.59 LP_REI
Description
The LP_RDI is a remote error indication alarm in the lower order path of the tributary board.
Attribute

Minor Service alarm

Parameters
table.
Name Meaning
Impact on System
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:
l Bit errors are received in the lower order path at the opposite station.
Handling Procedure
Step 1 View alarms of the opposite NE, and check whether there is the B3 or BIP bit error alarm.
If... Then...
There is the B3 or BIP bit error alarm See the corresponding section in this document to
clear the B3_EXC, B3_SD, BIP_EXC, or BIP_SD
alarm.
There is no B3 or BIP bit error alarm Proceed to the next step.
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If a few B3 or BIP bit errors occur in the remote, the fault usually
lies in the equipment instead of the optical path.
Step 3 Perform a 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.

If... Then...
There is the B3 or BIP bit error reported on The receive end at the opposite station is
the opposite board faulty. Replace the boards in an order of line
board, tributary board, and cross-connect and
timing board.
There is the B3 or BIP bit error reported on The transmit end at the local station is faulty.
the local board Replace the boards in an order of line board,
tributary board, and cross-connect and timing
board.
CAUTION
----End
Related Information
l 3.13 B3_EXC
l 3.15 B3_SD
l 3.18 BIP_EXC
l 3.19 BIP_SD
3.60 LP_REI_VC12
Description
The LP_REI_VC12 is a remote error indication alarm in the lower order path. If the board has
detected that bit 3 of the V5 byte is 1, the LP_REI_VC12 alarm is reported.

Attribute
Parameters
table.
Name Meaning
Impact on System
When the LP_REI_VC12 alarm occurs, the system is not affected. The alarm only shows that
some bit errors occur in the services in the VC-12 path at the opposite station. As a result, the
quality of the transmitted services is degraded.
Possible Causes
The possible cause of the LP_REI_VC12 alarm is as follows:
The LP_REI_VC12 alarm is an accompanying alarm. When an Ethernet board at the opposite
station has detected the BIP_SD or BIP_EXC alarm, it returns an LP_REI_VC12 alarm to the
local station.
Handling Procedure
After you clear the BIP_SD or BIP_EXC alarm that occurs at the opposite station, the
LP_REI_VC12 alarm is automatically cleared.
----End
Related Information
None.
3.61 LP_REI_VC3

Description
The LP_REI_VC3 is a remote error indication alarm in the lower order path. When the board
has detected that any of bits 1–4 in the G1 byte is 1, the LP_REI_VC3 alarm is reported.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the LP_REI_VC3 alarm occurs, the system is not affected. The alarm only shows that
some bit errors are received in the lower order path at the opposite station. As a result, the quality
of the transmitted services is degraded.
Possible Causes
The possible cause of the LP_REI_VC3 alarm is as follows:
The LP_REI_VC3 alarm is an accompanying alarm. When the Ethernet board at the opposite
station has detected the bit error alarm, B3_SD_VC3 or B3_EXC_VC3, it returns an
LP_REI_VC3 alarm to the local station.
Handling Procedure
After you clear the B3_SD_VC3 or B3_EXC_VC3 alarm that occurs at the opposite station, the
LP_REI_VC3 alarm is automatically cleared.
----End
Related Information
None.

3.62 LP_RFI
Description
The LP_RFI is an alarm indicating that the E1/T1 tributary board receives the remote failure
alarm of the lower order path from the downlink bus.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the LP_RFI alarm occurs, the local E1/T1 tributary board receives the remote failure alarm
of the lower order path (V5[b4]=1) at the opposite station.
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.
Handling Procedure
Step 1 Check and handle the alarms reported at the opposite station.
Step 2 If the LP_RFI alarm persists after the alarm at the opposite station is cleared, replace the
equipment that reports the alarm.

CAUTION
----End
Related Information
None.
3.63 LP_SIZE_ERR
Description
The LP_SIZE_ERR is an alarm indicating the TU specification error of the lower order signals
received by the E1/T1 tributary board.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the LP_SIZE_ERR alarm occurs, the mapping structure of the E1/T1 lower order services
is incorrect. As a result, the services are abnormal.

Possible Causes
The possible cause of the LP_SIZE_ERR alarm is as follows:
The mapping structure is incorrectly configured.
Handling Procedure
Step 1 Check whether any alarm is reported on the tributary board at the opposite station. (Check
whether the upstream services are of the TU-12 structure. )
Step 2 After clearing the relevant alarms, view alarms at the local station on the T2000. Check whether
the LP_SIZE_ERR alarm is cleared.
If... Then...
Step 3 Replace the tributary board that reports the LP_SIZE_ERR alarm at the local station.
Step 4 View alarms on the T2000 to check whether the alarm is cleared.
If... Then...
Step 5 Replace the tributary board at the opposite station.

If... Then...
CAUTION
----End
Related Information
None.
3.64 LP_SLM

Description
The LP_SLM is an alarm indicating mismatch of the lower order path signal label received by
the tributary board.
Attribute

Parameters
table.
Name Meaning
Impact on System
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[b5–b7], 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.
Handling 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 T2000 to check whether the LP_SLM alarm is cleared.

If... Then...
Step 4 View alarms on the T2000 to check whether the LP_SLM alarm is cleared.
If... Then...
----End
Related Information
None.
3.65 LP_SLM_VC12
Description
The LP_SLM_VC12 is a signal label mismatch alarm in the VC-12 lower order path. This alarm
is reported when the board has detected that the signal label byte V5 mismatch occurs.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the LP_SLM_VC12 occurs, the system is not affected.
Possible Causes
The possible causes of the LP_SLM_VC12 alarm are as follows:
l The type of the actually received signal does not match that of the signal to be received.
That is, the lower order path signal label byte V5[b5-b7] configured at the local station is
inconsistent with the actually received V5 byte[b5-b7].
Handling Procedure
Step 1 View the alarm on the T2000, and confirm the relevant path number according to the alarm
parameters.
Step 2 Check whether the type of the actually received signal is consistent with that of the signal to be
received. If not, modify them to be consistent and then check whether the LP_SLM_VC12 alarm
is cleared.
If... Then...
Step 3 Check whether the services in the path are correctly configured. If not, modify the incorrect
configuration and then check whether the LP_SLM_VC12 alarm is cleared.
If... Then...
----End
Related Information
None.
3.66 LP_SLM_VC3
Description
The LP_SLM_VC3 is a signal label mismatch alarm in the VC-3 lower order path. If the board
has detected that the signal label byte C2 mismatch occurs, the LP_SLM_VC3 alarm is reported.

Attribute
Parameters
table.
Name Meaning
Impact on System
When the LP_SLM_VC3 occurs, the system is not affected.
Possible Causes
The possible causes of the LP_SLM_VC3 alarm are as follows:
l The type of the actually received signal does not match that of the signal to be received.
That is, the lower order path signal label byte C2 is inconsistent with the received C2 byte.
l The service type is incorrectly configured.
Handling Procedure
parameters.
Step 2 Check whether the signal label byte in the lower order path of the Ethernet board at the opposite
station is consistent with that in the lower order path of the Ethernet board at the local station.
If not, modify them to be consistent and then check whether the LP_SLM_VC3 alarm is cleared.
If... Then...
Step 3 Check whether the services in the path are correctly configured. If not, modify the incorrect
configuration and then check whether the LP_SLM_VC3 alarm is cleared.

If... Then...
Step 4 Replace the Ethernet board at the local station.
If... Then...
Step 5 Replace the Ethernet board at the opposite station.
CAUTION
l Before replacing the Ethernet board, ensure that the new board is suitable.
l Replacing the Ethernet board without configuring the protection will interrupt all services
of the board. The operation is risky.
----End
Related Information
None.
3.67 LP_T_FIFO
Description
The LP_T_FIFO is an alarm indicating that the FIFO on the transmit side of the lower order
path of the E1/T1 tributary board overflows.
Attribute
Parameters
table.

Name Meaning
Impact on System
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:
l The frequency offset of the input signal is over great, and thus the pointer justification is
abnormal. As a result, the FIFO on the transmit side overflows.
Handling Procedure
Step 1 Replace the tributary board.
If... Then...
CAUTION
Replacing the tributary board will interrupt services. The operation is risky.
alarm is cleared.
If... Then...

After the board operates normally, view alarms on the T2000 to check whether the alarm is
cleared.
If... Then...
----End
Related Information
None.
3.68 LP_TIM
Description
The LP_TIM is an alarm indicating that the mismatch of the lower order path trace identifier
received by the tributary board.
Attribute
Parameters
table.
Name Meaning
Impact on System
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:
l The lower order path trace identifier to be received at the local station is configured
inconsistent with that transmitted at the opposite station.
Handling 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 T2000 to check whether the LP_TIM alarm is cleared.
If... Then...
Step 4 View alarms on the T2000 to check whether the LP_TIM alarm is cleared.
If... Then...
----End
Related Information
None.
3.69 LP_TIM_VC12
Description
The LP_TIM_VC12 is a trace identifier mismatch alarm in the VC-12 lower order path. This
alarm is reported when the board has detected that the J2 byte mismatch occurs.
Attribute


Parameters
table.
Name Meaning
Impact on System
When the LP_TIM_VC12 occurs, the system is not affected.
Possible Causes
The possible causes of the LP_TIM_VC12 alarm are as follows:
l The actually received J2 byte does not match that to be received.

l The service cross-connection is incorrectly configured.
Handling Procedure
parameters.
If... Then...
Step 2 Check whether the trace identifier in the lower order path at the opposite station is configured
consistent with that in the lower order path of the Ethernet board at the local station. If not,
modify them to be consistent. Then check whether the LP_TIM_VC12 alarm is cleared.
If... Then...
Step 3 Check whether the service cross-connection in the path is correctly configured. If not, modify
the incorrect configuration and then check whether the LP_TIM_VC12 alarm is cleared.

If... Then...
Step 4 Replace the Ethernet board at the local station. Then check whether the LP_TIM_VC12 alarm
is cleared.
If... Then...
Step 5 Replace the Ethernet board at the opposite station.
CAUTION
l Before replacing the Ethernet board, ensure that the new board is suitable.
l Replacing the Ethernet board without configuring the protection will interrupt all services
of the board. The operation is risky.
----End
Related Information
None.
3.70 LP_TIM_VC3
Description
The LP_TIM_VC3 is a trace identifier mismatch alarm in the VC-3 lower order path. This alarm
is reported when the board has detected that the J1 byte mismatch occurs.
Attribute
Parameters
table.

Name Meaning
Impact on System
When the LP_TIM_VC3 occurs, the system is not affected.
Possible Causes
The possible causes of the LP_TIM_VC3 alarm are as follows:
l The actually received J1 byte does not match that to be received.

l The service cross-connection is incorrectly configured.
Handling Procedure
Step 1 Check whether the trace identifier in the corresponding lower order path of the service board at
the opposite station is configured consistent with that in the lower order path of the service board
at the local station. If not, modify them to be consistent and then check whether the
LP_TIM_VC3 alarm is cleared.
If... Then...
Step 2 Check whether the service cross-connection is correctly configured. If not, modify the incorrect
configuration and then check whether the LP_TIM_VC3 alarm is cleared.
If... Then...
Step 3 Replace the service board at the local station and then check whether the LP_TIM_VC3 alarm
is cleared.
If... Then...
Step 4 If the alarm persists, replace the service board at the opposite station and then check whether
the LP_TIM_VC3 alarm is cleared.

If... Then...
CAUTION
----End
Related Information
None.
3.71 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
Parameters
table.
Name Meaning

Impact on System
When the LP_UNEQ alarm occurs, no services are loaded in the payload of the lower order path
(VC12: V5 [b5–b7], 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.
l The T_ALOS alarm is reported on the tributary board at the opposite station of the SDH
transmission equipment, and the inserting LP_UNEQ function is enabled.
Handling Procedure
Step 1 Check whether the lower order path at the opposite station is set as unused. If yes, set it as used.
Step 2 View alarms on the T2000 to check whether the LP_UNEQ alarm is cleared.
If... Then...
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.
Step 4 View alarms on the T2000 to check whether the LP_UNEQ alarm is cleared.
If... Then...
----End
Related Information
3.117 T_ALOS
3.72 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that no payload is equipped in the lower order path.
If the board has detected that the signal label in the V5 byte is 0, the LP_UNEQ_VC12 alarm is
reported.

Attribute
Parameters
table.
Name Meaning
Impact on System
When the LP_UNEQ_VC12 alarm occurs, no services are loaded in the VC-12 path. If the alarm
is caused by the incorrect service configuration, the services will be interrupted.
Possible Causes
The possible causes of the LP_UNEQ_VC12 alarm are as follows:
l The services on the Ethernet side are not accessed.
Handling Procedure
parameters.
Step 2 Check whether the service type configuration is correct. After modifying the incorrect
configuration and making sure that the services are correctly accessed on the Ethernet side, check
whether the LP_UNEQ_VC12 alarm is cleared.
If... Then...
Step 3 Check whether the attributes of the relevant Ethernet board are correctly configured. If not,
modify the incorrect configuration and the LP_UNEQ_VC12 alarm is automatically cleared.
----End

Related Information
None.
3.73 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that no payload is equipped in the VC-3 lower order
path. If a board has detected that the signal label in the C2 byte is 0, the LP_UNEQ_VC3 alarm
is reported.
Attribute

Parameters
table.
Name Meaning
Impact on System
When the LP_UNEQ_VC3 alarm occurs, no services are loaded in the path. If the alarm is caused
by the incorrect service configuration or no services accessed on the service board side, the
services will be interrupted.
Possible Causes
The possible causes of the LP_UNEQ_VC3 alarm are as follows:

l The services on the Ethernet side are not accessed.

Handling Procedure
parameters.
Step 2 Check whether the service type configuration is correct. After modifying the incorrect
configuration and making sure that the services are correctly accessed on the Ethernet side, check
whether the LP_UNEQ_VC3 alarm is cleared.
If... Then...
Step 3 Check whether the attributes of the relevant Ethernet board are correctly configured. After
modifying the incorrect configuration, the LP_UNEQ_VC3 alarm is automatically cleared.
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
3.74 LPT_INEFFECT
Description
The LPT_INEFFECT is an alarm indicating that the LPT function fails. If the user configures
the LPT function but the board does not support the LPT function, the LPT_INEFFECT alarm
is reported.
Attribute

Major Alarm Process alarm
Parameters
table.
Name Meaning
Parameter 0 0x01

Name Meaning
Parameter 1 and parameter 2 The ID of the path that generates the alarm. (when the board is
of an earlier version and thus the LPT is invalid, the alarm path
ID is 0x0001)
Parameter 3 Alarm cause
Impact on System
If the board is of an earlier version, the board software stops the state machine of the LPT
protocol, but reserves the LPT configuration. This alarm does not affect services.
Possible Causes
l The board is of an earlier version, and the user configures the LPT function.
l The encapsulation protocol of the board conflicts with the port bearer mode and the LPT
function is configured.
l The connected LPT protocol is inconsistent and the LPT function is configured.
Handling Procedure
Step 1 Check whether the LPT function is required. If the function is not required, delete the LPT
configuration from the T2000.
Step 2 Check whether the board version is too low. In the case that the hardware version is not supported
and you want to use the LPT function, replace the board with the match board. After the board
operates normally, view alarms on the T2000 to check whether the alarm is cleared.
Options Description
If this alarm is cleared The fault is rectified. End the alarm handling.
If this alarm persists Proceed to the next step.
Step 3 Check and ensure the encapsulation protocols or the port bearer modes are consistent. After
setup, view alarms on the T2000 to check whether the alarm is cleared.
Options Description
If this alarm persists Proceed to the next step.
Step 4 Check and ensure that the configurations of the LPT protocol at the two ends are the same. After
setup, view alarms on the T2000 to check whether the alarm is cleared.
Options Description
If this alarm persists Contact Huawei engineers for troubleshooting.
----End

Related Information
None.
3.75 LPT_RFI
Description
The LPT_RFI is an alarm indicating that the link state pass through function fails at the remote
end.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the number of the IP port.
Parameter 2 0x00: Indicates the port number (the value is always 0x00).
Parameter 3 0x01: Indicates the port number (the value is always 0x01).
Parameter 4 0xff
Parameter 5 0xff
Impact on System
The board software checks the network at regular intervals. When the LPT function takes effect
because the local Ethernet port is in the abnormal state, the Ethernet port at the opposite end
should report the LPT_RFI alarm. When the LPT function takes effect because the network
becomes abnormal, the Ethernet ports at both ends should report the LPT_RFI alarm.
Possible Causes
When a board is configured with the LPT function, if the local Ethernet port fails, the Ethernet
port at the opposite end should report the LPT_RFI alarm; if the SDH path fails, the Ethernet
ports at both ends should report the LPT_RFI alarm.

Handling Procedure
Step 1 Check whether the fiber connections at the local end and at the opposite end are abnormal, the
connector is loose, and the fiber cut occurs. If yes, remove the fault of the fiber. View alarms
on the T2000 to check whether the LPT_RFI alarm is cleared.
If... Then...
Step 2 If the Ethernet ports at both ends report the LPT_RFI alarm, replace the interface boards at both
ends. If only the Ethernet port at one end reports the LPT_RFI alarm, replace the interface board
at the opposite end. After the replacement, view alarms on the T2000 to check whether the
LPT_RFI alarm is cleared.
If... Then...
Step 3 Replace the processing board at the local end. View alarms on the T2000 to check whether the
LPT_RFI alarm is cleared.
If... Then...
Step 4 Replace the processing board at the opposite end.

----End
Related Information
None.
3.76 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the pluggable optical module is not installed.
Attribute
Parameters


table.
Name Meaning
Impact on System
When the LSR_NO_FITED alarm occurs, the pluggable optical module is not installed on the
board. As a result, the board cannot receive and transmit services, and thus the board fails to
function.
Possible Causes
The possible causes of the LSR_NO_FITED alarm are as follows:
l The pluggable optical module is not installed.

Handling Procedure
Step 1 Check whether the pluggable optical module is correctly installed on the board. If not, correctly
install the pluggable optical module on the board.
Step 2 View alarms on the T2000 to check whether the LSR_NO_FITED alarm is cleared.
If... Then...
Step 3 Replace the optical module with a new one of the same type.
Step 4 View alarms on the T2000 to check whether the LSR_NO_FITED alarm is cleared.
If... Then...
Step 5 The service board is faulty. Replace the faulty board. After the new board operates normally,
view alarms on the T2000 to check whether the LSR_NO_FITED alarm is cleared.

If... Then...
CAUTION
----End
Related Information
None.
3.77 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the life of the laser is close to the end.
Attribute
Parameters
table.
Name Meaning

Impact on System
When the LSR_WILL_DIE alarm occurs, the laser is going to stop working and this will affect
the service transmission and receiving. Replace the faulty laser or the service board as soon as
possible.
Possible Causes
The possible causes of the LSR_WILL_DIE alarm are as follows:
l The laser is faulty due to the over high bias current.
l The laser is aging.
Handling Procedure
Step 2 View alarms on the T2000 to check whether the LSR_WILL_DIE alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the LSR_WILL_DIE alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.78 LTI
Description
The LTI is an alarm indicating loss of the synchronization clock source set for the clock board.

Attribute
Parameters
table.
Name Meaning
Parameter 1 0x01: System clock priority table
0x02: The first external clock priority table
0x03: The second external clock priority table
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the LTI alarm occurs, all set synchronization clock sources of the NE fail. The
synchronization is performed based on the internal clock source. As a result, the bit errors may
be received, or the pointer justification occurs, or the alignment signal is lost.
Possible Causes
The possible causes of the LTI alarm are as follows:
l The fiber cut (in the case of tracing the line clock source) or the cable cut (in the case of
tracing the tributary clock source) occurs.
l There is the R_LOS, R_LOF, or R_LOC alarm.
l In the case of tracing the external clock source, there is no input from the external clock
source.
l The synchronization clock source is set to non-revertive, or is blocked, or is incorrectly set.
Handling Procedure
Step 1 Check whether the synchronization clock source traces the clock source that does not exist. If
not, modify the configuration and issue it again.
Step 2 View alarms on the T2000 to check whether the LTI alarm is cleared.

If... Then...
Step 3 If the configuration is correct, check whether the traced synchronization clock source is normal.
If... Then...
The line clock source is traced, and there See the corresponding section in this document
is the R_LOS, R_LOF, or R_LOC alarm to clear the alarm.
on the line board
The tributary clock source is traced, and See the corresponding section in this document
there is the T_ALOS or E1_LOC alarm to clear the alarm.
on the tributary board
The external clock source is traced Check whether the external clock works
normally and whether the cable of the external
clock is properly connected.
Step 4 After ensuring that the synchronization clock source is normal, view alarms on the T2000 to
check whether the LTI alarm is cleared.
If... Then...
alarm is cleared.
If... Then...
After the new board operates normally, view alarms on the T2000 to check whether the LTI
alarm is cleared.
If... Then...

CAUTION
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.102 R_LOC
l 3.117 T_ALOS
l 3.25 E1_LOC
3.79 MAINBD_SUBBD_MISMATCH
Description
The MAINBD_SUBBD_MISMATCH is an alarm indicating the mismatch between the
processing board and the access board.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the MAINBD_SUBBD_MISMATCH alarm occurs, the services will be interrupted.
Possible Causes
The possible causes of the MAINBD_SUBBD_MISMATCH alarm are as follows:
l The types of the access board and the processing board do not match.
l The logical board of the access board is not added.
l The logical board type of the access board is incorrect.
Handling Procedure
Step 1 Check whether the type of the physical access board matches with the type of the physical
processing board on the T2000.
If... Then...
There is a mismatch between the types of the two physical Proceed to the next step.
boards
The type of the physical access board matches that of the Go to step 3.
processing board
Step 2 Replace the access board with a new one that matches the type of the processing board. Or
replace the processing board with a new one that matches the type of the access board. After the
new board starts to work, view alarms on the T2000 to check whether the alarm is cleared.
If... Then...
Step 3 Check whether the logical board of the access board is added on the T2000.
If... Then...
The logical board of the access board is added Go to step 5.
The logical board of the access board is not added Proceed to the next step.
Step 4 Add the logical board of the access board on the T2000. After the new board starts to work, view
If... Then...

If... Then...
Step 5 Check whether the type of the logical access board matches that of the physical access board.
If... Then...
The type of the logical access board does Delete the logical board through commands on the
not match that of the physical access T2000. Return to step 4.
board
The type of the logical access board Contact Huawei engineers for troubleshooting.
matches that of the physical access
board
----End
Related Information
None.
3.80 MDL_ALARM
Description
The MDL_ALARM is an alarm indicating that there is a CAU fault.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the power module number.
0x01: Power module 1
0x02: Power module 2
Parameter 2 0x00

Name Meaning
Parameter 3 Indicates the alarm cause together with parameter 2.
0x01: The module is powered off.
0x02: The module is faulty.
0x03: The protection fails.
0x04: The communication fails.

Impact on System
When the MDL_ALARM alarm occurs, the power supply of the system is affected and thus the
NE will be abnormal.
Possible Causes
The possible causes of the MDL_ALARM alarm are as follows:
l The communication fails.

l The module is powered off.
l The hardware is faulty.
Handling Procedure
View the MDL_ALARM alarm on the T2000. Confirm the cause for the fault of the power
module according to Parameter 3.
If... Then...
The communication fails Find out the failure cause and remove the fault. Check whether
the MDL_ALARM alarm is cleared. If not, replace the CAU.
The module is powered off Power on the module. Check whether the MDL_ALARM alarm
is cleared. If not, replace the CAU.
The hardware is faulty Replace the CAU.
CAUTION
----End

Related Information
None.
3.81 MSAD_CROSSTR
Description
The MS_CROSSTR is an alarm indicating that the number of multiplex section bit errors crosses
the threshold.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
Impact on System
When the MSAD_CROSSTR alarm occurs, the multiplex section adaptation performance count
of the line board crosses the performance threshold in 15 minutes or 24 hours. The services are
affected.
Possible Causes
The possible causes of the MSAD_CROSSTR alarm are as follows:
l The section-level bit errors occur.

l The loop clock is distorted.

Handling Procedure
the board that reports the MSAD_CROSSTR alarm.
If... Then...
Step 2 Check whether the clock tracing in the entire network is correctly set.
If... Then...
The setting is correct Go to step 4.
The setting is not correct Modify the setting of the clock.
Step 3 After ensuring the clock tracing setting of the entire network, wait until the set performance
monitoring period ends. View alarms on the T2000 to check whether the MSAD_CROSSTR
alarm is cleared.
If... Then...
If... Then...
After the performance monitoring period The transmit end of the board at the opposite
ends, the multiplex section adaptation station is faulty. Replace the faulty board.
performance event is reported on the opposite
board
After the performance monitoring period The receive end of the board at the local
ends, the multiplex section adaptation station is faulty. Replace the faulty board.
performance event is reported on the local
board
CAUTION
----End

Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
3.82 MS_AIS
Description
The MS_AIS is an alarm indicating that the last three bits of the K2 byte in the signal received
on the line board are all "1"s.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the MS_AIS alarm occurs, the last three bits of the K2 byte in the signal received at the
optical interface on the line board are all "1"s. As a result, the services are unavailable. If the
automatic MSP switching or the path protection switching is configured, the alarm will trigger
the protection switching.
When the MS_AIS alarm occurs, the board returns the MS_RDI alarm to the opposite station.
Possible Causes
The possible causes of the MS_AIS alarm are as follows:

l The MS_AIS signal is transmitted at the opposite station.

l The receive part at the local station is faulty.
Handling Procedure
Step 1 Check whether the MS_AIS is inserted at the transmit end of the line board of the opposite
station.
If... Then...
The transmit end of the line board at the Cancel the inserted MS_AIS alarm. If the alarm
opposite station is inserted with the is cleared, end the alarm handling. Otherwise,
MS_AIS alarm proceed to the next step.
The transmit end of the line board at the Proceed to the next step.
opposite station is not inserted with the
MS_AIS alarm
Step 2 To check whether the transmit part of the line board at the opposite station is faulty, perform the
selfloop with fibers or the optical interface selfloop. Then check whether the line board at the
opposite station reports the MS_AIS alarm.
If... Then...
The line board of the opposite station is Perform a reset on the board or replace the
faulty board. Then check whether the alarm is
cleared.
The transmit part of the line board at the Proceed to the next step.
opposite station is normal
Step 3 To check the line board at the local station, also perform a selfloop with fibers or an optical
interface selfloop and then check whether the local line board reports the MS_AIS alarm. Check
whether the alarm is cleared by resetting the board.
If... Then...
Step 4 Check whether the alarm is cleared by replacing the board.
If... Then...

CAUTION
----End
Related Information
None.
3.83 MS_CROSSTR
Description
The MS_CROSSTR is an alarm indicating that the multiplex section performance of the signal
received by the line board crosses the threshold.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning
ID.

Impact on System
When the MS_CROSSTR alarm occurs, there are excessive multiplex section performance
events in the signal received at the optical interface on the line board. As a result, the services
at the optical interface are affected.
Possible Causes
The possible cause of the MS_CROSSTR alarm is as follows:
The bit errors occur in the multiplex section.
Handling Procedure
Step 1 View alarms on the T2000 and check whether there are other multiplex section bit error alarms
on the board that reports the MS_CROSSTR alarm.
If... Then...
to clear the alarm.
There are no such alarm as the B2_EXC Proceed to the next step.
and B2_SD
If... Then...
After the performance monitoring period The transmit end of the board at the opposite
ends, the multiplex section performance event station is faulty. Replace the faulty board.
is reported on the opposite board
After the performance monitoring period The receive end of the board at the local
ends, the multiplex section performance event station is faulty. Replace the faulty board.
is reported on the local board
CAUTION
----End
Related Information
l 3.11 B2_EXC
l 3.12 B2_SD
3.84 MS_RDI

Description
The MS_RDI is an alarm indicating that the last three bits of the K2 byte in the signal received
by the line are 110. The MS_RDI is a remote defect failure indication in the multiplex section.
Attribute

Parameters
table.
Name Meaning
Impact on System
When the MS_RDI alarm occurs, the last three bits of the K2 byte in the signal received at the
optical interface on the line board are 110. This alarm is caused by the returned multiplex section
receiving failure from the opposite station. There may be the R_LOS, R_LOC, R_LOF,
MS_AIS, or B2_EXC alarm at the opposite station. As a result, the services at the opposite
station are unavailable.
Possible Causes
The possible causes of the MS_RDI alarm are as follows:
l The opposite station receives the R_LOS, R_LOC, R_LOF, MS_AIS, or B2_EXC alarm.
Handling Procedure
Step 1 View alarms of the opposite station on the T2000. Check whether there is the R_LOC, R_LOS,
R_LOF, MS_AIS, or B2_EXC alarm on the line board at the opposite station.

If... Then...
There is the R_LOS, R_LOC, R_LOF, See the corresponding section in this document
MS_AIS, or B2_EXC alarm to clear the alarm.
There are no such alarms as the R_LOS, Proceed to the next step.
R_LOC, R_LOF, MS_AIS, and B2_EXC
Step 2 If there is no alarm or the corresponding alarm is cleared at the opposite station, the MS_RDI
alarm persists. The line board is faulty. Perform a loopback for the stations at two ends of the
line. Locate and replace the faulty line board.
CAUTION
----End
Related Information
l 3.104 R_LOS
l 3.102 R_LOC
l 3.103 R_LOF
l 3.82 MS_AIS
l 3.11 B2_EXC
3.85 MS_REI
Description
The MS_REI is an alarm indicating that the M1 byte in the signal received by the line contains
the bit error indication returned by the remote multiplex section.
Attribute
Warning Service alarm
Parameters
table.

Name Meaning
Impact on System
When the MS_REI alarm occurs, the signal received at the optical interface on the opposite line
board contains the multiplex section background block error (B2 BBE) and the number of the
background block error is then returned to the local station through the M1 byte.
Possible Causes
The possible causes of the MS_REI alarm are as follows:
l The B2 bit errors are received at the opposite station.
Handling Procedure
Step 1 View alarms of the opposite station on the T2000. Check whether there are B2 bit errors on the
opposite line board.
If... Then...
There are B2 bit errors See the corresponding section in this document to clear the bit
errors.
There are no B2 bit errors Proceed to the next step.
Step 2 If the MS_REI alarm persists when there are no B2 bit errors at the opposite station, perform
the selfloop for the corresponding interface at the local station to check whether the number of
the bit errors in the MS_REI performance event increases. This can identify that the fault occurs
at the transmit end at the local station or at the receive end at the opposite station.
If... Then...
The number of the bit errors no longer The receive end of the board at the opposite
increases station is faulty. Replace the faulty line board.
The number of the bit errors increases The transmit end of the board at the local
station is faulty. Replace the faulty line board.

CAUTION
Step 3 After replacing the line board, view alarms on the T2000 to check whether the MS_REI alarm
is cleared.
If... Then...
alarm is cleared.
If... Then...
cleared.
If... Then...
CAUTION
----End
Related Information
l 3.11 B2_EXC
l 3.12 B2_SD

3.86 MSSW_DIFFRENT
Description
The MSSW_DIFFERENT is an alarm indicating that the active SCC board and the standby SCC
board use different software versions.
Attribute
Major Processing alarm
Parameters
table.
Name Meaning
Parameter 1 00x02: Indicates the running software.
Parameter 2 0x00
Parameter 3 l 0x01: Indicates the first set of nesoft.hwx.
l 0x80: Indicates the first set of ne.ini.
l 0x05: Indicates the second set of nesoft.hwx.
l 0x81: Indicates the second set of ne.ini.
l 0x82: Indicates the first set of diaginfo.ini.
l 0x83: Indicates the second set of diaginfo.ini.
l 0x03: Indicates the basic BIOS. 0x04: Indicates the extended BIOS.
Parameter 4 0x08: Indicates that the active SCC board and the standby SCC board use
different software versions.
Impact on System
When the MSSW_DIFFERENT alarm occurs, it indicates that certain software used by the active
SCC board is different from the software used by the standby SCC board. As a result, the board-
level protection between the two SCC boards is affected.
Possible Causes
The possible causes of the MSSW_DIFFERENT alarm are as follows:

The active SCC board and the standby SCC board use different software versions.
Handling Procedure
Contact Huawei engineers for troubleshooting.
----End
Related Information
None.
3.87 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in the installing state.
Attribute
Critical Processing alarm
Parameters
table.
Name Meaning
Impact on System
When the NESTATE_INSTALL alarm occurs, the NE enters the installing state. As a result, all
boards cannot operate and cannot be normally used.
Possible Causes
The possible causes of the NESTATE_INSTALL alarm are as follows:

l After the NE issues the command for initializing the NE configuration, the check is not
issued or the check fails.
l When the NE is restarted after a power off, the database recovery fails or errors occur in
the database data check.
l The SCC board is faulty.
Handling Procedure
Step 1 Check whether the service configuration is correct. If not, issue the configuration again and
activate the configuration.
Step 2 View alarms on the T2000 to check whether the NESTATE_INSTALL alarm is cleared.
If... Then...
Step 3 Check whether there is the logical board of the cross-connect and timing board. If not, add the
logical board.
Step 4 View alarms on the T2000 to check whether the NESTATE_INSTALL alarm is cleared.
If... Then...
Step 5 The SCC board is faulty. Replace the faulty SCC board.
CAUTION
board.
----End
Related Information
None.
3.88 NO_BD_SOFT

Description
The NO_BD_SOFT is an alarm indicating that the software of the SCC board or the software
of the service board is damaged or does not exist.
Attribute
Parameters
table.
Name Meaning
Parameter 1 0x01
Parameter 2 0x00
Parameter 3 For the SCC board
l 0x01: The first set of NE software (nesoft.hwx)
l 0x05: The second set of NE software
l 0x80: The first set of configuration files
l 0x81: The second set of configuration files
l 0x82: The first set of fault matrix configuration files
l 0x83: The second set of fault matrix configuration files
For other boards:
l 0x01: Loss of board software or logic
Parameter 4 SCC board: 0x01

Other boards: 0xff (reserved)
Impact on System
When the NO_BD_SOFT alarm occurs, the software of the SCC board or the corresponding
software in the flash of the operating file system of the service board does not exist or is damaged.
If the SCC board or the service board restarts after a reset, the board cannot operate normally.
Possible Causes
The possible causes of the NO_BD_SOFT alarm are as follows:

l The original software is deleted and no new software is loaded, or the software is damaged.
l The SCC board or the service board is damaged.
Handling Procedure
Step 1 Load the software again according to alarm parameters. Perform a cold reset on the board that
has reported the NO_BD_SOFT alarm.
Step 2 View alarms on the T2000 to check whether the NO_BD_SOFT alarm is cleared.
If... Then...
Step 3 Replace the SCC board or the faulty board.
If... Then...
CAUTION
l For the SCC board:
protection switching cannot be performed. As a result, the service may be interrupted.
l After replacing the SCC board, ensure that the ID and IP are consistent with that of the
old board.
----End

Related Information
None.
3.89 NO_LSR_PARA_FILE
Description
The NO_LSR_PARA_FILE is an alarm indicating that in the case of the optical module with
the EEPROM being used, no laser parameter files are detected in the EEPROM of the optical
module after the board is started.
Attribute
Parameters
table.
Name Meaning
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the NO_LSR_PARA_FILE alarm occurs, the configuration parameter file of the laser
does not exist in the optical module with the EEPROM after the board is started. Consequently,
the optical module cannot be correctly set and the transmission and receiving of the services on
the board are affected.
Possible Causes
The possible causes of the NO_LSR_PARA_FILE alarm are as follows:


Handling Procedure
Step 2 View alarms on the T2000 to check whether the NO_PARA_FILE alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the NO_LSR_PARA_FILE alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.90 NODEID_MM
Description
The NODEID_MM is an alarm indicating that the MSP node ID mismatch.
Attribute
Parameters

table.
Name Meaning
Impact on System
When the NODEID_MM alarm occurs, the MSP switching fails. If the squelching is enabled,
the squelching function also fails.
Possible Causes
The possible cause of the NODEID_MM alarm is as follows:
The east and west node IDs configured for each node on the MSP ring do not match.
Handling Procedure
Step 1 Check whether the data configuration of the MSP meets the following requirements:
l The configured node IDs configured for any two NEs are not repeated.
l If node A is to the west of its adjacent node B, the local node ID of node A must be the same
as the west node ID of node B, and the local node ID of node B must be the same as the east
node ID of node A.
If... Then...
The data configuration meets the previously Proceed to the next step.
mentioned requirements
The data configuration does not meet the Configure the data again according to the
previously mentioned requirements requirements.
Step 2 Stop and then restart the MSP protocol. View alarms on the T2000 to check whether the
NODEID_MM alarm is cleared.
If... Then...
----End
Related Information
None.

3.91 OUT_PWR_ABN
Description
The OUT_PWR_ABN is an alarm indicating abnormal output optical power of the optical
module.
Attribute
Parameters
table.
Name Meaning
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the OUT_PWR_ABN alarm occurs, the output optical power of the optical module
exceeds the upper threshold or is below the lower threshold. The service bit errors may be
received or the signal cannot be aligned at the opposite station. As a result, the services are
unavailable.
Possible Causes
The possible causes of the OUT_PWR_ABN alarm are as follows:

Handling Procedure

Step 2 View alarms on the T2000 to check whether the OUT_PWR_ABN alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the OUT_PWR_ABN alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.92 OUTPWR_FAIL
Description
The OUTPWR_FAIL is an alarm indicating the output failure of the 3.3 V power supply.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the power supply number. The value is always 0x01.
Impact on System
If one power board reports the alarm, the power supply protection fails to function. If two power
boards both report the alarm, the system cannot operate normally. As a result, the services are
severely affected.
Possible Causes
The possible cause of the OUTPWR_FAIL alarm is as follows:
The power board is faulty.
Handling Procedure
Step 1 Replace the faulty power board.
If... Then...
CAUTION
Replacing the power board that is not configured with 1+1 backup will cause power off and
service interruption. The operation is risky.
----End
Related Information
None.
3.93 P_AIS

Description
The P_AIS is an alarm indicating that the received signals on the PDH side of the E3/T3 tributary
board are all 1s.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the P_AIS alarm occurs, the signals received on the PDH side of the E3/T3 tributary board
are all 1"s, that is, the AIS signal. As a result, the services at the port are unavailable.
Possible Causes
The possible causes of the P_AIS alarm are as follows:
l The transmission cable is faulty.
l The interconnected PDH equipment outputs the AIS signal.
Handling Procedure
Step 1 Check whether the configuration of the connected cables is correct.
If... Then...
The configuration is incorrect Use the correct cables. If the alarm persists, proceed to the
next step.
The configuration is correct Proceed to the next step.
Step 2 Check whether the opposite equipment transmits the AIS signal.

If... Then...
The opposite equipment transmits the AIS Handle the alarms of the opposite station.
signal
The opposite equipment does not transmit Contact Huawei engineers for troubleshooting.
the AIS signal
----End
Related Information
None.
3.94 P_LOS
Description
The P_LOS is an alarm indicating the loss of the signals received on the PDH side of the E3/T3
tributary board.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the P_LOS alarm occurs, the signals received on the PDH side of the E3/T3 tributary
board are lost. As a result, the services at the port are unavailable. If the port that reports the
P_LOS alarm is the current synchronization clock source for the NE, the synchronization clock
source switching occurs.

Possible Causes
The possible causes of the P_LOS alarm are as follows:
l The E3/DS3 services are not accessed.
l The E3/DS3 output interface at the DDF is loose or has fallen off.
l The E3/DS3 input interface at the local station is loose or has fallen off.
l The cable is faulty.
l The switch is reset.
Handling Procedure
Step 1 Confirm the relevant slot number and path number where the alarm occurs on the T2000.
Step 2 Perform a selfloop for the path that reports the P_LOS alarm on the E3/T3 interface board. Check
whether the P_LOS alarm is cleared.
If... Then...
The alarm is cleared The fault does not occur on the local NE. Go to step 4.
Step 3 Check whether the interface board has a good connection. If yes, replace the E3/T3 tributary
board.
CAUTION
Step 4 Perform a selfloop at the transmission equipment side of the DDF to check whether the fault
occurs on the cable between the DDF and the transmission equipment. Check whether the P_LOS
alarm is cleared on the T2000.
If... Then...
The alarm is cleared Proceed to the next step.
The alarm persists The fault occurs to the interface of the DDF and the cable connecting
the DDF to the interface board. Replace the cable.
Step 5 Perform a selfloop at the switch equipment side on the DDF to check whether the fault occurs
on the line between the DDF and the switch equipment or on the switch equipment.
----End
Related Information
None.

3.95 PATCH_ERR
Description
The PATCH_ERR is an alarm indicating that the patch file is incorrect when the NE loads the
path after a reset.
Attribute
Parameters
table.
Name Meaning
Parameter 1 0x00 (reserved)
Impact on System
When the PATCH_ERR alarm occurs, the NE restarts, automatically loads and runs the patch
file, and detects that the path file is incorrect. As a result, the patch cannot be loaded and run,
and functions of the patch are unavailable.
Possible Causes
The possible cause of the PATCH_ERR alarm is as follows:
A patch is running before the NE restarts. After the NE restarts, the patch file is detected incorrect.
Handling Procedure
Step 1 Load the patch file again, and perform a warm reset on the NE.
Step 2 View alarms on the T2000 to check whether the PATCH_ERR alarm is cleared.

If... Then...
Step 3 Check whether the NE software version supports the patch file. If not, load the NE software
according to the version mapping table. Then perform a warm reset on the NE.
Step 4 View alarms on the T2000 to check whether the PATCH_ERR alarm is cleared.
If... Then...
Step 5 Replace the SCC board.
CAUTION
board.
----End
Related Information
None.
3.96 PATCH_NOT_CONFIRM
Description
The PATCH_NOT_CONFIRM is an alarm indicating that confirming the activated path times
out after the NE loads the patch. This alarm is reported if the activated patch is not confirmed.
Attribute


Parameters
table.
Name Meaning
Parameter 1 Indicates the MSB of the patch number.
Parameter 2 Indicates the LSB of the patch number.
Impact on System
When the PATCH_NOT_CONFIRM alarm occurs, confirming the activated patch times out
after the NE loads the patch. As a result, the patch fails to operate and functions of the patch are
unavailable.
Possible Causes
The possible cause of the PATCH_NOT_CONFIRM alarm is as follows:
After a patch is activated, it requires to confirm whether to run this patch in a certain period.
Otherwise, the PATCH_NOT_CONFIRM alarm is reported.
Handling Procedure
Check the loaded patch in the activated status. Issue the patch-active command to run the patch.
----End
Related Information
None.
3.97 PATCHFILE_NOTEXIST
Description
The PATCHFILE_NOTEXIST is an alarm indicating that the patch file does not exist when the
NE loads the patch after a reset.

Attribute

Parameters
table.
Name Meaning
Impact on System
When the PATCHFILE_NOTEXIST alarm occurs, the NE restarts, automatically loads and runs
the patch file, and detects that the patch file does not exist. As a result, the patch cannot be loaded
and run, and functions of the patch are unavailable.
Possible Causes
The possible cause of the PATCHFILE_NOTEXIST alarm is as follows:
A patch is running before the NE restarts. After the NE restarts, the NE automatically loads and
runs the patch, and it detects that the patch file does not exist.
Handling Procedure
Step 1 Load the patch file again, and perform a reset on the NE.
Step 2 View alarms on the T2000 to check whether the PATCHFILE_NOTEXIST alarm is cleared.
If... Then...
Step 3 Replace the SCC board.

CAUTION
board.
----End
Related Information
None.
3.98 POWER_FAIL
Description
The POWER_FAIL is an alarm indicating the power supply failure.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the overvoltage or undervoltage.
l 0x12: Input overvoltage of the -48 V active power supply
l 0x13: Input undervoltage of the -48 V active power supply
l 0x24: Output overvoltage of the 3 V power supply
l 0x25: Output undervoltage of the 3 V power supply

Name Meaning
Impact on System
When the POWER_FAIL alarm occurs, the power module of the NE is faulty. As a result, the
normal operation of the NE is affected.
Possible Causes
The possible cause of the POWER_FAIL alarm is as follows:
The power supply is faulty.
Handling Procedure
Step 1 Replace the power board that reports the POWER_FAIL alarm.
Step 2 View alarms on the T2000 to check whether the POWER_FAIL alarm is cleared.
If... Then...
CAUTION
You need to power off the NE when replacing the power board of the NE. This will interrupt
the services on the NE if there is no 1+1 backup for the power supply board. The operation is
risky.
----End
Related Information
None.
3.99 PROTECT_MODE
Description
The PROTECT_MODE is an alarm indicating that the system database is in the protection mode.
When the resetting times of the NE software reach the threshold value (15 times by default), the
database enters the protection mode and the PROTECT_MODE alarm is reported.

Attribute

Parameters
table.
Name Meaning
Impact on System
When the PROTECT_MODE alarm occurs, the system is abnormal. To protect the service
configuration data in the database, the database enters the protection mode and this can avoid
that the data is illegally overwritten.
This alarm may interrupt services.
Possible Causes
The possible cause of the PROTECT_MODE alarm is as follows:
The SCC board is abnormally running.
Handling Procedure
Step 1 Perform a reset on the NE.
Step 2 View alarms on the T2000 to check whether the PROTECT_MODE alarm is cleared.
If... Then...
The alarm persists Replace the SCC board and check whether the PROTECT_MODE
alarm is cleared. If not, contact Huawei engineers for troubleshooting.
----End

Related Information
None.
3.100 PWR_MAJ_ALM
Description
The PWR_MAJ_ALM is an alarm indicating that the voltage of the power module of the NE is
over low or over high.
Attribute
Critical Environmental alarms
Parameters
table.
Name Meaning
Parameter 3 0x00: Power off
0x01: Undervoltage
0x02: Overvoltage

Impact on System
When the PWR_MAJ_ALM occurs, the voltage of the NE power module is over low or over
high. The normal operation of the NE is severely affected. Hence, emergent handling is required.
Possible Causes
The possible cause of the PWR_MAJ_ALM alarm is as follows:
The input power is abnormal.

Handling Procedure
Step 1 Check whether the thresholds of the severe over-voltage and severe under-voltage are correct.
Check whether the input voltage of the power that reports alarms is over or under the preset
value.
Step 2 Set the correct input voltage. View alarms on the T2000 to check whether the PWR_MAJ_ALM
alarm is cleared.
If... Then...
Step 3 Replace the power supply module of the NE.
CAUTION
----End
Related Information
None.
3.101 R_FIFO_E
Description
The R_FIFO_E is an alarm indicating that the FIFO received on the PDH side of the E3/T3
tributary board overflows.
Attribute
Parameters
table.

Name Meaning
Impact on System
When the R_FIFO_E alarm occurs, the receiving FIFO on the PDH side of the E3/T3 tributary
board overflows. As a result, the services received at the port are unavailable.
Possible Causes
The possible causes of the R_FIFO_E alarm are as follows:
l The E3/T3 tributary board is faulty.

l The E3/T3 tributary board or the cross-connect and timing board at the upstream station is
faulty.
Handling Procedure
Step 1 Replace the E3/T3 tributary board.
CAUTION
Step 2 After the board operates normally, view alarms on the T2000 to check whether the T_FIFO_E
alarm is cleared.
If... Then...

If... Then...
CAUTION
Step 4 The E3/T3 tributary board or the cross-connect and timing board at the upstream station is faulty.
Replace the faulty board.
----End
Related Information
None.
3.102 R_LOC
Description
The R_LOC is an alarm indicating the loss of the clock in the signals received by the line board
at the optical interface.
Attribute

Parameters
table.

Name Meaning
Impact on System
When the R_LOC alarm occurs, the clock in the signals received by the line board at the optical
interface is lost. As a result, the services at the optical interface are unavailable. If the automatic
MSP switching or the path protection switching is configured, the alarm will trigger the
protection switching. If the optical interface that reports the R_LOC alarm is the current
synchronization clock source for the NE, the synchronization clock source switching will occur.
When the R_LOC alarm occurs, the board returns the MS_RDI alarm to the opposite station.
Possible Causes
The possible causes of the R_LOC alarm are as follows:
l The clock in the received line signals is lost.
Handling Procedure
Step 1 Perform a selfloop for the optical interfaces on the upstream line board. Check whether there is
the R_LOC alarm on the upstream line board.
If... Then...
There is the alarm on the upstream line Replace the upstream line board. Proceed to
board the next step.
There is not such alarm on the upstream line Proceed to the next step.
board
Step 2 Remove the fault of the upstream board. View alarms on the T2000 to check whether the R_LOC
alarm is cleared.
If... Then...
Step 3 The receive part of the local line board is faulty. Replace the faulty board.

CAUTION
Step 4 View alarms on the T2000 to check whether the R_LOC alarm is cleared.
If... Then...
----End
Related Information
None.
3.103 R_LOF
Description
The R_LOF is an alarm indicating the loss of frame in the signals received by the line board at
the optical interface.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the R_LOF alarm occurs, the frame in the signals received by the line board at the optical
interface is lost. As a result, the services at the interface are unavailable. If the automatic MSP
switching or the path protection switching is configured, the alarm will trigger the protection
switching. If the optical interface that reports the R_LOF alarm is the current synchronization
clock source for the NE, the synchronization clock source switching will occur.
When the R_LOF alarm occurs, the board returns the MS_RDI alarm to the opposite station.
Possible Causes
The possible causes of the R_LOF alarm are as follows:

l The signals transmitted at the opposite station do not have the frame structure.
l The rate level of the optical interface at the receive end does not match that of the received
optical signals.
Handling Procedure
Step 1 Check whether the rate levels of the optical interface at the local station and the received optical
signals match.
If... Then...
The rate levels do not match Replace the line board so that the rate level of its optical
interface matches that of the received optical signals.
The rate levels match Proceed to the next step.
Step 2 Check whether the fibers are intact and whether the fiber connectors are connected properly.
Clean the fiber connectors.
Step 3 Remove the fault of the fibers. View alarms on the T2000 to check whether the R_LOF alarm
is cleared.
If... Then...
If... Then...
The opposite board reports the alarm The transmit end of the board at the opposite station
is faulty. Replace the faulty board.

If... Then...
The local board reports the alarm The receive end of the board at the local station is
faulty. Replace the faulty board.
CAUTION
----End
Related Information
None.
3.104 R_LOS
Description
The R_LOS is an alarm indicating the loss of signal at the receive optical interface on the line
board.
Attribute
Parameters
table.
Name Meaning

Impact on System
When the R_LOS alarm occurs, the signal at the receive optical interface on the line board is
lost. As a result, the services are interrupted. If the automatic MSP switching or the path
protection switching is configured, the alarm will trigger the protection switching. If the optical
interface that reports the R_LOS alarm is the current synchronization clock source for the NE,
the synchronization clock source switching will occur.
When the R_LOS alarm occurs, the board returns the MS_RDI alarm to the opposite station.
Possible Causes
The possible causes of the R_LOS alarm are as follows:
l The alarm reversion of the optical interface is enabled.

l The fiber cut occurs to the connected fibers.
l The line is attenuated to a great extent or the optical power is overloaded.
l The transmit part at the opposite station is faulty, and the line transmission fails.
Handling Procedure
Step 1 Check whether the optical interface is configured with the alarm reversal. If yes, cancel the alarm
reversal. Then check whether the R_LOS alarm is cleared.
If... Then...
Step 2 Check whether the fibers are intact and whether the fiber connectors are connected properly.
Step 3 Remove the fault of the fibers. View alarms on the T2000 to check whether the R_LOS alarm
is cleared.
If... Then...
If... Then...
The opposite board reports the alarm The transmit end of the board at the opposite station
is faulty. Replace the faulty board.
The local board reports the alarm The receive end of the board at the local station is
faulty. Replace the faulty board.

CAUTION
----End
Related Information
None.
3.105 R_OOF
Description
The R_OOF is an alarm indicating that the frame header cannot be identified for five consecutive
frames in the received signals of the line board. The board enters the out-of-frame state.
Attribute
Parameters
table.
Name Meaning
Impact on System
The R_OOF is an alarm indicating that the frame header cannot be identified for five 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 3 ms, the loss-of-frame state is entered. The equipment generates
the R_LOF alarm indicating the loss of frame.
Possible Causes
The possible causes of the R_OOF alarm are as follows:

l The bit errors in the transmission are excessive.
l The synchronization clock source is severely out of synchronization.
Handling Procedure
Step 1 Check whether the fibers are intact and whether the fiber connectors have a good connection.
Step 2 Remove the fault of the fibers. View alarms on the T2000 to check whether the R_OOF alarm
is cleared.
If... Then...
Step 3 Perform a selfloop at the opposite station. If the R_OOF alarm persists, it indicates that the line
board at the opposite station is faulty. Replace the faulty line board.
Step 4 Remove the fault of the opposite line board. View alarms on the T2000 to check whether the
R_OOF alarm is cleared.
If... Then...
Step 5 Trace the clock source of high quality.
Step 6 After rectifying the fault of the clock source, view alarms on the T2000 to check whether the
R_OOF alarm is cleared.
If... Then...
Step 7 Replace the local line board.

CAUTION
Step 8 View alarms on the T2000 to check whether the R_OOF alarm is cleared.
If... Then...
alarm is cleared.
If... Then...
CAUTION
Step 11 After the board operates normally, view alarms on the T2000 to check whether the alarm is
cleared.
If... Then...
----End
Related Information
None.

3.106 RELAY_ALARM
Description
The RELAR_ALARM is an alarm indicating that the alarm input/output status of the orderwire
board changes.
Attribute

Critical Environmental alarms
Parameters
table.
Name Meaning
Parameter 1 Indicates the alarm input/output number. The value range is 1–3.
Parameter 2 0x00
Parameter 3 0x01
Impact on System
The alarm input/output status changes. The services, however, are not affected.
Possible Causes
The possible cause of the RELAY_ALARM alarm is as follows:
The monitored input/output status changes.
Handling Procedure
Check whether the status of the equipment monitored by the alarm input/output changes. Handle
it accordingly.
----End

Related Information
The alarm input/output includes the alarm input and alarm output.
The alarm input is mainly used to monitor the status of the external equipment. The external
equipment can be the NE, temperature, humidity, smoke, or air conditioner.
The alarm output is mainly used to indicate the alarms and control the external equipment. The
alarm indication uses the alarm output settings to transmit the alarm status of the NE. The alarm
status can be transmitted to the alarm indicators or the upper monitoring NE to facilitate
monitoring the alarms of the NE. Controlling the external equipment uses the alarm output to
turn on or turn off the external equipment.
3.107 RINGMAPM_MM
Description
The RINGMAPM_MM is an alarm indicating the generation mode mismatch of the ring map.
Attribute
Minor Processing alarm
Parameters
table.
Name Meaning
Parameter 2 Indicates the logical direction.
Impact on System
The node map of a ring cannot be created, and thus the squelch function fails.
Possible Causes
The possible cause of the RINGMAPM_MM alarm is as follows:
The generation mode of the ring map at each node on the MSP ring is different.

Handling Procedure
Step 1 Perform a reset on the generation mode configuration of the squelch ring map. Configure the
generation mode of the ring map at each node on the ring so that they are consistent.
If... Then...
----End
Related Information
None.
3.108 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that the regenerator section performance of the line
board crosses the threshold.
Attribute

Minor Service alarm
Parameters
table.
Name Meaning

Name Meaning
ID.
Impact on System
When the RS_CROSSTR alarm occurs, the regenerator section performance of the line board
crosses the threshold. As a result, the services are affected.
Possible Causes
The possible cause of the RS_CROSSTR alarm is as follows:
The bit errors occur in the regenerator section.
Handling Procedure
Step 1 View alarms on the T2000 to check whether there are other regenerator section bit error alarms
on the board that reports the RS_CROSSTR alarm.
If... Then...
to clear the alarm.
There are not such alarm as the B1_EXC Proceed to the next step.
and B1_SD
If... Then...
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD

3.109 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock reference source of the clock board
is switched in the S1 byte mode.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the clock source type.
0x01: The switching of the clock source traced by the system occurs.
0x02: The switching of the 2M phase-locked source occurs
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the S1_SYN_CHANGE alarm occurs, the clock reference source of the clock board is
switched to other synchronization clock sources in the S1 byte mode, due to the failure of the
line source or tributary source or external clock source that is set in the clock source priority
table.
Possible Causes
The possible causes of the S1_SYN_CHANGE alarm are as follows:
l The fiber cut or the cable cut occurs.

l The clock switching occurs at the uplink station.

Handling Procedure
Step 1 View alarms on the T2000 to check whether there are alarms that are generated on the local NE
due to the causes mentioned earlier.
If... Then...
There is the R_LOS, R_LOC, R_LOF, See the corresponding section in this
T_ALOS, or EXT_SYNC_LOS alarm... document to clear the alarm.
There are such alarms as the MS_AIS and See the corresponding section in this
B2_EXC, and these alarms are set as document to clear the alarm.
conditions that can trigger the clock switching
There is no alarm Proceed to the next step.
Step 2 The clock source protection switching occurs in the network. Check the clock source switching
status in the network on the T2000. Check whether there are alarms that can trigger the clock
source switching on the upstream NE. If yes, handle these alarms.
----End
Related Information
l 3.104 R_LOS
l 3.102 R_LOC
l 3.103 R_LOF
l 3.82 MS_AIS
l 3.11 B2_EXC
l 3.117 T_ALOS
l 3.28 EXT_SYNC_LOS
3.110 SECU_ALM
Description
The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Attribute
Major Security alarm
Parameters
table.

Name Meaning
Impact on System
When the SECU_ALM occurs, an illegal user attempts to log in to the NE. When the password
to a user account is incorrectly entered three times, the user account is blocked temporarily. After
two minutes, the user can log in to the NE again.
Possible Causes
The possible cause of the SECU_ALM alarm is as follows:
The password is incorrectly entered three times.
Handling Procedure
Obtain the correct password from the administrator. After the user account is unlocked, use the
correct password to log in.
----End
Related Information
None.
3.111 SNCP_FAIL
Description
The SNCP_FAIL is an indication alarm of SNCP switching failure. This alarm indicates that
the switching action fails after the switching of the SNCP group.
Attribute
Parameters

table.
Name Meaning
Parameter 1 Indicates the MSB of the SNCP group ID.
Parameter 2 Indicates the LSB of the SNCP group ID.
Impact on System
The services protected by the SNCP are interrupted.
Possible Causes
The possible cause of the SNCP_FAIL alarm is as follows:
The abnormal operation of the SCC board causes the failure of the SNCP switching.
Handling Procedure
Step 1 Reset the NE.
Step 2 View alarms on the T2000 to check whether the SNCP_FAIL alarm is cleared and whether the
switching can be normally implemented.
If... Then...
----End
Related Information
None.
3.112 SNCP_INDI
Description
The SNCP_INDI is an alarm indicating the SNCP switching. This alarm indicates that the
switching action is already performed after the switching of the SNCP group.

Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the MSB of the SNCP group ID.
Parameter 2 Indicates the LSB of the SNCP group ID.
Impact on System
When the SNCP_INDI alarm occurs, the relevant SNCP group already enters the switching state
and the services of it are protected.
Possible Causes
The possible cause of the SNCP_INDI alarm is as follows:
The SNCP group enters the switching state.
Handling Procedure
Step 1 Query causes for the SNCP switching and remove the fault in the working path of the SNCP. If
the switching is of a manual switching triggered by the SNCP external command, issue the
corresponding command to switch the services to the original working path.
Step 2 View alarms on the T2000 to check whether the SNCP_INDI alarm is cleared.
If... Then...
----End
Related Information
None.

3.113 SQUTABM_MM
Description
The SQUTABM_MM is an alarm indicating the squelch table mode mismatch.
Attribute
Parameters
table.
Name Meaning
Parameter 2 Indicates the logical direction.
Impact on System
The squelch service cannot be correctly created, and thus the squelch function fails.
Possible Causes
The possible cause of the SQUTABM_MM alarm is as follows:
The generation mode of the squelch table at each node on the MSP ring is different.
Handling Procedure
Step 1 Reset the generation mode of the squelch services. Configure the generation mode of the squelch
table at each node on the ring so that it is the same.
If... Then...

If... Then...
----End
Related Information
None.
3.114 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the clock source of the clock board that is set in
the clock source priority table is lost.
Attribute
Warning Equipment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the slot number.
Parameter 2 Indicates the path number or the optical interface number.
Impact on System
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 When the higher-level clock source is unavailable, it indicates that 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).
l The clock source switching in the S1 byte mode occurs at the local station.
l The input of the external clock source (BITS) changes.
Handling Procedure
Step 1 View alarms on the T2000 to check whether there are alarms that are caused by the loss of clock
source on the local NE.
If... Then...
There is the R_LOS, R_LOC, R_LOF, or See the corresponding section in this document
T_ALOS alarm to clear the alarm.
There is no alarm Proceed to the next step.
Step 2 View alarms on the T2000 to check whether the SYNC_C_LOS alarm is cleared.
If... Then...
Step 3 If the priority level of the clock source is lost or is incorrectly configured, configure the clock
source priority table again.
Step 4 View alarms on the T2000 to check whether the SYNC_C_LOS alarm is cleared.
If... Then...
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.
See the S1_SYN_CHANGE.
----End
Related Information
l 3.104 R_LOS
l 3.102 R_LOC
l 3.103 R_LOF
l 3.117 T_ALOS
l 3.109 S1_SYN_CHANGE
3.115 SYNC_FAIL

Description
The SYNC_FAIL is an alarm indicating that the data synchronization between the active SCC
board and the standby SCC board fails.
Attribute

Parameters
table.
Name Meaning
Parameter 1 l 0x1f: The failure to back up the databases causes the failure to back up data
in batches.
l 0x20: The failure to verify the software versions used by the active and the
standby SCC boards causes the failure to back up data in batches.
l 0x21: A communication failure between the active SCC board and the standby
SCC board causes the failure to back up data in batches.
Impact on System
When the SYNC_FAIL alarm occurs, it indicates that the data synchronization between the
active SCC board and the standby SCC board fails. As a result, the data cannot be backed up
and the protection switching cannot be realized between the active SCC board and the standby
SCC board.
Possible Causes
The possible cause of the SYNC_FAIL alarm is as follows:
The software used by the standby SCC board is operating abnormally. The communication
between the active SCC board and the standby SCC board is abnormal. The active SCC board
and the standby SCC board use different software versions.

Handling Procedure
Step 1 Check the versions of the NE software on the T2000.
If... Then...
If the versions of the NE software are different Upgrade or downgrade the NE software.
If the versions of the NE software are the same Proceed to the next step.
Step 2 Check the communication between the active SCC board and the standby SCC board
If... Then...
If the communication between the active SCC board and the See COMMUN_FAIL.
standby SCC board fails
If the communication between the active SCC board and the Proceed to the next step.
standby SCC board is normal
Step 3 Check the backup of the database.
If... Then...
The database backup fails. Reset the standby SCC board. After the standby SCC
board starts to work normally, if the SYNC_FAIL alarm
is cleared, the fault is rectified.
The database backup is normal. Contact Huawei engineers for troubleshooting.
----End
Related Information
3.22 COMMUN_FAIL
3.116 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the current synchronization clock source of the clock
board is degraded.
Attribute
Parameters

table.
Name Meaning
Impact on System
When the SYN_BAD alarm occurs, the current synchronization clock source of the clock board
is degraded. As a result, system service transmission and receiving are affected.
Possible Causes
The possible cause of the SYN_BAD alarm is as follows:
The quality of the traced synchronization clock source is degraded.
Handling Procedure
Step 1 Check whether there are bit error and pointer justification performance events in the direction
of the traced clock source. Handle them As a result.
If... Then...
There are B1 bit error, B2 bit error and See the corresponding section in this document
pointer justification performance events to clear the alarm.
There is no such performance event Proceed to the next step.
Step 2 Check the setting of the clock source tracing. Avoid the clock tracing loop when configuring
the clock tracing.
Step 3 After rectifying the fault of the clock source tracing, view alarms on the T2000 to check whether
the SYN_BAD alarm is cleared.
If... Then...
alarm is cleared.
If... Then...

If... Then...
cleared.
If... Then...
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.81 MSAD_CROSSTR
3.117 T_ALOS
Description
The T_ALOS is an alarm indicating that the loss of the analog signal at the electrical interface
on the E1/T1 tributary board.
Attribute


Parameters
table.
Name Meaning
Impact on System
When the T_ALOS alarm occurs, the analog signal received at the interface on the E1/T1
tributary board is lost. As a result, the lower order service at the interface are unavailable. If the
port that reports the T_ALOS alarm is the current synchronization clock source for the NE, the
synchronization clock source switching occurs.
When the T_ALOS alarm occurs, the tributary board inserts the all "1"s signals in the upper-
level circuit.
Possible Causes
The possible causes of the T_ALOS alarm are as follows:
l The alarm reversal is configured in the electrical interface.

l The port of the cable is loose, or has fallen off.
l The cable is faulty.
l The services are not accessed.
l The interconnected equipment is faulty.
l The E1/T1 board is faulty.
Handling Procedure
Step 1 Check whether the alarm reversal is configured on the electrical interface. If yes, cancel the
alarm reversal and then check whether the T_ALOS alarm is cleared.
If... Then...
Step 2 Check whether the connectors of the cable at both ends are inserted firmly and whether the cables
are intact.

Step 3 After rectifying the fault of the cables, view alarms on the T2000 to check whether the T_ALOS
alarm is cleared.
If... Then...
Step 4 Check whether the service transmission of the interconnected equipment is normal and whether
the equipment is faulty.
Step 5 After rectifying the fault of the interconnected equipment, view alarms on the T2000 to check
whether the T_ALOS alarm is cleared.
If... Then...
Step 6 The local E1/T1 board is faulty. Replace the faulty board.
CAUTION
----End
Related Information
None.
3.118 T_FIFO_E
Description
The T_FIFO_E is an alarm indicating that the transmitting FIFO on the PDH side of the E3/T3
tributary board overflows.
Attribute
Parameters


table.
Name Meaning
Impact on System
When the T_FIFO_E alarm occurs, the transmitting FIFO on the PDH side of the E3/T3 tributary
board overflows. As a result, the services transmitted from the port are unavailable.
Possible Causes
The possible causes of the T_FIFO_E alarm are as follows:
l The E3/T3 tributary board is faulty.

Handling Procedure
Step 1 Replace the E3/T3 tributary board.
CAUTION
Replacing the E3/T3 tributary board will interrupt the services on the board. The operation is
risky. When replacing the E3/T3 tributary board, ensure that the type of the signal received on
the new board is consistent with that of the board to be replaced.
Step 2 After the board operates normally, view alarms on the T2000 to check whether the T_FIFO_E
alarm is cleared.
If... Then...

If... Then...
CAUTION
----End
Related Information
None.
3.119 T_LOC
Description
The T_LOC is an alarm indicating that the clock of the signal in the transmit direction of the
line board is lost.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the T_LOC alarm occurs, the clock of the signal on the transmit side of the line board is
lost. As a result, the services transmitted from the optical interface are unavailable.
Possible Causes
The possible causes of the T_LOC alarm are as follows:

l The line board is faulty.
Handling Procedure
Step 1 Replace the line board.
CAUTION
Step 2 View alarms on the T2000 to check whether the T_LOC alarm is cleared.
If... Then...
alarm is cleared.
If... Then...
After the new board operates normally, view alarms on the T2000 to check whether the T_LOC
alarm is cleared.

If... Then...
CAUTION
----End
Related Information
None.
3.120 T_LOS
Description
The T_LOS is an alarm indicating that no signal is input on the transmit side of the line board.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the T_LOS alarm occurs, there is no signal input on the transmit side of the line board.
As a result, the services transmitted from the optical interface are unavailable.
Possible Causes
The possible causes of the T_LOS alarm are as follows:
l The line board is faulty.
Handling Procedure
Step 1 Check the service configuration of the line board, if the service is not configured or is incorrectly
configured, proceed to the next step. If the configuration is correct, go to step 3.
Step 2 Configure the services to be transmitted from the line board again. View alarms on the T2000
to check whether the T_LOS alarm is cleared.
If... Then...
Step 3 Replace the optical module first. If the service is normal, end the alarm handling. If the service
is abnormal, replace the board.
CAUTION
Step 4 View alarms on the T2000 to check whether the T_LOS alarm is cleared.
If... Then...
alarm is cleared.

If... Then...
After the new board operates normally, view alarms on the T2000 to check whether the T_LOS
alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.121 TC_DEG
Description
The TC_DEG is a degraded signal indication alarm in the tandem connection. If the number of
B3 bit errors in the tandem connection monitoring section exceeds the specified TC_DEG
threshold value, the TC_DEG alarm is reported.
Attribute
Minor Service alarm
Parameters


table.
Name Meaning
Impact on System
When the TC_DEG alarm occurs, bit errors are detected in the tandem connection monitoring
section and in the output services.
When the TC_DEG alarm occurs, the TCM sink end returns the TC_REI through the N1 byte
to the TCM source end.
Possible Causes
The possible causes of the TC_DEG alarm are as follows:
l The higher-level bit error alarm occurs at the TCM source end or the TCM sink end.
l The receive part at the sink end is faulty.
l The transmit part at the source end is faulty.
l The performance of other carrier network that the services pass is degraded.
Handling Procedure
Step 1 Check whether there are the higher-level bit error alarms, such as the B1_EXC, B2_EXC,
B3_EXC, B1_SD, B2_SD, and B3_SD, at the source end or the sink end. If yes, first clear the
alarms. In addition, clean the fiber heads, and ensure the fiber connectors are inserted firmly.
Then check whether the TC_DEG alarm at the local station is cleared.
If... Then...
There is the B1_EXC, B2_EXC, B3_EXC, First clear these alarms. Clean the fiber heads
B1_SD, B2_SD, or B3_SD alarm and ensure that the fiber connectors are firmly
There are not such alarms as the B1_EXC, Go to step 3.
B2_EXC, B3_EXC, B1_SD, B2_SD, and
B3_SD

Step 2 Check whether the transmit board at the source end is faulty. If yes, perform a cold reset on the
corresponding line board at the source end. Check whether the TC_DEG alarm is cleared.
If... Then...
Step 3 Replace the line board at the source end. Then check whether the TC_DEG alarm is cleared.
If... Then...
Step 4 Check whether the receive board at the sink end is faulty. If yes, perform a cold reset on the line
board that reports the alarm at the sink end. Check whether the TC_DEG alarm is cleared.
If... Then...
Step 5 Replace the line board that reports the alarm at the sink end. Then check whether the TC_DEG
alarm is cleared.
If... Then...
Step 6 If the alarm persists, it indicates the performance of other carrier networks through which the
services pass may be degraded. In this case, contact the relevant carrier for troubleshooting.
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC

l 3.15 B3_SD
3.122 TC_EXC
Description
The TC_EXC is an alarm indicating excessive bit errors in the tandem connection. When the
number of B3 bit errors in the tandem connection monitoring section exceeds the specified
threshold value, the TC_EXC alarm is reported.
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Impact on System
When the TC_EXC alarm occurs, severe bit errors are detected in the tandem connection
monitoring section and in the output services.
When the TC_EXC alarm occurs, the TCM sink end returns the TC_REI through the N1 byte
to the TCM source end.
Possible Causes
The possible causes of the TC_EXC alarm are as follows:
l The higher-level bit error alarm occurs at the TCM source end or the TCM sink end.


l The performance of other carrier networks through which the services pass is degraded.
Handling Procedure
B3_EXC, B1_SD, B2_SD, or B3_SD at the source end.
If... Then...
B3_SD
Step 2 Replace the line board at the source end. Then check whether the TC_EXC alarm is cleared.
If... Then...
Step 3 Check whether there is the higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC,
B1_SD, B2_SD, or B3_SD, detected at the sink end.
If... Then...
B3_SD
Step 4 Replace the line board that reports the alarm at the sink end. Then check whether the TC_EXC
alarm is cleared.
If... Then...
Step 5 If the alarm persists, the performance of other carrier networks through which the services pass
may be degraded. In this case, contact the relevant carrier for troubleshooting.

CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC
l 3.15 B3_SD
3.123 TC_INCAIS
Description
The TC_INCAIS is an input indication alarm in the tandem connection. When the four most
significant IEC bits of the N1 byte in five consecutive frames received at the TCM sink end are
1110, the TC_INCAIS alarm is reported.
Attribute
Parameters
table.
Name Meaning

Name Meaning
Impact on System
When the TC_INCAIS alarm occurs, the services transmitted in the path are interrupted.
When the TC_INCAIS alarm occurs, by default, the system inserts the AU_AIS alarm in the
downstream station. At the same time, the TCM sink end returns the TC_ODI alarm through the
N1 byte to the TCM source end.
Possible Causes
The possible causes of the TC_INCAIS alarm are as follows:
l The higher-level alarms are received at the TCM source end.

l The services are incorrectly configured.
l The board that does not fully support the TCM Option2 function is used at the TCM source
end or sink end.
Handling Procedure
Step 1 Check whether there is the R_LOS, R_LOF, MS_AIS, AU_AIS, or AU_LOP alarm that can
trigger the AIS insertion at the TCM source end.
If... Then...
There is the alarm that can trigger the AIS First clear the previously mentioned alarms.
insertion Then check whether the TC_INCAIS alarm is
There are not such alarms that can trigger Proceed to the next step.
the AIS insertion
If... Then...
The service level is incorrectly configured Modify the service level, and check whether the
TC_INCAIS alarm is cleared. If not, proceed to
the next step.
The service level is correctly configured Proceed to the next step.
Step 3 Check whether the TCM source end and sink end fully support the TCM Option2 function. If
not, use the board that fully supports the TCM Option2 function.

If... Then...
The TCM source and sink do not support Use the board that supports the TCM Option2
the TCM Option2 function completely. function. Then check whether the TC_INCAIS
alarm is cleared. If not, contact Huawei
engineers for troubleshooting.
The TCM source and sink support the Proceed to the next step.
TCM Option2 function
Step 4 Replace the line board at the source end. Then check whether the TC_INAIS alarm is cleared.
If... Then...
Step 5 Replace the line board that reports the alarm at the sink end. Then check whether the TC_DEG
alarm is cleared.
If... Then...
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.82 MS_AIS
l 3.7 AU_AIS
l 3.8 AU_LOP
3.124 TC_LTC
Description
The TC_LTC is an alarm indicating the loss of multiframe header 72 in the tandem connection.
Attribute
Parameters


table.
Name Meaning
Impact on System
When the TC_LTC alarm occurs, the TCM function is disabled. When the TC_LTC alarm
occurs, the TCM sink end returns the TC_RDI and TC_ODI alarms through the N1 byte to the
TCM source end. If the AU_AIS alarm is set inserted when the TC_LTC alarm occurs, the
system automatically inserts the AU_AIS alarm in the downstream station.
Possible Causes
The possible causes of the TC_LTC alarm are as follows:
l The higher-level alarms are received at the TCM source end or sink end.
end or sink end.
Handling Procedure
If... Then...
to clear the alarm.
and B1_SD
Step 2 Check whether the receive optical power is normal.
If... Then...
The optical power is over low First check whether the fibers are intact, the fiber connectors
are not clean, and the transmit optical power of the opposite
line board is normal.
The optical power is normal Proceed to the next step.

Step 3 Check whether the working temperature is over high or over low. Check whether any threshold-
cross alarm occurs on the board.
If... Then...
The working temperature is over high or In the case of over high working temperature,
over low add the cooling device to the NE. In the case
of the over low working temperature, add the
heating device to the NE.
The working temperature is normal Proceed to the next step.
Step 4 Check whether the clock source at the local station is correctly configured. If not, modify or set
the synchronous clock source again.
Step 5 View alarms on the T2000 to check whether the TC_LTC alarm is cleared.
If... Then...
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
3.125 TC_ODI
Description
The TC_ODI is an alarm indicating an output defect in the tandem connection. When the TCM
sink end receives five consecutive frames that contains the N1 byte, showing the TC_ODI
indication (bit 7 of the 74th frame is 1), the TC_ODI alarm is reported.

Attribute

Parameters
table.
Name Meaning
Impact on System
When the TC_ODI alarm occurs, the system is not affected. This alarm only indicates that some
faults occur at the TCM sink end.
Possible Causes
The possible cause of the TC_ODI alarm is as follows:
There is the TC_UNEQ, TC_TIM, TC_LTC, or TC_INCAIS alarm at the sink end.
Handling Procedure
The TC_ODI alarm is an accompanying alarm. When the line board at the TCM sink end reports
the TC_UNEQ, TC_TIM, TC_LTC, or TC_INCAIS alarm, it returns a TC_ODI to the TCM
source end. After the alarm at the TCM sink end is cleared, the TC_ODI alarm is automatically
cleared.
----End
Related Information
l 3.130 TC_UNEQ
l 3.129 TC_TIM
l 3.124 TC_LTC
l 3.123 TC_INCAIS

3.126 TC_OEI
Description
The TC_OEI is an alarm indicating output bit errors in the tandem connection. When the
accumulated number of the output bit errors of the tandem connection received at the sink end
within one second is greater than 0, the TC_OEI alarm is reported.
Attribute

Warning Communication alarm
Parameters
table.
Name Meaning
Impact on System
When the TC_OEI alarm occurs, the system is not affected. This alarm only shows that some
bit errors occur in the output of the TCM sink end.
Possible Causes
The possible cause of the TC_OEI alarm is as follows:
Bit errors occur in the TCM source or sink end.
Handling Procedure

If... Then...
B3_SD
Step 2 Replace the line board at the source end. Then check whether the TC_OEI alarm is cleared.
If... Then...
If... Then...
B3_SD
Step 4 Replace the line board that reports the alarm at the sink end. Then check whether the TC_OEI
alarm is cleared.
If... Then...
CAUTION
----End

Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC
l 3.15 B3_SD
3.127 TC_RDI
Description
The TC_RDI is an alarm indicating a remote defect in the tandem connection. When the TCM
sink end receives five consecutive frames that contain the N1 byte, showing the TC_RDI
indication (bit 8 of the 73rd frame is 1), the TC_RDI alarm is reported.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the TC_RDI alarm occurs, the system is not affected. This alarm only indicates that some
Possible Causes
The possible cause of the TC_RDI alarm is as follows:

There is the TC_UNEQ, TC_TIM, or TC_LTC alarm at the sink end.
Handling Procedure
The TC_RDI alarm is an accompanying alarm. When the line board at the TCM sink end reports
the TC_UNEQ, TC_TIM, or TC_LTC alarm, it returns a TC_RDI to the TCM source end. After
the alarm at the TCM sink is cleared, the TC_RDI alarm is automatically cleared.
----End
Related Information
l 3.130 TC_UNEQ
l 3.129 TC_TIM
l 3.124 TC_LTC
3.128 TC_REI
Description
The TC_REI is an alarm indicating remote bit errors in the tandem connection. When the
accumulated number of bit errors in the remote tandem connection received at the sink end within
one second is greater than 0, the TC_REI alarm is reported.
Attribute

Warning Communication alarm
Parameters
table.
Name Meaning

Impact on System
When the TC_REI alarm occurs, the system is not affected. This alarm only indicates that some
Possible Causes
The possible cause of the TC_REI alarm is as follows:
l Bit errors are detected in the TC segment, that is, the TC connection segment service is
unstable.
l The performance of the other carrier network that the services pass is degraded.
Handling Procedure
If... Then...
B3_SD
Step 2 Replace the line board at the source end. Then check whether the alarm is cleared.
If... Then...
If... Then...
B3_SD
Step 4 Replace the line board that reports the alarm at the sink end. Then check whether the alarm is
cleared.

If... Then...
CAUTION
----End
Related Information
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD
l 3.13 B3_EXC
l 3.15 B3_SD
3.129 TC_TIM
Description
The TC_TIM is an alarm indicating the mismatch of the trace identifier alarm in the tandem
connection. When the tandem connection trace byte received at the TCM sink end does not
match the trace byte to be received, the TC_TIM alarm is reported.
Attribute
Parameters
table.

Name Meaning
Impact on System
When the TC_TIM alarm occurs, the TCM sink returns the TC_ODI and TC_RDI through the
N1 byte to the TCM source. If the AU_AIS alarm is set inserted when the TC_TIM alarm occurs,
the system automatically inserts the AU_AIS alarm in the downstream station.
Possible Causes
The possible causes of the TC_TIM alarm are as follows:
l The higher-level alarms are received at the TCM source end or sink end.
l The trace byte configured to be received at the sink end is inconsistent with that actually
received.
end or sink end.
l The performance of other carrier networks through which the services pass is degraded.
Handling Procedure
B3_EXC, B1_SD, B2_SD, and B3_SD, at the source end or sink end.
If... Then...
There is the alarm that can trigger the AIS First clear these alarms. Clean the fiber ends
insertion and ensure that the fiber connectors are firmly
inserted. Then check whether the TC_TIM
alarm is cleared. If not, proceed to the next step.
There are not such alarms that can trigger Proceed to the next step.
the AIS insertion
Step 2 If the alarm persists, check whether the tandem connection trace byte transmitted from the source
line board is consistent with that to be received by the sink line board.

If... Then...
The number is not consistent Modify them to be consistent. Then check whether the
TC_TIM alarm is cleared. If not, proceed to the next step.
If... Then...
The services are not correctly configured Modify the service level, and check whether the
alarm is cleared. If not, proceed to the next step.
The services are correctly configured Proceed to the next step.
Step 4 Check whether the TCM source end and sink end fully support the TCM Option2 function.
If... Then...
The TCM source and sink do not support the Use the board that support the TCM Option2
TCM Option2 function completely. function, and check whether the TC_TIM
alarm is cleared. If not, go to step 7.
The TCM source and sink support the TCM Proceed to the next step.
Option2 function
If... Then...
Step 6 Replace the line board that reports the TC_TIM alarm at the sink end.
If... Then...
Step 7 If the alarm persists, it indicates the performance of other carrier networks through which the
services pass may be degraded. In this case, contact the relevant carrier for troubleshooting.
CAUTION
----End

Related Information
None.
3.130 TC_UNEQ
Description
The TC_UNEQ is an alarm indicating that no services are equipped in the tandem connection.
When the N1 byte is all "0"s in the five consecutive frames received at the TCM sink end, the
TC_UNEQ alarm is reported.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the TC_UNEQ alarm occurs, the transmitted services are interrupted.
When the TC_UNEQ alarm occurs, by default, the system inserts the AU_AIS alarm in the
downstream station. At the same time, the TCM sink end returns the TC_RDI and TC_ODI
through the N1 byte to the TCM source end.
Possible Causes
The possible causes of the TC_UNEQ alarm are as follows:


Handling Procedure
If... Then...
The service level is incorrectly configured After modifying the incorrect configuration,
check whether the TC_UNEQ alarm is cleared.
The service level is correctly configured Proceed to the next step.
If... Then...
Step 3 Replace the line board at the sink end. Then check whether the TC_UNEQ alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.131 TEM_HA
Description
The TEM_HA is an alarm indicating that the temperature of the laser exceeds the upper
threshold.

Attribute
Parameters
table.
Name Meaning
Impact on System
When the TEM_HA alarm occurs, the working temperature of the laser on the line board is over
high and crosses the threshold. As a result, the transmit circuit is faulty and bit errors occur in
the transmitted signals. In addition, the aging of the laser will be accelerated.
Possible Causes
The possible causes of the TEM_HA alarm are as follows:
l The working temperature of the entire system is over high.

Handling Procedure
Step 1 Query whether there is the TEMP_ALARM alarm on the local equipment.
If... Then...
There is the TEMP_ALARM alarm See the corresponding section in this document to
clear the alarm. If the alarm persists, proceed to
the next step.
Step 2 After the optical module is replaced, view alarms on the T2000 to check whether the TEM_HA
alarm is cleared.

If... Then...
view alarms on the T2000 to check whether the TEM_HA alarm is cleared.
If... Then...
CAUTION
----End
Related Information
3.133 TEMP_ALARM
3.132 TEM_LA
Description
The TEM_LA is an alarm indicating that the working temperature of the laser is below the lower
threshold.
Attribute

Parameters
table.

Name Meaning
Impact on System
When the TEM_LA alarm occurs, the working temperature of the laser on the line board is over
low and crosses the threshold. As a result, the transmit circuit is faulty and bit errors occur in
the transmitted signals.
Possible Causes
The possible causes of the TEM_LA alarm are as follows:
l The working temperature of the entire system is over low.

Handling Procedure
Step 1 Query whether there is the TEMP_ALARM alarm on the local equipment.
If... Then...
There is the TEMP_ALARM alarm See the corresponding section in this document to
clear the alarm. If the alarm persists, proceed to
the next step.
Step 2 After the optical module is replaced, view alarms on the T2000 to check whether the TEM_LA
alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the TEM_LA alarm is cleared.
If... Then...

CAUTION
----End
Related Information
3.133 TEMP_ALARM
3.133 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that board reports a temperature alarm.
Attribute

Minor Environmental alarms
Parameters
table.
Name Meaning
Parameter 1 Indicates that the temperature crosses the threshold.
l 1: The temperature exceeds the upper temperature threshold.
l 2: The temperature is below the temperature lower threshold.


Impact on System
When the TEMP_ALARM occurs, the temperature of the board is abnormal. This will affect
the normal operation of the system.
If the fan board is configured, the fan will work at the maximum speed when the temperature of
the board exceeds the upper threshold.
Possible Causes
The possible causes of the TEMP_ALARM alarm are as follows:
l The temperature of the monitored equipment exceeds the upper threshold or is below the
lower threshold.
Handling Procedure
Step 1 Check whether the temperature of the monitored equipment is normal. If the temperature is over
high, enhance heat dissipation of the equipment. If the temperature is over low, increase the
ambient temperature.
Step 2 After handling the heat dissipation or the ambient environment, view alarms on the T2000 to
check whether the TEMP_ALARM is cleared.
If... Then...
Step 3 The board is faulty. Replace the board that reports the TEMP_ALARM alarm.
CAUTION
----End

Related Information
None.
3.134 TF
Description
The TF is an alarm indicating the transmission failure of the laser.
Attribute
Parameters
table.
Name Meaning
Parameter 2 0x00
Parameter 3 0x01
Impact on System
When the TF alarm occurs, the transmission of the laser fails. As a result, the services transmitted
by the optical interface are unavailable.
Possible Causes
The possible causes of the TF alarm are as follows:
l The laser is faulty.

Handling Procedure

Step 2 View alarms on the T2000 to check whether the TF alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the TF alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.135 TPS_FAIL
Description
The TPS_FAIL is an alarm indicating the TPS switching failure.
Attribute
Parameters
table.

Name Meaning
Parameter 1 TPS protection group ID
Impact on System
When the TPS_FAIL alarm occurs, the services will be interrupted for a long time.
Possible Causes
The possible cause of the TPS_FAIL alarm is as follows:
The TPS switching status on the NE software is inconsistent with that queried on the cross-
connect board.
Handling Procedure
Step 1 Replace the access board, and perform the manual switching.
Step 2 View alarms on the T2000 to check whether the TPS_FAIL alarm is cleared.
If... Then...
----End
Related Information
None.
3.136 TPS_INDI
Description
The TPS_INDI is an alarm indicating that the TPS switching action already occurs.
Attribute

Parameters
table.
Name Meaning
Parameter 1 TPS protection group ID
Impact on System
When the TPS_INDI alarm occurs, the services are switched to the protection board.
Possible Causes
The possible causes of the TPS_INDI alarm are as follows:
l The fault of the processing board triggers the automatic TPS switching.
l The manually issued TPS switching command triggers the TPS switching.
Handling Procedure
Step 1 Query the TPS switching status on the T2000.
If... Then...
The TPS is in the manual switching state Clear the manual switching command.
The TPS is in the automatic switching state Proceed to the next step.
Step 2 Replace the processing board.

Step 3 After the new processing board operates and the services are switched to the new processing
board, view alarms on the T2000 to check whether the TPS_INDI alarm is cleared.
If... Then...
----End
Related Information
None.

3.137 TU_AIS
Description
The TU_AIS is an alarm indicating that the signals in the lower order path received by the
tributary board on the cross-connection side are all "1"s.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the TU_AIS alarm occurs, the lower order path signals received on the cross-connection
side by the tributary board are all 1s. Consequently, the services in the lower order path are
unavailable.
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.
l The higher order alarms occur.

Handling Procedure
Step 1 View alarms on the T2000 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.
If... Then...
There is the R_LOS, R_LOC, R_LOF, See the corresponding section in this document
MS_AIS, AU_AIS, or AU_LOP alarm to clear the alarm.
The AIS is set inserted when there is the See the corresponding section in this document
B1_EXC, B2_EXC, B2_SD, B3_EXC, to clear the alarm.
HP_LOM, R_OOF, B1_SD, B3_SD,
HP_TIM, HP_UNEQ, or HP_SLM alarm
Step 2 Check whether there is the PDH alarm at the port that is configured with interconnection services
on the opposite tributary board.
If... Then...
There is the T_ALOS or E1_LOS alarm See the corresponding section in this document
to clear the alarm.
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 T2000 to check whether the TU_AIS alarm is cleared.
If... Then...
Step 5 Replace the tributary board that reports the TU_AIS alarm.
CAUTION
Step 6 View alarms on the T2000 to check whether the TU_AIS alarm is cleared.
If... Then...
alarm is cleared.

If... Then...
After the new board operates normally, view alarms on the T2000 to check whether the alarm
is cleared.
If... Then...
CAUTION
----End
Related Information
l 3.104 R_LOS
l 3.102 R_LOC
l 3.103 R_LOF
l 3.105 R_OOF
l 3.82 MS_AIS
l 3.7 AU_AIS
l 3.8 AU_LOP
l 3.38 HP_TIM
l 3.39 HP_UNEQ
l 3.37 HP_SLM
l 3.34 HP_LOM
l 3.9 B1_EXC
l 3.10 B1_SD
l 3.11 B2_EXC
l 3.12 B2_SD

l 3.13 B3_EXC
l 3.15 B3_SD
3.138 TU_AIS_VC12
Description
The TU_AIS_VC12 is a TU alarm indication. This alarm is the VC-12 path AIS. If the board
detects that the signals in the TU path are all "1"s, the alarm is reported.
Attribute

Parameters
table.
Name Meaning
Parameter 2 Indicates the AU-4 path number (MSB).
Parameter 3 Indicates the AU-4 path number (LSB).
Parameter 4 Indicates the VC-12 lower order path number. The value range is 1-63.
Impact on System
When the TU_AIS_VC12 alarm occurs, the services in the VC-12 path are interrupted.
Possible Causes
The possible causes of the TU_AIS_VC12 alarm are as follows:
l Higher-level alarms, such as the R_LOS, R_LOF, or AU_AIS, occur in the system.
l The hardware fault alarm occurs at the upstream station.
l The corresponding path at the opposite station fails.

Handling Procedure
Step 1 Check on the T2000 whether there is the higher-level alarm, such as the R_LOS, R_LOF, or
AU_AIS. If yes, first clear the higher level alarms. Then check whether the TU_AIS_VC12
alarm is cleared.
If... Then...
Step 2 Check whether any hardware fault alarm occurs at the upstream station. If yes, clear the hardware
alarms. Then check whether the TU_AIS_VC12 alarm is cleared.
If... Then...
Step 3 Perform a cold reset on or remove and insert the board that reports the TU_AIS_VC12 alarm.
Then check whether the TU_AIS_VC12 alarm is cleared.
If... Then...
Step 4 Replace the board that reports the TU_AIS_VC12 alarm. Then check whether the alarm is
cleared.
If... Then...
If... Then...
Step 6 Check whether the opposite board is faulty. If yes, replace the faulty board. Then check whether
the TU_AIS_VC12 alarm is cleared.
If... Then...

CAUTION
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.7 AU_AIS
3.139 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU alarm indication. This alarm is the VC-3 path AIS. If the board detects
that the signals in the TU path are all "1"s, the alarm is reported.
Attribute
Parameters
table.
Name Meaning
Impact on System
When the TU_AIS_VC3 alarm occurs, the services in the VC-3 path are interrupted.

Possible Causes
The possible causes of the TU_AIS_VC3 alarm are as follows:
Handling Procedure
AU_AIS. If yes, first clear the higher level alarms. Then check whether the TU_AIS_VC3 alarm
is cleared.
If... Then...
alarms. Then check whether the TU_AIS_VC3 alarm is cleared.
If... Then...
Step 3 Perform a cold reset on or remove and insert the board that reports the TU_AIS_VC3 alarm.
Then check whether the TU_AIS_VC3 alarm is cleared.
If... Then...
Step 4 Replace the board that reports the alarm. Then check whether the alarm is cleared.
If... Then...
If... Then...

If... Then...
the TU_AIS_VC3 alarm is cleared.
If... Then...
CAUTION
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.7 AU_AIS
3.140 TU_LOP
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
Parameters

table.
Name Meaning
Impact on System
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. When
the TU_LOP alarm occurs, the system returns the LP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the TU_LOP alarm are as follows:
l The interface between the tributary board and the cross-connect and timing board is faulty.
Handling Procedure
Step 1 Check whether the cross-connect and timing board or the tributary board is correctly configured.
Step 2 View alarms on the T2000 to check whether the TU_LOP alarm is cleared.
If... Then...
Step 3 Check whether the tributary board is faulty. Replace the faulty board.
CAUTION
Step 4 View alarms on the T2000 to check whether the TU_LOP alarm is cleared.

If... Then...
alarm is cleared.
If... Then...
After the new board operates normally, view alarms on the T2000 to check whether the alarm
is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.141 TU_LOP_VC12
Description
The TU_LOP_VC12 is an alarm indicating the loss of TU pointer. If a board detects that the
TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames, the TTU_LOP
alarm is reported.

Attribute
Parameters
table.
Name Meaning
Parameter 2 Indicates the AU-4 path number (MSB).
Parameter 3 Indicates the AU-4 path number (LSB).
Parameter 4 Indicates the VC-12 lower order path number. The value range is 1-63.
Impact on System
When the TU_LOP_VC12 alarm occurs, the services in the VC-12 lower order path are
interrupted.
Possible Causes
The possible causes of the TU_LOP_VC12 alarm are as follows:
Handling Procedure
AU_AIS. If yes, first clear the higher level alarms. Then check whether the alarm is cleared.
If... Then...
alarms. Then check whether alarm is cleared.

If... Then...
Step 3 Perform a cold reset on or remove and insert the board that reports the alarm. Then check whether
If... Then...
Step 4 Replace the board that reports the TU_LOP_VC12 alarm. Then check whether the alarm is
cleared.
If... Then...
If... Then...
If... Then...
CAUTION
----End

Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.7 AU_AIS
3.142 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating the loss of TU pointer. If a board has detected that
the TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames, the
TU_LOP_VC3 alarm is reported.
Attribute
Parameters
table.
Name Meaning
Parameter 2 Indicates the VC-3 path number (MSB).
Parameter 3 Indicates the VC-3 path number (LSB).
Impact on System
When the TU_LOP_VC3 alarm occurs, the services in the VC-3 path are interrupted.
Possible Causes
The possible causes of the TU_LOP_VC3 alarm are as follows:

Handling Procedure
AU_AIS. If yes, first clear the higher level alarms. Then check whether the alarm is cleared.
If... Then...
alarms. Then check whether alarm is cleared.
If... Then...
Step 3 Perform a cold reset on or remove and insert the board that reports the alarm. Then check whether
If... Then...
Step 4 Replace the board that reports the alarm. Then check whether the alarm is cleared.
If... Then...
If... Then...
If... Then...

CAUTION
----End
Related Information
l 3.104 R_LOS
l 3.103 R_LOF
l 3.7 AU_AIS
3.143 UP_E1AIS
Description
The UP_E1AIS is a 2M uplink signal alarm indication. When the 2M uplink signals are all "1"s,
the UP_E1AIS alarm is reported.
Attribute
Parameters
table.
Name Meaning

Impact on System
When the UP_E1AIS alarm occurs, the uplink E1 signals are all 1s. Consequently, the uplink
services are unavailable.
Possible Causes
The possible causes of the UP_E1AIS alarm are as follows:
l The E1 interface board is faulty.

l The higher-level alarm, such as the T_ALOS, occurs.
Handling Procedure
Step 1 Check whether there is the T_ALOS alarm on the tributary board.
If... Then...
There is the T_ALOS alarm First clear the T_ALOS alarm. Then check whether the
2M electrical interface on the interface board is correctly
connected. If yes, check whether the UP_E1AIS alarm is
There is not the T_ALOS alarm Proceed to the next step.
Step 2 Check whether the electrical interface of the path is performed the selfloop and whether there
is the DN_E1AIS alarm in the downlink.
If... Then...
There is the DN_E1AIS alarm First clear the DN_E1AIS alarm. Then check whether
the alarm is cleared. If no, proceed to the next step.
There is not the DN_E1AIS alarm Proceed to the next step.
Step 3 Check whether the local board is faulty.
If... Then...
The board is faulty Switch all services of the board to the standby board if other services
are available on the board. Then reset the board. If the fault is not
rectified, replace the board.
The board is not faulty Proceed to the next step.
Step 4 Check whether the interface board is faulty.
If... Then...
The board is faulty Remove and insert the board again. Then check whether the
UP_E1_AIS alarm is cleared. If not, replace the interface board and
then check whether the alarm is cleared. If the alarm persists, contact
Huawei engineers for troubleshooting.
The board is not faulty Contact Huawei engineers for troubleshooting.
----End

Related Information
l 3.117 T_ALOS
l 3.24 DN_E1AIS
3.144 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating that the delay of the virtual concatenation is too long.
This alarm occurs when the delay time of the timeslots bound to a VCTRUNK exceeds the time
allowed by the virtual concatenation delay.
Attribute

Critical Service alarm
Parameters
table.
Name Meaning
Impact on System
During the service data transmission, when the alignment time of the virtual concatenation delay
is too long, the timeslots cannot form a data frame. As a result, it causes the packet loss.
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows:
The actual SDH network delay exceeds the limits of the virtual concatenation delay
compensation.

Handling Procedure
Step 2 Configure the timeslots of the VCTRUNK, so that they pass through the same fiber. If they need
to pass through different fibers, make sure that the distance difference between the fibers is the
smallest.
----End
Related Information
None.
3.145 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating the loss of the virtual concatenation multiframe
in the VC-12 path. This alarm occurs when the system detects that the multiframe indicator
(MFI) field in the K4 byte of the VC-12 timeslot is illegal.
Attribute
Parameters
table.
Name Meaning
Impact on System
During the data transmission, if the LCAS is disabled, the services are interrupted.

Possible Causes
The possible causes of the VCAT_LOM_VC12 alarm are as follows:
l There are bit error alarms BIP_EXC and BIP_SD in the line.
l The virtual concatenation delay is excessive.
l The MFI filed in the K4 byte transmitted by the opposite end is incorrect.
Handling Procedure
Step 1 Check on the T2000 whether there are bit error alarms BIP_EXC and BIP_SD reported from
the board that reports the VCAT_LOM_VC12 alarm. If yes, first clear them and then check
whether the VCAT_LOM_VC12 alarm is cleared.
If... Then...
Step 2 Check on the T2000 whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual
concatenation delay is too long. See the procedure for handling the VCAT_LOA alarm to clear
it. After that, check whether the VCAT_LOM_VC12 alarm is cleared.
If... Then...
Step 3 Replace the board that reports the alarm. After the new board operates normally, view alarms
on the T2000 to check whether the VCAT_LOM_VC12 alarm is cleared.
If... Then...
Step 4 Replace the corresponding board at the opposite station. After the new board operates normally,
view alarms on the T2000 to check whether the VCAT_LOM_VC12 alarm is cleared.
If... Then...
CAUTION
----End

Related Information
None.
3.146 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating the loss of the virtual concatenation multiframe
in the VC-3 path. This alarm occurs when the system detects that the multiframe indicator (MFI)
field in the H4 byte of the VC-3 timeslot is illegal.
Attribute

Parameters
table.
Name Meaning
Impact on System
During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC3 alarm are as follows:
l There are bit error alarms B3_EXC and B3_SD in the line.
l The virtual concatenation delay is excessive.
l The MFI filed in the K4 byte transmitted by the opposite end is incorrect.

Handling Procedure
Step 1 Check on the T2000 whether there are bit error alarms B3_EXC and B3_SD reported from the
board that reports the VCAT_LOM_VC3 alarm. If yes, first clear them and check whether the
VCAT_LOM_VC3 alarm is cleared.
If... Then...
Step 2 Check on the T2000 whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual
concatenation delay is too long. See the procedure for handling the VCAT_LOA alarm to clear
it. After that, check whether the VCAT_LOM_VC3 alarm is cleared.
If... Then...
Step 3 Replace the board that reports the alarm. After the new board operates normally, view alarms
on the T2000 to check whether the VCAT_LOM_VC3 alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the VCAT_LOM_VC3 alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.

3.147 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 is an alarm indicating the SQ mismatch of the virtual concatenation
in the VC-12 path. This alarm occurs when the sequence numbers of members in the virtual
concatenation at the VC-12 level mismatch.
Attribute
Parameters
table.
Name Meaning
Impact on System
During the data transmission, the error occurs in the reassembly of the received sequence
numbers and the framing fails. As a result, the services are interrupted.
Possible Causes
The possible causes of the VCAT_SQM_VC12 alarm are as follows:
l There are bit error alarms BIP_EXC and BIP_SD in the line.
l The sequence number transmitted at the opposite station is incorrect.
Handling Procedure
Step 1 Check on the T2000 whether there are BIP_EXC and BIP_SD on the board that reports the
alarm. If yes, first clear them and check whether the VCAT_SQM_VC12 alarm is cleared.

If... Then...
Step 2 Replace the board that reports the VCAT_SQM_VC12 alarm. After the new board starts to work,
view alarms on the T2000 to check whether the VCAT_SQM_VC12 alarm is cleared.
If... Then...
Step 3 Replace the corresponding board at the opposite station. After the new board starts to work, view
alarms on the T2000 to check whether the VCAT_SQM_VC12 alarm is cleared.
If... Then...
CAUTION
----End
Related Information
None.
3.148 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 is an alarm indicating the SQ mismatch of the virtual concatenation in
the VC-3 path. This alarm occurs when the sequence numbers of members in the virtual
concatenation at the VC-3 level mismatch.
Attribute


Parameters
table.
Name Meaning
Impact on System
During the data transmission, the error occurs to the reassembly of the received serial numbers
and the framing fails. As a result, the services are interrupted.
Possible Causes
The possible causes of the VCAT_SQM_VC3 alarm are as follows:
l There are bit error alarms B3_EXC and B3_SD in the line.
l The sequence number transmitted at the opposite station is incorrect.
Handling Procedure
Step 1 Check on the T2000 whether there are bit error alarms B3_EXC and B3_SD reported from the
board that reports the VCAT_LOM_VC3 alarm. If yes, first clear them and check whether the
VCAT_SQM_VC3 alarm is cleared.
If... Then...
Step 2 Replace the board that reports the VCAT_SQM_VC12 alarm. After the new board operates
normally, view alarms on the T2000 to check whether the VCAT_SQM_VC3 alarm is cleared.
If... Then...
view alarms on the T2000 to check whether the VCAT_SQM_VC3 alarm is cleared.

If... Then...
CAUTION
----End
Related Information
None.
3.149 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that the type of the physical board installed in the
slot of the NE that reports the alarm is incorrect.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the slot number of the NE.

Impact on System
When the WRG_BD_TYPE alarm occurs, the type of the physical board installed in the slot that
reports the alarm is inconsistent with that of the logical board specified for the slot. As a result,
the board cannot normally start.
Possible Causes
The possible cause of the WRG_BD_TYPE alarm is as follows:
The incorrect physical board is inserted on the NE or the logical board is incorrectly configured.
Handling Procedure
Check whether the configured board type is consistent with that of the inserted board. If not,
modify the configuration of the logical board or insert the physical board of the consistent type
with the configured logical board.
----End
Related Information
None.
3.150 W_R_FAILURE
Description
The W_R_FAILURE is an alarm indicating that reading and writing the chip register fail.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Chip ID
Parameter 2 0x00
Parameter 3 0x00

Name Meaning
Impact on System
When the W_R_FAILURE alarm occurs, writing and reading the chip register fail. This will
affect the functions of the board.
Possible Causes
The possible cause of the W_R_FAILURE alarm is as follows:
The board is faulty.
Handling Procedure
Step 1 Perform a hard reset on, or remove and insert the board that reports the W_R_FAILURE alarm.
Step 2 After the board is on line again, view alarms on the T2000 to check whether the W_R_FAILURE
alarm is cleared.
If... Then...
Step 3 The board hardware is faulty, replace the relevant board.
CAUTION
Performing a cold reset on the board, removing and inserting the board, or replacing the board
will interrupt services. The operation is risky.
----End
Related Information
None.

Alarms and Performance Events Reference 4 Performance Event Clearing
4 Performance Event Clearing
About This Chapter
Introduces how to handle the performance events.
NOTE
l For troubleshooting bit errors, see "Troubleshooting Bit Errors" in the OptiX OSN 2000 Enhanced
STM-1/STM-4/STM-16 Multi-Service Optical Transmission System Troubleshooting.
l For troubleshooting pointer justifications, see "Troubleshooting Pointer Justifications" in the OptiX
OSN 2000 Enhanced STM-1/STM-4/STM-16 Multi-Service Optical Transmission System
Troubleshooting.
4.1 AUPJCHIGH
4.2 AUPJCLOW
4.3 AUPJCNEW
4.4 BDTMPCUR
4.5 BDTMPMAX
4.6 BDTMPMIN
4.7 HPBBE
4.8 HPCSES
4.9 HPES
4.10 HPFEBBE
4.11 HPFECSES
4.12 HPFEES
4.13 HPFESES
4.14 HPSES
4.15 HPUAS
4.16 HPFEUAS

4 Performance Event Clearing Alarms and Performance Events Reference
4.17 LPBBE
4.18 LPCSES
4.19 LPES
4.20 LPFEBBE
4.21 LPFECSES
4.22 LPFEES
4.23 LPFESES
4.24 LPSES
4.25 LPUAS
4.26 LPFEUAS
4.27 MSBBE
4.28 MSCSES
4.29 MSES
4.30 MSFEBBE
4.31 MSFECSES
4.32 MSFEES
4.33 MSFESES
4.34 MSSES
4.35 MSUAS
4.36 MSFEUAS
4.37 OSPITMPMAX
4.38 OSPITMPMIN
4.39 OSPITMPCUR
4.40 RPLCUR
4.41 RPLMAX
4.42 RPLMIN
4.43 RSBBE
4.44 RSCSES
4.45 RSES
4.46 RSOFS
4.47 RSSES
4.48 RSUAS
4.49 TLBMAX

4.50 TLBMIN
4.51 TLBCUR
4.52 TPLMAX
4.53 TPLMIN
4.54 TPLCUR
4.55 TUPJCHIGH
4.56 TUPJCLOW
4.57 TUPJCNEW

4.1 AUPJCHIGH
Performance Event Meaning

The AUPJCHIGH (Administrative Unit Pointer Justification Count HIGH) indicates the positive
justification count of the administrative unit (AU) pointer.
Impact on System
A small amount of pointer justification will not affect the services. A large amount of pointer
justification will cause bit errors in the services. At this time, you need to find out 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, which results in the mutual clock tracing of the two
NEs.
l If the NEs trace the external clock, check the quality of the external clock.
l The ambient temperature is too high or too low, which exceeds the normal working
temperature.
Incorrect configuration:
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l 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.

l The clock unit is faulty. As a result, the clock source is of a bad quality, or the traced clock
source cannot be locked.
Procedure
Step 1 Check whether the fibers are incorrectly connected. Usually, only in the case of the path
protection (PP) ring, services are normal even though the fibers are incorrectly connected. In
other networking modes, if the fibers are incorrectly connected, the services will be interrupted.
Step 2 If the NEs trace the external clock, check the quality of the external clock.
Step 3 Ensure that the configuration is correct.
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.

Step 5 Check whether the performance event is cleared. If the performance event persists, contact
Huawei engineers for troubleshooting.
----End
Related Information
None.
4.2 AUPJCLOW
Description
The AUPJCLOW (Administrative Unit Pointer Justification Count LOW) indicates the negative
Impact on System
Possible Causes
External causes
NEs.
temperature.
network.
Equipment problems:

Procedure
See the procedure in 4.1 AUPJCHIGH.
----End

Related Information
None.
4.3 AUPJCNEW
Description
The AUPJCNEW (Administrative Unit Pointer Justification Count NEW) indicates the new
Impact on System
Possible Causes
External causes
NEs.
temperature.
network.
Equipment problems:

Procedure
See the procedure in 4.1 AUPJCHIGH.
----End
Related Information
None.

4.4 BDTMPCUR

The BDTMPCUR indicates the count of the current board temperature.
Impact on the System

When the BDTMPCUR occurs, the system is not affected.
Possible Causes
This is the physical performance, which exists since the board is on line.
Procedure
None.
----End
Reference
None.
4.5 BDTMPMAX

The BDTMPMAX indicates the maximum value of the board temperature in the current period.

When the BDTMPMAX occurs, the system is not affected.
Possible Causes
Procedure
None.
----End
Reference
None.

4.6 BDTMPMIN

The BDTMPMIN indicates the minimum value of the board temperature in the current period.

When the BDTMPMIN occurs, the system is not affected.
Possible Causes
Procedure
None.
----End
Reference
None.
4.7 HPBBE

The HPBBE indicates higher order path background block error.
Impact on System
If bit errors occur in the services, you need to find out the causes and troubleshoot the problem
in time. Otherwise, alarms will be generated and the signal transmission quality will be affected.
If bit errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the
B3_EXC and B3_SD alarms will be generated.
Possible Causes
External causes
l The fiber performance degrades and the attenuation is excessive.
l The optical port is not clean, or the connector is not correct.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The heat dissipation of the equipment is poor and the operating temperature is too high.
Equipment problems:

l The signal attenuation on the receiving side of the line board is excessive, the transmitting
circuit of the opposite end is faulty, or the receiving circuit of the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board or the cross-connect unit and the tributary board
poorly match.
l The board fails or the board performance degrades.
Procedure
Step 1 Analyze the bit error performance events on the line board. Remove the line bit errors.
1. First handle the external causes, such as improper grounding, too high operating
temperature, too low or too high receiving optical power of the line board.
2. Observe the bit errors on the line board. Observe the bit errors on the line board. If all the
line boards report bit errors at a station, the clock unit of the station may be faulty. Replace
the clock board. If only one line board reports bit errors, the line board, opposite station,
or fiber may be faulty.
3. Locate the faulty board and replace it.
NOTE
If possible, perform a loopback to locate the fault.
Step 2 Analyze the bit error performance events on the tributary board. Remove the tributary bit errors.
If only the tributary reports bit errors, the problem may lie in the cooperation of the cross-connect
unit and tributary board at the local station. Replace the tributary board and cross-connect board
to verify the faulty point and clear the fault.
----End
Related Information
None.
4.8 HPCSES

The HPCSES indicates higher order path consecutive severely errored second.
Impact on System
Possible Causes
When a consecutive HPSES sequence is detected, the HPCSES performance event occurs. When
unavailable time comes or HPSES is absent in one second, the HPCSES sequence ends.
External causes


Equipment problems:
poorly match.
Procedure
See the procedure in 4.7 HPBBE.
----End
Related Information
None.
4.9 HPES

The HPES is a performance event indicating the higher order path errored second.
Impact on System
Possible Causes
The HPES performance event occurs when one or multiple bit error blocks are detected in one
second or, when the LOS, LOF, and MS_AIS alarms are detected on the optical interface, or
when the AU_AIS, AU_LOP, HP_UNEQ, and HP_TIM alarms are detected over the path.
External causes


Equipment problems:
poorly match.
Procedure
----End
Related Information
None.
4.10 HPFEBBE

The HPFEBBE indicates higher order path far end background block error.
Impact on System
If bit errors occur in the services on a remote NE, detect the causes and troubleshoot the problem
Possible Causes
External causes
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is not clean or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The heat dissipation of the equipment is poor and the operating temperature is too high at
Equipment problems:
l The signal attenuation on the receiving side of the line board at the opposite station is
excessive, the transmitting circuit of the opposite station is faulty, or the receiving circuit
of the local station is faulty.

l The synchronization performance of the clock is poor at the opposite station.

l The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
l The board fails or the board performance degrades at the opposite station.
Procedure
See the procedure for handling the HPBBE performance event to process the opposite NEs.
----End
Related Information
None.
4.11 HPFECSES

The HPFECSES indicates higher order path far end consecutive severely errored second.
Impact on System
Possible Causes
When a consecutive HPFESES sequence is detected, the HPFECSES performance event occurs.
When unavailable time comes or HPFESES is absent in one second, the HPFECSES sequence
ends.
External causes
Equipment problems:

Procedure
----End
Related Information
None.
4.12 HPFEES

The HPFEES indicates higher order path far end errored second.
Impact on System
Possible Causes
The HPFEES performance event occurs when one or multiple bit errors are returned by the G1
byte in one second or when the HP_RDI alarm is detected on the path.
External causes
Equipment problems:

Procedure
----End
Related Information
None.
4.13 HPFESES

The HPFESES indicates higher order path far end severely errored second.
Impact on System
Possible Causes
The LPFESES performance event occurs when one of the following requirements is met: 1. Not
less than 30% bit errors are contained in the message returned in one second. 2. At least one
severely disturbed period (SDP) occurs.
SDP occurs when the BER of all the continuous blocks in a period of at least four continuous
blocks or 1 ms (select the shorter period) is lower than 10-2 or when the HP_RDI alarm occurs.
External causes
Equipment problems:

Procedure
----End
Related Information
None.
4.14 HPSES

The HPSES indicates higher order path severely errored second.
Impact on System
Possible Causes
The MSSES performance event occurs when one of the following requirement is met: 1. Not
less than 30% bit errors are detected in one second. 2. At least one severely disturbed period
(SDP) occurs.
The SDP indicates that the BER of all the consecutive blocks is not lower than 10-2 or the LOS,
LOF and MS_AIS alarms occur in a period of at least four consecutive blocks or 1 ms (the longer
one is selected), or the AU_AIS, AU_LOP, HP_UNEQ, and HP_TIM alarms are detected on
the path.
External causes

Equipment problems:
poorly match.

Procedure
----End
Related Information
None.
4.15 HPUAS

The HPUAS indicates higher order path unavailable second.
Impact on System
Possible Causes
External causes

Equipment problems:
poorly match.
Procedure
----End

Related Information
None.
4.16 HPFEUAS

The HPFEUAS indicates higher order far end path unavailable second.
Impact on System
Possible Causes
External causes
l The opposite NE is improperly grounded.
l There is a strong interference source around the NE at the opposite station.
l The heat dissipation of the opposite NE is poor, and the working temperature of the
equipment is extremely high.
Equipment problems:
Procedure
----End
Related Information
None.
4.17 LPBBE


LPBBE is an errored block occurring as part of lower order path unavailable time and lower
order path severely errored second. When the service is of the VC-12 level, the first two bits of
the V5 byte are verified. When the service is of the VC-3 level, the B3 byte is verified.
Impact on System
If bit errors exceed the BIP bit error threshold-crossing threshold and degrade threshold, the
BIP_EXC and BIP_SD alarms will be generated.
Possible Causes
External causes
Equipment problems:
poorly match.
Procedure
Step 1 Analyze the bit error performance events on the line board. Remove the line bit errors.
1. First handle the external causes, such as poor grounding, too high operating temperature,
too low or too high receiving optical power of the line board.
2. Observe the bit errors on the line board. Observe the bit errors on the line board. If all the
line boards report bit errors at a station, the clock unit of the station may be faulty. Replace
the clock board. If only one line board reports bit errors, the line board, opposite station,
or fiber may be faulty.
3. Locate the faulty board and replace it.
NOTE
Step 2 Analyze the bit error performance events on the tributary board. Remove the tributary bit errors.
If only the tributary reports bit errors, the problem may lie in the cooperation of the cross-connect
unit and tributary board at the local station. Replace the tributary board and cross-connect board
to verify the faulty point and clear the fault.
----End

Related Information
None.
4.18 LPCSES

The LPCSES indicates lower order path consecutive severely errored second.
Impact on System
Possible Causes
When a consecutive LPSES sequence is detected, the LPCSES performance event occurs. When
unavailable time comes or LPSES is absent in one second, the LPCSES sequence ends. When
the service is of the VC-12 level, the first two bits of the V5 byte are verified. When the service
is of the VC-3 level, the B3 byte is verified.
External causes
Equipment problems:
poorly match.
Procedure
See the procedure in 4.17 LPBBE.
----End
Related Information
None.

4.19 LPES

The LPES indicates lower order path errored second.
Impact on System
Possible Causes
The LPES performance event occurs when one of the following requirements is met: 1. One or
multiple bit error blocks are detected in one second. 2. The LP_UNEQ, LP_TIM, TU_AIS, and
TU_LOP alarms are detected on the path. When the service is of the VC-12 level, the first two
bits of the V5 byte are verified. When the service is of the VC-3 level, the B3 byte is verified.
External causes

Equipment problems:
poorly match.
Procedure
----End
Related Information
None.

4.20 LPFEBBE

LPFEBBE indicates the lower order path far end errored block.
Impact on System
If bit errors occur in the services on a remote NE but no related alarms are reported on the remote
NE, the system will not be affected. However, you need to find out 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
Equipment problems:
Procedure
See the procedure for handling the LPBBE performance event to process the opposite NEs.
----End
Related Information
None.
4.21 LPFECSES


The LPFECSES indicates lower order path far end consecutive severely errored second.
Impact on System
will be affected.
Possible Causes
When a consecutive LPFECSES sequence is detected, the LPFECSES performance event
occurs. When unavailable time comes or LPFESES is absent in one second, the LPFECSES
sequence ends.
External causes
Equipment problems:
Procedure
----End
Related Information
None.
4.22 LPFEES

The LPFEES indicates lower order path far end errored second.

Impact on System
will be affected.
Possible Causes
The LPFEES performance event occurs when one of the following conditions is met: One or
multiple bit errors are returned within one second. The LP_RDI alarm is detected on the path
within one second. When the service is of the VC-12 level, the third bit of the V5 byte is verified.
When the service is of the VC-3 level, the G1 byte is verified.
External causes
Equipment problems:
Procedure
----End
Related Information
None.
4.23 LPFESES

The LPFESES indicates lower order path far end severely errored second.

Impact on System
will be affected.
Possible Causes
The LPFESES performance event occurs when one of the following requirements is met: 1. Not
severely disturbed period (SDP) occurs.
SDP is defined as the time period equivalent to four contiguous blocks or 1 millisecond,
whichever is larger, during which the BER of all the contiguous blocks is not lower than 10-2.
The LP_RDI alarm is detected. When the service is of the VC-12 level, the third bit of the V5
byte is verified. When the service is of the VC-3 level, the G1 byte is verified.
External causes
Equipment problems:
Procedure
----End
Related Information
None.
4.24 LPSES


The LPSES indicates lower order path severely errored second.
Impact on System
Possible Causes
The LPSES performance event occurs when one of the following requirements is met: 1. Not
(SDP) occurs.
SDP is defined as the time period equivalent to four contiguous blocks or 1 millisecond,
whichever is larger, during which the BER of all the contiguous blocks is not lower than 10-2.
The LP_UNEQ, LP_TIM, TU_AIS, or TU_LOP alarm is detected on the path. When the service
is of the VC-12 level, the first two bits of the V5 byte are verified. When the service is of the
VC-3 level, the B3 byte is verified.
External causes
Equipment problems:
poorly match.
Procedure
----End
Related Information
None.
4.25 LPUAS


The LPUAS indicates lower order path unavailable second.
Impact on System
Possible Causes
External causes
Equipment problems:
poorly match.
Procedure
----End
Related Information
None.
4.26 LPFEUAS

The LPFEUAS indicates higher order far end path unavailable second.
Impact on System

If bit errors exceed the BIP bit threshold and degrade threshold, the BIP_EXC and BIP_SD
alarms will be generated.
Possible Causes
External causes
Equipment problems:
Procedure
See the procedure in 4.22 LPFEES.
----End
Related Information
None.
4.27 MSBBE

The MSBBE indicates multiplex section background block error.
Impact on System
Possible Causes
External causes


Equipment problems:
l The cross-connect unit and the line board poorly match.
Procedure
Step 1 Analyze the bit error performance events on the line board. Remove the line bit errors. First
handle the external causes, such as improper grounding, too high operating temperature, too low
or too high receiving optical power of the line board.
Step 2 Observe the bit errors on the line board. Observe the bit errors on the line board. If all the line
boards report bit errors at a station, the clock unit of the station may be faulty. Replace the clock
board. If only one line board reports bit errors, the line board, opposite station, or fiber may be
faulty.
Step 3 Locate the faulty board and replace it.

NOTE
----End
Related Information
None.
4.28 MSCSES

The MSCSES indicates multiplex section consecutive severely errored second.
Impact on System

Possible Causes
The system detects the multiplex section bit errors through the B2 byte. When a consecutive
MSSES sequence is detected, the MSCSES performance event occurs. When unavailable time
comes or MSSES is absent in one second, the MSCSES sequence ends.
External causes
Equipment problems:
Procedure
See the procedure in 4.27 MSBBE.
----End
Related Information
None.
4.29 MSES

The MSES indicates multiplex section errored second.
Impact on System
Possible Causes
The MSES performance event occurs when one or multiple bit error blocks are detected in one
second or when the LOS, LOF, or MS_AIS alarm is detected.
External causes


Equipment problems:
Procedure
----End
Related Information
None.
4.30 MSFEBBE

The MSFEBBE indicates multiplex section far end background block error.
Impact on System
will be affected.
Possible Causes
External causes
l The equipment is not grounded properly at the opposite station.
Equipment problems:

l The cross-connect unit and the line board poorly match at the opposite station.
Procedure
See the procedure for handling the MSBBE performance event to process the opposite NEs.
----End
Related Information
None.
4.31 MSFECSES

The MSFECSES indicates multiplex section far end consecutive severely errored second.
Impact on System
will be affected.
Possible Causes
When a consecutive MSFESES sequence is detected, the MSFECSES performance event occurs.
When unavailable time occurs or MSFESES is absent within one second, the MSFECSES
sequence ends.
External causes
Equipment problems:


Procedure
----End
Related Information
None.
4.32 MSFEES

The MSFEES indicates multiplex section far end errored second.
Impact on System
will be affected.
Possible Causes
The MSFEES performance event occurs when one or multiple bit errors are returned in one
second or when the MS_RDI alarm is detected.
External causes
Equipment problems:

Procedure
----End
Related Information
None.
4.33 MSFESES

The MSFESES indicates multiplex section far end severely errored second.
Impact on System
will be affected.
Possible Causes
The MSFESES performance event occurs when one of the following requirement is met: 1. Not
severely disturbed period (SDP) occurs. The SDP occurs when the BER of all the continuous
blocks in a period of at least four continuous blocks or 1 ms (select the shorter period) is lower
than 10-2 or when the MS_RDI alarm occurs.
External causes
Equipment problems:

Procedure
----End
Related Information
None.
4.34 MSSES

The MSSES indicates multiplex section severely errored second.
Impact on System
Possible Causes
The MSSES performance event occurs when one of the following requirements is met: 1. Not
(SDP) occurs. The SDP indicates that the BER of all the consecutive blocks is not lower than
10-2 or the LOS, LOF and MS_AIS alarms occur in a period of at least four consecutive blocks
or 1 ms (the longer one is selected).
External causes

l The equipment is not grounded properly.
Equipment problems:

Procedure
----End
Related Information
None.
4.35 MSUAS

The MSUAS indicates multiplex section unavailable second.
Impact on System
Possible Causes
External causes
Equipment problems:
Procedure
----End
Related Information
None.

4.36 MSFEUAS

The MSFEUAS indicates higher order far end path unavailable second.
Impact on System
will be affected.
Possible Causes
External causes
Equipment problems:
Procedure
See the procedure in 4.32 MSFEES.
----End
Related Information
None.
4.37 OSPITMPMAX


The OSPITMPMAX indicates the maximum value of the laser temperature.
Impact on System
This performance event does not affect the system.
Possible Causes
This is the physical performance, which persists since the laser begins to operate normally.
Procedure
None.
----End
Related Information
None.
4.38 OSPITMPMIN

The OSPITMPMIN indicates the minimum value of the laser temperature.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.39 OSPITMPCUR


The OSPITMPCUR indicates the current value of the laser temperature.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.40 RPLCUR

The RPLCUR indicates the current value of the optical power received by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.41 RPLMAX


The RPLMAX indicates the maximum value of the optical power received by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.42 RPLMIN

The RPLMIN indicates the minimum value of the optical power received by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.43 RSBBE


The RSBBE indicates regenerator section background block error.
Impact on System
Possible Causes
External causes

Equipment problems:
Procedure
Step 1 Analyze the bit error performance events on the line board. Remove the line bit errors. First
handle the external causes, such as improper grounding, too high operating temperature, too low
or too high receiving optical power of the line board.
Step 2 Observe the bit errors on the line board. Observe the bit errors on the line board. If all the line
boards report bit errors at a station, the clock unit of the station may be faulty. Replace the clock
board. If only one line board reports bit errors, the line board, opposite station, or fiber may be
faulty.
Step 3 Locate the faulty board and replace it.

NOTE
----End
Related Information
None.

4.44 RSCSES

The RSCSES indicates regenerator section consecutive severely errored second.
Impact on System
Possible Causes
When a consecutive RSSES sequence is detected, the RSCSES performance event occurs. When
unavailable time occurs or RSSES is absent within one second, the RSCSES sequence ends.
External causes

Equipment problems:
Procedure
See the procedure in 4.43 RSBBE.
----End
Related Information
None.
4.45 RSES


The RSES indicates regenerator section errored second.
Impact on System
Possible Causes
The RSES performance event occurs when one of the following conditions is met: One or
multiple errored blocks are detected within one second. The LOS or LOF alarm is detected within
one second.
External causes

Equipment problems:
Procedure
----End
Related Information
None.
4.46 RSOFS

The RSOFS indicates regenerator section out-of-frame second.

Impact on System
This performance event 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 3 ms, the loss-of-frame state is entered. The equipment generates
the R_LOF alarm indicating the loss of frame.
Possible Causes
When a frame cannot receive the correct A1 or A2 byte, the frame header cannot be distinguished
in several consecutive frames. This second is called the regenerator section out-of-frame second.
External causes
Equipment problems:
Procedure
----End
Related Information
None.
4.47 RSSES

The RSSES indicates regenerator section severely errored second.
Impact on System

Possible Causes
The RSSES performance event occurs when one of the following requirements is met: 1. Not
(SDP) occurs. The SDP occurs when the BER of all the continuous blocks in a period of at least
four continuous blocks or 1 ms (select the shorter period) is lower than 10-2, or when the LOF
alarm occurs.
External causes
Equipment problems:
Procedure
----End
Related Information
None.
4.48 RSUAS

The RSUAS indicates regenerator section unavailable second.
Impact on System

Possible Causes
External causes

Equipment problems:
poorly match.
Procedure
----End
Related Information
None.
4.49 TLBMAX

The TLBMAX indicates the maximum value of the bias current transmitted by the laser.
Impact on System
Possible Causes
Procedure
None.
----End

Related Information
None.
4.50 TLBMIN

The TLBMIN indicates the minimum value of the bias current transmitted by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.51 TLBCUR

The TLBCUR indicates the current value of the bias current transmitted by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.

4.52 TPLMAX

The TPLMAX indicates the maximum value of the optical power transmitted by the laser.
Impact on System
Possible Causes
Count the maximum value of the optical power transmitted by the laser in the current period.
Handling Procedure
None.
Related Information
None.
4.53 TPLMIN

The TPLMIN indicates the minimum value of the optical power transmitted by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.

4.54 TPLCUR

The TPLCUR indicates the current value of the optical power transmitted by the laser.
Impact on System
Possible Causes
Procedure
None.
----End
Related Information
None.
4.55 TUPJCHIGH

The TUPJCHIGH (Tributary Unit Pointer Justification Counter HIGH) indicates the positive
justification count of the tributary unit (TU) pointer.
Impact on System
justification will cause bit errors in the services. At this time, you need to determine the causes
Possible Causes
External causes
NEs.

network.
Equipment problems:

l The tributary board is faulty. As a result, the clock is of a bad quality.
Procedure
Step 1 Check whether the fibers are incorrectly connected. Usually, only in the case of the SNCP ring,
services are normal even though the fibers are incorrectly connected. In other networking modes,
if the fibers are incorrectly connected, the services will be interrupted.
Step 2 If the NEs trace the external clock, check the quality of the external clock.
Step 3 Ensure that the configuration is correct.
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
Related Information
None.
4.56 TUPJCLOW

The TUPJCLOW (Tributary Unit Pointer Justification Counter LOW) indicates the negative
Impact on System
Possible Causes
External causes
NEs.

network.
Equipment problems:
Procedure
See the procedure in 4.55 TUPJCHIGH.
----End
Related Information
None.
4.57 TUPJCNEW

The TUPJCNEW (Tributary Unit Pointer Justification Counter NEW) indicates the new
Impact on System
Possible Causes
External causes
NEs.
network.

Equipment problems:
Procedure
See the procedure in 4.55 TUPJCHIGH.
----End
Related Information
None.

Alarms and Performance Events Reference A Glossary
A Glossary
A
Alarm A visible or an audible indication to notify the person concerned that a
failure or an emergency has occurred.
Alarm A function that is used to avoid generating relevant alarm information,
reversion thus preventing alarm interference, for the port that has already been
configured but not actually loaded with services.
Alarm filter Alarms are detected and reported to T2000 NM system, and whether the
alarm information is displayed and saved is decided by the status of the
alarm filter. If the status of alarm filter is enabled, the alarm information
will not be displayed and saved in T2000 NM system although monitored.
Alarm mask The function is for stop monitoring alarms of specific objects. These alarm
events can be generated from the network wide equipment, a particular
NE, board, or even a particular functional module of a board.
Alarm line The line for transmitting alarm signals.
Alarm cause When an interference or a fault occurs, many defects will be detected. A
fault is caused by the processing of correlation. The correlation processing
is for detecting the problems of generating interference or fault.
Alarm On the cabinet of an NE, there are three indicators with different colors
indication indicating the current state of the NE. If the green light is on, it indicates
that the NE is power on; if the red light is on, it indicates that severe alarms
are generated; if the orange light is on, it indicates that common alarms
are generated. You can stop the NE alarm indication through the T2000.
Automatic Report the alarm to the T2000 as soon as it is generated at the equipment
report of alarms side. The T2000 pops up the alarm board. The user can view this alarm
information in the alarm panel without active query.
Issue 02 (2008-10-15) Huawei Proprietary and Confidential A-1

A Glossary Alarms and Performance Events Reference
Administrative The information structure which provides adaptation between the higher
unit order path layer and the multiplex section layer. It consists of an
information payload (the higher order VC) and a AU pointer which
indicates the offset of the payload frame start relative to the multiplex
section frame start. Two AUs are provided. In China, the AU-4 is adopted.
It is composed of VC-4 and the AU pointer which indicates the phase
alignment relative to the STM-N frame. For the STM-N frame, the AU
pointer is fixed.
Administrator A user who has authority to access all the management domains of the
product. The user has access to the whole network and to all the
management functions.
Attribute The characteristics and features of the object.
Attenuator A passive component that attenuates an electrical or optical signal.
Automatic When the communication route fails, the service is switched to another
protection available route, and thus the system reliability is enhanced.
switching
B
Bind To designate one binding number to identify the VC-4s of the same virtual
cascaded service when configuring a virtual cascaded service. If a fault
occurs to one of the bound payloads, all bound payloads will switch as a
whole.
Backup The process of copying important data to the secondary storage in the event
the original is damaged, lost, or unavailable.
Bit interleaved The BIP-X is an error-detection technique. The transmitting equipment
parity generates X-bit of even parity in the specific area of signals: the first bit
of the code provides even parity for the first bit of the X-bit sequence in
the signal area. The second bit of the code provides even parity for the
second bit of the X-bit sequence in the signal area. Set the BIP-X to
generate even parity and ensure the number of ones in the detected signal
area is even. A monitored partition comprises all bits which are in the same
bit position within the X-bit sequences in the covered portion of the signal.
The covered portion includes the BIP-X.
Backplane A PCB circuit board in the subrack, which is connected with all the boards
in position.
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 An error to some bits in the digital code stream after receiving, generation.
Bit errors accompany the damage to the transmitted information.
Bit error ratio The number of coding violations detected in a unit of time, usually one
second. Bit error rate (BER) is calculated with this formula: BER = errored
bits received/total bits sent
A-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

C
Channel A trail located at the path layer.
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.
Concatenation A method of transmitting payload (for example, GE Ethernet signals)
whose capacity is greater than VC-4. Currently, the cascaded service can
combine the payload of multiple successive (4, 8, 16 or 64) AU4 services
and use the same set of higher order path overhead and AU4 pointer value
to form AU4-xC (x=4, 8, 16 or 64). And it is also multiplexed, cross-
connected and transmitted in the network as a single entity.
Current alarms Current alarm is the alarm that does not end, or has ended but is not
acknowledged.
Configuring Set basic parameters for the objects.
Configuration A command file for an NE which defines the configuration of the NE
data hardware. With the file, the NE can coordinate with other NEs in the entire
network. Configuration data is the key factor for the normal running of
the entire network. The typical configuration data includes board
configuration, clock configuration, and protection relationship.
Clock tracing The method of keeping all nodes synchronous with a clock source in the
network.
Converting When processing data, change the code type of the information. Or change
the pointer for displaying the change of the description.
E
Ethernet A data line level protocol that consists of the two bottom layers of the OSI
model. Several physical media, such as twisted pairs and coaxial cables,
can be used for the Ethernet broadcast network topology. The Ethernet
uses the CSMA/CD and TCP/IP to detect conflict.
Exercise An operation to check if the protection switching protocol functions
normally. The protection switching is not really performed.
F
Fault An event that cannot perform the specified operation on certain functions.
A fault does not involve the failure caused by preventive maintenance,
insufficiency of external resources and intentional settings.
Fiber New generation of connection protocol connects the NE and various
connection control units. The single-byte command protocols are transmitted through
the physical path of the fiber. The fiber connection provides higher speed
and better performance than the ESCON.

Fiber connector Installed at the ends of optical fiber, optical source, and receiver for
connecting with the equipment of the same type, and coupling the optical
wave to the optical fiber. A connector can be connected with two fiber
head-ends, or connected with one fiber head-end and one optical source
or photo detector.
Failure An event where a component cannot perform its necessary functions when
its consecutive fault duration reaches the specified value. In this case, the
component is considered to be a failure and the fault is detected.
Frame A set of consecutive time slots in which the relative position of each time
slot can be identified.
J
Jitter Short waveform variations caused by vibration, voltage fluctuations, or
control system instability.
L
Loopback The fault of each path on the optical fiber can be located by setting
loopback for each path of the line. There are three loopback modes: Non-
loopback, out-loop, and in-loop.
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.
Layer A concept used to allow the transport network functionality to be described
hierarchically as successive levels. Each layer only generates and transfers
its characteristic information.
M
Mapping A procedure by which tributary signals are adapted into virtual containers
at the boundary of the PDH/SDH network.
Multiplex To adapt multiple lower order path signals to a higher order path, or to
adapt multiple higher order path signals to a lower order path.
MSP A function provides capability for switching a signal from a working
channel to a protection channel.
Manual Automatic protection switching. When the protection channel is normal
switching and no higher-level switching is requested, switch the service from the
working channel to the protection channel to test whether the protection
capability of the network is available.

NE Network element that contains hardware and the software running on the
hardware. Generally, one network element should contain one SCC board
at least, which manages and monitors the entire network element. The NE
software runs on the SCC board.
O
Optical A component that connects several transmit or receive units.
interface
P
Pass-through To transmit the received higher order overheads to the next station. The
transmit equipment detects the higher order overheads, but does not
process them.
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.
Procedure A generic term for an action.
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.
Regenerator The overhead that comprises rows 1 to 3 of the SOH of the STM-N signal.
section
overhead
Route A path determined when multiple waypoints are used together.
S
Self-healing Establishment of a replacement connection by network without the NMC
function. When a connection failure occurs the replacement connection is
found by the network elements and rerouted depending on network
resources available at that time.
Suppressing When alarms of different levels are generated in the monitoring point,
alarms certain alarms of lower level is suppressed by alarms of higher level and
thus these alarms are not reported.

Stream The stream is the collection of the packets that have the same
characteristic. On the NMS or NE, it is a group of partition rules; on boards,
it is packets that perform the same QoS operation. Two types of stream
are supported: port-based stream and port VLAN -based stream. The port-
based stream is with the characteristics of the port ID, and the port VLAN-
based stream is with the characteristics of the port ID and VLAN number.
Two types of streams are not allowed to co-exist in the same port.
Suppression If the specified alarm is set as the "No Suppress" status, the NE will
status monitor this alarm event and generate this alarm information when the
relevant alarm occurs. If it is set as the "Suppress" status, the NE will not
monitor this alarm event and not generate this alarm when the relevant
alarm occurs.
Settings Optional operation parameters.
Synchronizatio A clock providing timing services to connected network elements. This
n source would include clocks complying with Recommendations G.811, G.812
and G.813.
Signal degrade A signal indicating the associated data has degraded in the sense that a
degraded defect (dDEG) condition is active.
T
Timeslot Single timeslot on a E1 digital interface—that is, a 64-kbps, synchronous,
full-duplex data channel, typically used for a single voice connection.
Tributary unit An information structure which provides adaptation between the lower
order path layer and the higher order path layer. It consists of an
information payload (the lower order VC) and a TU pointer which
indicates the offset of the payload frame start relative to the higher order
VC frame start. The TU-n (n = 1, 2, 3) consists of a VC-n together with a
tributary unit pointer.
U
User The T2000 client user. The unique user name and password determine the
corresponding operation management authority of the T2000.
V
Virtual Use the VC-12 or VC-4 (the route can be the same or not) of STM-N in
concatenation concatenation mode to form a virtual VC-4-xv, and then transmit signals.
Then combine them into an adjacent bandwidth in the transmission
termination point. The virtual concatenation requires that the terminal
equipment of the path provides the concatenation function.
Virtual An information structure for supporting path layer connection in the SDH.
container The virtual container is composed of information payload that is in the
block frame with the cycle of 125ms to 500ms, and the path overhead
information area.

W
Wander The long-term variations of the significant instants of a digital signal from
their ideal position in time (where long-term implies that these variations
are of frequency less than 10Hz).
Working The path with the working attributes in the protection group.
channel

Alarms and Performance Events Reference B Acronyms and Abbreviations
B Acronyms and Abbreviations
A
AIS Alarm Indication Signal
AU Administrative Unit
AUG Administrative Unit Group
H
HP Higher Order Path
HPA Higher Order Path Adaptation
HPOH Higher Order Path Overhead
HPT Higher Order Path Termination
L
LOF Loss of Frame
LOM Loss of Multiframe
LOP Loss of Pointer
LOS Loss of Signal
LP Lower Order Path
LPA Lower Order Path Adaptation
LPT Lower Order Path Termination
LVCUAT Lower Order VC Unavailable Event
M
MS Multiplex Section
Issue 02 (2008-10-15) Huawei Proprietary and Confidential B-1

B Acronyms and Abbreviations Alarms and Performance Events Reference
MSA Multiplex Section Adaptation

MSOH Multiplex Section Overhead
MSP Multiplex Section Protection
MST Multiplex Section Termination
MSUAT Multiplex Section Unavailable Event
P
PDH Plesiochronous Digital Hierarchy
POH Path Overhead
PPI PDH Physical Interface
R
RDI Remote Defect Indication
REI Remote Error Indication
RSOH Regenerator Section Overhead
RST Regenerator Section Termination
RSUAT Regenerator Section Unavailable Event
S
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SDP Serious Disturbance Period
SES Severely Errored Second
SF Signal Fail
T
TIM Trace Identifier Mismatch
TU Tributary Unit
TUG Tributary Unit Group
U
UAS Unavailable Second
B-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Alarms and Performance Events Reference B Acronyms and Abbreviations
V
VC Virtual Container
Issue 02 (2008-10-15) Huawei Proprietary and Confidential B-3

Alarms and Performance Events Reference Index
Index
A ETH_LOS, 3-60
EXER_FAIL, 3-61
A_LOC, 3-7 EXT_SYNC_LOS, 3-62
ALM_GFP_dCSF, 3-8
ALM_GFP_dLFD, 3-10 F
ALM_GFP_dSSF, 3-11
APS_FAIL, 3-13 FCS_ERR, 3-63
APS_INDI, 3-14 FLOW_OVER, 3-65
AU_LOP, 3-19 FUSE_ALARM, 3-66
AUPJCHIGH, 4-4
AUPJCLOW, 4-5 H
AUPJCNEW, 4-6
HARD_BAD, 3-68
B HP_CROSSTR, 3-70
HP_LOM, 3-73
B1_EXC, 3-21 HP_RDI, 3-75
B1_SD, 3-23 HP_REI, 3-77
B2_EXC, 3-25 HP_SLM, 3-79
B2_SD, 3-27 HP_TIM, 3-80
B3_EXC, 3-29 HP_UNEQ, 3-82
B3_EXC_VC3, 3-31 HPAD_CROSSTR, 3-83
B3_SD, 3-34 HPBBE, 4-8
B3_SD_VC3, 3-36 HPCSES, 4-9
BD_STATUS, 3-39 HPES, 4-10
BDTMPCUR, 4-7 HPFEBBE, 4-11
BDTMPMAX, 4-7 HPFECSES, 4-12
BDTMPMIN, 4-8 HPFEES, 4-13
BIP_EXC, 3-40 HPFESES, 4-14
BIP_SD, 3-42 HPFEUAS, 4-17
BUS_ERR, 3-44 HPSES, 4-15
BUS_LOC, 3-47 HPUAS, 4-16
C I
COMMUN_FAIL, 3-49 IN_PWR_ABN, 3-86
INPWR_FAIL, 3-88
D
J
DBMS_ERROR, 3-52
DN_E1AIS, 3-55 J0_MM, 3-89
E K
E1_LOC, 3-58 K1_K2_M, 3-91
Issue 02 (2008-10-15) Huawei Proprietary and Confidential i-1

Index Alarms and Performance Events Reference
K2_M, 3-92 MSCSES, 4-28

MSES, 4-29
L MSFEBBE, 4-30
MSFECSES, 4-31
LASER_MOD_ERR, 3-94 MSFEES, 4-32
LCAS_FOPR, 3-96 MSFEUAS, 4-36
LCAS_FOPT, 3-98 MSSES, 4-34
LCAS_PLCR, 3-99 MSSW_DIFFRENT, 3-164
LCAS_PLCT, 3-101 MSUAS, 4-35
LCAS_TLCR, 3-104
LCAS_TLCT, 3-107 N
LOOP_ALM, 3-109
LP_CROSSTR, 3-110 NESTATE_INSTALL, 3-165
LP_R_FIFO, 3-113 NO_BD_SOFT, 3-166
LP_RDI, 3-114 NO_LSR_PARA_FILE, 3-169
LP_RDI_VC12, 3-116 NODEID_MM, 3-170
LP_RDI_VC3, 3-117
LP_REI, 3-118 O
LP_REI_VC12, 3-120
LP_REI_VC3, 3-121 OSPITMPCUR, 4-37
LP_RFI, 3-123 OSPITMPMAX, 4-36
LP_SIZE_ERR, 3-124 OSPITMPMIN, 4-37
LP_SLM, 3-125 OUT_PWR_ABN, 3-172
LP_SLM_VC12, 3-127 OUTPWR_FAIL, 3-173
LP_SLM_VC3, 3-128
LP_T_FIFO, 3-130 P
LP_TIM, 3-132
LP_TIM_VC12, 3-133 P_AIS, 3-174
LP_TIM_VC3, 3-135 P_LOS, 3-176
LP_UNEQ, 3-137 PATCH_ERR, 3-178
LP_UNEQ_VC12, 3-138 PATCH_NOT_CONFIRM, 3-179
LP_UNEQ_VC3, 3-140 PATCHFILE_NOTEXIST, 3-180
LPBBE, 4-17 POWER_FAIL, 3-182
LPCSES, 4-19 PROTECT_MODE, 3-183
LPES, 4-20 PWR_MAJ_ALM, 3-185
LPFEBBE, 4-21
LPFECSES, 4-21 R
LPFEES, 4-22
LPFESES, 4-23 R_FIFO_E, 3-186
LPFEUAS, 4-26 R_LOC, 3-188
LPSES, 4-24 R_LOF, 3-190
LPT_INEFFECT, 3-141 R_LOS, 3-192
LPT_RFI, 3-143 R_OOF, 3-194
LPUAS, 4-25, 4-33 RELAY_ALARM, 3-197
LSR_NO_FITED, 3-144 RINGMAPM_MM, 3-198
LSR_WILL_DIE, 3-146 RPLCUR, 4-38
LTI, 3-147 RPLMAX, 4-38
RPLMIN, 4-39
RS_CROSSTR, 3-199
M RSBBE, 4-39
MAINBD_SUBBD_MISMATCH, 3-150 RSCSES, 4-41
MDL_ALARM, 3-152 RSES, 4-41
MS_AIS, 3-156 RSOFS, 4-42
MS_CROSSTR, 3-158 RSSES, 4-43
MS_RDI, 3-159 RSUAS, 4-44
MS_REI, 3-161
MSAD_CROSSTR, 3-154
MSBBE, 4-27
i-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Alarms and Performance Events Reference Index
S
S1_SYN_CHANGE, 3-201
SECU_ALM, 3-202
SNCP_FAIL, 3-203
SNCP_INDI, 3-204
SQUTABM_MM, 3-206
SYN_BAD, 3-210
SYNC_C_LOS, 3-207
SYNC_FAIL, 3-208
T
T_ALOS, 3-212
T_FIFO_E, 3-214
T_LOC, 3-216
T_LOS, 3-218
TC_DEG, 3-220
TC_EXC, 3-223
TC_INCAIS, 3-225
TC_LTC, 3-227
TC_ODI, 3-229
TC_OEI, 3-231
TC_RDI, 3-233
TC_REI, 3-234
TC_TIM, 3-236
TC_UNEQ, 3-239
TEM_HA, 3-240
TEM_LA, 3-242
TEMP_ALARM, 3-244
TF, 3-246
TLBCUR, 4-46
TLBMAX, 4-45
TLBMIN, 4-46
TPLCUR, 4-48
TPLMAX, 4-47
TPLMIN, 4-47
TPS_FAIL, 3-247
TPS_INDI, 3-248
TU_AIS, 3-250
TU_AIS_VC12, 3-253
TU_AIS_VC3, 3-255
TU_LOP, 3-257
TU_LOP_VC12, 3-259
TU_LOP_VC3, 3-262
TUPJCHIGH, 4-48
TUPJCLOW, 4-49
TUPJCNEW, 4-50
U
UP_E1AIS, 3-264
W
W_R_FAILURE, 3-275
WRG_BD_TYPE, 3-274
Issue 02 (2008-10-15) Huawei Proprietary and Confidential i-3


Huwaei Optix Osn 2000

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Huwaei Optix Osn 2000

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX OSN 2000 Enhanced STM-1/STM-4/STM16 Multi-Service

Optical Transmission System

Alarms and Performance Events Reference

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

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

2 Alarm and Performance Event List.........................................................................................2-1

Issue 02 (2008-10-15) Huawei Proprietary and Confidential i

2.2.11 EFT8B Board Alarm List...................................................................................................................2-16

ii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

2.4.5 EMS1 Board Performance Event List..................................................................................................2-37

Issue 02 (2008-10-15) Huawei Proprietary and Confidential iii

iv Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Issue 02 (2008-10-15) Huawei Proprietary and Confidential v

vi Huawei Proprietary and Confidential Issue 02 (2008-10-15)

4 Performance Event Clearing....................................................................................................4-1

Issue 02 (2008-10-15) Huawei Proprietary and Confidential vii

viii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Figure 1-1 SDH alarm signal flow.......................................................................................................................1-2

Issue 02 (2008-10-15) Huawei Proprietary and Confidential ix

Table 1-1 Same type of alarms with different names.........................................................................................1-14

Issue 02 (2008-10-15) Huawei Proprietary and Confidential xi

Table 2-30 RMON performance entry list.........................................................................................................2-30

xii Huawei Proprietary and Confidential Issue 02 (2008-10-15)

About This Document

Product Name Version

OptiX OSN 2000 V100R003

OptiX iManager T2000 V200R007C01

l Network monitoring engineer

Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1

A Glossary Appendix A lists the terms used in this document.

Indicates a hazard with a high level of risk which, if not

Indicates a hazard with a medium or low level of risk which,

Indicates a potentially hazardous situation that, if not

NOTE Provides additional information to emphasize or

Times New Roman Normal paragraphs are in Times New Roman.

2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are

{ x | y | ... } Alternative items are grouped in braces and separated by

[ x | y | ... ] Optional alternative items are grouped in square brackets

{ x | y | ... } * Alternative items are grouped in braces and separated by

Issue 02 (2008-10-15) Huawei Proprietary and Confidential 3

Updates in Issue 02 (2008-10-15)

Updates in Issue 01 (2008-08-30)

4 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

1 Generation of Alarms and Performance

About This Chapter

Issue 02 (2008-10-15) Huawei Proprietary and Confidential 1-1

Figure 1-1 shows the SDH alarm signal flow.

Figure 1-1 SDH alarm signal flow

SPI RST MST MSA HPT HPA LPT

Indicates that the corresponding alarm or signal is generated

1.1.1 Signal Flow Directions and Levels

1-2 Huawei Proprietary and Confidential Issue 02 (2008-10-15)

1.1.2 Two Common Alarms

1.1.1 Signal Flow Directions and Levels

Term Description Figure