Professional Documents
Culture Documents
V100R011C00
Issue 01
Date 2016-10-15
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.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
The following table lists the product versions related to this document.
Intended Audience
The intended audience of this document are:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Whole manual Some bugs in the manual of the previous version are fixed.
2 Alarm List 2.2.116 SCC Board Alarm List is modified: TN21SCC board is
deleted.
Update Description
Whole manual Some bugs in the manual of the previous version are fixed.
Update Description
Update Description
Whole manual Some bugs in the manual of the previous version are fixed.
Update Description
Update Description
2 Alarm List l Add "Service Affecting" in the section 2.1 Product Alarm List.
l 2.2.150 TSC Board Alarm List is added.
l 2.2.152 TTX Board Alarm List is added.
l 2.2.5 AUX Board Alarm List is modified.
l 2.2.26 EFI Board Alarm List is modified.
l 2.2.25 EFI2 Board Alarm List is modified.
l 2.2.33 EX2 Board Alarm List is modified.
l 2.2.27 EG16 Board Alarm List is modified.
l 2.2.51 LEM24 Board Alarm List is modified.
l 2.2.52 LEX4 Board Alarm List is modified.
l 2.2.66 LSX Board Alarm List is modified.
l 2.2.82 ND2 Board Alarm List is modified.
l 2.2.89 NS2 Board Alarm List is modified.
l 2.2.103 PND2 Board Alarm List is modified.
l 2.2.139 TEM28 Board Alarm List is modified.
Update Description
2 Alarm List 2.2.116 SCC Board Alarm List is modified, TN21SCC board is
deleted.
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Update Description
Contents
2 Alarm List......................................................................................................................................45
2.1 Product Alarm List....................................................................................................................................................... 46
2.1.1 Alarm List A.............................................................................................................................................................. 46
4.62 ERPS_IN_PROTECTION........................................................................................................................................586
4.63 ETH_APS_LOST..................................................................................................................................................... 588
4.64 ETH_APS_PATH_MISMATCH.............................................................................................................................. 589
4.65 ETH_APS_SWITCH_FAIL..................................................................................................................................... 591
4.66 ETH_APS_TYPE_MISMATCH.............................................................................................................................. 593
4.67 ETH_BIP8_SD......................................................................................................................................................... 594
4.68 ETH_CFM_AIS........................................................................................................................................................595
4.69 ETH_CFM_LOC...................................................................................................................................................... 596
4.70 ETH_CFM_MACSTATUS.......................................................................................................................................598
4.71 ETH_CFM_MISMERGE......................................................................................................................................... 600
4.72 ETH_CFM_RDI....................................................................................................................................................... 601
4.73 ETH_CFM_UNEXPERI.......................................................................................................................................... 602
4.74 ETH_EFM_DF......................................................................................................................................................... 603
4.75 ETH_EFM_EVENT................................................................................................................................................. 605
4.76 ETH_EFM_LOOPBACK.........................................................................................................................................606
4.77 ETH_EFM_REMFAULT......................................................................................................................................... 608
4.78 ETH_HI_BER.......................................................................................................................................................... 609
4.79 ETH_LINK_DOWN................................................................................................................................................ 610
4.80 ETH_LOS................................................................................................................................................................. 611
4.81 ETH_MISCONNECT.............................................................................................................................................. 615
4.82 ETH_NO_FLOW..................................................................................................................................................... 616
4.83 ETH_SERVICE_CONFIG_FAIL.............................................................................................................................617
4.84 ETHOAM_DISCOVER_FAIL.................................................................................................................................618
4.85 ETHOAM_RMT_CRIT_FAULT............................................................................................................................. 620
4.86 ETHOAM_RMT_LOOP.......................................................................................................................................... 621
4.87 ETHOAM_RMT_SD............................................................................................................................................... 622
4.88 ETHOAM_SELF_LOOP......................................................................................................................................... 623
4.89 ETHOAM_VCG_SELF_LOOP............................................................................................................................... 625
4.90 EX_ETHOAM_MPID_CNFLCT............................................................................................................................ 626
4.91 EXT_MODULE_OFFLINE..................................................................................................................................... 627
4.92 EXT_SYNC_LOS.................................................................................................................................................... 628
4.93 EXT_TIME_LOC.....................................................................................................................................................630
4.94 FAN_FAIL................................................................................................................................................................ 631
4.95 FAN_FAULT............................................................................................................................................................ 632
4.96 FC_8B10BERR_OVER........................................................................................................................................... 633
4.97 FC_AIS..................................................................................................................................................................... 634
4.98 FCS_ERR................................................................................................................................................................. 635
4.99 FDBSIZEALM_ELAN............................................................................................................................................ 637
4.100 FEATURE_WITHOUT_LICENSE........................................................................................................................638
4.101 FEC_LOF............................................................................................................................................................... 639
4.102 FEC_OOF............................................................................................................................................................... 640
4.103 FIBERTYPE_MIS.................................................................................................................................................. 641
4.230 ODUk_PM_LCK....................................................................................................................................................796
4.231 ODUk_PM_OCI..................................................................................................................................................... 797
4.232 ODUk_PM_TIM.................................................................................................................................................... 799
4.233 ODUk_TCMn_AIS................................................................................................................................................ 800
4.234 ODUk_TCMn_BDI................................................................................................................................................ 801
4.235 ODUk_TCMn_DEG...............................................................................................................................................802
4.236 ODUk_TCMn_EXC............................................................................................................................................... 804
4.237 ODUk_TCMn_LCK............................................................................................................................................... 805
4.238 ODUk_TCMn_LTC................................................................................................................................................806
4.239 ODUk_TCMn_OCI................................................................................................................................................ 807
4.240 ODUk_TCMn_SSF................................................................................................................................................ 808
4.241 ODUk_TCMn_TIM................................................................................................................................................809
4.242 ODUKSP_PS..........................................................................................................................................................810
4.243 ODUKSP_STA_INDI.............................................................................................................................................812
4.244 OH_LOOP.............................................................................................................................................................. 814
4.245 OLP_PS.................................................................................................................................................................. 815
4.246 OLP_STA_INDI..................................................................................................................................................... 816
4.247 OMS_BDI...............................................................................................................................................................818
4.248 OMS_BDI_O..........................................................................................................................................................819
4.249 OMS_BDI_P.......................................................................................................................................................... 820
4.250 OMS_FDI_O.......................................................................................................................................................... 821
4.251 OMS_FDI_P........................................................................................................................................................... 822
4.252 OMS_LOS_P..........................................................................................................................................................823
4.253 OMS_LOSS_ACCUM_ABN.................................................................................................................................824
4.254 OMS_LOSS_MON_FAIL......................................................................................................................................825
4.255 OMS_PMI.............................................................................................................................................................. 825
4.256 OMS_PWR_ADJ_FAIL......................................................................................................................................... 826
4.257 OMS_SSF............................................................................................................................................................... 827
4.258 OMS_SSF_O.......................................................................................................................................................... 828
4.259 OMS_SSF_P...........................................................................................................................................................829
4.260 ONE_PUMP_WORK............................................................................................................................................. 830
4.261 OOL........................................................................................................................................................................ 831
4.262 OOS_LOST............................................................................................................................................................ 832
4.263 OPA_FAIL_INDI....................................................................................................................................................833
4.264 OPU1_VCAT_SQM............................................................................................................................................... 834
4.265 OPU1_VCAT_VcPLM........................................................................................................................................... 835
4.266 OPU4_LOOMFI..................................................................................................................................................... 836
4.267 OPUk_CSF............................................................................................................................................................. 837
4.268 OPUk_MSIM..........................................................................................................................................................838
4.269 OPUk_PLM............................................................................................................................................................ 839
4.270 ORP_CRITICAL_HI..............................................................................................................................................840
4.271 OSC_CLK_MISMATCH....................................................................................................................................... 841
4.272 OSC_BDI................................................................................................................................................................843
4.273 OSC_DEG.............................................................................................................................................................. 843
4.274 OSC_RDI................................................................................................................................................................844
4.275 OSNR_LOSS_UNBALANCED............................................................................................................................ 845
4.276 OTS_BDI................................................................................................................................................................846
4.277 OTS_BDI_O........................................................................................................................................................... 847
4.278 OTS_BDI_P............................................................................................................................................................848
4.279 OTS_LOS_O.......................................................................................................................................................... 849
4.280 OTS_LOS_P........................................................................................................................................................... 850
4.281 OTS_PMI................................................................................................................................................................851
4.282 OTS_TIM............................................................................................................................................................... 852
4.283 OTU_AIS................................................................................................................................................................852
4.284 OTU_LOF.............................................................................................................................................................. 854
4.285 OTU_LOM............................................................................................................................................................. 855
4.286 OTUk_AIS..............................................................................................................................................................856
4.287 OTUk_BDI............................................................................................................................................................. 857
4.288 OTUk_DEG............................................................................................................................................................858
4.289 OTUk_EXC............................................................................................................................................................ 859
4.290 OTUk_LOM........................................................................................................................................................... 860
4.291 OTUk_TIM.............................................................................................................................................................861
4.292 OUT_PWR_ABN................................................................................................................................................... 862
4.293 OUT_PWR_LOW.................................................................................................................................................. 864
4.294 OWSP_PS...............................................................................................................................................................865
4.295 OWSP_STA_INDI................................................................................................................................................. 866
4.296 PASSWORD_NEED_CHANGE............................................................................................................................868
4.297 PATCH_ACT_TIMEOUT...................................................................................................................................... 869
4.298 PATCH_BD_EXCLUDE........................................................................................................................................870
4.299 PATCH_BD_MATCH_FAIL..................................................................................................................................870
4.300 PATCH_CHGSCC_NOTMATCH..........................................................................................................................871
4.301 PATCH_DEACT_TIMEOUT.................................................................................................................................872
4.302 PATCH_PKGERR.................................................................................................................................................. 873
4.303 PID_AUTO_ADJUST_FAIL................................................................................................................................. 873
4.304 PM_BDI..................................................................................................................................................................875
4.305 PM_BEI.................................................................................................................................................................. 876
4.306 PM_BIP8_OVER................................................................................................................................................... 877
4.307 PM_BIP8_SD......................................................................................................................................................... 878
4.308 PM_TIM................................................................................................................................................................. 880
4.309 PORT_EXC_TRAFFIC..........................................................................................................................................880
4.310 PORTSWITCH_FAIL............................................................................................................................................ 882
4.311 POWER_ABNORMAL..........................................................................................................................................882
4.312 POWER_DIFF_OVER...........................................................................................................................................884
4.313 POWER_SAMPLE_DIFF......................................................................................................................................885
4.314 PRBS_LSS..............................................................................................................................................................886
4.315 PRO_PKT_FLOODING........................................................................................................................................ 887
4.316 PTP_SOURCE_SWITCH...................................................................................................................................... 888
4.317 PTP_TIMESTAMP_ABN...................................................................................................................................... 889
4.318 PUM_BCM_ALM..................................................................................................................................................891
4.319 PUM_TEM_ALM.................................................................................................................................................. 892
4.320 PUMP_LINK_ULLAGE_HIGH............................................................................................................................893
4.321 PUMP_MIS_MATCH............................................................................................................................................ 894
4.322 PUMP_OFFLINE................................................................................................................................................... 894
4.323 PW_APS_DEGRADED......................................................................................................................................... 895
4.324 PW_APS_OUTAGE...............................................................................................................................................897
4.325 PW_NO_TRAFFIC................................................................................................................................................ 899
4.326 PWAPS_LOST....................................................................................................................................................... 900
4.327 PWAPS_PATH_MISMATCH.................................................................................................................................902
4.328 PWAPS_SWITCH_FAIL....................................................................................................................................... 904
4.329 PWAPS_TYPE_MISMATCH................................................................................................................................ 905
4.330 PWD_ENCRYPT_RISK........................................................................................................................................ 906
4.331 PWR_UNBALANCED.......................................................................................................................................... 907
4.332 R_LOC....................................................................................................................................................................908
4.332.1 R_LOC (OCS)..................................................................................................................................................... 908
4.332.2 R_LOC (OTN).....................................................................................................................................................909
4.333 RACK_CONFLICT_SCREEN.............................................................................................................................. 910
4.334 RELAY_ALARM_CRITICAL.............................................................................................................................. 912
4.335 RELAY_ALARM_IGNORE..................................................................................................................................913
4.336 RELAY_ALARM_MAJOR................................................................................................................................... 914
4.337 RELAY_ALARM_MINOR....................................................................................................................................916
4.338 REM_SD................................................................................................................................................................ 917
4.339 RL_CRITICAL_HI................................................................................................................................................ 918
4.340 RL_CRITICAL_LOW............................................................................................................................................919
4.341 RM_RLOS..............................................................................................................................................................920
4.342 RMON_ALM_INBADOCTS_OVER....................................................................................................................921
4.343 RS_CROSSTR........................................................................................................................................................922
4.344 RTC_FAIL.............................................................................................................................................................. 924
4.345 RX_POWER_ABNORMAL..................................................................................................................................924
4.346 RXCFG_WAVEDATA_MIS.................................................................................................................................. 926
4.347 S1_SYN_CHANGE............................................................................................................................................... 927
4.348 SCC_CHANGE...................................................................................................................................................... 928
4.349 SCC_LOC...............................................................................................................................................................929
4.350 SEC_RADIUS_FAIL............................................................................................................................................. 930
4.351 SERVICE_CAPACITY_EXCEED_LICENSE...................................................................................................... 931
4.352 SERVICE_TYPE_EXCEED_LICENSE................................................................................................................932
4.353 SHELF_AREA_POWER_OVER.......................................................................................................................... 933
4.396 SWDL_PKGVER_MM..........................................................................................................................................978
4.397 SWDL_ROLLBACK_FAIL...................................................................................................................................979
4.398 SYN_BAD..............................................................................................................................................................980
4.399 SYNC_C_LOS....................................................................................................................................................... 981
4.400 SYNC_DISABLE...................................................................................................................................................983
4.401 SYNC_F_M_SWITCH.......................................................................................................................................... 984
4.402 SYNC_FAIL........................................................................................................................................................... 985
4.403 SYNC_LOCKOFF................................................................................................................................................. 987
4.404 SYSLOG_COMM_FAIL....................................................................................................................................... 988
4.405 SYSPARA_CFDB_NOSAME............................................................................................................................... 989
4.406 T_LOSEX............................................................................................................................................................... 990
4.407 T_SLIP....................................................................................................................................................................991
4.408 TEM_HA................................................................................................................................................................ 992
4.409 TEM_LA................................................................................................................................................................ 993
4.410 TEST_STATUS...................................................................................................................................................... 994
4.411 THUNDERALM.................................................................................................................................................... 995
4.412 TIME_LOCK_FAIL............................................................................................................................................... 996
4.413 TIME_LOS............................................................................................................................................................. 997
4.414 TIME_NO_TRACE_MODE..................................................................................................................................999
4.415 TR_LOC............................................................................................................................................................... 1000
4.416 TU_AIS_VC3....................................................................................................................................................... 1002
4.417 TU_LOP_VC3......................................................................................................................................................1003
4.418 TUNNEL_APS_DEGRADED............................................................................................................................. 1004
4.419 TUNNEL_APS_OUTAGE...................................................................................................................................1005
4.420 VCAT_LOA..........................................................................................................................................................1006
4.420.1 VCAT_LOA (OCS)........................................................................................................................................... 1007
4.420.2 VCAT_LOA (OTN)...........................................................................................................................................1008
4.421 VCAT_LOM_VC3............................................................................................................................................... 1009
4.422 VCAT_LOM_VC4............................................................................................................................................... 1010
4.423 VCTRUNK_NO_FLOW...................................................................................................................................... 1011
4.424 VLAN_SNCP_PS.................................................................................................................................................1012
4.425 VOADATA_MIS.................................................................................................................................................. 1013
4.426 W_R_FAIL........................................................................................................................................................... 1014
4.427 WAVE_ADD_ABN.............................................................................................................................................. 1015
4.428 WAVE_DROP_ABN............................................................................................................................................ 1016
4.429 WAVEDATA_MIS................................................................................................................................................1017
4.430 WAVELEN_OVER...............................................................................................................................................1018
4.431 XC_UNSWITCH..................................................................................................................................................1019
6.103 ODUk_TCMn_FEBBER......................................................................................................................................1361
6.104 ODUk_TCMn_FEES............................................................................................................................................1362
6.105 ODUk_TCMn_FESES......................................................................................................................................... 1362
6.106 ODUk_TCMn_FESESR.......................................................................................................................................1363
6.107 ODUk_TCMn_FEUAS........................................................................................................................................ 1364
6.108 ODUk_TCMn_IAES............................................................................................................................................ 1364
6.109 ODUk_TCMn_SES.............................................................................................................................................. 1365
6.110 ODUk_TCMn_SESR............................................................................................................................................1366
6.111 ODUk_TCMn_TMP............................................................................................................................................. 1366
6.112 ODUk_TCMn_UAS............................................................................................................................................. 1367
6.113 OOPRL................................................................................................................................................................. 1368
6.114 OSC_BBE.............................................................................................................................................................1369
6.115 OSC_BBER.......................................................................................................................................................... 1369
6.116 OSC_BIAES......................................................................................................................................................... 1370
6.117 OSC_ES................................................................................................................................................................ 1371
6.118 OSC_FEBBE........................................................................................................................................................ 1371
6.119 OSC_FEBBER......................................................................................................................................................1372
6.120 OSC_FEES........................................................................................................................................................... 1373
6.121 OSC_FESES......................................................................................................................................................... 1373
6.122 OSC_FESESR...................................................................................................................................................... 1374
6.123 OSC_FEUAS........................................................................................................................................................1375
6.124 OSC_IAES............................................................................................................................................................1375
6.125 OSC_SES..............................................................................................................................................................1376
6.126 OSC_SESR........................................................................................................................................................... 1376
6.127 OSC_UAS............................................................................................................................................................ 1377
6.128 OSPICCV............................................................................................................................................................. 1378
6.129 OSPITMP............................................................................................................................................................. 1379
6.130 OTU2SMBIP8...................................................................................................................................................... 1380
6.131 OTUk_BBE.......................................................................................................................................................... 1381
6.132 OTUk_BBER........................................................................................................................................................1381
6.133 OTUk_BIAES...................................................................................................................................................... 1382
6.134 OTUk_ES............................................................................................................................................................. 1383
6.135 OTUk_FEBBE......................................................................................................................................................1384
6.136 OTUk_FEBBER................................................................................................................................................... 1385
6.137 OTUk_FEES.........................................................................................................................................................1385
6.138 OTUk_FESES...................................................................................................................................................... 1386
6.139 OTUk_FESESR....................................................................................................................................................1387
6.140 OTUk_FEUAS..................................................................................................................................................... 1388
6.141 OTUk_IAES......................................................................................................................................................... 1388
6.142 OTUk_SES........................................................................................................................................................... 1389
6.143 OTUk_SESR........................................................................................................................................................ 1390
6.144 OTUk_TMP..........................................................................................................................................................1391
7 Event List...................................................................................................................................1425
8 Event Processing...................................................................................................................... 1428
8.1 OWSP abnormal event............................................................................................................................................. 1429
8.2 ODUk SPRing abnormal event.................................................................................................................................1431
8.3 RMON performance value is above the upper limit.................................................................................................1434
8.4 RMON module performance value is lower than the lower threshold.....................................................................1436
8.5 1+1 Equipment Level Protection Switching Event Report...................................................................................... 1438
A Glossary....................................................................................................................................1440
1 Overview
This topic describes the meaning, impact, and indicator status of the alarms of four severities,
alarm categories, and examples for the alarm categories. In addition, it describes different
types of performance events, the alarm signal flow of OTU boards, the suppression
relationship between alarms, and performance events suppressed by alarms.
1.1 Alarm Severity
This topic describes the meaning, impact, and indicator status of the alarms of four severities.
1.2 Alarm Category
This topic describes the alarm categories and examples for the alarm categories.
1.3 Alarm Management
This section describes the alarm reporting process.
1.4 Performance Event Category
Performance events can be classified into seven categories according to the function
monitored by a performance event. Among these performance events, Performance Event of
Higher Order Path Bit Error, Lower Order Path Bit Error and Pointer Justification are
supported only by the OptiX OSN 8800.
1.5 Alarm Signal Flow(OTN)
This section describes the alarm signal flow of the OTU. It describes the generation,
detection, and transmission of alarms when the OTU accesses different types of signals.
1.6 Alarm Signal Flow (OCS)
This topic describes the generation principles and detection mechanism of certain signal flows
in the SDH services.
1.7 Suppression Relation of Alarms (OTN)
This topic describes the rules of alarm suppression and provides a figure to show the
suppression relationship between common alarms. A better understanding of the alarm
suppression relationship helps improve the efficiency for handling alarms.
1.8 Suppression Relation of Alarms (OCS)
The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This section describes the suppression relationships among SDH alarms.
1.9 Performance Event Suppression by Alarms
An optical port can report several alarms and performance events. Some performance events
are not important for maintenance engineers.
Critical alarm A global fault alarm that would cause the The SRV is on (red).
system down.
Major alarm A fault alarm reported on partial boards or The SRV is on (red).
lines.
Minor alarm General fault alarms and event alarms that The SRV is on (yellow).
are used to describe whether the board or
line works properly. A common alarm that
describes whether a board or line works
properly, for example, an alarm indicating
that a board underwent a reset, applying for
common resources failed, or allocating
common resources timed out.
Process alarm Alarms related to the software The alarm is generated when the
processing and anomalies database is in error or the NE is in
the installing state.
Equipment alarm Alarms related to the hardware of The alarm is generated when the
the equipment laser is faulty or an optical port is
looped back.
Service alarm Alarms related to the service The alarm is generated when the
status and network service quality signals at the line layer are
degraded.
Environment Alarms related to the power The alarm is generated when the
alarm supply system and environment of temperature of the power module
the equipment room is excessively high.
Security alarm Alarms related to the network The alarm is generated when the
management and the NE security NE user is not logged in.
l Alarm suppression
l Automatic alarm reporting
l Alarm masking
In addition, alarm filtering and alarm reversion affect alarm reporting.
Alarm Suppression
Lower-level alarms usually derive from a root alarm that is directly triggered by an exception
or fault. These lower-level alarms make fault locating and handling difficult. Alarm
correlation can be configured to suppress non-root alarms. Then, fewer alarms are reported to
the NMS, and faults can be identified and rectified quickly.
Alarm Masking
The alarm masking function can be enabled for all alarms on an NE or a board on an NE.
When an alarm is masked, the corresponding NE or board does not monitor this alarm.
Alarm Filtering
Alarm filtering is implemented on the NMS, and does not affect alarms on NEs. The NMS
accepts or discards reported alarms based on the alarm filtering configuration. If alarm
filtering is enabled for an alarm on an NE, the NMS discards the alarm and does not save it
into the alarm database. If alarm filtering is disabled for an alarm on an NE, the NMS accepts
the alarm and saves it into the alarm database.
Alarm Reversion
For ports that are not configured with services, the alarm reversion function can be used to
prevent alarms from being generated. This prevents interference from alarms.
When the alarm reversion function is enabled on a port, the alarm status of this port is
opposite to the actual status. That is, no alarm is reported when an alarm is generated and an
alarm is reported when no alarm is generated.
There are three alarm reversion modes: non-reversion, automatic reversion, and manual
reversion.
l Non-reversion
This mode indicates the normal alarm monitoring state and is the default mode. In this
mode, the alarm reversion function cannot be enabled on a port.
l Automatic reversion
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 does not report any
alarms. When the current alarms are cleared, the port automatically exits the reversion
mode and the alarm status reported by the port is restored to the actual alarm status.
l Manual reversion
In this mode, the alarm reversion function can be enabled on a port regardless of whether
any alarms are reported at this port.
– When the alarm reversion function is enabled on a port, the alarm status reported by
the port is opposite to the actual alarm status.
– When the alarm reversion function is disabled on a port, the alarm status reported
by the port is the same as the actual alarm status.
Take the following precautions when configuring the alarm reversion function:
l After alarm reversion is enabled on a port on a board, the alarm status of the board,
including the status of the alarm indicators on the board, remains unchanged and
indicates the running status of the board.
l The alarm reversion function is implemented by the NE software. The alarm data on the
NE is the same as the alarm data on the NMS. The alarm data indicates the alarm status
after alarm reversion is implemented.
A performance event is an important parameter that reflects the working performance of the
equipment. An understanding of the generation principle and the related boards and alarms of
performance events is helpful to find incipient faults in routine maintenance and analyze the
fault. Table 1-3 describes the categories of performance events..
Performance events and alarms are related. When the value of a performance event exceeds
the preset threshold, the related alarm is triggered. Therefore, when a performance event is
generated, check whether the related alarm is generated and handle the performance event by
referring to the handling procedure of the related alarm.
The OptiX OSN 8800/OptiX OSN 6800/OptiX OSN 3800 provides the remote monitoring
(RMON) function by which the network can monitor the transmission of data in different
network segments. The RMON provides flexible detection modes and control mechanisms to
cater for the needs of different types of networks. The RMON defines a series of statistic
formats and functions to realize data exchange among the control stations and detection
stations in compliance with the RMON standard. The RMON also provides error diagnosis,
planning and information receiving of the performance events on the entire network.
Performance event related to Performance event generated when the board performs
the check and error correction service check or bit error correction
Performance event related to Performance event generated when the optical power, the
the equipment function working current of the laser or other factors about the
running environment exceed the threshold
Performance event related to Performance event generated when bit errors occur on
the bit errors on the multiplex the multiplexing section in the SDH frames of the signals
section on the WDM side or the client side of a board
Performance event related to Performance event generated when bit errors occur on
the bit errors on the regenerator the regenerator section in the SDH frames of the signals
section on the WDM side or the client side of a board
Performance Event of Higher The performance event generated when bit errors occur
Order Path Bit Error on higher order path.
Performance Event of Lower The performance event generated when bit errors occur
Order Path Bit Error on lower order path.
Performance Event of Pointer The performance event generated when the board
Justification performs pointer justification.
OTN performance event Performance event generated when bit errors occur in the
PM, TCM or SM segment of the OTN service
RMON performance event Performance event related to the mode in which the
board transmits or receives data packets, the number and
quality of packets in different lengths transmitted or
received
1.5.1 Overview
This section describes the seven types of scenarios of the alarm signal flow, SF, SD, and basic
concepts in the alarm signal flow diagram.
Classification
For a WDM product, the detection and transmission of alarms vary according to the type of
the signals that are accessed into the OTU. The OTU is classified into the following types:
l Non-convergent OTU
It refers to an OTU that converts one channel of client service signals.
l Convergent OTU
It refers to an OTU that converges and converts multiple channels of client service
signals.
l Regenerating OTU
It refers to an OTU that regenerates the corresponding service signals at an intermediate
station.
According to the type of the OTU and the type of the signals accessed by the OTU, the
following seven situations are defined in this section:
This section describes the alarm signal flow when the non-convergent OTU processes
standard OTN signals.
l Convergent OTU processing standard SDH signals
This section describes the alarm signal flow when the convergent OTU processes
standard SDH signals.
l Convergent OTU processing standard OTN signals
This section describes the alarm signal flow when the convergent OTU processes
standard OTN signals.
l Regenerating OTU
This section describes the alarm signal flow of the regenerating OTU.
l OTU with the cross-connect function
This section describes the alarm signal flow of the OTU with the cross-connect function.
l OTU processing GE signals
This section describes the alarm signal flow when the OTU processes GE signals.
SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are
trigger conditions of a protection switching. Whether the SD event is used as a trigger
condition, however, it can be set by the user.
The SF and SD events are marked in the alarm signal flow diagrams in this section. These
events are generated when the equipment configured with network protection detects a certain
alarm. If the equipment is not configured with the network protection, the SF and SD events
are not detected or reported.
Concepts
The following concepts are used in the diagrams in this section:
l WDM side: It is the WDM side of the OTU.
l Client side: it is the client side of the OTU. On the client side, the services from a client
device are accessed.
l Middle part: It is the middle part between the WDM side and the client side. It is a
virtual concept, and therefore is not displayed on the U2000. This concept is introduced
to describe the alarm detection mechanism.
l N#1: It indicates channel 1 at optical port N on the OTU. For example, the client-side
optical ports of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical
port of the LQMD unit is numbered 1. Then, 3#1 indicates channel 1 at client-side
optical port 3.
l 1#N: It indicates channel N at WDM-side optical port 1 on the OTU. For example, 1#3
indicates channel 3 at WDM-side optical port 1.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH
signals
Station A Station B Client device
R_LOS
R_LOS REM_SF R_LOF
R_LOF
R_LOF REM_SF R_LOF
MS_AIS
MS_AIS REM_SF MS_AIS
BI errors
B1_EXC REM_SD B1errors
BI errors
B1_SD B1errors
SD
PM BIP8 errors ODUk_PM_DEG/
Errors
ODUk_PM_EXC
PM remote BER
performance events
SD
SM BIP8 Errors OTUk_DEG/
Errors
OTUk_EXC
SF
OTUk_AIS
OTUk_AIS R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF
OTUk_LOM
OTUk_LOM R_LOF
ODUk_PM_BDI
&OTUk_BDI
This section describes the alarm signal flow by analyzing how the OTU processes the R_LOS
alarm and PM BIP8 errors. The alarm signal flows of other alarms are similar.
l R_LOS
The client side of the OTU at station A detects the R_LOS alarm. The R_LOS signals
are processed on the WDM side of the OTU and then are sent to station B. The client
side of the OTU at station B detects the REM_SF alarm. The alarm is then sent to the
downstream client device of station B, and the OTU reports the R_LOF alarm to the
client device.
l PM BIP8 errors
The OTU at station B detects PM BIP 8 errors on the WDM side. When the PM BIP 8
errors exceed the threshold, the ODUk_PM_DEG or ODUk_PM_EXC alarm is
generated. The number of errors determines which alarm is generated. In addition, the
performance events indicting ODUk PM remote bit errors are sent to the WDM side of
upstream station A. The bit errors are then sent to the client device (The bit errors cannot
be sent to the downstream station except that the PM BIP 8 errors are from the data
inside). The alarms related to bit errors are detected in the client device.
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH
signals
Station A Station B Client device
Client-side WDM-side WDM-side Client-side Client-device
SF
MFAS frame discontinuous
OTUk_LOM
ODUk_PM_BDI
&OTUk_BDI The SF event is generated when the
SF TIM follow-up response is Enabled.
PM TTI byte mismatch
ODUk_PM_TIM R_LOF
ODUk_PM_BDI
The SF event is generated when the
SF TIM follow-up response is Enabled.
SM TTI byte mismatch
OTUk_TIM R_LOF
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
SF
OTUk_LOF
OTUk_LOF R_LOF
ODUk_PM_BDI
&OTUk_BDI
ODUk_PM_AIS/
SF
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/
ODUk_PM_OCI/ R_LOF
ODUk_PM_LCK
ODUk_PM_BDI
SF
R_LOS
R_LOS R_LOF
ODUk_PM_BDI
&OTUk_BDI
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
This section describes the alarm signal flow by analyzing how the OTU processes the
OTUk_LOF alarm. The alarm signal flows of other alarms are similar.
The WDM side of the OTU at station B detects the OTUk_LOF alarm. Then, the OTU sends
the ODUk_PM_BDI and OTUk_BDI alarms to the WDM side of upstream station A. In
addition, the alarm is then sent to the client side of station B. After the alarm is processed on
the client side, the R_LOF alarm is detected in the client device.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN
signals
Station A Station B Client device
R_LOS SF
R_LOS ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SD
PM BIP8 errors ODUk_PM_DEG/
ODUk_PM_DEG/ PM BIP8 errors
ODUk_PM_EXC ODUk_PM_EXC
SF
OTUk_LOF
OTUk_LOF ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SF
OTUk_LOM
OTUk_LOM ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SF
OTUk_AIS
OTUk_AIS ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI OTUk_LOF/
OTUk_LOM/ SF
OTUk_AIS OTUk_LOF/
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS
OTUk_BDI
This section describes the alarm signal flow by analyzing how the OTU unit processes the
R_LOS and OTUk_LOF alarms. The alarm signal flow of other alarms is similar.
l R_LOS
The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The WDM side
of the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is
generated. The event triggers a protection switching. The alarm is then sent to the
downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS
alarm to the client equipment.
l OTUk_LOF
The OTUk_LOF alarm is detected on the WDM side of the OTU board at station B, and
station B sends the OTUk_BDI alarm to the WDM side of the OTU at the upstream
station A. At the same time, the alarm is then sent to the downstream station of station B,
where it is processed on the client side of the OTU. In this case, the ODUk_PM_AIS
alarm is detected in the client equipment. An SF event is generated on the WDM side of
the OTU at station B, and a service channel protection switching is triggered.
The client side of the OTU at station A receives OTUk_LOF signals. The OTU sends the
OTUk_BDI alarm to the upstream client equipment of station A. In addition, the LOF
alarm is processed on the WDM side of the OTU and then is sent to station B. The
WDM side of the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF
event is generated. The event triggers a protection switching. The alarm is then sent to
the downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS
alarm to the client equipment.
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN
signals
OTUk_BDI
OTUk_BDI OTUk_BDI
OTUk_BDI OTUk_BDI
ODUk_PM_AIS/
SF
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS/ ODUk_PM_AIS/ ODUk_PM_AIS/
ODUk_PM_LCK/ ODUk_PM_LCK/ ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_OCI ODUk_PM_OCI
R_LOS SF
R_LOS ODUk_PM_AIS
OTUk_BDI
l OTUk_TIM
After the OTU at station A receives the OTUk_TIM alarm on the client side, it sends the
OTUk_BDI alarm to the upstream station, but it does not send the OTUk_TIM alarm to
the downstream station. If the TIM is enabled in the subsequent action, an SF event is
generated and the WDM side of the OTU at station B reports the ODUk_PM_AIS alarm.
The ODUk_PM_AIS alarm is sent to the downstream and the client device reports this
alarm.
After the OTU at station B receives the OTUk_TIM alarm on the WDM side, this alarm
is not sent to the downstream if the TIM is not enabled in the subsequent action. If the
TIM is enabled in the subsequent action, an SF event is generated. After the client side of
station B processes the event, the client device reports the ODUk_PM_AIS alarm.
l OTUk_BDI
The OTU detects the OTUk_BDI alarm from the upstream station. This alarm is not sent
to the downstream station.
l ODUk_PM_TIM/ODUk_PM_BDI
The OTU transparently transmits all PM alarms.
l ODUk_PM_AIS/ODUk_PM_LCK/ODUk_PM_OCI
The client side of the OTU at station A receives ODUk_PM_AIS, ODUk_PM_LCK, or
ODUk_PM_OCI signals. The signals are not processed and reported at the local station.
After the signals are sent to station B, the WDM side of the OTU at station B detects the
ODUk_PM_AIS, ODUk_PM_LCK, or ODUk_PM_OCI alarm. Then, an SF event is
generated. The event triggers a protection switching. The alarm is then sent to the
downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS,
ODUk_PM_LCK, or ODUk_PM_OCI alarm to the client equipment.
l R_LOS
The WDM side of the OTU at station B detects the R_LOS alarm. The OTU sends the
OTUk_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then
sent to the client side of station B. After the alarm is processed on the client side, the
ODUk_PM_AIS alarm is detected in the client equipment.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
NOTE
l In Figure 1-5, N#1 indicates channel 1 at optical port N of the OTU. For example, the client-side
optical ports of the LQMD are numbered 3, 4, 5, and 6, and the WDM-side optical port of the
LQMD is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical port 3. 1#N indicates
channel N at WDM-side optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-
side optical port 1.
l Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and
therefore is not displayed on the U2000. This concept is introduced to describe the alarm detection
mechanism. In the middle part of the convergent OTU, the optical port numbers and channel
numbers of signals are reallocated.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Station A Station B Client device
Client-side Middle WDM-side WDM-side Middle Client-side Client-device
R_LOS
N#1 R_LOS N#1 REM_SF N#1 R_LOF
R_LOS
N#1 R_LOS N#1 REM_SF N#1 R_LOF
R_LOF
N#1 R_LOF N#1 REM_SF N#1 R_LOF
R_LOC
N#1 R_LOC N#1 REM_SF N#1 R_LOF
SD
Errors
N#1 Errors 1#N BIT Errors Errors
A
N#1 A 1#N A A
B
N#1 B 1#N B B
C
N#1 C 1#N C C
D N#1 D 1#N D D
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
Station A Station B Client device
Client-side Middle WDM-side WDM-side Middle Client-side Client-device
R_LOF
SF R_LOF
R_LOS
R_LOS
R_LOF
ODUk_PM_BDI&
OTUk_BDI R_LOF
R_LOF
SF
OTUk_LOF/ R_LOF
OTUk_AIS OTUk_LOF/
OTUk_AIS
R_LOF
ODUk_PM_BDI&
R_LOF
OTUk_BDI
R_LOF
ODUk_PM_AIS/ SF
ODUk_PM_LCK/ ODUk_PM_AIS/ R_LOF
ODUk_PM_OCI ODUk_PM_LCK/
ODUk_PM_OCI R_LOF
ODUk_PM_BDI R_LOF
Errors
SD
PM BIP8 errors ODUk_PM_DEG/ Errors
ODUk_PM_EXC
Errors
Errors
SD
Errors
SM BIP8 errors OTUk_DEG/
OTUk_EXC
Errors
PM remote BER
performance events Errors
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
The WDM side of the OTU at station B accesses and processes the alarm signals. The
OTU sends the ODUk_PM_BDI and OTUk_BDI alarm to the WDM side of upstream
station A. In addition, the alarm is then sent to the client side of station B. After the
alarm is processed on the client side, the R_LOF alarm is detected in the client
equipment.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
l There are bit error alarms on the WDM side.
The OTU at station B accesses and processes bit error alarm signals on the WDM side,
and then sends remote bit error performance events to the WDM side of upstream station
A. The bit error alarm is then sent to the client side of the downstream station B, and the
bit error alarm is detected in the client equipment.
An SD event is generated on the WDM side of the OTU at station B. In this case, users
can determine whether the SD event triggers a service channel protection switching
through proper configuration.
NOTE
In Figure 1-7, N#1 indicates channel 1 at optical port N of the OTU. For example, the client-side optical
ports of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical port of the LQMD unit
is numbered 1. Hence, 3#1 indicates channel 1 at client-side optical port 3. 1#N indicates channel N at
WDM-side optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical port
1.
Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and
therefore is not displayed on the U2000. This concept is introduced to describe the alarm detection
mechanism. In the middle part of the convergent OTU, the optical port number and channel number of
signals are re-allocated.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
Station A Station B Client device
R_LOS SF
N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS
R_LOS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
R_LOS SF
R_LOS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS
OTUk_LOM SF
OTUk_LOF SF
Inserts OTUk_BDI back N#1 OTUk_LOF N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
OTUk_TIM
SF
Inserts OTUk_BDI back N#1 OTUk_TIM
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
ODUk_PM_AIS
N#1 ODUk_PM_AIS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
A 1#N A
N#1 A 1#N A
B 1#N B 1#N B
N#1 B
C 1#N C 1#N C
N#1 C
SD
BIT errors
N#1 BIT errors 1#N BIT errors 1#N BIT errors
xxx Detects and reports the xxx alarm A, B, C are the others of the OTN alarms
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
l Four channels of R_LOS signals are accessed on the client side.
The OTU at station A accesses four channels of R_LOS signals on the client side. After
being processed in the middle part and on the WDM side of the OTU at station A, the
alarm signals are then sent to station B. The ODUk_PM_AIS alarm of the corresponding
channel is generated in the middle part of station B. The ODUk_PM_AIS alarm is
detected in the client device.
An SF event is generated in each channel of the OTU at station B, and a protection
switching is triggered.
l One channel of R_LOS, OTUk_LOM or OTUk_LOF signals is accessed on the client
side.
The OTU at station A accesses one channel of R_LOS, OTUk_LOM or OTUk_LOF
signals on the client side, for example, channel 1 at optical port 3. After being processed
in the middle part and on the WDM side of the OTU at station A and the WDM side of
station B, the alarm signals are then sent to the downstream station. The ODUk_PM_AIS
alarm of channel 3 at optical port 1 is generated in the middle part of station B. The
ODUk_PM_AIS alarm is detected in the client device.
An SF event is generated in each channel of the OTU at station B, and a protection
switching is triggered.
l The alarm signals except for the signals of the R_LOS, OTUk_LOM, and OTUk_LOF
alarms are accessed on the client side.
When any of other alarm signals is accessed, the corresponding alarm is reported at each
detection point in the system.
Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
Station A Station B Client device
ODUk_PM_AIS
R_LOS SF ODUk_PM_AIS
R_LOS
ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
&OTUk_BDI
ODUk_PM_AIS
OTUk_LOF/ SF
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS OTUk_LOF/
OTUk_LOM/
OTUk_AIS ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
&OTUk_BDI
ODUk_PM_AIS
ODUk_PM_AIS/ SF
ODUk_PM_LCK/ ODUk_PM_AIS/ ODUk_PM_AIS
ODUk_PM_OCI
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS
ODUk_PM_BDI ODUk_PM_AIS
Errors
SD
PM BIP8 errors Errors
ODUk_PM_DEG/
ODUk_PM_EXC
Errors
PM remote BER
performance events Errors
Errors
SD
SM BIP8 errors Errors
OTUk_DEG/
OTUk_EXC
Errors
NOTE
The value of k on the WDM-side is different from that of the client device.
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
l There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI or
ODUk_PM_LCK on the WDM side.
The WDM side of the OTU at station B accesses and processes the alarm signals. The
OTU sends the ODUk_PM_BDI or OTUk_BDI alarm to the WDM side of upstream
station A. In addition, the alarm is then sent to the client side of station B. After the
alarm is processed on the client side, the ODUk_PM_AIS alarm is detected in the client
device.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
l There are bit error alarms on the WDM side.
The WDM side of the OTU at station B accesses and processes the bit error alarm
signals. The OTU sends the remote bit error performance events to the WDM side of
upstream station A. The alarm is then sent to the client side of the downstream station B.
The error-dependent alarm is detected in the client device.
An SD event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
NOTE
The ALS function of the OTU shown in the figure in this section is not enabled.
The non-intrusive monitoring of the board shown in the figure in this section is enabled.
MFASframe discontinuous
OTUk_LOM ODUk_PM_AIS
OTUk_BDI
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
OTUk_LOF
OTUk_LOF ODUk_PM_AIS
OTUk_BDI
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/ ODUk_PM_AIS/
ODUk_PM_OCI/ ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_LCK
R_LOS
R_LOS ODUk_PM_AIS
OTUk_BDI
In the case of the regenerating OTU, all alarms in the SM section are terminated at the local
station and are not sent to the downstream station (except that the OTUk_LOF alarm is
inserted with an ODUk_PM_AIS alarm to the downstream station). Other alarms are then sent
to the downstream station, and are reported on the WDM side of the OTU (except that the
R_LOS alarm is inserted with an ODUk_PM_AIS alarm to the downstream station).
Straight-Through Mode
Figure 1-10 shows the unidirectional signal flow in the straight-through mode.
NOTE
The optical port number and channel number shown in Figure 1-10 are the numbers that are displayed
on the U2000.
Figure 1-10 OTU with the cross-connect function in the straight-through mode
A B
3#1(RX1) 3#1(TX1)
1#3 1#3
4#1(RX2) 4#1(TX2)
1#4 1(OUT) 1(IN) 1#4
5#1(RX3) 5#1(TX3)
1#5 1#5
6#1(RX4) 6#1(TX4)
1#6 1#6
As shown in Figure 1-10, the four channels of optical signals accessed from RX1-RX4 on
unit A at the upstream station are sent to channels 3-6 that correspond to the OUT port in the
straight-through mode. One channel of optical signals that are input from the IN port on unit
B at the downstream station is demultiplexed into four channels of optical signals, which are
then directly sent to TX1-TX4.
Hence, in the straight-through mode, the REM_SF and REM_SD alarms at the downstream
station indicate that the signals at the corresponding port on the client side at the upstream
station fail or bit errors at this port exceed the threshold. For example, when the services in
channel 1 at optical port 3 on unit A at the upstream station fail, channel 1 at optical port 3 on
unit B at the downstream station reports the REM_SF alarm.
Cross-Connect Mode
The cross-connect mode is classified into intra-unit cross-connection and inter-unit cross-
connection.
l Intra-unit cross-connection
In Figure 1-11, the cross-connection from RX3 (channel 1 at optical port 5) on unit A to
OUT (channel 3 at optical port 1) on unit A is defined as the intra-unit cross-connection.
l Inter-unit cross-connection
In Figure 1-11, the cross-connection from RX1 (channel 1 at optical port 3) on unit C to
OUT (channel 6 at optical port 1) on unit A is defined as the inter-unit cross-connection.
The inter-unit cross-connection is realized by using the backplane.
Figure 1-11 shows the unidirectional signal flow in the cross-connect mode.
Figure 1-11 OTU with the cross-connect function in the cross-connect mode
A B
3#1(RX1) 3#1(TX1)
1#3 1#3
4#1(RX2) 4#1(TX2)
1#4 1(OUT) 1(IN) 1#4
5#1(RX3) 5#1(TX3)
1#5 1#5
6#1(RX4) 6#1(TX4)
1#6 1#6
3#1(RX1)
1#3
4#1(RX2)
1#4
5#1(RX3)
1#5
6#1(RX4)
1#6
The signals that are received from RX3 (channel 1 at optical port 5) on unit A at the upstream
station are sent to IN (channel 3 at optical port 1) on unit B at the downstream station. The
signals received from RX1 (channel 1 at optical port 3) on unit C at the upstream station are
sent to IN (channel 6 at optical port 1) on unit B at the downstream station.
The meaning of optical channels regarding the REM_SF and REM_SD alarms in the cross-
connect mode is different from that in the straight-through mode. For example, when the
services in channel 1 at optical port 4 on unit A at the upstream station fail, unit B at the
downstream station reports the REM_SF alarm in channel 1 at optical port 3; when the
services in channel 1 at optical port 3 on unit C at the upstream station fail, unit B at the
downstream station reports the REM_SF alarm in channel 1 at optical port 6.
Hence, when a unit reports the REM_SF or REM_SD alarm, query the cross-connections of
the unit at the upstream station to locate the alarm signal source. Then, check whether the
client signal status such as the optical power, fibers and optical modules in the channel at the
corresponding optical port is normal. If not, take the corresponding maintenance measures.
NOTICE
In any mode, proper configuration must be made on the U2000.
The GE services are encapsulated into OTN signals or SDH signals after they are accessed on
the client side of the OTU on an Ethernet network. The alarm signal processing when the GE
services are encapsulated into OTN signals differs slightly from the alarm signal processing
when the GE services are encapsulated into SDH signals.
Figure 1-12 and Figure 1-13 show the signal flow when the GE services are encapsulated
into OTN signals and the signal flow when the GE services are encapsulated into SDH signals
respectively.
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals
Errors
Errors Errors
SD
PM BIP8 errors
ODUk_PM_DEG/ Errors
ODUk_PM_EXC
PM remote BER
performance events
SD
SM BIP8 errors
OTUk_DEG/ Errors
OTUk_EXC
This section describes the alarm signal flow when the OTU processes the R_LOS and
LINK_ERR alarms. The signal flow for processing other alarms is similar.
l R_LOS
The client sides of the OTUs at station A and station B work in the non-auto-negotiation
mode. The R_LOS alarm signal is received on the client side of the OTU at station A.
The alarm signal is sent to station B after it is processed on the WDM side of the OTU.
In this case, the REM_SF alarm is generated on the client side of the OTU at station B,
and the client equipment at station B reports the LINK_ERR alarm.
The client sides of the OTUs at station A and station B work in the auto-negotiation
mode. The R_LOS alarm signal is received on the client side of the OTU at station A.
The alarm signal is sent to station B after it is processed on the WDM side of the OTU.
In this case, the REM_SF and LINK_ERR alarms are generated on the client side of the
OTU at station B, and the client equipment at station B reports the LINK_ERR alarm.
l LINK_ERR
The client sides of the OTUs at station A and station B work in the non-auto-negotiation
mode. The client signals at station A contain LINK_ERR alarms, and the client signals
are transmitted transparently from station A to the WDM side of the OTU at station B.
The client sides of the OTUs at station A and station B work in the auto-negotiation
mode. In the case of the Ethernet board that supports the LPT function, when the LPT
enabling status is set to Disable, the LINK_ERR alarm is not generated on the client side
of the OTU at station B; when the LPT enabling status is set to Enable, the LINK_ERR
alarm is generated on the client side of the OTU at station B.
Figure 1-13 Alarm signal flow 2: when the OTU processes GE signals
Station A Station B Client device
SF
R_LOS
R_LOS None LINK_ERR
SM_BDI
This section describes the alarm signal flow when the R_LOS alarm is received on the WDM
side of the OTU at station B. The signal flow for processing other alarms is similar to Figure
1-12.
After the R_LOS alarm is received on the WDM side of the OTU at station B, the SF event is
generated. In addition, station B sends the SM_BDI alarm to the WDM side of the OTU at
station A, and the client equipment at station B reports the LINK_ERR alarm.
OTU OTU
OTU
OM OA OA OD
OTU
Client-side equipment
Client-side equipment
Line-side ODF
Line-side ODF
OTU OTU
OTU OTU
OTU
OD OA OA OM
OTU
OTU OTU
Station A Station B
In this scenario, there are two stations. Station A and station B are OTM stations.
In this scenario, the OTS, OMS, and OCh trails are between adjacent nodes.
In case of the following faults, the association relations of alarms are as follows:
l The fiber from station A to station B is cut.
The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A
reports the OTS_BDI alarm.
l At station A, the optical amplifier unit in direction A-to-B is faulty.
The FIU board at station B reports the OTS_LOS_P alarm and the FIU board at station
A reports the OTS_BDI_P alarm.
l At station A, the optical amplifier in direction A-to-B loses input light.
The FIU board at station A inserts the OTS_PMI and the FIU board at station B does not
report the OTS_LOS_P alarm.
l At station A, the fiber in direction SC1-to-FIU is cut.
The FIU board at station B reports the OTS_LOS_O alarm and the FIU board at station
A reports the OTS_BDI_O alarm.
OTU OTU
OTU
Client-side equipment
Client-side equipment
OM OA OA OD
Line-side ODF
West line-side
OTU OTU
ODF
FI
SC1 FIU SC1
U FIU SC2 FIU
OTU OTU
OTU
OD OA OA OM
OA OTU
OTU OTU
In this scenario, there are three stations. Station A and station C are OTM stations, and station
B is an OLA station.
In this scenario, station OLA only amplifies signals and terminates the OTS layer. The OMS
and OCh trails are between station A and station C.
In case of the following faults, the association relations of alarms are as follows:
l The fiber from station A to station B is cut.
The FIU board at station B reports the OTS_LOS alarm and the OD unit at station C
reports the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A
report the OTS_BDI alarm and OMS_BDI alarm respectively.
l At station A, the optical amplifier unit in direction A-to-B is faulty.
The FIU board at station B reports the OTS_LOS_P alarm. The OD unit at station C
reports the OMS_FDI_P or OMS_SSF_P alarm. The FIU board and OM unit at station A
report the OTS_BDI_P alarm and OMS_BDI_P alarm respectively.
l At station A, the optical amplifier in direction A-to-B loses input light.
The FIU board at station A inserts the OTS_PMI and the FIU board at station B does not
report the OTS_LOS_P alarm.
l At station A, the fiber in direction SC1-to-FIU is cut.
The FIU board at station B reports the OTS_LOS_O alarm. The OD unit at station C
reports the OMS_FDI_O or OMS_SSF_O alarm. The FIU board and OM unit at station
A report the OTS_BDI_O alarm and OMS_BDI_O alarm respectively.
l The configuration of TTI to be received at station B is inconsistent with TTI transmitted
by station A.
The FIU board at station B reports the OTS_TIM alarm. The OD unit at station C reports
the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A report the
OTS_BDI alarm and OMS_BDI alarm respectively.
l The OM unit at station A is faulty.
The OD unit at station C reports the OMS_LOS_P alarm and the OM unit at station A
reports the OMS_BDI_P alarm.
l The OTU board at station A is faulty.
The OTU board at station C reports the OCh_LOS_P alarm.
OTU OOO O O OO O
T T T T T T T T OTU
U U U U U U U U
OTU
OM OA OD OM OA OD
OTU
Client-side equipment
Client-side equipment
West line-side ODF
Line-side ODF
Line-side ODF
OTU O O O OO O OO
T T T T T T T T OTU
U U U UU U UU
In this scenario, there are three stations. Station A and station C are OTM stations, and station
B is an ROADM station.
In this scenario, station ROADM adds and drops certain wavelengths. That is, certain
wavelengths are between stations A and B, or stations B and C, and the other wavelengths are
between stations A and C. Hence, certain OCh trails are between stations A and B, or B and
C, and the other OCh trails are between stations A and C.
In case of the following faults, the association relations of alarms are as follows:
l The fiber from station A to station B is cut.
The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
wavelengths between stations A and C).
l At station A, the optical amplifier unit in direction A-to-B is faulty.
The FIU board at station B reports the OTS_LOS_P alarm and the FIU board at station
A reports the OTS_BDI_P alarm. Station C reports the OCh_FDI_P or OCh_SSF_P
alarm (for wavelengths between stations A and C).
l At station A, the optical amplifier in direction A-to-B loses input light.
The FIU board at station A inserts the OTS_PMI and the FIU board at station B does not
report the OTS_LOS_P alarm.
l At station A, the fiber in direction SC1-to-FIU is cut.
The FIU board at station B reports the OTS_LOS_O alarm and the FIU board at station
A reports the OTS_BDI_O alarm. Station C reports the OCh_FDI_O or OCh_SSF_O
alarm (for wavelengths between stations A and C).
l The configuration of TTI to be received at station B is inconsistent with TTI transmitted
by station A.
The FIU board at station B reports the OTS_TIM alarm and the FIU board at station A
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
wavelengths between stations A and C).
l The OM unit at station A is faulty.
The OD unit at station B reports the OMS_LOS_P alarm and the OM unit at station A
reports the OMS_BDI_P alarm. Station C reports the OCh_FDI_P or OCh_SSF_P alarm
(for wavelengths between stations A and C).
l The OTU board at station A is faulty.
The OTU board at station B reports the OCh_LOS_P alarm (for wavelengths between
stations A and B). The OTU board at station C reports the OCh_LOS_P alarm (for
wavelengths between stations A and C).
l The fiber from station B to station C is cut.
The FIU board at station C reports the OTS_LOS alarm and the FIU board at station B
reports the OTS_BDI alarm.
l At station B, the optical amplifier unit in direction B-to-C is faulty.
The FIU board at station C reports the OTS_LOS_P alarm and the FIU board at station B
reports the OTS_BDI_P alarm.
l At station B, the optical amplifier in direction B-to-C loses input light.
The FIU board at station B inserts the OTS_PMI and the FIU board at station C does not
report the OTS_LOS_P alarm.
l At station B, the fiber in direction SC1-to-FIU is cut.
The FIU board at station C reports the OTS_LOS_O alarm and the FIU board at station
B reports the OTS_BDI_O alarm.
l The configuration of TTI to be received at station C is inconsistent with TTI transmitted
by station B.
The FIU board at station C reports the OTS_TIM alarm and the FIU board at station B
reports the OTS_BDI alarm.
l The OM unit at station B is faulty.
The OD unit at station C reports the OMS_LOS_P alarm and the OM unit at station B
reports the OMS_BDI_P alarm.
l The OTU board at station B is faulty.
The OTU board at station C reports the OCh_LOS_P alarm (for wavelengths from
station B to station C).
1.6.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.
PDH port
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, and AU_AIS alarms are common
AIS alarms.
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.
Generally, the alarms and performance events that are generated in the higher order paths
cause lower order alarms and performance events. Figure 1-18 shows the signal flow between
the SDH interface and the cross-connect unit.
Figure 1-18 Alarm signals generated between the SDH interface and the cross-connect unit
Frame synchronizer MS overhead Pointer processor and HP
and RS overhead processor overhead processor
processor
(RST) (MST) (MSA, HPT)
Based on the positions of the various overhead bytes in the STM-1 frame, the overhead bytes
are classified into the following four modules:
In normal cases, a fault in the first two modules affects all the higher order paths. A fault in
the higher order overhead bytes, however, affects higher order paths.
The following sections describe the signal flow and the processing of overhead bytes.
– If the number of B1 bit errors exceeds the threshold 10-3 (which is the default
value), a B1_EXC alarm occurs.
When there are ten consecutive severely errored seconds (SES, indicating a second in
which errored blocks reach a percentage of 30%) in the regenerator section, the
regenerator section unavailable time event (RSUAT) occurs.
The F1, D1-D3, and E1 bytes, which are irrelevant to alarms and performance events, are sent
to the SCC module and the overhead module.
In the case of the Huawei OSN series equipment, you can use the NMS to set whether the all "1"s
signal is inserted when the HP_TIM, HP_UNEQ alarm occurs. By default, the all "1"s signal is not
inserted.
Currently, the tributary unit group (TUG) is adopted as the payload structure in China.
The preset C2 value that corresponds to the TUG structure is "02".
If the B3 byte restored from the HPOH is not consistent with the BIP-8 computing result
of the VC-4 signal of the preceding frame, B3 bit errors are reported.
In the STM-N lower order SDH interface board, the TU-12 signal extracted from VC-4s
requires the H4 byte to indicate the frame number of the current multiframe in which the
current TU-12 is placed. If the H4 byte detected is illegal, an HP_LOM alarm is
reported.
If bit 5 of the G1 byte is "1", an HP_RDI alarm is reported. The value of bits 1-4 of the
G1 byte determines if an HP_REI alarm is reported. If the value of bits 1-4 of the G1
byte is 1-8, an HP_REI alarm is reported.
When B3 detects SES for 10 consecutive seconds, an HPUAT EVENT performance
event occurs.
Other overhead bytes such as the F3, K3 and N1 are reserved for future use.
Finally, the NxSTM-1 payloads are transmitted to the cross-connect unit for the cross
connection of the higher order path and the lower order path.
The higher order path overhead processor generates N x higher order path overhead bytes,
which are sent to the pointer processor with the N x STM-1 payloads. The setting of higher
order path overhead bytes such as the J1, C2, B3, G1, F2, F3 and N1 can be completed along
the upstream direction.
The pointer processor generates N x AU-4 pointers, and adapts the VC-4 into an AU-4 (H1
and H2 bytes). The N x AU-4s are then multiplexed into an STM-N signal by using the
multiplexing processor and are sent to the MSOH processor.
If an R_LOS, an R_LOF or an MS_AIS alarm is detected in the downstream signal flow, bits
6-8 of the K2 byte are set to "110", and an MS_RDI alarm is reported to the remote end.
If B2 bit errors are detected in the downstream signal flow, an MS_REI alarm is reported to
the remote end through the M1 byte.
After being scrambled by the frame synchronizer and scrambler, the STM-N electrical signal
is converted into an STM-N optical signal by the E/O module and then sent out of the optical
interface.
When the equipment is faulty, several alarms may be generated by the same optical port.
However, some alarms are not important for maintenance engineers. The alarm suppression
function analyzes the relationships between OTN alarms and minimizes the number of non-
fault source alarms reported. This helps users concentrate on fault source alarms and
facilitates quick fault location.
NOTE
l Inter-board and inter-node alarm suppression takes effect only after fiber connections and single-station
optical cross-connections are established on the corresponding link where FIU and OSC boards must be
configured.
l CMR2, CMR4, DMR1, and SBM2 boards do not support inter-board or inter-node alarm suppression.
l An NE equipped with the TN22SCC board does not support inter-board or inter-node alarm suppression.
As shown in Figure 1-19, the fiber between the upstream OTM and OLA sites is broken.
l If the alarm suppression function is not enabled, the OLA site reports the MUT_LOS and
OSC_LOS alarms, and the downstream OTM site reports the MUT_LOS and R_LOS
alarms.
l If the alarm suppression function is enabled, the OLA site reports only the OTS_LOS
alarm, and the downstream OTM site reports no alarm.
O O
T OD OA OD
OA OA T
U U
O
T OA O
OM OA OA OM
U T
U
The alarm suppression function is disabled by default. To enable it, you need to enable
optical-layer monitoring. For details, see Enabling/Disabling Supervision on the Optical
Layer.
NOTE
The R_LOS alarm on a single wavelength and alarms at the electrical layer are not suppressed by alarms
at the server layer.
OTS_LOS_P OTS_LOS-O
OTS_TIM
OTS_BDI
OTS_BDI_O OTS_BDI_P
OMS_SSF_P OMS_SSF_O
OMS_FDI
OMS_FDI_P OMS_FDI_O
OMS_PMI OMS_BDI
OCh_SSF_P OCh_SSF_O
OCh_FDI
OCh_FDI_P OCh_FDI_O
OCh_LOS_P OCh_OCI
OCh_TSF_P OCh_TSF_O
OCH_LOS
LOL
OTUk_LOF
OTUk_LOM
Note:
OTUk_SSF
The TIM alarm suppresses the
BDI alarm and DEG alarm of the
same layer just when the TIM
OTUk_TIM follow-up response is Enabled.
ODUk_TCMn_LTC/
ODUk_TCMn_LCK/ ODUk_TCMn_SSF
ODUk_TCMn_OCI
ODUk_TCMn_TIM
ODUk_TCMn_BDI ODUk_TCMn_DEG
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_SSF
ODUk_PM_TIM
ODUk_PM_BDI ODUk_PM_DEG
OPUk_PLM
OPUk_MSIM
Figure 1-22 shows the suppression between SDH service alarms and other common alarms
related to equipment alarms.
The alarm above an arrow suppresses the alarm below the arrow. For example, when an
optical port on the client side loses signals, the optical port only reports the R_LOS alarm.
The R_LOC and R_LOF alarms are not reported.
Figure 1-22 Suppression between alarms related to SDH services and other common
equipment alarms
R_LOS
R_LOF
MS_AIS
B1_EXC
B2_EXC AU_AIS
AU_LOP
The higher-level alarms above the arrow mask the lower-level alarms below the arrow. This
mechanism allows maintenance engineers to focus only on higher-level alarms.
NOTE
There are suppression relationships between different-level alarms, but not between different-level
performance data because there is no causality between performance events. B2 bit errors will not be
triggered when B1 bit errors occur. The B2 bit error data is derived from calculating the contents in the
managed area.
Table 1-4 Performance events suppressed by the R_LOS alarm (OptiX OSN 8800)
MSBBE RSBBE LSIOPMAX
MSFEUAS LSIOPCUR
Table 1-5 Performance events suppressed by the R_LOS alarm (OptiX OSN 6800/3800)
MSBBE MSFEUAS LSIOPCUR
MSFECSES
2 Alarm List
This topic describes all alarms supported by the product and the related information, and lists
the alarms of each board.
2.1 Product Alarm List
This topic lists the alarms supported by the product.
2.2 Board Alarm List
This topic lists the alarms of every board.
TN18APIU
FAN_FAIL
PUMP_LINK_ULLAGE_HI
LSR_WILL_DIE GH TEMP_OVER
MODULEFILE_UPDAT
E_FAIL PUMP_MIS_MATCH WAVEDATA_MIS
MODULE_TEMP_OVE
R PUMP_OFFLINE WRG_BD_TYPE
MOD_COM_FAIL PUM_BCM_ALM
MUT_LOS PUM_TEM_ALM
HARD_BAD OSC_BDI TD
IN_PWR_HIGH OSC_LOS TF
LASER_MODULE_MIS
MATCH OUT_PWR_LOW
INNER_COMMUN_MISCO SWDL_BD_NOT_MATCH
BD_STATUS N
HARD_BAD NO_ELABEL
TN12AUX
INNER_COMMUN_MISCO
BD_STATUS N SWDL_BD_NOT_MATCH
RACK_CONFLICT_SCREE
HARD_BAD NO_ELABEL N
TN22AUX
COMMUN_FAIL RELAY_ALARM_IGNOR
E
HARD_BAD RELAY_ALARM_MAJOR
TN21AUX
HARD_ERR RELAY_ALARM_MAJOR
TN51AUX
TN52AUX
COMMUN_FAIL SWDL_BD_MATCH_FAIL
TN16AUX
TN15AUX
INNER_COMMUN_MISCO
BD_LEDTEST N SWDL_BD_MATCH_FAIL
RACK_CONFLICT_SCREE
HARD_ERR SUBRACK_ID_MISMATCH N
OMS_FDI OMS_SSF_O
OMS_FDI OMS_SSF_O
OPA_FAIL_INDI
OPA_FAIL_INDI
OPA_FAIL_INDI
NO_BD_SOFT OMS_SSF_O
MODULE_COOLCUR_
OVER OMS_FDI_O SWDL_BD_MATCH_FAIL
MODULE_TEMP_OVE
R OMS_FDI_P SWDL_BD_NOT_MATCH
OMS_LOSS_MON_FAI
L OOS_LOST PUM_TEM_ALM
OMS_LOSS_ACCUM_A
BN OPA_FAIL_INDI R_LOF
SPAN_LOSS_EXCEED_
EOL OSC_BDI SCC_LOC
OSNR_LOSS_UNBALANC
HARD_ERR ED SUM_INPWR_HI
INSERTION_LOSS_HIG
H OTS_BDI SUM_INPWR_LOW
LASER_HAZARD_WA
RNING OTS_LOS TD
LASER_MODULE_MIS
MATCH SPAN_LOSS_UPPER_GAIN TEMP_OVER
SPAN_LOSS_LOWER_GAI
LOOP_ALM N TF
CLIENT_PORT_STA_IN
DI OCh_FDI OWSP_STA_INDI
SPAN_LOSS_EXCEED_
EOL OCh_FDI_P R_LOS
INTRA_OTU_STA_IND
I OCh_SSF_O WRG_BD_TYPE
TN12DCP
BD_LEDTEST INTRA_OTU_PS OCh_SSF_O
CLIENT_PORT_STA_IN
DI NO_BD_SOFT OWSP_PS
SPAN_LOSS_EXCEED_
EOL OCh_FDI_O POWER_DIFF_OVER
HARD_ERR OCh_SSF
TN13DCP
BD_LEDTEST INTRA_OTU_STA_INDI OCh_SSF_O
CLIENT_PORT_STA_IN
DI NO_ELABEL POWER_DIFF_OVER
SPAN_LOSS_EXCEED_EO
FOP_NR OCh_FDI_O L
OMS_LOSS_MON_FAI
L SPAN_LOSS_UPPER_GAIN WRG_BD_TYPE
OMS_LOSS_ACCUM_A SPAN_LOSS_LOWER_GAI
BN N
OMS_LOSS_MON_FAI
L OTS_BDI_O OTS_TIM
OMS_LOSS_ACCUM_A
BN OTS_BDI_P SPAN_LOSS_HIGH
SPAN_LOSS_EXCEED_
EOL OTS_LOS SPAN_LOSS_LOW
SPAN_LOSS_LOWER_GAI
OOS_LOST N WRG_BD_TYPE
OPA_FAIL_INDI
MODULEFILE_UPDAT
E_FAIL OMS_FDI SWDL_BD_NOT_MATCH
MODULE_ADJUST_FA
IL OMS_FDI_O TEMP_OVER
MODULE_TEMP_OVE
R OMS_FDI_P VOADATA_MIS
MUT_TLOS OMS_SSF
NO_BD_PARA OMS_SSF_O
PORT_MODULE_OFFL
BOOTROM_BAD HP_UNEQ INE
ETHOAM_DISCOVER_FAIL LAG_VC_PORT_FAIL TD
LASER_MODULE_MIS
ETHOAM_RMT_CRIT_FAULT MATCH TEMP_OVER
ETHOAM_VCG_SELF_LOOP LCAS_PLCT TF
HARD_ERR OUT_PWR_LOW TF
LASER_MODULE_MISMATCH TD
LAN_LOC RELAY_ALARM_MAJOR
RACK_CONFLICT_SCRE
EN
ETH_MISCONNECT RELAY_ALARM_CRITICA
L RELAY_ALARM_MINOR
RACK_CONFLICT_SC
REEN
TN16EFI
ETH_MISCONNECT RELAY_ALARM_CRITICA
L RELAY_ALARM_MINOR
RACK_CONFLICT_SC
REEN
TN18EFI
INNER_COMMUN_MISCO
BD_LEDTEST N RELAY_ALARM_MAJOR
RELAY_ALARM_CRITICA
HARD_BAD L TEMP_OVER
RACK_CONFLICT_SC
REEN
MPLS_TUNNEL_UNEXPP
BD_LEDTEST IN_PWR_HIGH ER
BWUTILIZATION_OVE
R LAG_DOWN MPLS_TUNNEL_SD
ELAN_SMAC_FLAPPI LASER_MODULE_MISMA
NG TCH NO_ELABEL
ETH_APS_PATH_MISM
ATCH LPT_CFG_CLOSEPORT PORT_EXC_TRAFFIC
ETH_APS_SWITCH_FA
IL LSR_WILL_DIE PORT_MODULE_OFFLINE
ETH_APS_TYPE_MISM
ATCH MAC_FCS_EXC PWAPS_LOST
ETH_EFM_DF MPLS_PW_RDI TD
ETH_LINK_DOWN MPLS_PW_UNEXPMEP TF
TUNNEL_APS_DEGRADE
ETH_LOS MPLS_PW_UNEXPPER D
FLOW_OVER MPLS_TUNNEL_RDI
MPLS_TUNNEL_UNEXPM
HARD_BAD EG
TN55EG16
MPLS_TUNNEL_UNEXPM
BD_STATUS IN_PWR_HIGH EG
MPLS_TUNNEL_UNEXPM
BUS_ERR IN_PWR_LOW EP
BWUTILIZATION_OVE MPLS_TUNNEL_UNEXPP
R LAG_DOWN ER
LASER_MODULE_MISMA
DROPRATIO_OVER TCH OUT_PWR_HIGH
ELAN_SMAC_FLAPPI
NG LASER_SHUT OUT_PWR_LOW
ETH_APS_PATH_MISM
ATCH LSR_WILL_DIE PWAPS_LOST
ETH_APS_SWITCH_FA
IL MAC_FCS_EXC PWAPS_PATH_MISMATCH
ETH_APS_TYPE_MISM
ATCH MCLAG_CFG_MISMATCH PWAPS_SWITCH_FAIL
ETH_EFM_DF MPLS_PW_SD TD
ETH_LINK_DOWN MPLS_PW_UNEXPPER TF
TUNNEL_APS_DEGRADE
ETH_LOS MPLS_TUNNEL_AIS D
FLOW_OVER MPLS_TUNNEL_RDI
HARD_BAD MPLS_TUNNEL_SD
BOOTROM_BAD LAG_PORT_FAIL TD
ETHOAM_RMT_CRIT_FA LCAS_PLCT TF
ULT
ODU1_TCM3_AIS ODU2_TCM3_AIS TD
ODU1_TCM3_LTC ODU2_TCM3_LTC TF
ODU1_TCM3_TIM ODU2_TCM3_TIM
TN54ENQ2
E1_AIS NO_BD_SOFT
LASER_HAZARD_WA
RNING OTS_BDI_O ORP_CRITICAL_HI
MPLS_TUNNEL_UNEXPP
BD_LEDTEST IN_PWR_HIGH ER
BWUTILIZATION_OVE
R LAG_DOWN MPLS_TUNNEL_SD
ELAN_SMAC_FLAPPI LASER_MODULE_MISMA
NG TCH NO_ELABEL
ETH_APS_PATH_MISM
ATCH LPT_CFG_CLOSEPORT PORT_EXC_TRAFFIC
ETH_APS_SWITCH_FA
IL LSR_WILL_DIE PORT_MODULE_OFFLINE
ETH_APS_TYPE_MISM
ATCH MAC_FCS_EXC PWAPS_LOST
ETH_EFM_DF MPLS_PW_RDI TD
ETH_LINK_DOWN MPLS_PW_UNEXPMEP TF
TUNNEL_APS_DEGRADE
ETH_LOS MPLS_PW_UNEXPPER D
FLOW_OVER MPLS_TUNNEL_RDI
MPLS_TUNNEL_UNEXPM
HARD_BAD EG
MPLS_TUNNEL_UNEXPM
B1_SD IN_PWR_HIGH EG
MPLS_TUNNEL_UNEXPM
BD_STATUS IN_PWR_LOW EP
MPLS_TUNNEL_UNEXPP
BUS_ERR J0_MM ER
BWUTILIZATION_OVE
R LAG_DOWN NO_ELABEL
LASER_MODULE_MISMA
DROPRATIO_OVER TCH OUT_PWR_LOW
ELAN_SMAC_FLAPPI
NG LASER_SHUT PORT_EXC_TRAFFIC
ETH_APS_PATH_MISM
ATCH LSR_WILL_DIE PWAPS_PATH_MISMATCH
ETH_APS_SWITCH_FA
IL MAC_FCS_EXC PWAPS_SWITCH_FAIL
ETH_APS_TYPE_MISM
ATCH MCLAG_CFG_MISMATCH PWAPS_TYPE_MISMATCH
ETH_EFM_EVENT MPLS_PW_SF TD
ETH_LOS MPLS_TUNNEL_AIS TF
TUNNEL_APS_DEGRADE
ETH_NO_FLOW MPLS_TUNNEL_LOCV D
FAN_FAIL
TN16FAN/TN18FAN
FAN_FAIL HARD_ERR
OMS_LOSS_ACCUM_A SPAN_LOSS_LOWER_GAI
BN OTS_LOS N
OMS_LOSS_MON_FAI
L OTS_LOS_O SPAN_LOSS_UPPER_GAIN
OPA_FAIL_INDI OTS_TIM
SPAN_LOSS_EXCEED_EO
OTS_BDI L
TN16FIU
SPAN_LOSS_EXCEED_E
BD_STATUS OOS_LOST OL
SPAN_LOSS_LOWER_G
HARD_ERR OTS_BDI_O AIN
SPAN_LOSS_UPPER_GA
MUT_LOS OTS_BDI_P IN
SWDL_BD_MATCH_FAI
NO_BD_PARA OTS_LOS L
SWDL_BD_NOT_MATC
NO_BD_SOFT OTS_LOS_O H
OMS_LOSS_MON_FAIL OTS_TIM
TN15FIU
SPAN_LOSS_LOWER_GAI
BD_STATUS OPA_FAIL_INDI N
OMS_LOSS_ACCUM_A
BN OTS_TIM WRG_BD_TYPE
OMS_LOSS_MON_FAI SPAN_LOSS_EXCEED_EO
L L
OMS_PWR_ADJ_FAIL SPAN_LOSS_LOW
TN14FIU
BD_LEDTEST MUT_LOS OTS_LOS_O
OMS_LOSS_MON_FAI
L OTS_BDI_O SPAN_LOSS_HIGH
OMS_LOSS_ACCUM_A
BN OTS_BDI_P SPAN_LOSS_LOW
SPAN_LOSS_EXCEED_
EOL OTS_LOS TEMP_OVER
SPAN_LOSS_LOWER_GAI
HARD_ERR N
TN13FIU
BD_STATUS OPA_FAIL_INDI OTS_LOS_O
OMS_LOSS_MON_FAI
L OTS_BDI_O OTS_TIM
OMS_LOSS_ACCUM_A
BN OTS_BDI_P SPAN_LOSS_HIGH
SPAN_LOSS_EXCEED_
EOL OTS_LOS SPAN_LOSS_LOW
SPAN_LOSS_LOWER_GAI
OOS_LOST N WRG_BD_TYPE
TN12FIU
BD_LEDTEST OOS_LOST OTS_TIM
OMS_LOSS_MON_FAI
L OTS_BDI_P SUM_INPWR_LOW
OMS_LOSS_ACCUM_A
BN OTS_LOS TEMP_OVER
SPAN_LOSS_EXCEED_
EOL SPAN_LOSS_UPPER_GAIN WAVEDATA_MIS
SPAN_LOSS_LOWER_GAI
HARD_BAD N WRG_BD_TYPE
HARD_ERR OTS_LOS_O
MUT_LOS OTS_LOS_P
TN11FIU
BD_LEDTEST NO_BD_SOFT OTS_LOS_P
OMS_LOSS_MON_FAI
L OTS_BDI SUM_INPWR_HI
OMS_LOSS_ACCUM_A
BN OTS_BDI_O SUM_INPWR_LOW
SPAN_LOSS_EXCEED_
EOL OTS_BDI_P SWDL_BD_MATCH_FAIL
SPAN_LOSS_LOWER_GAI
MUT_LOS N WAVEDATA_MIS
TN21FIU
OMS_LOSS_MON_FAI
L OTS_BDI_O OTS_TIM
OMS_LOSS_ACCUM_A
BN OTS_BDI_P SPAN_LOSS_HIGH
SPAN_LOSS_EXCEED_
EOL OTS_LOS SPAN_LOSS_LOW
SPAN_LOSS_LOWER_GAI
OOS_LOST N WRG_BD_TYPE
COMMUN_FAIL
LASER_MODULE_MIS
MATCH ODU2_TCMn_AIS ODUFLEX_TCMn_BDI
ODU1_PM_TIM ODU4_TCMn_AIS TD
ODU1_TCMn_DEG ODU4_TCMn_LCK TF
ODU1_TCMn_LTC ODU4_TCMn_OCI
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
MODULEFILE_UPDATE_F
BD_STATUS AIL SPAN_LOSS_LOW
LASER_HAZARD_WA OSNR_LOSS_UNBALANC
RNING ED WRG_BD_TYPE
TN51HBA
OSNR_LOSS_UNBALANC
HARD_ERR ED TEMP_OVER
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WRG_BD_TYPE
LSR_WILL_DIE PUM_BCM_ALM
MOD_COM_FAIL PUM_TEM_ALM
CRC4_CROSSTR NO_ELABEL TD
HARD_ERR OSC_RDI TF
LOOP_ALM R_LOF
TN12HSC1
HARD_BAD OSC_DEG TD
IN_PWR_HIGH OUT_PWR_HIGH TF
MPLS_TUNNEL_UNEXPM
AU_AIS EG ODUFLEX_PM_AIS
MPLS_TUNNEL_UNEXPM
AU_LOP EP ODUFLEX_PM_BDI
MPLS_TUNNEL_UNEXPP
B1_EXC ER ODUFLEX_PM_DEG
BWUTILIZATION_OVE
R OCh_OCI ODUFLEX_TCMn_SSF
ETH_APS_PATH_MISM
ATCH ODU0_PM_AIS ODU_SNCP_STA_INDI
ETH_APS_SWITCH_FA
IL ODU0_PM_BDI OH_LOOP
ETH_APS_TYPE_MISM
ATCH ODU0_PM_DEG OPA_FAIL_INDI
ELAN_SMAC_FLAPPI
NG ODU0_TCMn_LCK OTU2_BDI
LASER_MODULE_MIS
MATCH ODU1_TCMn_LTC PW_NO_TRAFFIC
MCLAG_CFG_MISMAT
CH ODU1_TCMn_TIM R_LOS
MPLS_PW_RDI ODU2_PM_OCI TD
MPLS_PW_UNEXPME
G ODU2_TCMn_AIS TEM_LA
MPLS_PW_UNEXPMEP ODU2_TCMn_BDI TF
TUNNEL_APS_DEGRADE
MPLS_TUNNEL_AIS ODU2_TCMn_LCK D
MPLS_TUNNEL_OAMF
AIL ODU2_TCMn_OCI WAVEDATA_MIS
MPLS_TUNNEL_SD ODU2_TCMn_TIM
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
BWUTILIZATION_OVE
R ODU0_PM_AIS ODUFLEX_PM_TIM
ETH_APS_PATH_MISM
ATCH ODU0_PM_SSF ODUFLEX_TCMn_LTC
ETH_APS_SWITCH_FA
IL ODU0_PM_TIM ODUFLEX_TCMn_OCI
ETH_APS_TYPE_MISM
ATCH ODU0_TCMn_AIS ODUFLEX_TCMn_SSF
ELAN_SMAC_FLAPPI
NG ODU1_LOFLOM OPU0_PLM
MCLAG_CFG_MISMAT
CH ODU2_PM_DEG PWAPS_LOST
MPLS_PW_UNEXPME
G ODU2_TCMn_LCK R_LOF
MPLS_TUNNEL_OAMF
AIL ODU3_PM_AIS SWDL_BD_NOT_MATCH
MPLS_TUNNEL_RDI ODU3_PM_BDI TD
MPLS_TUNNEL_SF ODU3_PM_LCK TF
MPLS_TUNNEL_UNEX
PMEG ODU3_PM_OCI TR_LOC
MPLS_TUNNEL_UNEX TUNNEL_APS_DEGRADE
PMEP ODU3_PM_SSF D
MPLS_TUNNEL_UNEX
PPER ODU3_PM_TIM TUNNEL_APS_OUTAGE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
TN11ITL
OMS_FDI OMS_SSF_O
TN12ITL
OMS_BDI OMS_SSF
OMS_BDI_O OMS_SSF_O
OCh_SSF_P ODU5G_TCM4_OCI TD
ODU5G_PM_DEG ODU5G_TCM5_BDI TF
OCh_OCI ODU1_TCM4_LTC TD
ODU1_LOFLOM ODU1_TCM5_AIS TF
OCh_OCI ODU1_TCM4_LTC TD
ODU1_LOFLOM ODU1_TCM5_AIS TF
ODU1_PM_DEG ODU1_TCM5_EXC
ODU1_PM_EXC ODU1_TCM5_LCK
OCh_SSF ODU1_TCM4_LTC TD
ODU1_PM_AIS ODU1_TCM5_AIS TF
ODU1_PM_LCK ODU1_TCM5_LCK
ODU1_PM_OCI ODU1_TCM5_LTC
OCh_SSF ODU1_TCM4_LCK TD
ODU1_PM_AIS ODU1_TCM4_TIM TF
ODU1_PM_LCK ODU1_TCM5_EXC
ODU1_PM_OCI ODU1_TCM5_LCK
ODU1_PM_SSF ODU1_TCM5_LTC
ODU1_LOFLOM ODU1_TCM4_SSF TD
ODU1_PM_EXC ODU1_TCM5_DEG TF
OCh_SSF_P ODU2_TCM4_TIM TD
ODU2_PM_LCK ODU2_TCM5_LCK TF
LASER_MODULE_MISM
BEFFEC_EXC ATCH OTU2_DEG
CLIENT_PORT_STA_IN
DI LPT_ACTIVE OTU2_SSF
CLIENT_PROT_NOTSTA
RT LPT_RFI OTU2_TIM
PORT_MODULE_OFFLIN
ERPS_IN_PROTECTION LSR_WILL_DIE E
ETHOAM_DISCOVER_F
AIL MULTI_RPL_OWNER PRBS_LSS
ETHOAM_RMT_CRIT_F
AULT NO_BD_SOFT REM_SD
ETHOAM_VCG_SELF_L
OOP ODU2_PM_BDI R_LOS
ETH_CFM_MISMERGE ODU2_PM_OCI TD
ETH_SERVICE_CONFIG
_FAIL ODU2_TCMn_AIS TEM_LA
EX_ETHOAM_CC_LOS ODU2_TCMn_BDI TF
EX_ETHOAM_MPID_CN
FLCT ODU2_TCMn_DEG VLAN_SNCP_PS
HARD_BAD ODU2_TCMn_OCI
HARD_ERR ODU2_TCMn_SSF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LASER_MODULE_MISMA
BEFFEC_EXC TCH OTU2_DEG
CLIENT_PORT_STA_IN
DI LPT_ACTIVE OTU2_SSF
CLIENT_PROT_NOTST
ART LPT_RFI OTU2_TIM
ERPS_IN_PROTECTIO
N LSR_WILL_DIE PORT_MODULE_OFFLINE
ETHOAM_DISCOVER_
FAIL MULTI_RPL_OWNER PRBS_LSS
ETHOAM_RMT_CRIT_
FAULT NO_BD_SOFT REM_SD
ETHOAM_VCG_SELF_
LOOP ODU2_PM_BDI R_LOS
ETH_CFM_MACSTATU
S ODU2_PM_LCK SWDL_BD_NOT_MATCH
ETH_CFM_MISMERGE ODU2_PM_OCI TD
ETH_SERVICE_CONFI
G_FAIL ODU2_TCMn_AIS TEM_LA
EX_ETHOAM_CC_LOS ODU2_TCMn_BDI TF
EX_ETHOAM_MPID_C
NFLCT ODU2_TCMn_DEG VLAN_SNCP_PS
HARD_BAD ODU2_TCMn_OCI
HARD_ERR ODU2_TCMn_SSF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
CLIENT_PORT_STA_IN
DI ODU1_PM_SSF OPUFLEX_PLM
CLIENT_PROT_NOTST
ART ODU1_PM_TIM OTU1_AIS
LASER_MODULE_MIS
MATCH ODU1_TCMn_TIM OTU2_BDI
OCh_SSF_P ODUFLEX_PM_DEG TD
ODU0_PM_DEG ODUFLEX_PM_TIM TF
FC_AIS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
CLIENT_PORT_STA_IN
DI OCh_SSF_O OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART OCh_SSF_P OUT_PWR_LOW
LASER_MODULE_MIS
MATCH ODU2_PM_SSF SWDL_BD_MATCH_FAIL
LSR_COOL_ALM ODU2_TCMn_DEG TD
MS_SNCP_PS ODU2_TCMn_SSF TF
NO_ELABEL OPU2_PLM
NULL_SEND OTU2_AIS
TN11LOG
ALS_ACTIVE ODU2_PM_OCI ODU2_TCM5_LTC
OCh_SSF_O ODU2_TCM4_OCI TD
ODU2_PM_BDI ODU2_TCM5_BDI TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
OCh_SSF ODU2_TCM4_OCI TD
ODU2_PM_BDI ODU2_TCM5_BDI TF
OCh_SSF ODU5G_TCM4_OCI TD
ODU5G_PM_AIS ODU5G_TCM5_BDI TF
ODU5G_PM_EXC ODU5G_TCM5_LCK
ODU5G_PM_LCK ODU5G_TCM5_LTC
OCh_OCI ODU1_TCM4_OCI TD
ODU1_LOFLOM ODU1_TCM5_BDI TF
ODU1_PM_EXC ODU1_TCM5_LTC
ODU1_PM_LCK ODU1_TCM5_OCI
TN11LQMD
ALS_ACTIVE ODU1_PM_LCK ODU1_TCM5_LTC
OCh_SSF ODU1_TCM4_OCI TD
ODU1_PM_AIS ODU1_TCM5_BDI TF
OCh_SSF_O ODU1_TCM4_TIM TD
ODU1_PM_BDI ODU1_TCM5_EXC TF
ODU1_PM_OCI ODU1_TCM5_SSF
ODU1_PM_SSF ODU1_TCM5_TIM
TN11LQMS
ALS_ACTIVE ODU1_PM_SSF ODU1_TCM5_SSF
OCh_SSF ODU1_TCM4_OCI TD
ODU1_PM_AIS ODU1_TCM5_BDI TF
ODU1_PM_LCK ODU1_TCM5_LTC
ODU1_PM_OCI ODU1_TCM5_OCI
LPT_ACTIVE ODU1_TCMn_LCK TD
ODU1_PM_BDI ODU1_TCMn_TIM TF
MS_SNCP_STA_INDI OTU1_BDI
CLIENT_PORT_STA_IN
DI OCHM_SSF_O OTU4_SSF
CLIENT_PROT_NOTST
ART OCHM_SSF_P OTU4_TIM
LASER_MODULE_MIS
MATCH ODU4_TCMn_BDI R_LOS
LOOP_ALM ODU4_TCMn_LTC TD
NO_BD_SOFT ODU4_TCMn_TIM TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
CLIENT_PORT_STA_IN
DI OCh_SSF OTU4_SSF
CLIENT_PROT_NOTST
ART OCh_SSF_O OTU4_TIM
LASER_MODULE_MIS
MATCH ODU4_TCMn_AIS RX_POWER_ABNORMAL
LASER_TYPE_MISMA
TCH ODU4_TCMn_DEG SWDL_BD_MATCH_FAIL
LOL ODU4_TCMn_LTC TD
NO_BD_PARA ODU4_TCMn_TIM TF
TN17LSC
ALS_ACTIVE OCh_FDI_O OTU4_BDI
CLIENT_PORT_STA_IN
DI OCh_SSF_P OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU4_PM_AIS OUT_PWR_LOW
LASER_MODULE_MIS
MATCH ODU4_TCMn_DEG SWDL_BD_MATCH_FAIL
LOL ODU4_TCMn_LTC TD
NO_BD_PARA ODU4_TCMn_TIM TF
NULL_SEND OPU4_PLM
OCh_FDI OTU4_AIS
TN15LSC
ALS_ACTIVE OCh_FDI_O OTU4_BDI
CLIENT_PORT_STA_IN
DI OCh_SSF_P OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU4_PM_AIS OUT_PWR_LOW
LASER_MODULE_MIS
MATCH ODU4_TCMn_DEG SWDL_BD_MATCH_FAIL
LOL ODU4_TCMn_LTC TD
NO_BD_PARA ODU4_TCMn_TIM TF
NULL_SEND OPU4_PLM
OCh_FDI OTU4_AIS
TN13LSC
ALS_ACTIVE OCh_FDI OPU4_PLM
CLIENT_PORT_STA_IN
DI OCh_SSF_O OTU4_SSF
CLIENT_PROT_NOTST
ART OCh_SSF_P OTU4_TIM
LASER_MODULE_MIS
MATCH ODU4_TCMn_BDI R_LOS
LOOP_ALM ODU4_TCMn_LTC TD
NO_BD_SOFT ODU4_TCMn_TIM TF
NULL_SEND OPU4_CSF
TN12LSC
ALS_ACTIVE OCh_FDI_P OTU4_BDI
CLIENT_PORT_STA_IN
DI ODU4_PM_AIS OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU4_PM_BDI OUT_PWR_LOW
LASER_MODULE_MIS
MATCH ODU4_TCMn_BDI R_LOS
LOOP_ALM ODU4_TCMn_LCK TD
NO_ELABEL ODU4_TCMn_SSF TF
OCh_FDI OPA_FAIL_INDI
OCh_FDI_O OPU4_PLM
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU3_PM_LCK ODU3_TCM5_AIS TD
ODU3_PM_SSF ODU3_TCM5_DEG TF
ODU3_TCM1_BDI ODU3_TCM5_LTC
ODU3_PM_SSF ODU3_TCM4_SSF TD
ODU3_TCM1_DEG ODU3_TCM5_DEG TF
TN12LSXLR
BD_LEDTEST ODU3_TCM1_OCI ODU3_TCM5_SSF
ODU3_PM_SSF ODU3_TCM4_TIM TD
ODU3_TCM1_AIS ODU3_TCM5_BDI TF
ODU3_TCM1_LCK ODU3_TCM5_LTC
ODU3_TCM1_LTC ODU3_TCM5_OCI
LSR_WILL_DIE ODU3_TCMn_OCI TD
OCh_FDI_O OPU3_PLM TF
TN12LSXL
ALS_ACTIVE OCh_FDI_P OTU3_AIS
LSR_WILL_DIE ODU3_TCMn_OCI TD
NO_ELABEL ODU3_TCMn_TIM TF
OCh_FDI_O OPU3_PLM
TN15LSXL
ALS_ACTIVE OCh_LOS_P OTU3_BDI
CLIENT_PORT_STA_IN
DI ODU3_PM_DEG OUT_PWR_LOW
CLIENT_PROT_NOTST
ART ODU3_PM_LCK PORT_MODULE_OFFLINE
NO_ELABEL ODU3_TCMn_SSF TD
OCh_FDI OPA_FAIL_INDI TF
OCh_FDI_P OTU3_AIS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU2_PM_SSF ODU2_TCM4_SSF TD
ODU2_TCM1_DEG ODU2_TCM5_DEG TF
ODU2_TCM1_OCI ODU2_TCM5_OCI
OCh_SSF_P ODU2_TCM4_TIM TD
ODU2_PM_LCK ODU2_TCM5_LCK TF
TN12LSX
ALS_ACTIVE ODU2_PM_TIM ODU2_TCM5_TIM
OCh_SSF ODU2_TCM4_SSF TD
ODU2_PM_BDI ODU2_TCM5_DEG TF
ODU2_PM_OCI ODU2_TCM5_OCI
ODU2_PM_SSF ODU2_TCM5_SSF
TN13LSX
ALS_ACTIVE ODU2_PM_TIM ODU2_TCM5_TIM
OCh_SSF ODU2_TCM4_SSF TD
ODU2_PM_BDI ODU2_TCM5_DEG TF
ODU2_PM_OCI ODU2_TCM5_OCI
ODU2_PM_SSF ODU2_TCM5_SSF
TN14LSX
ALS_ACTIVE OCh_FDI OTU2_AIS
CLIENT_PORT_STA_IN
DI OCh_SSF_P OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU2_PM_AIS OUT_PWR_LOW
LASER_MODULE_MIS
MATCH ODU2_TCMn_AIS R_LOC
LSR_INVALID ODU2_TCMn_OCI TD
L_SYNC ODU2_TCMn_TIM TF
NULL_SEND OPU2_PLM
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
CLIENT_PORT_STA_IN
DI ODU2_PM_DEG OTU4_SSF
CLIENT_PROT_NOTST
ART ODU2_PM_LCK OTU4_TIM
LASER_MODULE_MIS
MATCH ODU4_PM_LCK REM_SF
RMON_ALM_INBADOCTS
LASER_SHUT ODU4_PM_OCI _OVER
NO_ELABEL ODU4_TCMn_LTC TD
OCh_FDI ODU4_TCMn_SSF TF
OCh_FDI_P OPA_FAIL_INDI
OCh_LOS_P OPU2_PLM
TN12LTX
ALS_ACTIVE ODU2_PM_AIS OPU4_LOOMFI
CLIENT_PORT_STA_IN
DI ODU2_TCMn_AIS OTU2_TIM
CLIENT_PROT_NOTST
ART ODU2_TCMn_BDI OTU4_AIS
LASER_MODULE_MIS
MATCH ODU4_PM_AIS OUT_PWR_HIGH
RMON_ALM_INBADOCTS
NO_BD_SOFT ODU4_TCMn_AIS _OVER
OCh_OCI ODU4_TCMn_TIM TD
OCh_SSF_O OPU2_PLM TF
ODU2_LOFLOM OPU4_PLM
TN15LTX
ALS_ACTIVE ODU2_PM_TIM OPU2_MSIM
CLIENT_PORT_STA_IN
DI ODU2_TCMn_SSF OTU2_BDI
CLIENT_PROT_NOTST
ART ODU2_TCMn_TIM OTU2_DEG
LASER_MODULE_MIS
MATCH ODU4_TCMn_AIS OTU4_LOF
RMON_ALM_INBADOCTS
OCh_FDI ODUFLEX_PM_DEG _OVER
ODU2_LOFLOM ODUFLEX_TCMn_LCK TD
ODU2_PM_BDI ODUFLEX_TCMn_OCI TF
ODU2_PM_OCI OPA_FAIL_INDI
ODU2_PM_SSF OPU2_CSF
TN17LTX
ALS_ACTIVE ODU2_PM_TIM OPU2_MSIM
CLIENT_PORT_STA_IN
DI ODU2_TCMn_SSF OTU2_BDI
CLIENT_PROT_NOTST
ART ODU2_TCMn_TIM OTU2_DEG
LASER_MODULE_MIS
MATCH ODU4_TCMn_AIS OTU4_LOF
RMON_ALM_INBADOCTS
OCh_FDI ODUFLEX_PM_DEG _OVER
ODU2_LOFLOM ODUFLEX_TCMn_LCK TD
ODU2_PM_BDI ODUFLEX_TCMn_OCI TF
ODU2_PM_OCI OPA_FAIL_INDI
ODU2_PM_SSF OPU2_CSF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
PORT_MODULE_OFFLI
B1_EXC LSR_INVALID NE
HARD_BAD OCh_LOS_P TD
J0_MM OCh_SSF_P TF
PORT_MODULE_OFFLI
B1_EXC LSR_COOL_ALM NE
HARD_BAD OCh_FDI_P TD
IN_PWR_HIGH OCh_SSF_O TF
LASER_MODULE_MISMA OUT_PWR_HIGH
TCH
PORT_MODULE_OFFLI
B1_EXC LSR_INVALID NE
HARD_BAD OCh_LOS_P TD
J0_MM OCh_SSF_P TF
TN12LWXS
LSR_COOL_ALM PORT_MODULE_OFFLI
ALS_ACTIVE NE
COMMUN_FAIL OCh_LOS_P TD
IN_PWR_LOW OCh_SSF_P TF
LOOP_ALM OUT_PWR_LOW
MODULEFILE_UPDAT
E_FAIL OPA_FAIL_INDI WRG_BD_TYPE
TN12M40V
MODULEFILE_UPDAT
E_FAIL OPA_FAIL_INDI WRG_BD_TYPE
TN11M40V
HARD_ERR OPA_FAIL_INDI
MODULE_COOLCUR_OV SWDL_BD_MATCH_FAIL
ER
MODULEFILE_UPDATE
_FAIL OPA_FAIL_INDI WRG_BD_TYPE
COMMUN_FAIL PORTSWITCH_FAIL
HARD_BAD SWDL_BD_MATCH_FAIL
COMMUN_FAIL PORTSWITCH_FAIL
HARD_BAD SWDL_BD_MATCH_FAIL
MCS_SWITCH_BLOCK
ED OMS_FDI_P SWDL_BD_NOT_MATCH
MODULEFILE_UPDAT
E_FAIL OMS_LOS_P TEMP_OVER
MODULE_TEMP_OVE
R OMS_PMI VOADATA_MIS
NO_BD_SOFT OMS_SSF_P
NO_ELABEL OPA_FAIL_INDI
OMS_BDI_P OMS_SSF_O
OMS_FDI OMS_SSF_P
OMS_BDI_P OMS_SSF_O
OMS_FDI OMS_SSF_P
OMS_BDI_O OMS_SSF_O
TN12MR8V
NO_ELABEL OMS_SSF_O
OMS_BDI OMS_SSF_P
OMS_BDI_P OMS_SSF_O
OMS_FDI OMS_SSF_P
LASER_MODULE_MIS
MATCH ODU1_PM_SSF OPA_FAIL_INDI
ODU0_PM_LCK ODU2_TCMn_DEG TD
ODU0_TCMn_AIS ODU2_TCMn_SSF TF
ODU0_TCMn_LCK ODUFLEX_PM_AIS
ODU0_TCMn_LTC ODUFLEX_PM_BDI
TN53ND2(COMP)
BD_LEDTEST ODU0_PM_TIM ODU2_TCMn_TIM
LASER_MODULE_MISMATC
H ODU1_TCMn_AIS OPU2_PLM
PORT_MODULE_OFFL
OCh_LOS_P ODU2_PM_DEG INE
SWDL_BD_MATCH_FA
OCh_SSF_O ODU2_PM_SSF IL
SWDL_BD_NOT_MAT
OCh_SSF_P ODU2_PM_TIM CH
ODU0_LOFLOM ODU2_TCMn_AIS TD
ODU0_PM_LCK ODU2_TCMn_LTC TF
TN52ND2
ODU1_TCM2_LCK ODU2_TCM2_OCI TD
ODU1_TCM2_TIM ODU2_TCM3_BDI TF
ODU1_TCM3_DEG ODU2_TCM3_LTC
ODU1_TCM3_LCK ODU2_TCM3_OCI
TN52ND2(STND)
BD_LEDTEST ODU0_TCMn_LTC ODUFLEX_PM_AIS
LASER_MODULE_MIS
MATCH ODU1_PM_OCI ODU_SNCP_PS
ODU0_PM_DEG ODU2_TCMn_AIS TD
ODU0_PM_TIM ODU2_TCMn_LTC TF
ODU0_TCMn_DEG ODU2_TCMn_TIM
ODU0_TCMn_LCK ODUFLEX_LOFLOM
TN12ND2
BD_LEDTEST ODU1_TCM4_AIS ODU2_TCM4_AIS
ODU1_TCM2_TIM ODU2_TCM2_TIM TD
ODU1_TCM3_LCK ODU2_TCM3_LCK TF
ODU1_TCM3_SSF ODU2_TCM3_SSF
ODU1_TCM3_TIM ODU2_TCM3_TIM
TN11ND2
BD_LEDTEST ODU1_TCM4_AIS ODU2_TCM3_TIM
ODU1_TCM3_BDI ODU2_TCM3_AIS TD
ODU1_TCM3_OCI ODU2_TCM3_LTC TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LASER_MODULE_MIS
MATCH ODU1_PM_TIM OPU2_PLM
ODU0_PM_AIS ODU2_PM_TIM TD
ODU0_PM_DEG ODU2_TCMn_BDI TF
TN55NO2(REG)
LASER_MODULE_MIS
MATCH ODU2_TCMn_AIS PORT_MODULE_OFFLINE
OCh_FDI ODU2_TCMn_LTC TD
OCh_FDI_P ODU2_TCMn_SSF TF
OCh_SSF OPU2_PLM
OCh_SSF_O OTU2_AIS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
SWDL_BD_MATCH_FA
ODU0_PM_AIS ODU2_PM_TIM IL
SWDL_BD_NOT_MAT
ODU0_PM_BDI ODU2_TCMn_AIS CH
ODU0_PM_DEG ODU2_TCMn_BDI TD
ODU0_PM_TIM ODU2_TCMn_OCI TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
SWDL_BD_MATCH_FA
ODU0_PM_AIS ODU2_PM_TIM IL
SWDL_BD_NOT_MAT
ODU0_PM_BDI ODU2_TCMn_AIS CH
ODU0_PM_DEG ODU2_TCMn_BDI TD
ODU0_PM_TIM ODU2_TCMn_OCI TF
TN55NPO2
BD_LEDTEST ODU1_LOFLOM OMS_BDI
EXT_MODULE_OFFLI
NE ODU1_PM_OCI OMS_FDI_P
MAINBD_SUBBD_MIS
MATCH ODU1_TCMn_OCI OPU2_MSIM
ODU0_PM_AIS ODU2_TCMn_OCI TD
ODU0_PM_OCI ODUKSP_STA_INDI TF
TN54NPO2
BD_LEDTEST ODU1_TCM3_LTC ODU2_TCM4_LCK
ODU1_TCM2_LTC ODU2_TCM3_LCK TD
ODU1_TCM3_AIS ODU2_TCM3_TIM TF
ODU1_TCM3_LCK ODU2_TCM4_DEG
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU1_PM_LCK ODU4_PM_TIM TD
ODU1_PM_SSF ODU4_TCMn_BDI TF
ODU1_TCMn_BDI ODU4_TCMn_LTC
ODU1_TCMn_DEG ODU4_TCMn_OCI
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU1_PM_OCI ODU4_PM_TIM TD
ODU1_PM_TIM ODU4_TCMn_BDI TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LASER_MODULE_MIS
MATCH ODU1_PM_SSF OPA_FAIL_INDI
ODU0_PM_LCK ODU2_TCMn_DEG TD
ODU0_TCMn_AIS ODU2_TCMn_SSF TF
ODU0_TCMn_LCK ODUFLEX_PM_AIS
ODU0_TCMn_LTC ODUFLEX_PM_BDI
TN53NQ2(COMP)
BD_STATUS ODU1_LOFLOM ODUKSP_PS
PORT_MODULE_OFFL
OCh_LOS_P ODU2_PM_DEG INE
SWDL_BD_MATCH_FA
OCh_SSF_O ODU2_PM_SSF IL
SWDL_BD_NOT_MAT
OCh_SSF_P ODU2_PM_TIM CH
ODU0_LOFLOM ODU2_TCMn_AIS TD
ODU0_PM_LCK ODU2_TCMn_LTC TF
ODU0_PM_TIM ODU2_TCMn_TIM
TN54NQ2
BD_LEDTEST ODU1_TCM3_LCK ODU2_TCM3_SSF
ODU1_TCM2_DEG ODU2_TCM2_OCI TD
ODU1_TCM2_SSF ODU2_TCM3_BDI TF
ODU1_TCM3_BDI ODU2_TCM3_LTC
ODU1_TCM3_DEG ODU2_TCM3_OCI
TN52NQ2
BD_LEDTEST ODU1_TCM3_LCK ODU2_TCM3_SSF
ODU1_TCM2_DEG ODU2_TCM2_OCI TD
ODU1_TCM2_SSF ODU2_TCM3_BDI TF
ODU1_TCM3_BDI ODU2_TCM3_LTC
ODU1_TCM3_DEG ODU2_TCM3_OCI
TN51NQ2
BD_LEDTEST ODU1_TCM3_TIM ODU2_TCM3_TIM
ODU1_TCM2_SSF ODU2_TCM2_SSF TD
ODU1_TCM3_DEG ODU2_TCM3_DEG TF
ODU1_TCM3_OCI ODU2_TCM3_OCI
ODU1_TCM3_SSF ODU2_TCM3_SSF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LASER_MODULE_MIS
MATCH ODU1_PM_OCI ODU_SNCP_PS
ODU0_PM_SSF ODU2_TCMn_LCK TD
ODU0_TCMn_DEG ODU2_TCMn_TIM TF
TN53NS2(COMP)
BD_STATUS ODU1_LOFLOM ODUKSP_PS
LASER_MODULE_MISMATC
H ODU1_TCMn_AIS OPU2_PLM
PORT_MODULE_OFFL
OCh_LOS_P ODU2_PM_DEG INE
SWDL_BD_MATCH_FA
OCh_SSF_O ODU2_PM_SSF IL
SWDL_BD_NOT_MAT
OCh_SSF_P ODU2_PM_TIM CH
ODU0_LOFLOM ODU2_TCMn_AIS TD
ODU0_PM_LCK ODU2_TCMn_LTC TF
ODU0_PM_TIM ODU2_TCMn_TIM
TN52NS2
BD_LEDTEST ODU1_TCM3_LCK ODU2_TCM3_OCI
ODU1_TCM2_LTC ODU2_TCM2_SSF TD
ODU1_TCM3_AIS ODU2_TCM3_DEG TF
TN52NS2(STND)
BD_LEDTEST ODU0_TCMn_LTC ODUFLEX_LOFLOM
LASER_MODULE_MIS
MATCH ODU1_PM_OCI ODUKSP_STA_INDI
ODU0_PM_TIM ODU2_TCMn_LCK TD
ODU0_TCMn_BDI ODU2_TCMn_OCI TF
TN12NS2
BD_LEDTEST ODU1_TCM4_AIS ODU2_TCM3_TIM
ODU1_TCM3_BDI ODU2_TCM3_AIS TD
ODU1_TCM3_OCI ODU2_TCM3_LTC TF
TN11NS2
BD_LEDTEST ODU1_TCM4_BDI ODU2_TCM4_AIS
ODU1_TCM3_AIS ODU2_TCM2_TIM TD
ODU1_TCM3_LTC ODU2_TCM3_LCK TF
ODU1_TCM3_TIM ODU2_TCM3_SSF
ODU1_TCM4_AIS ODU2_TCM3_TIM
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU0_PM_DEG ODU3_TCMn_AIS TD
ODU0_PM_OCI ODU3_TCMn_DEG TF
ODU0_TCMn_AIS ODU3_TCMn_OCI
TN55NS3
BD_LEDTEST ODU1_PM_LCK ODU3_TCMn_AIS
ODU1_LOFLOM ODU3_PM_LCK TD
ODU1_PM_BDI ODU3_PM_SSF TF
TN54NS3/TN54NS3(STND)
BD_LEDTEST ODU1_PM_LCK ODU3_TCMn_BDI
LASER_MODULE_MIS
MATCH ODU1_TCMn_OCI ODU_SNCP_PS
MODULE_RATE_MISM
ATCH ODU2_PM_AIS OPU1_PLM
ODU0_PM_OCI ODU3_PM_BDI TD
ODU1_PM_AIS ODU3_PM_OCI TF
ODU1_PM_EXC ODU3_TCMn_AIS
TN52NS3
BD_LEDTEST ODU1_PM_SSF ODU3_TCMn_LTC
ODU0_PM_SSF ODU3_PM_LCK TD
ODU1_PM_BDI ODU3_TCMn_AIS TF
ODU1_PM_OCI ODU3_TCMn_LCK
TN11NS3
ODU3_PM_AIS ODU3_TCM4_SSF TD
ODU3_PM_DEG ODU3_TCM5_AIS TF
ODU3_PM_SSF ODU3_TCM5_LCK
ODU3_PM_TIM ODU3_TCM5_LTC
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU1_TCMn_DEG ODU4_TCMn_DEG TD
ODU1_TCMn_LTC ODU4_TCMn_LTC TF
ODU1_TCMn_TIM ODU4_TCMn_TIM
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU1_PM_LCK ODU4_TCMn_AIS TD
ODU1_PM_SSF ODU4_TCMn_DEG TF
ODU1_TCMn_AIS ODU4_TCMn_LTC
ODU1_TCMn_BDI ODU4_TCMn_OCI
ODU1_TCMn_DEG ODU4_TCMn_SSF
TN97NS4
BD_BPXC_MISMATCH ODU1_TCMn_AIS ODU4_TCMn_LCK
ODU1_PM_DEG ODU4_PM_SSF TD
ODU1_PM_OCI ODU4_TCMn_AIS TF
TN58NS4
BD_BPXC_MISMATCH ODU1_TCMn_BDI ODU4_TCMn_LTC
ODU1_PM_OCI ODU4_TCMn_AIS TD
ODU1_PM_TIM ODU4_TCMn_DEG TF
TN57NS4
BD_BPXC_MISMATCH ODU1_TCMn_DEG ODU4_TCMn_SSF
ODU1_PM_LCK ODU4_TCMn_AIS TD
ODU1_PM_SSF ODU4_TCMn_DEG TF
ODU1_TCMn_AIS ODU4_TCMn_LTC
ODU1_TCMn_BDI ODU4_TCMn_OCI
TN56NS4
BD_BPXC_MISMATCH ODU1_TCMn_BDI ODU4_TCMn_LCK
ODU1_PM_DEG ODU4_PM_OCI TD
ODU1_PM_OCI ODU4_PM_TIM TF
ODU1_PM_TIM ODU4_TCMn_BDI
ODU1_TCMn_AIS ODU4_TCMn_DEG
TN54NS4
BD_LEDTEST ODU1_TCMn_BDI ODU4_TCMn_BDI
ODU1_PM_DEG ODU4_PM_DEG TD
ODU1_PM_OCI ODU4_PM_OCI TF
ODU1_PM_TIM ODU4_PM_TIM
ODU1_TCMn_AIS ODU4_TCMn_AIS
TN54NS4(REG)
BD_LEDTEST OCh_SSF_O OPU4_PLM
OCh_FDI_P ODU4_TCMn_SSF TD
OCh_OCI OPA_FAIL_INDI TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
INSERTION_LOSS_HIG OSNR_LOSS_UNBALANC
H ED TEMP_OVER
LASER_HAZARD_WA
RNING PUMP_COOL_EXC VOADATA_MIS
NO_BD_SOFT PWR_UNBALANCED
SPAN_LOSS_EXCEED_EO
NO_ELABEL L
TN12OAU1
BD_LEDTEST PWR_UNBALANCED PUM_BCM_ALM
OMS_LOSS_MON_FAI
L NO_ELABEL SUM_INPWR_HI
OMS_LOSS_ACCUM_A
BN OA_LOW_GAIN SUM_INPWR_LOW
SPAN_LOSS_EXCEED_
EOL OA_OUT_PWR_ABN SWDL_BD_MATCH_FAIL
OSNR_LOSS_UNBALANC
HARD_BAD ED TEMP_OVER
INSERTION_LOSS_HIG SPAN_LOSS_LOWER_GAI
H N WAVEDATA_MIS
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WRG_BD_TYPE
TN11OAU1
BD_LEDTEST MUT_LOS PUM_TEM_ALM
INSERTION_LOSS_HIG OSNR_LOSS_UNBALANC
H ED TEMP_OVER
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WAVEDATA_MIS
SPAN_LOSS_EXCEED_EO
BD_STATUS OMS_LOSS_ACCUM_ABN L
SPAN_LOSS_LOWER_GAI
HARD_BAD ONE_PUMP_WORK N
OSNR_LOSS_UNBALANC
LSR_WILL_DIE ED SUM_INPWR_HI
MODULEFILE_UPDAT
E_FAIL PUMP_COOL_EXC SUM_INPWR_LOW
MODULE_TEMP_OVE PUMP_LINK_ULLAGE_HI
R GH SWDL_BD_MATCH_FAIL
SPAN_LOSS_LOWER_GAI
BD_STATUS OMS_LOSS_ACCUM_ABN N
OSNR_LOSS_UNBALANC
HARD_ERR ED SWDL_BD_MATCH_FAIL
LASER_HAZARD_WA
RNING PUMP_COOL_EXC SWDL_BD_NOT_MATCH
SPAN_LOSS_EXCEED_EO
NO_ELABEL L WRG_BD_TYPE
OA_LOW_GAIN SPAN_LOSS_HIGH
TN13OBU1
BD_LEDTEST OA_OUT_PWR_ABN SPAN_LOSS_LOW
SPAN_LOSS_LOWER_GAI
BD_STATUS OMS_LOSS_ACCUM_ABN N
OSNR_LOSS_UNBALANC
HARD_ERR ED SWDL_BD_MATCH_FAIL
LASER_HAZARD_WA
RNING PUMP_COOL_EXC SWDL_BD_NOT_MATCH
SPAN_LOSS_EXCEED_EO
NO_ELABEL L WRG_BD_TYPE
OA_LOW_GAIN SPAN_LOSS_HIGH
TN12OBU1
BD_LEDTEST PWR_UNBALANCED PUMP_COOL_EXC
OMS_LOSS_MON_FAI
L NO_ELABEL SPAN_LOSS_LOW
OMS_LOSS_ACCUM_A
BN OA_LOW_GAIN SUM_INPWR_HI
SPAN_LOSS_EXCEED_
EOL OA_OUT_PWR_ABN SUM_INPWR_LOW
OSNR_LOSS_UNBALANC
HARD_BAD ED VOADATA_MIS
LASER_HAZARD_WA SPAN_LOSS_LOWER_GAI
RNING N WRG_BD_TYPE
TN11OBU1
BD_LEDTEST NO_BD_PARA SPAN_LOSS_HIGH
OSNR_LOSS_UNBALANC
HARD_ERR ED TEMP_OVER
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WAVEDATA_MIS
MUT_LOS PUM_TEM_ALM
SPAN_LOSS_EXCEED_EO
BD_STATUS OMS_LOSS_ACCUM_ABN L
SPAN_LOSS_LOWER_GAI
HARD_BAD ONE_PUMP_WORK N
OSNR_LOSS_UNBALANC
LSR_WILL_DIE ED SUM_INPWR_HI
MODULEFILE_UPDAT
E_FAIL PUMP_COOL_EXC SUM_INPWR_LOW
MODULE_TEMP_OVE PUMP_LINK_ULLAGE_HI
R GH SWDL_BD_MATCH_FAIL
TN14OBU2
SPAN_LOSS_LOWER_GAI
BD_LEDTEST OMS_LOSS_ACCUM_ABN N
OSNR_LOSS_UNBALANC
HARD_BAD ED SWDL_BD_MATCH_FAIL
SPAN_LOSS_EXCEED_EO
NO_ELABEL L WRG_BD_TYPE
OA_LOW_GAIN SPAN_LOSS_HIGH
OA_OUT_PWR_ABN SPAN_LOSS_LOW
TN13OBU2
SPAN_LOSS_LOWER_GAI
BD_LEDTEST OMS_LOSS_ACCUM_ABN N
OSNR_LOSS_UNBALANC
HARD_BAD ED SWDL_BD_MATCH_FAIL
SPAN_LOSS_EXCEED_EO
NO_ELABEL L WRG_BD_TYPE
OA_LOW_GAIN SPAN_LOSS_HIGH
OA_OUT_PWR_ABN SPAN_LOSS_LOW
TN12OBU2
BD_LEDTEST MUT_LOS PUM_TEM_ALM
OMS_LOSS_MON_FAI
L OA_LOW_GAIN SUM_INPWR_LOW
OMS_LOSS_ACCUM_A
BN OA_OUT_PWR_ABN SWDL_BD_MATCH_FAIL
SPAN_LOSS_EXCEED_
EOL OPA_FAIL_INDI SWDL_BD_NOT_MATCH
OSNR_LOSS_UNBALANC
GAINDATA_MIS ED TEMP_OVER
SPAN_LOSS_LOWER_GAI
HARD_ERR N WAVEDATA_MIS
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WRG_BD_TYPE
PWR_UNBALANCED PUM_BCM_ALM
TN11OBU2
BD_LEDTEST NO_BD_PARA SPAN_LOSS_HIGH
OSNR_LOSS_UNBALANC
HARD_ERR ED TEMP_OVER
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WAVEDATA_MIS
MUT_LOS PUM_TEM_ALM
CLIENT_PORT_STA_IN
DI OCh_FDI POWER_DIFF_OVER
SPAN_LOSS_EXCEED_
EOL OCh_FDI_P SWDL_BD_MATCH_FAIL
INTRA_OTU_STA_IND
I OCh_SSF_O
MUT_LOS OCh_SSF_P
TN12OLP
BD_LEDTEST HARD_ERR OCh_SSF
CLIENT_PORT_STA_IN
DI MUT_LOS OLP_PS
SPAN_LOSS_EXCEED_
EOL OCh_FDI OPA_FAIL_INDI
TN13OLP
CLIENT_PORT_STA_IN
DI OCh_LOS_P OMS_SSF
SPAN_LOSS_EXCEED_EO
INTRA_OTU_PS OLP_STA_INDI L
INTRA_OTU_STA_IND
I OMS_BDI SWDL_BD_MATCH_FAIL
NO_ELABEL OMS_FDI_O
SPAN_LOSS_EXCEED_EO
COMMUN_FAIL OMS_PWR_ADJ_FAIL L
SPAN_LOSS_LOWER_GAI
HARD_BAD OTS_BDI N
OLP_PS OTS_PMI
OLP_STA_INDI OTS_TIM
SPAN_LOSS_EXCEED_EO
COMMUN_FAIL OMS_PWR_ADJ_FAIL L
SPAN_LOSS_LOWER_GAI
HARD_BAD OTS_BDI N
OLP_PS OTS_PMI
OLP_STA_INDI OTS_TIM
SPAN_LOSS_EXCEED_EO
COMMUN_FAIL OMS_PWR_ADJ_FAIL L
SPAN_LOSS_LOWER_GAI
HARD_BAD OTS_BDI N
OLP_PS OTS_PMI
OLP_STA_INDI OTS_TIM
COMMUN_FAIL PORTSWITCH_FAIL
TN12OPM8
COMMUN_FAIL PORTSWITCH_FAIL
TN15OPM8
COMMUN_FAIL PORTSWITCH_FAIL
TN97OPM8
MODULEFILE_UPDATE_F
BD_STATUS AIL SWDL_BD_NOT_MATCH
COMMUN_FAIL NO_ELABEL
HARD_BAD PORTSWITCH_FAIL
POWER_FAIL
BWUTILIZATION_OVE
R MCSP_PATH_LOCV ODU2_TCMn_TIM
ETH_APS_PATH_MISM
ATCH MPLS_PW_RDI OTU2_LOF
ETH_APS_SWITCH_FA
IL MPLS_PW_SD OTU2_LOM
ETH_APS_TYPE_MISM
ATCH MPLS_PW_SF OTU2_SSF
MPLS_TUNNEL_UNEXPM
ETH_EFM_EVENT EG PWAPS_LOST
MPLS_TUNNEL_UNEXPM
ETH_EFM_LOOPBACK EP PWAPS_PATH_MISMATCH
MPLS_TUNNEL_UNEXPP
ETH_EFM_REMFAULT ER PWAPS_SWITCH_FAIL
ELAN_SMAC_FLAPPI
NG MPLS_Tunnel_SF R_LOS
HARD_ERR ODU2_PM_DEG TD
IN_PWR_LOW ODU2_PM_OCI TF
TUNNEL_APS_DEGRADE
LAG_DOWN ODU2_PM_SSF D
LASER_MODULE_MIS
MATCH ODU2_TCMn_BDI WAVEDATA_MIS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU1_TCM2_LTC ODU2_TCM3_LCK TD
ODU1_TCM3_AIS ODU2_TCM3_TIM TF
ODU1_TCM3_LTC ODU2_TCM4_LCK
CLIENT_PORT_STA_IN
DI OCh_FDI R_LOS
SPAN_LOSS_EXCEED_EO
COMMUN_FAIL OCh_FDI_O L
INTRA_OTU_PS OCh_SSF_O
INTRA_OTU_STA_IND
I OCh_SSF_P
OMS_LOSS_ACCUM_A
BN NO_BD_SOFT SPAN_LOSS_HIGH
SPAN_LOSS_EXCEED_
EOL NO_ELABEL SPAN_LOSS_LOW
INSERTION_LOSS_HIG OSNR_LOSS_UNBALANC
H ED TEMP_OVER
LASER_HAZARD_WA
RNING SPAN_LOSS_UPPER_GAIN WRG_BD_TYPE
SPAN_LOSS_LOWER_GAI
LOCKPOW_MIS N
LSR_WILL_DIE PUMP_COOL_EXC
TN12RAU1
SPAN_LOSS_EXCEED_E
COMMUN_FAIL OA_OUT_PWR_ABN OL
OMS_LOSS_ACCUM_AB
FIBERTYPE_MIS N SPAN_LOSS_HIGH
SPAN_LOSS_LOWER_G
HARD_BAD OPA_FAIL_INDI AIN
OSNR_LOSS_UNBALAN SPAN_LOSS_UPPER_GA
HARD_ERR CED IN
LASER_HAZARD_WARNI
NG OTS_BDI_O SUM_INPWR_LOW
SWDL_BD_MATCH_FAI
LASER_OPEN_FAIL OTS_BDI_P L
MUT_LOS PUMP_COOL_EXC
NO_BD_PARA PUM_BCM_ALM
OMS_LOSS_ACCUM_A
BN NO_BD_SOFT RL_CRITICAL_HI
SPAN_LOSS_EXCEED_
EOL NO_ELABEL RL_CRITICAL_LOW
INSERTION_LOSS_HIG OSNR_LOSS_UNBALANC
H ED TEMP_OVER
LASER_HAZARD_WA
RNING SPAN_LOSS_UPPER_GAIN VOADATA_MIS
SPAN_LOSS_LOWER_GAI
LOCKPOW_MIS N WRG_BD_TYPE
LSR_WILL_DIE SWDL_BD_MATCH_FAIL
TN12RAU2
SPAN_LOSS_EXCEED_EO
FIBERTYPE_MIS OMS_LOSS_ACCUM_ABN L
OSNR_LOSS_UNBALANC
HARD_BAD ED SPAN_LOSS_LOW
SPAN_LOSS_LOWER_GAI
HARD_ERR OOS_LOST N
INSERTION_LOSS_HIG
H OTS_BDI SPAN_LOSS_UPPER_GAIN
LASER_HAZARD_WA
RNING OTS_BDI_O SUM_INPWR_HI
NO_BD_PARA PUMP_COOL_EXC
OMS_BDI OMS_SSF_O
OMS_BDI_O OMS_SSF_P
TN12RDU9
BD_LEDTEST OMS_BDI_O OPA_FAIL_INDI
NO_ELABEL OMS_SSF_O
OMS_BDI OMS_SSF_P
NO_ELABEL OMS_SSF_P
NO_BD_SOFT OMS_SSF_O
LASER_HAZARD_WA
RNING OTS_BDI_O PUM_TEM_ALM
MUT_LOS OTS_PMI
LASER_HAZARD_WA
RNING OTS_BDI_O RL_CRITICAL_HI
MUT_LOS OTS_TIM
TN97RPC
ALS_TRIGGERED MUT_LOS OTS_TIM
LASER_HAZARD_WA
RNING OTS_BDI_O RL_CRITICAL_HI
OPA_FAIL_INDI
HARD_ERR OSC_RDI TF
HARD_ERR OSC_RDI TF
SUBRACK_COMM_P
ALC_ADJUST_FAIL LCS_EXPIRED S
ALC_WAIT_ADJUST SUBRACK_ID_CONF
LCS_FILE_NOT_EXIST LICT
K2_M SUBNET_RT_CONFLICT
OSC_CLK_MISMATCH SCC_CHANGE
TN51SCC
LCS_FILE_NOT_EXIST SUBRACK_COMM_P
ALC_ADJUST_FAIL S
LCS_DAYS_OF_GRACE SSL_CERT_DAMAGED
LCS_EXPIRED SSL_CERT_TO_EXPIRE
TN11SCC
SUBRACK_TYPE_MISM
ALC_ADJUST_FAIL LCS_SHORTAGE_SHELF ATCH
ALC_WAIT_ADJUST SWDL_BD_MATCH_FAI
NESF_LOST L
LCS_FILE_NOT_EXIST SHELF_POWER_UNCONF
IG
TN22SCC/TN23SCC
SWDL_AUTOMATCH_I
ALC_ADJUST_FAIL PRO_PKT_FLOODING NH
ALC_WAIT_ADJUST SWDL_BD_MATCH_FAI
IPA_FAULT L
BD_LEDTEST SWDL_BD_NOT_MATC
LCS_DAYS_OF_GRACE H
BD_STATUS SWDL_BD_WEAKMATC
LCS_FILE_NOT_EXIST H
PATCH_BD_EXCLUDE PATCH_BD_MATCH_FAIL
TNK2SCC
SUBRACK_COMM_P
ALC_ADJUST_FAIL LCS_EXPIRED S
TN16SCC
ALC_ADJUST_FAIL LCS_SHORTAGE_SHELF SUBRACK_COMM_PS
SUBRACK_TYPE_MISMA
APS_INDI NESF_LOST TCH
SWDL_ACTIVATED_TIME
BD_LEDTEST NESTATE_INSTALL OUT
CFG_DATACHECK_FAI
L OOL SWDL_BD_WEAKMATCH
PASSWORD_NEED_CHAN SWDL_CHGMNG_NOMAT
CFG_DATASAVE_FAIL GE CH
CLK_NO_TRACE_MO
DE PATCH_BD_EXCLUDE SWDL_INPROCESS
PATCH_CHGSCC_NOTMA
COMMUN_FAIL TCH SUBRACK_EXCEED
DBMS_PROTECT_MO
DE PTP_TIMESTAMP_ABN SYNC_C_LOS
FEATURE_WITHOUT_ SERVICE_CAPACITY_EXC
LICENSE EED_LICENSE SYSLOG_COMM_FAIL
SERVICE_TYPE_EXCEED_ SYSPARA_CFDB_NOSAM
HARD_BAD LICENSE E
SHELF_AREA_POWER_O
HARD_ERR VER TEMP_OVER
STORM_CUR_QUENUM_O
K1_K2_M VER TIME_NO_TRACE_MODE
LCS_EXPIRED SSL_CERT_DAMAGED
LCS_FILE_NOT_EXIST SSL_CERT_TO_EXPIRE
OMS_BDI_P OMS_SSF
OMS_FDI OMS_SSF_O
HP_LOM OTU_LOM TF
HP_SLM PM_BIP8_OVER
HP_TIM PM_BIP8_SD
HP_LOM OTU_LOM TF
HP_TIM PM_BIP8_SD
HP_LOM OTU_LOM TF
HP_TIM PM_BIP8_SD
OMS_LOSS_MON_FAI
L OTS_BDI_O OTS_TIM
OMS_LOSS_ACCUM_A
BN OTS_BDI_P SPAN_LOSS_HIGH
SPAN_LOSS_EXCEED_
EOL OTS_LOS SPAN_LOSS_LOW
SPAN_LOSS_LOWER_GAI
OOS_LOST N WRG_BD_TYPE
FSELECT_STG MS_AIS TF
HP_LOM NO_BD_SOFT
FSELECT_STG MS_AIS TF
HP_LOM NO_BD_SOFT
FSELECT_STG MS_AIS TF
HP_LOM NO_BD_SOFT
FSELECT_STG MS_AIS TF
HP_LOM NO_BD_SOFT
FSELECT_STG MS_AIS TF
HP_LOM NO_BD_SOFT
FSELECT_STG MS_AIS TF
HP_LOM NO_BD_SOFT
SPAN_LOSS_EXCEED_EO
FIBERTYPE_MIS OMS_LOSS_MON_FAIL L
SPAN_LOSS_LOWER_GAI
HARD_ERR OPA_FAIL_INDI N
INSERTION_LOSS_HIG OSNR_LOSS_UNBALANC
H ED SPAN_LOSS_UPPER_GAIN
LASER_HAZARD_WA
RNING OTS_BDI SUM_INPWR_HI
NO_BD_PARA OTS_TIM
NO_BD_SOFT PUMP_COOL_EXC
COMMUN_FAIL OSC_BDI TD
HARD_ERR OSC_LOS TF
IN_PWR_LOW OUT_PWR_LOW
LASER_MODULE_MISMAT PORT_MODULE_OFFLI
CH NE
TN12ST2
PORT_MODULE_OFFLI
ALM_HANGUP LOOP_ALM NE
SWDL_BD_MATCH_FAI
BEFFEC_EXC NO_BD_SOFT L
SWDL_BD_NOT_MATC
COMMUN_FAIL NO_ELABEL H
HARD_BAD OSC_BDI TD
IN_PWR_HIGH OSC_LOS TF
LASER_MODULE_MISMAT
CH OUT_PWR_LOW
TN13ST2
SWDL_BD_MATCH_FAI
BD_STATUS NO_BD_SOFT L
SWDL_BD_NOT_MATC
BEFFEC_EXC NO_ELABEL H
COMMUN_FAIL OSC_BDI TD
HARD_ERR OSC_LOS TF
IN_PWR_LOW OUT_PWR_LOW
LASER_MODULE_MISMAT PORT_MODULE_OFFLI
CH NE
HARD_ERR SWDL_BD_NOT_MATCH
LTI SYNC_C_LOS
TNK3STG
BD_LEDTEST NO_BD_SOFT SYNC_C_LOS
CLK_NO_TRACE_MO
DE PTP_SOURCE_SWITCH SYN_BAD
LTI SWDL_BD_NOT_MATCH
TN12STG
BD_LEDTEST NO_BD_SOFT SYNC_C_LOS
CLK_NO_TRACE_MO
DE PTP_SOURCE_SWITCH SYN_BAD
LTI SWDL_BD_NOT_MATCH
TN54STG
BD_LEDTEST NO_BD_SOFT SYNC_C_LOS
CLK_NO_TRACE_MO
DE PTP_SOURCE_SWITCH SYN_BAD
LTI SWDL_BD_NOT_MATCH
TN13STG
CLK_NO_TRACE_MO
DE PTP_SOURCE_SWITCH SYN_BAD
LTI SWDL_BD_NOT_MATCH
ETHOAM_RMT_CRIT_FA LAG_VC_PORT_FAIL TD
ULT
ETHOAM_VCG_SELF_LO LPT_ACTIVE TF
OP
DERIVED_PWR_ERRO
R OA_LOW_GAIN SWDL_BD_MATCH_FAIL
MUT_LOS PUM_BCM_ALM
TN97TD20
BD_STATUS OMS_FDI_O OMS_SSF_O
OMS_BDI_P OMS_PMI
OMS_FDI OMS_SSF
PORT_MODULE_OFFLI
BD_LEDTEST MS_SNCP_PS NE
HARD_ERR ODU1_PM_EXC TD
LINK_ERR ODU1_PM_TIM TF
LSR_INVALID OUT_PWR_HIGH
CLIENT_PORT_STA_IN
DI ODU2_TCMn_DEG OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU2_TCMn_EXC OUT_PWR_LOW
LASER_MODULE_MIS
MATCH ODUFLEX_PM_AIS R_LOC
LSR_WILL_DIE ODUFLEX_PM_OCI TD
NULL_SEND ODU_SNCP_STA_INDI TF
RMON_ALM_INBADOCTS
ODU2_PM_BDI OPUFLEX_CSF _OVER
FC_AIS
TN52TDX
ALS_ACTIVE NULL_SEND OTU2_LOM
CLIENT_PORT_STA_IN
DI ODU2_PM_TIM REM_SF
CLIENT_PROT_NOTST
ART ODU2_TCMn_AIS REMOTE_FAULT
J0_MM ODU2_TCMn_SSF TD
LASER_MODULE_MIS
MATCH ODU2_TCMn_TIM TEMP_OVER
LPT_ACTIVE OPU2_PLM TF
NO_BD_SOFT OTU2_DEG
NO_ELABEL OTU2_LOF
TN11TDX
ALS_ACTIVE LSR_COOL_ALM OUT_PWR_LOW
LSR_INVALID PORT_MODULE_OFFLI
B1_EXC NE
HARD_BAD ODU1_PM_LCK TD
J0_MM OPA_FAIL_INDI TF
LPT_ACTIVE OUT_PWR_HIGH
TN12TDX
ALS_ACTIVE LSR_COOL_ALM OUT_PWR_LOW
LSR_INVALID PORT_MODULE_OFFLI
B1_EXC NE
HARD_ERR ODU2_PM_OCI TD
LASER_MODULE_MISMAT ODU_SNCP_STA_INDI TF
CH
LPT_ACTIVE OUT_PWR_HIGH
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LASER_MODULE_MISMA
BEFFEC_EXC TCH OTU2_DEG
CLIENT_PORT_STA_IN
DI LPT_ACTIVE OTU2_SSF
CLIENT_PROT_NOTST
ART LPT_RFI OTU2_TIM
ERPS_IN_PROTECTIO
N LSR_WILL_DIE PORT_MODULE_OFFLINE
ETHOAM_DISCOVER_
FAIL MULTI_RPL_OWNER PRBS_LSS
ETHOAM_RMT_CRIT_
FAULT NO_BD_SOFT REM_SD
ETHOAM_VCG_SELF_
LOOP ODU2_PM_BDI R_LOS
ETH_CFM_MACSTATU
S ODU2_PM_LCK SWDL_BD_NOT_MATCH
ETH_CFM_MISMERGE ODU2_PM_OCI TD
ETH_SERVICE_CONFI
G_FAIL ODU2_TCMn_AIS TEM_LA
EX_ETHOAM_CC_LOS ODU2_TCMn_BDI TF
EX_ETHOAM_MPID_C
NFLCT ODU2_TCMn_DEG VLAN_SNCP_PS
HARD_BAD ODU2_TCMn_OCI
HARD_ERR ODU2_TCMn_SSF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
CLIENT_PORT_STA_IN
DI ODU1_PM_OCI OTU1_LOF
CLIENT_PROT_NOTST
ART ODU1_PM_SSF OTU1_LOM
LASER_MODULE_MIS
MATCH ODU1_TCMn_OCI REM_SF
NO_BD_SOFT ODUFLEX_PM_EXC TD
ODU0_PM_AIS ODUFLEX_PM_TIM TF
RMON_ALM_INBADOCTS
ODU0_PM_LCK OPU0_PLM _OVER
ODU0_PM_OCI OPU1_CSF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
MODULEFILE_UPDAT
E_FAIL NO_BD_SOFT WRG_BD_TYPE
TN15TM20
MODULEFILE_UPDAT
E_FAIL NO_ELABEL WRG_BD_TYPE
MODULE_ADJUST_FA
IL OPA_FAIL_INDI
ODU1_TCM2_SSF ODU2_TCM3_DEG TD
ODU1_TCM3_DEG ODU2_TCM3_SSF TF
ODU1_TCM3_OCI ODU2_TCM4_BDI
TN12TMX
ALS_ACTIVE ODU1_PM_BDI OTU1_AIS
CLIENT_PORT_STA_IN
DI ODU1_TCMn_BDI OTU2_AIS
CLIENT_PROT_NOTST
ART ODU1_TCMn_DEG OTU2_BDI
LASER_MODULE_MIS
MATCH ODU2_PM_BDI OUT_PWR_LOW
OCh_LOS_P ODU2_TCMn_OCI TD
OCh_SSF_P OPU1_PLM TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
CLIENT_PORT_STA_IN
DI ODU1_PM_OCI OTU1_EXC
CLIENT_PROT_NOTST
ART ODU1_PM_SSF OTU1_LOF
LASER_MODULE_MIS
MATCH ODU1_TCMn_OCI REM_SD
NULL_SEND ODUFLEX_PM_LCK TD
ODU0_PM_DEG ODU_SNCP_PS TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
HARD_ERR ODU1_LOFLOM TD
LOOP_ALM ODU1_PM_LCK TF
L_SYNC ODU1_PM_TIM
NO_BD_SOFT OPU0_PLM
ODU0_PM_AIS ODU1_TCM4_OCI TD
ODU0_PM_OCI ODU1_TCM5_BDI TF
ODU1_PM_AIS ODU1_TCM5_LTC
ODU1_PM_BDI ODU1_TCM5_OCI
TN11TOM
ALS_ACTIVE ODU1_PM_SSF ODU1_TCM5_TIM
OCh_SSF_O ODU1_TCM4_TIM TD
ODU1_PM_BDI ODU1_TCM5_EXC TF
ODU1_PM_OCI ODU1_TCM5_SSF
CLIENT_PORT_STA_IN
DI ODU2_PM_SSF PRBS_LSS
CLIENT_PROT_NOTST
ART ODU2_PM_TIM REMOTE_FAULT
LASER_MODULE_MIS
MATCH ODU2_TCMn_SSF SWDL_BD_MATCH_FAIL
LOOP_ALM ODU_SNCP_PS TD
LSR_INVALID OPU2_CSF TF
NO_BD_SOFT OTU2_BDI
TN56TOX
ALS_ACTIVE ODU2_PM_AIS OPUFLEX_PLM
CLIENT_PORT_STA_IN
DI ODU2_TCMn_BDI OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU2_TCMn_DEG OUT_PWR_LOW
RMON_ALM_INBADOCTS
J0_MM ODUFLEX_LOFLOM _OVER
LASER_MODULE_MIS
MATCH ODUFLEX_PM_AIS RS_CROSSTR
L_SYNC ODUFLEX_PM_TIM TD
NO_BD_SOFT ODU_SNCP_STA_INDI TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
PORT_MODULE_OFFLI
ALS_ACTIVE LSR_WILL_DIE NE
HARD_ERR ODU1_PM_EXC TD
LASER_MODULE_MISMAT ODU1_PM_TIM TF
CH
LSR_INVALID OUT_PWR_LOW
TN12TQM
ALS_ACTIVE ODU1_TCM1_LTC ODU1_TCM6_DEG
ODU1_PM_OCI ODU1_TCM5_EXC TD
ODU1_TCM1_BDI ODU1_TCM5_SSF TF
ODU1_PM_TIM ODU1_TCM5_DEG TD
ODU1_TCM1_EXC ODU1_TCM5_OCI TF
ODU1_TCM1_OCI ODU1_TCM6_AIS
ODU1_TCM1_SSF ODU1_TCM6_BDI
CLIENT_PORT_STA_IN
DI ODU2_TCMn_DEG PORT_MODULE_OFFLINE
CLIENT_PROT_NOTST
ART ODU2_TCMn_LCK PRBS_LSS
RMON_ALM_INBADOCTS
IN_PWR_HIGH ODU2_TCMn_TIM _OVER
LASER_MODULE_MIS
MATCH ODUFLEX_PM_BDI R_LOF
LSR_COOL_ALM ODUFLEX_PM_SSF TD
NO_BD_SOFT OPU2_CSF TF
ODU2_PM_AIS OTU2_AIS
TN53TQX
ALS_ACTIVE NULL_SEND OTU2_DEG
CLIENT_PORT_STA_IN
DI ODU2_PM_SSF PORT_MODULE_OFFLINE
CLIENT_PROT_NOTST
ART ODU2_PM_TIM PRBS_LSS
LASER_MODULE_MIS
MATCH ODU2_TCMn_OCI R_LOS
LPT_ACTIVE ODU_SNCP_PS TD
L_SYNC OPUFLEX_CSF TF
TN52TQX
ALS_ACTIVE ODU2_TCM1_OCI ODU2_TCM6_DEG
ODU2_PM_LCK ODU2_TCM5_BDI TD
ODU2_TCM1_AIS ODU2_TCM5_OCI TF
ODU2_TCM1_LCK ODU2_TCM6_AIS
ODU2_TCM1_LTC ODU2_TCM6_BDI
TN11TQX
PORT_MODULE_OFFLI
ALS_ACTIVE LSR_COOL_ALM NE
HARD_BAD ODU2_PM_OCI TD
J0_MM ODU_SNCP_STA_INDI TF
LOOP_ALM OUT_PWR_HIGH
LPT_ACTIVE OUT_PWR_LOW
CLIENT_PORT_STA_IN
DI ODU4_PM_SSF OUT_PWR_LOW
CLIENT_PROT_NOTST
ART ODU4_PM_TIM PORT_MODULE_OFFLINE
LASER_MODULE_MIS
MATCH ODU4_TCMn_TIM SWDL_BD_NOT_MATCH
LOCAL_FAULT ODU_SNCP_PS TD
NO_BD_SOFT OPU4_PLM TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
HARD_ERR ODU2_PM_TIM TD
LOOP_ALM OPU2_MSIM TF
MS_AIS OUT_PWR_LOW
TN53TSXL
ALS_ACTIVE ODU3_TCM2_AIS ODU3_TCM6_DEG
ODU3_TCM1_BDI ODU3_TCM5_LCK TD
ODU3_TCM1_OCI ODU3_TCM5_TIM TF
ODU3_TCM1_TIM ODU3_TCM6_AIS
ODU3_TCM1_EXC ODU3_TCM6_BDI
TN54TSXL
ALS_ACTIVE NULL_SEND OTU3_LOF
RMON_ALM_INBADOCTS
CLIENT_PORT_PS ODU3_PM_TIM _OVER
CLIENT_PORT_STA_IN
DI ODU3_TCMn_AIS RX_POWER_ABNORMAL
CLIENT_PROT_NOTST
ART ODU3_TCMn_BDI R_LOC
LASER_MODULE_MIS
MATCH ODU3_TCMn_SSF TD
LOOP_ALM OPU3_PLM TF
NO_BD_SOFT OTU3_BDI
NO_ELABEL OTU3_DEG
CLIENT_PORT_STA_IN
DI ODU2_PM_BDI R_LOC
CLIENT_PROT_NOTST
ART ODU2_PM_DEG R_LOF
IN_PWR_HIGH ODU2_PM_TIM TD
J0_MM ODU_SNCP_STA_INDI TF
LASER_MODULE_MIS
MATCH OPU2_CSF WRG_BD_TYPE
RMON_ALM_INBADOCTS
LOCAL_FAULT OPU2_PLM _OVER
LOOP_ALM OUT_PWR_HIGH
TN55TTX
ALS_ACTIVE ODU2_PM_AIS OPUFLEX_PLM
CLIENT_PORT_STA_IN
DI ODU2_TCMn_BDI OUT_PWR_HIGH
CLIENT_PROT_NOTST
ART ODU2_TCMn_DEG OUT_PWR_LOW
RMON_ALM_INBADOCTS
J0_MM ODUFLEX_LOFLOM _OVER
LASER_MODULE_MIS
MATCH ODUFLEX_PM_AIS RS_CROSSTR
L_SYNC ODUFLEX_PM_TIM TD
NO_BD_SOFT ODU_SNCP_STA_INDI TF
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
TN16UXCM
SUBRACK_TYPE_MISMA
ARP_SPOOF NEBD_XC_DIF TCH
SWDL_ACTIVATED_TIME
BD_NOT_INSTALLED NESTATE_INSTALL OUT
CFG_DATACHECK_FAI
L OOL SWDL_BD_WEAKMATCH
PASSWORD_NEED_CHAN SWDL_CHGMNG_NOMAT
CFG_DATASAVE_FAIL GE CH
CLK_NO_TRACE_MO
DE POWER_FAIL SWDL_INPROCESS
DBMS_PROTECT_MO
DE S1_SYN_CHANGE SYNC_DISABLE
SERVICE_CAPACITY_EXC
EXT_SYNC_LOS EED_LICENSE SYNC_LOCKOFF
SERVICE_TYPE_EXCEED_
EXT_TIME_LOC LICENSE SYN_BAD
FEATURE_WITHOUT_ SHELF_AREA_POWER_O
LICENSE VER SYSLOG_COMM_FAIL
SYSPARA_CFDB_NOSAM
HARD_BAD SSL_CERT_NOENC E
STORM_CUR_QUENUM_O
K1_K2_M VER TIME_LOS
SHELF_POWER_UNCONFI
K2_M G TIME_NO_TRACE_MODE
LCS_DAYS_OF_GRAC
E PATCH_BD_MATCH_FAIL WRG_BD_TYPE
PATCH_CHGSCC_NOTMA
IGSP_ENTRIES_EXC TCH DCNLINK_OVER
SPAN_LOSS_LOWER_GAI
COMMUN_FAIL OPA_FAIL_INDI N
MODULE_TEMP_OVE
R OTS_BDI_P SUM_INPWR_LOW
OMS_LOSS_ACCUM_A
BN OTS_TIM WAVEDATA_MIS
OMS_LOSS_MON_FAI SPAN_LOSS_EXCEED_EO
L L WRG_BD_TYPE
TN12VA1
SPAN_LOSS_LOWER_GAI
COMMUN_FAIL OTS_BDI_O N
OMS_LOSS_ACCUM_A
BN OTS_LOS_P WAVEDATA_MIS
OMS_LOSS_MON_FAI
L OTS_PMI WRG_BD_TYPE
OMS_PWR_ADJ_FAIL OTS_TIM
SPAN_LOSS_EXCEED_EO
OOS_LOST L
TN13VA1
SPAN_LOSS_LOWER_GAI
COMMUN_FAIL OTS_BDI N
OMS_LOSS_ACCUM_A
BN OTS_PMI WAVEDATA_MIS
OMS_LOSS_MON_FAI
L OTS_TIM WRG_BD_TYPE
SPAN_LOSS_EXCEED_EO
OMS_PWR_ADJ_FAIL L
SPAN_LOSS_LOWER_GAI
COMMUN_FAIL OPA_FAIL_INDI N
MODULE_TEMP_OVE
R OTS_BDI_P SWDL_BD_NOT_MATCH
OMS_LOSS_ACCUM_A
BN OTS_TIM
OMS_LOSS_MON_FAI SPAN_LOSS_EXCEED_EO
L L
TN12VA4
BD_LEDTEST OPA_FAIL_INDI SPAN_LOSS_HIGH
SPAN_LOSS_LOWER_GAI
COMMUN_FAIL OTS_BDI_O N
OMS_LOSS_ACCUM_A
BN OTS_LOS_P WAVEDATA_MIS
OMS_LOSS_MON_FAI
L OTS_PMI WRG_BD_TYPE
OMS_PWR_ADJ_FAIL OTS_TIM
SPAN_LOSS_EXCEED_EO
OOS_LOST L
TN13VA4
BD_LEDTEST OOS_LOST SPAN_LOSS_HIGH
SPAN_LOSS_LOWER_GAI
COMMUN_FAIL OTS_BDI N
OMS_LOSS_ACCUM_A
BN OTS_PMI WAVEDATA_MIS
OMS_LOSS_MON_FAI
L OTS_TIM WRG_BD_TYPE
SPAN_LOSS_EXCEED_EO
OMS_PWR_ADJ_FAIL L
TN12WSD9/TN13WSD9
BD_LEDTEST OMS_BDI OMS_PMI
MOD_COM_FAIL OMS_SSF_O
MUT_LOS OMS_SSF_P
TN16WSD9
MODULEFILE_UPDAT
E_FAIL OMS_FDI SWDL_BD_MATCH_FAIL
MODULE_ADJUST_FA
IL OMS_FDI_O SWDL_BD_NOT_MATCH
MODULE_TEMP_OVE
R OMS_FDI_P TEMP_OVER
TN17WSD9
MODULEFILE_UPDATE_FA SWDL_BD_MATCH_FAI
IL OMS_FDI L
SWDL_BD_NOT_MATC
MODULE_ADJUST_FAIL OMS_FDI_O H
TN96WSD9
MODULEFILE_UPDAT
E_FAIL OMS_FDI SWDL_BD_MATCH_FAIL
MODULE_ADJUST_FA
IL OMS_FDI_O SWDL_BD_NOT_MATCH
MODULE_TEMP_OVE
R OMS_FDI_P TEMP_OVER
MODULE_ADJUST_FAI SWDL_BD_MATCH_FAIL
L
TN12WSM9/TN13WSM9
MODULEFILE_UPDATE_FAI OPA_FAIL_INDI
BD_LEDTEST L
TN17WSM9
SWDL_BD_MATCH_FAI
BD_LEDTEST MODULE_TEMP_OVER L
SWDL_BD_NOT_MATC
BD_STATUS MOD_COM_FAIL H
MODULEFILE_UPDATE_FA
IL NO_ELABEL WRG_BD_TYPE
MODULE_ADJUST_FAIL OPA_FAIL_INDI
TN16WSM9
MODULEFILE_UPDAT
E_FAIL NO_ELABEL WRG_BD_TYPE
MODULE_ADJUST_FA
IL OPA_FAIL_INDI
TN96WSM9
BD_LEDTEST MODULE_TEMP_OVER SWDL_BD_MATCH_FAIL
MODULEFILE_UPDAT
E_FAIL NO_ELABEL WRG_BD_TYPE
MODULE_ADJUST_FA
IL OPA_FAIL_INDI
MUT_LOS OMS_SSF_O
MUT_LOS OMS_SSF_O
TN12WSMD4
BD_LEDTEST MUT_TLOS OMS_SSF_P
MOD_COM_FAIL OMS_SSF
MUT_LOS OMS_SSF_O
TN13WSMD4
BD_LEDTEST NO_BD_PARA OMS_SSF_O
MODULEFILE_UPDAT
E_FAIL OMS_BDI_P SUM_INPWR_LOW
MODULE_ADJUST_FA
IL OMS_FDI SWDL_BD_MATCH_FAIL
MODULE_TEMP_OVE
R OMS_FDI_O SWDL_BD_NOT_MATCH
TN17WSMD4
SWDL_BD_MATCH_FAI
HARD_ERR OMS_BDI_P L
MODULEFILE_UPDATE_FA SWDL_BD_NOT_MATC
IL OMS_FDI H
MUT_TLOS OMS_SSF
NO_BD_PARA OMS_SSF_O
MUT_TLOS OMS_SSF_O
NO_BD_SOFT OMS_SSF_P
TN12WSMD9/TN15WSMD9
MODULEFILE_UPDAT
E_FAIL OMS_FDI SWDL_BD_NOT_MATCH
MODULE_ADJUST_FA
IL OMS_FDI_O TEMP_OVER
MODULE_TEMP_OVE
R OMS_FDI_P VOADATA_MIS
MUT_TLOS OMS_SSF_O
NO_BD_PARA OMS_SSF_P
TN16XCH
ALC_ADJUST_FAIL LTI SUBRACK_COMM_PS
ALC_WAIT_ADJUS SUBRACK_ID_CONFLI
T MS_APS_INDI_EX CT
APS_FAIL SUBRACK_ID_MISMAT
NEBD_XC_DIF CH
LCS_FILE_NOT_EX SCC_CHANGE
IST
LCS_SHORTAGE_S SSL_CERT_TO_EXPIRE
HELF
HARD_BAD SWDL_BD_MATCH_FAIL
TN12XCS
BD_LEDTEST HARD_ERR SWDL_BD_NOT_MATCH
HARD_BAD SWDL_BD_MATCH_FAIL
This topic describes common information relevant to alarm handling, including alarm
descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm
handling procedures.
NOTE
By default, optical-layer alarms (OTS, OMS, and OCH alarms) are not reported. You can enable optical-
layer alarm reporting as required using the NMS. For details, see "Enabling/Disabling Supervision on
the Optical Layer" in the Supporting Tasks.
NOTE
In the case of an alarm, see its handling procedure to clear it; if the alarm persists, contact Huawei
engineers for troubleshooting.
The alarm handling involves board reset, either cold or warm. Cold reset and warm reset have
different impacts on services.
l Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software,
neither the FPGA file nor hardware data is updated and so a warm reset does not
interrupt services. A cold reset of the SCC might result in re-setting of the key hardware,
such as FPGA reloading; the upper-layer software need be restarted.
l Reset of other boards: A warm reset on other boards does not affect running services
while a cold reset on other boards does. If such a board is reset incorrectly, the
communication between the board and the SCC is affected and even the services are
interrupted.
Certain alarms listed in this topic are handled in different ways, because the board types are
different. This topic describes how to handle alarms in the OCS and OTN systems separately
according to the system where the board is located.
3.1 B1_EXC
Refer to the alarm page according to the type of the board that reports the alarm.
3.2 BEFFEC_EXC
3.3 BOOTROM_BAD
See the alarm page according to the type of the board that reports the alarm.
3.4 BUS_ERR
See the alarm page according to the type of the board that reports the alarm.
3.5 CHAN_LOS
3.6 CLIENT_PORT_PS
3.7 COMMUN_FAIL
Refer to the alarm page according to the type of the board that reports the alarm.
3.8 ETH_8B10B_ERR
3.9 EX_ETHOAM_CC_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
3.10 FC_LINK_ERR
3.11 FC_SYNC_LOS
3.12 IN_PWR_HIGH
Refer to the alarm page according to the type of the board that reports the alarm.
3.13 IN_PWR_LOW
Refer to the alarm page according to the type of the board that reports the alarm.
3.14 INTRA_OTU_PS
3.15 LASER_MODULE_MISMATCH
3.16 LINK_ERR
Refer to the alarm page according to the type of the board that reports the alarm.
3.17 LOOP_ALM
Refer to the alarm page according to the type of the board that reports the alarm.
3.18 LPT_ACTIVE
3.19 LSR_WILL_DIE
3.20 MS_AIS
Refer to the alarm page according to the type of the board that reports the alarm.
3.21 MS_RDI
Refer to the alarm page according to the type of the board that reports the alarm.
3.22 MUT_LOS
3.23 OA_LOW_GAIN
3.24 ODU_SNCP_PS
3.25 ODUk_PM_AIS
3.26 ODUk_PM_BDI
3.27 ODUk_PM_DEG
3.28 ODUk_PM_EXC
3.29 ODUk_PM_SSF
3.30 OMS_FDI
3.31 OSC_LOS
3.32 OTS_LOS
3.33 OTUk_LOF
3.34 OTUk_SSF
3.35 OUT_PWR_HIGH
3.36 PORT_MODULE_OFFLINE
3.37 POWER_FAIL
3.38 PUMP_COOL_EXC
3.39 R_LOF
Refer to the alarm page according to the type of the board that reports the alarm.
3.40 R_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
3.41 R_OOF
3.42 R_SLIP
3.43 REM_SF
3.44 REMOTE_FAULT
3.45 SECU_ALM
3.46 SUBRACK_ID_CONFLICT
3.47 SUM_INPWR_LOW
3.48 SWDL_NEPKGCHECK
3.49 TD
3.50 TEMP_OVER
3.51 TF
3.52 TS_CFG_MISMATCH
3.53 WRG_BD_TYPE
3.1 B1_EXC
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.1.2 B1_EXC (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The B1_EXC is an alarm indicating that the number of B1 bit errors exceeds the specified
threshold. This alarm is reported when the line board detects that the number of regenerator
section bit errors exceeds the specified threshold (default threshold: 10-3) by monitoring the
B1 byte.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The bit error threshold is not proper.
l Cause 2: The ambient environment is abnormal.
l Cause 3: Line performance deteriorates.
l Cause 4: The equipment is not grounded properly
l Cause 5: The local receive board is faulty.
l Cause 6: The peer transmit board is faulty.
l Cause 7: The clock configuration is incorrect, or the clock unit performance deteriorates
Procedure
Step 1 Cause 1: The bit error threshold is not proper.
1. Check the bit error threshold. If it is low, raise the threshold as required.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, go to Step 2.
If... Then...
The transmit optical power of the peer board is out of range Go to Step 6.
The transmit optical power of the peer NE is within the Go to the next step.
specified range
2. On the NMS, check whether the transmit optical power of the local board is within the
specified range.
If... Then...
The transmit optical power of the local board is out of range Go to Step 5.
The transmit optical power of the local board is within the Go to the next step.
specified range
3. On the NMS, check whether the receive optical power of the local board is within the
specified range.
If... Then...
The receive optical power of the local board is Check the fiber ends, fiber
out of range connector, and optical cable in turn.
If... Then...
The fiber connector is loose Properly connect the fiber connector. Check whether
the B1_EXC alarm is cleared. If the alarm persists,
go to the next step.
If... Then...
6. Check whether the radius of the roll into which the pigtail is coiled is less than 6 cm, and
check the optical cable for damage, sheath stripping, aging, fusion, and cut. If the radius
is less than 6 cm, re-roll the pigtail. If any damage, sheath stripping, aging, fusion, or cut
is found on the optical cable, replace it and check whether the B1_EXC alarm is cleared.
7. If the alarm persists, check whether the optical cable matches the optical interface board
in model type. Mismatch in model type may result in low fiber sensitivity, large
dispersion, and signal distortion, which will cause bit errors.
If... Then...
The optical cable does not match the Replace the fiber or line board as
optical interface board in model type required and check whether the
B1_EXC alarm is cleared.
1. Ensure that the equipment is properly grounded. For example, ensure that the PGND
cable is properly connected and the cabinet and ground bar are properly connected.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, go to Step 5.
Step 7 Cause 7: The clock configuration is incorrect, or the clock unit performance deteriorates
1. Check the local and peer clock sources for timing loop or asynchronization. If pointer
adjustment events or alarms, such as the AUPJCHIGH event or the SYN_BAD alarm,
are reported along with the B1_EXC alarm, clear the pointer adjustment events or alarms
first.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
Description
Excessive errors on the regenerator section (B1). This alarm is generated when the received
SDH signals degrade and the B1 bit errors on the regenerator section exceed the threshold.
Attribute
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 (reported from the client side): The input signals on the client side contain B1
bit errors.
l Cause 2 (reported from the client side): The board that reports this alarm is faulty.
l Cause 1 (reported from the WDM side): The receive side of the local station (Station B)
is faulty.
l Cause 2 (reported from the WDM side): The attenuation of the received signals is
excessively high; the fiber or connector is not clean.
l Cause 3 (reported from the WDM side): The transmit side of the opposite station (Station
A) is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
Detects and reports Detects and reports
the B1_EXC alarm the B1_EXC alarm
O O
A F F A
OTU(A) I OTU(B)
D I D
Out-loop M U U M Out-loop
Station A Station B
l Cause 1 (reported from the client side): The input signals on the client side contain B1
bit errors.
a. If this alarm is reported from the client side of the board, apply a hardware
loopback between the transmit and receive optical ports on the client side of
OTU(A). If the alarm on OTU(A) persists, the OTU(A) hardware is faulty. See the
alarm handling procedure for cause 2 (reported from the client side).
NOTICE
Configuring a loopback on the board interrupts the services on the board.
b. If the alarm is cleared, the input signals on the client side of the board contain B1
bit errors. Rectify the fault on the client equipment.
l Cause 2 (reported from the client side): The board that reports the alarm is faulty.
a. Check whether the board that reports this alarm supports pluggable optical modules.
l Cause 1 (reported from the WDM side): The receive side of the local station (Station B)
is faulty.
a. Configure an outloop at the transmit and receive optical ports on the WDM side of
OTU(B). If there is no bit error alarm on the OTU(A), the board at the local station
(Station B) is faulty. Replace the faulty board.
NOTICE
Configuring a loopback on the board interrupts the services on the board.
b. If OTU(A) has bit error alarms, see the alarm handling procedure for cause 2
(reported from the WDM side).
l Cause 2 (reported from the WDM side): The attenuation of the received signals is
excessively high; the fiber or connector is not clean.
a. If there are bit errors, check the transmit optical power at the corresponding optical
ports on the opposite OTU(A) on the U2000. For the optical power specifications of
the specific board, see "Technical Specifications" in the Product Description. For
details, see "Querying Optical Power on the U2000" in the Supporting Tasks.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturing information of the optical
module on the board.
b. If the transmit optical power of the corresponding optical port on OTU(A) is within
the permitted range, check the attenuation of the transmission link between the
transmitting module of OTU(A) at the opposite station and the receiving module of
OTU(B) at the local station. If the preset attenuation values are excessively large,
correct them so that they are within the permitted range.
c. If the alarm persists, check the fiber connectors at stations A and B separately. If the
fiber connectors are dirty, clean or replace them. For details, see "Inspecting and
Cleaning the Fiber-Optic Connectors" in the Supporting Tasks.
d. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large
bending radius or it is damaged or aging, adjust or replace the fiber jumper. For
details, see "Replace the Fiber Jumper" in the Parts Replacement. If the fibers
inside a station are normal, check the optical cables between stations to rectify the
fault.
e. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 (reported from the WDM side).
l Cause 3 (reported from the WDM side): The transmit side of the opposite station (Station
A) is faulty.
a. Add a pigtail to connect a 5 dB fixed attenuator and the OTU(A) board on the
opposite station and perform a WDM-side hardware loopback. If the alarm on the
OTU(A) board persists, the OTU(A) board is faulty. In this case, replace the board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A88 The OTU Board Reports the B1_EXC Alarm, And There Are the Difference in
BER Reported by the OTU Board and Test Instrument
l MC-A105 Line Reflection Leads to Inaccurate BER Detection of the SSC6LWX Board,
the Board Reports the B1_EXC Alarm
3.2 BEFFEC_EXC
Description
Signal degraded before FEC. Signals sent from the WDM side of the opposite-end OTU have
the FEC function. As a result, before performing signal FEC in the receive direction on the
WDM side of the local-end OTU, the local-end OTU counts the bit error rate. This alarm is
generated when the counted bit error rate crosses the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-2 lists the fault symptom of the BEFFEC_EXC alarm.
The NE that reports this alarm reports a Cause 3 of this alarm in the case of multiple
temperature alarm or fan fault alarm, such wavelengths: The external environment is
as TEMP_OVER or FAN_FAIL, within a improper.
certain time.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Procedure" provided in this topic.
Possible Causes
The possible causes of this alarm in the case of a single wavelength are as follows:
l Cause 1: The input optical power of the OTU board is excessively high or low.
l Cause 2: The settings of the FEC mode of the interconnected OTU boards are different.
l Cause 3: The fiber between the OTU board and the multiplexer/demultiplexer board is
faulty.
l Cause 4: An inappropriate DCM is installed.
l Cause 5: The board that reports this alarm or the board at the opposite station is faulty.
The possible causes of this alarm in the case of multiple wavelengths are as follows:
l Cause 1: Fibers in the optical cables between stations or the multiplexing portions inside
a station are faulty.
l Cause 2: The attenuation of the signals during line transmission is excessively high.
l Cause 3: The external environment is improper.
Procedure
Step 1 On the U2000, check the alarm information and record the IDs of the port and channel where
the alarm is generated.
Step 2 Cause 1 of this alarm in the case of a single wavelength: The input optical power of the OTU
board is excessively high or low.
1. Check whether the receive optical power on the U2000 is within the permitted range. For
the optical power specifications of the specific board, see "Technical Specifications" in
the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for Boards" in
the Hardware Description to obtain the manufacturer information of the optical module on the
board.
2. If the input optical power is abnormal, see the methods for handling the IN_PWR_HIGH
and IN_PWR_LOW alarms.
3. If the input optical power is normal but the alarm persists, see the alarm handling
procedure for cause 2 of this alarm in the case of a single wavelength.
Step 3 Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of the
interconnected OTU boards are different.
1. On the U2000, check the settings of FEC mode of the two interconnected OTU boards. If
the settings are different, change the settings to FEC or AFEC to ensure consistency. For
details, see "Setting the FEC Mode" in the Supporting Tasks.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm in the case of a single wavelength.
Step 4 Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board
and the multiplexer/demultiplexer board is faulty.
1. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace
them. For details, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the
Supporting Tasks.
2. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Parts Replacement.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4 of this alarm in the case of a single wavelength.
Step 5 Cause 4 of this alarm in the case of a single wavelength: An inappropriate DCM is installed.
1. Check whether the DCM used on the existing network is appropriate. If not, replace the
DCM.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5 of this alarm in the case of a single wavelength.
Step 6 Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm or
the board at the opposite station is faulty.
1. If the alarm is reported simultaneously on the IN port of both the OTU(A) and OTU(B)
boards, as shown in the following figure, add a pigtail to connect a 5 dB fixed attenuator
and the OTU(B) board and perform a WDM-side loopback. If the alarm persists, the
OTU(B) board is faulty. If the alarm is cleared, the OTU(B) board is normal but the
OTU(A) board may be faulty.
OUT IN
OTU OTU
2 1
(A) (B)
IN OUT
Station A Station B
2. Release the loopback on the OTU(B) board. Add a pigtail to connect a 5 dB fixed
attenuator and the OTU(A) board on the opposite station and perform a WDM-side
hardware loopback. If the alarm on the OTU(A) board persists, the OTU(A) board is
faulty.
3. Replace the faulty board. Check whether the alarm is cleared.
The board does not support pluggable optical Replace the board.
modules,
Step 7 Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables between
stations or the multiplexing portions inside a station are faulty.
1. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace
them. For details, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the
Supporting Tasks.
2. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Parts Replacement. If the fibers inside a station are
normal, check the optical cables between stations to rectify the fault.
3. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm in the case of multiple wavelengths.
Step 8 Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals
during line transmission is excessively high.
1. Check the attenuation of the multiplexing portions inside a station and the line
attenuation between stations section by section. If the preset attenuation values are
excessively large, correct them so that they are within the permitted range.
2. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm in the case of multiple wavelengths.
Step 9 Cause 3 of this alarm in the case of multiple wavelengths: The external environment is
improper.
1. Check the ambient temperature inside the telecommunications room, the cleanliness of
the air filter, and the heat dissipation conditions of each fan. For details, see the
procedure for handling the TEMP_OVER alarm.
2. Check whether the alarm is cleared. If the alarm persists, check whether external
electromagnetic interference exists. For example, whether there is external electronic
equipment, whether the power supply is unstable, and whether the lightning
----End
Related Information
Related Cases:
l MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets
Close to the Threshold
l MC-A55 Improper DCM Distribution Causes Abnormal Service and Bit Error Alarm
BEFFEC_EXC Is Detected on the Newly-added LWFS Board
l MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board
l MC-A237 Dispersion Topology Affects System Performance
l MC-A238 High PMD Affects 40G Services
l MC-A239 Inappropriate Line Optical Power Adjustment Causes Deteriorated 40G
Performance
3.3 BOOTROM_BAD
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.3.2 BOOTROM_BAD (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l The extended BIOS software is damaged.
l The basic BIOS software is damaged.
l The board is faulty.
Procedure
Step 1 On the NMS, view the BOOTROM_BAD alarm and determine the type of the damaged BIOS
software based on alarm parameters.
If... Then...
The extended BIOS software is Reload the extended BIOS software and check
damaged whether the BOOTROM_BAD alarm is cleared.
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.
Description
BOOTROM data check failed. This alarm is generated when the basic or extended BIOS
software of the board is damaged.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 BIOS type. For example, 0x01 indicates the basic BIOS software,
and 0x02 indicates the extended BIOS software.
Fault Symptom
None
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The basic BIOS software of the system control board is damaged.
l Cause 2: The extended BIOS software of the system control board is damaged.
l Cause 3: The system control board is faulty.
Procedure
l Determine upon the alarm parameter (0x01 indicates the basic BIOS while 0x02 the
extended BIOS) whether the basic or extended BIOS software of the system control
board is damaged.
l Cause 1: The basic BIOS software of the system control board is damaged.
a. Replace the faulty system control board. For details, see "Replacing the SCC
Board" in the Parts Replacement.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l Cause 2: The extended BIOS software of the system control board is damaged.
a. Reload the extended BIOS of the system control board.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
NOTE
The BIOS detection interval is 24 hours. Therefore, the BOOTROM_BAD alarm is
displayed 24 hours later if the alarm is not cleared after you reload the extended BIOS.
l Cause 3: The system control board is faulty.
a. Replace the faulty system control board. For details, see "Replacing the SCC
Board" in the Parts Replacement.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None
3.4 BUS_ERR
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.4.2 BUS_ERR (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
the active cross-connect board has the HARD_BAD alarm, services are switched from
the active board to the standby board.
Possible Causes
l Cause 1: The service board does not match the cross-connect board in software version.
l Cause 2: The service board is faulty.
l Cause 3: The cross-connect board is faulty.
l Cause 4: The backplane bus from the service board to the cross-connect board is faulty.
Procedure
Step 1 Cause 1: The service board does not match the cross-connect board in software version.
1. Check whether the service board matches the cross-connect board in software version.
For details, see the software version mapping table in the Supporting Tasks.
If... Then...
Both boards do not match in Upgrade either board to the version matching that of
software version the other board.
Check whether the BUS_ERR alarm is cleared. If the
alarm persists, go to Step 2.
You can initially warm reset the service board. If the BUS_ERR alarm persists after the warm
reset, cold reset the board.
3. If the alarm persists, replace the service board. For details, see Parts Replacement. Then,
check whether the BUS_ERR alarm is cleared.
NOTICE
Cold reset or replace the board only when the services traverse the board are protected.
Otherwise, cold resetting or replacing the board may interrupt services.
NOTE
You can initially warm reset the cross-connect board. If the BUS_ERR alarm persists after the
warm reset, cold reset the board.
2. If the alarm persists, replace the alarm-reporting cross-connect board. For details, see the
Parts Replacement. Then, check whether the BUS_ERR alarm is cleared.
NOTICE
Replace the cross-connect board only when at least one standby cross-connect board is
working properly. Otherwise, replacing the board may interrupt services.
3. If the alarm persists, follow the preceding operations and reset or replace the other cross-
connect board that has not reported this alarm. Then, check whether the BUS_ERR
alarm is cleared.
4. If the alarm persists, go to Step 4.
Step 4 Cause 4: The backplane bus from the service board to the cross-connect board is faulty.
1. Contact Huawei technical support engineers to check whether the backplane has bent
pins. Replace the backplane if it is damaged.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
Parameter Description
Parameter 1 Indicates the bus type if the cross-connect board reports the alarm.
l 0x00 indicates higher order buses.
l 0x01 to 0x05 indicate lower order buses.
If a service board report the alarm, there is no parameter 1.
Parameters 2 Indicate the logical number of a bus if a cross-connect board reports the
and 3 alarm.
If a service board reports the alarm,
l For OptiX OSN 6800, the parameters indicate the number of the faulty
bus.
l For OptiX OSN 8800, the parameters indicate the slot ID of the
working/protection cross-connect board. When parameter 3 is 0x09, the
parameters indicate that the services on the cross-connect board in slot
9 are abnormal. 0x0a indicates that the services on the cross-connect
board in slot 10 are abnormal.
Parameter 4 Indicates the service board slot ID corresponding to the backplane bus if
the cross-connect board reports the alarm.
Fault Symptom
None
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The OTU broad, tributary or line board is not properly inserted or is faulty.
l Cause 2: The cross-connect board is not properly inserted or is faulty.
l Cause 3: When ASON services are configured, the type of services that are actually
received does not match the service type configured on the board.
l Cause 4: The pins are faulty or the bus is faulty on the backplane.
l Cause 5: When the OTN boards support 100G services or the universal line boards
support packet data services, the cross-connect boards (including physical and logical)
must be configured for high-capacity boards. If all logic cross-connect boards are
configured for high-capacity board in the subrack, while the physical cross-connect
board use the ordinary board, this alarm will be reported.
Procedure
l Cause 1: The OTU board, tributary or line board is not properly inserted or is faulty.
a. Remove and re-insert the board where the alarm is generated.
b. Along the signal flow, remove and re-insert the OTU board, tributary or line board
where the cross-connect service traverses.
c. Check whether the alarm is cleared. If the alarm persists, replace the board.
l Cause 2: The cross-connect board is not properly inserted or is faulty.
a. Remove and re-insert the cross-connect board.
b. Check whether the alarm is cleared. If the alarm persists, replace the cross-connect
board.
l Cause 3: When ASON services are configured, the type of services that are actually
received does not match the service type configured on the board.
a. Check whether the board that reports this alarm supports pluggable optical modules.
If... Then...
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The pins are faulty or the bus is faulty on the backplane.
a. On the U2000, perform a cold reset on the faulty board.
b. If the alarm persists, replace the backplane of the subrack. For the detailed
operations, contact Huawei for assistance.
l Cause 5: When the OTN boards support 100G services or the universal line boards
support packet data services, the cross-connect boards (including physical and logical)
must be configured for high-capacity boards. If all logic cross-connect boards are
configured for high-capacity board in the subrack, while the physical cross-connect
board use the ordinary board, this alarm will be reported.
a. Replace the physical cross-connect board to high-capacity cross-connect board in
the subrack.
----End
Related Information
Related Cases:
l MC-A144 The TDX Board Reports the BUS_ERR Alarm When Cross-Connections Are
Configured on the Board Because the Service Type of the Board Is Not Set
l MC-A161 The NS2 and TDG Boards Report the BUS_ERR Alarms at the Same Time
After ODUk SNCP Protection Is Configured Because The SCC Board Is Faulty
l MC-A209 Many Boards at A Site Report the BUS_ERR Alarms
l MC-A246 The TN52TQX Board in a Subrack Using the TN1K1AFB Backplane Reports
the BUS_ERR Alarm
3.5 CHAN_LOS
Description
Single-wavelength signal loss or performance (the center wavelength, power, or OSNR)
degrade alarm. The alarm is generated when the multi-channel spectrum analyzer (MCA)
board detects that the original wavelength is lost or the optical spectrum performance degrade
amount exceeds the threshold after it scans the optical spectrum.
Attribute
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The wavelength that needs to be monitored is not received or the shift of the
monitored wavelength exceeds 0.15 nm. For example, in the following figure, λ1 needs
to be monitored as configured, but actually λ1 is not received. The possible cause is that
the fiber on the WDM side of the OTU1 is not connected.
MCA
?1 M M ?1
OTU1 U OA OA U OTU3
X/ F F X/
?2 D I I D ?2
M U U M
OTU2 OTU4
U OA OA U
X X
Client WDM Client
WDM side
side side side
Station A Station B
l Cause 2: The laser on the board at the opposite station is turned off. For example, the
laser on OTU1 in the preceding figure is turned off.
l Cause 3: The optical power difference between the monitored wavelengths is excessively
large. For example, the optical power difference between λ1 and λ2 is excessively large.
l Cause 4: The attenuation of the multiplexer or OA board interconnected with the MCA is
excessively high.
l Cause 5: The OTU board located before the MCA is faulty. For example, OTU1 in the
preceding figure is faulty.
l Cause 6: The MCA that reports the alarm is faulty.
Procedure
l On the U2000, check the alarm information and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The wavelength that needs to be monitored is not received or the shift of the
monitored wavelength exceeds 0.15 nm.
a. Check whether the wavelength where the alarm is generated is required in the actual
network. If not, modify the wavelength monitoring configuration of the MCA so
that the monitoring of the wavelength is disabled.
b. If the wavelength needs to be received in the actual network, check the fiber
connection at the upstream stations along the signal flow so that the fiber
connection is established properly.
c. Check the historical and current performance statistics of the MCA board. Verify
that the shift of the monitored wavelength is within 0.15 nm. If the wavelength shift
exceeds the threshold, optimize the performance of related OTU boards or replace
them.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The laser on the board at the opposite station is turned off.
a. Check whether the laser on the OTU that transmits the wavelength is turned off. If
the laser is turned off, turn on the laser.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The optical power difference between the monitored wavelengths is excessively
large.
a. Query whether the APE function is configured. If it is, enable the APE function to
re-adjust the optical power of each wavelength. For detailed operations, see
"Automatic Power Equilibrium (APE)" in the Feature Description.
b. If the APE function is not configured for the system, manually enable the
adjustment of a single wavelength and adjust the optical power of the wavelengths
with excessively large difference, ensuring that the optical power is flat.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The attenuation of the multiplexer or OA board interconnected with the MCA is
excessively high.
a. Query the output optical power of the upstream OTU board connected to the
multiplexer board. Check whether the output optical power of the upstream OTU
board is within the permitted range. For the optical power specifications of the
specific board, see "Technical Specifications" in the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the board.
b. Use an optical meter to query the input optical power of the optical port that reports
the alarm, and calculate the output optical power of the upstream multiplexer or OA
board to determine whether the output optical power is within the permitted range.
For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the optical power is extremely low or
there is no light, check the attenuation that is set for the input optical power on the
multiplexer or OA board. If the attenuation is very high, decrease the attenuation for
the multiplexer or OA board.
NOTE
Output optical power of the multiplexer or OA board (dBm) = Input optical power at the IN
port on the MCA (dBm) - 10lg("MON"/"OUT") (dBm). "MON"/"OUT" represents the split
ratio of the MON port on the multiplexer or OA board. For details, see "MON Port Optical
Split Ratio" in the Hardware Description.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: The OTU in the upstream direction of the MCA is faulty.
a. Replace the OTU that transmits the wavelength to the MCA.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 6.
l Cause 6: The MCA that reports the alarm is faulty.
a. Use an optical spectrum analyzer to analyze the optical spectrum data of the
corresponding optical port on the MCA. If the data is normal, perform a cold reset
on the MCA.
b. If the alarm persists, replace the MCA that reports the alarm. Replace the board.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.6 CLIENT_PORT_PS
Description
Client-side 1+1 protection switching. This alarm is generated when a client 1+1 protection
group undergoes protection switching and the active channel is switched from the working
channel to the protection channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-5 lists the fault symptoms for the CLIENT_PORT_PS alarm.
Protection switching is performed, and the Cause 2: The services on the working
board on the working channel reports channel of the client 1+1 protection group
alarms that can trigger protection switching. are faulty. The active channel automatically
switches to the working channel and the
alarm is reported.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching. Such a command makes the active channel of a client 1+1 protection
group switch from the working channel to the protection channel, triggering the
CLIENT_PORT_PS alarm.
l Cause 2: The services on the working channel of a client 1+1 protection group are faulty
and the active channel automatically switches to the working channel, triggering the
CLIENT_PORT_PS alarm.
Procedure
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching.
a. On the U2000, query the switching status of the protection group. If the switching
state is forced switching or manual switching, check whether the external switching
operation is necessary.
b. If the external switching operation is necessary, ignore the alarm.
c. If the external switching operation is unnecessary, deliver an external command to
switch the active channel to the working channel, clearing the alarm.
l Cause 2: The services of the working channel of the client 1+1 protection group are
faulty. The active channel automatically switches to the working channel and the alarm is
reported.
a. Query whether the related boards for configuring the protection group have alarms
related to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_TIM, REM_SF,
ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC or REM_SD.
If they do, handle the alarms by referring to the alarm handling procedure.
b. If the alarm persists, check whether the attribute of the protection group is
Revertive. If yes, after WTR Time the current channel automatically switches to
the working channel and the alarm clears. If the attribute is Non-Revertive, set it to
Revertive, and after WTR Time the alarm clears.
c. Check whether the alarm clears. If the alarm persists, contact Huawei for assistance.
----End
Related Information
For details, see "Client 1+1 Protection" in the Feature Description.
3.7 COMMUN_FAIL
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.7.2 COMMUN_FAIL (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The COMMUN_FAIL is an alarm indicating that inter-board communication is interrupted.
This alarm is reported when the communication is interrupted between the SCC board and a
non-SCC board.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the path in which the alarm is generated.
l 0x00 0x01: path 1 of the RS485
l 0x00 0x02: path 2 of the RS485
l 0x00 0x03: inter-board Ethernet communication
l 0x00 0x04: inter-subrack Ethernet emergency path
Possible Causes
A single board may report the COMMUN_FAIL alarm due to the following causes:
Multiple boards may report the COMMUN_FAIL alarm due to the following causes:
Procedure
Step 1 Cause 1: The service board is being reset.
1. View the service board indicator to determine whether the board is being reset. For
details, see the Hardware Description. Alternatively, query historical resets of the board.
For details, see the Supporting Tasks.
If... Then...
The board is being reset Wait until the reset is complete (about 5 minutes) and
check whether the COMMUN_FAIL alarm is cleared.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the optical port number and the value is fixed at 0x01.
Parameters 2 Indicates the ID of the channel where the alarm is generated. For example,
and 3 l 0x00 0x01 indicates RS485 path 1.
l 0x00 0x02 indicates RS485 path 2.
l 0x00 0x03 indicates inter-board communication.
l 0x00 0x04 indicates the Ethernet emergency channel between
subracks.
l 0x00 0x05 indicates the SPI communication failure between the system
control board and AUX board.
l 0x00 0x06 indicates RS485 path 3.
l 0x00 0x07 indicates RS485 path 4.
l 0x00 0x08 indicates RS485 path 5.
l 0x00 0x09 indicates RS485 path 6.
l 0x00 0x0a indicates RS485 path 7.
l 0x00 0x0b indicates RS485 path 8.
Fault Symptom
Table 3-7 lists the fault symptom for the COMMUN_FAIL alarm.
A single board l The board also reports Cause 1 (reported on a single board):
reports the the BD_STATUS The board is in the cold reset or warm
COMMUN_FAIL alarm (only when the reset state.
alarm. board is in the cold
The alarm reset state).
parameter is 0x01 l The PROG indicator
0x00 0x03. on the board blinks
first at the frequency
of 300 ms on and 300
ms off (green) and
then at the frequency
of 100 ms on and 100
ms off (green).
The system control The network cables for Cause 2 (reported on a single board):
board of a slave cascading subracks are The network cables for cascading
subrack reports the self-made network cables subracks do not meet the requirements.
COMMUN_FAIL rather than standard
alarm. straight-through cables
The alarm with all eight cores being
parameter is 0x01 used.
0x00 0x04.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the COMMUN_FAIL alarm reported on a single board are as follows:
l Cause 1 (reported on a single board): The board is in the cold reset or warm reset state.
l Cause 2 (reported on a single board): The network cables for cascading subracks do not
meet the requirements.
l Cause 3 (reported on a single board): The board is faulty.
The possible causes of the COMMUN_FAIL alarm reported on multiple boards are as
follows:
l Cause 1 (reported on multiple boards): For OptiX OSN 6800 and OptiX OSN 3800: The
AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
NOTE
When the ports on the AUX board for communicating with other boards are faulty, the services
boards report the COMMUN_FAIL alarm but the standby system control board does not report
this alarm.
l Cause 2 (reported on multiple boards): The settings of the DIP switches of the subracks
are incorrect or the subracks are cascaded inappropriately.
l Cause 3 (reported on multiple boards): The system control board or cross-connect board
is faulty.
NOTE
If the active system control board is faulty, the active system control board, standby system control
board, and service boards report the COMMUN_FAIL alarm at the same time.
If the cross-connect board is faulty, the communication on channel 485 fails. In this case, the
cross-connect board and service boards report the COMMUN_FAIL alarm at the same time.
Procedure
l On the U2000, query the alarm to determine the boards that report the alarm and
corresponding alarm parameters.
l Cause 1 (reported on a single board): The board is in the cold reset or warm reset state.
a. View the alarm indicators on the board to check whether the board that reports this
alarm is in the warm reset or cold reset state. If it is, wait for 5 minutes and check
whether the alarm is cleared. For the description of the alarm indicators on the
board, see the Hardware Description.
b. If the alarm persists, see cause 2 (reported on a single board).
l Cause 2 (reported on a single board): The network cables for cascading subracks do not
meet the requirements.
a. Replace the network cables for cascading subracks with standard straight-through
network cables with all eight cores being used. Check whether the alarm is cleared.
b. If the alarm persists, see cause 3 (reported on a single board).
l Cause 3 (reported on a single board): The board is faulty.
a. Replace the board that reports the alarm. Replace the board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l Cause 1 (reported on multiple boards): For OptiX OSN 6800 and OptiX OSN 3800: The
AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty..
For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty.
a. Check whether the AUX board also reports alarms such as BD_STATUS, indicating
abnormal board status. Remove and re-insert the board. For details, see "Removing
Boards" and "Inserting Boards" in the Quick Installation Guide of the applicable
equipment.
b. Check whether the alarm is cleared. If the alarm persists, replace the AUX board.
For details, see "Replacing the AUX Board" in the Parts Replacement.
c. Check whether the alarm is cleared. If the alarm persists, see cause 2 (reported on
multiple boards).
For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
a. Check whether the EFI1 or EFI2 board also reports alarms such as BD_STATUS,
indicating abnormal board status. Remove and re-insert the board. For details, see
"Removing Boards" and "Inserting Boards" in the Quick Installation Guide of the
applicable equipment.
b. Check whether the alarm is cleared. If the alarm persists, replace the EFI1 or EFI2
board. For details, see "Replacing the EFI Board" in the Parts Replacement.
c. Check whether the alarm is cleared. If the alarm persists, see cause 2 (reported on
multiple boards).
l Cause 2 (reported on multiple boards): The settings of the DIP switches of the subracks
are incorrect or the subracks are cascaded inappropriately.
a. Check whether the SUBRACK_LOOP, SUBRACK_ID_CONFLICT, and
SUBRACK_ID_MISMATCH alarms are generated. If yes, clear these alarms in
advance.
b. Check whether the alarm is cleared. If the alarm persists, see cause 3 (reported on
multiple boards).
l Cause 3 (reported on multiple boards): The system control board or cross-connect board
is faulty.
a. Check whether the active system control board or active cross-connect board also
reports the BD_STATUS and HARD_BAD alarms. Remove and re-insert the board.
b. Check whether the alarm is cleared. If the alarm persists, Replace the board.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l If you deliver configuration to the board when the alarm is present on the board, the
board configuration will differ from the NE configuration after the alarm is cleared.
When this occurs, perform a warm reset on the board to ensure synchronization between
the board configuration and NE configuration.
----End
Related Information
Related Cases:
l MC-A191 How to Clear the COMMUN_FAIL Alarm on the OptiX OSN 6800
l MC-A197 High Ambient Temperature Causes the SCC Board on the OptiX OSN 8800
Repeatedly Reports Transient COMMUN_FAIL Alarms
l MC-A213 Internal Communication of an NE Is Abnormal And Many Boards Report
Transiently BD_STATUS or COMMUN_FAIL Alarms Due to Conflicted Subrack IDs
l MC-A223 When a Self-Made Network Cable Is Used, the OptiX OSN 6800 Reports the
COMMUN_FAIL Alarm
l MC-A224 The Network Cable at the COM Port on the EFI Board of the OptiX OSN
6800 Subrack Is Incorrectly Connected. Consequently, All the Boards on the OptiX OSN
6800 Subrack Report the COMMUN_FAIL Alarms
3.8 ETH_8B10B_ERR
Description
This alarm indicates an Ethernet line signal encoding/decoding error. The alarm occurs when
signals are converted from 8bit mode to 10bit mode.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The fiber between the access equipment and the optical port on the client side
of the board is faulty.
l Cause 2: The access equipment is faulty.
l Cause 3: The board hardware is faulty.
Procedure
l Cause 1: The fiber between the access equipment and the optical port on the client side
of the board is faulty.
a. Check whether the attenuation of the fiber between the input equipment and the port
on the client side of the board is overlarge, and whether the fiber is aged or loose. If
it is, clean the fiber connector or replace the fiber jumper.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The access equipment is faulty.
a. Apply a hardware loopback between the transmit and receive optical ports on the
client side of the board. If the alarm persists, it indicates that the board is faulty. In
this case, replace the board.
The board supports pluggable optical Replace the specific pluggable optical
modules, module.
The board does not support pluggable Replace the faulty board. Replace the
optical modules, board.
b. If the alarm is cleared, it indicates that the access equipment on the client side is
faulty. In this case, rectify the fault on the access equipment.
l Cause 3: The board hardware is faulty.
a. Replace the faulty board.
The board supports pluggable optical Replace the specific pluggable optical
modules, module.
The board does not support pluggable Replace the faulty board. Replace the
optical modules, board.
----End
Related Information
None.
3.9 EX_ETHOAM_CC_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.9.2 EX_ETHOAM_CC_LOS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 VLAN ID for the local maintenance point.
Name Meaning
Possible Causes
l Software or hardware faults occur between the source and sink maintenance points.
l Services are blocked or interrupted between the source and sink maintenance points.
Procedure
Step 1 View this alarm on the NMS and determine the ID of the maintenance point that generates the
alarm.
Step 3 Perform the loopback (LB) or linktrace (LT) test on the source and sink maintenance points to
locate source-sink faults.
Step 4 Check the involved software, hardware, and traffic and restore the faulty services. Then, you
can perform a loopback test to check whether the EX_ETHOAM_CC_LOS alarm is cleared.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
Description
This alarm indicates a loss of the periodic continuity check message. When the sink
maintenance point receives the continuity check (CC) message from the source maintenance
point, the timer is started to periodically check the link between the source and sink
maintenance points. If the sink maintenance point does not receive the CC message from the
source maintenance point in one period (3.5 times of the time during which the CC message is
transmitted from the source maintenance point to the sink maintenance point), this alarm is
generated.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameters 1 and 2 2 bytes, indicates the number of the Ethernet port where this alarm is
generated.
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
l Cause 1: A software or hardware failure occurs in the services from the source
maintenance point to the sink maintenance point.
l Cause 2: Service congestion or service interruption occurs between the source
maintenance point and the sink maintenance point.
Procedure
l Cause 1 and Cause 2: A software or hardware failure, service congestion or service
interruption occurs between the source maintenance point and the sink maintenance
point.
a. View the EX_ETHOAM_CC_LOS alarm on the U2000 and confirm the ID of the
relevant maintenance point according to the alarm parameters.
b. Query the information about the maintenance point.
c. Perform loopback (LB) for the source and sink maintenance points, to locate the
fault in the services between the source maintenance point and the sink maintenance
point.
d. Perform checks for the problem services, including software check, hardware
check, and traffic check. After the services restore, the alarm is automatically
cleared. You may perform LB to confirm that the alarm is cleared.
e. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.10 FC_LINK_ERR
Description
The FC_LINK_ERR alarm indicates an FC service link failure. This alarm is generated when
the FC link is faulty.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the status of the transmission link on the WDM side. It is used to
identify the link status on a transmission network.
l 0x00: means WAN_UP, indicating that the transmission link is normal.
l 0x01: means WAN_DOWN, indicating that the transmission link is faulty.
Fault Symptom
Table 3-9 lists the fault symptom for the FC_LINK_ERR alarm.
The WDM side of the opposite board may Cause 1: The WDM side of the opposite
report an R_LOS, R_LOF, OTUk_LOF, OTU reports an R_LOS, R_LOF,
OTUk_LOM, or OTUk_AIS alarm. OTUk_LOF, OTUk_LOM, or OTUk_AIS
alarm. (The value of parameter 1 is 0x01.)
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
l Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow
control management mode occurs. (The value of parameter 2 is 0x01.)
l Cause 3: The type or the time sequence of the services on the board is configured
improperly.
l Cause 4: The type of the client-side optical module on the board mismatches the type of
the actual service, or the actual fiber mismatches the fiber type that the optical module
supports.
l Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).
l Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
Procedure
l Check the information of this alarm on the U2000. Record the parameters of this alarm.
l Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
a. On the U2000, check whether an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or
OTUk_AIS alarm is generated on the WDM side of the connected board. If yes,
handle the alarm properly.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow
control management mode occurs. (The value of parameter 2 is 0x01.).
a. Check the alarm parameters to see whether the ISL mode is incorrect, or the flow
control management mode mismatches. If yes, check the configuration of the client
equipment in the network.
b. Reconfigure the ISL mode and the traffic control management mode.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The type or the time sequence of the services on the board is configured
improperly.
a. Check whether the service type of the OTU at the local station matches the type of
the services transmitted from the client data equipment. If not, change the service
type of the corresponding port on the board or replace the board with another board
that matches the service type. Replace the board.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
b. Check whether the rate that is configured for the services ports on the board where
the alarm is generated matches the rate of the actually received services. If they do
not match, you need to change the type of the accessed services or the type of the
services configured on the board according to the networking planning, thus to
ensure that the rates of these services are consistent.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The type of the client-side optical module on the board mismatches the type of
the actual service, or the actual fiber mismatches the fiber type that the optical module
supports.
a. Check whether the service type that the client-side optical module on the board is
the same as the actual service type. If not, replace the board or replace the optical
module if it is pluggable to ensure the optical module type matches the actual
service type.
b. If the alarm persists, check whether the fiber type supported by the client-side
optical module is the same as the type of the connected fiber. If not, replace the
board or the fiber.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).
a. If the alarm persists, the board that reports the alarm may be faulty. Replace the
board.
b. If the alarm persists, the OTU board at the opposite station may be faulty. In this
case, replace the faulty board.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 6.
l Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
a. If the alarm persists, the client equipment may be faulty. In this case, rectify the
fault on the client equipment.
b. If the alarm persists, the client equipment at the opposite station may be faulty. In
this case, rectify the fault on the client equipment at the opposite station.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.11 FC_SYNC_LOS
Description
This alarm indicates a loss of the FC service synchronous word. This alarm is generated when
the FC service state fails to obtain the signal alignment word.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-10 lists the fault symptom for the FC_SYNC_LOS alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the FC_SYNC_LOS alarm are as follows:
l Cause 1: The rate of the services to be received mismatches the rate of the services that
are actually received.
l Cause 2: The transmit optical power is abnormal.
Procedure
l Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
a. Check whether the rate that is configured on the U2000 of the services at the ports
on the local board matches the rate of the accessed services. If they are not matched,
you need to change the type of the accessed services or the type of the services on
the board according to the networking planning, to ensure that the rates of these
services are the same. The service type for an optical port on the board can be set or
queried on the U2000. For details, see "Querying and Setting the Service Type on
the Client Side of a Board" in the Supporting Tasks.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The transmit optical power is abnormal.
a. On the U2000, check whether the output optical power at the transmit end of the
board is within the permitted range. For the optical power specifications of the
specific board, see "Technical Specifications" in the Product Description. If the
output optical power is abnormal, see the handling procedures for the
OUT_PWR_HIGH and OUT_PWR_LOW alarms to rectify the fault.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.12 IN_PWR_HIGH
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.12.2 IN_PWR_HIGH (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The IN_PWR_HIGH is an alarm indicating a high receive optical power. This alarm is
reported when a board detects that the actual receive optical power exceeds the specified
upper threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Cause 1: The optical power threshold is not set properly.
l Cause 2: The transmit optical power is high at the peer end.
l Cause 3: The alarm-reporting board is faulty.
Procedure
Step 1 Cause 1: The optical power threshold is not set properly.
1. Query the optical-module details for the alarm-reporting board.
2. Check whether the optical power threshold is set properly. If the optical power threshold
is improperly set, reset Input Power Reference Lower Threshold and Input Power
Reference Upper Threshold based on board receiver sensitivity or optical-power
overload indicators.
3. Check whether the IN_PWR_HIGH alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The transmit optical power is high at the peer end.
1. On the NMS, check whether the transmit optical power of the peer board connected to
the local alarm-reporting board is above the specified upper threshold, or whether the
peer board reports the OUT_PWR_HIGH alarm.
If... Then...
The transmit optical power is above the specified upper Go to the next step.
threshold
2. Replace the optical module if it is pluggable on the peer board. Replace the board if the
optical module is unpluggable.
3. Check whether the IN_PWR_HIGH alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The alarm-reporting board is faulty.
1. If the receive optical power of the alarm-reporting board is proper, this board may be
faulty. In this case, replace the 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.
Description
Input optical power being too high. This alarm is generated when the input optical power is
higher than the upper threshold of the input optical power.
Attribute
Parameters
None
Fault Symptom
None
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 (reported from the client side): The input optical power is excessively high, and
the attenuation configured is insufficient.
l Cause 2 (reported from the client side): The board that reports this alarm is faulty.
l Cause 1 (reported from the WDM side): The output optical power of the board in the
upstream station is excessively high.
l Cause 2 (reported from the WDM side): The board that reports this alarm is faulty.
Procedure
l On the U2000, check the alarm information and record the IDs of the port and channel
where the alarm is generated.
l Cause 1 (reported from the client side): The input optical power is excessively high, and
the attenuation configured is insufficient.
a. If the alarm is generated on the client side, query the input optical power of the
board that reports the alarm on the U2000 to check whether the input optical power
is within the permitted range. For the optical power specifications of the specific
board, see "Technical Specifications" in the Product Description. If the input power
is abnormal as shown on the U2000, use a power meter to measure the input optical
power of the board that reports the alarm to check whether the input optical power
is within the permitted range. If the input optical power is abnormal, increase the
attenuation so that the input optical power is within the permitted range.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the board.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 (reported from the client side).
l Cause 2 (reported from the client side): The board that reports the alarm is faulty.
a. If the input optical power of the board that reports the alarm is normal, the board
may be faulty. In this case, replace the board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l Cause 1 (reported from the WDM side): The output optical power of the board in the
upstream station is excessively high.
a. If the alarm is generated on the WDM side, query the input optical power of the
board that reports the alarm on the U2000 to check whether the input optical power
is within the permitted range. For the optical power specifications of the specific
board, see "Technical Specifications" in the Product Description.. If the input
optical power is abnormal, query the input and output optical power of the board in
the upstream direction of the OTU along the reverse signal flow on the U2000. If
the input and output optical power of the upstream board exceeds the permitted
range, adjust the input optical power of the board to a proper value.
b. If the input optical power of the upstream boards is within the permitted range,
whereas the output optical power is abnormal, the upstream board may be faulty.
Replace the board.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 (reported from the WDM side).
l Cause 2 (reported from the WDM side): The board that reports the alarm is faulty.
a. If the input optical power of the board that reports the alarm is normal, the board
may be faulty. In this case, replace the board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l If the alarm is generated in multiple wavelengths, the alarm handling method is similar
to the handling method for this alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
Related Cases:
l MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption, the WDM Side of the LBE Reports the IN_PWR_HIGH and
OTU_LOF Alarms Abruptly
l MC-A97 The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of Optical
Power Reflection
l MC-A194 A Malfunctioning VA1 Board Causes Abnormal Optical Power, The NS2
Boards Reports IN_PWR_HIGH Alarms For Three Times
3.13 IN_PWR_LOW
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.13.2 IN_PWR_LOW (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The IN_PWR_LOW is an alarm indicating a low receive optical power. This alarm is reported
when a board detects that the actual receive optical power exceeds the specified lower
threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Cause 1: The optical power threshold is not set properly.
l Cause 2: The fiber connector is loose or contaminated.
l Cause 3: The transmit optical power is low at the peer end.
l Cause 4: The alarm-reporting board is faulty.
Procedure
Step 1 Cause 1: The optical power threshold is not set properly.
1. Query the optical-module details for the alarm-reporting board.
2. Check whether the optical power threshold is set properly. If the optical power threshold
is improperly set, reset Input Power Reference Lower Threshold and Input Power
Step 3 Cause 3: The transmit optical power is low at the peer end.
1. Replace the optical module if it is pluggable on the peer board. Replace the board if the
optical module is unpluggable.
2. Check whether the IN_PWR_LOW alarm is cleared. If the alarm persists, go to Step 4.
----End
Related Information
None.
Description
Input optical power being too low. The alarm is generated when the input optical power is
smaller than the lower threshold of the input optical power.
Attribute
Parameters
None
Fault Symptom
None
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the IN_PWR_LOW alarm are as follows:
l Cause 1 (reported from the client side): The fiber connector is dirty, and the fiber jumper
is over-bent, damaged or aged.
l Cause 2 (reported from the client side): The attenuation of the attenuator attached to the
optical port on the board that reports this alarm is excessively high.
l Cause 3 (reported from the client side): The board that reports this alarm is faulty.
l Cause 1 (reported from the WDM side): The fiber connector is dirty, and the fiber
jumper is over-bent, damaged or aged.
l Cause 2 (reported from the WDM side): The attenuation of the attenuator attached to the
optical port on the board that reports this alarm is excessively high.
l Cause 3 (reported from the WDM side): The attenuation attached to the transmit optical
port on the board at the opposite station is excessively high, or the transmit optical
module is faulty.
l Cause 4 (reported from the WDM side): The attenuation in the transmission of the
optical signals is excessively high and the compensation is insufficient.
l Cause 5 (reported from the WDM side): The board that reports this alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated. On the U2000, check whether the input optical power of
the board where the alarm is reported is within the permitted range.
l Cause 1 (reported from the client side): The fiber connector is dirty, and the fiber jumper
is over-bent, damaged or aged.
a. Use an optical power meter to measure the input optical power of the local board to
determine whether the input optical power is within the permitted range. For the
optical power specifications of the specific board, see "Technical Specifications" in
the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks to obtain the
manufacturer information of the optical module on the board.
b. If the detected power is excessively low, check the fiber connection. If the fiber
connector is dirty, clean or replace the fiber connector. For details, see "Inspecting
and Cleaning the Fiber-Optic Connectors" in the Supporting Tasks.
c. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent,
damaged or aged, adjust the fiber jumper or Replacing Fiber Jumpers.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 (reported from the client side).
l Cause 2 (reported from the client side): The attenuation of the attenuator attached to the
optical port on the board that reports the alarm is excessively high.
a. If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical port is excessively high. If the attenuation is excessively high,
decrease the attenuation value of the attenuator to a proper value or replace the
attenuator with a suitable attenuator. For details, see "Adjusting, Replacing, Adding
and Removing Attenuator" in the Supporting Tasks.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 (reported from the client side).
l Cause 3 (reported from the client side): The board that reports the alarm is faulty.
a. If the alarm persists, replace the board that reports the alarm.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l Cause 1 (reported from the WDM side): The fiber connector is dirty, and the fiber
jumper is over-bent, damaged or aged.
a. Use an optical power meter to measure the input optical power of the local board to
determine whether the input optical power is within the permitted range. For the
optical power specifications of the specific board, see "Technical Specifications" in
the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks to obtain the
manufacturer information of the optical module on the board.
b. If the detected power is excessively low, check the fiber connection. If the fiber
connector is dirty, clean or replace the fiber connector. For details, see "Inspecting
and Cleaning the Fiber-Optic Connectors" in the Supporting Tasks.
c. If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent,
damaged or aged, adjust the fiber jumper or replacing fiber jumpers.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 (reported from the WDM side).
l Cause 2 (reported from the WDM side): The attenuation of the attenuator attached to the
optical port on the board that reports the alarm is excessively high.
a. Check whether the attenuation of the attenuator attached to the receive optical port
is excessively high. If the attenuation is excessively high, decrease the attenuation
value of the attenuator to a proper value or replace the attenuator with a suitable
attenuator. For details, see "Adjusting, Replacing, Adding and Removing
Attenuator" in the Supporting Tasks.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 (reported from the WDM side).
l Cause 3 (reported from the WDM side): The attenuation attached to the transmit optical
port on the board at the opposite station is excessively high, or the transmit optical
module is faulty.
a. Check the board at the opposite station. If the laser on the board is turned off, turn
on it on the U2000.
b. Check whether the alarm is cleared. If the alarm persists, check whether an optical
attenuator with excessively high attenuation is attached to the transmit optical port
on the board at the opposite station. If it is, decrease the attenuation to a proper
value or replace the optical attenuator so that the output optical power of the
opposite board is normal. For details, see "Adjusting, Replacing, Adding and
Removing Attenuator" in the Supporting Tasks.
c. Check whether the alarm is cleared. If the alarm persists, check the output optical
power performance values and alarms of the board. If the reported alarms or
performance values are different from the specification values, see the
corresponding handling procedure for the alarms or performance events to rectify
the fault.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4 (reported from the WDM side).
l Cause 4 (reported from the WDM side): The attenuation in the transmission of the
optical signals is excessively high and the compensation is insufficient.
a. Query the input and output optical power of the boards in the upstream direction of
the OTU at the local station along the reverse signal flow on the U2000. Locate the
board with the excessively low optical power and adjust the input optical power of
the board to a proper value. For details, see "Adjusting, Replacing, Adding and
Removing Attenuator" in the Supporting Tasks.
b. Check the input and output optical power of the upstream stations one by one along
the reverse signal flow on the U2000 and locate the faulty section where the optical
power is excessively low.
c. If the output optical power of the upstream station is normal, check the cables, fiber
jumpers, fiber connectors, and attenuators. If the attenuation of the cables is higher
than the attenuation in the engineering design, adjust the attenuator, or rectify or
change the cables. If the fiber jumper, fiber connector or the attenuator is dirty,
clean or replace the fiber jumper, fiber connector or attenuator.
d. If the output optical power of the upstream station is abnormal, troubleshoot the
faults at the upstream station so that the output optical power is normal.
e. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5 (reported from the WDM side).
l Cause 5 (reported from the WDM side): The board that reports the alarm is faulty.
a. If the alarm persists, the board that reports the alarm may be faulty. Replace the
board.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
Related Cases:
l MC-A19 Use Power Monitoring To Process Problems on IN_PWR_LOW Alarm
l MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
l MC-A66 The Received Optical Power of Downstream Stations Is not Flat and Some
Wavelengths Report the IN_PWR_LOW Alarm
l MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
l MC-A201 Frequent Fiber Cut Results in High Line Attenuation and the IN_PWR_LOW
Alarm Reported by the OTU Board
l MC-A217 An IN_PWR_LOW Alarm Is Reported After an Optical-Layer ASON Service
Is Configured on the ASON OptiX OSN 6800 NE
3.14 INTRA_OTU_PS
Description
Intra-board 1+1 protection switching. This alarm is generated when an intra-board 1+1
protection group undergoes protection switching in which the active channel switches from
the working channel to the protection channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-13 lists the fault symptoms for the INTRA_OTU_PS alarm.
Protection switching is performed, and the Cause 2: The services of the working
board on the working channel reports channel of the intra-board 1+1 protection
alarms that can trigger protection switching. group are faulty. The active channel
automatically switches to the protection
channel and the alarm is reported.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching. Such a command makes the active channel of the intra-board 1+1
protection group switch from the working channel to the protection channel. Therefore,
the alarm is reported.
l Cause 2: The services on the working channel of the intra-board 1+1 protection group
are faulty. The active channel automatically switches to the protection channel and the
alarm is reported.
Procedure
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching.
a. On the U2000, query the switching status of the protection group. If the switching
state is forced switching or manual switching, check whether the external switching
operation is necessary.
b. If the external switching operation is necessary, ignore the alarm.
c. If the external switching operation is unnecessary, deliver an external command to
switch the active channel to the working channel to clear the alarm.
l Cause 2: The services on the working channel of the intra-board 1+1 protection group
are faulty. The active channel automatically switches to the protection channel and the
alarm is reported.
a. Query whether alarms related to the services are reported on the boards in the
protection group, such as R_LOF, R_LOS, POWER_DIFF_OVER, R_LOC,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC. If there are
such alarms, handle the alarms by referring to the alarm handling procedure.
b. If the alarm persists, check whether the attribute of the protection group is
Revertive. If it is, the active channel automatically switches to the working channel
and the alarm clears after WTR Times. If the attribute is Non-Revertive, set it to
Revertive, The alarm clears after WTR Times.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
For details, see "Intra-Board 1+1 Protection" in the Feature Description.
3.15 LASER_MODULE_MISMATCH
Description
This alarm indicates a mismatch of the optical module type and the fiber type. This alarm is
generated when the type of the optical module inserted into an optical port mismatches the
type of optical port.
Attribute
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
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 they mismatch, 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
assistance.
----End
Related Information
None.
3.16 LINK_ERR
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.16.2 LINK_ERR (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The LINK_ERR is an alarm indicating data link errors. This alarm is reported when
connections are incorrect and port negotiation fails on an Ethernet.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Cause 1: The transmit and receive ports work in different modes.
l Cause 2: Ethernet boards at both ends have different optical modules, or the types of the
two optical modules do not match those of the fibers connected to them.
l Cause 3: The fibers or cables connected to the Ethernet ports fail.
l Cause 4: The board is faulty.
Procedure
Step 1 View the alarm on the NMS, and determine the board that reports the alarm and the ID of the
port that reports the alarm according to alarm parameters.
Step 2 Cause 1: The transmit and receive ports work in different modes.
1. Check whether the transmit and receive ports work in the same mode. If they work in
different modes, for example, a port works in autonegotiation mode while the other port
works in non-autonegotiation mode, configure the working mode to keep its consistency
between both ports. in the Configuration Guide
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: Ethernet boards at both ends have different optical modules, or the types of the two
optical modules do not match those of the fibers connected to them.
1. Check whether the Ethernet boards at both ends have the same optical module. If they
have different optical modules, such as single- and multi-mode optical modules, replace
the optical module on either board to keep its consistency. If the optical module on the
board is pluggable, replace the optical module. For details, see the Parts Replacement.
2. Then, check whether the LINK_ERR alarm is cleared. If the alarm persists, check
whether the types of the two optical modules match those of the fibers connected to
them. If the type of an optical module does not match that of its fiber, for example, a
single-mode fiber is connected to a multi-mode optical module, replace the optical
module or fiber to keep the type consistency between them.
3. Check whether the LINK_ERR alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 3: The fibers or cables connected to the Ethernet ports fail.
1. Check whether the fibers or cables are properly connected to the Ethernet ports. If the
fibers or cables are improperly connected or even fail, re-connect or replace them.
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, go to Step 5.
If... Then...
The alarm is cleared Replace the peer board. For details, see Parts Replacement.
If... Then...
The alarm persists Replace the local board. For details, see Parts Replacement.
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-15 lists the fault symptom for the LINK_ERR alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
l Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet
ports are inconsistent. For example, one port is in auto-negotiation mode but the other is
in non-negotiation mode.
l Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or low.
l Cause 4: The fiber or cable that connects the two Ethernet ports fails.
l Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Therefore, the types of fibers that the two optical modules can be connected
to are inconsistent.
l Cause 6: The data equipment on the client side is faulty.
l Cause 7: The board that reports this alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is reported.
l Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
a. Check whether the service type of the OTU at the local station matches the type of
the services transmitted from the client data equipment. If they mismatch, change
the service type of the corresponding port on the board or replace the board with
another board that matches the service type.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports
are inconsistent.
a. Check whether the auto-negotiation mode of the optical port on the board that
reports the alarm is consistent with that of the client data equipment. If they are
inconsistent, modify the setting to ensure the consistency.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or low.
a. Check whether the input optical power of the two interconnected Ethernet ports is
within the permitted range. For the optical power specifications of the specific
board, see "Technical Specifications" in the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the board.
b. If the input optical power is abnormal, see the handling procedures for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The fiber or cable that connects the two Ethernet ports fails.
a. Check whether the fiber or cable that connects the two Ethernet ports is properly
connected. If it is not properly connected, reconnect or replace the fiber or cable.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Therefore, the types of fibers that the two optical modules can be connected
to are inconsistent.
a. Check whether the types of the optical modules on two interconnected boards are
consistent. If they are inconsistent, replace the boards or optical modules to ensure
the optical module type consistency.
b. If the alarm persists, check whether the optical module types of the two
interconnected boards match the type of the fiber that connects the two boards. If
they are inconsistent, replace the board whose optical module type does not match
the fiber board.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 6.
l Cause 6: The data equipment on the client side is faulty.
a. Apply a hardware loopback between the transmit and receive optical ports on the
client side of the board. If the alarm persists, the OTU at the local station is faulty.
For details, see the alarm handling procedure for cause 7.
b. If the alarm is cleared, the data equipment on the client side is faulty. In this case,
rectify the fault on the data equipment.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 7.
l Cause 7: The board that reports the alarm is faulty.
a. Perform a cold reset on the faulty board on the U2000.
b. If the alarm persists, the board that reports the alarm may be faulty. Replace the
board.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
The LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
l MC-A102 The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS
Alarm
l MC-A128 EPL Service Was Interrupted Due To a Service Mode Mismatch of L4G
Boards and Nodes Report R_LOF, ODU5G_PS_AIS, OTU5G_LOF, LINK_ERR Alarm
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
3.17 LOOP_ALM
Refer to the alarm page according to the type of the board that reports the alarm.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 optical interface number of the board.
Name Meaning
Possible Causes
Cause 1: A loopback command is issued for the test or maintenance purpose.
Procedure
Step 1 View the alarm on the NMS and determine the port that reports the alarm.
Step 2 Cause 1: A loopback command is issued for the test or maintenance purpose.
1. Check whether the loopback is configured for the test or maintenance purpose. If the test
or maintenance is complete, eliminate the loopback on the port with reference to
Supporting Tasks.
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.
Description
This alarm is generated when the optical port of a board is in the loopback state.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The loopback command is delivered during testing or maintenance.
a. Check whether the loopback is set on the optical port during testing or maintenance.
After the test or maintenance is complete, release the loopback configured for the
specific optical port. For details, see "Performing Inloop and Outloop" in the
Supporting Tasks.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.18 LPT_ACTIVE
Description
This alarm indicates that LPT switching occurred. The data equipment itself has protection
schemes. Hence, the protection provided by the WDM equipment is not needed. However, the
WDM equipment is needed for informing the data equipment about the faults in the
transmission layer. In this way, the switching would be triggered for the data equipment. The
alarm is generated when switching is triggered.
Attribute
Parameters
None.
Fault Symptom
Table 3-17 lists the fault symptoms for the LPT_ACTIVE alarm.
The R_LOS, LINK_ERR or L_SYNC alarm Cause 1: The input signals on the client side
may be generated on the client side of the are missing or the local board detects a
board. LINK_ERR or L_SYNC alarm.
An R_LOF alarm may be generated on the Cause 4: When the WDM equipment
WDM side. receives data services and the SDH frames
are transmitted on the WDM side, this alarm
may be triggered by the R_LOS or R_LOF
alarm on the WDM side.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The input signals on the client side are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
l Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
l Cause 3: When the WDM equipment receives data services and the OTN frames are
transmitted on the WDM side, this alarm may be triggered by the R_LOS, OTUk_AIS,
OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS,
ODUk_TCMn_OCI, or ODUk_TCMn_LCK alarm on the WDM side.
l Cause 4: When the WDM equipment receives data services and the SDH frames are
transmitted on the WDM side, this alarm may be triggered by the R_LOS or R_LOF
alarm on the WDM side.
l Cause 5: Regarding to separation of the tributary board from the line board, if the cross-
connection configuration does not exist, the alarm is generated.
Procedure
l On the U2000, check the alarm information and record the IDs of the port and channel
where the alarm is generated.
l Check whether the service type received by the WDM equipment and the frame format
transmitted on the WDM side is consistent with that of the service configuration model
using the U2000. If they are not consistent, configure them to ensure the consistency.
l Cause 1: The input signals on the client side are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
a. Check whether the R_LOS, LINK_ERR or L_SYNC alarm is generated on the
client side. If it is, clear the R_LOS, LINK_ERR or L_SYNC alarm.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
a. Check whether an REM_SF alarm is generated on the client side. If it is, clear the
REM_SF alarm.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: When the WDM equipment accesses the data services and the OTN frames are
transmitted on the WDM side, the alarm may be triggered by the R_LOS, OTUk_AIS,
OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS,
ODUk_TCMn_OCI or ODUk_TCMn_LCK alarm on the WDM side.
a. If the frames on the WDM side are transmitted in the OTN format, check whether
the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI or
ODUk_TCMn_LCK alarm is generated. If it is, clear the alarm.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: When the WDM equipment accesses the data services and the SDH frames are
transmitted on the WDM side, the alarm may be triggered by the R_LOS or R_LOF
alarm on the WDM side.
a. If the frames on the WDM side are transmitted in the SDH format, check the
R_LOS or R_LOF alarm information on the U2000 and clear the alarm.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5.
l Cause 5: Regarding to separation of the tributary board from the line board, if the cross-
connection configuration does not exist, the alarm is generated.
a. Check the trails of the cross-connect services according to the board that reports the
alarm. Regarding to separation of the tributary board from the line board, check
whether the cross-connection is configured on the U2000. If not, configure the
cross-connection.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
As a link-based protection scheme, link pass through (LPT) provides the required network-
level protection for point-to-point private line services by means of point-to-point link pass
through.For details, see "LPT(OTN)" in the Feature Description.
3.19 LSR_WILL_DIE
Description
This alarm indicates that the laser life will end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the LSR_WILL_DIE alarm are as follows:
Cause 1: The laser is aging. The service life of the laser will be terminated.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser is aging. The service life of the laser will be terminated.
a. Check whether the board that reports this alarm supports pluggable optical modules.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The detection circuit of the board is faulty.
a. Replace the board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.20 MS_AIS
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.20.2 MS_AIS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Parameters
None.
Possible Causes
l Cause 1: The local receive board is faulty.
l Cause 2: The active and standby cross-connect boards on the upstream NE are not
detected.
l Cause 3: The transmit or cross-connect board on the upstream NE is faulty.
Procedure
Step 1 Cause 1: The local receive board is faulty.
1. Cold reset the local receive board on the NMS or directly remove and insert the board.
For details about how to cold reset a board, see the Supporting Tasks. Then, check
whether the alarm is cleared.
NOTICE
If services on the board are not protected, cold resetting the board interrupts services.
2. If the alarm persists, replace the local receive board. For details, see Parts Replacement.
Then, check whether the alarm is cleared.
3. If the alarm persists, go to Step 2.
Step 2 Cause 2: The active and standby cross-connect boards on the upstream NE are not detected.
1. Check whether the active and standby cross-connect boards are loose on the upstream
NE. If yes, insert the boards firmly. Then, check whether the alarm is cleared.
2. If the alarm persists, cold reset the cross-connect boards on the NMS. For details, see the
Supporting Tasks. Then, check whether the alarm is cleared.
NOTICE
If there is no standby cross-connect board, cold resetting the active cross-connect board
may interrupt services.
----End
Related Information
None.
Description
This alarm is a multiplex section alarm indication. The alarm is generated when the input
signals from the client side contain the MS_AIS signal or the receive side of the local station
is faulty.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The input signals from the client side contain the MS_AIS signal, as shown in
the following figure.
Detects and
reports the
MS_AIS alarm
Station A Station B
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The input signals from the client side contain the MS_AIS signal
a. Apply a hardware loopback between the transmit and receive optical ports on the
client side of OTU(A). If the alarm on OTU(A) persists, it indicates that OTU(A) is
faulty. In this case, see the alarm handling procedure for cause 2.
b. If the alarm is cleared, it indicates that the input signals on the client side contain bit
errors. In this case, rectify the fault on the client equipment.
l Cause 2: The board that reports the alarm is faulty.
a. If the alarm persists, the board that reports the alarm is faulty. Replace the board.
If... Then...
The board supports pluggable optical Replace the specific pluggable optical
modules, module.
The board does not support pluggable Replace the faulty board. Replace the
optical modules, board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A57 How to Clear OTU Alarms Because of Unused Ports
3.21 MS_RDI
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.21.2 MS_RDI (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The local NE receives an alarm such as R_LOS and MS_AIS.
l The local transmit board is faulty.
l The peer receive board is faulty.
Procedure
Step 1 Check whether an alarm, such as R_LOS, R_LOF, MS_AIS, B2_EXC, and B2_SD, occurs on
the peer board. If yes, clear the alarm. Then, check whether the MS_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the local board is faulty. If yes, cold reset the local board.
Then, check whether the alarm is cleared.
Step 3 If the alarm persists, replace the local board. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the peer board is faulty. If yes, cold reset the peer board.
Then, check whether the alarm is cleared.
Step 5 If the alarm persists, replace the peer board. Then, check whether the alarm is cleared.
Step 6 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
Description
This alarm is a multiplex section remote defect indication. The alarm is generated at the local
station if the opposite station back transmits the information through overhead when the
WDM-side receive part of the opposite station is faulty (for example, the R_LOS, R_LOF or
MS_AIS alarm is generated).
Attribute
Parameters
None
Fault Symptom
Table 3-20 lists the fault symptom for the MS_RDI alarm.
The board at the opposite station reports an Cause 1 (reported from the WDM side): The
R_LOS, R_LOF, or MS_AIS alarm. receiver on the WDM side at the opposite
station detects a signal failure.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 (reported from the client side): For the OTU board whose client side supports
the SDH services, the input signals from the client side contain the MS_RDI signal. As
shown in the following figure, the input signals from the client side of the OTU board at
the local station A contain the MS_RDI signals. The OTU of the station A reports the
MS_RDI alarm on the client side after it detects the MS_RDI signals.
Client O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
l Cause 1 (reported from the WDM side): The receiver on the WDM side at the opposite
station detects a signal failure. (For example, an R_LOS, R_LOF, or MS_AIS alarm is
generated.) As shown in the following figure, the WDM side of the OTU board in station
B (the opposite station) sends the MS_RDI signals back to station A (the local station)
after it detects and reports the R_LOS, R_LOF or MS_AIS alarm. The WDM side of the
OTU board in station A reports the MS_RDI alarm after it detects the MS_RDI signals.
Detects and reports the R_LOS,
R_LOF, MS_AIS alarm
Client O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
Detects and reports the Sends the MS_RDI
MS_RDI alarm signal back
l Cause 2 (reported from the WDM side): The board that reports the alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1 (reported from the client side): In the case of the OTU board of which the client
side supports the SDH service, the input signals from the client side contain the MS_RDI
signal.
a. When the MS_RDI alarm is reported from the client side, rectify the fault on the
client equipment connected to the OTU board. For details, see the related manual of
the client equipment.
l Cause 1 (reported from the WDM side): The receiver on the WDM side at the opposite
station detects a signal failure (for example, an R_LOS, R_LOF or MS_AIS alarm is
generated).
a. Query the alarm of the board at the opposition station by using the U2000. If an
R_LOS, R_LOF or MS_AIS alarm exists, see the handling procedure of the
R_LOS, R_LOF, or MS_AIS alarm for troubleshooting.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the WDM side.
l Cause 2 (reported from the WDM side): The board that reports the alarm is faulty.
a. If the alarm persists, the board at the local station is faulty. Consider whether to
replace the faulty board according to the actual situation (for example, whether
replacing the board affects the services).
The board supports pluggable optical Replace the specific pluggable optical
modules, module.
The board does not support pluggable Replace the faulty board. Replace the
optical modules, board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.22 MUT_LOS
Description
Loss of multiplexed signals. This alarm is generated when the input multiplexed signals of the
board are lost.
Attribute
Parameters
None
Fault Symptom
Table 3-21 lists the fault symptom for the MUT_LOS alarm.
There is no input optical power on the Cause 1: The fiber connected to an optical
optical port where the MUT_LOS alarm is port at the receive end of the board that
reported. reports the alarm is not connected,
incorrectly connected, or damaged.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The fiber connected to an optical port at the receive end of the board that
reports the alarm is not connected, incorrectly connected, or damaged.
l Cause 2: The attenuation of the signals during line transmission is excessively high.
l Cause 3: The board that reports the alarm is faulty.
l Cause 4: For the TN97ASE board, the insertion loss between the TITL and RITL optical
ports is excessively high.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l On the U2000, check whether the boards on the multiplexing link in the upstream
direction report this alarm along the reverse direction of the signal flow.
l Cause 1: The fiber connected to an optical port at the receive end of the board that
reports the alarm is not connected, incorrectly connected, or damaged.
a. Check whether the fiber connected to an optical port at the receive end of the board
that reports the alarm is not connected or incorrectly connected. If it is not
connected or incorrectly connected, ensure that it is properly connected.
b. Check the fibers or fiber connectors on the board that reports this alarm are dirty. If
they are dirty, see Checking Fiber Jumpers by Using an Optical Power Meter or
Replace the Fiber Jumper to rectify the fault.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The attenuation of the signals during line transmission is excessively high.
a. Use an optical power meter to measure the actual receive optical power of the board
that reports the alarm. Check whether the receive optical power is within the
permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the board.
b. If the receive optical power is excessively low, check whether an optical attenuator
with excessively high attenuation is attached to the receive optical port on the
board. If it is, decrease the attenuation of the optical attenuator to a proper value or
replace the optical attenuator with a proper one.
c. If the alarm persists, check whether the attenuation of the built-in VOA in the
upstream board is excessively high. If it is, adjust the attenuation of the VOA to a
proper value.
d. Check whether the alarm is cleared. If the alarm persists, the optical cables between
stations may be faulty. In this case, rectify the fault on the optical cables.
e. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports the alarm is faulty.
a. If the alarm persists, the board that reports the alarm may be faulty. Replace the
board.
If... Then...
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l Cause 4: For the TN97ASE board, the insertion loss between the TITL and RITL optical
ports is excessively high.
a. Using U2000, query the output optical power of the TITL optical port and the input
optical power of the RITL optical port on the ASE board and calculate the insertion
loss between the two optical ports.
NOTE
Insertion loss = Output optical power of the TITL optical port - Input optical power of the
RITL optical power. On U2000, the insertion loss is the difference between the optical
power of optical port 1 and that of optical port 4.
b. If the insertion loss is excessively high, clean the fiber connectors on the TITL and
RITL optical ports.
c. Check whether the alarm is cleared. If the alarm persists, replace the fiber
connector.
d. Check whether the alarm is cleared. If the alarm persists, check the connection
scenarios of the TITL and RITL optical ports.
n If the TITL and RITL optical ports are connected to the ITL board, check
whether the insertion loss of the ITL board is normal. If it is abnormal, replace
the ITL board.
n If the TITL and RITL optical ports are short-circuited, check whether the
insertion loss of the short-circuited fiber jumper is normal. If it is abnormal,
replace the short-circuited fiber jumper.
e. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers
to handle the alarm.
----End
Related Information
Related Cases:
l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
l MC-A15 The Downstream Optical Amplifier Board Does Not Report MUT_LOS
l MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
l MC-A151 OWSP Protection Switching Fails Due to Incorrect Connection of Fiber
Jumpers On The DCP Boards, DCP Boards Report The MUT_LOS Alarms And TDG
Board Reports The OPU1_PLM Alarm
l MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper, the OAU Board Reports the MUT_LOS Alarm
l MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board
Causes Low Receive Optical Power, The Connected OAU Board At The Downstream
Station Reports MUT_LOS And R_LOS Alarms
l MC-A245 Physical Optical Cable Is Interrupted But Logical Fibers Connected to the
FIU Board Do Not Change to Red on the NMS
3.23 OA_LOW_GAIN
Description
Gain of an optical amplifier (OA) board being low. This alarm is generated when the actual
gain of an OA board is 3 dB lower than the nominal gain.
Attribute
Parameters
None
Fault Symptom
Table 3-22 lists the fault symptom for the OA_LOW_GAIN alarm.
The OAU board that reports this alarm also Cause 1: The input optical power of the
reports a power high alarm, such as OAU board is excessively high.
SUM_INPWR_HI.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The input optical power of the board is excessively high.
l Cause 2: This alarm may be generated because the insertion loss between the TDC and
RDC optical ports is excessively high. (This cause is applicable only to the OAU board.)
l Cause 3: The board that reports the alarm is faulty.
Procedure
l Cause 1: The input optical power of the board is excessively high.
a. On the U2000, check whether the receive optical power of the board is within the
permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
b. If the input optical power is not within the permitted range, adjust the optical
attenuator attached to the input optical port so that the input optical power meets the
specification requirement. For details, see "Adjusting, Replacing, Adding and
Removing Attenuator" in the Supporting Tasks.
c. If no optical attenuator is attached to the input optical port, add an optical attenuator
to ensure that the input optical power meets the specification requirement. For
details, see "Adjusting, Replacing, Adding and Removing Attenuator" in the
Supporting Tasks.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The insertion loss between the TDC and RDC optical ports is excessively high.
(This cause is applicable only to the OAU board.)
a. On the U2000, check the optical power at the TDC and RDC optical ports on the
OAU, and then calculate the insertion loss between the TDC and RDC optical ports.
For details, refer to "Querying the Insertion Loss Between the TDC and RDC
optical ports on the OAU board".
NOTE
Insertion loss = Optical power at the TDC optical port - Optical power at the RDC optical
port. On the U2000, the difference between the optical power at optical port 3 and the optical
power at optical port 5 represents the insertion loss.
b. If the insertion loss is excessive, clean the fiber jumper and fiber connector between
the TDC and RDC optical ports. For details, refer to "Inspecting and Cleaning the
Fiber-Optic Connectors". For the insertion loss specification, see the Product
Description. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
c. Check whether the alarm is cleared. If the alarm persists, replace the DCM module
between the TDC and RDC optical ports.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports the alarm is faulty.
a. Replace the faulty board.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.24 ODU_SNCP_PS
Description
ODUk SNCP protection switching. This alarm is generated on the board of working channel
when an ODU SNCP protection group actuates switching in which the current channel
switches to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-23 lists the fault symptoms for the ODU_SNCP_PS alarm.
Protection switching is performed, and the Cause 2: The services on the working
board on the working channel reports channel of the ODUk SNCP protection
alarms that can trigger protection switching. group are faulty and therefore services are
automatically switched to the protection
channel.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching. Such a command switches the services of the ODUk SNCP protection
group from the working channel to the protection channel.
l Cause 2: The services on the working channel of the ODUk SNCP protection group are
faulty and therefore services are automatically switched to the protection channel.
Procedure
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching.
a. On the U2000, query the switching state of the protection group. If the switching
state is forced switching or manual switching, check whether the external switching
operation is necessary.
b. If the external switching operation is necessary, ignore the alarm.
c. If the external switching operation is unnecessary, deliver an external command to
switch the current channel to the working channel.
l Cause 2: The services on the working channel of the ODUk SNCP protection group are
faulty and therefore services are automatically switched to the protection channel.
a. Query whether the related boards for configuring the protection group have service-
related alarms, for example, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_LTC,
ODUk_TCMn_TIM, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, ODUk_TCMn_DEG, ODUk_TCMn_EXC. If they do, handle
the alarms by referring to the corresponding handling procedure of the alarms.
b. If the alarm persists, check whether the attribute of the protection group is
Revertive. If it is, after WTR Time the active channel automatically switches to
the working channel and the alarm is cleared. If the attribute is Non-Revertive, set
it to Revertive, and after WTR Time the alarm is cleared.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
For details, see "ODUk SNCP Protection" in the Feature Description.
Related Cases:
l MC-A157 An OptiX OSN 6800 Network Cannot Be Reverted Back to the Working
Channel After Being Restored from an ODUk SNCP Protection Switching, The Board
Reports The ODU_SNCP_PS Alarm
3.25 ODUk_PM_AIS
Description
ODUk PM alarm indication signal. An AIS signal is transmitted to the downstream station,
indicating that a signal failure is detected at the upstream station.
k indicates the level of rate.
l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-24 lists the fault symptoms for the ODUk_PM_AIS alarm.
The client side of the corresponding OTU Cause 1 (reported from the WDM side): The
board at the opposite station reports an client side of the corresponding OTU board
ODUk_PM_AIS, R_LOS, OTUk_LOF, at the opposite station reports an
OTUk_LOM, or OTUk_TIM alarm. ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm and
then inserts an AIS signal to the local
station.
The WDM side of the OTU board at the Cause 2 (reported from the WDM side): The
local station reports an R_LOS, WDM side of the OTU board at the local
OTUk_LOF, OTUk_LOM, or OTUk_TIM station reports an R_LOS, OTUk_LOF,
alarm. OTUk_LOM, or OTUk_TIM alarm, and
therefore the board at the local station also
reports an ODUk_PM_AIS alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the ODUk_PM_AIS alarm are as follows:
Cause 1 (reported from the client side): Signals input from the client side contain an
ODUk_PM_AIS signal.See the following figure.
l The input signals on the client side of the OTU at station A contain ODUk_PM_AIS
signals. The OTU at station A reports an ODUk_PM_AIS alarm on the client side after
detecting the ODUk_PM_AIS signals.
The client
signals contain
the ODUk_PM_AIS
signal O O
Client T WDM WDM T Client
side U side side U side
Station A Station B
Cause 2 (reported from the client side): The board that reports the alarm is faulty.
Cause 1 (reported from the WDM side): The client side of the corresponding board at the
opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or
OTUk_TIM alarm, and then inserts an AIS signal to the local station.See the following figure.
l The client side of the OTU at station A automatically inserts an ODUk_PM_AIS signal
into the WDM-side signals after detecting an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm. The WDM side of the OTU at station B reports an
ODUk_PM_AIS alarm after detecting an ODUk_PM_AIS signal.
Detects and reports the
ODUk_PM_AIS, R_LOS, Insert the Detects and reports
OTUk_LOF, OTUk_LOM, ODUk_PM_AIS the ODUk_PM_AIS alarm
OTUk_TIM alarm signal
Station A Station B
Cause 2 (reported from the WDM side): The WDM side of the OTU board at the local station
reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and therefore the OTU
board at the local station also reports an ODUk_PM_AIS alarm.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1 (reported from the client side): Signals input from the client side contain an
ODUk_PM_AIS signal.
a. If this alarm is reported from the client side of the board, apply a hardware
loopback between the transmit and receive optical ports on the client side of OTU1.
If the alarm on OTU1 persists, the OTU1 hardware is faulty. See the alarm handling
procedure for cause 2 of this alarm generated on the client side.
b. If the alarm is cleared, the input signals on the client side of the board contain
ODUk_PM_AIS signals. Rectify the fault on the client equipment.
l Cause 2 (reported from the client side): The board that reports the alarm is faulty.
a. Check whether the board that reports this alarm supports pluggable optical modules.
l Cause 1 (reported from the WDM side): The client side of the corresponding OTU board
at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM,
or OTUk_TIM alarm and then inserts an AIS signal to the local station
a. On the U2000, check whether an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM or OTUk_TIM alarm exists on the client side of the OTU board at
the opposite end. If the alarm exists, check the equipment at the opposite station.
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the WDM side.
l Cause 2 (reported from the WDM side): The WDM side of the OTU board at the local
station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and
therefore the OTU board at the local station also reports an ODUk_PM_AIS alarm.
a. On the U2000, check whether an R_LOS, OTUk_LOF, OTUk_LOM, or
OTUk_TIM alarm exists on the WDM side of the OTU at the local station. If yes,
rectify the fault at the local station to clear the alarm.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
ITU-T G.709
Related Cases:
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
3.26 ODUk_PM_BDI
Description
ODUk PM backward defect indication. This alarm is generated when the PM section at the
opposite station detects a signal failure and inserts a BDI alarm to the local station.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-25 lists the fault symptom for the ODUk_PM_BDI alarm.
The board at the opposite station reports an Cause 1 (reported from the WDM side): The
R_LOS, OTUk_LOF, OTUk_LOM, WDM side of the corresponding board at
ODUk_PM_LCK, ODUk_PM_OCI, the opposite station reports an R_LOS,
ODUk_PM_TIM, or ODUk_PM_SSF OTUk_LOF, OTUk_LOM,
alarm. ODUk_PM_LCK, ODUk_PM_OCI,
ODUk_PM_TIM, or ODUk_PM_SSF alarm
and inserts an ODUk_PM_BDI back to the
local station (station A).
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 (reported from the client side): Signals input from the client side contain an
ODUk_PM_BDI signal.
l Cause 2 (reported from the client side): The board that reports this alarm is faulty.
l Cause 1 (reported from the WDM side): The WDM side of the corresponding board at
the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and inserts an
ODUk_PM_BDI back to the local station (station A).
O O
Client WDM WDM Client
T side T
side U side U side
Station A Station B
Detects and reports the Sends the
ODUk_PM_BDI alarm ODUk_PM_BDI signal
back
Procedure
l On the U2000, check whether there is an alarm with higher severity on the board. If there
is, handle the alarm properly.
l Cause 1 (reported from the client side): Signals input from the client side contain an
ODUk_PM_BDI signal.
a. If this alarm is reported from the client side of the board, apply a hardware
loopback between the transmit and receive optical ports on the client side of OTU
board. If this alarm persists, the board is faulty. In this case, see the alarm handling
procedure for cause 2 of this alarm generated on the client side.
NOTICE
A loopback on the board interrupts the existing services.
b. If this alarm is cleared, the input signals on the client side of the board contain bit
errors. Rectify the fault on the client equipment.
l Cause 2 (reported from the client side): The board that reports this alarm is faulty.
a. Check whether the board that reports this alarm supports pluggable optical modules.
l Cause 1 (reported from the WDM side): The WDM side of the corresponding board at
the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM, ODUk_PM_LCK,
ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and inserts an
ODUk_PM_BDI back to the local station.
a. If this alarm is reported from the WDM side, check whether the corresponding
OTU board at the opposite station receives an R_LOS, OTUk_LOF,
OTUk_LOM, ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or
ODUk_PM_SSF alarm by using the U2000. If yes, handle the corresponding alarm
at the opposite station.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
ITU-T G.709
3.27 ODUk_PM_DEG
Description
ODUk PM signal degraded. This alarm is generated if signal degradation occurs or the bit
error count exceeds the threshold when the BIP8 detection is in burst mode and generated if
signal degradation occurs when the BIP8 detection in poisson mode.
Attribute
Parameters
None
Fault Symptom
Table 3-26 lists the fault symptom for the ODUk_PM_DEG alarm.
The OTU board at the local station may Cause 1: The attenuation of received signals
report an IN_PWR_LOW or BEFFEC_EXC is excessively large. As a result, the input
alarm. optical power of the board is abnormal.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the ODUk_PM_DEG alarm are as follows:
Procedure
l Cause 1: The input optical power of the OTU board is abnormal.
a. On the U2000, view the alarms of the entire network to confirm the slot ID, port ID,
and channel ID of the board that generates this alarm.
b. Along the service signal flow, check whether the input optical power of the point
that first generates this alarm is within the permitted range. For the optical power
specifications of the specific board, see "Technical Specifications" in the Product
Description.
c. If the optical power is within the permitted range, query historical performance data
of the optical power on the U2000 to check whether there is an exception. For
details, see "Checking Historical WDM Performance Events" in the Supporting
Tasks. If there is an exception, see the alarm handling procedure for cause 2.
d. If the optical power is not within the permitted range, adjust the input optical power
of the board to a proper value. For details, see "Adjusting, Replacing, Adding and
Removing Attenuator" in the Supporting Tasks.
e. Check whether the alarm is cleared. If the alarm persists, troubleshoot this alarm
station by station along the service signal flow.
f. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The fiber on the transmission line is abnormal.
a. Check the related fiber connectors. If the fiber connectors are dirty, clean or replace
them. For details, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the
Supporting Tasks.
b. If the alarm persists, check the fiber jumper. If the fiber jumper endures a large
bending radius or it is damaged or aging, adjust or replace the fiber jumper.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The board that reports the alarm is faulty or the board in the upstream station is
faulty.
a. If the alarm persists, replace the board that reports the alarm or the faulty board in
the upstream station.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
ITU-T G.709
3.28 ODUk_PM_EXC
Description
ODUk PM BIP8 error count exceeding the threshold. This alarm is generated when the BIP8
detection is in poisson mode and bit error count exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Fault Symptom
Table 3-27 lists the fault symptoms for the ODUk_PM_EXC alarm.
The OTU board at the local station may Cause 1: The attenuation of the received
report an IN_PWR_LOW alarm. signals is rather large, and the fiber
transmission line is abnormal.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The attenuation of the received signals is rather large, and the fiber
transmission line is abnormal.
l Cause 2: The transmitter of the OTU board at the opposite station is faulty.
l Cause 3: The receiver of the OTU board at local station is faulty.
Procedure
l Cause 1: The attenuation of the received signals is rather large, and the fiber
transmission line is abnormal.
a. On the U2000, check whether the receive optical power is within the permitted
range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.For details, see "Querying Optical Power
on the U2000" in the Supporting Tasks.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the OTU board.
b. If the receive optical power of the OTU board at the local station is excessively low,
clear the alarm according to the handling procedure of the IN_PWR_LOW alarm.
c. If the alarm persists, check whether the launched optical power at the corresponding
optical port on the upstream board is within the permitted range on the U2000. For
the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the launched optical power of the
OTU board at the upstream station is excessively low, clear the alarm according to
the handling procedure of the OUT_PWR_LOW alarm.
d. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The transmitter of the OTU board at the opposite station is faulty.
a. Apply a hardware loopback between the transmit and receive optical ports on the
WDM side of the OTU board at the upstream station. If the alarm persists, the
transmitter on the OTU board of the opposite station is faulty. Replace the OTU
board.
The board supports pluggable optical Replace the specific pluggable optical
modules, module.
The board does not support pluggable Replace the faulty board. Replace the
optical modules, board.
b. If the alarm persists, see the alarm handling procedure for cause 3.
l Cause 3: The receiver of the OTU board at local station is faulty.
a. If the alarm persists, replace the faulty board at the local station.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709
3.29 ODUk_PM_SSF
Description
Failure of ODUk PM server-layer signals.
Attribute
Parameters
None
Fault Symptom
Table 3-28 lists the fault symptom for the ODUk_PM_SSF alarm.
A station may report the R_LOS or Cause 1: The line in the regeneration span is
OTUk_SSF alarm at the same time. abnormal when there are electrical
regeneration boards.
Cause 4: In the case of a station configured
with tributary boards and line boards, the
line boards report the ODUk_PM_SSF
alarm when the line is abnormal.
A station may report the Cause 2: The station reports an alarm of the
ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn type and the
ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_PM_SSF alarm at the same time.
ODUk_TCMn_LTC, or
ODUk_TCMn_TIM alarm at the same time.
A station may report the OTUk_TIM alarm Cause 3: The station reports the OTUk_TIM
at the same time. or ODUk_PM_AIS alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The line in the regeneration span is abnormal when there are electrical
regeneration boards. As shown in the following figure, when the line in the span from
the OTU1 board at station A to the OTU2 board at station B or in the span from the
OTU3 board at station B to the OTU4 board at station C is abnormal, the OTU4 board at
station C reports the ODUk_PM_SSF alarm.
M M M M
O U OA OA U U U
O O OA OA O
T X/ F F X/ X/ F F X/
T T T
U D I I D D I I D
U U U
1 M U U M M U U M
OA OA 2 3 4
Client WDM U U U OA OA U
side side X X X X WDM Client
side side
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line
boards.
l Cause 2: When Sink Enable Status is Enabled and Source Mode is Operation Mode
for the TCM overheads of the station, the station reports the ODUk_TCMn_SSF,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, or
ODUk_TCMn_TIM alarm and the ODUk_PM_SSF alarm at the same time. The
ODUk_TCMn_LTC alarm is reported only when Enable LTC Response is set to
Enabled. The ODUk_TCMn_TIM alarm is reported only when Enable TIM Response
is set to Enabled.
l Cause 3: The station reports the OTUk_TIM or ODUk_PM_SSF alarm. The OTUk_TIM
alarm is reported only when Enable TIM Response is set to Enabled.
l Cause 4: In the case of a station configured with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm when the line is abnormal.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The line in the regeneration span is abnormal when there are electrical
regeneration boards.
a. According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station, for example, the OTU4
board at station C in the figure.
b. If the OTU4 board is a tributary-line board, check whether the OTU2 board at
station B reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms. Handle these
alarms with precedence, otherwise see the next step.
c. If the OTU4 board consists of a tributary board and a line board, check whether the
line board at station C reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms.
Handle these alarms with precedence, otherwise see the next step.
d. Check whether the OTU2 board at station B reports the R_LOS, OTUk_SSF, and
OTUk_LOF alarms. Handle these alarms with precedence, otherwise see the next
step.
l Cause 2: The station reports an alarm of the ODUk_TCMn type and the ODUk_PM_SSF
alarm at the same time.
a. According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station.
b. Check whether the ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI,
ODUk_TCMn_AIS, ODUk_TCMn_LTC, or the ODUk_TCMn_TIM alarm is
reported at the station. If such an alarm is reported, handle the alarm first. That is,
clear the alarm according to the corresponding method.
c. Check whether the alarm is cleared. If the alarm persists, see cause 3.
l Cause 3: The station reports the OTUk_TIM or ODUk_PM_AIS alarm. The OTUk_TIM
alarm is reported only when Enable TIM Response is set to Enabled.
a. Check whether the OTUk_TIM or ODUk_PM_AIS is reported at the station. If
such an alarm is generated, handle the alarm first. That is, clear the alarm according
to the corresponding method.
b. Check whether the alarm is cleared. If the alarm persists, see cause 4.
l Cause 4: In the case of a station configured with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm when the line is abnormal.
a. Check whether the R_LOS, OTUk_SSF, and OTUk_LOF alarms are reported on
the WDM side of the line board at the station. If yes, handle the alarms with
precedence. That is, clear the alarms according to the corresponding methods. If the
alarm still exists, contact Huawei engineers.
----End
Related Information
Related Cases:
l MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of
ODUk SPRing Protection
l MC-A200 Fiber Faults Result in Service Interruption, The TDX Board Reports
ODU1_PM_SSF Alarms
l MC-A229 Switching Fails Due to Incorrect SNCP Protection Mode on the WDM
Equipment
3.30 OMS_FDI
Description
Forward defect indication at OMS layer. This alarm is generated to suppress the OMS_FDI_P
and OMS_FDI_O alarms when the two alarms coexist. When the board at the OTS layer
detects a signal loss alarm but cannot forward the alarm to the downstream station, it inserts
the OMS_FDI signal. When the downstream station receives the OMS_FDI signal, it reports
the OMS_FDI alarm.
Attribute
Parameters
None
Fault Symptom
Table 3-29 lists the fault symptom for the OMS_FDI alarm.
The board at the opposite station reports an Cause 2: At the upstream station, a fiber cut
OTS_LOS or OTS_TIM alarm. occurs or the optical power is excessively
low. Therefore, the signal loss alarm is
detected at the downstream station, and an
OMS_FDI alarm is then inserted to the
downstream station.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the OMS_FDI alarm are as follows:
l Cause 1: The logical fiber connections are inconsistent with the physical fiber
connections.
l Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively
low. Therefore, the loss of signal alarm is detected at the downstream station, and the
OMS_FDI is then inserted to the downstream station.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The logical fiber connections are inconsistent with the physical fiber
connections.
a. Check whether the logical fiber connection configured for the optical port where the
alarm is generated is consistent with its physical fiber connection. If it is not,
modify the configuration of the logical fiber connection so that the logical fiber
connection is consistent with the physical fiber connection. For details, see
"Checking Logical Fibers".
b. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively
low. Therefore, the signal loss alarm is detected at the downstream station, and then the
OMS_FDI is inserted to the downstream station.
a. Check whether an OTS_LOS or OTS_TIM alarm is generated at the opposite
station and all upstream stations. If it is, troubleshoot the OTS_LOS or OTS_TIM
alarm according to the alarm handling procedure.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.31 OSC_LOS
Description
Loss of input optical power on the OSC. This alarm is generated when the input optical power
of the OSC board exceeds the LOS threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: An optical port on the board that reports the alarm is not connected to a fiber.
l Cause 2: The laser of the board at the opposite station is shut down.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber cut
occurs on the transmission line.
l Cause 4: The transmit part of the opposite station is faulty.
l Cause 5: The receive part of the local station is faulty.
Procedure
l Query the alarm on the U2000 and record the IDs of the optical port and channel where
the alarm is generated.
l Cause 1: An optical port on the board that reports the alarm is not connected to a fiber.
a. Check whether the fiber jumper is connected to the optical port of the board at the
local station. If it is not, connect the fiber jumper.
l Cause 2: The laser of the board at the opposite station is shut down.
a. On the U2000, check whether the laser of the specific board at the opposite station
is turned on. If it is not, open the laser of the board.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber cut
occurs on the transmission line.
a. On the U2000 check whether the receive optical power at the optical port where the
alarm is generated is within the permitted range. For the optical power
----End
Related Information
None.
3.32 OTS_LOS
Description
The OTS_LOS alarm indicates a loss of signal at the OTS layer. When the OTS_LOS_P and
OTS_LOS_O alarms coexist, this alarm is generated. At the same time, the OTS_LOS_P and
OTS_LOS_O alarms are suppressed.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
Cause 1: The OTS_LOS_P and OTS_LOS_O alarms exist at the opposite station.
Procedure
l Check the alarm information on the U2000 and record the IDs of the optical port and
channel where the alarm is generated.
l Cause 1: The OTS_LOS_P and OTS_LOS_O alarms exist at the opposite station.
a. Check whether the logical fiber connections of the FIU are consistent with the
physical fiber connections. If not, modify the configuration of the logical fiber
connections so that logical fiber connections are consistent with the physical fiber
connections.
b. Check and make sure that the fiber connection between the "IN" port on the local
FIU and the opposite station is correct and reliable.
c. If the alarm persists, check whether the attenuation of the "IN" port on the FIU is
excessively high. If yes, adjust the attenuation to a proper value.
d. If the alarm persists, check and make sure that fibers connected to the optical ports
on the FIU are correct and reliable.
----End
Related Information
None.
3.33 OTUk_LOF
Description
The OTUk_LOF is an alarm indicating that the frame alignment signal (FAS) is abnormal.
This alarm occurs when the frame alignment processing is out of frame (OOF) in three
consecutive milliseconds.
Attribute
Parameters
None
Fault Symptom
Table 3-30 lists the fault symptom for the OTUk_LOF alarm.
Two boards at two ends of a single Cause 1: The settings of the service type or
wavelength report the OTUk_LOF alarm in FEC type are incorrect.
the deployment.
A single board at one end reports the Cause 3: The receive optical power or the
OTUk_LOF alarm in the deployment. In OSNR of the local board is abnormal.
addition, the alarm indicating abnormal
optical power is reported.
Multiple boards on the same link report the Cause 6: The dispersion compensation value
OTUk_LOF alarm in the deployment. is excessively great or small.
A single board at one end reports the Cause 2: The board that reports the alarm is
OTUk_LOF alarm in the deployment. faulty.
A board reports the OTUk_LOF alarm Cause 2: The board that reports the alarm is
during normal operation after deployment. faulty.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The settings of the service type or FEC type are incorrect.
l Cause 2: The board that reports the alarm is faulty.
l Cause 3: The receive optical power or the OSNR of the local board is abnormal.
l Cause 4: The signals transmitted by the corresponding board at the opposite end do not
have a frame structure.
l Cause 5: The fiber of the transmission line is abnormal.
l Cause 6: The dispersion compensation value is excessively great or small.
Procedure
l Cause 1: The settings of the service type or FEC type are incorrect.
a. Query the service type or FEC type on the U2000 to check whether the set service
type or FEC type is the same as the service type or FEC type supported by the
board. If the service type or FEC type is different from the service type or FEC type
supported by the board, reset the service type or FEC type to the same as the service
type or FEC type supported by the board.
b. Check whether the alarm is cleared. If the alarm persists, see cause 2.
l Cause 2: The board that reports the alarm is faulty.
a. See Performing Hardware Loopback to perform the relevant operation on the
optical port where the alarm is reported. Then check whether the alarm is cleared.
b. If the alarm persists, replace the board.
c. Check whether the alarm is cleared. If the alarm persists, see cause 5.
l Cause 5: The fiber of the transmission line is abnormal.
a. If the alarm persists, check whether the fiber meets the following requirements:
n The bending radius is not less than 40 mm.
n The optical port connector is well inserted.
n The fiber connector is clean.
n The cable is intact.
If the preceding requirements are not met, clean the fiber connector or replace the
fiber. For details, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the
Supporting Tasks.
b. Check whether the alarm is cleared. If the alarm persists, see cause 6.
----End
Related Information
ITU-T G.709
Related Cases:
l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
l MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with
the SSE1TMR
l MC-A56 LWF Board Reports OTU_LOF Alarm
l MC-A63 MSBBE Bit Errors and OTU_LOF Alarm Occur in a DWDM 10G Network
Due to the Incorrect PMD
l MC-A72 The OTU_LOF Alarm Reported in the LWC1 Due to Wrong Regenerator
Board
l MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption, the WDM Side of the LBE Reports the IN_PWR_HIGH and
OTU_LOF Alarms Abruptly
l MC-A115 Determine Whether the Type and Connections of the DCM Are Proper When
the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD Alarms Are Reported
Discontinuously on the WDM Side of LWF Board
l MC-A147 Services Are Unavailable Due to Inappropriate FEC Configuration on the
40G Regeneration Boards, The System Reports An OTU_LOF Alarm
l MC-A188 The LDGF2 Board on the OptiX OSN 1800 Reports an OTU1_LOF Alarm
l MC-A206 Service Provisioning Fails on an LHP Network, The OTU2_LOF Alarm Is
Reported
l MC-A208 40G Service Provisioning Fails On a Network, The OTU_LOF And
DCM_INSUFF Alarms Are Reported
l MC-A211 OTUk_LOF Alarm Is Reported Due to Mismatched Mapping Modes of the
LSX Boards in the Case of 10GE LAN Services
l MC-A215 Incorrect Configuration of an Added Wavelength During Expansion Results
in Service Interruption of Another Normal Wavelength on an OTU Board, The
Corresponding OTU Board Reports OTU2_LOF Alarm
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
l MC-A236 The OTU Board Transiently Reports the OTU_LOF Alarm Multiple Times
due to Excessively Large System PMD
l MC-A248 Network Services Are Interrupted After the Equipment Restarts Because the
Wavelengths Conflict After the Wavelength Configurations Are Modified
3.34 OTUk_SSF
Description
The OTUk_SSF is an alarm that the signal fails at the OTUk server layer.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 1, 2, 3.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-31 lists the fault symptom for the OTUk_SSF alarm.
A station may report the R_LOS, Cause 1: The station reports the R_LOS
OTUk_SSF alarm at the same time. alarm and the OTUk_SSF alarm at the same
time.
A station may report the OTUk_AIS, Cause 2: The station reports the OTUk_AIS,
OTUk_LOF, or OTUk_LOM alarm at the OTUk_LOF, or OTUk_LOM alarm and the
same time. OTUk_SSF alarm at the same time.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same
time. As shown in the following figure, the client side (the client side accesses the OTU
service) in the receive direction of the OTU1 board at station A or the WDM side in the
receive direction of the OTU2 board at station B reports the R_LOS alarm.
M M
O U OA U
OA O
T X/ F F X/
U D I T
I D
1 M U U
U M
U OA OA 2
Client WDM U
X WDM Client
side side X
side side
Station A Station B
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line
boards.
l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
OTUk_SSF alarm at the same time.
Procedure
l Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same
time.
a. According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station, for example, the OTU1
board at station A or the OTU2 board at station B in the figure.
b. Check whether the R_LOS alarm is reported in the receive direction of the OTU
board at the station. Handle the alarm in advance, otherwise to the next step.
l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
OTUk_SSF alarm at the same time.
a. According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station, for example, the OTU1
board at station A or the OTU2 board at station B in the figure.
b. Check whether the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm is reported in
the receive direction of the OTU board at the station. If the alarm still exists, contact
Huawei engineers.
----End
Related Information
Related Cases:
l MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of
ODUk SPRing Protection
3.35 OUT_PWR_HIGH
Description
Output optical power being too high. This alarm is generated when the laser output optical
power exceeds the upper threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
Cause 1: The optical module of the laser is faulty or the board is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the optical port and
channel where the alarm is generated.
l Cause 1: The optical module of the laser is faulty or the board is faulty.
a. Check whether the board that reports this alarm supports pluggable optical modules.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.36 PORT_MODULE_OFFLINE
Description
Optical module on an optical port being offline. This alarm is generated when the board
detects that an optical module is offline.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The optical module does not exist or is not correctly inserted.
l Cause 2: The optical module or the board is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The optical module does not exist or is not correctly inserted.
a. Check whether the optical port where this alarm is generated has an optical module.
The optical port has no optical Insert an optical module into the optical
module. port properly.
The optical port has an optical See the alarm handling procedure for cause
module. 2.
d. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.37 POWER_FAIL
Description
Power supply failure. This alarm is generated when the power supply of a board becomes
abnormal. For example, there is overvoltage or undervoltage of the power supply, or the
battery on the system control board has no charge.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 state of the power supply in which the alarm is generated. For
example:
0x01 indicates the overvoltage of the 5 V power supply.
0x02 indicates the undervoltage of the 5 V power supply.
0x03 indicates the overvoltage of the -5 V power supply.
0x04 indicates the undervoltage of the -5 V power supply.
0x05 indicates that the voltage of the battery is excessively low or the battery
fails.
0x06 indicates that the 4.8 V power supply is abnormal.
0x3d indicates the undervoltage of the -48 V power supply.
0x3f indicates the undervoltage of the -60 V power supply.
0x3e indicates the overvoltage of the -48 V power supply.
0x40 indicates the overvoltage of the -60 V power supply.
0x53 indicates the undervoltage of the -48 V fan power supply.
0x54 indicates the overvoltage of the -48 V fan power supply.
0x6E indicates no input for the -48 V power supply.
0x6D indicates no output of the 3.3 V power supply.
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic,
handle the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: If this alarm is reported by the system control board, the battery of the system
control and communication board is abnormal (the value of parameter 1 of this alarm is
0x05).
l Cause 2: If this alarm is reported by the PIU board, the input voltage of the subrack is
abnormal because the power supply module is faulty (the value of parameter 1 of this
alarm is 0x3d or 0x3f).
l Cause 3: If this alarm is reported by the PIU or CRPC board, the power supply module
of the board fails or is aging (the value of parameter 1 of this alarm may be any value
except 0x05).
Procedure
l Cause 1: If this alarm is reported by the system control board, the battery of the system
control and communication board is abnormal (the value of alarm parameter 1 is 0x05).
a. On the NMS, back up the NE configuration data to the flash database on the system
control board.
b. Check whether the jumper cap is correctly placed over the battery jumper. If it is,
check the jumper setting of the battery on the system control board. If the setting
disables the battery from providing power, change the setting to ensure that the
battery provides power to the system control board.
c. If the alarm persists, use a multimeter to measure the battery voltage. If the voltage
is lower than 3 V, the battery is out of work. The board must be replaced. Replace
the faulty board.
l Cause 2: If this alarm is reported by the PIU board, the input voltage of the subrack is
abnormal because the power supply module is faulty (the value of parameter 1 of this
alarm is 0x3d or 0x3f).
a. Check whether the switch on the DC power distribution box of the cabinet is ON. If
it is not, turn it to ON.
b. Use a multimeter to check whether the voltage of the external input power supply is
within the permitted range (the permitted range for the voltage of the working
power supply for OptiX optical transmission equipment is -72 V to -40 V). If the
voltage is not within the permitted range, check whether the power supply of the
equipment room is normal.
c. If the voltage of the external input power supply is within the permitted range but
the alarm persists, the power switch on the DC power distribution box may be
faulty. In this case, replace the switch. For details, see "Replacing the Power Switch
on the DC Power Distribution Box".
d. If the alarm persists, the PIU board is faulty. Replacing the PIU Board.
l Cause 3: If this alarm is reported by the PIU or CRPC board, the power supply module
of the board fails or is aging (the value of parameter 1 of this alarm may be any value
except 0x05).
a. Replace the faulty board. For details, see "Replacing the PIU Board" or "Replacing
the Raman Amplifier Board".
----End
Related Information
Related Cases:
l MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER
Alarms
l MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution
l MC-A112 The SCC Housed In the Slave Subrack Reports the POWER_FAIL Alarm
Because the Jumper on the Board Is Set Improperly
l MC-A204 Power Modules on Multiple Boards Report the POWER_FAIL Alarms Due to
Excessively High Temperature
3.38 PUMP_COOL_EXC
Description
Cooling current of the pump laser exceeding the threshold. This alarm is generated when the
laser cooling current is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
Parameter Description
Fault Symptom
Table 3-32 lists the fault symptom for the PUMP_COOL_EXC alarm.
The NE that reports this alarm reports a Cause 1: The ambient temperature of the
temperature alarm or fan fault alarm, such board is excessively high or low.
as TEMP_OVER or FAN_FAIL, within a
certain time.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the PUMP_COOL_EXC alarm are as follows:
Procedure
l Cause 1: The ambient temperature of the board is excessively high or low.
a. Check the ambient temperature of the equipment room, the cleanliness of the air
filter, and heat dissipation of 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. Refer to Replace the board.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None
3.39 R_LOF
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.39.2 R_LOF (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The R_LOF is an alarm indicating that frames are lost on the receive side of the line. This
alarm is reported when the local optical port receives five consecutive frames that do not
contain correct A1 and A2 bytes.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Cause 1: Two boards at different rates are interconnected.
l Cause 2: The transmit cable is faulty, and the fiber connector is loose or contaminated.
l Cause 3: The local receive board is faulty so that the frame structure is lost.
l Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is
lost.
Procedure
Step 1 View the alarm on the NMS and determine the alarm-reporting port according to alarm
parameters.
Step 3 Cause 2: The transmit cable is faulty, and the fiber connector is loose or contaminated.
1. Check whether the output optical power of the peer board is within the normal range. For
details about the optical power indicators for boards, see Product Description. For details
about how to check the output optical power of a board, see the Supporting Tasks.
NOTE
For detailed manufacturing information about an optical module, see the Supporting Tasks or Bar
Code in the Hardware Description.
If... Then...
The output optical power of the peer board is out of range Go to Step 5.
The output optical power of the peer board is within the Go to the next step.
normal range
2. On the NMS, check whether the input optical power of the local board is within the
normal range.
If... Then...
The input optical power of the local board is below the lower Go to the next step.
threshold
The input optical power of the local board is above the upper Go to Step 4.
threshold
3. Check whether the bending radius of the pigtail is within the normal range. If the
bending radius is smaller than 6 cm, re-roll the pigtail. Then, check whether the alarm is
cleared.
4. If the alarm persists, properly connect the pigtail to the optical port on the board. Then,
check whether the alarm is cleared.
5. If the alarm persists, check whether the fiber connector is contaminated. For details, see
the Supporting Tasks. If the fiber connector is contaminated, clean the fiber connector.
For details, see Supporting Tasks.
6. Check whether the optical cable is aged, damaged, or pressed. If yes, replace the optical
cable. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is lost.
1. Perform a hardware loopback on the port that reports the alarm on the local NE. For
details, see the Supporting Tasks.
NOTICE
A loopback interrupts services. Ensure that the optical power is within the normal range
when performing a hardware loopback. You can add an optical attenuator for the receive
optical interface according to the optical power specifications for the board.
If... Then...
The R_LOF alarm persists The local board is faulty. Go to the next step.
2. Replace the optical module if it is pluggable on the board. For details, see the Parts
Replacement. Replace the board if the optical module is unpluggable. For details, see
Parts Replacement.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is lost.
1. Replace the optical module if it is pluggable on the board. For details, see the Parts
Replacement. Replace the board if the optical module is unpluggable. For details, see
Parts Replacement. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the peer cross-connect board. For details, see the Parts
Replacement.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
Description
Loss of frames on the receiving line. This alarm is generated when the frame alignment
processing is out of frame (OOF) in 3 consecutive milliseconds.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-34 lists the fault symptom for the R_LOF alarm.
The upstream board may report an R_LOS Cause 4 (reported from the WDM side)
or R_LOF alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF signal.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The receive optical power or the
OSNR of the local board is abnormal.
l Cause 2 for this alarm generated on the WDM side: The signals transmitted by the
upstream OTU have no SDH frame structure.
l Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
l Cause 4 for this alarm generated on the WDM side: The input signals from the upstream
station contain an R_LOS or R_LOF signal.
l Cause 5 for this alarm generated on the WDM side: The dispersion is under- or over-
compensated.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF alarm signal.
a. If this alarm is reported from the client side of the board, apply a hardware
loopback between the transmit and receive optical ports on the client side of the
board. If this alarm on the board persists, the board is faulty. In this case, see the
alarm handling procedure for cause 2 of this alarm generated on the client side.
NOTICE
Configuring a loopback on the board interrupts the services on the board.
b. If this alarm is cleared, the input signals on the client side contain an R_LOF signal.
In this case, rectify the fault on the client equipment.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
a. Check whether board that reports this alarm supports pluggable optical modules.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
l Cause 1 for this alarm generated on the WDM side/Cause 2 for this alarm generated on
the WDM side: The receive optical power or the OSNR of the local board is abnormal;
the signals transmitted by the upstream OTU have no SDH frame structure.
a. If the WDM side reports this alarm, on the U2000 check whether the client side of
the board at the opposite station reports an R_LOF alarm. If yes, rectify the fault
according to the procedure for handling the R_LOF alarm generated on the client
side.
b. If the alarm persists, on the U2000 check whether the receive optical power at the
WDM-side optical port of the alarm-reporting board is within permitted range. For
the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturing information of the optical
module on the board.
c. If the optical power is abnormal, rectify the fault according the procedure for
handling the IN_PWR_LOW or IN_PWR_HIGH alarm.
d. If the receive optical power is normal, use an SDH meter to receive signals from the
WDM side of the board at the opposite station. Check whether the received signal is
of white spectrum (no signal frame) or has no SDH frame. If the received signal
fails to comply with the requirement, replace the faulty board.
e. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
a. If the alarm persists, the board may be faulty. Replace the faulty board at the local
station.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4 of this alarm generated on the WDM side.
l Cause 4 for this alarm generated on the WDM side: The input signals from the upstream
station contain an R_LOS or R_LOF signal.
a. If the alarm persists, clear the alarm of the equipment at the upstream station.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 5 of this alarm generated on the WDM side.
l Cause 5 for this alarm generated on the WDM side: The dispersion is under- or over-
compensated.
a. If the alarm persists, replace the DCM module.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test
Because the Line Fiber Loss Is Very Large
l MC-A21 An Interconnection Failure between the WDM and SDH Equipment
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS
Alarm on the Board
l MC-A31 Wrong Calculation for Dispersion in One DWDM Project
l MC-A104 No Optical Power Is Output on the WDM Side Due to Incorrect
Configuration,the Board Reports the R_LOF, R_LOC, TP_LOC Alarms
l MC-A115 Determine Whether the Type and Connections of the DCM Are Proper When
the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD Alarms Are Reported
Discontinuously on the WDM Side of LWF Board
l MC-A128 EPL Service Was Interrupted Due To a Service Mode Mismatch of L4G
Boards and Nodes Report R_LOF, ODU5G_PS_AIS, OTU5G_LOF, LINK_ERR Alarm
l MC-A133 In a WDM System with 1:N Optical Channel Protection, the R_LOF Alarm Is
Reported in the Receive Direction on the Client Side When the Laser on the LWC1
Board in the Protection Channel Is Open
l MC-A154 The N2SLQ16 Board Interconnected with the TQS Board Reports an R_LOS
Alarm Because The TQS Board Emits White Lights When the Input Optical Power Is
Normal
l MC-A156 An SDH Board on the SDH Equipment Reports an R_LOF Alarm When the
SDH Board Is Interconnected with a Tributary Board on the OptiX OSN 6800
l MC-A164 Why the WDM-Side Service Rate Reaches 11.1 Gbit/s When the LSX Board
Receives 10GE-LAN Services in Bit Transparent Transmission Mode on the Client Side
l MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper, the OAU Board Reports the MUT_LOS Alarm
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
3.40 R_LOS
Refer to the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 3.40.2 R_LOS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Alarm Severity Alarm Type
Parameters
None.
l The system automatically sends an MS_RDI signal to the upstream NE so that the
upstream NE reports the MS_RDI alarm.
If a data board reports an R_LOS alarm, the Ethernet port enters the link-down state.
If an E-Line service is configured between the Ethernet port and the corresponding
VCTRUNK port, the VCTRUNK port may insert a management frame containing the client
signal fail (CSF) signal to the downstream NE.
Possible Causes
l Cause 1: The local optical port is unused.
l Cause 2: The peer laser is disabled so that no optical signal is input.
l Cause 3: The fiber is cut or the line performance deteriorates.
l Cause 4: The local receive board is faulty so that signals fail to be received.
l Cause 5: The peer transmit board or cross-connect board is faulty so that signals fail to
be transmitted.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the alarm-reporting port.
If... Then...
The optical port is unused or No action is required. To clear the R_LOS alarm,
the specified fiber is not mask the alarm or use a fiber to connect the receive
connected to the optical port and transmit interfaces of the optical port.
NOTE
Masking the R_LOS alarm may trigger other alarms.
NOTICE
Ensure that the receive optical power is within the
specified range when performing a hardware loopback on
the optical port.
Step 3 Cause 2: The peer laser is disabled so that no optical signal is input.
1. Check whether the laser at the peer port is disabled.
If... Then...
The laser is disabled Enable the laser. For details, see the Supporting Tasks. Then,
check whether the alarm is cleared. If the alarm persists, go to
Step 4.
If... Then...
For detailed manufacturing information about an optical module, see the Supporting Tasks or Bar
Code in the Hardware Description.
If... Then...
The output optical power of the peer board is out of range Go to Step 6.
The output optical power of the peer board is within the Go to the next step.
specified range
2. Use a fiber to connect the receive and transmit ports of the local receive board. For
details, see the Supporting Tasks.
NOTICE
A loopback interrupts services. Ensure that the input optical power is within the specified
range when performing a hardware loopback. You can add an optical attenuator at the
receive optical interface of the optical port based on the optical power specifications for
the board.
If... Then...
The R_LOS alarm is Repeat steps Step 4.3 to Step 4.6 to check the pigtails
cleared and fiber connectors on the local and peer NEs.
3. Check whether the radius of the roll into which the pigtail is coiled is less than 6 cm. If
the radius is less than 6 cm, re-roll the pigtail. Then, check whether the alarm is cleared.
4. If the alarm persists, check whether the pigtail is correctly connected to the optical port.
If... Then...
The pigtail is connected Correctly connect the pigtail between the optical boards
incorrectly in the subrack based on site situations. Then, check
whether the alarm is cleared. If the alarm persists, go to
the next step.
If... Then...
5. Ensure that the pigtail is securely connected to the optical port. Then, check whether the
alarm is cleared.
6. If the alarm persists, check whether the fiber connector is contaminated. For details, see
the Supporting Tasks. If the fiber connector is contaminated, clean the fiber connector.
For details, see the Supporting Tasks.
Check whether the alarm is cleared. If the alarm persists, go to the next step.
7. Use an optical time-domain reflectometer (OTDR) to check whether a fiber cut occurs
on the transmission line and to further locate the position of the fiber cut. For details
about how to use an OTDR, see the OTDR operation guide.
If... Then...
A fiber cut occurs on the transmission Replace the optical fiber. Check whether the
line alarm is cleared. If the alarm persists, go to
Step 5.
Step 5 Cause 4: The local receive board is faulty so that signals fail to be received.
1. Replace the optical module if it is pluggable on the alarm-reporting board. For details,
see the Parts Replacement. Replace the alarm-reporting board if the optical module is
unpluggable. For details, see Parts Replacement.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 6.
Step 6 Cause 5: The peer transmit board or cross-connect board is faulty so that signals fail to be
transmitted.
1. Replace the optical module if it is pluggable on the alarm-reporting board. For details,
see the Parts Replacement. Replace the alarm-reporting board if the optical module is
unpluggable. For details, see Parts Replacement. Then, check whether the alarm is
cleared.
2. If the alarm persists, replace the peer cross-connect board. For details, see the Parts
Replacement.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
Description
Loss of signals at the receive end. This alarm is generated when the receive end receives no
signal.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1 (reported from the client side): No fiber jumper is connected to the optical port
on the board of the local station, the fiber jumper connected to the optical port is loose,
or the fiber jumper is connected incorrectly.
l Cause 2 (reported from the client side): The line attenuation is excessively high or a fiber
cut occurs.
l Cause 3 (reported from the client side): The board that reports this alarm is faulty.
l Cause 1 (reported from the WDM side): No fiber jumper is connected to the optical port
on the board of the local station, the fiber jumper connected to the optical port is loose,
or the fiber jumper is connected incorrectly.
l Cause 2 (reported from the WDM side): The line attenuation is excessively high or a
fiber cut occurs.
l Cause 3 (reported from the WDM side): The laser of the board at the opposite station is
shut down.
l Cause 4 (reported from the WDM side): The transmit module of the opposite station or
receive module of the local station is faulty.
Procedure
l On the U2000, check the alarm information and record the IDs of the port and channel
where this alarm is generated.
l Cause 1 (reported from the client side): No fiber jumper is connected to the optical port
on the board of the local station, the fiber jumper connected to the optical port is loose,
or the fiber jumper is connected incorrectly.
a. Check the fiber jumper connection on the board that reports this alarm at the local
station.
No fiber jumper is connected Connect the fiber jumper that is connected to the
to the optical port, upstream board to the optical port.
b. Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers between boards according to
the actual networking environment.
c. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the client side.
l Cause 2 (reported from the client side): The line attenuation is excessively high or there
is a fiber cut.
a. Use a test instrument to test the fiber connection to determine whether a fiber cut
occurs. If a fiber cut occurs, replace the fiber.
b. Check whether this alarm is cleared. If the alarm persists, on the U2000 check
whether the receive optical power of the optical port is within the permitted range.
For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.
The receive optical power is Check the relevant fiber connectors. If the fiber
normal, connectors are dirty, clean or replace the fiber
connectors.
c. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the client side.
l Cause 3 (reported from the client side): The board that reports this alarm is faulty.
a. Apply a hardware loopback between the transmit and receive optical ports on the
client side of the board that reports this alarm. If this alarm persists, the board is
faulty. In this case, replace the board. Replace the board. If this alarm is cleared, the
output power of the client equipment is abnormal. In this case, check for and rectify
the fault on the client equipment.
l Cause 1 (reported from the WDM side): No fiber jumper is connected to the optical port
on the board of the local station, the fiber jumper connected to the optical port is loose,
or the fiber jumper is connected incorrectly.
a. Check the fiber jumper connection on the board that reports this alarm at the local
station.
b. Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers between boards according to
the actual networking environment.
c. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2 of this alarm generated on the WDM side.
l Cause 2 (reported from the WDM side): The line attenuation is excessively high or there
is a fiber cut.
a. On the U2000, check whether the receive optical power at the optical port is within
the permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
The receive optical power Check the relevant fiber connectors. If there is any
is normal, dirt or damage, clean or replace the fiber
connectors.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 (reported from the WDM side): The laser of the board at the opposite station is
shut down.
a. On the U2000, check whether the laser on the board at the opposite station is on. If
not, open the laser.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4 of this alarm generated on the WDM side.
l Cause 4 (reported from the WDM side): The transmit module of the opposite station or
receive module of the local station is faulty.
a. If the alarm persists, check whether the board at the opposite station or the board at
the local station supports pluggable optical modules.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
l MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
The LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
l MC-A14 The LWF Board Reports R_LOS
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS
Alarm on the Board
l MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
l MC-A125 Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case
of a fiber break
l MC-A126 VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm
Even If the Attenuation Is Decreased
l MC-A141 Normal Boards Are Mistakenly Considered Faulty due to Optical Module
Characteristics
l MC-A145 The Client Equipment Interconnected with the TOM Board Reports the
R_LOS Alarm Due to a Problem with the Optical Module on the TOM Board
l MC-A153 It Is Recommended to Enable the Auto-Negotiation Working Mode at a GE
Port When the LPT Function Is Enabled, Or The Services Are Interrupted And The
System Reports The R_LOS Alarms
l MC-A154 The N2SLQ16 Board Interconnected with the TQS Board Reports an R_LOS
Alarm Because The TQS Board Emits White Lights When the Input Optical Power Is
Normal
l MC-A156 An SDH Board on the SDH Equipment Reports an R_LOF Alarm When the
SDH Board Is Interconnected with a Tributary Board on the OptiX OSN 6800
l MC-A159 Services Are Interrupted After the Protection Hold-Off Time Is Set to 10s
During Configuration of Client-Side 1+1 Protection on the OptiX OSN 6800, The
System Reports The R_LOS Alarm
l MC-A164 Why the WDM-Side Service Rate Reaches 11.1 Gbit/s When the LSX Board
Receives 10GE-LAN Services in Bit Transparent Transmission Mode on the Client Side
l MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper, the OAU Board Reports the MUT_LOS Alarm
l MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board
Causes Low Receive Optical Power, The Connected OAU Board At The Downstream
Station Reports MUT_LOS And R_LOS Alarms
l MC-A243 The TN52TOM Board Reports the R_LOS Alarm When Light Is Received
l MC-A252 Switching of ODUk SNCP Protection Fails
l MC-A282 R_LOS Is Reported by a Line Board on a Regular Basis Because of Incorrect
Wavelength Monitoring Configuration on the Electrical Regeneration NE (NG WDM
Equipment)
3.41 R_OOF
Description
Out of frames on the receiving line. This alarm is generated when the heads of five
consecutive frames fail to be detected.
Attribute
Parameters
None
Fault Symptom
Table 3-36 lists the fault symptoms for the R_OOF alarm.
The board that reports this alarm also report Cause 1 (reported from the WDM side)
an IN_PWR_LOW alarm.
The board that reports this alarm also Cause 2 (reported from the WDM side)
reports bit error alarms, such as B1_EXC
alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 for this alarm generated on the client side: The input signals on the client side
are abnormal and therefore an R_OOF alarm is generated.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The attenuation of the received
signals is excessively high.
l Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
l Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite
station is faulty.
l Cause 4 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1 for this alarm generated on the client side: The input signals on the client side
are abnormal and therefore an R_OOF alarm is generated.
a. If this alarm is reported from the client side of the board, apply a hardware
loopback between the transmit and receive optical ports on the client side of the
board. If this alarm on the board persists, the board is faulty. In this case, see the
alarm handling procedure for cause 2 of this alarm generated on the client side.
NOTICE
Performing a loopback on the board interrupts the services on the board.
b. If the alarm is cleared, the input signals on the client side contain R_OOF signals.
In this case, rectify the fault on the client equipment.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
a. If the alarm persists, replace the faulty board.
l Cause 1 for this alarm generated on the WDM side: The attenuation of the received
signals is excessively high.
a. If the client side reports this alarm, check whether the receive optical power of the
port is within the permitted range on the U2000. For the optical power
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the board.
b. If the receive optical power is not within the permitted range, see the procedure for
handling the IN_PWR_LOW alarm to rectify the fault.
c. If the receive optical power is within the permitted range, see the alarm handling
procedure for cause 2 of this alarm generated on the WDM side.
l Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
a. Check whether there are bit error alarms. If there are bit error alarms, clear the
alarms first according to the proper handling procedure.
b. If there is no bit error alarm and the receive optical power is normal, check the fiber
connector. If the fiber connector is dirty or damaged, clean or replace the fiber
connector.
c. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
l Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite
station is faulty.
a. On the U2000, check whether the transmit optical power at the corresponding
optical port on the opposite OTU is within the permitted range. For the optical
power specifications of the specific board, see "Technical Specifications" in the
Product Description. For details, see "Querying Optical Power on the U2000" in the
Supporting Tasks.
b. If the transmit optical power exceeds the permitted range, the opposite board is
faulty. Replace the faulty board.
c. If the transmit optical power is within the permitted range, see the alarm handling
procedure for cause 4 of this alarm generated on the WDM side.
l Cause 4 for this alarm generated on the WDM side: 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
assistance.
----End
Related Information
Related Cases:
l MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test
Because the Line Fiber Loss Is Very Large
l MC-A115 Determine Whether the Type and Connections of the DCM Are Proper When
the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD Alarms Are Reported
Discontinuously on the WDM Side of LWF Board
l MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
3.42 R_SLIP
Description
Frame slipping on the receive side. The alarm is generated when the phase deviation occurs in
the received service frames of the OSC board.
Attribute
Parameters
None
Fault Symptom
Table 3-37 lists the fault symptom for the R_SLIP alarm.
The board that reports this alarm also report Cause 2: The optical line attenuation is
an IN_PWR_HIGH or IN_PWR_LOW excessively high or the receive optical
alarm. power is excessively high.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The clock configuration is wrong or the clock signals are not synchronous.
l Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
l Cause 3: The fibers at the eastward and westward optical ports on the OSC board are
connected reversely.
l Cause 4: The board that reports this alarm is faulty.
Procedure
l Cause 1: The clock configuration is incorrect or the clock signals are not synchronous.
a. Check whether the clock configuration is correct. If it is not, reconfigure it to ensure
that the clocks of the total network are synchronous. For details on how to configure
the clock information, see Physical Clock (OCS) and Physical Clock (Packet).
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
a. On the U2000, check whether the receive optical power at the optical port is within
the permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
The receive optical power Check the fiber jumper or the fiber connector. If the
is excessively low, fiber jumper or fiber connector is dirty, clean the
fiber connector or replace the fiber jumper.
The receive optical power Adjust the optical attenuator to ensure that the
is excessively high, receive optical power is within the permitted range.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The fibers at the eastward and westward optical ports on the OSC board are
connected reversely. For example, the fibers for connecting to the TM1 optical port in
the west and the TM2 optical port in the east are connected reversely. See the following
figure.
a. If the alarm persists, check the engineering fiber connection diagram to see whether
the fibers at the eastward and the westward optical ports on the OSC board are
connected reversely. If the fiber connection is incorrect, correct it according to the
diagram.
OA
F RM1 TM2 F
I SC2 I
U TM1 RM2 U
OA
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The board that reports this alarm is faulty.
a. If the alarm persists, perform a cold reset on the faulty board on the U2000.
b. If the alarm persists, replace the faulty board.
c. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the
OSC Board
3.43 REM_SF
Description
Remote signal failure alarm indication. This alarm is generated when the client side of the
board at the opposite station fails to receive signals (for example, when there is an R_LOS or
R_LOF alarm).
Attribute
Parameters
None
Fault Symptom
Table 3-38 lists the fault symptom for the REM_SF alarm.
The OTU board at the opposite station Cause 1: An R_LOS, R_LOF, R_LOC,
reports an R_LOS, R_LOF, R_LOC, LINK_ERR, L_SYNC, or a
LINK_ERR, L_SYNC, or a LOCAL_FAULT alarm is generated on the
LOCAL_FAULT alarm. client side of the OTU at the opposite
station.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: An R_LOS, R_LOF, R_LOC , LINK_ERR, L_SYNC, or a LOCAL_FAULT
alarm is generated on the client side of the OTU board at the opposite station.
l Cause 2: The client side of the OTU board at the opposite station is faulty.
Procedure
l Cause 1: An R_LOS, R_LOF, R_LOC , LINK_ERR, L_SYNC, or a LOCAL_FAULT
alarm is generated on the client side of the OTU board at the opposite station.
a. On the U2000, check whether an R_LOS, R_LOF, R_LOC, LINK_ERR, L_SYNC
or LOCAL_FAULT alarm is generated on the client side of the OTU board at the
opposite station. If it is, clear the alarm.
l Cause 2: The client side of the OTU board at the opposite station is faulty.
a. Replace the OTU board at the opposite station.
b. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.44 REMOTE_FAULT
Description
Fault at the remote end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
Table 3-39 lists the fault symptom for the REMOTE_FAULT alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The LOCAL_FAULT alarm is reported at the opposite station when 10GE LAN
(BIT transparent transmission) services are received.
See the following figure.
The client side of the OTU board at station A detects a LOCAL_FAULT alarm, and the
client side of the OTU board at station B reports a REMOTE_FAULT alarm.
O O
Client WDM WDM Client
router side
T
side side
T
side
router
U U
Station A Station B
Detects and reports a fault Detects and reports the
at the remote end alarm REMOTE_FAULT alarm
Procedure
l Cause 1: The LOCAL_FAULT alarm is reported at the opposite station when 10GE LAN
(BIT transparent transmission) services are received.
a. Check whether the LOCAL_FAULT alarm is reported at the opposite station. If it
is, clear the LOCAL_FAULT alarm at the opposite station.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The data equipment on the client side is malfunctioning.
a. Rectify the fault on the data equipment.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.45 SECU_ALM
Description
Invalid access. This alarm is generated when a user fails to log in again after four consecutive
login failures.
Attribute
Parameters
None.
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: Authorized login. For example, the password is incorrect.
Procedure
l Cause 1: Authorized login. For example, the password is incorrect.
a. Verify that the user name and password are correct. If they are incorrect, use the
correct ones to log in again.
b. If the alarm persists after invalid users are cleared, reset the board or remove or
reinsert the board. If the alarm persists, replace the board.
----End
Related Information
None.
3.46 SUBRACK_ID_CONFLICT
Description
Conflict of subrack IDs. In the case of the master-slave subrack mode, this alarm is generated
when the master subrack detects that the DIP switch settings of the slave subracks are
repeated.
Attribute
Alarm Severity Alarm Type
Parameters
Parameter Description
Fault Symptom
Table 3-40 lists the fault symptom for the SUBRACK_ID_CONFLICT alarm.
The board may report the BD_STATUS, l Cause 1: In the case of the master-slave
COMMUN_FAIL, and WRG_BD_TYPE subrack mode, multiple master subracks
alarms at the same time. exist in the system.
l Cause 2: In the case of the master-slave
subrack mode, the DIP switch settings of
two slave subracks are repeated.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the SUBRACK_ID_CONFLICT alarm are as follows:
l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two
slave subracks are repeated.
Procedure
l Perform all the following steps regardless of whether the SUBRACK_ID_CONFLICT
alarm is cleared during the operations.
l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
a. There should be only one master subrack in the system. Identify the redundant
master subracks according to the actual networking and then remove them.
b. Perform a warm reset on the system control board in the master subrack.
c. Perform a warm reset on all boards on the NE.
d. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two
slave subracks are repeated.
a. Disconnect one slave subrack from the master subrack and reset the ID of this slave
subrack by changing the DIP switch setting on the system control board. In this
case, the IDs of the two slave subracks are different.
b. Perform a warm reset on the system control board in the master subrack on the NE.
c. After the subrack ID is changed, perform a warm reset on all the boards in the
subrack.
d. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
3.47 SUM_INPWR_LOW
Description
Input optical power of multiplexed wavelengths is excessively low. This alarm is generated
when the input optical power of multiplexed signals is lower than the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Fault Symptom
Table 3-41 lists the fault symptom for the SUM_INPWR_LOW alarm.
The upstream board reports an Cause 1: The output optical power of the
OUT_PWR_LOW alarm. upstream station decreases. Therefore, the
input optical power of the local station is
excessively low.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The output optical power of the upstream station decreases. 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, fiber
connectors, or optical attenuators are dirty.
l Cause 3: The board that reports this alarm is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The output optical power of the upstream station decreases. Therefore, the input
optical power of the local station is excessively low.
a. On the U2000, check the output optical power of the boards at the upstream station
along the reverse direction of the signal flow. If the output optical power of a
certain board is excessively low, adjust the output optical power of the board to a
value within the permitted range.
b. If the alarm persists, replace the board whose output optical power is excessively
low. Replace the board.
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, fiber
connectors, or optical attenuators 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 port on the board that reports this alarm. If it is, 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 it is, adjust the attenuation of the VOA to a
proper value.
c. If the alarm persists, check whether related fibers, fiber connectors, or optical
attenuators are dirty. If they are, replace the fiber jumpers or check and clean the
fiber connectors.
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
assistance.
----End
Related Information
None.
3.48 SWDL_NEPKGCHECK
Description
Loss of files. This alarm is generated when the NE software checks the software package and
finds that a file in a partition of the system control board software package is lost and the file
cannot be restored from the related file in another partition. This alarm clears when the NE
software checks the software package and finds the file during next preventive maintenance.
NOTE
The system control board checks the software package each time when the system control board starts up and
when the periodical check is performed. The periodical check is performed every hour by default.
Attribute
Parameters
None
Fault Symptom
Table 3-42 lists the fault symptom for the SWDL_NEPKGCHECK alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1: The same file in two partitions in the software package of the system control
board is lost and cannot be restored.
l Cause 2: A file in a partition in the software package of the system control board is lost
and the file cannot be restored from the associated file in another partition.
Procedure
l Causes 1 and 2: The same file in two partitions in the software package of the system
control board is lost and cannot be restored. A file in a partition in the software package
of the system control board is lost and the file cannot be restored from the associated file
in another partition.
a. On the U2000, select the software package of the same version to perform package
loading.
b. After the package is successfully loaded, the alarm clears. If the alarm persists,
contact Huawei for assistance.
----End
Related Information
None
3.49 TD
Description
Transmitter being degraded. The TD alarm threshold of the laser is set to a value 1.2 times of
the initial value of the bias current. The TD alarm is generated when the bias current of the
laser exceeds the threshold and is smaller than the initial value by 1.5 times.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
Cause 1: The laser is aging.
Procedure
l Cause 1: The laser is aging.
a. Check whether board that reports this alarm supports pluggable optical modules.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The detection circuit of the board is faulty.
a. Replace the faulty board. Refer to Replace the board.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
In a cooled optical module that adopts the automatic level control (ALC) function, the laser is
aged after long-term operation and the laser emitting efficiency decreases. To ensure constant
output optical power, the laser bias current, an index that reflects the laser aging degree, needs
to be increased.
3.50 TEMP_OVER
Description
Working temperature crossing the threshold. This alarm is generated when the system detects
that the board working temperature is higher than the upper threshold or lower than the lower
threshold.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Fault Symptom
Table 3-43 lists the fault symptom for the TEMP_OVER alarm.
On the NMS, the adjusting mode of the fan Cause 1: The set rotating speed of the fan
board is set to Adjustable Speed Mode and board is excessively low.
the rotating speed is set to Low Speed or
Medium Speed.
The fan board reports the FAN_FAIL or Cause 2: The fan board is faulty.
FAN_FAULT alarm.
The adjusting mode of the fan board is set to Cause 3: The air filter is excessively dusty.
Auto Speed Mode and the rotating speed is
set to High Speed. In addition, no other
alarms are generated.
The fan board reports the BD_STATUS Cause 5: The fan is not in position.
alarm.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the TEMP_OVER alarm are as follows:
l Cause 1: The set rotating speed of the fan board is excessively low.
l Cause 2: The fan board is faulty.
l Cause 3: The air filter is excessively dusty.
l Cause 4: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
l Cause 5: The fan is not in position.
l Cause 6: The board that reports the alarm is faulty.
Procedure
l Query the alarm parameter on the U2000. If the parameter indicates the upper threshold
is exceeded, handle the alarm according to causes 1 to 6. If the parameter indicates the
lower threshold is exceeded, handle the alarm according to causes 3 and 5.
l Cause 1: The set rotating speed of the fan board is excessively low.
a. Check the adjusting mode and rotating speed of the fan board on the U2000. If the
adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or
Medium Speed, change the rotating speed to High Speed or the adjusting mode to
Auto Speed Mode.
b. Check whether the alarm is cleared. If the alarm persists, see cause 2.
l Cause 2: The fan board is faulty.
a. If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is
generated on the fan board. If it is, handle the alarm immediately.
b. Check whether the alarm is cleared. If the alarm persists, see cause 3.
l Cause 3: The air filter is excessively dusty.
a. If the alarm persists, check whether the air filter is excessively dusty, causing the
problem of heat dissipation. You can feel the wind and the temperature of the wind
at the air exhaust vent.
b. If the problem is caused by dusty the air filter, remove and clean the air filter.
c. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
l Cause 4: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
a. Check whether the ambient temperature of the equipment room is higher than 45°C
or lower than 0°C. If the temperature is higher than 45°C or lower than 0°C, use a
cooler or heater to decrease or increase the ambient temperature.
NOTE
The TEMP_OVER alarm is cleared when the board temperature is 5°C lower than the upper
threshold or 5°C higher than the lower threshold so that intermittent TEMP_OVER alarms
can be prevented.
b. Check whether the alarm is cleared. If the alarm persists, see cause 5.
l Cause 5: The fan is not in position.
a. Check whether the NE reports the BD_STATUS alarm or check whether the fan is
in position on the U2000. If the fan is not in position, place it firmly.
b. Check whether the alarm is cleared. If the alarm persists, see cause 6.
l Cause 6: The board that reports the alarm is faulty.
a. Replace the board that reports the alarm. Refer to Replace the board.
l If the alarm persists, query the current working temperature of the board reporting the
alarm. If the temperature is in the permitted range, adjust the threshold for the working
temperature of the board based on the actual equipment room environment. Select the
desired board on the NE Explorer. In the navigation tree, choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface. On the
Temperature Attributes tab, set Temperature Upper Threshold (DEG.C) or
Temperature Lower Threshold (DEG.C).
NOTE
The preceding method can be used only to temporarily clear the TEMP_OVER alarm. Exercise
caution when using this method because the device lifespan may be affected if the method is used
for a long period of time.
----End
Related Information
Related Cases:
l MC-A134 How to Resolve The Problem of The OptiX BWS 1600G Subrack Reports
The TEMP_OVER Alarm
l MC-A146 The TN11LOM Board Intermittently Reports the TEMP_OVER Alarm
l MC-A225 Services on Boards Are Interrupted And The Boards Report The
HARD_BAD Alarm Due to Dusty Air Filters
3.51 TF
Description
Transmission failure. This alarm is generated when the transmit optical power of the laser
exceeds the threshold of the output optical power of the laser.
Attribute
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible causes of the TF alarm are as follows:
Cause 1: The laser module is damaged, or the laser is aging.
Cause 2: The detection circuit of the board is faulty.
Procedure
l Cause 1: The laser module is damaged, or the laser is aging.
a. Perform a cold reset on the faulty board on the U2000.
b. Check whether the board that reports this alarm supports pluggable optical modules.
c. Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The detection circuit of the board is faulty.
a. If the alarm persists, the board that reports the alarm may be faulty. Replace the
faulty board. Refer to Replace the board.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after a
long-term operation and therefore the laser emitting efficiency decreases. To ensure constant
output optical power, the laser bias current needs to be increased. Therefore, the bias current
is an index that reflects the aging degree of the laser.
Related Cases:
l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
l MC-A12 Certain Boards Report the TF Alarm Transiently
3.52 TS_CFG_MISMATCH
Description
Timeslot mismatch. This alarm is generated when the configured timeslot of one board at the
local station is inconsistent with the timeslot transmitted from the opposite station.
Attribute
Alarm Severity Alarm Type
Major Processing
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with the
received timeslot.
Procedure
l Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with
the received timeslot.
a. Check whether the value of Timeslot Configuration Mode of the board that
reports this alarm is the same as the value of Timeslot Configuration Mode of the
corresponding board at the opposite station. If it is not, set them to Automatic. For
details on how to configure the service timeslots, see "Configuring Service
Timeslots" in the Configuration Guide.
b. If the mode is consistent, check whether the timeslot configuration at the transmit
end of the opposite board is consistent with the timeslot configuration at the receive
end of the local board. If it is not, modify the timeslot configuration of the opposite
board or the local board according to the actual service.
c. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.53 WRG_BD_TYPE
Description
Incorrect board type. This alarm is generated when the logical board and the physical board
are inconsistent.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
None.
Possible Causes
The possible causes of the WRG_BD_TYPE alarm are as follows:
l Cause 1: The type of the logical board configured on the U2000 is different from the
type of the physical board installed in the slot.
l Cause 2: The board that reports this alarm is faulty.
Procedure
l Cause 1: The type of the logical board configured on the U2000 is different from the
type of the physical board installed in the slot.
a. On the U2000, check whether the type of the logical board is the same as the type
of the physical board installed in the corresponding slot. If it is not, determine
whether the type of logical board or the type of the physical board is inappropriate
according to the engineering configuration requirements.
n If the type of the logical board is inappropriate, reconfigure the logical board
on the U2000.
n If the type of the physical board is inappropriate, remove the existing board
and insert a board of the correct type.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 2.
l Cause 2: The board that reports this alarm is faulty.
a. Replace the board.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
4 Clearing Alarms
This topic describes information related to alarm handling, including alarm descriptions,
alarm parameters, impact of alarms on the system, alarm causes, and alarm handling
procedures.
NOTE
By default, optical-layer alarms (OTS, OMS, and OCH alarms) are not reported. You can enable optical-
layer alarm reporting as required using the NMS. For details, see "Enabling/Disabling Supervision on
the Optical Layer" in the Supporting Tasks.
NOTE
If the fault of an alarm cannot be located, contact Huawei engineers for troubleshooting.
The alarm handling involves board resets (either cold or warm). Warm and cold resets have
different impact on services.
l Reset of the system control board: A warm reset of the system control is a restart of the
upper-layer software, which neither updates the FPGA or hardware data nor interrupts
services. A cold reset of the system control may result in reconfiguration of the key
hardware, such as FPGA reloading, and the upper-layer software need to be restarted.
l Reset of other boards: A warm reset on other boards does not affect running services
while a cold reset on other boards does. A mis-reset of such a board affects the
communication between this board and the system control and even interrupts services.
The handling measures of certain alarms in this topic vary according to the boards that report
these alarms, and therefore the handling measures of these alarms are described according to
the systems (OCS and OTN systems) that the boards belong to.
4.1 AD_CHECK_FAIL
4.2 ALC_ADJUST_FAIL
4.3 ALC_WAIT_ADJUST
4.4 ALM_ALS
4.5 ALM_GFP_dCSF
4.6 ALM_GFP_dLFD
4.7 ALM_HANGUP
4.8 ALS_ACTIVE
4.9 ALS_TRIGGERED
4.10 APE_ADJUST_FAIL
4.11 APE_ADJUST_PEND
4.12 APS_FAIL
4.13 APS_INDI
4.14 APS_MANUAL_STOP
4.15 ARP_FAIL
4.16 ARP_SPOOF
4.17 ASE_NOT_CALIBRATE
4.18 AU_AIS
4.19 AU_LOP
4.20 B1_SD
See the alarm page according to the type of the board that reports the alarm.
4.21 B2_EXC
4.22 B2_SD
4.23 B3_EXC
4.24 B3_EXC_VC3
4.25 B3_EXC_VC4
4.26 B3_SD
4.27 B3_SD_VC3
4.28 B3_SD_VC4
4.29 BD_BPXC_MISMATCH
4.30 BD_LEDTEST
4.31 BD_NOT_INSTALLED
4.32 BD_STATUS
See the alarm page according to the type of the board that reports the alarm.
4.33 BDID_ERROR
4.34 BIOS_STATUS
4.35 BWUTILIZATION_OVER
4.36 C2_VCAIS
4.37 CFCARD_FAILED
4.38 CFG_DATACHECK_FAIL
4.39 CFG_DATASAVE_FAIL
4.40 CFP_LOS
4.41 CHAN_ADD
4.42 CHIP_ABN
4.43 CLIENT_PORT_STA_INDI
4.44 CLIENT_PROT_NOTSTART
4.45 CLK_LOCK_FAIL
4.46 CLK_NO_TRACE_MODE
4.47 COM_EXTECC_FULL
4.48 CRC4_CROSSTR
4.49 DB_RESTORE_FAIL
4.50 DBMS_DELETE
4.51 DBMS_ERROR
4.52 DBMS_PROTECT_MODE
4.53 DBPS_ABNORMAL
4.54 DCM_INSUFF
4.55 DCNLINK_OVER
4.56 DCNSIZE_OVER
4.57 DERIVED_PWR_ERROR
4.58 DLAG_PROTECT_FAIL
4.59 DSP_LOAD_FAIL
4.60 EFI_TYPE_MISMATCH
4.61 ELAN_SMAC_FLAPPING
4.62 ERPS_IN_PROTECTION
4.63 ETH_APS_LOST
4.64 ETH_APS_PATH_MISMATCH
4.65 ETH_APS_SWITCH_FAIL
4.66 ETH_APS_TYPE_MISMATCH
4.67 ETH_BIP8_SD
4.68 ETH_CFM_AIS
4.69 ETH_CFM_LOC
4.70 ETH_CFM_MACSTATUS
4.71 ETH_CFM_MISMERGE
4.72 ETH_CFM_RDI
4.73 ETH_CFM_UNEXPERI
4.74 ETH_EFM_DF
4.75 ETH_EFM_EVENT
4.76 ETH_EFM_LOOPBACK
4.77 ETH_EFM_REMFAULT
4.78 ETH_HI_BER
4.79 ETH_LINK_DOWN
4.80 ETH_LOS
4.81 ETH_MISCONNECT
4.82 ETH_NO_FLOW
4.83 ETH_SERVICE_CONFIG_FAIL
4.84 ETHOAM_DISCOVER_FAIL
4.85 ETHOAM_RMT_CRIT_FAULT
4.86 ETHOAM_RMT_LOOP
4.87 ETHOAM_RMT_SD
4.88 ETHOAM_SELF_LOOP
4.89 ETHOAM_VCG_SELF_LOOP
4.90 EX_ETHOAM_MPID_CNFLCT
4.91 EXT_MODULE_OFFLINE
4.92 EXT_SYNC_LOS
4.93 EXT_TIME_LOC
4.94 FAN_FAIL
4.95 FAN_FAULT
4.96 FC_8B10BERR_OVER
4.97 FC_AIS
4.98 FCS_ERR
4.99 FDBSIZEALM_ELAN
4.100 FEATURE_WITHOUT_LICENSE
4.101 FEC_LOF
4.102 FEC_OOF
4.103 FIBERTYPE_MIS
4.104 FLOW_OVER
4.105 FOP_NR
4.106 FOP_PM
4.107 FOP_PR
4.108 FPGA_ABN
4.109 FSELECT_STG
4.110 FWD_PKT_LOSS
4.111 GAINDATA_MIS
4.112 GFP_UPM
4.113 HARD_BAD
4.114 HARD_ERR
4.115 HARD_NONSUPPORT
4.116 HP_LOM
4.117 HP_RDI
4.118 HP_REI
4.119 HP_SLM
4.120 HP_TIM
4.121 HP_UNEQ
4.122 HSC_UNAVAIL
4.123 IGSP_ENTRIES_EXC
4.124 IN_PWR_ABN
4.125 INNER_COMMUN_MISCON
4.126 INSERTION_LOSS_HIGH
4.127 INTRA_OTU_STA_INDI
4.128 IPA_FAULT
4.129 IPA_SHUT
4.130 J0_MM
4.131 K1_K2_M
4.132 K2_M
4.133 L_SYNC
4.134 LAG_DOWN
4.135 LAG_MEMBER_DOWN
4.136 LAG_PORT_FAIL
4.137 LAG_VC_PORT_FAIL
4.138 LAN_LOC
4.139 LASER_HAZARD_WARNING
4.140 LASER_MOD_ERR
4.141 LASER_OPEN_FAIL
4.142 LASER_SHUT
4.143 LASER_PARA_ERR
4.144 LASER_TYPE_MISMATCH
4.145 LCAS_FOPR
4.146 LCAS_FOPT
4.147 LCAS_PLCR
4.148 LCAS_PLCT
4.149 LCAS_TLCR
4.150 LCAS_TLCT
4.151 LCS_DAYS_OF_GRACE
4.152 LCS_EXPIRED
4.153 LCS_FILE_NOT_EXIST
4.154 LCS_SHORTAGE_SHELF
4.155 LOCAL_FAULT
4.156 LOCK_CUR_FAIL
4.157 LOCKPOW_MIS
4.158 LOL
4.159 LP_RDI_VC3
4.160 LP_SLM_VC3
4.161 LP_UNEQ_VC3
4.162 LPT_CFG_CLOSEPORT
4.163 LPT_RFI
4.164 LSR_BCM_ALM
4.165 LSR_COOL_ALM
4.166 LSR_INVALID
4.167 LSR_NO_FITED
4.168 LSR_KEY_UNLOCK
4.169 LTI
4.170 MAC_FCS_EXC
4.171 MAINBD_SUBBD_MISMATCH
4.172 MCLAG_CFG_MISMATCH
4.173 MCSP_PATH_LOCV
4.174 MOD_COM_FAIL
4.175 MCS_SWITCH_BLOCKED
4.176 MODULE_ADJUST_FAIL
4.177 MODULE_COOLCUR_OVER
4.178 MODULE_RATE_MISMATCH
4.179 MODULE_TEMP_OVER
4.180 MODULEFILE_UPDATE_FAIL
4.181 MPLS_PW_AIS
4.182 MPLS_PW_LOCV
4.183 MPLS_PW_OAMFAIL
4.184 MPLS_PW_RDI
4.185 MPLS_PW_SD
4.186 MPLS_PW_SF
4.187 MPLS_PW_UNEXPMEG
4.188 MPLS_PW_UNEXPMEP
4.189 MPLS_PW_UNEXPPER
4.190 MPLS_TUNNEL_AIS
4.191 MPLS_TUNNEL_LOCV
4.192 MPLS_TUNNEL_OAMFAIL
4.193 MPLS_TUNNEL_RDI
4.194 MPLS_TUNNEL_SD
4.195 MPLS_TUNNEL_SF
4.196 MPLS_TUNNEL_UNEXPMEG
4.197 MPLS_TUNNEL_UNEXPMEP
4.198 MPLS_TUNNEL_UNEXPPER
4.199 MS_APS_INDI_EX
4.200 MS_CROSSTR
4.201 MS_REI
4.202 MS_SNCP_PS
4.203 MS_SNCP_STA_INDI
4.204 MULTI_RPL_OWNER
4.205 MUT_TLOS
4.206 NEBD_XC_DIF
4.207 NESF_LOST
4.208 NESTATE_INSTALL
4.209 NO_BD_PARA
4.210 NO_BD_SOFT
4.211 NO_ELABEL
4.212 NODEID_MM
4.213 NTP_SYNC_FAIL
4.214 NULL_SEND
4.215 OA_HIGH_GAIN
4.216 OA_OUT_PWR_ABN
4.217 OCH_FDI
4.218 OCH_FDI_O
4.219 OCH_FDI_P
4.220 OCH_LOS_P
4.221 OCH_OCI
4.222 OCH_SSF
4.223 OCH_SSF_O
4.224 OCH_SSF_P
4.225 ODU_AIS
4.226 ODU_LCK
4.227 ODU_OCI
4.228 ODU_SNCP_STA_INDI
4.229 ODUk_LOFLOM
4.230 ODUk_PM_LCK
4.231 ODUk_PM_OCI
4.232 ODUk_PM_TIM
4.233 ODUk_TCMn_AIS
4.234 ODUk_TCMn_BDI
4.235 ODUk_TCMn_DEG
4.236 ODUk_TCMn_EXC
4.237 ODUk_TCMn_LCK
4.238 ODUk_TCMn_LTC
4.239 ODUk_TCMn_OCI
4.240 ODUk_TCMn_SSF
4.241 ODUk_TCMn_TIM
4.242 ODUKSP_PS
4.243 ODUKSP_STA_INDI
4.244 OH_LOOP
4.245 OLP_PS
4.246 OLP_STA_INDI
4.247 OMS_BDI
4.248 OMS_BDI_O
4.249 OMS_BDI_P
4.250 OMS_FDI_O
4.251 OMS_FDI_P
4.252 OMS_LOS_P
4.253 OMS_LOSS_ACCUM_ABN
4.254 OMS_LOSS_MON_FAIL
4.255 OMS_PMI
4.256 OMS_PWR_ADJ_FAIL
4.257 OMS_SSF
4.258 OMS_SSF_O
4.259 OMS_SSF_P
4.260 ONE_PUMP_WORK
4.261 OOL
4.262 OOS_LOST
4.263 OPA_FAIL_INDI
4.264 OPU1_VCAT_SQM
4.265 OPU1_VCAT_VcPLM
4.266 OPU4_LOOMFI
4.267 OPUk_CSF
4.268 OPUk_MSIM
4.269 OPUk_PLM
4.270 ORP_CRITICAL_HI
4.271 OSC_CLK_MISMATCH
4.272 OSC_BDI
4.273 OSC_DEG
4.274 OSC_RDI
4.275 OSNR_LOSS_UNBALANCED
4.276 OTS_BDI
4.277 OTS_BDI_O
4.278 OTS_BDI_P
4.279 OTS_LOS_O
4.280 OTS_LOS_P
4.281 OTS_PMI
4.282 OTS_TIM
4.283 OTU_AIS
4.284 OTU_LOF
4.285 OTU_LOM
4.286 OTUk_AIS
4.287 OTUk_BDI
4.288 OTUk_DEG
4.289 OTUk_EXC
4.290 OTUk_LOM
4.291 OTUk_TIM
4.292 OUT_PWR_ABN
4.293 OUT_PWR_LOW
4.294 OWSP_PS
4.295 OWSP_STA_INDI
4.296 PASSWORD_NEED_CHANGE
4.297 PATCH_ACT_TIMEOUT
4.298 PATCH_BD_EXCLUDE
4.299 PATCH_BD_MATCH_FAIL
4.300 PATCH_CHGSCC_NOTMATCH
4.301 PATCH_DEACT_TIMEOUT
4.302 PATCH_PKGERR
4.303 PID_AUTO_ADJUST_FAIL
4.304 PM_BDI
4.305 PM_BEI
4.306 PM_BIP8_OVER
4.307 PM_BIP8_SD
4.308 PM_TIM
4.309 PORT_EXC_TRAFFIC
4.310 PORTSWITCH_FAIL
4.311 POWER_ABNORMAL
4.312 POWER_DIFF_OVER
4.313 POWER_SAMPLE_DIFF
4.314 PRBS_LSS
4.315 PRO_PKT_FLOODING
4.316 PTP_SOURCE_SWITCH
4.317 PTP_TIMESTAMP_ABN
4.318 PUM_BCM_ALM
4.319 PUM_TEM_ALM
4.320 PUMP_LINK_ULLAGE_HIGH
4.321 PUMP_MIS_MATCH
4.322 PUMP_OFFLINE
4.323 PW_APS_DEGRADED
4.324 PW_APS_OUTAGE
4.325 PW_NO_TRAFFIC
4.326 PWAPS_LOST
4.327 PWAPS_PATH_MISMATCH
4.328 PWAPS_SWITCH_FAIL
4.329 PWAPS_TYPE_MISMATCH
4.330 PWD_ENCRYPT_RISK
4.331 PWR_UNBALANCED
4.332 R_LOC
See the alarm page according to the type of the board that reports the alarm.
4.333 RACK_CONFLICT_SCREEN
4.334 RELAY_ALARM_CRITICAL
4.335 RELAY_ALARM_IGNORE
4.336 RELAY_ALARM_MAJOR
4.337 RELAY_ALARM_MINOR
4.338 REM_SD
4.339 RL_CRITICAL_HI
4.340 RL_CRITICAL_LOW
4.341 RM_RLOS
4.342 RMON_ALM_INBADOCTS_OVER
4.343 RS_CROSSTR
4.344 RTC_FAIL
4.345 RX_POWER_ABNORMAL
4.346 RXCFG_WAVEDATA_MIS
4.347 S1_SYN_CHANGE
4.348 SCC_CHANGE
4.349 SCC_LOC
4.350 SEC_RADIUS_FAIL
4.351 SERVICE_CAPACITY_EXCEED_LICENSE
4.352 SERVICE_TYPE_EXCEED_LICENSE
4.353 SHELF_AREA_POWER_OVER
4.354 SHELF_POWER_UNCONFIG
4.355 SLAVE_WORKING
4.356 SM_BDI
4.357 SM_BEI
4.358 SM_BIP8_OVER
4.359 SM_BIP8_SD
4.360 SM_IAE
4.361 SM_TIM
4.362 SNCP_FAIL
4.363 SO_SK_MISMATCH
4.364 SPAN_LOSS_EXCEED_EOL
4.365 SPAN_LOSS_HIGH
4.366 SPAN_LOSS_LOW
4.367 SPAN_LOSS_LOWER_GAIN
4.368 SPAN_LOSS_UPPER_GAIN
4.369 SPEED_OVER
4.370 SRV_SHUTDOWN_LD
4.371 SSL_CERT_DAMAGED
4.372 SSL_CERT_NOENC
4.373 SSL_CERT_TO_EXPIRE
4.374 SSM_LOS
4.375 SSM_QL_FAILED
4.376 STORM_CUR_QUENUM_OVER
4.377 SUBNET_RT_CONFLICT
4.378 SUBRACK_COMM_PS
4.379 SUBRACK_EXCEED
4.380 SUBRACK_ID_MISMATCH
4.381 SUBRACK_LOOP
4.382 SUBRACK_TYPE_MISMATCH
4.383 SUM_INPWR_HI
4.384 SW_SNCP_PS
4.385 SW_SNCP_STA_INDI
4.386 SWDL_ACTIVATED_TIMEOUT
4.387 SWDL_AUTOMATCH_INH
4.388 SWDL_BD_EXCLUDE
4.389 SWDL_BD_MATCH_FAIL
4.390 SWDL_BD_NOT_MATCH
4.391 SWDL_BD_WEAKMATCH
4.392 SWDL_CHGMNG_NOMATCH
4.393 SWDL_COMMIT_FAIL
4.394 SWDL_INPROCESS
4.395 SWDL_PKG_NOBDSOFT
4.396 SWDL_PKGVER_MM
4.397 SWDL_ROLLBACK_FAIL
4.398 SYN_BAD
4.399 SYNC_C_LOS
4.400 SYNC_DISABLE
4.401 SYNC_F_M_SWITCH
4.402 SYNC_FAIL
4.403 SYNC_LOCKOFF
4.404 SYSLOG_COMM_FAIL
4.405 SYSPARA_CFDB_NOSAME
4.406 T_LOSEX
4.407 T_SLIP
4.408 TEM_HA
4.409 TEM_LA
4.410 TEST_STATUS
4.411 THUNDERALM
4.412 TIME_LOCK_FAIL
4.413 TIME_LOS
4.414 TIME_NO_TRACE_MODE
4.415 TR_LOC
4.416 TU_AIS_VC3
4.417 TU_LOP_VC3
4.418 TUNNEL_APS_DEGRADED
4.419 TUNNEL_APS_OUTAGE
4.420 VCAT_LOA
See the alarm page according to the type of the board that reports the alarm.
4.421 VCAT_LOM_VC3
4.422 VCAT_LOM_VC4
4.423 VCTRUNK_NO_FLOW
4.424 VLAN_SNCP_PS
4.425 VOADATA_MIS
4.426 W_R_FAIL
4.427 WAVE_ADD_ABN
4.428 WAVE_DROP_ABN
4.429 WAVEDATA_MIS
4.430 WAVELEN_OVER
4.431 XC_UNSWITCH
4.1 AD_CHECK_FAIL
Description
Self-check failure of the analog to digital (AD) chip. This alarm is reported when the AD chip
on the board is faulty.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Perform a cold reset on the faulty board on the U2000.
Step 2 If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
----End
Related Information
None
4.2 ALC_ADJUST_FAIL
Description
ALC link adjustment failure. This alarm is generated when the ALC link adjustment fails.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Name Meaning
Parameters 3 and l Indicate the slot ID of the no-response board when parameter 2 is
4 0x01.
l Indicate the slot ID of the board and the optical port reporting the
alarm when parameter 2 is 0x02.
l When parameter 2 is 0x03, parameter 3 indicates the link number and
parameter 4 is invalid.
l Indicate the timeout period when parameter 2 is 0x04.
l Indicate the timeout period when parameter 2 is 0x05.
l When parameter 2 is 0x06, parameter 3 indicates the node status and
parameter 4 is invalid.
Parameters 5 and l Indicate the number of the port that has no response when parameter 2
6 is 0x01.
l Indicate the number of the port that generates the alarm when
parameter 2 is 0x02.
Possible Causes
l The board does not respond to a query.
l Alarms such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, and R_LOS are generated
on the equipment.
l The node receives adjustment frames but no link exists on the node.
l The link adjustment operation times out.
l The node adjustment operation times out.
l The node is in an incorrect state. That is, though receiving adjustment frames, the node is
not in the pre-adjustment state.
l The node does not permit another adjustment because more than two adjustments have
been performed.
l The link configuration is in disorder.
Procedure
Step 1 Check whether the ALC configuration is normal. The configuration rules are as follows:
l The sink node cannot be configured as a reference node.
l Reference equipment must be configured for the source node.
l The detection board should not be empty for a non-reference node.
l When the detection board is OBU1, the adjustment equipment cannot be empty.
l When configuring the source node, make sure that the same optical port is not
configured for the detection equipment and reference equipment.
Step 2 Check whether the adjustment on the adjustment node is within the range.
Step 3 On the U2000, check whether other alarms, such as WRG_BD_TYPE, BD_STATUS,
MUT_LOS, and R_LOS, are generated on the current equipment. If an alarm is generated on
the equipment, first rectify the alarm.
----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.3 ALC_WAIT_ADJUST
Description
Waiting for adjustment due to an ALC link exception. This alarm is generated at the source
node when the ALC link in manual mode is faulty and needs to be adjusted.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Currently, the ALC is in the manual mode and the ALC link needs to be adjusted
because it is faulty.
Procedure
Step 1 Manually start an ALC adjustment.
----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.4 ALM_ALS
Description
The ALM_ALS is an alarm indicating automatic laser shutdown. This alarm is generated
when the laser is automatically shut down due to the R_LOS alarm generated for the optical
port.
Attribute
Parameters
None.
Possible Causes
A user has enabled the automatic laser shutdown function.
Procedure
Step 1 Disables the automatic laser shutdown function.
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.5 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that GFP client signals are lost. When the source
end does not receive any GFP client signal, it sends a management frame to the sink end. This
alarm is generated when the sink end receives the management frame.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The source interface module is faulty. For example, the optical module does not exist or
match, or the optical or electrical signals are lost.
l The source physical link fails and cannot receive physical signals.
Procedure
Step 1 Check the alarm information on the NMS and determine the ID of the VCTRUNK port that
reports the alarm.
Step 2 Check whether the physical link where the source VCTRUNK port resides is functioning
properly. If the physical link fails due to optical-fiber damage, replace the optical fiber and
check whether the ALM_GFP_dCSF alarm is cleared.
Step 3 If the alarm persists, check whether the source interface module runs properly. If the source
interface module does not run properly, replace it.
Step 4 If the alarm persists, replace the board that reports the alarm.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.6 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the generic framing procedure (GFP) frame
is out of frame. This alarm is generated when the GFP state machine escapes from the SYNC
state, and is cleared when the state machine enters the SYNC state again.
Attribute
Parameters
None.
Possible Causes
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: The board reporting the alarm 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 (downlink) timeslots bound with the local
VCTRUNK is consistent with the number of downlink (uplink) timeslots bound with the
peer VCTRUNK.
If... Then...
The number of timeslots Modify Number of Bound Paths at either end to ensure
is inconsistent that the number of timeslots is consistent. Then, check
whether the ALM_GFP_dLFD alarm is cleared. If the
alarm persists, go to the next step.
2. Double-click a desired NE. In the NE Explorer, choose Configuration > SDH Service
Configuration from the navigation tree.
3. Check whether the number of timeslots bound with the VCTRUNK matches cross-
connection settings.
If... Then...
4. Check whether the service level is consistent between the SDH cross-connections at both
ends. If the service level is inconsistent, for example, the service level of the SDH cross-
connections at the local end is VC4 but that at the peer end is VC4-16C, reconfigure the
service level of SDH cross-connections to keep its consistency between both ends.
5. Check whether the ALM_GFP_dLFD alarm is cleared. If the alarm persists, go to Step
2.
If... Then...
Alarms, such as B3_EXC, B3_SD, Clear the alarms or events. Then, check
IN_PWR_HIGH, and IN_PWR_LOW, whether the ALM_GFP_dLFD alarm is
or events, such as RSBBE, MSBBE, and cleared. If the alarm persists, go to Step 3.
HPBBE exist
2. Then, check whether the alarm is cleared. If the ALM_GFP_dLFD alarm persists,
contact Huawei technical support engineers to handle this alarm.
----End
Related Information
Cell Delimitation State Machine
The cell delimitation state machine is available in three states: HUNT, PRESYNC, and
SYNC. In the HUNT state, the state machine hunts the position of delimitating cells in the
BYTE BY BYTE manner. After finding a correct HCS, the state machine changes to the
PRESYNC state. In the PRESYNC state, the state machine locks the position of delimitating
cells. After consecutively receiving DELTA correct HCS cells, the state machine changes to
the SYNC state. In this case, the cell boundary is found. In the PRESYNC state, after
receiving an incorrect HCS cell, the state machine returns to the HUNT state. In the SYNC
state, after consecutively receiving ALPHA incorrect HCS cells, the state machine changes to
the HUNT state. Otherwise, it keeps in the SYNC state, as shown in the following figure.
4.7 ALM_HANGUP
Description
Orderwire phone being in the off-hook state for a long time. This alarm is generated when the
orderwire phone is in the off-hook state for a long time.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The orderwire phone is in the off-hook state for a long time.
l The hardware is faulty.
Procedure
Step 1 Check whether the orderwire phone is hung up. If not, hang up the phone. Then, check
whether the ALM_HANGUP alarm is cleared.
Step 2 If the alarm persists, perform a cold reset on the optical supervisory channel board (for
example, SC2 board) on the U2000.
Step 3 If the ALM_HANGUP alarm persists, the board hardware may be faulty. Replace the board.
----End
Related Information
None
4.8 ALS_ACTIVE
Description
Automatic laser shutdown (ALS) alarm. This alarm is generated when the laser is turned off
using the ALS function.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The input signals on the client side are missing at the local or opposite site.
l The WDM side of the related boards at the local site is faulty or reports a (Lower Order
ODUk, LO ODUk) ODUk_PM_BDI alarm.
Procedure
Step 1 Check the ALS function configuration of the involved boards, and determine the triggering
condition of the ALS function. For details, see "ALS" in the Feature Description.
Step 2 On the U2000, query whether the R_LOS alarm is generated on the client side of the related
boards. If it is, handle the alarm with reference to the corresponding handling procedure.
Step 3 On the U2000, query whether the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, or (Lower Order ODUk, LO ODUk) ODUk_PM_BDI alarm is
generated on the WDM side of the related boards. If it is, handle the alarm with reference to
the corresponding handling procedure.
----End
Related Information
The OTU board and tributary board of WDM equipment provide the ALS function. For
details, see "ALS" in the Feature Description.
4.9 ALS_TRIGGERED
Description
This alarm is generated when the laser on a CRPC board or a TN12RAU1/TN12RAU2/
TN11SRAU/TN97RPC board is turned off by the automatic laser shutdown (ALS) function.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The laser on the CRPC board or a TN12RAU1/TN12RAU2/TN11SRAU/TN97RPC board is
shut down by the ALS function.
Procedure
Step 1 Check the communication between the CRPC board or a TN12RAU1/TN12RAU2/
TN11SRAU/TN97RPC board and the system control board.
Step 2 Restart the intelligent power adjustment (IPA) function. The laser on the OA board on the
upstream NE emits probe light to turn on the laser on the CRPC board or a TN12RAU1/
TN12RAU2/TN11SRAU/TN97RPC board and restore the services.
----End
Related Information
None
4.10 APE_ADJUST_FAIL
Description
Automatic power equilibrium (APE) adjustment failure. This alarm is generated when the
APE adjustment fails.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The communication between APE NEs fails.
l The involved board is offline.
l The involved board is faulty.
l The equilibrium cannot be reached after adjustment.
l The board type is incorrect.
l The number of adjustment times exceeds the upper limit.
l The adjustment is stopped by the user.
Procedure
Step 1 Isolate the alarm cause and handle the alarm accordingly.
----End
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.11 APE_ADJUST_PEND
Description
This alarm is generated when APE adjustment is pending.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
The APE detects that the optical power of some channels is unequal and is going to start an
adjustment.
Procedure
Step 1 Manually start an APE adjustment.
Step 2 If the APE_ADJUST_PEND alarm persists and simultaneously the APE_ADJUST_FAIL
alarm is reported, clear the alarms with reference to the procedure for clearing the
APE_ADJUST_FAIL alarm.
----End
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.12 APS_FAIL
Description
The APS_FAIL is an alarm indicating a multiplex section protection (MSP) switching failure.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 MSP group where the switching occurs.
l 0x01: linear MSP group
l 0x02: ring MSP group
Possible Causes
l MSP parameters are incorrectly configured.
l The MSP configuration is lost.
l The board is faulty.
Procedure
Step 1 Check whether the network-wide MSP configuration is correct. For ring MSP, check the
optical-fiber connection. For linear MSP, check working and protection optical-fiber
connections or MSP switching mode. After MSP configuration is corrected, check whether
the APS_FAIL alarm is cleared.
Step 2 If the alarm persists, check whether the network-wide MSP-related protocols are properly
running. If the protocols are not running properly, restart them. Then, check whether the
APS_FAIL alarm is cleared.
Step 3 If the alarm persists, replace the board that reports this alarm.
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.13 APS_INDI
Description
The APS_INDI is an alarm indicating the APS state. This alarm is generated when the MSP is
in the switching state.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: An external command is issued to initiate a switching (such as manual
switching, forced switching, exercise switching, and lockout of switching).
l Cause 2: There is an alarm that triggers an automatic MSP switching, for example,
R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD.
l Cause 3: The service board is faulty.
l Cause 4: The SCC board is faulty.
Procedure
Step 1 Query this alarm on the NMS and determine the MSP group type and ID based on alarm
parameters.
Step 2 Cause 1: An external command is issued to initiate a switching (such as manual switching,
forced switching, exercise switching, and lockout of switching).
1. Query the MSP switching state.
If... Then...
The MSP group is in the state of manual Clear the switching state and check
switching, forced switching, exercise whether the alarm is cleared. If the
switching, or locked switching. alarm persists, go to Step 3.
Step 3 Cause 2: There is an alarm that triggers an automatic MSP switching, for example, R_LOS,
R_LOF, MS_AIS, B2_EXC, or B2_SD.
1. Check whether the MSP group is in the automatic switching state.
If... Then...
The local NE reports the The MSP group enters the automatic switching
R_LOS, R_LOF, MS_AIS, or state and reports the APS_INDI alarm. In this case,
B2_EXC alarm. clear the R_LOS, R_LOF, MS_AIS, or B2_EXC
alarm and check whether the APS_INDI alarm is
cleared.
If the APS_INDI alarm persists, go to the next step.
The local NE reports the B2_SD After you enable the SD switching condition, the
alarm. SD-related alarm can trigger the MSP switching.
You can use either of the following methods to
NOTE
clear the APS_INDI alarm:
Both SF and SD switching
conditions can trigger automatic – Disable SD switching.
MSP switching. The B2_SD alarm
cannot trigger MSP switching by
– Clear the B2_SD alarm first.
default but can be specified as the
Check whether the APS_INDI alarm is cleared. If
SD switching condition to trigger
MSP switching. the alarm persists, go to the next step.
If... Then...
Revertive Mode is After the working path recovers, the services are switched
set to Revertive. automatically from the protection path to the working path only
when the preset wait to restore (WTR) time expires. The
APS_INDI alarm is cleared after the switching is successful.
When the MS is automatically restored from the switching state to
the normal state, check whether the APS_INDI alarm is cleared.
If the alarm persists, go to Step 4.
Revertive Mode is After the working path recovers, the services are not switched
set to Non- automatically from the protection path to the working path and
Revertive. the APS_INDI alarm persists.
To clear the alarm, manually switch the services from the
protection path to the working path.
3. In the NE Explorer, select the NE, and choose Configuration > Linear MS or
Configuration > Ring MS from the navigation tree. In the Slot Mapping Settings area,
right-click the working unit or the protection unit of a protection group and choose the
desired switching mode from the shortcut menu.
4. After the manual switching is successful, check whether the APS_INDI alarm is cleared.
If the alarm persists, go to Step 4.
If... Then...
If... Then...
The SCC board reports alarms indicating Warm reset the SCC board.
hardware or software faults, such as the
Check whether the alarm is cleared. If
HARD_BAD and HARD_BAD alarms.
the alarm persists, go to the next step.
The SCC board does not report alarms Contact Huawei technical support
indicating hardware or software faults. engineers to handle the alarm.
2. Replace the faulty SCC board. Check whether the alarm is cleared. If the alarm persists,
contact Huawei technical support engineers to handle the alarm.
----End
Related Information
Revertive Mode
The Revertive Mode field can be set to Revertive or Non-Revertive. Generally, the value
Revertive is recommended.
l If you set Revertive Mode to Revertive, the services will be automatically switched
from the protection path to the working path after the working path recovers.
l If you set Revertive Mode to Non-Revertive, the services will not be automatically
switched from the protection path to the working path after the working path recovers.
Instead, the services are still transmitted over the protection path.
4.14 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped
manually.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The MSP protocol is manually stopped.
Procedure
Step 1 On the NMS, locate the MSP subnet where the MSP protocol is stopped.
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.15 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.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
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.
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.
----End
Related Information
None
4.16 ARP_SPOOF
Description
The ARP_SPOOF alarm indicates that the system being spoofed by ARP.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
For the same IP address of ARP table, the numbers of free ARP packets and ARP response
packets that are received every minute and the MAC addresses of the packets are inconsistent
with the MAC addresses in the current ARP table exceed the thresholds.
Procedure
Step 1 Query the attacker list.
Step 2 Locate the attacker according the MAC address of the attacker list, and then remove it.
----End
Related Information
None
4.17 ASE_NOT_CALIBRATE
Description
This alarm is generated when the amplified spontaneous emission (ASE) on the Raman
optical module is not demarcated.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Possible Causes
After the demarcation for the RAU board is complete, the ASE of the Raman optical module
on the RAU board is not demarcated if the RAU board is replaced or the type of the logical
fibers used by the RAU board is changed.
Procedure
Step 1 On the U2000, demarcate the RAU board. If the demarcation is successful, the alarm will be
cleared automatically.
----End
Related Information
None
4.18 AU_AIS
Description
The AU_AIS is an alarm indication of the administrative unit (AU). This alarm is generated
when the optical port on the local NE receives the AU pointer of all 1s.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None.
Possible Causes
l Cause 1: The local NE has the higher level alarms.
l Cause 2: The upstream NE inserts the AIS alarm to the downstream NE.
l Cause 3: The transmit boards on the upstream NE are faulty.
l Cause 4: The receive boards on the local NE are faulty.
Procedure
Step 1 Cause 1: The local NE has the higher level alarms.
1. On the NMS, check the local NE for higher level alarms.
If... Then...
The higher level alarms, such as the Clear these alarms and then check whether
R_LOS, R_LOF, B1_EXC, and the AU_AIS alarm is cleared. If the alarm
B2_EXC alarms, are reported. persists, go to Step 2.
Step 2 Cause 2: The upstream NE inserts the AIS alarm to the downstream NE.
1. Check upstream NEs for higher level alarms.
If... Then...
Any of the alarms listed in Table 4-1 Clear the alarm and check whether the
occurs. AU_AIS alarm is cleared. If the alarm persists,
go to the next step.
2. Perform loopback to locate the upstream NE that initially generates the AU_AIS alarm.
NOTICE
The loopback will interrupt services.
3. Check whether the AU_AIS alarm occurs on the peer NE after the loopback is
performed.
If... Then...
The AU_AIS alarm is reported on The peer NE has transmitted the AU_AIS
the peer NE. alarm to the local NE. In this case, go to the
next step.
4. Perform loopback to locate the upstream NE that generates the AU_AIS alarm. Check
the service source board of the NE for higher level alarms.
If... Then...
Any of the alarms listed in Table 4-1 Clear the alarm and check whether the
occurs AU_AIS alarm is cleared. If the alarm
persists, go to Step 4.
----End
Related Information
HP_UNEQ
4.19 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm is generated when
the optical port of the local NE receives eight consecutive frames that contain NDFs or invalid
AU pointers.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Cause 1: The number of bit errors received by the local NE exceeds the upper threshold.
l Cause 2: The services transmitted by the peer NE and received by local NE are
inconsistent in the service level.
l Cause 3: Boards on the local NE are faulty.
l Cause 4: Boards on the peer NE are faulty.
Procedure
Step 1 Cause 1: The number of bit errors received by the local NE exceeds the upper threshold.
1. Check whether local NE reports the following bit error alarms:
– B1_EXC
– B1_SD
– B2_EXC
– B2_SD
2. If the local NE reports any of the preceding alarms, clear it and check whether the
AU_LOP alarm is cleared. If the local NE reports no bit error alarm, or the AU_LOP
alarm persists after bit error alarms are cleared, go to Step 2.
Step 2 Cause 2: The services transmitted by the peer NE and received by local NE are inconsistent in
the service level.
1. Check whether the services transmitted by the peer NE and received by local NE are
consistent in the service level.
If... Then...
Services transmitted by the peer NE and Reconfigure the service level on the
received by local NE are inconsistent in local and peer NEs and check whether
the service level. the AU_LOP alarm is cleared. If the
alarm persists, go to Step 3.
NOTICE
If services traversing the board are not protected, cold resetting the board will interrupt
services.
2. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the local
receive board.
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, go to Step 4.
NOTICE
If services traverse the board are not protected, a board cold reset will interrupt services.
2. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the peer
transmit board.
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
4.20 B1_SD
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.20.2 B1_SD (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
Procedure
Step 1 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 2 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 4 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 6 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 7 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
Description
Regenerator section (B1) signal degraded. This alarm is generated when the received signals
in SDH frame degrade and the B1 bit errors on the regenerator section exceed the signal
degrade (SD) threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The attenuation of the received signals is overlarge; the fiber or connector is dirty.
l The transmit part of the opposite station is faulty.
l The receive part of the local station is faulty.
Procedure
Step 1 On the U2000, check whether the receive optical power of the port is within the permitted
range. If the receive optical power of the board at the local station is excessively low, clear the
alarm according to the handling procedure of the IN_PWR_LOW alarm.
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding port on
the upstream board is within the permitted range on the U2000. If the transmit optical power
of the board at the upstream station is excessively low, clear the alarm according to the
handling procedure of the OUT_PWR_LOW alarm.
Step 3 If the alarm persists, check on the U2000 whether the bit error alarm exists at the upstream
station by using the and loop back the transmit optical port and receive optical port on the
WDM side of the OTU board at the upstream station. If bit errors exist, clear the bit error fault
of the upstream station.
Step 4 If the alarm persists and the faulty board supports pluggable optical modules, Replace the
specific pluggable optical module.
Step 6 If the alarm bursts, it may be caused by the transmission line influenced by various noise
sources. Search for the jam source that may cause the burst bit errors and remove the
interference.
----End
Related Information
None
4.21 B2_EXC
Description
The B2_EXC is an alarm indicating that the number of multiplex section B2 bit errors in the
signals received on the line exceed the specified value. When a line board detects that the bit
errors of the multiplex section signals exceed the threshold for the B2_EXC alarm by
detecting the B2 byte, the B2_EXC alarm is reported.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The possible causes of the B2_EXC alarm are as follows:
Procedure
Step 1 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 2 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 4 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 6 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 7 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.22 B2_SD
Description
The B2_SD is an alarm indicating that multiplex section B2 signals received on the line are
degraded. When a line board detects that the bit errors of the multiplex section signals exceed
the B2_SD alarm threshold but are lower than the B2_EXC alarm threshold, the B2_SD alarm
is reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The possible causes of the B2_SD alarm are as follows:
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 2 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 4 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 6 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 7 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.23 B3_EXC
Description
The B3_EXC is an alarm indicating that the number of the higher order path (HP) B3 bit
errors exceeds the specified threshold. This alarm is generated when a board detects that the
number of the HP bit errors exceeds the specified threshold (default threshold: 10-3) by
monitoring the B3 byte.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Possible Causes
The possible causes of the B3_EXC alarm are as follows:
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 2 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 4 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 6 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 7 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.24 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the number of lower order path (LP) VC-3 B3
bit errors exceeds the specified threshold. This alarm is generated when a board detects that
the number of the VC-3 bit errors exceeds the B3_EXC alarm threshold by monitoring the B3
byte.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Possible Causes
l Higher-level bit error alarms have occurred in the system.
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the local and upstream NEs for the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm. If any of these alarms exists, clear it and check whether the B3_EXC_VC3
alarm is cleared.
Step 2 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 3 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 4 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 6 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 7 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 9 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.25 B3_EXC_VC4
Description
The B3_EXC_VC4 is an alarm indicating that the number of the VC-4 B3 bit errors exceeds
the specified threshold. This alarm is generated when a board detects that the number of the
VC-4 bit errors exceeds the specified threshold by monitoring the B3 byte.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Higher-level bit error alarms have occurred in the system.
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the local and upstream NEs for the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm. If any of these alarms exists, clear it and check whether the B3_EXC_VC3
alarm is cleared.
Step 2 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 3 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 4 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 6 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 7 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 9 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
4.26 B3_SD
Description
The B3_SD is an alarm indicating higher order path (HP) B3 signal deterioration. This alarm
is generated when a board detects that the number of HP signal bit errors exceeds the B3_SD
alarm threshold (default threshold: 10-6) but remains below the B3_EXC alarm threshold
(default threshold: 10-3) by monitoring the B3 byte.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
The possible causes of the B3_SD alarm are as follows:
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 2 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 4 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 6 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 7 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.27 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the number of the VC-3 B3 bit errors exceeds the
specified threshold. This alarm is generated when a board detects that the number of the VC-3
bit errors exceeds the B3_SD alarm threshold by monitoring the B3 byte.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Higher-level bit error alarms have occurred in the system.
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the local and upstream NEs for the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm. If any of these alarms exists, clear it and check whether the B3_EXC_VC3
alarm is cleared.
Step 2 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 3 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 4 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 6 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 7 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 9 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.28 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that the number of the VC-4 B3 bit errors has
exceeded the specified threshold. This alarm is generated when a board detects that the
number of the VC-4 bit errors exceeds the specified threshold by monitoring the B3 byte.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Higher-level bit error alarms have occurred in the system.
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the local and upstream NEs for the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm. If any of these alarms exists, clear it and check whether the B3_EXC_VC3
alarm is cleared.
Step 2 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 3 Check whether the alarm-reporting board runs in an equipment room with a temperature
higher than 45°C or lower than 0°C for a long period of time. If the temperature is higher than
45°C or lower than 0°C, adjust it into the normal range and check whether the alarm is
cleared.
Step 4 If the alarm persists, check whether the alarm-reporting board has a proper receive optical
power.
If... Then...
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 5 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber
connector is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
the alarm is cleared.
Step 6 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 7 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 8 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 9 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
4.29 BD_BPXC_MISMATCH
Description
The board access capability mismatches the cross-connect capacity of the backplane in the
subrack.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Due to incorrect configurations or the limitations of the system initial status, the board access
capacity mismatches the backplane cross-connect capacity.
Procedure
Step 1 Configure the working mode of the service board to the regeneration mode.
Step 2 Replace the cross-connect board that matches with the service board capacity.
----End
Related Information
None
4.30 BD_LEDTEST
Description
Board LED blinking test alarm. This alarm is generated when an LED blinking test is
performed on a board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l A board receives a command for performing an LED blinking test.
Procedure
Step 1 Check whether an LED blinking test is being performed on the board. If an LED blinking test
is being performed, wait until the test is complete. The alarm will be terminated after the test
is complete.
----End
Related Information
None
4.31 BD_NOT_INSTALLED
Description
Logical board not added in the corresponding slot. This alarm is generated when a physical
board is installed on the equipment but no logical board is created on the U2000.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the slot ID of the board where the alarm is generated.
Possible Causes
The logical board is not created.
Procedure
Step 1 On the U2000, add a logical board for the board that reports the alarm.
----End
Related Information
None
4.32 BD_STATUS
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.32.2 BD_STATUS (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The BD_STATUS is an alarm indicating an offline physical board. This alarm is reported
when a user has configured a board on the NMS but has not installed the board.
Attribute
Parameters
None.
Possible Causes
l Cause 1: The board is being reset.
l Cause 2: The board is not installed or has poor contact with the backplane.
l Cause 3: The board is faulty or the backplane has bent pins.
Procedure
Step 1 Cause 1: The board is being reset.
1. View the board indicator to determine whether the board is being reset. For details, see
the Hardware Description. Alternatively, query historical resets of the board. For details,
see in Supporting Tasks.
If... Then...
The board is being reset Wait until the reset is complete (about 5 minutes) and
check whether the BD_STATUS alarm is cleared.
2. Check whether the BD_STATUS alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The board is not installed or has poor contact with the backplane.
1. On the NMS, double-click the alarm-reporting NE in the Main Topology. Then, record
the logical-board type for the alarm-reporting slot on the NE Panel.
2. Check whether the physical board is installed.
If... Then...
The physical board is not Properly install the physical board that matches the
installed logical board.
Check whether the BD_STATUS alarm is cleared. If the
alarm persists, go to Step 3.
If... Then...
If the contact is poor Remove and properly re-insert the board. Then, check whether
the BD_STATUS alarm is cleared. If the alarm persists, go to
Step 3.
If... Then...
Step 3 Cause 3: The board is faulty or the backplane has bent pins.
1. Replace the alarm-reporting board. For details, see Parts Replacement. Then, check
whether the BD_STATUS alarm is cleared.
2. If the alarm persists, check whether the backplane has bent pins.
If... Then...
The backplane has bent pins Contact Huawei technical support engineers to repair
the bent pins. Then, properly re-insert the board.
The backplane has no bent pin Contact Huawei technical support engineers to
handle the alarm.
----End
Related Information
None.
Description
Physical board being offline. This alarm is generated when the logical board is created on the
U2000 but the physical board is not inserted in the slot.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The AUX board is faulty.
l The logical board is configured but the physical board has not been inserted in the
corresponding slot.
l The connection between the plug of the board and the socket of the backplane is loose.
l The board is faulty.
l The backplane is faulty.
Procedure
Step 1 If the alarm is reported on the AUX board and all service boards but services are normal and
the SCC board operates normally, it indicates that the AUX board is faulty. Perform a warm
reset or cold reset on the faulty board through the U2000. If the alarm persists, replace the
AUX board.
Step 2 Check whether the corresponding physical board is inserted in the physical slot.
l If no corresponding board is inserted, insert the board.
l If the corresponding board is inserted, check whether the insertion is firm. If not, reset
the board.
Step 3 If the alarm persists, replace the faulty board. For details, see "Replace the board.".
Step 4 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A32 When OptiX BWS 1600G SCC Board Is Replaced with the SCE, TC2 Board
Reports BD_STATUS Alarm
l MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
l MC-A195 Incorrect DIP Settings Cause the BD_STATUS Alarm on the CRPC Board
l MC-A213 Internal Communication of an NE Is Abnormal And Many Boards Report
Transiently BD_STATUS or COMMUN_FAIL Alarms Due to Conflicted Subrack IDs
l MC-A231 The Board Cannot Identify the Subrack, So A New OTU Board on an OptiX
OSN 8800 NE Fails to Go Online
4.33 BDID_ERROR
Description
The BDID_ERROR is an alarm indicating an error in board position check. This alarm is
generated when a board parity check fails or the board is not properly installed.
Attribute
Parameters
None.
Possible Causes
l The board is not properly installed.
l The board has hardware faults.
l The backplane has bent pins.
Procedure
Step 1 Query this alarm on the NMS and determine the board that reports the alarm.
Step 2 Remove the board to check the backplane for bent pins. If the backplane has bent pins, repair
them and re-insert the board. Then, check whether the BDID_ERROR 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.34 BIOS_STATUS
Description
The BIOS_STATUS is an alarm indicating the BIOS status. By default, if loading of the board
software fails for three consecutive times within five minutes, the board enters the BIOS
status and the BIOS_STATUS alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the BIOS_STATUS alarm are as follows:
Procedure
Step 1 View the BIOS_STATUS alarm on the U2000, and then determine the board where the
BIOS_STATUS alarm is generated.
Step 2 Perform warm reset on the board and then check whether the BIOS_STATUS alarm is
cleared.
Step 3 If the BIOS_STATUS alarm persists, perform cold reset on the board. Then check whether the
BIOS_STATUS alarm is cleared.
Step 4 If the BIOS_STATUS alarm persists, contact Huawei technical support engineers and ask
them to replace the board software. After the board software is replaced, check whether the
BIOS_STATUS alarm is cleared.
Step 5 If the alarm persists, replace the board.
----End
Related Information
None
4.35 BWUTILIZATION_OVER
Description
The BWUTILIZATION_OVER is an alarm indicating that bandwidth usage exceeds the
threshold. If traffic received or transmitted by monitored objects such as traffic classification
exceeds the traffic threshold and the bandwidth usage exceeds the acceptable value, the
BWUTILIZATION_OVER alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 where 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.
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 Cause 1: The traffic received or transmitted by a monitored object exceeds the traffic
threshold.
1. On the NMS, view alarm information and determine the object (traffic classification)
that generates the alarm.
2. Check whether the network traffic exceeds the traffic threshold. If the configured traffic
threshold is low, check whether the threshold can be raised. You can raise the threshold
to make it greater than the actual traffic to clear the alarm. If the threshold cannot be
raised, go to the next step.
3. Check whether network storm or invalid data source exists on the network. Eliminate the
source that transmits a large amount of data and check whether the alarm is cleared.
4. If the alarm persists, enable CAR or configure QoS to reduce the data traffic transmitted
from the peer end.
5. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The configured bandwidth usage threshold for a monitored object is low.
1. On the NMS, view alarm information and determine the object (traffic classification)
that generates the alarm.
2. Check whether the bandwidth usage threshold for the object is low. If the configured
threshold is low, expand network capacity to clear the alarm.
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.36 C2_VCAIS
Description
The C2_VCAIS is an alarm pertaining to C2 bytes. This alarm is generated when a board
detects that all the received C2 bytes are 1.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The remote end has incorrectly configured the to-be-transmitted C2 bytes.
Procedure
Step 1 View the alarm information on the NMS and determine the VC path that reports this alarm.
Step 2 Check whether the remote end has correctly configured the to-be-transmitted C2 bytes. If the
remote end has incorrectly configured the C2 bytes, reconfigure them and check whether the
C2_VCAIS alarm is cleared.
Step 3 If the alarm persists, replace the transmit board of the remote end.
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.37 CFCARD_FAILED
Description
CF card failed.
Attribute
Parameters
None
Possible Causes
The CF card is faulty and needs to be replaced.
Procedure
Step 1 Replace the CF card and check whether the CFCARD_FAILED alarm is cleared. If the alarm
persists, replace the system control board.
----End
Related Information
None
4.38 CFG_DATACHECK_FAIL
Description
Database check error alarm. The database will be checked during the NE running. If the
database check fails, a database check failure alarm will be reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameters 1 and 2 Indicate the board on which the OCP database fails to recover.
Possible Causes
l The database check on the standby system control board fails.
l The real-time retransmission database check on the standby system control board fails.
l The batch backup database check on the active system control board fails.
Procedure
Step 1 When the database restoration fails, save the database for further fault diagnosis.
Step 2 Retrieve the backup database.
Step 3 Re-send service configurations.
----End
Related Information
None
4.39 CFG_DATASAVE_FAIL
Description
Failure to save configuration data. This alarm is reported when configuration fails to be saved
in the database.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameters 1 and 2 Indicate the board on which the OCP database fails to recover.
Possible Causes
l The configurations fail to be saved to the database.
l The command fails to be saved to the database.
Procedure
Step 1 When the database restoration fails, save the database for further fault diagnosis.
----End
Related Information
None
4.40 CFP_LOS
Description
Loss of signals in CFP module. This alarm is generated when the receive end of the channel
on the CFP module receives no signal.
Attribute
Parameters
None.
Possible Causes
l Cause 1: No fiber jumper is connected to the optical port on the channel of the CFP
module, the fiber jumper connected to the optical port is loose, or the fiber jumper is
connected incorrectly.
l Cause 2: The line attenuation is excessively high or a fiber cut occurs.
l Cause 3: The laser of the board at the opposite station is shut down.
l Cause 4: The transmit module of the opposite station or receive module of the local
station is faulty.
Procedure
l On the U2000, check the alarm information and record the IDs of the port and channel
where this alarm is generated.
l Cause 1: No fiber jumper is connected to the optical port on the channel of the CFP
module of the local station, the fiber jumper connected to the optical port is loose, or the
fiber jumper is connected incorrectly.
a. Check the fiber jumper connection on the channel of the CFP module of the local
station.
b. Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers according to the actual
networking environment.
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 there is a fiber cut.
a. On the U2000, check whether the receive optical power at the optical port is within
the permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
The receive optical power is Check the relevant fiber connectors. If there is
normal. any dirt or damage, clean or replace the fiber
connectors.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3.
l Cause 3: The laser of the board at the opposite station is shut down.
a. On the U2000, check whether the laser on the board at the opposite station is on. If
not, turn on the laser.
b. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 4.
l Cause 4: The transmit module of the opposite station or receive module of the local
station is faulty.
a. If the alarm persists, check whether the board at the opposite station or the board at
the local station supports pluggable optical modules.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None
4.41 CHAN_ADD
Description
Wavelengths being added to a single- wavelength signal. This alarm is generated when the
multi-channel spectrum analyzer (MCA) board detects that new wavelengths are added after it
scans the optical spectrum.
Attribute
Parameters
None
Possible Causes
l The configuration for wavelength monitoring is incorrect. The received wavelengths are
not configured as the monitored wavelengths.
l The MCA board is faulty.
Procedure
Step 1 On the U2000, check whether the configuration for wavelength monitoring of the MCA board
is incorrect. If the configuration is incorrect, modify the configuration to ensure that the
monitored wavelength and the number of the monitored wavelengths are consistent with the
accessed wavelength and the number of accessed wavelengths.
Step 2 If the alarm persists, test the optical spectrum data of the input optical signals using the
optical spectrum analyzer. If the data is normal, the optical spectrum analyzing module of the
MCA board may be faulty. Replace the faulty board.
----End
Related Information
None
4.42 CHIP_ABN
Description
The CHIP_ABN is an alarm indicating an invalid temperature chip. This alarm is generated
when a temperature chip becomes invalid.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 invalid temperature chip. The value 0x01 indicates
that the temperature chip becomes invalid.
Possible Causes
The temperature chip becomes invalid.
Procedure
Step 1 Check whether there is another cross-connect board that is working properly. If there is such a
board, cold reset the board that has reported the CHIP_ABN alarm. After the cold reset is
successful, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the alarm-reporting 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.
4.43 CLIENT_PORT_STA_INDI
Description
Status indication of a client 1+1 protection group. This alarm is generated when the working
or protection channel of a protection group is faulty or a user delivers an external switching
command.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching,
manual switching, or locked switching.
l Cause 2: The services on the working channel or the protection channel of a client 1+1
protection group are faulty.
l Cause 3: The switching is in WTR state. After WTR Times (s) elapses, the alarm clears.
Procedure
l Cause 1: A user delivers an external switching command such as forced switching,
manual switching, or locked switching.
a. On the U2000, query the switching status of the protection group. If the switching
state is forced switching, manual switching, or locked switching, check whether the
external switching operation is necessary.
b. If the external switching operation is necessary, ignore the alarm.
c. If the external switching operation is unnecessary, deliver a command to clear the
external switching.
l Cause 2: The services on the working channel or protection channel of the client 1+1
protection group are faulty.
a. Query whether the related boards on the working channel or protection channel of
the protection group have the alarms, such as R_LOF, R_LOS, R_LOC,
HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM,
ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_TIM,
REM_SF, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC or REM_SD.
If they do, handle the alarms with reference to the corresponding alarm handling
procedures.
b. If the alarm persists, check whether the attribute of the protection group is
Revertive. If the attribute is Revertive, after WTR Times the active channel of the
service automatically switches to the working channel and then the alarm clears. If
the attribute is Non-Revertive, set it to Revertive, and after WTR Times the alarm
clears.
l Cause 3: The switching is in WTR state. After WTR Times elapses, the alarm clears.
a. There is no need to handle this alarm. After WTR Times elapses, the alarm clears.
----End
Related Information
For details, see "Client 1+1 Protection" in the Feature Description.
4.44 CLIENT_PROT_NOTSTART
Description
Client 1+1 protection group not started. This alarm is generated when a client 1+1 protection
group is not started because the configurations on the both sides of the working and protection
channels of the protection group do not meet the requirements of enabling the protection
group.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l An incorrect electrical-layer cross-connections is configured on the working or
protection channel.
l Complete electrical-layer services between WDM-side ports and client-side ports are not
configured on the working or protection channel.
l An EVPL link that converges at a client-side optical port is configured for the working
or protection channel.
Procedure
Step 1 On the U2000, query whether an incorrect electrical-layer cross-connection is configured on
the working or protection channel, such as a cross-connection with an IP port as the source
and another IP port as the sink. If it is, delete the incorrect electrical-layer cross-connection.
Step 2 If the alarm persists, check the OTU board on which electrical-layer cross-connections can be
configured. If incomplete electrical-layer cross-connections are configured between WDM-
side ports and client-side ports, configure the complete electrical-layer cross-connections.
Step 3 If the alarm persists, check whether an EVPL link that converges in the downlink is
configured for the working or protection channel. If it is, change this EVPL link to an EPL
link or an EVPL link that broadcasts in the downstream.
----End
Related Information
For details, see "Client 1+1 Protection" in the Feature Description.
4.45 CLK_LOCK_FAIL
Description
Clock lockout failure alarm. When the frequency of an NE is synchronized from the
upstream, the frequency lock status is locking. When the frequency of an NE is not locked,
this alarm is reported to remind the user of the unlock status of the NE clock.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 clock board 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 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 0x02 indicates that the difference between phase discrimination values is
larger than 300 within 40s.
Possible Causes
The possible causes of the CLK_LOCK_FAIL alarm are as follows:
l Case 1: In the case of physical synchronization, the clock source has excessive frequency
deviation.
l Case 2: The physical link with the clock source is faulty.
Procedure
l Cause 1: In the case of physical synchronization, the clock source has excessive
frequency deviation.
a. Check for BER-related alarms or performance events at a higher level on the NMS.
If there are such alarms or performance events, handle them and then check whether
the CLK_LOCK_FAIL alarm is cleared.
b. If an external clock source is traced, check whether the clock signals are normal. If
not, update the traced clock source.
c. Check whether clock configuration is correct. For example, check whether the input
mode matches the output mode. Correct clock configuration and then check
whether the CLK_LOCK_FAIL alarm is cleared.
d. If the alarm persists, the clock board may be faulty. In this case, replace the faulty
clock board.
l Cause 2: The physical link with the clock source is faulty.
a. On the NMS determine the number of the port where the alarm is reported.
b. Check whether a network cable or fiber is disconnected from this port. If yes,
reconnect the network cable or fiber, and then check whether the alarm is cleared.
c. If the alarm persists, check whether the network cable or fiber is faulty. If yes,
replace the network cable or fiber and then check whether the alarm is cleared.
d. If the alarm persists, query the transmit optical power of the opposite NE on the
NMS. If the transmit optical power of the opposite NE is abnormal, replace the
optical module at the corresponding port on the opposite NE.
e. If the alarm persists, check whether the local receive board is faulty. If yes, replace
the board that reports the alarm on the local NE.
----End
Related Information
None
4.46 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE is an alarm indicating that the clock enters the non-tracing
mode. This alarm is generated when the current clock does not trace any line clock source,
tributary clock source, or external clock source.
Attribute
Parameters
None
Possible Causes
The possible causes of the CLK_NO_TRACE_MODE alarm are as follows:
l Cause 1: If SDH boards are configured on NEs, a priority table is not manually set for
the system, and NEs use their own default priority tables.
l Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.
Procedure
l Cause 1: If SDH boards are configured on NEs, a priority table is not manually set for
the system, and NEs use their own default priority tables.
a. Query the current priority table of the system. If there is only the internal clock
source in the priority table, set the clock source priority table to include other
available clock sources. After the setting, the alarm is automatically cleared. For
details, see Configuring the System Clock Source Priority Table in the Feature
Description.
l Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.
a. In the current priority table, if the internal clock source is not the only available
source, find out why other clock sources cannot be traced. Common causes are as
follows:
n The existence status of the clock source is lost. In this case, the system
generates the SYNC_C_LOS alarm. After the SYNC_C_LOS alarm is
cleared, the system clock traces any clock source other than the internal clock
source, and then check whether the CLK_NO_TRACE_MODE alarm is
cleared.
n The synchronous source is degraded. In this case, the system generates the
SYN_BAD alarm. After the SYN_BAD alarm is cleared, the system clock
traces any clock source other than the internal clock source, and then check
whether the CLK_NO_TRACE_MODE alarm is cleared.
n The local station enables the SSM protocol, while the upstream station does
not enable the SSM protocol. In this case, enable the SSM protocol at the
upstream station. When the system clock traces any clock source other than the
internal clock source, the CLK_NO_TRACE_MODE alarm is automatically
cleared. For details, see Configuring the Clock Source Protection in the
Feature Description.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.47 COM_EXTECC_FULL
Description
Number of TCP connections between NEs running the automatically extended ECC protocol
exceeding the system limit.
Attribute
Parameters
None
Possible Causes
The number of TCP connections between NEs running the automatically extended ECC
protocol exceeds the system limit.
Procedure
Step 1 Disable the automatically extended ECC protocol and enable the manually extended ECC
----End
Related Information
A data communication network (DCN) provides communication channels for the NEs that are
managed in a centralized manner to operate and maintain the NEs remotely. For details, see
"Outband DCN" in the Feature Description.
4.48 CRC4_CROSSTR
Description
CRC4 multi-frame bit error count exceeding the threshold. The alarm is generated when the
number of the bit errors in the CRC4 multiframe exceeds the threshold.
Attribute
Parameters
None
Possible Causes
l The configuration of the system clock is incorrect.
l The attenuation of the transmission line is overlarge.
l The receive optical power is overloaded.
Procedure
Step 1 On the U2000, check the clock configuration of the system to ensure that the configuration is
correct.
Step 2 Check whether the input optical power of the board at the local station is within the permitted
range on the U2000. If the optical power is abnormal, take the processing methods of alarms
such as IN_PWR_HIGH or IN_PWR_LOW for troubleshooting.
Step 3 If the services are not affected, check whether the fiber jumper between the FIU board and the
SC2/SC1/ST2 board is extruded. If the fiber jumper is extruded, clean up the routed fiber
jumper. If the fiber jumper is transformed due to the extrusion, replace the fiber jumper.
----End
Related Information
None
4.49 DB_RESTORE_FAIL
Description
Database restoration failure. This alarm is generated when the database fails to be restored.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameters 1 and 2 Indicate that the slot ID of the board whose OCP database fails to be
restored.
Possible Causes
l The database configuration file is lost.
l Data in the database is damaged.
Procedure
Step 1 Back up the database regularly to resolve this problem. Check and test the database in the
backup area to ensure that the database data is complete.
----End
Related Information
None
4.50 DBMS_DELETE
Description
NE database being deleted. This alarm is generated when the NE enters the database deletion
state after a user deletes the NE database from the flash memory of the system control board.
Attribute
Parameters
None
Possible Causes
l A user runs a command to delete the NE database.
Procedure
Step 1 Check whether the NE database is deleted incorrectly. If it is deleted incorrectly, back up the
NE database to the flash memory of the system control board, otherwise, reset the NE.
Step 2 Check whether this alarm is cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.51 DBMS_ERROR
Description
Database error. The alarm is generated when the database is in error.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
The system configuration data may be lost. A failure message may be displayed in response to
certain query or setting commands. The functions of the system may be unavailable.
Possible Causes
l Cause 1: The database operation fails.
l Cause 2: Data in the database is damaged.
l Cause 3: The board is faulty.
Procedure
l Periodically back up the database to resolve this problem. Check and test the database in
the backup area to ensure that the database data is complete.
l The alarm can be repaired automatically, and the database auto-repair function is
available in case of the alarm. If the alarm lasts for more than 2 hours, the auto-repair
function fails. In this case, manually repair the database.
l If only the standby SCC board reports this alarm, you only need to reset the standby SCC
board.
l When only the active SCC board reports this alarm, trigger the active/standby switching
first by means of manual switching. If manual switching fails, trigger the switching by
removing and reinserting the active SCC board. After the switching, reset the standby
SCC board.
l If this alarm is reported by both the active and standby boards and a warm reset can
trigger protection switching, perform the following operations:
a. Reset the active board. The active/standby protection switching is triggered.
b. After the board starts up, preferentially perform manual switching. If manual
switching fails, remove a board to trigger protection switching.
c. After the protection switching succeeds, reset the standby board.
l If this alarm is reported by both the active and standby boards and a warm reset cannot
trigger protection switching, perform the following operations:
a. Reset the active board.
b. When the active board starts up, reset the standby board.
l After the database is repaired, check for the alarm. If the alarm persists, the board
hardware is faulty. In this case, replace the board.
l If the alarm indicates that the board or port data fails to be restored using the database
reconciliation function, check the port status of the boards, and then manually rectify the
failure.
----End
Related Information
None
4.52 DBMS_PROTECT_MODE
Description
Database in the protection mode. This alarm is generated when the NE database is in the
protection mode.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The number of reset times for the NE in 5 minutes crosses the threshold of the protection
mode.
l The NE delivers a command to test the protection mode.
Procedure
Step 1 Check whether the NE database in the protection mode is caused by human factors. If it is
caused by human factors,
l On the U2000, perform a warm or cold reset on the system control board to release the
protection mode.
l Wait for 2 hours. Release the protection mode after the automatic reset.
Step 2 If the alarm persists, replace the faulty board.
----End
Related Information
None
4.53 DBPS_ABNORMAL
Description
The alarm indicates that the DBPS protection group is abnormal. When the DBPS protection
group detects anomalies, the DBPS_ABNORMAL alarm is reported.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameters 1 and 2 Indicate the ID of the protection group in which the alarm is generated.
Parameter 3 Indicates an abnormality of the DBPS protection group. The options are
as follows:
l 0x1 indicates that timeout occurs during the communication
between the active equipment and standby equipment.
l 0x2 indicates that the protection configuration of the active and
standby equipment is incorrect.
l 0x3 indicates that the snooping protocol is abnormal.
l If the protocol communication between the active equipment and the standby equipment
in the DBPS protection group cannot be established, there may be two pieces of active
equipment or standby equipment.
l If the DBPS protection status of the active equipment and standby equipment is
inconsistent, the service protection cannot function properly.
l If the snooping protocol used (VRRP or ARP) detects anomalies, the snooping function
cannot be realized, and therefore the protection status of the active equipment and the
protection status of the standby equipment are incorrect.
Possible Causes
l The protocol communication between the active equipment and the standby equipment is
interrupted. In this case, communication between the protocol interfaces cannot be
established, or the protection configuration on the active equipment and the protection
configuration on the standby equipment are inconsistent.
l The VLAN configuration of the active equipment and the VLAN configuration of the
standby equipment are inconsistent, or the active equipment and standby equipment use
different snooping protocols.
l In the case of the VRRP protocol, the configuration of the DBPS protection group may
be inconsistent with the configuration of the VRRP group of the interconnected routers
or the VRRP groups of the routers interconnected to the active and standby DBPS may
be different.
Procedure
Step 1 Query alarms on the U2000 to determine the ID of the protection group where the alarms are
generated.
Step 2 Check whether the protocol interface of the DBPS protection group is configured properly
and the IDs of the protection groups on the active and standby equipment are consistent. If
there are errors in the configuration, modify the configuration of the protection group.
Step 3 Check whether the VLAN configuration and the snooping protocol on DBPS protection group
are consistent. If not, modify the protection configuration.
Step 4 If the VRRP protocol is used, check whether the configuration of the DBPS protection group
is consistent with the configuration of the VRRP protection in the two interconnected routers.
Note that the DBPS protection group must correspond to the VRRP group. In addition, the
VRRP groups of the routers interconnected to the active and standby DBPS equipment must
be consistent. Otherwise, eliminate the incorrect VRRP configuration of the router, and then
re-configure the DBPS protection group.
----End
Related Information
For details, see "DBPS Protection" in the Feature Description.
4.54 DCM_INSUFF
Description
Insufficient dispersion compensation margin. This alarm is generated when the dispersion
compensation value is close to the limit of the dispersion compensation margin.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the positive or negative dispersion compensation margin. Value 0x00
indicates the positive dispersion compensation margin and value 0x01
indicates the negative dispersion compensation margin.
Possible Causes
The DCM module is not properly configured or is faulty.
Procedure
Step 1 On the U2000, Check whether an OTUk_LOF alarm is reported. If the OTUk_LOF alarm is
reported, clear the alarm according to the proper procedure.
Step 2 If there are no other alarms, query the dispersion compensation value of the board on the
U2000.
l If the dispersion compensation value is large and close to the upper limit of the
dispersion compensation margin, replace the DCM module with a DCM module that has
lower dispersion compensation capabilities.
l If the dispersion compensation value is small and close to the lower limit of the
dispersion compensation margin, replace the DCM module with a DCM module that has
higher dispersion compensation capabilities.
----End
Related Information
Related Cases:
l MC-A240 Isolated Bit Errors Are Found in the Long-Term Bit Error Testing of a 40G
System
4.55 DCNLINK_OVER
Description
The number of DCN OSPF neighbors excesses the suggested threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 l 0x01: Indicates the total number of DCN neighbors exceeds the suggested
threshold.
l 0x02: Indicates the number of DCN OSPF neighbors that are to the same
NE exceeds the suggested threshold.
Possible Causes
l The total number of DCN neighbors exceeds the suggested threshold.
l The number of DCN neighbors communicating with the same NE exceeds the suggested
threshold.
Procedure
Step 1 Check and disable the redundant DCN interfaces on the local NE if the parameter is 0x01.
Step 2 Check and disable the redundant DCN interfaces on the opposite NE if the parameter is 0x02.
----End
Related Information
None
4.56 DCNSIZE_OVER
Description
Number of NEs on a DCN subnet exceeding the setting threshold.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
The DCN subnet contains too many NEs.
Procedure
Step 1 Plan the DCN subnet again based on the actual networking.
----End
Related Information
None
4.57 DERIVED_PWR_ERROR
Description
Optical power exception alarm. This alarm is generated when any of the
SUM_INPWR_LOW, SUM_INPWR_HI, and OA_LOW_GAIN alarms is reported.
Attribute
Alarm Severity Alarm Type
Critical Communication
Parameters
None
Possible Causes
l The input optical power is excessively high.
l The input optical power is excessively low.
l The pump laser may be aged.
l The board that reports this alarm is faulty.
Procedure
Step 1 Check whether the input optical power of the input port of the board at the local station is
within the permitted range by using an optical power meter. If the power is not within the
permitted range, add proper attenuation by placing a fixed attenuator or a VOA.
Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.58 DLAG_PROTECT_FAIL
Description
The DLAG_PROTECT_FAIL is an alarm indicating that the DLAG protection fails. If
negotiation fails or any abnormality occurs during the DLAG protection, the
DLAG_PROTECT_FAIL alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The possible causes of the DLAG_PROTECT_FAIL alarm are as follows:
Procedure
Step 1 View the DLAG_PROTECT_FAIL alarm on the U2000, and determine the board where the
DLAG_PROTECT_FAIL alarm is generated. Determine the ID of the LAG where the
DLAG_PROTECT_FAIL alarm is generated according to Parameters 1 and 2, and determine
the cause of the DLAG_PROTECT_FAIL alarm at the port according to Parameter 3.
Step 2 If the value of Parameter 3 is 0x01, it indicates that the link becomes faulty or fails.
1. On the U2000, check whether the port in the LAG is enabled. If not, enable the port and
then check whether the DLAG_PROTECT_FAIL alarm is cleared.
2. If the DLAG_PROTECT_FAIL alarm persists, check the link state of all the ports.
Rectify the fault of the port link, and then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
Step 3 If the value of Parameter 3 is 0x02, it indicates that the port fails to receive the LACP packets.
1. On the U2000, check whether the LAG is configured at the opposite end, and check
whether the port connected to the faulty port is added to the LAG at the opposite end.
Make sure that the LAG is correctly configured, and then check whether the
DLAG_PROTECT_FAIL alarm is cleared.
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 state. Release the
loop and then check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 6 If the value of Parameter 3 is 0x05, it indicates that the communication between the active and
standby boards times out. Make sure the active and standby boards are in position, and the
communication between them is normal. Then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
Step 7 If the value of Parameter 3 is 0x06, it indicates that the communication between the board and
the cross-connect board and SCC board times out. Make sure that the software of the 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 that the active port
selected by LACP is consistent with the one selected by the cross-connect board, and then
check whether the DLAG_PROTECT_FAIL alarm is cleared.
----End
Related Information
None
4.59 DSP_LOAD_FAIL
Description
The DSP_LOAD_FAIL is an alarm indicating DSP software loading failure. The alarm occurs
when loading the DSP program fails.
Attribute
Parameters
None
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Perform a warm reset on the faulty board on the U2000. For details, see the Supporting Tasks.
Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.60 EFI_TYPE_MISMATCH
Description
Mismatch between the EFI board type and subrack type. This alarm is generated when the
EFI board type mismatches the type of the subrack where the EFI board is inserted.
Attribute
Parameters
None
Possible Causes
The EFI board type mismatches the subrack type.
Procedure
Step 1 Check the subrack type of the current NE and replace the EFI board with an EFI board that
matches the subrack type.
----End
Related Information
None
4.61 ELAN_SMAC_FLAPPING
Description
The ELAN_SMAC_FLAPPING alarm indicates that the source MAC address learned by an
E-LAN service undergoes a transfer. This alarm is reported when two ports on a bridge or VSI
learn the same source MAC address.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 6 Indicate the source MAC address that flaps.
Name Meaning
Parameter 9 Indicates the type of the port that learns the source MAC address
before the flapping occurs.
l 0x00: UNI
l 0x01: NNI
Parameters 10 to 13 Indicate the ID of the UNI or NNI that learns the source MAC address
before the flapping occurs.
Parameter 14 Indicates the type of the port that learns the source MAC address after
the flapping occurs.
l 0x00: UNI
l 0x01: NNI
Parameters 15 to 18 Indicate the ID of the UNI or NNI that learns the source MAC address
after the flapping occurs.
Possible Causes
A possible cause of the alarm is as follows:
Procedure
Step 1 Check for a loopback according to the port and VLAN ID of the E-LAN service.
Step 2 If a loopback exists, set loopback detection on E-LAN services to disable loopback services.
Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.62 ERPS_IN_PROTECTION
Description
This alarm is generated when ERPS (Ethernet Ring Protection Switching) switching is
triggered. It indicates that a node on the ERPS ring is faulty.
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.
Parameter Description
Parameters 3 Indicates the direction of the fault related to the ERPS RPL-OWNER
node on the ERPS ring.
l 0x00 indicates in west.
l 0x01 indicates in east.
Possible Causes
EPRS switching is triggered by a fault on the ERPS ring (for example, bidirectional fiber
cuts).
Procedure
Step 1 Locate the faulty node on the ERPS ring based on the alarm parameter.
Step 2 Locate the ERPS blocked port on the faulty node and handle the fault.
----End
Related Information
None
4.63 ETH_APS_LOST
Description
The ETH_APS_LOST alarm indicates that the automatic protection switching (APS) frames
are lost. This alarm is generated when no APS frame is received by the protection channel.
Attribute
Parameters
None.
The following figure shows the major suppression relationship between the alarm and other
alarms related to the ETH APS protection group.
The alarm above an arrow suppresses the alarm below the arrow. For example, the
ETH_APS_PATH_MISMATCH alarm suppresses the ETH_APS_LOST alarm.
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
ETH_APS_TYPE_ ETH_APS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the ETH_APS_LOST alarm are as follows:
Procedure
Step 1 Cause 1: The opposite NE is not configured with APS protection.
1. On the NMS, check whether the opposite NE is configured with APS protection.
If... Then...
The opposite NE is not configured with APS protection Go to the next step.
The opposite NE is configured with APS protection Go to Step 2.
2. Create a matching APS protection group on the opposite NE, and activate the APS
protocol.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
If... Then...
The APS protocol is disabled Disable the APS protocol on the local NE and then
enable the protocol at both ends.
The APS protocol is enabled Go to Step 3.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
----End
Related Information
None.
4.64 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH alarm indicates that the working and protection paths of
the APS protection group differ between the two ends. This alarm is generated when 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
Parameters
None.
The following figure shows the major suppression relationship between the alarm and other
alarms related to the ETH APS protection group.
The alarm above an arrow suppresses the alarm below the arrow. For example, the
ETH_APS_PATH_MISMATCH alarm suppresses the ETH_APS_LOST alarm.
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
ETH_APS_TYPE_ ETH_APS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the ETH_APS_PATH_MISMATCH alarm are as follows:
l Cause 1: The configured working and protection paths at the two ends differ.
l Cause 2: The physical link is connected incorrectly.
Procedure
Step 1 Cause 1: The configured working and protection paths at the two ends differ.
1. On the NMS, check whether the APS configurations at both ends are consistent. For
example, tunnel 1 is set as the working channel and tunnel 2 is set as the protection
channel at one end, whereas tunnel 1 is set as the protection channel and tunnel 2 is set
as the working channel at the other end. For the same tunnel, one end is the working
channel, the other end is the protection channel, and the working and protection channels
are different.
2. If the APS configurations at both ends are inconsistent, modify the configurations for
them at both ends to be consistent. Then, deactivate and activate the APS protection
groups at both ends. Check whether the alarm is cleared.
3. If the alarm persists, go to Step 2.
----End
Related Information
None.
4.65 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL alarm indicates a protection switching failure. This alarm is
generated 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
Parameters
None.
The following figure shows the major suppression relationship between the alarm and other
alarms related to the ETH APS protection group.
The alarm above an arrow suppresses the alarm below the arrow. For example, the
ETH_APS_PATH_MISMATCH alarm suppresses the ETH_APS_LOST alarm.
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
ETH_APS_TYPE_ ETH_APS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the ETH_APS_SWITCH_FAIL alarm are as follows:
l Cause 1: The configurations of the APS protection group at two ends differ.
l Cause 2: The physical link deteriorates or is connected incorrectly.
Procedure
Step 1 Cause 1: The configurations of the APS protection group at two ends differ.
1. On the NMS, check whether the APS configurations at both ends are consistent. For
example, if the APS protection group is enabled at one end but disabled at the other end,
the other end does not process a received switching request.
2. If the configurations at the two ends are inconsistent, modify the configurations for them
at both ends to be consistent. Then, deactivate and activate the APS protection groups at
both ends.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The physical link deteriorates or is connected incorrectly.
1. Check whether the protection channel reports an alarm related to signal loss or signal
degrade, such as ETH_LOS. If an alarm related to signal loss or signal degrade is
reported, clear the alarm first.
2. Check whether the fiber or cable is connected correctly. If the port on the working
channel is physically connected to the port on the protection channel, one end cannot
receive a switching request from the other end. If the fiber or cable is incorrectly
connected, rectify the fiber or cable connection.
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.66 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH alarm indicates protection scheme mismatch. This alarm
is generated when the information in the received automatic protection switching (APS) frame
is different from the APS protection scheme specified at the local end.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
ETH_APS_TYPE_ ETH_APS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the ETH_APS_TYPE_MISMATCH alarm are as follows:
l Cause 1: The switching types are different.
l Cause 2: The switching directions are different.
l Cause 3: The revertive modes are different.
Procedure
Step 1 On the NMS, check whether the APS configurations at both ends are consistent. For example,
check whether one end is configured with 1+1 protection, but the other end is configured with
1:1 protection.
Step 2 If the configurations at both ends are inconsistent, modify the configurations for them at both
ends to be consistent. Then, deactivate and activate the APS protection groups at both ends.
Step 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.67 ETH_BIP8_SD
Description
The ETH_BIP8_SD is an alarm indicating that the 40GE/100GE signal is degraded.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The optical port at the local end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. If the optical
power is not within the normal range, see the handing procedure of the IN_PWR_HIGH and
IN_PWR_LOW alarms for troubleshooting.
Step 2 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical port 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.
Step 3 If the alarm persists, the board may be faulty. Replace the board.
----End
Related Information
ITU-T G.709
4.68 ETH_CFM_AIS
Description
ETH MEP alarm indication signal. This alarm is generated when an AIS OAM packet is
received, indicating that the ETH at service level is faulty.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter Description
Possible Causes
The upstream NE detects that a fault occurs at the ETH server layer.
Procedure
Step 1 Check whether there is any defect in the ETH server layer between local NE and upstream
NE.
----End
Related Information
None
4.69 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating service connectivity loss. This alarm is reported
when the system does not receive CCM packets from the remote MEP in the 3.5 times of the
continuity check (CC) period.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter Description
Parameters 9 and 10 Indicate the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the CC source maintenance point.
Possible Causes
l Cause 1: The corresponding MEP at the opposite end is not configured correctly.
l Cause 2: The configuration of the Ethernet services that correspond to the MAs of the
MEPs at both ends is incorrect.
l Cause 3: The service transmission line between the MEPs at both ends is interrupted.
l Cause 4: The network is congested seriously.
Procedure
l Cause 1: The corresponding MEP at the opposite end is not configured correctly.
a. Check whether the MEP of the opposite end is configured correctly.
b. Modify the configuration of the MEP to ensure consistency at both ends.
l Cause 2: The configuration of the Ethernet services that correspond to the MAs of the
MEPs at both ends is incorrect.
a. Check whether the configuration of the Ethernet services is correct
If... Then...
l Cause 3: The service transmission line between the MEPs at both ends is interrupted.
a. Check whether the physical links (such as cables or fibers) between the MEPs at
both ends are correct.
If... Then...
The connection is incorrect. Connect the cable properly. Check whether the
alarm is cleared. If the alarm persists, go to the
next step.
If... Then...
The cable connector is loose. Connect the cable connector properly. Check
whether the alarm is cleared. If the alarm
persists, go to the next step.
c. Check whether the cable is pressed, damaged, peeled off, aged, or cut. If the cable is
faulty, replace the cable. Check whether the alarm is cleared. If the alarm persists,
go to case 4.
l Cause 4: The network is congested seriously.
a. Check the bandwidth utilization of the MEPs at both ends. For example, check
whether the FLOW_OVER alarm is reported.
If... Then...
----End
Related Information
None
4.70 ETH_CFM_MACSTATUS
Description
The ETH_CFM_MACSTATUS is a remote MAC defect indication. This alarm indicates that
a continuity check packet carrying a port tlv or an interface tlv is received from a given
remote MEP.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameters 9 and 10 Indicate the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).
Possible Causes
Cause 1: The residential port of the remote MEP encounters a MAC failure.
Procedure
l Cause 1: The residential port of the remote MEP encounters a MAC failure.
a. Check whether the residential port of the remote MEP encounters a MAC failure. If
the failure is detected, rectify it.
----End
Related Information
None
4.71 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating a misconnection. This alarm indicates
that there are misconnections between different maintenance domains (MDs).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Possible Causes
l Cause 1: The level of the MD to which the maintenance end point (MEP) belongs is
incorrectly configured.
l Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
l Cause 3: Certain physical links are incorrectly connected.
Procedure
l Cause 1: The level of the MD to which the MEP belongs is incorrectly configured.
a. Check whether the level of the maintenance point on the service is correctly
configured. If the level is incorrectly configured, change the level so that the level is
correct.
l Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
a. If the alarm persists, check whether the MD/MA names configured at the source
and sink ends are consistent. If not, modify them to the same, and then check
whether the alarm is cleared.
l Cause 3: Certain physical links are incorrectly connected.
a. If the alarm persists, check whether physical links are misconnected. If yes,
reconnect the fiber or line, and then check whether the alarm is cleared.
----End
Related Information
None
4.72 ETH_CFM_RDI
Description
The ETH_CFM_RDI is a remote CFM_OAM alarm indication. This alarm is generated at the
local end when the CFM_OAM fault is generated at the remote end. This alarm indicates that
at least one continuity check message (CCM) packet with the RDI indication is received.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter Description
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).
Possible Causes
Cause 1: The opposite equipment detects a fault.
Procedure
l Cause 1: The opposite equipment detects a fault.
a. Check whether ETH alarms exist on the opposite equipment, and then rectify the
fault according to the alarms.
----End
Related Information
None
4.73 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating error frames. This alarm is reported when
the system receives invalid CCM packets.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Possible Causes
l Cause 1: The cycles of the continuity check (CC) of the MEPs at both ends are different.
l Cause 2: The IDs of the MEPs at both ends conflict with each other.
l Cause 3: Loopback occurs in the service, and loopback packets are received.
Procedure
l Cause 1: The cycles of the continuity check (CC) of the MEPs at both ends are different.
a. Check whether the CCM periods that are configured on the MEPs at both ends are
consistent. If the CCM periods are inconsistent, change the configuration so that the
CCM periods are consistent.
l Cause 2: The IDs of the MEPs at both ends conflict with each other.
a. If the alarm persists, check whether the same MEP IDs are used in the MD to which
the MEPs of the stations belong. If the same MEP IDs are used, delete the repeated
MEP ID and create another MEP ID so that no MEP ID conflict exists in the MD.
l Cause 3: Loopback occurs in the service, and loopback packets are received.
a. If the alarm persists, check whether there are service loops in the MDs to which the
MEPs of the service belong. If there are service loops, release the service loops.
----End
Related Information
None
4.74 ETH_EFM_DF
Description
The ETH_EFM_DF alarm indicates discovery failure. This alarm is generated when the
negotiation of the P2P OAM protocol fails at a port.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Possible Causes
The possible causes of the ETH_EFM_DF alarm are as follows:
l Cause 1: Hardware equipment on the local end, such as the optical module, boards, or
physical link, is faulty.
l Cause 2: No OAM packet is received at the local end within a specified period.
l Cause 3: The OAM settings of one end do not meet the requirements of the other end.
Procedure
l Cause 1: Hardware equipment on the local end, such as the optical module, boards, or
physical link, is faulty.
a. On the NMS, check whether there are hardware-related alarms at the local end, such
as HARD_BAD and LSR_NO_FITED. If such alarms exist, clear these alarms.
Check whether the ETH_EFM_DF alarm is cleared.
b. If the alarm persists, check whether the optical fiber or Ethernet cable between the
local NE and the opposite NE is faulty. If the optical fiber or Ethernet cable is
faulty, replace the faulty optical fiber or Ethernet cable. Check whether the alarm is
cleared.
Related Information
None.
4.75 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT alarm indicates that an event occurs on the opposite NE. This alarm
is generated when the P2P OAM protocol is enabled and the local end receives an event
indication from the opposite end.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 a link event.
l 0x01: Indicates the errored symbol period.
l 0x02: Indicates the errored frames.
l 0x03: Indicates the errored frame period.
l 0x04: Indicates the errored frame seconds.
Possible Causes
The possible causes of the ETH_EFM_EVENT alarm are as follows:
l Cause 1: Boards at the two ends work improperly.
l Cause 2: The physical link between the two ends is faulty.
Procedure
l Cause 1: Boards at the two ends work abnormally.
a. On the NMS, check whether the opposite NE or the local NE reports any alarms
that are related to the hardware of the 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.
b. If the alarm persists, go to Cause 2.
l Cause 2: The physical link between the two ends is faulty.
a. Check whether the optical fiber or Ethernet cable between the local NE and the
opposite NE is faulty. If yes, replace the faulty optical fiber or Ethernet cable.
----End
Related Information
None.
4.76 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK alarm indicates a loopback. This alarm is generated when the
P2P OAM protocol is enabled and the local end initiates a loopback request or responds to the
loopback request initiated by the opposite end. If the ports at both ends can respond to a
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,
and the opposite port reports the alarm indicating the initiation of a 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,
and the opposite port clears the alarm indicating the initiation of a loopback.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 status.
Possible Causes
The possible causes of the ETH_EFM_LOOPBACK alarm are as follows:
l Cause 1: The local port initiates a loopback request and the opposite port responds to the
request.
l Cause 2: The opposite port initiates a loopback request and the local port responds to the
request.
Procedure
l Cause 1: The local port initiates a loopback request and the opposite port responds to the
request.
a. On the NMS, query the alarm information and locate the port that reports the alarm.
b. Set Remote Side Loopback Response of the port to Disabled.
l Cause 2: The opposite port initiates a loopback request and the local port responds to the
request.
a. On the NMS, query the alarm information of the opposite NE and locate the port
that reports the alarm.
b. Set Remote Side Loopback Response of the port to Disabled.
----End
Related Information
None.
4.77 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT alarm indicates that the opposite NE is faulty. This alarm is
generated when the P2P OAM protocol is enabled and the local end receives a fault indication
from the opposite end.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Possible Causes
The possible causes of the ETH_EFM_REMFAULT alarm are as follows:
l Cause 1: The opposite port is faulty.
l Cause 2: A board on the opposite NE works improperly.
l Cause 3: The physical link between the two ends is faulty.
Procedure
l Cause 1: The opposite port is faulty.
a. On the NMS, check whether the opposite port reports the ETH_LOS or
ETH_LINK_DOWN alarm. If yes, clear these alarms first. Check whether the
ETH_EFM_REMFAULT alarm is cleared.
b. If the alarm persists, go to Cause 2.
l Cause 2: A board on the opposite NE works improperly.
a. On the NMS, check whether the opposite NE reports alarms that are related to the
hardware of the optical modules or boards, such as HARD_BAD and
LSR_NO_FITED. If yes, clear these alarms first. Then, check whether the
ETH_EFM_REMFAULT alarm is cleared.
b. If the alarm persists, go to Cause 3.
l Cause 3: The physical link between the two ends is faulty.
a. Check whether the optical fiber or Ethernet cable between the two ends is faulty. If
yes, replace the faulty optical fiber or Ethernet cable.
----End
Related Information
None.
4.78 ETH_HI_BER
Description
The ETH_HI_BER is an alarm indicating that the number of 40GE/100GE signal bit errors
exceeds the preset threshold. This alarm is generated when the number of 40GE/100GE signal
bit errors exceeds the preset threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The attenuation of the received signals is excessively large and the fiber of the
transmission line is abnormal.
l The transmit part of the opposite site is faulty.
l The receive part of the local site is faulty.
Procedure
Step 1 Check whether the receive optical power of the port is within the permitted range on the
U2000. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the receive optical power of the board at the
local site is excessively low, clear the alarm according to the handling procedure of the
IN_PWR_LOW alarm.
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding port on
the upstream board is within the permitted range on the U2000. For the optical power
specifications of the specific board, see "Technical Specifications" in the Product Description.
If the transmit optical power of the board at the upstream site is excessively low, clear the
alarm according to the handling procedure of the OUT_PWR_LOW alarm.
Step 3 If the alarm persists, check whether the bit error alarm (for example, ETH_HI_BER or
ETH_BIP8_SD) exists at the upstream site on the U2000. If the bit errors exist, clear the bit
error fault of the upstream site.
Step 4 If the alarm persists, replace the faulty board at the local site.
----End
Related Information
ITU-T G.709
4.79 ETH_LINK_DOWN
Description
Failure of network interface connection.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The working modes of the transmit and receive ports are inconsistent and the negotiation
fails.
l The link is faulty.
l The cable or fiber is incorrectly connected or the opposite equipment is faulty.
Procedure
Step 1 View the alarm on the NMS to determine the board that reports the alarm. Then, determine
the number of the port on the board that reports the alarm.
Step 2 Check whether the working mode of the local port is consistent with that of the opposite port.
If not, change the modes to the same, and then check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the cable or fiber connection is faulty. If yes, recover the
cable or fiber connection, and then check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the opposite equipment is faulty. If yes, replace the faulty
board at the opposite station, and then check whether the alarm is cleared.
Step 5 If the alarm persists, replace the board that reports the alarm and verify that the working
modes of the ports at the local station and opposite station are consistent. Then the alarm is
cleared.
----End
Related Information
None
4.80 ETH_LOS
Description
The ETH_LOS is an alarm indicating the loss of network connection. This alarm is generated
when the Ethernet port fails to receive any Ethernet signal.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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. The value ranges
vary depending on boards.
In the case of packet processing boards and packet interface boards,
no parameters are available.
Parameter 2 and Parameter 2 is always 0x00, and Parameter 3 is always 0x01. These
Parameter 3 parameters are meaningless.
If this topic does not describe the common fault symptom or the actual fault symptom is not contained in
the description of the common fault symptom, handle the ETH_LOS alarm by following the steps
provided in Handling Procedure.
None.
Possible Causes
The possible causes of the ETH_LOS alarm are as follows:
l Cause 1: The port is enabled, but no signal is received from the client side.
l Cause 2: The working mode of the local port does not match the working mode of the
opposite port.
l Cause 3: The port is enabled, but the network cable or fiber is connected incorrectly or
faulty.
l Cause 4: The opposite board is faulty.
l Cause 5: The local board is faulty.
Procedure
Step 1 On the NMS, check the alarms. Determine the port that reports the alarm according to the
alarm parameters.
Step 2 Cause 1: The port is enabled, but no signal is received from the client side.
1. If the services on the Ethernet port are deleted but the Ethernet port is still Enabled, the
ETH_LOS alarm may be reported. Check whether the port accesses signals from the
client side and whether the port is enabled.
2. If the services at the port are deleted, configure services properly. If the port is no longer
required, disable the port.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: The working mode of the local port does not match the working mode of the
opposite port.
1. Query the working modes of the interconnected ports. Determine whether the ports
support the auto-negotiation mode, and then select a proper working mode.
2. Ensure that the working modes of the interconnected ports are consistent. Then, check
whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 3: The port is enabled, but the network cable or fiber is connected incorrectly or faulty.
1. Check whether the port where the alarm is reported is connected correctly to the network
cable or fiber. If the port is connected incorrectly to the network cable or fiber, connect
the port to the network cable or fiber correctly according to the requirements of the
actual network. Then, check whether the alarm is cleared.
2. Check whether the network cable or fiber jumper at the port is loose. If yes, install the
network cable or fiber jumper correctly. Check whether the alarm is cleared.
3. In the case of an optical port, check whether the fiber connector is dirty. If the fiber
connector is dirty, clean it immediately. Check whether the alarm is cleared.
4. If the alarm persists, exchange the cables or fibers to locate the fault. If the cable or fiber
is faulty, the Ethernet services may be interrupted. Replace the cable or fiber which may
be faulty with a good one. Check whether the alarm is cleared.
5. Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Cause 4: The opposite board is faulty.
If... Then...
1. In the case of an optical port board, check whether the transmit optical power of the
opposite board is within the permitted range on the NMS. For the optical power
If... Then...
The transmit optical power on the Replace the relevant board. Replace the
opposite NE is abnormal board. Check whether the alarm is cleared. If
the alarm persists, go to Step 6.
2. In the case of an electrical interface board, check whether the transmit optical power of
the local board is within the permitted range on the NMS.
If... Then...
3. In the case of an electrical interface board, check whether the board reports the alarms
indicating the fault of the board or chip, such as HARD_BAD.
If... Then...
None of the preceding alarms is reported Exchange the boards to locate the fault.
4. If the Ethernet board works with an interface board, replace the interface board first. If
the Ethernet board does not work with any interface board, replace the processing board.
Replace the board. Check whether the alarm is cleared. If the alarm persists, go to Step
6.
Step 6 Cause 5: The local board is faulty.
1. If the Ethernet board works with an interface board, replace the interface board first. If
the Ethernet board does not work with an interface board, replace the processing board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
If the negotiated mode of the Ethernet ports is half duplex, signals are transmitted in one
direction at the same time. As a result, the data transmission performance degrades greatly.
When the service traffic is low, packet loss occurs at the interconnected ports. When the
service traffic is high, services are interrupted.
4.81 ETH_MISCONNECT
Description
ETH_MISCONNECT is an alarm indicating an incorrect connection between network
interfaces. This alarm indicates that the LAN cable for connecting subracks is incorrectly
connected.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is
connected to a subrack.
Procedure
l Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is
connected to a subrack.
a. Check whether the ETH3 interface is connected to a subrack. If the ETH3 interface
is connected to a subrack, modify the network condition and disconnect the ETH3
interface from the subrack.
----End
Related Information
None.
4.82 ETH_NO_FLOW
Description
Ethernet port traffic alarm. This alarm is generated when there is no traffic at an Ethernet port.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 at an Ethernet port is interrupted.
For example, 0x00 indicates the receive direction and 0x01 indicates the
transmit direction.
Possible Causes
l The Ethernet port is enabled and linked up, but it is not configured with any services.
l The Ethernet port is enabled and linked up, but the local services are abnormal or no
packets are transmitted from the local port.
l The port is enabled and linked up, but the opposite end is abnormal or no packets are
transmitted to the local end.
Procedure
Step 1 Check whether services are configured at the port where the alarm is generated.
Step 2 Query alarm parameters on the U2000 and determine the traffic interruption direction. If
traffic is interrupted in the transmit direction, check whether services at the local NE are
normal. If the services at the local NE are abnormal, handle the alarm with reference to the
procedure for handling other alarms.
Step 3 If traffic is interrupted in the receive direction, check whether an exception occurs at the peer
NE and handle the alarm accordingly.
----End
Related Information
None
4.83 ETH_SERVICE_CONFIG_FAIL
Description
Ethernet service configuration failure alarm.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameters 1 and 2 Indicate the service ID. A link conflicting with DBPS is invisible to
users and the value of this parameter for such a link is 0xff 0xff
(invalid).
Parameters 3 and 4 Indicate the ingress port CVLAN ID. 0xff 0xff: No ingress port
CVLAN is available.
Parameters 5 and 6 Indicates the ingress port SVLAN ID. 0xff 0xff: No ingress port
SVLAN is available.
Parameter 7 Indicates the protection type. 0x00: LAG. 0x0a: DBPS. 0xff: No
protection is available.
Possible Causes
Cause 1: The Ethernet service fails to be configured due to resource conflict.
Procedure
l Cause 1: The Ethernet service fails to be configured due to resource conflict.
a. On the U2000, view the alarm parameters. If the value of parameter 7 is 0xff,
determine the service ID based on parameters 1 and 2 and delete the service
mapping. Then create the service again by using another VLAN or port.
b. If the value of parameter 7 is 0x00 (LAG), determine the service ID based on alarm
parameters 1 and 2 and delete the service mapping the service ID, or determine the
protection group ID based on alarm parameter 8 and delete the LAG protection
group mapping the protection group ID. Then create the service again by using
another port or VLAN.
c. If the value of parameter 7 is 0x01 (DBPS), determine the protection group ID
based on alarm parameter 8 and delete the southbound port of the DBPS protection
group or delete the DBPS protection group. Then, create the southbound port of the
DBPS protection group by using another port.
----End
Related Information
None.
4.84 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating the point-to-point Ethernet OAM
discovery failure. When the OAM protocol is enabled at the port of a board and the
negotiation with the opposite equipment fails, this alarm is generated.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l A link fault occurs at the local end.
l The local end fails to transmit the OAM message.
l The local end fails to receive the OAM message in a specified time.
l The OAM configurations of the opposite end do not meet the requirements of the local
end.
l The OAM configurations of the local end do not meet the requirements of the opposite
end.
Procedure
Step 1 View the ETHOAM_DISCOVER_FAIL alarm on the U2000 and determine the possible
causes of the alarm according to Parameter 1.
Step 2 When Parameter 1 is 0x01, it indicates that a link fault occurs at the local end. Query the
board-level alarms on the U2000. Then remove the fault according to the specific link alarms
such as LINK_ERR and L_SYNC.
Step 3 When Parameter 1 is 0x02, it indicates that the local end fails to transmit the OAM message.
View the printed information about the serial port. The DSSP, drive, and microcode
components are involved in the problem. The fault location needs the assistance of engineers
on related project teams.
Step 4 When Parameter 1 is 0x03, it indicates that the local end fails to receive the 3ahOAM
message from the opposite end in a user-defined time.
1. Check whether the MAC addresses of the interconnected ports are the same. If yes, set
different MAC addresses for the interconnected ports. Then check whether the alarm is
cleared.
2. Check whether the 3ahOAM protocol is enabled at the opposite end. If not, enable the
protocol at the opposite end. Then check whether the alarm is cleared.
3. If the alarm persists, the local end fails to receive the OAM message. Replace the board.
For details, see the Parts Replacement.
Step 5 When Parameter 1 is 0x04, it indicates that the OAM configurations of the opposite end,
including link event reporting capability and unidirectional operation capability, do not meet
the requirements of the local end. Query and modify the configurations of the opposite port on
the U2000. When the configurations meet the requirements of the local end, the alarm is
automatically cleared.
Step 6 When Parameter 1 is 0x05, it indicates that the OAM configurations of the local end do not
meet the requirements of the opposite end. Query and modify the configurations of the local
port on the U2000. When the configurations meet the requirements of the opposite end, the
alarm is automatically cleared.
----End
Related Information
None
4.85 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs on the
remote end of point-to-point Ethernet OAM. When the port with the OAM protocol enabled
receives the OAM message that contains critical fault information from the opposite end, this
alarm is generated.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
to services. This alarm indicates that the signal loss alarm is generated at the receive end of
the opposite port.
Possible Causes
The port with the OAM protocol enabled receives the OAM message that contains critical
fault information from the opposite end, such as a link fault or power failure.
Procedure
Step 1 If a link fault occurs at the opposite port, query board-level alarms on the U2000. Remove the
fault according to the specific link alarms such as L_SYNC and LINK_ERR. Check whether
the alarm is cleared.
Step 2 If irrecoverable problems such as a power failure occur at the opposite end, handle the
problems. The alarm is automatically cleared.
----End
Related Information
None
4.86 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating the remote loopback of the point-to-point
Ethernet OAM. This alarm only occurs at the port with the point-to-point OAM protocol
enabled. If the port is able to respond to loopback, it enters the loopback response state and
reports the loopback response alarm after it receives the remote loopback enabling command
sent by the opposite OAM port. The loopback initiation end reports the loopback initiation
alarm. If the port receives the loopback disabling command, it exits the loopback response
state and ends the loopback response alarm. The loopback initiation end also ends the
loopback initiation alarm.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l A command is issued to enable the loopback at the local port, and the opposite end is the
loopback response end.
l A command is issued to enable the loopback at the opposite port, and the local end is the
loopback response end.
Procedure
Step 1 Disable the loopback. The ETHOAM_RMT_LOOP alarm is automatically cleared.
----End
Related Information
None
4.87 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating the remote SD of the point-to-point Ethernet
OAM. When the port with the OAM protocol enabled receives the link event message from
the opposite end which indicates that the remote Ethernet performance is degraded, this alarm
occurs.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The port with the OAM protocol enabled receives the link event message from the opposite
end.
Procedure
Step 1 Improve the link performance at the opposite end so that the opposite end does not send link
event messages to the local end. Then, the ETHOAM_RMT_SD alarm at the local end is
automatically cleared.
Step 2 Adjust the link performance monitoring threshold at the opposite end. Then the
ETHOAM_RMT_SD alarm at the local end is automatically cleared.
Step 3 Disable the link event reporting at the opposite end. Then the ETHOAM_RMT_SD alarm at
the local end is automatically cleared.
----End
Related Information
None
4.88 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating loopback of the MAC port that receives
the OAM protocol packets in a point-to-point manner. If the MAC port of a board receives the
OAM protocol packets sent by itself or the board after detection of the loop is enabled, the
ETHOAM_SELF_LOOP alarm is reported.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Self-loop is performed for the port with a fiber.
l Loopback is set among ports of the board.
l The PHY/MAC loopback of the port is manually set.
Procedure
Step 1 Check whether the transmit and receive ends of the port are connected with a fiber. If yes,
connect the fiber correctly, and then check whether the ETHOAM_SELF_LOOP alarm is
cleared.
Step 2 If the ETHOAM_SELF_LOOP alarm persists, check whether the transmit and receive ends of
the port are connected to those of other ports with fibers. If yes, connect the fibers correctly,
and then check whether the ETHOAM_SELF_LOOP alarm is cleared.
Step 3 If the ETHOAM_SELF_LOOP alarm persists, check whether any PHY/MAC-layer loopback
is set for the port. If yes, release the loopback, or wait for 5 minutes until the U2000
automatically releases the loopback. Then check whether the ETHOAM_SELF_LOOP alarm
is cleared.
----End
Related Information
None
4.89 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP is an alarm indicating the loopback of the VCTRUNK
port that receives the OAM protocol packets in a point-to-point manner. If the VCTRUNK
port of a board receives the OAM protocol packets sent by itself or the board after detection
of the loop is enabled, the ETHOAM_VCG_SELF_LOOP alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The links of the VCG port is configured with a self-loop.
l The links between VCG ports of the board is configured with a loop.
l The port is configured with a loopback at the PHY/MAC layer manually.
Procedure
Step 1 Check the ETHOAM_VCG_SELF_LOOP alarm on the U2000, and determine the VCG port
number according to Parameters 1 and 2.
Step 2 Check the link configuration of the VCG port to see whether the transmit and receive
directions of the port are connected. Ensure that the link configuration is correct, and then
check whether the ETHOAM_VCG_SELF_LOOP alarm is cleared.
Step 3 If the ETHOAM_VCG_SELF_LOOP alarm persists, check the link configuration of the VCG
port to see whether this VCG port is connected to another VCG port on the board in the
transmit and receive directions. Make sure that the link configuration is correct. Then, the
ETHOAM_VCG_SELF_LOOP alarm is cleared.
Step 4 If the alarm persists, check whether the port is configured with a loopback at the PHY/MAC
layer. If the loopback exists, release it manually.
----End
Related Information
None
4.90 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the maintenance point (MP) ID
conflict. This alarm is reported when an MP receives the message sent by another MP with
the same MP ID in a maintenance domain.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameters 1 and 2 Indicate the number of the Ethernet port where the alarm is generated.
Parameter Description
Parameters 6 to 9 Indicate the ID of the MP where the alarm occurs. The highest byte
indicates the network ID. The second highest byte indicates the node ID
of the network. The lower two bytes indicate the identifier of the MP on
the network node.
The MP should be unique network-wide. Each node supports a
maximum of 1024 MPs. The local MP ID is the same as the MP ID of
the CC sink node..
Possible Causes
Multiple MPs with the same MPID are created in a maintenance domain.
Procedure
Step 1 View the EX_ETHOAM_MPID_CNFLCT alarm on the U2000 and confirm the ID of the
relevant MP according to the alarm parameters.
Step 2 Query the information about the MP. Delete all the MPs that repeat the MPID. Then, the
alarm is automatically cleared.
----End
Related Information
None
4.91 EXT_MODULE_OFFLINE
Description
Extended wavelength module offline. This alarm is generated when a user has configured
services on the channel corresponding to an extended module, but the physical extended
module is offline.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
A user has configured services on the channel corresponding to the extended module, but the
physical extended module is offline.
Procedure
Step 1 Check whether services on the channel corresponding to the extended module are necessary.
Step 2 If the services are necessary, check whether an extended module is properly installed. If the
extended module is properly installed, replace it with a new one.
----End
Related Information
None
4.92 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm is
generated when the system detects the loss of the external clock source traced by the
equipment.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the subrack where the clock board is located.
Name Meaning
Parameter 2 l When ports are cascaded, this parameter indicates the ID of the slot where
the board is located.
l When ports are not cascaded, the value is always 0xf0.
Possible Causes
The possible causes of the EXT_SYNC_LOS alarm are as follows:
l Cause 1: The physical port for the external clock source loses signals.
l Cause 2: The input and output modes of the external clock source are inconsistent.
l Cause 3: The clock input cable is incorrectly connected.
l Cause 4: The clock board is faulty.
Procedure
l Query alarms on the U2000. Determine the ID of the subrack where the clock loss occurs
and which clock is lost according to the alarm parameters.
l Cause 1: The physical port for the external clock source loses signals.
a. Check whether the output signals of the external clock equipment are normal. If not,
replace the faulty external clock equipment, and then check whether the alarm is
cleared.
l Cause 2: The input and output modes of the external clock source are inconsistent.
a. If the alarm persists, check whether the input and output modes of the external
clock source are consistent. After the input and output of the external clock source
are set to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is
cleared. For details, see Configuring Physical Clock in the Feature Description.
l Cause 3: The clock input cable is incorrectly connected.
a. If the alarm persists, check whether the clock input cable is correctly connected. If
not, ensure the correct connection of the clock input cable, and then check whether
the alarm is cleared. For details, see the Quick Installation Guide of the applicable
equipment.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.93 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm indicating the loss of the external time source. This alarm
is generated when the board does not detect the external timing signal after the external timing
port is enabled.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located.
Parameter 2 l When ports are cascaded, this parameter indicates the ID of the slot where
the board is located.
l When ports are not cascaded, the value is always 0xf0.
Possible Causes
The possible causes of the EXT_TIME_LOC alarm are as follows:
l Cause 1: The physical port for the external time source loses signals.
l Cause 2: The timing input cable is incorrectly connected.
l Cause 3: The clock board is faulty.
Procedure
l Query alarms on the U2000. Determine the number of the subrack where the external
timing loss occurs and which external time source is lost according to the alarm
parameters.
l Cause 1: The physical port for the external time source loses signals.
a. Check whether the output signals of the external timing equipment are normal. If
not, replace the faulty external timing equipment, and then check whether the alarm
is cleared.
l Cause 2: The timing input cable is incorrectly connected.
a. If the alarm persists, check whether the timing input cable is correctly connected. If
not, ensure the correct connection of the timing input cable, and then check whether
the alarm is cleared. For details, see "Installing and Routing Clock Cables" in the
Quick Installation Guide of the applicable equipment.
l Cause 3: The clock board is faulty.
a. If the alarm persists, perform a cold reset on the clock board, and then check
whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board"
in the Supporting Tasks.
b. If the alarm persists, replace the clock board. For details, see "Replacing the Clock
Board" in the Parts Replacement.
----End
Related Information
For details, see "IEEE 1588v2" in the Feature Description.
4.94 FAN_FAIL
Description
Fan failure. This alarm is generated when two or more fans fail.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The fans stop running.
l The speed of the fans is excessively low.
l The fans fail.
Procedure
Step 1 On the U2000, check whether FAN Speed Level is set to Stop or Low Speed. If it is, set
FAN Speed Level to High Speed. For details, see "Setting the Speed Level of Fans".
Step 2 If the alarm persists, replace the faulty fan tray assembly.
----End
Related Information
None
4.95 FAN_FAULT
Description
Fan fault. This alarm is generated when a fan fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l One fan fails.
l The logical inspection fails.
Procedure
Step 1 Replace the fan tray assembly.
----End
Related Information
None
4.96 FC_8B10BERR_OVER
Description
The FC_8B10BERR_OVER is an alarm indicating that the 8B10B bit errors in the FC
services cross the threshold. When the 8B10B bit errors in the FC services cross the threshold,
this alarm is generated.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
There are bit errors on the link, which causes the 8B10B bit errors on the ports of the FC link
layer after decoding cross the threshold.
Procedure
Step 1 Check whether there is dust on the optical fiber connector or the fiber is aged. If it is, clean
the optical fiber connector or replace the fiber.
Step 2 Check whether the input optical power of the board is within the permitted range. If the
optical power is abnormal, see the handing procedures for the IN_PWR_HIGH and
IN_PWR_LOW alarms to clear the alarm.
----End
Related Information
None
4.97 FC_AIS
Description
The FC_AIS is an FC service alarm indication signal. This alarm is reported when client-side
input signals contain an FC_AIS signal or the local device fails to receive signals.
Attribute
Major Service
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: Client-side input signals contain an FC_AIS signal.
l Cause 2: The peer board sends an FC_AIS signal.
Procedure
l On the U2000, check whether the board has an alarm with a higher severity. If yes,
handle the alarm with the higher severity.
l On the U2000, check whether the peer board reports an alarm such as R_LOS or R_LOF
on the client side. If yes, check the peer device.
l On the U2000, check whether a loopback is set for the upstream site. If yes, cancel the
loopback on the upstream site.
l Check whether the cross-connection configurations on the upstream site are correct. If
no, modify the configurations.
----End
Related Information
None
4.98 FCS_ERR
Description
The FCS_ERR is an alarm indicating that the frame check sequence (FCS) is incorrect. At the
local site, perform an FCS check for the received frames encapsulated in the GFP format. If
any error occurs in the check, the alarm is reported.
NOTE
The alarm is generated only when GFP services are received at the local site.
This is because the IDLE frame lacks the FCS field, if the IDLE frame is encapsulated in the GFP
format, the FCS check errors may occur.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the FCS_ERR alarm are as follows:
l Cause 1: Mapping protocols of the local site and opposite site are inconsistent. For
example, the local site uses the GFP encapsulation protocol whereas the opposite site
uses the LAPS encapsulation protocol. Or the parameter settings of the protocol are
inconsistent. For example, both sites use the GFP encapsulation but Extension Header
Option of the local site is set to Yes whereas Extension Header Option of the opposite
site is set to No.
l Cause 2: There are bit errors on the link.
l Cause 3: The optical connector of the Ethernet board at the optical port is loose or dirty.
l Cause 4: The board is faulty.
Procedure
l Query current alarms on the U2000. Determine the number of the VCTRUNK that
reports the alarm.
l Cause 1: The encapsulation protocols adopted by the local site and the opposite site are
inconsistent or the settings of the protocol parameters are inconsistent.
a. Check whether the encapsulation protocols of corresponding VCTRUNK ports of
the local site and the opposite site are consistent and whether the parameter settings
of the protocols are consistent. For example, check whether the settings of the
parameters such as Scramble and Set Inverse Value for CRC about the protocols
are the same. For details, see the Configuration Guide. Then, check whether the
alarm is cleared.
b. If the alarm persists, see Cause 2.
l Cause 2: There are bit errors on the link.
a. Check the network-wide alarms on the U2000. For operations, see the Routine
Maintenance. Check whether there are bit error alarms such as B3_EXC and
B3_SD on the link. If these alarms occur, clear these alarms according to
corresponding procedures. Then, check whether the alarm is cleared.
b. If the alarm persists, see Cause 3.
l Cause 3: The optical connector of the Ethernet board at the optical port is loose or dirty.
a. Check whether the connector of the fiber is normal. If the connector is loose,
tighten the connector.
b. Check whether the connector is contaminated. If the connector is contaminated,
clean it immediately. For the operations, see the Supporting Task.
c. If the attenuation value of the optical attenuator is improper, increase or decrease it
to a proper value. The value of the optical attenuator is set according to the receive
optical power of the board. For optical power specifications of boards, see Product
Description. For operations of adjusting the optical attenuator, see Part
Replacement. For operations of querying the optical power, see Supporting Task.
NOTE
From Supporting Task or Hardware Description, you can obtain the manufacturer
information of the optical module on the board.
d. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
l Cause 4: The board is faulty.
a. After the preceding causes are excluded, if the alarm persists, the board where the
alarm is reported is faulty. In the case of the Ethernet board with an interface board,
replace the interface board first. In the case of the board without an interface board,
replace the faulty board. For details, see Parts Replacement.
----End
Related Information
None
4.99 FDBSIZEALM_ELAN
Description
The FDBSIZEALM_ELAN alarm indicates that items listed in an E-LAN forwarding table
are all used. This alarm is generated when the number of actual items in the MAC address
table for the E-LAN service is greater than Address Detection Upper Threshold. This alarm
is cleared automatically when the number of items in the MAC address table of the E-LAN
service is lower than Address Detection Upper Threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the FDBSIZEALM_E-LAN alarm are as follows:
Procedure
l Cause 1: The value of Address Detection Upper Threshold is excessively small.
a. On the NMS, check whether the value of Address Detection Upper Threshold is
excessively small.
b. If yes, set the parameter to a larger value based on actual situations. Check whether
the alarm is cleared. If the alarm persists, go to Cause 2.
l Cause 2: The E-LAN service is attacked.
a. On the NMS, modify the settings so that the E-LAN service discards unknown
packets.
----End
Related Information
None.
4.100 FEATURE_WITHOUT_LICENSE
Description
Service without license. This alarm is generated when a license-controlled feature is used but
the license for the feature is not installed.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
A license-controlled feature is used but a license for the feature is not installed. The possible
causes why the feature is not authorized are as follows:
l A license for this feature is not purchased.
l The license file does not match ESN or V/R version, and the system has been operating
for more than 60 consecutive days.
l The trial period of the license-controlled feature has expired, and the keepalive period of
60 days has also elapsed since the expiration.
Procedure
Step 1 Load a correct license file to the system so that the license-controlled feature is authorized, or
delete the service of unauthorized feature.
----End
Related Information
None
4.101 FEC_LOF
Description
The FEC_LOF is an alarm indicating FEC frame loss. The alarm occurs when the FEC frame
is lost.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l The cable is faulty, or the optical power is improper.
l The service rate is incorrect.
l The clocks on the NEs are out of synchronization.
l The board hardware is faulty.
l Certain problems are found in the services from the opposite end.
Procedure
Step 1 Query the FEC_LOF alarm on the U2000 to determine the relevant board.
Step 2 Query the receive optical power of the board on the U2000. If the receive optical power is
excessively low, clean the fiber header and connector. If the receive optical power is
excessively high, provide more optical attenuators. After verifying that the receive optical
power is proper, check whether the FEC_LOF alarm is cleared.
Step 3 If the alarm persists, check whether the upstream service is the FEC service at the same rate.
If not, configure the FEC service at a correct rate, and then check whether the FEC_LOF
alarm is cleared.
Step 4 If the alarm persists, check whether the upstream service is supported by the board. If not,
configure a correct service, and then check whether the FEC_LOF alarm is cleared.
Step 5 If the alarm persists, check whether the clocks on the local NE and the opposite NE are
synchronous with those on the network. If not, set the clock tracing function, and then check
whether the FEC_LOF alarm is cleared.
Step 6 If the alarm persists, the board hardware may be faulty. Replace the board that reports the
alarm at the local site.
Step 7 If the alarm persists, the board at the opposite site may be faulty. In this case, replace the
board at the opposite site.
----End
Related Information
None
4.102 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out of frame.
Attribute
Parameters
None
Possible Causes
l The fiber is faulty, or the optical power is improper.
l Excessive bit errors occur during transmission.
l The clocks on the NEs are out of synchronization.
l The transmit unit at the opposite end is faulty.
Procedure
Step 1 Query the FEC_OOF alarm on the U2000 to determine the relevant board.
Step 2 Query the receive optical power of the board on the U2000. If the received optical power is
excessively low, clean the fiber header and the connector. If the receive optical power is
excessively high, provide more optical attenuators. After verifying that the receive optical
power is proper, check whether the FEC_OOF alarm is cleared.
Step 3 If the alarm persists, check the transmit optical power at the opposite end. If the transmit
optical power is excessively low, replace the board at the opposite end.
Step 4 If the alarm persists, check whether the clocks on the local NE and the opposite NE are
synchronous with those on the network. If not, set the clock tracing function, and then check
whether the FEC_OOF alarm is cleared.
Step 5 If the alarm persists, check whether the fiber is normal. If yes, replace the board that generates
the alarm.
Step 6 If the alarm persists, replace the cross-connect and timing board at the local station.
Step 7 If the alarm persists, replace the line board at the opposite end.
Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite end.
----End
Related Information
None
4.103 FIBERTYPE_MIS
Description
Mismatch between hardware parameters and fiber types.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes are as follows:
Procedure
Step 1 Commission the system by locking optical power.
Step 2 If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.104 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the input flow at the Ethernet port exceeds the
threshold. When the received traffic at the Ethernet port exceeds the expected traffic, this
alarm is generated.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameters 1 and 2 The value of parameter 1 is always 0x00, and the value of parameter 2
is always 0x01.
Parameters 3 and 4 Indicate the traffic exceeding the expected traffic, in Mbit/s.
Possible Causes
The traffic received by the port is greater than the preset traffic at the port.
Procedure
Step 1 View the information about the alarm on the U2000 and identify the board and number of the
port where the alarm is reported.
l If the expected traffic at the port can be increased, increase the expected traffic to a value
greater than the actual traffic at the port. For details, see "Setting the RMON
Performance Monitoring Parameters for an Ethernet Port" in the Supporting Tasks.
l If the expected traffic at the port cannot be increased, service packet loss can be avoided
only by reducing the traffic transmitted by the opposite station.
----End
Related Information
None
4.105 FOP_NR
Description
The FOP_NR alarm indicating that a protection group does not receive the negotiation
response from the peer end. This alarm is generated when the local end does not receive any
RRs or APS command requests from the peer end within 1s after transmitting an APS
command request.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: No protection group is configured at the peer end or the protection type and
configuration at the peer end are inconsistent with those at the local end.
l Cause 2: Dual-ended protection switching is not enabled for the peer end.
l Cause 3: Services on the protection channel are interrupted.
Procedure
Step 1 Check whether a protection group is configured at the peer end. If not, configure a protection
group and ensure that the protection type and configuration at the peer end are consistent with
those at the local end.
Step 2 Check whether a fault occurs on the protection channel. If yes, remove the fault.
Step 3 Check whether fiber connections are correct. Ensure that the fiber connections on the working
channel are consistent with the fiber connections on the protection channel.
----End
Related Information
None
4.106 FOP_PM
Description
The FOP_PM is an alarm indicating inconsistency between the transmitted B bit in the
protection protocol and the received B bit. This alarm is generated when the B bit information
in the received APS frame and the transmitted APS frame is inconsistent.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The transmitted B bit in the protection protocol and the received B bit are inconsistent.
Procedure
Step 1 Check whether the protection type and configuration of the local end are the same as those of
the peer end. If they are different, change them to the same attribute and the alarm will be
automatically cleared.
----End
Related Information
None
4.107 FOP_PR
Description
The FOP_PR is an alarm indicating inconsistency between the transmitted R bit in the
protection protocol and the received R bit. This alarm is generated when the information in
the received APS frame and the type of APS protection configured at the local end are
inconsistent.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Revertive mode settings at both ends are inconsistent.
Procedure
Step 1 Check whether the revertive attribute of the local end is the same as that of the peer end. If the
attributes are different, modify them to the same revertive attribute and the alarm
automatically clears.
----End
Related Information
None
4.108 FPGA_ABN
Description
FPGA status being abnormal. This alarm is generated when the standby FPGA is currently
used by the board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The active FPGA file does not exist when the board starts.
l Loading of the active FPGA file fails when the board starts.
Procedure
Step 1 Reload the FPGA file to the board.
----End
Related Information
None
4.109 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is selected forcibly.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Possible Causes
A command is issued to forcibly select the clock board.
Procedure
Step 1 Cancel the command for forcibly selecting the clock board.
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.110 FWD_PKT_LOSS
Description
The FWD_PKT_LOSS is an alarm indicating loss of packets at a certain port.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The packets received by the port do not match the service configuration.
l The packets received by the port do not match the port configuration.
l Packets are lost because of data congestion, such as the loss of the CAR shaping packet.
l The packets in a queue are lost, such as the loss of the COS packet.
l The MAC address of the received packets is blacklisted.
Procedure
Step 1 Check whether the service configuration and the attribute configuration of the port match the
received packets. If a mismatch occurs, re-configure the service and/or the attributes of the
port.
Step 2 If the alarm persists, check whether the packets transmitted at the opposite station are proper.
If not, transmit proper packets again.
Step 3 If the alarm persists, check whether the QoS is configured properly. If not, re-configure the
QoS.
Step 4 If the alarm persists, check whether the black list is configured properly. If not, re-configure
the black list.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
4.111 GAINDATA_MIS
Description
Mismatch of gain attributes. This alarm is generated when the preset nominal gain value falls
beyond the gain adjustment range supported by a board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: As for the nominal gain, replacing an optical amplifier (OA) board or the optical
module causes that the nominal gain value issued by the NE software falls beyond the new
gain adjustment range.
Procedure
l Cause 1: The nominal gain value issued by the NE software falls beyond the new gain
adjustment range.
a. On the U2000, query the threshold of the current actual nominal gain. Reconfigure
a valid nominal gain value for the corresponding optical port and channel of the
board based on the queried threshold.
----End
Related Information
None
4.112 GFP_UPM
Description
Client-side signal type mismatch alarm. This alarm is generated if the UPI in the received
TYPE domain is different from the planned UPI when the GFP encapsulation mode is used.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the logical port number. The parameter value is always
0x01.
Possible Causes
The UPI in the received TYPE domain is different from the planned UPI when the GFP
encapsulation mode is used.
Procedure
Step 1 Check whether the peer board uses the GFP encapsulation mode.
Step 2 Check whether the GFP encapsulation formats (GFP-T or GFP-F) used by the local and peer
NEs are the same. If they are not the same, modify them as required to ensure that they are the
same.
----End
Related Information
None
4.113 HARD_BAD
Description
Hardware failure. This alarm is generated when the system detects a 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.
Parameter Description
Parameter 1 For packet service processing boards: Indicates the failure chip.
For other boards,
l 0x01: The power supply module is abnormal.
l 0x02: The board is not properly installed (the board is not in good
contact with the backplane, for example, the board is not secured).
l 0x03: 38M system clock 1 is abnormal.
l 0x04: 38M system clock 2 is abnormal.
l 0x05: The 2M clock source is abnormal.
l 0x06: The digital phase-locked loop (PLL) is abnormal.
l 0x07: The 38M service clock is lost.
l 0x08: The bus is abnormal.
l 0x09: The standby board under TPS protection is abnormal.
l 0x0a: The active crystal oscillator of the clock stops.
l 0x0b: The frequency deviation of the crystal oscillator is excessively
large.
l 0x0c: The standby crystal oscillator of the clock stops.
l 0x0d: The CPU/DSP/coprocessor fails.
l 0x0e: The memory component fails.
l 0x0f: The component of the programmable logic device fails.
l 0x10: The SDH component fails.
l 0x11: The data communication component fails.
l 0x12: The clock component fails.
l 0x13: The interface component fails.
l 0x14: The power component fails.
l 0x15: Other faults occur.
l 0x16: The simulated PLL is abnormal.
l 0x17: The 32M clock is invalid.
l 0x18: The 66M clock is invalid.
l 0x19: The 25M clock is invalid.
l 0x1a: The loop of the cross-connect chip fails.
l 0x1b: The 8k online signal is pulled down.
l 0x1c: The chip of the probe laser fails.
l 0x1d: The chip of the loading laser fails.
l 0x1e: The clock of the DSP driver chip is lost.
l 0x1f: The output clock of the DSP is lost.
l 0x20: The RTM module is offline.
l 0x21: A chip fails.
l 0x22: 2M system frame header 1 fails.
Parameter Description
Parameters 2 For packet service processing boards: Indicates the Failure type.
and 3
For other boards,
l When parameter 1 is 0x08, bus A is abnormal if parameter 2 is 0x01 and
bus B is abnormal if parameter 2 is 0x02. Parameter 3 is 0xff.
l When parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16,
0x19, or 0x21, parameters 2 and 3 have different values, which indicate
different component, module, or chip faults.
l When parameter 1 is 0x15, a fault occurs on other components of the
local board, on other boards, or on other components of other boards.
l When parameter 1 is of another value, parameters 2 and 3 are fixed at
0xff.
Possible Causes
l Cause 1: The NE power supplies are abnormal.
l Cause 2: The board is not connected to the backplane properly or the board is faulty.
Procedure
l Cause 1: The NE power supplies are abnormal.
a. Check whether the NE power supplies are normal. If they are abnormal, apply new
power supplies to the NE.
l Cause 2: The board is not connected to the backplane properly or the board is faulty.
a. Remove and re-insert the system control board. Check whether the alarm is cleared.
b. If the alarm persists, replace the board. For details, see "Replace the board.".
----End
Related Information
Related Cases:
l MC-A143 The Service Alarm Indicator on an OTU Board Is Still Red After the
HARD_ERR and HARD_BAD Alarms Are Suppressed
4.114 HARD_ERR
Description
Hardware error. This alarm is generated when the board hardware has a minor fault.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter Description
Parameters 2 When parameter 1 is 0x08, bus A is abnormal if parameter 2 is 0x01 and bus
and 3 B is abnormal if parameter 2 is 0x02. Parameter 3 is 0xff.
When parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16, 0x19,
or 0x21, parameters 2 and 3 have different values, which indicate different
component, module, or chip faults.
When parameter 1 is 0x15, a fault occurs on other components of the local
board, on other boards, or on other components of other boards.
l For a clock board, parameters 0x15 0x0b 0x00 indicate that the ejector
lever is not properly closed or the micro switch is faulty, and therefore
the switchover between the active and standby clock boards may fail.
l For a WSS board, parameters 0x15 0x10 0xff indicate that the board does
not have the parameter table file or the incorrect parameter table file is
loaded; parameters 0x15 0x11 0xff indicate absence of board software.
l For an OTU board, parameters 0x15 0x05 0x00 and 0x15 0x05 0x01
indicate that the received backplane serial broadcast information is
incorrect; parameters 0x15 0x04 0x00 indicate that the subrack ID parsed
from the backplane broadcast information is inconsistent with the
subrack ID reserved during the board startup.
When parameter 1 is of another value, parameters 2 and 3 are fixed at 0xff.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 When the alarm parameter is 0x15 0x10 0xff, reload the corresponding software on the
U2000.
Step 2 On the U2000, perform a warm reset or cold reset on the faulty board.
Step 3 If the alarm persists, replace the faulty board. For details, see "Replace the board.".
----End
Related Information
Related Cases:
l MC-A143 The Service Alarm Indicator on an OTU Board Is Still Red After the
HARD_ERR and HARD_BAD Alarms Are Suppressed
4.115 HARD_NONSUPPORT
Description
This alarm indicates that the hardware does not support the configuration.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 that some functions configured on the board are not supported by the
board hardware.
l 0x01: ETH PWE3 control words.
l 0x02: PW OAM control words (GAL disable).
l 0x03: 2.5 Gbit/s bus rate is configured.
l 0x04: The transmit optical power is adjustable, or the configured transmit
optical power is beyond the permitted adjustment range.
Possible Causes
The hardware does not support the configuration.
Procedure
Step 1 If the alarm parameter is 0x04, set the transmit optical power to the default value or within the
permitted adjustment range on the U2000.
Step 2 Replace the board and use the board supporting functions.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.116 HP_LOM
Description
The HP_LOM is an alarm indicating that a higher order path (HP) multiframe is lost.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The service level is inconsistent between the source and sink ends.
l Cause 2: The cross-connect and clock board is faulty. As a result, the H4 byte is lost or
incorrect.
Procedure
Step 1 Query this alarm on the NMS and determine the IDs of the port and path that report the alarm.
Step 2 Check whether the level is consistent between the peer to-be-transmitted service and the local
to-be-received service. If the service level is inconsistent, change the service level at either
end to keep its consistency. Then, check whether the HP_LOM alarm is cleared.
Step 3 If the alarm persists, replace the cross-connect and clock 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.117 HP_RDI
Description
The HP_RDI is an alarm indicating the remote receive failure in the higher order path (HP).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
This is an accompanying alarm. When reporting the AU_AIS, AU_LOP, HP_TIM, or
HP_SLM alarm, the relevant path of the peer line board sends the HP_RDI alarm to the local
end.
Procedure
Step 1 Clear the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm reported by the relevant path of
the peer line board.
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.118 HP_REI
Description
The HP_REI is an alarm indicating remote bit errors in the higher order path (HP).
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
This is an accompanying alarm. When a service-traversed NE reports the B3_EXC or B3_SD
alarm after detecting B3 bit errors, it sends the HP_REI alarm to the local NE.
Procedure
Step 1 Clear the B3_EXC or B3_SD alarm reported by a service-traversed NE.
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.119 HP_SLM
Description
The HP_SLM is an alarm indicating signal label mismatch in the higher order path (HP). This
alarm is generated when the line board detects the inconsistency between the received and to-
be-received C2 bytes.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Cause 1: On the local NE, the received C2 byte (signal label overhead in the HP), which
is not 0x00, is inconsistent with the to-be-received C2 byte.
l Cause 2: The service type is incorrectly configured.
l Cause 3: The board on the terminating NE works improperly.
Procedure
Step 1 Determine the board that initially transmits lower order services by checking the upstream
NEs that have transmitted the services. The board that initially transmits the services is the
source of the C2 byte, while the other NEs transmit the C2 byte transparently. Then,
determine the remote NE that terminates the higher order overhead and transmits the C2 byte
to the local NE, and specify the remote NE as the terminating NE.
Step 2 Check whether the configured service type and to-be-transmitted C2 byte match on the
terminating NE. If they do not match, reconfigure the C2 byte. Then, check whether the
HP_SLM alarm is cleared.
Step 3 If the alarm persists, check whether the configured service type and to-be-received C2 byte
match on the local NE. If they do not match, reconfigure the C2 byte. Then, check whether
the HP_SLM alarm is cleared.
Step 4 If the alarm persists, check whether the configured service type is consistent between the
terminating and local NEs. If the configured service type is inconsistent, modify the service
on the required NE to keep the service consistency. Then, check whether the HP_SLM alarm
is cleared.
Step 5 If the alarm persists, cold reset the receive board of the terminating NE on the NMS or
directly remove and reinsert the board. Then, check whether the HP_SLM alarm is cleared.
Step 6 If the alarm persists, replace the receive board on the terminating NE.
Step 7 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
C2 byte (signal label byte)
The C2 byte indicates the structures of the higher order virtual containers (VC-3, VC-4, and
VC-4-Xc) and the payload property.
Transparent transmission and termination
Transparent transmission indicates that a service board receives a higher order overhead byte
from an upstream NE and directly transmits it to a downstream NE without processing them.
The higher order overhead byte remains unchanged when it is transmitted from the cross-
connect board to the service board and then to the downstream NE. In most cases, higher
order services, such as the VC-4 service, transparently transmit higher order overhead bytes.
Termination indicates that the higher order overhead byte from the cross-connect board to the
service board is modified and transmitted through the optical port. The source of lower order
services, such as the VC-3 and VC-12 services, terminates higher order overhead bytes.
Figure 4-1 shows overhead transparent-transmission and termination.
4.120 HP_TIM
Description
The HP_TIM is an alarm indicating the trace identifier mismatch (TIM) in the higher order
path (HP).
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The service cross-connection is incorrectly configured.
l The J1 byte is incorrectly configured.
Procedure
Step 1 Check whether the service cross-connection is correctly configured. If the service cross-
connection is incorrectly configured, correct it. Then, check whether the HP_TIM alarm is
cleared.
Step 2 If the alarm persists, determine the board that initially transmits lower order services by
checking the upstream NEs that have transmitted the services. The board that initially
transmits the services is the source of the J1 byte, while the other NEs transmit the J1 byte
transparently. Then, determine the remote NE that terminates the higher order overhead and
transmits the J1 byte to the local NE, and specify the remote NE as the terminating NE.
Step 3 Check whether the J1 byte to be transmitted by the line board on the terminating NE consists
with the J1 byte to be received by the line board on the local NE. If both J1 bytes are
different, reconfigure the J1 byte on the required NE to keep its consistency.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
J1 byte (path trace byte)
The J1 byte is used to repetitively transmit an HP access point identifier (APID), which helps
the receive end check whether the channel is correctly connected to the specified transmit end.
Transparent transmission and termination
Transparent transmission indicates that a service board receives higher order overhead bytes
from an upstream NE and directly transmits them to a downstream NE without processing
them. The higher order overhead byte remains unchanged when it is transmitted from the
cross-connect board to the service board and then to the downstream NE. In most cases,
higher order services, such as the VC-4 service, transparently transmit higher order overhead
bytes.
Termination indicates that the higher order overhead byte from the cross-connect board to the
service board is modified and transmitted through the optical port. The source of lower order
services, such as the VC-3 and VC-12 services, terminates higher order overhead bytes.
Figure 4-2 shows overhead transparent-transmission and termination.
4.121 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path (HP) carries no overhead.
The received C2 byte is 0x00.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Services are not configured at the upstream NEs.
l The received C2 byte is 0x00.
Procedure
Step 1 Check whether services are configured for the required path on the peer NE.
If... Then...
Services are not configured Correctly configure services and check whether the
HP_UNEQ alarm is cleared. If the alarm persists, go to Step
2.
If... Then...
Step 2 Check the service path passing through the upstream NE for the HP_UNEQ alarm.
If... Then...
The alarm exists The upstream NE transparently transmits services with no overhead to
the local NE. In this case, clear the HP_UNEQ alarm on the path
passing through the upstream NE. Then, check whether the HP_UNEQ
alarm is cleared on the local NE. If the alarm persists, go to Step 3.
Step 3 Determine the board that initially transmits lower order services by checking the upstream
NEs that have transmitted the services. The board that initially transmits the services is the
source of the C2 byte, while the other NEs transmit the C2 byte transparently. Then,
determine the remote NE that terminates the higher order overhead and transmits the C2 byte
to the local NE, and specify the remote NE as the terminating NE.
Step 4 Check whether the C2 byte to be transmitted by the terminating NE is 0x00. If the C2 byte is
0x00, modify it based on the actual service type. Then, check whether the HP_UNEQ alarm is
cleared.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
C2 byte (signal label byte)
The C2 byte indicates the structures of the higher order virtual containers (VC-3, VC-4, and
VC-4-Xc) and the payload property.
Transparent transmission indicates that a service board receives higher order overhead bytes
from an upstream NE and directly transmits them to a downstream NE without processing.
The higher order overhead byte remains unchanged when it is transmitted from the cross-
connect board to the service board and then to the downstream NE. In most cases, higher
order services, such as the VC-4 service, transparently transmit higher order overhead bytes.
Termination indicates that the higher order overhead byte from the cross-connect board to the
service board is modified and transmitted through the optical port. The source of lower order
services, such as the VC-3 and VC-12 services, terminates higher order overhead bytes.
4.122 HSC_UNAVAIL
Description
Working/protection switching failure. This alarm is generated when the configured active and
standby boards fail to perform switching.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l The active and standby board versions mismatch.
l The hardware of the standby board is faulty.
l Communication between the active and standby boards is abnormal.
Procedure
Step 1 Replace the standby board.
----End
Related Information
None
4.123 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
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 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.
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
Related Information
None
4.124 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
If the possible causes do not correspond to any symptoms, or the symptoms are not listed in this topic,
handle the alarm according to the handling procedures.
None.
Possible Causes
The possible causes of the IN_PWR_ABN alarm are as follows:
Procedure
Step 1 Cause 1: The threshold of the optical power is not set properly.
1. Query the type of the optical module that reports the alarm.
2. Check whether the optical power threshold is set properly. If the threshold is set
improperly, change Input Power Reference Lower Threshold and Input Power
Reference Upper Threshold according to the receiver sensitivity or overload threshold
of the board.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
If... Then...
2. Query whether the output optical power of the board that reports the alarm on the local
end is within the permitted range.
If... Then...
3. Query whether the input optical power of the board that reports the alarm on the local
end is within the permitted range.
If... Then...
The input optical power is Repeat the following step to check the pigtails
abnormal and fiber connectors at both ends in order.
4. Check whether the bend radius of the pigtail is within the permitted range. If the bend
radius is less than 6 cm, roll the pigtail again. Check whether the alarm is cleared.
5. If the alarm persists, check whether the fiber connector is loose. If the fiber connector is
firmly connected, check whether the alarm is cleared.
6. If the alarm persists, check whether the fiber connector is dirty.
7. If the fiber connector is clean, check whether the alarm is cleared. If the alarm persists,
go to Step 3.
Step 3 Cause 3: The model of the selected optical module is incorrect.
1. See IN_PWR_LOW to handle faults related to incorrect optical modules. Check
whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The board at the local end is faulty.
1. If the board supports the pluggable optical module, replace the pluggable optical module.
Otherwise, replace the faulty board.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Cause 5: The board at the opposite end is faulty.
1. Handle the fault in the transmit unit at the opposite end. For details, see Step 4. Check
whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.125 INNER_COMMUN_MISCON
Description
Incorrect connection between an internal network and an external network. This alarm is
generated when an internal network and an external network are incorrectly connected
because the ports on the equipment are incorrectly cascaded.
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 and Parameter 2 Indicates the cascading port that is incorrectly connected.
l 0x01 0x01: Indicates that EH1 is incorrectly connected.
l 0x01 0x02: Indicates that EH2 is incorrectly connected.
l 0x01 0x03: Indicates that EH3 is incorrectly connected.
Possible Causes
Due to misoperations, the internal and external network ports of the NE are connected in
serial mode.
Procedure
Step 1 Check the network cable connection of the NE and reconnect the cables if they are not
correctly connected.
----End
Related Information
None
4.126 INSERTION_LOSS_HIGH
Description
This alarm is generated when the insertion loss between the TDC and RDC is excessively
large or does not match the gain.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.
Possible Causes
The insertion loss between the input and output ports of the DCM connected to the optical
amplifier board is excessively large or does not match the gain.
Procedure
Step 1 Check whether the insertion loss between the input and output ports of the DCM connected to
the optical amplifier board is excessively large. If it is excessively large, the fiber connector
connected to the input or output port may be dirty or the pigtail may be abnormally bent.
Clean the fiber connector or replace the pigtail.
Step 2 On the U2000, query the actual permitted gain range of optical amplifier board and set the
gain again to ensure that the gain is within the permitted range.
----End
Related Information
None
4.127 INTRA_OTU_STA_INDI
Description
Status indication of an intra-board 1+1 protection group. This alarm is generated when the
working or protection channel of the protection group is faulty or the user delivers an external
switching command.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l Cause 1: A user delivers a command to perform the external switching such as forced
switching, manual switching, or lockout switching.
l Cause 2: The services of the working or protection channel of the intra-board 1+1
protection group are faulty.
l Cause 3: The switching is in WTR state. After the time specified by WTR Times
elapses, the alarm clears.
Procedure
l Cause 1: A user delivers a command to perform external switching.
a. On the U2000, query the switching status of the protection group. If the switching
state is forced switching, manual switching, or locked switching, check whether the
external switching operation is necessary.
b. If the external switching operation is necessary, ignore the alarm.
c. If the external switching operation is unnecessary, deliver a command to clear the
external switching.
l Cause 2: The services of the working or protection channel of the intra-board 1+1
protection group are faulty.
a. Query whether the associated boards for configuring the protection group have the
alarms, such as R_LOF, R_LOS, POWER_DIFF_OVER, R_LOC, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH,
IN_PWR_LOW, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG,
OTUk_EXC. If there are such alarms, handle the alarms with reference to the
corresponding alarm handling procedure to restore the services of the working or
protection channel.
b. If the alarm persists, check whether the attribute of the protection group is
Revertive. If it is Revertive, after the WTR Times period the protection channel
automatically switches to the working channel and the alarm clears. If the attribute
is Non-Revertive, set it to Revertive. The active channel automatically switches to
the working channel and after the WTR Times period the alarm clears.
l Cause 3: The switching is in the WTR state. After the time specified by WTR Times
elapses, the alarm clears.
a. This alarm requires no handling. After the time specified by WTR Times elapses,
the alarm clears.
----End
Related Information
For details, see "Intra-Board 1+1 Protection" in the Feature Description.
4.128 IPA_FAULT
Description
IPA detection board malfunctioning alarm. This alarm is generated when all detection boards
of IPA are offline.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
In the master-slave subrack mode, all detection boards will be offline or fail in
communication if the AUX board or inter-subrack communication fails.
Procedure
Step 1 Check whether the IPA detection boards are online and whether the communication of
detection boards are normal.
Step 2 Check whether the AUX boards are normal and whether the communication of the slave
subrack on which detection boards reside is normal.
Step 3 Check whether the communication between the IPA NE and the NE with detection boards is
normal.
----End
Related Information
None.
4.129 IPA_SHUT
Description
Laser shutdown by IPA. When the IPA function detects a LOS alarm for an input port of a
board, it automatically shuts down the laser for the corresponding output port of the board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The line fiber is damaged. As a result, the board reports a MUT_LOS alarm.
l The line loss is excessively large. As a result, the input optical power is lower than the
LOS threshold of the board.
l The board is faulty. As a result, it reports a MUT_LOS alarm.
Procedure
Step 1 On the U2000, check whether a MUT_LOS alarm is reported on the boards in an IPA pair. If
the alarm is reported, clear the alarm with reference to MUT_LOS. After the fault on the line
is rectified, the laser on the board that reports the IPA_SHUT alarm is enabled again and the
IPA_SHUT alarm is automatically cleared.
----End
Related Information
OptiX OSN 8800 provides the intelligent power adjustment (IPA) function for PID boards.
For details, see "Introduction to PID IPA" in the Feature Description.
4.130 J0_MM
Description
J0 byte or trace indicator mismatch. This alarm is generated when the received J0 byte is not
consistent with the J0 byte to be received.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The J0 byte mismatches.
l The service connection is incorrect.
Procedure
Step 1 Check whether the J0 byte to be transmitted by the board at the opposite station is set the
same as the J0 byte to be received by the board at the local station. If they are inconsistent, set
them to the same value.
Step 2 If the alarm persists, bit errors may exist on the line. See the handling procedure of the
B1_SD alarm for troubleshooting.
Step 3 If the alarm persists, determine whether to replace the board as required because only the
J0_MM alarm does not affect the services.
----End
Related Information
None
4.131 K1_K2_M
Description
The K1_K2_M is an alarm indicating a mismatch between the K1 and K2 bytes. This alarm is
generated when the K1 and K2 bytes indicates different channel numbers for a given period
(default: 160 ms).
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The optical fiber is not correctly connected.
l The MSP group type is inconsistent between both ends.
l The board is faulty.
l The cross-connect board is faulty.
Procedure
Step 1 Verify that the optical fiber of the multiplex section (MS) is properly connected and the
logical configuration of the fiber matches its physical configuration. Then, check whether the
K1_K2_M alarm is cleared.
Step 2 If the alarm persists, check whether the MSP group type is consistent between the two ends. If
the MSP group type is inconsistent, reconfigure the MSP group to keep its consistency
between both ends. Then, check whether the K1_K2_M alarm is cleared.
Step 3 If the alarm persists, check whether the local and peer MS-configured boards are faulty. If
either board is faulty, replace it and check whether the K1_K2_M alarm is cleared.
Step 4 If the alarm persists, check whether the local and peer cross-connect boards are faulty. If
either board is faulty, replace it.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.132 K2_M
Description
The K2_M is an alarm indicating a K2 byte mismatch. This alarm is generated when the fifth
bit of the received K2 byte indicates a specified period (default: 2s) of inconsistency between
the peer and local multiplex section protection (MSP) modes.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l The multiplex section (MS) configuration is incorrect.
l The board is faulty.
l The cross-connect board is faulty.
Procedure
Step 1 Check whether the MS configuration is consistent between the local and peer NEs. If the MS
configuration is inconsistent, reconfigure the MS to keep its consistency between the two
NEs. Then, check whether the K2_M alarm is cleared.
Step 2 If the alarm persists, check whether the local and peer MS-configured boards are faulty. If
either board is faulty, replace it and check whether the K2_M alarm is cleared.
Step 3 If the alarm persists, check whether the local and peer cross-connect boards are faulty. If
either board is faulty, replace it and check whether the K2_M alarm is cleared.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.133 L_SYNC
Description
Loss of synchronization. This alarm is generated when loss of synchronization occurs in the
physical coding sublayer (PCS) of a receiving port.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The peer end and the local end have different settings in the working mode of the
Ethernet port and in the types of services received on the client side.
l The link is faulty.
l The equipment at the opposite station is faulty.
l The receive optical power of the board at the local station is abnormal.
l The board at the local station is faulty.
Procedure
Step 1 Check whether the working mode (autonegotiation/full-duplex/half-duplex) of the Ethernet
port at the peer end is consistent with that of the local end. If they are inconsistent, modify the
setting to ensure the consistency.
Step 2 Check whether the service types configured for the local end are consistent with the actual
service types. If they are inconsistent, modify the setting to ensure the consistency.
Step 3 If the alarm persists, check whether the fiber or cable that is used to connect the equipment at
the local station and that at the opposite station are correctly connected. If they are not
correctly connected, reconnect or replace the fiber or cable.
Step 4 If the alarm persists, check whether the data equipment at the opposite station is faulty. If it is
faulty, rectify the fault in the data equipment at the opposite station.
Step 5 If the alarm remains, use the U2000 to check whether the receive optical power of the optical
ports on the alarm-reporting board is within the permitted range. If the optical power is
----End
Related Information
None
4.134 LAG_DOWN
Description
The LAG_DOWN alarm indicates that a link aggregation group (LAG) is unavailable. This
alarm is generated when the number of activated members in a LAG is 0.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the LAG_DOWN alarm are as follows:
l Cause 1: No LAG is configured for the opposite NE.
l Cause 2: All member ports in the LAG are unavailable.
Procedure
Step 1 Cause 1: No LAG is configured for the opposite NE.
1. Check whether a LAG is configured for the opposite NE.
2. If not, configure a LAG for the opposite NE. Check whether the alarm is cleared. If the
alarm persists, go to Step 2.
Step 2 Cause 2: All member ports in the LAG are unavailable.
1. Check whether the ETH_LOS, ETH_LINK_DOWN, or LAG_MEMBER_DOWN alarm
is reported. If yes, clear the ETH_LOS, ETH_LINK_DOWN, or
LAG_MEMBER_DOWN alarm.
2. Check whether the LAG_DOWN alarm is cleared. If the alarm persists, contact Huawei
technical support engineers for handling the alarm.
----End
Related Information
None.
4.135 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN alarm indicates that a member port in the link aggregation
group (LAG) is unavailable. This alarm is generated when a member port cannot be activated
and cannot work as the backup port.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The possible causes of the ETH_LINK_DOWN alarm are as follows:
Procedure
Step 1 On the U2000, query parameters of the reported alarm.
l If the alarm cause is 0x01, go to Step 2.
l If the alarm cause is 0x02, go to Step 3.
l If the alarm cause is 0x03, go to Step 4.
l If the alarm cause is 0x04, go to Step 5.
----End
Related Information
None.
4.136 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that the port in the aggregation group is invalid.
When the GE port is not available, the aggregation fails, and therefore this alarm occurs.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 Indicates the number of the port where the alarm is generated, consisting
2 of two bytes. For example, 0x00 0x01 indicates port 1, 0x00 0x02
indicates port 2, 0x03 indicates port 3, etc.
Parameter 3 Indicates the cause of the invalid port in the aggregate group. For
example, 0x01 indicates that the port is in the link down or disabled
state. 0x02 indicates that the port is in the half-duplex mode. 0x03
indicates that the port fails to receive LACP messages. 0x04 indicates
that the port is self-looped.
Possible Causes
l The port is in the link down or disabled state.
l The port is in the half-duplex mode.
l The port has not received LACP messages.
l The port is self-looped.
Procedure
Step 1 Check the link and enable status of all ports on the U2000. Remove link faults, and then set
the port to Enable on the U2000.
Step 2 On the U2000, check whether the operation mode of the port is set to Half-Duplex. If yes, set
it to Full-Duplex.
Step 3 Check whether the corresponding link aggregation group is configured at the opposite station.
If yes, check whether the MAC address of the opposite aggregation group that provides links
to the local aggregation group is invalid. If yes, re-configure it.
Step 4 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
4.137 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that the VCG port in the aggregation group
fails. When the VCTRUNK port is unavailable, the aggregation fails. Therefore, this alarm
occurs.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 Indicates the number of the port where the alarm is generated, consisting
2 of two bytes. For example, 0x00 0x01 indicates port 1, 0x00 0x02
indicates port 2, 0x03 indicates port 3, etc.
Parameter 3 Indicates the cause of the invalid port in the aggregate group. For
example, 0x01 indicates that the port is in the link down or disabled
state. 0x02 indicates that the port is in the half-duplex mode. 0x03
indicates that the port fails to receive LACP messages. 0x04 indicates
that the port is self-looped.
Possible Causes
l The port is in the link down or disabled state.
l The port has not received LACP messages.
l The port is self-looped.
Procedure
Step 1 Check whether the VCG port in the aggregation group fails. If yes, remove VCG port faults.
Step 2 Check whether the corresponding link aggregation group is configured at the opposite station.
If yes, check whether the MAC address of the opposite aggregation group that provides links
to the local aggregation group is invalid. If yes, re-configure it.
Step 3 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
4.138 LAN_LOC
Description
Ethernet communication failure. In the case of NE cascading, this alarm is generated when the
Ethernet communication between NEs fails.
Attribute
Parameters
None
Possible Causes
l The network port is required and is enabled on the U2000. However, the network cable is
not connected or incorrectly connected to the network port.
l The network port is not required but is enabled on the U2000.
l The network cable is faulty.
l The board is faulty.
Procedure
Step 1 Query the alarm information on the U2000. Check whether the corresponding network port is
required according to the alarm parameters.
The corresponding network port Verify that the network cable is properly connected to
is required the network port and the network ports at the two ends
of the network cable are in working state.
Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable
and re-connect it.
Step 3 If the alarm persists, the auxiliary interface board (such as the AUX, EFI, EFI1, or EFI2
board) may be faulty. In this case, replace the faulty board.
----End
Related Information
None
4.139 LASER_HAZARD_WARNING
Description
Hazard related to laser levels. When a high-power laser is used in the optical transmission
system, the system may cause personal injuries. In this case, if the IPA function is disabled or
not configured, this alarm is reported prompting the user to configure the IPA function.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 band. 0x01 indicates the C-band and 0x02 indicates the
L-band.
Possible Causes
l The laser power is high and the IPA function is not configured.
l The laser power is high and the IPA function is disabled even if it has been configured.
Procedure
Step 1 Check the IPA configuration on the NE. For details, see "Creating IPA" in the Feature
Description. Check the IPA configuration for a Raman system, see "Creating IPA for a Raman
System" in the Feature Description.
Step 2 If the IPA function is not configured for the NE, follow the network plan to create IPA
protection. For details, see "Creating IPA" in the Feature Description. To create IPA
protection for a Raman system, see "Creating IPA for a Raman System" in the Feature
Description.
Step 3 If the IPA function is configured for the NE but is disabled, enable the IPA function. For
details, see "Enabling IPA" in the Feature Description. To enable the IPA function for a
Raman system, see " Enabling the IPA in a Raman System" in the Feature Description.
Step 4 After the IPA function is configured and enabled, the alarm is cleared automatically. If the
alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
The system provides the intelligent power adjustment (IPA) function. For details, see
"Intelligent Power Adjustment (IPA)" in the Feature Description.
The power of the pump light from Raman amplifiers is excessively high. For details, see
"Intelligent Power Adjustment (IPA) of Raman System" in the Feature Description.
Related Cases:
l MC-A175 How to Clear the LASER_HAZARD_WARNING Alarms Reported on
Certain OBU and OAU Boards After an Upgrade of Software
4.140 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating mismatch of optical modules. When the type
of the optical module inserted does not match the type supported by the board, this alarm
occurs.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 rate of the optical module inserted does not match the rate of the
optical port of the board.
l 0x02: The type of the inserted optical module and the type of the port on
the actual board mismatch.
Possible Causes
The possible causes of the LASER_MOD_ERR alarm are as follows:
l The optical interface is configured as single mode, but a multi-mode optical module is
used; or the optical interface is configured as multi-mode, but a single-mode optical
module is used.
l The rate of the optical module inserted does not match the rate of the optical interface of
the board.
l The optical module is faulty.
Procedure
Step 1 View the LASER_MOD_ERR alarm on the NMS and confirm the relevant board.
Step 2 Correct the optical module's attributes, check if the alarm is cleared.
Step 3 If the alarm is consist, replace the optical module. The alarm is automatically cleared.
----End
Related Information
None.
4.141 LASER_OPEN_FAIL
Description
Laser turn-on failure alarm. This alarm is reported when the laser fails to be turned on because
the line fiber quality monitoring results do not satisfy the requirements.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The line fiber quality monitoring result of a board will not satisfy the requirements and the
laser on the board will fail to be turned on when any of the following conditions is met:
Procedure
Step 1 Run the Fiber Doctor system on the U2000, view abnormal line fiber quality events after the
line fiber quality monitoring is complete.
Step 2 Based on the information about abnormal line fiber quality events, clean the corresponding
fiber end face or repair the faulty fiber.
----End
Related Information
None.
4.142 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of the board is shut down.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The user uses the U2000 to perform the operation to shut down the laser.
l Cause 1: For OCS system boards, the user uses the U2000 to shut down the laser.
l Cause 2: For a non-coherent 40G board in a WDM system, the laser is shut down
because the board temperature exceeds the permitted range.
Procedure
l Cause 1: For OCS system boards, the user uses the U2000 to shut down the laser.
a. If the user cancels the setting of laser shutdown, the LASER_SHUT alarm is
automatically cleared.
l Cause 2: For a non-coherent 40G board in a WDM system, the laser is shut down
because the board temperature exceeds the permitted range.
a. Decrease the board temperature to the normal level, and check whether the alarm is
cleared.
b. If the alarm persists, turn on the laser or perform a cold reset on the board.
----End
Related Information
None
4.143 LASER_PARA_ERR
Description
The LASER_PARA_ERR is an alarm indicating that the parameter stored in the optical
module is missing or incorrect. This alarm is reported when the parameter stored in the optical
module is missing or damaged.
Attribute
Parameters
None
Possible Causes
The possible causes of the LASER_PARA_ERR alarm are as follows:
Procedure
Step 1 View the LASER_PARA_ERR alarm on the NMS and confirm the relevant board.
Step 2 Replace the faulty optical module and send it to Huawei engineers. The alarm is automatically
cleared.
----End
Related Information
None
4.144 LASER_TYPE_MISMATCH
Description
The LASER_TYPE_MISMATCH alarm is an alarm indicating mismatch of optical module
types. This alarm is reported when the type of the inserted optical module does not match the
type of the optical module that is previously inserted, or the optical module is not authorized
by Huawei.
Attribute
Alarm Severity Alarm Type
Parameters
None
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is not covered in this topic, handle the fault
according to "Handling Procedure" provided in this topic.
Possible Causes
The possible cause of the LASER_TYPE_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. Ensure that the type of the optical module is the same as the type of the optical
module previously inserted.
b. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
4.145 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the link capacity adjustment scheme (LCAS)
protocol fails in the receive direction. This alarm is generated when the system detects an
abnormality on the LCAS sink, which may result in an LCAS negotiation failure or error.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The downstream VCTRUNK port receives duplicate sequence numbers due to incorrect
configuration or link bit errors.
l The LCAS function is not enabled on the peer VCTRUNK port.
l The downstream VCTRUNK port concurrently receives the FIXED and other LCAS
control words due to incorrect configuration or link bit errors.
l The cross-connection is incorrectly bound.
Procedure
Step 1 View the alarm on the NMS and determine the number of the VCTRUNK port.
Step 2 Check whether the LCAS protocol is enabled at the peer end. If the protocol is not enabled at
the peer end, enable it and check whether the LCAS_FOPR alarm is cleared.
Step 3 If the alarm persists, check whether configurations, especially timeslot cross-connection
binding, are correct. If there are incorrect configurations, correct them and check whether the
LCAS_FOPR alarm is cleared.
Step 4 If the alarm persists, disable the LCAS protocol at both ends and concurrently enable it. Then,
check whether the LCAS_FOPR alarm is cleared.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.146 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the LCAS protocol fails in the transmit direction.
This alarm is generated when the system detects an abnormality on the LCAS source, which
may result in an LCAS negotiation failure or error.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
An unexpected multiplex section termination (MST) occurs and lasts long due to incorrect
configurations and invalid links.
Procedure
Step 1 View the alarm on the NMS and determine the number of the VCTRUNK port.
Step 2 Verify that the service cross-connection is bound correctly on the VCTRUNK port. Then,
check whether the LCAS_FOPT alarm is cleared.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.147 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating loss of partial bandwidth in the LCAS receive
direction. This alarm is generated when only some of the configured channels carry load in
the receive direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Bidirectional services are not configured.
l The downstream channels bound at the local end outnumber the upstream channels
bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
improperly connected physical links.
Procedure
Step 1 Check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM. If any of them
exists, clear it first and check whether the LCAS_PLCR alarm is cleared.
Step 2 If the alarm persists, verify the connectivity of the physical link and check whether
bidirectional services are configured. If bidirectional services are not configured, correctly
configure them and check whether the LCAS_PLCR alarm is cleared.
Step 3 If the alarm persists, check whether the number of downstream timeslots configured for the
local VCTRUNK port is consistent with that of upstream timeslots configured for the peer
VCTRUNK port on the NMS. If the number of timeslots is inconsistent, add or delete
timeslots as required to make the number of timeslots consistent. Then, check whether the
LCAS_PLCR alarm is cleared.
Step 4 Check whether the cross-connections are bound from the transmit end to the receive end. If
the cross-connections are not bound, bind them and check whether the LCAS_PLCR alarm is
cleared.
Step 5 If the alarm persists, check the wait-to-restore (WTR) duration and wait until the WTR
expires. Then, check whether the LCAS_PLCR alarm is cleared.
Step 6 If the alarm persists, disable and enable the LCAS protocol on the VCTRUNK port. Then,
check whether the LCAS_PLCR alarm is cleared.
Step 7 If the alarm persists, delete and re-bind all physical channels of the VCTRUNK port and
check whether the LCAS_PLCR alarm is cleared.
Step 8 If the alarm persists, perform a cold reset on the board and check whether the LCAS_PLCR
alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_PLCR alarm is cleared.
Step 10 If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.148 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating loss of partial bandwidth in the LCAS transmit
direction. This alarm is generated when only some of the configured channels carry load in
the transmit direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Bidirectional services are not configured.
l The upstream channels bound at the local end outnumber the downstream channels
bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
improperly connected physical links.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port.
Step 2 Check the peer end for the LCAS_PLCR alarm. If the alarm exists at the peer end, clear it and
check whether the LCAS_PLCT alarm is cleared.
Step 3 If the alarm persists, check whether bidirectional services are configured on the port. If
bidirectional services are not configured, correctly configure them and check whether the
LCAS_PLCT alarm is cleared.
Step 4 If the alarm persists, check whether the number of upstream timeslots configured for the local
VCTRUNK port is consistent with that of downstream timeslots configured for the peer
VCTRUNK port on the NMS. If the number of timeslots is inconsistent, add or delete
timeslots as required to make the number of timeslots consistent. Then, check whether the
LCAS_PLCT alarm is cleared.
Step 5 If the alarm persists, verify that the cross-connections are correctly bound from the transmit
end to the receive end.
Step 6 If the alarm persists, check the wait-to-restore (WTR) duration and wait until the WTR
expires. Then, check whether the LCAS_PLCT alarm is cleared.
Step 7 If the alarm persists, disable and enable the LCAS function on the VCTRUNK port. Then,
check whether the LCAS_PLCT alarm is cleared.
Step 8 If the alarm persists, delete and re-bind all physical channels of the VCTRUNK port and
check whether the LCAS_PLCT alarm is cleared.
Step 9 If the alarm persists, perform a cold reset on the board and check whether the LCAS_PLCT
alarm is cleared.
Step 10 If the alarm persists, replace the board and check whether the LCAS_PLCT alarm is cleared.
Step 11 If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.149 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating loss of all bandwidth in the LCAS receive direction.
This alarm is generated when none of the configured channels carries load in the receive
direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Bidirectional services are not configured.
l The upstream channels are not bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
other alarms.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port.
Step 2 Check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM. If any of them
exists, clear it first and check whether the LCAS_TLCR alarm is cleared.
Step 3 If the alarm persists, verify the connectivity of the physical link and check whether
bidirectional services are configured. If bidirectional services are not configured, correctly
configure them and check whether the LCAS_TLCR alarm is cleared.
Step 4 If the alarm persists, check whether timeslots are bound in the upstream direction at the peer
end. If timeslots are not bound in the upstream direction, correctly bind them and check
whether the LCAS_TLCR alarm is cleared.
Step 5 If the alarm persists, verify that the cross-connections are correctly bound from the transmit
end to the receive end. Then, check whether the LCAS_TLCR alarm is cleared.
Step 6 If the alarm persists, disable and enable the LCAS function on the VCTRUNK port. Then,
check whether the LCAS_TLCR alarm is cleared.
Step 7 If the alarm persists, delete and re-bind all physical channels of the VCTRUNK port and
check whether the LCAS_TLCR alarm is cleared.
Step 8 If the alarm persists, perform a cold reset on the board and check whether the LCAS_TLCR
alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_TLCR alarm is cleared.
Step 10 If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.150 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating loss of all bandwidth in the LCAS transmit direction.
This alarm is generated when none of the configured channels carries load in the transmit
direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The downstream channels are not bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
other alarms.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port.
Step 2 Check the peer end for the LCAS_TLCR alarm. If the alarm exists at the peer end, clear it and
check whether the LCAS_TLCT alarm is cleared.
Step 3 If the alarm persists, check the system for other alarms, such as the AIS, LOP, UNEQ, and
LOM. If any of them exists, clear it first and check whether the LCAS_TLCT alarm is
cleared.
Step 4 If the alarm persists, check whether timeslots are bound in the downstream direction at the
peer end. If timeslots are not bound in the downstream direction, correctly bind them and
check whether the LCAS_TLCT alarm is cleared.
Step 5 Verify that the cross-connections are correctly bound from the transmit end to the receive end.
Then, check whether the LCAS_TLCT alarm is cleared.
Step 6 If the alarm persists, disable and enable the LCAS function on the VCTRUNK port. Then,
check whether the LCAS_TLCT alarm is cleared.
Step 7 If the alarm persists, delete and re-bind all physical channels of the VCTRUNK port and
check whether the LCAS_TLCT alarm is cleared.
Step 8 If the alarm persists, perform a cold reset on the board and check whether the LCAS_TLCT
alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_TLCT alarm is cleared.
Step 10 If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.151 LCS_DAYS_OF_GRACE
Description
License in keepalive period. This alarm indicates that the license has expired but is within the
keepalive period of 60 days.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 5 l Indicates that the license or control item expires naturally when the
parameter value is 0x00.
l Indicates that the license has been revoked when the parameter
value is 0x01.
l Indicates ESN mismatching when the parameter value is 0x02.
l Indicates V/R mismatching when the parameter value is 0x03.
l Indicates ESN and V/R mismatching when the parameter value is
0x04.
When the values of parameters 1 and 2 are not 0x00 0x00, the value of
parameter 5 is 0x00.
Possible Causes
l The license file fails. The system is in the trial state and within the keepalive period of 60
days.
l The license file does not match ESN or V/R version. The system is in trial state and
within the keepalive period of 60 days.
l The license-controlled items exceed the expiration date but are within the keepalive
period of 60 days.
Procedure
Step 1 Load a license file to the system.
----End
Related Information
None
4.152 LCS_EXPIRED
Description
License expired. This alarm indicates that the license has expired and the keepalive period of
60 days has also elapsed.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 3 l Indicates that the license has been revoked when the parameter
value is 0x01.
l Indicates ESN mismatching when the parameter value is 0x02.
l Indicates V/R mismatching when the parameter value is 0x03.
l Indicates ESN and V/R mismatching when the parameter value is
0x04.
Possible Causes
l The license of the system has expired and the keepalive period of 60 days has also
elapsed.
l The system license file does not match the ESN or V/R version, and the keepalive period
of 60 days has elapsed.
Procedure
Step 1 Load a license file to the system.
----End
Related Information
None
4.153 LCS_FILE_NOT_EXIST
Description
No license file. This alarm indicates that the system is under license control but no license file
is loaded to the system.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
When starting up, the system does not find a license file, which is essential for the system to
run.
Procedure
Step 1 Load a license file to the system.
----End
Related Information
None
4.154 LCS_SHORTAGE_SHELF
Description
Licenses are insufficient, or the license function used exceeds the authorized amount.
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
Parameters 1 Indicates the license type. For example, 0x01 indicates the subrack speedup
license.
Possible Causes
Licenses are insufficient, or the license function used exceeds the authorized amount. For
example, a large capacity board has been set to line-mode without sufficient subrack speedup
licenses.
Procedure
Step 1 Purchase enough license authentication, get a new license file and reactivate it. For the lack of
sufficient subrack speedup licenses, configure the working mode of the service board to the
regeneration mode.
----End
Related Information
None
4.155 LOCAL_FAULT
Description
Local fault alarm.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The input fiber on the client side is transiently cut.
l The board receives a large number of bit errors.
l The input optical power on the client side is abnormal.
Procedure
Step 1 Check whether the attenuation of the fiber between the input equipment and the optical port
on the client side of the board is overlarge, and whether the fiber is aged or loose. If it is,
clean the fiber connector or replace the fiber.
Step 2 Check whether the output optical power of the input equipment is within the permitted range.
If the optical power is abnormal, rectify the fault in the input equipment.
----End
Related Information
None
4.156 LOCK_CUR_FAIL
Description
Failure to lock the working current. The alarm occurs when the working current is abnormal.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
The board is faulty.
Procedure
Step 1 Perform a warm reset on the faulty board on the U2000.
----End
Related Information
None
4.157 LOCKPOW_MIS
Description
Mismatch of locked pump optical power. This alarm is generated when the configured locked
pump optical power and the actual locked pump optical power of the board are inconsistent.
Attribute
Parameters
None
Possible Causes
The configured locked pump optical power and the actual locked pump optical power of the
board are inconsistent.
Procedure
Step 1 Reconfigure the locked pump optical power of the board on the U2000.
----End
Related Information
None
4.158 LOL
Description
Loss of lane alignment alarm.
Attribute
Alarm Severity Alarm Type
Critical Communication
Parameters
None
Possible Causes
The multilane alignment process is in the out-of-alignment (OLA) state, or the frame
alignment process is in the out-of-frame (OOF) state for 3 ms.
Procedure
Step 1 Ensure that the input optical power of the board is within the permitted range, and the type of
actually received services is consistent with the configured service type (OTU4).
Step 2 Check whether the service type supported by the optical module on the board matches with
the type of actually received services. If a service type mismatch occurs, replace the optical
module with an appropriated one.
----End
Related Information
None.
4.159 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating a remote receive failure on the VC-3 path. This
alarm is generated when a board detects bit 5 of the G1 byte is 1 for the VC-3 path.
Attribute
Parameters
None.
Possible Causes
The peer end receives alarms, such as TU_AIS_VC3 and TU_LOP_VC3.
Procedure
Step 1 On the NMS, check for severer alarms, such as such as TU_AIS_VC3 and TU_LOP_VC3.
Clear these alarms first.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.160 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating a mismatch between C2 bytes identifying VC-3
signals.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The type is inconsistent between the received and to-be-received signals. That is, the
received and to-be-received C2 bytes are different.
l The service type is set incorrectly.
Procedure
Step 1 View the alarm on the NMS and determine the number of the path that reports the alarm.
Step 2 Check whether the C2 byte is consistent between the VC-3 paths at the local and peer ends. If
the C2 byte is inconsistent, modify the C2 byte on the VC-3 path at either end to keep its
consistency. Then, check whether the LP_SLM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the VC-3 services are correctly configured. If the services
are incorrectly configured, correctly configure them and check whether the LP_SLM_VC3
alarm is cleared.
Step 4 If the alarm persists, replace the local board that reports the alarm.
Step 6 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.161 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that the VC-3 path carries no service. This alarm
is generated when a board detects that the C2 byte is 0.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The service type is set incorrectly.
l No service is received.
Procedure
Step 1 View the alarm on the NMS and determine the number of the path that reports the alarm.
Step 2 Verify that the service type is correctly set and services are correctly received. Then, check
whether the LP_UNEQ_VC3 alarm is cleared.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers for help.
----End
Related Information
None.
4.162 LPT_CFG_CLOSEPORT
Description
The LPT_CFG_CLOSEPORT is an alarm indicating that the link-state pass through (LPT)
disables a service port. On the packet domain, upon detecting that a remote access-side port
fails or the LPT service network fails, the LPT disables the local access-side port and reports
this alarm.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the LPT_CFG_CLOSEPORT alarm are as follows:
l Cause 1: A fault such as a port failure is detected on the remote access side.
Access link 1
becomes faulty. Access link 2
Access-side port
Network-side port
Access-side port
Network-side port
Procedure
Step 1 Cause 1: A fault such as a port failure is detected on the remote access side.
1. As shown in Figure 4-4, when access link 1 becomes faulty, NE1 sends LPT packets to
NE2 and NE2 closes its access-side port so that NE B on the user side detects the fault.
Check whether the ETH_LOS, ETH_LINK_DOWN, and LSR_NO_FITED alarms
exist on the remote access-side port.
2. If any of the ETH_LOS, ETH_LINK_DOWN, and LSR_NO_FITED alarms exists,
clear the alarms first. Check whether the LPT_CFG_CLOSEPORT alarm is cleared. If
the alarm persists, go to Step 2.
Step 2 Cause 2: The LPT service network is faulty.
1. As shown in Figure 4-5, when the remote and local NNI ports detect service network
failure, NE1 and NE2 send LPT packets to each other, and close their access-side ports
so that NE A and NE B on the user side can detect the fault. Check whether a fiber cut or
a tunnel signal degrade occurs on the LPT service network.
2. Rectify the fault that occurs on the service network. Then, check whether the
LPT_CFG_CLOSEPORT alarm is cleared. If the alarm persists, contact Huawei
technical support engineers for help.
----End
Related Information
None.
4.163 LPT_RFI
Description
The LPT_RFI is an alarm indicating that the link-state pass through (LPT) detects a remote
port failure. This alarm is generated when the LPT detects that a remote port or its LPT
service network fails.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The remote port fails. For example, the port reports the LINK_ERR alarm or is not
enabled.
Procedure
Step 1 View the alarm on the NMS, and determine the board that reports the alarm and the number of
the port that reports the alarm according to alarm parameters.
Step 2 Check whether the remote port is enabled. If the port is not enabled, enable it and check
whether the LPT_RFI alarm is cleared.
Step 3 If the alarm persists, check the remote end for the LINK_ERR alarm. If the alarm exists, clear
it and check whether the LPT_RFI alarm is cleared.
Step 4 If the alarm persists, check whether the remote LPT service network is faulty.
l If a fiber cut occurs, replace the fiber and check whether the LPT_RFI alarm is cleared.
l If there are bit error threshold-crossing alarms, such as B3_EXC, clear them and check
whether the LPT_RFI alarm is cleared.
l If there are alarms, such as VCAT_LOA, VCAT_LOM_VC3, VCAT_LOM_VC4, and
LP_UNEQ_VC3, clear them and check whether the LPT_RFI alarm is cleared.
Step 5 If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.164 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating that the bias current of the laser crosses the
threshold. If the bias current of the laser crosses the threshold, the LSR_BCM_ALM alarm is
reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Possible Causes
The possible causes of the LSR_BCM_ALM alarm are as follows:
Procedure
Step 1 View the LSR_BCM_ALM alarm on the NMS, and confirm the board where the
LSR_BCM_ALM alarm is reported.
Step 2 If the board supports a pluggable optical module, replace the pluggable optical module.
Otherwise, replace the faulty board, and then check whether the alarm is cleared.
----End
Related Information
None.
4.165 LSR_COOL_ALM
Description
Cooling current of the laser crossing the threshold. This alarm is generated when the cooling
current of the laser on the WDM side exceeds the threshold.
Attribute
Parameters
None
Possible Causes
The possible causes of the LSR_COOL_ALM alarm are as follows:
Procedure
Step 1 Check whether the ambient temperature is excessively high. If it is, decrease the ambient
temperature for the equipment to work normally, and 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
4.166 LSR_INVALID
Description
The LSR_INVALID is an alarm indicating an invalid optical module. This alarm is generated
when the optical module cannot pass authentication.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 Indicates the reason why the optical module is invalid. 0x01 indicates that the
optical module has no license. 0x02 indicates that the license verification of
the optical module is incorrect.
Possible Causes
l The optical module has no license.
l A fault occurs during verifying the license of the optical module.
Procedure
Step 1 Replace the optical module with another one with a correct license, and then re-verify the
license. After successful verification, the alarm is cleared.
----End
Related Information
None
4.167 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the laser is not installed. This alarm is
generated when the optical port is enabled but has no optical modules installed.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Possible Causes
The possible causes of the LSR_NO_FITED alarm are as follows:
l The enabled optical port has no optical modules installed.
l The optical module is faulty.
Procedure
Step 1 View the LSR_NO_FITED alarm on the U2000 and confirm the relevant board.
Step 2 Replace the board and check whether the LSR_NO_FITED alarm is cleared.
----End
Related Information
None
4.168 LSR_KEY_UNLOCK
Description
Abnormal board interlock switch. This alarm is generated when the cover of the interlock
switch on the TN97ERPC board is turned on and the laser is turned off, or is generated when
the interlock switch on another board is not properly tightened.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The cover of the interlock switch on the TN97ERPC board panel is opened.
l Cause 2: The interlock switch on the front panel of another board rather than TN97ERPC
is not properly tightened.
Procedure
l Cause 1: The cover of the interlock switch on the TN97ERPC board panel is opened.
a. Check whether the cover of the interlock switch on the board panel is opened by
mistake.
n If yes, close the cover of the interlock switch and restart the board laser.
n If no, open the cover of the interlock switch, and remove and re-insert the
board, or replace the board. Then, close the cover of the interlock switch and
restart the board laser.
NOTICE
Only authorized engineers are allowed to perform operations on the interlock
switch.
l Cause 2: The interlock switch on the front panel of another board rather than TN97ERPC
is not properly tightened.
a. The alarm is automatically cleared after the interlock switch on the front panel is
properly tightened.
----End
Related Information
None
4.169 LTI
Description
The LTI is an alarm indicating the loss of synchronization sources. This alarm is generated
when there are clock sources other than internal clock sources listed in the priority table but
the board operates in the holdover or free-run mode.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The possible causes of the LTI alarm are as follows:
l Cause 1: There is a fiber cut or a cable cut.
l Cause 2: There is no input from the external clock source.
l Cause 3: The synchronization source is set as non-revertive or is locked.
l Cause 4: The board is faulty.
Procedure
l On the U2000, view the clock sources traced by the NE that reports the LTI alarm. The
clock sources include external clock sources, line clock sources, and tributary clock
sources.
l Cause 1: There is a fiber cut or a cable cut. Cause 4: The board is faulty.
a. On the U2000, check whether the R_LOS, R_LOC, or R_LOF alarm occurs on the
relevant line board or tributary board. If yes, clear the alarm first, and then check
whether the LTI alarm is cleared.
b. If the alarm persists, perform a cold reset on the relevant line board or tributary
board. After successful cold reset, check whether the LTI alarm is cleared. For
details, see Performing Cold Reset on a Board in the Supporting Tasks.
c. If the alarm persists, replace the relevant line board or tributary board, and then
check whether the LTI alarm is cleared. For details, see Parts Replacement.
d. If the alarm persists, perform a cold reset on the clock board, and then check
whether the alarm is cleared. For details, see Performing Cold Reset on a Board
in the Supporting Tasks.
e. If the alarm persists, replace the clock board. For details, see the Parts
Replacement.
l Cause 2: There is no input from the external clock source. Cause 4: The board is faulty.
a. Make sure that the external clock equipment properly transmits signals. Replace the
external clock equipment with a normal one, and then check whether the LTI alarm
is cleared.
b. If the alarm persists, check whether the input and output modes of the external
clock source are consistent. After the input and output of the external clock source
are set to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is
cleared. For details, see Configuring Physical Clock in the Feature Description.
c. If the alarm persists, check whether the clock input cable is correctly connected.
After ensuring the correct connection of the clock input cable, check whether the
alarm is cleared.
d. If the alarm persists, perform a cold reset on the clock board, and then check
whether the alarm is cleared. For details, see Performing Cold Reset on a Board
in the Supporting Tasks.
e. If the alarm persists, replace the clock board. For details, see the Parts
Replacement.
l Cause 3: The synchronization source is set as non-revertive or locked.
a. On the U2000, check whether the synchronization source is set as non-revertive. If
yes, set the source as revertive. Then, check whether the alarm is cleared.
b. On the U2000, check whether the synchronization source is set as locked. If yes, set
the source as unlocked. Then, check whether the alarm is cleared.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.170 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 generated when the number of
bit errors crosses the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
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 opposite end is abnormal, which may be
caused by a faulty fiber connector.
l Cause 3: The receive optical power at the local end is abnormal, which may be caused by
a fiber connector.
Procedure
l Cause 1: Line signals deteriorate.
a. On the NMS, check whether the denial of service (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 opposite end is abnormal, which may be
caused by a faulty fiber connector.
a. On the NMS, check whether the transmit optical power at the opposite end is within
the permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for
Boards" in the Hardware Description to obtain the manufacturer information of the optical
module on the board.
i. Check whether the fiber connector is properly connected. Ensure that the fiber
connector is installed securely. Check whether the alarm is cleared.
ii. If the alarm persists, check whether the fiber connector is clean. If the fiber
connector is dirty, clean it. For details, see the Supporting Tasks. Check
whether the alarm is cleared.
c. If the alarm persists, check whether the attenuation value of the optical attenuator is
proper.
The attenuation value of the optical Adjust the value properly. Check whether
attenuator is improper the alarm is cleared. If the alarm persists,
go to the next step.
d. Check whether the fiber adapter is correctly connected. Ensure that the fiber adapter
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
opposite NE. Then, check whether the alarm is cleared.
f. If the alarm persists, check whether the service processing board and cross-connect
board of the opposite 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 fiber connector.
a. On the NMS, check whether the receive optical power at the local end is within the
permitted range. For details, see step 1 in Cause 2.
b. If the receive optical power is beyond the permitted range, see steps 2 to 6 in Cause
2 for troubleshooting at the local end.
----End
Related Information
None.
4.171 MAINBD_SUBBD_MISMATCH
Description
In one PID group, the service processing board must match the service outputting board;
otherwise, the MAINBD_SUBBD_MISMATCH alarm is generated.
Attribute
Parameters
None
For example, in a PID group where the NPO2 board and ENQ2 board are used together, if the
NPO2 board does not support the ENQ2 board installed in the corresponding slot, the
wavelength services on the NPO2 board will not be affected, but the wavelength services on
the ENQ2 board will be unavailable.
Possible Causes
The service outputting board does not support the service processing board. However, the
service processing board is housed in the corresponding slot.
Procedure
Step 1 Determine whether the service processing board is required.
Step 2 If the service processing board is required, replace the service outputting board with a board
that supports the service processing board. If the service processing board is not required,
remove it from the corresponding slot.
----End
Related Information
None
4.172 MCLAG_CFG_MISMATCH
Description
MC-LAG configuration mismatch alarm. This alarm is generated when the system detects that
the configurations at both ends of an MC-LAG are inconsistent.
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
Possible Causes
The MC-LAG configurations at two ends are different.
Procedure
Step 1 Query the alarm on the U2000. Then, determine the boards that report the alarm and
corresponding alarm parameter.
l If the alarm parameter is 0x01, check whether the LAG IDs at both ends are consistent.
l If the alarm parameter is 0x02, check whether the MC-LAG types at both ends are
consistent.
l If the alarm parameter is 0x04, check whether the MC-LAG load sharing modes at both
ends are consistent.
l If the alarm parameter is 0x08, check whether the LAG restoration modes at both ends
are consistent.
----End
Related Information
None
4.173 MCSP_PATH_LOCV
Description
Loss of connection of the protocol channel for multi-chassis synchronization protocol. This
alarm is generated when there is no expected Hello packet observed in any period of three
consecutive intervals.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The peer NE is malfunctioning.
l Cause 2: The physical link with the peer NE is interrupted.
l Cause 3: There is no path configuration on the peer NE.
Procedure
Step 1 Check whether the physical connection between the local NE and peer NE is valid. If yes,
check whether the physical fiber is damaged and replace the damaged fiber accordingly. If
not, check whether the physical connection is the same as the planned connection in the
planning drawing.
Step 2 Check whether the protocol channel status of the peer NE is normal. If the protocol channel
status is abnormal, rectify the fault.
----End
Related Information
None
4.174 MOD_COM_FAIL
Description
Module communication abnormality. The alarm is generated when the communication
between the CPU and other internal modules of the board is abnormal.
Attribute
Parameters
None
Possible Causes
l The board is in poor contact with the connector of the optical module.
l The software processing of the optical module on the board is faulty.
l The board hardware is faulty.
Procedure
Step 1 Check the connection between the board and optical module and re-connect the board and
optical module if they are not properly connected.
Step 2 If the alarm persists, perform a cold reset on the faulty board on the U2000 or remove the
faulty board and insert it again.
Step 3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board.
----End
Related Information
None
4.175 MCS_SWITCH_BLOCKED
Description
MCS_SWITCH_BLOCKED is an alarm indicating that the MCS switch is blocked. This
alarm is generated when the system finds that no optical cross-connection can be created
during wavelength verification and the MCS switch of the MCS0816 board is automatically
blocked.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The actual wavelength at the AM optical port of the MCS0816 board is
different from the configured wavelength.
l Cause 2: No logical fiber connection is configured between the AM optical port of the
MCS0816 board or the logical and physical fiber connections are inconsistent.
l Cause 3: No input wavelength can be detected at the AM optical port of the MCS0816
board.
l Cause 4: Among the input wavelengths at AM1 to AM16 of the MCS0816 board, the
same wavelength is configured at the same OUT port.
l Cause 5: When the MCS0816 board is used in optical/electrical NE separation scenario,
the communication between the optical and electrical NEs is abnormal.
l Cause 6: The MCS0816 board is used in optical/electrical NE separation scenario, and
the electrical NE version is earlier than V100R011C00.
Procedure
Step 1 Check the actual number of the input wavelength at the AM optical port where the optical
cross-connection fails to be created. If the wavelength is inconsistent with the configured
wavelength, change the wavelengths based on the wavelength planning so that they are
consistent.
Step 2 Check the logical fiber connection between the AM optical port of the MCS0816 board and
the coherent OTU board or protection board. Configure the correct logical fiber connection on
the U2000 so that the logical and physical fiber connections are consistent.
Step 3 Ensure that the board connected to the AM optical port where the optical cross-connection
fails to be created is properly functioning and can output wavelengths.
Step 4 Check the input wavelengths at AM1 to AM16 of the MCS0816 board. If there is the same
wavelength, configure the optical cross-connection again so that the same wavelength is
configured to different OUT ports.
Step 5 When the MCS0816 board is used in optical/electrical NE separation scenario, ensure that the
communication between the optical and electrical NEs is normal. If the communication is
restored to normal, check the version of the electrical NE. If the version is earlier than
V100R011C00, upgrade the version to V100R011C00.
----End
Related Information
None
4.176 MODULE_ADJUST_FAIL
Description
Optical module adjustment failure.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 Indicates the type of the component in which the alarm is generated. For
example, 0x01 indicates that the VOA adjustment fails. 0x02 indicates that the
optical switch adjustment fails.
Possible Causes
l The temperature of the optical module is excessively high.
l The optical module of the board is faulty.
Procedure
Step 1 Check whether the board temperature exceeds the threshold, and whether the TEM_HA or
TEMP_OVER alarm is generated. If it is, handle the alarm according to the corresponding
handling procedures.
Step 2 Deliver the configuration again. If the alarm persists, the adjusted range of the optical module
exceeds the threshold. Perform a warm reset on the board.
Step 3 If the alarm persists, replace the faulty optical module or board.
----End
Related Information
None
4.177 MODULE_COOLCUR_OVER
Description
Module cooling current exceeding the threshold. The alarm is generated when the cooling
current of the module is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates that the
upper threshold is exceeded and 0x02 indicates that the lower threshold is
exceeded.
Possible Causes
l The temperature of the optical module is excessively high.
l The board hardware is faulty.
Procedure
Step 1 Check the ambient temperature of the board. If the ambient temperature is excessively high,
handle the alarm according to the handling procedure of the TEMP_OVER alarm.
Step 2 If the alarm persists, the board at the local station may be faulty. Replace the faulty board.
----End
Related Information
None
4.178 MODULE_RATE_MISMATCH
Description
Signal rate mismatching an optical module. This alarm is generated when the optical module
does not support a mode, such as the speedup mode, specified by the user.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
None
Possible Causes
The module does not support the rate specified for the board.
Procedure
Step 1 Check whether the module supports the rate specified for the board. If it is not, change the
rate to the one that is supported by the module.
----End
Related Information
None
4.179 MODULE_TEMP_OVER
Description
Module temperature exceeding the threshold. This alarm is generated when the temperature of
the module is higher than the upper threshold or lower than the lower threshold.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the threshold crossing type. 0x01 indicates that the upper threshold is
exceeded and 0x02 indicates that the lower threshold is exceeded.
Possible Causes
l The ambient temperature of the board is excessively high or excessively low.
Procedure
Step 1 Check the ambient temperature of the board. If the ambient temperature is excessively high or
excessively low, handle the alarm according to the handling procedure of the TEMP_OVER
alarm.
Step 2 If the alarm persists, the board at the local station may be faulty. Perform a cold reset on the
faulty board on the U2000.
Step 3 If the alarm persists, replace the faulty board.
----End
Related Information
None
4.180 MODULEFILE_UPDATE_FAIL
Description
Failure to update the microprogram and laser parameter table. This alarm is generated when
the in-service upgrade of the optical module microprogram and the parameter table on the
U2000 fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The upgrade of the optical module microprogram or the laser parameter table fails.
Procedure
Step 1 Check whether the upgraded microprogram of the optical module and the parameter table of
the laser are correct.
Step 2 Upgrade the optical module microprogram and the laser parameter table again.
Step 3 If the alarm persists, replace the faulty optical module or board.
----End
Related Information
None
4.181 MPLS_PW_AIS
Description
The MPLS_PW_AIS is an alarm indicating defects of a PW. The MIP sends an AIS packet to
the downstream NE when it detects a fault on the tunnel that carries the PW. The sink MEP
NE reports this alarm upon receiving the AIS packet.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible cause of the MPLS_PW_AIS alarm is as follows:
Cause: The MIP NE detects a fault on a tunnel carrying the PW.
Procedure
Step 1 Cause: The MIP NE detects a fault on a tunnel carrying the PW.
1. Check whether MPLS Tunnel OAM is configured correctly on source and sink MEP
NEs and the MIP NE. If MPLS Tunnel OAM is configured incorrectly, modify the
configurations. Then, check whether the alarm is cleared.
2. If the alarm persists, check whether tunnel-related alarms are reported on MEP NEs. For
example, MPLS_TUNNEL_AIS. If any of these alarms exist, clear them immediately.
Then, check whether the MPLS_PW_AIS alarm is cleared.
3. If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.182 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV is an alarm indicating the loss of PW connectivity. This alarm is
generated when an Ethernet port fails to receive OAM detection packets for three consecutive
periods.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_PW_LOCV alarm are as follows:
Procedure
Step 1 Cause 1: PW labels are configured incorrectly.
1. Check the PW labels configured for all the NEs (including the source NE, transit NEs,
and sink NE), and ensure that ingress and egress labels on neighboring NEs are the same.
2. If the PW labels are configured incorrectly, change them to the same for neighboring
NEs. Check whether the alarm is cleared.
3. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network is severely congested.
1. Based on the actual situation, increase the value of Detection Packet Period
appropriately. Then, check whether the alarm is cleared.
2. If the alarm persists, check whether the bandwidth allocated to the faulty PW is fully
used. If yes, eliminate the source that transmits a large amount of invalid data. Then,
check whether the alarm is cleared.
3. If the alarm persists, go to Step 3.
Step 3 Cause 3: Board failure occurs.
1. On the NMS, 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_PW_LOCV alarm is cleared.
2. If the MPLS_PW_LOCV alarm persists, check whether the local NE and the opposite
NE report alarms that are related to the hardware of the optical modules or boards, such
as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first. Then, check
whether the MPLS_PW_LOCV alarm is cleared.
3. If the alarm persists, contact Huawei technical support engineers for help.
Step 4 Cause 4: The PW physical link is connected incorrectly or is faulty.
1. Check whether the fiber or cable is connected incorrectly. For example, a fiber or cable
is incorrectly connected to a port on the next-hop NE due to manual operations. If the
fiber or cable is incorrectly connected, rectify the fiber or cable connection. Check
whether the alarm is cleared.
2. If the alarm persists, check whether the fiber or cable is damaged or pressed. If the fiber
or cable is damaged or pressed, replace the faulty fiber or cable. Check whether the
alarm is cleared.
3. If the alarm persists, contact Huawei technical support engineers for help.
----End
Related Information
None.
4.183 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL is an alarm indicating that the OAM protocol negotiation fails.
This alarm is generated when the OAM protocol negotiation fails on NEs at both ends of a
PW.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
In the auto-negotiation mode, the possible causes of the MPLS_PW_OAMFAIL alarm are as
follows:
Cause 1: The OAM function is only enabled on the NE at one end of the PW.
NOTE
The alarm is reported only by the NE on which the OAM function is enabled. As shown in Figure 4-7,
only the local NE reports the MPLS_PW_OAMFAIL alarm.
Cause 2: The PW has been interrupted when enabling the OAM function.
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
NOTE
As shown in Figure 4-8, when the PW is interrupted in the forward direction or reverse direction, the
peer or local NE reports the MPLS_PW_OAMFAIL alarm accordingly.
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 such as
MPLS_TUNNEL_OAMFAIL are reported on the two ends of the PW. If any of these
alarms exist, clear them before you proceed.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.184 MPLS_PW_RDI
Description
The MPLS_PW_RDI is an alarm indicating defects of a remote PW. The remote MEP sends
an RDI packet to the local MEP when it detects a PW fault. The local MEP reports this alarm
after receiving the RDI packet.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
A PW fault is detected on the remote MEP NE.
RDI packet
MEP MEP
3. The remote MEP reports the 2. The local MEP cannot
MPLS_PW_RDI alarm upon receive the OAM packet due
receiving the RDI packet. to a PW fault. It returns an
RDI packet to the local MEP.
Procedure
Step 1 A PW fault is detected on the remote MEP NE.
1. Check whether the faulty NE reports port-, optical module- or board-related alarms. For
example, ETH_LOS, ETH_LINK_DOWN, LSR_NO_FITED, and HARD_BAD. If
any preceding alarms are reported, clear them.
2. Check whether service-related alarms are reported by the faulty NE. For example,
MPLS_PW_LOCV. If any of these alarms exist, clear them immediately. Then, check
whether the MPLS_PW_RDI alarm is cleared.
3. If the alarm persists, check whether the physical link between faulty NEs is faulty. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty
optical fiber or cable.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.185 MPLS_PW_SD
Description
The MPLS_PW_SD alarm indicates that signals on a PW degrade. This alarm is generated
when the loss ratio of continuity check (CC) packets is higher than the SD threshold but is
lower than the SF threshold.
Attribute
Parameters
None.
Possible Causes
The possible causes of the MPLS_PW_SD alarm are as follows:
Procedure
Step 1 Cause 1: An excessive number of bit errors occur.
1. Query the performance statistics of Ethernet ports to check whether bit errors or FCS
errored frames are generated.
2. Check whether the physical link is connected correctly. If any optical cables are broken,
replace the faulty optical fibers. If any optical ports are dirty or damaged, clean the
optical ports. If the bend radius of the fiber patch cord is less than 6 cm, reroute the fiber
patch cord. Clear bit errors on the transmission line first. Then, check whether the alarm
is cleared.
3. If the alarm persists, go to Step 2.
----End
Related Information
None.
4.186 MPLS_PW_SF
Description
The MPLS_PW_SF is an alarm indicating that signals on a PW degrades severely. This alarm
is generated when the loss ratio of CC packets crosses the SF threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_PW_SF alarm are as follows:
Procedure
Step 1 Cause 1: An excessive number of bit errors occur.
1. Query the performance statistics of Ethernet ports to check whether bit errors or FCS
errored frames are generated.
2. Check whether the physical link is connected correctly. If any optical cables are broken,
replace the faulty optical fibers. If any optical ports are dirty or damaged, clean the
optical ports. If the bend radius of the fiber patch cord is less than 6 cm, reroute the fiber
patch cord. Clear bit errors on the transmission line first. Then, check whether the alarm
is cleared.
3. If the alarm persists, go to Step 2.
----End
Related Information
None.
4.187 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG alarm indicates that an MEG is unexpected on the PW. This
alarm is reported when the MEP receives CCM frames with the correct MEG level but
incorrect MEG ID.
Attribute
Alarm Severity Alarm Type
Parameters
None.
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-10, 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.
PW1: PW outlabel = 1
PW inlabel = 1
PW2: PW outlabel = 1
PW1
NE1 NE2
PW2
Service flow
l Cause 2: MEG IDs configured on NEs at both ends of the PW are different.
As shown in Figure 4-11, 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 IDs and reports the MPLS_PW_UNEXPMEG
alarm.
MEG ID = 1 MEG ID = 2
NE1 NE2
Service flow
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-12, 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.
PW outlabel = 1 PW inlabel = 1
MEG ID = 1 MEG ID = 1
NE1 NE2
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-10, 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-11, 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-12, check whether the fiber or cable is correctly connected
between ports at both ends. If the fiber or cable is incorrectly connected, connect it
correctly.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.188 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP alarm indicates that an MEP is unexpected on a PW. This
alarm is reported when the MEP receives CCM frames with the correct MEG level, correct
MEG ID, but unexpected MEP ID.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_PW_UNEXPMEP alarm are as follows:
l Cause 1: MEP IDs are inconsistent on NEs at both ends of a PW.
As shown in Figure 4-13, 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.
PW
NE1 PSN NE2
Service flow
Procedure
Step 1 Cause 1: MEP IDs are inconsistent on NEs at both ends of a PW.
1. As shown in Figure 4-13, 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.
2. On the NMS, check whether tunnel-related alarms such as
MPLS_TUNNEL_OAMFAIL are reported by NEs at both ends of the PW. If any of
these alarms are reported, clear them before you proceed.
3. Check whether service-related alarms MPLS_TUNNEL_LOCV such as are reported by
NEs at both ends of the PW. If any of these alarms are reported, clear them before you
proceed.
----End
Related Information
None.
4.189 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER alarm indicates that the PW period is unexpected. This alarm is
reported when the MEP receives packets with the correct MEG level, MEG ID, and MEP ID,
but the period carried in the packets is different from the period for the MEP to transmit
packets.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_PW_UNEXPPER alarm are as follows:
Procedure
Step 1 Cause 1: The PW source or sink node is configured with an incorrect period.
1. Ensure that the correct periods are configured at the PW source and sink nodes,
according to the NE planning table.
2. If period configurations are incorrect, rectify them.
Step 2 Cause 2: The physical link has an incorrect connection.
1. Ensure that the related fiber or cable is correctly connected.
2. If the fiber or cable connection is incorrect, rectify the connection.
----End
Related Information
None.
4.190 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS is an alarm indicating defects of a tunnel. The MIP NE sends an
AIS packet to the downstream NE when it detects a fault on the upstream port. The MEP NE
reports the MPLS_TUNNEL_AIS alarm upon receiving the AIS packet.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The MIP node detects a fault on the tunnel physical layer.
Tunnel Tunnel
Procedure
Step 1 The MIP node detects a fault on the tunnel physical layer.
1. Check whether the faulty NE reports port-, optical module- or board-related alarms such
as ETH_LOS, ETH_LINK_DOWN, LSR_NO_FITED, and HARD_BAD. If any of
these alarms are reported, clear them immediately. Then, check whether the
MPLS_TUNNEL_RDI alarm is cleared.
2. If the alarm persists, check whether the physical link between faulty NEs is faulty. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty
optical fiber or cable.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.191 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV alarm indicates the loss of tunnel connectivity. This alarm is
generated when an Ethernet port fails to receive expected OAM detection packets for three
consecutive periods.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_TUNNEL_LOCV alarm are as follows:
l Cause 1: Tunnel labels are configured incorrectly.
l Cause 2: The network is severely congested.
l Cause 3: Board failure occurs.
l Cause 4: The physical link is connected incorrectly or is faulty.
l Cause 5: ARP entries fail to be learned.
NOTE
Procedure
Step 1 Cause 1: Tunnel labels are configured incorrectly.
1. Check the tunnel labels configured for all the nodes (including the ingress node, transit
nodes, and egress node) on the label switched path (LSP) in sequence, and ensure that
ingress and egress labels on neighboring nodes are the same.
2. If the tunnel labels are configured incorrectly, change them to the same settings for
neighboring nodes. Then, check whether the alarm is cleared.
3. If the alarm persists, go to Step 2.
Step 2 Cause 2: The network is severely congested.
1. Based on the actual situation, increase the value of Detection Packet Period
appropriately. Check whether the alarm is cleared.
2. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is fully
used. If yes, eliminate the source that transmits a large amount of invalid data. Check
whether the alarm is cleared.
3. If the alarm persists, go to Step 3.
Step 3 Cause 3: Board failure occurs.
1. On the NMS, 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.
2. On the NMS, check whether the local NE and the opposite NE report alarms that are
related to the hardware of the optical modules or boards, such as HARD_BAD and
LSR_NO_FITED. If yes, clear these alarms first. Then, check whether the
MPLS_TUNNEL_LOCV alarm is cleared.
3. If the alarm persists, go to Step 4.
Step 4 Cause 4: The physical link is connected incorrectly or is faulty.
1. Check whether the fiber or cable is connected incorrectly. For example, a fiber or cable
is incorrectly connected to a port on the next-hop NE due to manual operations. If the
fiber or cable is incorrectly connected, rectify the fiber or cable connection. Then, check
whether the alarm is cleared.
2. If the alarm persists, check whether the fiber or cable is damaged or pressed. If the fiber
or cable is damaged or pressed, replace the faulty fiber or cable. Then, check whether the
alarm is cleared.
3. If the alarm persists, go to Step 5.
Step 5 Cause 5: ARP entries fail to be learned.
1. Check the ARP entries on the explicit nodes (including the ingress node, transit nodes,
and egress node) in sequence according to the NE planning table, and ensure that the
mapping between IP addresses and MAC addresses is correct on neighboring nodes.
2. If the mapping between IP addresses and MAC addresses on the next-hop NE is not
displayed, ARP entries fail to be learned. Rectify the fault on the MPLS tunnel
immediately.
3. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.192 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL is an alarm indicating a failure to negotiate the OAM
protocol. This alarm is generated by a Tunnel OAM enabled NE when the OAM protocol
negotiation fails on NEs at both ends of a tunnel.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
In the auto-negotiation mode, the possible causes of the MPLS_TUNNEL_OAMFAIL alarm
are as follows:
Cause 1: The OAM function is enabled only on the NE at one end of the tunnel. The OAM
enabled end reports the MPLS_TUNNEL_OAMFAIL alarm.
Forward
tunnel
PSN
Backward
tunnel
MPLS_TUNNEL_OAMFAIL is reported.
Service flow
NOTE
Only the NE where the OAM function is enabled will report the MPLS_TUNNEL_OAMFAIL alarm.
As shown in Figure 4-15, only the local NE reports the MPLS_TUNNEL_OAMFAIL alarm.
Cause 2: The tunnel has been interrupted when the OAM function is enabled.
PSN
Backward
tunnel
MPLS_TUNNEL_OAMFAIL is reported
Service flow
NOTE
As shown in Figure 4-16, the MPLS_TUNNEL_OAMFAIL alarm is reported by the remote NE when
the forward tunnel is interrupted and by the local NE when the reverse tunnel is interrupted.
Procedure
Step 1 Cause 1: The OAM function is enabled only on the NE at one end of the tunnel. The OAM
enabled end reports the MPLS_TUNNEL_OAMFAIL alarm.
1. Query this alarm on the NMS and check whether the OAM function is enabled on NEs at
both ends of the tunnel. 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 tunnel has been interrupted when the OAM function is enabled.
1. On the NMS, check whether there are port-, optical module- and board-related alarms on
NEs which the tunnel traverses such as ETH_LOS, ETH_LINK_DOWN,
LSR_NO_FITED, and HARD_BAD. If any of these alarms exist, clear them before
you proceed.
2. Check whether there are service-related alarms on NEs which the tunnel traverses such
as MPLS_TUNNEL_LOCV. If any of these alarms exist, clear them before you
proceed.
3. Check whether physical links of this tunnel are faulty. For example, the optical fiber or
cable is damaged or pressed. If yes, replace the faulty optical fiber or cable.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.193 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI is an alarm indicating remote defects of a tunnel. The remote
MEP NE sends an RDI packet to the local MEP NE when it detects defects of a tunnel. The
local MEP NE reports this alarm upon receiving the RDI packet.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The remote MEP NE detects that the tunnel is faulty.
Forward tunnel
Backward Tunnel
3. Upon receiving the RDI packet, 2. Due to a tunnel fault, the local MEP fails to receive
the remote MEP reports the the OAM detection packet. As a result, the local MEP
MPLS_TUNNEL_RDI alarm. reports the MPLS_TUNNEL_LOCV alarm and returns
an RDI packet.
Procedure
Step 1 The remote MEP NE detects that the tunnel is faulty.
1. Check whether the faulty NE reports port-, optical module- or board-related alarms such
as ETH_LOS, ETH_LINK_DOWN, LSR_NO_FITED, and HARD_BAD. If any of
these alarms are reported, clear them immediately. Then, check whether the
MPLS_TUNNEL_RDI alarm is cleared.
2. Check whether the faulty NE reports service-related alarms such as
MPLS_TUNNEL_LOCV. If any of these alarms are reported, clear them immediately.
Then, check whether the MPLS_TUNNEL_RDI alarm is cleared.
3. If the alarm persists, check whether the physical link between faulty NEs is faulty. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty
optical fiber or cable.
4. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.194 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD alarm indicates that signals on a tunnel degrade. This alarm is
generated when the packet loss ratio of continuity (CC) is higher than the SD threshold but is
lower than the SF threshold.
Attribute
Parameters
None.
Possible Causes
The possible causes of the MPLS_TUNNEL_SD alarm are as follows:
Procedure
Step 1 Cause 1: An excessive number of bit errors occur.
1. On the NMS, check whether the MAC_FCS_EXC alarm is reported. If yes, clear the
MAC_FCS_EXC alarm first and then check whether the alarm is cleared.
2. If the alarm persists, go to Step 2.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for help.
----End
Related Information
None.
4.195 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF alarm indicates that signals on a tunnel degrade severely. During
the continuity check (CC), this alarm is reported if the packet loss ratio crosses the SF
threshold but CC packets are received in three consecutive periods.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_TUNNEL_SF alarm are as follows:
Procedure
Step 1 Cause 1: An excessive number of bit errors occur.
1. On the NMS, check whether the MAC_FCS_EXC alarm is reported. If yes, clear the
MAC_FCS_EXC alarm first and then check whether the alarm is cleared.
2. If the alarm persists, go to Step 2.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.
1. On the NMS, check whether the allocated bandwidth is fully used. If yes, eliminate the
source that transmits a large amount of invalid data. Check whether the alarm is cleared.
----End
Related Information
None.
4.196 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG alarm indicates that an MEG is unexpected on a tunnel.
This alarm indicates that the MEP receives CCM packets with the correct MEG level but
incorrect MEG ID.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the MPLS_TUNNEL_UNEXPMEG alarm are as follows:
l Cause 1: There are multiple tunnels with the same MEG ID between the source and sink
NEs.
An example is provided as follows: As shown in Figure 4-18, there are two links that are
connected to NE2 in the network plan: tunnel 1 between NE1 and NE2, and tunnel 2
between NE3 and NE2. The MEG ID of tunnel 1 is 1 and that of tunnel 2 is 2.
However, in actual configuration, outgoing MEG IDs of both tunnel 1 and tunnel 2 are
set to 1. NE2 receives a CCM packet that contains incorrect MEG ID from NE3. As a
result, NE2 reports the MPLS_TUNNEL_UNEXPMEG alarm.
MEG ID = 1 MEG ID = 1
Tunnel
NE1 NE2
el
PSN Tunn
Tunnel
NE1 PSN NE2
l Cause 3: Physical links are connected incorrectly. Multiple tunnels with the same MEG
ID are connected to the same sink NE.
As shown in Figure 4-20, 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 NE2 is mistakenly connected to NE3, 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.
Tunnel
NE1 NE2
el
Tunn
Tunnel
NE3 NE4
Service flow
Procedure
Step 1 Cause 1: There are multiple tunnels with the same MEG ID between the source and sink NEs.
1. As shown in Figure 4-18, check whether there are multiple tunnels with the same
outgoing 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-19, 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 incorrectly. Multiple tunnels with the same MEG ID are
connected to the same sink NE.
1. As shown in Figure 4-20, 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 to handle the alarm.
----End
Related Information
None.
4.197 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP alarm indicates that an MEP is unexpected on a tunnel.
This alarm is reported when the MEP receives CCM packets with the correct MEG level,
correct MEG ID, but unexpected MEP ID.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible cause of the MPLS_TUNNEL_UNEXPMEP alarm is as follows:
l Cause 1: MEP IDs are inconsistent on NEs at both ends of the tunnel.
As shown in Figure 4-21, 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 CCM packet
with an unexpected MEP ID from NE1.
Tunnel
NE1 PSN NE2
Procedure
Step 1 Cause 1: MEP IDs are inconsistent on NEs at both ends of the tunnel.
1. As shown in Figure 4-21, check whether MEP IDs are consistent on the source and sink
NEs of the tunnel.
NOTE
The MEP IDs must be consistent on the source and sink NEs of a tunnel.
2. If MEP IDs are inconsistent, change them to the same.
----End
Related Information
None.
4.198 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER alarm indicates that the tunnel period is unexpected. This
alarm is reported when the MEP receives CCM packets with the correct MEG level, MEG ID,
and MEP ID, but the period carried in the packets is different from the period for the MEP to
transmit packets.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible cause of the MPLS_TUNNEL_UNEXPPER alarm is as follows:
l Cause 1: The tunnel configurations are incorrect and the periods configured at the source
and sink NEs are different.
l Cause 2: The physical link has an incorrect connection.
Procedure
Step 1 Cause 1: The tunnel configurations are incorrect and the periods configured at the source and
sink NEs are different.
1. On the NMS, check the tunnel configurations and check whether the tunnel
configurations at the source and sink NEs are consistent.
2. If they are inconsistent, modify the tunnel configurations.
----End
Related Information
None.
4.199 MS_APS_INDI_EX
Description
The MS_APS_INDI_EX is an extended indication alarm of the MSP switching state. The
alarm occurs when the multiplex section switching causes the switching of services.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Name Meaning
Parameter 4 Indicates the slot ID of the board where the switching occurs.
Parameter 6 Indicates the number of the optical port where the switching occurs.
Possible Causes
The possible causes of the MS_APS_INDI_EX alarm are as follows:
l An external switching command is issued.
l There is a fiber cut.
l The board is faulty.
Procedure
Step 1 View the MS_APS_INDI_EX alarm on the U2000. According to the alarm parameters,
determine the slot ID and optical port number of the board where the protection switching
occurs.
Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked
switching. If yes, clear the switching, and then the alarm is automatically cleared.
Step 3 If the MSP is in the automatic switching state, do as follows:
1. Make sure that the fibers connected to the service board configured with the MSP are not
cut. Fix the broken fibers and then check whether the alarm is cleared.
2. Make sure that the service board configured with the MSP is not faulty. Replace the
relevant service board and then check whether the alarm is cleared.
3. Make sure that the cross-connect board configured with the MSP is not faulty. Replace
the relevant cross-connect board and then check whether the alarm is cleared.
----End
Related Information
If the services are switched in the 1+1 single-ended non-revertive linear multiplex section, the
services are not automatically switched back to the working channel after the optical channel
is recovered, and the MS_APS_INDI_EX alarm persists. In this case, the services need to be
manually switched from the protection channel to the working channel. The
MS_APS_INDI_EX alarm can be cleared only after successful switching.
4.200 MS_CROSSTR
Description
Multiplex section performance exceeds the threshold. The alarm is generated when the
performance module reports threshold-crossing performance events in the multiplex section.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l The performance of the laser on the board at the opposite station deteriorates.
l The input optical power of the board at the local station is excessively high or
excessively low.
l The performance of the clock at the opposite station deteriorates.
l The fiber performance deteriorates.
Procedure
Step 1 Check whether the fiber is aging or has excessive attenuation. If it is, remove the fault of the
fiber.
Step 2 Query whether the board has the B1_EXC, B2_EXC, B1_SD or B2_SD alarms by using the
U2000. If it is, clear the alarms.
Step 3 Check whether the input optical power of the board at the local station is within the permitted
range by using the U2000. For the optical power specifications of the specific board, see the
Product Description.
l If the optical power displayed on the U2000 is normal, the board might be faulty.
Replace the faulty board. For details, see the Parts Replacement.
l If the optical power displayed on the U2000 is abnormal, adjust the input optical power
to be within the permitted range.
Step 4 If the alarm persists, remove the fault of the board in the opposite station.
----End
Related Information
A performance monitoring period can be 15 minutes or 24 hours. A performance threshold-
crossing alarm checks whether the requirement of alarm clearance is met only after a new
monitoring period starts. If the alarm persists after you perform the provided procedure, query
whether the service has been restored to normal by checking the accumulated performance
values. Or wait after a new monitoring period starts and then check whether the alarm is
cleared.
4.201 MS_REI
Description
The MS_REI is an alarm indicating that bit errors occur at the remote end of the multiplex
section (MS). When the receive side of the optical port at the local station receives the M1
byte, which indicates the number of block bit errors detected by BIP-Nx24 (B2) at the
opposite station, the MS_REI alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The number of B2 bit errors received at the opposite station is beyond the specified range.
Procedure
Step 1 After you clear the B2_EXC or B2_SD alarm that occurs at the opposite station, the MS_REI
alarm is automatically cleared.
----End
Related Information
None
4.202 MS_SNCP_PS
Description
The MS_SNCP_PS is an alarm indicating the MS SNCP protection switching. This alarm is
generated when the MS SNCP protection group actuates switching in which the current
channel switches to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or
manual switching. Such a command makes the current channel of the MS SNCP
protection group switch to the protection channel from the working channel. Hence, the
alarm is reported.
l Cause 2: The services on the working channel of the MS SNCP protection group are
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching or manual switching, check whether the external switching operation is
necessary:
Step 2 If the alarm is generated due to the automatic switching of the protection group:
1. Query whether the related boards for configuring the protection group have alarms
relevant to the services, such as B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, REM_SF, and REM_SD. If yes, handle the alarms by referring to the
corresponding alarm handling procedures.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, after the time specified by WTR Times elapses the active channel automatically
switches to the working channel and the alarm is cleared. If the attribute is Non-
Revertive, set it to Revertive, and after the time specified by WTR Times elapses the
alarm is cleared.
----End
Related Information
None
For OptiX OSN 6800 and OptiX OSN 3800, see "MS SNCP Protection" in the Feature
Description.
4.203 MS_SNCP_STA_INDI
Description
The MS_SNCP_STA_INDI is an alarm indicating the MS SNCP protection group status. This
alarm is generated when the working or protection channel of the protection group is faulty or
a user runs an external switching command.
Reporting side: NA
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Possible Causes
l A user issues an external switching command such as forced switching, manual
switching, or locked switching.
l The services of the working or protection channel of the MS SNCP group are faulty.
l The switching is set to WTR State. After the WTR time, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching, manual switching or locked switching, check whether the external switching
is necessary:
1. If the external switching is necessary, ignore the alarm.
2. If the external switching is unnecessary, issue a switching clearing command to clear the
external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
1. Query whether alarms such as B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, REM_SF, and REM_SD are reported on the related boards for
configuring the protection group. If they are, handle the alarms according to the
corresponding handling procedure of the alarms to restore the services of the working or
protection channel.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
it is, after the time specified by WTR Times elapses the active channel automatically
switches to the working channel and the alarm is cleared. If the attribute is Non-
Revertive, set it to Revertive, and after the time specified by WTR Times elapses the
alarm is cleared.
Step 3 On the U2000, query the switching state of the protection group. If the switching is in the
WTR state, the alarm requires no handling. After the time specified by WTR Times elapses,
the alarm is cleared.
----End
Related Information
For OptiX OSN 6800 and OptiX OSN 3800, see "MS SNCP Protection" in the Feature
Description.
4.204 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that there is more than one RPL OWNER
node on the ring.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The ERPS protocol requires that the configuration of every node on a ring should be managed
and one RPL OWNER should exist on each ring. Therefore, the alarm is generated when
more than one RPL OWNER node is configured in a ring.
Procedure
Step 1 Check whether the node ID in all the received NR and RB packets is consistent with the ID of
the local node. If yes, proceed with the next step.
Step 2 Start the timer whose time is three times of the transmitting period (15s) of the packets. The
aging of the timer indicates the end of the alarm.
----End
Related Information
None
4.205 MUT_TLOS
Description
Loss of output multiplexed signals. This alarm is generated when the output multiplexed
signals of the board are lost.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the optical port where the alarm is generated. For example,
0x01 indicates optical port 1.
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is
generated. For example, 0x00 0x01 indicates channel 1 of the optical
port indicated by Parameter 1.
Possible Causes
l The optical power of the output port is excessively low. Maybe the input optical power
of the add wavelength is excessively low.
l The attenuation of signals in line transmission is overlarge.
l The board is faulty.
Procedure
Step 1 Verify that the fiber connections are correct according to the engineering fiber connection
diagram so that the input optical signals in different wavelengths are transmitted to
corresponding input optical ports of the board. If the fiber connections are incorrect, correct
them according to the diagram.
Step 2 If the alarm persists, measure the actual receive optical power of the board at the local station
by using an optical power meter. Check whether the receive optical power or transmit optical
power is within the permitted range.
Step 3 If the receive optical power or transmit optical power of the board at the local station is
excessively low, check whether the MUT_LOS alarm is generated at the local station.
l If yes, see the handling procedure of the MUT_LOS alarm for troubleshooting.
l If no, make sure that the input power of the added wavelength is normal.
Step 4 If the alarm persists, the board at the local station may be faulty. Replace the faulty board.
----End
Related Information
None
4.206 NEBD_XC_DIF
Description
Cross-connect matrix data of the NE and that of the board being different. This alarm is
generated when the cross-connection data stored on the system control board is not consistent
with that stored on a board supporting service cross-connections. It is also generated when
multiple subracks are configured in master-slave mode and SDH boards are present in the
slave subracks.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter Description
Possible Causes
l Cause 1: The cross-connection data stored on the board is incorrect.
l Cause 2: The cross-connection data stored on the system control board is incorrect.
l Cause 3: Multiple subracks are configured in master-slave mode and SDH boards are
present in the slave subracks.
Procedure
l Query the alarm on the U2000. Record the slot ID of the board that reports the alarm.
l Cause 1: The cross-connection data stored on the board is incorrect.
a. Re-configure the cross-connection data on the U2000.
l Cause 2: The cross-connection data stored on the system control board is incorrect.
a. If the alarm persists, perform a warm reset on the board related to service cross-
connections on the U2000.
b. If the alarm persists, perform a warm reset on the system control board on the
U2000.
l Cause 3: Multiple subracks are configured in master-slave mode and SDH boards are
present in the slave subracks.
a. Modify the board configurations in the slave subracks to ensure that no SDH board
is present when multiple subracks are configured in master-slave mode.
----End
Related Information
Related Cases:
l MC-A119 The NEBD_XC_DIF Alarm Occurs Because of Cross-Connections and
Outloop Configured on the Client Side of the LQG
4.207 NESF_LOST
Description
Absence of NE software. The alarm is generated when the NE software information is not
found on the system control board.
Attribute
Parameters
None
Possible Causes
The NE software is not reloaded after the NE software of the system control board is erased.
Procedure
Step 1 Reload the NE software of the system control board.
Step 2 If the alarm persists, the board at the local station may be faulty. Replace the faulty board.
----End
Related Information
None
4.208 NESTATE_INSTALL
Description
NE being in installing state and no data configured. This alarm is generated when the NE is in
the initial installation state.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The NE is in the initial installation state.
l The normal configuration is not delivered to the NE after the NE is initialized.
Procedure
Step 1 Deliver the configuration information to the board by using the U2000.
----End
Related Information
None
4.209 NO_BD_PARA
Description
Absence of the board parameter table file. This alarm is generated when the board does not
have the parameter table file.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The correct parameter table file 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 a warm reset on the faulty board on the U2000.
----End
Related Information
None
4.210 NO_BD_SOFT
Description
Absence of board software. This alarm is generated when the board does not have necessary
software, such as the loading software and logic software.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 Indicates the fault type. For example, 0x01 indicates that the file is lost
and 0x02 indicates that the file verification fails.
Parameter Description
l If the board that reports the alarm is not reset, the services and functions of the board are
not affected.
l If the board that reports the alarm is reset, the board may fail to start.
Possible Causes
l Parts of the software are not loaded to the board.
l The software on the board is abnormally lost in the running process.
l The internal detection of the board is abnormal.
Procedure
Step 1 Reload the corresponding software on the U2000.
----End
Related Information
None
4.211 NO_ELABEL
Description
Electronic label unloaded. This alarm is generated when the electronic label of a board is lost
or not loaded.
Attribute
Suggestion 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
Parameters 2 Indicates the electronic label number of the carrier that reports the alarm.
and 3
NOTE
Parameter 2 uses the fixed value of 0x00 and parameter 3 indicates sequence
number 0x01, 0x02, or 0x03. For example,
l 0x00 and 0x01 indicate that the carrier whose electronic label is missing is a
board.
l 0x00 and 0x02 indicate that the carrier whose electronic label is missing is an
optical module.
Possible Causes
The electronic label is lost or not loaded.
Procedure
Step 1 If 0x99 is reported for parameter 1, apply for a time window for high-risk operations and
perform a cold reset on the service board that reports the alarm, making the logical version of
the board take effect and clearing the alarm.
Step 2 If the electronic label of the board that reports this alarm, replace the board.
NOTE
During board replacement, check whether there are bent pins on the backplane. If there are bent pins on
the backplane, handle the bent pins in a timely manner.
Step 3 If the electronic label of the backplane is lost, check whether there are bent pins on the
backplane. If there are bent pins on the backplane, handle the bent pins in a timely manner. If
the problem persists after handling, replace the subrack.
Step 4 If the alarm persists after the preceding operations, contact Huawei engineers to handle the
problem.
----End
Related Information
None
4.212 NODEID_MM
Description
Mismatch of MSP node IDs. This alarm is generated when the configured ID of an MSP node
on the MS ring mismatches the actual node ID.
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 Indicates the ID of the MSP group in which the NODEID_MM alarm is
generated.
Possible Causes
The east and west node IDs configured for each node on the MSP ring do not match.
Procedure
Step 1 View the NODEID_MM alarm on the U2000 to determine the MSP group ID.
Step 2 Check whether the configuration of the MSP data meets the following requirements. If it is
not, re-configure the MSP according to the following requirements:
l The node IDs configured for any two NEs are not repeated.
l If node A is in the west of its adjacent node B, the local node ID of node A must be the
same as the west node ID of node B, and the local node ID of node B must be the same
as the east node ID of node A.
Step 3 Restart the MSP protocol. The alarm clears automatically.
----End
Related Information
None
4.213 NTP_SYNC_FAIL
Description
NTP synchronization failure. This alarm indicates that the NE is in the unsynchronized state.
The alarm is cleared when the NTP turns into the synchronous state.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l The NTP server is not configured or incorrectly configured.
l The NE fails to connect to the NTP server or the connection is interrupted.
l The NTP server stops unexpectedly.
Procedure
Step 1 Check whether the NTP server is configured correctly.
----End
Related Information
None
4.214 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
Parameters
None
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. After the
NULL mapping status is disabled, configure the NULL_SEND alarm to be monitored.
----End
Related Information
None
4.215 OA_HIGH_GAIN
Description
Gain of an optical amplifier (OA) board being high. This alarm is generated when the actual
gain of an OA board is 2 dB higher than the nominal gain.
Attribute
Parameters
None
Possible Causes
The possible causes of the OA_HIGH_GAIN alarm are as follows:
Procedure
Step 1 Check whether the specified fiber type matches the fiber in use. If they mismatch, set the fiber
type again so that they match each other.
Step 2 Check whether the current nominal gain is lower than the minimum nominal gain of the new
fiber. If it is, reset the nominal gain to ensure that it is within the permitted range.
Step 3 Check whether the upstream board is the TN14FIU board and whether it is properly
connected.
----End
Related Information
None.
4.216 OA_OUT_PWR_ABN
Description
Transmit-end OA power abnormal alarm. This alarm is generated when the difference
between the output optical power computed using the input optical power of the multiplexed
wavelengths on the transmit-end OA board and the standard optical power exceeds the
specified threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The input optical power of the monitored wavelengths is abnormal. As a result, the difference
between the computed output optical power and the standard power exceeds the threshold.
Procedure
Step 1 Check whether the line fiber connections are normal and whether the fibers are aged.
Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the VOA
attenuation to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively
low, set the alarm threshold according to the plan of the live network.
Step 4 Check whether the insertion loss of the board is normal.
----End
Related Information
None
4.217 OCH_FDI
Description
Forward defect at the OCh layer. This alarm is generated to suppress the OCH_FDI_P and
OCH_FDI_O alarms when the two alarms coexist.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The OCH_FDI_P and OCH_FDI_O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 If the alarm persists, check whether the OTS_LOS, OTS_TIM, OTS_LOS_O, or
OMS_LOS_P alarm is generated at the opposite station and all upstream stations. If yes, clear
the OTS_LOS, OTS_TIM, OTS_LOS_O, or OMS_LOS_P alarm by following proper
handling procedures.
----End
Related Information
None
4.218 OCH_FDI_O
Description
Forward defect (overhead) at the OCh layer. This alarm is generated when the downstream
station receives the OCH_FDI_O signal inserted by the OTS layer after the OTS layer detects
the OTS_LOS_O signal.
Attribute
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The OCh layer receives the FDI_O overhead signal inserted by the OMS layer at the
upstream station when the OMS layer loses overhead signals because of a fiber cut, low
optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 If the alarm persists, check whether there is the OTS_LOS_O alarm at the opposite station
and all upstream stations. If it is, clear the OTS_LOS_O alarm by following proper handling
procedures.
----End
Related Information
None
4.219 OCH_FDI_P
Description
Forward defect indication (payload) at the OCh layer. This alarm is generated when the
downstream station receives the OCH_FDI_P signal inserted by the OMS layer after the OMS
layer detects a payload LOS signal.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The OCh layer receives the FDI_P overhead signal inserted by the OMS layer at the
upstream station when the OMS layer loses payload signals because of a fiber cut, low
optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 If the alarm persists, check whether there is the OTS_LOS_P or OMS_LOS_P alarm at the
opposite station and all upstream stations. If it is, clear the OTS_LOS_P or OMS_LOS_P
alarm by following proper handling procedures.
----End
Related Information
None
4.220 OCH_LOS_P
Description
The OCH_LOS_P is an alarm indicating loss of signal (payload) at the OCh layer. When the
OTU detects LOS alarms and there is no OTS_LOS_P, OMS_LOS_P, or OMS_SSF_P alarm
at the upper OMS and OTS layers, the OCH_LOS_P alarm is reported.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The board detects no payload signals because of there is a fiber cut, low optical power,
or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If
not, modify the logical fiber connection to make it consistent with the actual fiber connection.
Step 2 Confirm that the fiber connection between the OTU board that reports this alarm and the
DEMUX board is correct.
Step 3 If the alarm persists, check whether the output optical power at the OUT port of the OTU
board at the opposite or upstream station is normal. If not, clear the alarm according to the
procedure for handling the IN_PWR_HIGH or IN_PWR_LOW alarm to make the output
optical power normal.
Step 4 If the alarm persists, check whether the fiber at the OUT port of the OTU board at the
opposite or upstream station is disconnected from the multiplexer board. If yes, correctly
connect the fiber between the two boards.
Step 5 If the alarm persists, check whether the dispersion of the fiber complies with the requirement.
If not, connect a suitable dispersion compensation module.
Step 6 If the alarm persists, check whether there is the R_LOS alarm.
l If yes, clear the alarm according to the handling procedure of R_LOS.
l If not, replace the faulty board.
----End
Related Information
None
4.221 OCH_OCI
Description
Open connection indication at the OCh layer. This alarm is generated when the optical
termination node in the downstream receives the OCI signal inserted to the downstream if no
optical cross-connections are configured on the upstream service link or no logical fiber
connection is configured from the OTU board to the multiplexer board.
Attribute
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l No optical cross-connection for services to the local station is configured at the upstream
station.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the optical cross-connections at the upstream station are configured. If they
are not, configure the optical cross-connections to ensure the normal transmission of the
services.
----End
Related Information
None
4.222 OCH_SSF
Description
Server signal failure at the OCh layer. This alarm is generated to suppress OCH_SSF_P and
OCH_SSF_O alarms when the two alarms coexist.
Attribute
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The OTS_LOS alarm at the upper OTS layer or the OMS_LOS alarm at the OMS layer
is generated.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether there is the OTS_LOS, OTS_TIM, OTS_LOS_P, OTS_LOS_O, or
OMS_LOS_P alarm is generated on the FIU board connected to the local board, If it is, clear
the OTS_LOS, OTS_TIM, OTS_LOS_P, OTS_LOS_O, or OMS_LOS_P alarm by following
the proper handling procedures.
Step 3 If the alarm persists, check whether the OTS_LOS, OTS_TIM, OTS_LOS_P, OTS_LOS_O,
or OMS_LOS_P alarm is reported at the opposite station and all upstream stations. If it is,
clear the OTS_LOS, OTS_TIM, OTS_LOS_P, OTS_LOS_O, or OMS_LOS_P alarm by
following the proper handling procedures.
----End
Related Information
None
4.223 OCH_SSF_O
Description
Server signal (overhead) failure at the OCh layer. This alarm is generated when the OMS
layer detects the loss of overhead signals.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The OCh layer receives the SSF_O overhead signal from the OMS layer when the OTS
layer loses overhead signals because of a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_O alarm is generated on the FIU board connected to the local
board. If it is, clear the OTS_LOS_O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether an OTS_LOS_O alarm is generated at the opposite station
and all upstream stations. If it is, clear the OTS_LOS_O alarm by following proper handling
procedure.
----End
Related Information
None
4.224 OCH_SSF_P
Description
Server signal (payload) failure at the OCh layer. This alarm is generated when the OMS layer
detects the loss of payload.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
The OCh layer receives the SSF_P overhead signal from the OMS layer when the OMS layer
loses payload signals because of a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_P or OMS_LOS_P alarm is generated on the FIU board
connected to the local board. If it is, clear the OTS_LOS_P or OMS_LOS_P alarm by
following proper handling procedure.
Step 3 If the alarm persists, check whether the OTS_LOS_P or OMS_LOS_P alarm is reported at the
opposite station and all upstream stations. If it is, clear the OTS_LOS_P or OMS_LOS_P
alarm by following proper handling procedure.
----End
Related Information
None
4.225 ODU_AIS
Description
The ODU_AIS is an alarm indicating an optical demultiplexing unit (ODU) alarm.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the alarm are as follows:
l Severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur on the local NE.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS,
occur on the local NE. If yes, clear these alarms first. Then, check whether the ODU_AIS
alarm is cleared.
Step 2 If the ODU_AIS alarm persists, locate the NE (FR NE) that initially reports the ODU_AIS
alarm. Then, repeat the preceding step.
Step 3 If the ODU_AIS alarm persists, check whether severer alarms occur on the upstream NE (PR
NE) of the FR NE. If yes, clear the alarms.
Step 4 If the ODU_AIS alarm persists, perform a loopback on the transmit optical ports of NEs from
the FR NE in the upward direction. Locate the NE (FL NE) that initially reports the
ODU_AIS alarm or severer alarms. Then, perform the following steps:
1. Check whether configurations on the FL NE are correct. If no, correct connection and
configurations.
2. If the ODU_AIS persists, replace the line board on the FL NE.
3. If the ODU_AIS persists, replace the cross-connect board on the FL NE.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
4.226 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the optical demultiplexing unit
(ODU) channel are locked.
Attribute
Parameters
None.
Possible Causes
The possible causes of the alarm are as follows:
Procedure
Step 1 Check whether the ODU channel is being tested. If yes, wait until the test is completed and
unlock the ODU channel. Then, check whether the alarm is cleared.
Step 2 If the ODU channel is not being tested, unclock it. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, the board is faulty. Replace the 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.227 ODU_OCI
Description
The ODU_OCI is an alarm indicating no connection at the optical demultiplexing unit (ODU)
layer.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the alarm are as follows:
l Severer alarms occur on the local NE, such as the R_LOS, FEC_LOF, and OTU_AIS
alarms.
l Upstream services are damaged.
l The board is faulty.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS,
occur on the local NE. If yes, clear these alarms first. Then, check whether the ODU_OCI
alarm is cleared.
Step 2 If the alarm persists, upstream services may be faulty. If the upstream device is an OSN
device, replace the line board. If the upstream device is not an OSN device, add cross-
connections for the downstream ODU channel that has received the ODU_OCI alarm
according to the related alarm handling document.
Step 3 If the alarm persists, the local board is faulty. Then, replace the local 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.228 ODU_SNCP_STA_INDI
Description
Status indication of an ODUk SNCP protection group. This alarm is generated on the board of
the working channel when the working or protection channel of the protection group is faulty
or a user runs an external switching command, or the status is WTR state.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching,
manual switching, or locked switching.
l Cause 2: The services on the working or protection channel of the ODUk SNCP group
are faulty.
l Cause 3: The switching is in the WTR state. After the time specified by WTR Times (s)
elapses, the alarm is cleared.
Procedure
l Cause 1: A user delivers an external switching command.
a. On the U2000, query the switching state of the protection group. If the switching
state is forced switching, manual switching, or locked switching, check whether the
external switching operation is necessary.
b. If the external switching operation is necessary, ignore the alarm.
c. If the external switching operation is unnecessary, deliver a command to clear the
external switching.
l Cause 2: The services on the working or protection channel of the ODUk SNCP group
are faulty.
a. Query whether the related boards for configuring the protection group have the
alarms, for example, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, OTUk_TIM, ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_LTC,
ODUk_TCMn_TIM, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG,
----End
Related Information
For details, see "ODUk SNCP Protection" in the Feature Description.
4.229 ODUk_LOFLOM
Description
Frame alignment signal (FAS) and multiframe alignment signal (MFAS) being abnormal. This
alarm is generated when the upstream frame header does not match the downstream frame
header.
Attribute
Parameters
None
Possible Causes
l The signals transmitted by the corresponding board at the opposite end do not have a
frame structure.
l The input optical power is abnormal.
l The FEC type is incorrectly configured.
l Bit errors in the received signals of the OTU board at the local station are excessive.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If this alarm is
generated, locate the position where the alarm is first generated according to the service flow.
If no alarm exists at the opposite end, the local end is the place where the alarm is first
generated.
Step 2 Check whether the input optical power of the place where the alarm is first generated is within
the permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the optical power is abnormal, handle the alarm
according to the handling procedure of the IN_PWR_HIGH or IN_PWR_LOW alarm.
Step 3 Query the FEC type of the board set on the U2000 to check whether it is consistent with the
FEC type of the board. For specific error correction types, see the Hardware Description. If
they are not consistent, modify the setting on the U2000 to ensure the consistency.
Step 4 Query the performance value of the BIP8 bit errors in the received signals of the board at the
local station. If the BIP8 bit errors are excessive, handle the alarm according to the handling
procedure of the OTUk_DEG or OTUk_EXC alarm.
Step 5 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical port 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.
----End
Related Information
ITU-T G.709
4.230 ODUk_PM_LCK
Description
ODUk PM signals 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. This alarm is generated when the STAT byte value is
"101" during locking.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The signals are locked because they are being tested.
Procedure
Step 1 On the U2000, query and locate the board slot ID, port number, and channel ID on the board
that generates this alarm.
Step 2 Query the board information and set LCK Insertion to Disabled so that the local station does
not insert an LCK signal to the downstream.
----End
Related Information
ITU-T G.709
Related Cases:
l MC-A157 An OptiX OSN 6800 Network Cannot Be Reverted Back to the Working
Channel After Being Restored from an ODUk SNCP Protection Switching, The Board
Reports The ODU_SNCP_PS Alarm
4.231 ODUk_PM_OCI
Description
Indication for an ODUk PM open connection. This alarm is generated when the output port is
not connected to the input port and the STAT byte value is "110".
k indicates the level of rate.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The corresponding board at the upstream station has the ODUk_PM_OCI alarm.
l There is a loopback on the corresponding board at the opposite station.
l The corresponding board at the opposite station has no cross-connection configuration
and the non-intrusive monitoring function at the local station is enabled.
Procedure
Step 1 On the U2000, query whether there is an alarm with a higher severity on the board. If there is,
handle the alarm with higher severity.
Step 2 If the alarm persists, query whether the upstream station generates the alarm. If this alarm is
generated, locate the station where the alarm is triggered according to the service flow.
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 the cross-connection configuration on the corresponding board at
the station where the alarm is triggered. If no cross-connection is configured, check whether
cross-connections need to be configured at the station. If yes, configure cross-connections. If
no, disable the non-intrusive monitoring function at the local station.
Step 5 Check whether the alarm is cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
ITU-T G.709
Related Cases:
l MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of
ODUk SPRing Protection
4.232 ODUk_PM_TIM
Description
Mismatch of the ODUk PM trace identifier. This alarm is generated during control process
when the trace identifier at the opposite end mismatches that at the local end when the TIM
detection is enabled. The system compares the access point identifiers (API) in the input
signals and the expected API.
Based on the configured TIM detection mode, the network architecture can be classified into
the following types.
l For the point-to-point topology, only the source access point identifiers (SAPI) is
compared for the sink of trail termination.
l For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
l For the multipoint-to-multipoint topology, only the destination access point identifiers
(DAPI) is compared for the sink of trail termination.
Attribute
Parameters
None
Possible Causes
l The networking architecture mismatches the TIM detection mode.
l The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to
be received at the local end.
l The fiber connection is incorrect.
l The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for
the local end based on the networking architecture. If the topology is a point-to-point
topology or point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination. If the topology is multipoint-to-multipoint topology, only the DAPI is compared
for the sink of trail termination.
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to
be received at the local end on the U2000. If they are inconsistent, query the received TTI, set
the SAPI and the DAPI of the TTI to be received at the local end to the same as these of the
received TTI.
Step 3 If the alarm persists, check whether the fiber connection between the local port and the
upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber.
Step 4 Check whether the cross-connection configuration is correct. If it is not, correctly configure
the cross-connection.
----End
Related Information
ITU-T G.709
4.233 ODUk_TCMn_AIS
Description
ODUk TCMn alarm indication signal. An AIS signal is transmitted to the downstream,
indicating that a signal failure is detected in the upstream.
k indicates the level of rate.
l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Signals input from the client side contain the ODUk_TCMn_AIS signal.
l The corresponding board at the opposite end transmits the ODUk_TCMn_AIS signals.
l The loopback or cross-connection is configured at the upstream station, or the FEC type
is incorrectly configured.
Procedure
Step 1 On the U2000, 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 Query whether the alarm is reported from the client side. If it is, check the equipment on the
client side.
Step 3 On the U2000, query whether the ODUk_PM_AIS, R_LOS, or R_LOF alarm exists on the
client side of the OTU board at the opposite end. If the alarm exists, check the equipment at
the opposite end.
Step 4 On the U2000, query whether a loopback is configured 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.
----End
Related Information
ITU-T G.709
4.234 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".
Attribute
Parameters
None
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 LOF, LOM,
ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or
ODUk_TCMn_SSF alarm.
Procedure
Step 1 On the U2000, 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 Query whether the alarm is reported on the client side or the WDM side.
l If the alarm is reported on the client side, check the equipment on the client side.
l If the alarm is reported on the WDM side, check whether the corresponding OTU board
at the downstream station receives the LOF, LOM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or ODUk_TCMn_SSF
alarm on the U2000. If it does, handle the corresponding alarm at the downstream
station.
----End
Related Information
ITU-T G.709
4.235 ODUk_TCMn_DEG
Description
ODUk TCMn signal being degraded. When the error detection is in burst mode, this alarm is
generated if signal degradation occurs or the bit error count exceeds the threshold. When the
error detection in Poisson mode, the alarm is generated if signal degradation occurs.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The optical port that reports the alarm is faulty.
l The optical port at the opposite end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 On the U2000, browse alarms of the entire network to determine the slot ID, optical port
number, 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
flow.
Step 3 Check whether the input optical power of the place where the alarm is first generated is within
the permitted range. If it is not, handle the alarm according to the handling procedures of the
IN_PWR_HIGH and 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 40 mm.
l The optical port 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.
Step 5 If the alarm persists, the optical port 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 port on the OTU board at the opposite end may be faulty.
Replace the pluggable optical module on the OTU board or the faulty OTU board.
----End
Related Information
ITU-T G.709
4.236 ODUk_TCMn_EXC
Description
Count of ODUk TCMn section BIP8 errors exceeding the threshold. This alarm is generated
when the number of bit errors exceeds the threshold if the error detection is in the Poisson
mode.
k indicates the rate level.
l For OptiX OSN 8800, its value is 1, 2, 3
l For OptiX OSN 6800, its value is 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 1, 2 or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The attenuation of the received signals is excessively large and the fiber of the
transmission line is abnormal.
l The transmit part of the opposite station is faulty.
l The receive part of the local station is faulty.
Procedure
Step 1 Check whether the received optical power of the port is within the permitted range on the
U2000. If the receive optical power of the board at the local station is excessively low, clear
the alarm according to the handling procedure of the IN_PWR_LOW alarm.
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding port on
the upstream board is within the permitted range on the U2000. If the transmit optical power
of the board at the upstream station is excessively low, clear the alarm according to the
handling procedure of the OUT_PWR_LOW alarm.
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station on the
U2000. Loop back the transmit optical port and receive optical port on the WDM side of the
related board at the upstream station. If the bit errors exist, clear the bit error fault of the
upstream station.
Step 4 If the alarm persists, replace the faulty board at the local station.
----End
Related Information
ITU-T G.709
4.237 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.
k indicates the level of rate.
l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The current line signals are locked for tested.
Procedure
Step 1 On the U2000, query and locate the slot ID, port number, and channel ID of the board that
generates this alarm.
----End
Related Information
ITU-T G.709
4.238 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".
Attribute
Parameters
None
Possible Causes
The TCM at the opposite end is not set as enabled, and there is no TCM source.
Procedure
Step 1 On the U2000, 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 opposite position is correct. If not,
modify the configuration
----End
Related Information
ITU-T G.709
4.239 ODUk_TCMn_OCI
Description
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".
k indicates the level of rate.
l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 opposite station.
l The corresponding board at the opposite station has no or incorrect cross-connection
configuration.
Procedure
Step 1 On the U2000, 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 flow.
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.
----End
Related Information
ITU-T G.709
4.240 ODUk_TCMn_SSF
Description
Failure of ODUk TCMn server-layer signals.
k indicates the level of rate.
l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 enabled.
l The OTUk_SSF alarm is generated.
Procedure
Step 1 Check along the service flow to locate the station that first generates the SSF alarm.
Step 2 If the alarm persists, check whether the OTUk_SSF alarm occurs on the line. If it does, clear
the alarm according to the alarm handling procedure.
----End
Related Information
None
4.241 ODUk_TCMn_TIM
Description
ODUk TCMn trace identifier mismatch. This alarm is generated during control process when
the trail trace identifier at the opposite end mismatches that at the local end when the TIM
detection is enabled.
Based on the configured TIM detection mode, the system compares the access point
identifiers (API) in the input signals and the expected API, and the network architecture can
be classified into the following types:
l For the point-to-point topology, only the source access point identifiers (SAPI) is
compared for the sink of trail termination.
l For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
l For the multipoint-to-multipoint topology, only the destination access point identifiers
(DAPI) is compared for the sink of trail termination.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The networking architecture mismatches the TIM detection mode.
l The trail trace identifier (TTI) sent at the opposite end is inconsistent with the TTI to be
received at the local end.
l The fiber connection is incorrect.
l The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable TIM
detection mode for the local end based on the networking architecture. If the topology is
point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail
termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the
sink of trail termination.
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to
be received at the local end on the U2000. If they are inconsistent, query the received TTI. Set
the SAPI and the DAPI of the TTI to be received at the local end to the same as those of the
received TTI.
Step 3 If the alarm persists, check whether the fiber connection between the local port and the
upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber.
Step 4 Check whether the cross-connection configuration is correct. If it is not, correctly configure
the cross-connection.
----End
Related Information
ITU-T G.709
4.242 ODUKSP_PS
Description
The ODUKSP_PS is an alarm indicating the ODUk SP protection switching. This alarm is
generated when the ODUk SP protection group actuates switching in which the current
channel switches to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or
manual switching. Such a command makes the current channel of the ODUk SP
protection group switch to the protection channel from the working channel. Hence, the
alarm is reported.
l Cause 2: The services of the working channel of the ODUk SP protection group are
faulty. The active channel automatically switches to the protection channel and the alarm
is reported.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching or manual switching, check whether the external switching operation is
necessary:
1. If the external switching operation is necessary, ignore the alarm.
2. If the external switching operation is unnecessary, issue an external command to switch
the current channel to the working channel, thus clearing the alarm.
Step 2 If the alarm is generated due to the automatic switching of the protection group:
1. Query whether the related boards for configuring the protection group have alarms
relevant to the services, such as R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG and
ODUk_TCMn_EXC. If yes, handle the alarms by referring to the corresponding alarm
handling procedures.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, after the time specified by WTR Times elapses the current channel automatically
switches to the working channel and the alarm is cleared. If the attribute is Non-
Revertive, set it to Revertive, and after the time specified by WTR Times elapses the
alarm is cleared.
----End
Related Information
The ODUk SPRing protection mainly applies to the ring network with distributed services.
This protection uses two different ODUk channels to achieve the protection of multiple
distributed services between all stations. For OptiX OSN 8800 and OptiX OSN 6800, see
"ODUk SPRing Protection" in the Feature Description.
Related Cases:
4.243 ODUKSP_STA_INDI
Description
The ODUKSP_STA_INDI is an alarm indicating the state of the ODUk SPRing protection
group. This alarm is reported when the working or protection channel of the protection group
is faulty or a user runs an external switching command.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter Description
Possible Causes
l A user issues an external switching command such as forced switching, manual
switching, or locked switching.
l The services of the working or protection channel of the ODUk SP protection group are
faulty.
l The switching is in the WTR state. After WTR Times, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching, manual switching, or locked switching, check whether the external
switching is necessary:
1. If the external switching is necessary, ignore the alarm.
2. If the external switching is unnecessary, issue a switching clearing command to clear the
external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
1. Check whether service related alarms such as R_LOS, R_LOC, HARD_BAD,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI,
Step 3 On the U2000, query the switching state of the protection group. If the switching is in the
WTR state, the alarm requires no handling. After the time specified by WTR Times elapses,
the alarm is cleared.
----End
Related Information
The ODUk SPRing protection mainly applies to the ring network with distributed services.
This protection uses two ODUk channels to achieve the protection of multiple distributed
services between all stations. For OptiX OSN 8800 and OptiX OSN 6800, see "ODUk
SPRing Protection" in the Feature Description.
4.244 OH_LOOP
Description
The OH_LOOP is an alarm indicating an overhead bus loopback on a line board.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
A loopback occurs on the overhead bus of the line board.
Procedure
Step 1 Release the loopback, and the alarm is automatically cleared.
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.245 OLP_PS
Description
Optical line protection switching. This alarm is generated when the optical line protection
group undergoes switching and the active channel switches to the protection channel from the
working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching or
manual switching. Such a command makes the active channel of the optical line
protection group switch to the protection channel from the working channel.
l Cause 2: The receive optical power of the working channel of the optical line protection
group is abnormal. As a result, the current channel automatically switches to the
protection channel and the alarm is reported.
l Cause 3: The difference between the optical power on the working channel and that on
the protection channel exceeds the threshold.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching or manual switching, check whether the external switching operation is
necessary:
1. If the external switching operation is necessary, ignore the alarm.
2. If the external switching operation is unnecessary, issue an external command to switch
the active channel to the working channel, thus clearing the alarm.
Step 2 If the alarm is generated due to the automatic switching of the protection group:
1. Query whether the input optical power of the working channel is within the permitted
range on the U2000. If the optical power is not within the normal range, handle the alarm
according to the handling procedure of the IN_PWR_LOW alarm to make the input
optical power of the working channel be within the permitted range.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
it is, after the time specified by WTR Times elapses the active channel automatically
switches to the working channel and the alarm is cleared. If the attribute is Non-
Revertive, set the attribute to Revertive, and after the time specified by WTR Times
elapses the alarm is cleared.
Step 3 If the alarm persists, check whether the POWER_DIFF_OVER alarm is generated. If it is,
handle the alarm according to the corresponding handling procedure.
----End
Related Information
Optical line protection (OLP) protects line fibers between adjacent stations by using the dual
fed and selective receiving function of OLP boards. For details, see "Optical Line Protection"
in the Feature Description.
4.246 OLP_STA_INDI
Description
Status indication of an optical line protection group. This alarm is generated when the
working or protection channel of the protection group is faulty or a user runs an external
switching command.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l A user delivers an external switching command such as forced switching, manual
switching, or locked switching.
l The services on the working channel or protection channel of the optical line protection
group are faulty.
l The switching is in the WTR state. After the WTR time elapses, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching, manual switching, or locked switching, check whether the external
switching is necessary:
1. If the external switching is necessary, ignore the alarm.
2. If the external switching is unnecessary, deliver a switching clearing command to clear
the external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
1. Query whether the input optical power of the working or protection channel is within the
permitted range on the U2000. If the optical power is not within the permitted range,
handle the alarm according to the handling procedure of the IN_PWR_LOW alarm to
make the input optical power of the working or protection channel be within the
permitted range.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
it is, after the time specified by WTR Times elapses the active channel automatically
switches to the working channel and the alarm is cleared. If the attribute is Non-
Revertive, set the attribute to Revertive, and after the time specified by WTR Times
elapses the alarm is cleared.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in the
WTR state. This alarm requires no handling. After the WTR time elapses, the alarm is
cleared.
----End
Related Information
Optical line protection (OLP) protects line fibers between adjacent stations by using the dual
fed and selective receiving function of OLP boards. For details, see "Optical Line Protection"
in the Feature Description.
4.247 OMS_BDI
Description
Backward defect indication at the OMS layer. This alarm is generated to suppress the
OMS_BDI_P and OMS_BDI_O alarms when the two alarms coexist.
Attribute
Parameters
None
Possible Causes
The OMS_BDI_P and OMS_BDI_O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS, OTS_LOS_O, OTS_TIM or OMS_LOS_P alarm is generated
at the opposite station and all downstream stations. If it is, clear the OTS_LOS, OTS_LOS_O,
OTS_TIM or OMS_LOS_P alarm by following proper handling procedures.
----End
Related Information
None
4.248 OMS_BDI_O
Description
Backward defect indication (overhead) at the OMS layer. This alarm is generated when the
local station receives the OMS_BDI_O signal inserted back by the downstream station after
the downstream station detects no overhead signals.
Attribute
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The local station receives the BDI_O overhead signal inserted back to the OMS layer by
the downstream station when the downstream station detects no overhead signals
because of a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_O alarm is generated at the opposite station and all
downstream stations. If it is, clear the OTS_LOS_O alarm by following proper handling
procedures.
----End
Related Information
None
4.249 OMS_BDI_P
Description
Backward defect indication (payload) at the OMS layer. This alarm is generated when the
local station receives the OMS_BDI_P signal inserted back by the downstream station after
the downstream station receives no payload signals from the local station.
Attribute
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
The local station receives the BDI_P overhead signal inserted back to the OMS layer by the
downstream station when the downstream station detects no overhead signals because of a
fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_P or OMS_LOS_P alarm is generated at the opposite station
and all downstream stations. If it is, clear the OTS_LOS_P or OMS_LOS_P alarm by
following proper handling procedures.
----End
Related Information
None
4.250 OMS_FDI_O
Description
Forward defect indication (overhead) at the OMS layer. This alarm is generated when the
downstream station receives the OMS_BDI_O signal inserted by the local station after the
OTS-layer board at local station detects loss of overhead signals and cannot send overhead
signals to the downstream station.
Attribute
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The FDI_O overhead signal is inserted to the OMS layer of the downstream station when
the local station detects no overhead signals because of a fiber cut, low optical power, or
dispersion. This alarm is generated when the downstream station receives the FDI_O
overhead signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_O alarm is generated at the opposite station and all
downstream stations. If it is, clear the OTS_LOS_O alarm by following proper handling
procedures.
----End
Related Information
None
4.251 OMS_FDI_P
Description
Forward defect indication (payload) at the OMS layer. This alarm is generated when the
downstream station receives the OMS_FDI_P signal inserted to the downstream station after
the OTS-layer board at the local station detects loss of overhead signals and cannot send
overhead signals to the downstream station.
Attribute
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
The FDI_P overhead signal is inserted to the OMS layer of the downstream station when the
local station detects loss of payload signals because of a fiber cut, low optical power, or
dispersion. This alarm is generated when the downstream station receives the FDI_P overhead
signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_P alarm is generated at the opposite station and all upstream
stations. If it is, clear the OTS_LOS_P alarm by following proper handling procedures.
----End
Related Information
None
4.252 OMS_LOS_P
Description
Loss of signal (payload) at the OMS layer. This alarm is generated when the OTU board
detects the LOS alarm but there is no OTS_LOS_P alarm at the OTS layer.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the physical fiber connection.
The OMS layer detects no payload signals because of there is a fiber cut, low optical power,
or dispersion.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Verify that the actual fiber connection between the board that reports this alarm and the FIU
board is correct.
Step 3 Check whether the OTS_LOS alarm is reported on the FIU board. If it is, clear the alarm
according to the procedure for handling OTS_LOS.
Step 4 Check whether the MUT_LOS alarm is generated at the local station and on upstream boards.
l If yes, clear the alarm according to the procedure for handling MUT_LOS.
l If no, replace the faulty board at the local station.
----End
Related Information
None
4.253 OMS_LOSS_ACCUM_ABN
Description
Abnormal accumulated span loss. This alarm is generated when the actual span loss is
different from the gain compensation value and the accumulated difference of all spans
exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Because of line fiber aging and environment temperature changes, the accumulated difference
between span loss and the gain compensation value exceeds the threshold.
Procedure
Step 1 Check whether the line fiber connections are normal and whether the fibers are aged, and
whether the fiber connectors are clean.
Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the VOA
attenuation to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively
low, set the alarm threshold according to the plan of the live network.For details about the
method of setting the alarm thresholds, see Configuring the OD Monitoring Function. Among
the threshold parameters, Line Attenuation Compensation Threshold(dB) indicates the
threshold for the difference between the loss of optical transmission section (OTS) and OA
gain.
Step 4 Check whether the insertion loss of the board is normal.
----End
Related Information
None
4.254 OMS_LOSS_MON_FAIL
Description
OMS loss monitoring failure alarm. This alarm is generated when OMS loss monitoring (of
the OD function) and ALC function are configured at the same time.
Attribute
Parameters
None
Possible Causes
OMS loss monitoring and ALC function are configured at the same time. A conflict occurs
and therefore span loss monitoring fails.
Procedure
Step 1 When enabling OMS loss monitoring, cancel the ALC configuration on the subnet that is
monitored.
----End
Related Information
None
4.255 OMS_PMI
Description
OMS-layer payload loss alarm. This alarm is generated when an OMS_PMI signal is detected
from the opposite station.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
A board at the OMS layer on the opposite station does not emit light or is faulty.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check for boards that do no emit light or are faulty at the OMS layer of the opposite station
and all upstream stations. If it is, replace the faulty boards.
----End
Related Information
None
4.256 OMS_PWR_ADJ_FAIL
Description
OMS loss compensation adjustment failure. This alarm is generated when OMS loss
compensation adjustment fails.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The logical fiber connections are inconsistent with the physical fiber connections.
l The margin at the adjustment point on the link does not address the requirements for
matching between the gain and attenuation.
l A board is malfunctioning.
Procedure
Step 1 Check whether the logical fiber connection configured for the optical port where the alarm is
generated is consistent with its physical fiber connection. If it is not, modify the configuration
of the logical fiber connection so that the logical fiber connection is consistent with the
physical fiber connection. For details, see "Checking Logical Fibers".
Step 2 Check whether there is a margin for the adjustment point, and whether the line design is
appropriate.
Step 3 If the adjustment times out, re-start adjustment.
----End
Related Information
None.
4.257 OMS_SSF
Description
Server signal failure at the OMS layer. This alarm is generated to suppress the OMS_SSF_P
and OMS_SSF_O alarms when the two alarms coexist.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The OMS_SSF_P and OMS_SSF_O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS, OTS_TIM, OTS_LOS_P, or OTS_LOS_O alarm is reported
on the FIU connected to the local board. If it is, clear the OTS_LOS, OTS_TIM,
OTS_LOS_P, or OTS_LOS_O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether the OTS_LOS, OTS_TIM, OTS_LOS_P, or OTS_LOS_O
alarm is generated at the opposite station and all upstream stations. If it is, clear the
OTS_LOS, OTS_TIM, OTS_LOS_P, or OTS_LOS_O alarms by following proper handling
procedures.
----End
Related Information
None
4.258 OMS_SSF_O
Description
Server signal (overhead) failure at the OMS layer. This alarm is generated when the OTS
layer detects the failure of the overhead signals, or receives the OMS_FDI_O signal from the
upstream station.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l Because of a fiber cut, low optical power, or dispersion, the OTS layer cannot detect
overhead signals and the OMS layer receives an overhead signal failure message from
the OTS layer.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the OTS_LOS_O or OOS_LOST alarm is reported on the FIU connected to
the local board. If it is, clear the OTS_LOS_O, or OOS_LOST alarm by following proper
handling procedures.
Step 3 If the alarm persists, check whether the OTS_LOS_O or OOS_LOST alarm is generated at the
opposite station and all upstream stations. If it is, clear the OTS_LOS_O or OOS_LOST
alarm by following proper handling procedures.
----End
Related Information
None
4.259 OMS_SSF_P
Description
Server signal fails (payload) at the OMS layer. This alarm is generated when the OTS layer
detects the failure of the payload signals or receives the OMS_FDI_P signal from the
upstream station.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
Because of a fiber cut, low optical power, or dispersion, the OTS layer cannot detect signals
and the OMS layer receives a payload signal failure message from the OTS layer.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether OTS_LOS_P alarm is generated on the FIU connected to the local board. If it
is, clear the OTS_LOS_P alarm by following proper handling procedures.
Step 3 If the alarm persists, check whether the OTS_LOS_P alarm is generated at the opposite
station and all upstream stations. If it is, clear the OTS_LOS_P alarms by following proper
handling procedures.
----End
Related Information
None
4.260 ONE_PUMP_WORK
Description
Single pump card working alarm. The alarm indicates that only one pump card is working
currently. There is no backup card, or the backup pump card is not started or cannot properly
work.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l One pump card is working, and the other pump card is not inserted.
l One pump card is working, and the other pump card is not started (the laser is not turned
on).
l One pump card is working, and the other pump card is disabled.
l One pump card is working, and the other pump card is faulty.
Procedure
Step 1 On U2000, query for the optical port on which the alarm is reported.
l If the alarm is reported on optical port 9, only pump card A is working.
l If the alarm is reported on optical port 10, only pump card B is working.
Step 2 According to the step 1, check if there is a card in the slot where no card is working.
l If there is no card, insert a card with a proper type.
l If there is a card in the slot, enable the laser of the pump card on the U2000. A user can
also press the Reset button on the pump card on site to enable the laser.
Step 3 If the alarm persists, check whether there are other alarms on the U2000. If yes, see the proper
procedure of the corresponding alarms to clear the alarms.
Step 4 If the alarm persists, the pump card might be faulty. Replace the card.
----End
Related Information
None
4.261 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm is
generated when the phase-locked loop on the clock board becomes faulty.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The board hardware of the phase-locked loop is damaged.
Procedure
l The board hardware of the phase-locked loop is damaged.
a. Perform a cold reset on the board. Then, check whether the alarm is cleared. For
details, see Performing Cold Reset of a Board in the Supporting Tasks.
b. If the alarm persists, replace the clock board. For details, see the Parts
Replacement.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.262 OOS_LOST
Description
Loss of OTM overhead signal (OOS). This alarm is generated when the local station receives
no overhead signals in 10 consecutive seconds and there is no OTS_LOS_O alarm.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The local station receives no overhead signals in 10 consecutive seconds because the
opposite station sends no overhead signals.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether the opposite station supports the optical line supervision (OLS) function.
l If no, this alarm does not need to be handled.
l If yes, make sure that the opposite station sends the correct overhead signals.
----End
Related Information
None
4.263 OPA_FAIL_INDI
Description
Failure in automatic power adjustment of optical cross-connections. The alarm is generated
when the calculated attenuation exceeds the adjustment range of the board during an
automatic optical power adjustment.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l Cause 1: The optical power budget is insufficient.
l Cause 2: The attenuation of the configured VA1 or VA4 board is manually modified.
l Cause 3: When there are adjustment points of multiplexed wavelengths and each single
wavelength in OPA scenarios, the attenuation of the VOAs at the multiplexed
wavelength adjustment points is not adjusted to the minimum value. For example, in the
OPA application scenario, the built-in VOAs on multiplexer or demultiplexer boards or
optical add/drop multiplexer (OADM) boards adjust single wavelengths, and the VA1 or
VA4 boards on the line side or the built-in VOAs adjust multiplexed wavelengths.
Procedure
l Cause 1: The optical power budget is insufficient.
a. Use OA boards with larger optical power, and modify the rated input and output
optical power of the OA boards. For details, see "Setting the Rated Optical Power
of the OA Board" in the Commissioning Guide.
l Cause 2: The attenuation of the configured VA1 or VA4 board is manually modified.
a. Change the optical cross-connection mode from automatic to manual and change
the mode to automatic again. An OPA adjustment will be triggered after the mode is
changed from manual to automatic. Therefore, check whether services are
configured on the trail where the OPA applies before you change the mode.
l Cause 3: When there are adjustment points of multiplexed wavelengths and each single
wavelength in the automatic optical power adjustment scenario, the attenuation of the
VOAs at the multiplexed wavelength adjustment points is not adjusted to the minimum
value.
a. On the U2000, adjust the attenuation of the VOAs on the VA1 or VA4 board or an
OA board to the minimum value, change the mode of all optical cross-connections
on the trail from automatic to manual, and change the mode to automatic again. An
OPA adjustment will be triggered after the mode is changed from manual to
automatic. Therefore, check whether services are configured on the trail where the
OPA applies before you change the mode.
----End
Related Information
None
4.264 OPU1_VCAT_SQM
Description
OPU1 sequence identifier mismatch. This alarm is generated when the received OPU1
sequence identifier (SQ) value is not consistent with the expected value. For example, the SQ
values of channels 1-4 on the system side are 0-3 respectively. When the services from
channel 1 are connected to channel 2 on the system side of the opposite TDX, the received SQ
value is 0 and the SQ value to be received is 1.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the cross-connection sequence of the virtual concatenated OPU1 at the local
end mismatches that at the opposite end. If it does not, re-configure the virtual concatenated
OPU1s at the local end.
----End
Related Information
Each channel on the WDM side has an SQ value. The SQ values of optical ports are in
ascending order. Compare the SQ value of the frame in each WDM-side optical port with that
of its previous frame. If mismatch is found, the SQ mismatch alarm of the optical port is
reported. If the SQ values of two optical ports are the same, the board also reports the SQ
mismatch alarm.
4.265 OPU1_VCAT_VcPLM
Description
OPU1 virtual concatenation payload mismatch. This alarm is generated when the type of the
OPU1 virtual concatenation payload received mismatches the expected type. Each service
type corresponds to a VcPt value. For 10GE LAN, the value is 5. For STM-64, the value is 3.
When two TDX boards are interconnected, the alarm is generated if the service types at the
two ends mismatch.
Attribute
Parameters
None
Possible Causes
l Service type configuration is incorrect.
l Cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the VcPt value to be received at the local end is consistent with the received
VcPt value. If it is not, check whether the service type at the opposite end is consistent with
that at the local end. Re-configure the cross-connect service of the interconnected TDX board.
Step 2 If the alarm persists, check whether the VcPt value of the services transmitted from the
opposite end is consistent with the VcPt value to be received at the local end. If it is not, re-
configure the cross-connect service at the opposite end.
----End
Related Information
ITU-T G.709
4.266 OPU4_LOOMFI
Description
Loss of OPU4 multiframe. The alarm is generated when the information about the upstream
OPU4 multiframe head does not match the information about the downstream OPU4
multiframe.
Attribute
Parameters
None
Possible Causes
l The input optical power is abnormal.
l Bit errors in the received signals of the OTU board at the local station are excessive.
l The fiber of the transmission line is abnormal.
l The board is faulty.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If this alarm is
generated, locate the position where the alarm is first generated according to the service flow.
If no alarm exists at the opposite end, the local end is the place where the alarm is first
generated.
Step 2 Check whether the input optical power of the place where the alarm is first generated is within
the permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the optical power is abnormal, handle the alarm
according to the handling procedure of the IN_PWR_HIGH or IN_PWR_LOW alarm.
Step 3 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical port 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.
Step 4 If the alarm persists, the board may be faulty. Replace the board.
----End
Related Information
ITU-T G.709
4.267 OPUk_CSF
Description
Client-side signal failure. This alarm is generated when the client-side signals of the remote
end fail. In this case, the OPU overhead is inserted at the local end and then an alarm is
reported, indicating the signal failure.
k indicates the rate level and its value is 0, 1, 2 or FLEX.
Attribute
Parameters
None
Possible Causes
An R_LOS or a PORT_MODULE_OFFLINE alarm is generated on the client side of the
remote end.
Procedure
Step 1 On the U2000, check whether an R_LOS or a PORT_MODULE_OFFLINE alarm is
generated on the client side of the remote end. If it is, clear the alarm.
----End
Related Information
ITU-T G.709
4.268 OPUk_MSIM
Description
OPUk multiplex structure identifier mismatch.
Attribute
Parameters
None
Possible Causes
l Cause 1: Bit errors in services cause damages to overheads.
l Cause 2: Two boards interconnected on the WDM side have inconsistent cross-
connection configurations and therefore their multiplexing structures are inconsistent.
Procedure
Step 1 Check for alarms related to bit errors. If any alarm related to bit errors is present,
preferentially handle the alarm to eliminate the bit errors.
Step 2 Check whether the board that reported the OPUk_MSIM alarm and the interconnected board
have consistent cross-connection configurations. If their cross-connection configurations are
inconsistent, change the configurations to be consistent.
----End
Related Information
ITU-T G.709
4.269 OPUk_PLM
Description
OPUk payload mismatch. The type of received payload mismatches the expected payload
type defined in the adaptation function.
k indicates the level of rate.
l For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The payload types in the data on the WDM side of the interconnected boards mismatch.
Procedure
Step 1 On the U2000, check whether the PT byte value to be received at the OPU layer of the local
board is consistent with that of the received PT bytes.
Step 2 Check whether the WDM-side fiber connection is correct according to the engineering fiber
connection diagram. If the fiber connection is incorrect, correctly connect the fiber according
to the engineering fiber connection diagram.
Step 3 Check whether the service type on the client side of the local board is the same as that of the
peer board. If the service types on the local board and peer board are not the same, set the
service types again based on the network plan to ensure that they are the same.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709
4.270 ORP_CRITICAL_HI
Description
Excessively high reflection power. This alarm is generated when the reflection power exceeds
threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The loss of the local-end fiber splicing point in the upstream of the board is excessively
large.
l The fiber near the ERPC board is over-bent or pressed.
l The connector of the fiber near the board is unclean.
l The connector of the fiber near the board is incorrectly inserted.
l The output optical power of the board is excessively high.
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Check whether the
fiber near the Raman board is properly connected. If it is not, reconnect it.
Step 2 Check whether the fiber near the Raman board is over-bent or pressed. If it is not, spool the
fiber again. If the fiber is broken because of the press, replace it or repair it by means of
splicing.
Step 3 Check whether the end face of the fiber near the Raman board is clean. If it is not, clean it
again and properly connect the fiber.
Step 4 On the U2000, check the set output optical power of the board and properly adjust the output
optical power in the permitted range.
Step 5 Turn on the pump laser on the port of the Raman board and check whether the alarm is
cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.271 OSC_CLK_MISMATCH
Description
This is an OSC clock conflict alarm. When the IEEE 1588 protocol is enabled on the
TN11AST2 board and the board is in the clock source priority table, but the TN11AST2 board
and the clock board or cross-connect board mismatch, this alarm will be reported.
Attribute
Alarm Severity Alarm Type
Warning Communication
Parameters
None
l If the system does not require the IEEE 1588 clock function, replacing the OSC board
(TN11AST2) has no impact on services.
l If the system needs to enable the IEEE 1588 clock function, the system control and
cross-connect board or clock board needs to be replaced, which has impact on services.
Possible Causes
The prerequisites for generating the OSC_CLK_MISMATCH alarm are that the IEEE 1588
protocol is enabled on the TN11AST2 board and the board is in the clock source priority
table. The possible causes of the alarm are as follows:
l The TN16XCH, TN16SCC, or TN16UXCM board is installed on the OptiX OSN 8800
T16 subrack.
l The TN52STG board is installed on the OptiX OSN 8800 T32 subrack.
l The TNK2STG board is installed on the OptiX OSN 8800 T64 subrack.
l The TN11STG/TN12STG board is installed on the OptiX OSN 6800 subrack.
l The TN11STG/TN12STG boards are installed on the UPS subrack.
Procedure
Step 1 On the U2000, query the board that reports this alarm.
l If the system does not require the IEEE 1588 clock function, you are advised to replace
the OSC (TN11AST2) board or disable the IEEE 1588 clock function of the TN11AST2
board.
l If the system needs to enable the IEEE 1588 clock function, replace the system control
and cross-connect board or clock board that reports this alarm. The configurations of the
clock board to be replaced are as follows:
a. For an OptiX OSN 8800 T16 subrack, replace the system control and cross-connect
board using a board except TN16XCH, TN16SCC, or TN16UXCM, and ensure that
no clock board is available on the subrack.
b. For an OptiX OSN 8800 T32 subrack, replace the TN52STG board using
TN54STG.
c. For an OptiX OSN 8800 T64 subrack, replace the TNK2STG board using
TNK3STG.
d. For an OptiX OSN 6800 subrack, replace the TN11STG or TN12STG board using
TN13STG.
e. For the UPS subrack, replace the TN11STG or TN12STG board using TN13STG.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
None
4.272 OSC_BDI
Description
Backward defect indication. This alarm is generated when a signal failure is detected and the
BDI byte value is 1.
Attribute
Parameters
None
Possible Causes
The BDI bit in the overhead field (byte 3, bit 5) is "1" for 5 consecutive frames.
Procedure
Step 1 Query whether an alarm with a higher severity is generated on the board on the U2000. If it is,
handle the alarm with a higher severity.
Step 2 If the alarm persists, check whether the corresponding board at the downstream site receives
the R_LOS or R_LOF alarm on the U2000. If it does, handle the corresponding alarm at the
downstream site.
----End
Related Information
None
4.273 OSC_DEG
Description
Signal degrade alarm. This alarm is generated when bit errors are of burst distribution and the
signal degrade or bit error count crosses the threshold.
Attribute
Parameters
None
Possible Causes
l The optical port at the local end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the input optical power of the board is within the permitted range. For the
optical power specifications of the specific board, see "Technical Specifications" in the
Product Description. If the optical power is not within the permitted range, handle the alarm
with reference to the handing procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms.
Step 2 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical port 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.
Step 3 If the alarm persists, the board may be faulty. Replace the board.
----End
Related Information
None
4.274 OSC_RDI
Description
Remote defect. This alarm is generated when the peer site returns the RDI alarm to the local
site after receiving an R_LOF alarm.
Attribute
Parameters
None
Possible Causes
l The peer site returns the RDI alarm to the local site after receiving the R_LOF signal.
l The optical fiber is damaged.
l The board is faulty.
Procedure
Step 1 Query whether the R_LOF alarm is generated at the peer site. If it is not, clear the OSC_RDI
alarm with reference to the handling procedure of the R_LOF alarm.
Step 2 If the alarm persists, check whether the fiber between the two sites is damaged. If it is, repair
the fiber.
----End
Related Information
None
4.275 OSNR_LOSS_UNBALANCED
Description
Unbalanced OSNR loss flatness alarm. This alarm is generated when the difference between
the OSNR loss of monitored wavelengths and the average loss exceeds the threshold.
Attribute
Parameters
None
Possible Causes
Because of abnormal wavelength attenuation adjustment and line condition changes, the
OSNR loss flatness of monitored wavelengths on an OMS is abnormal.
Procedure
Step 1 Check whether the boards and fiber connections are normal.
----End
Related Information
None
4.276 OTS_BDI
Description
Backward defect at the OTS layer. This alarm is generated to suppress the OTS_BDI_P and
OTS_BDI_O alarms when the two alarms coexist.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
l The logical fiber connection is not consistent with the actual fiber connection.
l The peer site reports the OTS_LOS alarm and inserts BDI signals back to the local site.
Procedure
Step 1 Check whether the logical fiber connection of the FIU board is consistent with the actual fiber
connection. If it is not, modify the logical fiber connection to make it consistent with the
actual fiber connection.
Step 2 Check whether the OTS_TIM or OTS_LOS alarm is generated at the peer site. If it is, clear
the OTS_TIM or OTS_LOS alarm by following proper handling procedures.
Step 3 If the alarm persists, check and make sure that fibers connected to the receive ports on the
local FIU are correct and no fiber is disconnected.
----End
Related Information
None
4.277 OTS_BDI_O
Description
Backward signal (overhead) defect at the OTS layer. This alarm is generated when the local
site receives the OTS_BDI_O signal inserted by the upstream site.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
The peer site inserts the BDI_O signal back to the local site when detecting no overhead
signals because of a fiber cut, low optical power, or dispersion. This alarm is generated when
the local site receives the BDI_O signal.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 If the alarm persists, verify that the fiber connection of the "RM" port on the local FIU board
is correct and no fiber is disconnected.
Step 3 Check whether the OTS_LOS_O alarm is generated on the peer FIU board. If it is, handle the
alarm by following proper handling procedures.
----End
Related Information
None
4.278 OTS_BDI_P
Description
Backward defect (payload) at the OTS layer. This alarm is generated when the local site
receives the OTS_BDI_P signal inserted back by the downstream site.
Attribute
Alarm Severity Alarm Type
Warning Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
The peer site inserts the BDI_P signal back to the local site, when detecting no payload signal
because of a fiber cut, low optical power, or dispersion. This alarm is generated when the
local site receives the BDI_P signal.
Procedure
Step 1 Check whether the logical fiber connection of the FIU board is consistent with the actual fiber
connection. If it is not, modify the logical fiber connection to make it consistent with the
actual fiber connection.
Step 2 If the alarm persists, verify that fiber connections of the receive ports of the local FIU board
are correct and no fiber is disconnected.
Step 3 Check whether the OTS_LOS_P alarm is generated on the peer FIU board. If it is, clear the
OTS_LOS_P alarm by following proper handling procedures.
----End
Related Information
None
4.279 OTS_LOS_O
Description
Loss of signals (overhead) at the OTS layer. This alarm is generated when the OSC board
connected to the "TM" port of the FIU board detects LOS signals.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
This alarm is generated when the OTS layer of the receive end detects no overhead signal
because of a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection of the FIU board is consistent with the actual fiber
connection. If it is not, modify the logical fiber connection to make it consistent with the
actual fiber connection.
Step 2 If the alarm persists, verify that the fiber connection between the "TM" port of the local FIU
board and the OSC board is correct and no fiber is disconnected.
Step 3 If the alarm persists, verify that the fiber connection between the "RM" port of the peer FIU
board and the OSC board is correct and no fiber is disconnected.
Step 4 If the alarm persists, check whether the laser of the OSC board at the peer site is on. If it is
not, turn on the laser of the OSC board.
----End
Related Information
None
4.280 OTS_LOS_P
Description
Loss of signals (payload) at the OTS layer. This alarm is generated when the OA board or
other boards connected to the transmit port of the FIU detects the LOS signals.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
This alarm is generated when the OTS layer of the receive end detects no payload signal
because of a fiber cut, low optical power, or dispersion.
Procedure
Step 1 Check whether the logical fiber connection of the FIU board is consistent with the actual fiber
connection. If it is not, modify the logical fiber connection to make it consistent with the
actual fiber connection.
Step 2 If the alarm persists, verify that the fiber connections of all ports on the local FIU board are
correct and no fiber is disconnected.
----End
Related Information
None
4.281 OTS_PMI
Description
OTS-layer payload loss alarm. This alarm is generated when an OTS_PMI signal is detected
from the peer site.
Attribute
Parameters
None
Possible Causes
l Cause 1: A board at the OTS layer on the peer site does not emit light or is faulty, and
therefore inserts the OTS_PMI overhead in the downstream direction.
l Cause 2: On an ASON network, a service board at the peer site does not carry services
and an OA board emits white light (without signal frames).
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If it
is not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 If the alarm persists, check whether the OTS_LOS_P alarm is generated at the local site and
all upstream sites, or whether the BD_STATUS alarm is generated at the OTS-layer boards. If
so, clear the OTS_LOS_P or BD_STATUS alarm using the related alarm handling procedure.
If not, go to the next step.
Step 3 If the OTS_PMI alarm is caused by cause 2, no action is required. The alarm automatically
clears after the ASON services are groomed to the related service board at the peer site.
----End
Related Information
None
4.282 OTS_TIM
Description
Mismatch of the trail trace identifier at the OTS layer. This alarm is generated when the API
of the received TTI at the OTS layer is not consistent with the API to be received.
Attribute
Parameters
None
Possible Causes
l The TTI transmitted at the upstream site is not consistent with the TTI to be received at
the local site.
l The fiber actual connection is incorrect.
Procedure
Step 1 Check whether the TTI transmitted at the transmit end (upstream site) is consistent with the
TTI to be received at the local end. If it is not, configure the TTI at the upstream site again.
Step 2 Check whether the fiber connection between the OSC and the "RM" or "TM" port of the FIU
board is compliant with the network regulation. If it is not, connect the fibers again.
----End
Related Information
For details about the API and TTI, see ITU-T G.709.
4.283 OTU_AIS
Description
The OTU_AIS is an alarm indicating an optical transponder unit (OTU) alarm.
Attribute
Parameters
None
Possible Causes
l Severer alarms such as the R_LOS and FEC_LOF alarm occur on the local NE.
l Upstream services are damaged.
l The board is faulty.
Procedure
Step 1 On the NMS, check whether severer alarms such as R_LOS and FEC_LOF occur on the local
NE. If yes, clear these alarms first. Then check whether the OTU_AIS alarm is cleared.
Step 2 If the OTU_AIS alarm persists, locate the NE (FR NE) that initially reports the OTU_AIS
alarm. Then repeat the preceding step.
Step 3 If the OTU_AIS persists, check whether severer alarms occur on the upstream NE (PR NE) of
the FR NE. If yes, clear the alarms.
Step 4 If the OTU_AIS alarm persists, perform a loopback on the transmit optical ports of NEs from
the FR NE in the upward direction. Locate the NE (FL NE) that initially reports the
OTU_AIS alarm or severer alarms. You can skip this step because fiber loopback interrupts
services. If fiber loopback is not allowed, replace the receive board on the FR NE and
transmit board on the PR NE.
1. Check whether configurations on the FL NE are correct. If no, correct connections and
configurations.
2. If the OTU_AIS persists, replace the line board on the FL NE.
3. If the OTU_AIS persists, replace the cross-connect board on the FL NE.
----End
Related Information
None
4.284 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame align signal (FAS) at the OTU layer is
lost.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The optical fiber is faulty or the optical power is out of range.
l The board has hardware faults.
l Services that are transmitted from the peer NE are abnormal.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the alarm.
Step 2 Check the input optical power of the board on the NMS. If the input optical power is below
the lower threshold, clean the fiber end and the connector. If the input optical power is above
the upper threshold, add an optical attenuator to adjust the optical power. Then check whether
the alarm is cleared.
Step 3 If the alarm persists, check the output optical power of the peer board. If the optical power is
below the lower threshold, replace the peer board.
Step 4 If the alarm persists, check whether clocks of the local and peer NEs are synchronized with
those on the network. If not, set clock tracing. Then check whether the alarm is cleared.
Step 5 If the alarm persists, check the transmission fiber. If the fiber is functioning properly, replace
the board that reports the alarm.
----End
Related Information
None
4.285 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the frame align signal (FAS) at the OTU layer is
lost.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The local NE has not received the expected consecutive number of frames.
l The bit errors during transmission are excessive.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the alarm.
Step 2 Check the input optical power of the board on the NMS. If the input optical power is below
the lower threshold, clean the fiber end and the connector. If the input optical power is above
the upper threshold, add an optical attenuator to adjust the optical power. Then check whether
the alarm is cleared.
Step 3 If the alarm persists, check the output optical power of the peer board. If the optical power is
below the lower threshold, replace the peer board.
Step 4 If the alarm persists, check whether clocks of the local and peer NEs are synchronized with
those on the network. If not, set clock tracing. Then check whether the alarm is cleared.
Step 5 If the alarm persists, check the transmission fiber. If the fiber is functioning properly, replace
the board that reports the alarm.
Step 6 If the alarm persists, replace the source board of the OTU channel (excluding the NEs that
transparently transmit the ODU channel).
Step 7 If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.286 OTUk_AIS
Description
OTUk alarm indication. An AIS signal travels downstream, which indicates that a signal
failure is detected in the upstream direction.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 1, 2, 3.
l For OptiX OSN 6800, its value is 1, 2, 3, or 5G.
l For OptiX OSN 3800, its value is 1, 2, or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Signals input from the client side contain ODUk_PM_AIS or OTUk_AIS signals.
l The upstream site has a loopback or cross-connection, or the FEC type configuration is
incorrect.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board on the U2000. If there is,
handle the alarm with a higher severity.
Step 2 If the alarm is reported from the client side, check client equipment.
Step 3 On the U2000, query whether the upstream site has any loopback. If it does, release the
loopback.
Step 4 Check whether the configuration of the cross-connection and FEC type is correct at the
upstream site. If the configuration is incorrect, correct the configuration.
----End
Related Information
ITU-T G.709
4.287 OTUk_BDI
Description
OTUk backward defect indication. This alarm is generated when the SM section detects a
signal failure and the value of the BDI byte is 1.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 1, 2, 3.
l For OptiX OSN 6800, its value is 1, 2, 3, or 5G.
l For OptiX OSN 3800, its value is 1, 2, or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l 100G/40G Board 38M crystal oscillator loss effectiveness.
l Signals input from the client side contain the OTUk_BDI alarm.
l The corresponding OTU board at the downstream site receives the LOF, LOM,
OTUk_AIS, OTUk_TIM, or OTUk_SSF alarm.
Procedure
Step 1 On the U2000, query whether an alarm with a higher severity is generated on the board. If it
is, handle the alarm with a higher severity.
Step 2 Query whether the alarm is reported from the client side or the WDM side.
l If the alarm is reported from the client side, check client equipment.
l If the alarm is reported from the WDM side, check whether the corresponding OTU
board at the downstream site receives the LOF, LOM, OTUk_AIS, OTUk_TIM, or
OTUk_SSF alarm by using the U2000. If yes, handle the corresponding alarm at the
downstream site.
----End
Related Information
ITU-T G.709
4.288 OTUk_DEG
Description
The OTUk_DEG is an alarm indicating that the OTUk signal is degraded. When the BIP8
detection is in burst mode, this alarm is generated if the signal degradation or bit error count
exceeds the threshold. When the BIP8 detection in poisson mode, this alarm is generated if
the signal degradation exceeds the threshold.
Attribute
Parameters
None
Possible Causes
l The optical port at the local end is faulty.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. If the optical
power is not within the normal range, handle the alarm with reference to the handing
procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms.
Step 2 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical port 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.
Step 3 If the alarm persists, the board may be faulty. Replace the board.
----End
Related Information
ITU-T G.709
4.289 OTUk_EXC
Description
OTUk bit error count crossing the threshold. This alarm is generated when the BIP8 detection
is in poisson mode and bit error count exceeds the threshold.
Attribute
Parameters
None
Possible Causes
l The attenuation of the received signals is excessively large, and the fiber of the
transmission line is abnormal.
l The receive part of the local site is faulty.
Procedure
Step 1 On the U2000, check whether the receive optical power of the port is within the permitted
range. If the receive optical power of the board at the local site is excessively low, clear the
alarm according to the handling procedure of the IN_PWR_LOW alarm.
Step 2 If the alarm persists, replace the faulty board at the local site.
----End
Related Information
ITU-T G.709
4.290 OTUk_LOM
Description
The OTUk_LOM is an alarm indicating that the multiframe alignment signal (MFAS) is
abnormal. This alarm occurs when the multiframe locating is out of multiframe (OOM) in
three consecutive milliseconds.
k indicates the level of rate.
l For OptiX OSN 8800, its value is 1, 2, 3.
l For OptiX OSN 6800, its value is 1, 2, 3, or 5G.
l For OptiX OSN 3800, its value is 1, 2, or 5G.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The FEC type is incorrectly configured.
l The bit errors in the received signals of the OTU board at the local site are excessive.
l The board at the local site is faulty.
Procedure
Step 1 Query the FEC type of the board set on the U2000 to check whether it is consistent with the
FEC type of the board. If they are not consistent, modify the setting on the U2000 to ensure
the consistency.
Step 2 Query the performance value of the BIP8 bit errors in the received signals of the board at the
local site through the U2000. If the BIP8 bit errors are excessive, handle the alarm with
reference to the handling procedure of the OTUk_EXC or OTUk_DEG alarm.
Step 3 If the alarm persists, the board at the local site may be faulty. Replace the faulty board.
----End
Related Information
ITU-T G.709
4.291 OTUk_TIM
Description
OTUk trail trace identifier (TTI) mismatch. This alarm is generated during the control process
when the TTI at the peer end mismatches that at the local end if the TIM detection is enabled.
The system compares the access point identifiers (APIs) in the input signals and the expected
API.
For the set TIM detection mode, the network architecture can be classified into the following
types:
l For the point-to-point topology, only the source access point identifiers (SAPIs) is
compared for the sink of trail termination.
l For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
l For the multipoint-to-multipoint topology, only the destination access point identifiers
(DAPIs) is compared for the sink of trail termination.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The networking architecture and the TIM detection mode to be configured are not
consistent.
l The TTI sent from the peer end is not consistent with the TTI to be received at the local
end.
l The fiber connection is incorrect.
l The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for
the local end on the U2000 according to networking architecture. If the topology is point-to-
point or point-to-multipoint, only the SAPI is compared for the sink of trail termination. If the
topology is multipoint-to-multipoint, only the DAPI is compared for the sink of trail
termination.
Step 2 If the alarm persists, query whether the TTI sent from the peer end is consistent with that to be
received at the local end on the U2000. If they are not consistent, query the received TTI on
the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to be the
same as these of the received TTI.
Step 3 If the alarm persists, check whether the fiber connection between the local port and the
upstream port is correct. If the fiber connection is incorrect, correctly connect the fiber.
Step 4 Check whether the cross-connection configuration is correct. If it is not, correctly configure
the cross-connection.
----End
Related Information
ITU-T G.709
4.292 OUT_PWR_ABN
Description
The OUT_PWR_ABN is an alarm indicating that the output optical power is abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
The possible causes of the OUT_PWR_ABN alarm are as follows:
Procedure
Step 1 Check whether the wavelength of the input optical signals is within the specified wavelength
range of the input optical signal of the boards, or check whether the boards report the
PUM_BCM_ALM alarm simultaneously. If the wavelength of the input optical signals is
beyond the specified wavelength range, adjust it to a proper value. Then check whether the
OUT_PWR_ABN alarm is cleared.
Step 2 If the alarm persists, replace the board that generates the OUT_PWR_ABN alarm.
----End
Related Information
None
4.293 OUT_PWR_LOW
Description
Output optical power being too low. This alarm is generated when the output optical power of
the laser is excessively low.
Attribute
Parameters
None
Possible Causes
l The laser is aged.
l The board is faulty.
Procedure
Step 1 Use an optical power meter to check whether the transmit optical power of the board is within
the permitted range.
l If the optical power is not within the permitted range, replace the module where the
faulty laser resides. If the alarm persists, replace the board.
l If the optical power is within the permitted range, perform a warm reset and then a cold
reset on the board. If the alarm persists, replace the board.
----End
Related Information
None
4.294 OWSP_PS
Description
The OWSP_PS is an alarm indicating the OWSP protection switching. This alarm is
generated when the OWSP protection group undergoes switching in which the current
channel switches to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or
manual switching. Such a command makes the current channel of the OWSP protection
group switch to the protection channel from the working channel. The alarm is reported.
l Cause 2: The services of the working channel of the OWSP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching or manual switching, check whether the external switching operation is
necessary.
1. If the external switching operation is necessary, ignore the alarm.
2. If the external switching operation is unnecessary, issue an external command to switch
the current channel to the working channel, clearing the alarm.
Step 2 If the alarm is generated during the automatic switching of the protection group,
1. Query whether the related boards for configuring the protection group have service
alarms such as R_LOC and R_LOS. If yes, handle the alarms with reference to the
corresponding alarm handling procedures.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, after WTR Times the current channel automatically switches to the working
channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive, and
after WTR Times the alarm clears.
----End
Related Information
The OWSP applies to ring networks with distributed services. It occupies two wavelengths to
provide protection for one channel of distributed services among all sites. For details, see
"Optical Wavelength Shared Protection (DCP board)" in the Feature Description.
4.295 OWSP_STA_INDI
Description
The OWSP_STA_INDI is an alarm indicating the state of the OWSP protection group. This
alarm is reported when the working or protection channel of the protection group is faulty or
the user runs an external switching command.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l The user issues an external switching command such as the forced switching, manual
switching, or locked switching.
l The services of the working or protection channel of the OWSP protection group are
abnormal.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching, manual switching, or locked switching, check whether the external
switching is necessary.
1. If the external switching is necessary, ignore the alarm.
2. If the external switching is unnecessary, issue a switching clearing command to clear the
external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
1. Query whether the related boards for configuring the protection group have alarms such
as R_LOC and R_LOS. If yes, handle the alarms according to the corresponding alarm
handling procedures.
Step 3 On the U2000, query the switching state of the protection group. If the switching is in the
WTR state, this alarm requires no handling. After the WTR Times, the alarm is cleared.
----End
Related Information
The OWSP applies to ring networks with distributed services. It occupies two wavelengths to
provide protection for one channel of distributed services among all sites. For details, see
"Optical Wavelength Shared Protection (DCP board)" in the Feature Description.
4.296 PASSWORD_NEED_CHANGE
Description
The password of a default user must be changed to reduce risks. This alarm is generated if the
password of any default user is not changed in time.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The password of the default user is never changed.
Procedure
Step 1 Change the default password.
----End
Related Information
None
4.297 PATCH_ACT_TIMEOUT
Description
Patch package activation timeout. This alarm is generated when the duration that a patch
package remains the activated state exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The duration that the patch package remains the activated state exceeds the threshold.
Procedure
Step 1 If the patch file is correct, run the patch file on the U2000 after the end of the observation.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one to the U2000.
----End
Related Information
None
4.298 PATCH_BD_EXCLUDE
Description
Isolation of a patch package board.
Attribute
Parameters
None
Possible Causes
The board loading fails during the loading of patch packages.
Procedure
Step 1 Contact Huawei engineers to perform a rollback or load the patch package again.
----End
Related Information
None
4.299 PATCH_BD_MATCH_FAIL
Description
Patch package matching failure.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The board fails to match the patch package.
Procedure
Step 1 Isolate the board or find out the root cause and match the board to the patch package again.
----End
Related Information
None
4.300 PATCH_CHGSCC_NOTMATCH
Description
Patch inconsistency after the system control board is replaced.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The board patch status is inconsistent with the patch package status after the system control
board is replaced.
Procedure
Step 1 Reselect the patch package and load the patch. The alarm is automatically cleared.
----End
Related Information
None
4.301 PATCH_DEACT_TIMEOUT
Description
Patch package deactivation timeout. This alarm is generated when the duration that a patch
package remains the deactivated state exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The duration that the patch package remains the deactivated state exceeds the threshold.
Procedure
Step 1 If the patch file is correct, activate the patch file on the U2000.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one to the U2000.
----End
Related Information
None
4.302 PATCH_PKGERR
Description
Patch package file error.
Attribute
Parameters
None
Possible Causes
Patch package files were damaged, deleted, or incomplete due to a committing failure.
Procedure
Step 1 Contact Huawei engineers to regenerate the patch package files.
----End
Related Information
None
4.303 PID_AUTO_ADJUST_FAIL
Description
Automatic adjustment failure of PID optical power alarm. This alarm is reported when the
automatic adjustment of PID receive optical power cannot meet requirements.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l The adjusted optical power does not change.
l The margin at the receive-end OA adjustment point is insufficient.
l The single-wavelength optical power is abnormal.
Procedure
Step 1 Check whether the physical fiber connection is correct between the receive-end OA board and
PID board.
Step 3 Check whether the margin at the receive-end power amplification adjustment point meets
requirements and the line design is proper.
Step 4 Check whether the multiplexed-wavelength optical power meets requirements and the single-
wavelength optical power is abnormal.
----End
Related Information
None
4.304 PM_BDI
Description
The PM_BDI is an alarm indicating a backward defect in PM overheads at the optical
demultiplexing unit (ODU) layer. This alarm is generated when a major alarm occurs at the
remote ODU and upper layers.
Attribute
Parameters
None
Possible Causes
l Alarms occur on the remote ODU termination NE.
l The local transmit unit is faulty.
l The remote receive unit is faulty.
Procedure
Step 1 Check whether severer alarms occur on the remote ODU termination NE. If yes, clear these
alarms first. Then check whether the PM_BDI alarm is cleared.
Step 2 If the alarms at the remote end persist, perform an inloop on the local optical ports. If any
alarms occur, correct configurations according to the alarms.
NOTICE
A loopback interrupts services.
Step 4 If the alarms at the remote end persist and the loopback test detects no abnormality on the
local optical ports, replace the remote board.
----End
Related Information
None
4.305 PM_BEI
Description
The PM_BEI is an alarm indicating a backward error in PM overheads at the optical
demultiplexing unit (ODU) layer. This alarm is generated when PM-BIP check bit errors
occur at the remote end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Bit errors occur on the remote ODU termination NE.
l The local transmit unit is faulty.
l The remote receive unit is faulty.
Procedure
Step 1 Check whether bit errors occur on the ODU termination NE. If any bit errors occur, clear
these bit errors. Then check whether the PM_BEI alarm is cleared.
Step 2 If the bit errors at the remote end persist, perform an inloop on the local optical ports to check
for alarms. If any alarms occur, correct configurations according to the alarms.
NOTICE
A loopback interrupts services.
Step 4 If the bit errors at the remote end persist and the inloop test detects no abnormality on the
local optical ports, replace the remote board.
----End
Related Information
None
4.306 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the PM section at
the optical demultiplexing unit (ODU) layer exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The received signals are heavily attenuated.
l The fiber connector is contaminated.
l The connector is incorrectly connected.
l The local receive unit is faulty.
l The peer transmit unit is faulty.
Procedure
Step 1 On the NMS, check for severer alarms such as R_LOS and R_LOF. Clear these alarms first
and check whether the PM_BIP8_OVER alarm is cleared.
Step 2 Check whether the receive optical power of the alarm-reporting board is within the permitted
range. If yes, go to step 9.
Step 3 Clean the local fiber connector and the receive optical port on the line board. Then check
whether the alarm is cleared.
Step 4 Check whether the fiber adapter is correctly connected to the optical attenuator on the local
NE, and whether the attenuation value specified for the optical attenuator is proper. After
determining that the fiber adapter and optical attenuator are used properly, check whether the
alarm is cleared.
Step 5 Check whether the transmit optical power atthe peer end is within the permitted range. If not,
replace the line board.
Step 6 If the transmit optical power is within the permitted range, clean the peer pigtail connector.
Then check whether the alarm is cleared.
Step 7 Check whether the fiber adapter is correctly connected to the optical attenuator on the peer
NE, and whether the attenuation value specified for the optical attenuator is proper. After
determining that the fiber adapter and optical attenuator are used properly, check whether the
alarm is cleared.
Step 8 Verify that optical fibers are properly connected. Then check whether the alarm is cleared.
Step 9 Replace the local line board that reports the alarm. Then check whether the alarm is cleared.
Step 10 Replace the local cross-connect board. Then check whether the alarm is cleared.
Step 11 Replace the peer line board. Then check whether the alarm is cleared.
Step 12 Replace the peer cross-connect board. Then check whether the alarm is cleared.
----End
Related Information
None
4.307 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the signals degrade in the PM section at the
optical transponder unit (OTU) layer.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The received signals are heavily attenuated.
l The fiber connector is contaminated.
l The connector is incorrectly connected.
l The local receive unit is faulty.
l The peer transmit unit is faulty.
Procedure
Step 1 On the NMS, check for severer alarms such as R_LOS and R_LOF. Clear these alarms first
and check whether the PM_BIP8_SD alarm is cleared.
Step 2 Check whether the receive optical power of the alarm-reporting board is within the permitted
range. If yes, go to step 9.
Step 3 Clean the local fiber connector and the receive optical port on the line board. Then check
whether the alarm is cleared.
Step 4 Check whether the fiber adapter is correctly connected to the optical attenuator on the local
NE, and whether the attenuation value specified for the optical attenuator is proper. After
determining that the fiber adapter and optical attenuator are used properly, check whether the
alarm is cleared.
Step 5 Check whether the transmit optical power at the peer end is within the permitted range. If not,
replace the line board.
Step 6 If the transmit optical power is within the permitted range, clean the peer pigtail connector.
Then check whether the alarm is cleared.
Step 7 Check whether the fiber adapter is correctly connected to the optical attenuator on the peer
NE, and whether the attenuation value specified for the optical attenuator is proper. After
determining that the fiber adapter and optical attenuator are used properly, check whether the
alarm is cleared.
Step 8 Verify that optical fibers are properly connected. Then check whether the alarm is cleared.
Step 9 Replace the local line board that reports the alarm. Then check whether the alarm is cleared.
Step 10 Replace the local cross-connect board. Then check whether the alarm is cleared.
Step 11 Replace the peer line board. Then check whether the alarm is cleared.
Step 12 Replace the peer cross-connect board. Then check whether the alarm is cleared.
----End
Related Information
None
4.308 PM_TIM
Description
The PM_TIM is an alarm indicating a trail trace identifier (TTI) mismatch in the PM
overheads at the optical demultiplexing unit (ODU) layer.
Attribute
Parameters
None
Possible Causes
The PM_TTI byte to be received by the local NE is incorrectly set.
Procedure
Step 1 Check whether the SM_TTI byte to be received by the board is consistent with the received
SM_TTI byte. If not, modify the settings.
----End
Related Information
None
4.309 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC is an alarm indicating that traffic at Ethernet ports exceeds the
threshold. This alarm is generated when traffic at an Ethernet port exceeds the expected value.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 that the bandwidth utilization rate on an Ethernet port exceeds the
threshold.
l 0x00: the RX direction
l 0x01: the TX direction
Possible Causes
The possible causes of the PORT_EXC_TRAFFIC alarm are as follows:
l Cause 1: The configured value is small for the bandwidth threshold on the Ethernet port.
l Cause 2: The configured Ethernet port traffic is heavy.
Procedure
Step 1 Cause 1: The configured value is small for the bandwidth threshold on the Ethernet port.
1. Query the bandwidth threshold of the Ethernet port on the NMS.
2. If the bandwidth threshold is set low, configure it again to increase the bandwidth or
expand network capacity.
3. If the alarm persists, go to Step 2.
Step 2 Cause 2: The configured Ethernet port traffic is heavy.
1. Query the bandwidth utilization of the Ethernet port on the NMS.
2. If the port bandwidth utilization exceeds its threshold, 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.310 PORTSWITCH_FAIL
Description
Optical switch switching failure. This alarm is generated when the board detects that an
optical switch inside the board fails to switch.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Perform a cold reset on the faulty board on the U2000, or remove the faulty board and insert it
again.
Step 2 After the board is reset, perform the spectrum analysis on the MCA again on the U2000.
----End
Related Information
None
4.311 POWER_ABNORMAL
Description
The POWER_ABNORMAL is an alarm indicating a power supply failure. This alarm is
generated when the power supply of a board becomes abnormal.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 and Each bit indicates whether the alarm is generated in the
Parameter 2 corresponding voltage. Bit 1 indicates that the alarm is generated,
and bit 0 indicates that no alarm is generated.
Possible Causes
l Cause 1: The input power of the PIU is abnormal.
l Cause 2: The jumper cap of the SCC is not configured.
l Cause 3: The power module on the board is faulty.
Procedure
l Query current alarms on the U2000. Then determine the board that reports the alarm. For
details, see Product Description.
l Cause 1: The input power of the PIU is abnormal.
a. Check the board alarm indicator to see whether the power input is normal. For the
description of the alarm indicators on the board, see the Hardware Description.
b. If not, feed the NE power again. For operations of connecting the power supply, see
Quick Installation Guide of the applicable equipment.
l Cause 2: The jumper cap of the SCC is not configured.
NOTE
The POWER_ABNORMAL alarm is reported when the jumper used to set the used input voltage
of the SCC is configured incorrectly.
a. Contact the local representative office of Huawei, and then check whether the
jumper of the SCC is correct. If not, adjust the jumper. For details on the jumper
setting of each SCC, see the Hardware Description.
l Cause 3: The power module on the board is faulty.
a. Check whether the alarm is cleared after you perform a cold reset on the board on
the U2000 or remove and insert the board. For the operations that are performed by
using the U2000, see Supporting Tasks.
NOTICE
If the services that pass the board are not under protection, the services are
interrupted after you perform cold reset on the board.
b. If the alarm persists, replace the board that reports the alarm. For details, see the
Supporting Tasks.
----End
Related Information
None
4.312 POWER_DIFF_OVER
Description
Optical power difference exceeding the system limit. This alarm is generated when the power
difference between the active and standby channels crosses the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l During transmission, the optical power attenuation of signals is excessively large or the
board at the local end is equipped with an over-large optical attenuator. Therefore, the
optical power difference between the active and standby OSCs at the receive end is
excessively large.
l The optical power difference of signals on the active and standby channels when the
board at the peer end transmits signals is excessively large.
Procedure
Step 1 Replace the existing optical attenuators with suitable ones. Adjust the optical power on the
active and standby channels of the board at the local site to ensure that the power difference is
within 5 dB.
NOTE
After the POWER_DIFF_OVER alarm is reported, the alarm can be cleared only when the power difference
is with the range of the preset threshold minus 2 dB to avoid alarm jitter.
Step 2 If the alarm persists, the detection circuit of the board at the local site is faulty. Replace the
faulty board.
----End
Related Information
None
4.313 POWER_SAMPLE_DIFF
Description
This alarm is generated when the current optical power of the protection channel is
inconsistent with the sampling optical power.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The difference between the current optical power of the protection channel and sampling
optical power exceeds 2 dB.
Procedure
l Check whether the line fibers are properly connected and whether they are aging. If they
are incorrectly connected or aging, reconnect or replace the fibers.
l Check whether all VOAs on the line are configured. If there are unconfigured VOAs,
manually adjust the attenuation of these VOAs to a proper value.
l Check whether the board insertion loss is normal. If it is abnormal, replace the board.
l If the line insertion loss remains unchanged but the alarm persists, sample the optical
power again.
----End
Related Information
None
4.314 PRBS_LSS
Description
Loss of pseudo-random binary sequence (PRBS) signals. This 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
Possible Causes
l Cause 1: The link is abnormal. Therefore, 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.
l If the alarm is cleared, the board is normal. See Step 2 to check the link.
l If the alarm persists, the board is faulty. Replace the board.
Step 2 Verify 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.315 PRO_PKT_FLOODING
Description
Protocol packet flooding attack alarm. This alarm is reported when the rates of protocol
packets received by a device exceed the upper rate threshold for 30 consecutive seconds.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Possible Causes
The rates of protocol packets received by a device exceed the upper rate threshold for 30
consecutive seconds.
Procedure
Step 1 Check whether there are protocol packet attacks. If yes, clear them.
----End
Related Information
None
4.316 PTP_SOURCE_SWITCH
Description
PTP time source switching alarm. When the ID of the grandmaster source traced by the NE or
the tracing port changes, this alarm is reported to remind the user of a switchover of the IEEE
1588v2 tracing source.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 and 2 Indicates the slot ID of the line board before switching.
Parameters 14 and 15 Indicates the slot ID of the line board after switching.
Possible Causes
The possible causes of the PTP_SOURCE_SWITCH alarm are as follows:
Procedure
l Cause 1: The physical link is faulty.
a. On the NMS determine the number of the port where the alarm is reported.
b. Check whether a network cable or fiber is disconnected from this port. If yes,
reconnect the network cable or fiber, and then check whether the alarm is cleared.
c. If the alarm persists, check whether the network cable or fiber is faulty. If yes,
replace the network cable or fiber and then check whether the alarm is cleared.
d. If the alarm persists, query the transmit optical power of the peer NE on the NMS.
If the transmit optical power is normal, replace the optical power of the board or the
board at the peer NE.
e. If the alarm persists, check whether the local receive board is faulty. If yes, replace
the board that reports the alarm on the local NE.
l Cause 2: Quality level, priority 1, or priority 2 of the Grandmaster clock changes.
a. Restore the quality level, priority 1, or priority 2 of the Grandmaster clock to that
before switching. The alarm is automatically cleared when the clock source after
switchover becomes stable.
l Cause 3: The network topology changes.
a. Check whether the new network topology complies with the live network planning.
If yes, the alarm is automatically cleared when the clock source after the switchover
becomes stable.
----End
Related Information
None
4.317 PTP_TIMESTAMP_ABN
Description
PTP time stamp exception. When the PTP (IEEE 1588v2) time stamp freezes, this alarm is
reported.
Attribute
Parameters
None.
Possible Causes
l Cause 1: The delay mode settings for the ports on two interconnected boards are
inconsistent.
l Cause 2: The hardware of the IEEE 1588v2 port currently traced is faulty.
l Cause 3: The hardware of the clock board is faulty.
l Cause 4: The clock module at the transmit end of the reference source is faulty.
Procedure
l Cause 1: The delay mode settings for the ports on two interconnected boards are
inconsistent.
a. Check whether the delay mode settings for the ports on two interconnected boards
are consistent. If not, modify them to be the same.
l Cause 2: The hardware of the IEEE 1588v2 port currently traced is faulty.
a. On the NMS, check for the HARD_BAD or HARD_ERR alarm on the board with
the IEEE 1588v2 port. Clear such an alarm if there is any.
l Cause 3: The hardware of the clock board is faulty.
a. On the NMS, check for the HARD_BAD or HARD_ERR alarm on the clock board.
Clear such an alarm if there is any.
l Cause 4: The clock module at the transmit end of the reference source is faulty.
a. If no HARD_BAD or HARD_ERR alarm occurs on the board with the IEEE
1588v2 port that is currently traced and the clock board, replace the interface board
that corresponds to the transmitter of the reference source.
----End
Related Information
None
4.318 PUM_BCM_ALM
Description
Bias current of the pump laser crossing the threshold. This alarm is generated when the pump
laser bias current of the optical amplifier unit crosses the threshold.
Attribute
Parameters
Parameter Description
Parameter 1 Indicates the threshold crossing type. The value is always 0x01.
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 it is not, adjust the ambient temperature
of the equipment to a proper degree.
Step 2 If the alarm persists, perform a warm reset on the faulty board on the U2000.
Step 3 If the alarm persists, remove and re-insert the board under the condition that the services are
not affected.
Step 4 If the alarm persists, replace the faulty board. Refer to Replace the board.
----End
Related Information
None
4.319 PUM_TEM_ALM
Description
Working temperature of the pump laser exceeding the threshold. This alarm is generated when
the operating temperature of the pump laser on the optical amplifier board crosses the
threshold.
Attribute
Parameters
Parameter Description
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.
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 it is not, adjust the ambient temperature
of the equipment to a proper degree.
Step 2 If the alarm persists, perform a warm reset on the faulty board on the U2000.
Step 3 If the alarm persists, remove and re-insert the board under the condition that the services are
not affected.
Step 4 If the alarm persists, replace the faulty board. Refer to Replace the board.
----End
Related Information
None
4.320 PUMP_LINK_ULLAGE_HIGH
Description
Pump laser connection insertion loss alarm. The alarm indicates that the insertion loss
between the pump laser and the optical amplifier module exceeds the threshold.
Attribute
Parameters
None
Possible Causes
l The fiber connector is dirty, and the fiber jumper is over-bent, damaged or aged.
l The pump card is faulty.
l The board is faulty.
Procedure
Step 1 Check the fiber connector, if the fiber connector is dirty, clean or replace the fiber connector.
Step 2 If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged or
aged, adjust the fiber jumper or Replacing Fiber Jumpers.
Step 3 If the alarm persists, the pump card might be faulty. Replace the card.
Step 4 If the alarm persists, the board might be faulty. Replace the board.
----End
Related Information
None
4.321 PUMP_MIS_MATCH
Description
Pump card mismatch. That is, the type of the pump card mismatches the type of the board
type.
Attribute
Parameters
None
Possible Causes
The type of the pump card mismatches the type of the board type.
Procedure
Step 1 Check the type of the pump card and the board type, replace the correct pump card.
----End
Related Information
None
4.322 PUMP_OFFLINE
Description
Pump card offline. That is, the alarm is generated when the software detects no pump card.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The pump card is not inserted into the slot.
l The pump card is faulty.
Procedure
Step 1 On U2000, query for the optical port on which the alarm is reported.
l If the alarm is reported on optical port 9, only pump card A is working.
l If the alarm is reported on optical port 10, only pump card B is working.
Step 2 According to the step 1, check if there is a card in the slot where no card is working.
l If there is no card, insert a card with a proper type.
l If there is a card in the slot, the pump card might be faulty. Replace the card.
----End
Related Information
None
4.323 PW_APS_DEGRADED
Description
The PW_APS_DEGRADED alarm indicates that a PW APS protection group is degraded
(APS is short for automatic protection switching). An NE reports a PW_APS_DEGRADED
alarm when detecting that a PW in a PW APS protection group fails, and clears the
PW_APS_DEGRADED alarm when detecting that both the primary and secondary PWs in
the PW APS protection group are functioning normally or fail. When detecting that both the
primary and secondary PWs in a PW APS protection group fail, an NE clears a reported
PW_APS_DEGRADED alarm and reports a PW_APS_OUTAGE alarm.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: A PW in the PW APS protection group for which a PW_APS_DEGRADED
alarm is reported fails.
As shown in Figure 4-22, PW 1 and PW 2 form a PW APS protection group. When
detecting that PW 1 is functioning normally and PW 2 fails, NE 2 reports a
PW_APS_DEGRADED alarm.
Tunnel
NE 1 NE 2
Procedure
Step 1 Cause 1: A PW in the PW APS protection group for which a PW_APS_DEGRADED alarm is
reported fails.
----End
Related Information
None
4.324 PW_APS_OUTAGE
Description
The PW_APS_OUTAGE alarm indicates that a PW APS protection group fails (APS is short
for automatic protection switching). An NE reports a PW_APS_OUTAGE alarm when
detecting that both the primary and secondary PWs in a PW APS protection group fail, and
clears the PW_APS_OUTAGE alarm when detecting that a PW in the PW APS protection
group recovers.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: Both the primary and secondary PWs in the PW APS protection group for
which a PW_APS_OUTAGE alarm is reported fail.
As shown in Figure 4-23, PW 1 and PW 2 form a PW APS protection group. When
detecting that both PW 1 and PW 2 fail, NE 2 reports a PW_APS_OUTAGE alarm.
Tunnel
NE 1 NE 2
Procedure
Step 1 Cause 1: Both the primary and secondary PWs in the PW APS protection group for which a
PW_APS_OUTAGE alarm is reported fail.
1. On the network management system (NMS), find the primary and secondary PWs in the
PW APS protection group for which a PW_APS_OUTAGE alarm is reported.
2. Check whether the ports carrying the primary and secondary PWs are enabled. If the
ports are disabled, enable them.
3. If the alarm persists, go to Step 2.
Step 2 Cause 2: The NE reporting a PW_APS_OUTAGE alarm reported a PW-related alarm.
1. Check for a PW-related alarm on the NE that reports a PW_APS_OUTAGE alarm, and
clear any PW-related alarms.
2. If the alarm persists, go to Step 3.
Step 3 Cause 3: The optical fiber carrying the PW APS protection group for which a
PW_APS_OUTAGE alarm is reported is not correctly connected to the optical port, or the
optical fiber connector is dirty.
1. Check whether the optical fiber is correctly connected to the optical port and whether the
optical fiber connector is clean. Rectify any faults by cleaning the optical fiber connector
or re-connecting or replacing the optical fiber.
----End
Related Information
None
4.325 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC is an alarm indicating that a PW that carries services (such as
L2VPN services) has no traffic.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The possible causes of the PW_NO_TRAFFIC alarm are as follows:
l Cause 1: No service is configured.
l Cause 2: The local services are abnormal and therefore no packet is transmitted to the
peer end.
l Cause 3: The peer—end services are abnormal and therefore no packet is transmitted to
the local end.
l Cause 4: The port that corresponds to the faulty PW works abnormally.
Procedure
Step 1 Determine the alarmed board, alarmed port, and direction in which the traffic is unavailable
according to the alarm information on the NMS.
If... Then...
Step 3 Cause 2: The local services are abnormal and therefore no packet is transmitted to the peer
end.
1. Check whether the local services carried by the PW are correctly configured.
2. Check whether the PW_NO_TRAFFIC alarm is cleared. If the alarm persists, go to Step
5.
Step 4 Cause 3: The peer—end services are abnormal and therefore no packet is transmitted to the
local end.
1. Check whether the peer—end services carried by the PW are correctly configured.
2. Check whether the PW_NO_TRAFFIC alarm is cleared. If the alarm persists, go to Step
5.
Step 5 Cause 4: The port that corresponds to the faulty PW works abnormally.
1. Replace the board that reports the PW_NO_TRAFFIC alarm at the local end.
2. If the alarm persists, replace the relevant board at the peer end.
3. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.326 PWAPS_LOST
Description
The PWAPS_LOST alarm indicates that the PW automatic protection switching (APS) frames
are lost. This alarm is generated when no PW APS frame is received from the protection
channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the alarm are as follows:
l Cause 1: PW APS protection is not configured for the peer NE.
l Cause 2: The PW APS protocol is disabled on the peer NE.
l Cause 3: The physical link is connected incorrectly or is faulty.
Procedure
Step 1 Cause 1: PW APS protection is not configured for the peer NE.
1. On the NMS, check whether PW APS protection is configured for the peer NE.
If... Then...
PW APS protection is not configured for the peer NE Go to the next step.
PW APS protection is configured for the peer NE Go to Step 2.
2. Configure a PW APS protection group on the peer NE according to the NE planning
table. Ensure that the configuration on the peer NE is consistent with the configuration
on the local NE. Then, enable the APS protocol. Check whether the alarm is cleared.
If... Then...
The protocol is disabled Disable the PW APS protocol on the local NE and then
enable the protocol at both ends.
The protocol is enabled Go to Step 3.
2. If the alarm persists, go to Step 3.
Step 3 Cause 3: The physical link is connected incorrectly or is faulty.
1. Check whether the fiber or cable is connected correctly. If the port on the working
channel is physically connected to the port on the protection channel, one end cannot
receive APS packets from the other end. If the fiber or cable is incorrectly connected,
rectify the fiber or cable connection. Check whether the alarm is cleared.
2. Check whether any faults such as signal loss, signal degrade, fiber or cable damage occur
on the protection channel. If yes, rectify these faults immediately.
3. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.327 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH alarm indicates that the local NE and the peer NE in a PW
APS protection group have different working and protection paths.
Attribute
Alarm Severity Alarm Type
Parameters
None
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the alarm are as follows:
l Cause 1: The local NE and the peer NE in a PW APS protection group have different
working and protection paths.
l Cause 2: Physical links are connected incorrectly.
Procedure
Step 1 Cause 1: The local NE and the peer NE in a PW APS protection group have different working
and protection paths.
1. On the NMS, check whether the PW APS settings at both ends are the same. For
example, check whether PW 1 is set to the working channel and PW 2 is set to the
protection channel at one end, whereas PW 1 is set to the protection channel and PW 2 is
set to the working channel at the other end. Check whether one end of a PW is the
working channel, the other end is the protection channel, and the working and protection
channels are different.
2. If the PW APS settings at both ends are different, change them to the same. Then check
whether the alarm is cleared.
3. If the alarm persists, go to Step 2.
----End
Related Information
None
4.328 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL alarm indicates a PW APS switching failure. This alarm is
generated 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
Parameters
None
The following figure shows the major suppression relationship between the alarm and other
alarms related to the PW APS protection group.
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the alarm are as follows:
l Cause 1: The configurations of the PW APS protection group differ at both ends.
l Cause 2: The physical link deteriorates or is connected incorrectly.
Procedure
Step 1 Cause 1: The configurations of the PW APS protection group differ at both ends.
1. On the NMS, check whether the PW APS settings at both ends are the same. For
example, if the APS protection group is enabled at one end but disabled at the other end,
the other end does not process a received switching request.
2. If the settings are different at the two ends, change them to the same. Then deactivate
and activate the APS protection groups at both ends.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The physical link deteriorates or is connected incorrectly.
1. Check whether the fiber or cable is connected correctly. If the port on the working
channel is physically connected to the port on the protection channel, one end cannot
receive a switching request from the other end. If the fiber or cable is incorrectly
connected, rectify the fiber or cable connection.
2. If the alarm persists, check whether any fault such as signal loss or signal degrade occurs
on the protection channel. If yes, rectify these faults immediately.
3. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.329 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH alarm indicates that the local NE and the peer NE have
different PW protection types. This alarm is generated 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
Parameters
None
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the alarm are as follows:
Procedure
Step 1 On the NMS, query the settings of the PW APS protection group on both ends, including
protection modes, switching modes, and revertive modes.
Step 2 If the settings are different, change them to the same and enable the APS protocol.
----End
Related Information
None
4.330 PWD_ENCRYPT_RISK
Description
User password encryption mode risk alarm. This alarm is generated when a user performs the
following operations:
l Uses a password encrypted in MD5 or SHA256 mode to log in to an NE, change the
login password, or add another user.
l Upgrades to V100R008C10SPC200 or a later version when the NE user password is
encrypted in MD5 or SHA256 mode.
Attribute
Parameters
None
Possible Causes
The user password is encrypted in MD5 or SHA256 mode.
Procedure
Step 1 Click the NE in the NE explorer and select Security > NE User Password Encryption
Management, then change Encryption Type to PBKDF2.
----End
Related Information
None
4.331 PWR_UNBALANCED
Description
Unbalanced optical power flatness alarm. This alarm is generated when the optical power
flatness of monitored wavelengths at the optical power monitoring point exceeds the
threshold.
Attribute
Parameters
None
Possible Causes
Because of abnormal wavelength attenuation adjustment and line condition changes, the
optical power flatness of monitored wavelengths at the optical power monitoring point is
abnormal.
Procedure
Step 1 Check whether the boards and fiber connections are normal.
----End
Related Information
None
4.332 R_LOC
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.332.2 R_LOC (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The R_LOC is an alarm indicating no clock on the receive side of the line. This alarm is
reported when the line board cannot extract the clock from line signals.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The link is faulty so that the board cannot extract the clock.
l Clock tracing is incorrectly configured on the board.
l The board is faulty.
Procedure
Step 1 Check whether the physical link is functioning properly. If not, rectify the link fault. Then,
check whether the alarm is cleared.
Step 2 If the alarm persists, check whether clock tracing configured on the board is the same as
planned. If not, modify the clock tracing configuration. Then, check whether the alarm is
cleared.
Step 3 If the alarm persists, cold reset the local line board that reports the alarm. Then, check
whether the alarm is cleared.
Step 4 If the alarm persists, the clock tracing module on the line board may be faulty. Replace the
line board and check whether the alarm is cleared.
Step 5 If the alarm still persists, check whether the clock board is faulty. If yes, replace the board.
Then, check whether the alarm is cleared.
Step 6 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
Attribute
Parameters
None
Possible Causes
l The link is abnormal and the board cannot properly extract clock signals.
l The setting of the board clock tracing is incorrect.
l The board is faulty.
Procedure
Step 1 Perform a self-loop on the board. Check whether the physical link is normal. If any
abnormality such as OTUk_LOF is found, remove the abnormality.
Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the
entire network plan. Adjust the board clock setting if it is incorrect.
Step 3 If the alarm persists, replace the faulty board. Refer to Replace the board.
----End
Related Information
Related Cases:
l MC-A104 No Optical Power Is Output on the WDM Side Due to Incorrect
Configuration,the Board Reports the R_LOF, R_LOC, TP_LOC Alarms
l MC-A214 The LQG Board Works Abnormally Due to Incorrect Clock Configuration On
The Board And The Board Reports CLIENT_SF And R_LOC Alarm
l MC-A227 Services Cannot Be Provisioned and The LWX2 Boards Report The R_LOC
Alarm Due to Incorrect Service Rates on LWX2 Board of OptiX OSN 1800
4.333 RACK_CONFLICT_SCREEN
Description
This alarm is reported after the AUX board isolates the subrack ID conflict caused by
incorrect connections between device cascading ports.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Possible Causes
l An incorrect connection causes a subrack ID conflict and the AUX board isolates the
conflict.
Procedure
Step 1 Handle the subrack ID conflict with reference to 3.46 SUBRACK_ID_CONFLICT and
ensure that the master and slave subrack IDs do not conflict.
Step 2 On the U2000, open the NE Explorer, choose Communication > Access control from the
navigation tree, select the disabled communication port, and change its status to Enable.
----End
Related Information
For details about the master/slave subrack feature of OptiX OSN 8800/6800, see Master-Slave
Subrack Management in the Feature Description.
4.334 RELAY_ALARM_CRITICAL
Description
Critical alarm of the alarm input.
Attribute
Parameters
None
For the OptiX OSN 6800, the status of the external equipment connected to the alarm input
port of the EFI board changes.
For the OptiX OSN 3800, the status of the external equipment connected to the alarm input
port of the AUX board changes.
Possible Causes
For the OptiX OSN 8800,
Procedure
Step 1 For the OptiX OSN 8800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI1 board changes. If it does,
remove the fault of the external equipment.
Step 2 For the OptiX OSN 6800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI board changes. If it does,
remove the fault of the external equipment.
Step 3 For the OptiX OSN 3800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the AUX board changes. If it does,
remove the fault of the external equipment.
Step 4 If no external equipment is connected to the alarm input port, set the input port to Unused and
the alarm is cleared.
----End
Related Information
None
4.335 RELAY_ALARM_IGNORE
Description
Warning alarm of the alarm input.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
For the OptiX OSN 8800,
Procedure
Step 1 For the OptiX OSN 8800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI1 board changes. If it does,
remove the fault of the external equipment.
Step 2 For the OptiX OSN 6800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI board changes. If it does,
remove the fault of the external equipment.
Step 3 For the OptiX OSN 3800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the AUX board changes. If it does,
remove the fault of the external equipment.
Step 4 If no external equipment is connected to the alarm input port, set the input port to Unused and
the alarm is cleared.
----End
Related Information
None
4.336 RELAY_ALARM_MAJOR
Description
Major alarm of the alarm input.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
For the OptiX OSN 6800, the status of the external equipment connected to the alarm input
port of the EFI board changes.
For the OptiX OSN 3800, the status of the external equipment connected to the alarm input
port of the AUX board changes.
Possible Causes
For the OptiX OSN 8800,
Procedure
Step 1 For the OptiX OSN 8800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI1 board changes. If it does,
remove the fault of the external equipment.
Step 2 For the OptiX OSN 6800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI board changes. If it does,
remove the fault of the external equipment.
Step 3 For the OptiX OSN 3800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the AUX board changes. If it does,
remove the fault of the external equipment.
Step 4 If no external equipment is connected to the alarm input port, set the input port to Unused and
the alarm is cleared.
----End
Related Information
None
4.337 RELAY_ALARM_MINOR
Description
Minor alarm of the alarm input.
Attribute
Parameters
None
For the OptiX OSN 6800, the status of the external equipment connected to the alarm input
port of the EFI board changes.
For the OptiX OSN 3800, the status of the external equipment connected to the alarm input
port of the AUX board changes.
Possible Causes
For the OptiX OSN 8800,
Procedure
Step 1 For the OptiX OSN 8800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI1 board changes. If it does,
remove the fault of the external equipment.
Step 2 For the OptiX OSN 6800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the EFI board changes. If it does,
remove the fault of the external equipment.
Step 3 For the OptiX OSN 3800, check whether the status of the external equipment (for example,
access control system) connected to the alarm input port of the AUX board changes. If it does,
remove the fault of the external equipment.
Step 4 If no external equipment is connected to the alarm input port, set the input port to Unused and
the alarm is cleared.
----End
Related Information
None
4.338 REM_SD
Description
Remote signals being degraded. When the received signals on the client side of the board at
the peer site is degraded, the alarm signal is inserted. This alarm is generated when the client
side of the board at the local site detects the signals.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The client side of the OTU board at the peer site has the B1_EXC alarm.
l The demultiplexed client signals on the WDM side of the OTU board at the local site
have the B1_EXC alarm.
Procedure
Step 1 Check whether the OTU board at the peer site has the B1_EXC alarm. If it does, see the
procedure of handling B1_EXC to handle the alarm.
Step 2 If the alarm persists, check whether demultiplexed client signals on the WDM side of the
OTU board at the local site have the B1_EXC alarm. If the B1_EXC alarm is found, see the
procedure of handling B1_EXC to handle the alarm.
----End
Related Information
None
4.339 RL_CRITICAL_HI
Description
Critical high return loss. This alarm is generated when the return loss is higher than the upper
threshold of the return loss alarm.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The fiber near the Raman board is broken.
l The fiber near the Raman board is over-bent or pressed.
l The connector of the fiber near the Raman board is unclean.
l The connector of the fiber near the Raman board is incorrectly inserted.
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Check whether the
fiber near the Raman board is properly connected. If it is not, reconnect it.
Step 2 Check whether the fiber near the Raman board is over-bent or pressed. If it is not, spool the
fiber again. If the fiber is broken because of the press, replace it or repair it by means of
splicing.
Step 3 Check whether the end face of the fiber near the Raman board is clean. If it is not, clean it
again and properly connect the fiber.
Step 4 Turn on the pump laser on the port of the Raman board and check whether the alarm is
cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.340 RL_CRITICAL_LOW
Description
Critical low return loss. This alarm is generated when the return loss is lower than the lower
threshold of the return loss alarm.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The fiber near the Raman board is broken.
l The fiber near the Raman board is over-bent or pressed.
l The connector of the fiber near the Raman board is unclean.
l The connector of the fiber near the Raman board is incorrectly inserted.
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether
the fiber near the Raman board is properly connected. If it is not, reconnect it.
Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If
it is, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by
means of splicing.
Step 3 If the alarm persists, check whether the end face of the fiber near the Raman board is clean. If
it is not, clean it again and properly connect the fiber.
Step 4 Turn on the pump laser on the port of the Raman board and check whether the alarm is
cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None
4.341 RM_RLOS
Description
Loss of input reverse pump optical signals. This alarm is generated when input reverse pump
optical signals are lost.
Attribute
Parameters
None
Possible Causes
The attenuation of the transmission line is excessively high, or a fiber cut occurs on the
transmission line.
Procedure
Step 1 Check the line status, sort out fibers, and check for fiber cuts using a test instrument. Replace
fibers if there are fiber cuts to ensure that the line is in good conditions.
Step 2 Check the upstream and downstream IPA configurations and ensure that they are correct.
----End
Related Information
None
4.342 RMON_ALM_INBADOCTS_OVER
Description
Statistics of receiving bad packets is over the upper threshold. The alarm is generated when
the octet number of bad packets detected by the Ethernet port of the board crosses the upper
threshold.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the Ethernet port where the alarm is generated. For example,
0x01 indicates Ethernet port 1.
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is
generated. For example, 0x00 0x01 indicates channel 1 of the port
indicated by Parameter 1.
Possible Causes
l The data equipment on the client side sends the abnormal data packets.
l The abnormal link between the client side and the Ethernet port on the board leads to the
error of the data packets in transmission.
l The faulty board leads to the regeneration of the signals or detection error.
Procedure
Step 1 Check whether the data equipment on the client side is normal. If it is abnormal, remove the
fault of the data equipment on the client side.
Step 2 If the alarm persists, check whether the link between the client side and the Ethernet port on
the board is normal.
1. Check whether the optical port mode (and the fiber mode) of the two connected Ethernet
ports are consistent. If they are not consistent, replace the fiber or board to ensure that
the optical port mode and the fiber type of the two Ethernet ports are consistent.
2. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
see the Troubleshooting.
3. Check whether the transmit/receive optical power of the two connected Ethernet ports is
within the permitted range. For the optical power specifications of the specific board, see
the Product Description. If the optical power is abnormal, take the alarm as the
IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.
Step 3 If the alarm persists, perform a warm reset on the faulty board on the U2000. For details, see
the Troubleshooting.
----End
Related Information
The abnormal data packets include:
4.343 RS_CROSSTR
Description
Regenerator section performance crossing the threshold. This alarm is generated when the
performance module reports the threshold crossing of regenerator section performance.
Attribute
Parameters
Name Meaning
Name Meaning
Possible Causes
l The performance of the laser on the board at the peer site deteriorates.
l The input optical power of the board at the local site is excessively high or excessively
low.
l The performance of the clock at the peer site deteriorates.
l The fiber performance deteriorates.
Procedure
Step 1 Check whether the fiber is aged or has excessive attenuation. If it is aged or has excessive
attenuation, remove the fault of the fiber.
Step 2 Query whether the board has the B1_EXC, B1_SD, B2_EXC or B2_SD alarm on the U2000.
If it does, clear the alarm.
Step 3 Check whether the input optical power of the board at the local site is within the permitted
range on the U2000. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.
l If the optical power displayed on the U2000 is normal, the board may be faulty. Refer to
Replace the board.
l If the optical power displayed on the U2000 is abnormal, adjust the input optical power
to a value within the permitted range.
Step 4 If the alarm persists, remove the fault of the board at the peer site.
----End
Related Information
A performance monitoring period can be 15-minute or 24-hour. For a performance threshold
crossing alarm, the system checks whether the requirement of alarm clearance is met only
after a new monitoring period starts. If the alarm persists after you perform the provided
procedure, query whether the service has been restored to normal by checking the
accumulated performance values. Or wait after a new monitoring period starts and then check
whether the alarm is cleared.
4.344 RTC_FAIL
Description
Timing failure of the real time clock (RTC).
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The clip of the RTC clock is damaged.
l The temperature of the board is excessively high.
Procedure
Step 1 Check whether the board temperature is normal. If it is abnormal, replace the fan.
Step 2 If the alarm persists, replace the faulty board. For details, see "Replacing the SCC Board" in
the Parts Replacement.
----End
Related Information
RTC is also called NE timing.
4.345 RX_POWER_ABNORMAL
Description
Receive optical power abnormal alarm. When the optical module demultiplexes one signal
into multiple channels of optical signals and transmits them at the same time. Although the
input multiplexed optical power is normal, this alarm will be reported if the optical power of
any channel is too high or too low.
Attribute
Parameters
None
Possible Causes
l Cause 1: A pigtail is not properly connected to an optical port on the board that reports
the alarm.
l Cause 2: The attenuation of the line is larger than the threshold or the fiber is broken.
l Cause 3: The board that reports the alarm is malfunctioning.
l Cause 4: The peer board of the board that reports the alarm is malfunctioning.
Procedure
Step 1 Check whether the receive optical power is close to the lower or upper limit. If the receive
optical power is abnormal, rectify the fault with reference to the procedure for handling the
IN_PWR_LOW or IN_PWR_HIGH alarm.
Step 2 Check whether a pigtail is connected to an optical port on the board or whether the pigtail is
properly connected. If no pigtail is connected or the pigtail is not properly connected, ensure
that the pigtail is properly connected.
Step 3 If the alarm persists, the board that reports the alarm may be malfunctioning. Replace the
board.
The board does not support pluggable optical Replace the board.
modules.
Step 4 If the alarm persists, the peer board of the board that reports the alarm may be malfunctioning.
Replace the malfunctioning board.
The board does not support pluggable optical Replace the board.
modules.
----End
Related Information
None
4.346 RXCFG_WAVEDATA_MIS
Description
The RXCFG_WAVEDATA_MIS alarm indicates that the physical receive wavelength or band
attribute (odd or even) of an optical module is different from the logical receive wavelength or
band attribute set by a user. This alarm is reported when the receive wavelength or band
attribute settings mismatch on a board and an NE.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible causes of the RXCFG_WAVEDATA_MIS alarm are as follows:
l Cause 1: The configured logical receive wavelength or band is different from the
actually supported receive wavelength or band.
l Cause 2: The board is faulty.
Procedure
Step 1 Cause 1: The configured logical receive wavelength or band is different from the actually
supported receive wavelength or band.
1. On the U2000, check whether the logical receive wavelength configured on the board is
the same as the actually supported receive wavelength. If the two wavelengths are
different, reconfigure the working receive wavelength of the corresponding optical port
to make it the same as the actual receive wavelength of the optical module on the board.
----End
Related Information
None.
4.347 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the
S1 mode.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 Indicates the ID of the priority table. Valid values are as follows:
l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source
Possible Causes
l Cause 1: The fiber connection is faulty.
l Cause 2: The upstream site generates the alarm.
Procedure
l Cause 1: The fiber connection is faulty.
a. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For
details, see the Supporting Tasks.
b. If the alarm persists, replace the faulty board. For details, see the Parts
Replacement.
l Cause 2: The upstream site generates the alarm.
a. If the alarm persists, check whether the S1_SYN_CHANGE alarm is generated at
the upstream site. If yes, repeat the preceding steps to clear the S1_SYN_CHANGE
alarm at the upstream site..
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.348 SCC_CHANGE
Description
The SCC_CHANGE is an alarm indicating that the SCC board is replaced. This alarm is
automatically reported after the SCC board on the NE is replaced.
Attribute
Parameters
None
Possible Causes
l The SCC board is replaced.
Procedure
l Check whether the SCC board replacement is necessary.
a. If the SCC board replacement is necessary, add and then delete any logical board of
the NE on the NMS. The alarm is automatically cleared.
b. If the SCC board is replaced by mistake, insert the original SCC board back.
----End
Related Information
For details, see "Replacing the SCC Board" in the Parts Replacement.
4.349 SCC_LOC
Description
Loss of system control board clock. This alarm is generated when the OSC board detects that
the clock source sent by the system control board is lost.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The board is faulty.
l The system control board is faulty.
l The alarm is generated during the cold reset of the system control board and is
automatically cleared after the cold reset is complete.
Procedure
Step 1 Query the reset record of the system control board.
l If the time when the alarm is cleared is consistent with the time when the system control
board is reset, the alarm may be caused by resetting the system control board. There is no
need to handle the alarm.
l If the time when the alarm is cleared is not consistent with the time that the system
control board is reset, the board may be faulty. Replace the faulty board. For details, see
"Replacing the SCC Board" in the Parts Replacement.
Step 2 If the alarm persists, the system control board may be faulty. Replace the faulty system
control board. For details, see "Replacing the SCC Board" in the Parts Replacement.
----End
Related Information
None
4.350 SEC_RADIUS_FAIL
Description
Excessive failures in RADIUS authentication. This alarm indicates that a large number of
authentication failures occur on the NE within a short period.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
A large number of RADIUS authentication failures occur on the NE within a short period.
Procedure
Step 1 Check whether the user account expires.
Step 2 Check whether the user password is changed or the user access policy is changed by the
administrator.
Step 3 Check whether an unauthorized user attempts to log in to the network device.
Step 4 Check whether the shared key between the GNAS and the RADIUS server is correct. For
example, whether a shared key is used.
----End
Related Information
None
4.351 SERVICE_CAPACITY_EXCEED_LICENSE
Description
Service capacity exceeding the license limit. This alarm indicates that the service capacity
configured in a subrack exceeds the license limit.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the ID of the subrack where the service capacity exceeds the license
limit.
Possible Causes
The service capacity configured in the subrack exceeds the license limit.
Procedure
Step 1 According to the alarm parameters, query the license capacity for the subrack where the alarm
is generated. Select a proper license capacity to meet the service requirements of the subrack.
Step 2 If no license with a proper capacity can be used, purchase the license with a proper capacity
from Huawei.
----End
Related Information
None
4.352 SERVICE_TYPE_EXCEED_LICENSE
Description
Service type exceeding the license limit. This alarm indicates that the type of configured
services exceeds the license limit.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Parameter 1 Indicates the ID of the subrack where the service type exceeds the license
limit.
Possible Causes
The service type configured in the subrack exceeds the license limit.
Procedure
Step 1 According the alarm parameter, check whether the type of configured services in the subrack
exceeds the license limit on the U2000.
Step 2 If it does, assign a proper license.
Step 3 If no proper license is available, purchase the license with a later version from Huawei.
----End
Related Information
None
4.353 SHELF_AREA_POWER_OVER
Description
Total optical power consumption of a subrack section exceeding the threshold. This alarm is
generated when the total power consumption of the boards in a section of the subrack is
higher than or equal to the power consumption threshold for this section.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The total power consumption of the boards in a section of the subrack is higher than or equal
to the power consumption threshold for each section.
Procedure
Step 1 Remove boards from the subrack section until the alarm is cleared. For details on subrack
sections, see section "Power Redundancy" in Product Description.
----End
Related Information
None
4.354 SHELF_POWER_UNCONFIG
Description
The power consumption threshold of a subrack is not configured. This alarm is reported if the
power consumption threshold of a subrack is not configured during new deployment or after
the NE database is cleared and the NE is reset.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Possible Causes
The power consumption threshold of a subrack is not configured.
Procedure
Step 1 Manually configure the power consumption threshold of the subrack.
----End
Related Information
None
4.355 SLAVE_WORKING
Description
The SLAVE_WORKING is an alarm indicating the working state of the standby board. If the
standby cross-connect board is selected for the service bus of the service board, and if the
standby clock is selected as the system clock, the SLAVE_WORKING alarm is reported.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Para 1 Indicates the working mode of the protection board. Valid values are as
follows:
l 0x00: cross-connect bus
l 0x01: clock board
l 0x02: system control board
l 0x03: chip bus
Para 2, Para 3 l If the value of Para 1 is 0x00 or 0x03, Para 2 indicates the bus number.
l If the value of Para 1 is 0x01 or 0x02 and the value of Para 2 is 0x01,
Para 3 indicates the slot ID of the protection board.
Possible Causes
The possible causes of the SLAVE_WORKING alarm are as follows:
Procedure
l Query current alarms on the NMS. Determine the board that reports the alarm. For
details, see Product Description.
l Cause 1: The active cross-connect board is not in position.
a. Check whether the active cross-connect board is loose. If yes, secure the active
cross-connect board. For details, see the Installation Guide. Then check whether the
alarm is cleared.
b. If the alarm persists, see Cause 2.
l Cause 2: The active cross-connect board is faulty.
a. Replace the active cross-connect board. For details, see Supporting Tasks. Then
check whether the alarm is cleared.
b. If the alarm persists, see Cause 3.
l Cause 3: The service board is faulty.
a. Perform a cold reset on the service board that reports the alarm by using the NMS,
or remove and then insert the service board that reports the alarm. For the
operations that are performed on the NMS, see Supporting Tasks. For operations of
removing and then inserting a board, see the Installation Guide. Then, check
whether the alarm is cleared.
b. If the alarm persists, replace the board that reports the alarm. For details, see
Supporting Tasks.
----End
Related Information
The active cross-connect board refers to the cross-connect board inserted in the slot of a
smaller ID.
The standby cross-connect board refers to the cross-connect board inserted in the slot of a
larger ID.
4.356 SM_BDI
Description
The SM_BDI is an alarm indicating a backward defect in SM overheads at the optical
transponder unit (ODU) layer. This alarm is generated when major alarms occur at the remote
OTU and upper layers.
Attribute
Parameters
None
Possible Causes
l Alarms occur on the remote OTU termination NE.
l The local transmit unit is faulty.
l The remote receive unit is faulty.
Procedure
Step 1 Check whether severer alarms occur on the remote OTU termination NE. If yes, clear the
alarms according to the related alarm-handling methods. Then check whether the SM_BDI
alarm is cleared.
Step 2 If alarms at the remote end persist, perform a loopback on the local optical ports. If any
alarms occur, correct configurations according to the alarms.
NOTICE
A loopback interrupts services.
Step 4 If the alarms at the remote end persist and the loopback test detects no abnormality on the
local optical ports, replace the remote board.
Step 5 If the alarm persists, contact Huawei for help.
----End
Related Information
Related Cases:
l MC-A37 The LWFS in the OptiX BWS 1600G Transiently Reports FEC_LOF Alarm
l MC-A56 LWF Board Reports OTU_LOF Alarm
l MC-A57 How to Clear OTU Alarms Because of Unused Ports
4.357 SM_BEI
Description
The SM_BEI is an alarm indicating a backward error in PM overheads at the optical
transponder unit (OTU) layer. This alarm is generated when SM-BIP check bit errors occur at
the remote end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Bit errors occur on the remote OTU termination NE.
l The local transmit unit is faulty.
l The remote receive unit is faulty.
Procedure
Step 1 Check board performance on the remote OTU termination NE and clear the remote bit errors.
----End
Related Information
None
4.358 SM_BIP8_OVER
Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the SM section at
the optical transponder unit (OTU) layer exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l The received signals are heavily attenuated.
l The fiber connector is contaminated.
l The connector is improperly connected.
l The local receive unit is faulty.
l The peer transmit unit is faulty.
Procedure
Step 1 On the NMS, check whether severer alarms occur, for example, the R_LOS and R_LOF
alarms. Clear these alarms first and check whether the SM_BIP8_OVER alarm is cleared.
Step 2 Check whether the receive optical power of the alarm-reporting board is within the permitted
range. If yes, go to step 9.
Step 3 Clean the local pigtail connector and the receive optical port on the line board. Then, check
whether the alarm is cleared.
Step 4 Check whether the flange is correctly connected to the optical attenuator on the local NE, and
whether the attenuation value specified for the optical attenuator is proper. After determining
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
Step 5 Check whether the peer transmit optical power is within the permitted range. If not, replace
the line board.
Step 6 If the transmit optical power is within the permitted range, clean the peer pigtail connector.
Then, check whether the alarm is cleared.
Step 7 Check whether the flange is correctly connected to the optical attenuator on the peer NE, and
whether the attenuation value specified for the optical attenuator is proper. After determining
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
Step 8 Verify that optical fibers are properly connected. Then, check whether the alarm is cleared.
Step 9 Replace the local line board that reports the alarm. Then, check whether the alarm is cleared.
Step 10 Replace the local cross-connect board. Then, check whether the alarm is cleared.
Step 11 Replace the peer line board. Then, check whether the alarm is cleared.
Step 12 Replace the peer cross-connect board. Then, check whether the alarm is cleared.
Step 13 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
Related Cases:
l MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction and the SM_BIP8_OVER and SM_BIP8_SD Alarms Are Transiently
Reported on the Board
4.359 SM_BIP8_SD
Description
The SM_BIP8_SD is an alarm indicating that the signals degrade in the PM section at the
optical transponder unit (OTU) layer.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The received signals are heavily attenuated.
l The fiber connector is contaminated.
l The connector is incorrectly connected.
l The local receive unit is faulty.
l The peer transmit unit is faulty.
Procedure
Step 1 On the NMS, check whether severer alarms occur, for example, the R_LOS and R_LOF
alarms. Clear these alarms first and check whether the SM_BIP8_SD alarm is cleared.
Step 2 Check whether the receive optical power of the alarm-reporting board is within the permitted
range. If yes, go to step 9.
Step 3 Clean the local pigtail connector and the receive optical port on the line board. Then check
whether the alarm is cleared.
Step 4 Check whether the fiber adapter is correctly connected to the optical attenuator on the local
NE, and whether the attenuation value specified for the optical attenuator is proper. After
determining that the fiber adapter and optical attenuator are used properly, check whether the
alarm is cleared.
Step 5 Check whether the peer transmit optical power is within the permitted range. If not, replace
the line board.
Step 6 If the transmit optical power is within the permitted range, clean the peer pigtail connector.
Then check whether the alarm is cleared.
Step 7 Check whether the fiber adapter is correctly connected to the optical attenuator on the peer
NE, and whether the attenuation value specified for the optical attenuator is proper. After
determining that the fiber adapter and optical attenuator are used properly, check whether the
alarm is cleared.
Step 8 Verify that optical fibers are properly connected. Then check whether the alarm is cleared.
Step 9 Replace the local line board that reports the alarm. Then check whether the alarm is cleared.
Step 10 Replace the local cross-connect board. Then check whether the alarm is cleared.
Step 11 Replace the peer line board. Then check whether the alarm is cleared.
Step 12 Replace the peer cross-connect board. Then check whether the alarm is cleared.
----End
Related Information
Related Cases:
l MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction and the SM_BIP8_OVER and SM_BIP8_SD Alarms Are Transiently
Reported on the Board
4.360 SM_IAE
Description
The SM_IAE is an alarm indicating an incoming alignment error (IAE) in the SM section at
the optical transponder layer (OTU). When the ODU frame is synchronously mapped into the
OTU frame, the IAE flag is set to true if a frame alignment error occurs. This alarm is
generated when the sink NE detects the IAE which indicates subframe alignment bit errors
occur in the received services.
Attribute
Parameters
None
Possible Causes
l A clock jitter event occurs in the transmit unit on the remote NE (the source of the
OTU/ODU adaption function).
l The frame offset on the termination side of the remote NE (the source of the OTU/ODU
adaption function) is inaccurate.
l The FEC processing chip on the remote NE (the source of the OTU/ODU adaption
function) is faulty.
Procedure
Step 1 Adjust the frame offset on the board system side of the remote NE (the source of the
OTU/ODU adaption function). Then check whether the alarm is cleared.
Step 2 If the alarm persists, replace the board on the remote NE (the source of the OTU/ODU
adaption function).
----End
Related Information
None
4.361 SM_TIM
Description
The SM_TIM is an alarm indicating a trail trace identifier (TTI) mismatch in the PM
overheads at the OTU layer.
Attribute
Parameters
None
Possible Causes
l The SM_TTI byte expected by the local NE is incorrectly set.
l The SM_TTI byte transmitted by the remote NE is incorrectly set.
l The fiber is incorrectly connected.
Procedure
Step 1 Determine the expected setting of the SM_TTI byte based on actual situations.
Step 2 Check whether the SM_TTI byte expected by the board is consistent with the received
SM_TTI byte. If the settings of the expected SM_TTI byte are incorrect, modify the setting.
Step 3 If the received SM_TTI byte is incorrect, verify that the fiber connection on the local optical
port is correct.
Step 4 Verify that the setting of the SM_TTI byte transmitted in the upstream services is correct.
----End
Related Information
None
4.362 SNCP_FAIL
Description
The SNCP_FAIL is an alarm indicating an SNCP switching failure.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
During the SNCP switching, the service grooming fails.
Procedure
Step 1 Reset the SCC board to re-configure all the services.
----End
Related Information
None
4.363 SO_SK_MISMATCH
Description
The SO_SK_MISMATCH is an alarm indicating that the number of timeslots is different on
the source and sink of the link capacity adjustment scheme (LCAS). This alarm is generated
when the number of upstream (or downstream) timeslots configured for the local VCTRUNK
port is inconsistent with that of downstream (or upstream) timeslots configured for the peer
VCTRUNK port.
Attribute
Parameters
None
NOTICE
After this alarm occurs, the intermediate timeslots deleted from the sink are added to other
VCTRUNK ports. As a result, services on the VCTRUNK ports are interrupted. Make the
number of timeslots consistent between the source and sink before you proceed.
Possible Causes
The number of timeslots is different on the source and sink of the LCAS.
NOTE
If an intermediate timeslot is deleted from the sink but the corresponding timeslot is not deleted from the
source, this alarm is reported.
If the last timeslot is deleted from the sink, but the corresponding timeslot is not deleted from the source,
this alarm is not reported.
Procedure
Step 1 View the alarm on the NMS and determine the number of the VCTRUNK port.
Step 2 On the NMS, check whether the number of upstream (or downstream) timeslots configured
for the local VCTRUNK port is consistent with that of downstream (or upstream) timeslots
configured for the peer VCTRUNK port. If not, add or delete timeslots based on actual
requirements to make the number of timeslots consistent. Then check whether the alarm is
cleared.
----End
Related Information
None
4.364 SPAN_LOSS_EXCEED_EOL
Description
Span fiber loss exceeding EOL. This alarm is generated when the actual fiber loss is larger
than the EOL value.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The line fiber ages or the ambient temperature changes, which causes excessively large line
loss.
Procedure
Step 1 Check whether the line fiber connections are normal, whether the fibers are aged, and whether
the fiber connectors are clean.
Step 2 Check whether the insertion loss of the board is normal.
----End
Related Information
None
4.365 SPAN_LOSS_HIGH
Description
Line insertion loss being too high. This alarm is generated when the actual line insertion loss
is greater than the reference value and the difference between the actual value and the
reference value exceeds the alarm threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l The line fiber is aging.
l The line insertion loss increases.
l The alarm threshold is incorrect.
l The insertion loss of a board on the line is abnormal.
l The sampled reference value of the line attenuation is inappropriate.
Procedure
Step 1 Check whether the line fiber connections are abnormal and whether the fibers are aging. If the
line fiber connections are abnormal or the fibers are aging, reconnect the fibers or replace the
aging fibers.
Step 2 Check whether any VOA is not configured on the line. If unconfigured VOAs are found,
manually adjust the attenuation to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively
low, set the alarm threshold according to the plan of the live network.
Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary,
refer to Replace the board.
Step 5 If none of the preceding problems occurs, re-sample the reference value.
----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.366 SPAN_LOSS_LOW
Description
Line insertion loss being too low. This alarm is generated when the actual line insertion loss is
lower than the reference value and the difference between the actual value and the reference
value exceeds the alarm threshold.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
l Aging fibers on the line are replaced with new fibers, or the line insertion loss decreases.
l The sampled reference value of the line attenuation is inappropriate.
Procedure
Step 1 Check whether the line fibers are aging. If the line fibers are new fibers, enable the ALC
function and sample the reference value again.
Step 2 Check whether any VOA is not configured on the line. If unconfigured VOAs are found,
manually adjust the attenuation to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively
low, set the alarm threshold according to the plan of the live network.
Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary,
refer to Replace the board.
Step 5 If none of the preceding problems occurs, re-sample the reference value.
----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.367 SPAN_LOSS_LOWER_GAIN
Description
Span loss lower than the gain compensation value. This alarm is generated when the actual
span loss is smaller than the power compensation value and the difference between the two
exceeds the specified threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Because of incorrect adjustment, board faults, span fiber aged, and environment temperature
changes, the actual span loss becomes smaller than the gain compensation value and the
difference between them exceeds the threshold.
Procedure
Step 1 Verify that the line fiber connections are normal.
Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the VOA
attenuation to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If required, change the threshold to an
appropriated value according to the network plan and actual network requirements.For details
about the method of setting the alarm thresholds, see Configuring the OD Monitoring
Function. Among the threshold parameters, Line Attenuation Compensation
Threshold(dB) indicates the threshold for the difference between the loss of optical
transmission section (OTS) and OA gain.
Step 4 Verify that the insertion loss of the board is normal.
----End
Related Information
None
4.368 SPAN_LOSS_UPPER_GAIN
Description
Span loss upper than the gain compensation value. This alarm is generated when the actual
span loss is larger than the power compensation value and the difference between the two
exceeds the specified threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Because of incorrect adjustment, board faults, span fiber aged, and environment temperature
changes, the actual span loss becomes larger than the gain compensation value and the
difference between them exceeds the threshold.
Procedure
Step 1 Check whether the line fiber connections are normal, whether the fibers are aged, and whether
the fiber connectors are clean.
Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the VOA
attenuation to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If required, change the threshold to an
appropriated value according to the network plan and actual network requirements.For details
about the method of setting the alarm thresholds, see Configuring the OD Monitoring
Function. Among the threshold parameters, Line Attenuation Compensation
Threshold(dB) indicates the threshold for the difference between the loss of optical
transmission section (OTS) and OA gain.
----End
Related Information
None
4.369 SPEED_OVER
Description
The SPEED_OVER is an alarm indicating that the data rate exceeds the configured limit. It
indicates a mismatch between the rate of the monitored optical port and the preset rate. This
alarm is generated when a board detects that the received rate mismatches the preset one.
Attribute
Parameters
None
Possible Causes
l The set rate of the optical port is incorrect.
l The board hardware is faulty.
Procedure
Step 1 Query the configured rate and actual rate on the U2000, and determine whether the configured
rate is incorrect.
Step 3 If the alarm persists, check whether the input optical power is normal. If the input optical
power is excessively high or excessively low, adjust it.
Step 4 If the alarm persists, check whether a hardware fault occurs on the board, that is, whether
there is a HARD_BAD or a HARD_ERR alarm at the local station. If yes, replace the relevant
board. For details, see the Parts Replacement
----End
Related Information
None
4.370 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD is an alarm indicating that Ethernet services are shut down. This
alarm is generated when an Ethernet service is shut down due to a service loopback. This
alarm is cleared after the Ethernet service is restarted.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible cause of the SRV_SHUTDOWN_LD alarm is as follows:
l There is a loopback in the network.
Procedure
Step 1 There is a loopback in the network.
1. Query alarm information on the NMS to find out the Ethernet service that is shut down.
2. Check whether a loopback is configured on the service trail that carries the Ethernet
service. If yes, release the loopback based on network plan.
3. Restart the shutdown service and the alarm is cleared automatically.
NOTE
If the loopback is not released, the network will report the alarm again after the Ethernet service is
restarted.
----End
Related Information
None
4.371 SSL_CERT_DAMAGED
Description
User-defined SSL certificate file damaged alarm.
Attribute
Parameters
None
Possible Causes
A user-defined SSL certificate file is damaged.
Procedure
Step 1 On the U2000, download and activate a user-defined SSL certificate file.
----End
Related Information
None
4.372 SSL_CERT_NOENC
Description
Certificate file of SSL not encrypted.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The certificate file of SSL is not encrypted.
Procedure
Step 1 On the U2000, download and activate the encrypted SSL certificate file.
----End
Related Information
None
4.373 SSL_CERT_TO_EXPIRE
Description
SSL certificate file is to expire alarm. This alarm is generated when the SSL certificate file is
going to expire two months later.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The SSL certificate file will expire two months later.
Procedure
Step 1 On the U2000, download and activate a user-defined SSL certificate file.
----End
Related Information
None
4.374 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 the specified period.
NOTE
For TN54TOA and TN54THA boards, the specified period is SSM Timeout Period (500ms), For other
boards, the specified period is 5 seconds.
Attribute
Alarm Severity Alarm Type
Parameters
None
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.375 SSM_QL_FAILED
Description
This alarm indicates that the received SSM quality is worse than the threshold. This alarm is
generated when the SSM quality received by a reference NE configured in the priority table is
worse than the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
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 queried SSM quality is the
same as the plan. If not, check whether the master NE properly traces the upstream NE.
Step 2 If the received SSM quality is normal, check whether the threshold is properly set based on
the network plan. If not, set the threshold again.
----End
Related Information
None
4.376 STORM_CUR_QUENUM_OVER
Description
Alarm storm. Some alarms on the system control board may be lost when the alarm queue is
full. This alarm indicates that the alarm module is in the alarm storm state.
Attribute
Parameters
None
Possible Causes
The alarm queue fails to contain all the alarms when there are excessive alarms.
Procedure
Step 1 Handle the existing alarms (except the STORM_CUR_QUENUM_OVER alarm). The
STORM_CUR_QUENUM_OVER alarm clears when the number of current alarms is equal
to or smaller than the STORM_CUR_QUENUM_OVER alarm threshold.
----End
Related Information
None
4.377 SUBNET_RT_CONFLICT
Description
The SUBNET_RT_CONFLICT is an alarm indicating a subnetwork route conflict. This alarm
occurs when the subnet route of an NMS port, that is, the IP subnet route of an NE, covers the
learned route of an OSPF subnet whose mask is longer than that of the IP subnet.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 Indicate the IP address of the subnet whose route is covered by the NE
Parameter 4 IP subnet route and whose mask is longer than that of the NE IP
subnet.
When the routes of multiple subnets are covered by the IP subnet
route, this parameter is the IP address of the subnet with the longest
mask.
Possible Causes
The subnet route of an NMS port (the IP subnet route of an NE) covers the learned route of an
OSPF subnet whose mask is longer than that of the IP subnet.
Procedure
Step 1 Collect the information about all NEs that report this alarm and check the DCN networking
based on the planned network topology.
Step 2 Obtain the information about the conflicting subnets and their masks based on the alarm
parameters.
Step 3 Determine the rectification plan based on the network topology and subnet information to
ensure that the subnet masks of non-gateway NEs are consistent with the mask of the gateway
NE. When subnet masks of multiple NEs need to be changed, change their subnet masks from
the farthest NE to the nearest one.
CAUTION
If the mask of a gateway NE needs to be changed, ensure that the DCN route after the change
is correct. If the DCN route is incorrect, NEs may be unreachable to the NMS.
----End
Related Information
None
4.378 SUBRACK_COMM_PS
Description
ETH2 port status. This alarm indicates that the ETH2 port in the master subrack is in working
state when the master subrack is under inter-subrack communication protection.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The ETH2 port in the master subrack is in working state when the master
subrack is under inter-subrack communication protection.
Procedure
l Cause 1: The ETH2 port in the master subrack is in working state when the master
subrack is under inter-subrack communication protection.
a. If the ETH2 port in the master subrack is in working state when the master subrack
is under inter-subrack communication protection, the original working channel
where the ETH1 port is located is malfunctioning. Check for any LAN_LOC alarm
on the NE. If the alarm is reported, restore the subrack connection according to the
alarm processing method. After the connection is restored, inter-subrack
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
4.379 SUBRACK_EXCEED
Description
Number of slave subracks exceeding threshold. This alarm is generated when the number of
master and slave subracks on a single NE is beyond the management capability of the system
control board in the master subrack.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The number of logical slave subracks on an NE is beyond the management capability of the
system control board in the master subrack of the NE.
Procedure
Step 1 The number of subracks supported by an NE depends on the types of subracks and system
control boards. For details, see Master-Slave Subrack Planning Principles and Capabilities in
the Product Description.
Step 2 When the number of subracks on an NE is beyond the management capability of the NE,
manage the subracks using two NEs so that the number of master and slave subracks on each
NE is within the management capability of the corresponding system control board.
----End
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
4.380 SUBRACK_ID_MISMATCH
Description
Mismatch of subrack IDs.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The DIP switch of the subrack ID is changed. The subrack ID detected by the NE software
and board software mismatches the actual subrack ID.
Procedure
Step 1 Change the DIP switch of the AUX board or EFI1 board to the subrack ID displayed in the
statistics diode of the system control board or power off the subrack.
----End
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
4.381 SUBRACK_LOOP
Description
Subracks are looped. This alarm is generated when the cascaded subracks form a closed loop.
Attribute
Parameters
None
Possible Causes
l In the master/slave subrack mode, the internal network ports are connected in a closed
loop.
l The AUX board is faulty, which leads to abnormal communication.
Procedure
Step 1 Confirm the subrack cascading mode according to the network plan. If the planned subrack
cascading mode is the ring mode, set the subrack cascading mode to ring on the NMS. If the
planned subrack cascading mode is the tree mode, check cable connections between subracks
and ensure that all subracks are cascaded in tree mode.
Step 2 If the alarm persists, perform a warm reset or perform a cold reset on the faulty board on the
U2000.
Step 3 If the alarm persists, replace the AUX board. For details, see "Replacing the AUX Board" in
the Parts Replacement.
----End
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
4.382 SUBRACK_TYPE_MISMATCH
Description
Subrack types are inconsistent.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The type of the configured logical subrack mismatches the type of the physical subrack.
Procedure
Step 1 Determine whether the logical subrack or the physical subrack is incorrect according to the
actual network.
Step 2 If the logical subrack is incorrect, perform the operations as follows:
l If the logical subrack of a non-enhanced subrack is incorrect, delete the incorrect subrack
from the U2000 and configure a correct logical subrack that is consistent with the
physical subrack.
l If the logical subrack of an enhanced subrack is falsely configured as a non-enhanced
subrack or that of a non-enhanced subrack is falsely configured as an enhanced subrack,
perform the following operations to clear the alarm:
a. If the logical master subrack is incorrect, delete the NE database from the U2000,
perform a cold reset on the system control board, delete the NE and create one
again, and configure a correct logical master subrack that is consistent with the
physical subrack.
NOTE
When creating the NE again, select Manual Configuration in the NE configuration wizard;
otherwise, the NE data loading will fail because the NE is in the installation state.
b. If the logical slave subrack is incorrect, delete the incorrect subrack from the U2000
and configure a correct logical subrack that is consistent with the physical subrack.
Step 3 If the physical subrack is incorrect, replace the subrack with a correct one and configure a
correct subrack ID. For details on the operations, see Feature Description.
Step 4 If the alarm persists, contact Huawei for assistance.
----End
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
4.383 SUM_INPWR_HI
Description
Input optical power of multiplexed wavelengths is excessively high. The alarm is generated
when the input optical power of multiplexed signals exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The output optical power of the board at the upstream site is normal and the power of the
received optical signals received by the board at the local site is excessively high. No
proper attenuation is added.
l The output optical power of the board at the upstream site or peer site is excessively
high.
Procedure
Step 1 Check whether the input optical power of the input port of the board at the local site is within
the permitted range using an optical power meter. For the optical power specifications of the
specific board, see "Technical Specifications" in the Product Description. If the power is not
within the permitted 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 sites
is within the permitted range using the U2000. For the optical power specifications of the
specific board, see "Technical Specifications" in the Product Description. If the input optical
power of the board at the local site 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 sites is excessively high, respectively check whether the corresponding input and
output optical power of each upstream site is within the permitted range.
l If the input and output optical power of the board at the upstream site is not within the
permitted range, adjust the input optical power to a value within the permitted range. For
the optical power specifications of the specific board, see "Technical Specifications" in
the Product Description.
l If the input optical power of the board at the upstream site is within the permitted range
but the output optical power is not within the permitted range, the board at the upstream
site may be faulty. Replace the board.
Step 3 If the alarm persists, the board at the local site is faulty. Replace the faulty board with
reference to Replace the board..
----End
Related Information
None
4.384 SW_SNCP_PS
Description
The SW_SNCP_PS is an alarm indicating the SW SNCP protection switching. This alarm is
generated when the SW SNCP protection group actuates switching in which the current
channel switches to the protection channel from the working channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: A user issues an external switching command such as forced switching or
manual switching. Such a command makes the current channel of the SW SNCP
protection group switch to the protection channel from the working channel. Therefore,
the alarm is reported.
l Cause 2: The services of the working channel of the SW SNCP protection group are
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching or manual switching, check whether the external switching operation is
necessary,
1. If the external switching operation is necessary, ignore the alarm.
2. If the external switching operation is unnecessary, issue an external command to switch
the current channel to the working channel, in this way clearing the alarm.
Step 2 If the alarm is generated during the automatic switching of the protection group, perform the
following operations:
1. Query whether the related boards for configuring the protection group have alarms
related to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK,
REM_SF, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
OTUk_DEG, OTUk_EXC, or REM_SD. If yes, handle the alarms with reference to the
corresponding alarm handling procedures.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, after WTR Times the current channel will automatically switch to the working
channel and the alarm will be cleared. If the attribute is Non-Revertive, change it to
Revertive, and after WTR Times the alarm will be cleared.
----End
Related Information
For details, see "SW SNCP Protection" in the Feature Description.
4.385 SW_SNCP_STA_INDI
Description
The SW_SNCP_STA_INDI is an alarm indicating the status of the SW SNCP protection
group. This alarm is generated when the working or protection channel of the protection
group is faulty or the user runs an external switching command.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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.
Parameter Description
Possible Causes
l The user issues an external switching command such as forced switching, manual
switching or locked switching.
l The services of the working or protection channel of the SW SNCP group are faulty.
l The switching is in WTR state. After the WTR time, the alarm is cleared.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching, manual switching, or locked switching, check whether the external
switching is necessary.
1. If the external switching is necessary, ignore the alarm.
2. If the external switching is unnecessary, issue a switching clearing command to clear the
external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, perform the following operations:
1. Query whether the alarm such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK,
REM_SF, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
OTUk_DEG, OTUk_EXC, or REM_SD is reported on the related boards for configuring
the protection group. If the alarm exists, handle it using the corresponding alarm
handling procedure to restore the services of the working or protection channel.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, after WTR Times the services will be automatically switched to the working
channel, and the alarm will be cleared. If no, set it to Revertive, and after WTR Times
the alarm will be cleared.
Step 3 On the U2000, query the switching status of the protection group. If the switching is in WTR
state, the alarm does not need to be handled and will be cleared after the WTR time.
----End
Related Information
For details, see "SW SNCP Protection" in the Feature Description.
4.386 SWDL_ACTIVATED_TIMEOUT
Description
Activation timeout. This alarm is generated when the activation operation is not committed
within 120s after the activation is complete during software package loading.
Attribute
Parameters
None
Possible Causes
The activation operation is not committed within 120 seconds after the activation is complete
during software package loading.
Procedure
Step 1 Commit the activation operation. If the alarm persists, check whether the software version is
correct. If the software version is incorrect, roll back the NE to the version before package
loading, and contact Huawei engineers to determine a correct software package. On the NMS,
use the correct software package to perform package loading on the board again.
NOTICE
Services may be affected if an incorrect software package is used for package loading.
Therefore, perform the procedure under guidance of Huawei engineers.
----End
Related Information
None
4.387 SWDL_AUTOMATCH_INH
Description
Automatic match inhibited. This alarm indicates that the automatic matching function is
disabled.
NOTE
After the automatic matching function is enabled, when a board is added to an NE, the system automatically
checks whether the board software matches the NE software. If the board software does not match the NE
software, the system control board upgrades the software of the new board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The automatic matching function is disabled.
Procedure
Step 1 If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.388 SWDL_BD_EXCLUDE
Description
Board being excluded during software package loading. This alarm is generated when the
software package loading of a board fails and the board is added to the exclusion list because
the board goes offline, the storage space is insufficient, or the board fails to communicate with
the system control board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The board is offline.
l Cause 2: The communication between the board and the system control 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 In the DC window of the U2000, check the information about the board that is excluded
during package loading.
Step 2 Check whether the excluded board is offline. If it is, enable the board to go online again.
Step 3 Check whether any COMMUN_FAIL alarm is generated on the excluded board. If the alarm
is generated, handle the problem with reference to the alarm handling method.
Step 4 Check whether the flash memory space on the board is sufficient. If the space is insufficient,
clean up the board for more space.
Step 5 Check whether the downloaded software matches the NE software version. If they mismatch,
download the correct software again.
Step 6 If the results of the preceding items are normal, select the excluded board in the DC window,
download software again, and activate the software.
Step 7 After handling all excluded boards, release the board exclusion. Then, the
SWDL_BD_EXCLUDE alarm will be cleared.
----End
Related Information
None
4.389 SWDL_BD_MATCH_FAIL
Description
The SWDL_BD_MATCH_FAIL alarm indicates a board software matching failure. This
alarm is reported if the board software version and the NE version mismatch during an NE
upgrade or downgrade.
Attribute
Alarm Severity Alarm Type
Parameters
None
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
Step 1 Check whether any COMMUN_FAIL alarm is generated on the board. If the alarm is
generated, handle the problem with reference to the alarm handling method.
Step 2 Check whether the free space of the board is sufficient. If the space is insufficient, contact
Huawei to release board storage space. Otherwise, perform a warm reset on the board.
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
Related Information
None
4.390 SWDL_BD_NOT_MATCH
Description
Board software mismatch alarm. The SWDL_BD_NOT_MATCH is an alarm indicating that
the actual board software version mismatches the board software version in the system control
board software package.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The software version of a board mismatches the board software version in the system control
board software package.
Procedure
Step 1 Check whether any COMMUN_FAIL alarm is generated on the board. If the alarm is
generated, handle the problem with reference to the alarm handling method.
Step 2 Check whether the free space of the board is sufficient. If the space is insufficient, contact
Huawei to release board storage space. Otherwise, perform a warm reset on the board.
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
Related Information
None
4.391 SWDL_BD_WEAKMATCH
Description
Weak matching between board software and NE software. This alarm is reported when the
software of boards on an NE weakly matches the NE software.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
During the NE upgrade, the software of some boards is inconsistent with the software package
but is compatible with the software version. The software of these boards will not be
upgraded. After the upgrade is complete, this alarm is reported if the NE contains this type of
boards.
Procedure
Step 1 After the package loading, check the weakly matched boards displayed in the DC window.
Step 2 Select the desired board and click Start in the DC window to enable the board software to
match the NE software.
Step 3 The alarm may be cleared after the board matching is completed or the next upgrade is
performed.
----End
Related Information
None
4.392 SWDL_CHGMNG_NOMATCH
Description
Software mismatching alarm after system control board replacement. The system re-checks
whether the software of each board matches the NE software after the NE starts up upon a
power failure or the system control board is replaced or reset (cold). This alarm is generated
when the board software of a board mismatches the NE software.
Attribute
Parameters
None
Possible Causes
l After the NE is powered off, a board is inserted and the software version of the board is
inconsistent with that of the system control board.
l The system control board is replaced and the software version of the new system control
board is inconsistent with the NE software version.
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the
correct software package to perform package loading on the board. In normal cases, this alarm
is automatically cleared after the package loading succeeds.
NOTICE
Services may be affected if an incorrect software package is used for package loading.
Therefore, perform the procedure under guidance of Huawei engineers.
----End
Related Information
Related Cases:
l MC-A85 SWDL_CHGMNG_NOMATCH Alarm Is Reported
l MC-A86 Inserting, Removing, and Resetting Operations Affect NG WDM Products
l MC-A87 SWDL_CHGMNG_NOMATCH Alarm Is Reported
l MC-A221 The Board Software Fails to Automatically Match a Board After the Board is
Replaced
4.393 SWDL_COMMIT_FAIL
Description
Commit failure. This alarm is generated when the commit operation fails during software
package loading.
Attribute
Parameters
None
Possible Causes
During package loading, the dual-partition board fails in copying the new software from one
partition to the other.
NOTE
The dual-partition board has two file systems. The two partitions are of mutual backups. In normal states,
every file is saved in both partitions.
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the
correct software package to perform package loading on the board. In normal cases, this alarm
is automatically cleared after the package loading succeeds.
NOTICE
Services may be affected if an incorrect software package is used for package loading.
Therefore, perform the procedure under guidance of Huawei engineers.
----End
Related Information
None
4.394 SWDL_INPROCESS
Description
NE being loading packages. This alarm is generated when the NE is performing package
loading and the alarm clears after the NE finishes the commit operation.
Attribute
Parameters
None
Possible Causes
The NE is performing package loading.
Procedure
Step 1 The software package loading is still in process. Wait until the package loading is complete
and the alarm clears.
----End
Related Information
None
4.395 SWDL_PKG_NOBDSOFT
Description
Board software canceled during customized package loading. This alarm is generated when
the customized software package of an NE does not contain the software of the boards
inserted to the NE after the software package is loaded for the NE and the software versions
of the boards do not match the version of the customized software.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual
requirement.
NOTE
This alarm is also generated if a board is inserted when the SWDL_CHGMNG_NOMATCH alarm is
reported.
Attribute
Parameters
None
Possible Causes
The customized software package contains the software information of only customized
boards.
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the
correct software package to perform package loading on the board. In normal cases, this alarm
is automatically cleared after the package loading succeeds.
NOTICE
Services may be affected if an incorrect software package is used for package loading.
Therefore, perform the procedure under guidance of Huawei engineers.
----End
Related Information
None
4.396 SWDL_PKGVER_MM
Description
Package version consistency check failure. This alarm is generated when the software version
information (similar to the file list category) of the software package is not consistent with the
actual software version information.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The files in the software package are faulty and therefore the software version information of
the software package is not consistent with the actual software version information.
Procedure
Step 1 Contact Huawei engineers to handle this alarm.
----End
Related Information
None
4.397 SWDL_ROLLBACK_FAIL
Description
NE rollback failure. This alarm is generated when the rollback of any board fail during an NE
rollback.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The rollback of certain boards fails during the NE rollback.
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the
correct software package to perform package loading on the board. In normal cases, this alarm
is automatically cleared after the package loading succeeds.
NOTICE
Services may be affected if an incorrect software package is used for package loading.
Therefore, perform the procedure under guidance of Huawei engineers.
----End
Related Information
None
4.398 SYN_BAD
Description
SYN_BAD is a synchronization source degrade alarm. This alarm is generated when the
frequency deviation of the synchronization source exceeds the permitted range so that quality
of the physical-layer synchronization source deteriorates.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 subrack where the clock board is located.
Parameter 2 Indicates the ID of the slot in the subrack where the clock source of the service
board is located. If the external clock source is used, the value is always 0xf0.
Parameter 4 In the case of the clock source of the service board, it indicates the number of
the port in the subrack where the clock source is located.
In the case of the external clock source, it indicates the sequence number of the
external clock.
l 0x01: the first external clock
l 0x02: the second external clock
Parameter 5 l 0x01: The frequency deviation is larger than 9.2 ppm for physical-layer
synchronization.
l 0x02: The frequency deviation detected by DSP exceeds the permitted
range for PTP synchronization.
Possible Causes
The possible causes of the SYN_BAD alarm are as follows:
l Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
l Cause 2: The input and output modes of the external clock source are inconsistent.
l Cause 3: The clock board that reports the alarm is faulty.
Procedure
l Check whether any higher-level bit error alarm (such as B1_EXC, B1_SD, B2_EXC,
B2_SD or MS_CROSSTR) or performance event is detected on the U2000. If yes, take
priority to handle the higher-level alarm or performance event, and then check whether
the SYN_BAD alarm is cleared.
l Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
a. If an external clock source is traced, check whether the clock signals are normal. If
not, replace the external clock source. For details, see Configuring Physical Clock
in the Feature Description.
l Cause 2: The input and output modes of the external clock source are inconsistent.
a. If the alarm persists, check whether the input and output modes of the external
clock source are consistent. After the input and output of the external clock source
are set to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is
cleared. For details, see Configuring Physical Clock in the Feature Description.
l Cause 3: The clock board that reports the alarm is faulty.
a. If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
b. If the alarm persists, replace the clock board. For details, see the Parts
Replacement.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.399 SYNC_C_LOS
Description
SYNC_C_LOS is an alarm indicating a synchronization source priority loss. This alarm is
generated when the clock source on a service board is absent from the priority table.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameter 1 Indicates the ID of the subrack where the switched clock source is located.
Parameter 2 Indicates the ID 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 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 sequence number of the
external clock.
l 0x01 indicates the first external clock.
l 0x02 indicates the second external clock.
Possible Causes
The possible causes of the SYNC_C_LOS alarm are as follows:
l Cause 1: Input signals are lost at the optical or electrical port that is connected to the
clock source.
l Cause 2: A fiber cut occurs when a line clock source is traced.
l Cause 3: The service board is faulty.
l Cause 4: The timing board is faulty.
Procedure
l Cause 1: Input signals are lost at the optical or electrical port that is connected to the
clock source. Cause 2: A fiber cut occurs when a line clock source is traced.
a. On the U2000, check whether the R_LOS alarm is generated on the relevant service
board. If yes, take priority to clear the R_LOS alarm, and then check whether the
SYNC_C_LOS alarm is cleared.
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.400 SYNC_DISABLE
Description
Automatic synchronization of the system control board being disabled. When the automatic
synchronization of the system control board is disabled, batch backup is not supported and
this alarm is generated.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The automatic synchronization state of the system control board is changed from enabled to
disabled.
Procedure
Step 1 Change the automatic synchronization state of the system control board to enabled. The alarm
is cleared automatically.
----End
Related Information
None
4.401 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH is an alarm indicating the forced or manual switching state of a
clock source.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the subrack where the switched clock source is located.
Parameter 2 Indicates the ID 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 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 sequence number of the
external clock.
l 0x01 indicates the first external clock.
l 0x02 indicates the second external clock.
Parameter 5 Indicates the ID of the priority table. Valid values are as follows:
l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source
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 U2000, 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. For details, see Configuring Physical Clock in the Feature
Description.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.402 SYNC_FAIL
Description
Batch backup failure.
Attribute
Alarm Severity Alarm Type
Parameters
Parameter Description
Possible Causes
l The database backup fails.
l Software versions of the active and standby boards are inconsistent.
l The communication on the standby board is unstable or unavailable.
l During the database backup process, the user performs configuration on a system control
board, or other users log in to the NE.
l Cause 1: The main and standby SCC boards have different versions of software.
l Cause 2: Databases on the main and standby SCC boards are damaged.
l Cause 3: The main and standby SCC boards have different data after an upgrade.
l Cause 4: Communication between the main and standby SCC boards fails.
l Cause 5: Forced switching occurs before the database backup is completed.
Procedure
Step 1 Cause 1: The main and standby SCC boards have different versions of software.
1. Query and record the software versions of the main and standby SCC boards according
to Querying the Board Information Report.
2. If the software versions are different, determine the correct version based on the version
mapping table and replace the SCC board with an incorrect version.
Step 2 Cause 2: Databases on the main and standby SCC boards are damaged.
1. Check whether the system reports the DBMS_ERROR alarm.
2. If yes, clear the DBMS_ERROR alarm. Then, check whether the SYNC_FAIL alarm is
cleared.
Step 3 Cause 3: The main and standby SCC boards have different data after an upgrade.
1. Re-install the standby SCC board.
Step 4 Cause 4: Communication between the main and standby SCC boards fails.
1. Check whether the system reports the COMMUN_FAIL alarm.
2. If yes, clear the COMMUN_FAIL alarm. The system will start batch backup
automatically.
Step 5 Cause 5: Forced switching occurs before the database backup is completed.
1. Perform a warm reset on the board that reports the alarm.
----End
Related Information
None
4.403 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating that the clock source in the priority list is
locked.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 subrack where the locked clock source is located.
Parameter 2 Indicates the ID 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.
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 locked clock source is located.
In the case of the external clock source, it indicates the sequence number of the
external clock.
l 0x01 indicates the first external clock.
l 0x02 indicates the second external clock.
Possible Causes
Cause 1: The NE software issues a command to lock the clock source.
Procedure
l View the SYNC_LOCKOFF alarm on the U2000, 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 U2000, the
SYNC_LOCKOFF alarm is automatically cleared. For details, see Configuring
Physical Clock in the Feature Description.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.404 SYSLOG_COMM_FAIL
Description
Failed communication between an NE and the syslog server. This alarm is generated when the
session or the connection between an NE and the syslog server is abnormal.
Attribute
Parameters
Name Meaning
Parameter 5 Indicates the type of the fault that causes the alarm. 0x0a indicates that
the connection fails. 0x02 indicates that the session is abnormal.
Possible Causes
In TCP mode, the connection between an NE and the syslog server or the session between
servers is abnormal.
Procedure
Step 1 Check whether the board is a board returned for repair. If it is, there is no need to handle the
alarm.
Step 2 Select the Start Syslog Service check box.
----End
Related Information
None
4.405 SYSPARA_CFDB_NOSAME
Description
Inconsistency between the data in the system parameter area and the CF card. The system
checks the consistency between the data on the system control board and the CF card. If they
are inconsistent, the system does not back up the data but generates this alarm. If they are
consistent, the system backs up the data.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The data on the system control board is inconsistent with that on the CF card upon the first
backup.
Procedure
Step 1 Wait for the next backup period so that the NE database automatically backs up data to the CF
card and the alarm is cleared.
----End
Related Information
None
4.406 T_LOSEX
Description
The T_LOSEX is an alarm indicating a signal loss in the service bus of the backplane. This
alarm is generated when the board detects that the service bus of the backplane is in the LOS
state.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Name Meaning
Parameter 2, Each bit indicates status of a backplane bus. If the value of bit[0] is 1,
Parameter 3 the first bus is faulty.
Possible Causes
l The service board is installed incorrectly.
l The cross-connect board is installed incorrectly.
l The clock source for the active and standby cross-connect boards is faulty or has poor
quality.
Procedure
Step 1 Query the alarm on the NMS and determine the board reporting the alarm.
Step 2 Verify that the board reporting the alarm is installed properly. Then, check whether the alarm
is cleared. If the alarm persists, go to the next step.
Step 3 Verify that the cross-connect board is installed properly. Then, check whether the alarm is
cleared. If the alarm persists, go to the next step.
Step 4 Replace the cross-connect board. Then, check whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.407 T_SLIP
Description
Frame slipping occurs at the transmit end. This alarm is generated when the phase deviation
occurs on the transmitted service frames of the board.
Attribute
Parameters
None
Possible Causes
The clock signals are not synchronous.
Procedure
Step 1 Perform a cold reset on the faulty board on the U2000.
----End
Related Information
None
4.408 TEM_HA
Description
Laser temperature being too high. This alarm is generated when the laser temperature is
higher than the upper laser temperature threshold.
Attribute
Parameters
None
Possible Causes
l The working temperature of the board is excessively high.
l The laser is faulty.
l The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature and ventilation of the equipment room. If the board
ambient temperature is excessively high, cool the equipment room with cooling devices, such
as an air conditioner.
----End
Related Information
None
4.409 TEM_LA
Description
Laser temperature being too low. This alarm is generated when the laser temperature is lower
than the lower threshold of the laser temperature.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The working temperature of the board is excessively low.
Procedure
Step 1 Check the board ambient temperature. If it is excessively low, increase it.
----End
Related Information
None
4.410 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that a board is being tested.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
A user has issued a command for the board to switch to the test state.
Procedure
Step 1 Query the alarm on the NMS and determine the board reporting the alarm.
Step 2 The alarm is automatically cleared after a command is issued to end the test. However, the
system is affected. It is advised to perform a cold reset on the board to prevent the impact on
the system.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.411 THUNDERALM
Description
Lightning protection circuit failure.
The alarm is generated when the PIU board detects a lightning protection circuit failure on the
PIU board.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Parameter Description
Parameter 1 Indicates the board that reports the alarm. For example,
The value 0x01 indicates the PIU1 board.
The value 0x02 indicates the PIU2 board.
Possible Causes
l The equipment is attacked by a strong lighting stroke (the common mode current is
larger than 5000 A and the differential mode current is larger than 3000 A). As a result,
the lightning protection component on the PIU board is invalid and the circuit is broken
during the automatic protection of the fuse. Therefore, the PIU detects the failure and
reports this alarm.
l The board hardware is faulty.
Procedure
Step 1 Replace the faulty PIU board.
----End
Related Information
In the stormy weather, intensive electromagnetic fields form in the air. To protect the
equipment against the lightning stroke, the equipment must be grounded during installation.
Related Cases:
l MC-A99 The PMU Reports the THUNDERALM Alarm
4.412 TIME_LOCK_FAIL
Description
Time lock failure alarm. When the time of an NE is synchronized from the upstream NE, the
time lock status is locking. When the time of an NE is not locked, this alarm is reported to
remind the user of the unlock status of the NE time.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 subrack where the clock board is located.
Parameter 2 Indicates the ID 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.
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 sequence number of the
external clock.
l 0x02: first external clock
l 0x04: second external clock
Possible Causes
There is an excessive step change in the time stamp of the NE. As a result, the NE fails to
trace the upstream time or clock source.
Procedure
Step 1 On the NMS, check whether the NE reports the 4.45 CLK_LOCK_FAIL or 4.414
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 the upstream NE is adjusting time. If the upstream NE adjusts time to a great
extent, the digital signal processor (DSP) on the local NE automatically performs adjustment
for a period. When the accumulated offset adjustment is less than 2610 ns within 96
consecutive seconds of the detection period, the alarm will be automatically cleared.
----End
Related Information
None
4.413 TIME_LOS
Description
The TIME_LOS is an alarm indicating the loss of the time source level. This alarm is
generated when the time source state does not exist after the precision time function is
enabled.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameter 1 Indicates the ID of the subrack where the clock board is located.
Parameter 2 Indicates the ID of the slot in the subrack where the switched clock source is
located.
Parameter 4 Indicates the number of the port in the subrack where the switched clock
source is located.
Possible Causes
The possible causes of the TIME_LOS alarm are as follows:
l Cause 1: There are fiber failures or misconnections.
l Cause 2: The service board is faulty.
l Cause 3: The clock board is faulty.
Procedure
l Cause 1: There are fiber failures or misconnections.
a. Check the fiber connections. Check whether there are optical port alarms, such as
R_LOS and R_LOF. If there are optical port alarms, clear the alarms first.
l Cause 2: The service board is faulty.
a. If the alarm persists, perform a cold reset on the related service board, and then
check whether the alarm is cleared. For details, see "Performing a Cold Reset of a
Board" in the Supporting Tasks.
b. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
l Cause 3: The clock is faulty.
a. If the alarm persists, perform a cold reset on the clock board, and then check
whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board"
in the Supporting Tasks.
b. If the alarm persists, replace the clock board. For details, see "Replacing the Clock
Board" in the Parts Replacement.
----End
Related Information
For details, see "IEEE 1588v2" in the Feature Description.
4.414 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the time enters the non-trace
mode. The precision time of the board is in the non-trace mode. This alarm is generated when
the board traces the internal source after the precision time function is enabled.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 when the IEEE 1588v2 port is enabled or an external
time input port is configured.
l 0x01: indicates that the frequency is in the trace mode.
l 0x02: indicates that the frequency is in the non-trace mode.
Possible Causes
The possible causes of the TIME_NO_TRACE_MODE alarm are as follows:
l Cause 1: The priority table is not configured.
l Cause 2: There are fiber failures or misconnections.
l Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
l Cause 4: The clock board is faulty.
Procedure
l Cause 1: The priority table is not configured.
a. Query the current priority table of the system. If there is only the internal clock
source in the priority table, set the clock source priority table to include other
available clock sources. After the setting, the alarm is automatically cleared. For
details, see "Configuring a IEEE 1588v2 Clock" in the Feature Description.
l Cause 2: There are fiber failures or misconnections.
a. Check the fiber connections. Check whether there are optical port alarms, such as
R_LOS and R_LOF. If there are optical port alarms, clear the alarms first.
l Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
a. If the alarm persists, check whether the attributes of the packets at the upstream NE
are configured correctly on the U2000. If any error is found, modify the
configuration. For details, see "Configuring a IEEE 1588v2 Clock" in the Feature
Description.
l Cause 4: The clock board is faulty.
a. If the alarm persists, perform a cold reset on the clock board, and then check
whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board"
in the Supporting Tasks.
b. If the alarm persists, replace the clock board. For details, see "Replacing the Clock
Board" in the Parts Replacement.
----End
Related Information
For details, see "IEEE 1588v2" in the Feature Description.
4.415 TR_LOC
Description
The TR_LOC is an alarm indicating a transmit reference clock loss.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Parameter 1 l 0x01: indicates that the transmit clock fails on the clock board with a
smaller slot ID.
l 0x02: indicates that the transmit clock fails on the clock board with a
greater slot ID.
l 0x03: indicates that the transmit clock fails on the active and standby clock
boards.
If the slot ID contains two bytes, the options for parameter 1 are as follows:
l bit[0]: indicates that the clock is lost on the cross-connect board with a
smaller slot ID.
l bit[1]: indicates that the frame header is lost on the cross-connect board
with a smaller slot ID.
l bit[2]: indicates that the cross-connect board with a smaller slot ID fails.
l bit[3]: indicates that the clock is lost on the cross-connect board with a
greater slot ID.
l bit[4]: indicates that the frame header is lost on the cross-connect board
with a greater slot ID.
l bit[5]: indicates that the cross-connect board with a greater slot ID fails.
Parameter 2 l 0x01: indicates that the clock is lost on the cross-connect board with a
smaller slot ID.
l 0x02: indicates that the frame header is lost on the cross-connect board
with a smaller slot ID.
l 0x04: indicates that the bus specifying the cross-connect board status is
faulty on the cross-connect board with a smaller slot ID.
l 0x08: indicates that the clock is lost on the cross-connect board with a
greater slot ID.
l 0x10: indicates that the frame header is lost on the cross-connect board
with a greater slot ID.
l 0x20: indicates that the bus specifying the cross-connect board status is
faulty on the cross-connect board with a greater slot ID.
Possible Causes
l The clock bus on the cross-connect board is faulty.
l The clock board is not installed or is faulty.
l The local board has hardware faults.
Procedure
Step 1 Verify that the clock board is installed. Then, go to the next step.
Step 2 Check clock-board-related alarms and determine the working status of the clock board.
l If the clock board reports an alarm, clear the alarm first.
l If the clock board does not report an alarm, the board that reports the TR_LOC alarm is
faulty. Perform a cold reset on the board or replace the board.
Step 3 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.416 TU_AIS_VC3
Description
The TU_AIS_VC3 is an alarm indicating an alarm indication signal (AIS) for a lower order
VC-3 TU channel. This alarm is generated when the board finds that signals in the TU
channel are all "1"s.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Severer alarms, such as R_LOS, R_LOF, or AU_AIS, occur in the system.
l The cross-connect board is faulty.
l The peer related channel is faulty.
Procedure
Step 1 On the NMS, check for severer alarms, such as R_LOS, R_LOF, HP_SLM, and AU_AIS.
Clear these alarms first and check whether the TU_AIS_VC3 alarm is cleared.
Step 2 Cold reset the alarm-reporting board and check whether the alarm is cleared. If the alarm
persists, go to the next step.
NOTICE
If services on the board are not protected, cold resetting the board interrupts services.
Step 3 Replace the alarm-reporting board and check whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 4 Check whether the cross-connect board is faulty. If yes, replace the cross-connect board.
Then, check whether the alarm is cleared.
Step 5 Check whether the peer board is faulty. If yes, replace the faulty board. Then, check whether
the alarm is cleared.
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.417 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating a pointer loss in the lower order VC-3 TU channel.
This alarm is generated when a board detects that the TU-PTR value is invalid or NDF
reverses in eight consecutive frames.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Severer alarms, such as R_LOS, R_LOF, or AU_AIS, occur in the system.
Procedure
Step 1 On the NMS, check for severer alarms, such as R_LOS, R_LOF, and AU_AIS. Clear these
alarms first and check whether the TU_LOP_VC3 alarm is cleared.
Step 2 Cold reset the alarm-reporting board and check whether the alarm is cleared. If the alarm
persists, go to the next step.
NOTICE
If services on the board are not protected, cold resetting the board interrupts services.
Step 3 Replace the alarm-reporting board and check whether the alarm is cleared. If the alarm
persists, go to the next step.
Step 4 Check whether the cross-connect board is faulty. If yes, replace the cross-connect board.
Then, check whether the alarm is cleared.
Step 5 Check whether the peer board is faulty. If yes, replace the faulty board. Then, check whether
the alarm is cleared.
----End
Related Information
None.
4.418 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED alarm indicates the degradation of a tunnel protection
group. This alarm is generated when one tunnel of a tunnel APS group becomes abnormal and
the usability of the protection group is impaired. The alarm is cleared if either of the following
conditions is met:
l After the protection tunnel recovers, both the working and protection tunnels are
available.
l Both the working and protection tunnels are unavailable.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The possible cause of the TUNNEL_APS_DEGRADED alarm is as follows:
Cause 1: One tunnel of a tunnel APS group becomes abnormal.
Procedure
Step 1 Cause 1: One tunnel of a tunnel APS group becomes abnormal.
1. In APS Protection Management, determine the abnormal tunnel based on the
information about the APS protection group.
2. Check whether the protection tunnel reports any alarm such as
MPLS_TUNNEL_LOCV. If yes, clear the alarm. Then check whether the
TUNNEL_APS_DEGRADED alarm is cleared. If the alarm persists, go to the next step.
3. Check whether the port that corresponds to the protection tunnel is disabled. If yes,
enable the port. If the alarm persists, go to the next step.
4. Check for fiber faults at the corresponding port, such as loose or incorrect fiber
connections, or contaminated fiber connectors. Ensure that fiber faults do not exist.
Then, check whether the alarm is cleared.
5. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.419 TUNNEL_APS_OUTAGE
Description
The TUNNEL_APS_OUTAGE alarm indicates that the tunnel APS protection group fails.
When both the working and protection tunnels in an APS protection group fail, the APS
protection group fails and the alarm is reported. The alarm is cleared after either the working
or protection tunnel is restored.
Attribute
Parameters
None
Possible Causes
The working and protection tunnels in the APS protection group are unavailable.
Procedure
Step 1 Check alarm information on the NMS to locate the APS protection group that generates the
alarm.
Step 2 Determine the working and protection tunnels based on the information about the APS
protection group.
Step 3 Check whether the working and the protection tunnels report any alarm such as
MPLS_TUNNEL_LOCV. If yes, clear the alarm. Then, check whether the
TUNNEL_APS_OUTAGE alarm is cleared. If the alarm persists, go to the next step.
Step 4 Check whether the ports on the working and protection tunnels are disabled. If yes, enable the
ports. If the alarm persists, go to the next step.
Step 5 Check whether the fiber connections to the ports on the working and protection tunnels are
incorrect, whether the fiber connections are loose, and whether optical connectors are
contaminated. Rectify the fiber connections and check whether the alarm is cleared.
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.420 VCAT_LOA
See the alarm page according to the type of the board that reports the alarm.
Boards other than the SF64, SF64A, SFD64, 4.420.2 VCAT_LOA (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, EGSH or EAS2
Description
The VCAT_LOA is an alarm indicating that the delay of a multiframe times out. This alarm is
reported when the delay between the timeslots bound with a VCTRUNK port exceeds the
acceptable time of the virtual concatenation.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The actual SDH network delay exceeds the limit of the virtual concatenation delay
compensation.
Procedure
Step 1 View the alarm on the NMS and determine the VCTRUNK port ID of the alarm-reporting
board according parameters 2 and 3.
Step 2 Reconfigure the timeslots of the VCTRUNK port so that they traverse the same fiber. If they
need to traverse different fibers, ensure that the distance difference of the fibers is the
smallest.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
ITU-T G.709
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
The actual SDH network delay exceeds the limit of the virtual concatenation delay
compensation.
Procedure
Step 1 View the alarm on the NMS and determine the VCTRUNK port ID of the alarm-reporting
board according parameters 2 and 3.
Step 2 Reconfigure the timeslots of the VCTRUNK port so that they traverse the same fiber. If they
need to traverse different fibers, ensure that the distance difference of the fibers is the
smallest.
----End
Related Information
ITU-T G.709
4.421 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating a virtual concatenation multiframe loss in the
VC-3 channel. This alarm is generated when the system detects that the multiframe indicator
(MFI) field is incorrect in the H4 byte of the VC-3 timeslot.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Bit error alarms, such as B3_EXC and B3_SD, occur on the line.
l The virtual concatenation delay times out.
l The MFI field in the K4 byte transmitted by the peer end is incorrect.
Procedure
Step 1 Query the alarm on the NMS and determine the board that reports the VCAT_LOM_VC3
alarm.
Step 2 On the NMS, check whether bit error alarms, such as B3_EXC_VC3 and B3_SD_VC3, are
reported on the board. If yes, clear them first and check whether the VCAT_LOM_VC3 alarm
is cleared.
Step 3 On the NMS, check whether the VCAT_LOA alarm is reported on the board. If yes, the
virtual concatenation delay times out. See the method of handling the VCAT_LOA alarm to
clear it. Then, check whether the VCAT_LOM_VC3 alarm is cleared.
Step 4 If the alarm persists, check whether the board is faulty. If yes, replace the faulty board. Then,
check whether the alarm is cleared.
Step 5 If the alarm persists, the MFI domain transmitted from the peer SDH NE is incorrect. Replace
the peer related board and check whether the alarm is cleared.
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.422 VCAT_LOM_VC4
Description
The VCAT_LOM_VC4 is an alarm indicating a virtual concatenation multiframe loss in the
VC-4 channel. This alarm is generated when the system detects that the multiframe indicator
(MFI) field is incorrect in the H4 byte of the VC-4 timeslot.
Attribute
Alarm Severity Alarm Type
Parameters
None.
Possible Causes
l Bit error alarms, such as BIP_EXC and BIP_SD, occur on the line.
l The virtual concatenation delay times out.
l The MFI field in the K4 byte transmitted by the peer end is incorrect.
Procedure
Step 1 Query the alarm on the NMS and determine the board that reports the VCAT_LOM_VC4
alarm.
Step 2 On the NMS, check whether bit error alarms, such as BIP_EXC and BIP_SD, are reported on
the board. If yes, clear them first and check whether the VCAT_LOM_VC4 alarm is cleared.
Step 3 On the NMS, check whether the VCAT_LOA alarm is reported on the board. If yes, the
virtual concatenation delay times out. See the method of handling the VCAT_LOA alarm to
clear it. Then, check whether the VCAT_LOM_VC4 alarm is cleared.
Step 4 If the alarm persists, check whether the board is faulty. If yes, replace the faulty board. Then,
check whether the alarm is cleared.
Step 5 If the alarm persists, the MFI domain transmitted from the peer SDH NE is incorrect. Replace
the peer related board and check whether the alarm is cleared.
Step 6 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.423 VCTRUNK_NO_FLOW
Description
VCTRUNK port traffic alarm. This alarm is generated when there is no traffic at a
VCTRUNK port.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 at a VCTRUNK port is interrupted.
For example, 0x00 indicates the receive direction and 0x01 indicates the
transmit direction.
Possible Causes
l No services are configured at the local end.
l The local services are abnormal or no packets are transmitted from the local port.
l The peer end is abnormal or no packets are transmitted to the local port.
Procedure
Step 1 Check whether services are configured at the VCTRUNK port where the alarm is generated.
Step 2 Query alarm parameters on the U2000 and determine the traffic interruption direction. If
traffic is interrupted in the transmit direction, check whether services at the local NE are
normal. If the services at the local NE are abnormal, handle the alarm with reference to the
procedure for handling other alarms.
Step 3 If traffic is interrupted in the receive direction, check whether the cross-connection
configurations of the local site are correct and whether the local-site cross-connect boards,
line boards, and fiber are normal. Then, handle the alarm with reference to the corresponding
alarm handling procedure.
----End
Related Information
None
4.424 VLAN_SNCP_PS
Description
VLAN SNCP protection switching alarm. This alarm is generated when the working or
protection channel of the protection group is faulty or the user issues an external switching
command.
Attribute
Alarm Severity Alarm Type
Parameters
Parameter Description
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated.
Possible Causes
l The user issues an external switching command such as forced switching, manual
switching or locked switching.
l The services of the working channel or the protection channel of the VLAN SNCP group
are faulty.
l The switching is in WTR State. After WTR Times, the alarm clears.
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is
forced switching, manual switching or locked switching, check whether the external switching
operation is necessary.
1. If the external switching operation is necessary, ignore the alarm.
2. If the external switching operation is unnecessary, issue a clear switching command to
clear the external switching.
Step 2 If the alarm is generated due to the fault of the working channel or the protection channel of
the protection group, perform the following operations:
1. Query whether the related boards for configuring the protection group have the alarms,
for example, R_LOF, R_LOS, R_OOF, OTUk_LOF, OTUk_LOM, OTUk_AIS. If yes,
clear the alarm to restore the services in the working channel or the protection channel.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If
it is, after WTR Times the working channel will automatically switch to the working
channel. The alarm will be cleared. If the attribute is Non-Revertive, change it to
Revertive. The alarm will be cleared after WTR Times.
Step 3 On the U2000, query the switching state of the protection group. If the switching is in WTR
State, this alarm requires no handling and will be cleared after WTR Times.
----End
Related Information
VLAN SNCP protection utilizes the dual fed and selective receiving function of the L2
module to protect the upstream convergence services. The service granularity of protection
switching is services at client-side ports, which are identified as VLAN. For details, see
"VLAN SNCP Protection" in the Feature Description.
4.425 VOADATA_MIS
Description
Mismatch of attenuation attributes. This alarm is generated when the preset attenuation value
falls beyond the adjustable attenuation range of the board.
Attribute
Parameters
None
Possible Causes
Cause 1: Replacing an attenuation board or optical module makes the stored attenuation value
issued by the NE software fall beyond the adjustable attenuation range of the new board.
Procedure
l Cause 1: Replacing an attenuation board or optical module makes the stored attenuation
value issued by the NE software fall beyond the adjustable attenuation range of the new
board.
a. Query the adjustable range of the current actual attenuation. Reset a valid
attenuation value for the optical port channel of the board based on the queried
adjustable range.
----End
Related Information
None
4.426 W_R_FAIL
Description
Writing or reading chip register failed. This alarm is generated when the read value and the
written value of the register are not consistent.
Attribute
Parameters
Parameter Description
Parameter 1 Indicates the IDs of the board register. For example, 0x01-0x09 indicates the
IDs of the faulty chips that are of different types.
Possible Causes
The board is faulty.
Procedure
Step 1 Perform a warm reset on the faulty board on the U2000.
Step 2 If the alarm persists, replace the faulty board. Refer to Replace the board.
----End
Related Information
None
4.427 WAVE_ADD_ABN
Description
APE detecting abnormal wavelength adding.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
The spectrum analysis module of the detection board obtains the actually received
wavelengths on each optical port and compares the scanned wavelengths obtained during the
defining. If a new wavelength is detected, this alarm is generated.
Procedure
Step 1 The U2000 instructs the user to re-define the APE standard optical power curve.
----End
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.428 WAVE_DROP_ABN
Description
APE detecting abnormal wavelength dropping.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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
Possible Causes
The spectrum analysis module of the detection board obtains the actually received
wavelengths on each optical port and compares the scanned wavelengths during the defining.
If a wavelength is not received, this alarm is generated.
Procedure
Step 1 The U2000 instructs the user to re-define the APE standard optical power curve.
----End
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.429 WAVEDATA_MIS
Description
Mismatch of wavelength or band attributes. This alarm is generated when the configured logic
wavelength or band differs with the actual wavelength or band.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
l Cause 2: The board is faulty.
Procedure
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
a. Query the actual wavelength of the unit and the logic wavelength stored on the
U2000. If these two wavelengths differ, reconfigure the operating wavelength of the
corresponding optical port to make it the same as the fixed wavelength of the
optical module on the board.
l Cause 2: The board is faulty.
a. If the alarm persists, Replace the board. or optical module with another one whose
wavelength is the same as that stored in the NE software.
----End
Related Information
None
4.430 WAVELEN_OVER
Description
Wavelength crossing the threshold. This alarm is generated when the wavelength drift of the
OTU board exceeds the threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The wavelength drift of the corresponding channel of the OTU board exceeds the upper
or lower threshold.
l The wavelength locking is mis-adjusted because the logical fiber connection is
inconsistent with the physical fiber connection.
l The wavelength locking module on the WMU board or a module on the OTU board is
malfunctioning.
Procedure
Step 1 Check whether the wavelength of the optical port connecting to the OTU board monitored by
the wavelength monitoring board is within the permitted range. If it is not, the OTU board
enables the wavelength locking function to adjust the monitored wavelength. When the
monitored wavelength restores to a value within the permitted range, this alarm is cleared.
Step 2 If the alarm persists, check whether the logical fiber connections are consistent with the
physical fiber connections. If they are not, modify the logical fiber connections so that the
logical fiber connections are consistent with the physical fiber connections. Refer to Checking
Logical Fibers.
Step 3 If the alarm persists, perform a cold reset on the OTU board.
NOTE
The alarm status can be updated only after an automatic or manual wavelength locking adjustment is
performed and the alarm is cleared only after the fault is rectified.
----End
Related Information
None
4.431 XC_UNSWITCH
Description
Cross-connect matrix of the board being not switched.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
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 subrack ID of the board whose cross-connect matrix is not
switched.
Parameter 2 Indicates the slot ID of the board whose cross-connect matrix is not switched.
Possible Causes
The possible causes of the XC_UNSWITCH alarm are as follows:
l The cross-connect board or the line board fails to respond to the cross-connect matrix
switching command issued by the NE software, and as a result is not updated with the
cross-connect matrix configured by the NE software.
l The board is in the BIOS state, and as a result cannot be updated with the cross-connect
matrix configured by the NE software.
Procedure
Step 1 Check whether the board that reports the alarm has communication alarms. Clear the
communication alarms if such alarms are found and check whether the XC_UNSWITCH
alarm is cleared.
Step 2 If the alarm persists, perform a warm reset on the board and check whether the
XC_UNSWITCH alarm is still present.
Step 3 If the alarm persists, contact Huawei engineers to re-load the board software.
Step 4 If the alarm persists, Replace the board. that reports the alarm.
----End
Related Information
None
This topic lists the names, description and relevant boards of the performance event in
alphabetical order and lists the performance event of every board.
5.1 Product Performance Event List
Lists the different types of performance event.
5.2 Board Performance Event List
This topic lists the performance events of each board.
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
RSOOF RS Out-of-Frame
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Name Description
Receive Transmit
direction direction
Board
Client WDM or
side backplane side
Transmit Receive
direction direction
FCS and Alignment Errors (ETHCRCALI) The total number of packets received that
had a length (excluding framing bits, but
including FCS octets) of between 64 and
1518 octets, inclusive, but had either a bad
Frame Check Sequence (FCS) with an
integral number of octets (FCS Error) or a
bad FCS with a non-integral number of
octets (Alignment Error).
Name Description
Undersize Packets Received (ETHUNDER) The total number of packets received that
were less than 64 octets long (excluding
framing bits, but including FCS octets) and
were otherwise well formed.
Oversize Packets Received (ETHOVER) The total number of packets received that
were longer than 1518 octets (excluding
framing bits, but including FCS octets) and
were otherwise well formed.
Packets Received, 64 Octets in Length The total number of packets (including bad
(RXPKT64) packets) received that were 64 octets in
length (excluding framing bits but including
FCS octets).
Packets Received, 65~127 Octets in Length The total number of packets (including bad
(RXPKT65) packets) received that were between 65 and
127 octets in length inclusive (excluding
framing bits but including FCS octets).
Packets Received, 128~255 Octets in The total number of packets (including bad
Length (RXPKT128) packets) received that were between 128
and 255 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Received, 256~511 Octets in The total number of packets (including bad
Length (RXPKT256) packets) received that were between 256
and 511 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Received, 512~1023 Octets in The total number of packets (including bad
Length (RXPKT512) packets) received that were between 512
and 1023 octets in length inclusive
(excluding framing bits but including FCS
octets).
Name Description
Packets Received, 1024~1518 Octets in The total number of packets (including bad
Length (RXPKT1024) packets) received that were between 1024
and 1518 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Received, 1519~MTU Octets in The total number of packets (including bad
Length (RXPKT1519) packets) received that were between 1519
and MTU octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Received and Transmitted, 64 The total number of packets (including bad
Octets in Length (PKT64) packets) received and transmitted that were
64 octets in length (excluding framing bits
but including FCS octets).
Packets Received and Transmitted, 65~127 The total number of packets (including bad
Octets in Length (PKT65) packets) received and transmitted that were
between 65 and 127 octets in length
inclusive (excluding framing bits but
including FCS octets).
Packets Received and Transmitted, 128~255 The total number of packets (including bad
Octets in Length (PKT128) packets) received and transmitted that were
between 128 and 255 octets in length
inclusive (excluding framing bits but
including FCS octets).
Packets Received and Transmitted, 256~511 The total number of packets (including bad
Octets in Length (PKT256) packets) received and transmitted that were
between 256 and 511 octets in length
inclusive (excluding framing bits but
including FCS octets).
Packets Received and Transmitted, The total number of packets (including bad
512~1023 Octets in Length (PKT512) packets) received and transmitted that were
between 512 and 1023 octets in length
inclusive (excluding framing bits but
including FCS octets).
Packets Received and Transmitted, The total number of packets (including bad
1024~1518 Octets in Length (PKT1024) packets) received and transmitted that were
between 1024 and 1518 octets in length
inclusive (excluding framing bits but
including FCS octets).
Packets Received and Transmitted, The total number of packets (including bad
1519~MTU Octets in Length (PKT1519) packets) received and transmitted that were
between 1519 and MTU octets in length
inclusive (excluding framing bits but
including FCS octets).
Name Description
Good Full Frame Octets Transmitted The total number of transmitted octets of
(TXFULLBGOOD) good packets (including framing bits and
FCS octets).
Good Full Frame Octets Received The total number of received octets of good
(RXFULLBGOOD) packets (including framing bits and FCS
octets).
Good Full Frame Speed Transmitted The rate of transmitted octets of good
(TXGOODFULLFRAMESPEED) packets (including framing bits and FCS
octets).
Good Full Frame Speed Received The rate of received octets of good packets
(RXGOODFULLFRAMESPEED) (including framing bits and FCS octets).
Full Frame Speed Transmitted The rate of octets of data (including those in
(VCG_TXSPEED) bad packets) transmitted on the network
(excluding framing bits but including FCS
octets).
Full Frame Speed Received The rate of octets of data (including those in
(VCG_RXSPEED) bad packets) received on the network
(excluding framing bits but including FCS
octets).
Packets Transmitted, 64 Octets in Length The total number of packets (including bad
(TXPKT64) packets) transmitted that were 64 octets in
length (excluding framing bits but including
FCS octets).
Packets Transmitted, 65~127 Octets in The total number of packets (including bad
Length (TXPKT65) packets) transmitted that were between 65
and 127 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Transmitted, 128~255 Octets in The total number of packets (including bad
Length (TXPKT128) packets) transmitted that were between 128
and 255 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Transmitted, 256~511 Octets in The total number of packets (including bad
Length (TXPKT256) packets) transmitted that were between 256
and 511 octets in length inclusive
(excluding framing bits but including FCS
octets).
Name Description
Packets Transmitted, 512~1023 Octets in The total number of packets (including bad
Length (TXPKT512) packets) transmitted that were between 512
and 1023 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Transmitted, 1024~1518 Octets in The total number of packets (including bad
Length (TXPKT1024) packets) transmitted that were between 1024
and 1518 octets in length inclusive
(excluding framing bits but including FCS
octets).
Packets Transmitted, 1519~MTU Octets in The total number of packets (including bad
Length (TXPKT1519) packets) transmitted that were between 1519
and MTU octets in length inclusive
(excluding framing bits but including FCS
octets).
Unicast Packets Received (RXUNICAST) The total number of good packets received
that were directed to a unicast address.
Good Octets Received (RXBGOOD) The total number of octets of good packets
received on the network (excluding framing
bits but including FCS octets).
Name Description
Good Octets Transmitted (TXBGOOD) The total number of octets of good packets
transmitted on the network (excluding
framing bits but including FCS octets).
Bad Octets Received (RXBBAD) The total number of octets of bad packets
received on the network (excluding framing
bits but including FCS octets).
Bad Octets Transmitted (TXBBAD) The total number of octets of bad packets
transmitted on the network (excluding
framing bits but including FCS octets).
Drop Events at Transmission Direction The total number of events in which packets
(TXETHDROP) were dropped by the probe due to lack of
resources at transmission direction. Note
that this number is not necessarily the
number of packets dropped; it is just the
number of times this condition has been
detected.
Name Description
Good full-frame bytes received The total number of received good packets,
(RXFULLBGOOD) including framing bits (20 bytes) and FCS
bytes.
Rate of good full-frame bytes received The rate of received good packets, including
(RXGOODFULLFRAMESPEED) framing bits (20 bytes) and FCS bytes.
Rate of good full-frame bytes transmitted The rate of transmitted good packets,
(TXGOODFULLFRAMESPEED) including framing bits (20 bytes) and FCS
bytes.
Count of lost packets of the PW service Number of data packets transmitted at the
(MPLS_PW_FL) source – number of data packets received
at the sink. This difference is detected by
the OAM mechanism.
Bits per second transmitted on PW Bits per second transmitted at the specified
(PW_TX_BPS) PW, that is, number of actually transmitted
bytes x 8/time unit.
Bits per second received on PW Bits per second received at the specified
(PW_RX_BPS) PW, that is, number of actually received
bytes x 8/time unit.
Packets per second received on Packets per second received at the specified
PW(PW_RX_PPS) PW, that is, number of actually received
packets/time unit.
Name Description
Bits per second transmitted on tunnel Bits per second transmitted on tunnel of the
(TUNNEL_TX_BPS) specified service, that is, number of actually
transmitted bytes x 8/time unit.
Bits per second received on Bits per second received on tunnel of the
tunnel(TUNNEL_RX_BPS) specified service, that is, number of actually
received bytes x 8/time unit.
Packets per second received on Packets per second received on tunnel of the
tunnel(TUNNEL_RX_PPS) specified service, that is, number of actually
received packets/time unit.
Count of lost packets of the tunnel service Number of data packets transmitted at the
(MPLS_TUNNEL_FL) source - number of data packets received at
the sink. This difference is detected by the
OAM mechanism.
Name Description
Delay variation of the tunnel service Difference in two frame delay tests.
(MPLS_TUNNEL_FDV)
E_Line service delay(ETH_CFM_FD) Frame delay = Time when the source MEP
sends a request packet - Time when the
source MEP receives the response packet.
Bits per second transmitted on the reverse Bits per second of transmitted on the reverse
tunnel (TUNNEL_REVERSE_TX_BPS) tunnel, that is, number of actually
transmitted bytes x 8/time unit.
Packets per second transmitted on the Packets per second of transmitted on the
reverse tunnel reverse tunnel, that is, number of actually
(TUNNEL_REVERSE_TX_PPS) transmitted packets/time unit.
Bits per second received on the reverse Bits per second of received on the reverse
tunnel (TUNNEL_REVERSE_RX_BPS) tunnel, that is, number of actually received
bytes x 8/time unit.
Name Description
Packets per second received on the reverse Packets per second of received on the
tunnel (TUNNEL_REVERSE_RX_PPS) reverse tunnel, that is, number of actually
received packets/time unit.
Bytes matching flow classification The number of bytes that match the flow
(QOS_STRM_MATCHBYTES) classification.
Packets matching flow classification The number of packets that match the flow
(QOS_STRM_MATCHPKTS) classification.
Bits per second received match some Bits per second = Number of received bytes
VLAN ID at the specified V-UNI of the x 8/Monitoring Period
specified service (VLAN_RX_BPS)
Packets per second received match some Packets per second = Number of received
VLAN ID at the specified V-UNI of the packets/Monitoring Period
specified service (VLAN_RX_PPS)
Bits per second transmitted match some Bits per second = Number of transmitted
VLAN ID at the specified V-UNI of the bytes x 8/Monitoring Period
specified service (VLAN_TX_BPS)
Packets per second transmitted match some Packets per second = Number of transmitted
VLAN ID at the specified V-UNI of the packets/Monitoring Period
specified service (VLAN_TX_PPS)
Bits per second received (RXBPS) Received bits per second = (Number of
received bytes x 8/Monitoring Period)
Bits per second transmitted (TXBPS) Transmitted bits per second = (Number of
transmitted bytes x 8/Monitoring Period)
Packets per second received (RXPPS) Received packets per second = (Number of
received packets/Monitoring Period)
Name Description
Packets per second transmitted (TXPPS) Transmitted packets per second = (Number
of transmitted packets/Monitoring Period)
Description
Description
Description
FEC_AFT_CORER_FLO
AT LSIOPCUR OSC_FEBBE
FEC_AFT_COR_ERAV
R LSIOPMIN OSC_FEES
FEC_BEF_CORER_FLO
AT LSOOPCUR OSC_FESES
FEC_UNCOR_BLOCK_
CNT OSC_BBE OSC_UAS
TN11D40
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
HPFEUAS LSOOPCUR
HPSES LSOOPMAX
Undersize Packets
Broadcast Packets Received Multicast Packets Received Received
TN55EG16
BDTEMPCUR MPLS_PW_SLS RPLCUR
Count of bytes received Rate of good full-frame bytes Packets Received, 256~511
on PW transmitted Octets in Length
Number of reversely
transmitted packets on a Packets Transmitted,
tunnel Packets Transmitted 1519~MTU Octets in Length
Number of reversely
transmitted bytes on a Packets Transmitted, 64 Packets Transmitted,
tunnel Octets in Length 1024~1518 Octets in Length
Number of reversely
received packets on a Packets Transmitted,
tunnel 128~255 Octets in Length Octets Received
Count of bytes
transmitted at V-UNI Control Frames Received
LSBIASMAX VC3CSES
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN54ENQ2
FEC_AFT_CORER_FLOAT ODU1_PM_SES ODU2_TCMn_BIAES
ODU1_PM_FESESR ODU2_TCMn_BBE
ODU1_PM_FEUAS ODU2_TCMn_BBER
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
CRC4BBE CRC4FESES
Count of bytes received Rate of good full-frame bytes Packets Received, 256~511
on PW transmitted Octets in Length
Number of reversely
transmitted packets on a Packets Transmitted,
tunnel Packets Transmitted 1519~MTU Octets in Length
Number of reversely
transmitted bytes on a Packets Transmitted, 64 Packets Transmitted,
tunnel Octets in Length 1024~1518 Octets in Length
Number of reversely
received packets on a Packets Transmitted,
tunnel 128~255 Octets in Length Octets Received
Count of bytes
transmitted at V-UNI Control Frames Received
Count of bytes received Rate of good full-frame bytes Packets Received, 256~511
on PW transmitted Octets in Length
Number of reversely
transmitted packets on a Packets Transmitted,
tunnel Packets Transmitted 1519~MTU Octets in Length
Number of reversely
transmitted bytes on a Packets Transmitted, 64 Packets Transmitted,
tunnel Octets in Length 1024~1518 Octets in Length
Number of reversely
received packets on a Packets Transmitted,
tunnel 128~255 Octets in Length Octets Received
Count of bytes
transmitted at V-UNI Control Frames Received
TN14FIU/TN16FIU
NOTE
TN97FIU does not support reporting board performance event feature.
FEC_AFT_CORER_FLO
AT ODU2_PM_FESESR ODUFLEX_PM_FEBBER
FEC_AFT_COR_ERAV
R ODU2_PM_SES ODUFLEX_PM_FESES
FEC_BEF_CORER_FLO
AT ODU2_PM_SESR ODUFLEX_PM_FESESR
FEC_UNCOR_BLOCK_
CNT ODU2_TCMn_FEBBE ODUFLEX_TCMn_BBER
ODUFLEX_TCMn_FEBBE
LSOOPCUR ODU2_TCMn_FESESR R
VALLEY_OUTPOWER_CU
ODU1_TCMn_ES ODU4_TCMn_BBE R
VALLEY_OUTPOWER_MA
ODU1_TCMn_FEBBE ODU4_TCMn_BBER X
VALLEY_OUTPOWER_MI
ODU1_TCMn_FEBBER ODU4_TCMn_BIAES N
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
TN11HBA
BCVCUR EDTMPMAX SUMOOPMIN
CRC4UAS LSIOPMAX
TN12HSC1
FEC_AFT_CORER_FLO
AT LSIOPCUR OSC_FEBBE
FEC_AFT_COR_ERAV
R LSIOPMIN OSC_FEES
FEC_BEF_CORER_FLO
AT LSOOPCUR OSC_FESES
FEC_UNCOR_BLOCK_
CNT OSC_BBE OSC_UAS
NOTE
TN12ITL and TN97ITL does not support reporting board performance event feature.
ODU5G_PM_BBE ODU5G_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
LSTMPMIN ODU1_TCMn_SES
ODU1_PM_BBE ODU1_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
LSTMPMIN ODU1_TCMn_SES
ODU1_PM_BBE ODU1_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
ODU1_PM_BBE ODU1_TCMn_SESR
ODU1_PM_BBER ODU1_TCMn_UAS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
LSTMPMAX ODU2_TCMn_SES
LSTMPMIN ODU2_TCMn_SESR
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Packets Transmitted(128~255
Alignment Errors Oversize Packets Received Octets in Length)
LSTMPMIN ODU2_TCMn_SES
ODU2_PM_BBE ODU2_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Good Full Frame Octets Good Full Frame Octets Good Full Frame Speed
Received Transmitted Transmitted
Packets Packets
Transmitted(512~1023 Transmitted(1024~1518
Octets in Length) Octets in Length)
LSTMPMIN ODU2_TCMn_SES
ODU2_PM_BBE ODU2_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Good Full Frame Octets Good Full Frame Octets Good Full Frame Speed
Received Transmitted Transmitted
Packets Packets
Transmitted(512~1023 Transmitted(1024~1518
Octets in Length) Octets in Length)
FEC_AFT_COR_ERAV
R ODU1_PM_UAS ODUFLEX_PM_FEES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_BBE ODUFLEX_PM_FESES
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_FEES OTU1_BBE
ODU1_PM_FEUAS ODUFLEX_PM_ES
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
LSOOPMIN ODU2_TCMn_FESESR
LSTMPCUR ODU2_TCMn_FEUAS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Multicast Packets
Drop Events Broadcast Packets Received Received
NOTE
In the GFP-T mode, the TN11LOG board does not support the RMON performance event.
LSTMPCUR ODU2_TCMn_FESESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Multicast Packets
Drop Events Broadcast Packets Received Received
FC_Client_RxOLSPrim_
CLIENT_CRC_ERR Cnt LINKTST_CNT
FC_Client_RxLRRPrim_Cnt FC_Client_TxOLSPrim_
Cnt
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN11LQMD
FCS and Alignment Errors Undersize Packets Received Oversize Packets Received
Oversize Packets
Transmitted
TN12LQMD
Packets Received Broadcast Packets
(1024~1518 Octets in Transmitted
Drop Events Length)
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN11LQMS
FCS and Alignment Errors Undersize Packets Received Oversize Packets Received
Oversize Packets
Transmitted
TN12LQMS
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
ODU1_PM_BBE ODU1_TCMn_SESR
ODU1_PM_BBER RSOFS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
FEC_AFT_CORER_FLO
AT ODU4_TCMn_BIAES PEAK_OUTPOWER_MAX
FEC_AFT_COR_ERAV
R ODU4_TCMn_FEBBE VALLEY_INPOWER_CUR
FEC_BEF_CORER_FLO
AT ODU4_TCMn_FEBBER VALLEY_INPOWER_MAX
FEC_UNCOR_BLOCK_
CNT ODU4_TCMn_SES VALLEY_LSTMP_MAX
VALLEY_OUTPOWER_CU
LSBIASMAX ODU4_TCMn_UAS R
VALLEY_OUTPOWER_MA
LSBIASMIN OTU4_BBE X
VALLEY_OUTPOWER_MI
LSIOPCUR OTU4_BBER N
Packets Received
(1519~MT Octets in
FCS Errors Octets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Broadcast Packets Transmitted Received
Packets Transmitted
(65~127 Octets in Length) Packets Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers
Packets Transmitted
(1518~MT Octets in Packets Received (512~1023
Length) Octets in Length)
PEAK_OUTPOWER_MA
ETH_BBE ODU4_PM_SES X
VALLEY_INPOWER_CU
FEC_AFT_COR_ER ODU4_TCMn_FEBBER R
VALLEY_INPOWER_MA
FEC_AFT_COR_ERAVR ODU4_TCMn_FEES X
VALLEY_INPOWER_MI
FEC_BEF_CORER_FLOAT ODU4_TCMn_FESES N
FEC_UNCOR_BLOCK_CN
T ODU4_TCMn_UAS VALLEY_LSTMP_MIN
VALLEY_OUTPOWER_C
LSBIASCUR OTU4_BBE UR
VALLEY_OUTPOWER_
LSBIASMAX OTU4_BBER MAX
VALLEY_OUTPOWER_
LSBIASMIN OTU4_BIAES MIN
LSCLCCUR OTU4_ES
LSCLCMAX OTU4_FEBBE
TN17LSC
BDTEMPCUR LSCLCMIN OTU4_FEBBER
FEC_AFT_CORER_FLO
AT ODU4_TCMn_FEBBE TDCMIN
FEC_AFT_COR_ERAV
R ODU4_TCMn_FEES VALLEY_INPOWER_MAX
FEC_BEF_CORER_FLO
AT ODU4_TCMn_FESES VALLEY_INPOWER_MIN
FEC_UNCOR_BLOCK_
CNT ODU4_TCMn_UAS VALLEY_LSTMP_MIN
VALLEY_OUTPOWER_CU
LSBIASCUR OTU4_BBE R
VALLEY_OUTPOWER_MA
LSBIASMAX OTU4_BBER X
VALLEY_OUTPOWER_MI
LSBIASMIN OTU4_BIAES N
LSCLCCUR OTU4_ES
LSCLCMAX OTU4_FEBBE
TN15LSC
BDTEMPCUR LSCLCMIN OTU4_FEBBER
FEC_AFT_CORER_FLO
AT ODU4_TCMn_FEBBE TDCMIN
FEC_AFT_COR_ERAV
R ODU4_TCMn_FEES VALLEY_INPOWER_MAX
FEC_BEF_CORER_FLO
AT ODU4_TCMn_FESES VALLEY_INPOWER_MIN
FEC_UNCOR_BLOCK_
CNT ODU4_TCMn_UAS VALLEY_LSTMP_MIN
VALLEY_OUTPOWER_CU
LSBIASCUR OTU4_BBE R
VALLEY_OUTPOWER_MA
LSBIASMAX OTU4_BBER X
VALLEY_OUTPOWER_MI
LSBIASMIN OTU4_BIAES N
LSCLCCUR OTU4_ES
LSCLCMAX OTU4_FEBBE
TN13LSC
BDTEMPCUR LSCLCMIN OTU4_FEBBER
FEC_AFT_CORER_FLO
AT ODU4_TCMn_FEBBE TDCMIN
FEC_AFT_COR_ERAV
R ODU4_TCMn_FEES VALLEY_INPOWER_MAX
FEC_BEF_CORER_FLO
AT ODU4_TCMn_FESES VALLEY_INPOWER_MIN
FEC_UNCOR_BLOCK_
CNT ODU4_TCMn_UAS VALLEY_LSTMP_MIN
VALLEY_OUTPOWER_CU
LSBIASCUR OTU4_BBE R
VALLEY_OUTPOWER_MA
LSBIASMAX OTU4_BBER X
VALLEY_OUTPOWER_MI
LSBIASMIN OTU4_BIAES N
LSCLCCUR OTU4_ES
LSCLCMAX OTU4_FEBBE
TN12LSC
BDTEMPCUR LSOOPCUR OTU4_FEES
FEC_AFT_CORER_FLO
AT ODU4_TCMn_BBER PEAK_OUTPOWER_MIN
FEC_AFT_COR_ERAV
R ODU4_TCMn_ES SUMIOPMAX
FEC_BEF_CORER_FLO
AT ODU4_TCMn_FEBBE SUMIOPMIN
FEC_UNCOR_BLOCK_
CNT ODU4_TCMn_IAES VALLEY_LSBIAS_MIN
VALLEY_OUTPOWER_CU
LSIOPCUR OTU4_ES R
VALLEY_OUTPOWER_MA
LSIOPMAX OTU4_FEBBE X
VALLEY_OUTPOWER_MI
LSIOPMIN OTU4_FEBBER N
Unicast Packets
Pause Frames Transmitted Broadcast Packets Transmitted Received
Packets Transmitted
(65~127 Octets in Length) Packets Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers
Packets Transmitted
(1518~MT Octets in Packets Received (512~1023 Good Packets
Length) Octets in Length) Received
Bad Packets
Good Octets Transmitted Bad Octets Transmitted Transmitted
TN15LSC/TN17LSC
Packets Received
(1519~MT Octets in
FCS Errors Octets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Broadcast Packets Transmitted Received
Packets Transmitted
(65~127 Octets in Length) Packets Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers
Packets Transmitted
(1518~MT Octets in Packets Received (512~1023
Length) Octets in Length)
TN13LSC
Packets Received
(1519~MT Octets in
FCS Errors Octets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Broadcast Packets Transmitted Received
Packets Transmitted
(65~127 Octets in Length) Packets Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers
Packets Transmitted
(1518~MT Octets in Packets Received (512~1023
Length) Octets in Length)
TN12LSC
Packets Received
(1024~1518 Octets in
FCS Errors Octets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Broadcast Packets Transmitted Received
Packets Transmitted
(65~127 Octets in Length) Packets Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers
LSTMPMAX ODU3_TCMn_SES
LSTMPMIN ODU3_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LSTMPCUR ODU3_TCMn_FESESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LSTMPMAX ODU3_TCMn_SES
LSTMPMIN ODU3_TCMn_SESR
TN15LSXL
FEC_AFT_CORER_FLO
AT ODU3_PM_FEBBE OTU3_FEBBER
FEC_AFT_COR_ERAV
R ODU3_PM_FEES OTU3_FESES
FEC_BEF_CORER_FLO
AT ODU3_PM_FESES OTU3_FESESR
FEC_UNCOR_BLOCK_
CNT ODU3_TCMn_BBE DGDAVG
ODU3_PM_ES OTU3_FEBBE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
LSTMPMAX ODU2_TCMn_SES
LSTMPMIN ODU2_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
LSTMPMAX ODU2_TCMn_SES
LSTMPMIN ODU2_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
Packets Received,
1024~1518 Octets in Packets Transmitted,
Undersize Packets Received Length 256~511 Octets in Length
Packets Transmitted,
Broadcast Packets Received Packets Received 512~1023 Octets in Length
Packets Transmitted,
Multicast Packets Received Unicast Packets Received 1024~1518 Octets in Length
Broadcast Packets
Octets Received Transmitted Packets Transmitted
TN13LSX
Packets Received, 64 Octets
Alignment Errors in Length Octets Transmitted
Packets Received,
1024~1518 Octets in Packets Transmitted,
Undersize Packets Received Length 256~511 Octets in Length
Packets Transmitted,
Broadcast Packets Received Packets Received 512~1023 Octets in Length
Packets Transmitted,
Multicast Packets Received Unicast Packets Received 1024~1518 Octets in Length
Broadcast Packets
Octets Received Transmitted Packets Transmitted
TN14LSX
Packets Received,
1024~1518 Octets in Packets Transmitted,
Oversize Packets Received Length 128~255 Octets in Length
Packets Received,
1519~MTU Octets in Packets Transmitted,
Undersize Packets Received Length 256~511 Octets in Length
Packets Transmitted,
Bad Octets Received Packets Received 512~1023 Octets in Length
Packets Transmitted,
Broadcast Packets Received Unicast Packets Received 1024~1518 Octets in Length
Packets Transmitted,
1519~MTU Octets in
Control Frames Received Bad Octets Transmitted Length
Broadcast Packets
Multicast Packets Received Transmitted Packets Transmitted
LSTMPMIN ODU4_TCMn_FESES
TN12LTX
BDTEMPCUR ODU2_PM_SES ODU4_TCMn_SESR
TN15LTX
BDTEMPCUR ODU2_TCMn_FEES ODUFLEX_TCMn_FEBBE
ODUFLEX_TCMn_FEBBE
BDTEMPMAX ODU2_TCMn_FESES R
FEC_AFT_CORER_FLO
AT ODU2_TCMn_UAS ODUFLEX_TCMn_SES
FEC_AFT_COR_ERAV
R ODU4_PM_BBER ODUFLEX_TCMn_UAS
FEC_BEF_CORER_FLO
AT ODU4_PM_ES OTU2_BBE
FEC_UNCOR_BLOCK_
CNT ODU4_PM_FEUAS OTU2_FEES
ODU2_TCMn_FEBBER ODUFLEX_TCMn_ES
TN17LTX
BDTEMPCUR ODU2_TCMn_FEES ODUFLEX_TCMn_FEBBE
ODUFLEX_TCMn_FEBBE
BDTEMPMAX ODU2_TCMn_FESES R
FEC_AFT_CORER_FLO
AT ODU2_TCMn_UAS ODUFLEX_TCMn_SES
FEC_AFT_COR_ERAV
R ODU4_PM_BBER ODUFLEX_TCMn_UAS
FEC_BEF_CORER_FLO
AT ODU4_PM_ES OTU2_BBE
FEC_UNCOR_BLOCK_
CNT ODU4_PM_FEUAS OTU2_FEES
ODU2_TCMn_FEBBER ODUFLEX_TCMn_ES
Good Octets
Pause Frames Transmitted Multicast Packets Transmitted Transmitted
Packets Transmitted
(128~255 Octets in Length) Pause Frames Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Received (65~127 Octets Undersize Packets
Length) in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1519~MTU Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers
TN15LTX
Packets Received
(1024~1518 Octets in
FCS Errors Good Octets Transmitted Length)
Packets Received
Control Frames (1519~MTU Octets in
Transmitted Broadcast Packets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Multicast Packets Transmitted Received
Good Octets
Packets Transmitted Oversize Packets Transmitted Transmitted
Packets Transmitted
(128~255 Octets in Length) Pause Frames Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Received (64 Octets in Undersize Packets
Length) Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (65~127 Octets Oversize Packets
Length) in Length) Received
Packets Transmitted
(1519~MTU Octets in Packets Transmitted (128~255
Length) Octets in Length) Octets Received
TN17LTX
Packets Received
(1024~1518 Octets in
FCS Errors Good Octets Transmitted Length)
Packets Received
Control Frames (1519~MTU Octets in
Transmitted Broadcast Packets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Multicast Packets Transmitted Received
Good Octets
Packets Transmitted Oversize Packets Transmitted Transmitted
Packets Transmitted
(128~255 Octets in Length) Pause Frames Received Fragments
Packets Transmitted
(512~1023 Octets in Packets Received (64 Octets in Undersize Packets
Length) Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (65~127 Octets Oversize Packets
Length) in Length) Received
Packets Transmitted
(1519~MTU Octets in Packets Transmitted (128~255
Length) Octets in Length) Octets Received
LSIOPMAX RSBBE
LSIOPMAX RSBBE
LSIOPMAX RSBBE
TN11M40
FEC_AFT_CORER_FLO
AT ODU0_TCMn_FESES ODU2_PM_UAS
FEC_AFT_COR_ERAV
R ODU0_TCMn_FEUAS ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU0_TCMn_IAES ODU2_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_ES ODU2_TCMn_FESESR
TN53ND2 (COMP)
FEC_AFT_CORER_FLOAT ODU0_PM_UAS ODU2_PM_SES
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN52ND2
FEC_AFT_CORER_FLO
AT ODU0_PM_UAS ODU2_PM_SES
FEC_AFT_COR_ERAV
R ODU1_PM_BBER ODU2_PM_UAS
FEC_BEF_CORER_FLO
AT ODU1_PM_ES ODU2_TCMn_BBE
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEUAS ODU2_TCMn_FEES
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN52ND2(STND)
FEC_AFT_CORER_FLO
AT ODU0_TCMn_FESES ODU2_PM_UAS
FEC_AFT_COR_ERAV
R ODU0_TCMn_FEUAS ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU0_TCMn_IAES ODU2_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_ES ODU2_TCMn_FESESR
TN12ND2
FEC_AFT_CORER_FLOAT ODU1_PM_SES ODU2_TCMn_BIAES
ODU1_PM_FESESR ODU2_TCMn_BBE
ODU1_PM_FEUAS ODU2_TCMn_BBER
TN11ND2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
FEC_AFT_CORER_FLO
AT ODU0_PM_UAS ODU2_PM_SES
FEC_AFT_COR_ERAV
R ODU1_PM_BBER ODU2_PM_UAS
FEC_BEF_CORER_FLO
AT ODU1_PM_ES ODU2_TCMn_BBE
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEUAS ODU2_TCMn_FEES
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN55NO2(REG)
FEC_AFT_CORER_FLO
AT LSTMPMAX ODU2_TCMn_FEUAS
FEC_AFT_COR_ERAV
R ODU2_PM_BBE ODU2_TCMn_SES
FEC_BEF_CORER_FLO
AT ODU2_PM_BBER ODU2_TCMn_SESR
FEC_UNCOR_BLOCK_
CNT ODU2_PM_FESESR OTU2_FEBBE
LSTMPCUR ODU2_TCMn_FESESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
ODU0_PM_UAS ODU2_PM_FEUAS
ODU1_PM_BBE ODU2_PM_SES
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
FEC_AFT_CORER_FLO
AT ODU1_TCMn_ES ODU4_PM_FEBBE
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEBBER ODU4_PM_FEES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_FEES ODU4_PM_FESES
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_SESR ODU4_TCMn_BBE
ODUFLEX_TCMn_FEBBE
ODU0_TCMn_ES ODU3_PM_FEBBE R
FEC_AFT_CORER_FLO
AT ODU1_TCMn_ES ODU4_PM_FEBBE
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEBBER ODU4_PM_FEES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_FEES ODU4_PM_FESES
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_SESR ODU4_TCMn_BBE
ODUFLEX_TCMn_FEBBE
ODU0_TCMn_ES ODU3_PM_FEBBE R
FEC_AFT_COR_ERAV
R ODU1_PM_BBER ODU2_PM_TMP
FEC_BEF_CORER_FLO
AT ODU1_PM_ES ODU2_PM_UAS
FEC_UNCOR_BLOCK_
CNT ODU1_PM_SES ODU2_TCMn_FEES
ODU0_PM_TMP ODU2_PM_FEUAS
TN53NQ2
FEC_AFT_CORER_FLO
AT ODU0_TCMn_FESESR ODU2_PM_UAS
FEC_AFT_COR_ERAV
R ODU0_TCMn_IAES ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU0_TCMn_SES ODU2_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEBBE ODU2_TCMn_FEUAS
TN53NQ2(COMP)
FEC_AFT_CORER_FLO
AT ODU0_PM_UAS ODU2_PM_SES
FEC_AFT_COR_ERAV
R ODU1_PM_BBER ODU2_PM_TMP
FEC_BEF_CORER_FLO
AT ODU1_PM_ES ODU2_PM_UAS
FEC_UNCOR_BLOCK_
CNT ODU1_PM_SES ODU2_TCMn_FEES
ODU0_PM_TMP ODU2_PM_FEUAS
TN52NQ2
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN51NQ2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
FEC_AFT_CORER_FLO
AT ODU0_TCMn_FESES ODU2_PM_UAS
FEC_AFT_COR_ERAV
R ODU0_TCMn_FEUAS ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU0_TCMn_IAES ODU2_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_ES ODU2_TCMn_FESESR
TN53NS2 (COMP)
FEC_AFT_CORER_FLOAT ODU0_PM_UAS ODU2_PM_SES
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN52NS2
FEC_AFT_CORER_FLO
AT ODU0_PM_UAS ODU2_PM_SES
FEC_AFT_COR_ERAV
R ODU1_PM_BBER ODU2_PM_UAS
FEC_BEF_CORER_FLO
AT ODU1_PM_ES ODU2_TCMn_BBE
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEUAS ODU2_TCMn_FEES
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN52NS2(STND)
FEC_AFT_CORER_FLO
AT ODU0_TCMn_FESES ODU2_PM_UAS
FEC_AFT_COR_ERAV
R ODU0_TCMn_FEUAS ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU0_TCMn_IAES ODU2_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_ES ODU2_TCMn_FESESR
TN12NS2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
TN11NS2
FEC_AFT_CORER_FLOAT ODU1_PM_FESESR ODU2_TCMn_BBER
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
FEC_AFT_CORER_FLO
AT ODU1_PM_BBE ODU3_TCMn_FESES
FEC_AFT_COR_ERAV
R ODU1_PM_ES ODU3_TCMn_FEUAS
FEC_BEF_CORER_FLO
AT ODU1_PM_FEBBE ODU3_TCMn_IAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_SES ODUFLEX_PM_ES
ODUFLEX_TCMn_FEBBE
LSCLCMAX ODU1_TCMn_SESR R
ODU0_TCMn_FEUAS ODU3_TCMn_BIAES
ODU0_TCMn_IAES ODU3_TCMn_ES
TN55NS3
FEC_AFT_CORER_FLO
AT ODU1_PM_UAS ODU3_PM_FESESR
FEC_AFT_COR_ERAV
R ODU1_TCMn_BBER ODU3_PM_SES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_BIAES ODU3_PM_SESR
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_FESESR ODU3_TCMn_FEBBE
ODU1_PM_SES ODU3_PM_FEES
ODU1_PM_SESR ODU3_PM_FESES
TN54NS3
FEC_AFT_CORER_FLO
AT ODU1_PM_FEUAS ODU2_TCMn_UAS
FEC_AFT_COR_ERAV
R ODU1_PM_SESR ODU3_PM_BBER
FEC_BEF_CORER_FLO
AT ODU1_PM_TMP ODU3_PM_ES
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_FEBBER ODU3_PM_SES
TN52NS3
FEC_AFT_COR_ER ODU1_PM_FESESR ODU2_TCMn_UAS
TN11NS3
ODU2_PM_ES ODU3_TCMn_FEBBE
FEC_AFT_COR_ER R
ODU2_PM_BBER ODU3_TCMn_FEBBE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
FEC_AFT_CORER_FLO
AT ODU1_TCMn_FEBBER ODU4_PM_FEBBER
FEC_AFT_COR_ERAV
R ODU1_TCMn_FESES ODU4_PM_FESES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_FESESR ODU4_PM_FESESR
FEC_UNCOR_BLOCK_
CNT ODU2_PM_BBE ODU4_TCMn_BBER
ODUFLEX_TCMn_FEBBE
ODU0_TCMn_FEBBER ODU3_PM_FEBBER R
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
FEC_AFT_CORER_FLO
AT ODU1_TCMn_FESESR ODU4_TCMn_BBER
FEC_AFT_COR_ERAV
R ODU1_TCMn_IAES ODU4_TCMn_ES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_SES ODU4_TCMn_FEBBE
FEC_UNCOR_BLOCK_
CNT ODU2_PM_FEBBE ODU4_TCMn_IAES
ODUFLEX_TCMn_FEBBE
ODU0_PM_FEES ODU2_TCMn_SESR R
Q_VALUE_EER_AVER_15
ODU1_PM_FEBBE ODU3_TCMn_IAES M
Q_VALUE_EER_AVER_24
ODU1_PM_FEBBER ODU3_TCMn_SES H
ODU1_PM_UAS ODU4_PM_FEBBER
ODU1_TCMn_BBE ODU4_PM_FEES
TN96NS4
BDTEMPCUR ODU1_TCMn_BBE ODU4_PM_FEBBER
FEC_AFT_CORER_FLO
AT ODU1_TCMn_FESES ODU4_PM_UAS
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEUAS ODU4_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU1_TCMn_IAES ODU4_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_ES ODU4_TCMn_FESESR
ODUFLEX_TCMn_FEBBE
ODU0_PM_FESESR ODU2_TCMn_UAS R
ODU1_PM_UAS ODU4_PM_FEBBE
TN58NS4
BDTEMPCUR ODU1_TCMn_BBE ODU4_PM_FEBBER
FEC_AFT_CORER_FLO
AT ODU1_TCMn_FESES ODU4_PM_UAS
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEUAS ODU4_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU1_TCMn_IAES ODU4_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_ES ODU4_TCMn_FESESR
ODUFLEX_TCMn_FEBBE
ODU0_PM_FESESR ODU2_TCMn_UAS R
ODU1_PM_SESR ODU4_PM_ES
ODU1_PM_UAS ODU4_PM_FEBBE
TN57NS4
FEC_AFT_CORER_FLO
AT ODU1_TCMn_FESES ODU4_PM_UAS
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEUAS ODU4_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU1_TCMn_IAES ODU4_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_ES ODU4_TCMn_FESESR
ODUFLEX_TCMn_FEBBE
ODU0_PM_FESESR ODU2_TCMn_UAS R
ODU1_PM_SESR ODU4_PM_ES
ODU1_PM_UAS ODU4_PM_FEBBE
TN56NS4
FEC_AFT_CORER_FLO
AT ODU1_TCMn_FESES ODU4_PM_UAS
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEUAS ODU4_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU1_TCMn_IAES ODU4_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_ES ODU4_TCMn_FESESR
ODUFLEX_TCMn_FEBBE
ODU0_PM_FESESR ODU2_TCMn_UAS R
ODU1_TCMn_FEBBER ODU4_PM_SES
ODU1_TCMn_FEES ODU4_PM_SESR
TN54NS4
FEC_AFT_CORER_FLO
AT ODU1_TCMn_BIAES ODU4_PM_BBER
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEBBE ODU4_PM_FEBBE
FEC_BEF_CORER_FLO
AT ODU1_TCMn_FEBBER ODU4_PM_FEBBER
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_SES ODU4_PM_SESR
ODU1_TCMn_BBER ODU4_PM_BBE
TN54NS4(REG)
FEC_AFT_CORER_FLO
AT ODU4_PM_BBER OTU4_BBER
FEC_AFT_COR_ERAV
R ODU4_PM_FEBBE OTU4_ES
FEC_BEF_CORER_FLO
AT ODU4_PM_FEBBER OTU4_FEBBE
FEC_UNCOR_BLOCK_
CNT ODU4_PM_SESR OTU4_IAES
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN13OBU2/TN14OBU2
BCVCUR EDTMPMAX SUMOOPMIN
TN97OBU2
BCVCUR EDTMPMIN SUMOOPMAX
TN12OPM8
TN15OPM8
TN97OPM8
FEC_AFT_CORER_FLO
AT MPLS_PW_SLS ODU2_TCMn_FEUAS
FEC_AFT_COR_ERAV
R MPLS_PW_LS_N ODU2_TCMn_SES
FEC_BEF_CORER_FLO
AT MPLS_PW_SLS_N ODU2_TCMn_SESR
FEC_UNCOR_BLOCK_
CNT ODU2_PM_FEBBE OTU2_FEBBE
LSOOPCUR ODU2_TCMn_BBER
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
Count of bytes received Rate of good full-frame bytes Packets Received, 256~511
on PW transmitted Octets in Length
Number of reversely
transmitted packets on a Packets Transmitted,
tunnel Packets Transmitted 1519~MTU Octets in Length
Number of reversely
transmitted bytes on a Packets Transmitted, 64 Packets Transmitted,
tunnel Octets in Length 1024~1518 Octets in Length
Number of reversely
received packets on a Packets Transmitted,
tunnel 128~255 Octets in Length Octets Received
Count of bytes
transmitted at V-UNI Control Frames Received
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN97RPC
CRC4SES LSIOPMIN
CRC4SES LSIOPMIN
AVGMEANPATHDELA
Y MAXPHASEOFFSET BDTEMPCUR
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
HPFEUAS RPLCUR
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
HPFESES OSPITMPMIN
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
MSES RPLMIN
MSES RPLMIN
MSES RPLMIN
MSES RPLMIN
MSES RPLMIN
MSES RPLMIN
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
AVGMEANPATHDELA
Y MAXPHASEOFFSET BDTEMPCUR
TN13STG
AVGMEANPATHDELA
Y MAXMEANPATHDELAY MINMEANPATHDELAY
LSOOPCUR RSES
NOTE
TN97TD20 does not support reporting board performance event feature.
FEC_AFT_CORER_FLO
AT ODU2_PM_FEBBER ODUFLEX_PM_FESESR
FEC_AFT_COR_ERAV
R ODU2_PM_FESES ODUFLEX_PM_SES
FEC_BEF_CORER_FLO
AT ODU2_PM_FESESR ODUFLEX_PM_SESR
FEC_UNCOR_BLOCK_
CNT ODU2_TCMn_BBER OTU2_FEBBE
TN52TDX
FEC_AFT_COR_ER ODU2_PM_BBE ODU2_TCMn_UAS
FEC_BEF_COR_ERAV ODU2_PM_FEBBE
R OTU2_BIAES
FEC_BEF_CORER_FL OTU2_FESES
OAT ODU2_PM_FEUAS
LSTMPMIN ODU2_TCMn_SESR
TN11TDX
LSBIASCUR LSTMPCUR ODU1_PM_SES
LSOOPMIN ODU1_PM_FEUAS
TN12TDX
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN53TDX
Packets Transmitted
(128~255 Octets in
Alignment Errors Octets Transmitted Length)
Packets Transmitted
Oversize Packets (1519~MTU Octets in
Bad Octets Received Received Length)
Packets Transmitted
Oversize Packets (256~511 Octets in
Bad Octets Transmitted Transmitted Length)
Packets Transmitted
(512~1023 Octets in
Broadcast Packets Received Packets Received Length)
Packets Received
(1024~1518 Octets in Packets Transmitted (64
Broadcast Packets Transmitted Length) Octets in Length)
Packets Received
(1519~MTU Octets in
Control Frames Transmitted Length) Pause Frames Received
Packets Received
(256~511 Octets in Pause Frames
FCS Errors Length) Transmitted
Packets Received
(512~1023 Octets in Undersize Packets
Fragments Length) Received
Packets Received
(65~127 Octets in Unicast Packets
Multicast Packets Received Length) Transmitted
Packets Transmitted
(1024~1518 Octets in
Octets Received Length)
TN52TDX
Packets Transmitted (128~255
Alignment Errors Octets Transmitted Octets in Length)
TN11TDX
Multicast Packets
Broadcast Packets Received Received FCS and Alignment Errors
TN12TDX
Undersize Packets
Octets Received Received FCS Errors
Packets Received
(65~127 Octets in
FCS Errors Broadcast Packets Transmitted Length)
Packets Transmitted
(128~255 Octets in
Drop Events Multicast Packets Transmitted Length)
Packets Received
Good Full Frame Octets (256~511 Octets in
Transmitted Good Full Frame Octets Received Length)
Packets Received
Good Full Frame Octets (512~1023 Octets in
Speed Transmitted Good Full Frame Octets Received Length)
Packets Received
Control Frames (1024~1518 Octets in
Transmitted Control Frames Received Length)
Packets Transmitted
(512~1023 Octets in Packets Received and Transmitted Oversize Packets
Length) (1519~MTU Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in
Length) Pause Frames Received Jabbers
Unicast Packets
Transmitted Packets Received
FEC_AFT_COR_ERAV
R ODU1_PM_BBE ODUFLEX_PM_FESES
FEC_BEF_CORER_FLO
AT ODU1_PM_BBER ODUFLEX_PM_FESESR
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEUAS OTU1_BBER
ODU0_PM_SES ODUFLEX_PM_ES
ODU0_PM_SESR ODUFLEX_PM_FEBBE
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
ODU1_TCMn_BBE ODU2_TCMn_SESR
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
FEC_AFT_COR_ERAV
R ODU1_PM_BBE ODUFLEX_PM_FESES
FEC_BEF_CORER_FLO
AT ODU1_PM_BBER ODUFLEX_PM_FESESR
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FESESR OTU1_BBER
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
Drop Events
TN54TOG
ODU0_PM_FEBBER ODU1_TCMn_FESESR
ODU0_PM_FEES ODU1_TCMn_FEUAS
TN11TOM
FEC_AFT_COR_ER ODU1_PM_FEBBER OTU1_BBE
ODU1_PM_FEBBE ODU1_TCMn_UAS
SEFS_S RSOFS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
TN11TOM
Packets
Received(1024~1518 Octets Multicast Packets
Broadcast Packets Received in Length) Transmitted
Drop Events
FEC_AFT_COR_ERAV
R ODU2_PM_FEBBER OTU2_BIAES
FEC_BEF_CORER_FLO
AT ODU2_PM_FEES OTU2_ES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_UAS OTU2_FEUAS
ODU2_PM_BBE ODU2_TCMn_SESR
ODU2_PM_BBER ODU2_TCMn_UAS
TN56TOX
FEC_AFT_CORER_FLO
AT ODUFLEX_PM_FESES ODU2_TCMn_IAES
FEC_AFT_COR_ERAV
R ODUFLEX_PM_FEUAS ODU2_TCMn_SESR
FEC_BEF_CORER_FLO
AT ODUFLEX_PM_SES ODU2_TCMn_UAS
FEC_UNCOR_BLOCK_
CNT ODU2_PM_FEBBE OTU2_FEBBER
ODUFLEX_PM_FEBBE
R ODU2_TCMn_FESESR
ODUFLEX_PM_FEES ODU2_TCMn_FEUAS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
TN55TOX
Packets Transmitted,
Bad Octets Received Unicast Packets Received 1519~MTU Octets in Length
Broadcast Packets
Received Bad Octets Transmitted Packets Transmitted
Multicast Packets
Pause Frames Received Transmitted
TN56TOX
Packets Transmitted,
Bad Octets Received Unicast Packets Received 1519~MTU Octets in Length
Broadcast Packets
Received Bad Octets Transmitted Packets Transmitted
Maximum bandwidth
utilization of the receive Average bandwidth Minimum bandwidth
port utilization of the receive port utilization of the receive port
Maximum bandwidth
utilization of the transmit Average bandwidth Minimum bandwidth
port utilization of the transmit port utilization of the transmit port
LSTMPCUR ODU1_PM_FEUAS
LSTMPMAX ODU1_PM_SES
TN12TQM
FEC_AFT_COR_ER ODU1_PM_FEBBE OTU1_BBE
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN11TQM
Multicast Packets
Drop Events Broadcast Packets Received Received
Oversize Packets
Transmitted
TN12TQM
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
ODU1_PM_ES ODU1_TCMn_UAS
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
FEC_AFT_CORER_FLO
AT ODU2_PM_FEES ODUFLEX_PM_FEUAS
FEC_AFT_COR_ERAV
R ODU2_PM_FESESR ODUFLEX_PM_SESR
FEC_BEF_CORER_FLO
AT ODU2_PM_FEUAS ODUFLEX_PM_TMP
FEC_UNCOR_BLOCK_
CNT ODU2_TCMn_BIAES OTU2_FEBBER
ODU2_PM_FEBBE ODUFLEX_PM_FESES
ODU2_PM_FEBBER ODUFLEX_PM_FESESR
TN53TQX
FEC_AFT_CORER_FLO
AT ODU2_PM_BBE ODU2_TCMn_UAS
FEC_AFT_COR_ERAV
R ODU2_PM_ES OTU2_BBER
FEC_BEF_CORER_FLO
AT ODU2_PM_FEBBE OTU2_BIAES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_SES OTU2_FESESR
LSTMPMAX ODU2_TCMn_SES
LSTMPMIN ODU2_TCMn_SESR
TN52TQX
FEC_AFT_CORER_FLO
AT ODU2_PM_BBER OTU2_BBE
FEC_AFT_COR_ERAV
R ODU2_PM_FEBBE OTU2_BIAES
FEC_BEF_CORER_FLO
AT ODU2_PM_FEBBER OTU2_ES
FEC_UNCOR_BLOCK_
CNT ODU2_PM_TMP OTU2_IAES
TN11TQX
LSBIASCUR LSTMPCUR ODU2_PM_SES
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
TN53TQX
Packets Transmitted (128~255
Alignment Errors Octets Transmitted Octets in Length)
TN52TQX
TN11TQX
Undersize Packets
Octets Received Received FCS Errors
FEC_AFT_CORER_FLO
AT ODU4_TCMn_FEES VALLEY_LSBIAS_CUR
FEC_AFT_COR_ERAV
R ODU4_TCMn_FESESR VALLEY_LSBIAS_MIN
FEC_BEF_CORER_FLO
AT ODU4_TCMn_FEUAS VALLEY_INPOWER_CUR
FEC_UNCOR_BLOCK_ VALLEY_OUTPOWER_CU
CNT OTU4_BBER R
VALLEY_OUTPOWER_MA
LSIOPCUR OTU4_BIAES X
VALLEY_OUTPOWER_MI
LSIOPMAX OTU4_ES N
Broadcast Packets
Octets Received Transmitted Packets Transmitted
Packets Received, 64
Octets in Length Octets Transmitted
LSOOPMIN ODU2_PM_FEUAS
TN53TSXL
FEC_AFT_CORER_FLOAT ODU3_PM_ES OTU3_BBE
ODU3_PM_BBE ODU3_TCMn_SESR
ODU3_PM_BBER ODU3_TCMn_UAS
TN54TSXL
VALLEY_OUTPOWER_CU
CFP_LSBIASMAX PEAK_INPOWER_CUR R
VALLEY_OUTPOWER_MA
CFP_LSBIASMIN PEAK_INPOWER_MAX X
VALLEY_OUTPOWER_MI
CFP_LSBIASCUR PEAK_INPOWER_MIN N
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
Unicast Packets
FCS Errors Good Octets Transmitted Received
Packets Transmitted
(512~1023 Octets in Packets Received (128~255 Octets Undersize Packets
Length) in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets Oversize Packets
Length) in Length) Received
Packets Transmitted
(1519~MTU Octets in Packets Received (512~1023
Length) Octets in Length) Jabbers
LSTMPMAX ODU2_PM_SES
TN55TTX
BDTEMPCUR ODU2_PM_FEBBE ODUFLEX_PM_FEES
FEC_AFT_CORER_FLO
AT ODU2_PM_FESES ODUFLEX_PM_FEUAS
FEC_AFT_COR_ERAV
R ODU2_PM_FEUAS ODUFLEX_PM_SESR
FEC_BEF_CORER_FLO
AT ODU2_PM_SES ODUFLEX_PM_UAS
FEC_UNCOR_BLOCK_
CNT ODU2_TCMn_ES OTU2_FEBBER
ODU2_PM_BBER ODUFLEX_PM_FEBBE
ODU2_PM_ES ODUFLEX_PM_FEBBER
NOTE
In the lists, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
TN54TTX
Packets Transmitted,
Bad Octets Received Unicast Packets Received 1519~MTU Octets in Length
Broadcast Packets
Received Bad Octets Transmitted Packets Transmitted
Multicast Packets
Pause Frames Received Transmitted
TN55TTX
Packets Transmitted,
Bad Octets Received Unicast Packets Received 1519~MTU Octets in Length
Broadcast Packets
Received Bad Octets Transmitted Packets Transmitted
Maximum bandwidth
utilization of the receive Average bandwidth Minimum bandwidth
port utilization of the receive port utilization of the receive port
Maximum bandwidth
utilization of the transmit Average bandwidth Minimum bandwidth
port utilization of the transmit port utilization of the transmit port
TN12VA1/TN13VA1
TN12VA4/TN13VA4
TN52XCH
BDTEMPCUR BDTEMPMAX BDTEMPMIN
6.15 CRC4ES
6.16 CRC4FEES
6.17 CRC4FESES
6.18 CRC4FEUAS
6.19 CRC4SES
6.20 CRC4UAS
6.21 DGD
6.22 EDRPL
6.23 EDTMP
6.24 EDTPL
6.25 EDWCS
6.26 ENVTMP
6.27 ETH_BBE
6.28 ETH_BBER
6.29 ETH_CFM_LS
6.30 ETH_CFM_SLS
6.31 ETH_CFM_CSLS
6.32 ETH_CFM_UAS
6.33 ETH_ES
6.34 ETH_ESR
6.35 ETH_SES
6.36 ETH_SESR
6.37 ETH_UAS
6.38 FEC_AFT_COR_ER
6.39 FEC_AFT_COR_ERAVR
6.40 FEC_AFT_CORER_FLOAT
6.41 FEC_BEF_COR_ER
6.42 FEC_BEF_COR_ERAVR
6.43 FEC_BEF_CORER_FLOAT
6.44 FEC_COR_0BIT_CNT
6.45 FEC_COR_1BIT_CNT
6.46 FEC_COR_BYTE_CNT
6.47 FEC_UNCOR_BLOCK_CNT
6.48 FSWIOP
6.49 FSWOOP
6.50 FSWSNL
6.51 FSWSNR
6.52 HPBBE
6.53 HPCSES
6.54 HPES
6.55 HPFEBBE
6.56 HPFECSES
6.57 HPFEES
6.58 HPFESES
6.59 HPFEUAS
6.60 HPSES
6.61 HPUAS
6.62 ICCLC
6.63 ICTMP
6.64 LSBIAS
6.65 LSCLC
6.66 LSIOP
6.67 LSOOP
6.68 LSTMP
6.69 MEANPATHDELAY
6.70 MPLS_PW_LS
6.71 MPLS_PW_SLS
6.72 MPLS_PW_CSLS
6.73 MPLS_PW_UAS
6.74 MSBBE
6.75 MSCSES
6.76 MSES
6.77 MSFEBBE
6.78 MSFECSES
6.79 MSFEES
6.80 MSFESES
6.81 MSFEUAS
6.82 MSSES
6.83 MSUAS
6.84 ODU2PMBIP8
6.85 ODUk_PM_BBE
6.86 ODUk_PM_BBER
6.87 ODUk_PM_ES
6.88 ODUk_PM_FEBBE
6.89 ODUk_PM_FEBBER
6.90 ODUk_PM_FEES
6.91 ODUk_PM_FESES
6.92 ODUk_PM_FESESR
6.93 ODUk_PM_FEUAS
6.94 ODUk_PM_SES
6.95 ODUk_PM_SESR
6.96 ODUk_PM_TMP
6.97 ODUk_PM_UAS
6.98 ODUk_TCMn_BBE
6.99 ODUk_TCMn_BBER
6.100 ODUk_TCMn_BIAES
6.101 ODUk_TCMn_ES
6.102 ODUk_TCMn_FEBBE
6.103 ODUk_TCMn_FEBBER
6.104 ODUk_TCMn_FEES
6.105 ODUk_TCMn_FESES
6.106 ODUk_TCMn_FESESR
6.107 ODUk_TCMn_FEUAS
6.108 ODUk_TCMn_IAES
6.109 ODUk_TCMn_SES
6.110 ODUk_TCMn_SESR
6.111 ODUk_TCMn_TMP
6.112 ODUk_TCMn_UAS
6.113 OOPRL
6.114 OSC_BBE
6.115 OSC_BBER
6.116 OSC_BIAES
6.117 OSC_ES
6.118 OSC_FEBBE
6.119 OSC_FEBBER
6.120 OSC_FEES
6.121 OSC_FESES
6.122 OSC_FESESR
6.123 OSC_FEUAS
6.124 OSC_IAES
6.125 OSC_SES
6.126 OSC_SESR
6.127 OSC_UAS
6.128 OSPICCV
6.129 OSPITMP
6.130 OTU2SMBIP8
6.131 OTUk_BBE
6.132 OTUk_BBER
6.133 OTUk_BIAES
6.134 OTUk_ES
6.135 OTUk_FEBBE
6.136 OTUk_FEBBER
6.137 OTUk_FEES
6.138 OTUk_FESES
6.139 OTUk_FESESR
6.140 OTUk_FEUAS
6.141 OTUk_IAES
6.142 OTUk_SES
6.143 OTUk_SESR
6.144 OTUk_TMP
6.145 OTUk_UAS
6.146 PCLSOP
6.147 PCLSSN
6.148 PCLSWL
6.149 PCLSWLO
6.150 PHASEOFFSET
6.151 PUMPORP
6.152 RMIOP
6.153 RPL
6.154 RS_TMP
6.155 RSBBE
6.156 RSES
6.157 RSOFS
6.158 RSOOF
6.159 RSSES
6.160 RSUAS
6.161 SUMIOP
6.162 SUMOOP
6.163 TDC
6.164 TLB
6.165 TPL
6.166 VC3BBE
6.167 VC3CSES
6.168 VC3ES
6.169 VC3FEBBE
6.170 VC3FECSES
6.171 VC3FEES
6.172 VC3FESES
6.173 VC3FEUAS
6.174 VC3SES
6.175 VC3UAS
6.176 WCV
6.1 AAINP
Description
Average input noise power of amplifiers boards.
It includes:
l AAINPMAX: stands for the maximum value during a period of time.
l AAINPMIN: stands for the minimum value during a period of time.
l AAINPCUR: stands for the current value.
Impact on System
None
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.2 AAISP
Description
Average input signal power of amplifiers boards.
It includes:
l AAISPMAX: stands for the maximum value during a period of time.
l AAISPMIN: stands for the minimum value during a period of time.
l AAISPCUR: stands for the current value.
Impact on System
None
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.3 AAONP
Description
Average output noise power of amplifiers boards.
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.4 AAOSP
Description
Average output signal power of amplifiers boards.
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.5 AUPJCHIGH
Description
Positive justification count of the administrative unit (AU) pointer.
Impact on System
A small number of positive justification events of the AU pointer occur in the data segment,
which does not affect the system. If the pointer justification event occurs frequently, you need
to check the causes and rectify the frequent adjustments so that the system runs stably.
Related Alarms
None.
Procedure
Step 1 Check whether clock alarms, such as SYN_BAD, LTI, S1_SYN_CHANGE, and
EXT_SYNC_LOS, are generated on the entire network. If yes, clear them first.
Step 2 For network-wide pointer justification, check whether clock configurations are the same as
planned. The configurations to be checked include the clock ID, SSM protocol, and clock
tracing level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are correctly
connected, and whether the ambient temperature of the equipment is within the permitted
range. If the AU pointer justification event occurs continuously, contact Huawei for
assistance.
----End
Related Information
None.
6.6 AUPJCLOW
Description
Negative justification count of the administrative unit (AU) pointer
Impact on System
A small number of negative justification events of the AU pointer occur in the data segment,
which does not affect the system. If the pointer justification event occurs frequently, you need
to check the causes and rectify the frequent adjustments so that the system runs stably.
Related Alarms
None.
Procedure
Step 1 Check whether clock alarms, such as SYN_BAD, LTI, S1_SYN_CHANGE, and
EXT_SYNC_LOS, are generated on the entire network. If yes, clear them first.
Step 2 For network-wide pointer justification, check whether clock configurations are the same as
planned. The configurations to be checked include the clock ID, SSM protocol, and clock
tracing level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are correctly
connected, and whether the ambient temperature of the equipment is within the permitted
range. If the AU pointer justification event occurs continuously, contact Huawei for
assistance.
----End
Related Information
None.
6.7 AUPJCNEW
Description
New count of the administrative unit (AU) pointer
Impact on System
A new count of AU pointers is generated, which does not affect the system. If a new count of
AU pointers is generated frequently, you need to check the causes and rectify the frequent
adjustments so that the system runs stably.
Related Alarms
None.
Procedure
Step 1 Check whether clock alarms, such as SYN_BAD, LTI, S1_SYN_CHANGE, and
EXT_SYNC_LOS, are generated on the entire network. If yes, clear them first.
Step 2 For network-wide pointer justification, check whether clock configurations are the same as
planned. The configurations to be checked include the clock ID, SSM protocol, and clock
tracing level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are connected
correctly, and whether the ambient temperature of the equipment is within the permitted
range. If the AU pointer justification event occurs continuously, contact Huawei for
assistance.
----End
Related Information
None.
6.8 BCV
Description
Pump laser back facet current
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.9 BDTEMP
Description
Board temperature. It contains the BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR,
which respectively indicates the maximum value, minimum value, and current value of the
temperature of a board.
Impact on System
Excessively high or low board temperature might cause faults such as degradation of the
board working performance and bit errors.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If any alarm occurs, handle the alarm by referring to the alarm handling procedure.
----End
Related Information
None.
6.10 CCV
Description
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.
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the PUMP_COOL_EXC alarm is generated, handle the alarm by referring to the alarm
handling procedure.
----End
Related Information
For a TN51MCS0816 board equipped with an optical module whose BoardType is
60461984, it is a normal symptom when an invalid value is reported during the query of
CCVMAX, CCVMIN, or CCVCUR performance. For details about the optical module
information, see Querying Optical Module Information.
6.11 CFP_LSBIAS
Description
Bias current of the laser on the channel of the CFP module.
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.12 CFP_LSIOP
Description
Input optical power of the laser on the channel of the CFP module.
It includes:
Impact on System
When the input optical power is excessively high or low, bit errors and the LOF alarm may be
generated in the received signals, which brings impact on the services.
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.13 CFP_LSOOP
Description
Output optical power of the laser on the channel of the CFP module.
It includes:
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal
transmission of services.
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.14 CFP_LSTMP
Description
Working temperature of the laser on the channel of the CFP module.
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.15 CRC4ES
Description
CRC4 errored seconds
Impact on System
There are bit errors in the services. If the CRC4 errored seconds are generated continuously,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.16 CRC4FEES
Description
CRC4 far end errored second
Impact on System
There are bit errors in the services. If the far-end errored seconds are generated continuously,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality. If the number of bit errors exceeds the threshold, the
CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.17 CRC4FESES
Description
CRC4 far end severely errored second
Impact on System
There are many bit errors in the services. Identify the cause and solve the problem in a timely
manner to avoid any alarm, and therefore ensuring the signal transmission quality. If the
number of bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.18 CRC4FEUAS
Description
CRC4 far end unavailable second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality. If the number of
bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.19 CRC4SES
Description
CRC4 severely errored second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality. If the number of
bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.20 CRC4UAS
Description
CRC4 unavailable second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality. If the number of
bit errors exceeds the threshold, the CRC4_CROSSTR alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.21 DGD
Description
Polarization mode dispersion
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.22 EDRPL
Description
EDFA input optical power
It includes:
Impact on System
When the input optical power is excessively high or very low, bit errors and the LOF alarm
may be generated in the received signals, which brings impact on the services.
Related Alarms
Alarm Name Correlation
IN_PWR_HIGH It is generated when the optical power input by board is higher than
the upper threshold.
IN_PWR_LOW It is generated when the optical power input by board is lower than
the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
history performance value and the change in optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
history performance value and the change in optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW alarm.
----End
Related Information
None
6.23 EDTMP
Description
Laser temperature value
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
PUM_TEM_ALM The working temperature of the pump laser exceeds the threshold.
This alarm is generated when the pump laser operating temperature
of the optical amplifier board exceeds the threshold.
Procedure
Step 1 See the procedure for handling the PUM_TEM_ALM alarm.
----End
Related Information
For a TN51MCS0816 board equipped with an optical module whose BoardType is
60461984, it is a normal symptom when the reported values are not stable during the query of
EDTMPMAX, EDTMPMIN, or EDTMPCUR performance. For details about the optical
module information, see Querying Optical Module Information.
6.24 EDTPL
Description
Pump output optical power
It includes:
Impact on System
Bit errors may be generated in the services and the services may be interrupted.
Related Alarms
Alarm Name Correlation
OUT_PWR_HIGH This alarm is generated when the optical power output by the pump
laser is higher than the upper threshold.
OUT_PWR_LOW This alarm is generated when the optical power output by the pump
laser is lower than the lower threshold.
Procedure
Step 1 See the procedure for handling the OUT_PWR_HIGH or OUT_PWR_LOW alarm.
----End
Related Information
None
6.25 EDWCS
Description
Value of EDFA working current setup
It includes:
l EDWCSMAX: stands for the maximum value during a period of time.
l EDWCSMIN: stands for the minimum value during a period of time.
l EDWCSCUR: stands for the current value.
Impact on System
None.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.26 ENVTMP
Description
Board ambient temperature
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the related handling procedure.
----End
Related Information
None
6.27 ETH_BBE
Description
40GE/100GE background block error.
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.28 ETH_BBER
Description
40GE/100GE ratio of background block error.
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.29 ETH_CFM_LS
Description
Packet loss seconds of the E-Line service
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of severe packet loss seconds. If the packet loss is severe, the service
quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If packet loss exists in a second, this second is included in packet loss seconds.
6.30 ETH_CFM_SLS
Description
Severe packet loss seconds of the E-Line service
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of severe packet loss seconds. If the packet loss is severe, the service
quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If the packet loss ratio in a second exceeds the set threshold value, this second is included in
the severe packet loss seconds.
6.31 ETH_CFM_CSLS
Description
Consecutive severe packet loss seconds of the E-Line service
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of consecutive severe packet loss seconds. If the packet loss is
severe, the service quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If the previous second is a severe packet loss second and this second is also a severe packet
loss second, this second is included in the consecutive severe packet loss seconds.
6.32 ETH_CFM_UAS
Description
Unavailable seconds of the E-Line service
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of unavailable seconds. If the packet loss is severe, the service
quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If the packet loss ratio exceeds the set threshold value for ten consecutive seconds and this
second is a severe packet loss second, these seconds are included in the unavailable seconds.
6.33 ETH_ES
Description
40GE/100GE errored second.
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.34 ETH_ESR
Description
40GE/100GE ratio of errored second
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.35 ETH_SES
center wavelength
40GE/100GE severely errored second.
Impact on System
There are severely errored second in the services. Identify the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.36 ETH_SESR
Description
40GE/100GE ratio of severely errored second.
Impact on System
There are severely errored second in the services. Identify the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.37 ETH_UAS
Description
40GE/100GE unavailable second.
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ETH_BIP8_SD or ETH_HI_BER alarm.
----End
Related Information
None
6.38 FEC_AFT_COR_ER
Description
After FEC correct errored rate
Impact on System
In normal cases, the value should be 0 after the error correction. If the value is not 0, the bit
errors in the services have affected the signal transmission quality. When this occurs, identify
the cause in a timely manner.
When there are post-FEC bit errors, there are also pre-FEC bit errors (FEC_BEF_COR_ER)
accompanied. In this case, check the services in a timely manner.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.39 FEC_AFT_COR_ERAVR
Description
After FEC correct average errored rate in monitor period
Impact on System
In normal cases, the value should be 0 after the error correction. If the value is not 0, the bit
errors in the services have affected the signal transmission quality. When this occurs, identify
the cause in a timely manner
When there are post-FEC bit errors, there are also pre-FEC bit errors
(FEC_BEF_COR_ERAVR) accompanied. In this case, check the services in a timely manner.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.40 FEC_AFT_CORER_FLOAT
Description
After FEC correct errored rate (floating point values)
Impact on System
In normal cases, the value should be 0 after the error correction. If the value is not 0, the bit
errors in the services have affected the signal transmission quality. When this occurs, identify
the cause in a timely manner.
When there are post-FEC bit errors, there are also pre-FEC bit errors
(FEC_BEF_CORER_FLOAT) accompanied. In this case, check the services in a timely
manner
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.41 FEC_BEF_COR_ER
Description
BER before FEC
Impact on System
There are bit errors on the line. The services, however, may not be affected. If the bit error
rate (BER) is low, the system operates properly. If the BER is high, identify the causes and
solve the problem timely to avoid any alarm, therefore ensuring the signal transmission
quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.42 FEC_BEF_COR_ERAVR
Description
Before FEC correct average errored Rate in monitor period
Impact on System
There are bit errors on the line. The services, however, may not be affected. If the bit error
rate (BER) is low, the system operates properly. If the BER is high, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.43 FEC_BEF_CORER_FLOAT
Description
Before FEC correct errored rate (floating point values)
Impact on System
There are bit errors on the line. The services, however, may not be affected. If the bit error
rate (BER) is low, the system operates properly. If the BER is high, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.44 FEC_COR_0BIT_CNT
Description
Forward error correction - corrected 0 bit count
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.45 FEC_COR_1BIT_CNT
Description
Forward error correction - corrected 1 bit count
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.46 FEC_COR_BYTE_CNT
Description
Forward error correction - corrected byte count
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.47 FEC_UNCOR_BLOCK_CNT
Description
Forward error correction - uncorrected block count
Impact on System
There are bit errors in the services and the signal transmission quality is affected.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.48 FSWIOP
Description
Single wave input power of amplifiers boards.
It includes:
Impact on System
When the input optical power is excessively high or low, bit errors and the LOF alarm may be
generated in the received signals, which brings impact on the services.
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.49 FSWOOP
Description
Single wave output power of amplifiers boards.
It includes:
Impact on System
When the output optical power is excessively high or low, bit errors may generated in the
services or even the services are interrupted.
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.50 FSWSNL
Description
Single wave OSNR loss of amplifiers boards.
It includes:
Impact on System
If the single-wavelength OSNR loss is abnormal, service signals may be unstable and the
BER may increase. Then, an alarm indicating excessively low or high path optical power may
occur and the performance may be abnormal.
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.51 FSWSNR
Description
Single wave OSNR of amplifiers boards.
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.52 HPBBE
Description
Background block error (BBE) on a higher-order path
Impact on System
A small number of bit errors occur on the higher-order path. If no related alarm is generated,
the system is not affected. You need to, however, identify the causes and resolve the problem
in a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
of the higher-order path deteriorates.
Related Alarms
Alarm Name Correlation
B3_SD This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10–6).
B3_EXC This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10-3).
Procedure
Step 1 See the procedures for handling the B3_SD and B3_EXC alarms.
----End
Related Information
BBE
The BBE indicates that one or more bit errors occur in the data block during transmission.
6.53 HPCSES
Description
Higher order path consecutive severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarms are generated,
the system is not affected. You need to, however, find out the causes and take proper measures
in time to avoid generating alarms, which affect the quality of the signals transmitted in the
higher order path.
Related Alarms
Alarm Name Correlation
B3_SD When the count of B3 bit errors in the alarm path is close to the
threshold (1 x 10-6), the alarm is reported.
B3_EXC When the count of B3 bit errors in the alarm path exceeds the
threshold (1 x 10-3), the alarm is reported.
Procedure
Step 1 See the procedures for handling the B3_SD and B3_EXC alarms.
----End
Related Information
None.
6.54 HPES
Description
Errored second (ES) on a higher-order path
Impact on System
A small number of bit errors occur on the higher-order path. If no related alarm is generated,
the system is not affected. You need to, however, identify the causes and resolve the problem
in a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
of the higher-order path deteriorates.
Related Alarms
Alarm Name Correlation
B3_SD This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10–6).
B3_EXC This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10–3).
Procedure
Step 1 See the procedures for handling the B3_SD and B3_EXC alarms.
----End
Related Information
ES
The ES indicates a second in which one or more errored blocks are detected.
6.55 HPFEBBE
Description
Far end background block error (BBE) on a higher-order path
Impact on System
The remote end detects that a small number of bit errors occur on the higher-order path. If no
related alarm is generated, the system is not affected. You need to, however, identify the
causes and resolve the problem in a timely manner. Otherwise, alarms may be generated, and
the signal transmission quality of the higher-order path deteriorates.
Related Alarms
Alarm Name Correlation
HP_REI This alarm is generated when the board detects that the value is 1 to 8
for bits 1 to 4 of the G1 byte on the higher-order path.
Procedure
Step 1 See the procedure for handling the HP_REI alarm.
----End
Related Information
BBE
The BBE indicates that one or more bit errors occur in the data block during transmission.
6.56 HPFECSES
Description
Higher order path far end consecutive severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarms
are generated, the system is not affected. You need to, however, find out the causes and take
proper measures in time to avoid generating alarms, which affect the quality of the signals
transmitted in the higher order path.
Related Alarms
Alarm Name Correlation
HP_REI If the board has detected that the value is 1-8 for bits 1-4 of the G1
byte in the higher order path, the alarm is reported.
Procedure
Step 1 See the procedure for handling the HP_REI alarm.
----End
Related Information
Severely Errored Second
The SES (severely errored second) refers to the second in which more than 30% errored
blocks occur or at least one SDP (serious disturbance period) occurs.
The CSES (consecutive severely errored second) refers to the SES (severely errored second)
event that occurs consecutively.
The remote bit error refers to the bit error that is detected at the opposite station.
6.57 HPFEES
Description
Far end errored second (ES) on a higher-order path
Impact on System
The remote end detects that a small number of bit errors occur on the higher-order path. If no
related alarm is generated, the system is not affected. You need to, however, identify the
causes and resolve the problem in a timely manner. Otherwise, alarms may be generated, and
the signal transmission quality of the higher-order path deteriorates.
Related Alarms
Alarm Name Correlation
HP_REI This alarm is generated when the board detects that the value is 1 to 8
for bits 1 to 4 of the G1 byte on the higher-order path.
Procedure
Step 1 See the procedure for handling the HP_REI alarm.
----End
Related Information
Far End Errored Second
The far end errored second (FEES) indicates an errored second that is detected at the remote
end.
6.58 HPFESES
Description
Far end severely errored second (SES) on a higher-order path
Impact on System
The remote end detects that a large number of bit errors occur on the higher-order path. If no
related alarm is generated, the system is not affected. You need to, however, identify the
causes and resolve the problem in a timely manner. Otherwise, alarms may be generated, and
the signal transmission quality of the higher-order path deteriorates.
Related Alarms
Alarm Name Correlation
HP_REI This alarm is generated when the board detects that the value is 1 to 8
for bits 1 to 4 of the G1 byte on the higher-order path.
Procedure
Step 1 See the procedure for handling the HP_REI alarm.
----End
Related Information
SES
The SES indicates a certain second in which more than 30% errored blocks occur or at least a
serious disturbance period (SDP) occurs.
6.59 HPFEUAS
Description
Far end unavailable second (UAS) on a higher-order path
Impact on System
If bit errors occur in the services on a remote NE, identify the causes and resolve the problem
in a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
deteriorates.
External causes:
l The fiber performance deteriorates or the attenuation is excessive on the remote NE.
l The fiber connector is contaminated or incorrect on the remote NE.
l The remote NE is improperly grounded.
l There is a strong interference source around the remote NE.
l The peer NE runs in an environment with a temperature that exceeds the threshold.
Equipment problems:
l The signals received by the line board on the remote NE are greatly attenuated, the
transmitting circuit on the remote end is faulty, or the receive circuit on the local end is
faulty.
l The synchronization performance of the clock is poor on the remote NE.
l The cross-connection unit and the line board do not match on the remote NE.
l The fan on the remote NE is faulty.
l The board malfunctions or the board performance deteriorates on the remote NE.
Related Alarms
Alarm Name Correlation
HP_REI Indicates a bit error on a higher-order path detected at the remote end.
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None.
6.60 HPSES
Description
Severely errored second on a higher-order path
Impact on System
A large number of bit errors occur on the higher-order path. If no related alarm is generated,
the system is not affected. You need to, however, identify the causes and resolve the problem
in a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
of the higher-order path deteriorates.
Related Alarms
Alarm Name Correlation
B3_SD This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10-6).
B3_EXC This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10-3).
Procedure
Step 1 See the procedures for handling the B3_SD and B3_EXC alarms.
----End
Related Information
SES
The SES indicates a certain second in which more than 30% errored blocks occur or at least a
serious disturbance period (SDP) occurs.
6.61 HPUAS
Description
Unavailable second (UAS) on a higher-order path
Impact on System
l A large number of bit errors occur on the higher-order path. If no related alarm is
generated, the system is not affected. You need to, however, identify the causes and
resolve the problem in a timely manner. Otherwise, alarms may be generated, and the
signal transmission quality of the higher-order path deteriorates.
l When this performance event occurs, check whether alarms, such as AU_AIS, B3_EXC,
and HP_UNEQ, exist. If yes, services may be interrupted.
Related Alarms
Alarm Name Correlation
B3_SD This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10–6).
B3_EXC This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1×10–3).
Procedure
Step 1 See the procedures for handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and HP_UNEQ
alarms.
----End
Related Information
None.
6.62 ICCLC
Description
Module cooling current
It includes:
l ICCLCMAX: stands for the maximum value during a period of time.
l ICCLCMIN: stands for the minimum value during a period of time.
l ICCLCCUR: stands for the current value.
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the MODULE_COOLCUR_OVER alarm is generated, see the related handling
procedure.
----End
Related Information
None
6.63 ICTMP
Description
Module temperature
It includes:
l ICTMPMAX: stands for the maximum value during a period of time.
l ICTMPMIN: stands for the minimum value during a period of time.
l ICTMPCUR: stands for the current value.
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the MODULE_TEMP_OVER alarm is generated, see the related handling procedure.
----End
Related Information
None
6.64 LSBIAS
Description
Laser bias current
It includes:
l LSBIASMAX: stands for the maximum value during a period of time.
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the TD alarm is generated, see the related handling procedure.
Step 2 If the LSR_WILL_DIE alarm is generated, see the related handling procedure.
----End
Related Information
None
6.65 LSCLC
Description
Laser cooling current
It includes:
Impact on System
When the cooling current of a laser exceeds the threshold, the optical module of the board
works abnormally. As a result, services cannot be correctly transmitted or received.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the LSR_COOL_ALM alarm is generated, see the related handling procedure.
----End
Related Information
None
6.66 LSIOP
Description
Input optical power
It includes:
Impact on System
When the input optical power is excessively high or low, bit errors and the LOF alarm may be
generated in the received signals, which brings impact on the services.
Related Alarms
Alarm Name Correlation
IN_PWR_HIGH This alarm is generated when the optical power input by board is
higher than the upper threshold.
IN_PWR_LOW This alarm is generated when the optical power input by board is
lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
historical performance value and the change in optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the
IN_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
historical performance value and the change in optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW
alarm.
----End
Related Information
None
6.67 LSOOP
Description
Output optical power
It includes:
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal
transmission of services.
Related Alarms
Alarm Name Correlation
OUT_PWR_HIGH This alarm is generated when the optical power output by a board is
higher than the upper threshold.
OUT_PWR_LOW This alarm is generated when the optical power output by a board is
lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
historical performance value and the change of optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the
OUT_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
historical performance value and the change of optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the
OUT_PWR_LOW alarm.
----End
Related Information
None
6.68 LSTMP
Description
Laser temperature
It includes:
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the TEM_HA or TEM_LA alarm is generated, see the related handling procedure.
----End
Related Information
None
6.69 MEANPATHDELAY
Description
Path delay between the master clock and a slave clock. It includes the
MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY
performance parameters, which indicate the maximum, minimum, and average path delays
respectively.
Impact on System
It is an indicator of the IEEE 1588v2 performance and has no impact on services.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.70 MPLS_PW_LS
Description
Packet loss seconds of the PW service.
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of packet loss seconds. If the packet loss is severe, the service
quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
During the statistics period, if packet loss exists in a second, this second is included in the
packet loss seconds.
6.71 MPLS_PW_SLS
Description
Severe packet loss seconds of the PW service.
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of severe packet loss seconds. If the packet loss is severe, the service
quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If the packet loss ratio in a second exceeds the set threshold value, this second is included in
the severe packet loss seconds.
6.72 MPLS_PW_CSLS
Description
Consecutive severe packet loss seconds of the PW service
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of consecutive severe packet loss seconds. If the packet loss is
severe, the service quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If the previous second is a severe packet loss second and this second is also a severe packet
loss second, this second is included in the consecutive severe packet loss seconds.
6.73 MPLS_PW_UAS
Description
Unavailable seconds of the PW service.
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of severe packet loss seconds. If the packet loss is severe, the service
quality is affected.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set
bandwidth, bandwidth expansion is needed.
----End
Related Information
If the packet loss ratio exceeds the set threshold value for ten consecutive seconds and this
second is a severe packet loss second, these seconds are included in the unavailable seconds.
6.74 MSBBE
Description
MS background block error
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
R_LOF Loss of frame on receiving line. This alarm is generated when the
frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
Step 1 See the procedure for handling the B2_EXC alarm.
----End
Related Information
None
6.75 MSCSES
Description
MS consecutive severely errored second
Impact on System
There are a large number of bit errors in the services. Identify the cause and solve the problem
in a timely manner because the bit errors severely affect the signal transmission quality. In
addition, the B2_EXC and B2_SD alarms may be generated.
Related Alarms
Alarm Name Correlation
R_LOF Loss of frame on receiving line. This alarm is generated when the
frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
Step 1 See the procedure for handling the B2_EXC alarm.
----End
Related Information
None
6.76 MSES
Description
MS errored second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
R_LOF Loss of frame on receiving line. This alarm is generated when the
frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
Step 1 See the procedure for handling the B2_EXC alarm.
----End
Related Information
None
6.77 MSFEBBE
Description
MS far end background block error
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the MS_RDI alarm.
----End
Related Information
None
6.78 MSFECSES
Description
MS far end consecutive severely errored second
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the MS_RDI alarm.
----End
Related Information
None
6.79 MSFEES
Description
MS far end errored second
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the MS_RDI alarm.
----End
Related Information
None
6.80 MSFESES
Description
MS far end severely errored second
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the MS_RDI alarm.
----End
Related Information
None
6.81 MSFEUAS
Description
MS far end unavailable second
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the MS_RDI alarm.
----End
Related Information
None
6.82 MSSES
Description
MS severely errored second
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
R_LOF Loss of frame on receiving line. This alarm is generated when the
frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
Step 1 See the procedure for handling the B2_EXC alarm.
----End
Related Information
None
6.83 MSUAS
Description
MS unavailable second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner to ensure the signal transmission quality.
Related Alarms
Alarm Name Correlation
R_LOS Loss of signal on receiving line. This alarm is generated when the
receive side receives no signals.
Procedure
Step 1 See the procedure for handling the B2_EXC alarm.
----End
Related Information
None
6.84 ODU2PMBIP8
Description
Number of BIP8 bit errors in the PM section at the optical data unit (ODU) layer
Attribute
Performance Event Performance Event Type
ID
Impact on System
Bit errors occur in the services. Identify the causes and resolve the problem in a timely
manner. Otherwise, alarms may be generated, and the signal transmission quality deteriorates.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None.
6.85 ODUk_PM_BBE
Description
ODU PM section background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
ODUk_PM_EXC Bit interleaved parity (BIP) in the PM section of the ODU layer
exceeds the upper threshold. This alarm is generated when the
number of BIP8 bit errors of the PM section on the optical channel
data unit layer exceeds the upper threshold.
ODUk_PM_DEG Bit interleaved parity signal in the PM section of the ODU layer
degrades. This alarm is generated when the number of BIP8 bit
errors of the PM section of the ODU layer exceeds the degrade
threshold.
Procedure
Step 1 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.86 ODUk_PM_BBER
Description
ODU PM section ratio of background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. This alarm
is generated when the number of BIP8 bit errors of the PM section
on the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG Bit interleaved parity signal in the PM section of the ODU layer
degrades. This alarm is generated when the number of BIP8 bit
errors of the PM section of the ODU layer exceeds the degraded
threshold.
Procedure
Step 1 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.87 ODUk_PM_ES
Description
ODU PM section errored second
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. This alarm
is generated when the number of BIP8 bit errors of the PM section
on the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG Bit interleaved parity signal in the PM section of the ODU layer
degrades. This alarm is generated when the number of BIP8 bit
errors of the PM section of the ODU layer exceeds the degraded
threshold.
Procedure
Step 1 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.88 ODUk_PM_FEBBE
Description
ODU PM section far end background block error
k indicate the level of rate. The value k is 0, 1, 2, 3, 4, 5G or FLEX.
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.89 ODUk_PM_FEBBER
Description
ODU PM section ratio of far end background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.90 ODUk_PM_FEES
Description
ODU PM section far end errored second
k indicate the level of rate. The value k is 0, 1, 2, 3, 4, 5G or FLEX.
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.91 ODUk_PM_FESES
Description
ODU PM section far end severely errored second
k indicate the level of rate. The value k is 0, 1, 2, 3, 4, 5G or FLEX.
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.92 ODUk_PM_FESESR
Description
ODU PM section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.93 ODUk_PM_FEUAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services on a far-end NE. The services may be affected.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.94 ODUk_PM_SES
Description
ODU PM section severely errored second
Impact on System
There are bit errors in services. Identify the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. This alarm
is generated when the number of BIP8 bit errors of the PM section
of the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG Optical channel data unit layer, path monitoring section bit
interleaved parity signal degraded. This alarm is generated when the
number of BIP8 bit errors of the PM section of the optical channel
data unit layer exceeds the degraded threshold.
Procedure
Step 1 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.95 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
k indicate the level of rate. The value k is 0, 1, 2, 3, 4, 5G or FLEX.
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. This alarm
is generated when the number of BIP8 bit errors of the PM section
on the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG Optical channel data unit layer, path monitoring section bit
interleaved parity signal degraded. This alarm is generated when the
number of BIP8 bit errors of the PM section on the optical channel
data unit layer exceeds the degraded threshold.
Procedure
Step 1 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.96 ODUk_PM_TMP
Description
Total period for period performance of ODU signals in the PM section
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.97 ODUk_PM_UAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.
Related Alarms
Alarm Name Correlation
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. This alarm
is generated when the number of BIP8 bit errors of the PM section
on the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG Optical channel data unit layer, path monitoring section bit
interleaved parity signal degraded. This alarm is generated when the
number of BIP8 bit errors of the PM section on the optical channel
data unit layer exceeds the degraded threshold.
Procedure
Step 1 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.98 ODUk_TCMn_BBE
Description
ODUk TCMn section background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 On the U2000, check whether there are a large number of BIP8 bit errors of the TCM section
in the input signals on the client side. If yes, rectify the fault on the client-side equipment.
Step 2 If the performance keeps deteriorating, see the procedure for handling the
ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.99 ODUk_TCMn_BBER
Description
ODUk TCMn section ratio of background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 On the U2000, check whether there are a large number of BIP8 bit errors of the TCM section
in the input signals on the client side. If yes, rectify the fault on the client-side equipment.
Step 2 If the performance event persists, see the procedure for handling the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.100 ODUk_TCMn_BIAES
Description
ODU TCMn section backward introducing alignment errored second
Impact on System
There are errors in frame alignment. Identify the cause and solve the problem in a timely
manner to ensure the signal transmission quality.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical port is within the
permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the input optical power is abnormal, see the
procedures for handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
----End
Related Information
None
6.101 ODUk_TCMn_ES
Description
ODUk TCMn section errored second
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 On the U2000, check whether there are a large number of BIP8 bit errors of the TCM section
in the input signals on the client side. If yes, rectify the fault on the client-side equipment.
Step 2 If the performance event persists, see the procedure for handling the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.102 ODUk_TCMn_FEBBE
Description
ODUk TCMn section far end background block error
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
inserted indication to the local end after the background block errors are detected at the
opposite end.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical port is within the
permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.. If the input optical power is abnormal, see the
procedures for handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
----End
Related Information
None
6.103 ODUk_TCMn_FEBBER
Description
ODUk TCMn section ratio of far end background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical port is within the
permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the input optical power is abnormal, see the
procedures for handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
----End
6.104 ODUk_TCMn_FEES
Description
ODUk TCMn section far end errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
None
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_BDI alarm.
----End
Related Information
None
6.105 ODUk_TCMn_FESES
Description
ODUk TCMn section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical port is within the
permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the input optical power is abnormal, see the
procedures for handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
----End
Related Information
None
6.106 ODUk_TCMn_FESESR
Description
ODUk TCMn section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Identify the cause and solve the problem
in a timely manner, therefore ensuring the signal transmission quality.
Related Alarms
None
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_SESR alarm.
----End
Related Information
None
6.107 ODUk_TCMn_FEUAS
Description
ODUk TCMn section unavailable second
Impact on System
The far-end services are not available.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_BDI alarm.
----End
Related Information
None
6.108 ODUk_TCMn_IAES
Description
ODUk TCMn section introducing alignment errored second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.
Related Alarms
Alarm Name Correlation
OTUk_LOF OTUk frame loss. The upstream station detects the LOF alarm and
then inserts IAE. The local station reports ODU1_TCMn_IAES.
Procedure
Step 1 See the procedure for handling the OTUk_LOF alarm.
----End
Related Information
None
6.109 ODUk_TCMn_SES
Description
ODUk TCMn section severely errored second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.110 ODUk_TCMn_SESR
Description
ODUk TCMn section ratio of severely errored second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.111 ODUk_TCMn_TMP
Description
Total period for monitoring performance of ODUk signals in the TCM section
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.112 ODUk_TCMn_UAS
Description
ODUk TCMn section unavailable second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.113 OOPRL
Description
Optical output power return loss
It includes:
l OOPRLMAX: maximum value of the output optical power return loss within a time
period
l OOPRLMIN: minimum value of the output optical power return loss within a time
period
l OOPRLCUR: current value of the output optical power return loss
Impact on System
Services may be interrupted.
Related Alarms
Alarm Name Correlation
RL_CRITICAL_HI This alarm is generated when the return loss is higher than the
upper threshold of the return loss alarm.
RL_CRITICAL_LO This alarm is generated when the return loss is lower than the lower
W threshold of the return loss alarm.
Procedure
Step 1 See the procedure for handling the RL_CRITICAL_HI or RL_CRITICAL_LOW alarm.
----End
Related Information
None
6.114 OSC_BBE
Description
OSC path section background block error
Impact on System
There are bit errors in the OSC signals. If the number of block errors increases, identify the
cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.115 OSC_BBER
Description
OSC path section ratio of background block error
Impact on System
When the value is not 0, there are bit errors in the OSC signals. When the value is large,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
background block errors to the number of all blocks minus the number of blocks during the
unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.116 OSC_BIAES
Description
OSC path backward incoming alignment errored second
Impact on System
There are errors in frame alignment. Identify the cause and solve the problem in a timely
manner to ensure the signal transmission quality.
Related Alarms
None
Procedure
Step 1 If the performance event persists, handling bit error fault.
----End
Related Information
None
6.117 OSC_ES
Description
OSC path errored second
Impact on System
There are bit errors in the OSC signals. If the number of bit errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.118 OSC_FEBBE
Description
OSC path far end background block error
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.119 OSC_FEBBER
Description
OSC path section ratio of far end background block error
Impact on System
When the value is not 0, there are bit errors in the signals. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.120 OSC_FEES
Description
OSC path section far end background block error
Impact on System
There are bit errors in the signals on a far-end NE. If the number of block errors increases,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.121 OSC_FESES
Description
OSC path section far end severely errored second
Impact on System
There are bit errors in the signals on a far-end NE. Identify the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.122 OSC_FESESR
Description
OSC path section ratio of far end severely errored second
Impact on System
There are bit errors in the signals on a far-end NE. Identify the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.123 OSC_FEUAS
Description
OSC path section unavailable second
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission
quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.124 OSC_IAES
Description
OSC path section errored second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.125 OSC_SES
Description
OSC path section severely errored second
Impact on System
There are severely errored second in the OSC signals. Identify the cause and solve the
problem in a timely manner because the bit errors have affected the signal transmission
quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.126 OSC_SESR
Description
OSC path section ratio of severely errored second
Impact on System
There are severely errored second in the signals. Identify the cause and solve the problem in a
timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.127 OSC_UAS
Description
OSC path section unavailable second
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission
quality.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.128 OSPICCV
Description
The OSPICCV indicates the value of the cooling current of the laser.
It includes:
Impact on System
The performance event does not affect the equipment and the system. If the cooling current of
the laser is excessively high or low, however, the laser may work abnormally. If the cooling
current is within the permitted range, you do not need to take any action.
Related Alarms
Alarm Name Correlation
LSR_COOL_ALM When the cooling current of the laser is beyond the specified
range, this alarm is generated.
Procedure
Step 1 See the procedure for handling the LSR_COOL_ALM alarm.
----End
Related Information
None
6.129 OSPITMP
Performance Event Meaning
Temperature in the tube core of the laser
It includes:
Impact on System
The performance event does not affect the equipment and the system. If the temperature in the
tube core of the laser is excessively high or low; however, the laser may work abnormally. As
a result, the services may be interrupted. If the temperature is within the permitted range, you
do not need to take any action.
Related Alarms
Alarm Name Correlation
TEM_HA When the temperature of the laser is higher than the upper
threshold, the alarm is reported.
TEM_LA When the temperature of the laser is less than the lower threshold,
the alarm is reported.
Procedure
Step 1 See the procedure for handling the TEM_HA and TEM_LA alarms.
----End
Related Information
None
6.130 OTU2SMBIP8
Description
Number of BIP8 bit errors in the SM section at the optical channel transport unit (OTU) layer
Attribute
Performance Event Performance Event Type
ID
Impact on System
Bit errors occur in the services. Identify the causes and resolve the problem in a timely
manner. Otherwise, alarms may be generated, and the signal transmission quality deteriorates.
Related Alarms
Alarm Name Correlation
SM_BIP8_OVER This alarm is generated when the number of BIP8 bit errors in the
SM section at the OTU layer exceeds the threshold.
SM_BIP8_SD This alarm is generated when the number of BIP8 bit errors in the
SM section at the OTU layer exceeds the degrade threshold.
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None.
6.131 OTUk_BBE
Description
OTU background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.132 OTUk_BBER
Description
OTU ratio of background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.133 OTUk_BIAES
Description
OTU SM section backward introducing alignment errored second
Impact on System
There are errors in frame alignment. Identify the cause and solve the problem in a timely
manner to ensure the signal transmission quality.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical port is within the
permitted range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description. If the input optical power is abnormal, see the
procedures for handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
----End
Related Information
None
6.134 OTUk_ES
Description
OTU errored second
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.135 OTUk_FEBBE
Description
OTU SM section far end background block error
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors
increases, identify the cause and solve the problem in a timely manner to avoid any alarm,
therefore ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.136 OTUk_FEBBER
Description
OTU SM section ratio of far end background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.137 OTUk_FEES
Description
OTU SM section far end errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.138 OTUk_FESES
Description
OTU SM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Identify the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.139 OTUk_FESESR
Description
OTU SM section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Identify the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.140 OTUk_FEUAS
Description
OTU SM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.141 OTUk_IAES
Description
OTU SM section introducing alignment errored second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.
Related Alarms
Alarm Name Correlation
OTUk_LOF OTU frame loss. The upstream station detects the LOF alarm and
then inserts IAE. The local station reports OTUk_IAES.
Procedure
Step 1 See the procedure for handling the OTUk_LOF alarm.
----End
Related Information
None
6.142 OTUk_SES
Description
OTU severely errored second
Impact on System
There are severely errored second in the services. Identify the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.143 OTUk_SESR
Description
OTU ratio of severely errored second
Impact on System
There are severely errored second in the services. Identify the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.144 OTUk_TMP
Description
Total period for monitoring performance of OTU signals in the SM section
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.145 OTUk_UAS
Description
OTU unavailable second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.146 PCLSOP
Description
Per-channel laser output power, indicating the optical power of a channel of signals monitored
by the spectrum analyzer unit.
It includes:
l PCLSOPMAX: stands for the maximum value during a period of time.
l PCLSOPMIN: stands for the minimum value during a period of time.
l PCLSOPCUR: stands for the current value.
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.147 PCLSSN
Description
Per-channel OSNR, indicating OSNR of a channel of signals monitored by the spectrum
analyzer unit.
It includes:
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.148 PCLSWL
Description
Per-channel center wavelength, indicating the center wavelength of a channel among optical
signals monitored by the spectrum analyzer unit.
It includes:
l PCLSWLMAX: stands for the maximum value during a period of time.
l PCLSWLMIN: stands for the minimum value during a period of time.
l PCLSWLCUR: stands for the current value.
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.149 PCLSWLO
Description
Per-channel center wavelength deviation, indicating the deviation between the ITU-T standard
wavelength and the wavelength of a channel among optical signals monitored by the spectrum
analyzer unit.
It includes:
l PCLSWLOMAX: stands for the maximum value during a period of time.
l PCLSWLOMIN: stands for the minimum value during a period of time.
l PCLSWLOCUR: stands for the current value.
Impact on System
None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.150 PHASEOFFSET
Description
Time deviation between the master clock and a slave clock. It includes the
MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET performance
parameters, which indicate the maximum, minimum, and average time deviations
respectively.
Impact on System
It is an indicator of the IEEE 1588v2 performance and has no impact on services.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 None
----End
Related Information
None
6.151 PUMPORP
Description
Pump optical reflection power
It includes:
Impact on System
If the detected reflection optical power is greater than 15 dBm, the laser will be automatically
shut down.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 If the ORP_CRITICAL_HI alarm is generated, see the related handling procedure.
----End
Related Information
None
6.152 RMIOP
Description
Input optical power of the Raman amplifier
It includes:
l RMIOPMAX: Maximum input optical power of the Raman amplifier.
l RMIOPMIN: Minimum input optical power of the Raman amplifier.
l RMIOPCUR: Current input optical power of the Raman amplifier.
Impact on System
None
Related Alarms
Alarm Name Correlation
RM_RLOS Loss of input reverse pump optical signals. This alarm is reported
when input reverse pump optical signals are lost.
Procedure
Step 1 See the procedure for handling the RM_RLOS alarm.
----End
Reference
None
6.153 RPL
Description
Input optical power
It includes:
l RPLMAX: stands for the maximum value during a period of time.
l RPLMIN: stands for the minimum value during a period of time.
Impact on System
The performance event does not affect the equipment and the system. If the input optical
power is excessively high, the laser may be damaged. If the input optical power is excessively
low, the laser may fail to detect the signals. You can know the normal range of the input
optical power by querying the specifications for related optical ports.
Related Alarms
Alarm Name Correlation
IN_PWR_LOW This alarm is generated when the input optical power is lower
than the lower threshold of the input optical power.
IN_PWR_HIGH This alarm is generated when the input optical power is higher
than the upper threshold of the input optical power.
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None
6.154 RS_TMP
Description
Total period for monitoring performance of regenerator section
Impact on System
None
module cannot be found or an optical path is not used. When ports are working properly, the
value of RS_TMP, which is expressed in seconds, increases with the working time.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.155 RSBBE
Description
RS background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the B1_EXC alarms.
----End
Related Information
None
6.156 RSES
Description
Regenerator section (RS) errored second
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the B1_EXC alarms.
----End
Related Information
None
6.157 RSOFS
Description
RS out-of-frame second
Impact on System
This performance event indicates that the frame headers cannot be identified in five or more
consecutive frames in the received signals of the line board. The board enters the out-of-frame
state. As a result, the services are unavailable. If the out-of-frame state lasts for 3 ms, the
board enters the loss-of-frame state and the R_LOF alarm is generated.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 Check whether the fibers are damaged and whether the connectors are properly installed.
Clean the fiber connectors.
Step 2 Check whether the input optical power of the input port of the board is within the permitted
range using an optical power meter. For the optical power specifications of the specific board,
see "Technical Specifications" in the Product Description. If the power is not within the
permitted range, add proper attenuation by adding a fix optical attenuator (FOA) or a variable
optical attenuator (VOA).
----End
Related Information
None
6.158 RSOOF
Description
Count of out-of-frame events in the regenerator section
Impact on System
When the performance event occurs, the frame alignment bytes are lost. As a result, the
services are interrupted.
Related Alarms
Alarm Name Correlation
R_LOF When the R_OOF alarm lasts for 3 ms, the alarm is reported.
Procedure
Step 1 See the procedures for handling the R_OOF and R_LOF alarms.
----End
Related Information
None
6.159 RSSES
Description
RS severely errored second
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal
transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the B1_EXC alarms.
----End
Related Information
None
6.160 RSUAS
Description
RS unavailable second
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely
manner because the bit errors have affected the signal transmission quality.
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the B1_EXC alarms.
----End
Related Information
None
6.161 SUMIOP
Description
Total input optical power
It includes:
Impact on System
If the total input optical power is excessively high, the optical modules on the local board and
the downstream board may be damaged and cause bit errors in the services or even service
interruption. If the total input optical power is excessively low, the single-wavelength optical
signals output by the board may be lost and cause bit errors in the services or even service
interruption.
SUMIOP is the total input optical power of the demultiplexer and optical amplifier boards.
Related Alarms
Alarm Name Correlation
IN_PWR_HIGH This alarm is generated when the input optical power is higher than
the upper threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power higher than the
upper threshold.
IN_PWR_LOW This alarm is generated when the optical power input by board is
lower than the lower threshold. Inaccurate optical power detection
or faulty optical module can cause the input optical power lower
than the lower threshold.
SUM_INPWR_HI This alarm is generated when the detected total input optical power
is higher than the upper threshold.
SUM_INPWR_LO This alarm is generated when the detected total input optical power
W is lower than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
historical performance value and the change in optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the
IN_PWR_HIGH or SUM_INPWR_HI alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
historical performance value and the change in optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW
or SUM_INPWR_LOW alarm.
----End
Related Information
None
6.162 SUMOOP
Description
Total output optical power
It includes:
Impact on System
The total output power has impact on the services. If the total output power is excessively
high, the input optical power of the downstream board may be excessively high. As a result,
bit errors are generated in the services or even the services are interrupted. In addition, the
receiver module of the OTU at the downstream station may be damaged. If the total output
power is excessively low, the input optical power of the downstream board may be
excessively low. As a result, bit errors are generated in the services or even the services are
interrupted.
Related Alarms
Alarm Name Correlation
OUT_PWR_HIGH This alarm is generated when the optical power output by board is
higher than the upper threshold. Inaccurate optical power detection
or faulty optical module can cause the input optical power higher
than the upper threshold.
OUT_PWR_LOW This alarm is generated when the optical power output by board is
lower than the lower threshold. Inaccurate optical power detection
or faulty optical module can cause the input optical power lower
than the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
historical performance value and the change in optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the
OUT_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
historical performance value and the change in optical power is not caused by normal
operations (such as expansion or upgrade), see the procedure for handling the
OUT_PWR_LOW alarm.
Step 3 If an alarm is generated, see the related handling procedure.
----End
Related Information
None
6.163 TDC
Description
Dispersion compensation value
It includes:
l TDCMAX: stands for the maximum dispersion compensation value during a period of
time.
l TDCMIN: stands for the minimum dispersion compensation value during a period of
time.
l TDCCUR: stands for the current dispersion compensation value during a period of time.
Impact on System
None
Related Alarms
Alarm Name Correlation
Procedure
Step 1 See the procedure for handling the OTUk_LOF alarm.
----End
Related Information
None
6.164 TLB
Description
Laser bias current value
It includes:
Impact on System
This performance event does not affect the equipment and the system. If the bias current of
the laser is beyond the normal range, however, the laser fails to work or is going to the end of
its life. As a result, the services are interrupted. If the bias current is within the permitted
range, you do not need to take any action.
Related Alarms
Alarm Name Correlation
TF When the bias current of the laser is beyond the normal range, the
alarm is reported, showing transmission failure of the laser.
LSR_WILL_DIE When the bias current of the laser is less than the TF value, the
alarm is reported, indicating that the life of the laser is going to
the end.
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None
6.165 TPL
Description
Output optical power
It includes:
Impact on System
The performance event does not affect the equipment and the system. If the output optical
power of the laser is beyond the normal range, however, the laser fails to work or is going to
the end of its life. As a result, the services are interrupted. If the output optical power is within
the permitted range, you do not need to take any action.
Related Alarms
Alarm Name Correlation
TF When the output optical power is beyond the normal range and
this causes transmission failure of the laser, the alarm is reported.
LSR_WILL_DIE When the output optical power is greatly beyond the normal
range, the alarm is reported, indicating that the life of the laser is
going to the end.
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None
6.166 VC3BBE
Performance Event Meaning
VC-3 background block error
Possible Causes
VC3BBE indicates bit errors detected in a verification and excluding the higher order path
unavailable time and higher order path severely errored second.
External causes:
l The fiber performance is degraded, and the attenuation of the fiber is excessively high.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end
is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the service board do not work with each other properly.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
Procedure
Step 1 Eliminate external causes. For example, the grounding is improper or the operating
temperature is high. The receive optical power of the service board is excessively low or high.
When this occurs, ground the equipment properly or provide a proper operating environment
for the equipment. For more information about solving the optical power problem, see the
6.153 RPL performance. Then, check whether bit errors occur on the service boards.
Step 2 If all the service boards of an NE have bit errors, the clock unit might be faulty. When this
occurs, replace the clock unit.
Step 3 If only a service board reports that bit errors exist, the local service board might be faulty or
that the opposite NE or fibers are faulty. Locate the faulty board using the loopback method.
Then, replace the faulty board.
----End
Reference
None.
6.167 VC3CSES
Performance Event Meaning
VC-3 continuous severely errored second
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 attenuation of the fiber is excessively high.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end
is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the service board do not work with each other properly.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
Procedure
Step 1 See 6.168 VC3ES.
----End
Reference
None.
6.168 VC3ES
Performance Event Meaning
VC-3 errored second
Possible Causes
The VC3ES performance event occurs when one or multiple bit error blocks are detected in
one second or, when the R_LOS, R_LOF, and MS_AIS alarms are detected on the optical
port, or when the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected over the path.
External causes:
l The fiber performance is degraded, and the attenuation of the fiber is excessively high.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end
is faulty.
Relevant Alarms
Alarm Name Correlation
Procedure
Step 1 If the R_LOS/R_LOF alarm is generated, a fiber cut, high attenuation, received overload or
faulty board might exist.
1. If the receive optical power is overloaded, add an attenuator.
2. Check whether the optical fiber cables are intact and whether the connectors are clean
and properly connected. Replace the fibers or clean the fiber connectors, if necessary.
3. If the board is faulty, replace the board.
----End
Reference
None.
6.169 VC3FEBBE
Performance Event Meaning
VC-3 far end background block error
Possible Causes
VC3FEBBE indicates the returned bit errors excluding the bit errors occurring in the VC3 far
end unavailable time and VC3 far end severely errored seconds.
External causes:
l The fiber performance degrades and the attenuation is excessively high at the opposite
station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the service board do not work with each other properly 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
Procedure
Step 1 See 6.166 VC3BBE to handle the NE at the opposite end.
----End
Reference
None.
6.170 VC3FECSES
Performance Event Meaning
VC-3 far end consecutive severely errored second
Possible Causes
When a consecutive VC3FECSES sequence is detected, the VC3FECSES performance event
occurs. When unavailable time comes or VC3FECSES is absent in one second, the
VC3FECSES sequence ends.
External causes:
l 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 improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the service board do not work with each other properly 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
Procedure
Step 1 See 6.171 VC3FEES.
----End
Reference
None.
6.171 VC3FEES
Performance Event Meaning
VC-3 far end errored second
Possible Causes
The VC3FEES performance event occurs when one or multiple bit errors are returned by the
G1 byte in one second or when the LP_RDI_VC3 alarm is detected on the path.
External causes:
l The fiber performance degrades and the attenuation is excessively high at the opposite
station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the service board do not work with each other properly 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
Procedure
Step 1 If the LP_RDI_VC3 alarm is generated:
1. Check whether the service board of the opposite station receives an alarm such as
TU_AIS_VC3, TU_LOP_VC3 and LP_UNEQ_VC3. If yes, first clear the alarm.
2. If the service board of the opposite station does not receive an alarm such as
TU_AIS_VC3, TU_LOP_VC3 and LP_UNEQ_VC3, or if the local station still reports
the LP_RDI_VC3 alarm after the opposite station ends this kind of alarm, check whether
the opposite station or the local station is faulty by looping back the fibers.
3. If the receive unit of the opposite station is faulty, replace the relevant board.
4. If the transmit part of the local station is faulty, replace the SCC board.
----End
Reference
None.
6.172 VC3FESES
Performance Event Meaning
VC-3 far end severely errored second
Possible Causes
The VC3FESES performance event occurs when not less than 15% bit errors are contained in
the message returned in one second or at least one severely disturbed period (SDP) occurs.
SDP occurs when the BER of all the continuous blocks in a period of at least four continuous
blocks or 1 ms (select the longer period) is lower than 10-2, or when the LP_RDI_VC3 alarm
is generated.
External causes:
l The fiber performance degrades and the attenuation is excessively high at the opposite
station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the service board do not work with each other properly 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
Procedure
Step 1 See 6.171 VC3FEES.
----End
Reference
None.
6.173 VC3FEUAS
Performance Event Meaning
VC-3 far end unavailable second
Possible Causes
VC3FEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l The fiber performance degrades and the attenuation is excessively high at the opposite
station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
l The synchronization performance of the clock is poor at the opposite station.
l The cross-connect unit and the service board do not work with each other properly 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
Procedure
Step 1 See 6.171 VC3FEES.
----End
Reference
None
6.174 VC3SES
Performance Event Meaning
VC-3 far end severely errored second
Possible Causes
The VC3SES performance event occurs when not less than 15% bit errors are detected in one
second or at least one severely disturbed period (SDP) occurs. The SDP indicates that the
BER of all the consecutive blocks is not lower than 10-2 or the R_LOS, R_LOF and MS_AIS
alarms are generated in a period of at least four consecutive blocks or i ms (the longer one is
selected), or the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected on the path.
External causes:
l The fiber performance is degraded, and the attenuation of the fiber is excessively high.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end
is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the service board do not work with each other properly.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
Procedure
Step 1 See 6.168 VC3ES.
----End
Reference
None.
6.175 VC3UAS
Performance Event Meaning
VC-3 unavailable second
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 attenuation of the fiber is excessively high.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
l The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end
is faulty.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the service board do not work with each other properly.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name Correlation
Procedure
Step 1 See 6.168 VC3ES.
----End
Reference
None
6.176 WCV
Description
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).
Impact on System
When the pump laser works properly, there is no impact on the services. If an alarm is
generated, identify the cause.
Related Alarms
Alarm Name Correlation
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.
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.
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the related handling procedure.
Step 2 If the LSR_WILL_DIE alarm is generated, see the related handling procedure.
----End
Related Information
None
7 Event List
ROADM wave check event Critical When the system starts a wavelength
resource consistency check, an ROADM
wave check event is reported.
ROADM wave reconfig event Critical When actions such as setting wavelength
blocking and deleting intra-board optical
cross-connections are performed, an
ROADM wave reconfig event is reported.
ROADM power adjust event Critical When the optical power equalization
adjustment at an ROADM node is started, an
ROADM power adjust event is reported.
OWSP abnormal event Major This event is reported when the optical
wavelength shared protection switching
occurs.
8 Event Processing
This chapter describes information relevant to event handling, including event descriptions,
event attribute, event parameters, impacts of events on the system, event causes, and event
handling procedures.
NOTE
In the case of an event, refer to its handling procedure to clear it; if this event persists, contact a
customer service technician of Huawei for troubleshooting.
When you view an event on the network management system, select the event. In the Detail
Description in the Event Details field display the related parameters of the event.
8.1 OWSP abnormal event
8.2 ODUk SPRing abnormal event
8.3 RMON performance value is above the upper limit
8.4 RMON module performance value is lower than the lower threshold
8.5 1+1 Equipment Level Protection Switching Event Report
Attribute
Event Severity Event Type
Major Communication
Parameter
Parameter Description
Parameter Description
Impact on System
When the switching occurs in the wavelength shared protection group, the services in the
system are transiently interrupted. When this event is reported, it indicates that the service in
the current working channel of the protection group may be abnormal. In this case, find and
rectify the fault.
Possible Causes
l Cause 1: The current working channel is abnormal.
l Cause 2: An external switching command is issued.
Procedure
l Cause 1: The current working channel is abnormal.
a. Find out the cause and rectify the fault according to the alarm information reported
in the current working channel. For details on the operation, see Alarm Processing
parts for respective alarms.
l Cause 2: An external switching command is issued.
a. Ignore the event.
----End
Related Information
None
Attribute
Event Severity Event Type
Major Communication
Parameter
Parameter Description
Parameter Description
Parameter Description
Impact on System
When the switching occurs in the ODUk SPRing protection group, the service is transiently
interrupted.
After this event is reported, if the ODUk SPRing protection group is currently in the
switching page, it indicates that the service in the westbound working channel or eastbound
working channel in the ODUk SPRing protection group is abnormal. In this case, find and
rectify the fault.
Possible Causes
l Cause 1: The user issues an external switching command, such as forced switching or
manual switching. Hence, in the ODUk SPRing protection group, the working channel in
a direction is switched to the protection channel in another direction, or the protection
channel in a direction is switched to the working channel in another direction. In this
case, this event is reported.
l Cause 2: When the service in the working channel of the ODUk SPRing protection group
is abnormal, the service is automatically switched to the protection channel. When the
service in the protection channel is abnormal, the service is automatically switched to the
working channel. Hence, this event is reported.
l Cause 3: If the service in the working channel of the ODUk SPRing is restored, after the
WTR time elapses, the service in the protection channel is automatically switched to the
working channel. Hence, this event is reported.
Procedure
l Cause 1 or Cause 3: The user issues an external switching command, or after the WTR
time elapses, the service in the protection channel is automatically switched to the
working channel.
a. Ignore the event.
l Cause 2: The service is automatically switched to the protection channel
a. On the U2000, query the related switching alarms. For details, see Handling
Procedure parts for respective alarms.
----End
Related Information
None
Attribute
Event Severity Event Type
Minor Communication
Parameter
Parameter Description
Parameter Description
Impact on System
The quality of the Ethernet service is degraded, or even the services in the system are
interrupted.
Possible Causes
l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly
transmits the data packets.
l Cause 2: The working modes of the ports at the local and opposite ends mismatch.
l Cause 3: The optical line attenuation is excessively large or the receive optical power is
abnormal.
l Cause 4: The optical fiber is damaged or the fiber connector is untidy.
l Cause 5: The board that reports this alarm is faulty.
Procedure
l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly
transmits the data packets.
a. Use the smartbits equipment to check whether bit errors occur in the data
transmitted at the client side. If bit errors occur, find and rectify the fault of the
client-side equipment.
l Cause 2: The working modes of the ports at the local and opposite ends mismatch.
a. On the U2000, query whether the working modes of the ports at the two ends of the
equipment match. If the working modes mismatch, adjust the working modes of the
ports according to the actual situation.
l Cause 3: The optical line attenuation is excessively large or the receive optical power is
abnormal.
a. Check whether the received optical power of the interface is within the normal
range by using the U2000. For the optical power specifications of the specific
board, see "Technical Specifications" in the Product Description.If the optical
power is not within the normal range, takes handling measures according to the
handling method of the IN_PWR_HIGH or IN_PWR_LOW alarm.
l Cause 4: The optical fiber is damaged or the fiber connector is untidy.
a. Check the fiber connector. If it is dirty, clean or replace the fiber connector.
l Cause 5: The board that reports this alarm is faulty.
a. If this event persists, replace the faulty board.
----End
Related Information
None
Attribute
Event Severity Event Type
Minor Communication
Parameter
Parameter Description
Parameter Description
Impact on System
When this event is reported, it indicates that the related Ethernet performance values are
recovered. The quality of the Ethernet service in the system is improved.
Possible Causes
The fault of the system is rectified, and the performance value is recovered.
Procedure
l Ignore the event.
----End
Related Information
None
Attribute
Event Severity Event Type
Critical Equipment
Parameter
Parameter Description
Impact on System
When the cross-connect board protection switching occurs in the protection group, the service
may be transiently interrupted.
Possible Causes
l Cause 1: The user issues an external switching command, such as forced switching or
clearing. In this case, the working unit of the protection group is switched to the
protection unit, or the protection unit is switched to the working unit, this event is
reported.
l Cause 2: When one unit in the protection group is abnormal, the protection group is
switched to another unit. In this case, this event is reported.
Procedure
l Cause 1: The user issues an external switching command.
a. Ignore the event.
l Cause 2: When one unit in the protection group is abnormal, the protection group is
switched to another unit. In this case, this event is reported.
a. If this event persists, replace the faulty board. For details on operations, see Parts
Replacement.
----End
Related Information
None
A Glossary
Numerics
3G See 3rd Generation.
3R reshaping, retiming, regenerating
3rd 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.
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
AA authentication authorization
AAA See Authentication, Authorization and Accounting.
AC alternating current
ACH associated channel header
ACK See acknowledgement.
ACL See access control list.
ACR allowed cell rate
ACS See Application Control Server.
ADC analog to digital converter
ADM add/drop multiplexer
ADSL See asymmetric digital subscriber line.
AF See assured forwarding.
Advanced A carrier-class processing platform that is designed to meet the service application
Telecommunications requirement of high performance, high specialization, and high integration.
Application
Environment (ATAE)
Application Control A subsystem of the Media Entertainment Middleware (MEM), used for providing a
Server (ACS) service control interface for the Electronic Program Guide (EPG) server.
Authentication Header A protocol that provides connectionless integrity, data origin authentication, and anti-
(AH) replay protection for IP data.
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.
access control list A list of entities, together with their access rights, which are authorized to access a
(ACL) resource.
access key ID (AK) An ID that confirms the identity of a user accessing the object-based storage system.
One access key ID belongs to only one user, but one user can have multiple access key
IDs. The object-based storage system recognizes the users accessing the system by
their access key IDs.
acknowledgement A response sent by a receiver to indicate reception of information. Acknowledgements
(ACK) may be implemented at any level, including the physical level (using voltage on one or
more wires to coordinate a transfer), link level (indicating transmission across a single
hardware link), or higher levels.
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.
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.
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.
automatic level control A function that keeps output power of components in a system essentially constant,
(ALC) even when line attenuation in a section of the system increases.
automatic power A function to automatically equalize channel optical power at the transmitter end,
equilibrium (APE) ensuring a required optical power flatness and OSNR at the receiver end.
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/S Browser/Server
BA booster amplifier
BBC See battery backup cabinet.
BBER background block error ratio
BC boundary clock
BDI See backward defect indication.
BE See best effort.
BEI backward error indication
BER Bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIAE backward incoming alignment error
BIOS See basic input/output system.
BIP-8 See bit interleaved parity-8.
BITS See building integrated timing supply.
BMC best master clock
BOM bill of materials
BPDU See bridge protocol data unit.
BPS board protection switching
BPSK See binary phase shift keying.
BRA See basic rate access.
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 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 domain A group of network stations that receives broadcast packets originating from any
device within the group. The broadcast domain also refers to the set of ports between
which a device forwards a multicast, broadcast, or unknown destination frame.
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.
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.
byte A unit of computer information equal to eight bits.
C
CAPEX capital expenditure
CAR committed access rate
CBS See committed burst size.
CCM continuity check message
CD chromatic dispersion
CDR See call detail record.
CE See customer edge.
CENELEC European Committee for Electrotechnical Standardization
CES See circuit emulation service.
CGMP Cisco Group Management Protocol
CIR committed information rate
CIST See Common and Internal Spanning Tree.
CLI command-line interface
CLNP connectionless network protocol
CMEP connection monitoring end point
CMI coded mark inversion
carrier sense multiple Carrier sense multiple access with collision detection (CSMA/CD) is a computer
access with collision networking access method in which:
detection (CSMA/CD)
l A carrier sensing scheme is used.
l A transmitting 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.
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.
circulation The number of copies of a newspaper or magazine per issue that are circulated in the
market
clock synchronization A process of synchronizing clocks, in which the signal frequency traces the reference
frequency, but the start points do not need to be consistent. This process is (also
known as frequency synchronization).
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.
comma separated A CSV file is a text file that stores data, generally used as an electronic table or by the
values (CSV) database software.
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.
common public radio A common standard of the key internal interface between the REC and the RE of the
interface (CPRI) wireless base station. This standard was established by Huawei, Ericsson, NEC,
Siemens, and Nortel in June 2003. It aims at standardizing the baseband and RF
interface. The CPRI has a set of mature standards, which advance the standard and
equipment. The major feature of the CPRI is that baseband is separated from RF to
reduce the cost of engineering, equipment room, and equipment.
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.
composite service An aggregation of a series of services relevant to each other.
configuration data A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other NEs in a network. Therefore, configuration data is the key
factor that determines the operation of an entire network.
consistency check A function that is used to check the consistency of service data and resource data
between two softswitches that have the dual homing relation. This ensures the
consistency of service data and resource data between the softswitches.
control VLAN A VLAN that transmits only protocol packets.
crossover cable A twisted pair patch cable wired in such a way as to route the transmit signals from
one piece of equipment to the receive signals of another piece of equipment, and vice
versa.
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
DAPI destination access point identifier
DB database
DBMS Database Management System
DBPS distributed board protect system
DC direct current
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.
DCE See data circuit-terminating equipment.
DCF See dispersion compensation fiber.
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
DEI device emulation interrupt
DHCP See Dynamic Host Configuration Protocol.
DIP switch dual in-line package switch
DLAG See distributed link aggregation group.
DM See delay measurement.
DMUX demultiplexer
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.
designated switch A designated switch of a device is a switch that is directly connected to the device and
forwards BPDUs to the device.
detection sensitivity The capability for a detector to respond to an exception.
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 signal processor A microprocessor designed specifically for digital signal processing, generally in real
(DSP) time.
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.
dispersion A type of fiber that uses negative dispersion to compensate for the positive dispersion
compensation fiber of the transmitting fiber to maintain the original shape of the signal pulse.
(DCF)
dispersion A type of module that contains dispersion compensation fibers to compensate for the
compensation module dispersion of the transmitting fiber.
(DCM)
distribute service A distributed service development and running framework, in which services comply
framework (DSF) with standard specifications, and can be loaded and run by containers. This framework
provides a range of services including registration, detection, routing, and distributed
access.
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.
domain A logical subscriber group based on which the subscriber rights are controlled.
dotted decimal A format of IP address. IP addresses in this format are separated into four parts by a
notation dot "." with each part is in the decimal numeral.
downlink traffic The network traffic transferred into an internal carrier network. Noticeably, downlink
refers to sending traffic to user-end link nodes.
downstream In an access network, the direction of transmission toward the subscriber end of the
link.
dual feed and selective A channel used to transmit monitoring data on an optical transmission network. The
receiving monitoring data is transmitted on the data communications channel as part of the
overhead of the service signal.
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.
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It provides
thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization,
and timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as
speech channels. Each timeslot sends or receives an 8-bit data per second. Each frame
sends or receives 256-bit data per second. 8000 frames will be sent or received per
second. Therefore the line data rate is 2.048 Mbit/s.
E2E end to end
EAPE enhanced automatic power pre-equilibrium
EBS See excess burst size.
EDFA See erbium-doped fiber amplifier.
EEC Ethernet Electric Interface PMC Card
EEPROM See electrically erasable programmable read-only memory.
EF See expedited forwarding.
EFM Ethernet in the First Mile
EIR See excess information rate.
EMC See electromagnetic compatibility.
EMF element management framework
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logic device.
EPON See Ethernet passive optical network.
ERPS Ethernet ring protection switching
ESC See electric supervisory channel.
ESCON See enterprise system connection.
ESD electrostatic discharge
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
F
FBG fiber Bragg grating
FC See Fibre Channel.
FDB flash database
FDD See frequency division duplex.
fixed mobile Communication service provided based on the combination of fixed-line and wireless
convergence (FMC) technologies. Service providing, access technologies, and terminal devices on an FMC
network are independent from each other. The same service can be obtained from
various access networks. Subscribers from different access networks can obtain and
use the same service.
flow An aggregation of packets that have the same characteristics. On boards, it is a group
of packets that have the same quality of service (QoS) operation.
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 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.
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.
G
G-ACH generic associated channel header
GAL generic associated channel header label
GCC general communication channel
GE Gigabit Ethernet
GE ADM A technique that improves the transmission of GE services on a metropolitan area
network. Using this technique, equipment configured with a high-speed backplane can
separately transmit, aggregate, or divert GE services over electrical-layer wavelengths
or sub-wavelengths. This achieves cross-connections of wavelengths and end-to-end
management of sub-wavelengths over a single device. GE ADM enables GE
convergence and cross-connections at the same time, thereby ensuring that network
resources are used effectively.
H
HA system high availability system
HCS higher order connection supervision
HD-SDI high definition serial digital interface
HDB3 See high density bipolar of order 3 code.
HDTV See high definition television.
HP higher order path
HPT higher order path termination
HSDPA See High Speed Downlink Packet Access.
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICMP See Internet Control Message Protocol.
ID See identity.
IEC International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers.
IETF Internet Engineering Task Force
IF See intermediate frequency.
IGMP See Internet Group Management Protocol.
IGRP Interior Gateway Routing Protocol
ILM incoming label map
IM See instant messaging.
IMP Instant Message Platform
IP address A 32-bit (4-byte) binary number that uniquely identifies a host connected to the
Internet. An IP address is expressed in dotted decimal notation, consisting of the
decimal values of its 4 bytes, separated with periods; for example, 127.0.0.1. The first
three bytes of the IP address identify the network to which the host is connected, and
the last byte identifies the host itself.
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.
identity (ID) The collective aspect of the set of characteristics by which a thing is definitively
recognizable or known.
input jitter tolerance The measure of a receiver's ability to tolerate jitter on an incoming waveform.
insertion loss The loss of power that results from inserting a component, such as a connector,
coupler, or splice, into a previously continuous path.
instant messaging (IM) A form of real-time communication between two or more people based on typed text.
The text is conveyed via devices connected over a network such as the Internet.
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.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF) signal.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations,
and control system instability.
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.
LAPS Link Access Protocol-SDH
LAS line assurance system
LB See loopback.
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.
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.
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.
link status The running status of a link, which can be Up, Down, backup, or unknown.
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.2ag 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.
M
MA maintenance association
MAC See Media Access Control.
MAC address A link layer address or physical address. It is six bytes long.
MAC address aging A function that deletes MAC address entries of a device when no packets are received
from this device within a specified time period.
MADM multiple add/drop multiplexer
MBB mobile broadband
MD See maintenance domain.
MD5 See message digest algorithm 5.
MDF See main distribution frame.
ME See maintenance entity.
MEG See maintenance entity group.
MEP maintenance association end point
MFAS See multiframe alignment signal.
MGC media gateway controller
MIB See management information base.
MID message identification
MIN mobile identification number
MIP See maintenance entity group intermediate point.
MLD See multicast listener discovery.
MML man-machine language
MNO See mobile network operator.
MOP See method of procedure.
MP maintenance point
MPI-R main path interface at the receiver
MPI-S main path interface at the transmitter
MPID maintenance point identification
MPLS See Multiprotocol Label Switching.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MRI See measurement result integrity.
MRO mobility robustness optimization
MS multiplex section
MS-AIS See multiplex section alarm indication signal.
MS-PW See multi-segment pseudo wire.
MSA multiplex section adaptation
MSDP See Multicast Source Discovery Protocol.
MSI mobile station identifier
MSOH multiplex section overhead
maintenance entity A MEG consists of MEs that meet the following criteria:
group (MEG)
l Exist within the same management edges.
l Have the same MEG hierarchy.
l Belong to the same P2P or P2MP connection.
maintenance entity An intermediate point in a MEG, which is able to forward OAM packets and respond
group intermediate to some OAM packets, but unable to initiate the transmission of OAM packets or
point (MIP) perform any operations on network connections.
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.
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.
measurement result Percentage of the number of the actually reported measurement results to the number
integrity (MRI) of the measurement results that should be reported.
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.
method of procedure A document that describes the process of executing a specific task. It facilitates the
(MOP) mutual understanding of and cooperation between a service provider and a carrier.
Before executing a task, the representatives from both parties confirm this document
and reach an agreement on it. This document describes who, when, where, why, and
how to execute a task and what to do.
mobile network A company that has a network infrastructure, sells large network capacities, and
operator (MNO) provides transparent network channels.
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.
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
NE Explorer The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NE Panel A graphical user interface, of the network management system, which displays
subracks, boards, and ports on an NE. On the NE Panel, the user can complete most of
the configuration, management and maintenance functions for an NE.
NHLFE next hop label forwarding entry
NM network management
NMC network management center
NNI network-to-network interface
NOC network operations center
NOS network operating system
NP See network processor.
NPE network provider edge
O
O&M operation and maintenance
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
OAMS Optical fiber line Automatic Monitoring System
OC ordinary clock
OCI open connection indication
OCP optical channel protection
Open Systems An open network architecture model developed by the International Organization for
Interconnection Standardization (ISO) and the ITU-T. This module consists of 7 layers. Each layer has
reference model (OSI special network functions, such as addressing, flow control, error control,
reference model) encapsulation, and reliable message transmission. The lowest layer (physical layer) is
closest to media technologies. The lower two layers are implemented in hardware and
software, and the upper five layers are implemented only in software. The highest
layer (application layer) is closest to users. The OSI reference model is a widely used
method of understanding network functions.
Optical A worldwide non-profit organization with membership open to any organization
Internetworking interested in shaping the future of optical internetworking.
Forum (OIF)
operation response The average time taken by a storage device to respond to each request. It is a critical
time (ORT) storage performance indicator.
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 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 line protection Optical line protection is implemented using the dual feeding and selective receiving
(OLP) function. Two pairs of fibers (that is, four fibers) are used. One pair of fibers function
as the working trail and is used to transmit service signals of a line when the line is
normal. The other pair of fibers function as the protection trail and is used to carry
protection switching signals when a fiber cut occurs or the signal attenuation is
excessively large.
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.
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.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PCB See printed circuit board.
PCC protection communication channel
PCN product change notice
PCS physical coding sublayer
PDG polarization-dependent gain
PDH See plesiochronous digital hierarchy.
PDL See polarization-dependent loss.
PDM pulse duration modulation
PDU See power distribution unit.
PE See provider edge.
PER packet error rate
PET polyester
PFI packet forward interface
PGA program global area
PHB See per-hop behavior.
PID photonics integrated device
PIM-DM Protocol Independent Multicast - Dense Mode
PIM-SM Protocol Independent Multicast - Sparse Mode
PLC See packet loss compensation.
PLL See phase-locked loop.
PM performance monitoring
PMD polarization mode dispersion
PMI payload missing indication
PMS Product Management System
PMU power monitoring unit
POH path overhead
PON passive optical network
POTS See plain old telephone service.
PPP Point-to-Point Protocol
Q
QPSK See quadrature phase shift keying.
R
RADIUS See Remote Authentication Dial In User Service.
RAN See radio access network.
RBW reverse-band working
RDI remote defect indication
RED See random early detection.
REG See regenerator.
RF See radio frequency.
RFC See Request For Comments.
RIP See Routing Information Protocol.
RJ45 registered jack45
RMEP remote maintenance association end point
RMON remote network monitoring
RMS resource management system
RMU rack monitoring unit
RNC See radio network controller.
ROADM reconfigurable optical add/drop multiplexer
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.
RSOH regenerator section overhead
RST regenerator section termination
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RSVP-TE See Resource Reservation Protocol-Traffic Engineering.
RTP real-time performance
RX receive
RXD receive data
RZ return to zero
RZ code return-to-zero code
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.
Request For A document in which a standard, a protocol, or other information pertaining to the
Comments (RFC) operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. 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 frequency (RF) A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic
wave. The AC with the frequency lower than 1 kHz is called low-frequency current.
The AC with frequency higher than 10 kHz is called high-frequency current. RF can
be classified into such high-frequency current.
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.
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
recognition Consumer awareness of having seen or heard an advertising message.
reference clock A stable and high-precision autonomous clock that provides frequencies as a reference
for other clocks.
regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
regenerator (REG) A piece of equipment or device that regenerates electrical signals.
regional root The root of the Internal Spanning Tree (IST) and Multiple Spanning Tree Instance
(MSTI) in the MST region. The regional root differs with the topology of the spanning
tree in the MST region.
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.
reservation An action that the charging module performs to freeze a subscriber's balance amount,
free resources, credits, or quotas before the subscriber uses services. This action
ensures that the subscriber has sufficient balance to pay for services.
ring network A network topology in which each node connects to exactly two other nodes, forming
a circular pathway for signals.
S
S-VLAN service virtual local area network
S1 byte A byte to transmit network synchronization status information. On an SDH network,
each NE traces hop by hop to the same clock reference source through a specific clock
synchronization path, realizing synchronization on the entire network. If a clock
reference source traced by an NE is missing, this NE will trace another clock reference
source of a lower level. To implement protection switching of clocks in the whole
network, the NE must learn about clock quality information of the clock reference
source it traces. Therefore, ITU-T defines S1 byte to transmit network synchronization
status information. It uses the lower four bits of the multiplex section overhead S1
byte to indicate 16 types of synchronization quality grades. Auto protection switching
of clocks in a synchronous network can be implemented using S1 byte and a proper
switching protocol.
SAI service area identifier
SAPI service access point identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SBS synchronous information backbone system
SCA selective call acceptance
SCE See service creation environment.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDI See serial digital interface.
SDP See Session Description Protocol.
SELV safety extra-low voltage
SES severely errored second
Secure Shell (SSH) A set of standards and an associated network protocol that allows establishing a secure
channel between a local and a remote computer. A feature to protect information and
provide powerful authentication function for a network when a user logs in to the
network through an insecure network. It prevents IP addresses from being deceived
and simple passwords from being captured.
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.
Session Description A protocol intended for describing multimedia sessions for the purposes of session
Protocol (SDP) announcement, session invitation, and other forms of multimedia session initiation.
Simple network "An IETF protocol for monitoring and managing systems and devices in a network.
management protocol The data being monitored and managed is defined by a MIB. The functions supported
(SNMP) by the protocol are the request and retrieval of data, the setting or writing of data, and
traps that signal the occurrence of events."
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.
security object (SO) A main part of the information security. It is not related with the communication mode
or terminal. It does not only focus on the security of the information exchange but also
provides feasible solutions of security for the user information, including the user
identity authentication, user password, and encryption.
segment A subset of an identity type. This is a different subset from a trust level including but
is not limited to the following examples: A subset based on customer age, a subset
based on where the identity was registered or based, a subset based on the customer's
gender, and a subset based on an association that the identity may have. For example,
an organization is confirmed as a supermarket or a customer is a member of a society.
serial digital interface An interface that transmits data in a single channel in sequence.
(SDI)
service creation A service generation tool that provides a graphical user interface (GUI) for
environment (SCE) programming.
service level agreement A service agreement between a customer and a service provider. SLA specifies the
(SLA) service level for a customer. The customer can be a user organization (source domain)
or another differentiated services domain (upstream domain). An SLA may include
traffic conditioning rules which constitute a traffic conditioning agreement as a whole
or partially.
service support data An identifier that defines data parameters of specific service feature descriptions in the
(SSD) global functional plane.
shaping A process of delaying packets within a traffic stream to cause it to conform to specific
defined traffic profile.
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 fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
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.
split ratio The ratio of the number one to the number of optical signal channels that are split
from a channel of downstream optical signals in a GPON network. A larger split ratio
implies greater optical splitting which creates the need for an increased power budget
to support the physical reach.
standard definition- Standard definition video signal transported by serial digital interface.
serial digital interface
signal (SD-SDI)
structured query A programming language widely used for accessing, updating, managing, and
language (SQL) querying data in a relational database.
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
T1 A North American standard for high-speed data transmission at 1.544Mbps. It
provides 24 x 64 kbit/s channels.
TCM tandem connection monitor
TCN topology change notification
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDM See time division multiplexing.
TIM trail trace identifier mismatch
TLS Transport Layer Security
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.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in
the scenario that the traffic matches network resources provided by the lower layer
devices, avoiding packet loss and congestion.
traffic statistics An activity of measuring and collecting statistics of various data on devices and
telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks.
The statistics also help the operators manage the device operating, locate problems,
monitor and maintain the networks, and plan the networks.
transparent mode A method of binary synchronous text transmission in which only transmission control
characters preceded by the data link escape (DLE) character are processed as
transmission control characters.
transparent A process during which the signaling protocol or data is not processed in the content
transmission but encapsulated in the format for the processing of the next phase.
trunk Physical communications line between two offices. It transports media signals such as
speech, data and video signals.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The
tunnel ensures secure and transparent transmission of VPN information. In most cases,
a tunnel is an MPLS tunnel.
two rate three color An algorithm that meters an IP packet stream and marks its packets based on two
marker (trTCM) rates, Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether
it exceeds or does not exceed the CIR.
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
UNI See user-to-network interface.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
upstream In an access network, the direction that is far from the subscriber end of the link.
upstream board A board that provides the upstream transmission function. Through an upstream
board, services can be transmitted upstream to the upper-layer device.
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-UNI See virtual user-network interface.
VA value assurance
VAS See value-added service.
VB virtual bridge
VBR See variable bit rate.
VC trunk See virtual container trunk.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCPLM virtual concatenation payload mismatch
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VDSL2 See very-high-speed digital subscriber line 2.
VLAN mapping A technology that enables user packets to be transmitted over the public network by
translating private VLAN tags into public VLAN tags. When user packets arrive at the
destination private network, VLAN mapping translates public VLAN tags back into
private VLAN tags. In this manner, user packets are correctly transmitted to the
destination.
VM virtual memory
VOA variable optical attenuator
VPN virtual private network
VPWS See virtual private wire service.
VRRP See Virtual Router Redundancy Protocol.
VSI See virtual switching instance.
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.
value-added service A service provided by carriers and service providers (SPs) together for subscribers
(VAS) based on voice, data, images, SMS messages, and so on. Communication network
technologies, computer technologies, and Internet technologies are used to provide
value-added services.
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 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 circuit A channel or circuit established between two points on a data communications
network with packet switching. Virtual circuits can be permanent virtual circuits
(PVCs) or switched virtual circuits (SVCs) .
virtual concatenation A group of co-located member trail termination functions that are connected to the
group (VCG) same virtual concatenation link.
virtual connection A logical tunnel built in a non-backbone area between two ABRs in a same OSPF
routing domain. It is used to maintain the logical connections between physical
division areas. The two ends of the virtual connection must be ABRs. In addition, to
make a virtual connection effective, the ABRs must be configured at the same time.
The virtual connection is identified by the ID of the peer router.
virtual container trunk The logical path formed by some cascaded VCs.
(VC trunk)
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.
virtual switching An instance through which the physical access links of VPLS can be mapped to the
instance (VSI) virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge
function and can terminate PW.
virtual user-network A virtual user-network interface, works as an action point to perform service
interface (V-UNI) classification and traffic control in HQoS.
W
WAN wide area network
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WFQ See weighted fair queuing.
WLAN See wireless local area network.
WRR weighted round robin
WSS wavelength selective switching
WTR See wait to restore.
WXCP See wavelength cross-connection protection.
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.
wavelength cross- A type of channel protection based on ring network topology. WXCP employs the
connection protection dual feed and selective receiving principle and uses the cross-connection function to
(WXCP) implement service switching between the working and protection channels.
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.
wireless local area A hybrid of the computer network and the wireless communication technology. It uses
network (WLAN) wireless multiple address channels as transmission media and carriers out data
interaction through electromagnetic wave to implement the functions of the traditional
LAN.
X
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
xDSL x digital subscriber line