Huawei OptiX OSN 550 Alarms and Performance Events Reference (V100R003)

OptiX OSN 550 Multi-Service CPE Optical
Transmission System
V100R003C00
Alarms and Performance Events

Reference
Issue
02
Date
2011-06-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

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

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2011-06-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
OptiX OSN 550 Multi-Service CPE Optical Transmission

System
Alarms and Performance Events Reference
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX OSN 550
V100R003C00
iManager U2000
V100R005C00
Intended Audience
Based on various services of the OptiX OSN, this document describes the troubleshooting
process, which involves background knowledge, information collection, general processing
flow, common troubleshooting methods, and case study.
This document provides guides to get the information about how to handle the troubleshooting.
This document is intended for:
l
Field maintenance engineer
System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
Issue 02 (2011-06-30)
Indicates a hazard with a high level of risk, which if not

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

iii

System
About This Document
Symbol
Description
CAUTION
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save

time.
NOTE
Provides additional information to emphasize or supplement

important points of the main text.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made to previous issues.
Changes in Issue 02 (2011-06-30)

This document is the second release for the V100R003C00 product version. Compared with the
first release, this release has the following new or optimized contents:
l
Added the OUT1TEMP_SENSOR_FAIL alarm.
Added the PATCH_ACT_TIMEOUT alarm.
Added the PATCH_DEACT_TIMEOUT alarm.
Added the PATCH_PKGERR alarm.
Changes in Issue 01 (2011-04-06)

This document for the V100R003C00 version is the first release.
iv

Issue 02 (2011-06-30)

System
Contents
Contents
About This Document...................................................................................................................iii
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-4
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-7
1.2.1 Downlink Signal Flow...........................................................................................................................1-8
1.2.2 Uplink Signal Flow..............................................................................................................................1-11
1.3 Generation and Detection of Alarms and Performance Events in the SDH Lower Order Signal Flow.......1-12
1.3.1 Downlink Signal Flow.........................................................................................................................1-13
1.3.2 Uplink Signal Flow..............................................................................................................................1-14
1.3.3 Difference Between Alarm Signals of PDH Interfaces at Various Rates............................................1-15
1.4 Suppression Correlation Between SDH Alarms...........................................................................................1-16
1.4.1 Intra-Board Alarm Suppression...........................................................................................................1-17
1.4.2 Inter-board Alarm Suppression............................................................................................................1-17
1.5 Generation and Detection of SDH Performance Events...............................................................................1-18
1.5.1 Bit Error................................................................................................................................................1-18
1.5.2 Pointer Justification..............................................................................................................................1-22
2 Generating and Detecting an Ethernet Alarm...................................................................... 2-1

2.1 Detecting Alarms of the Ethernet Transparent Transmission Board..............................................................2-2
2.1.1 Working Principles.................................................................................................................................2-2
2.1.2 Generating and Detecting Module Alarms.............................................................................................2-3
2.2 Detecting Alarms of the Ethernet Switching Board........................................................................................2-6
2.2.1 Working Principles.................................................................................................................................2-7
2.2.2 Generating and Detecting Module Alarms.............................................................................................2-8
2.3 Alarm Correlation.........................................................................................................................................2-13
3 Generation and Detection of SDH Performance Events....................................................3-1

3.1 Bit Error...........................................................................................................................................................3-2
3.2 Pointer Justification.........................................................................................................................................3-6
4 Detecting an Ethernet Performance Event............................................................................4-1

Issue 02 (2011-06-30)

Contents

System
5 Alarm Reference.........................................................................................................................5-1
5.1 Alarm List....................................................................................................................................................... 5-2
5.2 Alarm Clearing..............................................................................................................................................5-11
5.2.1 A_LOC.................................................................................................................................................5-18
5.2.2 ALM_ALS...........................................................................................................................................5-19
5.2.3 APS_FAIL............................................................................................................................................5-20
5.2.4 ALM_GFP_dCSF.................................................................................................................................5-22
5.2.5 ALM_GFP_dLFD................................................................................................................................5-23
5.2.6 APS_INDI............................................................................................................................................5-24
5.2.7 APS_MANUAL_STOP.......................................................................................................................5-26
5.2.8 AU_AIS................................................................................................................................................5-27
5.2.9 AU_LOP...............................................................................................................................................5-29
5.2.10 B1_EXC.............................................................................................................................................5-31
5.2.11 B1_SD................................................................................................................................................5-33
5.2.12 B2_EXC.............................................................................................................................................5-35
5.2.13 B2_SD................................................................................................................................................5-37
5.2.14 B3_EXC.............................................................................................................................................5-39
5.2.15 B3_EXC_VC3....................................................................................................................................5-41
5.2.16 B3_EXC_VC4....................................................................................................................................5-44
5.2.17 B3_SD................................................................................................................................................5-44
5.2.18 B3_SD_VC3.......................................................................................................................................5-46
5.2.19 B3_SD_VC4.......................................................................................................................................5-49
5.2.20 BAT1TEMP_SENSOR_FAIL...........................................................................................................5-50
5.2.21 BAT2TEMP_SENSOR_FAIL...........................................................................................................5-51
5.2.22 BDTEMP_SENSOR_FAIL...............................................................................................................5-52
5.2.23 BD_STATUS.....................................................................................................................................5-54
5.2.24 BIOS_STATUS..................................................................................................................................5-55
5.2.25 BIP_EXC............................................................................................................................................5-56
5.2.26 BIP_SD...............................................................................................................................................5-58
5.2.27 BOOTROM_BAD.............................................................................................................................5-60
5.2.28 BUS_ERR..........................................................................................................................................5-61
5.2.29 BUS_LOC..........................................................................................................................................5-64
5.2.30 CFCARD_FAILED............................................................................................................................5-65
5.2.31 CFCARD_FULL................................................................................................................................5-66
5.2.32 CFCARD_OFFLINE.........................................................................................................................5-68
5.2.33 CFCARD_W_R_DISABLED............................................................................................................5-69
5.2.34 CLK_NO_TRACE_MODE...............................................................................................................5-70
5.2.35 DBMS_ERROR.................................................................................................................................5-72
5.2.36 DBMS_PROTECT_MODE...............................................................................................................5-73
5.2.37 DCC_CHAN_LACK.........................................................................................................................5-74
5.2.38 DOWN_E1_AIS.................................................................................................................................5-75
5.2.39 DOWN_T1_AIS.................................................................................................................................5-77
vi

Issue 02 (2011-06-30)

System
Contents
5.2.40 E1_LOS..............................................................................................................................................5-79
5.2.41 E1_LOC.............................................................................................................................................5-80
5.2.42 ENVHUM_SENSOR_FAIL..............................................................................................................5-81
5.2.43 ENVTEMP_SENSOR_FAIL.............................................................................................................5-83
5.2.44 ENVTEMP1_SENSOR_FAIL...........................................................................................................5-84
5.2.45 ENVTEMP2_SENSOR_FAIL...........................................................................................................5-85
5.2.46 ETH_CFM_LOC................................................................................................................................5-87
5.2.47 ETH_CFM_MISMERGE...................................................................................................................5-89
5.2.48 ETH_CFM_RDI.................................................................................................................................5-91
5.2.49 ETH_CFM_UNEXPERI....................................................................................................................5-93
5.2.50 ETH_LOS...........................................................................................................................................5-95
5.2.51 ETHOAM_DISCOVER_FAIL..........................................................................................................5-96
5.2.52 ETHOAM_RMT_CRIT_FAULT......................................................................................................5-98
5.2.53 ETHOAM_RMT_LOOP....................................................................................................................5-99
5.2.54 ETHOAM_RMT_SD.......................................................................................................................5-101
5.2.55 ETHOAM_SELF_LOOP.................................................................................................................5-102
5.2.56 EX_ETHOAM_CC_LOS.................................................................................................................5-103
5.2.57 EX_ETHOAM_MPID_CNFLCT....................................................................................................5-106
5.2.58 EXT_SYNC_LOS............................................................................................................................5-108
5.2.59 FAN_AGING...................................................................................................................................5-109
5.2.60 FAN_FAIL.......................................................................................................................................5-110
5.2.61 FCS_ERR.........................................................................................................................................5-111
5.2.62 FLOW_OVER..................................................................................................................................5-112
5.2.63 HARD_BAD....................................................................................................................................5-113
5.2.64 HP_CROSSTR.................................................................................................................................5-116
5.2.65 HP_LOM..........................................................................................................................................5-119
5.2.66 HP_R_FIFO.....................................................................................................................................5-120
5.2.67 HP_RDI............................................................................................................................................5-121
5.2.68 HP_REI............................................................................................................................................5-123
5.2.69 HP_SLM...........................................................................................................................................5-125
5.2.70 HP_T_FIFO......................................................................................................................................5-126
5.2.71 HP_TIM...........................................................................................................................................5-127
5.2.72 HP_UNEQ........................................................................................................................................5-129
5.2.73 HPAD_CROSSTR...........................................................................................................................5-130
5.2.74 HSC_UNAVAIL..............................................................................................................................5-132
5.2.75 IN_PWR_ABN.................................................................................................................................5-133
5.2.76 INTEMP_SENSOR_FAIL...............................................................................................................5-135
5.2.77 J0_MM.............................................................................................................................................5-136
5.2.78 K1_K2_M.........................................................................................................................................5-137
5.2.79 K2_M...............................................................................................................................................5-139
5.2.80 LAG_PORT_FAIL...........................................................................................................................5-140
5.2.81 LASER_CLOSED............................................................................................................................5-142
Issue 02 (2011-06-30)

vii
Contents

System
5.2.82 LASER_MOD_ERR........................................................................................................................5-143
5.2.83 LASER_MOD_ERR_EX.................................................................................................................5-144
5.2.84 LCAS_FOPR....................................................................................................................................5-145
5.2.85 LCAS_FOPT....................................................................................................................................5-146
5.2.86 LCAS_PLCR....................................................................................................................................5-147
5.2.87 LCAS_PLCT....................................................................................................................................5-148
5.2.88 LCAS_TLCR...................................................................................................................................5-149
5.2.89 LCAS_TLCT....................................................................................................................................5-150
5.2.90 LCS_DAYS_OF_GRACE...............................................................................................................5-151
5.2.91 LCS_EXPIRED................................................................................................................................5-153
5.2.92 LCS_FILE_NOT_EXIST.................................................................................................................5-154
5.2.93 LINK_ERR.......................................................................................................................................5-155
5.2.94 LOOP_ALM.....................................................................................................................................5-156
5.2.95 LP_CROSSTR.................................................................................................................................5-157
5.2.96 LP_R_FIFO......................................................................................................................................5-158
5.2.97 LP_RDI............................................................................................................................................5-160
5.2.98 LP_RDI_VC12.................................................................................................................................5-161
5.2.99 LP_RDI_VC3...................................................................................................................................5-162
5.2.100 LP_REI...........................................................................................................................................5-163
5.2.101 LP_REI_VC12...............................................................................................................................5-164
5.2.102 LP_REI_VC3.................................................................................................................................5-166
5.2.103 LP_RFI...........................................................................................................................................5-168
5.2.104 LP_SIZE_ERR...............................................................................................................................5-169
5.2.105 LP_SLM.........................................................................................................................................5-170
5.2.106 LP_SLM_VC12.............................................................................................................................5-171
5.2.107 LP_SLM_VC3...............................................................................................................................5-172
5.2.108 LP_T_FIFO....................................................................................................................................5-173
5.2.109 LP_TIM..........................................................................................................................................5-175
5.2.110 LP_TIM_VC12..............................................................................................................................5-176
5.2.111 LP_TIM_VC3................................................................................................................................5-177
5.2.112 LP_UNEQ......................................................................................................................................5-179
5.2.113 LP_UNEQ_VC12...........................................................................................................................5-180
5.2.114 LP_UNEQ_VC3.............................................................................................................................5-181
5.2.115 LPS_UNI_BI_M............................................................................................................................5-183
5.2.116 LPT_RFI.........................................................................................................................................5-184
5.2.117 LSR_BCM_ALM...........................................................................................................................5-185
5.2.118 LSR_NO_FITED...........................................................................................................................5-186
5.2.119 LSR_WILL_DIE............................................................................................................................5-187
5.2.120 LTI..................................................................................................................................................5-188
5.2.121 MS_AIS..........................................................................................................................................5-190
5.2.122 MS_CROSSTR..............................................................................................................................5-191
5.2.123 MS_RDI.........................................................................................................................................5-193
viii

Issue 02 (2011-06-30)

System
Contents
5.2.124 MS_REI..........................................................................................................................................5-195
5.2.125 MSAD_CROSSTR.........................................................................................................................5-196
5.2.126 NESOFT_MM................................................................................................................................5-198
5.2.127 NE_POWER_OVER......................................................................................................................5-200
5.2.128 NESF_LOST..................................................................................................................................5-201
5.2.129 NESTATE_INSTALL...................................................................................................................5-202
5.2.130 NO_BD_SOFT...............................................................................................................................5-203
5.2.131 NO_LSR_PARA_FILE..................................................................................................................5-205
5.2.132 ODC_BATTERY_CURRENT_ABN............................................................................................5-206
5.2.133 ODC_BATTERY_PWRDOWN....................................................................................................5-207
5.2.134 ODC_DOOR_OPEN......................................................................................................................5-209
5.2.135 ODC_FAN_FAILED.....................................................................................................................5-211
5.2.136 ODC_HUMI_ABN........................................................................................................................5-212
5.2.137 ODC_LOAD_PWRDOWN...........................................................................................................5-214
5.2.138 ODC_MDL_ABN..........................................................................................................................5-216
5.2.139 ODC_POWER_FAIL.....................................................................................................................5-218
5.2.140 ODC_SMOKE_OVER...................................................................................................................5-220
5.2.141 ODC_SURGE_PORTECTION_FAIL...........................................................................................5-221
5.2.142 ODC_TEC_ALM...........................................................................................................................5-223
5.2.143 ODC_TEMP_ABN........................................................................................................................5-224
5.2.144 ODC_WATER_ALM....................................................................................................................5-226
5.2.145 OOL................................................................................................................................................5-227
5.2.146 OUT_PWR_ABN...........................................................................................................................5-228
5.2.147 OUT1TEMP_SENSOR_FAIL.......................................................................................................5-230
5.2.148 OUT2TEMP_SENSOR_FAIL.......................................................................................................5-231
5.2.149 P_AIS.............................................................................................................................................5-233
5.2.150 P_LOC............................................................................................................................................5-234
5.2.151 P_LOS............................................................................................................................................5-235
5.2.152 PATCH_ACT_TIMEOUT.............................................................................................................5-236
5.2.153 PATCH_DEACT_TIMEOUT.......................................................................................................5-237
5.2.154 PATCH_ERR.................................................................................................................................5-238
5.2.155 PATCH_NOT_CONFIRM............................................................................................................5-239
5.2.156 PATCH_PKGERR.........................................................................................................................5-240
5.2.157 PATCHFILE_NOTEXIST.............................................................................................................5-240
5.2.158 POWER_ABNORMAL.................................................................................................................5-242
5.2.159 POWER_FAIL...............................................................................................................................5-243
5.2.160 PWR_TEMP_OVERTH................................................................................................................5-245
5.2.161 POWER_MODULE_OFFLINE....................................................................................................5-247
5.2.162 R_APS............................................................................................................................................5-248
5.2.163 R_LOC...........................................................................................................................................5-249
5.2.164 R_LOF............................................................................................................................................5-251
5.2.165 R_LOS............................................................................................................................................5-252
Issue 02 (2011-06-30)

ix
Contents

System
5.2.166 R_OOF...........................................................................................................................................5-254
5.2.167 R_S_ERR.......................................................................................................................................5-256
5.2.168 RELAY_ALARM_CRITICAL......................................................................................................5-257
5.2.169 RELAY_ALARM_IGNORE.........................................................................................................5-258
5.2.170 RELAY_ALARM_MAJOR...........................................................................................................5-259
5.2.171 RELAY_ALARM_MINOR...........................................................................................................5-260
5.2.172 RS_CROSSTR...............................................................................................................................5-261
5.2.173 RTC_FAIL.....................................................................................................................................5-262
5.2.174 S1_SYN_CHANGE.......................................................................................................................5-263
5.2.175 SECU_ALM...................................................................................................................................5-265
5.2.176 SLAVE_WORKING......................................................................................................................5-266
5.2.177 SWDL_ACTIVATED_TIMEOUT................................................................................................5-268
5.2.178 SWDL_AUTOMATCH_INH........................................................................................................5-269
5.2.179 SWDL_CHGMNG_NOMATCH...................................................................................................5-269
5.2.180 SWDL_COMMIT_FAIL...............................................................................................................5-270
5.2.181 SWDL_INPROCESS.....................................................................................................................5-271
5.2.182 SWDL_NEPKGCHECK................................................................................................................5-272
5.2.183 SWDL_PKGVER_MM.................................................................................................................5-273
5.2.184 SWDL_PKG_NOBDSOFT...........................................................................................................5-273
5.2.185 SWDL_ROLLBACK_FAIL..........................................................................................................5-274
5.2.186 SYN_BAD.....................................................................................................................................5-275
5.2.187 SYNC_C_LOS...............................................................................................................................5-276
5.2.188 SYNC_FAIL..................................................................................................................................5-278
5.2.189 T_ALOS.........................................................................................................................................5-279
5.2.190 T_FIFO_E......................................................................................................................................5-280
5.2.191 T_LOC...........................................................................................................................................5-281
5.2.192 T_LOS............................................................................................................................................5-282
5.2.193 T_LOSEX.......................................................................................................................................5-284
5.2.194 TEM_HA........................................................................................................................................5-286
5.2.195 TEM_LA........................................................................................................................................5-287
5.2.196 TEMP_ALARM.............................................................................................................................5-289
5.2.197 TF...................................................................................................................................................5-290
5.2.198 THUNDERALM............................................................................................................................5-291
5.2.199 TR_LOC.........................................................................................................................................5-292
5.2.200 TU_AIS..........................................................................................................................................5-294
5.2.201 TU_AIS_VC12...............................................................................................................................5-295
5.2.202 TU_AIS_VC3.................................................................................................................................5-298
5.2.203 TU_LOP.........................................................................................................................................5-300
5.2.204 TU_LOP_VC12.............................................................................................................................5-301
5.2.205 TU_LOP_VC3...............................................................................................................................5-303
5.2.206 UP_E1_AIS....................................................................................................................................5-305
5.2.207 UP_T1AIS......................................................................................................................................5-306

Issue 02 (2011-06-30)

System
Contents
5.2.208 VCAT_LOA...................................................................................................................................5-307
5.2.209 VCAT_LOM_VC12.......................................................................................................................5-308
5.2.210 VCAT_LOM_VC3.........................................................................................................................5-310
5.2.211 VCAT_LOM_VC4.........................................................................................................................5-311
5.2.212 VCAT_SQM_VC12.......................................................................................................................5-312
5.2.213 VCAT_SQM_VC3.........................................................................................................................5-313
5.2.214 VCAT_SQM_VC4.........................................................................................................................5-314
5.2.215 W_R_FAIL.....................................................................................................................................5-315
5.2.216 WRG_BD_TYPE...........................................................................................................................5-317
6 Performance Event Reference..................................................................................................6-1

6.1 Performance Event List...................................................................................................................................6-2
6.2 Performance Event Clearing........................................................................................................................... 6-5
6.2.1 AUPJCHIGH..........................................................................................................................................6-7
6.2.2 AUPJCLOW...........................................................................................................................................6-9
6.2.3 AUPJCNEW.........................................................................................................................................6-10
6.2.4 BDTEMPCUR.....................................................................................................................................6-11
6.2.5 BDTEMPMAX....................................................................................................................................6-12
6.2.6 BDTEMPMIN......................................................................................................................................6-13
6.2.7 E1_LCV_SDH.....................................................................................................................................6-14
6.2.8 E1_LES_SDH......................................................................................................................................6-15
6.2.9 E1_LSES_SDH....................................................................................................................................6-16
6.2.10 HPBBE...............................................................................................................................................6-17
6.2.11 HPCSES.............................................................................................................................................6-18
6.2.12 HPES..................................................................................................................................................6-20
6.2.13 HPFEBBE..........................................................................................................................................6-22
6.2.14 HPFECSES.........................................................................................................................................6-24
6.2.15 HPFEES.............................................................................................................................................6-25
6.2.16 HPFESES...........................................................................................................................................6-26
6.2.17 HPFEUAS..........................................................................................................................................6-28
6.2.18 HPSES................................................................................................................................................6-29
6.2.19 HPUAS...............................................................................................................................................6-31
6.2.20 LPBBE...............................................................................................................................................6-32
6.2.21 LPCSES..............................................................................................................................................6-34
6.2.22 LPES...................................................................................................................................................6-35
6.2.23 LPFEBBE...........................................................................................................................................6-38
6.2.24 LPFECSES.........................................................................................................................................6-39
6.2.25 LPFEES..............................................................................................................................................6-41
6.2.26 LPFESES............................................................................................................................................6-42
6.2.27 LPFEUAS...........................................................................................................................................6-44
6.2.28 LPSES................................................................................................................................................6-45
6.2.29 LPUAS...............................................................................................................................................6-47
6.2.30 MSBBE..............................................................................................................................................6-48
Issue 02 (2011-06-30)

xi
Contents

System
6.2.31 MSCSES.............................................................................................................................................6-50
6.2.32 MSES.................................................................................................................................................6-51
6.2.33 MSFEBBE..........................................................................................................................................6-53
6.2.34 MSFECSES........................................................................................................................................6-54
6.2.35 MSFEES.............................................................................................................................................6-55
6.2.36 MSFESES...........................................................................................................................................6-56
6.2.37 MSFEUAS.........................................................................................................................................6-58
6.2.38 MSSES...............................................................................................................................................6-59
6.2.39 MSUAS..............................................................................................................................................6-61
6.2.40 OSPITMPCUR...................................................................................................................................6-62
6.2.41 OSPITMPMAX..................................................................................................................................6-63
6.2.42 OSPITMPMIN...................................................................................................................................6-64
6.2.43 RPLCUR............................................................................................................................................6-64
6.2.44 RPLMAX...........................................................................................................................................6-65
6.2.45 RPLMIN.............................................................................................................................................6-66
6.2.46 RSBBE...............................................................................................................................................6-67
6.2.47 RSCSES.............................................................................................................................................6-69
6.2.48 RSES..................................................................................................................................................6-70
6.2.49 RSOFS................................................................................................................................................6-72
6.2.50 RSOOF...............................................................................................................................................6-73
6.2.51 RSSES................................................................................................................................................6-74
6.2.52 RSUAS...............................................................................................................................................6-76
6.2.53 T1_LCV_SDH...................................................................................................................................6-77
6.2.54 T1_LES_SDH....................................................................................................................................6-78
6.2.55 T1_LSES_SDH..................................................................................................................................6-79
6.2.56 TLBCUR............................................................................................................................................6-80
6.2.57 TLBMAX...........................................................................................................................................6-81
6.2.58 TLBMIN.............................................................................................................................................6-82
6.2.59 TPLCUR.............................................................................................................................................6-83
6.2.60 TPLMAX...........................................................................................................................................6-84
6.2.61 TPLMIN.............................................................................................................................................6-84
6.2.62 TUPJCHIGH......................................................................................................................................6-85
6.2.63 TUPJCLOW.......................................................................................................................................6-87
6.2.64 TUPJCNEW.......................................................................................................................................6-88
6.2.65 VC3BBE.............................................................................................................................................6-89
6.2.66 VC3CSES...........................................................................................................................................6-90
6.2.67 VC3ES................................................................................................................................................6-92
6.2.68 VC3FEBBE........................................................................................................................................6-94
6.2.69 VC3FECSES......................................................................................................................................6-96
6.2.70 VC3FEES...........................................................................................................................................6-97
6.2.71 VC3FESES.........................................................................................................................................6-98
6.2.72 VC3FEUAS......................................................................................................................................6-100
xii

Issue 02 (2011-06-30)

System
Contents
6.2.73 VC3SES...........................................................................................................................................6-101
6.2.74 VC3UAS..........................................................................................................................................6-102
A Glossary and Acronyms..........................................................................................................A-1

A.1 Numerics........................................................................................................................................................A-3
A.2 A....................................................................................................................................................................A-3
A.3 B....................................................................................................................................................................A-5
A.4 C....................................................................................................................................................................A-7
A.5 D....................................................................................................................................................................A-9
A.6 E...................................................................................................................................................................A-10
A.7 F...................................................................................................................................................................A-12
A.8 G..................................................................................................................................................................A-14
A.9 H..................................................................................................................................................................A-15
A.10 I..................................................................................................................................................................A-15
A.11 J..................................................................................................................................................................A-17
A.12 L.................................................................................................................................................................A-17
A.13 M................................................................................................................................................................A-18
A.14 N................................................................................................................................................................A-20
A.15 O................................................................................................................................................................A-21
A.16 P.................................................................................................................................................................A-22
A.17 Q................................................................................................................................................................A-24
A.18 R................................................................................................................................................................A-24
A.19 S.................................................................................................................................................................A-26
A.20 T.................................................................................................................................................................A-29
A.21 U................................................................................................................................................................A-30
A.22 V................................................................................................................................................................A-31
A.23 W...............................................................................................................................................................A-31
Issue 02 (2011-06-30)

xiii

System
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-7
Figure 1-3 Generation of alarms between the E1 interface and the cross-connect unit.....................................1-12
Figure 1-4 Structure of the V5 byte....................................................................................................................1-14
Figure 1-5 Structure of the G1 byte....................................................................................................................1-16
Figure 1-6 Suppression relations among key alarms..........................................................................................1-17
Figure 1-7 Inter-board alarm suppression relations............................................................................................1-18
Figure 1-8 Error detection relation and location................................................................................................1-20
Figure 1-9 Location and content of AU_PTR....................................................................................................1-23
Figure 2-1 Functional modules of the Ethernet transparent transmission board..................................................2-2
Figure 2-2 Positions of alarms in the transparent transmission board ................................................................2-3
Figure 2-3 Concepts of the uplink and downlink.................................................................................................2-6
Figure 2-4 Functional modules of the Ethernet switching board.........................................................................2-7
Figure 2-5 Positions of alarms in the switching board ........................................................................................2-8
Figure 2-6 Concepts of the uplink and downlink...............................................................................................2-12
Figure 3-1 Error detection relation and location..................................................................................................3-3
Figure 3-2 Location and content of AU_PTR......................................................................................................3-6
Figure 4-1 Performance reporting flow................................................................................................................4-2
Issue 02 (2011-06-30)

xv

System
Tables
Tables
Table 1-1 Modes and application scenarios of alarm reversion...........................................................................1-5
Table 1-2 Same type of alarms with different names.........................................................................................1-15
Table 1-3 Bit error terms....................................................................................................................................1-20
Table 1-4 Alarms and performance events related to bit errors.........................................................................1-21
Table 1-5 Pointer justification state....................................................................................................................1-23
Table 2-1 Board alarms........................................................................................................................................2-3
Table 2-2 Port management module alarms.........................................................................................................2-4
Table 2-3 Alarms of the Ethernet data processing module...................................................................................2-4
Table 2-4 Encapsulation module alarms..............................................................................................................2-4
Table 2-5 Mapping module alarms (LCAS and virtual cascading)......................................................................2-5
Table 2-6 Mapping module alarms (SDH)...........................................................................................................2-6
Table 2-7 Port management module alarms.........................................................................................................2-9
Table 2-8 Alarms of the Ethernet data processing module.................................................................................2-10
Table 2-9 Encapsulation module alarms............................................................................................................2-11
Table 2-10 Mapping module alarms (LCAS and virtual cascading)..................................................................2-11
Table 2-11 Mapping module alarms (SDH).......................................................................................................2-12
Table 2-12 Correlation between Ethernet alarms and Mapping module alarms................................................2-13
Table 2-13 Correlation between Ethernet alarms...............................................................................................2-14
Table 3-1 Bit error terms......................................................................................................................................3-3
Table 3-2 Alarms and performance events related to bit errors...........................................................................3-5
Table 3-3 Pointer justification state......................................................................................................................3-7
Table 5-1 Alarm list..............................................................................................................................................5-2
Table 5-2 Alarms that may cause the TU_AIS alarm.......................................................................................5-295
Table 6-1 Pointer justification performance events..............................................................................................6-2
Table 6-2 E1 line side bit error performance events.............................................................................................6-2
Table 6-3 Regenerator section bit error performance events................................................................................6-2
Table 6-4 Multiplex section bit error performance events...................................................................................6-3
Table 6-5 Higher order path bit error performance events...................................................................................6-3
Table 6-6 Lower order path bit error performance events....................................................................................6-3
Table 6-7 T1 line side bit error performance events.............................................................................................6-4
Table 6-8 Equipment function performance events..............................................................................................6-4
Table 6-9 VC3 path bit error performance events................................................................................................6-5
Issue 02 (2011-06-30)

xvii

System
1 Generation of Alarms and Performance Events of SDH

Services
Generation of Alarms and Performance

Events of SDH Services
About This Chapter

This topic describes the generation and detection of alarms and performance events in the SDH
services.
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 inservice 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 (2011-06-30)

1-1

Services

System
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 inservice 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
AIS
J0-MM
(J0)
RS-BIP Err.
(B1)
"1"
MS-AIS
(K2)
AIS
MS-BIP Err.
(B2)
MS-REI
(M1)
MS-RDI
(K2)
"1"
AU-AIS
(H1,H2,H3)
AU-LOP
(H1,H2)
HP-SLM, HP-UNEQ
"1"
(C2)
HP-TIM
AIS
(J1)
HP-BIP Err.
(B3)
HP-REI
(G1)
HP-RDI
(G1)
"1"
TU-AIS
(V1,V2,V3)
TU-LOP
(V1,V2)
HP-LOM
(H4)
LP-UNEQ
(V5)
LP-TIM
(J2)
LP-BIP Err.
(V5)
LP-REI
(V5)
LP-RDI
(V5)
LP-SLM
(V5)
"1"
AIS
"1"
AIS
Indicates that the corresponding alarm or signal is generated

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

1-2

Issue 02 (2011-06-30)

System

Services
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.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
Downlink
signal
flow
A signal direction: SDH interface

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

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

interface and the cross-connect
unit.
Higer order part
SDH
interface
Crossconnect
unit
SDH
interface
PDH interface
Lower
order path
The path between the crossconnect unit and the PDH

interface.
SDH
interface
Crossconnect
unit
SDH
interface
PDH interface
Lower order part
Issue 02 (2011-06-30)

1-3

Services

System
1.1.2 Two Common Alarms

This section describes two types of common alarms: AIS and RDI.
Alarm
Description
Alarm Indication Signal

(AIS)
The all "1"s signal that is inserted into the lower level circuit
indicates that the signal is unavailable. The MS_AIS, AU_AIS,
TU_AIS and E1_AIS alarms are common AIS alarms.
Remote Defect Indication

(RDI)
This alarm indicates that the opposite NE has detected the loss
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.
The process of alarm reporting is as follows:
l
A board detects and reports the alarm to the NE software.
The NE software reports the alarm to the U2000 server.
Through the U2000 client, the user queries the alarm on the U2000 server.
In the entire process, alarms are saved on the U2000 after three levels of processing.
l
Alarm suppression
Alarm auto-report
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 iManager
U2000 subnet level management system (U2000) immediately after this alarm occurs. An alarm
panel is displayed on the U2000, where users can check the information about the alarm. Users
1-4

Issue 02 (2011-06-30)

System

Services
can also disable this function for certain alarms. This reduces the impact of a large number of
alarms on the U2000 performance.
Alarm Filter
When the alarm filter function is enabled on the U2000, it does not affect the alarms on the NE.
The U2000 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 U2000
discards the alarms, and the alarms are not saved into the alarm database. If the function is
disabled, the U2000 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 interference
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,
as listed in Table 1-1.
Table 1-1 Modes and application scenarios of alarm reversion
Issue 02 (2011-06-30)
Reversion Mode
Handling Method
Application Scenario
Non-revertive
This mode indicates the normal alarm

monitoring state, and is the default alarm
mode. In this mode, the alarm reversion
function cannot be enabled on a port.
In the case of ports that

carry services, you can use
this mode. Therefore, the
alarm state of a port can
indicate the actual state of
the port.

1-5

Services

System
Reversion Mode
Handling Method
Application Scenario
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.
After the system

commissioning, the
reported alarms indicate
nothing if the ports are not
configured with services.
In this case, you can set the
reversion mode to autorevertive. After the
reversion function is
enabled, alarm reporting
stops.
When the ports are
configured with services,
the reversion function is
automatically disabled if
the current alarms are
cleared. In this manner,
normal alarm reporting is
not affected.
Manual-revertive
In this mode, the alarm reversion function

can be enabled on a port, regardless of
whether any alarms exist on this port.
l When the alarm reversion function is
enabled on a port, the alarm state
reported by the port is opposite to the
actual alarm state.
l 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
identical with the actual alarm state.
1-6

This mode can be used in

certain special scenarios.
For example, in the case of
ports that do not carry
services but need to be
tested regularly, the alarms
indicate nothing and you
can use this mode to stop
alarm reporting.
If you use the autorevertive mode, the
reversion function is
automatically disabled
when alarm reporting
stops (for example, the
BER tester is used to test
the equipment). Therefore,
you can use the manualrevertive mode to enable
alarm reversion on the
port.
Issue 02 (2011-06-30)

System

Services
CAUTION
l Alarm reversion must be set on a port basis.
l After alarm reversion is enabled, the alarm state of the board, including the state of the alarm
indicators on the board, remains unchanged and indicates the running state of the equipment.
l You can obtain information about the actual alarm state of a board by querying the alarms
reported by the board.
l The alarm reversion function is implemented by the NE software. The alarm data on the NE
and the alarm data on the NMS are the same. The alarm data 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
RS overhead processor
(RST)
LOS
STM-N
optical
interface
A1,
A2
"1"
AIS
MS-AIS
LOF
K2
BI Err.
B1
Pointer processor and

HP overhead processor
(MSA, HPT)
MS overhead
processor
(MST)
B2
M1
B2-Err.
MS-REI
K2
"1"
AIS
H1,H2
H1,H2
J1
C2
C2
MS-RDI
H4
B3
G1
AU-AIS
AU-LOP
HP-TIM
HP-UNEQ
HP-SLM
HP-LOM
B3 Err.
HP-REI
G1
Downlink signal flow Signal

transfer point (Insert down all "1"s
signal)
Cross"1" connect
unit
HP-RDI
Alarm report or return Alarm

termination point
(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
Multiplex section overheads
Issue 02 (2011-06-30)

1-7

Services
Higher order path overheads
Lower order path overheads

System
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)
Regenerator section trace byte (J0)
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.
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.
1-8

Issue 02 (2011-06-30)

System

Services
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)
MS bit interleaved parity code (BIP-24) byte (B2)
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
Issue 02 (2011-06-30)
Detecting the B2 byte and the M1 byte

1-9

Services

System
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)
Signal label byte (C2)
Higher order path bit interleaved parity code (path BIP-8) byte (B3)
Path status byte (G1)
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.
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.
1-10

Issue 02 (2011-06-30)

System

Services
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.
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.
Issue 02 (2011-06-30)

1-11

System

Services
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
Crossconnect
board
V5
V5
J2
V1, V2
V1, V2
"1''
T-ALOS
LP-SLM
LP-UNEQ
LP-TIM
LP-TFIFO
TU-LOP
TU-AIS
E1
interface
H4 HP-LOM
V5
LP-RDI
"1''
V5
E1AIS
BIP-2
LP-REI
V5
LP-RFIFO
Signal flow
Signal transfer point
(Insert all "1"s signal)
Alarm report or return

Alarm termination point
(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:
1-12

Issue 02 (2011-06-30)

System

Services
Higher order path adaptation (HPA)
Lower order path termination (LPT)
Lower order path adaptation (LPA)
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)
Path state and signal label byte (V5)
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.
Issue 02 (2011-06-30)

1-13

System

Services
Figure 1-4 Structure of the V5 byte

V5
byte
b1
b2
b3
b4
BIP-2 error check 1:LP-REI Unused

Inconsistent:LPBBE
b5
b6
b7
Signal label
000:LP-UNEQ
b8
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.
1-14

Issue 02 (2011-06-30)

System

Services
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

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

Board
External signal loss occurs.
T_ALOS

Board
P_LOS
140 Mbit/s electrical

PDH Board
EXT_LOS

Board
Signals in the downstream signal flow

are all "1"s.

Board
Issue 02 (2011-06-30)

UP_E1AIS and
DOWN_E1AIS
P_AIS
1-15

Services
Board

System
Condition
Alarm

PDH Board
PDH Board
C4_R_LAISD
Signals in the upstream signal flow are
all "1"s.
C4_T_LAISD
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 PDH 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
b1
b2
b3
LP-REI
b4
b5
LP-RDI
b7
b6
Reserved
b8
Spare
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.
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-16

Issue 02 (2011-06-30)

System

Services
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
TU_AIS
R_LOF
J0_MM
MS_AIS
B1_EXC
TU_LOP
B2_EXC
BIP_EXC
AU_AIS
B3_EXC
HP_TIM
AU_LOP
HP_SLM
B3_SD
HP_LOM
TU_AIS
LP_UNEQ
For example:
B1_SD
B2_SD
HP_UNEQ
TU_LOP
BIP_EXC
LP_TIM
LP_SLM
BIP_SD
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.
Issue 02 (2011-06-30)

1-17

Services

System
Figure 1-7 Inter-board alarm suppression relations

R_LOS
R_LOC
R_LOF
MS_AIS
AU_LOP
HP_LOM
AU_AIS
TU_AIS
A
TU_AIS_VC3
TU_AIS_VC12
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

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
1.5.1 Bit Error

1-18

Issue 02 (2011-06-30)

System

Services
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.
Issue 02 (2011-06-30)

1-19

Services

System
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.
MST is multiplex section termination.
HPT is higher order path termination.
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-3 lists the relevant terms.
Table 1-3 Bit error terms
1-20
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.
Issue 02 (2011-06-30)

System

Services
Term
Description
ES
Errored second. It indicates a certain second that is detected with one or more
errored blocks.
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-4 lists the alarms and performance events related to bit errors.
Table 1-4 Alarms and performance events related to bit errors
Item
Regener
ator
section
Issue 02 (2011-06-30)
Performance Event
Alarm
If the bit
errors
exceed the
threshold at
the local
station, the
local station
reports the
relevant
event.
If the bit
errors exceed
the threshold
at the local
station, the
opposite
station
reports the
relevant
event.
If the bit errors

exceed the
threshold at the
local station, the
local station
reports the alarm.
If the bit errors

exceed the
threshold at the
local station, the
opposite station
reports the alarm.
RSBBE
B1_SD/B1_EXC

1-21

Services
Item

System
Performance Event
Alarm
If the bit
errors
exceed the
threshold at
the local
station, the
local station
reports the
relevant
event.
If the bit
errors exceed
the threshold
at the local
station, the
opposite
station
reports the
relevant
event.
If the bit errors

exceed the
threshold at the
local station, the
local station
reports the alarm.
If the bit errors

exceed the
threshold at the
local station, the
opposite station
reports the alarm.
Multiple
x section
MSBBE
MSFEBBE
B2_SD/B2_EXC
MS_REI
Higher
order
path
HPBBE
HPFEBBE
B3_SD/B3_EXC
HP_REI
Lower
order
path
LPBBE
LPFEBBE
BIP_SD/BIP_EXC
LP_REI
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-22

Issue 02 (2011-06-30)

System

Services
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
Y Byte: 1001SS11
1* Byte: 11111111
(S Unspecified )
9
270columns
10
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-5.
Table 1-5 Pointer justification state
State
Name
Pointer
zero
justificat
ion
Issue 02 (2011-06-30)
Byte Numbering and Content of the Fourth Row in the STM-1

Frame
7
10
11
12
H3
H3
H3
Informat
ion
Informat
ion
Informati
on

Rate
Relatio
n
Informat
ion =
containe
r
1-23

System

Services
State
Name

Frame
Rate
Relatio
n
10
11
12
Positive
pointer
justificat
ion
H3
H3
H3
Stuffing
Stuffing
Stuffing
Informat
ion <
containe
r
Negative
pointer
justificat
ion
Informat
ion
Informati
on
Informat
ion
Informat
ion
Informat
ion
Informati
on
Informat
ion >
containe
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.
TU pointer justification occurs during demultiplexing.

If the system clock is not consistent with the received clock, TU pointer justification occurs
during demultiplexing.
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.
1-24

Issue 02 (2011-06-30)

System

Services
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.
Issue 02 (2011-06-30)

1-25

System
2 Generating and Detecting an Ethernet Alarm
Generating and Detecting an Ethernet Alarm
About This Chapter

The OptiX OSN equipment provides multiple types of Ethernet processing boards to support
different Ethernet services. For different Ethernet services, alarm detection methods are slightly
different because the processing modules are different. This topic describes the alarm detection
principle of each type of Ethernet boards.
2.1 Detecting Alarms of the Ethernet Transparent Transmission Board
This topic describes the functions and alarm detection mechanism of each module on the Ethernet
transparent transmission board.
2.2 Detecting Alarms of the Ethernet Switching Board
switching board.
2.3 Alarm Correlation
Derivation and suppression exist among SDH alarms. Ethernet alarms, however, are scattered
among various functional modules. This topic describes the correlation between Ethernet alarms
and between Ethernet alarms and SDH alarms.
Issue 02 (2011-06-30)

2-1

System
2.1 Detecting Alarms of the Ethernet Transparent

Transmission Board
transparent transmission board.
2.1.1 Working Principles
The Ethernet transparent transmission board consists of the port management module, Ethernet
data processing module, encapsulation module, and mapping module.
2.1.2 Generating and Detecting Module Alarms
Ethernet service alarms are monitored at the relevant functional modules of the switching board.

The Ethernet transparent transmission board consists of the port management module, Ethernet
data processing module, encapsulation module, and mapping module.
Figure 2-1 shows the functional modules of the Ethernet transparent transmission board.
Figure 2-1 Functional modules of the Ethernet transparent transmission board
Uplink
Ethernet
Port
management
module
Ethernet data
processing
module
Encapsulation module
Mapping
module
Crossconnect
unit
SDH
Donwlink
NOTE
The functions supported by different modules may be different from each other.
Port Management Module

This module implements the serial-to-parallel conversion, code conversion, and auto-negotiation
of working modes.
Ethernet Data Processing Module

This module receives and transmits Ethernet frames, implements flow control, processes
JUMBO frames, and performs Ethernet performance statistics.
Encapsulation Module
This module supports the GFP, LAPS, and HDLC encapsulation modes. It also encapsulates
and decapsulates data.
2-2

Issue 02 (2011-06-30)

System
Mapping Module
In the uplink direction, this module maps encapsulated HDLC/LAPS/GFP packets into VCtrunks and multiplexes the VC-trunks into VC-4s to map Ethernet frames into SDH frames.
In the downlink direction, this module maps SDH frames into Ethernet frames.

The Ethernet board inspects whether a module is exceptional. If yes, the module directly reports
an exception alarm to the NE. This topic describes the principles of generating and detecting
alarms of each unit of the transparent transmission board by module.
Figure 2-2 shows the positions of alarms in the transparent transmission board.
Figure 2-2 Positions of alarms in the transparent transmission board
Port
management
module
Ethernet
Bottom-layer chip
register
Ethernet data
processing
module
Board software
RPR protocol
LAG_FAIL
ETH_LOS
LOOP_ALM
RPR
protocol
module
Encapsulation
module
Internal chip
of a board
RPR alalrm
Crossconnect
unit
SDH
Board software
ALM_GFP_dLFD
LPT protocol
FCS_
ERR
LPT_RFI
Board
software
Mapping
module
LINK_ERR
LCAS_BAND_DEC
REASED
Virtual cascading
alarm
LCAS protocol
LCAS alarm
LASER_MOD_ERR
Hardware
logic
TU alalrm indication at
the VC-3/VC-12 level
FLOW_OVER
TU LOP at the VC-3/

VC-12 level
LSR_NO_FITED
BIP BER
Indicates that corresponding alarms are generated.
XXX
Indicates that xxx alarm is detected and reported.
Detecting Board Alarms

This type of alarms describes the in-position status of a board, the exceptional status of a chip,
the uploading status of software, and the communication status of a board. These alarms are
independent of functional modules.
Table 2-1 lists certain board alarms.
Table 2-1 Board alarms
HARD_BAD
NO_BD_SOFT
SLAVE_WORKING
BD_STATUS
Detecting Port Management Module Alarms

Table 2-2 lists certain alarms reported by the port management module and corresponding
detection principles.
Issue 02 (2011-06-30)

2-3

System
Table 2-2 Port management module alarms

Alarm
Detection Principle
ETH_LOS
The bottom-layer chip register detects the signal connection

status of the Ethernet port. The board software decides whether
to report the alarm according to the value of the chip register.
LOOP_ALM
The bottom-layer chip register detects the loopback status of the

Ethernet port. The board software decides whether to report the
alarm according to the value of the chip register.
LINK_ERR
The bottom-layer chip register detects the negotiation status of

the Ethernet port. The board (EGT) software decides whether to
report the alarm according to the value of the chip register.
LSR_NO_FITED
The hardware logic detects whether an optical module is in

position. The board software decides whether to report the alarm
according to the read hardware interface data.
LASER_MOD_ERR
The board software detects whether the optical module type is

matched and then decides whether to report the alarm according
to the detection result.
Detecting Alarms of the Ethernet Data Processing Module

Table 2-3 lists certain alarms reported by the Ethernet data processing module and corresponding
Table 2-3 Alarms of the Ethernet data processing module
Alarm
Detection Principle
EX_ETHOAM_CC_LOS
The alarm is reported to the NE for display.
LPT_RFI
Whether to report the alarm to the NE for display depends on

the detection result.
Detecting Encapsulation Module Alarms

Table 2-4 lists certain alarms reported by the encapsulation module and corresponding detection
principles.
Table 2-4 Encapsulation module alarms
2-4
Alarm
Detection Principle
ALM_GFP_dLFD
The internal chip of the board aligns GFP frames. If an error

occurs during frame alignment, the board reports the alarm to
the NE for display.

Issue 02 (2011-06-30)

System
Alarm
Detection Principle
FCS_ERR
The internal chip of the board performs FCS check on GFP

frames. If an error occurs during FCS check, the board reports
the alarm to the NE for display.
Detecting Mapping Module Alarms

Table 2-5 lists certain alarms reported by the mapping module and corresponding detection
principles.
Table 2-5 Mapping module alarms (LCAS and virtual cascading)
Alarm
Detection Principle
LCAS_TLCR
The LCAS protocol detects changes to the uplink bandwidth.

When the bandwidth of all members in the uplink direction is
lost, the platform reports the alarm to the NE in the peer
downlink direction.
NOTE
For concepts of the uplink and downlink, see Figure 2-3.
LCAS_TLCT
The LCAS protocol detects changes to the downlink

bandwidth. When the bandwidth of all members in the
downlink direction is lost, the platform reports the alarm to
the NE in the peer uplink direction.
LCAS_FOPR
The alarm is reported when the LCAS module detects that the
protocol is invalid in the receiving direction of the LCAS.
LCAS_FOPT
protocol is invalid in the transmitting direction of the LCAS.
LCAS_PLCR

When the bandwidth of certain members in the uplink
direction is lost, the platform reports the alarm to the NE in
the peer downlink direction.
LCAS_PLCT

bandwidth. When the bandwidth of certain members in the
VCAT_LOA
The board software detects the delay time of passing through

the timeslot bound to the VC-trunk. If the delay time exceeds
the allowed virtual cascading delay, the alarm is reported to
the NE.
VCAT_LOM_VC12
The board software detects the MFI in the timeslots at

different levels, and decides whether to report the alarm to the
NE according to the detection result.
VCAT_LOM_VC3
VCAT_LOM_VC4
Issue 02 (2011-06-30)

2-5

System
Alarm
Detection Principle
VCAT_SQM_VC12
The board software detects the sequence in the timeslots at

VCAT_SQM_VC3
VCAT_SQM_VC4
Figure 2-3 Concepts of the uplink and downlink

Uplink
Source
port
Sink
port
Donwlink
Uplink: services towards the source port
Donwlink: services towards the sink port
Table 2-6 lists certain SDH alarms reported by the mapping module.
Table 2-6 Mapping module alarms (SDH)
AU_AIS
B3_EXC_VC3
B3_SD_VC3
BIP_EXC
BIP_SD
HP_LOM
LP_RDI_VC12
LP_RDI_VC3
LP_REI_VC12
LP_REI_VC3
LP_SLM_VC12
LP_SLM_VC3
LP_TIM_VC12
LP_TIM_VC3
LP_UNEQ_VC12
LP_UNEQ_VC3
TU_AIS_VC12
TU_AIS_VC3
TU_LOP_VC12
TU_LOP_VC3
T_LOS
B3_EXC_VC4
B3_SD_VC4
2.2 Detecting Alarms of the Ethernet Switching Board

switching board.
The Ethernet switching board consists of the port management module, Ethernet data processing
module, encapsulation module, and mapping module.
2-6

Issue 02 (2011-06-30)

System

The Ethernet switching board consists of the port management module, Ethernet data processing
module, encapsulation module, and mapping module.
Figure 2-4 shows the functional modules of the Ethernet switching board.
Figure 2-4 Functional modules of the Ethernet switching board
Uplink
Ethernet
Port
management
module
Ethernet data
processing
module
Encapsulation module
Mapping
module
Crossconnect
unit
SDH
Donwlink
NOTE
The functions supported by different modules may be different from each other.
Port Management Module

This module manages the ports for transmitting Ethernet commands between the board and the
NE. Through this module, you can set and query the following functions:
l
Port enabling
Port encapsulation format
Default VLAN value of a port
Tag-Aware/Tag-Access property of a port
Enabling of packet entry detection
Working mode of a port
Flow control
Maximum packet length on a port
Loopback on ports
Ethernet Data Processing Module

This module configures and processes Ethernet services, including:
l
EPL, EVPL, EPLAN, and EVPLAN services
Layer-2 switching function
RSTP, IGMP, LAG, 802.lag, 802.3ah, OAM and LPT protocols
Encapsulation Module
This module supports the GFP, LAPS, and HDLC encapsulation modes. It also encapsulates
and decapsulates data.
Issue 02 (2011-06-30)

2-7

System
Mapping Module
In the uplink direction, this module maps encapsulated HDLC/LAPS/GFP packets into VCtrunks and multiplexes the VC-trunks into VC-4s to map Ethernet frames into SDH frames.
In the downlink direction, this module maps SDH frames into Ethernet frames.

The Ethernet board inspects whether a module is exceptional. If yes, the module directly reports
an exception alarm to the NE. This topic describes the principles of generating and detecting
alarms of each unit of the switching board by module.
Figure 2-5 shows the positions of alarms in the switching board.
Figure 2-5 Positions of alarms in the switching board
Ethernet
data
processing
module
Port
management
module
Ethernet
Bottom-layer chip
register
ETH_LOS
LINK_ERR
PORTMODE_
MISMATCH
Hardware
logic
Board
software
ALM_GFP_dCSF
ETHOAM alarm
LPT protocol
LCAS protocol
Internal chip
of a board
LPT_RFI
Board software
Crossconnect
unit
Mapping
module
SDH
Board software
Board software
OAM upper-layer
protocol
LOOP_ALM
Encapsulation
module
Virtual cascading
alarm
LCAS_TLCR
ALM_GFP_dLFD
LCAS_TLCT
FCS_ERR
LCAS_FOPR
LAG alarm
LSR_NO_FITED
LCAS_FOPT
LASER_MOD_ERR
LCAS_PLCT
LCAS_TLCR
Input/output optical power

alarm
TU alalrm indication at
the VC-3/VC-12 level
Temperature alarm
TU LOP at the VC-3/

VC-12 level
Laser bias current alarm

Port traffic alarm
Security
check system
of the optical
module
BIP BER
TF
Indicates that corresponding alarms are generated.

XXX
Indicates that xxx alarm is detected and reported.
Detecting Board Alarms

As shown in Table 2-1, this type of alarms describes the in-position status of a board, the
exceptional status of a chip, the uploading status of software, and the communication status of
a board. These alarms are independent of functional modules.
Detecting Port Management Module Alarms

Table 2-7 lists certain alarms reported by the port management module and corresponding
2-8

Issue 02 (2011-06-30)

System
Table 2-7 Port management module alarms

Alarm
Detection Principle
ETH_LOS
The bottom-layer chip register detects the signal

connection status of the Ethernet port. The board software
decides whether to report the alarm according to the value
of the chip register.
LOOP_ALM
The bottom-layer chip register detects the loopback status

of the Ethernet port. The board software decides whether
to report the alarm according to the value of the chip
register.
LINK_ERR
The bottom-layer chip register detects the negotiation

status of the Ethernet port. The board software decides
whether to report the alarm according to the value of the
chip register.
LSR_NO_FITED
The hardware logic detects whether an optical module is

in position. The board software decides whether to report
the alarm according to the read hardware interface data.
LASER_MOD_ERR
The board software detects whether the optical module

type is matched and then decides whether to report the
alarm according to the detection result.
IN_PWR_ABN
The board software reads the input power of an optical

module. If the input power exceeds the upper threshold or
the lower threshold, the alarm is reported to the NE.
OUT_PWR_ABN
The board software reads the output power of an optical

module. If the output power exceeds the upper threshold
or the lower threshold, the alarm is reported to the NE.
LSR_WILL_DIE
The board software reads the bias current of an optical

module. When the bias current exceeds relevant
thresholds, the alarm is reported to the NE.
LSR_BCM_ALM
TEM_HA
The board software reads the temperature of an optical

module. If the temperature exceeds the upper threshold or
the lower threshold, the alarm is reported to the NE.
TEM_LA
Issue 02 (2011-06-30)
TF
The security system of an optical module detects that the

laser works abnormally and notifies the exception to the
board hardware logic. The board software reads the value
of the hardware logic and then decides whether to report
the alarm according to the judgement result.
FLOW_OVER
The board software detects whether the traffic received on

a port exceeds the preset threshold and then decides
whether to report the alarm according to the judgement
result.

2-9

System
Detecting Alarms of the Ethernet Data Processing Module

Table 2-8 lists certain alarms reported by the Ethernet data processing module and corresponding
Table 2-8 Alarms of the Ethernet data processing module
Alarm
Detection Principle
EX_ETHOAM_CC_LOS
If the periodic connectivity check packet of the 802.1ag

protocol of the board is lost, the alarm is reported to the NE
for display.
EX_ETHOAM_MPID_C
ONFLICT
The OAM upper-layer protocol detects the connection status

of Ethernet links. If the 802.1ag protocol of the board receives
the protocol packet containing the same maintenance point ID
as the board, the alarm is reported to the NE for display.
ETHOAM_RMT_LOOP
The OAM upper-layer protocol detects whether the local end

or peer end issues the loopback command. Whether to report
the alarm to the NE for display depends on the detection result.
ETHOAM_RMT_SD
The OAM upper-layer protocol detects whether the Ethernet

port receives the link event notification packet from the peer
end. Whether to report the alarm to the NE for display depends
on the detection result.
ETHOAM_RMT_CRIT_
FAULT
The OAM upper-layer protocol detects whether the Ethernet

port receives the OAM packet containing major faults from
the peer end. Whether to report the alarm to the NE for display
depends on the detection result.
ETHOAM_DISCOVER_F
AIL
The alarm is reported to the NE for display when the OAM

upper-layer protocol detects the negotiation failure between
the Ethernet port and the peer equipment.
ETHOAM_SELF_LOOP
The OAM upper-layer protocol detects the loopback status of

a MAC or VCTRUNK port. Whether to report the alarm to
the NE for display depends on the detection result.
LAG_PORT_FAIL
The board software detects the Ethernet port or VCTRUNK

LAG ports, and decides whether to report the alarm to the NE
for display according to the detection result.
LPT_RFI
Whether to report the alarm to the NE for display depends on

the detection result.
Detecting Encapsulation Module Alarms

Table 2-9 lists certain alarms reported by the encapsulation module and corresponding detection
principles.
2-10

Issue 02 (2011-06-30)

System
Table 2-9 Encapsulation module alarms

Alarm
Detection Principle
ALM_GFP_dLFD
The internal chip of the board aligns GFP frames. If an error

occurs during frame alignment, the board reports the alarm to
the NE for display.
FCS_ERR
The internal chip of the board performs FCS check on GFP

frames. If an exception occurs during FCS check, the board
reports the alarm to the NE for display.
ALM_GFP_dCSF
The board software detects the ID received by the port. If the

port receives the GFP management frame containing the
correct type header error control (THEC) and with the payload
type indictor (PTI) as 100 and the user payload identifier (UPI)
as 0000 0001, the alarm is reported to the NE for display.
NOTE
For the GFP protocol, see G.7041.
Detecting Mapping Module Alarms

Table 2-10 lists certain alarms reported by the LCAS and the virtual cascading modules, and
corresponding detection principles.
Table 2-10 Mapping module alarms (LCAS and virtual cascading)
Alarm
Detection Principle
LCAS_TLCR

When the bandwidth of all members in the uplink direction is
lost, the platform reports the alarm to the NE in the peer
downlink direction.
NOTE
For concepts of the uplink and downlink, see Figure 2-6.
Issue 02 (2011-06-30)
LCAS_TLCT

bandwidth. When the bandwidth of all members in the
the NE in the peer downlink direction.
LCAS_FOPR
protocol is invalid in the receiving direction of the LCAS.
LCAS_FOPT
protocol is invalid in the transmitting direction of the LCAS.
LCAS_PLCR

When the bandwidth of certain members in the uplink
direction is lost, the platform reports the alarm to the NE in
the peer downlink direction.

2-11

System
Alarm
Detection Principle
LCAS_PLCT

bandwidth. When the bandwidth of certain members in the
VCAT_LOA
The board software detects the delay time of passing through

the timeslot bound to the VC-trunk. If the delay time exceeds
the allowed virtual cascading delay, the alarm is reported to
the NE.
VCAT_LOM_VC12
The board software detects the multiple frame indictor field

(MFI) in the timeslots at different levels, and decides whether
to report the alarm to the NE according to the detection result.
VCAT_LOM_VC3
VCAT_SQM_VC12
VCAT_SQM_VC3
The board software detects the sequence in the timeslots at

Figure 2-6 Concepts of the uplink and downlink

Uplink
Source
port
Sink
port
Donwlink
Uplink: services towards the source port
Donwlink: services towards the sink port
Table 2-11 lists certain SDH alarms reported by the mapping module.
Table 2-11 Mapping module alarms (SDH)
2-12
AU_AIS
B3_EXC_VC3
B3_SD_VC3
HP_UNEQ
HP_TIM
HP_SLM
HP_RDI
HP_REI
AU_LOP
LP_UNEQ_VC3
LP_TIM_VC3
LP_SLM_VC3
TU_AIS_VC3
TU_LOP_VC3
LP_RDI_VC3
LP_REI_VC3
T_LOS

Issue 02 (2011-06-30)

System
2.3 Alarm Correlation

Derivation and suppression exist among SDH alarms. Ethernet alarms, however, are scattered
among various functional modules. This topic describes the correlation between Ethernet alarms
and between Ethernet alarms and SDH alarms.
Correlation Between Ethernet Alarms and Mapping Module Alarms

The SDH layer carries Ethernet data services. Alarm trigger conditions on the SDH side,
however, may cause associated Ethernet alarms.
Table 2-12 lists the correlation between Ethernet alarms and SDH alarms.
Table 2-12 Correlation between Ethernet alarms and Mapping module alarms
Ethernet Alarm
SDH Alarm
Correlation
ALM_GFP_dLF
D
l Bit error ratio

(BER)-related
alarms:
BIP_EXC and
BIP_SD
Bit errors, losses of pointers, and AIS signals in a

path may cause BIP BER alarms, pointer-related
alarms, and TU_AIS alarms on the SDH side. At
the same time, the generic framing procedure
(GFP) state machine may fail to locate GFP frames
correctly.
l Pointer-related
alarms:
TU_LOP_VC
12 and
TU_LOP_VC
3
l Path-related
AIS alarms:
TU_AIS_VC1
2 and
TU_AIS_VC3
FCS_ERR
l BIP_EXC
l BIP_SD
Certain bit errors produced in a path may cause BIP

BER alarms on the SDH side and may cause an
error when the packet parameter check is
performed on the GFP module.
Correlation Between Ethernet Alarms

The Ethernet over SDH (EOS) operates on the upper layer of the SDH. Suppression also exists
among Ethernet alarms.
l
When specific trigger conditions are not met, relevant alarms cannot be reported.
When the trigger conditions of multiple alarms are detected, certain alarms need to be
masked to avoid misleading the alarm handling. If certain alarms are not masked, many
similar alarms are reported at the same time.
Table 2-13 lists the correlation among certain Ethernet alarms.

Issue 02 (2011-06-30)

2-13

System
Table 2-13 Correlation between Ethernet alarms

Ethernet Alarm
Relevant
Operation or
Alarm
Correlation
ETH_LOS
l The Ethernet
port is
disabled.
l If the Ethernet port is disabled, relevant alarms

cannot be reported.
l LSR_NO_FI
TED
If the port management module reports an

LSR_NO_FITED or LASER_MOD_ERR alarm,
no ETH_LOS alarm is reported.
LASER_MOD_
ERR
LSR_NO_FITE
D
LOOP_ALM
ETH_LOS
l LASER_MO
D_ERR
2-14
LASER_MOD_
ERR
LSR_NO_FITE
D

LSR_NO_FITED alarm, no LASER_MOD_ERR
alarm is reported.
LINK_ERR
ETH_LOS

ETH_LOS alarm, no LINK_ERR alarm is
reported.

Issue 02 (2011-06-30)

System
3 Generation and Detection of SDH Performance Events
Generation and Detection of SDH

Performance Events
About This Chapter

3.1 Bit Error
3.2 Pointer Justification
Issue 02 (2011-06-30)

3-1

System
3.1 Bit Error

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

Issue 02 (2011-06-30)

System
Error Detection and Report

Figure 3-1 shows the error detection relation and location.
Figure 3-1 Error detection relation and location
LPT
HPT
MST RST
RST MST HPT
LPT
B1
B2
B3
V5
As shown in Figure 3-1, the modules are defined as follows:

l
RST is regenerator section termination.
MST is multiplex section termination.
HPT is higher order path termination.
LPT is lower order path termination.
The B1, B2, B3 and V5 bit errors are respectively monitored between these terminations. Figure
3-1 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 3-1 lists the relevant terms.
Table 3-1 Bit error terms
Issue 02 (2011-06-30)
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.
3-3

System
Term
Description
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.
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
3-2 lists the alarms and performance events related to bit errors.
3-4

Issue 02 (2011-06-30)

System
Table 3-2 Alarms and performance events related to bit errors

Item
Performance Event
Alarm
If the bit
errors
exceed the
threshold at
the local
station, the
local station
reports the
relevant
event.
If the bit
errors exceed
the threshold
at the local
station, the
opposite
station
reports the
relevant
event.
If the bit errors

exceed the
threshold at the
local station, the
local station
reports the alarm.
If the bit errors

exceed the
threshold at the
local station, the
opposite station
reports the alarm.
Regener
ator
section
RSBBE
B1_SD/B1_EXC
Multiple
x section
MSBBE
MSFEBBE
B2_SD/B2_EXC
MS_REI
Higher
order
path
HPBBE
HPFEBBE
B3_SD/B3_EXC
HP_REI
Lower
order
path
LPBBE
LPFEBBE
BIP_SD/BIP_EXC
LP_REI
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.
Issue 02 (2011-06-30)

3-5

System
3.2 Pointer Justification

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 3-2, 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 3-2 Location and content of AU_PTR
9 rows
H1 YY H2 1* 1* H3 H3 H3
AU- 4 PTR
Y Byte: 1001SS11
1* Byte: 11111111
VC-4
1
(S Unspecified )
9
10
270columns
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 3-3.
3-6

Issue 02 (2011-06-30)

System
Table 3-3 Pointer justification state

State
Name

Frame
Rate
Relatio
n
10
11
12
Pointer
zero
justificat
ion
H3
H3
H3
Informat
ion
Informat
ion
Informati
on
Informat
ion =
containe
r
Positive
pointer
justificat
ion
H3
H3
H3
Stuffing
Stuffing
Stuffing
Informat
ion <
containe
r
Negative
pointer
justificat
ion
Informat
ion
Informati
on
Informat
ion
Informat
ion
Informat
ion
Informati
on
Informat
ion >
containe
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.
TU pointer justification occurs during demultiplexing.

If the system clock is not consistent with the received clock, TU pointer justification occurs
during demultiplexing.
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.
Issue 02 (2011-06-30)

3-7

System
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.
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.
3-8

Issue 02 (2011-06-30)

System
4 Detecting an Ethernet Performance Event
Detecting an Ethernet Performance Event

An Ethernet service performance event is used to count the packets transmitted and received
and the transmission quality of Ethernet services.
The data board counts the packets transmitted and received on each Ethernet port. In the case
of certain data boards (such as the RPR board), the packets can be transmitted and received on
the VCTRUNK port. The statistical items include the times of losing packets and the number of
bytes in bad packets transmitted and received.
The board monitors the performance. For most data boards, the chip supports data statistics. For
example, in the case of the 15-minute performance, the board detects a spare performance
register and clears the data in the register at the beginning of each period, and then counts the
performance events. At the end of a period, the statistics performance data is refreshed and then
stored in the register.
Data boards read the number of packets entering a port and report it to the platform. Then the
platform detects whether the statistical value exceeds the preset performance event threshold.
l
If the statistical value does not exceed the threshold within a period of time, the platform
directly reports the RMON statistical value to the NE.
If the statistical value exceeds the threshold within a period of time, the platform reports
an RMON threshold-crossing event to the NE.
Figure 4-1 shows the performance reporting flow.
Issue 02 (2011-06-30)

4-1
4 Detecting an Ethernet Performance Event

System
Figure 4-1 Performance reporting flow

Whether to
enable the performance
monitoring?
No
End
Yes
The board collects the
performance data and saves the
result in the performance register
The performance data is saved

to the performance register on
the system control board
Does the
current performance cross
the threshold?
Yes
The abnormal performance

event is reported to the NM
No
Whether to
enable the automatic
reporting?
Yes
The performance data is
reported to the NM and
saved in the database
4-2
No

End
Issue 02 (2011-06-30)

System
5 Alarm Reference
Alarm Reference
About This Chapter

This topic describes the alarms of the OptiX OSN 550. In this topic, the categories and the
troubleshooting are involved.
5.1 Alarm List
This topic lists the alarms supported by the OptiX OSN 550 in alphabetical order.
5.2 Alarm Clearing
This topic describes how to clear the alarms.
Issue 02 (2011-06-30)

5-1

System
5 Alarm Reference
5.1 Alarm List

This topic lists the alarms supported by the OptiX OSN 550 in alphabetical order.
Table 5-1 lists the alarms.
Table 5-1 Alarm list
5-2
Name
Description
Severity
A_LOC
Add to bus - loss of clock
Major
ALM_ALS
Automatic laser shutdown
Minor
APS_FAIL
APS protection switching failed
Major
ALM_GFP_dCSF
The loss of GFP client signal
Critical
ALM_GFP_dLFD
GFP frame is out of frame
Major
APS_INDI
APS protection switching indication
Major
APS_MANUAL_ST
OP
MSP protocol is manually stopped
Minor
AU_AIS
AU alarm indication
Major
AU_LOP
AU loss of pointer
Major
B1_EXC
Regenerator section (B1) excessive errors
Minor
B1_SD
Regenerator section (B1) signal degraded
Minor
B2_EXC
Multiplex section (B2) excessive errors
Major
B2_SD
Multiplex section (B2) signal degraded
Minor
B3_EXC
Higher order path (B3) excessive errors
Major
B3_SD
The higher order path B3 signals received over

the line are degraded
Minor
B3_EXC_VC3
B3 excessive bit errors in VC3
Major
B3_EXC_VC4
B3 bit errors in the VC4 path reach the preset

threshold
Major
B3_SD_VC3
B3 signals degrade in VC3
Minor
B3_SD_VC4
B3 bit errors in the VC4 path reach the set

deterioration threshold
Minor
BAT1TEMP_SENSO
R_FAIL
The temperature sensor of battery group 1 fails
Major
BAT2TEMP_SENSO
R_FAIL
The temperature sensor of battery group 2 fails
Major

Issue 02 (2011-06-30)

System
Issue 02 (2011-06-30)
5 Alarm Reference
Name
Description
Severity
BDTEMP_SENSOR_
FAIL
Board temperature sensor failure
Major
BD_STATUS
Board not in position alarm
Major
BIOS_STATUS
the BIOS status
Major
BIP_EXC
BIP excessive errors
Minor
BIP_SD
BIP signal degraded
Minor
BOOTROM_BAD
The BOOTROM data check failure
Major
BUS_ERR
The bus is abnormal
Critical
BUS_LOC
Bus dropping loss of clock
Major
CLK_NO_TRACE_
MODE
The clock changes to the non-tracing running

mode
Minor
DBMS_ERROR
Database error
Major
DBMS_PROTECT_
MODE
NE database in the protection mode
Critical
DCC_CHAN_LACK
DCC channel resource is insufficient
Major
DOWN_E1_AIS
Alarm indication for downstream 2 Mbit/s

signals
Minor
DOWN_T1_AIS
Alarm indication for downstream 1.5 Mbit/s

signals
Minor
E1_LOS
Loss of 2 Mbit/s line signals (E1 signals)
Minor
ENVHUM_SENSOR
_FAIL
Ambient temperature sensor failure
Major
ENVTEMP_SENSO
R_FAIL
Ambient temperature sensor failure
Major
ENVTEMP1_SENSO
R_FAIL
Ambient temperature sensor 1 failure
Major
ENVTEMP2_SENSO
R_FAIL
Ambient temperature sensor 2 failure
Major
ETH_CFM_LOC
Loss of continuity
Critical
ETH_CFM_MISME
RGE
Incorrect connection alarm
Critical
ETH_CFM_RDI
The receive end of the MEP at the opposite end

fails.
Minor
ETH_CFM_UNEXP
ERI
Incorrect frame alarm
Minor

5-3

System
5 Alarm Reference
5-4
Name
Description
Severity
ETH_LOS
Loss of Ethernet connection
Critical
ETHOAM_DISCOV
ER_FAIL
The point-to-point Ethernet OAM discovery

fails.
Minor
ETHOAM_RMT_CR
IT_FAULT
A critical fault occurs on the point-to-point

Ethernet OAM of the opposite end.
Minor
ETHOAM_RMT_LO
OP
The remote end of the point-to-point Ethernet

OAM function is loop backed.
Minor
ETHOAM_RMT_SD
The Ethernet performance of the point-to-point

Ethernet OAM function is degraded at the
remote end.
Minor
ETHOAM_SELF_L
OOP
The MAC port that runs the point-to-point OAM

protocol is in a loopback.
Major
EX_ETHOAM_CC_
LOS
The periodic connectivity check (CC) packets

are lost.
Critical
EX_ETHOAM_MPI
D_CNFLCT
The MEP IDs are in conflict.
Major
EXT_SYNC_LOS
Loss of the external clock source set on the clock

board
Minor
FAN_AGING
Alarm of the aged fan
Minor
FAN_FAIL
Fans of the NE fail
Major
FCS_ERR
FCS error
Critical
FLOW_OVER
Port inflow over the limit
Minor
HARD_BAD
Hardware failed
Critical
HP_CROSSTR
Higher order path performance over threshold
Minor
HP_LOM
Higher order path loss of multiframe
Major
HP_R_FIFO
FIFO overflow at the receive side of higher

order path
Minor
HP_RDI
Higher order path remote defect indication
Minor
HP_REI
Higher order path remote error indication
Warning
HP_SLM
Higher order path signal identification

mismatch
Minor
HP_T_FIFO
FIFO overflow at the transmit side of higher

order path
Minor
HP_TIM
Higher order path tracking identification

mismatch
Minor

Issue 02 (2011-06-30)

System
Issue 02 (2011-06-30)
5 Alarm Reference
Name
Description
Severity
HP_UNEQ
No loading error in the higher order path
Minor
HPAD_CROSSTR
The performance of the higher order path

adaptation crosses the threshold
Minor
HSC_UNAVAIL
Abnormal hot-backup state
Minor
IN_PWR_ABN
The input optical power of the line board laser

crosses the lower or upper threshold
Major
J0_MM
Trace identifier mismatch
Minor
K1_K2_M
K1 and K2 mismatch
Minor
K2_M
K2 mismatch
Minor
LAG_PORT_FAIL
A port in the LAG fails.
Minor
LASER_CLOSED
Laser closed
Major
LASER_MOD_ERR
Optical module wrongly installed
Major
LASER_MOD_ERR
_EX
The pluggable optical module on the line board

does not match the optical port of the line board
Major
LCAS_FOPR
Failure of protocol receive
Major
LCAS_FOPT
Failure of protocol transmit
Major
LCAS_PLCR
Partial loss of capacity receive
Minor
LCAS_PLCT
Partial loss of capacity transmit
Minor
LCAS_TLCR
Total loss of capacity receive
Major
LCAS_TLCT
Total loss of capacity transmit
Major
LCS_DAYS_OF_GR
ACE
A license file remains in the grace period
Major
LCS_EXPIRED
A license file expires
Critical
LCS_FILE_NOT_EX
IST
The license file is not installed on the NE
Critical
LINK_ERR
The data link is incorrect
Critical
LOOP_ALM
Loop alarm
Minor
LP_CROSSTR
Lower order path performance parameter over

threshold
Minor
LP_R_FIFO
FIFO overflow at the receive side of lower order

path
Minor
LP_RDI
Lower order path remote defect indication
Minor
LP_RDI_VC12
VC12 level path remote defect indication
Minor

5-5

System
5 Alarm Reference
5-6
Name
Description
Severity
LP_RDI_VC3
A remote defect in the lower order path of the

tributary board
Minor
LP_REI
Lower order path remote error indication
Minor
LP_REI_VC12
VC12 level path remote error indication
Minor
LP_REI_VC3
A remote bit error in the lower order path of the

tributary board
Minor
LP_RFI
Alarm in the lower order path
Minor
LP_SIZE_ERR
TU structure error
Minor
LP_SLM
Lower order path signal label mismatch
Minor
LP_SLM_VC12
VC12 level path signal label mismatch
Minor
LP_SLM_VC3
The mismatch of the lower order path signal

label received by the tributary board
Minor
LP_T_FIFO
FIFO overflow at the transmit side of lower

order path
Minor
LP_TIM
Lower order path tracking identification

mismatch
Minor
LP_TIM_VC12
VC12 level path tracking identification

mismatch
Minor
LP_TIM_VC3
The mismatch of the lower order path trace

identifier received by the tributary board
Minor
LP_UNEQ
Lower order path unequipped
Minor
LP_UNEQ_VC12
VC12 level path unequipped
Minor
LP_UNEQ_VC3
The lower order path received by the tributary

board on the cross-connection side is
unequipped
Minor
LPS_UNI_BI_M
The mismatch of the single-ended and dualended modes in a linear MSP
Minor
LPT_RFI
Lower order path remote failure indication
Critical
LSR_BCM_ALM
The bias current of the laser crosses the

threshold
Major
LSR_NO_FITED
Laser not installed
Critical
LSR_WILL_DIE
Laser life to be ended
Critical
LTI
Loss of synchronous source
Major
MS_AIS
Multiplex section alarm indication
Major

Issue 02 (2011-06-30)

System
Issue 02 (2011-06-30)
5 Alarm Reference
Name
Description
Severity
MS_CROSSTR
Multiplex section path performance over

threshold
Minor
MS_RDI
Multiplex section remote defect indication
Minor
MS_REI
Multiplex section remote error indication
Warning
MSAD_CROSSTR
Multiplex section path performance over

threshold
Minor
NESOFT_MM
The NE software versions on the working and

protection SCC boards are inconsistent
Major
NE_POWER_OVER
The power consumption of an NE is over the

threshold
Major
NESF_LOST
The NE software is lost
Critical
NESTATE_INSTAL
L
NE in install state
Critical
NO_BD_SOFT
The software of the SCC board or the software

of the service board is damaged or does not exist
Critical
NO_LSR_PARA_FI
LE
No laser parameter files are detected in the

EEPROM of the optical module after the board
is started
Major
ODC_BATTERY_C
URRENT_ABN
The current of the storage battery is abnormal
Major
ODC_BATTERY_P
WRDOWN
The storage battery fails to supply power for the

equipment
Major
ODC_DOOR_OPEN
The door of an outdoor cabinet is open
Critical
ODC_FAN_FAILED
The fan is faulty
Major
ODC_LOAD_PWRD
OWN
The secondary load is powered off
Major
ODC_MDL_ABN
Exceptions occur in the power module
Major
ODC_HUMI_ABN
The relative humidity in the cabinet

environment exceeds the specified threshold
Minor
ODC_POWER_FAIL
Exceptions occur in the AC input power voltage

or the DC output power voltage
Major
ODC_SMOKE_OVE
R
Smoke occurs in an outdoor cabinet
Critical
ODC_SURGE_POR
TECTION_FAIL
The surge protection function of the outdoor

cabinet fails to work properly
Critical
ODC_TEC_ALM
The TEC air conditioning module in the cabinet

fails to work properly
Major

5-7

System
5 Alarm Reference
5-8
Name
Description
Severity
ODC_TEMP_ABN
The ambient temperature of the cabinet or the

temperature of the storage battery is
inappropriate
Minor
ODC_WATER_ALM
Water enters the cabinet
Critical
OOL
The phase-locked loop is out of lock
Major
OUT_PWR_ABN
Output power abnormal
Critical
OUT1TEMP_SENSO
R_FAIL
The temperature sensor at the air outlet fails
Major
OUT2TEMP_SENSO
R_FAIL
External outlet temperature sensor failure
Major
P_AIS
The received signals on the PDH side of the E3/

T3 tributary board are all 1s
Major
P_LOC
The loss of the input signals on the PDH side of

the E3/T3 tributary board
Major
P_LOS
The loss of the signals received on the PDH side

of the E3/T3 tributary board
Major
PATCH_ACT_TIME
OUT
Patch package activation times out
Minor
PATCH_DEACT_TI
MEOUT
Patch package deactivation timeout
Minor
PATCH_ERR
The patch file is detected incorrect when the NE

loads the path after a reset
Major
PATCH_NOT_CONFIRM
The activated patch times out after the NE loads

the patch
Major
PATCH_PKGERR
Patch package file is abnormal
Minor
PATCHFILE_NOTE
XIST
The patch file does not exist when the NE loads

the path after a reset
Major
POWER_ABNORM
AL
NE power is abnormal.
Major
POWER_FAIL
The power supply failure on an NE
Major
R_APS
Failure of the K1/K2 byte
Minor
R_LOC
Receive loss of clock
Critical
R_LOF
Receive loss of frame
Critical
R_LOS
Receive loss of signal
Critical

Issue 02 (2011-06-30)

System
Issue 02 (2011-06-30)
5 Alarm Reference
Name
Description
Severity
R_OOF
The frame header cannot be identified for five

consecutive frames in the received signals of the
line board
Critical
R_S_ERR
The received signal is incorrect
Critical
RELAY_ALARM_C
RITICAL
An alarm of critical alarm inputs
Critical
RELAY_ALARM_I
GNORE
An alarm of warning alarm inputs
Warning
RELAY_ALARM_M
AJOR
An alarm of major alarm inputs
Major
RELAY_ALARM_M
INOR
An alarm of minor alarm inputs
Minor
RS_CROSSTR
Regenerator section performance over

threshold
Minor
RTC_FAIL
SCC real time clock failure
Major
S1_SYN_CHANGE
Reference source change in S1 mode
Major
SECU_ALM
SCC reports an illegal login
Major
SLAVE_WORKING
The protection board is working
Warning
SWDL_ACTIVATE
D_TIMEOUT
The NE does not perform the commit operation

in a certain time after the board is activated
Critical
SWDL_AUTOMAT
CH_INH
The automatic match function is disabled
Minor
SWDL_COMMIT_F
AIL
The commit operation fails for some boards
Minor
SWDL_INPROCESS
The NE is loading the software package
Warning
SWDL_PKG_NOBD
SOFT
The files of some boards are not in the software

package for loading
Minor
SWDL_ROLLBACK
_FAIL
Some board rollback fails when the NE

performs rollback
Minor
SYN_BAD
The current synchronization clock source of the

clock board is degraded
Minor
SYNC_C_LOS
Synchronous source level loss
Warning
SYNC_FAIL
The batch backup of the databases of the active

and standby SCC boards fails
Minor
T_ALOS
E1 interface loss of analog signal
Major

5-9

System
5 Alarm Reference
5-10
Name
Description
Severity
T_FIFO_E
The transmission FIFO on the PDH side of the

E3/T3 tributary board overflows
Minor
T_LOC
Transmit loss of clock
Major
T_LOS
Transmit loss of signal
Major
T_LOSEX
A board has detected the loss of signal in the

service bus of the backplane
Major
TEM_HA
The temperature of the laser exceeds the upper

threshold.
Major
TEM_LA
The temperature of the laser exceeds the lower

threshold.
Major
TEMP_ALARM
The temperature of the laser crosses the

threshold
Minor
TF
Laser transmission failed
Critical
THUNDERALM
The surge protection failure
Minor
TR_LOC
The clock of the cross-connect board is faulty
Major
TU_AIS
TU alarm indication
Major
TU_AIS_VC3
the lower order path signals received at the

cross-connect unit side by the tributary board
are all "1"s
Major
TU_AIS_VC12
TU of VC12 level alarm indication
Major
TU_LOP
TU loss of pointer
Major
TU_LOP_VC3
TU pointer in the signals received by the

tributary board on the cross-connection side is
lost
Major
TU_LOP_VC12
TU of VC12 level loss of pointer
Major
UP_E1_AIS
E1 signal alarm indication
Minor
UP_T1AIS
T1 signal alarm indication
Minor
VCAT_LOA
Virtual concatenation loss of alignment
Critical
VCAT_LOM_VC3
Loss of multiframe of the VC3 virtual

concatenation
Major
VCAT_LOM_VC4

concatenation
Major
VCAT_LOM_VC12

concatenation
Major
VCAT_SQM_VC3
SQ mismatch of the VC3 virtual concatenation
Major

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Description
Severity
VCAT_SQM_VC4
Major
VCAT_SQM_VC12
Major
W_R_FAIL
Reading and writing the chip register fail
Major
WRG_BD_TYPE
Wrong inserted board type
Major
5.2 Alarm Clearing

This topic describes how to clear the alarms.
WARNING
l The CXL board on the OptiX OSN 550 integrates the system control, cross-connect, and
timing units.
l Some operations, such as replacing an optical module, performing a cold reset on a board,
or replacing a board, may result in service interruption. If services that travel a board are not
configured with the protection switching function, exercise caution when performing the
preceding operations.
l After replacing the chassis, make sure the optical interface level and transmission distance
of the line unit is consistent with the values of the old board and the version of the board
software is not earlier than the replaced version.
l Replacing a chassis will result in service interruption on the NE, and therefore is a risky
operation.
l After replacing a chassis, ensure that the level and transmission distance of the optical port
on the optical module of the line unit are the same as those of the original board. In addition,
after replacement, the board software of the NE must be of the previous version or a later
version. For information about the NE software version, see the Version Description and
Upgrade Guide of the NE software.
NOTE
l This document lists the alarm parameters that are displayed on the NMS. When you browse an alarm
on the NMS, select this alarm to display its parameters in Alarm Details. The alarm parameters are in
format of "alarm parameter (hexadecimal): parameter 1 parameter 2 ... parameter n", for example,
"alarm parameters (hexadecimal): 0x01 0x08 ...".
l If failing to clear the alarms by using these methods described in this document, contact Huawei
engineer for solution.
5.2.1 A_LOC
5.2.2 ALM_ALS
5.2.3 APS_FAIL
5.2.4 ALM_GFP_dCSF
5.2.5 ALM_GFP_dLFD
Issue 02 (2011-06-30)

5-11

System
5 Alarm Reference
5.2.6 APS_INDI
5.2.7 APS_MANUAL_STOP
5.2.8 AU_AIS
5.2.9 AU_LOP
5.2.10 B1_EXC
5.2.11 B1_SD
5.2.12 B2_EXC
5.2.13 B2_SD
5.2.14 B3_EXC
5.2.15 B3_EXC_VC3
5.2.16 B3_EXC_VC4
5.2.17 B3_SD
5.2.18 B3_SD_VC3
5.2.19 B3_SD_VC4
5.2.20 BAT1TEMP_SENSOR_FAIL
5.2.22 BDTEMP_SENSOR_FAIL
5.2.23 BD_STATUS
5.2.24 BIOS_STATUS
5.2.25 BIP_EXC
5.2.26 BIP_SD
5.2.27 BOOTROM_BAD
5.2.28 BUS_ERR
5.2.29 BUS_LOC
5.2.30 CFCARD_FAILED
5.2.31 CFCARD_FULL
5.2.32 CFCARD_OFFLINE
5.2.33 CFCARD_W_R_DISABLED
5.2.34 CLK_NO_TRACE_MODE
5.2.35 DBMS_ERROR
5.2.36 DBMS_PROTECT_MODE
5.2.37 DCC_CHAN_LACK
5.2.38 DOWN_E1_AIS
5-12

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.39 DOWN_T1_AIS
5.2.40 E1_LOS
5.2.41 E1_LOC
5.2.42 ENVHUM_SENSOR_FAIL
5.2.43 ENVTEMP_SENSOR_FAIL
5.2.44 ENVTEMP1_SENSOR_FAIL
5.2.46 ETH_CFM_LOC
5.2.47 ETH_CFM_MISMERGE
5.2.48 ETH_CFM_RDI
5.2.49 ETH_CFM_UNEXPERI
5.2.50 ETH_LOS
5.2.51 ETHOAM_DISCOVER_FAIL
5.2.52 ETHOAM_RMT_CRIT_FAULT
5.2.53 ETHOAM_RMT_LOOP
5.2.54 ETHOAM_RMT_SD
5.2.55 ETHOAM_SELF_LOOP
5.2.56 EX_ETHOAM_CC_LOS
5.2.57 EX_ETHOAM_MPID_CNFLCT
5.2.58 EXT_SYNC_LOS
5.2.59 FAN_AGING
5.2.60 FAN_FAIL
5.2.61 FCS_ERR
5.2.62 FLOW_OVER
5.2.63 HARD_BAD
5.2.64 HP_CROSSTR
5.2.65 HP_LOM
5.2.66 HP_R_FIFO
5.2.67 HP_RDI
5.2.68 HP_REI
5.2.69 HP_SLM
5.2.70 HP_T_FIFO
5.2.71 HP_TIM
Issue 02 (2011-06-30)

5-13

System
5 Alarm Reference
5.2.72 HP_UNEQ
5.2.73 HPAD_CROSSTR
5.2.74 HSC_UNAVAIL
5.2.75 IN_PWR_ABN
5.2.76 INTEMP_SENSOR_FAIL
5.2.77 J0_MM
5.2.78 K1_K2_M
5.2.79 K2_M
5.2.80 LAG_PORT_FAIL
5.2.81 LASER_CLOSED
5.2.82 LASER_MOD_ERR
5.2.83 LASER_MOD_ERR_EX
5.2.84 LCAS_FOPR
5.2.85 LCAS_FOPT
5.2.86 LCAS_PLCR
5.2.87 LCAS_PLCT
5.2.88 LCAS_TLCR
5.2.89 LCAS_TLCT
5.2.90 LCS_DAYS_OF_GRACE
5.2.91 LCS_EXPIRED
5.2.92 LCS_FILE_NOT_EXIST
5.2.93 LINK_ERR
5.2.94 LOOP_ALM
5.2.95 LP_CROSSTR
5.2.96 LP_R_FIFO
5.2.97 LP_RDI
5.2.98 LP_RDI_VC12
5.2.99 LP_RDI_VC3
5.2.100 LP_REI
5.2.101 LP_REI_VC12
5.2.102 LP_REI_VC3
5.2.103 LP_RFI
5.2.104 LP_SIZE_ERR
5-14

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.105 LP_SLM
5.2.106 LP_SLM_VC12
5.2.107 LP_SLM_VC3
5.2.108 LP_T_FIFO
5.2.109 LP_TIM
5.2.110 LP_TIM_VC12
5.2.111 LP_TIM_VC3
5.2.112 LP_UNEQ
5.2.113 LP_UNEQ_VC12
5.2.114 LP_UNEQ_VC3
5.2.115 LPS_UNI_BI_M
5.2.116 LPT_RFI
5.2.117 LSR_BCM_ALM
5.2.118 LSR_NO_FITED
5.2.119 LSR_WILL_DIE
5.2.120 LTI
5.2.121 MS_AIS
5.2.122 MS_CROSSTR
5.2.123 MS_RDI
5.2.124 MS_REI
5.2.125 MSAD_CROSSTR
5.2.126 NESOFT_MM
5.2.127 NE_POWER_OVER
5.2.128 NESF_LOST
5.2.129 NESTATE_INSTALL
5.2.130 NO_BD_SOFT
5.2.131 NO_LSR_PARA_FILE
5.2.132 ODC_BATTERY_CURRENT_ABN
5.2.133 ODC_BATTERY_PWRDOWN
5.2.134 ODC_DOOR_OPEN
5.2.135 ODC_FAN_FAILED
5.2.136 ODC_HUMI_ABN
5.2.137 ODC_LOAD_PWRDOWN
Issue 02 (2011-06-30)

5-15

System
5 Alarm Reference
5.2.138 ODC_MDL_ABN
5.2.139 ODC_POWER_FAIL
5.2.140 ODC_SMOKE_OVER
5.2.141 ODC_SURGE_PORTECTION_FAIL
5.2.142 ODC_TEC_ALM
5.2.143 ODC_TEMP_ABN
5.2.144 ODC_WATER_ALM
5.2.145 OOL
5.2.146 OUT_PWR_ABN
5.2.147 OUT1TEMP_SENSOR_FAIL
5.2.149 P_AIS
5.2.150 P_LOC
5.2.151 P_LOS
5.2.152 PATCH_ACT_TIMEOUT
5.2.153 PATCH_DEACT_TIMEOUT
5.2.154 PATCH_ERR
5.2.155 PATCH_NOT_CONFIRM
5.2.156 PATCH_PKGERR
5.2.157 PATCHFILE_NOTEXIST
5.2.158 POWER_ABNORMAL
5.2.159 POWER_FAIL
5.2.160 PWR_TEMP_OVERTH
5.2.161 POWER_MODULE_OFFLINE
5.2.162 R_APS
5.2.163 R_LOC
5.2.164 R_LOF
5.2.165 R_LOS
5.2.166 R_OOF
5.2.167 R_S_ERR
5.2.168 RELAY_ALARM_CRITICAL
5.2.169 RELAY_ALARM_IGNORE
5.2.170 RELAY_ALARM_MAJOR
5-16

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.171 RELAY_ALARM_MINOR
5.2.172 RS_CROSSTR
5.2.173 RTC_FAIL
5.2.174 S1_SYN_CHANGE
5.2.175 SECU_ALM
5.2.176 SLAVE_WORKING
5.2.177 SWDL_ACTIVATED_TIMEOUT
5.2.178 SWDL_AUTOMATCH_INH
5.2.179 SWDL_CHGMNG_NOMATCH
5.2.180 SWDL_COMMIT_FAIL
5.2.181 SWDL_INPROCESS
5.2.182 SWDL_NEPKGCHECK
5.2.183 SWDL_PKGVER_MM
5.2.184 SWDL_PKG_NOBDSOFT
5.2.185 SWDL_ROLLBACK_FAIL
5.2.186 SYN_BAD
5.2.187 SYNC_C_LOS
5.2.188 SYNC_FAIL
5.2.189 T_ALOS
5.2.190 T_FIFO_E
5.2.191 T_LOC
5.2.192 T_LOS
5.2.193 T_LOSEX
5.2.194 TEM_HA
5.2.195 TEM_LA
5.2.196 TEMP_ALARM
5.2.197 TF
5.2.198 THUNDERALM
5.2.199 TR_LOC
5.2.200 TU_AIS
5.2.201 TU_AIS_VC12
5.2.202 TU_AIS_VC3
5.2.203 TU_LOP
Issue 02 (2011-06-30)

5-17

System
5 Alarm Reference
5.2.204 TU_LOP_VC12
5.2.205 TU_LOP_VC3
5.2.206 UP_E1_AIS
5.2.207 UP_T1AIS
5.2.208 VCAT_LOA
5.2.209 VCAT_LOM_VC12
5.2.212 VCAT_SQM_VC12
5.2.215 W_R_FAIL
5.2.216 WRG_BD_TYPE
5.2.1 A_LOC
Description
The A_LOC is an alarm indicating that the upstream BUS clock loses at the electrical interface
of the tributary board.
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.
5-18
Name
Meaning
Parameter 1
The value is always 0x01, and this parameter is meaningless.
Parameter 2, Parameter 3
Indicate the path number.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Impact on the System

When the A_LOC alarm is reported, the clock of the tributary board is lost. 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 transmit signals of the interconnected PDH equipment is lost.
The receiving part of the board is faulty.
Procedure
Step 1 Check the configuration of the interconnected PDH equipment.
Step 2 After rectifying the fault of the interconnected PDH equipment, view alarms on the U2000 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 3 The tributary board is faulty, so you need to replace the faulty board.
----End
Related Information
None.
5.2.2 ALM_ALS
Description
The ALM_ALS(Auto Laser Shutdown) indicates that the line board laser is in the automatic
shutdown state.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
Issue 02 (2011-06-30)

5-19

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1
Indicates the optical interface number.

The alarm indicates that the R_LOS exists on the line board optical interface. To avoid the
damage of the laser, the ALS protection state is enabled. After the R_LOS ends, the ALS state
exits automatically. The alarm does not affect the system.
Possible Causes
The possible cause of the ALM_ALS alarm is as follows:
l
The ALS function of the optical port is enabled, and the R_LOS alarm exists on the optical
port, as a result, the laser enters the ALS state and reports the ALM_ALS alarm.
Procedure
Step 1 Check the service line. Eliminate the R_LOS alarm or disable the ALS function of the optical
port.
Step 2 View alarms on the U2000 to check whether the ALM_ALS alarm is cleared.
If...
Then...
If this alarm is cleared
The fault is rectified.
If this alarm persists
Contact Huawei technical support engineers

to handle the alarm.
----End
Related Information
R_LOS
5.2.3 APS_FAIL
Description
The APS_FAIL alarm indicates that the automatic MSP switching fails.
5-20

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the type of the protection group. The options are as

follows:
l Linear MSP: 0x01
l MSP ring protection: 0x02
Parameter 2
Indicates the protection group ID.
Parameter 3, Parameter 4 The value is always 0xff, and this parameter is unused.

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 switching fails.
The MSP node configuration is wrong. For example, the new/old protocol configured on
the node is inconsistent with that configured on the ring.
The MSP node information is lost.
Procedure
Step 1 Check whether the current MSP parameters of the NEs on the ring are correct. If not, configure
them to correct.
Step 2 View alarms on the U2000 to check whether the APS_FAIL alarm is cleared.
Issue 02 (2011-06-30)
If...
Then...
The fault is removed. End the alarm handling.

5-21

System
5 Alarm Reference
If...
Then...
Step 3 Check whether the pass-through and the auto-report of the K byte of each NE are normal. If the
line unit is faulty, replace the faulty board.
----End
Related Information
None
5.2.4 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating the GFP loss of client signal. When a GFP
management frame with a correct tHEC (type header error control) and with PTI being 100 and
UPI being 0000 0001, this alarm is generated; when such a GFP management frame is not
received or a correct user data frame is received within N x 1000 ms, the generated
ALM_GFP_dCSF alarm is cleared.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
The ID of the logical port, and the value is always 0x01.
Parameter 2, parameter 3
Indicates the path number.

If the client signal is lost, the downstream services of the VCTRUNK are unavailable.
5-22

Issue 02 (2011-06-30)

System
5 Alarm Reference
Possible Causes
The possible causes of the ALM_GFP_dCSF alarm are as follows:
l
Services are incorrectly configured.
The interconnected equipment is faulty.
Procedure
Step 1 Check whether the services at the opposite station and the local station are correctly configured.
If not, modify the incorrect configuration and issue it again.
Step 2 Check whether the service transmission of the interconnected SDH equipment is normal and
whether the equipment is faulty. If the opposite station uses the optical network equipment of
Huawei, check whether the Ethernet port of the service reports the ETH_LOS alarm. If the alarm
occurs, see the processing procedure in ETH_LOS.
----End
Related Information
None.
5.2.5 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating the GFP frame signal is lost. This alarm is
generated when the GFP state machine leaves the SYNC state, and the generated
ALM_GFP_dLFD alarm is cleared when the GFP state machine enters the SYNC state again.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
The ID of the logical port, and the value is always 0x01.
Issue 02 (2011-06-30)

5-23

System
5 Alarm Reference

The fixed frame is out of frame. The downstream service of the VCTRUNK is unavailable.
Possible Causes
The possible causes of the ALM_GFP_dLFD alarm are as follows:
l
Services are incorrectly configured.
The performance of optical paths transmitting services is degraded.
The interconnected equipment is faulty.
Procedure
Step 2 Check whether a B3_EXC, B3_SD, or IN_PWR_ABN alarm is reported on the NMS. If yes,
handle them with reference to 5.2.14 B3_EXC, 5.2.17 B3_SD, and 5.2.75 IN_PWR_ABN.
Step 3 View alarms of the NE, and check whether there is the TU_AIS, TU_LOP, LP_TIM or
LP_UNEQ alarm in the corresponding path of the data board at local station. If the alarms occur,
see TU_AIS, TU_LOP, LP_TIM, or LP_UNEQ for handling procedure.
Step 4 Check whether the service transmission of the interconnected SDH equipment is normal and
whether the equipment is faulty.
----End
Related Information
None.
5.2.6 APS_INDI
Description
The APS_INDI is an alarm indicating that the automatic MSP switching occurs.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
5-24

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1

follows:
l Linear MSP: 0x01
Parameter 2

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.
The external switching command is issued.
The attributes of the MSP group are incorrectly configured.
Procedure
Step 1 Check whether the alarms that cause the MSP switching are present on the local and opposite
NEs. If yes, handle these alarms first.
If...
Then...
There is the R_LOS, R_LOF, MS_AIS, or

B2_EXC alarm
Refer to the corresponding section in this

document to clear the alarm.
There is the B2_SD alarm
Disable the SD switching if it is enabled, or

refer to the corresponding section in this
document to clear the B2_SD alarm.
If the preceding alarms do not exist
Step 2 Check whether the external switching command for the protection group is issued. If yes, cancel
the issued external switching command.
Step 3 View alarms on the U2000 to check whether the APS_INDI alarm is cleared.
Issue 02 (2011-06-30)

5-25

System
5 Alarm Reference
If...
Then...
Step 4 Check whether the NE configuration is incorrect. Issue the MSP configuration again.
Step 5 View alarms on the U2000 to check whether the APS_INDI alarm is cleared.
If...
Then...
Step 6 If the service configuration is correct and the alarm persists, replace the SCC board.
----End
Related Information
R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD
5.2.7 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the protocol controller of the multiplex
section auto protection switching is stopped.
Attribute
Alarm Severity
Alarm Type
Minor
Processing failed
Parameters
table.
5-26

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1

follows:
l Linear MSP: 0x01
Parameter 2

The alarm indicates that the automatic protection switching protocol controller of the protection
group is stopped by the manual-delivered command. The protected services will lose the
protection from the multiplex section automatic protection switching.
Possible Causes
The possible cause of the APS_MANUAL_STOP alarm is as follows:
l
Manually issue the command of ending protection group protocol controller.
Procedure
Step 1 Issue commands from the U2000 or command lines to restart the protocol controller of the
protection group.
----End
Related Information
None
5.2.8 AU_AIS
Description
The AU_AIS is an alarm indicating that the AU pointer in the signal received by the line is all
"1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Issue 02 (2011-06-30)

5-27

System
5 Alarm Reference
Parameters
table.
Name
Meaning
parameter 3
Indicates the AU-4 path number.

When the AU_AIS alarm occurs, it indicates that the AU4 services are unavailable.
The system will send an HP_RDI alarm to the opposite end. If SNCP is configured, the SF
switching occurs.
Possible Causes
The possible causes of the AU_AIS alarm are as follows:
l
The higher-level alarms such as MS_AIS, R_LOS, and R_LOF cause the AU_AIS alarm
in the corresponding VC-4 channel.
The services are incorrectly configured.
The opposite station sends the AU_AIS alarm.
The transmit part at the opposite station is faulty.
The receive part of the local station is faulty.
Procedure
Step 1 Check whether section-level alarms are present on the line board of the upstream station. If VC-4
higher order pass-through services are configured on the line board, the AU_AIS alarm of the
corresponding AU4 path will be triggered.
If...
Then...
There is the R_LOS, R_LOF, R_LOC, or

MS_AIS alarm on the line board of the
upstream station

There is no such alarms as mentioned
Step 2 Check whether the line board at the opposite station is configured for the AU_AIS alarm inserted
to the transmit end.
5-28

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The transmit end of the line board at the

opposite station is inserted with the AU_AIS
alarm
Cancel the inserted AU_AIS alarm.

opposite station is not inserted with the
AU_AIS alarm
Step 3 Check the service configuration at the local and opposite ends and issue the configurations again.
Step 4 View alarms on the U2000 to check whether the AU_AIS alarm is cleared.
If...
Then...
Step 5 Check whether the transmitting part of the line board on the opposite station is faulty.
If...
Then...
If the line board of the opposite station is

faulty
Perform a reset on the board or replace the

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

opposite station is normal
Step 6 Check the line board of the local station. Perform a reset to the board or replace the board. Then
check whether the alarm is cleared.
----End
Related Information
R_LOS, R_LOF, R_LOC, MS_AIS
5.2.9 AU_LOP
Description
The AU_LOP is an alarm indicating loss of the AU pointer in the signal received by the line
board.
Issue 02 (2011-06-30)

5-29

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the the AU-4 path number.

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

alarm exist...

There are no such alarms as B1_EXC,

B1_SD, B2_EXC and B2_SD

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 2 Check whether the service configuration is correct on the local and opposite stations. If not,
configure them to correct.
Step 3 After verifying that the service configuration is correct, view alarms on the U2000 to check
whether the AU_LOP alarm is cleared.
If...
Then...
Step 4 Check whether the clock board of the opposite end is normal, whether the cross-connect unit
detects the clock. If the clock board of the opposite end or cross-connect board is faulty, replace
the SCC board of the opposite NE.
CAUTION
The SCC, cross-connect, timing units of the OptiX OSN 550 are integrated in the CXL board.
When a unit fails, replace the OptiX OSN 550 chassis.
Step 5 After replacing the SCC board of the opposite end, view alarms on the U2000 to check whether
the AU_LOP alarm is cleared.
If...
Then...
Step 6 Perform the loopback for the stations at both ends of the line. Locate and replace the faulty line
board.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, and B2_SD
5.2.10 B1_EXC
Description
The B1_EXC is an alarm indicating that the regenerator section B1 bit errors in the signals
received by the line crosses the threshold.
Issue 02 (2011-06-30)

5-31

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Service quality alarm
Parameters
table.
Name
Meaning
Parameter 1

When the B1_EXC occurs, it indicates that the number of the regenerator section B1 bit errors
in the signals received by the optical interface crosses the threshold. The services on the optical
interface are unavailable.
Possible Causes
The possible causes of the B1_EXC alarm are as follows:
l
The performance threshold of B1 bit errors in the regenerator section is set to a large or
small value.
The fiber connector is dirty or incorrectly connected, resulting in serious attenuation of

received signals.
The transmit line unit at the opposite station is faulty.
The clock source is incorrectly set, or the performance of the timing and cross-connect unit
deteriorates.
The receive line unit at the local station is faulty.
Procedure
Step 1 On the NMS, check whether the performance threshold of B1 bit errors in the regeneration
section is set to a large or small value.
5-32
If...
Then...
The performance threshold is set to a large or

small value
Set the performance threshold of B1 bit errors

in the regeneration section to the default
value. Check whether the alarm is cleared. If
the alarm persists, go to the next step.

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The performance threshold is set to a proper

value.
Go to the next step.
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 dirty, and the transmit
optical power of the opposite line board is
normal. Check whether the alarm is cleared.
If the alarm persists, go to the next step.
The optical power is normal
Step 3 Check whether the clock source at the local station is correctly set, and whether the performance
of the timing and cross-connect unit deteriorates.
If...
Then...
The clock source is incorrectly set
Change or reset the synchronous clock

source. Check whether the alarm is cleared.
The performance of the timing and crossconnect unit deteriorates

The clock source is correctly set, and the

timing and cross-connect unit functions
properly
Step 4 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.
----End
Related Information
None.
5.2.11 B1_SD
Description
The B1_SD is an alarm indicating that the B1 signals received by the line are degraded.
Issue 02 (2011-06-30)

5-33

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1

When the B1_SD alarm occurs, it indicates that the regenerator section B1 bit errors in the signals
received by 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:
l
The performance threshold of B1 bit errors in the regenerator section is set to a large or
small value.

received signals.
deteriorates.
Procedure
Step 1 On the NMS, check whether the performance threshold of B1 bit errors in the regeneration
section is set to a large or small value.
5-34
If...
Then...

small value

in the regeneration section to the default
value. Check whether the alarm is cleared. If

value.

Issue 02 (2011-06-30)

System
5 Alarm Reference

If...
Then...

If...
Then...



properly
----End
Related Information
None
5.2.12 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.
Issue 02 (2011-06-30)

5-35

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Parameters
table.
Name
Meaning
Parameter 1

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 are unavailable. If the MSP is
configured, this alarm will trigger the SF switching.
When the B2_EXC alarm occurs, the system 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 performance threshold of B2 bit errors in the multiplex section is set to a large or small
value.

received signals.
deteriorates.
Procedure
Step 1 On the NMS, check whether the performance threshold of B2 bit errors in the multiplex section
is set to a large or small value.
5-36

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...

small value

in the multiplex section to the default value.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.

value.

If...
Then...

If...
Then...



properly
----End
Related Information
None.
5.2.13 B2_SD
Issue 02 (2011-06-30)

5-37

System
5 Alarm Reference
Description
The B2_SD is an alarm indicating that the multiplex section B2 signals received by the line are
degraded.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1

If the alarm occurs, it indicates that serious multiplex section bit errors exist. The bit errors will
affect the service of the optical interface. If multiplex section auto protection switching is
configured and SD switching function is enabled, this alarm will trigger the B2_SD switching.
When the B2_SD alarm occurs, the system 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 performance threshold of B2 bit errors in the multiplex section is set to a large or small
value.

received signals.
deteriorates.
Procedure
Step 1 On the NMS, check whether the performance threshold of B2 bit errors in the multiplex section
is set to a large or small value.
5-38

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...

small value

in the multiplex section to the default value.

value.

If...
Then...

If...
Then...



properly
----End
Related Information
None.
5.2.14 B3_EXC
Issue 02 (2011-06-30)

5-39

System
5 Alarm Reference
Description
The B3_EXC is an alarm indicating that the B3 bit errors in the signals received by the line
crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Parameters
table.
Name
Meaning
Parameter 1

If the alarm occurs, it indicates that the number of bit errors (high order B3 bit errors of line
boards) 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 B3_EXC alarm occurs, the system will send the HP_REI alarm to the opposite end.
Possible Causes
l
The performance threshold of B3 bit errors is set to a large or small value.

received signals.
deteriorates.
Procedure
Step 1 On the NMS, check whether the performance threshold of B3 bit errors is set to a large or small
value.
5-40

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...

small value

to the default value. Check whether the alarm
is cleared. If the alarm persists, go to the next
step.

value.

If...
Then...

If...
Then...



properly
----End
Related Information
None.
5.2.15 B3_EXC_VC3
Issue 02 (2011-06-30)

5-41

System
5 Alarm Reference
Description
The B3_EXC_VC3 is an alarm indicating the B3 excessive bit errors in VC-3
Attribute
Alarm Severity
Alarm Type
Major
Parameters
table.
Name
Meaning
Parameter 1
Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-3 path number.

If the alarm occurs, it indicates that the number of bit errors (lower order B3 bit errors) is
excessive and crosses the performance threshold.
Possible Causes
The possible causes of the B3_EXC_VC3 alarm are as follows:
l
There are B1 or B2 bit errors.
The received signals are heavily attenuated.
The fiber head is dirty or the connector is incorrect.
Procedure
Step 1 Check whether B1 or B2 bit errors are present on the line board of the access service.
5-42
If...
Then...

alarm exist...



Issue 02 (2011-06-30)

System
5 Alarm Reference

If...
Then...

normal.
Step 3 Check whether the working temperature is over high or over low.
If...
Then...
The working temperature is over high or over

low
In the case of over high working temperature,

add the cooling device to the NE. In the case
f the over low working temperature, add the
heating device to the NE.
The working temperature is normal
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 wrong, modify
or re-issue the configuration.
Step 5 View alarms on the U2000 to check whether the B3_EXC_VC3 alarm is cleared.
If...
Then...
Step 6 Perform the loopback for the stations at two ends of the line. Locate the faulty board.
If...
Then...
The B3 bit error performance event is

reported on the opposite board
The transmit end of the board at the opposite

station is faulty. Replace the faulty board.

reported on the local board
The receive end of the board at the local

----End
Related Information
Issue 02 (2011-06-30)

5-43

System
5 Alarm Reference
5.2.16 B3_EXC_VC4
Description
The B3_EXC_VC4 is an alarm indicating that B3 bit errors in the VC-4 path reach the preset
threshold. When the system detects that the bit errors in the VC-4 path reach the preset threshold,
the system reports the B3_EXC_VC4 alarm.
Attribute
Alarm Severity
Alarm Type
Major
Parameters
table.
Name
Meaning
Parameter 1
Parameter 2, parameter 3 Indicates the VC-4 path number.

If the alarm occurs, it indicates that bit errors occur in the path-level services.
Possible Causes
The possible causes of the B3_EXC_VC4 alarm are the same as the possible causes of the
B3_EXC alarm.
Procedure
Step 1 Refer to the suggestions that are provided for handling the B3_EXC alarm.
----End
Related Information
None
5.2.17 B3_SD
5-44

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The B3_SD is an alarm indicating that the higher order path B3 signals received over the line
are degraded.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1

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 B3_SD switching function
is enabled, this alarm will trigger the B3_SD switching.
When the alarm occurs, the system will send the HP_REI alarm to the opposite end.
Possible Causes
l
The performance threshold of B3 bit errors is set to a large or small value.

received signals.
deteriorates.
Procedure
Step 1 On the NMS, check whether the performance threshold of B3 bit errors is set to a large or small
value.
Issue 02 (2011-06-30)

5-45

System
5 Alarm Reference
If...
Then...

small value

to the default value. Check whether the alarm
step.

value.

If...
Then...

If...
Then...



properly
----End
Related Information
None.
5.2.18 B3_SD_VC3
5-46

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The B3_SD_VC3 is an alarm indicating that B3 signals degrade in VC3
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1

If the alarm occurs, it indicates that serious lower order path bit errors exist. The bit errors will
affect the service of the path.
When the alarm occurs, the system will send the HP_REI alarm to the opposite end.
Possible Causes
The possible causes of the B3_SD_VC3 alarm are as follows:
l
The received signals are heavily attenuated.
The fiber head is dirty or the connector is incorrect.
Procedure
Step 1 Check whether B1 or B2 bit errors are present on the line board of access services.
Issue 02 (2011-06-30)
If...
Then...

alarm exists


5-47

System
5 Alarm Reference
If...
Then...


If...
Then...

normal.
Step 3 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.
Step 4 View alarms on the U2000 to check whether the B3_SD_VC3 alarm is cleared.
If...
Then...
Step 5 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 wrong, modify
or re-issue the configuration.
Step 6 View alarms on the U2000 to check whether the B3_SD_VC3 alarm is cleared.
If...
Then...
If...
Then...




----End
5-48

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
5.2.19 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that B3 bit errors in the VC-4 path reach the set
deterioration threshold. When the system detects that the bit errors in the VC-4 path reach the
set deterioration threshold, the system reports the B3_SD_VC4 alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1

If the alarm occurs, it indicates that bit errors occur in the path-level services.
Possible Causes
The possible causes of the B3_SD_VC4 alarm are the same as the possible causes of the B3_SD
alarm.
Procedure
Step 1 Refer to the suggestions that are provided for handling the B3_SD alarm.
----End
Related Information
None
Issue 02 (2011-06-30)

5-49

System
5 Alarm Reference
Description
The BAT1TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of battery
group 1 fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When this alarm is reported, the equipment cannot collect the temperature data of PMU battery
group 1.
Possible Causes
The possible causes of the BAT1TEMP_SENSOR_FAIL alarm are as follows:
l
The temperature sensor is not installed.
The temperature sensor is not correctly connected.
The temperature sensor is faulty.
The control board of the cabinet is faulty.
Procedure
Step 1 Check whether the temperature sensor of battery group 1 is installed.
If...
Then...
Install the temperature sensor correctly.
The temperature sensor is installed.
Step 2 Check on the NMS whether the BAT1TEMP_SENSOR_FAIL alarm is cleared. If the
BAT1TEMP_SENSOR_FAIL alarm persists, check whether the temperature sensor of battery
group 1 is correctly connected or the cable is damaged.
5-50
If...
Then...
The temperature sensor is not correctly

connected.
Connect the temperature sensor correctly.

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The cable is damaged.
Replace the cable with a proper one.
If the temperature sensor is correctly connected Go to the next step.

and the cable is intact.
BAT1TEMP_SENSOR_FAIL alarm persists, replace the temperature sensor with a proper one.
Step 4 If the BAT1TEMP_SENSOR_FAIL alarm persists after the temperature sensor is replaced,
replace the cabinet.
----End
Related Information
None.
Description
The BAT2TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of battery
group 2 fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When this alarm is reported, the equipment cannot collect the temperature data of PMU battery
group 2.
Possible Causes
The possible causes of the BAT2TEMP_SENSOR_FAIL alarm are as follows:
l
The temperature sensor is not correctly connected.
The control board of the cabinet is faulty.
Issue 02 (2011-06-30)

5-51

System
5 Alarm Reference
Procedure
Step 1 Check whether the temperature sensor of battery group 2 is installed.
If...
Then...
The temperature sensor is installed.
BAT2TEMP_SENSOR_FAIL alarm persists, check whether the temperature sensor of battery
group 2 is correctly connected or the cable is damaged.
If...
Then...
The temperature sensor is not correctly

connected.
If the temperature sensor is correctly connected Go to the next step.

and the cable is intact.
BAT2TEMP_SENSOR_FAIL alarm persists, replace the temperature sensor with a proper one.
Step 4 If the BAT2TEMP_SENSOR_FAIL alarm persists after the temperature sensor is replaced,
----End
Related Information
None.
5.2.22 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor on the board
fails.
Attribute
5-52
Alarm Severity
Alarm Type
Major
Equipment alarm

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
None.

If this alarm is reported, the equipment cannot collect the temperature data of the board on the
TCU.
Possible Causes
The possible causes of the BDTEMP_SENSOR_FAIL alarm are as follows:
l
The temperature sensor is incorrectly connected.
The control board in the cabinet is faulty.
Procedure
Step 1 Check whether the temperature sensor is installed.
If...
Then...
The temperature sensor is not installed
The temperature sensor is installed
Step 2 Check on the NMS whether the BDTEMP_SENSOR_FAIL alarm is cleared. If the
BDTEMP_SENSOR_FAIL alarm persists, check whether the temperature sensor is correctly
connected or the cable is intact.
If...
Then...
The temperature sensor is incorrectly

connected
The cable is damaged
Temperature sensor is correctly connected and Go to the next step.

the cable is intact
Step 3 Check on the NMS whether the BDTEMP_SENSOR_FAIL alarm is cleared. If the
BDTEMP_SENSOR_FAIL alarm persists, replace the temperature sensor with a proper one.
Step 4 If the BDTEMP_SENSOR_FAIL alarm persists after the temperature sensor is replaced, replace
the cabinet.
----End
Issue 02 (2011-06-30)

5-53

System
5 Alarm Reference
Related Information
None.
5.2.23 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the created logical board is offline.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the BD_STATUS, 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.
The board is installed but poorly connected.
The RAM memory is faulty.
The board is faulty.
Procedure
Step 1 Check the alarms reported by the NE. Check whether the board is correctly seated in the slot of
the NE.
5-54
If...
Then...
The board is not physically installed
Properly install the board into the

corresponding slot of the NE. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
If the board is poorly connected
Properly install the board into the

corresponding slot of the NE. Then, check

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
If the board is correctly installed
Step 2 Check whether the RAM memory on the equipment is faulty.

If...
Then...
The RAM memory is faulty
Replace the RAM memory with a functioning

one. If the alarm persists, go to the next step.
The RAM memory works properly
Step 3 check whether the board is faulty.

If...
Then...
If the board is faulty
Perform a cold reset on the board, or replace

the board with a functioning one.
If the board is not faulty

----End
Related Information
None.
5.2.24 BIOS_STATUS
Description
The BIOS_STATUS is an alarm indicating the BIOS status. By default, if loading of the board
software fails for five consecutive times within 780 seconds, the board enters the BIOS status
and the BIOS_STATUS alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
Issue 02 (2011-06-30)

5-55

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1
Indicates the slot number.

When an anomaly occurs in the board software or hardware, the BIOS_STATUS alarm is
generated and related services are interrupted.
Possible Causes
The possible causes of the BIOS_STATUS alarm are as follows:
l
The software is lost.
Incorrect software is loaded.
Writing or reading the software becomes abnormal.
The board hardware is faulty.
Procedure
Step 1 View the BIOS_STATUS alarm on the U2000, and then confirm the board where the
BIOS_STATUS alarm is generated according to Parameter 1.
Step 2 Perform warm reset for the board and then check whether the BIOS_STATUS alarm is cleared.
Step 3 If the BIOS_STATUS alarm persists, perform cold reset for the board. Then check whether the
BIOS_STATUS alarm is cleared.
Step 4 If the BIOS_STATUS alarm persists, contact Huawei technical support engineers and ask them
to replace the board software. After the board software is replaced, check whether the
BIOS_STATUS alarm is cleared.
Step 5 If the alarm persists, replace the board and check whether the BIOS_STATUS alarm is cleared.
----End
Related Information
None.
5.2.25 BIP_EXC
Description
The BIP_EXC is an alarm indicating that the number of BIP2 bit errors on the tributary board
exceeds the threshold.
5-56

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1

If the alarm occurs, it indicates that serious lower order path bit errors(BIP) exist. The bit errors
will affect the service of the path. If the SNCP switching is configured, and BIP_EXC switching
function is enabled, this alarm will trigger the BIP_EXC 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_EXC alarm are as follows:
l
The section-level or higher order bit errors occur.
The bit errors in lower order services are excessive.
The cross-connect board is faulty.
Procedure
Step 1 Check whether there are section-level or higher order bit errors on the line board that accesses
the services.
Issue 02 (2011-06-30)
If...
Then...
There is the B1_EXC, B2_EXC, B3_EXC,

B1_SD, B2_SD, or B3_SD alarm


B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD.

5-57

System
5 Alarm Reference
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 (on the corresponding access board) of
the board. Check whether the interconnected equipment reports bit errors.
Step 3 If yes, remove the fault of the PDH equipment. View alarms on the U2000 to check whether the
BIP_EXC alarm is cleared.
If...
Then...
Step 4 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



If the transmit end of the board at the local

station is faulty, replace the faulty board.
CAUTION
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD
5.2.26 BIP_SD
Description
The BIP_SD is an alarm indicating that the lower order signals (BIP2) on the tributary board
are degraded.
Attribute
5-58
Alarm Severity
Alarm Type
Minor

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

If the alarm occurs, it indicates that lower order path bit errors exist. The bit errors will affect
the service of the path. If lower order PP protection switching is configured and BIP_SD
switching function is enabled, this alarm will trigger the BIP_SD 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.
The BIP2 bit errors in lower order services are excessive.
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 the B1_EXC, B2_EXC, B3_EXC,

B1_SD, B2_SD, or B3_SD alarm


B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD.
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 (on the corresponding access board) of
the board. Check whether the interconnected equipment reports bit errors.
Step 3 If yes, remove the fault of the PDH equipment. View alarms on the U2000 to check whether the
BIP_SD alarm is cleared.
Issue 02 (2011-06-30)
If...
Then...

5-59

System
5 Alarm Reference
Step 4 Perform a loopback on the optical interface for the stations at both ends of the line. Locate the
faulty board.
If...
Then...



The transmit end of the board at the local

CAUTION
----End
Related Information
B1_EXC, B1_SD,B2_EXC,B2_SD,B3_EXC, B3_SD
5.2.27 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating the BOOTROM data check failure. During the
running of board software, the system periodically checks whether the BOOTROM data is
damaged. This alarm occurs when the BOOTROM data is detected damaged.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
table.
5-60

Issue 02 (2011-06-30)

System
Name
Meaning
Parameter 1
Indicates the type of the BIOS damage.
5 Alarm Reference
l 0x01: Basic BIOS damaged.

l 0x02: Extended BIOS damaged.
Parameter 2
0xff
Parameter 3
0xff

l
If the board has been started, the BOOTROM_BAD alarm does not affect the system or
the services.
If you perform a cold reset for the board when there is the BOOTROM_BAD alarm, the
board fails to load BIOS and cannot be started.
Possible Causes
The possible causes of the BOOTROM_BAD alarm are as follows:
l
The basic BIOS is damaged.
The extended BIOS is damaged.
The BOOTROM data area is damaged.
Procedure
Step 1 View the BOOTROM_BAD alarm on the U2000 and confirm the relevant board.
Step 2 Replace the board. If the board has been started, do not replace the board. Replacing the board
can interrupt services, whereas the BOOTROM_BAD alarm does not affect the system or the
services.
----End
Related Information
None
5.2.28 BUS_ERR
Description
The BUS_ERR is an alarm indicating that a bus error occurs. This alarm is reported when the
bus is abnormal.
Issue 02 (2011-06-30)

5-61

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the logical slot ID.

Parameter 2 Indicates the sequence number of the bus in the slot, that is, the sequence number
of the faulty bus.
Parameter 3 Indicates the BUS_ERR alarm status.
Parameter 4 Indicates the BUS_ERR alarm type in the case of the cross-connect board.
l 0x01: Detected by one cross-connect board.
l 0x02: Detected by active/standby cross-connect boards through the
handshake.

l
When the BUS_ERR alarm is reported, the services that pass through the relevant bus are
interrupted or have bit errors.
When the type II BUS_ERR alarm is reported, working/protection switching is triggered.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows:
l
The software versions do not match
The board is inserted in an incorrect slot or in poor contact with the backplane.
The service board is faulty.
The chip on the cross-connect board is faulty.
The backplane bus from the service board to the cross-connect board is faulty.
Procedure
Step 1 On the NMS, query the current alarms and determine the cross-connect board that reports the
BUS_ERR alarm. Determine the service board corresponding to the cross-connect board
5-62

Issue 02 (2011-06-30)

System
5 Alarm Reference
according to Parameter 1. Determine the type of the BUS_ERR alarm according to Parameter
4.
Step 2 If the value of Parameter 4 is 0x01 or 0x02, query the software version of the cross-connect
board that reports the BUS_ERR alarm and the software version of the service board indicated
by Parameter 1. Then, check whether the software versions match.
If...
Then...
The software versions match
Upgrade the required software to a mapping

version. For details about how to upgrade the
required software, see the product software
upgrade guide.
Step 3 Query the logical version and software version of the cross-connect board, and check whether
the software versions match.
If...
Then...
The software versions match
Upgrade the required software to a mapping

version. For details about how to upgrade the
required software, see the product software
upgrade guide.
Step 4 Check whether the service board indicated by Parameter 1 and the cross-connect board that
reports the alarm are properly inserted. Ensure that the boards are properly inserted. Then, check
whether the alarm is cleared. If the alarm persists, go to the next step.
Step 5 If the alarm persists, reset the service board, and then check whether the alarm is cleared. If the
NOTE
A warm reset can be performed first. If the alarm persists after the warm reset, perform a cold reset.
Step 6 If the alarm persists, replace the service board, and then check whether the alarm is cleared. If
CAUTION
If the services on the board are not protected, do not perform a cold reset or replace the board.
Otherwise, the services may be interrupted.
Issue 02 (2011-06-30)

5-63

System
5 Alarm Reference
Step 7 If the alarm persists, reset the service board, and then check whether the alarm is cleared. If the
Step 8 Reset the cross-connect board that reports the alarm, and then check whether the alarm is cleared.
NOTE
A warm reset can be performed first. If the alarm persists after the warm reset, perform a cold reset.
Step 9 If the alarm persists, replace the cross-connect board that reports the alarm, and then check
whether the alarm is cleared. If the alarm persists, go to the next step.
CAUTION
If no protection cross-connect board is working properly, do not perform the operation.
Otherwise, the services may be interrupted.
Step 10 If the alarm persists, reset or replace the cross-connect board that does not report the alarm. Then,
check whether the alarm is cleared. If the alarm persists, go to the next step.
Step 11 Contact Huawei technical support engineers to check whether the fault is caused by the bent
pins on the backplane. If the backplane is faulty, replace the backplane.
----End
Related Information
None.
5.2.29 BUS_LOC
Description
The BUS_LOC is an alarm indicating the loss of clock in the downlink bus on the tributary
board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
5-64

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1
Optical port ID, fixed as 0x01.

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.
Procedure
Step 1 Reset the tributary board.
Step 2 After the board operates normally, view alarms on the U2000 to check whether the BUS_LOC
alarm is cleared.
If...
Then...
Step 3 The tributary board is faulty. Replace the faulty board.
CAUTION
Replacing the board will interrupt services. This operation is of risk. Ensure that the type of the
received signal of the new tributary board is consistent with that of the board to be replaced.
----End
Related Information
None
5.2.30 CFCARD_FAILED
Description
The CFCARD_FAILED is an alarm indicating that operations on the CF card fail.
Issue 02 (2011-06-30)

5-65

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Name
Meaning
Parameter 1
Indicates the reason of a failed operation on the CF card.

l 0x01: Creating the file system of the CF card fails.
l 0x02: The file system of the CF card does not match.
l 0x03: The CF card fails to be initialized.

When this alarm occurs, the services are not affected. Only the corresponding operations on the
CF card cannot be successfully performed.
Possible Causes
The possible causes of the CFCARD_FAILED alarm are as follows:
l
Creating the file system of the CF card fails.
The file system of the CF card does not match.
The hardware initialization of the CF card fails.
Procedure
Step 1 On the U2000, check whether the CFCARD_FAILED alarm is reported.
If...
Then...
The alarm is reported
Replace the system control and clock board.
The alarm is not reported
----End
Related Information
None.
5.2.31 CFCARD_FULL
5-66

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The CFCARD_FULL is an alarm indicating that all capacity of the CF card is used.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the slot number of the board where the CFCARD_FULL

alarm is generated.
Parameter 2
Indicates the CF card number.
Parameter 3
Indicates the partition number of the CF card. If the bit is 1, it

indicates that this alarm is generated in this partition. If the bit is 0,
it indicates that this alarm is not generated in this partition.
l Bit (0) corresponds to SFS1.
NOTE
Bit (0) is the least significant bit.
Parameter 4, Parameter 5 Reserved.

In the case of the CFCARD_FULL alarm, services are not affected. The CFCARD_FULL alarm
is generated to indicate the CF card has no spare capacity.
Possible Causes
The possible cause of the CFCARD_FULL alarm is as follows:
l
Issue 02 (2011-06-30)
Used capacity of partitions of the CF card crosses the threshold, which is 80% of the
capacity.
5-67

System
5 Alarm Reference
Procedure
Step 1 On the U2000, check whether the CFCARD_FULL alarm is reported.
If...
Then...
The alarm is reported
Remove the excessive files from the CF card,

and then check whether the CFCARD_FULL
alarm is cleared. If the alarm persists, go to
the next step.
The alarm is not reported
Step 2 Replace the CF card with one of a larger capacity.

----End
Related Information
None.
5.2.32 CFCARD_OFFLINE
Description
The CFCARD_OFFLINE is an alarm of CF card offline.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the CFCARD_OFFLINE alarm occurs, the database cannot be backed up to the CF card
or be restored from the CF card. This alarm may cause rollback of the package loading upgrade.
Possible Causes
The possible cause of the CFCARD_OFFLINE alarm is as follows:
5-68
The CF card is not installed.
The CF card is in poor contact with the system control and communication board.
The CF card is faulty.
The SCC board is faulty.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 Check whether the CF card is installed.
If...
Then...
CF card is installed
Install the CF card. Then, check whether the

the next step.
CF card is not installed
Step 2 Check whether the alarm is cleared on U2000. If the CFCARD_OFFLINE alarm persists, check
whether the CF card is loosened..
If...
Then...
The CF card is loose
Install the CF card properly, and then check

whether the CFCARD_OFFLINE alarm is
cleared. If the alarm persists, go to the next
step.
The CF card is installed securely
Step 3 Check whether the alarm is cleared on U2000. Check whether the 5.2.63 HARD_BAD alarm
occurs on the system control and communication board.
If...
Then...
A hardware-related alarm is reported
Perform a cold reset or replace the system

control and clock board with a functioning
one. Then, check whether the
CFCARD_OFFLINE alarm is cleared. If the
No hardware-related alarm is reported

----End
Related Information
None.
5.2.33 CFCARD_W_R_DISABLED
Description
The CFCARD_W_R_DISABLED is an alarm indicating that reading and writing the CF card
are disabled.
Issue 02 (2011-06-30)

5-69

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the CFCARD_W_R_DISABLED alarm occurs, the system is not affected. The alarm
only indicates that reading and writing the CF card are disabled.
Possible Causes
The possible cause of the CFCARD_W_R_DISABLED alarm is as follows:
Keep pressing the button on the CF card for more than five seconds.
Procedure
Step 1 Press the button on the CF card again.
NOTE
A CFCARD_W_R_DISABLED alarm is reported when reading and writing the CF card are manually
disabled. Such an alarm will no longer be reported because the CF card button is removed from the front
panel of an OptiX OSN 550.
----End
Related Information
None.
5.2.34 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE is an alarm indicating that the clock changes to a non-tracing
running mode. This alarm occurs when the current clock does not trace any line clock source,
tributary clock source, or external clock source.
Attribute
5-70
Alarm Severity
Alarm Type
Minor
Equipment alarm

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: The clock changes from the tracing state to the hold state.
l 0x02: The clock changes from the tracing state to the free-run state.

When the CLK_NO_TRACE_MODE alarm occurs, the clock is in a non-tracing running mode.
In this case, the system clock is of a low quality. When the low quality clock results in the outof-synchronization status among NEs, the bit error rate of services increases.
Possible Causes
The possible causes of the CLK_NO_TRACE_MODE alarm are as follows:
l
A priority table is not manually set for the system, and NEs use their own default priority
tables.
A priority table is set, but only the internal clock source in the priority table can be traced.
Procedure
Step 1 Query the current priority table of the system. If there is only the internal clock source in the
priority table, set the clock source priority table to include other available clock sources. After
the setting, the alarm is automatically cleared.
Step 2 In the current priority table, if the internal clock source is not the only available source, find out
why other clock sources cannot be traced. Common causes are as follows:
l
The existence status of the clock source is lost. In this case, the system generates a
SYNC_C_LOS alarm. After the SYNC_C_LOS alarm is cleared, the system clock traces
any one clock source other than the internal clock source, and then the
CLK_NO_TRACE_MODE alarm is automatically cleared.
The local station enables the SSM protocol, while the upstream station does not enable the
SSM protocol. In this case, enable the SSM protocol at the upstream station. When the
system clock traces any one clock source other than the internal clock source, the
CLK_NO_TRACE_MODE alarm is automatically cleared.
----End
Related Information
None.
Issue 02 (2011-06-30)

5-71

System
5 Alarm Reference
5.2.35 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a database error.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the alarm type. The value is the error code that causes the
DBMS_ERROR alarm.
Parameter 2 Indicates the database storage area that has errors.
l 0x00: FDB0
l 0x01: FDB1
l 0x02: DRDB
Parameter 3 Indicates the ID of the database that has errors. Currently, the value can only be
0 - 255 (0x00 - 0xFF).
l 0x00: Entire storage area
l 0x01 to 0xFF: Specific database

The impacts of the DBMS_ERROR alarm on the system are as follows:
l
The backup of the active and standby databases fails.
The database cannot be restored by itself.
Possible Causes
The possible causes of the DBMS_ERROR alarm are as follows:
l
5-72
The software is abnormal.

Issue 02 (2011-06-30)

System
5 Alarm Reference
The hardware medium is abnormal.
Procedure
Step 1 When the DBMS_ERR alarm occurs, contact the engineers of Huawei.
----End
Related Information
The DBMS_ERR alarm is used for the R&D personnel to locate the system abnormality. When
the DBMS_ERR alarm occurs, contact the engineers of Huawei.
5.2.36 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE alarm indicates that the system database is in the protected
mode.
Attribute
Alarm Severity
Alarm Type
Critical
Processing failed
Parameters
None.

When the DBMS_PROTECT_MODE alarm occurs, the abnormality occurs to the system. 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.
Possible Causes
The possible cause of the DBMS_PROTECT_MODE alarm is as follows:
l
The SCC board is abnormal and thus the SCC board is repeatedly reset.
Procedure
Step 1 Replace the SCC board at the local station, and issue the service configuration again on the
U2000.
----End
Related Information
None
Issue 02 (2011-06-30)

5-73

System
5 Alarm Reference
5.2.37 DCC_CHAN_LACK
Description
The DCC_CHAN_LACK is an alarm indicating that the DCC channel resource is insufficient.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the slot number.

Parameter 2 Indicates the number of the optical interface.
Parameter 3 Indicates the DCC channel mode in which the CPU resource fails to be obtained.
l 0x03: Three bytes of the DCC channel resources fail to be obtained.
l 0x09: Nine bytes of the DCC channel resources fail to be obtained.
l 0x20: Thirty-two bytes of the DCC channel resources fail to be obtained.
l 0x60: Ninety-six bytes of the DCC channel resources fail to be obtained.

If the optical interface is not allocated with CPU resources, the corresponding ECC channel
cannot be used for communication.
Possible Causes
The possible causes of the DCC_CHAN_LACK alarm are as follows:
5-74
The CPU does not have enough resources to be allocated to the optical channel of the
corresponding type.
For example, if the channel type of optical interface 1 is D1 - D3, the CPU cannot allocate
three bytes of the channel resources to this optical interface.
Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 View the DCC_CHAN_LACK alarm on the NMS to determine the board where the alarm is
generated. According to Parameter 2, determine the number of the optical interface where the
alarm is generated.
Step 2 Delete the channel of the optical interface that cannot obtain the CPU resources, or set the
enabling state of the DCC communication of the optical interface to be disabled. Then, check
whether the alarm is cleared.
CAUTION
Do not delete the optical interface that is being used. For the DCC channel of the D1 - D3 or D4
- D12 type, the DCC communication of the optical interface should be disabled or enabled at
the same time.
----End
Related Information
None.
5.2.38 DOWN_E1_AIS
Description
The DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when the
tributary board detects the 2 Mbit/s downlink signal of all 1s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
The value is always 0x01 and this parameter is meaningless.
Issue 02 (2011-06-30)

5-75

System
5 Alarm Reference

When the DOWN_E1_AIS alarm occurs, the E1 signal in the path that reports the alarm is
unavailable.
Possible Causes
The possible causes of the DOWN_E1_AIS alarm are as follows:
l
The local station reports a high-level alarm, such as the R_LOS, R_LOC, R_LOF, or
MS_AIS alarm.
The opposite station reports the UP_E1_AIS or T_ALOS alarm.
The tributary board at the local station is faulty.
The system control and cross-connect board at the local station is faulty.
Procedure
Step 1 On the NMS, check whether the local station reports the R_LOS, R_LOC, R_LOF, or MS_AIS
alarm.
If...
Then...
The R_LOS, R_LOC, R_LOF, or MS_AIS

alarm is reported
Clear these alarms immediately, and then

check whether the DOWN_E1_AIS alarm is
step.
The R_LOS, R_LOC, R_LOF, or MS_AIS

alarm is not reported
Step 2 On the NMS, check whether the opposite equipment reports an UP_E1_AIS or T_ALOS alarm.
If...
Then...
The opposite equipment reports an

UP_E1_AIS or T_ALOS alarm
Handle the alarm. If the alarm persists, go to

the next step.
The opposite equipment does not report an

UP_E1_AIS or T_ALOS alarm
Step 3 Check whether the tributary board on the local equipment is faulty.
If...
Then...
The tributary board is faulty
Replace the tributary board with a

functioning one. If the alarm persists, go to
the next step.
The tributary board works properly
Step 4 Check whether the system control and cross-connect board at the local station is faulty.
5-76

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The system control and cross-connect board

is faulty
Replace the system control and cross-connect

board with a functioning one. If the alarm

works properly

----End
Related Information
None.
5.2.39 DOWN_T1_AIS
Description
The DOWN_T1_AIS is an indication alarm of the downstream 1.5 Mbit/s signals. If a tributary
board has detected that the value of the downstream T1 signals is all "1"s, the DOWN_T1_AIS
alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

When the DOWN_T1_AIS alarm occurs, the T1 signals in the board path are unavailable.
Issue 02 (2011-06-30)

5-77

System
5 Alarm Reference
Possible Causes
The possible causes of the DOWN_T1_AIS alarm are as follows:
l
A higher-level alarm, such as R_LOS, R_LOC, R_LOF or MS_AIS, occurs at the local
station.
The UP_T1AIS or T_ALOS alarm occurs on the tributary board at the opposite station.
The tributary board of the local station is faulty.
The cross-connect and timing board of the local station is faulty.
Procedure
Step 1 View the DOWN_T1_AIS alarm on the U2000 to confirm the relevant board.
Step 2 Check whether any higher-level alarm, such as R_LOS, R_LOC, R_LOF or MS_AIS, occurs at
the local station. If yes, take priority to clear it, and then check whether the DOWN_T1_AIS
alarm is cleared.
Step 3 On the U2000, check whether the UP_T1AIS or T_ALOS alarm is reported from the tributary
board of the opposite station. If yes, take priority to clear it, and then check whether the
DOWN_T1_AIS alarm is cleared.
Step 4 If the alarm persists, perform a cold reset on the tributary board that reports the alarm at the
opposite station. Then check whether the DOWN_T1_AIS alarm is cleared.
CAUTION
If the services travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
Step 5 If the alarm persists, replace the tributary board that reports the alarm at the local station. Then,
check whether the DOWN_T1_AIS alarm is cleared.
Step 6 If the alarm persists, perform a cold reset on the cross-connect and timing board of the local
station. Then, check whether the DOWN_T1_AIS alarm is cleared.
CAUTION
If there is not a standby cross-connect board that properly functions for protection, cold reset of
a cross-connect board may entirely interrupt the services.
Step 7 If the alarm persists, replace the cross-connect and timing board of the local station. Then, check
whether the DOWN_T1_AIS alarm is cleared.
----End
Related Information
None
5-78

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.40 E1_LOS
Description
The E1_LOS is an alarm indicating loss of 2 Mbit/s line signals (E1 signals).
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

When the E1_LOS alarm occurs, the uplink E1 signal of the 2 Mbit/s tributary board is lost.
Accordingly, the E1 services are unavailable.
The 2 Mbit/s board inserts the E1_AIS in the services to the cross-connect unit.
Possible Causes
The possible causes of the E1_LOS alarm are as follows:
l
The cable connector is loose, or the cable is broken.
The service transmission of the upstream PDH equipment is faulty.
Procedure
Step 1 Check whether the cable connector is loose or whether the cable is broken.
Step 2 If yes, rectify the fault of the cable. View alarms on the U2000 to check whether the E1_LOS
alarm is cleared.
Issue 02 (2011-06-30)
If...
Then...

5-79

System
5 Alarm Reference
If...
Then...
The alarm persists
Step 3 Check whether the service transmitting of the interconnected PDH equipment is faulty.
Step 4 Remove the fault of the interconnected equipment. View alarms on the U2000 to check whether
the E1_LOS alarm is cleared.
If...
Then...
The alarm persists
Step 5 Check the board that reports the alarm at the local station. Perform a reset on the board or replace
the board to clear the alarm.
----End
Related Information
None.
5.2.41 E1_LOC
Description
The E1_LOC is an alarm indicating that the uplink 2M clock is lost. This alarm occurs when
the tributary board fails to extract the clock from the E1 signal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
5-80
Name
Meaning
Parameter 1
Indicates the path number of the tributary port.

Issue 02 (2011-06-30)

System
5 Alarm Reference

When the E1_LOC occurs, the service is not affected.
Possible Causes
The possible causes of the E1_LOC alarm are as follows:
l
The opposite NE is faulty.
The wiring sequence of the cable is incorrect.
The receive unit of the tributary board on the local NE is faulty.
The input E1 signal has an abnormal waveform.
Procedure
Step 1 Rectify the fault on the opposite NE. Check whether the E1_LOC alarm is cleared.
Step 2 Redo the cable.
Step 3 If the alarm persists, replace the board where the line unit is located.
Step 4 Check whether any external interference causes the abnormal waveform of the E1 signal.
If...
Then...
There is the external interference
There is no external interference
Contact Huawei engineers.
----End
Related Information
None.
5.2.42 ENVHUM_SENSOR_FAIL
Description
The ENVHUM_SENSOR_FAIL is an alarm indicating that the ambient humidity sensor fails.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
None.
Issue 02 (2011-06-30)

5-81

System
5 Alarm Reference

If this alarm is reported, the equipment cannot collect the ambient humidity data of the PMU.
Possible Causes
The possible causes of the ENVHUM_SENSOR_FAIL alarm are as follows:
l
The ambient humidity sensor is not installed.
The ambient humidity sensor is incorrectly connected.
The ambient humidity sensor is faulty.
Procedure
Step 1 Check whether the ambient humidity sensor is installed.
If...
Then...
The ambient humidity sensor is not installed Install the ambient humidity sensor correctly.
The ambient humidity sensor is installed
Step 2 Check on the NMS whether the ENVHUM_SENSOR_FAIL alarm is cleared. If the
ENVHUM_SENSOR_FAIL alarm persists, check whether the ambient humidity sensor is
correctly connected or the cable is intact.
If...
Then...
The ambient humidity sensor is incorrectly Connect the ambient humidity sensor
connected
correctly.
The ambient humidity sensor is correctly

connected and the cable is intact
Step 3 Check on the NMS whether the ENVHUM_SENSOR_FAIL alarm is cleared. If the
ENVHUM_SENSOR_FAIL alarm persists, replace the ambient humidity sensor with a proper
one.
Step 4 If the ENVHUM_SENSOR_FAIL alarm persists after the ambient humidity sensor is replaced,
----End
Related Information
None.
5-82

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.43 ENVTEMP_SENSOR_FAIL
Description
The ENVTEMP_SENSOR_FAIL is an alarm indicating that the ambient temperature sensor
fails.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
None.

If this alarm is reported, the equipment cannot collect the ambient temperature data of the TCU.
Possible Causes
The possible causes of the ENVTEMP_SENSOR_FAIL alarm are as follows:
l
The ambient temperature sensor is not installed.
The ambient temperature sensor is incorrectly connected.
The ambient temperature sensor is faulty.
Procedure
Step 1 Check whether the ambient temperature sensor is installed.
If...
Then...
The ambient temperature sensor is not

installed
Install the ambient temperature sensor

correctly.
The ambient temperature sensor is installed
Step 2 Check on the NMS whether the ENVTEMP_SENSOR_FAIL alarm is cleared. If the
ENVTEMP_SENSOR_FAIL alarm persists, check whether the ambient temperature sensor is
Issue 02 (2011-06-30)
If...
Then...
The ambient temperature sensor is incorrectly

connected

5-83

System
5 Alarm Reference
If...
Then...
The ambient temperature sensor is correctly

Step 3 Check on the NMS whether the ENVTEMP_SENSOR_FAIL alarm is cleared. If the
ENVTEMP_SENSOR_FAIL alarm persists, replace the ambient temperature sensor with a
proper one.
Step 4 If the ENVTEMP_SENSOR_FAIL alarm persists after the ambient temperature sensor is
replaced, replace the cabinet.
----End
Related Information
None.
Description
The ENVTEMP1_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 1
fails.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
None.

If this alarm is reported, the equipment cannot collect the data of ambient temperature sensor 1
on the PMU.
Possible Causes
The possible causes of the ENVTEMP1_SENSOR_FAIL alarm are as follows:
5-84
Ambient temperature sensor 1 is not installed.
Ambient temperature sensor 1 is incorrectly connected.
Ambient temperature sensor 1 is faulty.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 Check whether ambient temperature sensor 1 is installed.
If...
Then...
Ambient temperature sensor 1 is not

installed
Install ambient temperature sensor 1

correctly.
Ambient temperature sensor 1 is installed
Step 2 Check on the NMS whether the ENVTEMP1_SENSOR_FAIL alarm is cleared. If the
ENVTEMP1_SENSOR_FAIL alarm persists, check whether ambient temperature sensor 1 is
If...
Then...
Ambient temperature sensor 1 is incorrectly Connect ambient temperature sensor 1

connected
correctly.
Ambient temperature sensor 1 is correctly

ENVTEMP1_SENSOR_FAIL alarm persists, replace ambient temperature sensor 1 with a
proper one.
Step 4 If the ENVTEMP1_SENSOR_FAIL alarm persists after the ambient temperature sensor is
----End
Related Information
None.
Description
The ENVTEMP2_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 2
fails.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Issue 02 (2011-06-30)

5-85

System
5 Alarm Reference
Parameters
None.

If this alarm is reported, the equipment cannot collect the data of ambient temperature sensor 2
on the PMU.
Possible Causes
The possible causes of the ENVTEMP2_SENSOR_FAIL alarm are as follows:
l
Ambient temperature sensor 2 is not installed.
Ambient humidity sensor 2 is incorrectly connected.
Ambient temperature sensor 2 is faulty.
Procedure
Step 1 Check whether ambient temperature sensor 2 is installed.
If...
Then...
Ambient temperature sensor 2 is not

installed.
Install ambient temperature sensor 2

correctly.
Ambient temperature sensor 2 is installed
ENVTEMP2_SENSOR_FAIL alarm persists, check whether ambient temperature sensor 2 is
If...
Then...
Ambient temperature sensor 2 is incorrectly Connect ambient temperature sensor 2

connected
correctly.
Ambient temperature sensor 2 is correctly

ENVTEMP2_SENSOR_FAIL alarm persists, replace ambient temperature sensor 2 with a
proper one.
Step 4 If the ENVTEMP2_SENSOR_FAIL alarm persists after the ambient temperature sensor is
----End
5-86

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None.
5.2.46 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating the loss of continuity. When the system does not
receive the continuity check message (CCM) sent by the maintenance end point (MEP) within
3.5 times of the continuity check (CC) period, the system reports the ETH_CFM_LOC alarm.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1, Parameter 2, Parameter 3,

Parameter 4 (Port)
Indicates the ID of the Ethernet port where the

alarm is reported.
Parameter 5, Parameter 6 (VLAN ID)
Indicates the VLAN ID of the relevant

maintenance point (MP).
Parameter 7 (Direction)
Indicates the direction of the relevant MP.

l 0x00: indicates that the direction of the port
is not considered.
l 0x01: indicates the ingress direction of the
port.
l 0x02: indicates the egress direction of the
port.
Issue 02 (2011-06-30)

5-87

System
5 Alarm Reference
Name
Meaning
Parameter 8 (Level)
Indicates the level of the maintenance domain.

l 0x00: indicates that the customer MP is at the
low level.
middle level.
high level.
l 0x03: indicates that the provider MP is at the
low level.
high level.
l 0x05: indicates that the operator MP is at the
low level.
middle level.
high level.
NOTE
Consumer indicates the user, provider indicates the
supplier, and operator indicates the carrier.
Parameter 9, Parameter 10 (RMEPID)
Indicates the ID of the remote MP.

l
The LB and LT test functions that comply with IEEE 802.1ag ETH-OAM are unavailable.
The services between the relevant standard MPs may be interrupted.
Possible Causes
The possible causes of the ETH_CFM_LOC alarm are as follows:
l
The Ethernet services between the standard MPs at the two ends are interrupted.
The MEP is not correctly configured at the opposite end.
Check whether the Ethernet services are correctly configured.
Severe congestion occurs on the network.
Procedure
Step 1 Check whether the physical links (for example, network cables or optical fibers) between the
standard MPs at the two ends are correctly connected.
5-88
If...
Then...
The physical links between the standard

MPs at the two ends are not correctly
connected
Re-connect the cables and rectify the fault on

the physical links.

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The physical links between the standard

MPs at the two ends are correctly connected
Step 2 Check whether the MEP is correctly configured at the opposite end.
If...
Then...
The MEP is not correctly configured at the Modify the configuration of the MEP and ensure
opposite end
that the configurations of the MEP at both ends
are consistent.
The MEP is correctly configured at the
opposite end
Step 3 Check whether the Ethernet services are correctly configured.

If...
Then...
The Ethernet services are not correctly

configured
Modify the service configuration and ensure

that the configurations of the services at both
ends are consistent.
The Ethernet services are correctly

configured
Step 4 Check the usage of the bandwidth. If the bandwidth resources are completely consumed, expand
the bandwidth or disable the sources that illegally transmit a large amount of data.
----End
Related Information
None
5.2.47 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating incorrect connection. When the system
receives a message that indicates a mismatch of maintenance association (MA) IDs or receives
a low-level CCM, the system reports the ETH_CFM_MISMERGE alarm.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
Issue 02 (2011-06-30)

5-89

System
5 Alarm Reference
table.
Name
Meaning

Parameter 4 (Port)

alarm is reported.
Indicates the VLAN ID of the relevant MP.

is not considered.
port.
port.
Parameter 8 (Level)

low level.
middle level.
high level.
low level.
high level.
low level.
middle level.
high level.
NOTE

l
The services between the relevant standard MPs may be interrupted, or the relevant standard
MPs receive the data streams of other services.
Possible Causes
The possible causes of the ETH_CFM_MISMERGE alarm are as follows:
5-90

Issue 02 (2011-06-30)

System
5 Alarm Reference
The maintenance domain levels of the standard MPs at the two ends are not the same.
The maintenance domain names or MA names of the standard MPs at the two ends are not
the same.
The cables are incorrectly connected.
The line configurations are incorrect.
Procedure
Step 1 Check whether the maintenance domain levels of the standard MPs at the two ends are the same.
If...
Then...
The maintenance domain levels of the

standard MPs at the two ends are not the
same
Set the same maintenance domain level for the

MPs at the two ends.
The maintenance domain levels of the

standard MPs at the two ends are the same
Step 2 Check whether the maintenance domain names or MA names of the standard MPs at the two
ends are the same.
If...
Then...
The maintenance domain names or MA

Set the same maintenance domain name or
names of the standard MPs at the two ends MA name for the standard MPs at the two
are not the same
ends.
The maintenance domain names or MA
names of the standard MPs at the two ends
are the same
Step 3 Check the physical connection and ensure that the cables are correctly connected.
Step 4 Check the line configurations. In the case of an error, configure the lines again.
----End
Related Information
None
5.2.48 ETH_CFM_RDI
Description
The ETH_CFM_RDI is an alarm indicating that the receive end of the MEP at the opposite end
fails. When the system receives a CCM that contains the RDI sent from the opposite end, the
system reports the ETH_CFM_RDI alarm.
Issue 02 (2011-06-30)

5-91

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning

Parameter 4 (Port)

alarm is reported.

is not considered.
port.
port.
Parameter 8 (Level)

low level.
middle level.
high level.
low level.
high level.
low level.
middle level.
high level.
NOTE
5-92

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 9, Parameter 10 (RMEPID)
Indicates the ID of the remote MP.

l
The services between the relevant standard MPs may be interrupted.
Possible Causes
The possible causes of the ETH_CFM_RDI alarm are as follows:
l
The equipment on the MEP at the opposite end is reset.
The equipment on the MEP at the opposite end is faulty (the physical link is not interrupted
but a software fault occurs).
Procedure
Step 1 Find the port that reports the alarm based on the parameter.
Step 2 Check whether the equipment on the MEP at the opposite end is reset. If the equipment is reset,
rectify the fault.
Step 3 Troubleshoot the MEP at the opposite end that is connected to the port that reports the alarm.
Focus on the following alarms that the MEP at the opposite end may report:
ETH_CFM_LOC, ETH_CFM_UNEXPERI and ETH_CFM_MISMERGE.
----End
Related Information
The standard MP refers to the MP that complies with IEEE802.1ag.
5.2.49 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating an incorrect frame. This alarm is reported
when an invalid continuity check message (CCM) is received.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
Issue 02 (2011-06-30)

5-93

System
5 Alarm Reference
table.
Name
Meaning

Parameter 4 (Port)

alarm is reported.

is not considered.
port.
port.
Parameter 8 (Level)

low level.
middle level.
high level.
low level.
high level.
low level.
middle level.
high level.
NOTE

l
The services may be abnormal due to loops.
Possible Causes
The possible causes of the ETH_CFM_UNEXPERI alarm are as follows:
l
5-94
No remote MEP is configured.

Issue 02 (2011-06-30)

System
5 Alarm Reference
The continuity check periods of the standard MPs at the two ends are not the same.
A loop occurs on the services. The packets that are looped back are received.
A software fault occurs at the MEP at the transmit end.
Procedure
Step 1 Check whether the remote MEP is configured. If not, configure the remote MEP first.
Step 2 Check whether the continuity check periods of the standard MPs at the two ends are the same.
If...
Then...
The continuity check periods of the

standard MPs at the two ends are not the
same
Set the same continuity check period for the

standard MPs at the two ends.
The continuity check periods of the

standard MPs at the two ends are the same
Step 3 Enable the P2P OAM loop test function to check whether a loop occurs on the services. If a loop
occurs on the services, release the loop.
Step 4 Perform a warm reset on the Ethernet board where the remote MEP is located.
----End
Related Information
None.
5.2.50 ETH_LOS
Description
The ETH_LOS is an alarm indicating the Ethernet port connection loss.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Issue 02 (2011-06-30)

5-95

System
5 Alarm Reference
Name
Meaning
Parameter 1

The link of the Ethernet port is lost. The services in the receiving direction are interrupted.
Possible Causes
The possible causes of the ETH_LOS alarm are as follows:
l
There is a fiber cut.
The Ethernet cable interference is severe.
The Ethernet port is invalid.
The cut of the twisted pair of the Ethernet occurs.
The processing board is faulty.
Procedure
Step 1 Check the configuration of the Ethernet port at the two sides. If a port is not enabled, enable it.
If the working modes of the two ports are inconsistent, modify the mode to ensure consistency
Step 2 Check whether the connection of the Ethernet twisted pair at two sides of the interface is normal.
Replace the twisted pair cable or insert a loopback crystal connector. Ensure the twisted pair
cable is normal.
Step 3 Check whether the LPT is configured. If the LPT is configured, check whether the service
network or the peer access point is faulty. If any fault is detected, rectify the fault.
Step 4 Replace the faulty processing board.
----End
Related Information
None.
5.2.51 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating the point-to-point Ethernet OAM
discovery failure. When the OAM function is enabled at the port of a board and the negotiation
with the equipment at the opposite end fails, the alarm is reported.
Attribute
5-96
Alarm Severity
Alarm Type
Minor
Equipment alarm

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
Indicates the port number.
Parameter 2, Parameter 3 The value is always 0x01 (reserved).

Parameter 4
Indicates the failure reason.

l 0x01: The local end is incorrectly connected.
l 0x02: The local end fails to transmit OAM packets.
l 0x03: The OAM packets from the opposite end are not received.
l 0x04: The OAM configuration of the opposite end does not meet
the requirements of the local end.
l 0x05: The OAM configuration of the local end does not meet
the requirements of the opposite end.
l 0x06: 0xFF (Reserved).

The alarm is generated when the system runs the IEEE 802.3ah OAM protocol. IEEE 802.3ah
OAM is a link management protocol and is irrelevant to services.
Possible Causes
The possible causes of the ETHOAM_DISCOVER_FAIL alarm are as follows:
l
A link fault occurs at the local end.
The local end fails to transmit the OAM packets.
The local end fails to receive the OAM packets within the specified time.
The OAM configuration of the opposite end does not meet the requirements of the local
end.
The OAM configuration of the local end does not meet the requirements of the opposite
end.
Procedure
Step 1 View the alarm on the NMS and determine the possible causes of the alarm according to
Parameter 4.
Step 2 When the value of Parameter 3 is 0x01, a link fault occurs at the local end. Query board level
alarms on the NMS. Then, rectify the fault according to the specific link alarms such as the
ETH_LOS and LINK_ERR.
Issue 02 (2011-06-30)

5-97

System
5 Alarm Reference
Step 3 When the value of Parameter 4 is 0x02, the local end fails to transmit the OAM packets. View
the printed information about the serial port. The DSSP, drive, and microcode components are
involved in the problem. The fault needs to be located under the assistance of the relevant
engineers.
Step 4 When the value of the parameter is 0x03, the local end fails to receive the 3ahOAM packets
from the opposite end within the time specified by the user.
1.
Check whether the MAC addresses of the interconnected ports are the same. If the MAC
addresses are different, check whether the alarm is cleared.
2.
Check whether the 3ahOAM protocol is enabled at the opposite end. If the protocol is
enabled, check whether the alarm is cleared.
3.
If the alarm persists, the local end fails to receive the packets. Replace the board.
Step 5 When the value of the parameter is 0x04, the OAM configuration of the opposite end, including
link event reporting capability and unidirectional operation capability, does not meet the
requirements of the local end. Query and modify the configuration of the opposite port on the
NMS. When the configuration meets the requirements of the local end, the alarm is cleared
automatically.
Step 6 When the value of the parameter is 0x05, the OAM configuration of the local end does not meet
the requirements of the opposite end. Query and modify the configuration of the local port on
the NMS. When the configuration meets the requirements of the opposite end, the alarm is
cleared automatically.
----End
Related Information
None.
5.2.52 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating a critical fault of the point-to-point
Ethernet OAM function at the remote end. When a port with the OAM function enabled receives
the OAM packets that contain critical fault information from the opposite end, this alarm is
reported.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
5-98

Issue 02 (2011-06-30)

System
Name
Meaning
Parameter 1
5 Alarm Reference
Parameter 2, Parameter 3 The value is always 0x01. These parameters are reserved.
Parameter 4
Indicates the types of the fault.

l 0x01: A link fault occurs at the port of the opposite end.
l 0x02: Irrecoverable problems such as the power failure occur at
the opposite end.
l 0x03: 0xxff (reserved).

OAM is a link management protocol and is irrelevant to services. This alarm indicates that the
signal loss alarm is reported at the receive direction of the opposite port. The fault is critical.
Possible Causes
The possible cause of the ETHOAM_RMT_CRIT_FAULT alarm is as follows:
l
The port with the OAM function enabled receives the OAM packets that contain critical
fault information (such as link fault and power failure) from the opposite end.
Procedure
Step 1 If a link fault occurs at the opposite port, query board level alarms on the NMS. Remove the
fault according to the link alarm such as ETH_LOS or LINK_ERR. Then, check whether the
alarm is cleared.
Step 2 If irrecoverable problems such as power failure occurs at the opposite end, after the fault is
rectified, the alarm is cleared automatically.
Step 3 If other unknown faults occur, contact Huawei engineers.
----End
Related Information
None.
5.2.53 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating the remote loopback of the point-to-point
Ethernet OAM. This alarm is reported only at the port with the point-to-point OAM function
enabled. If the port is able to respond to the loopback, it enters the loopback response state and
reports the loopback response alarm after it receives the remote loopback enabling command
from the OAM port at the opposite end. The loopback initiator reports the loopback initiating
Issue 02 (2011-06-30)

5-99

System
5 Alarm Reference
alarm. If the port receives the loopback disabling command, it exits the loopback response state
and ends the loopback response alarm. The loopback initiator also ends the loopback initiating
alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
The value is always 0x01 (reserved).
Parameter 4
l 0x01: The loopback is initiated.

l 0x02: The loopback is responded.

The alarm is generated when the system runs the IEEE 802.3ah OAM protocol. When the alarm
is reported, the services are loop backed from the loopback initiator to the loopback responder.
The services and other packets are all interrupted.
Possible Causes
The possible causes of the ETHOAM_RMT_LOOP alarm are as follows:
l
A command is issued to enable the loopback at the local port, and the opposite end acts as
the loopback responder.
A command is issued to enable the loopback at the opposite port, and the local end acts as
the loopback responder.
Procedure
Step 1 Disable the loopback function of the port. Then, the alarm is cleared automatically.
----End
Related Information
None.
5-100

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.54 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating the remote performance degradation of the
point-to-point Ethernet OAM function. When the alarm is reported, a port with the OAM
function enabled receives a link event message from the opposite end, indicating that the Ethernet
performance is degraded at the remote end.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
The value is always 0x01 (the value can be extended).
Parameter 4
Indicates the event type.

l 0x01: errored frame event
l 0x02: errored frame period event
l 0x03: errored frame second event

OAM is a link management protocol and is irrelevant to services. When the alarm is reported,
the number of errored frames crosses the threshold at the receive direction of the local port. The
service performance is degraded.
Possible Causes
The possible causes of the ETHOAM_RMT_SD alarm are as follows:
l
Issue 02 (2011-06-30)
The port with the OAM protocol enabled receives the link event message from the opposite
end.
5-101

System
5 Alarm Reference
Procedure
Step 1 Improve the link performance at the opposite end so that the opposite end does not send a link
event message to the local end any longer. Then, the ETHOAM_RMT_SD alarm at the local
end is cleared automatically.
Step 2 Modify the value of the link performance monitoring threshold at the opposite end. Then, the
ETHOAM_RMT_SD alarm at the local end is cleared.
Step 3 Disable the link event function at the opposite end. Then, the ETHOAM_RMT_SD alarm at the
local end is cleared.
----End
Related Information
None.
5.2.55 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs the
point-to-point OAM protocol. If the MAC port of a board receives the OAM protocol packets
transmitted from the local port or the local board after detection of the loop is enabled, the alarm
is reported.
Attribute
Alarm Severity
Alarm Type
Major
Environment
Parameters
table.
5-102
Name
Meaning
Parameter 1
The value is always 0x01.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 4
Indicates the loopback reason.

l 0x01: The port is self-looped.
l 0x02: The board is self-looped.
l 0x03: 0xff (reserved).

In the case of the ETHOAM_SELF_LOOP alarm, the port is in the self-loop state. The NMS
provides a function of automatically shutting down the port in the case of port self-loop. If the
user enables this function in advance, services at this port are interrupted. If the user does not
enable this function, a broadcast storm may occur.
Possible Causes
The possible causes of the ETHOAM_SELF_LOOP alarm are as follows:
l
The fiber at the port is self-looped.
A loopback is set among ports of the board.
The PHY or MAC loopback of the port is manually set.
Procedure
Step 1 Check whether the transmit and receive ends of the port are connected through a fiber. If the
fiber is properly connected, check whether the alarm is cleared.
Step 2 Check whether the transmit and receive ends of this port are connected to those of other ports
through fibers. If yes, connect the fibers correctly, and then check whether the alarm is cleared.
Step 3 Check whether any PHY layer or MAC layer loopback is set for this port. If yes, release the
loopback manually, or wait five minutes for the NMS to release the loopback automatically.
Then, check whether the alarm is cleared.
----End
Related Information
None.
5.2.56 EX_ETHOAM_CC_LOS
Description
The EX_ETHOAM_CC_LOS is an alarm indicating the loss of the periodic connectivity check
(CC) packets. After receiving the CC packets from the source maintenance point, the sink
maintenance point starts the timer and then periodically checks the link between the source and
sink maintenance points. If the sink maintenance point does not receive the CC packets from
the source maintenance point in one period (3.5 times of the duration in which the CC packets
are transmitted from the source maintenance point to the sink maintenance point), this alarm is
reported.
Issue 02 (2011-06-30)

5-103

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of maintenance point(MEP) where the

EX_ETHOAM_CC_LOS alarm is reported. The MEP ID should be unique in
the entire network.
Parameter 2 Indicates the number of the Ethernet port where the EX_ETHOAM_CC_LOS
alarm is reported.
l 0x03-0xff: types for expansion. MAC port number: 0x0001-0x0000 +
MAX_ETH_PORT.
l VCTRUNK port number: 0x8001-0x8000 + MAX_ETH_VCTRUNK.
NOTE
l The MAX_ETH_PORT indicates the maximum MAC port number supported by the
board.
l The MAX_ETH_VCTRUNK indicates the maximum VCTRUNK port number
supported by the board.
Parameter 3 Indicates the service VLAN ID.

l For a service with the VLAN tag, the VLAN ID ranges from 0x0000 to
0x0FFF.
l For a service without the VLAN tag, the VLAN ID is 0xffFF.
5-104

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 4 Indicates the maintenance domain level.

l 0x00: Consumer MEP level (high).
l 0x01: Consumer MEP level (middle).
l 0x02: Consumer MEP level (low).
l 0x03: Provider MEP level (high).
l 0x04: Provider MEP level (low).
l 0x05: Operator MEP level (high).
l 0x06: Operator MEP level (middle).
l 0x07: Operator MEP level (low).
NOTE
Consumer indicates the customer, provider the supplier and operator the carrier.
Parameter 5 Indicates the ID of the MEP at the CC source. The MEP ID should be unique in
the entire network.
Parameter 6 Indicates the ID of the MEP at the CC sink. The MEP ID should be unique in the
entire network.
NOTE
The ID of the MEP at the CC sink is the ID of the MEP where the EX_ETHOAM_CC_LOS
alarm is reported. Parameter 1 and Parameter 6 carry the same information.

This alarm reminds you that a unidirectional connectivity failure has been detected in the link
from the source maintenance point to the sink maintenance point.
Possible Causes
The possible causes of the alarm are as follows:
l
A software or hardware failure occurs on the services from the source maintenance point
to the sink maintenance point.
A congestion or an interruption occurs on the services from the source maintenance point
to the sink maintenance point.
Procedure
Step 1 View the alarm on the NMS. According to the parameters, determine the ID of the MEP where
the alarm occurs.
Step 2 Query the information about the MEP.
Step 3 Perform the loopback (LB) or link trace (LT) on the source and sink MEPs to locate the fault
on the services between the source and sink MEPs.
Issue 02 (2011-06-30)

5-105

System
5 Alarm Reference
Step 4 Check the faulty services (check the software, hardware, and traffic) and then restore the services.
When the services are restored, the alarm is automatically cleared.
----End
Related Information
None
5.2.57 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the ID conflict of the MEP. It means
that one maintenance point has received packets from another maintenance point with the same
maintenance point identity (MPID) in one maintenance domain.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the ID of maintenance point(MEP) where the alarm is reported. The
MEP ID should be unique in the entire network.
Parameter 2 Indicates the number of the Ethernet port where the alarm is reported.
l 0x03-0xff: types for expansion. MAC port number: 0x0001-0x0000 +
MAX_ETH_PORT.
l VCTRUNK port number: 0x8001-0x8000 + MAX_ETH_VCTRUNK.
NOTE
l The MAX_ETH_PORT indicates the maximum MAC port number supported by the
board.
l The MAX_ETH_VCTRUNK indicates the maximum VCTRUNK port number
supported by the board.
5-106

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 3 Indicates the service VLAN ID.

l For a service with the VLAN tag, the VLAN ID ranges from 0x0000 to
0x0FFF.
l For a service without the VLAN tag, the VLAN ID is 0xffFF.
Parameter 4 Indicates the maintenance domain level.
l 0x00: Consumer MEP level (high).
l 0x01: Consumer MEP level (middle).
l 0x02: Consumer MEP level (low).
l 0x04: Provider MEP level (low).
l 0x05: Operator MEP level (high).
l 0x06: Operator MEP level (middle).
l 0x07: Operator MEP level (low).
NOTE
Consumer indicates the customer, provider the supplier and operator the carrier.
Parameter 5 Indicates the ID of the local MEP. The MEP ID should be unique in the entire
network.
NOTE
The ID of the local MEP is the ID of the MEP where the alarm is reported. Parameter 1 and
Parameter 5 carry the same information.

The ID of the MEP must be unique in the entire network. If the MEP ID conflicts, the protocol
is affected. Consequently, the LB and LT tests become abnormal and the services are incorrectly
received.
Possible Causes
The possible causes of the EX_ETHOAM_MPID_CNFLCT alarm are as follows:
l
In a maintenance domain, multiple MEPs with the same MPID are created.
Procedure
Step 1 View the alarm on the NMS. According to the parameters, determine the ID of the MEP where
the alarm is reported.
Step 2 Query the information about the maintenance point. After the maintenance points with the same
MPID are deleted, the alarm is cleared automatically.
----End
Issue 02 (2011-06-30)

5-107

System
5 Alarm Reference
Related Information
None
5.2.58 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating loss of the external clock source set on the clock
board.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 to Parameter 4
Indicates the lost clock source.

l 0x01: clock source 1
l 0x02:clock source 2

When the EXT_SYNC_LOS occurs, the external clock source set in the clock source priority
table on the clock board is invalid. The signal framing is incorrect and massive receiving bit
errors and pointer justification events occur. As a result, the services are unavailable.
Possible Causes
The possible cause of the EXT_SYNC_LOS alarm is as follows:
l
The signal is lost at the physical external clock source interface.
Procedure
Step 1 Check whether the cable connection for inputting the external clock is abnormal, the cable
connector is loose, and the cable break occurs.
Step 2 If yes, remove the fault of the cable. View alarms on the U2000 to check whether the
EXT_SYNC_LOS alarm is cleared.
5-108

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
Step 3 Check whether the external clock device operates normally. If not, replace it.
----End
Related Information
None.
5.2.59 FAN_AGING
Description
The FAN_AGING is an alarm of the aged fan. This alarm occurs when the fan rotates at a speed
lower than 80% of the rated value.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the number of the alarmed fan.

When the alarm occurs, the temperature of the NE is too high and impacts the long-term operation
of the NE.
Possible Causes
The possible cause of the FAN_AGING alarm is as follows:
l
Issue 02 (2011-06-30)
The fan is aged.

5-109

System
5 Alarm Reference
Procedure
Step 1 Change the fan.
----End
Related Information
None
5.2.60 FAN_FAIL
Description
Indicates that fans of the NE fail.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Name
Meaning
Parameter 1
Indicates the number of faulty fans.
Parameter 2
Indicates the number of the faulty fan.

The alarm indicates that the fan is faulty and thus causes the problem of heat dissipation, as a
result, the system is affected.
Possible Causes
The possible causes of the FAN_FAIL alarm are as follows:
l
The fan module is not installed or not properly inserted.
The fan module fails.
Procedure
Step 1 Check the installation and work status of fans. If fans are not properly installed, install them
again.
Step 2 Check whether the fuse on the fan board melts down. If it melts down, replace it with a new one.
5-110

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 3 Check whether a fan module of a subrack is faulty. If it is faulty, replace it with a new one.
----End
Related Information
None.
5.2.61 FCS_ERR
Description
The FCS_ERR indicates that bit errors are detected in the FCS check for the local link
encapsulation protocol.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 2, Parameter 3 Indicates the path number.

None
Possible Causes
The possible causes of the FCS_ERR alarm are as follows:
l
Check whether link protocol configurations of two ends are consistent.
The bit errors of the SDH side occur.
Issue 02 (2011-06-30)

5-111

System
5 Alarm Reference
Procedure
Step 1 Check the configuration of the link protocol. If the protocols or parameters at two sides are
different, reconfigure the values.
Step 2 For the bound physical path, check whether any SDH alarm exists. If these alarms occur, follow
relevant troubleshooting steps to clear them.
Step 3 Configure the cross-connect loopback to check whether the alarm is cleared. If the alarm persists,
it indicates that the board of the local station is faulty. If the alarm is cleared, it indicates that
the opposite board is faulty. Replace the faulty board.
----End
Related Information
None
5.2.62 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the receive traffic of the port exceeds the limit.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1
Indicates the IP port number.

NOTE
If Parameters 1 is in the value of 0xff, the number of timslots that are bound
with VC-3 or VC-12 exceeds the value specified in the specifications of the
product.
Parameter 2, Parameter 3 Optical port ID, and the value is always 0x01.
NOTE
If Parameters 3 is in the value of 0xff, the number of timslots that are bound
with VC-3 or VC-12 exceeds the value specified in the specifications of the
product.
5-112

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 4, Parameter 5 Exceeds the value of the traffic, with the unit of Mbit/s
NOTE
If Parameters 4 and 5 are in the value of 0xff, the number of timslots that
are bound with VC-3 or VC-12 exceeds the value specified in the
specifications of the product.

None
Possible Causes
The possible causes of the FLOW_OVER alarm are as follows:
l
When the received traffic is greater than the port threshold, the alarm is reported.
Procedure
Step 1 None
----End
Related Information
None.
5.2.63 HARD_BAD
Description
The HARD_BAD is an alarm indicating board hardware failure.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-113

System
5 Alarm Reference
Name
Meaning
Parameter 1
Indicates the alarm cause.

l 0x10: A component is faulty.
l 0x14: A power component is faulty.
l 0x30: Some firmware is lost.
5-114

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 2, Parameter 3 Identify the alarm cause with Parameter 1.

When the value of Parameter 1 is 0x01:
l Parameter 2 = 0x01: The FPGA chip is faulty.
l Parameter 2 = 0x02: The SA82137 chip is faulty.
l Parameter 2 = 0x03 and Parameter 3 = 0x01: The first SA528
chip is faulty.
l Parameter 2 = 0x03 and Parameter 3 = 0x02: The second SA528
chip is faulty.
l Parameter 2 = 0x10 and Parameter 3 = 0x00: The 1.2 V power
supply is under-voltage.
l Parameter 2 = 0x05 and Parameter 3 = 0x01: The 5 V power
supply is over-voltage.
l Parameter 2 = 0x05 and Parameter 3 = 0x02: The 5 V power
l Parameter 2 = 0xff and Parameter 3 = 0xff: The 32 MHz PLL
is unlocked.
l Parameter 2 = 0x00 and Parameter 3 = 0x0c: Reading a
temperature value fails.
l Parameter 2 = 0x01: Driver files on the board side are lost.
l Parameter 2 = 0x02: FPGA files on the board side are lost.
l Parameter 2 = 0x01: Driver files on the board side fail to be
loaded.
When the value of Parameter 1 is 0xff:
l Parameter 2 = 0x03: Driver files on the board or NE side fail to
be loaded.
Issue 02 (2011-06-30)

5-115

System
5 Alarm Reference

When the HARD_BAD alarm occurs, 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:
l
Driver files of the board are lost or not loaded.
FPGA files of the board are lost or not loaded.
Procedure
Step 1 Check the alarm parameters on the NMS, and determine the ID of the lost file according to the
parameter.
If...
Then...
Driver files of the board are lost
Reload the lost Driver files. After loading the

file, reset the board. Check whether the alarm
step.
FPGA files of the board are lost
Reload the lost FPGA files. After loading the

file, reset the board. Check whether the alarm
step.
No file is lost
Step 2 Replace the faulty board and the alarm is cleared automatically.
----End
Related Information
None.
5.2.64 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that the performance of the higher-order path crosses
the threshold.
5-116

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1, Parameter 2 The higher two bits of Parameter 1 indicate the performance
monitoring period.
l 0x01: 15-minute performance monitoring
l 0x02: 24-hour performance monitoring
NOTE
The lower six bits of Parameter 1 together with Parameter 2 indicate the
performance event ID.

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.
The receive optical power on the line board at the local station is over high or over low.
The clock performance at the opposite station is degraded.
The fiber performance is degraded.
Procedure
Step 1 Check whether the laser performance on the line board at the opposite station is degraded.
Issue 02 (2011-06-30)
If...
Then...
The laser performance is degraded
Replace the laser with a functioning one.
The laser performance is proper

5-117

System
5 Alarm Reference
Step 2 After ensuring the clock tracing setting of the entire network, wait until the set performance
monitoring period ends. View alarms on the U2000 to check whether the HP_CROSSTR alarm
is cleared.
If...
Then...
The alarm persists
Step 3 Check whether the receive optical power on the line board at the local station is over high or
over low.
If...
Then...
The receive optical power is over high
Use the optical power attenuator to decrease

the value of the receive optical power. Then,
check whether the alarm is cleared. If the
The receive optical power is over low
Increase the value of the input optical power.

Then, check whether the alarm is cleared. If
The alarm persists
If...
Then...
The higher-order adaptation performance

event is reported on the board at the opposite
station
The clock board of the remote station is

faulty, replace the SCC board of the remote
station.

event is reported on the board at the local
station
The clock board of the local station is faulty,

replace the SCC board of the local station.
Step 5 Check whether the fiber performance is degraded.

If...
Then...
The fiber performance is degraded
Replace the fiber.
The fiber performance is proper

----End
Related Information
None.
5-118

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.65 HP_LOM
Description
The HP_LOM is an alarm indicating higher order path loss of multiframe.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Optical interface number.
Parameter 4
The value is always 0xff, and this parameter is unused.
Parameter 5

When the HP_LOM alarm occurs, it indicates that the values of the H4 bytes in the payload is
inconsistent with the expected values in several consecutive basic frames in the multiframe
sequence. The multiframe indication of the VC-12 services is lost. As a result, the VC-12 services
are unavailable.
When the HP_LOM alarm occurs, the board will insert VTAIS (TU_AIS for tributary services)
into the corresponding path.
Possible Causes
The possible causes of the HP_LOM alarm are as follows:
l
The H4 byte is lost or the H4 byte value is invalid.
Issue 02 (2011-06-30)

5-119

System
5 Alarm Reference
Procedure
Step 2 View alarms on the NMS to check whether the HP_LOM alarm is cleared.
If...
Then...
This alarm is cleared
This alarm persists
Step 3 Check whether the cross-connect unit and the line board are faulty. You can employ the optical
path self-loop method to check whether any hardware of the opposite station is faulty. If the
fault is located on the opposite station. Replace the line board first and then the SCC board of
the opposite station.
Step 4 View alarms on the NMS to check whether the HP_LOM alarm is cleared.
If...
Then...
This alarm persists
Step 5 Ensure the local station is faulty. Replace the faulty board.
----End
Related Information
None
5.2.66 HP_R_FIFO
Description
The HP_R_FIFO is an alarm indicating that the FIFO overflow on the HP receiving side.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
5-120

Issue 02 (2011-06-30)

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the HP_R_FIFO alarm occurs, the FIFO at the receive side of the higher order path of the
line board overflows. Accordingly, the services cannot be normally received and the service
interruption may occur.
Possible Causes
The possible causes of the HP_R_FIFO alarm are as follows:
l
The frequency difference between the performance of the received and transmitted clocks
is over great.
Procedure
Step 1 Check the settings of the service clock and the system clock. Modify the incorrect clock
configuration.
----End
Related Information
None
5.2.67 HP_RDI
Description
The HP_RDI is an alarm indicating that the local station receives the remote defect indication
in the higher order path sent from the opposite station
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 02 (2011-06-30)

5-121

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

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 opposite line receives the AU_AIS/AU_LOP/HP_TIM/HP_SLM alarms.
The receive part at the opposite station is faulty.
The transmit part at the local station is faulty.
Procedure
Step 1 View the alarms of the NE on the NMS and check whether there are higher order alarms.
If...
Then...
The AU_AIS, AU_LOP, HP_TIM, and

HP_SLM alarms occur

The AU_AIS, AU_LOP, HP_TIM, and

HP_SLM alarms do not occur
Step 2 View alarms on the NMS to check whether the HP_RDI alarm is cleared.
5-122
If...
Then...

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
This alarm persists
If...
Then...
The board at the opposite station reports the The transmit end of the board at the opposite
HP_RDI alarm
The board at the local station reports the
HP_RDI alarm

----End
Related Information
AU_AIS, AU_LOP, HP_TIM, HP_SLM
5.2.68 HP_REI
Description
The HP_REI is an alarm indicating that the local station receives the remote bit error in the
higher-order path sent from the opposite station.
Attribute
Alarm Severity
Alarm Type
Warning
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Issue 02 (2011-06-30)

5-123

System
5 Alarm Reference
Name
Meaning
Parameter 5

When the HP_REI alarm occurs, it indicates that the services received by the opposite station
have the higher-order B3 errored blocks. As a result, the HP_REI alarm is sent to the local station.
Possible Causes
The possible cause of the HP_REI alarm is as follows:
The B3 bit errors are received at the opposite station.
Procedure
Step 1 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.
If...
Then...
The equipment is poorly grounded.
Ground the equipment properly. Check

There is a strong interference source around

the equipment.
Remove the interference source, or install the

equipment at a position far away from the
interference source. Check whether the alarm
step.
The equipment is properly grounded, and

there is no interference source around the
equipment.
Step 2 Perform the loopback for the stations at two ends of the line. Check whether the cross-connect
and timing unit and the tributary board on both the opposite equipment and local equipment
operate normally. Following the service direction, check upstream stations one by one. Locate
the faulty board.
If...
Then...
The board at the opposite station reports B3

bit errors
The receive part at the opposite station is

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

errors
The transmit part of the board at the local

----End
5-124

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None.
5.2.69 HP_SLM
Description
The HP_SLM is an alarm indicating the mismatch of the higher-order path signal label (C2)
received by the line board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

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 line board reports the HP_RDI alarm to the opposite station
if the function of inserting an AIS alarm to the HP_SLM alarm is enabled.
Possible Causes
The possible causes of the HP_SLM alarm are as follows:
The signal label C2 byte expected to be received by the local station is inconsistent with that
transmitted by the opposite station.
Issue 02 (2011-06-30)

5-125

System
5 Alarm Reference
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 NMS to check whether the HP_SLM alarm is cleared.
If...
Then...
The alarm persists
Step 3 View alarms on the NMS to check whether the HP_SLM alarm is cleared.
If...
Then...
The alarm persists
Step 4 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
If...
Then...
The board at the opposite station reports the The receive part at the opposite station is
HP_SLM alarm
board and SCC board.
The board at the local station reports
HP_SLM bit errors
The receive part of the board at the local

----End
Related Information
None.
5.2.70 HP_T_FIFO
Description
The HP_T_FIFO is an alarm indicating the FIFO overflow at the transmit side of the line higher
order path.
5-126

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the HP_T_FIFO alarm occurs, the FIFO at the transmit side of the higher order path of
the line board overflows. Accordingly, the services cannot be normally transmitted and the
service interruption may occur.
Possible Causes
The possible causes of the HP_T_FIFO alarm are as follows:
l
The frequency difference between the performance of the received and transmitted clocks
is over great.
Procedure
Step 1 Check the settings of the serivce clock and the system clock. Modify the incorrect clock
configuration.
----End
Related Information
None
5.2.71 HP_TIM
Issue 02 (2011-06-30)

5-127

System
5 Alarm Reference
Description
The HP_TIM is an alarm indicating the mismatch of the higher-order path trace identifier (J1)
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

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_SLM alarm occurs, the line board reports the HP_RDI alarm to the opposite station
if the function of inserting an AIS alarm to the HP_TIM alarm is enabled.
Possible Causes
The possible causes of the HP_TIM alarm are as follows:
5-128
The path trace identifier J1 byte expected to be received by the local station is inconsistent
with that transmitted by the opposite station.

Issue 02 (2011-06-30)

System
5 Alarm Reference
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 NMS to check whether the HP_TIM alarm is cleared.
If...
Then...
The alarm persists
Step 4 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
If...
Then...
The board at the opposite station reports the The receive part at the opposite station is
HP_TIM alarm
board and SCC board.
The board at the local station reports
HP_TIM bit errors

----End
Related Information
None
5.2.72 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the higher-order path received by the line board is
unloaded.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
Issue 02 (2011-06-30)

5-129

System
5 Alarm Reference

table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

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 alarm are as follows:
l
The value of the C2 byte transmitted by the opposite NE is not 0x00.
The opposite NE is not configured with services.
Procedure
Step 1 Check the C2 byte configuration of the opposite NE to see whether the C2 byte has sent UNEQ.
If the configuration is incorrect, modify and re-issue the configuration.
Step 2 Check whether the line board of the opposite NE is configured with services in the transmitting
direction. If not, re-configure the services of the NE.
Step 3 View alarms on the NMS to check whether the HP_UNEQ alarm is cleared.
If...
Then...
The alarm persists
Step 4 The board at the local station is faulty. Replace the faulty board.
----End
Related Information
None.
5.2.73 HPAD_CROSSTR
5-130

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The HPAD_CROSSTR is an alarm indicating that the performance of the higher-order path
adaptation crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
None.

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 clock fails.
The laser performance on the line board at the opposite station is degraded.
The receive optical power on the line board at the local station is higher or lower than
expected value.
Procedure
Step 1 Check whether the clock tracing on the local station or in the entire network is correctly set. If
the setting is not correct, reset the clock tracing.
Step 2 After verifying the clock tracing settings are correct, wait until the set performance monitoring
period ends. View alarms on the NMS to check whether the HPAD_CROSSTR alarm is cleared.
If...
Then...
The alarm persists
Issue 02 (2011-06-30)

5-131

System
5 Alarm Reference
If...
Then...

event is reported on the board at the opposite
station
The clock board of the remote station is

faulty, replace the clock unit of the remote
station. Check whether the alarm is cleared.

event is reported on the board at the local
station
The clock board of the local station is faulty,

replace the SCC board of the local station.
Step 4 Check whether the optical attenuator does not match or is faulty, or whether the fiber is broken.
If...
Then...
The optical attenuator does not match or is

faulty
Replace the optical attenuator with a

functioning one. Then, check whether the
the next step.
The fiber is broken
Replace the fiber with a functioning one.

Then, check whether the alarm is cleared. If
The optical attenuator and fiber work

properly

----End
Related Information
None.
5.2.74 HSC_UNAVAIL
Description
The HSC_UNAVAIL is an alarm indicating an abnormal hot-backup state.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
5-132

Issue 02 (2011-06-30)

System
5 Alarm Reference

table.
Name
Meaning
Parameter 1
Indicates the working/protection status of the

available board.
Parameter 2
Indicates the slot number of the unavailable board.
Parameter 3, Parameter 4 and Parameter 5 0xff.

When the HSC_UNAVAIL alarm occurs, the services may be interrupted when the working/
protection boards are switched.
Possible Causes
The possible cause of the HSC_UNAVAIL alarm is as follows:
The hot switching control function fails.
Procedure
Step 1 Check on the NMS whether the HSC_UNAVAIL alarm is reported. If the HSC_UNAVAIL
alarm is reported, replace the board with a proper one.
----End
Related Information
None.
5.2.75 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power of the line board laser
crosses the lower or upper threshold.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Issue 02 (2011-06-30)

5-133

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

When the IN_PWR_ABN alarm occurs, the receive power of the laser is abnormal. As a result,
the bit errors may occur in the transmitted services or the service signals cannot be aligned.
Possible Causes
The possible causes of the IN_PWR_ABN alarm are as follows:
l
The optical power is higher or lower than the expected value.
The fiber head is dirty or the fiber connector type is incorrect.
The detector or amplifying circuit fails.
Procedure
Step 1 Check the input optical power of the line board. Take different actions according to different
optical power.
If...
Then...
The optical power is over high
Increase the attenuation of the signal

transmission line.
Decrease the attenuation of the signal

transmission or increase the opposite transmit
optical power.
Step 2 Replace the optical module with a functioning one. Then, check whether the alarm is cleared.
If...
Then...
The alarm persists
Replace the board.
----End
5-134

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None.
5.2.76 INTEMP_SENSOR_FAIL
Description
The INTEMP_SENSOR_FAIL is an alarm indicating that the inlet temperature sensor fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

If this alarm is reported, the equipment cannot collect the temperature data of the air inlet on the
TCU.
Possible Causes
The possible causes of the INTEMP_SENSOR_FAIL alarm are as follows:
l
The inlet temperature sensor is not installed.
The inlet temperature sensor is incorrectly connected.
The inlet temperature sensor is faulty.
Procedure
Step 1 Check whether the inlet temperature sensor is installed.
If...
Then...
The inlet temperature sensor is not installed Install the inlet temperature sensor correctly.
The inlet temperature sensor is installed
Step 2 Check on the NMS whether the INTEMP_SENSOR_FAIL alarm is cleared. If the
INTEMP_SENSOR_FAILL alarm persists, check whether the inlet temperature sensor is
Issue 02 (2011-06-30)

5-135

System
5 Alarm Reference
If...
Then...
The inlet temperature sensor is incorrectly

connected
The inlet temperature sensor is correctly

Step 3 Check on the NMS whether the INTEMP_SENSOR_FAIL alarm is cleared. If the
INTEMP_SENSOR_FAIL alarm persists, replace the inlet temperature sensor with a proper
one.
Step 4 If the INTEMP_SENSOR_FAIL alarm persists after the inlet temperature sensor is replaced,
----End
Related Information
None.
5.2.77 J0_MM
Description
The J0_MM is an alarm indicating the mismatch of the regenerator section trace identifier (J0)
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
5-136
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
5 Alarm Reference

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.
Procedure
Step 1 Check on the U2000 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 U2000 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 still reports the J0_MM alarm.
----End
Related Information
None
5.2.78 K1_K2_M
Description
The K1_K2_M is an alarm indicating the mismatch between the transmitted K1 byte and
received K2 byte in a linear MSP group.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
Issue 02 (2011-06-30)

5-137

System
5 Alarm Reference

table.
Name
Meaning
Parameter 1
Indicates the multiplex section type.

l Linear MSP: 0x01
Parameter 2

When the K1_K2_M alarm occurs, the transmitted K1 byte and received K2 byte of the linear
MSP group mismatch. This may cause the failure in the automatic protection switching and
therefore the interruption of the protected services.
Possible Causes
The possible causes of the K1_K2_M alarm are as follows:
l
The numbers of the channels through which the K1 byte is transmitted and the K2 byte is
received are inconsistent for a certain period (160 ms by default).
The types of the MSP group at two stations are not consistent
The fault occurs on the line board when it transmits or receives the K byte.
Procedure
Step 1 Check whether the MSP group types of two stations that form an MSP group are consistent.
Check whether they are both of the 1+1 or 1:N MSP group. If not, modify them to be consistent.
Step 2 If the MSP protocol at two stations is stopped, start the MSP protocol of the protection group
again.
Step 3 View alarms on the U2000 to check whether the K1_K2_M alarm is cleared.
If...
Then...
Step 4 If the alarm persists, replace the line board in the protection channel.
----End
Related Information
None.
5-138

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.79 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
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

l Linear MSP: 0x01
Parameter 2

When the K2_M alarm occurs, the mismatch between the transmitted K1 byte and received K2
byte of a linear MSP occurs. 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 fifth bit (from the most significant bit to the least significant bit) of the transmitted K2
byte is inconsistent with that of the received K2 byte for a certain period (2s by default).
The types of the MSP group at two stations are not consistent
The fault occurs on the line board when it transmits or receives the K byte.
Issue 02 (2011-06-30)

5-139

System
5 Alarm Reference
Procedure
Step 1 Check whether the MSP group types of two stations that form an MSP group are consistent.
Check whether they are both of the 1+1 or 1:N MSP group. If not, modify them to be consistent.
Step 2 If the MSP protocol at two stations is stopped, start the MSP protocol of the protection group
again.
Step 3 View alarms on the U2000 to check whether the K2_M alarm is cleared.
If...
Then...
Step 4 If the alarm persists, replace the line board in the protection channel.
----End
Related Information
None.
5.2.80 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that a port in the LAG fails. When a port in the
LAG is unavailable, the LAG_PORT_FAIL alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
table.
5-140
Name
Meaning
Parameter 1
Indicates the IP port number.

Issue 02 (2011-06-30)

System
Name
Meaning
Parameter 4
Indicates the cause of the protection failure.
5 Alarm Reference
l 0x01: The port is disabled or link down occurs on the port.

l 0x02: The port works in half-duplex mode.
l 0x03: The port fails to receive the LACP packets.
l 0x04: The port is self-looped.
l 0x05: Other unknown reasons.
0xff
Parameter 5

The port in the LAG cannot balance the service load, and the port does not transmit or receive
any services.
Possible Causes
The possible causes of the LAG_PORT_FAIL alarm are as follows:
l
The port is not enabled.
The link of the port is faulty.
The port is in half-duplex mode.
The port fails to receive the LCAP packets.
A self-loop is detected at the port.
Other unknown reasons.
Procedure
Step 1 View the alarm on the U2000, and confirm the board where the LAG_PORT_FAIL alarm is
generated. Confirm the number of the MAC port where the LAG_PORT_FAIL alarm is
generated according to Parameter 1, and confirm the cause of the LAG_PORT_FAIL alarm at
the port according to Parameter 4.
Step 2 If the value of Parameter 4 is 0x01, the link fails or is faulty.
1.
On the U2000, check whether the port in the LAG is enabled. If the port is not enabled,
enable the port and then check whether the alarm is cleared.
2.
Check the status of each port. Then, rectify the link fault of each port to check whether the
alarm is cleared.
Step 3 If the value of Parameter 4 is 0x02, check the working mode of the port in the LAG on the
U2000. If the port is in half-duplex mode, change the working mode of the port to full-duplex,
and then check whether the alarm is cleared automatically.
Step 4 If the value of Parameter 4 is 0x03, the port fails to receive the LACP packets.
1.
Issue 02 (2011-06-30)
On the U2000, check whether the LAG is configured at the opposite end, and check whether
the port connected to the faulty port is added to the LAG at the opposite end. Make sure
that the LAG is correctly configured, and then check whether the alarm is cleared.
5-141

System
5 Alarm Reference
2.
Check whether the local port transmits packets. If both ends can normally transmit and
receive packets, check whether the alarm is cleared.
Step 5 If the value of Parameter 4 is 0x04, the port is in the self-loop state. Release the self-loop, and
then check whether the alarm is cleared.
Step 6 If the value of Parameter 4 is 0x05, determine the cause according to the networking
environment, and then check whether the alarm is cleared.
----End
Related Information
None.
5.2.81 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the user issues the command of shutting down
the laser, and the laser of the line board is in the close status.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

The user issues the command of shutting down the laser, and the laser of the line board is in the
close status, which will affect the transmit and receive of the line board.
Possible Causes
The possible causes of the LASER_CLOSED alarm are as follows:
l
5-142
The user shuts down the laser through NMS or Navigator.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 The user disables the laser shutdown function through NMS or Navigator, or waits for the auto
start of the laser (five minutes after the laser is shut down)
----End
Related Information
None
5.2.82 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating mismatch of optical modules. When the type
of the optical module inserted does not match the type supported by the board, this alarm occurs.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Name
Meaning
Parameter 1

When the installed optical module is incorrect, the performance of the optical interface is
degraded. In severe cases, the services are interrupted.
Possible Causes
The possible causes of the LASER_MOD_ERR alarm are as follows:
l
The rate of the optical module inserted does not match the rate of the optical interface of
the board.
The type of the inserted optical module and the type of the port on the actual board
mismatch.
The optical module is faulty
Board failure occurs
Procedure
Step 1 View the LASER_MOD_ERR alarm on the NMS and confirm the relevant board.
Issue 02 (2011-06-30)

5-143

System
5 Alarm Reference
Step 2 Replace the faulty optical module.

If...
Then...
This alarm persists
Step 3 Refer to Parts Replacement. Replace the board that reports the alarm.
----End
Related Information
None
5.2.83 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR_EX is an alarm indicating that the pluggable optical module on the
line board does not match the optical port of the line board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

When the LASER_MOD_ERR_EX alarm occurs, it indicates that the pluggable optical module
installed on the line board does not match the optical port rate of the line board. The line board
will transmit/receive services abnormally.
Possible Causes
The possible causes of the LASER_MOD_ERR_EX alarm are as follows:
5-144

Issue 02 (2011-06-30)

System
5 Alarm Reference
The optical module installed in the optical port of the line board is of a wrong type.
The optical module or line board is faulty.
Procedure
Step 1 Check whether the optical module installed on the line board is of the correct type. If not, replace
it with the correct one.
Step 2 Check whether the LASER_MOD_ERR_EX alarm is cleared on the U2000.
If...
Then...
This alarm persists
Step 3 If the alarm still persists, the optical module or line board must be faulty. Replace the optical
module or the line board.
CAUTION
For the optical module with pluggable line boards, hot swap is supported.
----End
Related Information
None
5.2.84 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the protocol failure in the LCAS receive direction.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Issue 02 (2011-06-30)

5-145

System
5 Alarm Reference
Name
Meaning
Parameter 1
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.

The LCAS protection does not work.
Possible Causes
The possible causes of the LCAS_FOPR alarm are as follows:
l
The downlink VCG receives SQ repeatedly due to incorrect configuration or link bit errors.
The LCAS function of the opposite VCG is disabled.
The downlink VCG simultaneously receives the FIXED and other LCAS control bytes due
to incorrect configuration or bit errors in the link.
Procedure
Step 1 Check the service configurations of the local and opposite station. Check whether the bound
timeslots of the VCTRUNK are consistent. If any error exists, reconfigure the values.
Step 2 Check whether the LCAS is enabled at the opposite station. If not, enable the LCAS.
----End
Related Information
None
5.2.85 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the protocol failure in the LCAS transmit direction.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
5-146

Issue 02 (2011-06-30)

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1

The LCAS protection does not work.
Possible Causes
The possible causes of the LCAS_FOPT alarm are as follows:
l
There is the persistent and unexpected MST due to incorrect configuration or bit errors in
the link. For example, the member that transmits the IDLE always receives MST=OK.
Procedure
paths of the VCTRUNK are consistent. If any error exists, reconfigure the values.
Step 2 Check whether the path bound with the VCTRUNK reports SDH alarms. If any alarm is reported,
see the handling procedure of the corresponding alarm.
----End
Related Information
None
5.2.86 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating the loss of partial bandwidth in the LCAS receive
direction.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
Issue 02 (2011-06-30)

5-147

System
5 Alarm Reference

table.
Name
Meaning
Parameter 1

Partial configured paths are used in the receiving direction, as a result, the available bandwidth
decreases.
Possible Causes
The possible causes of the LCAS_PLCR alarm are as follows:
l
When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the
number of paths that carry load is less than the number of paths configured and is not zero.
Procedure
Step 2 Check whether the unequipped path reports SDH alarms. If yes, see the handling procedure of
the corresponding alarm.
----End
Related Information
None
5.2.87 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating the loss of partial bandwidth in the LCAS transmit
direction.
Attribute
5-148
Alarm Severity
Alarm Type
Minor

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

Partial paths are used in the transmit direction, as a result, the available bandwidth decreases.
Possible Causes
The possible causes of the LCAS_PLCT alarm are as follows:
l
When the LCAS function of the VCTRUNK is enabled, in the receive direction, the number
of paths that carry load is less than the number of paths configured and is not zero.
Procedure
Step 2 Check whether the unequipped path reports SDH alarms. If yes, see the handling procedure of
----End
Related Information
None
5.2.88 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating the loss of all bandwidth in the LCAS receive direction.
Attribute
Alarm Severity
Alarm Type
Major
Issue 02 (2011-06-30)

5-149

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

The paths configured in the receive direction are not used, so the available bandwidth is zero.
Possible Causes
The possible causes of the LCAS_TLCR alarm are as follows:
l
When the LCAS function of the VCTRUNK is enabled, in the receive direction, the number
of paths that carry load is zero, whereas the number of paths configured is not zero.
Procedure
Step 2 Check whether the configured path reports SDH alarms. If yes, see the handling procedure of
----End
Related Information
None
5.2.89 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating the loss of all bandwidth in the LCAS transmit direction.
Attribute
5-150
Alarm Severity
Alarm Type
Major

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

The paths configured in the transmit direction are not used, so the available bandwidth is zero.
Possible Causes
The possible causes of the LCAS_TLCT alarm are as follows:
l
When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the
number of paths that carry load is zero, whereas the number of paths configured is not zero.
Procedure
Step 2 Check whether the configured path reports SDH alarms. If yes, see the handling procedure of
----End
Related Information
None
5.2.90 LCS_DAYS_OF_GRACE
Description
The LCS_DAYS_OF_GRACE is an alarm indicating that a License file remains in the grace
period. This alarm is reported when the License file is ineffective, the version does not match,
or a feature expires but remains in the grace period of the License file.
Issue 02 (2011-06-30)

5-151

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1, Parameter 2 Indicates the ID of the feature.

Parameter 3, Parameter 4 Indicates the number of remaining days in the grace period of the
License file.
Parameter 5
Indicates the failure type.

l 0x01: The License file is ineffective.
l 0x02: The Equipment Serial Number (ESN) specified in the
License file does not match the ESN of the equipment.
l 0x03: The V/R version of the License file does not match the
software version of the equipment.
l 0x04: Both the ESN and V/R version do not match.
NOTE
l If the values of Parameters 1 and 2 are not zero, the value of Parameter
5 is always zero.
l If the value of Parameter 5 is not zero, the values of Parameters 1 and 2
are always zero.

If a License file is not replaced in the grace period, the system or feature changes to the default
state when the License file expires.
Possible Causes
The possible causes of the LCS_DAYS_OF_GRACE alarm are as follows:
5-152
The License file is ineffective, and the NE remains in the grace period of 60 days.
The License file, ESN, or V/R version does not match, and the NE remains in the grace
period of 60 days.
The feature expires but remains in the grace period of 60 days.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 Contact Huawei engineers to install a correct License file on the NE.
----End
Related Information
None.
5.2.91 LCS_EXPIRED
Description
The LCS_EXPIRED is an alarm indicating that a license file expires. This alarm is reported
when a license file is beyond its probation period.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1, Parameter 2 Indicates the number of days after the license file expires.
Parameter 3
Indicates the failure type.

l 0x01: The license file is ineffective.
l 0x02: The Equipment Serial Number (ESN) specified in the
license file dose not match the ESN of the equipment.
l 0x03: The V/R version of the license file dose not match the
software version of the equipment.
l 0x04: Both the ESN and V/R version do not match.

If the license file is running after the grace period expires, the equipment changes to the default
state in which a minimum of functions are available.
Issue 02 (2011-06-30)

5-153

System
5 Alarm Reference
Possible Causes
The possible causes of the LCS_EXPIRED alarm are as follows:
l
The license file is ineffective, and the NE operates continuously beyond the probation
period of the license file.
The license file, ESN, or V/R version does not match, and the NE operates continuously
beyond the probation period of the license file.
Procedure
Step 1 Contact Huawei engineers to install a correct license file on the NE.
----End
Related Information
None.
5.2.92 LCS_FILE_NOT_EXIST
Description
The LCS_FILE_NOT_EXIST is an alarm indicating that the License file is not installed on the
NE. This alarm is reported when the equipment is under control of a License file but is not
installed with the relevant License file.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None.

If the equipment is not installed with the relevant License file, the equipment may change to the
default state.
Possible Causes
The possible cause of the LCS_FILE_NOT_EXIST alarm is as follows:
l
The equipment is started up, but the relevant License file does not exist in the system.
Procedure
Step 1 Contact Huawei engineers to install a correct License file on the NE.
----End
5-154

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None.
5.2.93 LINK_ERR
Description
The LINK_ERR is an alarm indicating that the data link is incorrect. This alarm is reported when
the Ethernet connection is incorrect and the port negotiation fails.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the optical interface number of the board.
Indicates the port number of the board.

When the LINK_ERR alarm is reported during the data transmission, the network port
negotiation fails. The data cannot be received and the services are interrupted.
Possible Causes
The possible causes of the LINK_ERR alarm are as follows:
l
The working mode of the port at the transmit end is inconsistent with the working mode of
the port at the receive end. Hence, the negotiation fails.
The link is faulty.
The cable and fiber are connected improperly, or the equipment at the opposite end is faulty.
Procedure
Step 1 View the alarm on the U2000 to determine the relevant board. Then, determine the number of
the port on the board according to Parameter 1.
Issue 02 (2011-06-30)

5-155

System
5 Alarm Reference
Step 2 Check whether the working mode of the local port is consistent with that of the opposite port.
If the working modes are different, change the working modes to ensure consistency at two sides.
Then, check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the cable or fiber connection is faulty. If yes, rectify the fault
of the cable or fiber connection, and then check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the opposite equipment is faulty. If yes, replace the faulty
board at the opposite station, and then check whether the alarm is cleared.
Step 5 If the alarm persists, replace the board that generates the alarm. Make sure that the working
mode of the port at the local end is consistent with that of the port at the opposite end. Then, the
alarm is cleared automatically.
----End
Related Information
None
5.2.94 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that loopback alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the loopback mode.

l 0x00: optical/electrical port inloop
l 0x01: optical/electrical port outloop
l 0x02: path inloop
l 0x03: path outloop
5-156

Issue 02 (2011-06-30)

System
5 Alarm Reference

The alarm indicates that the loopback is set at the optical port or path of the line or tributary
board. If the setting is not cancelled, the services will be affected.
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
l
Inloop or outloop is performed for the board.
Procedure
Step 1 Set the line board to non-loop.
----End
Related Information
None.
5.2.95 LP_CROSSTR
Description
The LP_CROSSTR is an alarm indicating that the number of the lower order path bit errors
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None.

The impacts of the LP_CROSSTR alarm on the system are as follows:
l
The service quality of the services of the board that reports the alarm is downgraded.
The services of the board that reports the alarm are interrupted.
Possible Causes
The possible causes of the LP_CROSSTR alarm are as follows:
l
The laser performance at the opposite station is degraded.
the received optical power at the local station is over high or over low.
Issue 02 (2011-06-30)

5-157

System
5 Alarm Reference
The clock performance at the local station or the opposite station is degraded.
The fiber performance is degraded.
Procedure
Step 1 Perform an inloop on the board that reports the LP_CROSSTR alarm at the local station.
CAUTION
The loopback causes service interruption.
1.
If the alarm is cleared, go to Step 2.
2.
If the alarm persists, it indicates that the fault occurs to the local station. Go to Step 4.
Step 2 Perform an outloop at the opposite station.
CAUTION
1.
If the alarm is cleared, it indicates that the fault occurs to the opposite station. Go to Step
3.
2.
If the alarm persists, it indicates that the fiber performance is degraded or the fiber jumper
connector is dirty. Go to Step 5.
Step 3 Replace the line board at the opposite station.

1.
If the alarm is cleared, the fault is removed. The alarm handling ends.
2.
If the alarm persists, replace the cross-connect and timing board at the opposite station. The
alarm handling ends.
Step 4 Replace the board that reports the LP_CROSSTR alarm at the local station.
1.
2.
If the alarm persists, replace the cross-connect and timing board at the local station. The
alarm handling ends.
Step 5 Clean the fiber jumper connectors at both the local and opposite stations.
1.
2.
If the alarm persists, it indicates that the fault occurs to the fiber cables. Remove the fault,
and the alarm handling ends.
----End
Related Information
None
5.2.96 LP_R_FIFO
5-158

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The LP_R_FIFO is an alarm indicating that the FIFO messages on the receive side of the lower
order path overflow.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

When the LP_R_FIFO alarm occurs, bit errors may occur in the path services of the board.
Possible Causes
The possible causes of the LP_R_FIFO alarm are as follows:
l
The service cross-connections are incorrectly configured.
The service type is incorrectly configured.
Procedure
Step 1 View the LP_R_FIFO alarm on the U2000, and then confirm the path number according to the
alarm parameters.
Step 2 Check whether the service configuration of the path is correct. Make sure that the service type
at the local end is consistent with that at the opposite end, and that the cross-connection is
correctly configured. Then the LP_R_FIFO alarm is automatically cleared.
----End
Related Information
None
Issue 02 (2011-06-30)

5-159

System
5 Alarm Reference
5.2.97 LP_RDI
Description
The LP_RDI is an alarm indicating a remote defect in the lower order path of the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

When the LP_RDI alarm occurs, the opposite station receives the TU_AIS or TU_LOP alarm
and then returns the LP_RDI alarm (VC12: V5[b8],VC3: G1[b5]) to the local tributary board.
Possible Causes
The possible causes of the LP_RDI alarm are as follows:
l
The opposite station has received the TU_AIS or TU_LOP alarm.
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...
The TU_AIS or TU_LOP alarm is reported
Refer to 5.2.200 TU_AIS and 5.2.203

TU_LOP to clear the alarm. Check whether
the LP_RDI alarm is cleared. If the alarm
The TU_AIS or TU_LOP alarm is not

reported
Step 2 Replace the faulty board.

----End
Related Information
None.
5-160

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.98 LP_RDI_VC12
Description
The LP_RDI_VC12 indicates a remote defect in the lower order path of the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the LP_RDI alarm occurs, the opposite station receives the TU_AIS, TU_LOP, LP_TIM,
or LP_UNEQ alarm and then returns the LP_RDI alarm (VC12: V5[b8],VC3: G1[b5]) to the
local tributary board.
Possible Causes
The possible cause of the LP_RDI_VC12 alarm is as follows:
l
The opposite station has received the TU_AIS, TU_LOP, LP_TIM, or LP_UNEQ alarm.
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.
Issue 02 (2011-06-30)

5-161

System
5 Alarm Reference
If...
Then...
There is the TU_AIS, TU_LOP, LP_TIM, Refer to the corresponding section in this
or LP_UNEQ alarm
There are no such alarms as the TU_AIS, Proceed to the next step.
TU_LOP, LP_TIM, or LP_UNEQ alarm
Step 2 If there is no alarm or the corresponding alarm is cleared at the opposite station, the
LP_RDI_VC12 alarm persists. The tributary board is faulty. Replace the faulty board.
CAUTION
----End
Related Information
TU_AIS, TU_LOP, LP_TIM, and LP_UNEQ
5.2.99 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating a remote defect in the lower order path of the tributary
board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
5-162
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 4
Parameter 5

When the LP_RDI_VC3 alarm occurs, the opposite station receives the TU_AIS, TU_LOP,
LP_TIM, or LP_UNEQ alarm and then returns the LP_RDI_VC3 alarm (VC-12: V5[b8],VC3:
G1[b5]) to the local tributary board.
Possible Causes
The possible causes of the LP_RDI_VC3 alarm are as follows:
l
The opposite station has received the TU_AIS, TU_LOP, LP_TIM, or LP_UNEQ alarm.
Procedure
Step 1 View alarms of the NE, and check whether there is the TU_AIS, TU_LOP, LP_TIM, or
LP_UNEQ alarm in the corresponding path of the tributary board at the opposite station.
If...
Then...
There is the TU_AIS, TU_LOP, LP_TIM, or

LP_UNEQ alarm

There are no such alarms as the TU_AIS,

TU_LOP, LP_TIM, or LP_UNEQ
Step 2 If there is no alarm or the corresponding alarm is cleared at the opposite station, the
LP_RDI_VC3 alarm persists. The tributary board is faulty. Replace the faulty board.
CAUTION
----End
Related Information
TU_AIS, TU_LOP, LP_TIM, and LP_UNEQ
5.2.100 LP_REI
Issue 02 (2011-06-30)

5-163

System
5 Alarm Reference
Description
The LP_REI is a remote error indication alarm in the lower order path. When a board has detected
that bit 3 of the V5 byte is 1 or any of bits 1 - 4 of the G1 byte is 1, the LP_REI alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

When the LP_REI alarm occurs, the services at the local station are not affected. This alarm just
shows that some bit errors occur in the signals received in the lower order path at the opposite
station.
Possible Causes
The possible cause of the LP_REI alarm is as follows:
l
The LP_REI alarm is an accompanying alarm. When an tributary board at the opposite
station has detected a bit error alarm, such as the BIP_SD, BIP_EXC, B3_SD or B3_EXC,
it returns an LP_REI alarm to the local station.
Procedure
Step 1 According to the procedure of handling the 5.2.26 BIP_SD, 5.2.25 BIP_EXC, 5.2.17 B3_SD
or 5.2.14 B3_EXC alarm, clear the bit error alarm at the opposite station. Then the LP_REI
alarm is automatically cleared.
----End
Related Information
None
5.2.101 LP_REI_VC12
Description
The LP_REI_VC12 is an alarm indicating a remote bit error in the lower order path of the
tributary board.
5-164

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the LP_REI_VC12 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 cause of the LP_REI_VC12 alarm is as follows:
l
Bit errors are received in the lower order path at the opposite station.
Procedure
Step 1 View alarms of the opposite NE, and check whether there is the B3 or BIP bit error alarm.
If...
Then...
There is the B3 or BIP bit error alarm Refer to 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.
source around the equipment. If few B3 or BIP bit errors occur in the remote, the fault usually
Issue 02 (2011-06-30)

5-165

System
5 Alarm Reference
lies in the equipment instead of the optical path. If any interference source exists near the
equipment, change the location.
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
tributary board, line board, and SCC board.
There is the B3 or BIP bit error reported on The transmit end of the board at the local
the local board
CAUTION
----End
Related Information
B3_EXC, B3_SD, BIP_EXC, and BIP_SD
5.2.102 LP_REI_VC3
Description
The LP_REI_VC3 is an alarm indicating a remote bit error in the lower order path of the tributary
board.
Attribute
Alarm Severity
Alarm Type
Minor
Parameters
table.
5-166

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1
Optical port number, fixed as 0x01.
Parameter 4
Parameter 5

When the LP_REI_VC3 alarm occurs, the lower order background block error (BBE) occurs in
the received services at the opposite station and the LP_REI alarm (VC-12: V5[b3], VC3: G1
[b1-b4]) is returned to the local station.
Possible Causes
The possible cause of the LP_REI_VC3 alarm is as follows:
l
Bit errors are received in the lower order path at the opposite station.
Procedure
Step 1 View alarms of the opposite NE, and check whether there is the B3 or BIP bit error alarm.
If...
Then...
There is the B3 or BIP bit error alarm

document to clear the B3_EXC, B3_SD,
BIP_EXC, or BIP_SD alarm.
There is no B3 or BIP bit error alarm
source around the equipment. If few B3 or BIP bit errors occur in the remote, the fault usually
lies in the equipment instead of the optical path. If any interference source exists near the
equipment, change the location.
the faulty board.
Issue 02 (2011-06-30)
If...
Then...
There is the B3 or BIP bit error reported on

the opposite board
The receive end at the opposite station is

faulty. Replace the boards in an order of
tributary board, line board, and SCC board.

5-167

System
5 Alarm Reference
If...
Then...
There is the B3 or BIP bit error reported on

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

CAUTION
----End
Related Information
B3_EXC, B3_SD, BIP_EXC, and BIP_SD
5.2.103 LP_RFI
Description
The LP_RFI is a remote failure indication alarm in the lower order path. If a board has detected
that bit 4 of the V5 byte is 1, the LP_RFI alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

When the LP_RFI alarm occurs, the services at the local station are not affected. This alarm just
shows that the lower order path at opposite station fails to receive signals.
Possible Causes
The possible cause of the LP_RFI alarm is as follows:
The LP_RFI alarm is an accompanying alarm. When a tributary board at the opposite station
has detected the BIP_EXC alarm, it returns an LP_RFI alarm to the local station.
5-168

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 After you clear the 5.2.25 BIP_EXC alarm that occurs at the opposite end, the LP_RFI alarm
is automatically cleared.
----End
Related Information
5.2.25 BIP_EXC
5.2.104 LP_SIZE_ERR
Description
The LP_SIZE_ERR is a TU specification error alarm. When the mapping structure of the TU
services received at the board is inconsistent with that specified for the board, the LP_SIZE_ERR
alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the number of the path on which the alarm occurs.

When the LP_SIZE_ERR alarm occurs, the services in the lower order path are interrupted.
Possible Causes
The possible cause of the LP_SIZE_ERR alarm is as follows:
l
Issue 02 (2011-06-30)
The mapping structure of the lower order services is incorrectly configured.

5-169

System
5 Alarm Reference
Procedure
Step 1 View the LP_SIZE_ERR alarm on the U2000, and then confirm the path number according to
the alarm parameters.
Step 2 After you configure the correct mapping structure of services in the lower order path, the
LP_SIZE_ERR alarm is automatically cleared.
----End
Related Information
None
5.2.105 LP_SLM
Description
The LP_SLM is a signal label mismatch alarm in the lower order path. If a board has detected
that the signal label mismatch event occurs in the V5 or C2 byte, the LP_SLM alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

The system is not affected.
Possible Causes
The possible causes of the LP_SLM alarm are as follows:
l
The signal label configuration for the lower order path at the local station is inconsistent
with that at the opposite station.
The service type is incorrectly configured.
Procedure
Step 1 View the LP_SLM alarm on the U2000 to confirm the relevant board and path.
Step 2 Check whether the signal label byte for the relevant lower order path of the board at the opposite
station is consistent with that at the local station. If not, modify it, and then check whether the
LP_SLM alarm is cleared.
5-170

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 3 If the alarm persists, check whether the service configuration of the board that reports the alarm
is correct. After modifying the incorrect configuration, check whether the LP_SLM alarm is
cleared.
Step 4 If the alarm persists, perform a self-loop on the local station. Perform a loopback to check
whether the board at the local or opposite end is faulty. If the board is faulty, replace it.
----End
Related Information
None.
5.2.106 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating the mismatch of the lower order path signal label
received by the tributary board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the LP_SLM_VC12 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).
Issue 02 (2011-06-30)

5-171

System
5 Alarm Reference
Possible Causes
The possible causes of the LP_SLM_VC12 alarm are as follows:
l
The lower order path signal label to be received at the local station is inconsistent with that
transmitted at the opposite station.
Procedure
Step 1 Check whether the signal label byte to be transmitted by the corresponding lower order path of
the tributary board at the opposite station is configured consistent with that to be received at the
local station. If not, modify them to be consistent and issue the configuration again.
Step 2 View alarms on the NMS to check whether the LP_SLM_VC12 alarm is cleared.
If...
Then...
This alarm persists
----End
Related Information
None
5.2.107 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating the mismatch of the lower order path signal label
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
5-172

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the LP_SLM_VC3 occurs, the mapping structure of the lower order services received on
the tributary board is incorrect. As a result, the services are abnormal (VC-12: V5[b5-b7], VC3:
C2).
Possible Causes
The possible causes of the LP_SLM_VC3 alarm are as follows:
l
The lower order path signal label to be received at the local station is inconsistent with that
transmitted at the opposite station.
Procedure
Step 1 Check whether the signal label byte to be transmitted by the corresponding lower order path of
the tributary board at the opposite station is configured consistent with that to be received at the
local station. If not, modify them to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the LP_SLM_VC3 alarm is cleared.
If...
Then...
----End
Related Information
None
5.2.108 LP_T_FIFO
Issue 02 (2011-06-30)

5-173

System
5 Alarm Reference
Description
The LP_T_FIFO is an alarm indicating that the FIFO messages on the transmit side of the lower
order path overflow.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the number of the path.

When the LP_T_FIFO alarm occurs, bit errors may occur in the path services of the board.
Possible Causes
The possible causes of the LP_T_FIFO alarm are as follows:
l
The service cross-connections are incorrectly configured.
The accessed services are incorrect.
Procedure
Step 1 View the LP_T_FIFO alarm on the U2000. Then check whether the service configuration is
correct for both the board that generates the alarm and the relevant NE. After modifying the
incorrect configuration, check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the services accessed to the board are correct. After making
sure that the accessed services are correct, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the board.
----End
Related Information
None
5-174

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.109 LP_TIM
Description
The LP_TIM is a trace identifier mismatch alarm in the lower order path. If a board has detected
that the J2 or J1 byte does not match, the LP_TIM alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

The system is not affected.
Possible Causes
The possible causes of the LP_TIM alarm are as follows:
l
The trace identifier of the lower order path at the local station is inconsistent with that at
the opposite station.
The service cross-connection configuration is incorrect.
Procedure
Step 1 View the LP_TIM alarm on the U2000, and then confirm the path number according to the alarm
parameters.
Step 2 View the LP_TIM alarm on the U2000, and then check whether the trace identifier of the relevant
lower order path of the tributary board at the opposite station is consistent with that of the lower
order path of the line board at the local station. If not, modify it, and then check whether the
LP_TIM alarm is cleared.
Step 3 If the alarm persists, check whether the service cross-connection configuration of the relevant
path of the tributary board that reports the alarm is correct. After modifying the incorrect
configuration, check whether the LP_TIM alarm is cleared.
Step 4 If the alarm persists, perform a self-loop on the local station. Perform a loopback to check
whether the board at the local or opposite end is faulty. If the board is faulty, replace it.
----End
Related Information
None.
Issue 02 (2011-06-30)

5-175

System
5 Alarm Reference
5.2.110 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating the mismatch of the lower order path trace identifier
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the LP_TIM_VC12 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_VC12 alarm are as follows:
5-176
The lower order path trace identifier to be received at the local station is configured
inconsistent with that transmitted at the opposite station.

Issue 02 (2011-06-30)

System
5 Alarm Reference
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 NMS to check whether the LP_TIM_VC12 alarm is cleared.
If...
Then...
This alarm persists
Step 4 If the alarm persists, replace the faulty board.
----End
Related Information
None
5.2.111 LP_TIM_VC3
Description
The LP_TIM_VC3 is an alarm indicating the mismatch of the lower order path trace identifier
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Issue 02 (2011-06-30)

5-177

System
5 Alarm Reference
Name
Meaning
Parameter 4
Parameter 5

When the LP_TIM_VC3 alarm occurs, the lower order path trace identifier byte (VC-12: 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_VC3 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.
Procedure
Step 1 Check whether the trace identifier transmitted at the corresponding path of the tributary board
at the opposite station is configured consistent with that to be received at the local station. If not,
modify them to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the LP_TIM_VC3 alarm is cleared.
If...
Then...
Step 4 If the alarm persists, replace the faulty board.
----End
Related Information
None
5-178

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.112 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that no payload is equipped in the lower order path. This
alarm occurs when the board detects that the signal label in the V5 byte is 0.
NOTE
The V5 byte is used to detect bit errors, to indicate the remote error and failure in the lower order path.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

The services in the path are unavailable. If the service is configured with protection, the
protection switching is also triggered.
Possible Causes
The possible causes of the LP_UNEQ alarm are as follows:
l
The tributary path at the local station is configured with services, but the tributary path at
the remote station is not configured with services.
The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Check whether the tributary path at the remote station is configured with services.
If...
Then...
The tributary path at the remote station is not

configured with services
Configure services for the tributary path at the

remote station. Then, check whether the
the next step.
The tributary path at the remote station is

configured with services
Step 2 Check whether the cross-connect settings on the service transit stations are correct.
Issue 02 (2011-06-30)

5-179

System
5 Alarm Reference
If...
Then...
The settings are incorrect
Change the settings. Then, check whether the

the next step.
The settings are correct
Step 3 Check whether the attributes of the relevant tributary board are correctly configured. If the
attributes of the relevant tributary board are incorrectly configured, modify the incorrect
configuration. Then, the LP_UNEQ alarm is cleared.
----End
Related Information
None.
5.2.113 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the lower order path received by the tributary
board on the cross-connection side is unequipped.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
5-180
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

Issue 02 (2011-06-30)

System
5 Alarm Reference

When the LP_UNEQ_VC12 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_VC12 alarm are as follows:
l
The lower order path at the opposite station of the SDH transmission equipment is unused.
The T_ALOS alarm is reported on the tributary board at the opposite station of the SDH
transmission equipment, and the LP_UNEQ_VC12 is enabled to be inserted.
Procedure
Step 1 Check whether the lower order path at the opposite station is set unused. If the lower order path
is used, go to step 3; If the path is not used, set the path to use.
Step 2 View alarms on the NMS to check whether the LP_UNEQ alarm is cleared.
If...
Then...
This alarm persists
Step 3 Check whether the T_ALOS alarm is reported on the tributary board at the opposite station and
whether the LP_UNEQ_VC12 is enabled to be inserted. Clear the T_ALOS alarm or disable the
LP_UNEQ_VC12 to be inserted.
----End
Related Information
T_ALOS
5.2.114 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that the lower order path received by the tributary
board on the cross-connection side is unequipped.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 02 (2011-06-30)

5-181

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

When the LP_UNEQ_VC3 alarm occurs, no services are loaded in the payload of the lower
order path (VC-12: 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_VC3 alarm are as follows:
l
The lower order path at the opposite station of the SDH transmission equipment is unused.
The T_ALOS alarm is reported on the tributary board at the opposite station of the SDH
transmission equipment, and the LP_UNEQ_VC3 is enabled to be inserted.
Procedure
Step 1 Check whether the lower order path at the opposite station is set unused. If the lower order path
is used, go to step 3; If the path is not used, set the path to use.
Step 2 View alarms on the U2000 to check whether the LP_UNEQ_VC3 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_VC3 is enabled to be inserted. Clear the T_ALOS alarm or disable the
LP_UNEQ_VC3 to be inserted.
----End
5-182

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
T_ALOS
5.2.115 LPS_UNI_BI_M
Description
The LPS_UNI_BI_M is an alarm indicating the mismatch of the single-ended and dual-ended
modes in a linear MSP. This alarm is applicable to a linear MSP only. This alarm occurs, when
the opposite end single-ended/dual-ended mode indicated by the lower three bits of the K2 byte
is inconsistent with the local end single-ended/dual-ended mode, and when the inconsistency
lasts for a time period (2s by default).
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

l Linear MSP: 0x01
Parameter 2

When the LPS_UNI_BI_M alarm occurs, the MSP becomes unavailable. If a fiber cut or another
fault occurs at this time, the services are interrupted.
Possible Causes
The possible causes of the LPS_UNI_BI_M alarm are as follows:
l
Issue 02 (2011-06-30)
The MSP configuration is incorrect.

5-183

System
5 Alarm Reference
The service board is faulty.
Procedure
Step 1 Make sure that the local and opposite NEs have consistent MSP configurations. After updating
the MSP configurations, check whether the LPS_UNI_BI_M alarm is cleared.
Step 2 If the alarm persists, check whether the service boards configured with the MSP at the local and
opposite ends are faulty. After replacing faulty service boards, check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are
faulty. After replacing faulty cross-connect boards, check whether the alarm is cleared.
----End
Related Information
Single-Ended/Dual-Ended mode
The single-ended/dual-ended mode refers to the revertive mode of the linear MSP switching.
This revertive mode can be either the single-ended mode or the dual-ended mode.
5.2.116 LPT_RFI
Description
The LPT_RFI is the remote failure indication of Link state pass-through (LPT).
Attribute
Alarm Severity
Alarm Type
Critical
Parameters
None.

The LPT protection is enabled and the services of the working path are interrupted.
Possible Causes
The possible causes of the LPT_RFI alarm are as follows:
l
5-184
In the case of the board configured with LPT, if the Ethernet port at the local end fails, the
opposite end reports the LPT_RFI alarm; if the SDH path fails, the local end and the
opposite end report the LPT_RFI alarm.
Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 Check whether the fiber is normal. If the fiber is faulty, replace the fiber.
Step 2 Check whether the cable is normal. If the cable is faulty, replace the cable.
Step 3 Check whether the services are correctly configured. If the configuration is incorrect, modify
the configuration and issue it again.
----End
Related Information
None
5.2.117 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating that the bias current of the laser crosses the
threshold. If the bias current of the laser crosses the threshold, the LSR_BCM_ALM alarm is
reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

When the LSR_BCM_ALM alarm occurs, the laser works abnormally. If the working current
is too high, the laser will be damaged. If the working current is too low, the working current will
cause insufficient gain. In both cases, services will be interrupted.
Possible Causes
The possible causes of the LSR_BCM_ALM alarm are as follows:
l
Issue 02 (2011-06-30)
The laser is aging.

5-185

System
5 Alarm Reference
The laser is faulty.
Procedure
Step 1 View the alarm on the U2000 to confirm the board that generates the alarm.
Step 2 Replace the optical module. Then, the LSR_BCM_ALM alarm is cleared.
----End
Related Information
None.
5.2.118 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the pluggable optical module of the line board
is not installed.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

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
5-186
The pluggable optical module is not installed or is not installed correctly.

Issue 02 (2011-06-30)

System
5 Alarm Reference
The optical module or line board is faulty.
Procedure
Step 1 Check whether the pluggable optical module is installed on the board and whether it is correctly
installed. If not, correctly install the pluggable optical module on the board.
Step 2 View alarms on the U2000 to check whether the LSR_NO_FITED alarm is cleared.
If...
Then...
Step 3 If the alarm persists, the optical module or board is faulty. In this case, replace the optical module
first. If the alarm still persists, replace the board.
CAUTION
For the optical module with pluggable line boards, hot swap is supported.
----End
Related Information
None
5.2.119 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the life of the laser is close to the end.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-187

System
5 Alarm Reference
Name
Meaning
Parameter 1

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 aged, which causes the bias current too high.
Procedure
Step 1 The life of the line board laser is close to the end. Replace the laser first. If the alarm still persists,
replace the line board.
----End
Related Information
None
5.2.120 LTI
Description
The LTI is an alarm indicating loss of the synchronization clock source set for the clock board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
5-188

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 1 l 0x01: Indicates that all the synchronization sources of the system clock are
lost.
l 0x02: Indicates that all the synchronization sources of the first 2M phaselocked source are lost.

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.
There is the R_LOS, R_LOF, or R_LOC alarm.
In the case of tracing the external clock source, there is no input from the external clock
source.
The synchronization clock source is set to non-revertive, or is blocked, or is incorrectly set.
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 U2000 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.
Issue 02 (2011-06-30)
If...
Then...
The line clock source is traced, and there is

the R_LOS, R_LOF, or R_LOC alarm on the
line board

The tributary clock source is traced, and there

is the T_ALOS or E1_LOS 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 connected well.

5-189

System
5 Alarm Reference
Step 4 After ensuring that the synchronization clock source is normal, view alarms on the U2000 to
check whether the LTI alarm is cleared.
If...
Then...
Step 5 If the clock board is faulty, replace the faulty board.

----End
Related Information
None.
5.2.121 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
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

When the MS_AIS alarm occurs, the last three bits of the K2 byte in the signal received at the
optical interface of the line board are all "1"s. Consequently, the services are unavailable. If the
MSP APS or PPS service is configured, the alarm causes the protection switching. If the MS_AIS
is set as an optional switching condition, the clock source is switched.
5-190

Issue 02 (2011-06-30)

System
5 Alarm Reference
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
A high-level alarm such as the R_LOS or R_LOF alarm, which is reported by the opposite
station and inserted with an AIS alarm, is transmitted to the local station.
The receive part at the local station is faulty.
Procedure
Step 1 Check whether the transmit end of the line board at the opposite station is configured with the
MS_AIS alarm inserted.
If...
Then...

opposite station is inserted with the MS_AIS
alarm
Cancel the inserted MS_AIS alarm.

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. Then, check whether the line board at the opposite station reports the
MS_AIS alarm.
If...
Then...
If the line board of the opposite station is

faulty
Perform a reset on the board or replace the

The transmit part of the line board at the

opposite station is normal
Step 3 To check the line board at the local station, also perform the selfloop with fibers or the optical
interface selfloop and then check whether the local line board reports the MS_AIS alarm.
Perform a reset on the board or replace the board to check whether the alarm is cleared.
----End
Related Information
None.
5.2.122 MS_CROSSTR
Issue 02 (2011-06-30)

5-191

System
5 Alarm Reference
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
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 2, Parameter 3 The two most significant bits of parameter 2 indicate the
performance monitoring period.
l 0x01: The monitoring period is 15 minutes.
l 0x02: The monitoring period is 24 hours.
NOTE
The six least significant bits of parameter 2 and parameter 3 together indicate
the ID of a performance event.

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:
l
The multiplex section performance threshold is set to a large or small value.
The bit errors occur in the multiplex section.
Procedure
Step 1 On the NMS, check whether the multiplex section performance threshold regarding MSBBE,
MSES, MSSES, MSCSES, and MSUAS is set to a large or small value.
5-192

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...

small value
Change the multiplex section performance

threshold to the default value. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.

value
Step 2 View alarms on the U2000 and check whether there are other section-level bit error alarms on
the board that reports the MS_CROSSTR alarm.
If...
Then...
The B2_EXC or B2_SD alarm is reported

document to clear the alarm. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The B2_EXC or B2_SD alarm is not reported
Step 3 Perform the loopback for the stations at two ends of the line. Wait until the performance
monitoring ends. Locate the faulty board.
If...
Then...
The multiplex section performance event is

The transmit part of the board at the opposite

The multiplex section performance event is


----End
Related Information
B2_EXC, B2_SD, 6.2.30 MSBBE, 6.2.32 MSES, 6.2.38 MSSES, 6.2.31 MSCSES, 6.2.39
MSUAS
5.2.123 MS_RDI
Description
The MS_RDI is a remote defect indication in the multiplex section. When the last three bits of
the K2 byte in the signal received at the line board are 110, the remote multiplex section fails to
receive signals.
Issue 02 (2011-06-30)

5-193

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

When the MS_RDI alarm occurs, the last three bits of the K2 byte in the signal received by 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. Consequently, 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.
Procedure
Step 1 View alarms of the opposite station on the U2000. Check whether there is the R_LOS, R_LOS,
R_LOF, MS_AIS, or B2_EXC alarm on the line board at the opposite station.
5-194
If...
Then...
There is the R_LOS, R_LOC, R_LOF,

MS_AIS, or B2_EXC alarm

There are no such alarms as the R_LOS,

R_LOC, R_LOF, MS_AIS, and B2_EXC

Issue 02 (2011-06-30)

System
5 Alarm Reference
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 the loopback for the stations at two ends of the
line. Locate and replace the faulty line board.
----End
Related Information
R_LOS, R_LOC, R_LOF, MS_AIS, and B2_EXC
5.2.124 MS_REI
Description
The MS_REI is an indication alarm that bit errors occur at the remote end of the multiplex
section.
Attribute
Alarm Severity
Alarm Type
Warning
Service alarm
Parameters
table.
Name
Meaning
Parameter 1

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.
Issue 02 (2011-06-30)

5-195

System
5 Alarm Reference
Procedure
Step 1 View alarms of the opposite station on the U2000. Check whether there are B2 bit errors on the
opposite line board.
If...
Then...
There are B2 bit errors

document to clear the bit errors.
There are no B2 bit errors
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...
If the number of bit errors does not increase

any more
The receive end of the board at the opposite

station is faulty. Replace the faulty line board.
If the number of bit errors still increases

----End
Related Information
B2_EXC and B2_SD
5.2.125 MSAD_CROSSTR
Description
The MSAD_CROSSTR is an alarm indicating that the number of multiplex section bit errors
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
5-196

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1
Indicates the optical Interface number.
Parameter 4
Bit7-Bit6: Indicate the performance monitoring period.

l 0x01: The performance monitoring period is 15 minutes.
l 0x10: The performance monitoring period is 24 minutes.
Bit5-Bit0: Indicate the performance event ID.
l 0xff: Reserved
Parameter 5
Indicates the performance event ID.

l 0x2a: AUPJCHIGH
l 0x2b: AUPJCLOW
l 0x2c: AUPJCNEW
l 0xff: Reserved

If 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 performance threshold is set to an inappropriate value.
The section-level bit errors occur.
The loop clock is distorted.
Procedure
Step 1 On the NMS, check whether the threshold of the performance events regarding AUPJCHIGH,
AUPJCLOW, and AUPJCNEW is set to a large or small value.
Issue 02 (2011-06-30)
If...
Then...

small value
Change the performance threshold to the

default value. Check whether the alarm is
step.

value

5-197

System
5 Alarm Reference
Step 2 View alarms on the U2000 and check whether there are other section-level bit error alarms on
the board that reports the MSAD_CROSSTR alarm.
If...
Then...

alarm exist


Step 3 Check whether the clock tracing in the entire network is correctly set. If the setting is not correct,
reset the clock tracing.
Step 4 After ensuring the clock tracing setting of the entire network, wait until the set performance
monitoring period ends. View alarms on the U2000 to check whether the MSAD_CROSSTR
alarm is cleared.
If...
Then...
Step 5 Perform the loopback for the stations at two ends of the line. Wait until the set performance
monitoring period ends Locate the faulty board.
If...
Then...
The multiplex section adaptation

performance event is reported on the opposite
board
The transmit part of the board at the opposite

The multiplex section adaptation

performance event is reported on the local
board

----End
Related Information
5.2.126 NESOFT_MM
Description
The NESOFT_MM is an alarm indicating that the NE software versions on the working and
protection SCC boards are inconsistent.
5-198

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1
l 0x01: the files in the flash memory

l 0x02: the software that is currently running
Parameter 2 and Parameter 3 Indicate the IDs of the inconsistent files on the SCC board.
Parameter 4

l 0x04: The versions of the files in the working and the
protection areas of a single SCC board are inconsistent.
l 0x08: The file versions of the working SCC and those of the
protection SCC are inconsistent.
l 0x0C: The file versions in the working and the protection
areas of a single SCC board are inconsistent. At the same
time, the file versions of the working and those of the
protection SCC boards are inconsistent.

The NESOFT_MM alarm has the following impacts on the system:
l
If the software versions of the working SCC and the protection SCC are inconsistent, the
active/standby switching of the system is affected.
If no NE software exists on the FLASH, the system cannot reboot after the system is
powered off or reset.
Possible Causes
The causes for the NESOFT_MM alarm are as follows:
l
The version of the software that is currently running on the working SCC is inconsistent
with that on the protection SCC.
The software versions in the working and the protection areas (OFS1 and OFS2) are
inconsistent.
Issue 02 (2011-06-30)

5-199

System
5 Alarm Reference
On the working and protection SCC boards, no file named after the board exists under the
peer board directory.
Procedure
Step 1 Contact Huawei engineers to reload the mapping software.
----End
Related Information
None.
5.2.127 NE_POWER_OVER
Description
The NE_POWER_OVER is an alarm indicating that the power consumption of an NE is over
the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of NE power consumption that crosses the associated
threshold.
l 0x01: The physical power consumption of the NE crosses the associated
threshold.
l 0x02: The logical power consumption of the NE crosses the associated
threshold.

If the NE constantly works with a power consumption that is over the threshold, it brings great
pressure on the power supply board.
5-200

Issue 02 (2011-06-30)

System
5 Alarm Reference
Possible Causes
The possible causes of the NE_POWER_OVER alarm are as follows:
l
The power consumptions of all the logical boards of the NE are over the threshold.
The total power consumption of the boards inserted on the NE is over the threshold.
Procedure
Step 1 Delete the unused logical boards on the NMS.
Step 2 Remove the unused physical board from the NE.
----End
Related Information
None
5.2.128 NESF_LOST
Description
The NESF_LOST alarm indicates that the NE software is lost. This alarm is reported when the
NE software of the SCC board is not available.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
table.
Name
Meaning
Indicates the file type unavailable in the board software.

If the NE software of the working and protection SCC boards are not available, the boards do
not work normally in the following cases: the SCC boards are reset; the SCC boards are restarted
after they are powered off. As a result, the NMS fails to monitor the NEs.
Issue 02 (2011-06-30)

5-201

System
5 Alarm Reference
Possible Causes
The possible causes of the NESF_LOST alarm are as follows:
l
The NE software is not loaded or the NE software is loaded incorrectly.
The NE software is lost or damaged.
The flash memory does not exist or is faulty.
Procedure
Step 1 View the alarms on the U2000 and determine the board that generates the alarm.
Step 2 Reload the NE software and perform a warm reset on the faulty board on the U2000. Then, check
whether the alarm is cleared.
Step 3 If the NESF_LOST alarm persists, replace the board that generates the alarm.
----End
Related Information
None.
5.2.129 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in the installing state. This alarm
occurs when the NE is just delivered from the factory or when the user issues the command to
initialize the NE.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
None.

After the alarm occurs, no configuration exists at the NE side. Reload the configuration at the
NE side. Otherwise, the NE cannot be configured with services.
5-202

Issue 02 (2011-06-30)

System
5 Alarm Reference
CAUTION
If this alarm occurs, the NE data cannot be uploaded but only downloaded.
If the upload operation is performed after the NESTATUS_INSTALL alarm occurs, empty NE
data is uploaded. If the data is downloaded, the NE data is cleared. As a result, services are
interrupted.
Possible Causes
The possible causes of the NESTATE_INSTALL alarm are as follows:
l
The user issues the command to initialize the NE. Verification, however, is not performed.
The NE is in the initializing state, and thus is configured with no data.
The database on the SCC is faulty.
If only one SCC exists, replace the SCC.
Procedure
Step 1 Issue the configuration data again and perform the verification. Then, check whether the
NESTATE_INSTALL alarm is cleared.
----End
Related Information
None
5.2.130 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the software of the service board is damaged or
does not exist.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-203

System
5 Alarm Reference
Name
Meaning
Parameter 1
Parameter 2, Parameter 3 Indicate the ID of the file that is lost.

Parameter 4
Indicate the type of the file that is lost.

l 0x01: The file does not exist.
l 0x02: The file check fails.
l 0x04: The version of a file in the active area is different from
the version of the corresponding file in the standby area.
l 0x08: The version of a file on the active board is different from
the version of the corresponding file on the standby board.
l 0x0e: The file check fails. The version of a file in the active area
on the active board is different from the version of the
corresponding file in the standby area on the active board, and
from the version of the corresponding file on the standby board.

If the NO_BD_SOFT alarm occurs, no software is load to the service board of the NE, or the
software is not fully loaded to the board of the NE. If the board software does not exist or is not
fully loaded, the board does not work normally after being restarted.
Possible Causes
The possible causes of the NO_BD_SOFT alarm are as follows:
l
The software is lost, deleted, or not loaded.
The service board is damaged.
Procedure
Step 1 Check the alarm parameters, and determine the type of the lost file according to parameter 4.
Reload the lost file. After loading the file, reset the board.
Step 2 View alarms on the U2000 to check whether the NO_BD_SOFT alarm is cleared.
If...
Then...
The alarm persists
Step 3 If the alarm persists, replace the board.

----End
5-204

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None.
5.2.131 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
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

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 used after the board is started. As a result,
the optical module cannot be correctly set and the service transmission and receiving on the
board are affected.
Possible Causes
The possible causes of the NO_LSR_PARA_FILE alarm are as follows:
l
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.
Procedure
Step 1 Replace the optical module.
Step 2 View alarms on the U2000 to check whether the NO_PARA_FILE alarm is cleared.
Issue 02 (2011-06-30)

5-205

System
5 Alarm Reference
If...
Then...
Step 3 Replace the board that reports the NO_LSR_PARA_FILE alarm.

----End
Related Information
None
5.2.132 ODC_BATTERY_CURRENT_ABN
Description
The ODC_BATTERY_CURRENT_ABN alarm indicates that the current of the storage battery
is abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: The internal current loop of the storage battery is broken.
l 0x02: The recharge current of the storage battery is high.
l 0x03: The storage battery is discharged unevenly.

The equipment may fail to work normally, or even the equipment is damaged.
Possible Causes
The possible causes of the ODC_BATTERY_CURRENT_ABN alarm are as follows:
5-206

Issue 02 (2011-06-30)

System
5 Alarm Reference
For the storage battery in the cabinet, the circuit breaker is open or the fuse is blown.
The positive and negative polarities of the storage battery are connected inversely.
The power module frame is faulty.
The power monitoring module is faulty.
The power module is faulty. For example, the battery fails or ages.
Procedure
Step 1 Check whether the circuit breaker of the storage battery is open and whether the fuse of the
storage battery is blown.
If...
Then...
The circuit breaker is open
Close the circuit breaker.
The fuse of the storage battery is blown
Replace the fuse.
Step 2 Check whether the positive and negative electrodes of the storage battery are correctly connected.
If the positive and negative electrodes of the storage battery are incorrectly connected, connect
them correctly.
Step 3 Check whether the power module frame is damaged. If the power module frame is damaged,
replace the power module frame.
Step 4 Replace the power monitoring module.
Step 5 Check whether the ODC_MDL_ABN alarm is reported.
If...
Then...
The ODC_MDL_ABN alarm is reported
Rectify the fault according to the handling

procedure of the ODC_MDL_ABN alarm.
The ODC_MDL_ABN alarm is not

reported
Replace the power module.
----End
Related Information
None.
5.2.133 ODC_BATTERY_PWRDOWN
Description
The ODC_BATTERY_PWRDOWN alarm indicates that the storage battery fails to supply
power for the equipment.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Issue 02 (2011-06-30)

5-207

System
5 Alarm Reference
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: power-off due to low voltage
l 0x02: power-off due to background control
l 0x03: power-off due to local manual operations
l 0x04: power-off due to high temperature

No backup power supply is provided for the equipment.
Possible Causes
The possible causes of the ODC_BATTERY_PWRDOWN alarm are as follows:
l
The storage battery does not supply power for the equipment due to background control.
The BAT button on the front panel of the PMU is set to OFF.
The AC input power is abnormal.
The power module is faulty.
The temperature threshold that triggers power-off of the storage battery due to high
temperature is set to an inappropriate value.
The temperature of the storage battery is high.
The ambient temperature sensor of the power module is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Turn on the storage battery for the equipment.
Step 3 On the front panel of the PMU, hold the BAT ON button for 5-10 seconds to turn on the storage
battery.
Step 4 Query the threshold for the alarm indicating an exception in the AC power voltage. Then,
determine whether the threshold is appropriate according to the configuration and planning
information.
If...
Then...
The threshold is set to an inappropriate value Set the threshold to an appropriate value.
5-208

Issue 02 (2011-06-30)

System
If...
5 Alarm Reference
Then...
The threshold is set to an appropriate value Go to the next step.

Step 5 Check whether the AC circuit breaker is closed.
If...
Then...
The AC circuit breaker is open
Close the AC circuit breaker.
The AC circuit breaker is closed
Step 6 Check the connection of the AC power cable.

If...
Then...
The connection of the AC power cable is incorrect
Connect the cable properly.
The AC power cable is deteriorated or damaged
Replace the cable.
Step 7 Rectify the fault of the power module according to the handling procedure of the
ODC_MDL_ABN alarm.
Step 8 Rectify the fault of the power monitoring module.
Step 9 Query the threshold for the alarm indicating power-off due to high temperature. Then, determine
whether the threshold is appropriate according to the configuration and planning information.
If...
Then...
The threshold is appropriate
Step 10 Replace the storage battery.

Step 11 Replace the ambient temperature sensor of the power module.
----End
Related Information
None
5.2.134 ODC_DOOR_OPEN
Description
The ODC_DOOR_OPEN alarm indicates that the door of an outdoor cabinet is open.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Issue 02 (2011-06-30)

5-209

System
5 Alarm Reference
Parameters
None

If the cabinet door is open, the equipment is affected in the aspects of its temperature, relative
humidity, and dust-proof capability due to the external equipment. In addition, the equipment
may be damaged or stolen.
Possible Causes
The possible causes of the ODC_DOOR_OPEN alarm are as follows:
l
The door access alarm is set incorrectly.
The cabinet door is open.
The cable between the sensor and the monitoring equipment is connected incorrectly.
The sensor is faulty.
The associated monitoring equipment is faulty.
No door sensor is installed, but the door access alarm is enabled.
Procedure
Step 1 Check whether the door access alarm is set correctly according to the configuration and planning
information.
If...
Then...
The door access alarm is set correctly
The door access alarm is set incorrectly
Set the door access alarm correctly.
Step 2 Close the cabinet door.

Step 3 Check the cable connection between the sensor and the monitoring equipment.
If...
Then...
The cable is connected incorrectly or is loose Connect the cable properly.

The cable is deteriorated or damaged
Replace the cable.
The cable is connected correctly
Perform the operations required when the

alarm is generated due to Step 4.
Step 4 Rectify the fault of the sensor. Then, check whether the alarm clears.
If...
Then...
The alarm clears
End the alarm handling.
The alarm persists Perform the operations required when the alarm is generated due to
Step 5.
Step 5 Rectify the fault of the monitoring equipment.
5-210

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The alarm clears
Step 6.
Step 6 Install a door sensor and enable the door access alarm.
----End
Related Information
None
5.2.135 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED alarm indicates that the fan is faulty.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the location of the fault.

l 0x01: The fan at the internal ventilation hole is faulty.
l 0x02: The fan at the external ventilation hole is faulty.

The cabinet cannot dissipate heat properly. As a result, the equipment may be damaged and
services may be affected.
Possible Causes
The possible causes of the ODC_FAN_FAILED alarm are as follows:
l
Issue 02 (2011-06-30)
The cable of the fan is connected incorrectly.

5-211

System
5 Alarm Reference
The fan is faulty.
The fan is not installed.
Procedure
Step 1 Determine the faulty fan according to the alarm parameters displayed on the NMS.
Step 2 Connect the cable of the fan properly according to the specified regulations.
Step 3 Replace the module where the fan resides.
Step 4 Install the fan.
----End
Related Information
None
5.2.136 ODC_HUMI_ABN
Description
The ODC_HUMI_ABN alarm indicates that the relative humidity in the cabinet environment
exceeds the specified threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: The relative humidity is high.
l 0x02: The relative humidity is low.

In the case of high relative humidity, the equipment may be damaged. In the case of low relative
humidity, the life of the equipment may be shortened.
5-212

Issue 02 (2011-06-30)

System
5 Alarm Reference
Possible Causes
The possible causes of the ODC_HUMI_ABN alarm are as follows:
l
The threshold for the alarm is set to an inappropriate value.
The cable between the humidity sensor and the monitoring equipment is connected
incorrectly.
The humidity sensor is faulty.
Procedure
Step 1 Check whether the threshold for the relative humidity alarm is set to an appropriate value
according to the configuration and planning information.
If...
Then...
The threshold for the relative humidity

alarm is set to an appropriate value

The threshold for the relative humidity

alarm is set to an inappropriate value
Set the threshold for the relative humidity

alarm to an appropriate value.
Step 2 Check whether the cable between the humidity sensor and the monitoring equipment is properly
connected.
If...
Then...

Handle the exceptions of the cable.
The cable is connected properly

Step 3 Rectify the fault of the sensor.

Step 4 Then, check whether the alarm clears.
If...
Then...
The alarm clears
Step 5.
----End
Related Information
None
Issue 02 (2011-06-30)

5-213

System
5 Alarm Reference
5.2.137 ODC_LOAD_PWRDOWN
Description
The ODC_LOAD_PWRDOWN alarm indicates that the secondary load is powered off.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: power-off due to low voltage
l 0x02: power-off due to background control
l 0x03: power-off due to startup in the case of low temperature
l 0x04: power-off due to high temperature

The services on the secondary load are interrupted.
Possible Causes
The possible causes of the ODC_LOAD_PWRDOWN alarm are as follows:
5-214
The load is powered off due to background control.
The AC input power is abnormal.
The cabinet temperature is low.
The temperature threshold that triggers power-off of the load due to high temperature is set
to an inappropriate value.
The cabinet temperature is high.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Turn on the storage battery for the equipment.
Step 3 Query the threshold that triggers the alarm indicating an exception in the AC power voltage.
Then, determine whether the threshold is appropriate according to the configuration and planning
information.
If...
Then...
Step 4 Check whether the AC circuit breaker is closed.
If...
Then...
Step 5 Check the connection of the AC power cable.

If...
Then...
The connection of the AC power cable is incorrect Connect the cable properly.
The AC power cable is deteriorated or damaged
Step 6 Rectify the fault of the power module according to the handling procedure of the
ODC_MDL_ABN alarm.
Step 7 Rectify the fault of the power monitoring module.
Step 8 Check whether the temperature of the cabinet is low.
If...
Then...
The temperature of the cabinet is normal Go to the next step.

The temperature of the cabinet is low
Find the cause of the low temperature of the

cabinet, and then rectify the fault.
Step 9 Replace the ambient temperature sensor of the power module.

Step 10 Query the threshold for the alarm indicating power-off of the load due to high temperature. Then,
determine whether the threshold is appropriate according to the configuration and planning
information.
If...
Then...
The threshold is set to an inappropriate

value
Set the threshold to an appropriate value.
The threshold is set to an appropriate value Perform the operations required when the
alarm is generated by cause 2 of power-off
due to high temperature.
Issue 02 (2011-06-30)

5-215

System
5 Alarm Reference
Step 11 Check whether the ambient temperature is continuously high.

If...
Then...
The temperature is not continuously high Go to the next step.

The temperature is continuously high
Lower the ambient temperature of the

equipment.
Step 12 Replace the ambient temperature sensor.

----End
Related Information
The load that the DC power outlet on the cabinet corresponds to functions as the secondary load.
5.2.138 ODC_MDL_ABN
Description
The ODC_MDL_ABN alarm indicates that exceptions occur in the power module.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
5-216
Name
Meaning
Parameter 1
Indicates the ID of the power module that reports the alarm.

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 2, Parameter 3 Indicate the alarm cause.

l 0x01: The power module is switched off.
l 0x02: The power module is faulty.
l 0x03: The power module stops self-protection.
l 0x04: The power module fails to communicate with the power
monitoring module, or the power module is not in position.
l 0x05: The outdoor cabinet is not installed with a power module,
and the logical slot for a power module is not set on the NMS.
l 0x06: The outdoor cabinet is installed with a power module, but
the logical slot for the power module is not set on the NMS.

If the power module is faulty, the loading capability of the power system is affected. As a result,
the storage battery may discharge, or even the entire power system of the equipment is powered
off.
Possible Causes
The possible causes of the ODC_MDL_ABN alarm are as follows:
l
The power module is not configured on the NMS.
The power module is not in position, or the power module is not inserted securely.
Exceptions occur in the power monitoring unit.
Procedure
Step 1 Set the logical slot of the power module on the NMS.
Step 2 Check whether the power module is in position and whether the power module is properly
installed.
If...
Then...
The power module is not in position
Install the power module.
The power module is not properly installed
Install the power module properly.
Step 3 Check whether the power module is faulty.
Issue 02 (2011-06-30)
If...
Then...
The power module is faulty
Replace the optical module with a

functioning one. Then, check whether the
the next step.

5-217

System
5 Alarm Reference
If...
Then...
The power module works properly
Step 4 Check whether the PDU module is faulty. If Yes, replace the PDU module.
----End
Related Information
None.
5.2.139 ODC_POWER_FAIL
Description
The ODC_POWER_FAIL alarm indicates that exceptions occur in the AC input power voltage
or the DC output power voltage.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the type of the fault.

l 0x56: The voltage of the AC input power is high.
l 0x57: The voltage of the AC input power is low.
l 0x58: The voltage of the DC output power is high.
l 0x59: The voltage of the DC output power is low.
l 0x5b: No AC input power is available.
l 0x5c: The phase voltage is unavailable.

If exceptions occur in the AC input power voltage, the storage battery takes over the power
supply automatically and fails to support the normal operation of the equipment in a long term.
If exceptions occur in the DC output power voltage, the services on the equipment are interrupted.
5-218

Issue 02 (2011-06-30)

System
5 Alarm Reference
Possible Causes
The possible causes of the ODC_POWER_FAIL alarm are follows:
l
Exceptions occur in the AC input power voltage.
Exceptions occur in the DC output power voltage.
Procedure
Step 1 Check whether the threshold that triggers the alarm indicating exceptions in the AC input power
voltage is set to inappropriate value.
If...
Then...
Step 2 Check whether the AC circuit breaker is open.
If...
Then...
Step 3 Check whether the AC power cable is connected incorrectly.

If...
Then...
The cable is connected incorrectly or is loose
The connection is correct
Step 4 Check whether the AC power grid distributes the power inappropriately.
If...
Then...
The AC power grid distributes the power

inappropriately
Rectify the fault of the power module at

the base station.
The AC power grid distributes the power

appropriately
Step 5 Check whether the monitoring equipment is faulty.

If...
Then...
The monitoring equipment is faulty
Rectify the fault of the monitoring

equipment.
The monitoring equipment works properly Perform the operations required when the
Step 6 Check whether the threshold that triggers the alarm is set to an inappropriate value.
Issue 02 (2011-06-30)

5-219

System
5 Alarm Reference
If...
Then...
Step 7 Check whether the PSU module is faulty.
If...
Then...
The PSU module is faulty
Rectify the fault of the PSU module.
The PSU module works properly
Step 8 Check whether the power of the storage battery is insufficient.

If...
Then...
The power is insufficient
Recharge the storage battery.
The power is sufficient
Rectify the fault of the monitoring equipment.
----End
Related Information
None
5.2.140 ODC_SMOKE_OVER
Description
The ODC_SMOKE_OVER alarm indicates that smoke occurs in an outdoor cabinet.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None.

The equipment may be burned.
Possible Causes
The possible causes of the ODC_SMOKE_OVER alarm are as follows:
5-220
The smoke alarm setting does not comply with the configuration and planning information.
A fire and heavy smoke occur at the equipment in the cabinet.

Issue 02 (2011-06-30)

System
5 Alarm Reference
The cable between the smoke sensor and the monitoring equipment is connected
incorrectly.
The smoke sensor is faulty.
Procedure
Step 1 Check whether the smoke alarm setting and the configuration and planning information are the
same.
If...
Then...
The smoke alarm setting and the configuration and

planning information are the same
The smoke alarm setting and the configuration and

planning information are not the same
Set the smoke alarm correctly.
Step 2 Extinguish the fire in the cabinet.

Step 3 Check whether the cable between the sensor and the monitoring equipment is connected
correctly.
If...
Then...

The cable deteriorates or is damaged
Replace the cable.


Step 5 Check whether the alarm clears.
If...
Then...
The alarm is cleared End the alarm handling.

The alarm persists
Perform the operations required when the alarm is generated due

to Step 6.

----End
Related Information
None.
5.2.141 ODC_SURGE_PORTECTION_FAIL
Description
The ODC_SURGE_PROTECTION_FAIL alarm indicates that the surge protection function of
the outdoor cabinet fails to work properly.
Issue 02 (2011-06-30)

5-221

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the type of surge protection.

l 0x01: AC surge protection alarm
l 0x02: DC surge protection alarm

The AC surge protection function of the cabinet is disabled.
Possible Causes
The possible causes of the ODC_SURGE_PROTECTION_FAIL alarm are as follows:
l
The alarm setting does not comply with the configuration and planning information.
The cable between the lightning sensor and the monitoring equipment is connected
incorrectly.
The lightning sensor is faulty.
The lightning arrestor is faulty.
Procedure
Step 1 Check whether the alarm is set correctly according to the configuration and planning
information.
If...
Then...
The alarm is set correctly
The alarm is set incorrectly
Set the surge protection alarm correctly.
Step 2 Check the cable connection between the sensor and the monitoring equipment.
5-222

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
Replace the cable.

Step 4 Check whether the alarm clears.
If...
Then...
The alarm clears
The alarm persists
Step 5 Check whether the alarm output terminal of the lightning arrestor works properly.
If...
Then...
The alarm output terminal works properly
The alarm output terminal fails to work properly
Replace the lightning arrestor.

----End
Related Information
None.
5.2.142 ODC_TEC_ALM
Description
The ODC_TEC_ALM alarm indicates that the TEC air conditioning module in the cabinet fails
to work properly.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

If the TEC air conditioning module fails to work properly, the storage battery may operate at
very high or low temperature, and therefore it fails to operate safely.
Issue 02 (2011-06-30)

5-223

System
5 Alarm Reference
Possible Causes
The possible causes of the ODC_TEC_ALM alarm are as follows:
l
The TEC cable is connected incorrectly.
The TEC module is faulty.
The monitoring equipment is faulty.
Procedure
Step 1 Connect the TEC cable correctly.
Step 2 Replace the TEC module.
----End
Related Information
None
5.2.143 ODC_TEMP_ABN
Description
The ODC_TEMP_ABN alarm indicates that the ambient temperature of the cabinet or the
temperature of the storage battery is inappropriate.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: The ambient temperature is higher than the upper threshold.
l 0x02: The ambient temperature is lower than the lower threshold.
5-224

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 2
Indicates the temperature type.

l 0x01: Extremely high or extremely low temperature at the air outlet
l 0x0b: Extremely high or extremely low ambient temperature 1
l 0x0c: Extremely high or extremely low ambient temperature 2
l 0x0d: Extremely high or extremely low battery group temperature

If the temperature is inappropriate, the equipment performance declines and the life of the
equipment is shortened.
Possible Causes
The possible causes of the ODC_TEMP_ABN alarm are as follows:
l
The threshold for the temperature alarm is set to an inappropriate value.
The cable between the temperature sensor and the monitoring equipment is connected
incorrectly.
Procedure
Step 1 Check whether the threshold for the temperature alarm is set to an appropriate value according
to the configuration and planning information.
If...
Then...

correctly.
If...
Then...
Step 3 Check whether the temperature sensor is faulty. If the temperature sensor is faulty, replace it
with a functioning one.
Step 4 Check whether the alarm is cleared.
If...
Then...
Issue 02 (2011-06-30)

5-225

System
5 Alarm Reference
If...
Then...
The alarm persists

----End
Related Information
None.
5.2.144 ODC_WATER_ALM
Description
The ODC_WATER_ALM alarm indicates that water enters the cabinet.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None.

The moisture in the cabinet increases, and the equipment in the cabinet may be damaged.
Possible Causes
The possible causes of the ODC_WATER_ALM alarm are as follows:
l
The water alarm is set incorrectly.
Water enters the cabinet.
The cable between the water sensor and the monitoring equipment is connected incorrectly.
The water sensor is faulty.
Procedure
Step 1 Check whether the water alarm is set correctly according to the configuration and planning
information.
5-226
If...
Then...
The water alarm is set correctly

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The water alarm is set incorrectly
Set the water alarm correctly.
Step 2 Check whether water enters the cabinet. If water enters the cabinet, dry the cabinet immediately.
correctly.
If...
Then...


Step 4 Check whether the water sensor is faulty. If the water sensor is faulty, replace it with a functioning
one.
----End
Related Information
None.
5.2.145 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm is reported
when the phase-locked loop on the cross-connect board becomes faulty.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-227

System
5 Alarm Reference
Name
Meaning
Parameter 1
Indicates the failed phase-locked loop.

l 0x01: first 2M phase-locked loop
l 0x03: 38M analog phase-locked loop
l 0x04: 77M phase-locked loop on the board
l 0x05: 77M phase-locked loop on the board in the extended slot

When the OOL alarm occurs, the phase-locked loop cannot lock the input signals. The output
clock signals are affected, resulting in quality degrade or interruption of services.
Possible Causes
The possible cause of the OOL alarm is as follows:
l
The board hardware of the phase-locked loop is damaged.
Procedure
Step 1 Check whether the active clock board reports the OOL alarm.
If...
Then...
The active clock board reports the OOL

alarm
Switch from the active clock board to the

standby clock board. Then, check whether the
alarm is cleared. If the alarm persists, go to the
next step.
The active clock board does not report the Go to the next step.
OOL alarm
Step 2 Replace the board that reports the alarm.
----End
Related Information
None.
5.2.146 OUT_PWR_ABN
Description
The OUT_PWR_ABN is an alarm indicating that the output optical power is abnormal.
5-228

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

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:
l
The output optical power is extremely high or low.
Procedure
Step 1 Measure the output optical power of the line board by using an optical power tester, and check
whether the output optical power is within the normal range. If not, replace the optical module.
Step 2 View alarms on the U2000 to check whether the OUT_PWR_ABN alarm is cleared.
If...
Then...
Step 3 Replace the tributary board that reports the OUT_PWR_ABN alarm.
----End
Related Information
None
Issue 02 (2011-06-30)

5-229

System
5 Alarm Reference
Description
The OUT1TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor at the air
outlet fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

If this alarm is reported, the equipment cannot collect the temperature data of the air outlet on
the TCU.
Possible Causes
Possible causes of this alarm are as follows:
l
The outlet temperature sensor is not installed.
The outlet temperature sensor is incorrectly connected.
The outlet temperature sensor is faulty.
Procedure
Step 1 Check whether the outlet temperature sensor is installed.
If...
Then...
The outlet temperature sensor is not installed
Install the outlet temperature sensor

correctly. Check whether the alarm is cleared.
The outlet temperature sensor is installed
Step 2 Check whether the outlet temperature sensor is correctly connected and whether the cable is
intact.
5-230

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The outlet temperature sensor is incorrectly

connected

Replace the cable with a proper one. Check

The outlet temperature sensor is correctly

Step 3 Replace the outlet temperature sensor, and check whether the alarm is cleared.
If...
Then...
The alarm persists
Replace the cabinet and the alarm is cleared

automatically.
----End
Related Information
None.
Description
The OUT2TEMP_SENSOR_FAIL is an alarm indicating that the external outlet temperature
sensor fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

If this alarm is reported, the equipment cannot collect the temperature data of the air outlet on
the TCU.
Issue 02 (2011-06-30)

5-231

System
5 Alarm Reference
Possible Causes
The possible causes of the OUT2TEMP_SENSOR_FAIL alarm are as follows:
l
The external outlet temperature sensor is not installed.
The external outlet temperature sensor is incorrectly connected.
The external outlet temperature sensor is faulty.
Procedure
Step 1 Check whether the external outlet temperature sensor is installed.
If...
Then...
The external outlet temperature sensor is not

installed
The external outlet temperature sensor is

installed
Step 2 Check on the NMS whether the OUT2TEMP_SENSOR_FAIL alarm is cleared. If the
OUT2TEMP_SENSOR_FAIL alarm persists, check whether the external outlet temperature
sensor is correctly connected or the cable is intact.
If...
Then...

incorrectly connected

correctly connected and the cable is intact
Step 3 Check on the NMS whether the OUT2TEMP_SENSOR_FAIL alarm is cleared. If the
OUT2TEMP_SENSOR_FAIL alarm persists, replace the temperature sensor with a proper one.
Step 4 If the OUT2TEMP_SENSOR_FAIL alarm persists after the temperature sensor is replaced,
----End
Related Information
None.
5-232

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.149 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
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None.

When the P_AIS alarm is reported, the signals received on the PDH side of the E3/T3 tributary
board are all 1s, namely, 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.
The interconnected PDH equipment outputs the AIS signal.
The TU_AIS or TU_LOP alarm is reported on the corresponding path of the tributary board.
Procedure
Step 1 Check the configuration of the interconnected PDH equipment and the cable.
Step 2 On the NMS, check whether the TU_AIS or TU_LOP alarm is reported on the corresponding
path of the tributary board.
If...
Then...
The TU_AIS or TU_LOP alarm is reported
Refer to 5.2.200 TU_AIS or 5.2.203

TU_LOP to clear the alarm immediately.
Check whether the P_AIS alarm is cleared. If
The TU_AIS or TU_LOP alarm is not

reported
Step 3 Replace the E3/T3 tributary board that reports the alarm.
----End
Issue 02 (2011-06-30)

5-233

System
5 Alarm Reference
Related Information
None.
5.2.150 P_LOC
Description
The P_LOC (Loss Of PDH Interface Input Signal Clock) is an alarm indicating the loss of the
input signals on the PDH side of the E3/T3 tributary board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the alarm is reported, it indicates that the input clock signals are lost on the PDH side of
the E3/T3 tributary board. As a result, a large amount of bit errors are generated and frames
cannot be located.
Possible Causes
The possible causes of the P_LOC alarm are as follows:
l
The input signals are not E3/T3 signals.
The PDH signal clocks are lost.
Procedure
Step 1 Check whether the input signals of the board are normal E3/T3 signals. Set the transmit signals
of the interconnected PDH equipment to E3/T3 and then check whether the alarm is cleared.
Step 2 If the alarm persists, remove and insert the E3/T3 tributary board.
Step 3 If the alarm persists, replace the E3/T3 tributary board that reports the alarm.
----End
Related Information
None.
5-234

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.151 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
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the P_LOS alarm is reported, 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.
Possible Causes
The possible causes of the P_LOS alarm are as follows:
l
The output port of the PDH equipment connected with the local station is loose or has fallen
off.
The input port of the PDH equipment in the local station is loose or has fallen off.
The interface cable is faulty.
The transmit part of the PDH equipment connected with this station fails.
The input signal structure is not the E3/T3 service.
The E3/T3 board is faulty.
Procedure
Step 1 Check whether the cable ports of the PDH equipment and the local board are loose or have fallen
off. If yes, tighten the cable ports.
Step 2 View alarms on the U2000 to check whether the P_LOS alarm is cleared.
If...
Then...
The alarm persists
Step 3 Check whether the cable is faulty and whether the PDH equipment transmits properly. Check
whether the transmitted data is of E3/T3 service.
Issue 02 (2011-06-30)

5-235

System
5 Alarm Reference
Step 4 View alarms on the U2000 to check whether the P_LOS alarm is cleared.
If...
Then...
The alarm persists
Step 5 Replace the E3/T3 tributary board that reports the alarm.
----End
Related Information
None
5.2.152 PATCH_ACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating that patch package activation times out.
This alarm occurs when a patch package stays in the active state for a period longer than the
preset threshold. In this case, users need to handle the patch package.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None.

The active state of a patch package is unstable. If the board where the patch package resides is
reset, the patch package cannot take effect and enters the deactive state automatically after the
board starts working.
Possible Causes
Possible cause of this alarm is as follows:
A patch package stays in the active state for a period longer than the preset threshold.
Procedure
Step 1 Check whether the patch package in the active state is normal.
5-236

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The patch package is abnormal
Deactivate and delete the patch package. The

alarm is cleared automatically.
The patch package is normal
Run the patch package immediately.
----End
Related Information
None.
5.2.153 PATCH_DEACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating the patch package deactivation timeout.
If the deactivation of the patch times out, you need to process the patch.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None.

The deactivation status indicates that the patch is loaded but the patch is not running. If the board
is reset in this case, the patch is automatically restored to the idle status after the system restarts.
The functions of the patch do not exist or the bug corrected by the patch appears again.
Possible Causes
The possible cause of the PATCH_DEACT_TIMEOUT alarm is as follows:
The patch stays in the deactive state for a time longer than the specified period.
Procedure
Step 1 To enable the patch, you need to activate the patch.
Step 2 Delete the patch if it is not needed. The alarm is cleared automatically.
----End
Issue 02 (2011-06-30)

5-237

System
5 Alarm Reference
Related Information
None.
5.2.154 PATCH_ERR
Description
The PATCH_ERR is an alarm indicating that the patch file is detected incorrect when the NE
loads the path after a reset.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

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:
l
A patch is running before the NE restarts. After the NE restarts, the patch file is detected
incorrect.
Procedure
Step 1 Check whether the loaded patch file is correct on the U2000. If the patch file is incorrect, load
the correct patch file, and then reset the NE.
Step 2 View alarms on the U2000 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. Perform a reset on the NE. If yes, go to step 5.
Step 4 View alarms on the U2000 to check whether the PATCH_ERR alarm is cleared.
5-238

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
Step 5 Replace the SCC board.

----End
Related Information
None.
5.2.155 PATCH_NOT_CONFIRM
Description
The PATCH_NOT_CONFIRM is an alarm indicating that the activated patch times out after
the NE loads the patch. This alarm is reported if the activated patch has not yet confirmed.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

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:
l
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.
Procedure
Step 1 Check whether the loading status of the current patch is activated. If not, reactivate the patch.
----End
Issue 02 (2011-06-30)

5-239

System
5 Alarm Reference
Related Information
None.
5.2.156 PATCH_PKGERR
Description
The PATCH_PKGERR is an alarm indicating that the patch package file is abnormal.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

If the patch package file is abnormal, the normal loading, activation and running of the patch
package are affected.
NOTE
When this alarm is generated, the services are not interrupted.
Possible Causes
The possible causes of the PATCH_PKGERR alarm are as follows:
l
The patch package file is incorrect.
The patch package file is damaged.
The patch package file is deleted.
Procedure
Step 1 Re-load the correct patch package file. The alarm is cleared automatically.
----End
Related Information
None.
5.2.157 PATCHFILE_NOTEXIST
5-240

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The PATCHFILE_NOTEXIST is an alarm indicating that the patch file does not exist when the
NE loads the path after a reset.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the PATCHFILE_NOTEXIST alarm occurs, the NE restarts, automatically loads and runs
the patch file, and detects that the path 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:
l
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.
Procedure
Step 1 Load the patch file again, and perform a reset on the NE.
Step 2 View alarms on the U2000 to check whether the PATCHFILE_NOTEXIST alarm is cleared.
If...
Then...
Step 3 Replace the SCC board.

----End
Related Information
None
Issue 02 (2011-06-30)

5-241

System
5 Alarm Reference
5.2.158 POWER_ABNORMAL
Description
The POWER_ABNORMAL alarm is an alarm indicating the power supply failure. This alarm
is reported if one power supply of the NE fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the number of the power input.

l 0x01: power input 1
l 0x02: power input 2
Parameter 2
Indicates the status of the power input.

l 0x00: no power input
l 0x01: over-voltage
l 0x02: under-voltage

If the alarm is reported, it indicates that one of the two power supply channels are faulty. As a
result, the NE is affected.
Possible Causes
The possible causes of the POWER_ABNORMAL alarm are as follows:
l
The port of the cable is loose, or has fallen off.
The power board is faulty.
Procedure
Step 1 Check whether the faulty channel of the power supply is properly connected. If the channel is
not connected or the connection is loose, properly connect the channel.
5-242

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 2 View alarms on the U2000 to check whether the POWER_ABNORMAL alarm is cleared.
If...
Then...
The alarm persists
Step 3 Replace the NE subrack.
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. Hence, this operation is of risk.
----End
Related Information
None.
5.2.159 POWER_FAIL
Description
The POWER_FAIL is an alarm indicating the power supply failure on an NE.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-243

System
5 Alarm Reference
Name
Meaning
Parameter 1
Indicates the type of the power supply failure.

l 0x12: The 12 V power supply is over-voltage.
l 0x13: The 12 V power supply is under-voltage.
l 0x41: The 3.3 V power supply is over-voltage.
l 0x42: The 3.3 V power supply is under-voltage.
l 0x4b: The 1.2 V power supply is over-voltage.
l 0x4c: The 1.2 V power supply is under-voltage.
l 0x57: The -12 V power supply is over-voltage.
l 0x58: The -12 V power supply is under-voltage.
l 0x59: The 3.3 V DSP is over-voltage.
l 0x5a: The 3.3 V DSP is under-voltage.

l
If the CXL board reports this alarm, one of the five power fault detection points in the NE
power module fails. The fault affects the operation of the NE.
If the power board reports this alarm, power backup fails.
Possible Causes
The possible cause of the POWER_FAIL alarm is as follows:
l
The switch on the standby power board is turned off.
The power module is aged.
Procedure
Step 1 Check whether the switch on the standby power board in 1+1 protection is turned off.
5-244
If...
Then...
The switch on the standby power board is

turned off
Turn on the switch on the standby power

board. Then, check whether the alarm is
step.

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The switch on the standby power board is

turned on
Step 2 Check whether the power module on the NE is faulty or aged.

If...
Then...
The power module is faulty or aged
Replace the power board and then check

whether the alarm clears. If the alarm persists,
go to the next step.
Step 3 Check whether the POWER_FAIL alarm on the U2000 is cleared.

If...
Then...
Replace the NE subrack.
----End
Related Information
None.
5.2.160 PWR_TEMP_OVERTH
Description
The PWR_TEMP_OVERTH is an alarm indicating that the temperature of the power module
crosses the specified threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-245

System
5 Alarm Reference
Name
Meaning
Parameter 1 Indicates the number of the power module whose temperature crosses the
specified threshold.

If this alarm is reported, a board may report a temperature-related alarm, and work unstably.
Possible Causes
The possible causes of the PWR_TEMP_OVERTH alarm are as follows:
l
The ambient temperature is very high.
Procedure
Step 1 Check whether the ambient temperature is very high.
If...
Then...
The ambient temperature is very high
Decrease the ambient temperature to the

specified range, and then check whether the
the next step.
The ambient temperature is proper

If...
Then...
Replace the power board with a functioning

one, and then check whether the alarm is
step.
Step 3 Contact Huawei technical support engineers to handle the alarm.

----End
Related Information
None.
5-246

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.161 POWER_MODULE_OFFLINE
Description
The POWER_MODULE_OFFLINE is an alarm indicating that a power module is offline. This
alarm is reported when a power module is detected offline.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the power module number.

l 0x01: Power module 1 is offline.
l 0x02: Power module 2 is offline.

After this alarm is reported, no power is provided for the corresponding port.
Possible Causes
The possible causes of the ROWER_MODULE_OFFLINE alarm are as follows:
l
The power module is in poor contact.
Procedure
Step 1 Check whether the power module is in poor contact.
Issue 02 (2011-06-30)
If...
Then...
The power module is in poor contact
Insert the power module properly, and then

check whether the alarm is cleared. If the
The power module is in proper contact

5-247

System
5 Alarm Reference

If...
Then...
Replace the power module with a functioning

one.
Step 3 On the NMS, check whether the alarm is cleared.

If...
Then...
The alarm persists

----End
Related Information
None.
5.2.162 R_APS
Description
The R_APS is an alarm indicating that the line board failed to receive the K1/K2 byte.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
5-248
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 2, parameter 3 Indicates the path number. The values of parameter 2 and parameter
3 are always 0x01, respectively.
Parameter 4
The value is always 0xff (Reserved).
Parameter 5

When the R_APS alarm occurs, it indicates that the line board failed to receive the K1/K2 byte.
If the services are configured with MSP switching, the MSP switching will fail.
Possible Causes
The possible causes of the R_APS alarm are as follows:
l
The K1 or K2 bytes are inconsistent in any consecutive three frames of the 12 frames
Procedure
Step 1 Check the line board. That is, perform selfloop on the optical port of the line board.
Step 2 View alarms on the NMS to check whether the R_APS alarm is cleared.
If...
Then...
This alarm persists
The line board is faulty. Replace the board.
Step 3 If the opposite line board is faulty, replace the board.

----End
Related Information
None
5.2.163 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.
Issue 02 (2011-06-30)

5-249

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

NOTE
For example, the value 0x01 indicates optical interface 1.
Parameter 2, parameter 3 Indicates the path number. The values of parameter 2 and parameter
3 are always 0x00 and 0x01, respectively.
Parameter 4
Parameter 5

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.
Procedure
Step 1 The receive part of the local line board is faulty. Replace the faulty board.
----End
5-250

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None.
5.2.164 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
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

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 rates of the optical interfaces at the two ends are inconsistent.
The fiber connector is loose or dirty.
The transmission fiber cable is faulty.
The attenuation of the received signal is excessive.
The signals transmitted at the opposite station do not have the frame structure.
Issue 02 (2011-06-30)

5-251

System
5 Alarm Reference
Procedure
Step 1 Check the rates of the optical interfaces at the two ends of the fiber. If the rates are inconsistent,
replace the optical modules to ensure that the rates are consistent.
Step 2 Check whether the fibers are intact and whether the fiber connectors have a good connection.
Replace the fiber or clean the fiber connectors.
Step 3 Check whether the transmission fiber cable is faulty. If the the fiber cable is faulty, replace it
with a new one.
Step 4 Rectify the fault of the fibers. View alarms on the NMS to check whether the R_LOF alarm is
cleared.
If...
Then...
The alarm persists
Step 5 Check the level of the optical interface configured at the line boards. If the levels are different,
change the levels and issue the configuration.
Step 6 View alarms on the NMS to check whether the R_LOF alarm is cleared.
If...
Then...
The alarm persists
Step 7 Check whether the transmitted signals of the opposite line boards are normal. Perform loopback
for the optical interfaces of the opposite line board to check whether the R_LOF is reported. The
opposite line board is faulty, replace the board.
Step 8 Rectify the fault of the opposite line board. View alarms on the NMS to check whether the
R_LOF alarm is cleared.
If...
Then...
The alarm persists
Step 9 If the local line board is faulty, replace it.

----End
Related Information
None.
5.2.165 R_LOS
Description
The R_LOS is an alarm indicating the loss of signal at the receive optical interface on the line
board.
5-252

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

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 laser of the opposite line board is disabled.
The fiber cut occurs to the connected fibers.
The line is heavily attenuated or the optical power is overloaded.
The transmitter of the opposite station or line transmission fails.
Procedure
Step 2 Remove the fault of the fibers. View alarms on the NMS to check whether the R_LOS alarm is
cleared.
If...
Then...
Issue 02 (2011-06-30)

5-253

System
5 Alarm Reference
If...
Then...
This alarm persists
Step 3 Check whether the laser of the opposite line board is off, whether the optical power is normal,
and whether the transmit signal is normal. If the laser is off, turn on the laser. If the receive
optical power is overloaded, add the attenuator. If the transmit unit of the opposite line board is
faulty, replace the opposite optical module and line board.
Step 4 Remove the fault of the opposite line board. View alarms on the NMS to check whether the
R_LOS alarm is cleared.
If...
Then...
This alarm persists
Step 5 If the local line unit is faulty, replace the local optical module and faulty board.
----End
Related Information
None
5.2.166 R_OOF
Description
The R_OOF is an alarm indicating that the frame header can not be identified for five consecutive
frames in the received signals of the line board. The board enters the out-of-frame stated.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
5-254
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
5 Alarm Reference

The R_OOF is an alarm indicating that the frame header can not 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 fiber connector is loose or dirty.
The transmission fiber cable is faulty.
The synchronization clock source is severely out of synchronization.
The transmit unit at the opposite station is faulty.
The receive unit at the local station is faulty.
Procedure
Step 2 Check whether the transmission fiber cable is faulty. If the the fiber cable is faulty, replace it
with a new one.
Step 3 Remove the fault of the fibers. View alarms on the U2000 to check whether the R_OOF alarm
is cleared.
If...
Then...
Step 4 Check whether the received optical power is normal. If the attenuation of the received optical
power is excessive and the transmission of the opposite line board is faulty, replace the opposite
line board. If the received optical power is normal, go to step 5.
Step 5 Remove the fault of the opposite line board. View alarms on the U2000 to check whether the
R_OOF alarm is cleared.
If...
Then...
Step 6 Check the synchronization clock source of the tracing. If the clock source is severely out of
synchronization,re-trace the high-quality clock source.
Step 7 Remove the fault of the clock source. View alarms on the U2000 to check whether the R_OOF
alarm is cleared. If the clock source is normal, go to step 7.
Issue 02 (2011-06-30)

5-255

System
5 Alarm Reference
If...
Then...
Step 8 If the local line board is faulty, replace it.

----End
Related Information
None
5.2.167 R_S_ERR
Description
The R_S_ERR is an alarm indicating that the received signal has errors.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
Name
Meaning
Parameter 1
Indicates the optical interface number (the value is always 0x01).
Parameter 2, Parameter 3 Indicate the path number.

When the R_S_ERR alarm occurs, the services are interrupted.
Possible Causes
The possible causes of the R_S_ERR alarm are as follows:
l
The frequency offset of the input signal is very large.
Procedure
Step 1 Check whether the tributary board supports the type of the input signal.
5-256

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The tributary board does not support the

type of the input signal
Change the type of the output signal of the

remote site.
The tributary board supports the type of the Proceed to the next step.
input signal
Step 2 Test the frequency offset of the input signal.
If...
Then...
The frequency offset is very large
Troubleshoot the remote site.
The frequency offset meets the requirement

----End
Related Information
None.
5.2.168 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is an alarm of critical alarm inputs. This alarm occurs when
the user sets the severity of an available alarm input to critical.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the number of the alarm input/output.
Issue 02 (2011-06-30)

5-257

System
5 Alarm Reference

The RELAY_ALARM_CRITICAL alarm does not affect the operation of the SCC or the
services on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_CRITICAL alarm is as follows:
l
There is a critical alarm input.
Procedure
Step 1 View the RELAY_ALARM_CRITICAL alarm on the U2000. Confirm the number of the alarm
input/output according to Parameter 1.
Step 2 Cut off the alarm input. Then the RELAY_ALARM_CRITICAL alarm is automatically cleared.
----End
Related Information
None
5.2.169 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is an alarm of warning alarm inputs. This alarm occurs when
the user sets the severity of an available alarm input to warning.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
5-258
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
5 Alarm Reference

The RELAY_ALARM_IGNORE alarm does not affect the operation of the SCC or the services
on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_IGNORE alarm is as follows:
l
There is a warning alarm input.
Procedure
Step 1 View the RELAY_ALARM_IGNORE alarm on the U2000. Confirm the number of the alarm
Step 2 Cut off the alarm input. Then the RELAY_ALARM_IGNORE alarm is automatically cleared.
----End
Related Information
None
5.2.170 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is an alarm of major alarm inputs. This alarm occurs when the
user sets the severity of an available alarm input to major.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Issue 02 (2011-06-30)

5-259

System
5 Alarm Reference

The RELAY_ALARM_MAJOR alarm does not affect the operation of the SCC or the services
on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_MAJOR alarm is as follows:
l
There is a major alarm input.
Procedure
Step 1 View the RELAY_ALARM_MAJOR alarm on the U2000. Confirm the number of the alarm
Step 2 Cut off the alarm input. Then the RELAY_ALARM_MAJOR alarm is automatically cleared.
----End
Related Information
None
5.2.171 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is an alarm of minor alarm inputs. This alarm occurs when the
user sets the severity of an available alarm input to minor.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
5-260
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
5 Alarm Reference

The RELAY_ALARM_MINOR alarm does not affect the operation of the SCC or the services
on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_MINOR alarm is as follows:
l
There is a minor alarm input.
Procedure
Step 1 View the RELAY_ALARM_MINOR alarm on the U2000. Confirm the number of the alarm
Step 2 Cut off the alarm input. Then the RELAY_ALARM_MINOR alarm is automatically cleared.
----End
Related Information
None
5.2.172 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that the regenerator section performance of the line
board crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the period type of the performance statistics.

l 0x01: a 15-minute period
l 0x02: a 24-hour period
Issue 02 (2011-06-30)

5-261

System
5 Alarm Reference
Name
Meaning
Parameter 2, parameter 3 Indicate the performance event that causes the alarm.
l 0x01: The RSBBE performance event crosses the specified
threshold.
l 0x02: The RSES performance event crosses the specified
threshold.
l 0x03: The RSSES performance event crosses the specified
threshold.
l 0x06: The RSUAS performance event crosses the specified
threshold.

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.
Procedure
Step 1 View alarms on the U2000 to check whether there are other regenerator section bit error alarms
on the board that reports the RS_CROSSTR alarm.
If...
Then...
The B1_EXC or B1_SD alarm is reported

The B1_EXC or B1_SD alarm is not reported
Step 2 Perform the loopback for the stations at two ends of the line. Locate and replace the faulty line
board.
----End
Related Information
None.
5.2.173 RTC_FAIL
Description
The RTC_FAIL is an alarm of SCC real-time clock (RTC) failure. This alarm occurs when the
clock of the SCC is faulty.
5-262

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When this alarm occurs, the services are interrupted.
Possible Causes
The possible cause of the RTC_FAIL alarm is as follows:
The RTC chip of the SCC is damaged.
Procedure
Step 1 Replace the SCC board of the corresponding equipment.
----End
Related Information
None.
5.2.174 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
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2011-06-30)

5-263

System
5 Alarm Reference
Name
Meaning
Parameter 1
Indicates the switching type of the clock source.

l 0x01: switching of the clock source traced by the system
l 0x02: switching of 2M phase-locked clock source 1
l 0x03: switching of 2M phase-locked clock source 2

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.
The external BITS is broken.
The clock switching occurs at the uplink station.
New clock source is set in the local station.
Procedure
Step 1 View alarms on the U2000 to check whether there are alarms that are caused by the following
reasons on the local NE.
If...
Then...

T_ALOS, or EXT_SYNC_LOS alarm.

There are such alarms as the MS_AIS and

B2_EXC, and these alarms are set as
conditions that can trigger the clock
switching

There is no alarm
Step 2 It indicates that the clock source protection switching occurs in the network. Check the clock
source switching status in the network on the U2000. Check whether there are alarms that can
trigger the clock source switching on the upstream NE. If yes, handle these alarms.
----End
Related Information
R_LOS, R_LOC, R_LOF, T_ALOS, EXT_SYNC_LOS, MS_AIS, and B2_EXC
5-264

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.175 SECU_ALM
Description
The SECU_ALM is a security alarm indicating that the SCC reports an illegal login.
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of the terminal used to perform the login operation.
l 0x01: NM interface
l 0x02: LCT
l 0x03: command line
l 0x04: TL1 interface
l 0x05: SNMP interface
Parameter 2 Indicates the error that occurs in the login operation.
Parameter 3 Indicates the first two characters of the locked user name when the login
authentication fails.
l 0x01: The user does not exist.
l 0x02: The user has logged in.
l 0x04: The user password is wrong.
l 0x09: The login time is incorrect.
l 0x0F: The LCT provides no access.
l 0x10: The data operation is incorrect.
l 0x14: The user login terminal is wrong.
l 0x19: The user account is prohibited.
Issue 02 (2011-06-30)

5-265

System
5 Alarm Reference

The SECU_ALM alarm indicates that the SCC reports a security alarm of illegal login. If wrong
user passwords are entered for three consecutive times, the user account is locked for the time
being. In this case, wait for two minutes and then try to log in again.
Possible Causes
The possible cause of the SECU_ALM alarm is as follows:
l
The password is incorrectly entered three times during the login.
Procedure
Step 1 Obtain the correct password from the administrator. After the user account is unlocked, use the
correct password to log in.
----End
Related Information
None.
5.2.176 SLAVE_WORKING
Description
The SLAVE_WORKING is an alarm indicating that the protection board is working. This alarm
occurs when the service bus of the service board selects the protection cross-connect board and
the slave clock is selected as the system clock.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
5-266
Name
Meaning
Parameter 1
Parameter 2

Issue 02 (2011-06-30)

System
Name
Meaning
Parameter 3
Indicates the slot ID of the cross-connect board.
5 Alarm Reference

When the SLAVE_WORKING alarm occurs, the system is not affected. This alarm just shows
that the service bus of the service board selects the protection cross-connect board and the slave
clock is selected as the system clock.
Possible Causes
The possible causes of the SLAVE_WORKING alarm are as follows:
l
The working cross-connect and timing board is not in position.
The working cross-connect and timing board is deteriorated or faulty.
A certain service board is faulty.
The active/standby status bus of the cross-connect and timing board is damaged.
The connection bus between the line board and the working cross-connect and timing board
is damaged.
Procedure
Step 1 Check whether the working cross-connect and timing board is firmly inserted. If not, re-insert
the working cross-connect and timing board.
Step 2 Check whether the SLAVE_WORKING alarm is cleared. If the alarm persists, proceed to the
next step.
Step 3 Perform a cold reset on the working cross-connect and timing board by using the NMS, or
directly reseat this board.
CAUTION
If there is no protection cross-connect and timing board, performing a cold reset on the working
cross-connect and timing board may cause service interruptions.
Step 4 Check whether the SLAVE_WORKING alarm is cleared. If the alarm persists, replace the
working cross-connect and timing board.
Step 5 Check whether the SLAVE_WORKING alarm is cleared. If the alarm persists, perform a cold
reset on the service board that reports the SLAVE_WORKING alarm by using the NMS, or
directly reseat this board.
CAUTION
If the service on the board is not protected, a cold reset on the board causes service interruptions.
Issue 02 (2011-06-30)

5-267

System
5 Alarm Reference
Step 6 Check whether the SLAVE_WORKING alarm is cleared. If the alarm persists, replace the board
that reports the alarm.
Step 7 Check whether the SLAVE_WORKING alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
The working cross-connect board refers to the cross-connect board installed in the slot with a
smaller ID.
The protection cross-connect board refers to the cross-connect board installed in the slot with a
larger ID.
5.2.177 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that during software package
loading, the NE does not perform the commit operation in a certain time after the board is
activated.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
None

The NE does not perform commit for a long time, which causes the software in the two areas of
the double-area boards on the NE inconsistent. Once a board becomes abnormal, rollback occurs
to the entire NE.
Possible Causes
The possible cause of the SWDL_ACTIVATED_TIMEOUT alarm is as follows:
l
During the 30 minutes after the board is activated, the NE does not perform commit.
Procedure
Step 1 The software package loading is not complete. Proceed with the commit operation.
----End
5-268

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None
5.2.178 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function is
disabled. When the automatic match function of the board is disabled, the system reports the
alarm if the board cannot match the software from the system control board.
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
None

The board that reports the alarm cannot automatically match the software from the SCC board,
which affects the consistency of the software version on the entire NE. Some functions of the
NE may operate abnormally.
Possible Causes
The possible cause of the SWDL_AUTOMATCH_INH alarm is as follows:
l
The automatic match function is disabled.
Procedure
Step 1 Contact the Huawei technical support engineers for troubleshooting.
----End
Related Information
None
5.2.179 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm indicating that the NE software does not match
the board software. This alarm is reported in the situation where the board version information
Issue 02 (2011-06-30)

5-269

System
5 Alarm Reference
is inconsistent with that in the software package of the system control and communication (SCC)
board or the software package information in the CF card on the SCC board is inconsistent with
that in the flash memory of the SCC board after an NE is recycled and the board is online.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

When the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE may
be affected because the board software version is inconsistent with the version of the running
software.
Possible Causes
The possible cause of the SWDL_CHGMNG_NOMATCH alarm is as follows:
The software package of the SCC board does not match the software version of the board after
the SCC board is replaced.
Procedure
Step 1 Perform the package diffusion again on the NE where the SWDL_CHGMNG_NOMATCH
alarm is reported.
----End
Related Information
None.
5.2.180 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating that the commission operation on the NE
fails. This alarm is reported when the commission operation fails in the package diffusion.
Attribute
5-270
Alarm Severity
Alarm Type
Minor
Processing alarm

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
None

The SWDL_COMMIT_FAIL alarm occurs on double-area boards only. The consequence is that
the software versions in the two areas of the double-area board are inconsistent.
Possible Causes
The possible cause of the SWDL_COMMIT_FAIL is as follows:
l
The loaded package is incorrect.
Procedure
Step 1 Check whether the loaded package is correct.
Step 2 Perform the package diffusion again on the NE where the alarm is reported.
----End
Related Information
None
5.2.181 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the NE is loading the software package.
Attribute
Alarm Severity
Alarm Type
Warning
Processing alarm
Parameters
None

The NE is loading the software package. The operations including modifying configurations,
uploading/downloading files, and backing up the database are prohibited.
Possible Causes
The possible cause of the SWDL_INPROCESS alarm is as follows:
Issue 02 (2011-06-30)

5-271

System
5 Alarm Reference
The NE is loading the software package.
Procedure
Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback is
complete. Hence, this alarm can be neglected.
----End
Related Information
None
5.2.182 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that software package files are lost. This
alarm is reported when the NE software detects that some files in the CF card or flash memory
are lost after performing periodic checks, which are not initiated by commands.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
None.

When this alarm occurs, a certain file of the package is missing and the NE may malfunction.
Possible Causes
The possible cause of the SWDL_NEPKGCHECK alarm is as follows:
Certain files of the package are missing and cannot be recovered.
Procedure
Step 1 Ensure that the loaded software package is correct. Perform the package diffusion again on the
NE where the SWDL_NEPKGCHECK alarm is reported.
----End
Related Information
None.
5-272

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.183 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the software package version is
inconsistent with the software version specified in the software package. This alarm is reported
when the consistency check on the software package version fails.
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
None.

When this alarm occurs, certain functions of the NE may be affected, because the software
package version is inconsistent with the software version specified in the software package.
Possible Causes
The possible cause of the SWDL_PKGVER_MM is as follows:
The version information in the description file of the software package is inconsistent with the
actual version information.
Procedure
Step 1 Ensure that the loaded software package is correct. Perform the package diffusion again on the
NE where the alarm is reported.
----End
Related Information
None.
5.2.184 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing
from the software package. This alarm is reported when the required software is missing from
the software package during the automatic match of the board.
Issue 02 (2011-06-30)

5-273

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
None

As the software of the board is not contained in the software package, the board cannot perform
automatic match. As a result, the software version of the board is inconsistent with that of the
NE. Some functions may operate abnormally.
Possible Causes
The possible cause of the SWDL_PKG_NOBDSOFT alarm is as follows:
l
The software of some boards are removed during loading the customized software package.
Procedure
Step 1 Add the required board software to the software package.
Step 2 Alternatively, perform the software package loading again.
----End
Related Information
None
5.2.185 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that some board rollback fails when the
NE performs rollback. This alarm is reported when the rollback fails for any board on the NE.
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
None
5-274

Issue 02 (2011-06-30)

System
5 Alarm Reference

The board software version and the NE software version may mismatch. Some functions of the
NE may operate abnormally.
Possible Causes
The possible cause of the SWDL_ROLLBACK_FAIL alarm is as follows:
l
Certain board software is uninstalled during the software package loading.
Procedure
Step 1 Add the required board software to the software package. Alternatively, perform the software
package loading again.
----End
Related Information
None
5.2.186 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the current synchronization clock source of the clock
board is degraded.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None.

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:
l
Issue 02 (2011-06-30)
The quality of the traced synchronization clock source is degraded.

5-275

System
5 Alarm Reference
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

pointer justification performance events
Refer to the corresponding sections in this

document to clear the event.
There is no performance event.
Step 2 Check the clock source tracing setting. Prevent the clock tracing loop when configuring the clock
tracing.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD, and MSAD_CROSSTR
5.2.187 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
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
5-276

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 1 Indicates the clock source number.

l 0xf0: External clock source.
l 0xf1: Internal clock source.
NOTE
Two bytes are occupied for each clock source. The first byte indicates the slot ID, which
starts from 1. The second byte indicates the optical interface number.

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

T_ALOS alarm

There is no alarm
Go to step 3.
Step 2 View alarms on the U2000 to check whether the SYNC_C_LOS alarm is cleared.
If...
Then...
Step 3 If the priority level table is not properly configured, configure the clock source priority table
again.
Issue 02 (2011-06-30)

5-277

System
5 Alarm Reference
Step 4 View alarms on the U2000 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.
Refer to S1_SYN_CHANGE.
----End
Related Information
R_LOS, R_LOC, R_LOF, T_ALOS, and S1_SYN_CHANGE
5.2.188 SYNC_FAIL
Description
The SYNC_FAIL is an alarm indicating that the batch backup of the databases of the active and
standby SCC boards fails.
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of the error.

l 0x1f: The database backup fails.
l 0x20: The check of the software version of the active and standby SCC boards
fails.
l 0x21: The communication between the active and standby SCC boards fails.
5-278

Issue 02 (2011-06-30)

System
5 Alarm Reference

The data of the active and standby SCC boards is out of synchronization.
Possible Causes
The possible causes of the SYNC_FAIL are as follows:
l
The software versions of the active and standby SCC boards are inconsistent.
The communication fails during the batch backup of the databases of the active and standby
SCC boards.
Message sending fails or the database is detected damaged during the batch backup of the
databases of the active and standby SCC boards.
Procedure
Step 1 When Parameter 1 is 0x20, it indicates that the software versions of the active and standby SCC
boards are inconsistent. Replace the SCC boards or re-load the NE software to make the software
versions of the active and standby SCC boards consistent.
Step 2 When Parameter 1 is 0x21, it indicates that the communication fails during the batch backup. If
the communication fails for a short time, the system automatically initiates another batch backup.
If the communication fails for a long time, contact Huawei engineers.
Step 3 When Parameter 1 is 0x1F, contact Huawei engineers.
----End
Related Information
None.
5.2.189 T_ALOS
Description
The T_ALOS is an alarm indicating the loss of analog signals at the E1 or T1 interfaces. If no
service signals are input at the 2 Mbit/s or 1.5 Mbit/s port, the T_ALOS alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None.

When the T_ALOS alarm occurs, the PDH services are interrupted.
Issue 02 (2011-06-30)

5-279

System
5 Alarm Reference
Possible Causes
The possible causes of the T_ALOS alarm are as follows:
l
The E1 or T1 services are not accessed.
The output port of the E1 or T1 interface on the DDF side is disconnected or loose.
The cable is faulty.
Procedure
Step 1 View the T_ALOS alarm on the U2000 to confirm the relevant board.
Step 2 Check whether the E1 or T1 services in the relevant path of the board are accessed. After making
sure that the services are accessed, check whether the T_ALOS alarm is cleared. If the alarm
Step 3 If the alarm persists, perform service self-loop (namely, hardware inloop) to the path at the DDF.
CAUTION
l
If the alarm is cleared, the equipment at the opposite end is faulty. After removing the fault,
check whether the T_ALOS alarm is cleared.
Step 4 If the alarm persists, check whether the equipment at the opposite station is faulty. If yes, replace
the faulty board of the opposite station.
----End
Related Information
None.
5.2.190 T_FIFO_E
Description
The T_FIFO_E is an alarm indicating that the transmission FIFO on the PDH side of the E3/T3
tributary board overflows.
Attribute
5-280
Alarm Severity
Alarm Type
Minor
Equipment alarm

Issue 02 (2011-06-30)

System
5 Alarm Reference
Parameters
None.

When the T_FIFO_E alarm is reported, the transmission 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 cause of the T_FIFO_E alarm is as follows:
l
The E3/T3 tributary board is faulty.
Procedure
Step 1 If the E3/T3 tributary board is faulty, replace the faulty board.
CAUTION
Replacing the E3/T3 tributary board will interrupt the services on the board. This operation is
of risk. Make sure that the type of the signal received at or transmitted from the E3/T3 tributary
board is the same as that of the original board.
----End
Related Information
None
5.2.191 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
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Issue 02 (2011-06-30)

5-281

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

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 clock board is faulty.
The line board is faulty.
Procedure
Step 1 If the line board is faulty, replace it.
CAUTION
If the line board is not configured with automatic protection switching, replacing the optical
module of the line board, and performing a cold reset on the line board or replacing this line
board may cause the service interruption. This operation is of risk.
----End
Related Information
None
5.2.192 T_LOS
Description
The T_LOS is an alarm indicating that no signal is input on the transmit side of the line board.
5-282

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 4
Parameter 5

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
Procedure
Step 1 Check whether the services to be transmitted from this optical interface on the line board are
configured. If the transmission service is configured, go to step 3.
Step 2 Configure the services to be transmitted from the line board again. View alarms on the NMS to
check whether the T_LOS alarm is cleared.
If...
Then...
Issue 02 (2011-06-30)

5-283

System
5 Alarm Reference
If...
Then...
This alarm persists
Step 3 If the line board is faulty, reset the board.

Step 4 View alarms on the NMS to check whether the T_LOS alarm is cleared.
If...
Then...
This alarm persists
Step 5 If the cross-connect board is faulty, replace the SCC board.

----End
Related Information
None
5.2.193 T_LOSEX
Description
The T_LOSEX is an alarm indicating that a board has detected the loss of signal in the service
bus of the backplane. The T_LOSEX alarm is reported if a board has detected that the service
bus of the backplane is in the LOS status.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
5-284

Issue 02 (2011-06-30)

System
5 Alarm Reference
Name
Meaning
Parameter 1
Indicates the type of the lost bus signal.

l 0x01: The bus signal from the cross-connect board with a
smaller slot ID is lost.
l 0x02: The bus signal from the cross-connect board with a greater
slot ID is lost.
Parameter 2, Parameter 3 Each bit indicates the status of a backplane bus.

When the T_LOSEX alarm occurs, the services of a board are interrupted. Consequently, the
board fails to work normally.
Possible Causes
The possible causes of the T_LOSEX alarm are as follows:
l
The service board and the corresponding cross-connect board are inserted improperly.
Certain pins on the backplane are bent.
Procedure
Step 1 Check the alarm on the NMS, determine the service board that reports the alarm, and then confirm
the corresponding cross-connect board according to the alarm parameters.
Step 2 Check whether the service board that reports the alarm and the corresponding cross-connect
board are inserted firmly to the backplane.
If...
Then...
The boards are not inserted firmly Reseat the boards. For details on how to reseat a board.
Check whether the alarm is cleared. If the alarm
persists, proceed to the next step.
The boards are inserted firmly
Step 3 Replace the corresponding cross-connect board indicated by the alarm parameter. Check whether
the alarm is cleared.
Step 4 If the alarm persists, replace the board that reports the alarm.
Step 5 Check whether the alarm is cleared. If the alarm persists, proceed to the next step.
Step 6 Check whether certain pins on the backplane are bent.
Issue 02 (2011-06-30)

5-285

System
5 Alarm Reference
If...
Then...
Certain pins on the backplane are bent Contact Huawei technical support engineers to
repair the bent pins. Then, reseat the board.
The backplane is normal
Contact Huawei technical support engineers to

handle the alarm.
----End
Related Information
None.
5.2.194 TEM_HA
Description
The TEM_HA is an alarm indicating that the temperature of the laser exceeds the upper
threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

When the TEM_HA alarm is reported, the laser is faulty. Consequently, the services are
interrupted.
Possible Causes
The possible causes of the TEM_HA alarm are as follows:
l
5-286
The working ambient temperature is too high.

Issue 02 (2011-06-30)

System
5 Alarm Reference
The optical module is faulty.
Procedure
Step 1 Check the temperature of the NE subrack to determine whether the heat dissipation is proper.
Step 2 Check the line board that reports the alarm and replace the optical module.
Step 3 After the optical module is replaced, view alarms on the U2000 to check whether the TEM_HA
alarm is cleared.
If...
Then...
The alarm persists
Step 4 The line board is faulty. Replace the faulty board.
CAUTION
module of the line board, performing a hard reset on the line board, or replacing this line board
may cause the service interruption. This operation is of risk. For the optical module with
pluggable line boards, hot plugging is supported. Make sure that the rate and transmission
distance of the optical interface of the line board is the same as that of the original line board.
----End
Related Information
None
5.2.195 TEM_LA
Description
The TEM_LA is an alarm indicating that the temperature of the laser exceeds the lower threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Issue 02 (2011-06-30)

5-287

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1

When the TEM_LA alarm is reported, the laser is faulty. Consequently, the services are
interrupted.
Possible Causes
The possible causes of the TEM_LA alarm are as follows:
l
The working ambient temperature is excessively low.
The optical module is faulty.
Procedure
Step 1 Check whether the ambient temperature in the equipment room is excessively low. If yes,
increase it to a proper value for the equipment to work well, and then check whether the TEM_LA
alarm is cleared.
Step 2 If the alarm persists, the optical module may be faulty. Replace the board in which the alarm is
generated, and then check whether the alarm is cleared.
If...
Then...
The alarm persists
Step 3 The line board is faulty. Replace the faulty board.
CAUTION
module of the line board, performing a hard reset on the line board, or replacing this line board
may cause the service interruption. This operation is of risk. For the optical module with
pluggable line boards, hot plugging is supported. Make sure that the rate and transmission
distance of the optical interface of the line board is the same as that of the original line board.
----End
Related Information
None
5-288

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.196 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the temperature of the laser crosses the
threshold. The alarm is reported when the temperature of the laser crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the threshold-crossing type of temperature.

l 0x01: The temperature of the laser is higher than the upper threshold.
l 0x02: The temperature of the laser is lower than the lower threshold.

After the TEMP_ALARM alarm is reported, if the temperature is excessively high or low and
the optical module is damaged, the services are interrupted.
Possible Causes
The possible causes of the TEMP_ALARM alarm are as follows:
l
The ambient temperature of the board is excessively high.
The ambient temperature of the board is excessively low.
Procedure
Step 1 View the alarms on the U2000, and then confirm the temperature threshold crossing type
according to the Parameter 1.
Step 2 If the ambient temperature of the board is excessively high, decrease the temperature to a proper
value for the equipment to work properly, and then check whether the alarm is cleared.
Step 3 If the ambient temperature of the board is excessively low, the alarm may be caused by the
hardware fault of the board. Check whether the board reports the alarm that indicates board or
Issue 02 (2011-06-30)

5-289

System
5 Alarm Reference
chip fault, such as HARD_BAD. If the working status of the board is abnormal, replace the
faulty board. For details, see "Replacing a Board."
----End
Related Information
None.
5.2.197 TF
Description
The TF is a transmission failure indication alarm of the laser.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 4

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 cause of the TF alarm is as follows:
l
The laser of the line board is faulty.
Procedure
Step 1 Check the optical module of the line board to check whether the optical module is faulty. If yes,
replace it with the optical module of the same type.
5-290

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 2 After the new board operates normally, view alarms on the U2000 to check whether the TF alarm
is cleared.
If...
Then...
Step 3 If the line board is faulty, replace it.

----End
Related Information
None
5.2.198 THUNDERALM
Description
The THUNDERALM is an alarm indicating the lightning protection failure. If the system detects
the lightning protection circuit fails, the THUNDERALM occurs.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
Name
Meaning
Parameter 1
Indicates the power unit that reports the alarm.

l 0x00: All the power units fail.
l 0x01: The lightning protection of the PIU1 board fails.
l 0x02: The lightning protection of the PIU2 board fails.

When the THUNDERALM occurs, the system operation and services are not affected, but the
lightning protection function fails.
Possible Causes
The cause of the THUNDERALM alarm is as follows:
l
Issue 02 (2011-06-30)
The fuse tube of the lightning protection circuit is interrupted.

5-291

System
5 Alarm Reference
Procedure
Step 1 Replace the fuse tube, and then check whether the alarm is cleared.
Step 2 Replace the board that reports the THUNDERALM alarm.
----End
Related Information
None.
5.2.199 TR_LOC
Description
The TR_LOC is an alarm indicating that the clock of the cross-connect board is faulty. This
alarm is reported when a board detects that the clock signal transmitted from the clock unit to
the board is lost.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the slot ID of the board that loses the clock.
l 0x01: board with a smaller slot ID
l 0x02: board with a larger slot ID
l 0x03: two boards
5-292

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning
Parameter 2 Indicates the fault status of the cross-connect and timing board.
l bit[0]: clock loss of the cross-connect board in the slot with a smaller ID
l bit[1]: frame header loss of the cross-connect board in the slot with a smaller
ID
l bit[2]: 2M clock status of the cross-connect board in the slot with a smaller
ID
l bit[3]: clock loss of the cross-connect board in the slot with a greater ID
l bit[4]: frame header loss of the cross-connect board in the slot with a greater
ID
l bit[5]: 2M clock status of the cross-connect board in the slot with a greater
ID
NOTE
If the bit corresponding to Parameter 2 is 1, the TR_LOC alarm occurs. If the bit
corresponding to Parameter 4 is 0, the TR_LOC alarm does not occur.

When the TR_LOC occurs, the board fails to work normally. If the protection cross-connect
board is faulty, the services are not affected. If the working cross-connect board is faulty, the
services are switched. Consequently, the transient service interruption event occurs.
Possible Causes
The possible causes of the TR_LOC alarm are as follows:
l
If multiple boards report this alarm, the clock line of the cross-connect board is faulty.
If one board reports this alarm, the board hardware is faulty.
Procedure
Step 1 View the TR_LOC alarm at the local station, and check whether the alarm occurs at the service
boards.
1.
If the TR_LOC alarm occurs at most service boards, replace the CXL board.
2.
If the working cross-connect board is faulty, perform 1+1 protection switching on the crossconnect board.
3.
Perform a cold reset on the protection cross-connect board, and then check whether the
alarm is cleared.
4.
If the alarm persists, remove the chassis, And then check whether the alarm is cleared.
Step 2 View the TR_LOC alarm at the local station, and check whether the alarm occurs at only one
board.
1.
Perform a warm reset on the board that reports the alarm, and then check whether the alarm
is cleared. If the alarm persists, perform a cold reset on the board that reports the alarm.
2.
If the alarm persists, remove the board that reports the alarm and check whether certain
pins on the backplane are bent. Insert the board again, and then check whether the alarm is
cleared.
Issue 02 (2011-06-30)

5-293

System
5 Alarm Reference
3.
If the alarm persists, replace the board that reports the alarm.
----End
Related Information
None.
5.2.200 TU_AIS
Description
The TU_AIS is a TU alarm indication signal. If a board detects that the signals in the TU path
are all "1"s, the TU_AIS alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None.

When the TU_AIS alarm causes, the service in the TU path that reports the alarm is interrupted.
If the service is configured with protection, the protection switching is also triggered.
Possible Causes
The possible causes of the TU_AIS alarm are as follows:
l
Configuration data is incorrect.
The line is faulty.
The board at the opposite end is faulty.
The board at the local end is faulty.
Procedure
Step 1 Check whether the SDH service data is incorrect.
If...
Then...
The SDH service data is incorrect
Change the configuration data.
The SDH service data is correct
Step 2 Check whether a line alarm that causes AIS insertion is reported on the service trail.
5-294

Issue 02 (2011-06-30)

System
5 Alarm Reference
If...
Then...
The line alarm is reported
Clear the line alarms that cause AIS insertion.
No line alarm is reported
Step 3 Locate whether the board at the local end or at the opposite end is faulty.
If...
Then...
The board at the opposite end is faulty
Go to Step 4.
The board at the local end is faulty
Go to Step 5.
Step 4 Replace the faulty board at the opposite end.

Step 5 Replace the board where the local line unit resides.
If...
Then...
The alarm is cleared after the board is replaced
The alarm persists after the board is replaced

If...
Then...
The alarm is cleared after the board is

replaced
The alarm persists after the board is

replaced
Contact Huawei technical support engineers to

handle the alarm.
----End
Related Information
Table 5-2 Alarms that may cause the TU_AIS alarm
R_LOS
R_LOF
AU_LOP
HP_LOM
AU_AIS
5.2.201 TU_AIS_VC12
Issue 02 (2011-06-30)

5-295

System
5 Alarm Reference
Description
The TU_AIS_VC12 is an alarm indicating that the lower order path signals received at the crossconnect unit side by the tributary board are all "1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 2, parameter 3 Indicates the path number.

Parameter 4
Parameter 5

When the TU_AIS_VC12 alarm occurs, the lower order path signals received on the crossconnection side by the tributary board are all "1"s. Consequently, the services in the lower order
path are unavailable. If the SNCP protection is configured for the tributary board in the lower
order path, the TU_AIS_VC12 will trigger the switching of the SNCP protection.
When the TU_AIS_VC12 alarm occurs, the system returns the LP_RDI alarm to the opposite
station.
Possible Causes
The possible causes of the TU_AIS_VC12 alarm are as follows:
5-296
The relevant path at the opposite station is faulty.
The higher order alarms occur.
Cross-connect unit fault.

Issue 02 (2011-06-30)

System
5 Alarm Reference
Procedure
Step 1 View alarms on the NMS 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...

MS_AIS, AU_AIS or AU_LOP alarm

The AIS is set inserted when there is the Refer to the corresponding section in this
B1_EXC, B2_EXC, B2_SD, B3_EXC,
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, E1_LOS, or

UP_E1_AIS alarm
Refer tot the corresponding section in this

There is no T_ALOS, E1_LOS, and

UP_E1_AIS alarms
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 NMS to check whether the TU_AIS_VC12 alarm is cleared.
If...
Then...
This alarm persists
Step 5 Hard reset the faulty board.
CAUTION
Performing a hard reset on the board or replacing the board will interrupt services. This operation
is of risk.
Step 6 View alarms on the NMS to check whether the TU_AIS_VC12 alarm is cleared.
Issue 02 (2011-06-30)

5-297

System
5 Alarm Reference
If...
Then...
This alarm persists
Step 7 Replace the faulty SCC board.

----End
Related Information
R_LOS, R_LOC, R_LOF, MS_AIS, AU_AIS, AU_LOP, B1_EXC, B2_EXC, B2_SD,
B3_EXC, HP_LOM, B1_SD, B3_SD, HP_TIM, HP_UNEQ, HP_SLM, T_ALOS,
E1_LOS, and UP_E1_AIS
5.2.202 TU_AIS_VC3
Description
The TU_AIS_VC3 is an alarm indicating that the lower order path signals received at the crossconnect unit side by the tributary board are all "1"s.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
5-298
Parameter 4
Parameter 5

Issue 02 (2011-06-30)

System
5 Alarm Reference

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

MS_AIS, AU_AIS, or AU_LOP alarm

The AIS is set inserted when there is the

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

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, E1_LOS, or

UP_E1_AIS 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 U2000 to check whether the TU_AIS_VC3 alarm is cleared.
Issue 02 (2011-06-30)

5-299

System
5 Alarm Reference
If...
Then...
Step 5 Hard reset the faulty tributary board.
CAUTION
is of risk.
Step 6 View alarms on the U2000 to check whether the TU_AIS_VC3 alarm is cleared.
If...
Then...
Step 7 Replace the faulty SCC board.

----End
Related Information
R_LOS, R_LOC, R_LOF, MS_AIS, AU_AIS, AU_LOP, B1_EXC, B2_EXC, B2_SD,
B3_EXC, HP_LOM, R_OOF, B1_SD, B3_SD, HP_TIM, HP_UNEQ, HP_SLM,
T_ALOS, E1_LOS, and UP_E1_AIS
5.2.203 TU_LOP
Description
The TU_LOP is an alarm of TU pointer loss. This alarm occurs if a board detects that the TUPTR value is an invalid pointer or NDF reversion in eight consecutive frames.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None.
5-300

Issue 02 (2011-06-30)

System
5 Alarm Reference

The TU_LOP alarm causes service interruptions in the TU path of the relevant board. If the
service is configured with protection, the protection switching is also triggered.
Possible Causes
The possible causes of the TU_LOP alarm are as follows:
l
Service cross-connections are incorrectly configured.
The system control, cross-connect, and timing board is faulty.
Procedure
Step 1 Check whether the cross-connect service configurations are consistent with those specified in
the service planning document.
If...
Then...
The cross-connect service configurations are

inconsistent with those specified in the
service planning document
Re-configure the cross-connect services

according to the service planning document,
and then check whether the alarm is cleared.
The cross-connect service configurations are

consistent with those specified in the service
planning document
Step 2 Check whether the system control and cross-connect board is faulty.
If...
Then...

is faulty
Replace the system control and cross-connect

board with a functioning one, and then check

works properly
Step 3 Perform a loopback to check whether the tributary board at the local or opposite end is faulty.
If the tributary board is faulty, replace it.
----End
Related Information
None.
5.2.204 TU_LOP_VC12
Issue 02 (2011-06-30)

5-301

System
5 Alarm Reference
Description
The TU_LOP_VC12 is an alarm indicating that the TU pointer in the signals received by the
tributary board on the cross-connection side is lost.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

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

When the TU_LOP_VC12 alarm occurs, the TU pointer in the signals received by the tributary
board on the cross-connection side is lost. As a result, the services in the path are unavailable.
If the SNCP protection is configured for the tributary board in the lower order path, the
TU_LOP_VC12 will trigger the switching of the SNCP protection.
When the TU_LOP_VC12 alarm occurs, the system returns the LP_RDI alarm to the opposite
station.
Possible Causes
The possible causes of the TU_LOP_VC12 alarm are as follows:
l
The interface between the tributary board and the cross-connect unit is faulty.
Procedure
Step 1 Check whether the cross-connect unit or the tributary board is correctly configured. If not,
modify the incorrect configuration and issue it again.
5-302

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 2 View alarms on NMS to check whether the TU_LOP_VC12 alarm is cleared.
If...
Then...
This alarm persists
Step 3 Hard reset the tributary board.
CAUTION
Performing a hard reset on the board will interrupt services. This operation is of risk.
Step 4 View alarms on NMS to check whether the TU_LOP_VC12 alarm is cleared.
If...
Then...
This alarm persists
Step 5 The cross-connect unit is faulty. Replace the faulty board.

----End
Related Information
None
5.2.205 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating that the TU pointer in the signals received by the
tributary board on the cross-connection side is lost.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
Issue 02 (2011-06-30)

5-303

System
5 Alarm Reference
table.
Name
Meaning
Parameter 1

Parameter 4
Parameter 5

When the TU_LOP_VC3 alarm occurs, the TU pointer in the signals received by the tributary
board on the cross-connection side is lost. As a result, the services in the path are unavailable.
If the SNCP protection is configured for the tributary board in the lower order path, the
TU_LOP_VC3 will trigger the switching of the SNCP protection.
When the TU_LOP_VC3 alarm occurs, the system returns the LP_RDI alarm to the opposite
station.
Possible Causes
The possible causes of the TU_LOP_VC3 alarm are as follows:
l
The fault is with the interface between the tributary board and the cross-connect unit.
Procedure
Step 1 Check whether the cross-connect or the tributary board is correctly configured. If not, modify
the incorrect configuration and issue it again.
Step 2 View alarms on the U2000 to check whether the TU_LOP_VC3 alarm is cleared.
If...
Then...
Step 3 Hard reset the faulty board.

Step 4 View alarms on the U2000 to check whether the TU_LOP_VC3 alarm is cleared.
5-304
If...
Then...

Issue 02 (2011-06-30)

System
5 Alarm Reference
Step 5 The cross-connect unit is faulty. Replace the faulty board.

----End
Related Information
None
5.2.206 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indicating the upstream 2 Mbit/s signals. This alarm is reported if
a tributary board has detected that the upstream E1 signals are all "1"s.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None.

When the UP_E1_AIS alarm occurs, the E1 signals are unavailable.
Possible Causes
The possible causes of the UP_E1_AIS alarm are as follows:
l
The TU_LOP, TU_AIS, or DOWN_E1_AIS alarm is generated on the tributary board that
interconnects with the tributary board at the local end.
The T_ALOS alarm is generated on the tributary board that is located at the interconnected
NE and accesses the 2 Mbit/s signals.
The board that reports the alarm is faulty.
Procedure
Step 1 Check the alarm on the NMS, and then determine the board where the alarm is generated.
Step 2 Check whether a lower order alarm is generated on the tributary board that interconnects with
the tributary board at the local end.
Issue 02 (2011-06-30)

5-305

System
5 Alarm Reference
If...
Then...
An alarm such as the TU_LOP, TU_AIS, or

DOWN_E1_AIS alarm is generated
Clear the alarm immediately, and then check

whether the UP_E1_AIS alarm is cleared. If
the UP_E1_AIS alarm persists, go to Step
Step 3.
No lower order alarm is generated
Go to Step Step 3.
Step 3 Check whether the tributary unit that is located at the interconnected NE and accesses the 2 Mbit/
s signals reports an alarm indicating that the accessed signals are lost.
If...
Then...
An alarm such as the T_ALOS alarm is

generated
Clear the alarm immediately, and then check

whether the UP_E1_AIS alarm is cleared. If the
UP_E1_AIS alarm persists, go to Step Step 4.
The tributary unit at the opposite end does Go to Step Step 4.

not report an alarm indicating that the
accessed signals are lost
Step 4 If the board works abnormally, the UP_E1_AIS alarm is reported. Perform a cold reset on the
board that reports the alarm by using the NMS, or directly reseat this board. Check whether the
alarm is cleared.
If...
Then...
The alarm persists
Replace the tributary board that reports the alarm, and then check
whether the UP_E1_AIS alarm is cleared. If the UP_E1_AIS alarm
persists, contact Huawei technical support engineers to handle the
alarm.
The alarm is cleared The fault is rectified. End the alarm handling.
----End
Related Information
None.
5.2.207 UP_T1AIS
Description
The UP_T1AIS is an alarm indication of the upstream 1.5 Mbit/s signals. If a tributary board
has detected that the upstream T1 signals are all "1"s, the UP_T1AIS alarm is reported.
5-306

Issue 02 (2011-06-30)

System
5 Alarm Reference
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
Name
Meaning
Parameter 1
Indicates the port number. Value range: 0x01-0x2A

When the UP_T1AIS alarm occurs, the 1.5 Mbit/s services are interrupted. Consequently, the
1.5 Mbit/s services are unavailable.
Possible Causes
The possible causes of the UP_T1AIS alarm are as follows:
l
The TU_LOP, TU_AIS, or DOWN_T1_AIS alarm occurs on the tributary board that
interconnects with the tributary board at the local station.
An alarm such as T_ALOS or UP_T1AIS occurs on the tributary board that is located at
the opposite station and that accesses the 1.5 Mbit/s signals.
The local board is faulty.
Procedure
Step 1 On the U2000, check whether the TU_LOP, TU_AIS, or DOWN_T1_AIS alarm occurs on the
tributary board that interconnects with the tributary board of the local station. If yes, clear it, and
then check whether the UP_T1AIS alarm is cleared.
Step 2 If the alarm persists, check whether any alarm such as T_ALOS or UP_T1AIS occurs on the
tributary board that is located at the opposite station and that accesses the 1.5 Mbit/s signals. If
yes, clear it, and then check whether the UP_T1AIS alarm is cleared.
Step 3 If the alarm persists, replace the relevant board of the opposite station.
Step 4 Replace the board that reports the UP_T1AIS alarm.
----End
Related Information
None.
5.2.208 VCAT_LOA
Issue 02 (2011-06-30)

5-307

System
5 Alarm Reference
Description
The VCAT_LOA is an alarm indicating that the virtual concatenation time delay crosses the
threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the logical port number, and the value is always 1.
Parameter 4
Parameter 5

The services in the downstream direction of the VCTRUNK are interrupted.
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows:
l
The SDH network delay crosses the compensation limit of the virtual concatenation delay.
Procedure
Step 1 Configure the cross-connect loopback to check whether the alarm is cleared.
----End
Related Information
None
5-308

Issue 02 (2011-06-30)

System
5 Alarm Reference
Description
The VCAT_LOM_VC12 is an alarm indicating loss of multiframe of the VC-12 virtual
concatenation.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

Parameter 4
Parameter 5

Possible Causes
The possible causes of the VCAT_LOM_VC12 alarm are as follows:
l
The MFI at the opposite end of the virtual concatenation is inconsistent with that at the
local end.
Bit errors occur or the SDH physical path is interrupted.
Procedure
----End
Related Information
None
Issue 02 (2011-06-30)

5-309

System
5 Alarm Reference
Description
concatenation.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

Parameter 4
Parameter 5

The services at the downstream direction of the VCTRUNK are interrupted.
Possible Causes
l
The MFI at the opposite end of the virtual concatenation is inconsistent with that at the
local end.
Bit errors occur or the SDH physical path is interrupted.
Procedure
----End
5-310

Issue 02 (2011-06-30)

System
5 Alarm Reference
Related Information
None
Description
concatenation. When the system detects that the multi-frame indicator (MFI) field of the H4
byte of VC-4 timeslots is illegal, the system reports the VCAT_LOM_VC4 alarm.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1

Parameter 4
Parameter 5

If the LCAS function is disabled, the services are interrupted during the transmission of data.
Possible Causes
l
The BIP_EXC alarm and BIP_SD alarm occur on the line.
The delay of the virtual concatenation is very long.
The MFI field of the H4 byte sent by the opposite end is incorrect.
Issue 02 (2011-06-30)

5-311

System
5 Alarm Reference
Procedure
Step 2 Check whether the local board reports the BIP_EXC alarm and BIP_SD alarm on the U2000. If
the local board reports the BIP_EXC alarm and BIP_SD alarm, clear the alarms. Then, check
whether the VCAT_LOM_VC4 alarm is cleared.
Step 3 If the VCAT_LOM_VC4 alarm persists, check whether the VCAT_LOA alarm exists on the
U2000. If the VCAT_LOA alarm exists, it indicates that the delay of the virtual concatenation
is very long. Clear the VCAT_LOA alarm. Then, check whether the VCAT_LOM_VC4 alarm
is cleared.
Step 4 If the VCAT_LOM_VC4 alarm persists, check whether the local board that reports the
VCAT_LOM_VC4 alarm is faulty. Replace the local board that reports the VCAT_LOM_VC4
alarm. Then, check whether the VCAT_LOM_VC4 alarm is cleared.
Step 5 If the VCAT_LOM_VC4 alarm persists, the MFI field sent by the opposite SDH end is incorrect.
Replace the corresponding board on the NE at the opposite end. Then, check whether the
VCAT_LOM_VC4 alarm is cleared.
----End
Related Information
None
Description
The VCAT_SQM_VC12 is an alarm indicating SQ mismatch of the VC-12 virtual
concatenation.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
5-312
Name
Meaning
Parameter 1

Issue 02 (2011-06-30)

System
Name
5 Alarm Reference
Meaning

Parameter 4
Parameter 5

Possible Causes
The possible causes of the VCAT_SQM_VC12 alarm are as follows:
l
The SQ transmitted from the virtual concatenation at the opposite end is inconsistent with
the expected SQ at the local end.
Bit errors occur in the SDH physical path or the path is interrupted.
Procedure
----End
Related Information
None
Description
The VCAT_SQM_VC3 is an alarm indicating SQ mismatch of the VC-3 virtual concatenation.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Issue 02 (2011-06-30)

5-313

System
5 Alarm Reference
Name
Meaning
Parameter 1

Parameter 4
Parameter 5

Possible Causes
l
The SQ transmitted from the virtual concatenation at the opposite end is inconsistent with
the expected SQ at the local end.
Bit errors occur in the SDH physical path or the path is interrupted.
Procedure
----End
Related Information
None
Description
The VCAT_SQM_VC4 is an alarm indicating SQ mismatch of the VC-4 virtual concatenation.
The VCAT_SQM_VC4 alarm indicates that the sequence numbers of the members in the VC-4
virtual concatenation do not match each other.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
5-314

Issue 02 (2011-06-30)

System
5 Alarm Reference

table.
Name
Meaning
Parameter 1

Parameter 4
Parameter 5

The data is restructured according to the received sequence numbers during the transmission.
When errors occur during the restructuring, the framing fails and the services are interrupted.
Possible Causes
l
The BIP_EXC alarm and BIP_SD alarm occur on the line.
The sequence number sent by the opposite end is incorrect.
Procedure
Step 1 View the alarm on the U2000, and confirm the board where the VCAT_SQM_VC4 alarm is
generated.
Step 2 Check whether the local board reports the BIP_EXC alarm and BIP_SD alarm on the U2000. If
the local board reports the BIP_EXC alarm and BIP_SD alarm, clear the alarms. Then, check
whether the VCAT_SQM_VC4 alarm is cleared.
Step 3 f the VCAT_SQM_VC4 alarm persists, check whether the local board that reports the
VCAT_SQM_VC4 alarm is faulty. Replace the local board that reports the VCAT_SQM_VC4
alarm. Then, check whether the VCAT_SQM_VC4 alarm is cleared.
Step 4 If the VCAT_SQM_VC4 alarm persists, the sequence number sent by the opposite SDH end is
incorrect. Replace the corresponding board on the NE at the opposite end. Then, check whether
the VCAT_SQM_VC4 alarm is cleared.
----End
Related Information
None
5.2.215 W_R_FAIL
Issue 02 (2011-06-30)

5-315

System
5 Alarm Reference
Description
The W_R_FAIL is an alarm indicating that reading and writing the chip register fail.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

When the W_R_FAIL 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_FAIL alarm is as follows:
l
Procedure
Step 1 Perform a cold reset on, or remove and insert the board that reports the W_R_FAIL alarm.
Step 2 After the board is online again, view alarms on the U2000 to check whether the W_R_FAIL
alarm is cleared.
If...
Then...
Step 3 If the board hardware is faulty, replace the relevant board.
CAUTION
is of risk.
----End
Related Information
None
5-316

Issue 02 (2011-06-30)

System
5 Alarm Reference
5.2.216 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that the board type is incorrect. This alarm occurs
when the types of the logical board and the physical board are different.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None.

The WRG_BD_TYPE alarm does not affect the existing services and the operation of the system.
The slot that generates this alarm, however, cannot be configured with services.
Possible Causes
The possible causes of the WRG_BD_TYPE alarm are as follows:
The types of the logical board and the physical board are different.
Procedure
Step 1 Check whether the types of the logical board and the physical board are different.
If...
Then...
The types of the logical board and the

physical board are the same
Replace the physical board.
The types of the logical board and the

physical board are different
Create a correct logical board based on the

type of the physical board.
----End
Related Information
None.
Issue 02 (2011-06-30)

5-317

System
6 Performance Event Reference
Performance Event Reference
About This Chapter

This topic describes the performance events of the OptiX OSN 550. In this topic, the categories
and the troubleshooting are involved.
6.1 Performance Event List
This section describes the performance events supported by the equipment in a tabular form.
6.2 Performance Event Clearing
Describes how to handle the performance events.
Issue 02 (2011-06-30)

6-1

System
6.1 Performance Event List

This section describes the performance events supported by the equipment in a tabular form.
The performance events of SDH services can be classified into three categories as follows:
pointer justification, bit error, and equipment function.
Table 6-1 Pointer justification performance events
Abbreviation
Details
AUPJCHIGH
Count of positive AU pointer justifications
AUPJCLOW
Count of negative AU pointer justifications
AUPJCNEW
Count of new AU pointer justifications
TUPJCHIGH
Count of negative TU pointer justifications
TUPJCLOW
Count of positive TU pointer justifications
TUPJCNEW
Count of new TU pointer justifications
Table 6-2 E1 line side bit error performance events

Abbreviation
Details
E1_LCV_SDH
Count of E1 line side code violations
E1_LES_SDH
E1 line side code violation errored second
E1_LSES_SDH
E1 line side code violation severely errored second
Table 6-3 Regenerator section bit error performance events
6-2
Abbreviation
Details
RSBBE
Regenerator section block of background error
RSES
Regenerator section errored second
RSSES
Regenerator section severely errored second
RSOOF
Regenerator section out-of-frame
RSOFS
Regenerator section out-of-frame second
RSUAS
Regenerator section unavailable second
RSCSES
Regenerator section consecutive severely errored second

Issue 02 (2011-06-30)

System
Table 6-4 Multiplex section bit error performance events

Abbreviation
Details
MSBBE
Multiplex section block of background error
MSES
Multiplex section errored second
MSSES
Multiplex section severely errored second
MSCSES
Multiplex section consecutive severely errored second
MSUAS
Multiplex section unavailable second
MSFEUAS
Multiplex section far end unavailable second
MSFEES
Multiplex section far end errored second
MSFESES
Multiplex section far end severely errored second
MSFEBBE
Multiplex section far end block of background error
MSFECSES
Multiplex section far end consecutive severely errored second
Table 6-5 Higher order path bit error performance events

Abbreviation
Details
HPBBE
Higher order path block of background error
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 severely errored second
HPFECSES
Higher order path far end consecutive severely errored second
HPUAS
Higher order path unavailable second
HPFEUAS
Higher order path far end unavailable second
Table 6-6 Lower order path bit error performance events
Issue 02 (2011-06-30)
Abbreviation
Details
LPBBE
Lower order path block of background error
LPFEBBE
Lower order path far end block of background error

6-3

System
Abbreviation
Details
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 consecutive severely errored second
LPFECSES
Lower order path far end consecutive severely errored second
LPUAS
Lower order path unavailable second
LPFEUAS
Lower order path far end unavailable second
Table 6-7 T1 line side bit error performance events

Abbreviation
Details
T1_LCV_SDH
Count of T1 line side code violations
T1_LES_SDH
T1 line side code violation errored second
T1_LSES_SDH
T1 line side code violation severely errored second
Table 6-8 Equipment function performance events
6-4
Abbreviation
Details
BDTEMPMAX
Maximum value of board temperature
BDTMPMIN
Minimum value of board temperature
BDTMPCUR
Current value of board temperature
TLBMAX
Maximum value of laser bias current
TLBMIN
Minimum value of laser bias current
TLBCUR
Current value of laser bias current
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

Issue 02 (2011-06-30)

System
Abbreviation
Details
OSPITMPMAX
Maximum value of laser working temperature
OSPITMPMIN
Minimum value of laser working temperature
OSPITMPCUR
Current value of laser working temperature
Table 6-9 VC3 path bit error performance events

Abbreviation
Details
VC3BBE
Lower order path block of background error
VC3FEBBE
Lower order path far end block of background error
VC3ES
Lower order path errored second
VC3FEES
Lower order path far end errored second
VC3SES
Lower order path severely errored second
VC3FESES
Lower order path far end severely errored second
VC3CSES
Lower order path consecutive severely errored second
VC3FECSES
Lower order path far end consecutive severely errored second
VC3UAS
Lower order path unavailable second
VC3FEUAS
Lower order path far end unavailable second
6.2 Performance Event Clearing

Describes how to handle the performance events.
6.2.1 AUPJCHIGH
6.2.2 AUPJCLOW
6.2.3 AUPJCNEW
6.2.4 BDTEMPCUR
6.2.5 BDTEMPMAX
6.2.6 BDTEMPMIN
6.2.7 E1_LCV_SDH
6.2.8 E1_LES_SDH
6.2.9 E1_LSES_SDH
6.2.10 HPBBE
6.2.11 HPCSES
Issue 02 (2011-06-30)

6-5

System
6.2.12 HPES
6.2.13 HPFEBBE
6.2.14 HPFECSES
6.2.15 HPFEES
6.2.16 HPFESES
6.2.17 HPFEUAS
6.2.18 HPSES
6.2.19 HPUAS
6.2.20 LPBBE
6.2.21 LPCSES
6.2.22 LPES
6.2.23 LPFEBBE
6.2.24 LPFECSES
6.2.25 LPFEES
6.2.26 LPFESES
6.2.27 LPFEUAS
6.2.28 LPSES
6.2.29 LPUAS
6.2.30 MSBBE
6.2.31 MSCSES
6.2.32 MSES
6.2.33 MSFEBBE
6.2.34 MSFECSES
6.2.35 MSFEES
6.2.36 MSFESES
6.2.37 MSFEUAS
6.2.38 MSSES
6.2.39 MSUAS
6.2.40 OSPITMPCUR
6.2.41 OSPITMPMAX
6.2.42 OSPITMPMIN
6.2.43 RPLCUR
6.2.44 RPLMAX
6-6

Issue 02 (2011-06-30)

System
6.2.45 RPLMIN
6.2.46 RSBBE
6.2.47 RSCSES
6.2.48 RSES
6.2.49 RSOFS
6.2.50 RSOOF
6.2.51 RSSES
6.2.52 RSUAS
6.2.53 T1_LCV_SDH
6.2.54 T1_LES_SDH
6.2.55 T1_LSES_SDH
6.2.56 TLBCUR
6.2.57 TLBMAX
6.2.58 TLBMIN
6.2.59 TPLCUR
6.2.60 TPLMAX
6.2.61 TPLMIN
6.2.62 TUPJCHIGH
6.2.63 TUPJCLOW
6.2.64 TUPJCNEW
6.2.65 VC3BBE
6.2.66 VC3CSES
6.2.67 VC3ES
6.2.68 VC3FEBBE
6.2.69 VC3FECSES
6.2.70 VC3FEES
6.2.71 VC3FESES
6.2.72 VC3FEUAS
6.2.73 VC3SES
6.2.74 VC3UAS
6.2.1 AUPJCHIGH
Issue 02 (2011-06-30)

6-7

System
Performance Event Meaning

The AUPJCHIGH is a performance event indicating the count of AU pointer high justifications.
Performance Event Attributes

Performance
Event ID
Performance Event Type
0x2a
SDH performance event

A small amount of pointer justification does not affect the services, whereas a large amount of
pointer justification causes bit errors in the services. In this case, detect the causes and
troubleshoot the problem in a timely manner. Otherwise, alarms will be generated and the signal
transmission quality will be affected.
Possible Causes
External causes:
l
A fiber is incorrectly connected, resulting in the mutual clock tracing of the two NEs.
If the NE traces the external clock, check the quality of the external clock.
Human factors:
l
The configuration of the clock source is incorrect. There are two clock sources in one
network.
The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l
The line board is faulty. As a result, the clock is of a bad quality.
The clock unit is faulty. As a result, the clock source is of a bad quality, or the traced clock
source cannot be locked.
Relevant Alarms
6-8
Alarm name
Correlation
MSAD_CROSST
R
Multiplex section adapting performance parameter override alarm
RS_CROSSTR
Regenerator section performance parameter override alarm
MS_CROSSTR
Multiplex section performance parameter override alarm

Issue 02 (2011-06-30)

System
Procedure
Step 1 For non-network-wide pointer justification, check whether a fiber is correctly connected.
Step 2 If the NE traces the external clock, check the quality of the external clock.
Step 3 Ensure that the configuration is correct.
NOTE
Check the configuration items, such as clock ID, SSM protocol, and clock tracing priority.
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. Replace the faulty line board or
clock unit.
----End
Reference
None
6.2.2 AUPJCLOW
The AUPJCLOW is a performance event indicating the count of AU pointer low justifications.

Performance
Event ID
0x2b

Possible Causes
External causes:
l
Human factors:
l
Issue 02 (2011-06-30)
network.
6-9

System
Equipment problems:
l
Relevant Alarms
Alarm name
Correlation
MSAD_CROSST
R
RS_CROSSTR
MS_CROSSTR
Procedure
Step 1 Refer to the 6.2.1 AUPJCHIGH.
----End
Reference
None
6.2.3 AUPJCNEW
The AUPJCNEW is a performance event indicating the count of new AU pointer justifications.

Performance
Event ID
0x2c

6-10

Issue 02 (2011-06-30)

System
Possible Causes
External causes:
l
Human factors:
l
network.
Equipment problems:
l
Relevant Alarms
Alarm name
Correlation
MSAD_CROSST
R
RS_CROSSTR
MS_CROSSTR
Procedure
Step 1 Refer to the 6.2.1 AUPJCHIGH.
----End
Reference
None
6.2.4 BDTEMPCUR
The BDTEMPCUR indicates the current temperature of a board.
Issue 02 (2011-06-30)

6-11

System

Performance
Event ID
0x3A91
Equipment function

Excessively high or low board temperature might cause faults such as degradation of the board
working performance and bit errors.
Possible Causes
The current temperature of the board is displayed.
Relevant Alarms
None.
Procedure
Step 1 If the temperature of the board is within the specified range, do no take any actions.
Step 2 If the temperature of the board is excessively high or low, clear the alarm according to
corresponding handling procedures.
----End
Reference
5.2.196 TEMP_ALARM
6.2.5 BDTEMPMAX
The BDTEMPMAX indicates the maximum temperature of a board.

Performance
Event ID
0x3A8F
Equipment function

6-12

Issue 02 (2011-06-30)

System
Possible Causes
When the ambient temperature is abnormal, or when the heat-sinking and ventilation measures
are improper, the BDTEMP event occurs.
Relevant Alarms
None.
Procedure
----End
Reference
5.2.196 TEMP_ALARM
6.2.6 BDTEMPMIN
The BDTEMPMIN indicates the minimum temperature of a board.

Performance
Event ID
0x3A90
Equipment function

Possible Causes
When the ambient temperature is abnormal, or when the heat-sinking and ventilation measures
are improper, the BDTEMP event occurs.
Relevant Alarms
None.
Issue 02 (2011-06-30)

6-13

System
Procedure
----End
Reference
5.2.196 TEMP_ALARM
6.2.7 E1_LCV_SDH
The E1_LCV_SDH is a performance event indicating the E1 line side code violation count.

Performance
Event ID
0x0c
SDH performance events

If bit errors occur in the services, you need to find out the causes and troubleshoot the problem
in a timely manner. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
The E1_LCV_SDH is a performance event indicating the E1 line side code violation count.
External causes:
l
The fiber performance is degraded, and the fiber has extremely high attenuation.
The fiber connector is dirty or incorrect.
There is a strong interference source around the equipment.
The working temperature is extremely high or extremely low, and the opposite equipment
cannot tolerate such temperature.
Equipment problems:
6-14
Wrong service code types.
Board failure or performance deterioration.

Issue 02 (2011-06-30)

System
Relevant Alarms
None.
Procedure
Step 1 First eliminate external causes, such as poor grounding, too high operating temperature, too low
or too high the receiving optical power of the line board.
Step 2 Check whether the correct E1 service code is selected. If not, modify the code of the services
received by a board by setting the code type of the board.
Step 3 The port of the tributary board may be faulty. Replace the board.
----End
Reference
None.
6.2.8 E1_LES_SDH
The E1_LES_SDH is a performance event indicating the E1 line side code violation errored
second.

Performance
Event ID
0x0d

be affected.
Possible Causes
The E1_LES_SDH is a performance event indicating the E1 line side code violation errored
second.
External causes:
l
Issue 02 (2011-06-30)

6-15

System
Equipment problems:
l
Relevant Alarms
None.
Procedure
Step 1 Refer to the 6.2.7 E1_LCV_SDH.
----End
Reference
None.
6.2.9 E1_LSES_SDH
The E1_LSES_SDH indicates the E1 line side code violation severely errored second.

Performance
Event ID
0x0E

be affected.
Possible Causes
The E1_LSES_SDH is a performance event indicating the E1 line side code violation severely
errored second.
External causes:
6-16

Issue 02 (2011-06-30)

System
Equipment problems:
l
Relevant Alarms
None.
Procedure
Step 1 Refer to the 6.2.7 E1_LCV_SDH.
----End
Reference
None.
6.2.10 HPBBE
The HPBBE is a performance event indicating the higher order path background block error.

Performance
Event ID
0x30

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
HPBBE indicates bit errors that are detected in a verification and exclude the higher order path
unavailable time and higher order path severely errored second.
External causes:
l
Issue 02 (2011-06-30)
6-17

System
The equipment is improperly grounded.
A strong interference source is present near the equipment.
Equipment problems:
l
The signal attenuation at 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.
The synchronization performance of the clock is poor.
The cross-connect unit and the line board poorly match.
The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm name
Correlation
B3_EXC
B3 bit errors crossing the threshold
B3_SD
Signals degraded (B3)
Procedure
Step 1 Eliminate external causes, such as poor grounding, too high operating temperature, too low or
too high the received optical power of the line board. Then, check whether bit errors occur on
the line boards.
Step 2 If all the line boards of an NE have bit errors, the clock unit might be faulty. In this case, replace
the CXL board.
Step 3 If only a line board reports that bit errors exist, it indicates that the local line board might be
faulty or that the opposite NE or fibers are faulty. Perform a loopback to locate the faulty board,
and replace the faulty board or the fibers.
----End
Reference
None
6.2.11 HPCSES
The HPCSES is a performance event indicating the higher order path consecutive severely
errored second.
6-18

Issue 02 (2011-06-30)

System

Performance
Event ID
0x37

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:
l
Equipment problems:
l
Relevant Alarms
Issue 02 (2011-06-30)
Alarm name
Correlation
B3_EXC
B3_SD
R_LOS
The signal on the receiver line side is lost.
R_LOF
The out-of-frame fault occurs on the receiver line side.
MS_AIS
AU_AIS
AU alarm indication
6-19

System
Alarm name
Correlation
AU_LOP
AU pointer loss
HP_UNEQ
High order path unequipped
HP_TIM
High order path trace identifier mismatch
Procedure
Step 1 Refer to the 6.2.12 HPES.
----End
Reference
None
6.2.12 HPES
The HPES is a performance event indicating the higher order path errored second.

Performance
Event ID
0x31

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:
6-20

Issue 02 (2011-06-30)

System
Equipment problems:
l
Relevant Alarms
Alarm name
Correlation
B3_EXC
B3_SD
R_LOS
R_LOF
MS_AIS
AU_AIS
AU alarm indication
AU_LOP
AU pointer loss
HP_UNEQ
HP_TIM
Procedure
Step 1 If the LOS/LOF alarm occurs, a fiber cut, too much attenuation, received overload or faulty
board might exist.
1.
Add an attenuator if the received optical power is overloaded.
2.
Check whether the fiber is intact and whether the optical connector is well connected. Clean
the fiber connector.
3.
Replace the board.
Step 2 The MS_AIS alarm occurs.

1.
Check whether the transmit end of the line board at the opposite station is configured with
insertion of the MS_AIS alarm. If the insertion is set, cancel the setting.
2.
Check whether the transmitting part of the line board on the opposite station is faulty. If
any fault exists, replace the line boards of the opposite station.
3.
Perform a fiber self-loop to check the line board of the local station. Reset or replace the
Issue 02 (2011-06-30)

6-21

System
Step 3 The MS_AIS alarm occurs.

1.
1. For the AU_AIS alarm caused by MS_AIS, R_LOS, and R_LOF, analyze the MS_AIS,
R_LOS, and R_LOF alarms to locate the faults.
2.
2. Another cause might be that the receiving and transmitting of the VC4 path services
mismatch. And this causes that AU-AIS occurs on the VC4 paths. In this case, TU_AIS
occurs on the corresponding TU channels. Check the station on which the AU_AIS alarm
occurs and the stations that communicate services with the AU_AIS station. Check whether
the service timeslots are correctly allocated at the intermediate service pass-through station.
If the configuration is not correct, re-issue the configuration.
3.
Perform a fiber self-loop to check the opposite station. If the alarm persists, replace the
corresponding line board and SCC board.
4.
Perform a fiber self-loop to check the line units of the local station. Check whether the
alarm is cleared through resetting or replacing boards.
Step 4 The AU_LOP alarm occurs.

1.
Check whether the service configuration is correct on the local and opposite stations. If not,
2.
Perform a fiber self-loop to check the opposite station. If the alarm persists, replace the
corresponding SCC board and line board to locate the fault.
3.
Replace the CXL board of the local station.
Step 5 If the HP_UNEQ alarm occurs, check the configuration to determine if the C2 byte is correctly
configured. If not, modify the configuration and reissue it. If yes, it indicates that the board is
faulty. In this case, replace the faulty board.
Step 6 The HP_TIM alarm occurs.
1.
Check whether the J1 configuration of the higher order path in the opposite line board is
consistent with the J1 configuration to be received in the local station. If the configuration
is inconsistent, re-issue the configuration after modification.
2.
Check the service configuration of the opposite station and the local station. If the
configuration is not correct, modify the configuration and re-issue it.
3.
Perform loopbacks at the two stations interconnected. Check the equipment of the local
station and the opposite station. Locate the faulty side and replace the faulty line board and
SCC board.
Step 7 See the 6.2.10 HPBBE.

----End
Reference
None
6.2.13 HPFEBBE
The HPFEBBE is a performance event indicating the higher order path far end background block
error.
6-22

Issue 02 (2011-06-30)

System

Performance
Event ID
0x33

If bit errors occur in the services on a remote NE, detect the causes and troubleshoot the problem
be affected.
Possible Causes
HPFEBBE is an errored block not occurring as part of higher order path far end unavailable time
and higher order path far end severely errored second.
External causes:
l
On the opposite equipment, the fiber performance is degraded, and the fiber has extremely
high attenuation.
The fiber connector is dirty or incorrect at the opposite station.
The opposite equipment is improperly grounded.
There is a strong interference source around the equipment at the opposite station.
Equipment problems:
l
The signal attenuation at 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.
The synchronization performance of the clock is poor at the opposite station.
The cross-connect unit and the line board poorly match at the opposite station.
The fan of the opposite equipment becomes faulty.
The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Issue 02 (2011-06-30)
Alarm name
Correlation
HP_REI

6-23

System
Procedure
Step 1 Refer to the 6.2.10 HPBBE.
----End
Reference
None
6.2.14 HPFECSES
The HPFECSES is a performance event indicating the higher order path far end consecutive
severely errored second.

Performance
Event ID
0x38

be affected.
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:
l
high attenuation.
Equipment problems:
6-24

Issue 02 (2011-06-30)

System
degraded.
Relevant Alarms
Alarm name
Correlation
HP_REI
HP_RDI
Remote defect indication in higher order paths
Procedure
Step 1 Refer to the 6.2.15 HPFEES.
----End
Reference
None
6.2.15 HPFEES
The HPFEES is a performance event indicating the higher order path far end errored second.

Performance
Event ID
0x34

be affected.
Issue 02 (2011-06-30)

6-25

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:
l
high attenuation.
Equipment problems:
l
degraded.
Relevant Alarms
Alarm name
Correlation
HP_REI
HP_RDI
Procedure
Step 1 Refer to the method of handling the 5.2.67 HP_RDI alarm.
Step 2 Refer to the method of handling the 6.2.13 HPFEBBE performance event.
----End
Reference
None
6.2.16 HPFESES
6-26

Issue 02 (2011-06-30)

System

The HPFESES is a performance event indicating the higher order path far end severely errored
second.

Performance
Event ID
0x35

be affected.
Possible Causes
The HPFESES performance event occurs when one of the following requirement 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:
l
high attenuation.
Equipment problems:
l
degraded.
Issue 02 (2011-06-30)

6-27

System
Relevant Alarms
Alarm name
Correlation
HP_REI
HP_RDI
Procedure
----End
Reference
None
6.2.17 HPFEUAS
The HPFEUAS is a performance event indicating the higher order path far end unavailable
second.

Performance
Event ID
0x4C

be affected.
Possible Causes
HPFEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
6-28
high attenuation.

Issue 02 (2011-06-30)

System
Equipment problems:
l
degraded.
Relevant Alarms
Alarm name
Correlation
HP_REI
HP_RDI
Procedure
----End
Reference
None.
6.2.18 HPSES
The HPSES is a performance event indicating the higher order path severely errored second.
Issue 02 (2011-06-30)
Performance
Event ID
0x32

6-29

System

Possible Causes
The HPSES 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:
l
Equipment problems:
l
Relevant Alarms
6-30
Alarm name
Correlation
B3_EXC
B3_SD
R_LOS
R_LOF
MS_AIS
AU_AIS
AU alarm indication
AU_LOP
AU pointer loss
HP_UNEQ
HP_TIM

Issue 02 (2011-06-30)

System
Procedure
Step 1 Refer to the 6.2.12 HPES.
----End
Reference
None
6.2.19 HPUAS
The HPUAS is a performance event indicating the higher order path unavailable second.

Performance
Event ID
0x36

Possible Causes
HPUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Equipment problems:
l
Issue 02 (2011-06-30)
6-31

System
Relevant Alarms
Alarm name
Correlation
B3_EXC
B3_SD
R_LOS
R_LOF
MS_AIS
AU_AIS
AU alarm indication
AU_LOP
AU pointer loss
HP_UNEQ
HP_TIM
Procedure
Step 1 Refer to the 6.2.12 HPES, 5.2.14 B3_EXC, 5.2.17 B3_SD, 5.2.165 R_LOS, 5.2.164 R_LOF,
5.2.121 MS_AIS, 5.2.8 AU_AIS, 5.2.9 AU_LOP, 5.2.72 HP_UNEQ, 5.2.71 HP_TIM.
----End
Reference
None
6.2.20 LPBBE
The LPBBE is a performance event indicating the lower order path block of background error.
6-32
Performance
Event ID
0x90

Issue 02 (2011-06-30)

System

be affected. 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
LPBBE is an errored block not occurring as part of lower order path unavailable time and lower
order path severely errored second. When the service is of the VC12 level, the first two bits of
the V5 byte are verified. When the service is of the VC3 level, the B3 byte is verified.
External causes:
l
Equipment problems:
l
The cross-connect unit and the line unit or the cross-connect unit and the tributary unit
poorly match.
The tributary unit is faulty.
Relevant Alarms
Alarm name
Correlation
BIP_EXC:
Indicates that the BIP bit errors exceed the threshold when the service
level is VC12.
BIP_SD:
Indicates that the BIP signal degraded when the service level is VC12.
B3_EXC
Indicates BIP excessive errors when the service level is VC3.
B3_SD
Indicates that the higher order path (B3) signal degraded when the
service level is VC3.
Procedure
the line boards.
Issue 02 (2011-06-30)

6-33

System
the CXL board.
Step 3 If only a line board reports that bit errors exist, it indicates that the local line unit might be faulty
or that the opposite NE or fibers are faulty. Locate the faulty board and replace it.
Step 4 If only the tributary reports bit errors, the problem may lie in the cooperation of the cross-connect
unit and tributary unit at the local station. Replace the board to verify the faulty point and remove
the fault.
----End
Reference
None
6.2.21 LPCSES
The LPCSES is a performance event indicating the lower order path continuous severe bit error
second.

Performance
Event ID
0x97

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 VC12 level, the first two bits of the V5 byte are verified. When the service
is of the VC3 level, the B3 byte is verified.
External causes:
6-34

Issue 02 (2011-06-30)

System
Equipment problems:
l
poorly match.
Relevant Alarms
Alarm name
Correlation
BIP_EXC
Indicates the BIP bit errors exceed the threshold when the service level
is VC12.
BIP_SD:
B3_EXC
B3_SD
LP_UNEQ
The lower order path is not equipped.
LP_TIM
VC12 level path tracking identifier mismatch
TU_AIS
Indicates the TU alarm indication signal.
TU_LOP
Indicates the TU loss of pointer.
Procedure
Step 1 Refer to the 6.2.22 LPES.
----End
Reference
None
6.2.22 LPES
The LPES is a performance event indicating the lower order path errored second.
Issue 02 (2011-06-30)

6-35

System

Performance
Event ID
0x91

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 VC12 level, the first two
bits of the V5 byte are verified. When the service is of the VC3 level, the B3 byte is verified.
External causes:
l
Equipment problems:
l
poorly match.
Relevant Alarms
6-36
Alarm name
Correlation
BIP_EXC
Indicates the BIP bit errors exceed the threshold when the service level
is VC12.
BIP_SD
B3_EXC

Issue 02 (2011-06-30)

System
Alarm name
Correlation
B3_SD
LP_UNEQ
LP_TIM
TU_AIS
TU_LOP
Procedure
Step 1 When the LP_UNEQ alarm occurs:
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.
2.
Check whether the attributes of the tributary board at local and opposite stations are
correctly configured. If not, modify the incorrect configuration and issue it again.
3.
Check whether the opposite station or the local station is faulty by looping back the fiber.
4.
If the opposite station is faulty, replace the relevant tributary board, line board, and SCC
board in turn.
5.
If the local station is faulty, replace the tributary unit and cross-connect unit in turn.
6.
Check whether the attributes of the tributary board at local and opposite stations are
correctly configured
Step 2 When the LP_TIM alarm occurs:

1.
Check whether the trace identifier of the corresponding lower order path of the opposite
tributary board is the same as that of the local tributary board. If not, modify and re-issue
the configuration.
2.
Check whether the services at the opposite station and the local station are correctly
3.
4.
board in turn.
5.
Step 3 When the TU_AIS alarm occurs:

1.
Check whether any section-level or higher-level alarm occurs on the local line board that
is configured with the lower order services to the tributary board. If yes, clear the alarm
according to the relevant method.
2.
Check whether the PDH alarm occurs at the port that is configured with interconnection
services on the opposite tributary board. If yes, first rectify the fault of the interconnected
PDH equipment.
3.
Check whether the services are correctly configured. If not, modify the incorrect
configuration and issue it again.
4.
Issue 02 (2011-06-30)

6-37

System
5.
board in turn.
6.
Step 4 When the TU_LOP alarm occurs:

1.
Check whether the cross-connect unit or the tributary unit is correctly configured. If yes,
modify the incorrect configuration and issue it again.
2.
3.
board in turn.
4.
Step 5 Refer to the 6.2.20 LPBBE.

----End
Reference
None
6.2.23 LPFEBBE
The LPFEBBE is a performance event indicating the lower order path far end block of
background error.

Performance
Event ID
0x93

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 a timely manner. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
LPFEBBE is an errored block not occurring as part of lower order path far end unavailable time
and lower order path far end severely errored second. When the service is of the VC12 level,
the third bit of the V5 byte is verified. When the service is of the VC3 level, the G1 byte is
verified.
External causes:
6-38

Issue 02 (2011-06-30)

System
high attenuation.
Equipment problems:
l
The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
The opposite NE tributary board is faulty.
degraded.
Relevant Alarms
Alarm name
Correlation
LP_REI
Bit errors occur on the lower order path at the remote end.
Procedure
----End
Reference
None
6.2.24 LPFECSES
The LPFECSES is a performance event indicating the lower order path far end consecutive
Issue 02 (2011-06-30)

6-39

System

Performance
Event ID
0x98

Possible Causes
When a consecutive LPFESES 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:
l
high attenuation.
Equipment problems:
l
degraded.
Relevant Alarms
6-40
Alarm name
Correlation
LP_REI
LP_RDI

Issue 02 (2011-06-30)

System
Procedure
Step 1 Refer to the 6.2.25 LPFEES.
----End
Reference
None
6.2.25 LPFEES
The LPFEES is a performance event indicating the lower order path far end errored second.

Performance
Event ID
0x94

Possible Causes
The LPFEES performance event occurs when one or multiple bit errors are returned in one
second or when the LP_RDI alarm is detected. When the service is of the VC12 level, the third
bit of the V5 byte is verified. When the service is of the VC3 level, the G1 byte is verified.
External causes:
l
high attenuation.
Equipment problems:
Issue 02 (2011-06-30)

6-41

System
degraded.
Relevant Alarms
Alarm name
Correlation
LP_REI
LP_RDI
Procedure
Step 1 The LP_RDI alarm occurs.
1.
Check whether the TU_AIS or the TU_LOP alarm is reported on the corresponding path
of the tributary board at the opposite station. If yes, clear it and the LP_RDI alarm should
be cleared.
2.
If no alarm is reported at the opposite station or if the LP_RDI alarm persists after the
corresponding alarms are cleared, it indicates that the board is faulty. Replace it.

----End
Reference
None
6.2.26 LPFESES
The LPFESES is a performance event indicating the lower order path far end severely errored
second.
6-42

Issue 02 (2011-06-30)

System

Performance
Event ID
0x95

Possible Causes
The LPFESES performance event occurs when one of the following requirement is met:1. Not
less than 30% bit errors are contained in the message returned in one second.2. At least one
10-2, or when the LP_RDI alarm occurs. When the service is of the VC12 level, the third bit of
the V5 byte is verified. When the service is of the VC3 level, the G1 byte is verified.
External causes:
l
high attenuation.
Equipment problems:
l
degraded.
Issue 02 (2011-06-30)

6-43

System
Relevant Alarms
Alarm name
Correlation
LP_REI
LP_RDI
Procedure
----End
Reference
None
6.2.27 LPFEUAS
The LPFEUAS is a performance event indicating the lower order far end unavailable second.

Performance
Event ID
0x8e

Possible Causes
LPFEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
6-44
high attenuation.

Issue 02 (2011-06-30)

System
Equipment problems:
l
degraded.
Relevant Alarms
Alarm name
Correlation
LP_REI
LP_RDI
Procedure
----End
Reference
RSUAS
6.2.28 LPSES
The LPSES is a performance event indicating the lower order path severely errored second.
Issue 02 (2011-06-30)
Performance
Event ID
0x92

6-45

System

be affected. If bit errors exceed the BIP bit threshold and degrade threshold, the BIP_EXC and
BIP_SD alarms will be generated.
Possible Causes
The LPSES 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. SDP occurs when the BER of all the continuous blocks in a period of at least four
continuous blocks or 1 ms (select the longer period) is lower than 10-2, or when the LP_UNEQ,
LP_TIM, TU_AIS or TU_LOP alarm occurs on the path. When the service is of the VC12 level,
the first two bits of the V5 byte are verified. When the service is of the VC3 level, the B3 byte
is verified.
External causes:
l
Equipment problems:
l
poorly match.
Relevant Alarms
6-46
Alarm name
Correlation
BIP_EXC
Indicates that the BIP bit errors exceed the threshold when the service
level is VC12.
BIP_SD
B3_EXC
B3_SD
LP_UNEQ
LP_TIM

Issue 02 (2011-06-30)

System
Alarm name
Correlation
TU_AIS
TU_LOP
Procedure
Step 1 Refer to the 6.2.22 LPES.
----End
Reference
None
6.2.29 LPUAS
The LPUAS is a performance event indicating the lower order path unavailable second.

Performance
Event ID
0x96

in time. Otherwise, alarms will be generated and the signal transmission quality will be affected.
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
LPUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Issue 02 (2011-06-30)

6-47

System
Equipment problems:
l
The cross-connect unit does not match with the line unit or the tributary unit properly.
Relevant Alarms
Alarm Name
Correlation
BIP_EXC
Indicates the BIP bit errors cross the threshold when the service level is
VC12.
BIP_SD
B3_EXC
B3_SD
LP_UNEQ
Indicates that the lower order path is not equipped.
LP_TIM
Indicates the VC12 level path tracking identifier mismatch.
TU_AIS
TU_LOP
Procedure
Step 1 Refer to the 5.2.25 BIP_EXC, 5.2.26 BIP_SD, 5.2.14 B3_EXC, 5.2.17 B3_SD, 5.2.112
LP_UNEQ, 5.2.109 LP_TIM, 5.2.200 TU_AIS, 5.2.203 TU_LOP.
----End
Reference
None
6.2.30 MSBBE
The MSBBE is a performance event indicating the background block error of the multiplex
section (MS).
6-48

Issue 02 (2011-06-30)

System

Performance
Event ID
0x10

If bit errors exceed the B2 bit error threshold-crossing threshold and degrade threshold, the
B2_EXC and B2_SD alarms will be generated.
Possible Causes
MSBBE is an errored block not occurring as part of multiplex section unavailable time and
multiplex section severely errored second.
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B2_EXC
B2_SD
Procedure
the line boards.
Issue 02 (2011-06-30)

6-49

System
the CXL board.
faulty or that the opposite NE or fibers are faulty. Perform a loopback to locate the fault and
replace the faulty board.
----End
Reference
None
6.2.31 MSCSES
The MSCSES is a performance event indicating the consecutive severely errored seconds of the
MS.

Performance
Event ID
0x17

Possible Causes
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:
l
Equipment problems:
6-50

Issue 02 (2011-06-30)

System
Relevant Alarms
Alarm Name
Correlation
B2_EXC
B2_SD
Procedure
Step 1 Refer to the 6.2.32 MSES.
----End
Reference
None
6.2.32 MSES
The MSES is performance event indicating the errored seconds of the MS.

Performance
Event ID
0x11

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.
Issue 02 (2011-06-30)

6-51

System
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B2_EXC
B2_SD
R_LOS
R_LOF
MS_AIS
Procedure
board might exist.
1.
2.
Check the fiber and optical connector. Clean the fiber connector.
3.
Replace the board.
Step 2 If the MS_AIS alarm occurs:
6-52
1.
Check whether the transmit end of the line board at the opposite station is configured with
insertion of the MS_AIS alarm. If yes, cancel the setting.
2.
Check whether the transmitting part of the line board on the opposite station is faulty.
3.
Check the line board of the local station. Perform a reset to the board or replace the board.
Then check whether the alarm is cleared. Perform a fiber self-loop to check whether the
opposite line board reports the MS_AIS alarm.
4.
Check the line unit of the local station. Reset the board. If the alarm persists, replace the
board, and then check whether the alarm is cleared.
Issue 02 (2011-06-30)

System
Step 3 Refer to the 6.2.30 MSBBE, 5.2.12 B2_EXC, 5.2.13 B2_SD.

----End
Reference
None
6.2.33 MSFEBBE
The MSFEBBE is a performance event indicating the multiplex section far end background
block error.

Performance
Event ID
0x13

the problem in time. Otherwise, alarms will be generated and the signal transmission quality
will be affected.
Possible Causes
MSFEBBE is an errored block not occurring as part of multiplex section far end unavailable
time and multiplex section far end severely errored second.
External causes:
l
The fiber performance degrades and the attenuation is excessive at the opposite station.
The equipment is poorly grounded at the opposite station.
Equipment problems:
l
Issue 02 (2011-06-30)

6-53

System
The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name
Correlation
MS_REI
Procedure
Step 1 Refer to the 6.2.30 MSBBE.
----End
Reference
None
6.2.34 MSFECSES
The MSFECSES is a performance event indicating the multiplex section far end consecutive

Performance
Event ID
0x18

will be affected.
Possible Causes
When a consecutive MSFESES sequence is detected, the MSFECSES performance event occurs.
When unavailable time comes or MSFESES is absent in one second, the MSFECSES sequence
ends.
External causes:
6-54

Issue 02 (2011-06-30)

System
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
MS_REI
MS_RDI
A defect occurs at the remote end of the multiplex section.
Procedure
Step 1 Refer to the 6.2.35 MSFEES.
----End
Reference
None
6.2.35 MSFEES
The MSFEES is a performance event indicating the far end errored seconds of the MS.
Issue 02 (2011-06-30)
Performance
Event ID
0x14

6-55

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:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
MS_REI
MS_RDI
Procedure
Step 1 See the 5.2.124 MS_REI and 5.2.123 MS_RDI.
----End
Reference
None
6.2.36 MSFESES
6-56

Issue 02 (2011-06-30)

System

The MSFESES is a performance event indicating the multiplex section far end severely errored
second.

Performance
Event ID
0x15

will be affected.
Possible Causes
The MSFESES performance event occurs when one of the following requirement is met:?1. Not
less than 30% bit errors are contained in the message returned in one second.?2. At least one
10-2, or when the MS_RDI alarm occurs.
External causes:
l
Equipment problems:
l
Issue 02 (2011-06-30)

6-57

System
Relevant Alarms
Alarm Name
Correlation
MS_REI
MS_RDI
Procedure
----End
Reference
None
6.2.37 MSFEUAS
The MSFEUAS is a performance event indicating the multiplex section far end unavailable
second.

Performance
Event ID
0x21

will be affected.
Possible Causes
MSUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
6-58

Issue 02 (2011-06-30)

System
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
MS_REI
MS_RDI
Procedure
----End
Reference
None.
6.2.38 MSSES
The MSSES is a performance event indicating that severely errored seconds occur in the MS.

Performance
Event ID
0x12

Issue 02 (2011-06-30)

6-59

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
or 1 ms (the longer one is selected).
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B2_EXC
B2_SD
R_LOS
R_LOF
MS_AIS
Procedure
Step 1 Refer to the 6.2.32 MSES, 5.2.12 B2_EXC, 5.2.13 B2_SD, 5.2.165 R_LOS, 5.2.164 R_LOF,
5.2.121 MS_AIS.
----End
Reference
None
6-60

Issue 02 (2011-06-30)

System
6.2.39 MSUAS
The MSUAS is a performance event indicating the unavailable seconds of the MS.

Performance
Event ID
0x16

Possible Causes
MSUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Equipment problems:
l
Relevant Alarms
Issue 02 (2011-06-30)
Alarm Name
Correlation
B2_EXC
B2_SD

6-61

System
Alarm Name
Correlation
R_LOS
R_LOF
MS_AIS
Procedure
Step 1 Refer to the 6.2.32 MSES, 5.2.12 B2_EXC, 5.2.13 B2_SD, 5.2.165 R_LOS, 5.2.164 R_LOF,
5.2.121 MS_AIS.
----End
Reference
RSUAS
6.2.40 OSPITMPCUR
The OSPITMPCUR is a performance event indicating the current value of the laser temperature.

Performance
Event ID
0x6e

This performance event does not affect the system. When the laser temperature is too high or
too low, however, the laser does not work properly and therefore services may be interrupted.
Possible Causes
Count the current value of the laser temperature. This is the physical performance, which exists
since the laser is online.
Relevant Alarms
None
6-62

Issue 02 (2011-06-30)

System
Procedure
Step 1 Determine whether the laser temperature is in a normal range. If yes, no measure needs to be
taken. If not, go to the next step.
----End
Reference
None
6.2.41 OSPITMPMAX
The OSPITMPMAX is a performance event indicating the maximum value of the laser
temperature.

Performance
Event ID
0x6c

Possible Causes
Count the maximum value of the temperature of the laser in the current period. This is the
physical performance, which exists since the laser is online.
Relevant Alarms
None
Procedure
----End
Issue 02 (2011-06-30)

6-63

System
Reference
None
6.2.42 OSPITMPMIN
The OSPITMPMIN is a performance event indicating the minimum value of the laser
temperature.

Performance
Event ID
0x6d

Possible Causes
Count the minimum value of the temperature of the laser in the current period. This is the physical
performance, which exists since the laser is online.
Relevant Alarms
None
Procedure
----End
Reference
None
6.2.43 RPLCUR
The RPLCUR is a performance event indicating the current value of output optical power.
6-64

Issue 02 (2011-06-30)

System

Performance
Event ID
0x6b

This performance event does not affect the system. When the input optical power is too high,
the laser is damaged; when the input optical power is too low, the laser cannot detect signals.
NOTE
Check the range of input optical power allowed by the receive port to determine whether the input optical
power is normal.
Possible Causes
Count the current value of the optical power received by the laser. This is the physical
Relevant Alarms
Alarm Name
Correlation
IN_PWR_ABN
The received optical power is abnormal.
Procedure
Step 1 Check the received optical power of the line board. Do as follows according to the value of the
received optical power.
1.
If the optical power is too high, add a signal attenuator to the transmission line.
2.
If the optical power is too low, minimize the signal attenuation during transmission or
increase the transmitted optical power of the opposite station.
3.
If the optical power is normal, replace the board.
----End
Reference
None
6.2.44 RPLMAX
The RPLMAX is a performance event indicating the maximum value of the optical power
received by the laser.
Issue 02 (2011-06-30)

6-65

System

Performance
Event ID
0x69

NOTE
power is normal.
Possible Causes
Count the maximum value of the optical power received by the laser in the current period. This
is the physical performance, which exists since the laser is online.
Relevant Alarms
Alarm Name
Correlation
IN_PWR_ABN
Procedure
Step 1 Refer to the 5.2.75 IN_PWR_ABN.
----End
Reference
None
6.2.45 RPLMIN
The RPLMIN is a performance event indicating the minimum value of the optical power received
by the laser.
6-66

Issue 02 (2011-06-30)

System

Performance
Event ID
0x6a

NOTE
power is normal.
Possible Causes
Count the minimum value of the optical power received by the laser in the current period. This
Relevant Alarms
Alarm Name
Correlation
IN_PWR_ABN
Procedure
Step 1 Refer to the 5.2.75 IN_PWR_ABN.
----End
Reference
None
6.2.46 RSBBE
The RSBBE is a performance event indicating the background block error of the regenerator
section (RS).
Issue 02 (2011-06-30)

6-67

System

Performance
Event ID
0x01

Possible Causes
RSBBE is an errored block excluding bit errors during the regenerator section unavailable time
and regenerator section severely errored second.
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B1_EXC
B1_SD
Procedure
the line boards.
6-68

Issue 02 (2011-06-30)

System
the CXL board.
faulty or that the opposite NE or fibers are faulty. Perform a loopback to locate the faulty board
and replace it.
----End
Reference
None
6.2.47 RSCSES
The RSCSES is a performance event indicating the regenerator section consecutive severely
errored seconds.

Performance
Event ID
0x07

Possible Causes
When a consecutive RSSES sequence is detected, the RSCSES performance event occurs. When
unavailable time comes or RSSES is absent in one second, the RSCSES sequence ends.
External causes:
l
Equipment problems:
Issue 02 (2011-06-30)

6-69

System
Relevant Alarms
Alarm Name
Correlation
B1_EXC
B1_SD
R_LOS
R_LOF
Procedure
Step 1 Refer to the 6.2.48 RSES.
----End
Reference
None
6.2.48 RSES
The RSES is a performance event indicating the errored second of the RS.

Performance
Event ID
0x02

6-70

Issue 02 (2011-06-30)

System
Possible Causes
The RSES performance event occurs when one or multiple bit error blocks are detected within
one second or when the LOS or LOF alarm is detected in a second.
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B1_EXC
B1_SD
R_LOS
R_LOF
Procedure
board might exist.
1.
2.
Check the fiber and optical connector. Clean the fiber connector.
3.
Replace the board.
Step 2 See the 6.2.46 RSBBE.

----End
Reference
None
Issue 02 (2011-06-30)

6-71

System
6.2.49 RSOFS
The RSOFS is a performance event indicating the regenerator section out-of-frame second.

Performance
Event ID
0x05

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 three milliseconds, 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:
l
Equipment problems:
l
Relevant Alarms
6-72
Alarm Name
Correlation
R_OOF
Receive out of frame

Issue 02 (2011-06-30)

System
Alarm Name
Correlation
R_LOF
RS_CROSSTR
Procedure
Step 1 Refer to the 6.2.50 RSOOF.
----End
Reference
None
6.2.50 RSOOF
The RSOOF is a performance event indicating the regenerator section of OOF preference
seconds.

Performance
Event ID
0x04

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 for three milliseconds, 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. In this case, the receive end enters the out-of-frame counting state.
External causes:
l
Issue 02 (2011-06-30)

6-73

System
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
R_OOF
Receive out of frame
R_LOF
RS_CROSSTR
Procedure
Step 1 Add an attenuator if the received optical power is overloaded.
Step 2 Check the fiber and optical connector. Clean the fiber connector.
Step 3 Replace the board.
----End
Reference
None
6.2.51 RSSES
The RSSES is a performance event indicating the severely errored seconds of the RS.
6-74
Performance
Event ID
0x03

Issue 02 (2011-06-30)

System

Possible Causes
The RSSES 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. 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:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B1_EXC
B1_SD
R_LOF
Procedure
Step 1 Refer to the 6.2.48 RSES.
----End
Reference
None
Issue 02 (2011-06-30)

6-75

System
6.2.52 RSUAS
The RSUAS is a performance event indicating regenerator section unavailable second.

Performance
Event ID
0x06

Possible Causes
The RSUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Equipment problems:
l
Relevant Alarms
6-76
Alarm Name
Correlation
B1_EXC
B1_SD

Issue 02 (2011-06-30)

System
Alarm Name
Correlation
R_LOS
R_LOF
Procedure
Step 1 Refer to the 6.2.48 RSES, 5.2.10 B1_EXC, 5.2.11 B1_SD, 5.2.165 R_LOS and 5.2.164
R_LOF.
----End
Reference
UAT starts when the receive end detects ten consecutive SES events. These ten seconds are
contained in the UAT. When the receive end detects ten non-RSSES events, a new available
time (AT) starts. In this case, these ten seconds are contained in the AT.
6.2.53 T1_LCV_SDH
The T1_LCV_SDH is a performance event indicating the T1 line side code violation count.

Performance
Event ID
0xA4
Check and correction

be affected.
Possible Causes
T1_LCV_SDH is the count of detected code violations at the line side of T1 services.
External causes:
l
Issue 02 (2011-06-30)

6-77

System
Equipment problems:
l
Relevant Alarms
None.
Procedure
Step 1 First eliminate external causes, such as poor grounding, too high operating temperature, too low
or too high the receiving optical power of the line board.
Step 2 Check if the T1 service pattern is correct. If it is incorrect, set the pattern of the board to modify
the service pattern that the board receives.
Step 3 The port of the tributary board may be faulty. Replace the board.
----End
Reference
None.
6.2.54 T1_LES_SDH
The T1_LES_SDH is a performance event indicating the T1 line side code violation errored
second.

Performance
Event ID
0xA5

be affected.
Possible Causes
T1_LES_SDH is the count of errored seconds with code violations at the line side of T1 services.
External causes:
6-78

Issue 02 (2011-06-30)

System
Equipment problems:
l
Relevant Alarms
None.
Procedure
Step 1 Refer to the 6.2.53 T1_LCV_SDH.
----End
Reference
None.
6.2.55 T1_LSES_SDH
The T1_LSES_SDH is a performance event indicating the T1 line side code violation severely
errored second.

Performance
Event ID
0xA6

be affected.
Possible Causes
T1_LSES_SDH is the count of severely errored seconds with code violations at the line side of
T1 services.
Issue 02 (2011-06-30)

6-79

System
External causes:
l
Equipment problems:
l
Relevant Alarms
None.
Procedure
Step 1 Refer to the 6.2.53 T1_LCV_SDH.
----End
Reference
None.
6.2.56 TLBCUR
The TLBCUR is a performance event indicating the current value of the bias current of the laser.

Performance
Event ID
0x62

When the bias current of the laser is within the specified range, the equipment and system are
not affected. When the bias current of the laser is beyond the specified range, the laser will fail
or be damaged, and services may be interrupted.
6-80

Issue 02 (2011-06-30)

System
Possible Causes
Count the current value of the bias current transmitted by the laser. This is the physical
Relevant Alarms
Alarm Name
Correlation
LSR_WILL_DIE
The life of the laser is close to the end.
TF
Transmission failure in the laser.
Procedure
Step 1 Refer to the 5.2.119 LSR_WILL_DIE and 5.2.197 TF.
----End
Reference
None.
6.2.57 TLBMAX
The TLBMAX is a performance event indicating the maximum value of the bias current of the
laser.

Performance
Event ID
0x60

Possible Causes
Count the maximum value of the bias current transmitted by the laser in the current period. This
Issue 02 (2011-06-30)

6-81

System
Relevant Alarms
Alarm Name
Correlation
LSR_WILL_DIE
TF
Transmission failure in the laser.
Procedure
----End
Reference
None
6.2.58 TLBMIN
The TLBMIN is a performance event indicating the minimum value of the bias current of the
laser.

Performance
Event ID
0x61

Possible Causes
Count the minimum value of the bias current transmitted by the laser in the current period. This
Relevant Alarms
6-82
Alarm Name
Correlation
LSR_WILL_DIE

Issue 02 (2011-06-30)

System
Procedure
----End
Reference
None
6.2.59 TPLCUR
The TPLCUR is a performance event indicating the current value of the optical power launched
by the laser.

Performance
Event ID
0x68

When the output optical power of the laser is within the specified range, the equipment and
system are not affected. When the output optical power of the laser is beyond the specified range,
the laser will fail or be damaged, and services may be interrupted.
Possible Causes
Count the current value of the optical power launched by the laser. This is the physical
Relevant Alarms
Alarm Name
Correlation
OUT_PWR_ABN
The transmitted optical power is abnormal.
Procedure
Step 1 Refer to the 5.2.146 OUT_PWR_ABN.
----End
Issue 02 (2011-06-30)

6-83

System
Reference
None.
6.2.60 TPLMAX
The TPLMAX is a performance event indicating the maximum value of the optical power
launched by the laser.

Performance
Event ID
0x66

Possible Causes
Count the maximum value of the optical power transmitted by the laser in the current period.
This is the physical performance, which exists since the laser is online.
Relevant Alarms
Alarm Name
Correlation
OUT_PWR_ABN
Procedure
----End
Reference
None
6.2.61 TPLMIN
6-84

Issue 02 (2011-06-30)

System

The TPLMIN is a performance event indicating the minimum value of the optical power
launched by the laser.

Performance
Event ID
0x67

Possible Causes
Count the minimum value of the optical power transmitted by the laser in the current period.
This is the physical performance, which exists since the laser is online.
Relevant Alarms
Alarm Name
Correlation
OUT_PWR_ABN
Procedure
----End
Reference
None
6.2.62 TUPJCHIGH
The TUPJCHIGH is a performance event indicating the count of positive TU pointer
justifications.
Issue 02 (2011-06-30)

6-85

System

Performance
Event ID
0xaa

A small quantity of pointer justification does not affect the services, whereas a large amount of
troubleshoot the problem in time. Otherwise, alarms will be generated and the signal
Possible Causes
External causes:
l
The fibers are incorrectly connected, resulting in the mutual clock tracing of the two NEs.
If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l
network.
Equipment problems:
l
The tributary board is faulty. As a result, the clock is of poor quality.
The timing unit is faulty, providing bad timing source or being unable to lock the traced
timing source.
Relevant Alarms
Alarm Name
Correlation
LP_CROSSTR
Performance threshold-crossing of the lower order path
Procedure
Step 1 For non-network-wide pointer justification, check whether a fiber is correctly connected.
Step 2 If the NE traces the external clock, check the quality of the external clock. If the external clock
is of poor quality, modify the tracing configuration of the external clock.
Step 3 Check whether the configuration is correct. If not, modify the incorrect configuration and issue
it again.
6-86

Issue 02 (2011-06-30)

System
Step 4 Analyze the pointer justification performance events, and locate the faulty point by changing
the position of the clock source and clock tracing direction.
----End
Reference
None
6.2.63 TUPJCLOW
The TUPJCLOW is a performance event indicating the count of negative TU pointer
justifications.

Performance
Event ID
0xab

Possible Causes
External causes:
l
Human factors:
l
network.
Equipment problems:
l
timing source.
Issue 02 (2011-06-30)

6-87

System
Relevant Alarms
Alarm Name
Correlation
LP_CROSSTR
Procedure
Step 1 Refer to the 6.2.62 TUPJCHIGH.
----End
Reference
None
6.2.64 TUPJCNEW
The TUPJCNEW is a performance event indicating the count of new TU pointer justifications.

Performance
Event ID
0xac

Possible Causes
External causes:
l
Human factors:
6-88
network.
Issue 02 (2011-06-30)

System
Equipment problems:
l
timing source.
Relevant Alarms
Alarm Name
Correlation
LP_CROSSTR
Procedure
Step 1 Refer to the 6.2.62 TUPJCHIGH.
----End
Reference
None
6.2.65 VC3BBE
The VC3BBE is a performance event indicating the VC3 background block error.

Performance
Event ID
0x50

Possible Causes
VC3BBE indicates bit errors that are detected in a verification and exlude the higher order path
unavailable time and higher order path severely errored second.
External causes:
Issue 02 (2011-06-30)

6-89

System
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
Procedure
Step 1 Eliminate external causes. For example, the grounding is poor. The operating temperature is too
high. The received optical power of the line board is too low or too high. In this case, perform
the grounding again. Alternatively, find a better operating environment. For more information
about solving the optical power problem, see the 6.2.43 RPLCUR performance. Then, check
whether bit errors occur on the line boards.
the CXL board.
faulty or that the opposite NE or fibers are faulty. Locate the faulty board by using the loopback
method. Then, replace the faulty board with a new one.
----End
Reference
None
6.2.66 VC3CSES
The VC3CSES is a performance event indicating the VC3 continuous severely errored second.
6-90

Issue 02 (2011-06-30)

System

Performance
Event ID
0x57

Possible Causes
When a consecutive VC3CSES sequence is detected, the VC3CSES performance event occurs.
When unavailable time comes or VC3CSES is absent in one second, the VC3CSES sequence
ends.
External causes:
l
Equipment problems:
l
Relevant Alarms
Issue 02 (2011-06-30)
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
R_LOF
MS_AIS
AU_AIS
AU alarm indication
6-91

System
Alarm Name
Correlation
AU_LOP
AU pointer loss
LP_UNEQ_VC3
VC3 path unequipped
LP_TIM_VC3
VC3 path tracing identifier mismatch
Procedure
Step 1 Refer to the 6.2.67 VC3ES.
----End
Reference
None
6.2.67 VC3ES
The VC3ES is a performance event indicating VC3 errorred second.

Performance
Event ID
0x51

Possible Causes
The VC3ES 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, LP_UNEQ_VC3, and LP_TIM_VC3 alarms are detected over
the path.
External causes:
6-92

Issue 02 (2011-06-30)

System
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
R_LOF
MS_AIS
AU_AIS
AU alarm indication
AU_LOP
AU pointer loss
LP_UNEQ_VC3
VC3 path unequipped
LP_TIM_VC3
Procedure
board might exist.
1.
If the received optical power is overloaded, add an attenuator.
2.
heck whether the optical fiber cables are intact and whether the connectors are clean and
well connected. Replace the fibers or clean the fiber connectors, if necessary.
3.
If the board is faulty, replace the board.
Step 2 If the MS_AIS alarm occurs:

1.
Check whether the line board at the opposite station is configured with insertion of the
MS_AIS alarm. If yes, cancel the configuration.
2.
Check whether the transmit unit of the line board on the opposite station is faulty. Check
whether the line board reports the MS_AIS alarm by performing self-loop on the fibers.
3.
Check the line board of the local station. Reset or replace the board. Then, check whether
the MS_AIS alarm is cleared.
Issue 02 (2011-06-30)

6-93

System
Step 3 If the AU_AIS alarm occurs:

1.
For the AU_AIS alarm caused by MS_AIS, R_LOS, and R_LOF, analyze the MS_AIS,
R_LOS, and R_LOF alarms to locate the faults.
2.
Another cause might be that the receiving and transmitting of the VC4 path services
mismatch. And this causes that AU-AIS occurs on the VC4 paths. In this case, TU_AIS
occurs on the corresponding TU channels. Check the station on which the AU_AIS alarm
occurs and the stations that communicate services with the AU_AIS station. Check whether
the service timeslots at the intermediate service pass-through station are correctly
3.
whether the line board reports the MS_AIS alarm by performing self-loop on the fibers. If
the line board is faulty, reset or replace the board. Then, check whether the MS_AIS alarm
is cleared.
4.
If the line unit of the local station is faulty, replace the CXL board at the local station.
Step 4 If the AU_LOP alarm occurs:

1.
Check whether the service configuration is correct at the local and opposite stations. If not,
2.
whether the line board reports the AS_AIS alarm by performing self-loop on the fibers. If
the line board is faulty, reset or replace the board. Then, check whether the AU_AIS alarm
is cleared.
3.
If the line unit of the local station is faulty, replace the CXL board at the local station.
Step 5 If the LP_UNEQ_VC3 alarm occurs:

1.
Check whether the C2 byte is correctly configured. If not, modify the configuration and
redeliver it. If yes, the board is judged to be faulty. And then, replace the faulty board.
Step 6 If the LP_TIM_VC3 alarm occurs:

1.
Check whether the path trace identifier byte to be received at the local station is inconsistent
with that transmitted at the opposite station. If not, modify the configuration and redeliver
it.
2.
Check whether the services are incorrectly configured. If not, modify the configuration and
redeliver it.
Step 7 Refer to the 6.2.65 VC3BBE.

----End
Reference
None
6.2.68 VC3FEBBE
The VC3FEBBE is a performance event indicating the VC3 far end background block error.
6-94

Issue 02 (2011-06-30)

System

Performance
Event ID
0x53

Possible Causes
VC3FEBBE is an errored block not occurring as part of higher order path far end unavailable
time and higher order path far end severely errored second.
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
LP_REI_VC3
VC3 path remote error indication
Procedure
Step 1 Refer to the 6.2.65 VC3BBE.
----End
Issue 02 (2011-06-30)

6-95

System
Reference
None
6.2.69 VC3FECSES
The VC3FECSES is a performance event indicating the VC3 far end consecutive severely
errorred second.

Performance
Event ID
0x58

Possible Causes
When a consecutive VC3FECSES sequence is detected, the VC3FECSES performance event
occurs. When unavailable time comes or VC3FECSES is absent in one second, the VC3FECSES
sequence ends.
External causes:
l
Equipment problems:
6-96
Issue 02 (2011-06-30)

System
Relevant Alarms
Alarm Name
Correlation
LP_REI_VC3
LP_RDI_VC3
VC3 path remote defect indication
Procedure
Step 1 Refer to the 6.2.70 VC3FEES.
----End
Reference
None
6.2.70 VC3FEES
The VC3FEES is a performance event indicating the VC3 far end errored second.

Performance
Event ID
0x54

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:
l
Issue 02 (2011-06-30)

6-97

System
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
LP_REI_VC3
LP_RDI_VC3
Procedure
Step 1 If the LP_RDI_VC3 alarm occurs:
1.
Check whether the line board of the opposite station receives an alarm such as TU_AIS,
TU_LOP, LP_TIM, and LP_UNEQ. If yes, first clear the alarm.
2.
If the line board of the opposite station does not receive an alarm such as TU_AIS, TU_LOP,
LP_TIM, and LP_UNEQ, or if the local station still reports the LP_RDI_VC3 alarm after
the opposite station ends this kind of alarm, check whether the opposite station or the local
station is faulty by looping back the fibers.
3.
If the receive unit of the opposite station is faulty, replace the relevant Ethernet board and
SCC board in turn.
4.
If the transmit part of the local station is faulty, replace the SCC board.
Step 2 Refer to the 6.2.68 VC3FEBBE.

----End
Reference
None.
6.2.71 VC3FESES
The VC3FESES is a performance event indicating the VC3 far end severely errored second.
6-98

Issue 02 (2011-06-30)

System

Performance
Event ID
0x55

Possible Causes
The VC3FESES 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
10-2, or when the LP_RDI alarm occurs.
External causes:
l
Equipment problems:
l
Relevant Alarms
Issue 02 (2011-06-30)
Alarm Name
Correlation
LP_REI_VC3
LP_RDI_VC3

6-99

System
Procedure
----End
Reference
None
6.2.72 VC3FEUAS
The VC3FEUAS is a performance event indicating the VC3 far end unavailable second.

Performance
Event ID
0x59

Possible Causes
VC3FEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Equipment problems:
6-100

Issue 02 (2011-06-30)

System
Relevant Alarms
Alarm Name
Correlation
LP_REI_VC3
LP_RDI_VC3
Procedure
----End
Reference
None.
6.2.73 VC3SES
The VC3SES is a performance event indicating the VC3 far end severely errored second.

Performance
Event ID
0x52

Possible Causes
The VC3SES 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
or one millisecond (the longer one is selected), or the AU_AIS, AU_LOP, HP_UNEQ_VC3,
and HP_TIM_VC3 alarms are detected on the path.
Issue 02 (2011-06-30)

6-101

System
External causes:
l
Equipment problems:
l
Relevant Alarms
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
R_LOF
MS_AIS
AU_AIS
AU alarm indication
AU_LOP
AU pointer loss
LP_UNEQ_VC3
VC3 path unequipped
LP_TIM_VC3
Procedure
----End
Reference
None
6.2.74 VC3UAS
6-102

Issue 02 (2011-06-30)

System

The VC3UAS is a performance event indicating the VC3 unavailable second.

Performance
Event ID
0x56

Possible Causes
VC3UAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Equipment problems:
l
Relevant Alarms
Issue 02 (2011-06-30)
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
R_LOF

6-103

System
Alarm Name
Correlation
MS_AIS
AU_AIS
AU alarm indication
AU_LOP
AU pointer loss
LP_UNEQ_VC3
VC3 path unequipped
LP_TIM_VC3
Procedure
----End
Reference
6.2.74 VC3UAS
6-104

Issue 02 (2011-06-30)

System
A Glossary and Acronyms
Glossary and Acronyms
Terms and abbreviations are listed in an alphabetical order.

A.1 Numerics
A.2 A
A.3 B
A.4 C
A.5 D
A.6 E
A.7 F
A.8 G
A.9 H
A.10 I
A.11 J
A.12 L
A.13 M
A.14 N
A.15 O
A.16 P
A.17 Q
A.18 R
A.19 S
A.20 T
A.21 U
A.22 V
Issue 02 (2011-06-30)

A-1

System
A.23 W
A-2

Issue 02 (2011-06-30)

System
A.1 Numerics
1+1 protection
An architecture that has one normal traffic signal, one working SNC/trail, one protection
SNC/trail and a permanent bridge. At the source end, the normal traffic signal is
permanently bridged to both the working and protection SNC/trail. At the sink end, the
normal traffic signal is selected from the better of the two SNCs/trails. Due to the
permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic
signal to be provided.
100BASE-T
IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area network.
100BASE-TX
IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area network
over two pairs of Category 5 unshielded twisted-pair (UTP) or shielded twisted-pair
(STP) wire.
10BASE-T
An Ethernet specification that uses the twisted pair cable with the transmission speed as
10 Mbit/s and the transmission distance as 100 meters.
1:N protection
An architecture that has N normal service signals, N working SNCs/trails, and one
protection SNC/trail. It may have one extra service signal.
1PPS
Pulse per second, which, strictly speaking, is not a time synchronization signal. This is
because 1PPS provides only the "gauge" corresponding to the UTC second, but does not
provide the information about the day, month, or year. Therefore, 1PPS is used as the
reference for frequency synchronization. On certain occasions, 1PPS can also be used
on other interfaces for high precision timing.
3R
Reshaping, Retiming, Regenerating.
A.2 A
ABR
Available Bit Rate
AC
Alternating Current
ACAP
A channel configuration method, which uses two adjacent channels (a horizontal

polarization wave and a vertical polarization wave) to transmit two signals.
Active/Standby
switching of crossconnect board
The process in which the standby cross-connect board automatically takes the place of
the active one. If there are two cross-connect boards on the SDH equipment, which are
in hot back-up relation of each other, the operation reliability is improved. When both
the cross-connect boards are in position, the one inserted first is in the working status.
Unplug the active board, the standby one will run in the working status automatically.
When the active cross-connect board fails in self-test, the board is pulled out, the board
power supply fails or the board hardware operation fails, the standby cross-connect board
can automatically take the place of the active one.
add/drop multiplexer
Network elements that provide access to all or some subset of the constituent signals
contained within an STM-N signal. The constituent signals are added to (inserted), and/
or dropped from (extracted) the STM-N signal as it passed through the ADM.
ADM
See add/drop multiplexer
Issue 02 (2011-06-30)

A-3

System
Administrative Unit
The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and a AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
Administrative Unit
Group
One or more administrative units occupying fixed, defined positions in an STM payload.
An AUG consists of AU-4s.
Administrator
A user who has authority to access all the Management Domains of the product. He or
she has access to the whole network and to all the management functionalities.
Aging time
The time to live before an object becomes invalid.
AIS
Alarm Indication Signal
Alarm
A message reported when a fault is detected by a device or by the network management

system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
Alarm automatic
report
A function wherein an alarm generated on the device side is immediately and

automatically reported to the NMS. After an alarm is reported, an alarm panel prompts,
and the user can view the details of the alarm.
alarm cable
The cable for generation of visual or audio alarms.
alarm filtering
An alarm management method. Alarms are detected and reported to the NMS system,
and whether the alarm information is displayed and saved is decided by the alarm filtering
status. An alarm with the filtering status set to "Filter" is not displayed and saved on the
NMS, but is monitored on the NE.
alarm indication
A function that indicates the alarm status of an NE. On the cabinet of an NE, there are
four indicators in different colors indicating the current alarm status of the NE. When
the green indicator is on, the NE is powered on. When the red indicator is on, a critical
alarm is generated. When the orange indicator is on, a major alarm is generated. When
the yellow indicator is on, a minor alarm is generated. The ALM alarm indicator on the
front panel of a board indicates the current status of the board.
Alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure
has been detected and alarmed. It is associated with multiple transport layers.
Alarm inversion
For the port that has already been configured but has no service, this function can be
used to avoid generating relevant alarm information, thus preventing alarm interference.
The alarm report condition of the NE port is related to the alarm inverse mode (not
inverse, automatic recovery and manual recovery) setting of the NE and the alarm
inversion status (Enable and Disable) setting of the port. When the alarm inversion mode
of NE is set to no inversion, alarms of the port will be reported as usual no matter whatever
the inversion status of the port is. When the alarm inversion mode of the NE is set to
automatic recovery, and the alarm inversion state of the port is set to Enabled, then the
alarm of the port will be suppressed. The alarm inversion status of the port will
automatically recover to "not inverse" after the alarm ends. For the port that has already
been configured but not actually loaded with services, this function can be used to avoid
generating relevant alarm information, thus preventing alarm interference. When the
alarm inverse mode of the NE is set as "not automatic recovery", if the alarm inversion
status of the port is set as Enable, the alarm of the port will be reported.
Alarm Masking
An alarm management method. Alarms that are set to be masked are not displayed on
the NMS or the NMS does not monitor unimportant alarms.
A-4

Issue 02 (2011-06-30)

System
Alarm Severity
The significance of a change in system performance or events. According to ITU-T

recommendations, an alarm can have one of the following severities: Critical, Major,
Minor, Warning.
Alarm suppression
An alarm management method. Alarms that are set to be suppressed are not reported
from NEs any more.
ALS
See Automatic laser shutdown
APS
See Automatic Protection Switching
asynchronous
Pertaining to, being, or characteristic of something that is not dependent on timing.
Asynchronous
Transfer Mode
A protocol for the transmission of a variety of digital signals using uniform 53 byte cells.
A transfer mode in which the information is organized into cells; it is asynchronous in
the sense that the recurrence of cells depends on the required or instantaneous bit rate.
Statistical and deterministic values may also be used to qualify the transfer mode.
ATM
See Asynchronous Transfer Mode
ATPC
See Automatic Transmit Power Control
attenuation
Reduction of signal magnitude or signal loss, usually expressed in decibels.
AU
See Administrative Unit
AUG
See Administrative Unit Group
auto-negotiation
An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to
automatically exchange information over a link about speed and duplex abilities..
Automatic laser
shutdown
A technique (procedure) to automatically shutdown the output power of laser transmitters

and optical amplifiers to avoid exposure to hazardous levels.
Automatic Protection
Switching
Capability of a transmission system to detect a failure on a working facility and to switch

to a standby facility to recover the traffic.
Automatic Transmit
Power Control
A method of adjusting the transmit power based on fading of the transmit signal detected
at the receiver.
A.3 B
backplane
An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backup
A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth
A range of transmission frequencies that a transmission line or channel can carry in a

network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BDI
Backward Defect Indicator
BER
See Bit Error Rate
BER tester
Used to measure the bit error rate (BER) of signals during transmission.
Binding strap
The binding strap is 12.7 mm wide, with one hook side (made of transparent
polypropylene material) and one mat side (made of black nylon material).
Issue 02 (2011-06-30)

A-5

System
BIP
A method of error monitoring. With even parity an X-bit code is generated by equipment
at the transmit end over a specified portion of the signal in such a manner that the first
bit of the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-bit
sequences within the specified portion, and so on. Even parity is generated by setting the
BIP-X bits so that there is an even number of 1s in each monitored partition of the signal.
A monitored partition comprises all bits which are in the same bit position within the Xbit sequences in the covered portion of the signal. The covered portion includes the BIPX.
Bit error
An incompatibility between a bit in a transmitted digital signal and the corresponding

bit in the received digital signal.
Bit Error Rate
Ratio of received bits that contain errors. BER is an important index used to measure the
communications quality of a network.
BITS
See Building Integrated Timing Supply
bound path
A parallel path with several serial paths bundled together. It improves the data throughput
capacity.
BPDU
See Bridge Protocol Data Unit
BPS
Board Protection Switching
bridge
A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differs from repeaters because bridges
store and forward complete packets, while repeaters forward all electrical signals.
Bridges differ from routers because bridges use physical addresses, while routers use IP
addresses.
Bridge Protocol Data

Unit
The data messages that are exchanged across the switches within an extended LAN that
uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
broadcast
The process of sending packets from a source to multiple destinations. All the ports of
the nodes in the network can receive packets.
Broadcast
A means of delivering information to all members in a network. The broadcast range is

determined by the broadcast address.
BSC
Base Station Controller
BSS
Base Station Subsystem
Build-in WDM
A function which integrates some simple WDM systems into products that belong to the
OSN series. That is, the OSN products can add or drop several wavelengths directly.
Building Integrated
Timing Supply
In the situation of multiple synchronous nodes or communication devices, one can use
a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
BWS
Backbone WDM System
A-6

Issue 02 (2011-06-30)

System
A.4 C
cabling
The method by which a group of insulated conductors is mechanically assembled or

twisted together.
cable trough
The trough which is used for cable routing in the cabinet.
captive nut
See Floating nut
CAR
See committed access rate
CAS
Channel Associated Signaling
CBR
See Constant Bit Rate
CBS
Committed Burst Size
CCDP
Co-Channel Dual Polarization
CCM
Continuity Check Message
CDR
Clock and Data Recovery
CDVT
See Cell Delay Variation Tolerance
Cell Delay Variation

Tolerance
This parameter measures the tolerance level a network interface has to aggressive
sending (back-to-back or very closely spaced cells) by a connected device, and does not
apply to end-systems.
Centralized alarm
system
The system that gathers all the information about alarms into a certain terminal console.
CES
See circuit emulation service
CFM
Connectivity Fault Management
Chain network
One type of network that all network nodes are connected one after one to be in series.
channel
A telecommunication path of a specific capacity and/or at a specific speed between two

or more locations in a network. Channels can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s, kb/s, Mb/s, Gb/s, and Tb/s.
CIR
Committed Information Rate
Circuit
A combination of two transmission channels permitting transmission in both directions

between two points.
circuit emulation
service
A function with which the E1/T1 data can be transmitted through ATM networks. At the
transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
CIST
Common and Internal Spanning Tree
Class of Service
CoS is a rule for queuing. It classifies the packets according to the service type field or
the tag in packets, and specifies different priorities for them. All the nodes in DiffServ
domain forwards the packets according to their priorities.
Issue 02 (2011-06-30)

A-7

System
client
A device that sends requests, receives responses, and obtains services from the server.
Clock Synchronization Also called frequency synchronization. The signal frequency traces the reference
frequency, but the start point does not need to be consistent.
Clock tracing
The method to keep the time on each node being synchronized with a clock source in a
network.
CLP
Cell Loss Priority
CM
See Configuration Management
committed access rate
A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into Quality of Service (QoS) groups, and by which the input or output transmission rate
can be defined.
Concatenation
A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.
Configuration Data
A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other NEs in an entire network. Configuration data is the key factor for
normal running of an entire network.
Configuration
Management
A network management function defined by the International Standards Organization

(ISO). It involves installing, reinitializing & modifying hardware & software.
Configure
To set the basic parameters of an operation object.
congestion
An extra intra-network or inter-network traffic resulting in decreasing network service

efficiency.
Connection point
A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
Constant Bit Rate
A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
Convergence
A process in which multiple channels of low-rate signals are multiplexed into one or
several channels of required signals. It refers to the speed and capability for a group of
networking devices to run a specific routing protocol. It functions to keep the network
topology consistent.
Convergence service
A service that provides enhancements to an underlying service in order to meet the

specific requirements of users.
corrugated tube
Used to protect optical fibers.
CoS
See Class of Service
CPU
Central Processing Unit
CRC
See Cyclic Redundancy Check
current alarm
An alarm not handled or not acknowledged after being handled.
A-8

Issue 02 (2011-06-30)

System
Current Performance
Data
Performance data stored currently in a register. An NE provides two types of registers,

namely, 15-minute register and 24-hour register, to store performance parameters of a
performance monitoring entity. The two types of registers stores performance data only
in the specified monitoring period.
Cyclic Redundancy
Check
A procedure used in checking for errors in data transmission. CRC error checking uses
a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
A.5 D
Data Communication
Network
A communication network used in a TMN or between TMNs to support the data

communication function.
Digital Data Network
A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
DC
Direct Current
DCC
Data Communication Channel
DCD
Data Carrier Detect
DCE
Data Circuit-terminal Equipment
DCN
See Data Communication Network
DDF
See Digital Distribution Frame
DDN
See Digital Data Network
Defect
A limited interruption in the ability of an item to perform a required function.
Delay Measurement
The time elapsed since the start of transmission of the first bit of the frame by a source
node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.
Demultiplexing
A process applied to a composite signal formed by multiplexing, for recovering the

original independent signals, or groups of these signals.
Device set
A collection of multiple managed devices. By dividing managed devices into different

device sets, users can manage the devices by using the U2000 in an easier way. If an
operation authority over one device set is assigned to a user (user group), the authority
over all the devices in the device set is assigned to the user (user group), thus making it
unnecessary to set the operation authority over all the devices in a device set separately.
It is recommended to configure device set by geographical region, network level, device
type, or another criterion.
Differentiated Services A marker in the header of each IP packet that prompts network routers to apply
differentiated grades of service to various packet streams. It is specified by the DiffServ
Code Point
policy proposed by the IETF (Internet Engineering Task Force). This allows Internet and
other IP-based network service providers to offer different levels of service to customers.
Issue 02 (2011-06-30)

A-9

System
DiffServ
A service architecture that provides the end-to-end QoS function. It consists of a series
of functional units implemented at the network nodes, including a small group of perhop forwarding behaviors, packet classification functions, and traffic conditioning
functions such as metering, marking, shaping and policing.
Digital Distribution
Frame
A type of equipment used between the transmission equipment and the exchange with
transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,
cable patching, and test of loops that transmitting digital signals.
digital signal
A signal in which information is represented by a limited number of discrete states

number of discrete states (for example, high and low voltages) rather than by fluctuating
levels in a continuous stream, as in an analog signal. In the pulse code modulation (PCM)
technology, the 8 kHz sampling frequency is used and a byte contains 8 bits in length.
Therefore, a digital signal is also referred to as a byte-based code stream. Digital signals,
with simple structures and broad bandwidth, are easy to shape or regenerate, and are not
easily affected by external interference.
Distributed Link
Aggregation Group
A board-level port protection technology used to detect unidirectional fiber cuts and to
negotiate with the opposite end. Once a link down failure occurs on a port or a hardware
failure occurs on a board, the services can automatically be switched to the slave board,
achieving 1+1 protection for the inter-board ports.
DLAG
See Distributed Link Aggregation Group
DM
See Delay Measurement
DNI
See Dual Node Interconnection
domain
A logical subscriber group based on which the subscriber rights are controlled.
DSCP
See Differentiated Services Code Point
DSL
Digital Subscriber Line
DSLAM
Digital Subscriber Line Access Multiplexer
DSR
Data Set Ready
DTE
Data Terminal Equipments
DTR
Data Terminal Ready
Dual Node
Interconnection
DNI provides an alternative physical interconnection point, between the rings, in case
of an interconnection failure scenario.
DVB-ASI
Digital Video Broadcast- Asynchronous Serial Interface
DVMRP
Distance Vector Multicast Routing Protocol
DWDM
Dense Wavelength Division Multiplexing
A.6 E
E-AGGR
See Ethernet aggregation
Ear bracket
A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
ECC
See Embedded Control Channel
EFM
Ethernet in the First Mile
A-10

Issue 02 (2011-06-30)

System
E-LAN
A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet

virtual connection).
ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
E-Line
A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual

connection).
Embedded Control
Channel
A logical channel that uses a data communications channel (DCC) as its physical layer,
to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
EMS
Element Management System
encapsulation
A technology for layered protocols, in which a lower-level protocol accepts a message

from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP inside
IP.
Enterprise System
Connection
A path protocol which connects the host with various control units in a storage system.
It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
Entity
A part, device, subsystem, functional unit, equipment, or system that can be considered
individually.
EoD
See Ethernet over Dual Domains
EPL
See Ethernet Private Line
EPLAN
See Ethernet virtual private LAN service
Equipment Serial
Number
A string of characters that identify a piece of equipment and ensures correct allocation
of a license file to the specified equipment. It is also called "equipment fingerprint".
ESCON
See Enterprise System Connection
ESD
See ElectroStatic Discharge
ESD jack
Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
ESN
See Equipment Serial Number
Ethernet
A LAN technology that uses Carrier Sense Multiple Access/Collision Detection. The
speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/
s. An Ethernet network features high reliability and is easy to maintain.
Ethernet aggregation
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual

connection).
Ethernet Alarm Group The Ethernet alarm group periodically obtain the statistics value to compare with the
configured threshold. If the value exceeds the threshold, an event is reported.
Ethernet over Dual
Domains
A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet
service transmission across PSN and TDM networks.
Ethernet Private LAN

service
A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
service is carried over a dedicated bridge and point-to-multipoint connections.
Issue 02 (2011-06-30)

A-11

System
Ethernet Private Line
A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet virtual
private LAN service
service is carried over a shared bridge and point-to-multipoint connections.
Ethernet virtual
private line
service is carried over a shared bridge and point-to-point connections.
ETSI
European Telecommunications Standards Institute
EVPL
See Ethernet virtual private line
EVPLAN
See Ethernet virtual private LAN service
Exercise Switching
An operation to check whether the protection switching protocol functions properly. The
protection switching is not really performed.
Exerciser - Ring
This command exercises ring protection switching of the requested channel without
completing the actual bridge and switch. The command is issued and the responses are
checked, but no working traffic is affected.
Extended ID
The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The physical ID of an NE is comprised of the NE ID and extended
ID.
extra traffic
The traffic that is carried over the protection channels when that capacity is not used for
the protection of working traffic. Extra traffic is not protected.
A.7 F
Failure
If the fault persists long enough to consider the ability of an item with a required function
to be terminated. The item may be considered as having failed; a fault has now been
detected.
Fairness
A feature in which for any link specified in a ring network, the source node is provided
with certain bandwidth capacities if the data packets transmitted by the source node are
constrained by the fairness algorithm.
fairness algorithm
An algorithm designed to ensure the fair sharing of bandwidth among stations in the case
of congestion or overloading.
fault
A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources or intentional settings.
FC
See Fiber Channel
FD
See frequency diversity
FDDI
See fiber distributed data interface
FDI
Forward Defect Indicator
FE
Fast Ethernet
feature code
Code used to select/activate a service feature (for example, forwarding, using two or
three digit codes preceded by * or 11 or #, and which may precede subsequent digit
selection).
FEC
See forwarding equivalence class
A-12

Issue 02 (2011-06-30)

System
FEC
See Forward Error Correction
fiber patch cord
A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
Fiber Channel
A high-speed transport technology used to build storage area networks (SANs). Fiber
channel can be on the networks carrying ATM and IP traffic. It is primarily used for
transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode
and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair
copper wires and coaxial cables. Fiber channel provides both connection-oriented and
connectionless services.
Fiber Connect
A new generation connection protocol which connects the host to various control units.
It carries single byte command protocol through the physical path of fiber channel, and
provides higher rate and better performance than ESCON.
Fiber Connector
A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).
fiber distributed data

interface
A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
fiber/cable
General name of optical fiber and cable. It refers to the physical entities that connect the
transmission equipment, carry transmission objects (user information and network
management information) and perform the transmission function in the transmission
network. The optical fiber transmits optical signal, while the cable transmits electrical
signal. The fiber/cable between NEs represents the optical fiber connection or cable
connection between NEs. The fiber/cable between SDH NEs represents the connection
relationship between NEs. At this time, the fiber/cable is of optical fiber type.
FICON
See Fiber Connect
FIFO
First In First Out
Floating nut
Floating nuts (or as they are more correctly named, 'tee nuts') have a range of uses but
are more commonly used in the hobby for engine fixing (securing engine mounts to the
firewall), wing fixings, and undercarriage fixing.
Flow
An aggregation of packets that have the same characteristics. On the network

management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation.
FLR
See Frame loss ratio
Forced switch
For normal traffic signals, switches normal traffic signal to the protection section, unless
an equal or higher priority switch command is in effect or SF condition exists on the
protection section, by issuing a forced switch request for that traffic signal.
Forward Error
Correction
A bit error correction technology that adds the correction information to the payload at
the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
forwarding equivalence A class-based forwarding technology that classifies the packets with the same forwarding
class
mode. Packets with the same FEC are processed similarly on an MPLS network. The
division of FECs is flexible, and can be a combination of the source address, destination
address, source port, destination port, protocol type, and VPN.
Issue 02 (2011-06-30)

A-13

System
FPGA
Field Programmable Gate Array
frame
A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties.
Frame loss ratio
A ratio, is expressed as a percentage, of the number of service frames not delivered

divided by the total number of service frames during time interval T, where the number
of service frames not delivered is the difference between the number of service frames
arriving at the ingress ETH flow point and the number of service frames delivered at the
egress ETH flow point in a point-to-point ETH connection.
Free-run mode
An operating condition of a clock, the output signal of which is strongly influenced by

the oscillating element and not controlled by servo phase-locking techniques. In this
mode the clock has never had a network reference input, or the clock has lost external
reference and has no access to stored data, that could be acquired from a previously
connected external reference. Free-run begins when the clock output no longer reflects
the influence of a connected external reference, or transition from it. Free-run terminates
when the clock output has achieved lock to an external reference.
frequency diversity
A diversity scheme in which two or more microwave frequencies with a certain

frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
FTP
File Transfer Protocol
full-duplex
A full-duplex, or sometimes double-duplex system, allows communication in both

directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line
telephone networks are full-duplex, since they allow both callers to speak and be heard
at the same time. A good analogy for a full-duplex system would be a two-lane road with
one lane for each direction.
A.8 G
Gain
The difference between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
Gateway IP
When an NE accesses a remote network management system or NE, a router can be used
to enable the TCP/IP communication. In this case, the IP address of the router is the
gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot
identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP
networks. An NE may have multiple IP addresses, for example, one IP address of the
network and one IP address of the Ethernet port.
Gateway Network
Element
A network element that is used for communication between the NE application layer and
the NM application layer.
GE
Gigabit Ethernet
Generic Framing
Procedure
A framing and encapsulation method which can be applied to any data type. It has been
standardized by ITU-T SG15.
GFP
See Generic Framing Procedure
A-14

Issue 02 (2011-06-30)

System
GNE
See Gateway Network Element
GPS
Global Positioning System
GSM
Global System for Mobile Communications
GTS
Generic Traffic Shaping
GUI
Graphic User Interface
A.9 H
half-duplex
A transmitting mode in which a half-duplex system provides for communication in both

directions, but only one direction at a time (not simultaneously). Typically, once a party
begins receiving a signal, it must wait for the transmitter to stop transmitting, before
replying.
Hardware loopback
A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
HDLC
High level Data Link Control
HD-SDI
See High Definition-Serial Digital Interface signal
HEC
Header Error Control
Hierarchical Quality of A type of QoS that controls the traffic of users and performs the scheduling according
Service
to the priority of user services. HQoS has an advanced traffic statistics function, and the
administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth
can be allocated reasonably through traffic analysis.
High Definition-Serial High definition video signal transported by serial digital interface.
Digital Interface signal
History alarm
The confirmed alarm that has been saved in the memory and other external memories.
Historical performance The performance data that is stored in the history register or that is automatically reported
data
and stored on the NMS.
HP
Higher Order Path
HPT
Higher Order Path Termination
HQoS
See Hierarchical Quality of Service
A.10 I
IC
Integrated Circuit
IDU
Indoor Unit
IEEE
Institute of Electrical and Electronics Engineers
IETF
Internet Engineering Task Force
IF
Intermediate Frequency
IGMP
See Internet Group Management Protocol
Issue 02 (2011-06-30)

A-15

System
IGMP Snooping
A multicast constraint mechanism running on a layer 2 device. This protocol manages

and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented efficiently.
IMA
See Inverse Multiplexing over ATM
IMA frame
A control unit in the IMA protocol. It is a logical frame defined as M consecutive cells,
numbered 0 to M-l, transmitted on each of the N links in an IMA group.
Input jitter tolerance
The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30second measurement intervals.
Intelligent power
adjusting
A mechanism used to reduce the optical power of all the amplifiers in an adjacent
regeneration section in the upstream to a safety level if the system detects the loss of
optical signals on the link. If the fiber is broken, the device performance degrades, or the
connector is not plugged well, the loss of optical signals may occur. With IPA,
maintenance engineers will not be hurt by the laser sent out from the slice of broken
fiber.
Interface board area
The area for the interface boards on the subrack.
Internal cable
The cables and optical fibers which are used for interconnecting electrical interfaces and
optical interfaces within the cabinet.
Internet Group
Management Protocol
One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
multicast group memberships.
Inverse Multiplexing
over ATM
A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a

cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
IP
Internet Protocol
IP address
A 32-bit (4-byte) binary digit that uniquely identifies a host (computer) connected to the
Internet for communication with other hosts in the Internet by transferring packets. An
IP address is expressed in dotted decimal notation, consisting of decimal values of its 4
bytes, separated by periods (,), for example, 127.0.0.1. The first three bytes of an IP
address identify the network to which the host is connected, and the last byte identifies
the host itself.
IP over DCC
A technology that enables a DCC channel to carry TCP/IP protocol packets. The IP over
DCC technology provides the TCP/IP protocol without using any extra overheads or
service resources to ensure interconnection of management channels.
IPA
See Intelligent power adjusting
IS-IS
Intermedia System-Intermedia System
ISDN
Integrated Services Digital Network
ISO
International Standard Organization
ISP
Internet Service Provider
IST
Internal Spanning Tree
ITU-T
International Telecommunication Union Telecommunication Standardization
A-16

Issue 02 (2011-06-30)

System
A.11 J
Jitter
Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
jitter tolerance
Jitter tolerance is defined as the peak-to-peak amplitude of sinusoidal jitter applied on

the input ATM-PON signal that causes a 1 dB optical power penalty at the optical
equipment.
A.12 L
Label
A short identifier that is of fixed length and local significance. It is used to uniquely
identify the FEC to which a packet belongs. It does not contain topology information. It
is carried in the header of a packet and does not contain topology information.
LACP
See Link Aggregation Control Protocol
LAG
See link aggregation group
LAN
Local Area Network
LAPS
Link Access Procedure-SDH
Laser
A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
Layer
A concept used to allow the transport network functionality to be described hierarchically

as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
layer 2 switch
A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch

transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switch.
LB
See Loopback
LBM
Loopback Message
LBR
Loopback Reply
LC
Lucent Connector
LCAS
See Link Capacity Adjustment Scheme
LCD
Liquid Crystal Display
LCT
Local Craft Terminal
License
A permission that the vendor provides for the user with a specific function, capacity, and
duration of a product. A license can be a file or a serial number. Usually the license
consists of encrypted codes. The operation authority granted varies with the level of the
license.
Link
In the topology view, a link is used to identify the physical or logical connection between
two topological nodes. A link is used to connect signaling points (SPs) and signaling
transfer points (STPs) and transmit signaling messages.
Issue 02 (2011-06-30)

A-17

System
Link Aggregation
Control Protocol
A method of bundling a group of physical interfaces together as a logical interface to

increase bandwidth and reliability. For related protocols and standards, refer to IEEE
802.3ad.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
Link Capacity
Adjustment Scheme
LCAS in the virtual concatenation source and sink adaptation functions provides a
control mechanism to hitless increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the network and element management systems.
LLC
Logical Link Control
LM
See Loss Measurement
Locked switching
When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
LOF
Loss of Frame
LOM
Loss of Multiframe
Loopback
A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
LOS
Loss of Signal
Loss Measurement
Loss measurement, a method used to collect counter values applicable for ingress and
egress service frames where the counters maintain a count of transmitted and received
data frames between a pair of MEPs.
Lower Threshold
A lower performance limit which when exceeded by a performance event counter will
trigger a threshold-crossing event.
LP
Lower Order Path
LPT
Link State Pass Through
LSP
Label Switched Path
LSR
Label Switching Router
LT
Link Trace
A.13 M
MA
See Maintenance Association
MAC
Medium Access Control
Maintenance
Association
TThat portion of a Service Instance, preferably all of it or as much as possible, the

connectivity of which is maintained by CFM. It is also a full mesh of Maintenance
Entities.
A-18

Issue 02 (2011-06-30)

System
Maintenance Domain
The network or the part of the network for which connectivity is managed by connectivity
fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
MAN
See Metropolitan Area Network
Manual switch
Switches normal traffic signal to the protection section, unless a failure condition exists
on other sections (including the protection section) or an equal or higher priority switch
command is in effect, by issuing a manual switch request for that normal traffic signal.
Mapping
A procedure by which tributaries are adapted into virtual containers at the boundary of
an SDH network.
Marking-off template
A quadrate cardboard with four holes. It is used to mark the positions of the installation
holes for the cabinet.
MBS
Maximum Burst Size
MCF
Message Communication Function
MCR
Minimum Cell Rate
MD
See Maintenance Domain
Mean launched power
The average power of a pseudo-random data sequence coupled into the fiber by the
transmitter.
MEP
Maintenance End Point
Metropolitan Area
Network
A network that interconnects users with computer resources in a geographic area or

region larger than that covered by even a large LAN but smaller than the area covered
by an WAN. The term is applied to the interconnection of networks in a city into a single
larger network (which may then also offer efficient connection to a wide area network).
It is also used to mean the interconnection of several local area networks by bridging
them with backbone lines. The latter usage is also sometimes referred to as a campus
network.
MIB
Management Information Base
MIP
Maintenance Intermediate Point
MODEM
MOdulator-DEModulator
MP
Maintenance Point
MPID
Maintenance Point Identification
MPLS
See Multiprotocol Label Switching
MS
Multiplex Section
MSA
Multiplex Section Adaptation
MSOH
See Multiplex Section Overhead
MSP
See Multiplex Section Protection
MST
Multiplex Section Termination
MSTI
Multiple Spanning Tree Instance
MSTP
See Multi-service transmission platform
MSTP
See Multiple Spanning Tree Protocol
MTIE
Maximum Time Interval Error
Issue 02 (2011-06-30)

A-19

System
MTU
Maximum Transmission Unit
Multiprotocol Label
Switching
A technology that uses short tags of fixed length to encapsulate packets in different link
layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
Multi-service
transmission platform
A platform based on the SDH platform, capable of accessing, processing and transmitting
TDM services, ATM services, and Ethernet services, and providing unified management
of these services.
Multicast
A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
Multiple Spanning
Tree Protocol
A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Multiplex Section
Overhead
The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH
definition.
Multiplex Section
Protection
A function, which is performed to provide capability for switching a signal between and
including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
Multiplexing
A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
A.14 N
NE
See network element
NE Explorer
The main operation interface, of the network management system, which is used to
manage the telecommunication equipment. In the NE Explorer, the user can query,
manage and maintain the NE, boards, and ports on a per-NE basis.
network element
An NE contains both the hardware and the software running on it. One NE is at least
equipped with one system control and communication(SCC) board which manages and
monitors the entire network element. The NE software runs on the SCC board.
network node interface The interface at a network node which is used to interconnect with another network node.
network segment
A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
NLP
Normal Link Pulse
NMS
Network Management System
NNI
See network node interface
NPC
Network Parameter Control
A-20

Issue 02 (2011-06-30)

System
nrt-VBR
Non Real-Time Variable Bit Rate
NRZ
Non Return to Zero code
NSAP
Network Service Access Point
NTP
Network Time Protocol
A.15 O
OA
See Optical Amplifier
OADM
See Optical Add/Drop Multiplexer
OAM
Operations, Administration and Maintenance
OAM auto-discovery
In the case of OAM auto-discovery, two interconnected ports, enabled with the Ethernet
in the First Mile OAM (EFM OAM) function, negotiate to determine whether the mutual
EFM OAM configuration match with each other by sending and responding to the OAM
protocol data unit (OAMPDU). If the mutual EFM OAM configuration match, the two
ports enter the EFM OAM handshake phase. In the handshake phase, the two ports
regularly send the OAMPDU to maintain the neighborhood relation.
OCP
See Optical Channel Protection
ODF
See Optical Distribution Frame
ODU
Outdoor Unit
OFS
Out-of-frame Second
OHA
Overhead Access Function
OLT
Optical Line Terminal
Online Help
The capability of many programs and operating systems to display advice or instructions
for using their features when so requested by the user.
ONU
Optical Network Unit
OOF
Out of Frame
Optical Add/Drop
Multiplexer
A device that can be used to add the optical signals of various wavelengths to one channel
and drop the optical signals of various wavelengths from one channel.
Optical Amplifier
Devices or subsystems in which optical signals can be amplified by means of the

stimulated emission taking place in a suitable active medium.
Optical attenuator
A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
Optical Channel
Protection
In an optical transmission link that contains multiple wavelengths, when a certain

wavelength goes faulty, the services at the wavelength can be protected if the optical
channel protection is configured.
Optical Connector
A component normally attached to an optical cable or a piece of apparatus to provide

frequent optical interconnection/disconnection of optical fibers or cables.
Optical Distribution
Frame
A frame which is used to transfer and spool fibers.
Issue 02 (2011-06-30)

A-21

System
Optical Interface
A component that connects several transmit or receive units.
Optical Time Domain

Reflectometer
A device that sends a very short pulse of light down a fiber optic communication system
and measures the time history of the pulse reflection to measure the fiber length, the light
loss and locate the fiber fault.
orderwire
A channel that provides voice communication between operation engineers or

maintenance engineers of different stations.
OSI
Open Systems Interconnection
OSN
Optical Switch Node
OSPF
Open Shortest Path First
OTDR
See Optical Time Domain Reflectometer
OTU
See Optical transponder unit
Optical transponder
unit
A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength.
Output optical power
The ranger of optical energy level of output signals.
Overhead
Extra bits in a digital stream used to carry information besides traffic signals. Orderwire,
for example, would be considered overhead information.
A.16 P
Paired slots
Two slots of which the overheads can be passed through by using the bus on the
backplane.
pass-through
The action of transmitting the same information that is being received for any given
direction of transmission.
Path
A performance resource object defined in the network management system. The left end
of a path is a device node whose port needs to be specified and the right end of a path is
a certain IP address which can be configured by the user. By defining a path in the
network management system, a user can test the performance of a network path between
a device port and an IP address. The tested performance may be the path delay, packet
loss ratio or other aspects.
PBS
Peak Burst Size
PC
Personal Computer
PCM
Pulse Code Modulation
PCR
Peak Cell Rate
PDH
See Plesiochronous Digital Hierarchy
PDU
See Power distribution unit
PE
See provider edge
A-22

Issue 02 (2011-06-30)

System
Performance register
The memory space for performance event counts, including 15-min current performance
register, 24-hour current performance register, 15-min historical performance register,
24-hour historical performance register, UAT register and CSES register. The object of
performance event monitoring is the board functional module, so every board functional
module has a performance register. A performance register is used to count the
performance events taking place within a period of operation time, so as to evaluate the
quality of operation from the angle of statistics.
performance threshold A limit for generating an alarm for a selected entity. When the measurement result
reaches or exceeds the preset alarm threshold, the performance management system
generates a performance alarm.
Permanent Virtual
Connection
A connection between two ATM end hosts. The connection consists of PVPs between
the ATM end hosts and their respective switches, and SVPs between the switches.
PGND
Protection Ground
PGND cable
A cable which connects the equipment and the protection grounding bar. Usually, one
half of the cable is yellow, whereas the other half is green.
PIM-SM
Protocol Independent Multicast-Sparse Mode
PIR
Peak Information Rate
plesiochronous
Qualifying two time-varying phenomena, time-scales, or signals in which corresponding

significant instants occur at the same rate, any variations in rate being constrained within
specified limits. Note: Corresponding significant instants are separated by time intervals
having durations which may vary without limit.
Plesiochronous Digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
Hierarchy
rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
PLL
Phase-Locked Loop
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 this pointer is supported.
POS
Packet Over SDH
Power box
A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
Power distribution unit A unit that performs AC or DC power distribution.

PPP
Point-to-Point Protocol
PRBS
See Pseudo Random Binary Sequence
PRC
Primary Reference Clock
Primitive
In the hierarchy of signaling system No.7, when the upper layer applies for services from
the lower layer or the lower layer transmits services to the upper layer, the data is
exchanged between the user and the service provider. The data transmitted between
adjacent layers is called primitive.
Private Line
A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
Protection path
A specific path that is part of a protection group and is labeled protection.
Protection service
A specific service that is part of a protection group and is labeled protection.
Issue 02 (2011-06-30)

A-23

System
Protection subnet
In the NMS, the protection subnet becomes a concept of network level other than
multiplex section rings or path protection rings. The protection sub-network involves
NEs and fiber cable connections.
Protection View
The user interface, of the NMS, which is used to manage protection in the network.
provider edge
A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
PS
Packet Switched
PSD
Power Spectral Density
Pseudo Random Binary A sequence that is random in a sense that the value of an element is independent of the
Sequence
values of any of the other elements, similar to real random sequences.
Pseudo Wire
An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
Pseudo Sire Emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
edge-to-edge
telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
PVC
See Permanent Virtual Connection
PW
See Pseudo Wire
PWE3
See Pseudo Sire Emulation edge-to-edge
A.17 Q
QinQ
A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It add a public VLAN
tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to
be transmitted over the service providers backbone network based on the public VLAN
tag. This provides a layer 2 VPN tunnel for customers and enables transparent
transmission of packets over private VLANs.
QoS
See Quality of Service
Quality of Service
A commonly-used performance indicator of a telecommunication system or channel.

Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
A.18 R
Rapid Spanning Tree
Protocol
A-24
An evolution of the Spanning Tree Protocol, providing for faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Issue 02 (2011-06-30)

System
RDI
Remote Defect Indication
Receiver Sensitivity
The minimum acceptable value of average received power at point R to achieve a 1 x

10-12 BER (The FEC is open).
Reference clock
A kind of stable and high-precision autonous clock providing frequencies for other clocks
for reference.
REG
A piece of equipment or device that regenerates electrical signals.
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 section
overhead
The regenerator section overhead comprises rows 1 to 3 of the SOH of the STM-N signal.
Remote optical
pumping amplifier
A remote optical amplifier subsystem designed for applications where power supply and
monitoring systems are unavailable. The ROPA subsystem is a power compensation
solution to the ultra-long distance long hop (LHP) transmission.
Resilient Packet Ring
A network topology being developed as a new standard for fiber optic rings.
RF
Radio Frequency
RFA
Request For Announcement
RFI
Request for Information
ring network
A type of network topology in which each node connects to exactly two other nodes,
forming a circular pathway for signals.
RNC
Radio Network Controller
ROPA
See Remote optical pumping amplifier
route
The path that network traffic takes from its source to its destination. In a TCP/IP network,
each IP packet is routed independently. Routes can change dynamically.
router
A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
RP
Rendezvous Point
RPR
See Resilient Packet Ring
RS232
A asynchronous transfer mode that does not involve hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RS422
The specification that defines the electrical characteristics of balanced voltage digital
interface circuits. The interface can change to RS232 via the hardware jumper and others
are the same as RS232.
RSTP
See Rapid Spanning Tree Protocol
RTN
Radio Transmission Node
RX
Receiver
Issue 02 (2011-06-30)

A-25

System
A.19 S
S1 byte
A byte to transmit network synchronization status information. On an SDH network,

each NE traces hop by hop to the same clock reference source through a specific clock
synchronization path, realizing synchronization on the entire network. If a clock
reference source traced by an NE is missing, this NE will trace another clock reference
source of a lower level. To implement protection switching of clocks in the whole
network, the NE must learn about clock quality information of the clock reference source
it traces. Therefore, ITU-T defines S1 byte to transmit network synchronization status
information. It uses the lower four bits of the multiplex section overhead S1 byte to
indicate 16 types of synchronization quality grades. Auto protection switching of clocks
in a synchronous network can be implemented using S1 byte and a proper switching
protocol.
SAN
Storage Area Network
SC
Square Connector
SCR
Sustainable Cell Rate
SD
See space diversity
SD
See Signal Degrade
SD
See Standard definition
SDH
See Synchronous Digital Hierarchy
SDP
Serious Disturbance Period
SD-SDI
See Standard definition-Serial Digital Interface signal
SEC
SDH Equipment Clock
Section
The portion of a SONET transmission facility, including terminating points, between (i)
a terminal network element and a regenerator or (ii) two regenerators. A terminating
point is the point after signal regeneration at which performance monitoring is (or may
be) done.
Self-healing
A function of establishing a replacement connection by network without the network

management connection function. When a connection failure occurs, the replacement
connection is found by the network elements and rerouted depending on network
resources available at that time.
Serial port extended

ECC
The ECC channel realized by means of serial port.
server
A network device that provides services to network users by managing shared resources,
often used in the context of a client-server architecture for a LAN.
Service protection
A measure that ensures that the services can be received at the receive end.
SES
Severely Errored Second
SETS
Synchronous Equipment Timing Source
settings
Parameters of a system or operation that can be selected by the user.
SF
See Signal Fail
A-26

Issue 02 (2011-06-30)

System
Signal Fail
A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
SFP
See Small Form-Factor Pluggable
SHDSL
Single-line High speed Digital Subscriber Line
Side Mode Suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total
Ratio
source spectrum to the second largest peak.
signal cable
Common signal cables cover the E1 cable, network cable, and other non-subscriber
signal cable.
Signal Degrade
SD is a signal indicating the associated data has degraded in the sense that a degraded
defect (e.g., dDEG) condition is active.
Signal Fail
SF is a signal indicating the associated data has failed in the sense that a near-end defect
condition (not being the degraded defect) is active.
Simple Network
Management Protocol
A network management protocol of TCP/IP. It enables remote users to view and modify
the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
slide rail
Angle-bars on which shelves and chassis may slide and be supported within a cabinet or
shelf.
Small Form-Factor
Pluggable
A specification for a new generation of optical modular transceivers.
SMSR
See Side Mode Suppression Ratio
SNC
SubNetwork Connection
SNCMP
See Subnetwork connection multipath protection
SNCP
See SubNetwork Connection Protection
SNCP node
Set the SNC node on the protection sub-network to support sub-network connection
protection that spans protection sub-networks. The SNCP node of the ring sub-network
can support electric circuit dually feed and selectively receive a timeslot out of the ring,
thus implementing sub-network connection protection. The SNCP node is generally set
on the node on the line board with the path protection type of the dual fed and selectively
received.
SNCTP
See Subnetwork Connection Tunnel Protection
SNMP
See Simple Network Management Protocol
SNR
Signal Noise Ratio
space diversity
A diversity scheme that enables two or more antennas separated by a specific distance
to transmit/receive the same signal and selection is then performed between the two
signals to ease the impact of fading. Currently, only receive SD is used.
Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant
network to block some undesirable redundant paths through certain algorithms and prune
a loop network into a loop-free tree network.
SPI
Issue 02 (2011-06-30)
Synchronous Physical Interface

A-27

System
SSM
See Synchronization Status Message
SSU
Synchronization Supply Unit
Standard definition
Standard definition defines a video format with the resolution below 720P.
Standard definitionStandard definition video signal transported by serial digital interface.

Serial Digital Interface
signal
Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be
transmitted across a single physical channel. It dynamically allocates bandwidth only to
active input channels, to make better use of available bandwidth and allow more devices
to be connected than with other multiplexing techniques.
STM-4
SDH standard for transmission over optical fiber at 622.08 Mbit/s.
STP
See Spanning Tree Protocol
Sub-network number
A number used to differentiate network sections in a sub-network conference. A subnetwork ID consists of the first several digits (one or two) of a user phone number. An
order wire phone number consists of the sub-network ID and the user number.
subnet
A type of smaller networks that form a larger network according to a rule, for example,
according to different districts. This facilitates the management of the large network.
subnet mask
The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router matches with the IP address.
Subnetwork connection The only difference is that SNCP is of 1+1 protection and SNCMP is of N+1 protection.
multipath protection
That is, several backup channels protect one active channel in SNCMP.
SubNetwork
A function, which allows a working subnetwork connection to be replaced by a protection
Connection Protection subnetwork connection if the working subnetwork connection fails, or if its performance
falls below a required level.
Subnetwork
Connection Tunnel
Protection
SNCTP provides a VC-4 level channel protection. When the working channel is faulty,
the services of the entire VC-4 path can be switched over to the protection channel.
Support
A part used to support and fix a cabinet on the antistatic floor. It is made of welded steel
plates and is used to block up the cabinets to facilitate floor layout and cabling. Before
the whole set of equipment is grounded, insulation plates must be installed under the
supports, and insulating coverings must be added to the expansion bolts to achieve good
insulation performance.
Suppression state
An attribute set to determine whether an NE monitors the alarm. Under suppression

status, NE will not monitor the corresponding alarm conditions and the alarm will not
occur even when the alarm conditions are met.
SVC
Switching Virtual Connection
Switching priority
A priority of a board that is defined for protection switching. When several protected
boards need to be switched, a switching priority should be set for each board. If the
switching priorities of the boards are the same, services on the board that fails later cannot
be switched. Services on the board with higher priority can preempt the switching
resources of that with lower priority.
A-28

Issue 02 (2011-06-30)

System
Switching restoration
time
It refers to the period of time between the start of detecting and the moment when the
line is switched back to the original status after protection switching occurs in the MSP
sub-network.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message
Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
Synchronous Digital
Hierarchy
A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is used only for signals. SDH is suitable
for the fiber communication system with high speed and a large capacity since it uses
synchronous multiplexing and flexible mapping structure.
Synchronous source
A clock providing timing services to connected network elements. This would include
clocks conforming to Recommendations G.811, G.812 and G.813.
A.20 T
Tandem Connection
Monitor
In the SDH transport hierarchy, the TCM is located between the AU/TU management
layer and HP/LP layer. It uses the N1/N2 byte of POH overhead to monitor the quality
of the transport channels on a transmission section (TCM section).
TCM
See Tandem Connection Monitor
TCP/IP
See Transmission Control Protocol/Internet Protocol
TDM
Time Division Multiplexing
TIM
Trace Identifier Mismatch
Timeslot
Continuously repeating interval of time or a time period in which two devices are able
to interconnect.
Time Synchronization
Also called the moment synchronization, time synchronization means that the
synchronization of the absolute time, which requires that the starting time of the signals
keeps consistent with the UTC time.
TM
Terminal Multiplexer
TMN
Telecommunications Management Network
ToS
See Type of Service
TPS
See Tributary Protection Switch
Trail management
function
A network level management function of the network management system. This function
enables you to configure end-to-end services, view graphic interface and visual routes
of a trail, query detailed information of a trail, filter, search and locate a trail quickly,
manage and maintain trails in a centralized manner, manage alarms and performance
data by trail, and print a trail report.
Transceiver
A transmitter and receiver housed together in a single unit and having some circuits in
common, often for portable or mobile use.
Issue 02 (2011-06-30)

A-29

System
Transmission Control
Protocol/Internet
Protocol
Common name for the suite of protocols developed to support the construction of
worldwide internetworks.
transparent
transmission
A process during which the signaling protocol or data is not processed in the content but
encapsulated in the format for the processing of the next phase.
Tray
A component that can be installed in the cabinet for holding chassis or other devices.
Tributary loopback
A fault can be located for each service path by performing loopback to each path of the
tributary board. There are three kinds of loopback modes: no loopback, outloop, and
inloop.
Tributary Protection
Switch
A function that uses a standby tributary processing board to protect N tributary

processing boards.
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.
Tributary Unit Group
One or more Tributary Units, occupying fixed, defined positions in a higher order VCn payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that
mixed capacity payloads made up of different size Tributary Units can be constructed
to increase flexibility of the transport network.
TTL
Time To Live
TU
Tributary Unit
TUG
See Tributary Unit Group
Tunnel
A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
Type of Service
A field in an IP packet (IP datagram) used for quality of service (QoS). The TOS field
has 8 bits in length, which is divided into five subfields.
A.21 U
UART
Universal Asynchronous Receiver/Transmitter
UAS
Unavailable Second
UBR
Unspecified Bit Rate
underfloor cabling
The cables connected cabinets and other devices are routed underfloor.
UNI
See User-to-Network Interface
Unprotected
Pertaining to the transmission of the services that are not protected. The services cannot
be switched to the protection channel if the working channel is faulty or the service is
interrupted, because protection mechanism is not configured.
Unprotected subnetwork
A sub-network without any protection mechanism. The purpose of such configuration

is to provide the basic data of trail protection for subsequent trail management.
A-30

Issue 02 (2011-06-30)

System
Upload
An operation to report some or all configuration data of an NE to the NMS. The

configuration data then covers the configuration data stored at the NMS side.
UPM
Uninterruptible Power Module
Upper threshold
TThe critical value that can induce unexpected events if exceeded.
UPS
Uninterruptible Power Supply
Upward cabling
Cables or fibers connect the cabinet with other equipment from the top of the cabinet.
User
Any entity external to the network which utilizes connections through the network for
communication. A person or other entity authorized by a subscriber to use some or all
of the services subscribed to by that subscriber.
User-to-Network
Interface
The interface between user equipment and private or public network equipment (for
example, ATM switches).
UTC
Universal Time Coordinated
A.22 V
VB
Virtual Bridge
VBR
Variable Bit Rate
VC
Virtual Concatenation
VC
See Virtual Container
VCG
Virtual Concatenation Group
VCI
Virtual Channel Identifier
Virtual Container
The information structure used to support path layer connections in the SDH. It consists
of information payload and path overhead (POH) information fields organized in a block
frame structure which repeats every 125 or 500 s.
Virtual local area

network
A logical grouping of two or more nodes which are not necessarily on the same physical
network segment but which share the same IP network number. This is often associated
with switched Ethernet.
Virtual Private
Network
A system configuration, where the subscriber is able to build a private network via
connections to different network switches that may include private network capabilities.
VLAN
See Virtual local area network
VP
Virtual Path
VPI
Virtual Path Identifier
VPN
See Virtual Private Network
A.23 W
Wait to Restore
The number of minutes to wait before services are switched back to the working line.
WAN
Wide Area Network
Issue 02 (2011-06-30)

A-31

System
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
10 Hz).
washer
A washer is a thin flat ring of metal or rubber which is placed over a bolt before the nut
is screwed on.
Wavelength Division
Multiplexing
A technology that utilizes the characteristics of broad bandwidth and low attenuation of
single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple
channels to transmit simultaneously in a single fiber.
Wavelength protection Data for describing the wavelength protection structure. Its function is similar to that of
group
the protection subnet for SDH NEs. The wavelength path protection can work only with
the correct configuration of the wavelength protection group.
WDM
See Wavelength Division Multiplexing
WFQ
Weighted Fair Queuing
Winding pipe
A tool for fiber routing, which acts as the corrugated pipe.
Working path
A path allocated to transport the normal traffic.
WRED
Weighted Random Early Detection
WTR
See Wait to Restore
A-32

Issue 02 (2011-06-30)

Huawei OptiX OSN 550 Alarms and Performance Events Reference (V100R003)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Huawei OptiX OSN 550 Alarms and Performance Events Reference (V100R003)

Hochgeladen von

Copyright:

Verfügbare Formate

OptiX OSN 550 Multi-Service CPE Optical

Alarms and Performance Events

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

About This Document

About This Document

OptiX OSN 550

Field maintenance engineer

System maintenance engineer

Indicates a hazard with a high level of risk, which if not

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

About This Document

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Changes in Issue 02 (2011-06-30)

Added the OUT1TEMP_SENSOR_FAIL alarm.

Added the PATCH_ACT_TIMEOUT alarm.

Added the PATCH_DEACT_TIMEOUT alarm.

Added the PATCH_PKGERR alarm.

Changes in Issue 01 (2011-04-06)

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

2 Generating and Detecting an Ethernet Alarm...................................................................... 2-1

3 Generation and Detection of SDH Performance Events....................................................3-1

4 Detecting an Ethernet Performance Event............................................................................4-1

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

6 Performance Event Reference..................................................................................................6-1

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

A Glossary and Acronyms..........................................................................................................A-1

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

Huawei Proprietary and Confidential

OptiX OSN 550 Multi-Service CPE Optical Transmission

1 Generation of Alarms and Performance Events of SDH

Generation of Alarms and Performance

About This Chapter

Huawei Proprietary and Confidential

1 Generation of Alarms and Performance Events of SDH