Documentos de Académico
Documentos de Profesional
Documentos de Cultura
OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02
Cargado por
Keyson FariasDerechos de autor
Formatos disponibles
Compartir este documento
Compartir o incrustar documentos
¿Le pareció útil este documento?
¿Este contenido es inapropiado?
Denunciar este documentoCopyright:
Formatos disponibles
OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02
Cargado por
Keyson FariasCopyright:
Formatos disponibles
OptiX OSN 500/550/580
V100R008C50
Alarms and Performance Events
Reference
Issue 02
Date 2019-01-03
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2019. 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 a 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://e.huawei.com
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. i
OptiX OSN 500/550/580
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 500 V100R008C50
OptiX OSN 550 V100R008C50
OptiX OSN 580 V100R008C50
iManager U2000 V200R018C50
Intended Audience
Based on various services of the OptiX OSN equipment, 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
l System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
DANGER Indicates an imminently hazardous situation
which, if not avoided, will result in death or serious injury.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. ii
OptiX OSN 500/550/580
Alarms and Performance Events Reference About This Document
Symbol Description
WARNING Indicates a potentially hazardous situation
which, if not avoided, could result in death or serious
injury.
CAUTION Indicates a potentially hazardous situation
which, if not avoided, may result in minor or moderate
injury.
NOTICE Indicates a potentially hazardous situation
which, if not avoided, could result in equipment damage,
data loss, performance deterioration, or unanticipated
results. NOTICE is used to address practices not related to
personal injury.
TIP Provides a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or
supplement important points in 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.
Updates in Issue 02 (2019-01-03) Based on Product Version
V100R008C50
This document is the second issue for product version V100R008C50. Compared with Issue
01, this issue includes the following updates:
l OSN 550/580: in "Alarm Clearing", updated information of DB_UNSAVE alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. iii
OptiX OSN 500/550/580
Alarms and Performance Events Reference About This Document
l OSN 550/580: In "Alarm Clearing", added information about
DELAY_ADAPT_INVALID.
l OSN 500/550: in "CES Performance Event List", added information of CES_TX_PKTS
performance event.
Updates in Issue 01 (2018-04-30) Based on Product Version
V100R008C50
This document is the first issue for product version V100R008C50. Compared with
V100R008C30, V100R008C50 includes the following updates:
l In "Alarm Clearing", added information about the following alarms:
– OSN 500: MAC_EXT_EXC.
– OSN 550: AD_CHECK_FAIL, MUT_LOS, MAC_EXT_EXC, NO_BD_PARA,
NO_ELABEL, OA_LOW_GAIN, PUM_BCM_ALM, PUM_TEM_ALM,
PUMP_COOL_EXC, SUM_INPWR_HI, SUM_INPWR_LOW.
– OSN 580: PING_ARP_MISMATCH, PING_LOS.
– OSN 550/580: C3794_SLOTNUM_ERR, C3794_RDI, C3794_AIS, RELAY_LOF,
DB_UNSAVE.
l In "Alarm Clearing", updated information about the following alarms:
– OSN 500/550: MPLS_TUNNEL_UNEXPMEP, MPLS_TUNNEL_UNEXPMEG,
MPLS_PW_UNEXPMEP, MPLS_PW_UNEXPMEG, MPLS_PW_MISMATCH,
MPLS_PW_MISMERGE, MPLS_TUNNEL_MISMATCH,
MPLS_TUNNEL_MISMERGE.
– OSN 550: BUS_ERR.
– OSN 580: HARD_ERR.
– OSN 550/580: LOF_64K, HARD_BAD.
l In "Performance Event Reference", added information about the following performance
events:
– OSN 550: BCV, CCV, EDTMP, SUMIOP, SUMOOP, WCV, XCSTMP.
– OSN 550/580: C3794_LCV_SDH, C3794_LES_SDH, C3794_LSES_SDH.
– OSN 500/550: Added the performance events PKT64, PKT65, PKT128, PKT256,
PKT512, and PKT1024 in section of "Statistics of RMON Extended Performance
(packet)".
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. iv
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
Contents
About This Document.....................................................................................................................ii
1 Generation of Alarms and Performance Events of SDH Services....................................... 1
1.1 Overview........................................................................................................................................................................ 2
1.1.1 Directions and Levels of Signal Flows........................................................................................................................3
1.1.2 Two Common Alarms..................................................................................................................................................3
1.1.3 Alarm Management..................................................................................................................................................... 4
1.2 Generation and Detection of Alarms and Performance Events in the SDH Higher Order Signal Flow........................ 7
1.2.1 Downlink Signal Flow.................................................................................................................................................7
1.2.2 Uplink Signal Flow....................................................................................................................................................11
1.3 Generation and Detection of Alarms and Performance Events in the SDH Lower Order Signal Flow.......................12
1.3.1 Downlink Signal Flow...............................................................................................................................................13
1.3.2 Uplink Signal Flow....................................................................................................................................................14
1.3.3 Difference Between Alarm Signals of PDH Ports at Various Rates..........................................................................15
1.4 Suppression Correlation Between SDH Alarms...........................................................................................................16
1.4.1 Intra-Board Alarm Suppression.................................................................................................................................16
1.4.2 Inter-board Alarm Suppression..................................................................................................................................17
1.5 Generation and Detection of SDH Performance Events...............................................................................................18
1.5.1 Bit Errors................................................................................................................................................................... 18
1.5.2 Pointer Justification................................................................................................................................................... 22
2 Detecting and Reporting an Ethernet Alarm......................................................................... 26
2.1 Alarm Reporting Flow..................................................................................................................................................26
2.2 Alarm Correlation.........................................................................................................................................................28
3 Detecting Ethernet Performance Events................................................................................. 31
4 Alarm Reference.......................................................................................................................... 33
4.1 Alarm List.....................................................................................................................................................................33
4.1.1 Alarm List A.............................................................................................................................................................. 33
4.1.2 Alarm List B.............................................................................................................................................................. 35
4.1.3 Alarm List C.............................................................................................................................................................. 37
4.1.4 Alarm List D.............................................................................................................................................................. 39
4.1.5 Alarm List E.............................................................................................................................................................. 42
4.1.6 Alarm List F...............................................................................................................................................................44
4.1.7 Alarm List H.............................................................................................................................................................. 46
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. v
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.1.8 Alarm List I............................................................................................................................................................... 47
4.1.9 Alarm List J............................................................................................................................................................... 48
4.1.10 Alarm List K............................................................................................................................................................ 48
4.1.11 Alarm List L.............................................................................................................................................................49
4.1.12 Alarm List M........................................................................................................................................................... 52
4.1.13 Alarm List N............................................................................................................................................................ 57
4.1.14 Alarm List O............................................................................................................................................................ 58
4.1.15 Alarm List P.............................................................................................................................................................61
4.1.16 Alarm List R............................................................................................................................................................ 64
4.1.17 Alarm List S.............................................................................................................................................................65
4.1.18 Alarm List T............................................................................................................................................................ 68
4.1.19 Alarm List U............................................................................................................................................................ 70
4.1.20 Alarm List V............................................................................................................................................................ 70
4.1.21 Alarm List W........................................................................................................................................................... 72
4.2 Alarm Clearing............................................................................................................................................................. 72
4.2.1 A_LOC...................................................................................................................................................................... 73
4.2.2 ACR_LOCK_FAIL....................................................................................................................................................75
4.2.3 AD_CHECK_FAIL................................................................................................................................................... 77
4.2.4 ALM_ALS.................................................................................................................................................................78
4.2.5 ALM_E1RAI............................................................................................................................................................. 79
4.2.6 ALM_GFP_dCSF...................................................................................................................................................... 80
4.2.7 ALM_GFP_dLFD..................................................................................................................................................... 82
4.2.8 ALM_IMA_LIF.........................................................................................................................................................84
4.2.9 ALM_IMA_LODS.................................................................................................................................................... 87
4.2.10 ALM_IMA_RE_RX_UNUSABLE.........................................................................................................................89
4.2.11 ALM_IMA_RE_TX_UNUSABLE......................................................................................................................... 92
4.2.12 ALM_IMA_RFI...................................................................................................................................................... 94
4.2.13 APS_FAIL............................................................................................................................................................... 96
4.2.14 APS_INDI............................................................................................................................................................... 98
4.2.15 APS_MANUAL_STOP.........................................................................................................................................100
4.2.16 ARP_FAIL.............................................................................................................................................................100
4.2.17 ARP_MAC_MISMATCH..................................................................................................................................... 102
4.2.18 ARP_SPOOF......................................................................................................................................................... 103
4.2.19 ATMPW_UNKNOWNCELL_EXC......................................................................................................................104
4.2.20 AU_AIS................................................................................................................................................................. 105
4.2.21 AU_LOP................................................................................................................................................................ 107
4.2.22 B1_EXC.................................................................................................................................................................109
4.2.23 B1_SD....................................................................................................................................................................111
4.2.24 B2_EXC.................................................................................................................................................................113
4.2.25 B2_SD....................................................................................................................................................................115
4.2.26 B3_EXC.................................................................................................................................................................117
4.2.27 B3_EXC_VC3....................................................................................................................................................... 119
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. vi
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.28 B3_EXC_VC4....................................................................................................................................................... 121
4.2.29 B3_SD................................................................................................................................................................... 123
4.2.30 B3_SD_VC3.......................................................................................................................................................... 125
4.2.31 B3_SD_VC4.......................................................................................................................................................... 128
4.2.32 BAT1TEMP_SENSOR_FAIL............................................................................................................................... 130
4.2.33 BAT2TEMP_SENSOR_FAIL............................................................................................................................... 131
4.2.34 BD_NOT_INSTALLED........................................................................................................................................132
4.2.35 BD_STATUS......................................................................................................................................................... 133
4.2.36 BD_VER_NMAT.................................................................................................................................................. 135
4.2.37 BD_VER_NOT_MATCH..................................................................................................................................... 137
4.2.38 BDID_ERROR...................................................................................................................................................... 139
4.2.39 BDTEMP_SENSOR_FAIL................................................................................................................................... 140
4.2.40 BEFFEC_EXC.......................................................................................................................................................141
4.2.41 BIOS_STATUS......................................................................................................................................................143
4.2.42 BIP_EXC............................................................................................................................................................... 144
4.2.43 BIP_SD.................................................................................................................................................................. 147
4.2.44 BOOTROM_BAD.................................................................................................................................................150
4.2.45 BRDCASTRATIO_OVER.................................................................................................................................... 151
4.2.46 BUS_ERR..............................................................................................................................................................152
4.2.47 BUS_LOC............................................................................................................................................................. 160
4.2.48 BWUTILIZATION_OVER................................................................................................................................... 161
4.2.49 C2_VCAIS.............................................................................................................................................................162
4.2.50 C3794_SLOTNUM_ERR..................................................................................................................................... 164
4.2.51 C3794_RDI............................................................................................................................................................165
4.2.52 C3794_AIS............................................................................................................................................................ 166
4.2.53 CES_ACR_LOCK_ABN...................................................................................................................................... 168
4.2.54 CES_APS_INDI.................................................................................................................................................... 170
4.2.55 CES_APS_MANUAL_STOP............................................................................................................................... 172
4.2.56 CES_JTROVR_EXC.............................................................................................................................................173
4.2.57 CES_JTRUDR_EXC.............................................................................................................................................174
4.2.58 CES_K1_K2_M.....................................................................................................................................................176
4.2.59 CES_K2_M........................................................................................................................................................... 177
4.2.60 CES_LOSPKT_EXC.............................................................................................................................................178
4.2.61 CES_MALPKT_EXC........................................................................................................................................... 180
4.2.62 CES_MISORDERPKT_EXC................................................................................................................................181
4.2.63 CES_RDI............................................................................................................................................................... 182
4.2.64 CES_STRAYPKT_EXC........................................................................................................................................184
4.2.65 CESPW_OPPOSITE_ACFAULT......................................................................................................................... 185
4.2.66 CESPW_OPPOSITE_RAI.................................................................................................................................... 186
4.2.67 CFCARD_FAILED............................................................................................................................................... 187
4.2.68 CFCARD_FULL................................................................................................................................................... 188
4.2.69 CFCARD_OFFLINE.............................................................................................................................................189
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. vii
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.70 CFG_DATACHECK_FAIL................................................................................................................................... 191
4.2.71 CFG_DATASAVE_FAIL.......................................................................................................................................193
4.2.72 CHCS.....................................................................................................................................................................194
4.2.73 CHIP_ABN............................................................................................................................................................195
4.2.74 CLK_LOCK_FAIL................................................................................................................................................196
4.2.75 CLK_NO_TRACE_MODE...................................................................................................................................199
4.2.76 COM_EXTECC_FULL.........................................................................................................................................200
4.2.77 COMMUN_FAIL.................................................................................................................................................. 201
4.2.78 CPU_BUSY...........................................................................................................................................................203
4.2.79 CRC4_ERR_OVER...............................................................................................................................................204
4.2.80 CTS........................................................................................................................................................................ 205
4.2.81 DB_RESTORE_FAIL........................................................................................................................................... 206
4.2.82 DBMS_DELETE...................................................................................................................................................207
4.2.83 DBMS_ERROR.....................................................................................................................................................208
4.2.84 DBMS_PROTECT_MODE...................................................................................................................................211
4.2.85 DB_UNSAVE........................................................................................................................................................ 212
4.2.86 DCC_CHAN_LACK.............................................................................................................................................213
4.2.87 DCD.......................................................................................................................................................................214
4.2.88 DCN_CHANNEL_BITERROR............................................................................................................................ 215
4.2.89 DCNSIZE_OVER................................................................................................................................................. 221
4.2.90 DDN_AIS.............................................................................................................................................................. 222
4.2.91 DDN_ALOS.......................................................................................................................................................... 223
4.2.92 DDN_CRC4_ERR_OVER.................................................................................................................................... 225
4.2.93 DDN_LFA............................................................................................................................................................. 226
4.2.94 DDN_LMFA..........................................................................................................................................................227
4.2.95 DDN_LOOP_ALM............................................................................................................................................... 229
4.2.96 DDN_RFA............................................................................................................................................................. 230
4.2.97 DDN_RMFA..........................................................................................................................................................230
4.2.98 DELAY_ADAPT_INVALID.................................................................................................................................231
4.2.99 DSR....................................................................................................................................................................... 232
4.2.100 DTR..................................................................................................................................................................... 233
4.2.101 DLAG_PROTECT_FAIL....................................................................................................................................234
4.2.102 DOWN_E1_AIS.................................................................................................................................................. 236
4.2.103 DOWN_T1_AIS.................................................................................................................................................. 238
4.2.104 DROPRATIO_OVER.......................................................................................................................................... 240
4.2.105 E1DCN_64K_CONFLICT.................................................................................................................................. 242
4.2.106 E1DCN_SNCP_MM........................................................................................................................................... 243
4.2.107 E1_LOC...............................................................................................................................................................244
4.2.108 E1_LOS............................................................................................................................................................... 245
4.2.109 ELAN_SMAC_FLAPPING................................................................................................................................ 246
4.2.110 ENVHUM_SENSOR_FAIL................................................................................................................................ 247
4.2.111 ENVTEMP_SENSOR_FAIL...............................................................................................................................249
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. viii
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.112 ENVTEMP1_SENSOR_FAIL.............................................................................................................................250
4.2.113 ENVTEMP2_SENSOR_FAIL.............................................................................................................................251
4.2.114 ERPS_BLOCK.................................................................................................................................................... 253
4.2.115 ERPS_NOT_COMPLETE...................................................................................................................................254
4.2.116 ERPS_IN_PROTECTION...................................................................................................................................255
4.2.117 ETH_APS_LOST................................................................................................................................................ 256
4.2.118 ETH_APS_PATH_MISMATCH..........................................................................................................................257
4.2.119 ETH_APS_SWITCH_FAIL................................................................................................................................ 258
4.2.120 ETH_APS_TYPE_MISMATCH......................................................................................................................... 259
4.2.121 ETH_CFM_AIS...................................................................................................................................................260
4.2.122 ETH_CFM_LOC................................................................................................................................................. 262
4.2.123 ETH_CFM_MISMERGE.................................................................................................................................... 264
4.2.124 ETH_CFM_RDI.................................................................................................................................................. 267
4.2.125 ETH_CFM_UNEXPERI..................................................................................................................................... 269
4.2.126 ETH_EFM_DF.................................................................................................................................................... 271
4.2.127 ETH_EFM_EVENT............................................................................................................................................ 272
4.2.128 ETH_EFM_LOOPBACK....................................................................................................................................273
4.2.129 ETH_EFM_REMFAULT.................................................................................................................................... 275
4.2.130 ETH_LINK_DOWN........................................................................................................................................... 276
4.2.131 ETH_LOS............................................................................................................................................................ 277
4.2.132 ETH_NO_FLOW................................................................................................................................................ 279
4.2.133 ETHOAM_DISCOVER_FAIL............................................................................................................................280
4.2.134 ETHOAM_RMT_CRIT_FAULT........................................................................................................................ 282
4.2.135 ETHOAM_RMT_LOOP..................................................................................................................................... 283
4.2.136 ETHOAM_RMT_SD.......................................................................................................................................... 285
4.2.137 ETHOAM_SELF_LOOP.................................................................................................................................... 286
4.2.138 ETHOAM_VCG_SELF_LOOP.......................................................................................................................... 288
4.2.139 EX_ETHOAM_CC_LOS.................................................................................................................................... 289
4.2.140 EX_ETHOAM_MPID_CNFLCT....................................................................................................................... 292
4.2.141 EXT_SYNC_LOS............................................................................................................................................... 294
4.2.142 EXT_TIME_LOC................................................................................................................................................295
4.2.143 FAN_AGING.......................................................................................................................................................297
4.2.144 FAN_COMM_FAIL............................................................................................................................................ 298
4.2.145 FAN_FAIL........................................................................................................................................................... 299
4.2.146 FAN_FAULT....................................................................................................................................................... 300
4.2.147 FCS_ERR............................................................................................................................................................ 301
4.2.148 FDBSIZEALM_ELAN....................................................................................................................................... 303
4.2.149 FEATURE_WITHOUT_LICENSE.....................................................................................................................304
4.2.150 FIB_LEN_CHANGE...........................................................................................................................................307
4.2.151 FIBER_ASYMMETRIC_CHANGED................................................................................................................308
4.2.152 FLOW_OVER..................................................................................................................................................... 310
4.2.153 FUSE_ALARM................................................................................................................................................... 311
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. ix
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.154 FXO_POWER_FAULT....................................................................................................................................... 313
4.2.155 FXS_LINE_FAULT.............................................................................................................................................314
4.2.156 FXS_POWER_FAULT........................................................................................................................................316
4.2.157 HARD_BAD....................................................................................................................................................... 317
4.2.158 HARD_ERR........................................................................................................................................................ 342
4.2.159 HARD_NONSUPPORT...................................................................................................................................... 346
4.2.160 HP_CROSSTR.................................................................................................................................................... 347
4.2.161 HP_LOM............................................................................................................................................................. 349
4.2.162 HP_R_FIFO.........................................................................................................................................................351
4.2.163 HP_RDI............................................................................................................................................................... 352
4.2.164 HP_REI................................................................................................................................................................353
4.2.165 HP_SLM.............................................................................................................................................................. 355
4.2.166 HP_T_FIFO......................................................................................................................................................... 358
4.2.167 HP_TIM...............................................................................................................................................................359
4.2.168 HP_UNEQ........................................................................................................................................................... 361
4.2.169 HPAD_CROSSTR............................................................................................................................................... 362
4.2.170 HSC_UNAVAIL.................................................................................................................................................. 364
4.2.171 HPS_WP_LATEN_DIFF.....................................................................................................................................366
4.2.172 HPS_WP_LATEN_JITTER................................................................................................................................ 368
4.2.173 IGSP_ENTRIES_EXC........................................................................................................................................ 369
4.2.174 IMA_GROUP_LE_DOWN.................................................................................................................................371
4.2.175 IMA_GROUP_RE_DOWN................................................................................................................................ 372
4.2.176 IMA_TXCLK_MISMATCH............................................................................................................................... 374
4.2.177 IN_PWR_ABN.................................................................................................................................................... 375
4.2.178 IN_PWR_HIGH.................................................................................................................................................. 377
4.2.179 IN_PWR_LOW................................................................................................................................................... 378
4.2.180 INSUFFCNT_FLSH_SPACE..............................................................................................................................380
4.2.181 INSUFFCNT_MEM_SPACE..............................................................................................................................381
4.2.182 INTEMP_SENSOR_FAIL.................................................................................................................................. 382
4.2.183 J0_MM.................................................................................................................................................................384
4.2.184 K1_K2_M............................................................................................................................................................ 385
4.2.185 K2_M...................................................................................................................................................................386
4.2.186 KMC_KEY_SYNC_FAIL...................................................................................................................................387
4.2.187 LAG_DOWN.......................................................................................................................................................388
4.2.188 LAG_MEMBER_DOWN................................................................................................................................... 389
4.2.189 LAG_PORT_FAIL.............................................................................................................................................. 390
4.2.190 LAN_LOC........................................................................................................................................................... 392
4.2.191 LASER_CHECK_ERR....................................................................................................................................... 393
4.2.192 LASER_CLOSED............................................................................................................................................... 394
4.2.193 LASER_MOD_ERR........................................................................................................................................... 395
4.2.194 LASER_MOD_ERR_EX.................................................................................................................................... 396
4.2.195 LASER_MODULE_MISMATCH...................................................................................................................... 397
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. x
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.196 LASER_SHUT.................................................................................................................................................... 398
4.2.197 LASER_TYPE_MISMATCH............................................................................................................................. 399
4.2.198 LCAS_FOPR....................................................................................................................................................... 400
4.2.199 LCAS_FOPT....................................................................................................................................................... 401
4.2.200 LCAS_PLCR....................................................................................................................................................... 402
4.2.201 LCAS_PLCT....................................................................................................................................................... 403
4.2.202 LCAS_TLCR.......................................................................................................................................................404
4.2.203 LCAS_TLCT....................................................................................................................................................... 405
4.2.204 LCD..................................................................................................................................................................... 406
4.2.205 LCS_DAYS_OF_GRACE...................................................................................................................................408
4.2.206 LCS_EXPIRED................................................................................................................................................... 411
4.2.207 LCS_FILE_NOT_EXIST.................................................................................................................................... 413
4.2.208 LFA...................................................................................................................................................................... 415
4.2.209 LINK_ERR.......................................................................................................................................................... 416
4.2.210 LMFA.................................................................................................................................................................. 418
4.2.211 LOF_64K............................................................................................................................................................. 419
4.2.212 LOOP_ALM........................................................................................................................................................ 422
4.2.213 LP_CROSSTR.....................................................................................................................................................424
4.2.214 LP_R_FIFO......................................................................................................................................................... 426
4.2.215 LP_RDI................................................................................................................................................................427
4.2.216 LP_RDI_VC12.................................................................................................................................................... 428
4.2.217 LP_RDI_VC3...................................................................................................................................................... 429
4.2.218 LP_REI................................................................................................................................................................ 431
4.2.219 LP_REI_VC12.....................................................................................................................................................432
4.2.220 LP_REI_VC3.......................................................................................................................................................433
4.2.221 LP_RFI................................................................................................................................................................ 435
4.2.222 LP_SIZE_ERR.................................................................................................................................................... 436
4.2.223 LP_SLM.............................................................................................................................................................. 436
4.2.224 LP_SLM_VC12...................................................................................................................................................437
4.2.225 LP_SLM_VC3.....................................................................................................................................................439
4.2.226 LP_T_FIFO......................................................................................................................................................... 440
4.2.227 LP_TIM............................................................................................................................................................... 441
4.2.228 LP_TIM_VC12....................................................................................................................................................442
4.2.229 LP_TIM_VC3......................................................................................................................................................443
4.2.230 LP_UNEQ........................................................................................................................................................... 444
4.2.231 LP_UNEQ_VC12................................................................................................................................................ 446
4.2.232 LP_UNEQ_VC3.................................................................................................................................................. 447
4.2.233 LPS_UNI_BI_M..................................................................................................................................................448
4.2.234 LPT_AUTH_FAIL.............................................................................................................................................. 450
4.2.235 LPT_CFG_CLOSEPORT....................................................................................................................................451
4.2.236 LPT_RFI.............................................................................................................................................................. 453
4.2.237 LSR_BCM_ALM................................................................................................................................................ 454
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xi
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.238 LSR_COOL_ALM.............................................................................................................................................. 455
4.2.239 LSR_NO_FITED.................................................................................................................................................456
4.2.240 LSR_WILL_DIE................................................................................................................................................. 457
4.2.241 LTI....................................................................................................................................................................... 458
4.2.242 MAC_FCS_EXC................................................................................................................................................. 460
4.2.243 MAC_EXT_EXC................................................................................................................................................ 462
4.2.244 MASTER_SLAVE_MISMATCH........................................................................................................................463
4.2.245 MCLAG_CFG_MISMATCH.............................................................................................................................. 464
4.2.246 MCSP_PATH_LOCV.......................................................................................................................................... 466
4.2.247 MDL_ALARM.................................................................................................................................................... 467
4.2.248 MOD_COM_FAIL.............................................................................................................................................. 468
4.2.249 MOD_TYPE_MISMATCH.................................................................................................................................470
4.2.250 MP_DELAY........................................................................................................................................................ 471
4.2.251 MP_DOWN......................................................................................................................................................... 472
4.2.252 MPLS_PW_AIS.................................................................................................................................................. 474
4.2.253 MPLS_PW_BDI.................................................................................................................................................. 475
4.2.254 MPLS_PW_CSF..................................................................................................................................................476
4.2.255 MPLS_PW_Excess..............................................................................................................................................478
4.2.256 MPLS_PW_LCK.................................................................................................................................................479
4.2.257 MPLS_PW_LOCK.............................................................................................................................................. 480
4.2.258 MPLS_PW_LOCV.............................................................................................................................................. 482
4.2.259 MPLS_PW_MISMATCH....................................................................................................................................484
4.2.260 MPLS_PW_MISMERGE....................................................................................................................................486
4.2.261 MPLS_PW_OAMFAIL.......................................................................................................................................487
4.2.262 MPLS_PW_RDI.................................................................................................................................................. 489
4.2.263 MPLS_PW_SD....................................................................................................................................................491
4.2.264 MPLS_PW_SF.................................................................................................................................................... 492
4.2.265 MPLS_PW_UNEXPMEG...................................................................................................................................494
4.2.266 MPLS_PW_UNEXPMEP................................................................................................................................... 497
4.2.267 MPLS_PW_UNEXPPER.................................................................................................................................... 498
4.2.268 MPLS_PW_UNKNOWN....................................................................................................................................499
4.2.269 MPLS_TUNNEL_AIS........................................................................................................................................ 501
4.2.270 MPLS_TUNNEL_BDI........................................................................................................................................ 502
4.2.271 MPLS_TUNNEL_EXCESS................................................................................................................................ 503
4.2.272 MPLS_TUNNEL_FDI........................................................................................................................................ 504
4.2.273 MPLS_TUNNEL_LOCK.................................................................................................................................... 505
4.2.274 MPLS_TUNNEL_LOCV.................................................................................................................................... 506
4.2.275 MPLS_TUNNEL_MISMATCH..........................................................................................................................508
4.2.276 MPLS_TUNNEL_MISMERGE..........................................................................................................................509
4.2.277 MPLS_TUNNEL_OAMFAIL.............................................................................................................................510
4.2.278 MPLS_TUNNEL_RDI........................................................................................................................................ 511
4.2.279 MPLS_TUNNEL_SD..........................................................................................................................................512
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xii
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.280 MPLS_TUNNEL_SF.......................................................................................................................................... 513
4.2.281 MPLS_TUNNEL_UNEXPMEG.........................................................................................................................514
4.2.282 MPLS_TUNNEL_UNEXPMEP......................................................................................................................... 518
4.2.283 MPLS_TUNNEL_UNEXPPER.......................................................................................................................... 519
4.2.284 MPLS_TUNNEL_UNKNOWN..........................................................................................................................520
4.2.285 MRING_APS_LOST_E...................................................................................................................................... 521
4.2.286 MRING_APS_LOST_W.....................................................................................................................................523
4.2.287 MRING_APS_MISMATCH_E........................................................................................................................... 524
4.2.288 MRING_APS_MISMATCH_W..........................................................................................................................525
4.2.289 MRING_FAR_SW_FAIL_E............................................................................................................................... 527
4.2.290 MRING_FAR_SW_FAIL_W.............................................................................................................................. 528
4.2.291 MRING_OAM_LOCV_E................................................................................................................................... 529
4.2.292 MRING_OAM_LOCV_W.................................................................................................................................. 531
4.2.293 MRING_OAM_RDI_E....................................................................................................................................... 532
4.2.294 MRING_OAM_RDI_W...................................................................................................................................... 534
4.2.295 MRING_OAM_SD_E......................................................................................................................................... 535
4.2.296 MRING_OAM_SD_W........................................................................................................................................537
4.2.297 MRING_OAM_SF_E..........................................................................................................................................538
4.2.298 MRING_OAM_SF_W........................................................................................................................................ 539
4.2.299 MRING_OAM_UNEXPMEG_E........................................................................................................................ 540
4.2.300 MRING_OAM_UNEXPMEG_W.......................................................................................................................542
4.2.301 MRING_OAM_UNEXPMEP_E.........................................................................................................................544
4.2.302 MRING_OAM_UNEXPMEP_W....................................................................................................................... 545
4.2.303 MRING_OAM_UNEXPPER_E......................................................................................................................... 546
4.2.304 MRING_OAM_UNEXPPER_W........................................................................................................................ 547
4.2.305 MS_AIS............................................................................................................................................................... 548
4.2.306 MS_CROSSTR....................................................................................................................................................550
4.2.307 MS_RDI...............................................................................................................................................................552
4.2.308 MS_REI............................................................................................................................................................... 553
4.2.309 MSAD_CROSSTR.............................................................................................................................................. 554
4.2.310 MULTI_RPL_OWNER....................................................................................................................................... 556
4.2.311 MUT_LOS........................................................................................................................................................... 557
4.2.312 NE_POWER_OVER........................................................................................................................................... 558
4.2.313 NEBD_XC_DIF.................................................................................................................................................. 559
4.2.314 NEIP_CONFUSION........................................................................................................................................... 560
4.2.315 NESF_LOST....................................................................................................................................................... 562
4.2.316 NESOFT_MM..................................................................................................................................................... 563
4.2.317 NESTATE_INSTALL..........................................................................................................................................565
4.2.318 NO_BD_PARA....................................................................................................................................................566
4.2.319 NO_BD_POWER................................................................................................................................................ 567
4.2.320 NO_BD_SOFT.................................................................................................................................................... 567
4.2.321 NO_ELABEL...................................................................................................................................................... 569
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xiii
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.322 NO_LSR_PARA_FILE....................................................................................................................................... 570
4.2.323 NTP_SYNC_FAIL.............................................................................................................................................. 571
4.2.324 NULL_SEND...................................................................................................................................................... 573
4.2.325 OA_LOW_GAIN................................................................................................................................................ 574
4.2.326 OCD.....................................................................................................................................................................575
4.2.327 ODC_BATTERY_CURRENT_ABN.................................................................................................................. 576
4.2.328 ODC_BATTERY_PWRDOWN.......................................................................................................................... 577
4.2.329 ODC_DOOR_OPEN........................................................................................................................................... 579
4.2.330 ODC_FAN_FAILED........................................................................................................................................... 581
4.2.331 ODC_HUMI_ABN..............................................................................................................................................582
4.2.332 ODC_LOAD_PWRDOWN.................................................................................................................................584
4.2.333 ODC_MDL_ABN............................................................................................................................................... 586
4.2.334 ODC_POWER_FAIL.......................................................................................................................................... 588
4.2.335 ODC_SMOKE_OVER........................................................................................................................................ 590
4.2.336 ODC_SURGE_PORTECTION_FAIL................................................................................................................ 592
4.2.337 ODC_TEC_ALM................................................................................................................................................ 594
4.2.338 ODC_TEMP_ABN..............................................................................................................................................594
4.2.339 ODC_WATER_ALM...........................................................................................................................................596
4.2.340 ODUk_LOFLOM................................................................................................................................................ 598
4.2.341 ODUk_PM_AIS.................................................................................................................................................. 600
4.2.342 ODUk_PM_BDI.................................................................................................................................................. 603
4.2.343 ODUk_PM_DEG.................................................................................................................................................605
4.2.344 ODUk_PM_LCK.................................................................................................................................................607
4.2.345 ODUk_PM_OCI.................................................................................................................................................. 608
4.2.346 ODUk_PM_SSF.................................................................................................................................................. 610
4.2.347 ODUk_PM_TIM..................................................................................................................................................611
4.2.348 ODUk_TCMn_AIS............................................................................................................................................. 612
4.2.349 ODUk_TCMn_BDI............................................................................................................................................. 613
4.2.350 ODUk_TCMn_DEG............................................................................................................................................614
4.2.351 ODUk_TCMn_LCK............................................................................................................................................ 615
4.2.352 ODUk_TCMn_LTC.............................................................................................................................................616
4.2.353 ODUk_TCMn_OCI............................................................................................................................................. 617
4.2.354 ODUk_TCMn_SSF............................................................................................................................................. 618
4.2.355 ODUk_TCMn_TIM.............................................................................................................................................619
4.2.356 OOL..................................................................................................................................................................... 621
4.2.357 OPU1_MSIM.......................................................................................................................................................622
4.2.358 OPUk_PLM......................................................................................................................................................... 623
4.2.359 OTUk_AIS...........................................................................................................................................................624
4.2.360 OTUk_BDI.......................................................................................................................................................... 626
4.2.361 OTUk_DEG.........................................................................................................................................................628
4.2.362 OTUk_LOF......................................................................................................................................................... 629
4.2.363 OTUk_LOM........................................................................................................................................................ 631
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xiv
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.364 OTUk_SSF.......................................................................................................................................................... 633
4.2.365 OTUk_TIM..........................................................................................................................................................634
4.2.366 OUT_PWR_ABN................................................................................................................................................ 635
4.2.367 OUT_PWR_HIGH.............................................................................................................................................. 636
4.2.368 OUT_PWR_LOW............................................................................................................................................... 639
4.2.369 OUT1TEMP_SENSOR_FAIL............................................................................................................................ 641
4.2.370 OUT2TEMP_SENSOR_FAIL............................................................................................................................ 642
4.2.371 P_AIS...................................................................................................................................................................644
4.2.372 P_LOC................................................................................................................................................................. 646
4.2.373 P_LOS................................................................................................................................................................. 647
4.2.374 PASSWORD_NEED_CHANGE.........................................................................................................................649
4.2.375 PATCH_BD_EXCLUDE.....................................................................................................................................650
4.2.376 PATCH_BD_MATCH_FAIL...............................................................................................................................651
4.2.377 PATCH_CHGSCC_NOTMATCH.......................................................................................................................652
4.2.378 PATCH_INIT_FAIL............................................................................................................................................ 653
4.2.379 PATCH_MATCH_NO_START........................................................................................................................... 654
4.2.380 PATCH_OP_TIMEOUT......................................................................................................................................656
4.2.381 PATCH_PKGERR............................................................................................................................................... 657
4.2.382 PCM_64KSNCP_UNAVAIL...............................................................................................................................658
4.2.383 PCM_DATA_CONFLICT................................................................................................................................... 661
4.2.384 PING_ARP_MISMATCH................................................................................................................................... 662
4.2.385 PING_LOS.......................................................................................................................................................... 663
4.2.386 PORT_EXC_TRAFFIC.......................................................................................................................................665
4.2.387 PORT_MODULE_OFFLINE..............................................................................................................................666
4.2.388 PORTMODE_MISMATCH................................................................................................................................ 667
4.2.389 POWER_ABNORMAL...................................................................................................................................... 669
4.2.390 POWER_FAIL.....................................................................................................................................................670
4.2.391 POWER_MODULE_OFFLINE..........................................................................................................................673
4.2.392 PPP_LCP_FAIL...................................................................................................................................................674
4.2.393 PPP_NCP_FAIL.................................................................................................................................................. 675
4.2.394 PRBS_LSS...........................................................................................................................................................676
4.2.395 PRO_PKT_FLOODING..................................................................................................................................... 677
4.2.396 PTP_ATTR_MISMATCH................................................................................................................................... 678
4.2.397 PTP_DELAY_RESP_LOS.................................................................................................................................. 680
4.2.398 PTP_DECRYPTION_FAIL.................................................................................................................................681
4.2.399 PTP_PDELAY_RESP_LOS................................................................................................................................683
4.2.400 PTP_SOURCE_SWITCH................................................................................................................................... 684
4.2.401 PTP_SYNC_LOS................................................................................................................................................ 686
4.2.402 PTP_TIMESTAMP_ABN................................................................................................................................... 687
4.2.403 PTPSRV_LCS_INVALID................................................................................................................................... 689
4.2.404 PUM_BCM_ALM...............................................................................................................................................690
4.2.405 PUM_TEM_ALM............................................................................................................................................... 691
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xv
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.406 PUMP_COOL_EXC........................................................................................................................................... 692
4.2.407 PW_APS_DEGRADED...................................................................................................................................... 693
4.2.408 PW_APS_OUTAGE............................................................................................................................................694
4.2.409 PW_NO_TRAFFIC............................................................................................................................................. 695
4.2.410 PWAPS_LOST.................................................................................................................................................... 697
4.2.411 PWAPS_PATH_MISMATCH..............................................................................................................................699
4.2.412 PWAPS_SWITCH_FAIL.................................................................................................................................... 700
4.2.413 PWAPS_TYPE_MISMATCH............................................................................................................................. 701
4.2.414 PWD_ENCRYPT_RISK..................................................................................................................................... 702
4.2.415 PWR_MAJ_ALM................................................................................................................................................703
4.2.416 PWR_TEMP_OVERTH...................................................................................................................................... 704
4.2.417 R_APS................................................................................................................................................................. 706
4.2.418 R_LOC.................................................................................................................................................................707
4.2.419 R_LOF................................................................................................................................................................. 708
4.2.420 R_LOS................................................................................................................................................................. 710
4.2.421 R_OOF.................................................................................................................................................................712
4.2.422 R_S_ERR.............................................................................................................................................................714
4.2.423 RELAY_ALARM_CRITICAL........................................................................................................................... 715
4.2.424 RELAY_ALARM_IGNORE...............................................................................................................................716
4.2.425 RELAY_ALARM_MAJOR................................................................................................................................ 717
4.2.426 RELAY_ALARM_MINOR.................................................................................................................................718
4.2.427 RELAY_LOF.......................................................................................................................................................719
4.2.428 RFA......................................................................................................................................................................721
4.2.429 RMFA.................................................................................................................................................................. 722
4.2.430 RTS...................................................................................................................................................................... 723
4.2.431 RS_CROSSTR.....................................................................................................................................................723
4.2.432 RTC_FAIL........................................................................................................................................................... 725
4.2.433 S1_SYN_CHANGE............................................................................................................................................ 726
4.2.434 SEC_RADIUS_FAIL.......................................................................................................................................... 727
4.2.435 SECU_ALM........................................................................................................................................................ 729
4.2.436 SERVICE_CAPACITY_EXCEED_LICENSE................................................................................................... 731
4.2.437 SERVICE_TYPE_EXCEED_LICENSE.............................................................................................................731
4.2.438 SLAVE_WORKING............................................................................................................................................732
4.2.439 SOFTWARE_UNCOMMIT................................................................................................................................ 735
4.2.440 SRV_LOOP_LD.................................................................................................................................................. 735
4.2.441 SRV_SHUTDOWN_LD......................................................................................................................................736
4.2.442 SSL_CERT_DAMAGED.................................................................................................................................... 737
4.2.443 SSL_CERT_NOENC...........................................................................................................................................738
4.2.444 SSL_CERT_TO_EXPIRE................................................................................................................................... 739
4.2.445 SSM_LOS............................................................................................................................................................740
4.2.446 SSM_QL_FAILED.............................................................................................................................................. 740
4.2.447 STORM_CUR_QUENUM_OVER.....................................................................................................................741
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xvi
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.448 SUBNET_RT_CONFLICT................................................................................................................................. 742
4.2.449 SUBRATE_PROTOCOL_MM........................................................................................................................... 744
4.2.450 SUM_INPWR_HI............................................................................................................................................... 745
4.2.451 SUM_INPWR_LOW...........................................................................................................................................746
4.2.452 SWDL_ACTIVATED_TIMEOUT...................................................................................................................... 748
4.2.453 SWDL_AUTOMATCH_INH..............................................................................................................................749
4.2.454 SWDL_BD_EXCLUDE......................................................................................................................................749
4.2.455 SWDL_BD_MATCH_FAIL................................................................................................................................751
4.2.456 SWDL_BD_WEAKMATCH.............................................................................................................................. 752
4.2.457 SWDL_CHGMNG_NOMATCH........................................................................................................................ 753
4.2.458 SWDL_COMMIT_FAIL.....................................................................................................................................754
4.2.459 SWDL_INPROCESS.......................................................................................................................................... 754
4.2.460 SWDL_NEPKGCHECK..................................................................................................................................... 755
4.2.461 SWDL_PKG_NOBDSOFT.................................................................................................................................756
4.2.462 SWDL_PKGVER_MM.......................................................................................................................................757
4.2.463 SWDL_ROLLBACK_FAIL................................................................................................................................758
4.2.464 SYN_BAD...........................................................................................................................................................758
4.2.465 SYNC_C_LOS.................................................................................................................................................... 759
4.2.466 SYNC_CONFIG_ERR........................................................................................................................................ 761
4.2.467 SYNC_DISABLE................................................................................................................................................763
4.2.468 SYNC_F_M_SWITCH....................................................................................................................................... 764
4.2.469 SYNC_FAIL........................................................................................................................................................ 765
4.2.470 SYNC_LOCKOFF.............................................................................................................................................. 767
4.2.471 SYSLOG_COMM_FAIL.................................................................................................................................... 769
4.2.472 SYSPARA_CFDB_NOSAME............................................................................................................................ 770
4.2.473 T_ALOS.............................................................................................................................................................. 771
4.2.474 T_FIFO_E............................................................................................................................................................772
4.2.475 T_LOC.................................................................................................................................................................773
4.2.476 T_LOS................................................................................................................................................................. 774
4.2.477 T_LOSEX............................................................................................................................................................ 775
4.2.478 TD........................................................................................................................................................................ 777
4.2.479 TEM_HA............................................................................................................................................................. 778
4.2.480 TEM_LA............................................................................................................................................................. 780
4.2.481 TEMP_ALARM.................................................................................................................................................. 781
4.2.482 TEMP_OVER......................................................................................................................................................783
4.2.483 TF.........................................................................................................................................................................784
4.2.484 THUNDERALM................................................................................................................................................. 785
4.2.485 TIME_LOCK_FAIL............................................................................................................................................ 786
4.2.486 TIME_NO_TRACE_MODE...............................................................................................................................788
4.2.487 TPS_ALM........................................................................................................................................................... 789
4.2.488 TR_LOC.............................................................................................................................................................. 790
4.2.489 TU_AIS............................................................................................................................................................... 793
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xvii
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
4.2.490 TU_AIS_VC12.................................................................................................................................................... 795
4.2.491 TU_AIS_VC3...................................................................................................................................................... 796
4.2.492 TU_LOP.............................................................................................................................................................. 798
4.2.493 TU_LOP_VC12...................................................................................................................................................799
4.2.494 TU_LOP_VC3.....................................................................................................................................................800
4.2.495 TUNNEL_APS_DEGRADED............................................................................................................................ 802
4.2.496 TUNNEL_APS_OUTAGE..................................................................................................................................803
4.2.497 UHCS...................................................................................................................................................................804
4.2.498 UP_E1_AIS......................................................................................................................................................... 805
4.2.499 UP_T1AIS........................................................................................................................................................... 807
4.2.500 V5_VCAIS.......................................................................................................................................................... 809
4.2.501 VC_AIS............................................................................................................................................................... 810
4.2.502 VC_LOC..............................................................................................................................................................813
4.2.503 VC_RDI...............................................................................................................................................................816
4.2.504 VCAT_LOA.........................................................................................................................................................818
4.2.505 VCAT_LOM_VC12............................................................................................................................................ 819
4.2.506 VCAT_LOM_VC3.............................................................................................................................................. 820
4.2.507 VCAT_LOM_VC4.............................................................................................................................................. 821
4.2.508 VCAT_SQM_VC12.............................................................................................................................................822
4.2.509 VCAT_SQM_VC3...............................................................................................................................................823
4.2.510 VCAT_SQM_VC4...............................................................................................................................................824
4.2.511 VCTRUNK_NO_FLOW..................................................................................................................................... 826
4.2.512 VP_AIS................................................................................................................................................................827
4.2.513 VP_LOC.............................................................................................................................................................. 830
4.2.514 VP_RDI............................................................................................................................................................... 833
4.2.515 W_OFFLINE....................................................................................................................................................... 836
4.2.516 W_R_FAIL.......................................................................................................................................................... 837
4.2.517 WAVEDATA_MIS...............................................................................................................................................838
4.2.518 WRG_BD_TYPE................................................................................................................................................ 839
5 Performance Event Reference................................................................................................. 840
5.1 Performance Event List (OSN 500)............................................................................................................................840
5.2 Performance Event List (OSN 550)............................................................................................................................842
5.3 Performance Event List (OSN 580)............................................................................................................................850
5.4 Performance Event Clearing.......................................................................................................................................859
5.4.1 AUPJCHIGH........................................................................................................................................................... 859
5.4.2 AUPJCLOW............................................................................................................................................................ 860
5.4.3 AUPJCNEW............................................................................................................................................................ 861
5.4.4 AVGFREQDEV.......................................................................................................................................................863
5.4.5 AVGMEANPATHDELAY.......................................................................................................................................864
5.4.6 AVGPHASEOFFSET.............................................................................................................................................. 864
5.4.7 AVGPOSITIVEDELAY.......................................................................................................................................... 865
5.4.8 BCV......................................................................................................................................................................... 866
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xviii
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
5.4.9 BDTEMPCUR.........................................................................................................................................................867
5.4.10 BDTEMPMAX......................................................................................................................................................868
5.4.11 BDTEMPMIN....................................................................................................................................................... 868
5.4.12 CCV....................................................................................................................................................................... 869
5.4.13 C3794_LCV_SDH.................................................................................................................................................870
5.4.14 C3794_LES_SDH................................................................................................................................................. 871
5.4.15 C3794_LSES_SDH............................................................................................................................................... 872
5.4.16 CURPOSITIVEPDV............................................................................................................................................. 873
5.4.17 E1_LCV_SDH.......................................................................................................................................................874
5.4.18 E1_LES_SDH........................................................................................................................................................875
5.4.19 E1_LLOSS_SDH...................................................................................................................................................876
5.4.20 E1_LSES_SDH..................................................................................................................................................... 878
5.4.21 EDTMP..................................................................................................................................................................879
5.4.22 HPBBE.................................................................................................................................................................. 880
5.4.23 HPCSES.................................................................................................................................................................881
5.4.24 HPES..................................................................................................................................................................... 882
5.4.25 HPFEBBE..............................................................................................................................................................885
5.4.26 HPFECSES............................................................................................................................................................ 886
5.4.27 HPFEES.................................................................................................................................................................887
5.4.28 HPFESES...............................................................................................................................................................889
5.4.29 HPFEUAS............................................................................................................................................................. 890
5.4.30 HPSES................................................................................................................................................................... 891
5.4.31 HPUAS.................................................................................................................................................................. 893
5.4.32 HPS_PATH_CRC_ERR.........................................................................................................................................894
5.4.33 LPBBE...................................................................................................................................................................897
5.4.34 LPCSES................................................................................................................................................................. 898
5.4.35 LPES...................................................................................................................................................................... 900
5.4.36 LPFEBBE.............................................................................................................................................................. 903
5.4.37 LPFECSES............................................................................................................................................................ 904
5.4.38 LPFEES................................................................................................................................................................. 905
5.4.39 LPFESES............................................................................................................................................................... 907
5.4.40 LPFEUAS.............................................................................................................................................................. 908
5.4.41 LPSES....................................................................................................................................................................909
5.4.42 LPUAS...................................................................................................................................................................911
5.4.43 MAXFREQDEV................................................................................................................................................... 913
5.4.44 MAXMEANPATHDELAY................................................................................................................................... 914
5.4.45 MAXPHASEOFFSET...........................................................................................................................................914
5.4.46 MAXPOSITIVEDELAY....................................................................................................................................... 915
5.4.47 MINFREQDEV..................................................................................................................................................... 916
5.4.48 MINMEANPATHDELAY.....................................................................................................................................917
5.4.49 MINPHASEOFFSET............................................................................................................................................ 918
5.4.50 MINPOSITIVEDELAY.........................................................................................................................................919
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xix
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
5.4.51 MSBBE..................................................................................................................................................................920
5.4.52 MSCSES................................................................................................................................................................ 921
5.4.53 MSES.....................................................................................................................................................................922
5.4.54 MSFEBBE............................................................................................................................................................. 924
5.4.55 MSFECSES........................................................................................................................................................... 925
5.4.56 MSFEES................................................................................................................................................................ 926
5.4.57 MSFESES.............................................................................................................................................................. 928
5.4.58 MSFEUAS.............................................................................................................................................................929
5.4.59 MSSES...................................................................................................................................................................930
5.4.60 MSUAS................................................................................................................................................................. 932
5.4.61 OSPITMPCUR...................................................................................................................................................... 933
5.4.62 OSPITMPMAX..................................................................................................................................................... 934
5.4.63 OSPITMPMIN.......................................................................................................................................................935
5.4.64 RPLCUR................................................................................................................................................................935
5.4.65 RPLMAX...............................................................................................................................................................936
5.4.66 RPLMIN................................................................................................................................................................ 937
5.4.67 RSBBE...................................................................................................................................................................938
5.4.68 RSCSES.................................................................................................................................................................939
5.4.69 RSES......................................................................................................................................................................941
5.4.70 RSOFS................................................................................................................................................................... 942
5.4.71 RSOOF.................................................................................................................................................................. 943
5.4.72 RSSES................................................................................................................................................................... 945
5.4.73 RSUAS.................................................................................................................................................................. 946
5.4.74 SUMIOP................................................................................................................................................................ 947
5.4.75 SUMOOP...............................................................................................................................................................949
5.4.76 T1_LCV_SDH.......................................................................................................................................................951
5.4.77 T1_LES_SDH........................................................................................................................................................952
5.4.78 T1_LSES_SDH..................................................................................................................................................... 953
5.4.79 TLBCUR............................................................................................................................................................... 954
5.4.80 TLBMAX.............................................................................................................................................................. 955
5.4.81 TLBMIN................................................................................................................................................................ 956
5.4.82 TPLCUR................................................................................................................................................................ 956
5.4.83 TPLMAX...............................................................................................................................................................957
5.4.84 TPLMIN................................................................................................................................................................ 958
5.4.85 TUPJCHIGH......................................................................................................................................................... 959
5.4.86 TUPJCLOW.......................................................................................................................................................... 960
5.4.87 TUPJCNEW.......................................................................................................................................................... 961
5.4.88 VC3BBE................................................................................................................................................................ 963
5.4.89 VC3CSES.............................................................................................................................................................. 964
5.4.90 VC3ES................................................................................................................................................................... 965
5.4.91 VC3FEBBE........................................................................................................................................................... 968
5.4.92 VC3FECSES......................................................................................................................................................... 969
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xx
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
5.4.93 VC3FEES.............................................................................................................................................................. 970
5.4.94 VC3FESES............................................................................................................................................................ 972
5.4.95 VC3FEUAS........................................................................................................................................................... 973
5.4.96 VC3SES.................................................................................................................................................................974
5.4.97 VC3UAS................................................................................................................................................................976
5.4.98 WCV...................................................................................................................................................................... 977
5.4.99 XCSTMP............................................................................................................................................................... 978
5.5 RMON Event of the Ethernet Service List................................................................................................................. 979
5.5.1 CQ1..........................................................................................................................................................................980
5.5.2 CSHD.......................................................................................................................................................................980
5.5.3 EF8F........................................................................................................................................................................ 984
5.5.4 EFS8........................................................................................................................................................................ 985
5.5.5 EG4C....................................................................................................................................................................... 986
5.5.6 EG8.......................................................................................................................................................................... 987
5.5.7 EGS4........................................................................................................................................................................988
5.5.8 EGT1....................................................................................................................................................................... 989
5.5.9 EM10....................................................................................................................................................................... 990
5.5.10 EM20..................................................................................................................................................................... 992
5.5.11 EM6F..................................................................................................................................................................... 995
5.5.12 EM6T.....................................................................................................................................................................996
5.5.13 EX1........................................................................................................................................................................ 997
5.5.14 HUND2..................................................................................................................................................................999
5.5.15 HUNS3................................................................................................................................................................ 1001
5.5.16 MD1.....................................................................................................................................................................1003
5.5.17 PCX..................................................................................................................................................................... 1004
5.6 RMON Event of the Ethernet Service Description...................................................................................................1007
5.6.1 CES Performance Event List................................................................................................................................. 1008
5.6.2 PPP Performance Event List..................................................................................................................................1009
5.6.3 ML-PPP Performance Event List.......................................................................................................................... 1010
5.6.4 L2VPN Performance Event List............................................................................................................................ 1011
5.6.5 Tunnel Performance Event List............................................................................................................................. 1013
5.6.6 PW Performance Event List.................................................................................................................................. 1015
5.6.7 MPLS-TP OAM Performance Event List............................................................................................................. 1016
5.6.8 ETH OAM Performance Event List...................................................................................................................... 1018
5.6.9 QoS Performance Event List................................................................................................................................. 1018
5.6.10 ATM PWE3 Service Performance Event List..................................................................................................... 1023
5.6.11 ATM Service Performance Event List................................................................................................................. 1023
5.6.12 Statistics of RMON Basic Performance (packet)................................................................................................ 1027
5.6.13 Statistics of RMON Extended Performance (packet)..........................................................................................1029
5.6.14 Statistics of RMON basic performance (TDM).................................................................................................. 1034
5.6.15 Statistics of RMON extended performance (TDM)............................................................................................ 1036
5.6.16 Statistics of RMON VCG performance (TDM).................................................................................................. 1040
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xxi
OptiX OSN 500/550/580
Alarms and Performance Events Reference Contents
A Glossary....................................................................................................................................1042
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. xxii
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
1 Generation of Alarms and Performance
Events of SDH Services
About This Chapter
This topic describes the generation and detection of SDH higher order and lower order signal
flows, and suppression correlation between SDH alarms.
1.1 Overview
There are sufficient overhead bytes in SDH frames, including 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 monitor alarms
and bit errors in real time. With an understanding of the alarm generation and detection
principles, you can quickly identify 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, and then tributary; higher order first, and then
lower order". Therefore, more attention should be paid during maintenance to alarms and
performance events that are generated between the SDH port and the cross-connect unit. This
section describes the higher order signal flow and higher order overhead byte processing.
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. Therefore, the alarm signal
generation modes vary accordingly. This section describes the signal flow and the procedure
to handle 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 relationships among SDH alarms.
1.5 Generation and Detection of SDH Performance Events
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Performance events of an SDH network include bit errors and jitter. Jitter can result in pointer
justification on the equipment. This section describes generation and detection mechanism of
bit errors and pointer justification.
1.1 Overview
There are sufficient overhead bytes in SDH frames, including 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 monitor alarms
and bit errors in real time. With an understanding of the alarm generation and detection
principles, you can quickly identify faults.
Figure 1-1 shows the SDH alarm signal flow.
Figure 1-1 SDH alarm signal flow
SPI RST MST MSA HPT HPA LPT
LOS
"1"
(A1,A2) LOF
J0_MM AIS
(J0)
RS_BIP Err.
(B1)
MS_AIS "1"
(K2) AIS
MS_BIP Err.
(B2)
MS_REI
(M1)
MS_RDI
(K2)
AU_AIS "1"
(H1,H2,H3)
AU_LOP
(H1,H2)
HP_SLM, HP_UNEQ "1"
(C2)
HP_TIM
(J1) AIS
HP_BIP Err.
(B3)
HP_REI
(G1)
HP_RDI
(G1)
TU_AIS "1"
(V1,V2,V3)
TU_LOP
(V1,V2)
HP_LOM
(H4)
LP_UNEQ "1"
(V5)
LP_TIM
(J2)
LP_BIP Err. AIS
(V5)
LP_REI
(V5)
LP_RDI
(V5)
"1"
LP_SLM AIS
(V5)
Indicates that the corresponding alarm or signal is generated
Indicates that the corresponding alarm is detected
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 2
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
1.1.1 Directions and Levels of Signal Flows
This section describes basic concepts, including the uplink signal flow, downlink signal flow,
higher order path, and lower order path, involved in signal analysis.
Term Description Figure
Downlink The signal direction is as
signal follows: SDH port → cross- SDH SDH
flow connect unit → PDH port. port
Cross-connect
port
unit
PDH port
Downlink signal flow
Uplink The signal direction is as
signal follows: PDH port → cross- SDH
port Cross-connect
SDH
port
Uplink
flow connect unit → SDH port. unit signal flow
PDH port
Higher The signal flow between the Higer order part
order SDH port and the cross-connect
signal unit is the higher order signal SDH
port
Cross-connect
SDH
port
flow flow. unit
PDH port
Lower The signal flow between the
order cross-connect unit and the PDH SDH
port
SDH
port
Cross-connect
signal port is the lower order signal unit
flow flow. PDH port
Lower order part
1.1.2 Two Common Alarms
This section describes two common alarms: alarm indication signal (AIS) and remote defect
indication (RDI).
Alarm Description
AIS When an AIS alarm is reported, the system inserts all 1s into
the lower-level circuits to indicate that the signal is
unavailable. The MS_AIS, AU_AIS, TU_AIS, E1_AIS, and
T1_AIS alarms are common AIS alarms.
RDI When detecting the loss of signal (LOS), AIS, or trace
identifier mismatch (TIM) alarm, the opposite NE sends the
RDI alarm to the local NE.
The MS_RDI, HP_RDI, and LP_RDI alarms are common
RDI alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 3
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
NOTE
The generation of an alarm on an NE does not necessarily indicate that the NE is faulty. The alarm may
be generated due to a fault on the opposite NE or due to other causes.
For example, the R_LOS alarm is generated due to a fiber cut, or the HP_LOM alarm is generated on the
local NE due to the failure in the cross-connect unit on the opposite NE.
1.1.3 Alarm Management
When a network is operating abnormally, the NMS notifies the situation to the maintenance
personnel, who can take immediate measures to recover the network.
Alarm management consists of the following functions:
l Network-wide alarm monitoring and remote alarm notification enable the U2000 to
notify maintenance engineers of network exceptions in a timely manner so that the
engineers can rectify faults quickly.
l Alarm/Event relevance analysis, alarm masking, alarm filtering, alarm suppression,
automatic alarm reporting, alarm reversion, and maintenance experience databases
improve the effectiveness and efficiency of alarm handling.
l Alarm synchronization ensures the reliability of alarms.
Alarms can be reported in the following cases:
l A board detects and reports the alarms to the NE software.
l The NE software reports the alarms to the NMS server.
l The users query the alarms on the NMS server through the NMS client.
In the alarm reporting process, an alarm goes through the following procedures before it is
stored by the NMS:
l Alarm/Event relevance analysis
l Automatic alarm reporting
l Alarm suppression
l Alarm masking
l Alarm filtering
l Alarm reversion
l Alarm/Event redefine
Alarm/Event Relevance Analysis
In the alarm/event relevance analysis procedure, the NMS analyzes the alarms reported within
a period, identifies the root alarms and correlative alarms based on certain rules, and displays
the analysis results. Root alarms cause correlative alarms. If root alarms are cleared,
correlative alarms clear automatically.
The alarm/event relevance function identifies root alarms and correlatives alarms, allowing
the maintenance personnel to focus on root alarms in troubleshooting and therefore improving
the troubleshooting efficiency.
The alarm/event relevance function provides alarm relevance on NEs, alarm relevance on the
NMS, and user-defined alarm relevance.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 4
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Automatic Alarm Reporting
If automatic alarm reporting is enabled on an NE, the NE-side alarms can be reported to the
NMS immediately after they occur. Users can view the alarm information that is
automatically displayed on the NMS. This function can be disabled for minor alarms to
reduce the impacts of alarm information on the NMS performance.
Alarm Suppression
The NMS provides the alarm suppression function. If this function is enabled for an alarm,
the NE does not report the alarm.
Alarm Masking
This function masks minor alarms to avoid unnecessary alarm information.
During the maintenance, testing or deployment of an NE, numerous alarms may be reported
and there is no need to care about them. In this case, the alarm masking function can be used
to mask the alarms so that the NMS does not display or store the alarm information.
Figure 1-2 provides the differences between alarm suppression and alarm masking.
l If alarm suppression is enabled for an alarm, the NE does not report the alarm.
l If alarm masking is enabled for an alarm, the NE still reports the alarm but the NMS
discards the alarm information.
Figure 1-2 Differences between alarm suppression and alarm masking
Alarm masking Alarm suppression
NMS NMS
The NMS does The NMS cannot
not receive the receive the
masked alarms. suppressed
alarms.
X The NEs do not report
the suppressed
The NEs report
alarms. alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 5
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Alarm Filtering
To avoid redundant alarm information, alarm filtering can be enabled for a specific NE on the
NMS. The NMS filters the alarm information based on alarm name, object, severity, status,
type, latest report time, clear time and other conditions. This function improves alarm
browsing efficiency without affecting NE-side alarm reporting. The filtering conditions which
users are concerned about can be added to alarm filtering templates. Selecting an alarm
filtering template allows multiple required conditions to be applied at a time.
If alarm filtering is enabled for an alarm, the NMS discards the relevant alarm information; if
alarm filtering is disabled for an alarm, the NMS receives and records the relevant alarm
information.
Alarm Reversion
In the case of a port for which services are not activated, the alarm reversion function can be
used to prevent relevant alarm information from being generated and thus to prevent
interferences from the generated alarms. When the alarm reversion function is enabled, you
can set the alarm status of this port to be opposite to the actual status. That is, an alarm is
reported when no alarm occurs and no alarm is reported when alarms occur.
There are three modes of alarm reversion: non-revertive, auto-revertive, and manual-revertive
mode.
l Non-revertive: This is the normal alarm monitoring state, and is the default alarm mode.
In this mode, the alarm reversion function cannot be enabled for a port.
l Auto-revertive: In this mode, the alarm reversion function can be enabled only on a port
that reports alarms. After the alarm reversion function is enabled, the port enters the
alarm revertive mode, and does not report alarms. When the current alarms are cleared,
the port automatically exits the revertive mode, and the alarm state reported by the port is
restored to be the actual alarm state.
l Manual-revertive: In this mode, the alarm reversion function can be enabled on a port,
regardless of whether any alarms exist on this port.
– When the alarm reversion function is enabled on a port, the alarm state reported by
the port is inconsistent with the actual alarm state.
– When the manual-revertive mode is disabled, the alarm reversion mode is restored
to be the non-revertive mode. The alarm state reported by the port is consistent with
the actual alarm state.
The precautions for setting the alarm reversion function are as follows:
l The alarm state of the board, including the state of the alarm indicators on the board,
remains unchanged, which indicates the running state of the equipment.
l The alarm reversion function is realized by the NE software. The alarm data on the NE
and on the NMS is the same, which indicates the alarm state after the alarms are
reversed.
Alarm/Event Redefine
The U2000 can redefine attributes of all alarms or events, such as level, name, and type, to
locate and maintain alarms more effectively. For example, you can decrease the severities of
the alarms/events that do not require attention and increase the severities of the alarms/events
that require attention.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 6
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
The redefinition of alarm/event names takes effect for all NEs. It cannot take effect for only
the specified NEs. The redefinition of types and severities can take effect for either the
specified NEs or all NEs.
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, and then tributary; higher order first, and then
lower order". Therefore, more attention should be paid during maintenance to alarms and
performance events that are generated between the SDH port and the cross-connect unit. This
section describes the higher order signal flow and higher order overhead byte processing.
In normal cases, higher order alarms and performance events may cause the reporting of
lower order alarms and performance events. Figure 1-3 shows the signal flow between the
SDH port and the cross-connect unit.
Figure 1-3 Signal flow between the SDH port and the cross-connect unit
Frame synchronizer and MS overhead Pointer processor and
RS overhead processor processor HP overhead processor
(RST) (MST) (MSA, HPT)
LOS "1" AIS "1" AIS
A1, AU-AIS
LOF MS-AIS H1,H2
STM-N A2
K2 H1,H2
AU-LOP
optical B2-Err.
HP-TIM Cross-
B2
J1
HP-UNEQ "1" connect
port BI Err. MS-REI C2
HP-SLM
B1 M1 C2
unit
HP-LOM
MS-RDI H4
K2 B3 Err.
B3
HP-REI
G1
G1 HP-RDI
Downlink signal flow Alarm report or return
Signal transfer point (Insert all 1s) Alarm termination point
(Report to the SCC unit)
Based on the positions of overhead bytes in an STM-N frame, overhead bytes are classified
into four types:
l Regenerator section overhead
l Multiplex section overhead
l Higher order path overhead
l Lower order path overhead
If errors occur in the first two types of overhead types, all the higher order paths are affected.
If errors occur in the overhead bytes of a higher order path, only this higher order path and its
lower order paths are affected.
1.2.1 Downlink Signal Flow
Overhead bytes are extracted and terminated in the higher order downlink signal flow.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 7
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Frame Synchronizer and Regenerator Section Overhead Processor
The regenerator section overhead bytes related to alarms and performance events are as
follows:
l Frame aligning bytes (A1 and A2)
l Regenerator section trace byte (J0)
l Bit error check byte (B1)
The alarm signal flow is as follows:
l Receiving optical signals
When an STM-N optical signal from an optical path enters the optical receive module in
a line unit, the signal is converted into an electrical signal by the optical/electrical (O/E)
conversion module.
The signal is then transmitted to a frame synchronizer and a descrambler for processing.
During this process, the O/E conversion module checks the signal.
An R_LOS alarm is reported if one of the following faults is detected:
– No optical signal is input.
– The optical power is out of range.
– The code type of the input signal is not the expected code type.
When an R_LOS alarm is reported, the system inserts all 1s into the lower-level circuits.
The SDH equipment returns to the normal state only when the optical receive module at
the local NE detects two consecutive correct code patterns and no new R_LOS alarm is
detected.
l Monitoring 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 based on the A1 and the A2 bytes in
the STM-N signal.
Meanwhile, the frame synchronizer extracts the synchronization clock source of the line
unit from the STM-N signal and sends it to the timing unit for clock locking.
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 is
generated. If the R_OOF alarm lasts for more than 3 ms, an R_LOF alarm is generated
and all 1s are inserted. If the frame aligning state lasts for more than 1 ms after the
R_LOF alarm is generated, the equipment is restored to the normal state.
The J0 byte is used to verify if both ends of a regenerator section are always connected
to each other. The J0 byte transmitted by the transmit end must be the same as the J0
byte that the receive end is supposed to receive. Otherwise, the equipment reports a
J0_MM alarm, indicating inconsistent trace identifiers.
A descrambler descrambles all the bytes except the A1, A2, and J0 bytes and the two
bytes that follow the J0 byte in an STM-N signal.
l Monitoring the B1 byte
The regenerator section overhead processor extracts and processes regenerator section
overhead bytes in an STM-N signal. Of all the bytes, the B1 byte is the most important
one.
If the B1 byte extracted from an STM-N signal is not consistent with the BIP-8
computing result of the preceding STM-N frame, B1 bit errors occur.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 8
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
– If the number of B1 bit errors exceeds the threshold 10-3 (default value), a B1_EXC
alarm is generated.
– If the number of B1 bit errors exceeds the threshold 10-6 (default value), a B1_SD
alarm is generated.
When 10 consecutive RSSESs (a second in which block errors account for 30% is called
an RSSES) are detected using the B1 type, an RSUAT performance event occurs. RSSES
is short for regenerator section severely errored second.
The F1, D1-D3, and E1 bytes that are not related to alarms and performance events are
transmitted to the SCC unit and the overhead unit.
Multiplex Section Overhead Processor
The multiplex section overhead bytes that are related to alarms and the performance events
are as follows:
l Automatic protection switching bytes (K1 and K2)
l Multiplex section bit error monitoring byte (B2)
l Multiplex section remote block error indication byte (M1)
The signal flow is as follows:
l Monitoring the K1 and the K2 bytes
Bits 6 to 8 in the K2 byte indicate a multiplex section remote failure.
– If bits 6 to 8 in the K2 byte are 111, an MS_AIS alarm is generated and all 1s are
inserted.
– If bits 6 to 8 in the K2 byte are 110, an MS_RDI alarm is generated.
The K1 type and bits 1 to 5 in the K2 byte are used to transmit the automatic protection
switching (APS) protocol, and work with the SCC unit and the cross-connect unit to
implement multiplex section protection (MSP).
l Monitoring the B2 and M1 bytes
If the B2 byte extracted from an STM-N signal is not consistent with the BIP-24
computing result of the preceding STM-N frame (all bits expect the regenerator section
overhead), B2 bit errors occur.
The M1 byte is used to check if an MS_REI alarm is reported. The M1 byte carries the
number of incorrectly interleaved bit blocks that is detected using the B2 byte.
– If the number of B2 bit errors exceeds the threshold 10-6 (default value), a B2_SD
alarm is generated.
– If the number of B2 bit errors exceeds the threshold 10-3 (default value), a B2_EXC
alarm is generated.
In the default status of the NE software, MSP switching is enabled and the B2_SD and
B2_EXC alarms can trigger MSP switching.
When 10 consecutive MSSESs are detected using the B2 byte, an MSUAT performance
event occurs.
Pointer Processor and Higher Order Path Overhead Processor
The bytes that are related to pointer justification are H1, H2, and H3.
The bytes that are related to alarms and bit errors are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 9
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
l Higher order path trace byte (J1)
l Signal label byte (C2)
l Higher order path bit error monitoring byte (B3)
l Path status byte (G1)
l Multiframe position indication byte (H4)
The alarm signal flow is as follows:
l Monitoring the H1 and H2 bytes
The pointer processor interprets and justifies the pointer based on the H1 and H2 bytes in
each AU-4. It implements frequency and phase alignment, and tolerates phase jitter and
wander on the network. The pointer processor also locates each VC-4 and transmits it to
the corresponding higher order path overhead processor. If the H1 and H2 bytes of the
AU pointer are all 1s, an AU_AIS alarm is generated and all 1s are inserted. If the
pointer values indicated by the H1 and H2 bytes are out of the specified range (0-782)
and invalid pointers are received in eight consecutive frames, an AU_LOP alarm is
reported and all 1s are inserted.
If a positive AU pointer justification occurs, the number of PJCHIGHs of the multiplex
section adaptation (MSA) increases by 1. If a negative AU pointer justification occurs,
the number of PJCLOWs of the MSA increases by 1.
l Monitoring 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 all 1s are inserted.
If the C2 byte value is 00, an HP_UNEQ alarm is reported and all 1s are inserted. If the
C2 byte value detected is not the same as the preset value, an HP_SLM alarm is reported
and all 1s are inserted.
NOTE
For the Huawei OptiX Metro and OSN equipment, you can configure, on the NMS, all 1s to be
inserted when an HP_TIM, HP_UNEQ, or HP_SLM alarm is generated. By default, all 1s are not
inserted.
Currently, the tributary unit group (TUG) is used as the payload structure in China. The
preset C2 value corresponding to the TUG structure is 02.
If the B3 byte extracted from the HPOH is not consistent with the BIP-8 computing
result of the VC-4 signal of the preceding frame, B3 bit errors occur.
If bit 5 in the G1 byte is 1, an HP_RDI alarm is reported. The value of bits 1 to 4 in the
G1 byte determines whether an HP_REI alarm is reported. If the value of bits 1 to 4
ranges from 1 to 8, an HP_REI alarm is reported.
When 10 consecutive HPSESs are detected using the B3 type, an HPUAT performance
event occurs.
Other overhead bytes such as 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 between the higher order path and the lower order path.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 10
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
1.2.2 Uplink Signal Flow
The initial values of overhead bytes are generated and alarm signals are returned to the
opposite NE in the higher order uplink signal flow.
Pointer Processor and Higher Order Path Overhead Processor
NxSTM-1 payload signals from the cross-connect unit are first transmitted to the higher order
path overhead processor.
The higher order path overhead processor generates N higher order path overhead bytes, and
transmits them with the NxSTM-1 payloads to the pointer processor.
The higher order path overhead processor configures higher order path overhead bytes, such
as J1, C2, B3, G1, F2, F3, and N1, along the uplink direction.
If an AU_AIS, AU_LOP, or HP_UNEQ alarm is detected in the downlink signal flow, bit 5 in
the G1 byte is set to 1 and the G1 type is sent to the transmit end. The transmit end reports an
HP_RDI alarm.
If B3 bit errors are detected in the downlink signal flow, the value of bits 1 to 4 in the G1 byte
is set to the number of detected block errors (ranging from 1 to 8), and an HP_REI alarm is
reported to the transmit end.
The H4 byte is not processed in the uplink direction.
The pointer processor generates NxAU-4 pointers (indicated by the H1 and H2 bytes), and
adapts VC-4s into AU-4s. The NxAU-4s are then multiplexed into an STM-N signal by the
multiplexing processor and transmitted to the multiplex section overhead processor.
Multiplex Section Overhead Processor
The multiplex section overhead processor sets multiplex section overhead bytes, such as 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 downlink signal flow, bits 6
to 8 in the K2 byte are set to 110 and an MS_RDI alarm is sent to the transmit end using the
K2 byte.
If B2 bit errors are detected in the downlink signal flow, an MS_REI alarm is sent to the
transmit end using the M1 byte.
Frame Synchronizer and Regenerator Section Overhead Processor
The regenerator section overhead processor sets regenerator section overhead bytes, such as
A1, A2, J0, E1, F1, D1-D3, and B1, and sends a complete STM-N electrical signal to the
frame synchronizer and scrambler.
After the STM-N electrical signal is scrambled by the frame synchronizer and scrambler, the
E/O conversion module converts the STM-N electrical signal into an STM-N optical signal
and transmits it through an optical port.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 11
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
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. Therefore, the alarm signal
generation modes vary accordingly. This section describes the signal flow and the procedure
to handle each overhead byte by each module.
NOTE
This section uses E1, E3, and E4 signal sequences as examples.
This section describes the E1 signal flow processing and alarm generation processes between
PDH ports and the cross-connect unit.
Figure 1-4 shows the alarm signal flow.
Figure 1-4 Generation of alarms between E1 ports and the cross-connect unit
HPA , LPT LPA PPI
E1AIS "1'' T-ALOS
Cross- V5
LP-SLM
connect V5
LP-UNEQ
unit LP-TIM
J2
TU-LOP LP-TFIFO E1
V1, V2
V1, V2 TU-AIS port
H4 HP-LOM
LP-RDI
V5
E1AIS
"1''
BIP-2
V5
LP-REI
V5
LP-RFIFO
Signal flow Alarm report or return
Signal transfer point Alarm termination point
(Insert all 1s) (Report to the SCC unit)
As shown in Figure 1-4, the lower order part is divided into the following functional modules
by overhead byte processing characteristics:
l Higher order path adaptation (HPA)
l Lower order path termination (LPT)
l Lower order path adaptation (LPA)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 12
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
l PDH physical interface (PPI)
1.3.1 Downlink Signal Flow
By processing lower order overhead bytes, the system detects alarms and performance events
in the lower order downlink signal flow.
HPA and LPT
The HPA and LPT modules are key lower order functional modules, which process most
lower order overhead bytes.
The lower order overhead bytes include the following:
l Lower order path pointer indication bytes (V1, V2, and V3)
l Path state and signal label byte (V5)
l Lower order path identifier (J2)
The VC-4 signal from the cross-connect unit is transmitted to the HPA.
The HPA demaps the VC-4s into VC-12s. The pointers of all VC-12s are decoded to provide
the per-byte frame offset information between the VC-4s and the VC-12s.
When the NE clock at the TU-12 assembler differs from the local reference clock, continuous
pointer justification is performed. The positive TU pointer justification (TUPJCHIGH) and
the negative TU pointer justification (TUPJCLOW) are detected in the downlink signal flow.
If an incorrect 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 is reported,
all "1"s signal is inserted into the next functional module.
In addition, if a TU_AIS alarm is generated, an AIS signal is inserted in the downlink data. At
the same time, an LP_RDI alarm is reported; that is, bit 8 of the V5 byte is set to "1".
The VC-12 signal is transmitted to the LPT module for V5 byte processing.
Figure 1-5 shows the structure of the V5 byte.
Figure 1-5 Structure of the V5 byte
V5
byte b1 b2 b3 b4 b5 b6 b7 b8
BIP-2 error check 1:LP_REI Unused Signal label
Inconsistent:LPBBE 000:LP_UNEQ 1:LP_RDI
If bits 5-7 of the V5 byte in the downlink signal flow are detected to be "000", the lower order
paths are not equipped (LP_UNEQ). 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 13
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Error monitoring bits 1 and 2 of the V5 byte are detected and the BIP-2 for the VC-12 signal
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 process, an LVCUATEVENT is
reported.
At the same time, the lower order path identifier (J2) is recovered and the value of the
received J2 byte is checked. If the received J2 byte is different from the expected value, an
LP_TIM alarm is reported.
LPA and PPI
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.
1.3.2 Uplink Signal Flow
Lower order overhead bytes such as V5 and H4 are generated in the lower order uplink signal
flow.
LPA and PPI
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 into the upper level circuit.
The LPA completes data adaptation.
If a T_ALOS alarm is detected, an E1_AIS alarm is reported. The E1_AIS alarm can be
suppressed by a T_ALOS alarm when the corresponding alarm correlation is configured.
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 POHs to be inserted into a C-12 to form a 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 downlink signal flow, bit 3 of the V5 byte is set to
"1" in the next frame and an LP_REI alarm is generated.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 14
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
The HPA adapts a VC-12 into a TU-12, maps it into a higher order VC-4, and then sends it to
the cross-connect unit.
The per-byte frame offset 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 Ports 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-1 lists the differences between 2 Mbit/s and 34/140 Mbit/s alarm signals.
Table 1-1 Same type of alarms with different names
Board Condition Alarm
2 Mbit/s electrical PDH External signal loss occurs. T_ALOS
Board
34 Mbit/s electrical P_LOS
PDH Board
140 Mbit/s electrical EXT_LOS
PDH Board
2 Mbit/s electrical PDH Signals in the downlink signal flow UP_E1AIS and
Board are all "1"s. DOWN_E1AIS
34 Mbit/s electrical P_AIS
PDH Board
140 Mbit/s electrical C4_R_LAISD
PDH Board
140 Mbit/s electrical Signals in the uplink signal flow are C4_T_LAISD
PDH Board all "1"s.
NOTE
An EXT_LOS alarm can cause a C4_T_LAISD alarm.
Different Path Overhead Bytes for Alarm and Performance Event Monitoring
The path overhead bytes that are used in the 34 Mbit/s and 140 Mbit/s PDH Boards are B3,
J1, C2 and G1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 15
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
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-6 shows the structure of the G1 byte.
Figure 1-6 Structure of the G1 byte
G1 byte b1 b2 b3 b4 b5 b6 b7 b8
HP_REI 1: HP_RDI Reserved
The definition of bits 1-4 of the G1 byte is as follows:
l 0000-1000: indicates that there are 0 to 8 errors respectively.
l 1001-1111: indicates that there are no errors.
1.4 Suppression Correlation Between SDH Alarms
The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This function involves the intra-board alarm suppression and the inter-board alarm
suppression. In terms of these two types of alarm suppressions, this section describes the
suppression relationships 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.
Figure 1-7 shows the suppression relationships among key alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 16
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Figure 1-7 Suppression relationships among key alarms
R_LOS
R_LOF TU_AIS TU_LOP
J0_MM MS_AIS B1_EXC B2_EXC
BIP_EXC
AU_AIS AU_LOP B1_SD B2_SD
B3_EXC HP_TIM HP_SLM HP_LOM HP_UNEQ
B3_SD TU_AIS TU_LOP BIP_EXC
LP_UNEQ LP_TIM LP_SLM BIP_SD
For example: A B means A suppresses B
The higher level alarms above the arrow can suppress the lower level alarms below the arrow.
Therefore, 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-8 shows the inter-board suppression relationships among common alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 17
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Figure 1-8 Inter-board alarm suppression relationships
R_LOS
R_LOC
R_LOF
MS_AIS
AU_LOP
HP_LOM
AU_AIS
TU_AIS TU_AIS_VC3 TU_AIS_VC12
A B 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
Performance events of an SDH network include bit errors and jitter. Jitter can result in pointer
justification on the equipment. This section describes generation and detection mechanism of
bit errors and pointer justification.
1.5.1 Bit Errors
Bit errors are detected through the parity check of B1, B2, B3 and V5 bytes.
Generation Mechanism
The SDH system adopts bit interleaved parity (BIP) to detect bit errors. The BIP is performed
on the BIP matrix of the regenerator section (RS), multiplex section (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 RS. 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:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 18
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
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 stored 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 to error monitor in the MS, and the working mechanism is similar to that
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 byte is as follows:
1. At the transmit end, the BIP-24 is computed for all bits of the previous STM-1 frame
except the regenerator section overhead (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 for monitoring the bit errors of the VC-4 or the 140 Mbit/s signal within
the STM-N frame during 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 labeling, and VC-12 path
status indicating. 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-9 shows the error detection relationship and location.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 19
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Figure 1-9 Error detection relationship and location
LPT HPT MST RST RST MST HPT LPT
B1
B2
B3
V5
The modules in Figure 1-9 are defined as follows:
l RST is regenerator section termination.
l MST is multiplex section termination.
l HPT is higher order path termination.
l LPT is lower order path termination.
The B1, B2, B3 and V5 bit errors are monitored between these terminations. Figure 1-9
shows that bit errors that occur in the lower order path cannot be detected in the higher order
path, MS, or RS. If bit errors occur in the RS, 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. If the V5 bit error occurs, B3, B2 and B1 bit errors
are not necessarily generated.
When the SDH system detects errors, it reports the error performance events or alarms, and
notifies the remote end of error detection through overhead bytes.
Terms
Table 1-2 lists the relevant terms.
Table 1-2 Bit error terms
Term Description
BE Block error. It indicates that one or more bits have errors.
BBE Background block error. It indicates an errored block occurring outside the
period of UAT and SES.
FEBBE Far end background block error. It indicates that a BBE event is detected at the
far end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 20
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference 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
Upon detecting errors, 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 and remote ends, you
can determine the faulty section of the path or the signal directions where errors occur. Table
1-3 lists the alarms and performance events related to bit errors.
Table 1-3 Alarms and performance events related to bit errors
Item Performance Event Alarm
If bit errors If bit errors If bit errors cross If bit errors exceed
cross the cross the the threshold at the threshold at
threshold at threshold at the local end, the the local end, the
the local the local end, local end reports opposite end
end, the the opposite the relevant reports the
local end end reports alarm. relevant alarm.
reports the the relevant
relevant event.
event.
Regener RSBBE - B1_SD/B1_EXC -
ator
section
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 21
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Item Performance Event Alarm
If bit errors If bit errors If bit errors cross If bit errors exceed
cross the cross the the threshold at the threshold at
threshold at threshold at the local end, the the local end, the
the local the local end, local end reports opposite end
end, the the opposite the relevant reports the
local end end reports alarm. relevant alarm.
reports the the relevant
relevant event.
event.
Multiple MSBBE MSFEBBE B2_SD/B2_EXC MS_REI
x section
Higher HPBBE HPFEBBE B3_SD/B3_EXC HP_REI
order
path
Lower LPBBE LPFEBBE BIP_SD/BIP_EXC LP_REI
order
path
If the B1 byte recovered from the STM-N signal is inconsistent with the BIP-8 computing
result of the previous STM-N frame, the B1 bit error occurs.
If the B2 byte recovered from the STM-N signal is inconsistent with the BIP-24 computing
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 inconsistent 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 inconsistent from the
BIP-2 computing result of the VC-12 signal in the previous frame, the BIP errors are reported.
If B1, B2 and B3 bit errors cross the 10-6 threshold, alarms such as the B1_SD, B2_SD,
B3_SD occur. If B1, B2 and B3 bit errors cross the 10-3 threshold, alarms such as the
B1_EXC, B2_EXC and B3_EXC occur.
When B1 detects 10 consecutive SESs in the RS, it indicates that an RSUAT event occurs.
When B2 detects 10 consecutive SESs in the MS, it indicates that an MSUAT event occurs.
When B3 detects 10 consecutive SESs, it indicates that an HPUAT event occurs.
When V5 detects 10 consecutive SESs, it indicates that an LPUAT event occurs.
1.5.2 Pointer Justification
With the pointer justification, rate asynchronization and phase difference of payload signals
are allowed. The pointer justification adjusts the rate of the information payloads so that they
are synchronized with the STM-N frame.
SDH payload pointers can be classified into administrative unit pointer (AU_PTR) and
tributary board pointer (TU_PTR). Pointer justification involves administrative unit pointer
justification and tributary board pointer justification.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 22
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
Generation Mechanism of AU Pointer Justification
In the AU-4 frame shown in Figure 1-10, several bytes in specific locations (the first nine
bytes in the fourth row) are used to record 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-10 Location and content of AU_PTR
9 rows
VC-4
H1 YY H2 1* 1* H3 H3 H3
AU- 4 PTR 1 9
Y Byte: 1001SS11 (S Unspecified ) 10 270columns
1* Byte: 11111111
When the network is synchronous, the pointer is used to perform phase alignment among the
synchronous signals. If the NEs work under the same clock, the signals that are transmitted
from various NEs to a certain NE have the same clock frequency. Therefore, rate adaptation is
unnecessary. 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 virtual container (VC) is different from that of the administrative unit
group (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. Therefore, positive and negative pointer
justifications are performed. See Table 1-4.
Table 1-4 Pointer justification states
State Byte Numbering and Content of the Fourth Row in the Rate
Name STM-1 Frame Relatio
nship
7 8 9 10 11 12
Pointer H3 H3 H3 Informat Informat Informati Informat
zero ion ion on ion =
justificat containe
ion r
Positive H3 H3 H3 Stuffing Stuffing Stuffing Informat
pointer ion <
justificat containe
ion r
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 23
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
State Byte Numbering and Content of the Fourth Row in the Rate
Name STM-1 Frame Relatio
nship
7 8 9 10 11 12
Negative Informat Informati Informat Informat Informat Informati Informat
pointer ion on ion ion ion on ion >
justificat containe
ion r
NOTE
The information rate is the VC frame rate. The container rate is the AU encapsulation rate.
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
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, the signal is adapted to realize synchronization. Therefore, TU
pointer justification that is detected on the tributary board is generally transformed from
AU pointer justification.
l TU pointer justification occurs during demultiplexing.
If the system clock is inconsistent with the received clock, TU pointer justification
occurs during demultiplexing.
l When the upstream NE that the service passes through has pointer justification, TU
pointer justification occurs at the local NE during demultiplexing.
Detection and Reporting of Pointer Justifications
There are two modes of detection and reporting of AU pointer justification: remote detection
and local detection.
l Remote detection
The information about AU pointer justification that is generated at the local NE is
transferred to the remote NE through the H1 and H2 bytes. The remote NE reports the
AU pointer justification by interpreting the H1 and H2 bytes. Therefore, if the remote
NE reports an AU pointer justification event, the local NE has pointer justification. The
remote NE is the downstream NE in the service direction.
l Local detection
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 24
OptiX OSN 500/550/580 1 Generation of Alarms and Performance Events of SDH
Alarms and Performance Events Reference Services
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 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 25
OptiX OSN 500/550/580
Alarms and Performance Events Reference 2 Detecting and Reporting an Ethernet Alarm
2 Detecting and Reporting an Ethernet Alarm
About This Chapter
Alarms are always the information sources for checking the running state of equipment and
for locating faults. This section mainly describes the Ethernet alarm reporting flow and the
correlation rules of common service alarms on the packet domain.
2.1 Alarm Reporting Flow
The alarm reporting flow indicates the entire process from alarm generation to alarm
notification. The alarm reporting flow provides guidelines on handling alarms.
2.2 Alarm Correlation
When faults or exceptions occur on a network, a series of alarms are generated. Certain
alarms are crucial to fault locating and these alarms are considered as key alarms. In contract,
certain alarms interfere in fault locating and these alarms are considered as interference
alarms. Key alarms and interference alarms, however, have correlations between each other.
The packet domain supports the alarm correlation analysis function. Hence, alarm correlation
information helps in locating faults.
2.1 Alarm Reporting Flow
The alarm reporting flow indicates the entire process from alarm generation to alarm
notification. The alarm reporting flow provides guidelines on handling alarms.
Figure 2-1 shows the alarm reporting flow.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 26
OptiX OSN 500/550/580
Alarms and Performance Events Reference 2 Detecting and Reporting an Ethernet Alarm
Figure 2-1 Alarm reporting flow
Start
Alarms are detected by
board and saved to the
board alarm library
Whether to suppress Yes The alarm is suppressed
NE alarm and not monitored
No
Process the alarm according
to the specified alarm
reversion mode
Save the alarm to the SCC
alarm library
Whether to
Yes synchronize
alarms?
No
Alarm automatic No The alarm is not reported,
reporting? but the board keeps
monitoring the alarm
Yes
Whether to mask Yes
NE alarm? Discard the alarm data
No
The EMS detects the EMS
Save the alarm data to the alarm and saves it to the
EMS server EMS server
Alarm
correlation analysis Whether to mask Yes
NMS alarm?
No
Display the alarm on the
client
No
Whether to set alarm
notification?
Yes
Send alarm data to the
receive end
End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 27
OptiX OSN 500/550/580
Alarms and Performance Events Reference 2 Detecting and Reporting an Ethernet Alarm
NOTE
For details on alarm masking, automatic alarm reporting, and alarm filtering, see the OptiX iManager
U2000 Online Help or 1.1.3 Alarm Management.
2.2 Alarm Correlation
When faults or exceptions occur on a network, a series of alarms are generated. Certain
alarms are crucial to fault locating and these alarms are considered as key alarms. In contract,
certain alarms interfere in fault locating and these alarms are considered as interference
alarms. Key alarms and interference alarms, however, have correlations between each other.
The packet domain supports the alarm correlation analysis function. Hence, alarm correlation
information helps in locating faults.
Correlated alarms have the following characteristics:
l Alarms (root alarms) directly caused by a fault or an exception may generate other
alarms (correlated alarms). A root alarm and its correlated alarms have correlations.
l If multiple alarms occur due to the same fault or exception, these alarms are correlated.
On the packet domain, the alarm correlation rules are as follows:
l Alarm masking is implemented on the same equipment.
l The root alarm masks its correlated alarms.
l An alarm resulting from a fault at a lower layer of the hierarchical service model masks
off the alarms resulting from a fault at an upper layer of the hierarchical service model.
NOTE
The hierarchical service model contains the physical layer, data link layer, tunnel layer, PW layer, and
emulated service layer, in an ascending order. In the service model, upper layers function depending on
the services provided by lower layers. When a lower layer and an upper layer have faults at the same
time, the fault at the lower layer must be removed prior to removing the fault at the upper layer. At this
time, the alarm resulting from the lower-layer fault masks off the alarm resulting from the upper-layer
fault.
Figure 2-2 and Figure 2-3 respectively illustrate the alarm correlation rules for the packet
Ethernet services transmitted at the Ethernet port based on the MPLS and MPLS-TP
protocols.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 28
OptiX OSN 500/550/580
Alarms and Performance Events Reference 2 Detecting and Reporting an Ethernet Alarm
Figure 2-2 Alarm correlation rules for the Ethernet services transmitted over Ethernet ports
LSR_NO_FITED
Physical
LASER_MOD_ERR
ETH_LOS LASER_SHUT
Data-Link ETH_LINK_DOWN
MPLS_TUNNEL_FDI
LAG_MEMBER_ ETH_EFM_DF
DOWN
ETH_EFM_
REMFAULT
ETH_EFM_EVENT
MPLS_TUNNEL_ MPLS_TUNNEL_
FDI MISMATCH
Tunnel
MPLS_TUNNEL_
MERGE
MPLS_TUNNEL_ MPLS_TUNNEL_
MPLS_TUNNEL_BDI
BDI LOCV
MPLS_TUNNEL_ MPLS_TUNNEL_ MPLS_TUNNEL_SF
UNKNOWN Excess
MPLS_TUNNEL_SD
MPLS_PW_
PW MISMATCH
MPLS_PW_BDI
MPLS_PW_
MPLS_PW_LOCV
MISMERGE
MPLS_PW_BDI
MPLS_PW_
UNKNOWN MPLS_PW_SF
MPLS_PW_EXCESS MPLS_PW_SD
Emulated
ETH_CFM_RDI ETH_CFM_
Service
MISMERGE
（Ethernet）
ETH_CFM_
UNEXPERI
ETH_CFM_RDI
ETH_CFM_LOC
Alarm A suppresses the notification
A1 A2 Alarm A1 suppresses alarm A2 A N message N sent by the local NE
N indicates the notification message that is sent Notification message N1 suppresses
N or received by the NE
N1 N2
notification message N2
The NE generates alarm A and Notification message N suppresses
A N sends the notification message N N A alarm A
to other NEs
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 29
OptiX OSN 500/550/580
Alarms and Performance Events Reference 2 Detecting and Reporting an Ethernet Alarm
Figure 2-3 Alarm correlation rules for the packet Ethernet services transmitted at the Ethernet
port based on the MPLS-TP protocol
LSR_NO_FITED
Physical
LASER_MOD_ERR
ETH_LOS LASER_SHUT
Data-Link ETH_LINK_DOWN
MPLS_TUNNEL_AIS
ETH_EFM_DF
ETH_EFM_
REMFAULT
ETH_EFM_EVENT
MPLS_TUNNEL_ MPLS_TUNNEL_
AIS UNEXPMEG
Tunnel
MPLS_TUNNEL_
UNEXPMEP
MPLS_TUNNEL_
LOCV MPLS_TUNNEL_ MPLS_TUNNEL_RDI
MPLS_TUNNEL_ MPLS_TUNNEL_ UNEXPPER
RDI OAMFAIL
MPLS_TUNNEL_SF
MPLS_TUNNEL_
LOCK
MPLS_TUNNEL_SD
PW MPLS_TUNNEL_ MPLS_PW_
AIS UNEXPMEG
MPLS_PW_
MPLS_PW_RDI
OAMFAIL
MPLS_PW_
UNEXPMEP
MPLS_PW_LCK
MPLS_PW_LOCV MPLS_PW_RDI
MPLS_TUNNEL_
UNEXPPER
MPLS_PW_SF
MPLS_PW_SD
Emulated ETH_CFM_
UNEXPERI
Service ETH_CFM_RDI ETH_CFM_MISMERGE
（Ethernet）
ETH_CFM_
AIS
ETH_CFM_RDI
ETH_CFM_
LOC
Alarm A suppresses the notification
A1 A2 Alarm A1 suppresses alarm A2 A N message N sent by the local NE
N indicates the notification message that is sent Notification message N1 suppresses
N or received by the NE
N1 N2
notification message N2
The NE generates alarm A and Notification message N suppresses
A N sends the notification message N N A alarm A
to other NEs
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 30
OptiX OSN 500/550/580
Alarms and Performance Events Reference 3 Detecting Ethernet Performance Events
3 Detecting Ethernet Performance Events
Ethernet service performance events are used to count the packets transmitted and received
and the transmission quality of Ethernet services.
Data boards count the packets transmitted and received on each Ethernet port. The statistical
items include the number of packet losing events and the number of bytes in corrupted
packets transmitted and received.
Data boards monitor performance. The chips on most data boards support statistics. For
example, in the case of 15 minutes' performance statistics collection, a data board finds an
idle performance register, deletes the data in the register at the beginning of each period, and
then counts the performance events. At the end of each period, the data board saves the
performance statistics into the register.
Data boards read the number of packets entering each port and report it to the platform. Then,
the platform detects whether the RMON statistical value crosses the preset performance event
threshold.
l If the RMON statistical value does not cross the threshold within a period of time, the
platform directly reports the RMON statistical value to the NE.
l If the RMON statistical value crosses the threshold within a period of time, the platform
reports an RMON threshold-crossing event to the NE.
Figure 3-1 shows the performance reporting flow.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 31
OptiX OSN 500/550/580
Alarms and Performance Events Reference 3 Detecting Ethernet Performance Events
Figure 3-1 Performance reporting flow
Whether to No
enable the performance End
monitoring?
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 Yes The abnormal performance
current performance cross
event is reported to the NM
the threshold?
No
Whether to
enable the automatic
reporting?
Yes
The performance data is No
reported to the NM and End
saved in the database
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 32
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4 Alarm Reference
About This Chapter
This chapter lists the alarms of the equipment and describes how to clear these alarms.
4.1 Alarm List
This section lists the alarms supported by the OptiX OSN equipment in an alphabetical order.
4.2 Alarm Clearing
This section describes how to clear alarms.
4.1 Alarm List
This section lists the alarms supported by the OptiX OSN equipment in an alphabetical order.
4.1.1 Alarm List A
This section used a table to list the alarms starting with A.
Name Description Severity Applicable
Equipment
A_LOC Indicates that the upstream bus clock at the Major OptiX OSN
electrical port of a tributary board is lost. 550/580
ACR_L Indicating a failure to lock the IEEE 1588 Major OptiX OSN
OCK_F ACR. 550/500
AIL
AD_CH Indicates an AD (analog-to-digital converter) Major OptiX OSN
ECK_F self-check failure. 550/580
AIL
ALM_A Indicates that the laser on a line board is in the Minor OptiX OSN
LS auto laser shutdown (ALS) state. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 33
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
ALM_E Alarm indication at the remote end of an E1 Minor OptiX OSN
1RAI link. 550/500
ALM_G Indicating the GFP frame signal is lost. Major OptiX OSN
FP_dLF 550
D
ALM_G Indicating the loss of GFP client signal. Critical OptiX OSN
FP_dCS 550
F
ALM_I Out-of-frame alarm in an IMA link. Major OptiX OSN
MA_LI 550/500
F
ALM_I Indicates that the differential delay in the IMA Major OptiX OSN
MA_LO link crosses the threshold. 550/500
DS
ALM_I Indicates the failure in receiving signals on the Minor OptiX OSN
MA_RE remote IMA link. 550/500
_RX_U
NUSAB
LE
ALM_I Indicates the failure in transmitting signals on Minor OptiX OSN
MA_RE the remote IMA link. 550/500
_TX_U
NUSAB
LE
ALM_I Out-of-frame alarm in the remote IMA link. Major OptiX OSN
MA_RF 550/500
I
APS_FA Indicates that the multiplex section protection Major OptiX OSN
IL (MSP) switching fails. 550/580
APS_IN Indicates that the multiplex section protection Major OptiX OSN
DI (MSP) switching occurs. 550/580
APS_M Indicates that the automatic multiplex section Minor OptiX OSN
ANUAL protection (MSP) switching protocol is stopped 550/580
_STOP manually.
ARP_F Indicates that an Ethernet port fails to learn the Major OptiX OSN
AIL MAC address of the remote end using the ARP. 500/550/580
ARP_M Indicates that the configured static ARP MAC Major OptiX OSN
AC_MI address is different from the actual MAC 500/550/580
SMATC address.
H
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 34
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
ARP_SP Indicating an ARP spoofing attack. Major OptiX OSN
OOF 500/550/580
ATMP Indicates that the number of unknown ATM Major OptiX OSN
W_UN cells exceeds the specified threshold in a time 550/500
KNOW unit.
NCELL
_EXC
AU_AIS Indication of the administrative unit (AU). Major OptiX OSN
550/580
AU_LO Indicating the loss of the AU pointer. Minor OptiX OSN
P 550/580
4.1.2 Alarm List B
This section used a table to list the alarms starting with B.
Name Description Severity Applicable
Equipment
B1_EX Indicates that the number of regenerator Minor OptiX OSN
C section B1 bit errors in signals received 550/580
by the line board crosses the threshold.
B1_SD Indicates that regenerator section B1 Minor OptiX OSN
signals received by the line board are 550/580
degraded.
B2_EX Indicates that the number of multiplex Major OptiX OSN
C section B2 bit errors in signals received 550/580
by the line board crosses the threshold.
B2_SD Indicates that multiplex section B2 Minor OptiX OSN
signals received by the line board are 550/580
degraded.
B3_EX Indicates that the number of higher order Major OptiX OSN
C B3 bit errors in signals received by the 550/580
line board crosses the threshold.
B3_EX Indicates that B3 bit errors in a VC-3 path Major OptiX OSN
C_VC3 cross the threshold. 550/580
B3_EX Indicates that B3 bit errors in a VC-4 path Major OptiX OSN
C_VC4 cross the threshold. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 35
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
B3_SD Indicates that higher order path B3 Minor OptiX OSN
signals received by the line board are 550/580
degraded.
B3_SD_ Indicates that B3 signals in a VC-3 path Minor OptiX OSN
VC3 degrade. 550/580
B3_SD_ Indicates that B3 bit errors in a VC-4 path Minor OptiX OSN
VC4 cross the set deterioration threshold. 550/580
BAT1T Indicates that the temperature sensor of Major OptiX OSN
EMP_S battery group 1 fails. 550/500
ENSOR
_FAIL
BAT2T Indicates that the temperature sensor of Major OptiX OSN
EMP_S battery group 2 fails. 550/500
ENSOR
_FAIL
BD_NO Indicates that the logical board is not Minor OptiX OSN
T_INST installed in the correct slot. 550/500/580
ALLED
BD_ST Indicates that the created logical board is Major OptiX OSN
ATUS offline. 550/500/580
BD_VE Indicates a board version mismatch. Major OptiX OSN 580
R_NOT
_MATC
H
BD_VE Indicates a board version mismatch. Major OptiX OSN
R_NMA 550/580
T
BDID_E Indicates that errors occur in slot Major OptiX OSN
RROR verification. 550/580
BDTEM Indicates that the temperature sensor on Major OptiX OSN
P_SENS the board fails. 550/500
OR_FAI
L
BEFFE Forward error correction (FEC) signals Minor OptiX OSN 580
C_EXC degrade.
BIOS_S Indicates the BIOS status. Major OptiX OSN
TATUS 550/500/580
BIP_EX BIP excessive bit errors. Minor OptiX OSN
C 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 36
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
BIP_SD BIP signal degrade. Minor OptiX OSN
550/580
BOOTR Indicates the BOOTROM data check Major OptiX OSN
OM_BA failure. 550/500/580
D
BRDCA Indicates that the ratio of broadcast traffic Major OptiX OSN
STRATI exceeds the threshold. 550/500
O_OVE
R
BUS_E Indicates a bus is abnormal. Critical OptiX OSN
RR 550/500/580
BUS_L Indicates that the downstream bus clock Major OptiX OSN
OC on the tributary board is lost. 550/580
BWUTI Indicates that bandwidth usage exceeds Warning OptiX OSN 580
LIZATI the threshold.
ON_OV
ER
4.1.3 Alarm List C
This section used a table to list the alarms starting with C.
Name Description Severity Applicable
Equipment
C2_VCAIS Indicates a C2 byte alarm. Minor OptiX OSN 580
C3794_SLOT The actually received timeslot Major OptiX OSN
NUM_ERR bandwidth of C37.94 services 550/580
does not match the configured
timeslot bandwidth on the NMS.
C3794_RDI Indicates that data reception of Minor OptiX OSN
C37.94 services at the remote end 550/580
fails.
C3794_AIS Indicates that C37.94 services are Minor OptiX OSN
faulty. 550/580
CES_ACR_L Indicates that the CES ACR clock Minor OptiX OSN
OCK_ABN is locked abnormally. 550/500
CES_APS_IN Indicates that the configured Major OptiX OSN
DI packet MSP for a CES service is 550/500
in the switching state.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 37
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
CES_APS_M Indicates that the packet linear Minor OptiX OSN
ANUAL_STO MSP protocol is stopped 550/500
P manually.
CES_JTROV Indicates that the number of jitter Major OptiX OSN
R_EXC buffer overflows exceeds the 550/500
specified threshold value.
CES_JTRUD Indicates that the number of jitter Major OptiX OSN
R_EXC buffer underflows exceeds the 550/500
specified threshold value.
CES_K1_K2_ Indicates the mismatch between Minor OptiX OSN
M the K1 byte and the K2 byte. 550/500
CES_K2_M Indicates that a mismatched K2 Minor OptiX OSN
byte of packet MSP is detected. 550/500
CES_LOSPK Indicates that the number of lost Major OptiX OSN
T_EXC CES service packets exceeds the 550/500
specified threshold in a certain
period.
CES_MALPK Indicates that the number of Major OptiX OSN
T_EXC deformed CES service packets 550/500
exceeds the specified threshold in
a certain period.
CES_MISOR Indicates that the number of lost Major OptiX OSN
DERPKT_EX out-of-order CES service packets 550/500
C exceeds the specified threshold in
a certain period.
CES_RDI Indicates a failure in remote CES Minor OptiX OSN
services. 550/500
CES_STRAY Indicates that the number of error Major OptiX OSN
PKT_EXC CES service packets exceeds the 550/500
specified threshold in a certain
period.
CESPW_OPP Indicates a defect in an Major OptiX OSN
OSITE_ACFA attachment circuit. 550/500
ULT
CESPW_OPP Indicates an alarm on the NE at Major OptiX OSN
OSITE_RAI the opposite end. 550/500
CFCARD_FA Indicates that operations on the Major OptiX OSN
ILED CF card fail. 550/500
CFCARD_FU Indicates that the capacity of the Major OptiX OSN
LL CF card is used up. 550/500
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 38
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
CFCARD_OF Indicates that the CF card is Major OptiX OSN
FLINE offline. 550/500
CFG_DATAC Indicates an error in routine Major OptiX OSN
HECK_FAIL database check. 550/500/580
CFG_DATAS Indicates a data save failure. Major OptiX OSN
AVE_FAIL 550/500/580
CHCS Indicates that a correctable bit Minor OptiX OSN
error occurs in the cell header. 550/500
CHIP_ABN Indicates a failure in the voltage Minor OptiX OSN 550
chip or temperature chip.
CLK_LOCK_ Indicates a failure to lock the Major OptiX OSN
FAIL clock. 550/500/580
CLK_NO_TR Indicates that the clock changes to Minor OptiX OSN
ACE_MODE a non-tracing running mode. 550/500/580
COM_EXTE Indicates the excessive number of Major OptiX OSN
CC_FULL TCP connections between the 550/500/580
NEs running the automatic
extended ECC communication
protocol.
COMMUN_F Indicates an inter-board Major OptiX OSN
AIL communication failure. 550/500/580
CPU_BUSY Indicates that the CPU utilization Major OptiX OSN
is excessively high. 550/500
CRC4_ERR_ Indicates that the errors of CRC4 Minor OptiX OSN
OVER check for the E1 services cross the 550/580
threshold.
CTS Indicates that the data terminal Major OptiX OSN
equipment (DTE, namely, the 550/580
DDN service board) at the local
station has detected the abnormal
Clear To Send status.
4.1.4 Alarm List D
This section used a table to list the alarms starting with D.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 39
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
DB_RES Indicates that service restoration Major OptiX OSN
TORE_F fails due to failed access to the 550/500/580
AIL database.
DBMS_ Indicates that the database of an Critical OptiX OSN
DELETE NE is deleted. 550/500/580
DBMS_ Indicates a database error. Critical OptiX OSN
ERROR 550/500/580
DBMS_P Indicates that the system database Critical OptiX OSN
ROTECT is in the protected mode. 550/500/580
_MODE
DB_UNS Indicates that the configuration Critical OptiX OSN
AVE data in the database is not 550/580
permanently stored in the
NVRAM, DRDB, or FDB storage
area.
DCC_C Indicates that DCC channel Major OptiX OSN
HAN_L resources are insufficient. 550/580
ACK
DCD Indicates that the data terminal Major OptiX OSN
equipment (DTE, namely, the 550/580
DDN service board) at the local
station has detected the abnormal
Digital Carrier Detector status.
DCN_C Indicates a bit error on an outband Major OptiX OSN
HANNE DCN channel. 550/500/580
L_BITE
RROR
DCNSIZ Indicates an over-sized DCN Major OptiX OSN
E_OVER network. 550/500/580
DDN_AI Indicates signal at the DDN port. Minor OptiX OSN
S 550/580
DDN_A Indicates the loss of signal at the Major OptiX OSN
LOS DDN port. 550/580
DDN_C Indicates that the number of Minor OptiX OSN
RC4_ER CRC4 check errors in the 2 550/580
R_OVER Mbit/s services on the electrical
interface side crosses the
threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 40
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
DDN_LF Indicates the loss of frame Major OptiX OSN
A alignment in the PDH framed E1 550/580
services on the electrical interface
side.
DDN_L Indicates the loss of mulitframe Major OptiX OSN
MFA alignment in the PDH framed E1 550/580
services on the DDN side.
DDN_L Indicates that a loopback event Minor OptiX OSN
OOP_AL occur at the DDN port. 550/580
M
DDN_RF Indicates that a remote frame Minor OptiX
A alignment alarm of the framed E1 OSN550/580
services on the DDN side of a
board.
DDN_R Indicates that a remote alarm of Minor OptiX OSN
MFA the framed E1 multiframe on the 550/580
DDN side of a board.
DELAY_ The latency compensation fails on Major OptiX OSN
ADAPT_ the channel which is marked as 550/580
INVALI latency-sensitive.
D
DLAG_P Indicates that the DLAG Major OptiX OSN
ROTECT protection fails. 550/580
_FAIL
DOWN_ Downstream E1 alarm indication Minor OptiX OSN
E1_AIS signal. 550/580
DOWN_ Downstream T1 alarm indication Minor OptiX OSN
T1_AIS signal. 550/580
DROPR Indicates that packet loss exceeds Minor OptiX OSN
ATIO_O the threshold due to congestion. 550/500/580
VER
DSR Indicates that the DTE at the local Major OptiX OSN
end has detected the DCE at the 550/580
opposite station works
abnormally.
DTR Indicates that the DCE at the local Major OptiX OSN
end has detected the DTE at the 550/580
opposite end works abnormally.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 41
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.1.5 Alarm List E
This section used a table to list the alarms starting with E.
Name Description Severity Applicable
Equipment
E1_LOS Indicates loss of 2 Mbit/s Minor OptiX OSN
line signals (E1 signals). 550/580
E1_LOC Indicates that the uplink 2M Major OptiX OSN
clock is lost. 550/580
E1DCN_64K Indicates a timeslot resource Major OptiX OSN
_CONFLICT conflict between the E1 550/580
DCN and 64 kbit/s services.
E1DCN_SNC Indicates a mismatch Minor OptiX OSN
P_MM between E1 DCN and E1 550/580
SNCP.
ELAN_SMA Indicates flapping of the Major OptiX OSN
C_FLAPPIN source MAC address 550/500/580
G learned by an E-LAN
service
ELPS_CFG_ Indicating that ELPS Major OptiX OSN
MISMATCH configurations differ 550/500
between two ends of a link.
ENVHUM_S Indicates that the ambient Major OptiX OSN
ENSOR_FAI humidity sensor fails. 550/500
L
ENVTEMP_S Indicates that the ambient Major OptiX OSN
ENSOR_FAI temperature sensor fails. 550/500
L
ENVTEMP1_ Indicates that ambient Major OptiX OSN
SENSOR_FA temperature sensor 1 fails. 550/500
IL
ENVTEMP2_ Indicates that ambient Major OptiX OSN
SENSOR_FA temperature sensor 2 fails. 550/500
IL
ERPS_IN_PR Indicates that EPRS ring is Minor OptiX OSN
OTECTION in protection mode. 550/500/580
ERPS_BLOC Indicates that a port on the Minor OptiX OSN
K ERPS ring is blocked when 550/500/580
protection switching is
triggered (not in the idle
state).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 42
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
ERPS_NOT_ Indicates that the ERPS Minor OptiX OSN
COMPLETE configuration is incomplete. 550/500/580
ETH_APS_L Indicates that the Automatic Minor OptiX OSN
OST Protection Switching (APS) 550/500/580
frames are lost.
ETH_APS_P Indicates that the working Major OptiX OSN
ATH_MISM and protection paths of the 550/500/580
ATCH APS protection group differ
between both ends.
ETH_APS_S Indicates a protection Minor OptiX OSN
WITCH_FAI switching failure. 550/500/580
L
ETH_APS_T Indicates a protection Major OptiX OSN
YPE_MISMA scheme mismatch. 550/500/580
TCH
ETH_CFM_A Indicates that a local Major OptiX OSN
IS maintenance end point 550/500/580
(MEP) receives an alarm
indication signal (AIS).
ETH_CFM_L Indicates loss of continuity. Major OptiX OSN
OC 550/500/580
ETH_CFM_ Indicates an incorrect Major OptiX OSN
MISMERGE connection. 550/500/580
ETH_CFM_R Indicates that the receive Minor OptiX OSN
DI end of the MEP at the 550/500/580
opposite end fails.
ETH_CFM_U Indicates an incorrect frame. Minor OptiX OSN
NEXPERI 550/500/580
ETH_EFM_D Indicates that negotiation of Major OptiX OSN
F the P2P OAM protocol fails 550/500/580
at a port.
ETH_EFM_E Indicates that an event Major OptiX OSN
VENT occurs on the opposite NE. 550/500/580
ETH_EFM_L Indicates that a loopback Major OptiX OSN
OOPBACK occurs. 550/500/580
ETH_EFM_R Indicates that the opposite Critical OptiX OSN
EMFAULT NE is faulty. 550/500/580
ETH_LINK_ Indicates that the connection Critical OptiX OSN
DOWN at the Ethernet port is faulty. 550/500/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 43
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
ETH_LOS Indicates loss of Ethernet Critical OptiX OSN
port connection. 550/500/580
ETH_NO_FL Indicates that the ETH port Major OptiX OSN
OW has no traffic. 550/500/580
ETHOAM_D Indicating the point-to-point Minor OptiX OSN
ISCOVER_F Ethernet OAM discovery 550/580
AIL failure.
ETHOAM_R Indicating a critical fault of Minor OptiX OSN
MT_CRIT_F the point-to-point Ethernet 550/580
AULT OAM function at the remote
end.
ETHOAM_R Indicating the remote Minor OptiX OSN
MT_LOOP loopback of the point-to- 550/580
point Ethernet OAM.
ETHOAM_R Indicating the remote Minor OptiX OSN
MT_SD performance degradation of 550/580
the point-to-point Ethernet
OAM function.
ETHOAM_S Indicates loopback of the Major OptiX OSN
ELF_LOOP MAC port that runs the 550/500/580
point-to-point OAM
protocol.
ETHOAM_V Indicating the loopback of Major OptiX OSN
CG_SELF_L the VCTRUNK port that 550/580
OOP runs the point-to-point
OAM protocol.
EX_ETHOA Indicating the loss of the Critical OptiX OSN
M_CC_LOS periodic connectivity check 550/580
(CC) packets.
EX_ETHOA Indicating the ID conflict of Major OptiX OSN
M_MPID_CN the MEP. 550/580
FLCT
EXT_SYNC_ Indicates loss of the external Critical OptiX OSN
LOS clock source set on the clock 550/500/580
board.
EXT_TIME_ Indicates that the external Major OptiX OSN
LOC time source is lost. 550/500/580
4.1.6 Alarm List F
This section lists alarms starting with F.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 44
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
FAN_AGIN Alarm of an aged fan. Minor OptiX OSN
G 550/500
FAN_COM Indicates communication Major OptiX OSN 580
M_FAIL between the fan board and the
NE fails
FAN_FAIL Indicates that fans of the NE Major OptiX OSN
fail. 550/500/580
FAN_FAUL Indicates a fan fault Minor OptiX OSN 580
T
FCS_ERR Indicating that errors occur in Critical OptiX OSN
the verification of the frame 550/580
check sequence (FCS).
FDBSIZEAL Indicates that the E-LAN Minor OptiX OSN
M_ELAN forwarding table entries are 550/500/580
exhausted.
FEATURE_ Indicates a feature is used Major OptiX OSN
WITHOUT_ without a valid license. 550/500/580
LICENSE
FLOW_OVE Indicates that the receive Minor OptiX OSN
R traffic of the port exceeds the 550/500/580
limit.
FUSE_ALA Indicates output offline. Critical OptiX OSN
RM 550/500
FXO_POWE Indicates the absence of a Major OptiX OSN
R_FAULT feeding current on a foreign 550/580
exchange office (FXO) port.
FXS_LINE_ Indicates that a signal wire in Major OptiX OSN
FAULT a telephone line connecting to 550/580
a foreign exchange subscriber
(FXS) port is grounded or
connects to a -48 V voltage.
FXS_POWE Indicates that a telephone line Major OptiX OSN
R_FAULT connecting to a foreign 550/580
exchange subscriber (FXS)
port and a 220 V electrical
power cable are in contact.
FIB_LEN_C Indicates that the fiber length Minor OptiX OSN 580
HANGE changes.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 45
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
FIBER_ASY Indicates that the fiber Critical OptiX OSN 580
MMETRIC_ deviation value changes.
CHANGED
4.1.7 Alarm List H
This section used a table to list the alarms starting with H.
Name Description Severity Applicable
Equipment
HARD_ Indicates a board hardware failure. Critical OptiX OSN
BAD 550/500/580
HARD_ Indicates a hardware error. Minor OptiX OSN 580
ERR
HARD_ Indicating that a certain function is not Major OptiX OSN
NONSU supported by a board. 550/500/580
PPORT
HP_CR Indicates that the HP performance crosses Minor OptiX OSN
OSSTR the threshold. 550/580
HP_LO Indicates HP loss of multiframe. Major OptiX OSN
M 550/580
HP_R_F Indicates that the FIFO overflows on the Minor OptiX OSN
IFO HP receiving side. 550/580
HP_RDI Indicates that the local station receives a Minor OptiX OSN
remote defect indication in the higher 550/500/580
order path sent from the opposite station
HP_REI Indicates that the local station receives the Warning OptiX OSN
remote bit error in the higher order path 550/500/580
sent from the opposite station.
HP_SL Indicates mismatch of the higher order Minor OptiX OSN
M path signal label (C2) received by the line 550/500/580
board.
HP_T_F Indicates that the FIFO overflows at the Minor OptiX OSN
IFO transmit side of the line higher order path. 550/580
HP_TI Indicates mismatch of the higher order Minor OptiX OSN
M path trace identifier (J1) received by the 550/500/580
line board.
HP_UN Indicates that the higher order path Minor OptiX OSN
EQ received by the line board is unloaded. 550/500/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 46
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
HPAD_ Indicates that the performance of the Minor OptiX OSN
CROSS higher order path adaptation crosses the 550/580
TR threshold.
HSC_U Indicates an abnormal hot-backup state. Minor OptiX OSN
NAVAI 550/580
L
HPS_W Indicates that the delay difference Minor OptiX OSN
P_LATE between the working and protection paths 550/580
N_DIFF of the hitless protection group exceeds the
threshold.
HPS_W Indicates that the delay jitter in the Minor OptiX OSN
P_LATE working or protection path (long or short 550/580
N_JITT path) of the hitless protection group
ER exceeds the threshold.
4.1.8 Alarm List I
This section used a table to list the alarms starting with I.
Name Description Severity Applicable
Equipment
IGSP_ENTRIE Indicates that the number of Minor OptiX OSN
S_EXC IGMP Snooping multicast table 550/500/580
entries exceeds its upper
threshold.
IMA_GROUP_ Indicates a failure in the local Major OptiX OSN
LE_DOWN IMA group. 550/500
IMA_GROUP_ Indicates a failure in the remote Major OptiX OSN
RE_DOWN IMA group. 550/500
IMA_TXCLK_ Indicates that the transmit clock Minor OptiX OSN
MISMATCH modes at both ends of the IMA 550/500
group are different.
IN_PWR_ABN Indicates that the input optical Major OptiX OSN
power of the line board laser 550/500/580
crosses the lower or upper
threshold.
IN_PWR_HIG Indicates that the actual input Critical OptiX OSN
H optical power is higher than the 550/500/580
upper threshold of the input
power reference value.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 47
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
IN_PWR_LOW Indicates that the actual input Critical OptiX OSN
optical power is lower than the 550/500/580
lower threshold of the input
power reference value.
INSUFFCNT_F The file system space on the Critical OptiX OSN
LSH_SPACE flash is insufficient. 550/500/580
INSUFFCNT_ The file system space in the Critical OptiX OSN
MEM_SPACE memory is insufficient. 550/500/580
INTEMP_SEN Indicates that the inlet Major OptiX OSN
SOR_FAIL temperature sensor fails. 550/500
4.1.9 Alarm List J
This section used a table to list the alarms starting with J.
Name Description Severity Applicable
Equipment
J0_MM Indicates mismatch of the Minor OptiX OSN 550/580
regenerator section trace
identifier (J0) received by the
line board.
4.1.10 Alarm List K
This section used a table to list the alarms starting with K.
Name Description Severity Applicable
Equipment
K1_K2_ Indicates mismatch between Minor OptiX OSN 550/580
M the transmitted K1 byte and
received K2 byte in a linear
MSP group.
K2_M Indicates mismatch between Minor OptiX OSN 550/580
the received K2 byte and the
transmitted K2 byte of a linear
MSP group.
KMC_K Indicates a KMC key Critical OptiX OSN
EY_SY synchronization failure. 500/550/580
NC_FAI
L
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 48
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.1.11 Alarm List L
This section lists alarms starting with L.
Name Description Severity Applicable
Equipment
LAG_DO Indicates that a link aggregation Major OptiX OSN
WN group (LAG) is unavailable. 550/500/580
LAG_ME Indicates that a member port of a Minor OptiX OSN
MBER_D LAG is unavailable. 550/500/580
OWN
LAG_PO Indicating that a port in the LAG Minor OptiX OSN
RT_FAIL fails. 550/580
LASER_ Indicates that an optical module Minor OptiX OSN
CHECK_ reading/writing error occurs. 550/580
ERR
LASER_ Indicates that the user issues the Major OptiX OSN
CLOSED command of shutting down the 550/580
laser and the laser of the line board
is in the close status.
LASER_ Indicates mismatch of optical Major OptiX OSN
MOD_ER modules. 550/500/580
R
LASER_ Indicates that the pluggable optical Major OptiX OSN
MOD_ER module on the line board does not 550/580
R_EX match the optical port of the line
board.
LASER_ Indicates a mismatch of the optical Major OptiX OSN 580
MODUL module type and the fiber type.
E_MISM
ATCH
LASER_ Indicates that the laser of the board Major OptiX OSN
SHUT is shut down. 550/500/580
LASER_ Indicates that the optical module Major OptiX OSN 580
TYPE_M type does not match.
ISMATC
H
LCAS_F Indicating the protocol failure in Major OptiX OSN
OPR the LCAS receive direction. 550/580
Attribute
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 49
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
LCAS_F Indicating the protocol failure in Major OptiX OSN
OPT the LCAS transmit direction. 550/580
LCAS_P Indicating the loss of partial Minor OptiX OSN
LCR bandwidth in the LCAS receive 550/580
direction.
LCAS_P Indicating the loss of partial Minor OptiX OSN
LCT bandwidth in the LCAS transmit 550/580
direction.
LCAS_T Indicating the loss of all bandwidth Major OptiX OSN
LCR in the LCAS receive direction. 550/580
LCAS_T Indicating the loss of all bandwidth Major OptiX OSN
LCT in the LCAS transmit direction. 550/580
LCD Indicates loss-of-cell delimitation. Major OptiX OSN
550/500/580
LCS_DA Indicates that a license file remains Major OptiX OSN
YS_OF_ in the grace period. 550/500/580
GRACE
LCS_EX Indicates that a license file expires. Critical OptiX OSN
PIRED 550/500/580
LCS_FIL Indicates that the License file is not Critical OptiX OSN
E_NOT_ installed on the NE. 550/500/580
EXIST
LFA Indicates loss of E1 basic frame Major OptiX OSN
alignment. 550/500/580
LINK_E Indicates that the data link is Critical OptiX OSN
RR incorrect. 550/580
LMFA Indicates loss of multiframe Major OptiX OSN
alignment. 550/500/580
LOF_64K indicates that the local end carrying Major OptiX OSN
64 kbit/s services does not receive 550/580
any frames or frame alignment
signals from the remote end.
LOOP_A Indicates a loopback alarm. Minor OptiX OSN
LM 550/500/580
LP_CRO Indicates that the number of the Minor OptiX OSN
SSTR lower order path bit errors crosses 550/580
the threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 50
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
LP_R_FI Indicates that the FIFO messages Minor OptiX OSN
FO on the receive side of the lower 550/580
order path overflow.
LP_RDI Indicates the remote defect in the Minor OptiX OSN
lower order path of the tributary 550/580
board.
LP_RDI_ Indicates the remote defect in the Minor OptiX OSN
VC12 lower order path of the tributary 550/580
board.
LP_RDI_ Indicates the remote defect in the Minor OptiX OSN
VC3 lower order path of the tributary 550/580
board.
LP_REI Indicates the remote error Minor OptiX OSN
indication alarm in the lower order 550/580
path.
LP_REI_ Indicates the remote bit error in the Minor OptiX OSN
VC12 lower order path of the tributary 550/580
board.
LP_REI_ Indicates the remote bit error in the Minor OptiX OSN
VC3 lower order path of the tributary 550/580
board.
LP_RFI Indicates the remote failure Minor OptiX OSN
indication alarm in the lower order 550/580
path.
LP_SIZE Indicates the TU specification error Minor OptiX OSN
_ERR alarm. 550/580
LP_SLM Indicates signal label mismatch in Minor OptiX OSN
the lower order path. 550/580
LP_SLM Indicates the VC-12 lower order Minor OptiX OSN
_VC12 path signal label mismatch. 550/580
LP_SLM Indicates the VC-3 lower order Minor OptiX OSN
_VC3 path signal label mismatch. 550/580
LP_T_FI Indicates that the FIFO messages Minor OptiX OSN
FO on the transmit side of the lower 550/580
order path overflow.
LP_TIM Indicates trace identifier mismatch Minor OptiX OSN
in the lower order path. 550/580
LP_TIM_ Indicates the VC-12 lower order Minor OptiX OSN
VC12 path trace identifier mismatch. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 51
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
LP_TIM_ Indicates the VC-3 lower order Minor OptiX OSN
VC3 path trace identifier mismatch. 550/580
LP_UNE Indicates that no payload is Minor OptiX OSN
Q equipped in the lower order path. 550/580
LP_UNE Indicates the VC-12 lower order Minor OptiX OSN
Q_VC12 path unequipped. 550/580
LP_UNE Indicates the VC-3 lower order Minor OptiX OSN
Q_VC3 path unequipped. 550/580
LPS_UNI Indicates mismatch of the single- Minor OptiX OSN
_BI_M ended and dual-ended modes in a 550/580
linear MSP.
LPT_AU Indicates that LPT authentication Major OptiX OSN
TH_FAIL fails. 550/500/580
LPT_CF Indicates that the LPT closes a Major OptiX OSN
G_CLOS service port. 550/500/580
EPORT
LPT_RFI Indicates the remote failure Critical OptiX OSN
indication of Link state pass- 550/580
through (LPT).
LSR_CO Indicates that the cooling current of Major OptiX OSN 580
OL_ALM the laser crosses the threshold.
LSR_BC Indicates that the bias current of Major OptiX OSN
M_ALM the laser crosses the thresholds. 550/500/580
LSR_NO Indicates that the pluggable optical Critical OptiX OSN
_FITED module of the line board is not 550/500/580
installed.
LSR_WI Indicates that the life of the laser is Critical OptiX OSN
LL_DIE close to the end. 550/500/580
LTI Indicates loss of synchronization Major OptiX OSN
clock sources set for the clock 550/500/580
board.
4.1.12 Alarm List M
This section used a table to list the alarms starting with M.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 52
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
MAC_FCS_EX Indicates that a bit error threshold- Major OptiX OSN
C crossing event is detected at the MAC 500/550/580
layer.
MAC_EXT_EX Indicates that the number of bit errors at Major OptiX OSN
C the MAC layer crosses the threshold. 550/500
MASTER_SLA Indicating that the logical types of the Minor OptiX OSN
VE_MISMATC master and slave cross-connect boards are 550
H mismatched.
MCLAG_CFG_ Indicates that MC-LAG configurations at Major OptiX OSN
MISMATCH two ends are inconsistent. 580
MCSP_PATH_L Indicates the loss of connectivity on a Major OptiX OSN
OCV protocol channel on which synchronous 580
cross-equipment communication is
achieved.
MOD_COM_FA Indicates that the module communicates Major OptiX OSN
IL abnormally. 550/500
MOD_TYPE_M Indicates that a mismatched port module Critical OptiX OSN
ISMATCH is detected. 550/580
MDL_ALARM Power module faults. Major OptiX OSN
550/500
MP_DELAY Indicates that the differential delay of the Major OptiX OSN
PPP members in an MP group exceeds 550/500
the specified threshold.
MP_DOWN Indicates that an MP group fails. Major OptiX OSN
550/500
MPLS_PW_AIS Indicating that a defect is detected on a Major OptiX OSN
PW. 550/500/580
MPLS_PW_BDI Indicates defects in the backward Minor OptiX OSN
direction of a PW. 550/500
MPLS_PW_CS Indicates that client signals fail. Major OptiX OSN
F 550/500/580
MPLS_PW_Exc Indicates that excessive trail termination Warning OptiX OSN
ess source identifiers (TTSIs) of the PW are 550/500
received.
MPLS_PW_LC Indicates that the PW server layer is Major OptiX OSN
K locked. 550/500/580
MPLS_PW_LO Indicates that a command to lock the PW Major OptiX OSN
CK layer is issued on an MEP. 550/500/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 53
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
MPLS_PW_LO Indicates loss of PW connectivity. Major OptiX OSN
CV 550/500/580
MPLS_PW_MI Indicates mismatch of the TTSIs of PWs. Major OptiX OSN
SMATCH 550/500
MPLS_PW_MI Indicates that the TTSIs of PWs are Major OptiX OSN
SMERGE incorrectly merged. 550/500
MPLS_PW_OA Indicating that the OAM protocol Minor OptiX OSN
MFAIL negotiation fails. 550/500/580
MPLS_PW_RDI Indicating that a defect is detected on a Minor OptiX OSN
remote PW. 550/500/580
MPLS_PW_SD Indicates that the signal on a PW Major OptiX OSN
degrades. 550/500/580
MPLS_PW_SF Indicates that the signal on a PW Major OptiX OSN
degrades severely. 550/500/580
MPLS_PW_UN Indicating an error in the CCM Major OptiX OSN
EXPMEG information of the PW OAM packet. 550/500/580
MPLS_PW_UN Indicating an error of the PW OAM CCM Major OptiX OSN
EXPMEP information. 550/500/580
MPLS_PW_UN Indicating that the PW does not receive Major OptiX OSN
EXPPER CCM packets in the expected period. 550/500/580
MPLS_PW_UN Indicates that certain unknown defects Major OptiX OSN
KNOWN exist on a PW. 550/500
MPLS_TUNNE Indicating a defect is detected on a tunnel. Major OptiX OSN
L_AIS 550/500/580
MPLS_TUNNE Indicates defects in the backward Minor OptiX OSN
L_BDI direction of a tunnel. 550/500
MPLS_TUNNE Indicates that excessive Trail Termination Warning OptiX OSN
L_Excess Source Identifiers (TTSIs) are received. 550/500
MPLS_TUNNE Indicates defects in the forward direction Minor OptiX OSN
L_FDI of a tunnel. 550/500
MPLS_TUNNE Indicates that a command to lock the Minor OptiX OSN
L_LOCK tunnel layer is issued on an MEP. 550/500/580
MPLS_TUNNE Indicates loss of tunnel connectivity. Major OptiX OSN
L_LOCV 550/500/580
MPLS_TUNNE Indicates TTSI mismatch Major OptiX OSN
L_MISMATCH 550/500
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 54
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
MPLS_TUNNE Indicates that the TTSIs are mismerged Major OptiX OSN
L_MISMERGE on the tunnel. 550/500
MPLS_TUNNE Indicates that the source and sink nodes Minor OptiX OSN
L_OAMFAIL of a tunnel fail to negotiate on the OAM 550/500/580
protocol.
MPLS_TUNNE Indicating a defect is detected on a remote Minor OptiX OSN
L_RDI tunnel. 550/500/580
MPLS_TUNNE Indicates that the tunnel signal degrades. Major OptiX OSN
L_SD 550/500/580
MPLS_TUNNE Indicates that the tunnel signal degrades Major OptiX OSN
L_SF severely. 550/500/580
MPLS_TUNNE Indicating an error of the tunnel OAM Major OptiX OSN
L_UNEXPMEG CCM information. 550/500/580
MPLS_TUNNE Indicating an error of the tunnel OAM Major OptiX OSN
L_UNEXPMEP CCM information. 550/500/580
MPLS_TUNNE Indicating that the tunnel does not receive Major OptiX OSN
L_UNEXPPER CCM packet in expected period. 550/500/580
MPLS_TUNNE Indicates that certain unknown defects Major OptiX OSN
L_UNKNOWN exist on the tunnel. 550/500
MRING_APS_L Indicating APS packet loss in the east Major OptiX OSN
OST_E direction of an MPLS-TP ring. 550/500/580
MRING_APS_L Indicating APS packet loss in the west Major OptiX OSN
OST_W direction of an MPLS-TP ring. 550/500/580
MRING_APS_ Indicating incorrect configurations of east Major OptiX OSN
MISMATCH_E neighbor nodes on an MPLS-TP ring. 550/500/580
MRING_APS_ Indicating incorrect configurations of Major OptiX OSN
MISMATCH_W west neighbor nodes on an MPLS-TP 550/500/580
ring.
MRING_FAR_S Indicating an APS far-end switching Major OptiX OSN
W_FAIL_E failure in the east direction of an MPLS- 550/500/580
TP ring.
MRING_FAR_S Indicating an APS far-end switching Major OptiX OSN
W_FAIL_W failure in the west direction of an MPLS- 550/500/580
TP ring.
MRING_OAM_ Indicating OAM connectivity loss in the Critical OptiX OSN
LOCV_E east direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating OAM connectivity loss in the Critical OptiX OSN
LOCV_W west direction of an MPLS-TP ring. 550/500/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 55
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
MRING_OAM_ Indicating a remote defect in the east Minor OptiX OSN
RDI_E direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating a remote defect in the west Minor OptiX OSN
RDI_W direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating a signal degrade (SD) in the Major OptiX OSN
SD_E east direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating a signal degrade (SD) in the Major OptiX OSN
SD_W west direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating a signal fail (SF) in the east Major OptiX OSN
SF_E direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating a signal fail (SF) in the west Major OptiX OSN
SF_W direction of an MPLS-TP ring. 550/500/580
MRING_OAM_ Indicating that a east port on an MPLS- Critical OptiX OSN
UNEXPMEG_E TP ring receives an unexpected MEG ID. 550/500/580
MRING_OAM_ Indicating that a west port on an MPLS- Critical OptiX OSN
UNEXPMEG_ TP ring receives an unexpected MEG ID. 550/500/580
W
MRING_OAM_ Indicating that a east port on an MPLS- Major OptiX OSN
UNEXPMEP_E TP ring receives an unexpected MEP ID. 550/500/580
MRING_OAM_ Indicating that a west port on an MPLS- Major OptiX OSN
UNEXPMEP_W TP ring receives an unexpected MEP ID. 550/500/580
MRING_OAM_ Indicating that a east port on an MPLS- Major OptiX OSN
UNEXPPER_E TP ring receives unexpected period 550/500/580
information.
MRING_OAM_ Indicating that a east port on an MPLS- Major OptiX OSN
UNEXPPER_W TP ring receives unexpected period 550/500/580
information.
MS_AIS Indicates that the last three bits of the K2 Major OptiX OSN
byte in the signal received on the line 550/580
board are all "1"s.
MS_CROSSTR Indicates that the multiplex section Minor OptiX OSN
performance of the signal received by the 550/580
line board crosses the threshold.
MS_RDI Remote defect indication in the multiplex Minor OptiX OSN
section. 550/580
MS_REI Indicates that bit errors occur at the Warning OptiX OSN
remote end of the multiplex section. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 56
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
MSAD_CROSS Indicates that the number of multiplex Minor OptiX OSN
TR section bit errors crosses the threshold. 550/580
MUT_LOS Indicates loss of multiplexed signals. Critical OptiX OSN
550/580
MULTI_RPL_O Indicating that an Ethernet ring network Minor OptiX OSN
WNER contains more than one RPL_OWNER 550/500/580
node.
4.1.13 Alarm List N
This section lists alarms starting with N.
Name Description Severity Applicable
Equipment
NE_PO Indicates that the power consumption Major OptiX OSN
WER_O of an NE is over the threshold. 550/500/580
VER
NEBD_ Indicates that the cross-connect Critical OptiX OSN 580
XC_DIF matrix data of the NE and board is
different.
NEIP_C Indicates that an NE IP address Major OptiX OSN
ONFUS conflict occurs. 550/500/580
ION
NESF_L Indicates that the NE software is lost. Critical OptiX OSN
OST 550/500/580
NESOF Indicates that the NE software Major OptiX OSN
T_MM versions in the active and standby 550/500/580
system control units are inconsistent.
NESTA Indicates that the NE is in the Critical OptiX OSN
TE_INS installing state. 550/500
TALL
NO_BD Indicating that the software of the Critical OptiX OSN
_SOFT service board is damaged or does not 550/580
exist.
NO_BD Board not powered on. Major OptiX OSN 580
_POWE
R
NO_BD Indicates that board parameters are Critical OptiX OSN
_PARA not configured. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 57
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
NO_EL Indicates that the electronic label is Warning OptiX OSN
ABEL unloaded. 550/580
NO_LS Indicates that in the case of the Major OptiX OSN
R_PAR optical module with the EEPROM 550/580
A_FILE being used, no laser parameter files
are detected in the EEPROM of the
optical module after the board is
started.
NTP_S Indicates that NTP time Minor OptiX OSN
YNC_F synchronization fails. 550/500/580
AIL
NULL_ NULL signals (with payload being Warning OptiX OSN 580
SEND "0"s) being sent out.
4.1.14 Alarm List O
This section used a table to list the alarms starting with O.
Name Description Severity Applicable
Equipment
OA_LOW_ Indicates that the gain of the Critical OptiX OSN
GAIN optical amplifier is lower than the 550/580
threshold.
OCD Indicates out-of-cell delimitation. Major OptiX OSN
550/500
ODC_BATT Indicates that the current of the Major OptiX OSN
ERY_CUR storage battery is abnormal. 550/500
RENT_AB
N
ODC_BATT Indicates that the storage battery Major OptiX OSN
ERY_PWR fails to supply power for the 550/500
DOWN equipment.
ODC_DOO Indicates that the door of an Critical OptiX OSN
R_OPEN cabinet is open. 550/500
ODC_FAN_ Indicates that the fan is faulty. Major OptiX OSN
FAILED 550/500
ODC_HUM Indicates that the relative Minor OptiX OSN
I_ABN humidity in the cabinet 550/500
environment exceeds the specified
threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 58
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
ODC_LOA Indicates that the secondary load Major OptiX OSN
D_PWRDO is powered off. 550/500
WN
ODC_MDL Indicates that exceptions occur in Major OptiX OSN
_ABN the power module. 550/500
ODC_POW Indicates that exceptions occur in Major OptiX OSN
ER_FAIL the AC input power voltage or the 550/500
DC output power voltage.
ODC_SMO Indicates that smoke occurs in an Critical OptiX OSN
KE_OVER cabinet. 550/500
ODC_SUR Indicates that the surge protection Critical OptiX OSN
GE_PORTE function of the cabinet fails to 550/500
CTION_FAI work correctly.
L
ODC_TEC_ Indicates that the TEC air Major OptiX OSN
ALM conditioning module in the 550/500
cabinet fails to work correctly.
ODC_TEM Indicates that the ambient Minor OptiX OSN
P_ABN temperature of the cabinet or the 550/500
temperature of the storage battery
is inappropriate.
ODC_WAT Indicates that water enters the Critical OptiX OSN
ER_ALM cabinet. 550/500
ODUk_LOF ODUk loss of frame and Critical OptiX OSN 580
LOM multiframe
ODUk_PM_ ODUk PM alarm indication signal Warning OptiX OSN 580
AIS
ODUk_PM_ ODUk PM backward defect Warning OptiX OSN 580
BDI indication
ODUk_PM_ ODUk PM signal degraded Minor OptiX OSN 580
DEG
ODUk_PM_ ODUk PM signal locked Minor OptiX OSN 580
LCK
ODUk_PM_ ODUk PM open connection Minor OptiX OSN 580
OCI indication
ODUk_PM_ ODUk PM server layer signal Warning OptiX OSN 580
SSF failure
ODUk_PM_ ODUk PM TTI mismatch Minor OptiX OSN 580
TIM
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 59
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
ODUk_TC ODUk TCMn alarm indication Warning OptiX OSN 580
Mn_AIS signal.
ODUk_TC ODUk TCMn backward defect Warning OptiX OSN 580
Mn_BDI indication.
ODUk_TC ODUk TCMn signal being Minor OptiX OSN 580
Mn_DEG degraded.
ODUk_TC ODUk TCMn signal being locked. Minor OptiX OSN 580
Mn_LCK
ODUk_TC Loss of ODUk TCMn serial Minor OptiX OSN 580
Mn_LTC connection.
ODUk_TC ODUk TCMn open connection Minor OptiX OSN 580
Mn_OCI indication.
ODUk_TC Failure of ODUk TCMn server- Warning OptiX OSN 580
Mn_SSF layer signals.
ODUk_TC ODUk TCMn trace identifier Minor OptiX OSN 580
Mn_TIM mismatch.
OOL Indicates that the phase-locked Major OptiX OSN
loop is out of lock. 550/500/580
OPUk_MSI OPUk multiplex structure Minor OptiX OSN 580
M identifier mismatch.
OPUk_PLM OPUk payload mismatch Minor OptiX OSN 580
OTUk_AIS OTUk alarm indication signal Warning OptiX OSN 580
OTUk_BDI OTUk backward defect indication Warning OptiX OSN 580
OTUk_DEG OTUk signal degraded Minor OptiX OSN 580
OTUk_LOF Loss of OTUk frame Critical OptiX OSN 580
OTUk_LO Loss of OTUk multiframe Major OptiX OSN 580
M
OTUk_TIM OTUk TTI mismatch Minor OptiX OSN 580
OTUk_SSF The signal fails at the OTUk Warning OptiX OSN 580
server layer.
OUT_PWR Indicates that the output optical Critical OptiX OSN
_ABN power is abnormal. 550/500/580
OUT_PWR Output power is too high. Major OptiX OSN 580
_HIGH
OUT_PWR Output power is too low. Major OptiX OSN 580
_LOW
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 60
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
OUT1TEM Indicates that the temperature Major OptiX OSN
P_SENSOR sensor at the air outlet fails. 550/500
_FAIL
OUT2TEM Indicates that the external outlet Major OptiX OSN
P_SENSOR temperature sensor fails. 550/500
_FAIL
4.1.15 Alarm List P
This section lists alarms starting with P.
Name Description Severity Applicable
Equipment
P_AIS Indicates that the received signals on the Major OptiX OSN
PDH side of the E3/T3 tributary board 550/580
are all 1s.
P_LOC Indicates loss of the input signals on the Major OptiX OSN
PDH side of the E3/T3 tributary board. 550/580
P_LOS Indicates loss of signal on the PDH side Major OptiX OSN
of the E3/T3 tributary board in the 550/580
receive direction.
PASSWORD_ Indicates that the default user's default Major OptiX OSN
NEED_CHAN password is not changed. 550/500/580
GE
PATCH_CHGS Indicates that the versions of patch Major OptiX OSN
CC_NOTMAT packages on service boards are different 550/500/580
CH from the version of the patch package on
the SCC board after the SCC board is
replaced.
PATCH_BD_E Indicates that a board is isolated because Major OptiX OSN
XCLUDE a patch package cannot be installed on it. 550/500/580
PATCH_BD_ Indicates that a patch package fails to be Major OptiX OSN
MATCH_FAIL installed on a board. 550/500/580
PATCH_MAT Indicates that the system control board Minor OptiX OSN
CH_NO_STA does not initiate board patch matching. 550/500/580
RT
PATCH_PKGE Indicates that the patch package file is Minor OptiX OSN
RR abnormal. 550/500/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 61
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
PATCH_OP_T Indicates that a patch package operation Minor OptiX OSN
IMEOUT times out. 550/500/580
PATCH_INIT_ Indicates that patch initialization fails. Major OptiX OSN
FAIL 550/500/580
PCM_64KSNC Indicates that 64K subnetwork Major OptiX OSN
P_UNAVAIL connection protection (SNCP) is 550
unavailable.
PCM_DATA_ Indicates a data conflict of multiplexer Major OptiX OSN
CONFLICT group members. 550/580
PING_ARP_M Indicates that the dynamic ARP and static Minor OptiX OSN
ISMATCH ARP conflict in the ping operation. 580/550/500
PING_LOS Indicates that IP Ping fails. Minor OptiX OSN
580/550/500
PORT_EXC_T Indicating that the traffic over an Ethernet Major OptiX OSN
RAFFIC port exceeds its threshold. 550/500/580
PORT_MODU Indicates that the optical module on an Major OptiX OSN
LE_OFFLINE optical port is offline. 550/580
PORTMODE_ Indicates that the working mode of the Minor OptiX OSN
MISMATCH opposite FE port does not match with that 550/500/580
of the local FE port.
POWER_ABN Indicates that the power supply is Major OptiX OSN
ORMAL abnormal. 550/500
POWER_FAIL Indicates a power supply failure on an Major OptiX OSN
NE. 550/500/580
POWER_MO Indicates that a power module is offline. Major OptiX OSN
DULE_OFFLI 550
NE
PRO_PKT_FL Indicates the NE is under a flooding Major OptiX OSN
OODING attack of protocol packets. 550/500/580
PPP_LCP_FAI Indicates a Link Control Protocol (LCP) Major OptiX OSN
L negotiation failure. 550/500
PPP_NCP_FAI Indicates a Network Control Protocol Major OptiX OSN
L (NCP) negotiation failure. 550/500
PRBS_LSS Indicates loss of the pseudo-random Minor OptiX OSN
binary sequence (PRBS) signal. 580
PTP_ATTR_M Indicates the Precision Time Protocol Minor OptiX OSN
ISMATCH (PTP) port attributes are inconsistent at 580
both ends.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 62
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
PTP_DECRYP Indicates that packets returned on an Major OptiX OSN
TION_FAIL IEEE 1588 ring network fail to be 580
decrypted.
PTP_DELAY_ Indicates that Delay_Resp packets are Major OptiX OSN
RESP_LOS lost. 580
PTP_PDELAY Indicates that Pdelay_Resp packets are Major OptiX OSN
_RESP_LOS lost. 580
PTP_SYNC_L Indicates that SYNC packets are lost. Major OptiX OSN
OS 580
PTP_SOURCE Indicating that the PTP clock source is Minor OptiX OSN
_SWITCH switched. 550
PTP_TIMEST Indicating an abnormality of the PTP Major OptiX OSN
AMP_ABN timestamp. 550/580
PTPSRV_LCS Indicating that the service license for the Warning OptiX OSN
_INVALID PTP clock is invalid. 550
PUM_BCM_A Working current of pump laser over Major OptiX OSN
LM threshold 550/580
PUM_TEM_A The operating temperature of the pump Major OptiX OSN
LM laser exceeds the threshold 550/580
PUMP_COOL Cooling current of pump laser over Critical OptiX OSN
_EXC threshold 550/580
PW_NO_TRA Indicates that a PW does not receive or Critical OptiX OSN
FFIC transmit any traffic. 550/500
PW_APS_DE Indicates that a PW APS protection group Major OptiX OSN
GRADED degrades. 550/500/580
PW_APS_OU Indicates that a PW APS protection group Major OptiX OSN
TAGE fails. 550/500/580
PWAPS_LOST Indicates that the APS frames are lost. Minor OptiX OSN
550/500/580
PWAPS_PATH Indicates that the local NE and the Major OptiX OSN
_MISMATCH opposite NE are configured with different 550/500/580
working and protection paths of the PW
APS protection group.
PWAPS_SWIT Indicates a switching failure in the PW Minor OptiX OSN
CH_FAIL APS protection group. 550/500/580
PWAPS_TYPE Indicates that the local NE and the Major OptiX OSN
_MISMATCH opposite NE are configured with different 550/500/580
PW protection types.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 63
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
PWD_ENCRY The user password encryption mode of an Major OptiX OSN
PT_RISK NE has security risks. 550/500/580
PWR_MAJ_A Power supply overvoltage or Critical OptiX OSN
LM undervoltage. 550
PWR_TEMP_ Indicates that the temperature of the Critical OptiX OSN
OVERTH power module crosses the specified 550/500
threshold.
4.1.16 Alarm List R
This section used a table to list the alarms starting with R.
Name Description Severity Applicable
Equipment
R_APS Indicates that the line board failed to receive Minor OptiX OSN
the K1/K2 byte. 550/580
R_LOC Indicates loss of the clock in the signals Critical OptiX OSN
received by the line board at the optical port. 550/580
R_LOF Indicates loss of frame in the signals received Critical OptiX OSN
by the line board at the optical port. 550/580
R_LOS Indicates loss of signal at the receive optical Critical OptiX OSN
port on the line board. 550/580
R_OOF Indicates that the frame header cannot be Critical OptiX OSN
identified for five consecutive frames in the 550/580
received signals of the line board.
R_S_ERR Indicates that the received signal has errors. Critical OptiX OSN
550/580
RELAY_A Indicates critical alarm inputs. Critical OptiX OSN
LARM_C 550/500/580
RITICAL
RELAY_A Indicates warning alarm inputs. Warning OptiX OSN
LARM_IG 550/500/580
NORE
RELAY_A Indicates major alarm inputs. Major OptiX OSN
LARM_M 550/500/580
AJOR
RELAY_A Indicates minor alarm inputs. Minor OptiX OSN
LARM_M 550/500/580
INOR
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 64
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
RELAY_L Indicates that the receiving frames of the dry Major OptiX OSN
OF contact signal transmission are lost. 550/580
RFA Indicates that the framing E1/T1 frame Minor OptiX OSN
notification event occurs. 550/580
RMFA Indicates that the framing E1/T1 multiframe Minor OptiX OSN
notification event occurs. 550/580
RS_CROS Indicates that the regenerator section Minor OptiX OSN
STR performance of the line board crosses the 550/580
threshold.
RTC_FAI Indicates a real-time clock (RTC) failure on Major OptiX OSN
L the system control, switching, and timing 550/500/580
board.
RTS Indicates that the Request To Send status of Major OptiX OSN
the DCE is abnormal. 550/580
4.1.17 Alarm List S
This section used a table to list the alarms starting with S.
Name Description Severity Applicable
Equipment
S1_SYN_CH Indicates that the clock reference Major OptiX OSN
ANGE source of the clock board is 550/500/580
switched in the S1 byte mode.
SEC_RADIU Indicates that the number of Major OptiX OSN
S_FAIL consecutive RADIUS 550/500/580
authentication failures is too great.
SECU_ALM Indicates that the SCC reports an Major OptiX OSN
illegal login. 550/500/580
SERVICE_C Indicates that the capacity of the Major OptiX OSN
APACITY_E services configured for a 580
XCEED_LIC equipment exceeds the limit
ENSE defined by the license.
SERVICE_T Indicates that the service type Major OptiX OSN
YPE_EXCEE exceeds the license limit. 580
D_LICENSE
SLAVE_WO Indicates that the protection board Warning OptiX OSN
RKING is working. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 65
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
SOFTWARE Indicates that the board software is Major OptiX OSN
_UNCOMMI unauthorized. 550/500
T
SRV_LOOP_ Indicates that an Ethernet service Major OptiX OSN
LD loop occurs. 550/500/580
SRV_SHUTD Indicates that the Ethernet private Major OptiX OSN
OWN_LD service is stopped. 550/500/580
SSL_CERT_ Indicates that the Secure Sockets Critical OptiX OSN
DAMAGED Layer (SSL) certificate file is 550/500/580
damaged.
SSL_CERT_ Indicates that the Secure Sockets Major OptiX OSN
NOENC Layer (SSL) certificate file is not 550/500/580
encrypted.
SSL_CERT_ Indicates that the Secure Sockets Critical OptiX OSN
TO_EXPIRE Layer (SSL) certificate file is 550/500/580
about to expire.
SSM_LOS Indicates that the SSM quality Minor OptiX OSN
information fails to be received. 580
SSM_QL_FA Indicates that the received SSM Minor OptiX OSN
ILED quality is worse than the threshold. 580
STORM_CU Indicates that the number of Minor OptiX OSN
R_QUENUM current alarms on the NE reaches 550/500/580
_OVER the value that is equal to the
maximum number of alarms
supported by an alarm queue
minus one.
SUBNET_RT Indicates that subnets conflict on a Minor OptiX OSN
_CONFLICT data communication network 550/500/580
(DCN).
SUBRATE_P Indicates a rate mismatch of a sub- Major OptiX OSN
ROTOCOL_ rate protocol serial port. 550/580
MM
SUM_INPW Indicates that the input optical Major OptiX OSN
R_HI power is excessively high. 550/580
SUM_INPW Indicates that the total input Major OptiX OSN
R_LOW optical power is excessively low. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 66
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
SWDL_ACTI Indicates that during software Critical OptiX OSN
VATED_TIM package loading, the NE does not 550/500/580
EOUT perform the commit operation in a
certain time after the board is
activated.
SWDL_AUT Indicates that the automatic match Minor OptiX OSN
OMATCH_I function is disabled. 550/500/580
NH
SWDL_BD_ Indicates that a board is excluded Major OptiX OSN
EXCLUDE from software download during 580
software package downloading.
SWDL_BD_ Indicates a board software Minor OptiX OSN
MATCH_FAI matching failure. 550/500/580
L
SWDL_BD_ Indicates weak mapping during an Minor OptiX OSN
WEAKMAT upgrade by means of package 580
CH loading.
SWDL_CHG Indicates that the NE software Critical OptiX OSN
MNG_NOM does not match the board software. 550/500/580
ATCH
SWDL_COM Indicates that the commission Minor OptiX OSN
MIT_FAIL operation on the NE fails. 550/500/580
SWDL_INPR Indicates that the NE is loading the Warning OptiX OSN
OCESS software package. 550/500/580
SWDL_NEP Indicates that software package Critical OptiX OSN
KGCHECK files are lost. 550/500/580
SWDL_PKG Indicates that certain board Minor OptiX OSN
_NOBDSOF software is missing from the 550/500/580
T software package.
SWDL_PKG Indicates that the software package Minor OptiX OSN
VER_MM version is inconsistent with the 550/500/580
software version specified in the
software package.
SWDL_ROL Indicates that some board rollback Minor OptiX OSN
LBACK_FAI fails when the NE performs 550/500/580
L rollback.
SYN_BAD Indicates that the current Minor OptiX OSN
synchronization clock source of 550/500/580
the clock board is degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 67
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
SYNC_C_LO Indicates that the clock source of Warning OptiX OSN
S the clock board that is set in the 550/500/580
clock source priority table is lost.
SYNC_CON Indicates that the clock source Minor OptiX OSN
FIG_ERR configurations of an NE are 580
incorrect.
SYNC_DISA Indicates that the automatic Minor OptiX OSN
BLE synchronization of SCC boards is 550/580
disabled.
SYNC_F_M_ Indicates the forced or manual Warning OptiX OSN
SWITCH switching state of a clock source. 580
SYNC_FAIL Indicates that the batch backup of Minor OptiX OSN
the databases of the active and 550/580
standby SCC boards fails.
SYNC_LOC Indicates that the clock source in Warning OptiX OSN
KOFF the priority list is locked. 580
SYSLOG_C Indicates that communication Major OptiX OSN
OMM_FAIL between the NE and the Syslog 550/500/580
server fails.
SYSPARA_C Indicates that the SCC data and the Minor OptiX OSN
FDB_NOSA CF card data are inconsistent. 580
ME
4.1.18 Alarm List T
This section used a table to list the alarms starting with T.
Name Description Severity Applicable
Equipment
T_ALOS Indicates loss of analog signals at the E1 or Major OptiX OSN
T1 ports. 550/500/580
T_FIFO_E Indicates that the transmit FIFO on the Minor OptiX OSN
PDH side of the E3/T3 tributary board 550/580
overflows.
T_LOC Indicates that the clock of the signal in the Major OptiX OSN
transmit direction of the line board is lost. 550/580
T_LOS Indicates that no signal is input on the Major OptiX OSN
transmit side of the line board. 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 68
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
T_LOSEX Indicates that the board detects the loss of Major OptiX OSN
backplane service bus signals. 550/580
TD Indicates that the laser transmit Critical OptiX OSN
performance deteriorates. 550/580
TEM_HA Indicates that the temperature of the laser Major OptiX OSN
exceeds the upper threshold. 550/500/580
TEM_LA Indicates that the temperature of the laser Major OptiX OSN
exceeds the lower threshold. 550/500/580
TEMP_AL Indicates that the temperature crosses the Minor OptiX OSN
ARM threshold. 550/500/580
TEMP_OV Indicates that the operating temperature of Major OptiX OSN
ER the alarmed board is higher than the upper 550/500/580
threshold or lower than the lower
threshold.
TF Indicates a transmission failure of a laser. Critical OptiX OSN
550/500/580
THUNDER Indicates a lightning protection failure. Minor OptiX OSN
ALM 550/500/580
TIME_LOC Indicating a failure to lock the clock. Major OptiX OSN
K_FAIL 550/580
TIME_NO_ Indicating that the IEEE 1588v2 time goes Minor OptiX OSN
TRACE_M into no-trace mode. 550
ODE
TR_LOC Indicates that the clock of the cross- Major OptiX OSN
connect board is faulty. 550/500/580
TPS_ALM An alarm of TPS protection switching. Major OptiX OSN
550/580
TU_AIS TU alarm indication signal. Major OptiX OSN
550/580
TU_AIS_V VC-12 TU alarm indication signal. Major OptiX OSN
C12 550/580
TU_AIS_V VC-3 TU alarm indication signal. Major OptiX OSN
C3 550/580
TU_LOP TU loss of pointer. Major OptiX OSN
550/580
TU_LOP_V VC-12 TU loss of pointer. Major OptiX OSN
C12 550/580
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 69
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicable
Equipment
TU_LOP_V VC-3 TU loss of pointer. Major OptiX OSN
C3 550/580
TUNNEL_ Indicates that a tunnel APS protection Major OptiX OSN
APS_DEGR group degrades. 550/500/580
ADED
TUNNEL_ Indicates that a tunnel APS protection Major OptiX OSN
APS_OUTA group fails. 550/500/580
GE
4.1.19 Alarm List U
This section used a table to list the alarms starting with U.
Name Description Severity Applicabl
e
Equipmen
t
UHCS Indicates uncorrectable cell errors. Minor OptiX OSN
550/500/58
0
UP_E1_ Indicates an alarm in upstream E1 signals. Minor OptiX OSN
AIS 550/500/58
0
UP_T1 Indicates upstream 1.5 Mbit/s signals. Minor OptiX OSN
AIS 550/580
4.1.20 Alarm List V
This section used a table to list the alarms starting with V.
Name Description Severity Applicab
le
Equipme
nt
V5_VC Indicates that bits 5-7 of the V5 byte in the lower Major OptiX
AIS order VC-12 path are all "1"s. OSN
550/500/5
80
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 70
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicab
le
Equipme
nt
VC_AIS Indicates a virtual channel (VC) connection Critical OptiX
alarm. OSN
550/500
VC_LO Indicates loss of connectivity on the VC. Major OptiX
C OSN
550/500
VCAT_ Indicating that the virtual concatenation time Critical OptiX
LOA delay crosses the threshold. OSN
550/580
VCAT_ Indicates that multiframe of the VC-12 virtual Major OptiX
LOM_V concatenation is lost. OSN
C12 550/580
VCAT_ Indicates multiframe of the VC-3 virtual Major OptiX
LOM_V concatenation is lost. OSN
C3 550/580
VCAT_ Indicates that multiframe of the VC-4 virtual Major OptiX
LOM_V concatenation is lost. OSN
C4 550/580
VCAT_ Indicates SQ mismatch of the VC-12 virtual Major OptiX
SQM_V concatenation. OSN
C12 550/580
VCAT_ Indicates SQ mismatch of the VC-3 virtual Major OptiX
SQM_V concatenation. OSN
C3 550/580
VCAT_ Indicates that the sequence numbers of the Major OptiX
SQM_V members in the VC-4 virtual concatenation do OSN
C4 not match each other. 550/580
VC_RD Indicates a remote defect in the VC connection. Major OptiX
I OSN
550/500
VCTRU Indicating that the VCTRUNK port has no Major OptiX
NK_NO traffic. OSN
_FLOW 550/580
VP_AIS Indicates an alarm in the virtual channel (VP) Critical OptiX
connection. OSN
550/500
VP_LO Indicates loss of connectivity on the VP. Major OptiX
C OSN
550/500
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 71
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Description Severity Applicab
le
Equipme
nt
VP_RDI Indicates a remote defect in the VP connection. Major OptiX
OSN
550/500
4.1.21 Alarm List W
This section used a table to list the alarms starting with W.
Name Description Severity Applicabl
e
Equipmen
t
W_OFF Indicates that an ejector lever cannot be Minor OptiX OSN
LINE detected. 580
W_R_F Indicating that reading and writing the chip Major OptiX OSN
AIL register fail. 550
WAVED Indicates a wavelength or band mismatch. Major OptiX OSN
ATA_M 580
IS
WRG_B Indicates an incorrect board type. Major OptiX OSN
D_TYP 550/500/58
E 0
4.2 Alarm Clearing
This section describes how to clear alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 72
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 through a
board are not configured with protection, exercise caution when performing the preceding
operations.
l Before replacing a live line board, ensure that the optical port level and transmission
distance on the line board to substitute for the live line board are the same as the values of
the old board and its board software is not earlier than that on the live line board.
l Replacing a chassis will result in service interruption on the NE, and therefore is a risky
operation.
l Before replacing a chassis, ensure that the optical port level and transmission distance on
the line board are the same as those on the live line board and that the board software
versions of the NE are not earlier than the live board software versions. For the NE
software versions, see the Release Notes and Upgrade Guide.
NOTE
l The SCC, cross-connect and timing units of the OptiX OSN 550 are integrated in the PCX board.
l The SCC, cross-connect and timing units of the OptiX OSN 500 are integrated in the CSHD board.
l The SCC, cross-connect and timing units of the OptiX OSN 580 are integrated in the UCX board.
l This document lists the alarm parameters that are displayed on the U2000. To browse parameters of
an alarm on the U2000, select this alarm. Then, the alarm parameters are displayed in Alarm Details
in the following format: Alarm Parameters (hex): parameter 1 parameter 2...parameter N, for
example, Alarm Parameters (hex): 0x01 0x08.
l If you fail to clear the alarms by using these methods described in this document, contact Huawei
technical support engineers for a solution.
4.2.1 A_LOC
Description
The A_LOC alarm indicates that the upstream bus clock at the electrical port of a tributary
board is lost.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
Services on the board where the alarm is generated are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 73
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The interconnected PDH equipment is incorrectly configured or is faulty.
l The service type is incorrectly configured.
l The service cross-connections are incorrectly configured.
l The board hardware is faulty.
l The cross-connect and timing units are faulty.
Procedure
Step 1 Check whether the interconnected PDH equipment is incorrectly configured or is faulty.
If... Then...
The interconnected PDH equipment is Configure the PDH equipment correctly.
incorrectly configured Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The interconnected PDH equipment is Troubleshoot the PDH equipment. Then,
faulty check whether the alarm is cleared. If the
alarm persists, go to the next step.
The interconnected PDH equipment is Go to the next step.
operating properly
Step 2 Check whether the service type is incorrectly configured at the local end.
If... Then...
The service type is incorrectly configured Configure the service type correctly. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The service type is correctly configured Go to the next step.
Step 3 Check whether the service cross-connections are incorrectly configured at the local end.
If... Then...
The service cross-connections are Configure the service cross-connection
incorrectly configured correctly. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The service cross-connections are correctly Go to the next step.
configured
Step 4 Check whether the service cross-connections are incorrectly configured at the opposite end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 74
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The service cross-connections are Configure the service cross-connection
incorrectly configured correctly. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The service cross-connections are correctly Go to the next step.
configured
Step 5 Check whether the tributary board is faulty.
If... Then...
The tributary board is faulty Replace the faulty board. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The tributary board is functioning properly Go to the next step.
Step 6 Check whether the cross-connect and timing units are faulty.
If... Then...
The cross-connect and timing units are Replace the system control, cross-connect,
faulty and timing board.
The cross-connect and timing units are Contact Huawei technical support engineers
functioning properly to handle the alarm.
----End
Related Information
None.
4.2.2 ACR_LOCK_FAIL
Description
The ACR_LOCK_FAIL is an alarm indicating a failure to lock the IEEE 1588 ACR. This
alarm is reported when the NE works in IEEE 1588 ACR mode and the clock fails to be
locked.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 75
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The phase-locked loop (PLL) is in holdover or free-run mode.
l 0x02: The Sync timestamp remains unchanged when the Precision Time
Protocol (PTP) clock is synchronized.
l 0x03: The phase discrimination value per unit of time exceeds the upper
threshold.
l 0x04: The IEEE 1588 ACR algorithm is in the quick lockout phrase when
the clocks are synchronized by means of IEEE 1588 ACR.
Impact on the System
When this alarm occurs, services may happen to pointer justifications or bit errors.
Possible Causes
The possible causes of the ACR_LOCK_FAIL alarm are as follows:
l Cause 1: The IEEE 1588 ACR algorithm is in the quick lockout phrase when the clocks
are synchronized by means of IEEE 1588 ACR.
l Cause 2: A fault occurs on the main control board of the NE or its upstream NE or the
clock interface board.
l Cause 3: The third-party packet delay variation (PDV) that clocks traverse is overlarge.
Procedure
Step 1 Cause 1: The IEEE 1588 ACR algorithm is in the quick lockout phrase when the clocks are
synchronized by means of IEEE 1588 ACR.
1. If the value of the parameter is 0x04, you do not need to handle the alarm. About 15
minutes later, check whether the alarm is cleared.
2. If the alarm persists, go to Step 2.
Step 2 Cause 2: A fault occurs on the main control board of the NE or its upstream NE or the clock
interface board.
1. Check whether alarms related to hardware, such as 4.2.157 HARD_BAD, are reported
by the main control board of the NE or its upstream NE or the clock interface board. If
yes, clear these alarms first.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The third-party packet delay variation (PDV) that clocks traverse is overlarge.
1. Check whether the PDV of the NE is overlarge by performance event
CURPOSITIVEPDV. If yes, optimize the PDV of the third-party network.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 76
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Then, check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.3 AD_CHECK_FAIL
Description
The AD_CHECK_FAIL alarm indicates an AD (analog-to-digital converter) self-check
failure. This alarm is reported when the AD chip on the board is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.
Impact on the System
l This alarm may affect services.
l Parameters relevant to the AD chip on the board, such as board input/output optical
power, fail to be queried on the NMS. As a result, maintenance engineers can neither
obtain the current network performance data nor find in time any potential network
issues. Service interruption or system faults may occur.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Query the AD_CHECK_FAIL alarm on the NMS and determine the board that reports the
alarm. For details, see Viewing the Current Alarms in the Supporting Tasks.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 77
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Replace the board that reports the AD_CHECK_FAIL alarm.
----End
Related Information
None
4.2.4 ALM_ALS
Description
The ALM_ALS alarm indicates that the laser on a line board is in the auto laser shutdown
(ALS) state.
If the ALM_ALS alarm is generated, the R_LOS alarm has been generated at the optical port
of the line board. To prevent damage to the laser, the laser enters the ALS state. After the
R_LOS alarm is cleared, the laser automatically exits the ALS state.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Impact on the System
The ALM_ALS alarm does not have any impact on the system.
Possible Causes
The possible cause of this alarm is as follows:
The ALS function is enabled for the optical port, and the R_LOS alarm is generated at the
optical port. As a result, the laser enters the ALS state and reports the ALM_ALS alarm.
Procedure
Step 1 Check whether the line board reports the R_LOS alarm. If the line board reports the R_LOS
alarm, clear the alarm. Then, check whether the ALM_ALS alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 78
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Disable the ALS function for the optical port on the line board. Then, check whether the
ALM_AIS alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
R_LOS
4.2.5 ALM_E1RAI
Description
The ALM_E1RAI is an alarm indication at the remote end of an E1 link.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
This alarm is reported when the local service in the downstream direction is unavailable.
Possible Causes
Possible causes of the ALM_E1RAI alarm are as follows:
The T_ALOS, LFA, LMFA, DOWN_E1_AIS, or UP_E1_AIS alarm is reported at the
opposite end of the E1 link. The NE at the local end receives the ALM_E1RAI alarm that is
inserted in the downstream by the NE at the opposite end.
Procedure
Step 1 Check whether the T_ALOS, LFA, LMFA, DOWN_E1_AIS, or UP_E1_AIS alarm is
reported at the opposite end of the E1 link.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 79
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The T_ALOS, LFA, LMFA, UP_E1_AIS, Clear the alarm and check whether the
or DOWN_E1_AIS alarm is reported ALM_E1RAI alarm is cleared. If the
ALM_E1RAI alarm persists, go to the next
step.
The T_ALOS, LFA, LMFA, UP_E1_AIS, Go to the next step.
and DOWN_E1_AIS alarm are not reported
Step 2 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
T_ALOS, LFA, LMFA, UP_E1_AIS, DOWN_E1_AIS
4.2.6 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating the loss of GFP client signal. When the source
end cannot receive the client signal, it sends the management frame to the sink end. When the
sink end receives the management frame, the ALM_GFP_dCSF alarm is reported.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The ID of the logical port, and the value is always 0x01.
Parameter 2, parameter 3 Indicate the VCTRUNK number where the alarm occurs.
Impact on the System
During data transmission, the source end cannot receive the client signal. The services lose
packets or are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 80
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible causes of the ALM_GFP_dCSF alarm are as follows:
l Cause 1: The interface module at the source end is incorrect. For example, the interface
is faulty, or the board is faulty.
Figure 4-1 ALM_GFP_dCSF alarm detection 1
Direction of the Signal
Failed to receive signals due to Transmission of ALM_GFP_dCSF
the incorrect interface module management frames
Inter- X X Inter-
E L SDH L E
connected Ethernet C C Ethernet connected
U U network U U
equipment network S S network equipment
NE1 (Source end) NE2 (Sink end)
LU: Line unit
EU: Ethernet unit
XCS: Cross-connect unit
l Cause 2: The board that reports the alarm is faulty.
Figure 4-2 ALM_GFP_dCSF alarm detection 2
Direction of the Signal
ALM_GFP_dCSF
Inter- X X
E L SDH L E Inter-
connected Ethernet C C Ethernet
U U network U U connected
equipment network S S network
equipment
NE1 (Source end) NE2 (Sink end)
LU: Line unit
EU: Ethernet unit
XCS: Cross-connect unit
Procedure
Step 1 Cause 1: The interface module at the source end is incorrect. For example, the interface is
faulty, or the board is faulty.
1. As shown in Figure 4-1, check whether the interface module at the source end works
normally.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 81
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
A board at the source end reports an Clear the alarm immediately. Check
alarm (such as ETH_LOS alarm) whether the ALM_GFP_dCSF alarm is
associated with an ethernet port cleared. If the alarm persists, go to the
next step.
No alarm is reported Go to the next step.
2. Replace the corresponding board at the source end.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The board that reports the alarm is faulty.
1. Replace the board that reports the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.7 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The ID of the logical port, and the value is always 0x01.
Parameter 2, parameter 3 Indicate the VCTRUNK number where the alarm occurs.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 82
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
During data transmission, if the board fails to align the GFP frame, the services are
interrupted.
Possible Causes
The possible causes of the ALM_GFP_dLFD alarm are as follows:
l Cause 1: The settings of timeslots and other parameters of the VCTRUNKs at both ends
are inconsistent.
l Cause 2: The performance of the service transmission line degrades.
l Cause 3: A certain board is faulty.
Procedure
Step 1 Cause 1: The settings of timeslots and other parameters of the VCTRUNKs at both ends are
inconsistent.
1. Check whether the number of uplink (or downlink) timeslots bound with the VCTRUNK
at the local end is consistent with the number of downlink (or uplink) timeslots bound
with the VCTRUNK at the opposite end.
If... Then...
The number of timeslots at the local Increase or decrease Number of Bound
end is inconsistent with the number of Paths as required to ensure the
corresponding timeslots at the opposite consistency. Check whether the alarm is
end cleared. If the alarm persists, go to the
next step.
The number of timeslots at the local Go to the next step.
end is consistent with the number of
corresponding timeslots at the opposite
end
2. Select the relevant NE. Choose Configuration > SDH Service Configuration from the
Function Tree.
3. Check whether the number of timeslots bound with the VCTRUNK is consistent with the
settings of the cross-connections.
If... Then...
The number of timeslots bound with Reset the number of timeslots bound with
the VCTRUNK is inconsistent with the the VCTRUNK or cross-connections.
settings of the cross-connections Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The number of timeslots bound with Go to the next step.
the VCTRUNK is consistent with the
settings of the cross-connections
4. Check whether the service levels of the SDH cross-connections are the same at both
ends. If the service level of the SDH cross-connections at the local end is VC-12 and the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 83
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
service level of the SDH cross-connections at the opposite end is VC-4, the
ALM_GFP_dLFD alarm is reported. Thus, you need to reconfigure the cross-connect
service level in the case of the inconsistency.
5. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The performance of the service transmission line degrades.
1. The performance of the transmission line degrades if the fiber connector is loose or dirty,
the fiber or cable is faulty, or the components for the transmission are not in good
contact. Check whether the alarms related to errors and optical power and the
performance events related to errors occur in the service transmission line.
If... Then...
The BIP_EXC, BIP_SD, B3_EXC, Take priority to clear the preceding
B3_SD, HPBBE, LPBBE, or alarms or performance events. Check
IN_PWR_ABN occurs whether the alarm is cleared. If the alarm
persists, go to Step 3.
The preceding alarms or performance Go to Step 3.
events do not occur
Step 3 Cause 3: A certain board is faulty.
1. Replace the board directly.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.8 ALM_IMA_LIF
Description
The ALM_IMA_LIF alarm indicates that the local end of an IMA link fails to delimit
received IMA frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 84
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1, Parameter 2 ATM trunk ID.
Impact on the System
When the ALM_IMA_LIF alarm is reported, the alarmed IMA link is unavailable and the
number of available links in the IMA group decreases. If the service bandwidth configured for
the IMA group is higher than that provided by the available E1 links in the IMA group,
services over the IMA port are congested. Consequently, user cells are lost.
After the ALM_IMA_LIF alarm is cleared, the alarmed IMA link becomes available.
Possible Causes
Possible causes of the ALM_IMA_LIF alarm are as follows:
l The physical path that carries the alarmed IMA link reports SDH alarms, such as
R_LOS, R_LOF, and MS_AIS.
NOTE
The cause is only for OSN 550.
l The IMA protocol configuration at one end of the alarmed IMA link is different from
that at the other end.
l A VC-12 path on the alarmed IMA link is damaged.
l The alarmed IMA link is faulty.
Procedure
Step 1 Check whether SDH alarms are generated in the physical path that carries the alarmed IMA
link, such as R_LOS, R_LOF, and MS_AIS.
If... Then...
Any SDH alarms are generated Clear these SDH alarms and check whether
the ALM_IMA_LIF alarm is cleared. If the
ALM_IMA_LIF alarm persists, go to the
next step.
No SDH alarm is generated Go to the next step.
Step 2 On the U2000, check whether the IMA protocol configuration at one end of the alarmed IMA
link is different from that at the other end.
If... Then...
The IMA protocol configurations are Change the IMA protocol configurations to
different between both ends the same at both ends and check whether the
ALM_IMA_LIF alarm is cleared. If the
ALM_IMA_LIF alarm persists, go to the
next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 85
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The IMA protocol configuration at both Go to the next step.
ends is the same
Step 3 On the U2000, check whether the cross-connections configured for the alarmed IMA link are
correct.
If... Then...
The cross-connections are incorrect Rectify the cross-connections and ensure
that the physical path carrying the IMA link
is normal. Check whether the
ALM_IMA_LIF alarm is cleared. If the
ALM_IMA_LIF alarm persists, go to the
next step.
The cross-connections are correct Go to the next step.
Step 4 Check whether the fibers or cables are correctly connected to the ports on the local NE and
opposite NE.
If... Then...
A fiber/cable connection is incorrect Rectify the connection. Check whether the
ALM_IMA_LIF alarm is cleared. If the
ALM_IMA_LIF alarm persists, go to the
next step.
All fiber/cable connections are correct Go to the next step.
Step 5 Check whether fibers or cables connected to the ports of the local NE and opposite NE are
faulty.
If... Then...
Fibers or cables are incorrect Replace the faulty fibers or cables. Check
whether the ALM_IMA_LIF alarm is
cleared. If the ALM_IMA_LIF alarm
persists, go to the next step.
All fibers or cables are correct Go to the next step.
Step 6 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 86
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.9 ALM_IMA_LODS
Description
The ALM_IMA_LODS alarm indicates that the maximum differential delay between the
receive links in the local IMA group is longer than the threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 ATM trunk ID.
Impact on the System
When the ALM_IMA_LIF alarm is reported, the alarmed IMA link is unavailable and the
number of available links in the IMA group decreases. If the service bandwidth configured for
the IMA group is higher than that provided by the available E1 links in the IMA group,
services over the IMA port are congested. Consequently, user cells are lost.
After the ALM_IMA_LIF alarm is cleared, the alarmed IMA link becomes available.
Possible Causes
Possible causes of the ALM_IMA_LODS alarm are as follows:
l The physical path that carries the alarmed IMA link reports SDH alarms, such as
R_LOS, R_LOF, and MS_AIS.
NOTE
The cause is only for OSN 550.
l The IMA protocol configuration at one end of the alarmed IMA link is different from
that at the other end.
l A VC-12 path on the alarmed IMA link is damaged.
l The alarmed IMA link is faulty.
Procedure
Step 1 Check whether SDH alarms are generated in the physical path that carries the alarmed IMA
link, such as R_LOS, R_LOF, and MS_AIS.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 87
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Any SDH alarms are generated Clear these SDH alarms and check whether
the ALM_IMA_LODS alarm is cleared. If
the ALM_IMA_LODS alarm persists, go to
the next step.
No SDH alarm is generated Go to the next step.
Step 2 On the U2000, check whether the IMA protocol configuration at one end of the alarmed IMA
link is different from that at the other end.
If... Then...
The IMA protocol configurations at both Change the IMA protocol configurations to
ends differs the same at both ends and check whether the
ALM_IMA_LODS alarm is cleared. If the
ALM_IMA_LODS alarm persists, go to the
next step.
The IMA protocol configuration at both Go to the next step.
ends is the same
Step 3 On the U2000, check whether the cross-connections configured for the alarmed IMA link are
correct.
If... Then...
The cross-connections are incorrect Rectify the cross-connections and ensure
that the physical path carrying the IMA link
is normal. Check whether the
ALM_IMA_LODS alarm is cleared. If the
ALM_IMA_LODS alarm persists, go to the
next step.
The cross-connections are correct Go to the next step.
Step 4 Check whether the fibers or cables are correctly connected to the ports on the local NE and
opposite NE.
If... Then...
A fiber/cable connection is incorrect Rectify the connection. Check whether the
ALM_IMA_LODS alarm is cleared. If the
ALM_IMA_LODS alarm persists, go to the
next step.
All fiber/cable connections are correct Go to the next step.
Step 5 Check whether fibers or cables connected to the ports of the local NE and opposite NE are
faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 88
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Fibers or cables are incorrect Replace the faulty fibers or cables. Check
whether the ALM_IMA_LODS alarm is
cleared. If the ALM_IMA_LODS alarm
persists, go to the next step.
All fibers or cables are correct Go to the next step.
Step 6 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
Differential Delay
Differential delay indicates the delay difference between the services among the E1 links. A
delay buffer of 1024 cells is provided for each E1 link. The maximum differential delay is 256
ms.
Related Alarms
4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS
4.2.10 ALM_IMA_RE_RX_UNUSABLE
Description
The ALM_IMA_RE_RX_UNUSABLE alarm indicates that a remote IMA link fails to
receive signals and is unavailable.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 ATM trunk ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 89
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When the ALM_IMA_LIF alarm is reported, the alarmed IMA link is unavailable and the
number of available links in the IMA group decreases. If the service bandwidth configured for
the IMA group is higher than that provided by the available E1 links in the IMA group,
services over the IMA port are congested. Consequently, user cells are lost.
After the ALM_IMA_LIF alarm is cleared, the alarmed IMA link becomes available.
Possible Causes
Possible causes of the ALM_IMA_RE_RX_UNUSABLE alarm are as follows:
l The physical path that carries the alarmed IMA link reports SDH alarms, such as
R_LOS, R_LOF, and MS_AIS.
NOTE
The cause is only for OSN 550.
l The IMA protocol configuration at one end of the alarmed IMA link is different from
that at the other end.
l A VC-12 path on the alarmed IMA link is damaged.
l The alarmed IMA link is faulty.
Procedure
Step 1 Check for SDH alarms in the path that carries the alarmed IMA link, such as R_LOS, R_LOF,
and MS_AIS.
If... Then...
Any SDH alarms are reported Clear these alarms and check whether the
ALM_IMA_RE_RX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_RX_UNUSABLE alarm
persists, go to the next step.
No SDH alarm is reported Go to the next step.
Step 2 On the U2000, check whether the IMA protocol configuration differs at both ends of the
alarmed IMA link.
If... Then...
The IMA protocol configuration differs Change the IMA protocol configuration to
the same and check whether the
ALM_IMA_RE_RX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_RX_UNUSABLE alarm
persists, go to the next step.
The IMA protocol configuration is the same Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 90
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 On the U2000, check whether the cross-connections configured for the IMA link are correct.
If... Then...
The cross-connections are incorrect Rectify the cross-connections and ensure
that the path carrying the IMA link is
normal. Check whether the
ALM_IMA_RE_RX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_RX_UNUSABLE alarm
persists, go to the next step.
The cross-connections are correct Go to the next step.
Step 4 Check whether the fibers or cables are correctly connected to the ports of the local NE and
opposite NE.
If... Then...
A connection is incorrect Rectify the connection. Check whether the
ALM_IMA_RE_RX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_RX_UNUSABLE alarm
persists, go to the next step.
A connection is correct Go to the next step.
Step 5 Check whether fibers or cables connected to the ports of the local NE and opposite NE are
faulty.
If... Then...
The fibers or cables are incorrect Replace the faulty fibers or cables. Check
whether the
ALM_IMA_RE_RX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_RX_UNUSABLE alarm
persists, go to the next step.
The fibers or cables are correct Go to the next step.
Step 6 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 91
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.11 ALM_IMA_RE_TX_UNUSABLE
Description
The ALM_IMA_RE_TX_UNUSABLE alarm indicates that a remote IMA link fails to
transmit signals and is unavailable.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 ATM trunk ID.
Impact on the System
When the ALM_IMA_LIF alarm is reported, the alarmed IMA link is unavailable and the
number of available links in the IMA group decreases. If the service bandwidth configured for
the IMA group is higher than that provided by the available E1 links in the IMA group,
services over the IMA port are congested. Consequently, user cells are lost.
After the ALM_IMA_LIF alarm is cleared, the alarmed IMA link becomes available.
Possible Causes
Possible causes of the ALM_IMA_RE_TX_UNUSABLE alarm are as follows:
l The physical path that carries the alarmed IMA link reports SDH alarms, such as
R_LOS, R_LOF, and MS_AIS.
NOTE
The cause is only for OSN 550.
l The IMA protocol configuration at one end of the alarmed IMA link is different from
that at the other end.
l A VC-12 path on the alarmed IMA link is damaged.
l The alarmed IMA link is faulty.
Procedure
Step 1 Check for SDH alarms in the path that carries the alarmed IMA link, such as R_LOS, R_LOF,
and MS_AIS.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 92
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Any SDH alarms are reported Clear these alarms and check whether the
ALM_IMA_RE_TX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_TX_UNUSABLE alarm
persists, go to the next step.
No SDH alarm is reported Go to the next step.
Step 2 On the U2000, check whether the IMA protocol configuration differs at both ends of the
alarmed IMA link.
If... Then...
The IMA protocol configuration differs Change the IMA protocol configuration to
the same and check whether the
ALM_IMA_RE_TX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_TX_UNUSABLE alarm
persists, go to the next step.
The IMA protocol configuration is the same Go to the next step.
Step 3 On the U2000, check whether the cross-connections configured for the IMA link are correct.
If... Then...
The cross-connections are incorrect Rectify the cross-connections and ensure
that the path carrying the IMA link is
normal. Check whether the
ALM_IMA_RE_TX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_TX_UNUSABLE alarm
persists, go to the next step.
The cross-connections are correct Go to the next step.
Step 4 Check whether the fibers or cables are correctly connected to the ports of the local NE and
opposite NE.
If... Then...
A connection is incorrect Rectify the connection. Check whether the
ALM_IMA_RE_TX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_TX_UNUSABLE alarm
persists, go to the next step.
A connection is correct Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 93
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 5 Check whether fibers or cables connected to the ports of the local NE and opposite NE are
faulty.
If... Then...
The fibers or cables are incorrect Replace the faulty fibers or cables. Check
whether the
ALM_IMA_RE_TX_UNUSABLE alarm is
cleared. If the
ALM_IMA_RE_TX_UNUSABLE alarm
persists, go to the next step.
The fibers or cables are correct Go to the next step.
Step 6 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS
4.2.12 ALM_IMA_RFI
Description
The ALM_IMA_RFI alarm indicates that a remote IMA link fails to delimit received IMA
frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 ATM trunk ID.
Impact on the System
When the ALM_IMA_LIF alarm is reported, the alarmed IMA link is unavailable and the
number of available links in the IMA group decreases. If the service bandwidth configured for
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 94
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
the IMA group is higher than that provided by the available E1 links in the IMA group,
services over the IMA port are congested. Consequently, user cells are lost.
After the ALM_IMA_LIF alarm is cleared, the alarmed IMA link becomes available.
Possible Causes
Possible causes of the ALM_IMA_RFI alarm are as follows:
l The physical path that carries the alarmed IMA link reports SDH alarms, such as
R_LOS, R_LOF, and MS_AIS.
NOTE
The cause is only for OSN 550.
l The IMA protocol configuration at one end of the alarmed IMA link is different from
that at the other end.
l A VC-12 path on the alarmed IMA link is damaged.
l The alarmed IMA link is faulty.
Procedure
Step 1 Check for SDH alarms in the path that carries the alarmed IMA link, such as R_LOS, R_LOF,
and MS_AIS.
If... Then...
Any SDH alarms are reported Clear these alarms and check whether the
ALM_IMA_RFI alarm is cleared. If the
ALM_IMA_RFI alarm persists, go to the
next step.
No SDH alarm is reported Go to the next step.
Step 2 On the U2000, check whether the IMA protocol configuration differs at both ends of the
alarmed IMA link.
If... Then...
The IMA protocol configuration differs Change the IMA protocol configuration to
the same and check whether the
ALM_IMA_RFI alarm is cleared. If the
ALM_IMA_RFI alarm persists, go to the
next step.
The IMA protocol configuration is the same Go to the next step.
Step 3 On the U2000, check whether the cross-connections configured for the IMA link are correct.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 95
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The cross-connections are incorrect Rectify the cross-connections and ensure
that the path carrying the IMA link is
normal. Check whether the ALM_IMA_RFI
alarm is cleared. If the ALM_IMA_RFI
alarm persists, go to the next step.
The cross-connections are correct Go to the next step.
Step 4 Check whether the fibers or cables are correctly connected to the ports of the local NE and
opposite NE.
If... Then...
A connection is incorrect Rectify the connection. Check whether the
ALM_IMA_RFI alarm is cleared. If the
ALM_IMA_RFI alarm persists, go to the
next step.
A connection is correct Go to the next step.
Step 5 Check whether fibers or cables connected to the ports of the local NE and opposite NE are
faulty.
If... Then...
The fibers or cables are incorrect Replace the faulty fibers or cables. Check
whether the ALM_IMA_RFI alarm is
cleared. If the ALM_IMA_RFI alarm
persists, go to the next step.
The fibers or cables are correct Go to the next step.
Step 6 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS
4.2.13 APS_FAIL
Description
The APS_FAIL alarm indicates that the multiplex section protection (MSP) switching fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 96
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
Switching is unavailable for the services under protection, and the services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The MSP parameter configurations are incorrect.
l The MSP parameter configurations are lost.
Procedure
Step 1 Check whether the MSP parameter configurations of NEs are correct.
If... Then...
The MSP parameter configurations are Correct the MSP parameter configurations.
incorrect Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The MSP parameter configurations are Go to the next step.
correct
Step 2 Check whether the K byte pass-through and auto-reporting functions are working properly on
each NE. If the functions are not working properly on an NE, check the line board of the NE.
If... Then...
The line board is faulty Replace the related board.
The line board is functioning properly Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 97
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.14 APS_INDI
Description
The APS_INDI alarm indicates that the multiplex section protection (MSP) switching occurs.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The protected services are switched to the protection channel for transmission.
This alarm does not have any impact on services. However, if the protection channel also
fails, services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l An alarm that triggers MSP switching, such as R_LOS, R_LOF, MS_AIS, B2_EXC, or
B2_SD, is reported.
l The external switching command is issued.
l The attributes of the MSP group are incorrectly configured.
l The MSP protocol is abnormal.
l The system control unit is faulty.
Procedure
Step 1 Check whether the local or opposite NE reports an alarm that triggers MSP switching, such as
R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD. If an alarm that triggers MSP switching is
reported, clear this alarm first.
If... Then...
The R_LOS, R_LOF, MS_AIS, or Clear the R_LOS, R_LOF, MS_AIS, or
B2_EXC alarm is reported B2_EXC alarm. Then, check whether the
APS_INDI alarm is cleared. If the
APS_INDI alarm persists, go to the next
step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 98
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The B2_SD alarm is reported If signal degrade (SD) switching is enabled,
disable SD switching or clear the B2_SD
alarm. Then, check whether the APS_INDI
alarm is cleared. If the APS_INDI alarm
persists, go to the next step.
None of the preceding alarms are reported Go to the next step.
Step 2 Check whether the external switching command is issued.
If... Then...
The external switching command is issued Cancel the external switching command.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The external switching command is not Go to the next step.
issued
Step 3 Check whether the attributes of the MSP group are correctly configured.
If... Then...
The attributes of the MSP group are Apply the correct MSP group configuration.
incorrectly configured Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The attributes of the MSP group are Go to the next step.
correctly configured
Step 4 Enable the MSP protocol.
Enabling/Disabling the MSP protocol is dangerous and affects services.
Step 5 If the alarm persists, replace the system control, cross-connect, and timing board.
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
----End
Related Information
R_LOS, R_LOF, MS_AIS, B2_EXC, B2_SD
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 99
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.15 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP alarm indicates that the automatic multiplex section protection
(MSP) switching protocol is stopped manually.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Impact on the System
Protected services lose protection from MSP switching.
Possible Causes
The possible cause of this alarm is as follows:
The command for stopping the protection group protocol controller is manually issued.
Procedure
Step 1 Start the protection group protocol controller on the U2000. Then, check whether the alarm is
cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.16 ARP_FAIL
Description
The ARP_FAIL alarm indicates that an Ethernet port fails to learn the MAC address of the
remote end using the ARP.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 100
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 and 2 Indicate the VLAN ID of a VLAN subinterface. The parameters take
the fixed value of 0xFFFF for a non-VLAN sub-interface.
Parameters 3-6 Indicate the next-hop IP address.
Impact on the System
When this alarm occurs, services on the interface that reports the alarm are interrupted.
Possible Causes
A possible cause of the alarm is as follows:
l Cause 1: IP addresses of ports at both ends are not configured with IP addresses, or the
ports are not in the same network segment.
l Cause 2: Loop is performed for the link.
l Cause 3: Port has no traffic.
Procedure
Step 1 Cause 1: IP addresses of ports at both ends are not configured with IP addresses, or the ports
are not in the same network segment.
1. Check whether the interconnected ports at both ends are configured with IP addresses. If
no, configure IP addresses according to the network plan. For details, see Setting the
Layer 3 Attributes of Ethernet Ports of Configuration Guide (Packet Transport Domain).
2. Check whether IP addresses of the ports at both ends are in the same network segment. If
no, reconfigure IP addresses according to the network plan. For details, see Setting the
Layer 3 Attributes of Ethernet Ports of Configuration Guide (Packet Transport Domain).
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: Loop is performed for the link.
1. Check whether a software loopback (such as a PHY/MAC layer loopback) or hardware
loopback (such as loopback using network cables or optical fibers) is enabled at the
alarmed port. If yes, release the loopback. Check whether the alarm is cleared. For
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 101
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
details, see Setting the Advanced Attributes of Ethernet Ports of Configuration Guide
(Packet Transport Domain)
2. If the alarm persists, check whether there is switching equipment (such as a switch,
concentrator, or hub) between both ends. If there is switching equipment, check whether
a loopback is enabled on the switching equipment or a loopback occurs due to broadcast
on the switching equipment. Release the loopback and then check whether the alarm is
cleared.
3. If the alarm persists, check whether port MAC addresses at both ends are the same. If
they are the same, a loopback occurs. Release the loopback and then check whether the
alarm is cleared.
4. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Port has no traffic.
1. Check whether the alarmed port reports the ETH_NO_FLOW alarm. If yes, clear the
4.2.132 ETH_NO_FLOW alarm before first. Check whether the ARP_FAIL alarm is
cleared.
2. If the alarm persists, contact Huawei technical support engineers for handling the alarm.
----End
Related Information
None.
4.2.17 ARP_MAC_MISMATCH
Description
The ARP_MAC_MISMATCH alarm indicates that the Address Resolution Protocol (ARP)
static MAC address is different from the actual one.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Represent the IP index.
Impact on the System
When an ARP_MAC_MISMATCH alarm is generated, services are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 102
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The user-configured static ARP MAC address is different from the actual MAC address.
Procedure
Step 1 Reconfigure the static ARP MAC address to be same as the peer-end MAC address. For
details, see Configuring Address Resolution in the Configuration Guide (Packet Transport
Domain).
Step 2 Check whether the ARP_MAC_MISMATCH alarm clears. If the alarm persists, go to Step 3.
Step 3 Replace the peer-end board, ensuring that the MAC address of its port connecting to the local-
end board is the same as the static ARP MAC address configured at the local end.
Step 4 Check whether the alarm clears. If the alarm persists, contact Huawei engineers to handle the
alarm.
----End
Related Information
None.
4.2.18 ARP_SPOOF
Description
The ARP_SPOOF is an alarm indicating an ARP spoofing attack. The NE reports the alarm
when it is under an ARP spoofing attack.
Attribute
Alarm Severity Alarm Type
Major Security 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, parameter 2 Indicates the slot number.
Parameter 3 Indicates the subboard number (0xFF: no sub-board).
Parameter 4, parameter 5 Indicates the port number.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 103
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
If an ARP_SPOOF alarm is generated, the system impact from the associated fault could
include:
l A large number of CPU resources are occupied. As a result, the system is unstable and
the protocol status jitters.
l Normal ARP protocol packets are lost. As a result, ARP protocol entries are refreshed
and packet loss may occur.
Possible Causes
The possible causes of the ARP_SPOOF alarm include:
The number of gratuitous ARP packets and the number of ARP reply packets received per
minute exceed the thresholds for the same IP address in the ARP protocol entries. The MAC
address of the ARP packet is different from that of the current ARP protocol entry.
Procedure
Step 1 Check the ARP_SPOOF alarm on the NMS. Query the attacker list. For details, see
Configuring Address Resolution in the Configuration Guide (Packet Transport Domain).
Step 2 Find the host of the attacker based on the MAC address of the attacker. Disconnect the host
from the network to eliminate the attack source.
Step 3 Check whether the alarm is cleared. If it persists, contact Huawei engineers.
----End
Related Information
None.
4.2.19 ATMPW_UNKNOWNCELL_EXC
Description
The ATMPW_UNKNOWNCELL_EXC alarm indicates that the number of unknown ATM
cells exceeds the specified threshold within a certain period of time (2s by default). This
alarm is cleared when the number of unknown ATM cells is lower than the specified threshold
within another period of time (10s by default).
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 104
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The NE discards the detected unknown ATM cells, the packet loss ratio increases, and the
service performance is affected. If the packet loss ratio is high, the service may be interrupted.
Possible Causes
Possible causes of the ATMPW_UNKNOWNCELL_EXC alarm are as follows:
l PW control words are inconsistent.
l PW types are inconsistent.
l Physical links are incorrectly connected.
Procedure
Step 1 Check whether the ATM service configurations are the same at both ends of the PW, such as
the control word and PW type.
If... Then...
PW types are inconsistent Change PW types to the same. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
PW types are consistent Go to the next step.
Step 2 Check whether optical fibers or cables are correctly connected.
If... Then...
Physical links are incorrectly connected Rectify the cable or fiber connections.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
Physical links are connected correctly Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.20 AU_AIS
Description
The AU_AIS is an alarm indication of the administrative unit (AU). This alarm occurs when
the optical interface on the local NE receives the AU pointer of all 1s.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 105
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
If no network protection is configured, path-level services are interrupted.
The system sends the HP_RDI alarm to the opposite end. If subnetwork connection protection
(SNCP) is configured, the signal fail (SF) switching occurs.
Possible Causes
Possible causes of this alarm are as follows:
l The MS_AIS, R_LOC, R_LOS, or R_LOF alarm is generated on the upstream NE.
l Services are incorrectly configured.
l The opposite end sends the AU_AIS alarm.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether the VC-4 higher order pass-through services configured on the upstream NE
report the MS_AIS, R_LOC, R_LOS, or R_LOF alarm.
If... Then...
The R_LOS, R_LOF, R_LOC, or Clear the MS_AIS, R_LOC, R_LOS, or
MS_AIS alarm is reported R_LOF alarm. Then, check whether the
AU_AIS alarm is cleared. If the AU_AIS
alarm persists, go to the next step.
None of the preceding alarms is reported Go to the next step.
Step 2 Check whether the AU_AIS alarm is inserted into the transmit unit at the opposite end.
If... Then...
The AU_AIS alarm is inserted by the Cancel inserting AU_AIS alarm. Then,
transmit unit at the opposite end check whether the alarm is cleared. If the
alarm persists, go to the next step.
The AU_AIS alarm is not inserted by the Go to the next step.
transmit unit at the opposite end
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 106
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether service configurations at the local end and the opposite end are correct.
If... Then...
The service configurations are incorrect Correct the service configurations. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The service configurations are correct Go to the next step.
Step 4 Check whether the board at the opposite end is faulty.
If... Then...
The board at the opposite end is faulty Reset or replace the board. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The board at the opposite end is functioning Go to the next step.
properly
Step 5 Check whether the board at the local end is faulty.
If... Then...
The board at the local end is faulty Reset or replace the board. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The board at the local end is functioning Go to the next step.
properly
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.21 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm occurs when the
optical interface of the local NE receives the AU pointers with NDF or of invalid values for
eight consecutive frames.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 107
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
If no network protection is configured, path-level services are interrupted.
The system sends the HP_RDI alarm to the opposite end. If subnetwork connection protection
(SNCP) is configured, the signal fail (SF) switching occurs.
Possible Causes
Possible causes of this alarm are as follows:
l The local end receives excessive bit errors.
l The level of concatenated services transmitted by the opposite end is different from the
level of concatenated services that the local end is supposed to receive.
l The transmit unit or timing unit at the opposite end is faulty.
l The transmit unit or timing unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the board that reports the AU_LOP alarm also reports a bit
error alarm, such as B1_EXC, B1_SD, B2_EXC, or B2_SD.
If... Then...
The board reports a bit error alarm Clear the bit error alarm. Then, check
whether the AU_LOP alarm is cleared. If
the AU_LOP alarm persists, go to the next
step.
The board does not report a bit error alarm Go to the next step.
Step 2 Check whether service configurations at the local end and the opposite end are correct, for
example, check whether the level of concatenated services transmitted by the opposite end is
different from the level of concatenated services that the local end is supposed to receive.
If... Then...
The service configurations are incorrect Correct the service configurations. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 108
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The service configurations are correct Go to the next step.
Step 3 Check whether the timing unit is functioning properly and whether the cross-connect unit
detects the clock at the opposite end.
If... Then...
The timing unit is not functioning properly Replace the system control, cross-connect,
or the cross-connect unit does not detect the and timing board at the opposite end. Then,
clock check whether the alarm is cleared. If the
alarm persists, go to the next step.
The timing unit is functioning properly and Go to the next step.
the cross-connect unit detects the clock
Step 4 Check whether the timing unit is functioning properly and whether the cross-connect unit
detects the clock at the local end.
If... Then...
The timing unit is not functioning properly Replace the system control, cross-connect,
or the cross-connect unit does not detect the and timing board at the local end. Then,
clock check whether the alarm is cleared. If the
alarm persists, go to the next step.
The timing unit is functioning properly and Go to the next step.
the cross-connect unit detects the clock
Step 5 Set a loopback at the local end and a loopback at the opposite end. Replace the faulty board
that is detected in the loopbacks.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, and B2_SD
4.2.22 B1_EXC
Description
The B1_EXC alarm indicates that the number of regenerator section B1 bit errors in signals
received by the line board crosses the threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 109
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service quality alarm
Parameters
None.
Impact on the System
The quality of transmitted services deteriorates severely, and the services on the optical port
are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The threshold of regenerator section B1 bit errors is set to a small value.
l Fiber connectors are loosely connected, resulting in serious attenuation of received
signals.
l The clock source is incorrectly configured or the performance of the cross-connect and
timing units deteriorates.
l The line board of the transmit unit at the opposite end is faulty.
l The line board of the receive unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the threshold of regenerator section B1 bit errors is set to a
small value.
If... Then...
The threshold is set to a small value Set the threshold of regenerator section B1
bit errors to the default value. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The threshold is set to an appropriate value Go to the next step.
Step 2 Check whether the receive optical power is normal.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 110
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The receive optical power is two low Ensure that optical cables are intact, fiber
connectors are clean, and the transmit
optical power of the line board at the
opposite end is normal. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The receive optical power is normal Go to the next step.
Step 3 Check whether the clock source is correctly configured and whether the performance of the
cross-connect and timing units deteriorates at the local end.
If... Then...
The clock source is incorrectly configured Change or re-configure the clock source.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The performance of the cross-connect and Replace the system control, cross-connect
timing units deteriorates and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock source is correctly configured and Go to the next step.
the performance of the cross-connect and
timing units does not deteriorate
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
Step 4 Perform a self-loop at the local end. If bit errors are eliminated, the line board at the opposite
end is faulty. Replace the faulty line board. If bit errors increase, the line board at the local
end is faulty. Replace the faulty line board.
----End
Related Information
None.
4.2.23 B1_SD
Description
The B1_SD alarm indicates that regenerator section B1 signals received by the line board are
degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 111
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service quality alarm
Parameters
None.
Impact on the System
The quality of services deteriorates severely, and the services at the optical port are affected.
Possible Causes
Possible causes of this alarm are as follows:
l The threshold of regenerator section B1 bit errors is set to a small value.
l Fiber connectors are loosely connected, resulting in serious attenuation of received
signals.
l The clock source is incorrectly configured or the performance of the cross-connect and
timing units deteriorates.
l The line board of the transmit unit at the opposite end is faulty.
l The line board of the receive unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the threshold of regenerator section B1 bit errors is set to a
small value.
If... Then...
The threshold is set to a small value Set the threshold of regenerator section B1
bit errors to the default value. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The threshold is set to an appropriate value Go to the next step.
Step 2 Check whether the receive optical power is normal.
If... Then...
The receive optical power is two low Ensure that optical cables are intact, fiber
connectors are clean, and the transmit
optical power of the line board at the
opposite end is normal. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 112
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The receive optical power is normal Go to the next step.
Step 3 Check whether the clock source is correctly configured and whether the performance of the
cross-connect and timing units deteriorates at the local end.
If... Then...
The clock source is incorrectly configured Change or re-configure the clock source.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The performance of the cross-connect and Replace the system control, cross-connect
timing units deteriorates and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock source is correctly configured and Go to the next step.
the performance of the cross-connect and
timing units does not deteriorate
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
Step 4 Perform a self-loop at the local end. If bit errors are eliminated, the line board at the opposite
end is faulty. Replace the faulty line board. If bit errors increase, the line board at the local
end is faulty. Replace the faulty line board.
----End
Related Information
None.
4.2.24 B2_EXC
Description
The B2_EXC alarm indicates that the number of multiplex section B2 bit errors in signals
received by the line board crosses the threshold.
Attribute
Alarm Severity Alarm Type
Major Service quality alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 113
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
The services on the optical port are unavailable. If automatic multiplex section protection
(MSP) switching is configured, this alarm triggers signal fail (SF) switching.
When this alarm is generated, the system places the number of B2 bit errors into the M1 byte.
The opposite end receives the MS_REI alarm.
Possible Causes
Possible causes of this alarm are as follows:
l The threshold of multiplex section B2 bit errors is set to a small value.
l Fiber connectors are loosely connected, resulting in serious attenuation of received
signals.
l The clock source is incorrectly configured or the performance of the cross-connect and
timing units deteriorates.
l The line board of the transmit unit at the opposite end is faulty.
l The line board of the receive unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the threshold of multiplex section B2 bit errors is set to a small
value.
If... Then...
The threshold is set to a small value Set the threshold of multiplex section B2 bit
errors to the default value. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The threshold is set to an appropriate value. Go to the next step.
Step 2 Check whether the receive optical power is within the specified range.
If... Then...
The receive optical power is lower than the Ensure that optical cables are intact, fiber
lower threshold connectors are clean, and the transmit
optical power of the line board at the
opposite end is normal. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The receive optical power is within the Go to the next step.
specified range
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 114
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the clock source is correctly configured and whether the performance of the
cross-connect and timing units deteriorates at the local end.
If... Then...
The clock source is incorrectly configured Change or re-configure the clock source.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The performance of the cross-connect and Replace the system control, cross-connect,
timing units deteriorates and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock source is correctly configured and Go to the next step.
the performance of the cross-connect and
timing units does not deteriorate
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
Step 4 Perform a self-loop at the local end. If bit errors are eliminated, the line board at the opposite
end is faulty. Replace the faulty line board. If bit errors increase, the line board at the local
end is faulty. Replace the faulty line board.
----End
Related Information
None.
4.2.25 B2_SD
Description
The B2_SD alarm indicates that multiplex section B2 signals received by the line board are
degraded.
Attribute
Alarm Severity Alarm Type
Minor Service quality alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 115
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The services at the optical port are affected. If automatic multiplex section protection (MSP)
switching is configured and signal degrade (SD) switching is enabled, this alarm triggers SD
switching.
When this alarm is generated, the system places the number of B2 bit errors into the M1 byte.
The opposite end receives the MS_REI alarm.
Possible Causes
Possible causes of this alarm are as follows:
l The threshold of multiplex section B2 bit errors is set to a small value.
l Fiber connectors are loosely connected, resulting in serious attenuation of received
signals.
l The clock source is incorrectly configured or the performance of the cross-connect and
timing units deteriorates.
l The line board of the transmit unit at the opposite end is faulty.
l The line board of the receive unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the threshold of multiplex section B2 bit errors is set to a small
value.
If... Then...
The threshold is set to a small value Set the threshold of multiplex section B2 bit
errors to the default value. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The threshold is set to an appropriate value. Go to the next step.
Step 2 Check whether the receive optical power is within the specified range.
If... Then...
The receive optical power is lower than the Ensure that optical cables are intact, fiber
lower threshold connectors are clean, and the transmit
optical power of the line board at the
opposite end is normal. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The receive optical power is within the Go to the next step.
specified range
Step 3 Check whether the clock source is correctly configured and whether the performance of the
cross-connect and timing units deteriorates at the local end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 116
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The clock source is incorrectly configured Change or re-configure the clock source.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The performance of the cross-connect and Replace the system control, cross-connect,
timing units deteriorates and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock source is correctly configured and Go to the next step.
the performance of the cross-connect and
timing units does not deteriorate
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
Step 4 Perform a self-loop at the local end. If bit errors are eliminated, the line board at the opposite
end is faulty. Replace the faulty line board. If bit errors increase, the line board at the local
end is faulty. Replace the faulty line board.
----End
Related Information
None.
4.2.26 B3_EXC
Description
The B3_EXC alarm indicates that the number of higher order B3 bit errors in signals received
by the line board crosses the threshold.
Attribute
Alarm Severity Alarm Type
Major Service quality alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 117
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
If the line board is configured with higher order subnetwork connection protection (SNCP)
switching and switching in case of crossing of the higher order bit error threshold, this alarm
triggers switching in case of crossing of the higher order bit error threshold.
When the B3_EXC alarm is generated, the system sends the HP_REI alarm to the opposite
end.
Possible Causes
Possible causes of this alarm are as follows:
l The threshold of B3 bit errors is set to a small value.
l Fiber connectors are loosely connected, resulting in serious attenuation of received
signals.
l The clock source is incorrectly configured, or the performance of the cross-connect and
timing units deteriorates.
l The line board of the transmit unit at the opposite end is faulty.
l The line board of the receive unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the threshold of B3 bit errors is set to a small value.
If... Then...
The threshold is set to a small value Set the threshold of B3 bit errors to the
default value. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The threshold is set to an appropriate value Go to the next step.
Step 2 Check whether the receive optical power is within the specified range
If... Then...
The receive optical power is lower than the Ensure that optical cables are intact, fiber
lower threshold connectors are clean, and the transmit
optical power of the line board at the
opposite end is normal. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The receive optical power is within the Go to the next step.
specified range
Step 3 Check whether the clock source is correctly configured and whether the performance of the
cross-connect and timing units deteriorates at the local end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 118
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The clock source is incorrectly configured Change or re-configure the clock source.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The performance of the cross-connect and Replace the system control, cross-connect,
timing units deteriorates and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock source is correctly configured and Go to the next step.
the performance of the cross-connect and
timing units does not deteriorate
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
Step 4 Perform a self-loop at the local end. If bit errors are eliminated, the line board at the opposite
end is faulty. Replace the faulty line board. If bit errors increase, the line board at the local
end is faulty. Replace the faulty line board.
----End
Related Information
None.
4.2.27 B3_EXC_VC3
Description
The B3_EXC_VC3 alarm indicates that B3 bit errors in a VC-3 path cross the threshold.
Attribute
Alarm Severity Alarm Type
Major Service quality 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 119
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
If the alarm occurs, it indicates that the number of bit errors (lower order B3 bit errors)
crosses the performance threshold. The VC-3 services have severe bit errors.
Possible Causes
Possible causes of the B3_EXC_VC3 alarm are as follows:
l There are B1 or B2 bit errors.
l The received signals are heavily attenuated.
l The fiber head is dirty or an incorrect connector is used.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether B1 or B2 bit errors are present on the line board responsible for service access.
If... Then...
The B1_EXC, B1_SD, B2_EXC, or Refer to the corresponding section in this
B2_SDalarm is reported document to clear the B1_EXC, B1_SD,
B2_EXC, or B2_SD alarm.
No B1_EXC, B1_SD, B2_EXC, or B2_SD Go to the next step.
is reported
Step 2 Check whether the receive optical power is normal.
If... Then...
The optical power is lower than the lower Check whether the fibers are functional,
threshold fiber connectors are clean, and transmit
optical power of the opposite line board is
normal.
The optical power is normal Go to the next step.
Step 3 Check whether the working temperature is normal.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 120
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The working temperature is over high or In the case of over high working
over low temperature, add a cooling device to the NE.
In the case of the over low working
temperature, add a heating device to the NE.
The working temperature is normal Go to the next step.
Step 4 Check whether service configurations are correct. If the service configurations are incorrect,
rectify the configurations. If the service configurations are correct, go to the next step
Step 5 Check for the B3_EXC_VC3 alarm on the U2000.
If... Then...
If the B3_EXC_VC3 alarm is cleared No further action is required.
If theB3_EXC_VC3 alarm persists Go to the next step.
Step 6 Perform loopbacks at both the local and opposite ends to locate the faulty board.
If... Then...
The B3 bit error performance event is The transmit part of the opposite board is
reported on the opposite board faulty. Replace the faulty board.
The B3 bit error performance event is The receive part of the local board is faulty.
reported on the local board Replace the faulty board.
----End
Related Information
None.
4.2.28 B3_EXC_VC4
Description
The B3_EXC_VC4 alarm indicates that B3 bit errors in a VC-4 path cross the threshold.
Attribute
Alarm Severity Alarm Type
Major Service quality alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 121
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-4 path number that generates the alarm.
Impact on the System
If the alarm occurs, it indicates that the number of bit errors (lower order B3 bit errors)
crosses the performance threshold. The VC-4 services have severe bit errors.
Possible Causes
Possible causes of the B3_EXC_VC4 alarm are as follows:
l There are B1 or B2 bit errors.
l The received signals are heavily attenuated.
l The fiber head is dirty or an incorrect connector is used.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether B1 or B2 bit errors are present on the line board responsible for service access.
If... Then...
The B1_EXC, B1_SD, B2_EXC, or Refer to the corresponding section in this
B2_SDalarm is reported document to clear the B1_EXC, B1_SD,
B2_EXC, or B2_SD alarm.
No B1_EXC, B1_SD, B2_EXC, or B2_SD Go to the next step.
is reported
Step 2 Check whether the receive optical power is normal.
If... Then...
The optical power is lower than the lower Check whether the fibers are functional,
threshold fiber connectors are clean, and transmit
optical power of the opposite line board is
normal.
The optical power is normal Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 122
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the working temperature is normal.
If... Then...
The working temperature is over high or In the case of over high working
over low temperature, add a cooling device to the NE.
In the case of the over low working
temperature, add a heating device to the NE.
The working temperature is normal Go to the next step.
Step 4 Check whether service configurations are correct. If the service configurations are incorrect,
rectify the configurations. If the service configurations are correct, go to the next step
Step 5 Check for the B3_EXC_VC3 alarm on the U2000.
If... Then...
If the B3_EXC_VC3 alarm is cleared No further action is required.
If theB3_EXC_VC3 alarm persists Go to the next step.
Step 6 Perform loopbacks at both the local and opposite ends to locate the faulty board.
If... Then...
The B3 bit error performance event is The transmit part of the opposite board is
reported on the opposite board faulty. Replace the faulty board.
The B3 bit error performance event is The receive part of the local board is faulty.
reported on the local board Replace the faulty board.
----End
Related Information
None.
4.2.29 B3_SD
Description
The B3_SD alarm indicates that higher order path B3 signals received by the line board are
degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 123
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service quality alarm
Parameters
None.
Impact on the System
The services transmitted on the path are affected. If higher order subnetwork connection
protection (SNCP) switching is configured and switching in case of higher order signal
degradation is enabled, the B3_SD alarm triggers switching in case of higher order signal
degradation.
When the alarm B3_SD is generated, the system sends the HP_REI alarm to the opposite end.
Possible Causes
Possible causes of this alarm are as follows:
l The threshold of B3 bit errors is set to a small value.
l Fiber connectors are loosely connected, resulting in serious attenuation of received
signals.
l The clock source is incorrectly configured, or the performance of the cross-connect and
timing units deteriorates.
l The line board of the transmit unit at the opposite end is faulty.
l The line board of the receive unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the threshold of B3 bit errors is set to a small value.
If... Then...
The threshold is set to a small value Set the threshold of B3 bit errors to the
default value. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The threshold is set to an appropriate value Go to the next step.
Step 2 Check whether the receive optical power is within the specified range
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 124
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The receive optical power is lower than the Ensure that optical cables are intact, fiber
lower threshold connectors are clean, and the transmit
optical power of the line board at the
opposite end is normal. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The receive optical power is within the Go to the next step.
specified range
Step 3 Check whether the clock source is correctly configured and whether the performance of the
cross-connect and timing units deteriorates at the local end.
If... Then...
The clock source is incorrectly configured Change or re-configure the clock source.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The performance of the cross-connect and Replace the system control, cross-connect,
timing units deteriorates and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock source is correctly configured and Go to the next step.
the performance of the cross-connect and
timing units does not deteriorate
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
Step 4 Perform a self-loop at the local end. If bit errors are eliminated, the line board at the opposite
end is faulty. Replace the faulty line board. If bit errors increase, the line board at the local
end is faulty. Replace the faulty line board.
----End
Related Information
None.
4.2.30 B3_SD_VC3
Description
The B3_SD_VC3 alarm indicates that B3 signals in a VC-3 path degrade.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 125
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service quality 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 details
about each parameter, refer to the following 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 that generates the alarm.
Impact on the System
Services are affected.
The system sends the HP_REI alarm to the opposite end.
Possible Causes
Possible causes of the B3_SD_VC3 alarm are as follows:
l The received signals are heavily attenuated.
l The fiber head is dirty or an incorrect connector is used.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether B1 or B2 bit errors are present on the line board that is responsible for service
access.
If... Then...
The B1_EXC, B1_SD, B2_EXC, or B2_SD Clear the B1_EXC, B1_SD, B2_EXC, or
alarm is reported B2_SD alarm.
No B1_EXC, B1_SD, B2_EXC, or B2_SD Go to the next step.
is reported
Step 2 Check whether the receive optical power is normal.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 126
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The optical power is lower than the lower Ensure that the fibers are functional, fiber
threshold connectors are clean, and transmit optical
power of the opposite line board is normal.
The optical power is normal Go to the next step.
Step 3 Check whether the clock source at the local end is correctly configured. If not, rectify the
clock source configurations 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...
If this alarm is cleared No further action is required.
If this alarm persists Go to the next step.
Step 5 Check whether service configurations are correct. For example, if a lower order service from
the opposite end is configured as a pass-through service and the service configuration is
wrong, modify or redeliver the configuration.
Step 6 View alarms on the U2000 to check whether the B3_SD_VC3 alarm is cleared.
If... Then...
If this alarm is cleared No further action is required.
If this alarm persists Go to the next step.
Step 7 Perform loopbacks at both the local and opposite ends to locate the faulty board.
If... Then...
The B3 bit error performance event is The transmit part of the opposite board is
reported on the opposite board faulty. Replace the faulty board.
The B3 bit error performance event is The receive part of the local board is faulty.
reported on the local board Replace the faulty board.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 127
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.31 B3_SD_VC4
Description
The B3_SD_VC4 alarm indicates that B3 bit errors in a VC-4 path cross the set deterioration
threshold.
Attribute
Alarm Severity Alarm Type
Minor Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-4 path number that generates the alarm.
Impact on the System
If the alarm occurs, it indicates that bit errors occur in the path-level services.
Possible Causes
Possible causes of the B3_SD_VC4 alarm are as follows:
l There are B1 or B2 bit errors.
l The received signals are heavily attenuated.
l The fiber head is dirty or an incorrect connector is used.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether B1 or B2 bit errors are present on the line board responsible for service access.
If... Then...
The B1_EXC, B1_SD, B2_EXC, or Refer to the corresponding section in this
B2_SDalarm is reported document to clear the B1_EXC, B1_SD,
B2_EXC, or B2_SD alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 128
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
No B1_EXC, B1_SD, B2_EXC, or B2_SD Go to the next step.
is reported
Step 2 Check whether the receive optical power is normal.
If... Then...
The optical power is lower than the lower Check whether the fibers are functional,
threshold fiber connectors are clean, and transmit
optical power of the opposite line board is
normal.
The optical power is normal Go to the next step.
Step 3 Check whether the working temperature is normal.
If... Then...
The working temperature is over high or In the case of over high working
over low temperature, add a cooling device to the NE.
In the case of the over low working
temperature, add a heating device to the NE.
The working temperature is normal Go to the next step.
Step 4 Check whether service configurations are correct. If the service configurations are incorrect,
rectify the configurations. If the service configurations are correct, go to the next step
Step 5 Check for the B3_EXC_VC3 alarm on the U2000.
If... Then...
If the B3_EXC_VC3 alarm is cleared No further action is required.
If theB3_EXC_VC3 alarm persists Go to the next step.
Step 6 Perform loopbacks at both the local and opposite ends to locate the faulty board.
If... Then...
The B3 bit error performance event is The transmit part of the opposite board is
reported on the opposite board faulty. Replace the faulty board.
The B3 bit error performance event is The receive part of the local board is faulty.
reported on the local board Replace the faulty board.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 129
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.32 BAT1TEMP_SENSOR_FAIL
Description
The BAT1TEMP_SENSOR_FAIL alarm indicates that the temperature sensor of battery
group 1 of the PMU fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The equipment cannot collect temperature data of battery group 1.
Possible Causes
Possible causes of this alarm are as follows:
l No temperature sensor is installed.
l The temperature sensor is not correctly connected.
l The temperature sensor is faulty.
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether a temperature sensor is installed for battery group 1.
If... Then...
No temperature sensor is installed Install a temperature sensor correctly.
A temperature sensor is installed Go to the next step.
Step 2 On the U2000, check whether the BAT1TEMP_SENSOR_FAIL alarm is cleared. If the alarm
persists, check whether the temperature sensor of battery group 1 is correctly connected and
the cable is intact.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 130
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The temperature sensor is not correctly Connect the temperature sensor correctly.
connected
The cable is damaged Replace the cable.
The temperature sensor is correctly Go to the next step.
connected and the cable is intact
Step 3 On the U2000, check whether the BAT1TEMP_SENSOR_FAIL alarm is cleared. If the alarm
persists, replace the temperature sensor.
Step 4 If the BAT1TEMP_SENSOR_FAIL alarm persists after the temperature sensor is replaced,
replace the cabinet.
----End
Related Information
None.
4.2.33 BAT2TEMP_SENSOR_FAIL
Description
The BAT2TEMP_SENSOR_FAIL alarm indicates that the temperature sensor of battery
group 2 of the PMU fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The equipment cannot collect temperature data of battery group 2.
Possible Causes
Possible causes of this alarm are as follows:
l No temperature sensor is installed.
l The temperature sensor is not correctly connected.
l The temperature sensor is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 131
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether a temperature sensor is installed for battery group 2.
If... Then...
No temperature sensor is installed Install a temperature sensor correctly.
A temperature sensor is installed Go to the next step.
Step 2 On the U2000, check whether the BAT2TEMP_SENSOR_FAIL alarm is cleared. If the alarm
persists, check whether the temperature sensor of battery group 2 is correctly connected and
the cable is intact.
If... Then...
The temperature sensor is not correctly Connect the temperature sensor correctly.
connected
The cable is damaged Replace the cable.
If the temperature sensor is correctly Go to the next step.
connected and the cable is intact
Step 3 On the U2000, check whether the BAT2TEMP_SENSOR_FAIL alarm is cleared. If the alarm
persists, replace the temperature sensor.
Step 4 If the BAT2TEMP_SENSOR_FAIL alarm persists after the temperature sensor is replaced,
replace the cabinet.
----End
Related Information
None.
4.2.34 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED alarm indicates that a physical board is installed but its logical
board is not created on the U2000.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 132
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Number of the slot where this alarm is generated.
Parameter 2 to Parameter 5 Meaningless.
Impact on the System
When the BD_NOT_INSTALLED alarm is reported, the alarmed slot cannot be configured
with services. This alarm, however, does not affect the operation of the system.
Possible Causes
The possible cause of the BD_NOT_INSTALLED alarm is as follows:
A physical board is installed in a slot but its logical board is not created on the U2000.
Procedure
Step 1 Check the BD_NOT_INSTALLED alarm information on the U2000 and confirm the slot
number according to Parameter 1.
Step 2 The BD_NOT_INSTALLED alarm is cleared when the logical board is added to the correct
slot on the U2000.
Step 3 Optional: If the physical board is not being used, remove the physical board to clear this
alarm.
----End
Related Information
None.
4.2.35 BD_STATUS
Description
The BD_STATUS alarm indicates that a board for which the logical board has been created
cannot be detected or is offline.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 133
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The functions of the board are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The board is not installed or is loosely installed.
l The RAM is faulty.
l The board is faulty.
Procedure
Step 1 Check whether the board is correctly installed in the slot.
If... Then...
The board is not installed Install the board correctly. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
If the board is loosely installed Reinstall the board correctly. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
If the board is correctly installed Go to the next step.
Step 2 Check whether the RAM on the equipment is faulty.
If... Then...
The RAM is faulty Replace the RAM. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The RAM is functioning properly Go to the next step.
Step 3 Check whether the board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 134
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The board is faulty Perform a cold reset on the board, or replace
the board.
The board is functioning properly Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.36 BD_VER_NMAT
Description
The BD_VER_NMAT alarm indicates that the board version does not match. This alarm is
reported when the software or hardware version (FPGA version, BIOS version, extended
BIOS version, hardware PCB version, or hardware function version) of a board on an OSN
580 is inconsistent with that in the version mapping table of the board. This alarm is reported
when the FPGA version of a board on an OSN 550 is inconsistent with the software package
version.
NOTE
l FPGA: stands for field programmable gate array.
l BIOS: stands for basic input/output system.
l Hardware PCB: indicates the hardware module of the printed circuit board (PCB).
Attribute
Alarm Severity Alarm Type
Major Processing error 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicate the slot ID of the board that reports an BD_VER_NMAT alarm.
Parameter 2
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 135
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the version that is inconsistent with that in the version mapping
table for the OSN 580.
l 0x01: represents the extended BIOS version.
l 0x02: represents the software version.
l 0x03: represents the FPGA version.
l 0x04: represents the BIOS version.
l 0x05: represents the PCB version.
l 0x06: represents the hardware function version.
Indicates the version that is inconsistent with the software package version
for the OSN 550.
l 0x03: represents the FPGA version.
Parameter 4 If the value of Parameter 3 is 0x06 and the logical board is EFS8 for the
OSN 580, the values of Parameter 4 are as follows:
l 0x01: TNH1EFS8 board
l 0x02: TNH2EFS8 board
Impact on the System
Some specific functions are unavailable, which affects services.
Possible Causes
If the BD_VER_NMAT alarm is reported for an OSN 580, the possible causes are as follows:
l Cause 1: The software version of the board reporting a BD_VER_NMAT alarm is
inconsistent with that in the version mapping table.
l Cause 2: The hardware version (that is, FPGA version, BIOS version, extended BIOS
version, or PCB version) of the board reporting a BD_VER_NMAT alarm is inconsistent
with that in the version mapping table.
l Cause 3: The hardware function version of the board is inconsistent with that in the
version mapping table.
If the BD_VER_NMAT alarm is reported for an OSN 550, the possible cause is as follows:
l Cause 1: The FPGA version of the board is inconsistent with the software package
version.
Procedure
Step 1 Query the alarm on the NMS for the OSN 580. View Parameters 1 and 2 to determine the
board that reports the alarm, and view Parameters 3 and 4 to determine the version that is
inconsistent with that in the version mapping table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 136
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then…
The FPGA version, BIOS version, Upgrade or downgrade the board to ensure
extended BIOS version, or software that the FPGA version, BIOS version,
version of the board is inconsistent with extended BIOS version, and software
that in the version mapping table, version of the board are consistent with
those in the version mapping table.
The PCB version of the board is Replace the PCB hardware module to
inconsistent with that in the version ensure that the PCB version is consistent
mapping table, with that in the version mapping table.
The hardware function version of the Use a board with the correct hardware
board is inconsistent with that in the version to replace the board (for example,
version mapping table, use the TNH3EFS8 board to replace the
THN1EFS8 board).
Step 2 Query the alarm on the NMS for the OSN 550. View Parameters 1 and 2 to determine the
board that reports the alarm, and view Parameter 3 to determine the version that is
inconsistent with the software package version.
If… Then…
The FPGA version of the board is Perform a cold reset on the board to restore
inconsistent with the software package the FPGA version of the board to the correct
version, one. A cold reset may interrupt services.
Evaluate the impact on services and perform
a cold reset at an appropriate time.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.37 BD_VER_NOT_MATCH
Description
The BD_VER_NOT_MATCH alarm indicates a board version mismatch.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 137
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter Indicate the slot ID.
2
Parameter 3 Indicates the version that is different from that specified in the
version mapping table.
l 0x01: extended BIOS version
l 0x02: board software version
l 0x03: FPGA version
l 0x04: BIOS version
l 0x05: PCB version
Impact on the System
Certain functions fail.
Possible Causes
The possible causes of the BD_VER_NOT_MATCH alarm are as follows:
l Cause 1: The board software, FPGA, BIOS, or extended BIOS version does not match
that specified in the version mapping table.
l Cause 2: The board PCB version does not match that specified in the version mapping
table.
Procedure
Step 1 Cause 1: The board software, FPGA, BIOS, or extended BIOS version does not match that
specified in the version mapping table.
1. Upgrade or downgrade the board software, FPGA, BIOS, or extended BIOS to a correct
version and warm reset the board.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The board PCB version does not match that specified in the version mapping table.
1. Replace the PCB module with a new one of a correct version.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 138
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.38 BDID_ERROR
Description
The BDID_ERROR alarm indicates that errors occur in slot verification.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
None.
Impact on the System
l The alarmed board may fail to get online and services on the board are interrupted.
l You cannot configure and monitor the services on the board.
Possible Causes
Possible causes of the BDID_ERROR alarm are as follows:
l The board is not inserted tightly.
l The backplane has bent pins.
l The board has hardware faults.
Procedure
Step 1 View the BDID_ERROR alarm on the NMS to confirm the alarmed board.
Step 2 Check whether the board is inserted tightly.
If... Then...
The board is not inserted tightly Reseat the board and check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The board is inserted tightly Go to the next step.
Step 3 Remove the board to check whether the backplane has bent pins.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 139
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The backplane has bent pins Fix these bent pins and then insert the
board. Check whether the alarm is cleared.
If the alarm persists, go to the next step.
The backplane does not have bent pins Go to the next step.
Step 4 Check whether the board is functioning properly.
If... Then...
The board is malfunctioning Reset (cold) the board or replace it.
The board is functioning properly Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.39 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL alarm indicates that the temperature sensor on a board fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The equipment cannot collect temperature data of the TCU board.
Possible Causes
Possible causes of this alarm are as follows:
l No temperature sensor is installed.
l The temperature sensor is incorrectly connected.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 140
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The temperature sensor is faulty.
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether a temperature sensor is installed on the board.
If... Then...
No temperature sensor is installed Install a temperature sensor correctly. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
A temperature sensor is installed Go to the next step.
Step 2 Check whether the temperature sensor is correctly connected and the cable is intact.
If... Then...
The temperature sensor is incorrectly Connect the temperature sensor correctly.
connected Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The cable is damaged Replace the cable. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The temperature sensor is correctly Go to the next step.
connected and the cable is intact
Step 3 Replace the temperature sensor. Then, check whether the alarm is cleared.
If... Then...
The alarm persists Replace the cabinet. The alarm is
automatically cleared.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.40 BEFFEC_EXC
Description
The BEFFEC_EXC is an alarm that forward error correction (FEC) signals are degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 141
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None.
Impact on the System
When the BEFFEC_EXC alarm occurs, the service transmission performance is affected.
Possible Causes
The possible causes of the BEFFEC_EXC alarm are as follows:
l A higher-level alarm, such as the R_LOS or FEC_LOF, occurs in the system.
l The optical power is improper.
l The transmission fiber is faulty.
l The transmit unit at the opposite station is faulty.
l The board at the local station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS or FEC_LOF, occurs on the board.
If yes, take priority to clear it, and then check whether the BEFFEC_EXC alarm is cleared.
Step 2 If the alarm persists, clean the fiber connector, and then check whether the BEFFEC_EXC
alarm is cleared.
Step 3 If the alarm persists, check the input optical power. Moreover, you can add or remove some
optical attenuators so that the optical power is proper.
Step 4 If the alarm persists, check the launched optical power at the opposite end. If the optical
power is extremely low, replace the optical module on the board or the line board at the
opposite end.
Step 5 If the alarm persists, check whether the fiber is damaged. If yes, replace the fiber, and then
check whether the BEFFEC_EXC alarm is cleared.
Step 6 If bit errors still occur, replace the line board that reports bit errors at the local station.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 142
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.41 BIOS_STATUS
Description
The BIOS_STATUS alarm indicates the BIOS state. By default, if loading board software
fails for five consecutive times within 780 seconds, the board enters the BIOS state and the
BIOS_STATUS alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the slot number of the board in the BIOS state.
Impact on the System
Services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The software is lost.
l Incorrect software is loaded.
l Writing or reading the software becomes abnormal.
l The board hardware is faulty.
Procedure
Step 1 View the BIOS_STATUS alarm on the U2000 to determine the board that reports the
BIOS_STATUS alarm according to Parameter 1.
Step 2 Perform warm reset on the board. Then, check whether the BIOS_STATUS alarm is cleared.
If... Then...
The alarm persists Perform a cold reset on the board. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 143
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
Step 3 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.42 BIP_EXC
Description
The BIP_EXC alarm indicates that the number of lower order BIP-2 bit errors in the V5 byte
on the board crosses the preset threshold (10-3 by default).
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-12 path ID.
Impact on the System
The quality of VC-12 services deteriorates and VC-12 services are affected. If lower order
subnetwork connection protection (SNCP) switching is configured and switching in case of
crossing of the lower order bit error threshold is enabled, the BIP_EXC alarm triggers
switching in case of crossing of the lower order bit error threshold.
When the BIP_EXC alarm occurs, the system sends the LP_REI alarm to the opposite end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 144
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l A high-level bit error alarm, such as B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD, is generated.
l The optical power is abnormal.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
l The cross-connect unit is faulty.
Procedure
Step 1 Check whether the board that receives services reports a high-level bit error alarm, such as
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or B3_SD.
If... Then...
The B1_EXC, B1_SD, B2_EXC, B2_SD, Clear the B1_EXC, B1_SD, B2_EXC,
B3_EXC, or B3_SD alarm is reported B2_SD, B3_EXC, or B3_SD alarm. Then,
check whether the BIP_EXC alarm is
cleared. If the BIP_EXC alarm persists, go
to the next step.
The B1_EXC, B1_SD, B2_EXC, B2_SD, Go to the next step.
B3_EXC, or B3_SD alarm is not reported
Step 2 On the U2000, check whether the transmit optical power of the board at the opposite end is
within the specified range.
If... Then...
The transmit optical power of the board at Go to Step 4.
the opposite end is out of range
The transmit optical power of the board at Go to the next step.
the opposite end is within the specified
range
Step 3 On the U2000, check whether the receive optical power of the board at the local end is within
the specified range.
If... Then...
The receive optical power of the board at Go to Step 6.
the local end is out of range
The receive optical power of the board at Go to Step 7.
the local end is within the specified range
Step 4 Perform a cold reset on the board at the opposite end by using the U2000 or by reseating the
board. Then, check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 145
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the optical module or the board.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The alarm is cleared No further action is required.
Step 5 Replace the system control, cross-connect, and timing board at the opposite end. Then, check
whether the alarm is cleared.
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
The alarm is cleared No further action is required.
Step 6 Perform a cold reset on the board at the local end by using the U2000 or by reseating the
board. Then, check whether the alarm is cleared.
If... Then...
The alarm persists Replace the optical module or the board.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The alarm is cleared No further action is required.
Step 7 Replace the system control, cross-connect, and timing board at the local end. Then, check
whether the alarm is cleared.
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 146
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD
4.2.43 BIP_SD
Description
The BIP_SD alarm indicates that lower order signals (BIP-2) on the board are degraded. This
alarm is generated when the board detects that the number of BIP-2 bit errors in the V5 byte
crosses the preset threshold (10-6 by default).
Attribute
Alarm Severity Alarm Type
Minor Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-12 path ID.
Impact on the System
Services are affected. If lower order subnetwork connection protection (SNCP) switching is
configured and switching in case of lower order signal degradation is enabled, the BIP_SD
alarm triggers switching in case of lower order signal degradation.
When the BIP_SD alarm occurs, the system sends the LP_REI alarm to the opposite end.
Possible Causes
Possible causes of this alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 147
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l A high-level bit error alarm, such as B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD, is generated.
l The optical power is abnormal.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
l The cross-connect unit is faulty.
Procedure
Step 1 Check whether the board that receives services reports a high-level bit error alarm, such as
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or B3_SD.
If... Then...
The B1_EXC, B1_SD, B2_EXC, B2_SD, Clear the B1_EXC, B1_SD, B2_EXC,
B3_EXC, or B3_SD alarm is reported B2_SD, B3_EXC, or B3_SD alarm. Then,
check whether the BIP_EXC alarm is
cleared. If the BIP_EXC alarm persists, go
to the next step.
The B1_EXC, B1_SD, B2_EXC, B2_SD, Go to the next step.
B3_EXC, or B3_SD alarm is not reported
Step 2 On the U2000, check whether the transmit optical power of the board at the opposite end is
within the specified range.
If... Then...
The transmit optical power of the board at Go to Step 4.
the opposite end is out of range
The transmit optical power of the board at Go to the next step.
the opposite end is within the specified
range
Step 3 On the U2000, check whether the receive optical power of the board at the local end is within
the specified range.
If... Then...
The receive optical power of the board at Go to Step 6.
the local end is out of range
The receive optical power of the board at Go to Step 7.
the local end is within the specified range
Step 4 Perform a cold reset on the board at the opposite end by using the U2000 or by reseating the
board. Then, check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 148
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the optical module or the board.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The alarm is cleared No further action is required.
Step 5 Replace the system control, cross-connect, and timing board at the opposite end. Then, check
whether the alarm is cleared.
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
The alarm is cleared No further action is required.
Step 6 Perform a cold reset on the board at the local end by using the U2000 or by reseating the
board. Then, check whether the alarm is cleared.
If... Then...
The alarm persists Replace the optical module or the board.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The alarm is cleared No further action is required.
Step 7 Replace the system control, cross-connect, and timing board at the local end. Then, check
whether the alarm is cleared.
Replacing the system control, cross-connect, and timing board interrupts services. Exercise
caution when performing this operation.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 149
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.44 BOOTROM_BAD
Description
The BOOTROM_BAD alarm indicates that BOOTROM data check fails. During the running
of board software, the system periodically checks whether BOOTROM data is damaged. This
alarm is generated when the system detects that BOOTROM data is damaged.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the BIOS damage.
l 0x01: The basic BIOS is damaged.
l 0x02: The extended BIOS is damaged.
Parameter 2 The value is always 0xff, and this parameter is meaningless.
Parameter 3 The value is always 0xff, and this parameter is meaningless.
Impact on the System
If the board has started, the BOOTROM_BAD alarm does not have any impact on the system
and services.
If you perform a cold reset on the board after the BOOTROM_BAD alarm is generated,
loading BIOS to the board fails and the board cannot start.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 150
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The basic BIOS is damaged.
l The extended BIOS is damaged.
l The BOOTROM data area is damaged.
l The system control unit is faulty.
Procedure
Step 1 View the BOOTROM_BAD alarm on the U2000 to determine the board that reports the
alarm.
Step 2 Replace the board.
If the board has started, do not replace the board because replacing the board interrupts
services but the BOOTROM_BAD alarm does not have any impact on the system and
services.
----End
Related Information
None.
4.2.45 BRDCASTRATIO_OVER
Description
The BRDCASTRATIO_OVER alarm indicates that the ratio of broadcast traffic exceeds the
threshold. This alarm is reported when the ratio of broadcast and multicast packets to all
packets exceeds the specified threshold and the port traffic is greater than or equal to 10
Mbit/s.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 151
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the direction.
l 0x00: receive direction
l 0x01: transmit direction
Impact on the System
l The available bandwidth decreases and packet loss may occur.
l In IPTV scenarios, this alarm does not affect the system or services.
Possible Causes
The possible causes of the BRDCASTRATIO_OVER alarm are as follows:
l Cause 1: The threshold is improperly set.
l Cause 2: The ratio of broadcast and multicast packets exceeds the threshold.
Procedure
Step 1 Cause 1: The threshold is improperly set.
1. Set a proper threshold. By default, the upper threshold is 50% and the lower threshold is
40%. Check whether the alarm is cleared.
2. If the alarm persists, go to Step 2.
Step 2 Cause 2: The ratio of broadcast and multicast packets exceeds the threshold.
1. Check the configurations and networking. Clear any loop identified on the network and
check whether the alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
Step 3 This alarm does not affect IPTV systems or services. It is advised to disable the monitoring of
this alarm in IPTV scenarios.
----End
Related Information
None
4.2.46 BUS_ERR
Description
The BUS_ERR alarm indicates bus errors.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 152
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
TNH1CSHD (SCC) The values of parameter 1 are as follows:
l 0x01: BUS_LOS alarm
TNM1PCX (SCC)
l 0x02: BUS_OOF alarm
l 0x03: BUS_LOF alarm
l 0x04: BUS_OOA alarm
l 0x0a: BUS_SERDS_ERR alarm
l 0x0c: BUS_HW_ERR alarm
l 0x0d: BUS_FE_ERR alarm
l 0x0f: BUS_IIC_ERR alarm
Parameter 2 indicates the sequence number
of the faulty bus.
If parameter 1 is 0x11 and parameter 3 is
0x00, parameter 2 indicates that the state of
the link in the slot is abnormal.
TNW1PF4E8, TNW1SP3S l 0x01 0x00 0x01: The bus of the cross-
connect board with a smaller slot ID is
TNH2PL3T, TNH2SP3D, TNM1PD1, abnormal.
TNW1AT8, TNW1DXM, TNW1FXSO12, l 0x01 0x00 0x02: The bus of the cross-
TNW1SL41O, DIO connect board with a greater slot ID is
abnormal.
TNM1CQ1 0x02 0x47: The link between the 8870 chip
and the GE port of the backplane bus is
abnormal because the board is not properly
installed.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 153
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1CXL (XC) The values of parameter 1 are as follows:
l 0x01: BUS_LOS alarm
l 0x02: BUS_OOF alarm
l 0x03: BUS_LOF alarm
l 0x04: BUS_OOA alarm
l 0x0a: BUS_SERDS_ERR alarm
l 0x0c: BUS_HW_ERR alarm
l 0x0d: BUS_FE_ERR alarm
l 0x0f: BUS_IIC_ERR alarm
Parameter 2 indicates the sequence number
of the faulty bus.
TNM1EF8F 0x11 para[2] 0x00: The link status of the
DSA port is abnormal.
l para[2] indicates the board slot ID.
TNM1EG4C, TNM1EG8 l 0x11 0x01 0x00: The link of the board in
slot 1 is abnormal.
l 0x11 0x02 0x00: The link of the board in
slot 2 is abnormal.
l 0x11 0x03 0x00: The link of the board in
slot 3 is abnormal.
l 0x11 0x04 0x00: The link of the board in
slot 4 is abnormal.
l 0x11 0x05 0x00: The link of the board in
slot 5 is abnormal.
l 0x11 0x06 0x00: The link of the board in
slot 6 is abnormal.
TNM1EM6T, TNM1EM6F 0x11 para[2] 0x00: Alarms are inserted back
into an EM6T or EM6F board.
l para[2] indicates the board ID.
TNH1CSHD (ML1) 0x0c 0x01: An 8B/10B error is detected from
the TBI port.
TNM1MD1
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 154
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1PCX (PEXC), TNM1PCX (PUXC), Parameter 1 indicates the slot ID of a logical
TNM1PCX (PGXC) board.
Parameter 2 indicates the sequence number
of the faulty bus.
If a bit in parameter 3 is 1, the corresponding
alarm is reported. If a bit in parameter 3 is 0,
the corresponding alarm is not reported.
l bit[0] indicates a BUS_OOA alarm.
l bit[1] indicates a BUS_OOF alarm.
l bit[2] indicates a B1 bit error alarm.
l bit[3] indicates an FIFO overflow alarm.
l bit[4] indicates a BUS_LOS alarm.
The values of parameter 4 are as follows:
l 0x01: alarm for the bus of type I
l 0x02: alarm for the bus of type II
l 0x03: alarm for the bus of type III
l 0x04: TLOSEX alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 155
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1PCX (PEX1), TNM1EX1 The values of parameter 1 are as follows:
l 1 indicates a BUS_LOS alarm.
l 2 indicates a BUS_OOF alarm.
l 3 indicates a BUS_LOF alarm.
l 4 indicates a BUS_OOA alarm.
l 5 indicates a BUS_RX_DOWN alarm.
l 6 indicates a BUS_TX_DOWN alarm.
l 7 indicates a BUS_SPI_DOWN alarm.
l 8 indicates a BUS_SCI_ERR alarm.
l 9 indicates a BUS_OPP_CLK_LOC
alarm
l 10 indicates a BUS_SERDS_ERR alarm.
l 11 indicates a BUS_MII_ERR alarm.
l 12 indicates a BUS_HW_ERR alarm.
l 13 indicates a BUS_FE_ERR.
l 14 indicates a BUS_EMIF_ERR alarm.
l 15 indicates a BUS_IIC_ERR alarm.
l 16 indicates a BUS_GE_LINK_ERR
alarm.
l 17 indicates a BUS_EMIF alarm.
Parameter 2 indicates the sequence number
of the faulty bus.
Parameter 3 indicates a custom parameter.
TNW1EM20 l 0x0a 0x90 0x00: CPPI_GE_MAC.
l 0x0a 0x01 0x01: The active 40G service
bus is abnormal.
l 0x0a 0x01 0x02: The active 40G service
bus is abnormal.
l 0x0c 0x01 para[3]: The 1548 chip is
abnormal.
– para[3] indicates the ID of the
abnormal 1548 chip.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 156
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1EM10 l 0x01 0x01 0xff: The link between the
intra-board 8870 chip (CES service
processing chip) and the SD5890 chip
(packet service processing chip) is
abnormal. (The link error is reported on
the 8870 chip side.)
l 0x01 0x02 0xff: The TDM bus from the
cross-connect board in the smaller slot
(logical slot 51) to the service board is
abnormal.
l 0x01 0x03 0xff: The TDM bus from the
cross-connect board in the larger slot
(logical slot 61) to the service board is
abnormal.
l 0x0A 0x01 0x01: The status register of
the active 20G bus of the SD5890 chip is
abnormal.
l 0x0A 0x01 0x02: The status register of
the standby 20G bus of the SD5890 chip
is abnormal.
l 0x0C 0x01 0xff: The link between the
intra-board 8870 chip and the SD5890
chip is abnormal. (The link error is
reported on the SD5890 chip side.)
l 0x12 0xff 0x01: Both cross-connect
boards are abnormal.
l 0x12 0x02 0x01: The cross-connect board
in the smaller slot is the active board but
is offline.
l 0x12 0x03 0x01: The cross-connect board
in the larger slot is the active board but is
offline.
l 0x12 0x04 0x01: The active cross-
connect board on the NE is inconsistent
with that selected by the board.
TNW1HUND2, TNW1HUNS3 l 0x0a 0x90 0x00: CPPI_GE_MAC.
l 0x0a 0x01 0xff: The active 40G service
bus is abnormal.
l 0x0a 0x02 0xff: The standby 40G service
bus is abnormal.
l 0x0c 0x01 para[3]: An interlank bus is
abnormal.
– para[3] indicates the ID of the
abnormal interlank bus.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 157
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1UCXE (UXCE) l Parameter 1 indicates the board ID.
l Parameter 2 indicates the bus slot ID.
l Parameter 3 indicates a bus alarm.
l Parameter 4 indicates the bus type.
Impact on the System
The services that travel along the faulty bus are interrupted or have errors.
The BUS_ERR alarm triggers bus switching.
Possible Causes
Possible causes of the BUS_ERR alarm are as follows:
l The software version of the service board does not match the software version of the
cross-connect board.
l The active cross-connect board is configured with cross-connections but the standby
cross-connect board is not configured with cross-connections.
l The board is inserted in an incorrect slot or in poor contact with the backplane.
l The service board is faulty.
l The chip on the cross-connect board is faulty.
l The backplane bus from the service board to the cross-connect board is faulty.
Procedure
Step 1 Query the alarms on the U2000 and locate the cross-connect board that reports the BUS_ERR
alarm. Determine the service board used with the cross-connect board 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 alarmed cross-
connect board and the software version of the service board indicated by Parameter 1. Then,
check whether the software versions match.
If... Then...
The software versions are compatible Go to the next step.
The software versions do not match Upgrade the required software to a mapping
version. For details about how to upgrade
the required software, see the Upgrade
Guide.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
Step 3 Query the logic version and software version of the cross-connect board, and check whether
the software versions match.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 158
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The software versions match Go to the next step.
The software versions do not match Upgrade the required software to a mapping
version. For details about how to upgrade
the required software, see the Upgrade
Guide.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
Step 4 Check whether the service board indicated by Parameter 1 and the alarmed cross-connect
board are correctly inserted.
If... Then...
The cross-connect board is not inserted Insert the cross-connect board securely.
securely Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The cross-connect board is inserted securely Go to the next step.
Step 5 Reset (warm) the service board and then check whether the alarm is cleared.
If... Then...
The alarm persists Perform a cold reset on the service board or
replace it. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
NOTICE
If the services on the board are not protected, do
not reset (cold) or replace the board. Otherwise,
the services may be interrupted.
The alarm is cleared Go to the next step.
Step 6 Reset (warm) the alarmed cross-connect board and check whether the alarm is cleared.
If... Then...
The alarm persists Reset (cold) the alarmed cross-connect
board or replace it. Check whether the alarm
is cleared. If the alarm persists, go to the
next step.
NOTICE
If no functional standby cross-connect board is
available, do not perform the operation.
Otherwise, the services may be interrupted.
The alarm is cleared Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 159
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 7 Reset or replace the other cross-connect board and check whether the alarm is cleared.
If... Then...
The alarm persists Contact Huawei technical support engineers
to check whether the fault is caused by bent
pins on the backplane. If the backplane is
damaged, replace the backplane.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.47 BUS_LOC
Description
The BUS_LOC alarm indicates that the downstream bus clock on the tributary board is lost.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
Services are unavailable.
Possible Causes
The possible cause of this alarm is as follows:
The tributary board is faulty.
Procedure
Step 1 Perform a cold reset on the tributary board or reseat the tributary board.
Step 2 When the board is functioning properly, check on the U2000 whether the BUS_LOC alarm is
cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 160
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
If this alarm is cleared No further action is required.
If this alarm persists Go to the next step.
Step 3 The tributary board is faulty. Replace the faulty board.
Replacing the tributary board interrupts services. Exercise caution when performing this
operation. Before replacing the tributary board, ensure that the type of signals received by the
new tributary board is consistent with that of the tributary board to be replaced.
----End
Related Information
None.
4.2.48 BWUTILIZATION_OVER
Description
The BWUTILIZATION_OVER alarm indicates that bandwidth usage exceeds the threshold.
If traffic received or transmitted by monitored objects exceeds the traffic threshold and the
bandwidth usage exceeds the acceptable value, the BWUTILIZATION_OVER alarm is
reported.
Attribute
Alarm Severity Alarm Type
Warning QoS 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 161
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the direction in which the bandwidth utilization rate exceeds the
threshold.
l 0x00: indicates that the traffic in the receive direction exceeds the traffic
threshold.
l 0x01: indicates that the traffic in the transmit direction exceeds the traffic
threshold.
Impact on the System
When this alarm occurs, the network is congested.
Possible Causes
The possible causes of the BWUTILIZATION_OVER alarm are as follows:
l Cause 1: The traffic received or transmitted by a monitored object exceeds the traffic
threshold.
l Cause 2: The configured bandwidth usage threshold for a monitored object is low.
Procedure
Step 1 On the NMS, view alarm information to determine the alarm-reporting object.
Step 2 Check whether a network storm or a large amount of invalid data exists. If the preceding
problem exists, eliminate the source that creates a large amount of invalid data. Alternatively,
reduce the data traffic from the peer end by enabling flow control or configuring QoS.
Step 3 If the alarm persists, check whether the bandwidth threshold configured for the object is too
low. If the threshold is too low, expand network capacity.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.49 C2_VCAIS
Description
The C2_VCAIS is a C2 byte alarm indication. If a board has detected that the value of the
received C2 byte is all "1"s, the C2_VCAIS alarm is reported.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 162
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicates the slot number of the board where the alarm is
reported.
Parameter 3 Indicates the subboard number, Parameter 3 is always 0xFF.
Parameter 4 Indicates the optical port number of the board.
Parameter 5, Parameter 6 Indicates the path number.
Impact on the System
The services are interrupted.
Possible Causes
The possible causes of the C2_VCAIS alarm are as follows:
The value of the C2 byte to be transmitted is incorrectly configured at the remote end.
Procedure
Step 1 Confirm the VC path that reports the alarm according to the alarm parameters.
Step 2 Check whether the value of the C2 byte to be transmitted is correctly configured at the remote
end. If not, modify it, and then check whether the C2_VCAIS alarm is cleared.
Step 3 If the alarm persists, replace the transmit board at the remote end.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 163
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.50 C3794_SLOTNUM_ERR
Description
The actually received timeslot bandwidth of C37.94 services does not match the configured
timeslot bandwidth on the NMS.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of configured timeslots.
Parameter 2 Indicates the number of actually received timeslots.
Impact on the System
After the C3794_SLOTNUM_ERR alarm is generated, services are interrupted.
Possible Causes
The possible cause of this alarm is that the C37.94 service bandwidth is incorrectly
configured.
Procedure
Step 1 Correct the C37.94 service bandwidth configuration. In the Main Topology, right-click the
desired NE and choose NE Explorer. In the NE Explorer, click the board, choose
Configuration > PDH Interface, and then change the value of Number of C37.94 Timeslot.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 164
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.51 C3794_RDI
Description
The C3794_RDI alarm indicates that data reception of C37.94 services at the remote end fails.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
This alarm does not affect services at the local end, and data reception of services at the
remote end fails.
Possible Causes
Possible causes of this alarm are as follows:
l The opposite end receives the DDN_LFA or C3794_AIS alarm.
l The receive device at the opposite station is faulty.
l The transmit device at the local station is faulty.
Procedure
Step 1 Check whether the DDN_LFA or C3794_AIS alarm is reported on the board at the opposite
station.
If... Then...
The DDN_LFA or C3794_AIS alarm is Refer to the corresponding section in this
reported document to clear the DDN_LFA,
C3794_AIS. Then, check whether the
RELAY_LOF alarm is cleared. If the
RELAY_LOF alarm persists, go to the next
step.
NO DDN_LFA or C3794_AIS alarm is Go to the next step.
reported
Step 2 Perform a cold reset by using the NMS or directly reseat the receive board at the opposite end,
and check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 165
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the optical module or board. Then,
check whether the RELAY_LOF alarm is
cleared. If the RELAY_LOF alarm persists,
go to the next step.
The alarm is cleared No further action is required.
Step 3 Perform a cold reset by using the NMS or directly reseat the transmit board at the local end,
and check whether the alarm is cleared.
If... Then...
The alarm persists Replace the optical module or board. Then,
check whether the RELAY_LOF alarm is
cleared. If the RELAY_LOF alarm persists,
go to the next step.
The alarm is cleared No further action is required.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.52 C3794_AIS
Description
The C3794_AIS alarm indicates that C37.94 services are faulty.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
After the C3794_AIS alarm is generated, services are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 166
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l Higher-level alarms, such as T_ALOS and DDN_LFA, occur in the system.
l The cross-connect and timing board at the opposite station is faulty.
l The transmit device of the opposite station is faulty.
l The receive device of the local station is faulty.
Procedure
Step 1 Check whether the T_ALOS or DDN_LFA alarm is reported on the board at the local station.
If... Then...
The T_ALOS or DDN_LFA alarm is Refer to the corresponding section in this
reported document to clear the T_ALOS,
DDN_LFA. Then, check whether the
C3794_AIS alarm is cleared. If the
C3794_AIS alarm persists, go to the next
step.
No T_ALOS or DDN_LFA alarm is Go to the next step.
reported
Step 2 Replace the system control, cross-connect, and timing board at the opposite end and check
whether the alarm is cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 3 Perform a cold reset by using the NMS or directly reseat the transmit board at the opposite
end, and check whether the alarm is cleared.
If... Then...
The alarm persists Replace the optical module or board. Then,
check whether the C3794_AIS alarm is
cleared. If the C3794_AIS alarm persists, go
to the next step.
The alarm is cleared No further action is required.
Step 4 Perform a cold reset by using the NMS or directly reseat the receive board at the local end,
and check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 167
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the optical module or board. Then,
check whether the C3794_AIS alarm is
cleared. If the C3794_AIS alarm persists, go
to the next step.
The alarm is cleared No further action is required.
Step 5 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.53 CES_ACR_LOCK_ABN
Description
The CES_ACR_LOCK_ABN alarm indicates that a configured CES ACR clock is not
working in trace mode or is working in trace mode but is not locked to the reference clock
source.
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicate the PW index, which is the ID of the PW that is bound with the
ACR clock.
Parameter 5 Indicates the clock mode.
l 0x01: trace
l 0x02: holdover
l 0x03: free-run
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 168
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 6 Indicates whether the clock is locked to the reference clock source.
0x00: unlocked
Impact on the System
The service quality is affected.
Possible Causes
Possible causes of the CES_ACR_LOCK_ABN alarm are as follows:
l The CES ACR-associated service is unavailable or a CES service alarm is reported.
l The network is unstable.
l NEs on the alarmed CES service path are malfunctioning.
Procedure
Step 1 Check whether the CES ACR-associated service is unavailable or whether any CES service
alarms, such as CES_MISORDERPKT_EXC, are reported. If a CES service alarm is
reported, handle it first and then check whether the CES_ACR_LOCK_ABN alarm is cleared.
If... Then...
The CES_ACR_LOCK_ABN alarm is cleared No further action is required.
The CES_ACR_LOCK_ABN alarm persists Go to the next step.
Step 2 Query the service performance count and check whether any jitter or delay events occur on
the network. Analyze the network based on the service performance data. If the network is
unstable, rectify the faults on the network, or switch the service carrying the CES ACR clock
to a stable network. Check whether the CES_ACR_LOCK_ABN alarm is cleared.
If... Then...
The CES_ACR_LOCK_ABN alarm is cleared No further action is required.
The CES_ACR_LOCK_ABN alarm persists Go to the next step.
Step 3 Query the QoS settings, traffic count, and alarms on the service path. Check whether the QoS
settings are incorrect and the network traffic is abnormal. If yes, optimize the QoS settings
based on the actual network and ensure that the network traffic is normal. Check whether the
CES_ACR_LOCK_ABN alarm is cleared.
If... Then...
The CES_ACR_LOCK_ABN alarm is cleared No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 169
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The CES_ACR_LOCK_ABN alarm persists Go to the next step.
Step 4 Check whether any NEs on the CES service path and service processing boards are
malfunctioning. After ensuring that the NEs and the service processing boards are normal,
check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.54 CES_APS_INDI
Description
The CES_APS_INDI alarm indicates that the configured packet MSP for a CES service is in
the switching state.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
l Automatic protection switching or switching triggered by an external command occurs.
As a result, services are switched to the protection channel for transmission.
l This alarm does not affect services. If the protection channel fails at this time, the
services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: An external command is issued to trigger switching (such as manual switching,
forced switching, exercise switching, or lockout of switching).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 170
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 2: An alarm, such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD, or a
cold reset that triggers automatic MSP switching occurs.
l Cause 4: The MSP attributes are incorrectly configured.
l Cause 4: A certain service board is faulty.
l Cause 5: A certain cross-connect board is faulty.
Procedure
Step 1 Cause 1: An external command is issued to trigger switching (such as manual switching,
forced switching, exercise switching, or lockout of switching).
1. Check the switching status of the MSP group.
If... Then...
The MSP group is in the state of Clear the switching state. Check whether
manual switching, forced switching, or the CES_APS_INDI alarm is cleared. If
exercise switching the alarm persists, go to Step 2.
The MSP group is not in any of the Go to Step 2.
preceding switching states
Step 2 Cause 2: An alarm, such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD, or a cold
reset that triggers automatic MSP switching occurs.
1. Check whether the MSP group is in the automatic switching state.
If... Then...
The local NE reports the R_LOS, Clear the switching state. Check whether
R_LOF, MS_AIS, or B2_EXC alarm the CES_APS_INDI alarm is cleared. If
the alarm persists, go to Step 2.
The local NE reports the B2_SD alarm After you enable the SD switching
NOTE condition, SD associated alarms can
The automatic MSP switching conditions trigger MSP switching. You can use any
include the SF condition and SD condition. of the following methods to clear the
By default, the B2_SD alarm is not a B2_SD alarm.
trigger condition of MSP switching, but
you can select SD Enable. – Disable the SD switching condition.
– Clear the B2_SD alarm.
Check whether the CES_APS_INDI
alarm is cleared. If the alarm persists, go
to the next step.
The MSP group is not in any of the Go to the next step.
preceding switching states
2. Wait for MSP switching to restore automatically to the normal state, and check whether
the CES_APS_INDI alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 4: The MSP attributes are incorrectly configured.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 171
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. Check whether packet MSP configurations at the local and opposite NEs, such as the
protocol parameter and mapping unit, are correct. If any configurations are incorrect,
rectify them and deliver correct configurations.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: A certain service board is faulty.
1. Check whether the local and opposite service boards on which MSP is configured are
functional.
2. If any of them is faulty, replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Cause 5: A certain cross-connect board is faulty.
1. Check whether the local and opposite cross-connect boards are functional.
2. If any of them is faulty, replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.55 CES_APS_MANUAL_STOP
Description
The CES_APS_MANUAL_STOP alarm indicates that the packet linear MSP protocol is
stopped manually.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
The packet linear MSP protocol is stopped and MSP fails. As a result, channelized STM-1
services cannot be protected.
Possible Causes
The possible cause of this alarm is as follows:
Cause: The APS protocol for the alarmed protection group is manually stopped.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 172
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Cause: The APS protocol for the alarmed protection group is manually stopped.
1. Determine the ID of the MSP group whose APS protocol is stopped.
2. Restart the MSP protocol for the MSP group.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.56 CES_JTROVR_EXC
Description
The CES_JTROVR_EXC alarm indicates that the average number of overflows per second in
the jitter buffer is larger than the upper threshold value in a period. If the average number of
overflows per second is smaller than the lower threshold value in another period, this alarm is
cleared automatically.
NOTE
Overflows occur when the jitter buffer is full and can no longer receive service packets; as a result,
packet loss occurs.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The buffer does not have enough space for received frames and therefore frames are lost.
Possible Causes
Possible causes of the CES_JTROVR_EXC alarm are as follows:
l The buffer size configured for the CES service is small.
l At the opposite end, the service frame format is different from the frame format allowed
by the port.
l Clocks are not synchronous.
l A large number of hops are deployed on the network side, which intensifies the jitter.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 173
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Query the configured buffer size. According to the network plan, check whether Jitter
Compensation Buffering Time can be set to a larger value.
Step 2 If yes, set Jitter Compensation Buffering Time to a larger value to expand the buffer. Then,
check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Check whether the frame format of the service received at the opposite end is the same as the
frame format configured at the opposite port. If the frame formats are different, change the
frame format configured at the opposite port to the same as the frame format of the service
received at the opposite end.
Step 4 Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Check whether the LTI alarm or other clock-related alarms are generated on the alarmed NE.
If such alarms are reported, clocks are not synchronous and the incoming rate of the buffer is
far higher than the outgoing rate of the buffer.
Step 6 If yes, clear the LTI alarm and other clock-related alarms first and then check whether the
CES_JTROVR_EXC alarm is cleared. If the CES_JTROVR_EXC alarm persists, go to Step
7.
NOTE
If a large number of hops are deployed on the network side, the CES jitter may increase. In addition,
severe jitter causes unbalanced network traffic. If a large number of burst packets are transmitted, the
jitter buffer cannot receive all these packets and therefore overflows.
Step 7 According to the network plan, check whether the number of hops on the network side can be
decreased.
Step 8 If yes, decrease the number of hops on the network side. Then, check whether the
CES_JTROVR_EXC alarm is cleared. If the CES_JTROVR_EXC alarm persists, contact
Huawei technical support engineers to handle the alarm.
----End
Related Information
When the delay for an NNI port to receive CES packets is unstable, the percent of the
CESoETH frames overflowing from the jitter buffer exceeds the specified percent threshold.
As a result, the jitter buffer overflows. If the percent of the CESoETH frames overflowing
from the jitter buffer is larger than the specified percent threshold within a certain period, the
average number of overflows in a second becomes larger than the upper percent threshold.
The CES_JTROVR_EXC alarm is then reported.
4.2.57 CES_JTRUDR_EXC
Description
The CES_JTRUDR_EXC alarm indicates that the average number of underflows per second
in the jitter buffer is larger than the upper threshold value in a period. If the average number
of underflows per second is smaller than the lower threshold value in another period, this
alarm is cleared automatically.
NOTE
Underflows occur when the jitter buffer does not have packets to be transmitted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 174
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
No packet will be transmitted from the buffer and therefore the buffer underflows. As a result,
service transmission is affected.
Possible Causes
Possible causes of the CES_JTRUDR_EXC alarm are as follows:
l Clocks are not synchronous.
l A service loop is formed.
l The network is congested.
l Link signals deteriorate or are interrupted due to a fault in cables, optical fibers, or
optical modules.
Procedure
Step 1 Check whether the LTI alarm or other clock-related alarms are generated on the alarmed NE.
If such alarms are reported, clocks are not synchronous and the incoming rate of the buffer is
far lower than the outgoing rate of the buffer.
Step 2 If the LTI alarm and other clock-related alarms are reported, clear the alarms first and then
check whether the CES_JTRUDR_EXC alarm is cleared. If the CES_JTRUDR_EXC alarm
persists, go to Step 3.
Step 3 If service packets are looped back at the local end, the NE at the opposite end cannot receive
packets. In this case, the NE at the opposite end reports an underflow alarm and the NE at the
local end reports a loopback alarm. Check whether the services at the local end are configured
into a loop. If yes, change the service configurations.
Step 4 Check whether the CES_JTRUDR_EXC alarm is cleared. If the CES_JTRUDR_EXC alarm
persists, go to Step 5.
Step 5 If heavy traffic on the local port causes network congestion, packets are lost. As a result, the
NE at the opposite end cannot receive packets and reports an underflow alarm. Check whether
the local port is fully loaded with traffic.
Step 6 If network congestion occurs, find out the source that transmits a large amount of data and
adjust the traffic allocation on the ports. Then, check whether the CES_JTRUDR_EXC alarm
is cleared.
Step 7 If the CES_JTRUDR_EXC alarm persists, go to Step 8.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 175
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 8 Check whether cables or optical fibers are incorrectly connected to the ports and whether the
ports are dirty.
Step 9 If the cables or optical fibers are incorrectly connected, reconnect the cables or optical fibers.
Step 10 Check whether the CES_JTRUDR_EXC alarm is cleared. If the CES_JTRUDR_EXC alarm
persists, replace the cables, optical cables, or optical modules/boards.
Step 11 Check whether the CES_JTRUDR_EXC alarm is cleared. If the CES_JTRUDR_EXC alarm
persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
When the delay for an NNI port to receive CES packets is unstable, the percent of the
CESoETH frames underflowing from the jitter buffer exceeds the specified percent threshold.
As a result, the jitter buffer underflows. If the percent of the CESoETH frames underflowing
from the jitter buffer is larger than the specified percent threshold within a certain period, the
average number of underflows in a second becomes larger than the upper percent threshold.
The CES_JTRUDR_EXC alarm is then reported.
4.2.58 CES_K1_K2_M
Description
The CES_K1_K2_M alarm indicates the mismatch between the K1 byte and the K2 byte.
This alarm is reported when the channel numbers indicated in the transmitted K1 byte and the
received K2 byte are inconsistent and the inconsistency lasts for a period of time (160 ms by
default).
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
Packet MSP fails. If a fiber cut or other fault occurs at this time, services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The packet MSP types at the local and opposite ends are different.
l Cause 2: Fiber connections are incorrect.
l Cause 3: A certain service board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 176
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 4: A certain cross-connect board is faulty.
Procedure
Step 1 Cause 1: The packet MSP types at the local and opposite ends are different.
1. Check whether the packet MSP is consistently configured at the local and opposite ends.
If 1+1 protection is configured at one end and 1: N protection is configured at the other
end, the CES_K1_K2_M alarm is reported
2. Configure 1: N MSP at both ends, and check whether the CES_K1_K2_M alarm is
cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: Fiber connections are incorrect.
1. Verify that the optical fibers on the multiplex section are properly connected and that the
logical fiber configuration is the same as the physical fiber connection.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A certain service board is faulty.
1. Check whether the local and opposite service boards on which MSP is configured are
functional.
2. If any of them is faulty, replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: A certain cross-connect board is faulty.
1. Check whether the local and opposite cross-connect boards are functional.
2. If any of them is faulty, replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.59 CES_K2_M
Description
The CES_K2_M alarm indicates that a mismatched K2 byte of packet MSP is detected. This
alarm is reported when the protection mode used on the opposite NE, which is indicated by
bit 5 of the received K2 byte, is different from that used on the local NE for a period of time
(2s by default).
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 177
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
Packet MSP fails. If a fiber cut or other fault occurs at this time, services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The packet MSP configurations are incorrect.
l Cause 2: A certain service board is faulty.
l Cause 3: A certain cross-connect board is faulty.
Procedure
Step 1 Cause 1: The packet MSP configurations are incorrect.
1. Verify that the packet MSP configurations at the local and opposite ends are consistent.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: A certain service board is faulty.
1. Check whether the local and opposite service boards on which MSP is configured are
functional.
2. If any of them is faulty, replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A certain cross-connect board is faulty.
1. Check whether the local and opposite cross-connect boards are functional.
2. If any of them is faulty, replace the faulty board.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.60 CES_LOSPKT_EXC
Description
The CES_LOSPKT_EXC alarm indicates that the average number of lost packets exceeds the
upper threshold value within one second in a period. If the average number of lost packets in a
second is smaller than the lower threshold value in another period, this alarm is cleared
automatically.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 178
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When the packet loss rate exceeds the threshold value, all "1"s are inserted in the downstream.
As a result, services are interrupted.
Possible Causes
Possible causes of the CES_LOSPKT_EXC alarm are as follows:
l The parameter settings for the NEs at both ends of the CES service are inconsistent.
l The bandwidth configured for the tunnel or PW is so low that the link is congested.
l The link signals deteriorate or are interrupted due to a fault in cables, optical fibers, or
optical modules.
Procedure
Step 1 Check whether the parameter settings (for example, 64K Timeslot) are consistent on the NEs
at the local and opposite ends of the CES service.
Step 2 If the parameters settings are inconsistent at both ends, change the parameters settings to be
the same and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Check whether the bandwidth configured for the tunnel or PW which carries the CES service
is too low.
Step 4 If the bandwidth configured for the tunnel or PW which carries the CES service is too low,
allocate the tunnel or PW higher bandwidth. Then, check whether the alarm is cleared. If the
alarm persists, go to Step 5.
Step 5 Check whether cables or optical fibers are incorrectly connected to the ports and whether the
ports are dirty.
Step 6 If the cables or optical fibers are incorrectly connected, reconnect the cables or optical fibers.
Step 7 Check whether the alarm is cleared. If the alarm persists, replace the cables, optical cables, or
optical modules/boards.
Step 8 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 179
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.61 CES_MALPKT_EXC
Description
The CES_MALPKT_EXC alarm indicates that the number of deformed CES service packets
exceeds the specified threshold in a certain period. If a CESoPSN packet contains valid TDM
data and does not contain any error indication, but the size of the CESoPSN packet is
inconsistent with the specified size, this packet is considered as a deformed CESoPSN packet.
If the average number of deformed packets exceeds the upper threshold value within one
second in a specific period, this alarm is reported. If the average number of deformed packets
in a second is smaller than the lower threshold value in another period, this alarm is cleared
automatically.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
A deformed packet is discarded once it is detected. As a result, the packet loss rate increases.
Possible Causes
Possible causes of the CES_MALPKT_EXC alarm are as follows:
l The CES service configuration data is incorrect.
l The bandwidth configured for the tunnel or PW is so low that the link is congested.
l The link signals deteriorate or are interrupted due to a fault in cables, optical fibers, or
optical modules.
Procedure
Step 1 Check whether the CES service parameters are set correctly, such as Higher Order Path.
Step 2 If parameters of the CES service are set incorrectly, change the parameters to correct values
and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Check whether the bandwidth configured for the tunnel or PW which carries the CES service
is too low.
Step 4 If the bandwidth configured for the tunnel or PW which carries the CES service is too low,
allocate the tunnel or PW higher bandwidth. Then, check whether the alarm is cleared. If the
alarm persists, go to Step 5.
Step 5 Check whether cables or optical fibers are incorrectly connected to the ports and whether the
ports are dirty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 180
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 6 If the cables or optical fibers are incorrectly connected, reconnect the cables or optical fibers.
If the ports are dirty, clean the ports.
Step 7 Check whether the alarm is cleared. If the alarm persists, replace the cables, optical cables, or
optical modules/boards.
Step 8 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.62 CES_MISORDERPKT_EXC
Description
The CES_MISORDERPKT_EXC alarm indicates that the average number of lost out-of-
order packets exceeds the upper threshold value within one second, this alarm is reported. If
the average number of out-of-order packets in a second is smaller than the lower threshold
value in another period, this alarm is cleared automatically.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
An NNI port detects out-of-order packets and the packet loss rate is too high.
Possible Causes
Possible causes of the CES_MISORDERPKT_EXC alarm are as follows:
l The bandwidth configured for the tunnel or PW is so low that the link is congested.
l Clocks are not synchronous.
l The link signals deteriorate or are interrupted due to a fault in cables, optical fibers, or
optical modules.
Procedure
Step 1 Check whether the bandwidth configured for the tunnel or PW which carries the CES service
is too low.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 181
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 If the bandwidth configured for the tunnel or PW which carries the CES service is too low,
allocate the tunnel or PW higher bandwidth. Then, check whether the alarm is cleared. If the
alarm persists, go to Step 3.
Step 3 Check whether the LTI alarm or other clock-related alarms are reported on the NE. If such
alarms are reported, the clocks are not synchronous and the ingress rate of the buffer is
different from the egress rate of the buffer.
Step 4 Clear the LTI alarm and other clock-related alarms first, and then check whether the
CES_MISORDERPKT_EXC alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Check whether cables or optical fibers are incorrectly connected to the ports and whether the
ports are dirty.
Step 6 If the cables or optical fibers are incorrectly connected, reconnect the cables or optical fibers.
If the ports are dirty, clean the ports.
Step 7 Check whether the alarm is cleared. If the alarm persists, replace the cables, optical cables, or
optical modules/boards.
Step 8 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.63 CES_RDI
Description
The CES_RDI alarm indicates a failure in remote CES services. Upon detecting a fault in
CES services, the opposite end sets the R bit in control word to 1 and returns the RDI signal
to the local end. Upon receiving the RDI signal, the local end reports the CES_RDI alarm.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
When this alarm is reported, it indicates that excessive packets are lost at the opposite end.
Possible Causes
Possible causes of the CES_RDI alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 182
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The opposite end receives the LOS, LOF, or AIS signal.
l The opposite receive board is faulty.
l The local transmit board is faulty.
Procedure
Step 1 Check whether the opposite end reports the R_LOS, R_LOF, or MS_AIS alarm.
If... Then...
The R_LOS, R_LOF, or MS_AIS alarm is Clear these alarms first. Check whether the
reported alarm is cleared. If the alarm persists, go to
the next step.
The R_LOS, R_LOF, or MS_AIS alarm is Go to the next step.
not reported
Step 2 Perform a cold reset for the opposite receive board by using the U2000 or reseat the opposite
receive board. Check whether the alarm is cleared.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 3 Replace the opposite receive board and check whether the alarm is cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 4 Perform a cold reset for the local transmit board by using the U2000 or reseat the local
transmit board. Check whether the alarm is cleared.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 183
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 5 Replace the local transmit board and check whether the alarm is cleared.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
The alarm is cleared No further action is required.
----End
Related Information
4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS
4.2.64 CES_STRAYPKT_EXC
Description
The CES_STRAYPKT_EXC alarm indicates that the average number of error packets
exceeds the upper threshold value within one second, this alarm is reported. If the average
number of error packets in a second is smaller than the lower threshold value in another
period, this alarm is cleared automatically.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
After detecting a packet that does not belong to the CES service, the NNI port discards the
packet. As a result, the packet loss rate is too high.
Possible Causes
Possible causes of the CES_STRAYPKT_EXC alarm are as follows:
l The parameter settings for the NEs at both ends of the CES service are inconsistent.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 184
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The physical link is connected incorrectly.
Procedure
Step 1 Check whether the parameter settings (for example, 64K Timeslot) are consistent on the NEs
at the local and opposite ends of the CES service.
Step 2 If the parameters settings are inconsistent at both ends, change the parameters settings to be
the same and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Check whether the optical fibers or cables are correctly connected between both ends. If the
optical fibers or cables are incorrectly connected between both ends, rectify the fiber/cable
connections or change the service configurations.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.65 CESPW_OPPOSITE_ACFAULT
Description
The CESPW_OPPOSITE_ACFAULT is a defect indication in an attachment circuit. After
detecting a fault in the attachment circuit, the opposite end sets bit L in the control byte to "1"
and sends the control byte to the local end. After detecting bit L sent from the opposite end,
the local end reports the CESPW_OPPOSITE_ACFAULT alarm.
NOTE
The attachment circuit is the circuit connected to the UNI side of the NE at the opposite end.
Attribute
Alarm Severity Alarm Type
Major Communication
Parameters
None.
Impact on the System
The services on the attachment circuit are interrupted at the opposite end.
Possible Causes
The possible cause of the CESPW_OPPOSITE_ACFAULT alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 185
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
The attachment circuit is fault at the opposite end and the LOS/LOF/AIS signal is generated.
Procedure
Step 1 Check whether alarms such as R_LOS, R_LOF, MS_AIS, T_ALOS, UP_E1_AIS, LFA, or
LMFA are reported on the NE at the opposite end.
If... Then...
Alarms such as R_LOS, Handle the alarms first. Check whether the
R_LOF, MS_AIS, T_ALOS, CESPW_OPPOSITE_ACFAULT alarm is cleared. If the
UP_E1_AIS, LFA, or LMFA CESPW_OPPOSITE_ACFAULT alarm persists, go to
are reported the next step.
Alarms such as R_LOS, Contact Huawei technical support engineers to handle
R_LOF, MS_AIS, T_ALOS, the CESPW_OPPOSITE_ACFAULT alarm.
UP_E1_AIS, LFA, or LMFA
are not reported
----End
Related Information
R_LOS, R_LOF, MS_AIS, T_ALOS, UP_E1_AIS, LFA, LMFA
4.2.66 CESPW_OPPOSITE_RAI
Description
The CESPW_OPPOSITE_RAI is an alarm indication of the NE at the opposite end. After
receiving the RAI alarm, the NE at the opposite end sets bit L in the control byte to "0" and
bit M in the control byte to "10" and sends the control byte to the NE at the local end. After
detecting the control byte sent from the opposite end, the NE at the local end reports the
CESPW_OPPOSITE_RAI alarm.
Attribute
Alarm Severity Alarm Type
Major Communication
Parameters
None.
Impact on the System
Upstream and downstream services are interrupted on the NE at the opposite end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 186
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of the CESPW_OPPOSITE_RAI alarm is as follows:
The RAI alarm is reported at the opposite end.
Procedure
Step 1 Clear the ALM_E1RAI alarm at the opposite end and check whether the
CESPW_OPPOSITE_RAI alarm is cleared.
If... Then...
The alarm is cleared No further operation is required.
The alarm persists Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.67 CFCARD_FAILED
Description
The CFCARD_FAILED alarm indicates that an operation on the CF card fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameters 1 0x01: Creating the file system fails.
Impact on the System
This alarm does not have any impact on the system. Operations on the CF card cannot be
successfully performed.
Possible Causes
Possible causes of this alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 187
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Creating the file system of the CF card fails.
l The file system of the CF card does not match.
l The CF card hardware fails to initialize.
Procedure
Step 1 On the U2000, check whether the CFCARD_FAILED alarm is reported.
If... Then...
The alarm is reported Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists,
contact Huawei technical support personnel
to handle the alarm.
The alarm is not reported No further action is required.
----End
Related Information
None.
4.2.68 CFCARD_FULL
Description
The CFCARD_FULL alarm indicates that the capacity of the CF card is used up.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the slot number of the board that reports the
Parameter 2 CFCARD_FULL alarm.
Parameter 3 Indicates the number of the CF card.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 188
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 Indicates the partition number of the CF card. If the bit is 1, this alarm
has been generated in this partition. If the bit is 0, this alarm has not
been generated in this partition.
l Bit (0) corresponds to SFS1.
l Bit (1) corresponds to SFS2.
l Bit (2) corresponds to SFS3.
NOTE
Bit (0) is the least significant bit.
Parameter 5 Reserved.
Impact on the System
This alarm does not have any impact on services.
Possible Causes
The possible cause of this alarm is as follows:
The used capacity of the CF card partition crosses the threshold, which is 80% of the partition
capacity.
Procedure
Step 1 On the U2000, check whether the CFCARD_FULL alarm is reported.
If... Then...
The alarm is reported Delete unnecessary files from the CF card.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The alarm is not reported No further action is required.
Step 2 Replace the CF card with one of a larger capacity.
----End
Related Information
None.
4.2.69 CFCARD_OFFLINE
Description
The CFCARD_OFFLINE alarm indicates that the CF card is offline.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 189
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The database cannot be backed up to the CF card or be restored from the CF card. This alarm
may cause rollback of the upgrade implemented by loading the software package.
Possible Causes
Possible causes of this alarm are as follows:
l The CF card is not installed.
l The CF card is in poor contact with the system control, cross-connect, and timing board.
l The CF card is faulty.
l The system control unit is faulty.
Procedure
Step 1 Check whether the CF card is installed.
If... Then...
The CF card is not installed Install the CF card. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The CF card is installed Go to the next step.
Step 2 Check whether the CF card is in poor contact with the system control, cross-connect, and
timing board.
If... Then...
The CF card is in poor contact with the Install the CF card correctly. Then, check
system control, cross-connect, and timing whether the alarm is cleared. If the alarm
board persists, go to the next step.
The CF card is in good contact with the Go to the next step.
system control, cross-connect, and timing
board
Step 3 Check whether the system control unit reports any hardware alarms, such as 4.2.157
HARD_BAD.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 190
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The system control unit reports a hardware Perform a cold reset on the system control,
alarm cross-connect, and timing board or replace
the board. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The system control unit does not report any Contact Huawei technical support engineers
hardware alarms to handle the alarm.
----End
Related Information
None.
4.2.70 CFG_DATACHECK_FAIL
Description
The CFG_DATACHECK_FAIL alarm indicates an error in routine database check. An
operating NE regularly checks its database. This alarm is reported from a system control
board when routine database check fails.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1,
Indicate the slot ID of the board on which routine database check fails.
Parameter 2
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 191
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the cause for the database check failure.
l 0x01 (10-min routine check error type 1): indicates a failure to check
basic NE configuration data.
l 0x02 (10-min routine check error type 2): indicates a failure to check
database configuration information.
l 0x03 (10-min routine check error type 3): indicates a database
restoration failure.
l 0x04 (10-min routine check error type 4): indicates a database check
failure.
l 0x05: indicates a database check failure on the standby board.
l 0x06: indicates a failure in real-time retransmission database check on
the standby board.
l 0x07: indicates a failure in batch backup database check on the active
board.
Parameter 4,
The value is always 0xFF, and this parameter is meaningless.
Parameter 5
Impact on the System
Configuration data of existing services is lost, or the database is damaged.
Possible Causes
The possible cause of the CFG_DATACHECK_FAIL alarm is as follows:
l An error occurs during routine database check.
l A database check failure on the standby board.
l A failure in real-time retransmission database check on the standby board.
l A failure in batch backup database check on the active board.
Procedure
Step 1 When the alarm is reported, back up the faulty database for fault diagnosis. For details, see
Backing Up the NE Database Manually in the Supporting Tasks. You can contact Huawei
technical support engineers to analyze the faulty database.
Step 2 Obtain the latest normal back-up database files, deliver service configurations, and end the
alarm handling. For details, see Restoring the Database of the NE in the Supporting Tasks.
NOTE
The delivered service configurations are different from real services because the databases are not
backed up in real time. To restore the services before the fault occurs, configure the affected services.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 192
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.71 CFG_DATASAVE_FAIL
Description
The CFG_DATASAVE_FAIL alarm indicates a data save failure. This alarm is reported from
a system control board when the database fails to save configuration data.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1,
Indicate the slot ID of the board that fails to save data into the database.
Parameter 2
Parameter 3 Indicates the cause for the data save failure.
l 0x01: The database fails to save non-transaction configuration data.
l 0x02: The database fails to save transaction configuration data.
l 0x03: Operating the database fails when a system control board
delivers all configuration data to a board.
Parameter 4,
The value is always 0xFF, and this parameter is meaningless.
Parameter 5
Impact on the System
Configuration data of existing services may be lost, or the database may be damaged.
Possible Causes
The possible cause of the CFG_DATASAVE_FAIL alarm is as follows:
The database fails to save configuration data.
Procedure
Step 1 When the alarm is reported, back up the faulty database for fault diagnosis. For details, see
Backing Up the NE Database Manually in the Supporting Tasks. You can contact Huawei
technical support engineers to analyze the faulty database.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 193
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Obtain the latest normal back-up database files, deliver service configurations, and end the
alarm handling. For details, see Restoring the Database of the NE in the Supporting Tasks.
NOTE
The delivered service configurations are different from real services because the databases are not
backed up in real time. To restore the services before the fault occurs, configure the affected services.
----End
Related Information
None.
4.2.72 CHCS
Description
The CHCS alarm indicates that a correctable bit error occurs in the cell header.
NOTE
The CHCS alarm cannot be detected at a VC-12 VCTRUNK port.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
Services are not affected. This alarm only indicates that some cells with bit errors are detected
during port cell delimitation.
Possible Causes
Possible causes of the CHCS alarm are as follows:
l Bit errors occur in the SDH service receive path connected to the alarmed ATM port
where the alarm is reported. That is, alarms such as B1_SD, B2_SD, or B3_SD, occur in
the SDH service receive path connected to the alarmed ATM port.
l The ATM processing chip on the alarmed board is faulty.
Procedure
Step 1 On the U2000, check whether the SDH service receive path reports alarms indicating
excessive bit errors, such as B1_SD, B2_SD, and B3_SD.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 194
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Such alarms are reported Clear these alarms and check whether the
CHCS alarm is cleared. If the CHCS alarm
persists, go to the next step.
No such alarms are reported Go to the next step.
Step 2 Reset (cold) or reseat the board that reports the CHCS alarm, and then check whether the
CHCS alarm is cleared.
If... Then...
The CHCS alarm persists Go to the next step.
The CHCS alarm is cleared. No further operation is required.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
Step 3 Optional: Replace the board that reports the CHCS alarm, and then check whether the CHCS
alarm is cleared. If the CHCS alarm persists, contact Huawei technical support engineers to
handle the alarm.
NOTE
The CHCS alarm does not affect services but resetting (cold) or replacing the board interrupts the
services. Therefore, it is recommended that you do not perform reset (cold) or replace the board.
----End
Related Information
4.2.23 B1_SD, 4.2.25 B2_SD, 4.2.29 B3_SD
4.2.73 CHIP_ABN
Description
The CHIP_ABN alarm indicates a failure in the voltage chip or temperature chip.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 195
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the failed chip number.
l 0x01: failure in the temperature chip
l 0x02: failure in the voltage chip
Impact on the System
Services carried by the board are not affected.
Possible Causes
The possible cause of the CHIP_ABN alarm is as follows:
l The temperature chip on the board fails.
l The voltage chip on the board fails.
Procedure
Step 1 Check whether the equipment has another cross-connect board that is functioning properly. If
yes, perform a cold reset for the board that reports the CHIP_ABN alarm. After a successful
cold reset, check whether the alarm is cleared.
1. If yes, perform a cold reset for the board that reports the CHIP_ABN alarm. For details,
see Resetting Boards in Supporting Tasks. After a successful cold reset, check whether
the alarm is cleared.
2. If no, go to Step 2.
Step 2 If the alarm persists, replace the board. For details, see Parts Replacement.
----End
Related Information
None.
4.2.74 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL is an alarm indicating a failure to lock the clock. When the NE clock
frequency is synchronous with that of the upstream NE, the frequency is locked indicating
that the NE has traced the upstream NE successfully. This alarm is reported only when the
clock of the NE is unlocked.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 196
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The phase-locked loop (PLL) is in holdover or free-run mode.
l 0x02: The Sync timestamp remains unchanged when the Precision Time
Protocol (PTP) clock is synchronized.
l 0x03: The phase discrimination value per unit of time exceeds the upper
threshold.
Impact on the System
When this alarm occurs, the clock of the NE is unlocked and the NE clock cannot trace the
upstream NE clock so that bit errors occur in services.
Possible Causes
The possible causes of the CLK_LOCK_FAIL alarm are as follows:
l Cause 1: The clock source priority contains only internal clock sources when clocks are
synchronized at physical layer.
l Cause 2: The frequency deviation of the clock source exceeds the upper threshold when
clocks are synchronized at physical layer.
l Cause 3: A fault occurs on the physical links or optical modules of the clock source.
l Cause 4: The Sync timestamp remains unchanged because a fault occurs on the clock
board of the NE or upstream NE or IEEE 1588 service interface.
Procedure
Step 1 Cause 1: The clock source priority contains only internal clock sources when clocks are
synchronized at physical layer.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 197
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The clock source priority table contains Configure the clock source priority table
only internal clock sources again to contain other available clock
sources. Check whether the alarm is cleared.
If the alarm persists, go to Step 2.
The clock source priority table contains 1. Check whether the 4.2.465
other available clock sources SYNC_C_LOS alarm occurs. If this
alarm occurs, clear it first. Check
whether the CLK_LOCK_FAIL alarm is
cleared. If the alarm persists, go to the
next step.
2. Check whether the SSM protocol is
enabled on the NE and its upstream NE.
If not, enable the SSM protocol.
3. Check whether the alarm is cleared. If
the alarm persists, go to Step 2.
Step 2 Cause 2: The frequency deviation of the clock source exceeds the upper threshold when
clocks are synchronized at physical layer.
1. On the NMS, check whether the bit error alarm or other performance events are reported.
If yes, clear them first. Then, check whether the CLK_LOCK_FAIL alarm is cleared.
2. If the alarm persists, check whether the NE is tracing an external clock source.
– If yes, check whether signals of the clock source is normal. If the signal is
abnormal, switch the clock source to another one. Then, check whether the alarm is
cleared. If the alarm persists, go to the next step.
– If the NE is tracing a line clock source, go to the next step.
3. Check whether the clock is configured correctly. If not, modify the configurations. Then,
check whether the alarm is cleared.
4. If the alarm persists, check whether the clock board is faulty. If yes, replace the clock
board.
5. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A fault occurs on the physical links or optical modules of the clock source.
1. Check whether the 4.2.131 ETH_LOS or 4.2.177 IN_PWR_ABN alarm is reported. If
yes, clear it first.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The Sync timestamp remains unchanged because a fault occurs on the clock board of
the NE or upstream NE or IEEE 1588 service interface.
1. Check whether alarms related to hardware, such as 4.2.157 HARD_BAD, are reported
by the clock board of the NE or its upstream NE or the IEEE 1588 service interface
board. If yes, clear them immediately.
2. Then, check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 198
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.75 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE alarm indicates that the clock changes to the non-tracing
running state. This alarm is generated when the current clock does not trace any line clock
source, tributary clock source, or external clock source.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the path ID.
Parameter 2
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.
Impact on the System
The system clock is of poor quality. When the poor-quality clock results in the out-of-
synchronization status among NEs, the bit error rate of services increases.
Possible Causes
Possible causes of this alarm are as follows:
l A system priority table is not manually configured, and NEs use their own default
priority tables.
l A system priority table is configured, but only the internal clock source in the priority
table can be traced.
Procedure
Step 1 Query the system priority table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 199
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The system priority table contains only the Add other available clock sources to the
internal clock source system priority table. The alarm is
automatically cleared.
The system priority table contains the Find out why other clock sources cannot be
internal clock source and other available traced. Go to the next step.
clock sources
NOTE
If other clock sources cannot be traced, the common causes are as follows:
1. The existence status of other clock source is lost.
2. The SSM protocol is enabled on the local NE but is disabled on the upstream NE.
Step 2 Optional: If existence status of other clock source is lost, the system reports the
SYNC_C_LOS alarm. Clear the SYNC_C_LOS alarm. The system can trace any other clock
source except the internal clock source. The CLK_NO_TRACE_MODE alarm is
automatically cleared.
Step 3 Optional: If the SSM protocol is enabled on the local NE but is disabled on the upstream NE,
enable the SSM protocol on the upstream NE. The system can trace any other clock source
except the internal clock source. The CLK_NO_TRACE_MODE alarm is automatically
cleared.
----End
Related Information
4.2.465 SYNC_C_LOS
4.2.76 COM_EXTECC_FULL
Description
The COM_EXTECC_FULL is an alarm that indicates the excessive number of TCP
connections between the NEs running the automatic extended ECC communication protocol.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 200
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 to parameter 5 The fixed value is 0x00. This value is meaningless.
Impact on the System
The extended ECC is configured to work in automatic mode. As a result, lots of Bandwidth
resources are consumed, and the NE performance is impacted.
Possible Causes
The possible causes of the COM_EXTECC_FULL alarm include:
More than four TCP connections exist between the NEs running the automatic extended ECC
communication protocol.
Procedure
Step 1 Check the COM_EXTECC_FULL alarm on the NMS. Set the ECC Extended Mode
parameter to Specified Mode for the alarmed NE. For details, see Configuring the Extended
ECC.
Step 2 Check whether the alarm is cleared. If it persists, contact Huawei engineers.
----End
Related Information
None.
4.2.77 COMMUN_FAIL
Description
The COMMUN_FAIL alarm indicates that communication between the system control,
switching, and timing board and the other boards is interrupted.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 201
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNH1CSHD (EM6X) l parameter 1 indicates the optical port number. This parameter
has a fixed value of 0x01.
TNM1EM6T,
l parameter 2 and parameter 3 indicate the channel number.
TNM1EM6F,
para[2] has a fixed value of 0x00. para[3] has a fixed value of
TNM1EF8F
0x03, which indicates inter-board communication.
TNM1PCX (PEX1), l parameter 4 and parameter 5 are reserved and have a fixed
TNM1PCX (PEG1) value of 0xff.
TNW1HUND2, l 0x01 0x00 0x01 0xff 0xff: Channel A of the RS485 chip is
TNW1HUNS3 abnormal.
l 0x01 0x00 0x02 0xff 0xff: Channel B of the RS485 chip is
abnormal.
TNW1UCX (SCC), l 0x03: A minor alarm is reported, indicating that the
TNW1UCXE (SCC) communication between the system control board and the
current board is interrupted.
l 0x04: A critical alarm is reported, indicating that the
communication between the system control board and the
current board is interrupted.
Impact on the System
The NE configuration cannot be delivered to the board or the board cannot work. As a result,
services cannot be configured or the protection switching function is unavailable. This means
that a service cannot be successfully added.
Possible Causes
Possible causes for the COMMUN_FAIL alarm are as follows:
l A board is reset.
l A board has poor contact with the backplane.
l A board is faulty.
l A slot is faulty.
Procedure
Step 1 Observe indicators on the board or query board reset records to check whether the board is in
the reset state.
If... Then...
The board is in the reset state Wait for 5 minutes until the board reset state ends.
Check whether the alarm is cleared.
The board is not in the reset state Go to the next step.
Step 2 Reseat the alarmed board. Then, check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 202
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
The alarm persists Proceed to the next step.
Step 3 Replace the alarmed board and check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Proceed to the next step.
Step 4 Contact Huawei technical support engineers to handle the slot fault.
NOTE
l A slot usually becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to
check whether any pins are broken or bent.
l If a vacant slot is available, insert the board in the vacant slot and update the data on the U2000 so
that the board can work normally.
----End
Related Information
None.
4.2.78 CPU_BUSY
Description
The CPU_BUSY is an alarm indicating that the CPU utilization is excessively high. When the
board detects that the CPU utilization reaches the upper limit, this alarm occurs.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
If the CPU is overloaded, some packets may not be processed timely and therefore discarded,
and the alarmed NE becomes unreachable to the NMS.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 203
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible causes of the CPU_BUSY alarm are as follows:
l Cause 1: A lot of services are configured on an NE and a huge number of tasks such as
monitoring alarms and making performance statistics are started. Therefore, the CPU
work in a high utilization.
l Cause 2: DCN packets storm occurs in the network.
Procedure
Step 1 Cause 1: A lot of services are configured on an NE and a huge number of tasks such as
monitoring alarms and making performance statistics are started. Therefore, the CPU work in
a high utilization.
1. Stop parts of the tasks of monitoring alarms and making performance statistics, or
choose a 24-hour performance statistics instead of the 15-minute performance statistics
to reduce the CPU utilization. For details, see Enabling NE Performance Monitoring in
the Commissioning.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: DCN packets storm occurs in the network.
1. If the NE reporting a CPU_BUSY alarm houses two system control boards, check the
cable connection of the NMS ports on both the system control boards. Ensure that only
one NMS port is connected to the NMS either directly or indirectly.
2. If there is another network constructed by the equipment of a third party between the
NMS port and the NMS, ensure that no loopback occurs in the third equipment.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for handling the alarm.
----End
Related Information
None
4.2.79 CRC4_ERR_OVER
Description
The CRC4_ERR_OVER is an alarm indicating that the errors of CRC4 check for the E1
services cross the threshold. This alarm occurs when the accumulated number of CRC4 check
errors for the E1 services reaches or exceeds 12000 per minute.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 204
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
When the CRC4_ERR_OVER alarm occurs, the transmission quality of the E1 services is
downgraded.
Possible Causes
The possible causes of the CRC4_ERR_OVER alarm are as follows:
l The transmit unit of the opposite station is faulty. Accordingly, errors occur in the CRC4
check for the E1 services accessed to the local end.
l The hardware fault of the board causes errors to occur in the CRC4 check for the E1
services.
Procedure
Step 1 View the CRC4_ERR_OVER alarm on the U2000, and then confirm the path number
according to the alarm parameters.
Step 2 Make sure that the accessed E1 services in the path are correct and no CRC4 check errors
occur. Then check whether the CRC4_ERR_OVER alarm is cleared.
Step 3 If the alarm persists, replace the board that generates the alarm.
----End
Related Information
None.
4.2.80 CTS
Description
The CTS is an alarm indicating that the data terminal equipment (DTE, namely, the DDN
service board) at the local station has detected the abnormal Clear To Send status.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 205
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When the CTS alarm occurs, the DTE at the local station does not work. Consequently, the
services are interrupted.
Possible Causes
The possible cause of the CTS alarm is as follows:
The data circuit-terminal equipment (DCE) at the opposite station works abnormally. For this
reason, the DTE at the local station is not in the Clear To Send status.
Procedure
Step 1 Check whether the DCE at the opposite station works well by following the actions:
1. Check whether the cable is faulty. If yes, remove the fault.
2. Check whether the service configuration is correct, including the settings of DTE and
DCE, inter, slave or exter. Make sure that the service configuration is correct.
After making sure that the DCE at the opposite station works well, the CTS alarm is
automatically cleared.
----End
Related Information
None.
4.2.81 DB_RESTORE_FAIL
Description
The DB_RESTORE_FAIL alarm indicates that service restoration fails due to failed access to
the database. When starting to work, the NE software attempts to gain access to the associated
database for restoring services. This alarm is reported if service restoration fails because the
NE software finds that some database files are lost or damaged.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
Name Meaning
Parameter 1, Indicates the slot number.
Parameter 2
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 206
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the alarm cause.
l 0x01: Indicating that the database fails to recover.
l 0x02: Indicating that failed to operate the memory database.
l 0x03: Indicating that memory data and memory database are
different.
l 0x04: Indicating that memory database can't construct memory
data.
Parameter 4, Reserved. Each parameter has a fixed value of 0xff.
Parameter 5
Impact on the System
All service configurations are lost and no new service can be configured.
Possible Causes
The possible cause of the DB_RESTORE_FAIL alarm is as follows:
Database files are lost or damaged.
Procedure
Step 1 Back up the database files in which are lost or damaged.
NOTE
This operation helps to analyze and find the database error cause.
Step 2 Delete the database and reset the NE software.
Step 3 Obtain correct database files that are backed up most recently and apply service
configurations again to clear the alarm.
NOTE
The database is not backed up in real time. Therefore, the applied service configurations may be
different from those before this problem occurs. Configure the services that have been impaired to
completely restore the services.
----End
Related Information
None.
4.2.82 DBMS_DELETE
Description
The DBMS_DELETE is an alarm indicating that the database of an NE is deleted. This alarm
is reported if a user deletes the database of an NE.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 207
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None.
Impact on the System
After this alarm is generated, the NE configuration information cannot be saved within 48
hours.
Possible Causes
The possible cause of the DBMS_DELETE alarm is as follows:
A command is run by a user to delete the database of an NE, triggering the DBMS_DELETE
alarm.
Procedure
Step 1 Restore the database of the NE on the NMS and check whether the alarm is cleared.
Step 2 If the alarm is not cleared, reset the NE.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.83 DBMS_ERROR
Description
The DBMS_ERROR alarm indicates that an error occurs in the database.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 208
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x00: The board is working properly.
l 0x01: A database check is performed.
l 0x02: A periodical database backup is performed.
l 0x04: The system is running abnormally.
l 0x08: The database data is inconsistent on the active and standby system
control boards.
l 0x10: Database incremental data fails to be backed up.
l 0x20: Database incremental data fails to be backed up to the NVRAM.
l 0x40: Database incremental data fails to be backed up to the flash memory.
Parameter 2 Indicates the errored data storage area.
l 0x00: OSF1
l 0x01: OSF2
l 0x02: DRDB, indicating the reserved memory database
l 0x03: MDB, indicating the memory database
l 0x04: TDRDB, indicating the temporary memory database
l 0x05: database on the CF card
l 0x06: shared storage area
l 0x0C: NVRAM storage area
Parameter 3 Indicates the ID of the errored database. Currently, the value ranging from 0 to
255 (that is, from 0x00 to 0xff) is supported.
l 0x00: The entire storage area is faulty.
l 0x01 to 0xff: The database with a certain ID is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 209
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 Indicates the details about alarm causes (Parameter 1).
l When Parameter 1 is 0x01:
– 0x01: An error occurs when a list file is generated in the storage area.
– 0x02: An error occurs in database file verification.
– 0x04: An error occurs in the database record header.
l When Parameter 1 is 0x02:
– 0x01: The flash memory space is insufficient, resulting in a database
backup failure.
– 0x02: Syserr check for a database fails.
l When Parameter 1 is 0x10:
– 0x02: Syserr check for a database fails.
l When Parameter 1 is 0x20:
– 0x01: The NVRAM is exhausted.
– 0x02: Data headers saved in the NVRAM are abnormal.
l When Parameter 1 is 0x40:
– 0x01: The file system in the flash memory fails to generate a small file.
Impact on the System
The DBMS_ERROR alarm has the following impact on the system:
l The backup of the active and standby databases fails.
l The database cannot be restored by itself.
l System configurations may be lost, the execution of some query and setting commands
fails, and system functions may be unavailable.
l If the alarm has been reported, new configurations may be lost after the device is
powered off or reset.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: A database operation fails.
l Cause 2: Data in the database is damaged.
l Cause 3: A system control board is faulty.
Procedure
Step 1 This alarm can be cleared automatically. If the alarm persists after two hours, the automatic
clear function fails and you need to manually clear it.
1. If only the standby system control board has this alarm, warm reset the standby system
control board only. For details, see Resetting Boards.
2. If only the active system control board has this alarm, trigger an active/standby
switchover. (A manual switchover is preferred. If the manual switchover fails, attempt to
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 210
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
remove and then reinstall the active system control board to trigger a switchover.) Then
reset the current standby system control board.
NOTE
Manual switchover method: Log in to the NMS and double-click the target NE in the Main
Topology. In the board layout diagram that is displayed, right-click the desired system control
board and choose Configure Active/Standby Switchover from the shortcut menu. On the page
that is displayed, click Query. Then check the value of SCC Board Backup Status. If data exists,
select the board and click Working/Protection Switching to perform a manual switchover.
3. If both the active and standby system control boards have this alarm, warm reset the
active system control board to trigger an active/standby switchover. When the active
system control board starts, perform a manual switchover. If the manual switchover fails,
attempt to remove and then reinstall the board to trigger a switchover. After the
switchover, reset the current standby system control board.
4. Attempt to perform the preceding manual recovery operations one more time. If the
alarm still persists, the board is faulty. Replace the faulty board. For details, see Parts
Replacement.
Step 2 When the DBMS_ERR alarm occurs, contact Huawei technical support engineers.
----End
Related Information
The DBMS_ERR alarm helps R&D personnel to identify system exceptions. When the
DBMS_ERR alarm is generated, contact Huawei technical support engineers first.
4.2.84 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE alarm indicates that the system database is in protected
mode. To prevent the service configuration data in the database from being illegally
overwritten, the database changes to the protection mode.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
None.
Impact on the System
An exception occurs in the system.
Possible Causes
The possible cause of this alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 211
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The system control unit does not properly function and is repeatedly reset.
Procedure
Step 1 Replace the system control, cross-connect, and timing board at the local end, and apply the
service configuration data again on the U2000.
----End
Related Information
None.
4.2.85 DB_UNSAVE
Description
The DB_UNSAVE alarm indicates that the configuration data in the database is not
permanently stored in the NVRAM, DRDB, or FDB storage area. This alarm is reported if the
database configuration changes.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 0x01: The database is in the package loading prohibition state. That is, the
database is not saved.
Impact on the System
If this alarm is generated and the system is reset, new configurations cannot be permanently
stored.
Possible Causes
Possible causes of this alarm are as follows: Between the package loading activation and the
end of the commit operation, the set-forbidswitch command is used to enable the
configuration, and the configuration changes.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 212
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Commit the package loading, Check whether the DB_UNSAVE alarm is cleared.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.86 DCC_CHAN_LACK
Description
The DCC_CHAN_LACK alarm indicates that DCC channel resources are insufficient.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the slot number.
Parameter 2
Parameter 3 Indicates the optical port number.
Parameter 4 Indicates the DCC channel mode in which CPU resources fail to be
obtained.
l 0x01: One byte of DCC channel resources fail to be obtained.
l 0x03: Three bytes of DCC channel resources fail to be obtained.
l 0x09: Nine bytes of DCC channel resources fail to be obtained.
l 0x0C: Twelve bytes of DCC channel resources fail to be obtained.
l 0x20: Thirty-two bytes of DCC channel resources fail to be obtained.
l 0x60: Ninety-six bytes of DCC channel resources fail to be obtained.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 213
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
This alarm does not have any impact on the system and services.
Possible Causes
The possible cause of this alarm is as follows:
There are no sufficient CPU resources to be allocated to the optical channel of the
corresponding type. For example, the channel type of optical port 1 is D1-D3, but the CPU
cannot allocate three bytes of channel resources to this optical port.
Procedure
Step 1 View the DCC_CHAN_LACK alarm on the U2000 to determine the board and optical port
where the alarm is generated.
Step 2 Delete the DCC channel of the optical port that cannot obtain CPU resources, or disable the
DCC channel. Then, check whether the alarm is cleared.
Do not delete the DCC channels of an optical port that are being used. For the D1-D3 and D4-
D12 DCC channels, the DCC communication must be disabled or enabled at the same time.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.87 DCD
Description
The DCD is an alarm indicating that the data terminal equipment (DTE, namely, the DDN
service board) at the local station has detected the abnormal Digital Carrier Detector status.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 214
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
When the DCD alarm occurs, the DTE at the local station does not work. Consequently, the
services are interrupted.
Possible Causes
The possible causes of the DCD alarm are as follows:
l The communication line is faulty.
l The DCE at the opposite station work abnormally, causing abnormal carrier at the DTE
at the local station.
Procedure
Step 1 Check whether the DCE at the opposite station works well by following the actions:
1. Check whether the cable is faulty. If yes, remove the fault.
2. Check whether the service configuration is correct, including the settings of DTE and
DCE, inter, slave or exter. Make sure that the service configuration is correct.
After making sure that the DCE at the opposite station works well, the DCD alarm is
automatically cleared.
----End
Related Information
None.
4.2.88 DCN_CHANNEL_BITERROR
Description
The DCN_CHANNEL_BITERROR alarm indicates a bit error on an outband DCN channel.
This alarm is reported when a bit error has occurred on an outband DCN channel.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 215
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicate the board slot ID corresponding to an outband DCN channel.
Parameter 2
Parameter 3, Indicate the subboard ID corresponding to an outband DCN channel.
Parameter 4
Parameter 5, Indicate the board port number corresponding to an outband DCN
Parameter 6 channel.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 216
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 7 Indicates the type of an outband DCN channel.
l 0x00: no outband DCN channel
l 0x01: channels D1 to D3
l 0x02: channels D4 to D12
l 0x03: channels D1 to D12
l 0x04: channels D4 to D6
l 0x05: channels D7 to D9
l 0x06: channels D10 to D12
l 0x07: channel D1
l 0x0A: channels MD1 to D3
l 0x0B: channel MD4_D12
l 0x0C: channel MD1_D12
l 0x0D: channel GCC0
l 0x0E: channel GCC12_9
l 0x0F: channel GCC12_18
l 0x10: channel DCNOVERETH
l 0x12: channel RES_ODU
l 0x15: channel FE_DCN
l 0x16: channel FE_DCN_ASON
l 0x17: channel GCC0_18
l 0x18: channel GCC1_24
l 0x19: channel GCCM24
l 0x1A: channel OSC_18
Parameter 8 Indicates the layer at which the alarm is reported.
l 0x01: protocol layer
l 0x02: physical layer
l 0x03: overflowed transmit queue of the DCN channel
Impact on the System
There is no impact on services, but the DCN communication on the corresponding port may
be interrupted.
Possible Causes
The possible causes of the DCN_CHANNEL_BITERROR alarm are as follows:
l Cause 1: The outband DCN link is faulty.
l Cause 2: The system control board or line board is faulty.
l Cause 3: There are too many network packets in the DCN channel.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 217
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Cause 1: The outband DCN link is faulty.
1. Check whether the outband DCN link at the local end is faulty.
a. View alarm parameters 1 to 6, and locate the board port on which the alarm is
reported.
b. Check whether the receive optical power of the port is within the allowable range.
For details about the optical power of optical modules, see Specifications of
Optical/Electrical Modules.
If… Then...
The optical power is within an Go to the next step.
allowable range
The optical power is excessively high Increase the signal attenuation during
the transmission process. Check
whether the alarm is cleared. If the
alarm persists, go to the next step.
The optical power is excessively low Check whether the fibers are intact, the
fiber connectors are clean, and the
transmit optical power of the peer line
board is normal. Then check whether
the alarm is cleared. If the alarm
persists, go to the next step.
c. Check whether the port and fiber connected to the port are normal. Replace the fiber
with an intact one, and check whether the alarm is cleared.
If… Then...
The alarm is cleared The original fiber is faulty. Replace the
fiber.
The alarm persists Go to the next step.
d. Check whether the port and optical module connected to the port are normal.
Replace the optical module with a functional optical module that matches the port
on the line board, and check whether the alarm is cleared.
If… Then...
The alarm is cleared The original optical module is faulty.
Replace the optical module.
The alarm persists Go to the next step.
2. Check whether the outband DCN link at the peer end is faulty.
a. Locate the faulty board according to the network diagram. For example, in Figure
4-3, the faulty board is the system control board on NE1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 218
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-3 Network diagram for analyzing the DCN_CHANNEL_BITERROR
alarm
Service flow
DCN_CHANNEL
_BITERROR
processing board
processing board
System control
System control
connect board
connect board
Line board
Line board
and cross-
and cross-
Service
Service
SDH
network
NE1 NE2
b. Check whether the optical power of the outband DCN port on NE2 connected to the
faulty port on NE1 is within the allowable range. For details, see Step 1.1.b.
c. Check whether the fiber between the outband DCN port on NE2 and the faulty port
on NE1 is faulty. For details, see Step 1.1.c.
d. Check whether the optical module connected to the outband DCN port on NE2
connected to the faulty port on NE1 is faulty. For details, see Step 1.1.d.
e. Check whether the alarm is cleared. If the alarm persists, go to the next step.
Step 2 Cause 2: The system control board or line board is faulty.
1. Check whether the system control board and line board at the local end are faulty.
a. If the device has the active and standby system control boards, perform an active/
standby switchover. Then check whether the alarm is cleared.
If… Then...
The alarm is cleared The original active system control
board is faulty. Replace the faulty
board.
The alarm persists Go to the next step.
NOTE
If the device has only one system control board, attempt to cold reset the board, which may
cause service interruption.
b. Cold reset the line board specified by the alarm parameter. Then check whether the
alarm is cleared.
If… Then...
The alarm is cleared The software or logic of the line board
is faulty. No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 219
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
The alarm persists The board is faulty. Replace the faulty
board. For details, see Parts
Replacement.
Services are interrupted during the cold reset process.
2. Check whether the peer line board is faulty.
a. Locate the faulty board according to the network diagram. For example, in Figure
4-3, the faulty board is the system control board on NE1.
b. Reset the system control board and line board on NE 2 in sequence. (For details, see
Step 2.1.) Then check whether the alarm is cleared. If the alarm persists, go to the
next step.
c. Replace the line board connected to the outband DCN link on NE2. Then check
whether the alarm is cleared.
If… Then...
The alarm is cleared The peer line board is faulty. Replace
the faulty board.
The alarm persists Go to the next step.
Step 3 Cause 3: There are too many network packets in the DCN channel.
1. Check whether the DCNSIZE_OVER alarm is reported. If yes, handle the alarm with
reference to DCNSIZE_OVER.
2. If the DCNSIZE_OVER alarm is not reported, check whether a large number of alarms
or events are reported on the NE. If yes, handle them one by one.
Step 4 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
Multiple DCN_CHANNEL_BITERROR alarms reported by the same NE are displayed as
only one alarm record on the NMS, and the extended parameters of the alarm are those of the
latest DCN_CHANNEL_BITERROR alarm. To view all DCN_CHANNEL_BITERROR
alarms of the NE, perform the following operations:
l Right-click the DCN_CHANNEL_BITERROR alarm in the alarm list, and choose
Display > Alarm Logs from the shortcut menu.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 220
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l In the Alarm Logs list, view all DCN_CHANNEL_BITERROR alarms reported by the
NE.
4.2.89 DCNSIZE_OVER
Description
The DCNSIZE_OVER alarm indicates that the system control, switching, and timing board
on the gateway NE (GNE) detects excessive non-GNEs on a DCN subnet.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the size of a DCN network.
Impact on the System
The GNE needs to process more DCN packets if the non-GNEs increase on a DCN subnet.
When the traffic of DCN packets exceeds the bandwidth provided by DCN channels on the
GNE, some DCN packets will be discarded.
Possible Causes
The possible cause of the DCNSIZE_OVER alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 221
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
The number of non-GNEs on a DCN subnet exceeds the recommended value.
Procedure
Step 1 Replan the DCN subnet based on actual routes and reduce the number of non-GNEs within its
allowed range.
Step 2 Check whether the alarm is cleared.
If... Then...
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.90 DDN_AIS
Description
The DDN_AIS is an alarm indication signal at the DDN port. If a board has detected that the
signals at the DDN port are all "1"s, the DDN_AIS alarm is reported.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
When the DDN_AIS alarm occurs, the accessed signals at the DDN port are useless.
Possible Causes
The possible causes of the DDN_AIS alarm are as follows:
l The AIS alarm is inserted in the services in the upstream DDN equipment connected to
the electrical interface on the DDN board.
l The receive unit of the board at the local station is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 222
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View the DDN_AIS alarm on the U2000 to confirm the relevant board.
Step 2 Check whether the accessed E1 signals of the board are reported normally. After making sure
that the accessed E1 service signals are correct, check whether the DDN_AIS alarm is
cleared.
Step 3 If the alarm persists, replace the board.
----End
Related Information
None.
4.2.91 DDN_ALOS
Description
The DDN_ALOS alarm indicates the loss of signals on the DDN port. This alarm is reported
if no service is input on the DDN port.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
When the DDN_ALOS alarm occurs, the services transmitted in the path are interrupted.
Possible Causes
The possible causes of the DDN_ALOS alarm are as follows:
l The DDN service is not accessed.
l The DDN equipment interconnected to the path is faulty.
l The output port of the DDN interface on the DDF side is disconnected or loose.
l The input port of the DDN interface at the local station is disconnected or loose.
l The board is faulty.
l The cable is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 223
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Query the alarm on the NMS. View alarm parameters to determine the board that reports the
alarm and determine the number of the channel that reports the alarm.
Step 2 Check whether the cable between the local board and the peer board is properly connected.
If… Then...
The cable is properly connected, Connect both ends of a cable to the peer
device to form a loop, and check whether
the peer device works normally.
The cable is not properly connected, Connect the cable properly. Then check
whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 3 Check whether the DDN service on the channel of the board is received.
If… Then...
The DDN service is received, Go to the next step.
The DDN service is not received, After the DDN service is received, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 4 Perform a service self-loop on the channel (hardware inloop) at the digital distribution frame
(DDF).
The inloop causes service interruption.
If… Then...
The alarm is cleared, Rectify the fault on the peer device. Then
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The alarm persists, Go to the next step.
Step 5 Perform a service self-loop on the channel (hardware inloop) on the interface board.
The inloop causes service interruption.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 224
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
The alarm is cleared, Rectify the fault in the signal cable. Then
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The alarm persists, Go to the next step.
Step 6 On the NMS, configure an inloop on the channel.
The inloop causes service interruption.
If… Then...
The alarm is cleared, Reseat or replace the interface board. Then
check whether the alarm is cleared. If the
alarm persists, contact Huawei technical
support engineers to handle the alarm.
The alarm persists, Replace the board that reports the alarm.
Then check whether the alarm is cleared. If
the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.92 DDN_CRC4_ERR_OVER
Description
The DDN_CRC4_ERR_OVER is an alarm indicating that the number of CRC4 check errors
in the 2 Mbit/s services on the electrical interface side crosses the threshold. For the 2 Mbit/s
services, if the accumulated number of CRC check errors per second reaches or exceeds
12000, the DDN_CRC4_ERR_OVER is reported.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 225
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
When the DDN_CRC4_ERR_OVER alarm occurs, the system is not affected. This alarm just
shows that the quality of the transmitted E1 services is degraded.
Possible Causes
The possible causes of the DDN_CRC4_ERR_OVER alarm are as follows:
l CRC4 check errors occur in the accessed E1 services.
l The board hardware is faulty.
Procedure
Step 1 View the DDN_CRC4_ERR_OVER alarm on the U2000, and then confirm the path number
according to the alarm parameters.
Step 2 Make sure that the accessed E1 services in the path are correct and no CRC4 check errors
occur. Then check whether the DDN_CRC4_ERR_OVER alarm is cleared.
Step 3 If the alarm persists, replace the board that generates the DDN_CRC4_ERR_OVER alarm.
----End
Related Information
None.
4.2.93 DDN_LFA
Description
The DDN_LFA is an alarm indicating the loss of frame alignment in the PDH framed E1
services on the electrical interface side. When the electrical interface side fails to receive the
frame alignment signals in the framed E1 services, the DDN_LFA alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 226
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
l When the DDN_LFA alarm occurs, the E1 services of the board are unavailable.
l The DDN_RFA alarm is returned to the opposite end.
Clear
Possible Causes
The possible causes of the DDN_LFA alarm are as follows:
l The DDN equipment interconnected to the path is faulty.
l The service frame format is incorrectly configured.
l The board hardware is faulty.
Procedure
Step 1 View the DDN_LFA alarm on the U2000 to confirm the relevant board.
Step 2 Check whether the interconnected DDN equipment works well by performing loopback to the
equipment cable. If any fault is found, take priority to remove it, and then check whether the
DDN_LFA alarm is cleared.
Step 3 Check whether the frame format of the E1 signals transmitted from the opposite end is
consistent with that specified at the local end. Make sure that the service configuration is
correct, and that the frame format of the E1 signals matches each other at the two ends. Then
check whether the DDN_LFA alarm is cleared.
Step 4 If the alarm persists, perform a cold reset on the board. Then check whether the DDN_LFA
alarm is cleared.
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, the board is faulty. Replace the board. Then the DDN_LFA alarm is
automatically cleared.
----End
Related Information
None.
4.2.94 DDN_LMFA
Description
The DDN_LMFA is an alarm indicating the loss of mulitframe alignment in the PDH framed
E1 services on the DDN side. When the DNN side fails to receive the multiframe alignment
signals in the framed E1 services, the DDN_LMFA alarm is reported.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 227
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
l When the DDN_LMFA alarm occurs, the E1 services of the board are unavailable.
l The DDN_RMFA alarm is returned to the opposite end.
Possible Causes
The possible causes of the DDN_LMFA alarm are as follows:
l The DDN equipment interconnected to the path is faulty.
l The service frame format is incorrectly configured.
l The board hardware is faulty.
Procedure
Step 1 View the DDN_LMFA alarm on the U2000 to confirm the relevant board.
Step 2 Check whether the interconnected DDN equipment works well by performing loopback to the
equipment cable. If any fault is found, take priority to remove it, and then check whether the
DDN_LFA alarm is cleared.
Step 3 Check whether the frame format of the E1 signals transmitted from the opposite end is
consistent with that specified at the local end. Make sure that the service configuration is
correct, and that the frame format of the E1 signals matches each other at the two ends. Then
check whether the DDN_LMFA alarm is cleared.
Step 4 If the alarm persists, perform a cold reset on the board. Then check whether the DDN_LMFA
alarm is cleared.
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, the board is faulty. Replace the board. Then the DDN_LMFA alarm is
automatically cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 228
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.95 DDN_LOOP_ALM
Description
The DDN_LOOP_ALM is an alarm indicating that a loopback event occur at the DDN port.
If the port on the DDN side of a board is in the loopback status, the DDN_LOOP_ALM alarm
is reported.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the loopback type.
l 0x00: Inloop
l 0x01: Outloop
Impact on the System
When the DDN_LOOP_ALM alarm occurs, some DDN port service loopback events occur in
the system. Consequently, the services at the port are interrupted.
Possible Causes
The possible cause of the DDN_LOOP_ALM alarm is as follows:
The inloop or outloop at the DDN port is set manually.
Procedure
Step 1 View the DDN_LOOP_ALM alarm on the U2000 to confirm the relevant board.
Step 2 After you cancel the loopback settings of the board that reports the alarm, the
DDN_LOOP_ALM alarm is automatically cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 229
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.96 DDN_RFA
Description
The DDN_RFA is a remote frame alignment alarm of the framed E1 services on the DDN
side of a board. When the RDI bit is set to 1 for the E1 signals received on the DDN side of a
board from the opposite end, the DDN_RFA alarm is reported.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
When the DDN_RFA alarm occurs, the services at the local station are not affected. This
alarm just shows that the DDN_LFA alarm is received at the opposite end.
Possible Causes
The possible cause of the DDN_RFA alarm is as follows:
The DDN_LFA alarm is received at the opposite end.
Procedure
Step 1 After you clear the DDN_LFA alarm received at the opposite end, the DDN_RFA alarm is
automatically cleared.
----End
Related Information
None.
4.2.97 DDN_RMFA
Description
The DDN_RMFA is a remote alarm of the framed E1 multiframe on the DDN side of a board.
If the E1 signals received on the DDN side occur in Z (Z is from two through five)
consecutive CAS multiframe cycles, the DDN_RMFA alarm is reported when all the CAS
multiframe remote alarm bits of the input signals are set to 1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 230
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
When the DDN_RMFA alarm occurs, the services at the local station are not affected. This
alarm just shows that the DDN_LMFA alarm is received at the opposite station.
Possible Causes
The possible cause of the DDN_RMFA alarm is as follows:
The DDN_LMFA alarm is received at the opposite end.
Procedure
Step 1 After you clear the DDN_LMFA alarm received at the opposite end, the DDN_RMFA alarm
is automatically cleared.
----End
Related Information
None.
4.2.98 DELAY_ADAPT_INVALID
Description
The latency compensation fails on the channel which is marked as latency-sensitive.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 231
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the actual physical channel ID.
Impact on the System
After this alarm is reported, latency compensation fails and services are adversely affected.
Possible Causes
This alarm is reported when a conflict occurs in 64 kbit/s cross-connections at the sink end of
the channel on which latency is compensated for.
Procedure
Step 1 Find the sink end according to the port that reports the alarm, and check whether 64 kbit/s
cross-connections are set up between the sink end and multiple source ends.
Step 2 After the latency compensation takes effect, you are advised not to set up cross-connections
between the sink port with other ports to avoid conflict.
Step 3 If the alarm persists after the cross-connections that are set up with other source ends are
deleted, contact Huawei engineers for help.
----End
Related Information
None.
4.2.99 DSR
Description
The DSR is an alarm indicating that the DTE at the local end has detected the DCE at the
opposite station works abnormally. This is, the Data Set Ready status at the DCE is abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
When the DSR alarm occurs, the DTE at the local end does not work. Consequently, the
services are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 232
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of the DSR alarm is as follows:
The DCE at the opposite end works abnormally because the cable is improperly connected, or
the service configuration is incorrect.
Procedure
Step 1 Check whether the DCE at the opposite end works well by following the actions:
1. Check whether the cable is faulty. If yes, remove the fault.
2. Check whether the service configuration is correct, including the settings of DTE and
DCE, inter, slave or exter. Make sure that the service configuration is correct.
After making sure that the DCE at the opposite end works well, the DSR alarm is
automatically cleared.
----End
Related Information
None.
4.2.100 DTR
Description
The DTR is an alarm indicating that the DCE at the local end has detected the DTE at the
opposite end works abnormally. That is, the Data Terminal Ready status at the DTE is
abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
When the DTR alarm occurs, the DCE at the local end does not work. Consequently, the
services are interrupted.
Possible Causes
The possible cause of the DTR alarm is as follows:
The DTE at the opposite end works abnormally because the cable is improperly connected, or
the service configuration is incorrect.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 233
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the DTE at the opposite end works well by following the actions:
1. Check whether the cable is faulty. If yes, remove the fault.
2. Check whether the service configuration is correct, including the settings of DTE and
DCE, inter, slave or exter. Make sure that the service configuration is correct.
After making sure that the DTE at the opposite end works well, the DTR alarm is
automatically cleared.
----End
Related Information
None.
4.2.101 DLAG_PROTECT_FAIL
Description
The DLAG_PROTECT_FAIL is an alarm indicating that the DLAG protection fails. If
negotiation fails or any anomaly occurs during the DLAG protection, the
DLAG_PROTECT_FAIL alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicate the ID of the LAG for which the protection fails. Parameter 2 is the
Parameter 2 higher byte, and Parameter 3 is the lower byte.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 234
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the cause of the DLAG protection failure.
l 0x01: Both the working and protection links fail.
l 0x02: The active and standby ports fail to receive the LACP packets.
l 0x03: The equipment at the opposite end does not enter the LACP
synchronization status.
l 0x04: The active or standby port detects the self-loop. Alternatively, the
active or standby port may form a loop with other ports on the board.
l 0x05: The communication between the active and standby boards times
out.
l 0x06: The communication between the board and cross-connect board
times out.
l 0x07: The active port selected by LACP is inconsistent with the one
selected by cross-connect board.
Impact on the System
When all the protocols at the DLAG port fails, or when the board fails to normally
communicate with other boards, the DLAG_PROTECT_FAIL alarm is reported. In the case
of the DLAG_PROTECT_FAIL alarm, services cannot be received or transmitted in the
LAG, or the user cannot check whether services are normally working.
Possible Causes
The possible causes of the DLAG_PROTECT_FAIL alarm are as follows:
l Both the active and standby links fail.
l The active and standby ports fail to receive the LACP packets.
l The equipment at the opposite end does not enter the LACP synchronization status.
l The active or standby port detects the self-loop. Alternatively, the active or standby port
may form a loop with other ports on the board.
l The communication between the active and standby boards times out.
l The communication between the board and the cross-connect board or SCC board times
out.
l The active port selected by LACP is inconsistent with the one selected by cross-connect
board.
Procedure
Step 1 View the DLAG_PROTECT_FAIL alarm on the U2000, and confirm the board where the
DLAG_PROTECT_FAIL alarm is generated. Confirm the ID of the LAG where the
DLAG_PROTECT_FAIL alarm is generated according to Parameter 1 and Parameter 2, and
confirm the cause of the DLAG_PROTECT_FAIL alarm at the port according to Parameter 3.
Step 2 If the value of Parameter 3 is 0x01, it indicates that the link becomes faulty or fails.
1. On the U2000, check whether the port in the LAG is enabled. If not enabled, enable the
port and then check whether the DLAG_PROTECT_FAIL alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 235
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. If the DLAG_PROTECT_FAIL alarm persists, check the link state of all the ports.
Rectify the fault of the port link, then check whether the DLAG_PROTECT_FAIL alarm
is cleared.
Step 3 If the value of Parameter 3 is 0x02, it indicates that the port fails to receive the LACP packets.
1. On the U2000, check whether the LAG is configured at the opposite end, and check
whether the port connected to the faulty port is added to the LAG at the opposite end.
Make sure the LAG is correctly configured, and then check whether the
DLAG_PROTECT_FAIL alarm is cleared.
2. If the DLAG_PROTECT_FAIL alarm persists, check whether the local port transmits
packets. If both ends can normally transmit and receive packets, check whether the
DLAG_PROTECT_FAIL alarm is cleared.
Step 4 If the value of Parameter 3 is 0x03, it indicates that the opposite equipment fails to enter the
LACP protocol synchronization status. Check the connection of the port, and LAG
configuration at the opposite equipment, and then check whether the
DLAG_PROTECT_FAIL alarm is cleared.
Step 5 If the value of Parameter 3 is 0x04, it indicates the port is in the self-loop status. Release the
loop and then check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 6 If the value of Parameter 3 is 0x05, it indicates that the communication between the active and
standby boards times out. Make sure the active and standby boards are in position, and the
communication between them is normal. Then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
Step 7 If the value of Parameter 3 is 0x06, it indicates that the communication between the board and
the cross-connect board, or SCC board, times out. Make sure the software of the cross-
connect board and the SCC is normal. If the board normally communicates with the cross-
connect board or SCC board, check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 8 If the value of Parameter 3 is 0x07, it indicates that the active port selected by LACP is
inconsistent with the one selected by cross-connect board. Make sure the active port selected
by LACP is consistent with the one selected by cross-connect board, and then check whether
the DLAG_PROTECT_FAIL alarm is cleared.
----End
Related Information
None.
4.2.102 DOWN_E1_AIS
Description
The DOWN_E1_AIS alarm is an indication alarm of downstream 2 Mbit/s signals. This alarm
is generated when the tributary board detects that the values of downstream E1 signals are all
1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 236
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 This parameter is ineffective. It has a fixed value of 0x01.
Parameter 2, Parameter 3 Indicates the path ID.
Impact on the System
E1 signals in the path are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The local end reports a high-level alarm, such as R_LOS, R_LOC, R_LOF, or MS_AIS.
l The opposite end reports the UP_E1_AIS or T_ALOS alarm.
l The tributary board at the local end is faulty.
l The system control and cross-connect units at the local end are faulty.
Procedure
Step 1 On the U2000, check whether the local end reports the R_LOS, R_LOC, R_LOF, or MS_AIS
alarm.
If... Then...
The local end reports the R_LOS, R_LOC, Clear the R_LOS, R_LOC, R_LOF, or
R_LOF, or MS_AIS alarm MS_AIS alarm. Then, check whether the
DOWN_E1_AIS alarm is cleared. If the
DOWN_E1_AIS alarm persists, go to the
next step.
The local end does not report the R_LOS, Go to the next step.
R_LOC, R_LOF, or MS_AIS alarm
Step 2 On the U2000, check whether the opposite end reports the UP_E1_AIS or T_ALOS alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 237
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The opposite end reports the UP_E1_AIS or Clear the UP_E1_AIS or T_ALOS alarm.
T_ALOS alarm Then, check whether the DOWN_E1_AIS
alarm is cleared. If the DOWN_E1_AIS
alarm persists, go to the next step.
The opposite end does not report the Go to the next step.
UP_E1_AIS or T_ALOS alarm
Step 3 Check whether the tributary board at the local end is faulty.
If... Then...
The tributary board is faulty Replace the tributary board. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The tributary board is functioning properly Go to the next step.
Step 4 Check whether the system control and cross-connect units at the local end are faulty.
If... Then...
The system control and cross-connect units Replace the system control, cross-connect,
are faulty and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The system control and cross-connect units Contact Huawei technical support engineers
are functioning properly to handle the alarm.
----End
Related Information
None.
4.2.103 DOWN_T1_AIS
Description
The DOWN_T1_AIS alarm is an indication alarm of downstream 1.5 Mbit/s signals. This
alarm is generated when the tributary board detects that the values of downstream T1 signals
are all 1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 238
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicates the path ID.
Impact on the System
The T1 signals in the board path are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The local end reports a high-level alarm, such as R_LOS, R_LOC, R_LOF, or MS_AIS.
l The tributary board at the opposite end reports the UP_T1AIS or T_ALOS alarm.
l The tributary board at the local end is faulty.
l The cross-connect unit at the local end is faulty.
Procedure
Step 1 View the DOWN_T1_AIS alarm on the U2000 to determine the board that reports the alarm.
Step 2 Check whether the local end reports a high-level alarm, such as R_LOS, R_LOC, R_LOF, or
MS_AIS. If the local end reports a high-level alarm, clear the alarm. Then, check whether the
DOWN_T1_AIS alarm is cleared.
Step 3 On the U2000, check whether the tributary board at the opposite end reports the UP_T1AIS or
T_ALOS alarm. If the tributary board reports the UP_T1AIS or T_ALOS alarm, clear the
alarm. Then, check whether the DOWN_T1_AIS alarm is cleared.
Step 4 If the DOWN_T1_AIS alarm persists, perform a cold reset on the tributary board that reports
the alarm at the local end. Then, check whether the DOWN_T1_AIS alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 239
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If the services traveling through the board are not configured with protection, cold reset of the
board interrupts the services.
Step 5 If the alarm persists, replace the tributary board that reports the DOWN_T1_AIS alarm at the
local end. Then, check whether the DOWN_T1_AIS alarm is cleared.
Step 6 If the alarm persists, perform a cold reset on the system control, cross-connect, and timing
board at the local end. Then, check whether the DOWN_T1_AIS alarm is cleared.
If there is not a standby system control, cross-connect, and timing board that properly
functions for protection, cold reset of a system control, cross-connect, and timing board may
interrupt services.
Step 7 If the DOWN_T1_AIS alarm persists, replace the system control, cross-connect, and timing
board at the local end. Then, check whether the DOWN_T1_AIS alarm is cleared.
----End
Related Information
None.
4.2.104 DROPRATIO_OVER
Description
The DROPRATIO_OVER is an alarm indicating that packet loss exceeds the threshold due to
congestion. This alarm is reported if the packet loss of a certain performance monitoring
object is out of the expected range.
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 240
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the directions in which the packet loss exceeds the threshold:
l 0x00: indicates the receive direction.
l 0x01: indicates the transmit direction.
Impact on the System
If this alarm is generated, the service has packet loss.
Possible Causes
The possible causes of the DROPRATIO_OVER alarm are as follows:
l Cause 1: The service configuration is incorrect.
l Cause 2: The actual port traffic is out of the range of limited port bandwidth or
configured CIR bandwidth.
Procedure
Step 1 Cause 1: The service configuration is incorrect.
1. Reconfigure the service according to the service planning.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The actual port traffic is out of the range of limited port bandwidth or configured
CIR bandwidth.
1. Query the traffic at the Ethernet port. If the traffic is excessively heavy, check whether a
network storm occurs. If a network storm occurs, eliminate the source that transmits a
large amount of invalid data.
2. Query the Ethernet bandwidth restriction and bandwidth usage rate. If the bandwidth
restriction is configured too low, raise the bandwidth restriction or expand the network
capacity.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
NOTE
When the alarm indicating that packet loss exceeds the threshold in the receive direction is reported,
check the processing method of red packets. If red packets are not discarded, there is no packet loss in
the receive direction.
----End
Related Information
Committed Information Rate (CIR)
CIR is a traffic parameter, indicating the permitted transmission information rate when
services are successfully transmitted. That is the rate that tokens are transmitted to the leaky
bucket (unit: bit/s). Only when the number of tokens is equal to or larger than the length of
packets, can the extra tokens pass through the leaky bucket.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 241
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.105 E1DCN_64K_CONFLICT
Description
The E1DCN_64K_CONFLICT alarm indicates a timeslot resource conflict between the E1
DCN and 64 kbit/s services. The E1 DCN has priority over other features in using timeslots of
29 to 31. When the timeslots are used by other features, the E1DCN_64K_CONFLICT alarm
is reported.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
None
Impact on the System
The 64 kbit/s services that have a timeslot resource conflict with the E1 DCN are interrupted.
Other 64 kbit/s services are not affected.
Possible Causes
Cause: The E1 DCN needs to use timeslots of 29 to 31, but these slots are used by other
features. Other features include:
l E1 SNCP
l 64 kbit/s service cross-connection
l 8 kbit/s service cross-connection
l Multiplexer group
NOTE
This alarm is also reported when the timeslots of 29 to 31 of the E1 SNCP sink board are used.
Procedure
Step 1 Cause: The E1 DCN needs to use timeslots of 29 to 31, but these slots are used by other
features.
1. Query the alarm on the NMS. Determine the board that reports the alarm, and determine
the number of the path that reports the alarm based on alarm parameters.
2. Configure the feature (E1 SNCP, 64 kbit/s service cross-connection, or other feature) that
uses the timeslots of 29 to 31 in other timeslots.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 242
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.106 E1DCN_SNCP_MM
Description
The E1DCN_SNCP_MM alarm indicates a mismatch between E1 DCN and E1 SNCP. When
the E1 DCN status (enabled or disabled) is different on the working and protection paths of
E1 SNCP, this alarm is reported by the source E1 port of E1 SNCP on which the E1 DCN is
disabled.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None
Impact on the System
After an E1 SNCP switchover occurs, services are interrupted, or the NE becomes
unreachable to the NMS.
Possible Causes
Cause: The E1 DCN status is different on the working and protection paths of E1 SNCP.
Procedure
Step 1 Cause: The E1 DCN status is different on the working and protection paths of E1 SNCP.
1. Query the alarm on the NMS. Determine the board that reports the alarm, and determine
the number of the path that reports the alarm based on alarm parameters.
2. Query the E1 DCN status of the path on the NMS. For details, see Querying the Status of
E1 DCN Channels in the Feature Description.
3. Modify the E1 DCN status to ensure consistent E1 DCN status on the working and
protection paths of E1 SNCP. For details, see Setting DIP Switches of E1 DCN Channels
in the Feature Description.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 243
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.107 E1_LOC
Description
The E1_LOC alarm indicates that a tributary board fails to extract the clock from an E1
signal.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
Services are not affected.
Possible Causes
Possible causes of the E1LOC alarm are as follows:
l The opposite NE is faulty.
l The cable wiring sequence is incorrect.
l The receive unit of the tributary board on the local NE is faulty.
l The input E1 signal has an abnormal waveform.
Procedure
Step 1 Rectify the fault on the opposite NE. Check whether the E1LOC 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 If the alarm persists, check whether any external interference causes the abnormal waveform
of the E1 signal.
If... Then...
There is the external interference Contact Huawei technical support engineers.
There is no external interference No further action is required.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 244
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.108 E1_LOS
Description
The E1_LOS alarm indicates that 2 Mbit/s line signals (E1 signals) are lost.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
E1 services are unavailable.
The E1_AIS alarm is inserted into the cross-connect unit on the 2 Mbit/s tributary board.
Possible Causes
Possible causes of this alarm are as follows:
l The cable connector is loosely connected, or the cable is broken.
l The upstream PDH equipment is faulty.
Procedure
Step 1 Check whether the cable connector is loosely connected or the cable is broken.
Step 2 If the cable connector is loosely connected or the cable is broken, rectify the fault. Then,
check on the U2000 whether the E1_LOS alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 3 Check whether the upstream PDH equipment is faulty.
Step 4 If the upstream PDH equipment is faulty, rectify the fault. Then, check on the U2000 whether
the E1_LOS alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 245
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 5 Check the board that reports the E1_LOS alarm at the local end. Reset or replace the board to
clear the alarm.
----End
Related Information
None.
4.2.109 ELAN_SMAC_FLAPPING
Description
ELAN_SMAC_FLAPPING is an alarm indicating flapping of the source MAC address
learned by an E-LAN service. This alarm is reported when two ports on an NE configured
with an E-LAN service learn a same source MAC address.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 to Parameter Indicate the flapping source MAC address.
6
Parameter 7, Parameter 8 Indicate the VLAN ID of the E-LAN service.
Parameter 9 Indicates the port type prior to the MAC address flapping.
l 0x00: UNI port
l 0x01: NNI port
Parameter 10 to Parameter Indicate the port ID prior to the MAC address flapping, either a
13 UNI ID or an NNI ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 246
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 14 Indicates the port type after the MAC address flapping.
l 0x00: UNI port
l 0x01: NNI port
Parameter 15 to Parameter Indicate the port ID after the MAC address flapping, either a
18 UNI ID or an NNI ID.
Impact on the System
A network storm occurs.
Possible Causes
A possible cause of the alarm is as follows:
l Cause 1: A UNI port or an NNI port on the NE is looped.
Procedure
Step 1 Cause 1: A UNI port or an NNI port on the NE is looped.
1. Check for a loopback according to the VLAN ID of the E-LAN service. For details, see
Detecting a loopback of an E-LAN service.
2. If a loopback exists, shut down the looped port. Check whether the alarm is cleared. If
the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.110 ENVHUM_SENSOR_FAIL
Description
The ENVHUM_SENSOR_FAIL alarm indicates that the ambient humidity sensor fails.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 247
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The equipment cannot collect ambient humidity data of the PMU.
Possible Causes
Possible causes of this alarm are as follows:
l No ambient humidity sensor is installed.
l The ambient humidity sensor is incorrectly connected.
l The ambient humidity sensor is faulty.
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether an ambient humidity sensor is installed.
If... Then...
No ambient humidity sensor is installed Install an ambient humidity sensor correctly.
An ambient humidity sensor is installed Go to the next step.
Step 2 On the U2000, check 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 cable is damaged Replace the cable.
The ambient humidity sensor is correctly Go to the next step.
connected and the cable is intact
Step 3 On the U2000, check whether the ENVHUM_SENSOR_FAIL alarm is cleared. If the
ENVHUM_SENSOR_FAIL alarm persists, replace the ambient humidity sensor.
Step 4 If the ENVHUM_SENSOR_FAIL alarm persists after the ambient humidity sensor is
replaced, replace the cabinet. Then, the ENVHUM_SENSOR_FAIL alarm is automatically
cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 248
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.111 ENVTEMP_SENSOR_FAIL
Description
The ENVTEMP_SENSOR_FAIL alarm indicates that the ambient temperature sensor fails.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
None.
Impact on the System
The equipment cannot collect ambient temperature data of the TCU board.
Possible Causes
Possible causes of this alarm are as follows:
l No ambient temperature sensor is installed.
l The ambient temperature sensor is incorrectly connected.
l The ambient temperature sensor is faulty.
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether an ambient temperature sensor is installed.
If... Then...
No ambient temperature sensor is Install an ambient temperature sensor
installed correctly.
An ambient temperature sensor is Go to the next step.
installed
Step 2 On the U2000, check whether the ENVTEMP_SENSOR_FAIL alarm is cleared. If the
ENVTEMP_SENSOR_FAIL alarm persists, check whether the ambient temperature sensor is
correctly connected or the cable is intact.
If... Then...
The ambient temperature sensor is Connect the temperature sensor correctly.
incorrectly connected
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 249
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The cable is damaged Replace the cable.
The ambient temperature sensor is Go to the next step.
correctly connected and the cable is intact
Step 3 On the U2000, check whether the ENVTEMP_SENSOR_FAIL alarm is cleared. If the
ENVTEMP_SENSOR_FAIL alarm persists, replace the ambient temperature sensor.
Step 4 If the ENVTEMP_SENSOR_FAIL alarm persists after the ambient temperature sensor is
replaced, replace the cabinet. Then, the ENVTEMP_SENSOR_FAIL alarm is automatically
cleared.
----End
Related Information
None.
4.2.112 ENVTEMP1_SENSOR_FAIL
Description
The ENVTEMP1_SENSOR_FAIL alarm indicates that ambient temperature sensor 1 fails.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
None.
Impact on the System
The equipment cannot collect the data of ambient temperature sensor 1 on the PMU.
Possible Causes
Possible causes of this alarm are as follows:
l Ambient temperature sensor 1 is not installed.
l Ambient temperature sensor 1 is incorrectly connected.
l Ambient temperature sensor 1 is faulty.
l The control board of the cabinet is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 250
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether ambient temperature sensor 1 is installed.
If... Then...
Ambient temperature sensor 1 is not Install ambient temperature sensor 1
installed correctly.
Ambient temperature sensor 1 is installed Go to the next step.
Step 2 On the U2000, check whether the ENVTEMP1_SENSOR_FAIL alarm is cleared. If the
ENVTEMP1_SENSOR_FAIL alarm persists, check whether ambient temperature sensor 1 is
correctly connected or the cable is intact.
If... Then...
Ambient temperature sensor 1 is Connect ambient temperature sensor 1
incorrectly connected correctly.
The cable is damaged Replace the cable.
Ambient temperature sensor 1 is Go to the next step.
correctly connected and the cable is intact
Step 3 On the U2000, check whether the ENVTEMP1_SENSOR_FAIL alarm is cleared. If the
ENVTEMP1_SENSOR_FAIL alarm persists, replace ambient temperature sensor 1.
Step 4 If the ENVTEMP1_SENSOR_FAIL alarm persists after ambient temperature sensor is
replaced, replace the cabinet. Then, the ENVTEMP1_SENSOR_FAIL alarm is automatically
cleared.
----End
Related Information
None.
4.2.113 ENVTEMP2_SENSOR_FAIL
Description
The ENVTEMP2_SENSOR_FAIL alarm indicates that ambient temperature sensor 2 fails.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 251
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
The equipment cannot collect the data of ambient temperature sensor 2 on the PMU.
Possible Causes
Possible causes of this alarm are as follows:
l Ambient temperature sensor 2 is not installed.
l Ambient humidity sensor 2 is incorrectly connected.
l Ambient temperature sensor 2 is faulty.
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether ambient temperature sensor 2 is installed.
If... Then...
Ambient temperature sensor 2 is not Install ambient temperature sensor 2
installed. correctly.
Ambient temperature sensor 2 is installed Go to the next step.
Step 2 On the U2000, check whether the ENVTEMP2_SENSOR_FAIL alarm is cleared. If the
ENVTEMP2_SENSOR_FAIL alarm persists, check whether ambient temperature sensor 2 is
correctly connected or the cable is intact.
If... Then...
Ambient temperature sensor 2 is Connect ambient temperature sensor 2
incorrectly connected correctly.
The cable is damaged Replace the cable.
Ambient temperature sensor 2 is Go to the next step.
correctly connected and the cable is intact
Step 3 On the U2000, check whether the ENVTEMP2_SENSOR_FAIL alarm is cleared. If the
ENVTEMP2_SENSOR_FAIL alarm persists, replace ambient temperature sensor 2.
Step 4 If the ENVTEMP2_SENSOR_FAIL alarm persists after ambient temperature sensor is
replaced, replace the cabinet. Then, the ENVTEMP2_SENSOR_FAIL alarm is automatically
cleared.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 252
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.114 ERPS_BLOCK
Description
The ERPS_BLOCK alarm indicates that a port on the ERPS ring is blocked when protection
switching is triggered (not in the idle state).
Attribute
Alarm Severity Alarm Type
Minor Equipment Alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 - Parameter 2 Indicate the ID of an ERPS instance.
Impact on the System
The alarm does not affect the system.
Possible Causes
Cause 1: When ERPS protection switching occurs, a port on the ERPS ring is blocked.
Procedure
Step 1 Cause 1: When ERPS protection switching occurs, a port on the ERPS ring is blocked.
1. In revertive mode, check the ERPS_BLOCK alarm to determine the blocked point. After
the fault is rectified, the alarm is automatically cleared.
2. In non-revertive mode, after the fault is rectified, perform the clear operation on the
owner node to clear the alarm.
– In the NE Explorer, choose Configuration > Packet Configuration > Ethernet
Protection > ERPS Management.
– In the right pane, right-click Destination Node corresponding to ERPS and choose
Clear from the shortcut menu.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 253
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.115 ERPS_NOT_COMPLETE
Description
The ERPS_NOT_COMPLETE alarm indicates that the ERPS configuration is incomplete.
Attribute
Alarm Severity Alarm Type
Minor Equipment Alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1–2 Indicate the ID of an ERPS instance.
Impact on the System
When this alarm is generated, ERPS does not take effect.
Possible Causes
Cause 1: The ERPS configuration is incomplete.
Procedure
Step 1 Cause 1: The ERPS configuration is incomplete.
1. Check whether ERPS is correctly configured for all nodes on the physical ring. For
details, see the ERPS.
2. If ERPS is correctly configured, check whether the alarm is cleared. If the alarm persists,
contact Huawei technical support engineers.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 254
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
NOTE
The ERPS_NOT_COMPLETE alarm is not reported in the following cases:
l The ERPS ring network is in the single-port state.
l The ERPS ring node is in the forced switching (FS), signal failure (SF), or manual switching (MS)
state.
l The virtual channel is not enabled. After this alarm is reported, disable the virtual channel. The
alarm is cleared.
4.2.116 ERPS_IN_PROTECTION
Description
ERPS_IN_PROTECTION indicates that EPRS ring is in protection mode.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 ERPS ID.
Parameter 3 DIR, indicating whether the faulty node is in the east
or west direction of the ERPS RPL-OWNER node.
l 0x00: west
l 0x01: east
Parameter 4, Parameter 5, NODE ID, indicating the MAC address of the faulty
Parameter 6, Parameter 7, node.
Parameter 8, Parameter 9
Impact on the System
At least one node on the ring is unreachable. Services (if any) on this node may be
interrupted.
Possible Causes
Possible causes of the ERPS_IN_PROTECTION alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 255
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the
ERPS ring.
Procedure
Step 1 Locate the faulty node on the ERPS ring based on the alarm parameters.
Step 2 Locate the ERPS blocked port on the faulty node.
Step 3 Rectify the fault.
----End
Related Information
None.
4.2.117 ETH_APS_LOST
Description
The ETH_APS_LOST alarm indicates that no APS frame is received from the protection
channel.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
Service protection fails.
Possible Causes
Possible causes of the ETH_APS_LOST alarm are as follows:
l The opposite NE is not configured with APS protection.
l The APS protection group is deactivated.
l The settings of the APS protection group differ between both ends of a service.
l The service on the protection channel is interrupted.
Procedure
Step 1 On the U2000, check whether the opposite NE is provided with APS protection.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 256
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
No APS protection is provided Go to the next step.
APS protection is provided Go to Step 4.
Step 2 Create an APS protection group on the opposite NE, with all parameter values the same as
those for the APS protection group on the local NE. Activate the APS protection and check
whether the alarm is cleared.
Step 3 If the alarm persists, go to Step 8.
Step 4 Check whether the APS protection protocol is activated at both ends.
If... Then...
The APS protection protocol is Set the state of the APS protocol to Enabled.
deactivated at both ends
The APS protection is deactivated Change the state of the APS protocol to Disabled
only at one end at the activated end, and then re-activate the APS
protection protocol at both ends.
The APS protection is activated at Go to Step 6.
both ends
Step 5 Check whether the alarm is cleared. If the alarm persists, go to Step 6.
Step 6 On the U2000, check whether the settings of the APS protection group are the same at both
ends. If the settings are different, modify them so that they are the same. Deactivate and then
activate the APS protection groups at both ends.
Step 7 Check whether the alarm is cleared. If the alarm persists, go to Step 8.
Step 8 Check whether the protection channel reports an alarm indicating signal loss or signal
degrade, such as ETH_LOS. If yes, clear the alarm.
----End
Related Information
None.
4.2.118 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH alarm indicates that the working and protection paths at
one end are different from the working and protection paths at the other end.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 257
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
Service protection fails.
Possible Causes
Possible causes of the ETH_APS_PATH_MISMATCH alarm are as follows:
l The configured working and protection paths differ between both ends.
l The physical link is connected incorrectly.
Procedure
Step 1 On the U2000, check whether the APS settings at both ends are the same.
Step 2 If they are different, modify the settings so that they are the same. Then, deactivate and
activate the APS protection groups at both ends. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, go to Step 4.
Step 4 Check whether a fiber or cable is correctly connected between both ends. If not, connect the
fiber or cable correctly.
----End
Related Information
None.
4.2.119 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL alarm indicates that the request signals in the transmitted
Automatic Protection Switching (APS) frame are different from the bridge signals in the
received APS frame and this symptom lasts for 50 ms.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 258
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
Service protection fails.
Possible Causes
The possible cause of the ETH_APS_SWITCH_FAIL alarm is as follows:
l The settings of the APS protection group differ between both ends.
Procedure
Step 1 On the U2000, check whether the settings of the APS protection group are the same at both
ends.
Step 2 If the settings differ between both ends, modify them so that they are the same. Then,
deactivate and activate the APS protection groups at both ends.
----End
Related Information
None.
4.2.120 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH alarm indicates that the information in a received APS
frame is different from the APS protection scheme configured at the local end.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the specific difference.
l 0x01: Indicates that the switching type is different.
l 0x02: Indicates that the switching direction is different.
l 0x03: Indicates that the revertive mode is different.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 259
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
APS protection may fail and consequently services may be interrupted.
Possible Causes
Possible causes of the ETH_APS_TYPE_MISMATCH alarm are as follows:
l The switching type is different.
l The switching direction is different.
l The revertive mode is different.
Procedure
Step 1 On the U2000, check whether the APS settings at both ends are the same.
Step 2 If they are different, modify the settings so that they are the same. Then, deactivate and
activate the APS protection groups at both ends.
----End
Related Information
None.
4.2.121 ETH_CFM_AIS
Description
The ETH_CFM_AIS alarm indicates that a local maintenance end point (MEP) receives an
alarm indication signal (AIS). This alarm is reported if a local MEP receives an AIS.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter Indicate the IDs of the Ethernet ports that report the alarm.
2, Parameter 3,
Parameter 4 (Port)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 260
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 5, Parameter Indicate the VLAN IDs of the relevant MEP.
6 (VLAN ID)
Parameter 7 Indicates the direction of the relevant MEP.
(Direction)
l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (Level) Indicates the level of the maintenance domain (MD).
l 0x00: Operator MP level (low)
l 0x01: Operator MP level (middle)
l 0x02: Operator MP level (high)
l 0x03: Provider MP level (low)
l 0x04: Provider MP level (high)
l 0x05: Consumer MP level (low)
l 0x06: Consumer MP level (middle)
l 0x07: Consumer MP level (high)
NOTE
Consumer indicates the user, Provider indicates the supplier, and Operator
indicates the carrier.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
The possible cause of the ETH_CFM_AIS alarm is as follows:
The upstream NE detects a fault on the Ethernet link.
Procedure
Step 1 Check whether there are ETH alarms like 4.2.124 ETH_CFM_RDI reported at the remote
MEP connected with the local MEP. If yes, clear these alarms immediately.
Step 2 Then, check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle these alarms.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 261
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.122 ETH_CFM_LOC
Description
The ETH_CFM_LOC alarm indicates loss of continuity. This alarm is generated when the
system does not receive continuity check messages (CCMs) from the maintenance end point
(MEP) at the opposite end within 3.5 times of the continuity check (CC) period.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter
Indicates the number of the Ethernet port where the alarm is
2, Parameter 3,
reported.
Parameter 4 (Port)
Parameter 5, Parameter Indicates the VLAN ID of the maintenance point (MP).
6 (VLAN ID)
Parameter 7 Indicates the direction of the MP.
(Direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (Level) Indicates the level of the maintenance domain (MD).
l 0x00: Operator MP level (low)
l 0x01: Operator MP level (middle)
l 0x02: Operator MP level (high)
l 0x03: Provider MP level (low)
l 0x04: Provider MP level (high)
l 0x05: Consumer MP level (low)
l 0x06: Consumer MP level (middle)
l 0x07: Consumer MP level (high)
NOTE
Consumer indicates the user, Provider indicates the supplier, and Operator
indicates the carrier.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 262
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 9, Parameter Indicates the ID of the MEP at the opposite end.
10 (RMEPID)
Impact on the System
l The loopback (LB) and link trace (LT) functions defined in IEEE 802.1ag ETH-OAM
are unavailable.
l The services between the related standard MPs may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Ethernet services between the standard MPs at the two ends are interrupted.
l The MEP is not correctly configured at the opposite end.
l Ethernet services are not correctly configured.
l 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.
If... Then...
The physical links between the standard Reconnect the cables and rectify the fault on
MPs at the two ends are not correctly the physical links. Then, check whether the
connected alarm is cleared. If the alarm persists, go to
the next step.
The physical links between the standard Go to the next step.
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 at the
opposite end opposite end and ensure that the
configurations of the MEP are consistent at
the two ends. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The MEP is correctly configured at the Go to the next step.
opposite end
Step 3 Check whether Ethernet services are correctly configured.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 263
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Ethernet services are not correctly Modify the Ethernet service configurations
configured and ensure that the Ethernet service
configurations are consistent at the two
ends. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
Ethernet services are correctly configured Go to the next step.
Step 4 Check the bandwidth usage. If the bandwidth resources are used up, expand the bandwidth or
disable the sources that illegally transmit a large amount of data.
----End
Related Information
None.
4.2.123 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE alarm indicates an incorrect connection. This alarm is
generated when the system receives a message indicating inconsistent maintenance
association (MA) IDs or receives a low-level continuity check message (CCM).
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the number of the Ethernet port where the
Parameter 2, ETH_CFM_MISMERGE alarm is reported.
Parameter 3,
Parameter 4 (Port)
Parameter 5, Indicates the VLAN ID of the maintenance point (MP).
Parameter 6
(VLAN ID)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 264
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 7 Indicates the direction of the MP.
(Direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (Level) Indicates the level of the maintenance domain (MD).
l 0x00: Operator MP level (low)
l 0x01: Operator MP level (middle)
l 0x02: Operator MP level (high)
l 0x03: Provider MP level (low)
l 0x04: Provider MP level (high)
l 0x05: Consumer MP level (low)
l 0x06: Consumer MP level (middle)
l 0x07: Consumer MP level (high)
NOTE
Consumer indicates the user, Provider indicates the supplier, and Operator
indicates the carrier.
Impact on the System
l The loopback (LB) and link trace (LT) functions defined in IEEE 802.1ag ETH-OAM
are unavailable.
l The services between the related standard MPs may be interrupted, or the data flow may
be incorrectly routed.
Possible Causes
Possible causes of this alarm are as follows:
l The MD levels of the standard MPs at the two ends are not the same.
l The MD or MA names of the standard MPs at the two ends are not the same.
l The physical links are incorrectly connected.
l The line configurations are incorrect.
Procedure
Step 1 Check whether the MD levels of the standard MPs at the two ends are the same.
If... Then...
The MD levels of the standard MPs at the Re-configure the MD levels and ensure that
two ends are not the same the MD levels of the standard MPs at the
two ends are the same. Then, check whether
the alarm is cleared. If the alarm persists, go
to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 265
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The MD levels of the standard MPs at the Go to the next step.
two ends are the same
Step 2 Check whether the MD or MA names of the standard MPs at the two ends are the same.
If... Then...
The MD or MA names of the standard MPs Re-configure the MD or MA names and
at the two ends are not the same ensure that the MD or MA names of the
standard MPs at the two ends are the same.
Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The MD or MA names of the standard MPs Go to the next step.
at the two ends are the same
Step 3 Check whether the physical links are correctly connected.
If... Then...
The physical links are not correctly Rectify the fault. Then, check whether the
connected alarm is cleared. If the alarm persists, go to
the next step.
The physical links are correctly connected Go to the next step.
Step 4 Check the line configurations.
If... Then...
The line configurations are incorrect Correct the line configurations. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The line configurations are correct Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 266
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.124 ETH_CFM_RDI
Description
The ETH_CFM_RDI alarm indicates that the maintenance end point (MEP) at the opposite
end fails to receive packets. This alarm is generated when the system receives a continuity
check message (CCM) that contains RDI from the opposite end.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the ID of the Ethernet port where the ETH_CFM_RDI
Parameter 2, alarm is reported.
Parameter 3,
Parameter 4 (Port)
Parameter 5, Indicates the VLAN ID of the MP.
Parameter 6 (VLAN
ID)
Parameter 7 Indicates the direction of the MP.
(Direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (Level) Indicates the level of the maintenance domain (MD).
l 0x00: Operator MP level (low)
l 0x01: Operator MP level (middle)
l 0x02: Operator MP level (high)
l 0x03: Provider MP level (low)
l 0x04: Provider MP level (high)
l 0x05: Consumer MP level (low)
l 0x06: Consumer MP level (middle)
l 0x07: Consumer MP level (high)
NOTE
Consumer indicates the user, Provider indicates the supplier, and Operator
indicates the carrier.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 267
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 9, Indicates the ID of the MEP at the opposite end.
Parameter 10
(RMEPID)
Impact on the System
l The loopback (LB) and link trace (LT) functions defined in IEEE 802.1ag ETH-OAM
are unavailable.
l The services between the related standard MPs may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The equipment on the MEP at the opposite end is reset.
l The equipment on the MEP at the opposite end is faulty (the physical links are not
interrupted, but a software fault occurs).
Procedure
Step 1 On the U2000, query the ETH_CFM_RDI alarm and determine the port where the alarm is
reported.
Step 2 Check whether the equipment on the MEP at the opposite end is reset.
If... Then...
The equipment on the MEP at the opposite Rectify the fault. Then, check whether the
end is reset alarm is cleared. If the alarm persists, go to
the next step.
The equipment on the MEP at the opposite Go to the next step.
end is not reset
Step 3 Check whether the equipment on the MEP at the opposite end is faulty. Focus on the
following alarms that the MEP at the opposite end may report: ETH_CFM_LOC,
ETH_CFM_MISMERGE, and ETH_CFM_UNEXPERI.
If... Then...
The equipment on the MEP at the opposite Rectify the fault by following the
end is faulty procedures of handling the
ETH_CFM_LOC,
ETH_CFM_MISMERGE, and
ETH_CFM_UNEXPERI alarms. Then,
check whether the ETH_CFM_RDI alarm is
cleared. If the ETH_CFM_RDI alarm
persists, go to the next step.
The equipment on the MEP at the opposite Go to the next step.
end is functioning properly
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 268
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
A standard MEP refers to an MEP that complies with IEEE802.1ag.
4.2.125 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI alarm indicates an incorrect frame. This alarm is generated
when the system receives an invalid continuity check message (CCM).
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the ID of the Ethernet port where the
Parameter 2, ETH_CFM_UNEXPERI alarm is reported.
Parameter 3,
Parameter 4 (Port)
Parameter 5, Indicates the VLAN ID of the MP.
Parameter 6 (VLAN
ID)
Parameter 7 Indicates the direction of the MP.
(Direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 269
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 8 (Level) Indicates the level of the maintenance domain (MD).
l 0x00: Operator MP level (low)
l 0x01: Operator MP level (middle)
l 0x02: Operator MP level (high)
l 0x03: Provider MP level (low)
l 0x04: Provider MP level (high)
l 0x05: Consumer MP level (low)
l 0x06: Consumer MP level (middle)
l 0x07: Consumer MP level (high)
NOTE
Consumer indicates the user, Provider indicates the supplier, and Operator
indicates the carrier.
Impact on the System
l The loopback (LB) and link trace (LT) functions defined in IEEE 802.1ag ETH-OAM
are unavailable.
l The services may be abnormal due to loops.
Possible Causes
Possible causes of this alarm are as follows:
l No maintenance end point (MEP) is configured at the opposite end.
l The continuity check periods of the standard MPs at the two ends are not the same.
l A loop occurs in the services.
l A software fault occurs on the MEP in the transmit unit.
Procedure
Step 1 Check whether an MEP is configured at the opposite end. If no MEP is configured at the
opposite end, configure it.
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 Ensure that the continuity check periods of the
standard MPs at the two ends are not standard MPs at the two ends are the same.
the same Then, check whether the alarm is cleared. If the
alarm persists, go to the next step.
The continuity check periods of the Go to the next step.
standard MPs at the two ends are the
same
Step 3 Enable the loop detection function of the P2P OAM to check whether a loop occurs in the
services. If a loop occurs in the services, release the loop.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 270
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 Perform a warm reset on the Ethernet board where the MEP at the opposite end is located.
----End
Related Information
None.
4.2.126 ETH_EFM_DF
Description
The ETH_EFM_DF alarm indicates that negotiation of the P2P OAM protocol fails at a port.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the failure.
l 0x01: The connection at the local end fails.
l 0x02: No OAM packet is received at the local end within a specified
period.
l 0x03: The OAM settings at the opposite end are inconsistent with those at
the local end.
l 0x04: The OAM settings at the local end are inconsistent with those at the
opposite end.
l 0x05 - 0xff: Reserved.
Impact on the System
Services may be interrupted.
Possible Causes
Possible causes of the ETH_EFM_DF alarm are as follows:
l Hardware equipment on the local end, such as the optical module, boards, or physical
link, is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 271
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l No OAM packet is received at the local end within a specified period.
l The OAM settings at one end do not meet the requirements at the other end.
Procedure
Step 1 On the U2000, check whether there are hardware-related alarms at the local end, such as
HARD_BAD and LSR_NO_FITED. If yes, clear these alarms. Then, check whether the
ETH_EFM_DF alarm is cleared.
Step 2 If the alarm persists, check whether an optical fiber or a cable between the local NE and the
opposite NE is damaged. If yes, replace the faulty optical fiber or cable. Check whether the
alarm is cleared.
Step 3 If the alarm persists, go to the next step.
Step 4 On the U2000, check whether the OAM protocol is enabled on the opposite NE. If not, enable
the OAM protocol. Check whether the alarm is cleared.
Step 5 If the alarm persists, check whether the OAM modes are passive at both ends. For two
interconnected systems, the OAM mode of one system must be active. If yes, make the setting
of the OAM mode active at one end or two ends based on the actual situations. Then, check
whether the alarm is cleared.
Step 6 If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is exhausted.
If yes, expand the bandwidth allocated to the tunnel or eliminate the source that transmits a
large amount of invalid data.
----End
Related Information
None.
4.2.127 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT alarm indicates that the P2P OAM protocol is enabled and the local
end receives an event indication from the opposite end.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 272
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the type of a link event.
l 0x01: Indicates an error symbol period.
l 0x02: Indicates an error frame.
l 0x03: Indicates an error frame period.
l 0x04: Indicates error frame seconds.
Impact on the System
Services degrade or are interrupted.
Possible Causes
Possible causes of the ETH_EFM_EVENT alarm are as follows:
l Boards at both ends work abnormally.
l The physical link between both ends is faulty.
Procedure
Step 1 On the U2000, check whether the opposite NE or the local NE reports any alarms that are
related to the hardware of optical modules or boards, such as HARD_BAD and
LSR_NO_FITED. If yes, clear these alarms. Then, check whether the ETH_EFM_EVENT
alarm is cleared.
Step 2 If the ETH_EFM_EVENT alarm persists, go to the next step.
Step 3 Check whether an optical fiber or a cable between the local NE and the opposite NE is
damaged. If yes, replace the faulty optical fiber or cable.
----End
Related Information
None.
4.2.128 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK alarm indicates that the P2P OAM protocol is enabled and the
local end initiates a loopback or performs a loopback at the request from the opposite end. If
the ports at both ends can respond to the loopback:
l The local OAM port receives the remote loopback control enable command issued by
the opposite OAM port, responds to the command, and reports the corresponding alarm.
The opposite port reports the alarm indicating initiation of the loopback.
l The local OAM port receives the remote loopback control disable command issued by
the opposite OAM port, responds to the command, and clears the corresponding alarm.
The opposite port clears the alarm indicating initiation of the loopback.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 273
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the loopback state.
l 0x01: Indicates initiating a loopback.
l 0x02: Indicates performing a loopback at the request from the opposite end.
Impact on the System
Services are in the loopback state.
Possible Causes
Possible causes of the ETH_EFM_LOOPBACK alarm are as follows:
l The local port initiates a loopback and the opposite port performs a loopback at the
request from the local end.
l The opposite port initiates a loopback and the local port performs a loopback at the
request from the opposite end.
Procedure
Step 1 On the U2000, query the alarm information and locate the port that reports the alarm.
Step 2 Set Remote Side Loopback Response of the port to Disabled.
Step 3 On the U2000, query the alarm information about the opposite NE and locate the port that
reports the alarm.
Step 4 Set Remote Side Loopback Response of the port to Disabled.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 274
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.129 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT alarm indicates that the P2P OAM protocol is enabled and the
local end receives a fault indication from the opposite end.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the fault.
l 0x01: A Link fault occurs at the opposite port.
l 0x02: Irrecoverable problems such as a power failure occur at the opposite
end.
l 0x03: A critical event occurs at the opposite port.
Impact on the System
The opposite port is faulty and the services at the opposite port may be unavailable.
Possible Causes
Possible causes of the ETH_EFM_REMFAULT alarm are as follows:
l The opposite port is faulty.
l A board on the opposite NE works abnormally.
l The physical link between both ends is faulty.
Procedure
Step 1 On the U2000, check whether the opposite port reports the ETH_LOS alarm. If yes, clear the
alarm. Check whether the ETH_EFM_REMFAULT alarm is cleared.
Step 2 If the alarm persists, go to the next step.
Step 3 On the U2000, check whether the opposite NE reports alarms that are related to the hardware
of optical modules or boards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these
alarms. Check whether the ETH_EFM_REMFAULT alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 275
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 If the alarm persists, go to the next step.
Step 5 Check whether an optical fiber or a cable between both ends is faulty. If yes, replace the faulty
optical fiber or cable.
----End
Related Information
None.
4.2.130 ETH_LINK_DOWN
Description
The ETH_LINK_DOWN alarm indicates that the connection at an Ethernet port is incorrect
or negotiation over an Ethernet port fails.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None.
Impact on the System
If negotiation over an Ethernet port fails, the Ethernet port fails to receive data and
consequently services are interrupted.
Possible Causes
Possible causes of the ETH_LINK_DOWN alarm are as follows:
l The local port and the opposite port work in different modes.
l Cables or fibers are incorrectly connected or are faulty.
l The local or opposite board is faulty.
Procedure
Step 1 Determine the alarmed board and alarmed port based on the alarm information on the U2000.
Step 2 Check whether the local port and the opposite port work in different modes.
If... Then...
They work in different modes Change the working modes to the same.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 276
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
They work in the same mode Go to the next step.
Step 3 Check whether cables and fibers are connected correctly and whether they function correctly.
If... Then...
Cables or fibers are incorrectly connected or Rectify the fiber/cable connections. Check
damaged whether the alarm is cleared. If the alarm
persists, go to the next step.
Cables and fibers are connected correctly Go to the next step.
and function correctly
Step 4 Check whether the opposite board is faulty.
If... Then...
The opposite board is faulty Replace the opposite board. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The opposite board is functional Go to the next step.
Step 5 Check whether the local board is faulty.
If... Then...
The local board is faulty Replace the local board and ensure that the
local port and the opposite port work in the
same mode. The alarm is cleared
automatically.
The local board is functional Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.131 ETH_LOS
Description
The ETH_LOS alarm indicates the Ethernet port connection loss.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 277
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None.
Impact on the System
Services in the receive direction are interrupted.
Possible Causes
Possible causes of the ETH_LOS alarm are as follows:
l Ethernet port configurations are incorrect.
l The cable or optical fiber is connected incorrectly.
l The cable or optical fiber is faulty.
l The alarmed board is faulty.
Procedure
Step 1 Check whether the Ethernet port configurations at both ends are correct.
If... Then...
At least one Ethernet port is disabled Enable the Ethernet port. Check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The working modes of the Ethernet ports at Change the working modes to be consistent.
the two ends are inconsistent Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The Ethernet port configurations are correct Go to the next step.
Step 2 Check whether the cable or fiber is connected correctly and functional
If... Then...
The cable or optical fiber is connected Connect the cable or optical fiber correctly.
incorrectly Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The cable or optical fiber is faulty Replace the cable or optical fiber. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The cable or optical fiber is functional Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 278
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
The opposite board is faulty Replace the opposite board. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The local board is faulty. Replace the local board. Check whether the
alarm is cleared. If the alarm persists, go to
the next step.
Step 4 Contact Huawei technical support engineers for handling the alarm.
----End
Related Information
None.
4.2.132 ETH_NO_FLOW
Description
The ETH_NO_FLOW is an alarm indicating that the Ethernet port has no traffic. This alarm
is reported when a monitored object has no traffic. For example, when the Ethernet port is
enabled and in the Link Up state, this alarm is reported if the ETH port has no traffic.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the direction in which the traffic stops.
l 0x00: the RX direction.
l 0x01: the TX direction.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 279
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
This alarm indicates that the port has no traffic and the configured services are interrupted.
Possible Causes
Possible causes of the ETH_NO_FLOW alarm are as follows:
l An Ethernet port is enabled and in linkup state, but is not configured with services.
l Services at the local end become abnormal or no packets are transmitted to the opposite
end when an Ethernet port is enabled and in linkup state.
l Services at the opposite end become abnormal or no packets are transmitted to the local
end when an Ethernet port is enabled and in linkup state.
Procedure
Step 1 View the ETH_NO_FLOW alarm on the U2000 to confirm the object, such as port, tunnel,
and VLAN, where the ETH_NO_FLOW alarm is generated.
Step 2 Check whether any service is configured on the monitored object. If no services are
configured due to carelessness, configure services correctly.
Step 3 If services have been configured at the port, locate the direction in which the traffic stops
according to Parameter.
l If the traffic stops in the TX direction, check whether the local board works normally. If
the local board works abnormally, troubleshoot the local board.
l If the traffic stops in the RX direction, check whether the opposite board works normally.
If the opposite board works abnormally, troubleshoot the opposite board.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.133 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
Alarm Severity Alarm Type
Minor Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 280
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter 2 is always 0x00, and Parameter 3 is always 0x01. These
Parameter 3 parameters are meaningless.
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: Other unknown reasons.
Impact on the System
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. The ETH-OAM function is
disabled.
Possible Causes
The possible causes of the ETHOAM_DISCOVER_FAIL alarm are as follows:
l A link fault occurs at the local end.
l The local end fails to transmit the OAM packets.
l The local end fails to receive the OAM packets within the specified time.
l The OAM configuration of the opposite end does not meet the requirements of the local
end.
l 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 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
4.2.131 ETH_LOS and 4.2.209 LINK_ERR.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 281
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 When the value of Parameter 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 OAM 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 IEEE 802.3ah 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.
4.2.134 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
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 282
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter 2 is always 0x00, and Parameter 3 is always 0x01. These
Parameter 3 parameters are meaningless.
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-0xff: Other unknown reasons.
Impact on the System
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. 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.
4.2.135 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 283
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
command from the OAM port at the opposite end. The loopback initiator reports the loopback
initiating 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter 3 Parameter 2 is always 0x00, and Parameter 3 is always 0x01.
These parameters are meaningless.
Parameter 4 l 0x01: The loopback is initiated.
l 0x02: The loopback is responded.
Impact on the System
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.
l 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 284
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.136 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter 3 Parameter 2 is always 0x00, and Parameter 3 is always 0x01.
These parameters are meaningless.
Parameter 4 Indicates the event type.
l 0x01: errored frame event
l 0x02: errored frame period event
l 0x03: errored frame second event
Impact on the System
The alarm is generated when the system runs the IEEE 802.3ah protocol. IEEE 802.3ah 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:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 285
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The port with the OAM protocol enabled receives the link event message from the
opposite end.
Procedure
Step 1 Improve the link performance at the opposite end 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.
4.2.137 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP alarm indicates that a MAC port is looped back when the point-
to-point ETH-OAM function is enabled. This alarm is generated when the MAC port of a
board receives an OAM protocol packet from itself or the board after the loopback detection
function is enabled.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter Parameter 2 is always 0x00, and Parameter 3 is always 0x01.
3 These parameters are meaningless.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 286
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 Indicates the cause for the loopback.
l 0x01: self-loop of the port
l 0x02: self-loop of the board
l 0x03 - 0xff: types for expansion.
Impact on the System
If the automatic disabling function is enabled for the port, services at the port are interrupted.
If the automatic disabling function is not enabled, broadcast storms may occur.
Possible Causes
Possible causes of this alarm are as follows:
l The optical fiber in the transmit direction of the port is connected to the optical fiber in
the receive direction of the same port.
l The optical fibers in the transmit and receive directions of the port are connected to other
ports on the same board.
l The PHY/MAC loopback is manually configured at the port.
Procedure
Step 1 Check whether the optical fiber in the transmit direction of the port is connected to the optical
fiber in the receive direction of the same port.
If... Then...
The optical fiber in the transmit direction of Reconnect the optical fibers correctly. Then,
the port is connected to the optical fiber in check whether the alarm is cleared. If the
the receive direction of the same port. alarm persists, go to the next step.
The optical fibers are correctly connected Go to the next step.
Step 2 Check whether the optical fibers in the transmit and receive directions of the port are
connected to other ports on the same board.
If... Then...
The optical fibers in the transmit and Reconnect the optical fibers properly. Then,
receive directions of the port are connected check whether the alarm is cleared. If the
to other ports on the same board alarm persists, go to the next step.
The optical fibers in the transmit and Go to the next step.
receive directions of the port are not
connected to other ports on the same board
Step 3 Check whether the PHY/MAC loopback is manually configured at the port.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 287
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The PHY/MAC loopback is manually Release the loopback manually or wait 5
configured at the port minutes until the U2000 automatically
releases the loopback. Then, check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The PHY/MAC loopback is not manually Go to the next step.
configured at the port
Step 4 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.138 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP is an alarm indicating the loopback of the VCTRUNK
port that runs the point-to-point OAM protocol. If the VCTRUNK port of a board receives the
OAM protocol packets sent by the port or the board after detection of the loop is enabled, the
alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2, Parameter Indicate the VCG port number. Parameter 2 is the higher byte, and
3 Parameter 3 is the lower byte.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 288
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 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: types for expansion.
Impact on the System
In the case of the ETHOAM_VCG_SELF_LOOP alarm, the link between VCG ports is
configured into a loop. 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_VCG_SELF_LOOP alarm are as follows:
l The links of the VCG port are configured into a loop.
l The links between VCG ports of the board are configured into a loop.
Procedure
Step 1 View the alarm on the NMS and determine the number of the VCG port where the alarm
occurs according to alarm Parameter 2.
Step 2 Check the link configuration of the VCG port to see whether the transmit direction of the port
is connected to the receive direction of the port. Ensure that the link configuration is correct,
and then check whether the alarm is cleared.
Step 3 If the alarm persists, check the link configuration of the VCG port to see whether this VCG
port is connected to another VCG port on the board in the transmit and receive directions.
Ensure that the link configuration is correct. Then, the alarm is cleared.
----End
Related Information
None.
4.2.139 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 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 289
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 290
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name 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 0x03: Provider 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.
Impact on the System
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.
l 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 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 291
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 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
4.2.140 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
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 details
about each parameter, refer to the following 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.
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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 292
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name 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 0x03: Provider 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.
Impact on the System
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
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 293
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.141 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS alarm indicates loss of the external clock source in the timing unit.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the channel of the external clock source that is lost.
l 0x01: the first channel of the external clock source
l 0x02: the second channel of the external clock source
Impact on the System
This alarm results in incorrect frame alignment, or a great many bit errors on the receive side
and pointer justification events. As a result, services are unavailable.
Possible Causes
The possible cause of this alarm is as follows:
l The signals of the physical port of the external clock source are lost.
Procedure
Step 1 Check whether the cable for inputting the external clock is correctly connected, the cable is
loosely connected, or the cable is broken.
Step 2 Rectify the cable fault. Then, check on the U2000 whether the EXT_SYNC_LOS alarm is
cleared.
If... Then...
If this alarm is cleared No further action is required.
If this alarm persists Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 294
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the equipment that provides the external clock is properly operating. If the
equipment is not properly operating, replace the equipment.
----End
Related Information
None.
4.2.142 EXT_TIME_LOC
Description
The EXT_TIME_LOC alarm indicates that the external time source is lost. This alarm is
reported when the external time port is enabled but no external time signal is received.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: Faults occur on the link set up at the external time port.
l 0x02: The second value in the time of data (TOD) information does not
change, the second pulse is unavailable, or the second pulse is deteriorated.
l 0x03: Errors occur in the cyclic redundancy check (CRC) for the TOD
information.
Impact on the System
The time of the local NE cannot be synchronized to the external time equipment that is
connected to the enabled external time port.
Possible Causes
Possible causes of the EXT_TIME_LOC alarm are as follows:
l The cable is not connected to the correct external time port.
l Faults occur on the link set up at the external time port.
l The connector wire sequences do not match at both ends of the cable.
l Faults occur on the equipment that outputs the external time.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 295
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the cable is connected to the correct external time port.
If... Then...
The cable is not connected to the correct Connect the cable to the correct external
external time port time port, and check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The cable is connected to the correct Go to the next step.
external time port
Step 2 Check the link set up at the external time port.
If... Then...
The cable carrying the link is broken or Replace the cable, and check whether the
aged alarm is cleared. If the alarm persists, go to
the next step.
No fault occurs on the link Go to the next step.
Step 3 Check the connector wire sequences at both ends of the cable.
If... Then...
The connector wire sequences do not match Replace the cable to ensure that the
at both ends of the cable connector wire sequences match at both
ends of the cable. Check whether the alarm
is cleared.
The connector wire sequences match at both Go to the next step.
ends of the cable
Step 4 Check the equipment that outputs the external time.
If... Then...
Faults occur on the equipment Rectify the faults on the equipment, and
check whether the alarm is cleared. If the
alarm persists, go to the next step.
No fault occurs on the equipment Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 296
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.143 FAN_AGING
Description
The FAN_AGING alarm indicates that a fan is deteriorating. This alarm is generated when a
fan rotates at a speed that is 80% lower than the rated value.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the fan for which the FAN_AGING alarm is
generated.
Impact on the System
The temperature of the NE is excessively high, which will affect the long-term operation of
the NE.
Possible Causes
The possible cause of this alarm is as follows:
l The fan is deteriorating.
Procedure
Step 1 Replace the fan. The alarm is automatically cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 297
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.144 FAN_COMM_FAIL
Description
The FAN_COMM_FAIL alarm indicates communication between the fan board and the NE
fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 Indicates the number of faulty fans.
Parameter 2 Indicates the numbers of faulty fans.
Impact on the System
Heat cannot be dissipated efficiently, affecting the running of the system.
If the FAN_COMM_FAIL alarm is not cleared in a timely manner, the NE may be damaged
due to overheat. Then, all services on the NE are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The fan board is in poor contact with the backplane.
l The fan board fails.
Procedure
Step 1 Reseat the board to ensure that the board is in good contact with the backplane. Check
whether the alarm is cleared. If the alarm persists, go to the next step.
Step 2 Replace the fan board.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 298
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.145 FAN_FAIL
Description
The FAN_FAIL alarm indicates a fan failure.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 Indicates the number of faulty fans.
Parameter 2 Indicates the numbers of faulty fans.
Impact on the System
Heat cannot be dissipated efficiently, affecting the running of the system.
If the FAN_FAIL alarm is not cleared in a timely manner, the NE may be damaged due to
overheat. Then, all services on the NE are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The fan attribute is incorrectly set.
l The fan is not installed or is incorrectly installed.
l The fan fails.
l The board is in poor contact with the backplane.
Procedure
Step 1 Check whether the fan attribute is set to the adjustable mode and the fan speed level is not set.
If... Then...
The fan attribute is set to the adjustable Reset the fan attribute and fan speed level.
mode and the fan speed level is not set Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The fan attribute is not set to the adjustable Go to the next step.
mode and the fan speed level is set
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 299
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Check whether fans are correctly installed.
If... Then...
Fans are not installed or incorrectly installed Reinstall the fans correctly or replace the
fan. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
Fans are correctly installed Go to the next step.
Step 3 Check the fuse on the fan board.
If... Then...
The fuse is blown Replace the fuse. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The fuse is properly functioning Go to the next step.
Step 4 Check whether the board is in good contact with the backplane.
If... Then...
The board is in poor contact with the Reseat the board to ensure that the board is
backplane in good contact with the backplane.
The board is in good contact with the Contact Huawei technical support engineers
backplane to handle the alarm.
----End
Related Information
None.
4.2.146 FAN_FAULT
Description
The FAN_FAULT alarm indicates a fan fault. This alarm is generated when one fan fails.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 300
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
The failure of one fan may lead to the increase on the board temperature and even the damage
to the board.
Possible Causes
l One fan fails.
l The logical inspection fails.
Procedure
Step 1 Replace the fan board.
----End
Related Information
None
4.2.147 FCS_ERR
Description
The FCS_ERR is an alarm indicating that errors occur in the verification of the frame check
sequence (FCS). This alarm occurs if errors occur when a board performs FCS verification of
the received GFP frames.
NOTE
This alarm is reported when the local end receives the GFP service.
If an idle frame encapsulated in the GFP format is detected, errors occur in the verification of the FCS
because the idle frame does not contain the FCS field.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 301
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 The value is always 0x01, and this parameter is meaningless.
Parameter 2, Parameter 3 Indicate the VCTRUNK number where the alarm occurs.
Impact on the System
l If the FCS_ERR alarm occurs due to inconsistent encapsulation protocols, the services
are interrupted.
l If the FCS_ERR alarm occurs due to bit errors present in the system, packet loss occurs
in the services or the services are interrupted.
Possible Causes
The possible causes of the FCS_ERR alarm are as follows:
l Cause 1: The data parameters at both ends are inconsistent.
l Cause 2: The performance of the service transmission line degrades.
l Cause 3: A certain board is faulty.
Procedure
Step 1 Cause 1: The data parameters at both ends are inconsistent.
1. The mapping protocols at both ends are different. For instance, the local end adopts the
GFP encapsulation protocol, whereas the opposite end adopts the LAPS encapsulation
protocol. Or, the settings of the protocol parameters at both ends are inconsistent. For
instance, the mapping protocols at both ends are GFP, but Extension Header Option at
the local end is set to Yes and Extension Header Option at the opposite end is set to No.
2. Query the encapsulation protocol and the settings of the protocol parameters of the
VCTRUNK port that reports the FCS_ERR alarm at both ends, such as Scramble and
Set Inverse Value for CRC.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The performance of the service transmission line degrades.
1. The performance of the transmission line degrades if the fiber connector is loose or dirty,
the fiber or cable is faulty, or the components for the transmission are not in good
contact. Check whether the alarms related to errors and optical power and the
performance events related to errors occur in the service transmission line.
If... Then...
The BIP_EXC, BIP_SD, B3_EXC, Take priority to clear the preceding
B3_SD, IN_PWR_ABN, RSBBE, alarms or performance events. Check
MSBBE, HPBBE, or LPBBE occurs whether the alarm is cleared. If the alarm
persists, go to Step 3.
The preceding alarms or performance Go to Step 3.
events do not occur
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 302
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Cause 3: A certain board is faulty.
1. Replace the board directly.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.148 FDBSIZEALM_ELAN
Description
The FDBSIZEALM_ELAN alarm indicates that the E-LAN forwarding table entries are
exhausted. This alarm is reported when the number of the MAC table entries of the E-LAN
service exceeds the value of Address Detection Upper Threshold and is cleared after the
number is smaller than the value of Address Detection Upper Threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Impact on the System
The E-LAN service stops learning new MAC addresses. As a result, unknown unicast packets
in the traffic flow may increase, and the broadcast packets may increase accordingly, affecting
the line rate.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The value of Address Detection Upper Threshold is too small.
l Cause 2: The E-LAN service is attacked.
Procedure
Step 1 Cause 1: The value of Address Detection Upper Threshold is too small.
1. On the NMS, check whether the value of Address Detection Upper Threshold is too
small.
2. If the value is too small, set the parameter to a larger value based on the actual situations.
Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 303
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Cause 2: The E-LAN service is attacked.
1. On the NMS, set the processing mode of E-LAN service for the unknown frames to
discard.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.149 FEATURE_WITHOUT_LICENSE
Description
The FEATURE_WITHOUT_LICENSE alarm indicates a feature is used without a valid
license.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1, Parameter 2, Parameter 3, Parameter 4 Indicate the ID of a licensed feature.
Impact on the System
If this licensed feature has been applied to a service, the service is still available. In addition, a
user can query and delete the service and disable the feature, but cannot create or modify the
service or enable the feature.
Possible Causes
Possible causes of the FEATURE_WITHOUT_LICENSE alarm are as follows:
l The customer does not purchase the license for using this feature.
l The equipment serial number (ESN) or V/R version specified in the license file do not
match the ESN or V/R version of the NE, and this feature has been continually
functioning on the NE for a period longer than the grace period.
l The trial period of this feature expires, and the feature has been continually functioning
on the NE for a period longer than the grace period.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 304
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the customer purchases the license for using this feature.
If... Then...
The customer does not purchase the license Delete the service that uses this feature.
Alternatively, advise the customer to
purchase the license and install the license
file to the NE. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The customer has purchased the license Go to the next step.
Step 2 Check whether the (ESN) or V/R version specified in the license file matches the ESN or V/R
version of the NE, and whether the feature has been continually functioning on the NE for a
period longer than the grace period.
If... Then...
The ESN or V/R version number specified Delete the service that uses this feature.
in the license file does not match the ESN or Alternatively, advise the customer to
V/R version of the NE, and the feature has purchase the license and install the license
been continually functioning on the NE for file to the NE. Check whether the alarm is
a period longer than the grace period cleared. If the alarm persists, contact
Huawei technical support engineers to
handle the alarm.
The ESN or V/R version number specified Contact Huawei technical support engineers
in the license file matches the ESN or V/R to handle the alarm.
version of the NE, and the feature is still in
the grace period
Step 3 Check whether the trial period of the feature expires, and whether the feature has been
continually functioning on the NE for a period longer than the grace period.
If... Then...
The trial period expires, and the feature has Delete the service that uses this feature.
been continually functioning on the NE for Alternatively, advise the customer to
a period longer than the grace period purchase the license and install the license
file to the NE. Check whether the alarm is
cleared. If the alarm persists, contact
Huawei technical support engineers to
handle the alarm.
The feature is still in the trial period and Contact Huawei technical support engineers
grace period to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 305
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
Definitions of States
Normal state
In the normal state, all the check items of the license file pass the check, and the equipment
can properly implement all the functions specified in the license file.
Trial state
In the trial state, the license file fails to be checked for correctness. During the grace period,
the equipment can still implement all the functions specified in the license file.
License grace period
The license grace period is the amount of time the features specified in a license file can
continue functioning after the license file expires. By default, the license grace period lasts for
60 days.
Default state
In the default state, the integrity check for the license file fails. Ongoing services that use the
licensed features are available, but cannot be configured any more. For example, a service that
needs to use the licensed features cannot be added or modified.
State Transition
The following figure shows the basic state transition of a license file on an NE.
Table 4-1 provides the major conditions that trigger state transition of a license file.
Table 4-1 State transition of a license file
Original State Final State Trigger Condition
Normal state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Default state The installed license file expires and its grace
period also expires.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 306
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Original State Final State Trigger Condition
Trial state Normal state The correct license file is installed.
Default state The installed license file expires and its grace
period also expires.
Default state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Normal state The correct license file is installed.
4.2.150 FIB_LEN_CHANGE
Description
The FIB_LEN_CHANGE alarm indicates that the fiber length changes. A fiber length change
may affect IEEE 1588v2 time output signals.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the fault type.
l 0x01: The total fiber length is prolonged.
l 0x02: The total fiber length is shortened.
Parameter 2, Parameter Indicate the value (unit: meter) that the total fiber length is
3 prolonged/shortened by.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 307
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The fiber deviation value at the slave end may change, which will cause the NE to trace the
time abnormally.
Possible Causes
The possible causes of the FIB_LEN_CHANGE alarm are as follows:
l Cause 1: A fiber cutover has been performed.
l Cause 2: The peer NE connected by the optical fiber has changed.
Procedure
Step 1 Cause 1: A fiber cutover has been performed.
1. Check alarm parameters on the NMS and determine whether the alarmed port has any
change, such as a fiber cutover.
If… Then...
Yes Go to Step 2.
No Re-configure the fiber deviation value. For details, see Configuring the Cable
Transmission Offset Between NEs in Feature Description.
Step 2 Cause 2: The peer NE connected by the optical fiber has changed.
1. Check whether the fiber deviation value changes.
If… Then...
Yes Measure the fiber deviation value. For details, see Testing the Compensation for Fiber
Asymmetry Delay in Commissioning Guide. Then re-configure the fiber deviation
value. For details, see Configuring the Cable Transmission Offset Between NEs in
Feature Description.
No Re-configure the fiber deviation value. For details, see Configuring the Cable
Transmission Offset Between NEs in Feature Description.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.151 FIBER_ASYMMETRIC_CHANGED
Description
The FIBER_ASYMMETRIC_CHANGED alarm indicates a fiber deviation change.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 308
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm type.
l 0x01: ring-network compensation alarm
l 0x02: performance threshold-crossing alarm
NOTE
If the alarm is a performance threshold-crossing alarm, Parameters 2 to 6 are
unavailable.
Parameter 2 Indicates the fiber deviation direction.
l 0x00: positive
l 0x01: negative
Parameter 3 to Indicate the fiber deviation value after the change. The value 0xfffff
Parameter 6 indicates that the fiber deviation value must be manually measured.
Impact on the System
A fiber deviation change causes a time synchronization failure.
Possible Causes
After a fiber is replaced, the fiber deviation value changes.
Procedure
Step 1 Check whether any NEs on the primary and secondary paths report the TIME_LOCK_FAIL
alarm on the NMS.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 309
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
The TIME_LOCK_FAIL Clear the 4.2.485 TIME_LOCK_FAIL alarm and then
alarm is reported measure the fiber deviation value. For details, see Testing the
Compensation for Fiber Asymmetry Delay in
Commissioning Guide. Then re-configure the fiber deviation
value. For details, see Configuring the Cable Transmission
Offset Between NEs in Feature Description.
No TIME_LOCK_FAIL Re-configure the deviation direction and value according to
alarm is reported the alarm parameters. For details, see Configuring the Cable
Transmission Offset Between NEs in Feature Description.
Step 2 Check whether the FIBER_ASYMMETRIC_CHANGED alarm is cleared. If the
FIBER_ASYMMETRIC_CHANGED alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.152 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the traffic flow crosses the threshold. This
alarm is reported if the received or transmitted traffic flow of a certain performance
monitoring object is out of the expected traffic flow.
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 310
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the directions of traffic flow threshold-crossing as follows:
l 0x00: indicates the receive direction.
l 0x01: indicates the transmit direction.
NOTE
No parameter is reported if this alarm is reported by the EGT1 and EFS8 boards.
Impact on the System
The impact of this alarm on the system varies with the difference between actual traffic flow
and the traffic tolerance of a port.
l Packet loss occurs if the actual traffic flow exceeds the traffic tolerance and the flow
control function is disabled when this alarm is reported, causing the service delay.
l There is no impact on both the system and service if the actual traffic flow does not
exceed the traffic tolerance when this alarm is reported. Only a message is displayed
indicating that the actual traffic flow exceeds the preconfigured traffic flow threshold.
Possible Causes
The possible cause of the FLOW_OVER alarm is as follows:
The actual receive or transmit traffic flow of a certain performance monitoring object exceeds
the preconfigured traffic flow.
Procedure
Step 1 Query the traffic at the Ethernet port. If the traffic is excessively heavy, check whether a
network storm occurs. If a network storm occurs, eliminate the source that transmits a large
amount of invalid data.
Step 2 Query the Ethernet bandwidth restriction and bandwidth usage rate. If the bandwidth
restriction is configured too low, raise the bandwidth restriction or expand the network
capacity.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.153 FUSE_ALARM
Description
The FUSE_ALARM is an alarm indicating output offline. This alarm occurs when the fuse of
the CAU board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 311
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01, and indicates path 1.
Parameter 2, Indicates the type of the faulty fuse. Parameter 2 is the higher byte, and
Parameter 3 Parameter 3 is the lower byte.
The value of Parameter 2 is always 0x00. The values of Parameter 3 are
as follows:
l 0x01: Battery fuse
l 0x02: Battery discharge
l 0x03: Load fuse 1
l 0x04: Load fuse 2
Parameter 4, Parameter 4 is the higher byte, and Parameter 5 is the lower byte.
Parameter 5
The value of Parameter 4 is always 0x00. The value of Parameter 5 is
always 0x01, and indicates open circuits.
Impact on the System
The FUSE_ALARM alarm affects the power supply of the system. It may cause power failure
to the NE.
Possible Causes
The possible causes of the FUSE_ALARM alarm are as follows:
l Cause 1: The UPM is not in position.
l Cause 2: The fuse of the UPM is faulty.
l Cause 3: The load fuse is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 312
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View the FUSE_ALARM alarm on the U2000. Confirm the type of the faulty load fuse
according to Parameter 3.
l If the battery fuse is faulty, replace the fuse. Then, check whether the FUSE_ALARM
alarm is cleared.
l If the load fuse 1 is faulty, replace the fuse. Then, check whether the FUSE_ALARM
alarm is cleared.
l If the load fuse 2 is faulty, replace the fuse. Then, check whether the FUSE_ALARM
alarm is cleared.
----End
Related Information
None.
4.2.154 FXO_POWER_FAULT
Description
The FXO_POWER_FAULT alarm indicates the absence of a feeding current on a foreign
exchange office (FXO) port. An FXO port on an NE reports an FXO_POWER_FAULT alarm
when failing to receive a feeding signal.
As shown in Figure 4-4, an FXO port on NE 2 connects to a private branch exchange (PBX),
which connects to plain old telephone service (POTS) telephone sets. An FXO port on NE 2
reports an FXO_POWER_FAULT alarm when failing to receive a feeding signal from NE 1.
Figure 4-4 FXO_POWER_FAULT reporting
An FXO port on NE 2 fails
to receive a feeding signal.
F F
POTS telephone set X X POTS telephone set
S O
NE 1 NE 2 PBX
POTS telephone set POTS telephone set
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 313
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
Calls set up on a PBX that connects to an NE reporting an FXO_POWER_FAULT alarm are
interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The transmission line between the NE reporting an FXO_POWER_FAULT
alarm and the equipment supplying a feeding current to the NE is malfunctioning.
l Cause 2: The received current exceeds the threshold allowed by FXO ports.
l Cause 3: The board reporting an FXO_POWER_FAULT alarm is faulty.
Procedure
Step 1 Cause 1: The transmission line between the NE reporting an FXO_POWER_FAULT alarm
and the equipment supplying a feeding current to the NE is malfunctioning.
1. Check whether the transmission line is cut, is damaged, or is malfunctioning. If a fault is
found, replace the transmission line.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The received current exceeds the threshold allowed by FXO ports.
1. Change Min. Current (mA) or Max. Current(mA) of FXO ports. For details, see
Configuring a PCM Port in the Configuration Guide (SDH Transport Domain).
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The board reporting an FXO_POWER_FAULT alarm is faulty.
1. Replace the board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
For information about working principles of telephone lines, see Embedded PCM in the
Feature Description.
4.2.155 FXS_LINE_FAULT
Description
The FXS_LINE_FAULT alarm indicates that a signal wire in a telephone line connecting to a
foreign exchange subscriber (FXS) port is grounded or connects to a -48 V voltage.
As shown in Figure 4-5, an FXS port on NE 1 connects to plain old telephone service (POTS)
telephone sets. An FXS port on NE 1 reports an FXS_LINE_FAULT alarm when detecting
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 314
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
that the blue wire in a telephone line is grounded or the red wire in a telephone line connects
to a -48 V voltage.
Figure 4-5 FXS_LINE_FAULT reporting
F F
POTS telephone set X X POTS telephone set
S O
NE 1 NE 2 PBX
An FXS port on NE 1 detects that a
signal wire in a telephone line is
-48 V grounded or connects to a -48 V voltage.
voltage POTS telephone set
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
Calls set up on an FXS port that reports an FXS_LINE_FAULT alarm are not interrupted, but
the call quality deteriorates.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The blue wire in a telephone line connecting to the FXS port that reports an
FXS_LINE_FAULT alarm is grounded.
l Cause 2: The red wire in a telephone line connecting to the FXS port that reports an
FXS_LINE_FAULT alarm connects to a -48 V voltage.
Procedure
Step 1 Check whether the blue wires in all telephone lines connecting to the FXS port are not
grounded, and correct any incorrect connections. Then, check whether the alarm is cleared. If
the alarm persists, go to Step 2.
Step 2 Check whether the red wires in all telephone lines connecting to the FXS port and a -48 V
voltage are not in contact, and correct any incorrect connections.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 315
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
For information about working principles of telephone lines, see Embedded PCM in the
Feature Description.
4.2.156 FXS_POWER_FAULT
Description
The FXS_POWER_FAULT alarm indicates that a telephone line connecting to a foreign
exchange subscriber (FXS) port and a 220 V electrical power cable are in contact. An FXS
port on an NE reports an FXS_POWER_FAULT alarm when detecting that a telephone line
and a 220 V electrical power cable are in contact.
As shown in Figure 4-6, an FXS port on NE 1 connects to plain old telephone service (POTS)
telephone sets. An FXS port on NE 1 reports an FXS_POWER_FAULT alarm when detecting
that the blue and red wires in a telephone line and a 220 V electrical power cable are in
contact.
Figure 4-6 FXS_POWER_FAULT reporting
F F
POTS telephone set X X POTS telephone set
S O
NE 1 NE 2 PBX
An FXS port on NE 1 detects that the blue
220 V voltage and red wires in a telephone line and a 220
V electrical power cable are in contact. POTS telephone set
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
An FXS port reporting an FXS_POWER_FAULT alarm fails to provide services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 316
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of this alarm is as follows:
l Cause 1: A telephone line connecting to the FXS port that reports an
FXS_POWER_FAULT alarm and a 220 V electrical power cable are in contact.
l Cause 2: The FXS port is damaged.
Procedure
Step 1 Check whether a telephone line connecting to the FXS port and a 220 V electrical power
cable are in contact. If a telephone line connecting to the FXS port and a 220 V electrical
power cable are in contact, disconnect the telephone line from the 220 V electrical power
cable.
Step 2 Check whether the FXS port is damaged. If the FXS port is damaged, replace the board
housing the FXS port.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
For information about working principles of telephone lines, see Embedded PCM in the
Feature Description.
4.2.157 HARD_BAD
Description
The HARD_BAD alarm indicates a board hardware failure.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
TCU (OSN 500) 0x15: A board component is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 317
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TCU (0SN 550) l 0x15: A board component is faulty.
l 0x0f 0xff: The temperature control unit is abnormal.
TNH1CSHD l 0x30 0x02: 2 MHz system clock 1 is abnormal.
(AUX) l 0x14 0x04 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x05 0x01: The 5 V power supply is undervoltage.
l 0x14 0x04 0x02: The 3.3 V power supply is overvoltage.
l 0x14 0x05 0x02: The 5 V power supply is overvoltage.
l 0x03 0xff 0xff: The 38.88 MHz system clock (orderwire clock) on
the XCSA is abnormal.
l 0x03 0x02 0xff: The 2 kHz system frame header (orderwire clock)
on the XCSA is abnormal.
l 0x04 0xff 0xff: The 38.88 MHz system clock (orderwire clock) on
the XCSB is abnormal.
l 0x04 0x02 0xff: The 2 kHz system frame header (orderwire clock)
on the XCSB is abnormal.
l 0x0a 0xff 0xff: The 32.768 MHz VCXO clock (orderwire clock) is
abnormal.
l 0x16 0xff 0xff: A historical alarm was reported, indicating that the
analog PLL of the 32.768 MHz clock (orderwire clock) was
unlocked.
l 0x12 0xff 0xff: The 32 MHz clock PLL fails.
l 0x14 0x01 0x02: The 1.2 V power supply is overvoltage.
l 0x15 0x00 0x0c: Temperature fails to be read.
l 0x14 0x01 0x01: The 1.2 V power supply is undervoltage.
TNH1CSHD l 0x08 para[2]: A bus is abnormal.
(SCC) – para[2] indicates the ID of the faulty chip.
l 0x12 para[2]: A clock component is faulty.
– para[2] indicates the ID of the checked dedicated chip. The value
0xff indicates the control logic check.
l 0x14 para[2]: A power component fails.
– para[2] indicates the ID of the checked AD chip. The value 0xff
indicates the control logic check.
TNH1CSHD l 0x12 0x09: The 38 MHz clock output by the differential drive is lost.
(STG) l 0x12 0x0c: The active crystal oscillator on the clock chip is faulty.
l 0x12 0x15: The clock chip is faulty.
l 0x16 0x0b: The 38 MHz VCXO is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 318
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNH2EFS8 l 0x12 0x02 0xff 0xff 0xff 0xff: The 25 MHz clock of the 56024 chip
is lost.
l 0x12 0x03 0xff 0xff 0xff 0xff: The 25 MHz clock of the 5241 chip is
lost.
l 0x12 0x05 0xff 0xff 0xff 0xff: The 77 MHz clock of the board is
lost.
l 0x12 0x06 0xff 0xff 0xff 0xff: The 125 MHz clock of the board is
lost.
l 0x12 0x07 0xff 0xff 0xff 0xff: The 2 kHz frame header is lost.
l 0x12 0x04 0xff 0xff 0xff 0xff: The 77 MHz clock of the ALU
SerDes logic is lost.
l 0x12 0x09 0xff 0xff 0xff 0xff: The 38 MHz clock PLL is unlocked
and the system clock is lost.
l 0x14 0x1f 0xff 0xff 0xff 0xff: A voltage sag has occurred in the 3.3
V power supply.
l 0x13 0xff 0xff 0xff 0xff 0xff: The interface component of the 5248
chip is faulty.
l 0x10 0xff 0xff 0xff 0xff 0xff: The SDH component of the 579 chip is
faulty.
l 0x0f 0xff 0xff 0xff 0xff 0xff: The programming logic device of the
FPGA is faulty.
l 0x11 0xff 0xff 0xff 0xff 0xff: The data communication component of
the 56024 chip is faulty.
TNH2EGT1 l 0x01 0x00 0x0f 0xff 0xff 0xff: The programming logic device is
faulty.
l 0x01 0x00 0x13 0xff 0xff 0xff: A power component is faulty.
l 0x01 0x00 0x06 0xff 0xff 0xff: A digital PLL is abnormal.
l 0x01 0x00 0x16 0xff 0xff 0xff: An analog PLL is abnormal.
l 0x01 0x00 0x12 0xff 0xff 0xff: A clock component is faulty.
l 0x01 0x00 0x03 0xff 0xff 0xff: 38 MHz system clock 1 is abnormal.
l 0x01 0x00 0x0e 0xff 0xff 0xff: A memory component is faulty.
l 0x01 0x00 0x13 0xff 0xff 0xff: An interface component is faulty.
l 0x31 0x01 0xff 0xff 0xff 0xff: A driver fails to be loaded.
l 0x30 0x01 0xff 0xff 0xff 0xff: The driver firmware does not match.
l 0x31 0x02 0xff 0xff 0xff 0xff: The FPGA firmware does not match.
l 0x01 0x00 0x15 0xff 0xff 0xff: Another fault has occurred.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 319
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNH2PL3T (OSN l 0x0f 0x01: The SMB bus is abnormal.
550), TNH2SP3D l 0x0f 0x02: The board FPGA fails to be loaded.
(OSN 550) l 0x0f 0x03: Drivers of the system control board and current board fail
TNM1PD1 (OSN to be loaded.
550), TNM1DMS l 0x30 0x01: The board driver is lost.
(OSN 550) l 0x30 0x02: The board FPGA is lost.
l 0x31 0x01: The board driver fails to be loaded.
l 0x16: The 32 MHz PLL component fails.
l 0x10 0x00 0x04: LIU_1 is abnormal.
l 0x10 0x00 0x05: LIU_2 is abnormal.
l 0x14 0x00 0x04 0x00: The 1.8 V power supply is overvoltage.
l 0x14 0x00 0x04 0x01: The 1.8 V power supply is undervoltage.
l 0x14 0x00 0x03 0x00: The 2.5 V power supply is overvoltage.
l 0x14 0x00 0x03 0x01: The 2.5 V power supply is undervoltage.
l 0x14 0x00 0x02 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x00 0x02 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x00 0x02 0x02: The 3.3 V power supply of the backplane is
overvoltage.
l 0x14 0x00 0x02 0x03: The 3.3 V power supply of the backplane is
undervoltage.
l 0x1b 0x00: The board is damaged.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 320
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNH2PL3T (OSN l 0x0f 0x01: The SMB bus is abnormal.
580), TNH2SP3D l 0x0f 0x02: The board FPGA fails to be loaded.
(OSN 580) l 0x0f 0x03: Drivers of the system control board and current board fail
TNM1DMS to be loaded.
(OSN 580), l 0x31 0x01: The board driver fails to be loaded.
TNM1PD1 (OSN l 0x01 0x00 0x01: The system clock of the timing board with a
580) smaller slot ID is lost.
l 0x01 0x00 0x02: The system clock of the timing board with a greater
slot ID is lost.
l 0x01 0x00 0x03: The system clocks of both timing boards are lost.
l 0x10 0x00 0x01: Chip 1 is damaged.
l 0x10 0x00 0x02: Chip 2 is damaged.
l 0x10 0x00 0x03: Chip 3 is damaged.
l 0x10 0x00 0x04: LIU_1 is abnormal.
l 0x10 0x00 0x05: LIU_2 is abnormal.
l 0x12 0x00 0x03: The 155 MHz clock is abnormal.
l 0x12 0x00 0x0f: The 32 MHz clock is abnormal.
l 0x12 0x00 0x09: The 38 MHz clock is abnormal.
l 0x12 0x00 0x0c: The 77 MHz clock is abnormal.
l 0x12 0x00 0x0e: The 2 kHz frame header is abnormal.
l 0x12 0x00 0x10: The 34 MHz clock is abnormal.
l 0x12 0x00 0x11: The 45 MHz clock is abnormal.
l 0x12 0x00 0x0d: The active clock of the interface chip fails.
l 0x0e 0xff 0x01: The EEPROM is faulty.
l 0x15 0x00 0x0c: Temperature fails to be read.
l 0x05 0x00 0x00: The 2 MHz clock component fails.
l 0x0c 0x00 0x00: The standby crystal oscillator of the 2 MHz clock
fails.
l 0x0a 0x00 0x00: The active crystal oscillator of the 2 MHz clock
fails.
l 0x12 0x00 0x10 0x00: 139 MHz clock 1 is abnormal.
l 0x12 0x00 0x10 0x00: 139 MHz clock 2 is abnormal.
l 0x14 0x00 0x04 0x00: The 1.8 V power supply is overvoltage.
l 0x14 0x00 0x04 0x01: The 1.8 V power supply is undervoltage.
l 0x14 0x00 0x03 0x00: The 2.5 V power supply is overvoltage.
l 0x14 0x00 0x03 0x01: The 2.5 V power supply is undervoltage.
l 0x14 0x00 0x02 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x00 0x02 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x00 0x02 0x02: The 3.3 V power supply of the backplane is
overvoltage.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 321
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
l 0x14 0x00 0x02 0x03: The 3.3 V power supply of the backplane is
undervoltage.
l 0x14 0x00 0x05 0x00: The 1.2 V power supply is overvoltage.
l 0x14 0x00 0x05 0x01: The 1.2 V power supply is undervoltage.
l 0x14 0x00 0x06 0x00: The 1.0 V power supply is overvoltage.
l 0x14 0x00 0x06 0x01: The 1.0 V power supply is undervoltage.
l 0x14 0x00 0x07 0x00: The 5.0 V power supply is overvoltage.
l 0x14 0x00 0x07 0x01: The 5.0 V power supply is undervoltage.
l 0x14 0x00 0x09 0x00: The 1.15 V power supply is overvoltage.
l 0x14 0x00 0x09 0x01: The 1.15 V power supply is undervoltage.
l 0x14 0x00 0x0b 0x00: The 12 V power supply is overvoltage.
l 0x14 0x00 0x0b 0x01: The 12 V power supply is undervoltage.
l 0x14 0x00 0x0c 0x00: The 3.3 V power supply of the FPGA is
overvoltage.
l 0x14 0x00 0x0c 0x01: The 3.3 V power supply of the FPGA is
undervoltage.
l 0x08 0x00 0x01 0x01: The bus of mapping chip 1 is abnormal.
l 0x08 0x00 0x01 0x02: The bus of mapping chip 2 is abnormal.
l 0x08 0x00 0x01 0x03: The bus of mapping chip 3 is abnormal.
l 0x08 0x00 0x01 0x04: The bus of mapping chip 4 is abnormal.
l 0x08 0x00 0x01 0x05: The bus of mapping chip 5 is abnormal.
l 0x08 0x00 0x01 0x06: The bus of mapping chip 6 is abnormal.
l 0x16 0x00 0x00: The 38 MHz clock is abnormal.
l 0x16 0x00 0x01: The 32 MHz PLL fails.
l 0x16 0x00 0x02: The 77 MHz PLL fails.
l 0x16 0x00 0x03: The 38 MHz PLL fails.
l 0x14 0x00 0x33 0x00: The 3.3 V power supply of the backplane is
overvoltage.
l 0x14 0x00 0x33 0x01: The 3.3 V power supply of the backplane is
undervoltage.
TNH2SL1D, l 0x0f 0x02: The board FPGA fails to be loaded.
TNH2SL4D, l 0x0a: The active crystal oscillator of the system fails.
TNH2SL1Q
TNH2SL4D, 0x0f 0x02: The board hardware is damaged.
TNH2SL1Q,
TNW1SL16Q
TNW1SL64S,
TNW1SL64D,
TNW1SL41O
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 322
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNH3EFS8 l 0x01 0x00 0x01 0xff: The power module works abnormally.
l 0x01 0x00 0x02 0xff: The board is not properly installed (for
example, the board is in poor contact with the backplane).
l 0x01 0x00 0x03 0xff: 38 MHz system clock 1 is abnormal.
l 0x01 0x00 0x04 0xff: 38 MHz system clock 2 is abnormal.
l 0x01 0x00 0x05 0xff: The 2 MHz clock source is abnormal.
l 0x01 0x00 0x06 0xff: A digital phase-locked loop (PLL) is
abnormal.
l 0x01 0x00 0x07 0xff: The 38 MHz service clock is lost.
l 0x01 0x00 0x08 0xff: The bus is abnormal.
l 0x01 0x00 0x09 0xff: The TPS protection board is abnormal.
l 0x01 0x00 0x0a 0xff: The master oscillator stops oscillating.
l 0x01 0x00 0x0b 0xff: The frequency offset of the master oscillator
exceeds the upper threshold.
l 0x01 0x00 0x0c 0xff: The slave oscillator stops oscillating.
l 0x01 0x00 0x0d 0xff: A processor, such as a CPU, DSP, or
coprocessor, is faulty.
l 0x01 0x00 0x0e 0xff: A memory component is faulty.
l 0x01 0x00 0x0f 0xff: A programmable logic device is faulty.
l 0x01 0x00 0x10 0xff: An SDH component is faulty.
l 0x01 0x00 0x11 0xff: A data communication component is faulty.
l 0x01 0x00 0x12 0xff: A clock component is faulty.
l 0x01 0x00 0x13 0xff: An interface component is faulty.
l 0x01 0x00 0x14 0xff: A power component is faulty.
l 0x01 0x00 0x15 0xff: Other faults occur.
l 0x01 0x00 0x16 0xff: An analog PLL is abnormal.
l 0x01 0x00 0x20 0xff: The flash memory is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 323
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1AUX l 0x30 0x02: 2 MHz system clock 1 is abnormal.
(OSN 550) l 0x14 0x04 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x05 0x01: The 5 V power supply is undervoltage.
l 0x14 0x04 0x02: The 3.3 V power supply is overvoltage.
l 0x14 0x05 0x02: The 5 V power supply is overvoltage.
l 0x03 0xff 0xff: The 38.88 MHz system clock (orderwire clock) on
the XCSA is abnormal.
l 0x03 0x02 0xff: The 2 kHz system frame header (orderwire clock)
on the XCSA is abnormal.
l 0x04 0xff 0xff: The 38.88 MHz system clock (orderwire clock) on
the XCSB is abnormal.
l 0x04 0x02 0xff: The 2 kHz system frame header (orderwire clock)
on the XCSB is abnormal.
l 0x0a 0xff 0xff: The 32.768 MHz VCXO clock (orderwire clock) is
abnormal.
l 0x16 0xff 0xff: A historical alarm was reported, indicating that the
analog PLL of the 32.768 MHz clock (orderwire clock) was
unlocked.
l 0x12 0xff 0xff: The 32 MHz clock PLL fails.
l 0x14 0x01 0x02: The 1.2 V power supply is overvoltage.
l 0x15 0x00 0x0c: Temperature fails to be read.
l 0x14 0x01 0x01: The 1.2 V power supply is undervoltage.
TNM1AUX l 0x12 0xff 0xff: The 32 MHz clock PLL fails.
(OSN 580) l 0x14 0x01 0x02: The 1.2 V power supply is overvoltage.
l 0x14 0x01 0x01: The 1.2 V power supply is undervoltage.
l 0x14 0x04 0x02: The 3.3 V power supply is overvoltage.
l 0x14 0x04 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x05 0x02: The 5 V power supply is overvoltage.
l 0x14 0x05 0x01: The 5 V power supply is undervoltage.
l 0x15 0x00 0x0c: Temperature fails to be read.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 324
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1CQ1 l 0x15 0x31 0xff: The FPGA fails a self-test.
l 0x15 0x32 0xff: A historical alarm was reported, indicating that the
8 kHz FP clock of the board was lost.
l 0x15 0x33 0xff: A historical alarm was reported, indicating that the
8 MHz SOH clock of the board was lost.
l 0x15 0x34 0xff: A historical alarm was reported, indicating that the
77 MHz telecom clock of the board was lost.
l 0x15 0x3c 0xff: A historical alarm was reported, indicating that the
32 MHz voltage-controlled clock of the board was lost.
l 0x15 0x35 0xff: A historical alarm was reported, indicating that the
25 MHz voltage-controlled clock of the board was lost.
l 0x15 0x36 0xff: A historical alarm was reported, indicating that the
38 MHz voltage-controlled clock of the board was lost.
l 0x15 0x39 0xff: A historical alarm was reported, indicating that the
32 MHz VCXO lockout was abnormal.
l 0x15 0x37 0xff: A historical alarm was reported, indicating that the
25 MHz VCXO lockout was abnormal.
l 0x15 0x38 0xff: A historical alarm was reported, indicating that the
38 MHz VCXO lockout was abnormal.
l 0x15 0x3a 0xff: The board slot verification fails.
l 0x15 0x3b 0xff: The board is not securely inserted.
l 0x15 0x01 0xff: The 8502 chip fails a self-test.
l 0x15 0x02 0xff: The system clock of the 8502 chip is lost.
l 0x15 0x03 0xff: A historical alarm was reported, indicating that the
number of bit errors of the 8502 chip exceeded the upper limit.
l 0x15 0x04 0xff: The SerDes on the line side is abnormal.
l 0x15 0x05 0xff: A historical alarm was reported, indicating that the
77 MHz telecom bus clock was lost.
l 0x15 0x06 0xff: A historical alarm was reported, indicating that the
77 MHz frame header of the telecom bus was lost.
l 0x15 0x07 0xff: A historical alarm was reported, indicating that the
77 MHz (or port 1) frame header of the telecom bus wandered.
l 0x15 0x11 0xff: The 8870 chip fails a self-test.
l 0x15 0x12 0xff: PLL 0 of the 8870 chip fails a self-test.
l 0x15 0x13 0xff: PLL 1 of the 8870 chip fails a self-test.
l 0x15 0x14 0xff: PLL 2 of the 8870 chip fails a self-test.
l 0x15 0x15 0xff: PLL 3 of the 8870 chip fails a self-test.
l 0x15 0x16 0xff: The 25 MHz clock of the 8870 chip is lost.
l 0x15 0x17 0xff: The 38.88 MHz clock of the 8870 chip is lost.
l 0x15 0x18 0xff: The telecom clock of the 8870 chip is lost.
l 0x15 0x19 0xff: The PLL of the 8870 chip SerDes is unlocked.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 325
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
l 0x15 0x1a 0xff: A DDR multi-bit error has occurred in the 8870
chip.
l 0x15 0x1b 0xff: The SerDes of the 8870 chip fails a self-test.
l 0x15 0x1c 0xff: A historical alarm was reported, indicating that the
system reference frame header (RFP) was lost.
l 0x15 0x1d 0xff: A historical alarm was reported, indicating that the
system reference frame header (RFP) offset was incorrect.
l 0x15 0x1e 0xff: A historical alarm was reported, indicating that the
77 MHz telecom bus clock was lost.
l 0x15 0x1f 0xff: A historical alarm was reported, indicating that the
77 MHz frame header of the telecom bus was lost.
l 0x15 0x20 0xff: A historical alarm was reported, indicating that the
77 MHz frame header of the telecom bus wandered.
l 0x15 0x47 0xff: The link between the 8870 chip and the GE port of
the backplane bus is abnormal.
l 0x15 0x48 0xff: The DDR of the 8870 chip is busy.
l 0xff 0xff 0xff: The board is not successfully loaded.
TNM1EF8F, l 0x14 0xff 0x03: The 1.0 V voltage is abnormal.
TNM1EM6T, l 0x14 0xff 0x0a: The 1.2 V voltage is abnormal.
TNM1EM6F
l 0x14 0xff 0x04: The 1.8 V voltage is abnormal.
l 0x14 0xff 0x05: The 1.2VA voltage is abnormal.
l 0x14 0xff 0x02: The 3.3 V active voltage is abnormal.
l 0x14 0xff 0x06: The 3.3COMV active voltage is abnormal.
l 0x19 0x00 0x00: The 25 MHz clock is lost.
l 0x03 0x00 0x00: The 25M_l2 clock is lost.
l 0x18 0x00 0x00: The 66 MHz clock of the board logic is lost.
l 0x0f 0x00 0x00: The programming logic device is faulty.
l 0x16 0x00 0x00: An analog PLL is abnormal.
l 0x0d 0x00 0x00: A Layer 2 chip is abnormal.
l 0x02 0xff 0xff: The board is not securely inserted.
l 0x14 0xff 0x09: The 3.3 V standby voltage is abnormal.
l 0x07 0x00 0x00: The 38 MHz active service clock is lost.
l 0x02 0x00 0x00: The 125 MHz clock is lost.
l 0x0a 0x00 0x00: The active crystal oscillator of the clock stops
oscillating.
l 0x25 para[2] 0x00: A PHY chip is abnormal.
– para[2] indicates the ID of the alarmed PHY chip.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 326
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1EG4C, l 0x0d 0x00 0x00: A Layer 2 chip is abnormal.
TNM1EG8 l 0x08 0x01 0x01: The central board detects that the internal bus of
DX port 26 is abnormal.
l 0x08 0x02 0x01: The central board detects that the internal bus of
DX port 27 is abnormal.
l 0x08 0x01 0x03: The internal bus from the PLC040 PCSC to DX
port 26 is abnormal.
l 0x08 0x02 0x03: The internal bus from the PLC040 PCSB to DX
port 27 is abnormal.
l 0xff 0xff 0xff: The board is not successfully loaded.
TNM1EX1(OSN l 0x0d 0x00 0x00: A Layer 2 chip is abnormal.
550) l 0x08 0x01 0x01: The central board detects that the internal bus of
DX port 26 is abnormal.
l 0x08 0x02 0x01: The central board detects that the internal bus of
DX port 27 is abnormal.
l 0x08 0x01 0x03: The internal bus from the PLC040 PCSC to DX
port 26 is abnormal.
l 0x08 0x02 0x03: The internal bus from the PLC040 PCSB to DX
port 27 is abnormal.
l 0xff 0xff 0xff: The board is not successfully loaded.
l 0xf 0x03 0xff: Indicates that the internal interface FMEA input clock
is lost.
l Parameter 1 is 0x31. when Parameter 3 is 0x1, it indicates that the
port of faulty Heartbeat. The values of parameter 2 are as follows:
– 0x0: Heartbeat packet loss.
– 0x1: Heartbeat packet error.
TNM1EGS4 l 0x01 0x00 0x0f 0xff: The programming logic device is faulty.
l 0x01 0x00 0x14 0xff: A power component is faulty.
l 0x01 0x00 0x06 0xff: A digital PLL is abnormal.
l 0x01 0x00 0x16 0xff: An analog PLL is abnormal.
l 0x01 0x00 0x12 0xff: A clock component is faulty.
l 0x01 0x00 0x0e 0xff: A memory component is faulty.
l 0x01 0x00 0x13 0xff: An interface component is faulty.
l 0x01 0x00 0x11 0xff: A data communication component is faulty.
l 0x01 0x00 0x10 0xff: An SDH component is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 327
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNH1CSHD l 0x15 0x08 0xff: The FPGA fails a self-test.
(ML1) l 0x15 0x0e 0xff: The PL334 chip is abnormal.
TNM1MD1 l 0x15 0x16 0xff: A DDR on the PL334 does not properly perform
downlink scheduling.
l 0x15 0x0f 0xff: An exception has occurred when the PL334 writes a
DDR for multi-channel FIFO.
l 0x15 0x10 0xff: An exception has occurred when the PL334 reads a
DDR for multi-channel FIFO.
l 0x15 0x09 0x00: The CLK-125 MHz clock of the GMII port on
8871 chip 1 is lost.
l 0x15 0x09 0x01: The CLK-125 MHz clock of the GMII port on
8871 chip 2 is lost.
l 0x18 0x02 0xff: The 125 MHz clock is lost.
l 0x18 0x03 0xff: The 2.048 MHz clock is lost.
l 0x18 0x04 0xff: The 38 MHz VCXO clock is lost.
l 0x18 0x05 0xff: The 25 MHz VCXO clock is lost.
l 0x18 0x06 0xff: The 38 MHz clock PLL is unlocked.
l 0x18 0x07 0xff: The 25 MHz clock PLL is unlocked.
l 0x15 0x0a 0xff: The GMII0 clock input by the PL334 is unlocked.
l 0x15 0x0b 0xff: The GMII1 clock input by the PL334 is unlocked.
l 0x15 0x0c 0xff: The 62.5 MHz clock input by the GE TBI port on
the PL334 is unlocked.
l 0x15 0x0d 0xff: The 125 MHz clock input by the PL334 is unlocked.
l 0x15 0x11 para[3]: The SD8871 fails a self-test.
– para[3] indicates the ID of the failed SD8871.
l 0x15 0x13 para[3]: The SA8500 fails a self-test.
– para[3] indicates the ID of the failed SA8500.
l 0x15 0x14 para[3]: The 2.048 MHz clock of an SA8500 active clock
is lost.
– para[3] indicates the ID of the alarmed SA8500 active clock.
l 0xff 0xff 0xff: The board is not successfully loaded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 328
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1PCX l 0x16 0x09 0x00: The analog PLL of the 25 MHz clock is abnormal.
(PEG1) l 0x16 0x0a 0x00: The 25 MHz VCXO clock is abnormal.
l 0x16 0x0b 0x00: The 125 MHz clock of the AD9572 chip is
abnormal.
l 0x16 0x0c 0x00: The 125 MHz clock of the 72010 chip is abnormal.
l 0x0f 0xff 0xff: The programming logic device is faulty.
l 0x16 0x07 0xff: The data-dedicated PLL of the control logic detects
that the 25 MHz clock PLL is abnormal.
l 0x16 0x0a 0xff: The data-dedicated PLL of the control logic detects
that the 125 MHz clock PLL (72010 chip) is abnormal.
l 0x08 0x01 0x02: The PowerPC detects that the internal bus of
SerDes 0 on the PCSB is abnormal.
l 0x08 0x02 0x02: The PowerPC detects that the internal bus of
SerDes 1 on the PCSB is abnormal.
l 0x0f 0x0a 0x0a: The 75 MHz system clock of the service logic is
abnormal.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 329
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1PCX l 0x16 0x08 0x00: The FPGA_PEX1_CLK_125M clock is abnormal.
(PEX1) l 0x16 0x09 0x00: The FPGA_PEX1_CLK_25M clock is abnormal.
l 0x16 0x0a 0x00: The FPGA_PEX1_CLK_125M_AD9572 clock is
abnormal.
l 0x16 0x0b 0x00: The FPGA_PEX1_CLK_25M_VCXO clock is
abnormal.
l 0x16 0x0c 0x00: The FPGA_PEX1_CLK_155M_VCXO clock is
abnormal.
l 0x16 0x0d 0x00: The FPGA_PEX1_CLK_156M_VCXO clock is
abnormal.
l 0x25 0xff 0xff: A PHY chip alarm is reported.
l 0x0f 0xff 0xff: The programming logic device is faulty.
l 0x16 0x07 0xff: The data-dedicated PLL of the control logic detects
that the 25 MHz clock PLL is abnormal.
l 0x16 0x20 0xff: The data-dedicated PLL of the control logic detects
that the 156.25 MHz clock PLL is abnormal.
l 0x16 0x03 0xff: The data-dedicated PLL of the control logic detects
that the 155.52 MHz clock PLL is abnormal.
l 0x08 0x01 0x02: The PowerPC detects that the internal bus of the
PCSB is abnormal.
l 0x08 0x02 0x02: The PowerPC detects that the internal bus of the
PCSC is abnormal.
l 0x08 0x03 0x02: The internal bus of the PCSA is abnormal.
l 0x16 0x0e 0x00: Indicates that the internal interface FMEA input
clock is lost.
l Parameter 1 is 0x31. when Parameter 3 is 0x1, it indicates that the
port of faulty Heartbeat. The values of parameter 2 are as follows:
– 0x0: Heartbeat packet loss.
– 0x1: Heartbeat packet error.
TNM1PCX l 0x00 0x0a: The active crystal oscillator is damaged.
(SCC) l 0x1b 0x00: The board is abnormal.
l 0x0f: The FPGA is damaged.
l 0x0f 0x01: The FPGA and 35E logic chip are damaged.
l 0x12 para[2]: A clock component is faulty.
– para[2] indicates the ID of the checked dedicated chip. The value
0xff indicates the control logic check.
l 0x03 0xff: 38 MHz system clock 1 is abnormal.
l 0x07 0xff: The 38 MHz service clock is lost.
l 0x17 0xff: The 32 MHz clock fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 330
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNM1PCX l 0x0a: The active crystal oscillator of the system fails.
(SL1S), l 0x0f: The FPGA is damaged.
TNM1PCX
(SL4S), l 0x08 para[2] para[3]: A bus is abnormal.
TNM1PCX – para[2] indicates the ID of the faulty chip.
(SL16S) – para[3] indicates the ID of the faulty bus.
l 0x12 para[2] para[3]: A clock component is faulty.
– para[2] indicates the ID of the checked dedicated chip. The value
0xff indicates the control logic check.
– para[3] indicates the ID of the checked clock register.
l 0x14 para[2]: A power component is faulty.
– para[2] indicates the ID of the checked AD chip. The value 0xff
indicates the control logic check.
l 0x14 0x05 0x04 0x00: The 1.5 V power supply is overvoltage.
l 0x14 0x05 0x05 0x01: The 1.5 V power supply is undervoltage.
l 0x14 0x03 0x06 0x00: The 2.5 V power supply is overvoltage.
l 0x14 0x03 0x07 0x01: The 2.5 V power supply is undervoltage.
l 0x14 0x02 0x08 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x02 0x09 0x01: The 3.3 V power supply is undervoltage.
TNM1PCX l 0x06: A digital PLL is abnormal.
(STG), l 0x16 0x0b: The 38 MHz VCXO on the local board is abnormal.
TNM1CXL
(STG) l 0x19: The 25 MHz crystal oscillator of the local board is abnormal.
l 0x18: The 66 MHz crystal oscillator of the local board is abnormal.
l 0x12 0x20 0x03: The 2 kHz frame header of the peer board is
abnormal.
l 0x12 0x20 0x02: The 38 MHz clock of the peer board is abnormal.
l 0x12 0x20 0x01: The 2 kHz frame header of the local board is
abnormal.
l 0x12 0x09: The 38 MHz clock of the local board is abnormal.
l 0x12 0x0d: The 38 MHz clock output by the differential drive of the
local board is abnormal.
l 0x12 0x0c: The 2 MHz clock output by the SA800 of the local board
is abnormal.
l 0x12 0x0e: The 12.9 MHz crystal oscillator of the SA800 chip on
the local board is abnormal.
l 0x0d: A processor, such as a CPU, DSP, or coprocessor, is faulty.
l 0x12 0x15: The clock chip is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 331
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1AT8, l 0x01 0x00 0x01: The system clock of the timing board with a
TNW1FXSO12 smaller slot ID is lost.
l 0x01 0x00 0x02: The system clock of the timing board with a greater
slot ID is lost.
l 0x01 0x00 0x03: The system clocks of both timing boards are lost.
l 0x0f 0x01: The SMB bus is abnormal.
l 0x0f 0x02: The board FPGA fails to be loaded.
l 0x0f 0x03: Drivers of the system control board and current board fail
to be loaded.
l 0x12 0x00 0x0f: The 32 MHz clock is abnormal.
l 0x12 0x00 0x09: The 38 MHz clock is abnormal.
l 0x12 0x00 0x0e: The 2 kHz frame header is abnormal.
l 0x12 0x00 0x0a: The 65 MHz clock is abnormal.
l 0x12 0x00 0x0b: The 98 MHz clock is abnormal.
l 0x12 0x00 0x0c: The 77 MHz clock is abnormal.
l 0x14 0x00 0x02 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x00 0x02 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x00 0x02 0x02: The 3.3 V power supply of the backplane is
overvoltage.
l 0x14 0x00 0x02 0x03: The 3.3 V power supply of the backplane is
undervoltage.
l 0x14 0x00 0x03 0x00: The 2.5 V power supply is overvoltage.
l 0x14 0x00 0x03 0x01: The 2.5 V power supply is undervoltage.
l 0x14 0x00 0x05 0x00: The 1.2 V power supply is overvoltage.
l 0x14 0x00 0x05 0x01: The 1.2 V power supply is undervoltage.
l 0x14 0x00 0x09 0x00: The 1.15 V power supply is overvoltage.
l 0x14 0x00 0x09 0x01: The 1.15 V power supply is undervoltage.
l 0x14 0x00 0x07 0x00: The 5.0 V power supply is overvoltage.
l 0x14 0x00 0x07 0x01: The 5.0 V power supply is undervoltage.
l 0x14 0x00 0x0a 0x00: The 1.05 V power supply is overvoltage.
l 0x14 0x00 0x0a 0x01: The 1.05 V power supply is undervoltage.
l 0x14 0x00 0x0b 0x00: The 12 V power supply of the board is
overvoltage.
l 0x14 0x00 0x0b 0x01: The 12 V power supply of the board is
undervoltage.
l 0x14 0x00 0x0c 0x00: The 3.3 V power supply of the FPGA is
overvoltage.
l 0x14 0x00 0x0c 0x01: The 3.3 V power supply of the FPGA is
undervoltage.
l 0x15 0x00 0x0c: Temperature fails to be read.
l 0x16 0x00 0x00: The 32 MHz PLL fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 332
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
l 0x16 0x00 0x02: The 155 MHz PLL fails.
l 0x30 0x01: The board driver is lost.
l 0x30 0x02: The board FPGA is lost.
l 0x0e 0xff 0x01: The EEPROM is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 333
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1DXM, l 0x01 0x00 0x01: The system clock of the timing board with a
TNW1SP3S, smaller slot ID is lost.
TNW1PF4E8 l 0x01 0x00 0x02: The system clock of the timing board with a greater
slot ID is lost.
l 0x01 0x00 0x03: The system clocks of both timing boards are lost.
l 0x0f 0x01: The SMB bus is abnormal.
l 0x0f 0x02: The board FPGA fails to be loaded.
l 0x0f 0x03: Drivers of the system control board and current board fail
to be loaded.
l 0x10 0x01 para[2]: RAM fails. para[2] indicates the number of
failed blocks.
l 0x12 0x00 0x03: The 155 MHz clock is abnormal.
l 0x12 0x00 0x09: The 38 MHz clock is abnormal.
l 0x12 0x00 0x0a: The 2 MHz clock is abnormal.
l 0x12 0x00 0x0b: The 2 MHz clock of the LIU chip is abnormal.
l 0x12 0x00 0x0e: The 2 kHz frame header is abnormal.
l 0x12 0x00 0x0f: The 32 MHz clock is abnormal.
l 0x12 0x00 0x10 0x00: 139 MHz clock 1 is abnormal.
l 0x12 0x00 0x10 0x01: 139 MHz clock 2 is abnormal.
l 0x14 0x00 0x02 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x00 0x02 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x00 0x02 0x02: The 3.3 V power supply of the backplane is
overvoltage.
l 0x14 0x00 0x02 0x03: The 3.3 V power supply of the backplane is
undervoltage.
l 0x14 0x00 0x03 0x00: The 2.5 V power supply is overvoltage.
l 0x14 0x00 0x03 0x01: The 2.5 V power supply is undervoltage.
l 0x14 0x00 0x04 0x00: The 1.8 V power supply is overvoltage.
l 0x14 0x00 0x04 0x01: The 1.8 V power supply is undervoltage.
l 0x14 0x00 0x05 0x00: The 1.2 V power supply is overvoltage.
l 0x14 0x00 0x05 0x01: The 1.2 V power supply is undervoltage.
l 0x14 0x00 0x06 0x00: The 1.0 V power supply is overvoltage.
l 0x14 0x00 0x06 0x01: The 1.0 V power supply is undervoltage.
l 0x14 0x00 0x07 0x00: The 5.0 V power supply is overvoltage.
l 0x14 0x00 0x07 0x01: The 5.0 V power supply is undervoltage.
l 0x15 0x00 0x0c: Temperature fails to be read.
l 0x16 0x00 0x00: The 32 MHz PLL fails.
l 0x16 0x00 0x02: The 155 MHz PLL fails.
l 0x30 0x01: The board driver is lost.
l 0x30 0x02: The board FPGA is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 334
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1EM20 l 0x0d 0x90 0x00: The 5890 chip is faulty.
l 0x0f 0x01 0xff: The programming logic device is faulty.
l 0x02 0x01 0xff: The board is not securely inserted.
l 0x15 0x01 0xff: The ZL80018 chip is faulty.
l 0x0d 0x01 0xff: The 5890 chip ID is incorrect.
l 0x0e 0x01 0xff: One or more EMEM IERR errors have occurred.
l 0x0e 0x02 0xff: One or more PMC IF0 IERR errors have occurred.
l 0x0e 0x03 0xff: One or more PMC IF1 IERR errors have occurred.
l 0x0e 0x04 0xff: One or more PMC IF2 IERR errors have occurred.
l 0x0e 0x05 0xff: One or more SE DMC IERR errors have occurred.
l 0x12 0x01 0xff: The 50 MHz clock PLL of the FPGA is currently
unlocked.
l 0x12 0x02 0xff: The 50 MHz clock PLL of the FPGA was once
unlocked.
l 0x12 0x03 0xff: The 156.25 MHz clock of the FPGA PLL is
currently unlocked.
l 0x12 0x04 0xff: The 25 MHz clock of the FPGA is unlocked.
l 0x12 0x05 0x01: 1548 chip 1 is abnormal.
l 0x12 0x05 0x02: 1548 chip 2 is abnormal.
l 0x12 0x05 0x03: 1548 chip 3 is abnormal.
l 0x34 0x01 0xff: Heartbeat packet 1 is abnormal.
l 0x14 para[2] 0xff: The I2C voltage is abnormal.
– para[2] indicates the ID of the I2C voltage.
l 0x11 0xff 0xff: The board accesses the BootROM system.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 335
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1EM10 l 0x15 0x03 0xff: The AD80341 chip (clock chip) is faulty.
l 0x12 0x01 0xff: The LOC of the system clock on the AD80341 chip
is faulty.
l 0x12 0x02 0xff: The lockout status of the internal PLL0 on the
AD80341 chip is faulty.
l 0x12 0x03 0xff: The lockout status of the internal PLL1 on the
AD80341 chip is faulty.
l 0x15 0x08 0xff: The 77 MHz clock signals of the low-speed clock
are lost.
l 0x15 0x09 0xff: The 155 MHz clock signals of the low-speed clock
are lost.
l 0x35 0x01 0xff: The 38 MHz clock is faulty.
l 0x35 0x02 0xff: The RTC is faulty.
l 0x35 0x03 0xff: The second frame header is faulty.
l 0x35 0x04 0xff: The IIC is faulty.
l 0x15 0x01 0xff: The self-test of the SA8006 chip (CES clock
processing chip) fails.
l 0x12 0x04 0xff: The master crystal oscillator clock of the SA8006
chip is lost.
l 0x06 0x02 0xff: The PLLXO of the SA8006 chip is out of lock.
l 0x12 0x05 0xff: The LOC history of the first reference clock on the
SA8006 chip is lost.
l 0x15 0x02 0xff: The self-test of the 8870 chip fails.
l 0x12 0x06 0xff: The 25 MHz clock of the 8870 chip (CES service
processing chip) is lost.
l 0x12 0x07 0xff: The 38 MHz clock of the 8870 chip is lost.
l 0x12 0x08 0xff: The E1T1 clock of the 8870 chip is lost.
l 0x12 0x09 0xff: The telcom clock of the 8870 chip is lost.
l 0x06 0x03 0xff: The SerDes PLL of the 8870 chip is out of lock.
l 0x0e 0x05 0xff: A multi-bit error occurs when data is read back from
the DDR of the 8870 chip.
l 0x0e 0x06 0xff: A mult-bit error occurs in the DDR of the 8870
chip.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 336
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1HUND2, l 0x0d 0x90 0x00: The 5890 chip is faulty.
TNW1HUNS3 l 0x0d 0x01 0xff: The 5890 chip ID is incorrect.
l 0x0e 0x01 0xff: One or more EMEM IERR errors have occurred.
l 0x0e 0x02 0xff: One or more PMC IF0 IERR errors have occurred.
l 0x0e 0x03 0xff: One or more PMC IF1 IERR errors have occurred.
l 0x0e 0x05 0xff: One or more SE DMC IERR errors have occurred.
l 0x34 0x01 0xff: Heartbeat packet 1 is abnormal.
l 0x11 0xff 0xff: The board accesses the BootROM system.
l 0x0f 0x01 0xff: The programming logic device is faulty.
l 0x02 0x01 0xff: The connector between the board and the backplane
is not securely inserted.
l 0x02 0x02 0xff: The connector between the upper and lower boards
is not securely connected.
l 0x06 0x01 para[3]: The ASIC clock PLL is unlocked.
– para[3] indicates the ID of the alarmed ASIC clock.
l 0x06 para[2] 0xff: The FPGA clock is abnormal.
– para[2] indicates the ID of the alarmed FPGA clock.
l 0x08 0x01 0xff: The SI5327 chip ID is incorrect.
TNW1SL41O 0x0f 0x02: The board hardware is damaged.
TNW1UCX l 0x08 para[2] para[3]: A bus is abnormal.
(SCC), – para[2] indicates the ID of the faulty chip.
TNW1UCXE
(SCC) – para[3] indicates the ID of the faulty bus.
l 0x12 para[2] para[3]: A clock component is faulty.
– para[2] indicates the ID of the checked dedicated chip. The value
0xff indicates the control logic check.
– para[3] indicates the ID of the checked clock register.
l 0x14 para[2]: A power component is faulty.
– para[2] indicates the ID of the checked AD chip. The value 0xff
indicates the control logic check.
l 0x14 0x05 0x04 0x00: The 1.5 V power supply is overvoltage.
l 0x14 0x05 0x05 0x01: The 1.5 V power supply is undervoltage.
l 0x14 0x05 0x06 0x00: The 2.2 V power supply is overvoltage.
l 0x14 0x05 0x07 0x01: The 2.2 V power supply is undervoltage.
l 0x14 0x05 0x08 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x05 0x09 0x01: The 3.3 V power supply is undervoltage.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 337
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1UCX l 0x12 0x09: The 38 MHz clock output by the differential drive is lost.
(STG), l 0x12 0x0c: The active crystal oscillator on the clock chip is faulty.
TNW1UCXE
(STG) l 0x12 0x15: The clock chip is faulty.
l 0x16 0x0b: The 38 MHz VCXO is faulty.
l 0x12 0x20 0x01: The system 38 MHz clock is lost.
l 0x12 0x20 0x02: The system 2 kHz frame header is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 338
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1DIO(OSN l 0x12 0x00 0x0f: The 32 MHz clock is abnormal.
550/580) l 0x12 0x00 0x09: The 38 MHz clock is abnormal.
l 0x12 0x00 0x0e: The 2 kHz frame header is abnormal.
l 0x12 0x00 0x0a: The 65 MHz clock is abnormal.
l 0x12 0x00 0x0b: The 98 MHz clock is abnormal.
l 0x12 0x00 0x0c: The 77 MHz clock is abnormal.
l 0x16 0x00 0x00: The 32 MHz PLL fails.
l 0x16 0x00 0x02: The 155 MHz PLL fails.
l 0x14 0x00 0x2 0x00: The 3.3 V power supply is overvoltage.
l 0x14 0x00 0x2 0x01: The 3.3 V power supply is undervoltage.
l 0x14 0x00 0x2 0x02: The 3.3 V power supply of the backplane is
overvoltage.
l 0x14 0x00 0x2 0x03: The 3.3 V power supply of the backplane is
undervoltage.
l 0x14 0x00 0x3 0x00: The 2.5 V power supply is overvoltage.
l 0x14 0x00 0x3 0x01: The 2.5 V power supply is undervoltage.
l 0x14 0x00 0x5 0x00: The 1.2 V power supply is overvoltage.
l 0x14 0x00 0x5 0x01: The 1.2 V power supply is undervoltage.
l 0x14 0x00 0x9 0x00: The 1.15 V power supply is overvoltage.
l 0x14 0x00 0x9 0x01: The 1.15 V power supply is undervoltage.
l 0x14 0x00 0x7 0x00: The 5.0 V power supply is overvoltage.
l 0x14 0x00 0x7 0x01: The 5.0 V power supply is undervoltage.
l 0x14 0x00 0xa 0x00: The 1.05 V power supply is overvoltage.
l 0x14 0x00 0xa 0x01: The 1.05 V power supply is undervoltage.
l 0x30 0x2: The board FPGA is lost.
l 0x30 0x1: The board driver is lost.
l 0x0f 0x1: The SMB bus is abnormal.
l 0x0f 0x2: The board FPGA fails to be loaded.
l 0x0f 0x3: Drivers of the system control board and current board fail
to be loaded.
l 0x0e 0xff 0x1: The EEPROM is faulty.
l 0x15 0x00 0x0c: Temperature fails to be read.
l 0x01 0x00 0x01: The system clock of the timing board with a
smaller slot ID is lost.
l 0x01 0x00 0x02: The system clock of the timing board with a greater
slot ID is lost.
l 0x01 0x00 0x03: The system clocks of both timing boards are lost.
l 0x01 0x01 0x01: The 66M system clock of the timing board with a
smaller slot ID is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 339
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
l 0x01 0x01 0x02: The 66M system clock of the timing board with a
greater slot ID is lost.
l 0x01 0x01 0x03: The 66M system clocks of both timing boards are
lost.
l 0x20 0x00: The 16244 clock chip is faulty.
Impact on the System
A board that reports a HARD_BAD alarm cannot work properly. If the board is a standby
board, an active/standby switchover cannot be performed.
Possible Causes
Possible causes of the HARD_BAD alarm are as follows:
l The board is not properly connected to the main board.
l A BUS_ERR alarm is reported.
l The board software version does not match the NE software version.
l The power supply fails.
l The board is faulty.
l The main board is faulty.
Procedure
Step 1 Query the HARD_BAD alarm on the NMS to determine the board that has reported the alarm
and to identify the cause based on the alarm parameters.
Step 2 Check whether the board is properly connected to the main board.
If... Then...
The board is not properly connected to the Re-install the board to ensure that the board
main board is properly connected to the main board.
Check whether the HARD_BAD alarm is
cleared. If the alarm persists, go to the next
step.
The board is properly connected to the main Go to the next step.
board
Step 3 On the NMS, check whether a BUS_ERR alarm has been reported.
If... Then...
A 4.2.46 BUS_ERR alarm has been Clear the BUS_ERR alarm. Check whether
reported the HARD_BAD alarm is cleared. If the
alarm persists, go to the next step.
No 4.2.46 BUS_ERR alarm is reported Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 340
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 Check whether the board software version matches the NE software version.
If... Then...
The board software version does not match Upgrade the software. Check whether the
the NE software version HARD_BAD alarm is cleared. If the alarm
persists, go to the next step.
The board software version matches the NE Go to the next step.
software version
Step 5 On the NMS, check whether a POWER_ABNORMAL alarm has been reported.
NOTE
If the NE is powered off and immediately powered on, the board detects abnormal voltage and reports a
POWER_ABNORMAL alarm.
If... Then...
A 4.2.389 POWER_ABNORMAL alarm Reconnect the NE to the power supply
is reported device or replace the power supply device
with a stable one to clear the
POWER_ABNORMAL alarm. Check
whether the HARD_BAD alarm is cleared.
If the alarm persists, go to the next step.
No 4.2.389 POWER_ABNORMAL alarm Go to the next step.
is reported
Step 6 Check whether a service board or system control, switching, and timing board is faulty.
If... Then...
A board is faulty Reseat and replace service boards and
system control, switching, and timing
boards in turn. Check whether the
HARD_BAD alarm is cleared. If the alarm
persists, go to the next step.
No board is faulty Go to the next step.
Step 7 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 341
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.158 HARD_ERR
Description
The HARD_ERR alarm indicates a hardware error. The alarm occurs when the board
hardware has a minor fault.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 342
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the fault type of the alarm. For example:
0x01
l EM20, EM10: indicates that the clock chip is faulty.
l Other boards: indicates that the power supply module is abnormal.
0x02 indicates that the board is not properly installed (the board is not in
good contact with the backplane, that is, the board is not secured).
0x03 indicates that 38M system clock 1 is abnormal.
0x04 indicates that 38M system clock 2 is abnormal.
0x05 indicates that the 2M clock source is abnormal.
0x06 indicates the digital phase-locked loop is abnormal.
0x07 indicates that the 38M service clock is lost.
0x08
l HUNS3: indicates that the temperature is abnormal.
l Other boards: indicates that the bus is abnormal.
0x09 indicates that the standby board in TPS protection is abnormal.
0x0a indicates the active crystal oscillator of the clock stops.
0x0b indicates the frequency deviation of the crystal oscillator is excessively
large.
0x0c
l HUND2: indicates that the Interlank bus is faulty.
l Other boards: indicates that the standby crystal oscillator of the clock
stops.
0x0d indicates that the CPU/DSP/coprocessor fails.
0x0e indicates that the memory component the fails.
0x0f indicates that the component of the programmable logic device fails.
0x10 indicates that the SDH component fails.
0x11 indicates that the data communication component fails.
0x12 indicates that the clock component fails.
0x13 indicates that the interface component fails.
0x14 indicates that the power component fails.
0x15 indicates that other faults occur.
0x16 indicates that the simulated phase-locked loop (PLL) is abnormal.
0x17 indicates that the 32M clock is invalid.
0x18 indicates that the 66M clock is invalid.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 343
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
0x19
l EM10: indicates that an I2C bus abnormality occurs.
l Other boards: indicates that the 25M clock is invalid.
0x1a indicates that the loop of the cross-connect chip fails.
0x1b indicates that the 8k online signal is pulled down.
0x1c indicates that the chip of the probe laser fails.
0x1d indicates that the chip of the loading laser fails.
0x1e indicates that the clock of the DSP driver chip is lost.
0x1f indicates that the output clock of the DSP is lost.
0x20 indicates that the RTM module is offline.
0x21 indicates that a chip fault.
0x22 indicates the 2M system frame header 1.
0x23 indicates the 2M system frame header 2.
0x24 indicates that the self-check fails.
0x25 indicates the self-check of the PHY chip fails.
0x26 indicates that detecting the port status of the PHY chip fails.
0x27 indicates that the 25M clock is lost.
0x28 indicates that the APD fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 344
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameters 2 l HUNS3: When Parameter 1 is 0x08, it indicates that the temperature is
and abnormal. When Parameter 3 is 0xff and Parameter 2 is 0x01, it indicates
Parameters 3 that the temperature is excessively low. When Parameter 2 is 0x02, it
indicates that the temperature is too high.
l HUND2, EM10, and EM20: When Parameter 1 is 0x01, it indicates that
the clock chip is faulty. When Parameter 2 is 0x01 and Parameter 3 is
0xff, it indicates that the 1588 second frame header is faulty.
l HUND2: When Parameter 1 is 0x0c, it indicates that the Interlank bus is
faulty. When Parameter 2 is 0x01, it indicates that the Interlank bus
between SD8752 and SD5890 is abnormal. Parameter 3 indicates the ID
of the faulty channel.
l HUNS3, HUND2, EM10, and EM20: When Parameter 1 is 0x0d, it
indicates that the processor is faulty. When Parameter 2 is 0x90, it
indicates that a soft error occurs on the SD5890 chip. Parameter 3
indicates the internal module of the SD5890 chip.
l HUNS3, EM10, and EM20: When Parameter 1 is 0x12, it indicates that a
clock component fault occurs. Parameter 3 is always 0xff. The meanings
of Parameter 2 are as follows:
– 0x0001: 669M
– 0x0002: 38M clock of XCS A
– 0x0003: 38M clock of XCS B
– 0x0004: 2K clock of XCS A
– 0x0005: 2K clock of XCS B
– 0x0006: SD5890 synchronous Ethernet recovery clock
– 0x0007: Phy1 synchronous Ethernet recovery clock
– 0x0008: Phy2 synchronous Ethernet recovery clock
– 0x0009: Phy3 synchronous Ethernet recovery clock
l EM10 and EM20: When Parameter 1 is 0x14, it indicates that a power
supply fault occurs. When Parameter 2 is 0x08 and Parameter 3 is 0xff, it
indicates that the backup 3.3 V voltage is abnormal.
l EM10 and EM20: When Parameter 1 is 0x15, it indicates that other faults
occur. When Parameter 2 is 0x01 and Parameter 3 is 0xff, it indicates that
the I2C bus is abnormal.
l HUND2, EM10, and EM20: When Parameter 1 is 0x16, it indicates that
an analog PLL fault occurs. When Parameter 3 is 0xff and Parameter 2 is
0x1, it indicates that the SPI is abnormal. When Parameter 2 is 0x2, it
indicates that the flash logic fails to be loaded automatically.
l EM10: When Parameter 1 is 0x19, it indicates that the I2C bus is faulty.
When Parameter 2 is 0xff, it indicates that the I2C bus of the optical
module is abnormal. Parameter 3 indicates the optical module number.
Other boards:
l When Parameter 1 is 0x08 and Parameter 2 is 0x01, it indicates that bus
A is abnormal; When Parameter 1 is 0x08 and Parameter 2 is 0x02, it
indicates that bus B is abnormal. Parameter 3 is 0xff.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 345
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
l When Parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16,
0x19, or 0x21, Parameter 2 and Parameter 3 have different values, which
indicate different component, module, or chip faults.
l When Parameter 1 is 0x15, a fault on other units of the local board, a
fault on other boards, or a fault on other units of other boards.
l When Parameter 1 is of another value, Parameter 2 and Parameter 3 are
always 0xff.
Impact on the System
The services are not affected. For specific influence, see Parameter 1.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Perform warm reset or cold reset on the faulty board through the NMS.
Step 2 If the alarm persists, replace the faulty board.
----End
Related Information
None
4.2.159 HARD_NONSUPPORT
Description
The HARD_NONSUPPORT is an alarm indicating that a certain function is not supported by
a board. A function is configured on the device and a command is issued by the system to
enable the function on a board. If the board hardware does not support this function, this
alarm is reported.
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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 346
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates functions that are not supported by a board.
l 0x01: ETH PWE3 control word
l 0x02: N/A
Impact on the System
The ETH PWE3 control word function is unavailable if this alarm is reported.
Possible Causes
The possible cause of the HARD_NONSUPPORT alarm is as follows:
Cause: The board does not support the ETH PWE3 control word function even though it is
configured on the device.
Procedure
Step 1 Replace the board with a new one that supports the ETH PWE3 control word function.
----End
Related Information
None.
4.2.160 HP_CROSSTR
Description
The HP_CROSSTR alarm indicates that a performance indicator of the higher order path
crosses the threshold.
Attribute
Alarm Severity Alarm Type
Minor Service quality 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 347
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1, The two most significant bits of Parameter 1 indicate the performance
Parameter 2 monitoring period.
l 0x01: 15 minutes
l 0x02: 24 hours
NOTE
The six least significant bits of Parameter 1 together with Parameter 2 indicate a
performance event ID.
Impact on the System
The number of bit errors in the higher order path module crosses the threshold. As a result, the
service quality may deteriorate or services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The performance of the laser on the line board at the opposite end deteriorates.
l The clock performance at the local or opposite end deteriorates.
l The receive optical power of the line board at the local end is out of range.
l The optical fiber performance deteriorates.
Procedure
Step 1 Check whether the performance of the laser on the line board at the opposite end deteriorates.
If... Then...
The laser performance deteriorates Replace the laser. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The laser performance does not deteriorate Go to the next step.
Step 2 Check whether the clock performance at the local or opposite end deteriorates.
If... Then...
The clock performance deteriorates Re-configure clock tracing. After the
configured performance monitoring period
ends, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The clock performance does not deteriorate Go to the next step.
Step 3 Check whether the receive optical power of the line board at the local end is out of range.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 348
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The receive optical power is higher than the Use an optical power attenuator to decrease
upper threshold the value of the receive optical power. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The receive optical power is lower than the Increase the value of the input optical
lower threshold power. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The receive optical power is within the Go to the next step.
specified range
Step 4 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
The timing unit at the opposite end reports a The timing unit at the opposite end is faulty.
higher order adaptation performance event Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The timing unit at the local end reports a The timing unit at the local end is faulty.
higher order adaptation performance event Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
Step 5 Check whether the optical fiber performance deteriorates.
If... Then...
The optical fiber performance deteriorates Replace the optical fiber.
The optical fiber performance does not Contact Huawei technical support engineers
deteriorate to handle the alarm.
----End
Related Information
None.
4.2.161 HP_LOM
Description
The HP_LOM alarm indicates loss of multiframes in the higher order path.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 349
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Parameter 2, Parameter 3 Indicates the path ID.
Impact on the System
The value of the H4 byte 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.
The board inserts VTAIS into the corresponding path (the TU_AIS alarm is reported on the
tributary board).
Possible Causes
Possible causes of this alarm are as follows:
l Service configurations are incorrect.
l The H4 byte is lost or has an invalid value.
Procedure
Step 1 Check whether the service configurations at the opposite end and the local end are correct. If
the service configurations are incorrect, modify the configurations and apply the
configurations again.
Step 2 Check on the U2000 whether the HP_LOM alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 3 Perform an optical path self-loop to check whether the cross-connect unit and the line board at
the opposite end are faulty. If it can be determined that the fault is caused by the opposite end,
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 350
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
replace the line board at the opposite end. If the alarm persists, replace the system control,
cross-connect, and timing board at the opposite end.
Step 4 Check on the U2000 whether the HP_LOM alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 5 It can be determined that a board at the local end is faulty. Replace the faulty board.
----End
Related Information
None.
4.2.162 HP_R_FIFO
Description
The HP_R_FIFO alarm indicates FIFO overflow on the receive side of the higher order path
on the line board.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Parameter 2, Parameter 3 Indicates the path ID.
Impact on the System
Services cannot be correctly received and may be interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 351
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of this alarm is as follows:
l The frequency difference between the performance of the received and transmitted
clocks is over great.
Procedure
Step 1 Check the configuration of the service clock and system clock. If the configuration is
incorrect, correct the configuration.
----End
Related Information
None.
4.2.163 HP_RDI
Description
The HP_RDI alarm indicates that the board at the local end receives from the board at the
opposite end a message indicating a remote receive failure in the higher order path.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-4 path ID.
Impact on the System
This alarm indicates that the remote path-level services are interrupted, and it does not have
any impact on the local end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 352
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The opposite end receives the AU_AIS, AU_LOP, HP_SLM, or HP_TIM alarm.
l The receive unit at the opposite end is faulty.
l The transmit unit at the local end is faulty.
Procedure
Step 1 Check whether the opposite end reports a higher order alarm.
If... Then...
The opposite end reports the AU_AIS, Clear the AU_AIS, AU_LOP, HP_TIM, or
AU_LOP, HP_TIM, or HP_SLM alarm HP_SLM alarm. Then, check whether the
HP_RDI alarm is cleared. If the HP_RDI
alarm persists, go to the next step.
The opposite end does not report the Go to the next step.
AU_AIS, AU_LOP, HP_TIM, or
HP_SLM alarm
Step 2 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
A board at the opposite end reports the The board at the opposite end is faulty.
HP_RDI alarm Replace the faulty board.
A board at the local end reports the HP_RDI The board at the local end is faulty. Replace
alarm the faulty board.
----End
Related Information
AU_AIS, AU_LOP, HP_TIM, HP_SLM
4.2.164 HP_REI
Description
The HP_REI alarm indicates that the board at local end receives from the board at the
opposite end a message indicating remote bit errors in the higher order path.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 353
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Warning Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-4 path ID.
Impact on the System
This alarm indicates that NEs along the service trail receive bit errors and the quality of
higher order services deteriorates. This alarm does not have any impact on the local end.
Possible Causes
The possible cause of this alarm is as follows:
The opposite end receives a B3 bit error alarm, such as B3_EXC or B3_SD.
Procedure
Step 1 Check whether the equipment is securely grounded and there are any intense interference
sources around the equipment.
NOTE
If a few B3 bit errors occur at the opposite end, the fault usually lies in the equipment instead of the
optical path.
If... Then...
The equipment is poorly grounded Ground the equipment securely. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
There is an intense interference source Move the interference source away, or
around the equipment install the equipment at a position far away
from the interference source. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 354
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The equipment is securely grounded, and Go to the next step.
there is no intense interference source
around the equipment
Step 2 Check whether the opposite end reports a B3 bit error alarm, such as B3_EXC or B3_SD.
If... Then...
The opposite end reports the 4.2.26 Clear the 4.2.26 B3_EXC or 4.2.29 B3_SD
B3_EXC or 4.2.29 B3_SD alarm alarm. Then, check whether the HP_REI
alarm is cleared. If the HP_REI alarm
persists, go to the next step.
The opposite end does not report the4.2.26 Go to the next step.
B3_EXC or 4.2.29 B3_SD alarm
Step 3 Perform loopbacks at the local end and the opposite end to check whether the cross-connect
units and the tributary boards at the two ends are properly functioning. Check upstream NEs
one by one to locate the faulty board.
If... Then...
A board at the opposite end reports a B3 bit The receive unit at the opposite end is
error alarm faulty. Replace the line board first. If the
alarm persists, replace the tributary board. If
the alarm still persists, replace the system
control, cross-connect, and timing board.
A board at the local end reports a B3 bit The transmit unit at the local end is faulty.
error alarm Replace the faulty board.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.165 HP_SLM
Description
The HP_SLM alarm indicates inconsistent higher order path signal labels (C2 bytes).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 355
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-4 path ID.
Impact on the System
The services in the payload are unavailable, resulting in service interruption.
If the AIS insertion is enabled upon detection of the HP_SLM alarm, the local end sends the
HP_RDI alarm to the opposite end.
Possible Causes
Possible causes of this alarm are as follows:
l The label of higher order path signals (C2 byte) that the local end is supposed to receive
is inconsistent with the label of higher order path signals (C2 byte) transmitted by the
opposite end.
l Service configurations are incorrect.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether the configuration of the higher order path signal label (C2 byte) that the local
end is supposed to receive is inconsistent with the configuration of the higher order path
signal label (C2 byte) transmitted by the opposite end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 356
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The configuration of the higher order path Ensure that the configuration of the higher
signal label (C2 byte) that the local end is order path signal label (C2 byte) that the
supposed to receive is inconsistent with the local end is supposed to receive is consistent
configuration of the higher order path signal with the configuration of the higher order
label (C2 byte) transmitted by the opposite path signal label (C2 byte) transmitted by
end the opposite end. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The configuration of the higher order path Go to the next step.
signal label (C2 byte) that the local end is
supposed to receive is consistent with the
configuration of the higher order path signal
label (C2 byte) transmitted by the opposite
end
Step 2 Check whether service configurations at the local end and the opposite end are correct.
If... Then...
The service configurations are incorrect Correct the service configurations. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The service configurations are correct Go to the next step.
Step 3 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
A board at the opposite end reports the The transmit unit at the opposite end is
HP_SLM alarm faulty. Replace the line board first. If the
alarm persists, replace the system control,
cross-connect, and timing board.
A board at the local end reports the The receive unit at the local end is faulty.
HP_SLM alarm Replace the faulty board.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 357
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.166 HP_T_FIFO
Description
The HP_T_FIFO alarm indicates FIFO overflow on the transmit side of the higher order path
on the line board.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Parameter 2, Parameter 3 Indicates the path ID.
Impact on the System
Services cannot be transmitted and may be interrupted.
Possible Causes
The possible cause of this alarm is as follows:
l The frequency difference between the performance of the received and transmitted
clocks is over great.
Procedure
Step 1 Check the configuration of the service clock and system clock. If the configuration is
incorrect, correct the configuration.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 358
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.167 HP_TIM
Description
The HP_TIM alarm indicates inconsistent higher order path trace identifiers (J1 bytes).
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-4 path ID.
Impact on the System
The services in the payload are unavailable, resulting in service interruption.
If the AIS insertion is enabled upon detection of the HP_TIM alarm, the local end sends the
HP_RDI alarm to the opposite end.
Possible Causes
Possible causes of this alarm are as follows:
l The higher order path trace identifier (J1 byte) that the local end is supposed to receive is
inconsistent with the higher order path trace identifier (J1 byte) transmitted by the
opposite end.
l Service configurations are incorrect.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether the configuration of the higher order path trace identifier (J1 byte) that the
local end is supposed to receive is consistent with the configuration of the higher order path
trace identifier (J1 byte) transmitted by the opposite end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 359
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The configuration of the higher order path Ensure that the configuration of the higher
trace identifier (J1 byte) that the local end is order path trace identifier (J1 byte) that the
supposed to receive is inconsistent with the local end is supposed to receive is consistent
configuration of the higher order path trace with the configuration of the higher order
identifier (J1 byte) transmitted by the path trace identifier (J1 byte) transmitted by
opposite end the opposite end. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The configuration of the higher order path Go to the next step.
trace identifier (J1 byte) that the local end is
supposed to receive is consistent with the
configuration of the higher order path trace
identifier (J1 byte) transmitted by the
opposite end
Step 2 Check whether service configurations at the local end and the opposite end are correct.
If... Then...
The service configurations are incorrect Correct the service configurations. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The service configurations are correct Go to the next step.
Step 3 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
A board at the opposite end reports the The transmit unit at the opposite end is
HP_SLM alarm faulty. Replace the line board first. If the
alarm persists, replace the system control,
cross-connect, and timing board.
A board at the local end reports the The receive unit at the local end is faulty.
HP_SLM alarm Replace the faulty board.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 360
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.168 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path is unequipped. The actually
received C2 byte is 0x00.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number. The parameter has a fixed
value of 0x01.
Parameter 2, Parameter 3 Indicate the VC-4 path ID.
Impact on the System
The payload of signals transmitted by the board at the opposite end is not loaded with services
and services are interrupted.
If the AIS insertion is enabled upon detection of the HP_UNEQ alarm, the local end sends the
HP_RDI alarm to the opposite end.
Possible Causes
Possible causes of this alarm are as follows:
l The C2 byte is set to 0 at the opposite end.
l No services are configured in the transmit direction of the board at the opposite end.
l A board at the local end is faulty.
Procedure
Step 1 Check whether the C2 byte is set to 0 at the opposite end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 361
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The C2 byte is set to 0 Change the value of the C2 byte. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The C2 byte is not set to 0 Go to the next step.
Step 2 Check whether any services are configured in the transmit direction of the board at the
opposite end.
If... Then...
No services are configured Configure services in the transmit direction
of the board at the opposite end. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
Services are configured Go to the next step.
Step 3 Replace the faulty board at the local end. Then, check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.169 HPAD_CROSSTR
Description
The HPAD_CROSSTR alarm indicates that the higher order path adaptation performance
crosses the threshold.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 362
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the performance monitoring period.
l 0x01: The monitoring period is 15 minutes.
l 0x02: The monitoring period is 24 hours.
Parameter 2, Parameter 3 Indicate the ID of the threshold-crossing performance item.
Impact on the System
The quality of lower order services deteriorates or lower order services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The clock fails.
l The performance of the laser on the line board at the opposite end deteriorates.
l The receive optical power of the line board at the local end is out of range.
Procedure
Step 1 Check whether the clock tracing configurations at the local end and the entire network are
correct.
If... Then...
The clock tracing configurations are Modify the clock tracing configurations.
incorrect After the configured performance
monitoring period ends, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock tracing configurations are correct Go to the next step.
Step 2 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
The timing unit at the opposite end reports a The timing unit at the opposite end is faulty
higher order adaptation performance event Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The timing unit at the local end reports a The timing unit at the local end is faulty.
higher order adaptation performance event Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 363
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the optical attenuator does not match or is faulty, or whether the optical fiber
is broken.
If... Then...
The optical attenuator does not match or is Replace the optical attenuator.
faulty
The optical fiber is broken Replace the optical fiber.
The optical attenuator and fiber are Contact Huawei technical support engineers
functioning properly to handle the alarm.
----End
Related Information
None.
4.2.170 HSC_UNAVAIL
Description
The HSC_UNAVAIL alarm indicates that the hot-standby status of an SCC board is abnormal.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the working/protection status of the alarmed SCC board.
l 0x00: Working
l 0x01: Protection
Parameter 2 Indicates the slot ID of the alarmed SCC board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 364
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the alarm type.
l 0x01: The alarmed SCC board is in the bad status.
l 0x02: A service board detects the bad state of the alarmed SCC
board.
l 0x04: The alarmed SCC board detects a type II BUS_ERR alarm.
l 0x80: The time, which elapsed after a successful cold reset on the
alarmed SCC board, is less than five minutes.
Parameter 4, The values are always 0xff, and these parameters are meaningless.
Parameter 5
Impact on the System
If protection switching is implemented between the working and protection SCC boards when
an HSC_UNAVAIL alarm persists, services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The alarmed SCC board is being upgraded.
l Cause 2: The protection SCC board was cold reset 5 minutes or less ago.
l Cause 3: The working and protection SCC boards have inconsistent database versions.
l Cause 4: The protection SCC board cannot be detected or is faulty.
l Cause 5: The backplane is faulty.
Procedure
Step 1 Cause 1: The alarmed SCC board is being upgraded.
1. No operation is required. The HSC_UNAVAIL alarm may indicate that database backup
on the alarmed SCC board is not complete. If this is the case, the HSC_UNAVAIL alarm
automatically clears after the database backup is complete. Do not perform any
operations when the HSC_UNAVAIL alarm persists.
2. Check whether the alarm clears. If the alarm persists, go to Step 2.
Step 2 Cause 2: The protection SCC board was cold reset 5 minutes or less ago.
1. No operation is required. The HSC_UNAVAIL alarm may indicate that the protection
SCC board is synchronizing data with the working SCC board (5 to 8 minutes required).
If this is the case, do not cold reset or remove the working SCC board when the
HSC_UNAVAIL alarm persists.
2. Check whether the alarm clears. If the alarm persists, go to Step 3.
Step 3 Cause 3: The working and protection SCC boards have inconsistent database versions.
1. Check whether the working and protection SCC boards have consistent database
versions. For details, see Querying the Board Information Report.
2. If the working and protection SCC boards have inconsistent database versions, contact
Huawei engineers to upgrade software.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 365
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
3. Check whether the alarm clears. If the alarm persists, go to Step 4.
Step 4 Cause 4: The protection SCC board cannot be detected or is faulty.
1. Check whether the protection SCC board can be detected or is faulty. If the protection
SCC board cannot be detected, install an SCC board; if the protection SCC board is
faulty, replace it.
2. Check whether the alarm clears. If the alarm persists, go to Step 5.
Step 5 Cause 5: The backplane is faulty.
1. Check for a BUS_ERR or T_LOSEX alarm. If either alarm exists, clear it.
2. Check whether the alarm clears. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
4.2.171 HPS_WP_LATEN_DIFF
Description
The HPS_WP_LATEN_DIFF alarm indicates that the delay difference between the working
and protection paths of the hitless protection group exceeds the threshold. This alarm is
reported when the delay difference exceeds 12 ms.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the hitless protection group ID.
Impact on the System
The hitless protection group cannot provide protection services normally, and hitless
protection is unavailable for received services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 366
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible causes of the HPS_WP_LATEN_DIFF alarm are as follows:
l Cause 1: The distance between the physical links of the working and protection paths of
the hitless protection group is excessively long.
l Cause 2: There are excessive lower-order VC-12 cross-connections on the link.
Procedure
Step 1 Locate the hitless protection group according to the alarm parameters.
Step 2 Cause 1: The distance between the physical links of the working and protection paths of the
hitless protection group is excessively long.
1. Adjust the physical link of the working or protection path to shorten the distance
between the two physical links.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
3. If the alarm is cleared, reset the protection group.
Services are transiently interrupted during the reset process.
Step 3 Cause 2: There are excessive lower-order VC-12 cross-connections on the link.
1. Check whether the number of NEs on the physical link of the working path are much
greater or less than that on the physical link of the protection path.
If… Then...
Yes – Adjust the physical link of the
working or protection path.
– Check whether the alarm is cleared. If
the alarm persists, go to Step 3.2.
– If the alarm is cleared, reset the hitless
protection group.
NOTICE
Services are transiently interrupted during
the reset process.
No Go to Step 3.2.
2. Check whether the number of VC-12 cross-connections on the NE in the working path
are much greater or less than that on the NE in the protection path.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 367
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
Yes – Adjust the number of VC-12 cross-
connections on the NE in the working
or protection path.
– Check whether the alarm is cleared. If
the alarm persists, go to Step 3.2.
– If the alarm is cleared, reset the hitless
protection group.
NOTICE
Services are transiently interrupted during
the reset process.
No Go to Step 4.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.172 HPS_WP_LATEN_JITTER
Description
The HPS_WP_LATEN_JITTER alarm indicates that the delay jitter in the working or
protection path (long or short path) of the hitless protection group exceeds the threshold. This
alarm is reported when the delay jitter exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the hitless protection group ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 368
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The corresponding path fails to support delay alignment, and the protection path fails to
provide hitless switching. If the working path is faulty, services will be transiently interrupted
during protection group switching.
Possible Causes
The possible causes of the HPS_WP_LATEN_JITTER alarm are as follows:
l Cause 1: The network configurations of the transmission paths are adjusted.
l Cause 2: The devices on the transmission paths are replaced, upgraded, or expanded,
which causes the circuit processing delay to change.
Procedure
Step 1 Check whether the 4.2.171 HPS_WP_LATEN_DIFF alarm exists on the NE. If the alarm
exists, clear it first.
Step 2 Reset the hitless protection group.
Services are transiently interrupted during the reset process.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.173 IGSP_ENTRIES_EXC
Description
The IGSP_ENTRIES_EXC alarm is reported when the number of IGMP Snooping multicast
table entries exceeds its upper threshold, and will be cleared when the number of IGMP
Snooping multicast table entries is smaller than its lower threshold.
Attribute
Alarm Severity Alarm Type
Minor Security 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 369
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates whether the number of IGMP Snooping multicast table entries
exceeds its upper threshold.
l 0x00: indicates that the number of IGMP Snooping multicast table entries
does not exceed its upper threshold.
l 0x01: indicates that the number of IGMP Snooping multicast table entries
exceeds its upper threshold.
Parameter 2 Indicates whether the number of IGMP Snooping multicast group members
exceeds its upper threshold.
l 0x00: indicates that the number of IGMP Snooping multicast group
members does not exceed its upper threshold.
l 0x01: indicates that the number of IGMP Snooping multicast group
members exceeds its upper threshold.
Impact on the System
After the IGSP_ENTRIES_EXC alarm is reported, the IGMP Snooping multicast table has no
more space for learning new table entries. As a result, some IGMP service packets will be
discarded.
Possible Causes
l Cause 1: The configured upper threshold for the number of IGMP Snooping multicast
table entries is too small.
l Cause 2: IGMP Snooping protocol attack packets are generated on the network.
Procedure
Step 1 Cause 1: The configured upper threshold for the number of IGMP Snooping multicast table
entries is too small.
1. Check whether the configured upper threshold for the number of IGMP Snooping
multicast table entries is too small. If the upper threshold is too small, set another larger
value according to the network plan.
2. Check whether the alarm is cleared. If it persists, go to Step 2.
Step 2 Cause 2: IGMP Snooping protocol attack packets are generated on the network.
1. Check whether IGMP Snooping protocol attack packets are generated on the network.
Upon detection of any IGMP Snooping attack packets, locate the attack source and
shield it.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 370
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.174 IMA_GROUP_LE_DOWN
Description
The IMA_GROUP_LE_DOWN alarm indicates that the IMA protocol is not enabled on the
local NE or the number of activated links in an IMA group is smaller than the preset
minimum number of activated links.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
Services in the IMA group are interrupted.
Possible Causes
Possible causes of the IMA_GROUP_LE_DOWN alarm are as follows:
l The IMA group configurations at the local end are different from those at the opposite
end.
l The number of activated links in the local IMA group is smaller than the preset
minimum number of activated links.
l The IMA group at the local end is in the blocked or startup state.
Procedure
Step 1 Check whether IMA group configurations at the local end are different from those at the
opposite end.
If... Then...
The IMA group configurations are 1. Perform operations as described in
inconsistent Configuring IMA in the Feature
Description.
2. On the U2000, set IMA Protocol
Enable Status to Enabled for the local
NE.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 371
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The IMA group configurations are Go to the next step.
consistent
Step 2 On the U2000, check whether the ALM_IMA_LIF alarm has been reported.
If... Then...
This alarm persists 1. Clear the ALM_IMA_LIF alarm and
activate the member links in the local
IMA group.
2. When the actual number of activated
links reaches the configured minimum
activated link number, the
IMA_GROUP_LE_DOWN alarm will
be cleared automatically.
3. Optional: Add member links in the local
IMA group.
The alarm is cleared Go to the next step.
Step 3 Check whether the local IMA group is in a blocked or startup state.
If... Then...
The T_ALOS or R_LOS alarm is reported Clear the T_ALOS or R_LOS alarm first.
Check whether the
IMA_GROUP_LE_DOWN alarm is
cleared. If the IMA_GROUP_LE_DOWN
alarm persists, go to the next step.
No T_ALOS or R_LOS alarm is reported No further action is required.
----End
Related Information
4.2.8 ALM_IMA_LIF, 4.2.473 T_ALOS, 4.2.420 R_LOS
4.2.175 IMA_GROUP_RE_DOWN
Description
The IMA_GROUP_RE_DOWN alarm indicates that the IMA protocol is not enabled on the
remote NE or that the number of activated links in the IMA group is less than the configured
minimum activated link number.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 372
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
Services in the IMA group are interrupted.
Possible Causes
Possible causes of the IMA_GROUP_RE_DOWN alarm are as follows:
l The IMA group configurations at the local end are different from those at the opposite
end.
l The number of activated links in the local IMA group is smaller than the preset
minimum number of activated links.
l The IMA group at the local end is in the blocked or startup state.
Procedure
Step 1 Check whether IMA group configurations at the local end are different from those at the
opposite end.
If... Then...
The IMA group configurations are 1. Perform operations as described in
inconsistent Configuring IMA in the Feature
Description.
2. On the U2000, set IMA Protocol
Enable Status to Enabled for the local
NE.
The IMA group configurations are Go to the next step.
consistent
Step 2 On the U2000, check whether the ALM_IMA_LIF alarm has been reported.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 373
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
This alarm persists 1. Clear the ALM_IMA_LIF alarm and
activate the member links in the local
IMA group.
2. When the actual number of available
links reaches the configured minimum
available link number, the
IMA_GROUP_RE_DOWN alarm will
be cleared automatically.
3. Optional: Add member links in the local
IMA group.
The alarm is cleared Go to the next step.
Step 3 Check whether the local IMA group is in a blocked or startup state.
If... Then...
The T_ALOS or R_LOS alarm is reported Clear the T_ALOS or R_LOS alarm first.
Check whether the
IMA_GROUP_RE_DOWN alarm is
cleared. If the IMA_GROUP_RE_DOWN
alarm persists, go to the next step.
No T_ALOS or R_LOS alarm is reported No further action is required.
----End
Related Information
4.2.12 ALM_IMA_RFI, 4.2.473 T_ALOS, 4.2.420 R_LOS
4.2.176 IMA_TXCLK_MISMATCH
Description
The IMA_TXCLK_MISMATCH alarm indicates that the clock transmission mode at one end
of an IMA group is different from that at the other end.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 374
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
ATM cells may be lost, consequently affecting services.
Possible Causes
The possible cause of the IMA_TXCLK_MISMATCH alarm is as follows:
The clock transmission mode at one end of an IMA group is different from that at the other
end.
Procedure
Step 1 View the alarm information on the U2000 and determine the ATM trunk (on which board and
which NE) that reports the alarm.
Step 2 Query the clock mode of the ATM trunk that reports the alarm and check whether the clock
modes at both ends of the IMA group are consistent.
If... Then...
The clock modes at both ends of the IMA group Contact Huawei technical support
are consistent engineers to handle the alarm.
The clock modes at both ends of the IMA group Go to the next step.
are inconsistent
Step 3 Disable the IMA protocol of the ATM trunk and change the clock modes at both ends to the
same value. Enable the IMA protocol and check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.177 IN_PWR_ABN
Description
The IN_PWR_ABN alarm indicates that the input optical power of the laser on the board
crosses the lower or upper threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 375
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
Bit errors may occur during service transmission, service signals cannot be aligned, or
services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The input optical power is out of range.
l The fiber connector is dirty or loosely connected.
l The detector or amplifier circuit fails.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check the input optical power of the board.
If... Then...
The input optical power is higher than Increase the attenuation of signals in
the upper threshold transmission. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The input optical power is lower than the Decrease the attenuation of signals in
lower threshold transmission or increase the transmit optical
power at the opposite end. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The input optical power is within the Go to the next step.
specified range
Step 2 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
The transmit unit at the opposite end is Replace the faulty board at the opposite end.
faulty
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 376
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The receive unit at the local end is faulty Replace the faulty board at the local end.
----End
Related Information
None.
4.2.178 IN_PWR_HIGH
Description
The IN_PWR_HIGH alarm indicates that the actual input optical power is higher than the
upper threshold of the input power reference value.
Attribute
Alarm Severity Alarm Type
Critical Equipment
Parameters
None
Impact on the System
Bit errors occur in the services at optical ports. Over high input power also causes damages to
the laser.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The transmit power of the opposite end is over high.
l Cause 2: Inapplicable optical modules are used.
l Cause 3: The optical module at the receive end is faulty.
Procedure
Step 1 Cause 1: The transmit power of the opposite end is over high.
1. On the NMS, follow the instructions in Querying the Optical Power to check whether the
output power of the board connected to the alarm board is higher than that listed in
Specifications of Optical/Electrical Modules.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 377
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The output power is higher than that Add a proper attenuator at the receive
listed in Specifications of Optical/ end, and check whether the alarm is
Electrical Modules cleared. If the alarm persists, go to Step
2.
The output optical power is normal Go to Step 2.
Step 2 Cause 2: Inapplicable optical modules are used.
1. Check whether applicable optical modules are used at both receive and transmit ends
based on the transmission distance.
If... Then...
Inapplicable optical modules are used Replace the optical modules or board.
Applicable optical modules are used Go to Step 3.
Step 3 Cause 3: The optical module at the receive end is faulty.
1. Replace the optical module or board at the receive end.
2. Check whether alarm is cleared. If the alarm persists, contact Huawei technical support
personnel to handle the alarm.
----End
Related Information
None
4.2.179 IN_PWR_LOW
Description
The IN_PWR_LOW alarm indicates that the actual input optical power is lower than the
lower threshold of the input power reference value.
Attribute
Alarm Severity Alarm Type
Critical Equipment
Parameters
None
Impact on the System
Bit errors occur in the service at the optical port.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 378
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The bending radius of the fiber jumper is less than 6 cm, the optical fiber is
damaged, or the optical fiber connector is loose or dirty.
l Cause 2: The transmit power of the opposite end is over low.
l Cause 3: Inapplicable optical modules are used.
l Cause 4: The optical module at the receive end is faulty.
Procedure
Step 1 Cause 1: The bending radius of the fiber jumper is less than 6 cm, the optical fiber is
damaged, or the optical fiber connector is loose or dirty.
1. Check whether the bending radius of the fiber jumper is within the specified range. If the
bending radius is less than 6 cm, spool the fiber jumper again. Check whether the alarm
is cleared.
2. If the alarm persists, check whether the optical fiber is intact. If the optical fiber is
damaged, replace the optical fiber, and check whether the alarm is cleared.
3. If the alarm persists, check whether the fiber connector is firmly connected. Ensure that
the fiber connector is firmly connected, and check whether the alarm is cleared.
4. If the alarm persists, follow the instructions in Checking the Optical Fiber Connector to
check whether the fiber connector is clean and intact. If the fiber connector is dirty or
damaged, clean or replace the connector. For details, see Cleaning the Optical Fiber
Connector.
5. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The transmit power of the opposite end is over low.
1. On the NMS, follow the instructions in Querying the Optical Power to check whether the
output power of the board connected to the alarm board is lower than the value listed in
Specifications of Optical/Electrical Modules.
If... Then...
The output optical power is lower than Remove a proper attenuator at the receive
the value listed in Specifications of end, and check whether the alarm is
Optical/Electrical Modules cleared. If the alarm persists, go to Step
3.
The output optical power is normal Go to Step 3.
Step 3 Cause 3: Inapplicable optical modules are used.
1. Check whether applicable optical modules are used at both receive and transmit ends
based on the transmission distance.
If... Then...
Inapplicable optical modules are used Replace the optical modules or board.
Applicable optical modules are used Go to Step 4.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 379
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 Cause 4: The optical module at the receive end is faulty.
1. Replace the optical module or board at the receive end.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.180 INSUFFCNT_FLSH_SPACE
Description
The INSUFFCNT_FLSH_SPACE alarm indicates that the flash file space is insufficient.
l This alarm is reported when the flash space usage exceeds 95% for OSN 500 or OSN
550.
l This alarm is reported when the flash space usage exceeds 85% for OSN 580.
Attribute
Alarm Severity Alarm Type
Critical Processing failure 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the resource type.
l 0x00: ofs1
l 0x01: ofs2
Parameter 2 Indicates that the current flash space utilization.
Parameters 3 to 5 These parameters are reserved. Their values are always 0xff.
Impact on the System
File storage to the flash space fails.
Possible Causes
The file system space on the flash is insufficient.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 380
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check the alarm on the NMS for the specific alarmed flash space according to the alarm
parameters.
Step 2 Query the files stored in the alarmed flash space and check for any oversized files or extra
files.
Step 3 Delete oversized and extra files, if any.
Step 4 Check whether the alarm clears. If the alarm persists, contact Huawei engineers to handle the
alarm.
----End
Related Information
None.
4.2.181 INSUFFCNT_MEM_SPACE
Description
The INSUFFCNT_MEM_SPACE alarm indicates that the file system space in the memory is
insufficient.
l This alarm is reported when the flash space usage exceeds 95% for OSN 500 or OSN
550.
l This alarm is reported when the flash space usage exceeds 85% for OSN 580.
Attribute
Alarm Severity Alarm Type
Critical Processing failure 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the resource type.
l 0x00: mfs
Parameter 2 Indicates that the current memory space utilization.
Parameters 3 to 5 These parameters are reserved. Their values are always 0xff.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 381
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
l Package loading fails.
l Database backup fails.
Possible Causes
The file system space in the memory is insufficient.
Procedure
Step 1 Check the alarm on the NMS for the specific alarmed memory space according to alarm
parameters.
Step 2 Query the files stored in the alarmed memory space and check for any oversized files or extra
files.
Step 3 Delete oversized and extra files, if any.
Step 4 Check whether the alarm clears. If the alarm persists, contact Huawei engineers to handle the
alarm.
----End
Related Information
None.
4.2.182 INTEMP_SENSOR_FAIL
Description
The INTEMP_SENSOR_FAIL alarm indicates that the temperature sensor at the air intake
vent fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The equipment cannot collect the temperature data of the air intake vent on the TCU board.
Possible Causes
Possible causes of this alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 382
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l No temperature sensor is installed at the air intake vent.
l The temperature sensor at the air intake vent is incorrectly connected.
l The temperature sensor at the air intake vent is faulty.
l The control board of the cabinet is faulty.
Procedure
Step 1 Check whether a temperature sensor is installed at the air intake vent.
If... Then...
No temperature sensor is installed at the air Install a temperature sensor at the air intake
intake vent vent. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
A temperature sensor is installed at the air Go to the next step.
intake vent
Step 2 Check whether the temperature sensor at the air intake vent is correctly connected or the cable
is intact.
If... Then...
The temperature sensor at the air intake vent Connect the temperature sensor at the air
is incorrectly connected intake vent correctly. Then, check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The cable is damaged Replace the cable. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The temperature sensor at the air intake vent Go to the next step.
is correctly connected and the cable is intact
Step 3 Replace the temperature sensor at the air intake vent. Then, check whether the alarm is
cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 4 Replace the cabinet. Then, the alarm is automatically cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 383
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.183 J0_MM
Description
The J0_MM alarm indicates inconsistent regenerator section trace identifiers (J0 bytes).
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Impact on the System
None.
Possible Causes
The possible cause of this alarm is as follows:
l The regenerator section trace identifier (J0 byte) transmitted by the opposite end is not
the same as the regenerator section trace identifier (J0 byte) that the local end is
supposed to receive.
Procedure
Step 1 On the U2000, check whether the regenerator section trace identifier (J0 byte) transmitted by
the opposite end is the same as the regenerator section trace identifier (J0 byte) that the local
end is supposed to receive. Ensure that they are the same.
Step 2 Check on the U2000 whether the J0_MM alarm is cleared.
If... Then...
If this alarm is cleared No further action is required.
If this alarm persists Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 384
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 If the alarm persists, perform a self-loop with optical fibers for the optical ports on the line
boards at the two end. Replace the board that still reports the J0_MM alarm.
----End
Related Information
None.
4.2.184 K1_K2_M
Description
The K1_K2_M alarm indicates inconsistency between the transmitted K1 byte and received
K2 byte of a linear multiplex section protection (MSP) group.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
The automatic MSP switching may fail, and the protected services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The optical fibers are incorrectly connected.
l The types of the MSP groups at the two ends are different.
l The cross-connect unit is faulty.
Procedure
Step 1 Check whether the optical fibers are correctly connected.
If... Then...
The optical fibers are incorrectly connected Reconnect the optical fibers correctly. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The optical fibers are correctly connected Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 385
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Check whether the types of the MSP groups at the two ends are the same (both are 1+1 or 1:N
MSP groups).
If... Then...
The types of the MSP groups at the two Ensure that the types of the MSP groups at
ends are not the same the two ends are the same, and restart the
MSP protocols at the two ends. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The types of the MSP groups at the two Go to the next step.
ends are the same
Step 3 Replace the faulty system control, cross-connect, and timing board.
----End
Related Information
None.
4.2.185 K2_M
Description
The K2_M alarm indicates that inconsistency between the received K2 byte and the
transmitted K2 byte of a linear multiplex section protection (MSP) group.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Impact on the System
The automatic MSP switching may fail, and the protected services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The types of the MSP groups at the two ends are different.
l The cross-connect unit is faulty.
Procedure
Step 1 Check whether the types of the MSP groups at the two ends are the same (both are 1+1 or 1:N
MSP groups).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 386
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The types of the MSP groups at the two Ensure that the types of the MSP groups at
ends are not the same the two ends are the same, and restart the
MSP protocols at the two ends. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The types of the MSP groups at the two Go to the next step.
ends are the same
Step 2 Replace the faulty board.
----End
Related Information
None.
4.2.186 KMC_KEY_SYNC_FAIL
Description
The KMC_KEY_SYNC_FAIL alarm indicates a KMC key synchronization failure. (KMC is
short for key management center.)
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Impact on the System
The database cannot be backed up, KMC cannot be enabled or disabled, and KMC keys
cannot be configured.
Possible Causes
l Cause 1: The database on the alarmed NE is abnormal.
l Cause 2: The database backup fails on the alarmed NE.
Procedure
Step 1 Restore NE data from the latest backup database.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 387
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 If NE data restoration fails, contact Huawei engineers to handle the alarm.
----End
Related Information
None
4.2.187 LAG_DOWN
Description
The LAG_DOWN alarm indicates that the number of activated members in the link
aggregation group (LAG) is 0.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
Services are interrupted.
Possible Causes
Possible causes of the LAG_DOWN alarm are as the same as those of 4.2.188
LAG_MEMBER_DOWN.
Procedure
Step 1 Determine the port that reports the alarm based on alarm parameters.
Step 2 Rectify the fault at each member port according to the description in 4.2.188
LAG_MEMBER_DOWN.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 388
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.188 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN alarm indicates that a member port of a link aggregation group
(LAG) cannot be activated and cannot work as a backup port.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Parameter 2 Indicates the sub-board ID.
Parameter 3, Parameter 4 Indicates the port ID.
Parameter 5 Indicates the cause that makes the port unavailable.
l 0x01: The port is disabled or in link-down state.
l 0x02: The port receives no LACP packets.
l 0x03: The port works in half-duplex mode.
l 0x04: The port is looped back.
Impact on the System
The impact on the system varies depending on the load sharing mode.
l In load-sharing mode, packet loss may occur and persist due to bandwidth insufficiency.
l In non-load-sharing mode, link switching is triggered and packet loss occurs temporarily.
Possible Causes
Possible causes of the ETH_LINK_DOWN alarm are as follows:
l The port is unavailable.
l The port receives no LACP packets.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 389
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The port works in half-duplex mode.
l The port is looped back.
Procedure
Step 1 On the U2000, query Parameter 5 of the reported alarm.
l If the value of Parameter 5 is 0x01, go to Step 2.
l If the value of Parameter 5 is 0x02, go to Step 3.
l If the value of Parameter 5 is 0x04, go to Step 5.
Step 2 On the U2000, check whether the ETH_LOS alarm is reported on the port that reports the
LAG_MEMBER_DOWN alarm. If yes, clear the ETH_LOS alarm.
Step 3 On the U2000, check whether the ETH_LOS or FLOW_OVER alarm is reported on the port
that reports the LAG_MEMBER_DOWN alarm. If yes, clear the ETH_LOS or
FLOW_OVER alarm.
Step 4 On the U2000, check whether the port works in half-duplex mode. If yes, change the working
mode of the port into full-duplex.
Step 5 Check whether the port at the local end reports the LOOP_ALM alarm. If yes, delete the
loopback setting.
----End
Related Information
None.
4.2.189 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
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 390
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the IP port number.
Parameter 2, Parameter 3 The value is always 0x01.
Parameter 4 Indicates the cause of the protection failure.
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.
Parameter 5 The value is always 0xff, and this parameter is meaningless.
Impact on the System
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.
l The link of the port is faulty.
l The port is in half-duplex mode.
l The port fails to receive the LCAP packets.
l A self-loop is detected at the port.
l 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 391
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 If the value of Parameter 4 is 0x03, the port fails to receive the LACP packets.
1. On the U2000, check whether the LAG is configured at the opposite end, and check
whether the port connected to the faulty port is added to the LAG at the opposite end.
Make sure that the LAG is correctly configured, and then check whether the alarm is
cleared.
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.
4.2.190 LAN_LOC
Description
The LAN_LOC alarm indicates that the Ethernet communication fails.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
When the network port is faulty or there is a cut in the network cable, the communication at
this network port fails. In this case, the communication between the NE and the NMS stops.
Possible Causes
l The network port is required and is enabled on the NMS. However, the network cable is
not connected to the network port or is inappropriately connected.
l The network port is not required but is enabled on the NMS.
l The network cable is faulty.
l The board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 392
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Query the alarm information on the NMS. Check whether the corresponding network port is
required according to the alarm parameters.
If... Then...
The corresponding network port is not Disable the port on the U2000.
required
The corresponding network port is Verify that the network cable is properly
required connected to the network port.
Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable
and re-connect it.
Step 3 If the alarm persists, the auxiliary interface board may be faulty. In this case, replace the
faulty board.
----End
Related Information
None
4.2.191 LASER_CHECK_ERR
Description
The LASER_CHECK_ERR alarm indicates that an optical module reading/writing error
occurs.
Attribute
Alarm Severity Alarm Type
Minor Equipment
Parameters
None
Impact on the System
The optical module rate, alarms, performance, and manufacturing information cannot be
reported to the SCC board. Services are not affected.
Possible Causes
Possible causes of this alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 393
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 1: The optical module is faulty.
l Cause 2: The optical module connector is faulty.
Procedure
Step 1 Cause 1: The optical module is faulty.
1. Replace the alarmed optical module.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The optical module connector is faulty.
1. Replace the alarmed board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.192 LASER_CLOSED
Description
The LASER_CLOSED alarm indicates that the laser on the line board is shut down.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Impact on the System
The line board cannot transmit and receive services.
Possible Causes
The possible cause of this alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 394
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l A user shuts down the laser by using the U2000 or Navigator.
Procedure
Step 1 Start the laser by using the U2000 or Navigator, or wait for a period of time (5 minutes by
default) until the laser automatically starts.
----End
Related Information
None.
4.2.193 LASER_MOD_ERR
Description
The LASER_MOD_ERR alarm indicates inconsistency of optical module types. This alarm is
generated when the type of the optical module installed is not consistent with the type
supported by the board.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
The optical port performance deteriorates, services may be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The rate of the optical module installed is not consistent with the rate of the optical port
on the board.
l The type of the optical module installed is not consistent with the type supported by the
port on the board.
l The optical module is faulty.
l The board is faulty.
Procedure
Step 1 View the LASER_MOD_ERR alarm on the U2000 to determine the board that reports the
LASER_MOD_ERR alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 395
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Replace the optical module.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 3 Replace the faulty board.
----End
Related Information
None
4.2.194 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR_EX alarm indicates that the hot swapping optical module on the
line board does not match the optical port on the line board.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The line board cannot transmit and receive services correctly.
Possible Causes
Possible causes of this alarm are as follows:
l The type of the optical module installed is incorrect.
l The optical module or line board is faulty.
Procedure
Step 1 Check whether the optical module installed matches the optical port on the line board. If they
do not match, replace the optical module with one of the correct type.
Step 2 Check on the U2000 whether the LASER_MOD_ERR_EX alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 396
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 3 If the alarm persists, the optical module or line board is faulty. Replace the optical module. If
the alarm still persists, replace the line board.
The pluggable optical module on the line board supports hot swap.
----End
Related Information
None.
4.2.195 LASER_MODULE_MISMATCH
Description
This alarm indicates a mismatch of the optical module type and the fiber type. This alarm is
generated when the type of the optical module mismatches the type of the board.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
Services cannot be normally received or transmitted. It can even cause service interruption.
Fault Symptom
None
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 397
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of the LASER_MODULE_MISMATCH alarm is as follows:
l Cause 1: The optical port type supported by the physical board does not match the type
of the optical module inserted into the optical port.
Procedure
l Cause 1: The optical port type supported by the physical board does not match the type
of the optical module inserted into the optical port.
a. Check whether the optical module inserted into the optical port matches the type of
the optical port.
b. If not, replace the optical module with another one of the right type.
c. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.2.196 LASER_SHUT
Description
The LASER_SHUT alarm indicates that a laser on a board is shut down.
Attribute
Alarm Severity Alarm Type
Major Processing failure alarm
Parameters
None.
Impact on the System
Services are interrupted.
Possible Causes
The possible cause of the LASER_SHUT alarm is as follows:
The user uses the U2000 or Navigator to shut down the laser.
Procedure
Step 1 Delete the setting of laser shutdown.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 398
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
The LASER_SHUT alarm is automatically cleared.
----End
Related Information
None.
4.2.197 LASER_TYPE_MISMATCH
Description
The LASER_TYPE_MISMATCH alarm indicates an optical module mismatch. This alarm is
reported when a port enabled with Single-Fiber Two-Way Dispersion Compensation houses
a two-fiber bidirectional optical module.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
Services may be unavailable, or the laser of the optical module may be disabled.
Possible Causes
The possible cause of the LASER_TYPE_MISMATCH alarm is as follows:
A mismatched optical module is housed.
Procedure
Step 1 Check whether the alarmed port is enabled with Single-Fiber Two-Way Dispersion
Compensation.
If... Then...
Yes Go to Step 2.
No Go to Step 3.
Step 2 Check whether Single-Fiber Two-Way Dispersion Compensation is required according to
the live network condition.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 399
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
Yes Replace the optical module with a single-fiber bidirectional optical module. For
details, see Replacing a Pluggable Optical/Electrical Module in Maintenance Guide.
No Disable Single-Fiber Two-Way Dispersion Compensation.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.198 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.
Impact on the System
The LCAS protection does not work.
Possible Causes
The possible causes of the LCAS_FOPR alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 400
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The downlink VCG receives SQ repeatedly due to incorrect configuration or link bit
errors.
l The LCAS function of the opposite VCG is disabled.
l The downlink VCG simultaneously receives the FIXED and other LCAS control bytes
due to incorrect configuration or bit errors in the link.
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
4.2.199 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.
Impact on the System
The LCAS protection does not work.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 401
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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
Step 1 Check the service configurations of the local and opposite station. Check whether the bound
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
4.2.200 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 Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.
Impact on the System
Partial configured paths are used in the receiving direction, as a result, the available
bandwidth decreases.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 402
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 1 Check the service configurations of the local and opposite station. Check whether the bound
paths of the VCTRUNK are consistent. If any error exists, reconfigure the values.
Step 2 Check whether the unequipped path reports SDH alarms. If yes, see the handling procedure of
the corresponding alarm.
----End
Related Information
None
4.2.201 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating the loss of partial bandwidth in the LCAS transmit
direction.
Attribute
Alarm Severity Alarm Type
Minor Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.
Impact on the System
Partial paths are used in the transmit direction, as a result, the available bandwidth decreases.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 403
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 1 Check the service configurations of the local and opposite station. Check whether the bound
paths of the VCTRUNK are consistent. If any error exists, reconfigure the values.
Step 2 Check whether the unequipped path reports SDH alarms. If yes, see the handling procedure of
the corresponding alarm.
----End
Related Information
None
4.2.202 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 Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.
Impact on the System
The paths configured in the receive direction are not used, so the available bandwidth is zero.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 404
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 1 Check the service configurations of the local and opposite station. Check whether the bound
paths of the VCTRUNK are consistent. If any error exists, reconfigure the values.
Step 2 Check whether the configured path reports SDH alarms. If yes, see the handling procedure of
the corresponding alarm.
----End
Related Information
None
4.2.203 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating the loss of all bandwidth in the LCAS transmit
direction.
Attribute
Alarm Severity Alarm Type
Major Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK port number.
Impact on the System
The paths configured in the transmit direction are not used, so the available bandwidth is zero.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 405
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 1 Check the service configurations of the local and opposite station. Check whether the bound
paths of the VCTRUNK are consistent. If any error exists, reconfigure the values.
Step 2 Check whether the configured path reports SDH alarms. If yes, see the handling procedure of
the corresponding alarm.
----End
Related Information
None
4.2.204 LCD
Description
The LCD alarm indicates that the OCD alarm is reported and persists within the transmission
period of N cells. N indicates the LCD alarm threshold value, and it varies with the port type.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
l All the services in the receive direction of the port are interrupted.
l All the connections at the port insert the AIS cells in the segment or end point at the
downstream station.
Possible Causes
Possible causes of the LCD alarm are as follows:
l The SDH path connected to the alarmed ATM port fails to receive signals. For example,
an SDH alarm, such as R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP, TU_AIS, or
TU_LOP, is reported in the SDH path.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 406
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l A great number of bit errors occur in the SDH receive path connected to the alarmed
ATM port. That is, some bit error alarms, such as the B1_SD, B2_SD, or B3_SD, are
reported in the SDH path.
l The ATM processing chip on the alarmed board is faulty.
Procedure
Step 1 On the U2000, check whether any alarm, such as R_LOS, R_LOF, MS_AIS, AU_AIS,
AU_LOP, TU_AIS, or TU_LOP, is reported in the SDH path connected to the alarmed ATM
port.
If... Then...
The R_LOS, R_LOF, MS_AIS, Handle the R_LOS, R_LOF, MS_AIS, AU_AIS,
AU_AIS, AU_LOP, TU_AIS, or AU_LOP, TU_AIS, or TU_LOP alarm, and then
TU_LOP alarm is reported check whether the LCD alarm is cleared. If the
LCD alarm persists, go to the next step.
The R_LOS, R_LOF, MS_AIS, Go to the next step.
AU_AIS, AU_LOP, TU_AIS, or
TU_LOP alarm is not reported
Step 2 On the U2000, check whether the B1_EXC, B2_EXC, or B3_EXC alarm which indicates bit
errors on the tributary board exceeds the threshold is reported on the receive path.
If... Then...
The B1_EXC, B2_EXC, or B3_EXC Handle the alarms, and then check whether the
alarm is reported LCD alarm is cleared. If the alarm persists, go to
the next step.
The B1_EXC, B2_EXC, or B3_EXC Go to the next step.
alarm is not reported
Step 3 Reset (cold) the board that reports the LCD alarm. Then, check whether the alarm is cleared.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 4 Replace the board that reports the LCD alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 407
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
End and segment
An end point refers to a termination point in a chain network, and it is used to monitor the
whole virtual connection. A segment point is a dividing point on an ATM link. An ATM link
can comprise of many segments. A segment point is used to monitor an ATM link segment
and perform link continuity checks.
LCD alarm threshold values at different ports
For an external ATM port, the LCD alarm threshold is seven cells.
4.2.205 LCS_DAYS_OF_GRACE
Description
The LCS_DAYS_OF_GRACE alarm indicates that the license remains in the keepalive
period. This alarm is generated when the system detects that the license file is ineffective, the
license file version is incorrect, or a license control item expires but is still in the keepalive
period of the license.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the ID of the license control item.
Parameter 2
Parameter 3, Indicates the number of remaining days in the keepalive period of the
Parameter 4 license.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 408
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
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
is not the same as the ESN of the equipment.
l 0x03: The license file version does not match the software version of
the equipment.
l 0x04: The ESN specified in the license file is not the same as the ESN
of the equipment, and the license file version does not match the
software version of the equipment.
NOTE
l If the values of Parameter 1 and Parameter 2 are not 0, Parameter 5 has a fixed
value of 0.
l If the value of Parameter 5 is not 0, Parameter 1 and Parameter 2 have fixed
values of 0.
Impact on the System
If a license file is not replaced in the keepalive period, the system or license control items
enter the default state when the keepalive period ends.
Possible Causes
Possible causes of this alarm are as follows:
l The license file is ineffective, and the NE is in the keepalive period of 60 days.
l The ESN specified in the license file is not the same as the ESN of the equipment, or the
license file version does not match the software version of the equipment. In addition,
the NE is in the keepalive period of 60 days.
l A license control item expires but remains in the keepalive period of 60 days.
Procedure
Step 1 Contact Huawei technical support engineers to install a correct license file on the NE.
----End
Related Information
Definitions of States
Normal state
In the normal state, all the check items of the license file pass the check, and the equipment
can properly implement all the functions specified in the license file.
Trial state
In the trial state, the license file fails to be checked for correctness. During the grace period,
the equipment can still implement all the functions specified in the license file.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 409
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
License grace period
The license grace period is the amount of time the features specified in a license file can
continue functioning after the license file expires. By default, the license grace period lasts for
60 days.
Default state
In the default state, the integrity check for the license file fails. Ongoing services that use the
licensed features are available, but cannot be configured any more. For example, a service that
needs to use the licensed features cannot be added or modified.
State Transition
The following figure shows the basic state transition of a license file on an NE.
Table 4-2 provides the major conditions that trigger state transition of a license file.
Table 4-2 State transition of a license file
Original State Final State Trigger Condition
Normal state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Default state The installed license file expires and its grace
period also expires.
Trial state Normal state The correct license file is installed.
Default state The installed license file expires and its grace
period also expires.
Default state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Normal state The correct license file is installed.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 410
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.206 LCS_EXPIRED
Description
The LCS_EXPIRED alarm indicates that the license file has expired. This alarm is generated
when the license file is beyond its keepalive period.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the number of days after the license file expires.
Parameter 2
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
is not the same as the ESN of the equipment.
l 0x03: The license file version does not match the software version of
the equipment.
l 0x04: The ESN specified in the license file is not the same as the ESN
of the equipment, and the license file version does not match the
software version of the equipment.
Impact on the System
The equipment enters the default state in which minimum functions are available.
Possible Causes
Possible causes of this alarm are as follows:
l The license file is ineffective, but the NE still operates.
l The ESN specified in the license file is not the same as the ESN of the equipment, or the
license file version does not match the software version of the equipment. In addition,
the license file is ineffective, but the NE still operates.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 411
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Contact Huawei technical support engineers to install a correct license file on the NE.
----End
Related Information
Definitions of States
Normal state
In the normal state, all the check items of the license file pass the check, and the equipment
can properly implement all the functions specified in the license file.
Trial state
In the trial state, the license file fails to be checked for correctness. During the grace period,
the equipment can still implement all the functions specified in the license file.
License grace period
The license grace period is the amount of time the features specified in a license file can
continue functioning after the license file expires. By default, the license grace period lasts for
60 days.
Default state
In the default state, the integrity check for the license file fails. Ongoing services that use the
licensed features are available, but cannot be configured any more. For example, a service that
needs to use the licensed features cannot be added or modified.
State Transition
The following figure shows the basic state transition of a license file on an NE.
Table 4-3 provides the major conditions that trigger state transition of a license file.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 412
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Table 4-3 State transition of a license file
Original State Final State Trigger Condition
Normal state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Default state The installed license file expires and its grace
period also expires.
Trial state Normal state The correct license file is installed.
Default state The installed license file expires and its grace
period also expires.
Default state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Normal state The correct license file is installed.
4.2.207 LCS_FILE_NOT_EXIST
Description
The LCS_FILE_NOT_EXIST alarm indicates that no license file is installed on the NE.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None.
Impact on the System
The equipment enters the default state.
Possible Causes
The possible cause of this alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 413
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The equipment starts, but no license file is available.
Procedure
Step 1 Contact Huawei technical support engineers to install a correct license file on the NE.
----End
Related Information
Definitions of States
Normal state
In the normal state, all the check items of the license file pass the check, and the equipment
can properly implement all the functions specified in the license file.
Trial state
In the trial state, the license file fails to be checked for correctness. During the grace period,
the equipment can still implement all the functions specified in the license file.
License grace period
The license grace period is the amount of time the features specified in a license file can
continue functioning after the license file expires. By default, the license grace period lasts for
60 days.
Default state
In the default state, the integrity check for the license file fails. Ongoing services that use the
licensed features are available, but cannot be configured any more. For example, a service that
needs to use the licensed features cannot be added or modified.
State Transition
The following figure shows the basic state transition of a license file on an NE.
Table 4-4 provides the major conditions that trigger state transition of a license file.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 414
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Table 4-4 State transition of a license file
Original State Final State Trigger Condition
Normal state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Default state The installed license file expires and its grace
period also expires.
Trial state Normal state The correct license file is installed.
Default state The installed license file expires and its grace
period also expires.
Default state Trial state l The ESN or V/R version number specified in
the license file does not match the ESN or V/R
version of the NE, but the license file remains
in the grace period.
l The installed license file expires but remains
in the grace period.
Normal state The correct license file is installed.
4.2.208 LFA
Description
The LFA alarm indicates that basic frames fail to be delimited in the local IMA link.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
l The E1 link that reports the alarm is unavailable and fewer links in the IMA group are
available. If the service bandwidth configured for the IMA group is higher than that
provided by the available E1 links in the IMA group, a congestion event occurs at the
IMA port. Consequently, user cells are lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 415
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Services are interrupted if the VCTRUNK link binds only one member.
Possible Causes
Possible causes of the LFA alarm are as follows:
l Abnormal service traffic from the cross-connection side makes the E1 deframing module
on the IMA board fail to delimit the frames. Consequently, an alarm indicating loss of
cell delimitation is reported. For example, the cross-connections are not configured, or
some alarms, such as the TU_LOP or TU_AIS, occur.
l VC-12 cross-connection configurations are incorrect.
l The E1 mapping chip on an ATM board is faulty.
l A board is faulty.
Procedure
Step 1 On the U2000, check whether an alarm indicating no cross-connections, TU_LOP, or TU_AIS
alarm is reported. If yes, clear the alarm. Check whether the LFA alarm is cleared.
Step 2 If the LFA alarm persists, check whether VC-12 cross-connections are correctly configured on
the U2000. If not, rectify the VC-12 cross-connections and check whether the LFA alarm is
cleared.
Step 3 If the LFA alarm persists, the E1 mapping chip on the alarmed board may be faulty. Reset
(cold) the board and check whether the LFA alarm is cleared.
If the services on the alarmed board are not configured with protection, the services are
interrupted after the board cold reset.
Step 4 If the LFA alarm persists, replace the board that generates the LFA alarm.
----End
Related Information
None.
4.2.209 LINK_ERR
Description
The LINK_ERR alarm indicates that the data link is incorrect. This alarm is reported when
the Ethernet connection is incorrect and negotiation between ports fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 416
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port ID.
Parameter 2, Parameter 3 Indicates the port ID.
Impact on the System
When the LINK_ERR alarm is reported during the data transmission, negotiation between
network ports fails. As a result, the data cannot be received and services are interrupted.
Possible Causes
Possible causes of the LINK_ERR alarm are as follows:
l Ports at the local end and opposite end work in inconsistent modes. As a result,
negotiation between the ports fails.
l The cable or fiber is incorrectly connected.
l The link is faulty.
l The board at the opposite end is faulty.
Procedure
Step 1 Determine the alarmed board and alarmed port according to the alarm information on the
U2000.
Step 2 Check whether ports at the local end and opposite end work in consistent modes.
If... Then...
They work in inconsistent modes Change them to the same. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
They work in consistent modes Go to the next step.
Step 3 Check whether the cable or fiber is correctly connected and functional.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 417
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The cable or fiber is incorrectly connected Rectify the fiber or cable connection or
or is faulty replace the faulty fiber or cable. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The cable or fiber is correctly connected and Go to the next step.
is functional
Step 4 Check whether the board at the opposite end works properly.
If... Then...
The board at the opposite end is faulty Replace the faulty board. Check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The board at the opposite end works Go to the next step.
properly
Step 5 Replace the alarmed board. Make sure the ports at the local end opposite end work in
consistent modes. After the replacement, the alarm is cleared automatically.
----End
Related Information
None.
4.2.210 LMFA
Description
The LMFA alarm indicates that the local end expects to receive CRC-4 multiframes but
receives only basic frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The alarmed E1 links become unavailable. As a result, fewer links of the IMA group are
available. If the IMA group is comprised of only one link, services are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 418
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the LMFA alarm are as follows:
l The E1 frame format used by the PQ1 board is the basic frame whereas the E1 frame
format used by the IMA board connected to the PQ1 board is the multiframe format.
l The E1 mapping chip on an ATM board is faulty.
l A board is faulty.
Procedure
Step 1 On the U2000, check whether the E1 frame format used by the PQ1 board is the basic frame
whereas the E1 frame format used by the IMA board connected to the PQ1 board is the
multiframe format. If yes, modify the E1 frame formats as required to be the same. Then
check whether the LMFA alarm is cleared.
Step 2 If the alarm persists, the E1 mapping chip on the alarmed board may be faulty. Reset (cold)
the board and check whether the LFA alarm is cleared.
If the services on the alarmed board are not configured with protection, the services are
interrupted after the board cold reset.
Step 3 If the alarm persists, replace the board that generates the LMFA alarm.
----End
Related Information
Basic Frame
As defined in ITU-T G.704 Recommendation, even basic frames carry FAS information
whereas odd basic frames do not carry FAS information.
Multiframe
A multiframe contains 16 basic frames and can be checked in the cyclic redundancy check
(CRC) mode.
4.2.211 LOF_64K
Description
The LOF_64K alarm indicates that the local end carrying 64 kbit/s services does not receive
any frames from the remote end or overhead frames are lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 419
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of a hitless protection group.
Parameter 2 Indicates overhead timeslot 27.
Parameter 3 Indicates overhead timeslot 28.
NOTE
The preceding parameter description applies only to PF4E8 boards. Other boards do not involve any
parameters.
Impact on the System
When this alarm occurs, the 64 kbit/s services on the board are unavailable or the E1 hitless
protection group is unavailable.
Possible Causes
If there are alarm parameter 1/2/3, it means that the overhead frames are lost, the overhead
cross-connection is not set up or the link of the hitless protection group is faulty. Otherwise,
the receiving frame of the local end carrying 64K services does not receive any frames from
the remote end.
If overhead frames are lost, the following lists the possible causes of the LOF_64K alarm.
You must consider cause 1 first.
l Cause 1: The overhead cross-connection is not set up.
l Cause 2: The link of the hitless protection group is faulty.
If the local end carrying 64 kbit/s services does not receive any frames from the remote end,
LOF_64K is possibly caused by the following:
l Cause 1: The service frame format is incorrect.
l Cause 2: The transmit board (including the cross-connect and timing board) at the
remote end is faulty, and the frame structure is lost.
l Cause 3: The receive board at the local end is faulty, and the frame structure is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 420
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 If overhead frames are lost, LOF_64K can be handled as follows:
1. Cause 1: The overhead cross-connection is not set up.
a. According to parameter 2, 3, identify the timeslot for which the overhead cross-
connection is not set up. On the NMS, use the faulty channel as the source to set up
the overhead cross-connection. For details the configuration procedure, see
Configuring 64 kit/s Services.
b. Check whether the LOF_64K alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
2. Cause 2: The link of the hitless protection group is faulty.
a. Check the entire link of the hitless protection group. Replace the optical fiber or
optical module connected to the port with an intact optical fiber or optical module,
and then check whether the alarm is cleared.
b. If the alarm is cleared, the original optical fiber or optical module is faulty. Replace
the optical fiber or optical module. If the alarm persists, go to the next step.
Step 2 If the local end carrying 64 kbit/s services does not receive any frames from the remote end,
LOF_64K can be handled as follows:
1. Cause 1: The service frame format is incorrect.
a. Check whether the frame format is consistently configured for the local and remote
ends by checking Serial Port Rate (bps) of the receive and transmit boards. For
details, see Configuring a PCM Port in the Configuration Guide (SDH Transport
Domain).
b. Check whether the LOF_64K alarm is cleared. If the alarm persists, go to the next
step.
2. Cause 2: The transmit board (including the cross-connect and timing board) at the
remote end is faulty, and the frame structure is lost.
a. Replace the remote board connected to the alarmed board and check whether the
LOF_64K alarm is cleared. If the alarm persists, replace the remote cross-connect
and timing board.
b. Check whether the LOF_64K alarm is cleared. If the alarm persists, go to the next
step.
3. Cause 3: The receive board at the local end is faulty, and the frame structure is lost.
a. Replace the alarmed board.
b. Check whether the LOF_64K alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 421
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.212 LOOP_ALM
Description
The LOOP_ALM is a loopback alarm. This alarm occurs when service loopback is set.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 422
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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.
l 0x04: Loopback on the user side.
l 0x05: Loopback on the combination wave side.
l 0x06: SPI inloop.
l 0x07: SPI outloop.
l 0x08: ATM layer inloop.
l 0x09: ATM layer outloop.
l 0x0A: PHY layer inloop.
l 0x0B: PHY layer outloop.
l 0x0C: MAC layer inloop.
l 0x0D: MAC layer outloop.
l 0x0E: VC-4 timeslot inloop.
l 0x0F: VC-4 timeslot outloop.
l 0x10: VC-3 timeslot inloop.
l 0x11: VC-3 timeslot outloop.
l 0x12: VC-12 timeslot inloop.
l 0x13: VC-12 timeslot outloop.
l 0x14: IF outloop.
l 0x15: IF inloop.
l 0x16: RF inloop.
l 0xff: Any of the preceding loopback modes.
Impact on the System
The alarm indicates that an optical port loopback or path loopback is configured on a line
board or a tributary board. If the setting is not canceled, services may be interrupted.
Possible Causes
Possible causes of the LOOP_ALM alarm are as follows:
l Inloops or outloops are configured on a board.
l A board is faulty.
Procedure
Step 1 Set the loopback status of the alarmed port to no loop. Check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 423
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 2 Replace the alarmed board.
----End
Related Information
None.
4.2.213 LP_CROSSTR
Description
The LP_CROSSTR alarm indicates that the number of lower order path bit errors crosses the
threshold.
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the performance monitoring period.
l 0x01: The monitoring period is 15 minutes.
l 0x02: The monitoring period is 24 hours.
Parameter 2, Parameter 3 Indicate the ID of the threshold-crossing performance item.
Impact on the System
The quality of services on the board that reports the LP_CROSSTR alarm deteriorates, or the
services may be interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 424
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The performance of the laser on the line board at the opposite end deteriorates.
l The clock performance at the local or opposite end deteriorates.
l The receive optical power of the line board at the local end is out of range.
l The optical fiber performance deteriorates.
Procedure
Step 1 Check whether the performance of the laser on the line board at the opposite end deteriorates.
If... Then...
The laser performance deteriorates Replace the laser. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The laser performance does not deteriorate Go to the next step.
Step 2 Check whether the clock performance at the local or opposite end deteriorates.
If... Then...
The clock performance deteriorates Re-configure clock tracing. After the
configured performance monitoring period
ends, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The clock performance does not deteriorate Go to the next step.
Step 3 Check whether the receive optical power of the line board at the local end is out of range.
If... Then...
The receive optical power is higher than the Use an optical power attenuator to decrease
upper threshold the value of the receive optical power. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The receive optical power is lower than the Increase the value of the input optical
lower threshold power. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The receive optical power is within the Go to the next step.
specified range
Step 4 Perform loopbacks at the local end and the opposite end to locate the faulty board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 425
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The timing unit at the opposite end reports a The timing unit at the opposite end is faulty.
higher order adaptation performance event Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The timing unit at the local end reports a The timing unit at the local end is faulty.
higher order adaptation performance event Replace the system control, cross-connect,
and timing board. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
Step 5 Check whether the optical fiber performance deteriorates.
If... Then...
The optical fiber performance deteriorates Replace the optical fiber.
The optical fiber performance does not Contact Huawei technical support engineers
deteriorate to handle the alarm.
----End
Related Information
None.
4.2.214 LP_R_FIFO
Description
The LP_R_FIFO alarm indicates FIFO overflow on the receive side of the lower order path.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Impact on the System
Bit errors occur in lower order services of the board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 426
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The service cross-connections are incorrectly configured.
l The service type is incorrectly configured.
Procedure
Step 1 View the LP_R_FIFO alarm on the U2000 to determine the path ID of the board that reports
the LP_R_FIFO alarm.
Step 2 Check whether the configurations of services in the path are correct. Ensure that the service
type at the local end is the same as that at the opposite end, and the service cross-connections
are correctly configured. Then, the LP_R_FIFO alarm is automatically cleared.
----End
Related Information
None.
4.2.215 LP_RDI
Description
The LP_RDI alarm indicates a remote receive failure in the lower order path of the tributary
board. After receiving the TU_AIS or TU_LOP alarm, the opposite end sends the LP_RDI
alarm to the local end.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
None.
Possible Causes
Possible causes of this alarm are as follows:
l The opposite end receives the TU_AIS or TU_LOP alarm.
l The receive unit at the opposite end is faulty.
l The transmit unit at the local end is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 427
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the TU_AIS or TU_LOP alarm is reported in the corresponding path of the
tributary board at the opposite end.
If... Then...
The TU_AIS or TU_LOP alarm is reported Clear the 4.2.489 TU_AIS or 4.2.492
TU_LOP alarm. Then, check whether the
LP_RDI alarm is cleared. If the LP_RDI
alarm persists, go to the next step.
The TU_AIS or TU_LOP alarm is not Go to the next step.
reported
Step 2 Replace the faulty board.
----End
Related Information
None.
4.2.216 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 428
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
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.
l The receive part at the opposite station is faulty.
l The transmit part at the local station is faulty.
Procedure
Step 1 View alarms of the NE, and check whether there is the TU_AIS or TU_LOP alarm in the
corresponding path of the tributary board at the opposite station.
If... Then...
There is the TU_AIS, TU_LOP, LP_TIM, or Refer to the corresponding section in this
LP_UNEQ alarm document to clear the 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.
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
TU_AIS, TU_LOP, LP_TIM, and LP_UNEQ
4.2.217 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating a remote defect in the lower order path of the
tributary board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 429
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
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.
l The receive part at the opposite station is faulty.
l The transmit part at the local station is faulty.
Procedure
Step 1 View alarms of the NE, and check whether there is the TU_AIS, 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 Refer to the corresponding section in this
LP_UNEQ alarm document to clear the alarm.
There are no such alarms as the TU_AIS, Proceed to the next step.
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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 430
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
TU_AIS, TU_LOP, LP_TIM, and LP_UNEQ
4.2.218 LP_REI
Description
The LP_REI alarm indicates remote bit errors in the lower order path. This alarm is generated
when a board detects that bit 3 of the V5 byte is 1 or any of bits 1-4 of the G1 byte is 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
This alarm does not have any impact on the local end.
Possible Causes
The possible cause of this alarm is as follows:
l The LP_REI alarm is a correlated alarm. When the tributary board at the opposite end
detects a bit error alarm, such as BIP_SD, BIP_EXC, B3_SD, or B3_EXC, the tributary
board sends the LP_REI alarm to the local end.
Procedure
Step 1 Clear the 4.2.43 BIP_SD, 4.2.42 BIP_EXC, 4.2.29 B3_SD, or 4.2.26 B3_EXC alarm. Then,
the LP_REI alarm is automatically cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 431
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.219 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.
Attribute
Alarm Severity Alarm Type
Minor Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
When the LP_REI_VC12 alarm occurs, the lower order background block error (BBE) occurs
in the received services at the opposite end and the LP_REI alarm (VC12: V5[b3], VC3:
G1[b1-b4]) is returned to the local end.
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 end.
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 Refer to the corresponding section in this document
alarm to clear the B3_EXC, B3_SD, BIP_EXC, or
BIP_SD alarm.
There is no B3 or BIP bit error Proceed to the next step.
alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 432
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If few B3 or BIP bit errors occur in the remote, the fault usually
lies in the equipment instead of the optical path. If any interference source exists near the
equipment, change the location.
Step 3 Perform the loopback at two ends of the line. Check whether the cross-connect and timing
unit and the tributary board on both the opposite equipment and local equipment operate
normally. Following the service direction, check upstream stations one by one. Locate the
faulty board.
If... Then...
There is the B3 or BIP bit error The receive end at the opposite end is faulty.
reported on the opposite board Replace the boards in an order of tributary board,
line board, and SCC board.
There is the B3 or BIP bit error The transmit end of the board at the local end is
reported on the local board faulty. Replace the faulty board.
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B3_EXC, B3_SD, BIP_EXC, and BIP_SD
4.2.220 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 Service quality 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 433
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
When the LP_REI_VC3 alarm occurs, the lower order background block error (BBE) occurs
in the received services at the opposite end and the LP_REI alarm (VC-12: V5[b3], VC3:
G1[b1-b4]) is returned to the local end.
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 end.
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.
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If few B3 or BIP bit errors occur in the remote, the fault usually
lies in the equipment instead of the optical path. If any interference source exists near the
equipment, change the location.
Step 3 Perform the loopback at two ends of the line. Check whether the cross-connect and timing
unit and the tributary board on both the opposite equipment and local equipment operate
normally. Following the service direction, check upstream stations one by one. Locate the
faulty board.
If... Then...
There is the B3 or BIP bit error reported on The receive end at the opposite end is faulty.
the opposite board 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 end is faulty. Replace the faulty board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 434
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B3_EXC, B3_SD, BIP_EXC, and BIP_SD
4.2.221 LP_RFI
Description
The LP_RFI alarm indicates a remote receive failure in the lower order path. This alarm is
generated when a board detects that bit 4 of the V5 byte is 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
This alarm does not have any impact on the local end.
Possible Causes
The possible cause of the LP_RFI alarm is as follows:
The LP_RFI alarm is a correlated alarm. When the tributary board at the opposite end detects
the BIP_EXC alarm, the tributary board sends the LP_RFI alarm to the local end.
Procedure
Step 1 Clear the 4.2.42 BIP_EXC alarm. Then, the LP_RFI alarm is automatically cleared.
----End
Related Information
4.2.42 BIP_EXC
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 435
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.222 LP_SIZE_ERR
Description
The LP_SIZE_ERR alarm indicates incorrect TU specifications. This alarm is generated when
the mapping structure of the TU services (lower order services) received by a board is
inconsistent with that specified for the board.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
The lower order services are interrupted.
Possible Causes
The possible cause of this alarm is as follows:
l The mapping structure of the lower order services is incorrectly configured.
Procedure
Step 1 View the LP_SIZE_ERR alarm on the U2000 to determine the ID of the path where the
LP_SIZE_ERR alarm is generated.
Step 2 Re-configure the mapping structure of the lower order services transmitted over the path.
Then, the LP_SIZE_ERR alarm is automatically cleared.
----End
Related Information
None.
4.2.223 LP_SLM
Description
The LP_SLM alarm indicates inconsistent labels of signals in the lower order path. This alarm
is generated when a board detects inconsistent V5 or C2 bytes.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 436
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When the LP_SLM occurs, the mapping structure of the lower order services received on the
tributary board is incorrect. As a result, the services are abnormal (VC-12: V5[b5-b7], VC3:
C2).
Impact on the System
This alarm does not have any impact on the system.
Possible Causes
Possible causes of this alarm are as follows:
l The label of signals in the lower order path at the local end is not consistent with that at
the opposite end.
l The service type is incorrectly configured.
Procedure
Step 1 View the LP_SLM alarm on the U2000 to determine the board and path where the LP_SLM
alarm is generated.
Step 2 Ensure that the label of signals in the lower order path at the local end is consistent with that
at the opposite end. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the service configuration on the board that reports the
alarm is correct. After modifying the incorrect configuration, check whether the alarm is
cleared.
Step 4 If the alarm persists, perform a self-loop at the local end to check whether the board at the
local or opposite end is faulty. Then, replace the faulty board.
----End
Related Information
None.
4.2.224 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 437
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
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).
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.
l The services are incorrectly configured.
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 is cleared The fault is removed. End the alarm handling.
This alarm persists Proceed to the next step.
Step 3 Check whether the services at the opposite station and the local station are correctly
configured. If not, modify the incorrect configuration and issue it again.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 438
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.225 LP_SLM_VC3
Description
The LP_SLM_VC3 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
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.
l The services are incorrectly configured.
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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 439
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 View alarms on the U2000 to check whether the LP_SLM_VC3 alarm is cleared.
If... Then...
If this alarm is cleared The fault is removed. End the alarm
handling.
If this alarm persists Proceed to the next step.
Step 3 Check whether the services at the opposite station and the local station are correctly
configured. If not, modify the incorrect configuration and issue it again.
----End
Related Information
None
4.2.226 LP_T_FIFO
Description
The LP_T_FIFO alarm indicates that FIFO overflow on the transmit side of the lower order
path.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 This parameter is ineffective. It has a fixed value of 0x01.
Parameter 2, Parameter 3 Indicates the path ID.
Impact on the System
Bit errors occur in lower order services of the board.
Possible Causes
Possible causes of this alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 440
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The service cross-connections are incorrectly configured.
l The services received by the board are incorrect.
Procedure
Step 1 View the LP_T_FIFO alarm on the U2000, and check whether the service configurations on
the board that reports the LP_T_FIFO alarm and the NE are correct. If the service
configurations are incorrect, modify the service configurations and check whether the alarm is
cleared.
Step 2 If the alarm persists, check whether the services received by the board are correct. After
ensuring that the services are correct, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the board.
----End
Related Information
None.
4.2.227 LP_TIM
Description
The LP_TIM alarm indicates inconsistent lower order path trace identifiers. This alarm is
generated when a board detects inconsistent J2 or J1 bytes.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
This alarm does not have any impact on the system.
Possible Causes
Possible causes of this alarm are as follows:
l The lower order path trace identifier at the local end is inconsistent with that at the
opposite end.
l The service cross-connections are incorrectly configured.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 441
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View the LP_TIM alarm on the U2000 to determine the ID of the path where the LP_TIM
alarm is generated.
Step 2 Ensure that the lower order path trace identifier on the tributary board at the opposite end is
consistent with that on the line board at the local end. Then, check whether the LP_TIM alarm
is cleared.
Step 3 If the alarm persists, check whether the service cross-connection configuration of the path on
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 at the local end to check whether the board at the
local or opposite end is faulty. Then, replace the faulty board.
----End
Related Information
None.
4.2.228 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating the mismatch of the lower order path trace
identifier received by the tributary board.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
This alarm does not have any impact on the system.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 442
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible causes of the LP_TIM_VC12 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.
l The services are incorrectly configured.
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 is cleared The fault is removed. End the alarm handling.
This alarm persists Proceed to the next step.
Step 3 Check whether the services at the opposite station and the local station are correctly
configured. If not, modify the incorrect configuration and issue it again.
Step 4 If the alarm persists, replace the faulty board.
----End
Related Information
None
4.2.229 LP_TIM_VC3
Description
The LP_TIM_VC3 is an alarm indicating the mismatch of the lower order path trace identifier
received by the tributary board.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 443
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
This alarm does not have any impact on the system.
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.
l The services are incorrectly configured.
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...
If this alarm is cleared The fault is removed. End the alarm
handling.
If this alarm persists Proceed to the next step.
Step 3 Check whether the services at the opposite station and the local station are correctly
configured. If not, modify the incorrect configuration and issue it again.
Step 4 If the alarm persists, replace the faulty board.
----End
Related Information
None
4.2.230 LP_UNEQ
Description
The LP_UNEQ alarm indicates that the lower order path is not loaded with signals. This
alarm is generated when a board detects that the signal label in the V5 byte is 0.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 444
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
NOTE
The V5 byte is used to detect bit errors and indicate a remote error or failure in the lower order path.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
The lower order path services are unavailable. If the services are configured with protection,
the protection switching is triggered.
Possible Causes
Possible causes of this alarm are as follows:
l The lower order path at the local end is configured with services, but the lower order
path at the opposite end is not configured with services.
l The cross-connection configurations on the transit NEs are incorrect.
Procedure
Step 1 Check whether the lower order path at the opposite end is configured with services.
If... Then...
The lower order path at the opposite end is Configure services for the lower order path
not configured with services at the opposite end. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The lower order path at the opposite end is Go to the next step.
configured with services
Step 2 Check whether the cross-connect configurations on the transit NEs are correct.
If... Then...
The cross-connect configurations are Correct the cross-connect configurations.
incorrect Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The cross-connect configurations are correct Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 445
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the attributes of the board are correctly configured. If the attributes are
incorrectly configured, modify the incorrect configuration. Then, the LP_UNEQ alarm is
automatically cleared.
----End
Related Information
None.
4.2.231 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 alarm indicates that the VC-12 path is not loaded with signals.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
When the LP_UNEQ_VC12 alarm occurs, no services are loaded in the payload of the lower
order path (VC-12: V5 [b5-b7], VC-3: C2) received by the 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.
l The T_ALOS alarm is reported on the board at the opposite station of the SDH
transmission equipment, and the LP_UNEQ_VC12 is enabled to be inserted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 446
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 is cleared The fault is removed. End the alarm handling.
This alarm persists Proceed to the next step.
Step 3 Check whether the T_ALOS alarm is reported on the 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
4.2.232 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 alarm indicates that the VC-3 path is not loaded with signals.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 447
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When the LP_UNEQ_VC3 alarm occurs, no services are loaded in the payload of the lower
order path (VC-12: V5 [b5-b7], VC-3: C2) received by the 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.
l The T_ALOS alarm is reported on the 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 NMS to check whether the LP_UNEQ_VC3 alarm is cleared.
If... Then...
If this alarm is cleared The fault is removed. End the alarm
handling.
If this alarm persists Proceed to the next step.
Step 3 Check whether the T_ALOS alarm is reported on the 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
Related Information
T_ALOS
4.2.233 LPS_UNI_BI_M
Description
The LPS_UNI_BI_M alarm indicates a mismatch of the single-ended/dual-ended mode in a
linear multiplex section protection (MSP). This alarm is applicable to only linear MSPs. This
alarm is generated when the single-ended/dual-ended mode at the opposite end indicated by
the three least significant bits of the K2 byte is inconsistent with the ended/dual-ended mode
at the local end for a period of time (2 seconds by default).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 448
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Impact on the System
MSP becomes unavailable. If an optical fiber cut or other faults occur at this time, services are
interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The MSP configurations are incorrect.
l The boards configured with MSP are faulty.
l The cross-connect units are faulty.
Procedure
Step 1 Check whether the MSP configurations at the two ends are consistent.
If... Then...
The MSP configurations are inconsistent Ensure that the MSP configurations at the
two ends are consistent. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The MSP configurations are consistent Go to the next step.
Step 2 Check whether the boards configured with MSP are faulty at the two ends.
If... Then...
The boards configured with MSP are faulty Replace the faulty boards. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The boards configured with MSP are Go to the next step.
properly functioning
Step 3 Check whether the cross-connect units at the two ends are faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 449
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The cross-connect units are faulty Replace the system control, cross-connect,
and timing boards. Then, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The cross-connect units are properly Go to the next step.
functioning
Step 4 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
Single-ended/Dual-ended mode
The single-ended/dual-ended mode refers to the revertive mode of the linear MSP switching.
The revertive mode can be either the single-ended mode or the dual-ended mode.
4.2.234 LPT_AUTH_FAIL
Description
The LPT_AUTH_FAIL alarm indicates that LPT authentication fails.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the LPT type.
Parameters 2–5 If the LPT type is uniport, these parameters indicate the slot ID.
Otherwise, the value of these parameters is 0xFFFFFFFF.
Parameters 6–9 If the LPT type is uniport, these parameters indicate the subboard ID.
Otherwise, the value of these parameters is 0xFFFFFFFF.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 450
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameters 10–12 If the LTP type is uniport, these parameters indicate the port ID.
Otherwise, these parameters indicate the index number of PW, QINQ,
or L2NET.
Impact on the System
When the alarm is generated, LPT packet authentication fails, causing a network fault.
Possible Causes
l Cause 1: LPT packet authentication fails.
Procedure
Step 1 Cause 1: LPT packet authentication fails.
1. Check whether the authentication keys are consistently configured for the nodes. If not,
reconfigure the authentication keys.
2. Check whether a packet attack occurs. If yes, isolate the attack source.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers.
----End
Related Information
None
4.2.235 LPT_CFG_CLOSEPORT
Description
The LPT_CFG_CLOSEPORT alarm indicates that the LPT function shuts down a service
port. After detecting that the remote access port fails or the aggregation port at the local NE
fails, the LPT function automatically shuts down the local access-point port and reports this
alarm.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 451
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When this alarm is reported, a port is shut down. If no protection is configured on the port,
services carried on the port are interrupted. If protection is configured on the port, services are
switched to the standby link for transmission.
Possible Causes
Possible causes of the LPT_CFG_CLOSEPORT alarm are as follows:
l A port failure is detected on the remote access point.
l The aggregation port at the local end is faulty.
l The LPT service network is faulty.
Procedure
Step 1 On the U2000, check whether the remote aggregation port reports the ETH_LOS or
LSR_NO_FITED alarm.
If... Then...
The ETH_LOS or Handle the ETH_LOS or LSR_NO_FITED alarm, and
LSR_NO_FITED alarm is check whether the LPT_CFG_CLOSEPORT alarm is
reported cleared. If the LPT_CFG_CLOSEPORT alarm persists,
go to the next step.
The ETH_LOS or Go to the next step.
LSR_NO_FITED alarm is not
reported
Step 2 On the U2000, check whether the local aggregation port reports the ETH_LOS or
LSR_NO_FITED alarm.
If... Then...
The ETH_LOS or Handle the ETH_LOS or LSR_NO_FITED alarm, and
LSR_NO_FITED alarm is check whether the LPT_CFG_CLOSEPORT alarm is
reported cleared. If the LPT_CFG_CLOSEPORT alarm persists,
go to the next step.
The ETH_LOS or Go to the next step.
LSR_NO_FITED alarm is not
reported
Step 3 Check whether a fiber cut or a tunnel signal degrade occurs on the LPT service network.
Step 4 Rectify the fault that occurs on the service network. Then, check whether the
LPT_CFG_CLOSEPORT alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 452
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
The alarm persists Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.236 LPT_RFI
Description
The LPT_RFI is the remote failure indication of Link state pass-through (LPT).
Attribute
Alarm Severity Alarm Type
Critical Service quality 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the IP port number.
Parameter 2, parameter 3 Indicates the logical port number, and the value is always 0x01.
Parameter 4, parameter 5 Reserved. Each parameter has a fixed value of 0xff.
Impact on the System
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 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 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 453
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 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
4.2.237 LSR_BCM_ALM
Description
The LSR_BCM_ALM alarm indicates that the bias current of the laser crosses the thresholds.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port ID.
Impact on the System
When the LSR_BCM_ALM alarm occurs, the laser works improperly. If the working current
crosses the upper threshold, the laser will be damaged. If the working current crosses the
lower threshold, gain becomes insufficient. In both cases, services will be interrupted.
Possible Causes
Possible causes of the LSR_BCM_ALM alarm are as follows:
l The laser is aging.
l The laser is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 454
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Determine the alarmed board according to the alarm information on the U2000.
Step 2 Replace the optical module. The LSR_BCM_ALM alarm is cleared.
----End
Related Information
None.
4.2.238 LSR_COOL_ALM
Description
The LSR_COOL_ALM alarm indicates that the cooling current of the laser crosses the
threshold.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
When the cooling current of the laser exceeds the threshold, the optical module of the board
works abnormally. As a result, services cannot be transmitted or received normally.
Possible Causes
l The ambient temperature is excessively high.
l The laser is faulty.
Procedure
Step 1 Check whether the ambient temperature is excessively high. If yes, decrease it to a proper
value for the equipment to work well, and then check whether the LSR_COOL_ALM alarm is
cleared.
Step 2 If the alarm persists, the laser may be faulty. Replace the board that generates the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 455
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.239 LSR_NO_FITED
Description
The LSR_NO_FITED alarm indicates that no pluggable optical module is installed on the
board.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None.
Impact on the System
The board cannot receive and transmit services.
Possible Causes
Possible causes of this alarm are as follows:
l The pluggable optical module is not installed or is not correctly installed.
l The optical module is faulty.
l The board is faulty.
Procedure
Step 1 Check whether a pluggable optical module is correctly installed.
If... Then...
The pluggable optical module is not Install the pluggable optical module
installed or is not correctly installed correctly. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The optical module is correctly installed Go to the next step.
Step 2 Replace the optical module. Then, check whether the alarm is cleared.
The pluggable optical module on the board supports hot swap.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 456
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the board that reports the alarm.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.240 LSR_WILL_DIE
Description
The LSR_WILL_DIE alarm indicates that the life of the laser on the board will end.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None.
Impact on the System
If the life of the laser ends, the board cannot transmit and receive services correctly. The laser
must be replaced as soon as possible.
If the laser is not replaced in a timely manner, services will be interrupted.
Possible Causes
The possible cause of this alarm is as follows:
The laser is deteriorating, which causes excessively high bias current.
Procedure
Step 1 Replace the laser. Then, check whether the alarm is cleared.
If... Then...
The alarm persists Replace the board that reports the alarm.
The alarm is cleared No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 457
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
----End
Related Information
None.
4.2.241 LTI
Description
The LTI alarm indicates loss of synchronization clock sources configured for the timing unit.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: All the synchronization sources of the system clock are lost.
l 0x02: All the synchronization sources of the first 2 MHz phase-locked
source are lost.
l 0x03: All the synchronization sources of the second 2 MHz phase-locked
source are lost.
Impact on the System
The clock of the local NE enters the free-run state and cannot be synchronized with the clocks
of other NEs.
If the free-run state lasts for a long time, bit errors on the receive side, pointer justification, or
alignment signal loss may occur.
Possible Causes
Possible causes of this alarm are as follows:
l The clock configurations are incorrect.
l The optical fiber (in the case of tracing the line clock source) or cable (in the case of
tracing the tributary clock source) is broken.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 458
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l No external clock source is input (in the case of tracing the external clock source).
l The clock source is configured to be non-revertive, or is blocked, or is incorrectly
configured.
l The external clock, the clock delivered by the system control unit, and the local free-run
clock are lost.
l All the clock sources in the clock source priority table fail.
l A board is faulty.
Procedure
Step 1 Check whether the configured synchronization sources are available.
If... Then...
The configured synchronization sources are Ensure that the configured synchronization
unavailable sources are available. Then, check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The configured synchronization sources are Go to the next step.
available
Step 2 Check whether the traced clock source is normal.
If... Then...
The line clock source is traced, and the line Clear the R_LOS, R_LOF, or R_LOC
board report the R_LOS, R_LOF, or alarm. Then, check whether the LTI alarm is
R_LOC alarm cleared. If the LTI alarm persists, go to the
next step.
The tributary clock source is traced, and the Clear the T_ALOS or E1_LOS alarm. Then,
tributary board reports the T_ALOS or check whether the LTI alarm is cleared. If
E1_LOS alarm the LTI alarm persists, go to the next step.
The external clock source is traced Ensure that the external clock cable is
securely connected and is properly
functioning. Then, check whether the alarm
is cleared. If the alarm persists, go to the
next step.
Step 3 The timing unit is faulty. Replace the system control, cross-connect, and timing board. Then,
the alarm is automatically cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 459
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.242 MAC_FCS_EXC
Description
The MAC_FCS_EXC alarm indicates that a bit error threshold-crossing event is detected at
the MAC layer. The software periodically detects the number of bytes received by the MAC
chip and the number of bytes that have bit errors. This alarm is reported when the number of
bit errors crosses the threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When the MAC_FCS_EXC alarm occurs, services degrade or even are interrupted.
Possible Causes
The possible causes of the MAC_FCS_EXC alarm are as follows:
l Cause 1: Line signals deteriorate.
l Cause 2: The transmit optical power at the peer end is abnormal, which may be caused
by a dirty fiber connector or fiber performance deterioration.
l Cause 3: The receive optical power at the local end is abnormal, which may be caused by
a dirty fiber connector or fiber performance deterioration.
Procedure
l Cause 1: Line signals deteriorate.
a. On the NMS, check whether the DOS attack exists. If yes, eliminate the source that
transmits a large amount of invalid data, and then check whether the
MAC_FCS_EXC alarm is cleared.
b. If the alarm persists, check whether the cable or fiber is faulty. If yes, replace the
faulty cable or fiber, and check whether the MAC_FCS_EXC alarm is cleared.
c. If the alarm persists, go to Cause 2.
l Cause 2: The transmit optical power at the peer end is abnormal, which may be caused
by a dirty fiber connector or fiber performance deterioration.
a. On the NMS, check whether the transmit optical power at the peer end is within the
normal range.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 460
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The transmit optical power is Go to the next step.
beyond the normal range
The transmit optical power is within Go to Cause 3.
the normal range
b. Check the jumper connectors and fiber connectors.
n Check whether the fiber connector is properly connected. Ensure that the fiber
connector is installed securely. Check whether the alarm is cleared.
n If the alarm persists, see Cleaning the Optical Fiber Connector and check
whether the fiber connector is clean. If the fiber connector is dirty, clean it.
c. If the alarm persists, check whether the attenuation value of the optical attenuator is
proper.
If... Then...
The attenuation value of the optical Adjust the value properly. Check
attenuator is improper whether the alarm is cleared. If the
alarm persists, go to the next step.
The attenuation value of the optical Go to the next step.
attenuator is proper
d. Check whether the flange is correctly connected. Ensure that the flange is correctly
connected, and then check whether the alarm is cleared.
e. If the alarm persists, replace the optical module located at the transmit port of the
peer NE.
f. If the alarm persists, check whether the service processing board and cross-connect
board of the peer NE report hardware-related alarms, such as HARD_BAD and
TEMP_OVER. If yes, replace the board that reports a hardware-related alarm.
Then, check whether the alarm is cleared. If the alarm persists, go to Cause 3.
l Cause 3: The receive optical power at the local end is abnormal, which may be caused by
a dirty fiber connector or fiber performance deterioration.
a. On the NMS, check whether the receive optical power at the local end is within the
normal range. For details, see a in Cause 2.
b. If the receive optical power is beyond the normal range, see b to f in Cause 2 for
troubleshooting at the local end.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 461
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.243 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crosses
the threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the threshold crossing type.
l 0x01: ETHDROP threshold crossing
l 0x02: ETHEXCCOL threshold crossing
l 0x03: RXBBAD threshold crossing
Impact on the System
Service performance deteriorates.
Possible Causes
l Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the
upper threshold.
l Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfully
transmitted after successive collisions crosses the upper threshold.
l Cause 3: RXBBAD threshold crossing. The number of received bad packets crosses the
upper threshold.
Procedure
Step 1 Check whether the working modes of the ports at the transmit and receive ends are the same.
1. On the NMS, query the working modes of the ports at both ends.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 462
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The ports at both ends work in different Set the working modes of the two ports to
modes or in half-duplex mode both full-duplex or auto-negotiation by
referring to Setting the General Attributes
of Ethernet Interfaces.
The ports at both ends work in the same Go to the next step.
mode and are not working in half-
duplex mode
Step 2 Handle the packet transmission errors at the opposite end. Check whether the fiber or the
optical module are normal.
If... Then...
faulty, Replace the fiber or the optical module.
not faulty, Go to the next step.
Step 3 Check whether PLA configurations are correct. Check whether the local end reports
ETH_LOS alarm caused by external line breakage or excessive attenuation.
If... Then...
exists, Refer to the corresponding section in this document to clear alarm.
not exists, Go to the next step.
Step 4 If the board are faulty, Replace the board.
Step 5 Check whether alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.244 MASTER_SLAVE_MISMATCH
Description
The MASTER_SLAVE_MISMATCH is an alarm indicating that the logical types of the
master and slave cross-connect boards are mismatched.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 463
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm type:
0x01: indicates the logical types of the master and slave cross-connect
boards are mismatched.
Parameter 2, Indicates the cross-connect board slot number.
Parameter 3
The value of this parameter 2 is always 0x53, and the value of this
parameter is always 0x54.
The value of this parameter is always 0x01. Indicates the logical types
Parameter 4
of the master and slave cross-connect boards are mismatched.
Impact on the System
None
Possible Causes
The possible cause of the MASTER_SLAVE_MISMATCH alarm is as follows:
Cause: The logical types of the master and slave cross-connect boards are mismatched.
Procedure
Step 1 Modify the configuration of the master and slave cross-connect boards on the NE and ensure
the logical types of the master and slave cross-connect boards are same.
Step 2 Then, check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.245 MCLAG_CFG_MISMATCH
Description
The MCLAG_CFG_MISMATCH alarm indicates that MC-LAG configurations at two ends
are inconsistent.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 464
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicate the mismatch type.
Parameter 2
l 0x01: The LAG IDs at two ends are different.
l 0x02: The LAG aggregation types at two ends are different.
l 0x04: The MC-LAG load-sharing modes at two ends are different.
l 0x08: The MC-LAG revertive modes at two ends are different.
Impact on the System
Negotiation of MC-LAG configurations fails and services may be unavailable.
Possible Causes
The possible causes of the MCLAG_CFG_MISMATCH alarm are as follows:
l Cause 1: The LAG IDs at two ends are different.
l Cause 2: The LAG aggregation types at two ends are different.
l Cause 3: The MC-LAG load-sharing modes at two ends are different.
l Cause 4: The MC-LAG revertive modes at two ends are different.
Procedure
Step 1 Cause 1: The LAG IDs at two ends are different.
Cause 2: The LAG aggregation types at two ends are different.
Cause 3: The MC-LAG load-sharing modes at two ends are different.
Cause 4: The MC-LAG revertive modes at two ends are different.
1. Check whether the MC-LAG parameters (such as LAG ID, LAG aggregation type, LAG
load-sharing mode, and LAG revertive mode) at the two ends are set to the same. If the
MC-LAG parameters at the two ends are different, change them to the same. Then,
check whether the alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers for handling the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 465
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.246 MCSP_PATH_LOCV
Description
The MCSP_PATH_LOCV alarm indicates the loss of connectivity on a protocol channel on
which synchronous cross-equipment communication is achieved. This alarm is reported if
expected Hello packets are not received on the protocol channel in three consecutive periods.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the protocol channel ID.
Impact on the System
Dual-homing protection fails.
Possible Causes
The possible causes of the MCSP_PATH_LOCV alarm are as follows:
l Cause 1: The physical link that carries Hello packets is interrupted.
l Cause 2: The corresponding protocol channel is not configured on the NE at the peer
end.
l Cause 3: The NE at the peer end is faulty.
Procedure
Step 1 Cause 1: The physical link that carries Hello packets is interrupted.
1. Check whether the physical connection to the NE at the peer end is available. Check
whether the NE reports the ETH_LOS, R_LOS, or MPLS_TUNNEL_LOCV alarm,
indicating a link failure.
2. If yes, clear these alarms first. Check whether the MCSP_PATH_LOCV alarm is cleared.
If the alarm persists, go to Step 2.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 466
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Cause 2: The corresponding protocol channel is not configured on the NE at the peer end.
1. According to the NE planning table, check whether the corresponding protocol channel
is correctly configured on the NE at the peer end.
2. Configure the corresponding protocol channel on the NE at the peer end. Then, check
whether the MCSP_PATH_LOCV alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The NE at the peer end is faulty.
1. Check whether the NE at the peer end works properly. For example, check whether the
NE icon on the main topology of the NMS turns gray.
2. If the NE at the peer end is in the reset or power-off state, it automatically resumes
sending of Hello packets after being restored.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for handling the alarm.
----End
Related Information
None
4.2.247 MDL_ALARM
Description
The MDL_ALARM is an alarm of power module faults.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the faulty power module:
l 0x01: Power module 1.
l 0x02: Power module 2.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 467
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2, Indicates the causes for the faults of the power module. Parameter 2 is
Parameter 3 the higher byte, and Parameter 3 is the lower byte.
The value of Parameter 2 is always 0x00. The values of Parameter 3 are
as follows:
l 0x01: Power off.
l 0x02: Fault.
l 0x03: Protection.
l 0x04: Communication failure.
Impact on the System
The MDL_ALARM alarm affects the power supply of the system. This can cause the NE to
be abnormal.
Possible Causes
The possible causes of the MDL_ALARM alarm are as follows:
l Cause 1: The cable connecting the Power Module to the equipment is faulty.
l Cause 2: The Power Module is faulty.
l Cause 3: The standby module of the Power Module is faulty.
Procedure
Step 1 View the MDL_ALARM alarm on the U2000. Confirm the cause for the fault of the power
module according to Parameter 3.
l In case of power off, power on the system. Then, check whether the MDL_ALARM
alarm is cleared.
l In case of hardware faults, replace the CAU board.
l In case of communication failure, detect the failure cause and troubleshoot it. Then,
check whether the MDL_ALARM alarm is cleared.
----End
Related Information
None.
4.2.248 MOD_COM_FAIL
Description
The MOD_COM_FAIL alarm indicates that communication between modules fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 468
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 0x11 indicates that communication between the SCC unit and the packet
switching unit fails.
Impact on the System
Modules cannot be operated by using the U2000 and module performance information cannot
be queried on the U2000.
Possible Causes
l The related module software on the board performs incorrect processing.
l The board is faulty.
Procedure
Step 1 Reset (cold) or reseat the faulty board and check whether the alarm is cleared.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 2 Replace the faulty board and check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 469
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.249 MOD_TYPE_MISMATCH
Description
The MOD_TYPE_MISMATCH is an alarm indicating that a mismatched port module is
detected.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. For example,
Parameter 1 = 0x01 indicates that the alarm is reported by port 1 of the
related board.
Parameter 2, Parameter 2 is always 0x00, and Parameter 3 is always 0x01. These
Parameter 3 parameters are meaningless.
Impact on the System
The services carried over the port are interrupted.
Possible Causes
The possible causes of the MOD_TYPE_MISMATCH alarm are as follows:
The type of the SFP module is different from the equipment module type.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 470
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Based on the alarm parameters, locate the port that reports the alarm.
Step 2 Verify the type of the SFP module that connects to the port.
Step 3 If the type defined for the SFP module is wrong, replace the SFP module.
Step 4 If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None.
4.2.250 MP_DELAY
Description
The MP_DELAY alarm indicates that the differential delay of the PPP members in an MP
group exceeds the specified threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Parameter 2 Indicates the sub-board ID.
Parameter 3, Parameter 4 Indicate the port ID.
Parameter 5 Indicates the timeslot number or path ID.
0xff indicates that Parameter 5 is reserved.
Impact on the System
The services in the MP group deteriorate.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 471
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The configured maximum differential delay is over low.
l Cause 2: The network bandwidth is insufficient.
l Cause 3: Signals deteriorate because of damaged optical fibers.
Procedure
Step 1 Cause 1: The configured maximum differential delay is over low.
1. On the NMS, check whether the maximum differential delay configured for the MP
group is over low. If the maximum differential delay is over low, follow the instructions
in Creating MP Groups to increase the maximum differential delay.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network bandwidth is insufficient.
1. Check whether the network bandwidth is sufficient. If the bandwidth is insufficient, add
PPP members in the MP group to increase the bandwidth. For details, see Creating MP
Groups.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Signals deteriorate because of damaged optical fibers.
1. Check whether the optical fiber is intact. If the optical fiber is damaged, replace it.
2. Check whether alarm is cleared. If the alarm persists, contact Huawei technical support
personnel to handle the alarm.
----End
Related Information
None
4.2.251 MP_DOWN
Description
The MP_DOWN alarm indicates that an MP group fails. This alarm is reported when the
number of active members in an MP group is less than the specified minimum number of
active links. The default minimum number of active links is 1.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 472
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the MP group failure.
l 0x00: Unknown
l 0x01: The number of members in the MP group is less than the specified
number.
l 0x02: The MP configurations at two ends are inconsistent.
l 0x03: The Network Control Protocol (NCP) of the MP group is running
abnormally.
Impact on the System
The services in the MP group are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The MP configurations at the local and opposite ends are inconsistent or no IP
addresses are specified for the two ends.
l Cause 2: The Network Control Protocol (NCP) of member links in the MP group is
running abnormally.
l Cause 3: The physical link is interrupted.
Procedure
Step 1 Cause 1: The MP configurations at the local and opposite ends are inconsistent or no IP
addresses are specified for the two ends.
1. Check whether the MP configurations at the local and opposite ends are consistent and
whether IP addresses are configured for the two ends.
– If they are inconsistent, configure them consistently. For details, see Creating MP
Groups.
– If no IP addresses are configured for the two ends, configure IP addresses and
subnet masks for them. For details, see Creating MP Groups.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The Network Control Protocol (NCP) of member links in the MP group is running
abnormally.
1. On the NMS, check whether member links in the MP group have the 4.2.392
PPP_LCP_FAIL or 4.2.393 PPP_NCP_FAIL alarm. If such an alarm occurs, clear the
alarm first.
2. Check whether the MP_DOWN alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The physical link is interrupted.
1. Check whether member links in the MP group have the R_LOS or T_ALOS alarm
indicating loss of signals. If such an alarm occurs, clear the alarm first.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 473
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the MP_DOWN alarm is cleared. If the alarm persists, contact Huawei
technical support personnel to handle the alarm.
----End
Related Information
None
4.2.252 MPLS_PW_AIS
Description
The MPLS_PW_AIS is an alarm indicating that a defect is detected on a PW. The MIP NE
sends AIS packets to the downstream NE when it detects a fault on a tunnel carrying PW. The
sink MEP NE reports this alarm upon receiving the AIS packet.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
The possible cause of the MPLS_PW_AIS alarm is as follows:
The MIP NE detects a fault on a tunnel carrying the PW.
Figure 4-7 shows the process of MPLS_PW_AIS alarm detection.
Figure 4-7 MPLS_PW_AIS alarm detection
5. Generate the
2. Configure MS-PW. MPLS_PW_LOCV alarm after
3. Enable AIS insertion. failing to receive OAM packets.
1. Send OAM packets. 4. The MIP NE inserts AIS 6. Receive AIS packets, report
an MPLS_PW_AIS alarm, and
packets after detecting a fault.
suppress the MPLS_PW_LOCV
alarm.
OAM packets AIS packets
MEP MIP MEP
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 474
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the MPLS tunnel OAM are correctly configured for source and sink MEP NEs
and MIP NEs. If the MPLS tunnel OAM is configured incorrectly, modify MPLS tunnel
OAM configurations by referring to section Configuring MPLS OAM in Configuration Guide
(Packet Transport Domain). Then, check whether the alarm is cleared.
Step 2 If the alarm is uncleared, query whether there are tunnel-related alarms on MEP NEs, such as
4.2.269 MPLS_TUNNEL_AIS. If yes, clear them immediately. Then, check whether the
MPLS_PW_AIS alarm is cleared.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.253 MPLS_PW_BDI
Description
The MPLS_PW_BDI alarm indicates defects in the backward direction of a PW. This alarm is
reported when a BDI packet is received at the receive end, indicating that the forward PW is
faulty.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
This alarm affects services and even causes service interruption on the transmit side at the
local end.
Possible Causes
Possible causes of the MPLS_PW_BDI alarm are as follows:
l The physical link between the local NE and the remote NE is faulty.
l A hardware fault occurs at the remote end.
Procedure
Step 1 Check whether an optical fiber or a cable between the local NE and the opposite NE is
damaged.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 475
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
An optical fiber or cable is Replace the faulty optical fiber or cable and check
damaged whether the alarm is cleared. If the alarm persists, go
to the next step.
An optical fiber or cable is not Go to the next step.
damaged
Step 2 On the U2000, check whether any NE on the link reports hardware-related alarms (alarms on
optical modules or boards), such as HARD_BAD and LSR_NO_FITED.
If... Then...
The HARD_BAD or Handle the HARD_BAD or LSR_NO_FITED
LSR_NO_FITED alarm is reported alarm, and check whether the MPLS_PW_BDI
alarm is cleared. If the MPLS_PW_BDI alarm
persists, go to the next step.
The HARD_BAD or Go to the next step.
LSR_NO_FITED alarm is not
reported
Step 3 If the MPLS_PW_BDI alarm persists, contact Huawei technical support engineers to handle
the alarm.
----End
Related Information
None.
4.2.254 MPLS_PW_CSF
Description
The MPLS_PW_CSF alarm indicates that client signals fail. This alarm is reported when the
local NE receives a Client Signal Fail (CSF) packet from the opposite NE, indicating that a
fault occurs at the remote NE's client layer.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 476
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
Services are interrupted.
Possible Causes
The possible cause of this alarm is as follows:
Cause: A fault occurs at the client access side.
As shown in Figure 4-8, upon detecting a client service signal failure, MEP1 sends a PW
CSF packet to MEP2. MEP2 reports the MPLS_PW_CSF alarm after receiving the PW CSF
packet.
Figure 4-8 MPLS_PW_CSF generation process
1. Detects a fault at the AC 3. Reports an
side. MPLS_PW_CSF alarm
2. Sends a PW CSF packet to upon receiving the PW
the downstream MEP. CSF packet.
MEP1 MEP2
PW CSF
packet
NodeB
LSR A LSR B RNC
Procedure
Step 1 Cause: A fault occurs at the client access side.
1. Check whether the transmit port on the opposite client side is disabled. If the transmit
port is disabled, enable it. Check whether the alarm is cleared. If the alarm persists, go to
the next step.
2. Check whether a board is faulty or reset on the opposite client side. If a board is reset,
check whether the alarm is cleared after the board reset is complete. If a board is faulty,
replace the faulty board. Check whether the alarm is cleared. If the alarm persists, go to
the next step.
3. Check whether a link on the opposite client side is faulty. If a link is faulty, replace it.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 477
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.255 MPLS_PW_Excess
Description
The MPLS_PW_Excess alarm indicates that excessive PW trail termination source identifiers
(TTSIs) are received. This alarm is reported if five or more correct CV/FFD packets are
received in three consecutive CV/FFD periods.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None.
Impact on the System
PW services are interrupted. If traffic of packets is higher than the link capacity, Ethernet
services may be interrupted.
Possible Causes
Possible causes of the MPLS_PW_Excess alarm are as follows:
l Multiple PWs are configured with the same PW label and PW ID.
l The physical link is connected incorrectly.
Procedure
Step 1 On the U2000, check whether the PW OAM attribute at the local NE is consistent with that at
the remote NE.
If... Then...
The PW OAM attributes are Reconfigure the PW OAM attributes to be consistent,
inconsistent and check whether the alarm is cleared. If the alarm
persists, go to the next step.
The PW OAM attributes are Go to the next step.
consistent
Step 2 On the U2000, check whether several PWs are configured with the same PW label and PW
ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 478
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Several PWs are configured with the Delete redundant PWs or configure a unique label
same PW label and PW ID and PW ID for each PW, and check whether the
alarm is cleared. If the alarm persists, go to the
next step.
Each PW is configured with a unique Go to the next step.
label and PW ID
Step 3 Check whether an optical fiber or a cable is incorrectly connected between both ends.
If... Then...
An optical fiber or cable is Rectify the connection or service configurations based
incorrectly connected on the actual networking scenario. Check whether the
alarm is cleared. If the alarm persists, go to the next
step.
No optical fiber or cable is Go to the next step.
incorrectly connected
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.256 MPLS_PW_LCK
Description
The MPLS_PW_LCK alarm indicates that the PW server layer is locked. This alarm is
reported when an MEP receives a locked signal function (LCK) packet from its upstream NE,
indicating that the PW server layer is locked and the MPLS_PW_LOCV alarm is suppressed.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 479
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of this alarm is as follows:
Cause: The PW server layer (tunnel) is locked.
As shown in Figure 4-9, a command to lock the tunnel layer is issued on MEP2 and MEP2
reports an MPLS_TUNNEL_LOCK alarm and inserts PW LCK packets to the PW layer.
After receiving PW LCK packets from MEP2, MEP3 reports an MPLS_PW_LCK alarm. The
PW server layer is locked and the MPLS_PW_LOCV alarm is suppressed.
Figure 4-9 MPLS_PW_LCK generation process
1. Issues a command to lock the 4. Reports an
tunnel layer. MPLS_PW_LCK alarm and
2. Reports an suppresses the
MPLS_TUNNEL_LOCK alarm. MPLS_PW_LOCV alarm
3. Inserts a PW LCK packet to the upon receiving the PW LCK
PW layer. packet.
MEP1 MEP2 PW LCK MEP3
packet
LSR A LSR B LSR C
Tunnel 1 Tunnel 2 Tunnel
layer
PW 1 PW 2 PW
layer
MS-PW
Procedure
Step 1 Cause: The PW server layer (tunnel) is locked.
1. Check the PW server layer path and unlock the tunnel layer. For details, see Configuring
LCK of MPLS-TP PW OAM.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.257 MPLS_PW_LOCK
Description
The MPLS_PW_LOCK alarm indicates that a command to lock the PW layer is issued on an
MEP.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 480
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
None
Possible Causes
The possible cause of this alarm is as follows:
Cause: A command to lock the PW layer is issued on an MEP.
As shown in Figure 4-10, a command to lock the PW layer is issued on MEP3 and MEP3
reports an MPLS_PW_LOCK alarm.
Figure 4-10 MPLS_PW_LOCK generation process
1. Issues a command to lock the
PW layer.
2. Reports an MPLS_PW_LOCK
alarm.
MEP1 MIP2 MEP3
LSR A LSR B LSR C
Tunnel 1 Tunnel 2 Tunnel
layer
PW 1 PW
layer
Procedure
Step 1 Cause: A command to lock the PW layer is issued on an MEP.
1. Unlock the PW layer. For details, see Configuring LCK of MPLS-TP PW OAM.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 481
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.258 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV alarm indicates loss of PW connectivity. This alarm is reported if the
expected CV/FFD packet is not received in three consecutive periods.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The services that the faulty PW carries may be interrupted.
Possible Causes
Possible causes of the MPLS_PW_LOC alarm are as follows:
l The remote NE stops sending CV/FFD packets.
l The PW OAM attribute at the local NE is inconsistent with that at the remote NE.
l The service ports are incorrectly configured.
l PWs carrying services are faulty.
l The network is heavily congested.
l The equipment at the remote end is faulty.
Procedure
Step 1 On the U2000, check whether the remote NE has stopped sending CV/FFD packets.
If... Then...
The remote NE has stopped sending Enable the remote NE to send CV/FFD packets and
CV/FFD packets check whether the alarm is cleared. If the alarm
persists, go to the next step.
The remote NE does not stop Go to the next step.
sending CV/FFD packets
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 482
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 On the U2000, check whether the PW OAM attribute at the local NE is inconsistent with that
at the remote NE.
If... Then...
The PW OAM attributes are Go to the next step.
consistent
The PW OAM attributes are Reconfigure the PW OAM attributes to be consistent
inconsistent and check whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 3 Check whether the service port configuration is correct based on service plans.
If... Then...
The service port configuration is Reconfigure the service ports and check whether the
incorrect alarm is cleared. If the alarm persists, go to the next
step.
The service port configuration is Go to the next step.
correct
Step 4 Check whether an optical fiber or a cable between both ends is faulty.
If... Then...
An optical fiber or cable is Replace the faulty optical fiber or cable and check
faulty whether the alarm is cleared. If the alarm persists, go to
the next step.
An optical fiber of cable is Go to the next step.
correct
Step 5 Based on the actual situation, increase the value of Detection Packet Period appropriately.
Then, check whether the alarm is cleared.
If... Then...
The alarm is Check the PW bandwidth utilization. If the PW bandwidth is fully
cleared occupied, expand the bandwidth allocated to the PW or eliminate the
source that transmits a large amount of invalid data. Then, check whether
the alarm is cleared. If the alarm persists, go to the next step.
NOTE
After confirming that the PW bandwidth exhaustion is the cause, restore the value
of Detection Packet Period and keep the values consistent between both ends.
The alarm Go to the next step.
persists
Step 6 On the U2000, check whether the COMMUN_FAIL alarm is reported on the opposite NE.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 483
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The COMMUN_FAIL alarm is The opposite NE is being reset. After the
reported COMMUN_FAIL alarm is cleared, check whether the
MPLS_PW_LOCV alarm is cleared. If the alarm
persists, go to the next step.
The COMMUN_FAIL alarm is Go to the next step.
not reported
Step 7 On the U2000, check whether any NE on the link reports hardware-related alarms (alarms on
optical modules or boards), such as HARD_BAD and LSR_NO_FITED.
If... Then...
The HARD_BAD or Handle the alarms, and check whether the
LSR_NO_FITED alarm is reported MPLS_PW_LOCV alarm is cleared. If the alarm
persists, go to the next step.
The HARD_BAD or Go to the next step.
LSR_NO_FITED alarm is not
reported
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.259 MPLS_PW_MISMATCH
Description
The MPLS_PW_MISMATCH alarm indicates incorrect PW TTSIs. This alarm is reported if
no CV/FFD packet with a correct TTSI (including the PW ID and NE ID) is received in three
consecutive CV/FFD periods.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 484
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 LSRID/MEGID: Indicates the source of the packet.
Impact on the System
Services may be interrupted or packets from other PWs are received.
Possible Causes
Possible causes of the MPLS_PW_MISMATCH alarm are as follows:
l The PW settings are incorrect. The LSR ID or PW ID at one end of the PW are different
from that at the other end.
l The physical link is connected incorrectly.
Procedure
Step 1 On the U2000, check whether the LSR IDs are the same at the source and sink ends of the
PW.
If... Then...
The LAR IDs are Go to the next step.
the same
The LAR IDs are Reconfigure the LSR IDs to be the same at the source and sink ends of
different the PW, and check whether the alarm is cleared. If the alarm persists,
go to the next step.
NOTE
If the source NE is an ingress node, Opposite LSR ID is the LSR ID of the
sink NE. If the sink NE is an egress node, Opposite LSR ID is the LSR ID of
the source NE.
Step 2 On the U2000, check whether the PW IDs are the same at the source and sink ends of the PW.
If... Then...
The PW IDs are the same Go to the next step.
The PW IDs are different Reconfigure the PW IDs to be the same at the source and sink
ends of the PW, and check whether the alarm is cleared. If the
alarm persists, go to the next step.
Step 3 Check whether an optical fiber or a cable is incorrectly connected between both ends.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 485
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
An optical fiber or cable is Rectify the connection or service configurations based
incorrectly connected on the actual networking scenario. Check whether the
alarm is cleared. If the alarm persists, go to the next
step.
No optical fiber or cable is Go to the next step.
incorrectly connected
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.260 MPLS_PW_MISMERGE
Description
The MPLS_PW_MISMERGE alarm indicates that the TTSIs of PWs are incorrectly merged.
This alarm is reported if CV/FFD packets with correct TTSIs (including the PW ID and node
ID) and CV/FFD packets with incorrect TTSIs are received in three consecutive CV/FFD
periods.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 LSRID/MEGID: Indicates the source of the packet.
Impact on the System
The local PW receives packets from other PWs and services may be interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 486
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the MPLS_PW_MISMERGE alarm are as follows:
l Different PWs are configured with the same PW label and are sent to the same sink.
l The physical link is connected incorrectly.
Procedure
Step 1 On the U2000, check whether two PWs are configured with the same PW label.
If... Then...
Several PWs are configured with Delete redundant PWs or configure a unique label
the same PW label for each PW, and check whether the alarm is cleared.
If the alarm persists, go to the next step.
Each PW is configured with a Go to the next step.
unique PW label
Step 2 Check whether an optical fiber or a cable is incorrectly connected between both ends.
If... Then...
An optical fiber or cable is Rectify the connection or service configurations based
incorrectly connected on the actual networking scenario. Check whether the
alarm is cleared. If the alarm persists, go to the next
step.
No optical fiber or cable is Go to the next step.
incorrectly connected
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.261 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL is an alarm indicating that the OAM protocol negotiation fails.
This alarm is reported when the OAM protocol negotiation fails on NEs at both ends of a PW.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 487
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of an OAM protocol negotiation failure.
l 0x01: indicates that the OAM protocol negotiation is in the initial status,
that is, the OAM protocol negotiation on NEs at both ends of the PW fails.
Impact on the System
When this alarm occurs, the PW APS protection switching is triggered, and services are
switched to the protection PW.
Possible Causes
The possible causes of the MPLS_PW_OAMFAIL alarm are as follows:
l Cause 1: The OAM function is only enabled on the NE at one end of the PW.
The alarm is reported only by the NE on which the OAM function is enabled. As shown
in Figure 4-11, only the local NE reports the MPLS_PW_OAMFAIL alarm.
Figure 4-11 MPLS_PW_OAMFAIL alarm detection (1)
MPLS PW OAM is MPLS PW OAM is
enabled on the local disabled on the remote
NE. NE.
The local NE reports the
MPLS_PW_OAMFAIL alarm. Service flow
l Cause 2: The PW has been interrupted when enabling the OAM function.
As shown in Figure 4-12, when the PW is interrupted in the forward direction or reverse
direction, the peer or local NE reports the MPLS_PW_OAMFAIL alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 488
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-12 MPLS_PW_OAMFAIL alarm detection (2)
Local: Remote:
MPLS PW OAM is enabled. MPLS PW OAM is enabled.
OAM Detection Mechanism is set OAM Detection Mechanism is set
to auto-sensing. to auto-sensing.
Forward PW
Reverse PW
The remote NE reports the
MPLS_PW_OAMFAIL alarm.
Service flow
Procedure
Step 1 Cause 1: The OAM function is only enabled on the NE at one end of the PW.
1. On the NMS, query this alarm and check whether the OAM function is enabled on NEs
at both ends of the PW. If the OAM function is enabled only on one NE, set OAM
Status to Enabled for the other NE.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The PW has been interrupted when enabling the OAM function.
1. On the NMS, check whether tunnel-related alarms are reported on the two ends of the
PW. For example, 4.2.277 MPLS_TUNNEL_OAMFAIL. If any of these alarms exist,
clear them before you proceed.
2. Check whether service-related alarms are reported by NEs at both ends of the PW. For
example, 4.2.258 MPLS_PW_LOCV. If any service-related alarms are reported, clear
them immediately.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.262 MPLS_PW_RDI
Description
The MPLS_PW_RDI is an alarm indicating that a defect is detected on a remote PW. The
local MEP NE sends an RDI packet to the remote MEP NE when it detects a PW defect. The
remote MEP NE reports this alarm upon receiving the RDI packet.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 489
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, the local MEP NE cannot receive packets.
Possible Causes
The possible cause of the MPLS_PW_RDI alarm is as follows:
Cause: The local MEP NE detects that the PW is faulty.
Figure 4-13 shows the process of MPLS_PW_RDI alarm detection.
Figure 4-13 MPLS_PW_RDI alarm detection
1. The remote MEP NE 2. The local MEP NE
sends OAM packets. waits to receive the
OAM packets.
OAM packets PSN
RDI packets
MEP MEP
3. The PW is faulty. The
4. The remote NE receives
local MEP NE returns RDI
RDI packets and reports the
packets after failing to
MPLS_PW_RDI alarm.
receive OAM packets.
Procedure
Step 1 Check whether the faulty NE reports port-, optical module- or board-related alarms, such as
4.2.131 ETH_LOS, 4.2.130 ETH_LINK_DOWN, 4.2.239 LSR_NO_FITED, and 4.2.157
HARD_BAD. If any of these alarms exist, clear them before you proceed.
Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty, for
example, whether the optical fiber or cable is damaged or pressed. If yes, replace the faulty
optical fiber or cable.
Step 3 Check whether the faulty NE reports service alarms, such as 4.2.258 MPLS_PW_LOCV. If
yes, clear them immediately. Then, check whether the MPLS_PW_RDI alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 490
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.263 MPLS_PW_SD
Description
The MPLS_PW_SD alarm indicates that the signal on a PW degrades. This alarm is reported
when the loss ratio of CC packets is higher than the SD threshold but is lower than the SF
threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The quality of service degrades and a small number of packets are lost.
Possible Causes
Possible causes of the MPLS_PW_SD alarm are as follows:
l An excessive number of bit errors occur.
l The PW bandwidth is fully occupied.
l The surface of an optical fiber or optical module is dirty.
Procedure
Step 1 On the U2000, query the performance statistics on Ethernet ports to check whether bit errors
or FCS error frames are generated.
If... Then...
Bit errors or FCS error frames are Handle the performance events, and check whether
generated the alarm is cleared. If the alarm persists, go to the
next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 491
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Bit errors or FCS error frames are Go to the next step.
not generated
Step 2 Check whether the PW bandwidth PW is exhausted.
If... Then...
The bandwidth is Increase the PW bandwidth or eliminate any source that
exhausted transmits a large amount of invalid data, and check whether
the alarm is cleared. If the alarm persists, go to the next step.
The bandwidth is not Go to the next step.
exhausted
Step 3 Check whether the physical link is connected incorrectly, for example, whether any optical
cables are broken, any optical ports are dirty or damaged, or the bend radius of the fiber patch
cord is less than 7.5 mm.
If... Then...
The physical link is connected Reconnect the optical fibers, clean optical ports, or reroute
incorrectly the fiber patch cord, and check whether the alarm is
cleared. If the alarm persists, go to the next step.
The physical link is connected Go to the next step.
correctly
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.264 MPLS_PW_SF
Description
The MPLS_PW_SF alarm indicates that the signals on a PW degrade severely. This alarm is
reported when the loss ratio of CC packets exceeds the SF threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 492
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
The quality of service degrades severely and a large number of packets are lost.
Possible Causes
Possible causes of the MPLS_PW_SF alarm are as follows:
l An excessive number of bit errors occur.
l The PW bandwidth is fully occupied.
l The surface of an optical fiber or optical module is dirty.
Procedure
Step 1 On the U2000, query the performance statistics on Ethernet ports to check whether bit errors
or FCS error frames are generated.
If... Then...
Bit errors or FCS error frames are Handle the performance events, and check whether
generated the alarm is cleared. If the alarm persists, go to the
next step.
Bit errors or FCS error frames are Go to the next step.
not generated
Step 2 Check whether the PW bandwidth PW is exhausted.
If... Then...
The bandwidth is Increase the PW bandwidth or eliminate any source that
exhausted transmits a large amount of invalid data, and check whether
the alarm is cleared. If the alarm persists, go to the next step.
The bandwidth is not Go to the next step.
exhausted
Step 3 Check whether the physical link is connected incorrectly, for example, whether any optical
cables are broken, any optical ports are dirty or damaged, or the bend radius of the fiber patch
cord is less than 7.5 mm.
If... Then...
The physical link is connected Reconnect the optical fibers, clean optical ports, or reroute
incorrectly the fiber patch cord, and check whether the alarm is
cleared. If the alarm persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 493
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The physical link is connected Go to the next step.
correctly
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.265 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG is an alarm indicating an error in the CCM information of the
PW OAM packet. The sink NE reports the MPLS_PW_UNEXPMEG alarm upon receiving
the OAM CCM packet with an unexpected MEG ID.
1. The source NE adds a PW outgoing label to the OAM packet containing CCM
information (including MEG level, MEG ID, and MEP ID) and transmits them to the
sink NE.
2. The sink NE receives the OAM packet based on its incoming label and compares the
CCM information in the packet with that configured on itself. If MEG levels are
consistent but MEG IDs are inconsistent, the sink NE reports the
MPLS_PW_UNEXPMEG alarm.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 (OptiX OSN 500/550)LSRID/MEGID: Indicates the source of the packet.
NOTE
OptiX OSN 580 has no alarm parameters.
Impact on the System
When this alarm occurs, the sink NE receives OAM CCM packets of other PW services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 494
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible causes of the MPLS_PW_UNEXPMEG alarm are as follows:
l Cause 1: The PW is configured incorrectly. Different PWs use the same labels.
As shown in Figure 4-14, NE1 is the source NE, and NE2 is the sink NE. The PW
incoming label for NE2 is 1, indicating that it is supposed to receive packets from PW1
only.
On the live network, NE1 configures a PW outgoing label whose value is 1 to both PW1
and PW2. Therefore, after receiving CCM packets from PW2, NE2 detects different
MEG IDs and reports the MPLS_PW_UNEXPMEG alarm.
Figure 4-14 MPLS_PW_UNEXPMEG alarm detection (1)
PW1：PW outlabel = 1
PW inlabel = 1
PW2：PW outlabel = 1
PW1
NE1 NE2
PW2
NE2 reports the
MPLS_PW_UNEXPMEG alarm.
Service flow
l Cause 2: MEG IDs configured on NEs at both ends of the PW are different.
As shown in Figure 4-15, on the link from NE1 to NE2, the MEG ID is 1.
In practice, the MEG ID for NE1 is 1 and MEG ID for NE2 is 2. Then, NE2 receives
CCM packets containing different MEG ID and reports the MPLS_PW_UNEXPMEG
alarm.
Figure 4-15 MPLS_PW_UNEXPMEG alarm detection (2)
MEG ID = 1 MEG ID = 2
NE1 NE2
NE2 reports the
MPLS_PW_UNEXPMEG alarm.
Service flow
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 495
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 3: The physical link is connected incorrectly. Multiple PWs with the same label
are connected to the same sink NE.
As shown in Figure 4-16, a fiber between NE1 and NE2 is correctly connected. On the
link from NE1 to NE2, the PW outgoing label is 1, and the MEG ID is 1. On the link
from NE3 to NE4, the PW outgoing label is 1, and the MEG ID is 2.
In practice, if a fiber is incorrectly connected from NE3 to NE2, the outgoing label of
NE1 is the same as that on NE3, and the incoming label on NE2 is the same as that on
NE4. As a result, NE2 reports the MPLS_PW_UNEXPMEG alarm.
Figure 4-16 MPLS_PW_UNEXPMEG alarm detection (3)
PW outlabel = 1 PW inlabel = 1
MEG ID = 1 MEG ID = 1
NE1 NE2
NE2 reports the
MPLS_PW_UNEXPMEG alarm.
NE3 NE4
PW outlabel = 1 PW outlabel = 1
MEG ID = 2 MEG ID = 2
Service flow
Procedure
Step 1 Cause 1: The PW is configured incorrectly. Different PWs use the same labels.
1. As shown in Figure 4-14, check whether the PW label is configured correctly. If
multiple PWs use the same labels, reconfigure the PW label.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: MEG IDs configured on NEs at both ends of the PW are different.
1. As shown in Figure 4-15, check whether the PW configurations on NEs at both ends of
the PW are consistent. PW IDs on NEs at both ends of a PW must be set to the same
value.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The physical link is connected incorrectly. Multiple PWs with the same label are
connected to the same sink NE.
1. As shown in Figure 4-16, check whether the fiber or cable is correctly connected
between ports at both ends. If the fiber or cable is connected incorrectly, connect it
correctly.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 496
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers for a
solution.
----End
Related Information
None.
4.2.266 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP is an alarm indicating that the PW does not receive the
expected PEP ID. The sink NE reports this alarm upon receiving an OAM packet with an
unexpected MEP ID.
1. The source NE adds a PW outgoing label to the OAM packet that contains the CCM
information and sends the packet to the sink NE. CCM information includes the MEG
level, MEG ID, and MEP ID of the source NE.
2. The sink NE receives the OAM packet based on its incoming label and compares the
CCM information in the packet with that configured on itself. If MEG levels and MEG
IDs are consistent but MEP IDs are inconsistent, the sink NE reports the
MPLS_PW_UNEXPMEP alarm.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 (OptiX OSN 500/550)LSRID/MEGID: Indicates the source of the packet.
NOTE
OptiX OSN 580 has no alarm parameters.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
The possible cause of the MPLS_PW_UNEXPMEP alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 497
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Cause: MEP IDs are inconsistent on NEs at both ends of a PW.
As shown in Figure 4-17, NE2 is the sink end for NE1 and the MEP ID is 1 for both NEs in
the network plan.
However, the MEP ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore, NE2
reports the MPLS_PW_UNEXPMEP alarm upon receiving the CCM packet that contains
incorrect MEP ID from NE1.
Figure 4-17 MPLS_PW_UNEXPMEP alarm detection
MEP ID = 1 MEP ID = 2
PW
NE1 PSN NE2
NE2 reports the MPLS_PW_UNEXPMEP alarm.
Service flow
Procedure
Step 1 As shown in Figure 4-17, check whether PW configurations are consistent on the source and
sink NEs. MEP IDs must be set to the same value for NEs at both ends of a PW service.
Step 2 Check whether service-related alarms are reported by NEs at both ends of the PW. For
example, 4.2.258 MPLS_PW_LOCV. If any of these alarms are reported, clear them before
you proceed.
Step 3 On the NMS, check whether tunnel-related alarms are reported by NEs at both ends of the
PW. For example, 4.2.277 MPLS_TUNNEL_OAMFAIL. If any of these alarms are
reported, clear them before you proceed.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for a solution.
----End
Related Information
None.
4.2.267 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER is an alarm indicating that the PW does not receive CCM
packets in the expected period. The MEP NE reports this alarm upon receiving an OAM
packet with correct MEG level, MEG ID, and MEP ID in an unexpected period.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 498
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. The source MEP NE sends the connectivity detection packet that contains the CCM
information to the sink MEP NE. CCM information includes the MEG level, MEG ID,
and MEP ID of the source NE.
2. The sink MEP NE compares the received CCM information with that configured on the
NE. If the received information is in an unexpected period, the NE will report this alarm
though MEG levels, MEG IDs, and MEP IDs are correct.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, services may be interrupted.
Possible Causes
The possible cause of the MPLS_PW_UNEXPPER alarm is as follows:
Cause: CCM packet periods are inconsistent on the source and sink NEs at both ends of the
PW.
Procedure
Step 1 Check the periods of OAM packets on source and sink NEs at both ends of the PW.
Step 2 If periods of OAM packets are inconsistent, modify them.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.268 MPLS_PW_UNKNOWN
Description
The MPLS_PW_UNKNOWN alarm indicates that certain unknown defects exist on a PW.
This alarm is reported when the types or the cycles of the CC packets received within a
certain period (three times of the cycle) are not the expected types or cycles.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 499
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The PW OAM function is affected.
Possible Causes
Possible causes of the MPLS_PW_UNKNOWN alarm are as follows:
l The OAM attributes set at both ends are inconsistent.
l The NE receives packets from unknown sources.
Procedure
Step 1 On the U2000, check whether the MPLS_PW_LOCV alarm is reported after the
MPLS_PW_UNKNOWN alarm is transiently reported.
If... Then...
The MPLS_PW_LOCV alarm is Check whether PW OAM attributes are switched
reported after the between the NEs at the local and opposite ends.
MPLS_PW_UNKNOWN alarm is Reconfigure the PW OAM attributes at both ends to
transiently reported make them consistent, and check whether the
MPLS_PW_UNKNOWN alarm is cleared. If the
MPLS_PW_UNKNOWN alarm persists, go to the
next step.
NOTE
PW attributes include the type and cycle of CC packets.
The MPLS_PW_LOCV alarm is not Go to the next step.
reported after the
MPLS_PW_UNKNOWN alarm is
transiently reported
Step 2 Check whether any services are configured between the local NE and another unknown
source or whether an incorrect fiber connection results in connection between the local NE
and another unknown source.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 500
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Services are configured between the Modify the service configuration, and then check
local NE and another unknown whether the alarm is cleared. If the alarm persists,
source go to the next step.
An incorrect fiber connection results Reconnect the fiber, and check whether the alarm is
in connection between the local NE cleared. If the alarm persists, go to the next step.
and another unknown source
Neither of the above issues occurs Go to the next step.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.269 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS is an alarm indicating a defect is detected on a tunnel. The MIP
NE sends an AIS packet to the downstream NE when it detects a fault on the Ethernet port.
The sink MEP NE reports this alarm upon receiving the AIS packet.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
The possible cause of the MPLS_TUNNEL_AIS alarm is as follows:
Cause: The MIP NE detects a fault on the Ethernet port.
Figure 4-18 shows the process of MPLS_TUNNEL_AIS alarm detection.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 501
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-18 MPLS_TUNNEL_AIS alarm detection
4. Generate the
MPLS_TUNNEL_LOCV alarm after
2. Enable AIS insertion. failing to receive OAM packets.
3. The MIP NE inserts AIS 5. Receive AIS packets, report the
1. The MEP NE sends OAM packets after detecting a fault. MPLS_TUNNEL_AIS alarm and
packets.
suppress the MPLS_TUNNEL_LOCV
alarm.
Tunnel Tunnel
MEP MIP MEP
OAM packets
AIS packets
Procedure
Step 1 Check whether the faulty NE reports port-, optical module- or board-related alarms, such as
4.2.131 ETH_LOS, 4.2.130 ETH_LINK_DOWN, 4.2.239 LSR_NO_FITED, and 4.2.157
HARD_BAD. If any of these alarms are reported, clear them immediately. Then, check
whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty, for
example, whether the optical fiber or cable is damaged or pressed. If yes, replace the faulty
optical fiber or cable.
Step 3 Check whether the faulty NE reports service alarms, such as 4.2.274
MPLS_TUNNEL_LOCV. If any of these alarms are reported, clear them immediately. Then,
check whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.270 MPLS_TUNNEL_BDI
Description
The MPLS_TUNNEL_BDI alarm indicates defects in the backward direction of a tunnel. This
alarm is reported when a BDI packet is received at the receive end, indicating that the forward
tunnel is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 502
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
The services on the transmit channel at the local end are affected.
Possible Causes
The possible cause of the MPLS_TUNNEL_BDI alarm is as follows:
l The opposite NE detects that the tunnel is faulty.
Procedure
Step 1 On the U2000, check whether there are hardware-related alarms at the local end, such as
HARD_BAD and LSR_NO_FITED. If yes, clear these alarms. Then check whether the
MPLS_TUNNEL_BDI alarm is cleared.
Step 2 If the alarm persists, check whether an optical fiber or a cable between the local NE and the
opposite NE is damaged. If yes, replace the faulty optical fiber or cable.
----End
Related Information
None.
4.2.271 MPLS_TUNNEL_EXCESS
Description
The MPLS_TUNNEL_EXCESS alarm indicates that excessive trail termination source
identifiers (TTSIs) are received. This alarm is reported if five or more correct CV/FFD
packets are received in three consecutive CV/FFD periods.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 503
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
Services may be interrupted if excessive redundant packets are received.
Possible Causes
Possible causes of the MPLS_TUNNEL_EXCESS alarm are as follows:
l The physical link is incorrectly connected.
l Multiple tunnels are configured with the same value of Next Hop Address.
Procedure
Step 1 Check whether an optical fiber or a cable is incorrectly connected between both ends. If yes,
rectify the fiber/cable connection. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, go to Step 3.
Step 3 On the U2000, check whether multiple tunnels are configured with the same value of Next
Hop Address.
Step 4 If multiple tunnels are configured with the same value of Next Hop Address, delete extra
tunnels or change the Next Hop Address parameter to different values.
1. To delete the extra tunnels, select the extra tunnels and click Delete.
2. To change the Next Hop Address parameter, select the required tunnels and click
Modify.
----End
Related Information
None.
4.2.272 MPLS_TUNNEL_FDI
Description
The MPLS_TUNNEL_FDI alarm indicates defects in the forward direction of a tunnel. This
alarm is reported when a forward defect indication (FDI) packet is received, indicating that
the tunnel at the physical layer of the upstream NE is faulty.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 504
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
Services may be interrupted.
Possible Causes
The possible cause of the MPLS_TUNNEL_FDI alarm is as follows:
l The upstream NE detects that the tunnel at the physical layer is faulty.
Procedure
Step 1 On the U2000, check whether there are hardware-related alarms at the local end, such as
HARD_BAD and LSR_NO_FITED. If yes, clear these alarms. Then check whether the
MPLS_TUNNEL_FDI alarm is cleared.
Step 2 If the MPLS_TUNNEL_FDI alarm persists, check whether an optical fiber or a cable between
the local NE and the opposite NE is damaged. If yes, replace the faulty optical fiber or cable.
----End
Related Information
None.
4.2.273 MPLS_TUNNEL_LOCK
Description
The MPLS_TUNNEL_LOCK alarm indicates that a command to lock the tunnel layer is
issued on an MEP.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
None
Possible Causes
The possible cause of this alarm is as follows:
Cause: A command to lock the tunnel layer is issued on an MEP.
As shown in Figure 4-19, a command to lock the tunnel layer is issued on MEP3 and MEP3
reports an MPLS_TUNNEL_LOCK alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 505
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-19 MPLS_TUNNEL_LOCK generation process
1. Issues a command to lock the
tunnel layer.
2. Reports an
MPLS_TUNNEL_LOCK alarm.
MEP1 MIP2 MEP3
LSR A LSR B LSR C
Tunnel 1 Tunnel 2 Tunnel
layer
PW 1 PW
layer
Procedure
Step 1 Cause: A command to lock the tunnel layer is issued on an MEP.
1. Unlock the tunnel layer. For details, see Configuring LCK of MPLS-TP Tunnel OAM.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.274 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV alarm indicates loss of tunnel connectivity. This alarm is
reported if the expected CV/FFD packet is not received in three consecutive periods. For
example, this alarm is reported when the Ethernet port receives the continuity check packet
with the correct TTSI within three consecutive periods, but the packet type and period are
different from the expected values.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 506
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The services that the faulty tunnel carries may be interrupted.
Possible Causes
Possible causes of the MPLS_TUNNEL_LOCV alarm are as follows:
l The MPLS OAM settings differ between both ends. For example, the type of packets to
be checked or the check period differs between both ends.
l The network is severely congested.
l A board fails.
l The physical link is faulty.
Procedure
Step 1 On the U2000, check whether the MPLS OAM settings are the same at both ends.
Step 2 If they are different, modify them to be the same based on the actual situation. Then, check
whether the alarm is cleared.
Step 3 If the alarm persists, go to Step 4.
Step 4 Based on the actual situation, increase the value of the Detection Packet Period parameter
appropriately.
Step 5 If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is exhausted.
If yes, expand the bandwidth allocated to the tunnel or eliminate the source that transmits a
large amount of invalid data. Check whether the alarm is cleared.
Step 6 If the alarm persists, go to Step 7.
Step 7 On the U2000, check whether the COMMUN_FAIL alarm is reported on the opposite NE. If
yes, you can infer that the opposite NE is being reset. After the COMMUN_FAIL alarm is
cleared, check whether the MPLS_TUNNEL_LOCV alarm is cleared.
Step 8 On the U2000, check whether the local NE and the opposite NE report alarms that are related
to the hardware of optical modules or boards, such as HARD_BAD and LSR_NO_FITED. If
yes, clear these alarms and check whether the MPLS_TUNNEL_LOCV alarm is cleared.
Step 9 If the alarm persists, go to Step 10.
Step 10 Check whether an optical fiber or a cable between both ends is faulty. If yes, replace the faulty
optical fiber or cable.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 507
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.275 MPLS_TUNNEL_MISMATCH
Description
The MPLS_TUNNEL_MISMATCH alarm indicates trail termination source identifiers
(TTSIs) mismatch. This alarm is reported if no CV/FFD packet with a correct TTSI is
received in three consecutive CV/FFD periods.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 LSRID/MEGID: Indicates the source of the packet.
Impact on the System
Services may be interrupted or packets from other tunnels may be received.
Possible Causes
Possible causes of the MPLS_TUNNEL_MISMATCH alarm are as follows:
l Cause 1: The physical link is incorrectly connected.
l Cause 2: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ
at both ends of the tunnel.
Procedure
Step 1 Check whether an optical fiber or a cable is incorrectly connected between both ends. If yes,
rectify the fiber/cable connection.
Step 2 Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 On the U2000, check whether the LSR IDs or tunnel IDs are consistent at both ends of a
tunnel.
1. If the source NE is an ingress node, the value of Sink Node is the LSR ID of the sink
node. If the sink NE is an egress node, the value of Source Node is the LSR ID of the
source NE. For details about how to query the LSR ID of the source/sink NE, see the
Configuration Guide.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 508
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. The tunnel IDs configured on the source NE and sink NE of one tunnel should be the
same. For details about how to query tunnel IDs, see the Configuration Guide.
Step 4 If the tunnel IDs on both ends of a tunnel mismatch, change the tunnel IDs and ensure that the
tunnel IDs on both ends of a tunnel match.
----End
Related Information
None.
4.2.276 MPLS_TUNNEL_MISMERGE
Description
The MPLS_TUNNEL_MISMERGE alarm indicates that trail termination source identifiers
(TTSIs) are incorrectly merged. This alarm is reported if CV/FFD packets with correct TTSIs
and CV/FFD packets with incorrect TTSIs are received in three consecutive CV/FFD periods.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 LSRID/MEGID: Indicates the source of the packet.
Impact on the System
Packets from other tunnels are received.
Possible Causes
Possible causes of the MPLS_TUNNEL_MISMATCH alarm are as follows:
l Cause 1: The physical link is incorrectly connected.
l Cause 2: The tunnel settings are incorrect. For example, several tunnels are configured
with the same label.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 509
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether an optical fiber or a cable is incorrectly connected between both ends. If yes,
connect the optical fiber or cable correctly.
Step 2 Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 On the U2000, check whether several tunnels are configured with the same label. For details,
see the Configuration Guide.
Step 4 If yes, delete the redundant tunnels or modify the tunnel labels.
1. To delete a redundant tunnel, right-click the tunnel and choose Delete from the shortcut
menu.
2. To modify the label of a duplicate tunnel, delete the tunnel and create another tunnel.
----End
Related Information
On the NE, the label of each MPLS tunnel is unique.
4.2.277 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL alarm indicates that the source and sink nodes of a tunnel
fail to negotiate on the OAM protocol.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
MPLS APS switching is triggered and services are switched to the protection tunnel.
Possible Causes
Possible causes of the MPLS_TUNNEL_OAMFAIL alarm are as follows:
l The OAM function is enabled only on either the source or the sink node of the tunnel.
l The tunnel has been interrupted before the OAM function is enabled.
Procedure
Step 1 On the U2000, check whether the OAM function is enabled on NEs at both ends of the tunnel.
Enable the OAM function if it is not enabled at either end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 510
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 If the alarm persists, check whether the sink node of the alarmed tunnel reports the
HARD_BAD, ETH_LOS, or R_LOS alarm.
If... Then...
Exclude the alarms 4.2.157 HARD_BAD, 4.2.131 ETH_LOS,
the alarm is reported
and 4.2.420 R_LOS.
the alarm is not reported Go to the next step.
Step 3 Clear the alarm. After the OAM protocol negotiation is successful, the
MPLS_TUNNEL_OAMFAIL alarm clears.
----End
Related Information
None.
4.2.278 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI is an alarm indicating a defect is detected on a remote tunnel. The
local MEP NE sends an RDI packet to the remote MEP NE when it detects a tunnel defect.
The remote MEP NE reports this alarm upon receiving the RDI packet.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, the local MEP NE cannot receive packets.
Possible Causes
The possible cause of the MPLS_TUNNEL_RDI alarm is as follows:
Cause: The local MEP NE detects that the tunnel is faulty.
Figure 4-20 shows the process of MPLS_TUNNEL_RDI alarm detection.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 511
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-20 MPLS_TUNNEL_RDI alarm detection
1. The remote MEP NE 2. The local MEP NE waits to
sends OAM packets. receive OAM packets.
PSN
Forward tunnel
Reverse tunnel
4. The remote NE reports the 3. The tunnel is faulty. The
MPLS_TUNNEL_RDI alarm local NE reports the
after receiving RDI packets. MPLS_TUNNEL_LOCV
alarms and returns RDI
packets after failing to receive
OAM packets.
OAM packets
RDI packets
Procedure
Step 1 Check whether the faulty NE reports port-, optical module- or board-related alarms, such as
4.2.131 ETH_LOS, 4.2.130 ETH_LINK_DOWN, 4.2.239 LSR_NO_FITED, and 4.2.157
HARD_BAD. If any of these alarms are reported, clear them immediately. Then, check
whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty, for
example, whether the optical fiber or cable is damaged or pressed. If yes, replace the faulty
optical fiber or cable.
Step 3 Check whether the faulty NE reports service alarms, such as 4.2.274
MPLS_TUNNEL_LOCV. If any of these alarms are reported, clear them immediately. Then,
check whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.279 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD alarm indicates that the tunnel signal degrades. This alarm is
reported when the CC packet loss ratio is higher than the SD threshold but is lower than the
SF threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 512
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The quality of service degrades and a small number of packets are lost.
Possible Causes
Possible causes of the MPLS_TUNNEL_SD alarm are as follows:
l An excessive number of bit errors occur.
l The bandwidth of the tunnel is exhausted.
l Another service carrier layer is faulty.
Procedure
Step 1 On the U2000, check whether an alarm indicating excessive bit errors is reported. If yes, clear
the alarm. Check whether the MPLS_TUNNEL_SD alarm is cleared.
Step 2 If the MPLS_TUNNEL_SD alarm persists, go to Step 3.
Step 3 On the U2000, check whether the allocated bandwidth is exhausted. If yes, expand the
bandwidth allocated to the tunnel or eliminate the source that transmits a large amount of
invalid data. Check whether the MPLS_TUNNEL_SD alarm is cleared.
Step 4 If the MPLS_TUNNEL_SD alarm persists, go to Step 5.
Step 5 On the U2000, check whether another service carrier layer, such as the Ethernet layer, is
faulty. If yes, rectify running exceptions of the MPLS OAM protocol or setting inconsistency.
----End
Related Information
None.
4.2.280 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF alarm indicates that the tunnel signal degrades severely. This alarm
is reported if the CC packet loss ratio is higher than the SF threshold but CC packets are
received in three consecutive periods.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 513
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The quality of service degrades severely and a large number of packets are lost.
Possible Causes
Possible causes of the MPLS_TUNNEL_SF alarm are as follows:
l An excessive number of bit errors occur.
l The bandwidth of the tunnel is exhausted.
l Another service carrier layer is faulty.
Procedure
Step 1 On the U2000, check whether an alarm indicating excessive bit errors is reported. If yes, clear
the alarm. Check whether the MPLS_TUNNEL_SD alarm is cleared.
Step 2 If the MPLS_TUNNEL_SD alarm persists, go to Step 3.
Step 3 On the U2000, check whether the allocated bandwidth is exhausted. If yes, expand the
bandwidth allocated to the tunnel or eliminate the source that transmits a large amount of
invalid data. Check whether the MPLS_TUNNEL_SD alarm is cleared.
Step 4 If the MPLS_TUNNEL_SD alarm persists, go to Step 5.
Step 5 On the U2000, check whether another service carrier layer, such as the Ethernet layer, is
faulty. If yes, rectify running exceptions of the MPLS OAM protocol or setting inconsistency.
----End
Related Information
None.
4.2.281 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG is an alarm indicating an error of the tunnel OAM CCM
information. The sink NE reports this alarm upon receiving an OAM packet with an
unexpected MEG ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 514
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. The ingress NE adds a tunnel outgoing label to the OAM packet that contains the CCM
information and sends the packet to the egress NE. CCM information includes the MEG
level, MEG ID, and MEP ID of the ingress NE.
2. The egress NE receives the OAM packet based on its incoming label and compares the
CCM information in the packet with that configured on itself. If MEG levels are
consistent but MEG IDs are inconsistent, the egress NE reports the
MPLS_TUNNEL_UNEXPMEG alarm.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 (OptiX OSN 500/550)LSRID/MEGID: Indicates the source of the packet.
NOTE
OptiX OSN 580 has no alarm parameters.
Impact on the System
When this alarm occurs, the egress NE receives OAM packets (containing CCM information)
of other tunnels.
Possible Causes
The possible causes of the MPLS_TUNNEL_UNEXPMEG alarm are as follows:
l Cause 1: There are multiple tunnels with the same label between the source and sink
NEs.
An example is provided as follows: As shown in Figure 4-21, there are two links in the
network plan that are connected to NE2: tunnel 1 between NE1 and NE2, and tunnel 2
between NE3 and NE2. The label of tunnel 1 is 1 and tunnel 2 is 2.
However, in actual configuration, outgoing labels of both tunnel 1 and tunnel 2 are set to
1. NE2 receives an OAM packet (containing CCM information) that contains incorrect
MEG ID from NE3. As a result, NE2 reports the MPLS_TUNNEL_UNEXPMEG alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 515
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-21 MPLS_TUNNEL_UNEXPMEG alarm detection (1)
Tunnel outlabel = 1 Tunnel inlabel = 1
NE1 Tunnel NE2
el
Tu n n
NE2 reports the
NE3 MPLS_TUNNEL_UNEXPMEG alarm.
Tunnel outlabel = 1 Service flow
l Cause 2: MEG IDs are inconsistent on NEs at both ends of a tunnel.
An example is provided as follows: As shown in Figure 4-22, NE2 is the source end for
NE1 and the MEG ID on both NEs is 1 in the network plan.
However, the MEG ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore,
NE2 reports the MPLS_PW_UNEXPMEP alarm upon receiving the OAM packet
(containing CCM information) with an incorrect MEG ID from NE1.
Figure 4-22 MPLS_TUNNEL_UNEXPMEG alarm detection (2)
Tunnel outlabel = 1 Tunnel inlabel = 1
MEG ID = 1 MEG ID = 2
NE1 Tunnel NE2
NE2 reports the MPLS_TUNNEL_UNEXPMEG
alarm.
Service flow
l Cause 3: Physical links are connected improperly. Multiple tunnels with the same label
are connected to the same sink NE.
As shown in Figure 4-23, a fiber between NE1 and NE2 is connected correctly. The
tunnel between NE1 and NE2 has an outgoing label (label 1) and the MEG ID is 1. The
tunnel between NE3 and NE4 has an outgoing label (label 1) and the MEG ID is 2.
In practice, if NE1 is mistakenly connected to NE4, the outgoing label of a tunnel on
NE1 is the same as that of the tunnel from NE3 to NE4, and the incoming label of a
tunnel on NE2 is the same as the outgoing label of a tunnel from NE3 to NE4. As a
result, NE2 reports the MPLS_TUNNEL_UNEXPMEG alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 516
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-23 MPLS_TUNNEL_UNEXPMEG alarm detection (3)
Tunnel outlabel = 1 Tunnel inlabel = 1
MEG ID = 1 MEG ID = 1
NE1 Tunnel NE2
el
Tunn
NE2 reports the
MPLS_TUNNEL_UNEXPMEG alarm
NE3 Tunnel NE4
Tunnel outlabel = 1 Tunnel inlabel = 1
MEG ID = 2 MEG ID = 2
Service flow
Procedure
Step 1 Cause 1: There are multiple tunnels with the same label between the source and sink NEs.
1. As shown in Figure 4-21, check whether there are multiple tunnels with the same label
on the source and sink NEs. If yes, reconfigure labels for tunnels.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: MEG IDs are inconsistent on NEs at both ends of a tunnel.
1. As shown in Figure 4-22, check whether tunnel configurations are consistent on the
source and sink NEs. MEG IDs must be set to the same value on NEs at both ends of a
tunnel service.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Physical links are connected improperly. Multiple tunnels with the same label are
connected to the same sink NE.
1. As shown in Figure 4-23, check whether the fiber or cable correctly connects ports on
both source and sink NEs. If the fiber or cable connection is incorrect, connect it
correctly.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for a solution.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 517
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.282 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP is an alarm indicating an error of the tunnel OAM CCM
information. The sink NE reports this alarm upon receiving an OAM packet (containing CCM
information) with an unexpected MEP ID.
1. The ingress NE adds a tunnel outgoing label to the OAM packet that contains the CCM
information and sends the packet to the egress NE. CCM information includes the MEG
level, MEG ID, and MEP ID of the ingress NE.
2. The egress NE receives the OAM packet based on its incoming label and compares the
CCM information in the packet with that configured on itself. If MEG levels and MEG
IDs are consistent but MEP IDs are inconsistent, the egress NE reports the
MPLS_TUNNEL_UNEXPMEP alarm.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 (OptiX OSN 500/550)LSRID/MEGID: Indicates the source of the packet.
NOTE
OptiX OSN 580 has no alarm parameters.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
The possible cause of the MPLS_TUNNEL_UNEXPMEP alarm is as follows:
Cause: MEP IDs are inconsistent on NEs at both ends of the tunnel.
As shown in Figure 4-24, NE2 is the source end for NE1 and the MEP ID on both NEs is 1.
However, the MEP ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore, NE2
reports the MPLS_TUNNEL_UNEXPMEP alarm upon receiving the OAM packet
(containing CCM information) with an incorrect MEP ID from NE1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 518
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-24 MPLS_TUNNEL_UNEXPMEP alarm detection
MEP ID = 1 MEP ID = 2
NE1 PSN Tunnel NE2
NE2 reports the MPLS_TUNNEL_UNEXPMEP
alarm.
Service flow
Procedure
Step 1 As shown in Figure 4-24, check whether tunnel configurations are consistent on the source
and sink NEs. MEP IDs must be set to the same value on NEs at both ends of a tunnel.
NOTE
The MEP IDs must be consistent on the source and sink NEs of a tunnel.
Step 2 If MEP IDs are inconsistent, change them to the same.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for a solution.
----End
Related Information
None.
4.2.283 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER is an alarm indicating that the tunnel does not receive
CCM packet in expected period. The MEP NE reports this alarm upon receiving an OAM
packet with correct MEG level, MEG ID, and MEP ID in an unexpected period.
1. The source MEP NE sends the connectivity detection packet that contains the CCM
information to the sink MEP NE. CCM information includes the MEG level, MEG ID,
and MEP ID of the source NE.
2. The sink MEP NE compares the received CCM information with that configured on the
NE. If the received information is in an unexpected period, the NE will report this alarm
though MEG levels, MEG IDs, and MEP IDs are correct.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 519
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
The possible cause of the MPLS_TUNNEL_UNEXPPER alarm is as follows:
Cause: CCM packet periods are inconsistent on the source and sink NEs at both ends of the
tunnel.
Procedure
Step 1 Check the periods of OAM packets on source and sink NEs at both ends of the tunnel.
Step 2 If periods of OAM packets are inconsistent, modify them.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.284 MPLS_TUNNEL_UNKNOWN
Description
The MPLS_TUNNEL_UNKNOWN alarm indicates that certain unknown defects exist on the
tunnel. This alarm is reported if the type or time period of continuity check (CC) packets that
are received within a certain time (three times the period) are different from the expected type
or period.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 520
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
The OAM function is affected.
Possible Causes
Possible causes of the MPLS_TUNNEL_UNKNOWN alarm are as follows:
l The OAM settings differ between both ends. For example, the type of packets to be
checked or the check period differs between both ends.
l The NE receives packets from an unknown source NE.
Procedure
Step 1 If the MPLS_TUNNEL_UNKNOWN alarm is transiently reported, check whether the OAM
settings (including the type of packets to be checked and the check period) at both ends are
modified.
Step 2 If the OAM settings are modified, the MPLS_TUNNEL_LOCV alarm may be reported after
the MPLS_TUNNEL_UNKNOWN alarm is transiently reported. After confirming that the
OAM settings are consistent between both ends, check whether the alarm is cleared. For
details, see the Configuration Guide.
Step 3 Check whether the alarm is cleared. If not, go to Step 4.
Step 4 Check whether any service is configured between the local NE and the unknown source NE or
whether the NE is connected to the unknown source NE due to an incorrect fiber connection.
Step 5 If yes, change the service configuration or fiber connection.
----End
Related Information
None.
4.2.285 MRING_APS_LOST_E
Description
MRING_APS_LOST_E is an alarm indicating APS packet loss in the east direction of an
MPLS-TP ring. This alarm occurs when APS packet loss occurs on a east port of an MPLS-
TP ring.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 521
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
APS protection on the MPLS-TP ring fails.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical component is faulty.
l Cause 2: The opposite device is faulty.
l Cause 3: The network is severely congested.
Procedure
Step 1 Cause 1: A physical component is faulty.
1. Check whether physical components are normal, such as fibers, boards, and optical
modules. If any physical component is faulty, replace the faulty component. For details,
see the Maintenance Guide.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The opposite device is faulty.
1. Check whether the opposite device is normal. For example, check whether a board fault
or a device reset occurs. If any fault occurs, rectify the fault.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The network is severely congested.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 522
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.286 MRING_APS_LOST_W
Description
MRING_APS_LOST_W is an alarm indicating APS packet loss in the west direction of an
MPLS-TP ring. This alarm occurs when APS packet loss occurs on a west port of an MPLS-
TP ring.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
APS protection on the MPLS-TP ring fails.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical component is faulty.
l Cause 2: The opposite device is faulty.
l Cause 3: The network is severely congested.
Procedure
Step 1 Cause 1: A physical component is faulty.
1. Check whether physical components are normal, such as fibers, boards, and optical
modules. If any physical component is faulty, replace the faulty component. For details,
see the Maintenance Guide.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The opposite device is faulty.
1. Check whether the opposite device is normal. For example, check whether a board fault
or a device reset occurs. If any fault occurs, rectify the fault.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 523
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The network is severely congested.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.287 MRING_APS_MISMATCH_E
Description
MRING_APS_MISMATCH_E is an alarm indicating incorrect configurations of east
neighbor nodes on an MPLS-TP ring. This alarm occurs when a east port on an MPLS-TP
ring receives an APS packet that carries a source ID different from the source ID set by the
state machine.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
APS on the MPLS-TP ring works incorrectly and therefore cannot protect services from being
interrupted in case of a fault.
Possible Causes
A possible cause of the alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 524
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause: A physical link connection is incorrect.
As shown in Figure 4-25, a correct link connection should be connecting NE1 and NE3
through NE2. When a west port on NE1 is connected to an east port on NE3, the west
port on NE1 receives an APS packet that carries a source ID different from that set by
the state machine, reporting an MRING_APS_MISMATCH_W alarm. Meanwhile, the
east port on NE3 receives an APS packet that carries a source ID different from that set
by the state machine, reporting an MRING_APS_MISMATCH_E alarm.
Figure 4-25 MRING_APS_MISMATCH_W/MRING_APS_MISMATCH_E detection
Reporting an MRING_APS_MISMATCH_E alarm
Node ID=3
East port West port
Node ID=4
West port NE3 East port
NE4
Node ID=2 NE2
East port Node ID=1 West port
NE1
West port East port
Reporting an MRING_APS_MISMATCH_W alarm
Procedure
Step 1 Cause: A physical link connection is incorrect.
1. As shown in Figure 4-25, check whether the link connection is correct. If no, make a
correct link connection.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.288 MRING_APS_MISMATCH_W
Description
MRING_APS_MISMATCH_W is an alarm indicating incorrect configurations of west
neighbor nodes on an MPLS-TP ring. This alarm occurs when a west port on an MPLS-TP
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 525
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
ring receives an APS packet that carries a source ID different from the source ID set by the
state machine.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
APS on the MPLS-TP ring works incorrectly and therefore cannot protect services from being
interrupted in case of a fault.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A physical link connection is incorrect.
As shown in Figure 4-26, a correct link connection should be connecting NE1 and NE3
through NE2. When a west port on NE1 is connected to an east port on NE3, the west
port on NE1 receives an APS packet that carries a source ID different from that set by
the state machine, reporting an MRING_APS_MISMATCH_W alarm. Meanwhile, the
east port on NE3 receives an APS packet that carries a source ID different from that set
by the state machine, reporting an MRING_APS_MISMATCH_E alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 526
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-26 MRING_APS_MISMATCH_W/MRING_APS_MISMATCH_E detection
Reporting an MRING_APS_MISMATCH_E alarm
Node ID=3
East port West port
Node ID=4
West port NE3 East port
NE4
Node ID=2 NE2
East port Node ID=1 West port
NE1
West port East port
Reporting an MRING_APS_MISMATCH_W alarm
Procedure
Step 1 Cause: A physical link connection is incorrect.
1. As shown in Figure 4-26, check whether the link connection is correct. If no, make a
correct link connection.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.289 MRING_FAR_SW_FAIL_E
Description
MRING_FAR_SW_FAIL_E is an alarm indicating an APS far-end switching failure in the
east direction of an MPLS-TP ring.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 527
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
APS protection on the MPLS-TP ring fails.
Possible Causes
Possible causes of the alarm are as follows:
l Cause: APS status is abnormal.
Procedure
Step 1 Cause: APS status is abnormal.
1. Re-enable the APS state machine of the MPLS-TP ring. For details, see Creating an
MPLS-TP Protection Ring.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.290 MRING_FAR_SW_FAIL_W
Description
MRING_FAR_SW_FAIL_W is an alarm indicating an APS far-end switching failure in the
west direction of an MPLS-TP ring.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 528
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
APS protection on the MPLS-TP ring fails.
Possible Causes
Possible causes of the alarm are as follows:
l Cause: APS status is abnormal.
Procedure
Step 1 Cause: APS status is abnormal.
1. Re-enable the APS state machine of the MPLS-TP ring. For details, see Creating an
MPLS-TP Protection Ring
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.291 MRING_OAM_LOCV_E
Description
MRING_OAM_LOCV_E is an alarm indicating OAM connectivity loss in the east direction
of an MPLS-TP ring. This alarm occurs when a east port on an MPLS-TP ring fails to receive
any expected OAM packet within three consecutive periods.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 529
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm triggers APS switching on the MPLS-TP ring.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical link is faulty.
l Cause 2: A physical component is faulty.
l Cause 3: The opposite device is faulty.
l Cause 4: The network is severely congested.
Procedure
Step 1 Cause 1: A physical link is faulty.
1. Check whether the physical link is normal. If not, rectify the fault.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: A physical component is faulty.
1. Check whether physical components are normal, such as fibers, boards, and optical
modules. If any physical component is faulty, replace the faulty component. For details,
see the Maintenance Guide.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The opposite device is faulty.
1. Check whether the opposite device is normal. For example, check whether a board fault
or a device reset occurs. If any fault occurs, rectify the fault.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The network is severely congested.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 530
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.292 MRING_OAM_LOCV_W
Description
MRING_OAM_LOCV_W is an alarm indicating OAM connectivity loss in the west direction
of an MPLS-TP ring. This alarm occurs when a west port on an MPLS-TP ring fails to receive
any expected OAM packet within three consecutive periods.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm triggers APS switching on the MPLS-TP ring.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical link is faulty.
l Cause 2: A physical component is faulty.
l Cause 3: The opposite device is faulty.
l Cause 4: The network is severely congested.
Procedure
Step 1 Cause 1: A physical link is faulty.
1. Check whether the physical link is normal. If not, rectify the fault.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: A physical component is faulty.
1. Check whether physical components are normal, such as fibers, boards, and optical
modules. If any physical component is faulty, replace the faulty component. For details,
see the Maintenance Guide.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 531
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The opposite device is faulty.
1. Check whether the opposite device is normal. For example, check whether a board fault
or a device reset occurs. If any fault occurs, rectify the fault.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The network is severely congested.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.293 MRING_OAM_RDI_E
Description
MRING_OAM_RDI_E is an alarm indicating a remote defect in the east direction of an
MPLS-TP ring. This alarm occurs when a east port on an MPLS-TP ring receives an RDI
packet.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm triggers APS switching on the MPLS-TP ring.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 532
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A ring channel is faulty.
As shown in Figure 4-27, a ring channel between NE2 and NE3 is faulty, and NE3 sends
an RDI packet to NE2. After receiving the RDI packet, NE3 reports an
MRING_OAM_RDI_E alarm in the east.
Figure 4-27 MRING_OAM_RDI_E detection
2. Receives an RDI packet from the
1. Detects a ring channel fault and
opposite and reports an
sends an RDI packet to the opposite.
MRING_OAM_RDI_E alarm.
RDI packet
East port West port East port West port
NE3 NE2
NE1
Procedure
Step 1 Cause: A ring channel is faulty.
1. Check whether physical components are normal, such as fibers, boards, and optical
modules. If any physical component is faulty, replace the faulty component. For details,
see the Maintenance Guide.
2. Check whether the NEs at the two ends of the ring channel are normal. For example,
check whether an NE reset occurs. If a fault occurs, rectify the fault.
3. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 533
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.294 MRING_OAM_RDI_W
Description
MRING_OAM_RDI_W is an alarm indicating a remote defect in the west direction of an
MPLS-TP ring. This alarm occurs when a west port on an MPLS-TP ring receives an RDI
packet.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm triggers APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A ring channel is faulty.
As shown in Figure 4-28, a ring channel between NE2 and NE3 is faulty, and NE2 sends
an RDI packet to NE3. After receiving the RDI packet, NE3 reports an
MRING_OAM_RDI_W alarm in the west.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 534
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-28 MRING_OAM_RDI_W detection
2. Receives an RDI packet from the
1. Detects a ring channel fault and
opposite and reports an
sends an RDI packet to the opposite.
MRING_OAM_RDI_W alarm.
RDI packet
East port West port East port West port
NE3 NE2
NE1
Procedure
Step 1 Cause: A ring channel is faulty.
1. Check whether physical components are normal, such as fibers, boards, and optical
modules. If any physical component is faulty, replace the faulty component. For details,
see the Maintenance Guide.
2. Check whether the NEs at the two ends of the ring channel are normal. For example,
check whether an NE reset occurs. If a fault occurs, rectify the fault.
3. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.295 MRING_OAM_SD_E
Description
MRING_OAM_SD_E is an alarm indicating a signal degrade (SD) in the east direction of an
MPLS-TP ring. This alarm occurs when a east port on an MPLS-TP ring has a connectivity
packet loss rate higher than the SD threshold but lower than the signal fail (SF) threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 535
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical link connection or an optical module is faulty.
l Cause 2: The network bandwidth is insufficient and congestion occurs.
l Cause 3: A service carrier layer is faulty.
Procedure
Step 1 Cause 1: A physical link connection or an optical module is faulty.
1. Clean fiber connectors and optical modules, and reconnect fibers.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network bandwidth is insufficient and congestion occurs.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A service carrier layer is faulty.
1. Check service carrier layers. For example, check whether PWs or tunnels report any of
the following alarms: 4.2.263 MPLS_PW_SD, 4.2.264 MPLS_PW_SF, 4.2.279
MPLS_TUNNEL_SD, and 4.2.280 MPLS_TUNNEL_SF. If any of the preceding
alarms occurs, clear the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 536
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.296 MRING_OAM_SD_W
Description
MRING_OAM_SD_W is an alarm indicating a signal degrade (SD) in the west direction of
an MPLS-TP ring. This alarm occurs when a west port on an MPLS-TP ring has a
connectivity packet loss rate higher than the SD threshold but lower than the signal fail (SF)
threshold.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical link connection or an optical module is faulty.
l Cause 2: The network bandwidth is insufficient and congestion occurs.
l Cause 3: A service carrier layer is faulty.
Procedure
Step 1 Cause 1: A physical link connection or an optical module is faulty.
1. Clean fiber connectors and optical modules, and reconnect fibers.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network bandwidth is insufficient and congestion occurs.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 537
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A service carrier layer is faulty.
1. Check service carrier layers. For example, check whether PWs or tunnels report any of
the following alarms: 4.2.263 MPLS_PW_SD, 4.2.264 MPLS_PW_SF, 4.2.279
MPLS_TUNNEL_SD, and 4.2.280 MPLS_TUNNEL_SF. If any of the preceding
alarms occurs, clear the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.297 MRING_OAM_SF_E
Description
MRING_OAM_SF_E is an alarm indicating a signal fail (SF) in the east direction of an
MPLS-TP ring. This alarm occurs when a east port on an MPLS-TP ring has a connectivity
packet loss rate higher than the SF threshold.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
Possible causes of the alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 538
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 1: A physical link connection or an optical module is faulty.
l Cause 2: The network bandwidth is insufficient and congestion occurs.
l Cause 3: A service carrier layer is faulty.
Procedure
Step 1 Cause 1: A physical link connection or an optical module is faulty.
1. Clean fiber connectors and optical modules, and reconnect fibers.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network bandwidth is insufficient and congestion occurs.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A service carrier layer is faulty.
1. Check service carrier layers. For example, check whether PWs or tunnels report any of
the following alarms: 4.2.263 MPLS_PW_SD, 4.2.264 MPLS_PW_SF, 4.2.279
MPLS_TUNNEL_SD, and 4.2.280 MPLS_TUNNEL_SF. If any of the preceding
alarms occurs, clear the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.298 MRING_OAM_SF_W
Description
MRING_OAM_SF_W is an alarm indicating a signal fail (SF) in the west direction of an
MPLS-TP ring. This alarm occurs when a west port on an MPLS-TP ring has a connectivity
packet loss rate higher than the SF threshold.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 539
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
Possible causes of the alarm are as follows:
l Cause 1: A physical link connection or an optical module is faulty.
l Cause 2: The network bandwidth is insufficient and congestion occurs.
l Cause 3: A service carrier layer is faulty.
Procedure
Step 1 Cause 1: A physical link connection or an optical module is faulty.
1. Clean fiber connectors and optical modules, and reconnect fibers.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network bandwidth is insufficient and congestion occurs.
1. Check the link bandwidth utilization and check whether the 4.2.152 FLOW_OVER
alarm is reported on the NMS. If the 4.2.152 FLOW_OVER alarm is reported, handle
the 4.2.152 FLOW_OVER alarm with reference to 4.2.152 FLOW_OVER.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: A service carrier layer is faulty.
1. Check service carrier layers. For example, check whether PWs or tunnels report any of
the following alarms: 4.2.263 MPLS_PW_SD, 4.2.264 MPLS_PW_SF, 4.2.279
MPLS_TUNNEL_SD, and 4.2.280 MPLS_TUNNEL_SF. If any of the preceding
alarms occurs, clear the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.299 MRING_OAM_UNEXPMEG_E
Description
MRING_OAM_UNEXPMEG_E is an alarm indicating that a east port on an MPLS-TP ring
receives an unexpected MEG ID. This alarm occurs when a east port on an MPLS-TP ring
receives an incorrect MEG ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 540
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A physical link connection is incorrect so that the node IDs of the neighbor NEs
do not match.
As shown in Figure 4-29, a correct link connection should be connecting NE1 and NE3
through NE2. When a west port on NE1 is connected to an east port on NE3, due to the
fact that the node IDs of NE1 and NE3 do not match, the west port on NE1 reports an
MRING_OAM_UNEXPMEG_W alarm and the east port on NE3 reports an
MRING_OAM_UNEXPMEG_E alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 541
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-29 MRING_OAM_UNEXPMEG_W/MRING_OAM_UNEXPMEG_E
Detection
Reporting an MRING_OAM_UNEXPMEG_E alarm
Node ID=3
East port West port
Node ID=4
West port NE3 East port
NE4
Node ID=2 NE2
East port Node ID=1 West port
NE1
West port East port
Reporting an MRING_OAM_UNEXPMEG_W alarm
Procedure
Step 1 Cause: A physical link connection is incorrect so that the node IDs of the neighbor NEs do
not match.
1. As shown in Figure 4-29, check whether link connections on the MPLS-TP ring are
correct. If an incorrect link connection exists, make it correct.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.300 MRING_OAM_UNEXPMEG_W
Description
MRING_OAM_UNEXPMEG_W is an alarm indicating that a west port on an MPLS-TP ring
receives an unexpected MEG ID. This alarm occurs when a west port on an MPLS-TP ring
receives an incorrect MEG ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 542
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A physical link connection is incorrect so that the node IDs of the neighbor NEs
do not match.
As shown in Figure 4-30, a correct link connection should be connecting NE1 and NE3
through NE2. When a west port on NE1 is connected to an east port on NE3, due to the
fact that the node IDs of NE1 and NE3 do not match, the west port on NE1 reports an
MRING_OAM_UNEXPMEG_W alarm and the east port on NE3 reports an
MRING_OAM_UNEXPMEG_E alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 543
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-30 MRING_OAM_UNEXPMEG_W/MRING_OAM_UNEXPMEG_E
Detection
Reporting an MRING_OAM_UNEXPMEG_E alarm
Node ID=3
East port West port
Node ID=4
West port NE3 East port
NE4
Node ID=2 NE2
East port Node ID=1 West port
NE1
West port East port
Reporting an MRING_OAM_UNEXPMEG_W alarm
Procedure
Step 1 Cause: A physical link connection is incorrect so that the node IDs of the neighbor NEs do
not match.
1. As shown in Figure 4-30, check whether link connections on the MPLS-TP ring are
correct. If an incorrect link connection exists, make it correct.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.301 MRING_OAM_UNEXPMEP_E
Description
MRING_OAM_UNEXPMEP_E is an alarm indicating that a east port on an MPLS-TP ring
receives an unexpected MEP ID. This alarm occurs when a east port on an MPLS-TP ring
receives an incorrect MEP ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 544
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A physical link connection is incorrect so that the local node receives a different
OAM packet with a same label.
Procedure
Step 1 Cause: A physical link connection is incorrect so that the local node receives a different OAM
packet with a same label.
1. Check whether the link connection is correct. If no, make a correct link connection.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.302 MRING_OAM_UNEXPMEP_W
Description
MRING_OAM_UNEXPMEP_W is an alarm indicating that a west port on an MPLS-TP ring
receives an unexpected MEP ID. This alarm occurs when a west port on an MPLS-TP ring
receives an incorrect MEP ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 545
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm may trigger APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: A physical link connection is incorrect so that the local node receives a different
OAM packet with a same label.
Procedure
Step 1 Cause: A physical link connection is incorrect so that the local node receives a different OAM
packet with a same label.
1. Check whether the link connection is correct. If no, make a correct link connection.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.303 MRING_OAM_UNEXPPER_E
Description
MRING_OAM_UNEXPPER_E is an alarm indicating that a east port on an MPLS-TP ring
receives unexpected period information. This alarm occurs when a east port on an MPLS-TP
ring receives a CCM packet whose period information is incorrect.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 546
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm triggers APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: The period information of CCM packets differs on the NEs of the MPLS-TP ring.
Procedure
Step 1 Cause: The period information of CCM packets differs on the NEs of the MPLS-TP ring.
1. Check the period information of CCM packets on each NE and ensure that the period
information of CCM packets is consistent on each NE. For details, see Creating an
MPLS-TP Protection Ring.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.304 MRING_OAM_UNEXPPER_W
Description
MRING_OAM_UNEXPPER_W is an alarm indicating that a west port on an MPLS-TP ring
receives unexpected period information. This alarm occurs when a west port on an MPLS-TP
ring receives a CCM packet whose period information is incorrect.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 547
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the board ID.
Impact on the System
This alarm triggers APS switching on the MPLS-TP ring.
Possible Causes
A possible cause of the alarm is as follows:
l Cause: The period information of CCM packets differs on the NEs of the MPLS-TP ring.
Procedure
Step 1 Cause: The period information of CCM packets differs on the NEs of the MPLS-TP ring.
1. Check the period information of CCM packets on each NE and ensure that the period
information of CCM packets is consistent on each NE. For details, see Creating an
MPLS-TP Protection Ring.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.305 MS_AIS
Description
The MS_AIS alarm indicates that the last three bits of the K2 byte in the signals received by
the line board are all 1.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 548
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
Services are unavailable. If automatic multiplex section protection (MSP) switching or path
protection switching is configured, this alarm triggers protection switching. If the MS_AIS is
configured as an optional clock switching condition, this alarm also triggers clock source
switching.
When the MS_AIS alarm is generated, the board sends the MS_RDI alarm to the opposite
end.
Possible Causes
Possible causes of this alarm are as follows:
l A high-level alarm such as R_LOS or R_LOF, which is reported by the opposite end and
inserted with the AIS alarm, is transmitted to the local end.
l The transmit unit at the opposite end is faulty.
l The receive unit at the local end is faulty.
Procedure
Step 1 Check whether the MS_AIS alarm is inserted into the transmit unit at the opposite end.
If... Then...
The MS_AIS alarm is inserted into the Cancel the inserted MS_AIS alarm.
transmit unit at the opposite end
The MS_AIS alarm is not inserted into the Go to the next step.
transmit unit at the opposite end
Step 2 Perform a self-loop using optical fibers to check whether the transmit unit at the opposite end
is faulty.
If... Then...
The transmit unit at the opposite end is Reset the line board. If the alarm persists,
faulty replace the line board.
The transmit unit at the opposite end is Go to the next step.
functioning properly
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 549
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Perform a self-loop at the optical port using optical fibers to check whether the line board at
the local end reports the MS_AIS alarm. If the line board reports the MS_AIS alarm, reset the
line board. If the alarm persists, replace the line board.
----End
Related Information
None.
4.2.306 MS_CROSSTR
Description
The MS_CROSSTR alarm indicates that a performance indicator of the multiplex section of
signals received by the line board crosses the threshold
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Parameter 2, The two most significant bits of Parameter 2 indicate the performance
Parameter 3 monitoring period.
l 0x01: The performance monitoring period is 15 minutes.
l 0x02: The performance monitoring period is 24 hours.
NOTE
The six least significant bits of Parameter 2 together with Parameter 3 indicate a
performance event ID.
Impact on the System
The services at the optical port are affected.
Possible Causes
The possible cause of this alarm is as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 550
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The threshold of the multiplex section performance indicator is set to a large or small
value.
l Bit errors occur in the multiplex section.
Procedure
Step 1 On the U2000, check whether the thresholds of multiplex section performance indicators
regarding MSBBE, MSES, MSSES, MSCSES, and MSUAS are out of range.
If... Then...
The threshold of a multiplex section Change the threshold to the default value.
performance indicator is out of range Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The thresholds of the multiplex section Go to the next step.
performance indicators are within the
specified ranges
Step 2 View alarms on the U2000 to check whether the board that reports the MS_CROSSTR alarm
also reports other multiplex section bit error alarms, such as B2_EXC or B2_SD.
If... Then...
The B2_EXC or B2_SD alarm is reported Clear the B2_EXC or B2_SD alarm. Then,
check whether the MS_CROSSTR alarm is
cleared. If the MS_CROSSTR alarm
persists, go to the next step.
The B2_EXC or B2_SD alarm is not Go to the next step.
reported
Step 3 Perform loopbacks at the local end and the opposite end. After the performance monitoring
period ends, locate the faulty board.
If... Then...
A board at the opposite end reports a The transmit unit at the opposite end is
multiplex section performance event faulty. Replace the faulty board.
A board at the local end reports a multiplex The receive unit at the local end is faulty.
section performance event Replace the faulty board.
----End
Related Information
B2_EXC, B2_SD, 5.4.51 MSBBE, 5.4.53 MSES, 5.4.59 MSSES, 5.4.52 MSCSES, 5.4.60
MSUAS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 551
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.307 MS_RDI
Description
The MS_RDI alarm indicates a remote multiplex section receiving failure. This alarm is
generated when the last three bits of the K2 byte in signals received by the line board are 110.
Parameters
None.
Impact on the System
The services at the opposite end are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The opposite end receives the R_LOS, R_LOC, R_LOF, MS_AIS, or B2_EXC alarm.
l The receive unit at the opposite end is faulty.
l The transmit unit at the local end is faulty.
Procedure
Step 1 On the U2000, check whether the line board at the opposite end receives the R_LOS, R_LOS,
R_LOF, MS_AIS, or B2_EXC alarm.
If... Then...
The line board at the opposite end receives Clear the R_LOS, R_LOS, R_LOF,
the R_LOS, R_LOS, R_LOF, MS_AIS, or MS_AIS, or B2_EXC alarm. Then, check
B2_EXC alarm whether the MS_RDI alarm is cleared. If the
MS_RDI alarm persists, go to the next step.
The line board at the opposite end does not Go to the next step.
receive the R_LOS, R_LOS, R_LOF,
MS_AIS, or B2_EXC alarm
Step 2 If the line board at the opposite end does not receive the R_LOS, R_LOS, R_LOF, MS_AIS,
or B2_EXC alarm or the MS_RDI alarm persists after the R_LOS, R_LOS, R_LOF, MS_AIS,
or B2_EXC alarm is cleared, the line board is faulty. Perform loopbacks at the local end and
the opposite end to locate the faulty line board, and replace the faulty line board.
----End
Related Information
R_LOS, R_LOC, R_LOF, MS_AIS, and B2_EXC
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 552
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.308 MS_REI
Description
The MS_REI alarm indicates that the M1 byte in signals received by the line board indicates
remote multiplex section bit errors. After receiving multiplex section background block error
(B2 BBE) signals, the line board at the opposite end sends the number of B2 BBE signals to
the local end using the M1 byte.
Attribute
Alarm Severity Alarm Type
Warning Service alarm
Parameters
None.
Impact on the System
None.
Possible Causes
Possible causes of this alarm are as follows:
l The B2 bit errors are received at the opposite end.
l The receive unit at the opposite end is faulty.
l The transmit unit at the local end is faulty.
Procedure
Step 1 On the U2000, view alarms reported at the opposite end to check whether there are B2 bit
errors on the line board at the opposite end.
If... Then...
There are B2 bit errors on the line board at Clear the bit errors by referring to the
the opposite end sections about the B2_EXC and B2_SD
alarms.
There are no B2 bit errors on the line board Go to the next step.
at the opposite end
Step 2 Perform a self-loop on the corresponding optical port at the local end to check whether the
number of bit errors in the MS_REI performance event increases.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 553
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
If the number of bit errors does not increase The transmit unit at the opposite end is
faulty. Replace the faulty line board.
If the number of bit errors increases The receive unit at the local end is faulty.
Replace the faulty line board.
----End
Related Information
B2_EXC and B2_SD
4.2.309 MSAD_CROSSTR
Description
The MSAD_CROSSTR alarm indicates that a multiplex section adaptation performance
indicator of the line board crosses the threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None.
Impact on the System
The services are affected.
Possible Causes
Possible causes of this alarm are as follows:
l The performance threshold is set to an inappropriate value.
l Multiplex section bit errors occur.
l The loop clock is distorted.
Procedure
Step 1 On the U2000, check whether the thresholds of multiplex section adaptation performance
indicators regarding AUPJCHIGH, AUPJCLOW, and AUPJCNEW are within the specified
ranges.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 554
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The threshold of a multiplex section Change the threshold to the default value.
adaptation performance indicator is out of Then, check whether the alarm is cleared. If
range the alarm persists, go to the next step.
The thresholds of the multiplex section Go to the next step.
adaptation performance indicators are
within the specified ranges
Step 2 View alarms on the U2000 to check whether the board that reports the MSAD_CROSSTR
alarm also reports other multiplex section bit error alarms, such as B1_EXC, B1_SD,
B2_EXC, or B2_SD.
If... Then...
The B1_EXC, B1_SD, B2_EXC, or B2_SD Clear the B1_EXC, B1_SD, B2_EXC, or
alarm is reported B2_SD alarm. Then, check whether the
MSAD_CROSSTR alarm is cleared. If the
MSAD_CROSSTR alarm persists, go to the
next step.
The B1_EXC, B1_SD, B2_EXC, or B2_SD Go to the next step.
alarm is not reported
Step 3 Check whether the clock tracing in the entire network is correctly configured.
If... Then...
The clock tracing is incorrectly configured Re-configure the clock tracing correctly.
After the configured performance
monitoring period ends, check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The clock tracing is correctly configured Go to the next step.
Step 4 Perform loopbacks at the local end and the opposite end to locate the faulty board.
If... Then...
A board at the opposite end reports a The transmit unit at the opposite end is
multiplex section adaptation performance faulty. Replace the faulty board.
event
A board at the local end reports a multiplex The receive unit at the local end is faulty.
section adaptation performance event Replace the faulty board.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 555
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
B1_EXC, B1_SD, B2_EXC, and B2_SD
4.2.310 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that an Ethernet ring network contains
more than one RPL_OWNER node.
Attribute
Alarm Severity Alarm Type
Minor Operation 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the Ethernet ring protection ERPS instance ID.
Impact on the System
All the nodes on an Ethernet ring network lose connectivity. If the Ethernet ring network is
configured with services, services are interrupted.
Possible Causes
Possible cause of this alarm is as follows:
The Ethernet ring network contains more than one RPL_OWNER node.
Procedure
Step 1 Check whether the Ethernet ring network contains more than one RPL_OWNER node.
If... Then...
The Ethernet ring network contains more Reconfigure the ERPS protection. Ensure
than one RPL_OWNER node that all nodes on the Ethernet ring network
are configured with ERPS protection and
the Ethernet ring network contains only one
RPL_OWNER node.
The Ethernet ring network contains only Contact Huawei technical support engineers
one RPL_OWNER node for handling the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 556
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
----End
Related Information
None.
4.2.311 MUT_LOS
Description
The MUT_LOS alarm indicates loss of multiplexed signals. This alarm is reported when
multiplexed optical signals received by a board are lost.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Impact on the System
The services carried on the optical port are interrupted.
Possible Causes
l Cause 1: The fibers connected to the local receive optical port are incorrectly connected,
not connected, or damaged.
l Cause 2: Signal attenuation on the line is excessively high.
The following figure shows details.
l Cause 3: The board that reports the alarm is faulty.
Procedure
l On the NMS, check for the board that first reports the alarm along the reverse direction
of the signal flow. Perform the following operations on the board:
l Cause 1: The fibers connected to the local receive optical port are incorrectly connected,
not connected, or damaged.
a. Check whether the fibers connected to the optical port are correctly connected. If
the fibers are incorrectly connected, re-install the fibers.
b. Check whether the fibers connected to the optical port and fiber connectors are
dirty. If they are dirty, clean or replace the fiber connectors. For details, see
Cleaning the Optical Fiber Connector.
c. If the alarm persists, check whether the pigtail meets the following requirements:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 557
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
n The bending radius is not less than 6 cm.
n The fiber connectors are properly installed.
n The fiber connectors are clean.
n The cable is intact.
If the preceding requirements are not met, replace the pigtail.
d. If the alarm persists, go to Cause 2.
l Cause 2: Signal attenuation on the line is excessively high.
a. Check the input optical power of the local board using an optical power meter.
b. If the receive optical power is excessively low, check whether the optical attenuator
configured for the receive port has excessively high attenuation. If the attenuation is
excessively high, adjust the value or replace the optical attenuator.
c. If the alarm persists, rectify the faulty fiber between the NEs.
d. If the alarm persists, go to Cause 3.
l Cause 3: The board that reports the alarm is faulty.
a. If the alarm persists, replace the local board, which may be faulty.
b. If the alarm persists, contact Huawei technical support personnel to handle the
alarm.
----End
Related Information
None
4.2.312 NE_POWER_OVER
Description
The NE_POWER_OVER alarm indicates that the power consumption of an NE crosses the
threshold.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 558
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the type of NE power consumption that crosses the threshold.
l 0x01: The physical power consumption of the NE crosses the threshold.
l 0x02: The logical power consumption of the NE crosses the threshold.
Impact on the System
If the NE constantly works with high power consumption, the power board constantly works
with heavy load.
Possible Causes
Possible causes of this alarm are as follows:
l The power consumption of each logical board installed on the NE crosses the threshold.
l The total power consumption of all the physical boards installed on the NE crosses the
threshold.
Procedure
Step 1 Delete unused logical boards on the U2000.
Step 2 Remove unused physical boards from the NE. The alarm is automatically cleared.
----End
Related Information
None.
4.2.313 NEBD_XC_DIF
Description
The NEBD_XC_DIF alarm indicates that the cross-connect matrix data of the NE and board
is different. For the board supporting service cross-connection, the alarm occurs when the
cross-connection data stored on the SCC is not consistent with that stored on the board.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 559
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 and Parameters 2 Indicates the slot ID.
Parameters 3 Indicates the cross-connect type. For example:
0x3 indicates inconsistent space division cross-connections.
Impact on the System
Services are interrupted during service grooming or perform warm reset on the board.
Possible Causes
l Cause 1: The cross-connection data of the board is incorrect.
l Cause 2: The cross-connection data stored on the board is different from that on the SCC
board.
Procedure
l Query the alarm on the NMS. Record the slot ID of the board that reports the alarm.
l Cause 1: The cross-connection data of the board is incorrect.
a. Re-configure the cross-connection data on the NMS.
l Cause 2: The cross-connection data stored on the board is different from that on the SCC
board.
a. If the alarm persists, perform a warm reset on the board related to service cross-
connections on the NMS.
b. If the alarm persists, perform warm reset on the SCC on the NMS.
----End
Related Information
None
4.2.314 NEIP_CONFUSION
Description
The NEIP_CONFUSION alarm indicates an NE IP address conflict. (Several NEs use the
same IP address.)
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 560
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1-4 Indicate the IP address used by several NEs.
Impact on the System
The NEs using the same IP address may be unreachable to the NMS or cannot be stably
managed.
Possible Causes
The possible cause of the NEIP_CONFUSION alarm is as follows:
Several NEs use the same IP address.
l Cause 1: Several NEs use the same IP address.
l Cause 2: DCN is enabled on both ports of the NE that reports the alarm, and the two
ports are directly connected through a fiber or network cable.
Procedure
Step 1 On the main menu, choose Fault > Browse Current Alarm. Find the alarm based on the
alarm severity and name, and view the alarm information to determine the NE that reports the
alarm.
Step 2 Cause 1: Several NEs use the same IP address.
1. Change the IP address of the NE according to the network plan. For details, see
Changing IP Address of an NE in Commissioning Guide. Then check whether the alarm
is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: DCN is enabled on both ports of the NE that reports the alarm, and the two ports are
directly connected through a fiber or network cable.
1. Determine whether the user wants to disconnect the fiber or network cable.
If... Then...
The user wants to disconnect the fiber or Disconnect the fiber or network cable.
network cable, Then check whether the alarm is cleared.
If the alarm persists, go to Step 4.
The user does not want to disconnect the Go to Step 3.2.
fiber or network cable,
2. Determine the DCN type according to the network plan, and perform operations
accordingly.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 561
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Inband DCN is used, Disable the DNC port between the
directly connected ports. For details, see
Configuring Port DCN in Feature
Description. Then check whether the
alarm is cleared. If the alarm persists, go
to Step 4.
Outband DCN is used, Disable the DCC channel between the
directly connected ports. For details, see
Configuring the DCC Channel in Feature
Description. Then check whether the
alarm is cleared. If the alarm persists, go
to Step 4.
Step 4 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.315 NESF_LOST
Description
The NESF_LOST alarm indicates that the NE software in the system control unit is lost.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicates the types of files unavailable in the board software.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 562
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
If the NE software is unavailable in the active and standby system control units, the system
control units cannot function properly in the following cases:
The system control, cross-connect, and timing boards are reset.
The system control, cross-connect, and timing boards restart after they are powered off.
As a result, the U2000 fails to monitor NEs.
Possible Causes
Possible causes of this alarm are as follows:
l The NE software is not loaded or loading the NE software fails.
l The NE software is lost or damaged.
l The flash memory cannot be detected or is faulty.
Procedure
Step 1 View the NESF_LOST alarm on the U2000 to determine the board that reports the
NESF_LOST 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 faulty board.
----End
Related Information
None.
4.2.316 NESOFT_MM
Description
The NESOFT_MM alarm indicates that the NE software versions in the active and standby
system control units are inconsistent.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 563
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 l 0x01: files in the flash memory
l 0x02: software that is running
Parameter 2 and Indicate the IDs of inconsistent files in the active system control unit.
Parameter 3
Parameter 4 Indicates the alarm cause.
l 0x04: The versions of files in the active and standby areas (OFS1 and
OFS2) of a system control unit are inconsistent.
l 0x08: The versions of files in the active and standby system control
units are inconsistent, or the files in the corresponding directories of
the active and standby system control units have different names.
l 0x0C: The versions of files in the active and standby areas of a system
control unit are inconsistent, and the versions of files in the active and
standby system control units are inconsistent.
Impact on the System
l The active/standby switching of the system is affected.
l If the NE software does not exist in the flash memory, the system cannot restart after the
system is powered off or reset.
Possible Causes
Possible causes of this alarm are as follows:
l The versions of the software running in the active and standby system control units are
inconsistent.
l The versions of the software in the active and standby areas (OFS1 and OFS2) are
inconsistent.
l The files in the corresponding directories of the active and standby system control units
have different names.
Procedure
Step 1 Contact Huawei technical support engineers to reload the required software.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 564
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.317 NESTATE_INSTALL
Description
The NESTATE_INSTALL alarm indicates that an NE is in the installing state. This alarm is
generated when the NE is just delivered from the factory or a user issues the command for
initializing the NE.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
None.
Impact on the System
After the alarm occurs, no configuration exists on the NE side. If configurations are not
reloaded from the U2000, the NE cannot be configured with services.
If NE data is uploaded after the NESTATUS_INSTALL alarm is generated, the uploaded NE
data is empty data. If the empty data is downloaded, the NE data is cleared. As a result,
services are interrupted. Therefore, after this alarm is generated, NE data can only be
downloaded, but cannot be uploaded.
Possible Causes
Possible causes of this alarm are as follows:
l A user issues the command for initializing the NE. However, verification is not
performed.
l The NE is in the initializing state, and is not configured with any data.
l The database in the system control unit is faulty.
l The system control, cross-connect, and timing board is replaced when there is only one
system control, cross-connect, and timing board.
Procedure
Step 1 Apply the configuration data again and perform verification. Then, check whether the
NESTATE_INSTALL alarm is cleared.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 565
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.318 NO_BD_PARA
Description
The NO_BD_PARR alarm indicates absence of the board parameter table.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Impact on the System
The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l The correct parameter table is not loaded before delivery.
l The incorrect parameter table file is loaded on site, which overlaps the original file.
l The parameter table file is abnormally lost in the running process.
Procedure
Step 1 Perform warm reset on the faulty board through the NMS. For details, see Resetting Boards in
the Supporting Tarks.
Step 2 If the alarm persists, reset (cold) or reseat the faulty board. For details, see Resetting Boards
in the Supporting Tarks.
Cold resetting or replacing a board will interrupt services. The operation is risky.
Step 3 If the alarm persists, replace the faulty board. For details, see Parts Replacement.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 566
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.319 NO_BD_POWER
Description
Board not powered on. This alarm is generated when a board fails to start properly because
the power module of the board does not apply sufficient power supplies to the board and as a
result the CPLD is powered on but the CPU is not.
Attribute
Alarm Severity Alarm Type
Major Equipment
Parameters
None
Impact on the System
The board fails to start properly.
Possible Causes
l External power supplies cannot satisfy the power consumption requirements of the
power supply module of the board.
l The power supply module of the board is faulty.
Procedure
Step 1 Add external power supplies or replace the board.
----End
Related Information
None
4.2.320 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 567
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2, Indicate the ID of the file that is lost.
Parameter 3
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.
Impact on the System
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.
l 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 568
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 View alarms on the U2000 to check whether the NO_BD_SOFT alarm is cleared.
If... Then...
The alarm is cleared The fault is rectified.
The alarm persists Go to the next step.
Step 3 If the alarm persists, replace the board.
----End
Related Information
None.
4.2.321 NO_ELABEL
Description
The NO_ELABEL alarm indicates that the electronic label is unloaded.
Attribute
Alarm Severity Alarm Type
Warning 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 System control, fan, and power boards:
l 0x00: indicates that the electronic label of the backplane is lost.
l Other value: indicates the ID of the board whose electronic label is lost.
Other boards:
l 0x01: indicates that the electronic label of the board is lost.
l 0x03: indicates that the electronic label of the optical module is lost.
Parameter 2 System control, fan, and power boards: This parameter does not exist.
Other boards: The parameter value is fixed at 0x01.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 569
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 System control, fan, and power boards: This parameter does not exist.
Other boards:
l If parameter 1 is 0x01, the value of parameter 3 is fixed at 0x01.
l If parameter 1 is 0x03, parameter 3 indicates the ID of the optical port.
Impact on the System
None
Possible Causes
The electronic label is unloaded or lost.
Procedure
Step 1 Check whether the electronic label of the backplane, board, or optical module is faulty based
on alarm parameters.
Step 2 If the electronic label of the board or optical module is faulty, replace the board or optical
module.
Step 3 If the electronic label of the backplane is faulty, replace the chassis.
Step 4 If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None
4.2.322 NO_LSR_PARA_FILE
Description
The NO_LSR_PARA_FILE alarm indicates that the laser parameter file of an optical module
with EEPROM does not exist on the line board that uses laser parameter files when the board
restarts.
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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 570
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical port number.
Impact on the System
The optical module cannot be correctly configured, and the board cannot correctly transmit
and receive services.
Possible Causes
The possible cause of this alarm is as follows:
l No laser parameter file is detected in the EEPROM of the optical module.
Procedure
Step 1 Replace the optical module.
Step 2 On the U2000, check whether the NO_PARA_FILE alarm is cleared.
If... Then...
If this alarm is cleared No further action is required.
If this alarm persists Go to the next step.
Step 3 Replace the line board that reports the NO_LSR_PARA_FILE alarm.
----End
Related Information
None.
4.2.323 NTP_SYNC_FAIL
Description
The NTP_SYNC_FAIL alarm indicates that NTP time synchronization fails. This alarm is
reported when the NE time is not synchronized with the NTP time. This alarm clears after the
NE time is synchronized with the NTP time.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 571
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
Time on the alarmed NE is different from time on the NTP server. The records on the NE,
such as performance events, alarms, and operations, cannot be kept with exact times.
Possible Causes
Possible causes of the NTP_SYNC_FAIL alarm are as follows:
l The NTP server is not configured or is configured incorrectly.
l The NTP server cannot communicate with the NE.
l The NTP server fails.
Procedure
Step 1 Check whether the NTP server is configured correctly.
If... Then...
The NTP server is configured incorrectly Configure the NTP server correctly and
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The NTP server is configured correctly Go to the next step.
Step 2 Check whether the DCN communication between the NTP server and the NE is normal.
If... Then...
The DCN communication is abnormal Troubleshoot the network and check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The DCN communication is normal Go to the next step.
Step 3 Check whether the NTP server is running correctly.
If... Then...
The NTP server is abnormal Restart the NTP server.
The NTP server is running correctly Contact Huawei technical support engineers
to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 572
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.324 NULL_SEND
Description
NULL signals (with payload being "0"s) being sent out. When the NULL mapping status of
the board is enabled, the NULL_SEND alarm is generated, indicating that the NULL signals
are being sent out.
Attribute
Alarm Severity Alarm Type
Warning Equipment alarm
Parameters
None
Impact on the System
When this alarm is generated, the board that reports the alarm is sending out NULL signals
and the peer station will receive the NULL signals, interrupting services.
Possible Causes
The NULL Mapping Status parameter of the board is set to Enabled.
Procedure
Step 1 Check the NULL mapping status of the board that reports the alarm. If the NULL mapping
status is enabled, change the value from Enabled to Disabled.
NOTE
If the NULL mapping status needs to be enabled in the actual situation, suppress the alarm and then
disable the NULL mapping status. After that, configure the NULL_SEND alarm to be monitored.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 573
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.325 OA_LOW_GAIN
Description
The OA_LOW_GAIN alarm indicates that the gain of an optical amplifier board decreases.
This alarm is reported when the gain of an optical amplifier board is lower than 3 dB, the
nominal gain.
Attribute
Alarm Severity Alarm Type
Critical QoS alarm
Parameters
None
Impact on the System
If the alarm is caused by excessively high input optical power, system redundancy decreases,
affecting later capacity expansion.
Possible Causes
l Cause 1: The input optical power of the board is excessively high.
l Cause 2: The board that reports the alarmis faulty.
Procedure
l Cause 1: The input optical power of the board is excessively high.
a. Query whether the input optical power of the board is within the normal range on
the NMS.
b. If the input optical power is abnormal, adjust the attenuation of the optical
attenuator connected to the receive optical port.
c. If the alarm persists, go to Cause 2.
l Cause 2: The board that reports the alarmis faulty.
a. If the alarm persists, replace the faulty board. For details, see Parts Replacement.
b. If the alarm persists, contact Huawei technical support personnel to handle the
alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 574
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.326 OCD
Description
The OCD alarm indicates that the cell delimitation state machine is in the hunt or presyn state.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
All the services in the receive direction of the port are intermittently transmitted.
Consequently, cells are lost.
Possible Causes
Possible causes of the OCD alarm are as follows:
l A great number of bit errors occur in the SDH receive path connected to the alarmed
port. That is, bit error alarms, such as B1_SD, B2_SD, or B3_SD, are reported.
l The ATM processing chip on the alarmed board is faulty.
Procedure
Step 1 On the U2000, check whether the B1_EXC, B2_EXC, or B3_EXC alarm which indicates bit
errors on the tributary board exceeds the threshold is reported on the local NE.
If... Then...
The B1_EXC, B2_EXC, or B3_EXC Handle the alarms, and then check whether the
alarm is reported OCD alarm is cleared. If the OCD alarm persists,
go to the next step.
The B1_EXC, B2_EXC, or B3_EXC Go to the next step.
alarm is not reported
Step 2 Reset (cold) or reseat the board that reports the OCD alarm. Then, check whether the OCD
alarm is cleared.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 575
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 If the OCD alarm persists, replace the board and check whether the OCD alarm is cleared. If
the OCD alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.327 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The internal current loop of the storage battery is broken.
l 0x02: The recharge current of the storage battery is excessively high.
l 0x03: The storage battery is discharged unevenly.
Impact on the System
The equipment cannot operate properly or even be damaged.
Possible Causes
Possible causes of this alarm are as follows:
l The circuit breaker of the storage battery in the cabinet is open or the fuse is blown.
l The positive and negative polarities of the storage battery are connected inversely.
l The power module frame is faulty.
l The PMU is faulty.
l The power module is faulty. For example, the battery is faulty or is deteriorating.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 576
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 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 PMU.
Step 5 Check whether the ODC_MDL_ABN alarm is reported.
If... Then...
The ODC_MDL_ABN alarm is reported Clear the ODC_MDL_ABN alarm.
The ODC_MDL_ABN alarm is not reported Replace the power module.
----End
Related Information
None.
4.2.328 ODC_BATTERY_PWRDOWN
Description
The ODC_BATTERY_PWRDOWN alarm indicates that the storage battery is powered off.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 577
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The storage battery is powered off due to low voltage.
l 0x02: The storage battery is powered off due to background control.
l 0x03: The storage battery is powered off manually and locally.
l 0x04: The storage battery is powered off due to a high temperature.
Impact on the System
No backup power supply is available to the equipment.
Possible Causes
Possible causes of this alarm are as follows:
l The storage battery is powered off due to background control.
l The BAT OFF button on the front panel of the PMU is pressed.
l The AC input is abnormal.
l The power module is faulty.
l The PMU is faulty.
l The temperature threshold that triggers power-off of the storage battery is set to an
inappropriate value.
l The temperature of the storage battery is high.
l The temperature sensor of the power module is faulty.
Procedure
Step 1 Determine the cause for the alarm based on the alarm parameters displayed on the U2000.
Step 2 Power on the storage battery.
Step 3 Press and hold down the BAT ON button on the front panel of the PMU for 5 to 10 seconds to
power on the storage battery.
Step 4 Query the threshold for triggering an alarm indicating an exception in the mains supply
voltage. Determine whether the threshold is appropriate according to the configuration plan.
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 Go to the next step.
Step 5 Check whether the AC circuit breaker is closed.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 578
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The AC circuit breaker is open Close the AC circuit breaker.
The AC circuit breaker is closed Go to the next step.
Step 6 Check the AC input power cable.
If... Then...
The AC input power cable is incorrectly connected Connect the cable correctly.
The AC input power cable is deteriorating or damaged Replace the cable.
Step 7 Rectify the fault on the power module by following the procedure of handling the
ODC_MDL_ABN alarm.
Step 8 Rectify the fault on the PMU.
Step 9 Query the temperature threshold for triggering an alarm indicating power-off. Determine
whether the threshold is appropriate according to the configuration plan.
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 Go to the next step.
Step 10 Replace the storage battery.
Step 11 Replace the temperature sensor of the power module.
----End
Related Information
None.
4.2.329 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 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 579
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
The temperature, ambient humidity, and dust-proof capability of the equipment are affected
by the external environment. In addition, the equipment may be damaged or stolen.
Possible Causes
Possible causes of this alarm are as follows:
l The door access alarm configuration is incorrect.
l The cabinet door is opened by someone.
l The cable between the sensor and the monitoring equipment is incorrectly connected.
l The sensor is faulty.
l The monitoring equipment is faulty.
l No door status sensor is installed.
Procedure
Step 1 Check whether the door access alarm configuration is consistent with the configuration plan.
If... Then...
The door access alarm configuration is consistent Go to the next step.
with the configuration plan
The door access alarm configuration is inconsistent Configure the door access alarm
with the configuration plan enabling status correctly.
Step 2 Close the cabinet door.
Step 3 Check whether the cable between the sensor and the monitoring equipment is correctly
connected.
If... Then...
The cable is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is connected correctly Go to Step 4.
Step 4 Rectify the fault on the sensor. Then, check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 580
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Go to Step 5.
Step 5 Rectify the fault on the monitoring equipment.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to Step 6.
Step 6 Install a door status sensor and enable the door access alarm.
----End
Related Information
None.
4.2.330 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED alarm indicates that a circulating fan is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the location of the fault.
l 0x01: fan at the internal air exhaust vent
l 0x02: fan at the external air exhaust vent
Impact on the System
The cabinet cannot dissipate heat properly. As a result, the equipment may be damaged and
services may be affected.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 581
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The cable of the circulating fan is connected incorrectly.
l The circulating fan is faulty.
l No circulating fan is installed.
Procedure
Step 1 Determine the faulty circulating fan based on the alarm parameters displayed on the U2000.
Step 2 Connect the cable of the circulating fan correctly according to the specified regulations.
Step 3 Replace the module where the circulating fan resides.
Step 4 Install a circulating fan.
----End
Related Information
None.
4.2.331 ODC_HUMI_ABN
Description
The ODC_HUMI_ABN alarm indicates that the ambient humidity in the cabinet crosses the
threshold.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The ambient humidity is greater than the upper threshold.
l 0x02: The ambient humidity is less than the lower threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 582
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
High ambient humidity may damage the equipment, and low ambient humidity may shorten
the life of the equipment.
Possible Causes
Possible causes of this alarm are as follows:
l The ambient humidity alarm threshold is set to an inappropriate value.
l The cable between the humidity sensor and the monitoring equipment is incorrectly
connected.
l The humidity sensor is faulty.
l The monitoring equipment is faulty.
Procedure
Step 1 Check whether the ambient humidity alarm threshold is appropriate according to the
configuration plan.
If... Then...
The threshold is set to an appropriate value Go to Step 2.
The threshold is set to an inappropriate value Set the threshold to an appropriate value.
Step 2 Check whether the cable between the humidity sensor and the monitoring equipment is
correctly connected.
If... Then...
The cable is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is connected correctly Go to Step 3.
Step 3 Rectify the fault on the humidity sensor.
Step 4 Then, check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to Step 5.
Step 5 Rectify the fault on the monitoring equipment.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 583
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.332 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The secondary load is powered off due to low voltage.
l 0x02: The secondary load is powered off due to background control.
l 0x03: The secondary load is powered off due to startup at a low
temperature
l 0x04: The secondary load is powered off due to a high temperature
Impact on the System
The services on the secondary load are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The secondary load is powered off due to background control.
l The AC input is abnormal.
l The power module is faulty.
l The PMU is faulty.
l The cabinet temperature is lower than the lower threshold.
l The ambient temperature sensor is faulty.
l The temperature threshold that triggers power-off of the secondary load is set to an
inappropriate value.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 584
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The cabinet temperature is higher than the upper threshold.
l The ambient temperature sensor is faulty.
Procedure
Step 1 Determine the cause for the alarm based on the alarm parameters displayed on the U2000.
Step 2 Power on the secondary load.
Step 3 Query the threshold for triggering an alarm indicating an exception in the mains supply
voltage. Determine whether the threshold is appropriate according to the configuration plan.
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 Go to the next step.
Step 4 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 Go to the next step.
Step 5 Check the AC input power cable.
If... Then...
The AC input power cable is incorrectly connected Connect the cable correctly.
The AC input power cable is deteriorating or damaged Replace the cable.
Step 6 Rectify the fault on the power module by following the procedure of handling the
ODC_MDL_ABN alarm.
Step 7 Rectify the fault on the PMU.
Step 8 Check whether the cabinet temperature is lower than the lower threshold.
If... Then...
The cabinet temperature is within the Go to the next step.
specified range
The cabinet temperature is lower than the Find out the cause of the low temperature,
lower threshold and rectify the fault.
Step 9 Replace the ambient temperature sensor of the power module.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 585
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 10 Query the upper temperature threshold for triggering an alarm indicating power-off of the
secondary load. Determine whether the threshold is appropriate according to the configuration
plan.
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 Go to the next step.
Step 11 Check whether the ambient temperature is continuously higher than the upper threshold.
If... Then...
The temperature is not continuously higher than Go to the next step.
the upper threshold
The temperature is continuously higher than the Lower the ambient temperature of
upper threshold the equipment.
Step 12 Replace the ambient temperature sensor.
----End
Related Information
The load corresponding to the DC power outlet on the cabinet functions as the secondary
load.
4.2.333 ODC_MDL_ABN
Description
The ODC_MDL_ABN alarm indicates that an exception occurs in a power module.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the power module that reports the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 586
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2, Indicates the alarm cause.
Parameter 3
l 0x01: The power module is shut down.
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 PMU, or the
power module cannot be detected.
l 0x05: No power module is installed in the outdoor cabinet, and the
logical slot for the power module is not set on the U2000.
l 0x06: A power module is installed in the outdoor cabinet, but the logical
slot for the power module is not set on the U2000.
Impact on the System
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 may be powered off.
Possible Causes
Possible causes of this alarm are as follows:
l The power module is not configured on the U2000.
l The power module cannot be detected.
l The power module is faulty.
l An exception occurs in the PMU.
Procedure
Step 1 Set the logical slot for the power module on the U2000.
Step 2 Check whether the power module cannot be detected, or the power module is installed
loosely.
If... Then...
The power module cannot be detected Install the power module correctly. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The power module can be detected Reinstall the power module properly.
Step 3 Check whether the power module is faulty.
If... Then...
The power module is faulty Replace the optical module. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 587
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The power module is properly functioning Go to the next step.
Step 4 Check whether an exception occurs in the PMU. If an exception occurs, replace the PMU.
----End
Related Information
None.
4.2.334 ODC_POWER_FAIL
Description
The ODC_POWER_FAIL alarm indicates that the mains supply input power voltage or DC
output power voltage is abnormal.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the fault type.
l 0x56: The mains supply input power is over-voltage.
l 0x57: The mains supply input power is under-voltage.
l 0x58: The DC output power is over-voltage.
l 0x59: The DC output power is under-voltage.
l 0x5b: There is no mains supply input power.
l 0x5c: The phase voltage is unavailable.
Impact on the System
When the mains supply input power is abnormal, the storage battery provides power supply
for the equipment and cannot support long-term operation of the equipment.
When the DC output power abnormal, the services on the equipment are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 588
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The mains supply input power voltage is abnormal.
l The DC output power voltage is abnormal.
Procedure
Step 1 Check whether the threshold for triggering an alarm indicating abnormal mains supply input
power voltage is set to appropriate value.
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 Go to the next step.
Step 2 Check whether the AC circuit breaker is open.
If... Then...
The AC circuit breaker is open Close the AC circuit breaker.
The AC circuit breaker is closed Go to the next step.
Step 3 Check the AC input power cable.
If... Then...
The cable is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is connected correctly Go to the next step.
Step 4 Check whether the AC power grid distributes power correctly.
If... Then...
The AC power grid distributes power Rectify the fault on the power module at the
incorrectly base station.
The AC power grid distributes power Go to the next step.
correctly
Step 5 Check whether the monitoring equipment is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 589
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Rectify the fault on the monitoring
The monitoring equipment is faulty
equipment.
The monitoring equipment is functioning Go to Step 6.
properly
Step 6 Check whether the alarm threshold is set to an appropriate value.
If... Then...
The alarm threshold is set to an inappropriate Set the threshold to an appropriate
value value.
The alarm threshold is set to an appropriate value Go to the next step.
Step 7 Check whether the PSU module is faulty.
If... Then...
The PSU module is faulty Rectify the fault on the PSU module.
The PSU module is functioning properly Go to the next step.
Step 8 Check whether the power of the storage battery is sufficient.
If... Then...
The power is insufficient Recharge the storage battery.
The power is sufficient Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.335 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 590
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
The equipment may be burned.
Possible Causes
Possible causes of this alarm are as follows:
l The smoke alarm configuration is inconsistent with the configuration plan.
l A fire occurs in the cabinet.
l The cable between the smoke sensor and the monitoring equipment is connected
incorrectly.
l The smoke sensor is faulty.
l The monitoring equipment is faulty.
Procedure
Step 1 Check whether the smoke alarm configuration is consistent with the configuration plan.
If... Then...
The smoke alarm configuration is consistent with the Go to the next step.
configuration plan
The smoke alarm configuration is inconsistent with the Set the smoke alarm correctly.
configuration plan
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 is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is connected correctly Go to Step 4.
Step 4 Rectify the fault on the sensor.
Step 5 Check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 591
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Go to Step 6.
Step 6 Rectify the fault on the monitoring equipment.
----End
Related Information
None.
4.2.336 ODC_SURGE_PORTECTION_FAIL
Description
The ODC_SURGE_PROTECTION_FAIL alarm indicates that the surge protection function
of an cabinet is abnormal.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the surge protector.
l 0x01: AC surge protector
l 0x02: DC surge protector
Impact on the System
The AC surge protection function of the cabinet is disabled.
Possible Causes
Possible causes of this alarm are as follows:
l The surge protection alarm configuration is inconsistent with the configuration plan.
l The cable between the lightning sensor and the monitoring equipment is connected
incorrectly.
l The lightning sensor is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 592
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The surge protector is faulty.
l The monitoring equipment is faulty.
Procedure
Step 1 Check whether the surge protection alarm configuration is inconsistent with the configuration
plan.
If... Then...
The surge protection alarm configuration is consistent Go to the next step.
with the configuration plan
The surge protection alarm configuration is Configure the surge protection
inconsistent with the configuration plan alarm correctly.
Step 2 Check the cable between the lightning sensor and the monitoring equipment.
If... Then...
The cable is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is functioning properly Go to the next step.
Step 3 Rectify the fault on the lightning sensor.
Step 4 Check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 5 Check whether the alarm output terminal of the surge protector is properly functioning.
If... Then...
The alarm output terminal is properly functioning Go to the next step.
The alarm output terminal is not properly functioning Replace the surge protector.
Step 6 Rectify the fault on the monitoring equipment.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 593
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.337 ODC_TEC_ALM
Description
The ODC_TEC_ALM alarm indicates that the TEC air conditioning module in the cabinet is
not properly functioning.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The temperature of the storage battery is out of range, and therefore it fails to operate safely.
Possible Causes
Possible causes of this alarm are as follows:
l The TEC air conditioning module is incorrectly connected.
l The TEC air conditioning module is faulty.
l The monitoring equipment is faulty.
Procedure
Step 1 Connect the TEC air conditioning module correctly.
Step 2 Replace the TEC air conditioning module.
Step 3 Rectify the fault on the monitoring equipment.
----End
Related Information
None.
4.2.338 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 out of range.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 594
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The temperature is higher than the upper threshold.
l 0x02: The temperature is lower than the lower threshold.
Parameter 2 Indicates the temperature type.
l 0x01: The temperature at the air exhaust vent is out of range.
l 0x0b: Ambient temperature 1 is out of range.
l 0x0c: Ambient temperature 2 is out of range.
l 0x0d: The battery group temperature is out of range.
Impact on the System
The equipment performance deteriorates, and the life of the equipment is shortened.
Possible Causes
Possible causes of this alarm are as follows:
l The temperature thresholds are set to inappropriate values.
l The cable between the temperature sensor and the monitoring equipment is connected
incorrectly.
l The temperature sensor is faulty.
l The monitoring equipment is faulty.
Procedure
Step 1 Check whether the temperature thresholds are appropriate according to the configuration plan.
If... Then...
The temperature thresholds are set to Go to the next step.
appropriate values
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 595
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The temperature thresholds are set to Set the temperature thresholds to
inappropriate values appropriate values.
Step 2 Check the cable between the temperature sensor and the monitoring equipment.
If... Then...
The cable is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is properly functioning Go to the next step.
Step 3 Check whether the temperature sensor is faulty. If the temperature sensor is faulty, replace it.
Step 4 Check whether the alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 5 Rectify the fault on the monitoring equipment.
----End
Related Information
None.
4.2.339 ODC_WATER_ALM
Description
The ODC_WATER_ALM alarm indicates that water enters an cabinet.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None.
Impact on the System
The moisture in the cabinet increases, and the equipment in the cabinet may be damaged.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 596
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l The water alarm configuration is incorrect.
l Water enters the cabinet.
l The cable between the water sensor and the monitoring equipment is connected
incorrectly.
l The water sensor is faulty.
l The associated monitoring equipment is faulty.
Procedure
Step 1 Check whether the water alarm configuration is consistent with the configuration plan.
If... Then...
The water alarm configuration is consistent with the Go to the next step.
configuration plan
The water alarm configuration is inconsistent with the Configure the water alarm
configuration plan correctly.
Step 2 Check whether water enters the cabinet. If water enters the cabinet, dry the cabinet
immediately.
Step 3 Check the cable between the water sensor and the monitoring equipment.
If... Then...
The cable is connected incorrectly or loosely Connect the cable correctly and securely.
The cable is deteriorating or damaged Replace the cable.
The cable is properly functioning Go to Step 5.
Step 4 Check whether the water sensor is faulty. If the water sensor is faulty, replace it.
Step 5 Rectify the fault on the monitoring equipment.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 597
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.340 ODUk_LOFLOM
Description
The ODUk_LOFLOM alarm indicates that the frame alignment signal (FAS) and multiframe
alignment signal (MFAS) are abnormal. This alarm is reported when upstream frame header
information and downstream frame header information are inconsistent.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Impact on the System
The services carried by the board are interrupted.
Possible Causes
l Symptom 1: The optical power is abnormal.
The following figure shows details.
Input optical
Report an
1 power is 2 ODUk_LOFLOM alarm
abnormal.
universal line
universal line
board
board
NE 1 NE 2
l Cause 2: The FEC type is inconsistently configured at both ends.
The following figure shows details.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 598
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1 EC type set for 2 FEC type set for
NE 1: FEC NE 2: AFEC
3 The FEC type is inconsistently
configured for ports at both
ends, causing an
ODUk_LOFLOM alarm.
universal line
universal line
board
board
NE 1 NE 2
FEC type set for the port
FEC
AFEC
l Cause 3: The signals received by the local board contain too many bit errors.
l Cause 4: The optical transmission line is abnormal.
Procedure
l Check whether the peer NE reports the alarm. If the peer NE also reports the alarm,
check for the NE that first reports the alarm along the signal flow. If the peer NE does
not report the alarm, the local NE first reports the alarm.
l Symptom 1: The optical power is abnormal.
a. Check whether input optical power is within the normal range on the NE that first
reports the alarm. For board optical power indicators, see "Technical Specifications"
in the Hardware Description. If the input optical power is abnormal, refer to the
handling method for the IN_PWR_HIGH or IN_PWR_LOW alarm.
b. If the alarm persists, go to Cause 2.
l Cause 2: The FEC type is inconsistently configured at both ends.
a. Check whether the FEC type is consistently configured on interconnected boards. If
the configurations are inconsistent, rectify the configurations.
b. If the alarm persists, go to Cause 3.
l Cause 3: The signals received by the local board contain too many bit errors.
a. On the NMS, query the performance value of BIP8 errors in signals received by the
local board. If too many BIP8 errors exist, refer to the handling method of the
OTUk_DEG alarm.
b. If the alarm persists, go to Cause 4.
l Cause 4: The optical transmission line is abnormal.
a. Clean fiber connectors. For details, see Cleaning the Optical Fiber Connector.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 599
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
b. If the alarm persists, contact Huawei technical support personnel to handle the
alarm.
----End
Related Information
None
4.2.341 ODUk_PM_AIS
Description
The ODUk_PM_AIS alarm indicates that an NE receives an ODUk PM alarm indication
signal (AIS). When detecting a signal fail (SF) condition, an NE sends an AIS signal to its
downstream NE. Upon receiving the AIS signal, the downstream NE reports an
ODUk_PM_AIS alarm.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
The signal quality of services carried on the optical port that reports an ODUk_PM_AIS
alarm deteriorates.
Possible Causes
l Cause 1: Signals received contain an ODUk_PM_AIS signal.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When detecting an ODUk_PM_AIS signal in signals
received, the board of NE 1 reports an ODUk_PM_AIS alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 600
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2 The board of NE 1 reports an
ODUk_PM_AIS alarm.
1
Signals received contain
an ODUk_PM_AIS signal.
universal line
universal line
board
board
NE1 NE2
l Cause 2: The opposite board directly connected to the NE that reports an
ODUk_PM_AIS alarm reported an ODUk_PM_AIS, OTU_LOF, OTU_LOM, or
R_LOS alarm.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When the board of NE 1 detects an ODUk_PM_AIS,
OTU_LOF, OTU_LOM, or R_LOS alarm signal in signals received on the client side,
NE 1 sends an AIS signal to NE 2. When detecting the AIS signal, the board of NE 2
reports an ODUk_PM_AIS alarm.
1 The board of NE 1 detects
an ODUk_PM_AIS, OTU_LOF, 3 The board of NE 2 reports an
OTU_LOM, or R_LOS alarm signal. ODUk_PM_AIS alarm.
2 NE 1 sends an
AIS signal to NE 2.
universal line
universal line
board
board
NE1 NE2
l Cause 3: The board reporting an ODUk_PM_AIS alarm reported an OTU_LOF,
OTU_LOM, or R_LOS alarm.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When detecting an OTU_LOF, OTU_LOM, or R_LOS
alarm signal, the board of NE 2 reports an ODUk_PM_AIS alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 601
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
The board of NE 2 detects an
OTU_LOF, OTU_LOM, or R_LOS alarm signal
and reports an ODUk_PM_AIS alarm.
universal line
universal line
board
board
NE1 NE2
l Cause 4: The board reporting an ODUk_PM_AIS alarm is faulty.
Procedure
Step 1 Cause 1: Signals received contain an ODUk_PM_AIS signal.
1. Check whether the alarm is reported. If the alarm is reported, perform a hardware
loopback on the transmit and receive optical ports. For details, see Hardware Loopback.
A hardware loopback interrupts services.
2. Check whether the alarm is cleared. If the alarm persists, the board reporting the alarm is
faulty; in this case, go to Step 4. If the alarm is cleared, signals received on the client
side of the NE contain an ODUk_PM_AIS signal; in this case, rectify the fault in the
received signals.
Step 2 Cause 2: The opposite board directly connected to the NE that reports an ODUk_PM_AIS
alarm reported an ODUk_PM_AIS, OTU_LOF, OTU_LOM, or R_LOS alarm.
1. On the NMS, check for an ODUk_PM_AIS, 4.2.420 R_LOS, 4.2.362 OTUk_LOF, or
4.2.363 OTUk_LOM alarm on the upstream board that directly connects to the NE
reporting an ODUk_PM_AIS alarm. If the board reports any such alarms, clear these
alarms.
2. Check whether the ODUk_PM_AIS alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The board reporting an ODUk_PM_AIS alarm reported an OTU_LOF, OTU_LOM,
or R_LOS alarm.
1. On the NMS, check for an 4.2.420 R_LOS, 4.2.362 OTUk_LOF, or 4.2.363
OTUk_LOM alarm on the board that reports an ODUk_PM_AIS alarm. If the board
reports any such alarms, clear these alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 602
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the ODUk_PM_AIS alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The board reporting an ODUk_PM_AIS alarm is faulty.
1. Check whether a pluggable optical module is installed on the board. If yes, replace the
pluggable optical module; if no, replace the board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
4.2.342 ODUk_PM_BDI
Description
The ODUk_PM_BDI alarm indicates that an NE receives an ODUk PM backward defect
indication (BDI). When detecting a signal fail (SF) condition using the PM field, an NE sends
a BDI signal (all bits of the BDI byte are "1") to its upstream NE. Upon receiving the BDI
signal, the upstream NE reports an ODUk_PM_BDI alarm.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
The signal quality of services carried on the optical port that reports an ODUk_PM_BDI
alarm deteriorates.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: Signals received contain an ODUk_PM_BDI signal.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When detecting an ODUk_PM_BDI signal in signals
received, the board of NE 1 reports an ODUk_PM_BDI alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 603
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2 The board of NE 1 reports
an ODUk_PM_BDI alarm.
1
Signals received contain
an ODUk_PM_BDI signal.
universal line
universal line
board
board
NE1 NE2
l Cause 2: The opposite board directly connected to the NE that reports an
ODUk_PM_BDI alarm reported an ODUk_PM_LCK, ODUk_PM_OCI,
ODUk_PM_SSF, ODUk_PM_TIM, OTU_LOF, OTU_LOM, or R_LOS alarm.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When the board of NE 2 detects an ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_SSF, ODUk_PM_TIM, OTU_LOF, OTU_LOM, or
R_LOS alarm signal, NE 2 sends a BDI signal to NE 1. When detecting the BDI signal,
the board of NE 1 reports an ODUk_PM_BDI alarm.
1 The board of NE 2 detects an ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_SSF, ODUk_PM_TIM,
OTU_LOF, OTU_LOM, or R_LOS alarm.
universal line
universal line
board
board
2 NE 2 sends a BDI
signal to NE 1.
NE1 NE2
3 The board of NE 1 reports an
ODUk_PM_BDI alarm.
l Cause 3: The board reporting an ODUk_PM_BDI alarm is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 604
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Cause 1: Signals received contain an ODUk_PM_BDI signal.
1. Check whether the alarm is reported. If the alarm is reported, perform a hardware
loopback on the transmit and receive optical ports. For details, see Hardware Loopback.
A hardware loopback interrupts services.
2. Check whether the alarm is cleared. If the alarm persists, the board reporting the alarm is
faulty; in this case, go to Step 3. If the alarm is cleared, signals received contain an
ODUk_PM_BDI signal; in this case, rectify the fault in the received signals.
Step 2 Cause 2: The opposite board directly connected to the NE that reports an ODUk_PM_BDI
alarm reported an ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_SSF, ODUk_PM_TIM,
OTU_LOF, OTU_LOM, or R_LOS alarm.
1. On the network management system (NMS), check for an 4.2.420 R_LOS, 4.2.362
OTUk_LOF, 4.2.363 OTUk_LOM, 4.2.344 ODUk_PM_LCK, 4.2.345
ODUk_PM_OCI, 4.2.347 ODUk_PM_TIM, or 4.2.346 ODUk_PM_SSF alarm on the
downstream board that directly connects to the NE reporting an ODUk_PM_BDI alarm.
If the board reports any such alarms, clear these alarms.
2. Check whether the ODUk_PM_BDI alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The board reporting an ODUk_PM_BDI alarm is faulty.
1. Check whether a pluggable optical module is installed on the board. If yes, replace the
pluggable optical module; if no, replace the board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
4.2.343 ODUk_PM_DEG
Description
The ODUk_PM_DEG alarm indicates that an ODUk PM signal degraded. This alarm is
generated if signal degradation occurs or the bit error count exceeds its threshold when BIP8
detection is in burst mode.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 605
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
If this alarm is generated, bit errors are generated in the services carried at the optical port,
which makes the service signals invalid or even unavailable.
Possible Causes
l Cause 1: The input optical power of the board is abnormal.
l Cause 2: The fiber on the transmission line is abnormal.
l Cause 3: The board that reports the alarm is faulty or the board in the upstream station is
faulty.
Procedure
Step 1 Cause 1: The input optical power of the board is abnormal.
1. On the NMS, view the alarms on the entire network to check the slot ID, port ID, and
channel ID of the board that generates this alarm.
2. Along the service signal flow, check whether the input optical power of the optical port
on the board that first generates this alarm is within the permitted range. For board
optical power indicators, see "Technical Specifications" in the Hardware Description.
a. If the input optical power of the board is within the permitted range, check for
abnormal changes in optical power performance history. For details, see Querying
the Optical Power. If no abnormal changes are found, go to Step 2. If any abnormal
changes are found, go to Step 1.3.
b. If the optical power is not within the permitted range, adjust the optical attenuator to
change the input optical power of the board to a proper value.
3. Check whether the alarm is cleared. If the alarm persists, refer to Step 1.2 to
troubleshoot this alarm board by board along the service signal flow.
4. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The fiber on the transmission line is abnormal.
1. check whether the pigtail meets the following requirements:
– The bending radius is not less than 6 cm.
– The fiber connectors are properly installed.
– The fiber connectors are clean.
– The cable is intact.
If the preceding requirements are not met, replace the pigtail. For details, see Cleaning
the Optical Fiber Connector.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 606
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The board that reports the alarm is faulty or the board in the upstream station is
faulty.
1. Replace the board that reports the alarm or the faulty board in the upstream station. If the
board supports pluggable optical modules, replace the specific pluggable optical
modules. For details, see Replacing the Optical Module. If the board does not support
pluggable optical modules, replace the board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei to handle the
alarm.
----End
Related Information
None
4.2.344 ODUk_PM_LCK
Description
The ODUk_PM_LCK alarm indicates that ODUk PM signals are locked. The LCK function
is used to lock signals of a desired user access point during testing. When the signals of an
access point are locked, the value of the STAT byte is 101 and an ODUk_PM_LCK alarm is
reported.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
Services carried by the optical port are interrupted.
Possible Causes
The signals of an access point are manually locked to test the associated fiber line.
Procedure
Step 1 On the NMS, locate the board that reports an ODUk_PM_LCK alarm by querying its slot ID,
optical port ID, and channel ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 607
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Set LCK Insertion to Disabled on the board, to prevent insertion of an LCK signal to
downstream NEs.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
None
4.2.345 ODUk_PM_OCI
Description
The ODUk_PM_OCI alarm indicates an ODUk PM open connection. An optical port on an
NE reports an ODUk_PM_OCI alarm when its signal output end is not connected to its signal
input end and the value of the STAT byte is "110".
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
Services carried on the optical port that reports an ODUk_PM_OCI alarm are interrupted.
Possible Causes
l Cause 1: An board on an upstream NE of the NE that reports an ODUk_PM_OCI alarm
reported an ODUk_PM_OCI alarm.
The following figure shows details. Traffic flows from NE 1 to NE 2. Upon detecting
that an board on an upstream NE 1 detects an ODUk_PM_OCI alarm signal, the board of
NE 2 reports an ODUk_PM_OCI alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 608
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1 An board of an upstream NE 2 The board on NE k reports
detects an ODUk_PM_OCI an ODUk_PM_OCI alarm.
alarm signal.
universal line
universal line
board
board
NE1 NE2
l Cause 2: A loopback is configured for an board on the NE that is the service source.
l Cause 3: Cross-connections are not configured for an board on the NE that is the service
source, but non-intrusive monitoring is enabled on the NE that reports an
ODUk_PM_OCI alarm.
Procedure
Step 1 Cause 1: An board on an upstream NE of the NE that reports an ODUk_PM_OCI alarm
reported an ODUk_PM_OCI alarm.
1. Check for an ODUk_PM_OCI alarm on all boards of all upstream NEs. If an board on an
upstream NE reports an ODUk_PM_OCI alarm, find the NE that triggers the
ODUk_PM_OCI alarm based on the traffic direction.
2. Check whether a loopback is configured for the board on the NE that triggers the
ODUk_PM_OCI alarm, and release any configured loopbacks.
3. Check whether the ODUk_PM_OCI alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: A loopback is configured for an board on the NE that is the service source.
1. Check whether a loopback is configured for an board on the NE that is the service
source, and release any configured loopbacks.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Cross-connections are not configured for an board on the NE that is the service
source, but non-intrusive monitoring is enabled on the NE that reports an ODUk_PM_OCI
alarm.
1. Check whether cross-connections are configured for an board on the NE that is the
service source. If no cross-connections are configured and cross-connections do not need
to be configured, disable non-intrusive monitoring on the NE. If no cross-connections are
configured but cross-connections must be configured, configure cross-connections for
the board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 609
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.346 ODUk_PM_SSF
Description
The ODUk_PM_SSF alarm indicates that signals fail at the ODUk PM server layer.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
Services carried on the channel that reports an ODUk_PM_SSF alarm are interrupted.
Possible Causes
l An ODUk_PM_AIS or OTUk_TIM alarm is reported on the NE that reports an
ODUk_PM_SSF alarm.
Procedure
Step 1 Check information about the ODUk_PM_SSF alarm on the NMS, and find the channel
reporting the ODUk_PM_SSF alarm and the optical port housing the channel.
Step 2 Check for an 4.2.341 ODUk_PM_AIS or 4.2.365 OTUk_TIM alarm on the NE housing the
optical port. If the NE reported any such alarms, clear these alarms.
Step 3 Check whether the ODUk_PM_SSF alarm is cleared. If the alarm persists, contact Huawei
engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 610
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.347 ODUk_PM_TIM
Description
The ODUk_PM_TIM alarm indicates ODUk PM trace identifier mismatch. This alarm is
reported if the trace identifier mismatch (TIM) detection function is enabled and the trace
identifier at the local end and that at the peer end do not match during control processing.
k indicates the level of rate, its value is 0, 1, 2, 3, or flex.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
Quality of the services carried by the optical port deteriorates, and the services may be
unavailable.
Possible Causes
l Cause 1: The configured TIM detection mode is not applicable to the networking
topology.
l Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI
received at the local end.
l Cause 3: Fiber connections are incorrect.
l Cause 4: Cross-connections are incorrectly configured.
Procedure
Step 1 Cause 1: The configured TIM detection mode is not applicable to the networking topology.
1. On the NMS, query the TIM detection mode of the local NE. If the TIM detection mode
is not applicable to the networking topology, rectify the configurations.
– For the point-to-point topology, only the SAPI (Source Access Point Identifier) is
compared for the sink of trail termination.
– For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
– For the multipoint-to-multipoint topology, only the DAPI (Destination Access Point
Identifier) is compared for the sink of trail termination.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI received at
the local end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 611
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. On the NMS, query whether the TTI sent by the peer end and that received at the local
end are the same. If the two TTIs are different, query the TTI received by the local NE
on the NMS. Re-configure the SAPI and the DAPI of the TTI for the local NE to ensure
that the two TTIs are the same.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Fiber connections are incorrect.
1. Check whether the fiber connections between the local optical port and peer optical port
are correct. If the fiber connections are incorrect, connect the fibers correctly.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: Cross-connections are incorrectly configured.
1. Check whether the cross-connections are correctly configured. If the configurations are
incorrect, rectify the configurations.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
4.2.348 ODUk_TCMn_AIS
Description
ODUk TCMn alarm indication signal. An AIS signal is transmitted to the downstream,
indicating that a signal is failed in the upstream. The alarm is generated when the STAT byte
value is "111".
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, the services carried at the optical port are unavailable.
Possible Causes
l Signals input from the client side contain the ODUk_TCMn_AIS signal.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 612
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The corresponding board at the peer end transmits the ODUk_TCMn_AIS signals.
l The loopback or cross-connection is set at the upstream station, and the FEC type is
incorrectly configured.
Procedure
Step 1 On the NMS, query whether there is any OTUk-level alarm on the board. If there is, handle
the alarm.
Step 2 Query whether the alarm is reported from the client side. If it is, check the equipment on the
client side.
Step 3 On the NMS, query whether the 4.2.348 ODUk_TCMn_AIS, 4.2.420 R_LOS, or 4.2.419
R_LOF, alarm exists on the client side of the board at the peer end. If the alarm exists, check
the equipment at the peer end.
Step 4 On the NMS, query whether the loopback is set on the upstream station. If it is, release the
loopback of the upstream station.
Step 5 Check whether the configuration of the cross-connection and FEC type at the upstream station
is correct. If the configuration is incorrect, modify the configuration.
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.349 ODUk_TCMn_BDI
Description
ODUk TCMn backward defect indication. This alarm is generated when five consecutive BDI
bytes in the TCMn overhead field are "1".
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, bit errors occur at the downstream station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 613
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
l Signals input from the client side contain the ODUk_TCMn_BDI signal.
l The corresponding OTU board at the downstream station receives the ODUk_LOFLOM,
ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or
ODUk_TCMn_SSF alarm.
Procedure
Step 1 On the NMS, query whether there is any OTUk-level alarm on the board. If there is, handle
the alarm.
Step 2 Check whether the corresponding OTU board at the downstream station receives the 4.2.340
ODUk_LOFLOM, 4.2.348 ODUk_TCMn_AIS, 4.2.351 ODUk_TCMn_LCK, 4.2.352
ODUk_TCMn_LTC, 4.2.353 ODUk_TCMn_OCI, or 4.2.354 ODUk_TCMn_SSF alarm
on the NMS. If it does, handle the corresponding alarm at the downstream station.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.350 ODUk_TCMn_DEG
Description
ODUk TCMn signal being degraded. This alarm is generated if signal degradation occurs or
the bit error count exceeds the threshold when the error detection is in burst mode.
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, the services at the optical interface generate bit errors, which make
the service signals unavailable.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 614
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
l The optical interface that reports the alarm is faulty.
l The optical interface at the peer end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 On the NMS, browse alarms of the entire network to determine the slot ID, interface ID, and
channel ID of the board that generates this alarm.
Step 2 Locate the point that first generates the ODUk_TCMn_DEG alarm according to the service
route.
Step 3 Check whether the input optical power of the place where the alarm is first generated is within
the permitted range on the NMS. If it is not, handle the alarm according to the handling
procedures of the 4.2.178 IN_PWR_HIGH and 4.2.179 IN_PWR_LOW alarms.
Step 4 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 6 cm.
l The optical interface connector is well inserted.
l The fiber connector is clean.
l The cable is intact.
If the preceding requirements are not met, clean the fiber connector or replace the fiber. For
details, see Cleaning the Optical Fiber Connector.
Step 5 If the alarm persists, the optical interface on the board at the local end may be faulty. Replace
the pluggable optical module or the faulty board.
Step 6 If the alarm persists, the optical interface on the universal line board at the peer end may be
faulty. Replace the pluggable optical module on the board or the faulty OTU board.
Step 7 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
None
4.2.351 ODUk_TCMn_LCK
Description
ODUk TCMn signal being locked. The maintenance signal LCK byte required by the carrier
is used to lock the access point signal of users during testing. It can be generated when the
server layer adapts the source and sink. The alarm is generated when the STAT byte value is
"101" during locking.
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 615
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, the services carried at the optical port are unavailable.
Possible Causes
The current line signals are being tested.
Procedure
Step 1 On the NMS, query and locate the slot ID, port ID, and channel ID of the board that generates
this alarm.
Step 2 Set the LCK type to Disabled if it is Enabled.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.352 ODUk_TCMn_LTC
Description
Loss of ODUk TCMn serial connection. The TCM provides the connection monitoring
function of the ODUk to cater for different application scenarios. For example, the TCM from
optical network node interface (NNI) to optical network node interface (NNI) monitors the
connection of the ODUk through the carrier network. This alarm is generated when the serial
connection is lost and the STAT byte is "000".
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 616
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
If the alarm is generated, the TCM is not available.
Possible Causes
The TCM at the peer end is not set as enabled, and there is no TCM source.
Procedure
Step 1 On the NMS, find the position that generates this alarm first according to the logical fibers
topology.
Step 2 Query whether the configuration of the position and its peer position is correct. If not, modify
the configuration.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.353 ODUk_TCMn_OCI
Description
Indication for an ODUk TCMn open connection indication. This alarm is generated when the
output port is not connected to the input port and the STAT byte is "110".
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, the services carried at the optical port are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 617
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
l The corresponding board at the upstream station has the ODUk_TCMn_OCI alarm.
l There is a loopback on the corresponding board at the peer station.
l The corresponding board at the peer station has no or incorrect cross-connection
configuration.
Procedure
Step 1 On the NMS, query whether there is an alarm with a higher severity on the board. If there is,
handle the alarm with a higher severity.
Step 2 If the alarm persists, check whether the upstream station generates this alarm. If this alarm is
generated, locate the station that triggers this alarm according to the service route.
Step 3 Check whether the corresponding board of the station that triggers this alarm has any
loopback. If a loopback is found, release the loopback.
Step 4 If the alarm persists, check whether a cross-connection is correctly configured for the
corresponding board of the station that triggers this alarm. If it is not, configure the correct
cross-connection.
Step 5 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.354 ODUk_TCMn_SSF
Description
Failure of ODUk TCMn server-layer signals.
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, services are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 618
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
l The ODUk_TCMn_AIS or ODUk_LOFLOM alarm is generated on the line.
l The OTUk_TIM alarm is generated on the line and the OTUk_TIM follow-up response
is set to enabled.
l The OTUk_SSF alarm is generated on the line.
Procedure
Step 1 Check along the service signal flow to locate the station that first generates the SSF alarm.
1. Check whether the 4.2.348 ODUk_TCMn_AIS or 4.2.340 ODUk_LOFLOM alarm
occurs at the station. If it does, clear the alarm according to the corresponding handling
procedure.
2. Check whether the 4.2.365 OTUk_TIM alarm occurs at the station. If it does, clear the
alarm according to the alarm handling procedure.
Step 2 If the alarm persists, check whether the 4.2.364 OTUk_SSF alarm occurs on the line. If it
does, clear the alarm according to the alarm handling procedure.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.355 ODUk_TCMn_TIM
Description
ODUk TCMn trace identifier mismatch. This alarm is generated during control process when
the trail trace identifier at the peer end mismatches that at the local end when the TIM
detection is enabled.
l k indicates the level of rate, its value is 0, 1, or 2.
l n indicates the level of TCM, its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, the quality of the signals at the optical port is degraded. As a result,
the service signals may be unavailable.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 619
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
l Cause 1: The configured TIM detection mode is not applicable to the networking
topology.
l Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI
received at the local end.
l Cause 3: Fiber connections are incorrect.
l Cause 4: Cross-connections are incorrectly configured.
Procedure
Step 1 Cause 1: The configured TIM detection mode is not applicable to the networking topology.
1. On the NMS, query the TIM detection mode of the local NE. If the TIM detection mode
is not applicable to the networking topology, rectify the configurations.
– For the point-to-point topology, only the SAPI (Source Access Point Identifier) is
compared for the sink of trail termination.
– For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
– For the multipoint-to-multipoint topology, only the DAPI (Destination Access Point
Identifier) is compared for the sink of trail termination.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI received at
the local end.
1. On the NMS, query whether the TTI sent by the peer end and that received at the local
end are the same. If the two TTIs are different, query the TTI received by the local NE
on the NMS. Re-configure the SAPI and the DAPI of the TTI for the local NE to ensure
that the two TTIs are the same.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Fiber connections are incorrect.
1. Check whether the fiber connections between the local optical port and peer optical port
are correct. If the fiber connections are incorrect, connect the fibers correctly.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: Cross-connections are incorrectly configured.
1. Check whether the cross-connections are correctly configured. If the configurations are
incorrect, rectify the configurations.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 620
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.356 OOL
Description
The OOL alarm indicating that the phase-locked loop (PLL) on the cross-connect board is
out-of-loop.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of failed PLL.
l 0x01: first 2M PLL
l 0x02: second 2M PLL
l 0x03: 38M analog PLL
l 0x04: 77M PLL on the alarmed board
l 0x05: 77M PLL on the board in the extended slot
Impact on the System
The phase-locked loop cannot lock the input signals and outputs poor clock signals. As a
result, quality of services deteriorates or even services are interrupted.
Possible Causes
The possible cause of the OOL alarm is as follows:
The phase-locked loop is damaged.
Procedure
Step 1 Check whether the active clock board reports the OOL alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 621
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The active clock board reports the OOL Perform switching from the active clock
alarm board to a standby clock board and check
whether the alarm is cleared. If the alarm
persists, go to the next step.
A standby clock board reports the OOL Go to the next step.
alarm
Step 2 Replace the board that reports the alarm. The alarm is cleared automatically.
----End
Related Information
None.
4.2.357 OPU1_MSIM
Description
OPU1 multiplex structure identifier mismatch.
k indicates the level of rate, its value is 0, 1, 2, or 3.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
The services may be unavailable.
Possible Causes
The board does not support the multiplex structure for service transmission of the board on
the source NE.
Procedure
Step 1 Check whether the multiplex structure of the local board mismatches that of the
corresponding board on the source NE.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 622
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 If the multiplex structures of the two boards do not match, replace one of them with a
matched board.
----End
Related Information
None
4.2.358 OPUk_PLM
Description
The OPUk_PLM alarm indicates OPUk payload mismatch. This alarm is reported if the
payload type in the received signals differs from that defined in the adaptation function.
k indicates the level of rate, its value is 0, 1, 2, or 3.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
Services are unavailable.
Possible Causes
l Cause 1: Fiber connections are incorrect.
l Cause 2: The client-side service type of the local board and that of the peer board are
different.
Procedure
Step 1 Cause 1: Fiber connections are incorrect.
1. Check whether the fiber connections are correct according to the engineering fiber
connection diagram. If the fiber connections are incorrect, re-connect fibers according to
the engineering fiber connection diagram.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The client-side service type of the local board and that of the peer board are
different.
1. Check whether the client-side service type is consistently set for the local board and peer
board. If the two service types are different, set them consistently based on the network
plan.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 623
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
None
4.2.359 OTUk_AIS
Description
The OTUk_AIS alarm indicates that an NE receives an ODUk alarm indication signal (AIS).
When detecting a signal fail (SF) condition, an NE sends an AIS signal to its downstream NE.
Upon receiving the AIS signal, the downstream NE reports an OTUk_AIS alarm.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
The signal quality of services carried on the optical port that reports an OTUk_AIS alarm
deteriorates.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: Signals received contain an ODUk_PM_AIS or OTUk_AIS signal.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When detecting an ODUk_PM_AIS or OTUk_AIS
signal in signals received, the board of NE 1 reports an OTUk_AIS alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 624
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2 The board of NE 1 reports an
OTUk_AIS alarm.
1
Signals received contain an
ODUk_PM_AIS or OTUk_AIS
signal.
universal line
universal line
board
board
NE1 NE2
l Cause 2: A loopback or incorrect cross-connections are configured for the upstream
board that directly connects to the NE reporting an OTUk_AIS alarm.
l Cause 3: An incorrect forward error correction (FEC) type is configured for the board
reporting an OTUk_AIS alarm.
Procedure
Step 1 Cause 1: Signals received contain an ODUk_PM_AIS or OTUk_AIS signal.
1. Check whether signals received contain an ODUk_PM_AIS or OTUk_AIS signal. If the
signals contain an ODUk_PM_AIS or OTUk_AIS signal, rectify the fault in the signals.
2. Check whether the OTUk_AIS alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: A loopback or incorrect cross-connections are configured for the upstream board that
directly connects to the NE reporting an OTUk_AIS alarm.
1. Check whether a loopback is configured for the upstream board, and release any
configured loopbacks.
2. Check whether cross-connections configured for the upstream board are correct, and
correct any incorrect configurations.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: An incorrect forward error correction (FEC) type is configured for the board
reporting an OTUk_AIS alarm.
1. On the NMS, check whether the physical board and its logical board have the same FEC
type. If they have different FEC types, modify configurations to ensure that they have the
same FEC type. For information about FEC types, see the Hardware Description.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 625
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.360 OTUk_BDI
Description
The OTUk_BDI alarm indicates that an NE receives an OTUk backward defect indication
(BDI). When detecting a signal fail (SF) condition using the section monitoring (SM) field, an
NE sends a BDI signal (all bits of the BDI byte are "1") to its upstream NE. Upon receiving
the BDI signal, the upstream NE reports an OTUk_BDI alarm.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
The signal quality of services carried on the optical port that reports an OTUk_BDI alarm
deteriorates.
Possible Causes
l Cause 1: Signals received contain an OTUk_BDI signal.
The following figure shows details. NE 1 and NE 2 interconnect with each other, and
traffic flows from NE 1 to NE 2. When detecting an OTUk_BDI signal in signals
received, the board of NE 1 reports an OTUk_BDI alarm.
2 The board of NE 1 reports an
OTUk_BDI alarm.
1
Signals received contain
an OTUk_BDI signal.
universal line
universal line
board
board
NE1 NE2
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 626
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 2: An board on a downstream NE of the NE that reports an OTUk_BDI alarm
reported an OTUk_AIS, OTUk_LOF, OTUk_LOM, OTUk_SSF, or OTUk_TIM alarm.
The following figure shows details. Traffic flows from NE 1 to NE k. When an board on
a downstream NE of NE 1 detects an OTUk_AIS, OTUk_LOF, OTUk_LOM,
OTUk_SSF, or OTUk_TIM alarm signal, the downstream NE sends a BDI signal to NE
1. When detecting the BDI signal, the board of NE 1 reports an OTUk_BDI alarm.
1 An board of NE2 detects an OTUk_AIS, OTUk_LOF,
OTUk_LOM, OTUk_SSF, or OTUk_TIM alarm.
universal line
universal line
board
board
A BDI signal is
sent to NE 1.
NE1 NE2
2 The board of NE 1 reports
an OTUk_BDI alarm.
Procedure
Step 1 Cause 1: Signals received contain an OTUk_BDI signal.
1. Check whether signals received contain an OTUk_BDI signal. If the signals contain an
OTUk_BDI signal, rectify the fault in the signals.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: An board on a downstream NE of the NE that reports an OTUk_BDI alarm reported
an OTUk_AIS, OTUk_LOF, OTUk_LOM, OTUk_SSF, or OTUk_TIM alarm.
1. On the NMS, check for an 4.2.362 OTUk_LOF, 4.2.363 OTUk_LOM, 4.2.359
OTUk_AIS, 4.2.365 OTUk_TIM, or 4.2.364 OTUk_SSF alarm on each downstream
board. If a downstream board reports any such alarms, clear these alarms.
2. Check whether the OTUk_BDI alarm is cleared. If the alarm persists, contact Huawei
engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 627
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.361 OTUk_DEG
Description
The OTUk_DEG alarm indicates that an OTUk signal is degraded. This alarm is generated if
signal degradation occurs or the bit error count exceeds its threshold when BIP8 detection is
in burst mode.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
If the alarm is generated, the services at the optical port have bit errors, which make the
service signals invalid or even unavailable.
Possible Causes
l Cause 1: The optical port at the local end is faulty.
l Cause 2: The fiber on the transmission line is abnormal.
l Cause 3: The board is faulty.
Procedure
Step 1 Cause 1: The optical port at the local end is faulty.
1. Query the board that reports the alarm on the NMS.
2. Check whether the input optical power of the board is within the permitted range. For
board optical power indicators, see "Technical Specifications" in the Hardware
Description. If the optical power is not within the permitted range, see 4.2.178
IN_PWR_HIGH and 4.2.179 IN_PWR_LOW for troubleshooting.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The fiber on the transmission line is abnormal.
1. Check whether the fiber meets the following requirements:
– The bending radius is not less than 6 cm.
– The optical interface connector is well inserted.
– The fiber connector is clean.
– The cable is intact.
If the preceding requirements are not met, clean the fiber connector or replace the fiber.
For details, see Cleaning the Optical Fiber Connector.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 628
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The board is faulty.
1. Replace the board that reports the alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei to handle the
alarm.
----End
Related Information
None
4.2.362 OTUk_LOF
Description
The OTUK_LOF alarm indicates that the frame alignment signal (FAS) is abnormal. This
alarm is reported if the out of frame (OOF) state lasts for three consecutive milliseconds
during frame alignment processing.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Impact on the System
Services are interrupted on the board that reports an OTUk_LOF alarm.
Possible Causes
l Cause 1: The FEC type is inconsistently configured at both ends.
The following figure shows details.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 629
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1 FEC type set for 2 FEC type set for
NE 1: FEC NE 2: AFEC
3 The FEC type is inconsistently
configured for ports at both
ends, causing an OTUk_LOF
alarm.
universal line
universal line
board
board
NE 1 NE 2
FEC type set for the port
FEC
AFEC
l Cause 2: The board that reports the alarm is faulty.
l Cause 3: The receive optical power of the local board is abnormal.
The following figure shows details.
Input optical
Report an OTUk_LOF
1 power is 2 alarm
abnormal.
universal line
universal line
board
board
NE 1 NE 2
l Cause 4: The optical transmission line is abnormal.
Procedure
Step 1 Cause 1: The FEC type is inconsistently configured at both ends.
1. Check whether the FEC type is consistently configured on interconnected boards. If the
configurations are inconsistent, rectify the configurations.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 630
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. If the alarm persists, go to Cause 2.
Step 2 Cause 2: The board that reports the alarm is faulty.
1. The board that reports the OTUK_LOF alarm is faulty.
If... Then...
The board supports pluggable optical Replace pluggable optical modules. For
modules details, see Replacing the Optical
Module. If the alarm persists, replace the
faulty board.
The board does not support pluggable Reset the board. For details, see Resetting
optical modules Boards.
If the alarm persists, replace the faulty
board.
2. If the alarm persists, go to Cause 3.
Step 3 Cause 3: The receive optical power of the local board is abnormal.
1. Check whether input optical power is within the normal range on the NE that first reports
the alarm. If the input optical power is abnormal, refer to the handling method for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
2. If the alarm persists, go to Cause 4.
Step 4 Cause 4: The optical transmission line is abnormal.
1. Clean fiber connectors. For details, see Cleaning the Optical Fiber Connector.
2. If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None
4.2.363 OTUk_LOM
Description
The OTUK_LOM alarm indicates that the multiframe alignment signal (MFAS) is abnormal.
This alarm is reported if out of multiframe (OOM) state lasts for three consecutive
milliseconds during multiframe alignment processing.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 631
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
Service quality is affected.
Possible Causes
l Cause 1: The FEC type is inconsistently configured at both ends.
The following figure shows details.
1 FEC type set for 2 Port FEC type set
NE 1: FEC for NE 2: AFEC
3 The FEC type is inconsistently
configured for ports at both
ends, causing an OTUk_LOM
alarm.
universal line
universal line
board
board
NE 1 NE 2
FEC type set for the port
FEC
AFEC
l Cause 2: The signals received by the local universal line board contain too many bit
errors.
l Cause 3: The local board is faulty.
Procedure
Step 1 Cause 1: The FEC type is inconsistently configured at both ends.
1. Check whether the FEC type is consistently configured on interconnected boards. If the
configurations are inconsistent, rectify the configurations.
2. If the alarm persists, go to Cause 2.
Step 2 Cause 2: The signals received by the local universal line board contain too many bit errors.
1. On the NMS, query the performance value of BIP8 errors in signals received by the local
board. If too many BIP8 errors exist, refer to the handling method of the OTUk_DEG
alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 632
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. If the alarm persists, go to Cause 3.
Step 3 Cause 3: The local board is faulty.
1. The board that reports the OTUK_LOM alarm is faulty.
If... Then...
The board supports pluggable optical Replace pluggable optical modules. For
modules details, see Replacing the Optical
Module. If the alarm persists, replace the
faulty board.
The board does not support pluggable Reset the board. For details, see Resetting
optical modules Boards.
If the alarm persists, replace the faulty
board.
2. If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None
4.2.364 OTUk_SSF
Description
The OTUk_SSF alarm indicates that signals fail at the OTUk server layer.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Impact on the System
Services carried on the channel that reports an OTUk_SSF alarm are interrupted.
Possible Causes
An OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm is reported on the NE that reports an
OTUk_SSF alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 633
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check for an 4.2.359 OTUk_AIS, 4.2.362 OTUk_LOF, or 4.2.363 OTUk_LOM alarm on
the NE housing the optical port. If the NE reported any such alarms, clear these alarms.
Step 2 Check whether the OTUk_SSF alarm is cleared. If the alarm persists, contact Huawei
engineers to handle the alarm.
----End
Related Information
None
4.2.365 OTUk_TIM
Description
The OTUk_TIM alarm indicates OTUk trace identifier mismatch. This alarm is reported if the
trace identifier mismatch (TIM) detection function is enabled and the trace identifier at the
local end and that at the peer end do not match.
k indicates the level of rate, its value is 2 or 3.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
Quality of the services carried by the optical port deteriorates, and the services may be
unavailable.
Possible Causes
l Cause 1: The configured TIM detection mode is not applicable to the networking
topology.
l Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI
received at the local end.
l Cause 3: Fiber connections are incorrect.
l Cause 4: Cross-connections are incorrectly configured.
Procedure
Step 1 Cause 1: The configured TIM detection mode is not applicable to the networking topology.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 634
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. On the NMS, query the TIM detection mode of the local NE. If the TIM detection mode
is not applicable to the networking topology, rectify the configurations.
– For the point-to-point topology, only the SAPI (Source Access Point Identifier) is
compared for the sink of trail termination.
– For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
– For the multipoint-to-multipoint topology, only the DAPI (Destination Access Point
Identifier) is compared for the sink of trail termination.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The trail trace identifier (TTI) sent by the peer end differs from the TTI received at
the local end.
1. On the NMS, query whether the TTI sent by the peer end and that received at the local
end are the same. If the two TTIs are different, query the TTI received by the local NE
on the NMS. Re-configure the SAPI and the DAPI of the TTI for the local NE to ensure
that the two TTIs are the same.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Fiber connections are incorrect.
1. Check whether the fiber connections between the local optical port and peer optical port
are correct. If the fiber connections are incorrect, connect the fibers correctly.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: Cross-connections are incorrectly configured.
1. Check whether the cross-connections are correctly configured. If the configurations are
incorrect, rectify the configurations.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
4.2.366 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power of the optical module on
the board is out of range.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 635
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
Service bit errors may occur on the receive side at the opposite end or frames cannot be
aligned at the opposite end. As a result, the services are unavailable, and even are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The optical module is deteriorating.
l The optical module is faulty.
l The board that reports the OUT_PWR_ABN alarm is faulty.
Procedure
Step 1 Using an optical power meter, check whether the transmit optical power of the board is within
the specified range.
If... Then...
The transmit optical power of is out of The optical module is deteriorating or
range faulty. Replace the optical module. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
The transmit optical power of is within the Go to the next step.
specified range
Step 2 Replace the board that reports the OUT_PWR_ABN alarm.
----End
Related Information
None.
4.2.367 OUT_PWR_HIGH
Description
The OUT_PWR_HIGH is an alarm of too high output power. This alarm occurs when a board
detects that the actual output power is higher than the upper threshold of the output power
reference value.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 636
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
Too high output optical power causes damage to the laser or meters at the opposite end and bit
errors in the services.
Possible Causes
l Cause 1: The input optical power is excessively high.
The following figure shows details.
Output optical power is
1 Input optical power 2 excessively high and an
is excessively high. OUT_PWR_HIGH alarm is
reported.
universal line
universal line
board
board
NE 1 NE 2
l Cause 2: The local optical module or board is faulty.
The following figure shows details.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 637
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Because the optical module or board
is faulty, output optical power is
excessively high and an
OUT_PWR_HIGH alarm is reported.
universal line
universal line
board
board
NE 1 NE 2
Optical module fault
Procedure
Step 1 Cause 1: The input optical power is excessively high.
1. On the NMS, check whether an IN_PWR_HIGH alarm is reported. If such an alarm is
reported, clear it.
2. Check whether the OUT_PWR_HIGH alarm is cleared. If the alarm persists, go to
Cause 2.
Step 2 Cause 2: The local optical module or board is faulty.
1. Check whether the board supports pluggable optical modules.
If... Then...
The board supports pluggable optical Replace pluggable optical modules. For
modules details, see Replacing the Optical
Module. If the alarm persists, replace the
faulty board.
The board does not support pluggable Reset the board. For details, see Resetting
optical modules Boards.
If the alarm persists, replace the faulty
board.
2. If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 638
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.368 OUT_PWR_LOW
Description
The OUT_PWR_LOW is an alarm of too low output power. This alarm occurs when a board
detects that the actual output power is lower than the lower threshold of the output power
reference value.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
The output optical power of the laser is excessively low, which influences the normal
transmission of services.
Possible Causes
l Cause 1: The input optical power is excessively low.
The following figure shows details.
Output optical power is
1 Input optical power 2 excessively low and an
is excessively low. OUT_PWR_LOW alarm is
reported.
universal line
universal line
board
board
NE 1 NE 2
l Cause 2: Lasers are aged or board hardware is faulty.
The following figure shows details.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 639
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Because the laser is aged or the
board is faulty, output optical power
is excessively low and an
OUT_PWR_LOW alarm is reported.
universal line
universal line
board
board
NE 1 NE 2
Aged laser
Procedure
Step 1 Cause 1: The input optical power is excessively low.
1. On the NMS, check whether an IN_PWR_LOW alarm is reported. If such an alarm is
reported, clear it.
2. Check whether the OUT_PWR_LOW alarm is cleared. If the alarm persists, go to Cause
2.
Step 2 Cause 2: Lasers are aged or board hardware is faulty.
1. Check whether the board supports pluggable optical modules.
If... Then...
The board supports pluggable optical Replace pluggable optical modules. For
modules details, see Replacing the Optical
Module. If the alarm persists, replace the
faulty board.
The board does not support pluggable Reset the board. For details, see Resetting
optical modules Boards.
If the alarm persists, replace the faulty
board.
2. If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 640
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.369 OUT1TEMP_SENSOR_FAIL
Description
The OUT1TEMP_SENSOR_FAIL alarm indicates that the temperature sensor at the air outlet
fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The equipment cannot collect the temperature data of the air outlet on the TCU.
Possible Causes
Possible causes of the OUT1TEMP_SENSOR_FAIL alarm are as follows:
l The outlet temperature sensor is not installed.
l The outlet temperature sensor is incorrectly connected.
l The outlet temperature sensor is faulty.
l The control board in the cabinet is faulty.
Procedure
Step 1 Check whether the outlet temperature sensor is installed.
If... Then...
The outlet temperature sensor is not Install the outlet temperature sensor
installed correctly. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The outlet temperature sensor is installed Go to the next step.
Step 2 Check whether the outlet temperature sensor is correctly connected and whether the cable
connected to the sensor is intact.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 641
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The outlet temperature sensor is incorrectly Connect the temperature sensor correctly.
connected Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The cable is damaged Replace the cable with a correct one. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The outlet temperature sensor is correctly Go to the next step.
connected and the cable is intact
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.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.370 OUT2TEMP_SENSOR_FAIL
Description
The OUT2TEMP_SENSOR_FAIL alarm indicates that the temperature sensor at the external
cycling air exhaust vent fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
The equipment cannot collect the temperature data of the external cycling air exhaust vent on
the TCU board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 642
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l No temperature sensor is installed at the external cycling air exhaust vent.
l The temperature sensor at the external cycling air exhaust vent is incorrectly connected.
l The temperature sensor at the external cycling air exhaust vent is faulty.
l The cabinet is faulty.
Procedure
Step 1 Check whether a temperature sensor is installed at the external cycling air exhaust vent.
If... Then...
No temperature sensor is installed at the Install a temperature sensor at the external
external cycling air exhaust vent cycling air exhaust vent correctly. Then,
check whether the alarm is cleared. If the
alarm persists, go to the next step.
A temperature sensor is installed at the Go to the next step.
external cycling air exhaust vent
Step 2 Check whether the temperature sensor at the external cycling air exhaust vent is correctly
connected and whether the cable connected to the temperature sensor is intact.
If... Then...
The temperature sensor at the external Connect the temperature sensor at the
cycling air exhaust vent is incorrectly external cycling air exhaust vent correctly.
connected Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The cable connected to the temperature Replace the cable. Then, check whether the
sensor at the external cycling air exhaust alarm is cleared. If the alarm persists, go to
vent is damaged the next step.
The temperature sensor at the external Go to the next step.
cycling air exhaust vent is correctly
connected and the cable connected to the
temperature sensor is intact
Step 3 Replace the temperature sensor at the external cycling air exhaust vent. Then, check whether
the alarm is cleared.
If... Then...
The alarm persists Replace the cabinet. The alarm is
automatically cleared.
The alarm is cleared No further action is required.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 643
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
----End
Related Information
None.
4.2.371 P_AIS
Description
The P_AIS alarm indicates that signals received on the PDH side of the E3/T3 tributary board
are all 1.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The services at the port where the P_AIS alarm is reported are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The transmission cable is faulty.
l The interconnected PDH equipment outputs AIS signals.
l The TU_AIS or TU_LOP alarm is reported on the corresponding path of the tributary
board.
Procedure
Step 1 Check whether the transmission cable is normal.
If... Then...
The transmission cable is faulty Replace the transmission cable. Then, check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The transmission cable is properly Go to the next step.
functioning
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 644
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Check whether the interconnected PDH equipment is incorrectly configured or has a hardware
fault.
If... Then...
The interconnected PDH equipment is Correct the configuration of the PDH
incorrectly configured or has a hardware equipment or rectify the hardware fault.
fault Then, check whether the alarm is cleared. If
the alarm persists, go to the next step.
The interconnected PDH equipment is Go to the next step.
correctly configured or has no hardware
fault
Step 3 On the U2000, 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 Clear the TU_AIS or TU_LOP alarm. Then,
check whether the P_AIS alarm is cleared.
If the P_AIS alarm persists, go to the next
step.
The TU_AIS or TU_LOP alarm is not Go to the next step.
reported
Step 4 Reseat the E3/T3 tributary board. Then, check whether the alarm is cleared.
If the services traveling through the tributary board are not configured with protection,
reseating or replacing the tributary board interrupts the services.
If... Then...
The alarm persists Replace the E3/T3 tributary board.
The alarm is cleared Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
4.2.489 TU_AIS, 4.2.492 TU_LOP
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 645
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.372 P_LOC
Description
The P_LOC alarm indicates that input clock signals on the PDH side of the E3/T3 tributary
board are lost.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
A large number of service bit errors are generated, or frames cannot be aligned.
Possible Causes
Possible causes of this alarm are as follows:
l The input signals are not E3/T3 signals.
l The input clock signals on the PDH side are lost.
Procedure
Step 1 Check whether the input signals are E3/T3 signals.
If... Then...
The input signals are not E3/T3 signals Set the signals transmitted by the
interconnected PDH equipment to E3/T3
signals. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The input signals are E3/T3 signals Go to the next step.
Step 2 Reseat the E3/T3 tributary board. Then, check whether the alarm is cleared.
If the services traveling through the tributary board are not configured with protection,
reseating or replacing the tributary board interrupts the services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 646
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the E3/T3 tributary board.
The alarm is cleared Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.373 P_LOS
Description
The P_LOS alarm indicates that signals received on the PDH side of the E3/T3 tributary
board are lost.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
The services at the port where the P_LOS alarm is reported are unavailable.
If the clock source used by the port where the P_LOS alarm is reported is the synchronization
clock source for the NE, the P_LOS alarm triggers switching of synchronization clock
sources.
Possible Causes
Possible causes of this alarm are as follows:
l The cable to the output port on the PDH equipment interconnected with the local NE is
disconnected, loosely connected, or faulty.
l The cable to the PDH signal input port is disconnected, loosely connected, or faulty.
l The cable connecting the PDH equipment to the local NE is faulty.
l The PDH equipment interconnected with the local NE fails to transmit signals.
l The signals received by the local NE are not E3/T3 service signals.
l The E3/T3 tributary board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 647
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the cable to the output port on the PDH equipment interconnected with the
local NE is disconnected, loosely connected, or faulty.
If... Then...
The cable is disconnected, loosely Connect the cable correctly or replace the
connected, or faulty cable. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The cable is correctly connected and is Go to the next step.
properly functioning
Step 2 Check whether the cable to the PDH signal input port is disconnected, loosely connected, or
faulty.
If... Then...
The cable is disconnected, loosely Connect the cable correctly or replace the
connected, or faulty cable. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The cable is connected correctly and is Go to the next step.
functioning properly
Step 3 Check whether the PDH equipment interconnected with the local NE transmits E3/T3 service
signals correctly.
If... Then...
The PDH equipment does not transmit Correct the configuration of the PDH
E3/T3 service signals equipment to ensure that the PDH
equipment transmits E3/T3 services to the
local NE. Then, check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The PDH equipment transmits E3/T3 Go to the next step.
service signals correctly
Step 4 Reseat the E3/T3 tributary board. Then, check whether the alarm is cleared.
If the services traveling through the tributary board are not configured with protection,
reseating or replacing the tributary board interrupts the services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 648
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the E3/T3 tributary board.
The alarm is cleared Contact Huawei technical support engineers
to handle the alarm.
----End
Related Information
None.
4.2.374 PASSWORD_NEED_CHANGE
Description
The PASSWORD_NEED_CHANGE alarm indicates that the default user name and password
used to log in to an NE have not been changed.
Examples of default user names and passwords include:
l Username: szhw; password: Changeme_123
l Username: root; password: Changeme_123
l Username: lct; password: Changeme_123
l Username: LCD; password: Changeme_123
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None
Impact on the System
If the default user name and password have not been changed timely, network security risks
increase.
Possible Causes
The possible cause of the alarm is as follows:
l The default user name and password have not been changed.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 649
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Change the default user name and password, or delete the default account.
----End
Related Information
None
4.2.375 PATCH_BD_EXCLUDE
Description
The PATCH_BD_EXCLUDE is an alarm indicating board isolation. An NE reports the
PATCH_BD_EXCLUDE alarm after a board on which patching loading fails is isolated
automatically during patch package loading.
Attribute
Alarm Severity Alarm Type
Major Equipment
Parameters
None
Impact on the System
When an NE reports a PATCH_BD_EXCLUDE alarm, a board is isolated. As a result, the NE
software fails to perform a version matching check for the patch software of the board.
Possible Causes
The possible cause of the PATCH_BD_EXCLUDE alarm is as follows:
l During the patch package loading process, patch loading on a board fails.
l During the patch package loading process, a board is manually isolated.
Procedure
Step 1 If the patch package is running, delete the patch package and perform patch package loading
again. The PATCH_BD_EXCLUDE alarm will be automatically cleared.
Step 2 If the patch package is being loaded, roll back the patch package and perform patch package
loading again. The PATCH_BD_EXCLUDE alarm will be automatically cleared.
Step 3 If the alarm persists, contact Huawei engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 650
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.376 PATCH_BD_MATCH_FAIL
Description
The PATCH_BD_MATCH_FAIL is an alarm indicating a board patch mismatch. An NE
reports the PATCH_BD_MATCH_FAIL alarm if the patch software of a board fails to match
with the patch package software on the system control board for three consecutive times after
patch package loading completes.
Attribute
Alarm Severity Alarm Type
Major Equipment
Parameters
None
Impact on the System
If the system control board reports a PATCH_BD_MATCH_FAIL, patch package loading may
fail again. If another board reports a PATCH_BD_MATCH_FAIL alarm, the NE housing the
board may report a PATCH_BD_MATCH_FAIL alarm again.
Possible Causes
The possible causes of the PATCH_BD_MATCH_FAIL alarm are as follows:
l Cause 1: Board communication faults occur.
l Cause 2: The board software is abnormal.
Procedure
Step 1 Cause 1: Board communication faults occur.
1. On the NMS, check whether communication fault alarms such as 4.2.77
COMMUN_FAIL are reported. If any, clear the alarms.
2. Then, check whether the PATCH_BD_MATCH_FAIL alarm is cleared. If the alarm
persists, go to Step 2.
Step 2 Cause 2: The board software is abnormal.
1. On the NMS, manually isolate the board and rectify the board software fault.
2. Restart matching between the board patch software and the patch package software on
the system control board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 651
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to
handle the alarm.
----End
Related Information
None
4.2.377 PATCH_CHGSCC_NOTMATCH
Description
The PATCH_CHGSCC_NOTMATCH is an alarm indicating patch version inconsistency. An
NE housing a new system control board reports the PATCH_CHGSCC_NOTMATCH alarm if
board patch versions on specific boards are inconsistent with the patch versions in the patch
package on the new system control board.
Attribute
Alarm Severity Alarm Type
Major Equipment
Parameters
None
Impact on the System
Automatic synchronization of board patches with the patch package on the system control
board fails.
Possible Causes
The possible cause of the PATCH_CHGSCC_NOTMATCH alarm is as follows:
l The new system control board has its own patch package, in which patch versions are
inconsistent with versions of patches on specific boards.
Procedure
Step 1 Select the patch package to load and start patch package loading again. The
PATCH_CHGSCC_NOTMATCH alarm will be automatically cleared.
Step 2 If the alarm persists, contact Huawei engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 652
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.378 PATCH_INIT_FAIL
Description
The PATCH_INIT_FAIL alarm indicates that the patch initialization fails. This alarm is
reported after the patch initialization fails and the device or board is reset.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of a patch initialization failure.
l 0x01: software version mismatch
l 0x02: board type mismatch
l 0x03: incorrect patch status
l 0x04: failure to obtain a patch file list
l 0x05: patch file mismatch
l 0x06: patch loading failure
l 0x07: patch activation failure
l 0x08: patch submission failure
l 0xff: other error causes
Impact on the System
The patch may not take effect on the NE.
Possible Causes
The possible cause of the PATCH_INIT_FAIL alarm is as follows:
The patch initialization fails due to a patch file, version, or status error.
Procedure
Step 1 View the alarm information on the NMS. For details, see Viewing the Current Alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 653
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Determine the cause of the patch initialization failure based on the alarm information, and
perform operations accordingly.
If... Then...
The patch fails to be loaded, activated, or Load the patch again. Then check whether
submitted the alarm is cleared. If the alarm persists, go
to Step 3.
The software version, board type, or To diagnose the fault according to SWDL
patch file does not match, the patch logs, go to Step 3.
status is incorrect, the patch file list fails
to be obtained, or other errors occur
Step 3 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.379 PATCH_MATCH_NO_START
Description
The PATCH_MATCH_NO_START alarm indicates that the system control board does not
initiate board patch matching.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicate the slot ID of the system control board that does not initiate board
Parameter 2 patch matching.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 654
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the cause why the system control board does not initiate board
patch matching.
l 0x01: The primary status of package loading is normal but the substatus is
not normal.
l 0x02: The system control board is being replaced.
l 0x03: The system control board is recovering the patch from the external
system.
l 0x04: The software switch is on. (If the software switch is on and the
package loading status is not normal, the PATCH_MATCH_NO_START
alarm is not reported.)
l 0x05: The patch status on the NE side is not RUN.
l 0x06: The inspection result of the patch package is incorrect.
l 0xff: indicates an unknown cause.
Impact on the System
This alarm has no impact on services and on patch package loading upgrades, but the patch
package of the board cannot be matched.
Possible Causes
The possible causes of the PATCH_MATCH_NO_START alarm are as follows:
l The primary status and child status of package loading are not both normal.
l The system control board is being replaced.
l The patch status or patch file is incorrect.
Procedure
Step 1 Analyze the alarm cause according to the alarm parameters.
Step 2 If the system control board is being replaced, perform package loading again on the NE.
NOTE
If you are not familiar with package loading, contact Huawei technical support engineers.
Step 3 If the primary status and child status of package loading are not both normal, wait for 30
minutes and then check whether the alarm is cleared.
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 655
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.380 PATCH_OP_TIMEOUT
Description
The PATCH_OP_TIMEOUT alarm indicates that the patch installation times out. This alarm
is reported when the patch installation operation times out.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the patch status.
l 0x04: The patch is in the loaded state.
l 0x06: The patch is in the activated state.
Impact on the System
The patch may not take effect on the NE.
Possible Causes
The possible cause of the PATCH_OP_TIMEOUT alarm is as follows:
The Pause Before Current Operation check box is selected during the execution of a patch
installation task, but the patch has not been activated or submitted. As a result, the patch is in
the loaded or activated state for over 30 minutes.
Procedure
Step 1 Check whether the patch package is correct.
If... Then...
The patch package is correct Go to the next step.
The patch package is incorrect Use a correct patch package to perform an
upgrade. Then check whether the alarm is
cleared. If the alarm persists, go to Step 3.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 656
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 If the patch package is correct, determine whether to perform subsequent operations based on
the patch status.
If... Then...
The patch installation needs to be l If the value of Parameter 1 is 0x04,
continued choose Administration > NE Software
Management > NE Upgrade Task
Management on the main menu of the
NMS. Right-click the patch task name,
and choose Continue Task from the
shortcut menu to activate and submit the
patch. Then check whether the alarm is
cleared. If the alarm persists, go to Step
3.
l If the value of Parameter 1 is 0x06,
choose Administration > NE Software
Management > NE Upgrade Task
Management on the main menu of the
NMS. Right-click the patch task name,
and choose Continue Task from the
shortcut menu to submit the patch. Then
check whether the alarm is cleared. If the
alarm persists, go to Step 3.
The patch installation does not need to be Perform a rollback. The
continued PATCH_OP_TIMEOUT alarm is cleared
automatically.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.381 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicates that the patch package file is abnormal.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 657
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
If the patch package file is abnormal, loading, activation, and running of the patch package
are affected.
NOTE
When this alarm is reported, services are not interrupted.
Possible Causes
Possible causes of the PATCH_PKGERR alarm are as follows:
l The patch package file is incorrect.
l The patch package file is damaged.
l The patch package file is deleted.
Procedure
Step 1 Reload the correct patch package file. The alarm is cleared automatically.
----End
Related Information
None.
4.2.382 PCM_64KSNCP_UNAVAIL
Description
The PCM_64KSNCP_UNAVAIL alarm indicates that 64K subnetwork connection protection
(SNCP) is unavailable.
Attribute
Alarm Severity Alarm Type
Major Processing error 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate a protection group ID.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 658
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 3 Indicates the source working signaling value.
Parameter 4 Indicates the source protection signaling value.
Parameter 5 Indicates the sink signaling value.
Impact on the System
64K SNCP is unavailable.
Possible Causes
The possible causes of the PCM_64KSNCP_UNAVAIL alarm are as follows:
l Cause 1: The 64K SNCP group type is configured incorrectly.
l Cause 2: The active and standby links of the 64K SNCP group are in the SF state (signal
failure).
l Cause 3: The active and standby links of the 64K SNCP group are faulty.
Procedure
Step 1 Cause 1: The 64K SNCP group type is configured incorrectly.
1. Find the protection group configuration based on the protection group ID. Then check
whether the protection group type is consistent with the actual service type. For example,
if the protection group type is an audio service but the actual service type is not an audio
service, the PCM_64KSNCP_UNAVAIL alarm may be reported.
If… Then...
The protection group type is Delete the incorrect protection group, add a 64K
inconsistent with the actual SNCP group, and ensure that the protection
service type, group type is consistent with the actual service
type. For details, see Configuring 64K SNCP in
Feature Description.
The protection group type is Go to Step 2.
consistent with the actual service
type,
Step 2 Cause 2: The active and standby links of the 64K SNCP group are in the SF state (signal
failure).
1. Check the onsite conditions (for example, whether the switching conditions are
consistent between the NEs at both ends) to determine whether 64K SNCP switching
conditions can be modified, and perform operations accordingly.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 659
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
64K SNCP You are advised to set A, B, C, and D to 1 for the NEs at both
switching ends. Go to Step 2.2.
conditions can be
modified
64K SNCP Modify voice signaling configurations (off-hook and on-hook
switching signaling values, and ensure that the new signaling values are
conditions cannot different from the values of Parameters 3 to 5). For details about
be modified the operation method, see Configuring a PCM Port in
Configuration. For details about signaling configuration
parameters, see Advanced Configurations in Configuration.
Then check whether the alarm is cleared. If the alarm persists, go
to Step 3.
2. In the Main Topology, right-click the desired NE and choose NE Explorer from the
shortcut menu. Choose Configuration > 64K SNCP Service Control from the Function
Tree. Click Switching Condition, and set A, B, C, and D to 1.
Step 3 Cause 3: The active and standby links of the 64K SNCP group are faulty.
1. Check whether the fiber or electrical cable to the port on the NE is faulty.
If… Then...
The fiber or electrical cable is faulty, Replace the faulty fiber or electrical
cable. Then check whether the alarm is
cleared. If the alarm persists, go to Step
4.
The fiber or electrical cable is normal, If the alarm persists, go to Step 4.
Step 4 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 660
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.383 PCM_DATA_CONFLICT
Description
The PCM_DATA_CONFLICT alarm indicates a data conflict of multiplexer group members.
This alarm is reported when a multiplexer group receives multiple channels of valid data
simultaneously and a data conflict occurs.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 This parameter is meaningless. It has a fixed value of 0x01.
Parameter 2 Indicates the timeslot ID.
Parameter 3 Indicates the path numbers.
Impact on the System
Services of the multiplexer group are interrupted.
Possible Causes
Cause: The multiplexer group receives multiple channels of valid data simultaneously, which
causes a data conflict.
As shown in Figure 4-31, if service signals from both Slave 1 and Slave 2 to the Master are
valid, a data conflict of the multiplexer group members occurs on NE1. NE1's ports that
receive services from Slave 1 and Slave 2 report PCM_DATA_CONFLICT alarms.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 661
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Figure 4-31 PCM_DATA_CONFLICT alarm generation (Data-P2MP)
1. Service signals from both Slave 1 and
Slave 2 to the Master are valid.
2. NE1's ports that receive services from Slave 1
Slave 1 and Slave 2 report
PCM_DATA_CONFLICT alarms.
NE2
Slave 2
Master
NE3
NE1
Slave 3
NE4
Valid service signals from a Slave to the Master
Invalid service signals from a Slave to the Master
Valid service signals from the Master to a Slave
Procedure
Step 1 Cause: The multiplexer group receives multiple channels of valid data simultaneously, which
causes a data conflict.
1. Query the alarm on the NMS. Determine the number of the path where the data conflict
occurs in the multiplexer group based on alarm parameters.
2. Ensure that the PCM devices connected to the path do not transmit valid data
simultaneously.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.384 PING_ARP_MISMATCH
Description
The PING_ARP_MISMATCH alarm indicates that the dynamic ARP and static ARP conflict
in the ping operation.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 662
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
Name Meaning
Parameters 1-4 Indicate the IP addresses that conflict.
Impact on the System
None
Possible Causes
The MAC address configured for an IP address in the static ARP list is different from the
MAC address that is learnt by the IP address in the dynamic ARP list.
Procedure
Step 1 Check whether the MAC address configured for an IP address in the static ARP list is
different from the MAC address that is learnt by the IP address in the dynamic ARP list. If
they are different, delete the IP address from the static ARP list. For details, see the
Configuring Address Resolution.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.385 PING_LOS
Description
The PING_LOS alarm indicates that IP Ping fails.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 663
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
Name Meaning
Parameters 1–4 Indicate the destination IP address.
Parameter 5 Indicates the IP Ping type.
l 0x00: indicates the local end.
l 0x01: indicates the remote end.
Parameters 6–7 Indicate the external VLAN ID.
Parameter 8 Indicates the external VLAN priority.
Parameters 9–10 Indicate the inner VLAN ID.
Parameter 11 Indicates the inner VLAN priority.
Parameter 12 Indicates the alarm type.
l 0x01: indicates that sending ping packets fails or times out.
l 0x03: indicates that the CRC check on ping packets fails.
Impact on the System
None
Possible Causes
l Cause 1: The CRC check on ping packets fails.
l Cause 2: The ping operation times out.
l Cause 3: Sending ping packets fails.
Procedure
Step 1 Cause 1: The CRC check on ping packets fails.
1. Check for abnormal alarms related to physical links in the manner from the local end to
the peer end, such as ETH_LOS, MAC_FCS_EXC. If any abnormal alarms are found,
clear them.
2. Check whether the alarm is cleared. If the alarm persists, go to next step.
Step 2 Cause 2: The ping operation times out.
1. Check for abnormal alarms related to physical links in the manner from the local end to
the peer end. If any abnormal alarms are found, clear them.
2. If the abnormal alarms are cleared, check for service fault alarms and clear them.
3. Check whether the alarm is cleared. If the alarm persists, go to next step.
Step 3 Cause 3: Sending ping packets fails.
1. Check whether the dynamic ARP list contains the destination IP address. If not, check
whether the static ARP list contains the destination IP address. If not, add the destination
IP address to the static ARP list.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 664
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.386 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC is an alarm indicating that the traffic over an Ethernet port
exceeds its threshold. This alarm is reported if the traffic over an Ethernet port exceeds its
threshold.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the directions in which the traffic over an Ethernet port exceeds its
threshold:
l 0x00: indicates the receive direction.
l 0x01: indicates the transmit direction.
Impact on the System
Service traffic is excessively heavy if this alarm is generated, causing network congestion.
Possible Causes
The possible causes of the PORT_EXC_TRAFFIC alarm are as follows:
l Cause 1: The bandwidth restriction of an Ethernet port is configured too low.
l Cause 2: The configured Ethernet port traffic is too heavy.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 665
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Cause 1: The bandwidth restriction of an Ethernet port is configured too low.
1. Check the bandwidth restriction of an Ethernet port on the NMS. For details, see
Checking the Performance Data of the Statistics Group.
2. If the configured bandwidth restriction is too low, to increase the bandwidth restriction
value or perform network expansion.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The configured Ethernet port traffic is too heavy.
1. Check the traffic of an Ethernet port on the NMS.
2. If the port traffic is excessively heavy, check whether a network storm occurs. If a
network storm occurs, eliminate the source that transmits a large amount of invalid data.
----End
Related Information
None.
4.2.387 PORT_MODULE_OFFLINE
Description
This alarm indicates that the optical module on an optical port is offline. This alarm is
generated when the board detects that an optical module is offline.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
Absence of the optical module leads to an interruption of services through by the
corresponding optical port.
Fault Symptom
None
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 666
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
l Cause 1: The optical module does not exist or is not correctly inserted in the optical port.
l Cause 2: The optical module or the board is faulty.
Procedure
l Check the alarm information on the NMS and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The optical module does not exist or is not correctly inserted in the slot.
a. Check whether the optical port where this alarm is generated has an optical module.
If... Then...
The optical port has no optical Insert an optical module into the
module. optical port properly.
The optical port has an optical See the alarm handling procedure for
module. cause 2.
l Cause 2: The optical module or the board is faulty.
If... Then...
The board supports pluggable optical Replace pluggable optical modules. For
modules details, see Replacing the Optical
Module. If the alarm persists, replace the
faulty board.
The board does not support pluggable Reset the board. For details, see Resetting
optical modules Boards.
If the alarm persists, replace the faulty
board.
----End
Related Information
None
4.2.388 PORTMODE_MISMATCH
Description
The PORTMODE_MISMATCH alarm indicates that the working mode of the opposite FE
port does not match with that of the local FE port. When the local FE port is in the auto-
negotiation mode and the opposite FE port is in the non-auto-negotiation mode, the
PORTMODE_MISMATCH alarm is reported.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 667
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the working mode of the local FE port.
Parameter 1 is always 0x00.
Parameter 2 indicate the working mode of the local port.
0x01: 10M half duplex.
0x03: 100M half duplex.
0x05: 1000M half duplex.
Impact on the System
Service packets are lost on the link and the network rate decreases.
Possible Causes
The possible cause of the PORTMODE_MISMATCH alarm is as follows:
l The working mode of the local FE port is inconsistent with that of opposite FE port. For
example, the local FE port works in the auto-negotiation mode whereas the opposite FE
port works in the non-auto-negotiation mode.
Procedure
Step 1 View the PORTMODE_MISMATCH alarm on the U2000, and then confirm the number of
the MAC port where the PORTMODE_MISMATCH alarm is generated according to alarm
parameters.
Step 2 Disable and then enable the opposite FE port, and start the auto-negotiation mode. Ensure that
the working mode of the local FE port is consistent with that of the opposite FE port. Check
whether the PORTMODE_MISMATCH alarm is cleared.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 668
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.389 POWER_ABNORMAL
Description
The POWER_ABNORMAL alarm indicates a power failure. This alarm is reported if one
power supply of the NE fails.
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 details
about each parameter, refer to the following table.
Name Meaning
TNC1PIU l 0x01 0x00: Power supply 1 has no power input.
l 0x01 0x01: Power supply 1 is overvoltage.
TND1PIU
l 0x01 0x02: Power supply 1 is undervoltage.
l 0x02 0x00: Power supply 2 has no power input.
l 0x02 0x01: Power supply 2 is overvoltage.
l 0x02 0x02: Power supply 2 is undervoltage.
TNM1CQ1 0x14 0x00: A power component is faulty.
TNH1CSHD (ML1) l 0x01: The 1.2 V power supply is abnormal.
l 0x02: The 1.0 V power supply is abnormal.
TNM1MD1
l 0x03: The 1.8 V power supply is abnormal.
l 0x04: The 3.3 V standby power supply is abnormal.
l 0x05: The 3.3 V power supply is abnormal.
l 0x06: The 2.5 V power supply is abnormal.
l 0x07: The 3.0 V power supply is abnormal.
Impact on the System
If the alarm is reported, one of the two power inputs is faulty. As a result, the NE is affected.
Possible Causes
Possible causes of the POWER_ABNORMAL alarm are as follows:
l The power input port is loose, or has been disconnected.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 669
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The power board is faulty.
Procedure
Step 1 Check whether the power cable is connected correctly to the power input port. If the cable is
not connected or is loose, connect it correctly.
Step 2 View alarms on the U2000 to check whether the POWER_ABNORMAL alarm is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 3 Replace the NE subrack.
Replacing the power module or the subrack of the NE requires power—off of the NE. This
operation will interrupt the services on the NE. Hence, this operation is of risk.
----End
Related Information
None.
4.2.390 POWER_FAIL
Description
The POWER_FAIL alarm indicates a power failure on an NE.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 670
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNF1APIU l 0x55 0x01: The 1.0 V power supply is overvoltage.
l 0x4f 0x01: The 1.8 V power supply is overvoltage.
l 0x53 0x01: The 3.3 V power supply is overvoltage.
l 0x51 0x01: The 12 V power supply is overvoltage.
l 0x56 0x01: The 1.0 V power supply is undervoltage.
l 0x50 0x01: The 1.8 V power supply is undervoltage.
l 0x54 0x01: The 3.3 V power supply is undervoltage.
l 0x52 0x01: The 12 V power supply is undervoltage.
l 0x67 0x01: The 1.2 V power supply is overvoltage.
l 0x4d 0x01: The 1.26 V power supply is overvoltage.
l 0x5b 0x01: The 2.5 V power supply is overvoltage.
l 0x5d 0x01: The 5.0 V power supply is overvoltage.
l 0x68 0x01: The 1.2 V power supply is undervoltage.
l 0x4e 0x01: The 1.26 V power supply is undervoltage.
l 0x5c 0x01: The 2.5 V power supply is undervoltage.
l 0x5e 0x01: The 5.0 V power supply is undervoltage.
TNF2OBU l 0x41: The 3.3 V active power supply is overvoltage.
l 0x42: The 3.3 V active power supply is undervoltage.
TNF5APIU l 0x55: The input voltage of power supply 1 of the APIU is abnormal.
l 0x57: The output voltage of power supply 1 of the APIU is abnormal.
l 0x58: The output voltage of power supply 2 of the APIU is abnormal.
l 0x59: APIU overtemperature protection is triggered.
l 0x60: The APIU locks out due to output overvoltage.
l 0x61: The APIU encounters slight overtemperature.
TNF5PIU l 0x50: The 48 V active power supply is undervoltage.
TNH1CSHD l 0x6a 0x01: The 1.0 V power supply is undervoltage.
(SCC) l 0x69 0x01: The 1.0 V power supply is overvoltage.
TNM1PCX l 0x4c 0x01: The 1.2 V power supply is undervoltage.
(SCC) l 0x4b 0x01: The 1.2 V power supply is overvoltage.
l 0x44 0x01: The 1.8 V power supply is undervoltage.
l 0x43 0x01: The 1.8 V power supply is overvoltage.
l 0x25 0x01: The 3.3 V combined power supply is undervoltage.
l 0x24 0x01: The 3.3 V combined power supply is overvoltage.
l 0x42 0x01: The 3.3 V power supply is undervoltage.
l 0x41 0x01: The 3.3 V power supply is overvoltage.
l 0x13 0x01: The 12 V power supply is undervoltage.
l 0x12 0x01: The 12 V power supply is overvoltage.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 671
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
TNW1UCX l 0x05: The battery on the system control board is dead.
(SCC),
l 0x50: The 48 V active power supply is undervoltage.
TNW1UCXE
(SCC) l 0x52: The 48 V standby power supply is undervoltage.
Impact on the System
The power voltage of the board is low. As a result, switching of active/standby power supplies
occurs, or a cold reset occurs and causes service interruptions.
Possible Causes
Possible cause of the POWER_FAIL alarm is as follows:
l The switch on the standby power board is turned off.
l The power module is faulty.
l The power module is aged.
Procedure
Step 1 Check whether the switch on the standby power board is turned off.
If... Then...
The switch on the standby power board is Turn on the switch. Check whether the
turned off alarm is cleared. If the alarm persists, go to
the next step.
The switch on the standby power board is Go to the next step.
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. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The power module works normally Go to the next step.
Step 3 Replace the NE subrack and the alarm is cleared automatically.
Replacing the power module or the subrack of the NE requires power—off of the NE. This
operation will interrupt the services on the NE. Hence, this operation is of risk.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 672
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.391 POWER_MODULE_OFFLINE
Description
The POWER_MODULE_OFFLINE alarm indicates 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the power module number.
l 0x01: Power module 1 is offline.
l 0x02: Power module 2 is offline.
Impact on the System
When this alarm is reported, no power is provided for the corresponding port.
Possible Causes
Possible causes of the ROWER_MODULE_OFFLINE alarm are as follows:
l The power module is in poor contact.
l The power module is faulty.
Procedure
Step 1 Check whether the power module is in poor contact.
If... Then...
The power module is in poor contact Insert the power module correctly, and then
check whether the alarm is cleared. If the
alarm persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 673
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The power module is in good contact Go to the next step.
Step 2 Check whether the power module is faulty.
If... Then...
The power module is faulty Replace the power module with a
functioning one.
The power module works normally Contact Huawei technical support engineers
for handling the alarm.
----End
Related Information
None.
4.2.392 PPP_LCP_FAIL
Description
The PPP_LCP_FAIL alarm indicates a Link Control Protocol (LCP) negotiation failure. This
alarm is reported when a port uses the PPP encapsulation type and fails to negotiate with the
opposite port.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
None
Impact on the System
The LCP negotiation fails and services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The MP configurations on the local and opposite ports are inconsistent.
l Cause 2: The network is congested or its quality is poor, which causes improper running
of the LCP protocol.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 674
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l Cause 3: The physical link is interrupted.
Procedure
Step 1 Cause 1: The MP configurations on the local and opposite ports are inconsistent.
1. On the NMS, check whether the MP configurations at the local and opposite ports are
consistent. If they are inconsistent, configure them consistently. For details, see Creating
MP Groups.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network is congested or its quality is poor, which causes improper running of
the LCP protocol.
1. On the NMS, check whether the bandwidth for the tunnel connected to the ports is
configured low. If the configured tunnel bandwidth is low, increase the bandwidth.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The physical link is interrupted.
1. Check whether member links in the MP group have the R_LOS or T_ALOS alarm
indicating loss of signals. If such an alarm occurs, clear the alarm first.
2. Check whether alarm is cleared. If the alarm persists, contact Huawei technical support
personnel to handle the alarm.
----End
Related Information
None
4.2.393 PPP_NCP_FAIL
Description
The PPP_NCP_FAIL alarm indicates a Network Control Protocol (NCP) negotiation failure.
This alarm is reported when the NCP configuration attributes are inconsistent between the
local and opposite NEs.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
None
Impact on the System
The NCP negotiation fails and services are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 675
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
The possible cause of this alarm is as follows:
Cause: The MP configurations at the local and opposite NEs are inconsistent.
Procedure
Step 1 Cause: The MP configurations at the local and opposite NEs are inconsistent.
1. On the NMS, check whether the MP configurations at the local and opposite NEs are
consistent. If they are inconsistent, configure them consistently. For details, see Creating
MP Groups.
2. Check whether alarm is cleared. If the alarm persists, contact Huawei technical support
personnel to handle the alarm.
----End
Related Information
None
4.2.394 PRBS_LSS
Description
The PRBS_LSS alarm indicates loss of the pseudo-random binary sequence (PRBS) signal.
The alarm is generated when the board, on which the PRBS bit error test is performed, does
not receive the PRBS signals from the local board.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Impact on the System
The PRBS test services on the board are interrupted.
Possible Causes
l Cause 1: The link is abnormal. Hence, the board, on which the PRBS bit error test is
performed, does not receive the PRBS signals from the local board.
l Cause 2: The board is faulty, or the line is degraded.
Procedure
Step 1 Perform a self-loop by connecting the transmit end to the receive end of the PRBS signals on
the local board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 676
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l If the alarm is cleared, it indicates that the board is normal. See Step 2 to check the link.
l If the alarm persists, it indicates that the board is faulty. Replace the board.
Step 2 Check the link and make sure that the link under the PRBS test is a loop. If the alarm persists,
perform a loopback on each point of the link. Find out the abnormal point on the link, and
repair or replace the link.
----End
Related Information
None
4.2.395 PRO_PKT_FLOODING
Description
The PRO_PKT_FLOODING is an alarm indicates the NE is under a flooding attack of
protocol packets. The PRO_PKT_FLOODING alarm is reported when the rate of protocol
packets of a type exceeds the maximum speed for consecutive 30 seconds.
Attribute
Alarm Severity Alarm Type
Major Security 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, parameter 2 Indicates the slot number.
Parameter 3, parameter 4 Indicates the packet type.
Parameter 5, parameter 6 The fixed value is 0xFFFF.
Impact on the System
If the PRO_PKT_FLOODING alarm is generated, a large number of CPU resources are
occupied and the system is unstable. In addition, normal protocol packets may be lost.
Possible Causes
The possible causes of the PRO_PKT_FLOODING alarm include:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 677
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
The rate of protocol packets of a type exceeds the maximum speed for consecutive 30
seconds.
Procedure
Step 1 Check the PRO_PKT_FLOODING alarm on the NMS. Parameters 3 and 4 indicate whether
the ports on the alarmed board are configured with that protocol.
Step 2 If these ports are configured with that protocol, use the packet traffic on the ports to determine
whether the ports are under a flooding attack. If these ports are not configured with that
protocol, go to Step 4.
Step 3 The user should determine whether to disable the port under the flooding attack.
NOTE
Disabling the port will lead to protocol interruption on the port.
Step 4 Check whether the alarm is cleared. If it persists, contact Huawei engineers.
----End
Related Information
None.
4.2.396 PTP_ATTR_MISMATCH
Description
The PTP_ATTR_MISMATCH alarm indicates that Precision Time Protocol (PTP) port
attributes are inconsistent at two ends. If the PTP port attributes are inconsistent at two ends,
PTP packets may not be processed correctly. As a result, the time cannot be traced normally.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 678
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the inconsistent PTP port attribute.
l 0x01: The delay modes are inconsistent.
l 0x02: The encapsulation types are inconsistent.
l 0x03: The clock subnet IDs are inconsistent.
l 0x04: The peer clock source IDs to be received are inconsistent.
Impact on the System
The time cannot be traced normally.
Possible Causes
The possible causes of the PTP_ATTR_MISMATCH alarm are as follows:
l Cause 1: The delay modes are inconsistent.
l Cause 2: The encapsulation types are inconsistent.
l Cause 3: The clock subnet IDs are inconsistent.
l Cause 4: The peer clock source IDs to be received are inconsistent.
Procedure
Step 1 Check the alarm on the NMS and determine the cause of the alarm according to the alarm
parameters.
Step 2 Cause 1: The delay modes are inconsistent.
1. Check whether the time port delay mechanisms are consistent between the PTP ports at
both ends.
If… Then...
The time port delay Set the time port delay mechanisms to the same values for the
mechanisms are PTP ports at both ends. That is, set the P/E modes to either E2E
inconsistent, or P2P. For details, see Setting Parameters for IEEE 1588v2
Clock Packets in Feature Description. Then check whether the
alarm is cleared. If the alarm persists, go to Step 6.
The time port delay Check whether the alarm is cleared. If the alarm persists, go to
mechanisms are Step 6.
consistent,
Step 3 Cause 2: The encapsulation types are inconsistent.
1. Check whether the encapsulation types are consistent between the PTP ports at both
ends.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 679
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If… Then...
The encapsulation types Set PTP Packet Encapsulation Format to the same values for
are inconsistent, the PTP ports at both ends. For details, see Setting PTP Clock
Port Attributes in Feature Description. Then check whether the
alarm is cleared. If the alarm persists, go to Step 6.
The encapsulation types Check whether the alarm is cleared. If the alarm persists, go to
are consistent, Step 6.
Step 4 Cause 3: The clock subnet IDs are inconsistent.
1. Check whether the clock subnet IDs are consistent between the PTP ports at both ends.
If... Then...
The clock subnet IDs are Set the clock subnet IDs to the same values for the PTP ports at
inconsistent, both ends. For details, see Configuring a PTP Clock Subnet in
Feature Description. Then check whether the alarm is cleared.
If the alarm persists, go to Step 6.
The clock subnet IDs are Check whether the alarm is cleared. If the alarm persists, go to
consistent, Step 6.
Step 5 Cause 4: The peer clock source IDs to be received are inconsistent.
1. Check whether a loop exists on the link.
If... Then...
A loop exists on the link, Eliminate the loop. Then check whether the alarm is cleared. If
the alarm persists, go to Step 6.
No loop exists on the link, Check whether the alarm is cleared. If the alarm persists, go to
Step 6.
Step 6 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.397 PTP_DELAY_RESP_LOS
Description
The PTP_DELAY_RESP_LOS alarm indicates that Delay_Resp packets are lost. This alarm
is reported when a port in the Slave, Uncalibrated, or Passive state fails to receive
Delay_Resp packets (the port status can be queried in PPT clock synchronization attributes).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 680
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
If the alarm is reported on the port in the Slave or Uncalibrated state, the IEEE 1588v2 time
cannot be synchronized between NEs.
If the alarm is reported on the port in the Passive state, the standby IEEE 1588v2 link may
fail to provide the protection.
Possible Causes
A fault alarm is reported on the board.
Procedure
Step 1 Check whether a fault alarm (for example, 4.2.157 HARD_BAD or 4.2.158 HARD_ERR) is
reported on the board. If the fault alarm exists, clear it first. Then check whether this alarm is
cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.398 PTP_DECRYPTION_FAIL
Description
The PTP_DECRYPTION_FAIL alarm indicates that the packets returned on an IEEE 1588
ring network fail to be decrypted. This alarm is reported when IEEE 1588 packets returned by
the peer NE fail to be decrypted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 681
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicate the ID of the peer NE.
Impact on the System
The automatic compensation function of the IEEE 1588 ring network may be unavailable.
Possible Causes
The possible cause of the PTP_DECRYPTION_FAIL alarm is as follows:
The IEEE 1588 packet keys are inconsistent between the NEs.
Procedure
Step 1 Check the IEEE 1588 packet keys, find the NE with a different key, and change the key of the
NE to ensure that the keys are consistent between the NEs. The procedure is as follows:
1. In the Main Topology, right-click the desired NE and choose NE Explorer from the
shortcut menu.
2. Choose Configuration > Clock > PPT Clock > Set 1588 Compensation Back Safe
Password from the Function Tree.
3. Click the blank text box under Value next to 1588 Compensation Back Safe Password.
In the displayed dialog box, enter a key.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 682
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
NOTE
Only an NMS user with Operator Group rights or higher is allowed to set the key.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.399 PTP_PDELAY_RESP_LOS
Description
The PTP_PDELAY_RESP_LOS alarm indicates that Pdelay_Resp packets are lost. This
alarm is reported when a port in the Slave, Uncalibrated, or Passive state fails to receive
Pdelay_Resp packets (the port status can be queried in PPT clock synchronization attributes).
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 683
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
If the alarm is reported on the port in the Slave or Uncalibrated state, the IEEE 1588v2 time
cannot be synchronized between NEs.
If the alarm is reported on the port in the Passive state, the standby IEEE 1588v2 link may
fail to provide the protection.
Possible Causes
A fault alarm is reported on the board.
Procedure
Step 1 Check whether a fault alarm (for example, 4.2.157 HARD_BAD or 4.2.158 HARD_ERR) is
reported on the board. If the fault alarm exists, clear it first. Then check whether this alarm is
cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.400 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating that the PTP clock source is switched.
This alarm is reported when the NE switches from the Grandmaster time source or time port
to another time source or time port.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 684
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1, Parameter 2 Indicate the slot IDs of the board before the
switching.
Parameter 3 The value is always 0xff.
Parameter 4, Parameter 5 Indicate the ID of the port before the switching.
Parameters 6, Parameter 7, Parameter Indicate the Grandmaster time source ID1 before the
8, Parameter 9 switching.
Parameters 10, Parameter 11, Indicate the Grandmaster time source ID2 before the
Parameter 12, Parameter 13 switching.
Parameter 14, Parameter 15 Indicate the slot ID of the board after the switching.
Parameter 16 The value is always 0xff.
Parameter 17, Parameter 18 Indicate the ID of the port after the switching.
Parameters 19, Parameter 20, Indicate the Grandmaster time source ID1 after the
Parameter 21, Parameter 22 switching.
Parameters 23, Parameter 24, Indicate the Grandmaster time source ID2 after the
Parameter 25, Parameter 26 switching.
Impact on the System
When this alarm occurs, the PTP clock source of the NE is switched so that the PTP clock of
the entire network is switched.
Possible Causes
The possible causes of the PTP_SOURCE_SWITCH alarm are as follows:
l Cause 1: A fault occurs on the physical link tracing the Grandmaster clock source.
l Cause 2: Information about the Grandmaster clock source, such as the priority and
quality level, has changed.
l Cause 3: The network topology has changed.
NOTE
The PTP_SOURCE_SWITCH alarm is used to prompt you that the PTP clock source is switched and
will disappear with 5 seconds. You must handle it only when the PTP_SOURCE_SWITCH alarm is
reported frequently indicating that the PTP clock source is switched frequently.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 685
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Cause 1: A fault occurs on the physical link tracing the Grandmaster clock source.
1. On the NMS, check whether the 4.2.131 ETH_LOS alarm occurs at the port whose PTP
clock source is traced. If this alarm occurs, clear it first.
2. Check whether the alarm is reported frequently. If yes, go to Step 2.
Step 2 Cause 2: Information about the Grandmaster clock source, such as the priority and quality
level, has changed.
1. Check whether the priority and quality level of the Grandmaster clock source has
changed. If the Grandmaster clock source is faulty, switch the Grandmaster clock source
to another one.
2. Check whether the alarm is reported frequently. If yes, go to Step 3.
Step 3 Cause 3: The network topology has changed.
1. Check whether the network topology is changed. If yes, maintain the latest network
topology.
2. Then, check whether alarm is reported frequently. If yes, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.401 PTP_SYNC_LOS
Description
The PTP_SYNC_LOS alarm indicates that SYNC packets are lost. This alarm is reported
when a port in the Slave, Uncalibrated, or Passive state fails to receive SYNC packets (the
port status can be queried in PPT clock synchronization attributes).
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
If the alarm is reported on the port in the Slave or Uncalibrated state, the IEEE 1588v2 time
cannot be synchronized between NEs.
If the alarm is reported on the port in the Passive state, the standby IEEE 1588v2 link may
fail to provide the protection.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 686
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
A fault alarm is reported on the board.
Procedure
Step 1 Check whether a fault alarm (for example, 4.2.157 HARD_BAD or 4.2.158 HARD_ERR) is
reported on the board. If the fault alarm exists, clear it first. Then check whether this alarm is
cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.402 PTP_TIMESTAMP_ABN
Description
The PTP_TIMESTAMP_ABN alarm indicates an abnormality of the PTP timestamp. This
alarm is reported when the PTP timestamp remains unchanged.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x02: Timestamp t1 remains unchanged in 3 consecutive seconds.
l 0x03: Timestamp t2 remains unchanged in 3 consecutive seconds.
l 0x04: Timestamps t1 and t2 remain unchanged in three consecutive
seconds.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 687
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2 l 0x02: Timestamp t3 remains unchanged in 17 consecutive seconds.
l 0x03: Timestamp t4 remains unchanged in 17 consecutive seconds.
l 0x04: Timestamps t3 and t4 remain unchanged in 17 consecutive seconds.
Impact on the System
When this alarm occurs, the timestamp remains unchanged and the NE time cannot trace the
time of the upstream NE so that bit errors occur in services.
Possible Causes
The possible causes of the PTP_TIMESTAMP_ABN alarm are as follows:
l Cause 1: A fault occurs at transmit end field programmable gate array (FPGA) or on the
clock module.
l Cause 2: A fault occurs on the bus or clock module at the receive end.
l Cause 3: The Sync packet transmission frequency is lower than 8 packets per second on
the upstream NE when IEEE 1588 frequency synchronization is configured.
l Cause 4: The Sync packet transmission frequency is lower than 1 packets per second on
the upstream NE when physical-layer synchronization and IEEE 1588 synchronization is
configured.
Procedure
Step 1 Cause 1: A fault occurs at transmit end field programmable gate array (FPGA) or on the clock
module.
1. On the NMS, check whether the 4.2.157 HARD_BAD alarm is reported by the board on
which the port sending IEEE 1588 packets resides. If yes, clear it first.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: A fault occurs on the bus or clock module at the receive end.
1. On the NMS, check whether the 4.2.157 HARD_BAD or 4.2.46 BUS_ERR alarm is
reported by the board on which the port receiving IEEE 1588 packets resides. If yes,
clear it first.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The Sync packet transmission frequency is lower than 8 packets per second on the
upstream NE when IEEE 1588 frequency synchronization is configured.
1. In the NE Explorer, select the desired NE and choose Configuration > Clock > PTP
Clock > Clock Synchronization Attribute from the Function Tree. Click the Port
Message tab. On the SYNC Packet Period(s) drop-down menu, configure the upstream
node to transmit over eight Sync packets per second and click Apply. Then check
whether the alarm is cleared.
2. If the alarm persists, go to Step 4.
Step 4 Cause 4: The Sync packet transmission frequency is lower than 1 packets per second on the
upstream NE when physical-layer synchronization and IEEE 1588 synchronization is
configured.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 688
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. In the NE Explorer, select the desired NE and choose Configuration > Clock > PTP
Clock > Clock Synchronization Attribute from the Function Tree. Click the Port
Message tab. On the SYNC Packet Period(s) drop-down menu, configure the upstream
node to transmit over one Sync packet per second and click Apply. Then check whether
the alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
The Sync and Delay messages are used for end-to-end delay measurement and time
synchronization.
4.2.403 PTPSRV_LCS_INVALID
Description
The PTPSRV_LCS_INVALID is an alarm indicating that the service license for the PTP clock
is invalid. This alarm is reported when the PTP service exists but its license is invalid.
Attribute
Alarm Severity Alarm Type
Warning Equipment alarm
Parameters
None.
Impact on the System
None.
Possible Causes
The possible cause of the PTPSRV_LCS_INVALID alarm is as follows:
Cause: The feature license is invalid though the PTP clock service exists.
Procedure
Step 1 Configure a valid license for the PTP clock service.
NOTE
If the PTP clock service is in unauthorized use, you can delete the PTP clock service to clear the alarm.
For details about unauthorized use of the feature license, you can also refer to 4.2.149
FEATURE_WITHOUT_LICENSE for a solution.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 689
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.2.404 PUM_BCM_ALM
Description
The PUM_BCM_ALM alarm indicates that the bias current of the pump laser crosses the
threshold. This alarm occurs when the pump laser bias current of the optical amplifier unit
crosses the threshold.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
The pump laser may be aged. Report of this alarm has no impact on the services. If no
measure is taken, however, the output optical power of the board is affected in a period of
time. This affects the services
Possible Causes
l Excessively high or excessively low ambient temperature affects the laser.
l The board is faulty.
Procedure
Step 1 Check whether the ambient temperature is normal. If not, adjust the ambient temperature of
the equipment to a proper degree.
Step 2 If the alarm persists, perform a warm reset on the faulty board on the NMS. For details, see
Resetting Boards in the Supporting Tarks.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect the services.
Step 4 If the alarm persists, replace the faulty board. For details, see Parts Replacement.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 690
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.405 PUM_TEM_ALM
Description
The PUM_TEM_ALM alarm indicates that the working temperature of the pump laser
exceeds the threshold. This alarm occurs when the operating temperature of the pump laser on
the optical amplifier unit crosses the threshold.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 and 2 Indicates the optical port where the alarm is generated.
Parameter 3 Indicates the threshold crossing type. For example, 0x01 indicates the
upper threshold is crossed and 0x02 indicates the lower threshold is
crossed.
Impact on the System
The pump laser may be aged. Report of this alarm has no impact on the services. If no
measure is taken, however, the output optical power of the board is affected in a period of
time. This affects the services.
Possible Causes
l The ambient temperature is excessively high or excessively low.
l The cooling system of the pump laser is damaged.
l The pump laser has excessive current.
Procedure
Step 1 Check whether the ambient temperature is normal. If not, improve it.
Step 2 If the alarm persists, perform a warm reset on the faulty board through the NMS.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect services.
Step 4 If the alarm persists, replace the faulty board.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 691
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.406 PUMP_COOL_EXC
Description
This alarm indicates that the cooling current of the pump laser exceeds the threshold. This
alarm is generated when the laser cooling current is higher than the upper threshold or lower
than the lower threshold.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Impact on the System
When this alarm is reported, the laser ages sharply and the performance of output signals
degrades.
Possible Causes
l Cause 1: The ambient temperature is excessively high or low.
l Cause 2: The pump laser temperature is excessively high or low.
l Cause 3: The board that reports this alarm is faulty.
Procedure
l Cause 1: The ambient temperature is excessively high or low.
a. Check the ambient temperature inside the telecommunications room, and heat
dissipation through fans. For details, see TEMP_OVER to rectify the fault.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for causes 2 and 3.
l Causes 2: The pump laser temperature is excessively high or low/Cause 3: The board
that reports this alarm is faulty.
a. If the alarm persists, replace the faulty board.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 692
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.407 PW_APS_DEGRADED
Description
The PW_APS_DEGRADED alarm indicates that a pw APS protection group degrades. This
alarm is reported when the protection pw in a pw APS protection group fails and is cleared
after the protection pw recovers.
NOTE
This alarm is also cleared when the working and protection pws of the group fail.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None.
Impact on the System
The pw APS protection group cannot perform protection switching.
Possible Causes
Possible causes of the PW_APS_DEGRADED alarm are as follows:
l The port connected to the protection pw is disabled.
l Fiber connections are incorrect.
l The protection pw is faulty.
Procedure
Step 1 Query the status of the pw APS protection group on the U2000 and identify the protection pw.
Step 2 Check whether the port connected to the protection pw is disabled.
If... Then...
The pw port is disabled Enable the port. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The pw port is enabled Go to the next step.
Step 3 Check whether fiber connections to the port that is connected to the protection pw are
incorrect.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 693
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Fiber connections are incorrect or fibers are Rectify the incorrect fiber connections or
faulty replace the faulty fibers. Check whether the
alarm is cleared. If the alarm persists, go to
the next step.
Fiber connections are correct Go to the next step.
Step 4 Check whether the port connected to the protection pw reports any alarms.
If... Then...
The port reports alarms Clear these alarms first. Check whether the
PW_APS_DEGRADED alarm is cleared. If
the PW_APS_DEGRADED alarm persists,
go to the next step.
The port reports no alarm Go to the next step.
Step 5 Contact Huawei technical support engineers to handle the PW_APS_DEGRADED alarm.
----End
Related Information
None.
4.2.408 PW_APS_OUTAGE
Description
The PW_APS_OUTAGE alarm indicates that a pw APS protection group fails. This alarm is
reported when both the protection and working pws in a pw APS protection group fail, and is
cleared when either of the protection or working pw recovers.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None
Impact on the System
The pw APS group fails and services in the group are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 694
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: Ports carrying the working and protection pws are not enabled.
l Cause 2: Fibers connections are faulty.
l Cause 3: Alarms occur on both the working and protection pws.
Procedure
Step 1 Query the status of the pw APS protection group on the U2000 and identify the working and
protection pws.
Step 2 Cause 1: Ports carrying the working and protection pws are not enabled.
1. Check whether ports carrying the working and protection pws are enabled. If they are not
enabled, enable them.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: Fibers connections are faulty.
1. Replace the faulty fibers or connect the fibers correctly.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 3: Alarms occur on both the working and protection pws.
1. Check for alarms, such as 4.2.258 MPLS_PW_LOCV, on the working and protection
pws. If such an alarm occurs, clear the alarm first.
2. Check whether the PW_APS_OUTAGE alarm is cleared. If the alarm persists, contact
Huawei technical support personnel to handle the alarm.
----End
Related Information
None
4.2.409 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC alarm indicates that a PW does not receive or transmit any traffic.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 695
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the direction in which the traffic is unavailable.
l 0x00: Rx direction
l 0x01: Tx direction
NOTE
Parameter 1 has a fixed value of 0x00.
Impact on the System
Services that have been configured on the port are interrupted.
Possible Causes
Possible causes of the PW_NO_TRAFFIC alarm are as follows:
l No service is configured on the alarmed port.
l The local services are abnormal and therefore no packet is transmitted to the opposite
end.
l The opposite services are abnormal and therefore no packet is transmit to the local end.
l The alarmed port works improperly.
Procedure
Step 1 Determine the alarmed board, alarmed port, and direction in which the traffic is unavailable
according to the alarm information on the U2000
Step 2 Check whether services have been configured on the alarm port.
If... Then...
No service has been configured Configure services on the port correctly.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
Services have been configured Go to the next step.
Step 3 Check whether the local service configurations are correct.
If... Then...
The local service configurations are Rectify the service configurations. Check
incorrect whether the alarm is cleared. If the alarm
persists, go to the next step.
The local service configurations are correct Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 696
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 Check whether the opposite service configurations are correct.
If... Then...
The opposite service configurations are Rectify the service configurations. Check
incorrect whether the alarm is cleared. If the alarm
persists, go to the next step.
The opposite service configurations are Go to the next step.
correct
Step 5 Replace the alarmed board and check whether the alarm is cleared.
If... Then...
The alarm persists Replace the opposite board. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The alarm is cleared No further operation is required.
Step 6 Contact Huawei technical support engineers for handling the alarm.
----End
Related Information
None.
4.2.410 PWAPS_LOST
Description
The PWAPS_LOST alarm indicates that no PW APS frame is received from the protection
channel of a PW APS protection group.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
Service protection fails.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 697
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the PWAPS_LOST alarm are as follows:
l The opposite NE is not configured with PW APS protection.
l The PW APS protocol is disabled on the opposite NE.
l The service on the protection channel of a PW APS protection group is interrupted.
Procedure
Step 1 On the U2000, check whether the opposite NE is configured with PW APS protection.
If... Then...
The opposite NE is Go to the next step.
configured with PW APS
protection
The opposite NE is not Configure PW APS protection on the opposite NE according
configured with PW APS to the NE planning information. Ensure that the
protection configuration on the opposite NE is consistent with the
configuration on the local NE. Then, enable the APS
protocol. Check whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 2 Check whether the PW APS protocol is enabled on the opposite NE.
If... Then...
The protocol is enabled Go to the next step.
The protocol is disabled Disable the PW APS protocol on the local NE and then enable
the protocol at both ends. Check whether the alarm is cleared. If
the alarm persists, go to the next step.
Step 3 Check whether the protection channel reports an alarm indicating signal loss or signal
degrade.
If... Then...
An alarm indicating signal loss or Rectify the fault on the protection channel and
signal degrade is reported check whether the alarm is cleared. If the alarm
persists, go to the next step.
No alarm indicating signal loss or Go to the next step.
signal degrade is reported
Step 4 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 698
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.411 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH alarm indicates that the working and protection paths in the
PW APS protection group on the local NE are inconsistent with those in the related PW APS
protection group on the opposite NE.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
Service protection fails.
Possible Causes
Possible causes of the PWAPS_PATH_MISMATCH alarm are as follows:
l The configured working and protection paths differ between both ends.
l The physical link is connected incorrectly.
Procedure
Step 1 On the U2000, check whether the PW APS protection group settings are consistent at both
ends.
If... Then...
The settings are consistent Go to the next step.
The settings are Modify the settings of PW APS protection groups to make
inconsistent settings at both ends consistent, and check whether the alarm
is cleared. If the alarm persists, go to the next step.
Step 2 Check whether an optical fiber or a cable is incorrectly connected between both ends.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 699
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
An optical fiber or cable is Rectify the connection or service configurations based
incorrectly connected on the actual networking scenario. Check whether the
alarm is cleared. If the alarm persists, go to the next
step.
No optical fiber or cable is Go to the next step.
incorrectly connected
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.412 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL alarm indicates a switching failure in the PW APS protection
group. This alarm is reported when the request signals in the transmitted Automatic Protection
Switching (APS) frame are different from the bridge signals in the received APS frame and
this symptom lasts for 50 ms.
Attribute
Alarm Severity Alarm Type
Minor Processing
Parameters
None.
Impact on the System
Protection switching fails.
Possible Causes
Possible causes of the PWAPS_SWITCH_FAIL alarm are as follows:
The parameter values of the PW APS protection groups at two ends are inconsistent.
Procedure
Step 1 On the U2000, check whether the settings of the PW APS protection groups are consistent at
both ends. For example, "Protection Group ID", "Protection Type", and "Protection Mode".
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 700
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
All parameter values are Go to the next step.
consistent
Parameter values are Modify the parameter settings of the PW APS protection
inconsistent groups to be consistent and check whether the alarm is
cleared. If the alarm persists, go to the next step.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.413 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH alarm indicates that the local NE and the opposite NE are
configured with different PW protection types. This alarm is reported when the PW protection
type indicated in the received automatic protection switching (APS) frame is different from
that specified on the local NE.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
Service protection may fail.
Possible Causes
Possible causes of the PWAPS_TYPE_MISMATCH alarm are as follows:
l The protection mode is different.
l The switching mode is different.
l The revertive mode is different.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 701
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 On the U2000, check whether the PW APS protection group settings (for example, protection
mode, switching mode, and revertive mode) at the local and opposite ends are consistent.
If... Then...
Some parameter values Modify the settings of PW APS protection groups to make
are inconsistent settings at both ends consistent. Enable the PW APS protocol
and check whether the alarm is cleared. If the alarm persists,
go to the next step.
All parameter values are Go to the next step.
consistent
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.414 PWD_ENCRYPT_RISK
Description
The PWD_ENCRYPT_RISK alarm indicates that the user password encryption mode of an
NE has security risks. If the user password encryption mode of an NE is MD5 or SHA256,
this alarm is reported when you log in to the NE, change the user password, or create an NE
user.
Attribute
Alarm Severity Alarm Type
Major Security
Parameters
None
Impact on the System
The user password may be cracked.
Possible Causes
The possible cause of the alarm is as follows:
The user password encryption mode of the NE is MD5 or SHA256.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 702
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Change the user password encryption mode to PBKDF2 on the NMS.
1. On the Main Topology, right-click the required NE and choose NE Explorer from the
shortcut menu.
2. In the NE Explorer, click the NE and choose Security > NE User Password Encryption
Management.
3. Change Encryption Type to PBKDF2.
4. Click Apply.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.415 PWR_MAJ_ALM
Description
The PWR_MAJ_ALM is an alarm of power supply overvoltage or undervoltage.
Attribute
Alarm Severity Alarm Type
Critical Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: Indicates the power supply 1 which the alarm occurs.
l 0x02: Indicates the power supply 2 which the alarm occurs.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 703
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2 l 0x01: Indicates undervoltage of the power supply.
l 0x02: Indicates overvoltage of the power supply.
Parameter 3 l 0x00: Indicates the -220V power voltage.
l 0x01: Indicates the -48V AC/DC power voltage.
l 0x02: Indicates the -48V battery voltage.
l 0x03: Indicates the -5V DC/DC power voltage.
Impact on the System
The PWR_MAJ_ALM alarm affects the power supply of the system. This can cause the NE
to be abnormal.
Possible Causes
The possible causes of the PWR_MAJ_ALM alarm are as follows:
l Cause 1: The AC power is off.
l Cause 2: The DC power is undervoltaged or overvoltaged.
Procedure
Step 1 Cause 1: The AC power is off.
1. Find the power off cause. Then restore the power supply in a timely manner and check
whether the alarm is cleared.
Step 2 Cause 2: The DC power is undervoltaged or overvoltaged.
1. Replace the power board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
4.2.416 PWR_TEMP_OVERTH
Description
The PWR_TEMP_OVERTH alarm indicates that the temperature of the power module
crosses the specified threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 704
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the power module whose temperature crosses the
specified threshold.
Impact on the System
When this alarm is reported, a board may report a temperature-related alarm, and work
unstably.
Possible Causes
Possible causes of the PWR_TEMP_OVERTH alarm are as follows:
l Fans are faulty.
l The ambient temperature is high.
l The power module is faulty.
Procedure
Step 1 Check whether the fans are working normally.
If... Then...
The fans stop working or are faulty Restart or replace the fans. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The fans are working normally Go to the next step.
Step 2 Check whether the ambient temperature is high.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 705
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The ambient temperature is high Decrease the ambient temperature to the
specified range, and then check whether the
alarm is cleared. If the alarm persists, go to
the next step.
The ambient temperature is normal Go to the next step.
Step 3 Check whether the power module is faulty.
If... Then...
The power module is faulty Replace the power board with a functioning
one, and then check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The power module works normally Contact Huawei technical support engineers
for handling the alarm.
----End
Related Information
None.
4.2.417 R_APS
Description
The R_APS alarm indicates that the line board fails to receive the K byte.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
When the R_APS alarm occurs, the line board fails to receive the K byte. If the services are
configured with MSP switching, the MSP switching will fail.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 706
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the R_APS alarm are as follows:
l The K bytes are inconsistent in any consecutive three frames of the 12 frames received
by the line board.
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...
The alarm is cleared Go to the next step.
The 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.
4.2.418 R_LOC
Description
The R_LOC alarm indicates loss of clock in the signals received by the line board at the
optical interface.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 707
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the actual number of the optical interface on a board where
the alarm occurs.
For example, 0x01 indicates that the alarm is reported from optical
interface 1 of the board.
Parameter 2, Indicates the actual number of the optical interface on a board where
parameter 3 the alarm occurs.
For example, 0x01 indicates that the alarm is reported from optical
interface 1 of the board.
Impact on the System
When the R_LOC alarm occurs, the clock in the signals received by the line board at the
optical interface is lost. As a result, the services at the optical interface are unavailable. If the
automatic MSP switching or the path protection switching is configured, the alarm will trigger
the protection switching. If the optical interface that reports the R_LOC alarm is the current
synchronization clock source for the NE, the synchronization clock source switching will
occur.
When the R_LOC alarm occurs, the board reports the MS_RDI alarm to the opposite station.
Possible Causes
Possible causes of the R_LOC alarm are as follows:
l The clock in the received line signals is lost.
Procedure
Step 1 If receive part of the local line board is faulty, replace the board.
----End
Related Information
None.
4.2.419 R_LOF
Description
The R_LOF alarm indicates loss of frame in the signals received by the line board at the
optical interface.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 708
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number.
Impact on the System
When the R_LOF alarm occurs, the frame in the signals received by the line board at the
optical interface is lost. As a result, the services at the interface are unavailable. If the
automatic MSP switching or the path protection switching is configured, the alarm will trigger
the protection switching. If the optical interface that reports the R_LOF alarm is the current
synchronization clock source for the NE, the synchronization clock source switching will
occur.
When the R_LOF alarm occurs, the board reports the MS_RDI alarm to the opposite station.
Possible Causes
Possible causes of the R_LOF alarm are as follows:
l The rates of the optical interfaces at both ends are inconsistent.
l The fiber connector is loose or dirty.
l The transmission fiber cable is faulty.
l The attenuation of the received signal is excessive.
l The signals transmitted at the opposite station do not have the frame structure.
l The receive part at the local station is faulty.
Procedure
Step 1 Check the rates of the optical interfaces at both 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 are in good contact.
Replace the fiber or clean the fiber connectors.
Step 3 Check whether the transmission fiber cable is faulty. If 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 709
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared The fault is rectified.
The alarm persists Go to the next step.
Step 5 Check the levels of the optical interfaces configured at the line boards. If the levels are
different, change them and apply the configurations.
Step 6 View alarms on the NMS to check whether the R_LOF alarm is cleared.
If... Then...
The alarm is cleared The fault is rectified.
The alarm persists Go to the next step.
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. If 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 is cleared The fault is rectified.
The alarm persists Go to the next step.
Step 9 If the local line board is faulty, replace it.
----End
Related Information
None.
4.2.420 R_LOS
Description
The R_LOS alarm indicates loss of signal at the receive optical interface on the line board.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 710
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When the R_LOS alarm occurs, the signal at the receive optical interface on the line board is
lost. As a result, the services are interrupted. If the automatic MSP switching or the path
protection switching is configured, the alarm will trigger the protection switching. If the
optical interface that reports the R_LOS alarm is the current synchronization clock source for
the NE, the synchronization clock source switching will occur.
When the R_LOS alarm occurs, the board reports the MS_RDI alarm to the opposite station.
Possible Causes
Possible causes of the R_LOS alarm are as follows:
l The laser of the opposite line board is disabled.
l The fiber cut occurs on the connected fibers.
l The line is heavily attenuated or the optical power is overloaded.
l The transmitter of the opposite station or line transmission fails.
l The receive part of the local line board is faulty.
Procedure
Step 1 Check whether the fibers are intact and whether the fiber connectors are in good contact.
Replace the fiber or clean the fiber connectors.
Step 2 Remove the fault of the fibers. View alarms on the NMS to check whether the R_LOS alarm
is cleared.
If... Then...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
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 it on. If the receive optical
power is overloaded, add an 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...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 5 If the local line board is faulty, replace the optical module and faulty board at the local station.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 711
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.421 R_OOF
Description
The R_OOF alarm indicates that the frame header cannot be identified for five consecutive
frames in the received signals of the line board. The board changes to the out-of-frame state.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None.
Impact on the System
The frame header cannot be identified for five consecutive frames in the received signals of
the line board. The board changes to the out-of-frame state. As a result, the services are
unavailable.
If the out-of-frame state lasts 3 ms, the board changes to the loss-of-frame state. The
equipment generates the R_LOF alarm indicating the loss of frame.
Possible Causes
Possible causes of this alarm are as follows:
l The fiber connector is loose or dirty.
l Signals are heavily attenuated or have excessive bit errors.
l The transmission fiber is faulty.
l The synchronization clock source is out of synchronization.
l The transmit unit of the opposite end is faulty.
l The receive unit of the local end is faulty.
Procedure
Step 1 Check whether the fiber is intact and whether the fiber connector is clean and connected
correctly.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 712
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The fiber is damaged Replace the fiber. Check whether the alarm
is cleared. If the alarm persists, go to the
next step.
The fiber connector is dirty or connected Clean the fiber connector and connect the
incorrectly fiber correctly. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The fiber is intact and the fiber connector is Go to the next step.
clean and connected correctly
Step 2 Check whether the transmission fiber is normal.
If... Then...
The transmission fiber is faulty Replace the fiber. Check whether the alarm
is cleared. If the alarm persists, go to the
next step.
The transmission fiber is normal Go to the next step.
Step 3 Check whether the receive optical power is normal.
If... Then...
The receive optical power is heavily The opposite line board is faulty. Replace
attenuated the faulty board. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The receive optical power is normal Go to the next step.
Step 4 Check whether the synchronization clock source is normal.
If... Then...
The synchronization clock source is out of Trace a high-quality clock source. Check
synchronization whether the alarm is cleared. If the alarm
persists, go to the next step.
The synchronization clock source is normal Replace the local line board. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
Step 5 Contact Huawei technical support engineers for handling the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 713
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.422 R_S_ERR
Description
The R_S_ERR alarm indicates 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.
Impact on the System
When the R_S_ERR alarm occurs, the services are interrupted.
Possible Causes
Possible causes of the R_S_ERR alarm are as follows:
l The frequency offset of the input signal is large.
l The board is faulty.
Procedure
Step 1 Check whether the tributary board supports the type of the input signal.
If... Then...
The tributary board does not support the type Change the type of the output signal of
of the input signal the opposite station.
The tributary board supports the type of the Go to the next step.
input signal
Step 2 Test the frequency offset of the input signal.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 714
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The frequency offset is large Troubleshoot the opposite station.
The frequency offset meets the requirement Go to the next step.
Step 3 Replace the board that reports the alarm.
----End
Related Information
None.
4.2.423 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL alarm indicates critical alarm inputs. This alarm occurs
when the user sets the severity of an available alarm input to critical and some critical alarms
are input.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the alarm input.
Impact on the System
The RELAY_ALARM_CRITICAL alarm does not affect the operation of the system control,
switching, and timing board 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 715
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View the RELAY_ALARM_CRITICAL alarm on the U2000. Confirm the number of the
alarm input according to Parameter 1.
Step 2 Cut off the alarm input. Then the RELAY_ALARM_CRITICAL alarm is automatically
cleared.
----End
Related Information
None.
4.2.424 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE alarm indicates warning alarm inputs. This alarm occurs
when the user sets the severity of an available alarm input to warning and some warning
alarms are input.
Attribute
Alarm Severity Alarm Type
Warning 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the alarm input. The value ranges from 0x01 to 0x08.
Impact on the System
The RELAY_ALARM_IGNORE alarm does not affect the operation of the system control,
switching, and timing board or the services on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_IGNORE alarm is as follows:
l The alarm input port reports this alarm by default.
l There is a warning alarm input.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 716
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View the RELAY_ALARM_IGNORE alarm on the U2000. Confirm the number of the alarm
input according to Parameter 1.
Step 2 Check whether the alarm input port reports this alarm by default.
If... Then...
The alarm input port reports this alarm by Cancel this default setting. Check whether
default the alarm is cleared. If the alarm persists, go
to the next step.
The alarm input port does not report this Go to the next step.
alarm by default
Step 3 Cut off the alarm input. Then the RELAY_ALARM_IGNORE alarm is automatically cleared.
----End
Related Information
None
4.2.425 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR alarm indicates major alarm inputs. This alarm occurs when
the user sets the severity of an available alarm input to major and some major alarms are
input.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the alarm input. The value ranges from 0x01 to 0x08.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 717
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The RELAY_ALARM_MAJOR alarm does not affect the operation of the system control,
switching, and timing board or the services on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_MAJOR alarm is as follows:
l The alarm input port reports this alarm by default.
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
input according to Parameter 1.
Step 2 Check whether the alarm input port reports this alarm by default.
If... Then...
The alarm input port reports this alarm by Cancel this default setting. Check whether
default the alarm is cleared. If the alarm persists, go
to the next step.
The alarm input port does not report this Go to the next step.
alarm by default
Step 3 Cut off the alarm input. Then the RELAY_ALARM_MAJOR alarm is automatically cleared.
----End
Related Information
None.
4.2.426 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR alarm indicates minor alarm inputs. This alarm occurs when
the user sets the severity of an available alarm input to minor and some minor alarms are
input.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 718
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the alarm input. The value ranges from 0x01 to 0x08.
Impact on the System
The RELAY_ALARM_MINOR alarm does not affect the operation of the system control,
switching, and timing board or the services on the NE.
Possible Causes
The possible cause of the RELAY_ALARM_MINOR alarm is as follows:
l The alarm input port reports this alarm by default.
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
input according to Parameter 1.
Step 2 Check whether the alarm input port reports this alarm by default.
If... Then...
The alarm input port reports this alarm by Cancel this default setting. Check whether
default the alarm is cleared. If the alarm persists, go
to the next step.
The alarm input port does not report this Go to the next step.
alarm by default
Step 3 Cut off the alarm input. Then the RELAY_ALARM_MINOR alarm is automatically cleared.
----End
Related Information
None
4.2.427 RELAY_LOF
Description
The RELAY_LOF alarm indicates that the receiving frames of the dry contact signal
transmission are lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 719
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When this alarm occurs, services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The service frame format is incorrectly configured.
l The transmit board (including the cross-connect and timing board) at the opposite end is
faulty, and therefore the frame structure is lost.
l The receive board (including the cross-connect and timing board) at the local end is
faulty, and therefore the frame structure is lost.
Procedure
Step 1 The service frame format is incorrectly configured.
1. Check whether the frame format of the receive board at the local end is consistent with
that of the transmit board at the opposite end. Ensure that the service configuration is
correct.
If... Then...
The frame formats are inconsistent Check the frame format of the transmit
board at the opposite end, correctly
configure services on the NMS, and
ensure that the frame formats at both ends
are consistent. Then, check whether the
RELAY_LOF alarm is cleared. If the
RELAY_LOF alarm persists, go to the
next step.
The frame formats are consistent Go to the next step.
Step 2 Cause 1 and cause 2: The transmit board (including the cross-connect and timing board) at the
opposite or local end is faulty, and therefore the frame structure is lost.
1. Check whether the TU_AIS or DOWN_E1_AIS alarm occurs on the board at the local
end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 720
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The TU_AIS or DOWN_E1_AIS alarm is Refer to the corresponding section in this
reported document to clear the TU_AIS,
DOWN_E1_AIS. Then, check whether
the RELAY_LOF alarm is cleared. If the
RELAY_LOF alarm persists, go to the
next step.
No TU_AIS or DOWN_E1_AIS alarm is Go to the next step.
reported
Step 3 Replace the board that reports this alarm. For details about how to replace a specific board,
see Parts Replacement of the Maintenance Guide. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.428 RFA
Description
The RFA is an alarm indicating that the framing E1/T1 frame notification event occurs. If the
framing E1/T1 signals occur in consecutive Z (Z is from two through five) double-frame
cycles, the RFA alarm is reported when the RDI bit of the input signals is set to 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
When the RFA alarm occurs, the services at the local station are not affected. This alarm just
shows that the LFA alarm occurs at the opposite end.
Possible Causes
The possible cause of the RFA alarm is as follows:
The LFA alarm occurs at the remote end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 721
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check whether the LFA alarm occurs at the opposite end of the path corresponding to the
board that reports the alarm. If yes, clear the LFA alarm at the opposite end. Then the RFA
alarm at the local end is cleared accordingly.
----End
Related Information
None.
4.2.429 RMFA
Description
The RMFA is an alarm that the framing E1/T1 multiframe notification event occurs. If the
framing E1/T1 signals occur in consecutive Z (Z is from two through five) CAS multiframe
cycles, the RMFA alarm is reported when all the CAS multiframe mutual-notification bits of
the input signals are set to 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Impact on the System
When the RMFA alarm occurs, the services at the local station are not affected. This alarm
just shows that the LMFA alarm occurs at the opposite station.
Possible Causes
The possible cause of the RMFA alarm is as follows:
The LMFA alarm occurs at the remote end.
Procedure
Step 1 Check whether the LMFA alarm occurs at the opposite end of the path corresponding to the
board that reports the alarm. If yes, clear the LMFA alarm at the opposite end. Then the
RMFA alarm at the local end is cleared accordingly.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 722
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.430 RTS
Description
The RTS is an alarm indicating that the Request To Send status of the DCE is abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
When the RTS alarm occurs, the DCE fails to transmit services. Consequently, the services
are interrupted.
Possible Causes
The possible cause of the RTS alarm is as follows:
The DTE at the opposite end works abnormally because the cable is improperly connected, or
the service configuration is incorrect.
Procedure
Step 1 Check whether the DTE at the opposite end works well by following the actions:
1. Check whether the cable is faulty. If yes, remove the fault.
2. Check whether the service configuration is correct, including the settings of DTE and
DCE, inter, slave or exter. Make sure that the service configuration is correct.
After making sure that the DTE at the opposite end works well, the RTS alarm is
automatically cleared.
----End
Related Information
None.
4.2.431 RS_CROSSTR
Description
The RS_CROSSTR alarm indicates that the regenerator section performance of the line board
crosses the threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 723
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Service 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 details
about each parameter, refer to the following 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
Parameter 2, Indicate the performance event that causes the alarm.
parameter 3
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.
Impact on the System
When the RS_CROSSTR alarm occurs, the regenerator section performance of the line board
crosses the threshold. As a result, the services are affected.
Possible Causes
The possible cause of the RS_CROSSTR alarm is as follows:
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 See the corresponding section in this
document to clear the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 724
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The B1_EXC or B1_SD alarm is not Go to the next step.
reported
Step 2 Perform a loopback for the stations at both ends of the line. Locate and replace the faulty line
board.
----End
Related Information
None.
4.2.432 RTC_FAIL
Description
The RTC_FAIL alarm indicates a real-time clock (RTC) failure on the system control,
switching, and timing board. This alarm occurs when the clock of the system control,
switching, and timing board is faulty.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on the System
When this alarm occurs, the time stamp precision of the system decreases, resulting in service
interruptions.
Possible Causes
The possible cause of the RTC_FAIL alarm is as follows:
l The board temperature is high.
l The RTC chip of the system control, switching, and timing board is damaged.
Procedure
Step 1 Lower the board temperature. Check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 725
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 2 Replace the system control, switching, and timing board of the corresponding equipment.
----End
Related Information
None.
4.2.433 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE alarm indicates 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
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 details
about each parameter, refer to the following table.
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
Impact on the System
When the S1_SYN_CHANGE alarm occurs, the clock reference source of the clock board is
switched to other synchronization clock sources in the S1 byte mode, due to the failure in the
line source or tributary source or external clock source that is set in the clock source priority
table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 726
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the S1_SYN_CHANGE alarm are as follows:
l A fiber cut or a cable cut occurs.
l The external BITS is broken.
l Clock switching occurs at the uplink station.
l 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...
There is the R_LOS, R_LOC, R_LOF, See the corresponding section in this
T_ALOS, or EXT_SYNC_LOS alarm. document to clear the alarm.
There are such alarms as the MS_AIS and See the corresponding section in this
B2_EXC, and these alarms are set as document to clear the alarm.
conditions that can trigger the clock
switching
There is no alarm Go to the next step.
Step 2 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
4.2.434 SEC_RADIUS_FAIL
Description
The SEC_RADIUS_FAIL alarm indicates that the number of consecutive RADIUS
authentication failures is too great. This alarm is reported when the number of consecutive
RADIUS authentication failures reaches five. (If the interval between two RADIUS
authentication failures is less than 180 seconds, they are considered as consecutive RADIUS
authentication failures.)
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 727
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the user name (16 bits in length).
Impact on the System
Logins to an NE fail.
Possible Causes
Possible causes of the SEC_RADIUS_FAIL alarm are as follows:
l The usage period of the account expires.
l The password, access policy, or shared key of the account is changed.
l There are unauthenticated login attempts on the RADIUS server.
Procedure
Step 1 Check whether the usage period of the account expires.
If... Then...
The usage period of the account expires Use a valid account to log in to the NE.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The usage period of the account is still valid Go to the next step.
Step 2 Check whether the password or access policy of the account is changed on the RADIUS
server.
If... Then...
The password or access policy of the Correct the password or access policy of the
account is incorrect account. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The password and access policy of the Go to the next step.
account are correct
Step 3 Check whether the shared key for the NE (or GNE) and the RADIUS server is set correctly.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 728
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The shared key is set incorrectly Set the shared key correctly. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The shared key is set correctly Go to the next step.
Step 4 Check whether there are unauthenticated login attempts on the RADIUS server.
If... Then...
There are unauthenticated login attempts on Eliminate the source that initiates the
the RADIUS server unauthenticated login attempts. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
There is no unauthenticated login attempt Contact Huawei technical support engineers
on the RADIUS server to handle the alarm.
----End
Related Information
None.
4.2.435 SECU_ALM
Description
The SECU_ALM alarm indicates that the system control, switching, and timing board reports
an unauthorized login.
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 details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 729
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 type of 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.
Impact on the System
The SECU_ALM alarm indicates that the system control, switching, and timing board reports
a security alarm of unauthorized login. If wrong user passwords are entered for five
consecutive times, the user account is locked for the time being. In this case, wait for 900
seconds and then try to log in again.
This alarm does not affect the system and will be cleared automatically.
Possible Causes
The possible cause of the SECU_ALM alarm is as follows:
l The password is incorrectly entered for five consecutive times during the login, or the
user name does not exist.
l A board is faulty.
Procedure
Step 1 Obtain the correct user name and password from the administrator. After the user account is
unlocked, log in again.
Step 2 If login attempts fail, contact Huawei technical support engineers for handling the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 730
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.436 SERVICE_CAPACITY_EXCEED_LICENSE
Description
The SERVICE_CAPACITY_EXCEED_LICENSE alarm indicates that the capacity of the
services configured for a equipment exceeds the limit defined by the license.
Attribute
Alarm Severity Alarm Type
Major QoS alarm
Parameters
None
Impact on the System
When this alarm occurs, the existing services and the system are not affected but the alarm-
related services cannot be configured on the alarm-reporting equipment.
Possible Causes
The capacity of the services configured for the equipment exceeds the limit defined by the
license.
Procedure
Step 1 If an appropriate license is unavailable, purchase one from Huawei.
----End
Related Information
None
4.2.437 SERVICE_TYPE_EXCEED_LICENSE
Description
The SERVICE_TYPE_EXCEED_LICENSE alarm indicates that the service type exceeds the
license limit. The alarm indicates that the type of configured services exceeds the license
limit.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 731
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Service
Parameters
None
Impact on the System
When the SERVICE_TYPE_EXCEED_LICENSE alarm is generated, neither the existing
services nor the operation of the system is affected. The equipment where the alarm is
generated, however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service type configured in the equipment exceeds the license limit.
Procedure
Step 1 According the alarm parameter, check whether the type of configured services in the
equipment exceeds the license limit by using the NMS.
Step 2 If yes, assign a proper license.
Step 3 If no proper license is available, purchase the license with a higher version from Huawei.
----End
Related Information
None
4.2.438 SLAVE_WORKING
Description
The SLAVE_WORKING alarm indicates 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 732
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x00.
Parameter 2 The value is always 0x00.
Parameter 3 Indicates the slot ID of the cross-connect board.
Impact on the System
When the SLAVE_WORKING alarm occurs, the system is not affected. This alarm only
indicates 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
Possible causes of this alarm are as follows:
l The working cross-connect and timing board cannot be detected.
l The working cross-connect and timing board is faulty.
l The service board is faulty.
l The active/standby status bus of the cross-connect and timing board is damaged.
l The connection bus between the line board and the working cross-connect and timing
board is damaged.
Procedure
Step 1 Check whether the active cross-connect board is installed securely.
If... Then...
The active cross-connect board is loose Install the active cross-connect board
securely. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The active cross-connect board is installed Go to the next step.
securely
Step 2 Perform a cold reset for the active cross-connect and timing board by using the NMS or reseat
the board. Check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 733
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 3 Replace the active cross-connect and timing board, and check whether the alarm is cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 4 Perform a cold reset for the alarmed service board by using the NMS or reseat this board.
Check whether the alarm is cleared.
If the service on the board is not protected, a cold reset on the board causes service
interruptions.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 5 Replace the alarmed board and check whether the alarm is cleared.
If... Then...
The alarm persists Contact Huawei technical support engineers
for handling the alarm.
The alarm is cleared No further action is required.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 734
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.439 SOFTWARE_UNCOMMIT
Description
The SOFTWARE_UNCOMMIT alarm indicates that the board software is unauthorized. This
alarm is reported when the software version of a board is later than that of the system control
board and is unauthorized.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
The board runs improperly.
Possible Causes
Cause 1: The board software is unauthorized.
Procedure
Step 1 Load the software license to the board.
----End
Related Information
None
4.2.440 SRV_LOOP_LD
Description
The SRV_LOOP_LD alarm indicates that an Ethernet service loop occurs. This alarm is
reported when such a loop is detected.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 735
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 VLAN ID: Indicates the VLAN where a loop occurs.
Impact on the System
A service loop exists on the network.
Possible Causes
Cause 1: A service loop on the network is detected.
Procedure
Step 1 Cause 1: A service loop on the network is detected.
1. Identify the node that causes the loop and rectify it. Then, check whether the alarm is
cleared.
2. If the alarm persists, contact Huawei technical support engineers.
----End
Related Information
None
4.2.441 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD alarm indicates that the Ethernet private service is stopped. This
alarm is reported when the system detects a loopback on the Ethernet private service and stops
the service to prevent broadcast storm.
Attribute
Alarm Severity Alarm Type
Major Service 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 736
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 VLAN ID: Indicates the VLAN that is disabled.
Impact on the System
When this alarm is reported, the customer service is interrupted.
Possible Causes
The possible causes of the SRV_SHUTDOWN_LD alarm are as follows:
Cause: A loopback is detected on the Ethernet private service. Therefore, the service is
stopped.
Procedure
Step 1 Identify the fault according to the alarm. Query the shutdown Ethernet private service port
and release the loopback by configuring split horizon groups.
Step 2 Enable the shutdown Ethernet private service port to restore the Ethernet private service.
----End
Related Information
None.
4.2.442 SSL_CERT_DAMAGED
Description
The SSL_CERT_DAMAGED is an alarm indicating that a user-customized SSL certificate
file is damaged. This alarm is reported to notify the user to rectify the SSL certificate file and
is cleared after the file is rectified.
Attribute
Alarm Severity Alarm Type
Critical Security alarm
Parameters
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 737
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When this alarm occurs and the SSL certificate file is not rectified in time, the NE will be
unreachable to the NMS in SSL mode after the system control board of the NE is reset.
Possible Causes
Cause: The user-customized SSL certificate file is damaged.
Procedure
Step 1 Cause: The user-customized SSL certificate file is damaged.
1. Log in to the U2000, and load and activate the customized SSL certificate file again. For
details, see the section about loading board-level software in the iManager U2000
Product Documentation.
----End
Related Information
None
4.2.443 SSL_CERT_NOENC
Description
The SSL_CERT_NOENC alarm indicates that the Secure Sockets Layer (SSL) certificate file
is not encrypted.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
The private key information in the SSL certificate file is prone to interception.
Possible Causes
The possible cause of the SSL_CERT_NOENC alarm is as follows:
The SSL certificate file is not encrypted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 738
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Download and activate the SSL encryption certificate file.
----End
Related Information
None
4.2.444 SSL_CERT_TO_EXPIRE
Description
The SSL_CERT_TO_EXPIRE alarm indicates that the SSL certificate file is to expire or
expired.
Attribute
Alarm Severity Alarm Type
Critical Security alarm
Parameters
None
Impact on the System
If the customized SSL certificate file is not reloaded or activated in time, the NE cannot
communicate with the NMS through SSL after a reset.
Possible Causes
Cause: A customized SSL certificate file is to expire or expired.
Procedure
Step 1 Cause: A customized SSL certificate file is to expire or expired.
1. Log in to the U2000, and load and activate the customized SSL certificate file again. For
details, see the section about loading board-level software in the iManager U2000
Product Documentation.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 739
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.445 SSM_LOS
Description
This alarm indicates that the SSM quality information fails to be received. In SSM mode, this
alarm is reported when a reference source port configured in the priority table fails to obtain
valid SSM quality information within 5 seconds.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Impact on the System
This alarm triggers switching of the reference clock source.
Possible Causes
l The upstream NE sends invalid SSM quality information.
l In SSM mode, the NE fails to obtain valid SSM quality information.
Procedure
Step 1 On the NMS, check whether the SSM quality information is properly sent by the upstream
NE. If it is properly sent, check whether the upstream and local NEs are properly
interconnected.
Step 2 The alarm is cleared when valid SSM quality information is received.
----End
Related Information
None
4.2.446 SSM_QL_FAILED
Description
This alarm indicates that the received SSM quality is worse than the threshold. This alarm is
reported when the SSM quality received by a reference source port configured in the priority
table is worse than the threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 740
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Impact on the System
If the alarm is generated, the NE has to choose another timing source if available or has to go
into hold-over mode.
Possible Causes
The received SSM quality is worse than the configuration of SSM quality.
Procedure
Step 1 Query the received SSM quality on the NMS. Check whether the SSM quality is correct. If it
is incorrect, check whether the master NE traces the correct upstream NE.
Step 2 If the received SSM quality is correct, check whether the threshold is properly set based on
the network planning. If not, set the threshold again.
----End
Related Information
None
4.2.447 STORM_CUR_QUENUM_OVER
Description
The STORM_CUR_QUENUM_OVER alarm indicates a storm. When the number of current
alarms on the NE reaches the value that is equal to the maximum number of alarms supported
by an alarm queue minus one, the alarm is reported. The alarm cannot be wrapped by other
alarms on the NE.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 741
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When the alarm is reported, services are not affected. When the count of current alarms on the
NE reaches a certain value, the alarm is reported to prompt the user that the alarm queue is
full. In this case, certain alarms in the system control, switching, and timing board database
are lost due to the alarm storage mode.
Possible Causes
The possible cause of the STORM_CUR_QUENUM_OVER alarm is as follows:
The alarm queue is insufficient to contain all current alarms.
Procedure
Step 1 Check the queue of current alarms on the U2000. Identify and clear the frequently reported
alarms (STORM_CUR_QUENUM_OVER excluded). When the count of alarms in the alarm
queue is decreased to a specified value, the alarm is cleared automatically.
----End
Related Information
Alarm Storage
The NE register stores the alarm data by "Stopping" and "Wrapping". The NE uses the
"Wrapping" mode by default.
l When the storage mode is "Stopping", if the count of alarms reaches the capacity
threshold of the register, new alarms are discarded.
l When the alarm storage mode is "Wrapping", if the count of alarms reaches the capacity
threshold, new alarms overwrite earlier alarms and the new alarms are stored from the
start address of the register.
4.2.448 SUBNET_RT_CONFLICT
Description
The SUBNET_RT_CONFLICT alarm indicates that subnets conflict on a data communication
network (DCN). This alarm is reported when the subnet in which an NE resides and the
subnet in which a neighboring NE resides overlap.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 742
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
Name Meaning
Parameter 1 to Indicates the address of the conflicting subnet.
Parameter 4
NOTE
When the local subnet conflicts with multiple subnets, Parameter 1 to
Parameter 4 indicate the subnet address with the longest mask.
Parameter 5 Indicates the mask length of the conflicting subnet.
NOTE
When the local subnet conflicts with multiple subnets, Parameter 5 indicates
the length of the longest subnet mask.
Impact on the System
When an NE reports this alarm, the NE cannot be managed through its Ethernet port, and
even the PC connected to the NE fails to receive packets from the NE.
Possible Causes
The possible cause of the SUBNET_RT_CONFLICT alarm is as follows:
Cause: An NE (NE A) uses the longest prefix match rule to forward packets to a PC. If the
subnet address that NE A has learned from another NE (NE B) conflicts with the address of
the subnet in which NE A resides, and NE B has a longer subnet mask than NE A, NE A will
forward the packets to NE B, instead of the PC.
Figure 4-32 Networking diagram
Gateway NE NE4
10.12.0.11/24
NE1
NMS Router
10.12.0.1/24
NE3
DCN 10.12.0.10/24
10.168.0.1 10.168.0.100/24 10.12.0.2/24
NE2
10.12.0.12/16 PC B
10.12.0.9/24
PC A
10.12.0.13/16
Figure 4-32 shows a DCN, where NE1 is the gateway NE and connected to the NMS through
a router, and NE2 and NE4 are non-gateway NEs. The subnet addresses and masks of these
NEs are as follows:
l NE1: 10.12.0.1/24
l NE2: 10.12.0.12/16, PC A: 10.12.0.13/16
l NE3: 10.12.0.10/24, PC B: 10.12.0.9/24
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 743
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l NE4: 10.12.0.11/24
When attempting to send packets to PC A based on the addressing protocol (longest prefix
match rule), NE2 will identify NE1 as the destination, instead of PC A. As a result, PC A fails
to receive the packets from NE2.
Procedure
Step 1 Cause: An NE (NE A) uses the longest prefix match rule to forward packets to a PC. If the
subnet address that NE A has learned from another NE (NE B) conflicts with the address of
the subnet in which NE A resides, and NE B has a longer subnet mask than NE A, NE A will
forward the packets to NE B, instead of the PC.
1. View Parameter 1 to Parameter 4 to determine the conflicting subnet address.
2. Locate the NE according to the conflicting address and Parameter 5.
3. Re-configure the subnet mask of the NE to ensure that all NEs on the DCN have the
same subnet mask. It is recommended that the subnet mask of the affected NE be set
consistently with that of gateway NE.
– Do not modify the subnet mask of the gateway NE, because the gateway NE may be
unreachable to the NMS after such a modification.
– If the subnet addresses of multiple NEs conflict, it is recommended that the subnet
mask of the NE farthest away from the gateway NE be modified first. If you modify
an NE nearer to the gateway NE, the NE may be unreachable to the NMS after the
modification.
– When you modify subnet masks, new SUBNET_RT_CONFLICT alarms may be
reported. Handle the alarms according to the specific networking scenario.
----End
Related Information
None.
4.2.449 SUBRATE_PROTOCOL_MM
Description
The SUBRATE_PROTOCOL_MM alarm indicates a rate mismatch of a sub-rate protocol
serial port.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 744
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None
Impact on the System
Sub-rate services are unavailable.
Possible Causes
Cause: The rate configured for sub-rate protocol serial ports is different from the actual rate of
the serial port that receives sub-rate services. For example, if the configured Serial Port Rate
(bps) is 19.2K(V.110 32K) but the actual rate (bit/s) of the serial port that receives sub-rate
services is 38.4K(V.110 64K), the SUBRATE_PROTOCOL_MM alarm is reported.
Procedure
Step 1 Cause: The rate configured for sub-rate protocol serial ports is different from the actual rate of
the serial port that receives sub-rate services.
1. Query the alarm on the NMS. Determine the board that reports the alarm, and determine
the number of the path that reports the alarm based on alarm parameters.
2. Check whether Serial Port Rate (bps) configured for the path is the same as the actual
rate for receiving sub-rate services. If they are different, modify the configuration based
on the type of received services. For details, see Configuring a PCM Port in the
Configuration Guide (SDH Transport Domain).
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
4.2.450 SUM_INPWR_HI
Description
The SUM_INPWR_HI alarm indicates that the input optical power is excessively high. The
alarm occurs when the input optical power of the multiplexed signals exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 745
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
The optical modules of the boards at the local station and downstream station may be
damaged. The services have bit errors, or are even interrupted.
Possible Causes
l The output optical power of the board at the upstream station is normal and the power of
the received optical signals accessed by the board at the local station is excessively high.
The proper attenuation is not added.
l The output optical power of the board at the upstream station or peer station is
excessively high.
l The board at the local station is faulty.
Procedure
Step 1 Check whether the input optical power of the input interface of the board at the local station is
within the normal range by using an optical power meter. If the power is not within the
normal range, add proper attenuation by placing a fixed attenuator or a VOA.
Step 2 If the alarm persists, check whether the output optical power of the board at the upstream
stations is within the normal range by using the NMS. If the input optical power of the board
at the local station is excessively high, handle the alarm according to the handling procedure
of the IN_PWR_HIGH alarm. If the output optical power of the boards at the upstream
stations is excessively high, respectively check whether the corresponding input and output
optical power of each upstream station are within the normal range.
l If the input and output optical power of the board at the upstream station are not within
the normal range, adjust the input optical power to a value within the normal range.
l If the input optical power of the board at the upstream station is within the normal range
but the output optical power is not, the board at the upstream station may be faulty.
Replace the faulty board.
Step 3 If the alarm persists, replace the faulty board.
----End
Related Information
None
4.2.451 SUM_INPWR_LOW
Description
Sum input optical power is excessively low. The alarm is generated when the input optical
power of the multiplexed signals is lower than the threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 746
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
The output optical signals of a single channel of the board may be lost; the services in use
may have bit errors or even are interrupted.
Possible Causes
l Cause 1: The output optical power of the upstream station decreases, and therefore the
input optical power of the local station is excessively low.
l Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber
connectors are dirty.
l Cause 3: The board that reports this alarm is faulty.
Procedure
l Check the alarm information on the NMS and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The output optical power of the upstream station decreases and therefore the
input optical power of the local station is excessively low.
a. On the NMS, check the output optical power of the boards at the upstream station
along the reverse direction of the signal flow. If the output optical power of a
certain board is excessively low, adjust the output optical power of the board to a
value within the normal range.
b. If the alarm persists, replace the board whose output optical power is excessively
low.
c. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber
connectors are dirty.
a. If the output optical power of all the boards at the upstream stations is normal,
check whether an optical attenuator with excessively high attenuation is attached to
the receive optical interface on the board that reports this alarm. If yes, decrease the
attenuation of the optical attenuator to a proper value or replace the optical
attenuator with a proper one.
b. If the alarm persists, check whether the attenuation of the built-in VOA in the
upstream boards is excessively high. If yes, adjust the attenuation of the VOA to a
proper value.
c. If the alarm persists, check whether related fibers or fiber connectors are dirty. If
yes, replace the fiber jumpers or check and clean the fiber connectors.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 747
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
d. If the alarm persists, the optical cables between stations may be faulty. In this case,
rectify the fault on the optical cables.
e. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports this alarm is faulty.
a. If the alarm persists, replace the faulty board.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.2.452 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT alarm indicates that during software package loading
or package diffusion, 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.
Impact on the System
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 on 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 or package diffusion is not complete. Proceed with the commit
operation.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 748
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.453 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH alarm indicates 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, switching, and timing
board.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Impact on the System
The board that reports the alarm cannot automatically match the software from the system
control, switching, and timing 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.
4.2.454 SWDL_BD_EXCLUDE
Description
The SWDL_BD_EXCLUDE alarm indicates that a board is excluded from software
download during software package downloading. This alarm occurs when some board failed
because of a failure to communicate with the SCC board or insufficient flash space.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 749
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
None
Impact on the System
After package loading or package diffusion, the software of the board excluded from software
download mismatches with the NE software. This may result in damage to services. Hence,
handle this alarm in time.
Possible Causes
l Cause 1: The board is offline.
l Cause 2: The communication between the board and the SCC board is abnormal.
l Cause 3: The flash memory space on the board is insufficient.
l Cause 4: The board is repeatedly reset after activation because of a board software fault.
Procedure
Step 1 On the DC window of the U2000, view the information about the boards that are isolated
during package loading or package diffusion.
Step 2 Check whether the isolated boards are offline. If the isolated boards are offline, get them
online.
Step 3 Check whether any COMMUN_FAIL alarm is reported on the isolated boards. If the alarm is
reported, handle the problem by referring to the alarm processing method.
Step 4 Check whether the flash memory space on the boards is sufficient. If the space is insufficient,
clean up the boards to get sufficient space.
Step 5 Check whether the downloaded software matches with the isolated board version. If the
software mismatches the board version, download the correct software again.
Step 6 If the preceding items are checked and the results are normal, select the isolated boards on the
DC window, download software again, and then activate the software.
Step 7 After handling all isolated boards, the SWDL_BD_EXCLUDE alarm is cleared when the
board isolation is released.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 750
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.455 SWDL_BD_MATCH_FAIL
Description
The SWDL_BD_MATCH_FAIL alarm indicates a board software matching failure. This
alarm is reported if matching the board software version to the NE version fails during an NE
upgrade or downgrade.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Impact on the System
The NE upgrade or downgrade fails.
Possible Causes
l Cause 1: An error occurs when data is read from or written to the board file system or
flash memory.
l Cause 2: Communication between the board and the system control board fails.
l Cause 3: Free space of the board is insufficient.
Procedure
l Cause 1: An error occurs when data is read from or written to the board file system or
flash memory.
Cause 2: Communication between the board and the system control board fails.
a. Warm reset the board.
b. If the alarm persists, cold reset the board.
c. If the alarm persists, replace the board.
d. If the alarm persists, go to Cause 3.
l Cause 3: Free space of the board is insufficient.
a. Contact Huawei technical support engineers to release board storage space.
NOTE
If the free space of the board is sufficient, the board automatically matches its software
version with the software version of the system control board, and the alarm is cleared upon
a match success.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 751
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.456 SWDL_BD_WEAKMATCH
Description
The SWDL_BD_WEAKMATCH alarm indicates weak version mapping.
Attribute
Alarm Severity Alarm Type
Minor Device alarm
Parameters
None
Impact on the System
None
Possible Causes
During an NE upgrade by means of package loading, if a board's software is compatible but
different from that in the upgrade package, it will not be upgraded; instead, a weak mapping
alarm will be reported.
Procedure
Step 1 After the package loading is completed, you can click a menu option of the DC tool to check
for all weak mapping boards.
Step 2 On the displayed window, select a specific weak mapping board, right-click, and choose to
upgrade the board software.
Step 3 After all weak mapping boards' software is upgraded, the alarm may clear.
Step 4 For detailed operations, refer to the specific product's upgrade guide.
Step 5 Check whether the alarm clears. If the alarm persists, contact Huawei engineers to handle the
alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 752
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.457 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH alarm indicates that the NE software does not match the
board software. This alarm is reported in the situation where the board version information is
inconsistent with that in the software package of the system control, switching, and timing
board or the software package information in the CF card on the system control, switching,
and timing board is inconsistent with that in the flash memory of the system control,
switching, and timing board after an NE is recycled and the board is online.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None.
Impact on the System
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 system control, switching, and timing board does not match the
software version of the board after the system control, switching, and timing board is
replaced.
Procedure
Step 1 Perform the package loading or package diffusion again on the NE where the
SWDL_CHGMNG_NOMATCH alarm is reported.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 753
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.458 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL alarm indicates that the commit operation on the NE fails. This
alarm is reported when the commit operation fails in the package loading or package
diffusion.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Impact on the System
The SWDL_COMMIT_FAIL alarm occurs only on double-area boards. 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 During package loading or package diffusion, the dual-partition board fails in copying
the new software from one partition to the other.
Procedure
Step 1 Check whether the board is not online.
Step 2 Check whether the loaded package is correct.
Step 3 Perform the package loading or package diffusion again on the NE where the alarm is
reported.
----End
Related Information
None.
4.2.459 SWDL_INPROCESS
Description
The SWDL_INPROCESS alarm indicates that the NE is loading the software package.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 754
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Warning Processing alarm
Parameters
None.
Impact on the System
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:
l The NE is loading the software package.
Procedure
Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback is
complete.
----End
Related Information
None.
4.2.460 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK alarm indicates 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 755
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
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 loading or package
diffusion again on the NE where the SWDL_NEPKGCHECK alarm is reported.
----End
Related Information
None.
4.2.461 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT alarm indicates 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.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Impact on the System
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 is removed during loading the customized software
package.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 756
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the
correct software package to perform package loading or package diffusion on the board. In
normal cases, this alarm is automatically cleared after the package loading or package
diffusion succeeds.
----End
Related Information
None.
4.2.462 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM alarm indicates 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.
Impact on the System
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 loading or package
diffusion again on the NE where the alarm is reported.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 757
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.463 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL alarm indicates that some board rollback fails when the NE
performs rollback. This alarm is reported when the rollback fails for a board on the NE.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Impact on the System
The board software version and the NE software version may mismatch. Some functions of
the NE may work 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 or package
diffusion.
Procedure
Step 1 Add the required board software to the software package. Alternatively, perform the software
package loading or package diffusion again.
----End
Related Information
None.
4.2.464 SYN_BAD
Description
The SYN_BAD alarm indicates that the current synchronization clock source of the clock
board is degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 758
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Impact on the System
When the SYN_BAD alarm occurs, the current synchronization clock source of the clock
board is degraded. As a result, system service transmission and receiving are affected.
Possible Causes
The possible cause of the SYN_BAD alarm is as follows:
l The quality of the traced synchronization clock source is degraded.
Procedure
Step 1 Check whether there are bit error and pointer justification performance events in the direction
of the traced clock source. Handle them as a result.
If... Then...
There are B1 bit error, B2 bit error, and See the corresponding section in this
pointer justification performance events document to clear the event.
There is no performance event. Go to the next step.
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
4.2.465 SYNC_C_LOS
Description
The SYNC_C_LOS alarm indicates that the clock source of the clock board that is set in the
clock source priority table is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 759
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Warning 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 details
about each parameter, refer to the following table.
Name 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.
Impact on the System
When the SYNC_C_LOS alarm occurs, the clock source of the clock board set in the clock
source priority table is lost. As a result, the clock source of higher priority is unavailable and
the clock source switching may occur.
Possible Causes
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).
l The cold reset is performed on the board of the access clock source, or the upstream
traced clock source board is faulty.
l The clock source switching in the S1 byte mode occurs at the local station.
l The input of the external clock source (BITS) changes.
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 See the corresponding section in this
T_ALOS alarm document to clear the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 760
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
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...
If the alarm is cleared No further action is required.
If the alarm persists Go to the next step.
Step 3 If the priority level table is not correctly configured, configure the clock source priority table
again.
Step 4 View alarms on the U2000 to check whether the SYNC_C_LOS alarm is cleared.
If... Then...
If the alarm is cleared No further action is required.
If the alarm persists Go to the next step.
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
4.2.466 SYNC_CONFIG_ERR
Description
The SYNC_CONFIG_ERR alarm indicates that the clock source configurations of an NE are
incorrect.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 761
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicate the slot ID of the board that reports the
Parameter 2 SYNC_CONFIG_ERR alarm.
Parameter 3 Indicates the mapped virtual port number on the board.
Parameter 4 Indicates the cause why the SYNC_CONFIG_ERR alarm is reported.
l 0x01: The port number configured for the clock source is not the
virtual port number.
Impact on the System
The clock source cannot trace the port for which the alarm is reported.
Possible Causes
The port number configured for the clock source is not the first port number in the
corresponding virtual port group on the board, and the first virtual port is not created.
Procedure
Step 1 Identify the virtual port number according to the alarm parameters, and check whether this
port is the first port in each virtual port group.
If… Then...
No Add the first virtual port to the virtual port
group corresponding to the clock source.
Then check whether the alarm is cleared. If
the alarm persists, go to Step 2.
Yes Go to Step 2.
NOTE
l The virtual SDH ports on an HUNS3 board can be divided into four groups: 51(V_SDH-1) to
54(V_SDH-4), 55(V_SDH-5) to 58(V_SDH-8), 59(V_SDH-9) to 62(V_SDH-12), and
63(V_SDH-13) to 66(V_SDH-16).
l The virtual port configured for the clock source can only be 51(V_SDH-1), 55(V_SDH-1),
59(V_SDH-1), or 63(V_SDH-1).
l For example, if the virtual port 52(V_SDH-1) in the first group is configured for the clock source,
change the virtual port to 51(V_SDH-1).
Step 2 Delete the alarmed clock source from the clock source priority list, or lower the priority of the
clock source.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 762
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.2.467 SYNC_DISABLE
Description
The SYNC_DISABLE alarm indicates that the automatic synchronization function on the
system control, switching, and timing boards is disabled. This alarm is reported when the
automatic synchronization of the system control, switching, and timing boards is disabled.
This alarm is cleared after the automatic synchronization of the system control, switching, and
timing board is enabled.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None.
Impact on the System
The system cannot initiate batch backup between the active and standby system control,
switching, and timing boards. As a result, the data on the active and standby system control,
switching, and timing boards may be different.
Possible Causes
The possible cause of the SYNC_DISABLE alarm is as follows:
The status of the automatic synchronization function on the system control, switching, and
timing boards changes from enabled to disabled.
Procedure
Step 1 Contact Huawei technical support engineers for enabling the automatic synchronization
function on the system control, switching, and timing boards. Check whether the alarm is
cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 763
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the alarmed board and check
whether the alarm is cleared. If the alarm
persists, go to the next step.
The alarm is cleared No further action is required.
----End
Related Information
None.
4.2.468 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH alarm indicates the forced or manual switching state of a clock
source.
Attribute
Alarm Severity Alarm Type
Warning 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the subrack where the switched clock source is
located.
Parameter 2 Indicates the number of the slot in the subrack where the switched clock
source is located. If the external clock source is used, the value is always 0xf0.
Parameter 3 Indicates the reserved byte, whose value is always 0x00.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 764
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 In the case of the clock source of the service board, it indicates the number of
the port in the subrack where the switched clock source is located.
In the case of the external clock source, it indicates the number of the external
clock.
l 0x01 indicates the first external clock.
l 0x02 indicates the second external clock.
Parameter 5 Indicates the ID of the priority table. Valid values are as follows:
l 0x01: priority table of the system clock
Impact on the System
When the SYNC_F_M_SWITCH alarm is generated, the NE clock works in the forced or
manual switching state. This alarm does not affect services.
Possible Causes
Cause 1: A manual or forced switching command is issued for the clock source.
Procedure
l View the SYNC_F_M_SWITCH alarm on the NMS, and then determine the relevant
clock source according to the alarm parameters.
l Cause 1: A manual or forced switching command is issued for the clock source.
a. Clear the manual or forced switching for the relevant clock source, and the alarm is
automatically cleared.
----End
Related Information
None
4.2.469 SYNC_FAIL
Description
The SYNC_FAIL alarm indicates that the batch backup of the databases of the active and
standby system control, switching, and timing boards fails.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 765
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following 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 system
control, switching, and timing boards fails.
l 0x21: The communication between the active and standby system control,
switching, and timing boards fails.
l 0x22: Data is changed during the upgrade of the standby system control,
switching, and timing board and therefore is inconsistent with that on the
active system control, switching, and timing board.
l 0x23: A forced switchover is triggered before the database backup is
completed.
Parameter 2 Its value is always 0xff.
Parameter 3 Its value is always 0xff.
Impact on the System
When this alarm occurs, data synchronization between the active and standby system control,
switching, and timing boards fails, and the active/standby switching between the two boards
is unavailable.
Possible Causes
Possible causes of the SYNC_FAIL are as follows:
l The software versions of the active and standby system control, switching, and timing
boards are inconsistent.
l The communication fails during the batch backup of the databases of the active and
standby system control, switching, and timing boards.
l Message sending fails or the database is detected damaged during the batch backup of
the databases of the active and standby system control, switching, and timing boards.
l Data has changed during the data backup operation. As a result, the data between the
active and standby system control, switching, and timing boards are different.
l A forced switchover is triggered before the database backup is completed.
Procedure
Step 1 Query the alarm on the NMS, and determine the fault type based on Parameter 1.
Step 2 Optional: (Optional) If Parameter 1 is 0x20, the software versions differ between the active
and standby system control, switching, and timing boards.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 766
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The software versions differ between the Upload the software version from the
active and standby system control, standby system control, switching, and
switching, and timing boards timing board. Check if the alarm is cleared.
If the alarm persists, go to the next step.
The software versions of the active and Go to other causes.
standby system control, switching, and
timing boards are the same.
Step 3 Optional: (Optional) If Parameter 1 is 0x21, communication is interrupted during the data
backup operation. If the interruption is transient, the system automatically restarts batch
backup; if the interruption lasts long, contact Huawei technical support engineers for handling
the alarm.
If... Then...
The interruption is transient The system automatically restarts batch
backup. Check whether the alarm is cleared.
If the alarm persists, go to the next step.
The interruption lasts long Contact Huawei engineers.
The communication is normal Go to other causes.
Step 4 Optional: If Parameter 1 is 0x22, it indicates that data is changed during the upgrade of the
standby system control, switching, and timing board and therefore is inconsistent with that on
the active system control, switching, and timing board.
1. Reseat the standby system control board.
2. If the alarm persists, check for other causes.
Step 5 Optional: If Parameter 1 is 0x23, it indicates that a forced switchover is triggered before the
database backup is completed.
1. Warm reset the alarming board. For details, see Resetting Boards in the Supporting
Tasks.
2. If the alarm persists, check for other causes.
Step 6 Optional: (Optional) If Parameter 1 is 0x1f, contact Huawei technical support engineers for
handling the alarm.
----End
Related Information
None.
4.2.470 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF alarm indicates that the clock source in the priority list is locked.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 767
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Warning 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the subrack where the locked clock source is located.
Parameter 2 Indicates the number of the slot in the subrack where the locked clock source
is located. If the external clock source is used, the value is always 0xf0.
Parameter 3 Indicates the reserved byte, whose value is always 0x00.
Parameter 4 In the case of the clock source of the service board, it indicates the number of
the port in the subrack where the locked clock source is located.
In the case of the external clock source, it indicates the number of the external
clock.
l 0x01 indicates the first external clock.
l 0x02 indicates the second external clock.
Impact on the System
When the SYNC_LOCKOFF alarm is generated, the relevant clock source is locked and
cannot be traced by the NE. This alarm itself does not affect services.
Possible Causes
Cause 1: The NE software issues a command to lock the clock source.
Procedure
l View the SYNC_LOCKOFF alarm on the NMS, and then determine the locked clock
source according to the alarm parameters.
l Cause 1: The NE software issues a command to lock the clock source.
a. After the lockout of the clock source is released on the NMS, the
SYNC_LOCKOFF alarm is automatically cleared.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 768
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.471 SYSLOG_COMM_FAIL
Description
The SYSLOG_COMM_FAIL alarm indicates that communication between the NE and the
Syslog server fails.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2, Indicates the address of the Syslog server.
Parameter 3, Parameter 4
Parameter 5 Indicates the communication exception type.
l 0x01: The connection between the NE and the Syslog server
is interrupted.
l 0x02: The session between the NE and the Syslog server is
abnormal.
Impact on the System
When this alarm is generated, it indicates that the connection between the NE and the Syslog
server is interrupted, or the session between the NE and the server is abnormal.
Possible Causes
The possible cause of the SYSLOG_COMM_FAIL alarm is as follows:
In the TCP mode, the connection between the NE and the Syslog server is interrupted or the
session between the NE and the server is abnormal.
Procedure
Step 1 Rectify the fault on the link between the NE and the Syslog server or rectify the fault of the
protocol.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 769
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
The alarm is cleared automatically.
----End
Related Information
None.
4.2.472 SYSPARA_CFDB_NOSAME
Description
The SYSPARA_CFDB_NOSAMEindicates that the SCC data and the CF card data are
inconsistent. In the first startup, the SCC performs the consistency check between the SCC
data and the CF card data. If not consistent, the SCC does not perform a timed backup and
reports this alarm. If consistent, the SCC starts the timed backup.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None
Impact on the System
The data in the system parameter area are not consistent with that saved in the CF card. The
data cannot be recovered from the CF card.
Possible Causes
The SCC data and the CF card data are not consistent upon the first startup.
Procedure
Step 1 Wait for the next backup period so that the NE database automatically backs up data to the CF
card and the alarm is cleared.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 770
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.473 T_ALOS
Description
The T_ALOS alarm indicates 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.
Impact on the System
When the T_ALOS alarm occurs, the PDH services are interrupted.
Possible Causes
Possible causes of the T_ALOS alarm are as follows:
l The E1 or T1 services are not accessed.
l The output port of the E1 or T1 interface on the DDF side is disconnected or loose.
l The cable is faulty.
l The board is faulty.
Procedure
Step 1 View the T_ALOS alarm on the U2000 to confirm the alarmed board.
Step 2 Check whether the E1 or T1 services in the alarmed 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 persists, go to the next step.
Step 3 If the alarm persists, perform service self-loop (namely, hardware inloop) to the path at the
DDF.
The loopback causes service interruption.
l If the alarm is cleared, the equipment at the opposite station is faulty. After rectifying the
fault, check whether the T_ALOS alarm is cleared.
l If the alarm persists, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 771
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 If the alarm persists, check whether the equipment at the opposite station is faulty. If yes,
replace the faulty board at the opposite station.
----End
Related Information
None.
4.2.474 T_FIFO_E
Description
The T_FIFO_E alarm indicates that the transmit FIFO on the PDH side of the E3/T3 tributary
board overflows.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None.
Impact on the System
The alarmed port has bit errors and the services at the port are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l Incorrect services are accessed into the E3/T3 tributary board.
l Service cross-connections are incorrectly configured.
l The E3/T3 tributary board is faulty.
l The cross-connect and timing board is faulty.
Procedure
Step 1 Check whether correct services are accessed into the E3/T3 tributary board on the NMS.
If... Then...
Incorrect services are accessed Configure correct services to be accessed
into the E3/T3 tributary board. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
Correct services are accessed Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 772
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 2 Replace the E3/T3 tributary board and ensure that the new board transmits and receives the
same types of signals as the old board.
Replacing the E3/T3 tributary board will interrupt the services on the board. This operation is
of risk.
Step 3 If the alarm persists, replace the cross-connect and timing board.
----End
Related Information
None.
4.2.475 T_LOC
Description
The T_LOC alarm indicates 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
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the actual number of the optical interface on a board where
the alarm occurs.
For example, 0x01 indicates that the alarm is reported from optical
interface 1 of the board.
Parameter 2, Indicates the actual number of the optical interface on a board where
parameter 3 the alarm occurs.
For example, 0x01 indicates that the alarm is reported from optical
interface 1 of the board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 773
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Impact on the System
When the T_LOC alarm occurs, the clock of the signal on the transmit side of the line board is
lost. As a result, the services transmitted from the optical interface are unavailable.
Possible Causes
Possible causes of the T_LOC alarm are as follows:
l The cross-connect board is faulty.
l The clock board is faulty.
l The line board is faulty.
Procedure
Step 1 If the line board is faulty, replace it.
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.
4.2.476 T_LOS
Description
The T_LOS alarm indicates that no signal is input on the transmit side of the line board.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
When the T_LOS alarm occurs, there is no signal input on the transmit side of the line board.
As a result, the services transmitted from the optical interface are unavailable.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 774
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the T_LOS alarm are as follows:
l The services are incorrectly configured.
l The line board is faulty.
l The cross-connect board is faulty.
Procedure
Step 1 Check whether the services to be transmitted from this optical interface on the line board are
configured. If the services to be transmitted are 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...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
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...
The alarm is cleared No further action is required.
The alarm persists Go to the next step.
Step 5 If the cross-connect board is faulty, replace the system control, switching, and timing board.
----End
Related Information
None.
4.2.477 T_LOSEX
Description
The T_LOSEX alarm indicates that the board detects the loss of backplane service bus
signals. This alarm occurs when the board detects the LOS state of backplane service bus.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 775
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2 The value is always 0x00.
Parameter 3 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.
Impact on the System
All services on the board are interrupted and the board cannot work normally.
Possible Causes
Possible causes of this alarm are as follows:
l The service board and the corresponding cross-connect board are inserted incorrectly.
l Clock sources of the active and standby cross-connect boards deteriorate or fail.
l The board has hardware faults.
l The backplane has bent pins.
Procedure
Step 1 Check the alarm on the NMS, determine the alarmed service board, and then confirm the
corresponding cross-connect board according to the alarm parameters.
Step 2 Check whether the alarmed service board and the corresponding cross-connect board are
securely connected to the backplane.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 776
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The boards are loosely connected to the Reseat the boards. Check whether the alarm
backplane is cleared. If the alarm persists, go to the
next step.
The boards are securely connected to the Go to the next step.
backplane
Step 3 Replace the corresponding cross-connect board and check whether the alarm is cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 4 Replace the alarmed service board and check whether the alarm is cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 5 Check whether certain pins on the backplane are bent.
If... Then...
Certain pins on the backplane are bent Contact Huawei technical support engineers
for repairing the bent pins. Then, reseat the
board.
The backplane is normal Contact Huawei technical support engineers
for handling the alarm.
----End
Related Information
None.
4.2.478 TD
Description
The TD alarm indicates laser transmit performance deteriorates. This alarm is reported if the
bias current of the laser is higher than A, which is 1.2 times greater than the initial bias
current value, and lower than B, which is 1.5 times greater than the initial value.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 777
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Impact on the System
The laser cannot work properly and bit errors occur. Services may be interrupted.
Possible Causes
Cause: The laser is aged.
Procedure
l Cause: The laser is aged.
a. Check whether the board supports pluggable optical modules.
If... Then...
The board supports pluggable Replace pluggable optical modules.
optical modules For details, see Replacing the Optical
Module. If the alarm persists, replace
the faulty board.
The board does not support Reset the board. For details, see
pluggable optical modules Resetting Boards.
If the alarm persists, replace the faulty
board.
b. If the alarm persists, contact Huawei technical support personnel to handle the
alarm.
----End
Related Information
In a cooled optical module that adopts automatic level control (ALC), its laser ages after
working for a long time, resulting in reduced emission efficiency. To ensure constant output
optical power, the laser bias current, an indicator of laser aging degree, should be increased.
4.2.479 TEM_HA
Description
The TEM_HA alarm indicates that the temperature of the laser crosses the upper threshold.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 778
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port ID.
Impact on the System
The laser will be abnormal and aged more quickly. If the laser is faulty, bit errors will occur or
services will be interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The ambient temperature of the board is high.
l The optical module is faulty.
l The line board is faulty.
Procedure
Step 1 Check the temperature of the NE subrack.
If... Then...
The temperature of the NE subrack is high Decrease the ambient temperature to the
allowed range. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The temperature of the NE subrack is Go to the next step.
normal
Step 2 Check the alarmed line board and replace the optical module. Check whether the alarm is
cleared.
If... Then...
The alarm persists Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 779
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm is cleared No further action is required.
Step 3 Replace the line board.
----End
Related Information
None.
4.2.480 TEM_LA
Description
The TEM_LA alarm indicates that the temperature of the laser exceeds the lower threshold.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port number.
Impact on the System
When the TEM_LA alarm is reported, the laser is faulty. Consequently, the transmit circuit
will be faulty and bit errors will occur, resulting in service interruptions.
Possible Causes
Possible causes of the TEM_LA alarm are as follows:
l The ambient temperature of the board is low.
l The optical module is faulty.
l The line board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 780
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Check the temperature of the NE subrack.
If... Then...
The temperature of the NE subrack is low Increase the ambient temperature to the
allowed range. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The temperature of the NE subrack is Go to the next step.
normal
Step 2 Check the alarmed line board and replace the optical module. Check whether the alarm is
cleared.
If... Then...
The alarm persists Go to the next step.
The alarm is cleared No further action is required.
Step 3 Replace the line board.
----End
Related Information
None.
4.2.481 TEMP_ALARM
Description
The TEMP_ALARM alarm indicates that the temperature crosses the threshold.
Attribute
Alarm Severity Alarm Type
Minor Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 781
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the threshold-crossing type.
l 0x01: The temperature is higher than the upper threshold.
l 0x02: The temperature is lower than the lower threshold.
Impact on the System
The optical module may be damaged and services are interrupted.
Possible Causes
Possible causes of this alarm are as follows:
l The ambient temperature of the board is high.
l The ambient temperature of the board is low.
l The alarmed board is faulty.
Procedure
Step 1 Query the alarm on the NMS and determine the threshold-crossing type according to
Parameter 1.
Step 2 Check the temperature of the NE frame.
If... Then...
The ambient temperature of the board is Lower the ambient temperature to the
high normal range. Check whether the
TEMP_ALARM alarm is cleared. If the
alarm persists, go to the next step.
The ambient temperature of the board is low This may be caused by hardware faults of
the board. Go to Step 3.
The ambient temperature of the board is Go to Step 4.
normal
Step 3 Check whether the board reports any hardware-related alarms, such as HARD_BAD.
If... Then...
The board reports any hardware-related Clear these alarms first. Check whether the
alarm alarm is cleared. If the alarm persists, go to
the next step.
The board does not report any hardware- Go to the next step.
related alarm
Step 4 Replace the faulty board.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 782
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.482 TEMP_OVER
Description
The TEMP_OVER alarm indicates that the operating temperature of the alarmed board is
higher than the upper threshold or lower than the lower threshold.
Attribute
Alarm Severity Alarm Type
Major Equipment
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the threshold-crossing type of the board operating temperature.
l 0x01: The operating temperature of the alarmed board is higher than the
upper threshold.
l 0x02: The operating temperature of the alarmed board is lower than the
lower threshold.
Impact on the System
The system is in a highly dangerous state. If the system runs in this state for a long time, bit
errors may occur, the service may be interrupted, and the board may be burnt. Therefore, this
alarm must be handled timely.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: Dust builds up at the heat dissipation vents.
l Cause 2: Fans rotate at a speed lower than the rated speed or stop working.
l Cause 3: The ambient temperature is higher than 55°C or lower than -5°C due to a fault
on the cooler or heater equipment.
l Cause 4: The alarmed board is faulty.
l Cause 5: The configuration of the upper and lower threshold of the temperature alarm is
not proper.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 783
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 Cause 1: Dust builds up at the heat dissipation vents.
1. Check whether dust builds up at the heat dissipation vents, causing poor heat dissipation.
Place your hands at the air exhaust vent to feel the wind.
2. If dust builds up at the heat dissipation vents and heat dissipation is poor, clear the heat
dissipation vents.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: Fans rotate at a speed lower than the rated speed or stop working.
1. Check operation statuses of fans in the subrack. Handle the FAN_AGING or
FAN_FAIL alarm if any.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The ambient temperature is higher than 55°C or lower than -5°C due to a fault on the
cooler or heater equipment.
1. Check the ambient temperature of the telecommunications room. If the temperature is
higher than 55°C or lower than -5°C, use a cooler or heater to decrease or increase the
ambient temperature.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The alarmed board is faulty.
1. Check whether the alarmed board is functional. If the alarmed board is faulty, replace it.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Cause 5: The configuration of the upper and lower threshold of the temperature alarm is not
proper.
1. Contact Huawei technical support personnel to check the upper and lower temperature
thresholds and the current operating temperature, and determine whether the alarm is
falsely reported.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support personnel to handle the alarm.
----End
Related Information
None
4.2.483 TF
Description
The TF alarm indicates a transmission failure in the laser.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 784
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
When the TF alarm occurs, the transmission of the laser fails. As a result, the services are
interrupted.
Possible Causes
The possible cause of the TF alarm is as follows:
l The laser of the board is aged or faulty.
l The board is faulty.
Procedure
Step 1 Check the optical module of the board to check whether the optical module is aged or faulty.
If... Then...
The optical module is aged or faulty Replace the optical module. Check whether
the alarm is cleared. If the alarm persists, go
to the next step.
The optical module is normal Go to the next step.
Step 2 Replace the board.
----End
Related Information
None
4.2.484 THUNDERALM
Description
The THUNDERALM alarm indicates a surge-protection failure. If the system detects the
surge-protection circuit fails, the THUNDERALM occurs.
Attribute
Alarm Severity Alarm Type
Minor Environment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 785
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
Name Meaning
Parameter 1 Indicates the power unit that reports the alarm.
l 0x00: All the power units fail.
l 0x01: The surge protection of the PIU1 board fails.
l 0x02: The surge protection of the PIU2 board fails.
Impact on the System
When the THUNDERALM occurs, the system operation and services are not affected, but the
surge-protection function fails.
Possible Causes
The cause of the THUNDERALM alarm is as follows:
l The fuse tube of the surge-protection circuit is interrupted.
l The board is faulty.
Procedure
Step 1 Replace the fuse, and then check whether the alarm is cleared.
Step 2 Replace the board that reports the THUNDERALM alarm.
----End
Related Information
None.
4.2.485 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL is an alarm indicating a failure to lock the clock. When the NE time
is synchronous with that of the upstream NE, the time is locked indicating that the NE has
traced the upstream NE successfully. This alarm is reported only when the time of the NE is
unlocked.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 786
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The time synchronization is disabled or the IEEE 1588v2 port time is
not traced.
l 0x02: The clock is unlocked because phase discrimination value per unit of
time exceeds the upper threshold.
l 0x03: The forward delay is abnormal.
l 0x04: The backward delay is abnormal.
l 0x05: The offset value accumulated per unit of time exceeds 240 ns.
l 0x06: The offset values accumulated per unit of time is longer than 100 ns
but shorter than 240 ns.
Impact on the System
When this alarm occurs, the time of the NE is unlocked and the NE time cannot trace the
upstream NE time so that bit errors occur in services.
Possible Causes
The possible cause of the TIME_LOCK_FAIL alarm is as follows:
Cause: The timestamp changes greatly on the NE.
Procedure
Step 1 On the NMS, check whether the NE reports the 4.2.74 CLK_LOCK_FAIL or 4.2.486
TIME_NO_TRACE_MODE alarm. If yes, clear it first. Check whether the
TIME_LOCK_FAIL alarm is cleared. If not, go to the next step.
Step 2 Check whether time is adjusted on the upstream NE. If yes, the alarm will disappear within 5
seconds. You do not have to handle it.
----End
Related Information
Phrase discrimination: By comparing of two signals, add high speed pulse to the output signal
pulse, and through the recorded number of added pulses to test the phase discrimination.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 787
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.486 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the IEEE 1588v2 time goes into
no-trace mode. This alarm is reported when the IEEE 1588v2 time is enabled but the NE is
tracing an internal clock source.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The IEEE 1588v2 time is enabled at a random interface.
l 0x02: A random external time interface is configured as the input interface
for the IEEE 1588v2 time.
Impact on the System
When this alarm occurs, the IEEE 1588v2 time cannot be synchronized between the upstream
and downstream NEs.
Possible Causes
The possible causes of the TIME_NO_TRACE_MODE alarm are as follows:
l Cause 1: The clock source priority table contains only internal clock sources.
l Cause 2: The clock source priority table contains other available clock sources, but
internal clock sources are traced because of incorrect fiber connections or offline boards.
l Cause 3: The Announce attribute of the upstream NE is incorrect. As a result, the
relevant time source cannot be traced.
Procedure
Step 1 Cause 1: The clock source priority table contains only internal clock sources.
1. Configure the clock source priority table again to contain other available clock sources.
Check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 788
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
2. If the alarm persists, go to Step 2.
Step 2 Cause 2: The clock source priority table contains other available clock sources, but internal
clock sources are traced because of incorrect fiber connections or offline boards.
1. Check whether the fibers are connected properly or the boards are online. If not, connect
the fibers again or insert the board again. Check whether the alarm is cleared.
2. If the alarm persists, go to Step 3.
Step 3 Cause 3: The Announce attribute of the upstream NE is incorrect. As a result, the relevant
time source cannot be traced.
1. Check whether the Announce attribute of the upstream NE is configured correctly. If not,
modify the attribute. Check whether the alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
Announce packets are used to establish a clock master-slave hierarchy in best master clock
(BMC) algorithm.
4.2.487 TPS_ALM
Description
The TPS_ALM is an alarm of TPS protection switching.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01, Indicates the page number that performs the
switching.
Impact on the System
During the service data transmission, if the TPS protection groups are configured and they
work normally, the system performs the automatic switching when the HARD_BAD alarm is
reported due to the hardware fault of the working board or the working board is performed the
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 789
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
hard reset. When the TPS protection groups are in the automatic switching state, the services
are transiently interrupted.
Possible Causes
The possible causes of the TPS_ALM alarm are as follows:
l The hardware of the working board is faulty, and the TPS automatic switching occurs.
l The hardware of the working board is not faulty. The TPS switching command is issued,
however, and services are switched from the working board to the protection board.
Procedure
Step 1 Check whether the TPS switching command is manually issued.
l If yes, issue the command to clear the TPS switching. Accordingly, services are switched
from the protection board to the working board and the TPS_ALM alarm is
automatically cleared.
l If not, check whether there is the HARD_BAD alarm reported from the working board.
If yes, it indicates that the hardware of the working board is faulty. After the
HARD_BAD alarm is cleared, the services are switched from the protection board to the
working board and then the TPS_ALM alarm is cleared.
Step 2 For the tributary boards. Replace the working board and perform the service switching to the
working board. The TPS_ALM alarm is automatically cleared.
----End
4.2.488 TR_LOC
Description
The TR_LOC alarm indicates that the cross-connect and timing board is faulty. This alarm
occurs 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 790
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
Name Meaning
Parameter 1 For packet processing boards and EGS4 boards: indicates the clock board
whose transmit clock is faulty.
l 0x01: indicates that the transmit clock of the smaller-numbered cross-
connect and timing board is faulty.
l 0x02: indicates that the transmit clock of the larger-numbered cross-
connect and timing board is faulty.
l 0x03: indicates that the transmit clocks of both the active and standby
cross-connect and timing boards are faulty.
For SDH, PDH, and auxiliary boards, the parameter value is always 0x01.
Parameter 2 For packet processing boards: indicates the clock frequency.
l 0x01: indicates that the 38M clock is faulty.
l 0x02: indicates that the 2K clock is faulty.
l 0x03: indicates that the 66M clock is faulty.
For SDH, PDH, and auxiliary boards, the parameter value is always 0x00.
Parameter 3 For SDH, PDH, and auxiliary boards: indicates the slot ID of the board that
loses the clock.
l 0x01: board in the slot with a smaller ID.
l 0x02: board in the slot with a greater ID.
l 0x03: two boards.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 791
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 For EoS boards except for EGS4: indicates the slot number of the board whose
transmit clock is lost.
l 0x01: indicates the board with a smaller slot number.
l 0x02: indicates the board with a larger slot number.
l 0x03: indicates both boards.
For SDH, PDH, and auxiliary boards: 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]: 2 Mbit/s 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]: 2 Mbit/s clock status of the cross-connect board in the slot with a
greater ID
NOTE
If the bit corresponding to Parameter 4 is 1, the TR_LOC alarm occurs. If the bit
corresponding to Parameter 4 is 0, the TR_LOC alarm does not occur.
Impact on the System
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,
causing transient service interruption.
Possible Causes
Possible causes of this alarm are as follows:
l If multiple boards report this alarm, the clock cable of the cross-connect board is faulty.
l If one board reports this alarm, the board hardware is faulty.
Procedure
Step 1 Check whether multiple boards or one board at the local end reports this alarm.
If... Then...
Multiple boards report this alarm Go to Step 2.
One board reports this alarm Go to Step 3.
Step 2 Perform 1+1 protection switching on the cross-connect board. Reset the protection cross-
connect board (cold). Check whether the alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 792
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
The alarm persists Replace the cross-connect and timing board.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The alarm is cleared No further action is required.
Step 3 Perform a warm reset on the alarmed board, and check whether the alarm is cleared.
If... Then...
The alarm persists Perform a cold reset on the alarmed board.
Check whether the alarm is cleared. If the
alarm persists, go to the next step.
The alarm is cleared No further action is required.
Step 4 Remove the alarmed board and check whether certain pins on the backplane are bent.
If... Then...
The backplane has bent pins Insert the board. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
No pin on the backplane is bent Go to the next step.
Step 5 Replace the alarmed board.
----End
Related Information
None.
4.2.489 TU_AIS
Description
The TU_AIS alarm 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 793
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Parameters
None.
Impact on the System
When the TU_AIS alarm occurs, the service in the alarmed TU path is interrupted. If the
service is configured with protection, the protection switching is also triggered.
Possible Causes
Possible causes of the TU_AIS alarm are as follows:
l Configuration data is incorrect.
l The line is faulty.
l The board at the opposite end is faulty.
l The board at the local end is faulty.
Procedure
Step 1 Check whether SDH services are correctly configured. If the configuration is incorrect,
modify it. If the configuration is correct, go to Step 2.
Step 2 Check whether line alarms that cause AIS insertion are reported on the service trail. If these
alarms exist, clear them. If these alarms do not exist, go to Step 3.
Step 3 Check whether the fault occurs on the local or peer NE. If the fault occurs on the peer NE, go
to Step 4. If the fault occurs on the local NE, go to Step 5.
Step 4 Replace the faulty board on the peer NE. If the alarm persists, go to Step 6. If the alarm is
cleared, no further action is required.
Step 5 Replace the board on the local NE where the line unit resides. If the alarm persists, go to Step
6. If the alarm is cleared, no further action is required.
Step 6 Replace the board that reports the alarm. If the TU_AIS alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
Table 4-5 Alarms that may cause the TU_AIS alarm
R_LOS R_LOF AU_AIS
AU_LOP HP_LOM -
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 794
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.490 TU_AIS_VC12
Description
The TU_AIS_VC12 is a TU alarm indication signal in the VC-12 lower order path. TU alarm
indication is the VC-12 path AIS. If a board has detected that the TU path is all "1"s, the
TU_AIS_VC12 alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
When the TU_AIS_VC12 alarm occurs, the lower order path signals received on the cross-
connection side by the board are all "1"s. Consequently, the services in the lower order path
are unavailable. If the SNCP protection is configured for the 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:
l The higher order alarms occur.
l The relevant path at the opposite station is faulty.
l The services are incorrectly configured.
l Cross-connect unit fault.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 795
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View alarms on the NMS to check whether the R_LOS or TU_LOP_VC12 alarm is reported
on the upstream NE. If these alarms exist, handle these alarms by following instructions in
4.2.420 R_LOS and 4.2.493 TU_LOP_VC12. If these alarms do not exist, go to Step 2.
Step 2 Check whether the T_ALOS, E1_LOS, or UP_E1_AIS alarm is reported on the peer NE. If
these alarms exist, handle these alarms by following instructions in 4.2.473 T_ALOS, 4.2.108
E1_LOS, and 4.2.498 UP_E1_AIS. If these alarms do not exist, go to Step 3.
Step 3 Check whether services are correctly configured. If the configuration is incorrect, modify it
and issue the correct configuration. If the configuration is correct, go to Step 4.
Step 4 View alarms on the NMS to check whether the TU_AIS_VC12 alarm is cleared. If the alarm
persists, go to Step 5. If the alarm is cleared, no further action is required.
Step 5 Cold reset the faulty board. If the TU_AIS_VC12 alarm persists, go to Step 6. If the alarm is
cleared, no further action is required.
Cold resetting or replacing a board will interrupt services. The operation is risky.
Step 6 Replace the faulty cross-connect board. If the TU_AIS_VC12 alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.491 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU alarm indication signal in the VC-3 lower order path. TU alarm
indication is the AIS at the level of the VC-3 lower order path. If a board has detected that the
TU path is all "1"s, the TU_AIS_VC3 alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 796
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
When the TU_AIS_VC3 alarm occurs, the lower order path signals received on the cross-
connection side by the board are all "1"s. Consequently, the services in the lower order path
are unavailable. If the SNCP protection is configured for the 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 higher order alarms occur.
l The relevant path at the opposite station is faulty.
l The services are incorrectly configured.
l The cross-connect unit is faulty.
Procedure
Step 1 View alarms on the NMS to check whether the R_LOS or TU_LOP_VC3 alarm is reported on
the upstream NE. If these alarms exist, handle these alarms by following instructions in
4.2.420 R_LOS and 4.2.494 TU_LOP_VC3. If these alarms do not exist, go to Step 2.
Step 2 Check whether the T_ALOS alarm is reported on the peer NE. If the T_ALOS alarm is
reported on the peer NE, handle the alarm by following instructions in 4.2.473 T_ALOS. If
the T_ALOS alarm is not reported on the peer NE, go to Step 3.
Step 3 Check whether services are correctly configured. If the configuration is incorrect, modify it
and issue the correct configuration. If the configuration is correct, go to Step 4.
Step 4 View alarms on the NMS to check whether the TU_AIS_VC3 alarm is cleared. If the alarm
persists, go to Step 5. If the alarm is cleared, no further action is required.
Step 5 Cold reset the faulty board. If the TU_AIS_VC3 alarm persists, go to Step 6. If the alarm is
cleared, no further action is required.
Cold resetting or replacing a board will interrupt services. The operation is risky.
Step 6 Replace the faulty cross-connect board. If the TU_AIS_VC3 alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 797
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.492 TU_LOP
Description
The TU_LOP alarm indicates TU pointer loss. This alarm occurs if a board detects that the
TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Impact on the System
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
Possible causes of the TU_LOP alarm are as follows:
l Service cross-connections are incorrectly configured.
l The system control, cross-connect, and timing board is faulty.
l The board is faulty.
Procedure
Step 1 Check whether the cross-connect service configuration is consistent with the plan. If the
configuration is inconsistent with the plan, re-configure the cross-connect service as planned.
If the configuration is consistent with the plan, go to Step 2.
Step 2 Check whether the system control and cross-connect board is faulty. If the board is faulty,
replace it. If the board is working properly, go to Step 3.
Step 3 Check whether any board on the local or peer NE is faulty by performing loopbacks. If any
board is found faulty, replace it. If the TU_LOP alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 798
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.493 TU_LOP_VC12
Description
The TU_LOP_VC12 is an alarm indicating the loss of pointer in the TU of the VC-12 lower
order path. If a board has detected that the TU-PTR value is an invalid pointer or NDF
reversion in eight consecutive frames, the TU_LOP_VC12 alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Parameter 2, parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
When the TU_LOP_VC12 alarm occurs, the TU pointer in the signals received by the 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 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 higher order alarms occur.
l The relevant path at the opposite station is faulty.
l The services are incorrectly configured.
l Cross-connect unit fault.
Procedure
Step 1 View alarms on the NMS to check whether the R_LOS alarm is reported on the upstream NE.
If the R_LOS alarm is reported on the upstream NE, handle the alarm by following
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 799
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
instructions in 4.2.420 R_LOS. If the R_LOS alarm is not reported on the upstream NE, go to
Step 2.
Step 2 Check whether the T_ALOS, E1_LOS, or UP_E1_AIS alarm is reported on the peer NE. If
these alarms exist, handle these alarms by following instructions in 4.2.473 T_ALOS, 4.2.108
E1_LOS, and 4.2.498 UP_E1_AIS. If these alarms do not exist, go to Step 3.
Step 3 Check whether services are correctly configured. If the configuration is incorrect, modify it
and issue the correct configuration. If the configuration is correct, go to Step 4.
Step 4 Cold reset the faulty board. If the TU_LOP_VC12 alarm persists, go to Step 5. If the alarm is
cleared, no further action is required.
Cold resetting or replacing a board will interrupt services. The operation is risky.
Step 5 Replace the faulty cross-connect board. If the TU_LOP_VC12 alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.494 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating the loss of pointer in the VC-3 lower order path. If
a board has detected that the TU-PTR value is an invalid pointer or NDF reversion in eight
consecutive frames, the TU_LOP_VC3 alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the optical interface number. The value is always 0x01.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 800
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2, parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
When the TU_LOP_VC3 alarm occurs, the TU pointer in the signals received by the 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 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 higher order alarms occur.
l The relevant path at the opposite station is faulty.
l The services are incorrectly configured.
l Cross-connect unit fault.
Procedure
Step 1 View alarms on the NMS to check whether the R_LOS alarm is reported on the upstream NE.
If the R_LOS alarm is reported on the upstream NE, handle the alarm by following
instructions in 4.2.420 R_LOS. If the T_ALOS alarm is not reported on the upstream NE, go
to Step 2.
Step 2 Check whether the T_ALOS alarm is reported on the peer NE. If the T_ALOS alarm is
reported on the peer NE, handle the alarm by following instructions in 4.2.473 T_ALOS. If
the T_ALOS alarm is not reported on the peer NE, go to Step 3.
Step 3 Check whether services are correctly configured. If the configuration is incorrect, modify it
and issue the correct configuration. If the configuration is correct, go to Step 4.
Step 4 Cold reset the faulty board. If the TU_LOP_VC3 alarm persists, go to Step 5. If the alarm is
cleared, no further action is required.
Cold resetting or replacing a board will interrupt services. The operation is risky.
Step 5 Replace the faulty cross-connect board. If the TU_LOP_VC3 alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 801
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.495 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED alarm indicates that a tunnel APS protection group
degrades. This alarm is reported when the protection tunnel in a tunnel APS protection group
fails and is cleared after the protection tunnel recovers.
NOTE
This alarm is also cleared when the working and protection tunnels of the group fail.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None.
Impact on the System
The tunnel APS protection group cannot perform protection switching.
Possible Causes
Possible causes of the TUNNEL_APS_DEGRADED alarm are as follows:
l The port connected to the protection tunnel is disabled.
l Fiber connections are incorrect.
l The protection tunnel is faulty.
Procedure
Step 1 Query the status of the tunnel APS protection group on the U2000 and identify the protection
tunnel.
Step 2 Check whether the port connected to the protection tunnel is disabled.
If... Then...
The tunnel port is disabled Enable the port. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The tunnel port is enabled Go to the next step.
Step 3 Check whether fiber connections to the port that is connected to the protection tunnel are
incorrect.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 802
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
Fiber connections are incorrect or fibers are Rectify the incorrect fiber connections or
faulty replace the faulty fibers. Check whether the
alarm is cleared. If the alarm persists, go to
the next step.
Fiber connections are correct Go to the next step.
Step 4 Check whether the port connected to the protection tunnel reports any alarms.
If... Then...
The port reports alarms Clear these alarms first. Check whether the
TUNNEL_APS_DEGRADED alarm is
cleared. If the
TUNNEL_APS_DEGRADED alarm
persists, go to the next step.
The port reports no alarm Go to the next step.
Step 5 Contact Huawei technical support engineers to handle the TUNNEL_APS_DEGRADED
alarm.
----End
Related Information
None.
4.2.496 TUNNEL_APS_OUTAGE
Description
The TUNNEL_APS_OUTAGE alarm indicates that a tunnel APS protection group fails. This
alarm is reported when both the protection and working tunnels in a tunnel APS protection
group fail, and is cleared when either of the protection or working tunnel recovers.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None
Impact on the System
The tunnel APS group fails and services in the group are interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 803
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: Ports carrying the working and protection tunnels are not enabled.
l Cause 2: Fibers connections are faulty.
l Cause 3: Alarms occur on both the working and protection tunnels.
Procedure
Step 1 Cause 1: Ports carrying the working and protection tunnels are not enabled.
1. Check whether ports carrying the working and protection tunnels are enabled. If they are
not enabled, enable them.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: Fibers connections are faulty.
1. Replace the faulty fibers or connect the fibers correctly.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: Alarms occur on both the working and protection tunnels.
1. Check for alarms, such as 4.2.274 MPLS_TUNNEL_LOCV, on the working and
protection tunnels. If such an alarm occurs, clear the alarm first.
2. Check whether the TUNNEL_APS_OUTAGE alarm is cleared. If the alarm persists,
contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None
4.2.497 UHCS
Description
The UHCS alarm indicates that multiple uncorrectable bit errors occur in the cell header.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
When the UHCS alarm is reported, some cells with multiple bit errors are found during cell
the delimitation process at the port. Consequently, user cells are lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 804
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the UHCS alarm are as follows:
l Some bit errors occur in the SDH receive path connected to an ATM port on the alarmed
board. That is, some bit error alarms, such as the B1_SD, B2_SD, or B3_SD, occur in
the SDH path.
l The ATM processing chip on the alarmed board is faulty.
Procedure
Step 1 On the U2000, check whether alarms indicating that the signal degrades due to excessive
errors, such as B1_SD, B2_SD, and B3_SD, are reported at the local NE.
If... Then...
The alarms are reported Handle the alarms, and check whether the UHCS alarm is
cleared. If the UHCS alarm persists, go to the next step.
The alarms are not reported Go to the next step.
Step 2 Reset (cold) or reseat the board that reports the UHCS alarm, and then check whether the
UHCS alarm is cleared.
If the services on the alarmed board are not protected, a cold reset on the board causes service
interruption.
If... Then...
The UHCS alarm is cleared No further action is required.
The UHCS alarm persists Go to the next step.
Step 3 Replace the board that reports the UHCS alarm.
----End
Related Information
None.
4.2.498 UP_E1_AIS
Description
The UP_E1_AIS alarm indicates upstream E1 signals. This alarm occurs when a tributary
board detects upstream E1 signals of all 1s.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 805
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
Upstream E1 signals are unavailable.
Possible Causes
Possible causes of this alarm are as follows:
l The tributary board interconnected with the local tributary board reports the TU_LOP,
TU_AIS, or DOWN_E1_AIS alarm.
l The tributary board interconnected with the local tributary board reports the T_ALOS
alarm.
l The opposite end reports hardware fault alarms such as PLL_FAIL and CHIP_FAIL.
l The alarmed board is faulty.
Procedure
Step 1 Check whether the tributary board interconnected with the local tributary board reports the
TU_LOP, TU_AIS, or DOWN_E1_AIS alarm.
If... Then...
The TU_LOP, TU_AIS, or DOWN_E1_AIS Clear these alarms first. Then check whether
alarm is reported the UP_E1_AIS alarm is cleared. If the
alarm persists, go to the next step.
The TU_LOP, TU_AIS, or DOWN_E1_AIS Go to the next step.
alarm is not reported
Step 2 Check whether the tributary board interconnected with the local tributary board reports the
T_ALOS alarm.
If... Then...
The T_ALOS alarm is reported Clear the T_ALOS alarm first. Then check
whether the UP_E1_AIS alarm is cleared. If
the alarm persists, go to the next step.
The T_ALOS alarm is not reported Go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 806
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 3 Perform a cold reset on the alarmed tributary board by using the NMS or reseat this board.
Check whether the UP_E1_AIS alarm is cleared.
If... Then...
The alarm persists Replace the alarmed tributary board. Then
check whether the alarm is cleared. If the
alarm persists, contact Huawei technical
support engineers for handling the alarm.
The alarm is cleared No further action is required.
----End
4.2.499 UP_T1AIS
Description
The UP_T1AIS alarm indicates the status of upstream 1.5 Mbit/s signals. This alarm is
reported if a tributary board has detected that the upstream T1 signals are all "1"s.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None.
Impact on the System
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 Cause 1: 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.
l Cause 2: 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.
l Cause 3: The local board is faulty.
Procedure
Step 1 Cause 1: 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 807
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
1. On the NMS, check whether a 4.2.492 TU_LOP, 4.2.489 TU_AIS, or 4.2.103
DOWN_T1_AIS alarm is reported on the tributary board connected to the local tributary
board. If such an alarm exists, clear it and then check whether the UP_T1AIS alarm is
cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Go to the next step.
Step 2 Cause 2: 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.
1. Check whether a 4.2.473 T_ALOS or 4.2.499 UP_T1AIS alarm is reported on the peer
tributary board that receives 1.5 Mbit/s signals. If such an alarm exists, clear it and then
check whether the UP_T1AIS alarm is cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Go to the next step.
Step 3 Cause 3: The local board is faulty.
1. If the alarm persists, replace the relevant board of the opposite station. Then check
whether the alarm is cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Go to the next step.
2. Replace the board that reports the UP_T1AIS alarm. Then check whether the alarm is
cleared.
If… Then...
The alarm is cleared, No further action is required.
The alarm persists, Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 808
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.500 V5_VCAIS
Description
The V5_VCAIS alarm indicates that bits 5-7 of the V5 byte in the lower order VC-12 path are
all "1"s.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System
The TU path service transmission on the board is abnormal.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: A hardware fault alarm, such as the PLL_FAIL or CHIP_FAIL alarm, is
generated on the upstream board.
l Cause 2: The alarmed board is faulty.
Procedure
Step 1 Cause 1: A hardware fault alarm, such as the PLL_FAIL or CHIP_FAIL alarm, is generated
on the upstream board.
1. Check for hardware fault alarms, such as the PLL_FAIL or CHIP_FAIL alarm, on the
upstream board. If such an alarm occurs, clear the alarm first.
2. Check whether the V5_VCAIS alarm is cleared. If the alarm persists, go to Step 1.
Step 2 Cause 2: The alarmed board is faulty.
1. Perform a cold reset on the alarmed board.
2. Check whether the V5_VCAIS alarm is cleared. If the alarm persists, replace the
alarmed board.
3. Check whether the V5_VCAIS alarm is cleared. If the alarm persists, contact Huawei
technical support personnel to handle the alarm.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 809
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.501 VC_AIS
Description
The VC_AIS is an alarm indication signal of the virtual channel (VC) connection. When a
forward or backward VC connection that is configured with the segment/end point attribute
receives AIS cells, the VC_AIS alarm is reported indicating that the upstream services are
abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1 This parameter is used for the TDM-domain ATM board. The fixed value is
0x01 and the value is meaningless.
This parameter is used for packet-domain ATM boards and E1 interface
boards, and indicates connection direction.
l 0x01: forward
l 0x02: backward
Parameter 2, These parameters are used for the TDM-domain ATM board and indicate the
Parameter 3 connection ID and connection direction.
The value is the remainder of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
l ConnDir: the value 1 means forward and the value 2 means backward.
l ConnId: the value 1 means an odd number and the value 2 means an even number.
Parameter 2 is used for packet-domain ATM boards and E1 interface boards,
and indicates segment/end attribute of the alarm.
l 0x01: segment
l 0x02: end
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 810
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 This parameter is used for the TDM-domain ATM board and indicates the
group number.
The value is the integer result of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
The unidirectional connections of the alarm are divided on the 2048 base.
Parameter 5 This parameter is used for the TDM-domain ATM board and indicates the
source ATM port number of a certain connection in a certain direction.
l For the ATM board with the IMA function, the value of this parameter
ranges from 0x01 to 0x4A (1 to 74). The values 0x01 to 0x04 (1 to 4)
represent external optical port numbers; the values 0x05 to 0x4A (5 to 74)
represent internal VCTRUNK numbers.
l For the ATM board without the IMA function, the value of this parameter
ranges from 0x01 to 0x14. The values 0x01 to 0x04 (1 to 4) represent
external optical port numbers; the values 0x05 to 0x14 (5 to 20) represent
internal VCTRUNK numbers.
NOTE
Internal VCTRUNK numbers are calculated by applying the algorithm (VCTRUNK ID
- 0x8001 + 0x0005) to actual VCTRUNK IDs.
Impact on the System
l The continuity check (CC) sink of an upstream connection is activated, but the related
CC source is not activated, and no user cells are received because the current bandwidth
is zero. In this case, the upstream NE reports the CC_LOC alarm, and the AIS cells are
inserted at the downstream NE. Consequently, the local NE generates the VC_AIS
alarm. Services are not interrupted, but are unavailable in the connection.
l In other cases, the related VC connections have been interrupted when the VC_AIS
alarm is reported. Moreover, the AIS cells are continuously inserted at the downstream
station. In addition, the RDI cells are returned to the upstream station.
Possible Causes
Possible causes of the VC_AIS alarm are as follows:
l An upstream NE of the connection fails to receive signals in the SDH path. For example,
an SDH alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP, TU_AIS, or
TU_LOP, is reported at the NE.
l The LCD alarm is reported at an upstream ATM port of the connection.
l The CC sink of an upstream NE on the connection is activated, but the relevant CC
source is not activated, and no user cells are received because the current bandwidth is
zero. In this case, the upstream NE reports the CC_LOC alarm, and the AIS cells are
inserted at the downstream NE. Consequently, the local NE generates the VC_AIS
alarm.
l The ATM processing chip on the alarmed board is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 811
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Procedure
Step 1 View the VC_AIS alarm information on the U2000, and then confirm the connection where
the alarm is generated according to alarm parameters 2 and 3.
Step 2 Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,
TU_AIS, or TU_LOP, is generated in the SDH path of an upstream NE connected to the ATM
port. If yes, clear it, and then check whether the VC_AIS alarm is cleared. If the VC_AIS
alarm persists, go to the next step.
Step 3 Check whether the LCD alarm is reported at the ATM port on the ATM board of the upstream
NE. If yes, clear it, and then check whether the VC_AIS alarm at the local station is cleared.
Step 4 If the VC_AIS alarm persists, check whether the CC sink is activated at an upstream NE of
the connection but the CC source is not activated. If the CC sink is activated, deactivate it.
Moreover, check whether the CC_LOC alarm is reported. If yes, clear the CC_LOC alarm at
the upstream NE, and then check whether the VC_AIS alarm at the local NE is cleared.
Step 5 If the VC_AIS alarm persists, the ATM processing chip on the alarmed board may be faulty.
Reset (cold) the board and check whether the VC_AIS alarm is cleared.
If the services on the alarmed board are not configured with protection, the services are
interrupted after the board cold reset.
Step 6 If the VC_AIS alarm persists, replace the board that generates the alarm.
----End
Related Information
Unidirectional connection
A complete bidirectional connection is divided into a forward unidirectional connection and a
backward unidirectional connection. The direction of the forward and backward connections
is based on the same node.
End and segment
The end point refers to the termination point in the chain network, and it is used to monitor
the whole virtual connection. The segment point is, generally, used to monitor a segment of
the whole link.
Segment and end point
This is one of the segment end attributes. The segment end attributes include: segment point,
end point, segment and end point, non-segment and end point.
l If an NE is set with the segment end point attribute, it can retrieve the alarms that are
generated at the segment and end.
l If an NE is set with the segment point attribute, it can retrieve the alarms that are
generated at a segment.
l If an NE is set with the end point attribute, it can retrieve the alarms that are generated at
an end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 812
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l If an NE is set with the non-segment end point attribute, it fails to retrieve the alarms that
are generated at the segment and end.
4.2.502 VC_LOC
Description
The VC_LOC alarm indicates that the CC is enabled but no CC cells are received for more
than 3.5s (±0.5s). When any CC cell is received, the VC_LOC alarm is cleared automatically.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1 This parameter is used for the TDM-domain ATM board. The fixed value is
0x01 and the value is meaningless.
This parameter is used for packet-domain ATM boards and E1 interface
boards, and indicates connection direction.
l 0x01: forward
l 0x02: backward
Parameter 2, These parameters are used for the TDM-domain ATM board and indicate the
Parameter 3 connection ID and connection direction.
The value is the remainder of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
l ConnDir: the value 1 means forward and the value 2 means backward.
l ConnId: the value 1 means an odd number and the value 2 means an even number.
Parameter 2 is used for packet-domain ATM boards and E1 interface boards,
and indicates segment/end attribute of the alarm.
l 0x01: segment
l 0x02: end
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 813
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 This parameter is used for the TDM-domain ATM board and indicates the
group number.
The value is the integer result of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
The unidirectional connections of the alarm are divided on the 2048 base.
Parameter 5 This parameter is used for the TDM-domain ATM board and indicates the
source ATM port number of a certain connection in a certain direction.
l For the ATM board with the IMA function, the value of this parameter
ranges from 0x01 to 0x4A (1 to 74). The values 0x01 to 0x04 (1 to 4)
represent external optical port numbers; the values 0x05 to 0x4A (5 to 74)
represent internal VCTRUNK numbers.
l For the ATM board without the IMA function, the value of this parameter
ranges from 0x01 to 0x14. The values 0x01 to 0x04 (1 to 4) represent
external optical port numbers; the values 0x05 to 0x14 (5 to 20) represent
internal VCTRUNK numbers.
NOTE
Internal VCTRUNK numbers are calculated by applying the algorithm (VCTRUNK ID
- 0x8001 + 0x0005) to actual VCTRUNK IDs.
Impact on the System
l If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,
the service connection, though not interrupted, is not loaded with any user service.
l In other cases, the service is interrupted when the VC_LOC alarm is reported.
l When the VC_LOC alarm is reported, the system automatically inserts AIS cells to the
downstream.
l The VC_LOC alarm will be suppressed when the VC_AIS alarm is reported.
Possible Causes
The possible cause of the VC_LOC alarm is as follows:
l The CC sink is enabled on the local NE but no CC source is enabled on the upstream
NE. As a result, the local NE does not receive any CC cells.
l No bandwidth is available on the local NE and the CC cells cannot be received.
l An upstream SDH path is faulty. As a result, the ATM port connected to the faulty SDH
path abnormally receives signals.
l The LCD alarm is reported on an ATM port on an upstream NE.
l The board on the local NE is faulty.
Procedure
Step 1 On the U2000, check whether CC Activate Flag on the local NE is set to Sink activate or
Source + sink activate.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 814
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If... Then...
CC Activate Flag on the local NE is set to Sink Change CC Activate Flag to
activate or Source + sink activate Deactivate and check whether the
alarm is cleared.
CC Activate Flag on the local NE is not set to Sink Go to the next step.
activate or Source + sink activate
Step 2 On the U2000, check whether the bandwidth configured to the tunnel is exhausted. For
details, refer to the Configuration Guide.
If... Then...
The bandwidth configured to the Expand the bandwidth of tunnel or eliminate the
tunnel is exhausted source that transmits a large amount of illegal data.
Then, check whether the alarm is cleared.
The bandwidth configured to the Go to the next step.
tunnel is not exhausted
Step 3 Check whether there is any 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS, 4.2.20
AU_AIS or 4.2.21 AU_LOP alarm in the upstream SDH path.
If... Then...
There is an 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 clear the alarm and check
MS_AIS, 4.2.20 AU_AIS or 4.2.21 AU_LOP alarm in the whether the VC_LOC alarm is
upstream SDH path cleared.
There is no 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 Go to the next step.
MS_AIS, 4.2.20 AU_AIS or 4.2.21 AU_LOP alarm in the
upstream SDH path
Step 4 Check whether there is any LCD alarm is reported on an upstream NE and specific port.
If... Then...
There is an LCD alarm on the upstream NE Clear the LCD alarm and check
and specific port whether the VC_LOC alarm is cleared.
There is no LCD alarm on the upstream NE Go to the next step.
and specific port
Step 5 Reset (cold) the board that reports the VC_LOC alarm.
Step 6 Replace the board that reports the VC_LOC alarm.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 815
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None.
4.2.503 VC_RDI
Description
The VC_RDI is a remote defect indication of a virtual channel (VC) connection. When a
forward or backward VC connection that is set with the segment and endpoint attribute
receives RDI cells, the VC_RDI is reported indicating that the downstream services are
abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1 This parameter is used for the TDM-domain ATM board. The fixed value is
0x01 and the value is meaningless.
This parameter is used for packet-domain ATM boards and E1 interface
boards, and indicates connection direction.
l 0x01: forward
l 0x02: backward
Parameter 2, These parameters are used for the TDM-domain ATM board and indicate the
Parameter 3 connection ID and connection direction.
The value is the remainder of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
l ConnDir: the value 1 means forward and the value 2 means backward.
l ConnId: the value 1 means an odd number and the value 2 means an even number.
Parameter 2 is used for packet-domain ATM boards and E1 interface boards,
and indicates segment/end attribute of the alarm.
l 0x01: segment
l 0x02: end
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 816
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 4 This parameter is used for the TDM-domain ATM board and indicates the
group number.
The value is the integer result of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
The unidirectional connections of the alarm are divided on the 2048 base.
Parameter 5 This parameter is used for the TDM-domain ATM board and indicates the
source ATM port number of a certain connection in a certain direction.
l For the ATM board with the IMA function, the value of this parameter
ranges from 0x01 to 0x4A (1 to 74). The values 0x01 to 0x04 (1 to 4)
represent external optical port numbers; the values 0x05 to 0x4A (5 to 74)
represent internal VCTRUNK numbers.
l For the ATM board without the IMA function, the value of this parameter
ranges from 0x01 to 0x14. The values 0x01 to 0x04 (1 to 4) represent
external optical port numbers; the values 0x05 to 0x14 (5 to 20) represent
internal VCTRUNK numbers.
NOTE
Internal VCTRUNK numbers are calculated by applying the algorithm (VCTRUNK ID
- 0x8001 + 0x0005) to actual VCTRUNK IDs.
Impact on the System
When the VC_RDI alarm is reported, the services are not affected. This alarm just shows that
the services in the receive direction of the downstream VC connection are abnormal. The AIS
cells are received in a segment point of the connection, and the RDI cells are returned to the
upstream VC connection.
Possible Causes
Possible causes of the VC_RDI alarm are as follows:
l The VC_AIS alarm is reported in the receive direction of the downstream connection.
l The ATM processing chip of the board is faulty.
Procedure
Step 1 View the VC_RDI alarm on the U2000, and then confirm the relevant connection according to
Parameters 2 and 3.
Step 2 Check whether the 4.2.501 VC_AIS alarm is reported in the receive direction of the
downstream VC connection. If yes, clear it, and then check whether the VC_RDI alarm is
cleared.
Step 3 If the alarm persists, the ATM processing chip of the board may be faulty. Reset (cold) the
board. Then check whether the VC_RDI alarm is cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 817
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
If the services travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
Step 4 If the alarm persists, replace the board that generates the VC_RDI alarm.
----End
Related Information
Unidirectional Connection
A complete bidirectional connection is divided into a forward unidirectional connection and a
backward unidirectional connection. The direction of the forward and backward connections
is based on the same node.
End and Segment
The end point refers to the termination point in the chain network, and it is used to monitor
the whole virtual connection. The segment point is, generally, used to monitor a segment of
the whole link.
Segment and end point
This is one of the segment end attributes. The segment/end attributes include: segment point,
end point, segment and end point, non-segment and end point.
l If an NE is set with the segment end point attribute, it can retrieve the alarms that are
generated at the segment and end.
l If an NE is set with the segment point attribute, it can retrieve the alarms that are
generated at a segment.
l If an NE is set with the end point attribute, it can retrieve the alarms that are generated at
an end.
l If an NE is set with the non-segment end point attribute, it fails to retrieve the alarms that
are generated at the segment and end.
4.2.504 VCAT_LOA
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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 818
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, parameter 3 Indicates the VC trunk number that generates the alarm.
Impact on the System
During the service data transmission, when the alignment time of the virtual concatenation
delay is over long, the timeslots cannot form a data frame. Accordingly, it causes the packet
loss
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows:
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.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
4.2.505 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 alarm indicates that multiframe of the VC-12 virtual concatenation
is lost.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 819
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
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.
l Bit errors occur or the SDH physical path is interrupted.
Procedure
Step 1 Configure the cross-connect loopback to check whether the alarm is cleared.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.506 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 alarm indicates multiframe of the VC-3 virtual concatenation is lost.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 820
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
Possible causes of the VCAT_LOM_VC3 alarm are as follows:
l The MFI at the opposite end of the virtual concatenation is inconsistent with that at the
local end.
l Bit errors occur or the SDH physical path is interrupted.
Procedure
Step 1 Configure the cross-connect loopback to check whether the alarm is cleared.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.507 VCAT_LOM_VC4
Description
The VCAT_LOM_VC4 alarm indicates that multiframe of the VC-4 virtual concatenation is
lost. 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 821
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-4 path number that generates the alarm.
Impact on the System
If the LCAS function is disabled, the services are interrupted during data transmission.
Possible Causes
Possible causes of the VCAT_LOM_VC4 alarm are as follows:
l The MFI at the opposite end of the virtual concatenation is inconsistent with that at the
local end.
l Bit errors occur or the SDH physical path is interrupted.
Procedure
Step 1 Configure the cross-connect loopback to check whether the alarm is cleared.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.508 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 alarm indicates SQ mismatch of the VC-12 virtual concatenation.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 822
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-12 path number that generates the alarm.
Impact on the System
During the data transmission, the error occurs to the reassembly of the received serial
numbers and the framing fails. Accordingly, the services are interrupted.
Possible Causes
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.
l Bit errors occur in the SDH physical path or the path is interrupted.
Procedure
Step 1 Configure the cross-connect loopback to check whether the alarm is cleared.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.509 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 alarm indicates SQ mismatch of the VC-3 virtual concatenation.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 823
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-3 path number that generates the alarm.
Impact on the System
During the data transmission, the error occurs to the reassembly of the received serial
numbers and the framing fails. Accordingly, the services are interrupted.
Possible Causes
Possible causes of the VCAT_SQM_VC3 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.
l Bit errors occur in the SDH physical path or the path is interrupted.
Procedure
Step 1 Configure the cross-connect loopback to check whether the alarm is cleared.
Step 2 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.2.510 VCAT_SQM_VC4
Description
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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 824
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number, and the value is always 0x01.
Parameter 2, Parameter 3 Indicates the VC-4 path number that generates the alarm.
Impact on the System
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
Possible causes of the VCAT_SQM_VC4 alarm are as follows:
l The BIP_EXC alarm and BIP_SD alarm occur on the line.
l The sequence number sent by the opposite end is incorrect.
Procedure
Step 1 Determine the board that reports the VCAT_SQM_VC4 alarm according to the alarm
information on the U2000.
Step 2 Check whether the alarmed board reports the BIP_EXC alarm and BIP_SD alarm on the
U2000. If the alarmed 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 If the VCAT_SQM_VC4 alarm persists, check whether the alarmed board that reports the
VCAT_SQM_VC4 alarm is faulty. Replace the alarmed 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.
Step 5 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 825
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.511 VCTRUNK_NO_FLOW
Description
The VCTRUNK_NO_FLOW is an alarm indicating that the VCTRUNK port has no traffic. If
the VCTRUNK port has no traffic, the VCTRUNK_NO_FLOW alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Service 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicate the direction in which the traffic stops.
l 0x00: the RX direction.
l 0x01: the TX direction.
Parameter 2, Parameter 3, Parameter 4 The value of this parameter is always 0xff.
Impact on the System
In the case of the VCTRUNK_NO_FLOW alarm, services are not affected.
Possible Causes
The possible causes of the VCTRUNK_NO_FLOW alarm are as follows:
l No services are configured at the local end.
l The local end has abnormal alarms, or does not transmit packets.
l The opposite end has abnormal services, or no packets arrive at the local end.
Procedure
Step 1 Check whether any service is configured at the port. If not, check whether carelessness causes
the missing of service configuration.
Step 2 If yes, confirm the direction in which the traffic stops according to Parameter 1.
l If the traffic stops in the TX direction, check whether the local services are abnormal.
l If the traffic stops in the RX direction, check whether the local cross-connections are
correctly configured.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 826
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
– If not, rectify the incorrect configuration, and then check whether the
VCTRUNK_NO_FLOW alarm is cleared.
– If not, check whether the fiber in the RX direction is damaged. If the fiber is
damaged, replace the fiber and then check whether the VCTRUNK_NO_FLOW
alarm is cleared.
– If not, check whether the cross-connect board and line board involved in the RX
direction work normally. If not, replace the faulty board.
----End
Related Information
None.
4.2.512 VP_AIS
Description
The VP_AIS is an alarm indication signal of the virtual path. When a forward or backward
VP connection that is set with the segment and end point attribute receives AIS cells, the
VC_AIS alarm is reported indicating that the upstream services are abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1 This parameter is used for the TDM-domain ATM board. The fixed value is
0x01 and the value is meaningless.
This parameter is used for packet-domain ATM boards and E1 interface
boards, and indicates connection direction.
l 0x01: forward
l 0x02: backward
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 827
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2, These parameters are used for the TDM-domain ATM board and indicate the
Parameter 3 connection ID and connection direction.
The value is the remainder of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
l ConnDir: the value 1 means forward and the value 2 means backward.
l ConnId: the value 1 means an odd number and the value 2 means an even number.
Parameter 2 is used for packet-domain ATM boards and E1 interface boards,
and indicates segment/end attribute of the alarm.
l 0x01: segment
l 0x02: end
Parameter 4 This parameter is used for the TDM-domain ATM board and indicates the
group number.
The value is the integer result of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
The unidirectional connections of the alarm are divided on the 2048 base.
Parameter 5 This parameter is used for the TDM-domain ATM board and indicates the
source ATM port number of a certain connection in a certain direction.
l For the ATM board with the IMA function, the value of this parameter
ranges from 0x01 to 0x4A (1 to 74). The values 0x01 to 0x04 (1 to 4)
represent external optical port numbers; the values 0x05 to 0x4A (5 to 74)
represent internal VCTRUNK numbers.
l For the ATM board without the IMA function, the value of this parameter
ranges from 0x01 to 0x14. The values 0x01 to 0x04 (1 to 4) represent
external optical port numbers; the values 0x05 to 0x14 (5 to 20) represent
internal VCTRUNK numbers.
NOTE
Internal VCTRUNK numbers are calculated by applying the algorithm (VCTRUNK ID
- 0x8001 + 0x0005) to actual VCTRUNK IDs.
Impact on the System
l The continuity check (CC) sink of an upstream NE on the connection is activated but the
CC source is not activated, and no user cells are received because the current bandwidth
is zero. In this case, the upstream NE reports the CC_LOC alarm and the AIS cells are
inserted at the downstream station. Consequently, the local NE generates the VC_AIS
alarm. At this time, the services are not interrupted, but are unavailable in the
connection.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 828
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l In other cases, the related VP connections have been interrupted when the VP_AIS alarm
is reported. Moreover, the AIS cells are continuously inserted at the downstream NE. In
addition, the RDI cells are returned to the upstream NE.
Possible Causes
Possible causes of the VP_AIS alarm are as follows:
l An upstream NE of a connection fails to receive signals in the SDH path. For example,
an SDH alarm, such as R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP, TU_AIS, or
TU_LOP, is reported.
l The LCD alarm is reported at an upstream ATM port on the connection.
l The CC sink of an upstream NE on a connection is activated but the CC source is not
activated, and no user cells are received because the current bandwidth is zero. In this
case, the upstream NE reports the CC_LOC alarm, and the AIS cells are inserted at the
downstream NE. Consequently, the local NE generates the VP_AIS alarm.
l The ATM processing chip on the board is faulty.
Procedure
Step 1 View the VP_AIS alarm information on the U2000, and then confirm the connection where
the alarm is generated according to alarm parameters 2 and 3.
Step 2 Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,
TU_AIS, or TU_LOP, is reported in the SDH path of an upstream NE connected to the
alarmed ATM port. If yes, clear it and check whether the VP_AIS alarm is cleared. If the
VP_AIS alarm persists, Proceed to the next step.
Step 3 Check whether the LCD alarm is reported at the ATM port on the ATM board of the upstream
NE. If yes, clear it and check whether the VP_AIS alarm is cleared.
Step 4 If the VP_AIS alarm persists, check whether the CC sink of an upstream NE on the
connection is activated but the CC source is not activated. If the CC sink is activated,
deactivate it. Moreover, check whether the CC_LOC alarm is reported. If yes, clear it and
check whether the VP_AIS alarm is cleared.
Step 5 If the VP_AIS alarm persists, the ATM processing chip may be faulty. Reset (cold) the board
that generates the alarm and check whether the VP_AIS alarm is cleared.
If the services on the alarmed board are not configured with protection, the services are
interrupted after the board cold reset of the board.
Step 6 If the alarm persists, replace the board that generates the VP_AIS alarm.
----End
Related Information
Unidirectional Connection
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 829
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
A complete bidirectional connection is divided into a forward unidirectional connection and a
backward unidirectional connection. The direction of the forward and backward connections
is based on the same node.
End and Segment
The end point refers to the termination point in the chain network, and it is used to monitor
the whole virtual connection. The segment point is, generally, used to monitor a segment of
the whole link.
Segment and end point
This is one of the segment end attributes. The segment end attributes include: segment point,
end point, segment and end point, non-segment and end point.
l If an NE is set with the segment end point attribute, it can retrieve the alarms that are
generated at the segment and end.
l If an NE is set with the segment point attribute, it can retrieve the alarms that are
generated at a segment.
l If an NE is set with the end point attribute, it can retrieve the alarms that are generated at
an end.
l If an NE is set with the non-segment end point attribute, it fails to retrieve the alarms that
are generated at the segment and end.
4.2.513 VP_LOC
Description
The VP_LOC alarm indicates loss of continuity check (CC) on the virtual channel (VP).
When the CC is enabled but no CC cells are received for more than 3.5s (±0.5s), the VP_LOC
alarm is reported. When any CC cell is received, the VP_LOC alarm is cleared automatically.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1 This parameter is used for the TDM-domain ATM board. The fixed value is
0x01 and the value is meaningless.
This parameter is used for packet-domain ATM boards and E1 interface
boards, and indicates connection direction.
l 0x01: forward
l 0x02: backward
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 830
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2, These parameters are used for the TDM-domain ATM board and indicate the
Parameter 3 connection ID and connection direction.
The value is the remainder of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
l ConnDir: the value 1 means forward and the value 2 means backward.
l ConnId: the value 1 means an odd number and the value 2 means an even number.
Parameter 2 is used for packet-domain ATM boards and E1 interface boards,
and indicates segment/end attribute of the alarm.
l 0x01: segment
l 0x02: end
Parameter 4 This parameter is used for the TDM-domain ATM board and indicates the
group number.
The value is the integer result of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
The unidirectional connections of the alarm are divided on the 2048 base.
Parameter 5 This parameter is used for the TDM-domain ATM board and indicates the
source ATM port number of a certain connection in a certain direction.
l For the ATM board with the IMA function, the value of this parameter
ranges from 0x01 to 0x4A (1 to 74). The values 0x01 to 0x04 (1 to 4)
represent external optical port numbers; the values 0x05 to 0x4A (5 to 74)
represent internal VCTRUNK numbers.
l For the ATM board without the IMA function, the value of this parameter
ranges from 0x01 to 0x14. The values 0x01 to 0x04 (1 to 4) represent
external optical port numbers; the values 0x05 to 0x14 (5 to 20) represent
internal VCTRUNK numbers.
NOTE
Internal VCTRUNK numbers are calculated by applying the algorithm (VCTRUNK ID
- 0x8001 + 0x0005) to actual VCTRUNK IDs.
Impact on the System
l If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,
the service connection, though not interrupted, is not loaded with any user service.
l In other cases, the service is interrupted when the VP_LOC alarm is reported.
l When the VP_LOC alarm is reported, the system automatically inserts AIS cells to the
downstream.
l The VP_LOC alarm will be suppressed when the VP_AIS alarm is reported.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 831
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Possible Causes
Possible causes of the VP_LOC alarm are as follows:
l The CC sink is enabled on the local NE but no CC source is enabled on the upstream
NE. As a result, the local NE does not receive any CC cells.
l No bandwidth is available on the local NE and the CC cells cannot be received.
l An upstream SDH path is faulty. As a result, the ATM port connected to the faulty SDH
path abnormally receives signals.
l The LCD alarm is reported on an ATM port on an upstream NE.
l The board on the local NE is faulty.
Procedure
Step 1 On the U2000, check whether CC Activate Flag on the local NE is set to Sink activate or
Source + sink activate.
If... Then...
The CC Activate Flag on the local NE is set to Sink Change CC Activate Flag to
activate or Source + sink activate Deactivate and check whether the
alarm is cleared.
The CC Activate Flag on the local NE is not set to Go to the next step.
Sink activate or Source + sink activate
Step 2 On the U2000, check whether the bandwidth configured to the tunnel is exhausted. For
details, refer to the Configuration Guide.
If... Then...
The bandwidth configured to the Expand the bandwidth of tunnel or eliminate the
tunnel is exhausted source that transmits a large amount of illegal data.
Then, check whether the alarm is cleared.
The bandwidth configured to the Go to the next step.
tunnel is not exhausted
Step 3 Check whether there is any 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 MS_AIS, 4.2.20
AU_AIS or 4.2.21 AU_LOP alarm in the upstream SDH path.
If... Then...
There is an 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 Clear the alarm and check
MS_AIS, 4.2.20 AU_AIS or 4.2.21 AU_LOP alarm in the whether the VP_LOC alarm is
upstream SDH path cleared.
There is no 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305 Go to the next step.
MS_AIS, 4.2.20 AU_AIS or 4.2.21 AU_LOP alarm in the
upstream SDH path
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 832
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Step 4 Check whether there is any LCD alarm on the upstream NE and specific port.
If... Then...
There is an LCD alarm on the upstream NE Clear the LCD alarm and check
and specific port whether the VP_LOC alarm is cleared.
There is no LCD alarm on the upstream NE Go to the next step.
and specific port
Step 5 Reset (cold) the board that reports the VP_LOC alarm.
Step 6 Replace the board that reports the VP_LOC alarm.
----End
Related Information
None.
4.2.514 VP_RDI
Description
The VP_RDI is a remote defect indication for a virtual path. When a forward or backward VP
connection that is set with the segment and end point attribute receives the RDI cells, the
VP_RDI alarm is reported indicating that the downstream services are abnormal.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameter 1 This parameter is used for the TDM-domain ATM board. The fixed value is
0x01 and the value is meaningless.
This parameter is used for packet-domain ATM boards and E1 interface
boards, and indicates connection direction.
l 0x01: forward
l 0x02: backward
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 833
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Name Meaning
Parameter 2, These parameters are used for the TDM-domain ATM board and indicate the
Parameter 3 connection ID and connection direction.
The value is the remainder of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
l ConnDir: the value 1 means forward and the value 2 means backward.
l ConnId: the value 1 means an odd number and the value 2 means an even number.
Parameter 2 is used for packet-domain ATM boards and E1 interface boards,
and indicates segment/end attribute of the alarm.
l 0x01: segment
l 0x02: end
Parameter 4 This parameter is used for the TDM-domain ATM board and indicates the
group number.
The value is the integer result of applying the algorithm ((ConnId - 1)×2 +
ConnDir)/2048 to connection ID (Connld) and connection direction
(ConnDir).
NOTE
The unidirectional connections of the alarm are divided on the 2048 base.
Parameter 5 This parameter is used for the TDM-domain ATM board and indicates the
source ATM port number of a certain connection in a certain direction.
l For the ATM board with the IMA function, the value of this parameter
ranges from 0x01 to 0x4A (1 to 74). The values 0x01 to 0x04 (1 to 4)
represent external optical port numbers; the values 0x05 to 0x4A (5 to 74)
represent internal VCTRUNK numbers.
l For the ATM board without the IMA function, the value of this parameter
ranges from 0x01 to 0x14. The values 0x01 to 0x04 (1 to 4) represent
external optical port numbers; the values 0x05 to 0x14 (5 to 20) represent
internal VCTRUNK numbers.
NOTE
Internal VCTRUNK numbers are calculated by applying the algorithm (VCTRUNK ID
- 0x8001 + 0x0005) to actual VCTRUNK IDs.
Impact on the System
When the VP_RDI alarm is reported, services are not affected. This alarm only indicates that
the services in the receive direction of the downstream VP connection are abnormal. The AIS
cells are received in a segment point of the connection and the RDI cells are returned to the
upstream VC connection.
Possible Causes
Possible causes of the VP_RDI alarm are as follows:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 834
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
l The VP_AIS alarm is reported in the receive direction of the downstream connection.
l The ATM processing chip on the alarmed board is faulty.
Procedure
Step 1 View the VP_RDI alarm information on the U2000 and confirm the connection where the
alarm is generated according to alarm parameters 2 and 3.
Step 2 Check whether the 4.2.512 VP_AIS alarm is reported in the receive direction of the
downstream connection. If yes, clear it and check whether the VP_RDI alarm is cleared.
Step 3 If the VP_RDI alarm persists, the ATM processing chip on the board may be faulty. Reset
(cold) the board and check whether the VP_RDI alarm is cleared.
If services on a board are not configured with protection, the services are interrupted after the
board cold reset.
Step 4 If the VP_RDI alarm persists, replace the board that generates the alarm.
----End
Related Information
Unidirectional connection
A complete bidirectional connection is divided into a forward unidirectional connection and a
backward unidirectional connection. The direction of the forward and backward connections
is based on the same node.
End and segment
The end point refers to the termination point in the chain network, and it is used to monitor
the whole virtual connection. The segment point is, generally, used to monitor a segment of
the whole link.
Segment and end point
This is one of the segment end attributes. The segment end attributes include: segment point,
end point, segment and end point, non-segment and end point.
l If an NE is set with the segment end point attribute, it can retrieve the alarms that are
generated at the segment and end.
l If an NE is set with the segment point attribute, it can retrieve the alarms that are
generated at a segment.
l If an NE is set with the end point attribute, it can retrieve the alarms that are generated at
an end.
l If an NE is set with the non-segment end point attribute, it fails to retrieve the alarms that
are generated at the segment and end.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 835
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.515 W_OFFLINE
Description
The W_OFFLINE alarm indicates that an ejector lever cannot be detected.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: The upper ejector lever cannot be detected.
l 0x02: The lower ejector lever cannot be detected.
Impact on the System
The board is not in good contact with the backplane, possibly causing serious faults. If 1+1
protection is configured for the system control, switching, and timing boards, an active/
standby switchover may occur.
Possible Causes
l Cause 1: The ejector lever is open.
l Cause 2: The micro switch of the ejector lever is faulty.
Procedure
Step 1 Cause 1: The ejector lever is open.
Step 2 Cause 2: The micro switch of the ejector lever is faulty.
1. Lock the ejector lever.
2. If the alarm persists, replace the board.
3. If the alarm persists, contact Huawei technical support personnel to handle the alarm.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 836
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.516 W_R_FAIL
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.
Impact on the System
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 The board is faulty.
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...
If this alarm is cleared The fault is removed. End the alarm
handling.
If this alarm persists Proceed to the next step.
Step 3 If the board hardware is faulty, replace the relevant board.
Performing a hard reset on the board or replacing the board will interrupt services. This
operation is of risk.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 837
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
Related Information
None
4.2.517 WAVEDATA_MIS
Description
The WAVEDATA_MIS indicates a wavelength or band mismatch. If the operating wavelength
or band differs from the configured value, the alarm is reported.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Impact on the System
The service may be interrupted.
Possible Causes
l Cause 1: The operating wavelength or band differs from the configured value.
l Cause 2: The board is faulty.
Procedure
l Cause 1: The operating wavelength or band differs from the configured value.
a. Query the operating wavelength and configured wavelength of the board on the
NMS. If the two values differ, set the wavelength consistently with the actual
operating wavelength of the optical module.
l Cause 2: The board is faulty.
a. If the alarm persists, replace the board or optical module with another one whose
operating wavelength is the same as the configured value. For details, see the Parts
Replacement.
----End
Related Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 838
OptiX OSN 500/550/580
Alarms and Performance Events Reference 4 Alarm Reference
4.2.518 WRG_BD_TYPE
Description
The WRG_BD_TYPE alarm indicates 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.
Impact on the System
The WRG_BD_TYPE alarm does not affect the existing services and the operation of the
system. The alarmed board, however, cannot be configured with services.
Possible Causes
Possible causes of the WRG_BD_TYPE alarm are as follows:
l The types of the logical board and the physical board are different.
l The board is faulty.
Procedure
Step 1 Check whether the types of the logical board and the physical board are the same.
If... Then...
The types of the logical board and the Add a logical board according to the type of
physical board are different physical board. Check whether the alarm is
cleared. If the alarm persists, go to the next
step.
The types of the logical board and the Go to the next step.
physical board are the same
Step 2 Replace the alarmed board.
----End
Related Information
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 839
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5 Performance Event Reference
About This Chapter
This chapter describes the performance events of the equipment. In this chapter, the categories
and the troubleshooting are involved.
5.1 Performance Event List (OSN 500)
This section describes the performance events supported by the equipment in a tabular form.
5.2 Performance Event List (OSN 550)
This section describes the performance events supported by the equipment in a tabular form.
5.3 Performance Event List (OSN 580)
This section describes the performance events supported by the equipment in a tabular form.
5.4 Performance Event Clearing
This section describes how to handle the performance events.
5.5 RMON Event of the Ethernet Service List
This section uses a table to list the RMON performance events corresponding to the boards
supported by the equipment.
5.6 RMON Event of the Ethernet Service Description
Ethernet service performance events indicate the transmission quality of the Ethernet services.
This topic lists the main RMON events in the packet domain.
5.1 Performance Event List (OSN 500)
This section describes the performance events supported by the equipment in a tabular form.
Table 5-1 E1 line side bit error performance events
Abbreviation Details Unit
E1_LCV_SDH Count of E1 line side code second
violations
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 840
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
E1_LES_SDH E1 line side code violation error
second
E1_LLOSS_SD E1 line loss-of-signal seconds
H
E1_LSES_SDH E1 line side code violation
severely error second
Table 5-2 Equipment function performance events
Abbreviation Details Unit
BDTEMPMAX Maximum value of board 0.1°C
temperature
BDTEMPMIN Minimum value of board
temperature
BDTEMPCUR Current value of board temperature
TLBMAX Maximum value of laser bias 0.1mA
current
TLBMIN Minimum value of laser bias
current
TLBCUR Current value of laser bias current
TPLMAX Maximum value of output optical 0.1dBm
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
OSPITMPMA Maximum value of laser working 0.1°C
X temperature
OSPITMPMIN Minimum value of laser working
temperature
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 841
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
OSPITMPCUR Current value of laser working
temperature
5.2 Performance Event List (OSN 550)
This section describes the performance events supported by the equipment in a tabular form.
Table 5-3 Pointer justification performance events
Abbreviation Details Unit
AUPJCHIGH Count of positive AU pointer Block/times
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 5-4 E1 line side bit error performance events
Abbreviation Details Unit
E1_LCV_SDH Count of E1 line side code second
violations
E1_LES_SDH E1 line side code violation errored
second
E1_LLOSS_SD E1 line loss-of-signal seconds
H
E1_LSES_SDH E1 line side code violation
severely errored second
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 842
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-5 Regenerator section bit error performance events
Abbreviation Details Unit
RSBBE Regenerator section block of Block
background error
RSES Regenerator section errored second
second
RSSES Regenerator section severely
errored second
RSOOF Regenerator section out-of-frame Block
RSOFS Regenerator section out-of-frame second
second
RSUAS Regenerator section unavailable
second
RSCSES Regenerator section consecutive
severely second
Table 5-6 Multiplex section bit error performance events
Abbreviation Details Unit
MSBBE Multiplex section block of Block
background error
MSES Multiplex section errored second 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 Block
background error
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 843
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
MSFECSES Multiplex section far end second
consecutive severely errored
second
Table 5-7 Higher order path bit error performance events
Abbreviation Details Unit
HPBBE Higher order path block of Block
background error
HPFEBBE Higher order path far end block of
background error
HPES Higher order path errored second 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 5-8 Lower order path bit error performance events
Abbreviation Details Unit
LPBBE Lower order path block of Block
background error
LPFEBBE Lower order path far end block of
background error
LPES Lower order path errored second second
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 844
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
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 5-9 T1 line side bit error performance events
Abbreviation Details Unit
T1_LCV_SDH Count of T1 line side code second
violations
T1_LES_SDH T1 line side code violation errored
second
T1_LSES_SDH T1 line side code violation
severely errored second
Table 5-10 Equipment function performance events
Abbreviation Details Unit
BDTEMPMAX Maximum value of board 0.1°C
temperature
BDTEMPMIN Minimum value of board
temperature
BDTEMPCUR Current value of board temperature
TLBMAX Maximum value of laser bias 0.1mA
current
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 845
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
TLBMIN Minimum value of laser bias
current
TLBCUR Current value of laser bias current
TPLMAX Maximum value of output optical 0.1dBm
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
OSPITMPMA Maximum value of laser working 0.1°C
X temperature
OSPITMPMIN Minimum value of laser working
temperature
OSPITMPCUR Current value of laser working
temperature
BCVCUR Current back facet current of the 0.1mA
pump laser
BCVMAX Maximum back facet current of the
pump laser
BCVMIN Minimum back facet current of the
pump laser
CCVCUR Current cooling current of the
pump laser
CCVMAX Maximum cooling current of the
pump laser
CCVMIN Minimum cooling current of the
pump laser
EDTMPCUR Current ambient temperature for 0.1°C
the laser
EDTMPMAX Maximum ambient temperature for
the laser
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 846
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
EDTMPMIN Minimum ambient temperature for
the laser
SUMIOPCUR Current total input optical power 0.1dBm
SUMIOPMAX Maximum total input optical
power
SUMIOPMIN Minimum total input optical power
SUMOOPCUR Current total output optical power
SUMOOPMA Maximum total output optical
X power
SUMOOPMIN Minimum total output optical
power
WCVCUR Current working current of the 0.1mA
pump laser
WCVMAX Maximum working current of the
pump laser
WCVMIN Minimum working current of the
pump laser
XCSTMPCUR Current ambient temperature for 0.1°C
the board
XCSTMPMAX Maximum ambient temperature for
the board
XCSTMPMIN Minimum ambient temperature for
the board
Table 5-11 VC3 path bit error performance events
Abbreviation Details Unit
VC3BBE Lower order path block of Block
background error
VC3FEBBE Lower order path far end block of
background error
VC3ES Lower order path errored second second
VC3FEES Lower order path far end errored
second
VC3SES Lower order path severely errored
second
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 847
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
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
Table 5-12 1588 V2 clock performance events
Abbreviation Details Unit
MAXFREQDE Maximum value of frequency ns
V deviation
MINFREQDE Minimum value of frequency
V deviation
AVGFREQDE Average value of frequency
V deviation
MAXPHASEO Maximum value of phase offset
FFSET
MINPHASEOF Minimum value of phase offset
FSET
AVGPHASEOF Average value of phase offset
FSET
MAXMEANPA Maximum value of path delay
THDELAY
MINMEANPA Minimum value of path delay
THDELAY
AVGMEANPA Average value of path delay
THDELAY
CURPOSITIVE Current value of positive PDV
PDV
MAXPOSITIV Maximum value of positive delay
EDELAY
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 848
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
MINPOSITIVE Minimum value of positive delay
DELAY
AVGPOSITIVE Average value of positive delay
DELAY
Table 5-13 PCM Performance Events
Abbreviation Details Unit
CRC4_ERR CRC4 error Block
DDN_CRC4_E DDN-side CRC4 error
RR
SIGNAL_TOG Signal bit flip (from 0 to 1 or from second
GLE_SEC 1 to 0) second
CO64K_LCV_ Codirectional 64K line-side code Block
SDH violation
CO64K_LES_S Codirectional 64K line-side code second
DH violation errored second
CO64K_LSES_ Codirectional 64K line-side code
SDH violation severely errored second
R_VOICE_PE Maximum peak value of received -
AK_MAX audio
R_VOICE_PE Minimum peak value of received
AK_MIN audio
R_VOICE_PE Current peak value of received
AK_CUR audio
R_VOICE_TR Maximum trough value of
OUGH_MAX received audio
R_VOICE_TR Minimum trough value of received
OUGH_MIN audio
R_VOICE_TR Current trough value of received
OUGH_CUR audio
R_VOICE_AV Maximum average value of
G_MAX received audio
R_VOICE_AV Minimum average value of
G_MIN received audio
R_VOICE_AV Current average value of received
G_CUR audio
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 849
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
T_VOICE_PEA Maximum peak value of
K_MAX transmitted audio
T_VOICE_PEA Minimum peak value of
K_MIN transmitted audio
T_VOICE_PEA Current peak value of transmitted
K_CUR audio
T_VOICE_TR Maximum trough value of
OUGH_MAX transmitted audio
T_VOICE_TR Minimum trough value of
OUGH_MIN transmitted audio
T_VOICE_TR Current trough value of
OUGH_CUR transmitted audio
T_VOICE_AV Maximum average value of
G_MAX transmitted audio
T_VOICE_AV Minimum average value of
G_MIN transmitted audio
T_VOICE_AV Current average value of
G_CUR transmitted audio
HPS_PATH_CR a CRC and sequence number error Block
C_ERR occurs on the working or
protection channel of a hitless
protection group.
Table 5-14 C37.94 Line-side Code Violations Performance Events
Abbreviation Details Unit
C3794_LCV_SDH Count of C37.94 line-side Block
code violations
C3794_LES_SDH Error seconds of C37.94 second
line-side code violations
C3794_LSES_SDH Severely error seconds of second
C37.94 line-side code
violations
5.3 Performance Event List (OSN 580)
This section describes the performance events supported by the equipment in a tabular form.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 850
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-15 Pointer justification performance events
Abbreviation Details Unit
AUPJCHIGH Count of positive AU pointer Block/times
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 5-16 E1 line side bit error performance events
Abbreviation Details Unit
E1_LCV_SDH Count of E1 line side code second
violations
E1_LES_SDH E1 line-side code violation errored
second
E1_LSES_SDH E1 line-side code violation
severely errored second
Table 5-17 Regenerator section bit error performance events
Abbreviation Details Unit
RSBBE Regenerator section block of Block
background error
RSES Regenerator section errored second
second
RSSES Regenerator section severely
errored second
RSOOF Regenerator section out-of-frame Block
RSOFS Regenerator section out-of-frame second
second
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 851
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
RSUAS Regenerator section unavailable
second
RSCSES Regenerator section consecutive
severely second
Table 5-18 Multiplex section bit error performance events
Abbreviation Details Unit
MSBBE Multiplex section block of Block
background error
MSES Multiplex section errored second 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 Block
background error
MSFECSES Multiplex section far end second
consecutive severely errored
second
Table 5-19 Higher order path bit error performance events
Abbreviation Details Unit
HPBBE Higher order path block of Block
background error
HPFEBBE Higher order path far end block of
background error
HPES Higher order path errored second second
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 852
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
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 5-20 Lower order path bit error performance events
Abbreviation Details Unit
LPBBE Lower order path block of Block
background error
LPFEBBE Lower order path far end block of
background error
LPES Lower order path errored second 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 853
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
LPFEUAS Lower order path far end
unavailable second
Table 5-21 T1 line side bit error performance events
Abbreviation Details Unit
T1_LCV_SDH Count of T1 line side code second
violations
T1_LES_SDH T1 line side code violation errored
second
T1_LSES_SDH T1 line side code violation
severely errored second
Table 5-22 Equipment function performance events
Abbreviation Details Unit
BDTEMPMAX Maximum value of board 0.1°C
temperature
BDTEMPMIN Minimum value of board
temperature
BDTEMPCUR Current value of board temperature
TLBMAX Maximum value of laser bias 0.1mA
current
TLBMIN Minimum value of laser bias
current
TLBCUR Current value of laser bias current
TPLMAX Maximum value of output optical 0.1dBm
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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 854
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
RPLCUR Current value of input optical
power
OSPITMPMA Maximum value of laser working 0.1°C
X temperature
OSPITMPMIN Minimum value of laser working
temperature
OSPITMPCUR Current value of laser working
temperature
BCVCUR Current back facet current of the 0.1mA
pump laser
BCVMAX Maximum back facet current of the
pump laser
BCVMIN Minimum back facet current of the
pump laser
CCVCUR Current cooling current of the
pump laser
CCVMAX Maximum cooling current of the
pump laser
CCVMIN Minimum cooling current of the
pump laser
EDTMPCUR Current ambient temperature for 0.1°C
the laser
EDTMPMAX Maximum ambient temperature for
the laser
EDTMPMIN Minimum ambient temperature for
the laser
SUMIOPCUR Current total input optical power 0.1dBm
SUMIOPMAX Maximum total input optical
power
SUMIOPMIN Minimum total input optical power
SUMOOPCUR Current total output optical power
SUMOOPMA Maximum total output optical
X power
SUMOOPMIN Minimum total output optical
power
WCVCUR Current working current of the 0.1mA
pump laser
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 855
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
WCVMAX Maximum working current of the
pump laser
WCVMIN Minimum working current of the
pump laser
XCSTMPCUR Current ambient temperature for 0.1°C
the board
XCSTMPMAX Maximum ambient temperature for
the board
XCSTMPMIN Minimum ambient temperature for
the board
Table 5-23 VC-3 path bit error performance events
Abbreviation Details Unit
VC3BBE Lower order path block of Block
background error
VC3FEBBE Lower order path far end block of
background error
VC3ES Lower order path errored second 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
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 856
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-24 PCM performance events
Abbreviation Details Unit
CRC4_ERR CRC4 check error Block
DDN_CRC4_E DDN-side CRC4 check error
RR
SIGNAL_TOG Number of seconds with 0-to-1 or second
GLE_SEC 1-to-0 signal changes
CO64K_LCV_ Codirectional 64K line-side code Block
SDH violation
CO64K_LES_S Number of seconds with second
DH codirectional 64K line-side code
violations
CO64K_LSES_ Number of seconds with severe
SDH codirectional 64K line-side code
violations
R_VOICE_PE Maximum value of the peak -
AK_MAX receive audio
R_VOICE_PE Minimum value of the peak
AK_MIN receive audio
R_VOICE_PE Current value of the peak receive
AK_CUR audio
R_VOICE_TR Maximum value of the trough
OUGH_MAX receive audio
R_VOICE_TR Minimum value of the trough
OUGH_MIN receive audio
R_VOICE_TR Current value of the trough receive
OUGH_CUR audio
R_VOICE_AV Maximum value of the average
G_MAX receive audio
R_VOICE_AV Minimum value of the average
G_MIN receive audio
R_VOICE_AV Current value of the average
G_CUR receive audio
T_VOICE_PE Maximum value of the peak
AK_MAX transmit audio
T_VOICE_PE Minimum value of the peak
AK_MIN transmit audio
T_VOICE_PE Current value of the peak transmit
AK_CUR audio
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 857
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
T_VOICE_TR Maximum value of the trough
OUGH_MAX transmit audio
T_VOICE_TR Minimum value of the trough
OUGH_MIN transmit audio
T_VOICE_TR Current value of the trough
OUGH_CUR transmit audio
T_VOICE_AV Maximum value of the average
G_MAX transmit audio
T_VOICE_AV Minimum value of the average
G_MIN transmit audio
T_VOICE_AV Current value of the average
G_CUR transmit audio
HPS_PATH_C a CRC and sequence number error Block
RC_ERR occurs on the working or
protection channel of a hitless
protection group.
Table 5-25 IEEE 1588v2 Clock Performance Events
Abbreviation Details Unit
MAXPHASEO Maximum phase offset ns
FFSET
MINPHASEOF Minimum phase offset
FSET
AVGPHASEOF Average phase offset
FSET
MAXMEANPA Maximum path delay
THDELAY
MINMEANPAT Minimum path delay
HDELAY
AVGMEANPA Average path delay
THDELAY
Table 5-26 C37.94 Line-side Code Violations Performance Events
Abbreviation Details Unit
C3794_LCV_SDH Count of C37.94 line-side Block
code violations
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 858
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Details Unit
C3794_LES_SDH Error seconds of C37.94 second
line-side code violations
C3794_LSES_SDH Severely error seconds of second
C37.94 line-side code
violations
5.4 Performance Event Clearing
This section describes how to handle the performance events.
5.4.1 AUPJCHIGH
Description
The AUPJCHIGH event indicates the count of positive AU pointer justifications.
Attribute
Performance Event Performance Event Type
ID
0x2a SDH performance event
Impact on the System
A small pointer justification does not affect the services, whereas a large pointer justification
causes bit errors in the services. If a large pointer justification occurs, identify the causes and
rectify the fault immediately. These operations help to prevent alarms and to ensure signal
transmission quality.
Possible Causes
External causes:
l A fiber is incorrectly connected, resulting in a clock loop of the two NEs.
l If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 859
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The line board is faulty. As a result, the clock is of poor quality.
l The clock unit is faulty. As a result, the clock source is of poor quality, or the traced
clock source cannot be locked.
Related Alarms
Alarm Name Correlation
MSAD_CROSST Multiplex section adaptation performance threshold crossing alarm
R
RS_CROSSTR Regenerator section performance threshold crossing alarm
MS_CROSSTR Multiplex section performance threshold crossing alarm
Procedure
Step 1 For non-network-wide pointer justifications, check whether fibers are correctly connected.
Step 2 If the NEs trace the external clock, check the quality of the external clock.
Step 3 Verify that the configuration is correct.
NOTE
Check the configuration items, such as clock ID, SSM protocol, and clock tracing priority.
Step 4 Analyze pointer justification performance events, and locate the fault by changing the position
of the clock source and clock tracing direction. Replace the faulty line board or clock unit.
----End
Related Information
None.
5.4.2 AUPJCLOW
Description
The AUPJCLOW event indicates the count of negative AU pointer justifications.
Attribute
Performance Event Performance Event Type
ID
0x2b SDH performance event
Impact on the System
A small pointer justification does not affect the services, whereas a large pointer justification
causes bit errors in the services. If a large pointer justification occurs, identify the causes and
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 860
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
rectify the fault immediately. These operations help to prevent alarms and to ensure signal
transmission quality.
Possible Causes
External causes:
l A fiber is incorrectly connected, resulting in a clock loop of the two NEs.
l If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l The line board is faulty. As a result, the clock is of poor quality.
l The clock unit is faulty. As a result, the clock source is of poor quality, or the traced
clock source cannot be locked.
Relevant Alarms
Alarm Name Correlation
MSAD_CROSST Multiplex section adaptation performance threshold crossing alarm
R
RS_CROSSTR Regenerator section performance threshold crossing alarm
MS_CROSSTR Multiplex section performance threshold crossing alarm
Procedure
Step 1 See 5.4.1 AUPJCHIGH.
----End
Related Information
None.
5.4.3 AUPJCNEW
Description
The AUPJCNEW event indicates the count of new AU pointer justifications.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 861
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Attribute
Performance Event Performance Event Type
ID
0x2c SDH performance event
Impact on the System
A small pointer justification does not affect the services, whereas a large pointer justification
causes bit errors in the services. If a large pointer justification occurs, identify the causes and
rectify the fault immediately. These operations help to prevent alarms and to ensure signal
transmission quality.
Possible Causes
External causes:
l A fiber is incorrectly connected, resulting in a clock loop of the two NEs.
l If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l The line board is faulty. As a result, the clock is of poor quality.
l The clock unit is faulty. As a result, the clock source is of poor quality, or the traced
clock source cannot be locked.
Related Alarms
Alarm Name Correlation
MSAD_CROSST Multiplex section adaptation performance threshold crossing alarm
R
RS_CROSSTR Regenerator section performance threshold crossing alarm
MS_CROSSTR Multiplex section performance threshold crossing alarm
Procedure
Step 1 See 5.4.1 AUPJCHIGH.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 862
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Related Information
None.
5.4.4 AVGFREQDEV
Description
The AVGFREQDEV event indicates the average frequency deviation between the output
clock and the input reference source.
Attribute
Performance Event Performance Event Type
ID
0x3AF2 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
Determine the traced clock performance according to the frequency deviation between the
output clock and the input reference source.
Related Alarms
Alarm Name Relationship
SYN_BAD SYN_BAD is a synchronization source
deterioration alarm. This alarm is generated
when the frequency deviation of the
synchronization source traced by the device
exceeds the permitted range, which causes
the quality of the synchronization source to
deteriorate at the physical layer.
Procedure
Step 1 None
----End
Reference Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 863
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.5 AVGMEANPATHDELAY
Description
The AVGMEANPATHDELAY event indicates the average path delay between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AF8 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the path delay occurs between the master clock and the slave
clock.
Related Alarms
None
Procedure
Step 1 None
----End
Reference Information
None
5.4.6 AVGPHASEOFFSET
Description
The AVGPHASEOFFSET event indicates the average phase offset between the master clock
and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AF5 SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 864
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the phase offset occurs between the master clock and the slave
clock.
Related Alarms
Alarm Name Relationship
TIME_LOCK_FAIL TIME_LOCK_FAIL is a time lock failure
alarm. The time of the local NE is locked if
the local NE synchronizes the time with the
upstream NE. If the time of the local NE is
unlocked, this alarm is reported to alert users.
Procedure
Step 1 None
----End
Reference Information
None
5.4.7 AVGPOSITIVEDELAY
Description
The AVGPOSITIVEDELAY event indicates the average positive delay between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3B01 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 865
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Generation Principle and Possible Causes
This event is generated when the positive delay occurs between the master clock and the slave
clock.
Related Alarms
Alarm Name Relationship
TIME_LOCK_FAIL TIME_LOCK_FAIL is a time lock failure
alarm. The time of the local NE is locked if
the local NE synchronizes the time with the
upstream NE. If the time of the local NE is
unlocked, this alarm is reported to alert
users.
Procedure
Step 1 None
----End
Reference Information
None
5.4.8 BCV
Description
The BCV event indicates the pump laser back facet current. It includes:
l BCVMAX: stands for the maximum value during a period of time.
l BCVMIN: stands for the minimum value during a period of time.
l BCVCUR: stands for the current value.
Attribute
Performance Event Performance Event Type
ID
BCVMAX: 0x76 Equipment function
BCVMIN: 0x77
BCVCUR: 0x78
Impact on the System
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 866
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
Back facet current is current O/E converted from part of light reflected from the resonant
cavity of a laser. The back facet current reflects the laser output optical power value. If the
BCVCUR is 0, the laser is faulty. When this occurs, replace the board where this faulty laser
resides.
Related Alarms
None.
Procedure
Step 1 None.
----End
Related Information
None.
5.4.9 BDTEMPCUR
Description
The BDTEMPCUR event indicates the current board temperature.
Attribute
Performance Event Performance Event Type
ID
0x3A91 Equipment function
Impact on the System
High or low board temperature may cause faults such as deteriorating board working
performance and bit errors.
Possible Causes
When the ambient temperature is abnormal, or when the heat dissipation and ventilation
measures are inefficient, the BDTEMP event occurs.
Related Alarms
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 867
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 If the board temperature is within the specified range, do not take any actions.
Step 2 If the board temperature is higher or lower than the specified range, clear the generated alarm
according to specific handling procedures.
----End
Related Information
4.2.481 TEMP_ALARM
5.4.10 BDTEMPMAX
Description
The BDTEMPMAX indicates the maximum board temperature.
Attribute
Performance Event Performance Event Type
ID
0x3A8F Equipment function
Impact on the System
High or low board temperature may cause faults such as deteriorating board working
performance and bit errors.
Possible Causes
When the ambient temperature is abnormal, or when the heat dissipation and ventilation
measures are inefficient, the BDTEMP event occurs.
Related Alarms
None.
Related Information
4.2.481 TEMP_ALARM
5.4.11 BDTEMPMIN
Description
The BDTEMPMIN indicates the minimum board temperature.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 868
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Attribute
Performance Event Performance Event Type
ID
0x3A90 Equipment function
Impact on the System
High or low board temperature may cause faults such as deteriorating board working
performance and bit errors.
Possible Causes
When the ambient temperature is abnormal, or when the heat dissipation and ventilation
measures are inefficient, the BDTEMP event occurs.
Related Alarms
None.
Procedure
Step 1 If the board temperature is within the specified range, do not take any actions.
Step 2 If the board temperature is higher or lower than the specified range, clear the generated alarm
according to specific handling procedures.
----End
Related Information
4.2.481 TEMP_ALARM
5.4.12 CCV
Description
The CCV event indicates the pump laser cooling current. It includes:
l CCVMAX: stands for the maximum value during a period of time.
l CCVMIN: stands for the minimum value during a period of time.
l CCVCUR: stands for the current value.
Attribute
Performance Event Performance Event Type
ID
CCVMAX: 0x73 Equipment function
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 869
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Performance Event Type
ID
CCVMIN: 0x74
CCVCUR: 0x75
Impact on the System
None.
Possible Causes
An A/D converter is used to sample the voltage corresponding to the cooling current of each
laser, and convert the voltage into cooling current. This value shows the working status of the
cooling circuit in a laser.
Related Alarms
Alarm Name Correlation
4.2.406 PUMP_COOL_EXC This alarm is generated when the cooling current of
the laser exceeds the permitted range.
Procedure
Step 1 If the 4.2.406 PUMP_COOL_EXC alarm is generated, handle the alarm by referring to the
alarm handling procedure.
----End
Related Information
None.
5.4.13 C3794_LCV_SDH
Performance Event Meaning
The C3794_LCV_SDH performance event indicates the C37.94 port line-side code violation
count.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x3e72 SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 870
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
The C3794_LCV_SDH performance event indicates the C37.94 port line-side code violation
count.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types are selected.
l A board fails or its performance degrades.
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 C37.94 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.
5.4.14 C3794_LES_SDH
Performance Event Meaning
The C3794_LES_SDH performance event indicates the C37.94 port line-side code violation
errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 871
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x3e73 SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types are selected.
l A board fails or its performance degrades.
Relevant Alarms
None.
Procedure
Step 1 Refer to the C3794_LCV_SDH.
----End
Reference
None.
5.4.15 C3794_LSES_SDH
Performance Event Meaning
The C3794_LSES_SDH performance event indicates the C37.94 port line-side code violation
severely errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 872
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x3e74 SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types are selected.
l A board fails or its performance degrades.
Relevant Alarms
None
Procedure
Step 1 Refer to the C3794_LCV_SDH.
----End
Reference
None.
5.4.16 CURPOSITIVEPDV
Description
The CURPOSITIVEPDV event indicates the positive PDV value.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 873
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Attribute
Performance Event Performance Event Type
ID
0x3c39 Other performance events
Impact on the System
IEEE 1588 ACR performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
None
Related Alarms
Alarm Name Relationship
ACR_LOCK_FAIL Indicates a clock lock failure that occurs
when an NE works in IEEE 1588 ACR
mode.
Procedure
Step 1 None
----End
Reference Information
None
5.4.17 E1_LCV_SDH
Performance Event Meaning
The E1_LCV_SDH performance event indicates the E1 line side code violation count.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x0c SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 874
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
The E1_LCV_SDH performance event indicates the E1 line side code violation count.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types are selected.
l A board fails or its performance degrades.
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.
5.4.18 E1_LES_SDH
Performance Event Meaning
The E1_LES_SDH performance event indicates the E1 line side code violation errored
second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 875
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x0d SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
The E1_LES_SDH performance event indicates the E1 line side code violation errored
second.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types are selected.
l A board fails or its performance degrades.
Relevant Alarms
None.
Procedure
Step 1 Refer to the 5.4.17 E1_LCV_SDH.
----End
Reference
None.
5.4.19 E1_LLOSS_SDH
Performance Event Meaning
The E1_LLOSS_SDH performance event indicates a count of E1 line loss-of-signal seconds.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 876
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x0F SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
The E1_LLOSS_SDH is a performance event indicating a count of E1 line loss-of-signal
seconds. This performance event is reported if the count of E1 line loss-of-signal seconds
crosses the preset threshold.
External causes:
l The cable performance is degraded and the cable has extremely high attenuation.
l The cable connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types.
l Board failure or performance deterioration.
Related Alarms
4.2.473 T_ALOS
Procedure
Step 1 Refer to 5.4.17 E1_LCV_SDH.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 877
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.20 E1_LSES_SDH
Performance Event Meaning
The E1_LSES_SDH performance event indicates the E1 line side code violation severely
errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x0E SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected.
Possible Causes
The E1_LSES_SDH performance event indicates the E1 line side code violation severely
errored second.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
Equipment problems:
l Wrong service code types are selected.
l A board fails or its performance degrades.
Relevant Alarms
None.
Procedure
Step 1 Refer to the 5.4.17 E1_LCV_SDH.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 878
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Reference
None.
5.4.21 EDTMP
Description
The EDTMP is a performance event indicating the laser temperature. It contains the
EDTMPMAX, EDTMPMIN, and EDTMPCUR, which respectively indicates the maximum
value, minimum value, and current value during a period of time.
Attribute
Performance Event Performance Event Type
ID
EDTMPMAX: 0x82 Equipment function
EDTMPMIN: 0x83
EDTMPCUR: 0x84
Impact on System
None.
Generation Principle and Possible Causes
This performance event is detected by hardware detecting circuit and then the result is
calculated by the software for conversion. If the performance is not in the normal range, the
laser module might be faulty.
Related Alarms
Alarm Name Correlation
PUM_TEM_ALM Working temperature of the pump laser exceeds the
threshold. This alarm is generated when the pump laser
operating temperature of the optical amplifier unit exceeds
the threshold.
Procedure
Step 1 If any alarm occurs, use the method of the related alarm to clear it.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 879
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Related Information
None.
5.4.22 HPBBE
Description
The HPBBE event indicates the higher order path background block error.
Attribute
Performance Event Performance Event Type
ID
0x30 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately. These
operations help to prevent alarms and to ensure signal transmission quality. If bit errors
exceed the B3 error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be
generated.
Possible Causes
The HPBBE event indicates bit errors that are detected in a verification period excluding the
higher order path unavailable time and higher order path severely errored second.
External causes:
l The fiber performance deteriorates, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is incorrectly grounded.
l A severe interference source is present near the equipment.
l The ambient temperature is out of the specified temperature range for the equipment.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The clock synchronization performance is poor.
l The cross-connect unit and the line board fail to properly work together.
l The board becomes faulty, or the board performance deteriorates.
Related Alarms
Alarm Name Correlation
B3_EXC B3 errors threshold crossing
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 880
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
B3_SD Signal degrade (B3)
Procedure
Step 1 Eliminate external causes, such as incorrect grounding, high ambient temperature, or low or
high 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 may be faulty. Replace the system
control, cross-connect, and timing board.
Step 3 If only a line board reports bit errors, the local line board, the line board on the opposite NE,
or fibers are faulty. Perform loopbacks to locate the faulty board, and replace the faulty board
if any is found. If fibers are found faulty, replace the fibers.
----End
Related Information
None.
5.4.23 HPCSES
Performance Event Meaning
The HPCSES event indicates the higher-order path consecutive severely errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x37 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the
B3_EXC and B3_SD alarms will be generated.
Possible Causes
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:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 881
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l 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)
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 Multiplex section alarm indication
AU_AIS AU alarm indication
AU_LOP AU pointer loss
HP_UNEQ Higher-order path unequipped
HP_TIM Higher-order path trace identifier mismatch
Procedure
Step 1 See 5.4.24 HPES.
----End
Reference
None.
5.4.24 HPES
Performance Event Meaning
The HPES event indicates the higher-order path errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 882
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x31 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the
B3_EXC and B3_SD alarms will be generated.
Possible Causes
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:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l 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)
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 Multiplex section alarm indication
AU_AIS AU alarm indication
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 883
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
AU_LOP AU pointer loss
HP_UNEQ Higher-order path unequipped
HP_TIM Higher-order path trace identifier mismatch
Procedure
Step 1 If the R_LOS or R_LOF alarm occurs, a fiber cut, severe attenuation, received overload, or
faulty board may 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 securely
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 transmit unit of the line board at the opposite station is faulty. If any
fault exists, replace the line board at the opposite station.
3. Perform a fiber self-loop to check the line board at the local station. Reset or replace the
board to check whether the alarm is cleared.
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 may be that the receiving and transmitting of the VC-4 path services
mismatch. And this causes that AU-AIS occurs on the VC-4 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 system control, switching, and timing board.
4. Perform a fiber self-loop to check the line board at the local station. Check whether the
alarm is cleared by resetting or replacing boards.
Step 4 The AU_LOP alarm occurs.
1. Check whether service configurations are correct at the local and opposite stations. If
not, configure them correctly.
2. Perform a fiber self-loop to check the opposite station. If the alarm persists, replace the
corresponding system control, switching, and timing board, and line board to locate the
fault.
3. Replace the CXL board at the local station.
Step 5 If the HP_UNEQ alarm occurs, check the configuration to determine whether the C2 byte is
correctly configured. If not, modify the configuration and apply it again. If yes, the board is
faulty. In this case, replace the faulty board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 884
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
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 at the local station. If the
configuration is inconsistent, apply the configuration again 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 apply it again.
3. Perform loopbacks at both stations interconnected. Check the equipment at the local and
opposite stations. Locate the faulty side and replace the faulty line board, and system
control, switching, and timing board.
Step 7 See 5.4.22 HPBBE.
----End
Reference
None.
5.4.25 HPFEBBE
Performance Event Meaning
The HPFEBBE event indicates the higher-order path far end background block error.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x33 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will 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 high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 885
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
HP_REI Higher-order path remote error indication
Procedure
Step 1 See 5.4.22 HPBBE.
----End
Reference
None.
5.4.26 HPFECSES
Performance Event Meaning
The HPFECSES event indicates the higher-order path far end consecutive severely errored
second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x38 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 886
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
When a consecutive HPFESES sequence is detected, the HPFECSES event occurs. When
unavailable time comes or HPFESES is absent in one second, the HPFECSES sequence ends.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
HP_REI Higher-order path remote error indication
HP_RDI Remote defect indication in higher-order paths
Procedure
Step 1 See 5.4.27 HPFEES.
----End
Reference
None.
5.4.27 HPFEES
Performance Event Meaning
The HPFEES event indicates the higher-order path far end errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 887
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x34 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
The HPFEES 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 On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
HP_REI Higher-order path remote error indication
HP_RDI Remote defect indication in higher-order paths
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 888
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 See method of handling the 4.2.163 HP_RDI alarm.
Step 2 See method of handling the 5.4.25 HPFEBBE performance event.
----End
Reference
None.
5.4.28 HPFESES
Performance Event Meaning
The HPFESES event indicates the higher-order path far end severely errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x35 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
The HPFESES event occurs when one of the following requirements is met: 1. Not less than
30% bit errors are contained in the message returned in one second. 2. At least one severely
disturbed period (SDP) occurs. SDP occurs when the BER of all the continuous blocks in a
period of at least four consecutive blocks or 1 ms (select the shorter period) is lower than 10-2,
or when the HP_RDI alarm occurs.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 889
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
HP_REI Higher-order path remote error indication
HP_RDI Remote defect indication in higher-order paths
Procedure
Step 1 See 5.4.27 HPFEES.
----End
Reference
None.
5.4.29 HPFEUAS
Performance Event Meaning
The HPFEUAS event indicates the higher-order path far end unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x4C SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
The HPFEUAS event indicates the duration in which the unavailable time (UAT) state lasts.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 890
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
HP_REI Higher-order path remote error indication
HP_RDI Remote defect indication in higher-order paths
Procedure
Step 1 See 5.4.27 HPFEES.
----End
Reference
None.
5.4.30 HPSES
Performance Event Meaning
The HPSES event indicates the higher-order path severely errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 891
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x32 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the
B3_EXC and B3_SD alarms will be generated.
Possible Causes
The HPSES event occurs when one of the following requirements 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 The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l 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)
R_LOS The signal on the receiver line side is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 892
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
R_LOF The out-of-frame fault occurs on the receiver line side.
MS_AIS Multiplex section alarm indication
AU_AIS AU alarm indication
AU_LOP AU pointer loss
HP_UNEQ Higher-order path unequipped
HP_TIM Higher-order path trace identifier mismatch
Procedure
Step 1 See 5.4.24 HPES.
----End
Reference
None.
5.4.31 HPUAS
Performance Event Meaning
The HPUAS event indicates the higher-order path unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x36 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the
B3_EXC and B3_SD alarms will be generated.
Possible Causes
The HPUAS event indicates the duration in which the unavailable time (UAT) state lasts.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 893
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l 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)
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 Multiplex section alarm indication
AU_AIS AU alarm indication
AU_LOP AU pointer loss
HP_UNEQ Higher-order path unequipped
HP_TIM Higher-order path trace identifier mismatch
Procedure
Step 1 See 5.4.24 HPES, 4.2.26 B3_EXC, 4.2.29 B3_SD, 4.2.420 R_LOS, 4.2.419 R_LOF, 4.2.305
MS_AIS, 4.2.20 AU_AIS, 4.2.21 AU_LOP, 4.2.168 HP_UNEQ, or 4.2.167 HP_TIM.
----End
Reference
None.
5.4.32 HPS_PATH_CRC_ERR
Description
The HPS_PATH_CRC_ERR event indicates that a CRC and sequence number error occurs on
the working or protection channel of a hitless protection group.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 894
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Attribute
Performance Event Performance Event Type
ID
0x3e2f PDH performance event
Impact on the System
The working or protection link of the hitless protection group is faulty. As a result, services on
the link are unavailable.
Generation Principle and Possible Causes
Information contained in K4 and N2 bytes in the TU-12 frame structure is incorrect on the
working or protection link of the protection group.
The possible causes of this event are as follows:
l Cause 1: The link is faulty.
l Cause 2: The selectively received signals are not the signals sent by the source port in the
protection group.
l Cause 3: The pass-through path traverses DXM boards or other tributary boards, which
causes TU-12 overhead termination and regeneration.
l Cause 4: The pass-through network on the link is not a pure SDH network.
Related Alarms
Alarm Name Relationship
TU_LOP TU_LOP indicates the loss of the TU pointer.
TU_AIS TU_AIS is TU alarm indication.
BIP_SD BIP_SD indicates BIP signal degrade.
BIP_EXC BIP_EXC indicates excessive BIP bit errors.
Procedure
Step 1 Cause 1: The link is faulty.
1. Check whether the 4.2.492 TU_LOP, 4.2.489 TU_AIS, 4.2.43 BIP_SD, or 4.2.42
BIP_EXC alarm exists on the NE.
2. If the alarm exists, clear the alarm by following the handling procedure.
Step 2 Cause 2: The selectively received signals are not the signals sent by the source port in the
protection group.
1. According to the service flow, check whether any of the source ports involved in the
working or protection link is the working or protection source port in the hitless
protection group.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 895
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
The working link NE1-NE2-NE4 shown in Figure 5-1 is used as an example. According
to the service flow, start from NE4 (sink NE) to check whether the received protection
source signals are the signals sent by the protection source port on NE1.
– Open the NE Explorer of NE4, select the target board, choose Configuration >
Hitless Switching Protection Group, and click Query to view the working source
port and source timeslot in the hitless protection group.
– In the NE Explorer of NE4, select the NE, choose Configuration > SDH/PDH
Service Management, and click Query.
– Check whether the working source port and timeslot in the hitless protection group
of NE4 are the same as the source port and timeslot of the SDH service from line
board 1 on NE4 to the PF4E8 board.
– Check whether the fiber connection between line board 1 on NE4 and the port on
NE2 is correct.
– Check whether the fiber connection between the line board on NE2 and the line
board port on NE1 is correct.
– Check whether the source port and timeslot of the SDH service from line board 1 on
NE1 to the PF4E8 board are the same as the working or protection source port and
timeslot in the hitless protection group on the PF4E8 board.
– Check the network configurations and connections in the preceding sequence. If the
ports or timeslots are inconsistent, modify the configurations.
NOTE
Because Huawei's proprietary protocol is used for the interconnection between the local and peer
boards in the hitless protection group, PF4E8 boards must be used for the interconnection.
Figure 5-1 HPS_PATH_CRC_ERR performance detection
Service flow Reporting the
HPS_PATH_CRC_ERR performance
Lien board
Lien board 1
Lien board 1
Working
Source port in the VC-12 Sink port in the
source
protection group
PF4E8
VC-12 protection group
PF4E8
NE2
Lien board 2
Lien board 2
VC-12
Lien board
Protection
VC-12
source
NE1 NE3 NE4
Working link
Protection link
2. If the selectively received signals on an NE are inconsistent with the signals sent by the
source port, modify the configurations.
Step 3 Cause 3: The pass-through path traverses DXM boards or other tributary boards, which causes
TU-12 overhead termination and regeneration.
1. Check the protection group link that reports the event to check for DXM boards or other
tributary boards.
2. If any, modify the link configurations.
Step 4 Cause 4: The pass-through network on the link is not a pure SDH network.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 896
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
1. Check whether the working and protection links of the protection group traverse only an
SDH network.
2. If not, modify service configurations.
----End
Reference Information
None
5.4.33 LPBBE
Performance Event Meaning
The LPBBE event indicates the lower-order path block of background error.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x90 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
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
The LPBBE event 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 at the VC-12 level,
the first two bits of the V5 byte are verified. When the service is at the VC-3 level, the B3
byte is verified.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 897
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line unit or the cross-connect unit and the tributary unit
poorly match.
l The tributary unit is faulty.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
BIP_EXC Indicates that the BIP bit errors cross the threshold when the service
level is VC-12.
BIP_SD Indicates that the BIP signal degraded when the service level is
VC-12.
B3_EXC Indicates BIP excessive errors when the service level is VC-3.
B3_SD Indicates that the higher-order path (B3) signal degraded when the
service level is VC-3.
Procedure
Step 1 Eliminate external causes, such as poor grounding, high operating temperature, low or high
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 may be faulty. In this case,
replace the CXL board.
Step 3 If only a line board reports that bit errors exist, the local line board may 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 rectify the fault.
----End
Reference
None.
5.4.34 LPCSES
Performance Event Meaning
The LPCSES event indicates the lower-order path consecutive severe bit error second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 898
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x97 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
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
When a consecutive LPSES sequence is detected, the LPCSES event occurs. When
unavailable time comes or LPSES is absent in one second, the LPCSES sequence ends. When
the service is at the VC-12 level, the first two bits of the V5 byte are verified. When the
service is at the VC-3 level, the B3 byte is verified.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line unit or the cross-connect unit and the tributary unit
poorly match.
l The tributary unit is faulty.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
BIP_EXC Indicates that the BIP bit errors cross the threshold when the service
level is VC-12.
BIP_SD Indicates that the BIP signal degraded when the service level is
VC-12.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 899
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
B3_EXC Indicates BIP excessive errors when the service level is VC-3.
B3_SD Indicates that the higher-order path (B3) signal degraded when the
service level is VC-3.
LP_UNEQ Indicates that the lower-order path is not equipped.
LP_TIM Indicates that the lower-order path tracking identifiers mismatch.
TU_AIS Indicates the TU alarm indication signal.
TU_LOP Indicates the TU loss of pointer.
Procedure
Step 1 See 5.4.35 LPES.
----End
Reference
None.
5.4.35 LPES
Performance Event Meaning
The LPES event indicates the lower-order path errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x91 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
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
The LPES 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 at the VC-12 level, the first two bits of
the V5 byte are verified. When the service is at the VC-3 level, the B3 byte is verified.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 900
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line unit or the cross-connect unit and the tributary unit
poorly match.
l The tributary unit is faulty.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
BIP_EXC Indicates that the BIP bit errors cross the threshold when the service
level is VC-12.
BIP_SD Indicates that the BIP signal degraded when the service level is
VC-12.
B3_EXC Indicates BIP excessive errors when the service level is VC-3.
B3_SD Indicates that the higher-order path (B3) signal degraded when the
service level is VC-3.
LP_UNEQ Indicates that the lower-order path is not equipped.
LP_TIM Indicates that the lower-order path tracking identifiers mismatch.
TU_AIS Indicates the TU alarm indication signal.
TU_LOP Indicates the TU loss of pointer.
Procedure
Step 1 When the LP_UNEQ alarm occurs:
1. Check whether the services at the opposite and local stations are correctly configured. If
not, modify the service configurations and apply them again.
2. Check whether the attributes of the tributary boards at local and opposite stations are
correctly configured. If not, modify the attribute configurations and apply them again.
3. Check whether the opposite or local station is faulty by looping back the fiber.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 901
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
4. If the opposite station is faulty, replace the relevant tributary board, line board, and
system control, switching, and timing 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 boards 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 the
configuration and apply it again.
2. Check whether the services at the opposite and local stations are correctly configured. If
not, modify the service configurations and apply them again.
3. Check whether the opposite or local station is faulty by looping back the fiber.
4. If the opposite station is faulty, replace the relevant tributary board, line board, and
system control, switching, and timing board in turn.
5. If the local station is faulty, replace the tributary unit and cross-connect unit in turn.
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 service
configurations and apply them again.
4. Check whether the opposite or local station is faulty by looping back the fiber.
5. If the opposite station is faulty, replace the relevant tributary board, line board, and
system control, switching, and timing board in turn.
6. If the local station is faulty, replace the tributary unit and cross-connect unit in turn.
Step 4 When the TU_LOP alarm occurs:
1. Check whether the cross-connect unit or the tributary unit is correctly configured. If not,
modify the configuration and apply it again.
2. Check whether the opposite or local station is faulty by looping back the fiber.
3. If the opposite station is faulty, replace the relevant tributary board, line board, and
system control, switching, and timing board in turn.
4. If the local station is faulty, replace the tributary unit and cross-connect unit in turn.
Step 5 See 5.4.33 LPBBE.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 902
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.36 LPFEBBE
Performance Event Meaning
The LPFEBBE event indicates the lower-order path far end block of background error.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x93 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
The LPFEBBE event 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 at
the VC-12 level, the third bit of the V5 byte is verified. When the service is at the VC-3 level,
the G1 byte is verified.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
l The tributary board of the opposite equipment is faulty.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 903
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Relevant Alarms
Alarm Name Correlation
LP_REI Bit errors occur on the lower-order path at the remote end.
Procedure
Step 1 See 5.4.33 LPBBE.
----End
Reference
None.
5.4.37 LPFECSES
Performance Event Meaning
The LPFECSES event indicates the lower-order path far end consecutive severely errored
second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x98 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
When a consecutive LPFESES sequence is detected, the LPFECSES event occurs. When
unavailable time comes or LPFESES is absent in one second, the LPFECSES sequence ends.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 904
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
l The tributary board of the opposite equipment is faulty.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
LP_REI Bit errors occur on the lower-order path at the remote end.
LP_RDI Lower-order path remote defect indication
Procedure
Step 1 See 5.4.38 LPFEES.
----End
Reference
None.
5.4.38 LPFEES
Performance Event Meaning
The LPFEES event indicates the lower-order path far end errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x94 SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 905
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
The LPFEES 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 at the VC-12 level, the third bit of the V5
byte is verified. When the service is at the VC-3 level, the G1 byte is verified.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
l The tributary board of the opposite equipment is faulty.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
LP_REI Bit errors occur on the lower-order path at the remote end.
LP_RDI Lower-order path remote defect indication
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 then the LP_RDI alarm
should be cleared.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 906
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
2. If no alarm is reported at the opposite station or if the LP_RDI alarm persists after the
corresponding alarms are cleared, the board is faulty. Replace it.
Step 2 See 5.4.33 LPBBE.
----End
Reference
None.
5.4.39 LPFESES
Performance Event Meaning
The LPFESES event indicates the lower-order path far end severely errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x95 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
The LPFESES event occurs when one of the following requirements is met: 1. Not less than
30% bit errors are contained in the message returned in one second. 2. At least one severely
disturbed period (SDP) occurs. SDP occurs when the BER of all the continuous blocks in a
period of at least four consecutive blocks or 1 ms (select the shorter period) is lower than 10-2,
or when the LP_RDI alarm occurs. When the service is at the VC-12 level, the third bit of the
V5 byte is verified. When the service is at the VC-3 level, the G1 byte is verified.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 907
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
l The tributary board of the opposite equipment is faulty.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
LP_REI Bit errors occur on the lower-order path at the remote end.
LP_RDI Lower-order path remote defect indication
Procedure
Step 1 See 5.4.38 LPFEES.
----End
Reference
None.
5.4.40 LPFEUAS
Performance Event Meaning
The LPFEUAS event indicates the lower-order far end unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x8e SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 908
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
The LPFEUAS event indicates the duration in which the unavailable time (UAT) state lasts.
External causes:
l On the opposite equipment, the fiber performance is degraded, and the fiber has high
attenuation.
l The fiber connector is dirty or incorrect at the opposite station.
l The opposite equipment is poorly grounded.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board, or the cross-connect and the tributary board
poorly match at the opposite station.
l The tributary board of the opposite equipment is faulty.
l The fan of the opposite equipment becomes faulty.
l The board of the opposite equipment becomes faulty or the performance of the board is
degraded.
Relevant Alarms
Alarm Name Correlation
LP_REI Bit errors occur on the lower-order path at the remote end.
LP_RDI Lower-order path remote defect indication
Procedure
Step 1 See 5.4.38 LPFEES.
----End
Reference
RSUAS
5.4.41 LPSES
Performance Event Meaning
The LPSES event indicates the lower-order path severely errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 909
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x92 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will 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 event occurs when one of the following requirements 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 consecutive
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 at the VC-12 level, the
first two bits of the V5 byte are verified. When the service is at the VC-3 level, the B3 byte is
verified.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l A severe interference source is present near the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line unit or the cross-connect unit and the tributary unit
poorly match.
l The tributary board is faulty.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
BIP_EXC Indicates that the BIP bit errors cross the threshold when the service
level is VC-12.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 910
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
BIP_SD Indicates that the BIP signal degraded when the service level is
VC-12.
B3_EXC Indicates BIP excessive errors when the service level is VC-3.
B3_SD Indicates that the higher-order path (B3) signal degraded when the
service level is VC-3.
LP_UNEQ Indicates that the lower-order path is not equipped.
LP_TIM Indicates that the lower-order path tracking identifiers mismatch.
TU_AIS Indicates the TU alarm indication signal.
TU_LOP Indicates the TU loss of pointer.
Procedure
Step 1 See 5.4.35 LPES.
----End
Reference
None.
5.4.42 LPUAS
Performance Event Meaning
The LPUAS event indicates the lower-order path unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x96 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
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
The LPUAS event indicates the duration in which the unavailable time (UAT) state lasts.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 911
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit does not match with the line unit or the tributary unit correctly.
l The tributary board is faulty.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
BIP_EXC Indicates that the BIP bit errors cross the threshold when the service
level is VC-12.
BIP_SD Indicates that the BIP signal degraded when the service level is
VC-12.
B3_EXC Indicates BIP excessive errors when the service level is VC-3.
B3_SD Indicates that the higher-order path (B3) signal degraded when the
service level is VC-3.
LP_UNEQ Indicates that the lower-order path is not equipped.
LP_TIM Indicates the lower-order path tracking identifiers mismatch.
TU_AIS Indicates the TU alarm indication signal.
TU_LOP Indicates the TU loss of pointer.
Procedure
Step 1 See 4.2.42 BIP_EXC, 4.2.43 BIP_SD, 4.2.26 B3_EXC, 4.2.29 B3_SD, 4.2.230 LP_UNEQ,
4.2.227 LP_TIM, 4.2.489 TU_AIS, or 4.2.492 TU_LOP.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 912
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.43 MAXFREQDEV
Description
The MAXFREQDEV event indicates the maximum frequency deviation between the output
clock and the input reference source.
Attribute
Performance Event Performance Event Type
ID
0x3AF0 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
Determine the traced clock performance according to the frequency deviation between the
output clock and the input reference source.
Related Alarms
Alarm Name Relationship
SYN_BAD SYN_BAD is a synchronization source
deterioration alarm. This alarm is generated
when the frequency deviation of the
synchronization source traced by the device
exceeds the permitted range, which causes
the quality of the synchronization source to
deteriorate at the physical layer.
Procedure
Step 1 None
----End
Reference Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 913
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.44 MAXMEANPATHDELAY
Description
The MAXMEANPATHDELAY event indicates the maximum path delay between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AF6 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the path delay occurs between the master clock and the slave
clock.
Related Alarms
None
Procedure
Step 1 None
----End
Reference Information
None
5.4.45 MAXPHASEOFFSET
Description
The MAXPHASEOFFSET event indicates the maximum phase offset between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AF3 SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 914
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the phase offset occurs between the master clock and the slave
clock.
Related Alarms
Alarm Name Relationship
TIME_LOCK_FAIL TIME_LOCK_FAIL is a time lock failure
alarm. The time of the local NE is locked if
the local NE synchronizes the time with the
upstream NE. If the time of the local NE is
unlocked, this alarm is reported to alert users.
Procedure
Step 1 None
----End
Reference Information
None
5.4.46 MAXPOSITIVEDELAY
Description
The MAXPOSITIVEDELAY event indicates the maximum positive delay between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AFF SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 915
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Generation Principle and Possible Causes
This event is generated when the positive delay occurs between the master clock and the slave
clock.
Related Alarms
Alarm Name Relationship
TIME_LOCK_FAIL TIME_LOCK_FAIL is a time lock failure
alarm. The time of the local NE is locked if
the local NE synchronizes the time with the
upstream NE. If the time of the local NE is
unlocked, this alarm is reported to alert
users.
Procedure
Step 1 None
----End
Reference Information
None
5.4.47 MINFREQDEV
Description
The MINFREQDEV event indicates the minimum frequency deviation between the output
clock and the input reference source.
Attribute
Performance Event Performance Event Type
ID
0x3AF1 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
Determine the traced clock performance according to the frequency deviation between the
output clock and the input reference source.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 916
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Related Alarms
Alarm Name Relationship
SYN_BAD SYN_BAD is a synchronization source
deterioration alarm. This alarm is generated
when the frequency deviation of the
synchronization source traced by the device
exceeds the permitted range, which causes
the quality of the synchronization source to
deteriorate at the physical layer.
Procedure
Step 1 None
----End
Reference Information
None
5.4.48 MINMEANPATHDELAY
Description
The MINMEANPATHDELAY event indicates the minimum path delay between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AF7 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the path delay occurs between the master clock and the slave
clock.
Related Alarms
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 917
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 None
----End
Reference Information
None
5.4.49 MINPHASEOFFSET
Description
The MINPHASEOFFSET event indicates the minimum phase offset between the master clock
and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3AF4 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the phase offset occurs between the master clock and the slave
clock.
Related Alarms
Alarm Name Relationship
TIME_LOCK_FAIL TIME_LOCK_FAIL is a time lock failure
alarm. The time of the local NE is locked if
the local NE synchronizes the time with the
upstream NE. If the time of the local NE is
unlocked, this alarm is reported to alert users.
Procedure
Step 1 None
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 918
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Reference Information
None
5.4.50 MINPOSITIVEDELAY
Description
The MINPOSITIVEDELAY event indicates the minimum positive delay between the master
clock and the slave clock.
Attribute
Performance Event Performance Event Type
ID
0x3B00 SDH performance event
Impact on the System
IEEE 1588v2 performance is monitored. There is no impact on services.
Generation Principle and Possible Causes
This event is generated when the positive delay occurs between the master clock and the slave
clock.
Related Alarms
Alarm Name Relationship
TIME_LOCK_FAIL TIME_LOCK_FAIL is a time lock failure
alarm. The time of the local NE is locked if
the local NE synchronizes the time with the
upstream NE. If the time of the local NE is
unlocked, this alarm is reported to alert
users.
Procedure
Step 1 None
----End
Reference Information
None
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 919
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.51 MSBBE
Performance Event Meaning
The MSBBE event indicates the background block error of the multiplex section (MS).
Performance Event Attributes
Performance Event Performance Event Type
ID
0x10 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. 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
The MSBBE event is an errored block not occurring as part of multiplex section unavailable
time and multiplex section severely errored second.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B2_EXC B2 bit errors crossing the threshold
B2_SD Signals degraded (B2)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 920
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 Eliminate external causes, such as poor grounding, high operating temperature, low or high
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 may be faulty. In this case,
replace the CXL board.
Step 3 If only a line board reports that bit errors exist, the local line board may be 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.
5.4.52 MSCSES
Performance Event Meaning
The MSCSES event indicates the consecutive severely errored seconds of the MS.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x17 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. 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
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 The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 921
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B2_EXC B2 bit errors crossing the threshold
B2_SD Signals degraded (B2)
Procedure
Step 1 See 5.4.53 MSES.
----End
Reference
None.
5.4.53 MSES
Performance Event Meaning
The MSES event indicates the multiplex section errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x11 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B2 bit error threshold-crossing threshold and degrade threshold, the
B2_EXC and B2_SD alarms will be generated.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 922
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
The MSES event occurs when one or multiple bit error blocks are detected in one second or
when the R_LOS, R_LOF, or MS_AIS alarm is detected.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B2_EXC Indicates that B2 bit errors crossing the threshold.
B2_SD Indicates signals degraded (B2).
R_LOS Indicates that the signal on the receiver line side is lost.
R_LOF Indicates that the out-of-frame fault occurs on the receiver line side.
MS_AIS Indicates multiplex section alarm indication.
Procedure
Step 1 If the R_LOS or R_LOF alarm occurs, a fiber cut, severe attenuation, received overload, or
faulty board may exist.
1. Add an attenuator if the received optical power is overloaded.
2. Check the fiber and optical connector. Clean the fiber connector.
3. Replace the board.
Step 2 If 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 yes, cancel the setting.
2. Check whether the transmit unit of the line board at 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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 923
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
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.
Step 3 See 5.4.51 MSBBE, 4.2.24 B2_EXC, or 4.2.25 B2_SD.
----End
Reference
None.
5.4.54 MSFEBBE
Performance Event Meaning
The MSFEBBE event indicates the multiplex section far end background block error.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x13 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
The MSFEBBE event 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.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 924
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
MS_REI Multiplex section remote error indication
Procedure
Step 1 See 5.4.51 MSBBE.
----End
Reference
None.
5.4.55 MSFECSES
Performance Event Meaning
The MSFECSES event indicates the multiplex section far end consecutive severely errored
second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x18 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
When a consecutive MSFESES sequence is detected, the MSFECSES event occurs. When
unavailable time comes or MSFESES is absent in one second, the MSFECSES sequence
ends.
External causes:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 925
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
MS_REI Multiplex section remote error indication
MS_RDI A defect occurs at the remote end of the multiplex section.
Procedure
Step 1 See 5.4.56 MSFEES.
----End
Reference
None.
5.4.56 MSFEES
Performance Event Meaning
The MSFEES event indicates the far end errored seconds of the MS.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x14 SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 926
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality 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 The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
MS_REI Multiplex section remote error indication
MS_RDI A defect occurs at the remote end of the multiplex section.
Procedure
Step 1 See 4.2.308 MS_REI or 4.2.307 MS_RDI.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 927
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.57 MSFESES
Performance Event Meaning
The MSFESES event indicates the multiplex section far end severely errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x15 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
The MSFESES event occurs when one of the following requirements is met: 1. Not less than
30% bit errors are contained in the message returned in one second. 2. At least one severely
disturbed period (SDP) occurs. SDP occurs when the BER of all the continuous blocks in a
period of at least four consecutive blocks or 1 ms (select the shorter period) is lower than 10-2,
or when the MS_RDI alarm occurs.
External causes:
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 928
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Relevant Alarms
Alarm Name Correlation
MS_REI Multiplex section remote error indication
MS_RDI A defect occurs at the remote end of the multiplex section.
Procedure
Step 1 See 5.4.56 MSFEES.
----End
Reference
None.
5.4.58 MSFEUAS
Performance Event Meaning
The MSFEUAS event indicates the multiplex section far end unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x21 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE but no related alarms are reported on the
remote NE, the system will not be affected. However, it is required to identify the causes and
rectify the fault immediately. Otherwise, alarms will be generated and the signal transmission
quality will be affected.
Possible Causes
The MSUAS event indicates the duration in which the unavailable time (UAT) state lasts.
External causes:
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 929
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
MS_REI Multiplex section remote error indication
MS_RDI A defect occurs at the remote end of the multiplex section.
Procedure
Step 1 See 5.4.56 MSFEES.
----End
Reference
None.
5.4.59 MSSES
Performance Event Meaning
The MSSES event indicates that severely errored seconds occur in the MS.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x12 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B2 bit error threshold-crossing threshold and degrade threshold, the
B2_EXC and B2_SD alarms will be generated.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 930
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
The MSSES event occurs when one of the following requirements 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).
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B2_EXC B2 bit errors crossing the threshold
B2_SD Signals degraded (B2)
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 Multiplex section alarm indication
Procedure
Step 1 See 5.4.53 MSES, 4.2.24 B2_EXC, 4.2.25 B2_SD, 4.2.420 R_LOS, 4.2.419 R_LOF, or
4.2.305 MS_AIS.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 931
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.60 MSUAS
Performance Event Meaning
The MSUAS event indicates the unavailable seconds of the MS.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x16 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. 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
The MSUAS event indicates the duration in which the unavailable time (UAT) state lasts.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B2_EXC B2 bit errors crossing the threshold
B2_SD Signals degraded (B2)
R_LOS The signal on the receiver line side is lost.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 932
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
R_LOF The out-of-frame fault occurs on the receiver line side.
MS_AIS Multiplex section alarm indication
Procedure
Step 1 See 5.4.53 MSES, 4.2.24 B2_EXC, 4.2.25 B2_SD, 4.2.420 R_LOS, 4.2.419 R_LOF, or
4.2.305 MS_AIS.
----End
Reference
RSUAS
5.4.61 OSPITMPCUR
Performance Event Meaning
The OSPITMPCUR event indicates the current value of the laser temperature.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x6e SDH performance event
Impact on the System
This performance event does not affect the system. When the laser temperature is high or low,
however, the laser does not work normally and therefore services may be interrupted.
Possible Causes
Count the current value of the laser temperature. This value shows the physical performance,
which exists after the laser is online.
Relevant Alarms
None.
Procedure
Step 1 Determine whether the laser temperature is within the allowed range. If yes, no action is
required. If not, go to the next step.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 933
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Step 2 Replace the optical module.
----End
Reference
None.
5.4.62 OSPITMPMAX
Performance Event Meaning
The OSPITMPMAX event indicates the maximum value of the laser temperature.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x6c SDH performance event
Impact on the System
This performance event does not affect the system. When the laser temperature is high or low,
however, the laser does not work normally and therefore services may be interrupted.
Possible Causes
Count the maximum value of the temperature of the laser in the current period. This value
shows the physical performance, which exists after the laser is online.
Relevant Alarms
None.
Procedure
Step 1 Determine whether the laser temperature is within the allowed range. If yes, no action is
required. If not, go to the next step.
Step 2 Replace the optical module.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 934
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.63 OSPITMPMIN
Performance Event Meaning
The OSPITMPMIN event indicates the minimum value of the laser temperature.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x6d SDH performance event
Impact on the System
This performance event does not affect the system. When the laser temperature is high or low,
however, the laser does not work normally and therefore services may be interrupted.
Possible Causes
Count the minimum value of the temperature of the laser in the current period. This value
shows the physical performance, which exists after the laser is online.
Relevant Alarms
None.
Procedure
Step 1 Determine whether the laser temperature is within the allowed range. If yes, no action is
required. If not, go to the next step.
Step 2 Replace the optical module.
----End
Reference
None.
5.4.64 RPLCUR
Performance Event Meaning
The RPLCUR event indicates the current value of the optical power received by the laser.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 935
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x6b SDH performance event
Impact on the System
This performance event does not affect the system. When the input optical power is high, the
laser is damaged; when the input optical power is 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 value shows the
physical performance, which exists after the laser is online.
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. Perform the following operations
according to the values of the received optical power.
1. If the optical power is high, add a signal attenuator to the transmission line.
2. If the optical power is low, minimize the signal attenuation during transmission or
increase the transmitted optical power at the opposite station.
3. If the optical power is normal, replace the board.
----End
Reference
None.
5.4.65 RPLMAX
Performance Event Meaning
The RPLMAX event indicates the maximum value of the optical power received by the laser.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 936
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x69 SDH performance event
Possible Causes
Count the maximum value of the optical power received by the laser in the current period.
This value shows the physical performance, which exists after the laser is online.
Relevant Alarms
Alarm Name Correlation
IN_PWR_ABN The received optical power is abnormal.
Procedure
Step 1 See 4.2.177 IN_PWR_ABN.
----End
Reference
None.
5.4.66 RPLMIN
Performance Event Meaning
The RPLMIN event indicates the minimum value of the optical power received by the laser.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x6a SDH performance event
Impact on the System
This performance event does not affect the system. When the input optical power is high, the
laser is damaged; when the input optical power is low, the laser cannot detect signals.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 937
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
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 minimum value of the optical power received by the laser in the current period.
This value shows the physical performance, which exists after the laser is online.
Relevant Alarms
Alarm Name Correlation
IN_PWR_ABN The received optical power is abnormal.
Procedure
Step 1 See 4.2.177 IN_PWR_ABN.
----End
Reference
None.
5.4.67 RSBBE
Performance Event Meaning
The RSBBE event indicates the background block error of the regenerator section (RS).
Performance Event Attributes
Performance Event Performance Event Type
ID
0x01 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B1 bit error threshold-crossing threshold and degrade threshold, the
B1_EXC and B1_SD alarms will be generated.
Possible Causes
The RSBBE event is an errored block excluding bit errors during the regenerator section
unavailable time and regenerator section severely errored second.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 938
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B1_EXC B1 bit errors crossing the threshold
B1_SD Signals degraded (B1)
Procedure
Step 1 Eliminate external causes, such as poor grounding, high operating temperature, low or high
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 may be faulty. In this case,
replace the CXL board.
Step 3 If only a line board reports that bit errors exist, the local line board may be faulty or that the
opposite NE or fibers are faulty. Perform a loopback to locate the faulty board and replace it.
----End
Reference
None.
5.4.68 RSCSES
Performance Event Meaning
The RSCSES event indicates the regenerator section consecutive severely errored seconds.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 939
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x07 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B1 bit error threshold-crossing threshold and degrade threshold, the
B1_EXC and B1_SD alarms will be generated.
Possible Causes
When a consecutive RSSES sequence is detected, the RSCSES event occurs. When
unavailable time comes or RSSES is absent in one second, the RSCSES sequence ends.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B1_EXC B1 bit errors crossing the threshold
B1_SD Signals degraded (B1)
R_LOS The signal on the receiver line side is lost.
R_LOF The out-of-frame fault occurs on the receiver line side.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 940
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 See 5.4.69 RSES.
----End
Reference
None.
5.4.69 RSES
Performance Event Meaning
The RSES event indicates the regenerator section errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x02 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B1 bit error threshold-crossing threshold and degrade threshold, the
B1_EXC and B1_SD alarms will be generated.
Possible Causes
The RSES event occurs when one or multiple bit error blocks are detected within one second
or when the R_LOS or R_LOF alarm is detected in a second.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 941
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B1_EXC B1 bit errors crossing the threshold
B1_SD Signals degraded (B1)
R_LOS The signal on the receiver line side is lost.
R_LOF The out-of-frame fault occurs on the receiver line side.
Procedure
Step 1 If the R_LOS or R_LOF alarm occurs, a fiber cut, severe attenuation, received overload, or
faulty board may exist.
1. Add an attenuator if the received optical power is overloaded.
2. Check the fiber and optical connector. Clean the fiber connector.
3. Replace the board.
Step 2 See 5.4.67 RSBBE.
----End
Reference
None.
5.4.70 RSOFS
Performance Event Meaning
The RSOFS event indicates the regenerator section out-of-frame second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x05 SDH performance event
Impact on the System
This performance event indicates that the frame headers cannot be identified in five or more
consecutive frames in the received signals of the line board. The board changes to the out-of-
frame state. As a result, the services are unavailable.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 942
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
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. This second is called the regenerator section out-
of-frame second.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
R_OOF Receive out of frame
R_LOF Receive loss of frame
RS_CROSSTR Regenerator section performance parameter override alarm
Procedure
Step 1 See 5.4.71 RSOOF.
----End
Reference
None.
5.4.71 RSOOF
Performance Event Meaning
The RSOOF event indicates the regenerator section out-of-frame count.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 943
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x04 SDH performance event
Impact on the System
This performance event indicates that the frame headers cannot be identified in five or more
consecutive frames in the received signals of the line board. The board changes to 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 changes to the out-
of-frame counting state.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
R_OOF Receive out of frame
R_LOF Receive loss of frame
RS_CROSSTR Regenerator section performance parameter override alarm
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 944
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
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.
5.4.72 RSSES
Performance Event Meaning
The RSSES event indicates the severely errored seconds of the RS.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x03 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B1 bit error threshold-crossing threshold and degrade threshold, the
B1_EXC and B1_SD alarms will be generated.
Possible Causes
The RSSES event occurs when one of the following requirements 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
consecutive blocks or 1 ms (select the shorter period) is lower than 10-2, or when the LOF
alarm occurs.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 945
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B1_EXC B1 bit errors crossing the threshold
B1_SD Signals degraded (B1)
R_LOF The out-of-frame fault occurs on the receiver line side.
Procedure
Step 1 See 5.4.69 RSES.
----End
Reference
None.
5.4.73 RSUAS
Performance Event Meaning
The RSUAS event indicates regenerator section unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x06 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B1 bit error threshold-crossing threshold and degrade threshold, the
B1_EXC and B1_SD alarms will be generated.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 946
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
The RSUAS event indicates the duration in which the unavailable time (UAT) state lasts.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B1_EXC B1 bit errors crossing the threshold
B1_SD Signals degraded (B1)
R_LOS The signal on the receiver line side is lost.
R_LOF The out-of-frame fault occurs on the receiver line side.
Procedure
Step 1 See 5.4.69 RSES, 4.2.22 B1_EXC, 4.2.23 B1_SD, 4.2.420 R_LOS, or 4.2.419 R_LOF.
----End
Reference
UAT starts when the NE at the receive end detects ten consecutive SES events. These ten
seconds are contained in the UAT. When the NE at the receive end detects ten non-RSSES
events, a new available time (AT) starts. In such a situation, these ten seconds are contained in
the AT.
5.4.74 SUMIOP
Description
The SUMIOP indicates the total input optical power. This performance event includes three
items: SUMIOPMAX, SUMIOPMIN, and SUMIOPCUR. The SUMIOPMAX item indicates
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 947
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
the maximum value of the total input optical power. The SUMIOPMIN item indicates the
minimum value of the total input optical power. The SUMIOPCUR item indicates the current
value of the total input optical power.
Attribute
Performance Event ID Performance Event Type
SUMIOPMAX: 0xD2 Equipment function
SUMIOPMIN: 0xD3
SUMIOPCUR: 0xD4
Impact on System
l If the total input optical power is too high, the optical modules on the boards of both the
local end and the downstream station may be damaged. Consequently, the services may
encounter bit errors or even be interrupted.
l If the total input optical power is too low, the single-channel optical signals output from
the board may be lost. Consequently, the services may encounter certain bit errors or
even be interrupted.
Generation Principle and Possible Causes
The total input optical power is detected by the hardware circuits. After the board software
reads the input power value that is detected by the hardware circuits, the AD module
computes the actual input power value that is reported.
Related Alarms
Alarm Name Correlation
IN_PWR_HIGH The input optical power is too high. The value of the detected
input optical power is more than the upper-threshold and the
board reports the alarm in the following cases:
l The value of the input optical power is more than the upper-
threshold.
l The optical power fails to be detected correctly.
l The optical module is faulty.
SUM_INPWR_HI The total input optical power is too high. When the total value
of the detected total input optical power is more than the upper-
threshold, the board reports the alarm.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 948
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
IN_PWR_LOW The input optical power is too low. The value of the detected
input optical power is less than the lower-threshold and the
board reports the alarm in the following cases:
l The value of the input optical power is less than the lower-
threshold.
l The optical power fails to be detected correctly.
l The optical module is faulty.
SUM_INPWR_LOW The total input optical power is too low. When the total value of
the detected input optical power is less than the lower-threshold,
the board reports the alarm.
Procedure
Step 1 If the current performance value is 2 dB or more than the history performance value but no
alarm is reported, and if the power change is not caused by normal operations (such as
capacity expansion or upgrading), see the method of handling the IN_PWR_HIGH alarm to
handle the performance event.
Step 2 If the current performance value is 2 dB or more less than the history performance value but
no alarm is reported, and if the power change is not caused by normal operations (such as
capacity expansion or upgrading), see the method of handling the IN_PWR_LOW alarm to
handle the performance event.
----End
Related Information
None.
5.4.75 SUMOOP
Description
The SUMOOP indicates the total output optical power. This performance event includes three
items: SUMOOPMAX, SUMOOPMIN, and SUMOOPCUR. The SUMOOPMAX item
indicates the maximum value of the total output optical power. The SUMOOPMIN item
indicates the minimum value of the total output optical power. The SUMOOPCUR item
indicates the current value of the total output optical power.
Attribute
Performance Event ID Performance Event Type
SUMOOPMAX: 0xD5 Equipment function
SUMOOPMIN: 0xD6
SUMOOPCUR: 0xD7
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 949
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on System
l If the total output power is excessively high, the input optical power of the downstream
board may be excessively high. As a result, bit errors are generated in the services or
even the services are interrupted. In addition, the receiver module of the board at the
downstream station may be damaged.
l If the total output power is excessively low, the input optical power of the downstream
board may be excessively low. As a result, bit errors are generated in the services or even
the services are interrupted.
Generation Principle and Possible Causes
To obtain this performance event, perform a check using the check circuit, and then calculate
the result with software for conversion.
Related Alarms
Alarm Name Correlation
OUT_PWR_HIGH The output optical power is too high. The value of the detected
output optical power is more than the upper-threshold and the
board reports the alarm in the following cases:
l The value of the output optical power is more than the
upper-threshold.
l The optical power fails to be detected correctly.
l The optical module is faulty.
OUT_PWR_LOW The output optical power is too low. The value of the detected
output optical power is less than the lower-threshold and the
board reports the alarm in the following cases:
l The value of the output optical power is less than the lower-
threshold.
l The optical power fails to be detected correctly.
l The optical module is faulty.
Procedure
Step 1 If the current performance value is 2 dB or more than the history performance value but no
alarm is reported, and if the power change is not caused by normal operations (such as
capacity expansion or upgrading), see the method of handling the OUT_PWR_HIGH alarm
to handle the performance event.
Step 2 If the current performance value is 2 dB or more less than the history performance value but
no alarm is reported, and if the power change is not caused by normal operations (such as
capacity expansion or upgrading), see the method of handling the OUT_PWR_LOW alarm
to handle the performance event.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 950
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Related Information
None.
5.4.76 T1_LCV_SDH
Performance Event Meaning
The T1_LCV_SDH event indicates the T1 line side code violation count.
Performance Event Attributes
Performance Event Performance Event Type
ID
0xA4 Check and correction
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected.
Possible Causes
The T1_LCV_SDH event shows the count of detected code violations at the line side of T1
services.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The service code pattern is incorrect.
l The board is faulty or the performance deteriorates.
Relevant Alarms
None.
Procedure
Step 1 Eliminate external causes, such as poor grounding, high operating temperature, low or high
received optical power of the line board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 951
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Step 2 Check whether the T1 service code pattern is correct. If the T1 service code pattern is
incorrect, modify the service code pattern that the board receives by setting the code pattern
of the board.
Step 3 If the port of the tributary board is faulty, replace the board.
----End
Reference
None.
5.4.77 T1_LES_SDH
Performance Event Meaning
The T1_LES_SDH event indicates the T1 line side code violation errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0xA5 Check and correction
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected.
Possible Causes
The T1_LES_SDH event shows the count of errored seconds with code violations at the line
side of T1 services.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The service code pattern is incorrect.
l The board is faulty or the performance deteriorates.
Relevant Alarms
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 952
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 See 5.4.76 T1_LCV_SDH.
----End
Reference
None.
5.4.78 T1_LSES_SDH
Performance Event Meaning
The T1_LSES_SDH event indicates the T1 line side code violation severely errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0xA6 Check and correction
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected.
Possible Causes
The T1_LSES_SDH event shows the count of severely errored seconds with code violations
at the line side of T1 services.
External causes:
l The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The service code pattern is incorrect.
l The board is faulty or the performance deteriorates.
Relevant Alarms
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 953
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 See 5.4.76 T1_LCV_SDH.
----End
Reference
None.
5.4.79 TLBCUR
Performance Event Meaning
The TLBCUR event indicates the current value of the bias current of the laser.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x62 SDH performance event
Impact on the System
When the bias current of the laser is within the allowed range, the equipment and system are
not affected. When the bias current of the laser is beyond the allowed range, the laser will fail
or be damaged, and services may be interrupted.
Possible Causes
Count the current value of the bias current transmitted by the laser. This value shows the
physical performance, which exists after the laser is online.
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 See 4.2.240 LSR_WILL_DIE or 4.2.483 TF.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 954
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Reference
None.
5.4.80 TLBMAX
Performance Event Meaning
The TLBMAX event indicates the maximum value of the bias current of the laser.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x60 SDH performance event
Impact on the System
When the bias current of the laser is within the allowed range, the equipment and system are
not affected. When the bias current of the laser is beyond the allowed range, the laser will fail
or be damaged, and services may be interrupted.
Possible Causes
Count the maximum value of the bias current transmitted by the laser in the current period.
This value shows the physical performance, which exists after the laser is online.
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 See 4.2.240 LSR_WILL_DIE or 4.2.483 TF.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 955
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.81 TLBMIN
Performance Event Meaning
The TLBMIN event indicates the minimum value of the bias current of the laser.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x61 SDH performance event
Impact on the System
When the bias current of the laser is within the allowed range, the equipment and system are
not affected. When the bias current of the laser is beyond the allowed range, the laser will fail
or be damaged, and services may be interrupted.
Possible Causes
Count the minimum value of the bias current transmitted by the laser in the current period.
This value shows the physical performance, which exists after the laser is online.
Relevant Alarms
Alarm Name Correlation
LSR_WILL_DIE The life of the laser is close to the end.
Procedure
Step 1 See 4.2.240 LSR_WILL_DIE or 4.2.483 TF.
----End
Reference
None.
5.4.82 TPLCUR
Performance Event Meaning
The TPLCUR event indicates the current value of the optical power transmitted by the laser.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 956
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x68 SDH performance event
Impact on the System
When the output optical power of the laser is within the allowed range, the equipment and
system are not affected. When the output optical power of the laser is beyond the allowed
range, the laser will fail or be damaged, and services may be interrupted.
Possible Causes
Count the current value of the optical power transmitted by the laser. This value shows the
physical performance, which exists after the laser is online.
Relevant Alarms
Alarm Name Correlation
OUT_PWR_ABN The transmitted optical power is abnormal.
Procedure
Step 1 See 4.2.366 OUT_PWR_ABN.
----End
Reference
None.
5.4.83 TPLMAX
Performance Event Meaning
The TPLMAX event indicates the maximum value of the optical power transmitted by the
laser.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x66 SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 957
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
When the output optical power of the laser is within the allowed range, the equipment and
system are not affected. When the output optical power of the laser is beyond the allowed
range, the laser will fail or be damaged, and services may be interrupted.
Possible Causes
Count the maximum value of the optical power transmitted by the laser in the current period.
This value shows the physical performance, which exists after the laser is online.
Relevant Alarms
Alarm Name Correlation
OUT_PWR_ABN The transmitted optical power is abnormal.
Procedure
Step 1 See 4.2.366 OUT_PWR_ABN.
----End
Reference
None.
5.4.84 TPLMIN
Performance Event Meaning
The TPLMIN event indicates the minimum value of the optical power transmitted by the
laser.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x67 SDH performance event
Impact on the System
When the output optical power of the laser is within the allowed range, the equipment and
system are not affected. When the output optical power of the laser is beyond the allowed
range, the laser will fail or be damaged, and services may be interrupted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 958
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
Count the minimum value of the optical power transmitted by the laser in the current period.
This value shows the physical performance, which exists after the laser is online.
Relevant Alarms
Alarm Name Correlation
OUT_PWR_ABN The transmitted optical power is abnormal.
Procedure
Step 1 See 4.2.366 OUT_PWR_ABN.
----End
Reference
None.
5.4.85 TUPJCHIGH
Performance Event Meaning
The TUPJCHIGH event indicates the count of positive TU pointer justifications.
Performance Event Attributes
Performance Event Performance Event Type
ID
0xaa SDH performance event
Impact on the System
A small count of pointer justifications does not affect the services, whereas a large count of
pointer justifications causes bit errors in the services. If a large count of pointer justifications
occurs, identify the causes and rectify the fault immediately. Otherwise, alarms will be
generated and the signal transmission quality will be affected.
Possible Causes
External causes:
l The fibers are incorrectly connected, resulting in clock loop between NEs.
l If the NEs trace the external clock, check the quality of the external clock.
Human factors:
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 959
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l The line board is faulty. As a result, the clock is of poor quality.
l The tributary board is faulty. As a result, the clock is of poor quality.
l The timing unit is faulty, providing poor-quality 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 NEs trace 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 service configurations are correct. If not, modify the service configurations
and apply them again.
Step 4 Analyze the pointer justification performance events, and locate the faulty point by changing
the position of the clock source and clock tracing direction.
----End
Reference
None.
5.4.86 TUPJCLOW
Performance Event Meaning
The TUPJCLOW event indicates the count of negative TU pointer justifications.
Performance Event Attributes
Performance Event Performance Event Type
ID
0xab SDH performance event
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 960
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
A small count of pointer justifications does not affect the services, whereas a large count of
pointer justifications causes bit errors in the services. If a large count of pointer justifications
occurs, identify the causes and rectify the fault immediately. Otherwise, alarms will be
generated and the signal transmission quality will be affected.
Possible Causes
External causes:
l The fibers are incorrectly connected, resulting in clock loop between NEs.
l If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l The line board is faulty. As a result, the clock is of poor quality.
l The tributary board is faulty. As a result, the clock is of poor quality.
l The timing unit is faulty, providing poor-quality 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 See 5.4.85 TUPJCHIGH.
----End
Reference
None.
5.4.87 TUPJCNEW
Performance Event Meaning
The TUPJCNEW event indicates the count of new TU pointer justifications.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 961
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0xac SDH performance event
Impact on the System
A small count of pointer justifications does not affect the services, whereas a large count of
pointer justifications causes bit errors in the services. If a large count of pointer justifications
occurs, identify the causes and rectify the fault immediately. Otherwise, alarms will be
generated and the signal transmission quality will be affected.
Possible Causes
External causes:
l The fibers are incorrectly connected, resulting in clock loop between NEs.
l If the NEs trace the external clock, check the quality of the external clock.
Human factors:
l The configuration of the clock source is incorrect. There are two clock sources in one
network.
l The configuration of the clock source tracing priority is incorrect. The clocks of the two
NEs trace each other.
Equipment problems:
l The line board is faulty. As a result, the clock is of poor quality.
l The tributary board is faulty. As a result, the clock is of poor quality.
l The timing unit is faulty, providing poor-quality 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 See 5.4.85 TUPJCHIGH.
----End
Reference
None.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 962
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.4.88 VC3BBE
Performance Event Meaning
The VC3BBE event indicates the VC3 background block error.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x50 SDH performance event
Impact on the System
If bit errors occur in the services, identify the causes and rectify the fault immediately.
Otherwise, alarms will be generated and the signal transmission quality will be affected. If bit
errors exceed the B3 bit error threshold-crossing threshold and degrade threshold, the
B3_EXC and B3_SD alarms will be generated.
Possible Causes
The VC3BBE event 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 The fiber performance is degraded, and the fiber has high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a severe interference source around the equipment.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board is excessive, the transmit
circuit at the opposite end is faulty, or the receive circuit at the local end is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B3_EXC_VC3 B3 bit errors crossing the threshold
B3_SD_VC3 Signals degraded (B3)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 963
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Procedure
Step 1 Eliminate external causes, such as poor grounding, high operating temperature, low or high
received optical power of the line board. In this case, perform the grounding again.
Alternatively, find a better operating environment. For more information about solving the
optical power problem, see 5.4.64 RPLCUR. 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 may be faulty. In this case,
replace the CXL board.
Step 3 If only a line board reports that bit errors exist, the local line board may be faulty or that the
opposite NE or fibers are faulty. Locate the faulty board by using the loopback method. Then,
replace the faulty board with a new one.
----End
Reference
None.
5.4.89 VC3CSES
Performance Event Meaning
The VC3CSES performance event indicates the VC3 continuous severely error seconds.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x57 SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected. If bit errors exceed the B3 bit error threshold-crossing threshold and degrade
threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
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 The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 964
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
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.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B3_EXC_VC3 B3 bit errors crossing the threshold
B3_SD_VC3 Signals degraded (B3)
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 Multiplex section alarm indication
AU_AIS AU alarm indication
AU_LOP AU pointer loss
Procedure
Step 1 Refer to 5.4.90 VC3ES.
----End
Reference
None.
5.4.90 VC3ES
Performance Event Meaning
The VC3ES performance event indicates VC-3 error seconds.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 965
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Performance Event Attributes
Performance Event Performance Event Type
ID
0x51 SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected. If bit errors exceed the B3 bit error threshold-crossing threshold and degrade
threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
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 and AU_LOP alarms are detected over the path.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
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.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B3_EXC_VC3 B3 bit errors crossing the threshold
B3_SD_VC3 Signals degraded (B3)
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 Multiplex section alarm indication
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 966
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Alarm Name Correlation
AU_AIS AU alarm indication
AU_LOP AU pointer loss
Procedure
Step 1 If the LOS/LOF alarm is reported, a fiber cut, too much attenuation, received overload or
faulty 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 is reported:
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.
Step 3 If the AU_AIS alarm is reported:
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 is reported 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 configured. If not, modify the incorrect configuration and issue it again.
3. 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.
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 is reported:
1. Check whether the service configuration is correct at the local and opposite stations. If
not, configure them to correct.
2. Check whether the transmit unit of the line board on the opposite station is faulty. Check
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.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 967
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Step 5 Refer to 5.4.88 VC3BBE.
----End
Reference
None.
5.4.91 VC3FEBBE
Performance Event Meaning
The VC3FEBBE event indicates the VC-3 far end background block error.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x53 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
The VC3FEBBE event indicates 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 The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 968
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Relevant Alarms
Alarm Name Correlation
LP_REI_VC3 VC-3 path remote error indication
Procedure
Step 1 See 5.4.88 VC3BBE.
----End
Reference
None.
5.4.92 VC3FECSES
Performance Event Meaning
The VC3FECSES event indicates the VC-3 far end consecutive severely errorred second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x58 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
When a consecutive VC3FECSES sequence is detected, the VC3FECSES event occurs. When
unavailable time comes or VC3FECSES is absent in one second, the VC3FECSES sequence
ends.
External causes:
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 969
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
LP_REI_VC3 VC-3 path remote error indication
LP_RDI_VC3 VC-3 path remote defect indication
Procedure
Step 1 See 5.4.93 VC3FEES.
----End
Reference
None.
5.4.93 VC3FEES
Performance Event Meaning
The VC3FEES event indicates the VC-3 far end errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x54 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 970
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
The HPFEES 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 The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
LP_REI_VC3 VC-3 path remote error indication
LP_RDI_VC3 VC-3 path remote defect indication
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 system control, switching, and timing board in turn.
4. If the transmit part of the local station is faulty, replace the system control, switching,
and timing board.
Step 2 See 5.4.91 VC3FEBBE.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 971
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Reference
None.
5.4.94 VC3FESES
Performance Event Meaning
The VC3FESES event indicates the VC-3 far end severely errored second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x55 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
The VC3FESES event occurs when one of the following requirements is met: 1. Not less than
30% bit errors are contained in the message returned in one second. 2. At least one severely
disturbed period (SDP) occurs. SDP occurs when the BER of all the continuous blocks in a
period of at least four consecutive blocks or 1 ms (select the shorter period) is lower than 10-2,
or when the LP_RDI alarm occurs.
External causes:
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 972
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Relevant Alarms
Alarm Name Correlation
LP_REI_VC3 VC-3 path remote error indication
LP_RDI_VC3 VC-3 path remote defect indication
Procedure
Step 1 See 5.4.93 VC3FEES.
----End
Reference
None.
5.4.95 VC3FEUAS
Performance Event Meaning
The VC3FEUAS event indicates the VC-3 far end unavailable second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x59 SDH performance event
Impact on the System
If bit errors occur in the services on a remote NE, identify the causes and rectify the fault
immediately. Otherwise, alarms will be generated and the signal transmission quality will be
affected.
Possible Causes
The VC3FEUAS event indicates the duration in which the unavailable time (UAT) state lasts.
External causes:
l The fiber performance degrades and the attenuation is excessive at the opposite station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is poorly grounded at the opposite station.
l There is a severe interference source around the equipment at the opposite station.
l The working temperature is high or low, and the opposite equipment cannot tolerate such
temperature.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 973
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Equipment problems:
l The signal attenuation on the receive side of the line board at the opposite station is
excessive, or the transmit circuit at the opposite station is faulty, or the receive circuit at
the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the line board poorly match at the opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
Alarm Name Correlation
LP_REI_VC3 VC-3 path remote error indication
LP_RDI_VC3 VC-3 path remote defect indication
Procedure
Step 1 See 5.4.93 VC3FEES.
----End
Reference
None.
5.4.96 VC3SES
Performance Event Meaning
The VC3SES is a performance event indicating the VC3 far end severely error second.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x52 SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected. If bit errors exceed the B3 bit error threshold-crossing threshold and degrade
threshold, the B3_EXC and B3_SD alarms will be generated.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 974
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Possible Causes
The VC3SES performance event occurs when one of the following requirements 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 one millisecond (the longer one is selected), or the AU_AIS and
AU_LOP alarms are detected on the path.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
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.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
B3_EXC_VC3 B3 bit errors crossing the threshold
B3_SD_VC3 Signals degraded (B3)
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 Multiplex section alarm indication
AU_AIS AU alarm indication
AU_LOP AU pointer loss
Procedure
Step 1 Refer to 5.4.90 VC3ES.
----End
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 975
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Reference
None.
5.4.97 VC3UAS
Performance Event Meaning
The VC3UAS performance event indicates the VC3 unavailable seconds.
Performance Event Attributes
Performance Event Performance Event Type
ID
0x56 SDH performance event
Impact on the System
If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in time. Otherwise, alarms will be generated and the signal transmission quality will
be affected. If bit errors exceed the B3 bit error threshold-crossing threshold and degrade
threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
VC3UAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l The fiber performance is degraded, and the fiber has extremely high attenuation.
l The fiber connector is dirty or incorrect.
l The equipment is poorly grounded.
l There is a strong interference source around the equipment.
l The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
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.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the line board poorly match.
l The board becomes faulty, or the performance of the board is degraded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 976
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Relevant Alarms
Alarm Name Correlation
B3_EXC_VC3 B3 bit errors crossing the threshold
B3_SD_VC3 Signals degraded (B3)
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 Multiplex section alarm indication
AU_AIS AU alarm indication
AU_LOP AU pointer loss
Procedure
Step 1 Refer to 5.4.90 VC3ES.
----End
Reference
5.4.97 VC3UAS
5.4.98 WCV
Description
The WCV event indicates the pump laser working current, also called pump laser driver
current or pump laser bias current. It includes:
l WCVMAX: stands for the maximum value during a period of time (in 1 mA).
l WCVMIN: stands for the minimum value during a period of time (in 1 mA).
l WCVCUR: stands for the current value (in 1 mA).
Attribute
Performance Event Performance Event Type
ID
WCVMAX: 0x70 Equipment function
WCVMIN: 0x71
WCVCUR: 0x72
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 977
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Impact on the System
When the pump laser works properly, there is no impact on the services. If an alarm is
generated, identify the cause.
Possible Causes
WCV indicates the pump laser driver current of an optical amplifier board. The optical
amplifier board amplifies the input signal using the pump laser driven by pump laser working
current.
Related Alarms
Alarm Name Correlation
4.2.404 PUM_BCM_ALM Pump laser bias current threshold-crossing alarm. The
board reports this alarm when the detected pump laser
drive current is higher than the threshold due to laser
exceptions caused by laser aging, or over-high/low
ambient temperature.
4.2.240 LSR_WILL_DIE Laser life time termination alarm. The board reports this
alarm when the pump laser drive current is higher than the
termination threshold due to laser aging.
4.2.478 TD Transmitting laser degrade alarm. The threshold of the
laser is set to a value 1.2 times of the initial value of the
bias current. This alarm is generated when the bias current
of the laser exceeds the threshold and is smaller than the
initial value by 1.5 times.
Procedure
Step 1 If the 4.2.404 PUM_BCM_ALM alarm is generated, see the related handling procedure.
Step 2 If the 4.2.240 LSR_WILL_DIE alarm is generated, see the related handling procedure.
Step 3 If the 4.2.478 TD alarm is generated, see the related handling procedure.
----End
Related Information
None.
5.4.99 XCSTMP
Description
The XCSTMP is a performance event indicating the temperature of a board. It contains the
XCSTMPMAX, XCSTMPMIN, and XCSTMPCUR, which respectively indicates the
maximum value, minimum value, and current value of the temperature of a board.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 978
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Attribute
Performance Event Performance Event Type
ID
XCSTMPMAX: 0xBC Equipment function
XCSTMPMIN: 0xBD
XCSTMPCUR: 0xBE
Impact on System
Excessively high or low board temperature might cause faults such as degradation of the
board working performance and bit errors.
Generation Principle and Possible Causes
When the ambient temperature is abnormal, or when the heat-sinking and ventilation
measures are improper, the XCSTEMP event occurs.
Related Alarms
Alarm Name Correlation
TEMP_OVER This alarm is reported if the temperature of the board
exceeds the specified threshold.
TEMP_ALARM This alarm is reported if the ambient temperature of the
board exceeds the specified threshold.
Procedure
Step 1 If any alarm occurs, use the method of the related alarm to clear it.
----End
Related Information
None.
5.5 RMON Event of the Ethernet Service List
This section uses a table to list the RMON performance events corresponding to the boards
supported by the equipment.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 979
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.5.1 CQ1
Table 5-27 CES
CES_MISORDERPKTS CES_STRAYPKTS CES_MALPKTS
CES_JTRUDR CES_JTROVR CES_LOSPKTS
CES_RX_PKTS CES_TX_PKTS
Table 5-28 PW
PW_RCVPKTS PW_RCVBYTES
Table 5-29 PPP
PPP_TX_PKTS PPP_TX_BYTES PPP_RX_PKTS
PPP_RX_BYTES PPP_RX_FCSPKTS PPP_TX_LOSPKTS
PPP_RX_BW_UTILIZATI PPP_TX_BW_UTILIZATI
PPP_RX_LOSPKTS
ON ON
Table 5-30 ML-PPP
MP_TX_PKTS MP_TX_BYTES MP_RX_PKTS
MP_RX_BYTES MP_RX_ERRPKTS MP_TX_TOTALPKTS
MP_RX_BW_UTILIZATIO MP_TX_BW_UTILIZATI
MP_RX_TOTALPKTS
N ON
5.5.2 CSHD
SCC
Table 5-31 L2VPN
VUNI_RCVPKTS VUNI_RCVBYTES VLAN_RCVPKTS
VLAN_RCVBYTES VLAN_RX_BPS VLAN_RX_PPS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 980
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-32 Tunnel
TUNNEL_REVERSE_RC
TUNNEL_RCVPKTS TUNNEL_RCVBYTES
VPKTS
TUNNEL_REVERSE_RCVB
TUNNEL_RX_BPS TUNNEL_RX_PPS
YTES
TUNNEL_REVERSE_RX_B TUNNEL_REVERSE_RX_
PS PPS
Table 5-33 PW
PW_RCVPKTS PW_RCVBYTES PW_DROPPKTS
PW_RX_BPS PW_RX_PPS
Table 5-34 MPLS-TP OAM
MPLS_TUNNEL_FLR MPLS_TUNNEL_FL MPLS_TUNNEL_FLR_N
MPLS_TUNNEL_FL_N MPLS_TUNNEL_FD MPLS_TUNNEL_FDV
MPLS_PW_FLR MPLS_PW_FL MPLS_PW_FLR_N
MPLS_PW_FL_N MPLS_PW_FD MPLS_PW_FDV
Table 5-35 ETH OAM 802.1ag
ETH_CFM_FLR ETH_CFM_FL ETH_CFM_FD
ETH_CFM_FDV
Table 5-36 QoS
QOS_CARGRNPKTS QOS_CARYLWPKTS QOS_CARREDPKTS
QOS_CARREDRATIO
EM6X
Table 5-37 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 981
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-38 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-39 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 982
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
ML1
Table 5-40 ATM PWE3
ATMPW_UNKNOWNCE
ATMPW_SNDCELLS ATMPW_RCVCELLS
LLS
Table 5-41 ATM/IMA performance events on the access side
ATM_CORRECTED_HCSE ATM_UNCORRECTED_H
ATM_RCVCELLS
RR CSERR
ATM_RCVIDLECELLS ATM_SNDCELLS ATM_IF_INRATE_MAX
ATM_IF_OUTRATE_MA
ATM_IF_INRATE_MIN ATM_IF_INRATE_AVG
X
ATM_CELL_AVAILABIL
ATM_IF_OUTRATE_MIN ATM_IF_OUTRATE_AVG
ITY
PORT_RX_BW_UTILIZATI PORT_TX_BW_UTILIZAT
ATM_UNI1_INCELLS
ON ION
ATM_UNI1_OUTCELLS ATM_UNI2_INCELLS ATM_UNI2_OUTCELLS
ATM_UNI1_INRATE_AV
ATM_UNI1_INRATE_MAX ATM_UNI1_INRATE_MIN
G
ATM_UNI1_OUTRATE_MA ATM_UNI1_OUTRATE_M ATM_UNI1_OUTRATE_
X IN AVG
ATM_UNI2_INRATE_AV
ATM_UNI2_INRATE_MAX ATM_UNI2_INRATE_MIN
G
ATM_UNI2_OUTRATE_MA ATM_UNI2_OUTRATE_M ATM_UNI2_OUTRATE_
X IN AVG
Table 5-42 CES
CES_MISORDERPKTS CES_STRAYPKTS CES_MALPKTS
CES_JTRUDR CES_JTROVR CES_LOSPKTS
CES_RX_PKTS CES_TX_PKTS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 983
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-43 PW
PW_RCVPKTS PW_RCVBYTES
5.5.3 EF8F
Table 5-44 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-45 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT65 PKT128 PKT256
PKT512 PKT1024 PKT64
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-46 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 984
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
5.5.4 EFS8
Table 5-47 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHUNDER ETHOVER
ETHFRG ETHJAB RXPKT64
RXPKT65 RXPKT128 RXPKT256
RXPKT512 RXPKT1024
Table 5-48 Statistics of RMON extended performance
RXCTLPKTS TXOCTETS TXPKTS
TXCTLPKTS TXBRDCAST TXMULCAST
TXPKT64 TXPKT65 TXPKT128
TXPKT256 TXPKT512 TXPKT1024
RXUNICAST TXUNICAST RXPAUSE
TXPAUSE ETHALI ETHFCS
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
TXGOODFULLFRAME-
TXFULLBGOOD RXFULLBGOOD
SPEED
RXGOODFULLFRAME-
SPEED
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 985
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-49 Statistics of RMON VCG performance
VCG_TXGOODPACKETS VCG_TXPACKETS VCG_TXOCTETS
VCG_RXGOODPACKETS VCG_RXPACKETS VCG_RXOCTETS
VCG_TXSPEED VCG_RXSPEED
5.5.5 EG4C
Table 5-50 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-51 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 986
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-52 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
5.5.6 EG8
Table 5-53 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-54 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 987
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-55 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
5.5.7 EGS4
Table 5-56 Statistics of RMON basic performance
RXMULCAST RXBRDCAST RXPKTS
ETHFRG ETHJAB RXPKT64
RXPKT65 RXPKT128 RXPKT256
RXPKT512 RXPKT1024 ETHUNDER
ETHOVER
Table 5-57 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXMULCAST
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 988
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
TXBRDCAST RXPAUSE TXPAUSE
RXGOODFULLFRAME-
RXBGOOD TXBGOOD
SPEED
TXGOODFULLFRAME-
TXPKT64 TXPKT65
SPEED
TXPKT128 TXPKT256 TXPKT512
TXPKT1024 PKT64 PKT65
PKT128 PKT256 PKT512
PKT1024 RXFULLBGOOD TXFULLBGOOD
ETHALI ETHFCS
Table 5-58 Statistics of RMON VCG performance
VCG_TXGOODPACKETS VCG_TXPACKETS VCG_TXOCTETS
VCG_RXGOODPACKETS VCG_RXPACKETS VCG_RXOCTETS
VCG_TXSPEED VCG_RXSPEED
5.5.8 EGT1
Table 5-59 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHUNDER ETHOVER
ETHFRG ETHJAB RXPKT64
RXPKT65 RXPKT128 RXPKT256
RXPKT512 RXPKT1024
Table 5-60 Statistics of RMON extended performance
TXBRDCAST TXMULCAST TXPKT64
TXPKT65 TXPKT128 TXPKT256
TXPKT512 TXPKT1024 RXPAUSE
TXPAUSE ETHFCS PKT64
PKT65 PKT128 PKT256
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 989
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
PKT512 PKT1024 TXUNICAST
RXUNICAST
5.5.9 EM10
Table 5-61 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHUNDER ETHOVER
ETHFRG ETHJAB RXPKT64
RXPKT65 RXPKT128 RXPKT256
RXPKT512 RXPKT1024
Table 5-62 Statistics of RMON extended performance
RXPKT1519 RXUNICAST TXUNICAST
TXMULCAST TXBRDCAST RXPAUSE
TXPAUSE RXBGOOD TXBGOOD
ETHFCS ETHUTILIZ RXCTLPKTS
TXCTLPKTS TXPKTS TXOCTETS
RXGOODFULLFRAME- TXGOODFULLFRAME-
RXFULLBGOOD
SPEED SPEED
PORT_RX_BYTES_AVAIL PORT_RX_BW_UTILIZA
TXFULLBGOOD
ABILITY TION
PORT_TX_BW_UTILIZATI
RXBPS TXBPS
ON
RXPPS TXPPS TX_DROP_RATIO
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-63 L2VPN
VUNI_RCVPKTS VUNI_RCVBYTES VUNI_SNDPKTS
VUNI_SNDBYTES VUNI_TX_UTILIZATION VUNI_SND_DROPPKTS
VUNI_SND_DROPBYTES VUNI_SND_DROPRATIO VLAN_RCVPKTS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 990
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
VLAN_RCVBYTES VLAN_SNDPKTS VLAN_SNDBYTES
VLAN_RX_BPS VLAN_TX_BPS VLAN_RX_PPS
VLAN_TX_PPS
Table 5-64 Tunnel
TUNNEL_RCVPKTS TUNNEL_RCVBYTES TUNNEL_SNDPKTS
TNL_REVERSE_BW_UT
TUNNEL_SNDBYTES TNL_BW_UTILISATION
ILISATION
TUNNEL_REVERSE_SNDP TUNNEL_REVERSE_SND TUNNEL_REVERSE_RC
KTS BYTES VPKTS
TUNNEL_REVERSE_RCVB
TUNNEL_RX_BPS TUNNEL_TX_BPS
YTES
TUNNEL_REVERSE_RX
TUNNEL_RX_PPS TUNNEL_TX_PPS
_BPS
TUNNEL_REVERSE_TX_B TUNNEL_REVERSE_RX_ TUNNEL_REVERSE_TX
PS PPS _PPS
Table 5-65 PW
PW_RCVPKTS PW_RCVBYTES PW_SNDPKTS
PW_SNDBYTES PW_DROPPKTS PW_DROPBYTES
PW_BANDWIDTH_UTILIS
PW_RX_BPS PW_TX_BPS
ATION
PW_RX_PPS PW_TX_PPS
Table 5-66 MPLS-TP OAM
MPLS_TUNNEL_FLR MPLS_TUNNEL_FL MPLS_TUNNEL_FLR_N
MPLS_TUNNEL_FL_N MPLS_TUNNEL_FD MPLS_TUNNEL_FDV
MPLS_PW_FLR MPLS_PW_FL MPLS_PW_FLR_N
MPLS_PW_FL_N MPLS_PW_FD MPLS_PW_FDV
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 991
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-67 ETH OAM 802.1ag
ETH_CFM_FLR ETH_CFM_FL ETH_CFM_FD
ETH_CFM_FDV
Table 5-68 QoS
QOS_STRM_MATCHBYT
QOS_STRM_MATCHPKTS QOS_PRI_DROPPKTS
ES
QOS_PRI_DROPBYTES PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES
QOS_PORTQUEUE_DR
PORT_PRI_TX_BPS PORT_PRI_TX_PPS
OPRATIO
PWQUEUE_SNDDROPPK PWQUEUE_SNDDROPB
FLOW_RX_UTILIZATION
TS YTES
PWQUEUE_SNDDROPRAT
PWQUEUE_TX_BPS PWQUEUE_TX_PPS
IO
TNL_SNDDROPPKTS TNL_SNDDROPBYTES TNL_SNDDROPRATIO
TNL_REVERSE_SNDDROP TNL_REVERSE_SNDDR TNL_REVERSE_SNDDR
PKTS OPBYTES OPRATIO
VUNIQUEUE_SNDDROPP VUNIQUEUE_SNDDROP VUNIQUEUE_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDDROPP VUNIGROUP_SNDDROP VUNIGROUP_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDBYTE VGROUP_TX_UTILIZAT
VUNIGROUP_SNDPKTS
S ION
Table 5-69 CES
CES_MISORDERPKTS CES_STRAYPKTS CES_MALPKTS
CES_JTRUDR CES_JTROVR CES_LOSPKTS
CES_RX_PKTS CES_TX_PKTS PW_RCVPKTS
5.5.10 EM20
Table 5-70 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 992
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
RXMULCAST ETHUNDER ETHOVER
ETHFRG ETHJAB RXPKT64
RXPKT65 RXPKT128 RXPKT256
RXPKT512 RXPKT1024
Table 5-71 Statistics of RMON extended performance
RXPKT1519 RXUNICAST TXUNICAST
TXMULCAST TXBRDCAST RXPAUSE
TXPAUSE RXBGOOD TXBGOOD
ETHFCS ETHUTILIZ RXCTLPKTS
TXCTLPKTS TXPKTS TXOCTETS
RXGOODFULLFRAME- TXGOODFULLFRAME-
RXFULLBGOOD
SPEED SPEED
PORT_RX_BYTES_AVAIL PORT_RX_BW_UTILIZA
TXFULLBGOOD
ABILITY TION
PORT_TX_BW_UTILIZATI
RXBPS TXBPS
ON
RXPPS TXPPS TX_DROP_RATIO
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-72 L2VPN
VUNI_RCVPKTS VUNI_RCVBYTES VUNI_SNDPKTS
VUNI_SNDBYTES VUNI_TX_UTILIZATION VUNI_SND_DROPPKTS
VUNI_SND_DROPBYTES VUNI_SND_DROPRATIO VLAN_RCVPKTS
VLAN_RCVBYTES VLAN_SNDPKTS VLAN_SNDBYTES
VLAN_RX_BPS VLAN_TX_BPS VLAN_RX_PPS
VLAN_TX_PPS
Table 5-73 Tunnel
TUNNEL_RCVPKTS TUNNEL_RCVBYTES TUNNEL_SNDPKTS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 993
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
TNL_REVERSE_BW_UT
TUNNEL_SNDBYTES TNL_BW_UTILISATION
ILISATION
TUNNEL_REVERSE_SNDP TUNNEL_REVERSE_SND TUNNEL_REVERSE_RC
KTS BYTES VPKTS
TUNNEL_REVERSE_RCVB
TUNNEL_RX_BPS TUNNEL_TX_BPS
YTES
TUNNEL_REVERSE_RX
TUNNEL_RX_PPS TUNNEL_TX_PPS
_BPS
TUNNEL_REVERSE_TX_B TUNNEL_REVERSE_RX_ TUNNEL_REVERSE_TX
PS PPS _PPS
Table 5-74 PW
PW_RCVPKTS PW_RCVBYTES PW_SNDPKTS
PW_SNDBYTES PW_DROPPKTS PW_DROPBYTES
PW_BANDWIDTH_UTILIS
PW_RX_BPS PW_TX_BPS
ATION
PW_RX_PPS PW_TX_PPS
Table 5-75 MPLS-TP OAM
MPLS_TUNNEL_FLR MPLS_TUNNEL_FL MPLS_TUNNEL_FLR_N
MPLS_TUNNEL_FL_N MPLS_TUNNEL_FD MPLS_TUNNEL_FDV
MPLS_PW_FLR MPLS_PW_FL MPLS_PW_FLR_N
MPLS_PW_FL_N MPLS_PW_FD MPLS_PW_FDV
Table 5-76 ETH OAM 802.1ag
ETH_CFM_FLR ETH_CFM_FL ETH_CFM_FD
ETH_CFM_FDV
Table 5-77 QoS
QOS_STRM_MATCHBYT
QOS_STRM_MATCHPKTS QOS_PRI_DROPPKTS
ES
QOS_PRI_DROPBYTES PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 994
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
QOS_PORTQUEUE_DR
PORT_PRI_TX_BPS PORT_PRI_TX_PPS
OPRATIO
PWQUEUE_SNDDROPPK PWQUEUE_SNDDROPB
FLOW_RX_UTILIZATION
TS YTES
PWQUEUE_SNDDROPRAT
PWQUEUE_TX_BPS PWQUEUE_TX_PPS
IO
TNL_SNDDROPPKTS TNL_SNDDROPBYTES TNL_SNDDROPRATIO
TNL_REVERSE_SNDDROP TNL_REVERSE_SNDDR TNL_REVERSE_SNDDR
PKTS OPBYTES OPRATIO
VUNIQUEUE_SNDDROPP VUNIQUEUE_SNDDROP VUNIQUEUE_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDDROPP VUNIGROUP_SNDDROP VUNIGROUP_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDBYTE VGROUP_TX_UTILIZAT
VUNIGROUP_SNDPKTS
S ION
5.5.11 EM6F
Table 5-78 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-79 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 995
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-80 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
5.5.12 EM6T
Table 5-81 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-82 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 996
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-83 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
5.5.13 EX1
Table 5-84 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 997
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-85 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT65 PKT128 PKT256
PKT512 PKT1024 PKT64
RXBRDCAST_RATIO TXBRDCAST_RATIO -
Table 5-86 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 998
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.5.14 HUND2
Table 5-87 Statistics of RMON basic performance
PORT_RX_BW_UTILIZA
RXOCTETS RXPKTS
TION
PORT_TX_BW_UTILIZATI
ON
Table 5-88 Statistics of RMON extended performance
RXBPS TXBPS RXPPS
TXPPS TX_DROP_RATIO ETHUTILIZ
TXPKTS TXOCTETS
Table 5-89 L2VPN
VUNI_RCVPKTS VUNI_RCVBYTES VUNI_SNDPKTS
VUNI_SNDBYTES VUNI_TX_UTILIZATION VUNI_SND_DROPPKTS
VUNI_SND_DROPBYTES VUNI_SND_DROPRATIO VLAN_RCVPKTS
VLAN_RCVBYTES VLAN_SNDPKTS VLAN_SNDBYTES
VLAN_RX_BPS VLAN_TX_BPS VLAN_RX_PPS
VLAN_TX_PPS
Table 5-90 Tunnel
TUNNEL_RCVPKTS TUNNEL_RCVBYTES TUNNEL_SNDPKTS
TNL_REVERSE_BW_UT
TUNNEL_SNDBYTES TNL_BW_UTILISATION
ILISATION
TUNNEL_REVERSE_SNDP TUNNEL_REVERSE_SND TUNNEL_REVERSE_RC
KTS BYTES VPKTS
TUNNEL_REVERSE_RCVB
TUNNEL_RX_BPS TUNNEL_TX_BPS
YTES
TUNNEL_REVERSE_RX
TUNNEL_RX_PPS TUNNEL_TX_PPS
_BPS
TUNNEL_REVERSE_TX_B TUNNEL_REVERSE_RX_ TUNNEL_REVERSE_TX
PS PPS _PPS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 999
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-91 PW
PW_RCVPKTS PW_RCVBYTES PW_SNDPKTS
PW_SNDBYTES PW_DROPPKTS PW_DROPBYTES
PW_BANDWIDTH_UTILIS
PW_RX_BPS PW_TX_BPS
ATION
PW_RX_PPS PW_TX_PPS
Table 5-92 MPLS-TP OAM
MPLS_TUNNEL_FLR MPLS_TUNNEL_FL MPLS_TUNNEL_FLR_N
MPLS_TUNNEL_FL_N MPLS_TUNNEL_FD MPLS_TUNNEL_FDV
MPLS_PW_FLR MPLS_PW_FL MPLS_PW_FLR_N
MPLS_PW_FL_N MPLS_PW_FD MPLS_PW_FDV
Table 5-93 ETH OAM 802.1ag
ETH_CFM_FLR ETH_CFM_FL ETH_CFM_FD
ETH_CFM_FDV
Table 5-94 QoS
QOS_STRM_MATCHBYT
QOS_STRM_MATCHPKTS QOS_PRI_DROPPKTS
ES
QOS_PRI_DROPBYTES PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES
QOS_PORTQUEUE_DR
PORT_PRI_TX_BPS PORT_PRI_TX_PPS
OPRATIO
PWQUEUE_SNDDROPPK PWQUEUE_SNDDROPB
FLOW_RX_UTILIZATION
TS YTES
PWQUEUE_SNDDROPRAT
PWQUEUE_TX_BPS PWQUEUE_TX_PPS
IO
TNL_SNDDROPPKTS TNL_SNDDROPBYTES TNL_SNDDROPRATIO
TNL_REVERSE_SNDDROP TNL_REVERSE_SNDDR TNL_REVERSE_SNDDR
PKTS OPBYTES OPRATIO
VUNIQUEUE_SNDDROPP VUNIQUEUE_SNDDROP VUNIQUEUE_SNDDRO
KTS BYTES PRATIO
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1000
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
VUNIGROUP_SNDDROPP VUNIGROUP_SNDDROP VUNIGROUP_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDBYTE VGROUP_TX_UTILIZAT
VUNIGROUP_SNDPKTS
S ION
5.5.15 HUNS3
Table 5-95 Statistics of RMON basic performance
PORT_RX_BW_UTILIZA
RXOCTETS RXPKTS
TION
PORT_TX_BW_UTILIZATI
ON
Table 5-96 Statistics of RMON extended performance
RXBPS TXBPS RXPPS
TXPPS TX_DROP_RATIO ETHUTILIZ
TXPKTS TXOCTETS
Table 5-97 L2VPN
VUNI_RCVPKTS VUNI_RCVBYTES VUNI_SNDPKTS
VUNI_SNDBYTES VUNI_TX_UTILIZATION VUNI_SND_DROPPKTS
VUNI_SND_DROPBYTES VUNI_SND_DROPRATIO VLAN_RCVPKTS
VLAN_RCVBYTES VLAN_SNDPKTS VLAN_SNDBYTES
VLAN_RX_BPS VLAN_TX_BPS VLAN_RX_PPS
VLAN_TX_PPS
Table 5-98 Tunnel
TUNNEL_RCVPKTS TUNNEL_RCVBYTES TUNNEL_SNDPKTS
TNL_REVERSE_BW_UT
TUNNEL_SNDBYTES TNL_BW_UTILISATION
ILISATION
TUNNEL_REVERSE_SNDP TUNNEL_REVERSE_SND TUNNEL_REVERSE_RC
KTS BYTES VPKTS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1001
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
TUNNEL_REVERSE_RCVB
TUNNEL_RX_BPS TUNNEL_TX_BPS
YTES
TUNNEL_REVERSE_RX
TUNNEL_RX_PPS TUNNEL_TX_PPS
_BPS
TUNNEL_REVERSE_TX_B TUNNEL_REVERSE_RX_ TUNNEL_REVERSE_TX
PS PPS _PPS
Table 5-99 PW
PW_RCVPKTS PW_RCVBYTES PW_SNDPKTS
PW_SNDBYTES PW_DROPPKTS PW_DROPBYTES
PW_BANDWIDTH_UTILIS
PW_RX_BPS PW_TX_BPS
ATION
PW_RX_PPS PW_TX_PPS
Table 5-100 MPLS-TP OAM
MPLS_TUNNEL_FLR MPLS_TUNNEL_FL MPLS_TUNNEL_FLR_N
MPLS_TUNNEL_FL_N MPLS_TUNNEL_FD MPLS_TUNNEL_FDV
MPLS_PW_FLR MPLS_PW_FL MPLS_PW_FLR_N
MPLS_PW_FL_N MPLS_PW_FD MPLS_PW_FDV
Table 5-101 ETH OAM 802.1ag
ETH_CFM_FLR ETH_CFM_FL ETH_CFM_FD
ETH_CFM_FDV
Table 5-102 QoS
QOS_STRM_MATCHBYT
QOS_STRM_MATCHPKTS QOS_PRI_DROPPKTS
ES
QOS_PRI_DROPBYTES PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES
QOS_PORTQUEUE_DR
PORT_PRI_TX_BPS PORT_PRI_TX_PPS
OPRATIO
PWQUEUE_SNDDROPPK PWQUEUE_SNDDROPB
FLOW_RX_UTILIZATION
TS YTES
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1002
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
PWQUEUE_SNDDROPRAT
PWQUEUE_TX_BPS PWQUEUE_TX_PPS
IO
TNL_SNDDROPPKTS TNL_SNDDROPBYTES TNL_SNDDROPRATIO
TNL_REVERSE_SNDDROP TNL_REVERSE_SNDDR TNL_REVERSE_SNDDR
PKTS OPBYTES OPRATIO
VUNIQUEUE_SNDDROPP VUNIQUEUE_SNDDROP VUNIQUEUE_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDDROPP VUNIGROUP_SNDDROP VUNIGROUP_SNDDRO
KTS BYTES PRATIO
VUNIGROUP_SNDBYTE VGROUP_TX_UTILIZAT
VUNIGROUP_SNDPKTS
S ION
5.5.16 MD1
Table 5-103 ATM PWE3
ATMPW_UNKNOWNCE
ATMPW_SNDCELLS ATMPW_RCVCELLS
LLS
Table 5-104 ATM/IMA performance events on the access side
ATM_CORRECTED_HCSE ATM_UNCORRECTED_H
ATM_RCVCELLS
RR CSERR
ATM_RCVIDLECELLS ATM_SNDCELLS ATM_IF_INRATE_MAX
ATM_IF_OUTRATE_MA
ATM_IF_INRATE_MIN ATM_IF_INRATE_AVG
X
ATM_CELL_AVAILABIL
ATM_IF_OUTRATE_MIN ATM_IF_OUTRATE_AVG
ITY
PORT_RX_BW_UTILIZATI PORT_TX_BW_UTILIZAT
ATM_UNI1_INCELLS
ON ION
ATM_UNI1_OUTCELLS ATM_UNI2_INCELLS ATM_UNI2_OUTCELLS
ATM_UNI1_INRATE_AV
ATM_UNI1_INRATE_MAX ATM_UNI1_INRATE_MIN
G
ATM_UNI1_OUTRATE_MA ATM_UNI1_OUTRATE_M ATM_UNI1_OUTRATE_
X IN AVG
ATM_UNI2_INRATE_AV
ATM_UNI2_INRATE_MAX ATM_UNI2_INRATE_MIN
G
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1003
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
ATM_UNI2_OUTRATE_MA ATM_UNI2_OUTRATE_M ATM_UNI2_OUTRATE_
X IN AVG
Table 5-105 CES
CES_MISORDERPKTS CES_STRAYPKTS CES_MALPKTS
CES_JTRUDR CES_JTROVR CES_LOSPKTS
CES_RX_PKTS CES_TX_PKTS
Table 5-106 PW
PW_RCVPKTS PW_RCVBYTES
5.5.17 PCX
SCC
Table 5-107 L2VPN
VUNI_RCVPKTS VUNI_RCVBYTES VLAN_RCVPKTS
VLAN_RCVBYTES VLAN_RX_BPS VLAN_RX_PPS
Table 5-108 Tunnel
TUNNEL_REVERSE_RC
TUNNEL_RCVPKTS TUNNEL_RCVBYTES
VPKTS
TUNNEL_REVERSE_RCVB
TUNNEL_RX_BPS TUNNEL_RX_PPS
YTES
TUNNEL_REVERSE_RX_B TUNNEL_REVERSE_RX_
PS PPS
Table 5-109 PW
PW_RCVPKTS PW_RCVBYTES PW_DROPPKTS
PW_RX_BPS PW_RX_PPS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1004
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-110 MPLS-TP OAM
MPLS_TUNNEL_FLR MPLS_TUNNEL_FL MPLS_TUNNEL_FLR_N
MPLS_TUNNEL_FL_N MPLS_TUNNEL_FD MPLS_TUNNEL_FDV
MPLS_PW_FLR MPLS_PW_FL MPLS_PW_FLR_N
MPLS_PW_FL_N MPLS_PW_FD MPLS_PW_FDV
Table 5-111 ETH OAM 802.1ag
ETH_CFM_FLR ETH_CFM_FL ETH_CFM_FD
ETH_CFM_FDV
Table 5-112 QoS
QOS_CARGRNPKTS QOS_CARYLWPKTS QOS_CARREDPKTS
QOS_CARREDRATIO
PEX1
Table 5-113 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Table 5-114 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1005
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-115 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
PEG1
Table 5-116 Statistics of RMON basic performance
RXOCTETS RXPKTS RXBRDCAST
RXMULCAST ETHCOL ETHDROP
ETHUNDER ETHOVER ETHFRG
ETHJAB
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1006
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Table 5-117 Statistics of RMON extended performance
RXUNICAST TXUNICAST TXBRDCAST
RXPAUSE TXPAUSE RXBGOOD
RXGOODFULLFRAME- TXGOODFULLFRAME-
TXBGOOD
SPEED SPEED
RXFULLBGOOD TXFULLBGOOD TXMULCAST
TXPKTS RX_DROP_RATIO TX_DROP_RATIO
TXOCTETS RXBPS TXBPS
RXPPS TXPPS RXBBAD
ETHLATECOL ETHEXCCOL TXDEFFRM
PORT_RX_BW_UTILIZAT PORT_TX_BW_UTILIZA
ETHFCS
ION TION
PKT64 PKT65 PKT128
PKT256 PKT512 PKT1024
RXBRDCAST_RATIO TXBRDCAST_RATIO
Table 5-118 QoS
QOS_PORTCAR_MarkedRe QOS_PORTCAR_MarkedY QOS_PORTCAR_Marked
dPKTS ellowPKTS GreenPKTS
QOS_PORTSTRM_RCV
QOS_PRI_DROPPKTS QOS_PRI_DROPBYTES
MATCHPKTS
QOS_PORTSTRM_SNDMA QOS_PORTSTRM_RX_PP QOS_PORTSTRM_TX_P
TCHPKTS S PS
DS_CVLANPRI_PKTS DS_CVLANPRI_BYTES DS_SVLANPRI_PKTS
DS_SVLANPRI_BYTES DS_DSCP_PKTS DS_DSCP_BYTES
PORT_PRI_SNDPKTS PORT_PRI_SNDBYTES PORT_PRI_TX_BPS
PORTSTRM_SHAPING_D PORTSTRM_SHAPING_
PORT_PRI_TX_PPS
ROPPKTS DROPRATIO
QOS_PORTCAR_MarkedRe QOS_PORTQUEUE_DRO
dRATIO PRATIO
5.6 RMON Event of the Ethernet Service Description
Ethernet service performance events indicate the transmission quality of the Ethernet services.
This topic lists the main RMON events in the packet domain.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1007
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
The current performance statistics of an RMON performance item are the count of
performance events within the current sampling period (which is usually a few seconds). The
historical performance statistics of an RMON performance item are calculated using the
corresponding method based on counts in sampling periods within a specific statistical period.
Table 5-119 lists calculation methods for historical performance statistics.
Table 5-119 Classification of performance Counting Methods
Performance Calculation Method
Counting Method
Accumulated value Accumulates the counts in all sampling periods within a
statistical period and takes the accumulated value as the
historical performance count.
Maximum value Takes the maximum value among counts in all sampling
obtained among all periods within a statistical period as the historical performance
sampling periods count.
Minimum value Takes the minimum value among counts in all sampling periods
obtained among all within a statistical period as the historical performance count.
sampling periods
Value obtained in the Takes the count of the last sampling period within a statistical
last sampling period period as the historical performance count.
Average value of counts Takes the average value of counts in all sampling periods
in all sampling periods within a statistical period as the historical performance count.
NOTE
l The names of RMON performance entries may vary with the version of the NMS.
l Performance count: indicates the accumulated statistical value of a specific RMON performance
event.
l Threshold unit: indicates the statistical value of a specific RMON performance event obtained
within a unit time.
5.6.1 CES Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
CES_JTROVR Count of jitter buffer overflow times times(times/s) Accumulate
d value
CES_JTRUDR Count of jitter buffer underflow times times(times/s) Accumulate
d value
CES_LOSPKT Count of lost packets packets(packet Accumulate
S s/s) d value
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1008
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
CES_MALPKT Count of malformed packets packets(packet Accumulate
S s/s) d value
CES_MISORD Count of lost packets due to the out-of- packets(packet Accumulate
ERPKTS order condition s/s) d value
CES_RX_PKT Count of received packets packets(packet Accumulate
S s/s) d value
CES_STRAYP Count of misconnected packets packets(packet Accumulate
KTS s/s) d value
CES_TX_PKTS Count of transmitted packets packets(packet Accumulate
s/s) d value
PW_RCVPKTS Count of packets received on a PW packets(packet Accumulate
s/s) d value
PW_RCVBYT Count of bytes received on a PW Byte(Byte/s) Accumulate
ES d value
5.6.2 PPP Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
PPP_TX_PKTS Indicates the number of transmitted packets(packet Accumulate
PPP packets. s/s) d value
PPP_RX_PKTS Indicates the number of received PPP packets(packet Accumulate
packets. s/s) d value
PPP_TX_BYTE Indicates the number of bytes of Byte(Byte/s) Accumulate
S transmitted PPP packets. d value
PPP_RX_BYT Indicates the number of bytes of Byte(Byte/s) Accumulate
ES received PPP packets. d value
PPP_RX_FCSP Indicates the number of PPP packets packets(packet Accumulate
KTS that received FCS faults. s/s) d value
PPP_TX_LOSP Indicates the number of PPP packets packets(packet Accumulate
KTS dropped in the transmitting process. s/s) d value
PPP_RX_LOSP Indicates the number of PPP packets packets(packet Accumulate
KTS dropped in the receiving process. s/s) d value
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1009
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
PPP_RX_BW_ Indicates the PPP bandwidth usage in %(%) Average
UTILIZATION the receive direction. value of
counts in all
sampling
periods
PPP_TX_BW_ Indicates the PPP bandwidth usage in %(%) Average
UTILIZATION the transmit direction. value of
counts in all
sampling
periods
5.6.3 ML-PPP Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
MP_TX_PKTS Indicates the number of transmitted packets(packet Accumulate
MP packets. s/s) d value
MP_RX_PKTS Indicates the number of received MP packets(packet Accumulate
packets. s/s) d value
MP_TX_BYTE Indicates the number of bytes of Byte(Byte/s) Accumulate
S transmitted MP packets. d value
MP_RX_BYTE Indicates the number of bytes of Byte(Byte/s) Accumulate
S received MP packets. d value
MP_RX_ERRP Indicates the number of received packets(packet Accumulate
KTS errored MP packets. s/s) d value
MP_TX_TOTA Indicates the total number of packets(packet Accumulate
LPKTS transmitted MP packets. s/s) d value
MP_RX_TOTA Indicates the total number of received packets(packet Accumulate
LPKTS MP packets. s/s) d value
MP_RX_BW_ Indicates the MP bandwidth usage in %(%) Average
UTILIZATION the receive direction. value of
counts in all
sampling
periods
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1010
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
MP_TX_BW_U Indicates the MP bandwidth usage in %(%) Average
TILIZATION the transmit direction. value of
counts in all
sampling
periods
5.6.4 L2VPN Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
VUNI_RCVPK Count of packets received at a V-UNI packets(packet Accumulate
TS s/s) d value
VUNI_RCVBY Count of bytes received at a V-UNI Byte(Byte/s) Accumulate
TES d value
VLAN_RCVPK Count of packets received by a VLAN packets(packet Accumulate
TS of a V-UNI s/s) d value
VLAN_RCVB Count of bytes received by a VLAN of Byte(Byte/s) Accumulate
YTES a V-UNI d value
VLAN_RX_BP Bits per second received match some Bit/s(Bit/s) Value
S VLAN ID at the specified V-UNI of obtained in
the specified service (Bits per second = the last
Number of received bytes x 8/ sampling
Monitoring Period) period
VLAN_RX_PP Packets per second received match packets/ Value
S some VLAN ID at the specified V-UNI s(packets/s) obtained in
of the specified service (Packets per the last
second = Number of received packets/ sampling
Monitoring Period) period
VUNI_SNDPK Count of packets transmitted at a V- packets(packet Accumulate
TS UNI s/s) d value
VUNI_SNDBY Count of bytes transmitted at a V-UNI Byte(Byte/s) Accumulate
TES d value
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1011
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
VUNI_TX_UTI Bandwidth utilization in the transmit %(%) Average
LIZATION direction of a V-UNI (Bandwidth value of
utilization in the transmit direction of a counts in all
V-UNI = [Number of transmitted bytes sampling
x 8/Monitoring period]/Restricted periods
bandwidth)
VUNI_SND_D Count of packets discarded in the packets(packet Accumulate
ROPPKTS transmit direction of a V-UNI due to s/s) d value
congestion (Bandwidth limit has been
specified in the transmit direction.)
VUNI_SND_D Count of bytes discarded in the Byte(Byte/s) Accumulate
ROPBYTES transmit direction of a V-UNI due to d value
congestion (Bandwidth limit has been
specified in the transmit direction.)
VUNI_SND_D Packet loss rate in the transmit %(%) Average
ROPRATIO direction of a V-UNI due to congestion value of
(Packet loss rate = Number of packets counts in all
discarded in the transmit direction of a sampling
V-UNI/Total number of packets periods
transmitted at a V-UNI)
VLAN_SNDPK Count of packets transmitted by a packets(packet Accumulate
TS VLAN of a V-UNI s/s) d value
VLAN_SNDB Count of bytes transmitted by a VLAN Byte(Byte/s) Accumulate
YTES of a V-UNI d value
VLAN_TX_BP Bits per second transmitted match Bit/s(Bit/s) Value
S some VLAN ID at the specified V-UNI obtained in
of the specified service (Bits per the last
second = Number of transmitted bytes sampling
x 8/Monitoring Period) period
VLAN_TX_PP Packets per second transmitted match packets/ Value
S some VLAN ID at the specified V-UNI s(packets/s) obtained in
of the specified service (Packets per the last
second = Number of transmitted sampling
packets/Monitoring Period) period
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1012
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.6.5 Tunnel Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
TUNNEL_RCV Count of packets received on a tunnel packets(packet Accumulate
PKTS (number of packets transmitted at the s/s) d value
specified V-NNI of the specified
service)
TUNNEL_RCV Count of bytes received on a tunnel Byte(Byte/s) Accumulate
BYTES (number of bytes transmitted at the d value
specified V-NNI of the specified
service)
TUNNEL_SND Count of packets transmitted on a packets(packet Accumulate
PKTS tunnel (number of packets received at s/s) d value
the specified V-NNI of the specified
service)
TUNNEL_SND Count of bytes transmitted on a tunnel Byte(Byte/s) Accumulate
BYTES (number of bytes received at the d value
specified V-NNI of the specified
service)
TNL_BW_UTI Tunnel bandwidth utilization %(%) Average
LISATION (Bandwidth utilization of a designated value of
tunnel = [Number of transmitted bytes counts in all
x 8/unit time]/Configured bandwidth) sampling
periods
TNL_REVERS Bandwidth utilization of a reverse %(%) Average
E_BW_UTILIS tunnel (bandwidth utilization of a value of
ATION designated transit tunnel) counts in all
sampling
periods
TUNNEL_REV Number of transmitted packets on a packets(packet Accumulate
ERSE_SNDPK reverse tunnel (number of reversely s/s) d value
TS transmitted packets on a designated bi-
directional transit tunnel)
TUNNEL_REV Number of transmitted bytes on a Byte(Byte/s) Accumulate
ERSE_SNDBY reverse tunnel (number of reversely d value
TES transmitted bytes on a designated bi-
directional transit tunnel)
TUNNEL_REV Number of received packets on a packets(packet Accumulate
ERSE_RCVPK reverse tunnel (number of reversely s/s) d value
TS received packets on a designated bi-
directional transit tunnel)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1013
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
TUNNEL_REV Number of received bytes on a reverse Byte(Byte/s) Accumulate
ERSE_RCVBY tunnel (number of reversely received d value
TES bytes on a designated bi-directional
transit tunnel)
TUNNEL_RX_ Bit rate in the receive direction of a Bit/s(Bit/s) Value
BPS tunnel (Bit rate in the receive direction obtained in
of a tunnel = [Number of received the last
bytes x 8]/Monitoring period) sampling
period
TUNNEL_TX_ Bit rate in the transmit direction of a Bit/s(Bit/s) Value
BPS tunnel (Bit rate in the transmit obtained in
direction of a tunnel = [Number of the last
transmitted bytes x 8]/Monitoring sampling
period) period
TUNNEL_RX_ Packet rate in the receive direction of a packets/ Value
PPS tunnel (Packet rate in the receive s(packets/s) obtained in
direction of a tunnel = Number of the last
received packets/Monitoring Period) sampling
period
TUNNEL_TX_ Packet rate in the transmit direction of packets/ Value
PPS a tunnel (Packet rate in the transmit s(packets/s) obtained in
direction of a tunnel = Number of the last
transmitted packets/Monitoring sampling
Period) period
TUNNEL_REV Bits per second received on the reverse Bit/s(Bit/s) Value
ERSE_RX_BPS tunnel(Bits per second received on the obtained in
reverse tunnel = Number of received the last
bytes x 8/Monitoring Period) sampling
period
TUNNEL_REV Bits per second transmitted on the Bit/s(Bit/s) Value
ERSE_TX_BPS reverse tunnel(Bits per second obtained in
transmitted on the reverse tunnel = the last
Number of transmitted bytes x 8/ sampling
Monitoring Period) period
TUNNEL_REV Packets per second of received on the packets/ Value
ERSE_RX_PPS reverse tunnel(Packets per second of s(packets/s) obtained in
received on the reverse tunnel = the last
number of received packets/ sampling
Monitoring Period) period
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1014
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
TUNNEL_REV Packets per second of transmitted on packets/ Value
ERSE_TX_PPS the reverse tunnel(Packets per second s(packets/s) obtained in
of transmitted on the reverse tunnel = the last
number of transmitted packets/ sampling
Monitoring Period) period
5.6.6 PW Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
PW_RCVPKTS Count of packets received on a PW packets(packet Accumulate
s/s) d value
PW_RCVBYT Count of bytes received on a PW Byte(Byte/s) Accumulate
ES d value
PW_SNDPKTS Count of packets transmitted on a PW packets(packet Accumulate
s/s) d value
PW_SNDBYTE Count of bytes transmitted on a PW Byte(Byte/s) Accumulate
S d value
PW_BANDWI Bandwidth utilization of a PW (PW %(%) Average
DTH_UTILISA bandwidth utilization = [Number of value of
TION transmitted bytes x 8/Monitoring counts in all
period]/Configured or actual sampling
bandwidth) periods
PW_DROPPKT Count of packets discarded on a PW packets(packet Accumulate
S s/s) d value
PW_DROPBY Count of bytes discarded on a PW Byte(Byte/s) Accumulate
TES d value
PW_RX_BPS Bit rate in the receive direction of a Bit/s(Bit/s) Value
PW (Bit rate in the receive direction of obtained in
a PW = [Number of received bytes x the last
8]/Monitoring period) sampling
period
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1015
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
PW_TX_BPS Bit rate in the transmit direction of a Bit/s(Bit/s) Value
PW (Bit rate in the transmit direction obtained in
of a PW = [Number of transmitted the last
bytes x 8]/Monitoring period) sampling
period
PW_RX_PPS Packet rate in the receive direction of a packets/ Value
PW (Packet rate in the receive s(packets/s) obtained in
direction of a PW = Number of the last
received packets/Monitoring Period) sampling
period
PW_TX_PPS Packet rate in the transmit direction of packets/ Value
a PW (Packet rate in the transmit s(packets/s) obtained in
direction of a PW = Number of the last
transmitted packets/Monitoring sampling
Period) period
5.6.7 MPLS-TP OAM Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
MPLS_TUNNE Tunnel packet loss ratio ((number of %(%) Average
L_FLR data packets transmitted at the source - value of
number of data packets received at the counts in all
sink)/number of data packets sampling
transmitted at the source) periods
MPLS_TUNNE Count of lost packets of the tunnel packets(packet Accumulate
L_FL service (number of data packets s/s) d value
transmitted at the source - number of
data packets received at the sink. This
difference is detected by the OAM
mechanism)
MPLS_TUNNE Delay of the tunnel service (time when microsecond( Value
L_FD a request packet is transmitted at the microsecond) obtained in
tunnel source - time when the response the last
packet is received at the tunnel source) sampling
period
MPLS_TUNNE Delay variation of the tunnel service
L_FDV (difference in two frame delay tests)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1016
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
MPLS_TUNNE Tunnel near packet loss ratio ((number %(%) Average
L_FLR_N of data packets transmitted at the sink - value of
number of data packets received at the counts in all
source)/number of data packets sampling
transmitted at the sink) periods
MPLS_TUNNE Count of lost near packets of the tunnel packets(packet Accumulate
L_FL_N service (number of data packets s/s) d value
transmitted at the sink - number of data
packets received at the source. This
difference is detected by the OAM
mechanism)
MPLS_PW_FL PW packet loss ratio ((number of data %(%) Average
R packets transmitted at the source - value of
number of data packets received at the counts in all
sink)/number of data packets sampling
transmitted at the source) periods
MPLS_PW_FL Count of lost packets of the PW packets(packet Accumulate
service (number of data packets s/s) d value
transmitted at the source - number of
data packets received at the sink. This
difference is detected by the OAM
mechanism)
MPLS_PW_FD Delay of the PW service (time when a microsecond( Value
request packet is transmitted at the PW microsecond) obtained in
source - time when the response packet the last
is received at the PW source). sampling
period
MPLS_PW_FD Delay variation of the PW service microsecond( Value
V (difference in two frame delay tests) microsecond) obtained in
the last
sampling
period
MPLS_PW_FL PW near packet loss ratio ((number of %(%) Average
R_N data packets transmitted at the sink - value of
number of data packets received at the counts in all
source)/number of data packets sampling
transmitted at the sink) periods
MPLS_PW_FL Count of lost near packets of the PW packets(packet Accumulate
_N service (number of data packets s/s) d value
transmitted at the sink - number of data
packets received at the source. This
difference is detected by the OAM
mechanism)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1017
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.6.8 ETH OAM Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
ETH_CFM_FL Packet loss ratio of the E-Line service %(%) Average
R value of
counts in all
sampling
periods
ETH_CFM_FL Count of lost packets of the E-Line packets(packet Accumulate
service s/s) d value
ETH_CFM_FD Delay of the E-Line service microsecond( Value
microsecond) obtained in
the last
sampling
period
ETH_CFM_FD Delay variation of the E-Line service microsecond( Value
V microsecond) obtained in
the last
sampling
period
5.6.9 QoS Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
QOS_PRI_DR Count of packets loss at PORT_COS packets(packet Accumulate
OPPKTS s/s) d value
QOS_PRI_DR Count of bytes loss at PORT_COS Byte(Byte/s) Accumulate
OPBYTES d value
QOS_STRM_M Count of packets matching the traffic packets(packet Accumulate
ATCHPKTS classification rule s/s) d value
QOS_STRM_M Byte count of packets matching the Byte(Byte/s) Accumulate
ATCHBYTES traffic classification rule d value
PORT_PRI_SN Count of packets transmitted by a packets(packet Accumulate
DPKTS priority queue at an egress port s/s) d value
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1018
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
PORT_PRI_SN Count of bytes transmitted by a Byte(Byte/s) Accumulate
DBYTES priority queue at an egress port d value
PORT_PRI_TX Bits per second transmitted matching Bit/s(Bit/s) Value
_BPS PHB service class obtained in
the last
sampling
period
PORT_PRI_TX Packets per second transmitted packets/ Value
_PPS matching PHB service class s(packets/s) obtained in
the last
sampling
period
QOS_PORTQU Packet loss rate of a priority queue at %(%) Average
EUE_DROPRA an egress port due to congestion value of
TIO counts in all
sampling
periods
FLOW_RX_UT Bandwidth utilization in the receive %(%) Average
ILIZATION direction of a flow value of
counts in all
sampling
periods
PWQUEUE_S Count of packets discarded in the packets(packet Accumulate
NDDROPPKTS transmit direction of a PW priority s/s) d value
queue due to congestion
PWQUEUE_S Count of bytes discarded in the Byte(Byte/s) Accumulate
NDDROPBYT transmit direction of a PW priority d value
ES queue due to congestion
PWQUEUE_S Packet loss rate in the transmit %(%) Average
NDDROPRATI direction of a PW priority queue due to value of
O congestion counts in all
sampling
periods
PWQUEUE_T Bits per second discarded on the PW in Bit/s(Bit/s) Value
X_BPS the Ingress direction obtained in
the last
sampling
period
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1019
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
PWQUEUE_T Packets per second discarded on the packets/ Value
X_PPS PW in the Ingress direction s(packets/s) obtained in
the last
sampling
period
TNL_SNDDRO Count of packets discarded in the packets(packet Accumulate
PPKTS transmit direction of a tunnel due to s/s) d value
congestion
TNL_SNDDRO Count of bytes discarded in the Byte(Byte/s) Accumulate
PBYTES transmit direction of a tunnel due to d value
congestion
TNL_SNDDRO Packet loss rate in the transmit %(%) Average
PRATIO direction of a tunnel due to congestion value of
counts in all
sampling
periods
TNL_REVERS Count of packets discarded in the packets(packet Accumulate
E_SNDDROPP transmit direction of a reverse tunnel s/s) d value
KTS due to congestion
TNL_REVERS Count of bytes discarded in the Byte(Byte/s) Accumulate
E_SNDDROPB transmit direction of a reverse tunnel d value
YTES due to congestion
TNL_REVERS Packet loss rate in the transmit %(%) Average
E_SNDDROPR direction of a reverse tunnel due to value of
ATIO congestion counts in all
sampling
periods
VUNIQUEUE_ Count of packets discarded in the packets(packet Accumulate
SNDDROPPKT transmit direction of a V-UNI priority s/s) d value
S queue due to congestion
VUNIQUEUE_ Count of bytes discarded in the Byte(Byte/s) Accumulate
SNDDROPBY transmit direction of a V-UNI priority d value
TES queue due to congestion
VUNIQUEUE_ Packet loss rate in the transmit %(%) Average
SNDDROPRAT direction of a V-UNI priority queue value of
IO due to congestion counts in all
sampling
periods
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1020
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
VUNIGROUP_ Count of packets discarded in the packets(packet Accumulate
SNDDROPPKT transmit direction due to congestion s/s) d value
S
VUNIGROUP_ Count of bytes discarded in the Byte(Byte/s) Accumulate
SNDDROPBY transmit direction due to congestion d value
TES
VUNIGROUP_ Packet loss rate in the transmit %(%) Average
SNDDROPRAT direction of a V-UNI group due to value of
IO congestion counts in all
sampling
periods
VUNIGROUP_ Count of packets transmitted at a V- packets(packet Accumulate
SNDPKTS UNI group s/s) d value
VUNIGROUP_ Count of bytes transmitted at a V-UNI Byte(Byte/s) Accumulate
SNDBYTES group d value
VGROUP_TX_ Bandwidth utilization in the transmit %(%) Average
UTILIZATION direction of a V-UNI group value of
counts in all
sampling
periods
QOS_PORTCA Indicates the number of red packets packets(packet Accumulate
R_MarkedRedP after traffic monitoring is enabled s/s) d value
KTS
QOS_PORTCA Indicates the number of yellow packets packets(packet Accumulate
R_MarkedYello after traffic monitoring is enabled s/s) d value
wPKTS
QOS_PORTCA Indicates the number of green packets packets(packet Accumulate
R_MarkedGree after traffic monitoring is enabled s/s) d value
nPKTS
QOS_PORTST Indicates the number of packets packets(packet Accumulate
RM_RCVMAT received in the matched flow s/s) d value
CHPKTS
QOS_PORTST Indicates the number of packets packets(packet Accumulate
RM_SNDMAT transmitted in the matched flow s/s) d value
CHPKTS
QOS_PORTST Packets per second received matching packets/ Value
RM_RX_PPS port flow classification s(packets/s) obtained in
the last
sampling
period
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1021
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
QOS_PORTST Packets per second transmitted packets/ Value
RM_TX_PPS matching port flow classification s(packets/s) obtained in
the last
sampling
period
DS_CVLANPR Indicates the number of packets with packets(packet Accumulate
I_PKTS matched C-VLAN priorities in the DS s/s) d value
domain
DS_CVLANPR Indicates the number of bytes in the Byte(Byte/s) Accumulate
I_BYTES packets with matched C-VLAN d value
priorities in the DS domain
DS_SVLANPR Indicates the number of packets with packets(packet Accumulate
I_PKTS matched S-VLAN priorities in the DS s/s) d value
domain
DS_SVLANPR Indicates the number of bytes in the Byte(Byte/s) Accumulate
I_BYTES packets with matched S-VLAN d value
priorities in the DS domain
DS_DSCP_PK Indicates the number of packets with packets(packet Accumulate
TS matched IP DSCP priorities in the DS s/s) d value
domain.
DS_DSCP_BY Indicates the number of bytes in the Byte(Byte/s) Accumulate
TES packets with matched IP DSCP d value
priorities in the DS domain.
PORTSTRM_S Indicates the number of packets packets(packet Accumulate
HAPING_DRO discarded due to network congestion s/s) d value
PPKTS when the traffic shaping function is
enabled in the egress direction
PORTSTRM_S Indicates the ratio of packet loss due to %(%) Average
HAPING_DRO network congestion when the traffic value of
PRATIO shaping function is enabled in the counts in all
egress direction sampling
periods
QOS_PORTCA Indicates the proportion of packets %(%) Average
R_MarkedRedR marked in red when the traffic policing value of
ATIO function is enabled counts in all
sampling
periods
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1022
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.6.10 ATM PWE3 Service Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
ATMPW_SND Count of transmitted cells cell(cell/s) Accumulate
CELLS d value
ATMPW_RCV Count of received cells cell(cell/s) Accumulate
CELLS d value
ATMPW_UNK Count of unknown cells cell(cell/s) Accumulate
NOWNCELLS d value
5.6.11 ATM Service Performance Event List
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
ATM_UNI1_IN Total number of normal cells received cell(cell/s) Accumulate
CELLS by the connection through UNI1 d value
ATM_UNI1_O Total number of normal cells
UTCELLS transmitted by the connection through
UNI1
ATM_UNI2_IN Total number of normal cells received
CELLS by the connection through UNI2
ATM_UNI2_O Total number of normal cells
UTCELLS transmitted by the connection through
UNI2
ATM_CORREC Count of received cells with
TED_HCSERR correctable HCS errors
ATM_UNCOR Count of received cells with
RECTED_HCS uncorrectable HCS errors
ERR
ATM_RCVCEL Count of total cells received
LS
ATM_RCVIDL Count of total idle cells received
ECELLS
ATM_SNDCEL Count of total cells transmitted
LS
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1023
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
ATM_IF_INRA Maximum rate of normal cells cell/s(cell/s) Maximum
TE_MAX received by the port value
obtained
among all
sampling
periods
ATM_IF_INRA Minimum rate of normal cells received Minimum
TE_MIN by the port value
obtained
among all
sampling
periods
ATM_IF_INRA Average rate of normal cells received Average
TE_AVG by the port value of
counts in all
sampling
periods
ATM_IF_OUT Maximum rate of normal cells Maximum
RATE_MAX transmitted by the port value
obtained
among all
sampling
periods
ATM_IF_OUT Minimum rate of normal cells Minimum
RATE_MIN transmitted by the port value
obtained
among all
sampling
periods
ATM_IF_OUT Average rate of normal cells Average
RATE_AVG transmitted by the port value of
counts in all
sampling
periods
ATM_CELL_A Percentage of valid cells %(%) Average
VAILABILITY value of
counts in all
sampling
periods
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1024
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
ATM_UNI1_IN Maximum rate of normal cells cell/s(cell/s) Maximum
RATE_MAX received by the connection through value
UNI1 obtained
among all
sampling
periods
ATM_UNI1_IN Minimum rate of normal cells received Minimum
RATE_MIN by the connection through UNI1 value
obtained
among all
sampling
periods
ATM_UNI1_IN Average rate of normal cells received Average
RATE_AVG by the connection through UNI1 value of
counts in all
sampling
periods
ATM_UNI1_O Maximum rate of normal cells Maximum
UTRATE_MA transmitted by the connection through value
X UNI1 obtained
among all
sampling
periods
ATM_UNI1_O Minimum rate of normal cells Minimum
UTRATE_MIN transmitted by the connection through value
UNI1 obtained
among all
sampling
periods
ATM_UNI1_O Average rate of normal cells Average
UTRATE_AVG transmitted by the connection through value of
UNI1 counts in all
sampling
periods
ATM_UNI2_IN Maximum rate of normal cells Maximum
RATE_MAX received by the connection through value
UNI2 obtained
among all
sampling
periods
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1025
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
ATM_UNI2_IN Minimum rate of normal cells received Minimum
RATE_MIN by the connection through UNI2 value
obtained
among all
sampling
periods
ATM_UNI2_IN Average rate of normal cells received Average
RATE_AVG by the connection through UNI2 value of
counts in all
sampling
periods
ATM_UNI2_O Maximum rate of normal cells Maximum
UTRATE_MA transmitted by the connection through value
X UNI2 obtained
among all
sampling
periods
ATM_UNI2_O Minimum rate of normal cells Minimum
UTRATE_MIN transmitted by the connection through value
UNI2 obtained
among all
sampling
periods
ATM_UNI2_O Average rate of normal cells Average
UTRATE_AVG transmitted by the connection through value of
UNI2 counts in all
sampling
periods
PORT_RX_BW Bandwidth utilization of the port in the %(%) Average
_UTILIZATIO received direction value of
N counts in all
sampling
periods
PORT_TX_BW Bandwidth utilization of the port in the %(%) Average
_UTILIZATIO transmitted direction value of
N counts in all
sampling
periods
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1026
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
5.6.12 Statistics of RMON Basic Performance (packet)
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Octets The total number of octets of data Byte(Byte/s) Accumulate
Received/ (including those in bad packets) d value
RXOCTETS received on the network (excluding
framing bits but including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
received/ bad packets, broadcast packets, and s/s) d value
RXPKTS multicast packets) received.
Broadcast The total number of good packets packets(packet Accumulate
Packets received that were directed to the s/s) d value
Received/ broadcast address. Note that this does
RXBRDCAST not include multicast packets.
Multicast The total number of good packets packets(packet Accumulate
Packets received that were directed to a s/s) d value
Received/ multicast address. Note that this
RXMULCAST number does not include packets
directed to the broadcast address.
Collisions/ The best estimate of the total number times(times/s) Accumulate
ETHCOL of collisions on this Ethernet segment. d value
Drop Events/ The total number of events in which times(times/s) Accumulate
ETHDROP packets were dropped by the probe due d value
to lack of resources. Note that this
number is not necessarily the number
of packets dropped; it is just the
number of times this condition has
been detected.
Undersized The total number of packets received packets(packet Accumulate
packets that were less than 64 octets long s/s) d value
received/ (excluding framing bits, but including
ETHUNDER FCS octets) and were otherwise well
formed.
Oversize The total number of packets received packets(packet Accumulate
packets that were longer than 1518 octets s/s) d value
received/ (excluding framing bits, but including
ETHOVER FCS octets) and were otherwise well
formed.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1027
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Fragments/ The total number of packets received packets(packet Accumulate
ETHFRG that were less than 64 octets in length s/s) d value
(excluding framing bits but including
FCS octets) and had either a bad
Frame Check Sequence (FCS)with an
integral number of octets (FCS Error)
or a bad FCS with a non-integral
number of octets (Alignment Error).
Errored The total number of packets received packets(packet Accumulate
oversize packets that were longer than 1518 octets s/s) d value
received/ (excluding framing bits, but including
ETHJAB FCS octets), and had either a bad
Frame Check Sequence (FCS) with an
integral number of octets (FCS Error)
or a bad FCS with a non-integral
number of octets (Alignment Error).
Packets (64 The total number of packets (including packets(packet Accumulate
bytes) received/ bad packets) received that were 64 s/s) d value
RXPKT64 octets in length (excluding framing bits
but including FCS octets).
Packets (65-127 The total number of packets (including packets(packet Accumulate
bytes) received/ bad packets) received that were s/s) d value
RXPKT65 between 65 and 127 octets in length
inclusive (excluding framing bits but
including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
(128-255 bytes) bad packets) received that were s/s) d value
received/ between 128 and 255 octets in length
RXPKT128 inclusive (excluding framing bits but
including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
(256-511 bytes) bad packets) received that were s/s) d value
received/ between 256 and 511 octets in length
RXPKT256 inclusive (excluding framing bits but
including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
(512-1023 bad packets) received that were s/s) d value
bytes) received/ between 512 and 1023 octets in length
RXPKT512 inclusive (excluding framing bits but
including FCS octets).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1028
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Packets The total number of packets (including packets(packet Accumulate
(1024-1518 bad packets) received that were s/s) d value
bytes) received/ between 1024 and 1518 octets in
RXPKT1024 length inclusive (excluding framing
bits but including FCS octets).
5.6.13 Statistics of RMON Extended Performance (packet)
Abbreviation Description Performance Counting
Count Unit Method
(Threshold
Unit)
Unicast The total number of good packets packets(packet Accumulated
Packets received that were directed to a s/s) value
Received/ unicast address.
RXUNICAST
Unicast The total number of packets that packets(packet Accumulated
Packets higher-level protocols requested be s/s) value
Transmitted/ transmitted, and which were not
TXUNICAST addressed to a multicast or broadcast
address at this sub-layer, including
those that were discarded or not
sent.
Broadcast The total number of packets that packets(packet Accumulated
packets higher-level protocols requested be s/s) value
transmitted / transmitted, and which were
TXBRDCAST addressed to a broadcast address at
this sub-layer, including those that
were discarded or not sent.
Pause Frames A count of MAC Control frames frames(frames/ Accumulated
Received/ received on this interface with an s) value
RXPAUSE opcode indicating the PAUSE
operation.
Pause Frames A count of MAC Control frames frames(frames/ Accumulated
Transmitted/ transmitted on this interface with an s) value
TXPAUSE opcode indicating the PAUSE
operation.
Good Octets The total number of octets of good Byte(Byte/s) Accumulated
Received/ packets received on the network value
RXBGOOD (excluding framing bits but
including FCS octets).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1029
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Description Performance Counting
Count Unit Method
(Threshold
Unit)
Good Octets The total number of octets of good Byte(Byte/s) Accumulated
Transmitted/ packets transmitted on the network value
TXBGOOD (excluding framing bits but
including FCS octets).
Good Full The rate of received octets of good kbit/s(kbit/s) Value obtained
Frame Speed packets(including framing bits and in the last
Received/ FCS octets). sampling
RXGOODFUL period
LFRAMESPE
ED
Good Full The rate of transmitted octets of kbit/s(kbit/s) Value obtained
Frame Speed good packets(including framing bits in the last
Transmitted/ and FCS octets). sampling
TXGOODFUL period
LFRAMESPE
ED
Good Full The total number of received octets Byte(Byte/s) Accumulated
Frame Octets of good packets(including framing value
Received/ bits and FCS octets).
RXFULLBGO
OD
Good Full The total number of transmited Byte(Byte/s) Accumulated
Frame Octets octets of good packets(including value
Transmitted/ framing bits and FCS octets).
TXFULLBGO
OD
Multicast The total number of packets that packets(packet Accumulated
packets higher-level protocols requested be s/s) value
transmitted/ transmitted, and which were
TXMULCAST addressed to a multicast address at
this sub-layer, including those that
were discarded or not sent. For a
MAC layer protocol, this includes
both Group and Functional
addresses.
Packets The total number of packets packets(packet Accumulated
transmitted/ (including bad packets, broadcast s/s) value
TXPKTS packets, and multicast packets)
transmitted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1030
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Description Performance Counting
Count Unit Method
(Threshold
Unit)
Packet loss rate The discarded packets ratio in the %(%) Average value
in the ingress ingress direction, that is, number of of counts in all
direction/ actually drop packets/received sampling
RX_DROP_R packets. periods
ATIO
Packet loss The discarded packets ratio in the %(%) Average value
ratio in the ingress direction, that is, number of of counts in all
egress actually drop packets/transmitted sampling
direction/ packets. periods
TX_DROP_R
ATIO
Bytes The total number of octets of data Byte(Byte/s) Accumulated
transmitted/ (including those in bad packets) value
TXOCTETS transmitted on the network
(excluding framing bits but
including FCS octets).
Received bits Received bits per second = (Number Bit/s(Bit/s) Value obtained
per second/ of received bytes x 8/Monitoring in the last
RXBPS Period) sampling
period
Received Received packets per second = packets/ Value obtained
packets per (Number of received packets/ s(packets/s) in the last
second/RXPPS Monitoring Period) sampling
period
Transmitted Transmitted bits per second = Bit/s(Bit/s) Value obtained
bits per second/ (Number of transmitted bytes x 8/ in the last
TXBPS Monitoring Period) sampling
period
Transmitted Transmitted packets per second = packets/ Value obtained
packets per (Number of transmitted packets/ s(packets/s) in the last
second/TXPPS Monitoring Period) sampling
period
Bad Octets The total number of octets of bad Byte(Byte/s) Accumulated
Received/ packets received on the network value
RXBBAD (excluding framing bits but
including FCS octets).
Late collisions/ The number of times for which a times(times/s) Accumulated
ETHLATECO collision is detected after a length of value
L more than one timeslot. A later
collision is an obvious indication
that the LAN diameter is overlarge.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1031
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Description Performance Counting
Count Unit Method
(Threshold
Unit)
Frames Indicates the frames unsuccessfully Frames Accumulated
unsuccessfully transmitted after consecutive value
transmitted collisions.
after successive
collisions/
ETHEXCCOL
Delayed A count of frames whose first frames(frames/ Accumulated
frames/ transmission is delayed because the s) value
TXDEFFRM transmission media is busy. This
count does not include collision
related frames.
FCS Errors/ A count of frames received on a frames(frames/ Accumulated
ETHFCS particular interface that are an s) value
integral number of octets in length
but do not pass the FCS check. This
count does not include frames
received with frame-too-long or
frame-too-short error.
Packets The total number of packets packets(packet Accumulated
Received (including bad packets) received that s/s) value
(1519-MTU were between 1519 and MTU octets
Octets in in length inclusive (excluding
Length)/ framing bits but including FCS
RXPKT1519 octets).
Utilization/ The percent utilization of the %(%) Average value
ETHUTILIZ ethernet segment on a scale of 0 to of counts in all
100 percent. If greater precision is sampling
desired, the Packets Received and periods
Octets Received should be sampled
before and after a common interval.
The differences in the sampled
values are Pkts and Octets,
respectively, and the number of
seconds in the interval is Interval.
Control Frames A count of MAC Control frames frames(frames/ Accumulated
Received/ received on this interface with an s) value
RXCTLPKTS opcode indicating the special
operation.
Control Frames A count of MAC Control frames frames(frames/ Accumulated
Transmitted/ transmitted on this interface with an s) value
TXCTLPKTS opcode indicating the special
operation.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1032
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Description Performance Counting
Count Unit Method
(Threshold
Unit)
Port bandwidth Port bandwidth availability %(%) Average value
availability/ of counts in all
PORT_RX_BY sampling
TES_AVAILA periods
BILITY
Received port Received port bandwidth utilization %(%) Average value
bandwidth = ((Number of received bytes x 8/ of counts in all
utilization/ Monitoring Period)/Configured or sampling
PORT_RX_B actual bandwidth) periods
W_UTILIZATI
ON
Transmitted Transmitted port bandwidth %(%) Average value
port bandwidth utilization = ((Number of of counts in all
utilization/ transmitted bytes x 8/Monitoring sampling
PORT_TX_B Period)/Configured or actual periods
W_UTILIZATI bandwidth)
ON
Broadcast Ratio of broadcast and multicast %(%) Value obtained
traffic ratio in packets to all packets in the receive in the last
the receive direction sampling
direction/ period
RXBRDCAST
_RATIO
Broadcast Ratio of broadcast and multicast %(%) Value obtained
traffic ratio in packets to all packets in the transmit in the last
the transmit direction sampling
direction/ period
TXBRDCAST
_RATIO
Packets The total number of transmitted packets(packet Accumulated
received (64 packets (including bad packets) s/s) value
bytes in whose length is between 64 bytes
length)/PKT64 (excluding framing bits, but
including FCS bytes)
Packets The total number of transmitted packets(packet Accumulated
received packets (including bad packets) s/s) value
(65-127 bytes whose length is between 65 and 127
in length)/ bytes (excluding framing bits, but
PKT65 including FCS bytes)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1033
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Abbreviation Description Performance Counting
Count Unit Method
(Threshold
Unit)
Packets The total number of transmitted packets(packet Accumulated
transmitted packets (including bad packets) s/s) value
(128-255 bytes whose length is between 128 and
in length)/ 255 bytes (excluding framing bits,
PKT128 but including FCS bytes)
Packets The total number of transmitted packets(packet Accumulated
transmitted packets (including bad packets) s/s) value
(256-511 bytes whose length is between 256 and
in length)/ 511 bytes (excluding framing bits,
PKT256 but including FCS bytes)
Packets The total number of transmitted packets(packet Accumulated
transmitted packets (including bad packets) s/s) value
(512-1023 whose length is between 512 and
bytes in 1023 bytes (excluding framing bits,
length)/ but including FCS bytes)
PKT512
Packets The total number of transmitted packets(packet Accumulated
transmitted packets (including bad packets) s/s) value
(≥1024 bytes in whose length is greater than or equal
length)/ to 1024 bytes (excluding framing
PKT1024 bits, but including FCS bytes)
5.6.14 Statistics of RMON basic performance (TDM)
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Octets The total number of octets of data Byte(Byte/s) Accumulate
Received/ (including those in bad packets) d value
RXOCTETS received on the network (excluding
framing bits but including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Received/ bad packets, broadcast packets, and s/s) d value
RXPKTS multicast packets) received.
Broadcast The total number of good packets packets(packet Accumulate
Packets received that were directed to the s/s) d value
Received/ broadcast address. Note that this does
RXBRDCAST not include multicast packets.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1034
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Multicast The total number of good packets packets(packet Accumulate
Packets received that were directed to a s/s) d value
Received/ multicast address. Note that this
RXMULCAST number does not include packets
directed to the broadcast address.
Undersize The total number of packets received packets(packet Accumulate
Packets that were less than 64 octets long s/s) d value
Received/ (excluding framing bits, but including
ETHUNDER FCS octets) and were otherwise well
formed.
Oversize The total number of packets received packets(packet Accumulate
Packets that were longer than 1518 octets s/s) d value
Received/ (excluding framing bits, but including
ETHOVER FCS octets) and were otherwise well
formed.
Fragments/ The total number of packets received packets(packet Accumulate
ETHFRG that were less than 64 octets in length s/s) d value
(excluding framing bits but including
FCS octets) and had either a bad
Frame Check Sequence (FCS)with an
integral number of octets (FCS Error)
or a bad FCS with a non-integral
number of octets (Alignment Error).
Jabbers/ The total number of packets received packets(packet Accumulate
ETHJAB that were longer than 1518 octets s/s) d value
(excluding framing bits, but including
FCS octets), and had either a bad
Frame Check Sequence (FCS) with an
integral number of octets (FCS Error)
or a bad FCS with a non-integral
number of octets (Alignment Error).
Packets The total number of packets (including packets(packet Accumulate
Received(64 bad packets) received that were 64 s/s) d value
Octets in octets in length (excluding framing bits
Length)/ but including FCS octets).
RXPKT64
Packets The total number of packets (including packets(packet Accumulate
Received(65~12 bad packets) received that were s/s) d value
7 Octets in between 65 and 127 octets in length
Length)/ inclusive (excluding framing bits but
RXPKT65 including FCS octets).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1035
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Packets The total number of packets (including packets(packet Accumulate
Received(128~2 bad packets) received that were s/s) d value
55 Octets in between 128 and 255 octets in length
Length)/ inclusive (excluding framing bits but
RXPKT128 including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Received(256~5 bad packets) received that were s/s) d value
11 Octets in between 256 and 511 octets in length
Length)/ inclusive (excluding framing bits but
RXPKT256 including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Received(512~1 bad packets) received that were s/s) d value
023 Octets in between 512 and 1023 octets in length
Length)/ inclusive (excluding framing bits but
RXPKT512 including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Received(1024~ bad packets) received that were s/s) d value
1518 Octets in between 1024 and 1518 octets in
Length)/ length inclusive (excluding framing
RXPKT1024 bits but including FCS octets).
5.6.15 Statistics of RMON extended performance (TDM)
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Control Frames A count of MAC Control frames frames(frames Accumulate
Received/ received on this interface with an /s) d value
RXCTLPKTS opcode indicating the special
operation.
Octets The total number of octets of data Byte(Byte/s) Accumulate
Transmitted/ (including those in bad packets) d value
TXOCTETS transmitted on the network (excluding
framing bits but including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Transmitted/ bad packets, broadcast packets, and s/s) d value
TXPKTS multicast packets) transmitted.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1036
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Control Frames A count of MAC Control frames frames(frames Accumulate
Transmitted/ transmitted on this interface with an /s) d value
TXCTLPKTS opcode indicating the special
operation.
Broadcast The total number of packets that packets(packet Accumulate
Packets higher-level protocols requested be s/s) d value
Transmitted/ transmitted, and which were addressed
TXBRDCAST to a broadcast address at this sub-layer,
including those that were discarded or
not sent.
Multicast The total number of packets that packets(packet Accumulate
Packets higher-level protocols requested be s/s) d value
Transmitted/ transmitted, and which were addressed
TXMULCAST to a multicast address at this sub-layer,
including those that were discarded or
not sent. For a MAC layer protocol,
this includes both Group and
Functional addresses.
Packets The total number of packets (including packets(packet Accumulate
Transmitted(64 bad packets) transmitted that were 64 s/s) d value
Octets in octets in length (excluding framing bits
Length)/ but including FCS octets).
TXPKT64
Packets The total number of packets (including packets(packet Accumulate
Transmitted(65 bad packets) transmitted that were s/s) d value
~127 Octets in between 65 and 127 octets in length
Length)/ inclusive (excluding framing bits but
TXPKT65 including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Transmitted(12 bad packets) transmitted that were s/s) d value
8~255 Octets in between 128 and 255 octets in length
Length)/ inclusive (excluding framing bits but
TXPKT128 including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Transmitted(25 bad packets) transmitted that were s/s) d value
6~511 Octets in between 256 and 511 octets in length
Length)/ inclusive (excluding framing bits but
TXPKT256 including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Transmitted(51 bad packets) transmitted that were s/s) d value
2~1023 Octets between 512 and 1023 octets in length
in Length)/ inclusive (excluding framing bits but
TXPKT512 including FCS octets).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1037
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Packets The total number of packets (including packets(packet Accumulate
Transmitted(10 bad packets) transmitted that were s/s) d value
24~1518 Octets between 1024 and 1518 octets in
in Length)/ length inclusive (excluding framing
TXPKT1024 bits but including FCS octets).
Unicast Packets The total number of good packets packets(packet Accumulate
Received/ received that were directed to a unicast s/s) d value
RXUNICAST address.
Unicast Packets The total number of packets that packets(packet Accumulate
Transmitted/ higher-level protocols requested be s/s) d value
TXUNICAST transmitted, and which were not
addressed to a multicast or broadcast
address at this sub-layer, including
those that were discarded or not sent.
Pause Frames A count of MAC Control frames frames(frames Accumulate
Received/ received on this interface with an /s) d value
RXPAUSE opcode indicating the PAUSE
operation.
Pause Frames A count of MAC Control frames frames(frames Accumulate
Transmitted/ transmitted on this interface with an /s) d value
TXPAUSE opcode indicating the PAUSE
operation.
Alignment A count of frames received on a frames(frames Accumulate
Errors/ETHALI particular interface that are not an /s) d value
integral number of octets in length and
do not pass the FCS check.
FCS Errors/ A count of frames received on a frames(frames Accumulate
ETHFCS particular interface that are an integral /s) d value
number of octets in length but do not
pass the FCS check. This count does
not include frames received with
frame-too-long or frame-too-short
error.
Packets The total number of packets (including packets(packet Accumulate
Received and bad packets) received and transmitted s/s) d value
Transmitted(64 that were 64 octets in length
Octets in (excluding framing bits but including
Length)/PKT64 FCS octets).
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1038
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Packets The total number of packets (including packets(packet Accumulate
Received and bad packets) reveived and transmitted s/s) d value
Transmitted(65 that were between 65 and 127 octets in
~127 Octets in length inclusive (excluding framing
Length)/PKT65 bits but including FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Received and bad packets) reveived and transmitted s/s) d value
Transmitted(12 that were between 128 and 255 octets
8~255 Octets in in length inclusive (excluding framing
Length)/ bits but including FCS octets).
PKT128
Packets The total number of packets (including packets(packet Accumulate
Received and bad packets) reveived and transmitted s/s) d value
Transmitted(25 that were between 256 and 511 octets
6~511 Octets in in length inclusive (excluding framing
Length)/ bits but including FCS octets).
PKT256
Packets The total number of packets (including packets(packet Accumulate
Received and bad packets) reveived and transmitted s/s) d value
Transmitted(51 that were between 512 and 1023 octets
2~1023 Octets in length inclusive (excluding framing
in Length)/ bits but including FCS octets).
PKT512
Packets The total number of packets (including packets(packet Accumulate
Received and bad packets) reveived and transmitted s/s) d value
Transmitted(10 that were between 1024 and 1518
24~1518 Octets octets in length inclusive (excluding
in Length)/ framing bits but including FCS octets).
PKT1024
Good Full The total number of transmited octets Byte(Byte/s) Accumulate
Frame Octets of good packets(including framing bits d value
Transmitted/ and FCS octets).
TXFULLBGO
OD
Good Full The total number of received octets of Byte(Byte/s) Accumulate
Frame Octets good packets(including framing bits d value
Received/ and FCS octets).
RXFULLBGO
OD
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1039
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Good Full The rate of transmitted octets of good kbit/s(kbit/s) Value
Frame Speed packets(including framing bits and obtained in
Transmitted/ FCS octets). the last
TXGOODFUL sampling
LFRAMESPEE period
D
Good Full The rate of received octets of good kbit/s(kbit/s) Value
Frame Speed packets(including framing bits and obtained in
Received/ FCS octets). the last
RXGOODFUL sampling
LFRAMESPEE period
D
Good Octets The total number of octets of good Byte(Byte/s) Accumulate
Received/ packets received on the network d value
RXBGOOD (excluding framing bits but including
(RXBOK) FCS octets).
Good Octets The total number of octets of good Byte(Byte/s) Accumulate
Transmitted/ packets transmitted on the network d value
TXBGOOD (excluding framing bits but including
(TXBOK) FCS octets).
5.6.16 Statistics of RMON VCG performance (TDM)
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Octets The total number of octets of data Byte(Byte/s) Accumulate
Received/ (including those in bad packets) d value
VCG_RXOCTE received on the VCG port (excluding
TS framing bits but including FCS octets).
Octets The total number of octets of data Byte(Byte/s) Accumulate
Transmitted/ (including those in bad packets) d value
VCG_TXOCTE transmitted on the VCG port
TS (excluding framing bits but including
FCS octets).
Packets The total number of packets (including packets(packet Accumulate
Received/ bad packets, broadcast packets, and s/s) d value
VCG_RXPACK multicast packets) received on the
ETS VCG port.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1040
OptiX OSN 500/550/580
Alarms and Performance Events Reference 5 Performance Event Reference
Name of a Description Performance Counting
Performance Count Unit Method
Entry (Threshold
Unit)
Packets The total number of packets (including packets(packet Accumulate
Transmitted/ bad packets, broadcast packets, and s/s) d value
VCG_TXPACK multicast packets) transmitted on the
ETS VCG port.
Good Packets The total number of received octets of packets(packet Accumulate
Received/ good packets on the VCG port. s/s) d value
VCG_RXGOO
DPACKETS
Good Packets The total number of transmitted octets packets(packet Accumulate
Transmitted/ of good packets on the VCG port. s/s) d value
VCG_TXGOO
DPACKETS
Full Frame The rate of octets of data (including kbit/s(kbit/s) Value
Speed those in bad packets) received on the obtained in
Received/ VCG port (excluding framing bits but the last
VCG_RXSPEE including FCS octets). sampling
D period
Full Frame The rate of octets of data (including kbit/s(kbit/s) Value
Speed those in bad packets) transmitted on obtained in
Transmitted/ the VCG port (excluding framing bits the last
VCG_TXSPEE but including FCS octets). sampling
D period
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1041
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
A Glossary
Numerics
1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)
1+1 backup A backup method in which two components mirror each other. If the active
component goes down, the standby component takes over services from the active
component to ensure that the system service is not interrupted.
1+1 hot standby A backup mode in which two systems with the same functions are deployed, one in
the active state and the other in the standby state with power on. The standby system
backs up the data of the active system automatically. Once the active system
encounters a fault, the standby system takes over services from the active system
automatically or by manual intervention.
1000BASE-T An Ethernet specification that uses the twisted pair cable with the transmission speed
as 1000 Mbit/s and the transmission distance as 100 meters.
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.
2DM two-way delay measurement
3G See Third Generation.
3R reshaping, retiming, regenerating
802.1Q in 802.1Q A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The
(QinQ) implementation of QinQ is to 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
provider's 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.
A
A/D analog/digit
AAA See Authentication, Authorization and Accounting.
AAL See ATM Adaptation Layer.
ABR See available bit rate.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1042
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
AC alternating current
ACH associated channel header
ACL See Access Control List.
ACR allowed cell rate
ADM add/drop multiplexer
ADSL See asymmetric digital subscriber line.
AF See assured forwarding.
AIS alarm indication signal
AIS insertion Insertion of AIS in a channel with excessive errors to indicate that it is unavailable.
For a line board, it can be set whether to insert AIS when there are excessive errors in
the B1, B2 and B3 bytes. For tributary board at the E1/T1 level, it can be set whether
to insert AIS when there are excessive errors in BIP-2. For tributary board at the E3
level or higher, it can be set whether to insert AIS when there are excessive errors in
the B3 byte.
ALS See automatic laser shutdown.
AMI See alternate mark inversion.
APD See avalanche photodiode.
API See application programming interface.
APID access point identifier
APS automatic protection switching
ARP See Address Resolution Protocol.
AS See autonomous system.
ASCII American Standard Code for Information Interchange
ASIC See application-specific integrated circuit.
ASON automatically switched optical network
ATD attribute discovery
ATM Adaptation An interface between higher-layer protocols and Asynchronous Transfer Mode
Layer (AAL) (ATM). The AAL provides a conversion function to and from ATM for various types
of information, including voice, video, and data.
ATPC See automatic transmit power control.
AUG See administrative unit group.
Access Control List A list of entities, together with their access rights, which are authorized to access a
(ACL) resource.
Address Resolution An Internet Protocol used to map IP addresses to MAC addresses. The ARP protocol
Protocol (ARP) enables hosts and routers to determine link layer addresses through ARP requests and
responses. The address resolution is a process by which the host converts the target IP
address into a target MAC address before transmitting a frame. The basic function of
ARP is to use the target equipment's IP address to query its MAC address.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1043
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Authentication, A mechanism for configuring authentication, authorization, and accounting security
Authorization and services. Authentication refers to the verification of user identities and the related
Accounting (AAA) network services; authorization refers to the granting of network services to users
according to authentication results; and accounting refers to the tracking of the
consumption of network services by users.
administrative unit One or more administrative units occupying fixed, defined positions in an STM
group (AUG) payload. An AUG consists of AU-4s.
aging time The time to live before an object becomes invalid.
alarm cascading The method of cascading alarm signals from several subracks or cabinets.
alarm indication A mechanism to indicate the alarm status of equipment. On the cabinet of an NE, four
differently-colored indicators specify the current status of the NE. When the green
indicator is on, the NE is powered on. When the red indicator is on, a critical alarm
has been generated. When the orange indicator is on, a major alarm has been
generated. When the yellow indicator is on, a minor alarm has been generated. The
ALM alarm indicator on the front panel of a board indicates the current status of the
board.
alarm masking A method to mask alarms for the alarm management purpose. Alarms that are masked
are not displayed on the NMS or the NMS does not monitor unimportant alarms.
alarm suppression A method to suppress alarms for the alarm management purpose. Alarms that are
suppressed are no longer reported from NEs.
alternate mark A synchronous clock encoding technique which uses bipolar pulses to represent
inversion (AMI) logical 1 values.
application An application programming interface is a particular set of rules and specifications
programming interface that are used for communication between software programs.
(API)
application-specific A special type of chip that starts out as a nonspecific collection of logic gates. Late in
integrated circuit the manufacturing process, a layer is added to connect the gates for a specific function.
(ASIC) By changing the pattern of connections, the manufacturer can make the chip suitable
for many needs.
assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
(AF) It is suitable for certain key data services that require assured bandwidth and short
delay. For traffic within the bandwidth limit, AF assures quality in forwarding. For
traffic that exceeds the bandwidth limit, AF degrades the service class and continues
to forward the traffic instead of discarding the packets.
asymmetric digital A technology for transmitting digital information at a high bandwidth on existing
subscriber line (ADSL) phone lines to homes and businesses. Unlike regular dialup phone service, ADSL
provides continuously-available, "always on" connection. ADSL is asymmetric in that
it uses most of the channel to transmit downstream to the user and only a small part to
receive information from the user. ADSL simultaneously accommodates analog
(voice) information on the same line. ADSL is generally offered at downstream data
rates from 512 kbit/s to about 6 Mbit/s.
attenuation Reduction of signal magnitude or signal loss, usually expressed in decibels.
attenuator A device used to increase the attenuation of an Optical Fiber Link. Generally used to
ensure that the signal at the receive end is not too strong.
automatic laser A technique (procedure) to automatically shutdown the output power of laser
shutdown (ALS) transmitters and optical amplifiers to avoid exposure to hazardous levels.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1044
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
automatic transmit A method of adjusting the transmit power based on fading of the transmit signal
power control (ATPC) detected at the receiver
autonomous system A network set that uses the same routing policy and is managed by the same
(AS) technology administration department. Each AS has a unique identifier that is an
integer ranging from 1 to 65535. The identifier is assigned by IANA. An AS can be
divided into areas.
available bit rate A kind of service categories defined by the ATM forum. ABR only provides possible
(ABR) forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
avalanche photodiode A semiconductor photodetector with integral detection and amplification stages.
(APD) Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
B
B-ISDN See broadband integrated services digital network.
BA booster amplifier
BA2 2 x booster amplifier
BBE background block error
BC boundary clock
BCD binary coded decimal
BDI See backward defect indication.
BE See best effort.
BEI backward error indication
BER See basic encoding rule.
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIAE backward incoming alignment error
BIOS See basic input/output system.
BIP See bit interleaved parity.
BIP-8 See bit interleaved parity-8.
BITS See building integrated timing supply.
BMC best master clock
BNC See Bayonet-Neill-Concelman.
BOM bill of materials
BPDU See bridge protocol data unit.
BPS board protection switching
BRA See basic rate access.
BRAS See broadband remote access server.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1045
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
BSC binary synchronous communication
BTS base transceiver station
BTV broadband TV
BWS backbone wavelength division multiplexing system
Bayonet-Neill- A connector used for connecting two coaxial cables.
Concelman (BNC)
Bidirectional A fast and independent hello protocol that delivers millisecond-level link failure
Forwarding Detection detection and provides carrier-class availability. After sessions are established between
(BFD) neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system
regards that the bidirectional link fails and instructs the upper layer protocol to take
actions to recover the faulty link.
backplane An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backup Process of copying data to another storage area so that it can be used to restore the
data when the source data is damaged or lost.
backward defect A function that the sink node of a LSP, when detecting a defect, uses to inform the
indication (BDI) upstream end of the LSP of a downstream defect along the return path.
basic encoding rule A rule in the syntax structure of the ASN.1, which describes how data is represented
(BER) during transmission.
basic input/output Firmware stored on the computer motherboard that contains basic input/output control
system (BIOS) programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the
computer.
basic rate access An ISDN interface typically used by smaller sites and customers. This interface
(BRA) consists of a single 16 kbit/s data (or "D") channel plus two bearer (or "B") channels
for voice and/or data. Also known as Basic Rate Access, or BRI.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of
the network and routers. The amount of resource that a diagram can use depends of the
time it reaches. BE service does not ensure any improvement in delay time, jitter,
packet loss ratio, and high reliability.
bit interleaved parity A method of error monitoring. With even parity, the transmitting equipment generates
(BIP) an X-bit code 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 forth. Even parity is generated by
setting the BIP-X bits so that an even number of 1s exist in each monitored partition
of the signal. A monitored partition comprises all bits in the same bit position within
the X-bit sequences in the covered portion of the signal. The covered portion includes
the BIP-X.
bit interleaved parity-8 Consists of a parity byte calculated bit-wise across a large number of bytes in a
(BIP-8) transmission transport frame. Divide a frame is into several blocks with 8 bits (one
byte) in a parity unit and then arrange the blocks in matrix. Compute the number of
"1" or "0" over each column. Then fill a 1 in the corresponding bit for the result if the
number is odd, otherwise fill a 0.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1046
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
bound path A parallel path with several serial paths bundled together. It improves the data
throughput capacity.
bridge protocol data Data messages exchanged across switches within an extended LAN that uses a
unit (BPDU) spanning tree protocol (STP) topology. BPDU packets contain information on ports,
addresses, priorities, and costs, and they ensure that the data reaches its intended
destination. BPDU messages are exchanged across bridges to detect loops in a
network topology. These loops are then removed by shutting down selected bridge
interfaces and placing redundant switch ports in a backup, or blocked, state.
broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as
services digital voice. It currently uses the ATM technology to transmit data over SONNET-based
network (B-ISDN) circuits at 155 to 622 Mbit/s or higher speed.
broadband remote A new type of access gateway for broadband networks. As a bridge between backbone
access server (BRAS) networks and broadband access networks, BRAS provides methods for fundamental
access and manages the broadband access network. It is deployed at the edge of
network to provide broadband access services, convergence, and forwarding of
multiple services, meeting the demands for transmission capacity and bandwidth
utilization of different users. BRAS is a core device for the broadband users' access to
a broadband network.
broadcast A means of delivering information to all members in a network. The broadcast range
is determined by the broadcast address.
building integrated In the situation of multiple synchronous nodes or communication devices, one can use
timing supply (BITS) 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.
built-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.
burst A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast
sending.
bus A path or channel for signal transmission. The typical case is that, the bus is an
electrical connection that connects one or more conductors. All devices that are
connected to a bus, can receive all transmission contents simultaneously.
C
CAC See connection admission control.
CAPEX capital expenditure
CAR committed access rate
CAS See channel associated signaling.
CAU See client automatic upgrade.
CBS See committed burst size.
CC See continuity check.
CCI connection control interface
CCITT Consultative Committee of International Telegraph and Telephone
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1047
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
CCM continuity check message
CCS See Common Channel Signaling.
CDMA2000 A 3G technology developed by Qualcomm of the US. Technology competitive with
WCDMA, upgraded from CDMA1, and developed by the GSM community as a
worldwide standard for 3G mobile.
CDVT cell delay variation tolerance
CE See customer edge.
CES See circuit emulation service.
CF compact flash
CFM connectivity fault management
CFR cell fill rate
CGMP Cisco Group Management Protocol
CIR committed information rate
CISPR International Special Committee on Radio Interference
CIST See Common and Internal Spanning Tree.
CLEI common language equipment identification
CLK clock board
CLNP connectionless network protocol
CLP See cell loss priority.
CMEP connection monitoring end point
CMI coded mark inversion
CMR cell misinsertion ratio
CPU See central processing unit.
CR Connection Request
CR-LDP Constraint-based Routed Label Distribution Protocol
CRC See cyclic redundancy check.
CRC-4 multiframe A multiframe recommended by ITU-T G.704 and set up based on the first bit of
timeslot 0. The CRC-4 multiframe is different from the CAS multiframe in principle
and implementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4
multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is a
CRC-4 check block that contains 2048 (256 x 8) bits. Bits C1 to C4 of a check block
can check the previous check block.
CSA Canadian Standards Association
CSES consecutive severely errored second
CSF Client Signal Fail
CSMA/CD See carrier sense multiple access with collision detection.
CSPF Constrained Shortest Path First
CST See common spanning tree.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1048
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
CTC common transmit clock
CTP connection termination point
CV connectivity verification
CW control word
CWDM See coarse wavelength division multiplexing.
CoS class of service
Common Channel A signaling system used in telephone networks that separates signaling information
Signaling (CCS) from user data. A specified channel is exclusively designated to carry signaling
information for all other channels in the system.
Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the
bridged local area network are simply and fully connected.
called number The number dialed by the subscriber to originate a call.
carrier sense multiple Carrier sense multiple access with collision detection (CSMA/CD) is a computer
access with collision networking access method in which:a carrier sensing scheme is used. a transmitting
detection (CSMA/CD) data station that detects another signal while transmitting a frame, stops transmitting
that frame, transmits a jam signal, and then waits for a random time interval before
trying to send that frame again.
cell loss priority (CLP) A field in the ATM cell header that determines the probability of a cell being dropped
if the network becomes congested. Cells with CLP = 0 are insured traffic, which is
unlikely to be dropped. Cells with CLP = 1 are best-effort traffic, which might be
dropped.
central processing unit The computational and control unit of a computer. The CPU is the device that
(CPU) interprets and executes instructions. The CPU has the ability to fetch, decode, and
execute instructions and to transfer information to and from other resources over the
computer's main data-transfer path, the bus.
channel associated A signaling system in which signaling information is transmitted within a dedicated
signaling (CAS) voice channel. China Signaling System No. 1 is a type of CAS signaling.
circuit emulation A function with which the E1/T1 data can be transmitted through ATM networks. At
service (CES) 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.
client automatic A function that enables a user to automatically detect the update of the client version
upgrade (CAU) and upgrade the client. This keeps the version of the client is the same as that of the
server.
coarse wavelength A signal transmission technology that multiplexes widely-spaced optical channels into
division multiplexing the same fiber. CWDM spaces wavelengths at a distance of several nm. CWDM does
(CWDM) not support optical amplifiers and is applied in short-distance chain networking.
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum burst
(CBS) IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of
an IP packet to be forwarded.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1049
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST
(CST) region is considered as a switch; therefore, the CST can be considered as their
spanning tree generated with STP/RSTP.
congestion Extra intra-network or inter-network traffic resulting in decreased network service
efficiency.
connection admission A control process in which the network takes actions in the call set-up phase (or call
control (CAC) re-negotiation phase) to determine which connection request is admitted.
continuity check (CC) An Ethernet connectivity fault management (CFM) method used to detect the
connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
cross-connection The connection of channels between the tributary board and the line board, or between
line boards inside the NE. Network services are realized through the cross-connections
of NEs.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly
connecting to the Service Provider (SP) network. A CE can be a router, switch, or
host.
cyclic redundancy A procedure used to check for errors in data transmission. CRC error checking uses a
check (CRC) complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the
transmission is considered to be error free. This procedure is known as a redundancy
check because each transmission includes not only data but extra (redundant) error-
checking values.
D
D/A digital-analog converter
DAPI destination access point identifier
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common A power system, in which the BGND of the DC return conductor is short-circuited
(with ground) (DC-C) with the PGND on the output side of the power supply cabinet and also on the line
between the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited
ground) (DC-I) with the PGND on the output side of the power supply cabinet and is isolated from the
PGND on the line between the output of the power supply cabinet and the electric
equipment.
DCD data carrier detect
DCE See data circuit-terminating equipment.
DCF data communication function
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1050
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
DDN See digital data network.
DHCP See Dynamic Host Configuration Protocol.
DIP switch dual in-line package switch
DLAG See distributed link aggregation group.
DM See delay measurement.
DMM delay measurement message
DMR delay measurement reply
DNI dual node interconnection
DRDB dynamic random database
DRR dynamic rate repartitioning
DRZ differential phase return to zero
DSCP See differentiated services code point.
DSLAM See digital subscriber line access multiplexer.
DSP digital signal processing
DSR data set ready
DSS door status switch
DTE See data terminal equipment.
DTMF See dual tone multiple frequency.
DTR data terminal ready
DVB See digital video broadcasting.
DVB-ASI digital video broadcast-asynchronous serial interface
DVMRP See Distance Vector Multicast Routing Protocol.
DWDM See dense wavelength division multiplexing.
DiffServ See differentiated service.
Distance Vector An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
Multicast Routing implements a typical dense mode IP multicast solution and uses IGMP to exchange
Protocol (DVMRP) routing datagrams with its neighbors.
Dynamic Host A client-server networking protocol. A DHCP server provides configuration
Configuration Protocol parameters specific to the DHCP client host requesting information the host requires
(DHCP) to participate on the Internet network. DHCP also provides a mechanism for allocating
IP addresses to hosts.
data circuit- The equipment that provides the signal conversion and coding between the data
terminating equipment terminal equipment (DTE) and the line. A DCE is located at a data station. The DCE
(DCE) may be separate equipment, or an integral part of the DTE or intermediate equipment.
The DCE may perform other functions that are normally performed at the network end
of the line.
data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1051
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
data terminal A user device composing the UNI. The DTE accesses the data network through the
equipment (DTE) DCE equipment (for example, a modem) and usually uses the clock signals produced
by DCE.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a source
(DM) 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.
dense wavelength The technology that utilizes the characteristics of broad bandwidth and low
division multiplexing attenuation of single mode optical fiber, employs multiple wavelengths with specific
(DWDM) frequency spacing as carriers, and allows multiple channels to transmit simultaneously
in the same fiber.
differentiated service An IETF standard that defines a mechanism for controlling and forwarding traffic in a
(DiffServ) differentiated manner based on CoS settings to handle network congestion.
differentiated services According to the QoS classification standard of the Differentiated Service (Diff-Serv),
code point (DSCP) the type of services (ToS) field in the IP header consists of six most significant bits
and two currently unused bits, which are used to form codes for priority marking.
Differentiated services code point (DSCP) is the six most important bits in the ToS. It
is the combination of IP precedence and types of service. The DSCP value is used to
ensure that routers supporting only IP precedence can be used because the DSCP
value is compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB).
Therefore, terminal devices can identify traffic using the DSCP value.
digital data network A data transmission network that is designed to transmit data on digital channels (such
(DDN) as the fiber channel, digital microwave channel, or satellite channel).
digital subscriber line A network device, usually situated in the main office of a telephone company, that
access multiplexer receives signals from multiple customer Digital Subscriber Line (DSL) connections
(DSLAM) and uses multiplexing techniques to put these signals on a high-speed backbone line.
digital video A suite of internationally accepted open standards for digital television. DVB
broadcasting (DVB) standards are maintained by the DVB Project, an international industry consortium
with more than 300 members, and they are published by a Joint Technical Committee
(JTC) of European Telecommunications Standards Institute (ETSI), European
Committee for Electrotechnical Standardization (CENELEC) and European
Broadcasting Union (EBU).
dispersion The maximum error of the local clock compared with the reference clock.
dispersion A type of module that contains dispersion compensation fibers to compensate for the
compensation module dispersion of the transmitting fiber.
(DCM)
distributed link A board-level port protection technology that detects unidirectional fiber cuts and
aggregation group negotiates with the opposite port. In the case of a link down failure on a port or
(DLAG) hardware failure on a board, services are automatically switched to the slave board,
thereby achieving 1+1 protection for the inter-board ports.
downstream In an access network, the direction of transmission toward the subscriber end of the
link.A direction of message forwarding within a transaction that refers to the direction
that requests flow from the user agent client to user agent server.
dual tone multiple Multi-frequency signaling technology for telephone systems. According to this
frequency (DTMF) technology, standard set combinations of two specific voice band frequencies, one
from a group of four low frequencies and the other from a group of four high
frequencies, are used.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1052
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
E
E-Aggr See Ethernet aggregation.
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
E-Tree See Ethernet-tree.
E2E end to end
EBS See excess burst size.
ECC See embedded control channel.
EDFA See erbium-doped fiber amplifier.
EEC Ethernet Electric Interface PMC Card
EEPROM See electrically erasable programmable read-only memory.
EF See expedited forwarding.
EFCI explicit forward congestion indication
EFM Ethernet in the First Mile
EFM OAM Ethernet in the first mile OAM
EIA See Electronic Industries Alliance.
EIR See excess information rate.
EMC See electromagnetic compatibility.
EPD early packet discard
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPON See Ethernet passive optical network.
ERPS Ethernet ring protection switching
ESC See electric supervisory channel.
ESCON See enterprise system connection.
ESD electrostatic discharge
ESN See equipment serial number.
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
EXP See experimental bits.
Electronic Industries An association based in Washington, D.C., with members from various electronics
Alliance (EIA) manufacturers. It sets standards for electronic components. RS-232-C, for example, is
the EIA standard for connecting serial components.
EoD See Ethernet over dual domains.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1053
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Ethernet A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable
and easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s,
1000 Mbit/s, or 10,000 Mbit/s.
Ethernet aggregation A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
(E-Aggr) connection).
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
network (E-LAN) virtual connection).
Ethernet over dual A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet
domains (EoD) service transmission across PSN and TDM networks.
Ethernet passive An Ethernet Passive Optical Network (EPON) is a passive optical network based on
optical network Ethernet. It is a new generation broadband access technology that uses a point-to-
(EPON) multipoint structure and passive fiber transmission. It supports upstream/downstream
symmetrical rates of 1.25 Gbit/s and a reach distance of up to 20 km. In the
downstream direction, the bandwidth is shared based on encrypted broadcast
transmission for different users. In the upstream direction, the bandwidth is shared
based on TDM. EPON meets the requirements for high bandwidth.
Ethernet private LAN A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
service (EPLAN) networks. This service is carried over dedicated bandwidth between multipoint-to-
multipoint connections.
Ethernet private line A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
(EPL) networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private LAN service networks. This service is carried over shared bandwidth between multipoint-to-
(EVPLAN) multipoint connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private line (EVPL) networks. This service is carried over shared bandwidth between point-to-point
connections.
Ethernet-tree (E-Tree) An Ethernet service type that is based on a Point-to-multipoint Ethernet virtual
connection.
European ETSI is a multinational standardization body with regulatory and standardization
Telecommunications authority over much of Europe. GSM standardization took place under the auspices of
Standards Institute ETSI.
(ETSI)
Expires A header field of the SIP message. It specifies the duration after which the message or
message content expires.
eSFP enhanced small form-factor pluggable
egress The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory A technology that implements communication among all the nodes and transmission
channel (ESC) of monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1054
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
electrically erasable A type of EPROM that can be erased with an electrical signal. It is useful for stable
programmable read- storage for long periods without electricity while still allowing reprograming.
only memory EEPROMs contain less memory than RAM, take longer to reprogram, and can be
(EEPROM) reprogramed only a limited number of times before wearing out.
electromagnetic A condition which prevails when telecommunications equipment is performing its
compatibility (EMC) individually designed function in a common electromagnetic environment without
causing or suffering unacceptable degradation due to unintentional electromagnetic
interference to or from other equipment in the same environment.
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer
channel (ECC) to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
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.
encryption A function used to transform data so as to hide its information content to prevent it's
unauthorized use.
enterprise system A path protocol that connects the host to various control units in a storage system.
connection (ESCON) Enterprise system connection is a serial bit stream transmission protocol that operates
a rate of 200 Mbit/s.
equipment serial A string of characters that identify a piece of equipment and ensures correct allocation
number (ESN) of a license file to the specified equipment. It is also called "equipment fingerprint".
erbium-doped fiber An optical device that amplifies optical signals. This device uses a short optical fiber
amplifier (EDFA) doped with the rare-earth element, Erbium. The signal to be amplified and a pump
laser are multiplexed into the doped fiber, and the signal is amplified by interacting
with doping ions. When the amplifier passes an external light source pump, it
amplifies the optical signals in a specific wavelength range.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode,
traffic control is achieved by token buckets C and E. The excess burst size parameter
defines the capacity of token bucket E, that is, the maximum burst IP packet size when
the information is transferred at the committed information rate. This parameter must
be greater than 0 but should be not less than the maximum length of an IP packet to be
forwarded.
excess information rate The bandwidth for excessive or burst traffic above the CIR; it equals the result of the
(EIR) actual transmission rate without the safety rate.
exercise switching An operation to check whether the protection switching protocol functions properly.
The protection switching is not really performed.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
(EF) demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
experimental bits A field in the MPLS packet header, three bits long. This field is always used to
(EXP) identify the CoS of the MPLS packet.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1055
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
F
FAS frame alignment signal
FC See Fibre Channel.
FCC Federal Communications Commission
FCS frame check sequence
FDD See frequency division duplex.
FDDI See fiber distributed data interface.
FDI See forward defect indication.
FDI packet See forward defect indication packet.
FDV See frame delay variation.
FE fast Ethernet
FEC See forward error correction.
FFD fast failure detection
FIB See forwarding information base.
FICON See Fibre Connect.
FIFO See first in first out.
FLR See frame loss ratio.
FPGA See field programmable gate array.
FPS See fast protection switching.
FR See frame relay.
FRR See fast reroute.
FRU See field replaceable unit.
FTN FEC to NHLFE
FTP File Transfer Protocol
Fibre Channel (FC) A high-speed transport technology used to build SANs. FC is primarily used for
transporting SCSI traffic from servers to disk arrays, but it can also be used on
networks carrying ATM and IP traffic. FC supports single-mode and multi-mode fiber
connections, and can run on twisted-pair copper wires and coaxial cables. FC provides
both connection-oriented and connectionless services.
Fibre Connect A new generation connection protocol that connects the host to various control units.
(FICON) It carries a single byte command protocol through the physical path of fibre channel,
and provides a higher transmission rate and better performance than ESCON.
fast protection A type of pseudo wire automatic protection switching (PW APS). When the working
switching (FPS) PW is faulty, the source transmits services to the protection PW and the sink receives
the services from the protection PW. FPS generally works with the interworking
function (IWF) to provide end-to-end protection for services.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1056
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
fast reroute (FRR) A technology which provides a temporary protection of link availability when part of
a network fails. The protocol enables the creation of a standby route or path for an
active route or path. When the active route is unavailable, the traffic on the active
route can be switched to the standby route. When the active route is recovered, the
traffic can be switched back to the active route. FRR is categorized into IP FRR, VPN
FRR, and TE FRR.
fault alarm A type of alarm caused by hardware and/or software faults, for example, board failure,
or by the exception that occurs in major functions. After handling, a fault alarm can be
cleared, upon which the NE reports a recovery alarm. Fault alarms are of higher
severity than event alarms.
fiber distributed data A standard developed by the American National Standards Institute (ANSI) for high-
interface (FDDI) speed fiber-optic LANs. FDDI provides specifications for transmission rates of 100
megabits per second on token ring networks.
field programmable A semi-customized circuit that is used in the Application Specific Integrated Circuit
gate array (FPGA) (ASIC) field and developed based on programmable components. FPGA remedies
many of the deficiencies of customized circuits, and allows the use of many more gate
arrays.
field replaceable unit A unit or component of a system that is designed to be replaced in the field, i.e.,
(FRU) without returning the system to a factory or repair depot.Field replaceable units may
either be customer-replaceable or their replacement may require trained service
personnel.
firewall A security system consisting of a combination of hardware and software that limits the
exposure of a computer or computer network to attack from crackers; commonly used
on local area networks that are connected to the internet. Firewalls can be
implemented in either hardware or software, or a combination of both.
first in first out (FIFO) A stack management method in which data that is stored first in a queue is also read
and invoked first.
forced switching The action of switching traffic signals between a working channel and protection
channel. The switching occurs even if the channel to which traffic is being switched is
faulty or an equal or higher priority switching command is in effect.
forward defect A packet generated and traced forward to the sink node of the LSP by the node that
indication (FDI) first detects defects. It includes fields to indicate the nature of the defect and its
location. Its primary purpose is to suppress alarms being raised at affected higher level
client LSPs and (in turn) their client layers.
forward defect A packet that responds to the detected failure event. It is used to suppress alarms of
indication packet (FDI the upper layer network where failure has occurred.
packet)
forward error A bit error correction technology that adds correction information to the payload at the
correction (FEC) transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
forwarding A table that provides information for network hardware (bridges and routers) for them
information base (FIB) to forward data packets to other networks. The information contained in a routing
table differs according to whether it is used by a bridge or a router. A bridge relies on
both the source (originating) and destination addresses to determine where and how to
forward a packet.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1057
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
frame delay variation A measurement of the variations in the frame delay between a pair of service frames,
(FDV) where the service frames belong to the same CoS instance on a point to point ETH
connection.
frame loss ratio (FLR) 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.
frame relay (FR) A packet-switching protocol used for WANs. Frame relay transmits variable-length
packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the sake
of speed.
frequency division An application in which channels are divided by frequency. In an FDD system, the
duplex (FDD) uplink and downlink use different frequencies. Downlink data is sent through bursts.
Both uplink and downlink transmission use frames with fixed time length.
fuse A safety device that protects an electric circuit from excessive current, consisting of or
containing a metal element that melts when current exceeds a specific amperage,
thereby opening the circuit.
G
G-ACH generic associated channel header
G.711 Audio codec standard (A-law or U-law) that uses pulse code modulation (PCM). Its
data rate is 64 kbit/s.
GAL generic associated channel header label
GCC general communication channel
GCP GMPLS control plan
GCRA generic cell rate algorithm
GE Gigabit Ethernet
GFC generic flow control
GFP See Generic Framing Procedure.
GMPLS generalized multiprotocol label switching
GNE See gateway network element.
GPON gigabit-capable passive optical network
GPS See Global Positioning System.
GR See graceful restart.
GRE See Generic Routing Encapsulation.
GSM See global system for mobile communications.
GUI graphical user interface
Generic Framing A framing and encapsulated method that can be applied to any data type. GFP is
Procedure (GFP) defined by ITU-T G.7041.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1058
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Generic Routing A mechanism for encapsulating any network layer protocol over any other network.
Encapsulation (GRE) GRE is used for encapsulating IP datagrams tunneled through the Internet. GRE
serves as a Layer 3 tunneling protocol and provides a tunnel for transparently
transmitting data packets.
Global Positioning A global navigation satellite system that provides reliable positioning, navigation, and
System (GPS) timing services to users worldwide.
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 network An NE that serves as a gateway for other NEs to communicate with a network
element (GNE) management system.
global system for The second-generation mobile networking standard defined by the European
mobile Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for
communications global mobile phone networks. GSM consists of three main parts: mobile switching
(GSM) subsystem (MSS), base station subsystem (BSS), and mobile station (MS).
graceful restart (GR) In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/
MPLS) such as Open Shortest Path First (OSPF), Intermediate System-Intermediate
System (IS-IS), Border Gateway Protocol (BGP), Label Distribution Protocol (LDP),
and Resource Reservation Protocol (RSVP) are extended to ensure that the forwarding
is not interrupted when the system is restarted. This reduces the flapping of the
protocols at the control plane when the system performs an active/standby switchover.
This series of standards is called graceful restart.
H
HCS higher order connection supervision
HD-SDI high definition serial digital interface
HDB3 See High Density Bipolar of Order 3.
HDTV See high-definition television.
HEC See header error control.
HPA higher order path adaptation
HPT higher order path termination
HQoS See hierarchical quality of service.
HSDPA See High Speed Downlink Packet Access.
HSI high-speed Internet
HUAWEI Electronic The software used to view, search for, and upgrade electronic documentation of
Document Explorer Huawei products. HedEx, pronounced as [hediks], has two editions, HedEx Lite and
(HedEx) HedEx Server.
HedEx See HUAWEI Electronic Document Explorer.
High Density Bipolar A code used for baseband transmissions between telecommunications devices. The
of Order 3 (HDB3) HDB3 code has the following feature: high capability of clock extraction, no direct
current component, error-checking capability, and a maximum of three consecutive
zeros.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1059
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the
Packet Access requirement for asymmetric uplink and downlink transmission of data services. It
(HSDPA) enables the maximum downlink data service rate to reach 14.4 Mbit/s without
changing the WCDMA network topology.
header error control A field within the ATM frame whose purpose is to correct any single bit error in the
(HEC) cell Header and also to detect any multi-bit errors. It actually performs a CRC check in
the first four header bits and also at the receiving end.
hierarchical quality of A type of QoS that controls the traffic of users and performs the scheduling according
service (HQoS) 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 High-definition television (HDTV) is a television system providing an image
television (HDTV) resolution that is substantially higher than that of standard-definition television.HDTV
may be transmitted in various formats:1080p: 1920×1080p: 2,073,600 pixels (~2.07
megapixels) per frame1080i: 1920×1080i: 1,036,800 pixels (~1.04 MP) per field or
2,073,600 pixels (~2.07 MP) per frame Some countries also use a non-standard CEA
resolution, such as 1440×1080i: 777,600 pixels (~0.78 MP) per field or 1,555,200
pixels (~1.56 MP) per frame720p: 1280×720p: 921,600 pixels (~0.92 MP) per
frameThe letter "p" here stands for progressive scan, while "i" indicates interlaced.
I
IAE incoming alignment error
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICC See ITU carrier code.
ICMP See Internet Control Message Protocol.
ICP IMA Control Protocol
IDU See indoor unit.
IEC International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers.
IETF Internet Engineering Task Force
IGMP See Internet Group Management Protocol.
IGP See Interior Gateway Protocol.
ILM incoming label map
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.
IP Internet Protocol
IPA See intelligent power adjustment.
IPTV See Internet Protocol television.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1060
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
ISDN Integrated Services Digital Network
ISP See Internet service provider.
IST internal spanning tree
ITC independent transmit clock
ITU See International Telecommunication Union.
ITU carrier code (ICC) A code assigned to a network operator/service provider, maintained by the ITU-T
Telecommunication Standardization Bureau (TSB).
ITU-T International Telecommunication Union-Telecommunication Standardization Sector
Institute of Electrical A professional association of electrical and electronics engineers based in the United
and Electronics States, but with membership from numerous other countries. The IEEE focuses on
Engineers (IEEE) electrical, electronics, and computer engineering, and produces many important
technology standards.
Interior Gateway A routing protocol that is used within an autonomous system. The IGP runs in small-
Protocol (IGP) sized and medium-sized networks. The IGPs are RIP, IGRP, EIGRP, OSPF, and IS-IS.
International A United Nations agency, one of the most important and influential recommendation
Telecommunication bodies, responsible for recommending standards for telecommunication (ITU-T) and
Union (ITU) radio networks (ITU-R).
Internet Assigned A department operated by the IAB. IANA delegates authority for IP address-space
Numbers Authority allocation and domain-name assignment to the NIC and other organizations. IANA
(IANA) also maintains a database of assigned protocol identifiers used in the TCP/IP suite,
including autonomous system numbers.
Internet Control A network layer protocol that provides message control and error reporting between a
Message Protocol host server and an Internet gateway.
(ICMP)
Internet Group One of the TCP/IP protocols for managing the membership of Internet Protocol
Management Protocol multicast groups. It is used by IP hosts and adjacent multicast routers to establish and
(IGMP) maintain multicast group memberships.
Internet Protocol A system that provides TV services over the IP network. In the IPTV system, media
television (IPTV) streams from satellites, terrestrial, and studios are converted by the encoder to the
media streams applicable to the IP network. Then the media streams are transmitted to
the terminal layer on the IP network. Media content is displayed on a TV set after
media streams are processed by specified receiving devices (for example, an STB).
Internet Protocol The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
version 4 (IPv4) assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers
together are used for routing, and the host number is used to address an individual host
within the network or subnetwork.
Internet Protocol An update version of IPv4, which is designed by the Internet Engineering Task Force
version 6 (IPv6) (IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits
while an IPv6 address has 128 bits.
Internet service An organization that offers users access to the Internet and related services.
provider (ISP)
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1061
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
integrated circuit (IC) A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
intelligent power A technology that reduces the optical power of all the amplifiers in an adjacent
adjustment (IPA) regeneration section in the upstream to a safe level if the system detects the loss of
optical signals on the link. IPA helps ensure that maintenance engineers are not injured
by the laser escaping from a broken fiber or a connector that is not plugged in
properly.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations,
and control system instability.
jumper A connection wire for connecting two pins.
L
L2VPN Layer 2 virtual private network
L3VPN Layer 3 virtual private network
LACP See Link Aggregation Control Protocol.
LACPDU Link Aggregation Control Protocol data unit
LAG See link aggregation group.
LAN See local area network.
LAPD link access procedure on the D channel
LAPS Link Access Protocol-SDH
LB See loopback.
LBM See loopback message.
LBR See loopback reply.
LC Lucent connector
LCAS See link capacity adjustment scheme.
LCD liquid crystal display
LCK See Locked signal function.
LCN local communication network
LCT local craft terminal
LER See label edge router.
LIFO See last in first out.
LIU logical interface unit
LLC See logical link control.
LLID local loopback ID
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1062
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
LM See loss measurement.
LMP link management protocol
LOC loss of continuity
LOM loss of multiframe
LOP loss of pointer
LOS See loss of signal.
LP lower order path
LPA lower order path adaptation
LPT link-state pass through
LSA link-state advertisement
LSR See label switching router.
LT linktrace
LTE Long Term Evolution
LTM See linktrace message.
LTR See linktrace reply.
LU line unit
LVDS See low voltage differential signal.
Layer 2 switching 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 switching.
Link Aggregation A dynamic link aggregation protocol that improves the transmission speed and
Control Protocol reliability. The two ends of the link send LACP packets to inform each other of their
(LACP) parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
Locked signal function A function administratively locks an MEG end point (MEP) at the server layer,
(LCK) informs consequential data traffic interruption to the peer MEP at the client layer, and
suppresses the alarm at the client layer.
label edge router A device that sits at the edge of an MPLS domain, that uses routing information to
(LER) assign labels to datagrams and then forwards them into the MPLS domain.
label switching router Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR
(LSR) is composed of two parts: control unit and forwarding unit. The former is responsible
for allocating the label, selecting the route, creating the label forwarding table,
creating and removing the label switch path; the latter forwards the labels according to
groups received in the label forwarding table.
last in first out (LIFO) A play mode of the voice mails, the last voice mail is played firstly.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
(LAG) aggregation group so that a MAC client can treat the link aggregation group as if it
were a single link.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1063
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
link capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
adjustment scheme control mechanism to hitless increase or decrease the capacity of a link to meet the
(LCAS) 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.
linktrace message The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.
(LTM) LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.
linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called LTR. LTR also includes the TTL that equals the result of the TTL of LTM
minus 1.
local area network A network formed by the computers and workstations within the coverage of a few
(LAN) square kilometers or within a single building, featuring high speed and low error rate.
Current LANs are generally based on switched Ethernet or Wi-Fi technology and run
at 1,000 Mbit/s (that is, 1 Gbit/s).
logical link control According to the IEEE 802 family of standards, Logical Link Control (LLC) is the
(LLC) upper sublayer of the OSI data link layer. The LLC is the same for the various
physical media (such as Ethernet, token ring, WLAN).
loopback (LB) 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.
loopback message The loopback packet sent by the node that supports 802.2ag MAC Ping to the
(LBM) destination node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.1ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the
LBM. The LBR carries the sending time of LBM, the receiving time of LBM and the
sending time of LBR.
loss measurement A method used to collect counter values applicable for ingress and egress service
(LM) frames where the counters maintain a count of transmitted and received data frames
between a pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
low voltage differential A low noise, low power, low amplitude method for high-speed (gigabits per second)
signal (LVDS) data transmission over copper wire.
M
MA maintenance association
MAC See Media Access Control.
MADM multiple add/drop multiplexer
MBB mobile broadband
MBS maximum burst size
MCF message communication function
MCR minimum cell rate
MD See maintenance domain.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1064
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
MD5 See message digest algorithm 5.
MDF See main distribution frame.
ME See maintenance entity.
MEG See maintenance entity group.
MEL maintenance entity group level
MEP maintenance association end point
MFAS See multiframe alignment signal.
MIB See management information base.
MIP maintenance association intermediate point
MLD See multicast listener discovery.
MLT mechanized loop testing
MP maintenance point
MP3 See MPEG audio layer-3.
MPEG audio layer-3 A digital audio coding scheme used in distributing recorded music over the Internet.
(MP3) MP3 shrinks the size of an audio file by a factor of 10 to 12 without seriously
degrading the quality (CD-recording level) of the sound.
MPID maintenance point identification
MPLS See Multiprotocol Label Switching.
MPLS TE multiprotocol label switching traffic engineering
MPLS TP See Multiprotocol Label Switching traffic policing.
MPLS VPN See multiprotocol label switching virtual private network.
MPLS-TP shared A protection switchover mechanism defined in the ITU-T G.8132 standard. A group
protection ring of nodes constitute a closed loop and each node is connected to two adjacent nodes
(SPRing) using a bidirectional channel. Ring network protection involves two rings that provide
protection for each other and are in opposite directions. Both of the two rings provide
working and protection channels and redundant bandwidth or network devices. In this
way, services can be automatically restored after the network does not function
properly or deteriorates.
MS multiplex section
MS-AIS See multiplex section alarm indication signal.
MS-PW See multi-segment pseudo wire.
MSA multiplex section adaptation
MSOH multiplex section overhead
MSP See multiplex section protection.
MST See multiplex section termination.
MST region See Multiple Spanning Tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1065
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
MTBF See Mean Time Between Failures.
MTTR See Mean Time to Repair.
MTU See maximum transmission unit.
MUX See multiplexer.
Mean Time Between The average time between consecutive failures of a piece of equipment. It is a measure
Failures (MTBF) of the reliability of the system.
Mean Time to Repair The average time that a device will take to recover from a failure.
(MTTR)
Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of
(MAC) the data link layer in the OSI model and is mainly responsible for controlling and
connecting the physical media at the physical layer. When transmitting data, the MAC
protocol checks whether to be able to transmit data. If the data can be transmitted,
certain control information is added to the data, and then the data and the control
information are transmitted in a specified format to the physical layer. When receiving
data, the MAC protocol checks whether the information is correct and whether the
data is transmitted correctly. If the information is correct and the data is transmitted
correctly, the control information is removed from the data and then the data is
transmitted to the LLC layer.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol (MSTP) 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.
Multiple Spanning A region that consists of switches that support the MSTP in the LAN and links among
Tree region (MST them. Switches physically and directly connected and configured with the same MST
region) region attributes belong to the same MST region.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different
Switching (MPLS) link layers, and provides connection-oriented switching for the network layer on the
basis of IP routing and control protocols.
Multiprotocol Label It is a scheme that supervises the specific traffic entering the communication devices.
Switching traffic By policing the speed of traffic that enters the network, it "punishes" the traffic out of
policing (MPLS TP) the threshold, so the traffic going into network is limited to a reasonable range,
protecting the network resources and the interests of the carriers.
main distribution A device at a central office, on which all local loops are terminated.
frame (MDF)
maintenance domain The network or the part of the network for which connectivity is managed by
(MD) connectivity fault management (CFM). The devices in a maintenance domain are
managed by a single Internet service provider (ISP).
maintenance entity An ME consists of a pair of maintenance entity group end points (MEPs), two ends of
(ME) a transport trail, and maintenance association intermediate points (MIPs) on the trail.
maintenance entity A MEG consists of MEs that meet the following criteria:1. Exist within the same
group (MEG) management edges.2. Have the same MEG hierarchy.3. Belong to the same P2P or
P2MP connection.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1066
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
management A type of database used for managing the devices in a communications network. It
information base comprises a collection of objects in a (virtual) database used to manage entities (such
(MIB) as routers and switches) in a network.
manual switching The action of manually switching traffic signals between a working channel and a
protection channel. Manual switching fails if the channel to which traffic is being
switched is faulty or an equal or higher priority switching command is in effect.
maximum The largest packet of data that can be transmitted on a network. MTU size varies,
transmission unit depending on the network-576 bytes on X.25 networks, for example, 1500 bytes on
(MTU) Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
message digest A hash function that is used in a variety of security applications to check message
algorithm 5 (MD5) integrity. MD5 processes a variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian
integers). After a series of processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
mirroring The duplication of data for backup or to distribute network traffic among several
computers with identical data.
multi-segment pseudo A collection of multiple adjacent PW segments. Each PW segment is a point-to-point
wire (MS-PW) PW. The use of MS-PWs to bear services saves tunnel resources and can transport
services over different networks.
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.
multicast listener A protocol used by an IPv6 router to discover the multicast listeners on their directly
discovery (MLD) connected network segments, and to set up and maintain member relationships. On
IPv6 networks, after MLD is configured on the receiver hosts and the multicast router
to which the hosts are directly connected, the hosts can dynamically join related
groups and the multicast router can manage members on the local network.
multiframe alignment A distinctive signal inserted into every multiframe or once into every n multiframes,
signal (MFAS) always occupying the same relative position within the multiframe, and used to
establish and maintain multiframe alignment.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a
instance (MSTI) simply and fully connected active topology for frames classified as belonging to a
VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be
assigned to multiple MSTIs.
multiplex section An all-ONES characteristic or adapted information signal. It's generated to replace the
alarm indication signal normal traffic signal when it signal contains a defect condition in order to prevent
(MS-AIS) consequential downstream failures being declared or alarms being raised. AIS can be
identified as multiplex section alarm indication signal.
multiplex section A function, which is performed to provide capability for switching a signal between
protection (MSP) and including two multiplex section termination (MST) functions, from a "working" to
a "protection" channel.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1067
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
multiplex section A function that generates the multiplex section overhead (MSOH) during the
termination (MST) formation of an SDH frame signal and that terminates the MSOH in the reverse
direction.
multiplexer (MUX) Equipment that combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate
channels being fixed.
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.
multiprotocol label An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol
switching virtual label switching (MPLS) technology. It applies the MPLS technology for network
private network routers and switches, simplifies the routing mode of core routers, and combines
(MPLS VPN) traditional routing technology and label switching technology. It can be used to
construct the broadband Intranet and Extranet to meet various service requirements.
N
NAS network access server
NDF new data flag
NE network element
NEBS Network Equipment Building System
NHLFE next hop label forwarding entry
NLP normal link pulse
NMI network maintenance interface
NNI network-to-network interface
NPC See network parameter control.
NPE network provider edge
NRT-VBR non-real-time variable bit rate
NRZ non-return to zero
NRZ code non-return-to-zero code
NRZI non-return to zero inverted
NSAP See network service access point.
NSF non-stop forwarding
NTP Network Time Protocol
NVRAM nonvolatile random access memory
network parameter During communications, UPC is implemented to monitor the actual traffic on each
control (NPC) virtual circuit that is input to the network. Once the specified parameter is exceeded,
measures will be taken to control. NPC is similar to UPC in function. The difference is
that the incoming traffic monitoring function is divided into UPC and NPC according
to their positions. UPC locates at the user/network interface, while NPC at the network
interface.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1068
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
network segment Part of a network on which all message traffic is common to all nodes; that is, a
message broadcast from one node on the segment is received by all other nodes on the
segment.
network service access A network address defined by ISO, at which the OSI Network Service is made
point (NSAP) available to a Network service user by the Network service provider.
noise figure A measure of degradation of the signal-to-noise ratio (SNR), caused by components in
a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the
output noise power of a device to the portion thereof attributable to thermal noise in
the input termination at standard noise temperature T0 (usually 290 K). The noise
figure is thus the ratio of actual output noise to that which would remain if the device
itself did not introduce noise. It is a number by which the performance of a radio
receiver can be specified.
non-GNE See non-gateway network element.
non-gateway network A network element that communicates with the NM application layer through the
element (non-GNE) gateway NE application layer.
O
O&M operation and maintenance
OA optical amplifier
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAM&P operation, administration, maintenance and provision
OAMPDU operation, administration and maintenance protocol data unit
OAMS Optical fiber line Automatic Monitoring System
OAU See optical amplifier unit.
OC ordinary clock
OCS optical core switching
OCh optical channel with full functionality
ODF optical distribution frame
ODU See outdoor unit.
ODUk optical channel data unit - k
OHP overhead processing
ONT See optical network terminal.
ONU See optical network unit.
OOF out of frame
OOS out of service
OPEX operating expense
OPS optical physical section
OPU See optical channel payload unit.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1069
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
OPUk optical channel payload unit - k
OSC See optical supervisory channel.
OSI open systems interconnection
OSN optical switch node
OSNR See optical signal-to-noise ratio.
OSPF See Open Shortest Path First.
OSPF-TE Open Shortest Path First-Traffic Engineering
OTDR See optical time domain reflectometer.
OTN optical transport network
OTS See optical transmission section.
OTU See optical transponder unit.
OTUk optical channel transport unit - k
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
First (OSPF) cost as its routing metric. A link state database is constructed of the network topology,
which is identical on all routers in the area.
offset Defines the start position of the data part to be inspected in a packet or a stream. The
value of the offset cannot be greater than the maximum stream length. Packet offset
applies to every packet in every stream; stream offset applies to the first packet of
every stream.
operation, A set of network management functions that cover fault detection, notification,
administration and location, and repair.
maintenance (OAM)
optical add/drop A device that can be used to add the optical signals of various wavelengths to one
multiplexer (OADM) channel and drop the optical signals of various wavelengths from one channel.
optical amplifier unit A board that is mainly responsible for amplifying optical signals. The OAU can be
(OAU) used in both the transmitting direction and the receiving direction.
optical attenuator A passive device that increases the attenuation in a fiber link. An optical attenuator is
used to ensure that the optical power of a signal at the receive end is not excessively
high.
optical channel A protection architecture that allows one wavelength to provide protection for
payload unit (OPU) multiple services between different stations, saving wavelength resources and
lowering costs.
optical network A device that terminates the fiber optical network at the customer premises.
terminal (ONT)
optical network unit A form of Access Node that converts optical signals transmitted via fiber to electrical
(ONU) signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise The ratio of signal power to noise power in a transmission link. OSNR is the most
ratio (OSNR) important index for measuring the performance of a DWDM system.
optical supervisory A technology that uses specific optical wavelengths to realize communication among
channel (OSC) nodes in optical transmission network and transmit the monitoring data in a certain
channel.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1070
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
optical time domain A device that sends a series of short pulses of light down a fiber-optic cable and
reflectometer (OTDR) measures the strength of the return pulses. An OTDR is used to measure fiber length
and light loss, and to locate fiber faults.
optical transmission A section in the logical structure of an optical transport network (OTN). The OTS
section (OTS) allows the network operator to perform monitoring and maintenance tasks between
NEs.
optical transponder A device or subsystem that converts accessed client signals into a G.694.1/G.694.2-
unit (OTU) compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
outdoor unit (ODU) The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for radio frequency (RF) signals.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PA power amplifier
PADR PPPoE active discovery request
PBX private branch exchange
PC personal computer
PCB See printed circuit board.
PCI See peripheral component interconnect.
PCM See pulse code modulation.
PCN product change notice
PCR See peak cell rate.
PDH See plesiochronous digital hierarchy.
PDU See power distribution unit.
PE See provider edge.
PET polyester
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.
PHB See per-hop behavior.
PHP penultimate hop popping
PIM-DM Protocol Independent Multicast - Dense Mode
PIM-SM Protocol Independent Multicast - Sparse Mode
PLL See phase-locked loop.
PM performance monitoring
PMD polarization mode dispersion
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1071
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
PMU power monitoring unit
PNNI private network-node interface
PON passive optical network
POS See packet over SDH/SONET.
POTS See plain old telephone service.
PPD partial packet discard
PPI PDH physical interface
PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PPS port protection switching
PQ See priority queuing.
PRBS See pseudo random binary sequence.
PRC primary reference clock
PSI payload structure identifier
PSN See packet switched network.
PSTN See public switched telephone network.
PSU See power supply unit.
PT payload type
PTI payload type indicator
PTN packet transport network
PTP Precision Time Protocol
PVC See permanent virtual circuit.
PVID See port VLAN ID.
PVP See permanent virtual path.
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
PWR Power Cable
PnP See plug-and-play.
packet discarding A function of discarding the packets from unknown VLAN domain or broadcast
packets. Packet Discarding is used to prevent the situation where unknown packets or
broadcast packets use the bandwidth on a link, improving the reliability of service
transmission.
packet loss The discarding of data packets in a network when a device is overloaded and cannot
accept any incoming data at a given moment.
packet over SDH/ A MAN and WAN technology that provides point-to-point data connections. The POS
SONET (POS) interface uses SDH/SONET as the physical layer protocol, and supports the transport
of packet data (such as IP packets) in MAN and WAN.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1072
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
packet per second Packet per second though the network card. Unit of data service bandwidth.
(pps)
packet switched A telecommunications network that works in packet switching mode.
network (PSN)
parity check A method for character level error detection. An extra bit is added to a string of bits,
usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd
or even parity). Both ends of a data transmission must use the same parity. When the
transmitting device frames a character, it counts the numbers of 1s in the frame and
attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity
error, may ask for the data to be retransmitted.
peak cell rate (PCR) The maximum rate at which an ATM connection can accept cells.
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
(PHB) behaviors (PHB), such as, traffic scheduling and policing. A device in the network
should select the proper PHB behaviors, based on the value of DSCP. At present, the
IETF defines four types of PHB. They are class selector (CS), expedited forwarding
(EF), assured forwarding (AF), and best-effort (BE).
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.
peripheral component A standard designed for the bus connecting the computer main board to peripheral
interconnect (PCI) devices. The PCI1.0 standard was released by Intel in 1992 and related standards have
been released by PCI-SIG since 1993. Peripheral component interconnect (PCI)
delivers I/O functionality for computers ranging from servers to workstations, PCs,
laptop PCs and mobile devices.
permanent virtual A circuit that can be established as an option to provide a dedicated circuit link
circuit (PVC) between two facilities. PVC configuration is usually preconfigured by the service
provider. Unlike SVCs, PVCs are usually very seldom broken/disconnected. A
permanent virtual circuit (PVC) is a virtual circuit established for repeated/continuous
use between the same DTE. In a PVC, the long-term association is identical to the data
transfer phase of a virtual call. Permanent virtual circuits eliminate the need for
repeated call set-up and clearing.
permanent virtual Virtual path that consists of PVCs.
path (PVP)
phase-locked loop A circuit that consists essentially of a phase detector that compares the frequency of a
(PLL) voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator. The output of the phase detector, after passing through a loop
filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with
the incoming or reference frequency.
ping test A test that is performed to send a data packet to the target IP address (a unique IP
address on the device on the network) to check whether the target host exists
according to the data packet of the same size returned from the target host.
plain old telephone The basic telephone service provided through the traditional cabling such as twisted
service (POTS) pair cables.
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the
hierarchy (PDH) minimum rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1073
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
plug-and-play (PnP) A Windows technology that automatically detects and configures most of the adapters
and peripherals that can be connected to a PC. For communication networks, fast
discovery of network topology can help the newly attached devices communicate with
the nodes on the network, without the need to configure the new devices.
point-to-point service A service between two terminal users. In P2P services, senders and recipients are
(P2P) terminal users.
port VLAN ID (PVID) A default VLAN ID of a port. It is allocated to a data frame if the data frame carries
no VLAN tag when reaching the port.
power distribution unit A unit that performs AC or DC power distribution.
(PDU)
power supply unit A unit that converts the external power input into the power supply for internal use.
(PSU) Power supply units are classified into AC power units and DC power units.
pps See packet per second.
printed circuit board A board used to mechanically support and electrically connect electronic components
(PCB) using conductive pathways, tracks, or traces, etched from copper sheets laminated
onto a non-conductive substrate.
priority queuing (PQ) A queue scheduling algorithm based on the absolute priority. According to the PQ
algorithm, services of higher priorities are ensured with greater bandwidth, lower
latency, and less jitter. Packets of lower priorities must wait to be sent till all packets
of higher priorities are sent. In this manner, services of higher priorities are processed
earlier than others.
provider edge (PE) 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.
pseudo random binary A sequence that is random in the sense that the value of each element is independent
sequence (PRBS) of the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW) 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 wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of
edge-to-edge (PWE3) a 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.
public switched A telecommunications network established to perform telephone services for the
telephone network public subscribers. Sometimes it is called POTS.
(PSTN)
pulse code modulation A method of encoding information in a signal by changing the amplitude of pulses.
(PCM) Unlike pulse amplitude modulation (PAM), in which pulse amplitude can change
continuously, pulse code modulation limits pulse amplitudes to several predefined
values. Because the signal is discrete, or digital, rather than analog, pulse code
modulation is more immune to noise than PAM.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1074
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
QPSK See quadrature phase shift keying.
QinQ See 802.1Q in 802.1Q.
quadrature phase shift QPSK modulates two bits into each modulation symbol.
keying (QPSK)
R
RADIUS See Remote Authentication Dial In User Service.
RAI remote alarm indication
RAN See radio access network.
RDI remote defect indication
RED See random early detection.
REG See regenerator.
REI remote error indication
RFC See Requirement For Comments.
RGB red green blue
RIP See Routing Information Protocol.
RJ registered jack
RMEP remote maintenance association end point
RMON remote network monitoring
RNC See radio network controller.
ROPA See remote optical pumping amplifier.
RPR resilient packet ring
RS regenerator section
RS232 See Recommended Standard 232.
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.
RSL See received signal level.
RSOH regenerator section overhead
RSSI See received signal strength indicator.
RST regenerator section termination
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RSVP-TE See Resource Reservation Protocol-Traffic Engineering.
RTN radio transmission node
RTS request to send
RTU See remote test unit.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1075
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Rapid Spanning Tree An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
Protocol (RSTP) convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Recommended A standard that defines the electrical characteristics, timing, and meaning of signals,
Standard 232 (RS232) and the physical size and pinout of connectors.
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial In User Service access control mechanism. As a distributed server/client system, RADIUS provides
(RADIUS) the AAA function.
Requirement For A document about standards, protocols, or other information pertaining to the
Comments (RFC) operation of the Internet. The RFC, under the control of the Internet Architecture
Board (IAB), is actually issued after discussion and serves as a standard document.
RFCs can be obtained from sources such as InterNIC.
Resource Reservation A protocol that reserves resources on every node along a path. RSVP is designed for
Protocol (RSVP) an integrated services Internet.
Resource Reservation An extension to the RSVP protocol for setting up label switched paths (LSPs) in
Protocol-Traffic MPLS networks. The RSVP-TE protocol is used to establish and maintain the LSPs
Engineering (RSVP- by initiating label requests and allocating label binding messages. It also supports LSP
TE) rerouting and LSP bandwidth increasing.
RoHS restriction of the use of certain hazardous substances
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a
Protocol (RIP) route based on the smallest hop count between the source and destination. RIP is a
distance vector protocol that routinely broadcasts routing information to its
neighboring routers and is known to waste bandwidth.
radio access network The network that provides the connection between CPEs and the CN. It isolates the
(RAN) CN from wireless network.
radio network A device in a radio network subsystem that is in charge of controlling the usage and
controller (RNC) integrity of radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED) to the specified higher limit and lower limit of a queue so that global TCP
synchronization resulting from traditional tail drop can be prevented.
real-time variable bit A parameter intended for real-time applications, such as compressed voice over IP
rate (rt-VBR) (VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR),
sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source
device to transmit in bursts and at a rate that varies with time.
received signal level The signal level at a receiver input terminal.
(RSL)
received signal The received wide band power, including thermal noise and noise generated in the
strength indicator receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
(RSSI) within a specified timeslot. The reference point for the measurement shall be the
antenna. This is a value reported for the strength of a frame that has been received; it
acts much like a "volume" indicator for the transmission. The RSSI may be reported in
many different ways, but a common method is in dBm.
reference clock A stable and high-precision autonomous clock that provides frequencies as a reference
for other clocks.
regenerator (REG) A piece of equipment or device that regenerates electrical signals.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1076
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
remote optical A remote optical amplifier subsystem designed for applications where power supply
pumping amplifier and monitoring systems are unavailable. The ROPA subsystem is a power
(ROPA) compensation solution to the ultra-long distance long hop (LHP) transmission.
remote test unit (RTU) A subsystem capable of collecting, pre-processing, and sending data coming from the
field sensors to the SCU.
rt-VBR See real-time variable bit rate.
S
S-VLAN service virtual local area network
SAI service area identifier
SAN See storage area network.
SAPI source access point identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SC square connector
SCR sustainable cell rate
SD See signal degrade.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDI See serial digital interface.
SDP serious disturbance period
SEC security screening
SELT See single-ended loop test.
SELV safety extra-low voltage
SEMF synchronous equipment management function
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SFTP See Secure File Transfer Protocol.
SHDSL See single-pair high-speed digital subscriber line.
SLA See Service Level Agreement.
SLIP See Serial Line Interface Protocol.
SLM single longitudinal mode
SM section monitoring
SMB sub-miniature B
SMF See single-mode fiber.
SMSR side mode suppression ratio
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1077
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
SNC subnetwork connection
SNCMP subnetwork connection multipath protection
SNCP subnetwork connection protection
SNCTP subnetwork connection tunnel protection
SNMP See simple network management protocol.
SOH section overhead
SONET See synchronous optical network.
SPC soft permanent connection
SPI SDH physical interface
SPRing See MPLS-TP shared protection ring.
SRG See shared risk group.
SRLG shared risk link group
SSH See Secure Shell.
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
SSMB synchronization status message byte
SSRC synchronization source
SSU synchronization supply unit
STD system target decoder
STM See synchronous transport module.
STM-N Synchronous Transport Module level N
STP Spanning Tree Protocol
STelnet Secure Shell Telnet
SVC switched virtual connection
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol (SFTP)
Secure Shell (SSH) SSH is a set of network protocols for securing connections between computers, as
well as the utility suite that implements these protocols.
Secure Sockets Layer A security protocol that works at a socket layer. This layer exists between the TCP
(SSL) layer and the application layer to encrypt/decode data and authenticate concerned
entities.
Serial Line Interface A protocol that defines the framing mode over the serial line to implement
Protocol (SLIP) transmission of messages over the serial line and provide the remote host
interconnection function with a known IP address.
Service Level A service contract between a customer and a (SLA) service provider that specifies the
Agreement (SLA) forwarding service a customer should receive. A customer may be a user organization
(source domain) or another DS domain (upstream domain). A SLA may include traffic
conditioning rules which constitute a TCA in whole or in part.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1078
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Synchronization Status A message that carries the quality levels of timing signals on a synchronous timing
Message (SSM) link. SSM messages provide upstream clock information to nodes on an SDH network
or synchronization network.
serial digital interface An interface that transmits data in a single channel in sequence.
(SDI)
shared risk group A group of resources that share a common risk component whose failure can cause the
(SRG) failure of all the resources in the group.
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded
defect condition is active.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
simple network An IETF protocol for monitoring and managing systems and devices in a network.The
management protocol data being monitored and managed is defined by a MIB. The functions supported by
(SNMP) the protocol are the request and retrieval of data, the setting or writing of data, and
traps that signal the occurrence of events.
single-ended loop test An automated way of testing a DSL loop from one end of the line, providing operators
(SELT) with a method for efficiently evaluating their loop as part of their daily operational
practices.
single-mode fiber A type of optical fiber through which only one type of optical signal with a fixed wave
(SMF) length can travel at a time. The inner diameter of the single-mode fiber is less than 10
microns. This type of fiber can transmit data over a long distance.
single-pair high-speed A symmetric digital subscriber line technology developed from HDSL, SDSL, and
digital subscriber line HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
(SHDSL) terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
span The physical reach between two pieces of WDM equipment.
standard definition- Standard definition video signal transported by serial digital interface.
serial digital interface
signal (SD-SDI)
steering A protection switching mode defined in ITU-T G.8132, which is applicable to packet-
based T-MPLS ring networks and similar to SDH transoceanic multiplex section
protection (MSP). In this mode, the switching is triggered by the source and sink
nodes of a service.
storage area network A storage area network (SAN) is a dedicated network that provides access to
(SAN) consolidated, block level data storage. SANs are primarily used to make storage
devices, such as disk arrays, tape libraries, and optical jukeboxes, accessible to servers
so that the devices appear like locally attached devices to the operating system.A SAN
does not provide file abstraction, only block-level operations. However, file systems
built on top of SANs do provide file-level access, and are known as SAN filesystems
or shared disk file systems. An architecture to attach remote computer storage devices
such as disk array controllers, tape libraries and CD arrays to servers in such a way
that to the operating system the devices appear as locally attached devices.An
architecture to attach remote computer storage devices such as disk array controllers,
tape libraries and CD arrays to servers in such a way that to the operating system the
devices appear as locally attached devices.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1079
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
hierarchy (SDH) 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 B-
ISDN.
synchronous optical A high-speed network that provides a standard interface for communications carriers
network (SONET) to connect networks based on fiber optical cable. SONET is designed to handle
multiple data types (voice, video, and so on). It transmits at a base rate of 51.84
Mbit/s, but multiples of this base rate go as high as 2.488 Gbit/s.
synchronous transport An information structure used to support section layer connections in the SDH. It
module (STM) consists of information payload and Section Overhead (SOH) information fields
organized in a block frame structure which repeats every 125. The information is
suitably conditioned for serial transmission on the selected media at a rate which is
synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed
STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic
rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are
under consideration.
T
TAI tracking area identity
TC transmission convergence
TCI tag control information
TCM tandem connection monitor
TCN telecommunication network
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TD transmit degrade
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDC tunable dispersion compensator
TDD time division duplex
TDM See time division multiplexing.
TFTP See Trivial File Transfer Protocol.
TIM trail trace identifier mismatch
TL1 Transaction Language 1
TLS Transport Layer Security
TLV See type-length-value.
TM See terminal multiplexer.
TMN See telecommunications management network.
TOD time of day
TOS type of service
TPID tag protocol identifier
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1080
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
TPS See tributary protection switching.
TSD trail signal degrade
TST See Test.
TTI trail trace identifier
TTL See time to live.
TTSI See trail termination source identifier.
TU tributary unit
TUG tributary unit group
Test (TST) A function which is used to perform one-way on-demand in-service or out-of-service
diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit errors,
and so on.
Third Generation (3G) The third generation of digital wireless technology, as defined by the International
Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s
to 19.2 kbit/s offered by second generation technology.
Time Division- A 3G mobile communications standard found in UMTS mobile telecommunications
Synchronous Code networks in China as an alternative to W-CDMA. TD-SCDMA integrates technologies
Division Multiple of CDMA, TDMA, and FDMA, and makes use of technologies including intelligent
Access (TD-SCDMA) antenna, joint detection, low chip rate (LCR), and adaptive power control. With the
flexibility of service processing, a TD-SCDMA network can connect to other
networks through the RNC.
Transmission Control The protocol within TCP/IP that governs the breakup of data messages into packets to
Protocol (TCP) be sent using Internet Protocol (IP), and the reassembly and verification of the
complete messages from packets received by IP. A connection-oriented, reliable
protocol (reliable in the sense of ensuring error-free delivery), TCP corresponds to the
transport layer in the ISO/OSI reference model.
Trivial File Transfer A small and simple alternative to FTP for transferring files. TFTP is intended for
Protocol (TFTP) applications that do not need complex interactions between the client and server.
TFTP restricts operations to simple file transfers and does not provide authentication.
telecommunications A protocol model defined by ITU-T for managing open systems in a communications
management network network. TMN manages the planning, provisioning, installation, and OAM of
(TMN) equipment, networks, and services.
terminal multiplexer A device used at a network terminal either to multiplex multiple channels of low rate
(TM) signals into one channel of high rate signals, or to demultiplex one channel of high
rate signals into multiple channels of low rate signals.
threshold A limitation on an amount, scale, or level. Changes will occur when a threshold is
reached.
throughput The maximum transmission rate of the tested object (system, equipment, connection,
service type) when no packet is discarded. Throughput can be measured with
bandwidth.
throughput capability The data input/output capability of the data transmission interface.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1081
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
time division A multiplexing technology. TDM divides the sampling cycle of a channel into time
multiplexing (TDM) slots (TSn, n is equal to 0, 1, 2, 3...), and the sampling value codes of multiple signals
engross time slots in a certain order, forming multiple multiplexing digital signals to
be transmitted over one channel.
time to live (TTL) A specified period of time for best-effort delivery systems to prevent packets from
looping endlessly.
tolerance Permissible degree of variation from a pre-set standard.
traceroute A program that prints the path to a destination. Traceroute sends a sequence of
datagrams with the time-to-live (TTL) set to 1,2, and so on, and uses ICMP time
exceeded messages that return to determine routers along the path.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the
entire network. In this way, different traffic packets can be treated differently.
trail termination A TTSI uniquely identifies an LSP in the network. A TTSI is carried in the
source identifier connectivity verification (CV) packet for checking the connectivity of a trail. If it
(TTSI) matches the TTSI received by the sink point, the trail has no connectivity defect.
transmission delay The period from the time when a site starts to transmit a data frame to the time when
the site finishes the data frame transmission. It consists of the transmission latency and
the equipment forwarding latency.
tributary protection A function that uses a standby tributary processing board to protect N tributary
switching (TPS) processing boards.
type-length-value An encoding type that features high efficiency and expansibility. It is also called
(TLV) Code-Length-Value (CLV). T indicates that different types can be defined through
different values. L indicates the total length of the value field. V indicates the actual
data of the TLV and is most important. TLV encoding features high expansibility. New
TLVs can be added to support new features, which is flexible in describing
information loaded in packets.
U
UAS unavailable second
UAT See unavailable time event.
UBR+ Unspecified Bit Rate Plus
UMC See Unified Menu Center.
UMTS See Universal Mobile Telecommunications System.
UNI See user-to-network interface.
UPC See usage parameter control.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
UPS uninterruptible power supply
UTC Coordinated Universal Time
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1082
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Unified Menu Center The Unified Menu Center provides menu information for handset customers and
(UMC) collects service parameters for customer transactions.
Universal Mobile A 3G mobile technology that will deliver broadband information at speeds up to 2
Telecommunications Mbit/s. Besides voice and data, UMTS will deliver audio and video to wireless
System (UMTS) devices anywhere in the world through fixed, wireless and satellite systems.
unavailable time event An event that is reported when the monitored object generates 10 consecutive severely
(UAT) errored seconds.
unicast The process of sending data from a source to a single recipient.
upstream In an access network, the direction that is far from the subscriber end of the link.A
direction of message forwarding within a transaction that refers to the direction that
responses flow from the user agent server back to the user agent client.
usage parameter During communications, UPC is implemented to monitor the actual traffic on each
control (UPC) virtual circuit that is input to the network. Once the specified parameter is exceeded,
measures will be taken to control. NPC is similar to UPC in function. The difference is
that the incoming traffic monitoring function is divided into UPC and NPC according
to their positions. UPC locates at the user/network interface, while NPC at the network
interface.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
V-NNI virtual network-network interface
V.24 The physical layer interface specification between DTE and DCE defined by the ITU-
T. It complies with EIA/TIA-232.
V.35 The synchronous physical layer protocol defined by the ITU-T. It is used for
communication between network access devices and the packet-based network. V.35
is mainly used in America and Europe.
VB virtual bridge
VBR See variable bit rate.
VC See virtual channel.
VC trunk See virtual container trunk.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCI virtual channel identifier
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VDSL very-high-data-rate digital subscriber line
VDSL2 See very-high-speed digital subscriber line 2.
VIP very important person
VLAN virtual local area network
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1083
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
VOA variable optical attenuator
VP See virtual path.
VPI See virtual path identifier.
VPLS See virtual private LAN service.
VPN virtual private network
VPWS See virtual private wire service.
VRF VPN routing and forwarding
VRRP See Virtual Router Redundancy Protocol.
Virtual Router A protocol designed for multicast or broadcast LANs such as an Ethernet. A group of
Redundancy Protocol routers (including an active router and several backup routers) in a LAN is regarded as
(VRRP) a virtual router, which is called a backup group. The virtual router has its own IP
address. The host in the network communicates with other networks through this
virtual router. If the active router in the backup group fails, one of the backup routers
in this backup group becomes active and provides routing service for the host in the
network.
VoIP See Voice over Internet Protocol.
Voice over Internet A value-added service technology for IP calls. The VoIP service is a new IP telecom
Protocol (VoIP) service. It can run on fixed and mobile networks and support flexible access points.
Fees for VoIP subscribers are relatively low. Calls between VoIP subscribers who
belong to the same carrier are free of charge.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice
calls.
very-high-speed digital An extension of the VDSL technology, which complies with ITU G.993.2, supports
subscriber line 2 multiple spectrum profiles and encapsulation modes, and provides short-distance and
(VDSL2) high-speed access solutions to the next-generation FTTx access service.
virtual channel (VC) Any logical connection in the ATM network. A VC is the basic unit of switching in
the ATM network and is uniquely identified by a virtual path identifier (VPI)/virtual
channel identifier (VCI) value. It is the channel on which ATM cells are transmitted
by a switch.
virtual channel A VC logical trail that carries data between two end points in an ATM network. A
connection (VCC) point-to-multipoint VCC is a set of ATM virtual connections between two or multiple
end points.
virtual concatenation A group of co-located member trail termination functions that are connected to the
group (VCG) same virtual concatenation link.
virtual container trunk The logical path formed by some cascaded VCs.
(VC trunk)
virtual path (VP) A bundle of virtual channels, all of which are switched transparently across an ATM
network based on a common VPI.
virtual path identifier The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to
(VPI) which virtual path the cell belongs.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1084
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
virtual private LAN One kind of point-to-multipoint L2VPN services provided in public network, to
service (VPLS) connect isolated user sites by Metropolitan Area Network (MAN) or Wide Area
Network (WAN), which makes the connection like LAN connection. It is a Layer 2
VPN technology based on Multiprotocol Label Switching (MPLS) and Ethernet.
Through respective PE device, users in different locations can connect with each other
by accessing VPLS network. From the user's perspective, the whole VPLS network is
like a layer 2 switch network, users connect with each other like using LAN directly.
virtual private wire A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,
service (VPWS) Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.
voltage drop The voltage developed across a component or conductor by the flow of current
through the resistance or impedance of that component or conductor.
W
WAN wide area network
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WEEE waste electrical and electronic equipment
WFQ See weighted fair queuing.
WRR weighted round robin
WTR See wait to restore.
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
Wideband Code A standard defined by the ITU-T for the third-generation wireless technology derived
Division Multiple from the Code Division Multiple Access (CDMA) technology.
Access (WCDMA)
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
weighted fair queuing A fair queue scheduling algorithm based on bandwidth allocation weights. This
(WFQ) scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all
priority queues can be scheduled.
wrapping A protection switching mode defined in ITU-T G.8132, which is applicable to packet-
based T-MPLS ring networks and similar to SDH two-fiber bidirectional multiplex
section protection (MSP). In this mode, the switching is triggered by the node that
detects a failure. For details, see ITU-T G.841.
X
X.21 ITU-T standard for serial communications over synchronous digital lines. It is mainly
used in Europe and Japan.
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
XCS cross-connect and synchronous timing board
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1085
OptiX OSN 500/550/580
Alarms and Performance Events Reference A Glossary
Y
Y.1731 The OAM protocol introduced by the ITU-T. Besides the contents defined by
IEEE802.1ag, ITU-T Recommendation Y.173 also defines the following combined
OAM messages: Alarm Indication Signal (AIS), Remote Defect Indication (RDI),
Locked Signal (LCK), Test Signal, Automatic Protection Switching (APS),
Maintenance Communication Channel (MCC), Experimental (EXP), and Vendor
Specific (VSP) for fault management and performance monitoring, such as frame loss
measurement (LM), and delay measurement (DM).
Z
Z interface extension Extending the analogue subscriber to another place by extending the Z interface.
Issue 02 (2019-01-03) Copyright © Huawei Technologies Co., Ltd. 1086
También podría gustarte
- Signaling in Telecommunication NetworksDe EverandSignaling in Telecommunication NetworksCalificación: 4 de 5 estrellas4/5 (1)
- OptiX OSN 8800 6800 3800 Supporting Tasks (V100R008) PDFDocumento290 páginasOptiX OSN 8800 6800 3800 Supporting Tasks (V100R008) PDFvladAún no hay calificaciones
- OSN 8800 6800 3800 V100R011C10 Trouble Shooting 01Documento273 páginasOSN 8800 6800 3800 V100R011C10 Trouble Shooting 01Eduardo Fernández100% (1)
- OSN 8800 6800 3800 V100R009C10 Commissioning Guide 04Documento891 páginasOSN 8800 6800 3800 V100R009C10 Commissioning Guide 04Oscar Behrens ZepedaAún no hay calificaciones
- OSN 8800 6800 3800 V100R010C00 Alarms and Performance Events Reference 01Documento1526 páginasOSN 8800 6800 3800 V100R010C00 Alarms and Performance Events Reference 01Oscar Behrens ZepedaAún no hay calificaciones
- OSN 500 550 V100R007C00 Configuration Guide (Packet Transport Domain) 03Documento782 páginasOSN 500 550 V100R007C00 Configuration Guide (Packet Transport Domain) 03Derrick Senyo100% (2)
- OptiX OSN 7500Documento108 páginasOptiX OSN 7500Fek100% (1)
- OTF702301 OptiX RTN 980L Troubleshooting ISSUE 1.00Documento44 páginasOTF702301 OptiX RTN 980L Troubleshooting ISSUE 1.00krafael2Aún no hay calificaciones
- Imanager U2000 V200R014C60 Web LCT User Guide 01 PDFDocumento144 páginasImanager U2000 V200R014C60 Web LCT User Guide 01 PDFGrover David Perez HuancaAún no hay calificaciones
- 6 OptiX OSN 1500 Hardware Description ISSUE 1.30Documento128 páginas6 OptiX OSN 1500 Hardware Description ISSUE 1.30Regina PazAún no hay calificaciones
- RTN 980 V100R007C10 Product Description 02Documento257 páginasRTN 980 V100R007C10 Product Description 02Hugo Mauricio Sánchez CAún no hay calificaciones
- OSN 1800 II Enhanced Quick Installation Guide 05Documento55 páginasOSN 1800 II Enhanced Quick Installation Guide 05MD. SHEFAUL KARIMAún no hay calificaciones
- OptiX OSN 8800 T16 Quick Installation GuideDocumento74 páginasOptiX OSN 8800 T16 Quick Installation GuideBin Yussuf El-BahsanyAún no hay calificaciones
- Comission WDMDocumento107 páginasComission WDMThiago Andrade RangelAún no hay calificaciones
- RTN 950A V100R009C10 Product DescriptionDocumento265 páginasRTN 950A V100R009C10 Product DescriptionAnonymous sV02Ggn4TOAún no hay calificaciones
- Huawei OptiX Metro 1000 Commissioning Guide (V300R007)Documento143 páginasHuawei OptiX Metro 1000 Commissioning Guide (V300R007)Thunder-Link.comAún no hay calificaciones
- Huawei OptiX OSN 3500 Hardware Description (V200R012)Documento1756 páginasHuawei OptiX OSN 3500 Hardware Description (V200R012)Thunder-Link.com100% (1)
- OptiX OSN 500 Configuration ManualDocumento64 páginasOptiX OSN 500 Configuration ManualThunder-Link.com80% (10)
- Configuration in Huawei MW SyatemsDocumento18 páginasConfiguration in Huawei MW SyatemspankajengAún no hay calificaciones
- Huawei OptiX OSN 6800/3800 Optical Transponder Board ECOM DocumentDocumento26 páginasHuawei OptiX OSN 6800/3800 Optical Transponder Board ECOM DocumentThunder-Link.comAún no hay calificaciones
- Commissioning and Configuration Guide (V100R003C01 - 01)Documento382 páginasCommissioning and Configuration Guide (V100R003C01 - 01)johansenpanjaitan100% (2)
- RTN 905 1E&2E V100R007C00 Product Description 01 PDFDocumento196 páginasRTN 905 1E&2E V100R007C00 Product Description 01 PDFtv_romeo100% (3)
- 01-OptiX RTN 980 Hardware DescriptionDocumento74 páginas01-OptiX RTN 980 Hardware DescriptionPaulo Dembi75% (4)
- Optix Osn 7500 Commissioning GuideDocumento12 páginasOptix Osn 7500 Commissioning GuidenarendravsAún no hay calificaciones
- OptiX OSN 500 Configuration Guide (V100R002)Documento290 páginasOptiX OSN 500 Configuration Guide (V100R002)Thunder-Link.com100% (1)
- OSN 3500 V100&V200 Installation Guide 15Documento224 páginasOSN 3500 V100&V200 Installation Guide 15Thunder-Link.comAún no hay calificaciones
- RTN 950 Configuration Guide (Web LCT) - (V100R003C02 - 02)Documento1752 páginasRTN 950 Configuration Guide (Web LCT) - (V100R003C02 - 02)fajar mahardikaAún no hay calificaciones
- 01-03 Configuring Ethernet ServicesDocumento65 páginas01-03 Configuring Ethernet Servicesshadow267100% (2)
- RTN XMC ODU Hardware Description (V100 - 11)Documento69 páginasRTN XMC ODU Hardware Description (V100 - 11)Ahmed Elfaroug100% (1)
- RTN 905 1E&2E V100R006C10 Commissioning Guide 02. (Configure Basic) PDFDocumento180 páginasRTN 905 1E&2E V100R006C10 Commissioning Guide 02. (Configure Basic) PDFROUERN VannakAún no hay calificaciones
- How To Connect External Sensors Alarm To Huawei OSN EquipmentDocumento11 páginasHow To Connect External Sensors Alarm To Huawei OSN EquipmentThunder-Link.comAún no hay calificaciones
- Railway Operational Communication Solution OptiX OSN 1500 Product Overview (Hybrid)Documento77 páginasRailway Operational Communication Solution OptiX OSN 1500 Product Overview (Hybrid)Christopher MendesAún no hay calificaciones
- OptiX OSN 8800 6800 3800 V100R007C00 Upgrade GuideDocumento118 páginasOptiX OSN 8800 6800 3800 V100R007C00 Upgrade GuideChris BarrientosAún no hay calificaciones
- OSN 8800 TrainingDocumento30 páginasOSN 8800 TrainingProdipta Debnath100% (1)
- 03-OptiX IManager T2000 Deployment GuideDocumento61 páginas03-OptiX IManager T2000 Deployment Guidelors75Aún no hay calificaciones
- OptiX OSN 3500 Troubleshooting (V100R008)Documento223 páginasOptiX OSN 3500 Troubleshooting (V100R008)Thunder-Link.com100% (2)
- OptiX PTN 950 Packet Transport Platform Product BrochureDocumento6 páginasOptiX PTN 950 Packet Transport Platform Product BrochureJaime JaraAún no hay calificaciones
- N68E-22 Cabinet Installation Guide (01) (PDF) - enDocumento84 páginasN68E-22 Cabinet Installation Guide (01) (PDF) - enAnonymous iAYcAhAún no hay calificaciones
- OptiX PTN 960 V100R005C01 Hardware Description 02Documento228 páginasOptiX PTN 960 V100R005C01 Hardware Description 02Michael WongAún no hay calificaciones
- ATN 910&910I&910B&950B V200R003C10 Emergency Maintenance 02 (CLI)Documento39 páginasATN 910&910I&910B&950B V200R003C10 Emergency Maintenance 02 (CLI)Miky CCisAún no hay calificaciones
- Huawei OSN1800 Pre-Sale Training Slide For Agent (2012)Documento43 páginasHuawei OSN1800 Pre-Sale Training Slide For Agent (2012)azeem2012Aún no hay calificaciones
- RTN510 V100R002C00 Product OverviewDocumento13 páginasRTN510 V100R002C00 Product OverviewSinini MhlangaAún no hay calificaciones
- DBS3900 Product DescriptionDocumento50 páginasDBS3900 Product DescriptionWalid ChakrounAún no hay calificaciones
- RTN 950 IDU Hardware DescriptionDocumento915 páginasRTN 950 IDU Hardware DescriptionhekriAún no hay calificaciones
- OTC103101 OptiX BWS 1600G V100R002 Hardware Description ISSUE1 24 PDFDocumento72 páginasOTC103101 OptiX BWS 1600G V100R002 Hardware Description ISSUE1 24 PDFMarcelo Abdon Alborta AntezanaAún no hay calificaciones
- SSU - Operatind and Instruction ManuelDocumento100 páginasSSU - Operatind and Instruction ManuelLarba Sawadogo100% (1)
- OptiX OSN 7500 II Hardware DescriptionDocumento69 páginasOptiX OSN 7500 II Hardware DescriptionZizou AzzougAún no hay calificaciones
- MA5616 Configuration Guide (V800R308C01 - 04) PDFDocumento553 páginasMA5616 Configuration Guide (V800R308C01 - 04) PDFAlex Matias100% (1)
- OPtix OSN 3500 & N66T Rack Product OverviewDocumento101 páginasOPtix OSN 3500 & N66T Rack Product OverviewRogério FerreiraAún no hay calificaciones
- RTN 900 V100R005C01 Configuration Guide 04Documento2319 páginasRTN 900 V100R005C01 Configuration Guide 04EugeneAún no hay calificaciones
- Backhauling / Fronthauling for Future Wireless SystemsDe EverandBackhauling / Fronthauling for Future Wireless SystemsKazi Mohammed Saidul HuqAún no hay calificaciones
- VoLTE and ViLTE: Voice and Conversational Video Services over the 4G Mobile NetworkDe EverandVoLTE and ViLTE: Voice and Conversational Video Services over the 4G Mobile NetworkAún no hay calificaciones
- Optimizing and Testing WLANs: Proven Techniques for Maximum PerformanceDe EverandOptimizing and Testing WLANs: Proven Techniques for Maximum PerformanceAún no hay calificaciones
- Finisar ftlc1122sdnl 100gbase-Lr4 and Otu4 Multirate 10km cfp2 Optical Transceiver Productspecrevc3Documento11 páginasFinisar ftlc1122sdnl 100gbase-Lr4 and Otu4 Multirate 10km cfp2 Optical Transceiver Productspecrevc3Keyson FariasAún no hay calificaciones
- 134.4020.23 DM705 DatasheetDocumento32 páginas134.4020.23 DM705 DatasheetKeyson FariasAún no hay calificaciones
- Test Guide Daa Planning Deployment Maintenance White Papers Books enDocumento21 páginasTest Guide Daa Planning Deployment Maintenance White Papers Books enKeyson FariasAún no hay calificaciones
- Nokia Optical Diagnostics and TroubleshootingDocumento2 páginasNokia Optical Diagnostics and TroubleshootingKeyson Farias100% (2)
- Document PDFDocumento20 páginasDocument PDFKeyson FariasAún no hay calificaciones
- HPX10 71W PDFDocumento5 páginasHPX10 71W PDFKeyson FariasAún no hay calificaciones
- DatasheetDocumento7 páginasDatasheetKeyson FariasAún no hay calificaciones
- Nera Evolution METRO Datasheet Web A4Documento2 páginasNera Evolution METRO Datasheet Web A4Keyson FariasAún no hay calificaciones
- 1651 Operators Handbook PDFDocumento438 páginas1651 Operators Handbook PDFKeyson FariasAún no hay calificaciones
- Manual PDFDocumento248 páginasManual PDFKeyson FariasAún no hay calificaciones
- LEDR Series: Digital Energy MDSDocumento2 páginasLEDR Series: Digital Energy MDSKeyson FariasAún no hay calificaciones
- Price List Final Usd A4 Rev10jan14Documento77 páginasPrice List Final Usd A4 Rev10jan14Keyson FariasAún no hay calificaciones
- HPX10 71WDocumento5 páginasHPX10 71WKeyson FariasAún no hay calificaciones
- Especificacao Familia LEDR 1851Documento2 páginasEspecificacao Familia LEDR 1851Keyson FariasAún no hay calificaciones
- 3HE06512AAAHTQZZA01 - V1 - 5620 SAM Release 9.0 R8 Optical Parameter ReferenceDocumento326 páginas3HE06512AAAHTQZZA01 - V1 - 5620 SAM Release 9.0 R8 Optical Parameter ReferenceKeyson FariasAún no hay calificaciones
- Wavestar ADM 16.1 Compacto ManualDocumento30 páginasWavestar ADM 16.1 Compacto ManualKeyson FariasAún no hay calificaciones
- MN5300 Brochure Issue2.0 Mar29 2010Documento2 páginasMN5300 Brochure Issue2.0 Mar29 2010Keyson FariasAún no hay calificaciones
- Focus Notes - Philippine Standard On Auditing 120Documento1 páginaFocus Notes - Philippine Standard On Auditing 120Kristine Apale100% (1)
- RA11201 IRR DHSUD Act 2019Documento37 páginasRA11201 IRR DHSUD Act 2019ma9o0Aún no hay calificaciones
- Form PDF 344472690310722Documento11 páginasForm PDF 344472690310722NandhakumarAún no hay calificaciones
- Bullet Proof G WashingtonDocumento5 páginasBullet Proof G Washingtonapi-239094488Aún no hay calificaciones
- Conflict of Laws in Legitimacy, Legitimation and Adoption: Under The Guidance ofDocumento13 páginasConflict of Laws in Legitimacy, Legitimation and Adoption: Under The Guidance ofShivansh JaiswalAún no hay calificaciones
- Retro 80s Kidcore Arcade Company Profile Infographics by SlidesgoDocumento35 páginasRetro 80s Kidcore Arcade Company Profile Infographics by SlidesgoANAIS GUADALUPE SOLIZ MUNGUIAAún no hay calificaciones
- Strategies For Becoming A Franchisor: Know The Opportunities and ChallengesDocumento26 páginasStrategies For Becoming A Franchisor: Know The Opportunities and ChallengesShahmeer ShahidAún no hay calificaciones
- Vehicle Lease Agreement TEMPLATEDocumento5 páginasVehicle Lease Agreement TEMPLATEyassercarloman100% (1)
- List of European Countries Via WIKIPEDIA: Ran K State Total Area (KM) Total Area (SQ Mi) NotesDocumento3 páginasList of European Countries Via WIKIPEDIA: Ran K State Total Area (KM) Total Area (SQ Mi) NotesAngelie FloraAún no hay calificaciones
- Clado-Reyes V LimpeDocumento2 páginasClado-Reyes V LimpeJL A H-DimaculanganAún no hay calificaciones
- Rohmayati Pertemuan 8Documento5 páginasRohmayati Pertemuan 8Mamah ZhakiecaAún no hay calificaciones
- Gadbd f11078 12.3.2.1 Using Goldengate Big DataDocumento368 páginasGadbd f11078 12.3.2.1 Using Goldengate Big Dataganesh rajanAún no hay calificaciones
- Ebecryl-4175 en A4Documento1 páginaEbecryl-4175 en A4I Love MusicAún no hay calificaciones
- Reference and RevisionDocumento6 páginasReference and RevisionRohit kumar SharmaAún no hay calificaciones
- Jetblue PresentationDocumento38 páginasJetblue Presentationpostitman33% (3)
- Motion To Disqualify MCAO - 7-31-13Documento14 páginasMotion To Disqualify MCAO - 7-31-13crimefileAún no hay calificaciones
- First Year Phyiscs Ipe Imp Q.bank 2020-2021 - (Hyderad Centres)Documento26 páginasFirst Year Phyiscs Ipe Imp Q.bank 2020-2021 - (Hyderad Centres)Varun Sai SundalamAún no hay calificaciones
- ARTADocumento1 páginaARTAAron Paul Morandarte RulogAún no hay calificaciones
- 05 Solution 1Documento18 páginas05 Solution 1Mohar SinghAún no hay calificaciones
- Malala YousafzaiDocumento13 páginasMalala YousafzaiAde SihombingAún no hay calificaciones
- Passing Off Action Under Trade Mark LawDocumento15 páginasPassing Off Action Under Trade Mark LawPappu KumarAún no hay calificaciones
- EHDF Module 4 & 5Documento5 páginasEHDF Module 4 & 5Faizal KhanAún no hay calificaciones
- Nicoleta Medrea - English For Law and Public Administration.Documento57 páginasNicoleta Medrea - English For Law and Public Administration.gramadorin-10% (1)
- Required Documents For EnrolmentDocumento7 páginasRequired Documents For EnrolmentCamillus Carillo AngelesAún no hay calificaciones
- Business Law and Regulations 1Documento4 páginasBusiness Law and Regulations 1Xyrah Yvette PelayoAún no hay calificaciones
- FINAL-Telephone Directory-2019Documento107 páginasFINAL-Telephone Directory-2019Rizwan TahirAún no hay calificaciones
- Office of The Presiden T: Vivat Holdings PLC) Inter Partes Case No - 3799 OpposerDocumento5 páginasOffice of The Presiden T: Vivat Holdings PLC) Inter Partes Case No - 3799 OpposermarjAún no hay calificaciones
- About Dhanalaxmi Bank KarthikDocumento4 páginasAbout Dhanalaxmi Bank KarthikYkartheek GupthaAún no hay calificaciones
- Tort Outline .. Internet SourceDocumento43 páginasTort Outline .. Internet SourceColeman HengesbachAún no hay calificaciones
- Federal Discrimination Lawsuit Against City of Evanston, City Manager Wally BobkiewiczDocumento51 páginasFederal Discrimination Lawsuit Against City of Evanston, City Manager Wally BobkiewiczJonah MeadowsAún no hay calificaciones
